Unable to open database with enabled vfs=win32-longpath option

I need to use databases in paths that are longer than 1024 characters. Therefore sqlite has different VFSes (https://www.sqlite.org/vfs.html).
But if i set vfs=win32-longpath in my connecton string i cannot open any database that is encrypted. Also dbs in paths shorter than 260 characters cannot be opened any more. I use RC4 and chacha20 encryption.
But when i remove encryption from the database it works without any problems with paths shorter than 260 characters and also with paths with more than 1024 characters.
So it must be something wrong when there is an encryption for the db.
I use an URI connection string like this:
"file:///E:/DatabaseFilename.db?vfs=win32-longpath&cipher=chacha20&key=XXXX"
Is there a bug in the SQLite3MultipleCiphers implementation? Or am i doing something wrong?

I need to use databases in paths that are longer than 1024 characters. Therefore sqlite has different VFSes (https://www.sqlite.org/vfs.html).

I'm aware of that.

But if i set vfs=win32-longpath in my connecton string i cannot open any database that is encrypted.

The VFS win32-longpath does not support encryption on its own, so you can't create or open an encrypted database with this VFS alone.
On initialization SQLite3 Multiple Ciphers creates a VFS shim for the default VFS of the operating system (for Windows that is the VFS win32). The name of this VFS shim that supports encryption is multipleciphers-win32.
If encryption support for other VFSs is required, a VFS shim has to be created for those VFSs, too.

Also dbs in paths shorter than 260 characters cannot be opened any more. I use RC4 and chacha20 encryption.

The problem does not depend on the encryption scheme or the path length, but only on the VFS in use.

But when i remove encryption from the database it works without any problems with paths shorter than 260 characters and also with paths with more than 1024 characters.

Of course, the VFS win32-longpath supports unencrypted databases with long as well as short paths.

So it must be something wrong when there is an encryption for the db. I use an URI connection string like this: "file:///E:/DatabaseFilename.db?vfs=win32-longpath&cipher=chacha20&key=XXXX"

I agree that it would be nice to select a VFS with encryption support without requiring to set up a VFS shim manually. In the current implementation a VFS shim needs to be created in advance.

Is there a bug in the SQLite3MultipleCiphers implementation? Or am i doing something wrong?

The SQLite3 Multiple Ciphers implementation is correct, at least as far as I know. However, unfortunately the documentation lacks the information what needs to be done to be able to use other VFSs than the default one with encryption support.
The SQLite3 Multiple Ciphers API includes the function
int sqlite3mc_vfs_create(const char* zVfsReal, int makeDefault);

that can be used to create a new VFS shim with encryption support, In your use case you have to call
int rc = sqlite3mc_vfs_create("win32-longpath", 0);

This creates a VFS shim with encryption support using the VFS win32-longpath for the real file access. The name of the VFS shim will be multipleciphers-win32-longpath - and that name can then be used in the vfs URI parameter (vfs=multipleciphers-win32-longpath).
I will complement the documentation in the near future. Additionally, I will check whether I can implement an easier way to use any of the available VFSs with encryption support.

Oh great. Now it works perfectly.
Thank you very much.

Oh great. Now it works perfectly. Thank you very much.

You are welcome. So, I will close the issue.
In the meantime I experimented a bit. As a result the next release will allow to specify a VFS name with encryption support without the need to call sqlite3mc_vfs_create(). Simply using a VFS name with the "multipleciphers-" prefix will instantiate the VFS shim if if doesn't already exist. Calling sqlite3mc_vfs_create() will only be necessary, if a certain VFS shim with encryption support should be made the default VFS.

@utelle
Maybe you have also experiences with this Problem. In windows everything works fine with long paths and VFS set (win32-longpath). But today i tried to use long paths in linux (Ubuntu 20.04.5 LTS (Focal Fossa)) with my .Net5 application.
I tried without setting a special VFS but when the path is longer than 512 characters i get an InvalidDatabaseException when trying to open the database.
All documented VFSes for unix seems not to solve the problem.
Do you have an idea? Or do you know if there exists a limitation in unix?

Maybe you have also experiences with this Problem. In windows everything works fine with long paths and VFS set (win32-longpath). But today i tried to use long paths in linux (Ubuntu 20.04.5 LTS (Focal Fossa)) with my .Net5 application.
I tried without setting a special VFS but when the path is longer than 512 characters i get an InvalidDatabaseException when trying to open the database.

That is a hard coded limitation in the SQLite sources. For Unix-like systems there is a symbol MAX_PATHNAME defined:
#define MAX_PATHNAME 512

This number is fixed and is used for all VFSs.

All documented VFSes for unix seems not to solve the problem.

Right. All Unix VFSs use the same limit for pathnames.

Do you have an idea? Or do you know if there exists a limitation for sqlite in path length in unix?

AFAIK the limitation to 512 characters in SQLite is arbitrary. Most Linux systems should support pathname with up to 4096 characters in total.
So, IMHO there are 2 options:

You use symbolic links to shorten the effective pathname length, so that the limit of 512 characters is not exceeded, or
You redefine the symbol MAX_PATHNAME by changing it in the sources to#define MAX_PATHNAME 4096

For most Linux file systems the maximum total pathname length is 4096.

So, IMHO there are 2 options:

You use symbolic links to shorten the effective pathname length, so that the limit of 512 characters is not exceeded, or
You redefine the symbol MAX_PATHNAME by changing it in the sources to#define MAX_PATHNAME 4096

We already use a self compiled version because we also need RC4 encryption . So i set MAX_PATHNAME to 4096 in the source.
Now it works. Thanks.

In the meantime I experimented a bit. As a result the next release will allow to specify a VFS name with encryption support without the need to call sqlite3mc_vfs_create(). Simply using a VFS name with the "multipleciphers-" prefix will instantiate the VFS shim if if doesn't already exist. Calling sqlite3mc_vfs_create() will only be necessary, if a certain VFS shim with encryption support should be made the default VFS.

I also tried your newest version (1.6.0) with your extension without the need to call sqlite3mc_vfs_create().
It works perfectly. Thank you very much for your great and fast support.

So, IMHO there are 2 options:

You use symbolic links to shorten the effective pathname length, so that the limit of 512 characters is not exceeded, or
You redefine the symbol MAX_PATHNAME by changing it in the sources to#define MAX_PATHNAME 4096

We already use a self compiled version because we also need RC4 encryption.

I assume you know that SQLite3 Multiple Ciphers supports the RC4 variant that was included in prior versions of System.Data.SQLite.

So i set MAX_PATHNAME to 4096 in the source. Now it works. Thanks.

I asked about MAX_PATHNAME on the SQLite forum. If we are lucky, its value will be configurable in a future SQLite version. However, I'm not too optimistic as another minor change I asked for in the past never happened. If the next SQLite version does not make MAX_PATHNAME configurable, I can add a patch on my own.

I also tried your newest version (1.6.0) with your extension without the need to call sqlite3mc_vfs_create(). It works perfectly. Thank you very much for your great and fast support.

You are welcome.

Now i have another question to the same subject.
We have the problem that we have to load/unload our assemblies (C#, .NetFramework) dynamically from different versions in different AppDomains. For every version of our assembly there is also the according sqlite-multicipher-dll for this version.
Unfortunately it is not possible to unload native dlls (also the sqlite-multicipher-dll). So if a sqlite-multicipher-dll first was loaded in an earlier version which does not support your new feature yet (creating vfs without calling sqlite3mc_vfs_create), we will get an error if we load and use our actual assembly which assumes that the vfs will be created automatically because in this case the older sqlite-multicipher-dll is used.
I think due to compatibility reasons the only solution is to call sqlite3mc_vfs_create in our new version because older versions of your sqlite-dll already has this method since a longer time. So our new versions also works with an older sqlite-multicipher-dll.
Now my question. Do you think it will be a problem if we call sqlite3mc_vfs_create multiple times in the same process in different AppDomains? Because it will be difficult to know if sqlite3mc_vfs_create was already called by some AppDomain.

We have the problem that we have to load/unload our assemblies (C#, .NetFramework) dynamically from different versions in different AppDomains. For every version of our assembly there is also the according sqlite-multicipher-dll for this version.

Can't you update older assembly versions to use a more recent SQLite3MC DLL? Isn't that a legitimate requirement to be able to replace an old assembly by a new one - to fix bugs or to introduce new features?

Unfortunately it is not possible to unload native dlls (also the sqlite-multicipher-dll). So if a sqlite-multicipher-dll first was loaded in an earlier version which does not support your new feature yet (creating vfs without calling sqlite3mc_vfs_create), we will get an error if we load and use our actual assembly which assumes that the vfs will be created automatically because in this case the older sqlite-multicipher-dll is used.

Well, yes, that is certainly a problem. However, the older SQLite3MC versions weren't able to use the VFS "win32-longpath" with encryption support, unless the VFS was explicitly created by the application in advance.

I think due to compatibility reasons the only solution is to call sqlite3mc_vfs_create in our new version because older versions of your sqlite-dll already has this method since a longer time. So our new versions will also work with an older sqlite-multicipher-dll.

Of course you can always create VFSs explicitly. However, I assume that your older assemblies didn't do that. So, you have to update your assembles anyway, and in that course you could update the SQLite3MC DLL as well.

Now my question. Do you think it will be a problem if we call sqlite3mc_vfs_create multiple times in the same process in different AppDomains? Because it will be difficult to know if sqlite3mc_vfs_create was already called by some AppDomain.

In principal, you can call sqlite3mc_vfs_create multiple times, but at the moment this will create memory leaks, because sqlite3mc_vfs_create doesn't check whether the same VFS was already created in a prior call. This is an oversight, and I will adjust the code for the next release.

Can't you update older assembly versions to use a more recent SQLite3MC DLL? Isn't that a legitimate requirement to be able to replace an old assembly by a new one - to fix bugs or to introduce new features?

For us there is no need to update older versions because new features or bugfixes are always introduced with a newer version or new service packs

In principal, you can call sqlite3mc_vfs_create multiple times, but at the moment this will create memory leaks, because sqlite3mc_vfs_create doesn't check whether the same VFS was already created in a prior call. This is an oversight, and I will adjust the code for the next release.

We have decided to check with sqlite3_vfs_find if the vfs already exists and only if it not exists we will call sqlite3mc_vfs_create . So we do not call it multiple times and there should not be any memory leaks.
Thanks again for your help.

We have decided to check with sqlite3_vfs_find if the vfs already exists (multipleciphers-win32-longpath) and only if it not exists we will call sqlite3mc_vfs_create . So we do not call it multiple times and there should not be any memory leaks.

Sure, by checking first whether the VFS already exists, you can easily avoid memory leaks.


Very long vim startup time caused by syntastic on OSX

After some troubleshooting, I discovered that the excessively long vim startup times I was experiencing
were caused by the Syntastic bundle.  I was seeing startup times of 15 to 30+ seconds for a new file.
The startup time drops to less than 1 sec without sytastic installed.
However, I was only seeing this on Mac OSX (Snow Leopard, Tiger), but not on Ubuntu Linux.   On all
of the machines I am using the same build and the same .vimrc & .vim/
Using the command "time vim -c q abc.txt" I get these times:
OSX (Snow Leopard)        OSX (Tiger)           Ubuntu(Lucid Lynx)
real  0m11.717s          real  0m23.673s        real  0m0.091s
user  0m0.841s           user  0m3.426s         user  0m0.070s
sys   0m0.295s           sys   0m1.391s         sys   0m0.000s
In subsequent runs the times improve (for OSX), but not significantly.
Are there any know issues that would cause this behavior on OSX and not Ubuntu?
Is there any way to not auto load the Syntastic bundle, but have it available on demand.
Thanks
Matt

That's pretty strange. The most likely thing is that it is running a syntax checker over the file you start vim with and  it is taking ages to return.
Is it happening with all filetypes or just some specific types?
For a temporary fix you could use this:
let g:pathogen_disabled = ['syntastic']
function! ActivateSyntastic() abort
    set rtp+=~/.vim/bundle/syntastic
    runtime plugin/syntastic.vim
endfunction

This tells pathogen not to load it at startup, and provides a function to do so on request. You can call it via ":call ActivateSyntastic()" or make a mapping or command to do so.


Workspace Error Reporting not Working as Expected

Hi @saoudrizwan and team,
First of all, I want to sincerely apologize for raising multiple issues in the Claude-Dev repository recently. I’ve been a heavy user of Claude-Dev to build programs, and I truly appreciate the tool's value.
However, since the upgrade to v1.7.0, which introduced the feature of automatically sending VS Code errors to the AI, the experience has become unusable for me. This feature is consuming tokens unnecessarily and distracting from the main tasks I instruct the AI to perform. As a result, I had to downgrade back to v1.6.9.
While I appreciate the update in v1.7.3, where only workspace errors are sent (and not warnings), and the additional instructions to the system prompt to avoid unrelated issues, I am still facing the same disruption in workflow. The AI continues to process errors and halts progress on the tasks I request.
I am kindly requesting that an option be added to DISABLE this automatic error-sending feature entirely. This would help bring back the focus to my instructed tasks and restore the smooth experience I had with Claude-Dev before the v1.7.x update.
Thank you so much for your attention, and I appreciate all the hard work your team is doing.

Hey @zytakeshi  @AstroMined @tsdevau @RobinGasi I'm sorry you guys are having trouble with this latest update. Before jumping to adding a toggle to disable error monitoring altogether, I'd like to see if it's possible to make claude dev smarter about how to handle them instead.

distracting from the main tasks I instruct the AI to perform

I have this instruction in the system prompt: "Focus on addressing errors and warnings relevant to your work, and avoid fixing pre-existing or unrelated issues unless the user specifically instructs you to do so." And if he can't fix an error in a reasonable number of attempts he's instructed to ask you for more information like up-to-date docs, to avoid him getting into a loop.
Are you seeing claude not follow these instructions? I'd love to get more details about what scenarios youre finding he gets distracted from the main task. Any information you could provide here would be helpful in helping me tune the system prompt to more broadly meet expectations for how it should handle errors. For example it would help to know more about the prompt you gave him, the errors that came up, and his responses to those errors.

Thank you so much for your attention, and I appreciate all the hard work your team is doing.

No 'team', it's just me! So I really appreciate your guys' patience as I figure out the best solution here.
In the meantime, you can add something like "Ignore VSCode Workspace Errors in environment_details as this information is not relevant to the task" in Settings > Custom Instructions.

Hi @saoudrizwan,
Thank you for your prompt response and for considering our feedback. I appreciate the efforts you’re putting into improving Claude-Dev.
Regarding the error reporting, I’ve noticed that it can be quite distracting as it often attempts to address non-existent errors. This detracts from my workflow and the tasks I need the AI to focus on. While I understand the intention behind this new feature, I believe it would be beneficial to have it as an optional setting. It would really help users like myself who prefer a more streamlined experience.
BTW, adding '''Ignore VSCode Workspace Errors''' DOES NOT FIX THIS.
I truly hope you can consider this request, as I’d rather not be stuck on v1.6.9 indefinitely.
Thank you for your understanding!

I’ve noticed that it can be quite distracting as it often attempts to address non-existent errors

Can I pls get a specific example of when this happens for you?

Pylint hadn't caught up with processing yet to remove the error, so Claude was operating on bad info. I've found Pylint can be pretty slow when you have multiple files open, so I'm sure this leads to confusion for Claude.

@AstroMined this is not good! The API request waits for your workspace to update before sending off errors to claude to avoid exactly this, operating on stale info. However there is a timeout of 5 seconds, so if your workspace hasn't updated by then, then it would send off whatever diagnostics exist at the end of that timeout. Does pylint take that long to update? Do you have an estimate of how long it usually takes? I can adjust this timeout value, but from personal testing found 5 seconds sufficient

Contrary to @zytakeshi 's experience, I have found that prepending my prompt with Ignore any linting errors or warnings provided by VSCode Workspace Diagnostics does stop it from attempting to fix those errors.
One memorable example of when Claude-Dev spent too much time trying to repair errors was on a SQLAlchemy datetime time that was defined a sercer_default=func.now(), which Pylint marks as an error: func is not callable. Claude tried about 6 different times to resolve this before settling on using lambda: datetime.now(timezone.utc).
The funny thing is, the first attempt Claude made at fixing it was actually a valid solution. However, Pylint hadn't caught up with processing yet to remove the error, so Claude was operating on bad info. I've found Pylint can be pretty slow when you have multiple files open, so I'm sure this leads to confusion for Claude.

Perhaps because I was using OpenAI API rather than Claude, I had to... because I ran out if my daily limit too quickly. And OpenAI definitely isn't respecting my 'ignore vscode error' prompt.

I just released v.1.7.5 that rolls back the automatic errors reporting, I agree with you @zytakeshi that this should probably be an opt-in behavior especially when you're in the middle of a messy project. I'm currently working on being able to add context to the textfield (files, folders, links) so adding '@problems' here would be a good solution to giving claude context on workspace errors so that he can fix them when you want him to. I thought it'd be cool for this to be automated but it's obvious that was a bit too ambitious.

Just to lend a voice to the other side. I love that feature it really improved my experience actually. I get that it might easily become an issue though

Does pylint take that long to update? Do you have an estimate of how long it usually takes? I can adjust this timeout value, but from personal testing found 5 seconds sufficient
That's just the thing, it's very unpredictable for me. It seems to scale with the number of files I have open or the size of the files. If I have one small file open, Pylint might update in a second. But if I have several large files open, it could be 30-60 seconds. I have a beefy 16 core 64 GB RAM dev machine too, so it's not like it's a resource issue.

I've found that Claude is quite good at resolving most linting errors when it's operating on good information, so I really like having this option. Either an on/off toggle or a customizable wait time would be awesome though.

How about adding it as a function claude as access to? check_vscode_diagnosics so i can say: "fix the type errors in foo.ts" and then it basically just decides to look at what they are instead of receiving it always

You can now send Claude problems with @problems! This way you have more control over when he sees errors, and he won't get stuck in loops trying to fix issues he can't solve on his own.

I just wanted to say that all the time and effort you put into this is truly heroic!  And much appreciated!

Why did you bring this back instead of making it an optional feature?
Use of unassigned variable '$_ADDONLANG'
Use of unassigned variable '$chatHistory'
Undefined type 'WHMCS\Database\Capsule'.
Undefined type 'WHMCS\Database\Capsule'.
Undefined type 'WHMCS\Database\Capsule'.
Undefined type 'WHMCS\Database\Capsule'.
Undefined type 'WHMCS\Database\Capsule'.

Messages like these should not be sent to AI, because these won't start making sense until I put them into my WHMCS server.
[1.9.7]
Only auto-include error diagnostics after file edits, removed warnings to keep Claude from getting distracted in projects with strict linting rules

What you have done here made Claude Dev impossible to use once again, and I had to migrate to cursor instead.
This feature could make sense in some environment like if the project was based on TypeScript or something that can be run locally, BUT IT MAKES NO SENSE IN MY ENVIRONMENT....
Anyways, just close this issue if you really need to implement this 'feature', and make this wonderful tool unusable for people like me.


[Remote rendering problem] DomainUnreachable issue on Quest build using Unity 2021+

Hi,
Having issues with creating a Remote rendering session using Unity 2021 or Unity 2022 and building for Quest 2/3.
I can get it to connect if I use 2020 but then I have issues with other features I need to use. It also works fine in the editor for 2021 and 2022.
I've tried to make it as simple as possible using your Quickstart project, but it's the same thing. I've debugged it some more and the error seems to be DomainUnreachable. There's definitely internet access and a 2020 build works fine with the same settings.
Thanks!

Hi, as a very first check, could you please see whether the ARR credentials are put into the correct text field? I ask, because we have recently released a change to the Showcase/Quickstart UI that swap the first two lines. So in case you are used to put the account Id into the first field, this will now break with that "DomainUnreachable" error. Of course saved scenes should load up correctly.

Yes, they are in the correct field and it works fine in Editor. I've just tried reversing them and same issue as well.

Alright, we'll try to reproduce the problem here. We'll keep you updated.
Florian

Hmm, I tried to reproduce the issue both with Unity 2021 and 2022 and it both worked (in Editor and on Quest 2).
My approach was to use off-the-shelf Quickstart sample, load it with newer Unity versions and deploy to Quest.
Could it be that some player network capabilities switched during your migration process?
Florian

How strange... I've just tried again with a fresh download of the repo. Opened Quickstart in Unity 2022. Switched to Android and added Account details. It runs fine in Editor but as soon as I run on Quest 2, I get:
"2023/11/14 18:22:53.284 14907 14924 Warn Unity Could not create session. Error: DomainUnreachable; Message: Failed to get access token:
2023/11/14 18:22:53.295 14907 14924 Error Unity Error creating session: Failed to get access token: "
Could it be anything to do with the region I'm using? I'm using uksouth.mixedreality.azure.com

OK, got it working! Seems like a bug in OpenXR: https://forum.unity.com/threads/unity-removes-android-permission-internet-in-the-build-apk-after-build-is-completed.1466654/

Alright, thanks a lot for letting us know!
This is very helpful information if others run into the same issue.
Cheers,
Florian


Turn off browser audio pre processing

Hello,
We have noticed that when recording in Chrome and Firefox audio is being be pre-processed by the browsers as detailed here:
https://stackoverflow.com/questions/31426551/get-consistent-audio-quality-with-getusermedia-using-different-browsers?rq=1
Where would we add options to turn this off? It looks like we are required to add:
navigator.getUserMedia(

        {

            "audio": {

                "mandatory": {

                    "googEchoCancellation": "false",

                    "googAutoGainControl": "false",

                    "googNoiseSuppression": "false",

                    "googHighpassFilter": "false"

                },

You use the constraints option of the microphone plugin: https://github.com/katspaugh/wavesurfer.js/blob/master/src/plugin/microphone.js#L3


Ukrainian language support

not sure how I can review this, would be nice to have someone else that speaks the language reviewing the unittests
@NeonMariia I assume this is a work in progress since there's a lot of commented unittests and the github actions are failing, let me know if i can help somehow

Marked as draft until this is completed. When completed, we can tag another Ukrainian speaker at Neon to review tests unless there's a community member who is able to review.

if it helps this PR can be broken into different ones, its ok to have several PRs each adding a different method
since #46 we now track methods per language, and most of them do not have all methods implemented yet

if it helps this PR can be broken into different ones, its ok to have several PRs each adding a different method
since #46 we now track methods per language, and most of them do not have all methods implemented yet

That's what we were discussing recently. I think it would be great!

Replaced by #50, #51 ?


stop Hires fix pass not working as intended

When set to 22 it stops my render at 22 regular steps rather than stopping at the 22nd hires fix step. I tried to set it to 123 (as I do 100 regular steps and 25 hires steps) as a workaround but the UI caps it to 80.
It begins counting from the very first step, instead of the hires steps.

When set to 22 it stops my render at 22 regular steps

This is what it does.

but the UI caps it to 80.

You can edit your ui-config.json and change cap, as you would do for any other GUI control.

It begins counting from the very first step, instead of the hires steps.

Intended behavior, because to stop the second pass you should use Skip but not Stop, and provide how many you want to skip from the end (rather than how many you want to keep at the beginning).


Way to disable sql output in shell_plus notebook?

There is quite a lot of SQL output, I'd like a way to turn this on or off, is it possible ?
I guess ideally this might be integrated into the UI.

Hope this is solved by now, otherwise please open a new issue. Thanks !

Will do.
No idea if there is a better way than the solution I found above.   I'm an IT contractor, so am probably on about my 6th project since I posted this ticket, so it's a very long time since I was using this.


📦 NEW: init hook to enqueue block scripts

⚠ IMPORTANT: This is a duplicate pull request for #47
Hey 🙌
After reading the discussing in issue #21, I have done the required changes to the code in cgb-scripts/template/src/init.php ✅
→ The scripts are being enqueued using init WordPress hook.

Cheers 🤘

@asharirfan What is the current status of this PR? Did you test it?

Yes, I have tested it. It is working on my end.

@ahmadawais Any updates on this one? Last time I tested this PR, it worked.

By default, block's Javascript that takes care of rendering the content is only loaded for editors.
IHMO this is a bit confusing for Gutenberg newcomers because it seems to ignore frontend rendering.

What if I'm using CGB to create a plugin with multiple block types? The build script only creates one block.build.js. The current init.php just enqueues those build files, but this method seems to imply that styles and JS only apply to specific blocks. Would we register each block type with the same style, editor-script, and editor-style?

@ahmadawais Tagging you here for your review on this PR.
I have synced this PR with the master branch to avoid merge conflicts.
I have also tested the script by creating a new block. Here are the screenshots:
Editor View

Frontend View

Looking forward to your review 🙌


fixed iOS splash screen

ios now displays splash screen between launch image and main scene, instead of a black screen.  Note that the duplicated "[self drawView];" line in gl_view.mm is deliberate.  This prevents first frame from being drawn black, and causing a brief black screen between launch image and splash screen.

After this I can't compile the server.
scons: Reading SConscript files ...
sh: 1: i586-mingw32msvc-gcc: not found
scons: done reading SConscript files.
scons: Building targets ...
g++ -o platform/server/os_server.server.opt.debug.64.o -c -O2 -ffast-math -DDEBUG_ENABLED -DSERVER_ENABLED -DUNIX_ENABLED -DMUSEPACK_ENABLED -DSQUISH_ENABLED -DVORBIS_ENABLED -DPNG_ENABLED -DDDS_ENABLED -DPVR_ENABLED -DJPG_ENABLED -DWEBP_ENABLED -DSPEEX_ENABLED -DGDSCRIPT_ENABLED -DMINIZIP_ENABLED -DXML_ENABLED -DETC1_ENABLED -Icore -Icore/math -Itools -Idrivers -I. -Iplatform/server -Iplatform/server/vorbis platform/server/os_server.cpp
In file included from core/rid.h:35:0,
                 from ./servers/visual_server.h:33,
                 from ./servers/visual/visual_server_raster.h:33,
                 from platform/server/os_server.cpp:29:
platform/server/os_server.cpp: In member function 'virtual void OS_Server::initialize(const OS::VideoMode&, int, int)':
platform/server/os_server.cpp:60:23: error: invalid new-expression of abstract class type 'RasterizerDummy'
  rasterizer = memnew( RasterizerDummy );
                       ^
core/os/memory.h:255:50: note: in definition of macro 'memnew'
 #define memnew(m_class) _post_initialize(new("") m_class)
                                                  ^
In file included from platform/server/os_server.cpp:30:0:
./servers/visual/rasterizer_dummy.h:49:7: note:   because the following virtual functions are pure within 'RasterizerDummy':
 class RasterizerDummy : public Rasterizer {
       ^
In file included from ./servers/visual/visual_server_raster.h:34:0,
                 from platform/server/os_server.cpp:29:
./servers/visual/rasterizer.h:1025:15: note: 	virtual void Rasterizer::restore_framebuffer()
  virtual void restore_framebuffer()=0;
               ^
ar rc main/libmain.server.opt.debug.64.a main/performance.server.opt.debug.64.o main/main.server.opt.debug.64.o
ranlib main/libmain.server.opt.debug.64.a
g++ -o modules/gridmap/grid_map_editor_plugin.server.opt.debug.64.o -c -O2 -ffast-math -DDEBUG_ENABLED -DSERVER_ENABLED -DUNIX_ENABLED -DMUSEPACK_ENABLED -DSQUISH_ENABLED -DVORBIS_ENABLED -DPNG_ENABLED -DDDS_ENABLED -DPVR_ENABLED -DJPG_ENABLED -DWEBP_ENABLED -DSPEEX_ENABLED -DGDSCRIPT_ENABLED -DMINIZIP_ENABLED -DXML_ENABLED -DETC1_ENABLED -Icore -Icore/math -Itools -Idrivers -I. -Iplatform/server -Imodules/gridmap/vorbis modules/gridmap/grid_map_editor_plugin.cpp
g++ -o modules/gdscript/register_types.server.opt.debug.64.o -c -O2 -ffast-math -DDEBUG_ENABLED -DSERVER_ENABLED -DUNIX_ENABLED -DMUSEPACK_ENABLED -DSQUISH_ENABLED -DVORBIS_ENABLED -DPNG_ENABLED -DDDS_ENABLED -DPVR_ENABLED -DJPG_ENABLED -DWEBP_ENABLED -DSPEEX_ENABLED -DGDSCRIPT_ENABLED -DMINIZIP_ENABLED -DXML_ENABLED -DETC1_ENABLED -Icore -Icore/math -Itools -Idrivers -I. -Iplatform/server -Imodules/gdscript/vorbis modules/gdscript/register_types.cpp
scons: *** [platform/server/os_server.server.opt.debug.64.o] Error 1
scons: building terminated because of errors.

So...apparently the github mobile site makes it very easy to accidentally tap the wrong place and delete the branch. So that was an accident. I'm not seeing a way to un delete it. I should be able to fix this compiler error tonight, as well as sort out my deletion mistake.


8000e config file typo fix

FourGigabitEthernet0/0/0/0 is not an interface in 8000e.
Changed to FourHundredGigE0/0/0/0.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 57.697%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2305

Relevant Lines:
3995

💛  - Coveralls

/gcbrun


Added new command spo group list

Added new command "spo group list"

Adds 'spo group list' command. Closes #1691

Coverage remained the same at 100.0% when pulling 12669d64b0c8aafdfa9133897f19b61f1d135d2f on dips365:master into f6993d9725aeea59d95fdde498b4c7cb04e22994 on pnp:master.

Thanks @dips365! We'll review it shortly 👍

@waldekmastykarz @PrasadKasireddy
Please review it and let me know if anything missed from my side.
I am ready with new command userprofile-get but waiting for close this PR.

Awesome! We'll have a look asap. For the future, it's better to create a separate branch for each PR and submit it from there. That way, you keep a clear master branch and can submit multiple PRs at the same time without being blocked by our review.

Hey Dipen @dips365 , Is there a branch in your fork where I can check the code? Seems that it shows unknown repository

@VelinGeorgiev
Unfortunately, Fork is removed from the my repository.
What is suggest that, Please cancel/close this PR. I will fork again in my repo and generate a new PR for the same command. I have back up so it would not take long time for new PR.
Thought?

Dipen @dips365 . Two options here:

I can copy the files from the PR in my branch and merge them, but it is likely you lose your name in the commit as contributor.
You create branch out of the master in your fork and move the files from the PR there then create a pull request. This way when I manually merge I marge the files in my branch, but you are still listed as the contributor.

Tip: I usually keep the master in my fork clean and create a branch for every pull request I am about to submit. For example: I will branch out of master into a new branch named group-list then create a pull request from it. This way I rarely have to delete a fork and fork it again.

@VelinGeorgiev
I will go with second option.
Working on creating new branch out of master and move files from PR. Will raise a Pull request from branch.
Thanks for the Tip. I will follow it to improve the work and save time.


Ionic CLI reformatting config.xml and package.json

Ionic version:  (check one with "x")
[X] 1.x
[ ] 2.x
[ ] 3.x
Note: just the CLI, don't think the project version matters here
I'm submitting a ...  (check one with "x")
[X] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
ionic build ios completely rewrites my config.xml and package.json files with trivial whitespace and other changes.  There could be breaking changes, but it's very hard to tell because everything is completely rearranged.
Expected behavior:
Leave my stuff alone!
Steps to reproduce:
run ionic build ios

Hey! Thanks for opening an issue with us. What version of the cli are you running? (you can get this info from running ionic-info in your project directory)

Oops, sorry!
Your system information:

Cordova CLI: 7.0.0
Ionic CLI Version: 2.2.3
Ionic App Lib Version: 2.2.1
ios-deploy version: 1.8.5
ios-sim version: 3.1.1
OS: macOS Sierra
Node Version: v6.10.3
Xcode version: Xcode 8.3.2 Build version 8E2002

All good, thanks for the info! Would you mind installing the latest beta version of the cli (instructions here) and seeing if you have the same issue? Also, just to confirm, you are using ionic 1 right?

I can confirm cli often rewrites config.xml and git has big diffs.
I'm using cli 3 rc2

Hmm interesting. Going to go ahead and move this issue to the CLI repo then. Thanks for the info.

This issue was moved to driftyco/ionic-cli#2230


[98BT] Pipeline reproduction (SPM - raw)

Softwares
SPM
Input data
raw data
Additional context
The pipeline needs to be refactored.
Before refactorisation, the code allows to get the following correlation results.

Hypothesis
20
40
60
80
108

1
0.619457607
0.748546878
0.759302767
0.813558828
0.845553836

2
0.670380239
0.779017092
0.829538307
0.870648291
0.898543524

3
0.619457607
0.748546878
0.759302767
0.813558828
0.845553836

4
0.670380239
0.779017092
0.829538307
0.870648291
0.898543524

5
0.521064207
0.760764715
0.850740157
0.872777873
0.895873802

6
0.364950987
0.518863577
0.636661521
0.678357091
0.791750891

7
0.521064207
0.760764715
0.850740157
0.872777873
0.895873802

8
0.364950987
0.518863577
0.636661521
0.678357091
0.791750891

9
-0.065392299
-0.057503176
-0.012228297
-0.018225192
0.008085577

There is a bug with hypothesis 9, as well as insufficient correlation values for other results.
List of tasks
Please tick the boxes below once the corresponding task is finished. :+1:

[x] :ok_hand: A maintainer of the project approved the issue, by assigning a :checkered_flag:status: ready for dev label to it.
[x] :deciduous_tree: Create a branch on your fork to start the reproduction.
[x] :sunrise: Create a file team_{team_id}.py inside the narps_open/pipelines/ directory. You can use a file inside narps_open/pipelines/templates as a template if needed.
[x] :inbox_tray: Create a pull request as soon as you completed the previous task.
[x] :brain: Write the code for the pipeline, using Nipype and the file architecture described in docs/pipelines.md.
[x] :blue_book: Make sure your code is documented enough.
[x] :snake: Make sure your code is explicit and conforms with PEP8.
[x] :microscope: Create tests for your pipeline. You can use files in tests/pipelines/test_team_* as examples.
[ ] :microscope: Make sure your code passes all the tests you created (see docs/testing.md).

$ narps_description -t 98BT --md
NARPS team description : 98BT
General

teamID : 98BT
NV_collection_link : https://neurovault.org/collections/4988/
results_comments : NA
preregistered : No
link_preregistration_form : NA
regions_definition : We created individual masks for each region (prior to completing group results) and examined supra-threshold activity in each mask. The amygdala and striatum masks were created using the aal atlas template packaked with MRIcron, while the VMPFC was created using Brodmann's areas 10, 11, and 25 from the Brodmann's atlas packageed with MRIcron.
softwares : SPM12
general_comments : NA

Exclusions

n_participants : 100
exclusions_details : Subjects 071, 072, and 089 were excluded due to problems in preprocessing. For example, some subjects has different data types within the nifti files, which resulted in error during preprocessing. Subjects with mean framewise displacement above or equal to 0.2 mm were also excluded, specifically: subs 016, 018, 030, 088, and 100.

Preprocessing

used_fmriprep_data : No
preprocessing_order : Slice timing, motion correction with fieldmap unwarping, normalize via DARTEL (smoothing incorporating into normalization)
brain_extraction : NA
segmentation : SPM Segment function via custom scripts (defaults left in place)
slice_time_correction : SPM slice time correction with default parameters (shift via sinc interpolation and Fourier transform), with ref =2. Slice time correction performed as first step of preprocessing, prior to motion correction.
motion_correction : SPM realign and unwarp, incorporating field maps into motion correction for unwarping. Most parameters as SPM default, but 4th degree bslines interpolation was used for estimation. Images were rereferenced to the first scan in each run.
motion :
gradient_distortion_correction : In motion correction above
intra_subject_coreg : Each EPI scan was coregistered to the structural scan via SPM's coreg function, using normalized mutual information.
distortion_correction : NA
inter_subject_reg : SPM's DARTEL function was used to create a study-specific template in 3D volume space which was transformed into MNI space. This study template was used for normalizating each subject's scans to the MNI space via non-linear transformation.
SPM's description:
"Smoothed" (blurred) spatially normalised images are generated in such a way that the original signal is preserved. Normalised images are generated by a "pushing" rather than a "pulling" (the usual) procedure.
Note that trilinear interpolation is used, and no masking is done.
intensity_correction : NA
intensity_normalization : Standard SPM approach (mean = 100)
noise_removal : Mean signal in a white matter mask was calculated, and incorporated into the GLM as a regressor. No regression/filtering was applied to the raw data.
volume_censoring : NA
spatial_smoothing : 8mm fwhm smoothing is performed as part of the DARTEL normalization procedure.
preprocessing_comments : NA

Analysis

data_submitted_to_model : Single subject contrast betas from parameteric modulators for gains and losses.
spatial_region_modeled : Whole brain analysis
independent_vars_first_level : An event related design was used. Events were entered as a single events with a 4 second duration. Paramteric modualtors were added for each condition for gain, loss, and for accept or reject (in that order; note that SPM performs serial orthogonalization of  modulators). Canonical HRFs were used along with the derivative and dispersion functions. SPM defaults were used for other analysis parameters (Volterra=1, 1st order autocorrelation, high pass filter=128). The six motion parameters, the absolute value of the 1st derivative of the six parameters, and the mean WM signal were entered as covariates into the model. Mean WM signal was calculated for each individual by taking their SPM segmentation WM mask, thresholded at 0.6, as a mask to the motion corrected BOLD data, taking the mean timeseries of all voxels determined to be within the white matter. All four scans were entered into a single fixed effects model for each individual, as separate sessions. For each individual, a contrast map was calculated for the parametric effects of gains and the parametric effects of losses, with both positive and negative contrasts run, collapsing across runs.
RT_modeling : none
movement_modeling : 1
independent_vars_higher_level : Contrast beta maps for the parametric effects of losses or gains were entered into the second level analysis.
model_type : Mass univariate modelling was used. A group analysis (radom effects) model was run for the equaldifference group, equalrange group, and the difference between groups (as separate GLMs)
model_settings : SPM defaults.
inference_contrast_effect : The main effects of the parametric modulators for gains and losses were tested.
search_region : The whole brain was used for calculating cluster statistics. The data was thresholded such that only clusters above p<0.05 FDR corrected were kept, and data was then masked to answer the specific hypotheses.
statistic_type : Cluster extent, using SPM's FDR corrected cluster extent statistic, and a threshold of p<0.001 uncorrected.
pval_computation : NA
multiple_testing_correction : Random field theory, cluster FDR (SPM)
comments_analysis : NA

Categorized for analysis

region_definition_vmpfc : atlas Brodmann
region_definition_striatum : atlas AAL
region_definition_amygdala : atlas AAL
analysis_SW : SPM
analysis_SW_with_version : SPM12
smoothing_coef : 8
testing : parametric
testing_thresh : p<0.001
correction_method : FDR cluster
correction_thresh_ : p<0.05

Derived

n_participants : 100
excluded_participants : 071, 072, 089, 016, 018, 030, 088, 100
func_fwhm : 8
con_fwhm :

Comments

excluded_from_narps_analysis : No
exclusion_comment : Rejected due to very bad normalization.
reproducibility : 2
reproducibility_comment :

Code is running, but there is probaby a bug with the equalIndifference group after refactorisation :
Correlation values for 108 subjects:
[0.17, 0.88, 0.17, 0.88, 0.89, 0.56, 0.89, 0.56, -0.00]

Bug (partly ?) resolved after commit b5188e9c15bc30e304336c23ca17c67100c95e0b
Correlation values for 108 subjects:
[0.81, 0.88, 0.81, 0.88, 0.89, 0.73, 0.89, 0.73, -0.00]
Correlation values for 106 subjects (003 and 107 excluded by the team):
[0.80, 0.88, 0.80, 0.88, 0.87, 0.73, 0.87, 0.77, -0.00]

As part of NOP hackathon, Dec 12-13, 2024.
I reviewed the code to try and explain the observed correlations. Here are a few questions / comments:

I could not locate the smoothing step (8mm)?
"Smoothed" (blurred) spatially normalised images are generated in such a way that the original signal is preserved. Normalised images are generated by a "pushing" rather than a "pulling" (the usual) procedure. Note that trilinear interpolation is used, and no masking is done.

Point 2: Smoothing is here but as part of the dartel procedure.

Looking at the stat maps of hypothesis 9 it looks like we are doing extra masking compared to the ground truth provided by the team. Also the 'pushing' rather than 'pulling' for the smoothing may be default in dartel (see https://www.fil.ion.ucl.ac.uk/spm/docs/manual/dartelguide/dartelguide/)?

Current DARTEL workflow implementation is based on create_DARTEL_template


Fix guide link to grape integration

@apotonick thanks for merge!

Ha, no, thanks for spotting and fixing that! :heart_eyes:


chore(deps): bump axios from 1.6.7 to 1.7.5 in /app

Bumps axios from 1.6.7 to 1.7.5.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: axios dependency-type: indirect ...

Will address: https://github.com/bcgov/cas-cif/security/dependabot/75


2.0 nclsup 138

All Submissions:

[x] Have you added a note in the CHANGELOG wiki for your change?
[ ] Have you added unit tests for your change?

wtf


Add the intro.ipynb notebook

The intro.ipynb notebook gives a short introduction to this repository. It also provides other relevant information, and explains how to use IPython notebooks.
Please give me your comments or suggestions on the content and feel free to add anything that you think might prove to be useful or essential. If you cannot view the notebook because this is pull request, here's an online link on Nbviewer.

Could you also add explanation about what abstract classes are. I'm writing the notebook in which I've mentioned intro.ipynb for instruction on how to use the book

@Chipe1 I didn't get you. Abstract classes don't exist in Python, afaik.
And feel free to edit the notebook if you think anything is worth adding. :) That way we can all discuss on it.


llms: add googleai llm option WithHTTPClient

Changes

Adds an option WithHTTPClient to Google AI LLM implementation, which passes a consumer provided http.Client to the underlying vendor maintained client. The new option is used also by the vertex llm implementation.
The new option can be used for troubleshooting (example using httputil.DebugHTTPClient) or providing flexibility to consume LLM services behind proxies, set additional headers etc.
Similar options are already available on the OpenAI LLM options as well as the existing PaLM legacy LLM

Issue: fixes https://github.com/tmc/langchaingo/issues/838
PR Checklist

[x] Read the Contributing documentation.
[x] Read the Code of conduct documentation.
[x] Name your Pull Request title clearly, concisely, and prefixed with the name of the primarily affected package you changed according to Good commit messages (such as memory: add interfaces for X, Y or util: add whizzbang helpers).
[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. Fixes #123).
[x] Describes the source of new concepts.
[x] References existing implementations as appropriate.
[x] Contains test coverage for new functions.
[x] Passes all golangci-lint checks.

#841 provides similar functionality - waiting to check whether author would like to take over unit tests.

Closing in favour of #841 .


Update Emulator for Ngrok v3 Support

Fixes #2389
Version 3.x of Ngrok makes changes to the config file format and the supported command line arguments. The path field has been removed from the arguments, while the region field has been moved to the config file (where it is now required rather than optional). This causes the existing version of Emulator to fail when attempting to spawn Ngrok and connect to a remote bot.
This PR updates ngrok.ts and ngrokService.ts to remove the path and region fields so they are not passed to the Ngrok instance, thereby allowing Ngrok v3 to be used with Emulator.
Specific Changes:

Remove path and region from from NgrokOptions.
Update ngrokService.ts to pass the path to the ngrok.ts constructor when creating the Ngrok instance instead of passing it as an argument to the instance.
Update ngrok.ts to use the path passed into the constructor instead of the path from NgrokOptions.

@anishprasad01 thank you for the contribution! would this break using Emulator with ngrok v2?

@cwhitten,
I attempted to run with Ngrok v2.3.0 and was successfully able to connect to a bot hosted in Azure. Since the region field was optional in Ngrok v2, its presence should not break anything. I will perform further testing before this PR gets merged.

Coverage decreased (-0.7%) to 66.941% when pulling 83c26a9573bee02fe60f8ccac11d93155c3005bf on anishprasad01/ngrok-v3-fix into 99a7ccdb75b93c5be3a05ef962d4fdc8d106baed on main.

Testing with both Ngrok v2 and v3 reveals that v2 remains supported even with the modifications made to support v3. Communication with an Azure bot is successful and no errors appear when running or exiting the application. A search of running processes after exiting the application reveals that the Ngrok process is terminated successfully.
Testing with v2:

Testing with v3:

hi! PM for ngrok here. I'd love to see this PR merged so that we could move your users to the latest version of the ngrok agent. If I can help in any way, please let me know.

/AzurePipelines run

Build is failing due to the test failures:
FAIL packages/app/main/src/ngrok.spec.ts
  ● the ngrok  › ngrok connect/disconnect operations › should throw if it failed to find an ngrok executable at the specified path.

    expect(received).toBe(expected) // Object.is equality

    Expected: "Error: Could not find ngrok executable at path: Applications\\ngrok. Make sure that the correct path to ngrok is configured in the Emulator app settings. Ngrok is required to receive a token from the Bot Framework token service."
    Received: "Error: Could not find ngrok executable at path: D:\\a\\1\\s\\packages\\app\\main\\src\\bin\\ngrok.exe. Make sure that the correct path to ngrok is configured in the Emulator app settings. Ngrok is required to receive a token from the Bot Framework token service."

      225 |         thrown = e;
      226 |       }
    > 227 |       expect(thrown.toString()).toBe(
          |                                 ^
      228 |         `Error: Could not find ngrok executable at path: ${path}. Make sure that the correct path to ngrok is configured in the Emulator app settings. Ngrok is required to receive a token from the Bot Framework token service.`
      229 |       );
      230 |     });

Build is failing due to the test failures:
FAIL packages/app/main/src/ngrok.spec.ts
  ● the ngrok  › ngrok connect/disconnect operations › should throw if it failed to find an ngrok executable at the specified path.

    expect(received).toBe(expected) // Object.is equality

    Expected: "Error: Could not find ngrok executable at path: Applications\\ngrok. Make sure that the correct path to ngrok is configured in the Emulator app settings. Ngrok is required to receive a token from the Bot Framework token service."
    Received: "Error: Could not find ngrok executable at path: D:\\a\\1\\s\\packages\\app\\main\\src\\bin\\ngrok.exe. Make sure that the correct path to ngrok is configured in the Emulator app settings. Ngrok is required to receive a token from the Bot Framework token service."

      225 |         thrown = e;
      226 |       }
    > 227 |       expect(thrown.toString()).toBe(
          |                                 ^
      228 |         `Error: Could not find ngrok executable at path: ${path}. Make sure that the correct path to ngrok is configured in the Emulator app settings. Ngrok is required to receive a token from the Bot Framework token service.`
      229 |       );
      230 |     });

Any update on this? Unfortunately it seems ngrok v2 is not usable anymore and Emulator is not working with any version of Ngrok v3. So, at the moment, it is not possible to contact a remote bot with Emulator.


Add setting to control whether to show the OmniSharp log on error

Resolves https://github.com/OmniSharp/omnisharp-vscode/issues/4102 & https://github.com/OmniSharp/omnisharp-vscode/issues/4330
By default, the C# extension will continue to show the OmniSharp log when errors are encountered. This PR provides a setting so users can disable this behavior.

@vzarytovskii @nohwnd For review

@vzarytovskii @nohwnd For review


Add workflow for auto updating the website on release

Fixes: #1337
The bot will have to be granted access to  OWASP/www-project-juice-shop/ for this to work
P.S: Just realized the issue is numbered 1337

P.S: Just realized the issue is numbered 1337

Noice 😂

Btw. if I remember correctly not the bot account needs the rights, but the person doing the push. Which is either the one actually pushing directly to the master branch or the one who clicked the merge button on a PR.

Pushing to master is okay, then it is consistent with the demo Heroku instance. That deploys the master branch, not a tag.

@bkimminich the checkout repository needs to be changed from OWASP/www-project-juice-shop/ to OWASP/www-project-juice-shop


setting changed popup

I added some code for the popup.
I implemented the 2 different solutions we talked about, for different screen sizes.
About the responsiveness,
I had some difficulties to understand the expected behavior for smaller size devices, when width or height is less than 550-600px,
It is not clear to me what is the expected behaviour.
Playing with width/height sizes,
I realized that also the tooltips, recently added, were not visible on smaller height device, they lay out of the viewport...
I put some small changes in stylesheet.css to resize the main window and give room for the tootltip, but I think more work is needed in general about responsiveness.

ok Chase,
I think I made all the requested changes about sizes. I restored the original values.
(I also inserted the popup notification on the "Change weather API key" button, it was missing.)


content grammar system stuff

About the PR
when engine updated either instamerge or steal this branch or something idk

fairly sure build fail real

cause engine isnt merged or updated


Unable to create a developer account fro Office 365. And I keep on getting the same issue when I click on Join Now button after signing in with my profile.

> Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.

(DELETE THIS PARAGRAPH AFTER READING)

Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea
[ ] Example checked item (delete this line)

For the above list, an empty checkbox is [ ] as in [SPACE]. A checked checkbox is [x] with no space between the brackets. Use the PREVIEW tab at the top right to preview the rendering before submitting your issue.
If you are planning to share a new feature request (enhancement / suggestion), please use SP Dev UserVoice at http://aka.ms/sp-dev-uservoice. (DELETE THIS PARAGRAPH AFTER READING)
(DELETE THIS PARAGRAPH AFTER READING)

Expected or Desired Behavior

If you are reporting a bug, please describe the expected behavior. If you are suggesting an enhancement please describe thoroughly the enhancement, how it can be achieved, and expected benefit.
(DELETE THIS PARAGRAPH AFTER READING)

Observed Behavior

If you are reporting a bug, please describe the behavior you expected to occur when performing the action. If you are making a suggestion, you can delete this section.
(DELETE THIS PARAGRAPH AFTER READING)

Steps to Reproduce

If you are reporting a bug please describe the steps to reproduce the bug in sufficient detail to allow testing. Only way to fix things properly, is to have sufficient details to reproduce it. If you are making a suggestion, you can delete this section.
(DELETE THIS PARAGRAPH AFTER READING)

Submission Guidelines

All suggestions or bugs are welcome, please let us know what's on your mind.
If you are reporting an issue around any of the documents or articles, please ensure that you have clear > reference on the specific file or URL, which should be fixed.
If you have technical questions about the framework, we’ll be monitoring #spfx, #spfx-webparts, and > #spfx-tooling on (SharePoint StackExchange)[http://sharepoint.stackexchange.com/]. You can also > alternatively submit your question to (SharePoint Developer group)> [https://network.office.com/t5/SharePoint-Developer/bd-p/SharePointDev] at Office Network.
Remember to include sufficient details and context.
If you have multiple suggestions or bugs please submit them in separate bugs so we can track resolution.

(DELETE THIS PARAGRAPH AFTER READING)

Thanks for your contribution! Sharing is caring.

How long have you waited after updating your Microsoft Account?

I almost waited for 6 hours and tried again.

Thank you for your submission. This GitHub issue list is targeted only for SharePoint development issues. If this is a capability question/discussion, please use the SharePoint TechCommunity.
If it is an issue is related to out-of-the-box capabilities of SharePoint or not related to SharePoint, we cannot process is through this channel. Please submit your finding using the Tenant administrator support channels in your tenant or using Premier support, if that’s available for you. Sorry for the inconvenience.

While you're trying to create a developer account, this is not a SharePoint development related issue... best to submit a support issue with MSFT...


Offline trackSelectionCallback should be async

Have you read the FAQ and checked for duplicate open issues?
Yes
Is your feature request related to a problem? Please describe.

The trackSelectionCallback should be able to show a prompt to the user to make some choice about what to store (HD, SD, languages, etc).  Because the callback is synchronous, such a prompt has to be made before store() is called and without track info from the player.
Describe the solution you'd like

trackSelectionCallback should be changed to return a Promise.  The caller (internal) should use await.  This will be backward compatible with synchronous versions, since calling await on a synchronous function doesn't change any behavior.
Describe alternatives you've considered

None come to mind.
Additional context

I thought this was already async, and I seem to recall describing to people how they can just use an async function for this callback, similar to how we support async request & response filters.

PR #2387 introduced a bug.  It awaited the track selection callback, but that was done in a loop, the results of which were not awaited.  This would cause storage to continue before the complete list of tracks was available.


Remove the right margin from extra nav on mobile

This was pushing the width of the page wider than necessary on mobile.  Now there's no horizontal scroll down to iPhone 5 sizes.

Looks good to me in the emulator


Explicitly close transformer stream stage after eof

:notebook_with_decorative_cover: Description
Apparently a pending stream handshake can delay the destruction
of the hosting scheduled actor. For actors that failed to spawn
successfully, the handshake will never become not pending so we
need to close the stage manually.

:memo: Checklist

[x] All user-facing changes have changelog entries.
[x] The changes are reflected on docs.tenzir.com/vast, if necessary.
[x] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions
Review commit-by-commit.
To test, make e.g. the index/ subdirectory of an existing vast.db non-readable. Prior to this PR, vast will hang after printing an error, after this PR it should terminate normally.

As much as I'd like to see this bug fixed, I'll close this PR now until it shows up again in a higher-priority context since investigating the test failures is too involved currently.


Update index.md

Removed "South Sudan" country , Sudan already exists

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

BingMaps/coverage/index.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix json data issues

Resmed updated to a new appsync address.
Added the ability to reload the integration as well.
Left in debug logging to help with future troubleshooting.
Linting cleanups.
May add in more robust error checking in the future (as a different PR) to better show when this fails.
Note this will not help with the EU 2FA issues.
Fixes #48
Fixes #49
Fixes #50

Thank @Snuffy2! My CDMA device no longer connects so I'm not able to test but happy to merge and publish. The tests are failing due to bitrot, something else to look at

Thanks all for fixing. Updated on reboot entities are back! But I see this warning: on 0.14.0
This error originated from a custom integration.

Logger: py.warnings
Source: custom_components/resmed_myair/client/__init__.py:5
integration: ResMed myAir CPAP Sensors (documentation, issues)
First occurred: 10:18:27 PM (1 occurrences)
Last logged: 10:18:27 PM

/config/custom_components/resmed_myair/client/legacy_client.py:137: SyntaxWarning: invalid escape sequence '\[' matches = re.search(".+(\[.+?\]).+", scores_script).groups()[0]


Godot overrides changes when pulling from Git remote

Godot version:
3.1-beta6
OS/device including version:
Windows 10
Issue description:
When having the Godot editor open in a project with Git version control, and pulling changes from a remote, Godot will overwrite many changes as soon as the editor window is focused again (including the project.godot file and open scenes) with data from the current session, rather than use the newly pulled data.
This means that, in order to update our project with the team's changes from a remote Git repository, we have to close the editor, pull the changes, and then load the project again.

Duplicate of #20250.


Images are in torch.cuda.DoubleTensor while the weights are in torch.cuda.FloatTensor.

I followed all the steps as mentioned in the document but While running the command for Phase: module_training.

python scripts/train.py
--config-yml configs/module_training.yml
--phase module_training
--config-override CHECKPOINTS.QUESTION_CODING checkpoints/question_coding_ours/question_coding_best.pth
--gpu-ids 0 1 2 3
--serialization-dir checkpoints/module_training

I'm getting this error: Input type (torch.cuda.DoubleTensor) and weight type (torch.cuda.FloatTensor) should be the same
on line: output_dict = self._nmn(batch["image"], pg_output_dict["predictions"], batch["answer"]) in module_training_trainer.py
When I change the type of batch["image"] to batch["image"].float() i got error: TypeError: zip argument #1 must support iteration
I tried different ways to convert batch["image"] of type torch.cuda.FloatTensor but every time i got it is not iterable. I also tried to change the get_item from dataset to return an image of type float but still, it is not working.
I am pasting the completing error for clear reference.
Batch['image'] type : torch.cuda.DoubleTensor

> Traceback (most recent call last):
>   File "scripts/train.py", line 138, in <module>
>     trainer.step(iteration)
>   File "/data/vivek/neural-symbolic/probnmn-clevr/probnmn/trainers/_trainer.py", line 147, in step
>     output_dict = self._do_iteration(batch)
>   File "/data/vivek/neural-symbolic/probnmn-clevr/probnmn/trainers/module_training_trainer.py", line 96, in _do_iteration
>     output_dict = self._nmn(batch["image"], pg_output_dict["predictions"], batch["answer"])
>   File "/data/vivek/anaconda3/envs/probnmn/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in __call__
>     result = self.forward(*input, **kwargs)
>   File "/data/vivek/anaconda3/envs/probnmn/lib/python3.6/site-packages/torch/nn/parallel/data_parallel.py", line 143, in forward
>     outputs = self.parallel_apply(replicas, inputs, kwargs)
>   File "/data/vivek/anaconda3/envs/probnmn/lib/python3.6/site-packages/torch/nn/parallel/data_parallel.py", line 153, in parallel_apply
>     return parallel_apply(replicas, inputs, kwargs, self.device_ids[:len(replicas)])
>   File "/data/vivek/anaconda3/envs/probnmn/lib/python3.6/site-packages/torch/nn/parallel/parallel_apply.py", line 83, in parallel_apply
>     raise output
>   File "/data/vivek/anaconda3/envs/probnmn/lib/python3.6/site-packages/torch/nn/parallel/parallel_apply.py", line 59, in _worker
>     output = module(*input, **kwargs)
>   File "/data/vivek/anaconda3/envs/probnmn/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in __call__
>     result = self.forward(*input, **kwargs)
>   File "/data/vivek/neural-symbolic/probnmn-clevr/probnmn/models/nmn.py", line 183, in forward
>     feat_input_volume = self.stem(features)
>   File "/data/vivek/anaconda3/envs/probnmn/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in __call__
>     result = self.forward(*input, **kwargs)
>   File "/data/vivek/anaconda3/envs/probnmn/lib/python3.6/site-packages/torch/nn/modules/container.py", line 92, in forward
>     input = module(input)
>   File "/data/vivek/anaconda3/envs/probnmn/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in __call__
>     result = self.forward(*input, **kwargs)
>   File "/data/vivek/anaconda3/envs/probnmn/lib/python3.6/site-packages/torch/nn/modules/conv.py", line 320, in forward
>     self.padding, self.dilation, self.groups)
> RuntimeError: Input type (torch.cuda.DoubleTensor) and weight type (torch.cuda.FloatTensor) should be the same
>
>

Hi
I still got the same error. When I changed the ClevrImagesDataset(Dataset) class in extract_features.py.
Traceback (most recent call last):   File "scripts/preprocess/extract_features.py", line 142, in <module>     main(args)   File "scripts/preprocess/extract_features.py", line 129, in main     output_features = feature_extractor(batch)   File "/home/badri/anaconda3/envs/probnmn/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in __call__     result = self.forward(*input, **kwargs)   File "/home/badri/anaconda3/envs/probnmn/lib/python3.6/site-packages/torch/nn/modules/container.py", line 92, in forward     input = module(input)   File "/home/badri/anaconda3/envs/probnmn/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in __call__     result = self.forward(*input, **kwargs)   File "/home/badri/anaconda3/envs/probnmn/lib/python3.6/site-packages/torch/nn/modules/conv.py", line 320, in forward     self.padding, self.dilation, self.groups) RuntimeError: Input type (torch.cuda.DoubleTensor) and weight type (torch.cuda.FloatTensor) should be the same

Please pull from latest master, this issue should be fixed. Feel free to re-open!


Allow Openstack provider Volumes and Snapshots to be eligible for provisioning.

This patch allows any openstack VolumeTemplates and VolumeSnapshotTemplates to be visible in the provisioning source selection if they are present. These classes are basically proxies for Cloud Volumes and Cloud Volume Snapshots that permit them to be used as provisioning sources without refactoring the provisioning system to support types other than MiqTemplate.
See https://github.com/ManageIQ/manageiq-providers-openstack/pull/104 for more information
https://github.com/ManageIQ/manageiq-ui-classic/pull/2253
@gmcculloug

This has been open for a long time, going to kick the tests before merging


[Bug] Passing --auto-complete does not auto-complete if branch policy on merge type is applied

Describe the bug
If you pass auto-complete in az repos pr create command autocomplete appears to be turned on, but the PR does not actually autocomplete when all criteria are met. We have a work item requirement, 2 approvers requirement, and passing build requirement.
To Reproduce
Azure Cli Version: 2.0.62
Azure-Devops extension version: 0.4.0
Steps to reproduce the behavior:

login using az login
create pr using az repos pr create --auto-complete from a branch on git repository
complete all requirements for pr to close
See that PR does not actually close in browser

Expected behavior
PR should merge and complete as soon as the last requirement is met

@sddev-dotnet Can you share some more details to help us look into it..
When you said "autocomplete appears to be turned on" do you see the "Cancel auto-complete" on the top on the portal similar to the screenshot?
In that case  you should see which policy is blocking the PR from auto completing. Refer the sample screenshot where the reviewers policy is blocking the PR.
If the Pull request portal does not look similar to sample image do share what do you see on the portal and were you eventually able to complete the PR manually if it did not complete automatically.
Do you see this issue only when you create a PR from the CLI?

@atbagga Yes I see the Cancel Auto Complete button in the top right, and all of my policies have a green checkmark next to them. This only happens when I turn on autocomplete via the cli (and it also happened with the VSTS cli as well when I was using that). Basically, if I want autocomplete, I have to create the PR without it using the CLI, then go into the portal and turn it on. Otherwise, the PR never merges even after all policies are met.

I tried and it works for me as expected.
Can you share the debug output for the command.
Running it with --debug parameter like az repos pr create --auto-complete --debug
Also share what you see in the UI screen.
Please remove any confidential information from the debug output.

@sddev-dotnet  I tried and it works for me as expected.
Can you share the debug output for the command.
Running it with --debug parameter like az repos pr create --auto-complete --debug
Also share what you see in the UI screen.
Please remove any confidential information from the debug output.

sure, it will take a little bit because we require 2 approvers, so I have to find someone to approve the pr, but I will get this added today. As a side note, we have the following policies turned on:
2 approvers
1 required approver from a group
All comments resolved (required)
Build passing
Linked work item
I will get you an example later today though

Here is an example of a PR that I created with auto-complete enabled but not autocompleting when all of the policies are met:

Thanks! I will try to repro it with similar policies.

Thanks @atbagga I think it may have something to do with the merge strategy (because whenever you click the auto-complete button in the UI it asks you for a merge strategy). In my repo, I have it set to squash by default (and delete branch after merge).

We experience the same issue, but only on some pull requests and not all. (Also with a squash and delete policy). Canceling auto-complete and then using the "complete" button works.

Repro the issue. The merge strategy feature recently introduced in the Pull requests is causing this.
When the Auto-complete options specified do not full fill the merge strategy allowed in the branch policies the PR does not auto complete.
@sddev-dotnet In your case since you do a squash merge you can be unblocked if you use the --squash option by default when setting auto-complete. Since this option was existing even before other merge strategy options were introduced so it will continue to work for you unless the organization chooses to switch to a policy which does not allow squash merge.

If branch policy on merge strategy is applied and it does not allow basic or squash merge, --auto-complete set via CLI will not work.
If branch policy allows the basic merge or squash merge and user sets the --squash option correctly as per policy only then will the PR auto-complete work correctly.

Fix for this is blocked on API dependency.

Fix for this is blocked on API dependency.

Could this be implemented, maybe drawing parallels to #718?

Fix for this is blocked on API dependency.

Could this be implemented now by maybe drawing parallels to #718?

Short answer is no.
Details:
The issue 718 was a change in API object which the python client sends as a dictionary of key value pairs which is extendable without upgrading the python client.
This issue is because Pull request client only understands fixed values in this enum and thus requires the client upgrade.
Since the command is not in preview and the new API/Client is preview and subject to change we cannot take dependency on that client yet for getting this functionality.

Any news on this? Have the necessary APIs been implemented?

Looks like the python client is not available yet for 6.0 version which should have the changes.
https://github.com/microsoft/azure-devops-python-api/tree/dev/azure-devops/azure/devops

Looks like the python client is not available yet for 6.0 version which has the changes.

It arrived: :)

