Thought pathways

Similar to Neural pathways except on a larger, more modular scale.
While neural pathways connect neurons throughout distant areas of the brain, Donna's thought pathways would represent traversals through thought handlers.
A thought handler is a function that transforms a thought entity, given it has an expected input and output data type that the handler supports processing. While the brain has clusters of neurons that connect to each other and eventually learn how to process information passing through them (neural network), a thought handler is like a pre-computed neural network that is specialized for processing certain type of data and can output another specific type of data. For instance, there are areas of the brain responsible for understanding speech. In Donna, those areas would be represented as individual thought handlers, such as Speech-to-Text handler that supports input type audio or speech and output type of text. Donna could have another thought handler for text to Intent, such as wit.ai.
A thought entity can be thought as a unit describing a chunk of related information that can be processed by Donna.
Sensory input ( Input entities ) will be received by Donna and then be converted to Thought entities that can be passed through thought pathways in the same way information in the human body's nervous system passes through the neurons in the brain. Graph traversal algorithms could be implemented to improve efficiency / precision of traversal from input entity through thought handlers. Neural networks could also be used to further optimize which thought handlers are used more often in different cases.

Essentially making the InputEntity for raw data (right from the senses) and IntentEntity into ThoughtEntity and the IntentRouter would be the ThoughtRouter.

Thought entities should have a field for Thought Handler History or something similar, that handlers would be added to if the Thought passed through them.
By including this, we could take a Thought at the end of it's life, such as when it is sent to Output, and then compare the meta data for the thought and the thought handler history and further optimize, such as with artificial neural networks.

Also utilize the confidence factor. Picture an Artificial Neural Network

with each input flowing through the connections joining each of the nodes until it reaches the output.
Now consider that each of the hidden nodes represent a thought handler / process / transformer. In an ANN, each node has a coefficient. In the thought pathway, the coefficient reflects the bias of confidence for each thought handler (hidden node). Each thought handler should have their own confidence for their result given the input (thought entity), and that confidence is then influenced by their own coefficient as learned in the thought pathway network.

Examples of situations for Donna to process:

Sense -> Sense/Input receiver plugin
Thought -> Thought handler plugin
Output -> Output handler plugin

Playing a song, requested from voice

"Play " (Sense) -> Speech-to-text (Thought) -> text-to-intent with Wit.ai (Thought) -> intent processing for intent play_song (Thought) -> Play song on iTunes (Output)

Have an expiry date and date of last access attached to each of the Thoughts? Older thoughts can be pushed from short-term into long-term memory.

Thought entities should have keywords associated to them such that they can be "primed". Priming Priming is an implicit memory effect in which exposure to one stimulus influences a response to another stimulus. Donna is constantly receiving stimulus and priming is an important aspect of making sure she reacts appropritely.

Consider integrating with Node-RED! https://github.com/node-red/node-red

This looks interesting (especially the idea of using Node-RED) - would like to contribute to this. How much work have you done on this and could you provide any pointers to get started?


[feature request] reverse tunnel via hysteria

i'm looking for an approach that helps expose a local client listening port at server side (via hysteria), e.g.
[INTRANET IP]:443(listening) <---hysteria--- [PUBLIC IP]:443(listening)
Concretely, my router is running a bittorrent client announcing its DHT port to a tracker, unfortunately what the tracker see is the IP of the hysteria server (public). I need somehow to establish a 'reverse tunnel' that can forward the listened packets (both UDP and TCP) back to intranet.
Do you have any suggestions? Thanks.

see the frp

see the frp

yes but then it would be like hysteria(frp(traffic)), i.e. unnecessary nesting.

why you need the hysteria?
you can use the frp only

frp traffic can be easily identified and 'QoS'ed.

Dup of https://github.com/HyNetwork/hysteria/issues/55


ImportError: DLL load fails on Windows10 install. MFPlat.dll MF.dll

Please close (or add a note to the README).
I encountered a missing DLL error and the root cause was missing MFPlat.dll and friends. Exactly like https://github.com/skvark/opencv-python/issues/181#issuecomment-476319876
FYI / For Google.
The page to visit to determine "which version of the media features pack should I download" is
https://support.microsoft.com/en-us/help/3145500/media-feature-pack-list-for-windows-n-editions
It would be cool if you offered / built without the MSMF (media features). -D WITH_MSMF=no as this seems to be / was recently bugged https://github.com/opencv/opencv/issues/11696 and https://github.com/opencv/opencv/issues/11810 in 3.4 and above.
According to https://github.com/opencv/opencv/pull/11882 the priority is MSMF, DSHOW, VFW. Of those I think DSHOW has the least dependencies so maybe building with only that backend is sufficient on windows - but that might actually work worse for people where they have MF installed and an opecv version without a buggy MSMF backend.
In all cases it would be worth mentioning "Please install https://github.com/lucasg/Dependencies and open cv2.pyd to debug missing DLL issues."

I will have a look at those MSMF issues and add a note to the README.

Thanks. I learned that their is an entire version of Windows that misses these DLLs
https://www.google.com/amp/s/www.howtogeek.com/322112/what-is-an-n-or-kn-edition-of-windows/amp/
The current builds which require MSMF Will therefore always fail on this "Windows N"

I had the same issue. You can freely download the Media Pack for Windows 10 here : https://www.microsoft.com/en-us/software-download/mediafeaturepack

There is now a note in the README about this.
DSHOW can be forced via environment variable: OPENCV_VIDEOIO_PRIORITY_LIST=DSHOW
I'm keeping the builds as is to avoid any further issues.


GPL-nnn New plate type to cherrypick UK Biocenter [RT 688766]

User story
GPL-nnn | As process development we need to add a new plate type for Sample Management to cherry pick from in order to support the processing of deep well plates from the UK Biocentre in Project Heron.
Who the primary contacts are for this story
Scott T (R&D)
Acceptance criteria
To be considered successful the solution must allow:
The name of the plate type to be added should be ‘Optical96 and Base’.
Maximum volume should be 250ul
Additional context
Add any other context or screenshots about the feature request here.

Merged to develop:
https://github.com/sanger/sequencescape/commit/3988e43073b6c6799e1c1bcb14ee1a08f7e06362

Once deployed running:bundle exec rake plate_type:update will generate the necessary plate types


Segmentation Fault in ex_cmds.c

We found Segmentation Fault issue in vim binary and vim is complied with clang enabling ASAN.
Machine Setup
Machine : Ubuntu 16.04.3 LTS
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11)
VIM - Vi IMproved 8.1 (2018 May 18, compiled Oct 20 2019 11:04:35)
Included patches: 1-2191
version : 8.1.2191
Commit : 83e9a1c
Command : ./vim -u NONE -X -Z -e -s -S POC -c ':qa!'

POC : POC-2.zip
ASAN Output
fuzzer@fuzzer:~/victim/vim/src$ ./vim -u NONE -X -Z -e -s -S POC-2 -c ':qa!'
ASAN:DEADLYSIGNAL
=================================================================
==2621==ERROR: AddressSanitizer: SEGV on unknown address 0x000000f4e540 (pc 0x0000006c8237 bp 0x7ffeac5f2c50 sp 0x7ffeac5f2b00 T0)
    #0 0x6c8236 in linelen /home/fuzzer/victim/vim/src/ex_cmds.c:263:11
    #1 0x6c8236 in ex_align /home/fuzzer/victim/vim/src/ex_cmds.c:197
    #2 0x70768b in do_one_cmd /home/fuzzer/victim/vim/src/ex_docmd.c:2483:2
    #3 0x70768b in do_cmdline /home/fuzzer/victim/vim/src/ex_docmd.c:976
    #4 0x5022b2 in apply_autocmds_group /home/fuzzer/victim/vim/src/autocmd.c:2105:2
    #5 0x50548a in apply_autocmds /home/fuzzer/victim/vim/src/autocmd.c:1607:12
    #6 0x51a2e0 in buflist_new /home/fuzzer/victim/vim/src/buffer.c:2153:6
    #7 0x5283c6 in buflist_add /home/fuzzer/victim/vim/src/buffer.c:3335:11
    #8 0x4ee64c in alist_add /home/fuzzer/victim/vim/src/arglist.c:188:6
    #9 0x4ee64c in alist_set /home/fuzzer/victim/vim/src/arglist.c:157
    #10 0x4f0572 in do_arglist /home/fuzzer/victim/vim/src/arglist.c:458:6
    #11 0x4f2ed5 in ex_next /home/fuzzer/victim/vim/src/arglist.c:721:10
    #12 0x70768b in do_one_cmd /home/fuzzer/victim/vim/src/ex_docmd.c:2483:2
    #13 0x70768b in do_cmdline /home/fuzzer/victim/vim/src/ex_docmd.c:976
    #14 0xb5fd33 in do_source /home/fuzzer/victim/vim/src/scriptfile.c:1214:5
    #15 0xb5df9f in cmd_source /home/fuzzer/victim/vim/src/scriptfile.c:805:14
    #16 0x70768b in do_one_cmd /home/fuzzer/victim/vim/src/ex_docmd.c:2483:2
    #17 0x70768b in do_cmdline /home/fuzzer/victim/vim/src/ex_docmd.c:976
    #18 0xea7c77 in exe_commands /home/fuzzer/victim/vim/src/main.c:3133:2
    #19 0xea7c77 in vim_main2 /home/fuzzer/victim/vim/src/main.c:795
    #20 0xea3f6e in main /home/fuzzer/victim/vim/src/main.c:444:12
    #21 0x7f70763c982f in __libc_start_main /build/glibc-LK5gWL/glibc-2.23/csu/../csu/libc-start.c:291
    #22 0x41aaf8 in _start (/home/fuzzer/victim/vim/src/vim+0x41aaf8)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /home/fuzzer/victim/vim/src/ex_cmds.c:263:11 in linelen
==2621==ABORTING

The script is garbage.  I don't see how ex_cmds.c:263:11 can be wrong.
Please reopen if this can be reproduced in a reasonable way.

I could reproduce the crash and simplify it to this case without garbage characters:
./vim --clean -c 'au BufNew x center' -c 'next x'
Vim: Caught deadly signal SEGV
Vim: Finished.
Segmentation fault (core dumped)

