"Your docs are so great that I want a build of them w/ my theme" tips

Hi all:
For better or worse, I have a project that combines:

some selectively exported SUIR components, &
some custom inhouse components

I'm after the holy grail.

i need my UX team engaged in Code Reviews, so we use storybook's awesome service to deploy a static website on each commit, w/ all of our UI widgets on display
i need documentation for my inhouse components & want a widget playground for my custom components, so we integrate a styleguidist frame into our storybook
more importantly, i want to be able to see & get rolling updates of your great work in SUIR with my theme applied over it!

right now, I just iframe over to your docs, as seen above. it's a total hack.
because semantic themes have other assets beyond CSS, I can't just mess w/ the frame & inject my theme over it.
im brainstorming some ways to achieve my goal.  the goal is, get SUIR docs to render my custom theme.  i could:

clone suir, install deps, squash your assets, build

it intensive, slow, and arguably fragile

extract docs out of this package, into semantic-ui-react-docs. this exports an executable & a lib to control the build

node_modules/.bin/suir-docs --assets <my-asset-dir> -o <my-dest>
const suirDocs = require('suir-docs'); suriDocs.build(config)
this is invasive to the project, & i'd imagine you all wouldn't be nuts about it.  regardless, it could be pretty cool!  it would shrink this project up!

add some hooks into the docs website that enables me to swap assets

using postMessage the CSS could likely easily be swapped if in an iframe.  not sure about handling images/fonts, but they could possibly be Blobable and passed thru messaging.

<other-ideas-here>

anyway, thx for reading this far!  i appreciate your time. great work!

TL;DR
Yep.  Love this and have thought through all these same things.  In fact, I've built a few prototypes as well.  Here are my thoughts:
Component Explorer
I do like the docs we have, but, I'd like to have a component explorer more similar to react storybook.  See #427 for early prototypes.
The general idea is to give these things simultaneously:

a single rendered example
a form for changing component props (generated from the component props)
a set of predefined examples so choose from
the same code editor we currently have

How is this different than storybook?  The generated form for trying out different component props easily and the code editor to edit the full example live.  Essentially, it is more dev friendly.  Aside from that, it is obviously completely tailored to our build.
Themes
Yes!
A
I've built an in-browser theme customizer with hot CSS in the past, for bootstrap.  The app is old and slow, but you can get the idea here: http://bootstylebeta.herokuapp.com:

B
There is also an in-browser SUI theme toy for the GitHub rebuild example: http://semantic-org.github.io/example-github/

C
Finally, there is the theme selector for many examples in SUI core docs: http://semantic-ui.com/elements/button.html

I'd like to allow a way to build and preview themes in the docs, somehow.  I've been thinking this might be in the form of a theme customizer tool in the docs as in "A", maybe.  At a minimum, a way to select a theme similar to "B" and "C" above.
I've also been thinking perhaps this new method of theming and/or applying themes should also include a better way to theme our own components.  You can a lot of my thoughts on that here, #1009.
Lots of ideas and options here, just not yet totally sure which is the best way to go.  I do think I want to keep this as a doc site app feature.

thanks for the super detailed response!

Component Explorer

yup.  its fantastic ™.

Themes

i'm super in favor of a pure, native web-app.  however, themes cannot be applied completely in this strategy because non-CSS assets do not have a way of being reliably loaded.  we added on some extra fonts & imgs that integrate w/ SUIR components for example, that I consider key to our experience.  maybe that's too much to ask to support!  regardless, the only way I see my use case working is a means to essentially run a build on your docs w/ my content.  a little webservice attached to the webapp could also facilitate that, but bleck, that's a lot of work!

I see.  You could certainly clone our repo and run a build.  All scripts are in the package.json.
The doc site is a React app that lives in /docs/app.  The config is webpack.config.js.  The script to build them is npm run build:docs.  The built docs are emitted to /docs/dist.
I'm open to ideas and PRs for anything that takes us closer to a themeable doc site.  I'll close this issue for now but we can continue the discussion if needed.  Thanks for the taking the time to raise these points.  I trust we'll get some level of support here in the future one way or another.

cool, that's helpful.  i may need to automate that in our CI build!

Im sorry If I'm out of context here.
I did manage to build storybook inside a boilerplate with Phoenix+Webpack2+React+Semantic-UI-React-Semantic-UI-less
I am able to apply modifications on CSS and have it auto-reload with my own theming into semantic-ui-less variables and site overrides
Anyways, I thought it would be cool to use storybook for semantic-ui with plugins and stuff
anyways @cdaringe lemme know if you're still looking into this!

thanks @agustif.  i did end up finding an OK solution.  i do a SUI theme build, & pull in the theme into a react-styleguidist build.  we went styleguidist because our lib takes SUIR + theme-overrides as input, and provides SUIR & our own additional components as output, thus wanted the documentation engine that storybook just doesn't quite yet have yet.  here's a ref.  the caveat to our strategy is that we dont get all of SUIR examples which help make this project so great, and have to manually backfill them!
i also wrote a little package, surge-review, that makes the workflow really great.  once our CI builds the docs site on each pull request, surge-review posts the static build to surge (CDN), and then updates our PRs with a link the the documentation build. woo hoo 🎉

I also put together a solution to this problem here.
The repo is a clone of the Semantic UI React, with a themes directory at the root. In themes/src, there are two directories:

themes/src/themes: themes that get built
themes/src/themseTemplate: an empty template to create new themes from scratch

The themes directory also contains two directories:

parent-theme: a parent theme where general overrides can be defined
child-theme: a child theme where variables are defined, which are consumed by the overrides in the parent theme

I wrote this to be able to create multiple themes that share common characteristics, e.g. light and dark theme for the same application. So the color variables are defined in the child theme, and the overrides are defined in the parent theme, which consume the color variables.
If you clone the repo, run yarn reset, yarn build:themes, and yarn start to see the official Semantic UI React docs in dev mode and be able to instantly see changes to your themes as you write them.
I also added the capability of using Font Awesome native classes so you can write <Icon name='fas fa-check'> and the check icon will render.
I just finished it yesterday so I still have to write a proper readme and add some examples for additional features like icons with Font Awesome classes or styling of third party components but that is coming soon.

This is great.  We're doing a lot of work in the new https://github.com/stardust-ui/react repo around themes and docs.  We want to share that experience here in Semantic UI as well.  It will also likely be used by another large open source repo and some corporate private repos.
All said, we want to start modularizing our doc experience and sharing features between Stardust and Semantic.  Stardust supports typescript and has a "Transparent" background feature.  Semantic has prettier integration and runs babel.  I'd like to merge all these things into a singe clean experience that people can install and use in their own project.
I'd like to publish this doc experience from Stardust UI.  A good start would be cleanup and separate the concerns of each component used in the doc experience.

Thanks for your reply @levithomason!
I had not heard of Stardust UI but it looks great. Is it still a work in progress or are there more components coming to it soon?
Some of the most important reasons why I decided to write the Semantic UI theme builder were

To provide a centralized place where themes could be developed, versioned, built for production, and pulled from as other project's dependencies
To provide the Semantic UI docs web app, ready for deployment to a project's hosted domain, themed with the project's themes. The intention is that a project's UI/UX team can review the state of all of the project's themed components, as well as all other available components that have not yet been styled to the projects design specs
To include an 'Externals' component section in the Semantic UI docs web app so that SUI themes can also include styling for external components such as react-datepicker, react-table, etc. which consume the project's color variables and other common design parameters
To support the use of third party icon libraries like Font Awesome Free, Font Awesome Pro, etc.

Have you considered these points in the purpose and design of Stardust as well?
It would be excellent if Stardust also addressed these issues :)


Player loading and device orientation change animation - white screen behind the player view

When the YouTubePlayer is being rotated there is white screen showing behind the view. When the player view is being loaded - white screen is also showing. Changing the background colour doesn't help. I also tried changing the theme to dark.

hi.
Change your html  using this:
<head>
    <style>
        * { margin: 0; padding: 0; }
        html, body { width: 100%; height: 100%; }
        </style>
    <body style="background-color:black;">
</head>


Fix to Page Format Wizard

A fix to the wizard submitted to me by a Facebook user

Thanks for that... Yeah, the fix he sent me bothered me as well (seemed convoluted), but since it was 'working' I didn't pursue it. Your solution actually makes sense to me.
I took advantage of the fact that I got the linting check working on Zerobrane and eliminated all other linting errors as well.

Great, I absolutely will! Maybe not immediately, but soon… I’m at a choir director’s conference for the next few days but might have some pockets of time!

On Jan 25, 2024, at 4:39 AM, rpatters1 @.***> wrote:
Merged #657 https://github.com/finale-lua/lua-scripts/pull/657 into master.
—
Reply to this email directly, view it on GitHub https://github.com/finale-lua/lua-scripts/pull/657#event-11596777246, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMCBUQYQPEEOQO5KALNUO3DYQJG7DAVCNFSM6AAAAABCIKWKSGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGU4TMNZXG4ZDINQ.
You are receiving this because you authored the thread.


A11y: Line item - Voice-over sequence not following logical flow

The voice-over in line item of custom products is not following a logical or consistent sequence during playback. The narration jumps between sections, causing confusion and disrupting the overall user experience. This issue affects all users and needs to be resolved urgently.
Steps to Reproduce:
Open a line item of custom products in offcanvas and navigate to the section with the voice-over.
Play the audio and observe how the sequence is illogical and out of order.
Expected Result:
The voice-over should follow a clear, logical sequence that aligns with the intended script.
Actual Result:
The audio jumps between sections, causing it to be out of sync with the expected narrative flow.
!Screen Recording 2024-10-10 at 15.34.02.mov|width=3826,height=1858,alt="Screen Recording 2024-10-10 at 15.34.02.mov"!

[public] Shopware automated response: This issue is linked to the internal issue: CUS-746
[created from CUS-746, comment 502488]


Do not offer all the attributes for composite fields in a model or a type

The validation issue is in prisma/prisma, but the autocompletion for fields that point to a composite type should only list @ignore.
https://github.com/prisma/prisma/issues/14252

We should probably also list @default.


Add Gardener upgrade tests

How to categorize this PR?
/area testing high-availability
/kind test enhancement

What this PR does / why we need it:
This PR adds below test cases to Gardener upgrade test suite.

Gardener upgrade Tests for Shoot::e2e-upgrade when Pre-Upgrade (Gardener version:'v1.61.4')

should create a shoot [pre-upgrade]
deploying zero-downtime validator job to ensure no downtime while after upgrading gardener [pre-upgrade]

Gardener upgrade Tests for Shoot::e2e-upgrade when Post-Upgrade (Gardener version:'v1.62.0-dev')

should be able to restore etcd when etcd pod's pvc is corrupted in previous gardener release: [post-upgrade, etcd, high-availability]
verifying no downtime while upgrading gardener [post-upgrade]
should able to delete a shoot which was created in previous release [post-upgrade]

Gardener upgrade Tests for Shoot::e2e-upgrade-ha when Pre-upgrade (version:'v1.61.4')

should create a shoot [high-availability, pre-upgrade]

