Neo4j springboot migration fail using version 5.x

I am trying to use neo4j liquibase (4.17.1) using spring boot. But, while starting up the service, i am getting following exception for execution of liquibase change log.
2022-11-21 13:32:22.761  WARN 5812 --- [           main] o.n.jdbc.bolt.BoltNeo4jDatabaseMetaData  : Could not retrieve DBMS functions: org.neo4j.driver.exceptions.ClientException: There is no procedure with the name dbms.functionsregistered for this database instance. Please ensure you've spelled the procedure name correctly and that the procedure is properly deployed.
build.gradle is having following configuration.
    runtimeOnly 'org.springframework.boot:spring-boot-starter-jdbc'
    runtimeOnly 'org.liquibase:liquibase-core:4.17.2'
    runtimeOnly 'org.liquibase.ext:liquibase-neo4j:4.17.1'

Version 4.17.2 is not available on maven-central repository. But, I have seen that 4.17.2 is released in this repository already.
After doing some readup, i have found that there are some breaking changes in neo4j4.4 to neo4j5.0 .
Breaking changes neo4j
dbms.functions has been renamed to SHOW FUNCTIONS
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'liquibase' defined in class path resource [org/springframework/boot/autoconfigure/liquibase/LiquibaseAutoConfiguration$LiquibaseConfiguration.class]: Invocation of init method failed; nested exception is liquibase.exception.LockException: Could not acquire change log lock despite no lock currently stored
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1804) ~[spring-beans-5.3.23.jar:5.3.23]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:620) ~[spring-beans-5.3.23.jar:5.3.23]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542) ~[spring-beans-5.3.23.jar:5.3.23]
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335) ~[spring-beans-5.3.23.jar:5.3.23]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-5.3.23.jar:5.3.23]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333) ~[spring-beans-5.3.23.jar:5.3.23]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208) ~[spring-beans-5.3.23.jar:5.3.23]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:322) ~[spring-beans-5.3.23.jar:5.3.23]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208) ~[spring-beans-5.3.23.jar:5.3.23]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:955) ~[spring-beans-5.3.23.jar:5.3.23]
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918) ~[spring-context-5.3.23.jar:5.3.23]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583) ~[spring-context-5.3.23.jar:5.3.23]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:147) ~[spring-boot-2.7.4.jar:2.7.4]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:734) ~[spring-boot-2.7.4.jar:2.7.4]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:408) ~[spring-boot-2.7.4.jar:2.7.4]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:308) ~[spring-boot-2.7.4.jar:2.7.4]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1306) ~[spring-boot-2.7.4.jar:2.7.4]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1295) ~[spring-boot-2.7.4.jar:2.7.4]
	at com.proactis.core.organisation.OrganisationServiceApplication.main(OrganisationServiceApplication.java:12) ~[main/:na]
Caused by: liquibase.exception.LockException: Could not acquire change log lock despite no lock currently stored
	at liquibase.ext.neo4j.lockservice.Neo4jLockService.waitForLock(Neo4jLockService.java:73) ~[liquibase-neo4j-4.17.1.jar:4.17.1]
	at liquibase.Liquibase.lambda$update$1(Liquibase.java:239) ~[liquibase-core-4.17.2.jar:na]
	at liquibase.Scope.lambda$child$0(Scope.java:180) ~[liquibase-core-4.17.2.jar:na]
	at liquibase.Scope.child(Scope.java:189) ~[liquibase-core-4.17.2.jar:na]
	at liquibase.Scope.child(Scope.java:179) ~[liquibase-core-4.17.2.jar:na]
	at liquibase.Scope.child(Scope.java:158) ~[liquibase-core-4.17.2.jar:na]
	at liquibase.Liquibase.runInScope(Liquibase.java:2447) ~[liquibase-core-4.17.2.jar:na]
	at liquibase.Liquibase.update(Liquibase.java:236) ~[liquibase-core-4.17.2.jar:na]
	at liquibase.Liquibase.update(Liquibase.java:221) ~[liquibase-core-4.17.2.jar:na]
	at liquibase.integration.spring.SpringLiquibase.performUpdate(SpringLiquibase.java:328) ~[liquibase-core-4.17.2.jar:na]
	at liquibase.integration.spring.SpringLiquibase.afterPropertiesSet(SpringLiquibase.java:283) ~[liquibase-core-4.17.2.jar:na]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1863) ~[spring-beans-5.3.23.jar:5.3.23]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1800) ~[spring-beans-5.3.23.jar:5.3.23]
	... 18 common frames omitted
Caused by: java.util.concurrent.ExecutionException: liquibase.exception.LockException: Could not acquire lock
	at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[na:na]
	at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:205) ~[na:na]
	at liquibase.ext.neo4j.lockservice.ConditionCheckScheduler.scheduleCheckWithFixedDelay(ConditionCheckScheduler.java:38) ~[liquibase-neo4j-4.17.1.jar:4.17.1]
	at liquibase.ext.neo4j.lockservice.Neo4jLockService.waitForLock(Neo4jLockService.java:57) ~[liquibase-neo4j-4.17.1.jar:4.17.1]
	... 30 common frames omitted
Caused by: liquibase.exception.LockException: Could not acquire lock
	at liquibase.ext.neo4j.lockservice.Neo4jLockService.acquireLock(Neo4jLockService.java:129) ~[liquibase-neo4j-4.17.1.jar:4.17.1]
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[na:na]
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[na:na]
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[na:na]
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[na:na]
	at java.base/java.lang.Thread.run(Thread.java:833) ~[na:na]
Caused by: liquibase.exception.DatabaseException: Unique constraint creation for (n:__LiquibaseLock {lockedBy}) aborted: Neo4j version 5.1.0 is not supported
	at liquibase.ext.neo4j.database.Neo4jDatabase.createUniqueConstraint(Neo4jDatabase.java:109) ~[liquibase-neo4j-4.17.1.jar:4.17.1]
	at liquibase.ext.neo4j.lockservice.Neo4jLockService.init(Neo4jLockService.java:135) ~[liquibase-neo4j-4.17.1.jar:4.17.1]
	at liquibase.ext.neo4j.lockservice.Neo4jLockService.acquireLock(Neo4jLockService.java:109) ~[liquibase-neo4j-4.17.1.jar:4.17.1]
	... 5 common frames omitted

Caused by: liquibase.exception.LockException: Could not acquire change log lock despite no lock currently stored

Caused by: java.util.concurrent.ExecutionException: liquibase.exception.LockException: Could not acquire lock

Caused by: liquibase.exception.LockException: Could not acquire lock

Caused by: liquibase.exception.DatabaseException: Unique constraint creation for (n:__LiquibaseLock {lockedBy}) aborted: Neo4j version 5.1.0 is not supported```

Hello, as for https://github.com/liquibase/liquibase-neo4j/issues/282, the cause is the same: the underlying JDBC connector is not ready yet for v5, a release for Neo4j 5 support will land soon.

In the mean time, you can try building the neo4j-jdbc-bolt JAR from sources and see if that works for you:
git clone https://github.com/neo4j-contrib/neo4j-jdbc.git
mvn install --file neo4j-jdbc/pom.xml --also-make --projects neo4j-jdbc-bolt -DskipTests
Then add to your POM:

org.neo4j
neo4j-jdbc-bolt
5.1.0

Once you're done, do not forget to remove the dependency from your local cache (rm -r ~/.m2/repository/org/neo4j/neo4j-jdbc-bolt/5.1.0)

Alternatively @rohitbatta, can you try https://github.com/liquibase/liquibase-neo4j/releases/tag/liquibase-neo4j-jdbc-alpha-01 and report back?

@fbiville Sure, I will check with pre-release and test it with my use-case and will provide a feedback. Thanks.

@rohitbatta have you had a chance to try the pre-release?

|Hi @fbiville ,
I have tested the new version 4.19.0 locally and i found that following driver classes are not found anymore.
org.neo4j.jdbc.boltrouting.BoltRoutingNeo4jDriver and org.neo4j.jdbc.bolt.BoltDriver
Exception:
`Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.zaxxer.hikari.HikariDataSource]: Factory method 'dataSource' threw exception; nested exception is java.lang.IllegalStateException: Cannot load driver class: org.neo4j.jdbc.bolt.BoltDriver
Caused by: java.lang.IllegalStateException: Cannot load driver class: org.neo4j.jdbc.bolt.BoltDriver`
If I include following dependency to have jdbc-bolt driver.  implementation 'org.neo4j:neo4j-jdbc-bolt:5.0.0'
This result in following exception.
The called method's class, org.neo4j.driver.Values, is available from the following locations:
jar:file:/.../.gradle/caches/modules-2/files-2.1/org.neo4j/neo4j-jdbc-bolt/5.0.0/4077de6e53f6e6d3eb110dcf7251a8eeb734152e/neo4j-jdbc-bolt-5.0.0.jar!/org/neo4j/driver/Values.class
jar:file:/.../.gradle/caches/modules-2/files-2.1/org.neo4j.driver/neo4j-java-driver/4.4.11/b854f8e7f0f2ab253fb4f98d1cdf3129eaba5696/neo4j-java-driver-4.4.11.jar!/org/neo4j/driver/Values.class

The called method's class hierarchy was loaded from the following locations:
org.neo4j.driver.Values: file:/.../.gradle/caches/modules-2/files-2.1/org.neo4j/neo4j-jdbc-bolt/5.0.0/4077de6e53f6e6d3eb110dcf7251a8eeb734152e/neo4j-jdbc-bolt-5.0.0.jar

Action:
Correct the classpath of your application so that it contains compatible versions of the classes org.springframework.data.neo4j.core.convert.CypherTypes and org.neo4j.driver.Values

Hello @fbiville ,
If i include implementation 'org.neo4j:neo4j-jdbc-driver:4.0.9' this dependency, then it seems to me working for use-case.
Following, I have in my build.gradle to make it working.
    implementation 'org.springframework.boot:spring-boot-starter-jdbc'
    implementation 'org.liquibase:liquibase-core:4.19.0'
    implementation 'org.liquibase.ext:liquibase-neo4j:4.19.0'
    implementation 'org.neo4j:neo4j-jdbc-driver:4.0.9'```

@fbiville , thanks for your response. I will check the reference documentation and will provide you an update soon.


puppet-lint issues

these warnings are generated using the Puppet4 recommendations: http://www.camptocamp.com/en/actualite/getting-code-ready-puppet-4/
grafana/manifests/params.pp - WARNING: variable assigned to the empty string on line 23
grafana/manifests/init.pp - WARNING: class inheriting from params class on line 92

I believe this is a false-positive warning and may be entirely obviated by the next major release...
using a declaration like the following (taken from the README):
class { 'grafana':
  install_dir  => '/usr/local',
  datasources  => {
    'graphite' => {
      'type'    => 'graphite',
      'url'     => 'http://<IP_ADDRESS>',
      'default' => 'true'
    },
    'elasticsearch' => {
      'type'      => 'elasticsearch',
      'url'       => 'http://<IP_ADDRESS>:9200',
      'index'     => 'grafana-dash',
      'grafanaDB' => 'true',
    },
  }
}

