Boolean model should accept some values as true

Description
The default string to boolean conversion is not suitable, since all strings (including "false") are converted to true. This patch follows the convention used by validator.js to avoid inconsistencies.
Fixes #177
Type of change

[x] Bugfix
[ ] Feature

Checklist

[x] I have read the contribution guide: https://vaadin.com/docs/latest/guide/contributing/overview/
[x] I have added a description following the guideline.
[x] The issue is created in the corresponding repository and I have referenced it.
[x] I have added tests to ensure my change is effective and works as intended.
[x] New and existing tests are passing locally with my change.
[x] I have performed self-review and corrected misspellings.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Clustering failed && Does porec_paired.bam can using in Yahs

Hi,
Thanks for developing such wonderful tools.
I am working on birds with many, many micro-chromosomes.
I have some questions. I am looking forward to hearing from you.
For the input contig assembly from NextDenovo, I tried both HiC.bam and HiC.filtered.bam.

One-step pipeline reported that "some chromosomes were grouped together, or the maximum number of clusters(1) is even less than the expected number of chromosomes(31). Then I increased --max_inflation to 30 with step 0.3 running step-by-step, but I still failed in the Clustering. Should I further increase --max_inflation?
I used the quick-view model and found many small contigs with no HiC contact signal. Then, I sorted HiC.bam by name and input in Yahs; these small contigs showed increased HiC contact signals. Does this mean Yahs may be more suitable for birds?
I also note that Yahs changed the contig name Ctg000001 to Ctg000001.1, dose Ctg000001.1 is the same as Ctg000001 when I set "--no-contig-ec --no-scaffold-ec"?
The last question is can I use porec_paired.bam converted by Haphic prepare python script to Yahs, If Yahs more suitable for birds?

Best wishes!
Haoran

One-step pipeline reported that "some chromosomes were grouped together, or the maximum number of clusters(1) is even less than the expected number of chromosomes(31). Then I increased --max_inflation to 30 with step 0.3 running step-by-step, but I still failed in the Clustering. Should I further increase --max_inflation?
I used the quick-view model and found many small contigs with no HiC contact signal. Then, I sorted HiC.bam by name and input in Yahs; these small contigs showed increased HiC contact signals. Does this mean Yahs may be more suitable for birds?

Without contact maps and enough information, I cannot comment on the issues you’ve encountered or your observations. In addition, Hi-C contact signals are fully represented in the BAM file. Unless different filtering criteria are applied to the two tools, it is impossible to claim that “these small contigs showed increased Hi-C contact signals.” Furthermore, the BAM file requirements for HapHiC are consistent with those for YaHS. Therefore, if you generate the BAM file as I recommend, there is no need to sort it by name again.

I also note that Yahs changed the contig name Ctg000001 to Ctg000001.1, dose Ctg000001.1 is the same as Ctg000001 when I set "--no-contig-ec --no-scaffold-ec"?

The correspondence of contig ID is saved in *.liftover.agp.

The last question is can I use porec_paired.bam converted by Haphic prepare python script to Yahs, If Yahs more suitable for birds?

Yes. porec_paired.bam meets the format requirements of YaHS for the input file.

One-step pipeline reported that "some chromosomes were grouped together, or the maximum number of clusters(1) is even less than the expected number of chromosomes(31). Then I increased --max_inflation to 30 with step 0.3 running step-by-step, but I still failed in the Clustering. Should I further increase --max_inflation?
I used the quick-view model and found many small contigs with no HiC contact signal. Then, I sorted HiC.bam by name and input in Yahs; these small contigs showed increased HiC contact signals. Does this mean Yahs may be more suitable for birds?

Without contact maps and enough information, I cannot comment on the issues you’ve encountered or your observations. In addition, Hi-C contact signals are fully represented in the BAM file. Unless different filtering criteria are applied to the two tools, it is impossible to claim that “these small contigs showed increased Hi-C contact signals.” Furthermore, the BAM file requirements for HapHiC are consistent with those for YaHS. Therefore, if you generate the BAM file as I recommend, there is no need to sort it by name again.

I also note that Yahs changed the contig name Ctg000001 to Ctg000001.1, dose Ctg000001.1 is the same as Ctg000001 when I set "--no-contig-ec --no-scaffold-ec"?

The correspondence of contig ID is saved in *.liftover.agp.

The last question is can I use porec_paired.bam converted by Haphic prepare python script to Yahs, If Yahs more suitable for birds?

Yes. porec_paired.bam meets the format requirements of YaHS for the input file.

Many thanks for your reply!
The karyotype of the species is 2n=60+ZZ.
The commands and parameters used in running HapHiC is: "/media/perimeter/r2/srcs/HapHiC/haphic cluster /media/perimeter/r2/eeu/eeuontasm/03.ctg_graph/nd.asm.w60.fasta /media/perimeter/r2/eeu/eeuontasm/03.ctg_graph/HiC.filtered.bam 31 --max_inflation 30 --inflation_step 0.3
The log files generated by HapHiC
HapHiC_cluster.log
The methods (commands) used for Hi-C read mapping and filtering: as Hap HIC recommended.
The method used for genome assembly ONT ultra long reads to Nextdenovo without polish.
Statistics for the assembly input into HapHiC
Type           Length (bp)            Count (#)
N10            220407187                   1
N20            168975251                   2
N30            168975251                   2
N40            127899466                   3
N50             84066100                   5
N60             70663523                   6
N70             48140589                   9
N80             24783511                  12
N90             18726849                  18
Min.               72153                   -
Max.           220407187                   -
Ave.            18954379                   -
Total<PHONE_NUMBER>                  65
Best wishes!
Haoran

Although I still have not seen your contact maps, it doesn't matter. If you have carefully read our paper or listened to our presentation on bilibili, you should know that HapHiC and YaHS are two different types of scaffolders. HapHiC usually requires knowledge of the number of chromosomes and prefers a distribution of chromosome lengths, while YaHS does not. These trade-offs often result in HapHiC being more likely to achieve chromosome-level scaffolding results with a higher anchoring rate, while YaHS may have more difficulty with these. However, YaHS tends to be more stable when the number of chromosomes is unknown, or when there are significant differences in chromosome lengths.
In your case, I noticed that your L90 is only 18, indicating that the setting of 31 includes microchromosomes. Due to microchromosomes being much shorter compared to other chromosomes, HapHiC usually does not recognize them as proper chromosomes, hence the clustering number never reaches 31. To address this issue, it would be better to set nchrs to the number after subtracting the microchromosomes. Identification and scaffolding of microchromosomes require manual adjustment. Alternatively, you can start manual adjustments directly using the results from the quick view.
Regarding your statement that YaHS exhibits stronger Hi-C contact signals on short contigs compared to HapHiC, it’s important to note that the Hi-C contact signals on contact maps are independent of these scaffolding tools. Instead, they depend solely on your alignment and filtering methods. This observation might be due to other errors in your process.
Overall, if you believe that YaHS produces better results, please feel free to continue using it. However, if you prefer to use HapHiC, I would recommend reducing the number of chromosomes (nchrs) to the number of main chromosomes or just using the quick view mode. Since your contig length is already long enough, different scaffolders will not show significant differences.

"This observation might be due to other errors in your process." Yes, I have checked the raw file. I used filtered bam to Haphic and unfiltered bam to Yash and gave an error statement. Sorry for my carelessness.
HapHiC is an excellent software that is easy to use and handles haplotype assembly. I would try to reduce the "nchrs" setting.
Many thanks again!


Bbasic UI

Hello Dear reviewer,
thanks for taking time to review my code, feedbacks are welcomed. Here is what i did as steps to complete this project:
Created the App class
Created a main.rb file for user interface
Happy review :-)

For the next reviewer, please i do not have enough trials left, if the test fails on your side, kindly contact me om slack or zoom to notice me before rejecting again. I am also hurried by the time please


How to test using a rest client ?

Hi, excuse me if  is a silly question but, how i can test login flow using a rest client ?
I'm trying to make a social registration flow, but i don't understand how to send the "code" parameter in the request payload.
Thanks.

Hi Jose,
you can send a POST request to /api/login/social/session/ with payload
{
    "provider": "facebook",
    "code": "AQBPBBTjbdnehj51"
}

To get the code from facebook manually, go to url (replace client_id and redirect_uri to your values):
https://www.facebook.com/dialog/oauth?client_id=295137440610143&redirect_uri=http://restsocialexample.com:8000/
Please look at facebook docs for details.
After confirmation you will be redirected back to redirect_uri, and code will be in GET params:
http://restsocialexample.com:8000/?code=AQBMRCdyj...
So you can use this code for testing (it will be valid only for one request).
Also, there is an example_project, you can check, how it works.

Hey thank you for answer. What about if i'm using Token authentication ?
Thank you.

Then use /api/login/social/token/ or /api/login/social/token_user/ url, they are described in readme.

Hey, I tried to follow the flow you described.
But when i try to make POST to the  /api/login/social/token/  url, i'm getting 400 [ BAD REQUEST ].
So, am i missing something, an HTTP Header or something like that ?
I'm using PostMan App.
Thank you.

It is hard to say, having just this information.
One suggestion is bad redirect_uri. It must be the same in both requests to OAuth provider: code request and access_token request. By default, django-rest-social-auth will use the domain it is working on as redirect_uri. And this redirect_uri must be the same, as you manually specified in code request.
Example:

manually go to https://www.facebook.com/dialog/oauth?client_id=295137440610143&redirect_uri=http://restsocialexample.com:8000/ (note redirect_uri here is http://restsocialexample.com:8000/)
run server on localhost:8000. As a result, server will use redirect_uri=http://localhost:8000, which is not the same, and you get 400 [BAD REQUEST].

Hey
I am having a similar problem in django 1.10.
If I go to https://www.facebook.com/dialog/oauth?client_id=<client id>&redirect_uri=http://localhost:8000/, it is working fine. But when I try to authenticate to Django using a token obtained by Javascript SDK, it shows Status 400 (Bad Request).
I am using Token Authentication and POSTing the following data on http://localhost:8000/api/login/social/token/:
provider=facebook&code=<code here>
I have even tried this:
{ "provider": "facebook", "code": "EAADJVzOZAdnkBAM5wdnIlThWVyv27ZBb3tW8mpCB0edDuRQGuCafVnvCwgjOT6Oiascah5BpTIeRFATQiAFFMZA1RgKv9oueUQR04fFdA3cVPhzUAgzIZBUsqXaXL0u2uARN7QWCZAotTkryxrPh5boi1c5wZB4dpZChzgig5CX8sAuqQSb2usZB3nnu8Lhb0c8ZD" }
The token is working fine if I try to access the graph API.

Just as an FYI, I was getting a 400 when using httpie on the redirect request like you.
The solution was to add the sessionid cookie into the request.

