text:
Different results when running both iOS and Android versions of MLKit Text Recognition On-Device API with the same image as input

When using the same image as input for the iOS and Android versions of MLKit Text Recognition On-Device API, I do get different results on the bounding boxes information (x,y,width,height) provided by each solution.
Please see below the original input image I've used for my tests and another image that shows the resulting text block's bounding boxes that were drawn based on the information provided by both of the Text Recognition on-device APIs (in blue is the iOS result and in red is the Android one):
Original input image
Resulting bounding boxes
Does anyone knows what could cause such differences between the results for iOS and Android versions of the API? I suspect they use different ML models for the text recognition / extraction of bounding boxes. If so, is there any chance of having both solutions running the same model in a near future since they are still on beta release?
Any thoughts are welcome!

Filed b/112423460 with the ML team, I'll let you know what they say. I suspect this is a bug or artifact of some offline model packaging caveats.

This issue is the result of the iOS and Android SDKs using different versions of the same OCR engine. It will be resolved in a future update, though not soon. In the meantime, both SDKs should continue to identify text correctly, though they may report slightly different bounding boxes.
If either SDK does not recognize text correctly, please open a new issue and I'll take a look.
Thanks!


text:
Fix FCM service worker setup code for >= 7.0.0.

Update the FCM service worker setup code to work with >=7.0.0 Firebase JavaScript SDK. There was a major change in v7.0.0 as mentioned in the release notes.
The same has been also acknowledged in this firebase-js-sdk issue.
PS - I am not sure if the comment I have updated in this PR is used to render the official firebase.google.com docs but looking at the metadata around the comment and noticing that firebase.google.comcode block links to this commented code, I am guessing that's the case.

Thanks @aviaryan, nice catch! Since this will affect the docs, I've set @kroikie and @egilmorez as reviewers. Once they approve, we can merge this in.

Hi, any updates on this? Can I do anything to help?

Hey @aviaryan sorry for the delay. I added a new comment. Once you address that, we can merge :)

@jhuleatt Thanks for getting back. I have made the config object changes. I also changed double quotes to single quotes because the rest of the file was using that.
I haven't made the excluded appId checker changes yet as I am waiting for your thoughts. Posted my comments here. https://github.com/firebase/quickstart-js/pull/422#discussion_r394561221

source: gharchive/pull-request

authors: aviaryan jhuleatt

repo: firebase/quickstart-js

license_type: permissive

license_source: bigquery


text:
:bug: Fixes head dom diffing