With valgrind, I get:
$ valgrind ./vim --clean -c 'au BufNew x center' -c 'next x' 2> vg.log
$ cat vg.log
==7927== Memcheck, a memory error detector
==7927== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==7927== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==7927== Command: ./vim --clean -c au\ BufNew\ x\ center -c next\ x
==7927==
==7927==
==7927== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==7927==    at 0x711D187: kill (syscall-template.S:78)
==7927==    by 0x50CF54: mch_exit (os_unix.c:3334)
==7927==    by 0x625E75: getout (main.c:1710)
==7927==    by 0x6ED188F: ??? (in /lib/x86_64-linux-gnu/libpthread-2.27.so)
==7927==    by 0x460DB8: linelen (ex_cmds.c:262)
==7927==    by 0x460DB8: ex_align (ex_cmds.c:197)
==7927==    by 0x46EF5D: do_one_cmd (ex_docmd.c:2482)
==7927==    by 0x46EF5D: do_cmdline (ex_docmd.c:975)
==7927==    by 0x40C90E: apply_autocmds_group (autocmd.c:2105)
==7927==    by 0x40D1F9: apply_autocmds (autocmd.c:1607)
==7927==    by 0x4112B5: buflist_new (buffer.c:2153)
==7927==    by 0x4143FF: buflist_add (buffer.c:3335)
==7927==    by 0x4086D9: alist_add (arglist.c:188)
==7927==    by 0x4086D9: alist_set (arglist.c:157)
==7927==    by 0x408D61: do_arglist (arglist.c:458)

When running with gdb, it crashes at line ex_cmds.c:262:
 245│     static int
 246│ linelen(int *has_tab)
 247│ {
 248│     char_u  *line;
 249│     char_u  *first;
 250│     char_u  *last;
 251│     int     save;
 252│     int     len;
 253│
 254│     /* find the first non-blank character */
 255│     line = ml_get_curline();
 256│     first = skipwhite(line);
 257│
 258│     /* find the character after the last non-blank character */
 259│     for (last = first + STRLEN(first);
 260│                                 last > first && VIM_ISWHITE(last[-1]); --last)
 261│         ;
 262│     save = *last;
 263├>    *last = NUL;

(gdb) p last
$1 = (char_u *) 0x65bb82 ""
(gdb) p first
$2 = (char_u *) 0x65bb82 ""
(gdb) p line
$3 = (char_u *) 0x65bb82 ""

I see that ml_get_curline()->ml_get_buf() can return the constant string "".
So it is illegal to modify it of course at ex_cmds.c:262.
This patch fixes it:
diff --git a/src/ex_cmds.c b/src/ex_cmds.c
index bcff7ee71..090dc593e 100644
--- a/src/ex_cmds.c
+++ b/src/ex_cmds.c
@@ -253,6 +253,9 @@ linelen(int *has_tab)

     /* find the first non-blank character */
     line = ml_get_curline();
+    if (*line == NUL)
+       return 0;
+
     first = skipwhite(line);

     /* find the character after the last non-blank character */

I will create a PR soon to make sure that CI is green with this fix.


Injection Crash

Describe the bug
When trying to inject (manual map) the cmd prompt does its thing then crashes
To Reproduce
Just try to inject when the current GitHub version
Expected behavior
Unhandled exception at 0x0000000000000000 in cs2.exe: 0xC0000005: Access violation executing location 0x0000000000000000.
I'm sure you are aware of this.

Use loadlibrary


Describe the bug

Describe the bug
Problem: after trying to connect to Local Host (without a server running) if I then go to Chainlist and try to add any network I will see that my current network is Localhost even though I am on Rinkeby.
https://user-images.githubusercontent.com/54408225/167589129-5a4df0bb-efc1-425f-8dda-ee26d6ef83e4.mp4
Steps to reproduce
Reproduction steps:

Try to connect to Localhost - wait until says it's not possible
Click the top right cross button
Open a new window and go to Chainlist
Try to add a new network: here you'll see you are changing from Localhost to this new network, but in reality you are not in Localhost but in Rinkeby

Error messages or log output
No response
Version
10.14.0
Build type
No response
Browser
Firefox
Operating system
Linux
Hardware wallet
No response
Additional context
No response
Originally posted by @seaona in https://github.com/MetaMask/metamask-extension/issues/14671
Originally posted by @DNAOFFICIALL in https://github.com/DNAOFFICIALL/potential-eureka/issues/2
Originally posted by @DNAOFFICIALL in https://github.com/trustwallet/trust-web3-provider/issues/276

@DNAOFFICIALL

reported the issue and user as spam


New command: m365 spe container remove

Usage
m365 spe container remove [options]
Description
Removes a container
Options

Option
Description

-i, --id <id>
Container id

--recycle
Recycle a container instead of actually deleting it.

Examples
Permanently deletes a container
m365 spe container remove --id "b!ISJs1WRro0y0EWgkUYcktDa0mE8zSlFEqFzqRn70Zwp1CEtDEBZgQICPkRbil_5Z"

Recycles a container
m365 spe container remove --id "b!ISJs1WRro0y0EWgkUYcktDa0mE8zSlFEqFzqRn70Zwp1CEtDEBZgQICPkRbil_5Z" --recycle

Default properties
No response
Additional Info
we may use the following DELETE request to move a container to recycle bin
/storage/fileStorage/containers/{containerId}

https://learn.microsoft.com/en-us/graph/api/filestorage-delete-containers?view=graph-rest-1.0&tabs=http
to permanently delete it we may use
beta/storageContainers/{containerId}/permanentDelete

what's worth noticing is that permanent delete as of now is only available on beta MS Graph endpoint
https://learn.microsoft.com/en-us/graph/api/filestoragecontainer-permanentdelete?view=graph-rest-betathe

@pnp/cli-for-microsoft-365-maintainers any feed?

The recycle option is a bit vague. Won't it make more sense to recycle by default and hard delete it when you specify an additional option?
One small additional detail is that we're missing the --force option here.

Thank you for your comments.

The recycle option is a bit vague. Won't it make more sense to recycle by default and hard delete it when you specify an additional option?

Well this is aligned with what we have. Remove hard by default and recycle when --recycle is specified.  as an example
https://pnp.github.io/cli-microsoft365/cmd/spo/file/file-remove
or
https://pnp.github.io/cli-microsoft365/cmd/spo/listitem/listitem-remove

One small additional detail is that we're missing the --force option here.

thanks. Added  👍

@pnp/cli-for-microsoft-365-maintainers any other comment?

Looks good, ship it!


fix: TypeScript errors

Description

Fix TypeScript errors due to incorrect types, missing types, etc.
Fix TypeScript error in the typegoose classes due to strictPropertyInitialization defaulting to true - https://www.typescriptlang.org/tsconfig/#strictPropertyInitialization
Add npm script to check for TypeScript errors
Add GitHub action to check for ESLint and TypeScript errors when a commit is pushed

I really appreciate that!


Reference to Issue #226

I fixed the collision with folder of same name. Is it possible for me to get a pull request for the update.

no need too - as we have a solution using the equality function.


Remove unneeded !Sub function

Remove unneeded !Sub function

I'm not entirely sure if this is what's causing the deploy pipeline failure:
ERROR: Stack sagebase-dca-dev-cname in account<PHONE_NUMBER>03 (us-east-1) update failed. reason: unable to find export [object Object] in account<PHONE_NUMBER>29/us-east-1.<PHONE_NUMBER>03 = SageITAccount)


Replace crash_reporting flag with report send command

Open GitHub create issue window? Mail client? Offer pastebin uploading?

Closed by #716


Add releases tab to every repo page

Closes #8
I've successfully added a releases tab.
However I have some concerns which I hope I'd be able to address with your help.

Adding just <span class="octicon octicon-tag"> does not render an icon. I needed to add a full SVG markup like the rest of the icons I could found on github.com.
Appending the Releases tab and activating it instead of Code is rather slow and you could visually see the change after the page loads. Feedback appreciated.
If you have an idea how to easily count the number of releases (or tags) to put next to the label on the tab, that would be great.

P.S. This also adds a new shortcut g r for navigating to the releases page of a repo :smiley_cat:

Nice work!
When I click the tab and then click the back button in the browser, the Releases tab is duplicated. We need to somehow guard it. @stefanbuck Any tips on how to handle this? Something the injection module could handle for us maybe?

@sindresorhus I think I've addressed your comments. I've also added a quick check if the Releases tab is not already present which solves the back button behaviour. It should also work if GitHub decides to add a Releases tab themselves :smile:

I've also fixed the activation of Releases tab when visiting the Tags page, e.g. https://github.com/sindresorhus/refined-github/tags.

GitHub.com use some kind of cache for pages that you visited before. So if you navigate back and forth you just switch between the cache pages. That's the reason why the button was added multiple times, because in the cache version it was already there.
The quick check that @hkdobrev implemented looks simple and solid :+1:

@stefanbuck Thanks for chiming in. I'm aware of the caching. I was wondering more in the direction of a general solution than having to check everything you add.

Ahh I see, let me think about it.

@stefanbuck Ok, cool. Let's continue in https://github.com/octo-linker/injection/issues/2.

Perfect! Thank you @hkdobrev. This is a really nice addition.
Adding you to the repo per the open open source idea because of this awesome contribution.

If you have an idea how to easily count the number of releases (or tags) to put next to the label on the tab, that would be great.

We could scrape it from the repo landing page when the user goes there, persist it in localstorage, and then have it available to any repo page. Not sure whether it's worth the trouble, though.


The detail about accelerate my own t2v model

Hi, Yuanhao, thanks for your tips. I have some detailed question about accelerate my own t2v model.
The model I want to accelerate is VideoCrafter2. The biggest problem is VC2 doesn't use diffusers lib define its model. So, I have some questions in train and inference stage.

Train stage:
According to your tip, I have build my own webdataset-format dataset.
Modify model: I use vc2's code (vc2_model_define) and extract its unet model, what I still modify next?

Inference stage:
What I should modify in the demo.py, so that I can inference with my own t2v model?

Thanks a lot.

Could you give me some tips?
Thanks a lot!

Hi there, I did not try VideoCrafter before, but here are some general advice.
For training, I think modifying the dataset and the model definition are enough. Please be sure to check the noise schedulers, which can be critical for distillation.
For inference, you may need to adapt VideoCrafter's code for the model definition and the noise scheduler for the multi-step sampling.

Ok, I know what you mean.
Videocraft2 does not use the diffusers lib to define unet, therefore, some inputs need to be rewritten to adapt to VC2's Unet input
Now I am solving these problems.
Thanks a lot.


Fixes for serverless HLS

Actual changes from @luniki.

