text:
HA 0.110.2: Extra badge does not show up

Checklist

[x] I'm running the latest version of CustomUI (Update guide) or using a specific release that is not marked as "Broken".
[x] I tried to force-refresh (Ctrl+Shift+R / Ctrl+F5) the browser
[x] (Optional, but recommended) I'm using Chrome or tried to reproduce the feature on Chrome.

Browser + Version:
Chrome 81.0.4044.138 (Official Build) (64-bit)

CustomUI version:
20190518
Home Assistant release (hass --version):
0.110.2
Problem-relevant configuration.yaml entries:
customizer:
  custom_ui: local

frontend:
  themes: !include_dir_merge_named themes/
  extra_html_url:
  - https://raw.githubusercontent.com/andrey-git/home-assistant-custom-ui/master/state-card-custom-ui-dbg.html
  extra_html_url_es5:
  - https://raw.githubusercontent.com/andrey-git/home-assistant-custom-ui/master/state-card-custom-ui-dbg-es5.html

homeassistant:
  customize:
    light.gateway:
      custom_ui_state_card: state-card-custom-ui
      extra_badge:
        entity_id: sensor.gateway_illumination

ui-lovelace.yaml
cards:
- type: vertical-stack
  title: Living Room Controls
  show_header_toggle: false
  cards:
  - type: entities
    title: Lights and Switches
    entities:
    - light.gateway

Expecting extra badge here:

Problem-relevant Home Assistant log entries:
no any related entires noticed

Any errors from browser Javascript console:
no any related entires noticed... But here is a screenshot just in case..

extra_badge is long gone, and was designed for HA States, not for Lovelace.
btw If you want to keep coloring your icons, you need the state-card-custom-ui.html I changed, which is available in the Pull requests section of this repo. All other files can be taken out.

Oh, I see... Gotcha.. You are using the multiple-entity-row here.. I am aware of that, just wanted something new, like badge, lol. So the documentation for custom-ui is not clear about the badge.
Thank you very much for clarifying this.
So you mean the only feature of the custom-ui left is colorizing the icons and probably text?
But is your version of /local/custom_ui/state-card-custom-ui.html merged already?

no, many other things can still be customized using the template functionality custom-ui offers.
Only specific states ui options are no longer available, simply because homeassisant doesnt use them any longer, or has another way of doing things. Like with the icon_color recently after HA 110.
and yes, if you use the frontend method, you can completely remove customizer.
the pull request isn't merged, and probably never will, because the complete repo isn't maintained any longer.
Im am hoping we can have a modern custom-ui.js version anytime in the future, since both Bram and Thomas have been helping me using the legacy custom-ui work with ha 110, and I am sure they see the power ;-)
My switches are Z-wave switches that are connected to HA via Mqtt.