Solves: https://github.com/fireship-io/flamethrower/issues/45
I had introduced a bug not caught on the tests (in https://github.com/fireship-io/flamethrower/pull/28 ) that this fixes. It was preventing the loop from running and correctly identifying fresh/stale nodes beyond the first few while not otherwise sacrificing performance.
Also implements a simple short circuit on the lookbacks in the event old nodes or new nodes are undefined.

This still doesn't work, new head nodes are being added but the old nodes are no being removed

@shreyassanthu77 Are you sure?
https://user-images.githubusercontent.com/43540491/186188308-187a2828-6878-446a-aaff-fe34c7d49c34.mov

@shreyassanthu77 Are you sure?
Screen.Recording.2022-08-23.at.6.43.37.PM.mov

I am pretty sure, as you can see in the screenshot the title and some of style tags keeps re-adding

this is my setup:

used esbuild to build the package

and this is the result
https://user-images.githubusercontent.com/58223424/186193507-917132cd-5b05-4b49-8d6a-712c211f1f69.mp4

@shreyassanthu77 oh that makes more sense.
This change is not on my main branch (the one you're using). That would explain the difference in behaviors.

Ok that makes sense. I'm really sorry for wasting your time, I should've checked that. Sorry again and thank you :)

Finally, it works absolutely fine, thank you man

repo: fireship-io/flamethrower

license: MIT

license_source: github-api


text:
OS Package Repository

Currently, to upgrade Firezone you need to know there is a new release available. This most likely means subscribing to GitHub release notifications.
Instead, it would be useful if there is a package repository available for the various operating systems (eg. apt repo for Debian/Ubuntu, yum repo for RHEL and its derivatives). This will make the upgrade process much easier to manage as we can simply handle the upgrade as we would any other OS package. Also for those of us monitoring for available software upgrades on servers it is substantially easier.
For apt repositories, tools such as reprepro can be used to create/manage the relevant directory structure.

Thanks Chris for the suggestion. Unfortunately this may not be so straightforward with Omnibus since we bundle nginx, postgresql, and a couple dozen other utilities to ensure Firezone has a consistent environment to run within.
We have plans to clean this up and build native OS packages (see #378) that use the package manager's dependency tree instead of bundling all our dependencies with Omnibus. There's quite a bit of work involved here so it may be some time before we can get to it.

To be clear my suggestion wouldn't need the native OS packages to be used for supporting services; rather I suggest the existing packages are in a repository. An example of other software with the same setup I am suggesting is GitLab - it uses Ombibus also with its own packaged supporting services. The main thing is when package updates come out the OS package manager is aware that there is a new release.

Good point, I misunderstood. I knew Gitlab uses Omnibus but did not know they have a package server for the Omnibus builds. In that case, this is more doable in the short term.
Thanks for the suggestion!

Thanks @gbe0 for getting us set up with cloudsmith.io! Packages can be found here: https://cloudsmith.io/~firezone/repos/firezone/packages/
Keeping this issue to track:

[ ] Documentation on using this repo
[ ] Upload release packages from CI
[ ] Announcement in 0.5.0

@princemaple Think you could help with this one? Need:

[ ] CI action to push packages to cloudsmith.io on publish (I already have created the CLOUDSMITH_API_KEY secret), see https://github.com/cloudsmith-io/action). May need to retire last X packages due to space restraints.
[ ] Documentation updates:

[ ] Add a section to the Deploy guide showing how to install Firezone from package repo (in addition to manual install, automatic install)
[ ] Add section to Upgrade guide on what to do for version upgrades from repo

I can help with the documentation part.

source: gharchive/issue

repo: firezone/firezone


text:
bug(rust/phoenix-channel): flaky unit tests

Describe the bug
I saw this in CI just now and seen it locally a couple times but can't reproduce it
https://github.com/firezone/firezone/blob/main/rust/phoenix-channel/src/heartbeat.rs#L104
To Reproduce
Don't know how to reproduce it
Expected behavior
Expected phoenix-channel unit tests to be deterministic
Screenshots / Logs
returns_heartbeat_after_interval
https://github.com/firezone/firezone/actions/runs/11217278313/job/31178495534#step:6:4383
thread 'heartbeat::tests::returns_heartbeat_after_interval' panicked at phoenix-channel/src/heartbeat.rs:104:9:
assertion failed: elapsed >= INTERVAL
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

fails_if_not_provided_within_timeout
This failed within the same minute on 2 separate runners (Windows 2019 and 2022), I wonder if it could be related to a noisy neighbor in the GitHub VMs? Could the test fail if our threads don't get scheduled quick enough?
https://github.com/firezone/firezone/actions/runs/11334462513/job/31520713665#step:6:3639
thread 'heartbeat::tests::fails_if_not_provided_within_timeout' panicked at phoenix-channel\src\heartbeat.rs:152:38:
timeout should not resolve

https://github.com/firezone/firezone/actions/runs/11334462513/job/31520714119
thread 'heartbeat::tests::fails_if_not_provided_within_timeout' panicked at phoenix-channel\src\heartbeat.rs:152:38:
timeout should not resolve

Platform (please complete the following information)

Component (i.e. macOS client / Linux client / Gateway / Admin portal): phoenix-channel
Firezone Version (e.g. 1.0.0 or N/A): main
OS and version: (e.g. Ubuntu 22.04 or N/A): Ubuntu, probably Windows
Deployment method: (e.g. Docker / Systemd / App Store or N/A): N/A

Additional context

I ran the test binary in a loop 1000 times and it didn't fail :(

Saw it just now on another unit test of phoenix-channel. Updated the original post

Another pair where both Windows runners, and only Windows, failed.
https://github.com/firezone/firezone/actions/runs/11335501832/job/31523768987
https://github.com/firezone/firezone/actions/runs/11335501832/job/31523769151

@thomaseizinger I think this one has your new logging in it https://github.com/firezone/firezone/actions/runs/11349838342/job/31567097532#step:6:4301

These two
https://github.com/firezone/firezone/actions/runs/11349851924/job/31567118582#step:6:4293
https://github.com/firezone/firezone/actions/runs/11349851924/job/31567123537#step:6:4299

Testing on the Macbook in Windows, even at TIMEOUT * 5 it fails from time to time.

Made a test program and I don't see Windows undershooting the sleeps, although I do see a granularity of about 15 ms.
Requested sleep time --> Actual
8000 us --> 10395 us
8000 us --> 29510 us
8000 us --> 16665 us
8000 us --> 15756 us
8000 us --> 15213 us
9000 us --> 15455 us
9000 us --> 30821 us
9000 us --> 15081 us
9000 us --> 16063 us
9000 us --> 16640 us
10000 us --> 15596 us
10000 us --> 15168 us
10000 us --> 15583 us
10000 us --> 30643 us
10000 us --> 15224 us
11000 us --> 16021 us
11000 us --> 15334 us
11000 us --> 16723 us
11000 us --> 15126 us
11000 us --> 15618 us
12000 us --> 15156 us
12000 us --> 15972 us
12000 us --> 14683 us
12000 us --> 15784 us
12000 us --> 15395 us

But granularity could still explain it.

We poll both futures and expect the heartbeat to time out in 5 ms.
15 ms later, both futures are ready, Windows wakes us up, and we poll the timeout and panic.
I see this millisecond time scale is just for unit tests. I'll open a PR commenting that it's Windows' fault and increasing the smallest sleep unit to 15 ms.

Ah here are the answers to #7061! Thank you for digging into this. Could knowledge to document. cc @conectado

authors: ReactorScram thomaseizinger


text:
feat(relay): reduce packet drops

There is another channel which we didn't yet increase in size, the one between the allocation and the main task loop. Increasing to 1000 means each allocation can potentially buffer 65MB of data. With the biggest port range (16383 allocations), that would be a theoretical memory consumption of ~ 1TB. But, this would imply that we have 16383 connected clients that all send data at max speed, saturating our downlink and our uplink is somehow ridiculously small. As long as up and downlink are roughly within the same ballpark figure, it should be impossible to actually fill up these buffers.
I suspect that the current packet drops of the iperf test are happening because on localhost, sending 10 UDP packets is so quick that a tokio is unable to wake up the task in time to empty the queue.
In addition to the increased channel size, I've also added a check for the other channels to avoid writing to them in case they are not ready for some reason.

Also before merging let's test running the relayed flow integration test a few times just to double check it works before moving on.

Yep, sounds good!

Updated to get CI checks to run

authors: jamilbk thomaseizinger


text:
feat(windows): generate device ID and persist it on disk

Relating to #2697 and #2711

Had to move a bunch of files to hide the whole project from the Ubuntu CI. Otherwise it would have been a small change.


text:
Get familiar with GRiP/OpenCV

GRiP is the GUI version of OpenCV, the image processing software. The website is here (https://wpiroboticsprojects.github.io/GRIP/#/) and I think it's already installed on one or both of the ROBO-01 or ROBO-02 computers. Try it out with sample images to get familiar with it. These can include the examples provided by FRC for vision this year: https://files.slack.com/files-pri/T74UGMJGG-FSCQMHJMA/download/2020_vision_example.zip

This is the link to GRiP info from FRC: https://docs.wpilib.org/en/latest/docs/software/vision-processing/grip/introduction-to-grip.html
Sadly, it's still not accessible from the HACTC network... @jch13 :(

Going to consider GRIP familiarity complete.


text:
Select Effects

Hi,
it would be nice to get an option to let start the boot effects of Hyperion like the Rainbow mood, Rainbow Swirl, Blue mood blobs and all the other ones.

I would love this too @firsttris if it is possible?

@firsttris do you still support this plug-in? I would be very keen to get this functionality added.

Thanks for the reply :) I am very new to this sort of stuff, I will take a bit of a look and see if I can work it out. Worst case I’ll see if I can get someone to help me.

repo: firsttris/homebridge-hyperion-light


text:
Remove execute_close/handle_execute_close :fire:

Done in https://github.com/fishcakez/db_connection/commit/cca87d11d09c963b106ee6a0a460b3f603810d6a


text:
Define source tables

Related: https://github.com/fishtown-analytics/dbt/issues/790
Presently, the link between source data and dbt models is pretty tenuous. dbt should provide a mechanism for defining source tables, and users should be able to select from these source tables with a mechanism similar to ref. Further, these source tables should be documented alongside other dbt resources.
Proposed Syntax
sources:
  - name: snowplow
    loader: snowplow # This is new, see below
    loaded_at_field: etl_tstamp # This is new, see below
    description: "A snowplow dataset"
    freshness: # This is new, see below
      warn_after: {count: 12, period: hour}
      error_after: {count: 24, period: hour}
    tables:
        - name: event
          description: An immutable log of events collected by Snowplow
          loaded_at_field: _etl_tstamp # Override value from top-level source
          sql_table_name: snowplow.event
          columns:
            - name: collector_tstamp
              description: Timestamp for the event recorded by the collector

            - name: domain_userid
              description: User ID set by Snowplow using 1st party cookie
              tests:
                  - unique

        - name: web_page
          description: "{{ docs('snowplow_web_page') }}"
          sql_table_name: "{{ var('snowplow:web_page') }}"
          columns:
            - name: event_id
              description: {{ docs('snowplow_web_page.event_id') }}

Notes
For more information on the description and columns fields, check out the discussion on the new schema.yml syntax.
There are two new constructs here:
sql_table_name
This field will be responsible for pointing to a table in the warehouse. This syntax works for:
BigQuery:

Syntax: project-name.dataset.tablename
can select across projects

Snowflake:

Syntax: database.schema.tablename
can select across databases

pg/Redshift:

Syntax: schema.tablename
can not select across databases. Cross-db references should not however be enforced!

Rather than trying to construct the table name automatically, users will need to enter the exact identifier for the source table.
loader
This will be used for documentation. Loader can be something like Airflow, Stitch, Fivetran, etc. User supplied.
loaded_at_field
This field indicates which timestamp field in the source table should be used as the "loaded at" timestamp. This varies by ETL loader, but for loaders which do supply such a field, we can calculate how long ago certain sources were loaded. This field can be specified at the source level or at the table level. If specified at the table level, the value overrides the value from the source if present.
freshness
This field describes the acceptable latency for source tables. This field can be provided at the source or table level. If provided at the source level, it should apply to all of the tables in the source. If provided at the table level, it should override any freshness configuration at the source level. The freshness value for a table can be set to null to override the value specified in the source.
Acceptable formats:
    freshness:
      warn_after:
        count: 12
        period: hour
      error_after:
        count: 24
        period: hour

Acceptable periods are minute, hour, and day.
Usage
To select from a source table, users can use the source function, analogous to ref. This function accepts two arguments: a source and a table. For example:
-- models/snowplow/snowplow_sessions_xf.sql

select * from {{ source('snowplow', 'event') }}

will render to:
select * from snowplow.event

When source() is used, an edge will be added to the graph. This will allow model selection like: "run everything that depends on Snowplow data". In the above example snowplow_event is derived from the name: parameter of the first table definition.
Ex:
# run all models that touch Snowplow data
$ dbt run --models source:snowplow+

See #1014 for info about the selection syntax shown above.
See #1240 for info about model freshness

I like this a lot. I have a couple of questions that popped into my head from reading this that we'll likely have to answer before completing this feature:

what does the CLI syntax look like for selecting everything that depends on snowplow source tables? I don't think there's a way to do that with --models today because our hierarchy there is different...

what is the name of the file that contains this yaml? sources.yml? can there be many of these files? can packages define their own sources which then get namespaced as packages.source_name.table_name?

this looks great.
the only thing i'm not 100% sure on is sql_table_name. this is kind of like alias, right? but it also includes a schema, database, or other namespace. i wonder if it's better to define this like other relations, where you can specify a identifier, schema, and/or database. that way when we ref it we already have a relation in place.
so instead of sql_table_name, we'd have:
sources:
  - name: snowplow
    description: "A snowplow dataset"
    tables:
        - name: snowplow_event
          description: An immutable log of events collected by Snowplow
          schema: snowplow
          identifier: event
          columns:
            - name: collector_tstamp
              description: Timestamp for the event recorded by the collector

            - name: domain_userid
              description: User ID set by Snowplow using 1st party cookie
              tests:
                  - unique

        - name: web_page
          description: "{{ docs('snowplow_web_page') }}"
          # this used to be one var, which is unfortunate! hard to convert.
          # sql_table_name: "{{ var('snowplow:web_page') }}"
          schema: snowplow
          identifier: "{{ var('snowplow:web_page') }}"
          columns:
            - name: event_id
              description: {{ docs('snowplow_web_page.event_id') }}

That was what the initial version looked like, but databases are different in terms of how they address namespace--do you need to specify a database as well or just a schema? is it even possible to select from a different database? verbiage is different also.
Is there a benefit to actually defining database and schema for sources specifically instead of just having a string that defines where the table can be addressed? Since dbt doesn't create or maintain them, it only needs to know how to write the select statement that gets data out of them.

@jthandy

do you need to specify a database as well or just a schema? is it even possible to select from a different database?

Depends on the warehouse type. For Redshift and Postgres, you can't select from a different database. For Snowflake, you could. And, I think in Bigquery you have to specify the project.

verbiage is different also.

We made some decisions in the relations rollout to accommodate this, the big one being that we use schema everywhere even though the schema is actually a dataset in bigquery. So the only actual difference is that in Bigquery you have to specify a project, whereas in the other warehouses you may be able to optionally specify a database.

Is there a benefit to actually defining database and schema for sources specifically instead of just having a string that defines where the table can be addressed? Since dbt doesn't create or maintain them, it only needs to know how to write the select statement that gets data out of them.

This is true today, but a lot of our internal API for inspecting relations depends on this code being structured a certain way -- so for example you can imagine if we want to inspect the schema of a source table in Bigquery, we actually make an API call instead of just running some arbitrary SELECT.
OFC we could always convert this string back to a relation, it's just messy and there's room for bugs there.

All that make sense. I think that we would have to require database on snowflake and bq for every relation. As long as we're comfortable making that kind of thing conditional then makes sense.

I'm definitely leaning more towards constructing the SQL identifier from a database + schema + table name. Generally, I think there are some real questions to answer around implementation. We also need to figure out how these things fit into --models selection syntax, and we'll need to update the (prospective) docs site to account for them too.
I think we should kick this out of the 0.11.0 milestone, but we should definitely continue to shore up our thinking around implementation in this issue

@drewbanin would be super useful if we could set the location of the source (dataset), similar to how we can define that in profile.yml, this is particularly useful for BigQuery datasets which live in a single region - currently dbt queries only using multiregion args, ie. EU US
Please see this Slack thread for a concrete example:
https://getdbt.slack.com/archives/C99SNSRTK/p1592241999380600
Any workarounds (apart from creating a multi-region dataset) would be appreciated.

Hey @cosoare, do you mind opening a new issue and include all the relevant details? We can continue the discussion there. I want to better understand the pros/cons of single-region vs. multi-region datasets.

Just pasting in the thread details from Slack since they disappear on us :)

Is there a way to specify location for BigQuery datasets, specifically for source datasets? For context, I’m facing an issue where I can’t utilise a dataset I’ve created for sources since it’s a single region ie. europe-west2, and dbt is looking for EU

You can specify database in your model configuration. But this assumes that your authenticated user account has the necessary permissions for both projects

Ah, sorry I’ve just re-read your question. Actual location? No I don’t think so.

hmm… so I need to setup cross-region supported datasets? Not ideal :disappointed:

No you can do cross region as long as its within EU AFAIK

The problem with this is the assumption dbt makes that a BigQuery dataset will be cross-region (EU, US) hence when trying to run dbt run on a dataset that is not EU but rather a single region europe-west2 dbt fails.

You can indeed feel free to create a new issue for us to discuss this change, but I don't really think that dbt can help you here! BigQuery disallows querying datasets across regions. If you did provide a location for source datasets in BQ, there isn't really anything dbt could do with that information. The source data already lives in a specific region, and short of copying that data into a differently named dataset in a different region (something we would not want to do), I don't think there's anything dbt could do to make this work!
So, please pop open a new issue to discuss in further detail if you'd like. In particular, I'd like to know what you think dbt should be doing with these dataset locations if provided!

authors: cmcarthur cosoare drewbanin jtcohen6 jthandy

repo: fishtown-analytics/dbt


text:
catalog generation for bigquery

@drewbanin has something partially working for this

This is a one-off function from a little bit of experimentation I did recently.
# adapters/bigquery/impl.py

    @classmethod
    def get_catalog(cls, profile, project_cfg, manifest):
        # schemas = cls.get_existing_schemas(profile, project_cfg)
        schemas = list({node.to_dict()['schema'] for node in manifest.nodes.values()})

        columns = []

        for j, schema_name in enumerate(schemas):
            relations = cls.list_relations(profile, project_cfg, schema_name)
            for i, relation in enumerate(relations):
                cols = cls.get_columns_in_table(profile, project_cfg, schema_name, relation.name)
                for col_index, col in enumerate(cols):
                    columns.append({
                        "table_schema": relation.schema,
                        "table_name": relation.name,
                        "table_type": relation.type,
                        "table_comment": None,
                        "column_name": col.name,
                        "column_index": col_index,
                        "column_type": col.data_type,
                        "column_comment": None
                    })

        return dbt.clients.agate_helper.table_from_data(columns)

authors: cmcarthur drewbanin


text:
adapters as objects (#961)

Create adapters as singleton objects instead of classes, resolves #961.
Adapters now store the config on themselves when they're generated, and the factory returns singleton instances rather than types.
It does seem that the whole relation creation API could be changed to be a bit more streamlined - we could have relation creates go through the adapter directly and then we wouldn't need a proxy, but that would break a lot of existing macros. I don't think it's worth the effort if this proxy is good enough.
Most of this PR is converting method(cls, config, ...) to method(self, ...). The most substantial aspects are the changes to the factory code and the wrapper/relations quoting logic - I spent a lot of time getting quoting-related tests to pass.

can you elaborate on:

we could have relation creates go through the adapter directly and then we wouldn't need a proxy

authors: beckjake cmcarthur


text:
Support BigQuery OAuth using a refresh token and client secrets

resolves #2344
Description
This PR adds support for the bearer connection method on BQ. When this method is specified, a client_id, client_secret, refresh_token and token_uri must also be provided. Given these secrets, dbt will mint access tokens to authorize BigQuery queries.
TODO

[ ] Should we rename bearer to oauth-secrets as the auth method?
[x] Write tests
[x] Changelog entry

Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

I'm pretty excited about this feature!  Let me know if you need any help with an integration test case (whether that's feasible).  Currently, the BIGQUERY_SERVICE_ACCOUNT_JSON is passed in as an environment variable, so maybe a similar variable could be something like BIGQUERY_REFRESH_TOKEN_JSON, which would contain the parameters to the GoogleCredentials.Credentials method.

authors: drewbanin heisencoder


text:
stg_stripe__subscription

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
The model is still using stg_stripe__subscription. This is throwing error as the table doesn't not exist . It has been changed to stg_stripe__subscription_history
Relevant error log or model output
STRIPE.SUBSCRIPTION' does not exist or not authorized.

Expected behavior
The model is expected to run fine
dbt Project configurations
stripe_database: FIVETRAN_DB
stripe_schema: STRIPE
Package versions
0.7.2
What database are you using dbt with?
snowflake
dbt Version
1.1.1
Additional Context
No response
Are you willing to open a PR to help address this issue?

[X] Yes.
[X] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

As the subscription table is deprecated, isn't it better to have model with subscription _history ?

Hi @lijol the model name is actually stg_stripe__subscription (although with the variable it will pull from the history source, but will filter for the latest record). If you try dbt run -s +stg_stripe__subscription you should see success. Let me know!
Additionally, I agree that since the non history table has been deprecated it would make sense for the default of that variable to be true. However, I believe the deprecation is only for new connectors. Since we have a lot customers still on the older version of the connector, we don't want to break their runs. That being said, we are planning updates to our Stripe package next quarter and will be adjusting the default value of the variable during those next breaking changes!

thanks @fivetran-joemarkiewicz this worked.
by default making it true will be very helpful

authors: fivetran-joemarkiewicz lijol


text:
1.1.10 panic: unknown connector service: business_central crashes on plan

Describe the bug
The business central connector is a preview connector.  I was testing upgrading our TF to the latest version but it crashes.
fivetran = {
source  = "fivetran/fivetran"
version = "0.7.3". (works / previous)
version = "~> 1.1.10" (crashes)
To Reproduce
resource "fivetran_connector" "business_central_connector" {
  group_id           = data.aws_ssm_parameter.fivetran_group_id_external_id_versioned.value
  service            = "business_central"
  run_setup_tests    = true
  trust_fingerprints = true
  trust_certificates = true

  destination_schema {
    name = local.business_central_connector_name
  }
}

Expected behavior
Not crash.
Logs & Output
plan output:
...
fivetran_connector.amplitude_connector: Refreshing state... [id=xya]

Planning failed. Terraform encountered an error while generating this plan.

╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the plugin6.(*GRPCProvider).ReadResource call. The plugin logs may contain more details.
╵
╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the plugin6.(*GRPCProvider).ReadResource call. The plugin logs may contain more details.
╵
╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the plugin6.(*GRPCProvider).ReadResource call. The plugin logs may contain more details.
╵
╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the plugin6.(*GRPCProvider).ReadResource call. The plugin logs may contain more details.
╵

Stack trace from the terraform-provider-fivetran_v1.1.10 plugin:

panic: unknown connector service: `business_central`

goroutine 15 [running]:
github.com/fivetran/terraform-provider-fivetran/fivetran/framework/core/model.getDestinationSchemaValuesMap({0x140003b9550, 0x10}, {0x1400011c288, 0x14})
        github.com/fivetran/terraform-provider-fivetran/fivetran/framework/core/model/connector.go:344 +0x578
github.com/fivetran/terraform-provider-fivetran/fivetran/framework/core/model.getDestinationSchemaValue({0x140003b9550, 0x10}, {0x1400011c288, 0x14})
        github.com/fivetran/terraform-provider-fivetran/fivetran/framework/core/model/connector.go:337 +0x150
github.com/fivetran/terraform-provider-fivetran/fivetran/framework/core/model.(*ConnectorResourceModel).ReadFromContainer(0x1400011e200, {{0x140003b9510, 0xe}, {0x1400011c288, 0x14}, {0x1400011c2b8, 0x15}, {0x14000628300, 0x24}, {0x1400011c240, ...}, ...})
        github.com/fivetran/terraform-provider-fivetran/fivetran/framework/core/model/connector.go:229 +0x12c
github.com/fivetran/terraform-provider-fivetran/fivetran/framework/core/model.(*ConnectorResourceModel).ReadFromResponse(_, {{{0x140003b9478, 0x7}, {0x0, 0x0}}, {{{0x140003b9510, 0xe}, {0x1400011c240, 0x11}, {0x140003b9550, ...}, ...}, ...}})
        github.com/fivetran/terraform-provider-fivetran/fivetran/framework/core/model/connector.go:132 +0x84
github.com/fivetran/terraform-provider-fivetran/fivetran/framework/resources.(*connector).Read(0x14000114058, {0x1039761c0, 0x1400088cf00}, {{{{0x10397ae58, 0x14000f6cf30}, {0x10385bb20, 0x140007e6480}}, {0x10397c788, 0x140007b62d0}}, 0x1400028e038, ...}, ...)
        github.com/fivetran/terraform-provider-fivetran/fivetran/framework/resources/connector.go:197 +0x578
github.com/hashicorp/terraform-plugin-framework/internal/fwserver.(*Server).ReadResource(0x140000e8000, {0x1039761c0, 0x1400088cf00}, 0x1400088cf90, 0x14000793540)
        github.com/hashicorp/terraform-plugin-framework@v1.4.2/internal/fwserver/server_readresource.go:101 +0x4a4
github.com/hashicorp/terraform-plugin-framework/internal/proto6server.(*Server).ReadResource(0x140000e8000, {0x1039761c0?, 0x1400088cdb0?}, 0x1400060e640)
        github.com/hashicorp/terraform-plugin-framework@v1.4.2/internal/proto6server/server_readresource.go:55 +0x1a4
github.com/hashicorp/terraform-plugin-mux/tf6muxserver.(*muxServer).ReadResource(0x103976118?, {0x1039761c0?, 0x1400088ca80?}, 0x1400060e640)
        github.com/hashicorp/terraform-plugin-mux@v0.12.0/tf6muxserver/mux_server_ReadResource.go:35 +0x188
github.com/hashicorp/terraform-plugin-go/tfprotov6/tf6server.(*server).ReadResource(0x140004cdc20, {0x1039761c0?, 0x1400088c2a0?}, 0x14000099320)
        github.com/hashicorp/terraform-plugin-go@v0.19.0/tfprotov6/tf6server/server.go:787 +0x3e8
github.com/hashicorp/terraform-plugin-go/tfprotov6/internal/tfplugin6._Provider_ReadResource_Handler({0x103938620?, 0x140004cdc20}, {0x1039761c0, 0x1400088c2a0}, 0x140001b2000, 0x0)
        github.com/hashicorp/terraform-plugin-go@v0.19.0/tfprotov6/internal/tfplugin6/tfplugin6_grpc.pb.go:431 +0x170
google.golang.org/grpc.(*Server).processUnaryRPC(0x14000276000, {0x10397b320, 0x140002949c0}, 0x1400089e000, 0x1400070ac00, 0x103f3bbe8, 0x0)
        google.golang.org/grpc@v1.57.0/server.go:1360 +0xc88
google.golang.org/grpc.(*Server).handleStream(0x14000276000, {0x10397b320, 0x140002949c0}, 0x1400089e000, 0x0)
        google.golang.org/grpc@v1.57.0/server.go:1737 +0x82c
google.golang.org/grpc.(*Server).serveStreams.func1.1()
        google.golang.org/grpc@v1.57.0/server.go:982 +0x84
created by google.golang.org/grpc.(*Server).serveStreams.func1
        google.golang.org/grpc@v1.57.0/server.go:980 +0x16c

Error: The terraform-provider-fivetran_v1.1.10 plugin crashed!

This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.

Provide terraform CLI output on plan | apply. If it is possible, please, refer to this guide to enable debug output.
Plugin version:
1.1.0
Additional context
1.0.0 also fails
...
Planning failed. Terraform encountered an error while generating this plan.

╷
│ Error: read error
│
│   with fivetran_connector.business_central_connector,
│   on connector-business-central.tf line 4, in resource "fivetran_connector" "business_central_connector":
│    4: resource "fivetran_connector" "business_central_connector" {
│
│ unknown service: `business_central`

Thank you for this report. Working on it!

I found the issue: the problem is that this connector is in Private Preview state. And it's not included in our Open API schema.
We are working on this issue, and the service will be included into OAS with the next release I believe.
Previously we didn't check if service is represented in OAS so it was working for older versions of Terraform.

Fix merged, release v1.1.11.

fixed!

repo: fivetran/terraform-provider-fivetran


text:
Issue on page /examples/02_all_pass_filter.html

I defined an add-drop like:
ring, _ = sax.circuit(
netlist={
"instances": {
"lft": coupler,
"top": waveguide,
"bot": waveguide,
"rgt": coupler,
},
"connections": {
"lft,in1": "top,in0",
"lft,out1":"bot,in0",
"rgt,in1": "top,out0",
"rgt,out1":"bot,out0",
},
"ports": {
"in0": "lft,in0",
"in1": "rgt,in1",
"out0": "lft,out0",
"out1": "rgt,out1",
},
}
)
I simulate the behaviour like below:
wl = jnp.linspace(1.54, 1.56, 10001)
result = ring(wl=wl, lft={'coupling': 0.02}, top={'length': 100.0,'loss':0.00155}, bot={'length': 100.0,'loss':0.00155}, rgt={'coupling': 0.02})
print(result.values().sizeof())
plt.plot(1e3wl, jnp.abs(result['in0', 'out0'])**2, label="in0->out0")
plt.plot(1e3wl, jnp.abs(result['in0', 'in1'])**2, label="in0->in1", ls="--")
plt.plot(1e3*wl, jnp.abs(result['out0', 'out1'])**2, label="out0->out1", ls="--")
plt.xlabel("λ [nm]")
plt.ylabel("T")
plt.grid(True)
plt.figlegend(ncol=2, loc="upper center")
plt.show()
Whatever the backend I obtain a transmission greater than 1 or 2

I visualized the netlist with saxviz.visualize_netlist and got this:

clearly the ports on coupler rgt are doubly connected.
you can fix it like this:
netlist={
    "instances": {
        "lft": "coupler",
        "top": "straight",
        "bot": "straight",
        "rgt": "coupler",
    },
    "connections": {
        "lft,in1": "top,in0",
        "lft,out1": "bot,in0",
        "rgt,in1": "top,out0",
        "rgt,out1": "bot,out0",
    },
    "ports": {
        "in0": "lft,in0",
        "in1": "rgt,in0",
        "out0": "lft,out0",
        "out1": "rgt,out0",
    },
}

models = {
    "straight": sax.models.straight,
    "coupler": sax.models.coupler,
}

ring, _ = sax.circuit(
    netlist=netlist,
    models =models
)

which gives the following netlist visualization:

And the following result:

authors: flaport philippevelha

repo: flaport/sax


text:
Re-imagine landing page

The content of the landing page needs restructuring

The recently added/recently updated is not relevant to normal users

It's relevant to admins and news outlets, so we should keep it, but does not have to be on the main page

Is it time to not show verified on there anymore?
Would a tabbed layout work better?
Could kill the more button somehow?

If I can add a bit of additional information, the idea is to provide a simpler navigation structure. Today the navigation with the MORE button makes for a slightly tedious nav experience: 1) Pick a MORE button 2) look/page/look again 3) Back button to pick another MORE button.
If there was some type of tabbed approach (there are a few ways to do this) the user could just go tab, look, tab, look, etc. It's just an easier way to quickly go through the apps. It also has the benefit of removing all of the MORE buttons.
Note, depending on how many apps are in each section, they may need to page but the goal is to have the number of items in each tab area larger than today so depending on how you sort the items in each tab, the user could see quite a few before needing to page. The goal is that MOST of the time, the user would just need to use the Tabs (with maybe some scrolling)