Pefer master playlists over non-master playlists and mp4s
Prefer native_hls renderer
Wait for !isFinitite instead of isNan for this renderer

Pinging @luniki to look at this review since he is the original author of the patch IIRC.


//  See the documentation for GetLocaleInfoEx.
//
//  A language ID is a 16 bit value which is the combination of a
//  primary language ID and a secondary language ID.  The bits are
//  allocated as follows:
//
//       +-----------------------+-------------------------+
//       |     Sublanguage ID    |   Primary Language ID   |
//       +-----------------------+-------------------------+
//        15                   10 9                       0   bit
//
//  WARNING:  This pattern is broken and not followed for all languages.
//            Serbian, Bosnian & Croatian are a few examples.
//
//  WARNING:  There are > 6000 human languages.  The PRIMARYLANGID construct
//            cannot support all languages your application may encounter.
//            Please use Language Names, such as "en".
//
//  WARNING:  There are > 200 country-regions.  The SUBLANGID construct cannot
//            represent all valid dialects of languages such as English.
//            Please use Locale Names, such as "en-US".
//
//  WARNING:  Some languages may have more than one PRIMARYLANGID.  Please
//            use Locale Names, such as "en-FJ".
//
//  WARNING:  Some languages do not have assigned LANGIDs.  Please use
//            Locale Names, such as "tlh-Piqd".
//
//  It is recommended that applications test for locale names rather than
//  attempting to construct/deconstruct LANGID/PRIMARYLANGID/SUBLANGID
//
//  Language ID creation/extraction macros:
//
//    MAKELANGID    - construct language id from a primary language id and
//                    a sublanguage id.
//    PRIMARYLANGID - extract primary language id from a language id.
//    SUBLANGID     - extract sublanguage id from a language id.
//
//  Note that the LANG, SUBLANG construction is not always consistent.
//  The named locale APIs (eg GetLocaleInfoEx) are recommended.
 The author(s) have been notified to review your proposed change.


🐛 Nextcloud: App cannot be installed because it makes the server unstable

Description
Every time I try as admin to install an app in my nextcloud instance, I get the message that this makes the server unstable. Unfortunately, this has been going on all along and I thought that the problem would be fixed with version <IP_ADDRESS>, but unfortunately this is not the case
Reproduction steps
Go to Profile
> Apps > try to install any Apps > error

Addon Logs
migrations] 02-default-location: skipped
[migrations] done
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────

using keys found in /data/config/keys
Initializing nextcloud <IP_ADDRESS> (this can take a while) ...
Setting permissions
Initializing finished
Starting...
/etc/cont-init.d/02-init_steps.sh: executing
Setting logs

----------------------------------------
 Nextcloud <IP_ADDRESS> is installed
----------------------------------------
... checking for app updates
All apps are up-to-date or no updates could be found
... Clean potential errors
Maintenance mode already disabled
... Remove CODE if installed as not compatible
... Disabling check_data_directory_permissions
System config value check_data_directory_permissions set to boolean false
    0 [>---------------------------]    0 [->--------------------------]    0 [--->------------------------]    0 [----->----------------------]    0 [------->--------------------]post_max_size set to 2056
... enabling thumbnails
System config value preview_ffmpeg_path set to string /usr/bin/ffmpeg
System config value enable_previews set to string true
/etc/cont-init.d/02-mariadb_discovery.sh: executing
---
HAos

Hello, given that we cannot install the applications, how can I install the applications manually with occ and in which applications (portainer?). I wanted to install 'Brute-force settings' because I have an error message in Nextcloud "Your network address has been identified as "<IP_ADDRESS>" and it is restricted by the anti-intrusion mechanism which slows down the performance of certain requests. If this network address is not yours, this could mean that there is a proxy configuration error?
Thanks

Hi, it's a complex issue indeed. Actually the apps are installed, but not enabled  you can use two methods from this thread to enable manually :  https://github.com/alexbelgium/hassio-addons/issues/1333#issuecomment-2046801286 or this one https://github.com/alexbelgium/hassio-addons/issues/1333#issuecomment-2090281733

Hello and thank you, finally I succeeded, I went through portainer, you just have to find the exact word of the application for the occ line. I am left with an error in Nextcloud: "Your web server is not configured correctly to resolve .well-known URLs, failed on: /.well-known/caldav". (I think because I installed it on an external usb3 ssd drive from rapsberry "/mnt/sdb1/nextcloud" and after installation, it is found in /media/ssd1t/nextcloud). For this error, I cannot find a solution.

Nextcloud is annoying they don't seem to really care about breaking things... There even is a thread here : https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897 Well they say that nginx proxies are our responsibility. The nginx proxy we are is configured by linuxserver's nextcloud image but there is not much activity going there to solve those issues...

Thanks, i keep like this ? It's not "grave" ?


dep enhancements

I recently did some bisecting and noticed that "dep ensure" wasn't getting called despite changes in the Gopkg files, leading to build failures. Now it's called depending on the time stamps of the input files. This also makes it possible to do a parallel build without having to worry about potentially invoking "dep ensure" multiple times in parallel.
The update of Gopkg.lock is something that was apparently missed when doing the corresponding code changes.

@pohly Curious why other folks have not hit the same issue? Could it be that it maybe the result of your workflow?

On Thu, 2018-03-15 at 13:41 +0000, Serguei Bezverkhi wrote:

@pohly Curious why other folks have not hit the same issue?

With issue, do you mean the modified Gopkg.lock? Everyone who checks
out anew should hit that at the moment.
You should be able to reproduce it with master by removing "vendor" and
running "make".

modification of Gopkg.lock when you run dep ensure is expected when packages' versions have relatively loose constraints. Why do you want to remove vendor?

@sbezverk I'm just explaining the situation that developers face when checking out the repo anew and running "make". Manually removing "vendor" is just a quick way to replicate that situation.
The diff in commit 1211eabb7a isn't because of changed versions, is it? If I read it right, it came from removing dependencies on github.com/golang/mock and github.com/kubernetes-csi/csi-test.
Anyway, I don't have any strong opinion about how dependencies should be handled. All care for is that the Makefile does the "right thing" (whatever that is) for some random John Doe who checks out the repo and tries to build.
If Gopkg.lock is only meant to be updated by developers who know what they are doing, then the Makefile should do "dep ensure -vendor-only".
I still think that this should be done automatically when Gopkg.lock or Gopkg.toml change, because otherwise "make" after "git checkout" might end up failing due to incompatible content in "vendor".

On Thu, 2018-03-15 at 07:58 -0700, Serguei Bezverkhi wrote:

modification of Gopkg.lock when you run dep ensure is expected when
packages' versions have relatively loose constraints.

Is that really true? "dep ensure" doesn't change that much for me. It's
only "dep ensure -update" which changes a lot of package versions.

I still think this PR is relevant. @andyzhangx just got bitten by not calling "vendor dep" manually, presumably after changing commits, which is one of the cases that now gets handled automatically. See https://github.com/kubernetes-csi/drivers/issues/76#issuecomment-377484669
I've rebased the change unto the latest master.

vendor is now committed in master.


complete module translation

Marked all needed strings for translation
Added Turkish language translation file. Credits to @hbayindir 🎉!

@zzacharo is this still applicable? I think it's stale and we can close...

@fenekku I think it has been mostly done here: https://github.com/inveniosoftware/invenio-app-rdm/pull/216

Closed via #216


Add model for institutional users

Ticket: ENG-1067
Feature flag: Institutional Dashboard

Purpose
Add institutional-users model for use on new Institutional Dashboard.
Summary of Changes
Added institutional-users model, adapter, and serializer. Also tweaked specific config settings for Windows linting.

Pull Request Test Coverage Report for Build 3443

12 of 12 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 75.47%

Totals

Change from base Build 3439:
0.0%

Covered Lines:
7797

Relevant Lines:
9072

💛  - Coveralls


Add support for setting Bounds with ClientOptions

In our project we wanted to call fitBounds on our map to fit the view based on an array of LatLngBounds (coming from a drawn polygon) but since this code:
   $js[] = "$name.setView({$lateInitClientOptions['center']}, {$lateInitClientOptions['zoom']});";

was being called at the end regardless, we couldn't. So I extended the registerScript function in Map to use an extra parameter in ClientOptions to use fitBounds instead of setView if it is set. The parameter should be a JsExpression of LatLngBounds::getBoundsOfLatLngs().

@sergeantjonas sorry for the delay. Do you mind fix tests?

What happened to this? Did it get merged?

@markebjones needs tests to be fixed

Ahh ok. Seems to be a problem with composer and fxp/composer-asset-plugin? Looks like a common problem for many Pull Requests. Is it something specific that needs to be done to setup the tests correctly before they are run?

Give me a few min and I'll fix it

Cool. Thank you.


add verbosity to pg connections

Needed more verbosity on connections to the postgres DB.

I've spent some time refactoring these DNS lookups and error management, and I thought it was nodejs driving me crazy, but I can't even docker build and run the master branch as-is. There is always a connection error when the backend connects to the postgres DB.
So I'll pause my work on this for now.


GitWritter with Tekton Example

A current gap that exists is the ability to write to a git repository. The purpose of this issue is to create an example supply chain with the last step leveraging the pipeline service and Tekton to write some YAML to a git repository.
Acceptance Criteria
An example exists where:

A supply chain writes some yaml (likely a knative service wrapped in a Kapp App) to a git repository
Usage of the supply chain is documented in both OSS and Commericial docs

Note While we may eventually need the ability to specify the git repository in the workload, for now having the operator hard code it in a Tekton pipeline is sufficient.

Leaving open as it gets rolled into #405


findFiles API should not get default excludes

It seems that all API calls inhert the configured exclude settings which isn't what all extensions want.
Start reading here: https://github.com/Microsoft/vscode/issues/31882#issuecomment-326009834

fyi @joaomoreno

I also think we should be careful about changing the defaults for performance reasons. @roblourens are we using ripgrep for the findFiles call or our old slow find mechanism?

The old one, it takes the same path as quickopen.

I just hit this case where findFiles is getting the default excludes (blocking me for searching for a file in the .git folder). I honestly don't mind that the default changed, but the fact that you can't override the default excludes by passing null or '' or something feels like a much bigger issue, imo.

but the fact that you can't override the default excludes by passing null or '' or something feels like a much bigger issue, imo.

That.

Moving this to December so that we can try this a little but my plan is to not-inherit default excludes when they are set to null via the API


python312Packages.iocsearcher: 2.3-unstable-2024-03-04 -> 1.0.0