Gardener upgrade Tests for Shoot::e2e-upgrade when Post-Upgrade (Gardener version:'v1.62.0-dev')

should be able to upgrade a non-HA shoot which was created in previous gardener release to HA with failure tolerance type 'zone' [high-availability, post-upgrade]
should be able to delete a shoot which was created in previous gardener release [high-availability, post-upgrade]

Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
cc: @rfranzke
Release note:

/test pull-gardener-e2e-kind

should be able to restore etcd when etcd pod's pvc is corrupted in previous gardener release

Isn't this rather a e2e2-test we want to have in Etcd-Druid or do you want to test any specific Gardener functionality here?

should be able to restore etcd when etcd pod's pvc is corrupted in previous gardener release

Isn't this rather an e2e-test we want to have in Etcd-Druid or do you want to test any specific Gardener functionality here?

I understand your point, and it's indeed valuable to have such a test case in the Gardener E2E test suite. By including this test case, we can simulate real-time scenarios where an etcd PVC might get corrupted during the Gardener upgrade of a shoot cluster.

should be able to restore etcd when etcd pod's pvc is corrupted in previous gardener release

Isn't this rather an e2e-test we want to have in Etcd-Druid or do you want to test any specific Gardener functionality here?

I understand your point, and it's indeed valuable to have such a test case in the Gardener E2E test suite. By including this test case, we can simulate real-time scenarios where an etcd PVC might get corrupted during the Gardener upgrade of a shoot cluster.

I have trouble understanding this scenario-  why would an etcd PVC get corrupt during a Gardener upgrade? Can you explain when/how this would happen?
From my current understanding, I would rather second @timuthy's point and agree that such test case rather belongs to gardener/etcd-druid and is not related to gardener/gardener.

Gardener upgrade Tests for Shoot::e2e-upgrade-ha when Pre-upgrade (version:'v1.61.4')

should create a shoot [high-availability, pre-upgrade]

Gardener upgrade Tests for Shoot::e2e-upgrade when Post-Upgrade (Gardener version:'v1.62.0-dev')

should be able to upgrade a non-HA shoot which was created in previous gardener release to HA with failure tolerance type 'zone' [high-availability, post-upgrade]
should be able to delete a shoot which was created in previous gardener release [high-availability, post-upgrade]

What is this test case about? We upgrade the non-HA shoot to HA after we upgraded Gardener, and then delete it? Don't we already have upgrade tests like this? In https://prow.gardener.cloud/view/gs/gardener-prow/pr-logs/pull/gardener_gardener/7786/pull-gardener-e2e-kind-ha-multi-zone-upgrade/1646807961093279744, I see

Test E2E Gardener Suite: [It] Gardener upgrade Tests for Shoot::e2e-upgrade-ha when Post-Upgrade (Gardener version:'v1.69.0-dev', Git version:'v1.69.0-dev') should be able to upgrade a non-HA shoot which was created in previous gardener release to HA with failure tolerance type 'zone' [high-availability, post-upgrade]

Isn't this exactly this case?
Also, what about https://github.com/gardener/gardener/issues/2692? Isn't such scenario (deleting without previous reconciliation) more valuable?

What is this test case about? We upgrade the non-HA shoot to HA after we upgraded Gardener, and then delete it? Don't we already have upgrade tests like this? In https://prow.gardener.cloud/view/gs/gardener-prow/pr-logs/pull/gardener_gardener/7786/pull-gardener-e2e-kind-ha-multi-zone-upgrade/1646807961093279744, I see

In this job pull-gardener-e2e-kind-ha-multi-zone-upgrade we are trying to upgrade non-HA shoot cluster to HA in same release.
In this test case, the goal is to upgrade a non-HA shoot created in the previous release to an HA shoot in the next release. We discovered a critical bug https://github.com/gardener/gardener/pull/7434 while I was testing this test case only.

I have trouble understanding this scenario- why would an etcd PVC get corrupt during a Gardener upgrade? Can you explain when/how this would happen?

@rfranzke Let's say, for some reason, etcd's PVC gets corrupted during or before the Gardener upgrade. The next release should not be affected in terms of restoring the data. This test case is not only about PVC corruption; it also covers scenarios where one of the etcd nodes is down and recovering. There should not be any downtime in the cluster, and this test ensures that the next release does not cause any downtime while one of the etcd nodes is recovering.

Isn't this exactly this case?
Also, what about #2692? Isn't such scenario (deleting without previous reconciliation) more valuable?

We are already covering this test case:

should able to delete a shoot which was created in previous release [post-upgrade]