This is done now

authors: razzeee scottjenson

repo: flathub-infra/website


text:
finish-args-not-defined error with finish-args:[]

Using finish-args:[] used to work , but recently this lint started to happen finish-args-not-defined.
Maybe this is correct and expected, but I'm just opening the issue because the behavior has changed.
The fix/workaround now is to to populate finish-args with something even if its not needed.

You need an exception like this:
https://github.com/flathub/flatpak-builder-lint/blob/655d3fbeb53f11dcd54472851aec70472fc19451/flatpak_builder_lint/staticfiles/exceptions.json#L1179
Regular apps are assumed to always have a finish-arg.

I see thanks

I see thanks

Please make a PR against that file, following the example.

The test was written for checking the manifest but lately linter has been checking the generated metadata which changes things a bit.

I added a fix for this for baseapps and extensions since those two can never have finish-args.
https://github.com/flathub/flatpak-builder-lint/pull/211/commits/400cdb64b5045c545eea81b58bdd4f4962ca8837
The same cannot be said for console applications because they may or may not have them.
Eg. https://github.com/flathub/dev.paullee.scraterpreter.Scrapec/blob/master/dev.paullee.scraterpreter.Scrapec.json has type=console-application but comes with finish-args

authors: bbhtt hfiguiere sigmaSd

