Add Search Functionality to Documents

What would you like to be added:
Currently, there is no search functionality available within the document management system. The requested enhancement is to add a basic keyword search feature that allows users to search for specific terms within the document content. Additionally, it would be beneficial to incorporate a natural language search capability utilizing AI technology to enhance the search experience further.
Why is this needed:
The addition of a search feature will significantly improve user experience and efficiency when navigating through a large number of documents. By enabling users to search for specific content within documents, they can quickly locate relevant information, improving overall productivity.
Additional Information:

I will try this issue. Is there anything that I need to consider like how UI should look like?

I’ve assigned you to this task. Currently, there’s no UI/UX design for the search feature, so feel free to share any suggestions or ideas you might have!
I have a few questions regarding this feature:

What do you think about the scope of the search? Should it cover only the titles of documents, or both the titles and content? If we decide to include content search, we’ll need to discuss how to store the document content in our CodePair database.
Do you think MongoDB alone is sufficient for implementing the search feature? I believe it should be enough given the current low number of users, but I’d like to hear your thoughts.

If you have any questions or need clarification, don’t hesitate to ask!

@devleejb I’m planning to implement the title scope from the frontend side only, for now.

Due to the pagination API, It seems that it doesn't work properly.
How about adding search parameter to  GET /workspaces/{workspace_id}/documents?

@devleejb Great! I think I need to review the codebase and the API spec of the CodePair first :)

OK! Here are some code pointers related to this issue:
Frontend Hook for fetching documents: https://github.com/yorkie-team/codepair/blob/061dc3ead2501739e31136bde915bfb6de113e7d/frontend/src/hooks/api/workspaceDocument.ts#L25-L47
Backend API Controller (GET /workspaces/{workspace_id}/documents): https://github.com/yorkie-team/codepair/blob/061dc3ead2501739e31136bde915bfb6de113e7d/backend/src/workspace-documents/workspace-documents.controller.ts#L80-L110
Additionally, you can check the API spec in the Swagger documentation of the backend application by visiting http://localhost:3000/api. Please note that this page is accessible only when the backend server is running.


does goofys support multiple clients to mount a bucket?

I know YAS3FS does support multiple clients to mount a bucket, just wondering if goofys also support that? and what's the benchmark difference between goofys and YAS3FS?

goofys does not hook into SNS or use other mechanism to synchronize caches, but it also doesn't cache object contents. You can set --stat-cache-ttl and --type-cache-ttl to 0 to get up to date listings.
I have not benchmarked yas3fs but it shouldn't be hard to modify bench/run_bench.sh to do so.

To answer the title question, yes, in my experience goofys does support multiple clients mounting a single bucket. I have three servers currently running which all mount the same S3 bucket using goofys and also the same AWS credentials.


Allow Locale Configuration for Pyright Output Messages

Feature or enhancement
I am using the pyright-langserver-for-pycharm plugin on mac with IntelliJ. While Pyright provides diagnostic messages in multiple languages, it currently relies on the system-wide locale settings to determine the language of these messages. I would like to configure the language of Pyright's output messages independently of the system-wide locale settings, as changing the system locale is not always desirable or practical.
Proposed solution
I propose adding a feature to the pyright-langserver-for-pycharm plugin that allows users to configure the locale for Pyright's output messages directly within the IDE. This could be implemented as a settings option in the plugin, where users can specify the desired locale for diagnostic messages without affecting the system-wide locale settings on mac or other operating systems. This would offer greater flexibility for developers who work in multilingual environments or prefer to see error messages in a specific language.
Alternatives considered
No response
Additional context
https://github.com/microsoft/pyright/blob/main/docs/configuration.md#locale-configuration

@InSyncWithFoo
Thank you so much for the quick response and implementation! I’ve tried out the new build, and it works perfectly. The ability to configure the locale for Pyright’s output messages directly within the IDE is exactly what I needed. I really appreciate your prompt attention to this feature request and the excellent work in delivering it.
Thanks again for your support and for making this enhancement happen!


Add seals environments and corresponding (tentative) hyperparameters.

Thanks for the review @AdamGleave! This is a bit of a confusing PR, since it is constantly being rebased on top of https://github.com/DLR-RM/rl-baselines3-zoo/pull/240, which contains all the functionality that is going upstream. Most of your comments would rather apply to that PR.


Updated README.md with examples of access token as parameter

Updated README.md with examples of access token as parameter

that's great thanks! can you please rebase? :)

Hopefully this works! Sorry, it took me some time to figure it out. :)

