Indexing error: "TypeError: Table and inner RecordBatch schemas must be equivalent."

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: Ubuntu 20 on WSL via Windows 11 Pro
- Continue: v0.8.46
- IDE: VS Code
- Model: Claude 3.5 Sonnet or GPT-4o
- config.json:

{
  "models": [
    {
      "model": "claude-3-5-sonnet-20240620",
      "provider": "anthropic",
      "apiKey": "Redacted",
      "title": "Claude 3.5 Sonnet"
    },
    {
      "model": "gpt-4o",
      "contextLength": 128000,
      "apiKey": "REDACTED",
      "title": "GPT-4o",
      "systemMessage": "You are an expert software developer. You give helpful and concise responses.",
      "provider": "openai"
    }
  ],
  "customCommands": [
    {
      "name": "test",
      "prompt": "{{{ input }}}\n\nWrite a comprehensive set of unit tests for the selected code. It should setup, run tests that check for correctness including important edge cases, and teardown. Ensure that the tests are complete and sophisticated. Give the tests just as chat output, don't edit any file.",
      "description": "Write unit tests for highlighted code"
    }
  ],
  "tabAutocompleteModel": {
    "title": "Codestral",
    "provider": "mistral",
    "model": "codestral-latest",
    "apiKey": "PnhawsLZIHCludnW7V4NS5FJ4SjI5ViN"
  },
  "embeddingsProvider": {
    "provider": "free-trial"
  },
  "reranker": {
    "name": "free-trial"
  }
}

Description
The file indexer throws an error.
To reproduce
Open a project and the Continue panel and hit the little indicator button at the bottom.
Log output
[Extension Host] error when indexing:  TypeError: Table and inner RecordBatch schemas must be equivalent.
    at new Table (c:\Users\dsieradski\.vscode\extensions\continue.continue-0.8.46-win32-x64\out\extension.js:136754:19)
    at makeArrowTable (c:\Users\dsieradski\.vscode\extensions\continue.continue-0.8.46-win32-x64\out\extension.js:143111:16)
    at LocalTable.add (c:\Users\dsieradski\.vscode\extensions\continue.continue-0.8.46-win32-x64\out\extension.js:153293:44)
    at LanceDbIndex.update (c:\Users\dsieradski\.vscode\extensions\continue.continue-0.8.46-win32-x64\out\extension.js:360745:15)
    at CodebaseIndexer.indexFiles (c:\Users\dsieradski\.vscode\extensions\continue.continue-0.8.46-win32-x64\out\extension.js:428989:37)
    at CodebaseIndexer.refresh (c:\Users\dsieradski\.vscode\extensions\continue.continue-0.8.46-win32-x64\out\extension.js:428856:30)
    at Core.refreshCodebaseIndex (c:\Users\dsieradski\.vscode\extensions\continue.continue-0.8.46-win32-x64\out\extension.js:429842:26)
    at c:\Users\dsieradski\.vscode\extensions\continue.continue-0.8.46-win32-x64\out\extension.js:429799:11
    at c:\Users\dsieradski\.vscode\extensions\continue.continue-0.8.46-win32-x64\out\extension.js:469223:20
    at i.value (c:\Users\dsieradski\.vscode\extensions\continue.continue-0.8.46-win32-x64\out\extension.js:435971:32)

Ok, I just looked at the directions and setup VoyageAI as an embedding provider and now it works without an error. So you probably need to pop-up a window that says "No embedding provider has been configured" when someone clicks on the button.

I think this error might have been unrelated to your configuration of VoyageAI. Should be patched in https://github.com/continuedev/continue/pull/2020.

@Patrick-Erichsen You're correct because now with it configured, I'm still getting the error.

I'm now encountering the same error, which is strange since the file indexing worked perfectly yesterday with a green status.
However, I'm now receiving the error: TypeError: Table and inner RecordBatch schemas must be equivalent.
I've tried everything, reloading the window, uninstalling and reinstalling the extension, but the error persists.
Any suggestions to fix the indexing would be greatly appreciated.
Thank you for your excellent work; it helps many developers improve their applications.

Same here

I got same error as well.

I got the same error.
It started after updating to version 0.8.46, no problem before.

Same error on the old project. No problems on the new one

Same for me

Same problem here

I've seen this problem intermittently as well.

Same here but it appear after a hours of using it, meaning that after finish up all the download and installation (follow exactly the step by step from the extension page), this error, will not happen immediately, it will appear after a hour or after the system reboot.

What has helped so far is deleting the contents of ~/.continue/ and rolling back to v0.8.45

What has helped so far is deleting the contents of ~/.continue/ and rolling back to v0.8.45

Well, I did that... And then it indexed all my files and it worked for ~10 minutes or so. And then:
Error updating the codeSnippets index: Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: code_snippets.path, code_snippets.cacheKey, code_snippets.content, code_snippets.title, code_snippets.startLine, code_snippets.endLine

@marcov-dart You should not deleted the all file inside ~/.continue/, just as i mentioned, only deleted the folder inside ~/.continue/index/lancedb/, reason is, several config file still need it to be the function to do the re-index step, if you deleted it, meaning that the whole function to do the re-index will be block. That what i see from the structure of ~/.continue folder.
To me, after deleted the folder and re-index, it been a day no more error appear. But i dont think it is the solution.

@marcov-dart You should not deleted the all file inside ~/.continue/, just as i mentioned, only deleted the folder inside ~/.continue/index/lancedb/, reason is, several config file still need it to be the function to do the re-index step, if you deleted it, meaning that the whole function to do the re-index will be block. That what i see from the structure of ~/.continue folder.
To me, after deleted the folder and re-index, it been a day no more error appear. But i dont think it is the solution.

In my case i did as you said (went to ~/.continue/index/lancedb/ and delete folders only related to a specific project name)
next time i open vscode it started indexing again but then i got the same exact issue
Error updating the codeSnippets index: Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: code_snippets.path, code_snippets.cacheKey, code_snippets.content, code_snippets.title, code_snippets.startLine, code_snippets.endLine

@marcov-dart i can confirm that your error is missing file from the below

autocompleteCache.sqlite
docs.sqlite
globalContext.json
index.sqlite

You may be right, but all the files you mention exist in my .continue folder. They seem to have been recreated. And indexing started at the top, reindexing everything. It managed to finished ok. And then 10 minutes or so of working on my code suddenly the SQLITE_CONSTRAINT: UNIQUE constraint failed: code_snippets.path, code_snippets.cacheKey, code_snippets.content, code_snippets.title, code_snippets.startLine, code_snippets.endLine.

Also, why can't I delete everything?
What would be the correct procedure to restart using continue entirely from scratch clearing all history and everything if not to delete this .continue folder?

Same problem here since I started using in last days. I just started to use Continue, was pretty excited and then became sad that this is not working.

Indexing error: "TypeError: Table and inner RecordBatch schemas must be equivalent."

I'm happy to see that it's a recent issue and maybe someone find a solution.

Please delete only ~/.continue/index completely and leave all other parts inside ~/.continue alone.
Do not delete only ~/.continue/index/lancedb/ or single files there, other parts in ~/.continue/index depend on this and get out of sync.

Ok, then it works. For about 5 minutes.
When I start working, saving files etc then soon after it is broken again. Using continue as it stands is more bother than it is worth. I don't want to be fighting tools I depend on so I sadly deinstalled continue.

Not sure what happen to your system @marcov-dart, but from my first post till now, the error no more appear.
Possible to remove all and reinstall back from step one?

Already done that 3 times. It will index everything which takes a while but seems to work fine. After that I do manual reindex which finishes quickly and also no problem. I can add files, modify files and remove files and reindex with no problems . Also seems to work. And then I start working and after a bit the error pops up and it stops working.

@marcov-dart Which editor and which Continue version do you use?

VsCode on macOS with continue v0.8.46 (latest release).
I also tried previous and the current pre-release version, but no dice.

Switching between version can create problems, esp. when going backwards from a Pre-Release. I'd recommend to wipe out the index folder in that case.
Also I'd recommend to stick with Pre-Releases for now, if possible, they include many fixes for the indexer. If possible also check if your code base includes files that might be problematic for the indexer (e.g. binary files, files with very long lines). Most of those files should get excluded automatically, but edge cases exist.
You can check the default ignore/exclusion patterns here -> https://github.com/continuedev/continue/blob/main/core/indexing/ignore.ts

Well, the pre-release also doesn't work. But it is ok. I removed continue and will no longer be using it.

There are two scenario.

If you open a folder, it will automatically index all the file/sub-folder into ~/.continue/index/lancedb/homexxxxxxmainvectordbOllamaEmbeddingsProvidernomic-embed-text.lance (the xxxxxx is the path folder you want to open) and at continue icon, you will see it starting index from 0% to 100%, if successful index, you will see a green button, if fail, you will get a red button (with error messages). while if it start indexing, pls dont interrrupt it, if not you will fail to index, and you will get red button (with error messages).
If you open single file, it will not doing any index, and at continue icon, you will see a gray button.

That what happen to my system.

@thyeun
Yeah it indexes from 0 to 100% then it reports it is done with a green icon. It has a created a whole bunch of folders inside the lancedb folder. (I have a few dozen folders in my workspace). It takes a while and I don't interrupt it.
But it just does not keep working. It will just fail after a while and suddenly show the red icon. I assume some actions like saving a file triggers the reindexing or maybe it is on a timer I am not sure.
And the error will not clear by itself. Restarting vscode or restarting the whole computer has no effect. The database has gotten corrupted or something. I'll have to reset everything and wait again for all the embeddings to be calculated.
As it is continue is unworkable at least for me on my system.

Some remote index services can be problematic. I have seen a few reports of Voyager being involved with error or corrupt databases (in the end).
If possible I'd recommend to stick to the default transformers.js based embeddings model (included in VSCode, just remove all embeddingsProivder and reranker blocks from your config.json), or run a local embeddings model via Ollama (embeddings models are not LLMs, they don't need much compute and should run fine on CPU), see here -> https://docs.continue.dev/features/codebase-embeddings#ollama

I AM using the default transformers.js

I AM using the default transformers.js

Interesting. Do you any other special setup? Remote SSH or other (dev-)container based things?

Nope. I have nothing special like that. Its all local filesystem on macos.

Nope. I have nothing special like that. Its all local filesystem on macos.

Thank you for the valuable information.

i only can reproduce if i manually force to re-index, after i make change on a file (save it also), than i will getting the same message as yours.
But if i not doing manually force to re-index, and finish up what ever things be change on the file (save it also) than after closing vs code, the next round after i open up vs code and i can see the continue icon will start automatically indexing. It will index successfully.
That what i can try and reproduce the error. It might different from others, or someone can try to reproduce?

Ok, I will try one more time. I have cleared everything and re-installed continue. I have not modified any settings and it immediately started the indexing. It says computing embeddings for 100 files with a progress bar. I will go get dinner and let it do its thing. I will not press the thing for manual reindexing. And see if it holds. I will report back.

FYI: Really huge repositories (like e.g. the Linux kernel with ~90k files and 5GB total size) will break the indexer currently btw. Medium sized repositories (<10k files and <1GB size) should be fine (just a rough guess, not exactly clear where the breaking point lies and there are already fixes in discussion to get rid of this problem).