repo: flathub/flatpak-builder-lint


text:
Use translated AppStream metadata

Currently, English-only AppStream metadata are displayed for apps. Consider using translated strings if available.

https://github.com/flathub/website/pull/88

Oops, I did not notice that PR. Thanks! :-)

authors: AsciiWolf razzeee

repo: flathub/website


text:
readJSONFileSync

I think a synchronous version of readJSONFile would be really useful, since you can inline it with stuff.
Any objections?

This looks good to me. I've cherry-picked your last commit (looks like the first one is in master already). Now in master as 23f3aecf088a510247f7324ecc662fd144502856.

authors: jesusabdullah mmalecki

repo: flatiron/utile

license: mit


text:
Handle user-provided log densities that throw exceptions

This came up in a discussion with @gil2rok during #39, but applies to all of our algorithms. The user provided log_density_gradient function may throw an exception (we may even expect it to, e.g. if the parameters are out of support).
Currently, if this happens, the exception is propagated all the way up out of the algorithm and into the caller's code. This is probably not what we want to do. Instead, we could work as Stan does and treat any exception in the log density calculation as resulting in a rejection (assuming the algorithm contains an accept-reject step)

Stan separates two kinds of errors.  If there are indexing errors, we tend to throw things that stop the algorithm because those aren't recoverable.  If they are numerical errors like underflow, we treat them as rejections in the Stan algorithms.   One thing to do would be to convert an exception into a negative infinite log density, which in any Metropolis setting will reject.
reject.stan
parameters {
  vector[2] y;
}
model {
  y[1:3] ~ normal(0, 1); // reject
}

Running this produces an error and sampling doesn't happen:
RuntimeError: Error during sampling:
Exception: vector[min_max] max indexing: accessing element out of range. index 3 out of range; expecting index to be between 1 and 2 (in 'reject.stan', line 5, column 2 to column 24)

reject2.stan
parameters {
  vector<upper=0>[2] y;
}
model {
  y ~ exponential(1);  // out of range
}

Running this produces a bunch of rejections of draws:
RuntimeError: Error during sampling:
        Exception: exponential_lpdf: Random variable[1] is -0.155166, but must be nonnegative! (in 'reject2.stan', line 5, column 2 to column 21)
	Exception: exponential_lpdf: Random variable[1] is -4.05851, but must be nonnegative! (in 'reject2.stan', line 5, column 2 to column 21)
	Exception: exponential_lpdf: Random variable[1] is -0.75561, but must be nonnegative! (in 'reject2.stan', line 5, column 2 to column 21)
	Exception: exponential_lpdf: Random variable[1] is -3.93886, but must be nonnegative! (in 'reject2.stan', line 5, column 2 to column 21)
	Exception: exponential_lpdf: Random variable[1] is -0.16518, but must be nonnegative! (in 'reject2.stan', line 5, column 2 to column 21)
	Exception: exponential_lpdf: Random variable[1] is -0.633151, but must be nonnegative! (in 'reject2.stan', line 5, column 2 to column 21)
	Exception: exponential_lpdf: Random variable[1] is -1.43768, but must be nonnegative! (in 'reject2.stan', line 5, column 2 to column 21)
	Exception: exponential_lpdf: Random variable[1] is -0.61375, but must be nonnegative! (in 'reject2.stan', line 5, column 2 to column 21)
...

If it could've gotten past initialization, it would've given very different answers.

We could try to separate those errors at the python level (e.g., we could have it so IndexError and others are not caught, but ArithmeticError and RuntimeError are). There is a well-established hierarchy of built in error types in Python.
Unfortunately, I believe as implemented today, BridgeStan raises all errors as RuntimeErrors, but other user-defined classes could follow this pattern

authors: WardBrian bob-carpenter

repo: flatironinstitute/bayes-kit


text:
TimePicker does not function correctly

Duplicate Check

[X] I have searched the opened issues and there are no duplicates

Describe the bug
This is a bug & feature report :-)
Using v0.23.1 and the TimePicker control:

Trying the TimePicker sample code from the control's doc (https://flet.dev/docs/controls/timepicker/) works once for the first time only. After confirming picked time and getting back the main page, clicking the button again to pick time does nothing, instead of presenting the time selection window again.
In the control's doc, the displayed graphic shows AM/PM below the hours:minutes. When running the sample code, this is not displayed.
Is there a way to tell the dial not to display two dials for the hour selection? Instead, pass a parameter that will instruct the code to either present the 12 or the 24 hours dial.
Is there a way to embed the TimePicker control in a page (displayed all the time as part of an AlertDialog, with additional fields) without the need to have a button to pop it?
Thanks!

Code
See sample code in the control's doc
To reproduce
See sample code in the control's doc
Expected behavior
No response
Screenshots
No response
Operating System
Windows
Operating system details
Win11
Flet version
0.23.1
Regression
I'm not sure / I don't know
Suggestions
Fix :-)
Additional details
No response

About the 1 first point I don't know why but the problem seems to lie in the lambda.
Try this workaround:
`
def my_open(e):
page.open(time_picker)
page.update()
page.add(
    ft.ElevatedButton(
        "Pick time",
        icon=ft.icons.TIME_TO_LEAVE,
        on_click=my_open,
    )
)

`

Looks like v0.23.2 fixed issue #1.
Will appreciate getting answers to issues 2,3,4.
Thanks!

Yep, point 1 has been fixed.
For the other points, I suggest you make some searches on how this is done in Flutter, and if you find something, then open a discussion, so we can discuss on its implementation here. (Flutter TimePicker Widget)
Closing this issue resolved.

authors: LucaPrg mottibz ndonkoHenri

repo: flet-dev/flet


text:
Wrapped --codesign-identity & --add-binary for flet pack

Wrapping --codesign-identity & --add-binary for flet pack allows end to end code signing on macOS. This avoids having to use pyinstaller directly which leads to app naming issues.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant joshvisionalgo


