Elisp updates

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@brprice
https://github.com/NixOS/nixpkgs/issues/196414#issuecomment-1305051476

Oh man!
By some obscure reason MELPA is failing to view Cask
https://melpa.org/#/cask

@brprice
#196414 (comment)

Thanks for the ping. As I understand it, this PR won't directly help with #196414, since that issue is with 22.05 and this PR is targeted at master. However, I'm not very familiar with nixos' development flow, so I may just be confused here.

Well, the idea would be backport this change (using git cherrypick dark magic).

@ofborg build emacs.pkgs.ada-mode

Okay something happened again with ada-mode's dep on wisi, I'll have to take a look.

Seems like ada-mode 7.1.3 (which seems to be a version not properly checked into their git repository?) needs wisi 4.1.1 which is not released on ELPA – likely also some other changes as wisi was changed somehow.

@adisbladis what do you think about concentrating the manual ad-hoc packages in a subdir?


Use tensorflow instead of tensorflow-gpu

Version 0.0.1 has tensorflow in requirements.txt.
0.0.3 now uses tensorflow-gpu.
It is common use case to write and test model in laptop without GPU and then deploy it to server with GPU.
So it will be great to support both CPU and GPU modes in the DeepPavlov lib.
python setup.py develop outputs
Searching for tensorflow-gpu==1.4.0
Reading https://pypi.python.org/simple/tensorflow-gpu/
No local packages or working download links found for tensorflow-gpu==1.4.0
error: Could not find suitable distribution for Requirement.parse('tensorflow-gpu==1.4.0')

pip 9.0.3
Python 3.6.1

We added tensorflow-gpu to requirements because the SQuAD model does not work on the CPU.
We will consider your notes about using DP on laptops and maybe return CPU version of TF and add additional notes for SQuAD model to README


Test: file events

Refs:

[x] macOS @sana-ajani
[x] linux @joaomoreno
[x] windows @joyceerhl

Complexity: 2
Create Issue

File events are now throttled but only when a large number of events is coming in. This test plan item is not for testing the throttling but making sure normal amount of file events are still properly reported because quite a bit of code was refactored and changed during the milestone.
Testing:

open VSCode file explorer and editor on a folder side by side with an external tool that allows to do changes
verify file modifications visualise in the explorer and editor (change, delete, create)
verify the same steps opening a multi-root workspace (a different file watcher is used in that case)

Works well!


Static files not served as expected

I wasn't able to access the static files after following the README. I have ASSETS_URL=/static in my .env file and the summary endpoint reports model_url: "/static/cif/P38398.cif" as expected. However, http://localhost:8000/static/cif/P38398.cif gives a 404 error. The file is present locally at ./data/cif/P38398.cif. Should it be in some other location?

Thanks for creating this issue and sorry for the huge delay getting back to you.
This was basically an issue with documentation - the API is available on port 80, but we should be using people to go via the nginx frontend which is running on port 80 (this is also responsible for serving static files).
#35 should address this

Thanks @sillitoe. I figured it would be something easy like this. I can confirm it works on port 80.


Add 2.6.0 to BWC Version Matrix

Description
Add 2.6.0 to BWC Version Matrix
Check List

[x] All tests pass
[x] Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #810 (01b6738) into 2.x (6ff359c) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 01b6738 differs from pull request most recent head 55e64f8. Consider uploading reports for the commit 55e64f8 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##                2.x     #810   +/-   ##
=========================================
  Coverage     85.18%   85.18%
  Complexity     1083     1083
=========================================
  Files           151      151
  Lines          4380     4380
  Branches        393      393
=========================================
  Hits           3731     3731
  Misses          472      472
  Partials        177      177

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

I guess this is a missing backport from https://github.com/opensearch-project/k-NN/pull/793.

I guess this is a missing backport from #793.
No, the BWC matrix is different for main and 2.x


The terminal's company instructions have no effect

When using the company command on the terminal, it has no effect. And it will also confuse the display content of planets in the Moons list!
Using LethalLevelLoader 1.2.2! @IAmBatby  May I ask what the situation is?

Having the same issue here

Can confirm that trying to navigate to the Company Building does not work using LethalLevelLoader v1.2.2.

I FOUND A TEMPORARY FIX
install the mod "AutoCompanyBuilding" by La_chips and it will just force you to the company building and work.

Can confirm that trying to navigate to the Company Building does not work using LethalLevelLoader v1.2.2.

I FOUND A TEMPORARY FIX
install "AutoCompanyBuilding" by La_chips and at day 0 it will force you to the company building and it works.

The actual temporary fix is to downgrade LethalLevelLoader 1.2.1 until the issue can be patched.
P.S. Commenting "me too" contributes nothing to the conversation. Just thumbs up to reduce the noise on an issue.

same issue

The actual temporary fix is to downgrade LethalLevelLoader 1.2.1 until the issue can be patched.
P.S. Commenting "me too" contributes nothing to the conversation. Just thumbs up to reduce the noise on an issue.

Don't downgrade to 1.2.1. This version has a tendency to corrupt saves/items.

i got a temporary solution now, check #78

in short, u cannot rely on LLL Terminal Formatting in 1.2.2, ok that really break my trust a little

Don't downgrade to 1.2.1. This version has a tendency to corrupt saves/items.

Certainly made for an interesting series of games. Loaded in with three jetpacks instead of pro flashlights :laughing:
@CoolLKKPS  are you saying to pair the LethalLevelLoader 1.2.2 with TerminalFormatter 0.2.3?

Resolved in future versions of the project.


[WIP] Refactor analytics tests

@rishig

Automated message from Dropbox CLA bot
@umkay, it looks like you've already signed the Dropbox CLA. Thanks!

Closing since this is now in #1923.


[QUESTION] changing  value of dependency of dependency

Helm version
version.BuildInfo{Version:"v3.7.0", GitCommit:"eeac83883cb4014fe60267ec6373570374ce770b", GitTreeState:"clean", GoVersion:"go1.16.8"}
Cloud Provider/Platform:
Minikube
Problem
I am using helm charts this way:

generic-service chart - is template for any service
oauth2-service-base - is template for any env. It has dependency generic-service chart
oauth2-service-local - is template for local env. It has dependency oauth2-service-base chart

When I override value for generic-service chart in  oauth2-service-base work as expected.
When I want to override value for generic-service chart in oauth2-service-local value is not
overridden,  oauth2-service-base value is present.
Question
Is override of template value of dependency of dependency possible?

This is intentional. Template functions are globally namespaced. That is to say, chart dependencies and the root chart share the same function namespace, so if two charts define a function named _helpers.serviceAccountName, it is undefined which function will be called.

@joejulian
This means that way that I want to use Helm:
abstract chart -> less abstract chart -> implementation chart
is not corresponding with helm architecture.
I want to avoid situation where someone want to create
chart for my_new_env and just copy paste chart from another one
and just changing few values.
How I can achieve that in way that is more corresponding with Helm architecture?

You mention value and template. I think there may be some miscommunication. Can you offer an example that I can duplicate on my own? That would help me offer better advice.
If you have a sample chart directory, you can tar it and drop it in your response.

github: "Something went really wrong..." when I drop file.
Link to we transfer: https://we.tl/t-admK4ahr6E


Add an option in Scaffold to not register to the Scaffold to the ScaffoldMessengerState

Use case
I need to wrap the entire app with a widget that displays a box above the keyboard. To do so, I used a Scaffold:
runApp(MaterialApp(
  builder: (_, child) {  // `child` is one of the many page of the app (ex: `MyPage`) which might contain a `Scaffold`.
    return Scaffold(
      body: Column(
        children: [
          Expanded(
            child: child,
          ),
          MyBox(), // <- Generic widget I need to display on top of the keyboard. It might contain some business logic, change its size etc...
        ],
      ),
    );
  },
));

The issue is that the page displayed might contain a Scaffold too (to display an AppBar, a FloatingActionButton , a Drawer etc.)
Ex:
class MyPage extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: MyAppBar(),
      floatingActionButton: MyFloatingActionButton(),
      body: MyBody(),
    );
  }
}

When I do
ScaffoldMessenger.of(context).showSnackBar(mySnackbar);

it uses the root Scaffold which is the one used to display MyBox and not the on in MyPage containing the FloatingActionButton or other elements.
It results in the Snackbar appearing on top of the FloatingActionButton (and not above it), because the Scaffold displaying it doesn't have the FloatingActionButton.

Proposal