@fry69 Yes, i try to reproduce with 4.8GB folder, than i will not possible to finish up the indexing, and will get fail message, after restart vs code (meaning that close and re-open back).
Kindly to double confirm here, if indexing fail, before close up vs code, for my system, i still can see the indexing button turn to green, but after close up and re-open back vs code, than only the button turn red with error message.

Never seen the indexing error again after deleting all files inside ~/.continue/index/lancedb/.
P.S.: This is a great tool, can't be more grateful to people who develop and support this project. Thank you guys!

It is also possible to disable indexing for a specific workspace folder / project. Create a file called .continuerc.json in the workspace root and put
{
	"disableIndexing": true
}

into it.

I do not think the size of my stuff is the problem. I suspect the problem is due to unclean shutdown of indexing task in my case when switching workspaces for instance while the indexing task is running. I had the SQLITE_BUSY: database is locked when switching workspaces one time.

@fry69 continuerc.json already inside ~/.continue/, or you mean for a folder that existed 5GB will need to create a file continuerc.json in this folder to avoid indexing?
Is this a solution or a temporary fix?

Thanks everyone for sharing feedback. A fix for this is on the way, as well as in general better tools to manage a corrupt state when necessary. Look out for a pre-release later today, and going forward our indexing is much more thoroughly tested, so you can expect less "fighting" of the tool. If worst comes to worst, "disableIndexing" will remain an option

Great tool, awesome work :)
I installed it yesterday and see this error. How do you install the pre-release version? What is the official 'fix' from the dev team for the current production version, if index is not disabled.

Can confirm that latest pre-release version works fine for me now.
Before that nothing worked - manually deleting index folder, etc. Given that I used default settings for embeddings (no configuration in config.json), and my codebase was extremely small - just index.html and index.js for testing purposes.
Thank you for this update!

In a folder with a lot of files, I used to get the above issue, but not with my other smaller project.
When I switch to pre-release, I get this problem in the "Extension Host" dropdown of the Output pane:

2024-08-22 01:05:44.539 [error] Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: tag_catalog.dir, tag_catalog.branch, tag_catalog.artifactId, tag_catalog.path, tag_catalog.cacheKey
2024-08-22 01:05:44.649 [error] Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: tag_catalog.dir, tag_catalog.branch, tag_catalog.artifactId, tag_catalog.path, tag_catalog.cacheKey
2024-08-22 01:05:44.744 [error] Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: tag_catalog.dir, tag_catalog.branch, tag_catalog.artifactId, tag_catalog.path, tag_catalog.cacheKey

And this issue when hovering over the error marker in my other project.

These are both remote-ssh folders.
The errors persist when I switch back to the Release candidate version. I uninstall and reinstall, and it works for my smaller project (Python) but still does not work for the larger project (PHP).

@kyleboddy Yes, if your folder larger than 5GB (a file size with more than 1mb) than this error will become very obvious.
Do you try out the pre-release version?

Yes, I did and ran into the SQLITE_CONSTRAINT errors above.

When I switch to pre-release, I get this problem in the "Extension Host" dropdown of the Output pane:

@kyleboddy 100mb you have to wait till the indexing process finish from 0% to 100%, it might need sometime, depend also your file size. But if successful indexing to 100%, your case should be no problem.

Was there a new pre-release for the vscode extension? I am not sure. I didn't notice it updating though.
In any case I tried v0.9.198 (pre-release) and this time it wasn't even able to finish to 100% after resetting everything and just leaving it alone without it failing.

After taking installing the pre-release version, there is a new error when using @codebase,
Error getting context items from codebase: TypeError: db.search is not a function
download open-webui and try @codebase to repro. Not ready for primetime just yet, invest in qa :)

Experienced same issue on Mac OS (some workspaces but not all), switching to latest pre-release version resolved. Thank you so much, guys!

Vscode extension pre-release v0.9.199 does NOT fix the problems on Mac OS for me.

I deleted the whole index folder.
It will start indexing and does complete with "index up to date"
The index folder is 293 Mb in size afterwards
I cannot close vscode and reopen it. It will report "Indexing error - click to retry" and when hovering over it then it says "TypeError: Cannot read properties of undefined (reading 'id')"
I cannot do a manual indexing after it finished and says "index up to date" either. It will start saying "indexing 3 files" and bug out.

I don't know what is going on or why it is so hard to get this right, but there you go.

Yeah, so it was ok for about an hour and then I switched to another workspace. The indexing at the time was not running or at least not showing to be running. I checked before switching. It started reindexing after switching to the new workspace and then failed with "TypeError: Cannot read properties of undefined (reading 'id')".

@marcov-dart Are you using pre-release?

Was Specified:
Vscode extension pre-release v0.9.199 does NOT fix the problems on Mac OS for me.

I did some debugging on this. the schema is in fact different when trying to store the files, but I have no idea why.  Attaching the json export of the schema of the db vs the requested schema.  It's an intermittent problem.
batch.schema.json
schema.json
--- schema.json	2024-08-23 09:43:09.039580400 -0400
+++ batch.schema.json	2024-08-23 09:43:43.411651000 -0400
@@ -41,7 +41,7 @@
             "type": {
                 "precision": 2
             },
-            "nullable": false,
+            "nullable": true,
             "metadata": {}
         },
         {
@@ -49,13 +49,13 @@
             "type": {
                 "precision": 2
             },
-            "nullable": false,
+            "nullable": true,
             "metadata": {}
         },
         {
             "name": "contents",
             "type": {},
-            "nullable": false,
+            "nullable": true,
             "metadata": {}
         }
     ],

This should now be completely resolved. If anyone is still experiencing the problem though, please re-open the issue and let me know!

fixed for me in v0.9.200 (WSL2)

Same, no problems here anymore either (for the last 4 hours). Is looking good. v0.9.200 as well.
Thanks!

Unfortunately I spoke to soon...
I opened up a 2nd workspace. The 2nd workspace started to do some indexing but then seems to be blocked by the other. And then after closing vscode and starting it back up now "SQLITE_BUSY: database is locked"

Fix with the new version worked for me too. I'm running local with only one workspace however.

I'm still using 0.8.47 version (linux), dont hv any issue, can auto-indexing, re-indexing and etc for more than 2 to 3 days.


Wait longer for cert manager in baseprofiles test

What type of PR is this?
/kind failing-test
What this PR does / why we need it:
We timeout waiting for cert manager which should be now more stable.
Which issue(s) this PR fixes:

None
Does this PR have test?
None

Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

Codecov Report

Merging #1641 (4ac4572) into main (f411119) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1641   +/-   ##
=======================================
  Coverage   48.65%   48.65%
=======================================
  Files          69       69
  Lines        6785     6785
=======================================
  Hits         3301     3301
  Misses       3353     3353
  Partials      131      131


Backdrop shows, but no actual dialog

Hello,
I have this script:

var tour = new Tour({
	debug: true,
    storage: false,
    keyboard: false,
        onEnd: function (tour) {
	        window.location.replace("http://daltonempire.nl/?tour=false");
    },
        steps: [
        {
          orphan: true,
          title: "Welcome to DaltonEmpire!",
          content: "Congratulations!

 You just successfully logged in for the first time!
This tour will take you through the uses of DaltonEmpire in simple steps.

You can always exit the tour if you want to, and you can redo it anytime in the dropdown of your username in the top-right corner.

For now, just click next",
          backdrop: true
      }, {
          element: "#commentsys",
          placement: "top",
          title: "Comments",
          content: "If you want to, you can always leave a comment and share your opinion on DaltonEmpire right here on the homepage."
      }, {
          element: "#rankingsys",
          placement: "top",
          title: "Ranking",
          content: "Also, this is a small tabel in which users are ranked on their number of uploaded documents."
      }, {
          element: "#homepage",
          placement: "bottom",
          title: "Navigation",
          content: "DaltonEmpire is centered around two pages, Upload and Download.
These are essential during your stay."
      }, {
        element: "#uploadpage",
        placement: "bottom",
        title: "Navigation",
        content: "Now navigate to the Upload page.",
        next: -1,
        onShow: function(tour){
	        $("#uploadpage").attr("href", "/Upload");
        }
       }

    ]
});

This is valid Javascript, bootstrap-tour.min.js and bootstrap-tour.min.css are included.
Bootstrap-Tour says the console Bootstrap Tour 'tour' | Show the orphan step 1. Orphans option is true.,  as it should. The backdrop is there, but no dialog is to be seen, tested from various browsers.

Also, the console gives the error Uncaught TypeError: undefined is not a function, caused by line 6 of the bootstrap.min.js. This disappears if I exclude the script above. However, the script is valid and all the elements referred to, exist.
Why doesn't the dialog shows (it isn't even present on the page, even not in the source), and what causes the TypeError (which probably causes the problem itself)?
P.S. Even including just one step, with or without backdrop, the dialog refuses to show its face.

I feel horrible. I hadn't noticed the version was updated, but now I use the newest version and the standalone and all works.. Thanks!


Can you provide examples for the ASP.NET TypeScript ecosystem?

As a Microsoft consultant I am eager to see ready-to-use examples that are based on the ASP.NET 4.6 or even 5 stack ideally combined with TypeScript. Any plans?

You could add a type definition... http://definitelytyped.org/
Though, to be honest, this has almost nothing to do with ASP.Net, and most of the exposed interfaces are meant to accept functions.

We're only going to support a single server rendering example—with Node, because that's what most people who do server rendering use, and it's easiest to maintain because it uses the same ecosystem and tooling (Babel, NPM, etc).
We have a recipe on server rendering which may give you an idea of how to make it work on other platforms as long as they can run some JavaScript. If you're not interested in server rendering, from ASP .NET's point of view, using Redux isn't any different from using Backbone or any other client-side library.
I'm closing since there is nothing actionable here for us, but feel free to continue the discussion.


What is the results of your model on COCO 1x training?

Hi! what is mask ap results for 1x training of BCNet using mask-rcnn?

Aslo, for fair comparison, 3x PointRend can achieve 38.0 on val set (38.2 on test dev) using detectron2. Why your PointRend result is 36.3 since your model come from 3x traing?

Hi! what is mask ap results for 1x training of BCNet using mask-rcnn?

I remembered that I did't test a 1x training Faster R-CNN on coco-test-dev. The results of PointRend would be corrected after my further checking. I am in a very tight paper ddl these days, and will further response your question under this issue after it.

https://arxiv.org/pdf/2105.11668.pdf
I think it may miss a comparison on coco-test-dev. Since both methods are using boundary for instance segmentation. We have released our 3x training checkpoint and results.

I will cite all your work.


Invalid error using Null type as an iterable in a for-in

Null x;
for(var i in x) {...}

CFE accepts this, analyzer rejects it. My understanding is that it should be statically valid code.
Post-nnbd, this won't be, but we need to be careful that this might(?) need to work @leafpetersen to confirm.
Never x;
for(var i in x) {...}