Gotcha! Thank you for elaborating this... I actually noticed that my battery level icons are not being colorized any longer (((.
I have tried what you suggested, completely removed the customizer and downloaded the state-card-custom-ui.html from your repo patch-1 branch but they are still not colorized (((
Here is what I have:
frontend:
  themes: !include_dir_merge_named themes/
  extra_html_url:
  - /local/custom_ui/state-card-custom-ui.html

homeassistant:
  customize:
    sensor.bedroom_t_h_p_battery:
      custom_ui_state_card: state-card-custom-ui
      templates:
        # Following changes the text color in details window,
        # when clicking on sensor in UI, according to custom themes/alert.yaml:
        theme: if (state <= 10) return 'alert_red'; else if (state <= 30) return 'alert_yellow';
        # Following changes the sensor's lovelace icon color:
        icon_color: >
          if (state <= 10) return 'rgb(220, 76, 64)'; else if (state <= 30) return 'rgb(248, 192, 30)';

Result (still no color):

But when I click on the sensor icon (it's colorized, so the theme seems to be applied, or am I wrong?):

Any ideas what may be wrong then?

which version HA are you using?
change some of the syntax below, you had some dangerous 'else' clauses, creating diffuculties when the state would be above 30
homeassistant:
  customize:
    sensor.bedroom_t_h_p_battery:
      # custom_ui_state_card: state-card-custom-ui  <-- take out this
      templates:
        # Following changes the text color in details window,
        # when clicking on sensor in UI, according to custom themes/alert.yaml:
        theme: >
          if (state <= 10) return 'alert_red';
          if (state <= 30) return 'alert_yellow';
          return 'grey';
        # Following changes the sensor's lovelace icon color:
        icon_color: >
          if (state <= 10) return 'rgb(220, 76, 64)';
          if (state <= 30) return 'rgb(248, 192, 30)';
          return 'grey';

not sure tbh, maybe the theme takes precedence over icon_color, you can check that in line 27 (which is enormously long....)

I changed the "state-card-custom-ui.html" as per instructions elsewhere on Github after release of 0.110.0 , works fine now with colors, using 0.110.2 as of now:

Code:

great, as we made it work!
glad its working out for you.

I use HA 0.110.1, sorry, for some reason I thought it's 0.110.2, but I guess your version of state-card-custom-ui.html should work with this version too..
I tried the code you proposed and now it even stopped colorizin the details window:

See, it's not yellow anymore so I guess there is some missing part of the configuration, or
custom_ui_state_card: state-card-custom-ui is still kinda needed in my case for some reason?
And I thought if do not use something like return 'grey'; at the end of templating, it should automatically pick the main theme color (which changes when the theme changes)... At least it worked this way long ago... before 0.106 I guess (I may be wrong though)...

@drew-kun
Have you tried another browser? In case of severe caching issue?
Your "state-card-custom-ui.html" is correctly updated within the code?

and yes, you still need this in "configuration.yaml":

in anyway, dont use both theme, and icon_color.
Ive updated the Pull request file, so it reflects the correct version:
200225-adapted-for-HA110+

inspector:

so you know its loaded alright ;-)

Yeah, testing it on Chrome and Android app, which updates pretty good... Also, just updated to 0.110.2 but still the same issue.

you should post this in the other thread really, as this is about the extra badge, and your question is on activating custom-ui.
Just because this repo is no longer maintained, we shouldn't abuse the threads .....

Ive updated the Pull request file, so it reflects the correct version:
200225-adapted-for-HA110+

Do you have a link to that?

Ive updated the Pull request file, so it reflects the correct version:
200225-adapted-for-HA110+

Do you have a link to that?

https://github.com/andrey-git/home-assistant-custom-ui/blob/3bef7470dadea6fb93d37ced0ed521e0b34db02d/state-card-custom-ui.html

you should post this in the other thread really, as this is about the extra badge, and your question is on activating custom-ui.
Just because this repo is no longer maintained, we shouldn't abuse the threads .....

Ok, guys, sorry. Closing this. Will open the new issue soon. Thank you.

authors: Mariusthvdb drew-kun nolenjohan

repo: andrey-git/home-assistant-custom-ui


text:
Proposed changes to send callback

Hi,
I've been using node mailer for sometime now and feel the callback can be simplified a bit. Instead of returning a status if email was sent successfully, how about changing it to be called only when there's an error. So success is more of an implied action.
This way if an error occurs a dev can get more detailed info on why an email wasn't sent and act on it. Another idea is to create a true status object that looks like this. { status: true/false, response: 'response from MTA' }
Let me know what you think.
-Ardie

Hi,
Generally I agree with you about the behavior of "sucess" but I'm afraid this change would break a lot of existing scripts that rely on success being true so I'm not going to pull the patch. I'm currently working on a new version of Nodemailer with connection pooling, large file streaming etc. and there this change will probably be included.

Ok great! Looking forward to the new version. One feature that would be really helpful is if you can return the MTA status whenever an email is sent.

I need to think about it as the response status format is not standardized by any way (except, of course, the response status code). Probably should include the whole message then, including the code part.
Nodemailer is basically going to be a wrapper for my other modules simplesmtp (the client and the connection pool) + mailcomposer (for generating rfc822 formatted messages), so you could see most of the coming features from these modules already.

There is a myriad of SMTP servers out there and each of these might have implemented the final announcment on their own wat. For example, the Postfix SMTP log found from Wikipedia ends with
250 Ok: queued as 12345

but similar Exchange log ends with
250 2.6.0 <AlanUNPPqlY2LukY4W00000001@Alan.ExchGuy.com> Queued mail for delivery

As you probably know what to expect from the server (as Nodemailer is probably always connecting to the same host) this information can be predictable and useful so it makes sense to return the response string. But there's no point of parsing the response in the module side.

The new version which is now live includes a responseObject instead of success for the callback and it the object also includes the last message retreived from the server

Awesome! Thanks for all your handwork. I'll be upgrading asap.

source: gharchive/issue

license: mit

license_type: permissive

license_source: bigquery


text:
fix broken link

There is a misplaced square bracket in the README. This fixes it :)

@Fleker I already have a CLA signed because of other Google projects I contribute to. Do I need a specific one for this project? It seems that the CI already recognized my signature.

I was just looking at your GitHub username. It looks like your email (from your GH profile) has already been associated with one. I'll pull in your change.

source: gharchive/pull-request

authors: Fleker danicat

repo: androidthings/sample-googleassistant


text:
Exo player covered by something when it inside Surface

I am new to android, I want to write an android tv app.
I ran into a problem, I started a new empty project, added Media3 and created a simple composable
in this case I can't see the video, only the sound. After a few hours of debugging, I realized what the cause of the problem was
when Exo Player is inside the Surface, it seems that the video is covered by something, but I can see the controls.
  TestExoTheme {
      Surface(
          modifier = Modifier.fillMaxSize(),
          shape = RectangleShape
      ) {
          Greeting("Android")
      }
  }

When I remove surface everything works as expected.
So can someone pls explain me why it happens
here is the full code
class MainActivity : ComponentActivity() {
    @UnstableApi
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContent {
            TestExoTheme {
                Surface(
                    modifier = Modifier.fillMaxSize(),
                    shape = RectangleShape
                ) {
                    Greeting("Android")
                }
            }
        }
    }
}

@UnstableApi
@Composable
fun Greeting(name: String, modifier: Modifier = Modifier) {
    val EXAMPLE_VIDEO_URI = "https://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4"

    // Get the current context
    val context = LocalContext.current

    // Initialize ExoPlayer
    val exoPlayer = remember {
        ExoPlayer.Builder(context).build().apply {
            videoScalingMode = C.VIDEO_SCALING_MODE_SCALE_TO_FIT_WITH_CROPPING
        }
    }

    // Create a MediaSource
    val mediaSource = remember(EXAMPLE_VIDEO_URI) {
        MediaItem.fromUri(EXAMPLE_VIDEO_URI)
    }

    // Set MediaSource to ExoPlayer
    LaunchedEffect(mediaSource) {
        exoPlayer.setMediaItem(mediaSource)
        exoPlayer.prepare()
        exoPlayer.playWhenReady = true
    }

    // Manage lifecycle events
    DisposableEffect(Unit) {
        onDispose {
            exoPlayer.release()
        }
    }

    // Use AndroidView to embed an Android View (PlayerView) into Compose
    AndroidView(
        factory = {
            PlayerView(context).apply {
                player = exoPlayer
                useController = true
            }
        },
        modifier = Modifier
            .fillMaxSize()
            .zIndex(1f)
            .height(500.dp) // Set your desired height
    )
}

I'm unsure why you want or are required to touch a Surface for your use case. However, I'd start without this when using a PlayerView. The PlayerView laready is inflating a Surface internally and a user doesn't require to do something regaring the UI for a basic setup.
I suggest to remove all code that creates or sets a Surface as a first step. Until that is working, I'd also remove all code that manually manipulates the size of the PlayerView in case there is such code.

To add to Marc's comment:
Please take a look at Surface composable documentation. Quoting:
The Surface is responsible for:

* Clipping
* Elevation
* Borders
* Background
* Content color
* Blocking touch propagation behind the surface (<--!!!)

You can even see Surface's implementation - it's essentially a Box with special properties.
I just opened Android Studio and set up an Empty Activity. This is what MainActivity.kt would have in it:
class MainActivity : ComponentActivity() {
  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    enableEdgeToEdge()
    setContent {
      MyApplicationTheme {
        Scaffold(modifier = Modifier.fillMaxSize()) { innerPadding ->
          Greeting(
            name = "Android",
            modifier = Modifier.padding(innerPadding)
          )
        }
      }
    }
  }
}

Some time ago Surface was replaced with Scaffold to help you build out your layout first. You might never end up needing a Surface composable.
Also, Surface is a bit of an overloaded term. You will see that

your Surface comes from the material world androidx.compose.material.Surface
There is also a Surface that comes from the View world: https://developer.android.com/reference/kotlin/android/view/Surface
There are also composables AndroidEmbeddedExternalSurface and AndroidExternalSurface from androidx.compose.foundation

The thing that I understood Surface controls all colors inside. In my case Surface was added by android studio itself when I started a new project. Don't know if Scaffold works for TV.
If I remove Surface all my colors stops inherits from theme, it means I need to specify color to each text node, If my screen wrapped with Surface all texts inherits colors from it. I think I can't do much here, I remove Surface from pot level and wrap each screen individually as a workaround.

authors: NuclleaR marcbaechinger oceanjules

repo: androidx/media

license_source: github-api


text:
Unexpected error occurred when play Ad

Version
ExoPlayer 2.18.4
More version details
No response
Devices that reproduce the issue
Any
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Yes
Reproduction steps
Replace line 532 in DefaultMediaSourceFactory with the following.
        new DataSpec(Util.getDataUriForString("text/xml", "<?xml version=\"1.0\" encoding=\"UTF-8\"?><vmap:VMAP xmlns:vmap=\"http://www.iab.net/videosuite/vmap\" version=\"1.0\">\n"
            + "  <vmap:AdBreak timeOffset=\"start\" breakType=\"linear\" breakId=\"preroll\">\n"
            + "    <vmap:AdSource id=\"preroll-ad-0\" allowMultipleAds=\"true\" followRedirects=\"true\">\n"
            + "      <vmap:AdTagURI templateType=\"vast3\">https://ad.doubleclick.net/ddm/pfadx/N703922.1534589IPRIMA.CZ/B30145407.369534207;sz=0x0;ord=%%VIEWID%%;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;dc_tdv=1;dcmt=text/xml;dc_sdk_apis=[APIFRAMEWORKS];dc_omid_p=[OMIDPARTNER];dc_vast=4;dc_mpos=[BREAKPOSITION];ltd=</vmap:AdTagURI>\n"
            + "    </vmap:AdSource>\n"
            + "  </vmap:AdBreak>\n"
            + "</vmap:VMAP>")),

Expected result
Play ad.
Actual result
Ad is skipped with error 900 and IMA extension failed on internal error.
Stacktrace:
2023-07-21 07:52:13.686 ActivityThread           W  handleWindowVisibility: no activity for token android.os.BinderProxy@521941
2023-07-21 07:52:13.839 ExoPlayerImpl            I  Init 8a180f2 [ExoPlayerLib/2.18.4] [generic_x86, Android SDK built for x86, Google, 29]
2023-07-21 07:52:13.847 EventLogger              D  playWhenReady [eventTime=0.00, mediaPos=0.00, window=0, true, USER_REQUEST]
2023-07-21 07:52:13.850 EventLogger              D  surfaceSize [eventTime=0.00, mediaPos=0.00, window=0, 0, 0]
2023-07-21 07:52:13.857 EventLogger              D  timeline [eventTime=0.01, mediaPos=0.00, window=0, periodCount=1, windowCount=1, reason=PLAYLIST_CHANGED
2023-07-21 07:52:13.857 EventLogger              D    period [?]
2023-07-21 07:52:13.857 EventLogger              D    window [?, seekable=false, dynamic=true]
2023-07-21 07:52:13.857 EventLogger              D  ]
2023-07-21 07:52:13.858 EventLogger              D  mediaItem [eventTime=0.01, mediaPos=0.00, window=0, reason=PLAYLIST_CHANGED]
2023-07-21 07:52:13.862 EventLogger              D  state [eventTime=0.02, mediaPos=0.00, window=0, BUFFERING]
2023-07-21 07:52:13.917 EventLogger              D  surfaceSize [eventTime=0.07, mediaPos=0.00, window=0, 1080, 1731]
2023-07-21 07:52:13.935 EGL_emulation            D  eglMakeCurrent: 0xf7053680: ver 2 0 (tinfo 0xf7089a30)
2023-07-21 07:52:13.962 EGL_emulation            D  eglMakeCurrent: 0xf7053680: ver 2 0 (tinfo 0xf7089a30)
2023-07-21 07:52:14.013 exoplayer2.dem           W  Accessing hidden method Lsun/misc/Unsafe;->compareAndSwapObject(Ljava/lang/Object;JLjava/lang/Object;Ljava/lang/Object;)Z (greylist, linking, allowed)
2023-07-21 07:52:14.019 GASS                     D  Clearcut logging disabled
2023-07-21 07:52:14.020 EventLogger              D  loading [eventTime=0.17, mediaPos=0.00, window=0, period=0, true]
2023-07-21 07:52:14.055 EGL_emulation            D  eglMakeCurrent: 0xf7053680: ver 2 0 (tinfo 0xf7089a30)
2023-07-21 07:52:14.173 eglCodecCommon           D  setVertexArrayObject: set vao to 0 (0) 0 0
2023-07-21 07:52:14.173 EGL_emulation            D  eglCreateContext: 0xc66c14e0: maj 2 min 0 rcv 2
2023-07-21 07:52:14.174 EGL_emulation            D  eglMakeCurrent: 0xc66c14e0: ver 2 0 (tinfo 0xc8683af0)
2023-07-21 07:52:14.178 eglCodecCommon           D  setVertexArrayObject: set vao to 1 (1) 0 0
2023-07-21 07:52:14.187 EGL_emulation            D  eglMakeCurrent: 0xe07c3c80: ver 2 0 (tinfo 0xc8683af0)
2023-07-21 07:52:14.253 chromium                 I  [INFO:CONSOLE(1141)] " [  0.001s] [ima.NativeBridge] OMID measurement with OM SDK SessionClient version 1.4.5-google_20230606 is ready. ", source: https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js (1141)
2023-07-21 07:52:14.290 chromium                 I  [INFO:CONSOLE(1141)] " [  0.041s] [ima.loader.AdsLoaderImpl] Requesting ads using new ads loader. ", source: https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js (1141)
2023-07-21 07:52:14.290 chromium                 I  [INFO:CONSOLE(1141)] " [  0.041s] [ima.loader.AdsLoaderImpl] requestAds, processing external request. ", source: https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js (1141)
2023-07-21 07:52:14.290 chromium                 I  [INFO:CONSOLE(1141)] " [  0.042s] [ima.loader.SequentialAdsLoader] Enqueued new request. ", source: https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js (1141)
2023-07-21 07:52:14.290 chromium                 I  [INFO:CONSOLE(1141)] " [  0.042s] [ima.loader.SequentialAdsLoader] Starting request from queue. ", source: https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js (1141)
2023-07-21 07:52:14.293 chromium                 I  [INFO:CONSOLE(1141)] " [  0.042s] [ima.loader.AdXmlFetcher] Using adsRequest.adsResponse for ad load. ", source: https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js (1141)
2023-07-21 07:52:14.295 chromium                 I  [INFO:CONSOLE(1141)] " [  0.047s] [ima.loader.AdXmlFetcher] Creating AdsRequestsMap. ", source: https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js (1141)
2023-07-21 07:52:14.298 chromium                 I  [INFO:CONSOLE(1141)] " [  0.050s] [ima.loader.SequentialAdsLoader] Starting request from queue. ", source: https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js (1141)
2023-07-21 07:52:14.341 AdTagLoader              D  Content progress: not ready
2023-07-21 07:52:14.350 EventLogger              D  timeline [eventTime=0.50, mediaPos=0.00, window=0, periodCount=1, windowCount=1, reason=SOURCE_UPDATE
2023-07-21 07:52:14.350 EventLogger              D    period [?]
2023-07-21 07:52:14.350 EventLogger              D    window [?, seekable=false, dynamic=false]
2023-07-21 07:52:14.350 EventLogger              D  ]
2023-07-21 07:52:14.351 AdTagLoader              D  Content progress: not ready
2023-07-21 07:52:14.352 AdTagLoader              D  Initialized with ads rendering settings: com.google.ads.interactivemedia.v3.impl.data.g@c1a74643
2023-07-21 07:52:14.361 EventLogger              D  timeline [eventTime=0.52, mediaPos=0.00, window=0, period=0, adGroup=0, ad=0, periodCount=1, windowCount=1, reason=SOURCE_UPDATE
2023-07-21 07:52:14.361 EventLogger              D    period [?]
2023-07-21 07:52:14.362 EventLogger              D    window [?, seekable=false, dynamic=false]
2023-07-21 07:52:14.362 EventLogger              D  ]
2023-07-21 07:52:14.368 chromium                 I  [INFO:CONSOLE(1141)] " [  0.120s] [ima.loader.AdsLoaderImpl] requestAds, processing internal request. ", source: https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js (1141)
2023-07-21 07:52:14.368 chromium                 I  [INFO:CONSOLE(1141)] " [  0.120s] [ima.loader.SequentialAdsLoader] Enqueued new request. ", source: https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js (1141)
2023-07-21 07:52:14.369 chromium                 I  [INFO:CONSOLE(1141)] " [  0.120s] [ima.loader.SequentialAdsLoader] Starting request from queue. ", source: https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js (1141)
2023-07-21 07:52:14.371 chromium                 I  [INFO:CONSOLE(1141)] " [  0.122s] [ima.loader.AdsManagerChannel] Error while processing a message URIError: URI malformed
                                                        at decodeURI (<anonymous>)
                                                        at aA (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:393:178)
                                                        at new L (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:388:518)
                                                        at YT (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:781:611)
                                                        at Pba (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:1340:44)
                                                        at https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:1339:725
                                                        at i$ (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:1340:9)
                                                        at j$ (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:1339:772)
                                                        at Caa (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:1341:385)
                                                        at A7 (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:1174:64) ", source: https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js (1141)
2023-07-21 07:52:14.391 IMASDK                   E  JsMessage (ima.loader.AdsManagerChannel): Error while processing a message URIError: URI malformed
                                                        at decodeURI (<anonymous>)
                                                        at aA (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:393:178)
                                                        at new L (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:388:518)
                                                        at YT (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:781:611)
                                                        at Pba (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:1340:44)
                                                        at https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:1339:725
                                                        at i$ (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:1340:9)
                                                        at j$ (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:1339:772)
                                                        at Caa (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:1341:385)
                                                        at A7 (https://imasdk.googleapis.com/native/core/3.363.4/native_bridge_debug__en.js:1174:64)
2023-07-21 07:52:14.403 AdTagLoader              D  onAdError
                                                      AdError [errorType: PLAY, errorCode: AdErrorCode [name: UNKNOWN_ERROR, number: 900], message: An unexpected error occurred and the cause is not known. Refer to the inner error for more info. Caused by: URIError: URI malformed]
                                                          at com.google.ads.interactivemedia.v3.internal.ajc.f(IMASDK:1)
                                                          at com.google.ads.interactivemedia.v3.internal.ajx.k(IMASDK:52)
                                                          at com.google.ads.interactivemedia.v3.internal.ake.f(IMASDK:6)
                                                          at com.google.ads.interactivemedia.v3.internal.aka.onPostMessage(IMASDK:2)
                                                          at androidx.webkit.internal.WebMessageListenerAdapter.onPostMessage(WebMessageListenerAdapter.java:54)
                                                          at java.lang.reflect.Method.invoke(Native Method)
                                                          at org.chromium.support_lib_boundary.util.BoundaryInterfaceReflectionUtil$InvocationHandlerWithDelegateGetter.invoke(BoundaryInterfaceReflectionUtil.java:162)
                                                          at java.lang.reflect.Proxy.invoke(Proxy.java:1006)
                                                          at $Proxy2.onPostMessage(Unknown Source)
                                                          at org.chromium.android_webview.WebMessageListenerHolder.onPostMessage(Unknown Source:50)
                                                          at android.os.MessageQueue.nativePollOnce(Native Method)
                                                          at android.os.MessageQueue.next(MessageQueue.java:336)
                                                          at android.os.Looper.loop(Looper.java:174)
                                                          at android.app.ActivityThread.main(ActivityThread.java:7356)
                                                          at java.lang.reflect.Method.invoke(Native Method)
                                                          at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
                                                          at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
2023-07-21 07:52:14.403 AdTagLoader              D  Removing ad 0 in ad group 0
2023-07-21 07:52:14.405 AdTagLoader              D  onAdEvent: ALL_ADS_COMPLETED
2023-07-21 07:52:14.413 EventLogger              E  internalError [eventTime=0.56, mediaPos=0.00, window=0, loadError
                                                      com.google.android.exoplayer2.source.ads.AdsMediaSource$AdLoadException: java.io.IOException: Failed to load ad group 0
                                                          at com.google.android.exoplayer2.ext.ima.AdTagLoader.handleAdGroupLoadError(AdTagLoader.java:1092)
                                                          at com.google.android.exoplayer2.ext.ima.AdTagLoader.access$1000(AdTagLoader.java:81)
                                                          at com.google.android.exoplayer2.ext.ima.AdTagLoader$ComponentListener.onAdError(AdTagLoader.java:1422)
                                                          at com.google.ads.interactivemedia.v3.internal.ajj.c(IMASDK:2)
                                                          at com.google.ads.interactivemedia.v3.internal.ajc.o(IMASDK:1)
                                                          at com.google.ads.interactivemedia.v3.internal.ajc.f(IMASDK:2)
                                                          at com.google.ads.interactivemedia.v3.internal.ajx.k(IMASDK:52)
                                                          at com.google.ads.interactivemedia.v3.internal.ake.f(IMASDK:6)
                                                          at com.google.ads.interactivemedia.v3.internal.aka.onPostMessage(IMASDK:2)
                                                          at androidx.webkit.internal.WebMessageListenerAdapter.onPostMessage(WebMessageListenerAdapter.java:54)
                                                          at java.lang.reflect.Method.invoke(Native Method)
                                                          at org.chromium.support_lib_boundary.util.BoundaryInterfaceReflectionUtil$InvocationHandlerWithDelegateGetter.invoke(BoundaryInterfaceReflectionUtil.java:162)
                                                          at java.lang.reflect.Proxy.invoke(Proxy.java:1006)
                                                          at $Proxy2.onPostMessage(Unknown Source)
                                                          at org.chromium.android_webview.WebMessageListenerHolder.onPostMessage(Unknown Source:50)
                                                          at android.os.MessageQueue.nativePollOnce(Native Method)
                                                          at android.os.MessageQueue.next(MessageQueue.java:336)
                                                          at android.os.Looper.loop(Looper.java:174)
                                                          at android.app.ActivityThread.main(ActivityThread.java:7356)
                                                          at java.lang.reflect.Method.invoke(Native Method)
                                                          at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
                                                          at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
                                                      Caused by: java.io.IOException: Failed to load ad group 0
                                                          at com.google.android.exoplayer2.ext.ima.AdTagLoader.handleAdGroupLoadError(AdTagLoader.java:1092)
                                                          at com.google.android.exoplayer2.ext.ima.AdTagLoader.access$1000(AdTagLoader.java:81)
                                                          at com.google.android.exoplayer2.ext.ima.AdTagLoader$ComponentListener.onAdError(AdTagLoader.java:1422)
                                                          at com.google.ads.interactivemedia.v3.internal.ajj.c(IMASDK:2)
                                                          at com.google.ads.interactivemedia.v3.internal.ajc.o(IMASDK:1)
                                                          at com.google.ads.interactivemedia.v3.internal.ajc.f(IMASDK:2)
                                                          at com.google.ads.interactivemedia.v3.internal.ajx.k(IMASDK:52)
                                                          at com.google.ads.interactivemedia.v3.internal.ake.f(IMASDK:6)
                                                          at com.google.ads.interactivemedia.v3.internal.aka.onPostMessage(IMASDK:2)
                                                          at androidx.webkit.internal.WebMessageListenerAdapter.onPostMessage(WebMessageListenerAdapter.java:54)
                                                          at java.lang.reflect.Method.invoke(Native Method)
                                                          at org.chromium.support_lib_boundary.util.BoundaryInterfaceReflectionUtil$InvocationHandlerWithDelegateGetter.invoke(BoundaryInterfaceReflectionUtil.java:162)
                                                          at java.lang.reflect.Proxy.invoke(Proxy.java:1006)
                                                          at $Proxy2.onPostMessage(Unknown Source)
                                                          at org.chromium.android_webview.WebMessageListenerHolder.onPostMessage(Unknown Source:50)
                                                          at android.os.MessageQueue.nativePollOnce(Native Method)
                                                          at android.os.MessageQueue.next(MessageQueue.java:336)
                                                          at android.os.Looper.loop(Looper.java:174)
                                                          at android.app.ActivityThread.main(ActivityThread.java:7356)
                                                          at java.lang.reflect.Method.invoke(Native Method)
                                                          at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
                                                          at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
                                                      Caused by: AdError [errorType: PLAY, errorCode: AdErrorCode [name: UNKNOWN_ERROR, number: 900], message: An unexpected error occurred and the cause is not known. Refer to the inner error for more info. Caused by: URIError: URI malformed]
                                                          at com.google.ads.interactivemedia.v3.internal.ajc.f(IMASDK:1)
                                                          at com.google.ads.interactivemedia.v3.internal.ajx.k(IMASDK:52)
                                                          at com.google.ads.interactivemedia.v3.internal.ake.f(IMASDK:6)
                                                          at com.google.ads.interactivemedia.v3.internal.aka.onPostMessage(IMASDK:2)
                                                          at androidx.webkit.internal.WebMessageListenerAdapter.onPostMessage(WebMessageListenerAdapter.java:54)
                                                          at java.lang.reflect.Method.invoke(Native Method)
                                                          at org.chromium.support_lib_boundary.util.BoundaryInterfaceReflectionUtil$InvocationHandlerWithDelegateGetter.invoke(BoundaryInterfaceReflectionUtil.java:162)
                                                          at java.lang.reflect.Proxy.invoke(Proxy.java:1006)
                                                          at $Proxy2.onPostMessage(Unknown Source)
                                                          at org.chromium.android_webview.WebMessageListenerHolder.onPostMessage(Unknown Source:50)
                                                          at android.os.MessageQueue.nativePollOnce(Native Method)
                                                          at android.os.MessageQueue.next(MessageQueue.java:336)
                                                          at android.os.Looper.loop(Looper.java:174)
                                                          at android.app.ActivityThread.main(ActivityThread.java:7356)
                                                          at java.lang.reflect.Method.invoke(Native Method)
                                                          at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
                                                          at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
                                                    ]
2023-07-21 07:52:14.416 EventLogger              D  timeline [eventTime=0.57, mediaPos=0.00, window=0, periodCount=1, windowCount=1, reason=SOURCE_UPDATE
2023-07-21 07:52:14.416 EventLogger              D    period [?]
2023-07-21 07:52:14.416 EventLogger              D    window [?, seekable=false, dynamic=false]
2023-07-21 07:52:14.416 EventLogger              D  ]
2023-07-21 07:52:14.416 AdTagLoader              W  onEnded without ad media info
2023-07-21 07:52:14.863 EventLogger              D  timeline [eventTime=1.02, mediaPos=0.00, window=0, period=0, periodCount=1, windowCount=1, reason=SOURCE_UPDATE
2023-07-21 07:52:14.863 EventLogger              D    period [128.27]
2023-07-21 07:52:14.864 EventLogger              D    window [128.27, seekable=true, dynamic=false]
2023-07-21 07:52:14.864 EventLogger              D  ]
2023-07-21 07:52:14.867 EventLogger              D  videoEnabled [eventTime=1.02, mediaPos=0.00, window=0, period=0]
2023-07-21 07:52:14.868 EventLogger              D  audioEnabled [eventTime=1.02, mediaPos=0.00, window=0, period=0]
2023-07-21 07:52:14.870 EventLogger              D  tracks [eventTime=1.02, mediaPos=0.00, window=0, period=0
2023-07-21 07:52:14.870 EventLogger              D    group [
2023-07-21 07:52:14.870 EventLogger              D      [X] Track:0, id=1, mimeType=video/avc, codecs=avc1.4D401F, res=1280x720, language=en, selectionFlags=[default], supported=YES
2023-07-21 07:52:14.870 EventLogger              D    ]
2023-07-21 07:52:14.870 EventLogger              D    group [
2023-07-21 07:52:14.870 EventLogger              D      [X] Track:0, id=2, mimeType=audio/mp4a-latm, codecs=mp4a.40.2, channels=2, sample_rate=44100, language=und, selectionFlags=[default], supported=YES
2023-07-21 07:52:14.870 EventLogger              D    ]
2023-07-21 07:52:14.870 EventLogger              D  ]
2023-07-21 07:52:14.871 OMXClient                I  IOmx service obtained
2023-07-21 07:52:14.873 SurfaceUtils             D  connecting to surface 0xc8c47808, reason connectToSurface
2023-07-21 07:52:14.873 MediaCodec               I  [OMX.google.h264.decoder] setting surface generation to 11167747
2023-07-21 07:52:14.874 SurfaceUtils             D  disconnecting from surface 0xc8c47808, reason connectToSurface(reconnect)
2023-07-21 07:52:14.874 SurfaceUtils             D  connecting to surface 0xc8c47808, reason connectToSurface(reconnect)
2023-07-21 07:52:14.874 ACodec                   E  [OMX.google.h264.decoder] setPortMode on output to DynamicANWBuffer failed w/ err -1010
2023-07-21 07:52:14.875 ACodec                   I  codec does not support config priority (err -1010)
2023-07-21 07:52:14.876 EventLogger              D  timeline [eventTime=1.03, mediaPos=0.00, window=0, period=0, periodCount=1, windowCount=1, reason=SOURCE_UPDATE
2023-07-21 07:52:14.876 EventLogger              D    period [128.27]
2023-07-21 07:52:14.877 EventLogger              D    window [128.27, seekable=true, dynamic=false]
2023-07-21 07:52:14.877 EventLogger              D  ]
2023-07-21 07:52:14.879 EventLogger              D  downstreamFormat [eventTime=1.03, mediaPos=0.00, window=0, period=0, id=1, mimeType=video/avc, codecs=avc1.4D401F, res=1280x720, language=en, selectionFlags=[default]]
2023-07-21 07:52:14.885 EventLogger              D  videoDecoderInitialized [eventTime=1.04, mediaPos=0.00, window=0, period=0, OMX.google.h264.decoder]
2023-07-21 07:52:14.886 EventLogger              D  videoInputFormat [eventTime=1.04, mediaPos=0.00, window=0, period=0, id=1, mimeType=video/avc, codecs=avc1.4D401F, res=1280x720, language=en, selectionFlags=[default]]
2023-07-21 07:52:14.886 OMXClient                I  IOmx service obtained
2023-07-21 07:52:14.887 EventLogger              D  downstreamFormat [eventTime=1.04, mediaPos=0.00, window=0, period=0, id=2, mimeType=audio/mp4a-latm, codecs=mp4a.40.2, channels=2, sample_rate=44100, language=und, selectionFlags=[default]]
2023-07-21 07:52:14.888 ACodec                   I  codec does not support config priority (err -2147483648)
2023-07-21 07:52:14.894 EventLogger              D  audioDecoderInitialized [eventTime=1.05, mediaPos=0.00, window=0, period=0, OMX.google.aac.decoder]
2023-07-21 07:52:14.895 EventLogger              D  audioInputFormat [eventTime=1.05, mediaPos=0.00, window=0, period=0, id=2, mimeType=audio/mp4a-latm, codecs=mp4a.40.2, channels=2, sample_rate=44100, language=und, selectionFlags=[default]]
2023-07-21 07:52:15.123 MediaCodec               D  [OMX.google.h264.decoder] setting dataspace on output surface to #104
2023-07-21 07:52:15.126 EventLogger              D  videoSize [eventTime=1.28, mediaPos=0.00, window=0, period=0, 1280, 720]
2023-07-21 07:52:15.140 EventLogger              D  surfaceSize [eventTime=1.29, mediaPos=0.00, window=0, period=0, 1080, 607]
2023-07-21 07:52:15.141 SoftwareRenderer         D  setting dataspace on output surface to #104
2023-07-21 07:52:15.159 EventLogger              D  renderedFirstFrame [eventTime=1.31, mediaPos=0.00, window=0, period=0, Surface(name=null)/@0x5c5d8b9]
2023-07-21 07:52:15.455 EventLogger              D  state [eventTime=1.61, mediaPos=0.00, window=0, period=0, READY]
2023-07-21 07:52:15.458 EventLogger              D  isPlaying [eventTime=1.61, mediaPos=0.00, window=0, period=0, true]
2023-07-21 07:52:15.472 AudioTrack               D  getTimestamp_l(10): device stall time corrected using current time 1558251130800
2023-07-21 07:52:15.504 AudioTrack               W  getTimestamp_l(10): retrograde timestamp time corrected, 1558266392300 < 1558273357000
2023-07-21 07:52:16.348 EventLogger              D  playWhenReady [eventTime=2.50, mediaPos=0.81, window=0, period=0, false, USER_REQUEST]
2023-07-21 07:52:16.353 EventLogger              D  isPlaying [eventTime=2.51, mediaPos=0.81, window=0, period=0, false]
2023-07-21 07:52:16.801 EventLogger              D  loading [eventTime=2.95, mediaPos=0.82, window=0, period=0, false]
2023-07-21 07:52:24.365 AdTagLoader              W  Unable to determine ad group index for ad group load error
                                                      java.io.IOException: Ad loading timed out
                                                          at com.google.android.exoplayer2.ext.ima.AdTagLoader.handleAdLoadTimeout(AdTagLoader.java:1098)
                                                          at com.google.android.exoplayer2.ext.ima.AdTagLoader.$r8$lambda$O25GS4aeawxxlofO7DreAKW0930(Unknown Source:0)
                                                          at com.google.android.exoplayer2.ext.ima.AdTagLoader$$ExternalSyntheticLambda0.run(Unknown Source:2)
                                                          at android.os.Handler.handleCallback(Handler.java:883)
                                                          at android.os.Handler.dispatchMessage(Handler.java:100)
                                                          at android.os.Looper.loop(Looper.java:214)
                                                          at android.app.ActivityThread.main(ActivityThread.java:7356)
                                                          at java.lang.reflect.Method.invoke(Native Method)
                                                          at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
                                                          at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)

Media
Any media and the following VAST URL in VMAP.
https://ad.doubleclick.net/ddm/pfadx/N703922.1534589IPRIMA.CZ/B30145407.369534207;sz=0x0;ord=%%VIEWID%%;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;dc_tdv=1;dcmt=text/xml;dc_sdk_apis=[APIFRAMEWORKS];dc_omid_p=[OMIDPARTNER];dc_vast=4;dc_mpos=[BREAKPOSITION];ltd=
Bug Report

[ ] You will email the zip file produced by adb bugreport to dev.exoplayer@gmail.com after filing this issue.

I think that is something you'd need to ask your contact for the IMA integration. The URL gets resolved by the IMA SDK based on information I don't know. One thing I noticed is that your URL has placeholders (e.g. [APIFRAMEWORKS], [OMIDPARTNER] and [BREAKPOSITION]) that need to be resolved to actual values before the request is made. I'm not sure if this is something the IMA SDK is meant to do or whether you need to resolve this before providing this URL.

Closing the issue because the problem is outside of our libraries (either the serving side or the IMA SDK)


text:
Automatic video quality does not work

Version
Media3 1.2.0
More version details
Automatic video quality does not work in LibreTube.They said it was related to Media3.We would appreciate it if you could fix your library and make the feature work in our application.
Devices that reproduce the issue
My Samsung A21s (Android 12).Many devices I've tested have had the problem.Works on YouTube.
Devices that do not reproduce the issue
No
Reproducible in the demo app?
Not tested
Reproduction steps
I can't use the demo application

Play the video in LibreTube.
Network quality is poor. Automatic selection selects the highest quality and does not change

https://youtu.be/SCSu6BkRaug&t=0
Expected result
Automatic select to adjust the quality according to the network.
Actual result
Auto selection doesn't work.Can't watch the video.
Media
Not applicable
Bug Report

[ ] You will email the zip file produced by adb bugreport to android-media-github@google.com after filing this issue.

Please elaborate a bit what is not working. The best way to demonstrate something isn't working is adding a media URI to the demo app and see whether this works. If it does not work add the media URI here in the issue and describe the steps how to repro the problem.
We are not evaluating other apps like LibreTube. If developers of an app say the problem is in ExoPlayer, they can apply the procedure from above and repro in the ExoPlayer main demo app.

I don't know how to use the demo application. The URL has been added to the issue. The highest video quality is selected and the automatic selection does not adjust the quality according to the network speed.Google doesn't have this problem

I don't think ExoPlayer can play YouTube videos directly I'm afraid. I'm not sure how LibreTube is doing this.
ExoPlayer has support for adaptive streaming by supporting DASH, HLS and SmoothStreaming. This includes an adaptive track selector that selects a format according to the available bandwidth. The demo app includes such formats and can be modified to try other media samples.
If a developer thinks that adaptive track selection for a stream does not work as intended, then they should file a bug with a sample stream and some reproduction steps. We are happy to help with this.

LibreTube runs streaming instances, not the YouTube API

1700481360.868 10410  8678 24735 I SurfaceView@5e0135d: 261995047 wPL, frameNr = 0
1700481360.868 10410  8678 24735 I SurfaceView@5e0135d: aOrMT: uB = true t = android.view.SurfaceControl$Transaction@bcf1e0b fN = 0 android.view.SurfaceView.access$500:124 android.view.SurfaceView$SurfaceViewPositionUpdateListener.positionLost:1785 android.graphics.RenderNode$CompositePositionUpdateListener.positionLost:326
1700481360.868 10410  8678 24735 I SurfaceView@5e0135d: aOrMT: vR.mWNT, vR = ViewRootImpl@b508fe6[IconBird]
1700481360.868 10410  8678 24735 I ViewRootImpl@b508fe6[IconBird]: mWNT: t = android.view.SurfaceControl$Transaction@bcf1e0b fN = 0 android.view.SurfaceView.applyOrMergeTransaction:1628 android.view.SurfaceView.access$500:124 android.view.SurfaceView$SurfaceViewPositionUpdateListener.positionLost:1785
1700481360.869 10410  8678 24735 I ViewRootImpl@b508fe6[IconBird]: mWNT: merge t to BBQ
1700481360.870 10410  8678  8678 I SurfaceView@5e0135d: windowStopped(true) false android.view.SurfaceView{5e0135d V.E...... ........ 0,0-720,405} of ViewRootImpl@b508fe6[IconBird]
1700481360.871 10410  8678  8678 I SurfaceView@5e0135d: pST: mTmpTransaction.apply, mTmpTransaction = android.view.SurfaceControl$Transaction@1acd309
1700481360.872 10410  8678  8678 I SurfaceView@5e0135d: surfaceDestroyed callback.size 1 #1 android.view.SurfaceView{5e0135d V.E...... ........ 0,0-720,405}
1700481360.873 10410  8678 30706 D SurfaceUtils: connecting to surface 0x7d6e70a010, reason connectToSurface
1700481360.873 10410  8678 30706 I MediaCodec: [OMX.Exynos.avc.dec] setting surface generation to 8886293


text:
🛑 Group - swe - www.swe.informatik.uni-goettingen.de is down

In 685f72a, Group - swe - www.swe.informatik.uni-goettingen.de (https://www.swe.informatik.uni-goettingen.de) was down:

HTTP code: 403
Response time: 647 ms

Resolved: Group - swe - www.swe.informatik.uni-goettingen.de is back up in d70b74b.

repo: androtelema/upptime

license: MIT


text:
Exception in MyAccountBuilder

I have now provided the whoami endpoint, then I come across this error:
11-24 13:56:29.464 V/AccountData133: new rdf-pub-admin@dev.rdf-pub.org/ActivityPub from jso: {
  "account": "rdf-pub-admin@dev.rdf-pub.org\/ActivityPub",
  "origin_name": "ActivityPub",
  "username": "rdf-pub-admin",
  "unique_name": "rdf-pub-admin@dev.rdf-pub.org",
  "credentials_verified": "1",
  "oauth": "true",
  "user_id": "0",
  "is_syncable": "true",
  "sync_automatically": "true",
  "fetch_frequency": "0",
  "myversion": "48",
  "order": "1",
  "user_token": "*******",
  "user_secret": "{\"access_token\":\"*****",\"expires_in\":300,\"refresh_expires_in\":1800,\"refresh_token\":\"*****",\"token_type\":\"Bearer\",\"not-before-policy\":1684133009,\"session_state\":\"******",\"scope\":\"read follow write\"}"
}
11-24 13:56:29.478 V/MyQuery: actorwebfinger_idToId; 0+rdf-pub-admin@dev.rdf-pub.org -> 0
11-24 13:56:29.488 D/OAuthClientKeys: Loaded OAuthClientKeysDynamic-17-dev.rdf-pub.org; Keys present
11-24 13:56:29.497 I/MyAccountBuilder:  Load failed: Invalid account; MyAccount: {(invalid) accountName:rdf-pub-admin@dev.rdf-pub.org/ActivityPub,Actor: {origin:ActivityPub, id: 0, webFingerId: rdf-pub-admin@dev.rdf-pub.org, username: rdf-pub-admin},not persistent,OAuth,access:NEVER,credentialsPresent,syncable,syncauto}
java.lang.Exception
	at org.andstatus.app.util.MyLog.getCurrentStackTrace(MyLog.kt:331)
	at org.andstatus.app.account.MyAccountBuilder.logLoadResult(MyAccountBuilder.kt:73)
	at org.andstatus.app.account.MyAccountBuilder.access$logLoadResult(MyAccountBuilder.kt:42)
	at org.andstatus.app.account.MyAccountBuilder$Companion.loadFromAccountData(MyAccountBuilder.kt:377)
	at org.andstatus.app.account.MyAccountBuilder$Companion$fromJsonString$1.invoke(MyAccountBuilder.kt:369)
	at org.andstatus.app.account.MyAccountBuilder$Companion$fromJsonString$1.invoke(MyAccountBuilder.kt:366)
	at org.andstatus.app.account.MyAccountBuilder$Companion.fromJsonString$lambda$0(MyAccountBuilder.kt:366)
	at org.andstatus.app.account.MyAccountBuilder$Companion.$r8$lambda$GICBHO9t4YawFEbeJv85N1prV5Y(Unknown Source:0)
	at org.andstatus.app.account.MyAccountBuilder$Companion$$ExternalSyntheticLambda0.apply(Unknown Source:2)
	at io.vavr.control.Try.map(Try.java:416)
	at org.andstatus.app.account.MyAccountBuilder$Companion.fromJsonString(MyAccountBuilder.kt:366)
	at org.andstatus.app.account.StateOfAccountChangeProcess.<init>(StateOfAccountChangeProcess.kt:74)
	at org.andstatus.app.account.StateOfAccountChangeProcess.<init>(Unknown Source:0)
	at org.andstatus.app.account.StateOfAccountChangeProcess$Companion.fromStoredState(StateOfAccountChangeProcess.kt:166)
	at org.andstatus.app.account.AccountSettingsActivity.restoreState(AccountSettingsActivity.kt:203)
	at org.andstatus.app.account.AccountSettingsActivity.onCreate(AccountSettingsActivity.kt:167)
	at android.app.Activity.performCreate(Activity.java:8342)
	at android.app.Activity.performCreate(Activity.java:8321)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1421)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3626)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3782)
	at android.app.ActivityThread.handleRelaunchActivityInner(ActivityThread.java:5783)
	at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:5674)
	at android.app.servertransaction.ActivityRelaunchItem.execute(ActivityRelaunchItem.java:71)
	at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:45)
	at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:138)
	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2307)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loopOnce(Looper.java:201)
	at android.os.Looper.loop(Looper.java:288)
	at android.app.ActivityThread.main(ActivityThread.java:7924)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)

