[MM-37423] Custom Status: Don't show 'Custom Date and Time' for recent statuses

Summary
Custom Status: Don't show 'Custom Date and Time' for recent statuses
Ticket Link
https://mattermost.atlassian.net/browse/MM-37423
Checklist

[ ] Added or updated unit tests (required for all new features)
[ ] Has UI changes
[ ] Includes text changes and localization file updates

Device Information
This PR was tested on:
Screenshots

Release Note

Building app in separate branch.

Hello @AshishDhama,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Building app in separate branch.


fix type mismatch error for arm

Description
Resolved the portable issues of mseed crate for arm target
Testing
Tested this changes with cross compliation for arm target and it complied successfully.

Hi @damb , This PR is ready for review. Thanks

Great. Could you please fix the formatting, firstly. cargo-fmt is your friend. Thanks.

Thank you again. It would be nice if you still could check whether the examples need a fix. In case of errors a PR is very welcome.

Thank you again. It would be nice if you still could check whether the examples need a fix. In case of errors a PR is very welcome.

I have  verified all the examples works as expected.


Add pagination to series index page

Nice entry issue:
Add pagination to the series index page, by reusing the existing pagination component.
Movies index page example:
https://github.com/midarrlabs/midarr-server/blob/master/lib/media_server_web/live/movies_live/index.html.heex#L27-L32
https://github.com/midarrlabs/midarr-server/blob/master/lib/media_server_web/live/movies_live/index.ex#L15-L35

:tada: This issue has been resolved in version 1.12.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[FEAT] - Enhance Cluster onboarding process

Priority
(Medium) I'm annoyed but I'll live
Description
tbd
Reference Issues
No response

Adding to the wishlist:

I can onboard a directly connected cluster from the UI and don't require greenhousectl

API endpoint for onboarding / mass onboarding
Onboard cluster via kubectl ( no need for greenhousectl)

closed with #655


Use nfd release instead of master

Master branch of the NFD project is broken. It broke SGX plugin deployment.
Changed reference to the release tag.

Codecov Report

Merging #823 (e1c11a5) into main (f9e04ad) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #823   +/-   ##
=======================================
  Coverage   54.29%   54.29%
=======================================
  Files          39       39
  Lines        3597     3597
=======================================
  Hits         1953     1953
  Misses       1531     1531
  Partials      113      113

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 f9e04ad...e1c11a5. Read the comment docs.

master has a fix for #739 so we cannot use 0.9.0.

closing. Let's wait for the fix to be merged then.


User configs doesn't understand spaces

If we input in user name spaces, we got error.

"Use one word only, no special characters"
But just remove the spaces and you'll be fine.
This will be probably improved in the future.


MM-26620 Add system console setting to disable ask the community link

Summary
Adds a system console setting to disable ask the community link in help guide dropdown
PR is on top of https://github.com/mattermost/mattermost-webapp/pull/5843. Changes for this PR are at https://github.com/mattermost/mattermost-webapp/commit/0a57fda03ad8facf4c880b29a5a9da7a447e174a
Ticket Link
https://mattermost.atlassian.net/browse/MM-26620
Related Pull Requests
https://github.com/mattermost/mattermost-redux/pull/1188
Screenshots

@jasonblais Can you please provide some clarification on capitalization for "community"
Help text shows "Ask the Community" and the menu option is  "Ask the community".  We should make it consistent.

@jgilliam17 Good catch, it should be consistent.
@sudheerDev Can you help update the help text to read: When true, "As the community" link appears ...

@jgilliam17 Text updated :


Inference in Batch

Hi everyone, I have trained a Padim model and exported to torch and openvino. I would like to know if it is possible to run inference in a batch (16, 32, an so on) images? If so, how could I do it?

Hello. It seems like the export has dynamic axes enabled for batch:
https://github.com/openvinotoolkit/anomalib/blob/d7e7d86411d106369e9cca53d8c148cba659493a/src/anomalib/deploy/export.py#L157-L165
So I think you could pass a batched input, but you'd need to modify the code as current inferencers do it file by file.


added one col view

I am sorry for opening yet another pr, but i wanted to deliever the "one-col view" i didnt do in #65 . Can merge them though if you want. (trying to keep pr small).
let me know what you think
fixes #64

Rebased and reviewed, looks awesome. Thank you so much! And sorry for the delay :)

no problem, but since they re closed i guess i now have to find new changes to make ¯_(ツ)_/¯


refactor: minor test cleanup

Please read contributing guidelines and remove this line.

#9339  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @benesjan and the rest of your teammates on  Graphite


Fix for #734

LGTM.

I think you can also delete this.jobContext.getJobState().setEndTime(workflowContext.getFinishTime()); since it is set again later on: https://github.com/linkedin/gobblin/blob/8fb95bfe27e67cdcdd84ec41d79d2e84b719cb18/gobblin-runtime/src/main/java/gobblin/runtime/AbstractJobLauncher.java#L311

@sahilTakiar Deleted this.jobContext.getJobState().setEndTime(workflowContext.getFinishTime())

@sahilTakiar Updated

LGTM


Add support for declaring section header and footer titles in LMTableView

Since processing instructions are not localized, this would need to be done via elements; for example:
<LMTableView>
    <sectionHeader title="@firstSectionHeader"/>
    ...
    <sectionFooter title="@firstSectionFooter"/>
</LMTableView>

This was prototyped. The use of both tags and processing instructions in the same view was confusing. Since similar behavior can be achieved by using the existing <?sectionHeaderView?> processing instruction with an instance of UITableViewHeaderFooterView, this feature is not critical. Closing.


refactor: refactor mapping functions

Codecov Report

Merging #55 (68560bb) into main (a567a5c) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #55   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           11        11
  Lines          980       983    +3
  Branches       178       178
=========================================
+ Hits           980       983    +3

Impacted Files
Coverage Δ

sdf_wot_converter/converters/sdf_to_wot.py
100.00% <100.00%> (ø)

sdf_wot_converter/converters/utility.py
100.00% <100.00%> (ø)

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 a567a5c...68560bb. Read the comment docs.


WebKit2GTK+ Is Unavailable

Issue Description
When trying to start Site Cloner in King Phisher, I got an error saying that WebKit2GTK+ package is not available.
Reproduction Steps

Start King Phisher client on Windows
Click on Tools > Clone Web Page

Environment Details
Host OS: Windows 7
Error Details / Stack Trace

As it states the WebKit2GTK+ package is unavailable on Windows. This is due to limitations and bugs in the upstream repository that we're trying to resolve. At this time the we've cloning capabilities require that package and because of that are only available on Linux. If you require that feature I recommend you switch to Ubuntu 16.04 LTS for your King Phisher client.


Upgrading from Angular 2 to Angular 4 "Call to Node module failed with error: Error: Uncaught (in promise):"

Hi,
I'm upgrading my current Angular 2 SPA with new yeoman template that use Angular 4.
I've moved all my code but I obtain one cryptic error message on application startup, this is the error message:
 Call to Node module failed with error: Error: Uncaught (in promise): Exception: Call to Node module failed with error: Error: Uncaught (in promise): Error at resolvePromise (C:\Users\utente\Desktop\Progetto.WebApp\ClientApp\dist\vendor.js:83659:31) at resolvePromise (C:\Users\utente\Desktop\Progetto.WebApp\ClientApp\dist\vendor.js:83630:17) at C:\Users\utente\Desktop\Progetto.WebApp\ClientApp\dist\vendor.js:83707:17 at ZoneDelegate.module.exports.ZoneDelegate.invokeTask (C:\Users\utente\Desktop\Progetto.WebApp\ClientApp\dist\vendor.js:83316:31) at Object.onInvokeTask (C:\Users\utente\Desktop\Progetto.WebApp\ClientApp\dist\vendor.js:14877:37) at ZoneDelegate.module.exports.ZoneDelegate.invokeTask (C:\Users\utente\Desktop\Progetto.WebApp\ClientApp\dist\vendor.js:83315:36) at Zone.module.exports.Zone.runTask (C:\Users\utente\Desktop\Progetto.WebApp\ClientApp\dist\vendor.js:83083:47) at drainMicroTaskQueue (C:\Users\utente\Desktop\Progetto.WebApp\ClientApp\dist\vendor.js:83476:35) at <anonymous> at process._tickCallback (internal/process/next_tick.js:169:7)
Any ideas?

Sorry, no clues about that. Since the error is happening inside Zone you might be better looking at Angular docs or raising the question with that community.

@ilMattion Did you remove all references to the older angular2-universal package / angular2-universal-polyfills etc as well?

Hi,
This is my package.json:
"dependencies": {
"angular/animations": "4.1.2",
"angular/common": "4.1.2",
"angular/compiler": "4.1.2",
"angular/core": "4.1.2",
"angular/forms": "4.1.2",
"angular/http": "4.1.2",
"angular/platform-browser": "4.1.2",
"angular/platform-browser-dynamic": "4.1.2",
"angular/platform-server": "4.1.2",
"angular/router": "4.1.2",
"types/node": "7.0.18",
"angular-2-local-storage": "1.0.1",
"angular2-template-loader": "0.6.2",
"aspnet-prerendering": "^2.0.5",
"aspnet-webpack": "^1.0.29",
"awesome-typescript-loader": "3.1.3",
"bootstrap": "3.3.7",
"css": "2.2.1",
"css-loader": "0.28.4",
"es6-shim": "0.35.3",
"event-source-polyfill": "0.0.9",
"expose-loader": "0.7.3",
"extract-text-webpack-plugin": "2.1.2",
"file-loader": "0.11.2",
"html-loader": "0.4.5",
"isomorphic-fetch": "2.2.1",
"jquery": "3.2.1",
"jslinq": "1.0.21",
"json-loader": "0.5.4",
"mydatepicker": "2.0.20",
"ng2-pagination": "2.0.1",
"ng2-bs3-modal": "0.10.4",
"ng2-file-upload": "1.2.1",
"ng2-toasty": "4.0.3",
"ng2-typeahead": "1.2.0",
"ngx-accordion": "0.0.17",
"ngx-popover": "0.0.16",
"preboot": "4.5.2",
"raw-loader": "0.5.1",
"reflect-metadata": "0.1.10",
"rxjs": "5.4.1",
"style-loader": "0.18.2",
"to-string-loader": "1.1.5",
"typescript": "2.3.4",
"typings": "2.1.1",
"url-loader": "0.5.9",
"webpack": "2.6.1",
"webpack-hot-middleware": "2.18.0",
"webpack-merge": "4.1.0",
"zone.js": "0.8.12"
}

@ilMattion Did you ever solve this issue?


step by step instructions?

absolutely no idea what to do or what to download, do i get the dev build? do i go to releases? if so what do i download there?

releases, like almost every other project on GitHub. download the one that is for your os


[SPARK-26350][SS]Allow to override group id of the Kafka consumer

What changes were proposed in this pull request?
This PR allows the user to override kafka.group.id for better monitoring or security. The user needs to make sure there are not multiple queries or sources using the same group id.
How was this patch tested?
The new added unit tests.