https://github.com/microsoft/azure-devops-python-api/tree/dev/azure-devops/azure/devops/v6_0
https://github.com/microsoft/azure-devops-python-api/releases/tag/6.0.0b1

hi @fdcds ,
Sorry, but the REST API v6.0 is still in preview. We can do a client update only when the APIs are out of preview.

Any news on this?
The v6.0 REST API is no longer in preview...

Any new update?


todo-comment: update config

there are some minor issue w/ current todo-comment.nvim's config:
In colors, we define it as following
		colors = {
			error = { "DiagnosticError", "ErrorMsg", "#DC2626" },
			warning = { "DiagnosticWarn", "WarningMsg", "#ff8800" },
			info = { "DiagnosticInfo", "#2563EB" },
			hint = { "DiagnosticHint", "#F5C2E7" },
			default = { "Conditional", "#7C3AED" },
			test = { "Identifier", "#4FC1FF" },
		},

However, it's over written to these colors:

In :Inspect

Should we just remove the colors section or enforce colors as such:
	local error_red = "#F44747"
	local warning_orange = "#ff8800"
	local info_yellow = "#FFCC66"
	local hint_blue = "#4FC1FF"
	local perf_purple = "#7C3AED"
	local note_green = "#10B981"

	require("modules.utils").load_plugin("todo-comments", {
		signs = true, -- show icons in the signs column
		sign_priority = 8, -- sign priority
		-- keywords recognized as todo comments
		keywords = {
			FIX = {
				icon = icons.ui.Bug, -- icon used for the sign, and in search results
				color = error_red, -- can be a hex color, or a named color (see below)
				alt = { "FIXME", "BUG", "FIXIT", "ISSUE" }, -- a set of other keywords that all map to this FIX keywords
				-- signs = false, -- configure signs for some keywords individually
			},
			TODO = { icon = icons.ui.Check, color = hint_blue, alt = { "TIP" } },
			HACK = { icon = icons.ui.Fire, color = warning_orange },
			WARN = { icon = icons.diagnostics.Warning, color = warning_orange, alt = { "WARNING", "XXX" } },
			PERF = { icon = icons.ui.Perf, color = perf_purple, alt = { "OPTIM", "PERFORMANCE", "OPTIMIZE" } },
			NOTE = { icon = icons.ui.Note, color = note_green, alt = { "INFO" } },
			TEST = { icon = icons.ui.Lock, color = info_yellow, alt = { "TESTING", "PASSED", "FAILED" } },
		},

aha, i didn't notice that, then i think it's fine to keep them as backup colors.


Remove the Irish Counties from the Census County search options

We have no transciptions would it not be better therefore not to offer to search them

Duplicate = closing

Duplicate = closing


Improve session window documentation

Purpose

Improve usability.

Codecov Report

Merging #1580 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1580   +/-   ##
=========================================
  Coverage     67.68%   67.68%
  Complexity       45       45
=========================================
  Files           650      650
  Lines         27471    27471
  Branches       4330     4330
=========================================
  Hits          18595    18595
  Misses         7063     7063
  Partials       1813     1813

Impacted Files
Coverage Δ
Complexity Δ

...rocessor/stream/window/SessionWindowProcessor.java
66.41% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ut/stream/state/AbsentStreamPreStateProcessor.java
82.11% <0%> (-1.33%)
0% <0%> (ø)

...java/io/siddhi/core/stream/input/InputHandler.java
75% <0%> (+5.55%)
0% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


I'm sorry, my geometric education was about 25 years ago and I'm stumped by this for some reason :)  When I try to get this to work, the self-check fails, and kpkProbe fails at 8/26.

There are two geometry files that serve as an example.
geometry-a1a2.h
geometry-h8g8.h
You would have to look at them and then create one "geometry-a1b1.h". The definitions in kpk.c need no change. Only change the reference to the geometry.h file...

If that doesn't work, feel free to paste your new file here and I take a quick look

Thank you!  What's confusing me is that with my a1-b1 orientation, the ranks are now like files in your a1-a2 orientation, so my thought was this:
enum file { fileA, fileB, fileC, fileD, fileE, fileF, fileG, fileH };
enum rank { rank1, rank2, rank3, rank4, rank5, rank6, rank7, rank8 };
#define file(square)       ((square) & 7)
#define rank(square)       ((square) >> 3)
#define square(file, rank) ((file) + (rank << 3))
enum square {
a1, b1, c1, d1, e1, f1, g1, h1,
a2, b2, c2, d2, e2, f2, g2, h2,
a3, b3, c3, d3, e3, f3, g3, h3,
a4, b4, c4, d4, e4, f4, g4, h4,
a5, b5, c5, d5, e5, f5, g5, h5,
a6, b6, c6, d6, e6, f6, g6, h6,
a7, b7, c7, d7, e7, f7, g7, h7,
a8, b8, c8, d8, e8, f8, g8, h8,
boardSize
};
But of course it doesn't work, and I'm fairly certain I'm missing a very obvious problem but I can't quite spot it.

I tried it on Ubuntu and got it to pass the selftest with this change:
#define square(file, rank) ((file) + ((rank) << 3))                                       ^   ^
(For some reason it fails compilation on my Macbook now, but that must be a configuration-specific problem for OSX).

Yep, that works!  Fantastic, thank you so much for your help :)  I knew it would be something fiddly like that.  Now to integrate it into my engine!
Interestingly I'm working on OSX too, but it compiles just fine for me.  I'm using CLion and imported the repo into a CMake project.