I'm having the redirect_uri issue, but I can't find why!
At my OAuth2 specification to get Facebook's code, the Redirect URL is: http://localhost:8000/api/login/social/token_user/
Than I get the code, when I try to reach the URL, I get the error. And the URL I'm trying to reach is the same http://localhost:8000/api/login/social/token_user/ with the body:
  "provider": "facebook",
  "code": "AQAI0u0Pg0XJ_oSL-Ye_Lcv7JcVg67nrkms6SK93OF-UXKB5SYYmCQ6jWzu6x8c8rChbKQ2WT9pNqe0dlBsCZE3Eu3m1rtEhJSXkoVnXzp4v2E3EUGAl7LR_rJSLZOPQZc-LU_F07UvSOdJUnWbAExP2vYdjHviRpz4ic5BGPcCgM2HmJZjZJrc2Ym5rWgzogb7Xdv1qDkgkqlkAdKldnz73rYfiMPa0_EMatgSdjGfYRXl3AX-FGVD0BhG8XE1KdH1vpiDWakYNc_IVZDOAeOx1PKFqDojwmPUqq-imphz0KEbEjUOFs2TvR7HabZYvHZZbfYSY1webi3S6q2KQjBvEWacwR-MnTk9xHF8hMhv8rQ"
}```

Can't understand why!


fix: to get exact height to avoid scrolling deviation

There will be a rolling deviation cause show is not complete when the item Element be setted marginTop or marginBottom.

Hello, why don't have any new message for it? I think the problem for calculating heights is need to be considered.

Hello, why don't have any new message for it? I think the problem for calculating heights is need to be considered.

hello，did any issues relate to this? Or could you provide a reproduction link？Thank you very much!

Hello, why don't have any new message for it? I think the problem for calculating heights is need to be considered.

Sorry， maybe you should set an issue at Ant-Design repository, this repository is safeguarded by Ant-Design, so they might not notice PR without issue related.


[Help] Dependency Track Parent Project selection

Hello,
I would like to export all the sboms of images (as individual project) from one cluster to a specific (existing) parent project. I'm pretty unclear how could I achieve this.
config- values.yaml:
args:
  targets: dtrack
  dtrack-base-url: <url>
  format: cyclonedxjson
  dtrack-parent-project-annotation-key: cluster-1

Expected project hierarchy in DTrack:
cluster-1
|------- image-1
|------- image-2
|....
cluster-2
cluster-3

But for each image, operator creating a project outside cluster-1 project.
Did I understand wrong?

Update:

I have created a pod as in example: https://github.com/ckotzbauer/sbom-operator?tab=readme-ov-file#example-pod-annotation and it couldn't fetch the parent project until unless the version (cluster-1:latest) specified as below

apiVersion: v1
kind: Pod
metadata:
  annotations:
    cluster-1/my-nginx: cluster-1:latest
spec:
  containers:
    - image: nginx:latest
      name: my-nginx

Is there any other way to map additional annotation  by default as we have one default ckotzbauer.sbom-operator.io/<IMAGE>?


Vulnerability: cve-2022-22965 - is CCDS validator impacted ?

https://tanzu.vmware.com/security/cve-2022-22965
does CCDA - validator has an impact ? If yes, is there any plan to update the dependencies?
**Am I Impacted?**
These are the requirements for the specific scenario from the report:

- JDK 9 or higher
- Apache Tomcat as the Servlet container.
- Packaged as a traditional WAR (in contrast to a Spring Boot executable jar).
- spring-webmvc or spring-webflux dependency.
- Spring Framework versions 5.3.0 to 5.3.17, 5.2.0 to 5.2.19, and older versions.

However, the nature of the vulnerability is more general, and there may be other ways to exploit it that have not been reported yet.

Affected VMware Products and Versions
Severity is critical unless otherwise noted.

Spring Framework
5.3.0 to 5.3.17
5.2.0 to 5.2.19
Older, unsupported versions are also affected
**Mitigation**
Users of affected versions should apply the following mitigation: 5.3.x users should upgrade to 5.3.18+, 5.2.x users should upgrade to 5.2.20+. No other steps are necessary. There are other mitigation steps for applications that cannot upgrade to the above versions. Those are described in the early announcement blog post, listed under the Resources section. Releases that have fixed this issue include:

Spring Framework
5.3.18+
5.2.20+

The deployed validator(s) are not impacted as they are built with Java 8.

thank you @Plow74


fix: update command to run hello world script

The -f flag seems to be no longer required.

Thanks! Closing this as merged in #152


Added a buffer tool

Following feedback from users, we have created a buffer tool so that a point can be drawn on the map with a buffer where the user can specify the size and measurement unit. The buffer tool is included with the annotation tools in the left sidebar.

Just like with other annotation tools, the fill/stroke colours, opacity etc can be chosen to style the buffer as you like.

Closes #209

Couple things:

The 'type' of the radius input field should be 'number' to prevent people typing in text
The inputs probably don't need to be full width. They may look a bit better if they were sized more appropriately to their content

This has been achieved using bootstraps grid system

You can experiment to find appropriate sizes across various screens.
When you edit the buffer, it shows you the option for changing the radius, but changing it does nothing. You can edit the actual geometry of the buffer like you would a polygon, as that is what the geometry is. There are a couple of options here:

Disable the form field when editing.
Update the buffer size if the user does (will likely involve deleting the original buffer and recreating it on the fly)

The 'tip' that appears when you hover over the map says 'Click to start drawing'. Ideally it would say something like 'Click to draw buffer'


Consider removing flag auto-generation?

So @asahasrabuddhe dramatically improved the flag generation in this PR https://github.com/urfave/cli/pull/836. I think that PR was a necessary first step in us rethinking the flag generation, so I super appreciate that work and love that it was done ✨
I think what we've been doing lately is expanding upon that idea behind that PR ^ and "normalizing" the flag code. So the next step in this process is: should we consider removing the flag generation entirely? I think we could keep the essence of flag generation, by adding tests that ensure the flags all have some attributes defined.
Some motivations behind removing auto-generation:

it many cases you don't end up writing any less code to implement a feature, so auto-generation isn't saving on LOC
auto-generation is high complexity, and hard to describe to contributors
given that we are in total control of the inputs and outputs, there's no particular forcing factor that requires this package have auto-generation

@AudriusButkevicius has mentioned supporting this in passing.

I didn't understand why the flags were generated in the first place. I support removing this and would like to contribute to this.

🚀🚀🚀 @asahasrabuddhe 🚀🚀🚀

on it

I have started to work on this but I am still getting an error in the test cases
=== RUN   TestToMan
--- FAIL: TestToMan (0.00s)
    helpers_test.go:20: (docs_test.go:68) Expected .TH "greet" "8" " "
        .nh
        .ad l
        .TH "Harrison"
        .nh
        .ad l

        .SH NAME
        .PP
        greet \- Some app

        .SH SYNOPSIS
        .PP
        greet

        .PP
        .RS

        .nf
        [\-\-another\-flag|\-b]
        [\-\-flag|\-\-fl|\-f]=[value]
        [\-\-socket|\-s]=[value]

        .fi
        .RE

        .SH DESCRIPTION
        .PP
        app [first\_arg] [second\_arg]

        .PP
        \fBUsage\fP:

        .PP
        .RS

        .nf
        greet [GLOBAL OPTIONS] command [COMMAND OPTIONS] [ARGUMENTS...]

        .fi
        .RE

        .SH GLOBAL OPTIONS
        .PP
        \fB\-\-another\-flag, \-b\fP: another usage text

        .PP
        \fB\-\-flag, \-\-fl, \-f\fP="":

        .PP
        \fB\-\-socket, \-s\fP="": some 'usage' text (default: value)

        .SH COMMANDS
        .SH config, c
        .PP
        another usage test

        .PP
        \fB\-\-another\-flag, \-b\fP: another usage text

        .PP
        \fB\-\-flag, \-\-fl, \-f\fP="":

        .SS sub\-config, s, ss
        .PP
        another usage test

        .PP
        \fB\-\-sub\-command\-flag, \-s\fP: some usage text

        .PP
        \fB\-\-sub\-flag, \-\-sub\-fl, \-s\fP="":

        .SH info, i, in
        .PP
        retrieve generic information

        .SH some\-command (type string) - Got .nh
        .TH greet(8)

        .SH Harrison

        .SH NAME
        .PP
        greet \- Some app

        .SH SYNOPSIS
        .PP
        greet

        .PP
        .RS

        .nf
        [\-\-another\-flag|\-b]
        [\-\-flag|\-\-fl|\-f]=[value]
        [\-\-socket|\-s]=[value]

        .fi
        .RE

        .SH DESCRIPTION
        .PP
        app [first\_arg] [second\_arg]

        .PP
        \fBUsage\fP:

        .PP
        .RS

        .nf
        greet [GLOBAL OPTIONS] command [COMMAND OPTIONS] [ARGUMENTS...]

        .fi
        .RE

        .SH GLOBAL OPTIONS
        .PP
        \fB\-\-another\-flag, \-b\fP: another usage text

        .PP
        \fB\-\-flag, \-\-fl, \-f\fP="":

        .PP
        \fB\-\-socket, \-s\fP="": some 'usage' text (default: value)

        .SH COMMANDS
        .SH config, c
        .PP
        another usage test

        .PP
        \fB\-\-another\-flag, \-b\fP: another usage text

        .PP
        \fB\-\-flag, \-\-fl, \-f\fP="":

        .SS sub\-config, s, ss
        .PP
        another usage test

        .PP
        \fB\-\-sub\-command\-flag, \-s\fP: some usage text

        .PP
        \fB\-\-sub\-flag, \-\-sub\-fl, \-s\fP="":

        .SH info, i, in
        .PP
        retrieve generic information

        .SH some\-command (type string)
FAIL

Process finished with exit code 1

@saschagrunert would really appreciate your help here

Hm, it might be related to the indirect blackfriday dependency of go-md2man. Can you try to remove $GOPATH/pkg/mod folder completely and re-test it again? Does it still occur?

The issue here was inconsistent use of Go Module system. I dropped in an environment variable GO111MODULE=on which made a lot of difference. Earlier it would run the tests using a different version of dependencies for different Go versions. Now that has been fixed.
I, however, have a new problem related to short flags now

This is done and released as a part of v1.22.2


Jetbrains Integration Codebase Context Bug with FTS Database

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 22.04 LTS
- Continue: 0.0.62
- IDE: Pycharm 2024.2
- Model: Claude 3.5 Sonnet
- config.json:

  {
  "systemMessage": "You are a senior software developer who specializes in Python 3.11 with pydantic v2. You adhere to SOLID and DRY principles. You specialize in unit testing and refactors. Your unit tests should always be done with pytest and prefer using classes for tests. You always use static typing. You focus on performance, maintainability, readability and security. You always use existing docstrings and write new ones in the sphinx format, if needed. You favor pep 8 python formatting and you write method parameters on new lines.",
  "contextProviders": [
    {
      "name": "code"
    },
    {
      "name": "search"
    },
    {
      "name": "codebase"
    },
    {
      "name": "folder"
    },
    {
      "name": "url"
    },
    { "name": "diff" }
  ],
  "models": [
    {
      "model": "claude-3-5-sonnet-20240620",
      "contextLength": 200000,
      "title": "Claude 3.5 Sonnet",
      "apiKey": "REDACTED",
      "provider": "anthropic"
    }
  ],
  "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. Prefer creating classes for the tests. Give the tests just as chat output, don't edit any file. Use pytest with classes.",
      "description": "Write unit tests for highlighted code"
    },
    {
      "name": "integration_test",
      "prompt": "{{{ input }}}\n\nWrite a comprehensive set of integration 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. Prefer creating classes for the tests. Give the tests just as chat output, don't edit any file. Use pytest with classes.",
      "description": "Write unit tests for highlighted code"
    },
    {
      "name": "doc",
      "prompt": "Write a docstring for the current code in sphinx format.  Do not add new code.",
      "description": "Write the docstring"
    },
    {
      "name": "review",
      "prompt": "Review this code and suggestion improvements if needed.",
      "description": "Review code"
    },
    {
      "name": "refactor",
      "prompt": "{{{ input }}}\n\nRefactor the selected code to improve its readability, maintainability, and performance.  Improving coupling, cohesion and efficiency.",
      "description": "Refactor the selected code"
    },
    {
      "name": "refactor_for_test",
      "prompt": "{{{ input }}}\n\nRefactor the selected code to improve its unit testability. SOLID principles should be followed and docstrings must be maintained. Prefer using Protocol instead of abstract classes for interfaces. If no refactor is needed, please write 'No refactor needed'.",
      "description": "Refactor the selected code"
    }
  ],
  "embeddingsProvider": {
    "provider": "ollama",
    "model": "nomic-embed-text"
  },
  "allowAnonymousTelemetry": true
}

Description
Whenever I try to use @codebase in a prompt, I get an error stating Error retrieving from FTS: Error: SQLITE_ERROR: no such table: fts. The notification in Pycharm shows Error getting context items from codebase: TypeError: db. search is not a function.
I have rebuilt the index and still have the same issue. Another user on Discord also reported this occurring in WebStorm. This leads me to think it's an issue with Jetbrains in general, not just PyCharm.
To reproduce
This assumes you have Pycharm installed with the Continue plugin enabled already.

Open the Continue panel
Make sure the project is indexed
Write any prompt and include @codebase in the prompt. I recommend a prompt that refers to a file that has dependencies on other files.
Submit the prompt
Observe the error. The prompt still runs, but the automatic context isn't found.

Log output
[2024-08-23T18:12:33] Error retrieving from FTS: Error: SQLITE_ERROR: no such table: fts
[2024-08-23T18:13:58] Error retrieving from FTS: Error: SQLITE_ERROR: no such table: fts

I can confirm that I get the same behavior (after updating to EAP version).

OS: MacOS 14.6.1
Continue: 0.0.63
IDE: Webstorm 2024.2 (Build #WS-242.20224.342)
Model: Claude 3.5 Sonnet

I tried to remove the index folder and force re-index, which seems to run successfully, but still getting Error retrieving from FTS: Error: SQLITE_ERROR: no such table: fts when trying to use @codebase

Me too.
OS: Ubuntu 22.04
Continue: 0.9.199
IDE: VSCode 1.92.2
Model: ollama based
Other: chat works, several context providers don't
console.ts:137 [Extension Host] Error retrieving from FTS: Error: SQLITE_ERROR: no such table: fts
--> in Database#all('SELECT fts_metadata.chunkId, fts_metadata.path, fts.content, rank\n' +
'    FROM fts\n' +
'    JOIN fts_metadata ON fts.rowid = fts_metadata.id\n' +
'    JOIN chunk_tags ON fts_metadata.chunkId = chunk_tags.chunkId\n' +
    WHERE fts MATCH '"What" OR "does" OR "this" OR "project" OR "do"' AND chunk_tags.tag IN (?)\n +
'      \n' +
'    ORDER BY rank\n' +
'    LIMIT ?', [ '/home/vscode/src::NONE::chunks', 13 ], [Function (anonymous)])
at new Promise ()
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
y	@	console.ts:137
$logExtensionHostMessage	@	mainThreadConsole.ts:39
S	@	rpcProtocol.ts:458
Q	@	rpcProtocol.ts:443
M	@	rpcProtocol.ts:373
L	@	rpcProtocol.ts:299
(anonymous)	@	rpcProtocol.ts:161
B	@	event.ts:1230
fire	@	event.ts:1261
fire	@	ipc.net.ts:652
K.onmessage	@	localProcessExtensionHost.ts:378
VSCode info:
Version: 1.92.2
Commit: fee1edb8d6d72a0ddff41e5f71a671c23ed924b9
Date: 2024-08-14T17:29:30.058Z
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.8.0-40-generic

IntelliJ IDEA: IntelliJ IDEA 2<IP_ADDRESS> (Ultimate Edition), Build #IU-242.20224.419, built on August 19, 2024
Continue: 0.0.64
OS: Win 11
Using context provider "codebase" for both claude-3-5-sonnet-20240620 or gpt-4o-mini-2024-07-18,
With Prompt like @codebase describe structure
Causes message in Intellij:
Error getting context items from codebase: TypeError: db. search is not a function
And the following in core.log file:
Error retrieving from FTS: Error: SQLITE_ERROR: no such table: fts
As a result I can see in a chat that AI don't know what am I asking for.
Other context providers, I've tested like "folder" or "open" work without issues.
Configured EmbeddingsProvider is text-embedding-3-small
Moreover, not sure if related, right after start I can see in core.log:
Error loading config.ts:  Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
I've also tried to use early version of Continue -> same issues here.
Cheers, and looking for the fix!
First, looking promising, IJ plugin worth to spend hours to configure - keep going!

Same issue. Reported on discord.

I can't wait to see codebase context in action in IntelliJ, so I've spent last few hours to try to spot the root cause... So...
In my opinion, the problem is with FullTextSearchCodebaseIndex and its createTables method.
https://github.com/continuedev/continue/blob/ed9bbba81b68263c7fd1ae54e0f65c981eec958b/core/indexing/FullTextSearch.ts#L22
I suppose, changing a place of fts tables creation to a constructor of the FTSCI should solve a race contition to read the tables from other places, which are quite few.
https://github.com/continuedev/continue/blob/ed9bbba81b68263c7fd1ae54e0f65c981eec958b/core/indexing/CodebaseIndexer.ts#L91
https://github.com/continuedev/continue/blob/ed9bbba81b68263c7fd1ae54e0f65c981eec958b/core/autocomplete/retrieval.ts#L13
https://github.com/continuedev/continue/blob/ed9bbba81b68263c7fd1ae54e0f65c981eec958b/core/context/retrieval/fullTextSearch.ts#L15
What do you think?

Same problem, any help?

came here to check on this same issue. I am getting the same bug on vscode with the recommended config for "Best overall experience" https://docs.continue.dev/setup/configuration#best-overall-experience
I suppose the issue is not specific to the embeddings model used

Same, tried with openai embeddings. Worked initially, broke on the second generation

Codebase working again for me in 9.202 with VSCode.

This typo here was causing the fts table not to be created https://github.com/continuedev/continue/commit/16c795ee52aa4379045e6e06dd858b076c595484
This fix is released already in vscode 0.9.202 as noted above, and will soon be released in Jetbrains!

I've installed the EAP in Jetbrains and this solved my problem. Thanks!

I'm also 0.0.68 and 2024.2.1. Before updating @codebase didn't work at all but I could send entire files (e.g., @tox.ini) before updating.
Are you sure you have the same bug? (Error retrieving from FTS: Error: SQLITE_ERROR: no such table: fts)

@Will-So No I don't see that error anymore. The logs look fine and codebase retrieval seems to work. But I cannot use specific file context anymore. See screenshot. It's always "Loading"

Here's my config:
{
  "systemMessage": "You are a senior software developer who specializes in Python 3.11 with pydantic v2. You adhere to SOLID and DRY principles. You specialize in unit testing and refactors. Your unit tests should always be done with pytest and prefer using classes for tests. You always use static typing. You focus on performance, maintainability, readability and security. You always use existing docstrings and write new ones in the sphinx format, if needed. You favor pep 8 python formatting and you write method parameters on new lines.",
  "contextProviders": [
    {
      "name": "file"
    },
    {
      "name": "code"
    },
    {
      "name": "search"
    },
    {
      "name": "repo-map"
    },
    {
      "name": "codebase"
    },
    {
      "name": "folder"
    },
    {
      "name": "url"
    },
    { "name": "diff" },
    {
      "name": "database",
      "params": {
        "connections": [
          {
            "name": "cc_local",
            "connection_type": "mysql",
            "connection": {
              "user": "root",
              "host": "localhost",
              "database": "codecritic",
              "password": "",
              "port": 3306
            }
          }
        ]
      }
    }
  ],
  "models": [
    {
      "title": "gpt4o - LLM Router",
      "provider": "openai",
      "contextLength": 128000,
      "model": "gpt-4o",
      "apiBase": "http://localhost:8051/v1",
      "apiKey": "api-key",
      "completionOptions": {
        "maxTokens": 12000
      }
    },
    {
      "title": "deepseekv2.5 - LLM Router",
      "provider": "openai",
      "contextLength": 32768,
      "model": "deepseekv25",
      "apiBase": "http://localhost:8051/v1",
      "apiKey": "api-key",
      "completionOptions": {
        "maxTokens": 12000
      }
    },
    {
      "title": "Deepseek Coder 2 0724 - LLM Router",
      "provider": "openai",
      "contextLength": 32768,
      "model": "deepseek_coder_2_0724",
      "apiBase": "http://localhost:8051/v1",
      "apiKey": "api-key",
      "completionOptions": {
        "maxTokens": 12000
      }
    },
    {
      "title": "deepseekv2 - LLM Router",
      "provider": "openai",
      "contextLength": 32768,
      "model": "deepseekv2",
      "apiBase": "http://localhost:8051/v1",
      "apiKey": "api-key",
      "completionOptions": {
        "maxTokens": 12000
      }
    },
    {
      "title": "Llama 3.1 405b - LLM Router",
      "provider": "openai",
      "contextLength": 128000,
      "model": "llama31_405b",
      "apiBase": "http://localhost:8051/v1",
      "apiKey": "api-key",
      "completionOptions": {
        "maxTokens": 12000
      }
    },
    {
      "title": "Llama 3.1 70b - LLM Router",
      "provider": "openai",
      "contextLength": 128000,
      "model": "llama31_70b",
      "apiBase": "http://localhost:8051/v1",
      "apiKey": "api-key",
      "completionOptions": {
        "maxTokens": 12000
      }
    }
  ],
  "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. Prefer creating classes for the tests. Give the tests just as chat output, don't edit any file. Use pytest with classes.",
      "description": "Write unit tests for highlighted code"
    },
    {
      "name": "integration_test",
      "prompt": "{{{ input }}}\n\nWrite a comprehensive set of integration 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. Prefer creating classes for the tests. Give the tests just as chat output, don't edit any file. Use pytest with classes.",
      "description": "Write unit tests for highlighted code"
    },
    {
      "name": "doc",
      "prompt": "Write a docstring for the current code in sphinx format.  Do not add new code.",
      "description": "Write the docstring"
    },
    {
      "name": "review",
      "prompt": "Review this code and suggestion improvements if needed.",
      "description": "Review code"
    },
    {
      "name": "refactor",
      "prompt": "{{{ input }}}\n\nRefactor the selected code to improve its readability, maintainability, and performance.  Improving coupling, cohesion and efficiency.",
      "description": "Refactor the selected code"
    },
    {
      "name": "refactor_for_test",
      "prompt": "{{{ input }}}\n\nRefactor the selected code to improve its unit testability. SOLID principles should be followed and docstrings must be maintained. Prefer using Protocol instead of abstract classes for interfaces. If no refactor is needed, please write 'No refactor needed'.",
      "description": "Refactor the selected code"
    }
  ],
  "embeddingsProvider": {
    "provider": "ollama",
    "model": "nomic-embed-text"
  },
  "allowAnonymousTelemetry": true
}


Bugfix/admin not prio

Admins did get a very limited list on /start/ and /persons/,
if they also had an group-connection.
Now admin trumps the group-connection, and thus pages show all groups.

Took me some time to understand why the old data disappeared when i imported another group.
They didn't, I as admin just didn't have the rights to see them....


Vector Stream Network Analysis tool

I am more of a front-end user so this may be quite a bit more difficult than I imagine, but I would love to see the Vector Stream Network Analysis tool get added to WBT. I use it all the time in WhiteboxGAT. Lots of good uses for the output (as shown in your 2019 paper on the WhiteboxGAT version).
These are great tools you have developed, I am a big fan of them. Between WBT/GAT and Topotoolbox I rarely have to open ArcMap anymore.

Hello @sraul1 ,
The VectorStreamNetworkAnalysis Tool has been officially added to WhiteboxTools (https://www.whiteboxgeo.com/manual/wbt_book/available_tools/stream_network_analysis.html#VectorStreamNetworkAnalysis). The tool is apart of the General Toolset Extension and requires a software license. You can see more about the General Toolset Extension here.


[BUG]: AlmaLinux v8 warns it is not supported

What happened?
What happened?
After upgrading to Agent v3.243.0 the pipeline warns
The operating system version this agent is running on is not supported on an upcoming update to the Pipelines Agent.
The agent is hosted on AlmaLinux 8, which should be the same as the supported RHEL.
Versions
Agent: v3.243.0
OS: AlmaLinux 8
Versions
v243.0
AlmaLinux 8
Environment type (Please select at least one enviroment where you face this issue)

[X] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
AlmaLinux 8
Version controll system
No response
Relevant log output
No response

Hi @corppeon. Thanks for reporting!
This is a bug, you're right. We will add AlmaLinux to the list of supported OS and release a fix soon


Two level cache hierarchy

We need to implement two-level hierarchy (00/fcf5a6a, f4/3cf5a6a etc) for DVC cache the same way as Git caches are organized.
The reason - one level slows down the operations when the number of data files (including all the versions) is very big.

After a bit more thinking, I agree that this also makes sense to be included in the current release. I will take a closer look soon.


TMCM-1240

Hello,
Can we use this driver to control TMCM-1240? If not, is it possible to tweak the codes to accomodate TMCM-1240? What changes might be required in this case?
Thank you!

Hi @ahmad38faraz - we have a planned upgrade which you can try for TMCM-1240. It will be released by mid-next week. I'll notify you here once available.

Hello @mmaralit-adi , is there any progress on this issue so far? thanks!

Hello @ahmad38faraz - we finalized it in our internal repo today, planned release here is tomorrow (July 26). Will tag you again here once done.

Hi @ahmad38faraz, this is not committed at latest noetic branch (commit 4374d13). We are yet to tag that commit as v2.0.0. Please try and let us know if you encounter any problems.

Thank you very much! I am excited to look into the package.
I have TMCM-1240 (CANOpen) driver. I have a stepper motor which is not a trinamic stepper motor but compatible with the driver. I want to write hardware interface of this motor because it will be one of the joints of my robotic arm. So, essentially, I have to implement init(), read(), and write() functions for this motor.  I will go through the codes and will try to set it up.
Thank you again!

Closing now since TMCM-1240 as of v2.0.0-noetic.


 The problem when you want to update packages but do not really read all their changelogs.

I usually say something like "Bump deps" or "Update React" etc.


[Command Idea] Blacklist

Ive wondered for a while how i could make a blacklist command but im not sure how that could work for all commands. I know you can just add a list of userID's to return to, but that seems a bit... unconventional.

Make a class so that you can add a decorator that will check if the user is in the list of commands. For example
from blacklist import blacklist

@blacklist("list1")
@commands.command(name="command")
async def command_with_blacklist(self, ctx):
    """do somin"""
    # Code here

I can probably whip up an example soon but I'm still working on the help command upgrades

accidently closed this, my bad. But yeah, if you could put an example or something that be really nice

Yeah, I can do that once help command is done. Got some things irl to do then, if I have time, I'll start work on it. Me big big busy

Yeah, I can do that once help command is done. Got some things irl to do then, if I have time, I'll start work on it. Me big big busy

Alright, take your time. Im actually really appreciative of this repo. thanks for everything you've posted.

Yeah, I can do that once help command is done. Got some things irl to do then, if I have time, I'll start work on it. Me big big busy

Alright, take your time. Im actually really appreciative of this repo. thanks for everything you've posted.

No bother, I am happy you enjoy everything :D


Section about customization and configuration file location in docker

Fixes go-gitea/gitea#2173

LGTM

LGTM


[DO NOT DELETE] Todo List

General

[x] carousel
[x] Jekyll
[x] Materialise
[ ] Search page(google custem search engine)

Page

[ ] Blog

[x] Tags
[x] Catgories
[x] Archive

[x] List of all are websites (services)
[x] Team page

Wiki

[ ] Create articles

How do we fix the unticked boxes?

I will fix this never fear citizen

what at you talking about please explain


Add a PubKey Type to the types module

We need an implementation of
https://github.com/tendermint/tendermint/blob/dfa9a9a30a666132425b29454e90a472aa579a48/privval/socket.go#L503-L506
in the types module

As per discussion with @zmanian we initially only need to support ed25519 public keys. This will change later. I'll implement a ed25519 pub-key struct (we'll need that anyways) which can be easily converted into a signatory pub-key.

A followup on this with a few options on how this could be implemented.
This is a bit trickier than we thought. Reason for that is that on the go-side the registered type PubKeyEd25519 is just a type alias type PubKeyEd25519 [PubKeyEd25519Size]byte.
type PubKeyMsg struct {
	PubKey crypto.PubKey // <- we only need PubKeyEd25519 for this PR!
}

The encoded bytes will have prefix bytes for the registered types privval.PubKeyMsg and the registered type crypto.PubKeyEd25519.
To achieve the same via prost we would ideally, be able to annotate a rust type alias. That isn't possible as derive only works on structs, enums and unions.
In signatory, the key is a struct without an explicit field:
https://github.com/tendermint/signatory/blob/aec83b4c6f18b63f598bc74336ca6ad414988fba/src/ed25519/public_key.rs#L10-L14
This looks like another candidate how we could handle this: annotate a similar struct with derive. Again, this doesn't work from scratch. This time the restrictions come from proc-marco2 on which prost is based on (implicit field "names" are numbers).
This leaves us with two options:

add an amino_name (or similar) attribute to fields (and not only structs as currently) to derive the prefix bytes from (and without the need to define another annotated struct).

add an attribute a la skip_fieldnum_and_type; as field tagged with this attribute would cause encoding the field contents of field (and not their field num and wire type as default in amino and mandatory in proto3). This could even be useful to encode raw bytes as in secret connection: https://github.com/tendermint/tendermint/blob/2aa2b63cadc42cca1071c36adfd2f2ce14e1aa8f/p2p/conn/secret_connection.go#L202-L220

Thoughts @zmanian?  I'm leaning to option 2) as this would further ease implementing secret connection.

@Liamsi I'd suggest having separate types for serialization versus e.g. signatory::ed25519::PublicKey and impl Into (or a fallible method) to convert between them

Yes, thanks Tony. That was the plan anyways.


python3Packages.nexia: 0.9.10 -> 0.9.11

Motivation for this change
Update to latest upstream release 0.9.11
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

1 package failed to build:

home-assistant

2 packages built:

python38Packages.nexia
python39Packages.nexia

Successfully installed homeassistant-2021.7.4
/tmp/nix-build-homeassistant-2021.7.4.drv-0/source
Finished executing pipInstallPhase
@nix { "action": "setPhase", "phase": "fixupPhase" }
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/j0xhm8x1nw07d7dz75jvchcjg7ff72z4-homeassistant-2021.7.4
patching script interpreter paths in /nix/store/j0xhm8x1nw07d7dz75jvchcjg7ff72z4-homeassistant-2021.7.4
checking for references to /tmp/nix-build-homeassistant-2021.7.4.drv-0/ in /nix/store/j0xhm8x1nw07d7dz75jvchcjg7ff72z4-homeassistant-2021.7.4...
Rewriting #!/nix/store/yqjhkdarf7p74wcha7aypzsb751n7wl2-python3-3.9.5/bin/python3.9 to #!/nix/store/yqjhkdarf7p74wcha7aypzsb751n7wl2-python3-3.9.5
wrapping `/nix/store/j0xhm8x1nw07d7dz75jvchcjg7ff72z4-homeassistant-2021.7.4/bin/hass'...
Executing pythonRemoveTestsDir
Finished executing pythonRemoveTestsDir
@nix { "action": "setPhase", "phase": "installCheckPhase" }
running install tests
no Makefile or custom installCheckPhase, doing nothing
@nix { "action": "setPhase", "phase": "pythonCatchConflictsPhase" }
pythonCatchConflictsPhase
@nix { "action": "setPhase", "phase": "pythonRemoveBinBytecodePhase" }
pythonRemoveBinBytecodePhase
@nix { "action": "setPhase", "phase": "pythonImportsCheckPhase" }
pythonImportsCheckPhase
Executing pythonImportsCheckPhase
@nix { "action": "setPhase", "phase": "pytestCheckPhase" }
pytestCheckPhase
Executing pytestCheckPhase
mkdir: cannot create directory ‘/build/media’: No such file or directory

