limits.rb

FILE
ActiveAdmin.register Limit do
  permit_params :name, :slug, :amount, :units, :time_frame, :currency, :status

  config.sort_order = 'name_asc'

  menu parent: 'Configuration', label: 'Limits'

  # See permitted parameters documentation:
  # https://github.com/activeadmin/activeadmin/blob/master/docs/2-resource-customization.md#setting-up-strong-parameters
  #
  # Uncomment all parameters which should be permitted for assignment
  #
  # permit_params :name, :slug, :amount, :units, :time_frame, :currency, :status
  #
  # or
  #
  # permit_params do
  #   permitted = [:name, :slug, :amount, :units, :time_frame, :currency, :status]
  #   permitted << :other if params[:action] == 'create' && current_user.admin?
  #   permitted
  # end

  form do |f|
    f.inputs do
      f.input :name
      f.input :slug
      f.input :amount
      f.input :units
      f.input :time_frame
      f.input :currency
      f.input :status, as: :select, collection: ['active', 'inactive']
    end
    f.actions
  end
end

This ActiveAdmin configuration defines an interface for managing Limit records within your application. The configuration provides a form for creating and updating records, and organizes these records under the "Configuration" menu with the label "Limits." Here's a detailed breakdown of the setup:
1. Menu Configuration

menu parent: 'Configuration', label: 'Limits':
This adds the Limit resource to the "Configuration" menu in ActiveAdmin with the label "Limits."

2. Permitted Parameters

permit_params :name, :slug, :amount, :units, :time_frame, :currency, :status:
This line specifies the parameters that are allowed to be submitted through forms. It ensures that only the listed attributes can be mass-assigned, protecting against unwanted data changes.

3. Sorting Configuration

config.sort_order = 'name_asc':
This sets the default sort order for the index page of the Limit resource, sorting the records by the name field in ascending order.

4. Form Configuration

form do |f|:
This block defines the form that will be used to create or edit Limit records.

Form Fields:

f.input :name: Input for the limit's name.
f.input :slug: Input for the slug, typically a URL-friendly version of the name.
f.input :amount: Input for the limit amount.
f.input :units: Input for the units associated with the limit (e.g., transactions, dollars).
f.input :time_frame: Input for the time frame over which the limit applies (e.g., daily, monthly).
f.input :currency: Input for the currency associated with the limit.
f.input :status, as: :select, collection: ['active', 'inactive']: A dropdown for selecting the status of the limit, with options for "active" and "inactive."

Form Actions:
f.actions generates the submit and cancel buttons for the form.

Summary
This configuration creates a straightforward interface for managing Limit records in your application via ActiveAdmin. It organizes the resource under the "Configuration" menu, allows admins to create or update limits with relevant attributes, and provides a clean and user-friendly form with input fields and a status selector. The default sorting by name helps administrators quickly locate specific limits in the index view.


When you're at the beginning of the song, it lags and closes automaticly!

Describe your bug here.
Is this an issue or not?
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No :(

Download the source again and do it all over again, there is no other option

Can't fix it. :(


Initialize status and reason

In cases where you're calling the diff function but not referencing two different source trees, newly added lines can lead to situations where one line_status is None while the other one has a boolean value as expected. That ends up potentially never initializing status and reason.

Also, ideally, please add a test case that reproduces the issue.

@zoetetal this looks great, thank you so much! I have a minor comment but other than that, it's good to go!

OK thanks @aconrad just getting the final whitespace fix in. I forgot that as soon as we updated master on my fork the PR would update. Anyway if you remove the initialized status and reason and run tests you'll see the issue. Thanks for a nice library, we're using it during validation of pull requests.

Thanks @zoetetal, I merge-squashed. I will try to make a new release of pycobertura this week.

Released pycobertura v0.10.0, thanks again @zoetetal!


React imports do not use relative paths with es6-global

With "module": "es6-global" in my bsconfig.json, my imports look like this:
import * as React from "react";
import * as Js_exn from "../node_modules/rescript/lib/es6/js_exn.js";
import * as ReactDom from "react-dom";
import * as Belt_Option from "../node_modules/rescript/lib/es6/belt_Option.js";
import * as Caml_option from "../node_modules/rescript/lib/es6/caml_option.js";
import * as App$MyThing from "./App.mjs"

which causes this error message in my browser console:
Uncaught TypeError: Failed to resolve module specifier "react". Relative references must start with either "/", "./", or "../".

Hm... I'm actually not sure if this is the right repo for this issue. I just found this: https://github.com/rescript-lang/rescript-compiler/issues/2118

Yeah, this should be reported in the compiler. I will close this for now, feel free to reopen if you think it still belongs here.


Preferred theme settings should be scoped to relative set

I would expect that only dark themes appear in the list for workbench.preferredDarkColorTheme and vice versa for the other theme lists. Especially since we split out the list in the color theme picker:

What you see are the list of allowed themes, as defined by the configuration. By limiting it to only the light themes, functionality would be lost. Right now a user is free to choose a light theme when the OS scheme is dark.
The settings UI is generated out of the settings configuration which are done using JSON schema. Improving the UI is not easy.

I’d argue that if you want to have the same theme for dark and light then you don’t need to use this feature as that’s how it works by default.

One could use a light theme when the OS is dark, and a dark theme when the OS is light. Ok, I'm completely making this up, but I just wonder if we really gain anything from restricting the themes.

For me it was more of "Why isn't VS Code smart enough to know that I only want the dark themes listed for dark preferences" and felt like a bug. Also, that list is hard to read through because the order feels random and not alphabetical (looks like defaults are near the top). We should just polish this experience.

No plans to change the current behavior.


New version: sparrowwallet.sparrow version 2.0.0

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Resolve #174624

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

seems there is an issue when requesting update :
C:\Windows\System32>winget update sparrow
No applicable upgrade found.
A newer package version is available in a configured source, but it does not apply to your system or requirements.
if i remove the 1.9.1 package then reinstall, it works


fix handle create rowset error to avoid null pointer exception

Proposed changes
When I use merge on write table and load it, coredump happened when create rowset error in _generate_delete_bitmap
The purpose of this pr is to fix coredump when meet the error.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall


[DNM] drivers: ssp: update SSP driver to support Intel ACE30 PTL

This commit refactors the SSP driver to support the Intel ACE30 PTL platform. The changes include:

Adding new structures ssp_rx_dir and ssp_tx_dir to hold the TDM slot configuration for RX and TX directions
Adjusting the dai_ssp_set_config_blob functions to work with the new TDM slot configuration.

Necessary SOF changes:

[ ] https://github.com/thesofproject/sof/pull/9220

This [whitespace changes] is not only very distracting (does it hide any actual change?), it can also break git merge/cherry-pick/revert/etc.

As funny coincidence, guess what I'm doing right now? Fixing whitespace git conflicts when rebasing #74125 on top of 15c9d3711ced5f214 ...
To be fair it's not just whitespace conflicting in my case. But it's really not helping.


Fixup a test for -f processing

Thanks to @ahmetalpbalkan for noticing... we had an old check in this
testcase that no longer applied (due to stuff being removing recently).
However, while in there I added a check to make sure that the file referenced
by the query parameter isn't used at all.
Signed-off-by: Doug Davis<EMAIL_ADDRESS>

LGTM

LGTM


Yarn update to version 3

This PR updates to the latest version of yarn and fixes the current dependency vulnerabilities.
Before:

After:

Thanks a lot, this looks good to me!

@marvin-roesch Would you mind adding a hacktoberfest-accepted label to this PR? Or maybe even consider adding the Hacktoberfest topic to this repo? Hacktoberfest

@cmpickle Ah, of course! I thought this repo was already tagged.


capture arrow keys and modify users input during prompt.Run()

I want to add user input history (like in bash) to my console app.
Pressing UP-Key will get previously used command string and paste it to prompt.
That wold be graet if app could capture special keys, like arrows, TAB, ESC, ALT, CTRL etc
And there must be some way to modify current promp.
With that it would be possible to add autocompletion feature like pressing TAB in bash

Has there been any info on this? this could be a deal breaker for me, though I am not sure how I would implement this


Remove console config

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Fixed issues
-

See https://github.com/yiisoft/config/pull/12

Why removing console config?

Why removing console config?

Class View configured in common config.


Suggestion: --select-exact to auto accept --querys that are exact matches

Category

[x] fzf binary
[ ] fzf-tmux script
[ ] Key bindings
[ ] Completion
[ ] Vim
[ ] Neovim
[ ] Etc.

OS

[x] Linux
[x] Mac OS X
[x] Windows
[x] Windows Subsystem for Linux
[x] Etc.

Shell

[x] bash
[x] zsh
[x] fish

Analogously to --select-1, which returns immediately if the supplied --query matches only one result, I think it would be nice to have something like an --select-exact that returns immediately if the supplied --query exactly matches a result (however many others are partial matches).
For example, I have a fish function:
begin
    set --local IFS
    set list (get_list)
end
if test "$argv"; and test (echo "$list" | rg --count "^$argv\$") -eq 1
    set read "$argv"
else
    set read (echo "$list" | fzf --no-preview --no-multi --query="$argv")
end
somecmd "$read"

that would be reduced to:
somecmd (get_list | fzf --no-preview --no-multi --select-exact --query="$argv")

also for navigating nested menu systems it would be great if fzf automatically accepts when a menu item is full matching the query. Right now I workaround this by killing fzf via the preview process when {q} fully matches any of {+} - not exactly clean ;-)


Remix rootAuthLoader callback's typescript types don't allow returning null.

[X] Review the documentation: https://clerk.com/docs
[X] Search for existing issues: https://github.com/clerkinc/javascript/issues
[X] Go through package changelog files.
[ ] Provide the Frontend API key from your application dashboard.