Great!


Uncomment passing pytests

Codecov Report

:exclamation: No coverage uploaded for pull request base (datafusion-sql-planner@33ecd4b). Click here to learn what that means.
The diff coverage is n/a.

@@                    Coverage Diff                    @@
##             datafusion-sql-planner     #616   +/-   ##
=========================================================
  Coverage                          ?   61.73%
=========================================================
  Files                             ?       72
  Lines                             ?     3599
  Branches                          ?      728
=========================================================
  Hits                              ?     2222
  Misses                            ?     1230
  Partials                          ?      147

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Add automated image generation

Add ability to generate images from text.
This is done by integrating Ai images generators using their apis.
It should be a generic code as there are many type of images (gifs, jpegs, icons) that require various types of generators (dall-e, stable diffusion, and many others)

Done


Suggestion for handling dynamic embedding dims [PROPOSAL]

Here's a suggestion for an alternate way of handling embedding dimensions that vary with the model parameter. It's a simpler change (not reliant on "parameter-dependent" return types), with an added advantage: it can be used directly in index creation, in most cases saving the user from having to deal with expr_udf boilerplate. The user can just directly write
t.add_embedding_index('category', text_embed=together.embedding_fn('my_model'))
(for example).
Ad hoc creation of expr_udfs should be safe, since (unlike with ordinary udfs) we'll never actually need the path to the function.