text:
update auth tag

Description
When a Log Analytics cred is created in cred manager, it has the provider tag azure_log set by default. The Instance Log Analytics policy is filtering by the azure_rm tag.
Issues Resolved
[List any existing issues this PR resolves]
Contribution Check List

[x] All tests pass.
[x] New functionality includes testing.
[x] New functionality has been documented in the README if applicable
[x] New functionality has been documented in CHANGELOG.MD

          1 Warning

:warning:
Should this include readme changes

  Generated by :no_entry_sign: Danger

authors: flexera-ci srpomeroy


text:
Erro "ENOENT: no such file or directory, scandir 'C:\webOS_TV_SDK\Simulator'" ao tentar executar simulador webOS TV no Windows

I'm trying to run my webOS TV application on Windows using the command npx rnv run -p webos, but I get the following error:
error: ⨯ ○ run: Error: ENOENT: no such file or directory, scandir 'C:\webOS_TV_SDK\Simulator'
PS D:\free-lancers\my_smart_app> npx rnv run -p webos

┌─────────────────────────────────────────────────────────────────┐
│ ██████╗ ███████╗███╗   ██╗ █████╗ ████████╗██╗██╗   ██╗███████╗ │
│ ██╔══██╗██╔════╝████╗  ██║██╔══██╗╚══██╔══╝██║██║   ██║██╔════╝ │
│ ██████╔╝█████╗  ██╔██╗ ██║███████║   ██║   ██║██║   ██║█████╗   │
│ ██╔══██╗██╔══╝  ██║╚██╗██║██╔══██║   ██║   ██║╚██╗ ██╔╝██╔══╝   │
│ ██║  ██║███████╗██║ ╚████║██║  ██║   ██║   ██║ ╚████╔╝ ███████╗ │
│ ╚═╝  ╚═╝╚══════╝╚═╝  ╚═══╝╚═╝  ╚═╝   ╚═╝   ╚═╝  ╚═══╝  ╚══════╝ │
│ $ rnv run -p webos                                              │
└─────────────────────────────────────────────────────────────────┘
info: Current engine: @rnv/engine-rn-web (D:\free-lancers\my_smart_app\node_modules\@rnv\engine-rn-web)
task: ○ run ↺1
task: ○ configure ↺1
task: ○ platform configure ↺1
task: ○ project configure ↺1
task: ○ workspace configure ↺1
task: ✔ workspace configure
task: ○ app configure ↺1
info: Current app config: app
task: ✔ app configure
info: D:\free-lancers\my_smart_app\node_modules\@react-native-community\cli-platform-ios\build\tools\listIOSDevices.js overridden by: \@rnv\config-templates\pluginTemplates\@react-native-community\cli-platform-ios\overrides@12.3.6.json
info: D:\free-lancers\my_smart_app\node_modules\@react-native-community\cli-platform-ios\build\tools\listIOSDevices.js overridden by: \@rnv\config-templates\pluginTemplates\@react-native-community\cli-platform-ios\overrides@12.3.6.json
info: D:\free-lancers\my_smart_app\node_modules\@react-native-community\cli-platform-ios\build\commands\runIOS\index.js overridden by: \@rnv\config-templates\pluginTemplates\@react-native-community\cli-platform-ios\overrides@12.3.6.json
info: D:\free-lancers\my_smart_app\node_modules\@react-native-community\cli\build\bin.js overridden by: \@rnv\config-templates\pluginTemplates\@react-native-community\cli\overrides.json
task: ✔ project configure
info: Current Build Scheme: debug
task: ○ sdk configure ↺1
task: ✔ sdk configure
task: ✔ platform configure
info: Found custom assetSources at D:\free-lancers\my_smart_app\node_modules\@flexn\assets-renative-outline\assets\webos. Will be used to generate assets.
task: ✔ configure
info: Your webos devServer at port 8088 is not running. Starting it up for you...
info: Your webos devServerHost 127.0.0.1 at port 8088 is not running. Starting it up for you...
┌─────────────────────────────────────────────────────────────────┐
│ ✔ BUNDLER STARTED | 13/10/2024, 19:39:43 | rnv@                 │
│ $ rnv run -p webos                                              │
├─────────────────────────────────────────────────────────────────┤
│ Project: my_smart_app@0.1.0                                     │
│ Workspace: rnv                                                  │
│ Platform (-p): webos                                            │
│ Engine: @rnv/engine-rn-web                                      │
│ Template: @rnv/template-starter                                 │
│ App Config (-c): app                                            │
│ Build Scheme (-s): debug                                        │
│ Supported Platforms: web, ios, android, tizen, webos            │
│ Env Info: win32 | x64 | node v20.18.0                           │
│ Executed Time: 0h:0m:2s:375ms                                   │
│ You are trying to run global rnv command in your current project.
│ This might lead to unexpected behaviour.
│ Run your rnv command with npx prefix:
│ npx rnv run -p webos
│ Project location: D:\free-lancers\my_smart_app\platformBuilds\app_webos
└─────────────────────────────────────────────────────────────────┘
(node:6540) [DEP_WEBPACK_DEV_SERVER_ON_AFTER_SETUP_MIDDLEWARE] DeprecationWarning: 'onAfterSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:6540) [DEP_WEBPACK_DEV_SERVER_ON_BEFORE_SETUP_MIDDLEWARE] DeprecationWarning: 'onBeforeSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option.
Starting the development server...

Compiled successfully!

You can now view my_smart_app in the browser.

  Local:            http://localhost:8088
  On Your Network:  http://192.168.1.15:8088

Note that the development build is not optimized.
To create a production build, use yarn build.

assets by path static/ 3.47 MiB
  asset static/js/bundle.js 3.16 MiB [emitted] (name: main) 1 related asset
  asset static/media/Inter-Light.58a136ec3193fa8a63e5.ttf 303 KiB [emitted] [immutable] [from: appConfigs/base/fonts/Inter-Light.ttf] (auxiliary name: main)
  asset static/media/logo.63d54a55b067ffc3e842.png 12.1 KiB [emitted] [immutable] [from: platformAssets/runtime/logo.png] (auxiliary name: main)
asset index.html 1.88 KiB [emitted]
asset asset-manifest.json 356 bytes [emitted]
cached modules 2.65 MiB (javascript) 315 KiB (asset) 28.7 KiB (runtime) [cached] 676 modules
webpack 5.95.0 compiled successfully in 1129 ms
No issues found.
✔ Executing: "C:\Users\Ariel\AppData\Roaming\npm\ares-package.cmd" -o "D:\free-lancers\my_smart_app\platformBuilds\app_webos\output" "D:\free-lancers\my_smart_app\platformBuilds\app_webos" -n
✔ Executing: "C:\Users\Ariel\AppData\Roaming\npm\ares-device.cmd" -D
✔ Executing: "C:\Users\Ariel\AppData\Roaming\npm\ares-launch.cmd" -V
error: ⨯ ○ run: Error: ENOENT: no such file or directory, scandir 'C:\webOS_TV_SDK\Simulator'

Here's what I've done so far:

Downloaded the webOS_TV_24_Simulator_1.4.1.exe from the official site link and placed the file in a folder named Simulator inside C:\webOS_TV_SDK.

Configured the CLI from the link oficial

Set up my renative.json file with the SDK path like this:

{
  "defaultTargets": {},
  "sdks": {
    "WEBOS_SDK": "C:\\webOS_TV_SDK"
  }
}

Despite these steps, the error persists. Does anyone know how I can fix this or if I'm missing something in the simulator configuration?
Note:
I also tried running it using the command rnv target launch -p webos -t emulator, as instructed in the documentation
However, I didn't understand this configuration: <USER_PATH>/Library/webOS_TV_SDK/Emulator/v4.0.0/LG_webOS_TV_Emulator_RCU.app
Either way, it resulted in the following error:
PS D:\free-lancers\my_smart_app> npx rnv target launch -p webos -t emulator

┌─────────────────────────────────────────────────────────────────┐
│ ██████╗ ███████╗███╗   ██╗ █████╗ ████████╗██╗██╗   ██╗███████╗ │
│ ██╔══██╗██╔════╝████╗  ██║██╔══██╗╚══██╔══╝██║██║   ██║██╔════╝ │
│ ██████╔╝█████╗  ██╔██╗ ██║███████║   ██║   ██║██║   ██║█████╗   │
│ ██╔══██╗██╔══╝  ██║╚██╗██║██╔══██║   ██║   ██║╚██╗ ██╔╝██╔══╝   │
│ ██║  ██║███████╗██║ ╚████║██║  ██║   ██║   ██║ ╚████╔╝ ███████╗ │
│ ╚═╝  ╚═╝╚══════╝╚═╝  ╚═══╝╚═╝  ╚═╝   ╚═╝   ╚═╝  ╚═══╝  ╚══════╝ │
│ $ rnv target launch -p webos -t emulator                        │
└─────────────────────────────────────────────────────────────────┘
info: Current engine: @rnv/engine-rn-web (D:\free-lancers\my_smart_app\node_modules\@rnv\engine-rn-web)
task: ○ target launch ↺1
task: ○ workspace configure ↺1
task: ✔ workspace configure
error: ⨯ ○ target launch: Error: ENOENT: no such file or directory, scandir 'C:\webOS_TV_SDK\Simulator'
    at Object.readdirSync (node:fs:1506:26)
    at getDirectories (D:\free-lancers\my_smart_app\node_modules\@rnv\core\src\system\fs.ts:811:10)
    at D:\free-lancers\my_smart_app\node_modules\@rnv\sdk-webos\src\deviceManager.ts:46:54
    at step (D:\free-lancers\my_smart_app\node_modules\tslib\tslib.js:195:27)
    at Object.next (D:\free-lancers\my_smart_app\node_modules\tslib\tslib.js:176:57)
    at D:\free-lancers\my_smart_app\node_modules\tslib\tslib.js:169:75
    at new Promise (<anonymous>)
    at Object.__awaiter (D:\free-lancers\my_smart_app\node_modules\tslib\tslib.js:165:16)
    at launchWebOSimulator (D:\free-lancers\my_smart_app\node_modules\@rnv\sdk-webos\src\deviceManager.ts:37:67)
    at D:\free-lancers\my_smart_app\node_modules\@rnv\sdk-webos\src\tasks\taskTargetLaunch.ts:14:35