@naturzukunft It may help if you create an account for "andstatus" at your server so I could test it myself!

@yvolk you can register a user here: https://login.m4h.network/auth/realms/LOA/login-actions/registration?client_id=account-console&tab_id=csiOMexnQRQ

@naturzukunft OK, I registered andstatus@gmail.com there, but in order to access your dev server I need to register something like "andstatus@dev.rdf-pub.org"  ?!

The server was not running, what exactly (endpoint) do you call?
rdf-pub creates the actor profile, if the authenticated actor is calling it's profile the first time. so if you try to access the profile as anonymous user before, it's not available.
But the whoami should work after registration
Info, you can check if the server is up with https://dev.rdf-pub.org/actuator/health

@naturzukunft Did you try connect with AndStatus?
I'm trying and it's failing at the Client registration step:

AndStatus posts to  "https://login.m4h.network/auth/realms/LOA/clients-registrations/openid-connect"
this:

{
  "redirect_uris": [
    "http:\/\/oauth-redirect.andstatus.org"
  ],
  "client_name": "AndStatus",
  "client_uri": "http:\/\/andstatus.org\/andstatus",
  "logo_uri": "http:\/\/andstatus.org\/images\/andstatus-logo.png",
  "scope": "read write follow",
  "policy_uri": "https:\/\/github.com\/andstatus\/andstatus\/blob\/master\/doc\/Privacy-Policy.md",
}