Coverage remained the same at 100.0% when pulling 95755a8721aa1bcbb3f88af5f5421c17fa3cbd73 on khendrikse:master into 3a2bbb6270181a6b6ffc5dba1c249c39d03893c9 on pradel:master.

Also can you please run npm run format before the commit (it will make the ci green :) )

Coverage remained the same at 100.0% when pulling cb97e2f52dbcd1e1f7f6d1f41cf14386899fe41d on khendrikse:master into 3a2bbb6270181a6b6ffc5dba1c249c39d03893c9 on pradel:master.

Auch sorry for that, that was very messy of me. Hopefully now it works right?

Coverage remained the same at 100.0% when pulling 5f41545c45d6d24ec5ef61b13d447471b50c5305 on khendrikse:master into 3a2bbb6270181a6b6ffc5dba1c249c39d03893c9 on pradel:master.

Coverage remained the same at 100.0% when pulling 5f41545c45d6d24ec5ef61b13d447471b50c5305 on khendrikse:master into 3a2bbb6270181a6b6ffc5dba1c249c39d03893c9 on pradel:master.

Thats perfect thank you for the pr! :)


Update Notebook with API Changes

endpoints = [e for e, s in zip(meta.endpoints, meta.S) if (s > torch.quantile(meta.S, 0.9))] will throw this error if the list is empty:
Endpoints should have one of the following types. - a single endpoint tensor shape [250]...

Nice work, can you clear all outputs before submitting. This will clean the notebook.

@unconst resolved


Update Groovy to 3.0.8 for JDK17 support

And workaround the new bugs.
Specifically:

https://issues.apache.org/jira/browse/GROOVY-10055
https://issues.apache.org/jira/browse/GROOVY-10122

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


Add 'Dolby TrueHD' sound mode

Log from HA 0.92:
2019-04-29 11:45:24 WARNING (SyncWorker_17) [DenonAVR] Not able to match sound mode: 'Dolby TrueHD', returning raw sound mode.

thanks 👍


Custom redirect for broken pages

This adds a small JS script to every page of the developer hub.
We check the current url, and see if any of the desired redirect patterns match.
If so, we take the user to the new page, leaving the old page in history.
This script currently replaces instances of docs/en/next or docs/next with docs/en/knolwedgebase or docs/knolwedgebase which should handle the majority situation.
Custom full redirects beyond that can be added given the template I have provided, or this script can be modified for the needs of the site.

This probably needs to be customized further for all the ways that the dev hub has changed before being merged. Feel free to modify this PR and merge it at your own leisure.

which should handle the majority situation.

Actually I imagine this will break about 80% of the time. When I transitioned from here to the knowledge-base repo I reorganized the directory structure. We don't even have these conceptual and developer prefixes anymore.

@joepetrowski then you should customize the logic so that it handles your restructuring. In general I am not very aware of what was done.

makes sense to do a sweeping check for broken pages/links and either update them or nuke them- alternatively or in addition our 404 might reflect commonly searched for topics/spaces as a static list, including a reference to the riot chat for additional support

makes sense to do a sweeping check for broken pages/links and either update them or nuke them- alternatively or in addition our 404 might reflect commonly searched for topics/spaces as a static list, including a reference to the riot chat for additional support

Yes, I am 100% in favor of a 404 page with more info and a note that we've restructured. There really is no pattern to match. The old DevHub was deep in technical debt and I manually went through the articles one by one and either moved them to a new folder or deleted them (I found 3 "intro to ink" pages in different directories under the old structure...).
I know this is pessimistic but I think there are two options:

Redirect a few pages and show a useful error message for the rest.
Look at this commit and hardcode all these changes: https://github.com/substrate-developer-hub/knowledgebase/commit/4dae04260f3069150d488395c6c45c516c334ad1

@danforbes I would say that this would be an improvement. It's a small one but it could be complemented by other type of redirections. I think that it won't really break what exists, it would be another step to catch an incorrect url in case that they get through the first redirect.

@danforbes I would say that this is an improvement. It's a small one but it could be complemented with other type of redirections. I think that it won't really break what exists, it would be another step to catch an incorrect url in case that it gets through the first redirect.

So Id suggest we push a 404 page with more info and a note that we've restructured and are reworking the dev hub-- if people have additional issues suggestion they go to riot and write up a quick issue for us

That works for me. I pulled down this branch and tried to access the redirect logic and couldn't get anything useful to happen. I asked @riusricardo to look into things on his end to see if I'm just missing something. I am all for a more descriptive and helpful 404 page.

The logic is correct but Docusaurus ignores it.
I ran the script steps in the console and it does the redirect. But if I try to access the url directly or I modify it, it doesn't work.