┌─────────────────────────────────────────────────────────────────┐
│ ⨯ SUMMARY | 13/10/2024, 19:38:49 | rnv@                         │
│ $ rnv target launch -p webos -t emulator                        │
├─────────────────────────────────────────────────────────────────┤
│ Project: my_smart_app@0.1.0                                     │
│ Workspace: rnv                                                  │
│ Platform (-p): webos                                            │
│ Engine: @rnv/engine-rn-web                                      │
│ Template: @rnv/template-starter                                 │
│ App Config (-c): app                                            │
│ Build Scheme (-s): debug                                        │
│ Env Info: win32 | x64 | node v20.18.0                           │
│ Executed Time: 0h:0m:0s:488ms                                   │
│ error: ⨯ ○ target launch: Error: ENOENT: no such file or directory, scandir 'C:\webOS_TV_SDK\Simulator'
    at Object.readdirSync (node:fs:1506:26)
    at getDirectories (D:\free-lancers\my_smart_app\node_modules\@rnv\core\src\system\fs.ts:811:10)
    at D:\free-lancers\my_smart_app\node_modules\@rnv\sdk-webos\src\deviceManager.ts:46:54
    at step (D:\free-lancers\my_smart_app\node_modules\tslib\tslib.js:195:27)
    at Object.next (D:\free-lancers\my_smart_app\node_modules\tslib\tslib.js:176:57)
    at D:\free-lancers\my_smart_app\node_modules\tslib\tslib.js:169:75
    at new Promise (<anonymous>)
    at Object.__awaiter (D:\free-lancers\my_smart_app\node_modules\tslib\tslib.js:165:16)
    at launchWebOSimulator (D:\free-lancers\my_smart_app\node_modules\@rnv\sdk-webos\src\deviceManager.ts:37:67)
    at D:\free-lancers\my_smart_app\node_modules\@rnv\sdk-webos\src\tasks\taskTargetLaunch.ts:14:35