Package + Version

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[X] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore
[ ] other:

Dependencies + versions
Provide a json with the dependencies used in your project (copy paste from yarn.lock / package-lock.json) or a github project / template that reproduces the issue.
Include the @clerk/ packages and their versions!*
Example:
{
  "dependencies": {
    "react": "18.2.0",
    "@remix-run/cloudflare": "1.19.3",
    "@remix-run/cloudflare-pages": "1.19.3",
    "@remix-run/css-bundle": "1.19.3",
    "@remix-run/react": "1.19.3",
    "@clerk/remix": "2.9.1",
    "@clerk/clerk-react": "4.13.0"
  }
}

Description
This one is fairly simple. In Remix, you're allowed to return "null" from a loader when it should return nothing. That's useful when you have conditional redirects, for example.
Eyeballing the code of @clerk/remix, it seems to be handling that correctly. The types however, are declared separately to handle the overloads, and it loosely ends up with "Return a response or some data. If returning data, it has to extend {}", which does not allow null.
So something like this will file the type check:
export async function loader(args: LoaderArgs) {
  return rootAuthLoader(args, ({ request }) => {
    const url = new URL(request.url);
    if (url.pathname === "/") {
      return redirect("/mypage");
    }

    return null;
  });
}

As a workaround, you can replace return null; with return {};, so it isn't a big deal, but it would be nice for consistency to have the types 1:1 with the Remix types, which do allow returning null.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Bugfixed:Modify commment of h2quic.client

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1860   +/-   ##
=======================================
  Coverage   86.93%   86.93%
=======================================
  Files          96       96
  Lines        6567     6567
=======================================
  Hits         5709     5709
  Misses        614      614
  Partials      244      244

Impacted Files
Coverage Δ

h2quic/client.go
87.58% <ø> (ø)
:arrow_up:

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 a63ee3d...e8ae892. Read the comment docs.

I don’t think this is a bug, neither does it need fixing. Furthermore, this package is going to be replaced by HTTP/3 very soon.


[ISSUE #945]Optimize request_callback_producer code style

Which Issue(s) This PR Fixes(Closes)

Fixes #945
Brief Description

How Did You Test This Change?

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥


glib failure in gstreamer_pipeline.py

After running 9 minutes,
PipelineStatus(avg_fps=43.18830125933299, avg_pipeline_latency=3.0989729501227146, elapsed_time=427.7101671695709, id=1, start_time=1590402984.9836986, state=<State.RUNNING: 2>)
Fatal Python error: deallocating None
Thread 0x00007ff174b7a700 (most recent call first):
Current thread 0x00007ff15ffff700 (most recent call first):
Thread 0x00007ff176b7e700 (most recent call first):
File "/usr/lib/python3/dist-packages/gi/overrides/GLib.py", line 585 in run
File "/home/vaserving/gstreamer_pipeline.py", line 45 in gobject_mainloop
File "/usr/lib/python3.6/threading.py", line 864 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap
Thread 0x00007ff19e40b700 (most recent call first):
File "/usr/lib/python3/dist-packages/watchdog/utils/delayed_queue.py", line 65 in get
File "/usr/lib/python3/dist-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
File "/usr/lib/python3/dist-packages/watchdog/observers/inotify.py", line 129 in queue_events
File "/usr/lib/python3/dist-packages/watchdog/observers/api.py", line 146 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap
Thread 0x00007ff19ec0c700 (most recent call first):
File "/usr/lib/python3/dist-packages/watchdog/observers/inotify_c.py", line 296 in read_events
File "/usr/lib/python3/dist-packages/watchdog/observers/inotify_buffer.py", line 59 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap
Thread 0x00007ff19f40d700 (most recent call first):
File "/usr/lib/python3.6/threading.py", line 299 in wait
File "/usr/lib/python3.6/threading.py", line 551 in wait
File "/home/runva.py", line 123 in loop
File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56 in run
File "/usr/lib/python3.6/concurrent/futures/thread.py", line 69 in _worker
File "/usr/lib/python3.6/threading.py", line 864 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap
Thread 0x00007ff19fc0e700 (most recent call first):
File "/usr/lib/python3.6/threading.py", line 299 in wait
File "/usr/lib/python3.6/queue.py", line 173 in get
File "/usr/lib/python3/dist-packages/watchdog/observers/api.py", line 360 in dispatch_events
File "/usr/lib/python3/dist-packages/watchdog/observers/api.py", line 199 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap
Thread 0x00007ff1a040f700 (most recent call first):
File "/usr/lib/python3.6/threading.py", line 1072 in _wait_for_tstate_lock
File "/usr/lib/python3.6/threading.py", line 1056 in join
File "/home/rec2db.py", line 54 in loop
File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56 in run
File "/usr/lib/python3.6/concurrent/futures/thread.py", line 69 in _worker
File "/usr/lib/python3.6/threading.py", line 864 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap
Thread 0x00007ff1a4da4b80 (most recent call first):
File "/usr/lib/python3.6/threading.py", line 1072 in _wait_for_tstate_lock
File "/usr/lib/python3.6/threading.py", line 1056 in join
File "/usr/lib/python3.6/concurrent/futures/thread.py", line 152 in shutdown
File "/usr/lib/python3.6/concurrent/futures/_base.py", line 611 in exit
File "/home/count-entrance.py", line 32 in connect
File "/home/count-entrance.py", line 77 in

This was a bug in one of the gstreamer elements being used. A hotfix was released for that element and this issue was resolved.

@xwu2git With the release of the hotfix for DL Streamer - can we close this issue?

Yes

This issue with gvapython element was resolved in DL Streamer v1.0.1
PR#71


Investigate bundle size

Is it tiktoken, or something else?

Hello!
Looking at the bundle size and metafile when bundled through esbuild + wrangler, the main reason the bundle size is large is due to the big WASM file included by @dqbd/tiktoken.
The WASM file contains the rankings for all models (~3 MB uncompressed) + the tokenizer logic itself (~700 kB uncompressed).
Even if ranks only for gpt-3.5/gpt-4 are bundled (skipping older gpt-2 ranks etc.), the cl100k_base (1.1 MB uncompressed) + tokenizer fits just right into the 1 MB limit when compressed, not leaving enough space for rest of langchain.
I think the best way forward is to either:

Split the @dqbd/tiktoken package into a separate endpoint for the edge. That way, we're not bundling anything. However, as this would be an additional network call, this would be at the expense of slower tokenization. Some preliminary work has been done in that regard, we could release an isomorphic package, which would call an API if imported in edge runtimes.
Avoid tokenization altogether when just consuming OpenAI and other LLMs. This would be harder to do as far as I can see and would most likely be a breaking change.

Adding the analyzed meta.json bundle when just importing OpenAi LLM.

Note: this is not only related to CF Workers but for all other edge runtimes as well.

Thanks a lot for this investigation @dqbd
Approach 1 sounds interesting to me, anything I can do to help here?
Approach 2 is harder as the tokeniser is eg used deep inside some chains, so not terribly clear how to make it more optional.
That said, we could conceivably move the countTokens methods outside of the LLM classes so that they need to be imported separately, I'd be okay with that, I don't think many people are using them directly.
What's harder is

The chains that use it, those would need to be moved to separate endpoints from other chains
The maxTokens=-1 behaviour on OpenAI LLM which uses the tokeniser to calculate max tokens, that'd be harder to remove

but I would however be perfectly okay with making it require a remote download when used as you suggested
thoughts?

Thanks @dqbd I'm seeing something similar when running cloudflare worker cli:
wrangler publish --dry-run --outdir dist

I like your first idea as well. To accomplish this, are you referring to the suggestion by cloudflare here?
I see Denoflare has a way to import a wasm file via url:
import { importWasm } from 'https://raw.githubusercontent.com/skymethod/denoflare/v0.5.11/common/import_wasm.ts';
const module = await importWasm(import.meta.url, './hello.wasm');

But I don't see a way in Cloudflare to accomplish the same. How would you suggest making that happen?


[Request] Port for Terasology

Hi,
I was wondering if and when we can expect a port of this for Terasology.
I am not really into minecraft.

We'll see


Redesign of facet browser

A proposal for the redesign of the facet sections:

4DN-facets.pdf

Meant to add that the icons are from the Gizmo symbol set: https://symbolset.com/icons/gizmo

@ngehlenborg on Monday we should discuss how sub-facets might fit into this. Specifically, those are facets that will only appear/expand once the corresponding parent facet has been selected. For example, selecting "immortalized cell line" should produce a sub-facet listing the specific cell lines.

Facets are redesigned, excepting any changes that Burak will want to make when I show him tomorrow,


Improve validation error messages

[x] #5054
[ ] Use widget validation structure for actions

Duplicate of #2675


Table with plot exclamation point hangs around

If you put a row in an error state and then get rid of the error, the red exclamation point still hangs around.

there should be a property to remove the exclamation point all together from the error handling of the datagrid in the xaml. not sure what the property is, but that will fix it. the exclamation point is not necessary at all, the red cells do the work we want.

<DataGrid.RowValidationErrorTemplate></DataGrid.RowValidationErrorTemplate>
https://stackoverflow.com/questions/8394829/hide-wpf-datagrid-row-error


Task/data field exposure

Codecov Report

Merging #5 (fcd3b5e) into master (1a4ab36) will decrease coverage by 94.33%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master      #5       +/-   ##
==========================================
- Coverage   96.69%   2.35%   -94.34%
==========================================
  Files           5       5
  Lines         212     212
==========================================
- Hits          205       5      -200
- Misses          7     207      +200

Impacted Files
Coverage Δ

lib/src/build_transaction.dart
0.00% <0.00%> (-100.00%)
:arrow_down:

lib/src/utils.dart
100.00% <100.00%> (ø)

lib/src/mnemonic.dart
0.00% <0.00%> (-100.00%)
:arrow_down:

lib/src/exceptions.dart
0.00% <0.00%> (-100.00%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[BUG] cluster conditions sais "WaitApplied(2) [Bundle fleet-agent-local] "

It's Aarch64. user Iaas on Oracle cloud infrastructure
Rancher Server Setup

Rancher version:
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): k3s

Proxy/Cert Details: self signed cert.

Information about the Cluster

Kubernetes version: v1.26.6 +k3s1
Cluster Type (Local/Downstream): Local

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom): Admin

