Render a set of items with dynamic row properties

I have a quick question about whether react-virtualized would fit our use case and, if so, what the best way to go about it would be.
We have a list of <Card/> components that looks like:

We want to virtualize this list as it's going to get rather large. Currently there is no conception of rows in the parent rendering component, it's just a large list and we rely on CSS to create rows. The "rows" also contain a dynamic number of cards (two cards on smaller viewports, one card on mobile).
The questions I have are:

Does react-virtualize require the data be split into discrete "rows" or is there a component/method that would allow us to virtualize this without augmenting our data structure?
How would you handle dynamic properties like card count per row? For example, when the user resizes the window from 1400px to 900px all rows should go from 3 cards to 2 cards.
For question 2 I though we might be able to set a rowCardCount variable in local state that updates on resize that we use the get a slice of the main list,  but would that affect already rendered rows?

Hey @Aweary! Welcome to the project. :)

Does react-virtualize require the data be split into discrete "rows" or is there a component/method that would allow us to virtualize this without augmenting our data structure?

All RV components require explicit row counts. That's an important part of how the windowing is done. But I think what you've described could work within that constraint.

How would you handle dynamic properties like card count per row? For example, when the user resizes the window from 1400px to 900px all rows should go from 3 cards to 2 cards.

You could use a high-order component like AutoSizer (or your own resize listener) to notify you of the available space for your list and then determine your row and column counts based on the size (similar to how you do with media queries).
If you have 1000 items and the current width is sufficient for 2 items per row then you have 500 rows. If it can fit 3 items per row then you have 334 rows. etc.

For question 2 I though we might be able to set a rowCardCount variable in local state that updates on resize that we use the get a slice of the main list, but would that affect already rendered rows?

Yes, any time the row-count changes the window of data is refreshed.
If your column widths aren't fixed- you may also want to consider using a Grid and ColumnSizer high-order component as is shown in this demo to help with the exact layout of each card/cell.

@Aweary I'm going to close this issue since it's just a question and I think I've provided the information you need. We can keep chatting here though if you still have questions. I don't mind. I just don't like leaving non-actionable issues open.

@bvaughn yeah totally :+1: I may have some more questions in the near future so I'll ping you here if I do. Thanks!

@aweary Hey! Did you manage to make it work? Cause I have a similar problem now.

@Pszek You might find this proof of concept helpful: http://plnkr.co/edit/zjCwNeRZ7XtmFp1PDBsc?p=preview

@bvaughn Thanks! I believe adding InfiniteLoader to that would be impossible (I mean the detection when to load more rows)?

@Pszek Should still be possible. Assuming you were doing something like the proof of concept I linked to, you'd just need to multiply the row indices InfiniteLoader provided by itemsPerRow to get the real range. (So if 4 items fit per row and InfiniteLoader tells you to load rows 100-110, you know that actually means loading items 400-440.)

@bvaughn  I know this is an old thread.
I had a doubt though as to how one would handle the size of the cards when the window resizes.
Like as @aweary had asked :

How would you handle dynamic properties like card count per row? For example, when the user resizes the window from 1400px to 900px all rows should go from 3 cards to 2 cards.

I would also like to add that when the cards go from 3 to 2, the dimensions of the card also usually change to enable responsiveness. How can I handle this?
Please let me know if I wasn't clear enough.

@SevenSinS02 do you have a working example of what you did? I'm trying to implement this in a website with a responsive grid and I'm having trouble.


Allow systems to return results

Objective
When writing an app in rust, the main function usually returns nothing, but it can also return a Result; when doing this, returning an Err value will result in a panic. This makes writing fallible code much more ergonomic, since ? can be used to propagate errors.
This flexibility should be extended to systems: users should be able to return a Result from their systems. This can be done by calling system.pipe(unwrap) when adding the system, however this approach requires more boilerplate, incurs a runtime overhead due to the PipeSystem, removes context from the error message (since the panic message has no way of accessing the system's name), and makes the name of the combined system messier (which is stored by allocating a new String).
Solution
A system can only be added to a schedule if it implements IntoSystemConfigs<>. Currently, this is only implemented for systems that take no input and return nothing. Now, this trait is also implemented for any systems that return Result<(), impl Debug>. A custom system adapter is used that panics when the system returns an error and includes the system name in the message.
Initially, I was concerned that this may make the compile error for systems with invalid return types more confusing. However in my testing, the error message does not seem to be any worse.

Changelog

Systems may now return values of type Result<(), E>, where E is any type that implements std::fmt::Debug.

I'm closing this out. Using ? for errors like this is convenient and pretty when writing code, but I find that it makes the debugging experience worse when something goes wrong, since the error message points to the location where the error was reported rather than where it was produced -- using .unwrap() is actually much nicer here.
If anyone finds a way of improving the panic message reporting, feel free to make a new PR based off of this.


TILA-1818 | Add django celery beat and worker pod conf to entrypoint

Adds django celery beat to project and makes use of it enrypoint script.
TILA-1818

Exciting stuff! Remember to update visualizations. The test seems to be failing relaxed

oh yes, the django-celery-beat has some migrations :+1:


Added page "how to debug"

Awaiting my enhancement about the crash popup, still WIP. I'll continue this page right after it's done.


[docs] Inconsistencies between  Creating an Update Channel-Target Groups  doc and actual behaviour

Currently in the  Creating an Update Channel section of managed-ota-updates page the Target Groups is declared as an optional field, but in the Fronted page (/update-channels/new) of Edgehog Create Update Channel the field is declared as Required

See also the discussion about at least one target group being required or not: #518


Fix the lower bound for some signed integer types

Some of the lower bounds were missing their negative sign

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

#sign-off


Issue 1

I have tested the partner route and it seems to be working. Let me know if I am going in the right direction. Thanks!

add node_modules to your .gitignore file (research and update git ignore for a typescript project)
I'm not familiar with ts-express, I guess I should read up some on it. I believe that routes in express will be equivalent to handlers in go-gorilla - so this looks good to me. Do you still need to serve up / from app.ts?
not quite setup to clone and run locally so this is just a visual review


setup CI

There are already some tests available (codestyle, phan, php-stan, unit), so we should run them in CI

I suggest to take a copy of https://github.com/owncloud/activity/blob/master/.drone.star
Delete all the not-relevant sections (acceptance tests etc) and keep the sections for code-style, phan, phpstan, phptests (unit and integration are options in the same phptests function).
Then enable the code-style, phan, phpstan and phpunit in the config section.
That should get CI running for all the test pipelines that we have so far.

fixed by #11


Remove some Undefined Behavior

It's UB to specialize std::ostream's operator<< on std::vector and std::pair.
Replace uses of it in tests with GoogleTest's ::testing::PrintToString()
While we're at it, remove an unnecessariy opening of namespace std for specializing std::hash on Envoy::HashedValue. This is okay, but we can do it without opening the namespace.
Risk Level: low
Testing: CI

This UB is one of the roadblocks for updating our Abseil dependency.

Over to Ryan for senior maintainer stamp


feat: extract subviews on extension

I found that settings view was really big, so I decided to extract them on method returning some View for a better readability.
If you have any feedback do not hesitate to reach me or comment the PR.
I think we can have a better naming for methods but I am not much inspired now

This is a great idea! I'd be curious why these can't be pulled out to separate views entirely, rather than leaving them as methods.

This is a great idea! I'd be curious why these can't be pulled out to separate views entirely, rather than leaving them as methods.

I have used methods that return views because what they do is quite explicit. This limits the number of files and previews to be added in addition to putting fewer lines to the file.
If it's better for the project, I can use structs to keep the homogeneity of the app

Once we move over to @Observable (when macOS 15 is likely to be released around October), it's more efficient to create smaller views than one big one, even when methods are involved. So, let's plan ahead, just like we're moving towards Swift 6 already 🙂

Yeah for sure we can take advances, the problem with my extension of the view is the coupling of subview with the main view, I think it's better to use separate view entirely.
I'll make the changes soon 🔜

This works as expected, if you see some improvements do not hesitate to told me @twostraws
https://github.com/twostraws/ControlRoom/assets/63256761/560978ef-870f-4b68-be89-d1c86aa2e7ae

This is perfect – thank you!


Global variable workflow.duration cannot be resolved in exit handler during validation

Summary
What happened/what you expected to happen?
We are trying to use the global variable workflow.duration from a template that is part of an exit handler, but we are seeing a validation error when creating the workflow template.  If we skip the validation via kubectl, it apparently works.
I've also created a PR with a potential fix for this issue: https://github.com/argoproj/argo-workflows/pull/5483
Diagnostics
What version of Argo Workflows are you running?
v2.12.4
apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
metadata:
  name: exit-handlers-234
spec:
  entrypoint: intentional-fail
  onExit: exit-handler
  templates:
  - name: intentional-fail
    container:
      image: alpine:latest
      command: [sh, -c]
      args: ["echo intentional failure; exit 1"]

  - name: exit-handler
    steps:
    - - name: notify
        arguments:
          parameters:
            - name: wfDuration
              value: "{{workflow.duration}}"
        template: send-email
        when: "{{workflow.status}} == Succeeded"

  - name: send-email
    inputs:
      parameters:
        - name: wfDuration
    container:
      image: alpine:latest
      command: [sh, -c]
      args: ["echo send e-mail: {{workflow.name}} {{inputs.parameters.wfDuration}}"]

If we attempt to create a workflow template from this YAML file, we get the following error message.
argo template create wf.yaml -n argo
ERRO[2021-03-22T18:10:38.424Z] Error in file wf.yaml: templates.exit-handler.steps failed to resolve {{workflow.duration}}
FATA[2021-03-22T18:10:38.424Z] Errors encountered in validation

If we skip the validation, it apparently works as expected:
kubectl apply -f wf.yaml -n argo
argo submit --from workflowtemplate/exit-handlers-234 -n argo

Name:                exit-handlers-234-mzmwf
Namespace:           argo
ServiceAccount:      default
Status:              Pending
Created:             Mon Mar 22 18:18:39 +0100 (now)
Progress:

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Hi still having this issue. Any updates?

still doesn't work,
let me make a PR for this

FWIW, it seems this issue only occurs if the workflow is created via the UI. If I put {{workflow.duration}} in a wf template and then launch a workflow with the template, it would work fine


fix: remove postgresql user default

Description
Fixes FL-1586
How has this been tested?

Checklist

[ ] changelog was updated with notable changes
[ ] documentation was updated

/e2e

End to end tests: :hourglass_flowing_sand: STARTING

/e2e


implement bin_patricia_hashed trie

Code is moved to another branch with huge differences with previous version, so decided to recreate pr.

got an issue when trying to start from block 1M (flag --block)
create aggregator: rebuilding recent state from change files: aggregateToBtree prevTx: inconsistent tx iteration

commitment files
bin  2.7M blocks: dat 374M idx 7.5M
hex  3M   blocks: dat 300M idx 19M


Trouble disabling ng-idle

I'm trying to disable ng idle doing
app.config(['IdleProvider', function(IdleProvider) {
IdleProvider.keepalive(false);
IdleProvider.timeout(false);
    }]);

    // assume myApp was defined according to the "Configure" example above
    app.run(['Idle', function(Idle) {
        Idle.unwatch();
    }]);

But this isnt wprking.. Is there a way to do this?

I think I'm missing some piece of information. config and run are only executed once, when your application starts. So here you've effectively told it to turn off keepalive and timeout, and when it runs, you tell it to stop watching even though you never told it to start watching. Ng-Idle does not automatically start by default, so I'm not sure what the problem you're experiencing is.


OLS-227: add E2E test

Description
End to end tests consist of reconciliation test and the TLS settings verification.
Please have a look on this PR on liveness and readiness probes, too. The retry of portforwarding in TLS tests can be reduced to a single forward in the test setup if we have the readiness probe.
Type of change

[ ] Refactor
[x] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #
Closes # OLS-227

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] PR has passed all pre-merge test jobs.
[x] If it is a core feature, I have added thorough tests.