This test case addresses the scenario you mentioned (#2692), ensuring that a shoot created in the previous release can be deleted successfully

/test pull-gardener-e2e-kind-ha-single-zone

/test pull-gardener-e2e-kind-migration

I have trouble understanding this scenario- why would an etcd PVC get corrupt during a Gardener upgrade? Can you explain when/how this would happen?

This test case is not only about PVC corruption; it also covers scenarios where one of the etcd nodes is down and recovering.

Again, even if it's about this, this is all something related to etcd-druid, isn't it? Which role does Gardener play here? It has nothing to do with managing the etcd pods other than deploying the desired state of the Etcd resource. I still think all this belongs to etcd-druid only.

Isn't this exactly this case?
Also, what about #2692? Isn't such scenario (deleting without previous reconciliation) more valuable?

We are already covering this test case:

should able to delete a shoot which was created in previous release [post-upgrade]

This test case addresses the scenario you mentioned (#2692), ensuring that a shoot created in the previous release can be deleted successfully

OK, then you can probably update the PR description with "fixes #2692" so that this issue gets closed when this PR is merged?

Again, even if it's about this, this is all something related to etcd-druid, isn't it? Which role does Gardener play here? It has nothing to do with managing the etcd pods other than deploying the desired state of the Etcd resource. I still think all this belongs to etcd-druid only.

Yes, removed ETCD related test cases.

@rfranzke @timuthy @ScheererJ
The PR is ready for review. I have removed the ETCD-related test cases and updated the PR description.

/test pull-gardener-e2e-kind

/lgtm

/approve

/test pull-gardener-e2e-kind

/test pull-gardener-e2e-kind-operator


pr-pull: skip bottles for CI-syntax-only PRs

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[ ] Have you successfully run brew tests with your changes locally?
[x] Have you successfully run brew man locally and committed any changes?

Don't try to download bottle artifacts when merging PRs labeled as CI-syntax-only. This will allow CI-syntax-only PRs to be automerged.
Before, automerging would usually fail because pr-pull tried to download bottle artifacts that CI never created (see https://github.com/Homebrew/homebrew-core/pull/64740 and the attempted merge for an example).

Nice work, thanks @Rylan12!


getPaywallProducts parsing error

Upgraded to v2.2.0 and I'm unable to fetch products from any of the paywalls I've created.
try {
    const paywall = await adapty.getPaywall(id);
    const products = await adapty.getPaywallProducts(paywall);
    return products;
  } catch (error) {
    console.log(error)
  }

adapty.getPaywallProducts throws this error: [SyntaxError: JSON Parse error: Unexpected identifier "AdaptyProductCoder"]
It's throwing the error when it tries to run tryDecode –>Coder.AdaptyProductCoder.tryDecode(product) on this logic:
var subscriptionPeriodRaw = data['subscription_period'];
if (!subscriptionPeriodRaw) {
    throw this.errRequired('subscriptionPeriod');
}

The product is missing the key subscription_period since it's a paywall for consumable products and not subscription products
How do I go about fixing this? Thanks!

Hey! Looking into it, going to reply in 2 hours

Thank you so much for researching the code! It's seems I have initially missed the optional mark on this field and developed further as considered this required.
I've released v2.2.1, that provides a fix for this issue! @mlaythe

It's late in Europe, but tomorrow I would certainly check that all required fields are validly set
Please, let me know if you consider issue resolved and thanks for migrating to v2 so fast!

Hope the issue is fixed, I'll mark this as resolved. If you find this problem remained, please re-open it


Localization with nuxtjs/i18n not working

Localization with nuxtjs/i18n not working, some or all components don't respond to locale change. UModal doesn't even respond to RTL attribute. I have added a minimum example below to demonstrate the issue
Version
"devDependencies": {
    "@nuxthq/ui": "^2.2.0",
    "@nuxtjs/i18n": "8.0.0-rc.2",
    "@types/node": "^18",
    "nuxt": "^3.5.0"
  }

Reproduction Link
https://stackblitz.com/edit/nuxtlabs-ui-jvruxp
Steps to reproduce
Change the locale in the test playground using dropdown, I have added UVerticalNavigation which won't render translation, same happens with UModal

It is related to i18n and not to this UI library. Function t is not reactive inside ref objects. t is called when you declaring the ref, not in render function of component. This means that example A is equivalent to B:
A:
const links = ref([
  {
    label: t('welcome'),
  },
]);

B:
const links = ref([
  {
    label: 'Welcome',
  },
]);

A possible solution to solve this in Vue is a computed property for t strings so they render again on Locale change.
From this:
const links = ref([
  {
    label: t('welcome'),
  },
]);

To this:
const links = computed(() => {
  return [
  {
    label: t('welcome'),
  },
]

Thanks, it worked, I have created the issue on @nuxt/i18n list

I have same problem.
<NuxtLink :to="localePath('/register')">Register</NuxtLink> // this is working
<UButton :to="localePath('/register')" label="Register" /> // not working


[Bug]QuickShout - str.replace needs /g

Description:
A clear and concise description of what the bug is.
Walkthrough:
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected Behavior:
A clear and concise description of what you expected to happen.
Error Log:

If you are able to, please enable the "Error Log" setting near the bottom of the MAM+ Settings on your preference page.
Navigate to the page that is experiencing the bug
Open your browser's console (How do I open the browser console?).
Screenshot or copy/paste everything that appears in the console and add it here.

This is a code block. If you're pasting text, this would be a good spot to do so.

Technical Details:

OS: [ex. Windows 10, Android 9.0]
Browser: [ex. Chrome 60, Firefox 42]
Userscript: [ex. Tampermonkey, Greasemonkey]

Other:
Add any other context about the problem here.

Thanks @gardenshade for taking care of this. Been swamped with work and family and kept not being able to spend time on personal stuff. Appreciate it. :)

I also just noticed that all the text i put into the body of this Bug didnt show up and reverted back to default bug report contents. I spent more time writing up the bug report than actually fixing the bug and it didnt even show!

Haha, and here I thought it was a power move to say that this tiny little bug wasn't even worth the time to fill out the report xD


multi: update lnd dependency to v0.16.0-beta.rc3

NOTE: currently itests compile with testModeIntegrated and testLargeHttpHeader passing.
One subtest from testModeRemote fails and testFirewallRules also needs changes.

Ah, need to update all Golang versions in the GitHub Actions.


Issue creating WS API through the REST API

I used below request xml in creating WS API through the REST API.
`{
"name": "sample1235656",
"description": "This document describe a RESTFul API for Pizza Shack online pizza delivery store.\r\n",
"context": "/sample1236666",
"version": "1.0.0",
"provider": "admin",
"type": "WS",
"transport":    ["WS"],
"tags": ["pizza"],
"tiers": ["Unlimited"],
"maxTps":    {
"sandbox": 5000,
"production": 1000
},
"visibility": "PUBLIC",
"visibleRoles": [],
"endpointConfig": "{"production_endpoints":{"url":"ws://google.com","config":null,"template_not_supported":false},"sandbox_endpoints":{"url":"ws://google.com","config":null,"template_not_supported":false},"endpoint_type":"http"}",
"endpointSecurity":    {
"username": "user",
"type": "basic",
"password": "pass"
},
"gatewayEnvironments": "Production and Sandbox",
"sequences": [],
"isDefaultVersion":true,
"subscriptionAvailability": null,
"subscriptionAvailableTenants": [],
"businessInformation":    {
"businessOwnerEmail"<EMAIL_ADDRESS>"technicalOwnerEmail"<EMAIL_ADDRESS>"technicalOwner": "John Doe",
"businessOwner": "Jane Roe"
}
}`
There was an error without add transport property. Therefore transport property is made as a mandatory. AFAIK this should not be a mandatory property in WS API.
Without "transport" property I am getting below error.
[2018-06-19 12:21:00,064]  INFO - CarbonAuthenticationUtil<EMAIL_ADDRESS>[-1234]' logged in at [2018-06-19 12:21:00,064+0100] [2018-06-19 12:21:00,078]  INFO - DependencyTracker Sequence : _PRODUCTION_-Asdasa-v1 was  removed from the Synapse configuration successfully [2018-06-19 12:21:00,090]  INFO - DependencyTracker Sequence : _SANDBOX_-Asdasa-v1 was  removed from the Synapse configuration successfully [2018-06-19 12:22:11,525] ERROR - UserAwareAPIProvider Unsupported Transport [] [2018-06-19 12:22:11,526] ERROR - ApisApiServiceImpl Error while adding new API : admin-sample1235656-1.0.0 org.wso2.carbon.apimgt.api.APIManagementException: Error in adding API :sample1235656 	at org.wso2.carbon.apimgt.impl.APIProviderImpl.addAPI(APIProviderImpl.java:714) 	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.addAPI(UserAwareAPIProvider.java:63) 	at org.wso2.carbon.apimgt.rest.api.publisher.impl.ApisApiServiceImpl.apisPost(ApisApiServiceImpl.java:259) 	at org.wso2.carbon.apimgt.rest.api.publisher.ApisApi.apisPost(ApisApi.java:574) 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
With transport with "WS" also giving an error.
[2018-06-19 13:47:03,815] ERROR - UserAwareAPIProvider Unsupported Transport [WS] [2018-06-19 13:47:03,817] ERROR - ApisApiServiceImpl Error while adding new API : admin-sample1235656-1.0.0 org.wso2.carbon.apimgt.api.APIManagementException: Error in adding API :sample1235656
Having transport= http made the successful WS API creation, but this seems to be wrong.

I’m closing this issue because it has been inactive for more than two years. Please reopen if you still encounter this issue with the latest version.


Add support for Central Package Management

The release of NuGet 6.2.0, released with Visual Studio 2022 17.2, makes it possible to manage the versions of package references centrally in a single (or multiple, if one would wish) Directory.Packages.props file.
See Central Package Management (CPM) on Microsoft Docs.
I've been migrating some of our projects to use CPM. Today I tried to migrate our first Sdk="MSBuild.SDK.SystemWeb/4.0.82" project, but I'm getting a NU1008 error:

Projects that use central package version management should not define the version on the PackageReference items but on the PackageVersion items: Microsoft.CodeDom.Providers.DotNetCompilerPlatform;Microsoft.Net.Compilers.Toolset.

I presume MSBuild.SDK.SystemWeb would need to be updated to support this scenario?
Basically, when a Directory.Packages.props file is defined / used, the Version attribute on packages Microsoft.CodeDom.Providers.DotNetCompilerPlatform and Microsoft.Net.Compilers.Toolset should either be removed or be updated to VersionOverride.
Could this be considered for a future, perhaps for the next release?
For the meantime, I could quite easily workaround this issue by setting property ExcludeASPNetCompilers to true:
<PropertyGroup>
  <ExcludeASPNetCompilers>true</ExcludeASPNetCompilers>
</PropertyGroup>

So supporting CPM is by no means an urgent feature request.
Thank you!

I confirm this works, thank you for your support @CZEMacLeod!


feat: update paste_window options to be either a table of function

Options
Type
Description

paste_window.winopts_overrides
fun(paste_winopts: KsbWinOpts): table<string,any>?
Paste float window overrides, see nvim_open_win() for configuration

paste_window.footer_winopts_overrides
fun(footer_winopts: KsbWinOpts, paste_winopts: KsbWinOpts): table<string,any>?
Paste footer window overrides, see nvim_open_win() for configuration

paste_window.highlight_as_normal_win
fun(): boolean?
If function returns true, use Normal highlight group. If false, use NormalFloat

Currently, the overrides winopts_overrides, footer_winopts_overrides, highlight_as_normal_win are required to be a function. Update them to allow either a function or table.

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


Turn png images to code using PaintCode

This bring resolution independence and give the user abilities to tweak images.

Please, can you provide me an explanation?


ECSqlStatement toRow API binding

imodel-native: https://github.com/iTwin/imodel-native/pull/786

Performance Improvements:
@khanaffan @ColinKerr The following table showcases the performance improvements achieved through this change. The measurements were conducted on my local machine by running the test 6-7 times and averaging the results. It's important to note that these numbers can vary slightly due to other applications running on the machine during the tests.

ElementClassName
Element Count
Before (Avg Time in sec)
After (Avg Time in sec)
Improvement

PerfElement2d
10000
3.2661
0.60725
81.31%

PerfElement2d
100000
29.3028
5.90163
79.84%

PerfElement2dSub1
10000
3.8125
0.6822
82.12%

PerfElement2dSub1
100000
37.7555
6.17383
83.65%

PerfElement2dSub2
10000
4.8337
0.68654
85.80%

PerfElement2dSub2
100000
46.6497
6.47896
86.11%

PerfElement2dSub3
10000
6.0925
0.72204
88.15%

PerfElement2dSub3
100000
60.2998
7.46575
87.62%

PerfElement3d
10000
3.3252
0.6332
80.96%

PerfElement3d
100000
32.9899
5.8268
82.34%

PerfElement3dSub1
10000
3.9245
0.638
83.74%

PerfElement3dSub1
100000
38.1947
6.3721
83.32%

PerfElement3dSub2
10000
4.3661
0.6871
84.27%

PerfElement3dSub2
100000
42.4498
6.5449
84.58%

PerfElement3dSub3
10000
5.3051
0.7357
86.13%

PerfElement3dSub3
100000
52.2635
7.1111
86.39%

@akshay05n, please prioritize this PR - you already merged the related native PR and now all addon PRs fail because this one is not merged.

@akshay05n, please prioritize this PR - you already merged the related native PR and now all addon PRs fail because this one is not merged.

I'm currently waiting for the new addon package to be published and integrated into this PR. This should have been completed already. Once integrated, this pull request will be validated and ready to merge.

the native addon / pr was reverted, needs to be re-done and integrated again


python3Packages.pid: remove nose dependency

Description of changes
pid package no longer needs nose as of this commit - remove nose dependency.
(Recreates/fixes #327372)
Addresses https://github.com/NixOS/nixpkgs/issues/326513.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

irrd fails on hydra https://hydra.nixos.org/build/269510337


When set scrollable={true} of , alert error: Two valid but unequal nodes with the same data-reactid

function: _buildMirror()
mirrorRow.appendChild(cells[i].cloneNode(true));
This cloneNode will clone all child elements with 'data-reactid', it will show error:
Uncaught Invariant Violation: ReactMount: Two valid but unequal nodes with the same data-reactid: .<IP_ADDRESS>:<IP_ADDRESS>.0.1:
When thead/tr/th include React Element:

Self

Report wrong repository


how do you attach data?

on the compose page, “Input data:” is empty and there’s no obvious thing to do with it. The tutorial seems to diverge from what I see, at any rate. See screenshot.
This occurs on both Brave and Safari browsers.

the new interface at https://dashboard.stage.wholetale.org looks much clearer :)

the new interface at https://dashboard.stage.wholetale.org looks much clearer :)

Thanks! However, I certainly agree that documentation is severely lacking. We are going to address that.

IMO (as someone who teaches a lot in short course workshops) documentation is
the SECOND resort. A good UI means I don't need to (mentally/computationally)
exit the workspace to hunt for things in the docs!
--t
On Fri, Oct 11, 2019 at 07:33:30AM -0700, Kacper Kowalik wrote:

the new interface at https://dashboard.stage.wholetale.org looks much clearer :)

Thanks! However, I certainly agree that documentation is severely lacking. We are going to address that.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/whole-tale/whole-tale/issues/74#issuecomment-541090021
--
C. Titus Brown<EMAIL_ADDRESS>


Cert tests: Use docker compose instead of docker-compose

Signed-off-by: Bernd Verst<EMAIL_ADDRESS>Description
Cert tests: Use docker compose instead of docker-compose

Is there a reason for this PR? docker-compose can usually be used as alias for docker compose

Is there a reason for this PR? docker-compose can usually be used as alias for docker compose

This is easier for folks to run certification tests if they only have the Docker CLI. Also it is my understanding that docker-compose is discouraged and docker compose should be used.

Is there a reason for this PR? docker-compose can usually be used as alias for docker compose

This is easier for folks to run certification tests if they only have the Docker CLI. Also it is my understanding that docker-compose is discouraged and docker compose should be used.

root:[~]$ docker compose
docker: 'compose' is not a docker command.
See 'docker --help'
root:[~]$ docker-compose
Define and run multi-container applications with Docker.

Usage:
  docker-compose [-f <arg>...] [--profile <name>...] [options] [--] [COMMAND] [ARGS...]
  docker-compose -h|--help

If apply this change, we should document the supported docker version.


Contact page: slack and IRC incorrect?

I was looking at https://www.rabbitmq.com/contact.html and was trying to join the IRC channel, and it says freenode which is dead, have you moved over to Libera.Chat or OFTC or something?
As an alternative I tried to join the Slack, but the linked https://rabbitmq-slack.herokuapp.com/ just gives a blank "application error" page (the end of Heroku free-tier?)
Is there a way these could be updated, and what would be the right info?

I don't know where the IRC channel has moved, if anywhere at all. We can set one up next week.
As for the self-invite app on Heroku, both Slack and that app were set up by someone outside of VMware so we will have to look into how to transfer that account so that it can either use a paid tier or move to a different service.

@swantzter we would be happy to move our IRC to Libera Chat. Do you know how we can get administrative privileges for #rabbitmq there?

@michaelklishin I do! (well I'm biased as Libera Chat staff)
Just drop us an email, with the contents listed at https://libera.chat/chanreg/#project-registration to the address listed at the same place, we'll get back to do a quick verification and then dish out channel control

@swantzter an org registration/claim email deployed! 😄

Identifying myself as the person in an email thread with Libera staff :) libera-5185brjnab15

Slack self-invite app is now back thanks to @gmr who has generously bumped it to a paid Heroku plan.


Bind to specific IP addresses if provided with any

This still only applies to IPv4.
#98
@Tratcher @DamianEdwards @davidfowl

:shipit:


disabling prototype extentions

Disabling of prototype extentions (ref discussion in https://github.com/emberjs/ember-collection/pull/25)

I shouldn't have enabled the array extensions in the first place (Instead I should have checked if we actually needed the observability or not).

wow -- a short film emoticon! Awesome! Brightening my day before my first coffee!


SEP10 v3.0: Add back homeDomain matching constraint for SEP-10 helpers

resolves stellar/go#3176
Updates tests and readChallengeTx function to check for the homeDomain parameter within the first Manage Data op key.

We should hold off merging this until we're ready for it to be released and for people to use it since this repo doesn't use versioning correctly it's easier for some folks to import the last version on master.

We should hold off merging this until we're ready for it to be released and for people to use it since this repo doesn't use versioning correctly it's easier for some folks to import the last version on master.

Sure, I'll let you make that call. That issue not something we want to resolve?

@leighmcculloch
The only failed test I'm getting doesn't seem to be related. The Horizon team just added captive core right?
--- FAIL: TestCaptiveGetLedgerTerminated (0.01s)
    captive_core_backend_test.go:836:
        	Error Trace:	captive_core_backend_test.go:836
        	Error:      	Error message not equal:
        	            	expected: "stellar-core process exited unexpectedly without an error"
        	            	actual  : "stellar-core process not-running"
        	Test:       	TestCaptiveGetLedgerTerminated
FAIL****```

I reran tests and everything passed.


JB-484 - clicking anywhere in the NFTs & Rewards card will take user to NFTs & Rewards tab

What does this PR do and why?
Closes JB-484.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] (if relevant) I have tested this PR in all supported browsers.
[ ] (if relevant) I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #3794

PR #3795

PR #3796

PR #3797

PR #3798

PR #3799

PR #3800

PR #3801

@wraeth-eth started a stack merge that includes this pull request via Graphite.

Graphite rebased this pull request as part of a merge.

@wraeth-eth merged this pull request with Graphite.


Create a new release with last version

Hi @kouinkouin, I see several changes to the master that are not in the release (in particular the Insurance depreciation).
Can you create a new release ?
Thanks a lot,
Olivier.

Bad repo


add support for llama vision model conversion

What does this PR do?
Updated the script to support converting finetuned llama 3.2 vision model to HF format, so it works with multimodal inference.
Feature/Issue validation/testing
Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.
Tested following scripts and it works, without the fix it gives conversion error between llama and mllama config.
python src/llama_recipes/inference/checkpoint_converter_fsdp_hf.py --fsdp_checkpoint_path  /path/to/finetuned/model --consolidated_model_path  /path/to/save/converted/model  --HF_model_path_or_name /home/ubuntu/llama/Llama-3.2-11B-Vision-Instruct/ --multimodal True

python recipes/quickstart/inference/local_inference/multi_modal_infer.py --image_path  /home/ubuntu/chair.jpg --prompt_text "Describe this image" --temperature 0.5 --top_p 0.8 --model_name finetuned_model_mind2web/fine-tuned-meta-llama/hf_model/ --hf_token HF_TOKEN

Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue? Please add a link
to it if that's the case.
[x] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

Thanks for contributing 🎉!

Hi @init27 @tryrobbo , could you help take a look and merge this? I'd like to demo the official llama-receipe repo in a workshop instead of my fork. Thanks!

@roywei Thanks for your PR on this important feature. I will run some tests on your branch now to double check.


async vs sync explanation

Document the motivating reasons behind the async proposal https://github.com/ewasm/design/pull/48

Fixed some typos and linked in to the FAQ.
I think it does a good job at explaining.


capture_span return None, which is not handled correctly

Describe the bug:
I run into an issue, where the KafkaInstrumentation class throws an exception in line 146 of https://github.com/elastic/apm-agent-python/blob/main/elasticapm/instrumentation/packages/kafka.py:
AttributeError: 'NoneType' object has no attribute 'cancel'
this happens when iterating over KafkaConsumer. Indeed, looking at the code, in https://github.com/elastic/apm-agent-python/blob/main/elasticapm/instrumentation/packages/kafka.py, line 132 a context manager is created; the capture_span class calls handle_enter (in https://github.com/elastic/apm-agent-python/blob/main/elasticapm/traces.py, line 1085), which might return None,
but inside of the with block the check (if span) is done only in the subsequent line.
Environment (please complete the following information)

OS: Linux
Python version: 3.9.17
Framework and version [e.g. Django 2.1]: Django 3.2.19
Agent version: 6.15.1

Thanks for reporting and for the analysis.


Wrong coursier cache path under WSL

Issue
I'm using coursier with SBT under a WSL environment. After updating SBT from version 1.3.13 to 1.4.1 coursier is looking at the wrong path for the cache, specifically it's using a windows path, and dependency resolution fails.
At the moment I worked around this by setting COURSIER_CACHE but this was not a problem in 1.3.13
Environment
OS: Windows 10, but running under WSL/Ubuntu 18.04.4 LTS
SBT: 1.4.1 (don't know how to check coursier version)
JVM: Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
Current behaviour
Under WSL, coursier uses a Windows path to resolve the cache:
$ sbt
...
[info] loading project definition from /mnt/c/Users/JamesSmith/Projects/myproject/project
[error] java.nio.file.NoSuchFileException: C:\Users\JamesSmith\AppData\Local\Coursier\cache\v1\https\repo1.maven.org\maven2\com\typesafe\config\1.3.3\config-1.3.3.jar
...
[error] (Compile / bloopGenerate) java.nio.file.NoSuchFileException: C:\Users\JamesSmith\AppData\Local\Coursier\cache\v1\https\repo1.maven.org\maven2\com\typesafe\config\1.3.3\config-1.3.3.jar

Expected behaviour
Coursier should use a WSL path when working inside WSL

Coursier uses directories-jvm to determine the cache directory. Could you report this to dirs-dev/directories-jvm too please?

I've noticed that also SBT 1.4.3 has the same issue

It doesn't look like directories-jvm is the culprit. Cloning the latest version and running the tests gives me this:
UserDirectories (Linux):
  homeDir     = '/mnt/c/Users/ColOfAbRiX'
  audioDir    = '/mnt/c/Users/ColOfAbRiX'
  fontDir     = '/mnt/c/Users/ColOfAbRiX/.local/share/fonts'
  desktopDir  = '/mnt/c/Users/ColOfAbRiX/Desktop'
  documentDir = '/mnt/c/Users/ColOfAbRiX'
  downloadDir = '/mnt/c/Users/ColOfAbRiX'
  pictureDir  = '/mnt/c/Users/ColOfAbRiX'
  publicDir   = '/mnt/c/Users/ColOfAbRiX'
  templateDir = '/mnt/c/Users/ColOfAbRiX'
  videoDir    = '/mnt/c/Users/ColOfAbRiX'

BaseDirectories (Linux):
  homeDir       = '/mnt/c/Users/ColOfAbRiX'
  cacheDir      = '/mnt/c/Users/ColOfAbRiX/.cache'
  configDir     = '/mnt/c/Users/ColOfAbRiX/.config'
  dataDir       = '/mnt/c/Users/ColOfAbRiX/.local/share'
  dataLocalDir  = '/mnt/c/Users/ColOfAbRiX/.local/share'
  executableDir = '/mnt/c/Users/ColOfAbRiX/.local/share/../bin/'
  preferenceDir = '/mnt/c/Users/ColOfAbRiX/.config'
  runtimeDir    = 'null'
ProjectDirectories (Linux):
  projectPath   = 'foobar-app'
  cacheDir      = '/mnt/c/Users/ColOfAbRiX/.cache/foobar-app'
  configDir     = '/mnt/c/Users/ColOfAbRiX/.config/foobar-app'
  dataDir       = '/mnt/c/Users/ColOfAbRiX/.local/share/foobar-app'
  dataLocalDir  = '/mnt/c/Users/ColOfAbRiX/.local/share/foobar-app'
  preferenceDir = '/mnt/c/Users/ColOfAbRiX/.config/foobar-app'
  runtimeDir    = 'null'


⚠ Samsung has degraded performance

In c9cd01d, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2648 ms

Resolved: Samsung performance has improved in d3002ce.


Error loading the view strategy:  Type Error: Cannot read properties of undefined (reading 'domains')

I don't know how to solve that, I'm very new at this, thank you.

https://github.com/AalianKhan/mushroom-strategy/discussions/90

hey i have exactly the same :(

@Thepapy Did you follow the instructions at #90?


SortableGroup error test case

When removing a entity with Sortable extension that has "JOINED" inheritance doctrine fails with PDOException.
This relates to #197 and when running var_dump code snippet by Ryan I've got these results:
Working results (i.e. even if using "SINGLE_TABLE" inheritance):
.string(144) "UPDATE Sortable\Fixture\Transport\Vehicle n SET n.sortByEngine = n.sortByEngine - :delta WHERE n.sortByEngine >= :start AND n.engine = :group__1"
string(141) "UPDATE Vehicle SET sortByEngine = sortByEngine - ? WHERE (sortByEngine >= ? AND engine_id = ?) AND discriminator IN ('vehicle', 'car', 'bus')"

Not working result ("JOINED" inheritance):
string(144) "UPDATE Sortable\Fixture\Transport\Vehicle n SET n.sortByEngine = n.sortByEngine - :delta WHERE     n.sortByEngine >= :start AND n.engine = :group__1"
array(1) { [0]=> string(96) "UPDATE Vehicle SET sortByEngine = sortByEngine - ? WHERE (id) IN (SELECT id FROM Vehicle_id_tmp)" }

As you can see the only real difference is that second query in not working result is wrapped in an array for whatever reason.

great, thanks

hope to fix it next week or so, today theres no time already :)

Haha,I know - thanks for your help - it's deep enough in Doctrine that I can't wrap my mind around how to fix this. I'm looking forward to seeing your patch.


[Bug]: failed to compile while installing from git main branch

🐛 Bug
Compiling move-stackless-bytecode v0.1.0 (C:\Users\ALL.cargo\git\checkouts\move-cd543da0a1ae83ac\725168d\language\move-prover\bytecode)
error: expected one of (, ,, ::, or =, found -
--> language\move-prover\bytecode\src\well_formed_instrumentation.rs:38:26
|
38 | #[allow(clippy::redundant-clone)]
|                          ^ expected one of (, ,, ::, or =
warning: unnecessary parentheses around match arm expression
--> language\move-prover\bytecode\src\access_path.rs:474:55
|
474 |             (Type::Vector(t), Offset::VectorIndex) => (*t.clone()),
|                                                       ^          ^
|
= note: #[warn(unused_parens)] on by default
help: remove these parentheses
|
474 -             (Type::Vector(t), Offset::VectorIndex) => (*t.clone()),
474 +             (Type::Vector(t), Offset::VectorIndex) => *t.clone(),
|
warning: move-stackless-bytecode (lib) generated 1 warning
error: could not compile move-stackless-bytecode (lib) due to previous error; 1 warning emitted
warning: build failed, waiting for other jobs to finish...

I'm experiencing the exact same issue. Here is a screenshot:

This should be easy to fix, so I'll work around it somehow in the meanwhile.

Hi, any update on this?


Add Revision History Appendix

We include all the significant changes from v1.0 to v1.1. Changes are
loosely ordered by "importance", i.e. how likely they are to impact
users / client & server implementations.
Fixes #255

@chrispsommers I don't see any inline comments from you?

@antoninbas Sorry my comments didn't post for some reason. I see you fixed one typo (s/highest/higher) already. See the other one above: s/controller/controllers

@chrispsommers Thanks, I think it may indeed have been because I was doing the edits as you were reviewing.


Could anyone please help me with this issue

Running "flutter pub get" in my_project...
Because no versions of flutter_form_builder match >4.2.0 <5.0.0 and flutter_form_builder 4.2.0 depends on flutter_localizations any from sdk, flutter_form_builder ^4.2.0 requires flutter_localizations any from sdk.
And because every version of flutter_localizations from sdk depends on intl 0.17.0, flutter_form_builder ^4.2.0 requires intl 0.17.0.
So, because my_project depends on both intl ^0.16.1 and flutter_form_builder ^4.2.0, version solving failed.
pub get failed (1; So, because my_project depends on both intl ^0.16.1 and flutter_form_builder ^4.2.0, version solving failed.)
exit code 1
So, I just upgraded my flutter sdk to 2.0.3 and this issue came

this will fix it:
dependency_overrides:
intl: ^0.17.0-nullsafety.2

yeah Thanks It worked


Unknown keywords trigger an IllegalArgumentException

In most parts of parser we throw an InvalidRecurrenceRuleException. In order to stay consistent we should also do so here.
Test: (BYMONHT is unkown)
"FREQ=YEARLY;BYMONHT=2"

Current exception:
java.lang.IllegalArgumentException: No enum constant org.dmfs.rfc5545.recur.RecurrenceRule.Part.BYMONHT

this has been fixed already.


Deprecation warning regarding Module#parent when used with Rails 6.0.0

Environment
Ruby: 2.6.0
Rails: 6.0.0
symmetric_encryption: 4.3.0
Expected Behavior
No deprecation warning.
Actual Behavior
When booting a Rails 6.0.0 app which has symmetric_encryption in the Gemfile, the following warning is shown:
DEPRECATION WARNING: `Module#parent` has been renamed to `module_parent`. `parent` is deprecated and will be removed in Rails 6.1. (called from <module:Core> at /<deleted>/config/application.rb:23)

Running Rails with ActiveSupport::Deprecation.debug = true in application.rb gives a full stacktrace:
/usr/local/var/rbenv/versions/2.6.1/lib/ruby/gems/2.6.0/gems/symmetric-encryption-4.3.0/lib/symmetric_encryption/railtie.rb:32:in `block in <class:Railtie>'
/usr/local/var/rbenv/versions/2.6.1/lib/ruby/gems/2.6.0/gems/activesupport-6.0.0/lib/active_support/lazy_load_hooks.rb:69:in `block in execute_hook'
/usr/local/var/rbenv/versions/2.6.1/lib/ruby/gems/2.6.0/gems/activesupport-6.0.0/lib/active_support/lazy_load_hooks.rb:62:in `with_execution_control'
/usr/local/var/rbenv/versions/2.6.1/lib/ruby/gems/2.6.0/gems/activesupport-6.0.0/lib/active_support/lazy_load_hooks.rb:67:in `execute_hook'
/usr/local/var/rbenv/versions/2.6.1/lib/ruby/gems/2.6.0/gems/activesupport-6.0.0/lib/active_support/lazy_load_hooks.rb:52:in `block in run_load_hooks'
/usr/local/var/rbenv/versions/2.6.1/lib/ruby/gems/2.6.0/gems/activesupport-6.0.0/lib/active_support/lazy_load_hooks.rb:51:in `each'
/usr/local/var/rbenv/versions/2.6.1/lib/ruby/gems/2.6.0/gems/activesupport-6.0.0/lib/active_support/lazy_load_hooks.rb:51:in `run_load_hooks'
/usr/local/var/rbenv/versions/2.6.1/lib/ruby/gems/2.6.0/gems/railties-6.0.0/lib/rails/application.rb:96:in `inherited'
<additional irrelevant lines deleted>

Fixed in https://github.com/rocketjob/symmetric-encryption/pull/134


Allow URL authentication

Context
As an alternative to passing the token via the request header, we want to be able to pass the token via the query parameters.
example: GET /protected?token=XXX
Implementation

The Authenticable#authenticate method now looks for a token param before falling back to the request header.

Notes
This closes #17

Great work! Sorry couldn't get a PR turned around quickly

No worries! Finally found some time to work on this :)

Could this also look for an id_token in the params?
I think that is what Auth0 call the URL param when "signing in as".

I guess it should be possible to configure this. token seems like a reasonable default.

I agree.
auth_token would also make good sense.


multiple criteria fields don't work anymore.

There is a line break in the dlrs record as pictured:

But the trigger seems to break.

Yes this is a bug. The workaround is to set these via the Custom Metadata standard UI. I believe this was reported on the Chatter group, not sure if it found its way here, i'll check.

The custom metadata api is removing the \r from the \r\n delimiter. Having spent some time with various XML escaping i've not been able to work around it. As such i've resorted to modifying the parsing code to support either \r\n or \n. I'll package it soon and get this fix out.

Fixed in v2.2.


Add custom meas_level support to qasm jobs

What is the expected enhancement?
Currently, only meas_level=2 is supported on QASM jobs, but we would like to add level 1 support. @lcapelluto has added level 1 support on the backend, and now the results object needs to be updated so it is fully working

When the circuit model compiles a QuantumCircuit to a QObj it includes a header for each circuit which maps the circuit's classical register index to a respective memory_slot. This is then used upon postprocessing in Qiskit to map the location of the counts to the appropriate classical register. See https://github.com/Qiskit/qiskit-terra/blob/668e57d1d9b624dd08810d2da0d156c41215818d/qiskit/result/counts.py for how this is done.
We wish for backends to support returning measurement level 1 data. Unfortunately, these results are meaningless unless we know which qubits -> classical registers -> memory_slots. A new Memory object could provide this mapping if provided a header in conjunction with some helper methods. A follow-up issue should include a header with the scheduled circuits. This proposed solution may not be the best one and alternatives should be considered.

Resolved by #5452.


Question about evaluation metrics in PushT environment: Fixed episode length and final coverage choice

Question about evaluation metrics in PushT environment: Fixed episode length and final coverage choice
First, thank you for sharing this impressive work and codebase. I have some questions about the evaluation methodology in the PushT environment, specifically regarding the choice of episode length and metrics.
Current Implementation and Results
From the code and my reproduction of experiments using your codebase:
# Fixed episode length implementation
if self.step_idx > 300:
    done = True

# Results from my experimental runs
final coverage max: 0.97899    # Best final state coverage
final coverage mean: 0.54716   # Average final state coverage
max coverage max: 0.97953      # Best achieved coverage
max coverage mean: 0.59142     # Average max coverage achieved

https://github.com/jeffacce/dynamo_ssl/blob/62874039e5d3fc663b0fccd2083b2dd2c8d9935e/envs/pusht.py#L478
Questions

What was the reasoning behind using fixed 300-step episodes with final coverage as the main metric?

I noticed that episodes run for exactly 300 steps, regardless of task completion
The final coverage at this fixed endpoint (mean: 54.7%) is used as the main evaluation metric
I'm curious whether this metric might be sensitive to the arbitrary choice of episode length
This setup might not directly reflect the policy's task completion capability

Would you be willing to share comparison results with other SSL methods using additional metrics?

Results using max coverage-based success rates
Time-to-success measurements (steps to achieve target coverage)
Stability metrics (duration of maintaining high coverage)
Any other performance metrics you might have explored

I'm genuinely interested in understanding the intended evaluation objectives and why this particular setup was chosen over alternatives. Your insights would be very helpful for better understanding the evaluation methodology in manipulation tasks.

Hi @gritYCDA ,
Thanks for your interest in our work!

We use the Push-T environment implementation from VQ-BeT, which evaluates all episodes to 300 steps:
https://github.com/jayLEE0301/vq_bet_official/blob/09d4851288ca5deaaa1ab367a208e520f8ee9a84/examples/pusht_env.py#L478
I believe this is from the original Push-T environment limiting max steps to 300:
https://github.com/real-stanford/diffusion_policy/blob/548a52bbb105518058e27bf34dcf90bf6f73681a/diffusion_policy/config/task/pusht_image.yaml#L25
In our experiments, we observe that final coverage at T=300 and max coverage during the episode are highly correlated. We report the final coverage metric, consistent with the VQ-BeT paper.

We haven't tried the alternative metrics you proposed here, but here are the Push-T runs in the paper with both final and max coverage listed:

Representation
Final Coverage
Max Coverage

Random
0.07
0.18

ImageNet
0.41
0.46

R3M
0.49
0.52

VC 1
0.38
0.44

MVP
0.20
0.28

BYOL
0.23
0.32

BYOL T
0.34
0.42

MoCo v3
0.57
0.60

RPT
0.56
0.58

TCN SV
0.07
0.08

MAE
0.07
0.08

DynaMo
0.66
0.69

If you'd like to run additional experiments with alternative metrics, you can modify this part: https://github.com/jeffacce/dynamo_ssl/blob/62874039e5d3fc663b0fccd2083b2dd2c8d9935e/online_eval.py#L217-L224
Let us know if you have any other questions!
Best,
Jeff


Standardize auth code per CDC specification

User Story:
As a CDC project, I should align with the CDC on the standardization and authorization approach of my applications.
Description/Use Case
Turn RS Auth Code into Building Block
Presently, ReportStream implements the two-legged auth approach specified by FHIR. This part appears to be fine. To increase reusability between CDC projects, for example with ETOR, we will need to break out this code into a reusable library.
Identity Providers:
CDC is looking to standardize their SAMS system to NIST 800-63. SAMS is a sort-of home grown version of Okta whose purpose is to allow external entities to access CDC datasets and probably does not handle server-server auth. SAMS is old and might be undergoing modernization efforts. If it does, CDC may want us to use it instead of Okta.
Boris (Yu Ning) from the CD recommends we take a look at Keycloak (open source identity provider on the come up) for our Identity Provider. Then he suggests using Login.gov for identity proofing, either via
ReportStream -> Keycloak -> SAMS -> Login.gov
or maybe
ReportStream -> Keycloak ->  Login.gov
We should set up a meeting with Boris at some point (include Peter from Flexion) to discuss these options further and compare them to Okta and others.
We currently use Okta which is owned by SimpleReport, not ReportStream. We need Identity management of public keys. We do this in our database right now in settings. Can Okta or something else do this?
Risks/Impacts/Considerations
Dev Notes:
TODO: Create spikes to speak with Boris
Acceptance Criteria

[ ] Auth code broken out into separate library
[ ] Auth architecture/strategy finalized and implemented. How do we do identity management? How do we store keys?

Regarding Keycloak:
I think the two interesting things that stuck out to me while I was glancing through the documentation were:
Resource-based permissions in addition to scoped-based permissions.  We have the latter with our Okta setup, but as we’re moving toward a self-service model, it could be the case that we’d want to have granularity on resource management like Organizations/Senders/Receivers
Impersonation, which could help with service requests if there’s an issue we can’t reproduce as admins.  Not too big of an issue right now because the website isn’t used too frequently, but I could imagine this feature being a huge boon in the future

@arnejduranovic Can you confirm if we can icebox/reassign these issues and epic to another group?

superseded by microservice work


Map one field value to multiple model values

For example, if a JSON API resource had an attribute that was a hash of values, we might want to flatten this into multiple model fields. At the moment the mutators on the adapter do not allow us to do this. Might be worth supporting this feature?

At the moment we have deserializeFooField for a mutator, maybe fillFooField for something that requires conversion for filling? Would receive the model and the value.

Implemented in the new version via the Map field:
https://laraveljsonapi.io/docs/1.0/schemas/attributes.html#map-field


Fixed problem with windows last boot time and multiple timezones

I realised that there was a flaw in the previous logic. createFromFormat() 'O' expects an offset in HHMM format and wmic returns it as minutes.
The code worked fine for +060 (UTC+1 hour/British Summer Time) but when we tried it in New York (+240), this was incorrectly interpreting it as 2 hours 4 minutes rather than UTC-4 hours!

Good catch! Didn't notice this on your latest PR. What version of wmci are you using?

Thanks Márcio
We tested it on some Windows 7 and Server 2012 machines which I don't available to me at the moment.
Just booted a virtual Windows 7 machine here which gives the output of wmic os get version as 6.1.7601. Is this the version number you need?

Thanks. Released as 0.2.0.


Concerns

Dear @lazaronixon ,
thank you very much for this awesome library - i use it as replacement for "devise", and i really (!) like it.
However, i stumbled upon some issues, with respect to maintainability of my own code, when updating your library.
Every time i run rails g authentication --with-some-custom-arguments, my user.rb model is updated (i.e., all my changes are lost). I then need to manually accept / reject changes via console (i.e., to restore my previous functionality and add the required new features).
Therefore, i propose to move everything related to authentication-zero that is now within the User model (within app/models/user.rb) to a dedicated Authenticable concern (within app/models/concerns/authenticable.rb) and just include Authenticable in the User model.
I guess, i could do a PR, if you want - however, you may need to assist me, how to get your project running and tell me how i can test my changes.
All the best and thank you very much for your effort,
Johannes
This is similar to #106

Although I use and recommend concerns, I want this generator to be friendly for beginners and don't introduce a authentication DSL

why can't we have an additional CLI flag to decide if we would like to have a concern or not?
rails g authentication -c or something?

😬 It's too much customization, but to be honest with you, when I use this generator, the first thing I do is create concerns, and I would dislike someone creating them for me.

Dear @lazaronixon ,
i dont really get your answer. I mean - you state that the first thing you do is, to create concerns..
I think, this generator really would benefit from moving everything to (one or more!) concerns.
First, the code would be more structured, it would be easier to update (i.e., everything related to authentication is within one concern, you can add your own business logic directly to the User model, without fear of overwriting something if you re-run the generator), better structure, and so on..
Also, you state that you "would dislike someone creating them for me". But basically that is what your generator does anyway ;) So i don't see an issue with generating the concerns as well ;)
All the best


Updates on blockchain structure documentation

#218

@dmugtasimov Please take a look why this fails, probably I am exceeding some char limit in a line or something?

@led76marx please, squash commits. Please, also take care about failing tests (your changes broke them). It is OK if you do not want or can't do it. I can manually bring you changes in the codebase. Just let me know.


Document potential AV software issues

Or give user a message that AV software may be affecting logger.
These symptoms strongly remind me of some overly aggressive antivirus software – some of them will watch the file system, and as soon as a new file appears, will open it for exclusive access to run a scan on it. If the application does rapid open/write/close cycles on the same file (as is the case with plots when you resize one, I believe), it may try to open the file for the second time while AV is still running the scan. This has been a major source of problems for VS in general historically.

Also applies to plots. Really, applies to anything that can potentially write a file to disk, close it, and then open it very shortly afterwards.
For what it's worth, VS itself has suffered from similar issues (often breaks F5, because the newly built .exe cannot be copied from obj to bin), and ended up just doc'ing it. So at this point there's already an established understanding that dev tools do require disabling (or at least dialing down, via exclusions) your antivirus.

Since this affects many areas, we can't really fix it completely. We'll doc it then as VS did.

Over to https://github.com/Microsoft/RTVS-docs/issues/51


Can't load Hass.io Panel

Hello.
Hass.io v 0.72.
Hass.io panel don't load. Even on latest chrome
Not working on Safari on Mac and IOS
Chrome on Mac and IOS
FF same
Not load on iPhone app.

/move home-assistant/home-assistant-polymer


Running into an error with both the interactive and non-interactive viewer

❓ Questions and Help
Device Specifications
OS: Ubuntu 18.04
GPU: NVIDIA Geforce 1050ti, Driver Version: 390.129
CUDA 9.0
Steps to reproduce the error

Followed the instructions detailed in the README using the python setup.py install --with-cuda to build in a virtual environment

To test the interactive viewer I ran the command ./build/viewer /path/to/data/scene_datasets/habitat-test-scenes/skokloster-castle.glb which resulted in this error message:
Platform: can't get Xft.dpi property for virtual DPI scaling, falling back to physical DPI
GLX: GLX extension not found
Platform::GlfwApplication::tryCreate(): cannot create a window with core OpenGL context, falling back to compatibility context
GLX: No GLXFBConfigs returned
GLX: Failed to find a suitable GLXFBConfig
Platform::GlfwApplication::tryCreate(): cannot create a window with OpenGL context

Tried to test the non-interactive viewer as well by running the command python examples/example.py --scene /path/to/data/scene_datasets/habitat-test-scenes/skokloster-castle.glb  which resulted in this error message:
sim_cfg.physics_config_file = ./data/default.phys_scene_config.json
Initialized Sensor Spec:
Sensor uuid:  color_sensor
Sensor type:  SensorType.COLOR
Sensor position:  [0.  1.5 0. ]
Platform::WindowlessGlxContext: no supported framebuffer configuration found
WARNING: Logging before InitGoogleLogging() is written to STDERR
F0108 21:38:01.951243 15016 WindowlessContext.cpp:201] Check failed: glxCtx_.isCreated() [GLX] Failed to created headless glX context
*** Check failure stack trace: ***
[1]    15016 abort (core dumped)  python examples/example.py --scene

Other notes
Issue #32 seemed to be facing a similar problem, however, I am not employing any port forwarding in my case and am testing this out on a local machine. I have not opened 2 separate issues since I feel they are related to each other however I may be wrong in assuming this.
Any help would be greatly appreciated :)

Assuming your compute does have an attached display, then non headless mode should work.  What does echo $DISPLAY return?  It should almost certainly be set :0

Yeah, it does return :0

Not sure what is going on then, you can try building with --headless.  The viewer won't work, but everything else should.

One other idea:  Maybe you are using Wayland not X11, what does echo $XDG_SESSION_TYPE show?

Huh this is pretty weird, it doesn't return anything. It just outputs a blank space.
Running env | grep XDG_ returns the following:
XDG_SEAT=seat0
XDG_SESSION_ID=3
XDG_CURRENT_DESKTOP=KDE
XDG_RUNTIME_DIR=/run/user/1000
XDG_DATA_DIRS=/usr/share:/usr/share:/usr/local/share
XDG_VTNR=1
This does seem abnormal

A bit more context:
While booting into Ubuntu, I manually start the xorg server (exec startx). This was made necessary since I was running into an endless login loop when I first installed Ubuntu on my system.

@wannabeOG you can also check a step by step installation on a fresh Ubuntu in our CI setup and find missing pieces or repeat steps yourself. Ignore Javascript, emscripten, chrome and other unrelated dependencies.


Fix ChangeLoggingTimestampedWindowBytesStore

Pass bool retainDuplicates parameter into ChangeLoggingTimestampedWindowBytesStore
Because UpdateSeqnumForDups() in this class require retainDuplicates parameter

Simple re-check:

Create simple join-processor: LEFT with RIGHT topics with 1 key ("key-1") into DESTINATION topic
Add 5 messages into LEFT topic
Wait Kafka to process into *-STORE-CHANGE-LOG topic
Delete StateDir with change logs
Start join-processor
Add 1 message to RIGHT topic
FIND AN EXCEPTION: in DESTINATION we required to see 5 messages, but we can see only one

@charleyskills
Thanks for your contribution, I will check asap

so... @LGouellec, can you merge my PR ?

@LGouellec and... when new version will build?

I plan June or July

I plan June or July

Hi ;)


chore: prepare release v0.80.0-sumo-1

Release Windows packaging fixes and native packages for macOS.

LGTM! 👍


feat: v6.0 proposal migration

Description

we still need to update the emergency group address

@robert-zaremba  @toteki  Instead of upgradev6 , we can follow this folder struct
- app
 - upgrades
   - v6
   - v3


There is an error in the last update

From the screenshot, it looks like you compiled this yourself.  Which commit did you compile?  What CMake options did you use?  You might be missing a Microsoft Visual C Redistributable.

ا
The problem of switching from dev to version v0.17.1 has been solved


Out of memory - script killed

I want to upscale a video HD in 4K.
I exported the video to a png sequence and create sub-images to avoid  CUDA ERROR: Out of memory (V100 with 16 Go).
But with 7000 png in a folders, the script is killed at
imgs_LQ = data_util.read_img_seq(test_dataset_folder)
Any idea to avoid it ?

With only 100 images, it works...

How did you export to PNG and recompile the video in an effective way?


[Enhancement] Zero-copy DAG_CBOR into Vec parser.

Summary of changes

Changes introduced in this pull request:

Introduced a deserializer to speed up CBOR > Vec parsing.

Reference issue to close (if applicable)

Closes
Other information and links

Change checklist

[ ] I have performed a self-review of my own code,
[ ] I have made corresponding changes to the documentation,
[ ] I have added tests that prove my fix is effective or that my feature works (if possible),
[ ] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

I'm confused - the title says zero-copy serialization of Vec<Cid>, but I'd expect to see a lifetime in that case, deserializing into a &'serial [Cid] or something.
Plus, the in-memory representation of a CID is different to the CBOR serialization, so I'd expect to see a new struct, but I don't - what am I missing?

The title does not say anything about serialization whatsoever. It's deserialization of a CBOR-encoded blob into a Vec<Cid>.

We are recursively traversing the DAB_CBOR-encoded blob without parsing everything into a recursive Ipld struct.
All the results are saved into a Vec<Cid>.
That yields 3x performance boost over normal parsing.

I'm confused - the title says zero-copy serialization of Vec<Cid>, but I'd expect to see a lifetime in that case, deserializing into a &'serial [Cid] or something.
Plus, the in-memory representation of a CID is different to the CBOR serialization, so I'd expect to see a new struct, but I don't - what am I missing?

The CIDs are copied (which can be done without any heap allocations.) Other data, such as bytes and strings, are not copied.

Yeah, zero-copy here is a bit misleading, I'll make sure this is documented properly.

I'm confused - the title says zero-copy serialization of Vec<Cid>, but I'd expect to see a lifetime in that case, deserializing into a &'serial [Cid] or something.
Plus, the in-memory representation of a CID is different to the CBOR serialization, so I'd expect to see a new struct, but I don't - what am I missing?

The CIDs are copied (which can be done without any heap allocations.) Other data, such as bytes and strings, are not copied.

Yeah, zero-copy here is a bit misleading, I'll make sure this is documented properly.

I don't think it's inaccurate to call this a zero-copy parser. The PR is doing two things: a) parsing an ipld structure, b) extracting CIDs from Link branches. The parsing part is definitely zero-copy. It's not a generalized zero-copy Ipld parser, though.