and gets:
Registration failed with Status code: FORBIDDEN; hard; Error='insufficient_scope'; ; statusCode:FORBIDDEN (403); url:'https://login.m4h.network/auth/realms/LOA/clients-registrations/openid-connect'; response:'{"error":"insufficient_scope","error…'

@naturzukunft Did you try connect with AndStatus app?

yes, that was working, after i did some settings in keycloack.
I added *.andstatus.org to trusted hosts.
if i do a ping andstatus.org i get
64 bytes from www.andstatus.org (185.87.193.233): icmp_seq=1 ttl=52 time=63.0 ms
The request, that produces the error above cames from 37.204.0.215 ?
Fredy

If 37.204.0.215 is your dev machine, i can add it to trusted hosts!

Yes, currently this is my IP (but it's not static...)

ResourceAccessException: I/O error on GET request for "https://login.m4h.network/auth/realms/LOA/protocol/openid-connect/certs": login.m4h.network; nested exception is java.net.UnknownHostException: login.m4h.network
i've to do some setup to access the whoami endpoint from postman.

i also has trouble to access keycloak from postman. i ve to contact my keycloak admin. sorry.

^ tomorrow he will take a look on it.

Info: The admin unfortunately got sick and is still in bed

Today i was able to request a jwt again!
Let me know, if i should add a new ip address to thrustred hosts

Hello @naturzukunft !
I see my IP didn't change yet.

I tested once again

Create ActivityPub account
Unique name: andstatus@dev.rdf-pub.org
Client registration succeeded
Web page prompting for my email and password opened
I typed "andstatus@gmail.com" and the password that I used during registration at  https://login.m4h.network/auth/realms/LOA/login-actions/registration?client_id=account-console&tab_id=csiOMexnQRQ
A screen with confirmation opened and I confirmed that I allow AndStatus app to access my account.
Got Access token as I see in logs
Requested: uri: 'https://dev.rdf-pub.org/api/whoami' and successfully got this Person object:

{
  "id": "https:\/\/dev.rdf-pub.org\/actor\/4ee107d9-753b-43a8-a952-3d6571487cf2",
  "type": "Person",
  "inboxSparql": "https:\/\/dev.rdf-pub.org\/actor\/4ee107d9-753b-43a8-a952-3d6571487cf2\/inbox\/sparql",
  "outboxSparql": "https:\/\/dev.rdf-pub.org\/actor\/4ee107d9-753b-43a8-a952-3d6571487cf2\/outbox\/sparql",
  "identifier": "4ee107d9-753b-43a8-a952-3d6571487cf2",
  "version": {
    "type": "xsd:long",
    "@value": "1"
  },
  "inbox": "https:\/\/dev.rdf-pub.org\/actor\/4ee107d9-753b-43a8-a952-3d6571487cf2\/inbox",
  "outbox": "https:\/\/dev.rdf-pub.org\/actor\/4ee107d9-753b-43a8-a952-3d6571487cf2\/outbox",
  "preferredUsername": "4ee107d9-753b-43a8-a952-3d6571487cf2",
  "@context": [
    "https:\/\/schema.org\/docs\/jsonldcontext.json",
    "https:\/\/www.w3.org\/ns\/activitystreams",
    "https:\/\/rdf-pub.org\/schema\/rdf-pub-context.json"
  ]
}

And AndStatus decided that this is metadata of some other Person:
These are credentials of another account: 4ee107d9-753b-43a8-a952-3d6571487cf2@dev.rdf-pub.org/ActivityPub account name: andstatus@dev.rdf-pub.org/ActivityPub vs username: 4ee107d9-753b-43a8-a952-3d6571487cf2

I'm not sure, if this is correct. 4ee107d9-753b-43a8-a952-3d6571487cf2 is the userid which is in the subject claim of the token. it's the userid of your user in keycloak. If you request via webfinger you get https://dev.rdf-pub.org/actor/4ee107d9-753b-43a8-a952-3d6571487cf2
I think that is valid.
I'm wondering why preferredUsername is 4ee107d9-753b-43a8-a952-3d6571487cf2.

rdf-pub is not working with usernames, because it's terrible if the username is changing!
Then all subjects are wrong.

Yes of corse. Thats a bug.
Am 11. Dezember 2023 20:04:53 MEZ schrieb Yuri Volkov @.***>:

rdf-pub is not working with usernames, because it's terrible if the username is changing!
Then all subjects are wrong.

Ok. But preferredUsername should be "andstatus" in this object anyway, I think.
--
Reply to this email directly or view it on GitHub:
https://github.com/andstatus/andstatus/issues/585#issuecomment-1850707777
You are receiving this because you were mentioned.
Message ID: @.***>
-- Sent from /e/OS Mail.

but... i'm thinking about making the preferred username independent of the oauth2 server. Because if different oauth2 servers are offered for authentication, the preferred username from the JWToken is no longer unique. The same with the userId, which in rdf-pub is currently the id of the oauth2 server. it is possible that I will introduce a mapping here too.
Thanks for supporting me and rdf-pub. I'm
I will not be available from 14.12. to 17.12.

authors: naturzukunft yvolk

repo: andstatus/andstatus


text:
Why there isn't ZPOPMAX in Sorted Set?

I'd like to pop the value with the max score, but redis-py does not have zpopmax nor zpopmin.
So what are the suitable replaces of ZPOPMAX and ZPOPMIN?

See this?. Zpopmin and Zpopmax is new command in redis 5.0.0, maybe the command is in release.
I use zrevrange('yourkey', 0, 1) to get the max value and then zrem('yourkey') to delete the element.

@ramwin Your method is a workaround way. However, it is not thread safe. two threads may get the same value.

Yes, if you want to ensure the thread safe, you should do some extra work using pipelining.

This should be resolved via #1037

Yes, if you want to ensure the thread safe, you should do some extra work using pipelining or transactions.

You need to use both pipelining AND transactions. Pipelining just ensures that the commands are executed in order and also reduces the RTT(Round Trip Time). Transactions are the ones that ensure atomicity of the commands in execution.

authors: itamarhaber kingname namanjain2707 ramwin

repo: andymccurdy/redis-py


text:
StrictRedis blocked if socket_timeout=None

This is my code snippet:
redis_client = redis.StrictRedis(host=redis_ip, port=redis_port, db=redis_no, password=passwd)
while(True): {
	id = get_item_from_kafka() #get id from kafka
	redis_client.get(id)
	time.sleep(1)
	print id
}
Is there any condition that this code snippnet blocked and never print id again(At the beginning, the code works fine and print id for several time). The socket_timeout parameter by default is None.
Ps:this code is run in k8s

There's not enough information here to figure out what's going on. Are you sure the redit_client.get() call is the one blocked? Could the call to get the ID from kafka be the culprit?

No info has been added for 6 months. I'm going to close this issue. If you're still having this issue and can provide more info, please feel free to reopen.

authors: andymccurdy rebornfxx


text:
Issue 126

Implemented a view change toggled by a button on the page. Min date is the earliest VCC - 10 days, max date is latest fix + 10 days.
Looking for feedback:

where should I place the button?
I set padding for 10 days, suggestions?

Oops this is actually for issue #155

repo: andymeneely/vulnerability-history


text:
可以把自动签到一起写了吗大佬

弹窗完成后无法进行自动签到，需要手动点击签到

检测到“xxx 邀请您使用签到”窗口后脚本会点击“打开应用”按钮，然后在签到窗口中点击“点击签到”按钮。

所以你的情况是脚本能点击“打开应用”按钮，但是无法正常点击“点击签到”按钮？
告诉我你的显示器分辨率和缩放大小，我再研究研究哪里出了问题。


text:
fix: add video_id to oembed for issue #286

#286
video_id seems to be vimeo specific field, this may confuse users who youtube or an other video source and the field would be null.

Thanks @MarcMcIntosh, I'll publish this shortly.

Published in v3.3.4

Neat :)