If custom, define the set of permissions:

Describe the bug

Fleet agent pod Failed to register agent.
To Reproduce

on aarch64 machine
install k3s, install rancher with helm.
create gitea pod, connect gitea to rancher continuous delivery.

install k3s curl -sfL https://get.k3s.io/ | K3S_KUBECONFIG_MODE="660" INSTALL_K3S_VERSION=v1.26.6+k3s1 K3S_TOKEN=rancher.oci.cola16 sh -s - server --cluster-init
install cert-manager

helm install cert-manager jetstack/cert-manager \
  --namespace cert-manager \
  --create-namespace \
  --set installCRDs=true

install rancher

helm install rancher rancher-latest/rancher \
  --namespace cattle-system \
  --set hostname=<domain> \
  --set bootstrapPassword=admin

create gitea pod, connect gitea to rancher continuous delivery.

Result
fleet-agent-local bundle, gitea-svc bundle stuck in wait applied
Expected Result

The pod described in gitea is created.
Screenshots

Additional context

I found a secret called fleet-agent-bootstrap.
The apiServerURL was a public URL.
The public URL is that only access by logging in with SSO.
So I changed it to a private URL  that pointing LoadBalancer.
But I got an unauthorized error and couldn't proceed.
I tried applying rancher.cattle-system.svc.cluster.local, but I got an X509 error.
What should be the value of CAcert, what should be the value of apiServer,
How can I verify that this is normal?
Translated with www.DeepL.com/Translator (free version)

Resolved.
Knowing that it is managed by HELM, I uninstalled the fleet and installed it with a private DNS, then installed the
secret was also changed to private dns again.


There is no extension able

If you received a notification "There is no extension able to load the configuration for" when resetting the cache, check the bundle.php file: it may well be that for some reason the bundle did not register there.
In this case, you need to either deal with the cause of this case or manually register the bundle.
If you chose the second option, just add this line to the end of the bundle.php file:
Reiterus\McxInfoBundle\McxInfoBundle::class => ['all' => true]

this is a hint...


Add preorder_idx to the JSON schema

Coverage remained the same at 83.869% when pulling b3d3343ffe866a129a831411ce933a685b2b3723 on vrajmohan:update-json-schema into fe86f863ba1fb8490d8b736c25f66fd65635768d on eregs:master.

Looks good


Use round avatar for E.Cash room avatar

@TomatoToaster please review
Details
Just changes the Avatar from being square to round
Fixed Issues
$ https://github.com/Expensify/Expensify/issues/170939
Tests/QA

Join / View a default chat room from the side bar, make sure the chair icon is round.

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging         in version: 1.0.79-5🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

This passed qa so I'm checking this off

🚀 Deployed to production         in version: 1.0.80-2🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Add q2-feature-classifier as an option

This seems to work pretty well with PacBio and Loop full length 16S runs and the full-length trained data.  On our local cluster using the QIIME2 output from the pipeline:
module load QIIME2/2020.6
qiime feature-classifier classify-sklearn --i-classifier QIIME2/silva-138-99-nb-classifier.qza --i-reads sequences.qza --o-classification tax_final.qiime2.qza --p-n-jobs $SLURM_NPROCS
qiime tools export --input-path tax_final.qiime2.qza --output-path tax_final.qiime2

Note that a dada2 Silva database is also now available for this step, which works well with internal data (both Loop and PacBio).


use the original domain concept type for assertion answers values

Ha, didn't know I could approve a PR with a non-team account... oops!


isNaN accept only number argument

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/isNaN
it accept strings too, lol.

If you want implicit conversions, why are you using TypeScript? Anyway, this isn't controlled by this package, so if you have to you might file an issue on TypeScript repo https://github.com/Microsoft/typescript/issues


feat(options): added --prefix option

Hi! I'm a new nps user and I love it! I added this feature for myself but maybe it'd be useful to others.
What:
This adds a prefix option to prepend a string to the start of each script name in the cli

Why:
I wanted to be able to do something like this:
cli
npm test unit functional

package-scripts.js
module.exports = {
  scripts: {
    test: {
      unit: 'mocha ./tests',
      functional: 'intern'
    }
  }
}

package.json
{
  "scripts": {
    "test": "nps --prefix=test"
  }
}

Checklist:

[x] Documentation
[x] Tests
[x] Ready to be merged
[x] Added myself to contributors table

I don't think the default case is working here. I'll push an update soon

@dannycoates is this ready for review now? Sorry, I didn't see you updated it after the last comment!

@sezna yes, it's ready, thanks!

Looks good to me, sorry about the delay!


Fix pretty function magic constant overwriting

This would change the current behavior when printing for gcc/clang.
From:
test_io.cpp->TestBody:639
To:
test_io.cpp->virtual void CustomLogLevels_AddANonFatal_Test::TestBody():639
I replaced __FUNCTION__ with __func__ as the fallback because it seems like that is more standard because it is part of the c99/c++11 standards.
However, maybe __FUNCTION__ should be kept for backwards compatibility sake.
I changed the name of the macro, so it doesn't collide with the compiler versions.

Revisiting this and might have to revert some of these changes.


Improvement

Hey Thomas, I'm sending some updates:
Changed some properties of the grid layout for use FR Unit;
Added responsible layout with mobile first

Hey @simoneas02, thanks for the pull request. Better mobile support would be great. I'll take a look!


Thread 8: Fatal error: attempt to await next() on more than one task

Thread 8: Fatal error: attempt to await next() on more than one task
xcode 14.3

That's old code I don't use now. You better call yt_dlp().

As you can see it's just an alias, there should be no change in behavior.

I guess you can comment out init() entirely.

Thread 8: Fatal error: Could not access PythonObject member 'Popen'

@kewlbear Thread 8: Fatal error: Could not access PythonObject member 'Popen'


[stable/suitecrm] Update prerequisites

Is this a new chart
No
What this PR does / why we need it:
Update prerequisites to match the ones that we test our charts with
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

@javsalgar can you close this PR in favor of https://github.com/helm/charts/pull/18029?

It's not a duplicate... The title confused me. It should be "Testlink"

/retest

/check-dco


Run the BalaurProcessor from a resource model

The tests can't pass because of the locally published dependency.  This is being merged into a side branch and not main/master, so I will go ahead.

Thank you!
On Fri, Jul 7, 2023 at 21:36 Keith Alcock @.***> wrote:

Merged #730 https://github.com/clulab/processors/pull/730 into balaur.
—
Reply to this email directly, view it on GitHub
https://github.com/clulab/processors/pull/730#event-9757969634, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI75TS4HEFE4P7POZD7M3TXPBJMNANCNFSM6AAAAAA2CELNB4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Add support for TLS/SSL enabled clusters

Here is a patch to support SSL enabled Hadoop services.
Tested in our environment with Yarn and HDFS 2.7.1, works fine :-)
You will need to add jvm_args="-Djavax.net.ssl.trustStore=path_to_truststore" in elephant.conf
There is still one error with the swebhdfs client in the SparkFSFetcher.scala class complaining about a SSL certificate problem.
Seems to be related to a dependency brought by sbt. I have not that error in a simple unit test project built with Maven.
Any review will be welcome.

Thanks for the PR @damienclaveau. I didn't get a chance to review it completely today but I have added a few comments. Will finish my review by tomorrow.
Adding @shankar37 @nntnag17 to review.

Thanks for the review.
I would like to rely more on the Hadoop codebase (org.apache.hadoop.http.HttpConfig, org.apache.hadoop.yarn.conf.YarnConfiguration.getSocketAddr, org.apache.hadoop.yarn.webapp.util.WebAppUtils.getRMWebAppURLWithScheme),
... but there has been a lot of refactoring in theses methods between Hadoop 2.3 and Hadoop 2.7
Such dependencies will probably break backward compatibility.
Please, what is the minimal hadoop version that dr-elephant must support ?

@damienclaveau , as far as I know, Dr. Elephant currently supports all the hadoop 2.x versions.

Hi @damienclaveau @akshayrai, I'd like to get this committed, but it's not immediately clear to me if there's anything left to do. Are there any remaining action items or is this patch ready for a final review? Thanks.

@damienclaveau, can you update the PR fixing all the conflicts? Do you have anything left to add to this PR?

Is there anything happening with this PR @damienclaveau  ? We would really like to see it included.

Hi everyone, with the major refactoring done to the SparkFSFetcher, this PR won't easily rebase.
I will have a look at this it in the next few days, and test everything against our clusters.

@damienclaveau , did you get a chance to rebase and test this?

@damienclaveau  - would be great to have SSL/TLS support.

Would this work when HTTPS authentication is enabled?

esourceManager Web Application HTTPS Port (TLS/SSL) - set with port 8090, so http - 8088 doesnt open cos of SSL settings.
is it possible for Dr elephant to read using https - 8090 port.
please help on this.


audio works, but video needs rejoining to work