Ahh I understand now!

The CIDs are copied (which can be done without any heap allocations.) Other data, such as bytes and strings, are not copied.
We are recursively traversing the DAG_CBOR-encoded blob without parsing everything into a recursive Ipld struct.
The PR is doing two things: a) parsing an ipld structure, b) extracting CIDs from Link branches. The parsing part is definitely zero-copy. It's not a generalized zero-copy Ipld parser, though.

Zero-copy in my head means holding references into buffers. Copying CIDs out of it is not zero copy ;)
I think (pre?) filtered deserialization could be a better term here?

Ahh I understand now!

The CIDs are copied (which can be done without any heap allocations.) Other data, such as bytes and strings, are not copied.
We are recursively traversing the DAG_CBOR-encoded blob without parsing everything into a recursive Ipld struct.
The PR is doing two things: a) parsing an ipld structure, b) extracting CIDs from Link branches. The parsing part is definitely zero-copy. It's not a generalized zero-copy Ipld parser, though.

Zero-copy in my head means holding references into buffers. Copying CIDs out of it is not zero copy ;)

Imagine a zero-copy parser that returns an Ipld structure with references instead of owned data. Then imagine traversing that structure to extract the CIDs. This PR does both at once, with the intermediate structure deforested out.

Is this feature covered by unit tests?

