stream_info: add downstream handshake completion timing

Signed-off-by: Paul Sohn<EMAIL_ADDRESS>Commit Message: Adds a downstreamTiming field to the connection-level streamInfo for when the TLS handshake completed for HTTP 1/2/3, for monitoring handshake latency.
Additional Description: Note that for HTTP/3 zero-RTT, the handshake may complete well into the life of the request, which is why this field is not copied into the stream-level streamInfo when a stream is created.
Risk Level: Low
Testing: Integration tests included in the PR.
Docs Changes: None
Release Notes: Added

@pksohn this needs some formatting fixes
you can use the diff/artefacts here to fix
https://dev.azure.com/cncf/envoy/_build/results?buildId=113538&view=results

@ggreenway the checks are finally passing for this PR. Any chance you might be able to take a look? Thanks!

@ggreenway @alyssawilk One thing I meant to ask about:
I removed the assertion that the handshake timestamp can only be written once, in this commit: https://github.com/envoyproxy/envoy/pull/22367/commits/61a8618bc246063886be9eba6ecbd4e19521b57e, upon discovering that the SslSocketTest::ClientSessionResumption... tests were failing due to SslSocket::onSuccess being called multiple times.
In practice do we actually expect SslSocket::onSuccess to be called multiple times for the same connection (e.g. on resumption)? If so, would we want the handshake-complete timestamp to be overwritten?

@ggreenway ping!

Would you be willing to add an access log formatter in source/common/formatter/substitutions_formatter.cc, at least for tcp-proxy access logs? I think this new field is generally useful so I'd like to make it more easily available.

Thanks -- I think I've added what you were suggesting.

@pksohn can you fix CI? Then I'll ping the reviewers again to try to make some progress.
/wait

/wait on coverage

/retest

@alyssawilk: there was a question above that we were hoping you could weigh in on (namely whether to move this metric into the SSL connection or leave it in downstream timing): https://github.com/envoyproxy/envoy/pull/22367#discussion_r941792000

I think you need to merge main to pick up #22792


Add a list of models and parameters to the documentation

Having a list of currently available models and the respective free parameters in the documentation would make it easier for new users to get started with Stage 5.
I have something similar like this for PACMAN (an HST pipeline). See here: https://pacmandocs.readthedocs.io/en/latest/models.html

Yeah, we still don't have anything on Stage 5 at all, so I'll start working on that.


Dashboard/project UI issues as user account role

All issues reproduced under user-account role (not admin!):

Deploy 2 Vms, volumes in a user account
Create a project under a user account -> the project tab doesn't refresh; next try to add an account (say admin) -> the account tab doesn't refreshes. Finally deploy 1 VM, volumes in that account.
Go to project dashboard, you'll see 1 VM; now switch to default view -> you'll see dashboard does not refresh/change

ISSUE TYPE

Bug Report

COMPONENT NAME

UI

CLOUDSTACK VERSION

4.15, 4.16/main

cc @Pearl1594 @shwstppr @davidjumani @nvazquez @sureshanaparti @weizhouapache

@davidjumani @utchoang I could reproduce the issues, simply clicking Compute -> Instances as a user and then Projects makes the projects list to not being refreshed, however I can see the notification at the top. Any idea on this issues?

@rhtyd @nvazquez regarding step #2 i.e., On creation of a project - the project tab doesn't auto-refresh, I was able to reproduce the issue, but on clearing the cache - surprisingly things worked as it should i.e., Project tab auto refreshes on creation of a new project


User Assigned Browser Window Names in the "All Windows" Pane

Description
Currently, the "All Windows" pane uses a naming convention for open windows that completely ignores the actual names a user assigns to their browser windows. The current convention of meaningless window names such as "CurrentWindow", "Window 1", "Window 2", etc. is not helpful when the T3 user has more than a few browser windows open.
Use case
If this feature were added and the "All Windows" pane were to use the user assigned browser window names, then the T3 user experience would be greatly improved because the window name would immediately guide the T3 user to the information they are seeking and save a lot of time.
Alternatives
Because the "All Windows" pane has the above noted naming convention hard-coded, there is no possibility of a user workaround. Changes in the T3 UI would be required to either allow the user to assign window names from within the "All Windows" pane or otherwise internal logic would need to be added to capture the window name from the Chrome native feature that enables users to assign names to browser windows.
Additional context
Please see the attached screen capture for further illustration of this feature request.

@WebWorX-io
Thank you for submitting this issue.
I also share the same concern, but unfortunately, the current Chrome extension API does not support retrieving window names.
Once the API provides this capability, I plan to update the extension to include this feature.


feat(postgres): Connection to database in backend

I have added pg dependencies to establish a connection with PostgresSQL. I have also added an endpoint that fetches all the entries of antennas in the database.

#32 #22


How do i change button color?

How do i change button color?
If i can't can you add a option to change button color?

Setting the BootstrapType on a button changes its color, you can do this either through XML or code. As the purpose of the library is to use predefined colors/sizes from Bootstrap I don't see why there should be an option to change the button color - however, if there's a lot of popular demand I will reopen this. It should be relatively easy to create your own fork if you want to alter the backgrounds available.

@jamie-beardedhen
+1 I would also like to see this feature in upcoming releases.

+1 Me too, I would like to see this feature.

Fixed in 2.0.0, use the BootstrapBrand interface to define custom styles

How do i define my own custom style and using it in app:bootstrapBrand ?

Firstly, Library/Res/values/colors.xml add your style like: #373a3c,
Secondly Library/Res/values/attrs.xml add custom syle name like:
After, com.beardedhan.androidbootstrap/api/defaults/DefaultBootstrapBrand.java define your style like DENEME(R.color.bootstrap_brand_deneme) and add to switch(attrValue) case 5:
return DENEME; , I Hope understand me :)

Updates to README are required due to frequency of this question


Uncaught Error: ENOENT: no such file or directory, scandir '/Users/Sachdev/AtomBackups'

[Enter steps to reproduce below:]

...
...

Atom Version: 1.8.0
System: Mac OS X 10.11.5
Thrown From: config-import-export package, v0.3.1
Stack Trace
Uncaught Error: ENOENT: no such file or directory, scandir '/Users/Sachdev/AtomBackups'
At fs.js:856

Error: ENOENT: no such file or directory, scandir '/Users/Sachdev/AtomBackups'
    at Error (native)
    at Object.fs.readdirSync (fs.js:856:18)
    at Object.fs.readdirSync (ATOM_SHELL_ASAR.js:497:28)
    at ImportView.module.exports.ImportView.attach (/Users/Sachdev/.atom/packages/config-import-export/lib/config-import-view.coffee:40:16)
    at atom-workspace.commandSubscription.atom.commands.add.config-import-export:import (/Users/Sachdev/.atom/packages/config-import-export/lib/config-import-view.coffee:19:42)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61)
    at CommandRegistry.module.exports.CommandRegistry.dispatch (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:160:19)
    at AtomEnvironment.module.exports.AtomEnvironment.dispatchApplicationMenuCommand (/Applications/Atom.app/Contents/Resources/app.asar/src/atom-environment.js:1100:28)
    at EventEmitter.outerCallback (/Applications/Atom.app/Contents/Resources/app.asar/src/application-delegate.js:327:25)
    at emitTwo (events.js:87:13)
    at EventEmitter.emit (events.js:172:7)

Commands
     -4:34.1.0 core:select-all (atom-text-editor.editor.mini.is-focused)
     -4:26.3.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -1:08.0 core:paste (atom-text-editor.editor.mini.is-focused)
     -1:07.5.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -1:01.5.0 core:select-all (atom-text-editor.editor.mini.is-focused)
     -1:01.3.0 core:paste (atom-text-editor.editor.mini.is-focused)
     -0:59.1.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -0:01.1.0 config-import-export:import (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "themes": [
      "atom-material-ui",
      "atom-material-syntax"
    ]
  },
  "config-import-export": {
    "defaultPath": {
      "darwin": "/Users/Sachdev/AtomBackups",
      "freebsd": "",
      "linux": "",
      "sunos": "",
      "win32": ""
    }
  }
}

Installed Packages
# User
atom-material-syntax, v0.4.6
atom-material-ui, v1.2.13
config-import-export, v0.3.1
file-icons, v1.7.15
fonts, v1.5.0

# Dev
No dev packages

This is the third time this error has been reported here. For each of the previous two errors the solution was to manually create the missing directory. The question needs to be asked why is this a repeatedly reported error? Is there a problem with the directory being automatically created or a problem with the documentation requiring the user to create the directory manually?

The package should ask for an import / export directory instead of "assuming" a hardcoded directory.  This would also enable users to select a folder in Google Drive, OneDrive, Dropbox, network drive or an usb drive
This would greatly improve the user friendliness.


"Publish" and "Switch to Draft" button not updating the DB

Bug Description

"Publish" and "Switch to Draft" button are not making actual changes in the DB, currently, the user needs to click additional "Update" or "Save draft" for these to make a change.
Expected Behaviour
"Publish" and "Switch to Draft" button should directly Publish or Switch to Draft without the user having to click additional "Save" after clicking the button.
Ideally, we should also display a confirmation for publishing!

Steps to Reproduce

Add a Story
Click "Publish"
Refresh.
See the Story is still a Draft.

Screenshots

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria
QA Instructions

@obetomuniz Can you move the ticket to QA or done when it complete. Also when you reference a ticket in a PR, can you use the correct keywords.