Add an boolean option to the Scaffold constructor (ex: this.registerToScaffoldMessenger = true), when it is set to false, it won't register the Scaffold to the ScaffoldMessenger at :
https://github.com/flutter/flutter/blob/ba01ec8faae9a9be3cd90ee2b7357a803b7a7178/packages/flutter/lib/src/material/scaffold.dart#L2656-L2669
could become:
@override
 void didChangeDependencies() {
   // Using maybeOf is valid here since both the Scaffold and ScaffoldMessenger
   // are currently available for managing SnackBars.
   final ScaffoldMessengerState? currentScaffoldMessenger = ScaffoldMessenger.maybeOf(context);
   // If our ScaffoldMessenger has changed, unregister with the old one first.
   if (_scaffoldMessenger != null &&
     (currentScaffoldMessenger == null || _scaffoldMessenger != currentScaffoldMessenger)) {
     _scaffoldMessenger?._unregister(this);
   }
   // Register with the current ScaffoldMessenger, if there is one.
   _scaffoldMessenger = currentScaffoldMessenger;
  if (widget.registerToScaffoldMessenger) {
    _scaffoldMessenger?._register(this);
  }

Assuming that there are multiple ScaffoldMessengers (i.e. a root + a nested one somewhere in the tree), I'd expect a different BuildContext to get a different ScaffoldMessenger. This is similar to how other inherited widgets work.
If I run this code sample and inspect the Widget tree with the Devtools, I see only one ScaffoldMessenger.
import 'package:flutter/material.dart';

void main() async {
  runApp(MaterialApp(
    home: Scaffold(body: Center(child: Text("foo"))),
  ),
);

You are going to need to insert your own ScaffoldMessenger in your widget tree, below the MaterialApp.

@navaronbracke what we did was to give a kRootScaffoldMessengerKey = GlobalKey<ScaffoldMessengerState>() to our MaterialApp to then call
kRootScaffoldMessengerKey.currentState!.showSnackBar(mySnackBar);

From anywhere in the app without a need for the context (so the services could do it).
So adding a nested/scoped ScaffoldMessenger inside the builder of the MaterialApp would prevent us from using one common kRootScaffoldMessengerKey.

Sorry, after reading out the docs of the builder of the MaterialApp:

A builder for inserting widgets above the [Navigator] or - when the [WidgetsApp.router] constructor is used - above the [Router] but below the other widgets created by the [WidgetsApp] widget, or for replacing the [Navigator]/[Router] entirely.

I can as you suggested add a Scaffold and then another ScaffoldMessenger below with our global key since it will be built once (and not once for every routes):
MaterialApp(
  builder: (context, child) {
    Scaffold(
      body: Column(
        children: [
          Expanded(
            child: ScaffoldMessenger(
              key: kRootScaffoldMessengerKey,
              child: child,
            ),
          ),
          MyBox(), // <- Generic widget I need to display on top of the keyboard. It might contain some business logic, change its size etc...
        ],
      ),
    );
  },
),

Thank you for you quick response, I'll close the issue since the requested feature doesn't have any motivation anymore.


{"message":"Invalid handler specified"}

Please help me,
when i launch Dyson cloud i receive this message Italian language :
Impossibile caricare il flusso di configurazione: {"message":"Invalid handler specified"}

the same Dyson local
Config flow could not be loaded: {“message”:“Invalid handler specified”}

same over here for both

Error log says
Error occurred loading configuration flow for integration dyson_cloud: cannot import name 'DysonPurifierHumidifyCoolFormaldehyde' from 'libdyson' (/usr/local/lib/python3.10/site-packages/libdyson/__init__.py)

Are u sure to have DysonPurifierHumidifyCoolFormaldehyde ? i have hp06 (formaaldeide) but dosn't work. .. i chose simply hot+cool and it work.

Solved.  Config flow could not be loaded: {“message”:“Invalid handler specified”}

Deleted integrations in hack.
Deleted directories in custom component (with terminal).
Restart Home Assistant.
Used terminal (python3 get_devices.py) to discover serial credential etc...
initially it didn't work because I had disconnected the account from the mobile phone.
I logged in with my phone, ran python3 get_devices.py again and it worked.
In home assistant I only installed the hacs dyson local component.
Restarted home assistant
Launch dyson local and it worked choosing dyson hot+cool (i have hp06)

Ciao, se posso volentieri
Cosa non ti è ciaro?

Ciao, se posso volentieri Cosa non ti è chiaro?

Intanto grazie per la risposta :)
Brevemente ho fatto una installazione del HACS e tutto ok, poi quando ho fatto il nuovo aggiornamento di HA mi ha dato quell'errore che ha dato pure a te.
Per risolverlo ho dovuto caricare un Backup.
Ora non credo farò l'aggiornamento.

Ciao, quell'errore a me lo ha dato quando ho installato il modulo per il Dyson.
L'aggiornamento dell' HACS era invece andato a buon fine.
Ora ho anche io diversi aggiornamenti pendenti ma... visto che ora funziona tutto .. non tocco nulla :)

Similar issues with Dyson local and Dyson cloud.
After adding and downloading the integrations https://github.com/shenxn/ha-dyson and https://github.com/shenxn/ha-dyson-cloud, I tried to configure Dyson local or cloud but the following error appeared:
The Config flow could not be loaded: {“message”:“Invalid handler specified”}
This is the HA logfile about the issue:
Logger: homeassistant.config_entries
Source: config_entries.py:834
First occurred: 10:16:01 (2 occurrences)
Last logged: 10:16:06
Error occurred loading configuration flow for integration dyson_cloud: cannot import name 'DysonPurifierHumidifyCoolFormaldehyde' from 'libdyson' (/usr/local/lib/python3.10/site-packages/libdyson/init.py)
Error occurred loading configuration flow for integration dyson_local: cannot import name 'DysonPurifierHumidifyCoolFormaldehyde' from 'libdyson' (/usr/local/lib/python3.10/site-packages/libdyson/init.py)

Similar issues with Dyson local and Dyson cloud.
After adding and downloading the integrations https://github.com/shenxn/ha-dyson and https://github.com/shenxn/ha-dyson-cloud, I tried to configure Dyson local or cloud but the following error appeared:

Dyson cloud is not actively updated and it messes things up:

Solved. Config flow could not be loaded: {“message”:“Invalid handler specified”}

Deleted integrations in hack.
Deleted directories in custom component (with terminal).
Restart Home Assistant.
Used terminal (python3 get_devices.py) to discover serial credential etc...
initially it didn't work because I had disconnected the account from the mobile phone.
I logged in with my phone, ran python3 get_devices.py again and it worked.
In home assistant I only installed the hacs dyson local component.
Restarted home assistant
Launch dyson local and it worked choosing dyson hot+cool (i have hp06)

Looks like this is working but not for me, i have a TP09.

I had a similar issue, not exactly the same but perhaps my solution may help here.  I tried to use the latest source code from the main branch and encountered this error when attempting to load dyson_local:
Error occurred loading configuration flow for integration dyson_local: No module named 'libdyson'

I did a little digging and found that this commit was implemented a while back, and decided to implement the referenced libdyson Github code in the requirements field as follows:
    "requirements": ["libdyson@git+https://github.com/shenxn/libdyson@main"],

The full manifest.json was this, and this worked for me:
# cat manifest.json
{
    "domain": "dyson_local",
    "name": "Dyson Local",
    "config_flow": true,
    "documentation": "https://github.com/shenxn/ha-dyson",
    "issue_tracker": "https://github.com/shenxn/ha-dyson/issues",
    "dependencies": ["zeroconf"],
    "codeowners": ["@shenxn"],
    "requirements": ["libdyson@git+https://github.com/shenxn/libdyson@main"],
    "version": "0.16.4-4",
    "iot_class": "local_polling"
}

Here's also another solution I found:
I found a solution, buried in this thread:
https://github.com/shenxn/libdyson/pull/32#issuecomment-1399591550
@javemp wrote it, I followed it and now it's working:
to get this working:

fully uninstall existing integration and restart ha
reinstall the integration from hacs (do not restart ha yet) and modify your manifest.json file to change:
“requirements”: [“libdyson==0.8.11”]
to:
“requirements"<EMAIL_ADDRESS>restart ha and install integration as per normal, you should now see purifier cool in the list of devices

huge thanks to @jezzab for his work

Here's also another solution I found:
I found a solution, buried in this thread: shenxn/libdyson#32 (comment) @javemp wrote it, I followed it and now it's working: to get this working:

fully uninstall existing integration and restart ha
reinstall the integration from hacs (do not restart ha yet) and modify your manifest.json file to change:
“requirements”: [“libdyson==0.8.11”]
to:
“requirements"<EMAIL_ADDRESS>restart ha and install integration as per normal, you should now see purifier cool in the list of devices

huge thanks to @jezzab for his work

Looks promising except that i have a Hot+Cool+Formaldehyde and that one isn't shown, even with this trick

Adding “requirements"<EMAIL_ADDRESS>fixed this for me. I was able to use it for the cloud as well, log in, then add the local entity and delete cloud.
Any plans on making that the main lib?


Build the image in Konflux with buildah-24gb

Build the image in Konflux with buildah-24gb

/hold

/close


Passing a template to ngx raw project

Hello everyone,
I bought a template and I passed all scripts and styles in the NGX Structure and all works but fonts don't work when I compile the application.
The template has a style.scss where imports a font from Google API.
@import url(https://fonts.googleapis.com/css?family=Dosis:400,600,700|Great+Vibes);
I compiled the application with the command npm run build but I think the proccess ignore the import that in dist folder doesn't appear the font.
What do you suggest me guys?

The import works well, but it's not supposed to be present in your build folder as this syntax is for dynamic imports: the font will be loaded directly from google servers, even in your prod build.
If you want to package the font with your app, you have to download it from google font along with the css, and put it in your app sources.

Closing this as we haven't heard more from @ChristianGalvez23, and @sinedied's answer seems to be spot on.


InvalidOperationException for Visual Studio 2017

I have Visual Studio 2017 community edition installed on my machine and I am not able to get the VsixFact to work. I have the Visual Studio SDK installed through the Visual Studio installer. My version of Visual Studio is 15.7.4
I have the following test:
 [VsixFact]   public void Testing2()   {       Assert.True(true);   }
When I run it, I get the following error:

Message: System.InvalidOperationException : Cannot execute test for specified VisualStudioVersions=15.0 because there is no VSSDK installed for that version.

I even tried adding the NuGet package for Microsoft.VisualStudio.Shell.15.0 (which pulls a ton of stuff down).

@kzu I tried installing VS2015 with update 1 on top of the VS2017. I still wasn't able to get my test to run. There could be some configuration I am missing.

Yep, the support for 2017 wasn't solid to begin with (I wrote most of the stuff when there wasn't even a 2017 at all, back in 2015).

Ahh I see. I wasn't able to get it to work with 2015 either. I was having some issues with some of the linq statements not returning anything.
I believe VsVersion.cs  was one of the problems, in the constructor.
I've tried going through and fixing everything on my machine, but it seems like xUnit isn't wanting to use the test frameworks, executors, and runners you have written.

So I've gotten all the way up to Visual Studio launching when the test is run, but it looks like the test itself doesn't actually run.

Ok, documentation still pending, but things are working great for 2017 and later :).
It's been a long while, but perhaps you'd consider giving it another try.
Closing for now, feel free to reopen if you have issues.