Testing

Have a running Openshift cluster.
Run the operator make deploy
Set these 2 environment variables:

$KUBECONFIG - the path to the config file of kubenetes client
$LLM_TOKEN - the access token given by the LLM provider, here we use OpenAI for testing.

run the e2e test make test-e2e

The output should looks like this
➜  lightspeed-operator git:(e2e-test) ✗ make test-e2e
go test ./test/e2e  -ginkgo.v -ginkgo.progress -test.v
=== RUN   TestE2E
Running Suite: End-to-End Suite - /home/hsun/lightspeed-operator/test/e2e
=========================================================================
Random Seed:<PHONE_NUMBER>

Will run 6 of 6 specs
------------------------------
[BeforeSuite]
/home/hsun/lightspeed-operator/test/e2e/suite_test.go:24
  STEP: Check the operator is ready @ 03/27/24 10:30:51.107
  STEP: Create 2 LLM token secrets @ 03/27/24 10:30:51.533
[BeforeSuite] PASSED [0.724 seconds]
------------------------------
TLS activation should activate TLS on service HTTPS port
/home/hsun/lightspeed-operator/test/e2e/tls_test.go:47
  STEP: Creating a OLSConfig CR @ 03/27/24 10:30:51.83
  STEP: wait for application server deployment rollout @ 03/27/24 10:30:52.03
  STEP: Wait for the application service created @ 03/27/24 10:30:57.126
  STEP: check the secret holding TLS ceritificates is created @ 03/27/24 10:30:57.221
  STEP: check the deploy has the certificate secret mounted @ 03/27/24 10:30:57.316
  STEP: check HTTPS connection on forwarded port @ 03/27/24 10:30:57.316
  STEP: Forward the HTTPS port to a local port @ 03/27/24 10:30:57.316
  STEP: send HTTPS request to forwared port @ 03/27/24 10:30:58.34
  2024-03-27T10:30:58+01:00     INFO    E0327 10:30:58.534694  105258 portforward.go:409] an error occurred forwarding 33075 -> 8443: error forwarding port 8443 to pod e43054f3493d37acc3395ef58ae95543c22b07093044029757c5f344895954d1, uid : port forward into network namespace "/var/run/netns/f036d519-9f05-4d8c-98f3-2e95fd7cda41": failed to connect to localhost:8443 inside namespace e43054f3493d37acc3395ef58ae95543c22b07093044029757c5f344895954d1: dial tcp [::1]:8443: connect: connection refused
  2024-03-27T10:30:58+01:00     INFO    error: lost connection to pod
  STEP: Forward the HTTPS port to a local port @ 03/27/24 10:31:02.319
  STEP: send HTTPS request to forwared port @ 03/27/24 10:31:03.358
  2024-03-27T10:31:03+01:00     INFO    E0327 10:31:03.550317  105381 portforward.go:409] an error occurred forwarding 33319 -> 8443: error forwarding port 8443 to pod e43054f3493d37acc3395ef58ae95543c22b07093044029757c5f344895954d1, uid : port forward into network namespace "/var/run/netns/f036d519-9f05-4d8c-98f3-2e95fd7cda41": failed to connect to localhost:8443 inside namespace e43054f3493d37acc3395ef58ae95543c22b07093044029757c5f344895954d1: dial tcp [::1]:8443: connect: connection refused
  2024-03-27T10:31:03+01:00     INFO    error: lost connection to pod
  STEP: Forward the HTTPS port to a local port @ 03/27/24 10:31:07.32
  STEP: send HTTPS request to forwared port @ 03/27/24 10:31:08.363
  2024-03-27T10:31:08+01:00     INFO    E0327 10:31:08.557925  105480 portforward.go:409] an error occurred forwarding 45261 -> 8443: error forwarding port 8443 to pod e43054f3493d37acc3395ef58ae95543c22b07093044029757c5f344895954d1, uid : port forward into network namespace "/var/run/netns/f036d519-9f05-4d8c-98f3-2e95fd7cda41": failed to connect to localhost:8443 inside namespace e43054f3493d37acc3395ef58ae95543c22b07093044029757c5f344895954d1: dial tcp [::1]:8443: connect: connection refused
  2024-03-27T10:31:08+01:00     INFO    error: lost connection to pod
  STEP: Forward the HTTPS port to a local port @ 03/27/24 10:31:12.32
  STEP: send HTTPS request to forwared port @ 03/27/24 10:31:13.327
  2024-03-27T10:31:13+01:00     INFO    E0327 10:31:13.523750  105550 portforward.go:409] an error occurred forwarding 41221 -> 8443: error forwarding port 8443 to pod e43054f3493d37acc3395ef58ae95543c22b07093044029757c5f344895954d1, uid : port forward into network namespace "/var/run/netns/f036d519-9f05-4d8c-98f3-2e95fd7cda41": failed to connect to localhost:8443 inside namespace e43054f3493d37acc3395ef58ae95543c22b07093044029757c5f344895954d1: dial tcp [::1]:8443: connect: connection refused
  2024-03-27T10:31:13+01:00     INFO    error: lost connection to pod
  STEP: Forward the HTTPS port to a local port @ 03/27/24 10:31:17.32
  STEP: send HTTPS request to forwared port @ 03/27/24 10:31:18.336
  2024-03-27T10:31:18+01:00     INFO    E0327 10:31:18.527997  105614 portforward.go:409] an error occurred forwarding 46655 -> 8443: error forwarding port 8443 to pod e43054f3493d37acc3395ef58ae95543c22b07093044029757c5f344895954d1, uid : port forward into network namespace "/var/run/netns/f036d519-9f05-4d8c-98f3-2e95fd7cda41": failed to connect to localhost:8443 inside namespace e43054f3493d37acc3395ef58ae95543c22b07093044029757c5f344895954d1: dial tcp [::1]:8443: connect: connection refused
  2024-03-27T10:31:18+01:00     INFO    error: lost connection to pod
  STEP: Forward the HTTPS port to a local port @ 03/27/24 10:31:22.317
  STEP: send HTTPS request to forwared port @ 03/27/24 10:31:23.342
  2024-03-27T10:31:23+01:00     INFO    E0327 10:31:23.536492  105733 portforward.go:409] an error occurred forwarding 41177 -> 8443: error forwarding port 8443 to pod e43054f3493d37acc3395ef58ae95543c22b07093044029757c5f344895954d1, uid : port forward into network namespace "/var/run/netns/f036d519-9f05-4d8c-98f3-2e95fd7cda41": failed to connect to localhost:8443 inside namespace e43054f3493d37acc3395ef58ae95543c22b07093044029757c5f344895954d1: dial tcp [::1]:8443: connect: connection refused
  2024-03-27T10:31:23+01:00     INFO    error: lost connection to pod
  STEP: Forward the HTTPS port to a local port @ 03/27/24 10:31:27.32
  STEP: send HTTPS request to forwared port @ 03/27/24 10:31:28.348
  2024-03-27T10:31:28+01:00     INFO    E0327 10:31:28.546397  105803 portforward.go:409] an error occurred forwarding 40359 -> 8443: error forwarding port 8443 to pod d9e07af5d6511c680a79e2c71ab7f1f600d554742837b3e6445b17cb9a4d5de2, uid : port forward into network namespace "/var/run/netns/820e2497-9842-493e-bd0b-6503152a80eb": failed to connect to localhost:8443 inside namespace d9e07af5d6511c680a79e2c71ab7f1f600d554742837b3e6445b17cb9a4d5de2: dial tcp [::1]:8443: connect: connection refused
  2024-03-27T10:31:28+01:00     INFO    error: lost connection to pod
  STEP: Forward the HTTPS port to a local port @ 03/27/24 10:31:32.32
  STEP: send HTTPS request to forwared port @ 03/27/24 10:31:33.235
  STEP: Deleting the OLSConfig CR @ 03/27/24 10:31:33.652
• [41.921 seconds]
------------------------------
Reconciliation From OLSConfig CR should setup application server
/home/hsun/lightspeed-operator/test/e2e/reconciliation_test.go:41
  STEP: Creating a OLSConfig CR @ 03/27/24 10:31:33.751
  STEP: make application server deployment running @ 03/27/24 10:31:33.856
  STEP: exposing its HTTPS port in a service @ 03/27/24 10:31:38.953
• [5.301 seconds]
------------------------------
Reconciliation From OLSConfig CR should setup console plugin
/home/hsun/lightspeed-operator/test/e2e/reconciliation_test.go:71
  STEP: make console plugin deployment running @ 03/27/24 10:31:39.052
  STEP: exposing its HTTPS port in a service @ 03/27/24 10:31:39.149
• [0.204 seconds]
------------------------------
Reconciliation From OLSConfig CR should setup a cache
/home/hsun/lightspeed-operator/test/e2e/reconciliation_test.go:100
• [0.000 seconds]
------------------------------
Reconciliation From OLSConfig CR should reconcile app deployment after changing deployment settings
/home/hsun/lightspeed-operator/test/e2e/reconciliation_test.go:104
  STEP: update the replica number in the OLSConfig CR @ 03/27/24 10:31:39.256
  STEP: check the replica number of the deployment that should be updated @ 03/27/24 10:31:39.361
• [5.222 seconds]
------------------------------
Reconciliation From OLSConfig CR should reconcile app configmap after changing application settings
/home/hsun/lightspeed-operator/test/e2e/reconciliation_test.go:124
  STEP: fetch the app deployment generation @ 03/27/24 10:31:44.478
  STEP: update LogLevel in the OLSConfig CR @ 03/27/24 10:31:44.574
  STEP: wait for the app configmap to be updated @ 03/27/24 10:31:44.674
  STEP: check the app deployment generation that should be inscreased @ 03/27/24 10:31:44.781
  STEP: update models in the OLSConfig CR @ 03/27/24 10:32:04.882
  STEP: wait for the app configmap to be updated @ 03/27/24 10:32:04.985
  STEP: check the app deployment generation that should be inscreased @ 03/27/24 10:32:05.081
  STEP: change LLM token secret reference @ 03/27/24 10:32:15.187
  STEP: check the app deployment generation that should be inscreased @ 03/27/24 10:32:15.286
  STEP: check the app configmap to contain the new secret volume @ 03/27/24 10:32:25.385
  STEP: check the deployment to mounted the new secret volume @ 03/27/24 10:32:25.498
  STEP: Deleting the OLSConfig CR @ 03/27/24 10:32:25.498
• [41.122 seconds]
------------------------------
[AfterSuite]
/home/hsun/lightspeed-operator/test/e2e/suite_test.go:68
  STEP: Delete the 2 LLM token Secrets @ 03/27/24 10:32:25.6
[AfterSuite] PASSED [0.199 seconds]
------------------------------

Ran 6 of 6 Specs in 94.693 seconds
SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 0 Skipped
You're using deprecated Ginkgo functionality:
=============================================
  --ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=2.13.0

--- PASS: TestE2E (94.69s)
PASS
ok      github.com/openshift/lightspeed-operator/test/e2e       94.703s