Neat :)

authors: MarcMcIntosh angeloashmore

repo: angeloashmore/gatsby-source-prismic


text:
n-Queens example does not work on db2 v10.5

Describe the bug
When deploying the SPs, there is an error related to the guards when using boolean values.
To Reproduce
Steps to reproduce the behavior:

Deploy the n-queens example, specifically in the SOLVE_N_QUEENS procedure, and it will return a SQL0104 syntax error.

Expected behavior
Deploy the example without any error.
Db2 installation (please complete the following information):

Server OS: AIX
Db2 version with fixpack 10.5.11
Log4db2 version 1

Solved


text:
Error when consuming shared library on cli monorepo

When using shared library on cli monorepo and register the shared library name with SharedMappings register method.
when serving the app we get the follow warning -
"[DEP_WEBPACK_COMPILATION_ASSETS] DeprecationWarning: Compilation.assets will be frozen in future"
when we made changes in one of the micro frontend application and saved, we get the follow error -
"Conflict: Multiple assets emit different content to the same filename"
the error prevent from the app to re compile the application and the changes doesn't reflected.
used with version 1.2.0 and angular version 11 cli.

Thanks for reaching out. Actually, I know this one. To solve those issue, just add the following property to the output section in your webpack configs:
chunkFilename: '[name]-[contenthash].js',