error: invalid use of ‘auto’ const std::string& pre) -> auto { ^ .... during the process of "make -j4"

环境
1.系统环境：Red hat Linux Enterprise
2.MegEngine版本：
3.python版本：
复现步骤

请提供关键的代码片段便于追查问题
请提供完整的日志及报错信息
(base) [intern6@node011 build]$ make -j4
-- Building MegBrain 8.6.0
-- Using GNU gold linker.
-- Found PythonInterp: /mnt/xfs1/home/intern6/anaconda3/envs/CRDET/bin/python3 (found suitable version "3.6.10", minimum required is "3")
-- Setting build type to 'RelWithDebInfo' as none was specified.
-- Found PythonInterp: /mnt/xfs1/home/intern6/anaconda3/envs/CRDET/bin/python3 (found version "3.6.10")
-- Found CuDNN: /cm/shared/apps/cudnn/7.4.2 (found version: 7.4)
-- Found TensorRT: /mnt/xfs1/home/intern6/software/TensorRT-<IP_ADDRESS> (found version: 5.1.5)
-- Build with MKL in /mnt/xfs1/home/intern6/software/MegEngine/third_party/mkl/x86_64
-- GPU support is disabled
-- Intel(R) MKL: include /mnt/xfs1/home/intern6/software/MegEngine/third_party/mkl/x86_64/include
-- Intel(R) MKL: lib libmkl
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
git found: /mnt/xfs1/home/intern6/git/libexec/git-core/git
-- NumPy ver. 1.18.5 found (include: /mnt/xfs1/home/intern6/anaconda3/envs/CRDET/lib/python3.6/site-packages/numpy/core/include)
-- Configuring done
-- Generating done
-- Build files have been written to: /mnt/xfs1/home/intern6/software/MegEngine/build
[  2%] Built target halide
[  2%] Built target zmq
[  2%] Built target protobuf
[  3%] Built target flatc
[  3%] Built target flatbuffers
[  3%] Built target flathash
[  3%] Built target cuda-stub
[  3%] Built target lapack_static_weak_target
[  3%] Built target _opr_param_defs
[  4%] Built target gtest
[  4%] Built target ucx
[  4%] Built target dnnl_common
[  4%] Built target nccl
[  4%] Built target mgb_proto_target
[  4%] Built target _mgb_opr_param_defs
[  6%] Built target mgb_serialization_schema_fbs
[  6%] Built target mgb_opr_py
[  9%] Built target mgb_swig_compilation
[ 12%] Built target dnnl_cpu
[ 12%] Built target version_ld
[ 12%] Built target dnnl
[ 13%] Built target megray
[ 13%] Building CXX object dnn/src/CMakeFiles/megdnn.dir/common/add_update.cpp.o
[ 13%] Building CXX object dnn/src/CMakeFiles/megdnn.dir/common/argmxx/base_impl.cpp.o
[ 13%] Building CXX object dnn/src/CMakeFiles/megdnn.dir/common/basic_types.cpp.o
[ 13%] Building CXX object dnn/src/CMakeFiles/megdnn.dir/common/argsort.cpp.o
[ 13%] Building CXX object dnn/src/CMakeFiles/megdnn.dir/common/batch_conv_bias.cpp.o
[ 13%] Building CXX object dnn/src/CMakeFiles/megdnn.dir/common/batch_normalization.cpp.o
[ 13%] Building CXX object dnn/src/CMakeFiles/megdnn.dir/common/batched_matrix_mul.cpp.o
[ 13%] Building CXX object dnn/src/CMakeFiles/megdnn.dir/common/checksum.cpp.o
[ 13%] Building CXX object dnn/src/CMakeFiles/megdnn.dir/common/concat_split.cpp.o
[ 13%] Building CXX object dnn/src/CMakeFiles/megdnn.dir/common/cond_take/opr_impl.cpp.o
[ 13%] Building CXX object dnn/src/CMakeFiles/megdnn.dir/common/conv_bias.cpp.o
[ 14%] Building CXX object dnn/src/CMakeFiles/megdnn.dir/common/conv_pooling.cpp.o
/mnt/xfs1/home/intern6/software/MegEngine/dnn/src/common/conv_bias.cpp: In static member function ‘static megdnn::ConvBiasForward::WinogradParam megdnn::ConvBiasForward::parse_winograd_name(const string&)’:
/mnt/xfs1/home/intern6/software/MegEngine/dnn/src/common/conv_bias.cpp:337:49: error: invalid use of ‘auto’
const std::string& pre) -> auto {
^
make[2]: *** [dnn/src/CMakeFiles/megdnn.dir/common/conv_bias.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [dnn/src/CMakeFiles/megdnn.dir/all] Error 2
make: *** [all] Error 2

Which gcc version are you using?

pls refs scripts/cmake-build/BUILD_README.md  to install build env or consider upgrade u gcc


modulenotfounderror: no module named attrs for version 21.2.0

Unable to obtain attrs library version 21.2.0. No mention of this version not working was found in the documentation. Only version 21.1.0 was mentioned. The modulenotfounderror error only occurs with version 21.2.0

attrs 21.2.0 is right there: https://pypi.org/project/attrs/21.2.0/
You seem to have some issues with your packaging that we cannot affect.


Footer section icons

Related Issue
#1537
Description
This pull request addresses the issue of incorrectly displayed icons in the footer section of our website. It involves updating the icons for Facebook and Twitter with the correct base64 encoded SVG images and adjusting other icons, such as those for "Advertise" and "Become a Seller," to closely match the original website's design.
Changes Made:

Replaced broken or incorrect icon URLs for Facebook and Twitter with valid base64 encoded SVGs.
Updated icons for features like "Advertise" and "Become a Seller" to match the design of the original website.

Type of PR

[X] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
After updation:

Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.

Additional context:
If there are any additional adjustments or feedback, please let me know.
Your review and approval are appreciated to merge these fixes into the main branch.
Thank you for considering this pull request. Looking forward to your feedback!

resolve conflicts.


Allow automatic "waiting" in tests.

This has been fundamentally supported when using $.ajax based requests for quite some time (since at least Ember 1.8ish).
This change brings testing parity to ember-fetch...

@rwjblue check this first: https://github.com/emberjs/ember-test-helpers/pull/202

Yeah, that PR looks nice, but it doesn't really help us here AFAICT.  Main reasons:

ember-test-helpers/wait implementation is only used for unit and integration tests (not acceptance tests).  The acceptance test infrastructure is (for now) still in emberjs/ember.js itself.
Things downstream that run in production cannot easily know if ember-test-helpers module is present so a straight import { incrementPendingRequestCount } from 'ember-test-helpers' cannot be done, because when ember-test-helpers is not present an error will be thrown by the loader.
I think a promise based API would still be nice to add support for.  (this is really just an opinion thing though)

looks good, we should add 1 acceptance test in the dummy app so we dont regress in the future.

The problem with approach is that it adds waiters instead of ajax requests. wait accepts an options hash to skip waiting for a few things. Passing wait({ waitForAjax: false }) should affect $.ajax and fetch as both network requests and should be grouped.
However I never saw that feature in use, probably no one would ever notice.
If we wanted to provide helpers (and a nicer promise-based API too), how would you make that import go await in production? Babel transforms?
I could make the same refactor in Ember itself.

I've discovered that my the approach in my PR was flawed and probably this is too.
A numeric counter is not enough because if the user doesn't wait it is possible for a not-awaited fetch requests to end in the next test, incorrectly decrementing the counter.
We should keep an array of pending promises and when they are fulfilled, slice them from the array. The timer needs to wait until the array has zero length.

I take it back. Since this approach doesn't reset the counter of requests between tests, this approach is safe. The worst that can happen is that a tests has to wait a bit longer because a pending promise from the previous test.

I used this fork and it's better, but not quite there yet. Before test failed, not they pass just ~50% of the time: https://github.com/cibernox/ember-native-dom-helpers/pull/48
My only guess is that there is a race condition. The only place where I can see that happening, and I hope I'm wrong because I won't see an easy solution.
My theory is that the promise from fetch resolves when the response starts comming back, but the resolved value (a Response object) might still be transmitting. You await for this stream of data by using reponse.json() or response.text(), all of which return another promise.
I suspect that if the data transfer is not fast enough, the waiter is going to continue and thats why tests fail intermittently.
I think that for fixing that we need to wait for the data transfer to finish (only in testing) and return a cloned response.
Untested pseudo javascript:
if (detectTestingEnvironment) {
  var pending = 0;
  if (Ember.default.Test) {
    Ember.default.Test.registerWaiter(function() { return pending === 0; });
  }

  function decrement(result) {
    pending--;
    return result;
  }

  self['default'] = function() {
    pending++;
    self.fetch.apply(self, arguments).then((response) => {
      response.clone().blob().then(decrement,decrement);
      return response;
    }, decrement);
  }
} else {
  self['default'] = self.fetch;
}

@stefanpenner Friendly ping

@cibernox thanks for the ping, it looks like the acceptance test (to ensure this works) is still missing. If that is added, I am good to 🚢

@cibernox thanks for the ping, it looks like the acceptance test (to ensure this works) is still missing. If that is added, I am good to 🚢

ping, if we can get a test here. I'll merge and release!

C**p, I forgot about this 😞
I'll try to get this done at some point today.

@cibernox Should this still work out of the box today? Anything special needed to wire things up? I'm having trouble getting my test to wait. (I'm seeing the registerWaiter call you added here, but the actual waiter that checks for pending === 0 never seems to be invoked.)

@samselikoff are you still having problems with it? I'm facing the same problem. I guess those issues are related: https://github.com/emberjs/ember-test-helpers/issues/477 and https://github.com/emberjs/ember-test-helpers/issues/347.

I haven't checked back on this, it was for some older work

I'm moving an ic-ajax based service to be ember-fetch (wrapper around fetch calls).  Got it working except for running into issues with tests not waiting. I've sprinkled a crap-ton of await settled() calls in my tests as a temporary workaround. So yeah, seems to still be a problem.
I just confirmed the problem in the 6.3.1 release.

Also note using latest ember-qunit (4.2.0) and ember-test-helpers (1.1.0).

It’s pretty unlikely that commenting here (long dead PR) will result in help...
Would you mind filing a new issue (hopefully with a reproduction) so we can try to figure out what’s going on?

I'm finishing up my last day of work before mid-January. Unlikely I'll be able to create a new issue with a reproduction before I sign-off for the break. If @viniciussbs doesn't beat me to it, I'll put something together when I return.


fix(sink)：Fix NATS publish returns feature's that don't execute

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
nats publish will return a feature

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Will be fixed in the next feature pr


Error related to pagination limit when join field is set.

Link to reproduction
No response
Environment Info
Node: 22.9.0
npm: 10.8.3
Yarn: 1.22.22
pnpm: 9.10.0
Relevant Packages:
payload: 3.0.0-beta.113
next: 15.0.0-canary.173
@payloadcms/db-mongodb: 3.0.0-beta.113
@payloadcms/graphql: 3.0.0-beta.113
@payloadcms/next/utilities: 3.0.0-beta.113
@payloadcms/richtext-lexical: 3.0.0-beta.113
@payloadcms/translations: 3.0.0-beta.113
@payloadcms/ui/shared: 3.0.0-beta.113
react: 19.0.0-rc-3edc000d-20240926
react-dom: 19.0.0-rc-3edc000d-20240926
Describe the Bug
Error: invalid argument to $limit stage: Expected a number in: $limit: "10"
Once pagination is set on the collection view, the page fails due to this error.
The limit and other arguments do not get set on the URL.
When i manually set a limit argument on the url eg "?limit=100", it prevents this error.
I don't think this error was present in beta 111.
Reproduction Steps
This occurs when there is a join field on the collection view being displayed.
Use the "per page" pagination, which subsequently should set the limit argument on the URL.
Adapters and Plugins
db-mongodb

This appears to be resolved in 114

Sorry, spoke too soon still seeing the issue.

@energee I am trying to follow but struggling to. Can you provide a screenshot of the view you are experiencing this in?

It seems like i can adjust the pagination but when i navigate to: /admin/collection/ and payload retrieves the limit from mongoDB, it fails (looks like its getting a string?)

I am also getting this error. It appears related to join field, as noted previously. For example: Collection_A with a join field to Collection_B that has a relationship field back to Collection_A will show this error.
"@payloadcms/db-mongodb": "3.0.0-beta.118",
 ⨯ node_modules/.pnpm/mongodb@4.17.1_@aws-sdk+client-sso-oidc@3.675.0_<EMAIL_ADDRESS>(231:1) @ Connection.onMessage
 ⨯ MongoServerError: invalid argument to $limit stage: Expected a number in: $limit: "10"
    at MessageStream.emit (node:events:519:28)
    at Socket.emit (node:events:519:28)
digest: "2508765017"
  229 |                 }
  230 |                 if (document.ok === 0 || document.$err || document.errmsg || document.code) {
> 231 |                     callback(new error_1.MongoServerError(document));
      | ^
  232 |                     return;
  233 |                 }
  234 |             }