cc @tdas

Test build #100048 has started for PR 23301 at commit fccfee1.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/6037/
Test PASSed.

Test build #100048 has finished for PR 23301 at commit fccfee1.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100048/
Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/6039/
Test PASSed.

Merged build finished. Test PASSed.

Test build #100050 has started for PR 23301 at commit bd1c0b8.

Test build #100050 has finished for PR 23301 at commit bd1c0b8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100050/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/6100/
Test PASSed.

Test build #100115 has started for PR 23301 at commit c279fd5.

Test build #100256 has started for PR 23301 at commit d9d3065.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/6228/
Test PASSed.

Test build #100256 has finished for PR 23301 at commit d9d3065.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100256/
Test PASSed.

retest this please

Test build #100367 has started for PR 23301 at commit d9d3065.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/6330/
Test PASSed.


Audio media is not valid in Android

I have added custom sound for Android notification in res/res_sound.m4a but on initialize getting following exception and notification is not working:
me.carda.awesome_notifications.notifications.exceptions.AwesomeNotificationException: Audio media is not valid 	at me.carda.awesome_notifications.notifications.models.NotificationChannelModel.validate(NotificationChannelModel.java:286) 	at me.carda.awesome_notifications.notifications.managers.ChannelManager.saveChannel(ChannelManager.java:136) 	at me.carda.awesome_notifications.AwesomeNotificationsPlugin.setChannels(AwesomeNotificationsPlugin.java:1145) 	at me.carda.awesome_notifications.AwesomeNotificationsPlugin.setDefaultConfigurations(AwesomeNotificationsPlugin.java:1088) 	at me.carda.awesome_notifications.AwesomeNotificationsPlugin.channelMethodInitialize(AwesomeNotificationsPlugin.java:1070) 	at me.carda.awesome_notifications.AwesomeNotificationsPlugin.onMethodCall(AwesomeNotificationsPlugin.java:438) 	at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(MethodChannel.java:262) 	at io.flutter.embedding.engine.dart.DartMessenger.invokeHandler(DartMessenger.java:296) 	at io.flutter.embedding.engine.dart.DartMessenger.lambda$dispatchMessageToQueue$0$DartMessenger(DartMessenger.java:320) 	at io.flutter.embedding.engine.dart.-$$Lambda$DartMessenger$TsixYUB5E6FpKhMtCSQVHKE89gQ.run(lambda) 	at android.os.Handler.handleCallback(Handler.java:751) 	at android.os.Handler.dispatchMessage(Handler.java:95) 	at android.os.Looper.loop(Looper.java:154) 	at android.app.ActivityThread.main(ActivityThread.java:6077) 	at java.lang.reflect.Method.invoke(Native Method) 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:866) 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:756)
Initialized notification channel as follows:
NotificationChannel(         channelKey: 'android_sound_channel',         channelName: 'Android Custom Sound Notifications',         channelDescription: 'Notification channel for Android Custom Sound',         playSound: true,         soundSource: 'resource://raw/res_sound',         defaultColor: Colors.green,         ledColor: Colors.white,         importance: NotificationImportance.Max, ),
Note: I have converted the sound from mp3 to m4a and it's working fine in macOS with iTunes and other players.

I copy over the customer sound file to the android emulator and it plays without any issue.

I have an example app that uses all awesome notifications features, including custom sounds. Tou can try to run it or take a look on how i did it.
And you need to remember that, for Android 8+, the sound is defined by notification channels and, once defined, it cannot be changed anymore.

@rafaelsetragni Actually, the issue was because of the iOS sound source. I am using the different channels for iOS and Android.

@maksumon
hello
How did you solve the problem?


Allow configuring multiple-versions lint level on per-crate basis

Is your feature request related to a problem? Please describe.
Sometimes, it is desireable to enforce certain (usually direct) dependencies are not in the dependency graph another time, while at the same time it is pretty much impossible to enforce that every crate is only present once in the depgraph.
Describe the solution you'd like
Allow banning multiple versions of specific crates (in addition to being able to set the lint level for any crate being in the depgraph multiple times).

So you are wanting to opt in to detecting multiple versions of the same crate, rather than needing to mark one or more duplicates via the skip section?
Can you maybe give an anecdotal scenario or example configuration so I can understand what you want more clearly, because right now the change in my head would lead to either duplicates creeping in over time, or possibly needing to make multiple configuration changes for each duplicate crate.

Yes. I think this can be useful when a certain dependency is rather heavy, for example tokio. You might not want to enforce "no duplicate crates" for the whole project since maintaining that with a large depgraph is a decent bit of extra work and having small dependencies duplicated doesn't usually hurt much (e.g. different versions of macro-rules crates like matches or pin-project-lite), but having multiple versions of one of those heavy dependencies is a problem and should be prevented.

Yep, I want this to deny having multiple versions of rustix, which is equivalent in complexity to a C library.
I may try implementing this if there's consensus.  What should the syntax look like?  Perhaps:
[[bans.deny]]
name = "rustix"
multiple-versions = "deny"


Build lib/make.sh with python3 env. failed

Hi Jianwei, I've tried to build this project in conda venv with python3 and cuda 9.0. But encountered compile failure while running lib/make.sh.
More build details: https://github.com/clement10601/faster-rcnn.pytorch
Env:

OS: Archlinux (4.14.8)
x86_64-conda_cos6-linux-gnu-cc: gcc version 7.2.0 (Thread model: posix)
nvcc: release 9.0, V9.0.176
Graphic card: Tesla k20m

Env var:

CPATH=/opt/cuda/include
CUDA_PATH=/opt/cuda/

Traceback
/home/kchwang/miniconda3/envs/frcnn3/bin/x86_64-conda_cos6-linux-gnu-cc -DNDEBUG -fwrapv -O2 -Wall -Wstrict-prototypes -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2 -pipe -DNDEBUG -D_FORTIFY_SOURCE=2 -O2 -fPIC -DWITH_CUDA -I/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include -I/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH -I/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/THC -I/home/kchwang/miniconda3/envs/frcnn3/include/python3.6m -c _roi_crop.c -o ./_roi_crop.o
In file included from /home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/THC/THC.h:4:0,
                 from _roi_crop.c:493:
/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/THC/THCGeneral.h:9:10: fatal error: cuda.h: No such file or directory
 #include "cuda.h"
          ^~~~~~~~
compilation terminated.
Traceback (most recent call last):
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/distutils/unixccompiler.py", line 118, in _compile
    extra_postargs)
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/distutils/ccompiler.py", line 909, in spawn
    spawn(cmd, dry_run=self.dry_run)
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/distutils/spawn.py", line 36, in spawn
    _spawn_posix(cmd, search_path, dry_run=dry_run)
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/distutils/spawn.py", line 159, in _spawn_posix
    % (cmd, exit_status))
distutils.errors.DistutilsExecError: command '/home/kchwang/miniconda3/envs/frcnn3/bin/x86_64-conda_cos6-linux-gnu-cc' failed with exit status 1

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/site-packages/cffi/ffiplatform.py", line 51, in _build
    dist.run_command('build_ext')
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/distutils/command/build_ext.py", line 339, in run
    self.build_extensions()
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/distutils/command/build_ext.py", line 448, in build_extensions
    self._build_extensions_serial()
    1 #!/usr/bin/env bash
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/distutils/command/build_ext.py", line 473, in _build_extensions_serial
    self.build_extension(ext)
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/distutils/command/build_ext.py", line 533, in build_extension
    depends=ext.depends)
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/distutils/ccompiler.py", line 574, in compile
    self._compile(obj, src, ext, cc_args, extra_postargs, pp_opts)
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/distutils/unixccompiler.py", line 120, in _compile
    raise CompileError(msg)
distutils.errors.CompileError: command '/home/kchwang/miniconda3/envs/frcnn3/bin/x86_64-conda_cos6-linux-gnu-cc' failed with exit status 1

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "build.py", line 36, in <module>
    ffi.build()
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/site-packages/torch/utils/ffi/__init__.py", line 167, in build
    _build_extension(ffi, cffi_wrapper_name, target_dir, verbose)
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/site-packages/torch/utils/ffi/__init__.py", line 103, in _build_extension
    ffi.compile(tmpdir=tmpdir, verbose=verbose, target=libname)
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/site-packages/cffi/api.py", line 690, in compile
    compiler_verbose=verbose, debug=debug, **kwds)
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/site-packages/cffi/recompiler.py", line 1515, in recompile
    compiler_verbose, debug)
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/site-packages/cffi/ffiplatform.py", line 22, in compile
    outputfilename = _build(tmpdir, ext, compiler_verbose, debug)
  File "/home/kchwang/miniconda3/envs/frcnn3/lib/python3.6/site-packages/cffi/ffiplatform.py", line 58, in _build
    raise VerificationError('%s: %s' % (e.__class__.__name__, e))
cffi.error.VerificationError: CompileError: command '/home/kchwang/miniconda3/envs/frcnn3/bin/x86_64-conda_cos6-linux-gnu-cc' failed with exit status 1

I come up with a similar error, but the solutions above cannot solve this problem.
`/home/yongyi/anaconda3/compiler_compat/ld: cannot find -lpthread
/home/yongyi/anaconda3/compiler_compat/ld: cannot find -lc
collect2: error: ld returned 1 exit status
Traceback (most recent call last):
File "/home/yongyi/anaconda3/lib/python3.6/distutils/unixccompiler.py", line 197, in link
self.spawn(linker + ld_args)
File "/home/yongyi/anaconda3/lib/python3.6/distutils/ccompiler.py", line 909, in spawn
spawn(cmd, dry_run=self.dry_run)
File "/home/yongyi/anaconda3/lib/python3.6/distutils/spawn.py", line 36, in spawn
_spawn_posix(cmd, search_path, dry_run=dry_run)
File "/home/yongyi/anaconda3/lib/python3.6/distutils/spawn.py", line 159, in _spawn_posix
% (cmd, exit_status))
distutils.errors.DistutilsExecError: command 'gcc' failed with exit status 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/yongyi/anaconda3/lib/python3.6/site-packages/cffi/ffiplatform.py", line 49, in _build
dist.run_command('build_ext')
File "/home/yongyi/anaconda3/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/yongyi/anaconda3/lib/python3.6/distutils/command/build_ext.py", line 339, in run
self.build_extensions()
File "/home/yongyi/anaconda3/lib/python3.6/distutils/command/build_ext.py", line 448, in build_extensions
self._build_extensions_serial()
File "/home/yongyi/anaconda3/lib/python3.6/distutils/command/build_ext.py", line 473, in _build_extensions_serial
self.build_extension(ext)
File "/home/yongyi/anaconda3/lib/python3.6/distutils/command/build_ext.py", line 558, in build_extension
target_lang=language)
File "/home/yongyi/anaconda3/lib/python3.6/distutils/ccompiler.py", line 717, in link_shared_object
extra_preargs, extra_postargs, build_temp, target_lang)
File "/home/yongyi/anaconda3/lib/python3.6/distutils/unixccompiler.py", line 199, in link
raise LinkError(msg)
distutils.errors.LinkError: command 'gcc' failed with exit status 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "build.py", line 35, in
ffi.build()
File "/home/yongyi/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/init.py", line 167, in build
_build_extension(ffi, cffi_wrapper_name, target_dir, verbose)
File "/home/yongyi/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/init.py", line 103, in _build_extension
ffi.compile(tmpdir=tmpdir, verbose=verbose, target=libname)
File "/home/yongyi/anaconda3/lib/python3.6/site-packages/cffi/api.py", line 684, in compile
compiler_verbose=verbose, debug=debug, **kwds)
File "/home/yongyi/anaconda3/lib/python3.6/site-packages/cffi/recompiler.py", line 1484, in recompile
compiler_verbose, debug)
File "/home/yongyi/anaconda3/lib/python3.6/site-packages/cffi/ffiplatform.py", line 20, in compile
outputfilename = _build(tmpdir, ext, compiler_verbose, debug)
File "/home/yongyi/anaconda3/lib/python3.6/site-packages/cffi/ffiplatform.py", line 56, in _build
raise VerificationError('%s: %s' % (e.class.name, e))
cffi.error.VerificationError: LinkError: command 'gcc' failed with exit status 1`