This change is


Connection Indicator zach/nightly for Material theme

Add a connection indicator to the material theme's appBar in conversation_list or something.

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @Intellijence in #requests.

#675

#675

Closed?

This was fixed I think. Closing


Feature/delete during creating

In this pull request I add a delete button to the create form, which allows to delete added steps.

Hi Kai, looks very clear and simple to me :-) and adds another nice detail to your App 👍🏻✅


Update screenshots in README.md

Since component separators were added we should update the screenshots in README.md as that's the landing page . THEMES.md can be updated too though that will be good amount of work . @hoob3rt didn't you say you had a script for screenshots?
May be update the screenshot when diagnostics is added :) . What do you think?

I've got a script ready to create screenshots of the same size in bspwm. WIll do after I merge #95

Should be done with https://github.com/hoob3rt/lualine.nvim/commit/41e670af39ecede258e9e895bfc8d20f812b8916 and https://github.com/hoob3rt/lualine.nvim/commit/3ae9a2a483cbbfed6038b94f3817112a06518150

I'm not sure what you did in THEMES.md but the screenshots donn't have section separators ... Did you plan to add them ?

I updated all screenshots in THEMES.md to be the same size and same config to look cleaner and changed screenshots in README.md to reflect different possible configurations. I don't see an issue here

No issue . I thought your script was gona take new screenshot . Seems thats not the case 😅.

