Cannot create service of type TaskExecuter using ProjectExecutionServices.createTaskExecuter()

Gradle Build error in android studio 3.6.1 Gradle Version 5.6.4
Cannot create service of type TaskExecuter using ProjectExecutionServices.createTaskExecuter() as there is a problem with parameter #22 of type ReservedFileSystemLocationRegistry.

Cannot create service of type ReservedFileSystemLocationRegistry using ProjectExecutionServices.createReservedFileLocationRegistry() as there is a problem with parameter #1 of type List.

I have the same

Same here, need help please :/

I ran into the same issue when trying to deploy another project on the same virtual device.
For me it was solved by selecting "Wipe Data" for that Virtual Device in Android Virtual Device Manager.

I'm facing this issue too, any answer?

Same issue here launching brand new Flutter project.  Flutter launches fine on iOS Simulator interestingly enough.

I ran into this issue on my mac with a Flutter project when gradle cache consumed disk space to exhaustion. From that point on, and despite clearing cache to recover disk space, every gradle-based Flutter command would result in the above error. Restarting the machine worked for me.

Encountered this exact error with Unreal Engine project for Android stored on external drive. Android Studio fails to build the gradle project. When project is copied over to the local hard drive, no issues building it.

Yeah, same issue here. I face the same issue from the flutter project that I stored in external drive and used VS code. I made android project from android studio and faced the same issue. I have updated the android studio to 3.6.3.

I have the same,I use an external hard drive

It turned out that there was a problem with my gradle environment variable setting, I fixed it

@Weightang what was wrong with the environment/what did you check? maybe i have similar issue

@peetonn gradle environment,  GRADLE_HOME  Configuration.

What did you change

I had this error in a flutter project and mysteriously there was a (zombie?) gradle process lingering around (possibly holding file locks). After killing it, flutter built again.

I have the same issue

I am working on React Native, I had this issue while building the project with gradle for the first time using "react-native run-android", I resolved this by changing the project directory permission.
sudo chown -R   <Path of prjoject folder or . for current directory>

I faced the same problem when running application then I open a terminal in vscode  and write flutter clean command and then run my code and it works.

@peetonn gradle environment, GRADLE_HOME Configuration.

Could you elaborate more on that answer please ?

Running chown <your-username>:<your-username> <project-root-dir> and then chmod 777 -R <project-root-dir> fixed it for me. You might want to make your keystores more restrticted after that

Remove the caches directory under c:\Users<Your user name directory>.gradle directory worked for me.

same issue

I just try to create "empty activity" application with latest and greatest version of Android Studio, and I get this error out of no reason.
Same here

I encountered the same issue in react native I resolved it by stopping Gradle and then executing the step again
gradle --stop

Sorry to open this issue again. If you put the project on an external hard drive, you need to give Android Studio full access to the disk on the Mac. Hope to solve your problem

Sorry to open this issue again. If you put the project on an external hard drive, you need to give Android Studio full access to the disk on the Mac. Hope to solve your problem

I am facing the same issue in android studio please help!!! I am panicking |_|
help me or my team will kick me out

Same issue while building a react-native project with gradle for the first time using "react-native run-android"

the same here

@tresat try this: https://github.com/tassilo-posegga/Firefly Basically I created a new empty multiplatform project and upgraded all dependencies.

Can anybody in this thread check the reproducer?
On my side, it built fine multiple times fine - but I would like to see this fail.
Some questions also you could help us out:

Is the issue intermittent, or it's constantly breaking?
After fixing the issues by various means, is it coming back immediately, comes back later, or disappears forever?

Environment info:
------------------------------------------------------------
Gradle 7.2
------------------------------------------------------------

Build time:   2021-08-17 09:59:03 UTC
Revision:     a773786b58bb28710e3dc96c4d1a7063628952ad

Kotlin:       1.5.21
Groovy:       3.0.8
Ant:          Apache Ant(TM) version 1.10.9 compiled on September 27 2020
JVM:          11.0.15 (Oracle Corporation 11.0.15+3)
OS:           Linux 5.16.11-zen1-1-zen amd64

Closing given the reproducer seems to work fine


Delete removed images using Folder Collections Media

possibly related to Delete path folder when delete entry #3615
Describe the bug
When using Folder Collections Media  a folder is created for the post, images are loaded from and saved to this folder
They are not accessible to the media assets UI
When removing an image from the page it is not deleted from git
To Reproduce
In config.yml use a collection storing images in a folder for the post

path creates a folder
media_folder is relative to this folder
a list of images is used

Create a post with at least one image
publish
Edit that post and delete the image
Expected behavior
I would expect the image to be deleted from the post front matter and from git
What happens is that the image is deleted from frontmatter but not from git
You can replace the image in frontmatter with a new image but not remove the old one
You can't remove it via the media assets tool either as it isn't in the folder this looks at.
While the image isn't in frontmatter it may still be used by the site generator (eg Hugo still sees this as a valid Page Resource)
Applicable Versions:
netlify-cms-app 2.14.28
netlify-cms-core 2.38.6
netlify-cms 2.10.98
Gitlab
Ubuntu
Chromium Version 89.0.4389.82 (Official Build) snap (64-bit)
CMS configuration

backend:
  name: git-gateway
  branch: master # Branch to update (optional; defaults to master)
collections:
  - name: "gallery" # Used in routes, e.g., /admin/collections/blog
    label: "Gallery" # Used in the UI
    folder: "content/gallery" # The path to the folder where the documents are stored
    slug: "{{year}}-{{slug}}" # Filename template, e.g., YYYY-MM-DD-title.md
    path: '{{slug}}/index'
    media_folder: ''
    public_folder: '/content/gallery/{{year}}-{{slug}}/'
    create: true # Allow users to create new documents in this collection
    fields: # The fields for each document, usually in front matter
      - {label: "Title", name: "title", widget: "string"}
      - {label: "Publish Date", name: "date", widget: "datetime"}
      - {label: "Description", name: "description", widget: "string"}
      - label: "Keywords"
        name: "tags"
        widget: "list"
      - label: "Images"
        name: "images"
        widget: "list"
        summary: '{{fields.image}}'
        field: {label: Image, name: image, widget: image}
      - {label: "Body", name: "body", widget: "markdown"}

Additional context
Using media folders per page works very well mainly - but there is a need to be able to manage these images.

Hi @seanburlington, to get the image deleted you'll need to click choose different image and delete it from within the media library dialog (clicking remove image is not enough).
Does that work for you?

ahh - yes and I can manage the page images from there
Thank you
I think I was thrown by clicking "remove image" which removed the image from the "page" but not the folder
I will write up a post on how to use netlify-cms with Hugo page bundles as it hasn't been 100% clear to me
If there is a way to contribute docs let me know.


Error: Cannot find module '/github/workspace/index.js'

I have following setup:
name: Publish Package

on:
  release:
    types: [published]

jobs:
  releaser:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: mmarchini-oss/npm-otp-publish@v0
        with:
          npm_token: ${{ secrets.NPM_TOKEN }}
          github_token: ${{ secrets.GITHUB_TOKEN }}
          github_actor: ${{ github.actor }}
          version_url: https://github.com/${{ github.repository }}/releases/tag/${{ steps.release.outputs.tag_name }}

It shows error:
Run mmarchini-oss/npm-otp-publish@v0
  with:
    npm_token: ***
    github_token: ***
    github_actor: vedmant
    version_url: https://github.com/vedmant/nuxt3-vuex/releases/tag/
    notifier: github-issue
    timeout: 15
    github_release_team: github-issue