The script works, you just need to set up your computer to serve the pages that we want to redirect from. You can test by creating dummy pages under a next folder

The script works, you just need to set up your computer to serve the pages that we want to redirect from. You can test by creating dummy pages under a next folder

If I understand correctly, what you are saying is doing something similar to the old redirect approach.
We need to recreate the old structure of docs with empty files under a next folder just to make this work.
Don't take it wrong, but from the analytics I saw that most of the invalid landing pages weren't using next or a version. However google could still have old docs in their cache.
IMHO looks to messy for a possible <20% success rate. If everyone agrees to this, we can do it.

@riusricardo you are incorrect here.
You only need to do this to simulate the redirect locally. The behavior of your local server versus the actual hosted server is not the same. On a local server, if you go to a page that does not exist you are not served any page.
If you go to a missing page on the real server, you are hosted a 404 page and hence you are also hosted this script.

Thanks for the clarification @shawntabrizi.
I'm good with the changes. We should commit and test. Then a follow-up PR could expand it.


Duplicate XML submissions to Crossref

Dave’s resource for reference:
https://www.hydroshare.org/resource/493e0ad05c2d45199427cc41a6c76de0/
Here is the most recent Crossref deposit for Dave’s resource
https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1609223636
In the message, it shows FAILURE:

<doi_batch_diagnostic status="completed" sp="ds3.crossref.org">
<submission_id>1609223636</submission_id>
<batch_id>493e0ad05c2d45199427cc41a6c76de0</batch_id>
<record_diagnostic status="Failure" msg_id="4">
10.4211/hs.493e0ad05c2d45199427cc41a6c76de0
Record not processed because submitted version:<PHONE_NUMBER>5239 is less or equal to previously submitted version<PHONE_NUMBER>5239
</record_diagnostic>
<batch_data>
<record_count>1</record_count>
<success_count>0</success_count>
<warning_count>0</warning_count>
<failure_count>1</failure_count>
</batch_data>
</doi_batch_diagnostic>

This failure message doesn’t make a lot of sense to me. The version numbers provided are actually the same exact number: “20230615035239”
The actual deposited XML:
https://doi.crossref.org/servlet/submissionAdmin?sf=content&submissionID=1609223636
And what was actually sent to Crossref:
https://new-hs-ci.hydroshare.org/view/02-Deployment/job/Production-Deployment/job/prod-hsctl-command/262/console
Additional information
HS v2.12
Related to https://github.com/hydroshare/hydroshare/issues/5225

After quite a bit of digging, I found this crossref record
https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1608210543

<doi_batch_diagnostic status="completed" sp="ds3.crossref.org">
<submission_id>1608210543</submission_id>
<batch_id>493e0ad05c2d45199427cc41a6c76de0</batch_id>
<record_diagnostic status="Success">
10.4211/hs.493e0ad05c2d45199427cc41a6c76de0
Successfully updated
</record_diagnostic>
<batch_data>
<record_count>1</record_count>
<success_count>1</success_count>
<warning_count>0</warning_count>
<failure_count>0</failure_count>
</batch_data>
</doi_batch_diagnostic>

Submission ID:<PHONE_NUMBER>
Version:	0
Name:	493e0ad05c2d45199427cc41a6c76de0_deposit_metadata.xml
Size:	5245 [bytes]
Type:	XML metadata
Received:	23-Jan-24 11:50:58
Started:	23-Jan-24 12:15:30
Finished:	23-Jan-24 12:15:35
Modified:	23-Jan-24 12:15:35

Comparing with
Submission ID:<PHONE_NUMBER>
Version:	0
Name:	493e0ad05c2d45199427cc41a6c76de0_deposit_metadata.xml
Size:	5245 [bytes]
Received:	29-Jan-24 12:05:25
Started:	29-Jan-24 12:05:33
Finished:	29-Jan-24 12:05:34
Modified:	29-Jan-24 12:05:34
https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1609223636

closing this issue because the 2nd record in crossref was a valid second submission, containing the same metadata as the first submission


jitpack io build failed.

Describe the bug
The jitpack.io build failed therefore android studio is unable to resolve it.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://jitpack.io/com/github/SimformSolutionsPvtLtd/SSImagePicker/2.2/build.log'
See error

Additional context