@YongyiTang92  I got the same problem, have you solved it

@ShoufaChen
Test "compile one" first:
cd model/nms/src
echo "Compiling nms kernels by nvcc..."
nvcc -c -o nms_cuda_kernel.cu.o nms_cuda_kernel.cu -x cu -Xcompiler -fPIC -arch=sm_52
cd ../
python build.py

if it's compling correct~ you can change others like this. (Note: sm_xx depend to you gpu)


fix: dak.cartesian was not tracing properly, fix data touching, behaviors

@yimuchen if you take this PR you should be able to continue with your tests.

Original symptoms were:
function call on just metas failed

and then the resulting arrays were stripped of their behaviors... I'll add a fix to the length_zero_array() fallback as well.

@agoose77 The problem with the data touching here was a bit interesting. In the nested form of cartesian if I asked for the unzipped components of the cartesian ["0"] or ["1"] then instead of needing to get the required data from both parts of the nested object since that defines the shape of the array it would only get the data related to that particular subarray and the calculation would fail since it couldn't do the original cartesian.
With touching all typetracers before calling the cartesian it works fine.

I'm aware of some typetracer problems with the cartesian function here: https://github.com/scikit-hep/awkward/pull/2295/
I'm not sure if it's related to this one, though. (adds to pile!)

Codecov Report

Merging #189 (70f776d) into main (0060a1f) will increase coverage by 0.01%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #189      +/-   ##
==========================================
+ Coverage   94.49%   94.51%   +0.01%
==========================================
  Files          19       19
  Lines        2018     2022       +4
==========================================
+ Hits         1907     1911       +4
  Misses        111      111

Impacted Files
Coverage Δ

src/dask_awkward/lib/core.py
90.53% <100.00%> (ø)

src/dask_awkward/lib/structure.py
95.44% <100.00%> (+0.05%)
:arrow_up:

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


Refactor design of Queues wizard page

Description
This PR refactors the design of Queues wizard page. Now each queue has its own dedicated container, and compute resources are not wrapped in an additional container.
Furthemore:

Add queue button has been moved to the top-right part of the container
Compute resources names are now displayed in the wizard
Added Queue name validation

How Has This Been Tested?

Manual tests on local environment
Unit tests

References

https://cloudscape.design/components/column-layout/

Screenshots

PR Quality Checklist

[x] I added tests to new or existing code
[x] I removed hardcoded strings and used react-i18next library (useTranslation hook and/or Trans component), see an example here
[ ] I made sure no sensitive info gets logged at any time in the codebase (see here) (e.g. no user info or details, no stacktraces, etc.)
[ ] I checked that infrastructure/update_infrastructure.sh runs without any error
[x] I checked that npm run build builds without any error
[x] I checked that clusters are listed correctly
[x] I checked that a new cluster can be created (config is produced and dry run passes)
[ ] I checked that login and logout work as expected

In order to increase the likelihood of your contribution being accepted, please make sure you have read both the Contributing Guidelines and the Project Guidelines
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

General remark: how is this PR going to affect the e2e tests?

General remark: how is this PR going to affect the e2e tests?

Should not affect e2e since in the Queue page the only element we look for is the heading, which is untouched. Tested locally, it works.


Use of mime_content_type breaks on some systems

In services/EmbeddedAssetsService.php, mime_content_type() is used.
However, this function comes from a deprecated library and doesn't exist at all in some vendor builds of PHP 5.3+. This makes any attempt to upload an embedded asset fail silently on these systems, because mime_content_type() is undefined.

Hey thanks for the report. The PHP docs don't directly say anything about the deprecation of mime_content_type on that functions page so I never knew. Thanks for the heads up, it's fixed now!


Update Schema Compare dialog to start a new connection

This PR fixes #5222. With the new changes, Schema Compare dialog will present an extra connection button from where new connections can be added (and will show up in the dropdown of the server list).

Pull Request Test Coverage Report for Build 786426605

13 of 34 (38.24%)  changed or added relevant lines in 3 files are covered.
487 unchanged lines in 11 files lost coverage.
Overall coverage decreased (-0.03%) to 43.576%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/schema-compare/src/dialogs/schemaCompareDialog.ts
10
31
32.26%

Files with Coverage Reduction
New Missed Lines
%

src/sql/base/common/dataProvider.ts
2
14.29%

extensions/schema-compare/src/dialogs/schemaCompareDialog.ts
5
49.87%

src/sql/workbench/contrib/notebook/browser/notebookEditor.ts
7
91.81%

src/sql/base/browser/ui/table/hybridDataProvider.ts
13
1.75%

src/sql/workbench/contrib/notebook/browser/find/notebookFindModel.ts
15
33.74%

src/sql/workbench/contrib/notebook/browser/cellViews/textCell.component.ts
20
3.27%

src/sql/base/browser/ui/table/tableDataView.ts
23
47.16%

src/sql/base/parts/editableDropdown/browser/dropdown.ts
46
49.55%

src/sql/workbench/contrib/notebook/browser/cellViews/markdownToolbar.component.ts
54
1.81%

src/sql/workbench/api/common/extHostDataProtocol.ts
148
12.72%

Totals

Change from base Build 765140852:
-0.03%

Covered Lines:
26270

Relevant Lines:
55067

💛  - Coveralls

Seems like the PR build is failing for this PR - please take a look before checkin

Seems like the PR build is failing for this PR - please take a look before checkin

The validation failure is related to "Component Governance" issue, not specific to this PR.
All the tests are passing as well.


Package.resolved pin keeps changing

Hi, I noticed that the record for AWSiOSSDKV2 keeps changing. I'm trying to figure out if the change is caused by different xcode 13 versions, but basically, jenkins nodes tend to remove it when building

And dev machines try to add it back

Builds keep failing due to git being dirty.
One info that might be useful is that I'm using https://github.com/awslabs/aws-mobile-appsync-sdk-ios on local swift package module.

Thanks for opening this issue @gevartosky. We'll take a look at this and get back to you.

It seems that this is a general Xcode / SPM issue that can occur when your app depends on the same dependency through multiple channels; either direct + transitively, or multiple transitive. In that case, if the URLs aren't identical, this issue can happen. So if one has .git and the other doesn't or if one uses SSH and the other HTTPS.
flowchart LR
App --> FooKit
App -->|https://github.com/foo/bar| BarKit
FooKit -->|https://github.com/foo/bar.git| BarKit

flowchart LR
App --> FooKit
App --> BarKit
FooKit -->|https://github.com/foo/baz| BazKit
BarKit -->|https://github.com/foo/baz.git| BazKit

Based on your info about using AWSAppSync, I believe that may be the case here.
If you're depending on AWS SDK iOS either directly or through another dependency (Amplify for example), can you check that the URLs in the applicable Package.swift files are identical?
Please let us know whether this fixes your issue or not. Thanks!

Thanks for the detailed answer @atierian. I noticed these days that our devs were using different versions of xcode. I asked everyone to update xcode 13.3 and the issue stopped

Great! I'm going to close this issue now then.


Enemy collision

Added player with enemy collision. Also changed input system to a vector system with friction and gravity. Jump also works. Enemy is 1 stationary object. Moved all collision related functions to entity.c

merged in heavydemon21's pr


chore(ci): use GHA with shared workflows

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@2a5fd2d). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #32   +/-   ##
=========================================
  Coverage          ?   92.87%
=========================================
  Files             ?       33
  Lines             ?     3511
  Branches          ?        0
=========================================
  Hits              ?     3261
  Misses            ?      250
  Partials          ?        0

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 2a5fd2d...21e97dd. Read the comment docs.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@2a5fd2d). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #32   +/-   ##
=========================================
  Coverage          ?   92.87%
=========================================
  Files             ?       33
  Lines             ?     3511
  Branches          ?        0
=========================================
  Hits              ?     3261
  Misses            ?      250
  Partials          ?        0

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 2a5fd2d...c9d9340. Read the comment docs.


Jobs: adjust swift module wrapping job (NFC)

With -emit-module, the output type computed is the swiftmodule. This output is subsequently wrapped by the module wrap job which will embed the swift module into an object file. This would trigger the assertion previously. Clean up some of the planning code associated with this in tandem.

@swift-ci please test


Component: Flow/deployment card

Card should contain at least all the data a row in the FlowsTable and a given flow's DeploymentsTable would have

https://www.figma.com/file/WQwcuqBAxug8JqLigWaztu/Designs?node-id=4202-31079&t=Ir707uJDqtq2J9nL-0

Resolved by #1346


Fix safe checker error handling to return the currently verified env

This allow printing errors in the right (verified) environement, which is much better for debugging...

Cool! It's my fault, I didn't know how to get the proper environment. :)


Is this config tested on macos?

No, since I only use linux. It should work on windows since I initially started off on there but I've never used macos. It's probably worth clarifying these aren't dotfiles I really expect anyone else to use. More often than not their probably broken since I keep a lot of new commits on my local machine before pushing. I've been meaning to setup a test-suite but I install so many packages that I didn't want to spam MELPA whenever I update my dotfiles.

I get

Is the output you're sharing from emacs? Could you run with --debug-init and share the resulting stack-trace. The first few errors seem to be because of a macro that isn't defined but I'm not getting that error so I can't reproduce.
It'd probably be helpful if you zipped up your .emacs.d? Although yours seems to have tangled into ~/.emacs instead which isn't possible with my configuration.

I was curious about the all-the-icons and nerd-fonts in tty related code, since I am trying to fix messed up icons in my tty emacs config in dired (all-the-icons-dired).
Tried to lift the relevant sections from init.org, into my config, no errors. However, the icons in dired mode are messed up.
Thus cloned your config to test if the icons related code works in your config in macos.