Try to update to v3.0.0-beta.121 or later where #8913 is fixed. The error message seems the same.

From what I can see so far, it appears to be resolved, running beta.123

I'm still seeing thig even in v3.0.0-beta.124.
Error: invalid argument to $limit stage: Expected a number in: $limit: "100"
    at resolveErrorDev (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@15.0.0_babel-plugin-react-compiler@0.0.0-experimental-48eb8f4-20240822_react-dom@19.0.0-_olzgyrhn3cj6yjvy663zgvkzo4/node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-client.browser.development.js:1790:63)
    at processFullStringRow (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@15.0.0_babel-plugin-react-compiler@0.0.0-experimental-48eb8f4-20240822_react-dom@19.0.0-_olzgyrhn3cj6yjvy663zgvkzo4/node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-client.browser.development.js:2067:17)
    at processFullBinaryRow (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@15.0.0_babel-plugin-react-compiler@0.0.0-experimental-48eb8f4-20240822_react-dom@19.0.0-_olzgyrhn3cj6yjvy663zgvkzo4/node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-client.browser.development.js:2055:7)
    at progress (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@15.0.0_babel-plugin-react-compiler@0.0.0-experimental-48eb8f4-20240822_react-dom@19.0.0-_olzgyrhn3cj6yjvy663zgvkzo4/node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-client.browser.development.js:2258:17)

It works on one collection, but does not work on the other.

@HriBB you might want to try clearing out your payload-preferences table, it looks like the config is being sanitized on its way INTO the database so it won't go away until that is reset.

Thanks @energee! That solved the problem ;)


Fix bug in make images push

When we make images for service catalog project, execute
the following instructions "make images push", we find some
errors like "Error parsing reference:
"gcr.io/google-containers/debian-base-amd64:0.3 as base"
is not a valid repository/tag: invalid refe". It is a bug and
we do this patch.

This PR is a

[ ] Feature Implementation
[ ] Bug Fix
[ ] Documentation

What this PR does / why we need it:
Which issue(s) this PR fixes

Fixes #
Please leave this checklist in the PR comment so that maintainers can ensure a good PR.
Merge Checklist:

[ ] New feature

[ ] Tests
[ ] Documentation

[ ] SVCat CLI flag
[ ] Server Flag for config

[ ] Chart changes
[ ] removing a flag by marking deprecated and hiding to avoid
breaking the chart release and existing clients who provide a
flag that will get an error when they try to update

/assign @luksa

/hold
until someone figures out what's going on here

@MHBauer OK, thanks.

@viviyww What OS are you using?

@luksa Linux k8s-master 4.9.6-200.2.el7.bclinux.x86_64 #1 SMP Wed Mar 1 18:39:23 CST 2017 x86_64 x86_64 x86_64 GNU/Linux

And the file permissions on build/update-apiserver-gen.sh?
Here are mine:
$ ls -la build/
total 52
...
-rwxrwxr-x.  1 luksa luksa 4879 nov  6 08:51 update-apiserver-gen.sh
-rwxrwxr-x.  1 luksa luksa 3741 okt  9 07:59 update-client-gen.sh

Yes, that is true. I think it would be better if the script could do this automatically.

@viviyww Not sure what you mean. Your files should get those permissions automatically - when you check out the code from git. Is that not the case on your machine?

@luksa Yes, that is the case.

@luksa I am sorry. Maybe it is  the reason for my machine. I want to close this patch. Thank you for your review.


pyglove/backend.py: possible dependency on internal google vizier module?

While trying to use Vizier with PyGlove (and running into #1029 and #1030), I also noticed
https://github.com/google/vizier/blob/e9e1671ada5970cb20e9417eb0a4efd47e1f590c/vizier/_src/pyglove/core.py#L32
which causes my script to fail with a ModuleNotFoundError:
Traceback (most recent call last):
  File "/Users/connorbaker/Packages/ghc_hyperopt/./ghc_hyperopt/__main__.py", line 4, in <module>
    from vizier import pyglove as pg_vizier
  File "/Users/connorbaker/micromamba/envs/ghc_hyperopt/lib/python3.11/site-packages/vizier/pyglove/__init__.py", line 20, in <module>
    from vizier._src.pyglove.oss_vizier import init
  File "/Users/connorbaker/micromamba/envs/ghc_hyperopt/lib/python3.11/site-packages/vizier/_src/pyglove/oss_vizier.py", line 32, in <module>
    from vizier._src.pyglove import backend
  File "/Users/connorbaker/micromamba/envs/ghc_hyperopt/lib/python3.11/site-packages/vizier/_src/pyglove/backend.py", line 31, in <module>
    from vizier._src.pyglove import client
  File "/Users/connorbaker/micromamba/envs/ghc_hyperopt/lib/python3.11/site-packages/vizier/_src/pyglove/client.py", line 28, in <module>
    from vizier._src.pyglove import pythia as pg_pythia
  File "/Users/connorbaker/micromamba/envs/ghc_hyperopt/lib/python3.11/site-packages/vizier/_src/pyglove/pythia.py", line 29, in <module>
    from vizier._src.pyglove import core
  File "/Users/connorbaker/micromamba/envs/ghc_hyperopt/lib/python3.11/site-packages/vizier/_src/pyglove/core.py", line 32, in <module>
    from vizier.google import metadata_to_user
ModuleNotFoundError: No module named 'vizier.google'

The dependency was introduced as part of https://github.com/google/vizier/commit/bf576cdcedf1abcae948668b1e11d50afa4170ae, but I can't find it anywhere in the source tree.
Any suggestions?

Thank you for the bug report, fixed in https://github.com/google/vizier/pull/1032
Best,
Sagi


Add Objective-C support to extension of FileManager

Fixes #
Package is impossible to use in mix Swift-Objective-C projects without writing some kind of wrapper.
Making whole package Objective-C compatible seems to be a big rework.
But (NS)FileManager is Objective-C class and it sounds reasonable if methods of its extension will be available to be used from Objective-C.
This PR proposes minor changes needed to make extension of FileManager available for Objective-C.
Changes proposed in this PR
Makes following methods of FileManager extension available from Objective-C

zipItem(at sourceURL:to:shouldKeepParent:compressionMethod:progress:)
unzipItem(at:to:skipCRC32:progress:preferredEncoding:)

Tests performed
If in general this PR would be accepted, I will add tests for new added methods.
Further info for the reviewer
n/a
Open Issues
n/a

If in general this PR would be accepted, I will add tests for new added methods.

I don't have plans to add Obj-C support to the framework. If people want to use ZIP Foundation from a mixed Obj-C/Swift codebase, they can wrap ZIP Foundation on the call site.


up prune doesn't appear to prune different stages

I have two stages: production & staging.
Run:
up prune
Bug?
Doesn't appear to do anything at all. I even tried up prune staging. Nada.

It does both at the same time currently, but I thinkkkk you're right, having some granular control there would be good!

Oh, ha ha that's not even what I was suggesting, but I do like that. 👍
I was just saying that up prune doesn't appear to work for me:
» up version
0.6.1-pro
» up prune
     prune: 0 old files removed from S3 (0 B) (1.824s)

When I take a peek in the S3 bucket, all the prior zip files are still there.

I only have one up bucket, and it's in the newer format (removed the #s): up-xxxxxxxxxxxx-us-east-2.
I'm going to try something drastic and rename the whole bucket though. See if it starts behaving with a new bucket.

Update: starting fresh solved nothing. I'm still getting prune: 0 old files removed from S3 (0 B) (1.549s) and I know there are (currently) 9 zip files in the staging S3 folder and 4 in the production folder.

Ah. Gotcha. Makes sense.

Pretty arbitrary number right now hahah.. but the price of retaining 60 should be pretty negligible, definitely open to tuning the default though

8c3ed9572e changes that behaviour a bit since it targets the specific stage, but that'll be in the next release

Yeah, the Lambda is still there, so it didn't entirely blow up. Thanks for setting a default and hanging in there with me on this. 👍


=colwidth and =colalign should allow arbitrary whitespace between arguments

Today we require eg =colwidth 1 2 3 4 5 6 7 8 but it is useful when writing a table spec to be able to write eg =colwidth 1 2 3 4 5   6 7 8 where the column specs are in groups of 5.
Experience tells me this is useful with counting column specs.
So we just need to turn multiple spaces into one - when parsing =colwidth and =colalign.

Done and merged.


Fix group entity API inconsistency with async_update

Fixes: https://github.com/home-assistant/core/issues/123472

So that’s why we had update() before for groups 😄

I knew I had a reason when I changed it... LOL


Active Pilots List

Post CREST / ESI integration  ( see #162 ) the 'Active Pilots' list is inaccurate. It will list a pilot as active when they are also docked or offline. Which obviously isn't true.
To check for docked pilots check if the structure_id or station_id optional field is returned in the ESI location API request. If they are present then it means the pilot is not in space and should not be displayed as being active.  It could be possible to look up the structure / station IDs and display them as docked (and where they are docked) instead.
The ESI location API still returns a valid location if the pilot isn't even logged into the game and places them in the Active Pilots List. However the CREST location API does not return any data if the pilot is offline. Thus a CREST location API check needs to be done to find out if a pilot is online or not

Even when you are logged off in space you get that person on the active pilot list. There is a feature request on the ESI github to cover this in the future.

If you have been in space then dock, your active pilot status isn't removed.

It is after 5 min. :)

Oh in the state_locations celery job. I see! I guess I just wasn't being patient enough. :)

It was a quick fix, the caching of 5 min should also be handled differently when ESI is more stable. It could probably go down to 1 minute (just in case it fails one of the tasks).

If you have mapped out a high sec system (eg our home wormhole has a B274 Static) then if you dock up in a station in that mapped high sec system then you don't get removed from the active pilots list. This is because the ESI API doesn't return a structure_id for this situation. It returns a station_id instead.
{
  "solar_system_id": 30001650,
  "station_id": 60009298
}

Fixed.


Making Content browser aware of context

Fixes #1674

@plone/volto-team this is something that our clients asked for a lot. What is your experience here? Are you ok with merging this and starting the content browser in the current location/context instead of on the root?

I'm very much ok with it.


Adding instructions for those with neither an application nor a tenant role

There have been some who have had an account but currently have no tenant status. For them, the instructions do not show up, because those are displayed only to those who have a tenant status but with a tenant_until field in the past.
There, we could display two options: one to request tenant status again and one which redirects to the application form. WDYT?

Can you test registering as tenant and check the gotten roles?

Hm... they do get a tenant role, with tenant_until set to the appropriate date.
But you are right the approach itself is flawed; I'll close this as per #604. See #609 for the new issue.


Is it possible to retrieve stddev with a query in a TICKScript?

Hi everyone, i'm very new to the tick stack and I'm struggling with a problem. i've developed a software which reports wrong dns queries done by hosts in a LAN and im monitoring it with TICK (no Telegraf, didn't need it). I've set an alert rule which notifies me on Telegram every time a new value greater than 4 is put in influxdb. Everything seems to work except that "4" was a value decided by me in order to test things: i'd like to replace is with the stddev of the last 5 minutes of data in my db.
This is the TICKscript: https://hastebin.com/hecixajisu.php
I tried to use a query while configuring the alert but it seems that Kapacitor only accepts integer or reals as thresholds. I hope someone can help me or I'll have to change everything about this project :disappointed:

up

@greasy-sandwich hey man, I can't see your script as hastebin was acquired by someone and they changed their api, can you paste a copy here?


General noise simulation

Implementation of Sec. 3.1 of the design doc (exact arbitrary operator-sum noise), with the general interface of Sec 2, plus some deep-bug fixes

@chriseclectic this is operator-sum noise interface and implementation. Will you do the merge here? @smolinIBM @jaygambetta

@yaelbh we need to put this on hold or even close this PR. There are a few issues.

I would like the bug fixes pulled out into their own PR or possible PRs following the contribution guidelines.
The extensions should be discussed in the qiskit.slack.org channel on simulators and we should plan how to make the merge with the simulator.

Thanks

Thanks, will close the PR then.


Leaderboard

Hello,
This is a request for a new feature.
It would be nice to have a leaderboard functionality based on different criteria, by country for example.
@QuincyLarson
Thanks!

@seifsg there is actually a leaderboard project as part of the DataViz projects that determines ranking by brownie points. With the move the the forum, however, it is less accurate and does apply at the country-level.
https://codepen.io/freeCodeCamp/full/eZGMjp

@dhcodes I meant a tab or some official page to the FCC project itself.
Plus the points system is a bit unfair to those who only want to go for starred map items.
So what I meant is a leaderboard system integrated within the FCC site that counts, for example, the people who finished all certificates or countries with most campers etc..

@seifsg Thanks for explaining. Would you like to build a prototype?

@dhcodes Yes. But I still don't know so well on how to properly contribute. Are there any restrictions on delivery time?

Sounds good a internal ranking.

Hi, @seifsg
However interesting this might sound, we will not have a leaderboard, due to a policy.
We DO NOT encourage competition via the UX of the platform
That's because most users are new to programming, while it may sound great to have a competing page where you can see who is leading, it's often daunting for newcomers.
Also, any such system can be fooled into motivated rewarding of points. Again a behavior that we would not encourage.
So, to summarize that platforms sole motive is to provide a medium to learn to code for free without distractions of competing. This is very important because of the ideology that we have.
Thanks once again for your valuable time and interest.
Happy coding!

@seifsg As @raisedadead said, we want to encourage cooperation, rather than competition. This said, you're welcome to create a stand-alone leaderboard system, for the campers who are interested in competing.
We hope to launch an open API in 2018 that will make this much easier to build and maintain.


For Friday presentation

[ ] Absorption/"fate" - should pulse only once, but each time an absorption happens. Should happen when measurement happens, which is not always at the end of the level
[ ] Play button - remove from encyclopedia mini boards,
[x] Play button - remove hint circle around the button
[ ] Bomb - it shouldn't always explode, should depend on the measurement
[x] Goals - fix - goals donut doesn't update
[ ] Transition matrix - add legend + style
[x] Graph - fast redesign for the purpose of Friday presentation
[x] Encyclopedia landing page - for chrome
[ ] "Dark" mode - for when the photon is moving on the board

A nice moment to look at the past. Now, let's move on. :)


Standardise contribution tags

Standardises

all contribution tags to dcterms
all orcids to IRIs

This seems fine to me. Can I merge? Should I wait?

@matentzn @gopi-kris I also added branch protection rules for main.

Good to merge


Fix setting incorrect active scene

Active scene is no longer set to an incorrect value when opening a scene.

SonarQube analysis reported 1 issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)


The precision of double serialization

I use this package with Microsoft Web API2. When serialize a C# double (64bit) to json, and convert the json back to javascript double (64bit), I find there will be precision loss. Anything I can configure there?

The documentation has information about float parsing options.

Do you mean this one?
http://www.newtonsoft.com/json/help/html/T_Newtonsoft_Json_FloatParseHandling.htm
I did not find others, will you please give more hints?
thanks.
On Wed, Sep 30, 2015 at 10:40 AM, James Newton-King <
<EMAIL_ADDRESS>wrote:

The documentation has information about float parsing options.
—
Reply to this email directly or view it on GitHub
https://github.com/JamesNK/Newtonsoft.Json/issues/666#issuecomment-144263547
.

Hi, I just come across this issue which is also a problem for me now. that is, always parsing numeric float string into either decimal or double will lead to precision loss. ideally I would expect the JsonTextReader to return decimal/double/long whichever can fit best. for example:
(1) decimal.MaxValue string should be automatically parsed as decimal not double:
decimal.Parse("79228162514264337593543950335",NumberStyles.Float, NumberFormatInfo.InvariantInfo)  - correct parsing, has all the precision
79228162514264337593543950335
double.Parse("79228162514264337593543950335",NumberStyles.Float, NumberFormatInfo.InvariantInfo)
7.9228162514264338E+28
(2) double.MaxValue string should be automatically parsed as double not decimal:
decimal.Parse("1.7976931348623157E+308",NumberStyles.Float, NumberFormatInfo.InvariantInfo)
throws 'System.OverflowException'
double.Parse("1.7976931348623157E+308",NumberStyles.Float, NumberFormatInfo.InvariantInfo)    - correct parsing, only double can hold this big number.
1.7976931348623157E+308
so a better approach to me is to do long.TryParse(...), if failed then decimal.TryParse(...), if failed again then double.Parse(...), and the latter two can be selected by a .FloatParseHandling setting.
@JamesNK  can you comment on this? I can start working on a PR as needed.

PR: #884

Sorry I disagree with this. The user is asking for a decimal. Getting a double when the value gets too large is more surprising than getting an error message saying the value is now too large.
I think in cases like this you should just deserialize to a string and then process it using your own rules. I'll re-purpose your test to make sure that this possible.

Done https://github.com/JamesNK/Newtonsoft.Json/commit/81098652b37266bf7ed29d8c1e86c270ae18b79d

@JamesNK  thank you. In some other scenarios where user is unable to predict the numeric value & call ReadAsString(), I think the important thing is to read the accurate value out (no matter as decimal or as double, and with as much precision as possible) , then let user do further processing. so do you think this feature request is valid?
Based on that, I have reverted the previous change, then add Json.FloatParseHandling.Auto for trying decimal precision first and fallback to double if needed. it is the same PR: #884

@JamesNK  the scenario I am seeking to solve is reading arbitrary JSON with as high precision as possible by calling Read() not ReadAsString()  (I can explain more about this feature request if needed), the below are 2 examples, looking forward to support of this.  so can you evaluate this PR?  #884   / 8d14715b13b7c57e30daf82342942c9089c1e461  .
"{"amountValue": 1.7976931348623157E+308}"   (result value has to be double)
or
"{"amountValue":<PHONE_NUMBER>42643375935439503.35}"     (result value has to be decimal)

So, I have annoying old good issue with json and floats. I need to deserialize raw binary data, then serialize into JSON for editing then serialize into binary again. Obviously, I lose on floats. Value 0xF9FF4FC1 (big endian, roughly -12.9999933) gets rounded to 0xF6FF4FC1 ("-12.99999"). I know it is not a big loss and I know floats are little shits but I want to keep the precision as close as possible due to possibly incompatibility issues later. Anyone tackled this problem before with JSON?
Yes, I've tried built in option for handling floats but there is no difference in output unfortunately.


UpdateObject function should operate on a deepcopy of the object

What steps did you take and what happened:
the UpdateObject (and maybe createObject too) functions in metal3machine_manager.go (branch release-0.3) should operate on deepcopies of the object. Using the object directly translates into a lost status.

Cluster-api version: 0.3.2
CAPBM version: 0.3.0

/kind bug

This should be fixed both in master and in branch release-0.3

How was the 'lost status' detected?
Is there a test case that reproduces this problem?

it was detected in the metadata implementation phase. There is no test case that tests this, but you could add one on the updateObject function. Calling the function with an object with the status , after the call the object should retain its status.


[Bug] Cannot disable suggestions for only one editor on page

Reproducible in vscode.dev or in VS Code Desktop?