Puppet-Lint warns: "[quoted_booleans] quoted boolean value found" for the  'default' => 'true' and 'grafanaDB' => 'true' lines. I suspect this is a false-positive because these are strings being interpreted later.

Hi @neoice thanks for opening this. Let me address your points in turn.
grafana/manifests/params.pp - WARNING: variable assigned to the empty string on line 23

I'm not overly concerned with this one as there is no logic wrapped around whether the admin password is an empty string, instead it's just a straight substitution in config.js.
grafana/manifests/init.pp - WARNING: class inheriting from params class on line 92

This check is only present to ensure backwards compatibility with Puppet <= 2.6.2, and in fact use of a params class for supplying module defaults is accepted per the style guide.
"Class inheritance should only be used for myclass::params parameter defaults. Other use cases can be accomplished through the addition of parameters or conditional logic."
How are you running puppet-lint? This check is specifically disabled in the Rakefile so if you are using bundle exec rake test the lint checks will pass.
[quoted_booleans] quoted boolean value found

You are correct this is a false-positive, however unquoting the boolean does not impact functionality and in fact the default datasource configuration was corrected in a recent commit. The README should be updated to reflect this.
Thanks!

@neoice I've published a new version of the module supporting Grafana 2.x and don't feel there's anything here left to action as the module's behavior has changed. Thoughts?

I think this has been fixed by https://github.com/voxpupuli/puppet-grafana/pull/1.


401 Unauthorized error when posting.

I am able to make get calls with it successfully but when I try to post it gives me 401 invalid signature error.
my code for Ionic 2.
var WooCommerce = new WooCommerceAPI({
url: 'http://vishaljoshi.in/woocommerce',
consumerKey: 'ck_',
consumerSecret: 'cs_',
wpApi: true,
version: 'wc/v1',
wpAPIPrefix: 'wp-json'
})
WooCommerce.post('customers', this.data, function(err, data, res) {
console.log(res);
});
// Am i missing something here?

@rishab121 what was the issue? i am facing the same problem can you please guide me please?

I wasn't able to resolve issue with the node.js wrapper. so instead of directly posting data from Ionic to woocommerce; I posted the data from Ionic to python api (bottle) and then used python wrapper to post data to woocommerce server.


Force SSL not working with non-standard port

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

Yes

Are you sure you're not using someone else's docker image?

Yes

Have you searched for similar issues (both open and closed)?

Yes

Describe the bug