Hello,
Many times when a Mobile user joins, they are able to hear the audio - but we are not able to see each other's videos.
Refreshing / Rejoining the meeting fixes this.
My preferred encoding in config.js H264 ( as using VP8 heats up the device a lot )
Since, Refresh / Rejoin solves the issue, but it is not user friendly - so can we make the code do this automatically?
Where do I need to make the code change?
I have done several customizations to the code, such as mute lock room etc - so will be able to do the above fix with some guidance.
Here is my encoder config:
`		// Router media codecs.
mediaCodecs :
[
{
kind      : 'audio',
mimeType  : 'audio/opus',
clockRate : 48000,
channels  : 2
},
{
kind       : 'video',
mimeType   : 'video/h264',
clockRate  : 90000,
parameters :
{
'packetization-mode'      : 1,
'profile-level-id'        : '42E01e',
'level-asymmetry-allowed' : 1,
'x-google-start-bitrate'  : 1000
}
},
			{
				kind       : 'video',
				mimeType   : 'video/h264',
				clockRate  : 90000,
				parameters :
				{
					'packetization-mode'      : 1,
					'profile-level-id'        : '42e01f',
					'level-asymmetry-allowed' : 1,
					'x-google-start-bitrate'  : 1000
				}
			},

			{
				kind       : 'video',
				mimeType   : 'video/VP8',
				clockRate  : 90000,
				parameters :
				{
					'profile-id'             : 2,
					'x-google-start-bitrate' : 1000
				}
			},

			{
				kind       : 'video',
				mimeType   : 'video/h264',
				clockRate  : 90000,
				parameters :
				{
					'packetization-mode'      : 1,
					'profile-level-id'        : '42801e',
					'level-asymmetry-allowed' : 1,
					'x-google-start-bitrate'  : 1000
				}
			},

			{
				kind       : 'video',
				mimeType   : 'video/h264',
				clockRate  : 90000,
				parameters :
				{
					'packetization-mode'      : 1,
					'profile-level-id'        : '4d0032',
					'level-asymmetry-allowed' : 1,
					'x-google-start-bitrate'  : 1000
				}
			},

			{
				kind       : 'video',
				mimeType   : 'video/VP9',
				clockRate  : 90000,
				parameters :
				{
					'x-google-start-bitrate' : 1000
				}
			}

		]
`

My preferred encoding in config.js H264 ( as using VP8 heats up the device a lot )
Since, Refresh / Rejoin solves the issue, but it is not user friendly - so can we make the code do this automatically?
Where do I need to make the code change?

I was wondering about the same thing recently, simply reordering the order of videocodecs in config.js did the trick for me if you want to be using H264.

Yes, I have already re-ordered, as you can see in my original post. However, in some mobile devices, people have to refresh/rejoin to otherwise their videos are not visible to each-other in first attempt.
I am looking for a solution to this.

My preferred encoding in config.js H264 ( as using VP8 heats up the device a lot )
Since, Refresh / Rejoin solves the issue, but it is not user friendly - so can we make the code do this automatically?
Where do I need to make the code change?

I was wondering about the same thing recently, simply reordering the order of videocodecs in config.js did the trick for me if you want to be using H264.

I can confirm I've hit this today too as a regular desktop user with Firefox 83 on Fedora 32.  The other party could not see my video until I rejoined.  @varundabke are you seeing this only on mobile devices?  Thanks.

Was other party on Mobile?
Most of our users are on Mobile, so I am not sure if it occurs on desktop
as well - but dont remember noticing it on desktop.
Any expert comments from Edumeet team?
On Wed, Dec 9, 2020 at 10:54 PM Jiri Mencak<EMAIL_ADDRESS>wrote:

I can confirm I've hit this today too as a regular desktop user with
Firefox 83 on Fedora 32. The other party could not see my video until I
rejoined. @varundabke https://github.com/varundabke are you seeing this
only on mobile devices? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/edumeet/edumeet/issues/633#issuecomment-741921376,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB74QHAWHJJY672SLHOEZ4DST6XGPANCNFSM4T7AAU4Q
.

Was other party on Mobile?

No, both were desktop Linux users.

I wonder if this could be bandwidth related.  I've realized I was on a much slower ISP provider today and I haven't seen these issues in the past when using my regular/faster ISP.  I'll try to spend some time using traffic shaping to artificially limit my bandwidth and try and reproduce this.

Linking an issue that could be related: https://github.com/edumeet/edumeet/issues/656

for VP8, reducing frame rate has reduced battery consumption. After all the research, i have decided to go ahead with reduced frame rate + vp8

for VP8, reducing frame rate has reduced battery consumption. After all the research, i have decided to go ahead with reduced frame rate + vp8


Reverse first sort direction when a user sorts on a column in the monitor

In practice, we almost always want to see the greatest when sorting columns (ingest, entries, running scans, etc). Right now, this requires 2 sorts since the default sort is ascending.

@alerman Default to descending makes sense to me for most columns, except for the name field. I'm not sure how easy it would be to make the default sort order different for different columns.
The monitor has undergone a lot of work in the current development branch. Sorting is now much cheaper, and client-side. Have you had a chance to see if this issue affects the latest version in our 2.0 development branch / master?


Update chrome devtools user test baseline

Fixes user suite.
Maybe we should pin the version, since it contains so many errors, until we fix most of those errors. Thoughts?

Unless we reconcile null handling with Closure, we’ll always have hundreds of type errors. And I’m working on the typescript spec this month, so the baselines aren’t going to get better soon. The pinning question probably won’t change much in the future. Is the unpinned test too burdensome now?


Feature suggestion: TailwindCSS support

Will there ever be support for tailwind palette icon colouring for this package?

You can use tailwind's 'fill' to change the colour of the icons as they are just SVGs.
Usage:
<div class="fill-red-500">
    <Icon src={ICON} />
</div>


changed max gas fee to gwei instrad of percentage

Max Gas Fee UI Updates
Changes 👷♀

Updated the UI for max gas fee to now be represented by a gwei rather than a %

when it comes to UI change its enough, logic part including initialization and handling is in the scope of other story if I recall correctly.
useBasicSellStateInitializator we should just change file name (I guess we can do it at the very end to avoid conflicts), this file contains initialization both for basic buy and basic sell using given type so there is no need for duplication


WITHOUT ROWID Optimization