Good point, it actually isn't.


G*.pth checkpoints do not match the RVC v2 models

Hi there,
I'm trying to load a G*.pth checkpoint to load my net_g model using:
'''
utils.load_checkpoint(
utils.latest_checkpoint_path(hps.model_dir, "G_*.pth"), net_g, optim_g
)
'''
I get the following error:
INFO:root:enc_p.emb_pitch.weight is not in the checkpoint
INFO:root:dec.m_source.l_linear.weight is not in the checkpoint
INFO:root:dec.m_source.l_linear.bias is not in the checkpoint
INFO:root:dec.noise_convs.0.weight is not in the checkpoint
INFO:root:dec.noise_convs.0.bias is not in the checkpoint
INFO:root:dec.noise_convs.1.weight is not in the checkpoint
INFO:root:dec.noise_convs.1.bias is not in the checkpoint
INFO:root:dec.noise_convs.2.weight is not in the checkpoint
INFO:root:dec.noise_convs.2.bias is not in the checkpoint
INFO:root:dec.noise_convs.3.weight is not in the checkpoint
INFO:root:dec.noise_convs.3.bias is not in the checkpoint
INFO:root:dec.noise_convs.4.weight is not in the checkpoint
INFO:root:dec.noise_convs.4.bias is not in the checkpoint
INFO:root:dec.ups.4.bias is not in the checkpoint
INFO:root:dec.ups.4.weight_g is not in the checkpoint
INFO:root:dec.ups.4.weight_v is not in the checkpoint
INFO:root:dec.resblocks.12.convs1.0.bias is not in the checkpoint
INFO:root:dec.resblocks.12.convs1.0.weight_g is not in the checkpoint
INFO:root:dec.resblocks.12.convs1.0.weight_v is not in the checkpoint
INFO:root:dec.resblocks.12.convs1.1.bias is not in the checkpoint
INFO:root:dec.resblocks.12.convs1.1.weight_g is not in the checkpoint
INFO:root:dec.resblocks.12.convs1.1.weight_v is not in the checkpoint
INFO:root:dec.resblocks.12.convs1.2.bias is not in the checkpoint
INFO:root:dec.resblocks.12.convs1.2.weight_g is not in the checkpoint
INFO:root:dec.resblocks.12.convs1.2.weight_v is not in the checkpoint
INFO:root:dec.resblocks.12.convs2.0.bias is not in the checkpoint
INFO:root:dec.resblocks.12.convs2.0.weight_g is not in the checkpoint
INFO:root:dec.resblocks.12.convs2.0.weight_v is not in the checkpoint
INFO:root:dec.resblocks.12.convs2.1.bias is not in the checkpoint
INFO:root:dec.resblocks.12.convs2.1.weight_g is not in the checkpoint
INFO:root:dec.resblocks.12.convs2.1.weight_v is not in the checkpoint
INFO:root:dec.resblocks.12.convs2.2.bias is not in the checkpoint
INFO:root:dec.resblocks.12.convs2.2.weight_g is not in the checkpoint
INFO:root:dec.resblocks.12.convs2.2.weight_v is not in the checkpoint
INFO:root:dec.resblocks.13.convs1.0.bias is not in the checkpoint
INFO:root:dec.resblocks.13.convs1.0.weight_g is not in the checkpoint
INFO:root:dec.resblocks.13.convs1.0.weight_v is not in the checkpoint
INFO:root:dec.resblocks.13.convs1.1.bias is not in the checkpoint
INFO:root:dec.resblocks.13.convs1.1.weight_g is not in the checkpoint
INFO:root:dec.resblocks.13.convs1.1.weight_v is not in the checkpoint
INFO:root:dec.resblocks.13.convs1.2.bias is not in the checkpoint
INFO:root:dec.resblocks.13.convs1.2.weight_g is not in the checkpoint
INFO:root:dec.resblocks.13.convs1.2.weight_v is not in the checkpoint
INFO:root:dec.resblocks.13.convs2.0.bias is not in the checkpoint
INFO:root:dec.resblocks.13.convs2.0.weight_g is not in the checkpoint
INFO:root:dec.resblocks.13.convs2.0.weight_v is not in the checkpoint
INFO:root:dec.resblocks.13.convs2.1.bias is not in the checkpoint
INFO:root:dec.resblocks.13.convs2.1.weight_g is not in the checkpoint
INFO:root:dec.resblocks.13.convs2.1.weight_v is not in the checkpoint
INFO:root:dec.resblocks.13.convs2.2.bias is not in the checkpoint
INFO:root:dec.resblocks.13.convs2.2.weight_g is not in the checkpoint
INFO:root:dec.resblocks.13.convs2.2.weight_v is not in the checkpoint
INFO:root:dec.resblocks.14.convs1.0.bias is not in the checkpoint
INFO:root:dec.resblocks.14.convs1.0.weight_g is not in the checkpoint
INFO:root:dec.resblocks.14.convs1.0.weight_v is not in the checkpoint
INFO:root:dec.resblocks.14.convs1.1.bias is not in the checkpoint
INFO:root:dec.resblocks.14.convs1.1.weight_g is not in the checkpoint
INFO:root:dec.resblocks.14.convs1.1.weight_v is not in the checkpoint
INFO:root:dec.resblocks.14.convs1.2.bias is not in the checkpoint
INFO:root:dec.resblocks.14.convs1.2.weight_g is not in the checkpoint
INFO:root:dec.resblocks.14.convs1.2.weight_v is not in the checkpoint
INFO:root:dec.resblocks.14.convs2.0.bias is not in the checkpoint
INFO:root:dec.resblocks.14.convs2.0.weight_g is not in the checkpoint
INFO:root:dec.resblocks.14.convs2.0.weight_v is not in the checkpoint
INFO:root:dec.resblocks.14.convs2.1.bias is not in the checkpoint
INFO:root:dec.resblocks.14.convs2.1.weight_g is not in the checkpoint
INFO:root:dec.resblocks.14.convs2.1.weight_v is not in the checkpoint
INFO:root:dec.resblocks.14.convs2.2.bias is not in the checkpoint
INFO:root:dec.resblocks.14.convs2.2.weight_g is not in the checkpoint
INFO:root:dec.resblocks.14.convs2.2.weight_v is not in the checkpoint
shape-dec.conv_post.weight-mismatch|need-torch.Size([1, 16, 7])|get-torch.Size([1, 32, 7])
INFO:root:dec.conv_post.weight is not in the checkpoint
INFO:root:Loaded model weights
Do you know what the cause of the issue is?