[data-export] Implement query plan

Is your feature request related to a problem? Please describe.
It would be great to have the query plan from data export page
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_query_explain.htm

Help article link to display around the query plan toggle for more explanation
https://help.salesforce.com/s/articleView?id=000386864&type=1


Odd issue with follow and group functionality in WP6

When following a member from the Members page or from a profile the request never completes (it keeps circling) but if you refresh the page it has worked. I've seen a similar issue with groups buttons, but the groups seem to work intermittently.

I can replicate this in multiple browsers with a test user, but not with an admin user. Admin users experience the expected result.

I'm experiencing a similar issue to this when requesting group membership to a private group. When I click the "request membership" button, nothing happens, and when I refresh the page it shows the request was sent. However, in my group admin account, I never received any membership requests.
Shortly after, in the group, I started having issues with the "as the only admin, you cannot leave the group" error message. Not sure if these are related?

I got another weird popup just clicking on groups in the sidebar after logging in Something funky is going on with this page I think. Javascript issue?

Now that I think about it I left a group yesterday. Could this be the delayed popup thing we saw previously that KF mentioned in chat?

Every time I log in as myself (bonnie) I get this popup when I click on the groups link in the left-hand sidebar:

I am also able to replicate Larissa's issue above where I requested membership in Dave's Test Group 2 as myself. The request membership button disappeared, but the request never made it to Dave. It's gone in the ether.