Diff: https://github.com/malicialab/iocsearcher/compare/5f7b87761f2195eb358006f3492f0beac7ecc4b0...v1.0.0
Changelog: https://github.com/malicialab/iocsearcher/releases/tag/v1.0.0
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.11 Release Notes (or backporting 23.11 and 24.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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 330813 run on x86_64-linux 1

5 packages built:

iocsearcher (python312Packages.iocsearcher)
iocsearcher.dist (python312Packages.iocsearcher.dist)
nixpkgs-manual
python311Packages.iocsearcher
python311Packages.iocsearcher.dist


Allow default constructor for generated classes

Add new option for records:
xxx = record {
a: string;
b: string;
} deriving (init)
which will generate default constructor i.e.
xxx() = default; //C++
xxx() {} //java
The reason is sometimes when records contain lot of members it's impractical to use generated constructor with many arguments. And often many of them have sensible defaults anyway (empty strings, vectors, optionals). But because the generated class already contains 1 generated constructor the default constructor is not created.
If you don't like default constructor for some reason f.e. because it doesn't initialize scalar values to 0 like in java, generate constructor which will value initialize all members i.e.
xxx() : a(), b() {}
This would be very useful addition

In C++ a record is a struct for which brace-initialization already does the same as the generated constructor, so in theory we could even drop the generated constructor. Then the struct has an implicitly generated default constructor if all members are default-initialized and users have the option to use xxx{} for zero-initialization and xxx() for default-initialization. However that might be a breaking change because the types can no longer be initialized with parens, meaning xxx(a, b) suddenly becomes invalid.

The reason is sometimes when records contain lot of members it's impractical to use generated constructor with many arguments.

I'd say don't use records with too many fields. in such cases I try to group fields together into other records where it makes logical sense and nest them. This doesn't of course work all the time.

Not really sure why structs are even being used. Records should just be classes. Setters and getters should also be predefined for all fields. The defaults for copy and move constructors/assignment-ops should also be generated.

For reference #216

I like this idea, though I'm not a fan of the "= default" version of this which doesn't guarantee any initialization at all.  I think it would be best to have well defined default initial values for all types (false, zero, empty), and generate initializers for them in all languages.  Alternately, we could consider @mknejp's suggestion of dropping the ctor in C++ entirely and relying on default braced initialization entirely, though that doesn't address the question for other languages.
I also think it would be cool to go further and allow constants to be used as "initializers" for fields which want non-zero initial values (like what we can do in C++11 now), but that goes well beyond the minimum needed here. :)

Yea, the generated ctors (and lack of a default) can definitely get annoying quickly.
@artwyman what about including this option so that it's not breaking, either in the record def or as a djinni flag? (--cpp-with-record-default-ctors?).  I might start using a fork of djinni with https://github.com/dropbox/djinni/pull/216 included otherwise.
The ctors as they are now are there in order to ensure consistency across languages?  It seems not too bad to offer an inconsistent but convenient and performant mode as an option.

I think my comments #216 cover this.  I like making it configurable, though I'd prefer making it per-record-type via "deriving" rather than a command-line option.  However, I feel strongly that the default constructor should give all fields a well-defined value, which a simple "= default" definition won't (depending on how it's used, it will sometimes leave numeric fields in an undefined state).  It should be easy for the generator to provide explicit default values, either via initializers in the ctor, or via "= 0" after the field declarations.  I would merge a PR which did those two things.

I think the expected behavior of default ctor is a function of what language shapes your perspective.  C++ and Obj-C expect allocation without initialization; Java does not.  Could we add the change proposed in https://github.com/dropbox/djinni/pull/216/files and add simply the proposed deriving tag to use default ctors?  "Zero-initialization" is not super trivial ... to do it properly encompasses support for user-defined types.

In most cases, I consider creating objects in non-initialized states to be a bug not a feature in the languages which have it.  I can see the argument for it in high-performance scenarios, but I think the likelihood of that being relevant to Djinni types is low.  On the flip side, Djinni's bridging abilities will expose those semantics to other languages which have different expectations, which I think has the potential to cause a lot of confusion.  I'd strongly prefer semantics which initialize everything by default, though I wouldn't object to an opt-in ability to avoid that if someone wants it for high performance.

My use case is performance-sensitive, and the maintainers of my code will have an understanding of multi-language initialization behavior.  (And oblivious users will be isolated from the issue through an interface).
Shall we call it "deriving (default-ctor)" ?  Then perhaps "deriving (init)" could be reserved for the zero-initialization feature.

I'd be okay with default constructor as a separate option, either in deriving, or on the command-line.  It's a bit cpp-specific.  Would you create constructors with the same minimal behavior in every language?  I guess ObjC can have default field values just as C++ can, while Java will default-initialize fields to zero.  Python fields can't exist if they aren't given some explicit value, which could be None, or zero for numbers.
An alternative, at least for the C++ side, would be a subtractive feature which would inhibit the generation of the current all-arguments constructor.  That should leave every struct with the auto-generated default constructor, as well as allowing braced initializers for any number of arguments.  Honestly, if I were implementing Djinni from scratch today I think that's what I would make the default behavior, since the explicit all-arguments constructor has always felt awkward.  That behavior wouldn't even be incompatible with providing full-initialization of all fields as an option too, since the generator could simply declare fields as "int32_t x;" for uninitialized or "int32_t x = 0;" for initialized, without ever having to define a constructor. As it is, since there are backward-compatibility concerns, it probably can't be the out-of-box default, but it could be behavior controlled by global command-line flag, or a per-record "anti-deriving" declaration.


Middle mouse click on a folder note opens two identical tabs. CTRL does not.