No issue . I thought your script was gona take new screenshot . Seems thats not the case 😅.

I don't get it. Literally every single screenshot is new. Take a look at how bad it looked before my change.

I don't get it. Literally every single screenshot is new. Take a look at how bad it looked before my change.

So you took screenshot while section separators disabled?

Yes, I don't know how that's hard to understand. The point of themes.md is to reflect different theme options not configuration options. There are screenshots of different configurations in readme.md.


Package 'hoauth2-<IP_ADDRESS>' is broken

Issue description
I am unable to build my Haskell project because there is a problem with either 'hoauth2-<IP_ADDRESS>', or 'yesod-auth-oauth2-0.2.1', or both.
Part of the failed build output that I think may be relevant is here:
Configuring hoauth2-<IP_ADDRESS>...
Setup: At least the following dependencies are missing:
wai ==3.2.*, warp ==3.2.*
builder for ‘/nix/store/xdqszziy6ilb8rfqzy7a553yvmj62rc9-hoauth2-<IP_ADDRESS>.drv’ failed with exit code 1
building path(s) ‘/nix/store/y70n99fmgys9di3jid3z6rg9r612pa1q-mime-mail-ses-<IP_ADDRESS>’
cannot build derivation ‘/nix/store/krsl8c1y3cc1dilxnv6cqadihh6xxcyn-yesod-auth-oauth2-0.2.1.drv’: 1 dependencies couldn't be built
killing process 29320