Logs
Build starting...
Start: Mon Apr 22 12:42:46 UTC 2024 298a9a930258
Git:
2.2-0-g21a7dac
commit 21a7dac86fdb529324efd7abfbc180ba9141b001
Author: SohamSimform
Date:   Mon Apr 22 17:59:22 2024 +0530

    Develop to Main (#70)

Init SDKMan
Found Android manifest
Android SDK version: . Build tools:
Found gradle
Gradle build script
Found gradle version: 8.2.
Using gradle wrapper
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Dhttps.protocols=TLSv1.2
Downloading https://services.gradle.org/distributions/gradle-8.2-bin.zip
.
Unzipping /home/jitpack/.gradle/wrapper/dists/gradle-8.2-bin/bbg7u40eoinfdyxsxr3z4i7ta/gradle-8.2-bin.zip to /home/jitpack/.gradle/wrapper/dists/gradle-8.2-bin/bbg7u40eoinfdyxsxr3z4i7ta
Set executable permissions for: /home/jitpack/.gradle/wrapper/dists/gradle-8.2-bin/bbg7u40eoinfdyxsxr3z4i7ta/gradle-8.2/bin/gradle

------------------------------------------------------------
Gradle 8.2
------------------------------------------------------------

Build time:   2023-06-30 18:02:30 UTC
Revision:     5f4a070a62a31a17438ac998c2b849f4f6892877

Kotlin:       1.8.20
Groovy:       3.0.17
Ant:          Apache Ant(TM) version 1.10.13 compiled on January 4 2023
JVM:          11.0.2 (Oracle Corporation 11.0.2+9)
OS:           Linux 4.14.63-xxxx-std-ipv6-64 amd64

0m4.495s
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Dhttps.protocols=TLSv1.2
openjdk version "11.0.2" 2019-01-15
OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)
Getting tasks: ./gradlew tasks --all
Tasks:

 ⚠   WARNING:
 Gradle 'publishToMavenLocal' task not found. Please add the 'maven-publish' or 'maven' plugin.
 See the documentation and examples: https://docs.jitpack.io

Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Dhttps.protocols=TLSv1.2
/home/jitpack/build/buildSrc/build.gradle.kts has component: java

FAILURE: Build failed with an exception.

* Where:
Build file '/home/jitpack/build/app/build.gradle.kts' line: 1

* What went wrong:
An exception occurred applying plugin request [id: 'com.android.application']
> Failed to apply plugin 'com.android.internal.application'.
   > Android Gradle plugin requires Java 17 to run. You are currently using Java 11.
      Your current JDK is located in /usr/lib/jvm/jdk-11
      You can try some of the following options:
       - changing the IDE settings.
       - changing the JAVA_HOME environment variable.
       - changing `org.gradle.java.home` in `gradle.properties`.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 2s
Running: ./gradlew -Pgroup=com.github.SimformSolutionsPvtLtd -Pversion=2.2 publishToMavenLocal

> Configure project :buildSrc
w: file:///home/jitpack/build/buildSrc/build.gradle.kts:2:5: 'jcenter(): MavenArtifactRepository!' is deprecated. Deprecated in Java
w: file:///home/jitpack/build/buildSrc/build.gradle.kts:10:15: The expression is unused
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Dhttps.protocols=TLSv1.2
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:10:13: Expecting an element
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:12:9: Expecting an element
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:19:34: Expecting an element
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:19:46: Expecting an element
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:20:34: Expecting an element
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:29:45: Expecting an element
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:10:1: Function invocation 'apply()' expected
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:10:1: Not enough information to infer type variable T
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:10:7: Unresolved reference. None of the following candidates is applicable because of receiver type mismatch:
public inline fun ObjectConfigurationAction.plugin(pluginClass: KClass<out Plugin<*>>): ObjectConfigurationAction defined in org.gradle.kotlin.dsl
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:10:15: Too many characters in a character literal ''maven-publish''
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:12:1: Unresolved reference: def
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:15:1: Expression 'publishing' cannot be invoked as a function. The function 'invoke()' is not found
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:15:1: Unresolved reference. None of the following candidates is applicable because of receiver type mismatch:
public val PluginDependenciesSpec.publishing: PluginDependencySpec defined in org.gradle.kotlin.dsl
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:16:5: Unresolved reference: publications
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:17:9: Expression '"${name}"' of type 'String' cannot be invoked as a function. The function 'invoke()' is not found
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:17:19: Classifier 'MavenPublication' does not have a companion object, and thus must be initialized here
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:19:17: Unresolved reference: def
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:19:54: Unresolved reference: it
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:19:65: Too many characters in a character literal ''java''
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:19:75: Unresolved reference: it
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:19:86: Too many characters in a character literal ''release''
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:20:17: Function invocation 'from(...)' expected
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:20:17: Unresolved reference. None of the following candidates is applicable because of receiver type mismatch:
public inline fun <reified T : VersionControlSpec> VcsMapping.from(noinline configureAction: TypeVariable(T).() -> Unit): Unit defined in org.gradle.kotlin.dsl
public inline fun <T : VersionControlSpec> VcsMapping.from(type: KClass<TypeVariable(T)>, configureAction: Action<in TypeVariable(T)>): Unit defined in org.gradle.kotlin.dsl
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:22:13: Unresolved reference: groupId
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:23:13: Unresolved reference: artifactId
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:24:23: Unresolved reference: ver
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:29:7: Unresolved reference: publishToMavenLocal