@srustamo

Tried to lift the relevant sections from init.org, into my config, no errors. However, the icons in dired mode are messed up.

Share a screenshot please.

The screenshot is a part of the tty screen running emacs, showing dired buffer.

@srustamo
Looks like some glyphs are missing (the rhombus with a question mark) and others aren't beeing associated properly (the suitcase). In my terminal I've got multiple fonts setup including all the all-the-icons fonts; when emacs draws one it checks each font for a matching glyph in turn falling back to the next. I'm not sure whether iterm supports this but you should try to do so as well.
As for your other issues I don't convert every all-the-icon glyph to its equivalent nerd font. I really only do this for glyphs as I encounter them (which you can see in the config I shared before). For example ((all-the-icons-alltheicon . "c-line") . (all-the-icons-nerd-custom . "c")) converts any references to c-line with alltheicon fonts to c with nerd-custom font. Annoyingly some parts of all the icons hardcodes references to icons into functions for example the suitcase icon being used for symlinks and the only way to fix that is with advice (but it's too big a job for me to bother).
When in doubt you can run all-the-icons-insert to determine which icon is being inserted where and maybe see alternatives for it.

Looks like I need to read up on the font rendering in tty. Any suggested resources?
iTerm2 has only this option for non-ASCII fonts:

Tried many fonts - blindly - not much luck. This all-the-icons issue tracker issue says iTerm can set one non-ASCII font.
The all-the-icons readme has a troubleshooting section. The first step, running (all-the-icons-insert-icons-for 'alltheicon) shows the correct icons, other commands show question marks in rhombuses.

(all-the-icons-insert-icons-for 'octicon 10)

Sorry for just dumping my observations here, perhaps you can point me to the right direction.

@srustamo
Well my normal response would be to stop using iterm. Frankly this is the same reason I stopped using alacritty. Although I'm aware macos doesn't have as many alternatives and iterm2 seems to be more than just a terminal emulator, it also supports window oriented multiplexing which is quite cool. That said you might want to try kitty if you're looking for a feature-full cross platform terminal emulator.
The alternative would be to patch your own font. It might be a little involved but you can combine each of the fonts used by all-the-icons arranging the overlapping glyphs in the order you want. Not ideal but it should work. You may also want to include nerd-fonts or just use it as your main font since iterm appears to let you select a ascii and unicode font independently.

Indeed, I tried alacritty, which also doesn't support fontsets.
kitty's readme says it supports multiple fonts, so far I only saw separate font definitions for Regular, Italic etc, and font maps for specific ASCII codes, which seems something I need to explore more.
Many thanks for your tips.

You don't use Evil mode in emacs tty, do you? If you do, how do you manage Ctrl-I (vim's jump forward) and TAB, which is normally not differentiated from Ctrl-I in ttys?

@srustamo
I do use evil in the terminal. See here. I ended up just remapping some of the terminal specific bindings into custom keys (eg: [C-i]) which I bind separate to "TAB"/"C-i" (which emacs internally stores as a literal tab character \t). For something a little less manual you may want to try term-keys.


A quick question (efficient method for copying components in gridfunctions?)

Hello everyone,
I have a quick question.
I'd like to copy a specific component in a grid function.
For example, let's say grid function A has a vector length of 10, and grid function B has a vector length of 30 (three components). Currently, I've been using a for loop to copy the third component element by element, but I feel like this is not an efficient approach.
Is there a more efficient way to do this?
Thanks,
Sungho

@pazner I understand, thank you for your comment. There is a method using projection for grid functions, but it also necessitates preparing the appropriate number of projection classes corresponding to the number of components I want to handle. Therefore, it still presents an inefficiency. Anyhow, thanks again.


Warning: Prop className did not match. with next js and strictmode

Current Behavior 😯
If i add strict mode to next.config i get this warning: Prop className did not match. Server etc.
This leads to the fact that the styles on my site do not work.
Expected Behavior 🤔
Fix this warn
Steps to Reproduce 🕹
Please see the console
https://codesandbox.io/s/weathered-bush-pp3so?file=/pages/index.js

Duplicate of https://github.com/mui-org/material-ui/issues/26595

Hi @mnajdova! I don't think this is a duplicate because the problem came from using strict mode in nextjs. This link doesn't match my problem and these solutions don't help me


Spring vendor fixes

Fixes Issue #3494
Description of Change
Fix JarAnalyzer to make existing base-hints match
Add base-hint to make gradle plugin match for Spring-projects that use gradle for the build
Update suppressions to avoid false positives with the improved vendor-assignment for Spring.io binaries
Fix an erroneous base-hint (Spring-security is not part of Spring-framework)
Have test cases been added to cover the new functionality?
no

Appears to me that the 629-jackson-dataformat failure is a failure that should've occurred for all PRs since 20 Jan 2021 as per the NIST NVD modification Modified Analysis 1/19/2021 10:41:56 AM
CVE-2018-1000873 changed from cpe:2.3:a:fasterxml:jackson-databind to cpe:2.3:a:fasterxml:jackson-modules-java8

Same holds for the 1512, which is using the same CVE for validation

Base hints contained a mixture of 'proper' full pom groupIds (that would be added as evidences by the MavenAnalyzer) and truncated pom groupIds (that would be added by the unmodified JarAnalyzer.
One of these was for jackson-core adding the java8 product as evidence which triggers the detection of CVE-2018-1000873 (as per the hint added in aa2ed52ec76a9c879cafc3d1fda790d094e437a2). Looking at the details that appears inappropriate, for which I'll file a separate issue to discuss it.
For this PR I'll put the appropriate com/org prefixes in the hints where they were left out to make them properly match again with the evidences gathered by Maven Plugin, Central-/Nexus- and Jar-Analyzer.

Build passes on my machine. We may need to disable the node audit analyzer tests for a more stable build - possibly setup a new set of integration tests specifically to cover when ODC calls out to 3rd party services.


Maya: Fix Look Maya 2020 Py2 support for Extract Look

Changelog Description
Fix Extract Look supporting python 2.7 for Maya 2020.
Additional info
attr dataclass must be new style class.
Testing notes:

Publish look from Maya 2020.

This will also need https://github.com/ynput/OpenPype/pull/4795 since it'll otherwise fail on extraction due to the colorspace logic.

Hi, I confirm that this change solved the lookdev publish problem for Maya 2020!


SHA jet fails

The following program fails at jet_sha_256_ctx_8_add_32. This is strange because SHA jets almost never fail, and the program type-checks.
sha256_init : 2^256 -> _
sha256_init := comp unit jet_sha_256_ctx_8_init

sha256 : 2^256 -> 2^256
sha256 := comp
    comp
        pair sha256_init iden
        jet_sha_256_ctx_8_add_32
    jet_sha_256_ctx_8_finalize

preimage := const 0x9dd01b56b15645143ead158dec19f8cea90bd0a9b2f81d21ffa3a4c64481d41c
image := const 0x0bcfe0e54e6cc7d34f4f7c1df0b0f503f2f712912a0605b414ed337f7f032e03

main := comp
    comp
        pair (comp preimage sha256) image
        jet_eq_256
    jet_verify

The program is taken from our post on sharing and disconnect (Consider the following program, which checks whether the user has found a SHA256 "fixed point")
The (pre)images are taken from a test vector from bitcoin-hashes.

You are missing
https://github.com/rust-bitcoin/rust-bitcoin/blob/53461f71c9cd6ed49acff61396758f53f8fa3de8/hashes/src/sha256.rs#L899-L900
from your program

@roconnor-blockstream Thanks for pointing this out. Updating the (pre)images fixes the program in rust-simplicity.
preimage := const 0x0000000000000000000000000000000000000000000000000000000000000000
image := const 0x66687aadf862bd776c8fc18b8e9f8e20089714856ee233b3902a591d0d5f2925

The webide (where this error originated) still returns an error, but this has likely to do with WASM or with the IDE itself.


Support multiple domains #101.

[x] domains/misc/badssl.com/index.html:

[x] The ---\n--- at the start are needed to get Jekyll to properly apply templating for the {{ site.domain }} tags.

[ ] Makefile:

[x] Reflects the current setting there into _config.yml.
[x]  Reflects the current setting there into various nginx related *.conf files.

That's a very good point about modifying a commited file, but consider this:

We will need to modify many other files to support subdomains (see a83d17f).
Any committer only need to set $SITE in the Makefile back to badssl.com

We will need to modify many other files to support subdomains (see a83d17f).

I wouldn't mind templatizing the nginx files.
Alternatively, is it possible to add a a few lines to nginx that say "if you get any requests for badssl.test, treat it is an alias for badssl.com?

Hmmm I'll explore the possibility of templating the nginx files with Jekyll perhaps...

@lgarron As per @marumari 's suggestion I had it modify files in _site produced by Jekyll.
I'm still not sure how to handle the _config.yml problem. Would you suggest setting it, building using jekyll, then unsetting it?

I'm still not sure how to handle the _config.yml problem. Would you suggest setting it, building using jekyll, then unsetting it?

I would actually prefer to build everything with jekyll and then dropping the static output in the _site folder. Including the nginx files and _config.yml.

@lgarron Right, what I'm saying is if we don't modify _config.yml before building, then badssl.com will be used still instead of the correct domain from the Makefile. So if we modify it, have jekyll build everything, then modify it back then we won't actually be changing a commited file for anything more than the build process.

Hmm, I see. But I'd still prefer to avoid a fragile build process. Can jekyll set a site variable based on a commandline/environment variable?

@lgarron Yeah looks like we can if we use a plugin! :) Should work.

Excellent, thanks!
I've started work on updating the nginx files to use jekyll variables and eliminating as many hard-coded badssl.com references as possible: https://github.com/lgarron/badssl.com/commit/template
(Also a big TODO: figuring out what to do with the cert generator.)
I don't have time to continue it right now, but feel free to take it from there.

Oh wow, you can template conf files! I apprently didn't get the secret sauce working. I'll take it from here, thanks.

I apprently didn't get the secret sauce working

Neither did I, until I saw your comment above:

The ---\n--- at the start are needed to get Jekyll to properly apply templating for the {{ site.domain }} tags.

;-)

At least you learn from me, i sure don't!

@lgarron This should be ready for review, I've tried to split up the commits so it's easier to review piece by piece.


Adapt to new neo4j-admin commands layout

Hi @jennyowen please ping me when you will be up to review this one. It comes with a story :)


Drop Python 3.7 support

Python 3.7 has reached its end-of-life (EOL) as of June 2023.

Codecov Report
Patch and project coverage have no change.

Comparison is base (c91201f) 77.87% compared to head (700a821) 77.87%.

: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           @@
##             main     #559   +/-   ##
=======================================
  Coverage   77.87%   77.87%
=======================================
  Files          15       15
  Lines        1279     1279
=======================================
  Hits          996      996
  Misses        283      283

Flag
Coverage Δ

unit
77.87% <ø> (ø)

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

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


[TwitScoopBridge] Add bridge