│ You are trying to run global rnv command in your current project.
│ This might lead to unexpected behaviour.
│ Run your rnv command with npx prefix:
│ npx rnv target launch -p webos -t emulator
└─────────────────────────────────────────────────────────────────┘
PS D:\free-lancers\my_smart_app>
``´
![image](https://github.com/user-attachments/assets/04e557a9-4c5c-429d-a693-f9f21977169e)

@arielsardinha thanks for reporting, what rnv version are you using?

@arielsardinha The issue most likely is that you put your simulator into sdk folder, your simulator should be put like this C:\webOS_TV_SDK\Simulator\webOS_TV_24_Simulator_1.4.1

I am using version 1.3.0.
I had already done that, placing the simulator in the indicated folder, which was intuitive due to the warning, but it still doesn't solve the issue, @pauliusguzas

Hello @arielsardinha,
I see that that folder name is a bit confusing. It is actually simulators folder where you put separate simulators.
For example, this webos_tv_23 simulator has its own folder in "Simulator" folder.

That's exactly it, @Marius456.
It worked perfectly.
Thank you so much!!!

authors: Marius456 arielsardinha pauliusguzas

repo: flexn-io/renative


text:
Translations of images

We can translate articles into other languages, but what about the pictures in the articles? Should we translate them? Or should we make no changes and make the translations compatible with the pictures?

Hi, I don't have any automated tool to deal with image translations at the moment, so don't worry about those for now. Thanks for the translations by the way.

I mean ways to encode/store such translations on images. Right now I'm storing the rasterised images and vector files in english, and my build scripts can't generate new images from translations at the moment, so the website/ebooks only use images with english text. It may be possible to tweak the scripts to bring support for translations, but it will take some time and I'm working on a new article at the moment.

authors: EuropaYou flipacholas

repo: flipacholas/Architecture-of-consoles


text:
could not find repo

* What went wrong:
Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
        > Could not find com.github.flipkart-incubator:inline-youtube-view:1.0.1.
        Searched in the following locations:
        file:/Users/dantecervantes/Library/Android/sdk/extras/m2repository/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.pom
file:/Users/dantecervantes/Library/Android/sdk/extras/m2repository/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.jar
file:/Users/dantecervantes/Library/Android/sdk/extras/google/m2repository/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.pom
file:/Users/dantecervantes/Library/Android/sdk/extras/google/m2repository/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.jar
file:/Users/dantecervantes/Library/Android/sdk/extras/android/m2repository/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.pom
file:/Users/dantecervantes/Library/Android/sdk/extras/android/m2repository/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.jar
file:/Applications/Android Studio.app/Contents/gradle/m2repository/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.pom
file:/Applications/Android Studio.app/Contents/gradle/m2repository/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.jar
file:/Users/dantecervantes/.m2/repository/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.pom
file:/Users/dantecervantes/.m2/repository/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.jar
https://jcenter.bintray.com/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.pom
https://jcenter.bintray.com/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.jar
file:/Users/dantecervantes/Documents/react-native/Tests/node_modules/react-native/android/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.pom
file:/Users/dantecervantes/Documents/react-native/Tests/node_modules/react-native/android/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.jar
https://dl.google.com/dl/android/maven2/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.pom
https://dl.google.com/dl/android/maven2/com/github/flipkart-incubator/inline-youtube-view/1.0.1/inline-youtube-view-1.0.1.jar
Required by:
project :app > project :react-native-youtube-player

* 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 6s

Did you add maven { url "https://jitpack.io" } in the root build folder ?

Same issue here.
Could not find com.github.flipkart-incubator:android-inline-youtube-view:1.0.1.
Searched in the following locations:
file:/C:/Android/sdk/extras/m2repository/com/github/flipkart-incubator/android-inline-youtube-view/1.0.1/android-inline-youtube-view-1.0.1.pom
file:/C:/Android/sdk/extras/m2repository/com/github/flipkart-incubator/android-inline-youtube-view/1.0.1/android-inline-youtube-view-1.0.1.jar
file:/C:/Android/sdk/extras/google/m2repository/com/github/flipkart-incubator/android-inline-youtube-view/1.0.1/android-inline-youtube-view-1.0.1.pom
file:/C:/Android/sdk/extras/google/m2repository/com/github/flipkart-incubator/android-inline-youtube-view/1.0.1/android-inline-youtube-view-1.0.1.jar
file:/C:/Android/sdk/extras/android/m2repository/com/github/flipkart-incubator/android-inline-youtube-view/1.0.1/android-inline-youtube-view-1.0.1.pom
file:/C:/Android/sdk/extras/android/m2repository/com/github/flipkart-incubator/android-inline-youtube-view/1.0.1/android-inline-youtube-view-1.0.1.jar
https://dl.google.com/dl/android/maven2/com/github/flipkart-incubator/android-inline-youtube-view/1.0.1/android-inline-youtube-view-1.0.1.pom
https://dl.google.com/dl/android/maven2/com/github/flipkart-incubator/android-inline-youtube-view/1.0.1/android-inline-youtube-view-1.0.1.jar
https://jcenter.bintray.com/com/github/flipkart-incubator/android-inline-youtube-view/1.0.1/android-inline-youtube-view-1.0.1.pom
https://jcenter.bintray.com/com/github/flipkart-incubator/android-inline-youtube-view/1.0.1/android-inline-youtube-view-1.0.1.jar
Required by:
project :app
Top level build file :
buildscript {
repositories {
    maven { url "https://jitpack.io" }
    google()
    jcenter()

}
dependencies {
    classpath 'com.android.tools.build:gradle:3.1.3'

    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
}

}
allprojects {
repositories {
google()
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
Project build file :
apply plugin: 'com.android.application'
android {
compileSdkVersion 28
defaultConfig {
applicationId "asit.ytl"
minSdkVersion 21
targetSdkVersion 28
versionCode 1
versionName "1.0"
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
}
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
}
dependencies {
implementation fileTree(dir: 'libs', include: ['*.jar'])
implementation 'com.android.support:appcompat-v7:28.0.0-alpha3'
implementation 'com.android.support.constraint:constraint-layout:1.1.1'
implementation 'com.android.support:design:28.0.0-alpha3'
testImplementation 'junit:junit:4.12'
androidTestImplementation 'com.android.support.test:runner:1.0.2'
androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'
implementation 'com.github.flipkart-incubator:android-inline-youtube-view:1.0.1'
}

@asitjain Try adding the jetpack dependency in the allProject block
Add it in your root build.gradle at the end of repositories :
// in root build.gradle
allprojects {
   repositories {
     ...
     maven { url "https://jitpack.io" }
   }
}

// in app build.gradle
dependencies {
   compile 'com.github.flipkart-incubator:inline-youtube-view:1.0.1'
}

Also, try pointing to the new version of the library.

Closing due to no activity

authors: anirudhramanan asitjain cinder92


text:
Search query is not works

Hi, I'm sending simple search query:
jira.search.search({ 		jql: 'project = "MAX"' 	}, function(error, result) { 		console.log(error); 		console.log(result); 	});
and getting the error:
'Unrecognized field "fieldsByKeys" (Class com.atlassian.jira.rest.v2.search.SearchRequestBean), not marked as ignorable\n'.
What am I doing wrong?
Originally posted by @sakuta in https://github.com/floralvikings/jira-connector/issues/89#issuecomment-561222896

Fixed in 3.0.1

repo: floralvikings/jira-connector


text:
ViewPager Title is not complete

Hi Guys
First of all, thank you so much for great efforts.
Recently I noticed that when we use this "Material View Pager" in Android N the title of TAB's are not coming as full name as it was coming in previous versions of Android.
Does anyone has any fix or suggestion to overcome this.
Also attached the copy of the screenshot on Android N.

Same problem here.
The solution was to create a tab bar, just like in the description
https://github.com/florent37/MaterialViewPager#or-create-your-own-tab-bar
and then put the app:pstsPaddingMiddle="false"

authors: kumarkeviv ricardocatarinoaltran


text:
Use Serenity Message Application Framework for Sound Boards

Apparently, Serenity has a framework for associating applications with messages. See this example. If possible, this is probably a cleaner way to implement soundboards.

Currently available in branch board-msg-components


text:
docs: update readme

What type of PR is this?
/kind documentation
What this PR does / why we need it:
Just testing deployment
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Additional documentation e.g., usage docs, etc.:

(!) Bunnyshell could not create the Environment App-main-branch / development:master / PR-88 for PR #88.

repo: flow-build/workflow-api


text:
slow subtitle loading with long videos

refs: https://github.com/video-dev/hls.js/issues/1303

+1

authors: blacktrash jakubkol

repo: flowplayer/flowplayer-hlsjs


text:
Implementing basic application layer

Use MediatR to add crud operations between ui and domain service for user entity.

implemented in #87

repo: fluentcms/FluentCMS


text:
FFI changes for Purescript 0.7

Purescript 0.7 breaks backwards compatibility by deprecating inline FFI and removing the implicit Prelude. This patch moves the FFI to a separate JS file and removes use of the $ operator (defined in Prelude).

Thanks!  If you are interested in taking this library over, feel free.  It's been a while since I did purescript stuff, and I suspect it will be a while before I do again.

authors: ScottPeterJohnson fluffynukeit


text:
Does fluid-player support multiple audios or multiple subtitles through dash/hls?

Its a basic question:
Does fluid-player support multiple audios or multiple subtitles through dash/hls. I have an mpd file and an m3u8 files through with I want to use those files to switch between audios and subtitles.

No activity since 2018, I guess this is resolved.

repo: fluid-player/fluid-player


text:
feat: add the ability for users to add resources to their collections

Adds Livewire support to Hearth, which is used to build a Livewire component for selecting resources users want to add to their resource collections. Also, updates ResourceCollection controller and requests to have ability to include resources on resource collection create, and update.
Testing

Verify that ResourceSelect component loads all available resources
Verify that ResourceSelect component loads any resources those are already included in a collection
Verify adding or removing resources from ResourceSelect

@chosww Can you check the two failing tests and see if you can resolve them?

@chosww Can you check the two failing tests and see if you can resolve them?

Yep, I am working on them -- the issue seems like caused by Hearth not able to find ResourceSelect component. I will let you know once I figure it out.

Hey @greatislander, I fixed the previous CI tests, but now I am getting code coverage failure because of the line I added in HearthCommand. Is HearthCommand something we should test or do I have to update ignore coverage check somewhere?

authors: chosww greatislander

repo: fluid-project/hearth


text:
Dependency error: auto-patchelf failed to find all the required dependencies

Attempting to run against my python/flask repo - after lots of log output with no errors, I get to the following:  I am complete newbie at this so not sure where to turn:
. . .
error: auto-patchelf could not satisfy dependency libtbb.so.12 wanted by /nix/store/iih2zsnv5iy24ziqbnkh8d7pjwx9zgkk-python3.11-numba-0.59.1/lib/python3.11/site-packages/numba/np/ufunc/tbbpool.cpython-311-x86_64-linux-gnu.so
auto-patchelf failed to find all the required dependencies.
Add the missing dependencies to --libs or use --ignore-missing="foo.so.1 bar.so etc.so".
/nix/store/v5irq7wvkr7kih0hhnch5nnv2dcq8c4f-stdenv-linux/setup: line 74: pop_var_context: head of shell_variables not a function context
/nix/store/v5irq7wvkr7kih0hhnch5nnv2dcq8c4f-stdenv-linux/setup: line 1454: pop_var_context: head of shell_variables not a function context
/nix/store/v5irq7wvkr7kih0hhnch5nnv2dcq8c4f-stdenv-linux/setup: line 1557: pop_var_context: head of shell_variables not a function context
error: builder for '/nix/store/m93245gk21712an8ljxb9lyla6msx5d2-python3.11-numba-0.59.1.drv' failed with exit code 1
error: 1 dependencies of derivation '/nix/store/cj20w56pqqvlimx6n67sbd5biss7siwv-python3-3.11.7-env.drv' failed to build
error: 1 dependencies of derivation '/nix/store/xh7fd7d13fiq4k5bcsdv5js3azjyd39f-make-template-for-make-search-paths.drv' failed to build
error: 1 dependencies of derivation '/nix/store/p9qkhi75fq8jywvx0w8hrjpdldp2kg7l-make-template-for-make-search-paths.drv' failed to build
error: 1 dependencies of derivation '/nix/store/2jb36d2hm6hnhy7ndrvd4581j227svmv-make-template-for-sorts-config-runtime.drv' failed to build
error: 1 dependencies of derivation '/nix/store/7j27dar00l20067gf53rz2rf7hkansfn-make-template-for-make-search-paths.drv' failed to build
error: 1 dependencies of derivation '/nix/store/2wa2wddig9gmvvbpnxicy7c712crwj2d-make-template-for-make-script-for-sorts.drv' failed to build
error: 1 dependencies of derivation '/nix/store/gfs7vim0hbak41ppsb85h633657hf0ch-sorts.drv' failed to build
───────────────────────── 🐛 Failed with exit code 100 ─────────────────────────

Hi @erik-lab,
This error means you must provide libtbb.so.12 as a buildInput for patchelf to be able to find it.
Here are some nixpkgs packages related to tbb: https://search.nixos.org/packages?channel=23.11&from=0&size=50&sort=relevance&type=packages&query=tbb
Please provide relevant code so we can further assist you.

I am more than a bit lost. I am trying to complete a static scan for initial Google app validation.  I was following the instructions provided to build then run a docker image of FluidAttacks on my Windows 10 dev machine against a Python/Flask repo.  The Docker built fine, but the run failed.  I have no idea what the scanner software is doing specifically, have little experience monitoring a docker image, and am not sure  what the things are you suggest that I provide (or how to provide them, or why).  (really sorry for the newbiness !)
This is the run command I used:  docker run -v D:\edahl\Documents\eme_code_scan\eme_vector:/repo/eme_vector ghcr.io/fluidattacks/makes/amd64:latest m gitlab:fluidattacks/universe@trunk /sorts /repo/eme_vector
The run started, followed by several hundred rows of output and finally the error pasted above.
I shared my private Repo to you (https://github.com/erik-lab/eme_vector.git).  Is there anything else that would help?  Like the full log of the aborted run?
Thanks for your patience!  :-)

Hi @erik-lab,
I am curious about where you found that command.
If you want to scan your app for CASA Tier 2 compliance, you should follow this official guide: CASA Tier 2 Compliance Guide.
If you could let us know where you found a guide that recommends that specific command that you are using, it would help us prevent further misinformation.

The Google notification I received during validation included a link to the App Defense Alliance site (https://appdefensealliance.dev/casa) which includes instructions on performing static and dynamic scans.  I tried to follow the static scan guide to get to this point.
I have been underwater for a bit, but I skimmed the Compliance guide site you shared and it seemed clearer.  I will give it a try tonight when I resurface.  Back to the day job for now.
Erik

Hi @erik-lab
With the information you have provided, I am not able to pinpoint a specific issue. If you could kindly share the output generated by the command, I will glady help you out.
The only thing I noticed is that you are not using the config.yaml file we recommended in the guide. It is not a problem per se, but you should use it as is (changing only the path you defined) because it has the correct exclusions that could enhance the scan performance.
Note: If the output reaches a point and shows something like this:

and stays there for a while, it means the scan is in progress, and you should wait a bit longer.

Hi @jgomezb11 - I reverted to the default config, I modified the sast recursion-limit to be 1000 and turned off the file_size_limit  after I saw errors with a couple large js files I had included, and the scan ran (woo hoo) - it took a while but I got my results.  While I am not thrilled with 99 vulnerabilities, at least I have a path forward now.  Thank you for your help!  I may be back after I digest the vulnerabilities, I am sure I will need some help remediating some of them.

repo: fluidattacks/makes


text:
fix: generated schema snapshot now includes history annotations

Description
Added the same annotations already present in schema.tmpl to the internally generated struct.
Motivation and Context
The history schema struct gets written to a json string when using the schema/snapshot feature flag, which is used to load the ent schema if any errors occur during normal loading. Such an error would be the usage of a generated package within schema definitions after manually deleting these files generated by ent in order to get a clean repository.
As of now, history tables get saved in the snapshot without the history annotations and, when loading the schema from that snapshot, enthistory tries to generate another history table for them, e.g. FooHistoryHistory (which results in an error as expected because these tables include the history columns twice).
How Has This Been Tested?
This has not yet been tested thoroughly, just in a somewhat complex local project which I can't share here. I will build a little mock project tomorrow for further testing. I would appreciate help for creating an automated test because the exact scenario is a bit complex (approx. reproduction: use intercept and schema/snapshot feature flags without enthistory, create an interceptor in any schema so that the schema package needs the generated intercept package, add enthistory and run generation, delete every generated ent file but internal/schema.go, run the generation again) and I don't know yet how to run the generation multiple times during a test while also deleting files.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update or addition to documentation for this project)

Checklist:

[x] My code follows the code style of this project.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

@jan-4brainsolutions Thanks for the quick fix! Not sure we'll be able to create the tests for this regarding generation super easily but after looking at the feature's code it make sense that this was an issue to begin with. If the Annotation was left out of the schema snapshot and a merge did occur then the history schemas would end up without them. If you're okay with it we can test that the annotations are making it into the schema snapshot directly. I wrote up a quick test using the AST to parse that out that you could drop into your branch.
For this test you'd need to turn on the schema/snapshot feature in the _examples/basic/ent/entc.go file
func TestSchemaSnapshotAnnotations(t *testing.T) {
	fset := token.NewFileSet()
	node, err := parser.ParseFile(fset, "./basic/ent/internal/schema.go", nil, parser.ParseComments)
	assert.NoError(t, err)

	assert.Len(t, node.Decls, 1)
	schemaDecl := node.Decls[0].(*ast.GenDecl)
	assert.Len(t, schemaDecl.Specs, 1)
	schemaSpec := schemaDecl.Specs[0].(*ast.ValueSpec)

	assert.Len(t, schemaSpec.Values, 1)
	assert.Len(t, schemaSpec.Names, 1)

	assert.Equal(t, "Schema", schemaSpec.Names[0].Name)

	schemaValue := schemaSpec.Values[0].(*ast.BasicLit).Value
	assert.NotEmpty(t, schemaValue)

	var g = struct {
		gen.Graph
		Features []string
	}{}
	err = json.Unmarshal([]byte(strings.Trim(schemaValue, "`")), &g)
	assert.NoError(t, err)

	for _, schema := range g.Schemas {
		if strings.Contains(strings.ToLower(schema.Name), "history") {
			historyAnnotations := schema.Annotations["History"]
			assert.NotEmpty(t, historyAnnotations)
			historyAnnotationsMap, ok := historyAnnotations.(map[string]any)
			assert.True(t, ok)
			assert.True(t, historyAnnotationsMap["exclude"].(bool))
			assert.True(t, historyAnnotationsMap["isHistory"].(bool))
		} else {
			assert.Empty(t, schema.Annotations["History"])
		}
	}
}

repo: flume/enthistory


text:
FormBuilderDropdown change location items

Environment
Package name:
Everyone Hi
I want the item select sheet to always be strictly FormBuilderDropdown
How to do it?

FormBuilderDropdown(
elevation: 1,
name: 'city_dropdown',
initialValue: 'Нур-Султан',
items: const [
DropdownMenuItem(
value: 'Алматы',
child: Text('Алматы'),
),
DropdownMenuItem(
value: 'Москва',
child: Text('Москва'),
),
DropdownMenuItem(
value: 'Питер',
child: Text('Питер'),
),
DropdownMenuItem(
value: 'Нур-Султан',
child: Text('Нур-Султан'),
),
],)
I have written like this

 I want do this

I don't know what means this
A round component, a custom icon, a line between options...
Need more details that expect behaviour and actual behaviour

If you look at the picture, you can see that the list for selecting cities is located under the FormBuilderDropdown.
How to do also?

I have written like this FormBuilderDropdown( elevation: 1, name: 'city_dropdown', initialValue: 'Нур-Султан', items: const [ DropdownMenuItem( value: 'Алматы', child: Text('Алматы'), ), DropdownMenuItem( value: 'Москва', child: Text('Москва'), ), DropdownMenuItem( value: 'Питер', child: Text('Питер'), ), DropdownMenuItem( value: 'Нур-Султан', child: Text('Нур-Султан'), ), ], )

I can see the list, but this code don't is enough for that?

No)
If i tap on FormBuilderDropdown his list went down from below him.
From this it looks like this

Do you want that dropdown options appers below of FormBuilderDropdownField?

Due to lack of response, I will close this issue.
If the bug still exists, feel free to open a new issue

authors: deandreamatias lllymaknuga


text:
Dart docs, add AlertDialog example

I'd like to suggest adding an AlertDialog example. This way a developer doesn't have to hunt for the wiring procedure.
https://docs.flutter.io/flutter/material/AlertDialog-class.html
  void onSignedInError() {
    var alert = new AlertDialog(
      title: new Text("Sign in Error"),
      content: new Text("There was an error signing in. Please try again."),
    );
    showDialog(context: context, child: alert);
  }

Is there a PR for this? (just want to link for those that like to follow along :)

https://github.com/flutter/flutter/pull/10812

authors: Hixie branflake2267 sethladd

repo: flutter/flutter


text:
Error (Xcode): redefinition of module 'Firebase' /Users/sparshbansal/Development/Playground/buy_sell/ios/Pods/Firebase/CoreOnly/Sources/module.modulemap:0:7  Error (Xcode): failed to emit precompiled header '/Users/sparshbansal/Library/Developer/Xcode/DerivedData/Runner-eygfgnuelkwzzpbxozolsfdjmxit/Build/Intermediates.noindex/PrecompiledHeaders/Runner-Bridging-Header-swift_2HIAQV5EQ9XFZ-clang_289EBCJULZ6AD.pch' for bridging header '/Users/sparshbansal/Development/Playground/buy_sell/ios/Runner/Runner-Bridging-Header.h'

Please help me solve these errors

dependencies
cupertino_icons: ^1.0.2
  flutter_signin_button: ^2.0.0
  animated_text_kit: ^4.2.2
  firebase_core: ^1.24.0
  firebase_auth: ^3.11.1
  cloud_firestore: ^3.5.1
  location: ^4.4.0
  geocoder2: ^1.4.0
  google_sign_in: ^5.4.2
  email_validator: ^2.1.17
  open_mail_app: ^0.4.5
  country_state_city_picker: ^1.2.8
  flutter_neumorphic: ^3.2.0
  provider: ^6.0.3
  image_picker: ^0.8.6
  firebase_storage: ^10.3.11
  galleryimage: ^1.2.0
  google_maps_flutter: ^2.2.1
  geocoding: ^2.0.5
  geolocator: ^9.0.2
  like_button: ^2.0.5
  photo_view: ^0.14.0
  maps_launcher: ^2.0.1
  search_page: ^2.2.0

Hi @sparshba,
Please provide your flutter doctor -v and flutter run --verbose logs. The output of this may be huge so kindly put it into a .txt file and attach it here. Please also make sure that your plugins/packages are all up to date.
Thank you

Hi @danagbemava-nc
This issue has been resolved.
But whenever i am clicking on a button the app crashes with no error.
flutterverbose.docx
doctor.docx
Whenever i click button on this page[Button:Around Me]
location_screen.txt
home_screen.txt

authors: danagbemava-nc sparshba


text:
DataTable: missing secondary tap callback

Use case
Showing context menus on desktop platforms.
Currently, DataCell has onTap, onTapDown, onTapCancel, onLongPress, and onDoubleTap whereas DataRow only has a onLongPress gesture callback.
Proposal
Add onSecondaryTap(Down) to both DataRow and DataCell for showing row- and cell-specific context menus.

cc @justinmc

It would be nice if we could use composition to get these behaviors, but it seems impractical here, especially because DataCell and DataRow are not widgets.  So, I think adding onSecondaryTap and onSecondaryTapDown to DataRow and DataCell makes sense.
Currently, DataCell uses Inkwell's GestureDetector under the hood:
https://github.com/flutter/flutter/blob/d1436d1df21ee2d40713af682446c66ee3165a58/packages/flutter/lib/src/material/data_table.dart#L870
And Inkwell doesn't have an onSecondaryTap parameter, I'm not sure why.  We would need to either add it or wrap it in another GestureDetector there.

authors: darrenaustin jpnurmi justinmc


text:
Bring and Add Native Splash Screen in Windows Desktop

I Have Sugestion Bring and Add Native Splash Screen in Windows Desktop.

it would be nice to add this to the 3rd party flutter_native_splash (here) which is an absolute must

Closing this as duplicate of https://github.com/flutter/flutter/issues/41980

authors: YahyaAtta darshankawar iapicca


text:
i have this issue " Upstream repository https://github.com/samstickkz/login.git is not a standard remote"

i have not been able to see a good fix on youtube or anywhere...  how can i fix this ?

@samstickkz
Upstream repository https://github.com/samstickkz/login.git this doesn't look like the expected repo that flutter doctor -v expects. Usually it should be something like below:
Upstream repository https://github.com/flutter/flutter.git
Not sure how are you seeing the said repo. Have you properly installed the Flutter sdk as mentioned in the official documentation ? https://docs.flutter.dev/get-started/install/macos
I suggest you to follow the recommended approach as mentioned in the documentation and try again.
Closing for now. If the similar log persists, write in comments and I'll reopen it.

authors: darshankawar samstickkz


text:
[SelectionArea] Once text is pushed to a new line after resizing the window, we can no longer select the text on the second line

Steps to Reproduce

Execute flutter run on the code sample
Resize application
Drag or Double click to SelectionText

Expected results:  After resize app SelectionArea can double, drag text .
Actual results:  Can't selection text if drag text with newLine wrap.

Code sample

class _MyHomePageState extends State<MyHomePage> {
  @override
  void initState() {
    super.initState();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: const SelectionArea(
        child: Center(
          child: Text(
            'Hi, I am is Beta. Good bye. Hi, I am is Beta. Good bye. Hi, I am is Beta. Good bye. Hi, I am is Beta. Good bye.'
          ),
        ),
      ),
    );
  }
}

Logs

[✓] Flutter (Channel stable, 3.3.10-0.0.pre.5, on macOS 12.5.1 21G83 darwin-x64, locale en-VN)
    • Flutter version 3.3.10-0.0.pre.5 on channel stable at /Users/tungle/workspaces/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 3778e3c76c (9 weeks ago), 2022-12-14 23:44:46 -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/tungle/Library/Android/sdk
    • Platform android-31, build-tools 30.0.3
    • Java binary at: /Library/Java/JavaVirtualMachines/jdk-16.0.1.jdk/Contents/Home/bin/java
    • Java version Java(TM) SE Runtime Environment (build 16.0.1+9-24)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).