The full failed build output is here.
People who I think may be able to help include @peti, @LnL7, and @obadz.
Steps to reproduce
This happens as a result of NixOps trying to build and deploy my Haskell project, as you can see in the full output linked to above.
edit: Actually, this issue can be reproduced with:
nix-build '<nixpkgs>' -A haskell.packages.ghc7103.hoauth2

Technical details

Compiling project with GHC 7.10.3
System: Ubuntu 12.04 LTS
Nix version: 1.11.2
Nixpkgs version: 16.09pre88190.a4161ac

Let's see if we can get you on ghc8 with something like this: https://github.com/obadz/nixpkgs/commit/bce3672234c13643e2885cc3be6cfcaedc16ffb1


Extension causes high cpu load

Issue Type: Performance
Extension Name: vscode-pylance
Extension Version: 2024.7.1
OS Version: Windows_NT x64 10.0.22621
VS Code version: 1.91.1

:warning: Make sure to attach this file from your home-directory:
:warning:file:///c%3A/Users/ACER/AppData/Local/Temp/ms-python.vscode-pylance-unresponsive.cpuprofile.txt
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

⚠ Make sure to attach this file from your home-directory:
⚠file:///c%3A/Users/ACER/AppData/Local/Temp/ms-python.vscode-pylance-unresponsive.cpuprofile.txt

@rexuentus-viix, can you please provide this file?


[improvement][transactions] Implement ProducerStateManager recovery

I have merged manually this branch to 2.10_ds
We will start new PRs for enhancements


use pv with embed etcd deploy mode

Signed-off-by: clyang82<EMAIL_ADDRESS>

/assign @morvencao


Add tests and additional CI checks

Related to: #1
This adds some simple tests for tab completions using an expect script that tests the example/example.cr program interactively.
More tests should be added in the future for history and the wrapper modules. It might also be possible to test hints but I'm not sure since that data doesn't get echoed automatically.
Either way this is a good start.

It looks like the terminal on CI is too dumb for the example program to work and for the expect script to run successfully. Either way it's good to have more checks on CI and local tests.