You shouldn't modify the sample rate during training. It's caused by sample rate modifying when continuing training.


Upgrade Router

This.
Looks.
INCREDIBLE!!!!

Gaa, forgot some changes for the new router. Rebase coming in h0t.


Invalid json test cases + strings validation

Summary of the Pull Request

Added unit test for invalid jsons
Added validation for guid and device id string to prevent possible errors on parsing step.

PR Checklist

[x] Applies to #1459

Rerunning CI

Let's not rerun CI until the current master is proven to work and the PRs are rebased on master.


Update common-policies.md

Added an end of line regex symbol $ to the TLD example in order to block:
domain.fail

but avoid unintended blocks like:
domain.fail.com

The regex for catching unintended blocks was implemented here.

في الثلاثاء، ١٨ يوليو ٢٠٢٣ ٧:٠٥ م Max Phillips @.***>
كتب:

Closed #9073 https://github.com/cloudflare/cloudflare-docs/pull/9073.
—
Reply to this email directly, view it on GitHub
https://github.com/cloudflare/cloudflare-docs/pull/9073#event-9852440115,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWV6NCQXPQTIKZIAXZ5P4ZTXQ2X5VANCNFSM6AAAAAAYNLNMF4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>


I am trying to use multi retreival QA chain but not sure what version of langchain will be best?