[✓] VS Code (version 1.74.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.58.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 12.5.1 21G83 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 109.0.5414.119

[✓] HTTP Host Availability
    • All required HTTP hosts are available

https://user-images.githubusercontent.com/46608407/218371777-71526504-c861-4b6c-8657-848c776cfdae.mov

Triage report
I can reproduce this issue with Master (3.8.0-10.0.pre.34).
Code Sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatelessWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text(title)),
      body: const Center(
        child: SelectionArea(
          child: Text(
            'Nisi commodo eleifend vulputate hendrerit in rhoncus nunc. '
            'Vitae aliquam est, eros hac habitant tempor.',
          ),
        ),
      ),
    );
  }
}

flutter doctor -v (Master)
[!] Flutter (Channel master, 3.8.0-10.0.pre.34, on macOS 13.2 22D49 darwin-arm64, locale en-US)
    • Flutter version 3.8.0-10.0.pre.34 on channel master at /Users/nabeelparkar/fvm/versions/master
    ! Warning: `dart` on your path resolves to /opt/homebrew/Cellar/dart/2.19.1/libexec/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nabeelparkar/fvm/versions/master. Consider adding /Users/nabeelparkar/fvm/versions/master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 53fe8a3f94 (74 minutes ago), 2023-02-13 02:37:24 -0500
    • Engine revision 4107a7b71f
    • Dart version 3.0.0 (build 3.0.0-231.0.dev)
    • DevTools version 2.21.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nabeelparkar/Library/Android/sdk/
    • Platform android-33, build-tools 33.0.0
    • ANDROID_SDK_ROOT = /Users/nabeelparkar/Library/Android/sdk/
    • Java binary at: /Users/nabeelparkar/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /Applications/Brave Browser.app/Contents/MacOS/Brave Browser

[✓] Android Studio (version 2021.3)
    • Android Studio at /Users/nabeelparkar/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9123335/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] Android Studio (version 2022.1)
    • Android Studio at /Users/nabeelparkar/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] VS Code (version 1.75.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.58.0

[✓] Connected device (3 available)
    • iPhone 14 Pro Max (mobile) • 6BC61E88-4DE0-4BCB-8599-DA5294269146 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-2 (simulator)
    • macOS (desktop)            • macos                                • darwin-arm64   • macOS 13.2 22D49 darwin-arm64
    • Chrome (web)               • chrome                               • web-javascript • Brave Browser 110.1.48.158

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

cc @chunhtai

Anything update this problem?

same problem

We also have this problem 3.10.6  (also 3.13.x).
Our app has 3000 installs on android but the problem is mostly related to our desktop version about 700 installed desktop devices.
Tipitaka Pali Reader
You can install the app from the mac or ms app store or flathub and also experience the same bug.

This issue is very important on desktop apps that require text selection. It can also be replicated on flutter 3.22.

authors: annd22 bksubhuti exaby73 goderbauer letungcntt zhibisora