Similar to (this question)[https://serverfault.com/questions/338700/redirect-http-example-com12345-to-https-example-com12345-in-nginx]
Nginx Proxy Manager Version

2.9.9
To Reproduce
Steps to reproduce the behavior:

While create docker container, bind container's 443 port to any port other than 443 on host, like 60443
Create SSL certificates, create a proxy server and enable SSL and force-SSL
Request http://server_name:60443. You'll get an 400 Error 'The plain HTTP request was sent to HTTPS port';

Expected behavior

Get a 302 redirect to  https://server_name:60443
Screenshots

Operating System

Additional context

Solution is in the link too. Maybe 'error_page 497' is better than 'if() redirect'

This sounds like it is best solved by hosting nginx in the cloud and routing traffic back to your home network using an overlay network service like tailscale or zerotier.
Normal http -> https redirection works by you entering http://my.domain:80 and being redirected to https://my.domain:443, which wouldn't work if you enter the wrong port.

does force ssl even work with the standard ports? At my instance, with subdomains, that isn't working

@ysslang Have you solved it? I have encountered the same situation.

@ysslang Have you solved it? I have encountered the same situation.

我最后是这么解决的！
error_page 497 301 =301 https://your_domain:your_port$request_uri;

@ysslang Have you solved it? I have encountered the same situation.

This is how I finally solved it! error_page 497 301 =301 https://your_domain:your_port$request_uri;

please can you explain better?
My isp block a port range, so i open 443 to 32763
80 to 32764
How can I setup in proxy manager?


Feature request: Hide bullets in insert mode

As title says, so that in normal mode:
 ○ Development

And in insert:
## Development

I have this planned :+1:


add ocm_cluster_rosa_classic data source to get cluster id/name, stat…

add ocm_cluster_rosa_classic data source to get cluster id/name, state and version of existing cluster

@vamsinm this should be covered as part of terraform import command...

@bardielle can you please elaborate?  it does not make sense to run import command in to terraform state just to be able to lookup. any reservations why we can not have data source?

@vamsinm  This repository is deprecated, please open the same PR in the new repository - https://github.com/terraform-redhat/terraform-provider-ocm


Add javascript + ruby output to "Add another failing test"

As described in #238, the js as well as ruby version of this section was incomplete.
Stepped through the tutorial locally and added the output.

Hi @hanneskaeufler,
Thanks for your making your first contribution to Cucumber, and welcome to the Cucumber committers team! You can now push directly to this repo and all other repos under the cucumber organization! 🍾
In return for this generous offer we hope you will:

✅ Continue to use branches and pull requests. When someone on the core team approves a pull request (yours or someone else's), you're welcome to merge it yourself.
💚 Commit to setting a good example by following and upholding our code of conduct in your interactions with other collaborators and users.
💬 Join the community Slack channel to meet the rest of the team and make yourself at home.
ℹ Don't feel obliged to help, just do what you can if you have the time and the energy.
🙋 Ask if you need anything. We're looking for feedback about how to make the project more welcoming, so please tell us!

On behalf of the Cucumber core team,
Aslak Hellesøy
Creator of Cucumber

Thanks for picking this up @hanneskaeufler! Please let us know if you're interested in helping out more?
You can join us on Slack in the #docs channel.


Use Previously Authenticated Details to Re-Login (Application Use)

The OAuth2 wiki page doesn't go into much detail on how to re-gain access to the previously logged-in user without having to have the user re-allow the application access to their profile.
Currently, I ask the user for a username + password, and if the UserChallengeTask completes correctly, I store the two values to re-authenticate on the next time the application is opened. I can create a new credentials object using the username + password, but how do you tell the RedditClient to log in using those details and skip the permissions screen (that they have already accepted)?
Thanks!

Assuming you're using version <IP_ADDRESS> and you request a refresh token when you call OAuthHelper.getAuthorizationUrl(), you can use OAuthHelper.setRefreshToken(String) followed by OAuthHelper.refreshToken(Credentials) to retrieve another valid access token.

Thank you for the quick reply!
So I should store the username, password, and access token, then do OAuthHelper.setRefreshToken(storedtoken) and .refreshToken(Credentials.installedApp(username, password, appkey, url)?

Issue referenced: #51


give a way to access the stale cache

an update for #181 :)

Codecov Report

Merging #216 into master will decrease coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #216      +/-   ##
==========================================
- Coverage   90.61%   90.58%   -0.03%
==========================================
  Files          15       15
  Lines         714      712       -2
==========================================
- Hits          647      645       -2
  Misses         58       58
  Partials        9        9

Impacted Files
Coverage Δ

bigcache.go
99.10% <ø> (ø)

shard.go
91.22% <100.00%> (-0.08%)
:arrow_down:

Continue to review full report at Codecov.

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

@cristaloleg this looks good to me. I think it would be good to version bump after merging this because it sets an explicit value, so it's technically a minor API change.
@flisky can you please rebase and then re-request a review?


Added link to iPad 6th gen spec

Added missing link to iPad 6th generation spec.

Oops, wrong file


Unhandled Exception on install

This pops up when I try to install EnhancedDiscord.
My computer is running Windows 7 x64, and my Discord install is completely vanilla.
No clue how to fix this. :/

Try updating .net from here: https://dotnet.microsoft.com/download/dotnet-framework-runtime
If that doesn't work make sure you don't have any Windows updates pending.

I do have updates pending! I will install those and report back if I still have problems.

Needed to install updates. That's it.


AWS amplify deploy completes successfully but error 404 on access to website

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
dqcry7h9xp57z
AWS Region
us-east-1
Amplify Hosting feature
Deployments, SSR
Frontend framework
Next.js
Next.js version
13.5.3
Next.js router
App Router
Describe the bug
Deploys successfully but no content is actually pushed to the website. Domain name and DNS are confirmed to be valid and the page responds to dns queries sent by route53. Updated platform to "platform": "WEB_DYNAMIC" with no result.
Expected behavior
Expect content to be served correctly during deployment and appear when navigating to the site.
Reproduction steps

Deploy with AWS Amplify.
Navigate to domain name https://coal-reality.me/
??????

Build Settings
version: 1
frontend:
  phases:
    preBuild:
      commands:
        - cd coal-reality
        - npm ci
    # IMPORTANT - Please verify your build commands
    build:
      commands:
        - npm run build
  artifacts:
    # IMPORTANT - Please verify your build output directory
    baseDirectory: coal-reality/.next/
    files:
      - '**/*/*/*'
  cache:
    paths:
        - 'coal-reality/node_modules/**/*' # Cache `node_modules` for faster `yarn` or `npm i`
        - 'coal-reality/.next/cache/**/*' # Cache Next.js for faster application rebuilds

backend:

Log output

# Put your logs below this line
No backend:

Frontend:
                                 # Starting phase: preBuild
                                 # Executing command: cd coal-reality
2023-09-28T11:27:17.365Z [INFO]: # Executing command: npm ci
2023-09-28T11:27:41.179Z [INFO]: added 498 packages, and audited 499 packages in 24s
2023-09-28T11:27:41.182Z [INFO]: 110 packages are looking for funding
                                 run `npm fund` for details
                                 found 0 vulnerabilities
2023-09-28T11:27:41.201Z [INFO]: # Completed phase: preBuild
                                 # Starting phase: build
2023-09-28T11:27:41.201Z [INFO]: # Executing command: npm run build
2023-09-28T11:27:41.549Z [INFO]: ><EMAIL_ADDRESS>build
                                 > next build
2023-09-28T11:27:42.198Z [INFO]: Creating an optimized production build ...
2023-09-28T11:27:45.111Z [WARNING]: Warning: For production Image Optimization with Next.js, the optional 'sharp' package is strongly recommended. Run 'npm i sharp', and Next.js will use it automatically for Image Optimization.
                                    Read more: https://nextjs.org/docs/messages/sharp-missing-in-production
2023-09-28T11:27:57.438Z [WARNING]: (node:965) [DEP_WEBPACK_MODULE_UPDATE_HASH] DeprecationWarning: Module.updateHash: Use new ChunkGraph API
                                    (Use `node --trace-deprecation ...` to show where the warning was created)
2023-09-28T11:28:00.089Z [INFO]: ✓ Compiled successfully
2023-09-28T11:28:00.090Z [INFO]: Linting and checking validity of types ...
2023-09-28T11:28:02.468Z [INFO]: ./app/coal-mines/CoalMineInstance.tsx
                                 24:17  Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
                                 67:25  Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
                                 67:25  Warning: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images.  jsx-a11y/alt-text
                                 ./app/counties/CountiesInstance.tsx
                                 24:17  Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
                                 67:25  Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
                                 67:25  Warning: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images.  jsx-a11y/alt-text
                                 ./app/healthcare-providers/HealthcareProvidersInstance.tsx
                                 24:17  Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
                                 67:25  Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
                                 67:25  Warning: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images.  jsx-a11y/alt-text
                                 info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
2023-09-28T11:28:04.022Z [INFO]: Collecting page data ...
2023-09-28T11:28:04.960Z [INFO]: Generating static pages (0/18) ...
2023-09-28T11:28:05.146Z [INFO]: Generating static pages (4/18)
2023-09-28T11:28:05.218Z [INFO]: Generating static pages (8/18)
2023-09-28T11:28:05.305Z [INFO]: Generating static pages (13/18)
2023-09-28T11:28:05.367Z [INFO]: ✓ Generating static pages (18/18)
2023-09-28T11:28:05.379Z [INFO]: Finalizing page optimization ...
2023-09-28T11:28:05.383Z [INFO]:
2023-09-28T11:28:05.393Z [INFO]: Route (app)                                      Size     First Load JS
                                 ┌ ○ /                                            181 B          79.6 kB
                                 ├ ○ /_not-found                                  878 B          80.3 kB
                                 ├ ○ /about                                       23.9 kB         103 kB
                                 ├ ○ /coal-mines                                  3.59 kB        89.8 kB
                                 ├ ○ /coal-mines/coal-mine-1                      1.11 kB         111 kB
                                 ├ ○ /coal-mines/coal-mine-2                      1.13 kB         111 kB
                                 ├ ○ /coal-mines/coal-mine-3                      1.12 kB         111 kB
                                 ├ ○ /counties                                    3.69 kB        89.9 kB
                                 ├ ○ /counties/counties-1                         1.24 kB         111 kB
                                 ├ ○ /counties/counties-2                         1.28 kB         111 kB
                                 ├ ○ /counties/counties-3                         1.4 kB          111 kB
                                 ├ ○ /healthcare-providers                        3.93 kB        90.1 kB
                                 ├ ○ /healthcare-providers/healthcare-provider-1  1.13 kB         111 kB
                                 ├ ○ /healthcare-providers/healthcare-provider-2  1.3 kB          111 kB
                                 └ ○ /healthcare-providers/healthcare-provider-3  1.31 kB         111 kB
                                 + First Load JS shared by all                    79.5 kB
                                 ├ chunks/864-975492c2867153e8.js               26.6 kB
                                 ├ chunks/fd9d1056-5b3ee06fda64bfbf.js          50.8 kB
                                 ├ chunks/main-app-f96c3abf373a3af4.js          221 B
                                 └ chunks/webpack-d2c94483f6ce9836.js           1.87 kB
2023-09-28T11:28:05.394Z [INFO]: ○  (Static)  automatically rendered as static HTML (uses no initial props)
2023-09-28T11:28:05.529Z [INFO]: # Completed phase: build
2023-09-28T11:28:05.531Z [INFO]: ## Build completed successfully
2023-09-28T11:28:05.532Z [INFO]: # Starting caching...
2023-09-28T11:28:05.544Z [INFO]: # Creating cache artifact...
2023-09-28T11:28:18.716Z [INFO]: # Created cache artifact
2023-09-28T11:28:18.902Z [INFO]: # Uploading cache artifact...
2023-09-28T11:28:22.556Z [INFO]: # Uploaded cache artifact
2023-09-28T11:28:22.772Z [INFO]: # Caching completed
2023-09-28T11:28:22.779Z [INFO]: # No custom headers found.
2023-09-28T11:28:22.805Z [INFO]: # Starting build artifact upload process...
2023-09-28T11:28:25.795Z [INFO]: # Uploading build artifact '__artifacts.zip'...
2023-09-28T11:28:25.839Z [INFO]: # Uploading build artifact '__artifactsHash.zip'...
2023-09-28T11:28:26.287Z [INFO]: # Build artifact upload completed
2023-09-28T11:28:26.287Z [INFO]: # Starting environment caching...
2023-09-28T11:28:26.288Z [INFO]: # Uploading environment cache artifact...
2023-09-28T11:28:26.363Z [INFO]: # Uploaded environment cache artifact
2023-09-28T11:28:26.363Z [INFO]: # Environment caching completed
Terminating logging...

Deploy:
2023-09-28T11:28:33 [INFO]: Beginning deployment for application dqcry7h9xp57z, branch:main, buildId<PHONE_NUMBER>
2023-09-28T11:28:33 [INFO]: Got archive: 31496477 bytes
2023-09-28T11:28:37 [INFO]: Deployment complete

Additional information
Gitlab repo:
https://gitlab.com/emily.yue/group-3-swe-project

I had the same problem and I have fixed it downgrading NextJJ to 13.4.12

my issue was relating to the directory structure of my build file


how to go to definition with react className attribute

VSCode Version: 1.11.2
OS Version:macos 10.12.1

how to locate to scss file when I use go to definition with className in *.jsx or *.tsx file
render() {         return (             <div className="app" >             </div>           )     }

This is not supported out-of-the box. But https://github.com/Zignd/HTML-CSS-Class-Completion tries to solve that.

Duplicate of #15568

Does this issue have a solution so far?

@jasminecjc  No but we are tracking it with #15568
There also also some extensions that may provide this functionality


Create MultipleH1_2.md

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Docset5/Test/MultipleH1_2.md
:white_check_mark:Succeeded

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


Obelisk lib unpack errors (Rhyolite, GHC 8.10)

In an Obelisk+Rhyolite project that uses GHC 8.10.7, builds succeed when .obselisk/impl is packed and fail when unpacked.  I am getting errors like the following.  In different experiments, I have seen this error for different Obelisk lib projects.
error: builder for '/nix/store/3mnd3jf3kbflw8a9716bp87py7scqzgd-tabulation-<IP_ADDRESS>.drv' failed with exit code 1;
       last 5 log lines:
       > setupCompilerEnvironmentPhase
       > Build with /nix/store/26k0ndap2lmh08l9x3ah8yhmbkzm5qj3-ghc-8.10.7.
       > unpacking sources
       > unpacking source archive /home/tcard/tmp/obelisk-rhyolite-810-issue/.obelisk/impl/lib/tabulation
       > do not know how to unpack source archive /home/tcard/tmp/obelisk-rhyolite-810-issue/.obelisk/impl/lib/tabulation
       For full logs, run 'nix log /nix/store/3mnd3jf3kbflw8a9716bp87py7scqzgd-tabulation-<IP_ADDRESS>.drv'.

Repository
I created a minimal example in the TravisCardwell/obelisk-rhyolite-810-issue repository.  I setup this repository as follows.
  Perhaps there is something in my cache that allows this, but I am not sure.
$ ob shell
shell$ exit

Unpack Obelisk:
$ nix-thunk unpack .obelisk/impl

With Obelisk unpacked, I get an error like above when running ob run or ob shell.
$ ob shell
error: builder for '/nix/store/3mnd3jf3kbflw8a9716bp87py7scqzgd-tabulation-<IP_ADDRESS>.drv' failed with exit code 1;
       last 5 log lines:
       > setupCompilerEnvironmentPhase
       > Build with /nix/store/26k0ndap2lmh08l9x3ah8yhmbkzm5qj3-ghc-8.10.7.
       > unpacking sources
       > unpacking source archive /home/tcard/tmp/obelisk-rhyolite-810-issue/.obelisk/impl/lib/tabulation
       > do not know how to unpack source archive /home/tcard/tmp/obelisk-rhyolite-810-issue/.obelisk/impl/lib/tabulation
       For full logs, run 'nix log /nix/store/3mnd3jf3kbflw8a9716bp87py7scqzgd-tabulation-<IP_ADDRESS>.drv'.

@TravisCardwell
I am quite sure that this is not a regression in Obelisk, and does not need the rhyolite or GHC 8.10 to be used. I have hit the same issue a long time back while using GHC 8.6. I think this is due to something weird going on with Obelisk trying to "interpret" (ie not nix build) the unpacked dependencies. But those dependencies are already being used by other packed dependencies.
My workaround for this was to use --no-interpret for each unpacked dependency.
As I was working on reflex-dom, I did
ob run --no-interpret .obelisk/impl/dep/reflex-platform/haskell-overlays/reflex-packages/dep/reflex-dom/chrome-test-utils --no-interpret .obelisk/impl/dep/reflex-platform/haskell-overlays/reflex-packages/dep/reflex-dom/reflex-dom-core
For your case it should be (although I haven't tested this)
ob shell --no-interpret .obelisk/impl/lib/tabulation

Thank you, @dfordivam!
I was indeed able to avoid the errors in the minimal repository using the following command:
$ ob shell \
    --no-interpret .obelisk/impl/lib/tabulation \
    --no-interpret .obelisk/impl/lib/executable-config/inject \
    --no-interpret .obelisk/impl/lib/executable-config/lookup \
    --no-interpret .obelisk/impl/lib/route \
    --no-interpret .obelisk/impl/lib/frontend

BTW, I wrote some scripts to automate this.
ob-run:
#!/usr/bin/env bash

set -o errexit
set -o nounset
set -o pipefail
#set -o xtrace

NO_INTERPRET_OPTS=()
if [ -d ".obelisk/impl/lib" ] ; then
  while IFS= read -r -d $'\0'; do
    NO_INTERPRET_OPTS+=("--no-interpret" "${REPLY}")
  done < <(find ".obelisk/impl/lib" -maxdepth 1 -mindepth 1 -type d -print0 | sort -z)
fi

exec ob run "${NO_INTERPRET_OPTS[@]}" "${@}"

ob-shell:
#!/usr/bin/env bash

set -o errexit
set -o nounset
set -o pipefail
#set -o xtrace

NO_INTERPRET_OPTS=()
if [ -d ".obelisk/impl/lib" ] ; then
  while IFS= read -r -d $'\0'; do
    NO_INTERPRET_OPTS+=("--no-interpret" "${REPLY}")
  done < <(find ".obelisk/impl/lib" -maxdepth 1 -mindepth 1 -type d -print0 | sort -z)
fi

exec ob shell "${NO_INTERPRET_OPTS[@]}" "${@}"


Restrict range on numeric values

The builder has some neat methods already for restricting Time, Date and String ranges.
I just ran into an issue where the database only accepts numbers within a certain range. Since my POJO has dozens of fields it is not feasable to set them each. I should be able to specify a range for double and int values in the EnhancedRandomBuilder.

Hi,
Have you tried to use one of the range randomizers ? Something like:
EnhancedRandom enhancedRandom = aNewEnhancedRandomBuilder()
                .randomize(Double.class, new DoubleRangeRandomizer(1, 10))
                .build()

Does this help?
Kr
Mahmoud

Will this work also if the field is a primitive type?

Yes, it should work fine.
You can also be more precise when specifying the type. Here is an example: https://github.com/benas/random-beans/blob/master/random-beans/src/test/java/io/github/benas/randombeans/randomizers/range/IntegerRangeRandomizerTest.java#L86

Thanks, this is great!
The only suggestion I have remaining is to include this feature in the README.md for future users :)
Keep up the awesome work!


Update sbt to 0.13.16; add Scala 2.12 support.

To clean, test, and build Scala 2.11 and Scala 2.12 versions:
% sbt +clean +test +publishLocal

You need to be running Java 8 to build the 2.12 version.

retest this please

retest this please

Could someone approve this please? I'd like to get it into next week's release.


New Deployment Failed - adminweb

Describe the bug
A clear and concise description of what the bug is.
New deployment failed upon executing azd up. The adminweb was not there in the resource group.
Expected behavior
A clear and concise description of what you expected to happen.
How does this bug make you feel?
Share a gif from giphy to tells us how you'd feel

Debugging information
Steps to reproduce
Steps to reproduce the behavior:

Run azd up
See error:

Deploying services (azd deploy)
(x) Failed: Deploying service adminweb
ERROR: getting target resource: resource not found: unable to find a resource tagged with 'azd-service-name: adminweb'. Ensure the service resource is correctly tagged in your infrastructure configuration, and rerun provision
ERROR: error executing step command 'deploy --all': getting target resource: resource not found: unable to find a resource tagged with 'azd-service-name: adminweb'. Ensure the service resource is correctly tagged in your infrastructure configuration, and rerun provision
Screenshots
If applicable, add screenshots to help explain your problem.
Logs
If applicable, add logs to help the engineer debug the problem.

Tasks
To be filled in by the engineer picking up the issue

[ ] Task 1
[ ] Task 2
[ ] ...

Thanks for the bug report @mirojs. Can you check your .azure//.env file and tell me what the value of the AZURE_APP_SERVICE_HOSTING_MODEL variable is?

Ok, if you're deploying from your clone of the repo, please follow the instructions at https://github.com/Azure-Samples/chat-with-your-data-solution-accelerator/blob/main/docs/LOCAL_DEPLOYMENT.md.
Specifically, you need to run
azd env set AZURE_APP_SERVICE_HOSTING_MODEL code

before azd up.

@mirojs can you confirm whether that fixed your problem?

@superhindupur For the previous deployed one, after using azd down -> azd up, it worked again.
For brand new deployment, it would prompt
"ERROR: listing accounts: listing subscriptions: failed to load subscriptions from tenant 'Default Directory' : reauthentication required, run azd auth login --scope https://management.azure.com//.default to log in; failed to load subscriptions from tenant '---' : reauthentication required, run azd auth login --scope https://management.azure.com//.default to log in". And the reauthentication didn't work.

@superhindupur For the previous deployed one, after using azd down -> azd up, there's an error "ERROR - Container web-...-admin_... for site web-...-admin has exited, failing site start
"

@superhindupur Managed For brand new deployment, azd auth logout -> azd auth login -> azd up -> ERROR: error executing step command 'package --all': failed packaging service 'adminweb': failed invoking event handlers for 'prepackage', 'prepackage' hook failed with exit code: '127', Path: '/tmp/azd-prepackage-1333944515.sh'. : exit code: 127, stdout: , stderr: /tmp/azd-prepackage-1333944515.sh: 5: poetry: not found

Looks like you might not be running with a devcontainer. Are you following the steps at https://github.com/Azure-Samples/chat-with-your-data-solution-accelerator/blob/main/docs/LOCAL_DEPLOYMENT.md exactly?

@superhindupur Sorry, I git clone from the  repo first and then followed step 4  to 6 in the link since I need a private repo for the following code update

Ok,. Are you using VSCode? You will need to install the DevContainers extension for VSCode and open the Chat With Your Data project inside a DevContainer (https://code.visualstudio.com/docs/devcontainers/containers#_quick-start-open-an-existing-folder-in-a-container). Then you can follow https://github.com/Azure-Samples/chat-with-your-data-solution-accelerator/blob/main/docs/LOCAL_DEPLOYMENT.md from step 4.

@superhindupur I'm not using VSCode but I could give it a try if that a must. In the meanwhile, how should the public repo update be synced and merged smoothly in that case?

There's another option. If you aren't using VSCode (and therefore can't use the devcontainers extension), follow https://github.com/Azure-Samples/chat-with-your-data-solution-accelerator/blob/main/docs/NON_DEVCONTAINER_SETUP.md
You can ignore the VSCode section, but install all the other mentioned tools. In your error message, you were missing 'poetry', which you will need to install (https://python-poetry.org/docs/)

@superhindupur It's deploying! One poetry away, thanks a million!
BTW, for one previous deployed App (git clone -->azd up), which was broken (container apps shown in resource group) following the public repo update, I did azd down --purge --> azd env set AZURE_APP_SERVICE_HOSTING_MODEL code --> azd up last night and the deployment went through but adminweb app could not be started now with "ERROR - Container web-...-admin_... for site web-...-admin has exited, failing site start".
Any clue why container was mentioned in the error message? Anything else I could do to clean up further without starting over everything from the very beginning? Thanks.

@superhindupur After deploying for a 3rd time, it started to work by itself. Not sure why. And thanks for the help!

@ross-p-smith please, thanks for the help!


[BUG] - Seems to be broken with vue 3.5

Describe the bug
With the latest release of 3.5, there is now an error when building components.
Building for production...C:\App\src\SiteWidget\node_modules\@unplugin-vue-ce\sub-style\index.cjs:110
  if (isApplyStylesIdentifier && isVueElementIdentifier && isBaseClassIdentifier && node.type === "CallExpression" && node.callee.type === "MemberExpression" && node.callee.property.name === "appendChild" && node.callee.object.property.name === "shadowRoot") {

TypeError: Cannot read properties of undefined (reading 'name')
    at injectApiCustomElement (C:\App\src\SiteWidget\node_modules\@unplugin-vue-ce\sub-style\index.cjs:110:237)
    at Object.enter (C:\App\src\SiteWidget\node_modules\@unplugin-vue-ce\sub-style\index.cjs:146:7)
    at d.visit (C:\App\src\SiteWidget\node_modules\estree-walker-ts\index.cjs:1:1360)
    at d.visit (C:\App\src\SiteWidget\node_modules\estree-walker-ts\index.cjs:1:1794)
    at d.visit (C:\App\src\SiteWidget\node_modules\estree-walker-ts\index.cjs:1:1756)
    at d.visit (C:\App\src\SiteWidget\node_modules\estree-walker-ts\index.cjs:1:1794)
    at d.visit (C:\App\src\SiteWidget\node_modules\estree-walker-ts\index.cjs:1:1756)
    at d.visit (C:\App\src\SiteWidget\node_modules\estree-walker-ts\index.cjs:1:1794)
    at x (C:\App\src\SiteWidget\node_modules\estree-walker-ts\index.cjs:1:3444)
    at injectVueRuntime (C:\App\src\SiteWidget\node_modules\@unplugin-vue-ce\sub-style\index.cjs:134:36)

Node.js v21.7.3

Reproduction
No response
System Info
No response
Used Package Manager
npm
Validations

[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a unplugin-vue-ce issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs instead.
[X] The provided reproduction is a minimal reproducible example of the bug.

I am glad that Vue 3.5 supports more features of custom elements. This repository should have completed its mission (a transitional solution before Vue supports more features for custom elements), so this repository should not support 3.5.


Can't login with Google

My Trello account is set up with my institution's gmail account, and the SSO does not work right

But I was able to log in with a browser and create a password for my account and then login with my username and password. Thanks for developing this.


Pagination or search function /admin/product

The list is endless right now. There needs to be a way to efficiently go through the list to find your items.

Will be fixed in #49


proxying to an apache virtual host domain takes arounds 5 seconds to resolve

Hi,
If I proxy to localhost is very fast (100ms). But proxying to something like mysite.local takes around 5 seconds.
This delay does not happen if I load mysite.local directly from browser, so does not seem to be an apache misconfiguration.
Apache/2.4.9 (Unix)
Any idea ?

I have same problem with nginx. Was looking for solutions and found this issue.

This may or may not be related but I've noticed that the proxy seems to be resolving the domain and sending the request to the IP address. I haven't noticed a problem with the speed of this but I noticed it because the apache server receiving the request doesn't route the request through the virtual host record for the domain.


Abstract Routers

Move functionality into their own routers.

Followed this article a bit.
https://wanago.io/2018/12/03/typescript-express-tutorial-routing-controllers-middleware/


Problem with multithreading

in readme.md

Please make note that the ApiClient inheirits of IDisposable, so that you dispose of it when you're done with it.

consider this code:
await Parallel.ForEachAsync(Enumerable.Range(1, 100), async (i, token) =>
{
    try
    {
        using var apiClient = new ApiClient("MY_API_KEY", "MY_EMAIL");
        var file = await apiClient.GetModAsync(238222);
    }
    catch (Exception e)
    {
        Console.WriteLine(e);
    }
});

it pops out some exceptions like this:
System.Threading.Tasks.TaskCanceledException: OperationCanceled
 ---> System.IO.IOException: net_io_read
 ---> System.ObjectDisposedException: ObjectDisposed_Generic
ObjectDisposed_ObjectName_Name, System.Net.Sockets.NetworkStream
   at System.Net.Sockets.NetworkStream.<ThrowIfDisposed>g__ThrowObjectDisposedException|63_0()
.......
   at CurseForge.APIClient.ApiClient.GET[T](String endpoint, ValueTuple`2[] queryParameters) in D:\Git\CurseForge.APIClient\ApiClient.cs:line 79
   at CurseForge.APIClient.ApiClient.GetModAsync(UInt32 modId) in D:\Git\CurseForge.APIClient\Mods.cs:line 22
   at Program.<>c.<<<Main>$>b__0_0>d.MoveNext() in C:\Users\cyl18\source\repos\TestDotNet6\TestDotNet6\Program.cs:line 15

in ApiClient.cs, the _httpClient is static, which means a single instance disposes would affect all existing instances
https://github.com/CurseForgeCommunity/.NET-APIClient/blob/05caa75f202a3c483c8abbd65bb3be1dc97a911e/ApiClient.cs#L13
and a static HttpClient would cause extra problems like all ApiClient will use the same ApiKey
i have made a simple pull request to fix this problem :) (#2)

Well, the point of the client, is to use a single API key. (Which could be handled with multiple instances as well, but that's beside the point)
The problem with creating a new per instance, could be port exhaustion.
But I could redo it to use IHttpClientFactory, which will handle pooling internally, while still allowing multithreading and avoid port exhaustion. Will work on it during lunch.
Thanks for notifying me of this though!


PDF/A3 conversion not valid

I tried to convert a PDF/A-1a file to PDF/A-3a using mustang. According to http://www.mustangproject.org/use.html#pdfa3, this conversion can be done using the command line.
As a result, I created a new PDF file. This PDF is not valid according to verapdf, because "The value of pdfaid:part shall be the part number of ISO 19005 to which the file conforms.".
The result of exiftool shows, that the part is sill set to 1 instead of 3.
So, is it possible to set the correct part number within the conversion process?

i can reproduce the issue

The steps to reproduce were: download mustangproject.org/files/MustangGnuaccountingBeispielRE-20170509_505blanko.pdf as invoice.pdf, run ´java -jar mustang-1.5.4.jar -a´, the resulting invoice.a3.pdf remains PDF/A-1.
That was caused because the non-ZUGFeRD load process did not invoke my "prepareDocument" at all, which would have changed the metadata.
That's now fixed, please confirm with the interim version on http://www.mustangproject.org/deploy/mustang-1.5.5-SNAPSHOT.jar
VeraPDF has apparently improved and now also shows errors which went undetected before. To follow up on these errors is a different issue, I created #64 for this.

Thank you for you commit.
I checked out the latest mustang version and retried to convert a PDF/A-1A file (see procedure above).
Today, I get a PDF/A-3U instead of a PDF/A-3A file! Furthermore, the XMP Schemas is empty.
To reproduce this information, you can use exiftool: https://www.sno.phy.queensu.ca/~phil/exiftool/
here are my results
exiftool -xmp:all pdf1afile.pdf

Part                            : 1
Conformance              : A

exiftool -xmp:all convertedpdf3afile.pdf

Part                            : 3
Conformance              : U
Schemas                     :

So, the Schemas XMP Property is new and has not a correct value (see #64) and the conformance level is not right.
Could you reopen this issue again?


Task sorter v0.0.2

Sort tasks in a note by priority (e.g. !, !!, !!! -- the more exclamations, the higher the priority -- also works with todo.txt (A), (B) etc.)
My personal workflow: Sweep tasks with /sw7 and then sort tasks with /ts (see my /sw7 pull request also)
Ignores indents for now, but once I understand more about @EduardMe's heading-indent thinking, I can get it back in there.
Need to work on the @context and #hashtag sorting next.
@jgclark @EduardMe Look forward to comments

I think @dwertheimer, "indent" values are only available on tasks and bullets because these are the only items where you can indent the full paragraph. Plain text, headings, etc are not 'indentable' like tasks. You only get the first line indented. There is a discussion on Discord about indenting all fully. Then it would make sense to set an indent level everywhere.
Let me know if this helps or if I mixed up something.

Thx @EduardMe. When you get a moment, pls try out my PRs for the task sweeper and the sorter.
Task sweeper sweeps the last #H1 over with an indented task. The sorter, by design, just sorts tasks and ignores text and titles.  So at some point, we should come up with a strategy for how to do the sorting when there are indents and titles. The base case is simple but let's say you sweep multiple indented tasks of differing priorities to today's note. They are all now under the #H1. But when you sort them, what should happen?

Thanks, will check it out. Generally, indented tasks should stay below
their parent task, but that's not easy to implement (searching for the
parent) and then to sort indented tasks only between the other indented
tasks under the same parent. Because there might be tasks which are further
indented into level 2, 3, etc. I wanted to code this somehow, but couldn't
figure out a simple way to get the relationships right.
On Mon, Jun 28, 2021 at 12:08 PM David Wertheimer @.***>
wrote:

Thx @EduardMe https://github.com/EduardMe. When you get a moment, pls
try out my PRs for the task sweeper and the sorter.
Task sweeper sweeps the last #H1 over with an indented task. The sorter,
by design, just sorts tasks and ignores text and titles. So at some point,
we should come up with a strategy for how to do the sorting when there are
indents and titles. The base case is simple but let's say you sweep
multiple indented tasks of differing priorities to today's note. They are
all now under the #H1. But when you sort them, what should happen?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NotePlan/plugins/pull/23#issuecomment-869859491, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZCAYXPDEQXWGDRFYME74LTVCUBZANCNFSM47M4JEFA
.

I've only checked which files have been updated (given the issues reported in #22).
So not reviewed, or tested, but committing as requested.


When jointly mapping different modal features to the same semantics, which layer of the hidden layer is more appropriate to select

Now I have extracted the image pre-training features using clip, but I don't know how to choose which layer of mert's features is more suitable for the

Hi, I think the layer selection really depends on the task you are working on. If you are trying to do a CLIP-style training, I would suggest you use the last layer output for a general purpose.


Fix git push error for protected CLA branch

The pull request is created from master636912081691463933 to master to fix git push error for protected CLA branch

@Taojunshen : Thanks for your contribution! The author, @gregvanl, has been notified to review your proposed change.


deps: up goreleaser to v1.11.2

Details are here https://github.com/goreleaser/goreleaser/releases/tag/v1.11.2.

https://github.com/kamilsk/godownloader/blob/d83a5dec63114df42d1a00733835ee68d3c514dc/go.mod#L8


Difference between resource-locker and this?

Both seem to have the same functionality with resource-locker being a superset of patch-operator? If so a possible reasoning for this over resource-locker

yes, thanks for the question, this explanation is overdue. The resource locker operator name was confusing and people, by and large, were only using the patch feature.
So I decided to change the name and add a couple of features:

you can not patch multiple objects with a single patch definition. So for example you can say patch all the service accounts with the label so and so.
if you don't need continuous enforcing of the patch, you can just patch objects at creation time with a mutating webhook.
My intention is to deprecate the resource locker operator soon (after I have some confirmation that the patch operator is stable).

may I close this?

Sure
On Mon., Feb. 7, 2022, 5:34 a.m. raffaelespazzoli, @.***>
wrote:

may I close this?
—
Reply to this email directly, view it on GitHub
https://github.com/redhat-cop/patch-operator/issues/2#issuecomment-1031475425,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYC342WVJY2HBJGU76RG3UZ7C5BANCNFSM5LAJKKMQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


[bitwardenrs] Adjust if statement

Description of the change
Statement was not updated on last PR.  My guess it was overwritten.
Benefits
Ldapsync will load.
Possible drawbacks
None
Applicable issues

fixes
Statement logic

Additional information

Checklist

[*] Chart version bumped in Chart.yaml according to semver.
[*] Title of the PR starts with chart name (e.g. [home-assistant])
[*] (optional) Chart is using our common library as a dependency.
[ ] (optional) Variables are documented in the README.md

sorry about that, I thought I merged master into our major PR branch.

thanks for being patient, we're trying our best to work around the 3rd party OSS tools for managing helm chart repos.


ccx: BMM150 Magnetometer Sensor Driver

Product page
Datasheet
Interface: LPI2C3
Address: 0x10
Also needs to generate an interrupt signal.

Driver from Bosch
PX4 driver


Update Readme for Release of 1.9

This is issue is to track the updates to the README which should be done for 1.9 as there are multiple requests noting issues with examples.
This closes #137 in favour of more systematic updates.

Will be moving examples into Wiki instead so it can be updated without PR's


Getting websocket disconnected multiple times

Is there an existing issue for the same bug?

[X] I have checked the troubleshooting document at https://opendevin.github.io/OpenDevin/modules/usage/troubleshooting
[X] I have checked the existing issues.

Describe the bug
18:53:44 - opendevin:INFO: session.py:38 - WebSocket disconnected, sid: 10a52176-5b07-4e31-9491-a61dc78971e8
INFO:     ('<IP_ADDRESS>', 56104) - "WebSocket /ws?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzaWQiOiIxMGE1MjE3Ni01YjA3LTRlMzEtOTQ5MS1hNjFkYzc4OTcxZTgifQ.sHjtG7U-ydUuwqn87AmkmLhLPDILLLQrmXoiXf8oSc4" [accepted]
Starting loop_recv for sid: 10a52176-5b07-4e31-9491-a61dc78971e8, False
18:53:44 - opendevin:INFO: session.py:38 - WebSocket disconnected, sid: 10a52176-5b07-4e31-9491-a61dc78971e8
INFO:     connection closed
6:53:44 PM [vite] ws proxy socket error:
Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:962:11)
    at Socket._write (node:net:974:8)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Writable.write (node:internal/streams/writable:337:10)
    at Socket.ondata (node:internal/streams/readable:809:22)
    at Socket.emit (node:events:517:28)
    at addChunk (node:internal/streams/readable:368:12)
    at readableAddChunk (node:internal/streams/readable:341:9)
    at Readable.push (node:internal/streams/readable:278:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
INFO:     connection open

Also showing "Connection failed. Retry..." in UI
Current OpenDevin version
1.0

Installation and Configuration
conda create -n opendevin python=3.11
conda activate opendevin
# Add Docker's official GPG key:

sudo apt-get update

sudo apt-get install ca-certificates curl

sudo install -m 0755 -d /etc/apt/keyrings

sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc

sudo chmod a+r /etc/apt/keyrings/docker.asc

# Add the repository to Apt sources:

echo \

 "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \

 $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \

 sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

sudo apt-get update
sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

# installs NVM (Node Version Manager)
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash

# download and install Node.js
nvm install 20

# verifies the right Node.js version is in the environment
node -v # should print `v20.12.2`

# verifies the right NPM version is in the environment
npm -v # should print `10.5.0`
sudo apt update
sudo apt install pipx
pipx ensurepath
sudo pipx ensurepath --global
pipx install poetry
git clone https://github.com/nnilayy/OpenDevin.git
cd OpenDevin
make build
ollama serve
ollama pull mistral:7b
make run

Model and Agent
mistral:7b
Operating System
Linux
Reproduction Steps
No response
Logs, Errors, Screenshots, and Additional Context
No response

Does this occur when you're using OpenDevin or OpenDevin doesn't even initialize?

When I am using OpenDevin

@xingyaoww I remember you mentioned that this model isn't very good with OpenDevin and not capable enough. Is this the issue here or is the web disconnected something else entirely?

I do not know, I have to look into.

Which browser are you using?

brave

Could you check in Chrome/Edge?

Experiencing a websocket disconnected issue as well, seems to occur randomly.
Using chrome Browser and GTP-4o.
session.py:66 - WebSocket disconnected, sid: ce327121-f285-4a56-9edd-9cc6a1aa99c0                             ERROR:    Exception in ASGI application                                                                                Traceback (most recent call last):                                                                                File "/app/.venv/lib/python3.12/site-packages/uvicorn/protocols/websockets/websockets_impl.py", line 332, in asgi_send                     await self.send(data)  # type: ignore[arg-type]                                                                                ^^^^^^^^^^^^^^^^^^^^^                                                                                File "/app/.venv/lib/python3.12/site-packages/websockets/legacy/protocol.py", line 635, in send                                            await self.ensure_open()                                                                                File "/app/.venv/lib/python3.12/site-packages/websockets/legacy/protocol.py", line 939, in ensure_open                                     raise self.connection_closed_exc()                                                                                websockets.exceptions.ConnectionClosedError: no close frame received or sent                                                                                The above exception was the direct cause of the following exception:                                                                                Traceback (most recent call last):                                                                                File "/app/.venv/lib/python3.12/site-packages/starlette/websockets.py", line 97, in send                                                   await self._send(message)                                                                                File "/app/.venv/lib/python3.12/site-packages/starlette/_exception_handler.py", line 50, in sender                                         await send(message)                                                                                File "/app/.venv/lib/python3.12/site-packages/uvicorn/protocols/websockets/websockets_impl.py", line 345, in asgi_send                     raise ClientDisconnected from exc                                                                                uvicorn.protocols.utils.ClientDisconnected                                                                                During handling of the above exception, another exception occurred:                                                                                Traceback (most recent call last):                                                                                File "/app/.venv/lib/python3.12/site-packages/uvicorn/protocols/websockets/websockets_impl.py", line 244, in run_asgi                      result = await self.app(self.scope, self.asgi_receive, self.asgi_send)  # type: ignore[func-returns-value]                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^                                                                 File "/app/.venv/lib/python3.12/site-packages/uvicorn/middleware/proxy_headers.py", line 70, in call                                   return await self.app(scope, receive, send)                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^                                                                                File "/app/.venv/lib/python3.12/site-packages/fastapi/applications.py", line 1054, in call                                             await super().call(scope, receive, send)                                                                                File "/app/.venv/lib/python3.12/site-packages/starlette/applications.py", line 123, in call                                            await self.middleware_stack(scope, receive, send)                                                                                File "/app/.venv/lib/python3.12/site-packages/starlette/middleware/errors.py", line 151, in call                                       await self.app(scope, receive, send)                                                                                File "/app/.venv/lib/python3.12/site-packages/starlette/middleware/base.py", line 103, in call                                         await self.app(scope, receive, send)                                                                                File "/app/.venv/lib/python3.12/site-packages/starlette/middleware/cors.py", line 77, in call                                          await self.app(scope, receive, send)                                                                                File "/app/.venv/lib/python3.12/site-packages/starlette/middleware/exceptions.py", line 65, in call                                    await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)                                                               File "/app/.venv/lib/python3.12/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app                                    raise exc                                                                                File "/app/.venv/lib/python3.12/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app                                    await app(scope, receive, sender)                                                                                File "/app/.venv/lib/python3.12/site-packages/starlette/routing.py", line 756, in call                                                 await self.middleware_stack(scope, receive, send)                                                                                File "/app/.venv/lib/python3.12/site-packages/starlette/routing.py", line 776, in app                                                      await route.handle(scope, receive, send)                                                                                File "/app/.venv/lib/python3.12/site-packages/starlette/routing.py", line 373, in handle                                                   await self.app(scope, receive, send)                                                                                File "/app/.venv/lib/python3.12/site-packages/starlette/routing.py", line 96, in app                                                       await wrap_app_handling_exceptions(app, session)(scope, receive, send)                                                                 File "/app/.venv/lib/python3.12/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app                                    raise exc                                                                                File "/app/.venv/lib/python3.12/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app                                    await app(scope, receive, sender)                                                                                File "/app/.venv/lib/python3.12/site-packages/starlette/routing.py", line 94, in app                                                       await func(session)                                                                                File "/app/.venv/lib/python3.12/site-packages/fastapi/routing.py", line 348, in app                                                        await dependant.call(**values)                                                                                File "/app/opendevin/server/listen.py", line 264, in websocket_endpoint                                                                    await websocket.send_json({'token': token, 'status': 'ok'})                                                                            File "/app/.venv/lib/python3.12/site-packages/starlette/websockets.py", line 198, in send_json                                             await self.send({"type": "websocket.send", "text": text})                                                                              File "/app/.venv/lib/python3.12/site-packages/starlette/websockets.py", line 100, in send                                                  raise WebSocketDisconnect(code=1006)                                                                                starlette.websockets.WebSocketDisconnect                                                                                INFO:     ('<IP_ADDRESS>', 53218) - "WebSocket /ws?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzaWQiOiJjZTMyNzEyMS1mMjg1LTRhNTYtOWVkZC05Y2M2YTFhYTk5YzAifQ.BNxF4pGx6VEmzIp4ZzmSrPOJNA9l6LPf9pqU6R86FVs&latest_event_id=15" [accepted]                                             INFO:     connection open

I am experiencing a similar issue. Happens every couple of minutes.
I've started opendevin with
docker run -it     --pull=always     -e SANDBOX_USER_ID=$(id -u)     -e WORKSPACE_MOUNT_PATH=$WORKSPACE_BASE     -v $WORKSPACE_BASE:/opt/workspace_base     -v /var/run/docker.sock:/var/run/docker.sock     -p 3000:3000     --add-host host.docker.internal:host-gateway     --name openhands-app-$(date +%Y%m%d%H%M%S)     ghcr.io/all-hands-ai/openhands:0.8_amd64

Error message:
22:22:55 - opendevin:INFO: session.py:66 - WebSocket disconnected, sid: 855a1d05-6f21-42b4-af16-f9e22fe6a58d
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "/app/.venv/lib/python3.12/site-packages/uvicorn/protocols/websockets/websockets_impl.py", line 332, in asgi_send
    await self.send(data)  # type: ignore[arg-type]
    ^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.12/site-packages/websockets/legacy/protocol.py", line 635, in send
    await self.ensure_open()
  File "/app/.venv/lib/python3.12/site-packages/websockets/legacy/protocol.py", line 939, in ensure_open
    raise self.connection_closed_exc()
websockets.exceptions.ConnectionClosedError: no close frame received or sent

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/app/.venv/lib/python3.12/site-packages/starlette/websockets.py", line 97, in send
    await self._send(message)
  File "/app/.venv/lib/python3.12/site-packages/starlette/_exception_handler.py", line 50, in sender
    await send(message)
  File "/app/.venv/lib/python3.12/site-packages/uvicorn/protocols/websockets/websockets_impl.py", line 345, in asgi_send
    raise ClientDisconnected from exc
uvicorn.protocols.utils.ClientDisconnected

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/.venv/lib/python3.12/site-packages/uvicorn/protocols/websockets/websockets_impl.py", line 244, in run_asgi
    result = await self.app(self.scope, self.asgi_receive, self.asgi_send)  # type: ignore[func-returns-value]
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.12/site-packages/uvicorn/middleware/proxy_headers.py", line 70, in __call__
    return await self.app(scope, receive, send)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.12/site-packages/fastapi/applications.py", line 1054, in __call__
    await super().__call__(scope, receive, send)
  File "/app/.venv/lib/python3.12/site-packages/starlette/applications.py", line 123, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/app/.venv/lib/python3.12/site-packages/starlette/middleware/errors.py", line 151, in __call__
    await self.app(scope, receive, send)
  File "/app/.venv/lib/python3.12/site-packages/starlette/middleware/base.py", line 103, in __call__
    await self.app(scope, receive, send)
  File "/app/.venv/lib/python3.12/site-packages/starlette/middleware/cors.py", line 77, in __call__
    await self.app(scope, receive, send)
  File "/app/.venv/lib/python3.12/site-packages/starlette/middleware/exceptions.py", line 65, in __call__
    await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
  File "/app/.venv/lib/python3.12/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/app/.venv/lib/python3.12/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/app/.venv/lib/python3.12/site-packages/starlette/routing.py", line 756, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/app/.venv/lib/python3.12/site-packages/starlette/routing.py", line 776, in app
    await route.handle(scope, receive, send)
  File "/app/.venv/lib/python3.12/site-packages/starlette/routing.py", line 373, in handle
    await self.app(scope, receive, send)
  File "/app/.venv/lib/python3.12/site-packages/starlette/routing.py", line 96, in app
    await wrap_app_handling_exceptions(app, session)(scope, receive, send)
  File "/app/.venv/lib/python3.12/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/app/.venv/lib/python3.12/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/app/.venv/lib/python3.12/site-packages/starlette/routing.py", line 94, in app
    await func(session)
  File "/app/.venv/lib/python3.12/site-packages/fastapi/routing.py", line 348, in app
    await dependant.call(**values)
  File "/app/opendevin/server/listen.py", line 264, in websocket_endpoint
    await websocket.send_json({'token': token, 'status': 'ok'})
  File "/app/.venv/lib/python3.12/site-packages/starlette/websockets.py", line 198, in send_json
    await self.send({"type": "websocket.send", "text": text})
  File "/app/.venv/lib/python3.12/site-packages/starlette/websockets.py", line 100, in send
    raise WebSocketDisconnect(code=1006)
starlette.websockets.WebSocketDisconnect

@remod @lapochka8 Can't seem to reproduce this issue. Could you list the steps you took that caused the error?
One thing I notice common between the two of you is the using a Python 3.12 venv. The official supporting Python version for OpenHands is 3.11, could you confirm that you still encounter the same issue after using 3.11 instead?

I'm also getting websocket disconnected, here's an example:
15:20:08 - openhands:INFO: session.py:139 - Server event
15:20:08 - OBSERVATION
**CmdOutputObservation (source=EventSource.AGENT, exit code=1)**
npm error code EJSONPARSE
npm error path /workspace/rss-parser/package.json
npm error JSON.parse Expected double-quoted property name in JSON at position 546 (line 22 column 3) while parsing near "...ocha\": \"^10.2.0\",\n  },\n  \"dependencies\":..."
npm error JSON.parse Failed to parse JSON data.
npm error JSON.parse Note: package.json must be actual JSON, not just JavaScript.
npm error A complete log of this run can be found in: /home/openhands/.npm/_logs/2024-09-16T19_20_08_757Z-debug-0.log

[Python Interpreter: /openhands/poetry/openhands-ai-5O4_aCHf-py3.11/bin/python]
openhands@db9e4bfb62bc:/workspace/rss-parser $
15:20:08 - openhands:INFO: session.py:139 - Server event

==============
CodeActAgent LEVEL 0 LOCAL STEP 7 GLOBAL STEP 7

15:20:12 - openhands:INFO: llm.py:515 - Cost: 0.04 USD | Accumulated Cost: 0.25 USD
Input tokens: 11965
Output tokens: 91

15:20:12 - ACTION
**CmdRunAction (source=EventSource.AGENT)**
THOUGHT: I apologize for the error. It seems that removing the Puppeteer line has caused a JSON parsing issue. Let's fix the package.json file by ensuring it's properly formatted. We'll use the `jq` command to prettify the JSON:
COMMAND:
jq '.' package.json > temp.json && mv temp.json package.json
cat package.json
15:20:12 - openhands:INFO: runtime.py:413 - Awaiting session
15:20:12 - openhands:INFO: runtime.py:306 -
-----------------------------------Container logs:-----------------------------------
    |INFO:     <IP_ADDRESS>:65417 - "GET /alive HTTP/1.1" 200 OK
    |INFO:     <IP_ADDRESS>:65417 - "POST /execute_action HTTP/1.1" 200 OK
--------------------------------------------------------------------------------
15:20:12 - openhands:INFO: session.py:139 - Server event
15:20:12 - OBSERVATION
**CmdOutputObservation (source=EventSource.AGENT, exit code=127)**
bash: jq: command not found

[Python Interpreter: /openhands/poetry/openhands-ai-5O4_aCHf-py3.11/bin/python]
openhands@db9e4bfb62bc:/workspace/rss-parser $
15:20:12 - openhands:INFO: session.py:139 - Server event

==============
CodeActAgent LEVEL 0 LOCAL STEP 8 GLOBAL STEP 8

15:20:14 - openhands:INFO: llm.py:515 - Cost: 0.04 USD | Accumulated Cost: 0.29 USD
Input tokens: 12147
Output tokens: 61

15:20:14 - ACTION
**CmdRunAction (source=EventSource.AGENT)**
THOUGHT: I apologize for the confusion. Since `jq` is not available, let's manually fix the package.json file. We'll use `cat` to view the contents, then edit it using `sed`:
COMMAND:
cat package.json
15:20:20 - openhands:INFO: session.py:65 - WebSocket disconnected, sid: 6b69486e-82e8-483f-bee8-9154bec8e765
INFO:     connection closed
INFO:     ('<IP_ADDRESS>', 49895) - "WebSocket /ws?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzaWQiOiI2YjY5NDg2ZS04MmU4LTQ4M2YtYmVlOC05MTU0YmVjOGU3NjUifQ.nHIzIhS1H562_zZ_0YBzOzBM31m4fjmK-g3nTBFCwvw&latest_event_id=17" [accepted]
15:20:20 - openhands:INFO: runtime.py:413 - Awaiting session
15:20:20 - openhands:INFO: runtime.py:306 -
-----------------------------------Container logs:-----------------------------------
    |INFO:     <IP_ADDRESS>:65417 - "GET /alive HTTP/1.1" 200 OK
    |INFO:     <IP_ADDRESS>:65417 - "POST /execute_action HTTP/1.1" 200 OK
--------------------------------------------------------------------------------

FWIW I have encountered this in the past, on Brave only, I wasn't seeing it on Safari. However, recently I haven't experienced it in Brave either. (although, I haven't used the UI much recently, so the latter might not be relevant)


have a flag to NOT do masking of zero counts.

i.e. report 0 humans as 0 humans, 0 trips as 0 instead of applying privacy/extrapolation

Can one of the admins verify this patch?


Commands to increment and decrement numbers

Vim has commands to increment (Ctrl-A) and decrement (Ctrl-X) numbers. These would be good to have in Xi as well.
Some details to pay attention to:

If the caret is not pointing at a number, the next number after the caret is selected, but only within the same line.
After the command, the caret is placed at the end of the number.
Negative numbers are meaningfully handled.

I'd put this firmly in 'one day'/'nice to have' territory? I do use this in vim sometimes, but it still feels like a slightly odd feature, that is mostly justified by it's use in macros? maybe?
Does it handle hex/octal/binary?
In any case, this does feel like a fun fairly self-contained project, so I would certainly be open to having someone work on it if they were interested.

I don't use Vim often, and I don't even now how to make macros in Vim, but when I do use Vim, I often use this feature. When I use Emacs I miss it.
Octal numbers are handled in the confusing way you can see following the link. I think it would be better not to handle octal numbers, or have interpretation of numbers depend on the language being edited.

I'd like to give this a try. If I manage to implement this, then I'll also add support to Xi-Mac

I've added an implementation here: https://github.com/xi-editor/xi-editor/pull/877


+= 1

1762 is currently modified to += 0.5, it could be safely += 1
1762,"****",59,"*****"
1762.5,"****",59,"*******"

see: https://github.com/theDavidBarton/koronavirus.gov.hu-scraper/pull/29/files#diff-965c8f56960b66b61b2edae76c6b75416e6d444b2543168b6f72faf41551144cR23423

fixed by #33


Filter Authors by Product

Buganizer: https://b.corp.google.com/issues/246519428
Added a function in the config directory named queryAuthorByProducts with the following functionality:

Takes in a product array as a parameter to act as the filter
Goes through the products of each author and finds the best fit authors for the selected products
Returns a list of type interface QueryResult to be rendered by the frontend

This function can be imported and called in Author.vue once the frontend frames are available for the filters

@garimame Can you take a look and approve the workflows so we can merge this change?

@mijaz18 for me to test the changes, please generate a firebase staging url.

@garimame There's no frontend change (no .vue files) changed in this PR which is why a the firebase staging url was not generated. The UI remains the same, and the function created is unused till the frontend is ready and calls it.
If you still want me to generate a firebase staging URL I can add a small change to one of the .vue files temporarily.


Change compent style colors

What is the recommended way to change the colors of the default theme?

The best way is crafting your theme, follow this instruction from element-ui: http://element.eleme.io/1.4/#/zh-CN/component/custom-theme


virtualenvwrapper: Remove realpath dependency using zsh :A

PR #3918 introduced a dependency on the command realpath to the virtualenvwrapper plugin. This is a problem because realpath is not installed on many systems by default. (It's not even available in the main Homebrew tap for OS X.) This caused problems for some users (#4079).
This PR removes the realpath dependency by replacing realpath calls with zsh's native :A parameter expansion modifier, which does the same thing as realpath, except portably and with no external dependency. This is also a performance win because it avoids the need to shell out to an external command.
The original code also called realpath at every step of the directory tree it was walking up. This is unnecessary because the first realpath or :A call resolves intermediate symlinks. This PR removes the extra calls.
Uses $PWD instead of $(pwd), to avoid an unnecessary shell-out (for performance) and to make the :A modifier call a one-liner.
Fixes #4079.
Fixes #4030.
Closes #4025, which attempted to fix the issue by checking for the existence of realpath. Using :A results in simpler, faster code. (Sorry for stepping on your PR, @SandyRogers, but people are asking for a fix for immediate breakage.)
Closes #4074, which is basically the same thing.

Hi!
I just tried out this solution and:

it removes the error on first "cd"
it still DOES NOT activate the virtualenv for the current directory (if any).

Am i missing something?
Thanks for your time :)
d.

@davidetruffo can you try #4074 ?

Of course i can @mcornella
But unfortunately no venv active still..
i'm no backend/programmer at all, but from my understanding the main issue is that the ENV_NAME is always an empty string, and this makes the function to never get into the activation condition...
while [[ "$PROJECT_ROOT" != "/" && ! -e "$PROJECT_ROOT/.venv" ]]; do
        PROJECT_ROOT=${PROJECT_ROOT:A:h}
      done
      if [[ "$PROJECT_ROOT" == "/" ]]; then
        PROJECT_ROOT="."
      fi
      # Check for virtualenv name override
      if [[ -f "$PROJECT_ROOT/.venv" ]]; then
        ENV_NAME=`cat "$PROJECT_ROOT/.venv"`
      elif [[ -f "$PROJECT_ROOT/.venv/bin/activate" ]];then
        ENV_NAME="$PROJECT_ROOT/.venv"
      elif [[ "$PROJECT_ROOT" != "." ]]; then
        ENV_NAME=`basename "$PROJECT_ROOT"`
      else
        ENV_NAME=""
      fi

and the result is always that
ENV_NAME == ""

so it doesn't satisfy this
if [[ "$ENV_NAME" != "" ]]; then
````

$ENV_NAME will only be set if there's a .venv file or folder in the current directory or any of the parents. So you have to create a .venv file with the ENV_NAME you want as content, and put it somewhere in one of the parent folders to test this.
@apjanke this version of #4074 doesn't translate exactly as the realpath alternative. Here only the $PWD is translated into the symlink target, not the rest of the parents. The realpath alternative follows exactly what the git rev-parse command did before (see https://github.com/robbyrussell/oh-my-zsh/pull/4025#issuecomment-112897449), so I'll support #4074 instead. BTW, there's a small detail to polish, but I'll propose it there instead.

@mcornella: Are you basing that on a test, or examining the code? I believe the behavior of this :A version is the same as the realpath version. Both realpath and zsh's :A modifier resolve symlinks all the way up the path, not just at the current leaf file like realink does. So the calls to realpath at every step up the tree were redundant in the first place; only the one call on $PWD was necessary. I removed it for efficiency and clarity. I've done some basic tests on :A vs realpath on OS X in this situation, and they behaved the same. (Using the realpath from brew tap iveney/mocha; brew install realpath.)
Here's a test case.
cd ~
mkdir -p tmp
cd tmp
mkdir -p foo/bar
mkdir -p baz/real/path
ln -s ~/tmp/baz/real/path foo/bar/link
cd foo/bar/link
mkdir -p dirs/under/link
cd dirs/under/link
echo $PWD
echo ${PWD:A}

I get this on OS X 10.9.5.
$ echo $PWD
/Users/janke/tmp/foo/bar/link/dirs/under/link
$ echo ${PWD:A}
/Users/janke/tmp/baz/real/path/dirs/under/link

Note that it resolved the symlink three levels up. You can take it another step, and make a symlink to a dir under the original symlink, so you have multiple levels of symlink indirection at different levels in the file path.
cd ~/tmp/foo
ln -s ~/tmp/foo/bar/link/dirs another_symlink
cd another_symlink/under/link
echo $PWD; echo ${PWD:A}

Both get resolved, and the canonical non-symlinked path is the result.
$ echo $PWD; echo ${PWD:A}
/Users/janke/tmp/foo/another_symlink/under/link
/Users/janke/tmp/baz/real/path/dirs/under/link

Since there are no longer any symlinks in the file path, there is no need to do symlink resolution with :A or readlink again as you're walking up the path.

Either way, how did I miss the existence of #4074? Sorry about that; I need to search harder next time.
I miss real bug tracking systems where you can see dependency and other relationship graphs. Anybody know how to view that for GitHub issues?

@mcornella thanks for the explanation!
It still doesn't activate the venv for me..
Here's a sample of the structure i used to have (and it used to work)
Projects
  |- project_1
  |- project_2
  |- venvs
       |- project_1 (venv for project_1)
       |- project_2

so typing
cd Projects/project_1

would activate Projects/venvs/project_1
I have now updated my structure to test (i hope properly :) ) to this:
Projects
  |- project_1
       |- .venv (a file, containing "project_1" as a string)
  |- project_2
  |- venvs
       |- project_1 (venv for project_1)
       |- project_2

But still nothing (or better, i get $ENV_NAME set, but the virtualenv is not activated
I'm wondering if i misunderstood it all, meaning that this fix just removes the dependency on realpathor it should ALSO activate/deactivate the virtualenv just cd-ing in/out
Again, thanks for your time :)

@apjanke: wow I hadn't thought of that possibility, so one :A is all we need. Thanks for the extensive response and test suite. Can you do one more test? Make a git repository inside one of these folders and see what git rev-parse --show-toplevel returns (if it's the canonical path or also contains symlinks).
@davidetruffo:

Without .venv doesn't work as it used to be due to the way the new algorithm is done: PROJECT_ROOT is used to traverse the path up to the root element, but if no .venv is found, PROJECT_ROOT stays / and then PROJECT_ROOT=. in the next if. Therefore in the following if chain the execution doesn't enter the proper if branch.
The proper way to fix this would be to use a temporary variable holding the current folder being traversed, and only set PROJECT_ROOT if .venv was found. Can you implement this @apjanke ?

The automatic activation is done in this part of the code. So it either runs workon $ENV_NAME or source $PROJECT_ROOT/.venv/bin/activate, but it will not activate if neither of those exist.

@mcornella thanks for the sweet and clear explanation!
So to make it work (activating/deactivating the right venv) i need to update my structure, am i correct? (just to be super-duper clear)

It depends, (1) will work when it is fixed. (2) should work as long as you have $WORKON_HOME set to Projects/venv, can you post the output of echo $WORKON_HOME?

You're welcoeme.
Here's the git part of the test. The git rev-parse --show-toplevel is identical to the :A implementation: canonical path, with all symlinks removed.
cd ~/tmp/foo/another_symlink/under/link/
mkdir git-repo; cd git-repo; git init
echo ${PWD:A}; git rev-parse --show-toplevel;
if [[ "$(git rev-parse --show-toplevel)" == "${PWD:A}" ]]; then echo SAME; fi

My results:
➜  git-repo git:(master) echo ${PWD:A}; git rev-parse --show-toplevel;
/Users/janke/tmp/baz/real/path/dirs/under/link/git-repo
/Users/janke/tmp/baz/real/path/dirs/under/link/git-repo
➜  git-repo git:(master) if [[ "$(git rev-parse --show-toplevel)" == "${PWD:A}" ]]; then echo SAME; fi
SAME

And about that other bit with the "no-.venv" case – sure, I'll add that in. This PR was originally just to fix the realpath dependency, but it should really take care of any bugs introduced by the recent changes that added in the realpath stuff. Give me an hour or two...

Perfect, so git behavior confirmed. Thanks for the hard work!

:+1: for merging this ...and if there is an issue with :A, then that can be a separate issue.

@mcornella
here's the output for echo $WORKON_HOME ->  /Users/davidetruffo/Projects/venvs
it is set in my .zshrc

Uh oh. So, I reviewed the old version of virtualenvwrapper and #3918, and the expected behavior in edge cases isn't clear to me.
Originally, before #3918, it looks like your "project root" was the root dir of the lowermost git repo you were in, and the "$ENV_NAME" was the basename of that project root directory, and it could be overridden by a ".venv" dir directly under the Git repo. With #3918, the .venv could be located anywhere on the path above you, and the lowermost one would be taken as the project root. But the semantics of using the git repo's root dir basename as the default $ENV_NAME were removed. It would only recognize a project if it was explicitly customized with a .venv dir. It's sounding like that was unintentional, and the git repo root should still be taken as the project root, in the absence of a .venv.
(That test for the Git behavior I did only tested that it treated symlinks the same way :A does. It didn't test for the old semantics of "a git repo defines a project root".)
I can restore that. The implementation is easy enough. But I need to know how the two are supposed to interact. It's not documented in the code or PR, and I don't know virtualenv/virtualenvwrapper conventions well enough to answer that myself.

It seems clear that a .venv at or below the git repo root takes precedence, and defines the $ENV_NAME.
What about a .venv located above a git repo root which doesn't have its own .venv? Should the git repo basename be used? Or should the .venv higher up in the path take precedence? To me, it seems like the Git repo should take precedence, but I don't understand the workflow intentions behind #3918, so maybe that's not the case.
@davidetruffo: I'm assuming in your example that those projects are git repos, right?  That if you're not under a Git repo or a dir with .venv, then you are not in a virtualenv and it should be deactivated.

Tested that this works as intended, great and conventional fix! I would recommend merging this as it solves the issue in case and try moving the discussion regarding #3918 to separate issue.
It's already plenty difficult to catch up with the issue and the PRs floating around :)

Yeah, that makes sense to me. (There's enough out there that I missed a PR on this myself.) Let's clear up this immediate realpath breakage with this, and resolve the "git repo base dir vs explcit .venv only" problem under a different PR. They are distinct questions, and it doesn't affect the correctness of this PR for the "realpath dependency" issue.
I'm :+1: for merging this now, and we can open a separate issue to discuss the git vs .venv semantics.

@apjanke yes, they are git repos (in my example: project_1, project_2 are git repos). My bad, i gave it for granted but it's not that granted :)

Ok, I've proposed this PR to Robby. Hopefully this one and #4041 will be merged during the day.

:+1:

Looks like some other people are expecting the old behavior of "treat git repos without .venv as project roots", too: #4110. I'll put together a separate PR for that.

I put in a follow-up fix for treating Git repos as project roots: #4122.
@davidetruffo, that should fix the problem with your Git projects that you described. Could you try that one out, and if it works, give a +1 in the comments on #4122?

@apjanke sorry for the late reply!
#4122 works like a charm with my example (so it activates/deactivates the right virtualenv when you cd in/out from a git repo)

:+1: This fixes #4030 for me.

+1, please merge.

:+1: This PR fixes the workon_cwd:6: command not found: realpath infinite loop for me, please merge.


After login I got: CSRF verification failed. Request aborted.

I followed guide on https://traxio.readthedocs.io/en/latest/deploy.html and after succesfully pass all steps and configure DJANGO_ALLOWED_HOSTS I cannot login. I get error:
Forbidden (403)
CSRF verification failed. Request aborted.
Could you please help me how to fix this issue?

Hi and sorry for the delay!
Can you tell me how your instance is deployed? I'm especially interested in your webserver setup. Do you have a reverse proxy in front of the app and, if yes, how is it configured ?

Hi and thanks for the response.
I tried on 2 different servers and got the same results. Things that I do are following this tutorial step by step  https://traxio.readthedocs.io/en/latest/deploy.html
`# clone the repository
git clone https://github.com/EliotBerriot/trax.git
cd trax
setup the environment variables
edit the .env file, especially the TIME_ZONE variable
and the DJANGO_ALLOWED_HOSTS one
cp env.example .env
nano .env
set up the docker-compose file
customize any configuration in the docker compose file
especially, you can change the listening port and ip
cp docker-compose.example.yml docker-compose.yml
nano docker-compose.yml
build and run the containers
docker-compose build
docker-compose up -d
create tables in the database
docker-compose run django python manage.py migrate
create an admin user (this will be needed to configure your tokens)
docker-compose run django python manage.py createsuperuser`
Changed just DJANGO_ALLOWED_HOSTS=dev.minimaldevelo.com in .env
I got http://dev.minimaldevelop.com:8079/accounts/login/ when I try to login I got CSRF error.
I don't have reverse proxy set.
Here are docker ps
ubuntu@dev:~$ docker ps CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                  NAMES 03925d23cebe        trax_nginx          "nginx -g 'daemon of…"   2 days ago          Up 2 days           <IP_ADDRESS>:8079->80/tcp   trax_nginx_1 0fc23cf0c9f4        trax_django         "/entrypoint.sh /gun…"   2 days ago          Up 2 days                                  trax_django_1 a4f193fe6710        trax_worker         "/entrypoint.sh pyth…"   2 days ago          Up 2 days                                  trax_worker_1 1bb42258165a        trax_postgres       "docker-entrypoint.s…"   2 days ago          Up 2 days           5432/tcp               trax_postgres_1 90ebdace0cce        redis:latest        "docker-entrypoint.s…"   2 days ago          Up 2 days           6379/tcp               trax_redis_1
If you need some more information please let me know. I am willing to give you access to server if you like.

Thanks for the additional info. I think you're bitten by  this setting. Basically, trax is designed to be deployed in a secure-first way, meaning it will only send cookies and CSRF toen when served behind an https connection.
Can you please try adding a reverse proxy in front of trax. On nginx, the configuration should look like this:
upstream trax {
    # depending on your setup, you may want to udpate this
    server localhost:8079;
}

# Uncomment this after you have https setup
# server {
#   listen 80;
#   listen [::]:80;
#   server_name trax.yourdomain.com;
#   location / { return 301 https://$host$request_uri; }
# }

server {
    listen      443 ssl;
    listen [::]:443 ssl;
    server_name trax.yourdomain.com;

    ssl_certificate      /etc/ssl/yourcert/domain.crt;
    ssl_certificate_key  /etc/ssl/yourcert/domain.key;

    location /
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        # this is the important bit: if you cannot serve trax behind https for
        # some reason, you can comment this line and uncomment the next one.
        # It will lie to trax about being served behind https
        proxy_set_header X-Forwarded-Proto $scheme;
        # proxy_set_header X-Forwarded-Proto https;
        proxy_set_header X-Forwarded-Host   $host:$server_port;
        proxy_set_header X-Forwarded-Port   $server_port;

        proxy_redirect off;
        proxy_pass   http://trax;
    }
}

If it works, it's definitely an https issue, and I'll make a PR so we can configure trax to work on http as well. I realize we also miss some documentation about the reverse proxy part.

I have created proxy with nginx which is on the host server error regarding CSRF is gone, but I have only this page:
http://storage3.static.itmages.com/i/18/0226/h_1519679306_9829953_05af346043.pngl
I cannot setup token because when I point to https://dev.minimaldevelop.com/trax/admin it says Page not found, is it some problem with the proxy settings?

The fact the admin page result in a 404 is probably because you miss the DJANGO_ADMIN_URL setting in your .env file. You can set it to ^trax/admin/ if you want the admin to be reachable at https://dev.minimaldevelop.com/trax/admin
I'm really sorry for the trouble, it's an old project and I don't have much time to maintain it these days :/

Thank you very much. It is working now.


Support BetterTouchTool install

BetterTouchTool is feature packed app that allows you to customize various input devices.
https://folivora.ai/

If you want version checking if that is accepted, then you can add this line below downloadURL:
appNewVersion=$(curl -fs https://updates.folivora.ai/bettertouchtool_release_notes.html | grep BetterTouchTool | head -n 2 | tail -n 1 | cut -d '>' -f 3 | cut -d '<' -f 1)