I didn't expect it would work, but leaving here in case some would try it. It happens randomly after a few dozens of items are added.
Uncaught (in promise) DOMException: Failed to execute 'advance' on 'IDBCursor': The transaction has finished.
    at f.read (blob:http://localhost:3000/59fedd9f-74f2-4db5-b08a-a4d22abebf7e:1:5038)
    at blob:http://localhost:3000/59fedd9f-74f2-4db5-b08a-a4d22abebf7e:1:7600
    at w (blob:http://localhost:3000/59fedd9f-74f2-4db5-b08a-a4d22abebf7e:1:6652)
    at blob:http://localhost:3000/59fedd9f-74f2-4db5-b08a-a4d22abebf7e:1:7560
    at g (blob:http://localhost:3000/59fedd9f-74f2-4db5-b08a-a4d22abebf7e:1:7671)
    at g (blob:http://localhost:3000/59fedd9f-74f2-4db5-b08a-a4d22abebf7e:1:9082)

It happened with me as well and I have no clue when and why does it happen.

@oceanwap Check https://github.com/evoluhq/evolu

@steida why did you close an issue? 🤔


When multiple Workflows use the same realtime metric, deleting one Workflow causes the metric to be deleted altogether

Pre-requisites

[X] I have double-checked my configuration
[X] I can confirm the issues exists when I tested with :latest
[X] I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?
What happened:
Workflow has a realtime metric. If 2 Workflows (such as 2 Workflows evoked from the same CronWorkflow) use that metric, then once one is deleted the metric is removed from memory altogether.
That is because of this line.
What I expected:
delete(m.customMetrics, metric) would only be called if the metric weren't present in any existing Workflows
The net effect in the CronWorkflow example below is that the metric is deleted right around the same time that the new metric is created:

t     | WF 1 started |
t+~10 | WF 1 completed |
t+60  | WF 2 started |
t+~70 | WF 2 completed | <- this adds to m.customMetrics
t+~70 | WF 1 deleted | <- this deletes from m.customMetrics

Version
latest
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
: argoproj.io/v1alpha1
kind: CronWorkflow
metadata:
  annotations:
    description: This cron workflow creates canaries which we monitor
  labels:
    canary: "true"
  name: canary
  namespace: argo
spec:
  schedule: '* * * * *'
  workflowMetadata:
    labels:
      monitoring: "true"
  workflowSpec:
    activeDeadlineSeconds: 30
    entrypoint: whalesay
    metrics:
      prometheus:
      - gauge:
          realtime: true
          value: '{{workflow.duration}}'
        help: Duration of canary
        name: canary_duration
    podDisruptionBudget:
      minAvailable: 1
    podGC:
      strategy: OnPodCompletion
    serviceAccountName: argo
    templates:
    - container:
        args:
        - ok
        command:
        - echo
        image: docker.intuit.com/dev/containers/argo/service/argoexec:v2.6.3
        name: main
      name: whalesay
    ttlStrategy:
      secondsAfterCompletion: 90
      secondsAfterFailure: 90
      secondsAfterSuccess: 90

Logs from the workflow controller
N/A

Logs from in your workflow's wait container
N/A

Actually, this may not be a bug. Digging deeper, I think this may be what was intended: that a metric would only be for a single Workflow at a given time. I see in the documentation here it explicitly says "Now, whenever we run our first workflow that validates 'Model A' a metric with the amount of time it took it to do so will be created and emitted. For each subsequent time that this happens, no new metrics will be emitted and the same metric will be updated with the new value." So, maybe one Workflow should ever use a metric at a given time, and therefore the metric should be deleted when that one Workflow dies?
I found if I add a label for {{workflow.name}} to the metric than each labeled metric is unique, and at least one of them is always present in the system.
 - gauge:
          realtime: true
          value: '{{workflow.duration}}'
        help: Duration of canary
        name: canary_duration
        labels:
          - key: workflow
            value: "{{workflow.name}}"


RuntimeError: Given input size: (256x9x27). Calculated output size: (256x0x2). Output size is too small

Hi, I am using detectron2 v0.6, train on coco2017, but it occur a RuntimeError: Given input size: (256x9x27). Calculated output size: (256x0x2). Output size is too small.
[10/25 22:08:38 d2.utils.events]:  eta: 3 days, 11:34:06  iter: 7329  total_loss: 3.163  loss_ce: 1.256  loss_objectness: 0.5939  loss_dice: 1.001  loss_mask: 0.3219  time: 1.1804  data_time: 0.0963  lr: 5e-05  max_mem: 8099M
Traceback (most recent call last):
File "train_net.py", line 196, in
launch(
File "c:\users\f\detectron2\detectron2\engine\launch.py", line 82, in launch
main_func(*args)
File "train_net.py", line 190, in main
return trainer.train()
File "c:\users\f\detectron2\detectron2\engine\defaults.py", line 484, in train
super().train(self.start_iter, self.max_iter)
File "c:\users\f\detectron2\detectron2\engine\train_loop.py", line 150, in train
self.after_step()
File "c:\users\f\detectron2\detectron2\engine\train_loop.py", line 180, in after_step
h.after_step()
File "c:\users\f\detectron2\detectron2\engine\hooks.py", line 555, in after_step
self._do_eval()
File "c:\users\f\detectron2\detectron2\engine\hooks.py", line 528, in _do_eval
results = self._func()
File "c:\users\f\detectron2\detectron2\engine\defaults.py", line 453, in test_and_save_results
self._last_eval_results = self.test(self.cfg, self.model)
File "c:\users\f\detectron2\detectron2\engine\defaults.py", line 617, in test
results_i = inference_on_dataset(model, data_loader, evaluator)
File "c:\users\f\detectron2\detectron2\evaluation\evaluator.py", line 158, in inference_on_dataset
outputs = model(inputs)
File "D:\ana\envs\detectron2\lib\site-packages\torch\nn\modules\module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "D:\YaoJiawei\python_workspace\SparseInst_TensorRT\sparseinst\sparseinst.py", line 101, in forward
features = self.encoder(features)
File "D:\ana\envs\detectron2\lib\site-packages\torch\nn\modules\module.py", line 1130, in call_impl
return forward_call(*input, **kwargs)
File "D:\YaoJiawei\python_workspace\SparseInst_TensorRT\sparseinst\encoder.py", line 82, in forward
prev_features = self.ppm(self.fpn_laterals0)
File "D:\ana\envs\detectron2\lib\site-packages\torch\nn\modules\module.py", line 1130, in call_impl
return forward_call(*input, **kwargs)
File "D:\YaoJiawei\python_workspace\SparseInst_TensorRT\sparseinst\encoder.py", line 38, in forward
priors = [F.interpolate(input=F.relu(stage(feats)), size=(
File "D:\YaoJiawei\python_workspace\SparseInst_TensorRT\sparseinst\encoder.py", line 38, in
priors = [F.interpolate(input=F.relu(stage(feats)), size=(
File "D:\ana\envs\detectron2\lib\site-packages\torch\nn\modules\module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "D:\ana\envs\detectron2\lib\site-packages\torch\nn\modules\container.py", line 139, in forward
input = module(input)
File "D:\ana\envs\detectron2\lib\site-packages\torch\nn\modules\module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "D:\ana\envs\detectron2\lib\site-packages\torch\nn\modules\pooling.py", line 622, in forward
return F.avg_pool2d(input, self.kernel_size, self.stride,
RuntimeError: Given input size: (256x9x27). Calculated output size: (256x0x2). Output size is too small

Hi, thanks for your interest in SparseInst 😄.
The input size is too small, which causes this error. Could you tell me what input size is used in your setting?

Hi, thanks for your interest in SparseInst 😄. The input size is too small, which causes this error. Could you tell me what input size is used in your setting?

Do you mean this in Base-SparseInst.yaml, I did not change this. Should I delete 416, even 448?
INPUT:
MIN_SIZE_TRAIN: (416, 448, 480, 512, 544, 576, 608, 640)
MAX_SIZE_TRAIN: 853
MIN_SIZE_TEST: 640
MAX_SIZE_TEST: 853
FORMAT: "RGB"
MASK_FORMAT: "bitmask"

This problem is weird and have you re-run the training?

This problem is weird and have you re-run the training?

It occured twice on COCO2017 yesterday, while never happen on selfdata(about 800*1500), maybe some picture too small in COCO.

I've never met the error when training COCO and I'd like to check this problem. Maybe I need to know what you've modified already.

The first thing I did aftering download this repo was try to train on COCO2017. So, at the beginning, I did not change anything, just unzip COCO2017 annotations, train2017 and val2017, put them into datasets. Run this command:
python train_net.py --config-file configs/sparse_inst_r50vd_dcn_giam_aug.yaml --num-gpus 1
"RuntimeError: Given input size: (256x9x27). Calculated output size: (256x0x2). Output size is too small" occured after 3 minutes for the first time, and occured after about 2 hours for the second time. I google the RuntimeError, and I guess some pictures may been resized into a small size, but I did not catch. Maybe I should try again when the GPU(RTX3060) is free.

Ok, I see. I'll check it soon whether the augmentation in v0.6 causes this error.


Blaze 0.14.0 Release

We need to integrate the newest blaze in order to release 0.20.0

v0.20.0-M6 seems to be using Blaze 0.14.0-M12.
Changelog entry for M5 incorrectly says blaze was upgraded to 0.14.0-M2.

Released


add blog for feature ServiceNodePortStaticSubrange

add blog for KEP 3668 https://github.com/kubernetes/enhancements/issues/3668
this blog describes the behavior of the new Feature ServiceNodePortStaticSubrange, and the problems it solves, and shows some examples

@tengqm  thank you so much, It's all fixed.

@xuzhenglun There are still quite a few nits you didn't respond to.

/lgtm

Hello, Comms Lead for v1.27 here. The publication order and date for the Feature Blog series has been finalized and the tracking board is updated.
The publication date for this article is 11-05-2023 (May 11).
Thank you!

/hold cancel
Cancelling hold because the date and filename is correct.
/approve
Approved from docs side.

@tengqm please allow me to ask few more question.
Is there anything else I need to do next? Does the lgtm label need to wait until it is released in May?

No. I omitted lgtm because I believe this is a work large enough to warrant another pair of eyes, preferably from someone who can give it a tech review, although this one doesn't seem a strong need for tech review.

@xuzhenglun You have to rename the file according to the release date assigned.

/hold
again for filename change.
Feel free to lift the hold when it is corrected.

@tengqm

No. I omitted lgtm because I believe this is a work large enough to warrant another pair of eyes, preferably from someone who can give it a tech review, although this one doesn't seem a strong need for tech review.

Really thanks for your explanation patiently.

You have to rename the file according to the release date assigned.

The file name has been corrected.

/hold cancel

/lgtm

ups, I noticed there is a typo https://github.com/kubernetes/website/pull/40204/files#r1163933056 , @xuzhenglun can you please follow up on that?

ops, thank you for your careful review.  The PR has been submitted in https://github.com/kubernetes/website/pull/40635.


feat: add strong typing for ModalController dismiss values

Feature Request
Ionic version:
[x] 4.x
Describe the Feature Request
Currently the dismissal data of a shown modal is not typed. onWillDismiss uses the following signature:
'onWillDismiss': () => Promise<OverlayEventDetail<any>>;

OverlayEventDetail already supports the parametrization but any type is specified here. Instead it could be using a type specified when creating the modal so this
const modal = await this.modalController.create({
  component: EditDeviceSettingsPage
});
await modal.present();
const { settings } = await modal.onWillDismiss().then(({ data }) => data);
// settings is of type any

would become
const modal = await this.modalController.create<Settings>({
  component: EditDeviceSettingsPage
});
await modal.present();
const { settings } = await modal.onWillDismiss().then(({ data }) => data);
// settings is of type Settings

Describe Preferred Solution
Add type parameter for ModalController::create to specify the possible value returned upon dismissal.
Additional Context
This would not improve the typing in the modal component itself as it could still dismiss anything it wishes. I cannot foresee any chance to improve that with the current design but this would at least improve the ergonomics on the parent.

Interested .. I will investigate in this

Thank you for the issue! This has been done with the following PR: https://github.com/ionic-team/ionic/pull/21393
Please let me know if this doesn't solve your use case and I will reopen, thanks!


simple multisig transaction builder

This add simple multisig transaction to exist simple transaction builder framework

this PR is based on #66


main: FieldValue interface

@lavrukov Please fix minor checkstyle failures:
Error:  /home/runner/work/yoj-project/yoj-project/databind/src/main/java/tech/ydb/yoj/databind/expression/values/RealFieldValue.java:13:36: 'switch' is not preceded with whitespace. [WhitespaceAround]
Error:  /home/runner/work/yoj-project/yoj-project/databind/src/main/java/tech/ydb/yoj/databind/expression/values/TimestampFieldValue.java:14:36: 'switch' is not preceded with whitespace. [WhitespaceAround]
Error:  /home/runner/work/yoj-project/yoj-project/databind/src/main/java/tech/ydb/yoj/databind/expression/values/NumberFieldValue.java:14:36: 'switch' is not preceded with whitespace. [WhitespaceAround]
Error:  /home/runner/work/yoj-project/yoj-project/databind/src/main/java/tech/ydb/yoj/databind/expression/values/FieldValue.java:37:1: '{' at column 1 should be on the previous line. [LeftCurly]
Error:  /home/runner/work/yoj-project/yoj-project/databind/src/main/java/tech/ydb/yoj/databind/expression/values/StringFieldValue.java:16:36: 'switch' is not preceded with whitespace. [WhitespaceAround]

and this will be ready to merge, I think :-)

TODO: Move FieldValue interface a package up (to where it was) for better compatibility

UPD: Brought back compatibility FieldValue interface in old package (with deprecation warnings, of course!)

@lavrukov Sasha, please look at this. I've made the FieldValue interface a bit more backwards-compatible then before, for a smooth transition :-)
(And we'll still release this as the next major version, 2.6.0)


Add Animations (AOS) on Homepage

Refer: https://michalsnik.github.io/aos/
Animations on scroll would look great on the homepage according to me!
If you have any other suggestions on how to make the homepage look more eye-catchy comment on  this ISSUE or Open a new issue here
Join our Discord if you want to discuss anything!

Do one thing let me combine all homepage related issues here i will solve in one go

#21 #57 #23

#21 #57 #23

Amazing!!!
Thank you for taking the issues @neeraj15022001 ⚡

put me as asignee i will start these after previous issue

https://user-images.githubusercontent.com/55191873/133639893-7342a846-3db5-4b07-805c-f4f66dfb2a1f.mp4
Progress till now on these three issue :

Working on navbar there is some issue coming while changing icon
Illustration changed - will change if i came across some better
Fixed order of second illustration on smaller screen size ( now there is no need to hide it )
Made spacing in footer and added new underline effect on links

@AnirudhPanda check this video

in footer and added new underline effect on links

The progress Looks Great @neeraj15022001
Should we add AOS on the cards as well? Will it look good?

in footer and added new underline effect on links

The progress Looks Great @neeraj15022001
Should we add AOS on the cards as well? Will it look good?

Will think on that

in footer and added new underline effect on links

The progress Looks Great @neeraj15022001
Should we add AOS on the cards as well? Will it look good?

Will think on that

Cool!
Let me share this PR on Discord

https://user-images.githubusercontent.com/55191873/133704347-6650a303-cd47-4ec7-be88-04fe702befcb.mov
Added Close Button to Navbar in reference to issue number #23

in reference to issue number #23 #21 changes are done
Navbar : Added close button
Footer : Fixed responsiveness and added underline effect with faster transitions
#57  Issue is almost done just searching new illustrations

in reference to issue number #23 #21 changes are done
Navbar : Added close button
Footer : Fixed responsiveness and added underline effect with faster transitions
#57 Issue is almost done just searching new illustrations

Great work!!

About AOS i believe AOS involves lots of javascript processing as there is continuous event listener listening to scrolls so it will reduce website performance and on top of that it sometimes breaks existing code, so i believe we should not add that

Illustration Changed on About Page

Illustration changed on home screen for about us section

Illustration Changed on About Page

Illustration changed on home screen for about us section

the bottom one sizing has to be done!

Then it will look way to small that's why i even scaled it up, instead we can center the content of right part. What's your thought on that?

Then it will look way to small that's why i even scaled it up, instead we can center the content of right part. What's your thought on that?

Isn't the animation way too large? Yeah we can try that ig

If i will reduce the size it will not have that much impact i mean it will look that tiny that purpose of adding image will get destroyed. Rest you can think and tell

i will make changes accordingly

Ok, I understand!
We can center that then and if we get better ideas we will modify that on a later stage

Planning this!!
https://user-images.githubusercontent.com/66218496/133971277-cdd4e65c-a31e-4965-a466-2c67307658b5.mp4

Great, this can replace current illustrations. What is source of these illustrations

Great, this can replace current illustrations. What is source of these illustrations

Canva

hey @AnirudhPanda should i close this PR now and create seperate PR's ?

@AnirudhPanda shall i add AOS ?

@AnirudhPanda can you tell me status for this issue if we need to add AOS or not ?

Hi!, I wanted to work on this issue.

@AnirudhPanda please close this i case this is resolved


Rename "tf-controller-tf-controller-planner" to "tf-branch-planner" in the Deployment YAML

rename "tf-controller-tf-controller-planner" to "tf-branch-planner" in HelmChart template

Not blocking anyone with current name.

will be resolved in https://github.com/weaveworks/tf-controller/pull/834

Closed as completed by #834


单数和复数的文件夹名称可不可以都有一个icon，例如services和service。

[ ] I'm sure this issue is not a duplicate.

[ ] I'm submitting an icon request:

Type: ``
Icon Name: service
Sample original Icon:
Extensions: ``
Filenames: ``
Language ids: ``

Language Extensions:

More info:

Google translator:

Can both the singular and plural folder names have an icon, such as services and services.

Of course, but please use english language when opening a new issue or feature request.
Cheers!

This is all Chinese to me.


Enzyme and precompilation produces segfault

The following module is to be put in a package such that it can be precompiled:
module MyModule

using Enzyme
using SnoopPrecompile

export myfunction, gradient

myfunction(θ) = θ.α^2
gradient(f, θ) = only(autodiff(Reverse, f, Active(θ)))

@precompile_setup begin
    θ = (α = 0.1,)
    @precompile_all_calls begin
        @info gradient(myfunction, θ)
    end
end

end

In Julia 1.8 and 1.9, the following will trigger a segfault. The segfault does not happen when the precompilation block above is removed.
julia> using MyModule
[ Info: Precompiling MyModule [e0b44dc7-ccfe-4aa7-a216-f44cae2f5f9d]
[ Info: (α = 0.2,)

julia> θ = (α = 0.1,)
(α = 0.1,)

julia> gradient(myfunction, θ)

signal (11): Segmentation fault
in expression starting at REPL[3]:1
unknown function (ip: 0x7f96c1fd8010)
macro expansion at ~/.julia/packages/Enzyme/DIkTv/src/compiler.jl:6819 [inlined]
enzyme_call at ~/.julia/packages/Enzyme/DIkTv/src/compiler.jl:6544 [inlined]
CombinedAdjointThunk at ~/.julia/packages/Enzyme/DIkTv/src/compiler.jl:6507 [inlined]
autodiff at ~/.julia/packages/Enzyme/DIkTv/src/Enzyme.jl:217 [inlined]
autodiff at ~/.julia/packages/Enzyme/DIkTv/src/Enzyme.jl:248
Allocations: 2762221 (Pool: 2760938; Big: 1283); GC: 3
Segmentation fault (core dumped)

Julia 1.8 version info
julia> versioninfo()
Julia Version 1.8.5
Commit 17cfb8e65ea (2023-01-08 06:45 UTC)
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 8 × Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-13.0.1 (ORCJIT, skylake)
  Threads: 1 on 8 virtual cores

Julia 1.9 version info
julia> versioninfo()
Julia Version 1.9.0-rc1
Commit 3b2e0d8fbc1 (2023-03-07 07:51 UTC)
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 8 × Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-14.0.6 (ORCJIT, skylake)
  Threads: 1 on 8 virtual cores

What happens when you use Enzyme.jl#main?

I'd like to try that out<EMAIL_ADDRESS>doesn't seem to be registered:
(MyModule) pkg> add Enzyme#main
    Updating git-repo `https://github.com/EnzymeAD/Enzyme.jl.git`
   Resolving package versions...
ERROR: Unsatisfiable requirements detected for package EnzymeCore [f151be2c]:
 EnzymeCore [f151be2c] log:
 ├─possible versions are: 0.1.0-0.2.0 or uninstalled
 └─restricted to versions 0.2.1-0.2 by Enzyme [7da242da] — no versions left
   └─Enzyme [7da242da] log:
     ├─possible versions are: 0.11.0 or uninstalled
     ├─restricted to versions * by MyModule [e0b44dc7], leaving only versions 0.11.0
     │ └─MyModule [e0b44dc7] log:
     │   ├─possible versions are: 0.1.0 or uninstalled
     │   └─MyModule [e0b44dc7] is fixed to version 0.1.0
     └─Enzyme [7da242da] is fixed to version 0.11.0-dev

Correct, try add EnzymeCore#main add Enzyme#main

Unfortunately the issue persists on Enzyme#main.

Can you post what output occurs when you add a Enzyme.API.printall!(true) after the import.
Also can you paste @code_llvm and @code_typed of running the code that segfaults?

@simsurace you need to use Enzyme.API.printall!(true) before any call to autodiff

I'd be happy to provide more info or to run more tests, but I'm not sure what is missing.

@simsurace how exactly did you set this up to test. I'm failing to set up and trigger this.

For example, my setup:
wmoses@beast:~/git/Enzyme.jl (inac_boxchar) $ cat snp.jl
module MyModule

using Enzyme
using SnoopPrecompile

export myfunction, gradient

myfunction(θ) = θ.α^2
gradient(f, θ) = only(autodiff(Reverse, f, Active(θ)))

@precompile_setup begin
    θ = (α = 0.1,)
    @precompile_all_calls begin
        @info gradient(myfunction, θ)
    end
end

end

using .MyModule

θ = (α = 0.1,)
gradient(myfunction, θ)

$ ./julia-1.9.0-rc1/bin/julia --project snp.jl
# No error

I will make a repo for reproducibility when I get back to my computer. Thanks for trying.

I created a package EnzymePrecompilationTest. Simply clone and run the tests. The segfaults also appear in the CI.

Just a heads up, I just re-tested and EnzymePrecompilationTest](https://github.com/simsurace/EnzymePrecompilationTest.jl) is still broken with Enzyme v0.11.8.

From earlier conversations, I believe this is an upstream issue where there needs to be support for precompilation in GPUCompiler.
cc @vchuravy @gbaraldi @maleadt

My recollection from last chat with v churavy:
you cannot use Enzyme in precompiled code, since effectively we'll jit the
new function, which is valid in that session, but if you restart julia [and
reload that function pointer from the sysimage], its just a random pointer
that hasn't been jit'd and will segfault
He said that we may be able to add support for sys images in GPU compiler
and then generate pointers that continue to be valid
On Mon, Sep 25, 2023 at 8:09 AM Tim Besard @.***> wrote:

I believe this is an upstream issue
I'm not sure how? I only see a segfault in Enzyme here, what makes you
think this GPUCompiler related?
—
Reply to this email directly, view it on GitHub
https://github.com/EnzymeAD/Enzyme.jl/issues/681#issuecomment-1733680948,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJTUXHI3PZTTEEIZJDAO6DX4F7BTANCNFSM6AAAAAAWA43VGU
.
You are receiving this because you commented.Message ID: <EnzymeAD/Enzyme.
@.***>


Update iot-hub-csharp-csharp-getstarted.md

Added missing directive so Task.Delay would compile

Hi @khilscher, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (kevin.hilscher). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@khilscher - Hi, thanks for your contribution. We are in the process of refactoring the Azure technical articles, so we can’t merge this PR. When the refactoring is complete, we can give you a link to the new location of the article you updated so you can resubmit your update, if you want to.

@khilscher - Thanks for your contribution to the Azure docs. On November 16th, we announced the availability of our Azure technical documentation in a new location on docs.microsoft.com. You can read about it on our team blog. This change means the article source lives in a new GitHub repository. Because there are some changes in the source markdown as a result of the move, we can’t pull your contribution over to the new repo without creating a ton of merge conflicts. We invite you to resubmit the change (if you are willing) to the new version of the article at https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-csharp-csharp-getstarted. Thanks for your understanding.


Refactor Apparmor Profile generation

We now have a way to resolve conflicts between local and global profile allowing us to set a priority order in the code for what to expect when conflicting rules exist between a global policy and fromSource.
This conflict deemed a complex resolution logic so I ended up refactoring the profile generation logic to more freely analyse and manipulate the profiles.
TODO

[ ] Add test cases
[ ] Handle in BPF LSM ( Will be handled in seperate PR )

Ref #787

LGTM!

@daemon1024 Can you please squash your commits.

@daemon1024 Can you please squash your commits.

@achrefbensaad The commits address different problems individually, would prefer to keep it this way!

Codecov Report

Merging #796 (69339dd) into main (5af0ae9) will increase coverage by 2.23%.
The diff coverage is 51.16%.

:exclamation: Current head 69339dd differs from pull request most recent head c302a37. Consider uploading reports for the commit c302a37 to get more accurate results

@@            Coverage Diff             @@
##             main     #796      +/-   ##
==========================================
+ Coverage   38.62%   40.86%   +2.23%
==========================================
  Files          29       30       +1
  Lines        9423     9103     -320
==========================================
+ Hits         3640     3720      +80
+ Misses       5300     4905     -395
+ Partials      483      478       -5

Impacted Files
Coverage Δ

KubeArmor/enforcer/appArmorProfile.go
52.58% <49.24%> (+6.66%)
:arrow_up:

KubeArmor/enforcer/appArmorTemplate.go
100.00% <100.00%> (ø)

KubeArmor/feeder/policyMatcher.go
49.58% <0.00%> (+0.41%)
:arrow_up:

KubeArmor/core/kubeUpdate.go
49.10% <0.00%> (+0.62%)
:arrow_up:

KubeArmor/enforcer/runtimeEnforcer.go
32.88% <0.00%> (+1.34%)
:arrow_up:

KubeArmor/core/kubeArmor.go
52.74% <0.00%> (+2.62%)
:arrow_up:

KubeArmor/monitor/logUpdate.go
73.89% <0.00%> (+3.38%)
:arrow_up:

KubeArmor/common/common.go
42.68% <0.00%> (+4.06%)
:arrow_up:

KubeArmor/core/dockerHandler.go
53.33% <0.00%> (+53.33%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Multiple subprojects trunk under one project migrate\export to one project.

Hi Team,
I have 2 subproject trunks in one tfs  project.
for e.g. $/project
$/project/subprojectA/TRUNK
$/project/subprojectB/TRUNK
I need to export or migrate with tfs history into one git hub repository.
How can i achieve that?
Let me know if you have any questions.
Thanks!

Good luck because it will be difficult to achieve and you will need a lot of trial/error steps...

I think this is answered by the different proposals from @pmiossec , can we close this issue?


Organization of test project should use test/Project.toml

Code at https://github.com/invenia/PkgTemplates.jl/blob/master/src/generate.jl#L141-L162
try
    Pkg.activate(pkg_dir)
    Pkg.add("Test")

    # Move the Test dependency into the [extras] section.
    toml = read(joinpath(pkg_dir, "Project.toml"), String)
    lines = split(toml, "\n")
    idx = findfirst(l -> startswith(l, "Test = "), lines)
    testdep = lines[idx]
    deleteat!(lines, idx)
    toml = join(lines, "\n") * """
    [extras]
    $testdep
    [targets]
    test = ["Test"]
    """
    gen_file(joinpath(pkg_dir, "Project.toml"), toml)
    Pkg.update()  # Regenerate Manifest.toml (this cleans up Project.toml too).
finally
    proj === nothing ? Pkg.activate() : Pkg.activate(proj)
end

does not follow the new organization of test project based on test/Project.toml from Julia v1.2
One does not need to split and shake so much the main project.toml starting from now.
[extras] will become obsolete in v2.
See
https://julialang.github.io/Pkg.jl/v1/creating-packages/#Adding-tests-to-the-package-1

I don't think I actually want this yet, because Julia 1.0 is still supported and it won't work for that version. Of course we could decide what to do based on the chosen Julia version to support as well.
In #61, the test generation is its own plugin instead of being some special thing, so I think that the best thing to do would be to add a project flag to it (and when it's true, generate a new Project.toml instead of adding the [extras] section).
And FWIW, in #61 the modifications of Project.toml happen via Pkg.TOML and normal Dict updates, rather than the current ugly text substitution :slightly_smiling_face:.

Agree that before v2, may be in 2020 something, there's no emergency. It's only (re)-orientation.
So you will go with a big patch fea66eaf6f303afa697d80f1fb9af673d7e64694 next time. Lot of work there!
I am borrowing you some of your code i appreciate, thanks.
To be more precise, i follow the programming in the small way you took, but not the programming in the large. Recipes are good, gathering may be less IMHO.
Every successful framework i know today have more or less reimplement a make as an internal dsl and try to generate initial stuff over it. I believe it's the way to go and the one i will follow.

And FWIW, in #61 the modifications of Project.toml happen via Pkg.TOML and normal Dict updates, rather than the current ugly text substitution slightly_smiling_face.

I have seen that
https://github.com/invenia/PkgTemplates.jl/blob/fea66eaf6f303afa697d80f1fb9af673d7e64694/src/plugins/defaults.jl#L157-L162
looks way better :slightly_smiling_face:


add diff ignore paths

When using kubecfg in combination with openshift, some issues arise due to openshift either having a broken api spec (e.g the status field in route objects is not optional) or updating the spec by using triggers.
This PR allows to specify one or multiple paths to ignore when calculating diffs.
For example --ignore='spec.template.spec.containers.0.image' ignores changes to image of the first container in a deploymentconfig.

i've encountered some issues with this approach. i'll rewrite this (possibly without external dependencies) and submit a new PR


[DOC]: fix obsolete documentation moved

[ ] I have followed (at least) the PR section of the contributing guide.

I have moved the documentation part as written in this comment: https://github.com/mui/material-ui/pull/32937#issuecomment-1140294051
This should solve this issue: https://github.com/mui/material-ui/issues/36573

Codecov error in ci, I cannot understand why. Can someone explain it to me?


add support for pagination in application list

PR summary
Add support for pagination in list applications method
Fixes: <! -- link to issue -->
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[x] Feature
[x] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Integration tests -
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
Ran 173 of 173 Specs in 173.634 seconds
SUCCESS! -- 173 Passed | 0 Failed | 0 Pending | 0 Skipped
--- PASS: TestIbmAnalyticsEngineApiV3 (173.69s)
PASS
ok      github.com/IBM/ibm-iae-go-sdk/v2/ibmanalyticsengineapiv3        174.772s

:tada: This PR is included in version 2.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add support using pooled direct buffers for Redis commands

Background
https://github.com/turms-im/turms/issues/786


Integration credentials not available

System Health details
Up-to-date
Checklist

[X] I have enabled SmartInspect debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue
SpotifyPlus integration for credentials is not available in an up-to-date install.
Created the described credentials on the spotify dev page, however I can only create spotify credentials and not the spotifyplus as in the manual on git.
Is this not necessary anymore and is the "Spotify" credentials enough?
Reproduction steps

Debug logs
-

Diagnostics dump
No response

@tudstudent Not for sure what you mean by "SpotifyPlus integration for credentials is not available in an up-to-date install" ...
I assume you already have a Spotify Premium account setup, and are referring to the Spotify Developer App credentials creation process in Step 2 of the  instructions?  The Spotify developer app is required in order to use the SpotifyPlus integration.  If successful, you should have a Spotify Developer App client id and client secret value.
What do you mean by "_ ... however I can only create spotify credentials and not the spotifyplus as in the manual on git._"?
Are you referring to Step 3 - Home Assistant Application Credentials?

Sorry, half my message dropped. I have indeed created on the spotify website te dev credentials (the unique code).
I installed your software through HACS. Also no problem and the card is available.
However in 1 step you describe how to connect the HA environment to spotify with the created credentials.
Therefore we need to go to devices and integrations and the credentials, you then describe dropdown -> SpotifyPlus. This one is not existent.

Are you referring to the Step 3a - Add Application Credentials step?
And is it this form that does not contain the "SpotifyPlus" entry in the "Integrations" dropdown list?

If so, then something went wrong in the HACS installation - there should be a "SpotifyPlus" entry in that drop down list if the HACS Installation Instructions were followed.  Note that you have to "restart HA to start using the component" after the download and install step is complete.
This could be related to a browser caching issue as well.  You might try clearing your browser cache and restarting HA.

Sorry, no luck.
I cannot get the SpotifyPlus in my install...
Redownloaded, rebooted, and cleared cache.

Do you see the "Spotify" integration in the "Add Credentials" list?  Just curious if it is in the list.
I would also ensure that you look at the entire dropdown list (scroll to the bottom of the list) to ensure the "SpotifyPlus" entry is not listed at the bottom of the list.  The list should be sorted in alphabetical order if the cache was cleared; if not, then the "SpotifyPlus" entry will appear at the bottom of the list.
Another thing to verify is your installed version of HACS - make sure you are running the 2.0.1+ version.

Also, are there any entries in the HA system log regarding SpotifyPlus or HACS?
You might also try using the Manual Installation instructions to install the integration.  This is not optimal I know, but obviously something is going wrong with the HACS install.
I am not sure where to direct you on this, as the HACS install if failing to register the integration.

HACS version installed: 2.0.1
In  "Add Credentials" list "Spotify" Exists, and I configured it to see if the plus became available.
No Pus whatsoever, not by searching, not by scrolling.
Is there a log we can look to see what should happen (and if there is an error).

Take a look at the system log (Settings \ System \ Log).  Click on the "Load Full Logs" button to view the entire log.
I still believe it's a caching issue ...  What browser are you using?
Also to verify ... when you cleared your browser cache, did you clear ALL type of cache entries: files, cookies, and images?  Both "cookies" and "files" need to be cleared, then restart Home Assistant.

Firefox and Chrome (on same pc same result)
Android (firefox -> same result)
So for me it doesn't feel as caching to be honest (however I hope being wrong)

Any relevant messages in the system log? (Settings \ System \ Log). Click on the "Load Full Logs" button to view the entire log.

"And the plugin needs to be created as a dashboard item not a integration (in case of system rights whatsoever?)"
The SpotifyPlus integration needs to be created as an Integration (not dashboard), as stated in the installation docs.  If you specified "dashboard", then that is incorrect - you will need to uninstall from HACS and re-install.
To clarify, you are trying to install the "SpotifyPlus Integration", yes?  and NOT the "SpotifyPlus UI Card"?

Today, not my best day I think....
Thanks for supporting, I screwed up tremendously indeed. I installed the Card UI and not the Integration.
It now ask to reboot (instead of refresh).
After reboot I see now indeed SpotifyPlus.
Sorry my bad, I was already wondering why the versioning did not look OK in the first GIT I looked as in HACS it was lower, but the integration has the correct number.
Again thanks and sorry for my mess-up.

No worries, glad we got it figured out.
The SpotifyPlus Card is new (still in beta), and is a front-end UI / dashboard to the "SpotifyPlus integration" media player.   Feel free to try it out if you like, just be sure to get the "SpotifyPlus integration" installed and configured first.

Yep, got it working right away.
Playing with the UI card right now (works already, however I am searching to make it screen width).
Furthermore need to see how "casting" works, as I currenlty use my sonos, but want to use per room speakers (so casting to a "media device" is more flexible, but I think this should be doable.
But anyway wanted to let you know all works at this moment.


TwoStretchSource

Just discussed with @drhay53 about adding the "two stretch model". It would be really similar to the implementation of StretchSource, but with an extra stretch parameter. Something like:
class TwoStretchSource(Source):
    _param_names = ['amplitude', 's1', 's2']  # extra stretch parameter
    param_names_latex = ['A', 's_1', 's_2']

    def __init__(self, phase, wave, flux, name=None, version=None):
        self.name = name
        self.version = version
        self._phase = phase
        self._wave = wave
        self._parameters = np.array([1., 1., 1.])  # initialize both stretches to 1.
        self._model_flux = Spline2d(phase, wave, flux, kx=2, ky=2)

    def minphase(self):
        return self._parameters[1] * self._phase[0]  # minphase uses first stretch

    def maxphase(self):
        return self._parameters[2] * self._phase[-1]  # max phase uses second stretch

    def _flux(self, phase, wave):
        # for phases less than 0, adjust by first stretch.
        # for phases greater than 0, adjust by second stretch.
        mphase = np.where(phase < 0.,
                          phase / self._parameters[1],
                          phase / self._parameters[2])
        return self._parameters[0] * self._model_flux(mphase, wave)

What is the proper github-y way for me to test this? Fork SNCosmo, add this to the source code, test it out, and do a pull-request?

I am a little confused. I thought the stretch relates the time - peak to phase through:
(time - peak) =stretch* phase and this would be generalized to two equations depending on whether phase was positive or negative. But _flux for a particular phase would not depend on these stretch parameters. Similarly I would have expected minphase and maxphase to be independent of the stretch parameters.
Maybe this is a very different kind of model ?

@drhay53 You need not modify the sncosmo source to use this. You can just plop it in a file mymod.py:
import numpy as np
import sncosmo
from scipy.interpolate import RectBivariateSpline as Spline2d

class TwoStretchSource(sncosmo.Source):
    #
    # see source above
    #

# create a model using the source you just defined
source = TwoStretchSource(phase, wave, flux)  # need to get the phase, wave, flux grid separately
model = sncosmo.Model(source=source)
# fit the model or whatever...

@rbiswas4 There are two separate "phases" here. self._phase contains the phases corresponding to stretch of 1. The phase input to the _flux method is the actual observed "time - peaktime" in the SN restframe. The two are related via phase = self._phase * s.

@kbarbary is there no way to access the default phase and wavelength of a built-in sncosmo.Model? For testing, I would want to just load the hsiao template and use whatever is there as the template for TwoStretchSource.

Unfortunately, there's no good way that's well documented!
Here's a hack:
from sncosmo.builtins import get_url
from astropy.utils.data import download_file

remote_url = get_url('hsiao', version='3.0')
fn = download_file(remote_url, cache=True)
phase, wave, flux = sncosmo.read_griddata_fits(fn)

This depends on a very recent change so be sure you're working with current sncosmo master.

I thought _phase, _wave accessed the native values that were read in ... is
that changed?
On Mon, Jan 26, 2015 at 3:04 PM, Kyle Barbary<EMAIL_ADDRESS>wrote:

Unfortunately, there's no good way that's well documented!
Here's a hack:
from sncosmo.builtins import get_urlfrom astropy.utils.data import download_file
remote_url = get_url('hsiao', version='3.0')
fn = download_file(remote_url, cache=True)
phase, wave, flux = sncosmo.read_griddata_fits(fn)
This depends on a very recent change so be sure you're working with
current sncosmo master.
—
Reply to this email directly or view it on GitHub
https://github.com/sncosmo/sncosmo/issues/66#issuecomment-71557586.

@rbiswas4 Yes, it's true that you can get the phase and wavelength grids by doing, e.g.,
source = sncosmo.get_source('hsiao')
phase, wave = source._phase, source._wave

but even this is a hack because these attributes start with _ and are therefore meant to be "private" variables (in the Python sense).
The flux grid on the other hand is not even saved directly; only the interpolation coefficients are saved (in the source._model_flux attribute). I suppose you could reconstruct the flux grid by doing
flux = source.flux(source._phase, source._wave)

@kbarbary is there a reason why phase and wave are not public?
Or, going a different direction; could a source just learn it's phase/wave/flux directly from a model?

@drhay53 In fact, phase and wavelength used to be public in previous versions (v0.2 and before I think). The reasoning for making them private is that not all sources will necessarily have a "native" grid of phases and wavelengths (though all currently implemented models do). For example, imagine some model based on gaussian processes. Therefore, none of the functions that interact with models (such as fit_lc or plot_lc) should assume that the model has a grid of phases and wavelengths.
You could also say that the model is a smooth spectral surface and the grid is irrelevant: The fact that the smooth surface is initialized by fitting B splines to a grid of points when you call Source.__init__() is an "implementation detail," as they say.
All that said, one could make public the grids for models that define them, being careful not to rely on the grids for anything that is supposed to work on any general model.
I think in your second question you're asking if you could initialize, for example a TwoStretchSource from an already-initialized TimeSeriesSource, such as:
source1 = sncosmo.get_source('hsiao')
source2 = sncosmo.TwoStretchSource(source1)

I've thought about making this possible. My hesitation is that the Hsiao template (or any other simple spectral timeseries) could be used equally well in a TimeSeriesSource, a StretchSource, or a TwoStretchSource. Why should get_source('hsiao') return the first rather than the second or third? Perhaps we should make the initialization something like:
source1 = sncosmo.TimeSeriesSource('hsiao')
source2 = sncosmo.TwoStretchSource('hsiao')

where passing in the string 'hsiao' rather than phase, wave, flux means to load the phase, wave, flux from the Hsiao template. I kinda like that, but it makes initializing a Model in a single line harder.

Closing this as outside the scope of sncosmo for the time being.


ISPN-5141 SingleFileStore.process() should use sequential access

Sort the list of keys by offset before processing.
https://issues.jboss.org/browse/ISPN-5141

Why was this fixed? Did it do it slowly before? Or did you throw any errors?

Oh, I've seen the email thread, i'll add it as link in the JIRA

Integrated