Parsing error if decorators are applied to methods with computed properties

If decorator is applied to the method with computed property key, eslint throws parse error. Is this the correct behavior?
  @autobind
  [method](arg) {
      // do something
  }

Eslint throws error on the first {, saying :  Parsing error: Unexpected token.
Latest eslint and babel-eslint

This would require a change to babylon to fix the Unexpected token issue if this is valid

Borken for me as well with latest 6.0.4 version. Any updates?

It's not broken, it has never been supported. This is what @hzoo is trying to say above. We should close this and open an issue in Babylon, the parser Babel uses.

Created an issue in bablylon repo: https://github.com/babel/babylon/issues/33. Closing this one. Thank you, guys!


npe2 doc feedback

📚 Documentation
This is a collation of issues reported in this zulip thread
npe2 getting started guide

[x] cookiecutter should generate reader for *.npy files but doesn't

npe2 migration guide

[ ] migration guide refers to _hookimpls:AnimationWidget in one place and _qt.AnimationWidget in another.
[ ] using builtins in examples is confusing
[ ] not clear: what happens when a plugin has both napari-plugin-engine bindings and npe2 bindings.
[ ] need examples with multiple kinds of contributions.
[ ] surprising: commands, readers, writers at same level in hierarchy

Thanks for opening this issue regarding my comments. I just wanted to mention that I opened an issue regarding the very first point directly on the cookiecutter-napari-plugin repo (https://github.com/napari/cookiecutter-napari-plugin/issues/73).

I opened an issue regarding the very first point directly on the cookiecutter-napari-plugin repo

thanks!

@tlambert03 has done some significant improvements to the plugin docs in napari#3916. Linking it here since it addresses some of this feedback.

@nclack looks like these items are all addressed for npe2 doc? Are there still outstanding ones you'd like to track, or should we close this issue?


Investigate Kubernetes Monitoring Alertmanager Time Zone setting

Investigate Kubernetes Monitoring Alertmanager TimeZone setting and pair triggered alerts with appropriate logs.
e.g.:

Alert arrives at 8:03 AM CET

Container detail view

and  Logs explorer

shows 9:03 AM CET

Consider that alert manager waits 5min before sending a notification about new alerts.

Timezones inside cluster (Alertmanager, Prometheus..) are consistently set to UTC.
Time in mattermost and grafana is set to browser time.
In example above is alert probably paired with wrong log. (can't investigate further, because logs have been already deleted)

Timezones inside cluster (Alertmanager, Prometheus..) are consistently set to UTC.
Time in mattermost and grafana is set to browser time.
In example above is alert probably paired with wrong log. (can't investigate further, because logs have been already deleted)

Investigating same error etcdHighNumberOfFailedGRPCRequests on 01-20-2021:
1.Alerts arrived at 13:32 and 13:55 CET

Count of logs for etcd container in range 12:00 - 15:00 CET

Errors and therefore increased amount of logs occured at the same time (+- delay of alertmanager) as alerts came.

Small part of logs from etcd during duration of second error:

Conclusion:
Alerts and and appropriate logs timezone matches.

Investigating same error etcdHighNumberOfFailedGRPCRequests on 01-20-2021:
1.Alerts arrived at 13:32 and 13:55 CET

Count of logs for etcd container in range 12:00 - 15:00 CET

Errors and therefore increased amount of logs occured at the same time (+- delay of alertmanager) as alerts came.

Small part of logs from etcd during duration of second error:

Conclusion:
Alerts and and appropriate logs timezone matches.


About blacklisting

In general terms this library looks like instantclick but more lightweight, so that's good!
I thin that blacklisting links can be improved:

data-no-pageAccelerator instead of data-pageAccelerator="false". Or something similar. Less characters, more semantic.
Add ability to blacklisting a group of elements. For example, in instantclick:

To blacklist all links in a parent element, add data-no-instant to that element.

Being able to disable pageAccelerator via something passed to the function would be fantastic as well. I'm trying to figure out how to exclude the WordPress admin bar from being accelerated, and I think I may just need to write a walker or something.


Toast message on Inheritance

[x] Error due to multiple intentional touch

[x] Need to work on the timing of toast message on click

https://github.com/bithyve/bitcoin-keeper/assets/107177634/dddd0b67-3107-4791-ac5f-546a3e304aa8
https://github.com/bithyve/bitcoin-keeper/assets/107177634/1c1d92ca-3c4d-41d8-8e2b-12b7353cac1d

Completed in version 1.2.2 (330)


"releases" widget show v1.7.6 from 2016 as last release (and no changelogs)

In the right column, currently shows 8 releases, but it says that 1.7.2 (december 2016) is the most current release.
I miss changelogs too.
Thanks.

Updated the latest release. Thanks.


⚠ Bofrost.es has degraded performance

In 805293b, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1771 ms

Resolved: Bofrost.es performance has improved in 16e6618 after 6 minutes.


Typos "commmand" > "command"; "autogenerated" > "auto-generated"

@TheQwerty : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks great. Thanks for the help, @TheQuerty! #sign-off


[BOSS]Tower of Nereza

Tower of Neraza
Tier: High, mechanically can be soloed but nah.
Inspiration: Ancient tower from d3
Primary Damage Source: Minions, Debuff
Primary Defense Type: None
Attack Type:AoE, summons
Attack Animation(2nd phase only): TBD
Lore:
-Tower: Situated in a distanced island , the tower itself was once a gathering point for the island's cult which worshipped a Goddess named Nereza. The tower was used as a place where high priests would make human sacrifices as an offering to Nereza so that in return she would protect the island from evil beings that roams the realm. Underneath the tower were series of flooded dungeons that were meant to kept the offered humans, now with only remains of the misfortunes and the foul creatures that are attracted to the land.
-Nereza: Nereza is a nephalem, a half demon half angel born in times of chaos and corrupted in times of chaos. After being banished for her crimes of turning men to misshapen creatures that attack their own kind, the heavily injured Nereza proceeded to reside in a small island where she took the form of a human and plans her recovery. Using what's left of her strength, Nereza tricked the local into worshipping her as a goddess and bring her souls to feed on. When she was founded out, the cult tried to cull her but only succeeded physically. Nereza demonic soul became a curse to the cult and the whole island with the tower in the middle became an interception for dark energy across the realm to converge.
Environment
-Arena: River surrounding a small high ground with an extra size tower
Phases
Phase 1: Tower phase
Tower is immune to all physical and magical dmg. Underworld minions run in from the water and skeleton raised from the ground attack players. Periodically(10-12s?), the tower releases a small AoE represents the dark energy converged peaking and escaping from the tower. AoE lasts for 2-3s, does small dmg but mainly to grant summons(enemy only) that walks inside with atk dmg and atk speed.  Every 15s, the tower transform a random player into an angry beast that will be taunted by players standing too close to them, transformed player can navigate with beast to run straight into the tower to deal dmg to it. That player will regain his form after a 2 sec stun on impact. At 50% health the tower will release the AoE more often and minion will also receive speed, armor and health buff, making them harder to kill and cant be ignored.
-Tl,dr: survive the AoE and creeps, kill the tower with charge from the beast transform.
Phase 2
After the tower reaches 0%, it collapses, releasing the ghost of Nereza and also ending the endless stream of summons therefore starting phase 2.Ghost is affected by all dmg(yes it is a ghost). The ghost will now raise a barrier that prevents the player from reaching the water around the island and continues to release the AoE in phase 1 but now deals significantly more dmg and now slows. At every 25% health, the ghost will charge an attack that will kill everything inside the barrier. 1 player(most likely the tank or someone mobile) has to run up to the ghost to channel at a spot(for 1s), gaining a debuff that deals dmg over time from absorbing the dark magic to weaken the barrier so that the team can seek shelter in the water. The water will be crowded with the many underworld minions trapped outside the barrier at the start of the phase. At the 50% then 25%, Nereza will summon 1 then 2 cult fanatics that do knockbacks to prevent you from breaking the barrier.
-The fight ends when the ghost reaches 0 hp and the physical body of Nereza appears where the tower used to be.

Nereza is a character from Diablo III, by the way.

I like the idea of a tower being a boss. Rest is uninteresting. Closed but I noted down the general thought for further exploration.


Add Post Numbering functionality

Some users prefer to order posts by Post Number rather than the dates. Post Numbering should be an additional option.
day/time and post numbering, stardate and post numbers, etc.
If post numbering is turned on the Title of the Mission Post will have the Post number prepended to the Title.
Example:
Test Post is the third post made in the mission. Its title would be "Post 3 - Test Post"
Testing Post is the first post make in the mission. Its title would be "Post 1 - Testing Post"
Post number will be derived from the total number of posts activated in the mission prior to submission.

fixed

Post numbering should be configured at the mission level on/off functionality.

fixed

Unchecking Post Numbers does not stick after clicking submit.

fixed

unchecking post numbering works now.
However, when post numbering is off the sort should return to Date Time/Day Time/Stardate. This is not happening.

fixed

confirmed fixed


search in mongoid fails when there is no field with type String

it don't what to search for - maybe it shouldn't render form at all of there is no searchable field ?

Hmhm. As a variant. It is really ambiguous situation.


prefer query_parameters to params for search endpoint

Using params will pull values from the request body (if not present in the query parameters). We shouldn't ever see these in normal use, but somebody could pass them in to poison a cache that only keys on query parameters, not bodies (like Cloudflare). More details in #1551.
I'm still unconvinced this would be a problem in practice, since real users would be sending a search parameter in the query string, and that would skip the poisoned entry. But it's easy enough to workaround anyway, so let's do it.
It would be nice if there were a more systematic solution here, so we don't end up with a similar problem later. But this site really does very little parameter processing in the first place (this seems to be the only case in the whole code base).
Fixes: #1551

Just visiting the PR deployment won't help much here (beyond telling you I didn't totally break the search feature, of course), since that won't have Cloudflare in front of it. I manually pushed it up to the main Heroku site, so it is currently active if you visit the regular git-scm.com site.


Bug - Certification Page Uses Night Theme When Set For Code Formatting

Describe the bug
I'm back again, with another bug that I've observed in the certification page.
It uses the night theme setting when styling code in the solution modal, but the page doesn't use night theme elsewhere.
To Reproduce

Visit your settings and ensure that the Night Mode is set to on - https://www.freecodecamp.org/settings
Visit a certification with script in it eg - https://www.freecodecamp.org/certification/rtpharry/javascript-algorithms-and-data-structures
Scroll down to the projects, click on any solution
Observe that the code is barely readable because its using the night theme code colours, but the certification page itself doesn't use the night theme for anything else.

For bonus points, go back and switch night mode off and observe that it then shows readable code:

Expected behavior
Should ignore the night theme setting and display in consistent colours.

Thank you, for taking the time to open this. It was briefly mentioned, but appears to have been lost in the bussle.
Something to keep track of with this: https://github.com/freeCodeCamp/freeCodeCamp/issues/37166

What would be the desired experience?
I see two potential solutions

Use the selected theme and make the background of the code viewer dark when night theme is set
Force the code viewer to use the light theme when viewing one of the solutions on the certification

We want to go with the second option there - just use the light theme.

@moT01 , is this still relevant? Wanting to help out.

Yes, it was never fixed @TomerPacific
An issue with the help wanted or first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors.
If you would like to contribute, and have not read the contributors docs, please do so here: https://contribute.freecodecamp.org/#/
If you have any issues with contributing, be sure to join us on the contributors channel, or on the contributors sub-forum

@ieahleen, I'll start working on it.

I've gone over the project structure and am trying to pinpoint where the changes must occur.
I saw the following:

themes.js is responsible for the light/dark theme
certifications.tsx is responsible for rendering the different certifications
cert-and-project-map.ts has all the projects for each certification
Inside the templates/challenges/projects folder there is the Show.tsx which I am assuming is responsible for showing the code for each project's solution
I noticed that at the redux folder, inside index.js there is a method called createNightModeSaga (and the relevant file), but I don't know how relevant it is
There is also the certification layout inside the layouts folder

As you are probably aware, the project's structure can be quite astounding and I would appreciate some pointers as to if I am looking in the right direction or if I should be looking elsewhere.

@TomerPacific for certification completion, you can take the solutions from the md file of the projects and submit those, so then you have a completed is cert to test stuff with


Added a store less generation option for strawberry shake

Closes #3403 , #3392

@michaelstaib  I did not add a tests for subscriptions to avoid another flaky test. Should I test the NoStoreOperationExecutor?
Also, could you try this generation behaviour on one of your fancy Blazor apps?


Appstudio update test-component-pac-bpkx

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-bpkx-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
13 seconds
clone-repository

✅ Succeeded
23 seconds
build-container

✅ Succeeded
12 seconds
deprecated-base-image-check

✅ Succeeded
12 seconds
sanity-inspect-image

✅ Succeeded
34 seconds
clamav-scan

✅ Succeeded
7 seconds
clair-scan

✅ Succeeded
7 seconds
sbom-json-check

✅ Succeeded
14 seconds
sanity-label-check

✅ Succeeded
13 seconds
sanity-optional-label-check

✅ Succeeded
4 seconds
show-summary

Pipelines as Code CI/test-component-pac-bpkx-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
13 seconds
clone-repository

✅ Succeeded
23 seconds
build-container

✅ Succeeded
12 seconds
deprecated-base-image-check

✅ Succeeded
34 seconds
clamav-scan

✅ Succeeded
7 seconds
clair-scan

✅ Succeeded
12 seconds
sanity-inspect-image

✅ Succeeded
7 seconds
sbom-json-check

✅ Succeeded
14 seconds
sanity-label-check

✅ Succeeded
13 seconds
sanity-optional-label-check

✅ Succeeded
4 seconds
show-summary


Agree and update everywhere our App name

Throughout our App, README files, web-page, etc. we use different ways to call our app:

SG Land Transport
SG Land Transport App
SG Landtransport
SG Landtransport App

Let's agree on SG Land Transport, @bobrenji and @ameego?

corrected on the app and on the website


feat: Expose public top-level API

This PR creates an index.js to establish a top level, public API for the library. It also updates the example to use the npm library.
Open to exporting other stuff in the public API. I'm not yet sure what is meant to be exposed and what isn't.

Note: I bumped the version to 0.2.0 and you'll need to publish it
for the README example to work.

Published. Took a bit as I had to install a newer node.js version in a vm to be able to run an npm version new enough to allow publishing.

Published. Took a bit as I had to install a newer node.js version in a vm to be able to run an npm version new enough to allow publishing.

😅 the joys of the js ecosystem
I can make this easier for us with a github action. Will send a PR

That would be great!


Bugs when negative number

If the sum of two number is a negative number, the decrypted result is incorrect.
for example:
If   a= -99, b = 9
then decrypt( encrypt(a) + encrypt(b))  !=-90

solved.  minus n when make the decryption


Official support for Wizard?

https://huggingface.co/TheBloke/WizardLM-7B-uncensored-GGML
It would be nice to have support for an unencumbered model. Censored models don't seem to be as good at following prompts.

If it's based on Llama you should be able to run it using the LLama command
llm llama infer -m <path to Wizard model here> -p "prompt"

I've confirmed that one of TheBloke's WizardLM models works with LLaMA.


chore(rockspec) bump lua-resty-healthcheck to 1.6.1

Summary
Bump lua-resty-healthcheck to latest 1.6.x release. This is needed to use any lua-resty-events 0.1.x release.
Full changelog

lua-resty-healthcheck 1.6.1

We need to update CHANGELOG.md.


feat(gatsby-plugin-fastify): Implement trailingSlash api.

Description
Implements the trailingSlash API introduced in v4.
https://www.gatsbyjs.com/docs/reference/config-files/gatsby-config/#trailingslash
Documentation
Yup
Related Issues
closes #147

Se: https://github.com/gatsby-uc/plugins/issues/147#issuecomment-1344885282 for why this will need serious re-work.
I'm also going to go through this PR to extract some of the fixes needed to get #322 released.

saving for later

import type { FastifyServerOptions } from "fastify";
import type { GfConfig } from "./config";

export function createFastifyConfig(config: GfConfig): FastifyServerOptions {
   const { cli: { logLevel }, server: { fastify: userOptions, trailingSlash } } = config;

   return {
       logger: { level: logLevel },
       maxParamLength: 500,
       ...userOptions,
       // @ts-expect-error v4 of Gatsby had a legacy mode that should keep this true
       ignoreTrailingSlash: trailingSlash === "ignore" || trailingSlash === "legacy" ? true : false,
   }
}

With the announcement of the Gatsby Adapters spec we'll be discontinuing any work on this plugin. Should the need for a performant node server still be needed this work can continue under the official spec as gatsby-adapter-fastify.


Feature/iterate cyclic unsupported

Description
This PR is a continuation of https://github.com/microsoft/fhir-server/pull/1314.
It addresses two cases:

Cyclic include iterate queries - which are not supported.
That is, include iterate queries that include a (transitive) cycle. For example, in this query the parameter _include:iterate=DiagnosticReport:patient produces what Patient:general-practitioner consumes:
/MedicationDispense?_include=MedicationDispense:prescription&_include:iterate=MedicationRequest:patient&_include:iterate=Patient:general-practitioner&_revinclude:iterate=DiagnosticReport:performer:Practitioner&_include:iterate=DiagnosticReport:patient&_id=12345
Include Iterate parameters with Circular Reference - which according to the spec results in multiple iterations and up to the implementer to decide how many. We implement it with one iteration and the  For example, in this query, 'partof' reference is os type Organization:
Organization?_include:iterate=Organization:partof

Related issues
Addresses #1313
Testing

Unit tests in IncludeRewriterTests to assert that exception is thrown for cyclic queries
E2E tests in IncludeSearchTests to assert that for a include iterate parameters with circular reference, the iteration is executed once and an informational issue is added to indicate that

@johnstairs I've given it some thought,  I think we should consider relaxing the exception on Cyclic include iterate queries and take a similar approach to circular reference. That is if a cyclic (transitive) query exists, we can execute is it once, the order of the loop is based on the original query, and then provide informational issue as an operation outcome.
It's basically similar to circular reference, only a transitive recursion, so why not execute one iteration?
WDYT?

/azp run

@LTA-Thinking Looks like Cosmos E2E tests fail, even though the changes are related to SQL only.
There are also failures due to tests running more than 60 minutes.
Is this an environment issue?

@limorl It looks like some flaky tests. I'm rerunning them and will keep an eye on it.

@limorl It looks like some flaky tests. I'm rerunning them and will keep an eye on it.

Thanks a lot!

Thanks @limorl!


feat(Geometry/RingedSpace/OpenImmersion): make IsOpenImmersion instance

LGTM thanks!
maintainer merge

Thanks!
bors merge


Tower top load sensor accounting for yaw bearing mass

Is your feature request related to a problem? Please describe.
As far as I understand, nowadays there is no option to obtain the loading at tower top taking into account the yaw bearing mass.
The ElastoDyn sensor YawBrFzp provides the results at the yaw bearing without considering its mass.
Describe the solution you'd like
One sensor located at tower top able to provide the tower top loading accounting for the yaw bearing mass.
Describe alternatives you've considered
The sensor TwHt1FLzt provides the vertical force at tower gage 1. However, the tower gage nodes (TwrGagNd) are defined in an odd fashion, not allowing to extract the results at tower top. From the documentation:

The above formula can be expressed as: Node location = (TwrGagNd-0.5)*TowerHt/TwrNodes.
As it can be observed, by using TwrGagNd = TwrNodes (maximum allowed in the range), the actual position is always below the tower top. So, this sensor will account for the tower top loading (including the yaw bearing mass) plus a contribution from tower mass.

I suggest we add a set of sensors with the following names:

TwrTpFxi - inertial frame tower top loads, aligned with xi-axis
TwrTpFxp - tower top loads at tower top in the tower-top/base-plate coordinate system, aligned with xp-axis

Other force and moment measurements will be similarly named.


refactor(yaml): align additional error messages

Aligns the error messages in the yaml folder to match the style guide.
https://github.com/denoland/std/issues/5574

Some messages use Error 'verb'-ing form and some uses Cannot 'verb' form. I think these 2 forms are interchangeable. Should we align these 2 forms into the 1 form, or should we just allow using either of them?

Some messages use Error 'verb'-ing form and some uses Cannot 'verb' form. I think these 2 forms are interchangeable. Should we align these 2 forms into the 1 form, or should we just allow using either of them?

I think consistency would be good here. I think we've used Cannot 'verb' more often, I'll take a pass and align them. We've come this far.


Add support for #rgba, and #rrggbbaa rgba color parser

Closes 2296
✅ Pull Request Checklist:

[x] Included link to corresponding React Spectrum GitHub Issue.
[x] Added/updated unit tests and storybook for this change (for new code or code which already has tests).

📝 Test Instructions:
parseColor() will now support alpha hex values without breaking backwards compatibility
parseColor('#abcd')
parseColor('#aabbccdd')

close to fix CLA signature

Noticed during testing today, this does not enable RGBA in ColorField itself due to this line https://github.com/adobe/react-spectrum/blob/main/packages/%40react-stately/color/src/useColorFieldState.ts#L155
is that something you needed? the PR only says for the color parser, so I'm assuming you aren't using the Field?


fix: update doc deploy actions to to correct local search path on landing page

This PR addresses a search issue in the deployment script by updating the search action path in the landing page. Previously, the search action was set to search.html, causing search functionality to look for the incorrect file. With this fix, the search action path is updated to version/stable/search.html for stable versions or version/dev/search.html for development versions. This ensures that the search functionality points to the correct location, resolving the search issue effectively.

Tested successfully in https://templates.ansys.com/


Update with react 18next to latest

Fixes #4532
This updates the with-react-i18next example to latest next.js version with support for the _app.js file.

this should also finally close: https://github.com/zeit/next.js/issues/4532

Awesome, thanks!

thank you for all the work done here...


specify categorization page

Purpose
Let me see the columns in my tabular file (and their descriptions if they have them) and allow me to map each to a category from a pre-selected list of categories.
Use cases and input / output
OK, this is interesting now. I don't think there is any information that this page actually has to receive or even pass through. It probably just a layout component without any internal logic now. It contains other components that do the work. These components receive their data directly from the state. And all the logic needed to prepare the input for these components (filtering etc) will be implemented inside the store getter methods. So yeah, I think this is just about layout.
What do you think @jarmoza ?

@surchs Regarding the input, that's a correct assessment. If you look in categorization.vue, you can see that it receives its input directly from the store (mapState) and provides store values via provide and props to its child components.
So if we decide that child components can have access to the store then these mechanisms disappear for the categorization page and its current components.
Method-wise, the page does exist as more than a mere layout, however. It initiates app state via its mounted and there are several methods that perform setup for its child components. This can be an interesting rewrite for a cleaner implementation regarding separation of concerns.

Ah interesting. Yes, I think now would be a good time to think about the things the categorization page currently does during mounted. There are:

let the store know that "categorization" is now the current page

I think this doesn't lead anywhere. Eventually state.currentPage gets set in the store, but I don't think this is used.
I also think that the desired result of this would be that the nav-bar changes the color of the current page. So the nav-bar component could be where that's handled (and I think it is already)

make a "columnToCategoryTable" to be shown on the page

with the new data flow, this responsibility would fall to the table component
the store would need a getter with some reusable data and the component would need to massage into the form it needs for display

tell the store what the currently selected category is

that can also be done by the category-select component via mutation / dispath

tell the store to initialize the next page (e.g. "annotation").

I think this could run in the store / some generic initialization procedure?
afaik this is only used for the annotation page initialization. And having this interdependency between pages probably also makes testing harder

I think this could run in the store / some generic initialization procedure

Just to point out that the store action initializePage is this generic initialization procedure. The current flow is to allow access to the next page of the tool when (one of) the completion states of the current page has been reached, and then page initialization is handled in mounted of that next page.

Since so much is being removed from this page (and I already have a bunch of this work done from my previous refactor work on it), I think another possibility is the entire removal of the next page button from each page and putting it into a footer in the layout template file.
This way 'next page accessible' functionality is relegated to the store (since each check solely depends on values record into the store from user interaction).

Closed by https://github.com/neurobagel/annotation_tool/pull/233


Disable Sequence Generator for non supported providers

#151

for now did you tried?
SequenceGenerator.SupportedFactories.Add(typeof(MSSqlProviderFactory),typeof(YouCustomSqlProvider));
```cs

Hi Tolis,
I tried with <IP_ADDRESS>
SequenceGenerator.SupportedProviders.Clear(); SequenceGenerator.SupportedProviders.Add(typeof(MSSqlProviderFactory));
The same Error.

@CWolffIF sorry I missed your post, please feel free to ping me again. Also provide the connectionstring you using

Hi Tolis,
no problem. I use MSSQL server 2017:

@CWolffIF please subscribe to #161 as it is the same issue

Closing issue for age. Feel free to reopen it at any time.
.Thank you for your contribution.


Cannot open joystick or color palette

  "devDependencies": {
    "@vitejs/plugin-react": "4.3",
    "vite": "^5.4.1"
  },
  "dependencies": {
    "@react-three/drei": "^9.111.2",
    "@react-three/fiber": "^8.17.5",
    "leva": "^0.9.35",
    "react": "18.3",
    "react-dom": "18.3",
    "three": "^0.167.1"
  }

I am doing a tutorial and this is my code:
import { OrbitControls } from "@react-three/drei";
import { useControls } from "leva";

export default function Experience() {

    const {color, position} = useControls({
        position: {
            value: {x: -2, y: 0 },
            step: 0.01
        },
        color: "#ff0000"

    })

    console.log(color)

  return (
    <>
      <OrbitControls makeDefault />

      <directionalLight position={[1, 2, 3]} intensity={1.5} />
      <ambientLight intensity={0.5} />

      <mesh position={[position.x, position.y, 1]}>
        <sphereGeometry />
        <meshStandardMaterial color= {color} />
      </mesh>

      <mesh position-x={2} scale={1.5}>
        <boxGeometry />
        <meshStandardMaterial color="mediumpurple" />
      </mesh>

      <mesh position-y={-1} rotation-x={-Math.PI * 0.5} scale={10}>
        <planeGeometry />
        <meshStandardMaterial color="greenyellow" />
      </mesh>
    </>
  );
}

And whenever I click on the joystick or color, I got an error:

Error when clicking on color:
chunk-GPLYVEWD.js?v=abca52b8:16659 Uncaught
TypeError: Cannot read properties of null (reading 'getBoundingClientRect')
    at leva.js?v=abca52b8:8901:30
    at commitHookEffectListMount (chunk-GPLYVEWD.js?v=abca52b8:16904:34)
    at commitLayoutEffectOnFiber (chunk-GPLYVEWD.js?v=abca52b8:16992:23)
    at commitLayoutMountEffects_complete (chunk-GPLYVEWD.js?v=abca52b8:17976:17)
    at commitLayoutEffects_begin (chunk-GPLYVEWD.js?v=abca52b8:17965:15)
    at commitLayoutEffects (chunk-GPLYVEWD.js?v=abca52b8:17916:11)
    at commitRootImpl (chunk-GPLYVEWD.js?v=abca52b8:19349:13)
    at commitRoot (chunk-GPLYVEWD.js?v=abca52b8:19273:13)
    at performSyncWorkOnRoot (chunk-GPLYVEWD.js?v=abca52b8:18891:11)
    at flushSyncCallbacks (chunk-GPLYVEWD.js?v=abca52b8:9135:30)

chunk-CW27B3EL.js?v=abca52b8:47385 The above error occurred in the <Color> component:

    at Color (http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:9040:3)
    at div
    at Styled.div
    at div
    at Styled.div
    at Row (http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:6180:5)
    at ColorComponent (http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:9105:7)
    at div
    at Styled.div
    at ControlInput (http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:10060:5)
    at http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:10297:3
    at div
    at Styled.div
    at div
    at Styled.div
    at http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:10382:11
    at div
    at Styled.div
    at http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:10772:3
    at LevaRoot (http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:10739:5)
    at Leva (http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:10854:5)

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://reactjs.org/link/error-boundaries to learn more about error boundaries.
chunk-GPLYVEWD.js?v=abca52b8:9145 Uncaught
TypeError: Cannot read properties of null (reading 'getBoundingClientRect')
    at leva.js?v=abca52b8:8901:30
    at commitHookEffectListMount (chunk-GPLYVEWD.js?v=abca52b8:16904:34)
    at commitLayoutEffectOnFiber (chunk-GPLYVEWD.js?v=abca52b8:16992:23)
    at commitLayoutMountEffects_complete (chunk-GPLYVEWD.js?v=abca52b8:17976:17)
    at commitLayoutEffects_begin (chunk-GPLYVEWD.js?v=abca52b8:17965:15)
    at commitLayoutEffects (chunk-GPLYVEWD.js?v=abca52b8:17916:11)
    at commitRootImpl (chunk-GPLYVEWD.js?v=abca52b8:19349:13)
    at commitRoot (chunk-GPLYVEWD.js?v=abca52b8:19273:13)
    at performSyncWorkOnRoot (chunk-GPLYVEWD.js?v=abca52b8:18891:11)
    at flushSyncCallbacks (chunk-GPLYVEWD.js?v=abca52b8:9135:30)

client.ts:479 [vite] hot updated: /Experience.jsx

Error when clicking on joystick:
chunk-GPLYVEWD.js?v=abca52b8:16659 Uncaught TypeError: Cannot read properties of null (reading 'style')
    at leva.js?v=abca52b8:9239:29
    at commitHookEffectListMount (chunk-GPLYVEWD.js?v=abca52b8:16904:34)
    at commitLayoutEffectOnFiber (chunk-GPLYVEWD.js?v=abca52b8:16992:23)
    at commitLayoutMountEffects_complete (chunk-GPLYVEWD.js?v=abca52b8:17976:17)
    at commitLayoutEffects_begin (chunk-GPLYVEWD.js?v=abca52b8:17965:15)
    at commitLayoutEffects (chunk-GPLYVEWD.js?v=abca52b8:17916:11)
    at commitRootImpl (chunk-GPLYVEWD.js?v=abca52b8:19349:13)
    at commitRoot (chunk-GPLYVEWD.js?v=abca52b8:19273:13)
    at performSyncWorkOnRoot (chunk-GPLYVEWD.js?v=abca52b8:18891:11)
    at flushSyncCallbacks (chunk-GPLYVEWD.js?v=abca52b8:9135:30)
(anonymous) @ leva.js?v=abca52b8:9239
commitHookEffectListMount @ chunk-GPLYVEWD.js?v=abca52b8:16904
commitLayoutEffectOnFiber @ chunk-GPLYVEWD.js?v=abca52b8:16992
commitLayoutMountEffects_complete @ chunk-GPLYVEWD.js?v=abca52b8:17976
commitLayoutEffects_begin @ chunk-GPLYVEWD.js?v=abca52b8:17965
commitLayoutEffects @ chunk-GPLYVEWD.js?v=abca52b8:17916
commitRootImpl @ chunk-GPLYVEWD.js?v=abca52b8:19349
commitRoot @ chunk-GPLYVEWD.js?v=abca52b8:19273
performSyncWorkOnRoot @ chunk-GPLYVEWD.js?v=abca52b8:18891
flushSyncCallbacks @ chunk-GPLYVEWD.js?v=abca52b8:9135
flushSyncCallbacksOnlyInLegacyMode @ chunk-GPLYVEWD.js?v=abca52b8:9120
batchedUpdates$1 @ chunk-GPLYVEWD.js?v=abca52b8:18915
batchedUpdates @ chunk-GPLYVEWD.js?v=abca52b8:3579
dispatchEventForPluginEventSystem @ chunk-GPLYVEWD.js?v=abca52b8:7176
dispatchEventWithEnableCapturePhaseSelectiveHydrationWithoutDiscreteEventReplay @ chunk-GPLYVEWD.js?v=abca52b8:5478
dispatchEvent @ chunk-GPLYVEWD.js?v=abca52b8:5472
dispatchDiscreteEvent @ chunk-GPLYVEWD.js?v=abca52b8:5449
Show 17 more frames
Show lessUnderstand this error
chunk-CW27B3EL.js?v=abca52b8:47385 The above error occurred in the <Joystick> component:

    at Joystick (http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:9218:3)
    at div
    at Styled.div
    at div
    at Styled.div
    at Row (http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:6180:5)
    at Vector2dComponent (http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:9378:7)
    at div
    at Styled.div
    at ControlInput (http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:10060:5)
    at http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:10297:3
    at div
    at Styled.div
    at div
    at Styled.div
    at http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:10382:11
    at div
    at Styled.div
    at http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:10772:3
    at LevaRoot (http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:10739:5)
    at Leva (http://localhost:5173/@fs/Users/daysond/Desktop/threejs_tutorial/57-debug-a-r3f-application/node_modules/.vite/deps/leva.js?v=abca52b8:10854:5)

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://reactjs.org/link/error-boundaries to learn more about error boundaries.
console.error @ chunk-CW27B3EL.js?v=abca52b8:47385
overrideMethod @ console.js:288
logCapturedError @ chunk-GPLYVEWD.js?v=abca52b8:14036
update.callback @ chunk-GPLYVEWD.js?v=abca52b8:14056
callCallback @ chunk-GPLYVEWD.js?v=abca52b8:10511
commitUpdateQueue @ chunk-GPLYVEWD.js?v=abca52b8:10528
commitLayoutEffectOnFiber @ chunk-GPLYVEWD.js?v=abca52b8:17083
commitLayoutMountEffects_complete @ chunk-GPLYVEWD.js?v=abca52b8:17976
commitLayoutEffects_begin @ chunk-GPLYVEWD.js?v=abca52b8:17965
commitLayoutEffects @ chunk-GPLYVEWD.js?v=abca52b8:17916
commitRootImpl @ chunk-GPLYVEWD.js?v=abca52b8:19349
commitRoot @ chunk-GPLYVEWD.js?v=abca52b8:19273
performSyncWorkOnRoot @ chunk-GPLYVEWD.js?v=abca52b8:18891
flushSyncCallbacks @ chunk-GPLYVEWD.js?v=abca52b8:9135
flushSyncCallbacksOnlyInLegacyMode @ chunk-GPLYVEWD.js?v=abca52b8:9120
batchedUpdates$1 @ chunk-GPLYVEWD.js?v=abca52b8:18915
batchedUpdates @ chunk-GPLYVEWD.js?v=abca52b8:3579
dispatchEventForPluginEventSystem @ chunk-GPLYVEWD.js?v=abca52b8:7176
dispatchEventWithEnableCapturePhaseSelectiveHydrationWithoutDiscreteEventReplay @ chunk-GPLYVEWD.js?v=abca52b8:5478
dispatchEvent @ chunk-GPLYVEWD.js?v=abca52b8:5472
dispatchDiscreteEvent @ chunk-GPLYVEWD.js?v=abca52b8:5449
Show 21 more frames
Show lessUnderstand this error
chunk-GPLYVEWD.js?v=abca52b8:9145 Uncaught TypeError: Cannot read properties of null (reading 'style')
    at leva.js?v=abca52b8:9239:29
    at commitHookEffectListMount (chunk-GPLYVEWD.js?v=abca52b8:16904:34)
    at commitLayoutEffectOnFiber (chunk-GPLYVEWD.js?v=abca52b8:16992:23)
    at commitLayoutMountEffects_complete (chunk-GPLYVEWD.js?v=abca52b8:17976:17)
    at commitLayoutEffects_begin (chunk-GPLYVEWD.js?v=abca52b8:17965:15)
    at commitLayoutEffects (chunk-GPLYVEWD.js?v=abca52b8:17916:11)
    at commitRootImpl (chunk-GPLYVEWD.js?v=abca52b8:19349:13)
    at commitRoot (chunk-GPLYVEWD.js?v=abca52b8:19273:13)
    at performSyncWorkOnRoot (chunk-GPLYVEWD.js?v=abca52b8:18891:11)
    at flushSyncCallbacks (chunk-GPLYVEWD.js?v=abca52b8:9135:30)

this should solve your issue: https://github.com/pmndrs/leva/issues/508#issuecomment-2239498515


Guest checkout: data not retained when returning to previous steps

Reproduce:

Add random item to cart
Start guest checkout
Provide valid shipping and billing data and proceed
Provide valid credit card data and arrive at step 5 (Checkout)
Use breadcrumbs (or browser back) to return to any of the previous steps

Issue: The forms are empty which makes it impossible to edit existing input. If the user wants to change something, they have to start all over again. The previous input should be retained here.
https://github.com/Xceptance/posters-demo-store/assets/141221329/38f5d728-dc65-452a-bc3e-062408779f3a

Issue not fixed for poster version 2.1.
No more breadcrumbs to use to navigate between checkout steps.
When using "browser back" the forms are empty and no input is saved.


Résolution issue2

I have solved the window size issue. It is now larger, and I can make it even larger if necessary.
Regarding the score, I have added a counter that is displayed at the top right corner of the screen.
All the modifications made to the code can be seen using the comments I have added.

It's still not large enough, in my opinion, maybe try to make it even larger !


Review dApp/SDK installation instructions

User Story
As a developer I want to have instructions to start working on the light client or SDK. At the moment, have have some instructions but they are quite old and we haven't tested them in a while.
Acceptance criteria

[x] Instructions verified
[x] Code snippet were cleaned up (e.g. removing python comments in TypeScript code)

Tasks

I followed the instructions to clone the LC repo and install all dependencies in a clean Docker container. @kelsos was correct about that we need to execute both npm run build and npm install --save raiden-ts else it will not work.

@taleldayekh Is this issue completed? If yes, please go ahead and close it.

Yep! Will do!


Fix hyperkube handling for k8s master (pre-1.8)

Current kubeadm no longer supports KUBE_HYPERKUBE_IMAGE and requires passing control plane image via the config.

/cc @pmichali

Working on this issue, ETA is Monday Aug 28

@ivan4th any update on this issue?

I've been working on trying to integrate IPv6 capabilities into kubeadm-dind-cluster, and have been hitting a bunch of issues with bringing up the cluster. @danehans pointed me to this issue and I was wondering if it is related to what I'm seeing, as I'm trying to use local source code repo for kubernetes.
If so, please let me know as soon as you have something for this. I'm glad to try out any proposed changes.

Just to provide some background for the issue. It looks like DinD isn't working, when one wants to use a local kubernetes repo and run in "source" mode. From discussions with Ivan, it appears that KubeAdm no longer is accepting the KUBE_HYPERKUBE_IMAGE environment variable, which was the mechanism being used to allow local binaries to be used.
It sounds like the KubeAdm --config option needs to be used instead.

@ivan4th I found an issue with the fix-1.8+ branch. This gist details the issue and fix. In summary, the kdc deploy "almost" completes, it hangs on kube-proxy. The kube-proxy daemonset does not get deployed because the controller-manager pod is not running on the master container. The controller-manager pod on the master container is not running because the associated manifest is in /manifests.bak instead of /etc/kubernetes/manifests. I see that snapshot is moving the manifest to /manifests.bak, but I don't understand the reasoning behind this code to update it as needed.

I also had to update DefaultKubernetesVersion to v1.8.0-rc.1 in cmd/kubeadm/app/apis/kubeadm/v1alpha1/defaults.go. I need to understand how you manage the kubeadm.conf file so this k/v pair can be added or updated.

@ivan4th I still intermittently notice the kube-controllermanager.yaml static pod manifest not getting moved from the backup dir > /etc/kubernetes/manifests:
* Taking snapshot of the cluster
deployment "kube-dns" scaled
deployment "kubernetes-dashboard" scaled
pod "kube-proxy-ztff7" deleted
WARNING: cluster glitch: proxy pods aren't removed; pods may 'blink' for some time after restore
* Waiting for kube-proxy and the nodes
...................................................

After moving the manifest # mv /manifests.bak/kube-controller-manager.yaml /etc/kubernetes/manifests/:
* Waiting for kube-proxy and the nodes
................................................................................................[done]
* Bringing up kube-dns and kubernetes-dashboard
deployment "kube-dns" scaled
deployment "kubernetes-dashboard" scaled
.....[done]
NAME          STATUS         AGE       VERSION
kube-master   Ready,Master   4m        v1.9.0-alpha.1.609+a43cb7e2f363b8
kube-node-1   Ready          29s       v1.9.0-alpha.1.609+a43cb7e2f363b8
kube-node-2   Ready          29s       v1.9.0-alpha.1.609+a43cb7e2f363b8
* Access dashboard at: http://localhost:8899/ui

real	14m12.389s
user	0m49.801s
sys	0m14.597s

@danehans In the PR I have (#42), I included a fix for that. The code just returns, if the controller or proxy pods cannot be stopped, and misses out out restoring the file. I changed the returns to breaks, as part of that PR and don't see that issue.
One one system, I do see a problem stopping DNS occasionally, but the system does come up, after a longer time.

1.8 and later versions work ok now


Adding support for KijkOnline on Vier and Vijf in existing extractor.

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[X] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[X] Searched the bugtracker for similar pull requests
[X] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[X] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[X] New extractor
[ ] New feature

Description of your pull request and other information
Adding support for KijkOnline on Vier and Vijf in existing extractor.

I just checked this out locally and verify it works.

This PR was verified to work by several people. Can this be merged, @dstftw? Or is there anything else we can do? Cheers!

Works for me as well.

It might've slipped @dstftw's attention?

Verified that this works nicely.

I worked nicely but it recently stopped working nicely
Traceback (most recent call last):
  File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "~/development/tools/youtube-dl/youtube-dl/__main__.py", line 19, in <module>
  File "~/development/tools/youtube-dl/youtube-dl/youtube_dl/__init__.py", line 465, in main
  File "~/development/tools/youtube-dl/youtube-dl/youtube_dl/__init__.py", line 455, in _real_main
  File "~/development/tools/youtube-dl/youtube-dl/youtube_dl/YoutubeDL.py", line 1988, in download
  File "~/development/tools/youtube-dl/youtube-dl/youtube_dl/YoutubeDL.py", line 784, in extract_info
  File "~/development/tools/youtube-dl/youtube-dl/youtube_dl/extractor/common.py", line 438, in extract
  File "~/development/tools/youtube-dl/youtube-dl/youtube_dl/extractor/vier.py", line 76, in _real_extract
IndexError: list index out of range

Same here.....
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Git HEAD: bbd9d8c17
[debug] Python version 3.6.5 (CPython) - Darwin-15.6.0-x86_64-i386-64bit
[debug] exe versions: avconv 12.3, avprobe 12.3, ffmpeg 3.4.2, ffprobe 3.4.2
[debug] Proxy map: {}
[viervijfkijkonline] None: Downloading webpage
Traceback (most recent call last):
  File "/usr/local/Cellar/python/3.6.5/Frameworks/Python.framework/Versions/3.6/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/local/Cellar/python/3.6.5/Frameworks/Python.framework/Versions/3.6/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/Users/mwesten/source/youtube-dl/youtube_dl/__main__.py", line 19, in <module>
    youtube_dl.main()
  File "/Users/mwesten/source/youtube-dl/youtube_dl/__init__.py", line 471, in main
    _real_main(argv)
  File "/Users/mwesten/source/youtube-dl/youtube_dl/__init__.py", line 461, in _real_main
    retcode = ydl.download(all_urls)
  File "/Users/mwesten/source/youtube-dl/youtube_dl/YoutubeDL.py", line 1989, in download
    url, force_generic_extractor=self.params.get('force_generic_extractor', False))
  File "/Users/mwesten/source/youtube-dl/youtube_dl/YoutubeDL.py", line 785, in extract_info
    ie_result = ie.extract(url)
  File "/Users/mwesten/source/youtube-dl/youtube_dl/extractor/common.py", line 440, in extract
    ie_result = self._real_extract(url)
  File "/Users/mwesten/source/youtube-dl/youtube_dl/extractor/vier.py", line 76, in _real_extract
    season = title_split[1].split('Seizoen')[1].strip()
IndexError: list index out of range

Made a small adjustment on the part where season number is determined. Should be working again now.

Just checked out locally and it works for me, too.  Great work!
@dstftw, I would vote for merging....

Also checked out locally and it works.
@dstftw, I would vote for merging....

This works for me!

@brechtm A lot of people confirmed this works and the PR is almost open for over a year now (a lot more than 6-10 days ;-) ). Any reason why this PR is not merged?

Hi @dstftw, could you take a look at this PR as @brechtm is not active anymore I think?
Thx!

I am not and never was involved with youtube-dl development/maintenance in any way, so it's not up to me :-)
I do notice that it takes a long time for PRs to get merged. I suspect this is due to the fact that this is a very popular project, and the maintainers simply do not have the time to handle all PRs in a timely manner. Perhaps it would be good to rethink how PRs are handled; for example, having volunteers handle PRs for extractors. For example, one volunteer could be responsible for all Belgian TV channel extractors.

I like that idea!
Indeed, a PR that takes over a year to get merged is a bit long.
On Sun, Feb 10, 2019, 00:23 Brecht Machiels<EMAIL_ADDRESS>wrote:

I am not and never was involved with youtube-dl development/maintenance in
any way, so it's not up to me :-)
I do notice that it takes a long time for PRs to get merged. I suspect
this is due to the fact that this is a very popular project, and the
maintainers simply do not have the time to handle all PRs in a timely
manner. Perhaps it would be good to rethink how PRs are handled; for
example, having volunteers handle PRs for extractors. For example, one
volunteer could be responsible for all Belgian TV channel extractors.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rg3/youtube-dl/pull/15636#issuecomment-462088760, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAiqIvpG5yjiVL0bbrygFcMJYhxN_wBZks5vL1hhgaJpZM4SJmJP
.

Checked it out locally, but does not work here.
>youtube-dl https://www.vier.be/video/hotel-romantiek/hotel-romantiek-seizoen-3/hotel-romantiek-s3-aflevering-6 --verbose
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['https://www.vier.be/video/hotel-romantiek/hotel-romantiek-seizoen-3/hotel-romantiek-s3-aflevering-6', '--verbose']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2019.03.09
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.17763
[debug] exe versions: avconv 11.3, avprobe 11.3
[debug] Proxy map: {}
[vier] hotel-romantiek-s3-aflevering-6: Downloading webpage
ERROR: Unable to extract filename; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpy110f8qy\build\youtube_dl\YoutubeDL.py", line 794, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpy110f8qy\build\youtube_dl\extractor\common.py", line 522, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpy110f8qy\build\youtube_dl\extractor\vier.py", line 170, in _real_extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpy110f8qy\build\youtube_dl\extractor\common.py", line 997, in _search_regex
youtube_dl.utils.RegexNotFoundError: Unable to extract filename; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

@dmbekker Just tried downloading that episode myself, and it worked fine:
./youtube-dl 'https://www.vier.be/video/hotel-romantiek/hotel-romantiek-seizoen-3/hotel-romantiek-s3-aflevering-6' --username [USERNAME] --password [PASSWORD]

[viervijfkijkonline] None: Downloading webpage
[viervijfkijkonline] Peforming API Call
[viervijfkijkonline] d38f1100-d383-4dd6-a191-41d14f3bfa3f: Downloading m3u8 information
[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 253
[download] Destination: Hotel Römantiek - Seizoen 3 - Aflevering 6-d38f1100-d383-4dd6-a191-41d14f3bfa3f.mp4
[download]  15.1% of ~180.04MiB at  1.26MiB/s ETA 00:04

It seems like you're not using the fixed branch of @wernerkarlheisenberg, but instead another youtube-dl version (the main branch probably?). What do you get for youtube-dl --version? It should be '2018.01.21'.
Also note that you need to provide a username/email and password. But if you're on the right branch, you should get appropriate warnings if you don't.

@jeffreykuiken Not an expert on Git, I'm probably doing some Git-wizardry wrong..
david@Laptop-David $ git checkout
 Your branch is up-to-date with 'origin/master'.
david@Laptop-David $ git fetch origin pull/15636/head:Vier-support
david@Laptop-David $ git checkout Vier-support
 Switched to branch 'Vier-support'
david@Laptop-David $ bin/youtube-dl --version
 2019.03.09

This won't be accepted with 3rdparty dependencies.

What 3rd party dependency?

@michaelarnauts I think it's the boto3 and warrant imports: https://github.com/ytdl-org/youtube-dl/pull/15636/files#diff-0b9e729a4218ad20621e16c6ef2665efR11

Ow right, I only looked at the imports at the top. @wernerkarlheisenberg is there a way to rewrite this PR without these dependencies?

Trying to download from vier for the first time and getting filename error.  I just updated to latest version and video does work on the site.
Davids-MacBook-Pro:~ davidnewell$ youtube-dl --verbose https://www.vier.be/video/bake-off-vlaanderen/bake-off-vlaanderen-s3/bake-off-vlaanderen-s3-aflevering-1-04092019
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'--verbose', u'https://www.vier.be/video/bake-off-vlaanderen/bake-off-vlaanderen-s3/bake-off-vlaanderen-s3-aflevering-1-04092019']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2019.12.25
[debug] Python version 2.7.16 (CPython) - Darwin-18.7.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 4.2.1, ffprobe 4.2.1, rtmpdump 2.4
[debug] Proxy map: {}
[vier] bake-off-vlaanderen-s3-aflevering-1-04092019: Downloading webpage
ERROR: Unable to extract filename; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 796, in extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 530, in extract
ie_result = self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/vier.py", line 170, in _real_extract
webpage, 'filename')
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 1005, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract filename; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
If I try to login I get this error:
Davids-MacBook-Pro:~ davidnewell$ youtube-dl -u<EMAIL_ADDRESS>https://www.vier.be/video/bake-off-vlaanderen/bake-off-vlaanderen-s3/bake-off-vlaanderen-s3-aflevering-1-04092019
Type account password and press [Return]:
[vier] Logging in
ERROR: Unable to log in: HTTP Error 403: Forbidden (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

@dnewell425 That episode is behind a geoblock and only accessible from Belgium, resulting in this error when you're downloading from outside Belgium. Could that be the case for you?

I’m using a VPN for Belgium - which so far has worked for Kenya, Germany, Denmark…. I suppose I could try the geo workarounds in youtube-dl and see if that works?

On Dec 28, 2019, at 7:17 AM, Jeffrey<EMAIL_ADDRESS>wrote:
@dnewell425 https://github.com/dnewell425 That episode is behind a geoblock and only accessible from Belgium, resulting in this error when you're downloading from outside Belgium. Could that be the case for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ytdl-org/youtube-dl/pull/15636?email_source=notifications&email_token=AOEP2OAOE5KPIVEN326QEMTQ247WHA5CNFSM4ERGMJH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHYIT5I#issuecomment-569412085, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOEP2OCBTYAPFFQ6JCUJ4LTQ247WHANCNFSM4ERGMJHQ.

It looks like they changed their website structure. With the following patch, it works again for me:
diff --git a/youtube_dl/extractor/vier.py b/youtube_dl/extractor/vier.py
index 86d7e007f..6464e7b82 100644
--- a/youtube_dl/extractor/vier.py
+++ b/youtube_dl/extractor/vier.py
@@ -67,7 +67,7 @@ class VierVijfKijkOnlineIE(CognitoBaseIE):
         webpage = self._download_webpage(url, None)

         title = self._html_search_regex(
-            r'
(.+?)
',
+            r'<meta\s*property="og:title"\s*content="(.+?)"\s*/>',
             webpage, 'title')

         title_split = title.split(' - ')
@@ -83,7 +83,7 @@ class VierVijfKijkOnlineIE(CognitoBaseIE):
             episode = title_split[1].split('Aflevering')[1].strip()

         video_id = self._html_search_regex(
-            r'
]+data-file="(.+?)"[^>]+>',
+            r'"videoUuid":"([0-9a-f-]*)"',
             webpage, 'video_id')

         api_url = 'https://api.viervijfzes.be/content/%s' % (video_id)

The problem is with the boto3 and warrant dependencies, since they won't be approved. I have an implementation that doesn't require those.
https://github.com/add-ons/plugin.video.viervijfzes/blob/master/resources/lib/viervijfzes/auth_awsidp.py

What is the correct way to continue? Can we update this pull request or can only @wernerkarlheisenberg do this?

I have another way to fix this, will probably do this in another PR unless somebody else does it first :)

I have another way to fix this, will probably do this in another PR unless somebody else does it first :)

Since it has been a while since you said this, and because of all the other patches needed on top of the current PR for it to work, I thought I do it myself. So I've created a new PR based on all the great contributions in the current PR. Hopefully it can get merged this time.

I have another way to fix this, will probably do this in another PR unless somebody else does it first :)

Since it has been a while since you said this, and because of all the other patches needed on top of the current PR for it to work, I thought I do it myself. So I've created a new PR based on all the great contributions in the current PR. Hopefully it can get merged this time.


drawio extension for Google Docs is not working well

Preflight Checklist

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

You must agree to search and the code of conduct. You must fill in this entire template. If you delete part/all or miss parts out your issue will be closed.
If you are technical, you should reporting bugs along the lines of https://marker.io/blog/how-to-write-bug-report. If you are not technical, we will make allowances, please try to make an effort to understand the process.
Describe the bug
I installed the extension in Google Docs and tried to add a chart and every time I got an error message
Screenshots
https://www.loom.com/share/4e3aa69c1a3b48b088ea1750fd44ee5e?sid=990ab406-55a9-414c-ae9c-27e6d2a4c33c
I did a record of the bug
draw.io version (In the Help->About menu of the draw.io editor):

draw.io version 24.6.1

Desktop (please complete the following information):

OS: Windows 10 Pro
Browser chrome
Browser Version 126.0.6478.127

I tested the problem in incognito/private mode with all browser extensions switched off, write "yes" below:

That's a error with the Google Drive picker, it's not an error in our code. As i workaround I would suggest to already have the file uploaded to Google Drive prior to selecting in the addon.


Rename helm chart to jupyterhub-home-nfs

Also accounts for the move to 2i2c-org GitHub organization.
@sgibson91  We should rename this repo to jupyterhub-home-nfs before merging this PR. I don't have enough access to do that. Could you please make that change?

Fixes #2
related to https://github.com/2i2c-org/infrastructure/issues/4889

Could you please make that change?

Done!

I also just bumped you to admin of the repo as well. With great power... 😉


Caching feature for handling rate limits of pinboard.in service

I think that the pinboard plugin which uses pinboard.js works even without a rate limiter by redirecting user to the actual page (all bookmarks - go to pinboard.in/:your username).
However it would be nice to add some kind of simple caching feature that would check for last timestamp (via a simple file?) of request and check if last posts/all call was 5 minutes ago or not).
More info on rate limited pinboard.in API at https://pinboard.in/api/

API requests are limited to one call per user every three seconds, except for the following:
posts/all - once every five minutes
posts/recent - once every minute

Caching can be implemented in a lot of ways (e.g. LRU, caching in memory, caching to disk). It's best for us to keep this library low level and if anyone wants to implement caching on top of it, then they can wrap with their needs.


Client crashes when server-hopping after server reintegration

This seems to be media related

This should be fixed now, feel free to comment if I'm wrong


Virus detections on executable

Check my release, built on mingw32: 2 minor detections compared to 16 on VC build at VirusTotal.
The case could be in your build chain options

Nice, nice, nice, thanks 👌😀

Nice, nice, nice, thanks 👌😀


Inconsistent Behaviour of the plugin

Upon installing the mixer plugin, the behaviour was as expected

After sometime, used to provide correct response even though the consumer key is not passed

And again, even though the consumer key was properly sent, it failed with PERMISSION_DENIED error

Could not set any consistent behaviour though.
Using new version of the plugin and K8s 1.9.3

This deserves investigation. It is possible that the behavior you're seeing is due to a cache?

I'm seeing this inconsistent behavior as well with the verify api key functionality. I run several curl commands in a row, using a valid API key, some succeed, others fail with PERMISSION_DENIED.

I'm investigating this now. If there's any way you can recreate this behavior with debug logging on for the adapter, that would be extremely helpful.

Also, if you could provide your platforms and whether you ran istio-demo.yaml or istio-demo-auth.yaml, that would be helpful. Thanks.

Hi Scott, below are some details about my setup. I deployed the helloworld sample (used istio-demo.yaml) from my local mac, to a GKE cluster.
Istio Mixer Adapter version:
istio-mixer-adapter_1.0.0_macOS_64-bit
K8s version:
kubectl version --short
Client Version: v1.9.7
Server Version: v1.10.5-gke.4
I'll look into getting a debug log.

What I've found during my troubleshooting is what appears to be "inconsistent" behavior is really due to the fact that applying the rule takes time to get propagated to all instances (in this case helloworld v1 and helloworld vs). This means that after you apply the rule, there will be a short period of time where the rule applies to one version but has not been applied to the other version. Thus, as the load balancer sends your request back and forth to both versions during that time, it will appear that it works sometimes (hitting v1) but not work other times (hitting v2). After a short time, after the rule has propagated to both, the behavior becomes consistent.

There is also a short delay between changing any configuration in the Product in Apigee Edge and having that change reflected and applied by the adapter.
OP, I'm not sure if this is your issue, but please watch out for these timing issues as they can bite you if you start attempting to test immediately after making a change (i.e. before the change has had time to fully propagate).

Yes, by default, the polling refresh rate for product information from Apigee is every 2 minutes. This could be adjusted in config or you could turn on debug level logging for the adapter and watch for lines like this to indicate that the product information has been refreshed:
2018-08-31T16:58:05.660590Z	debug	adapters	retrieving products from: https://theganyo1-eval-test.apigee.net/istio-auth/products	{"adapter": "apigee-handler.apigee.istio-system"}
2018-08-31T16:58:06.103321Z	debug	adapters	retrieved 3 products, kept 2	{"adapter": "apigee-handler.apigee.istio-system"}

@aswinsegu Is it possible that your issue was caused by config latency as described above? Thanks.

@theganyo The issue is not due to latency, as i had given enough time around 10 mins for each behaviour to act up on. Any how, had to clean the cluster and now its working from scratch up.
But need to see why that happened at all

I cannot recreate this issue directly, but I believe this problem is likely due to a timing issue in the product dispatch that I've since fixed. I've also reviewed the code and don't see any other culprits. I'm going to close this, but I'll be keeping an eye out for any potential reasons why false rejections could occur. If it happens again, please also try to capture the mixer logs at DEBUG level. See: https://github.com/apigee/istio-mixer-adapter/wiki/Mixer-logging-and-metrics.

Still see this error. The bug which you have mentioned has that been released in 1.0.4?


fix(cloud-masthead): ensure megamenu bottom graident sticks to bottom

Related Ticket(s)
#7232
Description
Cloud megamenu has a gradient at the bottom of the megamenu that user sees when the megamenu is scrollable. When user scrolls however, the gradient is stuck in the same position. Seems the megamenu needs a set bottom value

FIX:

Changelog
Removed

bottom: auto

@annawen1 I just caught this bug the other yesterday! Here's the issue https://app.zenhub.com/workspaces/carbon-for-ibmcom-5d449f3642eb1962336cbe52/issues/carbon-design-system/carbon-for-ibm-dotcom/7232. I added it to PR description, but not sure if you'd like to assign yourself or what's the standard.

@annawen1 I just caught this bug the other yesterday! Here's the issue https://app.zenhub.com/workspaces/carbon-for-ibmcom-5d449f3642eb1962336cbe52/issues/carbon-design-system/carbon-for-ibm-dotcom/7232. I added it to PR description, but not sure if you'd like to assign yourself or what's the standard.

oh great! I'll assign myself!

@proeung & @annawen1 This bottom: auto was added because other wise you can't click out of the dropdown menu unless you go all the way into the bottom 4rem of the viewport where this element's margin is.

Gotcha, new PR to add the bottom: auto back and set the gradient pseudo element positioning to fixed instead: https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/7253


Changed the protocols to be class protocols.

fixes #45
By doing this, these protocols can now NOT be
impelmented by structs.

:+1: looks good, thanks for catching this!


More visibility in Seq for events dropped at the client

after setting eventBodyLimitBytes to some value, if an event is dropped because it's size is too big please add an option to add an alternative fixed message to the log (e.g. "Event dropped because size is too big") so that the person reading Seq will at least know that there was something here and that he might find this info in the file logs I keep

Thank you for your suggestion, Dani.
One way this might be emulated, currently, is to enable SelfLog and re-emit an event through the Serilog pipeline if the text matches the one in:
https://github.com/serilog/serilog-sinks-seq/blob/dev/src/Serilog.Sinks.Seq/Sinks/Seq/SeqSink.cs#L187
Not an entirely elegant solution, but worth considering if this is important in your usage scenario.

Nick,
Few points:

that would cause the long json event to be logged (as it is written in the line you mentioned)
I have created in Seq many API keys for many services. Chances are that the user reading the logs using Seq will filter by specific properties added by each API key to distinguish the source of the message. That means they will not see the messages emitted from the self log and when reading the log will not know a line is missing.
another thing that comes to mind is that the alternative event written to the logs should be customizable with a few properties (like original message timestamp, original message size). not sure about allowing access to other properties of the original message so a loop is not created if I reference the original message property that caused the whole thing to be too long

We've reviewed this again and think that something along these lines could address your requirements and not add too much more complexity in this sink:
https://github.com/serilog/serilog/issues/1791#issuecomment-1884134585
The essential idea is that you'd register a handler for logging failures, the handler would have access to the "problem" events in their original form, and we'd try to make the result of the callback actionable. Will continue fleshing this out over there.


Needs tests written

Currently there are no spec/e2e tests - these will need writing asap

begun as of https://github.com/j3ddesign/j3ng-components/commit/5ff5f17a077add3a7109eb12ec22d7cb465ead3e

Closing for now as this was more of a reminder to myself


Lmstudio support

Please add support for working with local Lm studio server.

hey @SuperLotar - you can use LM Studio now!
I have added compatibility for any open ai compatible server. you can use the custom LLM provider it to set a custom base url and point that to your LM studio server.
checkout the README & cookbook for an example


Nav2 not working

Hi, I am getting this error at runtime:
[ERROR] [gzserver-1]: process has died [pid 21874, exit code -2, cmd 'gzserver -s libgazebo_ros_init.so /home/jetbot/nav2_ws/install/nav2_bringup/share/nav2_bringup/worlds/waffle.model'].

Hi, I see that this is an error with gazebo, which is probably not installed. However, it is weird that this comes up since gazebo is not a part of this project. Are you trying to run some sort of simulation?


Wrong parsing useragents string on www.useragents.me

Some strings end with a dot, some strings clearly lack numbers at the end. Such (compatible; Google-Read-Aloud; +https://support.google.com/webmasters/answer/1061943 usergents are no good either.
Thanks for project.

I don't do any parsing, I just get user agents from useragents.me. If the parsing is wrong there, you can contact the author of the website. Let me know.


add Sender::is_closed method

It useful to be able to check if the channel is closed without registered to a task.
I didn't do it in this PR because I'm unsure of the name, but it's related: as mention in https://github.com/rust-lang-nursery/futures-rs/issues/775, it would be useful to close a channel from a Sender. I'm not sure if it should be required to have a Context, like with poll_close, so that someone could signal a close in another thread, but I'm sure the name close is reserved to be the mini-future for poll_close that borrows self.

Any thoughts on the point in the description comment?

About the naming of close? Maybe close_channel?

Or you could keep with the pattern used in some of the other methods and have poll_close and try_close, where try_close doesn't take a task::Context.

Of course, closing an mpsc channel has no error case, so it could just be fn close_channel(&mut self) {.

Seems fine to me!


Implement NativeExtension pointer arguments

Allows calling into native extensions directly with a pointer
Makes it easier to implement some APIs more efficiently
Appears with a "*" in the documentation for the argument.
Implementing the pointer handling is entirely up to the implementation, although the extension API provides some hint.
AudioStream has been implemented as an example, allowing to create NativeExtension based AudioStreams.

Example of how it looks:
GDVIRTUAL3(_mix, GDNativePtr<AudioFrame>, float, int)

So if I understand we can now directly send pointers to Godot by casting them to regular int64 by using this new hint.
Will that solve this proposal: https://github.com/godotengine/godot-proposals/issues/3037 ?
When it comes to usability, not sure I really get the AudioStream example.
So in 3.x, this class could only be used/implemented in a module because it was making use of a pointer to an internal structure AudioFrame. But in 4.0, AudioStream is exposed in the API because of the new virtual bind and the _mix method "sees" an int in place of the AudioFrame pointer?

@CedNaru This is not a way to send generic pointers to Godot, it's a way for Godot to send generic pointer to native extensions. It's only meant for implementations using compiled languages to receive low level data required in some situations (like mixing audio, writing network data buffers, etc).

I also have no idea if it solves the proposal, the author did not make clear what the intention was with it.

Hum ok, so this PR won't solve it.
The intent was to send pointers to third-party library structs/classes to Godot and store them in a variant for future use which is kinda the reverse of this PR.

@CedNaru as written in that proposal, you can cast to integer and back, its not very difficult and makes little difference.

Are the AudioFrame members meant to be accessed by native extensions? If so how can they do this if they don't have the struct declaration?


RNN Transducer training problem

Hi,
It seems that your implementation of RNN Transducer loss function is right. But when I train
Graves2012 TIMIT, the loss decrease, but the PER increase, no matter how to adjust learning rate.
( If choose a small lr, the PER would be first decrease, then increase all the time. )
In your training procedure, the RNNT loss is exactly decreasing, but if you output the PER, it increasing!
So what's wrong ?

Hi,
Recently, I write a greedy decoding for transducer:
    def greedy_decode(self, batch):
        x, y, x_lens, y_lens = self.collate(*batch)
        x = self.encode(x)[0]
        vy = autograd.Variable(torch.LongTensor([0]), volatile=True).view(1,1) # vector preserve for embedding
        y, h = self.dec_rnn(autograd.Variable(torch.zeros((1, 1, 256)), volatile=True)) # decode first zero
        y_seq = []; logp = 0
        for i in x:
            out = self.fc1(i) + self.fc1(y[0][0])
            out = nn.functional.relu(out)
            out = self.fc2(out)
            out = F.log_softmax(out, dim=0)
            p, pred = torch.max(out, dim=0)
            pred = int(pred); logp += float(p)
            if pred != self.blank:
                y_seq.append(pred)
                vy.data[0][0] = pred # change pm state
                y = self.embedding(vy)
                y, h = self.dec_rnn(y, h)
        return [y_seq]

This code can be placed in your transducer_model.py file. Here just support one sequence per batch.
After decoding, PER is 24.4% in your training model ( maybe not converged).
It seems that the training PER calculated in the CTC way doesn't make sense.
Beam search would be much better.

It seems that the training PER calculated in the CTC way doesn't make sense.
What do you mean?

@smolendawid what you said is exactly what I mean.
Since the CTC transition topology is almost the same with HMM, the greedy search can be treated as viterbi decode. But the transition of RNN Transducer is two dimensional, decode any one of them doesn't make any sense.

It seems that the training PER calculated in the CTC way doesn't make sense.
I have the same problem. What's wrong with it ?

@HawkAaron  your greed decode implement is wrong. this will not find the best path
Here is my implement
`    print(result)
def decode(preds,lens,lstm_decoder,alpha):
print preds.size()
_,batch_size,nclass=preds.size()
zero_cat=torch.FloatTensor(1,1,nclass-1).fill_(0)
a=time.time()
y_seq=[""]*batch_size
yi_index_old=93984
loop_count=0
for batch_index in range(batch_size):
  y, hid1,hid2 = lstm_decoder.decode(Variable(zero_cat).cuda())
  pred=preds[:,batch_index,:]
  for xi_index in range(lens[batch_index]):
     xi=pred[xi_index][:]
     flag=True
     loop_count=0
     while flag:
       loop_count+=1
       y_i=y[0][0][:]
       ytu = nn.functional.softmax(y_i+xi,dim=0)
       max_value,yi=torch.max(ytu,0)
       yi_index=int(yi.data)
       #print(yi_index)
       if loop_count>1 and yi_index==yi_index_old:
          flag=False
          break
       if yi_index!=0:
          yi_index_old=yi_index
          t=torch.IntTensor([yi_index-1])
          l=torch.IntTensor([1])
          t_onehot=utils.oneHot(t,l,nclass-1)
          t_onehot=t_onehot.permute(1,0,2) #btn
          y, hid1,hid2 = lstm_decoder.decode(Variable(t_onehot).cuda(),hid1,hid2)
          y_seq[batch_index]+=alpha[yi_index-1]
       else:
          flag=False
return y_seq`

def decode(preds,lens,lstm_decoder,alpha):     _,batch_size,nclass=preds.size()     zero_cat=torch.FloatTensor(1,1,nclass-1).fill_(0)     a=time.time()     y_seq=[""]*batch_size     yi_index_old=93984     loop_count=0     for batch_index in range(batch_size):       y, hid1,hid2 = lstm_decoder.decode(Variable(zero_cat).cuda())       pred=preds[:,batch_index,:]       for xi_index in range(lens[batch_index]):          xi=pred[xi_index][:]          flag=True          loop_count=0          while flag:            loop_count+=1            y_i=y[0][0][:]            ytu = nn.functional.softmax(y_i+xi,dim=0)            max_value,yi=torch.max(ytu,0)            yi_index=int(yi.data)            if loop_count>1 and yi_index==yi_index_old:               flag=False               break            if yi_index!=0:               yi_index_old=yi_index               t=torch.IntTensor([yi_index-1])               l=torch.IntTensor([1])               t_onehot=utils.oneHot(t,l,nclass-1)               t_onehot=t_onehot.permute(1,0,2) #btn               y, hid1,hid2 = lstm_decoder.decode(Variable(t_onehot).cuda(),hid1,hid2)               y_seq[batch_index]+=alpha[yi_index-1]            else:               flag=False     return y_seq

@Duum That is based on the assumption that one acoustic feature frame has at most one corresponding label.
To find more comparable paths, you can refer to my beam search implementation.


Packwiz won't upgrade the Fabric API from 0.75.0 to 0.76.0 for 1.19.2

Just encountered an issue where my Fabric API version will not upgrade.
5 days ago there was a release for 1.19.2 https://www.curseforge.com/minecraft/mc-mods/fabric-api/files/4438705 and every time I packwiz upgrade fabric-api it tells me it is up to date, even though it is on 0.75.0.
TLDR:  Stays on fabric-api-0.75.0+1.19.2.jar when packwiz upgrade fabric-api should take it to fabric-api-0.76.0+1.19.2.jar

Further testing

removing and re-addng does nothing for the situation.  It pulls down 0.75.0.

Are you using the latest version of packwiz? What is in your pack.toml? I can't seem to replicate this issue.


Not supported on older browser versions due to Intl.PluralRules & Intl.Locale

https://caniuse.com/?search=PluralRules
My main phone is an iPhone 6S running 12.1.1. It's not able to load the webpage as it does not have Intl.PluralRules & Intl.Locale. As such I'm using polyfills for both:
import "@formatjs/intl-pluralrules/polyfill";
import "@formatjs/intl-locale/polyfill";

This isn't really a bug or problem with the library. But perhaps the library could either call an alternative method or provide a section with instructions on how to solve this issue on older browsers:
TypeError: undefined is not a constructor (evaluating 'new Intl.PluralRules(locale)')
getTranslateInstance
src/util.object.ts:20
  17 | // eslint-disable-next-line @typescript-eslint/explicit-module-boundary-types, @typescript-eslint/no-explicit-any
  18 | function i18nObject(locale, translations, formatters = {}) {
  19 |     return createProxy(getTranslateInstance(locale, translations, formatters));
20 | }
  21 | exports.i18nObject = i18nObject;
  22 | const createProxy = (fn, prefixKey) => new Proxy((prefixKey ? fn.bind(null, prefixKey) : {}), {
  23 |     get: (_target, key) => createProxy(fn, prefixKey ? ${prefixKey}.${key} : key),

EDIT: I updated to 2.34.0 and tried it again. On 2.34.0, it doesn't outright crash but instead it shows the translation label keys. In a way it's good because it still renders and is still usable. In other ways it's bad because it fails silently.

Hi @aelesia;
I'm aware that these functions are not supported in older browsers. I don't want to include the polyfills in the library itself, so like you already guessed, you need to include them by yourself.
The only thing I could do is updating the READMRE file to make it clear.
Do these two polyfills you mentioned work on older browsers?

Hi! Yup I've tested on my iPhone 6S running 12.1.1. It works after adding both of these lines:
import "@formatjs/intl-pluralrules/polyfill";
import "@formatjs/intl-locale/polyfill";

https://formatjs.io/docs/polyfills/intl-pluralrules/
https://formatjs.io/docs/polyfills/intl-locale

Ok, thanks! I will update the README file

@aelesia nut sure why you need to include both polyfills?
I just checkt the formatjs website and it seems you would only need this polyfill:
https://formatjs.io/docs/polyfills/intl-pluralrules/
typesafe-i18n by default only uses Intl.PluralRules. Additional there exist two optional formatters that use the Intl.NumberFormat and Intl.DateTimeFormat functions. But it seems these two are included into the Intl.PluralRules polyfill.
Can you please confirm that it works only with the single polyfill?


ci: prepare release

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


Rare Satoshi Supply figures on docs.ordinals.com are inconsistent

Hi everyone,
It's possible I've made some errors in my calculations but please could this be checked? [Checked by sat_stats (X) and amended]
Ordinals.com is seen as the primary source of rare sat data so I think it's important that everything is correct.
From https://docs.ordinals.com/overview.html :
uncommon: 6,929,999
rare: 3437
epic: 32
legendary: 5
mythic: 1
Now, assuming that higher rarities supersede lower rarities, then the mythic is not a legendary, and hence there are 5 legendaries, as shown. However, according to this logic, the mythic and the legendaries are neither epics nor rares, so there should only be 27 epics and 3432 rares. Likewise there will only be 6,926,535 uncommons.
So assuming rarities don't overlap (the best approach imo) then the list should look like this: [figures amended based on checks performed by sat_stats (X)]
uncommon: 6,926,535
rare: 3432
epic: 27
legendary: 5
mythic: 1
If they do overlap then it would look like this: [figures amended based on checks performed by sat_stats (X)]
uncommon: 6,930,000
rare: 3438
epic: 33
legendary: 6
mythic: 1
The existing list is inconsistent even with regards to the mythic, as it removes the mythic from the legendaries, epics and uncommons, but not the rares. Personally I think the originally intended mythic logic should also be applied "all the way up". I appreciate that by purely using set logic with the definitions, then the mythic would be every sub-rarity too. However, coming from a CCG/TCG background, I don't think anyone would describe a rare trading card as also being uncommon/common according to set logic. On the ordinals.com sat pages, only the highest rarity is shown too (also with charms), e.g. there are only 27 sats displaying the epic tag/charm on ordinals.com.
Thanks :)

The figures at https://docs.ordinals.com/overview.html remain incorrect. Thanks

I agree with the premise here, higher rarities should not be included in the figures for lower rarities. Please feel free to open a PR!

Done, thanks :) https://github.com/ordinals/ord/pull/4152

Fixed in #4152


Python version

what is the python version used?

In the "enviroment.yml" it says on line 18:  python=3.6.13


Feature Request: More powerful parser

@squeaky-pl Thanks for this great library!
In flask you can do prefix match '/tree/{path:path}' to take in path strings with slashes in it. I'm trying to use this to parse file paths.
Would be great to have this as part of the route. If there is an easy way to override the default behavior that would be great too.

Hey guys, I found webargs! looks like this is what flask is using to parse url arguments.
https://github.com/sloria/webargs
i found it through this thread: https://github.com/flask-restful/flask-restful/issues/335#issuecomment-125264387


rtorrent-rutorrent : Error with filebot

I have an error with filebot but I don't why nor who to blame. This is the error:
cat /filebot/data/logs/amc.log
Fetch failed: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure [https://app.filebot.net/scripts/m1.jar.xz]
Received fatal alert: handshake_failure
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
        at net.filebot.web.WebRequest.fetch(WebRequest.java:143)
        at net.filebot.CachedResource.lambda$fetchIfModified$9(CachedResource.java:216)
        at net.filebot.CachedResource.lambda$null$0(CachedResource.java:87)
        at net.filebot.CachedResource.retry(CachedResource.java:120)
        at net.filebot.CachedResource.retry(CachedResource.java:132)
        at net.filebot.CachedResource.retry(CachedResource.java:132)
        at net.filebot.CachedResource.lambda$get$1(CachedResource.java:87)
        at net.filebot.Cache.computeIf(Cache.java:90)
        at net.filebot.CachedResource.get(CachedResource.java:82)
        at net.filebot.MemoizedResource.get(Resource.java:36)
        at net.filebot.cli.ScriptBundle.getScript(ScriptBundle.java:32)
        at net.filebot.cli.ScriptShell.runScript(ScriptShell.java:74)
        at net.filebot.cli.ArgumentProcessor.runScript(ArgumentProcessor.java:113)
        at net.filebot.cli.ArgumentProcessor.run(ArgumentProcessor.java:30)
        at net.filebot.Main.main(Main.java:120)
Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
        at net.filebot.web.WebRequest.fetch(WebRequest.java:140)
        ... 14 more

Failure (°_°)

Do you have an idea about this ?
Thanks

look like an libressl/openssl error

Probably! Stil dont't know how to resolve this yet

Try to add openssl and openssl-dev in dockerfile, the last dockefile is based on alpine 3.5 and use libressl instead of openssl ! I'm not sure but maybe filebot need openssl to get info from tvdb, moviedb .etc

Go idea, I'll try to rebuild with openssl and Alpine 3.4 to see if it's better or not.
Thanks.

you can also keep Alpine 3.5 just add openssl
it's available for alpine 3.5
https://pkgs.alpinelinux.org/packages?name=openssl*&branch=v3.5&repo=&arch=x86_64&maintainer=

I tried that first but I got an error.
ERROR: unsatisfiable constraints:
  libressl-dev-2.4.4-r0:
    conflicts:
               openssl-dev-1.0.2j-r2[pc:libcrypto=2.4.4]
               openssl-dev-1.0.2j-r2[pc:libssl=2.4.4]
               openssl-dev-1.0.2j-r2[pc:openssl=2.4.4]
    satisfies: libssh2-dev-1.7.0-r2[libressl-dev]
               libssh2-dev-1.7.0-r2[pc:libcrypto]
               libssh2-dev-1.7.0-r2[pc:libssl]
               curl-dev-7.52.1-r0[libressl-dev]
  openssl-dev-1.0.2j-r2:
    conflicts:
               libressl-dev-2.4.4-r0[pc:libcrypto=1.0.2j]
               libressl-dev-2.4.4-r0[pc:libssl=1.0.2j]
               libressl-dev-2.4.4-r0[pc:openssl=1.0.2j]
    satisfies: world[openssl-dev]
               libssh2-dev-1.7.0-r2[pc:libcrypto]
               libssh2-dev-1.7.0-r2[pc:libssl]

So I'm building it with Alpine 3.4 to see if I can get filebot back

Filebot works with Alpine 3.4 and openssl !
I can't build with Alpine 3.5 + openssl and libressl trigger an error with Java.
So I think the issue can remain open.
Thanks @ohmybside for pointing me the problem.

It's good now.
I replaced openjdk8-jre-8.111.14-r1 (from alpine:3.5) by openjdk8-jre-8.111.14-r0 (from alpine:3.4), no java error with filebot.
I will contact the maintainer of openjdk to know that they are the made changes between these two versions.

Great! Thank you very much :heart:

Issue alpine :
https://bugs.alpinelinux.org/issues/6704
and
https://bugs.alpinelinux.org/issues/6809

It works with latest version of openjdk.
I close this issue


operators [CI] tackle-operator (2.0.0-beta.0)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[x] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[x] Is your submission signed?
[x] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

@PhilipCattanach,@carlosthe19916,@m-brophy,@jonathanvila,@mrizzi , please approve

@fbladilo can you fix conflict?

@PhilipCattanach,@carlosthe19916,@m-brophy,@jonathanvila,@mrizzi , please approve

After https://github.com/k8s-operatorhub/community-operators/pull/1231 has been merged, we're expecting this PR to automerge once @fbladilo will merge latest main (which has to be done to fix the conflict).
In this way it will be proved the added owners works as expected with no need for manual approval, ensuring the new owners have full autonomy in PRs.

/merge possible

/merge possible