Is home assistant broken for the time being?


Fixes to make master work in a disconnected environment

Fixes to allow master to work without internet access:

Force ruby-augeas onto the uniform bcpc_chef_gem definition
Use the --deployment flag for bundler install when applicable
Add poise to the recipe for install_stub in C-A-R

Miscellaneous:

Update java 8 to b131, which is actually available on Oracle internet mirrors
Add a chef-bach version string to the message of the day

Resubmitted in 875


[Feature Request] [Collapsible Headings] Shortcut to add heading above/below

A really slick UI feature that would save people a lot of annoyance would be a shortcut to add a heading at the current level above/below the current section.
The most obvious use case is when you have two really long sections next to each other and want to add a section between. If you add a cell above the lower section title, the collapsible headings section (rightfully) expands the upper section. This then requires that you scroll to the bottom of the section to first add the desired section title, then usually back up again to collapse the accidentally expanded section.
This seems silly, but in truly huge notebooks like the ones I use to organize my Ph.D. work, I end up temporarily reactivating Vimperator to navigate at that point, when collapsible-headings could in principle be enough to keep everything organized.

Certainly possible, and sounds like a reasonable use-case. I guess we could add keyboard shortcuts and/or toolbar buttons easily enough, I'll take a look when I get a chance...

@brunobeltran  any suggestions for button icons/shortcut keys?