Issue you'd like to raise.
I am trying to develop a chatbot that can give answers from multiple namespace.That why I am try to use the MULTIRETREIVALQA chain but the langchain versions seems to be making some issues for me . Any suggestions?
Suggestion:
No response

Are you referring to vector databases like Pinecone? Also, please share the error messages you are getting so I can help out :+1:

Yes I am referring pinecone database.There are issue with chatvectordbqa chain and importing of different modules

What modules are you trying to import?

I am trying to use the fromLLMAndRetriever from the MultiRetrievalQAChain but cannot use it any help with that?

I have the same problem...
Error:
Type 'VectorStoreRetriever' is missing the following properties from type 'VectorStoreRetriever': lc_namespace, searchType, _vectorstoreType, _getRelevantDocuments, and 20 more
how to you finally fix this?

I have the same problem... Error: Type 'VectorStoreRetriever' is missing the following properties from type 'VectorStoreRetriever': lc_namespace, searchType, _vectorstoreType, _getRelevantDocuments, and 20 more
how to you finally fix this?

import { PineconeStore } from 'langchain/vectorstores/pinecone';
you can create a custom chain and add the following code to that
vectorstore: pineconStore
and  simply when returning the instance of the chain add this
const retriever=vectorstore.asRetriever();


Add OpenMP support for widget rendering