[ I don't know ] Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

[ ] Not reproducible in the monaco editor playground

Monaco Editor Playground Code
const container1 = document.createElement('div');
const container2 = document.createElement('div');
const style = 'height: 200px; border: 1px solid #000; margin: 10px;';
container1.setAttribute('style', style);
container2.setAttribute('style', style);
document.body.appendChild(container1);
document.body.appendChild(container2);

// basic editor #1
monaco.editor.create(container1, {
	value: '/* suggestions are not working here */\n<Item type="Test1" id="512FF7893DBCD6D1AC1F55B87A480934">\n</Item>',
	language: 'xml'
});

// read only editor #2
monaco.editor.create(container2, {
    value: '/* read only editor */\n<Item type="Read Only Editor">\n\n</Item>',
    language: 'xml',
    readOnly: true,
    suggest: {
        showFields: false,
        showFunctions: false
    },
    quickSuggestions: {
        "other": false,
        "comments": false,
        "strings": false
    },
    parameterHints: {
        enabled: false
    },
    ordBasedSuggestions: false,
    suggestOnTriggerCharacters: false,
    acceptSuggestionOnEnter: "off",
    tabCompletion: "off",
    wordBasedSuggestions: false
});

Reproduction Steps
Call suggestions dialog at first editor
Actual (Problematic) Behavior
There is always "No suggestions"
Expected Behavior
Suggestions dialog works and displays and includes only keywords from current editor.
Additional Context
I have two editors on page and I need to split suggestions for them. Keywords for each editor should be taken separately.
As a workaround I tries to disable editing and all suggestions options for the second editor. But these options also applies for the first editor. It's unexpected.
Do anyone has idea how to split suggestions keywords between each editor? Or maybe to leave only code highlighting for the second one.
P.S. There is a service where user inputs XML request (should be with IntelliSense) in first monaco editor and after request user should see highlighted XML response in second editor (this one can be stupid - without editing, suggestions etc.)

same problem for me.
when I create multiple monaco instances and add different suggestions for them, they will be mixed up and some will show up multiple times.
It seems that all monaco instances will interact with each other, any ideas?


feat: Duplicate Check for Registered Data Validator

Duplicate Check for Registered Data Validator using QueryDataValidator in Panacea.
It checks duplication when the dataval start.

When you merge this PR to the main, please rename the title from Duplicate Check to Duplication Check. The duplicate check means the double-checking which checks something twice for safety.

Modify Cosmwasm .so file in Dockerfile based on panacea-core Dockerfile.

This branch was rebased from main branch.
Close #65 as we discussed.
Restore the docker-compose.yml because registering the data validator will be performed manually.


support dotenv

It would be easier and more developer friendly to use .env file to configure that long list of environment variables yea?

@murugaratham thanks for the contribution! I'll try to release this over the next few days


create necessary lib/ files on install, fixes #16

adds aposinstall script to create the necessary but gitignore'd lib/index.css and lib/generate-theme.scss files.

@brenna found a workaround here! Thanks for catching this


Kodi checker rework

1. Tell us something about your changes.
kodichecker rework

use new logger
'enable' flag in config
startable, stoppable and reconfigure on runtime
rename xbmc to kodi

2. If this changes affect the .conf file. Please provide the changed section
now xbmc is kodi:
 	"kodiVideoChecker" :
 	{
 		"enable" : true,
 		"kodiAddress" : "<IP_ADDRESS>",
 		"kodiTcpPort" : 9090,
 		"grabVideo" : true,
 		"grabPictures" : true,
 		"grabAudio" : true,
 		"grabMenu" : false,
 		"grabPause" : false,
		"grabScreensaver" : true,
 		"enable3DDetection" : true
},

3. Reference a issue (optional)
Note: For further discussions use our forum: forum.hyperion-project.org

nice work!
Could you add the enable flag to our commented and default .json? Then it is complete. :)
Don't think to hard about the json checker schema, Paulchen-Panther reworked this already.

I just do that ;-)

Aww what is this?
libsrc/effectengine/EffectDefinition.schema.json
A copy of the json checker schema? Delete?

let us think about schema defs later. There is some work todo.
config is updated.

Thank you, i just saw this schema and now i am confused why we have it 2 times ;)
But as already pointed out from Paulchen, the result of the checker is never used to output something (like a warning) so this is just another point at the long list of boring todos :)

just for tracking
https://github.com/hyperion-project/hyperion.ng/issues/3

and #25


Add optional instructions field to the Add-On

Part of https://github.com/MuckRock/documentcloud-frontend/issues/314

@duckduckgrayduck heads up I invited you to be a collaborator in this repo so you can merge PRs if changes are needed.


Union and intersection of two arrays

Description
Union and intersection of two arrays
Domain
Standard Template Library
Type of Contribution
Addition
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of LearnCPP.

i would like to work on it under Gssoc22


Battery icon animation

The battery icon now reflects the real state of the battery charge transforming the battery SVG icon.

Hey @NickTikhonov how are these PRs going?

Hey @davegomez - It's been a busy few weeks, I'll definitely take a look at everything tomorrow :)

Cool 👍 Merging.


Use new way to query dtTwin's relationships

@mahkoCosmo Could you please add the issue number (PROD-7683) to the commit message as well? Thanks.


fixes #1095: changed dimens.xml and the consequent layout files

made changes to the dimens.xml.

@arp95
for changes like this, always post screenshots of old layout vs new layout.

@championswimmer sure sir. Actually i just replaced the old values with the new items in dimens.xml so felt no need of that.
Will take care of it in future.


How do I load source maps from ng-serve?

I am trying to debug a standalone Angular CLI project. After running ng-serve, opening the browser, navigating to the webpage and attaching the debugger, breakpoints are not being bound.
If I add a "debugger" statement in the code, VS does actually break, but instead of breaking in whatever typescript file I addded the statement in, it breaks in "main.js [dynamic]" and I can step through this code without problems, but it still won't bind to breakpoints in typescript files.
Edge dev console correctly shows the breakpoint.
This is a standalone Angular CLI project and not some ASP project. I simply opened the folder in Visual Studio. There is no project (.csproj) or solution (.sln) and I'd like it to stay that way.

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

ID: dbb9adca-2c5c-edff-2c4e-4645579fb907
Version Independent ID: 85cade65-f1b0-61d4-c69e-fb8ca94fefed
Content: Debug a JavaScript or TypeScript app - Visual Studio
Content Source: docs/javascript/debug-nodejs.md
Product: visual-studio-windows
Technology: vs-javascript
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@tudor-vlad -- thank you for your well-researched feedback.  This repo is solely for documentation issues, and this appears to be product-related.  Please consider adding your concern here:

Report product issues to us via the Report a Problem tool that appears in the Visual Studio IDE.
Suggest a feature, track product issues, and find answers in the Visual Studio Developer Community.

Here are some Visual Studio resources:

Visual Studio on Q&A
Visual Studio MSDN Forum
Stack Overflow
Reddit

I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.
cc @Mikejo5000 for awareness


Clear button is not accessible

Hello, we discovered that clear button which appears when allowClear property used is not accessible due to 2 reasons:

button wrapper uses tabindex=-1 which makes it inaccessible through the keyboard using tab/shift+tab
button wrapper uses span tag which prevent to click it via space or shift when it is on focus

I opened PR to fix this and added tests to check behavior, could you check it please
https://github.com/react-component/input/pull/63

Fixed in https://github.com/react-component/input/pull/63


Obsoletion request: GO:0008153  para-aminobenzoic acid biosynthetic process

Please provide as much information as you can:

GO term ID and Label

GO:0008153  para-aminobenzoic acid biosynthetic process
The chemical reactions and pathways resulting in the formation of para-aminobenzoic acid, an intermediate in the synthesis of folic acid, a compound which some organisms, e.g. prokaryotes, eukaryotic microbes, and plants, can synthesize de novo. Others, notably mammals, cannot. In yeast, it is present as a factor in the B complex of vitamins. PMID:11377864 PMID:11960743

Reason for deprecation Put an x in the appropriate box:

[ ] The reason for obsoletion is that the data from the paper for which the term was requested can be accurately described using [appropriate GO term].

I'm picking up IBA mappings to this term, but it seems to be describing an intermediate according to the definition? I annotated only to
GO:0046656 | folic acid biosynthetic process

[ ]  The reason for obsoletion is that this term was added in error.

"Replace by" term (ID and label)
If all annotations can safely be moved to that term

"Consider" term(s) (ID and label)
Suggestions for reannotation

Are there annotations to this term?

How many EXP:

Are there mappings and cross references to this term? (InterPro, Keywords; check QuickGO cross-references section)

Is this term in a subset? (check the AmiGO page for that term)

Any other information

Checklist for ontology editor
Check term usage and metadata in Protégé

[ ] check term usage in the ontology
[ ] check internal mappings: RHEA, EC, MetaCyc
[ ] check subset usage
[ ] check taxon constraints

Check annotations

[ ] create Annotation Review spreadsheet

Annotation Review template: https://docs.google.com/spreadsheets/d/1izV3q1jnq_Ybg5MJ53O_b5BCTkGtjl_Fi-cOg3-7eBE/edit#gid=0

Instructions: https://wiki.geneontology.org/Annotation_Review_Request

[ ] create annotation review ticket: https://github.com/geneontology/go-annotation/issues/new?assignees=&labels=annotation+review&template=annotation-review-for-obsoletion.md&title=Review+annotations+to+[INSERT+GO+TERM]
[ ] find external mappings (via IEAS), include in obsoletion notice
[ ] tag curators in Annotation Review ticket. Responsible annotator for each group: https://github.com/geneontology/go-site/blob/master/metadata/group-contacts.csv

Notification

[ ] create obsoletion announcement
[ ] announce to GO friends<EMAIL_ADDRESS>[ ] paste the text in the ontology ticket

I don’t get the rationale
It’s a distinct pathway? The product of the pathway could feed into other
pathways… but that’s true of many more?
https://biocyc.org/META/NEW-IMAGE?type=PATHWAY&object=PWY-6543
On Thu, Feb 1, 2024 at 5:42 AM Val Wood @.***> wrote:

Please provide as much information as you can:

GO term ID and Label

GO:0008153 para-aminobenzoic acid biosynthetic process
The chemical reactions and pathways resulting in the formation of
para-aminobenzoic acid, an intermediate in the synthesis of folic acid,
a compound which some organisms, e.g. prokaryotes, eukaryotic microbes, and
plants, can synthesize de novo. Others, notably mammals, cannot. In yeast,
it is present as a factor in the B complex of vitamins. PMID:11377864
PMID:11960743

Reason for deprecation Put an x in the appropriate box:

The reason for obsoletion is that the data from the paper for which
the term was requested can be accurately described using [appropriate GO
term].

I'm picking up IBA mappings to this term, but it seems to be describing an
intermediate according to the definition? I annotated only to
GO:0046656 | folic acid biosynthetic process

The reason for obsoletion is that this term was added in error.

"Replace by" term (ID and label)
If all annotations can safely be moved to that term
"Consider" term(s) (ID and label)
Suggestions for reannotation
Are there annotations to this term?

How many EXP:

Are there mappings and cross references to this term? (InterPro,
Keywords; check QuickGO cross-references section)
Is this term in a subset? (check the AmiGO page for that term)
Any other information

Checklist for ontology editor
Check term usage and metadata in Protégé

check term usage in the ontology
check internal mappings: RHEA, EC, MetaCyc
check subset usage
check taxon constraints

Check annotations

create Annotation Review spreadsheet

Annotation Review template:
https://docs.google.com/spreadsheets/d/1izV3q1jnq_Ybg5MJ53O_b5BCTkGtjl_Fi-cOg3-7eBE/edit#gid=0

Instructions:
https://wiki.geneontology.org/Annotation_Review_Request

create annotation review ticket:
https://github.com/geneontology/go-annotation/issues/new?assignees=&labels=annotation+review&template=annotation-review-for-obsoletion.md&title=Review+annotations+to+[INSERT+GO+TERM]
find external mappings (via IEAS), include in obsoletion notice
tag curators in Annotation Review ticket. Responsible annotator for
each group:
https://github.com/geneontology/go-site/blob/master/metadata/group-contacts.csv

Notification