@raptorsun Please remove the personal Paths in the configs. LGTM . Will merge once the path is fixed.

@raptorsun Please remove the personal Paths in the configs. LGTM . Will merge once the path is fixed.

Thank you ! readme file updated and new commit pushed for review :)

/test bundle-e2e

/test bundle-e2e

/lgtm
/approve

/test bundle-e2e

/retest-required

/retest-required

/retest-required

/retest-required

/retest-required

/retest-required

/retest

/test all

/retest-required


predictionOptions.slot cannot bind to settings

i want to bind preditionOptions.slot to primary appsetting.config, as following:
{
  "$kind": "Microsoft.LuisRecognizer",
  "id": "LUIS_IvrBot",
  "applicationId": "=settings.luis.IvrBot_en_us_lu.appId",
  "version": "=settings.luis.IvrBot_en_us_lu.version",
  "endpoint": "=settings.luis.endpoint",
  "endpointKey": "=settings.luis.endpointKey",
  "predictionOptions": {
    "includeAPIResults": true,
    "slot": "=settings.luis.slot"
  }
}

but it seems do not work. when i check source code, i found that slot is evaluated with dialogContext. (in LuisAdaptiveRecognizer.cs)
options.Slot = this.Options.Slot?.GetValue(dialogContext);
it seems it need to evaluate with dialogContext.State to make it work, as version did.
options.Version = this.Version?.GetValue(dialogContext.State);

Hi @kino-song
Is this a Composer bot? If so, what version? If an SDK bot, what version of the SDK are you using? Is this based off of a Sample?

I am using bot composer v2.1.2, bot sdk was 4.14.1 (generated by bot composer by default),
then i tried to upgrade sdk to 4.15.2, still have the same issue.

Hi @kino-song
Is this a Composer bot? If so, what version? If an SDK bot, what version of the SDK are you using? Is this based off of a Sample?

I am using bot composer v2.1.2, bot sdk was 4.14.1 (generated by bot composer by default),
Then I tried to upgrade sdk to 4.15.2, still have the same issue.

Hi @kino-song Thank you. I was able to reproduce your findings and am currently investigating further.

Closing as PR has been submitted. If approved, it will be included in some future build. Thank you for your contribution.


PowerToys Run not working wherever the shortcuts keys is

PowerToys Run not working wherever the shortcuts keys is
Acer V Nitro Black Edition

PowerToys version: v0.33.1
PowerToy Utility: PowerToys Run
Running PowerToys as Admin: Yes and No
Windows build number: 19043.844

1.I tried to Run  Power App as administrator and none Administrator too
2. I changed the shortcuts multiple times to check
All Powertoys utilities are working perfectly only "PowerToys Run"

@Gkhadra
if you open the Task Manager -> Details do you see the PowerLauncher.exe process running?