Adds bridge for TwitScoop. Returns trending Twitter topics by country.
Closes #2017

for "Russia" filter it returns message:
Bad Request: can't parse entities: Unsupported start tag "10k" at byte offset 26

for "Russia" filter it returns message:
Bad Request: can't parse entities: Unsupported start tag "10k" at byte offset 26

Where is this error return? by your RSS reader or by rss-bridge.

for "Russia" filter it returns message:
Bad Request: can't parse entities: Unsupported start tag "10k" at byte offset 26

Where is this error return? by your RSS reader or by rss-bridge.
Edit: This should be fixed by #2023.

https://premium.thefeedreaderbot.com/

@travstrat , I have merged the @VerifiedJoseph's fix of that. Please confirm, that it works.

unfortunately it still appear when adding to premium.thefeedreaderbot.com for Russia filter (USA works)
Message shown when click to "send test message":
"Bad Request: can't parse entities: Unsupported start tag "10k" at byte offset 41"


Fix ServiceMonitor

we can't release it to OCP yet, needs some more coordination
we also can't release to the community version, because of GDPR regulations, and deployment failure if Prometheus isn't installed
you can easily build your own version containing the ServiceMonitor with the new container-build-metrics Make target
fixed label selector by adding the app.kubernetes.io/name: node-healthcheck-operator label

/lgtm

OCP tests are on hold I will try retrigger them..
/retest


Fix links in the README.md

Thanks for wasm-pack!
There's a bunch of links pointing to non-existent documents.
This PR compliments #246 and addresses what has not been addressed in #254, which removes some of the duplications in the documentation.

[ ] (not relevant) You have the latest version of rustfmt installed and have your
cloned directory set to nightly
[ ] (not relevant) You ran rustfmt on the code base before submitting
[x] You reference which issue is being closed in the PR text

Closes #253

Thanks! Going to merge this now, so that we don't have broken links until the mdbook lands.


problem

Description
What steps will reproduce the problem?

What is the expected output? What do you see instead?
Please provide any additional information below
File "C:\Anaconda2\envs\tensorflow\lib\site-packages\spyder_profiler\widgets\profilergui.py", line 261, in
self.finished(ec, es))
File "C:\Anaconda2\envs\tensorflow\lib\site-packages\spyder_profiler\widgets\profilergui.py", line 326, in finished
self.show_data(justanalyzed=True)
File "C:\Anaconda2\envs\tensorflow\lib\site-packages\spyder_profiler\widgets\profilergui.py", line 347, in show_data
self.datatree.load_data(self.DATAPATH)
File "C:\Anaconda2\envs\tensorflow\lib\site-packages\spyder_profiler\widgets\profilergui.py", line 459, in load_data
stats_indi = [pstats.Stats(profdatafile),]
File "C:\Anaconda2\envs\tensorflow\lib\pstats.py", line 72, in init
self.init(arg)
File "C:\Anaconda2\envs\tensorflow\lib\pstats.py", line 86, in init
self.load_stats(arg)
File "C:\Anaconda2\envs\tensorflow\lib\pstats.py", line 99, in load_stats
with open(arg, 'rb') as f:
FileNotFoundError: [Errno 2] No such file or directory: 'C:\Users\wuyi\.spyder-py3\profiler.results'
Version and main components

Spyder Version: 3.2.3
Python Version: 3.6.2
Qt Versions: 5.6.2, PyQt5 5.6 on Windows

Dependencies
pyflakes >

Thanks for reporting. This is a duplicate of issue #5107.
In the meantime, you can open a terminal (cmd.exe) and run
spyder --reset

to fix this.


Assertion messages

Here is the article about several suggestions related to good practices that could be applied for Java tests.
The one of the suggestions is "Assertion messages".  We have to check that all assertions have messages:
assertThat(
    "Total count of greetings",
    p.greetings().count(), equalTo(1)
);

or
MatcherAssert.assertThat(
    "Has different hash codes",
    new JavaParserCase(clazz, name, path).hashCode(),
    Matchers.is(new JavaParserCase(clazz, name, path).hashCode())
);

The next code would be wrong:
assertThat(
    p.greetings().count(), equalTo(1)
);

or
MatcherAssert.assertThat(
    new JavaParserCase(clazz, name, path).hashCode(),
    Matchers.is(new JavaParserCase(clazz, name, path).hashCode())
);

@volodya-lombrozo 2 puzzles #145, #146 are still not solved.

@volodya-lombrozo 4 puzzles #145, #146, #151, #152 are still not solved; solved: #149.

@volodya-lombrozo 4 puzzles #145, #146, #151, #155 are still not solved; solved: #149, #152.

@volodya-lombrozo 4 puzzles #145, #146, #151, #157 are still not solved; solved: #149, #152, #155.

@volodya-lombrozo 5 puzzles #145, #146, #151, #160, #161 are still not solved; solved: #149, #152, #155, #157.

@volodya-lombrozo 6 puzzles #145, #146, #151, #161, #164, #166 are still not solved; solved: #149, #152, #155, #157, #160, #165.

@volodya-lombrozo 5 puzzles #145, #146, #151, #161, #164 are still not solved; solved: #149, #152, #155, #157, #160, #165, #166.

@volodya-lombrozo 5 puzzles #145, #146, #151, #161, #171 are still not solved; solved: #149, #152, #155, #157, #160, #164, #165, #166, #170, #173.

@volodya-lombrozo 4 puzzles #145, #146, #151, #171 are still not solved; solved: #149, #152, #155, #157, #160, #161, #164, #165, #166, #170, #173.

@volodya-lombrozo 2 puzzles #146, #151 are still not solved; solved: #145, #149, #152, #155, #157, #160, #161, #164, #165, #166, #170, #171, #173.

@volodya-lombrozo the puzzle #151 is still not solved; solved: #145, #146, #149, #152, #155, #157, #160, #161, #164, #165, #166, #170, #171, #173.


[backport] Fix dataset path to support Windows

Backport of #5100

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 1c1b8121d83a8983d75302893724053415b81d3b) succeeded without errors!

LGTM!

Jenkins CI test (for commit 1c1b8121d83a8983d75302893724053415b81d3b) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)


Populate licenses on replacements

When using a library such as protocol buffers, it is common to do something like:
In workspace:
http_archive(
    name = "com_google_protobuf",
    sha256 = "cef7f1b5a7c5fba672bec2a319246e8feba471f04dcebfe362d55930ee7c1c30",
    strip_prefix = "protobuf-3.5.0",
    urls = ["https://github.com/google/protobuf/archive/v3.5.0.zip"],
)

Elsewhere, the deps then need to use @com_google_protobuf//:protobuf_java. To ensure that any JARs retrieved from Maven use the same version, it makes sense to add something like this to dependencies.yaml:
replacements:
  com.google.protobuf:
    protobuf-java:
      lang: java
      target: "@com_google_protobuf//:protobuf_java"

This works, however it seems awkward that within my project I must use @com_google_protobuf//:protobuf_java when there is a file at //3rdparty/com/google/protobuf:protobuf-java that is perfectly useable, except it doesn't have the appropriate licenses to be usable. Could the BUILD file entries generated for replacements support the same licenses setting?

Maybe -- I'm not familiar with Scala, but can probably stumble through if you can point out roughly what needs to change.

I think I figured out what to change, but I wasn't able to find any tests that were verifying the generated results included the license -- I wasn't sure how to test this change other than using it and verifying it works (which I did).


Support installers that always reboot by warning user / requiring an opt-in flag

Description of the new feature / enhancement
Some installers will always reboot, regardless of what we ask of them.  We can support these by having the data in the manifest to indicate it, then warning the user and possibly requiring an opt-in flag on the command line.
Proposed technical implementation details
Add a field to the manifest to indicate a forced reboot from installation.
Warn (aka error) the user if they try to install
Only proceed if a new option is passed in: --allow-reboot or similar

Could be similar to:

#1786


Cross-Compile: X1 (arm64) & ppc64le

macOS: no arm64 ("X1") native runners yet
Linux: native runners on Travis CI are out of credits

Checklist

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

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Ah too early, need to add macOS arm64/X1 support to openPMD-api's feedstock first.


Add SortApplicantParserTest

Codecov Report

Merging #309 (da0c6bf) into master (ad70c7c) will increase coverage by 0.51%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #309      +/-   ##
============================================
+ Coverage     73.07%   73.58%   +0.51%
- Complexity      868      873       +5
============================================
  Files           131      131
  Lines          2915     2915
  Branches        383      383
============================================
+ Hits           2130     2145      +15
+ Misses          647      632      -15
  Partials        138      138

Impacted Files
Coverage Δ

...in/java/seedu/address/logic/parser/ParserUtil.java
87.20% <0.00%> (+4.00%)
:arrow_up:

...ss/logic/parser/applicant/SortApplicantParser.java
100.00% <0.00%> (+100.00%)
: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 ad70c7c...da0c6bf. Read the comment docs.


Cross-compile to Aarch64

Closing as the ARM64 arch. is already in the build list and is producing a binary executable for that platform/arch.


pgbench: error: connection to server at "<IP_ADDRESS>", port 5432 failed

Steps to reproduce
kubectl apply -f vm-deploy.yaml

Running pgbench
VM_NAME=postgres14-disk-test scripts/run-bench.sh

Expected result
Get the pressure test results.
Actual result
I found that postgresql could not be connected, which caused the pressure test to fail.
$ VM_NAME=postgres14-disk-test scripts/run-bench.sh
If you don't see a command prompt, try pressing enter.
fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/community/x86_64/APKINDEX.tar.gz
(1/8) Installing postgresql-common (1.2-r0)
Executing postgresql-common-1.2-r0.pre-install
(2/8) Installing lz4-libs (1.9.4-r4)
(3/8) Installing libpq (15.3-r0)
(4/8) Installing ncurses-terminfo-base (6.4_p20230506-r0)
(5/8) Installing libncursesw (6.4_p20230506-r0)
(6/8) Installing readline (8.2.1-r1)
(7/8) Installing zstd-libs (1.5.5-r4)
(8/8) Installing postgresql15-client (15.3-r0)
Executing busybox-1.36.1-r0.trigger
Executing postgresql-common-1.2-r0.trigger
* Setting postgresql15 as the default version
OK: 12 MiB in 23 packages
Running pgbench. Query:
   select length(factorial(length(factorial(1223)::text)/2)::text);
pgbench: error: connection to server at "<IP_ADDRESS>", port 5432 failed: Host is unreachable
        Is the server running on that host and accepting TCP/IP connections?
pgbench: error: could not create connection for setup
pod "pgbench-postgres14-disk-test" deleted
pod default/pgbench-postgres14-disk-test terminated (Error)

Environment
autoscaling: v0.11.0
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.17", GitCommit:"953be8927218ec8067e1af2641e540238ffd7576", GitTreeState:"clean", BuildDate:"2023-02-22T13:34:27Z", GoVersion:"go1.19.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.11", GitCommit:"8cfcba0b15c343a8dc48567a74c29ec4844e0b9e", GitTreeState:"clean", BuildDate:"2023-06-15T00:55:52Z", GoVersion:"go1.19.10", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.23) and server (1.25) exceeds the supported minor version skew of +/-1