create obsoletion announcement
https://github.com/geneontology/go-announcements/issues/new?assignees=&labels=obsoletion&template=obsoletion-notice.md&title=Obsoletion+notice%3A+[GO+ID%3A+term+label]
announce to GO friends @.***)
paste the text in the ontology ticket

—
Reply to this email directly, view it on GitHub
https://github.com/geneontology/go-ontology/issues/26927, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMMOKNU6TKO37A6WZVBFDYROLTVAVCNFSM6AAAAABCU5UYIGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEYTENJUHE4DAOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I hadn't looked in detail yet but I'm basing on

says intermediate in the def (we don't include pathway intermediates for linear pathways)
The only thing annotated to this seems to be  "para-aminobenzoate synthase" so it seems to be a single step in a linear pathway to folic acid, will double check this

It's the left hand branch here.

@deustp01  will probably know if this goes anywhere else other than folate....

@deustp01 will probably know if this goes anywhere else other than folate

No such luck. Here is a PubMed citation suggesting that it can be metabolized but we don't have any annotations - our relevant ones start with uptake of dietary folate, derived from organisms that can synthesize it.

I can't find any evidence that PABA is used for anything other than folate biosynthesis and onwardly for tetrahydrofolate,  so it does seem to be an intermediate in a linear pathway.
However, it seems that humans can make PABA but not folic acid (they are missing the conversion enzyme), which implies there is another role for PABA?

However, it seems that humans can make PABA

I don't know of any evidence for this (which definitely is not proof it doesn't happen). Wikipedia describes its synthesis by human gut organisms, so we could get it from there -

4-Aminobenzoic acid - Wikipedia
PABA is an intermediate in the synthesis of folate by bacteria, plants, and fungi. Many bacteria, including those found in the human intestinal tract such as E. coli, generate PABA from chorismate by the combined action of the enzymes 4-amino-4-deoxychorismate synthase and 4-amino-4-deoxychorismate lyase.

https://biocyc.org/compound?orgid=META&id=P-AMINO-BENZOATE#RXNS
various other end-products there

ok thanks
not to self ubiquinol-6 biosynthesis from 4-aminobenzoate (yeast)

It seems like Para-Aminobenzoic Acid may have a physiological role?
https://pubmed.ncbi.nlm.nih.gov/34607467/
Also about intermediates, we need to be careful to check that it's not a branch point; in this case the term could be useful.

It is a branch point, in yeast for ubiquinol-6 biosynthesis and folic acid

It is a branch point, in yeast for ubiquinol-6 biosynthesis and folic acid

OK, better to keep it


URGENCY HIGH - Change email layouts

I would also like to change the look of our reply email please because when I saw hers I noticed it needs to look more professional. How can we adjust the look?

Hire a designer for Sendgrid.


Attendee could have no status from Api payload

Sometimes, an attendee can have no Status key.
An example is visible from MSDN here:
https://msdn.microsoft.com/office/office365/APi/calendar-rest-operations#Createevents

updated @Taluu

Thanks @krichprollsch

Could you add a tag plz @Taluu ?


Ref docs issue

Error:

##[error]  WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None))': /packages/47/03/333a691759ffda85006f8fd660dbcfdbcdb46cf2873391d3643d4b03e6cf/azure-loganalytics-0.1.1.zip

For more details check here:

https://apidrop.visualstudio.com/Content CI/_build/results?buildId=308387&view=results

@danieljurek for notification.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.4329647,Storage:0.10891231,Service Bus:0.035702817'

@danieljurek I guess you may have the context?

Thanks for the notification. This looks like a transient issue that has been resolved since Saturday. Closing.


Remove Developer Menu from RELEASE builds

Removed using compiler conditions
Made DMDeveloperMenu class not available for RELEASE builds

Looks good to me – I tested it and it works.
Let's wait with the merge until we got word that the developer menu is no longer needed.

Let's do that after the evening release.


[release-v0.53.x] Fix: Identify workspace usage in a Task

Manual cherry-pick of https://github.com/tektoncd/pipeline/pull/8016 to resolve errors.
Changes

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[x] Has Tests included if any functionality added or changed
[x] pre-commit Passed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
Fix: Identify workspace usage in a Task

/kind bug

/assign @vdemeester

@chitrangpatel can you change a bit the 2nd commit message or squash ? 🙏🏼 I also renamed the pull-request to be a bit more… informative 😛

Thanks! Done!


Spurious failure with "request was unmatched by any stub matching" since upgrade to WireMock 2.9.0

Without changing any of our own code, updating from WireMock 2.8.0 to 2.9.0 causes many tests to fail with spurious "unmatched request" errors.
Example test:
@Test
public void testAuditLogRequestHeader() throws Exception
{
    callingOurStuffHere();
    verify(postRequestedFor(urlEqualTo("/1/team/log/get_events"))
               .withHeader("Authorization", WireMock.equalTo("Bearer " + TOKEN))
               .withRequestBody(equalToJson("{}")));
}

Failure text:
com.github.tomakehurst.wiremock.client.VerificationException: A request was unmatched by any stub mapping. Request was:

	at com.github.tomakehurst.wiremock.client.VerificationException.forUnmatchedRequests(VerificationException.java:92)
	at com.github.tomakehurst.wiremock.junit.WireMockRule.checkForUnmatchedRequests(WireMockRule.java:90)
	at com.github.tomakehurst.wiremock.junit.WireMockRule.access$000(WireMockRule.java:34)
	at com.github.tomakehurst.wiremock.junit.WireMockRule$1.evaluate(WireMockRule.java:74)
	at com.acme.common.test.rules.BaseTestRule$1.evaluate(BaseTestRule.java:45)
	at com.acme.common.test.rules.BaseTestRule$1.evaluate(BaseTestRule.java:45)
	at com.acme.common.test.rules.BaseTestRule$1.evaluate(BaseTestRule.java:45)
	at com.acme.common.test.rules.BaseTestRule$1.evaluate(BaseTestRule.java:45)
	at com.acme.common.test.rules.BaseTestRule$1.evaluate(BaseTestRule.java:45)
	at com.acme.common.test.rules.Timeout$CustomFailOnTimeout$StatementRunner.run(Timeout.java:137)
	at java.lang.Thread.run(Thread.java:745)

The odd thing is how it doesn't actually print out anything...
This appears to occur consistently for tests using verify(postRequestedFor(...)) but tests using stubFor(post(...)) still pass.

LOL, well... I guess this answers the last part of the question:
{noformat}
return new VerificationException(String.format("A request was unmatched by any stub mapping. Request was: ",
unmatchedRequests.get(0)));
{noformat}

Extra strangeness, I breakpointed in the place where it was throwing the error, and evaluated:
WireMock.postRequestedFor(WireMock.urlEqualTo("/1/team/log/get_events"))
        .withHeader("Authorization", WireMock.equalTo("Bearer [token redacted]"))
        .withRequestBody(WireMock.equalToJson("{}"))
        .build()
        .match(unmatchedRequests.get(0))
        .isExactMatch()

This returns true... so the request did match, but was on the list of unmatched requests for some reason.

Did it do this consistently or intermittently? Could you supply a full test case that replicates this?

I'm working at removing both our framework and Dropbox's API from the picture but it's taking a while. It happens every single test run, though, so I expect it to be fully reproducible. Problem is, I might end up with a test case which, although standalone, still contains our real credentials to connect to Dropbox. :|

Here's where we are so far. I redacted the token out but I've removed all instances of the Dropbox library itself and it's still getting the same unmatched result.
import java.io.IOException;

import com.github.tomakehurst.wiremock.core.WireMockConfiguration;
import com.github.tomakehurst.wiremock.junit.WireMockRule;
import org.apache.commons.io.input.ProxyInputStream;
import org.apache.http.HttpHost;
import org.apache.http.client.methods.CloseableHttpResponse;
import org.apache.http.client.methods.HttpPost;
import org.apache.http.conn.routing.HttpRoute;
import org.apache.http.conn.ssl.NoopHostnameVerifier;
import org.apache.http.conn.ssl.TrustSelfSignedStrategy;
import org.apache.http.entity.ContentType;
import org.apache.http.entity.StringEntity;
import org.apache.http.impl.client.CloseableHttpClient;
import org.apache.http.impl.client.HttpClientBuilder;
import org.apache.http.message.BasicHeader;
import org.apache.http.ssl.SSLContexts;
import org.junit.Rule;
import org.junit.Test;

import static com.github.tomakehurst.wiremock.client.WireMock.*;

public class TestWiremockIssue
{
    @Rule
    public final WireMockRule wireMockRule = new WireMockRule(WireMockConfiguration.wireMockConfig().httpsPort(8443));

    private static final String TOKEN = "[REDACTED]";

    @Test
    public void testAuditLogRequestHeader() throws Exception
    {
        codeUnderTest();

        verify(postRequestedFor(urlEqualTo("/1/team/log/get_events"))
                   .withHeader("Authorization", equalTo("Bearer " + TOKEN))
                   .withRequestBody(equalToJson("{}")));
    }

    Object codeUnderTest() throws Exception
    {
        HttpPost request = new HttpPost("https://api.dropbox.com/1/team/log/get_events");
        request.addHeader(new BasicHeader("Authorization", "Bearer " + TOKEN));
        request.addHeader(new BasicHeader("Content-Type", "application/json"));
        request.addHeader(new BasicHeader("Accept", "application/json"));
        request.setEntity(new StringEntity("{}", ContentType.APPLICATION_JSON));
        request.removeHeaders("Content-Length");

        CloseableHttpClient httpClient = createClient();
        CloseableHttpResponse response = httpClient.execute(request);

        if (response.getStatusLine().getStatusCode() == 200)
        {
            return new ProxyInputStream(response.getEntity().getContent())
            {
                @Override
                public void close() throws IOException
                {
                    super.close();
                    response.close();
                    httpClient.close();
                }
            };
        }
        else
        {
            return null;
        }
    }

    private CloseableHttpClient createClient() throws Exception
    {
        return HttpClientBuilder.create()
                                .disableAuthCaching()
                                .disableAutomaticRetries()
                                .disableCookieManagement()
                                .disableRedirectHandling()
                                .disableContentCompression()
                                .setSSLContext(SSLContexts.custom().loadTrustMaterial(null, new TrustSelfSignedStrategy()).build())
                                .setSSLHostnameVerifier(NoopHostnameVerifier.INSTANCE)
                                .setRoutePlanner((httpHost, httpRequest, httpContext) ->
                                                     new HttpRoute(new HttpHost("localhost", 8443, httpHost.getSchemeName())))
                                .build();
    }
}

Should note that I've tried to remove Commons HTTP from the code a couple of times, and each time it resulted in a different error, and I haven't quite figured out what I did wrong when replacing it with java.net calls.