FAILURE: Build failed with an exception.

 None of the following candidates is applicable because of receiver type mismatch:
                     public inline fun ObjectConfigurationAction.plugin(pluginClass: KClass<out Plugin<*>>): ObjectConfigurationAction defined in org.gradle.kotlin.dsl

  Line 10: apply plugin: 'maven-publish'
                         ^ Too many characters in a character literal ''maven-publish''

  Line 12: def ver = version
                   ^ Expecting an element

  Line 12: def ver = version
           ^ Unresolved reference: def

  Line 15: publishing {
           ^ Expression 'publishing' cannot be invoked as a function. The function 'invoke()' is not found

  Line 15: publishing {
           ^ Unresolved reference. None of the following candidates is applicable because of receiver type mismatch:
               public val PluginDependenciesSpec.publishing: PluginDependencySpec defined in org.gradle.kotlin.dsl

  Line 16:     publications {
               ^ Unresolved reference: publications

  Line 17:         "${name}"(MavenPublication) {
                   ^ Expression '"${name}"' of type 'String' cannot be invoked as a function.  None of the following candidates is applicable because of receiver type mismatch:
                               public inline fun <reified T : VersionControlSpec> VcsMapping.from(noinline configureAction: TypeVariable(T).() -> Unit): Unit defined in org.gradle.kotlin.dsl
                               public inline fun <T : VersionControlSpec> VcsMapping.from(type: KClass<TypeVariable(T)>, configureAction: Action<in TypeVariable(T)>): Unit defined in org.gradle.kotlin.dsl

  Line 22:             groupId = group
                       ^ Unresolved reference: groupId

  Line 23:             artifactId = name
                       ^ Unresolved reference: artifactId

  Line 24:             version = ver
                                 ^ Unresolved reference: ver

  Line 29: tasks.publishToMavenLocal.dependsOn assemble
                                                       ^ Expecting an element

  Line 29: tasks.publishToMavenLocal.dependsOn assemble
                 ^ Unresolved reference: publishToMavenLocal

27 errors

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 2s
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Dhttps.protocols=TLSv1.2
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:10:13: Expecting an element
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:12:9: Expecting an element
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:19:34: Expecting an element
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:19:46: Expecting an element
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:20:34: Expecting an element
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:29:45: Expecting an element
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:10:1: Function invocation 'apply()' expected
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:10:1: Not enough information to infer type variable T
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:10:7: Unresolved reference. None of the following candidates is applicable because of receiver type mismatch:
public inline fun ObjectConfigurationAction.plugin(pluginClass: KClass<out Plugin<*>>): ObjectConfigurationAction defined in org.gradle.kotlin.dsl
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:10:15: Too many characters in a character literal ''maven-publish''
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:12:1: Unresolved reference: def
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:15:1: Expression 'publishing' cannot be invoked as a function. The function 'invoke()' is not found
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:15:1: Unresolved reference. None of the following candidates is applicable because of receiver type mismatch:
public val PluginDependenciesSpec.publishing: PluginDependencySpec defined in org.gradle.kotlin.dsl
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:16:5: Unresolved reference: publications
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:17:9: Expression '"${name}"' of type 'String' cannot be invoked as a function. The function 'invoke()' is not found
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:17:19: Classifier 'MavenPublication' does not have a companion object, and thus must be initialized here
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:19:17: Unresolved reference: def
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:19:54: Unresolved reference: it
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:19:65: Too many characters in a character literal ''java''
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:19:75: Unresolved reference: it
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:19:86: Too many characters in a character literal ''release''
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:20:17: Function invocation 'from(...)' expected
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:20:17: Unresolved reference. None of the following candidates is applicable because of receiver type mismatch:
public inline fun <reified T : VersionControlSpec> VcsMapping.from(noinline configureAction: TypeVariable(T).() -> Unit): Unit defined in org.gradle.kotlin.dsl
public inline fun <T : VersionControlSpec> VcsMapping.from(type: KClass<TypeVariable(T)>, configureAction: Action<in TypeVariable(T)>): Unit defined in org.gradle.kotlin.dsl
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:22:13: Unresolved reference: groupId
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:23:13: Unresolved reference: artifactId
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:24:23: Unresolved reference: ver
e: file:///home/jitpack/build/buildSrc/build.gradle.kts:29:7: Unresolved reference: publishToMavenLocal

FAILURE: Build failed with an exception.

 None of the following candidates is applicable because of receiver type mismatch:
                     public inline fun ObjectConfigurationAction.plugin(pluginClass: KClass<out Plugin<*>>): ObjectConfigurationAction defined in org.gradle.kotlin.dsl

  Line 10: apply plugin: 'maven-publish'
                         ^ Too many characters in a character literal ''maven-publish''

  Line 12: def ver = version
                   ^ Expecting an element

  Line 12: def ver = version
           ^ Unresolved reference: def

  Line 15: publishing {
           ^ Expression 'publishing' cannot be invoked as a function. The function 'invoke()' is not found

  Line 15: publishing {
           ^ Unresolved reference. None of the following candidates is applicable because of receiver type mismatch:
               public val PluginDependenciesSpec.publishing: PluginDependencySpec defined in org.gradle.kotlin.dsl

  Line 16:     publications {
               ^ Unresolved reference: publications

  Line 17:         "${name}"(MavenPublication) {
                   ^ Expression '"${name}"' of type 'String' cannot be invoked as a function.  None of the following candidates is applicable because of receiver type mismatch:
                               public inline fun <reified T : VersionControlSpec> VcsMapping.from(noinline configureAction: TypeVariable(T).() -> Unit): Unit defined in org.gradle.kotlin.dsl
                               public inline fun <T : VersionControlSpec> VcsMapping.from(type: KClass<TypeVariable(T)>, configureAction: Action<in TypeVariable(T)>): Unit defined in org.gradle.kotlin.dsl

  Line 22:             groupId = group
                       ^ Unresolved reference: groupId

  Line 23:             artifactId = name
                       ^ Unresolved reference: artifactId

  Line 24:             version = ver
                                 ^ Unresolved reference: ver

  Line 29: tasks.publishToMavenLocal.dependsOn assemble
                                                       ^ Expecting an element

  Line 29: tasks.publishToMavenLocal.dependsOn assemble
                 ^ Unresolved reference: publishToMavenLocal

27 errors

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 2s
Build tool exit code: 0
Looking for artifacts...
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Dhttps.protocols=TLSv1.2
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Dhttps.protocols=TLSv1.2
Looking for pom.xml in build directory and ~/.m2
2024-04-22T12:44:45.304172347Z
Exit code: 0

⚠ ERROR: No build artifacts found

incredibly version 2.1 with READ_MEDIA_IMAGES works fine but I wonder how 😄. I tested on the remote device with Android Studio Koala. it was interesting.

@farshadmb We are releasing the new version today to fix the issue on the current version.

thanks so much bro @yashwantgowla-simform <3

@farshadmb SSImagePicker is up now with the latest version v2.3.
https://github.com/SimformSolutionsPvtLtd/SSImagePicker/releases/tag/2.3
Please feel free to reach out in case of any issue and star this library for future updates. Thanks!


Avoid use of EpochInfo within ChainDB (and actually within consensus at all)

This is a second attempt at #1700, but got stuck on #1155. We've now solved that in #1706, but as a consequence this branch is once again horribly out of date and I will need to go again.

I should remember to close the branch used for #1700 once we're sure all the changes there have an analogue in this PR.

Superseded by #1750.


chore: update workflows now branch protection is enabled

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Global Intercom feature should be dropped

It is proprietary, instant voice-feature between team members like IM, which depends on an upstream Jitsi API that's now changed. Its usage also is reported to have been replaced. We should drop this feature.

Done in version 0.9.2.


Add auto-baseline main pipeline config for core

This should address the baseline PRs coming in for every pipeline

/azp run c - client


Support for Expo Managed Workflow

At first glance the library looks very promising, good job!
Unfortunately, I'm not able to utilze it in my Expo project. When I reach the page that renders Clusterer, I receive the following errors:
// iOS

Error: The package 'react-native-clusterer' doesn't seem to be linked. Make sure:

- You have run 'pod install'
- You rebuilt the app after installing the package
- You are not using Expo managed workflow

// Android

Error: The package 'react-native-clusterer' doesn't seem to be linked. Make sure:

- You rebuilt the app after installing the package
- You are not using Expo managed workflow

Project dependencies:
"expo": "~46.0.13",
"react": "18.0.0",
"react-native": "0.69.5",
"react-native-clusterer": "^1.2.2",
"react-native-maps": "^1.3.2"

I wonder if the problem will be resolved if I eject the Expo config, but I'm afraid I wouldn't want to do such change on the project configuration.

You don't need a config plugin because the library doesn't require any modifications to the native code. All you have to do is install the npm package and make an expo dev build


Footer login and register anchor tags works locally but not when deployed.

Description
The login and register links on the footer of landing page is not working and throwing a 404 error when clicked.
Screenshots

Additional information
No response

I've opened a pull request fixing this issue, Kindly check it out.

I've opened a pull request fixing this issue, Kindly check it out.


How to get the dom instance of the  component?

How can I get the DOM instance of the  component? I read the document, but the official ref can only call toggle. Is the next step planned to add methods that can obtain component instances?

you mean all components dom instance?

release on 2.0.0-alpha.34 🚀

aha, very thanks!


[5.5] Ability to build a response using a fallback route name

Having:
Route::fallback('ServersController@notFound')->name('notFoundServer');

In your exception handler or inside another route you can do:
return Route::respondWith('notFoundServer');

This will run the ServersController@notFound action and return its response.
This is useful for when you want to catch a ModelNotFound exception and return a fallback route instead of the 404.blade.php view.

Would this support route middlewares like StartSession so we can get session support on the custom 404 pages?

@sisve yes

Is this can be used with any route name?

@decadence I was able to use it with any route name.

@browner12
Any route as long as it doesn't require parameters © @themsaid

Where would be the best place to catch response exceptions and return return Route::respondWith('notFoundServer'); to override of normal behavior in the whole app?

@unstoppablecarl the exception handler.


High CPU and RAM Usage with Bolt.New

Describe the bug
When using language models that fit within my GPU (e.g., through Aider or OpenWebUI), they run smoothly, utilizing only the GPU and delivering optimal performance. However, when attempting to use the same models through Bolt.New, I encounter significant performance issues:
as soon as i send anything through bolt.new the ollama server spikes in both ram and CPU usage its as if im running a model that is a lot bigger not the same small model i am running.
Link to the Bolt URL that caused the error
I used pnpm run dev to test it out before deploying
Steps to reproduce
Load a language model that fits within the GPU using Bolt.New.
Observe CPU and RAM usage in the system monitor.
Note the token generation speed compared to other platforms.
Expected behavior
The model should run smoothly, leveraging the GPU for computation, similar to its performance in other environments like Aider or OpenWebUI.
Screen Recording / Screenshot
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

i second this too. right now i am 1hour  into generating an app with phi3.5 model on my M1 mac 8gb ram. this is the only model which responded fast and could actually execute and preview code. the others only behaved like chat-gpt offering me solutions that i could implement myself....but 1h into it and still going it hasnt finished generating the package.json file...
Is there a way to smooth this out ?

Same here high CPU and RAM Usage What will be the fix to this?

yeah so I'm on windows so what I did was set it in the environment variables. After that, I restarted the Ollama process to ensure it picked up the changes. Unfortunately, the issue still persists. Any ideas on what else I could try?"

I already have that pre-configured, also when i send a prompt using bolt.new if i open a a command terminal and type ollama ps I can see that the model I picked is the only one that's running so I don't think the issue is that multiple models are being loaded

this is an outdated version please try the latest and start a new issue if the problem persists

The problem persists.


Update link_credential_phishing_intent_and_other_indicators.yml

Description
Add additional coverage for missed password reset phish
Associated samples

Sample 1

Associated hunts
L14D of messages that will now match this rule

Hunt 1

Screenshot (insights)
For new insights only: Insert a screenshot of the insight firing. Remove this section if not applicable.

/mql-mimic-exempt: 428539
428539 = actually fires in analyzer


New menu

Opening for @lunson to demo under the snoopy account.

Lots of general impresssions:

I like the new top bar with the menu more than when it was at the side

Not sure about the Twitter/Facebook/LinkedIn/IRC bar - I find it disracting and will the content be IDR specific or be the openmicroscopy accounts.  Would a feedback/questions email button that sends us an email be better than IRC? This could be a final option on the menu bar.

The new top bars push the rest of the page content down quite far on my screen (13" laptop) so much so that it fills the screen and its not obvious that there is anything past 'Take a look at the data' on the 'About us' page. Could the background image be cropped so that its clear there is more content on that page?

What is at the top of the background image changes on different pages. Might be slicker to have the same top of the image on all pages.  Where the image is cut off at the bottom might change depending on the amount of text.

Because the drop downs always appear when you mouse over the 'Submissions Overview' it made me think that there was just the two 'Screens' and 'Experiments' pages and not an 'Overview' page aswell.  Maybe all 3 should appear in the drop down as 'Overview', 'Screens' and 'Experiments' and the top level text should just be 'Submissions'.  The top level could either link to the Overview if clicked on or not be a link and just allow selection from the 3 dropdown choices?

Hope this is helpful.

Not sure about the Twitter/Facebook/LinkedIn/IRC bar ... will the content be IDR specific or be the openmicroscopy accounts. Would a feedback/questions email button that sends us an email be better than IRC? This could be a final option on the menu bar.

I'd probably limit to twitter since that's the only account we have/use. (@IDRnews and @IDRstatus for deployment issues). I like the email/feedback button.

Not sure about the Twitter/Facebook/LinkedIn/IRC bar - I find it disracting and will the content be IDR specific or be the openmicroscopy accounts. Would a feedback/questions email button that sends us an email be better than IRC? This could be a final option on the menu bar.

What email do you want to use? I'll post the two twitter accounts and an email icon for the top bar in the next revision.

@joshmoore All of @eleanorwilliams' items have been addressed in this push. Let me know of any more changes. Thanks!

Screenshot updated.

":thumbsup:" in slack.


Development: Use GitLab library methods to create access tokens

@coderabbitai ignore

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[x] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] Important: I implemented the changes with a very good performance and prevented too many (unnecessary) database calls.
[x] I strictly followed the server coding and design guidelines.
[x] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[x] I documented the Java code using JavaDoc style.

Changes affecting Programming Exercises

[x] I tested all changes and their related features with all corresponding user types on a test server configured with Gitlab and Jenkins.

Motivation and Context
To create version control access tokens Artemis currently uses a custom DTO and calls the GitLab API directly via a REST request rather than using the GitLab4j library that abstracts the calls.
This library is used in many other places in Artemis where possible. A TODO already existed that this custom REST call should be replaced when available via the library instead.
Description
The GitLab API library has been updated since the TODO comment was added and added the required functionality natively. We now make use of it.
Steps for Testing

Prerequisites:

1 Artemis instance connected to Gitlab/Jenkins that has cloning via access tokens enabled (artemis.version-control.version-control-access-token: true in the config, might be enabled on the test servers, otherwise please test locally).

Register as a new user in Artemis.

If registration is disabled, as admin you can access the user management and create a new user there.

When starting an exercise, the clone URL has the format https://username:****@… Where **** is an access token for GitLab.
You can clone the repository using this URL, and also push changes to it.

Testserver States

[!NOTE]
These badges show the state of the test servers.
Green = Currently available, Red = Currently locked

Review Progress

Performance Review

[ ] I (as a reviewer) confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
[ ] I (as a reviewer) confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

[x] Code Review 1
[ ] Code Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Test Coverage

Class/File
Line Coverage
Confirmation (assert/expect)

GitlabUserManagementService.java
90%
✅

Superseded by #8175.


cleanup flow of constants and dev

@keybase/react-hackers more flow cleanup

👍

reopening vs master


Update README with building instructions.

Not being a Golang developer, I had to figure out how to actually build this. There is no top-level Makefile, nor does go build work out of the box. So here's what I figured out, as an enumerated list section in the README.

Thanks for the contribution. Much appreciated!
Just out of interest, why did you want to build from source? Did you miss that you could download binaries directly from Github releases, just a preference, or that you want to add a feature or something?

Ah, just seen your other PR. Makes sense now! Thanks!

Indeed, I have a use case for ddbimport (which really is faster than any other bulk import tool I tried), that is beyond what your version provides at the moment. But my input data comes in a strange form and number of files, because of legacy. Hence the need for accepting various file sizes in the other PR.
Additionally, ddbimport, as it is now, doesn't support values of complex types, like set, list or map. I do have a patch that handles maps, but only of a very specific format (string keys, numeric values) that is of little use to others.


Update dynamic code to use MTR functions

This PR updates the OG-USA code to allow for separately estimated MTR functions.
It also stream lines the code a bit so that running run_simulation_from_json.py will take create the microdata (with MTRs) , estimate the tax functions, and solve the model in the SS and along the time path.

OK @jdebacker I will continue to put updates/refactors in this PR. On my local machine, I have Amy's PR with the capital_mtr function for taxcalc and I have the PUF, so I can import ogusa. After running for a while, the output I get is:
Tax function estimation time:  36  min,  36.5  sec

So I think I'm on the right track in running everything.

@talumbau The commit above related to txfunc.py should help integrate it into the parameters.py file by creating a tax_func_estimate function.
These commits also fix:

get_micro_data.py - updated to grab combined rates for all years -  prior version just did this for 2015.
the calculation of the labor MTRs in txfunc.py (type created wrong ratios when doing weighted avg of mtr on wages and mtr on self-emp income.