Is your feature request related to a problem? Please describe.
https://github.com/lc-soft/LCUI/blob/4a9516e8eb3bc23b681575653ac31468093d8a2c/src/display.c#L151-L172
Describe the solution you'd like
Dirty rectangle repaint tasks can be assigned to multiple CPU cores to improve rendering performance.
Describe alternatives you've considered
None.
Additional context
https://en.wikipedia.org/wiki/OpenMP

IssueHunt Summary

Backers (Total: $20.00)

 lc-soft ($20.00)

Become a backer now!
Or submit a pull request to get the deposits!
Tips

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on IssueHunt to raise funds.

IssueHunt has been backed by the following sponsors. Become a sponsor

I would like to work on this issue.


Dependency Bot: Trigger CI Tests

Github action workflows have a limitation where workflows cannot trigger other workflows. In this case our dependency bot putting up a PR cannot trigger our CI tests. To get around this we need to provide a personal access token instead of using the repo token.  Here is an example: https://docs.github.com/en/actions/reference/events-that-trigger-workflows#triggering-new-workflows-using-a-personal-access-token

@jeremyliweishih I can provide you with a personal access token


✨[feature Request]: Improve the UI of Home Page

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
In the front of home page the picture and sign up section is not properly fixed. Through which website not looks good.
I can improve it.
@Anjaliavv51  Kindly assign me the issue under the label of gssoc-ext, hacktoberfest'24, hacktoberfest-accepted, level-2.
Use Case
I would like to enhance the UI of Home Page.
Benefits
The Home page looks good, Sign up section will also looks good.
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24EXTD contributor
[X] I have starred the repository

@Anjaliavv51 Kindly assign me the issue under the label of gssoc-ext, hacktoberfest'24, hacktoberfest-accepted, level-2.


warnings in aot build.

After the inital project setup. Multiple warnings are shown when a aot build is done .
Steps:

npm run build:aot

Output
WARNING in ./src/app/app.component.ngfactory.js
(Emitted value instead of an instance of Error) Cannot open SourceMap
'.../src/app/app.component.ngfactory.js.map':
Error: ENOENT: no such file or directory, ...src/app/app.component.ngfactory.js.map'

I've disabled sourcemaps in aot, not quite sure what causes it...but will take a pull requesst


Update aws-java-sdk-core to 1.12.345

Updates com.amazonaws:aws-java-sdk-core from 1.12.344 to 1.12.345.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #322.


Unstable container

I've used Pi Gallery 2 for a week or to, but my Docker-host crashed two times, and become unavailable. CPU load was stuck at 100%, and i couldn't get in contact with the machine by SSH.
I rebooted it, and everything was good.
After two days, the same thing happened again.
This was my docker-compose file:
pigallery2:
  image: bpatrik/pigallery2:nightly-stretch
  container_name: pigallery2
  environment:
    - NODE_ENV=production
  volumes:
    - ./pigallery2/config:/app/data/config
    - /home/USERNAME/pigallery2/db:/app/data/db
    - /media/pictures:/app/data/images
    - ./pigallery2/tmp:/app/data/tmp
  ports:
    - "CUSTOMPORT:80"
  restart: unless-stopped

After that, i removed the container - and everything has been stable hereafter.
Am I the only one, with that issue?
I would like to dump more details and so, however, with all the crashed, i can't get it back up, before i have a few days here within my Home-network, cause everything becomes unavailable, at the time, of the CPU is going to 100%.
I did setup some logging for the docker containers too, but at the time of the Pi Gallery 2 is starting to cook my CPU, the logging is stuck - and no useful information is logged.
My docker software is not the newest (Docker version 18.03.0-ce, build 0520e24), but EVERYTHING ELSE works just fine, with no issues, what so ever :-)

Hi,
Thanks for the report.
Can you confirm that you were not accidentally running any build in background job? (Like clicking on the transcode videos, create thumbnails, etc.. button)
You can also try going to advanced settings mode and check if there anything running at the jobs panel. (technically it is possible that you don't have a job like indexing listed at the panel, but it is still running in the background, but only you set it up)
If everything it alright than it should use too much resources. I'll try to keep an eye on my instance.
In the meantime, you can try running it with:
command:
 --Server-Log-level=6

This will enable more detailed logging.

Hi bpatrik.
First, i'm sorry for the late reply!
It's actually a good question - cause i did start the transcode of every video-file. However, it happend two times, as mentioned - and the 2nd time, i had disabled the "video"-feature.
But one thing; Kindly note that i'm unable to access everything on the VM, where the docker-container is hosted, so i can't log in, and check for jobs and so, "while" it's toasting my server :-D
I could enable the logs, and test it once more, but, do you think, it will give us the proper amount of details?
(And oh, btw, my server has been rock stable again, after i stopped the container with PiGallery2, to it must be a problem with that)

Hi,
I'm running the app (with nightly-alpine image) on my raspberry pi 3 B for days by now and I do not see any odd behavior.
I suspect that there might be running some job in the background.
To make sure noghting runs, empty the jobs in the config.json:
....
    Jobs: {
      maxSavedProgress: 10,
      scheduled: []
   }
...

And restart the app. (And do not click after that on any green running button (like: 'convert video' 'index db now', etc..) :) )
Note: If you started the video converting. Disabling the video support, wont stop the video converting, just hide it from the  UI (I might fix it once). Plus if you canceled video converting, It wont stop until that current video in progress is converted. (So canceling means, no further video conversion, but not immediate stopping)
Also how high is the traffic on the app? I'm mostly using it with 1-2 parallel users.
Thumbnail and photo (down scale for faster laod) generation happens on the fly. If your users are different folders, that was not opened before, that adds also extra load.
A way to avoid that to index the whole folder and generate all thumbnail, photo at once with the jobs.
This is my pipeline:

Once the indexing is done, it also creates all thumbnail, photo etc.
You can also schedule it to run every night at 2am or so.

Limiting runtime resources is also an option https://docs.docker.com/config/containers/resource_constraints/

Yes. But it's just a ugly hack - but maybe it's usefull to find out what's
going on within the container, at the time, there the issue is present :-)
I'll start my container again today, and see hos it goes.
søn. 12. jan. 2020 22.41 skrev Suika<EMAIL_ADDRESS>
Limiting runtime resources is also an option
https://docs.docker.com/config/containers/resource_constraints/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bpatrik/pigallery2/issues/122?email_source=notifications&email_token=AA3CSBPF4GWNCEPSKESEFR3Q5OFA3A5CNFSM4KD4OGR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIXE74Q#issuecomment-573460466,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA3CSBMOAE7KFY3XOY3U2Q3Q5OFA3ANCNFSM4KD4OGRQ
.

And, the whole VM was unavailable again, not more than 24 hours after i enabled the PiGallery2-container again.
So, now i've defined a resourcelimit, and i'll check how that goes:
    deploy:
      resources:
        limits:
          cpus: '0.50'
          memory: 50M
        reservations:
          cpus: '0.25'
          memory: 20M

And oh, btw - there's MANY scheduled things in my config-file:
"scheduled": [
                {
                    "name": "Indexing",
                    "jobName": "Indexing",
                    "config": {},
                    "trigger": {
                        "type": 1
                    }
                },
                {
                    "name": "Thumbnail Generation",
                    "jobName": "Thumbnail Generation",
                    "config": {
                        "sizes": [
                            160
                        ]
                    },
                    "trigger": {
                        "type": 4,
                        "afterScheduleName": "Indexing"
                    }
                },
                {
                    "name": "Photo Converting",
                    "jobName": "Photo Converting",
                    "config": {},
                    "trigger": {
                        "type": 4,
                        "afterScheduleName": "Thumbnail Generation"
                    }
                },
                {
                    "name": "Video Converting",
                    "jobName": "Video Converting",
                    "config": {},
                    "trigger": {
                        "type": 4,
                        "afterScheduleName": "Photo Converting"
                    }
                },
                {
                    "name": "Temp Folder Cleaning",
                    "jobName": "Temp Folder Cleaning",
                    "config": {},
                    "trigger": {
                        "type": 4,
                        "afterScheduleName": "Video Converting"
                    }
                }
            ]

That config file is normal (those are the default settings. Those settings do not start any job/task, just set up a pipline that is easy to configure. And also you can delete them by settings the scheduled property to an empty array [])
Setting a resource limit does not solve the issue, but maybe you will have access to your server at least. Seeing some docker logs would be nice.
Btw can you access it through the web when it is running at 100% CPU?
There are actually 3 differences between your docker-compose and my one:

I'm using the alpine build (should not matter)
I restart: always (docker might restart the instance if it is not responding)
for the db, I'm using named volumes instead of a mounted filesystem path (should not matter)

I changed the restart procedure to restart: unless-stopped to see if that matters.
btw I was using the app on RPi2, now on RPI3 since 2016 (without docker) and I never had this 100% CPU issue.  So it is very interesting in your case :)

It just happend again - and the VM sadly become unavailable.
It's so wierd..

I don't really have the time to debug, it i need to try everything to get it working. I started using PiGallery2, case i really like it simple - and it's using the file-path, and not requesting me to import anything. (Our pictures is sorted in folders)
Also, i would not like to just go with restart:always, cause restart: unless-stopped should be good enough :-)
I've removed it again. The same VM are hosting Home Assistant, and my girlfriend shouldn't even control our lights this morning :-)
My Docker-instance is not that new anymore (18.03), but it's not a problem for other containers, so i don't really know what to do.
But's it's clear that something within that container, are getting the host to just to almost 100% - and hereafter, become unavailable.
Damn :D

I'm sorry to hear that. :/
I'll let you know if I came across this issue and find a solution to it.
You can look around at these places for an alternative:
https://github.com/awesome-selfhosted/awesome-selfhosted
https://www.reddit.com/r/selfhosted/search/?q=photo&restrict_sr=1
I see Piwigo, Lychee the most on these forums.

Also is you image only about the pigallery2 container?
Because the CPU load should be ~0% if you using (=browsing) the app.

I'll just follow up.
I've no problem, since i removed PiGallery2. Not a single crash of my VM, or anything, like that. The load is normal, and so.
So something must be wrong. But i can't say if it's related to how my images was accessed, or so. My images is located on another instance, and data was mounted by NFS, which i'm also using for other files, with much more regular (and power demanded) load.
Overall i'm still not sure about what's triggering this, but i can't have yet anther day, where the VM arn't working :-)

Hi,
thanks for following up. Unfortunately I could not reproduce this and no one else reported anything like this, so I do not really have a clue about this issue.