Similar to the Excel icon to add a row, but # Title1, # Title 2, etc instead of spreadsheet rows?
Link for reference Excel Insert Row Icon
Ideally the menu entry would be a drop down or list-like menu that lets you select from "add section  above", and "add section below", then adds a new markdown cell with ## Title in it with the appropriate number of pound signs to match the level of the nearest parent cell of the currently highlighted cell, then highlights the new cell for editing of the title.
Shift-A and Shift-B aren't taken, so it seems like that's the obvious way to extend the current a, b shortcuts for adding a cell above and below.
Thanks a ton for putting time into this! If I finish up my current project in time, I'll make sure to lend a hand.

Right, I haven't bothered making whole new icons, but currently (see PR #620) just gone with a # plus an arrow. If you fancy making some icons I'll be happy to include them. Toolbar buttons are optional, shortcuts default to shift-a and shift-b as you suggested, but are configurable as with the existing collapse/uncollapse/select shortcuts. I've also added items to the 'insert' menu, but didn't put in a dropdown yet (it seemed like it'd be more frustrating than useful, given only 2 items added to the menu). Let me know if/when you get a chance to test it 😊

oh, also worth noting that I've swapped a lot of the parameter names from things like collapsible_headings_shortcut_uncollapse to collapsible_headings.shortcuts.uncollapse, which will mean you'll need to reconfigure any non-default settings for those options.

@brunobeltran if this is working ok for you, I guess we can merge, since it's extra features rather than altering existing stuff...

Was going to submit a fix actually, or you can add it. You need a
Jupyter.notebook.execute_cell() at line 595ish of main.js. That way, if you
add a cell below, Collapsible Headings registers it as a title before you
put the user into edit mode, preventing it from being "bury"'d inside of an
existing, closed section.
Not sure if this makes sense?
On Wed, Jun 8, 2016 at 5:03 PM, Josh Barnes<EMAIL_ADDRESS>wrote:

@brunobeltran https://github.com/brunobeltran if this is working ok for
you, I guess we can merge, since it's extra features rather than altering
existing stuff...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ipython-contrib/IPython-notebook-extensions/issues/616#issuecomment-224767242,
or mute the thread
https://github.com/notifications/unsubscribe/ABaDPiKSQpaPh81IXMGZinWlk47bgSDYks5qJ1hmgaJpZM4Ir-GG
.


[Bug] Incorrect implementation "didFromUrl"

If code starts with verificationMethod of format:
did:web:ex.github.io:qa:alice#mdrZ9

Then function urlFromDid will return http://ex.github.io/qa/alice/did.json what is correct.
However didFromUrl having input as http://ex.github.io/qa/alice/did.json will return did:web:ex.github.io:qa:alice:did.json, what is not correct.
Expected did must be did:web:ex.github.io:qa:alice.
This happens because these lines have not entirely correct logic:
  if (pathname && pathname !== '/' && pathname !== '/.well-known/did.json') {
    pathComponent = pathname.split('/').map(encodeURIComponent).join(':');
  }

Before these lines I would do a transformation (which would fix the problem):
if (pathname.endsWith('/did.json')) {
    pathname = pathname.substring(0, pathname.length - '/did.json'.length);
}

Thanks @iliecirciumaru! You're absolutely right.
Do you mind adding a PR for this?

Thanks @iliecirciumaru! You're absolutely right. Do you mind adding a PR for this?

Yes, with a pleasure.
I will try to do it this week.

@dmitrizagidulin please take a look when you have time: https://github.com/interop-alliance/did-web-resolver/pull/21

@iliecirciumaru - thanks again for the fix! Will release a new version with it, shortly.

@iliecirciumaru - published as v3.0.1.

Thanks!


Add initial flake for installing build dependencies for proof-systems

This is the start of a very simple flake.
In scope for this version of the flake:

nix develop . will open a dev shell with everything you need to develop on various parts of proof-systems in scope (caveat about rust and ocaml toolchain version in next point).
You must still use rustup to manage your rust toolchains.
You must still use opam to manage your ocaml toolchains.

Out of scope for this version of the flake:

Distributed caching -- only if the others in this list come.
Actually building things using nix -- likely to come.

Can we have a continuous check in the CI that it works, and the code can be built, please?

Absolutely.  I have tested
cargo build and that succeeds.  What other checks would you like?  My understanding is there is go and ocaml code somewhere in this repo.

Can we have a continuous check in the CI that it works, and the code can be built, please?

Absolutely. I have tested
cargo build and that succeeds. What other checks would you like? My understanding is there is go and ocaml code somewhere in this repo.

Would it be worth, even if the nix config is simple, to check in the CI that it works? By running, for instance, cargo build in the nix environment? IIRC, we do that in the Mina repository.

I will make an issue so I don't forget to.


[BUG] npm run test requires a docker instance of OpenSearch

What is the bug?
Tests require a local OpenSearch running on 9200. This is unexpected for unit tests.
How can one reproduce the bug?
$ npm run test -- tools/tests/tester/TestsRunner.test.ts

><EMAIL_ADDRESS>test
> jest tools/tests/tester/TestsRunner.test.ts

 FAIL  tools/tests/tester/TestsRunner.test.ts
  ✕ stories folder (134 ms)

  ● stories folder

    connect ECONNREFUSED ::1:9200

      26 |     const response: Record<string, any> = {}
      27 |     const [url, params] = this.#parse_url(chapter.path, chapter.parameters ?? {})
    > 28 |     await axios.request({
         |     ^
      29 |       url,
      30 |       auth: {
      31 |         username: 'admin',

      at Function.Object.<anonymous>.AxiosError.from (node_modules/axios/lib/core/AxiosError.js:89:14)
      at RedirectableRequest.handleRequestError (node_modules/axios/lib/adapters/http.js:610:25)
      at ClientRequest.eventHandlers.<computed> (node_modules/follow-redirects/index.js:38:24)
      at Axios.request (node_modules/axios/lib/core/Axios.js:45:41)
      at ChapterReader.read (tools/src/tester/ChapterReader.ts:28:5)
      at ChapterEvaluator.evaluate (tools/src/tester/ChapterEvaluator.ts:35:22)
      at StoryEvaluator.#evaluate_chapters (tools/src/tester/StoryEvaluator.ts:71:28)
      at StoryEvaluator.evaluate (tools/src/tester/StoryEvaluator.ts:50:22)
      at TestsRunner.run (tools/src/tester/TestsRunner.ts:45:26)
      at Object.<anonymous> (tools/tests/tester/TestsRunner.test.ts:20:30)

    Cause:
    connect ECONNREFUSED ::1:9200

Test Suites: 1 failed, 1 total
Tests:       1 failed, 1 total
Snapshots:   0 total
Time:        1.42 s, estimated 2 s

What is the expected behavior?
Tests run by default should not require a server.
Do you have any additional context?
We can move some tests to integration tests, use mocks, or the new --dry-run option added in #303.
Running all tests fails with unhelpful errors.
node:internal/child_process/serialization:159
    const string = JSONStringify(message) + '\n';
                   ^

TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'Object'
    |     property '_httpMessage' -> object with constructor 'Object'
    --- property 'socket' closes the circle
    at stringify (<anonymous>)
    at writeChannelMessage (node:internal/child_process/serialization:159:20)
    at process.target._send (node:internal/child_process:838:17)
    at process.target.send (node:internal/child_process:738:19)
    at reportSuccess (/Users/dblock/source/opensearch-project/opensearch-api-specification/dblock-opensearch-api-specification/node_modules/jest-worker/build/workers/processChild.js:82:11)

The weird error message comes from Jest. I got the exact same error previously when trying to run the integ tests for the spec test framework without a docker container running. Instead of an AXIOS error being printed out (as it does when you run npm run test:spec), Jest obfuscates that error and throws TypeError: Converting circular structure to JSON instead because the AXIOS error object has cyclic references among its properties.

tools/tests/tester/TestsRunner.test.ts is actually an integ test tho?


ari.lt

my website, https://ari.lt/
~80 kb

Welcome to the 250Kb Club! Your page will be https://250kb.club/ari-lt


How does it compare to LiquidCore or other similar projects?

In terms of start time time, executing time, cross platform support?
https://github.com/LiquidPlayer/LiquidCore

iOS has JavaScriptCore and the web has always been a native JavaScript VM
so there's no need for cross platform support in Duktape (and it's not like
that library offers cross platform support anyway).
Duktape is about 100x smaller than LiquidCore, so there's that.
There's no real startup time, but parsing and execution depends on what JS
you're running and you'll have to measure those things for yourself.
On Wed, Aug 30, 2017 at 11:34 PM letitfly<EMAIL_ADDRESS>wrote:

In terms of start time time, executing time, cross platform support?
https://github.com/LiquidPlayer/LiquidCore
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/square/duktape-android/issues/94, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEEEWY9LMICY86G00460JcctM6JL2lSks5sdim-gaJpZM4PIQq4
.

That's the info I am looking for.  Thank you!


remove reference to window in override console

replacing the reference to window.console to just console so that it works in Node.

Wow, does this work for web too?

yes, it does work for both

I will update the npm package in a few hours. I have a vet appointment (not for me.)

awesome !

Did you get a chance to update the npm package

I sure did. Try it out

Works great now.  Thank you !


[ENH] Make GIFs look much better for qsiprep results on T2ws

The opacity parameters needed some tweaking and I refactored the code.

Bringing in HBCD specific updates from Matt


refactor(initializer): use fs.copy and for...of

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
The changes are appropriately documented (not applicable).
[x] The changes have sufficient test coverage (if applicable).
[x] The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:
We use the excellent fs-extra module now :smile:
Also, I try to avoid forEach unless there's a good reason to use it. Especially given that Node 6 is required.

The test failure is a yarn issue, merging 👍


Model keeps accumulating the new and the restored variables after a restoring from a checkpoint resulting in bigger model size.

When you restore the model from a checkpoint it retains the new variables which are created as part of the initialization of the model during the restore in the tf.session along with the restored variables.
So when the restored model is saved again the size of the checkpoint doubles or increases by the previous checkpoint size.

Image showing duplicate variables in the session


Linux pypi packages do not work

See #122
The problem is that vtk is built on a too recent Ubuntu distro. I think I should move the cibuildwheels to manylinux_2014, and change the vtk-buikds to use that very same container

Good news, I already fixed the vtk-builds.
I also produced some artifacts and tested them on Linux. Everything worked like a charm.
I finally fixed the pipeline, which now building all the architectures. Hopefully I am submitting the PR tomorrow

This has been solved here


Add history as a global variable.

Fixes #910

I started to do that, but it was a rabbit hole. Do you want me to remove the other duplications (like location)?

I removed the duplicates I saw in a quick scan.


Make sure that Group  is taken into account when filling out an org hierarchy

This is not necessarily the most efficient code. But the dataset is so small and it's only done "offline", that it's not worth rewriting right now.

Yep, should totally not be done that way in the end. Best thing would be if this was done by a completely separate processor, even in the BuiltinKindsEntityProcessor - but it would have to be able to get a global view of the catalog state. Either that, or this one could emit relations and then just live with the fact that there will typically be duplicates emitted elsewhere.

With relations you typically don't get duplicates, as you'd just define the relations from one end


Avoid warning the user about oc not found

The approach we took for choose if oc needs to be installed or not is to call it, and if it fails, rescue the task and install it. That yields an error that a user is usually interpreting as a real one. We should not pass that error to the user, and ignore it.
At the same time, it seems that under certain circumstances, the fact catching mechanism is capturing the variable that holds where oc should be installed, what's a problem if the previous run was done with a different user, like root, as the extraction of oc will fail because of lack of permission.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

/lgtm


3d version

Hi!
I wanted to first thank you for this incredibly cute icon!
I've been using it for a while and it has made my programming days a lot more enjoyable. :)
Second, I wanted to say that I took your challenge (in https://github.com/jaidetree/doom-icon?tab=readme-ov-file#try-3d-modeling-a-version) and I made a 3D version that is 3d-printer/slicer friendly!
It's on sketchfab: https://sketchfab.com/3d-models/doom-cacodemon-923becaf8202497388c25dab0b3bd9e7
I could upload it here too if you want, as long as I'm credited. I can make a usda version so it's just a big ASCII text file.
Here are some screengrabs of quick renders coming from Blender:

Thank you!
Valerio

Wow! You did a great job! The lighting, the texturing, and sculpting look fantastic.
As far as where it lives, my plan a year ago was to archive this repo in favor of https://github.com/jaidetree/eccentric-icons given it now includes icons for kitty terminal and more apps overtime. It also includes a script for automatically downscaling images and creating image sets so it's easier to maintain.
Could you please render a transparent png?
That said, I would like to add this one here too just because it's so good then archive it and point to the new repo.
This is kinda embarrassing I did take a stab at a high-poly and low-poly version in Nomad sculpt but still have a lot to learn 😓
They're below for a laugh. Thanks for sharing this!

Thank you! I'm glad you like it, your icon was the original inspiration so I tried to keep the final style as close as possible to yours.
Here you go, I've rendered a 1920x1920 transparent PNG here: https://valerioviperino.me/assets/img/articles/cacodemon/doom-emacs-cacodemon-v013.png , you'll find another image on my website too: https://valerioviperino.me/of-dooming-cacodemon/ (I couldn't upload it here directly since it was above 10MB).
For the 3d model itself, let me know if you want to host it here too, I could make a self-contained USDZ of the textures too, or just shared as USDA the 3d model only.

Sure I can add the source files if you'd like. I'm unfamiliar with 3d formats in general so whatever makes sense to you should be fine

Sorry for the delay!
I tried to set up LFS (since the .usda file comes at ~150 MB) :
$ du -sh *
648K    doom.icns
144K    doom.ico
208K    doom.png
272K    doom.svg
155M    doom.usda
3.8M    src

but it looks like GitHub doesn't actually support LFS on public forks.
I got this:

https://github.com/git-lfs/git-lfs/issues/1906#issuecomment-276602035

I could be wrong, but I recall modern versions of git automatically optimizing the way it handles the file after a certain threshold. I'll have to look that up later as I may have hallucinated that


Add sutaakar to org members and distributed workloads maintainers

Description
Add sutaakar to org members and distributed workloads maintainers
New Open Data Hub Member Requirements

[ ] New members have reviewed and acknowledged the Open Data Hub:

Code of Conduct
Contribution Guide
Community Membership Guidelines

[ ] Enabled 2FA on their GitHub account

Pull Request Requirements

[x] New members are added in alphabetical order
[x] Only one new member change per commit (if you add two members separate it in two commits
[x] For individual user changes: Commit message format Add <USERNAME> to <opendatahub-io, mlops-sig, ...>.
[ ] For new team requests: Commit message format Create <TEAMNAME>. If the new team consists solely of existing members, you may
[ ] New GitHub team requests are from an existing opendatahub-io member who will function as the maintainer of the team. Each additional member will follow the same requirements for adding new members

@accorvin @anishasthana Please approve


Ruby Bundix does not build on HEAD (maybe non-deterministic build?)

Here's the error message:
output path ‘/nix/store/q7aq9f95rnybb1snsif9271139vgsjvg-git-export’ should have r:sha256 hash ‘1l4r55n1wzr817l225l6pm97li1mxg9icd8s51cpfihh91nkdz68’, instead has ‘0q7cjmz1fsrw3yfsr3h274qjamwnw01xgaqq3h5cjbqlrni4iq7k’
cannot build derivation ‘/nix/store/jax9rqzrp6aq8q5jjxdavagp7mqgcbgn-ruby-2.1.3-p0-bundler-HEAD.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/h04qx4xj9x6c6gawqp3d62hxd1cdrjjn-bundix.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/h04qx4xj9x6c6gawqp3d62hxd1cdrjjn-bundix.drv’ failed

Here's the full log:
~/p/nixpkgs (master)$ git rev-parse HEAD
abf330a79aa4bb10b23c729e553cfa9688b0b1c3
~/p/nixpkgs (master)$ uname -a
Linux rtmnix 3.14.36 #1-NixOS SMP Thu Jan 1 00:00:01 UTC 1970 x86_64 GNU/Linux
~/p/nixpkgs (master)$ nix-shell -I . -p bundix --pure
these derivations will be built:
  /nix/store/n7405xxvann2xqb1xh1rwk4gk7mmvjqz-git-export.drv
  /nix/store/jax9rqzrp6aq8q5jjxdavagp7mqgcbgn-ruby-2.1.3-p0-bundler-HEAD.drv
  /nix/store/h04qx4xj9x6c6gawqp3d62hxd1cdrjjn-bundix.drv
building path(s) ‘/nix/store/q7aq9f95rnybb1snsif9271139vgsjvg-git-export’
exporting https://github.com/bundler/bundler.git (rev a2343c9eabf5403d8ffcbca4dea33d18a60fc157) into /nix/store/q7aq9f95rnybb1snsif9271139vgsjvg-git-export
Initialized empty Git repository in /nix/store/q7aq9f95rnybb1snsif9271139vgsjvg-git-export/.git/
remote: Counting objects: 42487, done.
remote: Compressing objects: 100% (162/162), done.
remote: Total 42487 (delta 3), reused 150 (delta 0), pack-reused 42325
Receiving objects: 100% (42487/42487), 16.56 MiB | 6.08 MiB/s, done.
Resolving deltas: 100% (22164/22164), done.
From https://github.com/bundler/bundler
 * [new branch]      0-8-stable -> origin/0-8-stable
 * [new branch]      0-9-stable -> origin/0-9-stable
 * [new branch]      1-0-stable -> origin/1-0-stable
 * [new branch]      1-1-stable -> origin/1-1-stable
 * [new branch]      1-2-stable -> origin/1-2-stable
 * [new branch]      1-3-stable -> origin/1-3-stable
 * [new branch]      1-5-stable -> origin/1-5-stable
 * [new branch]      1-6-stable -> origin/1-6-stable
 * [new branch]      1-7-stable -> origin/1-7-stable
 * [new branch]      1-8-stable -> origin/1-8-stable
 * [new branch]      1-9-stable -> origin/1-9-stable
 * [new branch]      1-99-dev   -> origin/1-99-dev
 * [new branch]      171        -> origin/171
 * [new branch]      2-0-dev    -> origin/2-0-dev
 * [new branch]      2-0-dev-archived -> origin/2-0-dev-archived
 * [new branch]      2813-fix-self-dependency-bug -> origin/2813-fix-self-dependency-bug
 * [new branch]      autobundle -> origin/autobundle
 * [new branch]      checksum   -> origin/checksum
 * [new branch]      dont_run_git_commands_during_runtime -> origin/dont_run_git_commands_during_runtime
 * [new branch]      execless   -> origin/execless
 * [new branch]      fetchers_fetchers_everywhere -> origin/fetchers_fetchers_everywhere
 * [new branch]      fix-backtracking-from-child -> origin/fix-backtracking-from-child
 * [new branch]      fix-bug-with-bundle-cache-erroring -> origin/fix-bug-with-bundle-cache-erroring
 * [new branch]      fix-thread-safety-parallel-install -> origin/fix-thread-safety-parallel-install
 * [new branch]      fix-worker-cleanup-error -> origin/fix-worker-cleanup-error
 * [new branch]      fix-worker-index-jruby -> origin/fix-worker-index-jruby
 * [new branch]      fix_missing_gem_dir -> origin/fix_missing_gem_dir
 * [new branch]      gem_tasks  -> origin/gem_tasks
 * [new branch]      gemfile_hashing -> origin/gemfile_hashing
 * [new branch]      gh-pages   -> origin/gh-pages
 * [new branch]      make-paralle-fetch-jruby -> origin/make-paralle-fetch-jruby
 * [new branch]      master     -> origin/master
 * [new branch]      molinillo  -> origin/molinillo
 * [new branch]      new-index  -> origin/new-index
 * [new branch]      old-gem-version -> origin/old-gem-version
 * [new branch]      parallel_threads -> origin/parallel_threads
 * [new branch]      platforms  -> origin/platforms
 * [new branch]      refactor-resolver -> origin/refactor-resolver
 * [new branch]      removing_the_spec_gil -> origin/removing_the_spec_gil
 * [new branch]      retry_network -> origin/retry_network
 * [new branch]      rubygems22_exts -> origin/rubygems22_exts
 * [new branch]      seg-force  -> origin/seg-force
 * [new branch]      sources    -> origin/sources
 * [new branch]      test_default_gems -> origin/test_default_gems
 * [new branch]      travis-docker -> origin/travis-docker
 * [new branch]      unsupported_sources -> origin/unsupported_sources
 * [new branch]      user_agent -> origin/user_agent
 * [new branch]      user_agent2 -> origin/user_agent2
 * [new tag]         v1.1.5     -> v1.1.5
 * [new tag]         v1.2.5     -> v1.2.5
 * [new tag]         v1.6.9     -> v1.6.9
 * [new tag]         v1.7.14    -> v1.7.14
 * [new tag]         v1.8.6     -> v1.8.6
 * [new tag]         0.3.1      -> 0.3.1
 * [new tag]         0.4.0      -> 0.4.0
 * [new tag]         0.4.1      -> 0.4.1
 * [new tag]         0.5.0      -> 0.5.0
 * [new tag]         0.6.0      -> 0.6.0
 * [new tag]         0.7.0      -> 0.7.0
 * [new tag]         0.7.2      -> 0.7.2
 * [new tag]         0.8.0      -> 0.8.0
 * [new tag]         0.8.2      -> 0.8.2
 * [new tag]         0.8.5      -> 0.8.5
 * [new tag]         0.9.10     -> 0.9.10
 * [new tag]         0.9.11     -> 0.9.11
 * [new tag]         0.9.12     -> 0.9.12
 * [new tag]         0.9.13     -> 0.9.13
 * [new tag]         0.9.14     -> 0.9.14
 * [new tag]         0.9.15     -> 0.9.15
 * [new tag]         0.9.16     -> 0.9.16
 * [new tag]         0.9.17     -> 0.9.17
 * [new tag]         0.9.18     -> 0.9.18
 * [new tag]         0.9.19     -> 0.9.19
 * [new tag]         0.9.20     -> 0.9.20
 * [new tag]         0.9.21     -> 0.9.21
 * [new tag]         0.9.22     -> 0.9.22
 * [new tag]         0.9.23     -> 0.9.23
 * [new tag]         0.9.24     -> 0.9.24
 * [new tag]         0.9.25     -> 0.9.25
 * [new tag]         0.9.26     -> 0.9.26
 * [new tag]         0.9.3      -> 0.9.3
 * [new tag]         0.9.4      -> 0.9.4
 * [new tag]         0.9.5      -> 0.9.5
 * [new tag]         0.9.6      -> 0.9.6
 * [new tag]         0.9.7      -> 0.9.7
 * [new tag]         0.9.8      -> 0.9.8
 * [new tag]         0.9.9      -> 0.9.9
 * [new tag]         1.0.0      -> 1.0.0
 * [new tag]         1.0.0.beta.1 -> 1.0.0.beta.1
 * [new tag]         1.0.0.beta.10 -> 1.0.0.beta.10
 * [new tag]         1.0.0.beta.2 -> 1.0.0.beta.2
 * [new tag]         1.0.0.beta.3 -> 1.0.0.beta.3
 * [new tag]         1.0.0.beta.4 -> 1.0.0.beta.4
 * [new tag]         1.0.0.beta.5 -> 1.0.0.beta.5
 * [new tag]         1.0.0.beta.6 -> 1.0.0.beta.6
 * [new tag]         1.0.0.beta.7 -> 1.0.0.beta.7
 * [new tag]         1.0.0.beta.8 -> 1.0.0.beta.8
 * [new tag]         1.0.0.beta.9 -> 1.0.0.beta.9
 * [new tag]         1.0.0.rc.1 -> 1.0.0.rc.1
 * [new tag]         1.0.0.rc.2 -> 1.0.0.rc.2
 * [new tag]         1.0.0.rc.3 -> 1.0.0.rc.3
 * [new tag]         1.0.0.rc.4 -> 1.0.0.rc.4
 * [new tag]         1.0.0.rc.5 -> 1.0.0.rc.5
 * [new tag]         1.0.0.rc.6 -> 1.0.0.rc.6
 * [new tag]         v0.9.0     -> v0.9.0
 * [new tag]         v0.9.0.pre3 -> v0.9.0.pre3
 * [new tag]         v0.9.0.pre4 -> v0.9.0.pre4
 * [new tag]         v0.9.0.pre5 -> v0.9.0.pre5
 * [new tag]         v1.0.0     -> v1.0.0
 * [new tag]         v1.0.1     -> v1.0.1
 * [new tag]         v1.0.10    -> v1.0.10
 * [new tag]         v1.0.11    -> v1.0.11
 * [new tag]         v1.0.12    -> v1.0.12
 * [new tag]         v1.0.13    -> v1.0.13
 * [new tag]         v1.0.14    -> v1.0.14
 * [new tag]         v1.0.15    -> v1.0.15
 * [new tag]         v1.0.16    -> v1.0.16
 * [new tag]         v1.0.17    -> v1.0.17
 * [new tag]         v1.0.18    -> v1.0.18
 * [new tag]         v1.0.19.rc -> v1.0.19.rc
 * [new tag]         v1.0.2     -> v1.0.2
 * [new tag]         v1.0.20    -> v1.0.20
 * [new tag]         v1.0.20.rc -> v1.0.20.rc
 * [new tag]         v1.0.21    -> v1.0.21
 * [new tag]         v1.0.21.rc -> v1.0.21.rc
 * [new tag]         v1.0.22    -> v1.0.22
 * [new tag]         v1.0.3     -> v1.0.3
 * [new tag]         v1.0.4     -> v1.0.4
 * [new tag]         v1.0.5     -> v1.0.5
 * [new tag]         v1.0.6     -> v1.0.6
 * [new tag]         v1.0.7     -> v1.0.7
 * [new tag]         v1.0.8     -> v1.0.8
 * [new tag]         v1.0.9     -> v1.0.9
 * [new tag]         v1.1.0     -> v1.1.0
 * [new tag]         v1.1.1     -> v1.1.1
 * [new tag]         v1.1.2     -> v1.1.2
 * [new tag]         v1.1.3     -> v1.1.3
 * [new tag]         v1.1.pre   -> v1.1.pre
 * [new tag]         v1.1.pre.1 -> v1.1.pre.1
 * [new tag]         v1.1.pre.10 -> v1.1.pre.10
 * [new tag]         v1.1.pre.2 -> v1.1.pre.2
 * [new tag]         v1.1.pre.3 -> v1.1.pre.3
 * [new tag]         v1.1.pre.4 -> v1.1.pre.4
 * [new tag]         v1.1.pre.5 -> v1.1.pre.5
 * [new tag]         v1.1.pre.6 -> v1.1.pre.6
 * [new tag]         v1.1.pre.7 -> v1.1.pre.7
 * [new tag]         v1.1.pre.8 -> v1.1.pre.8
 * [new tag]         v1.1.pre.9 -> v1.1.pre.9
 * [new tag]         v1.1.rc    -> v1.1.rc
 * [new tag]         v1.1.rc.2  -> v1.1.rc.2
 * [new tag]         v1.1.rc.3  -> v1.1.rc.3
 * [new tag]         v1.1.rc.4  -> v1.1.rc.4
 * [new tag]         v1.1.rc.5  -> v1.1.rc.5
 * [new tag]         v1.1.rc.6  -> v1.1.rc.6
 * [new tag]         v1.1.rc.7  -> v1.1.rc.7
 * [new tag]         v1.1.rc.8  -> v1.1.rc.8
 * [new tag]         v1.2.0     -> v1.2.0
 * [new tag]         v1.2.0.pre -> v1.2.0.pre
 * [new tag]         v1.2.0.pre.1 -> v1.2.0.pre.1
 * [new tag]         v1.2.0.rc  -> v1.2.0.rc
 * [new tag]         v1.2.0.rc.2 -> v1.2.0.rc.2
 * [new tag]         v1.2.1     -> v1.2.1
 * [new tag]         v1.2.2     -> v1.2.2
 * [new tag]         v1.2.3     -> v1.2.3
 * [new tag]         v1.2.4     -> v1.2.4
 * [new tag]         v1.3.0     -> v1.3.0
 * [new tag]         v1.3.0.pre -> v1.3.0.pre
 * [new tag]         v1.3.0.pre.2 -> v1.3.0.pre.2
 * [new tag]         v1.3.0.pre.3 -> v1.3.0.pre.3
 * [new tag]         v1.3.0.pre.4 -> v1.3.0.pre.4
 * [new tag]         v1.3.0.pre.5 -> v1.3.0.pre.5
 * [new tag]         v1.3.0.pre.6 -> v1.3.0.pre.6
 * [new tag]         v1.3.0.pre.7 -> v1.3.0.pre.7
 * [new tag]         v1.3.0.pre.8 -> v1.3.0.pre.8
 * [new tag]         v1.3.1     -> v1.3.1
 * [new tag]         v1.3.2     -> v1.3.2
 * [new tag]         v1.3.3     -> v1.3.3
 * [new tag]         v1.3.4     -> v1.3.4
 * [new tag]         v1.3.5     -> v1.3.5
 * [new tag]         v1.3.6     -> v1.3.6
 * [new tag]         v1.4.0.pre.1 -> v1.4.0.pre.1
 * [new tag]         v1.4.0.pre.2 -> v1.4.0.pre.2
 * [new tag]         v1.4.0.rc.1 -> v1.4.0.rc.1
 * [new tag]         v1.5.0     -> v1.5.0
 * [new tag]         v1.5.0.rc.1 -> v1.5.0.rc.1
 * [new tag]         v1.5.0.rc.2 -> v1.5.0.rc.2
 * [new tag]         v1.5.1     -> v1.5.1
 * [new tag]         v1.5.2     -> v1.5.2
 * [new tag]         v1.5.3     -> v1.5.3
 * [new tag]         v1.6.0     -> v1.6.0
 * [new tag]         v1.6.0.pre.1 -> v1.6.0.pre.1
 * [new tag]         v1.6.0.pre.2 -> v1.6.0.pre.2
 * [new tag]         v1.6.0.rc  -> v1.6.0.rc
 * [new tag]         v1.6.0.rc2 -> v1.6.0.rc2
 * [new tag]         v1.6.1     -> v1.6.1
 * [new tag]         v1.6.2     -> v1.6.2
 * [new tag]         v1.6.3     -> v1.6.3
 * [new tag]         v1.6.4     -> v1.6.4
 * [new tag]         v1.6.5     -> v1.6.5
 * [new tag]         v1.6.6     -> v1.6.6
 * [new tag]         v1.6.7     -> v1.6.7
 * [new tag]         v1.6.8     -> v1.6.8
 * [new tag]         v1.7.0     -> v1.7.0
 * [new tag]         v1.7.1     -> v1.7.1
 * [new tag]         v1.7.1.pre -> v1.7.1.pre
 * [new tag]         v1.7.1.pre.2 -> v1.7.1.pre.2
 * [new tag]         v1.7.1.pre.3 -> v1.7.1.pre.3
 * [new tag]         v1.7.10    -> v1.7.10
 * [new tag]         v1.7.11    -> v1.7.11
 * [new tag]         v1.7.12    -> v1.7.12
 * [new tag]         v1.7.13    -> v1.7.13
 * [new tag]         v1.7.2     -> v1.7.2
 * [new tag]         v1.7.3     -> v1.7.3
 * [new tag]         v1.7.4     -> v1.7.4
 * [new tag]         v1.7.5     -> v1.7.5
 * [new tag]         v1.7.6     -> v1.7.6
 * [new tag]         v1.7.7     -> v1.7.7
 * [new tag]         v1.7.8     -> v1.7.8
 * [new tag]         v1.7.9     -> v1.7.9
 * [new tag]         v1.8.0     -> v1.8.0
 * [new tag]         v1.8.0.pre -> v1.8.0.pre
 * [new tag]         v1.8.1     -> v1.8.1
 * [new tag]         v1.8.2     -> v1.8.2
 * [new tag]         v1.8.3     -> v1.8.3
 * [new tag]         v1.8.4     -> v1.8.4
 * [new tag]         v1.8.5     -> v1.8.5
 * [new tag]         v1.9.0     -> v1.9.0
 * [new tag]         v1.9.0.pre -> v1.9.0.pre
 * [new tag]         v1.9.0.pre.1 -> v1.9.0.pre.1
 * [new tag]         v1.9.0.rc  -> v1.9.0.rc
 * [new tag]         v1.9.1     -> v1.9.1
 * [new tag]         v1.9.2     -> v1.9.2
Switched to a new branch 'fetchgit'
git revision is a2343c9eabf5403d8ffcbca4dea33d18a60fc157
git human-readable version is v1.7.9-390-ga2343c9
Commit date is 2015-01-11 17:25:27 -0800
Deleted remote branch origin/0-8-stable (was 74de75e).
Deleted remote branch origin/0-9-stable (was 6b60c60).
Deleted remote branch origin/1-0-stable (was 43a74f9).
Deleted remote branch origin/1-1-stable (was bbce585).
Deleted remote branch origin/1-2-stable (was 50ce456).
Deleted remote branch origin/1-3-stable (was 2df02a3).
Deleted remote branch origin/1-5-stable (was 7235f9e).
Deleted remote branch origin/1-6-stable (was 7e67be5).
Deleted remote branch origin/1-7-stable (was 1d7ab32).
Deleted remote branch origin/1-8-stable (was 52625b1).
Deleted remote branch origin/1-9-stable (was aef89a4).
Deleted remote branch origin/1-99-dev (was da8ffe2).
Deleted remote branch origin/171 (was ef9e90f).
Deleted remote branch origin/2-0-dev (was 8dd298c).
Deleted remote branch origin/2-0-dev-archived (was b909438).
Deleted remote branch origin/2813-fix-self-dependency-bug (was b88481e).
Deleted remote branch origin/autobundle (was 7cec62a).
Deleted remote branch origin/checksum (was 7dd7e49).
Deleted remote branch origin/dont_run_git_commands_during_runtime (was eaa91b9).
Deleted remote branch origin/execless (was 8bbd5b7).
Deleted remote branch origin/fetchers_fetchers_everywhere (was 20f628c).
Deleted remote branch origin/fix-backtracking-from-child (was 7a98d5d).
Deleted remote branch origin/fix-bug-with-bundle-cache-erroring (was a4ee812).
Deleted remote branch origin/fix-thread-safety-parallel-install (was 487862b).
Deleted remote branch origin/fix-worker-cleanup-error (was b6f0a56).
Deleted remote branch origin/fix-worker-index-jruby (was d4fb9f9).
Deleted remote branch origin/fix_missing_gem_dir (was 2f62ac5).
Deleted remote branch origin/gem_tasks (was a3c2fd8).
Deleted remote branch origin/gemfile_hashing (was 3d88ab9).
Deleted remote branch origin/gh-pages (was 6d2c016).
Deleted remote branch origin/make-paralle-fetch-jruby (was 57d8890).
Deleted remote branch origin/master (was af73937).
Deleted remote branch origin/molinillo (was 178247b).
Deleted remote branch origin/new-index (was aaad341).
Deleted remote branch origin/old-gem-version (was 5df697b).
Deleted remote branch origin/parallel_threads (was b1e7b7b).
Deleted remote branch origin/platforms (was c3b003c).
Deleted remote branch origin/refactor-resolver (was 1c121ea).
Deleted remote branch origin/removing_the_spec_gil (was 5b7f695).
Deleted remote branch origin/retry_network (was 833b69c).
Deleted remote branch origin/rubygems22_exts (was 9007c94).
Deleted remote branch origin/seg-force (was 97cb33c).
Deleted remote branch origin/sources (was eefe9c6).
Deleted remote branch origin/test_default_gems (was e2cf0b1).
Deleted remote branch origin/travis-docker (was f426548).
Deleted remote branch origin/unsupported_sources (was 39e7f6e).
Deleted remote branch origin/user_agent (was 8b1d376).
Deleted remote branch origin/user_agent2 (was 2441ff1).
Deleted tag 'v1.8.0' (was 25e30aa)
Deleted tag 'v1.8.0.pre' (was 3930ccc)
Deleted tag 'v1.8.1' (was 12edaff)
Deleted tag 'v1.8.2' (was 629365b)
Deleted tag 'v1.8.3' (was 86fbeb7)
Deleted tag 'v1.8.4' (was 047c935)
Deleted tag 'v1.8.5' (was 94abab8)
Deleted tag 'v1.8.6' (was 8bc00cb)
Deleted tag 'v1.9.0' (was 34922d2)
Deleted tag 'v1.9.0.pre' (was 8765197)
Deleted tag 'v1.9.0.pre.1' (was b49e03c)
Deleted tag 'v1.9.0.rc' (was 554f40e)
Deleted tag 'v1.9.1' (was a4bc7ec)
Deleted tag 'v1.9.2' (was 6373035)
output path ‘/nix/store/q7aq9f95rnybb1snsif9271139vgsjvg-git-export’ should have r:sha256 hash ‘1l4r55n1wzr817l225l6pm97li1mxg9icd8s51cpfihh91nkdz68’, instead has ‘0q7cjmz1fsrw3yfsr3h274qjamwnw01xgaqq3h5cjbqlrni4iq7k’
cannot build derivation ‘/nix/store/jax9rqzrp6aq8q5jjxdavagp7mqgcbgn-ruby-2.1.3-p0-bundler-HEAD.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/h04qx4xj9x6c6gawqp3d62hxd1cdrjjn-bundix.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/h04qx4xj9x6c6gawqp3d62hxd1cdrjjn-bundix.drv’ failed
/run/current-system/sw/bin/nix-shell: failed to build all dependencies
~/p/nixpkgs (master)$

cc @cstrahan

My installation command was wrong. I had
nix-shell -I . -p bundix --pure

when I should have had
nix-shell -I nixpkgs=. -p bundix --pure


Experimenting with running workflows on fork PRs with workflow_run trigger

#4922  👈
main

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

Join @CatChen and the rest of your teammates on  Graphite


Introduce typed version of coalesce

Fixes #1376

This is more of a sketch at the moment. The signature clashes with the old version of coalesce.
The new version provides better return types, but different name should be used to avoid clashes.

Looks good to me, even as a sketch.

I'd expect to see some unit tests for this.


Should entropy of different actions be reduced by sum?

Entropy is used in some PG algorithms (such as PPO, TRPO). The entropy of different actions is now reduced by mean:
entropy = tf.reduce_mean(input_tensor=tf.concat(values=entropies, axis=1), axis=1)

In my option, since the action number may be different in actions, the max values of entropy of each action are different, thus the more number of actions makes the larger max values. As a result, the mean of entropy of different actions do not make sense. If we do the mean,  we give a "weight" to the entropy by the number of actions, the action with more number has a larger weight. So, we should use reduce_sum to merge the entropy from different actions, and "sum" means the total information entropy of all the actions.
By the way, it's OK to reduce the entropy from different batch record, which is exactly the way in current implementation.

Would you suggest to apply tf.reduce_mean per action, but tf_reduce_sum for the resulting action means, or just replace tf.reduce_mean with tf.reduce_sum in the line you refer to? I assume the former, since it seems to me the latter wouldn't effectively change much. The former kind of makes sense to me, one would interpret an action consisting of potentially multiple sub-actions, but these sub-actions are not 'on the same level' as the actions  in terms of contribution to the loss. Would you agree with this understanding?

Yes, I agree with you. But, I think this is depends on the user, and current  implementation is OK. So, I close this issue.

Hmm, so you think it is fine after all? It won't necessarily make a massive difference, but I see the point of the latter possibility...


Evaluate gradio space tiiuae/falcon-180b-demo

While we wait for this 400GB monster to be quantized, let's take advantage of https://huggingface.co/spaces/tiiuae/falcon-180b-demo to pre-test this magnificent new bird.

Complete, note this is actually https://huggingface.co/tiiuae/falcon-180B-chat


Simple API for doing it all

This API will have a nice entry point with arguments:

The Job object
The Input dataset
Any other minor info
Number of files

It will return the following:

A list of files that can be opened on the local machine
An exception with the job id in it fi the job isn't done or failed.

Need to remind myself where this would get used... :-)


Python debugger doesn't work

Python debugger doesn't work with version 2022.4.0. (Run-Debugging/without debugging), however, after re-install the python extension with v2021.12.1559732655, everything works well. Please check this point out.
I follow accepted solution from link.
Thank you.

Exactly the same issue. The pre-Release version v2022.5.10911002 does not work, either. Only the older version works.

I have the same problem. Debugger will exit in a flash after launch. This happens only after a recent update.

Same here. This only happens when I launch VS Code from my Miniconda terminal (via the "code" command) though, which I sometimes need to do


Fix for user page playback

refs #935

This fix still gets the album name as the song title, just without the "noise"  (some span tag) that was in there before.
The actual tag to load the album name from on song title pages is the ... descendant of the album; or, equally valid, the ....

My bad - I was 1/2 a sleep. Are you sure you're change gets the currently playing track?

Yes, absolutely. I use this myself now.

-------- Ursprüngliche Nachricht --------Von: Malachi Soord  Datum: 06.04.16  14:43  (GMT+01:00) An: david-sabata/web-scrobbler  Cc: Regenspaziergang  Betreff: Re: [david-sabata/web-scrobbler] Fix for user page playback (#937)

My bad - I was 1/2 a sleep. Are you sure you're change gets the currently playing track?

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/david-sabata/web-scrobbler/pull/937#issuecomment-206352186

Could you please merge my proposed changes into this PR and tell the author that it works?

:+1: done


Add keypath parameter for typed calls

Resolves #17

This is a very cool addition and way cleaner than the previous globally set keypaths!!!


Refactor footer into its own html file and include it in all files

It's super annoying to edit the footer, because you then have to edit it on all pages.
-> Create a footer.html file and include this one in all *.html files that make use of the footer.

@Imipenem please take the footer from the JOIN page, since I fixed some links on this one.

As soon as this is done we can close https://github.com/cookiejar/cookietemple_website/issues/18

header as well


How to run with torchrun?

❓ Questions
Torchrun is the standard recommended way to run multi gpu, multi machine training. How can one launch projects that are written to use dora using torchrun?

Can you try torchrun -m yourproject.train [ARGS] ?
I think it should work out of the box if not I'll have a look. You won't be able to use some of the Dora features like inserting the base config from an existing run with -f [SIG]. If all your machines are on slurm then it will definitely be easier to use the grid system. If training on a single machine juste run dora run -d

I've checked this actually works, even on multi machines, see: https://github.com/facebookresearch/dora/blob/main/README.md#multi-node-training-without-slurm

https://github.com/facebookresearch/dora/blob/main/README.md#multi-node-training-without-slurm

hi, how does the [ARGS] here mean?

it seems that using torchrun has some logging issues


Nuxt3:  fast-deep-equal does not provide an export named 'default'

Describe the bug
Error in development in chrome
Uncaught SyntaxError: The requested module '/_nuxt/node_modules/fast-deep-equal/index.js?v=59f3ca57' does not provide an export named 'default'

Causes my whole script tag to pause in development.
But it transpiles and builds correctly in production environnement
To Reproduce
Steps to reproduce the behavior:

Followed steps here
And here
Start project in development mode

Expected behavior
The page to load and all subsequent vue script to load
Desktop (please complete the following information):**

Device: PC
OS: Windows 10
Browser Chrome
Version 106.0.5249.91

I had the same issue had to fix via vite config

    optimizeDeps: {
      // fast-deep-equal doesnt have default export
      // https://github.com/vitejs/vite/issues/2679
      include: ['@apollo/client/core', '@apollo/client/cache', '@apollo/client/link/context', 'fast-deep-equal'],
      exclude: ['@apollo/react'],
    },

'fast-deep-equal'

This works for me !, thanks a lot

Workaround: downgrade/pin version to 0.9.72
https://github.com/fawmi/vue-google-maps/issues/164#issuecomment-1320840776

optimizeDeps: {
// fast-deep-equal doesnt have default export
// https://github.com/vitejs/vite/issues/2679
include: ['@apollo/client/core', '@apollo/client/cache', '@apollo/client/link/context', 'fast-deep-equal'],
exclude: ['@apollo/react'],
},

Worked for me too


Support for attributes

It looks like it's currently not possible to add an attribute of an entity to the graph. Would be really nice, if the card could support this as I would like to compare multiple values that are not entities themselves. Thanks! 🙂

It's complicated. Basically it comes down to performance. Supporting attributes, as nice as it may be, would incur a hard performance toll on the card which would also affect all other graphs that don't show attributes. That's from the way the HA recorder manages the database internally. There are (hacky) ways around this somewhat, but they would make the card code considerably more complex and hard to maintain.
Here's some more info from my post on the HA forums:
https://community.home-assistant.io/t/new-interactive-history-explorer-custom-card/369450/87
Due to these technical limitations, at this time I won't implement this sadly. But I will keep an eye on the option, maybe some future HA version will make this more efficient. In the meantime, you can always use a template sensor to map an attribute into its own state entity that can then be displayed.

Thanks for your reply. I understand the technical issues related to this change, so I think it's the best to put it on the back burner for now.
The workaround with templates sensors is a great interim solution, I didn't think of before, thanks!


Updated turbinia config template + added server count

…form config.
Thanks for opening a Pull Request!
Here's a handy checklist to ensure your PR goes smoothly.

[x] I signed Google's Contributor License Agreement
[x] My code conforms to Google's python style.
[x] My PR at a minimum doesn't decrease unit-test coverage (if applicable).
[x] My PR has been functionally tested.
[x] All of the tests pass.
[x] I have submitted a corresponding PR for documentation in the forsetisecurity.org-dev branch and included this on this PR (if applicable).
[x] My documentation has been functionally tested and used (if applicable).
[x] I have submitted a corresponding PR in the Forseti Terraform module (if applicable).

These guidelines and more can be found in our contributing guidelines.

fixes https://github.com/google/turbinia/issues/520

fixes google/turbinia#523

fixes google/turbinia/issues/512

@alimez Do you need someone to review this PR?

@gkowalski-google yes it needs a reviewer. PTAL


Marine Coders 404 Page

Summary
Currently Marine Coders has a default Github 404 page. Eventually transitioning off of Github Pages into a Government owned S3 bucket we will need a custom 404 page.

Ideas from Slack

I think the 404 page should just say "lcpl don't know"

Can it alternate between that and a lost TBS student holding a map and compass?


Godot 3.0.beta.build1 crashes after creating new project or opening existing project

**Operating system or device, Godot version, GPU Model and driver (if graphics related):
Mac OSX 10.9.5, Godot 3.0 beta1
Issue description:
Godot 3.0.beta.build1 crashes after creating new project or opening existing project.
I first trashed my Godot 3.0.alpha.build2 version and the one project I had created using it. I downloaded Godot 3.0.beta.build1 and dragged it to my applications folder. I started the app and got the create project dialog entered a directory and a folder and clicked create. Then the app crashed before I get to the editor. When I reopen the Godot, the new project is listed but when a double click it Godot crashes again.
I have posted the beginning of the error log below for reference. I also noticed that the size of the beta1 app is only 72 MB while the alpha2 app is 140.7 MB.
Steps to reproduce:
Start a new project causes a crash
Open a project causes a crash
top section of error log
Process:         Godot [1014]
Path:            /Users/USER/Downloads/Godot.app/Contents/MacOS/Godot
Identifier:      org.godotengine.godot
Version:         3.0-dev (3.0-dev)
Code Type:       X86-64 (Native)
Parent Process:  ??? [1]
Responsible:     Godot [1014]
User ID:         501
Date/Time:       2017-12-01 15:57:57.170 -0800
OS Version:      Mac OS X 10.9.5 (13F1507)
Report Version:  11
Anonymous UUID:  2801C782-005A-B2E4-6A7D-62CD0C8C02DF
Crashed Thread:  0  Dispatch queue: com.apple.main-thread
Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Dyld Error Message:
Symbol not found: __os_log_internal
Referenced from: /Users/USER/Downloads/Godot.app/Contents/MacOS/Godot
Expected in: /usr/lib/libSystem.B.dylib

Not a high priority. Downvoted, and voting to close.


Allow overriding the base queryset to be used in Snippets IndexView

Part of wagtail/rfcs#85. Incorporates #10271.
This PR extracts a get_base_queryset() method to the generic IndexView (inspired by ModelAdmin's WMABaseView.get_base_queryset() for the initial logic of the queryset, before any filters or search are applied. The API is surfaced in SnippetViewSet as get_queryset(request) to mirror ModelAdmin.get_queryset(request) API. On the Snippets IndexView.get_base_queryset(), we first try to call SnippetViewSet.get_queryset(self.request). If the result is None (the default), the original implementation in the generic IndexView is used.
Please check the following:

[x] Do the tests still pass?[^1]
[x] Does the code comply with the style guide?

[x] Run make lint from the Wagtail root.

[x] For Python changes: Have you added tests to cover the new/fixed behaviour?
[x] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
Continuing the test example in #10256:
from wagtail.snippets.models import register_snippet
from wagtail.snippets.views.snippets import SnippetViewSet

class PersonViewSet(SnippetViewSet):
    icon = "user"
    list_per_page = 2
    chooser_per_page = 1
    admin_url_namespace = "some_namespace"
    base_url_path = "deep/within/the/admin"
    chooser_admin_url_namespace = "my_chooser_namespace"
    chooser_base_url_path = "choose/wisely"
    # this will generate exact filters
    list_filter = ["job_title", "first_name"]
    # alternatively, this will generate filters with lookups
    list_filter = {
        "job_title": ["contains"],
        "first_name": ["contains"],
        "first_published_at": ["date"],
    }

    def get_queryset(self, request):
        return self.model._default_manager.all().exclude(job_title__contains="[HIDDEN]")

register_snippet(Person, viewset=PersonViewSet)

If you create a Person object with a job title that contains [HIDDEN], it won't be shown on the listing view.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Merged in fbd3cca30f85a101f5f7f1a59900ee32a746fd84