@enricogior
Because the plugin list is empty (see screenshot) I think that PowerLauncher.exe isn't running.
(Note: Plugins get initialized on first start of PT Run's process.)

@htcfreek
I turned off all the plugins and the search box still shows up.
@Gkhadra
can you clarify if the search box doesn't show up or if it shows up and it doesn't return any result?
If you restart PowerToys, the Settings page still doesn't show any plugin available?

@htcfreek
I turned off all the plugins and the search box still shows up.

This is an expected behavior.
What I mean in the case of the issue is:

Pressing the shortcut doesn't shows search bar. (As I understand the issue.)
In settings the plugin list is empty. The list is written to Run's settings.json on starting/by the PT Run process. (Seems to not happened.)
=> These two points let me think that PowerLauncher.exe isn't running (correctly).

@htcfreek
OK, agreed. I thought you meant the other way around: PowerLauncher.exe isn't running because the plugin list is empty.

From https://github.com/microsoft/PowerToys/issues/9431#issuecomment-793264021

That the PowerToys Run feature immediately turned off after the update (on regular user) and the "Plugins" were not listed, so at first glance, I basically don't know why is it turned off (and always turned itself off if I tried to turn it on) and can't see what the Plugins should show.
And I think after I log-off from the regular user and log-in to the administrator account, and turn on the feature there (PT Run is still functional there) and back into the regular user account, I can see the Plugins list content after that, but still unable to turn on the feature (keep turning it off immediately)

@Gkhadra
if you open the Task Manager -> Details do you see the PowerLauncher.exe process running?

You mean PowerToys.exe

@htcfreek
I turned off all the plugins and the search box still shows up.
@Gkhadra
can you clarify if the search box doesn't show up or if it shows up and it doesn't return any result?
If you restart PowerToys, the Settings page still doesn't show any plugin available?

Yes the search box doesn't show up at all
I noticed too that each time i need to open the power toys settings and Enable "PowerToys Run" when i restart or turn on my laptop.
however even if i enable this tools still not working "the menu not showing up" when I press the predefined shortcuts

@Gkhadra
if you open the Task Manager -> Details do you see the PowerLauncher.exe process running?

You mean PowerToys.exe
PowerLauncher.exe not showing up as i assume only PowerToys.exe

@Gkhadra
if you open the Task Manager -> Details do you see the PowerLauncher.exe process running?

You mean PowerToys.exe
PowerLauncher.exe not showing up as i assume only PowerToys.exe

No we mean PowerLauncher.exe which is the Program file for PT Run.


Error : Not compatible with this version of Home Assistant

What version of Music Assistant has the issue?
2022.8.0 BETA 2
The problem
Hello, newest PreRelease unfortunatly is not compatible with:
Version | core-2022.7.7
Installationstyp | Home Assistant Supervised
How to reproduce
Integration is not starting. Showing Error: Not compatible with this version of Home Assistant
Relevant log output
No response
Additional information
No response
What version of Home Assistant Core are your running
Home Assistant 2022.7.7
What type of installation are you running?
Home Assistant Supervised
On what type of hardware are you running?
Linux

Look at the version number of Music Assistant 2022.8.x BETA
Is it perhaps compatible with Home Assistant 2022.8 BETA ?
To resolve, you either upgrade Home Assistant to 2022.8 (beta is in final stage now, release is tomorrow) OR you downgrade Music Assistant to the latest 2022.7 stable version. There's an option hidden in HACS called "reinstall" which will let you pick the version to install.


Reverse mail order option

Would anyone be interested in providing an option so that the correspondence in emails is instead reverse with newest appearing on top. Currently it is the other way around. What I am thinking is more like what you see in the outlook.com web interface.

Looking more into it, it seems to be fairly easy to make this change (assuming that interface functionality is not lost). I'll make so that there will be an option in general so that users can change their preferred order DESC or ASC in viewing messages. I have a few things on my plate so it may take a while.

#21

#25 updated pull request


SSD

您好，请问有SSD的提升效果的表格吗

Hi, currently I dont have ssd results

你好，我想问下那个resnet50-h是通道数为一半的resnet50而不是float16的resnet50？
---Original---
From<EMAIL_ADDRESS>Date: Fri, Jun 14, 2019 18:11 PM
To<EMAIL_ADDRESS>Cc: "Author"author<EMAIL_ADDRESS>Subject: Re: [twangnh/Distilling-Object-Detectors] SSD (#2)
Hi, currently I dont have ssd results
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

the resnet50-h is obtained with halving each layer's channel number of resnet50

谢谢，还有一个问题您的论文中frcnn使用的是roipooling还是roialign？因为我在做过实验室roipooling和roipooling差别很大的。
---Original---
From<EMAIL_ADDRESS>Date: Wed, Jun 19, 2019 11:01 AM
To<EMAIL_ADDRESS>Cc: "Author"author<EMAIL_ADDRESS>Subject: Re: [twangnh/Distilling-Object-Detectors] SSD (#2)
the resnet50-h is obtained with halving each layer's channel number of resnet50
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

roialign is used in the experiments

I have seen your project on github, it is interesting that roialign and roipooling have so large difference on distillation results, do you have any update for the issue?

你可以用gluoncv去做下实验，差别很大。
---Original---
From<EMAIL_ADDRESS>Date: Tue, Jun 25, 2019 12:49 PM
To<EMAIL_ADDRESS>Cc: "Author"author<EMAIL_ADDRESS>Subject: Re: [twangnh/Distilling-Object-Detectors] SSD (#2)
I have seen your project on github, it is interesting that roialign and roipooling have so large difference on distillation results, do you have any update for the issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

你可以用gluoncv去做下实验，差别很大。
…

我想问一下您复现的Fine Grained feature imitation实验中roi Align和roi pooling效果会差多少？论文中roi Align提升约2.9%，那么如果是roi pooling大约提升多少呢？

看他github的
---Original---
From<EMAIL_ADDRESS>Date: Wed, Mar 18, 2020 14:51 PM
To<EMAIL_ADDRESS>Cc: "Author"<author<EMAIL_ADDRESS>Subject: Re: [twangnh/Distilling-Object-Detectors] SSD (#2)
你可以用gluoncv去做下实验，差别很大。
…
我想问一下您复现的Fine Grained feature imitation实验中roi Align和roi pooling效果会差多少？论文中roi Align提升约2.9%，那么如果是roi pooling大约提升多少呢？
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

看他github的
…
---Original---
From<EMAIL_ADDRESS>Date: Wed, Mar 18, 2020 14:51 PM
To<EMAIL_ADDRESS>Cc: "Author"<author<EMAIL_ADDRESS>Subject: Re: [twangnh/Distilling-Object-Detectors] SSD (#2)
你可以用gluoncv去做下实验，差别很大。
…
我想问一下您复现的Fine Grained feature imitation实验中roi Align和roi pooling效果会差多少？论文中roi Align提升约2.9%，那么如果是roi pooling大约提升多少呢？
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

哪里可以看到数据对比呢，我看您的GAN-KD论文里也没有Fine Grained feature imitation方法的roi align和roi pooling的对比，我最近尝试了带fpn的faster rcnn应用Fine Grained feature imitation方法，用的roi pooling，但是发现蒸馏后的结果比学生的基线还低，所以比较困惑，请问您那边实验的结果是什么样的呢？roi pooling会有提升吗？


Suppress detailed responses for security-sensitive (PCI-DSS) environments

Before this PR, Kafka Connect's exception mapper would print an unchecked messages from unhandled stack traces. I am contributing this code change so that the community has the option to change this behavior based on a configuration option, "error.rest.response.message.detail.enabled"
As this functionality is an API-level change, as it changes the response of handled errors, it should not be enabled by default. I have provided a unit test for handling the expected response if the option is enabled.

Issue: https://issues.apache.org/jira/browse/KAFKA-9766


time_sampler = ts.TimeSampler(stop_time=20)

import TimeSynth as ts
time_sampler = ts.TimeSampler(stop_time=20)

gives error:
AttributeError: module 'TimeSynth' has no attribute 'TimeSampler'

The build is passing. Are you using Python 3.5 or higher?


Deprecated lifecycles

Removed all instances of componentWillMount and componentWillReceiveProps
For the most part, cWM was changed to cDM, except in cases where a parent's function needed to be run before a child's, so those were moved into the constructor. (see Router.js as an example).
cWRP was replaced with componentDidUpdate. In one case where infinite loops could happen, I added an equality check to stop that. (see Route.js).
Updated all documentation and examples to remove the old lifecycles and use their supported counterparts.
It appears that I'm the first person to change many of these files after the addition of prettier as a git hook. Many changes, such as adding ; and changing single to double quotes ", appear to be a result of that.
Tests all pass. I linked this updated code to one of my projects and it appears to all work the same as before, but I only use pretty basic RR-dom components and it's not exhaustive.
Hopefully resolves #6060 and is a more robust version of #6256

@timdorr just checking in to see if there's anything else preventing this from merging?

Michael let me know he's planning on giving Router his full attention over the coming week, so I expect it will make its way in somehow!

Thanks for the PR, @frehner :)
I did some major refactoring over the past week and eliminated all the deprecated componentWill methods in the process, so we won't need this anymore. You can see some of my commits here and here.
My apologies for not guiding you through this work so we could get this merged, but it was a little tricky and I wanted to make sure I understood all of the implications of making this change, so I decided to do it myself. You can expect this to be published in our next beta release sometime this week. 😅

No worries, just glad to see it done! Thanks!


Change the processing of preprocessors

At the moment, they way we execute a preprocessor chain goes something like this:
def run(source_file, [preprocessor | remaining_preprocessors]) do
  preprocessor.run(source_file)
  |> run(remaining_preprocessors)
end

We execute one after the other, using the output of one as the input of the next.
This has two relevant limitations: a preprocessor cannot stop the execution of the chain, a preprocessor cannot execute after the remaining preprocessor. The profiler could be a preprocessor that stores the current time, calls the remaining preprocessor, and then calculates the diff. The pass-through copy could be a preprocessor that checks whether a file is eligible for copy and if it is, stops the chain right there. There are many more use cases for such functionality.
With this change, we rewrite the internals of Preprocessor so that each preprocessor calls the next. This change doesn't affect the existing API, instead, it extends it.

This feels like a very Javascript-y way to do thinks. It also feels error prone when adding custom preprocessors having to make that call every time.
Wouldn't it be better to return either {:ok, value} | {:error, reason}? Or, if you want to allow preprocessors to stop without having to idiomatically call it an error, {:cont, value}, {:halt, value} (which is already used in Elixir, for example, in Stream.chunk_while/4, among others)

I don't think I've written something like this in JavaScript, but to be honest, I don't think that matters, the discussion mostly about which API is better to support this functionality.
The difference between this API and the one you're suggesting is that this one can run code after the next preprocessors terminate. To achieve the same thing with an API like the one you're suggesting we would need callbacks, which is what plug does. I'm fine with that approach, but it's more complicated because you need another process to store the callbacks and run them in the end. With don't need any of that with this approach, it just functions calling other functions. Maybe it's error-prone, but that's for the advanced use case, where you actually want to have that control, you don't have to use it.

@frm after some of our conversations, I updated everything :P let me know what you think


feature: add GetHTTPPath function for cdn mgr

Signed-off-by: Starnop<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #563 into master will decrease coverage by 0.04%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #563      +/-   ##
==========================================
- Coverage   49.72%   49.67%   -0.05%
==========================================
  Files          95       95
  Lines        5213     5218       +5
==========================================
  Hits         2592     2592
- Misses       2428     2433       +5
  Partials      193      193

Impacted Files
Coverage Δ

supernode/daemon/mgr/cdn/manager.go
15.38% <0%> (-0.9%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e8f36c8...f04bc20. Read the comment docs.


Pass env with build info to docker container

CI build ID
CI build Interval
CI build item ID

This will allow having multiple CI builds running the same code, but in .shoov.yml we can execute different tests (e.g. Behat every 3 min, and visual regression testing every 1 hour)

Could you please add some more explanation for this?


Daily Question screen in the app

[ ] Design Daily Question UI
[ ] Build Xamarin view

@lukecookssw @matt-goldman

Design Daily Question UI

Done - Please find the new frames here: https://zpl.io/JEnDY7x

@lukecookssw @matt-goldman

Design Daily Question UI

Done - Please find the new frames here: https://zpl.io/JEnDY7x

This looks awesome, thanks! One question, should this be pinned or scroll with the rest of the quizzes?

@lukecookssw @matt-goldman
This looks awesome, thanks! One question, should this be pinned or scroll with the rest of the quizzes?

I think it should always be the first item in the list but scroll with the rest of them.


Devhub Issue: Typography [short description here]

path: (do not delete) https://github.com/bcgov/design-system/blob/master/styles/typography/typography.md
(do not delete) devhub page: /Typography

Devhub Content Issue
Are there plans to support more font weights in BC Sans? Is this in progress?
Just Bold and Regular can be slightly limiting.

We only have plans to support bold and regular at this time. This is primarily due to performance having to load additional weights. Light versions of fonts should be avoided for accessibility.


Bug in preview : missing service or alias

Hi,
I've just upgraded to 2.0 and I've got an error when I preview a block

Maybe all these resolver services need a public : true declaration in resolver.yml ?

Best regards,
David

Hi. Thanks for reporting the bug. 2.0 is not stable yet, we will release a tested version soon.

Should be fixed in #773fabd.


haskellPackages.tar: disable tests

They fail on i686-linux: http://hydra.nixos.org/build/25088435/nixlog/2
This should fix the build for several transitive dependencies, notably including darcs.

Would you mind reporting that error upstream so that the author has a chance to fix it?

@dcoutts, are you aware of the test suite failures of tar that we see in http://hydra.nixos.org/build/25088435/nixlog/2?


Plugin breaks gutenberg for custom post type

select( 'core/editor' ).getEditedPostAttribute( 'meta' ) will return undefined, for post types that register without support for custom-fields.

@mougias thanks for the feedback. We can replicate and confirm this is now a known issue.
This issue also affects reusable Gutenberg blocks so it's now a high priority to find a resolution for this.

@mougias thanks for the feedback. We can replicate and confirm this is now a known issue.
This issue also affects reusable Gutenberg blocks so it's now a high priority to find a resolution for this.

Any progress on this? Looking forward to taking this plugin for a "ride".

This issue was fixed by https://github.com/coilhq/coil-wordpress-plugin/pull/42


Wrong line numbers reported for errors

I am getting seemingly wrong line numbers reported by karma:
Expected false to be truthy.
  at Object.<anonymous> (/Users/dmitrizaitsev/Repos/lodash-tests/tests/round_test.js:128:35)
Expected Function to be 0.1.
  at Object.<anonymous> (/Users/dmitrizaitsev/Repos/lodash-tests/tests/round_test.js:129:31)

where in fact the error generating lines are 82 and 83:
// round_test.js
...
line 82:  expect(isFinite(roundCurried)).toBeTruthy()
line 83:  expect(roundCurried(0.13)).toBe(0.1)

Here are the lines from my karma.conf.js:
...
 files: [
    'tests/**/*.js'
 ],
 preprocessors: {
   'tests/**/*.js': ['webpack']
 },

This is the repo to reproduce the mismatch:
https://github.com/dmitriz/lodash-tests/tree/number-mismatch

Per the README, have you tried adding the webpack preprocessor?
preprocessors: {
    'tests/**/*.js': ['webpack', 'sourcemap']
},

Even though I am including it, the only time I get correct line numbers is when I debug the tests in Chrome (I haven't tried other browsers).
Related: #109, #104

Add ```
webpack: {
// ...
devtool: 'inline-source-map'
}
to karma or do similar in your webpack config


[BUG] it detects ^ in code blocks.

x=a^2

It thinks it's a block reference.

I fixed it in 1.0.5. Please check if it works now. However, in this change, it would not detect a^2 in your previous issue (#2) as a block id anymore since it is an invalid block id anyways.


Read dynamic table and roundabouts from DDI

I forget to put new version number as the title of the PR


Make has_unitary and unitary fallback to decompose

Intended to fix #1163
So far, I have made has_unitary and unitary fallback to  decompose, together with some tests of the new functionality. Note that only objects that are instances of cirq.Operation are decomposed at the moment.
There is currently one test failing, which I have yet to solve (I did have 704 failed tests at some point, so progress!).
@Strilanc If I could get some comment on what I have done so far, what more tests I should implement, and "As part of this issue, a lot of special case "decompose to get unitary" code strewn around the code base (e.g. in simulators) should be rewritten.", that would be very much appreciated.

I hope that I addressed all your comments on my last commit.
About the failing test in convert_to_cz_and_single_gates_test.py, it tries to optimize a two qubit circuit consisting of composite gates. Before these composite gates did not have unitaries (the name of the test is also test_composite_gates_without_matrix), but with the new implementation of unitary and has_unitary they do now. This seems to lead to a different global phase for the optimized circuit since
cirq.testing.assert_allclose_up_to_global_phase(         circuit.to_unitary_matrix(),         c_orig.to_unitary_matrix(),         atol=1e-7)
passes fine, but assert circuit == expected does not.
If one indeed prints the two circuits,
circuit:
0: ───X───Y^0.5───@───────────────
│
1<EMAIL_ADDRESS>expected:
0: ───X───Y^0.5───@───────────────
│
1<EMAIL_ADDRESS>Is this test no longer meaningful, is there something wrong, or how should I handle this?

Hi @Strilanc, could you please review this again? It should now work correctly for operations, but not yet for gates. Should I try to implement this for gates as part of this PR? If so, what would be the best way to pass the qubit order to unitary?

I think that the has_unitary part should be done (it checks if all decomposed objects has unitaries), am I missing some functionality here?
I had some new tests from controlled operation fail, I tracked it down to that it was trying to get the unitary of a parameterized CCZ gate. What happens is that CCZPowGate._unitary_() returns NotImplemented if is_parameterized returns True, this leads to that cirq.unitary tries to decompose the gate, however CCZPowGate._decompose_ raises an error if CCZPowGate._exponent is a symbol. To solve this I found three different solutions:

Make CCZPowGate._decompose_ return NotImplemented if it is parameterized.
Make cirq.unitary  (cirq.has_unitary) check if val is parameterized and return default (False) if it is.
Only decompose in cirq.unitary ( cirq.has_unitary) if val._unitary (val._has_unitary) doesn't exist, i.e. if they do exist and returns NotImplemented, we don't decompose.

Which of these alternatives would you prefer @Strilanc?

Make CCZPowGate._decompose_ return NotImplemented if it is parameterized.

To be specific:
    def _decompose_(self, qubits):
        """An adjacency-respecting decomposition.

        0: ───p───@──────────────@───────@──────────@──────────
                  │              │       │          │
        1: ───p───X───@───p^-1───X───@───X──────@───X──────@───
                      │              │          │          │
        2: ───p───────X───p──────────X───p^-1───X───p^-1───X───

        where p = T**self._exponent
        """
        if protocols.is_parameterized(self):
            return NotImplemented

        a, b, c = qubits

        # Hacky magic: avoid the non-adjacent edge.
        if hasattr(b, 'is_adjacent'):
            if not b.is_adjacent(a):
                b, c = c, b
            elif not b.is_adjacent(c):
                a, b = b, a

        p = common_gates.T**self._exponent
        sweep_abc = [common_gates.CNOT(a, b),
                     common_gates.CNOT(b, c)]

        return [
            p(a), p(b), p(c),
            sweep_abc,
            p(b)**-1, p(c),
            sweep_abc,
            p(c)**-1,
            sweep_abc,
            p(c)**-1,
            sweep_abc,
        ]

You can ignore the num_qubits method coverages via # coverage: ignore

Thanks for the help! This should finally be ready to merge.


Sometime app frozen/map distored after zoom in and zoom out map.

Sometime my app frozen after zoom in and zoom out map. I leave the screen for a few minute but nothing change, and app not crash too.
Sometime zoom in and zoom out mapview also cause map distorted

Is this a bug report?
Yes
Have you read the [Installation Instructions]
Yes
Environment
react-native: 0.59.1
react: 16.8.3
react-native-maps: 0.23.0
map provider: Google
platform: iOS
device: iPhone X Max

Steps to Reproduce
I can't reproduce it's consistently , it's happen very randomly when I zoom in and zoom out google map , I also have some marker and circle on map, most of the time it's work correct.

@kduy969 this can't be handled as a bug report since we don't have any details provided.
Please spend time analysing ideally using a sample project and once you find out the exact bug source we're happy to look into it.
But freezes sound like too many rerender attempts or too much communication over the bridge, please try to optimize there.
Feel free to submit a new issue with better description / more details.

Sometime my app frozen after zoom in and zoom out map. I leave the screen for a few minute but nothing change, and app not crash too.
Sometime zoom in and zoom out mapview also cause map distorted

Is this a bug report?
Yes
Have you read the [Installation Instructions]
Yes
Environment
react-native: 0.59.1
react: 16.8.3
react-native-maps: 0.23.0
map provider: Google
platform: iOS
device: iPhone X Max

Steps to Reproduce
I can't reproduce it's consistently , it's happen very randomly when I zoom in and zoom out google map , I also have some marker and circle on map, most of the time it's work correct.

Did you solve this?

Any update on this issue, please?


Website login functionality

 Issue by nup002
Fri Jun 29 20:26:48 2018
Originally opened as https://github.com/codelucas/newspaper/issues/587

This is not so much an issue as a suggestion/request.
This suggestion came up as I needed to pull articles from a website with a paywall. I have a user, but could not for the life of me figure out how get a logged in session going in Newspaper.
If the solution is simple and I am just too daft to understand it, feel free to come with suggestions.

https://github.com/AndyTheFactory/newspaper4k/issues/668 has not been created yet afaict

Just to follow up on this I was able follow the Playwright example herehttps://github.com/AndyTheFactory/newspaper4k/issues/220
Basically, I am using Playwright to click any cookie compliance while making sure the same context is applied when checking the for existence of relevant content. Note that the button in this case is contained within an iframe.
`
from playwright.sync_api import sync_playwright
import newspaper
def accept_cookies_and_fetch_article(url):
# Using Playwright to handle login and fetch article
with sync_playwright() as p:
browser = p.chromium.launch(headless=True)  # Set headless=False to watch the browser actions
page = browser.new_page()
    # create a new incognito browser context
    context = browser.new_context()
    # create a new page inside context.
    page = context.new_page()

    page.goto(url)

    # Automating iframe button click
    page.frame_locator("iframe[title=\"SP Consent Message\"]").get_by_label("Essential cookies only").click()

    content = page.content()
    # dispose context once it is no longer needed.
    context.close()
    browser.close()

# Using Newspaper4k to parse the page content
article = newspaper.article(url, input_html=content, language='en')

return article

Example URL
url = 'https://www.skysports.com/football/live-blog/11661/12476234/transfer-centre-live-luis-guilherme-joao-palhinha-jadon-sancho-latest'
Fetch and process the article
article = accept_cookies_and_fetch_article(url)
article.nlp()
print(f"Title: {article.title}")
print(f"Authors: {article.authors}")
print(f"Publication Date: {article.publish_date}")
print(f"Summary: {article.summary}")
print(f"Text: {article.text}")
print(f"Keywords: {article.keywords}")
`


SourceForge URLs A-D

Changes to a cask
Editing an existing cask

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.

The docs need to be updated with the new Sourceforge URL scheme.

@jawshooah, docs are updated now.


docs: add instructions for protos contribution

Clarify an important workflow in CONTRIBUTING.md to avoid users adding compiled protos through their own workflows.
Example: related PR with above issue.

This change is

How do I run the linter locally before committing this doc change?
Is there a doc on the repo I can refer for that?

Thanks Tyler, I will push your requested changes later today.


DeepSpeed Accelerator can NOT save optimizer state

Same as title. ~I'm in investigating.~ With following modification, scripts can save optimizer state.
Error messages will be attached here.

Environment

4 x RTX 3090 GPUs
sd-scripts: 71e2c91330a9d866ec05cdd10584bbb962896a99

Using train_network.py normally

logs of saving optimizer state

INFO     Saving DeepSpeed Model and Optimizer  logging.py:61
[rank1]:[E ProcessGroupNCCL.cpp:523] [Rank 1] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=6004, OpType=ALLREDUCE, NumelIn=126834688, NumelOut=126834688, Timeout(ms)=600000) ran for 600410 milliseconds before timing out.
[rank2]:[E ProcessGroupNCCL.cpp:523] [Rank 2] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=6004, OpType=ALLREDUCE, NumelIn=126834688, NumelOut=126834688, Timeout(ms)=600000) ran for 600771 milliseconds before timing out.
[rank3]:[E ProcessGroupNCCL.cpp:523] [Rank 3] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=6004, OpType=ALLREDUCE, NumelIn=126834688, NumelOut=126834688, Timeout(ms)=600000) ran for 600333 milliseconds before timing out.
[rank1]:[E ProcessGroupNCCL.cpp:537] Some NCCL operations have failed or timed out. Due to the asynchronous nature of CUDA kernels, subsequent GPU operations might run on corrupted/incomplete data.
[rank1]:[E ProcessGroupNCCL.cpp:543] To avoid data inconsistency, we are taking the entire process down.

Here is corresponding codes in sd-scripts. This structure is same as save_every_n_epoch.
if args.save_every_n_steps is not None and global_step % args.save_every_n_steps == 0:
    accelerator.wait_for_everyone()
    **if accelerator.is_main_process**:
        ckpt_name = train_util.get_step_ckpt_name(args, "." + args.save_model_as, global_step)
        save_model(ckpt_name, accelerator.unwrap_model(network), global_step, epoch)

        **if args.save_state:**
            train_util.save_and_remove_state_stepwise(args, accelerator, global_step)

Analysis: Only Rank 0(GPU 0, or cuda:0) is ready to save optimizer states. With ZeRO, stage above 0, optimizer state is distributed cross all gpus. So, in the block of is_main_process, accelerator wait forever rest of gpus(rank1, 2, 3) which never try to save optimizer state. Therefore, NCLL group raise timeout error. Of course, saving model is not a problem.
Related issue: get stuck when save_state using DeepSpeed backend under training train_text_to_image_lora

Applying related issue' method

make save state line out of is_main_process block.
if args.save_every_n_steps is not None and global_step % args.save_every_n_steps == 0:
    accelerator.wait_for_everyone()
    if accelerator.is_main_process:
        ckpt_name = train_util.get_step_ckpt_name(args, "." + args.save_model_as, global_step)
        save_model(ckpt_name, accelerator.unwrap_model(network), global_step, epoch)

        if args.save_state and not args.deepspeed:
            train_util.save_and_remove_state_stepwise(args, accelerator, global_step)

    if args.save_state and args.deepspeed:
            train_util.save_and_remove_state_stepwise(args, accelerator, global_step)
    accelerator.wait_for_everyone()

This is ad-hoc modification for solving problem. And here are log of codes.
[2024-04-09 15:39:37,942] [INFO] [logging.py:96:log_dist] [Rank 0] Saving model checkpoint: ./training/model/temp/test-step00000001-state/pytorch_model/mp_rank_00_model_states.pt
[2024-04-09 15:39:37,942] [INFO] [torch_checkpoint_engine.py:21:save] [Torch] Saving ./training/model/temp/test-step00000001-state/pytorch_model/mp_rank_00_model_states.pt...
[2024-04-09 15:40:06,463] [INFO] [torch_checkpoint_engine.py:23:save] [Torch] Saved ./training/model/temp/test-step00000001-state/pytorch_model/mp_rank_00_model_states.pt.
[2024-04-09 15:40:07,083] [INFO] [torch_checkpoint_engine.py:21:save] [Torch] Saving ./training/model/temp/test-step00000001-state/pytorch_model/zero_pp_rank_0_mp_rank_00_optim_states.pt...
[2024-04-09 15:40:07,246] [INFO] [torch_checkpoint_engine.py:21:save] [Torch] Saving ./training/model/temp/test-step00000001-state/pytorch_model/zero_pp_rank_1_mp_rank_00_optim_states.pt...
[2024-04-09 15:40:07,246] [INFO] [torch_checkpoint_engine.py:21:save] [Torch] Saving ./training/model/temp/test-step00000001-state/pytorch_model/zero_pp_rank_2_mp_rank_00_optim_states.pt...
[2024-04-09 15:40:07,249] [INFO] [torch_checkpoint_engine.py:21:save] [Torch] Saving ./training/model/temp/test-step00000001-state/pytorch_model/zero_pp_rank_3_mp_rank_00_optim_states.pt...
[2024-04-09 15:40:08,808] [INFO] [torch_checkpoint_engine.py:23:save] [Torch] Saved ./training/model/temp/test-step00000001-state/pytorch_model/zero_pp_rank_1_mp_rank_00_optim_states.pt.
[2024-04-09 15:40:08,808] [INFO] [engine.py:3477:_save_zero_checkpoint] zero checkpoint saved ./training/model/temp/test-step00000001-state/pytorch_model/zero_pp_rank_1_mp_rank_00_optim_states.pt
[2024-04-09 15:40:08,808] [INFO] [torch_checkpoint_engine.py:33:commit] [Torch] Checkpoint pytorch_model is ready now!
[2024-04-09 15:40:08,818] [INFO] [torch_checkpoint_engine.py:23:save] [Torch] Saved ./training/model/temp/test-step00000001-state/pytorch_model/zero_pp_rank_2_mp_rank_00_optim_states.pt.
[2024-04-09 15:40:08,818] [INFO] [engine.py:3477:_save_zero_checkpoint] zero checkpoint saved ./training/model/temp/test-step00000001-state/pytorch_model/zero_pp_rank_2_mp_rank_00_optim_states.pt
[2024-04-09 15:40:08,819] [INFO] [torch_checkpoint_engine.py:33:commit] [Torch] Checkpoint pytorch_model is ready now!
[2024-04-09 15:40:08,824] [INFO] [torch_checkpoint_engine.py:23:save] [Torch] Saved ./training/model/temp/test-step00000001-state/pytorch_model/zero_pp_rank_0_mp_rank_00_optim_states.pt.
[2024-04-09 15:40:08,832] [INFO] [torch_checkpoint_engine.py:23:save] [Torch] Saved ./training/model/temp/test-step00000001-state/pytorch_model/zero_pp_rank_3_mp_rank_00_optim_states.pt.
[2024-04-09 15:40:08,832] [INFO] [engine.py:3477:_save_zero_checkpoint] zero checkpoint saved ./training/model/temp/test-step00000001-state/pytorch_model/zero_pp_rank_3_mp_rank_00_optim_states.pt
[2024-04-09 15:40:08,832] [INFO] [torch_checkpoint_engine.py:33:commit] [Torch] Checkpoint pytorch_model is ready now!
[2024-04-09 15:40:08,883] [INFO] [engine.py:3477:_save_zero_checkpoint] zero checkpoint saved ./training/model/temp/test-step00000001-state/pytorch_model/zero_pp_rank_0_mp_rank_00_optim_states.pt
[2024-04-09 15:40:08,884] [INFO] [torch_checkpoint_engine.py:33:commit] [Torch] Checkpoint pytorch_model is ready now!
2024-04-09 15:40:08 INFO     DeepSpeed Model and Optimizer saved   logging.py:61
                             to output dir
                             ./training/model/temp/test-step000000
                             01-state/pytorch_model
Traceback (most recent call last):
  File "/home/hard2251/workspace/sd-scripts/./sdxl_train_network.py", line 185, in <module>
    trainer.train(args)
  File "/home/hard2251/workspace/sd-scripts/train_network.py", line 949, in train
    train_util.save_and_remove_state_stepwise(args, accelerator, global_step)
  File "/home/hard2251/workspace/sd-scripts/library/train_util.py", line 4845, in save_and_remove_state_stepwise
    accelerator.save_state(state_dir)
  File "/home/hard2251/anaconda3/envs/sd-scripts/lib/python3.10/site-packages/accelerate/accelerator.py", line 2706, in save_state
    hook(self._models, weights, output_dir)
  File "/home/hard2251/workspace/sd-scripts/train_network.py", line 488, in save_model_hook
    weights.pop(i)
IndexError: pop from empty list

Related issue: get stuck when save_state using DeepSpeed backend under training train_text_to_image_lora.
Before
def save_model_hook(models, weights, output_dir):
    # pop weights of other models than network to save only network weights
    if accelerator.is_main_process:
        remove_indices = []
        for i, model in enumerate(models):
            if not isinstance(model, type(accelerator.unwrap_model(network))):
                remove_indices.append(i)
        for i in reversed(remove_indices):rr
            weights.pop(i)

After
def save_model_hook(models, weights, output_dir):
    # pop weights of other models than network to save only network weights
    if accelerator.is_main_process:
        remove_indices = []
        for i, model in enumerate(models):
            if not isinstance(model, type(accelerator.unwrap_model(network))):
                remove_indices.append(i)
        for i in reversed(remove_indices):
            **if weights:**
                weights.pop(i)

After modifying both block of save_state and function of save_model_hook, sd-scripts is now able to save optimizer state when deepspeed=true.

Issue is updated!

By doing above problem, I met another error.
TypeError: cannot pickle 'torch._C._distributed_c10d.ProcessGroup' object


Sonobuoy not retrying failed tests

Running conformance tests, some of them are failing, want to retry them:
sonobuoy run --mode=certified-conformance --kube-conformance-image gcr.io/google-containers/conformance:v1.19.0-rc.1
results=$(sonobuoy retrieve)
sonobuoy run --wait --rerun-failed $results --mode=certified-conformance --kube-conformance-image gcr.io/google-containers/conformance:v1.19.0-rc.1

What did you expect to happen:
sonobuoy running only failed tests, but running all, from scratch.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Sonobuoy version: 0.54.0
Kubernetes version:

Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.11", GitCommit:"c6a2f08fc4378c5381dd948d9ad9d1080e3e6b33", GitTreeState:"clean", BuildDate:"2021-05-12T12:27:07Z", GoVersion:"go1.15.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19+", GitVersion:"v1.19.13-eks-8df270", GitCommit:"8df2700a72a2598fa3a67c05126fa158fd839620", GitTreeState:"clean", BuildDate:"2021-07-31T01:36:57Z", GoVersion:"go1.15.14", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes installer & version: EKS 1.19
Cloud provider or hardware configuration: AWS
OS (e.g. from /etc/os-release): running sonobuoy inside official container
Sonobuoy tarball ^^^

Looks like regression of #1387

💯 I'll repro locally and fix this right away. Should be pretty straight forward. In a week or so I can release a 55.1 with minor bug fixes like this.

Oh I will say that I notice something about your command that may cause it;
notice that you have two flags that interact on the same field:

--mode=certified-conformance
--rerun-failed ...

You specified the rerun failed first, then the certified conformance. It probably set the E2E_FOCUS to the failed tests an then to the certified conformance afterwards.
You'll just want to remove the --mode if you want to rerun failed.
In this situation a warning should have appeared though since those flags can conflict. I'll put up a PR for that.
Can you confirm the behavior of Sonobuoy when you remove the unnecessary flag?

@johnSchnake, sorry for inconvinience, now I did as you said, only mode, then retry:
> sonobuoy results<PHONE_NUMBER>40_sonobuoy_918eff36-bdf7-45fc-ae90-548053dc381f.tar.gz

Plugin: systemd-logs
Status: passed
Total: 6
Passed: 6
Failed: 0
Skipped: 0

Plugin: e2e
Status: failed
Total: 5239
Passed: 276
Failed: 21
Skipped: 4942

Failed tests:
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny attaching pod [Conformance]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]
[sig-api-machinery] Aggregator Should be able to support the 1.17 Sample API Server using the current Aggregator [Conformance]
[sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching  [Conformance]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny pod and configmap creation [Conformance]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should not be able to mutate or prevent deletion of webhook configuration objects [Conformance]
[sig-scheduling] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run  [Conformance]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with pruning [Conformance]
[sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert a non homogeneous list of CRs [Conformance]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource [Conformance]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with different stored version [Conformance]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] listing validating webhooks should work [Conformance]
[sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] listing mutating webhooks should work [Conformance]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should deny crd creation [Conformance]
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]

> kubectl delete ns sonobuoy

namespace "sonobuoy" deleted

> sonobuoy run --rerun-failed<PHONE_NUMBER>40_sonobuoy_918eff36-bdf7-45fc-ae90-548053dc381f.tar.gz --kube-conformance-image gcr.io/google-containers/conformance:v1.19.0-rc.1

INFO[0001] create request issued                         name=sonobuoy namespace= resource=namespaces
INFO[0001] create request issued                         name=sonobuoy-serviceaccount namespace=sonobuoy resource=serviceaccounts
INFO[0001] object already exists                         name=sonobuoy-serviceaccount-sonobuoy namespace= resource=clusterrolebindings
INFO[0001] object already exists                         name=sonobuoy-serviceaccount-sonobuoy namespace= resource=clusterroles
INFO[0001] create request issued                         name=sonobuoy-config-cm namespace=sonobuoy resource=configmaps
INFO[0002] create request issued                         name=sonobuoy-plugins-cm namespace=sonobuoy resource=configmaps
INFO[0002] create request issued                         name=sonobuoy namespace=sonobuoy resource=pods
INFO[0002] create request issued                         name=sonobuoy-aggregator namespace=sonobuoy resource=services

and no more output. Retrieve giving nothing
> sonobuoy retrieve
error retrieving results: no valid entries in result

Sorry, my fault, forgot to add --wait....


Issues while compiling THEOplayer with ReNative framework

Hi there, I'm experiencing issues while using ReNative framework and THEOplayer package.
To be more specific, the error appears while compiling for AndroidTV (haven't tested for other platforms yet)
`FAILURE: Build completed with 2 failures.
Task failed with an exception.
What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.

Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
Could not find any matches for com.theoplayer.theoplayer-sdk-android:unified:+ as no versions of com.theoplayer.theoplayer-sdk-android:unified are available.
Searched in the following locations:
- https://www.jitpack.io/com/theoplayer/theoplayer-sdk-android/unified/maven-metadata.xml
- https://www.jitpack.io/com/theoplayer/theoplayer-sdk-android/unified/6.6.0/unified-6.6.0.pom
- https://repo.maven.apache.org/maven2/com/theoplayer/theoplayer-sdk-android/unified/maven-metadata.xml
- https://dl.google.com/dl/android/maven2/com/theoplayer/theoplayer-sdk-android/unified/maven-metadata.xml
- https://plugins.gradle.org/m2/com/theoplayer/theoplayer-sdk-android/unified/maven-metadata.xml
- file:/Volumes/CRUCIAL_M2/renative/project/node_modules/react-native/android/com/theoplayer/theoplayer-sdk-android/unified/maven-metadata.xml
- file:/Volumes/CRUCIAL_M2/renative/project/node_modules/jsc-android/dist/com/theoplayer/theoplayer-sdk-android/unified/maven-metadata.xml
Required by:
project :app > project :react-native-theoplayer
Could not find any matches for com.theoplayer.theoplayer-sdk-android:unified-ads:+ as no versions of com.theoplayer.theoplayer-sdk-android:unified-ads are available.
Searched in the following locations:
- https://www.jitpack.io/com/theoplayer/theoplayer-sdk-android/unified-ads/maven-metadata.xml
- https://www.jitpack.io/com/theoplayer/theoplayer-sdk-android/unified-ads/6.6.0/unified-ads-6.6.0.pom
- https://repo.maven.apache.org/maven2/com/theoplayer/theoplayer-sdk-android/unified-ads/maven-metadata.xml
- https://dl.google.com/dl/android/maven2/com/theoplayer/theoplayer-sdk-android/unified-ads/maven-metadata.xml
- https://plugins.gradle.org/m2/com/theoplayer/theoplayer-sdk-android/unified-ads/maven-metadata.xml
- file:/Volumes/CRUCIAL_M2/renative/project/node_modules/react-native/android/com/theoplayer/theoplayer-sdk-android/unified-ads/maven-metadata.xml
- file:/Volumes/CRUCIAL_M2/renative/project/node_modules/jsc-android/dist/com/theoplayer/theoplayer-sdk-android/unified-ads/maven-metadata.xml
Required by:
project :app > project :react-native-theoplayer
Could not find any matches for com.theoplayer.theoplayer-sdk-android:unified-ads-ima:+ as no versions of com.theoplayer.theoplayer-sdk-android:unified-ads-ima are available.
Searched in the following locations:
- https://www.jitpack.io/com/theoplayer/theoplayer-sdk-android/unified-ads-ima/maven-metadata.xml
- https://www.jitpack.io/com/theoplayer/theoplayer-sdk-android/unified-ads-ima/6.6.0/unified-ads-ima-6.6.0.pom
- https://repo.maven.apache.org/maven2/com/theoplayer/theoplayer-sdk-android/unified-ads-ima/maven-metadata.xml
- https://dl.google.com/dl/android/maven2/com/theoplayer/theoplayer-sdk-android/unified-ads-ima/maven-metadata.xml
- https://plugins.gradle.org/m2/com/theoplayer/theoplayer-sdk-android/unified-ads-ima/maven-metadata.xml
- file:/Volumes/CRUCIAL_M2/renative/project/node_modules/react-native/android/com/theoplayer/theoplayer-sdk-android/unified-ads-ima/maven-metadata.xml
- file:/Volumes/CRUCIAL_M2/renative/project/node_modules/jsc-android/dist/com/theoplayer/theoplayer-sdk-android/unified-ads-ima/maven-metadata.xml
Required by:
project :app > project :react-native-theoplayer

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Task failed with an exception.
What went wrong:
Execution failed for task ':react-native-theoplayer:generateDebugRFile'.

Could not resolve all files for configuration ':react-native-theoplayer:debugCompileClasspath'.
Could not find any matches for com.theoplayer.theoplayer-sdk-android:unified:+ as no versions of com.theoplayer.theoplayer-sdk-android:unified are available.
Required by:
project :react-native-theoplayer
Could not find any matches for com.theoplayer.theoplayer-sdk-android:unified-ads:+ as no versions of com.theoplayer.theoplayer-sdk-android:unified-ads are available.
Required by:
project :react-native-theoplayer
Could not find any matches for com.theoplayer.theoplayer-sdk-android:unified-ads-ima:+ as no versions of com.theoplayer.theoplayer-sdk-android:unified-ads-ima are available.
Required by:
project :react-native-theoplayer`

Among all these errors I noticed:
`What went wrong:
Execution failed for task :react-native-theoplayer:generateDebugRFile.

Could not resolve all files for configuration ':react-native-theoplayer:debugCompileClasspath'.
Could not find any matches for com.theoplayer.theoplayer-sdk-android:unified:+ as no versions of com.theoplayer.theoplayer-sdk-android:unified are available.
Required by:
project :react-native-theoplayer
Could not find any matches for com.theoplayer.theoplayer-sdk-android:unified-ads:+ as no versions of com.theoplayer.theoplayer-sdk-android:unified-ads are available.
Required by:
project :react-native-theoplayer
Could not find any matches for com.theoplayer.theoplayer-sdk-android:unified-ads-ima:+ as no versions of com.theoplayer.theoplayer-sdk-android:unified-ads-ima are available.
Required by:
project :react-native-theoplayer`

It seems like It can't find these packages which are required...any clue?
Any help on this It would be appreciated, thank you!
ReNative 0.37.4
React Native THEOplayer 3.2.1

Same issue here! Can't build my project for android anymore due to this error.

It looks like it still tries to resolve pre-v6.0.0 native SDKs. Since 6.0, the native Android player SDK has been renamed from
com.theoplayer.theoplayer-sdk-android:unified:+ to com.theoplayer.theoplayer-sdk-android:core:+
The extension modules also have been renamed.
In react-native-theoplayer v3.0.0 support for renaming has been included (https://github.com/THEOplayer/react-native-theoplayer/blob/develop/CHANGELOG.md#300---23-10-06), so it looks like there is still a reference to an older react-native-theoplayer SDK version in the project.
Is it possible to verify this in your project? Maybe check in the resolved ./node_module/react-native-theoplayer if this really is a v3+ version?

Hi there,
it seems to be 3.2.1 the version installed, here you are the package.json in ~/node_modules/react-native-theoplayer
{   "name": "react-native-theoplayer",   "version": "3.2.1",   "description": "A THEOplayer video component for react-native.",   "main": "lib/commonjs/index",   "module": "lib/module/index",   "types": "lib/typescript/index.d.ts",   "react-native": "src/index",   "source": "src/index",   "files": [     "src",     "lib",     "android",     "ios",     "cpp",     "react-native-theoplayer.podspec",     "react-native-theoplayer.json",     "CHANGELOG.md",     "!lib/typescript/example",     "!android/build",     "!ios/build",     "!**/__fixtures__",     "!**/__mocks__"   ],   "scripts": {     "typescript": "tsc --noEmit",     "lint": "eslint \"**/*.{ts,tsx}\"",     "prepare": "bob build && husky install",     "release": "release-it",     "pods": "cd example && pod-install --quiet"   },   "keywords": [     "react-native",     "THEOplayer",     "ios",     "android"   ],   "repository": {     "type": "git",     "url": "git@github.com:THEOplayer/react-native-theoplayer.git"   },   "author": "THEO Technologies",   "license": "SEE LICENSE AT https://www.theoplayer.com/terms",   "homepage": "https://theoplayer.com/",   "publishConfig": {     "registry": "https://registry.npmjs.org/"   },   "devDependencies": {     "@commitlint/config-conventional": "^11.0.0",     "@react-native-community/eslint-config": "^2.0.0",     "@release-it/conventional-changelog": "^7.0.2",     "@types/react": "^18.2.24",     "@types/react-native": "^0.72.3",     "commitlint": "^17.7.2",     "eslint": "^7.32.0",     "eslint-config-prettier": "^7.2.0",     "eslint-plugin-prettier": "^3.4.1",     "eslint-plugin-react-native": "^4.1.0",     "husky": "^6.0.0",     "pod-install": "^0.1.39",     "prettier": "^2.8.8",     "react": "^18.2.0",     "react-native": "^0.72.5",     "react-native-builder-bob": "^0.18.3",     "release-it": "^16.2.1",     "theoplayer": "^6.1.0",     "typescript": "^4.9.5"   },   "peerDependencies": {     "react": "*",     "react-native": "*",     "theoplayer": ">=5.0.1"   },   "peerDependenciesMeta": {     "theoplayer": {       "optional": true     }   },   "commitlint": {     "extends": [       "@commitlint/config-conventional"     ]   },   "release-it": {     "git": {       "commitMessage": "chore: release ${version}",       "tagName": "v${version}"     },     "npm": {       "publish": true     },     "github": {       "release": true     },     "plugins": {       "@release-it/conventional-changelog": {         "preset": "angular"       }     }   },   "eslintIgnore": [     "node_modules/",     "lib/"   ],   "react-native-builder-bob": {     "source": "src",     "output": "lib",     "targets": [       "commonjs",       "module",       [         "typescript",         {           "project": "tsconfig.build.json"         }       ]     ]   },   "dependencies": {     "buffer": "^6.0.3"   } }

@andread95 OK we'll check it with a vanilla Renative project as well.

To give you more context, my error is similar
* What went wrong:
Could not determine the dependencies of task ':app:processDebugResources'.
> Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
   > Could not find any matches for com.nicepeopleatwork:theoplayer-unified-adapter:+ as no versions of com.nicepeopleatwork:theoplayer-unified-adapter are available.
     Searched in the following locations:
       - file:/Users/michelecocuccio/Desktop/THE_WAVE/PROJECTS/LBA/lba-app/node_modules/react-native/android/com/nicepeopleatwork/theoplayer-unified-adapter/maven-metadata.xml
       - file:/Users/michelecocuccio/Desktop/THE_WAVE/PROJECTS/LBA/lba-app/node_modules/jsc-android/dist/com/nicepeopleatwork/theoplayer-unified-adapter/maven-metadata.xml
       - https://dl.google.com/dl/android/maven2/com/nicepeopleatwork/theoplayer-unified-adapter/maven-metadata.xml
       - https://repo.maven.apache.org/maven2/com/nicepeopleatwork/theoplayer-unified-adapter/maven-metadata.xml
       - https://www.jitpack.io/com/nicepeopleatwork/theoplayer-unified-adapter/maven-metadata.xml
       - https://oss.sonatype.org/content/repositories/snapshots/com/nicepeopleatwork/theoplayer-unified-adapter/maven-metadata.xml
     Required by:
         project :app > project :theoplayer_react-native-analytics-youbora
   > Could not find com.nicepeopleatwork:configutil:0.4.7.
     Searched in the following locations:
       - file:/Users/michelecocuccio/Desktop/THE_WAVE/PROJECTS/LBA/lba-app/node_modules/react-native/android/com/nicepeopleatwork/configutil/0.4.7/configutil-0.4.7.pom
       - file:/Users/michelecocuccio/Desktop/THE_WAVE/PROJECTS/LBA/lba-app/node_modules/jsc-android/dist/com/nicepeopleatwork/configutil/0.4.7/configutil-0.4.7.pom
       - https://dl.google.com/dl/android/maven2/com/nicepeopleatwork/configutil/0.4.7/configutil-0.4.7.pom
       - https://repo.maven.apache.org/maven2/com/nicepeopleatwork/configutil/0.4.7/configutil-0.4.7.pom
       - https://www.jitpack.io/com/nicepeopleatwork/configutil/0.4.7/configutil-0.4.7.pom
       - https://oss.sonatype.org/content/repositories/snapshots/com/nicepeopleatwork/configutil/0.4.7/configutil-0.4.7.pom
     Required by:
         project :app > project :theoplayer_react-native-analytics-youbora
   > Could not find com.theoplayer.theoplayer-sdk-android:ads-wrapper:4.8.0.
     Searched in the following locations:
       - file:/Users/michelecocuccio/Desktop/THE_WAVE/PROJECTS/LBA/lba-app/node_modules/react-native/android/com/theoplayer/theoplayer-sdk-android/ads-wrapper/4.8.0/ads-wrapper-4.8.0.pom
       - file:/Users/michelecocuccio/Desktop/THE_WAVE/PROJECTS/LBA/lba-app/node_modules/jsc-android/dist/com/theoplayer/theoplayer-sdk-android/ads-wrapper/4.8.0/ads-wrapper-4.8.0.pom
       - https://dl.google.com/dl/android/maven2/com/theoplayer/theoplayer-sdk-android/ads-wrapper/4.8.0/ads-wrapper-4.8.0.pom
       - https://repo.maven.apache.org/maven2/com/theoplayer/theoplayer-sdk-android/ads-wrapper/4.8.0/ads-wrapper-4.8.0.pom
       - https://www.jitpack.io/com/theoplayer/theoplayer-sdk-android/ads-wrapper/4.8.0/ads-wrapper-4.8.0.pom
       - https://oss.sonatype.org/content/repositories/snapshots/com/theoplayer/theoplayer-sdk-android/ads-wrapper/4.8.0/ads-wrapper-4.8.0.pom
     Required by:
         project :app > project :react-native-theoplayer
   > Could not find com.theoplayer.android-connector:mediasession:5.11.0-local.
     Searched in the following locations:
       - file:/Users/michelecocuccio/Desktop/THE_WAVE/PROJECTS/LBA/lba-app/node_modules/react-native/android/com/theoplayer/android-connector/mediasession/5.11.0-local/mediasession-5.11.0-local.pom
       - file:/Users/michelecocuccio/Desktop/THE_WAVE/PROJECTS/LBA/lba-app/node_modules/jsc-android/dist/com/theoplayer/android-connector/mediasession/5.11.0-local/mediasession-5.11.0-local.pom
       - https://dl.google.com/dl/android/maven2/com/theoplayer/android-connector/mediasession/5.11.0-local/mediasession-5.11.0-local.pom
       - https://repo.maven.apache.org/maven2/com/theoplayer/android-connector/mediasession/5.11.0-local/mediasession-5.11.0-local.pom
       - https://www.jitpack.io/com/theoplayer/android-connector/mediasession/5.11.0-local/mediasession-5.11.0-local.pom
       - https://oss.sonatype.org/content/repositories/snapshots/com/theoplayer/android-connector/mediasession/5.11.0-local/mediasession-5.11.0-local.pom
     Required by:
         project :app > project :react-native-theoplayer
         ```

         Package.json
         ```
      "react-native": "0.72.6",
     "react-native-theoplayer": "^3.2.1",
    "@theoplayer/react-native-analytics-youbora": "^1.1.1",
    "@theoplayer/react-native-ui": "^0.3.0",
    ```

@michelecocuccio we created a sample app for ReNative here:
https://github.com/THEOplayer/renative-theoplayer-sample
could you try this one?
Passing the extra repository is important:
https://github.com/THEOplayer/renative-theoplayer-sample#android-plugin-configuration

I am so sorry, I haven't properly read the issue and I easily mistaken "Renative" with "React Native".
Mi issue (which is similar) happens in a expo managed project but this should not make a difference in fact I was able to build it until a couple of weeks ago. Should I open a separated issue? Sorry again if I made this mistake

@michelecocuccio OK no problem, Expo has similar issues with resolving the internal Maven modules. It doesn't process the custom repository url we provide in the gradle file.
We are adding an Expo plugin to react-native-theoplayer to accommodate this:
https://github.com/THEOplayer/react-native-theoplayer/pull/242
The plugin will add the Maven repo to the generated Android template when it is installed. We'll release it as soon as possible.

@michelecocuccio OK no problem, Expo has similar issues with resolving the internal Maven modules. It doesn't process the custom repository url we provide in the gradle file. We are adding an Expo plugin to react-native-theoplayer to accommodate this: #242
The plugin will add the Maven repo to the generated Android template when it is installed. We'll release it as soon as possible.

Thank you very much, it's very appreciated

@michelecocuccio could you try v3.4.1 of the react-native-theoplayer SDK?
Specify react-native-theoplayer as a plugin in the app.json file if your Expo app:
"plugins": ["react-native-theoplayer"]

We have a minimal Expo sample app, but it's not publicly available yet. Documentation is also pending.

@tvanlaerhoven Hi there, I've tried your solution but without success.
Still facing issues while building...I've tried with our project and with a sample one with just your RN SDK..we're getting this errors:
`FAILED with ERROR:
FAILURE: Build failed with an exception.

Where:
Build file '/Volumes/CRUCIAL_M2/test_renative/test_app/node_modules/react-native-theoplayer/android/build.gradle' line: 31

What went wrong:
A problem occurred evaluating project ':react-native-theoplayer'.

No signature of method: build_9ga7bnczku91pl30t7w9lf48l.android() is applicable for argument types: (build_9ga7bnczku91pl30t7w9lf48l$_run_closure1) values: [build_9ga7bnczku91pl30t7w9lf48l$_run_closure1@4bfdf7fd]

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 2s
Command failed with exit code 1: ./gradlew assembleDebug -x bundleReleaseJsAndAssets
FAILURE: Build failed with an exception.

Where:
Build file '/Volumes/CRUCIAL_M2/test_renative/test_app/node_modules/react-native-theoplayer/android/build.gradle' line: 31

What went wrong:
A problem occurred evaluating project ':react-native-theoplayer'.

No signature of method: build_9ga7bnczku91pl30t7w9lf48l.android() is applicable for argument types: (build_9ga7bnczku91pl30t7w9lf48l$_run_closure1) values: [build_9ga7bnczku91pl30t7w9lf48l$_run_closure1@4bfdf7fd]

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 2s
Configuration on demand is an incubating feature.

Configure project :app
Warning: The 'kotlin-android-extensions' Gradle plugin is deprecated. Please use this migration guide (https://goo.gle/kotlin-android-extensions-deprecation) to start working with View Binding (https://developer.android.com/topic/libraries/view-binding) and the 'kotlin-parcelize' plugin.

FAILURE: Build failed with an exception.

Where:
Build file '/Volumes/CRUCIAL_M2/test_renative/test_app/node_modules/react-native-theoplayer/android/build.gradle' line: 31

What went wrong:
A problem occurred evaluating project ':react-native-theoplayer'.

No signature of method: build_9ga7bnczku91pl30t7w9lf48l.android() is applicable for argument types: (build_9ga7bnczku91pl30t7w9lf48l$_run_closure1) values: [build_9ga7bnczku91pl30t7w9lf48l$_run_closure1@4bfdf7fd]

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 2s
Error: Command failed with exit code 1: ./gradlew assembleDebug -x bundleReleaseJsAndAssets
FAILURE: Build failed with an exception.

Where:
Build file '/Volumes/CRUCIAL_M2/test_renative/test_app/node_modules/react-native-theoplayer/android/build.gradle' line: 31

What went wrong:
A problem occurred evaluating project ':react-native-theoplayer'.

No signature of method: build_9ga7bnczku91pl30t7w9lf48l.android() is applicable for argument types: (build_9ga7bnczku91pl30t7w9lf48l$_run_closure1) values: [build_9ga7bnczku91pl30t7w9lf48l$_run_closure1@4bfdf7fd]

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 2s
Configuration on demand is an incubating feature.

Configure project :app
Warning: The 'kotlin-android-extensions' Gradle plugin is deprecated. Please use this migration guide (https://goo.gle/kotlin-android-extensions-deprecation) to start working with View Binding (https://developer.android.com/topic/libraries/view-binding) and the 'kotlin-parcelize' plugin.
at makeError (/Volumes/CRUCIAL_M2/test_renative/test_app/node_modules/execa/lib/error.js:60:11)
at handlePromise (/Volumes/CRUCIAL_M2/test_renative/test_app/node_modules/execa/index.js:118:26)
at processTicksAndRejections (node:internal/process/task_queues:96:5)`

@michelecocuccio there was an issue when the plugin was used without arguments like this:
"plugins": ["react-native-theoplayer"]
for which we released a patched version (3.4.2).
Your build error indicated something else I think. Could you double check the package versions are correct. Maybe also post here what is on the failing line 31 of the build.gradle file. Which version of Expo are you using?

Hi @andread95,
Are you still having the same error while building with Renative?
Can you please let me know if you could build the sample app my colleague shared so that we know if something is missing on your development environment or on your project? Please try to build https://github.com/THEOplayer/renative-theoplayer-sample (you will need to use node 16 with it). This project currently only includes Android and Web.

@michelecocuccio @andread95 we'll close this ticket for now. Let us know if you still encounter issues regarding ReNative.


Bolt says GPT-4 doesn't exist

Describe the bug
Bolt doesn't recognise my gpt-4o api.
Error is: "The model gpt-4 does not exist or you do not have access to it."
https://bolt.new/~/sb1-sc4kjb?utm_campaign=stackblitz-on-page&utm_source=web-app&utm_medium=nav-button
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-sc4kjb?utm_campaign=stackblitz-on-page&utm_source=web-app&utm_medium=nav-button
Steps to reproduce

Go to preview
Choose ai model
Insert keyword
Add details if you like
Click "generate SEO article"
Stare into the abyss of disappointment

Expected behavior
I expect bolt to accept the api and write an article calling on that api
Screen Recording / Screenshot
No response
Platform
Browser name = Firefox
Full version = 132.0
Major version = 132
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:132.0) Gecko/20100101 Firefox/132.0
performance.memory = undefined
Username = FinMcC
Chat ID = 50a0a68bc73d

Additional context
No response

At times, there are programming challenges that are too complex for the AI to solve. As such, manual intervention is required. You can read more about continuing to develop your project here: #2310.


Teamviewer hash issue when it is downloaded in China

Hi, all!
As I recently tried to submit a pr #3678 to fix the issue I've encountered ( or maybe someone else has encountered as well, say #3676 ) which is a tiny hash mismatch issue of Teamviewer. It turns out that @Dabombber @Ash258 and the bot are all free from this issue.
According to the screenshot provided by @Ash258, I did some investigation. And here are some facts I've found

If I download the teamviewer.zip using a proxy (which bridges to a server located in California), the sha256sum of the file is identical to the hash stated in the manifest.json

If I download it without the proxy, that is downloading directly (and I myself is located in China), then I'll get a different hash

I may assume that the Teamviewer I downloaded in China might have been specially treated by the Teamviewer team.
So, should I submit a special version of teamviewer.json (which should not be auto-updated from outside China, since the hash generated from outside China will not work in China)

If you are sure the file is correct then install it with skip parameter.
scoop install teamviewer -s And installation will continue even with hash mismatch.
There is no reason for extras bucket to handle it (same as #3280 ). If you want custom use custom generated manifest, but fastest way is to install it with skip.


Change order of benefits of LitElement

To put the biggest differentiator first.

Reference Issue

Yes, my thinking is that the main comparison we're targeting with this page is LitElement vs a non-WC framework.
Developers who already know they want WCs are are motivated to scan the headings and read more.

I think we can close this and focus on the new site :)


PluginValidationError using Datahub Plugin v2 in Airflow 2.5.0

Describe the bug
The Airflow scheduler and triggerer pod always crash after installing Datahub Plugin v2.
To Reproduce
Steps to reproduce the behavior:

Set up Kubernetes.
Create an Airflow namespace and install this chart.
Create a datahub namespace and install this chart.
Follow this: https://datahubproject.io/docs/lineage/airflow/#datahub-plugin-v2.

Expected behavior
The Airflow scheduler and triggerer will crash.
Screenshots

Desktop (please complete the following information):

Kubernetes: v1.27.2
Airflow: 2.5.0, Python: 3.8
Datahub: 0.12.0

Additional context

Here is the requirements.txt I used in the Dockerfile to build the image.
Here is the scheduler log in text:

➜  kubectl logs -f -n airflow airflow-scheduler-6455976774-c9wcb
Defaulted container "scheduler" out of: scheduler, git-sync, scheduler-log-groomer, wait-for-airflow-migrations (init), git-sync-init (init)

[2024-01-24T05:14:06.241+0000] {utils.py:430} WARNING - No module named 'airflow.providers.ftp.operators'
[2024-01-24T05:14:06.247+0000] {utils.py:430} WARNING - No module named 'airflow.providers.dbt'
[2024-01-24T05:14:07.101+0000] {base.py:73} INFO - Using connection ID 'datahub_rest_default' for task execution.
[2024-01-24T05:14:07.103+0000] {base.py:73} INFO - Using connection ID 'datahub_rest_default' for task execution.
[2024-01-24T05:14:07.104+0000] {datahub_listener.py:140} INFO - DataHub plugin v2 using DataHubRestEmitter: configured to talk to http://datahub-datahub-gms.datahub:8080/ with token: eyJh**********aZVg
  ____________       _____________
 ____    |__( )_________  __/__  /________      __
____  /| |_  /__  ___/_  /_ __  /_  __ \_ | /| / /
___  ___ |  / _  /   _  __/ _  / / /_/ /_ |/ |/ /
 _/_/  |_/_/  /_/    /_/    /_/  \____/____/|__/
Traceback (most recent call last):
  File "/home/airflow/.local/bin/airflow", line 8, in <module>
    sys.exit(main())
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/__main__.py", line 39, in main
    args.func(args)
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/cli/cli_parser.py", line 52, in command
    return func(*args, **kwargs)
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/utils/cli.py", line 108, in wrapper
    return f(*args, **kwargs)
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/cli/commands/scheduler_command.py", line 73, in scheduler
    _run_scheduler_job(args=args)
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/cli/commands/scheduler_command.py", line 36, in _run_scheduler_job
    job = SchedulerJob(
  File "<string>", line 4, in __init__
  File "/home/airflow/.local/lib/python3.8/site-packages/sqlalchemy/orm/state.py", line 482, in _initialize_instance
    manager.dispatch.init_failure(self, args, kwargs)
  File "/home/airflow/.local/lib/python3.8/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__
    compat.raise_(
  File "/home/airflow/.local/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 210, in raise_
    raise exception
  File "/home/airflow/.local/lib/python3.8/site-packages/sqlalchemy/orm/state.py", line 479, in _initialize_instance
    return manager.original_init(*mixed[1:], **kwargs)
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/jobs/scheduler_job.py", line 153, in __init__
    super().__init__(*args, **kwargs)
  File "<string>", line 6, in __init__
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/jobs/base_job.py", line 114, in __init__
    get_listener_manager().hook.on_starting(component=self)
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/listeners/listener.py", line 72, in get_listener_manager
    integrate_listener_plugins(_listener_manager)
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/plugins_manager.py", line 505, in integrate_listener_plugins
    listener_manager.add_listener(listener)
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/listeners/listener.py", line 59, in add_listener
    self.pm.register(listener)
  File "/home/airflow/.local/lib/python3.8/site-packages/pluggy/_manager.py", line 114, in register
    self._verify_hook(hook, hookimpl)
  File "/home/airflow/.local/lib/python3.8/site-packages/pluggy/_manager.py", line 232, in _verify_hook
    raise PluginValidationError(
pluggy._manager.PluginValidationError: Plugin 'datahub_airflow_plugin._datahub_listener_module' for hook 'on_dag_run_running'
hookimpl definition: on_dag_run_running(dag_run, session)Argument(s) {'session'} are declared in the hookimpl but can not be found in the hookspec

Looks like there was a small typo. I put up a PR to fix that

@hsheth2 Thank you very much. Looking forward to test again after the PR is merged.