I'm not sure this is valid code now.
The specifcation was changed recently to require the iterated object to be an Iterable.
The spec now says:
\begin{normativeDartCode}
$T$ $\id_1$ = $e$;
\VAR{} $\id_2$ = $id_1$.iterator;
\WHILE{} ($\id_2$.moveNext()) \{
\ \ $D$ \id{} = $\id_2$.current;
\ \ \{ $S$ \}
\}
\end{normativeDartCode}

\noindent
If the static type of $e$ is a top type
(\ref{superBoundedTypes})
then $T$ is \code{Iterable<dynamic>},
otherwise $T$ is the static type of $e$.
It is a compile-time error if $T$ is not assignable to \code{Iterable<dynamic>}.

In short, the for-in loop is equivalent to code starting with:
Null id_1 = null;
var id_2 = id_1.iterator;

This is not type correct, so the program is not valid.
The analyzer matches the specification (the specification might have been changed to match the analyzer, but we did it on purpose).
For Never, I'm not sure whether we'll make it an error to have unreachable code, the example above is definitely invalid because it fails to initialize a non-nullable variable (Never is not nullable) before it's used.
If you had:
Never x = throw "Banana";
for (var y in x) ...

then I guess the same problem would occur when you try to do id_1.identifier where id_1 has type Never. (Unless we decide to allow member access on Never and just give it type Never again).

I don't think the runtime behavior leads to clear static rules, and that both should be specified separately rather than one inferred from the other, in cases like this.
For instance, this:
It is a compile-time error if $T$ is not assignable to \code{Iterable<dynamic>}.

makes me think that there is no compile time error when $T$ is Null.

The rule that It is a compile-time error if $T$ is not assignable to \code{Iterable<dynamic>} is an extra constraint, and we still have the general rule here specifying that errors in desugared code are taken into account (even though the error message should of course not refer to code that the developer has never seen).

analyzer and CFE seem to both accept this still, with Never:
void f(Never x) {
  for (var i in x) {
    print(i);
  }
}

analyzer and CFE seem to both accept this still, with Never:
void f(Never x) {
  for (var i in x) {
    print(i);
  }
}

Not sure that it should be an error for Never since Never is a subtype of Iterable and allows .iterator to be invoked on it.
In sound null safe code, it won't ever get there with a value implementing Null.
In unsound code, it the value might be null, and that will just cause a run-time error.
Statically typing as Null is different because Null does not allow .iterator like Never does.

Not sure that it should be an error for Never since Never is a subtype of Iterable and allows .iterator to be invoked on it.
In sound null safe code, it won't ever get there with a value implementing Null.
In unsound code, it the value might be null, and that will just cause a run-time error.
Statically typing as Null is different because Null does not allow .iterator like Never does.

Ok leaving analyzer as is, as this is solved for null safety; analyzer does the right thing.

Ok leaving analyzer as is, as this is solved for null safety; analyzer does the right thing.


some special error on page

** version:**
[ ] cordova -vc 6.5.0
[ ] ionic -v 2.2.1
[ ] node -v
when use ionic run android ,the application is ok,
but when i use shell command  pm intsall xx.apk (the apk is created by ionic ) ,it usually have some error ,
such as ,when i jump to a -> b ->c, i always stay at  b.can't go back to a and cant' trun to c .( i have do smthing on page b such as open the mass storage).
however ,if i reboot the device, the error never appears. it just happen in the first time i use the command to install the apk .
could you help me ,thanks very much .

This is more likely a support request.
Besides opening a forum thread, I recommend using Rollbar, to track JavaScript issues (rollbar for browser, not rollbar native)

Hello! Thanks for opening an issue with us! As this seems like more of a support question i will urge that you ask this question on our forum or on our slack channel. Thanks for using Ionic!


#1161, Trinity logs should automatically rotate across runs

What was wrong?
#1161, Trinity logs should automatically rotate across runs
How was it fixed?
Log rotation per instantiation of the client with format, YYYYMMDD_HHMMSS. File name would look like trinity_20191024_095854.log.

Re-ran the tests.

Hi @mhchia ,
Those errors seem not relative to my commitment. Could you help check it? Thanks :)

@KimiWu123 I believe these CI fails would vaporize if you rebase on top of latest master. The reason for those is (I believe) that the underlying fixtures submodule was recently updated so the tests in this PR does not work with them until you rebase on top of latest master.


Pytest dep

Hi there,
Thanks for taking the time to create anchorpy and reading this. Any specific reason why pytest is included as a dependency and not in dev dependencies?

It's an actual dependency because anchorpy ships with a pytest plugin

I think ideally the pytest plugin would be a separate package

Please open an issue if this is causing problems for you


Approach to image optimisation, esp for retina screens

Not sure exactly the best way to do this but need to investigate, e.g. http://www.filamentgroup.com/lab/compressive-images.html
These include:

Loading screen logo
Question images
Connect images (curator, content images)

Lots here to digest. One thing to keep in mind is using a reasonably good standard image doesn't ruin the experience for a retina user - it is mildly diminished but if the images are not mixed (retina and non-retina) on the same site it is less obvious. Let me do a couple tests and then maybe we can test a few online to find our sweet-spot. This would be easier is we weren't dealing with images of artwork that need to be pretty faithful.

Here is a link to 3 images each sized 5 different ways.
I did one at 150% of retina size - I don't think it is worth trying 200%. Oversizing and then over-compressing has a lot of associated problems and I would lean heavily towards a retina sized at 100% and compressed medium-low. There is a lot of discussion about all this and no great consensus but it seems to me people are generally (maybe you know better) using the @2x to serve a file for retinal and a different file for the others. In this case I'd lean towards 768px images at 50-60 compression.
I've colour-coded the matching sizes in this link and named with px size and compression:
https://www.dropbox.com/sh/vrwab6axzo6id69/AADjx47y1qvbEjO7FIW_T2QDa?dl=0

Also keep in  mind most of our images won't need to be full screen necessarily so these kb sizes would be less.

Excellent. Thanks for the experiments. You're right about the @x2. I'm going to use something like this:
http://imulus.github.io/retinajs/
The only thing to be aware of is the naming convention: for example my_image.png and<EMAIL_ADDRESS>so basically you add @2x to the end of the filename and it should all work well!
Closing this issue.

Adding this link about ideal image size as it might come in useful:
http://www.themepunch.com/faq/ideal-image-size/


Upper case letters in path causing match to fail

What version of Hugo are you using (hugo version)?

$ hugo version
Hugo Static Site Generator v0.74.3-DA0437B4/extended linux/amd64 BuildDate: 2020-07-23T16:30:30Z

Does this issue reproduce with the latest release?
yes
Probably easiest to read jmoorings comment on the forum:
https://discourse.gohugo.io/t/upper-case-letters-in-path-causing-match-to-fail/28069
Basically there seems to be an issue when matching folder names that have upper case letters in. jmooring suggests it is because case normalisation is being done on the pattern, rather than on the directory path.

I accidentally duped this bug (as jmooring noticed) - but it still happened 29 days ago on the most recent hugo back then:
hugo v0.81.0-59D15C97 linux/amd64 BuildDate=2021-02-19T17:07:12Z VendorInfo=gohugoio

I accidentally duped this bug (as jmooring noticed) - but it still happened 29 days ago on the most recent hugo back then:
hugo v0.81.0-59D15C97 linux/amd64 BuildDate=2021-02-19T17:07:12Z VendorInfo=gohugoio

Still suffering this bug in the latest Hugo version:
hugo v0.83.1-5AFE0A57+extended linux/amd64 BuildDate=2021-05-02T14:38:05Z VendorInfo=gohugoio

Still reproducible with v0.100.1
MRE
git clone --single-branch -b hugo-github-issue-7686 https://github.com/jmooring/hugo-testing hugo-github-issue-7686
cd hugo-github-issue-7686
hugo server

@satotake This is still failing with https://github.com/gohugoio/hugo/commit/281554ee97eb243af097611aaf6bfec8940ad6d1. Is that expected?
git clone --single-branch -b hugo-github-issue-7686 https://github.com/jmooring/hugo-testing hugo-github-issue-7686
cd hugo-github-issue-7686
hugo server

My motivation of https://github.com/gohugoio/hugo/commit/281554ee97eb243af097611aaf6bfec8940ad6d1 was from my own situation and I have never seen this issue. Not sure whether expected or not at the moment.
Anyway I will take a look at this tomorrow. @jmooring

@jmooring have you tested it with ... Hugo 0.104.0?

have you tested it with ... Hugo 0.104.0?

Yes, still fails.

Yes, still fails.

That is certainly odd, oh well.
What I wish for my next life is that very OS implemented a file system with forward slashes and filenames limited to lower case ascii.

https://github.com/gohugoio/hugo/pull/10305 did not consider case-unmatched patterns.
So I had no expectation of {{ with resources.GetMatch "images/abc/*" }} for assets/images/ABC/kitten.jpg (though I have found that we should cover the case now.)
However, it is unexpected that {{ with resources.GetMatch "images/ABC/*" }}  does not match the image.
Seemingly, we need more test and fixations.
Thanks for pointing out @jmooring

I wish for operating system APIs that handle path components more like
objects than strings, and for all APIs to just automatically do the right
thing for UTF8, and that every programmer wonders every time they touch a
string, "will this work for UTF8?"
But I have screwed it up myself plenty of times so I know that's a pipe
dream.
On Fri, Sep 23, 2022, 11:12 Bjørn Erik Pedersen @.***>
wrote:

Yes, still fails.
That is certainly odd, oh well.
What I wish for my next life is that very OS implemented a file system
with forward slashes and filenames limited to lower case ascii.
—
Reply to this email directly, view it on GitHub
https://github.com/gohugoio/hugo/issues/7686#issuecomment-1256404720,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALGLJIMKDBGHFIEPCEJQKDV7XJF3ANCNFSM4RLJMUGQ
.
You are receiving this because you commented.Message ID:
@.***>


New import script, update tree sitter grammars to newest available version