Btw: Can you share your example?

@manfredsteyer Thanks a lot, it's solved my problem 👍
Sure, this is just a simple application generated from the Angular cli. i am using it for my POC to investigate micro frontend architecture.
this is the link to the repo - Link

@chenlevin89 That’s one dead 404 link right there.

authors: Frikki chenlevin89 manfredsteyer


text:
feat(dependencies): Add data-fromId and data-toId on links svg canvas

This allow advanced css styling of links based on their related task ids.

Coverage decreased (-0.1%) to 48.785% when pulling b5f0ee34a4cb55996f9dd70d64dfc567fc2be55f on dependencies-advanced-css into 958d686e274e119d0e433a170203b59b8bcbb718 on master.

authors: Toilal coveralls

repo: angular-gantt/angular-gantt


text:
Chuck Norris Jokes Challenge

https://github.com/JamesChe91/chuckNorrisChallenge/

Hi @JamesChe91 , wow what a great solution :neckbeard: :100:
I :heart: your code, very clean, great use of RxJS, :confetti_ball:

repo: angular-medellin/challenges


text:
'format-day-title' can not work

I added format-day-title="yyyy MMMM" into datepicker input element.
but it can not work, the title still show

When I modify ui-bootstrap-tpls.js and change

it's works.
I think this issue need to fix.

@smallg, I'm not exactly sure I follow.  What do you mean by 'title?'

@icfantv I want format this title

but this way can not work format-day-title="yyyy MMMM"

That is not supported as far as I can see from the documentation. You have to use the datepicker-options attribute to bind the desired datepicker options.

it works, thanks

authors: icfantv smallg wesleycho

repo: angular-ui/bootstrap


text:
When installing with bower templates are not accessible

After installing package with bower.
I've missing templates directory.
I found that they are missing in: https://github.com/angular-ui/bootstrap-bower
Whats more this missing templates are searched in
$compile/tpload?p0=uib%2Ftemplate%2Fmodal%2Fbackdrop.html&p1=404&p2=Not%20Found

hardcoded uib directory? structure of my project is following, and I rather like to keep it like it is
my-project:
   |_ javascript
   |_ libs  <-- where bower downloads are
   |_ templates
   |_ index.html

Could you help me?

Ok solved according to this stackoverflow.
I've missed that i need to include: ui-bootstrap-tpls.


text:
fixes TypeError: Cannot set property 'isOpen' of null

Sometimes $evalAsync is fired when scope is null and I get error in console. This fixes that specificc situation

@RobJacobs is this possible when using $evalAsync? Seems strange to me...but not necessarily against this fix. Thoughts?

@wesleycho I agree, would be nice to see a plunk reproducing the problem or a description of how this occurred. I'm not against the change but there may be a better approach.

I'll merge this for now, and perhaps an investigation could be done to figure out what is happening here - this seems like a perpetual problem :( .

authors: RobJacobs kwiateusz wesleycho


text:
onError Transition Hook cannot continue when returned a TransitionState

This issue tracker is for Bug Reports and Feature Requests only.
Please direct requests for help to StackOverflow.  See http://bit.ly/UIR-SOF for details.
This is a:

[1 ] Bug Report

My version of UI-Router is: 1.0.3
Bug Report
Current Behavior:
When returning a transition.target object from the onError transition hook, the target is not transitioned to.
Expected Behavior:
returning a transition.target object from any transition hook should transition to that target.
Link to Plunker that reproduces the issue:
https://plnkr.co/edit/FILx0kLzPPhfWzXROuAZ
Thanks for the awesome work on this package everyone.

Thanks for the plunker!
The onError hooks happen after a transition is complete.  As such, they cannot redirect the current transition.  You could instead start a new transition using $state.go, however.
See here: https://ui-router.github.io/ng1/docs/latest/classes/transition.transitionservice.html#onerror
specifically the Lifecyle section:

Lifecycle
The onError hooks are chained off the Transition's promise (see Transition.promise). If a Transition fails, its promise is rejected and the onError hooks are invoked. The onError hooks are invoked in priority order.
Since these hooks are run after the transition is over, their return value is ignored.

Yep all works fine using transition.router.stateService.go in this case.
I think I got confused in the docs because onError does specify that the return value is ignored but this wasn't mentioned when I read the TransitionHookFn signature section.
Thanks for your help

authors: christopherthielen sean-stanley

repo: angular-ui/ui-router


text:
feat(uiSrefActive): match on abstract states that are included by the current state

This pull request is based on the suggestion by @nateabele on issue #1431. It enables ui-sref-active to be passed an expression that should evaluate to an object hash with the activeClass and state properties. If state is provided, activeClass is applied to its element if the current active state includes state, even if state is abstract. It works even if ui-sref is found neither on the element nor on any of its children. Furthermore, if state is provided, it takes precedence over the state exposed by ui-sref. Hope it helps to close #1431 :)

Hey, sorry for not responding right away. After a belated internal discussion with @christopherthielen, we agreed an ng-class-style interface would be better, i.e. with class names as keys and state names/globs as the values, i.e. { active: "admin.*" } — I think that would provide a lot more flexibility and a lot less verbosity?
Would you be willing to update the PR to support that? If not, no worries, and sorry for the back-and-forth.

Hi, no problem at all about that! I definitely agree with you guys about the ng-{class,style} providing a cleaner interface.
I will update the PR in this week-end.

Awesome, thanks!

Hi, I've updated the PR to match the new requirements. Please, let me know if anything else needs to be done :)

Can we get another PR to merge to feature-1.0?

Hi, I've just opened PR #2375 which brings this feature into feature-1.0.

This is a great feature. you should really document it. I see no mention of this.

Agree with @shali3, docs are missing this.

authors: christopherthielen fpipita maybenull nateabele shali3


text:
Form gets $dirty by default with debounce = false

This is a follow up of issue #238 which should have fixed incorrect $dirty reports.
Basically what happens is that a form just loaded will report the field as being dirty, even if it hasn't been touched yet - IF debounce is set to false. When debounce is set to true, the warnings works kind-of correctly, but only after a certain delay - meaning the user must pause before hitting save.

Please post a plunker reproducing the issue so people can look into fixing it.
A PR fixing the issue would be nice if you have found a reproducible bug.

sorry for seeming daft, but I've never made a plunkr. Do you have a good sample using angular-ui-tinymce unto which I could then build upon?

If debounce is set to 'false', no dirty-check is made before updating the view. Therefore, the editor is considered dirty by default (take a look at 'debouncedUpdate', which performs a dirty-check).
https://github.com/angular-ui/ui-tinymce/blob/master/src/tinymce.js#L95-L102
A tested patch:
// Update model when:
// - a button has been clicked [ExecCommand]
// - the editor content has been modified [change]
// - the node has changed [NodeChange]
// - an object has been resized (table, image) [ObjectResized]
ed.on('ExecCommand change NodeChange ObjectResized', function () {
    if (options.debounce) debouncedUpdate(ed);
    else if (ed.isDirty()) {
        ed.save();
        updateView(ed);
    }
});

authors: christophbuehler deeg iJungleboy

repo: angular-ui/ui-tinymce


text:
Do not support import？

Hello, it is now using npm to manage my project dependencies, but the dependency of this project can not be introduced by import

This project is dead, instead install directly what you need from the list.

authors: PowerKiKi shaodahong

repo: angular-ui/ui-utils


text:
Angular CLI 1.7.3 Cannot find module '@angular-devkit/build-optimizer'

Versions
<!--
Angular CLI: 1.7.3
Node: 9.8.0
OS: darwin x64
Angular: 5.2.9
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic
... platform-server, router

@angular/cdk: 5.2.4
@angular/cli: 1.7.3
@angular/flex-layout: 5.0.0-beta.13
@angular/material: 5.2.4
@schematics/package-update: 0.3.2
typescript: 2.5.3
webpack-node-externals: 1.6.0
webpack: 3.10.0