Logs, links
pods
$ kubectl get pods --all-namespaces -o wide
NAMESPACE            NAME                                         READY   STATUS    RESTARTS   AGE     IP            NODE                 NOMINATED NODE   READINESS GATES
cert-manager         cert-manager-5b8f9b9d96-xjsx4                1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker          <none>           <none>
cert-manager         cert-manager-cainjector-54f68bfb64-8cq6d     1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker          <none>           <none>
cert-manager         cert-manager-webhook-f6c8487d6-rf9gg         1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker          <none>           <none>
default              postgres14-disk-test-ll7fg                   1/1     Running   0          8m53s   <IP_ADDRESS>   kind-worker          <none>           <none>
kube-system          autoscale-scheduler-59d466865c-mg9n4         1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker2         <none>           <none>
kube-system          autoscaler-agent-c2br7                       1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker          <none>           <none>
kube-system          autoscaler-agent-vvjnb                       1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker2         <none>           <none>
kube-system          coredns-565d847f94-sd86q                     1/1     Running   0          6d1h    <IP_ADDRESS>    kind-control-plane   <none>           <none>
kube-system          coredns-565d847f94-swwfk                     1/1     Running   0          6d1h    <IP_ADDRESS>    kind-control-plane   <none>           <none>
kube-system          etcd-kind-control-plane                      1/1     Running   0          6d1h    <IP_ADDRESS>    kind-control-plane   <none>           <none>
kube-system          kindnet-2dj4h                                1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker          <none>           <none>
kube-system          kindnet-cq6p6                                1/1     Running   0          6d1h    <IP_ADDRESS>    kind-control-plane   <none>           <none>
kube-system          kindnet-fqljc                                1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker2         <none>           <none>
kube-system          kube-apiserver-kind-control-plane            1/1     Running   0          6d1h    <IP_ADDRESS>    kind-control-plane   <none>           <none>
kube-system          kube-controller-manager-kind-control-plane   1/1     Running   0          6d1h    <IP_ADDRESS>    kind-control-plane   <none>           <none>
kube-system          kube-multus-ds-6bh7k                         1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker          <none>           <none>
kube-system          kube-multus-ds-drmlr                         1/1     Running   0          6d1h    <IP_ADDRESS>    kind-control-plane   <none>           <none>
kube-system          kube-multus-ds-rhg8m                         1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker2         <none>           <none>
kube-system          kube-proxy-647cj                             1/1     Running   0          6d1h    <IP_ADDRESS>    kind-control-plane   <none>           <none>
kube-system          kube-proxy-8wkrg                             1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker          <none>           <none>
kube-system          kube-proxy-ptz76                             1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker2         <none>           <none>
kube-system          kube-scheduler-kind-control-plane            1/1     Running   0          6d1h    <IP_ADDRESS>    kind-control-plane   <none>           <none>
kube-system          whereabouts-j2bdc                            1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker          <none>           <none>
kube-system          whereabouts-nzsq6                            1/1     Running   0          6d1h    <IP_ADDRESS>    kind-control-plane   <none>           <none>
kube-system          whereabouts-xfqnn                            1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker2         <none>           <none>
local-path-storage   local-path-provisioner-7cf55d6b5d-x6978      1/1     Running   0          6d1h    <IP_ADDRESS>    kind-control-plane   <none>           <none>
neonvm-system        neonvm-controller-7585bb456-4xmf5            2/2     Running   0          6d1h    <IP_ADDRESS>    kind-worker2         <none>           <none>
neonvm-system        neonvm-device-plugin-k2gxw                   1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker2         <none>           <none>
neonvm-system        neonvm-device-plugin-lzmsr                   1/1     Running   0          6d1h    <IP_ADDRESS>    kind-control-plane   <none>           <none>
neonvm-system        neonvm-device-plugin-rh26l                   1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker          <none>           <none>
neonvm-system        neonvm-vxlan-controller-dprrc                1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker2         <none>           <none>
neonvm-system        neonvm-vxlan-controller-ft5vx                1/1     Running   0          6d1h    <IP_ADDRESS>    kind-worker          <none>           <none>
neonvm-system        neonvm-vxlan-controller-ldc86                1/1     Running   0          6d1h    <IP_ADDRESS>    kind-control-plane   <none>           <none>

svc
$ kubectl get svc --all-namespaces -o wide
NAMESPACE       NAME                                TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                  AGE    SELECTOR
cert-manager    cert-manager                        ClusterIP   <IP_ADDRESS>   <none>        9402/TCP                 6d1h   app.kubernetes.io/component=controller,app.kubernetes.io/instance=cert-manager,app.kubernetes.io/name=cert-manager
cert-manager    cert-manager-webhook                ClusterIP   <IP_ADDRESS>    <none>        443/TCP                  6d1h   app.kubernetes.io/component=webhook,app.kubernetes.io/instance=cert-manager,app.kubernetes.io/name=webhook
default         kubernetes                          ClusterIP   <IP_ADDRESS>       <none>        443/TCP                  6d1h   <none>
kube-system     kube-dns                            ClusterIP   <IP_ADDRESS>      <none>        53/UDP,53/TCP,9153/TCP   6d1h   k8s-app=kube-dns
neonvm-system   neonvm-controller-metrics-service   ClusterIP   <IP_ADDRESS>     <none>        8443/TCP                 6d1h   control-plane=controller
neonvm-system   neonvm-webhook-service              ClusterIP   <IP_ADDRESS>   <none>        443/TCP                  6d1h   control-plane=controller

endpoints
$ kubectl get endpoints --all-namespaces -o wide
NAMESPACE       NAME                                ENDPOINTS                                               AGE
cert-manager    cert-manager                        <IP_ADDRESS>:9402                                         6d1h
cert-manager    cert-manager-webhook                <IP_ADDRESS>:10250                                        6d1h
default         kubernetes                          <IP_ADDRESS>:6443                                         6d1h
kube-system     kube-dns                            <IP_ADDRESS>:53,<IP_ADDRESS>:53,<IP_ADDRESS>:53 + 3 more...   6d1h
neonvm-system   neonvm-controller-metrics-service   <IP_ADDRESS>:8443                                         6d1h
neonvm-system   neonvm-webhook-service              <IP_ADDRESS>:9443                                         6d1h

describe
$ kubectl describe pods postgres14-disk-test-ll7fg
Name:         postgres14-disk-test-ll7fg
Namespace:    default
Priority:     0
Node:         kind-worker/<IP_ADDRESS>
Start Time:   Sun, 25 Jun 2023 10:19:54 +0000
Labels:       app.kubernetes.io/name=NeonVM
              autoscaling.neon.tech/enabled=true
              autoscaling.neon.tech/testing-only-always-migrate=false
              vm.neon.tech/name=postgres14-disk-test
              vm.neon.tech/runner-version=1
Annotations:  autoscaling.neon.tech/bounds: { "min": { "cpu": 0.25, "mem": "1Gi" }, "max": { "cpu": 1.25, "mem": "5Gi" } }
              k8s.v1.cni.cncf.io/network-status:
                [{
                    "name": "kindnet",
                    "interface": "eth0",
                    "ips": [
                        "<IP_ADDRESS>"
                    ],
                    "mac": "82:e5:89:ee:a3:3c",
                    "default": true,
                    "dns": {}
                }]
              k8s.v1.cni.cncf.io/networks-status:
                [{
                    "name": "kindnet",
                    "interface": "eth0",
                    "ips": [
                        "<IP_ADDRESS>"
                    ],
                    "mac": "82:e5:89:ee:a3:3c",
                    "default": true,
                    "dns": {}
                }]
              kubectl.kubernetes.io/default-container: neonvm-runner
              vm.neon.tech/usage: {"cpu":"250m","memory":"1Gi"}
Status:       Running
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  VirtualMachine/postgres14-disk-test
Init Containers:
  init-rootdisk:
    Container ID:  containerd://2182e6a69e28d3db1ff58f3073c9c696c206959823933e622a1fa68677f3dd55
    Image:         pg14-disk-test:dev
    Image ID:      sha256:5914355d278e58ffae977e7f78400738fabf5a0efbe0936e9ec06691b26094d7
    Port:          <none>
    Host Port:     <none>
    Args:
      cp
      /disk.qcow2
      /vm/images/rootdisk.qcow2
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Sun, 25 Jun 2023 10:19:55 +0000
      Finished:     Sun, 25 Jun 2023 10:19:55 +0000
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /vm/images from virtualmachineimages (rw)
  sysctl:
    Container ID:  containerd://1544b8d7f59de5c417a81b8bacac6c56d59032fa9ffb55e048b87fff455ea4d8
    Image:         runner:dev
    Image ID:      sha256:400b9c5ba6a5c60d1341075c4d6d124708e6ea1bbf583d7923b555c450287f87
    Port:          <none>
    Host Port:     <none>
    Command:
      sysctl
      -w
      net.ipv4.ip_forward=1
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Sun, 25 Jun 2023 10:19:57 +0000
      Finished:     Sun, 25 Jun 2023 10:19:57 +0000
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:         <none>
Containers:
  neonvm-runner:
    Container ID:  containerd://8c1e05e6cdcc152105c9b4e1dd53c44ba86bad15594908ed879ec8109d781194
    Image:         runner:dev
    Image ID:      sha256:400b9c5ba6a5c60d1341075c4d6d124708e6ea1bbf583d7923b555c450287f87
    Ports:         20183/TCP, 22/TCP, 5432/TCP, 9100/TCP, 10301/TCP
    Host Ports:    0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP
    Command:
      runner
      -vmspec
      eyJxbXAiOjIwMTgzLCJydW5uZXJQb3J0IjoyNTE4MywidGVybWluYXRpb25HcmFjZVBlcmlvZFNlY29uZHMiOjUsInNjaGVkdWxlck5hbWUiOiJhdXRvc2NhbGUtc2NoZWR1bGVyIiwicG9kUmVzb3VyY2VzIjp7fSwicmVzdGFydFBvbGljeSI6IkFsd2F5cyIsImd1ZXN0Ijp7ImNwdXMiOnsibWluIjoiMjUwbSIsIm1heCI6IjEyNTBtIiwidXNlIjoiMjUwbSJ9LCJtZW1vcnlTbG90U2l6ZSI6IjFHaSIsIm1lbW9yeVNsb3RzIjp7Im1pbiI6MSwibWF4Ijo1LCJ1c2UiOjF9LCJyb290RGlzayI6eyJpbWFnZSI6InBnMTQtZGlzay10ZXN0OmRldiIsInNpemUiOiI4R2kiLCJpbWFnZVB1bGxQb2xpY3kiOiJJZk5vdFByZXNlbnQifSwicG9ydHMiOlt7InBvcnQiOjIyLCJwcm90b2NvbCI6IlRDUCJ9LHsicG9ydCI6NTQzMiwicHJvdG9jb2wiOiJUQ1AifSx7InBvcnQiOjkxMDAsInByb3RvY29sIjoiVENQIn0seyJwb3J0IjoxMDMwMSwicHJvdG9jb2wiOiJUQ1AifV19LCJlbmFibGVBY2NlbGVyYXRpb24iOnRydWV9
      -vmstatus
      eyJjb25kaXRpb25zIjpbeyJ0eXBlIjoiQXZhaWxhYmxlIiwic3RhdHVzIjoiVW5rbm93biIsImxhc3RUcmFuc2l0aW9uVGltZSI6IjIwMjMtMDYtMjVUMTA6MTk6NTRaIiwicmVhc29uIjoiUmVjb25jaWxpbmciLCJtZXNzYWdlIjoiU3RhcnRpbmcgcmVjb25jaWxpYXRpb24ifV0sInBoYXNlIjoiUGVuZGluZyIsInBvZE5hbWUiOiJwb3N0Z3JlczE0LWRpc2stdGVzdC1sbDdmZyJ9
    State:          Running
      Started:      Sun, 25 Jun 2023 10:19:58 +0000
    Ready:          True
    Restart Count:  0
    Limits:
      neonvm/kvm:        1
      neonvm/vhost-net:  1
    Requests:
      neonvm/kvm:        1
      neonvm/vhost-net:  1
    Environment:         <none>
    Mounts:
      /sys/fs/cgroup from sysfscgroup (rw)
      /vm/images from virtualmachineimages (rw)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  virtualmachineimages:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  sysfscgroup:
    Type:          HostPath (bare host directory volume)
    Path:          /sys/fs/cgroup
    HostPathType:  Directory