The import of syntax nodes from the installed tree sitter grammars now keeps the currently included mappings between syntax nodes and metrics specified in the current nodeTypesConfig.json-file instead of creating a new file without any mappings, reducing the maintenance work.
Furthermore, this does not include unnamed nodes other than the different kinds of binary expressions in the config-file. This again improves maintainability and prevents errors caused by unnamed nodes that have the same name as named nodes in another language, like the error in #30 caused by the "function" node of the JavaScript-grammar representing an inline function, while for PHP, its just a keyword.
In order to handle any breaking changes of the language grammars regarding the metric calculation process, the new script prints warning messages if a syntax node was removed from a language that was used to calculate a metric before. An overview over all syntax nodes which were added, removed or only for some languages added or removed from the grammars, a changelog with this information is written as a CSV-file by the import script.
Updating all tree sitter grammars and importing the syntax nodes with the new script works just fine for the file metrics, however, the substantial changes in the tree sitter grammar for PHP demand changes in the source code of the coupling metric. Therefore, this includes some manual changes in the queries of the coupling code to make them compatible with the new grammar.
NOTE: This does as of yet only manage to make the test case for PHP run successfully again. There seem to be many additional cases in the grammar for the changed parts which are not covered by the code, both new cases and also cases that were already present in the old grammar, so this has been an issue before and should be fixed by another PR (see #45).
Additional improvements:

Fixes TODO: fromClassName and toClassName are broken  in src/parser/metrics/coupling/Coupling.ts and updates snapshots accordingly to have the correct fromClassName.

Closes #24

I have noted that the order of the new nodes being imported is not deterministic, which is probably caused by the asynchronous updateLanguage function, as the order in which languages are processed depends upon, for example, for which language the readFile-operation for the node-types.json-file completes first. This of course makes it harder to compare whether some changes to this script do lead to an equal result.


Feature request - Private hipchat support

It would be nice to be able to specify a hipchat server in the configuration for those of us with private self-hosted hipchat enterprise servers.

I would also like this.  A minimal implementation of this should just require taking where hipchat.go currently hardcodes "api.hipchat.com", and instead allow the host to be passed in.  The API for the SaaS and privately hosted HipChat products are exactly the same.

closing. merged pull request to add this functionality a while back


[iOS][Dev-tool] Input max-length property does't work

Describe the bug
input max-length property does't work
To Reproduce
demo: http://dotwe.org/vue/d2719749f8b386fca525441b5c8d5f63
Environment
weex-playground
Expected behavior
max-lenth to control input length
Screenshots

The valid attribute is maxlength.
Related issues #2380 , #3180

Please update the document then, it's confusing.
english doc
chinese doc


Discard all changes deletes all files from unrelated folder

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.67.1
OS Version: MacOS Bigsur

Steps to Reproduce:

create a file in any folder (in my case it was the Download folder), open this file dragging into VSCode window
notice it will show up more than 10k files in the Source Control button
discard all changes
notice every single file from downloads folder and subfolders from Download folder and user profile folder as well will be deleted... every single file

this doesn't seems to be the correct behavior... is it?
Now, where are all my files? Because none of them are in Trash or something. For some weird (and unknown reason) the only files that weren't deleted was from 'repos' folder... but all other folders and files are now gone

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.67.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

@ofabrizio, apologies for not getting back to you on this. When you open a file/folder/workspace, VS Code will execute git.exe to discover any repositories that should be displayed in the Source Control view. It seems that git.exe has discovered a repository somewhere on the path of the file that was opened. Did you have a git repository somewhere on the path?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


_reactNativeMdm2.default.isSupported is not a function.

Hi @ajwhite
I am very glad someone has built this bridge for react native to better integrate with MDM. Thank you!
However, I keep getting this error saying
TypeError: _reactNativeMdm2.default.isSupported is not a function
or
TypeError: _reactNativeMdm2.default.getConfiguration is not a function
I called these function exactly like instructed in your README.md file.
Is something deprecated or changed?
I am on "react-native-mdm": "^1.0.4"
Thanks

@yuxiaoma could you double check that you've properly linked the Native Module on the native side? It doesn't look like we describe the setup process, apologies. You'd link it natively like you would normally with a RN module; no extra steps with react-native-mdm

yes, that turns out to be the issue. thanks for the quick reply.
Guild for RN linking libraries, in case anyone have the same problem:
https://facebook.github.io/react-native/docs/linking-libraries-ios.html

FYI the app halts on device, and quit on similator.

Is this happening on Android or iOS?

react-native link react-native-mdm

Looks like we haven't added support for automated linking. In the meantime, reset your changes and link manually

This is happening on iOS.
I will try to link manually, but it would great if the package has automated linking support.

it would great if the package has automated linking support.

For sure, let's keep this issue open to track that

Hi, I have a problem with building the app with react-native-mdm library for iOS.  Below is the error which I get:
node_modules/react-native-mdm/ios/RNMobileDeviceManager.h:8:9: fatal error: module 'AppConfigSettingsFramework' not found
I did manual link of the library to my Xcode project. I added AppConfigSettingsFramework.framework and libRNMobileDeviceManager.a libraries to the "Link Binary With Libraries" section in Build Phases and locally it works, but on the build server I get an error. It looks like RNMobileDeviceManager library is build before AppConfigSettingsFramework. How can I enforce proper build order?

Hi, i have the same problem, i solved it opening the RNNMobileDeviceManager.xcodeproj and setting in 'Build Phases' 'AppConfigSettingsFramework' as Target Dependencies.

Hi all. @DiegoNegri and @ajwhite I was facing the same issue after running yarn add<EMAIL_ADDRESS>and launching the project. I then ran cd ios && pod install and launched the project again in the emulator and it worked.

@ajwhite @DiegoNegri can i get Screen time in the IOS using this library. Please provide me detail for this.


Add the description about TsClean to docs

TsClean-IoTDB is a UDF library of Apache IoTDB. It implements many key functions of TsClean, a data quality system of time series,  including data quality indicator calculation, value filling, value repairing, etc.
This pull request adds the description about it to docs/UserGuide/Operation Manual/UDF User Defined Function.md and docs/zh/UserGuide/Operation Manual/UDF User Defined Function.md.

Hi, could you update the webpage you give, to remove "How to package the project" chapter? There is no so called "project".


Reader toolbar button blurry on non-retina

I'm pretty sure I got it this time.  Let me know if you see anything wrong.


Refactored CanHacker and Added Common_Can Support

Refactored CanHacker to remove tight integration of MCP2515 driver
Added integration with common_can library that provides wrappers to use MCP or STM drivers

JIRA EN-1122

Verified this with can_multitool communicating with the Pi.


API examples inlined in API documentation

Our documentation needs more examples of code usage where the code is documented. Some users have requested better examples.

Addressed this in 1549dc742aa2e53446b9ae75bb55341cb8a493b0 and b74032fdae97f1d3f9c78feac577554e6b837640.


ROS2 on Windows, #warning is not recognized by VS

In this deprecated header: https://github.com/ros/pluginlib/blob/9b319f1440a7153d6edf68067093449ff7b14201/pluginlib/include/pluginlib/class_list_macros.h#L36
Possible solutions:

Use #pragma message("...")
Surround #warning checking for compiler
Remove the deprecated header and break things

More discussion about solutions
https://stackoverflow.com/questions/2685598/warning-in-visual-studio

I think we removed this a long time ago, so going ahead and closing this one.


Time-series sliding window doesn't affect the time axes

Describe the bug
I'm using your tool and it has been of great help so far. I just noticed that the time axes stays stuck to the values of the initial window. If I move the window or change its size the plot does move but the time axes isn't affected.
To Reproduce
Here is a test file I used and imported as a new time-series in a new project.
test.csv
I configured the labeling interface with this code:
<View>
  <TimeSeries name="ts" valueType="url" value="$csv" sep="," timeColumn="timestamp" timeFormat="%Y-%m-%d %H:%M:%S" timeDisplayFormat="%Y-%m-%d" overviewChannels="value">
    <Channel column="value" displayFormat=",.1f" strokeColor="#000000"/>
  </TimeSeries>
  <TimeSeriesLabels name="label" toName="ts">
    <Label value="anomaly" background="#FFA39E"/>
  </TimeSeriesLabels>
</View>

You can just open the task and move the window. The data will slide but not the time axes.
Expected behavior
I expected to have a time axis with labels (time values) corresponding to the window.
Screenshots
When opening the task

After moving the window

Environment (please complete the following information):

OS: MacOs Catalina 10.15.3
Browser: Google Chrome - Version 92.0.4515.159
Label Studio Version 1.2

Duplicated by https://github.com/heartexlabs/label-studio/issues/1329


Is Support get gpu metric on windows?

I have the same question.

it looks like it can not build and run in Windows OS


Need to add security headers and CORS policies

4
5
6
7
8
9
10
11
12
13
14
15
16
Title: Need to add security headers and CORS policies
As a service provider
I need my service to use security headers and CORS policies
So that my web site is not vulnerable to CORS attacks
#### Assumptions
* Flask-Talisman will be used for security headers
* Flask-Cors will be used to establish cross-origin resource sharing (CORS) policies
#### Acceptance Criteria
gherkin     Given the site is secured     When a REST API request is made     Then secure headers and a CORS policy should be returned


Rails 5.0.2 commas separating tags are being removed when tags are displayed in a text field

View (same code used to create and update):
<div class="form-group">
    <%= f.label :tag_list, "Tags (comma separated)" %>
    <%= f.text_field :tag_list, class: "form-control", placeholder: "Add tags" %>
 </div>

Model and corresponding controller are modified as explained in the documentation
When creating a new article with tags, they are properly stored in DB and displayed if rendered using
<%= @article.tag_list %>: tag1, tag2, tag3
However, when editing the same article tags are set as 1 tag and the commas separating each of them is removed.
Rails: version 5.0.2
PostgreSQL
act-as-taggable-on from git

Answer is in the Wiki...


Minor performance tweaks to match the guide.

I believe these are still NHWC which I did not want to mess with.  I fixed the following:

Input pipeline on CPU
batch_norm fused
for AlexNet I moved the local_ps_device to GPU which is the better option if the GPUs are peered and about equal to CPU:0 otherwise.  No fancy NCCL which does not seem to work well on K80s and no non-NCCL replicated variables which would likely speed this up as well.
I added a flag to both for local_ps_device and set it to the default that I expect works the best on K80s and likely P100s as well.
I fixed the eval to set is_training = False.  Does not matter for perf testing but that is how it is supposed to be.
ResNet also converges to a slightly better loss now due to a change in the learning rate.  It could be better but I was not interested in adding a learning rate decay right now.
AlexNet converges to the same level as before but I think a little faster but that might be luck.
I noticed your K80 is clocked at ~500Mhz.  The normal is ~845Mhz that seemed weird but I assume consistent.
I also did some general cleanup where the losses were added to a collection and then taken out and then added to nothing and then I am not sure what it was but it was not needed.
Finally, off the top of my head the numbers I see:
AlexNet 4 GPUs  ~70ms on AWS with 4 K80s using the CPU as the PS_server this is ~100ms
ResNet 4 GPUs ~140ms on AWS and Google Cloud
Both are I think 50% or more savings in time or 2x speedup or whatever.

Some people think that the batch_norm is not doing beta and gamma.  Check the code it is built into the function you should do not control how it is initialized.
Finally, the changes I made are not exotic now am I really skilled. I just added the basic that I would suggest for anyone else.  I might change it over to NCHW but this seemed good enough for now.  I think we are about to push a "crazy" alexnet in our benchmark that uses some fun staging ops but I did not want to mess up your scripts.

thank you @shyhuai   If you have any questions just ask.  This is not perfect but a little better without too much work.

Thank you for contributing to the project!

@tfboyd many thanks for your contribution and the detailed comments in improving the codes. We will update the results to our website soon.


Git Extension doesn't detect repo - MacOS homebrew

Type: Bug
Open any folder in which there is an initialized git repo.  I have not yet found root cause but current theory is that the extension cannot handle a symlinked git binary as with homebrew.
I am using default settings for git extension on a completely clean install.
VS Code version: Code - Insiders 1.95.0-insider (fe997185b5e6db94693ed6ef5456cfa4e8211edf, 2024-10-23T05:06:13.568Z)
OS version: Darwin arm64 24.0.0
Modes:

System Info

Item
Value

CPUs
Apple M1 (8 x 2400)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
2, 2, 3

Memory (System)
8.00GB (0.10GB free)

Process Argv
--log vscode.git=trace --crash-reporter-id f58ace6f-1116-4b33-80b7-c3f39217abbf

Screen Reader
no

VM
0%

Extensions: none
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
vsaa593cf:30376535
py29gd2263:31024238
c4g48928:30535728
962ge761:30841072
pythongtdpath:30726887
pythonnoceb:30776497
asynctok:30898717
dsvsc014:30777825
dsvsc015:30821418
pythonmypyd1:30859725
h48ei257:31000450
pythontbext0:30879054
cppperfnew:30980852
pythonait:30973460
0ee40948:31013168
dvdeprecation:31040973
dwnewjupyter:31046869
2f103344:31071589
nb_pri_only:31057983
nativerepl1:31134653
refactort:31084545
pythonrstrctxt:31093868
wkspc-onlycs-t:31132770
nativeloc1:31118317
wkspc-ranged-t:31151552
cf971741:31144450
e80f6927:31120813
autoexpandse:31146404
12bdf347:31141542
iacca1:31150324
notype1:31143044
dwcopilot:31158714
g7688163:31155431

Logs:
024-10-23 09:45:11.406 [info] [main] Log level: Trace
2024-10-23 09:45:11.406 [info] [main] Validating found git in: "opt/homebrew/bin/git"
2024-10-23 09:45:11.438 [info] [main] Using git "2.47.0" from "opt/homebrew/bin/git"
2024-10-23 09:45:11.438 [info] [Model][doInitialScan] Initial repository scan started
2024-10-23 09:45:11.438 [trace] [Model][doInitialScan] Settings: autoRepositoryDetection=true, openRepositoryInParentFolders=prompt
2024-10-23 09:45:11.438 [trace] [Model][onDidChangeWorkspaceFolders] Workspace folders: []
2024-10-23 09:45:11.440 [info] [Model][doInitialScan] Initial repository scan completed - repositories (0), closed repositories (0), parent repositories (0), unsafe repositories (0)
2024-10-23 09:45:13.368 [trace] [Model][onDidChangeConfiguration] Workspace folders: []
2024-10-23 09:45:15.491 [info] [main] Log level: Trace
2024-10-23 09:45:15.491 [info] [main] Validating found git in: "opt/homebrew/bin/git"
2024-10-23 09:45:15.500 [info] [main] Using git "2.47.0" from "opt/homebrew/bin/git"
2024-10-23 09:45:15.501 [info] [Model][doInitialScan] Initial repository scan started
2024-10-23 09:45:15.501 [trace] [Model][doInitialScan] Settings: autoRepositoryDetection=true, openRepositoryInParentFolders=prompt
2024-10-23 09:45:15.501 [trace] [Model][onDidChangeWorkspaceFolders] Workspace folders: [/Users/jpshack/code/aider]
2024-10-23 09:45:15.501 [trace] [Model][scanWorkspaceFolders] Workspace folder: /Users/jpshack/code/aider
2024-10-23 09:45:15.501 [trace] [Model][openRepository] Repository: /Users/jpshack/code/aider
2024-10-23 09:45:15.505 [trace] [Model][openRepository] Opening repository for path='/Users/jpshack/code/aider' failed. Error:spawn opt/homebrew/bin/git ENOENT {
  "gitErrorCode": "NotAGitRepository"
}Error: spawn opt/homebrew/bin/git ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:286:19)
	at onErrorNT (node:internal/child_process:484:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-10-23 09:45:15.507 [trace] [Model][scanWorkspaceFolders] Workspace scan settings: repositoryScanMaxDepth=1; repositoryScanIgnoredFolders=[node_modules]; scanRepositories=[]
2024-10-23 09:45:15.507 [trace] [Model][scanWorkspaceFolders] Workspace scan sub folders: [/Users/jpshack/code/aider/.aider.tags.cache.v3, /Users/jpshack/code/aider/.github, /Users/jpshack/code/aider/.pytest_cache, /Users/jpshack/code/aider/aider, /Users/jpshack/code/aider/aider_chat.egg-info, /Users/jpshack/code/aider/benchmark, /Users/jpshack/code/aider/docker, /Users/jpshack/code/aider/scripts, /Users/jpshack/code/aider/tests, /Users/jpshack/code/aider/website]
2024-10-23 09:45:15.507 [trace] [Model][openRepository] Repository: /Users/jpshack/code/aider/.aider.tags.cache.v3
2024-10-23 09:45:15.508 [trace] [Model][openRepository] Opening repository for path='/Users/jpshack/code/aider/.aider.tags.cache.v3' failed. Error:spawn opt/homebrew/bin/git ENOENT {
  "gitErrorCode": "NotAGitRepository"
}Error: spawn opt/homebrew/bin/git ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:286:19)
	at onErrorNT (node:internal/child_process:484:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-10-23 09:45:15.508 [trace] [Model][openRepository] Repository: /Users/jpshack/code/aider/.github
2024-10-23 09:45:15.508 [trace] [Model][openRepository] Opening repository for path='/Users/jpshack/code/aider/.github' failed. Error:spawn opt/homebrew/bin/git ENOENT {
  "gitErrorCode": "NotAGitRepository"
}Error: spawn opt/homebrew/bin/git ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:286:19)
	at onErrorNT (node:internal/child_process:484:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-10-23 09:45:15.508 [trace] [Model][openRepository] Repository: /Users/jpshack/code/aider/.pytest_cache
2024-10-23 09:45:15.509 [trace] [Model][openRepository] Opening repository for path='/Users/jpshack/code/aider/.pytest_cache' failed. Error:spawn opt/homebrew/bin/git ENOENT {
  "gitErrorCode": "NotAGitRepository"
}Error: spawn opt/homebrew/bin/git ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:286:19)
	at onErrorNT (node:internal/child_process:484:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-10-23 09:45:15.509 [trace] [Model][openRepository] Repository: /Users/jpshack/code/aider/aider
2024-10-23 09:45:15.510 [trace] [Model][openRepository] Opening repository for path='/Users/jpshack/code/aider/aider' failed. Error:spawn opt/homebrew/bin/git ENOENT {
  "gitErrorCode": "NotAGitRepository"
}Error: spawn opt/homebrew/bin/git ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:286:19)
	at onErrorNT (node:internal/child_process:484:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-10-23 09:45:15.510 [trace] [Model][openRepository] Repository: /Users/jpshack/code/aider/aider_chat.egg-info
2024-10-23 09:45:15.510 [trace] [Model][openRepository] Opening repository for path='/Users/jpshack/code/aider/aider_chat.egg-info' failed. Error:spawn opt/homebrew/bin/git ENOENT {
  "gitErrorCode": "NotAGitRepository"
}Error: spawn opt/homebrew/bin/git ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:286:19)
	at onErrorNT (node:internal/child_process:484:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-10-23 09:45:15.510 [trace] [Model][openRepository] Repository: /Users/jpshack/code/aider/benchmark
2024-10-23 09:45:15.511 [trace] [Model][openRepository] Opening repository for path='/Users/jpshack/code/aider/benchmark' failed. Error:spawn opt/homebrew/bin/git ENOENT {
  "gitErrorCode": "NotAGitRepository"
}Error: spawn opt/homebrew/bin/git ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:286:19)
	at onErrorNT (node:internal/child_process:484:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-10-23 09:45:15.511 [trace] [Model][openRepository] Repository: /Users/jpshack/code/aider/docker
2024-10-23 09:45:15.511 [trace] [Model][openRepository] Opening repository for path='/Users/jpshack/code/aider/docker' failed. Error:spawn opt/homebrew/bin/git ENOENT {
  "gitErrorCode": "NotAGitRepository"
}Error: spawn opt/homebrew/bin/git ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:286:19)
	at onErrorNT (node:internal/child_process:484:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-10-23 09:45:15.511 [trace] [Model][openRepository] Repository: /Users/jpshack/code/aider/scripts
2024-10-23 09:45:15.512 [trace] [Model][openRepository] Opening repository for path='/Users/jpshack/code/aider/scripts' failed. Error:spawn opt/homebrew/bin/git ENOENT {
  "gitErrorCode": "NotAGitRepository"
}Error: spawn opt/homebrew/bin/git ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:286:19)
	at onErrorNT (node:internal/child_process:484:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-10-23 09:45:15.512 [trace] [Model][openRepository] Repository: /Users/jpshack/code/aider/tests
2024-10-23 09:45:15.512 [trace] [Model][openRepository] Opening repository for path='/Users/jpshack/code/aider/tests' failed. Error:spawn opt/homebrew/bin/git ENOENT {
  "gitErrorCode": "NotAGitRepository"
}Error: spawn opt/homebrew/bin/git ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:286:19)
	at onErrorNT (node:internal/child_process:484:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-10-23 09:45:15.512 [trace] [Model][openRepository] Repository: /Users/jpshack/code/aider/website
2024-10-23 09:45:15.513 [trace] [Model][openRepository] Opening repository for path='/Users/jpshack/code/aider/website' failed. Error:spawn opt/homebrew/bin/git ENOENT {
  "gitErrorCode": "NotAGitRepository"
}Error: spawn opt/homebrew/bin/git ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:286:19)
	at onErrorNT (node:internal/child_process:484:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-10-23 09:45:15.514 [info] [Model][doInitialScan] Initial repository scan completed - repositories (0), closed repositories (0), parent repositories (0), unsafe repositories (0)
2024-10-23 09:45:17.502 [trace] [Model][onDidChangeConfiguration] Workspace folders: [/Users/jpshack/code/aider]
2024-10-23 09:45:17.502 [trace] [Model][openRepository] Repository: /Users/jpshack/code/aider
2024-10-23 09:45:17.503 [trace] [Model][openRepository] Opening repository for path='/Users/jpshack/code/aider' failed. Error:spawn opt/homebrew/bin/git ENOENT {
  "gitErrorCode": "NotAGitRepository"
}Error: spawn opt/homebrew/bin/git ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:286:19)
	at onErrorNT (node:internal/child_process:484:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

The logs are noisy because of all of the sub-directories the extension is searching--but I can confirm that there is indeed a git repo:
drwxr-xr-x  33 jpshack  staff   1.0K Jul 13 10:42 .
drwxr-xr-x  88 jpshack  staff   2.8K Oct 21 15:33 ..
-rw-r--r--@  1 jpshack  staff   161K Jun  3 15:07 .aider.chat.history.md
-rw-r--r--@  1 jpshack  staff   5.2K Jun  3 15:07 .aider.input.history
drwxr-xr-x@  5 jpshack  staff   160B Jun  3 10:05 .aider.tags.cache.v3
-rw-r--r--   1 jpshack  staff    61B May 30 10:43 .dockerignore
-rw-r--r--   1 jpshack  staff    50B May 30 10:43 .flake8
drwxr-xr-x  15 jpshack  staff   480B Jul 13 10:39 .git
drwxr-xr-x   4 jpshack  staff   128B May 30 10:43 .github
-rw-r--r--   1 jpshack  staff   131B Jun 18 11:57 .gitignore
-rw-r--r--   1 jpshack  staff   385B Jun 18 12:39 .pre-commit-config.yaml
drwxr-xr-x@  6 jpshack  staff   192B May 31 10:41 .pytest_cache

@jpshack-at-palomar, is there any reason why you have set the git.path setting? That should not be necessary.

Thank to the clarifications.
I am using git installed using homebrew and here is the snippet from my log without having the git.path setting set:
2024-11-01 10:19:54.685 [info] [main] Log level: Info
2024-11-01 10:19:55.128 [info] [main] Validating found git in: "/opt/homebrew/bin/git"
2024-11-01 10:19:55.213 [info] [main] Using git "2.46.0" from "/opt/homebrew/bin/git"

So without specifying the git.path setting, git should be correctly discovered.
Could you clear the git.path setting on your machine and see if your log would match what I am seeing?

As mentioned in my previous comment, I do not have the setting set, use git that is installed through homebrew and VS Code detects the git path as /opt/homebrew/bin/git. I will steps through the code but from the initial looks I am not seeing any code path that would trim the path that is being returned by "which git".

@jpshack-at-palomar, could you please run printenv in the VS Code integrated terminal and share them (assuming that there is no sensitive information in your environment variables). I am wondering whether an incorrect environment variable might be the root cause here. Thanks!


added unit test and fixed logging

[Current coverage][cc-pull] is 46.28% (diff: 43.57%)

Merging [#99][cc-pull] into [master][cc-base-branch] will increase coverage by 0.26%

@@             master        #99   diff @@
==========================================
  Files            21         22     +1
  Lines          3029       3122    +93
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1394       1445    +51
- Misses         1635       1677    +42
  Partials          0          0

Powered by Codecov. Last update [2e6af83...7eea7d3][cc-compare]
[cc-base-branch]: https://codecov.io/gh/cloudviz/agentless-system-crawler/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/cloudviz/agentless-system-crawler/compare/2e6af83fcdf1b993066dc600b10968dafffd8792...7eea7d3619cde29f44f65e16588e20af4175ac9a?src=pr
[cc-pull]: https://codecov.io/gh/cloudviz/agentless-system-crawler/pull/99?src=pr

Can you rebase it to master please:
$ git checkout <your_branch>
$ git rebase -i master

Okay, just did.


dep: remove mkdirp dependency

What / Why

dep: mkdirp hasn't been updated in 4 years, and node's fs library
has had a recursive option for fs since v10.12 (oldest active LTS
version). Additionally mkdirp depends on a version of library minimist that has a minor vulnerability associated.

Refs:

https://nodejs.org/api/fs.html#fs_fs_mkdir_path_options_callback
https://npmjs.com/advisories/1179

Any status on this? @rharriso, can you fix the conflict and maybe the maintainers won't have an issue merging?

Freebased.


not using GPU on HPC environment

This may not be a bug with the tool itself.
When installing all the requirements and running the tool on the test folder with moondream, the GPU is not used.

Error message below.

torch detects one CUDA device
but query for first device specs crashes
that error affects bvqa execution

kXXXXXX@erc-hpc-comp190:/scratch/users/kXXXXXX/kdl-vqa$ python -c "import torch; print(torch.cuda.device_count())"
1

>>> torch.cuda.get_device_properties(0)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/scratch/users/kXXXXXX/kdl-vqa/venv/lib/python3.11/site-packages/torch/cuda/__init__.py", line 523, in get_device_properties
    _lazy_init()  # will define _get_device_properties
    ^^^^^^^^^^^^
  File "/scratch/users/kXXXXXX/kdl-vqa/venv/lib/python3.11/site-packages/torch/cuda/__init__.py", line 319, in _lazy_init
    torch._C._cuda_init()
RuntimeError: CUDA unknown error - this may be due to an incorrectly set up environment, e.g. changing env variable CUDA_VISIBLE_DEVICES after program start. Setting the available devices to be zero.

kXXXXXX@erc-hpc-comp190:/scratch/users/kXXXXXX/kdl-vqa$ python bvqa.py describe -r
  0%|                                                                      | 0/3 [00:00<?, ?it/s]/scratch/users/kXXXXXX/kdl-vqa/venv/lib/python3.11/site-packages/torch/cuda/__init__.py:129: UserWarning: CUDA initialization: CUDA unknown error - this may be due to an incorrectly set up environment, e.g. changing env variable CUDA_VISIBLE_DEVICES after program start. Setting the available devices to be zero. (Triggered internally at ../c10/cuda/CUDAFunctions.cpp:108.)
  return torch._C._cuda_getDeviceCount() > 0
WARNING: running model on CPU
PhiForCausalLM has generative capabilities, as `prepare_inputs_for_generation` is explicitly overwritten. However, it doesn't directly inherit from `GenerationMixin`. From 👉v4.50👈 onwards, `PreTrainedModel` will NOT inherit from `GenerationMixin`, and this model will lose the ability to call `generate` and other related functions.
  - If you're using `trust_remote_code=True`, you can get rid of this warning by loading the model with an auto class. See https://huggingface.co/docs/transformers/en/model_doc/auto#auto-classes
  - If you are the owner of the model architecture code, please modify your model class such that it inherits from `GenerationMixin` (after `PreTrainedModel`, otherwise you'll get an exception).
  - If you are not the owner of the model architecture class, please contact the model code owner to update it.
The attention mask is not set and cannot be inferred from input because pad token is same as eos token. As a consequence, you may observe unexpected behavior. Please pass your input's `attention_mask` to obtain reliable results.
The `seen_tokens` attribute is deprecated and will be removed in v4.41. Use the `cache_position` model input instead.
`get_max_cache()` is deprecated for all Cache classes. Use `get_max_cache_shape()` instead. Calling `get_max_cache()` will raise error from v4.48
100%|██████████████████████████████████████████████████████████████| 3/3 [02:33<00:00, 51.22s/it]

Most likely explanation is that compute node erc-hpc-comp190 has been reported as malfunctioning. That node is the one I get by default when requesting an A30. When I pass --exclude erc-hpc-comp190 to srun I get an alternative node with an A30 which works well with bvqa.
kXXXXXX@erc-hpc-comp196:/scratch/users/kXXXXXX/kdl-vqa$ python -c "import torch; print(torch.__version__); print(torch.cuda.is_available()); print([torch.cuda.get_device_properties(i) for i in range(torch.cuda.device_count())]);"
2.5.1+cu124
True
[_CudaDeviceProperties(name='NVIDIA A30', major=8, minor=0, total_memory=24062MB, multi_processor_count=56, uuid=e9514850-72a7-4c6e-a991-92a457f37aff, L2_cache_size=24MB)]


Add getboardstate function

Add getboardstate function.
However, this function is displayed in only Japanese version document...
https://lightning.bitflyer.jp/docs?lang=ja#板の状態

LTGM! Thank you!


Make cloudpickle the default pickle library

Make cloudpickle the default pickle library.

See change https://github.com/apache/beam/pull/15472 and docs https://s.apache.org/beam-picklers.

Imported from Jira BEAM-13386. Original Jira may contain additional context.
Reported by: Ryan.Thompson.

Blocking issue: https://github.com/apache/beam/issues/26209
We should also investigate whether unpickling the same DoFn twice (e.g. in two different threads) would also result in unwanted shared state.
Until this is addressed, cloudpickle support should be considered experimental.

Blocking issue has been resolved.


qubo QAOA

…In anticommuting_op commented out old code. In noncontextual_op have added QAOA functionality and tests written.

Codecov Report

Merging #120 (673ce73) into main (1491474) will increase coverage by 1.56%.
The diff coverage is 95.49%.

@@            Coverage Diff             @@
##             main     #120      +/-   ##
==========================================
+ Coverage   70.57%   72.13%   +1.56%
==========================================
  Files          30       30
  Lines        3106     3180      +74
==========================================
+ Hits         2192     2294     +102
+ Misses        914      886      -28

Impacted Files
Coverage Δ

symmer/evolution/decomposition.py
8.60% <0.00%> (-0.19%)
:arrow_down:

symmer/operators/anticommuting_op.py
91.17% <ø> (+18.65%)
:arrow_up:

tests/test_projection/test_utils.py
85.71% <66.66%> (ø)

symmer/operators/noncontextual_op.py
78.24% <100.00%> (+4.39%)
:arrow_up:

symmer/projection/utils.py
56.38% <100.00%> (+0.94%)
:arrow_up:

tests/test_operators/test_noncontextual_op.py
100.00% <100.00%> (ø)

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


APISIX load wasm plugin report error in macosx platform?

Can you reproduce it in Linux (I don't have Mac to test it)?


Buffer map and unmap seems no longer necessary on MacOS

I found that some samples such as texture_loading is not working on MacOS with latest Vulkan SDK (<IP_ADDRESS>). After inspecting on this problem, I finally found that map and unmap in vkb::core::Buffer makes a problem that the host data is not properly transferred to device memory.
I also found that just by commenting out the following line fixes the problem:
https://github.com/KhronosGroup/Vulkan-Samples/blob/d2d68ca7005fd79a908af57527aadf82abf571c9/framework/core/buffer.cpp#L33
My environment is:

iMac (Retina 5K, 27-inch, 2017)
MacOS 10.15.6 Catalina
LunarG Vulkan SDK <IP_ADDRESS>
Radeon Pro 570 4GB

After reading the comment beside the above line, I wondered if the problem of map and unmap in MoltenVK has already been resolved, and if so, vkb::core::Buffer should be updated such that we can choose keep or disable VMA_ALLOCATION_CREATE_MAPPED_BIT.
If the above fix is valid, I am happy to make a PR for that.

@billhollings - Can you advise on this issue as well?

Starting in 10.15.6 (I think), Metal supports creating linear textures in Shared storage. So unmapping isn't necessary starting on 10.15.6. Unfortunately, for 10.15.5 and below, it's still necessary.

@cdavis5e Thank you for your advice. As far as I see the source codes, maybe, there are no option to disable map and unmap in vkb::core::Buffer with MacOS.
As in the following CMake script, VK_USE_PLATFORM_MACOS_MVK is always defined for MacOS. I think it helpful to add a new option to disable map and unmap.
https://github.com/KhronosGroup/Vulkan-Samples/blob/4eaa13632c426586cfeeb32caf4e450c09d8c345/third_party/CMakeLists.txt#L57
What do you think?

@tatsy

What do you think?

What does it mean within the sample code to add a build option to "disable map and unmap"? On the surface, that sounds like a drastic action.
If you do so, are there alternate paths that will automatically be taken in the sample code, such as staging buffers, etc? But since you reference disabling this in vkb::core::Buffer, it sounds like that might impact staging buffers too.
And would the changes apply to all samples, or just select ones that need coherent linear texture memory?

@billhollings I thought that it was almost enough to add a new CMake option such as VK_USE_PLATFORM_MACOS_NEWER_OSX_15_6 or something like that.
If we do not need to see the minor version of OSX, it can also be detected from CMAKE_OSX_DEPLOYMENT_TARGET. However, I am not really sure that only disabling map and unmap in vkb::core::Buffer works fine for all the samples.

I thought that it was almost enough to add a new CMake option such as VK_USE_PLATFORM_MACOS_NEWER_OSX_15_6 or something like that.

That's possible. But this is a run-time issue. What matters is the run-time environment, not the build environment. So you might build for 10.15.6 and above, but it wouldn't run properly if you actually ran it on earlier OS versions.
I'm also somewhat confused about what the problem is on newer macOS versions. Does the sample not work correctly when avoiding using map and unmap on 10.15.6 and above? If so, do you have more information about what the resulting problem is? If there is a problem not using map and unmap, and it's coming from MoltenVK, then we should fix it.

Ideally, once built, we'd want the sample to run correctly across both old and new OSes.  This implies either a runtime check in the sample, or some kind of fix in MoltenVK (such that the map/unmap required for old OSes doesn't corrupt behavior on new OSes).   Are either of these options a possibility here, or do we need to drop back and include instructions/mechanisms in the sample/framework to disable map/unmap at build time for newer OSes (not preferred)?  Any insights?

Vulkan Portability doesn't define any VK_USE_PLATFORM_MACOS_NEWER_OSX_15_6, and vulkan samples should target it (as opposed to MoltenVK specifically).
If this is an issue with Vulkan Portability, let's file an issue there and discuss - https://github.com/KhronosGroup/Vulkan-Portability
Otherwise, this is an issue with MoltenVK and should be moved there - https://github.com/KhronosGroup/MoltenVK

@marty-johnson59 I tend to agree with @kvark, this is an issue better addressed in either Portability or MoltenVK.  For my two cents, I'd recommend that MoltenVK take a pass at making this a little bit more seamless.

OK, I opened a new issue in MoltenVK (MoltenVK#1327).  Closing this one.  Please refer to that bug moving forward.  Thanks


Call out terraform 0.12 in README

A few of us are still on 0.11. Trying to terraform init, I get:
There are some problems with the configuration, described below.

The Terraform configuration must be valid before initialization so that
Terraform can determine which modules and providers need to be installed.

Initializing provider plugins...

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.```

@adamdavis40208 Thanks for pointing this out. I'll update the README to address this.


Add support for escaped parentheses in

For our latest project we need to escape parenthesis since they occur in the URLs (which is uncommon but valid). This PR is based on this old one (https://github.com/ReactTraining/react-router/pull/2533 by @Zoxive) which has been closed since at some point in time you wanted to refactor the URL matching into a separate module - unfortunately that has not happened yet so it would be very nice if the PR would make it this time.

As far as I can see Router v4 can handle escaped parenthesis by delegating the matching mechanism to this module: https://github.com/pillarjs/path-to-regexp
Is it something desirable for v3 as well? I could work on a PR that uses that module instead of having  a custom implementation? Are there any barriers that I don't see right now?

I believe that using path-to-regexp in v3 may actually break some existing apps that use our custom path syntax. I'm not opposed to merging this into v3. Looks like you've got some decent tests around it too.

Ok didn't know that path-to-regexpwould break stuff. Would be lovely if the PR could make it in the next release. If you need anything - I'm glad to help.

Changing something like that would require a major version bump. And the next major is already reserved 😉

Why would the change require a major version bump? Did I change a public API that behaves different now?

No no, I mean if we switched out matchPattern for path-to-regexp in 3.0.

I think we can merge this and ship a patch release of 3.0 with it

Yeah, it LGTM too.

I'll package this up as 3.0.1 soon. There's some other outstanding bug fixes to push out too.

Uhh thanks a lot <3


DependencyVulnerabilityCheck does not bump major.minor version schemes

What's changed?
Tests to replicate issue with DependencyVulnerabilityCheck as reported via Slack:
https://rewriteoss.slack.com/archives/C01A843MWG5/p1685635464607779?thread_ts=1685556511.929269&cid=C01A843MWG5
The snakeyaml test now fails due to this LatestPatch restriction in the recipe:
https://github.com/openrewrite/rewrite-java-dependencies/blob/5034484c423ab2ebc0194489dad9a320128234fc/src/main/java/org/openrewrite/java/dependencies/DependencyVulnerabilityCheck.java#L349-L352
What's your motivation?
Looking at this sampling of Spring Boot managed dependencies:
https://docs.spring.io/spring-boot/docs/current/reference/html/dependency-versions.html
We now fail to support bumps to these dependencies:
com.graphql-java:graphql-java:20.2
com.samskivert:jmustache:1.15
commons-codec:commons-codec:1.15
commons-pool:commons-pool:1.6
javax.money:money-api:1.1
org.hamcrest:hamcrest:2.2
org.hamcrest:hamcrest-core:2.2
org.hamcrest:hamcrest-library:2.2
org.influxdb:influxdb-java:2.23
org.webjars:webjars-locator-core:0.52
org.yaml:snakeyaml:1.33

Which while granted isn't a huge list, it still contains Snakeyaml, which recently had some public vulnerabilities.
Have you considered any alternatives or workarounds?
We could either have the recipe support broader updates (with risks tied to that as well),
or document the fact that the recipe has this major.minor.patch restriction clearly.
Checklist

[x] I've added unit tests to cover both positive and negative cases
[x] I've added the license header to any new files through ./gradlew licenseFormat
[x] I've used the IntelliJ auto-formatter on affected files
[ ] I've updated the documentation (if applicable)

I think we need to add some very clear documentation both to the recipe and docs, that DependencyVulnerabilityCheck will ONLY modify the patch part of the version, if it exists.
For the example from slack, it's using Spring Boot and Snakeyaml. What I would have normally done is upgrade Spring Boot which would have provided a new Snakeyaml version (latest in Gradle vs closest in Maven). The input being provided to Snakeyaml is most often user authored YAML which is safe for consumption and honestly reduces the risk of the vulnerability to low. If the application were accepting YAML from some remote source, then that's a different situation.
I feel like all in all, bumping the "last" version available as part of the semver semantics will likely carry more risk, than doing nothing for this specific case.


What's the proper syntax when working with FileStream?

Description of bug and reproducing it
Hey guys, I've got the method below that I am trying to abstract out for testing. File and Directory additions are working fine, but when working with the filestream on using (FileStream fs = fileSystem.File.Create(classPath.FullClassPath)), I am getting an Cannot implicitly convert type 'System.IO.Stream' to 'System.IO.FileStream'. An explicit conversion exists (are you missing a cast?) error. I'm assuming I should use something else for the FileStream type, but I'm not seeing it in the docs, issues, etc.
        public static void CreateEntity(string solutionDirectory, Entity entity, IFileSystem fileSystem)
        {
            try
            {
                var classPath = ClassPathHelper.EntityClassPath(solutionDirectory, $"{entity.Name}.cs");

                if (!fileSystem.Directory.Exists(classPath.ClassDirectory))
                    fileSystem.Directory.CreateDirectory(classPath.ClassDirectory);

                if (fileSystem.File.Exists(classPath.FullClassPath))
                    throw new FileAlreadyExistsException(classPath.FullClassPath);

                using (FileStream fs = fileSystem.File.Create(classPath.FullClassPath))
                {
                    var data = GetEntityFileText(classPath.ClassNamespace, entity);
                    fs.Write(Encoding.UTF8.GetBytes(data));
                }

                GlobalSingleton.AddCreatedFile(classPath.FullClassPath.Replace($"{solutionDirectory}{Path.DirectorySeparatorChar}", ""));
            }
            catch (FileAlreadyExistsException e)
            {
                WriteError(e.Message);
                throw;
            }
            catch (Exception e)
            {
                WriteError($"An unhandled exception occurred when running the API command.\nThe error details are: \n{e.Message}");
                throw;
            }
        }

Expected behavior
I'd expect to be able to do something along the lines of fileSystem.FileStream like I've done with File or Directory, but no luck. Assuming there's just a simple syntax difference I'm missing.

🤦♂ Literally just thought of the solution after I posted it. Sorry guys.
For others that run into this, I just updated it to var and it was completely fine:
                using (var fs = fileSystem.File.Create(classPath.FullClassPath))
                {
                    var data = GetEntityFileText(classPath.ClassNamespace, entity);
                    fs.Write(Encoding.UTF8.GetBytes(data));
                }

I was curious on what was going on. Just for reference, here are my findings:
System.IO.File.Create returns a FileStream, whereas using System.IO.Abstractons IFileSystem.File.Create returns a Stream to allow easier mocking.


Add --cnpm for chinese projects.

Coverage remained the same at 47.857% when pulling e7c697b9333f3bfa878daac5c077bf91c6175e81 on wxs77577:patch-2 into d7cf77f5c2e4abc1afe49135926ba6eaf5ea7a89 on adonisjs:develop.

@thetutlage  will you merge this PR?


[Bug] Snap doesn't work on object with only child colliders

When you have a snappable object that has the VRTK_InteractableObject script but no Collider and it contains several child objects that do have Colliders then you can't do a ForceSnap() on it.
This is basically because in several parts of the code it's assumed that for a call to ForceSnap(objectToSnap) the following holds true:
objectToSnap.GetComponentInChildren<Collider>().gameObject == objectToSnap

Which obviously is false in this case.
Relevant code is (in VRTK_SnapDropZone):
    private void AttemptForceSnap(GameObject objectToSnap)
    {
        //force snap settings on
        willSnap = true;
        currentValidSnapObject = objectToSnap;
        //Force touch one of the object's colliders on this trigger collider
        OnTriggerStay(objectToSnap.GetComponentInChildren<Collider>());
    }

and:
    private void OnTriggerStay(Collider collider)
    {
        [snip]
        //if the current colliding object is the valid snappable object then we can snap
        if (currentValidSnapObject == collider.gameObject)

But these aren't the only places.

Would be helpful to list all the places it is affected if you know where they are.

Well I tried fixing it in OnTriggerStay() and then it failed in the next method SnapObject() so it probably just goes down the chain :)
I can look at it some more, maybe even come up with a patch, but tonight perhaps, no time now.

I think this has been resolved

I get the same thing with the last version of VRTK.
The problem doesn't seem to be fixed for me.

@KospY can you provide steps to reproduce in an example scene? if so, I can re-open the issue.


Error of task filtering duplicate feature list rows of Aligned feature list peak: Java heap space

Basic information

My operating system: Windows
My mzmine version: tried both 4.1 and 4.2

What happened

I am getting this error while running this batch mode 6 times before on different samples, and it worked fine. Is that considered an issue with memory ?

batch mode file is attached
batch_01_with_noise_filter.zip

here are the screenshots for the error:

I set the preferences to another folder rather than the default one"C:\Users\mtawfik\AppData\Local\Temp"

Did you check how many samples and features you got per sample? Aligning tens of thausands of features across hundreds of samples may fail. Make sure to filter out noise.
Did you adjust your parameters for the new dataset or is it all the same instrument and same parameters?
Check out the performance options: https://mzmine.github.io/mzmine_documentation/performance.html

i have many samples and also more features per sample as the machine is producing more MS2. This project wsa 644 samples. Noise was set already as in the bactch file that was created. Processing Wizard was used intitially for that version 4.2 where the batch was created.
2.it is same instrunment/parameters (details is already in the batch file)
thanks, so mzmine3 performance should be similar to mzmine 4, COOL.


[BUG] BlobClient Uri now returns url encoding paths

Hi, in the old version of Azure.Storage.Blobs (12.4.4 and down), the BlobClient.Uri returns a uri without the path encoded, but the new versions (12.5.1 and up), returns uri with path as encoded characters.
Example: below is the old versions 12.4.4

And below here is new version 12.5.1

I can download the "foo.txt" file whether i download it from "/devstoreaccount1/scratch/hello/foo.txt" or "/devstoreaccount1/scratch/hello%2Ffoo.txt"
But the problem right now is the name of the file will be different.
I'm using a third-party service, that will for example download a file from my blobstorage, and save the file in their own system as "foo.txt", but if i use the new version, the third-party service will name the file "hello2Ffoo.txt" which is not what i wanted.
This means the fix to my problem is that i either have to manually replace all "%2F" to "/" or use the old 12.4.4 version.
In my example, i'm using Storage with localhost emulator, but the same thing happens if i used Storage on Azure.
I dont see anywhere in the release notes that made this change.
https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/storage/Azure.Storage.Blobs/CHANGELOG.md
So was this intended or is it a bug?

Thank you for your feedback.  Tagging and routing to the team best able to assist.

This is by design, we got a lot of complaints about the previous behavior.  The storage service considers encoded and unencoded paths to be the same.

@seanmcc-msft Okay, so this case is closed now, right?


Page the list of snippets

Allow to page the list of snippets at the exploration page level

The scroll ifinie has been added


Fix firehose filters

https://github.com/streamingfast/sf-ethereum/blob/develop/proto/sf/ethereum/transform/v1/transforms.proto

https://github.com/graphprotocol/graph-node/issues/3606 needs a review and needs some extra testing


How are CFG.visit_Break and CFG.visit_Continue get called?

Hello Tangent Authors,
I got a question as the title of this issue.
I see that class CFG is a subclass of gast.NodeVisitor and it has some visit methods.  The only place I noticed that would get these visit methods called is in the CFG.visit_statements method:
https://github.com/google/tangent/blob/3318ecab3eec71ef97702df66a59d1a2197c8de3/tangent/cfg.py#L112-L113
where gast.NodeVisitor.visit is called only if the current statement under interest is a control-flow, which includes the following kinds of statements:
https://github.com/google/tangent/blob/3318ecab3eec71ef97702df66a59d1a2197c8de3/tangent/grammar.py#L20
My question is that the above tuple doesn't include Break or Continue, whereas the class CFG has visit_Break and visit_Continue:
https://github.com/google/tangent/blob/3318ecab3eec71ef97702df66a59d1a2197c8de3/tangent/cfg.py#L159
https://github.com/google/tangent/blob/3318ecab3eec71ef97702df66a59d1a2197c8de3/tangent/cfg.py#L162
Are these two visit methods get called from somewhere else I didn't notice?
Thank you!

Sorry for bothering. I just realized that the invocation to visit inside visit_statements would check inside the loop and conditional structures.


Let BeatError extend from Exception

BeatError was not extending Exception. When raising BeatError it would throw TypeError: exceptions must derive from BaseException. This should not happen anymore.

Merged. Thanks!

No problem, mate!
But a question: WIll you update the python index (pip) also?


Add extended

Adds collectExtended, akin to collectSource and collectSimple, but for ExtendedPoints

It seems suboptimal that the user has to keep track for themselves of setting/clearing the LSB in addresses to distinguish extended points; it's just asking for people to screw up. I'm not sure whether this should be solved here though, might be more appropriate in Marquise.Client itself.

See https://github.com/anchor/marquise/issues/61 for discussion of the LSB issue in Marquise.


Azure config param throws error.

Hi, thank you for this nice tool.
I was using Azure TTS and set some custom config but getting error from the lib packages. I was curious how to tackle with this issue?
my current code snippet:
from livekit.plugins.azure.tts import ProsodyConfig

config = ProsodyConfig(rate="fast") # this is the config file we can set for Azure

async def entrypoint(ctx: JobContext):
    initial_ctx = llm.ChatContext().append(
        role="system",
        text=prompt,
    )

    await ctx.connect(auto_subscribe=AutoSubscribe.AUDIO_ONLY)

    # Wait for the first participant to connect
    participant = await ctx.wait_for_participant()

    assistant = VoicePipelineAgent(
        vad=ctx.proc.userdata["vad"],
        stt=deepgram.STT(language="ko"),
        llm=openai.LLM(model="gpt-4o-mini"),
        tts=azure.TTS(
            voice="ko-KR-JiMinNeural",
            language="ko-KR",
            prosody=config
        ),
        chat_ctx=initial_ctx,
    )

++++++++++++++++++++ below is Azure TTS class and we can pass the config here:+++++++++++++
class TTS(tts.TTS):
    def __init__(
        self,
        *,
        speech_key: str | None = None,
        speech_region: str | None = None,
        voice: str | None = None,
        endpoint_id: str | None = None,
        language: str | None = None,
        prosody: ProsodyConfig | None = None,
    ) -> None:

+++++++++++++++++ when I do so there is a ValueError ++++++++++++++++++++
raise ValueError(
ValueError: failed to synthesize audio: ResultReason.Canceled: CancellationReason.Error (Connection was closed by the remote host. Error code: 1007. Error details: Ssml should contain at least one [VOICE] tag. USP state: TurnStarted. Received audio size: 0 bytes.)

would appreciate any help for this.

This is a problem because there is no voice tag in ssml of azure tts.
livekit-plugins/livekit-plugins-azure/livekit/plugins/azure/tts.py
This is resolved by changing the "_synthsize" function of 180 lines.
def _synthesize() -> speechsdk.SpeechSynthesisResult:
    if self._opts.prosody:
        ssml = f'<speak version="1.0" xmlns="http://www.w3.org/2001/10/synthesis" xml:lang="{self._opts.language or "en-US"}">'
        voice_ssml = f'<voice name="{self._opts.voice}">'
        prosody_ssml = "<prosody"

        if self._opts.prosody.rate:
            prosody_ssml += f' rate="{self._opts.prosody.rate}"'
        if self._opts.prosody.volume:
            prosody_ssml += f' volume="{self._opts.prosody.volume}"'
        if self._opts.prosody.pitch:
            prosody_ssml += f' pitch="{self._opts.prosody.pitch}"'
        prosody_ssml += ">"
        ssml += voice_ssml
        ssml += prosody_ssml
        ssml += self._text
        ssml += "</prosody></voice></speak>"
        return synthesizer.speak_ssml_async(ssml).get()  # type: ignore

    return synthesizer.speak_text_async(self._text).get()  # type: ignore

Hey, seems like this was fixed inside the PR https://github.com/livekit/agents/pull/929

Unfortunately, it did not solve the problem. I still cannot pass config file.
what might be I am doing wrong in here?
thank you

https://github.com/livekit/agents/pull/929
Now that the change has been merged, why don't you get the project source code again and run it?

thank you @harmlessman


Fix default Python config.

The Python linter we're using (Flake8) expects a non-JSON configuration format, and passing {} to it causes an exception.
Since constants in Ruby aren't inherited in the same way as methods, we need to move the default to a method in order to override it.

LGTM! :package:

Thanks!

It might be worth also making a similar change in https://github.com/thoughtbot/hound/blob/master/app/models/config/go.rb


feat: ipv6 declarative

What does this fix or implement?

Checklist

[ ] PR name added as appropriate (e.g. feat/fix/doc/test/refactor/etc)
[ ] Tests added or updated
[ ] Documentation updated
[ ] Changelog updated and version incremented (label: upcoming release)
[ ] Github Issue linked if any

Hi, quick question:
Is there a ETA on this?
There has no activity since a month

Hi, quick question:
Is there a ETA on this? There has no activity since a month

Hello,
We should be making a beta release today which will include this as well as the other declarative changes


Google Search Console cannot read sitemap

Hi,
I have a https://aiuanyu.vercel.app/sitemap.xml generated (Base URL set),
but Google Search Console reports that it cannot read the sitemap.

Trying to make sure if this is an issue with Google or Digital Garden...
Is there anyone encountering this?

I assume it's Google. I never had an sitemap issue with my digital garden and our sitemaps look similar.
https://derwissensarbeiter.de/sitemap.xml


General question on how to use the Code Introspection

Hi, I'm loving Hydrogen! It's replacing my work on Ipython Notebook.
But I am having trouble to use Code Introspection. It looks like a great feature coming from NB. But how exactly can I use it?
Following the instruction,

You can use the "Hydrogen: Inspect" command from the Command Palette to get metadata from the kernel about the object under the cursor.

, I clicked on "Hydrogen: Inspect" but the below message pop up and the metadata wasn't shown.

I was trying to get the metadata of numpy.linspace.
Thanks!

Thanks for your feedback!
The completion result depends on the cursor position. Place the cursor somewhere inside the word linspace or highlight it and it should work.
Also make sure to run the import numpy before requesting the completion.

Ah, this was a silly question.. Yes positioning the cursor inside the word worked! But highlighting it didn't work(?)

Also this wouldn't be possible on Atom but if I can type tab+shift just like NB and metadata pops up, it'd be super useful :)

Ah sorry you have to highlight numpy.linspace to make it work. Or import linspace with from numpy import linspace or from numpy import *.

tab+shift is currently used by Atom itself for indentation.
But you can define a custom keyboard shortcuts for this function for yourself by adding
'atom-text-editor':
  'cmd-ctrl-i': 'hydrogen:inspect',

to your Atom keymaps file.


Adding community resources

Adding three articles from my site, not sure I used the right key. Thank you!

Thanks @superterrific!
I think the keys look right to me, per a quick grep of existing key values:
git grep -Eho "key:\s?\"(.*?)\"" src/_data | sort | uniq

key: "api-services-avatar"
key: "api-services-opengraph"
key: "api-services-screenshot"
key: "api-services-sparkline"
key: "collections"
key: "data"
key: "data-cascade"
key: "getting-started"
key: "image"
key: "javascript"
key: "plugins"
key: "quicktips"
key: "serverless"
key: "tutorial-blog"
key: "tutorial-intro"
key: "tutorial-simplewebsite"


option to send email as html

Can you add an option to send emails as HTML when using the email provider? According to Strapi docs, you just need to set a "html" property instead of "text":
        await strapi.plugins['email'].services.email.send({
          to: recipient.email,
          from: config.from,
          subject: config.subject ? config.subject : 'New Contact Form Submission',
          html: message,
        })

It would be cool if this choice could be set up in some config file. Overriding the send() function for a small thing like this seems like an overkill.

Wouldn't be too hard to add, would probably add a config option something like allowUnsafeHtmlAsMessage since there is a concern of malicious actors using their own HTML to make stuff like phishing emails. Not sure when I could get to this but if you make a PR I'd be happy to merge.

made a rough draft, gonna test it later but feel free to try it
https://github.com/excl-networks/strapi-plugin-ezforms/pull/41