Repro steps

npm run build:prod

Observed behavior
Cannot find module '@angular-devkit/build-optimizer' from '/my/project/directory'
Error: Cannot find module '@angular-devkit/build-optimizer' from '/my/project/directory'
    at Function.module.exports [as sync] (/my/project/directory/node_modules/resolve/lib/sync.js:40:15)
    at Object.getCommonConfig (/my/project/directory/node_modules/@angular/cli/models/webpack-configs/common.js:138:56)
    at NgCliWebpackConfig.buildConfig (/my/project/directory/node_modules/@angular/cli/models/webpack-config.js:33:31)
    at Class.run (/my/project/directory/node_modules/@angular/cli/tasks/build.js:31:92)
    at Class.run (/my/project/directory/node_modules/@angular/cli/commands/build.js:250:40)
    at resolve (/my/project/directory/node_modules/@angular/cli/ember-cli/lib/models/command.js:261:20)
    at new Promise (<anonymous>)
    at Class.validateAndRun (/my/project/directory/node_modules/@angular/cli/ember-cli/lib/models/command.js:240:12)
    at Promise.resolve.then.then (/my/project/directory/node_modules/@angular/cli/ember-cli/lib/cli/cli.js:140:24)
    at <anonymous>
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! search@0.0.0 build:prod: `ng build --prod`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the search@0.0.0 build:prod script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/Mark/.npm/_logs/2018-03-20T12_06_15_012Z-debug.log

Desired behavior
To build prod without error
Mention any other details that might be useful (optional)
My project's package.json
"dependencies": {
    "@angular/animations": "^5.2.9",
    "@angular/cdk": "^5.2.4",
    "@angular/common": "^5.2.0",
    "@angular/compiler": "^5.2.0",
    "@angular/core": "^5.2.0",
    "@angular/flex-layout": "^5.0.0-beta.13",
    "@angular/forms": "^5.2.0",
    "@angular/http": "^5.2.0",
    "@angular/material": "^5.2.4",
    "@angular/platform-browser": "^5.2.0",
    "@angular/platform-browser-dynamic": "^5.2.0",
    "@angular/platform-server": "^5.2.9",
    "@angular/router": "^5.2.0",
    "@ngrx/effects": "^4.1.0",
    "@ngrx/store": "^4.1.0",
    "@nguniversal/express-engine": "^5.0.0-beta.6",
    "@nguniversal/module-map-ngfactory-loader": "^5.0.0-beta.6",
    "@ngx-translate/core": "^9.1.1",
    "@ngx-translate/http-loader": "^2.0.1",
    "bodybuilder": "2.2.1",
    "core-js": "^2.4.1",
    "elasticsearch": "^13.3.1",
    "hammerjs": "^2.0.8",
    "intl": "^1.2.5",
    "jsdom": "^11.6.2",
    "jsdom-global": "^3.0.2",
    "libphonenumber-js": "^1.0.24",
    "rxjs": "^5.5.6",
    "ts-loader": "^3.5.0",
    "web-animations-js": "^2.3.1",
    "zone.js": "^0.8.19"
  },
  "devDependencies": {
    "@angular/cli": "~1.7.3",
    "@angular/compiler-cli": "^5.2.0",
    "@ngrx/store-devtools": "^4.0.0",
    "@types/googlemaps": "^3.30.0",
    "@types/jasmine": "~2.8.3",
    "@types/node": "~6.0.60",
    "codelyzer": "^4.0.1",
    "jasmine-core": "~2.8.0",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "~2.0.0",
    "karma-chrome-launcher": "~2.2.0",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "^1.2.1",
    "karma-jasmine": "~1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "node-sass": "^4.7.2",
    "protractor": "~5.1.2",
    "ts-node": "~4.1.0",
    "tslint": "~5.9.1",
    "typescript": "~2.5.3",
    "webpack": "^3.10.0",
    "webpack-node-externals": "^1.6.0"
  }