I think there are two underlying issues here.
Issue #1 - A user can remain logged-in to WordPress after their SAML session is expired.
When the page reloads, they will be removed from all groups and societies because the membership data that is expected to be passed to WordPress from the SAML session is not present. This commit makes it so that if there is no membership data available, leave a user's memberships unchanged. A possible problem with this is if a user never logs out, they could remain in societies / groups they have been removed from. I'm not sure how long a user is able to remain logged-in to WordPress.
https://github.com/MESH-Research/humanities-commons/commit/d5047b29ea1249cf2e5e549277f92fd04e72efc8
Issue #2 - A bug in the buddypress-followers plugin
When a user is follower or unfollowed, the buddyprss-followers plugin generates an email notification. There is a bug in that function where a string value is treated as an array:
function bp_follow_new_follow_email_notification( $args = '' ) {
	...

	// Check to see if this leader has already been notified of this follower before
	$has_notified = bp_get_user_meta( $r['follower_id'], 'bp_follow_has_notified', true );

	...

	// Not been notified before, update usermeta and continue to mail
	$has_notified[] = $r['leader_id'];

         ...

In the above snippet, $has_notified is returned as a single value rather than an array, because the third parameter in the function call is set to true rather than false (see: https://www.buddyboss.com/resources/reference/functions/bp_get_user_meta/ ). It is then treated as an array below, which causes an exception to be thrown and the AJAX call returns an error so the Follow button never leaves the spinning state even though the user was followed. Setting the third parameter to false so that $has_notified is an array seems to fix the problem.
I think this is a PHP compatibility issue rather than a WordPress 6.0 issue. We recently updated to PHP 7.4.
The buddypress-followers plugin has not been updated in 6 years ( https://wordpress.org/plugins/buddypress-followers/ ). I don't think we can abandon it easily, however, as it is part of our core functionality.
For now, I think this means we have to fork the plugin. 🤮

The buddypress-followers plugin has a newer version on its GitHub page ( https://github.com/r-a-y/buddypress-followers ) than is available on the wordpress.org plugin repository. The newer version corrects the above bug. Switching to that addresses the issue.
This commit removes a now-redundant spinning animation created by BuddyBoss. The plugin now creates this animation so BuddyBoss was causing there to be two spinners.  https://github.com/MESH-Research/boss-child/commit/5d757ba8511f55df251cdb63811b48673076f6ea

There is a handler that is supposed to force-reload the page when you join / leave a group ( https://github.com/MESH-Research/boss-child/blob/7107b5288cc0b317332aff2e783f2e6a8f363400/js/boss-child.js#L1 ). Because the live() function was deprecated (https://api.jquery.com/live/) the handler wasn't being called, so the page wasn't force-reloaded and the user didn't immediately see the notification.
This commit addresses that issue: https://github.com/MESH-Research/boss-child/commit/7107b5288cc0b317332aff2e783f2e6a8f363400
The resulting user experience is, imo, pretty terrible, but I think it is operating as designed.


Experiments Plugin

I would like some way to record simple experiments.
A python CLI tool. Then a plugin for llm.

For a given input, create multiple requests varying the parameters and rank the responses


Update package references and use new features

Hi @heaths, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Heath Stewart). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

:white_check_mark: Build vssetup.powershell 1.0.35-rc+g65199e639f completed (commit https://github.com/Microsoft/vssetup.powershell/commit/65199e639f by @heaths)


Update information for Marvin Beckers

Hey folks! 👋🏻
I would like to add some more information to my profile, so here is a PR that updates things and puts them a bit more into standard (I think the personal website in the bio is kind of unusual, and there's a field for it anyway).
I'm a little confused about slack vs slack_id. Many entries have the slack field, but slack_id seems to be the right one according to schema.json. If this correction is not accurate, please let me know and I will drop it from the commit.

Thanks for calling this out. I've replaced all "slack" attributes with the correct "slack_id". This caused conflicts in this PR, so I made the changes you wanted manually. If I made an error or you want something else changed, please open a new PR.


Fix IResolvers type

[x] If this PR is a new feature, reference an issue where a consensus about the design was reached (not necessary for small changes)

[x] Make sure all of the significant new logic is covered by tests

[x] Rebase your changes on master so that they can be merged easily

[x] Make sure all tests and linter rules pass

[x] Update CHANGELOG.md with your change. Include a description of your change, link to PR (always) and issue (if applicable). Add your CHANGELOG entry under vNEXT. Do not create a new version number for your change yourself.

[x] blocking

I believe that the IResolvers type is incorrect as  according to the resolvers documentation it should provide support for the example under Unions and interfaces.
const resolverMap = {
    Vehicle: {
        __resolveType: (obj, context, info) => "Object",
    },
};

In addition, whilst not mentioned in the documentation, I believe the below should also be allowed, so I added the possibility of IResolverObject having itself as a property:
const resolverMap = {
    Query: {
        Vehicle: {
            resolve: () => true,
            __resolveType: (obj, context, info) => "Object",
        },
    },
};

I also added the source & context generics whilst doing this.

Great work, thank you!


Restore Defaults Button Not Working

In the options menu, the Restore Defaults button doesn't work, it doesn't do anything and is not clickable. Tested in Chrome and Firefox.

Fixed in 26b3e8e10565b4a46ebfb9520f000a9a77b09480. Knew I would forget something, thanks for catching that. Let me know if you find anything else I missed; I was working on it pretty late.

@KorySchneider I don't think this is fixed. the button is clickable and the message pops up but the setting for Default Command doesn't reset.

Did some more testing, sometimes the reset button works but it doesn't change the setting, sometimes nothing happens until I restart the browser, sometimes nothing happens at all.

You're right, I overlooked something. The options do get reset but the selected options don't change, so when you hit 'Done' it overwrites them.

Really fixed in 8144f5aebc5e471beded6b9b99f78cb50c3abc9d


Torrent from similarly named TV Show, "Space: 1999" showing up in the list for "Spaced"

Not sure if this is correct place to report data problems, but here goes:
In the list of streaming options for S01E01 of Spaced (1999–2001), I'm getting an option that references this torrent, which is from another show, called Space: 1999 (1975–1977).

https://app.strem.io/shell-v4.4/?#/detail/series/tmdb:745/tt0187664:1:1

Should be fixed once the caches expire


how can we make 2 lines in the TextDrawable ?

like this ? any suggestion ?

I guess that  gray transparent circle, with about 4dp border and an arc along its  border, I can't implement it but if someone it interested it would be nice


Fix tags on repo

refs #58

Job VTB Documentation, step Sync Docs on 7494485 wanted to post the following:
View the site here
This comment will be updated on new commits.

Only changes doco and doco passed


issues when running on macOs

Hello, I am running a project with solid_queue.
When doing some development on my windows pc with WSL, solid_queue runs greatly! However, when running on my macbook, I get either get file descriptors or weird reading errors:
Bad file descriptors:
10:16:17 jobs.1 | [SolidQueue] Restarting fork[5568] (status: 1)
10:16:17 jobs.1 | [SolidQueue] Starting Worker(pid=5592, hostname=Carloss-MacBook-Pro.local, metadata={:polling_interval=>0.3, :queues=>"*", :thread_pool_size=>4})
10:16:48 jobs.1 | /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/processes/interruptible.rb:21:in `wait_readable': Bad file descriptor (Errno::EBADF)
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/processes/interruptible.rb:21:in `interruptible_sleep'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/worker.rb:29:in `run'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/processes/runnable.rb:48:in `block (2 levels) in do_start_loop'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/activesupport-7.1.3/lib/active_support/execution_wrapper.rb:92:in `wrap'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/app_executor.rb:7:in `wrap_in_app_executor'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/processes/runnable.rb:47:in `block in do_start_loop'
10:16:48 jobs.1 |       from <internal:kernel>:187:in `loop'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/processes/runnable.rb:44:in `do_start_loop'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/processes/runnable.rb:39:in `start_loop'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/processes/runnable.rb:15:in `start'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/supervisor.rb:123:in `block in start_fork'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/supervisor.rb:122:in `fork'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/supervisor.rb:122:in `start_fork'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/supervisor.rb:152:in `replace_fork'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/supervisor.rb:134:in `block in reap_and_replace_terminated_forks'
10:16:48 jobs.1 |       from <internal:kernel>:187:in `loop'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/supervisor.rb:130:in `reap_and_replace_terminated_forks'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/supervisor.rb:51:in `block in supervise'
10:16:48 jobs.1 |       from <internal:kernel>:187:in `loop'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/supervisor.rb:47:in `supervise'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/supervisor.rb:26:in `start'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/supervisor.rb:14:in `start'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/tasks.rb:4:in `block (2 levels) in <main>'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/task.rb:281:in `block in execute'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/task.rb:281:in `each'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/task.rb:281:in `execute'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/task.rb:199:in `synchronize'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/task.rb:199:in `invoke_with_call_chain'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/task.rb:188:in `invoke'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:182:in `invoke_task'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:138:in `block (2 levels) in top_level'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:138:in `each'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:138:in `block in top_level'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:147:in `run_with_threads'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:132:in `top_level'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:83:in `block in run'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:208:in `standard_exception_handling'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:80:in `run'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/exe/rake:27:in `<top (required)>'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/bin/rake:25:in `load'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/bin/rake:25:in `<top (required)>'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/3.3.0/bundler/cli/exec.rb:58:in `load'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/3.3.0/bundler/cli/exec.rb:58:in `kernel_load'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/3.3.0/bundler/cli/exec.rb:23:in `run'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/3.3.0/bundler/cli.rb:451:in `exec'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/3.3.0/bundler/vendor/thor/lib/thor/command.rb:28:in `run'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/3.3.0/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/3.3.0/bundler/vendor/thor/lib/thor.rb:527:in `dispatch'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/3.3.0/bundler/cli.rb:34:in `dispatch'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/3.3.0/bundler/vendor/thor/lib/thor/base.rb:584:in `start'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/3.3.0/bundler/cli.rb:28:in `start'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/bundler-2.5.3/exe/bundle:28:in `block in <top (required)>'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/3.3.0/bundler/friendly_errors.rb:117:in `with_friendly_errors'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/bundler-2.5.3/exe/bundle:20:in `<top (required)>'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/bin/bundle:25:in `load'
10:16:48 jobs.1 |       from /Users/carlos/.rbenv/versions/3.3.0/bin/bundle:25:in `<main>'
10:16:49 jobs.1 | [SolidQueue] Restarting fork[5592] (status: 1)

end of file reached error:
10:25:29 jobs.1 | <internal:io>:63:in `read_nonblock': end of file reached (EOFError)
10:25:29 jobs.1 | 	from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/processes/interruptible.rb:22:in `block in interruptible_sleep'
10:25:29 jobs.1 | 	from <internal:kernel>:187:in `loop'
10:25:29 jobs.1 | 	from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/processes/interruptible.rb:22:in `interruptible_sleep'
10:25:29 jobs.1 | 	from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/worker.rb:29:in `run'
10:25:29 jobs.1 | 	from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/processes/runnable.rb:48:in `block (2 levels) in do_start_loop'
10:25:29 jobs.1 | 	from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/activesupport-7.1.3/lib/active_support/execution_wrapper.rb:92:in `wrap'
10:25:29 jobs.1 | 	from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/app_executor.rb:7:in `wrap_in_app_executor'
10:25:29 jobs.1 | 	from /Users/carlos/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/solid_queue-0.2.2/lib/solid_queue/processes/runnable.rb:47:in `block in do_start_loop'

this happened both when running via the puma plugin or starting solid_queue via Procfile.
It still run jobs if I enqueue them. However the worker crashes often.
Workaround so far is to run inside docker

I think I have the same issue on my mac. A piece of the message is solid_queue | /Users/natannobrechaves/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/pg-1.5.4/lib/pg/connection.rb:690: [BUG] Segmentation fault at 0x000000011d5b0b0e.

using rosetta to run your terminal (iterm for me) also seems to do the trick!
https://apple.stackexchange.com/questions/428768/on-apple-m1-with-rosetta-how-to-open-entire-terminal-iterm-in-x86-64-architec

nvm.. pulled trigger too early. fails with rosetta as well

@natannobre I'm also having the same issue. Seems like it has been solved earlier here: https://github.com/rails/solid_queue/issues/145#issuecomment-1954024164

Hey @ArglosStudios, is this still happening for you? Did https://github.com/rails/solid_queue/issues/145#issuecomment-1954024164 help at all?

I have this issue but with a MySQL backend (I don't have the option to swap it for another DB).

Hey @rjhancock, does this still happen for you? Are you running the last version?

Just tested with latest gems for everything and this is the error I get.

Huh, this one seems to be similar or the same as https://github.com/brianmario/mysql2/issues/1163 🤔
It seems it affects Rails's parallel testing too: https://github.com/rails/rails/issues/41176
There's a suggested solution here: compile mysql2 with a MySQL 5.7 client. Do you think this could work for you?

Sadly no as deployed MySQL is 8.0 same with local MySQL via Homebrew.

That's ok! You can continue using MySQL 8.0, this is just for the mysql2 gem. You can compile it against a MySQL 5.7 client and continue using it to access a MySQL 8.0 server.
This is what @johnmaxwell proposed here:
gem uninstall mysql2
brew install<EMAIL_ADDRESS>gem install mysql2 --<EMAIL_ADDRESS>

When I test my Solid Queue code, I just run it within Docker Compose. Not ideal but works. I'd rather not add another monkey patch to the instructions and code base for a bug in one of two libraries that would bring my development environment more out of line from the production environment.

That makes sense! I wonder why you get the error then 🤔 In theory, this happens only in macOS, so I assumed you were running everything in your local machine.

Only happens on macOS. When running via Docker Compose, runs fine. The servers are all Ubuntu boxes running dockerized containers with Ruby 3.3.4 as the base image.
I try not to run the images inside Docker while working on the code as it greatly slows things down over all. I generally don't need to test the Job system as it's already well tested.
Most of the code I can run without working with queues so it doesn't impact too much. Just wish the bug could be found as looking through the solutions it looks like this has been a bug somewhere for the last several years.

I recently switched to Omakub and ubuntu for development due to a number of macos related issues after the ARM on mac transition for this exact reason.. Like you, I run on production using kamal and docker containers (on x86_64 hw) so being on ubuntu helps me more accurately replicate production. Would be nice to identify a root cause though.


fix: LEAP-861: Resolve CUDA runtime error issue

Fixed runtime error with executing ML backend in CUDA environment with gunicorn:
RuntimeError: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method

More details in the issue

Codecov Report
Attention: Patch coverage is 11.11111% with 8 lines in your changes are missing coverage. Please review.

Project coverage is 46.45%. Comparing base (e7a5d97) to head (eb77277).

Files
Patch %
Lines

label_studio_ml/wsgi.py
0.00%
8 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #452      +/-   ##
==========================================
- Coverage   47.03%   46.45%   -0.59%
==========================================
  Files          13       13
  Lines         640      648       +8
==========================================
  Hits          301      301
- Misses        339      347       +8

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

It looks like all of the test suites are running the SAM test, which is failing for unknown reasons:
ERROR label_studio_ml/examples/segment_anything_model/test_predict.py
!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!


Swan PKCE

Respond to: https://bithyve-workspace.slack.com/archives/C02H7PTBXQX/p1644937749470259

Closing this issue as discussed with dev.


Add colors and names to loggers.

Add colors based on logs severity when a logger print in stdout/stderr.
Also add the possibility to name the logger, allowing to have the bomberman logger and the raylib logger in stderr.
Resolves: #93

Codecov Report

Merging #101 (3900140) into master (5017897) will decrease coverage by 0.49%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #101      +/-   ##
==========================================
- Coverage   24.28%   23.78%   -0.50%
==========================================
  Files          67       67
  Lines        1186     1198      +12
  Branches      412      420       +8
==========================================
- Hits          288      285       -3
- Misses        783      789       +6
- Partials      115      124       +9

Impacted Files
Coverage Δ

src/logger/Logger.cpp
24.00% <0.00%> (-7.75%)
:arrow_down:

src/logger/Logger.hpp
25.00% <ø> (-25.00%)
:arrow_down:

src/main.cpp
0.00% <0.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 5017897...3900140. Read the comment docs.


Update CONTRIBUTING.md

added link to fmriprep style guide in order to check off NMIND item

Changes proposed in this pull request

Documentation that should be reviewed

@tsalo can you merge this PR? it's just a minor update

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 44.22%. Comparing base (8bb6c0d) to head (75dbdeb).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #896   +/-   ##
=======================================
  Coverage   44.22%   44.22%
=======================================
  Files          66       66
  Lines        9835     9835
  Branches     1096     1096
=======================================
  Hits         4350     4350
  Misses       5262     5262
  Partials      223      223

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


Matmul and reduce in lazy mode fails with ArgumentError

Hi @willow-ahrens,
I implemented triangle counting (SpA @ SpA * SpA), it runs for eager mode but decorating with @sparse.compiled to run lazy mode fails with:
ERROR: ArgumentError: Please supply initial value for reduction of Any with +.
Stacktrace:
 [1] initial_value(op::Function, T::Type)
   @ Finch ~/JuliaProjects/Finch.jl/src/interface/lazy.jl:114
 [2] reduce(op::Function, arg::Finch.LazyTensor{Any, 2})
   @ Finch ~/JuliaProjects/Finch.jl/src/interface/lazy.jl:127
 [3] sum(arr::Finch.LazyTensor{Any, 2})
   @ Finch ~/JuliaProjects/Finch.jl/src/interface/lazy.jl:74
 [4] top-level scope
   @ REPL[5]:1

Here's a code snippet to reproduce it:
using Finch

A = Tensor(Dense(Dense(Element(0.0))), 10, 10)
res = sum(tensordot(A, A, ((1,), (2,))))

A_lazy = Finch.LazyTensor(A)
res = sum(tensordot(A_lazy, A_lazy, ((1,), (2,))))  # fails

this looks like a type inference failure. somehow tensordot lost the types of things.


Domain validation not working for subdomains

Hello - the latest DSS exe is working well overall.  Oddly obtaining the following result when running a set of domains with EXE for ftpc.fpcusa.com:
ftpc.fpcusa.com 0	invalid domain name	 spf: We couldn't detect any active SPF record for your domain. Please visit https://dmarcguide.globalcyberalliance.org to fix this. bimi: We couldn't detect any active BIMI record for your domain. Please visit https://dmarcguide.globalcyberalliance.org to fix this. dkim: We couldn't detect any active DKIM record for your domain. Please visit https://dmarcguide.globalcyberalliance.org to fix this. dmarc: You do not have DMARC setup! domain: Your domain looks good! No further action needed. mx: You do not have any mail servers setup, so you cannot receive email at this domain.

Interactively checking with EasyDMARC online at the following link https://easydmarc.com/tools/domain-scanner?referred_landing=false&domain=ftpc.fpcusa.com returns results for SPF, DKIM, and DMARC:

The Windows CMD line I'm using:
dss.exe scan -t120 -n<IP_ADDRESS>,<IP_ADDRESS> -a -f csv < domainsin_01.19.2024.csv > results_out_2024.csv

Hey @OrlandoMD!
The error to focus on is the following:
scanResult:
    domain: ftpc.fpcusa.com
    error: invalid domain name

Looks like our basic domain parser that validates domains before running any checks doesn't qualify subdomains correctly. Thanks for the bug report!

@OrlandoMD this should now be fixed :) Please let us know if you continue to experience issues!


Use of DB::transaction in queued job results in missing failed_job record for database queued driver.

Laravel Version: 7.19.1
PHP Version: 7.4.7
Database Driver & Version: MySQL 5.6

Description:
We are using horizon for queue management but we have set in cofiguration that failed jobs are written in database for better management.
We have a job that performs logic inside DB::transaction. When this job fails it can be found in horizon dashboard in failed job but it's not in database failed_jobs table. It is saved in Redis but not in MySQL.
When debugging MySQL audit logs for that specific connection we can see in order:

START TRANSACTION statement
the select and insert statements that our code does
insert into failed_jobs statement
DISCONNECT statement
The transaction is never committed thus the failed_job is not actually written in.

Also we did receive notification that is issued from
 Queue::failing(function (JobFailed $event) {
 // code that sends notification
 });

Steps To Reproduce:
Setting queue driver to database and hitting this endpoint
Route::get('/test-queues', function () {
    dispatch(function () {
        \Illuminate\Support\Facades\DB::transaction(function () {
            throw new \Exception('Exception from DB transactions');
        });
    });
});

should be enough to see that the failed job is not in failed_jobs table

I think the behaviour is expected.
Is it possible to configure a different connection to write to failed_jobs?
Then that wouldn't be considered part of your business logic transaction and wouldn't be rolled back.

I can't replicate this. The transaction is rolled back once an exception is detected and then we re-throw the exception for the worker to catch and add the job in the failed_jobs table.
The example code you shared works as expected and the job was sent to the failed_jobs table. The issue seems to be somewhere else in your application code.


[api evolution] Make all public enums into structs with static properties

We need to do the usual trick of
public struct Thing {
  let underlying: _Thing

  internal enum _Thing {
  case example
  }

  public static example = .init(.example)

  internal init(_ underlying: _Thing) {
    self.underlying = underlying
  }
}

to ensure future API compatibility -- for example for all settings, like singleton allocation strategy etc.

This is required for 1.0

For errors the dance is even more involved:
public struct SomeError: Error, Sendable {
  let underlying: _Storage

  internal class _Storage {
    let error: _SomeError
    let file: String
    let line: UInt
  }

  internal enum _SomeError {
  case something(...)
  }

  internal init(error: _SomeError, file: String = #fileID (or path? I forgot?), line: UInt = #line) {
    self.underlying = .init(error: error, file: file, line: line)
  }

  var description: String {
    "(Self.self)(\(error: \(underlying.error), at: \(underlying.file):\(underlying.line))
}

or something like that...
Did I get that right @fabianfett @glbrntt ?

Thanks for double checking :)


Impact Of Warning Messages

Hello,
During different phases of training I get various warning messages. I'm sharing all warning messages I receive as below:

UserWarning: "ImageToTensor" pipeline is replaced by "DefaultFormatBundle" for batch inference. It is recommended to manually replace it in the test data pipeline in your config file.

DeprecationWarning: `np.float` is a deprecated alias for the builtin `float`. To silence this warning, use `float` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.float64` here.

UserWarning: Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.

UserWarning: Setting MKL_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.

UserWarning: The key "bbox" is deleted for more accurate mask AP of small/medium/large instances since v2.12.0. This does not change the overall mAP calculation.

.venvs/mmdet/lib/python3.9/site-packages/mmdet/models/roi_heads/mask_heads/mask_point_head.py:304: UserWarning: __floordiv__ is deprecated, and its behavior will change in a future version of pytorch. It currently rounds toward 0 (like the 'trunc' function NOT 'floor'). This results in incorrect rounding for negative values. To keep the current behavior, use torch.div(a, b, rounding_mode='trunc'), or for actual floor division, use torch.div(a, b, rounding_mode='floor').

Do these error messages have any significant impact on the performance of the inference model I'm training? Thanks.

These warnings will not affect the training and testing performance.

@RangiLyu thanks for your quick and clear response.


Kinesis Elasticsearch Sink: stop verifying number of fields in enriched event

So the sink won't break if new fields are added to the end of the TSV.

I think we should log a warning if the number of fields in the incoming enriched event TSV isn't as expected.

As in to stdout/err? Sounds fair...


Inconsistent scala 2.11.x dependency

Hi,
My project is constrained to scala 2.11.8, and the scala-json-rpc 1.5.0 release depends on scala 2.11.8, but its dependency play-json_2.11 , depends on scala 2.11.7.
I can't find any scala-json-rpc release that has a consistent scala 2.11.8 dependency.   The team is adamant , we need this, so it looks like my only options is either to fork this project and create a release myself, or maybe have a release put on this github repo?
Thanks
Max

Hi. I'd like to help, but I first need to make sure I understand the problem so I can be sure of what the solution should be.
Can you confirm what problem the inconsistency causes for you? Is it that you have strict dependency conflict resolution enabled and SBT fails when updating due to the patch version mismatch? Or does it not fail (standard dependency conflict resolution), but give an eviction warning? It would help if you could share a minimal example build definition that demonstrates the problem.

Hi,
We have a rather large shared codebase with different teams working on it.
Some time back issues were reported by some users using Maven, in scala.reflect.internal were it breaks between 2.11.6 and 2.11.8.   The problem arises when you have transitive dependencies on something relies on one of these packages.
It was decreed for stability reasons, to not have dependencies that have inconsistent scala versions, citing http://docs.scala-lang.org/overviews/core/binary-compatibility-of-scala-releases.html.
I'm sure there may be ways to work around this, but the reality on these large codebases is that it's not always practically easy to do or get past the gatekeepers.
This prevented me from adding a dependency to this scala-json-rpc, and I resorted to a private fork, where I basically have the latest version of your code, but running with scala 2.11.8 and play-json 2.6.0-M7 (which depends on scala 2.11.8).
Hope this helps and we can converge on an official release.
Thanks

So if we were to do an official release of scala-json-rpc for this, would you want it to depend on Scala 2.11.8 and play-json 2.6.0-M7? Is there no non-milestone release of play-json that would suffice?
What do you think an appropriate version number would be for it? It's just that I don't think e.g. 2.0.1 or 2.1.0 would make sense and there aren't any immediately obvious alternatives that come to mind.

Yeah, it's a bit unfortunate, but looks like for play-json, only milestone releases depend on 2.11.8.   Not sure what you do with that to be honest.  Does that leak into your versioning and your release also becomes a M release?  Should we ask for a official release of play-json with a non-milestone release?
Maybe it's a big ask,.  I mean,  what we have works now, so if it's I suppose it's something for you to keep in mind in future releases.   Inconsistent scala dependencies can cause issues with binary compatibility.  Eventually we will upgrade scala release going through the whole process again

Yeah, it's unfortunate. I don't think a scala-json-rpc release is the right way to fix it though.


Add kubridge

It's a bit of a shame that I had to manually copy instead of using the install command, but it should work just fine.

It seems the license should be GPL 3+


is there any chance for independent developer to data persistence with google and amazon service limited

hi, I carefully read the doc you contributed.
But Google and Amzon service in my country are limited, and I'm a independent developer with no company.
Do I have any chance or ways to make my data persistence?
Br

Would need more details on that one.
Are you referring to the platform self hosting deployment ? If so that platform is available to anyone here and self deployment is only intended for companies that have privacy requirements.

yes, I mean self hosting deployment, but sorry, my network is limited can not visit your website.
I noticed you can provide docker for self hosting right? I'm not sure if I satisfy the requirements to use it.
Is it possible that the ordinary user can implement their "host" for data persistence? Many thx


[Bug]: Chroma collection is always empty for local persistence

What happened?
I am using local persistence, files are saved. However, each time I load, it creates new files. The list_collections function always return none.
import chromadb
from chromadb.config import Settings

WORKING_DIR = '../..'
CHROMA_STORAGE_PATH = os.path.join(WORKING_DIR, 'bin', 'chromadb')

full_path = os.path.abspath(CHROMA_STORAGE_PATH)
print(full_path)
full_path = os.path.abspath(CHROMA_STORAGE_PATH)

assert os.path.exists(full_path), f"The path {full_path} does not exist."

chroma_client = chromadb.Client(
    Settings(
        chroma_db_impl="duckdb+parquet",
        persist_directory=CHROMA_STORAGE_PATH))
collections = chroma_client.list_collections()

if not collections:
    print('Chroma collection is empty')
for collection in collections:
    print('Retrieved chroma collection with name: %s %s',
                    collection.id, collection.name)

Versions
chromadb                      0.3.26
Relevant log output
Chroma collection is empty

@jma7889 are you using many clients? This usually happens when the way atExit handles cleanup... it will auto-persist the first client last which makes it look like it is wiping the db.
Sorry about this! we are considering taking out the magic entirely since it seems to bite a lot of people.

@jeffchuber I don't intend to use many or more than 1 client. The only place I get client is using code above. I do use it in jupyter notebook, so the code might be called more than once. And each time it seems create a new set of files but list collections always return None.


If applied this commit updates the asset's url's

The problem

When cloned and ran locally , the assets such as the CSS , JS files , few routes & img's were not being loaded as the src url generated for them was not pointing to the correct location.

Solution

Asset's src url's updated to use laravel's url() helper to generate
fully qualified correct url to the asset location.

@introwit Thanks so much!


Reset the media store state if collection state changes

Fixes

Fixes #3976 by @zackkrida
Description

This PR adds clearMedia call to the search store's function setting the collection state. This makes the setCollectionState similar to setSearchStateFromUrl. To make sure that we don't clear media when non-collection state params change (for instance, if we add filters to the collection views, or if we add page parameter to the frontend URL to improve pagination), we first check if the collectionParams are different.
Testing Instructions

Go through the following steps and check that the linked issue is fixed (step 5):

Run the app locally using just frontend/run dev
Make sure the additional_search_views feature is enabled: http://localhost:8443/preferences
Search "rabbit" from StockSnap only: http://localhost:8443/search/image?q=rabbit&source=stocksnap
Click on a single result, then a tag
Observe that the tag view is not filtered to only show StockSnap results. You can refresh and see the same results.

Checklist

[ ] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[ ] My pull request targets the default branch of the repository (main) or a parent feature branch.
[ ] My commit messages follow best practices.
[ ] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible errors.
[ ] I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

I wanted to try and review this PR, but it doesn't have any testing instructions so I'm not sure how best to proceed 🙂 I do have one question.

Sorry, I updated the instructions :)


Setup Jest and add basic unit tests

Builds currently fail because of an issue with Jest, MyCryptoHQ/ui#65


fix: remove pylint from CI

This pylint check is far too pedantic and often just wrong. It is reasonable, for instance, for some functions (rare ones!) to have 7+ arguments.
It also works on some code that is semantically identical to other code that fails: that's too flaky.
Drop it from CI.
Additionally, all the CI steps ran twice - once for the push, once for the pull. That's silly.

@ef0xa
I would not remove it since this is a publicly-maintained repo. We should still have some pylint check. I agree it's too much and unreasonable at some of its rules. I probed our current files and ranked the top 20 most common pylint disable comments here. These should just be disabled globally since it's obviously ignored by now:
 120 line-too-long
  66 import-outside-toplevel
  43 too-many-arguments
  41 unused-argument
  41 broad-except
  37 invalid-name
  34 protected-access
  23 broad-exception-raised
  22 too-few-public-methods
  19 W0613
  17 broad-exception-caught
  10 too-many-locals
  10 too-many-instance-attributes
  10 too-many-branches
  10 no-member
   8 unused-import
   8 signature-differs
   8 no-self-use
   8 import-error
   8 duplicate-code

I can suggest a .pylintrc file that will do the job

@deanq , I'm fine with either way, but what you added to my PR adds a big .pylintrc and still leaves them disabled. Let's do one or the other.


Dev

This merge was difficult because the changes in readme file caused a conflict. this would have been easier to resolve in the dev branch


Reflect latest changes from single file ontology to the split ontology and shapes files

Okay, thanks Pete.

@rivettp There are some things missing like class Domain and the property dprod:offersDistribution has been replaced by isAccessServiceOf
Maybe you just copy the existing artifacts as is from dprod.tll to the corresponding files?

@rivettp Can you add the classes Protocol and Domain in the ontology file and the corresponding Shapes ?
Also can you remove the belongsToDataset property? It is superseded with the isDistributionOf


Add ids key in body when saving/removing tracks - Fixes #193

Even though the requests work without ids, it's a good idea to include it so they match the documentation.

Coverage remained the same at 88.957% when pulling f0b6b52df72ca9862e9eb981234fea741ba00853 on jperez/fix-193 into 803fe10a527a7e4065e58932777b0de6a6853c22 on master.


Cleaned up code to make it more C++11/14 enabled

Changes

pass retained ctor params by value and std::move into place in order to enable move semantics (passing by const ref in those cases is a pessimization)
return movable types by value instead of const value, to enable move semantics. Returning by const value is a pessimization in those cases, and useless in every case except for return by const ref
use unique_ptr instead of shared_ptr for pimpl members, where possible
pass shared_ptr by const ref instead of by value in cases when ownership is not transferred/shared, to avoid useless refcounting
pass vectors and std::functions by const ref instead of const value
use static (ie. translation unit local) linkage for all the non-exported symbols in SetReplace.cpp

Comments

the net effect of all these shallow changes is a 20k (~12%) reduction in binary size, as well as presumably an (yet-unmeasured) increase in performance

Examples

Add explicit inputs and outputs (as screenshots in case of graphics) showcasing new functionality.

This change is

For some reson, our CI passed this build. Upon further review, all the tests in were not passed. See our contributing guidelines to see how to run unit tests. Please make sure all tests are passed on your local machine before opening a pull request.
Once you fix these issues, push again to this branch and I will review your changes again.

For some reson, our CI passed this build. Upon further review, all tests were not passed. See our contributing guidelines to see how to run unit tests. Please make sure all tests are passed on your local machine.
Once this is fixed, push again to this branch and I will review your changes.

Hi,
I am currently unable to run the tests on my machine because this paclet requires WolframEngine 12.1 and the freely downloadable version (Mac) is 12.0.1. Can you help me or point me to the correct way of getting WolframEngine 12.1?
Thanks!

Most of this pull request has been obsoleted by changes made in one of the upstream branches. I'll submit the remaining fixes as a series of smaller pull requests.


Review param intrisic value and clamped values

A few changes on the parameters:

use mul_add when possible (no visible perf change on my side)
review how intrisic_value is handled according to min and max, it adds a loop but:

no visible perf change again,
make the added test pass
more simple to reason about: intrisic_value and computations are always exact disregarding the nominal range, only the buffer and the current_value are clamped

For the record I tried to change AudioParamProcessor::buffer to  ArrayVec<f32; RENDER_QUANTUM_SIZE> but it seemed to spoil the perfs compared to pure Vec (which feels kind of weird, but...)

Thanks, this definitely is better than clamping and then using the clamped value for the next automation.
I will merge this already. And I am looking forward for the fix (and unit test :) ) you have in mind for clamping the full intrinsic + added values.


Fixed performance issue on ios comparing dates

Closes https://github.com/web-ridge/react-native-paper-dates/issues/383
https://github.com/user-attachments/assets/da1b2335-e34f-441d-9d4c-cd821ef7c9a7

Good job bro!


notifications: Use a dynamic SVG favicon for unread counts

Closes #2304. Followup to #15802. Replaces #16534.
Rewritten for improved visual design, better display for large counts, and an integrated PM dot (no more flashing!). This embeds a subsetted copy of the Source Sans Pro font into the SVG, as that seems to be the only way to convince browsers to use it.
Testing Plan: Run notifications.update_unread_counts(unread_count, pm_count) in the browser console.
GIFs or Screenshots:

Hmm, the font is working in Firefox but not in Chrome. Someone else has the same problem.

I accidentally found a bizarre workaround for Chrome: it works if I pre-load the SVG using an Image object before setting it as the favicon.

Looks great, merged, thanks @andersk!  We'll want to do a feedback thread on chat.zulip.org to determine if we want to do some visual tweaks.  (I do notice that the white halo is smaller here than in the old icons, which could make the unread count less readable, but feel like we need more data to know if that's a problem; the old white halo was ugly).


FPET- 301 bundling release3.1 changes(NOT Ready FOR MERGE)

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/FPET-301
Change description
Bundling Release 3.1 (Bundling changes
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ X] No

Not required


Implement disjointed statics

I'm not super enthused about the impl duplicating much of disjointed_slice, and certainly wants some more test coverage, but it works sufficiently enough for initial review of the approach.
The initial vision for #81 allowed using unsized types for the static (e.g. dyn Trait), but to avoid silently introducing extra indirection, this restricts disjointed statics to sized types. For dyn Trait injection, you can use &dyn Trait as the static type. However, no shorthand is provided for linking static IMPL: Concrete to such a declaration, and downstream must create the correctly typed static themselves. This is at least in part due to the moderate difficulty of hygienically naming the correct item type from downstream.
This feels a little bad for linking fn(), since ending up with &fn() is kind of silly. We might want for a separate "disjointed fn" which links the function item instead of a static item.
closes #81

... oops, didn't fix the nonwindows cfg. Had to go afk after submitting this but I'll fix that when I get back.

Potential alternative name: #[linkme::injected]. With that name I'd consider it important to work for fn items directly. I might have an idea that could work well, but it just as likely might fall short.

I have not gotten a chance to review this yet — sorry about the delay. I am still occupied with a different project (which I had though might be done by now, but isn't). If I were to add you on linkme as a maintainer, could you merge this yourself, or get a review from anyone else and then merge? Of course, I am not sure whether this defeats your intention for putting the new macro into this crate as opposed to your own crate.


support debug go+ and go

For remote debugging, the attribute must point to the absolute path to the package or binary to debug in the remote host’s file system even when is specified.  substitutePath
https://github.com/golang/vscode-go/blob/master/docs/debugging.md?plain=1#L173

For remote debugging, the attribute must point to the absolute path to the package or binary to debug in the remote host’s file system even when is specified. substitutePath
https://github.com/golang/vscode-go/blob/master/docs/debugging.md?plain=1#L173

we can add:
"substitutePath": [
{ "from": "${workspaceFolder}", "to": "/path/to/remote/workspace" },
...
]


Request: Support property values in queries

It would be great to select on game object property values. I'm not sure what the best approach is.
Some examples:
// Find all children under Foo that are enabled
var xxx = root.SelectAll("Foo[go('activeSelf') == true]");

// Find all children under Foo whose y position is less than 1
var xxx = root.SelectAll("Foo[trans('position', 'y') < 1]");

Both of these can be achieved by using LINQ as scene query returns an IEnumerable for SelectAll or a GameObject for SelectOne. In this case we will use the SelectOne and then use the Children function to get an IEnumerable of all child game objects.
So assuming foo is a root object we can to the following.
// Find all children under Foo that are enabled
var results = SceneQuery.SelectOne("/Foo")
    .Children()
    .Where(go => go.activeSelf);

// Find all children under Foo whose y position is less than 1
var results = SceneQuery.SelectOne("/Foo")
    .Children()
    .Where(go => go.transform.position.y < 1.0f);

Unfortunately this doesn't work for my use-case. I created a couple of game components that allow the developer/designer to specify multiple object paths using strings inside the inspector. At run-time I pass them to your asset and use the results to dynamically bind objects together.
I did this to avoid having people touch the code. The LINQ implementation is nice but you have to write code.

Unless I'm missing something this issue shouldn't be closed.
This bug breaks some examples on the main page and your article "Scene query recipes for Unity". Anytime you have a "." after a "?" this bug will kick in.

Sorry I missed the intended use you were you were looking for however Unity Scene Query was intended to be used by programmers. What you are suggesting while interesting does not fall under the intended scope or our day to day use.
If you implement such a feature we are open to pull requests.


Dev tools plugin

I'd recommend updating the name to dev-tools.  "dev" suggests it's for the development environment.

Use the new Description annotation to expose the documentation.

Compiles locally.
Some tests did not pass locally.


New GIT stuff in 16.8 limited!

[Enter feedback here]
I am really disliking the changes in 2019 ( 16.8) with regards to GIT
How to you do rebase a branch in the newest version?
This really is a step backwards and is not the only thing which has changed and is now either not there or make no sense... and it is highly annoying!

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bcf2704e-ef04-e4ab-88ba-48533fa62d21
Version Independent ID: e59a9067-775b-d9df-94b7-29076dbfbf25
Content: Update your branch history with rebase - Azure Repos
Content Source: docs/repos/git/rebase.md
Product: devops
Technology: devops-code-git
GitHub Login: @vtbassmatt
Microsoft Alias: macoope

I much preferred the "older" way pre (16.8), it was so much easier, and quicker to get stuff down. could we not have the best of both!, please i really feel like this is a step backwards
This is specially to the GIT options  in the Team Explorer

@Seabizkit Thanks for your feedback! It looks like you've encountered an issue with the product itself, rather than an issue with the documentation. To make sure it gets in front of the right people, please submit your bug here.

well i can say that it was all fixed which is great. 16.10.2 maybe have been one release before this. but its all working again, so thanks


add clock effect

1. Tell us something about your changes.
And another effect. Just my little contribution to make this project even more awesome.
2. If this changes affect the .conf file. Please provide the changed section
3. Reference an issue (optional)
Note: For further discussions use our forum: forum.hyperion-project.org

thx! can you add a json schema  file. This is located in effects/schema. This file is needed for the effect configurator and json validation

//done

@7h30n3
i noticed after some testing that the minutes are at the wrong position for me.
Has it something to do with 12h 24h format?
Actually 15.00 o'clock is shown has 15.25.
Thanks for any help

@brindosch
I have to admit, I programmed this effect long time ago, but today it did a couple of tests with the Hyperion Effect Dev Kit.
At first  my setting (in main.py of the dev kit):
horizontal_led_num = 16
vertical_led_num = 9
first_led_offset_num = -17
leds_in_clockwise_direction = True
has_corner_leds = True
So my (50)LEDs start in the bottom middle of the TV, however I have to define an offset of 25 inside the clock.json the see the time displayed the right way. So offset inside clock.json is different form the first_led_offset.
I will look deeper into it at the weekend. Maybe you can solve your/the problem in the meantime.
It would be very good, if there would be a function to get the offset configured in hyperion, something like hyperion.ledCount

When you design the effect as an image instead of writing to the led stripe directly,then point 0,0 is always top left.
I done this in the light-céock effect

Considering that there is already an clock effect with less configuration effort maybe we just should delete this one here.

//fixed and made a cleanup, you had a lot of vars and steps which have been never applied. Also i added a option for the markers to define them from ui (or disable them with -1)
https://github.com/brindosch/hyperion.ngBeta/blob/webb/effects/clock.py
Currently the clock effect of redPanther doesn't need a specific configuration, but i don't like the gradients. I wanted to add here anyway some options. Maybe one with and one without. And free editable colors.
I like the markers, could be also a good idea for redPanthers effect

@brindosch
I have seen the changes you made at:  https://github.com/brindosch/hyperion.ngBeta/blob/webb/effects/clock.py
Looks much better now. For markers maybe you should consider something like this:
marker = hyperion.ledCount/4
markers = (0, int(marker), (2*marker), int(3*marker))

So you can get rid of the option in the json-file.

Nice, as always don't forget the offset :)
I consider to keep it, but without a .json file. As everyone needs to adjust this. (But depends on how well i could adjust redPanthers clock)
So, one last question and as i have no idea of python.
I don't get a float here for the hour (at least it looks so), even forced with float(). I wanted to make it more precise.
Hints appreciated :)
https://github.com/brindosch/hyperion.ngBeta/blob/webb/effects/clock.py#L39

My clock runs backward...
Am i getting younger?

 Maybe there should be a boolean to define the direction.
@brindosch I can't see any mistake in the function you mentioned. If I type this line in the python console (Python 3.6.0b3) and print the result I get a float value:
Let's assume its: 12:43
Start cmd.exe
python
>>> hmin = float(12+(1/60*43))
>>> print(hmin)
12.716666666666667

Same result without float().
You should also consider using round() inside/instead of int() (lines 45, 48, 51), so for example if you use:

Python 2: int(round(12.716))  becomes 13 and not 12

Python 3: round(12.716)  becomes 13 and not 12

Correct - I would have fixed it myself but am zoo busy playing with some led device driver code

#395

Thank you for investigation, maybe a issue with py 2.7.
i think refer  to a inconsistent value is bad.
Am 10.02.2017 2:57 nachm. schrieb "penfold42"<EMAIL_ADDRESS>
#395 https://github.com/hyperion-project/hyperion.ng/issues/395
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hyperion-project/hyperion.ng/pull/383#issuecomment-278947650,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APOlv95JAWIzH8G4pEEDKEBFeBbnl4JNks5rbGzbgaJpZM4L3mNq
.


Handle despawn

Including a couple of fun little demos that I modified to test that it works.

I think commands.remove_one::<T>(entity) will return an error result if the entity does not have such a component. We could do let _ = commands.remove_one::<T>(entity); to ignore the result entirely. That said, I liked having the checks and warnings printed because it lets you know when something is leaked and until we fix that, that could be useful. What do you think?

I think commands.remove_one::<T>(entity) will return an error result if the entity does not have such a component. We could do let _ = commands.remove_one::<T>(entity); to ignore the result entirely.

This sounds reasonable. If the component isn't there that means it has already been removed somehow, and we should be OK with that since we would have removed it anyways.

That said, I liked having the checks and warnings printed because it lets you know when something is leaked and until we fix that, that could be useful. What do you think?

In what case exactly could we end up with a leak?

That said, I liked having the checks and warnings printed because it lets you know when something is leaked and until we fix that, that could be useful. What do you think?

In what case exactly could we end up with a leak?

For now for example we can’t handle removal of joints without changes to rapier. Arguably we should just fix that though. I’ll make a PR over there soon unless someone beats me to it.

For now for example we can’t handle removal of joints without changes to rapier. Arguably we should just fix that though. I’ll make a PR over there soon unless someone beats me to it.

I implemented the joint removal in the version 0.3.1 of Rapier. So if this was the only case where we would end up with a leak, I'd suggest to use the simplified despawn system without the hash-maps and the eprintln!().

I merged the bevy 0.3 changes from #24, so merge that first. I simplified as much as I could but the HashMaps had to remain as the components are gone already so we can't use query.get_component::<Component>(entity) to look them up. And I added two joint despawn examples to test that they work too.

All good, thanks!


Question regarding image shape for perceptual loss

Hi,
I wonder why we should reshape image to 256 x 256 ,
even though the default image shape for VGG is 224 x 224.
Thanks!

This model doesn't use imagenet pretrained vgg, so it doesn't need to be restricted on 224px resolutions. (By the way, vgg also uses 256px for evaluation.)

Thanks for your kind reply!


WCM Inbox Felix Console Plugin throws Traversal error

Required Information

[X] AEM Version, including Service Packs, Cumulative Fix Packs, etc: 6.4 (possibly earlier)
[X] ACS AEM Commons Version: 3.19.0
[X] Reproducible on Latest? yes

Expected Behavior
WCM Inbox should list the inbox paths available for purging.
Actual Behavior
WCM Inbox throws a traversal error and fails to query the inbox paths to purge.
19.12.2018 18:04:04.154 *WARN* [Thread-110] org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor Traversed 1000 nodes with filter Filter(query=select e.[jcr:path] as [jcr:path], e.[jcr:score] as [jcr:score], e. *from [nt:base] as a inner join [nt:base] as b on ischildnode(b, a) inner join [nt:base] as c on ischildnode(c, b) inner join [nt:base] as d on ischildnode(d, c) inner join [nt:base] as e on ischildnode(e, d) where name(a) = ‘wcm’ and isdescendantnode(a, ‘/home’) and name(b) = ‘notification’ and name(c) = ‘config’ and name(d) = ‘subscriptions’ and e.[type] = ‘page’ option(traversal OK) /* xpath: /jcr:root/home//wcm/notification/config/subscriptions/* [@type=‘page’] option(traversal ok) */, path=/home//*, property=[:localname=[wcm]]); consider creating an index or changing the query

Steps to Reproduce
Invoke the ACS Commons WCM Inbox Web Console plugin (ensure you have enough nodes under /home to trigger the traversal) or Explain Query the query used [1] and see that it is a traversal.
[1] https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/bundle/src/main/java/com/adobe/acs/commons/wcm/impl/WCMInboxWebConsolePlugin.java#L81
Thanks to Sammit P. for identifying

@justinedelson this appears to be a feature to support the clearing of Inbox tasks for ClassicUI - and i believe Inbox Tassk are now stored under /var/taskmanagement (or their respective projects folders) and not the rep:User.
Should we remove this feature for 4.0.0 (since it doesnt work)?  WDYT?

Classic UI is a dinosaur.  Kill it.

I'm fine removing this, but my preference would be to leave the plugin in place for 4.0.0 and just output something like "This web console plugin has been removed for performance reasons" when you navigate to it. That way there aren't questions about where it went (in case anyone is using it).
See https://github.com/Adobe-Consulting-Services/acs-aem-commons/pull/1643

Hi Justin,
I just want to more appropriate on the topic.
Yes, I have same warning message in my server which says as below:-
18.06.2019 23:53:05.942 WARN [Thread-414] org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor Traversed 2000 nodes with filter Filter(query=select e.[jcr:path] as [jcr:path], e.[jcr:score] as [jcr:score], e.* from [nt:base] as a inner join [nt:base] as b on ischildnode(b, a) inner join [nt:base] as c on ischildnode(c, b) inner join [nt:base] as d on ischildnode(d, c) inner join [nt:base] as e on ischildnode(e, d) where name(a) = 'wcm' and isdescendantnode(a, '/home') and name(b) = 'notification' and name(c) = 'config' and name(d) = 'subscriptions' and e.[type] = 'page' option(traversal OK) /* xpath: /jcr:root/home//wcm/notification/config/subscriptions/* [@type='page'] option(traversal ok) /, path=/home//, property=[:localname=[wcm]]); consider creating an index or changing the query
The version of ACS Common package I'm using in my instance is 3.8.4. So, it will resolve the issue if I use higher of it?
Rakesh

Rakesh - this is fixed (Ie the plugin is effectively removed) in v4.0.0 of acs commons. You should upgrade to 4.x if possible.

Hi @davidjgonzalez,
Thanks a lot for the response.
So, now I'm planning to push the 4.x.x package in instance but the only worry is to understand the dependency of this package.
It would be great if you can share some info regarding this.
Rakesh

@trakeshkumar34  check out ... https://adobe-consulting-services.github.io/acs-aem-commons/pages/releases/4-0-0.html

Hi @davidjgonzalez,
Thanks for the link much needful.
Rakesh

We have had the same error in AEM 6.5.1, ACS AEM 4.1
03.12.2019 01:02:34.835 *WARN* [Thread-903] org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor Traversed 1000 nodes with filter Filter(query=select e.[jcr:path] as [jcr:path], e.[jcr:score] as [jcr:score], e.* from [nt:base] as a inner join [nt:base] as b on ischildnode(b, a) inner join [nt:base] as c on ischildnode(c, b) inner join [nt:base] as d on ischildnode(d, c) inner join [nt:base] as e on ischildnode(e, d) where name(a) = 'wcm' and isdescendantnode(a, '/home') and name(b) = 'notification' and name(c) = 'config' and name(d) = 'subscriptions' and e.[type] = 'page' option(traversal OK) /* xpath: /jcr:root/home//wcm/notification/config/subscriptions/* [@type='page'] option(traversal ok) */, path=/home//*, property=[:localname=[wcm]]); consider creating an index or changing the query
But WCM Inbox is deactivated.
https://loalhost/system/console/wcm-inbox

This web console plugin has been removed as it is specific to the Classic UI.

Is there any other option where we can find this Traversal Error?

We upgraded to ACS version to 4.2.0 and are on AEM 6.4.4 and are still getting the WARN and after a certain amount of nodes an ERROR. WCM Inbox is deactivated also.
WARN [Thread-115] org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor Traversed 1000 nodes with filter Filter(query=select e.[jcr:path] as [jcr:path], e.[jcr:score] as [jcr:score], e.* from [nt:base] as a inner join [nt:base] as b on ischildnode(b, a) inner join [nt:base] as c on ischildnode(c, b) inner join [nt:base] as d on ischildnode(d, c) inner join [nt:base] as e on ischildnode(e, d) where name(a) = 'wcm' and isdescendantnode(a, '/home') and name(b) = 'notification' and name(c) = 'config' and name(d) = 'subscriptions' and e.[type] = 'page' option(traversal OK) /* xpath: /jcr:root/home//wcm/notification/config/subscriptions/* [@type='page'] option(traversal ok) /, path=/home//, property=[:localname=[wcm]]); consider creating an index or changing the query

Hi All,
Based on earlier updates, we spent effort in upgrading to latest ACS versions, but still no luck with resolving issue.
@justinedelson Can this be fixed? Can we get some updates at least?
@All,  Any other suggestions that can be done to get rid of this error.
13.01.2020 12:21:29.559 WARN [Thread-1618] org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor Traversed 7000 nodes with filter Filter(query=select e.[jcr:path] as [jcr:path], e.[jcr:score] as [jcr:score], e.* from [nt:base] as a inner join [nt:base] as b on ischildnode(b, a) inner join [nt:base] as c on ischildnode(c, b) inner join [nt:base] as d on ischildnode(d, c) inner join [nt:base] as e on ischildnode(e, d) where name(a) = 'wcm' and isdescendantnode(a, '/home') and name(b) = 'notification' and name(c) = 'config' and name(d) = 'subscriptions' and e.[type] = 'page' option(traversal OK) /* xpath: /jcr:root/home//wcm/notification/config/subscriptions/* [@type='page'] option(traversal ok) /, path=/home//, property=[:localname=[wcm]]); consider creating an index or changing the query

Hi Akash,
Do you use classic UI?
Rakesh
On Tue, 14 Jan, 2020, 02:01 akashramchandani<EMAIL_ADDRESS>wrote:

Hi All,
Based on earlier updates, we spent effort in upgrading to latest ACS
versions, but still no luck with resolving issue.
@justinedelson https://github.com/justinedelson Can this be fixed? Can
we get some updates at least?
@ALL https://github.com/ALL, Any other suggestions that can be done to
get rid of this error.
13.01.2020 12:21:29.559 WARN [Thread-1618]
org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor Traversed
7000 nodes with filter Filter(query=select e.[jcr:path] as [jcr:path],
e.[jcr:score] as [jcr:score], e.* from [nt:base] as a inner join [nt:base]
as b on ischildnode(b, a) inner join [nt:base] as c on ischildnode(c, b)
inner join [nt:base] as d on ischildnode(d, c) inner join [nt:base] as e on
ischildnode(e, d) where name(a) = 'wcm' and isdescendantnode(a, '/home')
and name(b) = 'notification' and name(c) = 'config' and name(d) =
'subscriptions' and e.[type] = 'page' option(traversal OK) /* xpath:
/jcr:root/home//wcm/notification/config/subscriptions/* [@type
https://github.com/type='page'] option(traversal ok) /, path=/home//,
property=[:localname=[wcm]]); consider creating an index or changing the
query
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/1635?email_source=notifications&email_token=AMSXL77VQSJV2C3JCRIS373Q5TFT5A5CNFSM4GLLOKV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI2FVNY#issuecomment-573856439,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMSXL73JLVSGJSXYNPFD6FDQ5TFT5ANCNFSM4GLLOKVQ
.

We don't use classic UI. Rarely for something important, we use classic UI.
Just trying to understand more, when does this occur. Is it when we access classic UI? Or when purging activity takes place.
Suggestion, can't we create index here that can improve performance and avoid this issue?

We spoke with Adobe directly. Workaround is
Stop the component in  /system/console/components ->notification: com.day.cq.wcm.notification.impl.NotificationManagerImpl and to keep it stopped by using ACS-commons component disabler
https://adobe-consulting-services.github.io/acs-aem-commons/features/osgi-disablers/component-disabler/index.html

Hello @palbiez,
We also have ACS Commons 4.0.0 but still, see this error in our logs.
You have mentioned that the workaround was provided by Adobe. Just wanted to understand if this has been logged in somewhere so that we can also check with our AMS team to make sure we implement the same. Not sure what function this component serves.
Thanks
Ruchi

Hi Ruchi,.
Just wanted to know in your application do you use any classic ui
components??
Rakesh
On Mon, 18 May, 2020, 11:29 ruchimishra<EMAIL_ADDRESS>wrote:

Hello @palbiez https://github.com/palbiez,
We also have ACS Commons 4.0.0 but still, see this error in our logs.
You have mentioned that the workaround was provided by Adobe. Just wanted
to understand if this has been logged in somewhere so that we can also
check with our AMS team to make sure we implement the same. Not sure what
function this component serves.
Thanks
Ruchi
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/1635#issuecomment-629963660,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMSXL72BLI7HM53TCVCOH7LRSDFFBANCNFSM4GLLOKVQ
.

@ruchimishra
This component is deprecated and used by old UI. Normally in the WCM inbox you can see messages from AEM. But this inbox is not longer in use.
As mentioned the wordaround is to deactivate inbox service in AEM Admin.
Stop the component in /system/console/components ->notification: com.day.cq.wcm.notification.impl.NotificationManagerImpl and to keep it stopped by using ACS-commons component disabler
https://adobe-consulting-services.github.io/acs-aem-commons/features/osgi-disablers/component-disabler/index.html

@trakeshkumar34, @palbiez,
Our content authors don't use the classic UI. There could be some random usage but we certainly don't need the inbox. Will disable it.
Thanks a lot for the help and input.

Just to be clear, it appears that most of the comments in this thread do not relate to ACS AEM Commons. The query used by the WCM Inbox web console plugin (which was removed in 4.0.0) were

/jcr:root//element(, rep:User)/wcm/notification/config/subscriptions/element()[@channel='inbox']

And

/jcr:root//element(*, rep:User)/wcm/notification/inbox

The queries in the last handful of comments here are:

/jcr:root/home//wcm/notification/config/subscriptions/*[@type='page']


History with back button issue

The browser back button does not seem to be handled correctly. It pushes a "/" at the end of the url instead of bringing me back to the earlier level.
for routes :
'/':'home',    '/RequestList': 'list',    '/Request/:id': 'request'
navigation goes :
http://localhost:9999/
use link with  data-bind="path: '/RequestList'"  navigates to :
http://localhost:9999/RequestList
back button navigates to:
http://localhost:56830/RequestList/
notice the "/" added at the end instead of returning to  http://localhost:9999/
the back button is more broken with more levels.

@vbeaulieu2 What browser is this in? I'm not able to repro in Chrome, Safari, or Firefox.
This is the code I'm using

Chrome and IE 11
Go to your docs page, nested routing, use foo-ception 3 times and play with back and forward.
You should see a similar problem in the url. At some point back and forward don't seem to work anymore.

I was able to reproduce a bit of unexpected behavior, but nothing like you've described. Could you check out the docs again and see if the problem you were having persists? If so, you could list the steps to repro?
Thanks

My first description comes from a project a bit more complex so I am not able to give you a simple version of the problem yet. I noticed later that the foo-ception exemple had a similar behavior and I think both are related.
I have recorded a quick video of the problem on your docs page and attached it here.
The result is that both history buttons and adress bar becomes invalid at some point.
Recording #8.zip
I will try send you some code later this week if you need another version of the problem.

The behavior you've recorded is due to the fact that the example is using recursive routing; I can't imagine this being a real-word scenario, but I've fixed it nonetheless for demo purposes.

Didn't fix the problem in my app.
I'll get back to you with a simple version of the problem as soon as i can.
Thanks

I came up with this example
Hope it helps. Thanks again.
Steps to reproduce : .
0. starting adress should be http://localhost.../main

use "request list" link. adress is now http://localhost.../main/request
use back button. final adress: http://localhost.../main/request/main/

components and routes :
ko.components.register('app', {
viewModel: function app() {
function app(name) {
this.routes = {
'/': '',
'/request': 'requestList'
}
};
return app
},
template: 'Request list'
});
ko.components.register('requestList', {
viewModel: function requestListViewModel() {
var self = this;
this.routes = {
'/': '',
'/:id': 'request',
'/edit/:id': 'editRequest',
};
},
template: ('' +
'  Request List' +
'  ' +
'  Go To Request with ID : 8' +
'  Go To Request with ID : 12' +
'  Router content' +
'  ' +
'  ' +
'')
});
ko.components.register('request', {
viewModel: function requestViewModel(ctx) {
var self = this;
this.id = ko.observable(ctx.params.id ? ctx.params.id() : null);
},
template: '' +
'Request Header' +
'' +
' ID:  ' +
' View' +
'' +
''
});
ko.components.register('editRequest', {
template: 'edit...'
});


Ability to use render.js in Service Worker

I'm writing a service worker for offline website editing and want to dynamically generate index pages for file directories. I like the file listings that serve provides - I just love the minimal, clean aesthetics! If I could refactor /lib/render.js so it could be used on its own would you be interested in having those modifications upstream? And if not, do you mind if I re-use the handlebars template and CSS in my own project?

So... same root goal, slightly different wording: Look ma, no handlebars!
const render = ({directory, paths, files, assetDir}) => (
`<!DOCTYPE html>

  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">

  <title>Files within ${directory}</title>

  <link rel="stylesheet" href="${assetDir}/styles.css">

      Index of
${
paths.map(
  ({url, name}) => `
        ${name}`
).join('')
}

${
files.map(
  ({relative, title, ext, base, size}) => `

        ${base}
        ${size}

`
).join('')
}

`)

You can also inline styles.css. If you did that, you'd be able to delete the views and assets directories, lib/view.js, and remove the dependency on handlebars. There are some obvious downsides so this is more of an experiment/proof of concept. But the advantage / nice thing is the render function is pure js with no dependencies, so it'll run in the browser, in a Web Worker, and in a Service Worker. My thinking is you could publish this as its own npm module called serve-render. That way other tools could use it as a standard "go-to" index page listing module.

We're not going to support this.
However, with the latest release, serve now accepts application/json for the Accept header value, which means you can dynamically load the contents of a directory and render them on the client.

serve now accepts application/json for the Accept header value, which means you can dynamically load the contents of a directory and render them on the client.

That's actually the exact opposite of what I was suggesting, which was to make the beautiful index pages work on the client side (or any JS environment). Doesn't really matter, I'll just use my fork.


Mention that array indexes start at 0

Most people would expect array indexes to start at 0 but it's even better to erase all doubt 😃

@googlebot I signed it!


Add support for screen events

Describe the feature
Currently dbt_segment handles Segment style page events, but not screen events.
We have both web and mobile native versions of our app and would like to use dbt_segment to consume both page and screen events, which would allow us to analyse mbile app user behaviour, and more importantly to compare user behaviour across platforms.
Describe alternatives you've considered

Munge ingested screen events in a way that they can be passed off as page views, but that seems quite ugly.
Rather than using SDK's in mobile native apps that send in screen events, use a HTML endpoints to send in raw page events, but seems even worse than 1.

Please let me know of any other approaches people can think of.
Additional context
I think this should be able to be independent of specific databases. We currently use Snowflake, but I don't expect that should matter.
Similar to DB specifics, I think this should be independent of whose SDK is being used to collect the screen events. We are using Rudderstack's SDK, which is fully compatible with Segment's API and collects the same data.
Who will this benefit?
This will benefit anyone collecting screen events using mobile app SDK's from Segment, Rudderstack, etc. It will be even more beneficial for people who have both web and mobile native apps, which will enable comparisons of user behaviour across platforms.
Are you interested in contributing this feature?
I'm interested in contributing to this feature and would need a hand getting started please.

Hey @grumBit! Happy to take a look at this with you if you're interested in contributing! Feel free to drop any questions here, or find me on dbt slack @Adam Jones (same profile pic).