OK, thanks for posting the test case. I'll try and take a look.

On breakpointing it and stepping around, it looks like the response I get back is 404.
I don't really use this verify(...) style in any of my own tests so I don't know how it's supposed to work, but in my own tests, I'm using stubFor(...) before doing the action, and I get a 200 response. And with this other style where it's checked after doing the action, I'm not entirely sure how it's supposed to work.
But in this particular case, if I do change out their style for my usual stubbing style, the test passes...

OK, so you're not actually creating any stubs here. WireMock's default behaviour is to fail your test if you've made requests that it hasn't been able to match, on the assumption that this probably means you've missed something. This is analogous to the approach some object mocking tools take where unexpected calls are considered errors.
Two options to fix this:

Stub the call being made so that there's something to match it (I'd consider this best practice)
Disable the failure behaviour by setting failOnUnmatchedRequests to false in the rule constructor.

I've ended up updating all the tests using verify to use stubFor instead, and they're passing, so I'll just close this. Thanks for the info.


Bot using a Discord account.

Please tick all applicable boxes.

[ ] I am using Python 3.5 or higher (run python --version on the command line)
[ ] I have followed the official guides to install the bot for my system
[ ] I have updated my dependencies to the latest version using the appropriate update script

Which version are you using?

[ ] The latest master version (1.9.7)
[ ] The latest review version

What type of issue are you creating?

[ ] Bug
[ ] Feature request
[- ] Question

Description of issue
I have updated the bot after a long time now is it still possible to you a Discordaccount instead of a bot token? If yes, how? Because I am seeing Token where there was a slot to type it account data.
Steps to reproduce

Log file
Please attach your MusicBot log file (located at logs/musicbot.log) to this issue. You can do so by dragging and dropping the file here. If you do not include your log file, you WILL be asked to provide one.

Discord no longer will tolerate user bots, and doing so is a bannable offense now. As such, the option to use email and password has been removed.
https://support.discordapp.com/hc/en-us/articles/115002192352-Automated-user-accounts-self-bots-


MM-28332: Add a fallback for when unaccent is not available (now ready to merge)

Summary
A rebased copy of #280. The original summary:

I've changed the migration so we don't finish it when we are unable to create the extension, but only log the error. Also, in case the extension fails to be created, I've added a fallback so we don't use it (I considered implementing a noop SQL function so we don't need to check whether the real function exists, but we would have the same problem: does the user has permissions to add a function?)
I've smoke-tested that the general Mattermost search is not affected by this change. Also, I'm 99% sure it won't affect anything because all the extension does is adding a dictionary and a function, which you need to explicitly call to get the behavior.
Also, I was testing this mostly with the ñ letter, and after all was implemented, I tried to create an incident with letters with accents (áéíóú) and it turns out we cannot create incidents with those letters :sob: (my gut feeling is because of channel names restrictions). We may want to look into that, of course, but as this work was already done, I think it's better to merge it and tackle that in the future.

Ticket Link
https://mattermost.atlassian.net/browse/MM-28332

Sorry for the re-request of the review, @crspeller and @cpoile. But I messed up the rebase in the other PR and, although the changes are minimal, wanted your re-approval :)

Codecov Report

Merging #284 into master will decrease coverage by 0.02%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##           master     #284      +/-   ##
==========================================
- Coverage   45.96%   45.94%   -0.03%
==========================================
  Files          22       22
  Lines        2837     2847      +10
==========================================
+ Hits         1304     1308       +4
- Misses       1360     1364       +4
- Partials      173      175       +2

Impacted Files
Coverage Δ

server/sqlstore/migrate.go
41.66% <0.00%> (ø)

server/sqlstore/incident.go
78.57% <50.00%> (-1.60%)
:arrow_down:

server/sqlstore/migrations.go
78.78% <66.66%> (ø)

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 c1e1bb1...44b5b3f. Read the comment docs.

@lieut-data, not sure if using the sqlStore struct is the best place to put the cached value. Any other ideas?


Update build to work with JDK 11

Is your feature request related to a problem? Please describe.
The codebase is currently targetted to be build with JDK 8, where as JDK 11 has now been the latest LTS for awhile - further the next LTS (JDK 17) is due this year (2021).
Describe the solution you'd like
Fix the current issues with the SBT build which is blocking this. (In theory the code would not yet have to be changed, as this ticket does not yet suggest also increasing the target version to 11 - another ticket should capture that.)
Describe alternatives you've considered
Just upgrading to 9 or 10 - however they're already obsolete.
Additional context
Here is a quick attempt with no effort to address anything.
At git commit:
$ git log --oneline -1
717109d89 (HEAD -> develop, origin/develop, origin/HEAD) chore(deps): Update SBT wrapper script

With java version:
$ java -version
openjdk version "11.0.10" 2021-01-19
OpenJDK Runtime Environment 18.9 (build 11.0.10+9)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.10+9, mixed mode)

Results in (using the SBT wrapper script in project root):
$ ./sbt installerZip
[info] Loading settings from idea.sbt ...
[info] Loading global plugins from /home/ian/.sbt/1.0/plugins
[info] Loading settings from plugins.sbt ...
[info] Loading project definition from /var/tmp/openEQUELLA/project
[info] Updating ProjectRef(uri("file:/var/tmp/openEQUELLA/project/"), "openequella-build")...
[info] Done updating.
[warn] Found version conflict(s) in library dependencies; some are suspected to be binary incompatible:
[warn] 	* org.ow2.asm:asm-commons:8.0.1 is selected over 7.0
[warn] 	    +- org.jacoco:org.jacoco.core:0.8.6                   (depends on 8.0.1)
[warn] 	    +- org.pantsbuild:jarjar:1.7.2                        (depends on 7.0)
[warn] 	* org.ow2.asm:asm-analysis:8.0.1 is selected over 7.0
[warn] 	    +- org.ow2.asm:asm-commons:8.0.1                      (depends on 8.0.1)
[warn] 	    +- org.ow2.asm:asm-commons:7.0                        (depends on 7.0)
[warn] 	* org.ow2.asm:asm-tree:8.0.1 is selected over 7.0
[warn] 	    +- org.jacoco:org.jacoco.core:0.8.6                   (depends on 8.0.1)
[warn] 	    +- org.ow2.asm:asm-analysis:8.0.1                     (depends on 8.0.1)
[warn] 	    +- org.ow2.asm:asm-commons:8.0.1                      (depends on 8.0.1)
[warn] 	    +- org.ow2.asm:asm-analysis:7.0                       (depends on 7.0)
[warn] 	    +- org.ow2.asm:asm-commons:7.0                        (depends on 7.0)
[warn] 	* org.ow2.asm:asm:8.0.1 is selected over 7.0
[warn] 	    +- org.jacoco:org.jacoco.core:0.8.6                   (depends on 8.0.1)
[warn] 	    +- org.ow2.asm:asm-tree:8.0.1                         (depends on 8.0.1)
[warn] 	    +- org.ow2.asm:asm-commons:8.0.1                      (depends on 8.0.1)
[warn] 	    +- org.pantsbuild:jarjar:1.7.2                        (depends on 7.0)
[warn] 	    +- org.ow2.asm:asm-tree:7.0                           (depends on 7.0)
[warn] 	    +- org.ow2.asm:asm-commons:7.0                        (depends on 7.0)
[warn] 	* net.sf.saxon:Saxon-HE:9.6.0-5 is selected over 10.3
[warn] 	    +- com.etsy:sbt-checkstyle-plugin:3.1.1 (scalaVersion=2.12, sbtVersion=1.0) (depends on 9.6.0-5)
[warn] 	    +- com.puppycrawl.tools:checkstyle:8.41.1             (depends on 10.3)
[warn] Run 'evicted' to see detailed eviction warnings
[info] Compiling 16 Scala sources to /var/tmp/openEQUELLA/project/target/scala-2.12/sbt-1.0/classes ...
[info] Non-compiled module 'compiler-bridge_2.12' for Scala 2.12.6. Compiling...
[info]   Compilation completed in 4.681s.
[warn] there were two feature warnings; re-run with -feature for details
[warn] one warning found
[info] Done compiling.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.protobuf.UnsafeUtil (file:/home/ian/.sbt/boot/scala-2.12.6/org.scala-sbt/sbt/1.1.6/protobuf-java-3.3.1.jar) to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of com.google.protobuf.UnsafeUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
/var/tmp/openEQUELLA/build.sbt:140: error: ambiguous reference to overloaded definition,
both method putAll in class Properties of type (x$1: java.util.Map[_, _])Unit
and  method putAll in class Hashtable of type (x$1: java.util.Map[_ <: Object, _ <: Object])Unit
match argument types (java.util.Map[String,String])
  props.putAll(
        ^
[error] Type error in expression
Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore?

This obviously looks like a fairly simple issue, but it's just a question of how many of these follow.
NOTE: Those dependency warnings are not new or related to this.

I've also just noticed in com.tle.core.application.impl.PluginServiceImpl there is use of Reflection.getCallerClass(depth) which is deprecated in Java 8 and slated for removal in 9. Probably need to go and find others like this and get a list together.


issue #2562 fix

this fix is for issue #2562 where I have set transformInLineCode to true

closes #2562
Fixes Issue
#2562

Changes proposed

Check List (Check all the applicable boxes)

[ x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x ] All new and existing tests passed.
[x ] This PR does not contain plagiarized content.
[ x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers
I need more advice for this PR to check if it is correct

Thank you Sean! Can you add a screenshot of before and after please

just to clarify:
do you want me to add screenshots of the code changes?
I'm not sure what to screenshot otherwise

Sorry for the confusion. Not the code changes because I can see the code changes in the files changed tab. But it would be useful to see what effect the change the config file had to the docs that are created to see if the inline code is now rendered and the issue #2562 is resolved.

Ah I got it! I shall do that. Thank you Eddie!

im stuck in finding the new (and correct) stuff to be displayed
the old error which @Pradumnasaraf had shown is in this link:
https://linkfree.eddiehub.io/docs/contributing/hacktoberfest

In order for this to work correctly, the following code needs to be added to styles/globals.css before the tailwind imports:
code.language-unknown::before, code.language-unknown::after {
  content: ""
}

Then the hacktoberfest docs will look like the following:

Hey @dan-mba
I have now updated the styles/global.css file as you have specified.
Is it correct?

Hey @dan-mba I have now updated the styles/global.css file as you have specified. Is it correct?

@AldrinSeanPereira  The styles change looks good.
Now you need to fix next.config.mjs like I mentioned here

Thank you @schmelto for getting this fixed.
Thank you @dan-mba for your help 🙌🏼
I had been busy with work and unfortunately forgot to get back to this.

Great collab everyone 👍