/usr/bin/docker run --name c3d7c1[2](https://github.com/vedmant/nuxt3-vuex/actions/runs/4213792037/jobs/7313774596#step:4:2)c7cc824fa08c78[3](https://github.com/vedmant/nuxt3-vuex/actions/runs/4213792037/jobs/7313774596#step:4:3)16dea5a[4](https://github.com/vedmant/nuxt3-vuex/actions/runs/4213792037/jobs/7313774596#step:4:4)4ec_b13904 --label 498[5](https://github.com/vedmant/nuxt3-vuex/actions/runs/4213792037/jobs/7313774596#step:4:5)9c --workdir /github/workspace --rm -e "INPUT_NPM_TOKEN" -e "INPUT_GITHUB_TOKEN" -e "INPUT_GITHUB_ACTOR" -e "INPUT_VERSION_URL" -e "INPUT_NPM_USER" -e "INPUT_NOTIFIER" -e "INPUT_TIMEOUT" -e "INPUT_GITHUB_RELEASE_TEAM" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/nuxt3-vuex/nuxt3-vuex":"/github/workspace" 49859c:3d7c12c7cc824fa08c7831[6](https://github.com/vedmant/nuxt3-vuex/actions/runs/4213792037/jobs/7313774596#step:4:6)dea5a44ec  "--npm-user=" "--version-url=https://github.com/vedmant/nuxt3-vuex/releases/tag/" "--npm-token=***" "--github-token=***" "--notifier=github-issue" "--github-actor=" "--github-release-team="
internal/modules/cjs/loader.js:905
  throw err;
  ^

Error: Cannot find module '/github/workspace/index.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
    at Function.Module._load (internal/modules/cjs/loader.js:[7](https://github.com/vedmant/nuxt3-vuex/actions/runs/4213792037/jobs/7313774596#step:4:7)46:27)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:[12](https://github.com/vedmant/nuxt3-vuex/actions/runs/4213792037/jobs/7313774596#step:4:13))
    at internal/main/run_main_module.js:[17](https://github.com/vedmant/nuxt3-vuex/actions/runs/4213792037/jobs/7313774596#step:4:18):47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Same, looks like this project although it looks great is most likely abandoned

Trying to move over to this one myself to adjust the release I already had configured but now having OTP enabled https://github.com/step-security/wait-for-secrets


change hardcoded dataTypeContent->id to dataTypeContent->getKey()

Fix this error:
https://github.com/the-control-group/voyager/issues/4315
and possible bugs with other fields

too aggresive search and replace to wrong code


Link to repo broken on Notifications page under Port 3000

Gitea version (or commit ref): 1.13.4
Git version: 2.30.2
Operating system: Debian Buster

Used package from https://packaging.gitlab.io/gitea

Running as user gitea via service

Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No

Log gist:

Description

In our gitea installation, running in a VM under standard port 3000, links to repos on Notfications page are broken: the link is without port.
On the other hand, on the dashboard those repo links are fine.

Check that you have correct ROOT_URL set in app.ini file: https://docs.gitea.io/en-us/config-cheat-sheet/#server-server

@lafriks Thanks, manually inserting HTTP_PORT in ROOT_URL fixed the issue.
I am unsure whether you can set ROOT_URL on initial config page though, maybe I've missed setting port there.


Browser source does not pick up dev changes

It's inconvenient to develop / debug it if all of Oratio has to be restarted to pick up changes to that webpage.
Should look into some kind of reloading, ideally hot reloading.

I gave this a go for a day and I feel like I still don't know understand how the build system interacts.
It all seems quite magic to me.
I've tried these things and I couldn't tell if it did anything:
https://github.com/Y0dax/Oratio/commit/c510397000f979976dd9cfab3a0e0959361492e2
I'm unassigning myself as I don't think I can make meaningful progress on this issue.


🐛: Search and Filter options not visible when browse page is scrolled down

Contact Details
No response
Location
BioSimulations
What happened?
Options are not visible when selecting search and filter after scrolling down page. User needs to scroll back up to see the menu appear.
What made it happen?

Scrolled down the browse page
Clicked on "Search and Filter" button
Did not see options
Scrolled to top
Saw options

Version
Development (Deployed on a .dev domain)
What browsers are you seeing the problem on?
Firefox, Chrome
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Added scroll to top on the opening of that panel

:tada: This issue has been resolved in version 7.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add more messages to console

A lot of commands simply execute while not having a visible impact.
While silence is indication of a successful exectuion, it's nonconclusive.

Partially complete, could use a once over to ensure that any edgecases which should be verbose have not been missed.


merge from template-node-app

package.json

chore(deps): add ^10.12.0 remove ^10.11.3 (devDependencies.npm-pkgbuild)

.github/workflows/ci.yml

chore: (jobs.test.strategy)

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

npm package (@latest dist-tag)
v6.1.0
GitHub release

Your semantic-release bot :package::rocket:


gssapi fails on debian buster

failure to use gssapi authentication
GSSAPI auth doesn't seem to work:
Authentication method 'gssapi-with-mic' (Kerberos) is not available.

Expected Behavior
bolt should support all ssh auth methods
Steps to Reproduce

configure ssh config for using gssapi
run any bolt command on host

Environment

Version 1.44.0-1buster
Platform Debian Buster

Full stacktrace
<Gem::ConflictError> Unable to activate net-ssh-krb-0.4.0, because gssapi-1.3.0 conflicts with gssapi (~> 1.2.0)
        /opt/puppetlabs/bolt/lib/ruby/2.5.0/rubygems/specification.rb:2325:in `raise_if_conflicts'
        /opt/puppetlabs/bolt/lib/ruby/2.5.0/rubygems/specification.rb:1438:in `activate'
        /opt/puppetlabs/bolt/lib/ruby/2.5.0/rubygems.rb:224:in `rescue in try_activate'
        /opt/puppetlabs/bolt/lib/ruby/2.5.0/rubygems.rb:217:in `try_activate'
        /opt/puppetlabs/bolt/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:128:in `rescue in require'
        /opt/puppetlabs/bolt/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:39:in `require'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/transport/ssh.rb:65:in `initialize'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/executor.rb:35:in `new'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/executor.rb:35:in `block (2 levels) in initialize'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/concurrent-ruby-1.1.5/lib/concurrent/delay.rb:87:in `block in value'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/concurrent-ruby-1.1.5/lib/concurrent/synchronization/mutex_lockable_object.rb:41:in `block in synchronize'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/concurrent-ruby-1.1.5/lib/concurrent/synchronization/mutex_lockable_object.rb:41:in `synchronize'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/concurrent-ruby-1.1.5/lib/concurrent/synchronization/mutex_lockable_object.rb:41:in `synchronize'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/concurrent-ruby-1.1.5/lib/concurrent/delay.rb:83:in `value'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/concurrent-ruby-1.1.5/lib/concurrent/delay.rb:137:in `wait'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/concurrent-ruby-1.1.5/lib/concurrent/concern/obligation.rb:87:in `wait!'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/executor.rb:57:in `transport'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/executor.rb:90:in `block in queue_execute'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/executor.rb:89:in `each'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/executor.rb:89:in `flat_map'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/executor.rb:89:in `queue_execute'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/executor.rb:145:in `batch_execute'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/executor.rb:259:in `block in run_task'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/executor.rb:153:in `log_action'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/executor.rb:255:in `run_task'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/bolt-modules/boltlib/lib/puppet/functions/run_task.rb:127:in `run_task_with_description'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pops/functions/dispatch.rb:60:in `invoke'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pops/functions/dispatcher.rb:43:in `block in dispatch'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pops/functions/dispatcher.rb:42:in `catch'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pops/functions/dispatcher.rb:42:in `dispatch'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pops/functions/function.rb:46:in `block in call'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pops/functions/function.rb:45:in `catch'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pops/functions/function.rb:45:in `call'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pops/evaluator/runtime3_support.rb:283:in `block in external_call_function'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/util/profiler/around_profiler.rb:58:in `profile'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/util/profiler.rb:51:in `profile'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pops/evaluator/runtime3_support.rb:282:in `external_call_function'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pal/compiler.rb:29:in `call_function'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/pal.rb:427:in `block in run_task'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/pal.rb:199:in `block (2 levels) in in_task_compiler'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/pal.rb:142:in `block (3 levels) in in_bolt_compiler'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/context.rb:62:in `override'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet.rb:274:in `override'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/pal.rb:141:in `block (2 levels) in in_bolt_compiler'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pal/pal_impl.rb:468:in `block (3 levels) in main'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/parser/script_compiler.rb:47:in `block in compile'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/context.rb:62:in `override'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet.rb:274:in `override'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/parser/script_compiler.rb:42:in `compile'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pal/pal_impl.rb:465:in `block (2 levels) in main'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/context.rb:62:in `override'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet.rb:274:in `override'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pal/pal_impl.rb:464:in `block in main'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/context.rb:62:in `override'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet.rb:274:in `override'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pal/pal_impl.rb:418:in `main'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pal/pal_impl.rb:92:in `with_script_compiler'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/pal.rb:137:in `block in in_bolt_compiler'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pal/pal_impl.rb:330:in `block in in_environment_context'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/context.rb:62:in `override'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet.rb:274:in `override'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pal/pal_impl.rb:322:in `in_environment_context'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/pal/pal_impl.rb:224:in `in_tmp_environment'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/pal.rb:136:in `in_bolt_compiler'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/pal.rb:198:in `block in in_task_compiler'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet/context.rb:62:in `override'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/puppet-6.11.0/lib/puppet.rb:274:in `override'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/pal.rb:180:in `with_bolt_executor'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/pal.rb:197:in `in_task_compiler'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/pal.rb:425:in `run_task'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/cli.rb:416:in `block in execute'
        /opt/puppetlabs/bolt/lib/ruby/2.5.0/benchmark.rb:308:in `realtime'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/cli.rb:402:in `execute'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/exe/bolt:10:in `<top (required)>'
        /opt/puppetlabs/bolt/bin/bolt:23:in `load'
        /opt/puppetlabs/bolt/bin/bolt:23:in `<main>'
        --- Caused by ---
        <Gem::ConflictError> Unable to activate net-ssh-krb-0.4.0, because gssapi-1.3.0 conflicts with gssapi (~> 1.2.0)
        /opt/puppetlabs/bolt/lib/ruby/2.5.0/rubygems/specification.rb:2325:in `raise_if_conflicts'
        /opt/puppetlabs/bolt/lib/ruby/2.5.0/rubygems/specification.rb:1438:in `activate'
        /opt/puppetlabs/bolt/lib/ruby/2.5.0/rubygems.rb:218:in `try_activate'
        /opt/puppetlabs/bolt/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:128:in `rescue in require'
        /opt/puppetlabs/bolt/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:39:in `require'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/transport/ssh.rb:65:in `initialize'
        --- Caused by ---
        <LoadError> cannot load such file -- net/ssh/krb
        /opt/puppetlabs/bolt/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
        /opt/puppetlabs/bolt/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/transport/ssh.rb:65:in `initialize'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/executor.rb:35:in `new'
        /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.44.0/lib/bolt/executor.rb:35:in `block (2 levels) in initialize'

Hi @faxm0dem - this is a known issue (https://puppet.com/docs/bolt/latest/bolt_known_issues.html#limited-kerberos-support). We can't formally recommend installing the net-ssh-krb gem, but if you install the net-ssh-krb gem into the bolt environment with /opt/puppetlabs/bolt/bin/gem install --user-install <gem> you should be able to authenticate with kerberos.

woo-hoo there seems to be a new version available https://rubygems.org/gems/net-ssh-krb

it seems 59d3f66629f1a4b8bc6fe4a4b9a52812446665d3 removed the code that activated gssapi authentication. @lucywyman was this a mistake?

No, we previously could not ship with the gem so had to try to load it and fail if it wasn't in bolt's gem environment. That allowed users to manually add the gem if they liked, and see the warning if they tried to use gssapi without it. The net-ssh gem is what uses net-ssh-krb, so now that we know it's available in bolt's gem env we don't have to try to load it to make sure it's there.

the problem is that gssapi auth doesn't work without those lines:
+        begin
+          require 'net/ssh/krb'
+        rescue LoadError
+          logger.debug("Authentication method 'gssapi-with-mic' (Kerberos) is not available.")
+        end

We still have to require the library, we just dont need to rescue a LoadError bc the gemspec ensures the gem is available.


Add missing tests

I don't understand this line: https://github.com/jonschlinkert/object.omit/commit/b23b2fd79473518dd81ce75a9a6bb64b7942abee#diff-168726dbe96b3ce427e7fedce31bb0bcR16
In enables the usage of object.fit that's not documented nor tested. Why wasn't the previous one enough (.isArray, etc)?
Additionally, the current usage of arguments kills V8 optimization, so I suggest changing that line either way. Let me know if you'd like me to fix it by dropping this undocumented behavior or by using .apply before .slice
One more question: can Node 0.10 support be dropped?

I don't understand this line

Honestly, I don't remember why I did that, so neither of us understand why I did that.

Additionally, the current usage of arguments kills V8 optimization

True, but that is less of an issue with recent versions of node.js, and it doesn't "kill" V8 optimization in an absolute sense, only in this specific function. Moreover, I've done many benchmarks on different libs with slicing arguments, and most of the time there is zero performance penalty from using it at all. Keep in mind that V8 only optimizes code that has things to be optimized in the first place.
Anyway, I agree that it's probably unnecessary here. I'll make some changes before I publish a new release.

One more question: can Node 0.10 support be dropped?

In what way? engine in package.json, or something in the code?
thanks for the pr!

@bfred-it I just pushed up 3.0.0 with some changes

I don't remember what exactly I meant to do by dropping 0.10, but I guess the idea was to use some API that wasn't available there.

Ah, possibly by using for of loops, but that'd raise browser compatibility a lot too :)

yeah, browser compatibility is key for microlibs like this.
Just out of curiosity, what is the reasoning behind wanting to upgrade code to es6? This seems to be common, but I can't wrap my arms around why. It makes sense to use new features on new code if and when there are performance, maintenance or readability benefits in doing so, but what is the benefit of retroactively "upgrading" older code to use newer features (specifically when those features are nothing more than syntax sugar)?  IMHO even the time spent refactoring will usually negate any maintenance related gains. Really am curious about your thoughts.

As you said

It makes sense to use new features on new code if and when there are [...] readability benefits in doing so

  var keys = Object.keys(obj);
  for (var i = 0; i < keys.length; i++) {
    var key = keys[i];
    var val = obj[key];

Becomes
  for (const key of Object.keys(obj)) {
    const val = obj[key];

Of course if you leave it as is it just keeps working and nobody cares, but sometimes it's just fun to find better/shorter ways do things, see https://codegolf.stackexchange.com/

but sometimes it's just fun to find better/shorter ways do things

Absolutely! Totally agree.

for..of has actually become faster than .forEach for this reason

Just for fun, I did some basic benchmarks with an object with 5, 10, 100, 1,000 and 10,000 keys.
// **5 keys**
// for x 3,188,152 ops/sec ±0.75% (88 runs sampled)
// foreach x 2,215,841 ops/sec ±0.50% (91 runs sampled)
// forin x 2,475,861 ops/sec ±0.80% (92 runs sampled)
// forof x 2,871,289 ops/sec ±0.36% (92 runs sampled)
// while x 3,127,017 ops/sec ±0.99% (89 runs sampled)

// **10 keys**
// for x 8,155,854 ops/sec ±0.53% (91 runs sampled)
// foreach x 4,006,585 ops/sec ±0.78% (89 runs sampled)
// forin x 8,261,419 ops/sec ±0.46% (91 runs sampled)
// forof x 7,278,734 ops/sec ±0.75% (89 runs sampled)
// while x 7,664,888 ops/sec ±0.94% (87 runs sampled)

// **100 keys**
// for x 327,443 ops/sec ±0.73% (87 runs sampled)
// foreach x 240,528 ops/sec ±0.42% (92 runs sampled)
// forin x 259,540 ops/sec ±0.87% (89 runs sampled)
// forof x 322,249 ops/sec ±0.32% (92 runs sampled)
// while x 329,402 ops/sec ±0.72% (92 runs sampled)

// **1,000 keys**
// for x 35,025 ops/sec ±0.42% (91 runs sampled)
// foreach x 25,733 ops/sec ±0.74% (90 runs sampled)
// forin x 27,325 ops/sec ±0.77% (93 runs sampled)
// forof x 35,565 ops/sec ±0.56% (93 runs sampled)
// while x 36,681 ops/sec ±0.96% (91 runs sampled)

// **10,000 keys**
// for x 3,555 ops/sec ±0.79% (89 runs sampled)
// foreach x 2,593 ops/sec ±0.60% (88 runs sampled)
// forin x 2,785 ops/sec ±0.89% (91 runs sampled)
// forof x 3,461 ops/sec ±0.43% (91 runs sampled)
// while x 3,551 ops/sec ±0.42% (93 runs sampled)

I have to say, you're right about for..of, I was surprised at how performant it is. Needless to say, for and while are still my favorites, as they are consistently faster regardless of the size of the data set... but, for..of will definitely be in my personal toolkit more often in libs where I don't need to think about browser compatibility.  Glad you mentioned it, thanks!


Problems with dump

When i like to dump databases i have this error and i don't understand because i have installed all clients for all databases.

Hi,
This is probably because you have not specified, in your connection settings, where are the client tools for your DBRMS.
So, if you edit your connection (select the connection and press "F4" or right-clic on the connection and select "Edit connection"), you get a window like this one:

There, you have to clic on the "Local client" combobox and choose "Browse...".
You get a window like this one:

Clic on "Add Home", browse to the directory with your RDBMS client tools (psql / pg_dump... for PostgreSQL, mysql for MySQL), depending on your RDBMS and your OS (which you did not precise in your post).
Once you are in the good directory, clic OK twice. The Local Client combo is now filled correctly.
Clic on OK and try your dump again. It should be OK (I hope so).


More customizable appearance on the TVP panel

Task
Right now in the tree the only distinction between nodes are whether one can be expanded or not, whether on is a method (signified via (), and that's it. However, the nodes contain symbol information about what type of Node it is. In coc-metals for example this is distinguished with colors. In VS Code it's done with little icons. This probably be made customizable.
Search terms
TVP Panel UI

fyi: I plan to work on metals-neotree integration so that metals data can be displayed as yet another neotree panel using neotree display logic.


Small bug.

OOPS! Typo here! You forgot to close your quotations! I'm a stickler for stuff like this. If you could merge this I would be so thankful!

Sorry for the late response. You are welcome for the contribution!


PFAM website is being shutdown. Start HMM can no longer be downloaded.

Problem Description
I get the following error in hmm_download.log:
--2023-09-29 16:15:44--  https://pfam.xfam.org/family/PF00308/hmm
Resolving pfam.xfam.org (pfam.xfam.org)... <IP_ADDRESS>
Connecting to pfam.xfam.org (pfam.xfam.org)|<IP_ADDRESS>|:443... connected.
ERROR: no certificate subject alternative name matches
        requested host name ‘pfam.xfam.org’.
To connect to pfam.xfam.org insecurely, use `--no-check-certificate'.

The HTTPS certificate for Xfam had expired or something close to that, so the download failed.
Problem Solution
I added the --no-check-certificate to the download HMM rule.
rule download_hmm:
    output:
        hmm=os.path.join(config.get("db_dir"), "hmm", config.get("start_hmm_pfam_id") + ".hmm")
    log:
        "logs/download/hmm_download.log"
    benchmark:
        "benchmarks/download/hmm_download.txt"
    params:
        db_dir=os.path.join(config.get("db_dir"), "hmm"),
        url="https://pfam.xfam.org/family/" + config.get("start_hmm_pfam_id") + "/hmm"
    shell:
        """
        mkdir -p {params.db_dir}
        wget -O {output.hmm} --no-check-certificate {params.url} 2> {log}
        """

Note that this allows the HMM to be downloaded but has security implications.

Okay, this downloads an HTML file rather than the HMM itself.

Okay, so the PFAM website is being shutdown. So we will have to get the HMM from a different source.

Okay, the URL http://pfam-legacy.xfam.org/family/PF08299/hmm works, but the HMM will not be updated as all updates will be done on InterPro. On Interpro, you cannot download individual HMMs, and the batch download of all PFAMs returns one big HMM file for all PFAMs.

@jmtsuji So, do we eventually start batch downloading all of PFAM and running part of the big HMM? I wonder if you can tell HMMER to run just one ID out of an HMM or extract PF08299 from the bigger HMM. Thoughts?

Temporary fixed added in https://github.com/jmtsuji/rotary/commit/9dfd461b89aff91aac0f2dd4dd58392dc8464871

@LeeBergstrand Thanks for looking into this issue. Too bad that the new hosting setup for Pfam HMMs is not ideal for single-HMM download....
One option is to change to the TIGRFAM rpoB HMM, which is hosted at NCBI: https://www.ncbi.nlm.nih.gov/genome/annotation_prok/evidence/TIGR02013/
It's possible to download the HMM as a single file: https://ftp.ncbi.nlm.nih.gov/hmm/current/hmm_PGAP.HMM/TIGR02013.1.HMM
Thoughts?

Temporary fixed added in 9dfd461

Thanks for adding this temporary fix!

@LeeBergstrand Thanks for looking into this issue. Too bad that the new hosting setup for Pfam HMMs is not ideal for single-HMM download....
One option is to change to the TIGRFAM rpoB HMM, which is hosted at NCBI: https://www.ncbi.nlm.nih.gov/genome/annotation_prok/evidence/TIGR02013/
It's possible to download the HMM as a single file: https://ftp.ncbi.nlm.nih.gov/hmm/current/hmm_PGAP.HMM/TIGR02013.1.HMM
Thoughts?

From TIGRFAMS NCBI site:
The TIGRFAMs database was transferred in April 2018 to the National Center for Biotechnology Information (NCBI), which
now holds the creative commons license to this data and is responsible for maintaining and distributing this intellectual
property. The database is used in NCBI's Prokaryotic Genome Annotation Pipeline for GenBank and RefSeq sequence
annotation, and curators continue to revise existing models.

Okay, so from this description, the models are being updated. That would be my main concern. Also, TIGERFAM are whole gene HMMs, so they should be more specific.
@jmtsuji Let's go with the TIGRFAM rpoB HMM.

Sounds good!

@jmtsuji Code for this has been committed here: https://github.com/jmtsuji/rotary/tree/new_hmm_download
I had trouble running it because I think the development branch of Rotary doesn't call these rules yet. Even when I ran snakemake's --forceall flag. Does this branch have to be integrated into your repair ends branch?

I'm not sure why you had trouble running this rule -- so long as you have circular contigs, it should in theory run (independently of end repair). However, snakemake won't know that it needs to run this code until it reaches a checkpoint partway through the pipeline and verifies that you actually have circular contigs. This is not ideal (it would be better if we had a rapid and guaranteed way of testing this rule), so I think this could be another reason to make a dedicated download rule/function as described in #45
Anyway, I tested the new rule in the end repair branch, and it works! Thus, I will close this issue.

@jmtsuji Sounds good!


Jackett monitoring does not work

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
Hello,
I'm trying to monitor jackett instance which is running on windows vm in proxmox. Uptime-Kuma cannot detect it while I can open jackett web interface with no problem in chrome. My local path is http://<IP_ADDRESS>:9117/UI/Dashboard.
Maybe someone has experience with it?
🐻 Uptime-Kuma Version
1.18.5
💻 Operating System and Arch
Lroxmox lxc container
🌐 Browser
Chrome
🐋 Docker Version
No response
🟩 NodeJS Version
No response

Operating System and Arch
lxc container

Usually it is a network issue. Did you allow your Uptime Kuma LXC container to access your LAN (192.168.1.X)?
https://github.com/lxc/lxd/issues/1343

I have Radarr, plex, and sonarr  on the same Vm and its working fine with Kuma. Only Jackett refuses to work.

I experience the same issue.
A normal ping works, but checking the webpage doesn't.

For anyone having this issue, I was able to fix it by disabling redirects and adding the 302 (Found) http status code to the monitor for jackett:

Thanks. That worked for me also.

For anyone having this issue, I was able to fix it by disabling redirects and adding the 302 (Found) http status code to the monitor for jackett:

Do you know the reason? As normally, Uptime Kuma will follow redirects to the final page.

Do you know the reason? As normally, Uptime Kuma will follow redirects to the final page.

Not 100% sure but it looks like Jacketts web server is setup weirdly.
Found this issue, could be why (uptime-kume gets redirected to login, but doesnt save cookie, goes back to dashboard, then because no cookie, back to login, infinite loop? Not even sure if kuma supports cookies, so I could be wrong): https://github.com/Jackett/Jackett/issues/12475#issuecomment-954224293

Having the same problem as above..
jackett setup on baremetal.. neither accessing through reverse nginx nor directly is working with uptime Kuma, even after trying above tips..

This is still an issue

@pkishino
This issue has been closed because it was raised with the help tag.
Please open an issue with more details than the current issue.
If you decide to do so please attach this information:

Currently there sadly is no way this is reproducible what the response of jackett to the inital ping is. => include how jackett redirects
what cookies it sets

I used https://hub.docker.com/r/linuxserver/jackett/ and getting curl to cooperate was a bit harder:
curl -v --cookie-jar -b cookiefile --junk-session-cookies --location http://localhost:9117

Resulting log

* Host localhost:9117 was resolved.
* IPv6: ::1
* IPv4: <IP_ADDRESS>
*   Trying [::1]:9117...
* Connected to localhost (::1) port 9117
> GET / HTTP/1.1
> Host: localhost:9117
> User-Agent: curl/8.6.0
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Content-Length: 0
< Date: Tue, 07 May 2024 18:40:36 GMT
< Server: Kestrel
< Location: /UI/Dashboard
<
* Ignoring the response-body
* Connection #1 to host localhost left intact
* Issue another request to this URL: 'http://localhost:9117/UI/Dashboard'
* Found bundle for host: 0x5593ad409ea0 [serially]
* Can not multiplex, even if we wanted to
* Re-using existing connection with host localhost
> GET /UI/Dashboard HTTP/1.1
> Host: localhost:9117
> User-Agent: curl/8.6.0
> Accept: */*
>
< HTTP/1.1 302 Found
< Content-Length: 0
< Date: Tue, 07 May 2024 18:40:36 GMT
< Server: Kestrel
< Location: http://localhost:9117/UI/Login?ReturnUrl=%2FUI%2FDashboard
<
* Ignoring the response-body
* Connection #1 to host localhost left intact
* Issue another request to this URL: 'http://localhost:9117/UI/Login?ReturnUrl=%2FUI%2FDashboard'
* Found bundle for host: 0x5593ad409ea0 [serially]
* Can not multiplex, even if we wanted to
* Re-using existing connection with host localhost
> GET /UI/Login?ReturnUrl=%2FUI%2FDashboard HTTP/1.1
> Host: localhost:9117
> User-Agent: curl/8.6.0
> Accept: */*
>
< HTTP/1.1 302 Found
< Content-Length: 0
< Date: Tue, 07 May 2024 18:40:36 GMT
< Server: Kestrel
< Cache-Control: no-store,no-cache
< Location: TestCookie
< Pragma: no-cache
* Added cookie TestCookie="1" for domain localhost, path /, expire 0
< Set-Cookie: TestCookie=1; path=/
<
* Ignoring the response-body
* Connection #1 to host localhost left intact
* Issue another request to this URL: 'http://localhost:9117/UI/TestCookie'
* Found bundle for host: 0x5593ad409ea0 [serially]
* Can not multiplex, even if we wanted to
* Re-using existing connection with host localhost
> GET /UI/TestCookie HTTP/1.1
> Host: localhost:9117
> User-Agent: curl/8.6.0
> Accept: */*
> Cookie: TestCookie=1
>
< HTTP/1.1 302 Found
< Content-Length: 0
< Date: Tue, 07 May 2024 18:40:36 GMT
< Server: Kestrel
< Cache-Control: no-store,no-cache
< Location: Login?cookiesChecked=1
< Pragma: no-cache
<
* Ignoring the response-body
* Connection #1 to host localhost left intact
* Issue another request to this URL: 'http://localhost:9117/UI/Login?cookiesChecked=1'
* Found bundle for host: 0x5593ad409ea0 [serially]
* Can not multiplex, even if we wanted to
* Re-using existing connection with host localhost
> GET /UI/Login?cookiesChecked=1 HTTP/1.1
> Host: localhost:9117
> User-Agent: curl/8.6.0
> Accept: */*
> Cookie: TestCookie=1
>
< HTTP/1.1 302 Found
< Content-Length: 0
< Date: Tue, 07 May 2024 18:40:36 GMT
< Server: Kestrel
< Cache-Control: no-cache,no-store
< Expires: Thu, 01 Jan 1970 00:00:00 GMT
< Location: Dashboard
< Pragma: no-cache
* Added cookie Jackett="CfDJ8KRxCoQqb95MnzVHT7NPkrhBWPC9s_3rW_h8K7jkpvmbbapBmeVF5G-kYvyPVMb36bWxVxX1nnrxqLaJD3w5w9xCBVmT4y3XBdYc7YIn0cO-c4j15e_IwYx1gYEpohNlMMvAzjLp2JSTgdQhvN_6XcbVDj6wQ1gtNTA0PxVhiqvmskmgbKJG_kZ9jcdu2OD3-OQnQIBaVaUQIGvuk-M-VGAPFngNxNwFN5r0H-03Fe5X4MYUUGyOcOWsdurSme9_WfsrszeM4UqE5yp49zdBr30aHhBL2ICAJByy1W8iywgnC6JGgvdYkiHgCC3Z6dU2LuoUwp7p_V0nZlgU4-QD3Tc" for domain localhost, path /, expire<PHONE_NUMBER>
< Set-Cookie: Jackett=CfDJ8KRxCoQqb95MnzVHT7NPkrhBWPC9s_3rW_h8K7jkpvmbbapBmeVF5G-kYvyPVMb36bWxVxX1nnrxqLaJD3w5w9xCBVmT4y3XBdYc7YIn0cO-c4j15e_IwYx1gYEpohNlMMvAzjLp2JSTgdQhvN_6XcbVDj6wQ1gtNTA0PxVhiqvmskmgbKJG_kZ9jcdu2OD3-OQnQIBaVaUQIGvuk-M-VGAPFngNxNwFN5r0H-03Fe5X4MYUUGyOcOWsdurSme9_WfsrszeM4UqE5yp49zdBr30aHhBL2ICAJByy1W8iywgnC6JGgvdYkiHgCC3Z6dU2LuoUwp7p_V0nZlgU4-QD3Tc; expires=Tue, 21 May 2024 18:40:37 GMT; path=/; samesite=lax; httponly
<
* Ignoring the response-body
* Connection #1 to host localhost left intact
* Issue another request to this URL: 'http://localhost:9117/UI/Dashboard'
* Found bundle for host: 0x5593ad409ea0 [serially]
* Can not multiplex, even if we wanted to
* Re-using existing connection with host localhost
> GET /UI/Dashboard HTTP/1.1
> Host: localhost:9117
> User-Agent: curl/8.6.0
> Accept: */*
> Cookie: TestCookie=1; Jackett=CfDJ8KRxCoQqb95MnzVHT7NPkrhBWPC9s_3rW_h8K7jkpvmbbapBmeVF5G-kYvyPVMb36bWxVxX1nnrxqLaJD3w5w9xCBVmT4y3XBdYc7YIn0cO-c4j15e_IwYx1gYEpohNlMMvAzjLp2JSTgdQhvN_6XcbVDj6wQ1gtNTA0PxVhiqvmskmgbKJG_kZ9jcdu2OD3-OQnQIBaVaUQIGvuk-M-VGAPFngNxNwFN5r0H-03Fe5X4MYUUGyOcOWsdurSme9_WfsrszeM4UqE5yp49zdBr30aHhBL2ICAJByy1W8iywgnC6JGgvdYkiHgCC3Z6dU2LuoUwp7p_V0nZlgU4-QD3Tc
>
< HTTP/1.1 200 OK
< Content-Length: 44176
< Content-Type: text/html
< Date: Tue, 07 May 2024 18:40:36 GMT
< Server: Kestrel
< Cache-Control: no-store,no-cache
< Last-Modified: Tue, 07 May 2024 05:58:38 GMT
< Pragma: no-cache
<
<!DOCTYPE html>

Extracted request flow

GET /
=> 301 to Location=/UI/Dashboard
GET /UI/Dashboard
=> 302 to Location=/UI/Login?ReturnUrl=%2FUI%2FDashboard
GET /UI/Login?ReturnUrl=%2FUI%2FDashboard
=> 302 to Location=TestCookie with Set-Cookie=TestCookie=1; path=/
GET /UI/TestCookie with Cookie=TestCookie=1
=> 302 to Location=Dashboard with Set-Cookie=Jackett=Cf...D3Tc; expires=Tue, 21 May 2024 18:40:37 GMT; path=/; samesite=lax; httponly
GET /UI/Dashboard with Cookie=TestCookie=1;Jackett=Cf...D3Tc
=> 200 with html

So the real request flow is super weird.
Please use an api endpoint instead to monitor the health such as GET /health mentioned in https://github.com/Jackett/Jackett/issues/12784#issuecomment-1008434003
Persising cookies during rediects is already tracked in https://github.com/louislam/uptime-kuma/issues/2309 => re-closing as resolved (due to /health)


csharp: fix nullable warnings

What happened?
I should be able to compile without getting ~20 warnings about nullable reference types.
How can we reproduce the bug?
No response
Environment/Setup
No response

I'm going to repurpose this work item to cover adding nullability annotations to the C# implementation.


Add required metadata to publish on the Directus Extensions Marketplace

To publish on the newly added Directus Extensions Marketplace, the package.json file must contain the following:
{
  "directus:extension": {
    "host": "^10.3.3",
    "type": "hook"
  }
}

See: https://docs.directus.io/extensions/marketplace/publishing.html#required-metadata
In addition, your README.md installation instructions (step 1) says to clone the repo to the extensions/hooksdirectory, but Directus now requires all extensions to reside in the root extensions directory.
Thank you for this fantastic extension!

Thanks @robinsonjohn ! I'll do that as soon as possible :)

The extension should appear on the marketplace soon :)

@martabitbrain Sounds great, it will make installation much easier, and hopefully boost the visibility of this great extension.
Thank you


test(client): Regression test for gh-13089

Closes: https://github.com/prisma/prisma/issues/13089
Related: https://github.com/prisma/prisma-engines/pull/3211

I think it's ok, but maybe we want to test more operations with where clauses?

Member

Sure, I added update and delete.


MacBook Pro intel chip

Hello everyone, The code requires NVIDIA CUDA to work but I'm using Mac (intel) is there any solution. I tried running the code with the CPU but it takes forever. is there any solution ?
Thanks

Hello, have find a solution for this issue? I have the same problem on Apple M2 Max.


Medic V2

Allow medic to be mind controller by partner

Profiling metrics are showing medics use 0-2 cpu/tick for 9 mining rooms, which is a major cpu hit from power mining (power miner is 1 cpu). a lot of this is from movement.


Ingress docs are incorrect

The "using ingress" docs in the CDK readme are incorrect.

An ingress controller is provided to you by default and deployed into
the default namespace of the
cluster.

This is incorrect. The nginx ingress controller is deployed in the "ingress-nginx" namespace, not in the default namespace.
As a result, the output of kubectl get pods is incorrect: ingress controller is not shown in this output because it only shows pods in the default namespace.
kubectl get ingress also gives me a slightly different output: the address part is not present in my output.
My output:
$ kubectl get ingress
NAME               HOSTS                           ADDRESS   PORTS   AGE
microbot-ingress   microbot.<IP_ADDRESS>.xip.io             80      11m

$ kubectl get pods
NAME                        READY   STATUS    RESTARTS   AGE
microbot-5b9864df4d-57zfr   1/1     Running   0          12m
microbot-5b9864df4d-lntt2   1/1     Running   0          12m
microbot-5b9864df4d-zlszj   1/1     Running   0          12m

Fix merged.  Thanks for raising @galgalesh.


Repalce RDA with dbRDA

Hi,
I replaced RDA with dbRDA.
There is a minor issue: RDA has scale argument, dbRDA does not have. I added there scaling, but it does not take na.action into account. This means that now scaling is done for all the values. Before it was done only for those values that were specified by na.action. --> slightly different results if there are missing values.
I'm not sure if we should implement na.action also to scaling, since scale is not even implemented in vegan:dbRDA.
Naming: when dbRDA is done with euclidean distances, it equals to RDA. Therefore, I think that the current name (runRDA) is still valid
Issue: https://github.com/microbiome/mia/issues/227
-Tuomas

Faling checks..?

It is related to scaling
"Some constraints were aliased because they were collinear (redundant)" --> because scaling is done inside the rda function the result is different
Now it works, but we should think about that scaling probably

Scaling is not part of the core dbRDA (or RDA) procedure and I think it should be optional.
Examples should therefore show scaling as an extra step before applying (db)RDA on the scaled data. Then the users can choose whether to used scaled or non-scaled data as input to dbRDA.
The Z transformation does scaling. If it does not have na.action argument already then that could be added to the transform* functions. Then the transformSamples would be used to scale the data before dbRDA.
The Z transformation is zero mean, unit variance in its standard form. If we allow shifting or scaling to other values, then a different name might be needed ("scaling"?). But I am not sure if this is really needed right now, perhaps that can be skipped.
The runRDA should be fine for name as you explained.

ready to merge?

After these are passed then it is ready to be merged


[CLI][TESTS] Fix error message when browser is unsupported and add tests for platform utils

Description

The error message when browser is unsupported on the current platform said ERROR: <name> browser is unavailable. Check --help for available browsers. The help section listed this as a valid browser name. This can cause confusion as the reason is that the browser is not supported on current platform.
Added a new function get_platform_name in utils that returns a human readable name of the current platform.
Added rudimentary tests for get_platform and get_platform_name

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] I have read the contribution guidelines and followed it as far as possible.
[x] I have performed a self-review of my own code (if applicable)
[x] I have commented my code, particularly in hard-to-understand areas (if applicable)
[x] My changes generate no new warnings
[x] I have enabled the pre-commit hook and it's not detecting any issue.
[x] Any dependent and pending changes have been merged and published

Thank you for reviewing!

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@c1fc098). Click here to learn what that means.
The diff coverage is 88.88%.

@@            Coverage Diff            @@
##             master     #143   +/-   ##
=========================================
  Coverage          ?   87.68%
=========================================
  Files             ?        5
  Lines             ?      471
  Branches          ?       88
=========================================
  Hits              ?      413
  Misses            ?       35
  Partials          ?       23

Flag
Coverage Δ

unittests
87.68% <88.88%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

browser_history/utils.py
68.00% <85.71%> (ø)

browser_history/generic.py
88.88% <100.00%> (ø)

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 c1fc098...0f7668d. Read the comment docs.


You have onOfType instead of oneOfType - Breaking on React startup

You have a typo in your propTypes section.
Should be oneOfType and not onOfType.

This is a dupe. I see there's a PR for a fix already

Fixed.


Add codes to the directories

Go the specific directories, and create your file for your code

Hey, I would love to add Graph problems.

Hey, can I add DP problems ?


Crawler reached the maxRequestsPerCrawl limit of 100 requests and will shut down soon. Requests that are in progress will be allowed to finish.

how do i overcome this limit?

ignore it


Improve indentation

Indentation is sometimes a bit unpredictable / illogical.  I will illustrate this with some concrete cases.
Pressing ENTER after a WHERE clause indents 4 spaces, but we are outside of any for of nesting, so I was expecting indentation to be zero here:
select * {
  :s [:p :o ]
}
    *HERE*

Pressing ENTER at the position marked *HERE* changes the indentation of that line (it moves to the left):
select * {
  :a :b [
    :c [
      :d :e*HERE*

closed. your second use case is covered, your first one isnt (as that isnt a valid sparql query)


DataTriggerBehavior doesn't appear to work with Nullable types

I cannot get the following DataTriggerBehavior to work with a nullable type; e.g.
double? MyValue = null;
                        <i:Interaction.Behaviors>
                            <ic:DataTriggerBehavior Binding="{Binding MyValue}" Value="{x:Null}" >
                                <ic:ChangePropertyAction PropertyName="Foreground" Value="Red"/>
                            </ic:DataTriggerBehavior>
                        </i:Interaction.Behaviors>

The foreground never turns Red.

Assuming MyValue is a dependency property, leave the CLR property type as double? by change the dependency property type to object and see what happens. :) This bug, by the way, in the dependency framework has finally been resolved and we will see the fix in the Anniversary Update of Windows 10.


Code clean up for routes v2

Please describe the Improvement and/or Feature Request
This issue is to track all the code that needed to be removed/cleaned up when we migrate to routes v2
Scope (please mark with X where applicable)

New Functionality          [ ]
Install                    [ ]
SMI Traffic Access Policy  [ ]
SMI Traffic Specs Policy   [ ]
SMI Traffic Split Policy   [ ]
Permissive Traffic Policy  [ ]
Ingress                    [ ]
Egress                     [ ]
Envoy Control Plane        [ ]
CLI Tool                   [ ]
Metrics                    [ ]
Certificate Management     [ ]
Sidecar Injection          [ ]
Logging                    [ ]
Debugging                  [ ]
Tests                      [ ]
CI System                  [ ]
Project Release            [ ]

Possible use cases

We'll need to update the design docs as part of this work as well.


Filter operation: convolution/correlation

Convolution/correlation are common operations in signal and image processing. Since I tend to use ndarray now for most of my array-type data, it would be nice if it comes with a generic function for those operations.
It probably shouldn't be located in the core crate directly, but a child to contain such kind of operations. I currently have a implementation for the 2D case I move around, but I would be willing to contribute.

That sounds great, we might as well use separate crates for major extensions. For smaller kernel convolutions I'd guess there is a lot to win from having type level size information, but that's something we can punt on for now.
(Core numerics support must be in ndarray since it involves implementing traits like Add and so on, so I'm relatively happy with the included numerics as they are now).

Ok, how should one now proceed?

What do you think about creating a new repo for the new crate? Go ahead and create it. It can be named something with ndarray- prefix and you and I can maintain it both. Can we determine scope and name now? Something like ndarray-signal, ndarray-convolve, or what you like?

Ok, this is now inactive.


Customization of session time out

Many users and IPT administrators/editors want to have a longer time before the session expired. We are trying to setup the time session, but it has to be done modifying the docker and compiling again. We are wondering if is possible to parametrisize this in a simplier way in a customization file.

Thanks @RicardoOrtizG
It's not possible now, but we can make that thing configurable in the future

@RicardoOrtizG How do you customize that please?

Hi! @mike-podolskiy90  I'm sorry for taking a lot of time to answer but I needed confirmation from a third-party TI.
In the file AppConfig.java in the folder config https://github.com/gbif/ipt/blob/master/src/main/java/org/gbif/ipt/config/AppConfig.java in line 85 there is a constant named CSRF_TOKEN_EXPIRATION whit the value 15*60, equivalent to 15 minutes.
The TI explains to me that he has to make a change on this value in order to increase the time of the session, and it implies a modification of the IPT that we are trying to avoid.
The idea of @MattBlissett sounds good to us too.

Thanks @RicardoOrtizG
So let's just increase this property a little? That would be much easier, and more secure I think.
What value do you use please?

I made a consultation within SiB Colombia and we consider 60 minutes is enough time for the session to close. Thanks!

Hello,
I did a PR (https://github.com/gbif/ipt/pull/1731) to allow the customization of the session timeout in the ipt.properties file.
By default (if nothing is set in the ipt.properties file), the value is set to 1 hour.
We had the same requirement in France, especially for training sessions where it's frustating to loose it's pending work.
@RicardoOrtizG , be careful, the CSRF_TOKEN_EXPIRATION is not the session timeout.
It's the CSRF token timeout, which is used to prevent CSRF attack (before the login is done).
To change the session timeout, you need to change the web.xml file, or by code, use the setMaxInactiveInterval on the session object (https://github.com/gbif/ipt/blob/f45b86c1bb374810a04af7dc4eae128f62ba2191/src/main/java/org/gbif/ipt/action/LoginAction.java#L91)
Cheers,
Sylvain

Thanks a lot, @sylmorin-gbif  for the recommendation, we will take this into consideration for further opportunities, for now, I think the 1-hour default configuration will work for us.

Thanks @sylmorin-gbif , I merged the PR. Closing this one


[DOC] Guide on how to add new models

Currently adding new models will require modifying the source code. Adding a new model involves adding different source and header files on C++/CUDA side as well as adding its Python interface. There should be a guide on how to do this.

This is done in 51de7ad8bc97fa103dc5219d9ade7e1173f76ede


APIView should have an option to choose persistent language preference

APIView shows reviews created for all languages by default and user has to select appropriate filter if they want to view reviews for a specific language only. It will be a good option to store user preference and create default view based on user preference. User should still be able to select other languages or unselect to see reviews created for other langauges.

Let's put this in backlog. Language param in URL is good enough to achieve this and any one who wants to see reviews for a specific language can use a bookmarked link to APIView with language param.

SImilar to "sticky filters" that are currently being implemented but this would be persistent.

This has been resolved with the persistence of user preferences


Empty error message for TransactionWriteItems validation error

It appears that not all error messages come from DynamoDB endpoints in lowercase.
For instance, for TransactWriteItems operation, if one of transaction components fails, client gets a Message property instead:

It is seems like a DynamoDB bug, but it's not really clear when this issue should be reported. Having a fallback in this client is the simplest thing we can do.

I assume that update an be more comprehensive, since that message doesn't tell anything especially specific. but at least it gives a direction, which component needs to be checked.

Error: Transaction cancelled, please refer cancellation reasons for specific reasons [None, None, ValidationError]


3.3.0 crashes on map load

Hi,
I have just upgraded RB from 3.2.3 to 3.3.0 and I am always greeted with the following:
268.575 Error AppManagerStates.cpp:1595: The mod Recipe Book (3.3.0) caused a non-recoverable error.
Please report this error to the mod author.
Error while running event RecipeBook::on_init()
RecipeBook/scripts/database/beacon.lua:9: attempt to call field 'from_dimensions' (a nil value)
stack traceback:
RecipeBook/scripts/database/beacon.lua:9: in function 'beacon'
RecipeBook/scripts/database.lua:55: in function 'build'
RecipeBook/control.lua:177: in function <RecipeBook/control.lua:169>
Which other information do you require?
Regards
Tom

You need to update the Factorio Library mod. I negelcted to update the dependency when I released 3.3.0. The dependency has been updated for 3.3.1.


Run the Employee Onboarding Sample Scenario

Tutorial URL: https://developers.sap.com/tutorials/cp-starter-ibpm-employeeonboarding-5-run.html
Please specify the step you are referring to
Hi Archana,
Thank you for the detailed tutorial, I have encountered an issue tutorial 5 of 5 at step 4. The execution log says -
"Determine Equipment" failed
17 Apr 2020, 18:02:16
Service endpoint:
BUSINESS_RULES
Error message:
The OAuth token request to URL 'https://p2000499014trial.authentication.eu10.hana.ondemand.com?grant_type=client_credentials' failed with HTTP status code 403 (Forbidden) and response body '{"error":"Could not verify the provided CSRF token because your session was not found."}'
I have tried in incognito, I have even checked the destination once again and it returns the code 302, not sure if this is causing the problem.
Could you please help me with this?
Vishal

This issue comes because the token url for business rules destination is not correct. check if you have /oauth/token in the end of the token url.

No I have not included yet, do you want me to include?

I tried including as well and it didn't work.. it's still giving me 302.

Hello, I'm also stuck in the same step (Well, I continued with the next steps, and I got an error when I start a workflow instance related to OAuth). Did you find a way to solve it?

Please check your token service URL. It's still not correct. In the end its should have /oauth/token for example: Token Service URL should be: https://p787658trial.authentication.eu10.ondemand.com/oauth/token (also check the setup chapter, its clearly mentioned there)

Thank you, Archana! The issue has been resolved.


[switchdev 1/x] Add additional methods to host/kernel.go

New methods are:

BindDriverByBusAndDevice - binds device to the provided driver
UnbindDriverByBusAndDevice unbind device identified by bus and device ID from the driver

Both methods allows to work with devices not
only on PCI bus.
+refactor driver-related methods
+add unit-tests for changed methods
Context:

part of switchdev refactoring
these changes are required to configure drivers for VDPA devices. VDPA device are on /sys/bus/vdpa, not on /sys/bus/pci

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.2%) to 24.427%

Totals

Change from base Build<PHONE_NUMBER>:
1.2%

Covered Lines:
2430

Relevant Lines:
9948

💛  - Coveralls

/test-all

I personally prefer using literals instead of constants in test code, but I see it's debatable. Just saying that to see if any other has the same preference.

Thanks for the review @zeeke
I thought about your point, and I agree that it is better to use string literals in this case. It is much easier to understand what the test does in this case. I already updated the PR.

LGTM, will merge once CI is green.


Behavior of identifier property seems inconsistent and temperamental

Running on Windows, the following code throws a NullReferenceException:
[Entity]
public interface IEntity
{
    string Id
    {
        get;
    }
}

var entity = new Entity();

// this line throws
var id = entity.Id;

Exception stack (shortened for clarity):
System.NullReferenceException was unhandled
  HResult=-2147467261
  Message=Object reference not set to an instance of an object.
  Source=BrightstarDB
  StackTrace:
       at BrightstarDB.EntityFramework.BrightstarEntityObject.GetIdentityBase()
       at BrightstarDB.EntityFramework.BrightstarEntityObject.GetKey()
       at BrightstarDB_REPRO.Entity.get_Id()

Similar code on iOS has different behavior: it returns null as the value of an unset identifier, but setting it to null will subsequently return string.Empty as the identifier's value.
This can result in a lot of confusion because seemingly innocent code like this:
public static ISomeEntity ToEntity(this ISomeContract @this)
{
    return new SomeEntity
    {
        Id = @this.Id,
        Foo = @this.Foo
    };
}

can result in an entity with string.Empty as its identifier rather than null per the contract.
I don't know enough about the internal workings of B* to offer anything other than an outsider's perspective and expectations on how this could work:

one can always get/set the identifier property without ever getting an exception
getting an unset identifier returns null
setting an identifier to null effectively unsets it. Subsequent retrievals of the identifier would therefore return null

I'll have to look into this a bit more. I can see where you are coming from but for B* the implementation is a bit different from an ORM because the identity of the resource is fundamental. When I added in the composite key support I updated the code to allow an identity to be changed (previously it was immutable) - and I suspect that those changes are responsible for some of the confusion.
It's always good to get another perspective on things as everyone comes to an API with different expectations and I want to try and strive to make sure that B* conforms to the principal of least suprise (at least for most of the people, most of the time!)
Thanks for taking the time to provide this feedback (and all the others) it really is extremely helpful!

You're welcome. Thanks for such a great product!

Hi,
Can you check that this is not a duplicate of #191. The code you provide for Windows looks the same as the code on that bug, so if the problem was related to not having an entity context, that has been fixed. If there is still some other residual problem, just let me know.
Cheers
Kal

Hey,
It could be the same underlying problem, but they're different use cases. In this issue I'm getting the ID whereas in #191 I'm attempting to set it.
Cheers

I think that the notion of unsetting an Id is going to be difficult to support. The URI identifier of the entity is the "hook" on which all of the properties are hung. Unlike a relational table where the row could  still exist if the Id column was set to null, a triple store has no rows, the URI is both primary key and "row" in effect.
However I agree that there should be consistency in the value returned by an unset ID in the case where you are testing a new locally created entity before you add it to a context. And getting the value of an unset ID should return null and not throw an exception.

I just added a repro (see the link above).
The NRE is happening because the static initialization of the context is not performed if you don't create a context object. If you either create a context object first or call the static InitializeEntityMappingStore method on the context class, then you will avoid the NRE.
With that caveat, retrieving an unset id does return null on Windows.

Hi,
This issue is closed but I still see the problem where setting an entity's ID to null results in it becoming an empty string. See the part of my initial message that starts with:

Similar code on iOS

Should I open a separate issue specifically about this?

In a way the code is behaving "as expected" - by not providing an ID you are generating an RDF resource with a URI consisting only of the prefix, then when you ask for the ID again later the code is splitting of the prefix and returning what is left of the URI - which is an empty string.
In practice this sort of thing is dangerous. If you have a prefix it is because you expect multiple distinct IDs to be generated using that prefix. I think it would be better if setting an ID to null or an empty string is disallowed with an ArgumentException being raised. I'll open a separate issue for this.

That would definitely be more helpful than the current behavior. Thanks.


UndoHelper.remove(...) return type changed

I was fetcching the Snackbar created by the Undo Helper by saving the return value of UndoHelper.remove(...).
However it seems that you changed the return type to void  in a commit two days ago (SHA 37a304be45652624a274003c738e5bb208ed653b). That makes it impossible to access the Snackbar.
For some events I want to forcefully hide the snackbar (and execute deletion) before the undo time is over yet. That seems not  possible without accessing the Snackbar (snackbar.dismiss()). Please change return type back to "Snackbar" again.
Thanks in advance!

Yes, I can revert it back. It will be available in the Snapshot version soon.


Bump version to 0.1.2

Coverage remained the same at 100.0% when pulling 3d8f8869d22afb34237cdcbcb9bdeb6bee41e9c1 on update-gem-version into f3439cc6929ebeaa610aa9d76c86b5157953929c on master.

Coverage remained the same at 100.0% when pulling 3d8f8869d22afb34237cdcbcb9bdeb6bee41e9c1 on update-gem-version into f3439cc6929ebeaa610aa9d76c86b5157953929c on master.


Unable to install onnxruntime on MacOS 15

I ran uv sync, and it hrows this error on MacOS 15
Resolved 245 packages in 9ms
error: Distribution `onnxruntime==1.19.2 @ registry+https://pypi.org/simple` can't be installed because it doesn't have a source distribution or wheel for the current platform

Following up here, it's reported as a bug in uv: https://github.com/astral-sh/uv/issues/9228
If you need, you can get around it by selecting a specific version of Python:
 uv venv --python 3.11.10

This will install Python 3.11.10, and then allow you to proceed to follow instructions.


Issues setting up with Appfog

I wanted to learn a bit more about pump.io, so I tried to deploy to Appfog following these instructions:
https://github.com/e14n/pump.io/wiki/Appfog
I tried to deploy the latest tag off of the github repository and ran into the following error:
Creating Application: OK
Creating Service [mongodb-pump]: OK
Binding Service [mongodb-pump]: OK
Uploading Application:
  Checking for available resources: OK
  Processing resources: OK
  Packing application: OK
  Uploading (997K): OK
Push Status: OK
Staging Application 'pump': OK
Starting Application 'pump': .
Error: Application [pump] failed to start, logs information below.

====> /logs/stderr.log <====

node.js:201
        throw e; // process.nextTick error, or 'error' event on first tick
              ^
Error: Unable to load shared library /mnt/var/vcap.local/dea/apps/pump-0-3eb3f60e6f6f25f711a805b8b57d1c70/app/node_modules/bcrypt/build/Release/bcrypt_lib.node
    at Object..node (module.js:472:11)
    at Module.load (module.js:348:31)
    at Function._load (module.js:308:12)
    at Module.require (module.js:354:17)
    at require (module.js:370:17)
    at bindings (/mnt/var/vcap.local/dea/apps/pump-0-3eb3f60e6f6f25f711a805b8b57d1c70/app/node_modules/bcrypt/node_modules/bindings/bindings.js:74:15)
    at Object.<anonymous> (/mnt/var/vcap.local/dea/apps/pump-0-3eb3f60e6f6f25f711a805b8b57d1c70/app/node_modules/bcrypt/bcrypt.js:1:96)
    at Module._compile (module.js:441:26)
    at Object..js (module.js:459:10)
    at Module.load (module.js:348:31)

Any ideas on what to do?
UPDATE:
I tried the process again, this time using the zip of the tag instead of cloning.  It deployed the Appfog without error!  But then immediately crashed.  I'm getting the impression things have changed since the tutorial was written?

@bcomnes did you get installation to work?

Nah.  Gave up.  Just cleaning up old issues that I created. Feel free to reopen if its of any value still.


Feature: Approval config management

As an admin, I can create approval processes on services
Serial process
A service has multiple approval processes that must execute in a hierarchical sequence. If two approval processes are assigned to a service in serial, the approval group in the first approval process must approve the request before notification is sent to the second approval group. Priority of approval process execution is based on its position on the approval process list view. Approval processes at the top of the list will execute before the processes below it.
Parallel process
A service has one approval process containing multiple groups. All groups are notified simultaneously when a request is created and the order is not granted until all groups approve it. Any group that declines the request ends the process and the user is notified the request has been denied.

Dot graph could be added to have a visual on the approval process state
Example 1: one parallel process with 3 group
All group approve

On group reject

Example 2: Serial  process
All group approve

Second approval group reject

erDiagram
    REQUEST {
        int id
        string approval_state
    }

    OPERATION {
        int id
    }

    APPROVAL_GROUP {
        int id
        string name
        string type
    }

    TEAM {
        int id
        string name
    }

    APPROVAL_GROUP_STATE {
        int id
        string approval_state
    }

    REQUEST ||--o{ OPERATION: has
    REQUEST |o--o{ APPROVAL_GROUP: approval_group_status
    OPERATION ||--o{ APPROVAL_GROUP: has
    APPROVAL_GROUP |o--o| APPROVAL_GROUP: next
    APPROVAL_GROUP |o--o| APPROVAL_GROUP: previous
    APPROVAL_GROUP }|--o{ TEAM: has
    APPROVAL_GROUP }o--|| APPROVAL_GROUP_STATE: has
    TEAM }o--|| APPROVAL_GROUP_STATE: has
    REQUEST }o--|| APPROVAL_GROUP_STATE: has

Done and merged and released.


Feature/add percy

This is the most naive possible attempt to add Percy to this repository.
It follows the instructions here:
https://docs.percy.io/docs/gatsby
The Percy key is supposed to be kept out of the codebase, so I haven't committed it to code.  It is in the Netlify deploy keys here: https://app.netlify.com/sites/think-dev-standards/settings/deploys#environment
If this works (and we will see if it does), the Netlify deployment should run gatsby build , which will in turn trigger Percy. Let's see what happens!

Approving so I can rebase @rayng86 's PR onto main and then see what Percy does with PR#2!


Publish to a folder?

Would I be able to publish to a specific folder?
The use case is as follows. I run multiple open-source projects that are al documented at GitHub pages, but that doesn't allow me to publish the beta branch documentation.
Also PR requests that change the documentation should also be visible somewhere.
What I want to do is build the documentation and publish it to the storage account in the folder with the name of the branch. So storage.azurestorage.com/branch-name/index.html
That would make it easy to link to the beta docs or to publish some pr documentation.

Short answer YES!

This wasn't possible when I created the issue right?
I see the option in the readme now!


0.1.30

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 63.15789% with 7 lines in your changes missing coverage. Please review.

Project coverage is 83.25%. Comparing base (ffdcc41) to head (04afa14).

Files
Patch %
Lines

easychart/models/series.py
62.50%
6 Missing :warning:

easychart/__init__.py
50.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           latest      #20      +/-   ##
==========================================
- Coverage   83.44%   83.25%   -0.19%
==========================================
  Files          80       80
  Lines        1764     1780      +16
==========================================
+ Hits         1472     1482      +10
- Misses        292      298       +6

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


impliedrelationship bug

Description
Hi Simon,
It seems there is a not expected error when we just change the order of two relations in a dsl file. Please check Steps to reproduce.
This is a small example of a bug we get often in our bigger project.
Thanks.
Best regards.
Eric PANIER
OPAL-RT TECHNOLOGIES
Steps to reproduce

Load workspace.dsl generates the following error:
 workspace.dsl: A relationship between "SoftwareSystem://SYSTEM_A" and "SoftwareSystem://system_b" already exists at line 1 of /usr/local/structurizr/workspaces/../systems/intersystem_relations.dsl: system_a -> system_b "RELATION_SEND_CMDS" "TECHNO_HTTP" at line 5 of /usr/local/structurizr/workspaces/../systems/systems.dsl: !include intersystem_relations.dsl at line 3 of /usr/local/structurizr/workspaces/myworkspace.dsl: !include ../systems/systems.dsl at line 1 of /usr/local/structurizr/workspace.dsl: !include workspaces/myworkspace.dsl

change the order of the two lines of the file systems\system_a\intercontainer_relations.dsl

Load workspace.dsl then it works correctly
relation_bug_project.zip

Screenshot
No response
Code sample
No response
Configuration
structurizr Lite docker bd8d97bd4f58f3cdc90d90dbd0601bece27c53497ded1db061a206698b042585
Severity
Major
Priority
High
Resolution
I have no budget and there's no rush, please fix this for free
More information
No response

Thank you very much for your responsiveness.
Let me take time to understand. Because I did not catch the order of relation declaration was important between component_a2 -> component_b3 and component_a1 -> component_b3 and how the implied relationship strategy works.


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(package): add nyc from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

Codecov Report

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

@@           Coverage Diff           @@
##           master     #371   +/-   ##
=======================================
  Coverage   85.04%   85.04%
=======================================
  Files           1        1
  Lines         214      214
=======================================
  Hits          182      182
  Misses         32       32

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 a873707...f292915. Read the comment docs.

Coverage remained the same at 85.654% when pulling f2929159f08e5bbdca8af5fcfa4f04f2880f813d on template-sync-1 into a873707a7530e4578069534615da9250b60d3df8 on master.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


refactor: introduce package structure

This PR introduces an internal package structure to better group related code.
The current proposal is

app containing core logic and defining types used throughout the dasbhoard
gateway containing all the kubernetes related code to query Argo CD applications
web containing HTML rendering and request handling for the dashboard

There is also a small CSS fix contained, that shows the "Eclipse Tractus-X" logo and text side by side

"There is also a small CSS fix contained, that shows the "Eclipse Tractus-X" logo and text side by side" Best change! <3


fix angular version cap in bower.json

package.json allows to use this package for versions of angular lower than 1.7.0.
This was not allowed in bower.json: https://github.com/urish/angular-load/commit/693d704c801d95190aaac06ecaafe1ce1c7d825b#diff-b9cfc7f2cdf78a7f4b91a753d10865a2R10
This PR bumps cap for angular version in bower.json
Solves: https://github.com/urish/angular-load/issues/43

Thanks!


Service Worker: Push Notification

https://blog.angular-university.io/angular-push-notifications/
https://github.com/angular-university/angular-pwa-course/blob/1-notifications-finished/src/app/lessons/lessons.component.ts
Need service worker:
https://blog.angular-university.io/angular-service-worker/
ng add @angular/pwa --project <name of project as in angular.json>
# or
ng add @angular/pwa --project angular

Also want push service:
sudo npm install web-push -g

Specific page where this is happening:
ng g c navpages/notification
ng generate service service/notification-post

Will need to have working tests... reference

/label rawDoc

/label "PR Issue (<>)"


fix: Behavior form should prompt anytime you navigate away and there are changes pending

Summary of changes 🔍
Moving all of the state management for the behavior form into a context. This allows us to track every update that is made to the behavior and know whether it has any changes or not. With this information, we can then show a confirmation dialog anytime the user tries to navigate away from the form. These flows include:

cancel form
mode switch toggle (viewer/builder)
breadcrumb navigation

We do NOT show the prompt in any of those cases if no changes have been made OR if the changes were reverted back to matching the original state (ex: add an element and then remove it, then try to navigate, would not get a confirmation)

Product Backlog Item 14504805: Dirty state prompt should be handled more holistically
Fixes issue #472
TODO: Add more unit tests for the context
Testing 🧪
Try everything related to the behavior form and make sure that any change in the form would result in a dialog before navigating away from the form.
Added unit tests for the context

Checklist ✔

[x] Linked associated issue (if present)
[x] Added relevant labels
[x] Requested developer reviews
[x] Request UI review from design / PM
[x] Verify all code checks are passing

The behaviors form alerts tab seems to be keeping edits to the draft even after clicking cancel & discard

The live update behavior preview modal seems to be gone.  Not sure why, but def need that back haha

When in a dirty state on the behaviors form, if you click on the scene name in the breadcrumb, the 'are you sure' dialog opens, but on clicking 'discard' nothing happens - you just stay on the widget form.  widgetFormInfo likely needs to be cleared out somewhere.

Editing an existing widget then clicking 'Cancel' doesn't prompt user with Discard message (if that behavior is covered under this PR)

Edit an existing Widget (changing the value ranges or display name, etc.)
Hit 'Cancel'
Just exits you out of Widgets tab
Click back in, changes gone

The live update behavior preview modal seems to be gone. Not sure why, but def need that back haha

Should be fixed now.

Editing an existing widget then clicking 'Cancel' doesn't prompt user with Discard message (if that behavior is covered under this PR)

Edit an existing Widget (changing the value ranges or display name, etc.)
Hit 'Cancel'
Just exits you out of Widgets tab
Click back in, changes gone

This is expected for now. We are focused on Behaviors atm but it'd be great to get the widgets inline eventually as well.

When in a dirty state on the behaviors form, if you click on the scene name in the breadcrumb, the 'are you sure' dialog opens, but on clicking 'discard' nothing happens - you just stay on the widget form. widgetFormInfo likely needs to be cleared out somewhere.

Update -- the same seems to be true anywhere from the behavior edit form. Clicking the scene name in the breadcrumb opens the dialog, but confirming the discard doesn't do anything

Good catch. I think I've fixed this now. I had a slight regression on a recent commit.


Allow fetching with FormData using FetchService

Problem
FetchService can only be used to fetch with text / binary data in the request body. It should also support other body types like FormData

Let me take care of it

FetchService is no more as of #1842 so I think we should close this.


Npm install failed - angular/Cli - 8.3.12

npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of '@angular/cli'
npm ERR! notarget

The package has been released and is available as shown here: https://www.npmjs.com/package/@schematics/angular
This might be an issue with an intermittent issue with a particular npm mirror.

I don't think its available. can you check once. Because I was trying since yesterday.
Even if I updated to<EMAIL_ADDRESS>- it is looking for<EMAIL_ADDRESS>

Please see<EMAIL_ADDRESS>Published 21 hours ago.

Thank you for reply.
This might be an issue with an intermittent issue with a particular npm mirror. -- Does it take time to get updated.


User's profile lists prolog

The following user reached out to me and said that while his profile lists prolog he hasn't done any.
https://sourcerer.io/komzpa

Issue resolved, profile cleaned.


Implemented Copy Functionality for JSON generator

Description
This feature adds Copy Functionality to JSON Generator
Fixes #420
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)

Checklist:

[X] My code follows the style guidelines of this project
[X] Any new tools are named according to the Tool Naming Convention outlined in contributing.md
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] Any dependent changes have been merged and published in downstream modules

Screenshots (if applicable):

Please Add under hacktoberfest topic

@Bashamega pls add hacktoberfest label


freebsd's libxml2 version info is incorrect

Looks like libxml2's LIBXML_VERSION_STRING and/or xmlParserVersion is being set to 209013 on FreeBSD instead of what we expect, which is 20913, resulting in warnings messages like:
WARNING: Nokogiri was built against libxml version 2.9.13, but has dynamically loaded 20.90.13

I've started looking into how the freebsd port of libxml2 is curated and built. The 2.9.13 changeset is here:
https://reviews.freebsd.org/D34338
but I'm awaiting account activation on that site to comment.

See also https://github.com/freebsd/freebsd-ports/commit/a13ec21cd733f67a9fc0dc00ab45268bdc236246

I've opened an upstream bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263094

Looks like this has been fixed upstream in the freebsd distro: https://github.com/sparklemotion/nokogiri/runs/6062473115?check_suite_focus=true#step:3:6413


gop run panic in 09-AircraftWar

2021/10/01 07:25:29 Member Initialize false // *index
panic: -:  undefined (type *index has no field or method Initialize)
goroutine 1 [running]:
github.com/goplus/gox.(*CodeBuilder).MemberVal(...)
github.com/goplus/gox@v1.7.7/codebuild.go:1376
github.com/goplus/gop/cl.gmxMainFunc(0xc0029b7d40, 0xc002a0b200)
github.com/goplus/gop/cl/class_file.go:160 +0x345
The problem is that calling Initialize function not exist

rm $SPXROOT/.gop/cache


"The square root of 169" causes error

Not sure what kind of error yet, but it errors on the demo site.

This apparently got fixed during the rework of some of the programming parser earlier.


Improving debugger.py

Sorry for the size of this PR. Issues to fix kept growing. See below:
Use typing to make the function signatures clearer.
Use constants for hard-coded values.
Create a helper function for checking file extensions.
Improve the error handling in the walk_directory function.
Use f-strings for better readability and performance.
Add function and module-level docstrings for better understanding of the code.

thats great, thanks so much! the biggest issue with debugger is that context length becomes a problem much sooner than most. would like to fix that next, but happy to discuss what the right approach is in issues (i may move faster than issues here)

i have not merged yet because i'm not sure that this is how i want the code style to be, but also have not closed because i might come around to it

Ok sounds good. Let me know if there's anything else I can do.

you've done great. just share usecases/examples/pain points! i'll be refactoring quite a bit this week to accommodate the enlarged planning.


[Bug?] Odd behavior adding bookmark to keymaps (multiple added in different location)

Steps happening in the gif ^:

<leader>tl: Show bookmarks in Telescope
<leader>tb: Toggle bookmark on line
<C-s>: Save.
<leader>tl: Show bookmarks, single bookmark shows up fine.
<leader>tb: Toggle bookmark on local function map(...) function.
<C-s>: Save... bookmark indicator on the left disappears.
<leader>tl: Show bookmarks. Two new bookmarks show up in the list, neither of them the line I set a bookmark on, and both are on a map function being called at the very end of the file. You can see the bookmark indicators on lines 237 and 239.
<leader>tb: Toggle bookmark on a map on line 15.
<C-s>: Save.
<leader>tl: The indicator again disappears and another entry shows up in the Telescope list of bookmarks. Seems like this new entry is again on the last line/function in the file, though only the two indicators remain on 237 and 239.

plugins/ui.lua:
{
    'tristone13th/lspmark.nvim',
    config = function()
        require('lspmark').setup()
        require('telescope').load_extension 'lspmark'
    end,
},

config/keymaps.lua:
local function map(mode, lhs, rhs, opts)
    opts = opts or {}
    opts.silent = opts.silent ~= false
    vim.keymap.set(mode, lhs, rhs, opts)
end

map('n', '9', '$', { noremap = true, desc = 'Go to end of line' })

map('n', '<C-a>', 'ggVG', { desc = 'Select [A]ll' })

-- Lspmark.nvim
map('n', 'p', function()
    require('lspmark.bookmarks').paste_text()
end, { desc = 'Lspmark [P]aste' })
map('n', '<leader>tb', function()
    require('lspmark.bookmarks').toggle_bookmark()
end, { desc = 'Lspmark [T]oggle [B]ookmark' })
map('n', '<leader>tl', ':Telescope lspmark<CR>', { desc = 'Toggle [L]spmark [T]elescope' })
map('v', 'd', function()
    require('lspmark.bookmarks').delete_visual_selection()
end, { desc = 'Lspmark [D]elete visual selection' })
map('n', 'dd', function()
    require('lspmark.bookmarks').delete_line()
end, { desc = 'Lspmark [D]elete line' })

Maybe it's something with my map function, which follows the format seen above, or it's some other part of my config I have wrong, I'm not sure. Using the bookmarks in other lua files in and out of my dotfiles seems to work fine though. Like just inside a plugin's repo it doesn't seem to have the same 'duplicate incorrect bookmarks' thing.
NVIM v0.9.5

Other minor thing I noticed (not sure if it's expected behavior or not). When adding a bookmark to the top of this loop it adds a second to the end of it as well. When trying to remove the second bookmark on the end of the loop, then saving, it's added back. Also when toggling a bookmark on the single map(...) line inside the loop, a second bookmark is again added to end.
Again, not sure if it's expected or not... and please tell me if it's something to do with the way I've written things :|

Thanks for reporting this bug! I can reproduce it using your file config/keymaps.lua, but I may need some time to debug and fix this.

I see, that's because (symbol kind, symbol name) couldn't identify a unique symbol in a text document, the anonymous functions in each map function call are both assigned a name map which conflicts with the map function defined at the beginning, I need to find a way to fix this, maybe refresh the internal representation of each symbol.

#5 should fix this.


fix(source): workaround avro date default

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Resolves #13505, a bug in upstream apache_avro crate that logical type date cannot parse its default.
The actual fix is at https://github.com/risingwavelabs/avro/commit/d0846a16ce813a225af04ade35b3b8117b137a29
Checklist

[ ] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Can we contribute it back to the Avro official repo?

Specific to this issue: This may not be the right fix, so I used the word "workaround".
General to other avro issues: Yes, and we will have to. The official rust implementation is far behind the specification and other language implementations (eg Java).