I'm experiencing the same issue. I've done some quick debugging and it seems the middle mouse click handler is executed twice (call to plugin.app.workspace.openLinkText(...) in https://github.com/aidenlx/alx-folder-note/blob/2a0af99bd40c32d173b74f315ab23de1ec81d24a/src/click-handler.ts#L48).


editor:delete-to-previous-word-boundary and editor:delete-to-next-word-boundary does not work properly with newlines

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
editor:delete-to-previous-word-boundary and editor:delete-to-next-word-boundary does not work properly with newlines
Steps to Reproduce

Open Atom and insert the following js code snippet

function doubleNumber (num) {

  return num*2
}

Put your cursor before the r in return.
Open command palette and run Delete to previous word boundary

Expected behavior: [What you expect to happen]
Should go to the {
Actual behavior: [What actually happens]
deletes the white space before the return and sees each newline as a new word.
If you repeat this step by putting your cursor on the new line after the { and run editor:delete-to-next-word-boundary  It just deletes 1 newline but doesn't go to the return statement.
Reproduces how often: [What percentage of the time does it reproduce?]
100%
Versions
Atom    : 1.23.0-dev-cbc2bdb20
Electron: 1.6.15
Chrome  : 56.0.2924.87
Node    : 7.4.0
Additional Information
This issue was broken out from  https://github.com/atom/atom/issues/4026#issuecomment-338884328 from @bcorcoran and @PhiLhoSoft as it is a separate issue.

This seems to be the expected behavior. Since there haven't been any other comments here, we're going to close for now barring someone giving some more explanation as to why the current behavior should be changed.


.EXE?

There is no .exe
How i can do this?

Check the readme, you can grab it from the Github Actions.
It's compiled there as a ZIP at the bottom.


Remove duplicated Omnibus content

Incorporated this change into https://github.com/mattermost/docs/pull/6274. Closing


[client-v2] reader buffer optimization

Summary
A lot small buffers may be allocated while reading numeric information.
This PR implements a reusing buffers withing a reader. It is not a default behavior.
Introduced Client.Builder#allowBinaryReaderToReuseBuffers to control the behavior
Note:

implementation is not thread-safe
reader should be called by one thread at a time
small buffers will 64 bytes are pre-allocated

Checklist
Delete items not relevant to your PR:

[x] Unit and integration tests covering the common scenarios were added
[ ] A human-readable description of the changes was provided to include in CHANGELOG
[ ] For significant changes, documentation in https://github.com/ClickHouse/clickhouse-docs was updated with further explanations or tutorials

I do not see tests that enable the flag client_allow_binary_reader_to_reuse_buffers

I've added client-v2/src/test/java/com/clickhouse/client/query/BinaryReadyReusesBuffersTests.java that overrides QueryTests and sets client_allow_binary_reader_to_reuse_buffers


Scope index is broken

indent.get does not return the correct whitespace_tbl for space indent.

Could this cause the scope feature to not work at all? I just migrated from v2 by installing the latest version of v3 and noticed that the scope feature isn't working. I have Treesitter installed, and the lua language parser, but still no scope.

Could this cause the scope feature to not work at all?

No, scope itself works fine.
In your screenshot you are not in any scope. Please read :help ibl.config.scope, that should make it clear.

Is this what is causing the scope highlight to be a different color than the indent highlight if using multiple highlight colors?
Or shall I create a seperate issue?

Is this what is causing the scope highlight to be a different color than the indent highlight if using multiple highlight colors?

yes, it is.


Bug 2196912: Add missing and fix confusing "CPU | Memory" help texts

📝 Description
Fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=2196912
Add missing "CPU | Memory" helper texts in the following pages:

Catalog drawer page:
The VirtualMachine will have {{sockets}} sockets, {{threads}} threads, and {{cores}} cores.

Fix confusing "CPU | Memory" helper texts in the following pages (there was incorrect resource in the text):

Review and create VirtualMachine page:
The VirtualMachine will have {{sockets}} sockets, {{threads}} threads, and {{cores}} cores.
VM Template Details tab:
The template has {{sockets}} sockets, {{threads}} threads, and {{cores}} cores.
VMI Details:
The VirtualMachineInstance has {{sockets}} sockets, {{threads}} threads, and {{cores}} cores.

In which pages the help text for "CPU | Memory" field remains the same/what is correct:

VM Details page

What else has changed (see https://bugzilla.redhat.com/show_bug.cgi?id=2172390#c20):

CPUs = sockets X threads X cores. in the helper text changed to:
CPUs = sockets x threads x cores.

TODO:

[x] wait for Avital to make sure about the help text for Templates

🎥 Screenshots
Before:
Catalog drawer - no any help text available:

VM Template Details tab (looks same also in VMI Details tab and in Review and create VirtualMachine page):

After:
Catalog drawer:

Review and create VirtualMachine page:

VM Template Details tab:

VMI Details:

/retest

@apinnick WDYT about these changes? WDYT about the help text for templates?  'The VirtualMachineTemplate has...' or 'The Template has...' or 'The template has...'  is the best? Thanks!

@avivtur @metalice @pcbailey @upalatucci @vojtechszocs please review

/retest

/lgtm


Pluggable auth

Currently authentication is embedded in things and users services.
Implement auth as a separate and extendible microservice. It should be configurable and provide events and config so that anyone can plug his/hers own implementation of auth.

Related to #651

Closed with #941


Override package for nixfmt

How can I override the package for nixfmt?
I would like to use nixfmt-rfc-style from unstable.

@Nebucatnetzer, if you're on the latest version: hooks.nixfmt.package = pkgs.nixfmt;

Thank you, that might be a problem with devenv then.
The version in there points to a commit from February.

Yeah, we'll get that updated at some point soon.
For older versions, you have to override the entire package set via tools.

Yeah, we'll get that updated at some point soon.

Should I make a per to point nixfmt to nixfmt-rfc-style?

In unstable the old one is now called nixfmt-classic, maybe the soon rename nixfmt-rfc-style to nixfmt?


Remove ajax call debouncing (make optional?) for infinite scroll and empty query term

Hi!
I propose to remove debouncing for cases in subject.
In case of loading next page of data for infinite scroll I don't see what we are waiting for because user didn't actually change anything in search conditions.
As for empty term... It's not so simple as first case. In my project we have two sources of data for select2: 1) let's call it local client data (quite rarely read from secondary service and cached on client); and 2) data from "main" ajax call against not empty user's query term (call to that service with an empty query will return an error so this is completely meaningless). So, when user initially opens dropdown he will always see only local data but in this scenario debouncing of transport function call will just delay appearing local data which actually is available instantly. This is what I propose to change. Hope I explained it clear enough.

This should be fixed in 4.0.0.


SQLitePCL.native.sqlite3.v110_xp.0.9.0 seems to look for esqlite3 in the wrong package directory

Just installed the 0.9.0 stuff and then installed the native/plugin tools for a .net 4.5.2 unit test project and started getting this error
Severity	Code	Description	Project	File	Line	Source	Suppression State
Error		Could not copy the file "\packages\build\native\sqlite3\v110_xp\x64\esqlite3.dll" because it was not found.
I checked the targets file and it's
<Content Include="$(MSBuildThisFileDirectory)..\..\build\native\sqlite3\v110_xp\x86\esqlite3.dll">
If I change it to
<Content Include="$(MSBuildThisFileDirectory)..\build\native\sqlite3\v110_xp\x86\esqlite3.dll">
or
<Content Include="$(MSBuildThisFileDirectory)native\sqlite3\v110_xp\x86\esqlite3.dll">
Then it all works super
I'm running this from an MSunit test which maybe changes the dynamics of things

That's a legit bug that somebody else also found last night.  I've pushed the fix to github, but not yet to nuget.  A 0.9.1 with that fix is in the next day or so.

0.9.1 is on nuget.


Remap broken in going from MOM5 ICA ➡ MOM6 NL3 on mil with develop version

Few things with the remap script:

The yaml file changes format, which implies old ones – that worked in past simply can’t be used.
Not asking for backward compatibility or a translator, but please note down what has changed here Appreciate that!

Output from my test case is at: /discover/nobackup/sakella/restarts/emc_golden_period/output/*_rst; I ran on Milan/SCU17.

A run from those restarts left me with a super interesting crash! :-o /discover/nobackup/sakella/free_run_gold_per/slurm-28387344.out
A run using restarts that I have from past, all fine!
mepo status is following; all is GEOSgcm v11.5.1, except develop branch of GEOS_Util (as of 02/01/2024).
GEOSgcm                | (t) v11.5.1 (DH)
env                    | (t) v4.25.1 (DH)
cmake                  | (t) v3.38.0 (DH)
ecbuild                | (t) geos/v1.3.0 (DH)
NCEP_Shared            | (t) v1.3.0 (DH)
GMAO_Shared            | (t) v1.9.7 (DH)
GEOS_Util              | (b) main
MAPL                   | (t) v2.43.1 (DH)
FMS                    | (t) geos/2019.01.02+noaff.8 (DH)
GEOSgcm_GridComp       | (t) v2.5.1 (DH)
FVdycoreCubed_GridComp | (t) v2.10.0 (DH)
fvdycore               | (t) geos/v2.8.1 (DH)
GEOSchem_GridComp      | (t) v1.13.1 (DH)
HEMCO                  | (t) geos/v2.2.3 (DH)
geos-chem              | (t) geos/v13.0.0-rc1 (DH)
GOCART                 | (t) sdr_v<IP_ADDRESS> (DH)
QuickChem              | (t) v1.0.0 (DH)
TR                     | (t) v1.1.0 (DH)
GMI                    | (t) v1.1.0 (DH)
StratChem              | (t) v1.0.0 (DH)
GEOS_OceanGridComp     | (t) v2.1.5 (DH)
mom                    | (t) geos/5.1.0+1.2.0 (DH)
mom6                   | (t) geos/v2.2.3 (DH)
mit                    | (t) checkpoint68o (DH)
cice6                  | (t) geos/v0.1.3 (DH)
icepack                | (t) geos/v0.1.1 (DH)
sis2                   | (t) geos/v0.0.1 (DH)
GEOSradiation_GridComp | (t) v1.6.0 (DH)
RRTMGP                 | (t) geos/v1.6+1.1.0 (DH)
ww3                    | (t) v6.07.1-geos-r2 (DH)
umwm                   | (t) v2.0.0-geos-r1 (DH)
GEOSgcm_App            | (t) v2.3.1 (DH)
UMD_Etc                | (t) v1.3.0 (DH)
CPLFCST_Etc            | (t) v1.0.1 (DH)

cc: @GEOS-ESM/gmao-si-team

More info:

I cloned a version v10.26.0 of GEOSgcm (the version I wish to use is: v11.5.1; see ⬆), built and ran (on sky/cas; as opposed to my wish of using mil) the remap_restarts app from there in. Output is at: /discover/nobackup/sakella/restarts/emc_golden_period/output-GEOSgcm-v10.26.0 ➡ seems okay!

A log of GEOSgcm run with these restarts is at /discover/nobackup/sakella/free_run_gold_per/slurm-28448900.out and has no errors as in /discover/nobackup/sakella/free_run_gold_per/slurm-28387344.out

This establishes beyond doubt there is a problem somewhere:

Either the boundary conditions are bad?
Code and/or script(s) has some bug somewhere?

@sanAkel : Sorry for these issues.  I can't say what the problem might be.  Did you use "MOM[x] tripoloar grid" bcs from:
 /discover/nobackup/projects/gmao/bcs_shared/fvInput/ExtData/esm/tiles/NL3/
I thought those were "manually" created by Yury and Sarith.  It's anyone's guess if those would work sensibly with remap restarts, or a recent version of the GCM.

@sanAkel : Sorry for these issues.  I can't say what the problem might be.  Did you use "MOM[x] tripoloar grid" bcs from:
 /discover/nobackup/projects/gmao/bcs_shared/fvInput/ExtData/esm/tiles/NL3/
I thought those were "manually" created by Yury and Sarith.  It's anyone's guess if those would work sensibly with remap restarts, or a recent version of the GCM.

Yes @gmao-rreichle that's the path to the bcs that the script fills in.
If there is a good reason to believe that it's garbage, I would insist on the script echoing a warning that it won't work.
But having someone go through a futile exercise is meaningless!

If there is a good reason to believe that it's garbage, I would insist on the script echoing a warning that it won't work.
But having someone go through a futile exercise is meaningless!

Agreed, and sorry again for the troubles.  The problem is that we rely on the others in GMAO to find these kinds of issues before we can document and (hopefully) fix them.  The cleanup and reorganization of the bcs and remap_restarts is a massive undertaking, and the ocean bcs have been particularly gnarly.  We do what we can, but we can't possibly test everything on our end.  Someone has to be the guinea pig.   Thanks for being patient.

@gmao-rreichle no worries at all! Thank you!
It is a massive undertaking to maintain and develop an earth system model like ours!
Whenever @GEOS-ESM/gmao-si-team gets to it. I have a restart set that works.

@sanAkel : We are a bit lost as to what the exact problem is.  Per @biljanaorescanin on the separate Teams chat, there was an issue in some of the archived bcs files, but I understand that has been corrected now, and those were not used by you anyway.  Besides documentation fixes, the only remaining problem (i.e., something not working) that I can see in the comments above is your crash report on Milan:

A run from those restarts left me with a super interesting crash! :-o /discover/nobackup/sakella/free_run_gold_per/slurm-28387344.out

Can this issue be summarized as "The coupled model does not work on Milan" ?  If so, maybe start a new issue, or change the title of this issue and confirm in a new comment what exactly the problem is.   Thanks!
cc: @weiyuan-jiang

@sanAkel : We are a bit lost as to what the exact problem is.  Per @biljanaorescanin on the separate Teams chat, there was an issue in some of the archived bcs files, but I understand that has been corrected now, and those were not used by you anyway.  Besides documentation fixes, the only remaining problem (i.e., something not working) that I can see in the comments above is your crash report on Milan:

A run from those restarts left me with a super interesting crash! :-o /discover/nobackup/sakella/free_run_gold_per/slurm-28387344.out

Can this issue be summarized as "The coupled model does not work on Milan" ?  If so, maybe start a new issue, or change the title of this issue and confirm in a new comment what exactly the problem is.   Thanks!
cc: @weiyuan-jiang

@gmao-rreichle I edited this issue title.

Thanks, @sanAkel.  If I can rephrase the title change of the present Issue in my own words, you're finding that remap_restarts.py produces bad restarts on Milan with the "develop" version?  But @biljanaorescanin told me (somewhere in the depths of Teams) that she can reproduce binary identical restarts across SLES12 and SLES15.  Since remap_restarts.py is in the GEOS_Util external repo, which only has a "main" branch (not "develop"), is it possible that the GEOS_Util release in components.yaml of the coupled model is out of date?

I used this PR to make restarts: https://github.com/GEOS-ESM/GEOS_Util/pull/53
SLES12 vs SLES15 are zero diff. So if SLES12 created restarts worked SLES15 has to work as well.
Here is full path SLES15:
/discover/nobackup/borescan/brisi/util_pr_43/feb_2/testing/c180_ica_72_mom5_to_c180_nl3_72_mom6_sles15
Here is full path SLES12:
/discover/nobackup/borescan/brisi/util_pr_43/feb_2/testing/c180_ica_72_mom5_to_c180_nl3_72_mom6_72
Maybe problem is not restarts but coupled model setup on SLES15?
I can double check main, but we only changed upper restarts on PR link vs remap that shouldn't affect coupled run to fail but just give diff starting point.

@biljanaorescanin, @gmao-rreichle, as time permits, I'll re- clone and test all again- as long as discover file system is stable.
Please let's pause until then.
Meanwhile if @weiyuan-jiang wants to troubleshoot, that's fine with me!

I'll re- clone and test all again- as long as discover file system is stable.

@sanAkel:  Before you get to build and run, I suggest looking at the release/branch info for GEOS_Util and GEOSgcm_GridComp.  If the "wrong" (outdated) versions are associated with the coupled model, remap_restarts.py wouldn't be expected to work.

@gmao-rreichle point noted.
For the case/testing I have right now, indeed I have GEOS_Util at develop and rest v11.5.1, see above.

For the case/testing I have right now, indeed I have GEOS_Util at develop and rest v11.5.1, see https://github.com/GEOS-ESM/GEOS_Util/issues/55#issue-2113919792.

Sorry, @sanAkel, I missed that you already provided all these details.  Given this info and @biljanaorescanin's success in reproducing identical restarts on SLES12 and SLES15, I'm having a hard time believing that there's anything wrong with remap_restarts.py per se that would have caused your coupled model failure.  It's still possible that something was wrong in the configuration of your remapping of the restarts, but if remap_restarts.py produced the expected files, that's also unlikely.  I agree, running the test again and seeing if the failure is reproducible is the logical next step.

Will reopen this issue, if I can reproduce the error!


File icons incorrect when file extensions are not lowercase

Directory Lister Version
v3.7.3 (and all prior versions)
Describe the bug
File icons are not properly showing up when file extensions are not lowercase.
For example, a file named directory-lister.svg will show the correct (image) icon but if if named directory-lister.SVG or directory-lister.Svg it will show the default (blank file) icon.

Fixed in v3.7.4

Fixed in v3.7.4


Password Manager will not save new password since Chromium 80

Describe the bug
Password manager will not save new detected password in login fields, auto filling of loaded password will still work.
To Reproduce
Steps to reproduce the behavior:

Go to any website login
Fill in any in/valid credentials
Try save password to password manager
Open password manager for current site
"No password saved for this site"

Expected behavior
Password manager should save new passwords.
Environment (please complete the following information):

OS/Platform and version: Windows 10 Enterprise Version 2004 OS Build 10.0.19041.450
ungoogled-chromium version: 84.0.4147.135-1 built by tangalbert919

Additional context
Flags
--flag-switches-begin --user-data-dir=..\profile --no-default-browser-check --allow-outdated-plugins --disable-logging --disable-breakpad --disable-machine-id --disable-encryption --extension-mime-request-handling=always-prompt-for-install --fingerprinting-canvas-image-data-noise --fingerprinting-canvas-measuretext-noise --fingerprinting-client-rects-noise --max-connections-per-host=15 --profile-directory=Default --enable-logging --v=1 --disable-extensions --flag-switches-end
chrome_debug.log

What platform are you running on?

For some reason I forget to attach the platform information.

OS/Platform and version: Windows 10 Enterprise Version 2004 OS Build 10.0.19041.450
ungoogled-chromium version: 84.0.4147.135-1 built by tangalbert919

I thought ill add something too..
I have the same Problem also.. The browser doesnt even ask me if i want to save the PW...
Im using windows 10 LTSC 1809  Up to Date..
Flags of Chromium:
ChromiumCommandLine=--flag-switches-begin --user-data-dir=..\profile --no-default-browser-check --allow-outdated-plugins --disable-logging --disable-breakpad --flag-switches-end --enable-features=WebUIDarkMode --force-dark-mode --disable-windows10-custom-titlebar
Chromium Version:
Chromium v85.0.4183.121-r782793 - ungoogled
https://github.com/macchrome/winchrome/releases/
same with this version...
85.0.4183.102-1
https://github.com/Eloston/ungoogled-chromium/releases
Best Regards..

@raisehero That's strange. I've had problems saving passwords on Linux via GNOME Keyring, but I've never had any problems saving credentials on Windows (I'm also running Windows 10 Enterprise 2004). Unfortunately, I currently lack knowledge of Chromium's password manager to debug this issue.
@B-eT-a Are you sure you enabled "Offer to save passwords" in chrome://settings/passwords?

The regression, and #1183 all begin after Ungoogled Chromium 80. 79 doesn't have both issues.

@Eloston
aye, im 100% shure that the option "Offer to save Passwords" is enabled..
I also double checked :)
Best Regards

I've tried transplanting the "Default" profile folder (--profile-directory) to a new installation and this bug and #1183 will cease to exist.
Comparing files from both user data folder (--user-data-dir) and deleting folder and files from the old user data folder leads to the root cause of the problem.
This "Local State" Local State.zip file inside the user data dir will cause both bugs (#1182 and #1183) to manifest. This file was created from before Chromium 80.
Compare to this "Local State" file which is created on Chromium 86.
Local State.zip
Unfortunately this leaves the newly saved password encrypted despite --disable-machine-id --disable-encryption is passed…

Closing, issue stems from a common root cause which is related to platform specific issue: ungoogled-software/ungoogled-chromium-windows#58


Pass custom_objects as args in TocoConverter.from_keras_model_file

Pass custom_objects as an argument to TocoConverter.from_keras_model_file() to allow for things like custom Keras layers.

Nagging Assignee @rmlarsen: It has been 23 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rmlarsen: It has been 38 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rmlarsen: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@benjamintanweihao could you please resolve the conflicts?

these files have been deleted in master , closing this PR


Naming Convention not Matched

https://stimulus.hotwired.dev/reference/controllers#naming-conventions

In filenames, separate multiple words using either underscores or dashes (snake_case or kebab-case: controllers/date_picker_controller.js, controllers/list-item-controller.js)

from the stimulus docs, I would think using the eagerLoadControllersFrom and lazyLoadControllersFrom would allow me to decide the conventions for my js controller file names
IMO kebab case is much less surprising in the mapping from filename to controller and better matches  JS conventions (don't get me wrong, ruby files should be underscored, but I like kebab for JS)
but the code for eager and lazy load:
export function eagerLoadControllersFrom(under, application) {
  const paths = Object.keys(parseImportmapJson()).filter(path => path.match(new RegExp(`^${under}/.*_controller$`)))
  paths.forEach(path => registerControllerFromPath(path, under, application))
}

only matches underscored names (unless you mix and match which is the worst of both worlds)
I think there should be a very small update to change RegExp(^${under}/._controller$) to RegExp(^${under}/.[_-]controller$)
and in controllerFilename it should also parse the import map and return the first match
e.g.
function controllerFilename(name, under) {
  const reg = RegExp(`^${under}/${name.replace(/--/g, "/").replace("-", "[_-]"}[_-]controller`)
  return Object.keys(parseImportmapJson()).find(path => reg.test(path))
}

You don't have to use the JavaScript helpers provided for loading. You can certainly also do so by hand. But the point of a convention is to stick with one way of doing it by default, so that's what we're doing here.


Remove child clone volume reference from the parent volume

Describe what this PR does
when a Cloned images retain a reference to the parent snapshot then
we cannot delete the volume. flattening will remove the reference
so that volume can be deleted even if it is cloned from a snapshot
Added a check in delete volume, if the volume contains any snapshot
we are not allowing the volume deletion, prior to volume delete
all its associated snapshots should be deleted first.
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>Related issues
closes #70, closes #227

don't merge this PR till I add snapshot e2e for the current code

@Madhu-1 quick review comments from me, PTAL.

@humblec Thanks for the quick review. addressed review comments PTAL

@dillaman can you confirm below-listed steps are correct to clone an image with a different version of ceph
steps to create rbd clone
ceph versions less than Mimic

[1]create an image with the `deep-flattern` option
[2]create a snapshot
[3] protect snapshot
[4]clone a new image from snapshot
[5]flattern newly  created image
[6]delete the newly created image[5] (this will be independent step can be one at last  also)
[7]unprotect snapshot
[8]delete snapshot
[8]delete image  create in  step[1](this image cannot be deleted if it has snapshots)

ceph version Mimic onwards

[1]create an image with the `deep-flattern` option
[2]create a snapshot
[3]clone a new image from snapshot
[4]flattern newly cloned image
[5]delete the cloned image[3]  (this will be independent step can be one at last  also)
[6]delete image created in [1] with `rbd rm --rbd_move_to_trash_on_remove=true`
[7]delete snapshot ([6] and [7] may interchange)
The image moved to trash will be automatically deleted once the snapshot is deleted?

@humblec @j-griffith @ShyamsundarR let me know your thoughts on below query

what versions of ceph we should support with csi?
if version less than Mimic do we need to handle cloning differently

use clone v1 for ceph version less than Mimic
use clone v2 for Mimic later

based on the answer I will update this patch (this patch will help to finish smart cloning work)

@dillaman @humblec @ShyamsundarR @j-griffith  can I get an answer to the above questions?

@Madhu-1 The issue w/ deep-flatten + k8s is that by default and design, the krbd kernel driver is used. This driver is not tied to a Ceph release and doesn't support deep-flatten until v5.1.
Since deep-flatten is only required once a snapshot is created on a cloned image, perhaps you can just defer the flatten operation until the first snapshot is created on the cloned image (since it may never occur for most images and therefore saves disk space) and/or run flatten immediately after cloning if deep-flatten isn't enabled.
One important note is that if the exclusive-lock feature is enabled, you cannot run the flatten operation when krbd is using the image, so it would need to be run immediately after the clone operation.

@Madhu-1

what versions of ceph we should support with csi?

I don't have enough visibility in to the field to know the best answer here.  My thought was that we would not have a limitation on ceph version, but provide different capabilities based on version.

if version less than Mimic do we need to handle cloning differently
    use clone v1 for ceph version less than Mimic

Or don't support cloning in the capabilities when the version is < Mimic?  I don't know the implications of this in terms of customers in production with Kube; but given that cloning is alpha in 1.15 it's pretty "new" so setting a cut off doesn't seem heavy handed to me.

    use clone v2 for Mimic later

Same note as above, it's up to you though if you want to have two implementations and select based on ceph version that's great; so long as the implementations are clean and easily separated.  I would hate to see too much overhead or maintenance cost by trying to support both.

what versions of ceph we should support with csi?
if version less than Mimic do we need to handle cloning differently
use clone v1 for ceph version less than Mimic
use clone v2 for Mimic later

@Madhu-1 imo, from >v1.0 onwards we will be supporting nautilus, especially for clone its good enough to declare we support this feature  ONLY for nautlius.

closing this one, as flatten will be taken care in volume cloning PR https://github.com/ceph/ceph-csi/pull/693


RollerShutter not recognized

Describe The Bug:
When connecting Tahoma Switch to Homebridge, the Roller Shutter (RTS) is not recognized as a screen in Homebridge.
The debug logs show the device, but the logs also show "0 screens".
To Reproduce:
Initialize Tahoma Switch
Connect RTS-based Roller Shutter to Tahoma Switch
Install this plugin to Homebridge
Expected behavior:
As I have connected one RTS-based Roller Shutter to the Tahoma Switch, I would expect this to show up in Homebridge.
Logs:

Plugin Config:
{
"name": "Tahoma",
"service": "somfy_europe",
"username": "XXXXXXXXXX",
"password": "XXXXXXX.",
"debug": true,
"platform": "Somfy TaHoma Screen"
}
Environment:

Plugin Version: v1.0.21
Homebridge Version: v1.8.4
Node.js Version: v20.17.0
Operating System: DietPi v9.7.1

Hello all,
I'm facing the same problem.

Hi,
can you please add the log too?

Sure, here it is:.
I am missing the Device Markise that formerly worked.
Do you need anything else?

Changed

[package]: Update to eslint, jest and prettier flat config.

I have no way to test it against your screen.
Can you try and let me know please?
My Best.

Well done! Thanks for fixing it.


Add extra filtering to  vectorStore?

I want to add userId to documents table so vectorStore only retrieves documents for that userId, any ideas?

I think you can achieve that by using setting up row level security.
Add new RLS to your documents table with following USING and WHERE expression:
((auth.uid())::text = (metadata ->> 'user'::text))

and my metadata contains user field with users uuid
metadata: {
   'user': 'e1965a54-4760-4....'
}

Thanks yeah that is my plan too.

I'm also searching for a solution to this. I want to allow users to further narrow down what documents they want to search over.
I could not find any existing way for this in the current supabaseVectorStore implementation here.
I guess one would need to raise a PR in the langchain main repo for this?

Hi, there is an open PR in the main repo enabling this which we plan to merge and release soon https://github.com/hwchase17/langchainjs/pull/905


Keep PayPerEmail order pending after failed payment

Is there a way that only PayPerEmail orders don't get cancelled after a failed payment. I know there is a global option, but is it possible to only have this for PayPerEmail?

I disabled the cron option a while ago. The orders are immediately cancelled. Could have sworn this wasn't the case a while ago. It means we have to recreate the order and send out a  new link everytime a payment failed which is pretty inefficient. If it's possible it would be really great to have an option to keep the PayPerEmail order pending.


nss: refactor into latest and esr

Description of changes
This should ease maintenance of firefox while having a supported version for everything else, so the mass rebuilds can go through staging and nss_latest can just be bumped and both can be backported, on the release and one to staging.
cacert still uses nss_latest, so we always have an up to date certificate store.
Things done

Built on platform(s)

[x] 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.05 Release Notes (or backporting 21.11 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

[x] Fits CONTRIBUTING.md.

cacert still uses nss_latest, so we always have an up to date certificate store.

That's a little confusing sentence.  It has a separately controlled version, and I think it only makes sense to update when the CA list changes, as seen on https://wiki.mozilla.org/NSS:Release_Versions

firefox/common.nix, thunderbird and similar: perhaps use the ESR version of NSS for ESR versions of these packages?  My understanding is that the ESR NSS is created primarily to support those, even though I don't recall any issues from us using newer NSS in there.
I'm not sure what version requirements are there in other packages, but I guess we'll see when we attempt to rebuild them – and switch to _latest where needed.  The most important dependents are chromium- and electron-based, perhaps?

cacert still uses nss_latest, so we always have an up to date certificate store.

That's a little confusing sentence. It has a separately controlled version, and I think it only makes sense to update when the CA list changes, as seen on https://wiki.mozilla.org/NSS:Release_Versions

Yes, totally. What I meant by that is that the excellent cacert update script already checks if nss_latest is available and uses it, if it is. AFAIR it also checks if the output changed (or something like that) so you wouldn't even need to check the wiki page to know if something changed.

firefox/common.nix, thunderbird and similar: perhaps use the ESR version of NSS for ESR versions of these packages?  My understanding is that the ESR NSS is created primarily to support those, even though I don't recall any issues from us using newer NSS in there.

I'm not sure what version requirements are there in other packages, but I guess we'll see when we attempt to rebuild them – and switch to _latest where needed.  The most important dependents are chromium- and electron-based, perhaps?

Does chromium even use nss? When I looked into the package I only saw the DRM plugin using it.
electron I seem to remember though. I think I already broke something there once, when I did something with nss.

@ofborg eval
@ofborg test firefox

Bisect says firefox stopped building on staging after eb9c616c79596c9ff43ec9e7ced46c4739a16047 nss_latest: 3.76.1 -> 3.77:
$ nix build -f. firefox
...
In file included from /build/firefox-98.0.2/security/certverifier/CertVerifier.cpp:14:
/build/firefox-98.0.2/security/manager/ssl/CSTrustDomain.h:50:28: error: no type named 'SignedDigest' in namespace 'mozilla::pkix'
      const mozilla::pkix::SignedDigest& signedDigest,
            ~~~~~~~~~~~~~~~^
...

Can you retest against firefox 99.0?

firefox-99 seems to fail in a very similar way:
In file included from Unified_cpp_certverifier0.cpp:47:
/build/firefox-99.0/security/certverifier/OCSPVerificationTrustDomain.cpp:63:11: error: unknown type name 'SignedDigest'
    const SignedDigest& aSignedDigest, Input aSubjectPublicKeyInfo) {
          ^
/build/firefox-99.0/security/certverifier/OCSPVerificationTrustDomain.cpp:74:11: error: unknown type name 'SignedDigest'
    const SignedDigest& aSignedDigest, Input aSubjectPublicKeyInfo) {
          ^

I guess eb9c616c79596c9ff43ec9e7ced46c4739a16047 should be alright to revert and just re-revert when Firefox 100, which will require it, arrives?

Reverted in 79a5b548cc48770c062a6a60503628017ea0855e.

None of these updates needs to get to master fast, right?  (ATM they're not included in the current staging-next iteration.)

Bump reinstated in #171332 and bumped further to 3.78.


[RU] Add 'basics/comprehensions' lesson translation

@brain-geek can you take a peek at this?

Looks good.

@nscyclone I've looked through once again - looks like there is a similar mistake in three places.
Otherwise, it's ready to merge

Thanks for your review, @brain-geek!
I've just fixed those three similar mistakes.

Thanks, @nscyclone


30 notify list crud

closes #30
blocked by #32

#32 has been merged, so this pr is no longer blocked 🥳


Components

Started to work but need to resolve dependency issues with the webpack alias.

lock file is re-introduced. causing issues with the module that this one is based on as well. See https://github.com/nuxt-community/auth-module/issues/734


javascript es6 instead of coffeescript

Hi,
Are you planning to use nature javascript (es6) instead of coffeescript
Thanks
Best Regards

If this ever happens, then yes. But we're not going to rewrite Meteor Blog just to rewrite it in ES2015. Hope this helps.


build: improve goreleaser, add testing capabilities, "head" release, docs, fixes #5821, fixes #5811

The Issue

Add a "head" release that is kept updated
Add testing capabilities via the ddev-test org
Add docs on how to test manually with goreleaser or the ddev-test org
#5821
#5811

How This PR Solves The Issue
Manual Testing Instructions
Automated Testing Overview

Related Issue Link(s)
Release/Deployment Notes

Tested this with release in https://github.com/ddev-test/ddev/releases/tag/v1.22.8-pr5824-goreleaser-fixes
The shell completion scripts are now gzipped.
https://github.com/ddev-test/homebrew-ddev-edge got updated (it's a prerelease so homebrew-ddev didn't get updated)
I think this is probably ready.


Show ??? for undefined wormhole types

Replace K162 with "???" if both sides of a connection are undefined.
Hopefully this will encourage pilots to edit connection details.
PS: apologies for double PR, I'm bad.

I think you would want to check specifically for K162 since otherwise, GATE<>GATE connections will be converted to ???

Right, thanks! Fixed it :smile:


Adding --mandatory to distribute-release

#692

For automatically build with some other services like Bitbucket for example, in "build configuration" section, there is no checkbox to distribute release as mandatory (it distributes as not mandatory version). Is there any way to make it mandatory automatically?


Removed pause on hibernate.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/219/
Hooray Jenkins reported success with all tests good!


Add notifications to Linode handler

I moved some things around to add notifications to the Linode handler.
I manually tested the DNS record updating functionality against Linode, and the notifications against Discord. Let me know if there are any other ways you'd like me to test.

Thanks a lot!


! Org question: is it good idea move this project to org & add co-mantainers / developers?

Hello everyone!
I see this project is more or less interesting for people. I'd like to develop it, but I have no enough free time, sorry :(
So here is idea how this situation can be solved:

Move this repository from https://github.com/io-developer into https://github.com/io-develop
Create core team and add co-mantainer / co-developers
...

Profits:

More independent collaboration
Faster way to solve issues and apply PRs

Possible issues:

I don't know how to do it smooth and right with no breaking (composer integration and etc.)
Different views on project future
Collision / conflicts

You're welcome to left your thougts.
@bessone you're number one candidate to be co-mantainer. What do you think?

I've been using this package heavily in one of my projects I'm happy to support this however I can.
You can transfer from settings to an org account which will transfer everything over and GIT will automatically redirect the URLs as I understand it:

All links to the previous repository location are automatically redirected to the new location. When you use git clone, git fetch, or git push on a transferred repository, these commands will redirect to the new repository location or URL. However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL.

https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/transferring-a-repository

It's good. However composer.json should be updated by users I guess (for long term cases)
For now I have composer page here - https://packagist.org/packages/io-developer/php-whois
I guess new page should be created also too (for long term cases)

yeah if I remember correctly I think packagist follows the internal redirects as well. It would be better if users used the newer vendor name tho.


Fix new api java<->json conversion problem #1859

According to the jackson doc: https://jersey.java.net/documentation/latest/user-guide.html#json.jackson
I added one line to the code and resolved the problem.

Thanks for pull request. I still don't quite understand why it works fine for me, but not for you.


Remove local-gadget from the default build target

The local-gadget target in our Makefile requires having CLang and libbpf-dev installed locally, which are not considered required dependencies for building Inspektor Gadget. The default build target should only include targets that can be built with the listed tools.
This change removes local-gadget from "build", and creates an "all" target that includes local-gadget
How to use / Testing done
Run make and see how it doesn't call CLang outside of docker.
Run make all and see how it does (or fails to, if you machine doesn't have CLang and/or libbpf-dev).

CI is failing because of the integration tests but the provided output is not enough to determine what was the cause. I had already filed an issue to improve the output (https://github.com/kinvolk/inspektor-gadget/issues/567). For now, please re-run the failed job.


Ee 21998

Close this pull request.
Changes included here: https://github.com/RWS/languageweaver-sdk-samples/pull/19


access: approvers

Hi,
See https://golang.org/wiki/GerritAccess
I'd like to request "approvers" access.
I see many times like https://go-review.googlesource.com/c/go/+/539579 such trivial and obviously right change CL, I used to vote codereview + 1 promote the review process of this kind of CL.
I want to be able to vote codereview+2 to approve this kind of CL.
Gerrit user<EMAIL_ADDRESS>

@gopherbot add NeedsDecision

cc @golang/release

No updates here?

cc @golang/release

Maybe I should CC on Monday?
cc @golang/release

Apologies for the delay in reviewing this request, our notifications about this request got missed.
Thanks for your contributions and making this access request. The "approvers" access permits reviewing and submitting CLs across the entire Go project as documented https://go.dev/wiki/GerritAccess#approving-cls-approvers, so it needs a longer history of contributions and demonstrated familiarity with the Go project before granting access can be considered. It looks like you're off to a strong start, but it's still early. I'm going to close this for now, but please keep up the good work and feel free to reapply at a later time.


aos-animate class doesn't apply

Hello there!,
I really appreciate your lib which has made things easy; for now it's been couple of days I'm trying to fix that issue about " 'aos-animate' class isn't applied while only class applied is 'aos-init' which makes the element invisible " although I have couple of aos animation working correctly  but were preset before.
briefly: aos-data attribute works on some normally "which has been there long time ago" but any new element I try to add aos-data it goes invisible as the only class applied aos-init.
fixing: made sure of the last version linked, tired to refresh and refreshHard on load, Aos.init(); is placed before /body tag.
any advise pls!

Hi! I had same issue and I found this fix: https://github.com/michalsnik/aos/issues/182 and it works well for me

Seems like there is a solution ☝ If it doesn't work for you feel free to reopen this issue @risha700 :)

Thanks Guys


[SoC2019]Support more security choose

Currently the security support of Dubbo is not enough. We should provide more feature to use. Such as TLS support,  Authorization，high-level encrypt data.
Required feature

TLS support

1.1 Support TLS , maybe you can refer the netty implements.
1.2 Use the same port as the TCP port , default is 20880.  And the server should consume the invocation of simple TCP or TCP+TLS.
Options feature

Authorization

2.1  You can add some authorization between client and server.
2.2  You should focus on client and server communication, but not on registration.
2.3  This feature is option.
If you are interested in this topic, please refer to : https://github.com/apache/incubator-dubbo/issues/4001

I am interested in this idea.

You can apply for the topic directly. If you have any question, you can leave a message here.

What a pity! My undergraduate graduation project is all about adding security feature to Dubbo (including TLS support), but now I'm having a job to do and unable to participate in this. Hope someone could pick this up and do a better job !

@cvictory That is such a great news for Dubbo users.
Do you have an update regarding the progress of these security support features in Dubbo code base?
Very eager to see version of Dubbo with these features integrated
Best


Command /usr/bin/codesign failed with exit code 1

Hi ! I have a problem. When I compile on Xcode, I have this error :
CodeSign /Users/xavier/Library/Developer/Xcode/DerivedData/Unity-iPhone-fpeszmwfkauotdedryaxpkpelaly/Build/Products/TouchOrDie.app/Frameworks/GoogleOpenSource.framework
cd "/Users/xavier/Desktop/DELAMERDE/untitled folder 12/opiujk"
export CODESIGN_ALLOCATE=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate
export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
Signing Identity:     "iPhone Developer: Xavier BERAUD (79ZUKS9QP2)"
/usr/bin/codesign --force --sign E94204C8692B2240116F52F9147FF163E658C9D3 --preserve-metadata=identifier,entitlements,resource-rules /Users/xavier/Library/Developer/Xcode/DerivedData/Unity-iPhone-fpeszmwfkauotdedryaxpkpelaly/Build/Products/TouchOrDie.app/Frameworks/GoogleOpenSource.framework

Warning: usage of --preserve-metadata with option "resource-rules" (deprecated in Mac OS X >= 10.10)!
/Users/xavier/Library/Developer/Xcode/DerivedData/Unity-iPhone-fpeszmwfkauotdedryaxpkpelaly/Build/Products/TouchOrDie.app/Frameworks/GoogleOpenSource.framework: bundle format unrecognized, invalid, or unsuitable
Command /usr/bin/codesign failed with exit code 1
I tried a lot of things but I still can't figure this out... Couls you please help me ?!
Thank you.

Is it really related to SOOMLA?
Sometime code-signing error occur when you don't have a valid signing key. Try to create a good signing key and work with that.

@robinDesBits have you had any luck with this? was this resolved for you?

Sorry, late answer. We solved all our problems by removing google + and twitter. Just Facebook is working fine, maybe we will try again later, but for now we have submitted our app without it.

@robinDesBits a shame we couldn't help you to get this working.
So, are you going to try and use Twitter and Google+ soon?

Don't worry, it's not a big deal, Facebook was the more important for us.
I don't know, we are waiting apple's validation, then I will probably work on it again.

@robinDesBits ok, so should I leave the issue open? or will you create a new one if need be?

Outdated issue. Closing. Open if still relevant.


Fix cloning the bb8::Pool

bb8::Pool derivces Clone, but this does not make the struct cloneable
if the generic type parameter is not cloneable. However, the struct is
cloneable with any type parameter, because it internally uses an Arc.
Implementing Clone manually and calling the Arc::clone method does
the trick.
Background: I'm writing a bb8 middleware for Gotham. There, I want to have a struct that holds a pool instance and that can be cloned:
struct MyMiddleware<M: ManageConnection>
    pool: Pool<M>,
}

However, I cannot use .clone() in generic implementations of the struct. With this patch, Rust knows that any instance of Pool implements Clone and thus allows me to call the method.

Thanks!


[ENH] Update logo

Summary
PR aims to propose new logo variants generated through an open-source designing tool.
The Scivision logo was created from early interactions between project members in 2021. The logo features a koala i.e. a sort of avatar for representing so-called scivisioners holding a lupe i.e. to highlight our key service as a toolkit for datasets and models discovery and mounted in a lab tube i.e. science. The logo name variant uses the koala to replace the third character, the letter i.
The current logo was designed in Powerpoint. It uses Avenir Next which is a Microsoft-licensed font (only for home, student, or non-commercial use) and icons without any royalty or copyright to worry about.
I propose to replace the current logo files with new ones generated in Penpot, an open-source design and prototyping platform. This platform is more collaborative and suited to generate high-quality vector graphics than MS Powerpoint. Furthermore. anyone interested in drafting the logo can access and edit in penpot with Editor or Admin roles.
List of changes proposed in this PR (pull-request)

Replace logo.png and logo_name.png files.
The proposed logo with name replaces Avenir Next by Monserrat (SIL Open Font License). This font type is more suited to multiple purposes including commercial use. Icons are ok.
A minor modifications of the logo_name.png file is the white offset which I've found too large.

What should a reviewer concentrate their feedback on?

Logo variants
Impact of a smaller white offset in the logo with name
Where in the documentation, front-end and slide decks we should update the logo if accepted

ps. We should record somewhere in the scivision repo or front-ends our brand origins.

@edwardchalstrey1 thanks for testing it in the front-end! I already validated the new logo in a scivision group meeting last week so I think it's good to merge then.


Remove non used version check

This line checks if the datapackage version is bigger than "0.2.1" https://github.com/open-AIMS/ADRIA.jl/blob/916e947b9a7f22f1d69cd7137a1de2ba18bb530a/src/ExtInterface/ADRIA/Domain.jl#L274
BUT it's impossible to load a datapackage with that version, because it is not listed here: https://github.com/open-AIMS/ADRIA.jl/blob/916e947b9a7f22f1d69cd7137a1de2ba18bb530a/src/ADRIA.jl#L102
So we should just remove the check.

@ConnectedSystems FYI

The first link points to a line that checks if the start year is earlier than the end year?

This is the line I meant:

@ConnectedSystems updated the description to match the right line - that in my branch must be different.

Bigger or equal to.
The check there is when a very old datapackage was being loaded.
I suggest putting in a deprecation warning and mark for removal later.

Bigger or equal to.
The check there is when a very old datapackage was being loaded.
I suggest putting in a deprecation warning and mark for removal later.

But any datapackage with version smaller than that will never get to this line because it wont pass this one: https://github.com/open-AIMS/ADRIA.jl/blob/916e947b9a7f22f1d69cd7137a1de2ba18bb530a/src/ExtInterface/ADRIA/Domain.jl#L269C36-L269C36

Yes I see - then I agree, it should be removed.


Rename BioSharing to FAIRsharing

Apparently I forgot to open this PR!
Renames BioSharing to FAIRsharing as per https://trello.com/c/SzTkfAjq/70-bio-sharingorg

staged at https://snoopycrimecop.github.io/www.openmicroscopy.org/about/


fix: support 'AUTHTYPE' as alias for 'AUTH_TYPE' config property

:tada: This PR is included in version 9.12.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Use CMake INSTALL to simplify build process

We really should make use of cmake  INSTALL  support, and just add all our required dlls as install(DIRECTORY 3rd_party/bin...
INSTALL is a step that can copy files to target directory, including dlls, so if we have install target we can skip some custom command stuff for the build dlls

We should pre-set the target path to match current out dir one.
Qt-creator has support for deploy-before-run in Projects view, Run settings deploy steps. So running/debugging application will cause it to be properly installed first in the target directory.

Would make #509 obsolete

Pushing back to v0.7 as we have a pretty full plate for the 0.6 release.