QoS Class:         BestEffort
Node-Selectors:    <none>
Tolerations:       node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                   node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type    Reason          Age   From                 Message
  ----    ------          ----  ----                 -------
  Normal  Scheduled       13m   autoscale-scheduler  Successfully assigned default/postgres14-disk-test-ll7fg to kind-worker
  Normal  AddedInterface  13m   multus               Add eth0 [<IP_ADDRESS>/24] from kindnet
  Normal  Pulled          13m   kubelet              Container image "pg14-disk-test:dev" already present on machine
  Normal  Created         13m   kubelet              Created container init-rootdisk
  Normal  Started         13m   kubelet              Started container init-rootdisk
  Normal  Pulled          13m   kubelet              Container image "runner:dev" already present on machine
  Normal  Created         13m   kubelet              Created container sysctl
  Normal  Started         13m   kubelet              Started container sysctl
  Normal  Pulled          13m   kubelet              Container image "runner:dev" already present on machine
  Normal  Created         13m   kubelet              Created container neonvm-runner
  Normal  Started         13m   kubelet              Started container neonvm-runner

logs
$ kubectl logs postgres14-disk-test-ll7fg
2023/06/25 10:19:58 resizing rootDisk from 1Gi to 8Gi
Image resized.
2023/06/25 10:19:58 using KVM acceleration
2023/06/25 10:19:58 setup bridge interface br-def
2023/06/25 10:19:58 create /dev/net/tun
2023/06/25 10:19:58 setup tap interface tap-def
2023/06/25 10:19:58 setup masquerading for outgoing traffic
2023/06/25 10:19:58 setup DNAT for incoming traffic, port 22
2023/06/25 10:19:58 setup DNAT for incoming traffic, port 5432
2023/06/25 10:19:58 setup DNAT for incoming traffic, port 9100
2023/06/25 10:19:58 setup DNAT for incoming traffic, port 10301
2023/06/25 10:19:58 run dnsmqsq for interface br-def
2023/06/25 10:19:58 setting cgroup to 25000 100000
2023/06/25 10:19:58 using cgexec args: [-g cpu:/postgres14-disk-test-ll7fg-vm-runner qemu-system-x86_64 -runas qemu -machine q35 -nographic -no-reboot -nodefaults -only-migratable -audiodev none,id=noaudio -serial pty -serial stdio -msg timestamp=on -qmp tcp:<IP_ADDRESS>:20183,server,wait=off -drive id=rootdisk,file=/vm/images/rootdisk.qcow2,if=virtio,media=disk,index=0,cache=none -drive id=runtime,file=/vm/images/runtime.iso,if=virtio,media=cdrom,readonly=on,cache=none -enable-kvm -cpu max -smp cpus=1,maxcpus=2,sockets=1,cores=2,threads=1 -m size=1073741824b,slots=4,maxmem=5368709120b -netdev tap,id=default,ifname=tap-def,script=no,downscript=no,vhost=on -device virtio-net-pci,netdev=default,mac=56:a9:fd:99:8c:59 -kernel /vm/kernel/vmlinuz -append init=/neonvm/bin/init memhp_default_state=online_movable console=ttyS1 loglevel=7 root=/dev/vda rw]
2023/06/25 10:19:58 watching OS signals
char device redirected to /dev/pts/0 (label serial0)

Please help me how to troubleshoot, why can't I connect to postgresql in NeonVM?
And, how can I use it with Neon after deploying autoscaling (Neon is deployed using docker-compose)?

@sharnoff @cicdteam Can you guys help me?

Hi @yaoyinnan — I'll try to help where I can, but: in future, please refrain from @-ing members of the team to try to get a faster response to your issue. It's the weekend, and "self-hosted Neon" is not a paid product.

It looks like you have two questions here. I'll answer the shorter one first:

And, how can I use it with Neon after deploying autoscaling (Neon is deployed using docker-compose)?

We do not currently support running Neon in docker-compose with autoscaling. Our autoscaling feature requires Kubernetes; I'll check with the team to see if we have any docs on self-hosted Neon in K8s, but you may be on your own (it's definitely possible; OTOH I don't think we have docs for that).
For the main issue:
If what you've shown is the complete output from kubectl logs <PODNAME>, then it looks like QEMU got stuck, somehow. I have not seen this before.
A few questions:

Does this happen every time you create a VM?
Can you share more details about the exact steps you took to reproduce? e.g. how did you create the cluster? How did you install the autoscaling components onto it?
Can you share what OS (and version) and CPU ISA (x86 / ARM) you're using? Include the host machine as well if you're running in a VM or other isolation technology (e.g. WSL, a container, etc)
When doing this, are you running into system resource limits? Could it be running out of memory or throttling? That could mean that QEMU is not actually stuck, but instead very slow (or something like that).

Hi @yaoyinnan — I'll try to help where I can, but: in future, please refrain from @-ing members of the team to try to get a faster response to your issue. It's the weekend, and "self-hosted Neon" is not a paid product.

Thanks a lot for your help. Sorry for the weekend interruption.
Regarding the first question you answered, I still have some questions to ask:
I see that currently only NeonVM and PostgreSQL are deployed in Kubernetes for autoscaling, and there are no components such as Neon's SafeKeeper, PageServer, and MinIO. May I ask how the current open source autoscaling can only enable Compute to perform elastic scaling? How does it relate to Neon's other storage components?
Regarding your second question, I provide the following information for your reference and help me:

Yes, every boot is like this problem. I can see the qemu process after entering the virtual machine with kubectl exec:

/ # ps -A
PID   USER     TIME  COMMAND
    1 root      0:01 runner -vmspec eyJxbXAiOjIwMTgzLCJydW5uZXJQb3J0IjoyNTE4MywidGVybWluYXRpb25HcmFjZVBlcmlvZFNlY29uZHMiOjUsInNjaGVkdWxlck5hbWUiOiJhdXRvc2NhbGUtc2NoZWR1bGVyIiwicG9kUmVzb3V
   34 root      0:00 [dnsmasq]
   35 dnsmasq   0:00 dnsmasq --port=0 --bind-interfaces --dhcp-authoritative --interface=br-def --dhcp-range=<IP_ADDRESS>,static,<IP_ADDRESS> --dhcp-host=56:a9:fd:99:8c:59,169.254.2
   36 qemu      4h03 qemu-system-x86_64 -runas qemu -machine q35 -nographic -no-reboot -nodefaults -only-migratable -audiodev none,id=noaudio -serial pty -serial stdio -msg timestamp=on -
   56 root      0:00 /bin/sh
   81 root      0:00 ps -A

The steps to create a cluster are as follows:

I deployed it according to the steps in the README of autoscaling.
Build NeonVM Linux kernel (it takes time, can be run only once)
make kernel

Build docker images:
make docker-build

Start local kind cluster:
make local-cluster

Deploy NeonVM and Autoscaling components:
make deploy

Build and load the test VM:
make pg14-disk-test

Start the test VM:
kubectl apply -f vm-deploy.yaml

I am autoscaling cluster running in virtual machine.

Host kernel:
$ uname -a
Linux xxxxx.xxx.xxx.xxx 3.10.0-693.21.1.el7.x86_64 #1 SMP Wed Mar 7 19:03:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Guest kernel:
$ uname -a
Linux dev 3.10.0-1160.90.1.el7.x86_64 #1 SMP Thu May 4 15:21:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

And have ensured that nested virtualization is turned on:
$ lsmod | grep kvm
kvm_intel             188793  3
kvm                   653928  1 kvm_intel
irqbypass              13503  1 kvm

$  grep -Eoc '(vmx|svm)' /proc/cpuinfo
8

I have not restricted the system resources, but the resources of the virtual machine are less, and the specifications are as follows:

CPU: 8C
RAM: 32GB
Disk: 300GB

I don't know if it has any effect, I can try to adjust it a little bigger and try again.
Thank you again for your help, sorry to bother you on weekends, if it is not convenient, you can reply on weekdays.

@yaoyinnan
Have you tried with fresh main branch ? I just tried reproduce the issue but everything is going well. One note: make kind-setup should now be used instead of make local-cluster.
Also, your kernel seems to be very old (3.10). Can you try on a server with a more recent kernel?

@cicdteam @sharnoff Thank you very much for your continued help, I have solved this problem.
I switched to using baremetal deployment and switched to ubuntu 20.04 (5.18.4-051804-generic) with a higher kernel version, and the autoscaling used was also switched to the main branch.


Add Upload construct

See the docs for explanations.

[ ] More tests
[ ] Document what is done with CORS ?
[ ] Axios example ?
[ ] in depth explanation of wha the function does ?
[ ] example code for backend processing ?

See some working examples here https://github.com/t-richard/lift-upload-example
Steps to deploy it are in the README

This is really cool!


NGINX Plus: Server Zone Metrics are not Emitted

NGF currently does not emit any server_zone metrics from NGINX Plus. This appears to be an oversight in our exposure of metrics, so this is something we need to fix.
Reported by Dan Edgar:

Acceptance

All server_zone metrics emitted by NGINX Plus when used as our data plane should be exposed on our metrics endpoint.
An NGINX directive is added to every location in every server block that NGF generates so that a server_zone metric is emitted for each location.

https://nginx.org/en/docs/http/ngx_http_api_module.html#status_zone