NPM was working fine for me, but then it suggested I update npm from 5.6.0 to 5.7.1.  I ran "npm i npm", and after that was done, I started getting the above error.  (NPM claimed it probably wasn't being caused by npm.)
I then ran "npm update" (as administrator), and now I'm no longer getting this error.
Not sure if this means anything to anyone, but I thought I'd at least log my experience in case it helps someone figure out what's causing this error.

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.

repo: angular/angular-cli


text:
ng serve crashes upon change

🐞 Bug report
Command (mark with an x)

- [ ] new
- [ ] build
- [ x ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Is this a regression?

Yes, the previous version in which this bug was not present was: ....
Description
when serving an angular app, after any change made the watcher recompiles it and crashes
🔬 Minimal Reproduction
ng new testApp
ng serve
Make any change to any project file (just like a new line in app.component.hml)
🔥 Exception or Error

`* Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
ℹ ｢wdm｣: Compiled successfully.
ℹ ｢wdm｣: Compiling...
 98% after emitting SizeLimitsPlugin(node:18296) UnhandledPromiseRejectionWarning: Error [ERR_INSPECTOR_NOT_CONNECTED]: Session is not connected
    at Session.post (inspector.js:75:13)
    at Promise (/home/jcuervas/projects/angular_test/test/node_modules/webpack/lib/debug/ProfilingPlugin.js:54:25)
    at new Promise ()
    at Profiler.sendCommand (/home/jcuervas/projects/angular_test/test/node_modules/webpack/lib/debug/ProfilingPlugin.js:53:11)
    at Profiler.stopProfiling (/home/jcuervas/projects/angular_test/test/node_modules/webpack/lib/debug/ProfilingPlugin.js:76:15)
    at Proxy.compiler.hooks.done.tapAsync (/home/jcuervas/projects/angular_test/test/node_modules/webpack/lib/debug/ProfilingPlugin.js:209:21)
    at args (/home/jcuervas/projects/angular_test/test/node_modules/speed-measure-webpack-plugin/WrappedPlugin/index.js:40:16)
    at args (/home/jcuervas/projects/angular_test/test/node_modules/webpack/lib/debug/ProfilingPlugin.js:394:11)
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/home/jcuervas/projects/angular_test/test/node_modules/tapable/lib/HookCodeFactory.js:33:10), :92:1)
    at Watching._done (/home/jcuervas/projects/angular_test/test/node_modules/webpack/lib/Watching.js:97:28)
    at compiler.emitRecords.err (/home/jcuervas/projects/angular_test/test/node_modules/webpack/lib/Watching.js:72:19)
    at Compiler.emitRecords (/home/jcuervas/projects/angular_test/test/node_modules/webpack/lib/Compiler.js:449:39)
    at compiler.emitAssets.err (/home/jcuervas/projects/angular_test/test/node_modules/webpack/lib/Watching.js:53:20)
    at hooks.afterEmit.callAsync.err (/home/jcuervas/projects/angular_test/test/node_modules/webpack/lib/Compiler.js:435:14)
    at _next0 (eval at create (/home/jcuervas/projects/angular_test/test/node_modules/tapable/lib/HookCodeFactory.js:33:10), :32:1)
    at _err0 (eval at create (/home/jcuervas/projects/angular_test/test/node_modules/tapable/lib/HookCodeFactory.js:33:10), :43:1)
(node:18296) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:18296) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
`

🌍 Your Environment

Angular CLI: 8.0.6
Node: 10.16.0
OS: linux x64
Angular: 8.0.3
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.800.6
@angular-devkit/build-angular     0.800.6
@angular-devkit/build-optimizer   0.800.6
@angular-devkit/build-webpack     0.800.6
@angular-devkit/core              8.0.6
@angular-devkit/schematics        8.0.6
@angular/cli                      8.0.6
@ngtools/webpack                  8.0.6
@schematics/angular               8.0.6
@schematics/update                0.800.6
rxjs                              6.4.0
typescript                        3.4.5
webpack                           4.30.0

Anything else relevant?

My system is under ubuntu 19.04,
just tested same under windows and bug is not happening, everything is alright

I tried following your steps in a new app and didn't see any of the errors you mentioned. Can you double check this happens with a brand new app in your machine?
In the log you included it shows stuff about profiling which is not enabled by default for new apps, did you change any build options perhaps?

umm you gave me the hint. I enabled this env variable: NG_BUILD_PROFILING="true". Don't remember why.
After removing it the compiler is going ok.
Thanks

authors: filipesilva jcuervas


text:
Add param in config to exclude files to help to solve the "heap out of memory" issue

🚀 Feature request
Command (mark with an x)

- [ ] build

Description
Hi There,
I had suffered a lot from the "heap out of memory" issue recently. That is caused by the source map for my case. (Angular 7 + Node 8 + window10)
I found this function in webpack config utility: (node_modules@angular-devkit\build-angular\src\angular-cli-files\models\webpack-configs\utils.js)
function getSourceMapDevTool() {
    // ...

    return new webpack_1.SourceMapDevToolPlugin({
        filename: inlineSourceMap ? undefined : '[file].map',
        include,
        exclude: ['vendor.js'],    //<----  Here, I excluded vendor.js and the issue gone. Build speed is much faster and it almost did not affect daily debugging!**
        append: hiddenSourceMap ? false : undefined,
    });

I noticed that there is a configuration in "angular.json" "sourceMap" under architect->build->option;
Could you guys please add an "exclude" param in that object? So that specified file could be excluded by us individually. If you can add that function, that might help a lot of people. Thank you!
Thanks,
Joey

Did you already try increasing allowed heap size for your node process?
You can create an environment variable for this:
name: NODE_OPTIONS
value: --max_old_space_size=4096

@flash-me Yep. Some guys in our team use "cross-env NODE_OPTIONS=--max_old_space_size=4096" in package.json to fix this issue.

Since nodejs v8 you can also set a user / system variable.
Enter in an elevated command prompt
setx NODE_OPTIONS --max_old_space_size=4096
Add \m for setting it as a system variable.

@flash-me That is quite helpful. Thank you!

Isn't this only a temporary solution? What are we looking at in the long term?

It's not like as if one could say "Let's turn this feature off" or "Let's optimize this particular part" to solve this. Every part of the toolchain affects the memory usage. From typescript itself to terser.
If the only requirement is low heap size, then go ahead and process everything sequentially. The drawback are gigantic build times.
Even the used OS has an impact on this. On *nix machines you will build faster then on Windows with same hardware. Thats because Microsoft has a different interpretation of a process than *nix.
To put it straight: There are ongoing efforts to reduce this, but you will have higher memory usage in general when developing with angular compared with default node.js.

I believe we've made a few improvements to memory usage in the last few versions. Node has also made a lot of headway in this area (in particular version 10 or 12 I believe?). Is this still an issue for you on the latest CLI and a more up-to-date version of Node?
We'd rather solve the underlying memory-usage issue out-of-the-box than introduce a new option for users to tweak.

Closing a there was no further communication. If the problem persists feel free to open a new issue.

Closing a there was no further communication. If the problem persists feel free to open a new issue.


text:
Unable to run unit tests using npm scripts

Please provide us with the following information:

OS?

Linux (Ubuntu). Mac OSX (El Capitan)

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

@angular/cli: 1.0.0-beta.30
node: 6.9.1
os: darwin x64

Repro steps.
I have npm script to run unit tests on CI
  "scripts": {
    "ng": "ng",
    "start": "ng serve --host 0.0.0.0",
    "lint": "tslint \"src/**/*.ts\"",
    "test": "npm run ng -- test --single-run"
   ...

when I try to run npm t I get an error as shown below. It was working fine before beta.30.
The log given by the failure.
You have to be inside an angular-cli project in order to use the test command.
Mention any other details that might be useful.

Thanks! We'll be in touch soon.

@m0t0r check my answer here https://github.com/angular/angular-cli/issues/4439#issuecomment-277576090 , i think your issue is related.

@beeman, yes that helped, thanks a lot!

@hansl, would it possible to add a note on migration from angular-cli beta.28  to @angular/cli beta.30 that there should not be any devDependency on angular-cliin package.json as it seems to cause different issues. I can do a PR if you could guide where it should be added. Thank you

@m0t0r I'm working on a check that detects this. Hope to have it in the cli within the next release

@beeman great, thanks!


text:
chore(server): Disable compileOnSave within tsconfig.json

To stop the annoying: "TS Emit Failed" within your IDE, since your server is already watching and recompiling

Oh god yes please!
lsgtm (looks so good to me)

authors: filipesilva intellix


text:
Docs TS: guide dependency-injection

[ ] dependency-injection

Je prends

authors: aradjdi ocombe

repo: angular/angular-fr


text:
Docs TS: guide router

[ ] router

Je peux m'occuper de celui-ci

Plutôt wip ?

Yep, merci.
L'interface Github sur mobile est juste atroce :(

authors: feloy manekinekko ocombe


text:
_http_outgoing.js:351       throw new TypeError('The header content contains invalid characters');       ^

Environment :
Windows 10 64bit, nodejs 4.3.x and nodejs 5.6.x
Issue :
Trying to connect after starting with "npm start",  http-server die with follwing error.
_http_outgoing.js:351
      throw new TypeError('The header content contains invalid characters');
      ^

TypeError: The header content contains invalid characters
    at ServerResponse.OutgoingMessage.setHeader (_http_outgoing.js:351:13)
    at ResponseStream.(anonymous function) [as setHeader] (C:\SourceIgloo\0.Studying\AngularJS\angular-phonecat\node_modules\http-server\node_modules\union\lib\response-stream.js:86:34)
    at serve (C:\SourceIgloo\0.Studying\AngularJS\angular-phonecat\node_modules\http-server\node_modules\ecstatic\lib\ecstatic.js:146:11)
    at C:\SourceIgloo\0.Studying\AngularJS\angular-phonecat\node_modules\http-server\node_modules\ecstatic\lib\ecstatic.js:139:9
    at FSReqWrap.oncomplete (fs.js:82:15)

Solution :
need to upgrade http-server to 0.8.5
In package.json
"http-server": "^0.8.5"

It doesn't solve the problem in my environment...
(Windows 10 64bit, nodejs 4.3)

Solution : upgrade karma

Solution: upgrade karma

How to do this?

maybe...
npm install karma --save
(you should see package.json file and update karma related packages)

Solved: OS language wasn't english, so chars in header were not identified -> TypeError('The header content contains invalid characters')

@DanGld Change OS lang because framework's example does not work? No.
Try npm install http-server -D. More info in PR: #311

why "http-server": "^0.8.5" isn't work on my issue? Throw the same err:TypeError: The header content contains invalid characters
node v4
npm v2

@HBXSZ try the 0.9.0 version. check the PR: #311

not work

@igoradamenko yep! It works fine,thanks a lot!

@igoradamenko Thanks,It works fine!!!

Yes, 0.9.0 version works fine on my environment!

Changing version to 0.9.0 works well!

Yeah! I got the same problem and you solve my issue :+1:

@igoradamenko Thanks,that's the anwser.

works fine

authors: Aslan1992 DanGld HBXSZ Themercee igoradamenko inithink kimbeast martinlong77 namecgg ottercoder seeallsea

repo: angular/angular-phonecat


text:
StyleGuide - "Naming" Typo

maintainbility -> maintainability

Fixed.


text:
First run 404 issue fixed for QuickStart

There is 404 GET /app/main.js during initial npm start because of this file is not yet compiled. You have to hit Reload page to make the demo work. Quick and dirty workaround could be adding "prestart": "tsc". Dirty because it causes multiple file reloads then (but fixes the initial issue).

Open to another solution I you have one.

authors: wardbell webmaxru


text:
1.5.8 breaks  with jQ 3.1.1 w/ Migrate 3.0.0 due to using an undocumented API in jQuery.data

Angular 1.5.8 replaceWith uses copy the associated jQuery data of the DOM element into another by using
jqLite.data(newNode, jqLite.data(firstElementToRemove));

If jQuery is present on the page, then it will be used instead of the bundled jqLite. However a problem arises when jQuery 3.1.1 is used alongside jQuery Migrate 3.0.0. It turns out that the outer call working in the first place with previous versions of jQuery was just a fluke. According to the documentation, if 2 arguments are passed to jQuery.data, the second argument must be a string; and there is no support for passing in an object. This is unlike .data() which since 1.4.3 is documented to accept an object.
To reproduce
My ng-fu is not too good to make a minimal example, but it is reproduceable by this Plunker; I took the working example from ui-select and added jQuery 3.1.1 and jquery-migrate 3.0.0 (and reset the angular version to 1.5.8). Upon running, the following error log is produced for each select box rendered by ui-select (and the select boxes themselves wouldn't work):
Error: string.replace is not a function
.camelCase@https://code.jquery.com/jquery-3.1.1.js:355:10
jQuery.data@https://code.jquery.com/jquery-migrate-3.0.0.js:306:24
replaceWith@https://ajax.googleapis.com/ajax/libs/angularjs/1.5.8/angular.js:9908:9
compileTemplateUrl/<@https://ajax.googleapis.com/ajax/libs/angularjs/1.5.8/angular.js:9663:15
processQueue@https://ajax.googleapis.com/ajax/libs/angularjs/1.5.8/angular.js:16383:28
scheduleProcessQueue/<@https://ajax.googleapis.com/ajax/libs/angularjs/1.5.8/angular.js:16399:27
$RootScopeProvider/this.$get</Scope.prototype.$eval@https://ajax.googleapis.com/ajax/libs/angularjs/1.5.8/angular.js:17682:16
$RootScopeProvider/this.$get</Scope.prototype.$digest@https://ajax.googleapis.com/ajax/libs/angularjs/1.5.8/angular.js:17495:15
$RootScopeProvider/this.$get</Scope.prototype.$apply@https://ajax.googleapis.com/ajax/libs/angularjs/1.5.8/angular.js:17790:13
bootstrapApply@https://ajax.googleapis.com/ajax/libs/angularjs/1.5.8/angular.js:1761:9
invoke@https://ajax.googleapis.com/ajax/libs/angularjs/1.5.8/angular.js:4718:16
bootstrap/doBootstrap@https://ajax.googleapis.com/ajax/libs/angularjs/1.5.8/angular.js:1759:5
bootstrap@https://ajax.googleapis.com/ajax/libs/angularjs/1.5.8/angular.js:1779:12
angularInit@https://ajax.googleapis.com/ajax/libs/angularjs/1.5.8/angular.js:1664:5
@https://ajax.googleapis.com/ajax/libs/angularjs/1.5.8/angular.js:31763:5
resolve/</mightThrow@https://code.jquery.com/jquery-3.1.1.js:3570:21
resolve/</process<@https://code.jquery.com/jquery-3.1.1.js:3638:12
angular.js:13920:18

It would be preferable if the undocumented behaviour wasn't relied upon since more and more people will need to integrate some legacy Angular 1 with something that requires jQuery 3, and these kinds of errors are all too confusing. Another possibility would be to push this behaviour to be added into jQuery Migrate 3.0.0 but I am not too sure it would get accepted.

This seems to be related to https://github.com/jquery/jquery-migrate/issues/198.

So, @mgol, does it mean that if jquery/jquery-migrate#198 gets fixed, we don't need to change anything in Angular? Or do we need to fix something (e.g. in 1.6.x) to be compatible with jQuery 3.x?

Yes, we'll fix this in Migrate. While technically it's an undocumented feature, it might be that a lot of code actually depends on it so it makes sense to patch in Migrate regardless.
We'll think if we want to unprivatize this API in jQuery.
I'll close this issue since we won't be applying any changes to Angular.

@gkalpak Note that this issue only occurs if you use Angular with jQuery 3 + Migrate 3; it works fine with just jQuery 3 and we have tests to prove it. :)
We don't run tests with Migrate but the purpose of Migrate is to ease code migration and remove it afterwards, it shouldn't be running on production for too long.

https://github.com/jquery/jquery-migrate/issues/198 has been fixed; the next Migrate release will include it.

@ztane Could you make sure the development version of Migrate fixes your issue?

authors: gkalpak mgol ztane


text:
avoid publishing new releases to deprecated bower

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
N/A
What is the current behavior? (You can also link to an open issue here)
bower install angular

installs latest version of angularjs *

What is the new behavior (if this is a feature change)?
bower install angular
installs old version of angular
Does this PR introduce a breaking change?
yes, no new bower releases.
Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:

This will probably require some doc fixes for how people can transition to npm based angular, eg use /node_modules/ rather than /bower_components/

currently this PR stops all new releases to bower, however it might be better to release 1.7 and above only on npm.

TBH, I don't see the benefit in doing so. Although not recommended for use in new projects, bower is still maintained and there are people using it. Given the next-to-zero overhead for us, I don't see why we should make the lives of people still using bower more difficult than they already are 😈

@gkalpak perhaps to start this off, I could make a PR that updates the tutorial to use plain old npm

Well, that would be nice, but...the tutorial uses angular-seed as a starting point, so we need to update angular/angular-seed. And there are currently three PRs open for that (#385, #389, #390) :flushed:
We should get one of those in (probably #390) and then you could work on the tutorial :grin:

@gkalpak #390 is closed

Wrong link. Try again :)

Is there a cost to supporting bower?  It seems needlessly breaking to stop publishing to it even if it is deprecated, especially since it's probably an automated process that is doing so.

I agree that stopping publishing to bower is a needless BC. I also agree that we can point out the deprecation where possible, but let's not track this in this PR.

authors: Narretz dcherman gkalpak graingert


text:
bug(mat-icon): mat-icon names are searchable and highlited doing a ctrl + f browser search

Reproduction
Use StackBlitz to reproduce your issue:

Components: https://stackblitz.com/fork/components-issue
Harnesses: https://stackblitz.com/fork/harness-issue

Steps to reproduce:

Do a browser search (ctlr+f) inside a page with mat-icon and search by the name of the icon and it will be highlited

Expected Behavior
What behavior were you expecting to see?
Actual Behavior
What behavior did you actually see?
Is there a way to avoid this?
Environment

Angular: 9
CDK/Material: mat-icon
Browser(s): all
Operating System (e.g. Windows, macOS, Ubuntu):

Duplicate of https://github.com/angular/components/issues/23195.

authors: crisbeto ignaciostellino

repo: angular/components