fix secrets

Contributing a Chart / update to an existing Chart

[x] Run helm lint on the chart dir.
[x] (Update) Bump the Chart.yaml version before merging, to release it as a new version.
[x] (Update) If the PR includes new configurable parameters in the chart's values.yaml. Add documentation in the appropiate README.

Thanks!

@glpatcern how do I properly test if the wopi is working correcly? https://cs3mesh.softwaremind.com/wopi is this enough, or should I test collabora/codimd as well?

@dagl you should first try and deploy release 7.5.5 as older WOPI server releases do not work with latest Reva. Then it sould be tested with Collabora, yes, and as an intermediate step you could execute the WOPI server testsuite to validate that the WOPI server can talk to Reva.
If you want we can discuss more details over e.g. gitter.im/, let me know.

@dagl you should first try and deploy release 7.5.5 as older WOPI server releases do not work with latest Reva. Then it sould be tested with Collabora, yes, and as an intermediate step you could execute the WOPI server testsuite to validate that the WOPI server can talk to Reva.
If you want we can discuss more details over e.g. gitter.im/, let me know.

I did deploy version  7.5, but I didn't deploy the latest Reva yet. What testsuite are you talking about? And what's you handle on Gitter?

I did deploy version 7.5, but I didn't deploy the latest Reva yet.

OK, but from what I saw at https://cs3mesh.softwaremind.com/wopi it's v6.7

What testsuite are you talking about? And what's you handle on Gitter?

The WOPI testsuite at https://github.com/cs3org/wopiserver/#unit-testing. My gitter handle is the GitHub one.


should be able to use maxConnectRetries

be able to specify max_connect_retries in the dsn string as part of the query string

:+1:

Looks good - thank you!

you're welcome @chrisboulton. good to see you back here!


Cannot docker compose

Operating System: Windows
Running command: docker-compose up -d
Result:
Pulling kairon-question-generation (digite/kairon-question-generation:latest)...
ERROR: The image for the service you're trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing.

Continue with the new image? [yN]y
Pulling kairon-question-generation (digite/kairon-question-generation:latest)...
ERROR: pull access denied for digite/kairon-question-generation, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Sorry for the late reply, Get the latest docker-compose


Pick up Codis to Pika.

I tried to relocate the codis project to Pika and removed the redis dependency and upgraded to the go module. At the moment, the dependency jemalloc-go for compiling codis in the makefile of codis has not been modified yet, so the subsequent make process has not been verified yet. If you are familiar with go module and makefile, you can help to finish this pull request.

能编译过就行。jemalloc-go可以后面再加

🙋 I have some familiarity with Golang.

🙋 I have some familiarity with Golang.

ok

滴滴

大佬，带我一个，我有在生产用codis+pika

接触过一些codis，混个脸熟

滴滴 想尽自己所能参与一下

@kernelai 这个改动是不是和已有的改动https://github.com/kernelai/codis/tree/release3.2-dev 不兼容，是不是得合并一下

@kernelai 这个改动是不是和已有的改动https://github.com/kernelai/codis/tree/release3.2-dev 不兼容，是不是得合并一下

不兼容的地方比较多。后面的pr可以把特性慢慢合进来。这个pr 可以主要解决codis的代码能合并到pika仓库，解决go mod的问题。

接触过codis


birdtray: fix qttranslations path

Motivation for this change

fix qttranslations path (#86054)
birdtray crashes not finding the translations without this fix.

Things done

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

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

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

Thanks, builds and runs.
I just tried the version without the fix (/nix/store/q85idskz8qizkyxxrghcf66fy5nija0w-birdtray-1.8.1) and env LC_ALL=de birdtray correctly works and shows translations too?

I just tested on 20.09pre228622.029a5de0839 (Nightingale):
Without env:
[nix-shell:~]$ birdtray
Using Wayland-EGL
Segmentation fault (core dumped)

With:
[nix-shell:~]$ env LC_ALL=de birdtray
Using Wayland-EGL
Segmentation fault (core dumped)

This is what the log shows (run with option -l):
2020-06-16 10:33:31 Birdtray version 1.8.1 started
2020-06-16 10:33:31 Failed to load translation for de_DE

The log shows the same message for any locale.
According to the issue I linked, this is the expected behavior without the patch.

It doesn’t work on wayland anyway, neither with, nor without the patch :)
I always test with env QT_QPA_PLATFORM= WAYLAND_DISPLAY= birdtray there.
Ah, I didn’t know about -l. I also get Failed to load translation for de_DE but it still displays everything in german (without the patch), so I guess it fails to load translations that are used somewhere else?

I just found out it does launch on wayland!
Just prefix QT_QPA_PLATFORM="xcb" when running, then it works!
Yeah, I'm not sure which translations are the problem, but this patch removes the error, so I guess it is needed?

I just found out it does launch on wayland!
Just prefix QT_QPA_PLATFORM="xcb" when running, then it works!
Yeah, I'm not sure which translations are the problem, but this patch removes the error, so I guess it is needed?

This likely enforces xwayland.

Sorry everyone, I forgot to checkout a new branch. I'm still a bit new to this and learning! Rebased my commits and now it looks clean again...
Hope I didn't cause any trouble.


Add a template for planner cards

Extending a template makes it easier to supply blocks of HTML than when using a macro.
This is very rough still:

Currently the leadin and body block surrounds are present even if there's no content for them
The ID probably doesn't need to be specified manually, at least not like this
There's only three cards, and their presence and order is hardcoded right now.
The styling on the definition list is completely off.

:)


inconsistency between different preprocessing pipelines

naming inconsistency
in the demo data within this repo, kidney_function is named kf.
The Python script produces mortality while the r script produces mortality24.
data inconsistency
The data produced by the R script seems to be missing some lines.

In [6]: py = pd.read_parquet("data/mortality/mimic/sta.parquet")

In [7]: r =  pd.read_parquet("data_r/mortality24/mimic/sta.parquet")

In [8]: len(py)
Out[8]: 38667

In [9]: len(r)
Out[9]: 38139

Hi Leo,
thanks for the interest in our benchmark and for alerting us the discrepancies you have observed.
Regarding the data inconsitencies: I've looked specifically at the mortality task for MIMIC III, and it seems that the inconsistency comes from differences in how the base cohort is defined in R and Python. The experiments shown in the paper were all run on R-generated data, so those should generally be regarded as the "gold standard". The Python script was only added later to make the repo easier to use for Pythonians. Nevertheless, the two scripts should obviously arrive at the same number, so thank you for flagging that that's not the case.
I've now fixed the issues for mortality/MIMIC. Before I push, I just want to do another check that similar issues aren't appearing in other tasks and that I haven't broken anything along the way. I'll aim to push my changes by EoD Monday, and will fix the naming inconsistencies while I am at it.

Great, Thanks!


Gate::resource should merge extra habilites

Laravel Version: v5.4.28
PHP Version: 7.1.4-1+deb.sury.org~xenial+1
Database Driver & Version: Irrelevant

Description:
Using the method Gate::resource() and defining the last attribute array $abilities = null as described on the documentation:

By default, the view, create, update, and delete abilities will be defined. You may define additional abilities by passing an array as the third argument to the resource method. The key of the array defines the name of the ability while the value defines the method name:

Currently, if you define the third argument it is overriding the default abilities on the resource method.
Steps To Reproduce:
Use the method Gate::resource() passing the third attribute as an array of extra abilities.

i agree with you, the wording on the documentation suggests that they will merge, but personally i would prefer to keep the existing functionality, and just change the docs.
by overriding, you still have the ability to define extra methods by something like
Gate::resource('blogs', 'BlogController', ['index', 'create', 'store', 'edit', 'update', 'destroy', 'foo', 'bar']);

granted, it is a little verbose, but if we switch to a merging functionality, we lose the ability to only define our custom methods, and get rid of the default ones.
Gate::resource('blogs', 'BlogController', ['foo', 'bar']);

@browner12 Sounds reasonable to just update the docs with the correct information.

Thanks for https://github.com/wlepinski/docs/pull/1 :)


NUI-552 [Travis] All Action Code Open Source Repos Should Only be Tested on Linux

NUI-552 [Travis] All Action Code Open Source Repos Should Only be Tested on Linux

Removed Node versions 10.15 and 10.19 from Travis
Modified Travis to run only on Linux
Added code coverage reporting
Simplified script test
Added script beautify
Updated eslint version and fixed complaints

Note that 27.1.0 was an erroneous release. It was unpublished.


Add formatting to /wallet

https://github.com/x7finance/telegram-bot/commit/4c25a1ec4b62a1b46c8e627efc283a2912beb2c4


add inc modeling test

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Feature Request : Add cncf-cla check in the bot

Check the cla status and add appropriate labels, as per cncf license guidelines each and every contributor should have signed cla.

@asifdxtreme We don't have any CLA requirement yet.

+1


Cannot interact with tooltip messages that appear when hovering on them

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
For instance, see this error message:

The issue here is that I cannot interact with the tooltip message (e.g., I cannot copy the link or click on it.) That would be useful, considering I can only remember so much of that URL at once that I have to go back and forth between Zed and Safari to compose the entire URL. 🙂
Environment
Zed: v0.102.2 (stable)
OS: macOS 13.5.1
Memory: 64 GiB
Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
No response

If I'm not mistaken, this issue looks a lot like #1222.

Not sure if they’re related to the same UI feature, but if it is, then I think you're right. Thanks!


[shapes] DrawPolyEx() and DrawPolyExLines() naming could be confusing

Some related issues were introduced recently: https://github.com/raysan5/raylib/issues/702 and https://github.com/raysan5/raylib/issues/797
It seems those functions naming is confusing for several users. One idea for a re-branding of the functions could be:
DrawPolyEx() --> DrawTriangleFan()
DrawPolyExLines() --> DrawLineStrip()

Functions renamed in commit https://github.com/raysan5/raylib/commit/604a8c0b78b6f51abcce61aa0c3db25412acafa7.


PhoneNumber validator: Wrong/invalid regex strings

Wriong fixed national pattern in BE
(File: Zend/I18n/Validator/PhoneNumber/BE.php)
Regular expression used:
'/^(?:1[0-69]|[23][2-8]|[49][23]|5\\d|6[013-57-9]|71)\\d{6}|8(?:0[1-9]|[1-79]\\d)\\d{5}$/'

The start (^) and end ($) tokens are separated by an OR (\d{6} | 8), which makes the expression match a lot of invalid phone numbers (eg. numbers that are way too long but match the first part)
Proposed solution:
'/^(?:(?:1[0-69]|[23][2-8]|[49][23]|5\\d|6[013-57-9]|71)\\d{6}|8(?:0[1-9]|[1-79]\\d)\\d{5})$/'

Invalid expressions in VA
(File: Zend/I18n/Validator/PhoneNumber/VA.php)
Regular expression used (twice):
'/^N/A$/'

Obviously the forward slash cannot be used without escaping, but it should probably be null or something.

This issue has been closed as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html