Couldn't open browser (if you are using BrowserSync in a headless environment, you might want to set the open option to false)

When i run Gulp google cloud. I am getting below response please can you tell how to execute the in google cloud(Linux).
sudo gulp
[14:09:01] Using gulpfile ~/ATLAS/gulpfile.js
[14:09:01] Starting 'browser-sync'...
[14:09:01] Finished 'browser-sync' after 14 ms
[14:09:01] Starting 'watch'...
[14:09:01] Finished 'watch' after 14 ms
[14:09:01] Starting 'default'...
[14:09:01] Finished 'default' after 10 Î¼s
[BS] Access URLs:
   Local: http://localhost:3000/./production/index.html
External: http://:3000/./production/index.html

      UI: http://localhost:3001

UI External: http://:3001
[BS] Serving files from: ./
[BS] Couldn't open browser (if you are using BrowserSync in a headless environment, you might want to set the open option to false)

Hi there @ShanmugapriyaDurairaj ,
Unfortunately we didn't use it with BrowserSync , but this might help you :)

We will close this ticket for now but feel free to reopen it with further questions whenever you need to.

im also facing same issue..

[15:28:44] Using gulpfile ~\Downloads\bootstrapProject\gulpfile.js
[15:28:44] Starting 'js'...
[15:28:44] Starting 'sass'...
[15:28:44] Starting 'fa'...
[15:28:44] Starting 'fonts'...
[15:28:44] Finished 'fa' after 108 ms
[15:28:44] Finished 'js' after 150 ms
[15:28:44] Finished 'fonts' after 156 ms
[15:28:44] Finished 'sass' after 435 ms
[15:28:44] Starting 'serve'...
[15:28:44] Finished 'serve' after 30 ms
[15:28:44] Starting 'default'...
[15:28:44] Finished 'default' after 37 μs
[Browsersync] Access URLs:
   Local: http://localhost:3000
External: http://<IP_ADDRESS>:3000

      UI: http://localhost:3001

UI External: http://<IP_ADDRESS>:3001
[Browsersync] Serving files from: ./src
[Browsersync] Couldn't open browser (if you are using BrowserSync in a headless environment, you might want to set the open option to false)

plzzz tell me.. what should i do..

As I said before, we didn't use Gulp in this environment, however I think you could use this to solve your issue, basically it's the same issue. Good luck !

how to set environment ?

@AndreiCN
I am also having this issue using BrowserSync with Gulp in the Ubuntu Bash Terminal on Windows 10.
Adding "C:\Windows\System32" or "\c\Windows\System32" or "\mnt\c\Windows\System32" (or any of these variations with the slashes going the other direction, or with WINDOWS rather than Windows) did nothing to solve the issue.
I am still getting the error: "Couldn't open browser (if you are using BrowserSync in a headless environment, you might want to set the open option to false)"
I have also tried adding the browser option to the init function with no success.
Please give some more direction. I have looked all over Stack Overflow and through all of the various issue tickets on GitHub and nothing has solved this problem.

Question what is this issue ? :thinking:

If you're on Windows try with Git Bash as a terminal, will open your
BrowserSync for sure.
Regards,
Andrei.
On Feb 14, 2018 7:00 PM, "Chad Dugas"<EMAIL_ADDRESS>wrote:

@AndreiCN https://github.com/andreicn
I am also having this issue using BrowserSync with Gulp in the Ubuntu Bash
Terminal on Windows 10.
Adding "C:\Windows\System32" or "\c\Windows\System32" or
"\mnt\c\Windows\System32" (or any of these variations with the slashes
going the other direction, or with WINDOWS rather than Windows) did nothing
to solve the issue.
I am still getting the error: "Couldn't open browser (if you are using
BrowserSync in a headless environment, you might want to set the open
option to false)"
I have also tried adding the browser option to the init function with no
success.
Please give some more direction. I have looked all over Stack Overflow and
through all of the various issue tickets on GitHub and nothing has solved
this problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/puikinsh/gentelella/issues/489#issuecomment-365673773,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT1BhpK2asFEXNBr_ccylR45CLOXx0yQks5tUxE5gaJpZM4NorQC
.

for windows  -> change ["google chrome"] to ["chrome.exe"]
browserSync.init({
browser: ["chrome.exe"], //  ["google chrome"]
...

I also had the same problem.
Open your favourite browser and in the search bar explicitly write the local access URL just mentioned above the error you got in the command promt like localhost:3002. You might have got port number like 3000 or 3001 there. Press enter and Browsersync would be connected and index.html is executed.
I hope this works for you as well!

I also had the same problem.
Open your favourite browser and in the search bar explicitly write the local access URL just mentioned above the error you got in the command promt like localhost:3002. You might have got port number like 3000 or 3001 there. Press enter and Browsersync would be connected and index.html is executed.
I hope this works for you as well!

thank you so much

I also had the same problem.
Open your favourite browser and in the search bar explicitly write the local access URL just mentioned above the error you got in the command promt like localhost:3002. You might have got port number like 3000 or 3001 there. Press enter and Browsersync would be connected and index.html is executed.
I hope this works for you as well!

Thank you so much man.

I also had the same problem.
Open your favourite browser and in the search bar explicitly write the local access URL just mentioned above the error you got in the command promt like localhost:3002. You might have got port number like 3000 or 3001 there. Press enter and Browsersync would be connected and index.html is executed.
I hope this works for you as well!

THANK YOU SOOO MUCH

There was a similar problem, I solved it by entering a direct path to the browser exe file:
WSL
function syncInit() {
  browserSync({
    server: {
      baseDir: './',
      index: 'index.html'
    },
    notify: false,
    browser: "/mnt/c/Program Files/Google/Chrome/Application/chrome.exe",
})

Have no this problem on Windows, but the solution with entering the full path should help there too.


[Java] Update Unit Tests for Gandiva Module

Describe the enhancement requested
This is a sub-issue of the issue below.

#41680

The unit tests should use the org.junit.jupiter.api package. This issue deals with the gandiva module.
Component(s)
Java

take

Issue resolved by pull request 42166
https://github.com/apache/arrow/pull/42166


More Like This query is sending a null _index value to the server

I am attempting to do a "More Like This" query and in looking at the raw json query sent to the server, there is an attached _index field that is set to null which causes a "Can't get text on a VALUE_NULL" exception within elasticsearch.  There doesn't appear to be a way to either remove the _index value or set it.
c# code being used to query for matching results:
            var results = clientSearch.Search<DupeAtom>( req =>
                req.Index( Indices.Index( DuplicateIndex ) ).Query( q =>
                    q.MoreLikeThis( mlt =>
                        mlt.Like( l => l.Document( d => d.Id( atom.Id ) ) )
                        .Fields( f => f.Fields( "title", "text" ) )
                        .MinTermFrequency(1)
                        .MinDocumentFrequency(1)
                        .MaxDocumentFrequency(100)
                    )
                ).Fields( s => s.Fields( "id", "title" )).Size(10)
            );

Generated query to the server
{"size":10,"fields":["id","title"],"query":{"mlt":{"fields":["title","text"],"like":[{"_index":null,"_type":"dupeatom","_id":"kyXzqPXzZt"}],"min_term_freq":1,"min_doc_freq":1,"max_doc_freq":100}}}]
If I manually remove the "_index" property in the like object, the query is correct.
Thanks.

Hi @ahazelwood what version of NEST are you using?

@ahazelwood any update on this?

Closing this because I can not reproduce this using the latest NEST.
@ahazelwood if you still see this issue please reopen and let us know!


"Room server join error" in apprtc calls

Browsers and versions affected
Chrome : 63.0.3239.26 / 10032.21.0 dev
OS: Chrome and Linux
Steps to reproduce
Start an apprtc loopback call on any chrome device or Linux machine and click on "Join"
Expected results
Apprtc call should connect successfully
Actual results
Apprtc call fails with "Room server join error: Registration error: ERROR
WebSocket register error: Registration error: ERROR"

JS logs :
0.507: Initializing; server= undefined.
apprtc.debug.js:5657 0.507: Initializing; room=undefined.
apprtc.debug.js:5657 2.023: Opening signaling channel.
apprtc.debug.js:5657 2.026: Setting up loopback WebSocket.
apprtc.debug.js:5657 2.110: Room server join error: Registration error: ERROR
apprtc.debug.js:5657 2.111: WebSocket register error: Registration error: ERROR
apprtc.debug.js:5657 2.174: Retrieved ICE server information.
apprtc.debug.js:5657 2.181: Signaling channel opened.
apprtc.debug.js:5657 2.309: Loopback WebSocket opened.
apprtc.debug.js:5657 2.406: Got access to local media with mediaConstraints:
'{"audio":true,"video":{"optional":[{"minWidth":"1280"},{"minHeight":"720"}],"mandatory":{}}}'
apprtc.debug.js:5657 2.408: User has granted access to local media.
apprtc.debug.js:5657 2.410: Attaching local stream.

Apprtc calls are working fine now. Server error appears to be transient.


Result of spark job

Hi @ywilkof, Once the job is submitted. How can get the result of the job, i am not talking about the status; i know how to get that. Does your api return something like this? i am interested in the result object.
{
"duration": "6.341 secs",
"classPath": "spark.jobserver.WordCountExample",
"startTime": "2015-10-16T03:17:03.127Z",
"context": "b7ea0eb5-spark.jobserver.WordCountExample",
"result": {
"a": 2,
"b": 2,
"c": 1,
"see": 1
},
"status": "FINISHED",
"jobId": "5453779a-f004-45fc-a11d-a39dae0f9bf4"
}⏎

Hi @aminaaslam ,
This scenario is not covered as part of this project, as this requires a process to wait for the result, and this is aclient which only sends single HTTP requests with no sessions or contexts. This is however covered in the scope of the Job Server, by sending requests with the sync=true flag. You will have to set up the server and change your job to implement their traits.


fix: card refactor to multiple exports

contributes to #948
takes Card and puts existing code into two additional exports- CardHeader and CardFooter. the body component wasn't really worth it as it's just a pretty straight forward <div>{children}</div> implementation. most of the logic remains in Card and is passed down to the other components. aside from that updates were made to the class names to be more in line with current standards.

@matthewgallo changes made 👍


Feature request: Automatically change the color when joining a live-collaboration session

Following #1868, it would be nice to auto-change the default color to the color of avatar, e.g. if I enter a live-collaboration session and I'm assign a red avatar, my default color would be red and all I'd type would be red instead of black. It wouldn't prevent me from changing the color.
I'm not sure this is a behavior we would always want. It could be a toggle when creating a session. My use case is team retrospectives, where we write and draw stuff one by one.

I really like this idea! It’s easy to undo and would make it easy to collaborate :)

On Jul 3, 2020, at 9:37 AM, Warren Seine<EMAIL_ADDRESS>wrote:

Following #1868, it would be nice to auto-change the default color to the color of avatar, e.g. if I enter a live-collaboration session and I'm assign a red avatar, my default color would be red and all I'd type would be red instead of black. It wouldn't prevent me from changing the color.
I'm not sure this is a behavior we would always want. It could be a toggle when creating a room.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


kruskal screening p-values and fdr

I was wondering why isn't there a correction for multiple testing after the kruskal selection step at all?
thanks

Hello
Yes - I have a similar question/ concern - especially if I am using multiple marker genes
Thanks
Laura


New Adapter: Alkimi

@And1sS fixed.

@pro-nsk You have problems with github action(checkstyle failed)
To be sured, that your code changes will pass our github actions
before push, pls run mvn clean package -f extra

@SerhiiNahornyi Thanks, fixed.

@pro-nsk Pls consider to fix CI failure
Error:  Failures:
Error:    AlkimiTest.openrtb2AuctionShouldRespondWithBidsFromAlkimi:34->IntegrationTest.assertJsonEquals:250 ext

@SerhiiNahornyi fixed


Command+Click on line in OUTPUT console should go to line in already open file

From @tylerb on July 10, 2017 18:34
Repro:

Use two code views
Left view open an unrelated file
Right view open a test file with a failing test
Run test to generate output in the OUTPUT pane
Click on the left view to select it
command+click the failing line in OUTPUT

Expected result: the right view jumps to the line that was just command+clicked
Actual result: the file is opened, again, in the left view and then jumps to the line
I'd really like it if this process would first search to see if any view has the file open already.
Thanks!
Copied from original issue: Microsoft/vscode-go#1080

The Go extension only prints out the links to the output pane.
The links are implemented by core VS Code

Dup of https://github.com/Microsoft/vscode/issues/23917
https://github.com/Microsoft/vscode/issues/24027


Lunch code no longer seems to work

There aren't any school lunches for us to crawl, given that classes have been online since September.

There aren't any school lunches for us to crawl, given that classes have been online since September.

Sure, but even if crawled, the code to serve them in the schedule is disabled.

Sure, but even if crawled, the code to serve them in the schedule is disabled.

It's possible that the lunch code (which was added in September) didn't
make it to the new AWS hosted four11, I'll look into it.
On Sat, Jan 2, 2021 at 10:53 PM Justin Uberti<EMAIL_ADDRESS>wrote:

Sure, but even if crawled, the code to serve them in the schedule is
disabled.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/guberti/epschedule/issues/391#issuecomment-753577024,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABUPM5CEFSXUNULP6V24LTSYAH6RANCNFSM4VROQRXQ
.

It's possible that the lunch code (which was added in September) didn't
make it to the new AWS hosted four11, I'll look into it.
On Sat, Jan 2, 2021 at 10:53 PM Justin Uberti<EMAIL_ADDRESS>wrote:

Sure, but even if crawled, the code to serve them in the schedule is
disabled.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/guberti/epschedule/issues/391#issuecomment-753577024,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABUPM5CEFSXUNULP6V24LTSYAH6RANCNFSM4VROQRXQ
.

Lunches are back up at EPS, so this is now an actual problem again. @kuberti is going to look into it.

Added lunch id back into the json response to
four11.eastsideprep.org/epsnet/courses. should be under individual>lunch_id
also added cohort to the schedule response, it will be "" until defined. We
currently only have cohorts listed through April 9th
On Sun, Mar 21, 2021 at 11:31 PM Justin Uberti @.***>
wrote:

Lunches are back up at EPS, so this is now an actual problem again.
@kuberti https://github.com/kuberti is going to look into it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/guberti/epschedule/issues/391#issuecomment-803799347,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABUPMZKGZQKZCUHD5HKC4TTE3P2PANCNFSM4VROQRXQ
.

ICS feed at webcal://www.eastsideprep.org/wp-content/plugins/dpProEventCalendar/includes/ical.php?calendar_id=19
(https://www.eastsideprep.org/wp-content/plugins/dpProEventCalendar/includes/ical.php?calendar_id=19) will download the file
https://teams.microsoft.com/l/message/19:Ioin1xdJGXhgspCLMSb2XPdTOkYKNX5LVvLggWsNj2g1@thread.tacv2/1647543474598?tenantId=b2681e8b-dd20-46cf-b163-371a2d7c6014&groupId=25b01c99-67aa-4749-a21e-63aff498675b&parentMessageId=1647542764592&teamName=EPSchedule&channelName=General&createdTime=1647543474598

Lunches have been restored by #498


Speed up build of web page

Now that we are rendering an mdbook during the build of www.acton-lang.org, we have to first install mdbook. We also make use of svgbob, so we need to install mdbook-svgbob. This is currently done using cargo and that takes a long time, like 7 minutes or so!?
Before we used svgbob, we used a github action to bring in mdbook and that was much faster. It didn't support installing mdbook-svgbob, forcing the current solution... but it is so much slower. What can we do to speed it up? Also, without creating a ton of new stuff to maintain.

Actually, not sure how big of a problem this is. With a local build of zola etc, we can iterate fast locally and then submit when ready. It's okay that it takes 10 minutes to build. Not worthy spending time to fix this.


Request to provide new function type

Hi in this PR I want to request and discuss a design change of function type in RetDec config.
Before this PR function type might have been one of the following:

USER_DEFINED
STATICALLY_LINKED
DYNAMICALLY_LINKED
SYSCALL
IDIOM

The default function type that was generated for every function was
USER_DEFINED. This in my opinion is not right as we have to distinguish functions that
were provided by user through some kind of front-end and functions that
were automatically detected by decompiler. This is why I propose new type

DECOMPILER_DEFINED.

A reason to distinguish these two function types is for example in parameter
analysis. When user specifies that the return type is integer, the decompiler
should not continue to do heuristics to detect return type. If an user
wants a function to be of some type they should get the function with the type
on output. Also this brings more flexibility when it comes to creation of custom plugins
that provide data to RetDec (like r2plugin).
I traced every implementation/usage of previous default type (USER_DEFINED) and changed it accordingly.

Meanwhile, lets Run TeamCity builds and see if everything is ok.

Well, I will look into the problem why tests in debug build did not pass and push fix. However the doxygen build is failing becuase of the new integrated libraries (yaracpp, pelib). I can fix those too, but I think we should discuss if we will not disable building documentation for those (for example by moving these libraries back into deps/ directory).

Lets Run TeamCity builds after doxygen build and tests on debug build on master are passing.


Cookie tracking in responses

Partially addresses #767.
This PR adds the ability to observe cookies in transit within a Response object.
This option is opt-in based on the tracking_cookie_store function added to ClientBuilder due to the minor performance hit of creating clones of cookie store state. It is dependent on the cookies feature and having enabled a cookie store on the Client.

Thanks for the PR!
So, let me see if I understand correctly. This would allow enabling "tracking", and Response::session_cookies() would contain all the current session cookies that would be sent to the URL of the Response?

@seanmonstar Yes, except Response::session_cookies() returns all cookies, not localized to the specific URL of the response. It would be up to user usage to filter by domain/path/HTTP/S if they wanted to. It might make sense to have the intuitive filter also available through another function, but I didn't personally need it at time of implementation.

Oh, in that case, should it just be a method on Client?

@seanmonstar Due to the possibility of racing responses creating inconsistent cookies with checking them after a request on Client, I decided to put it on the Response. I'm working under the assumption of HTTP/2/3 primarily, but I imagine there may be also be a race condition in the async polling for several pipelined responses in HTTP/1.1. Let me know what you think.

Sure, that could happen. Being on Response, a user needs to remember the order they received them in, since the first ones won't have cookies from newer responses.
Looking at Golang, the cookie jar is accessible from the Client, that seems like the right place here too.

Has any progress been made on this? This feature would be useful to me.
Is there any reason not to support getting cookies from both the Client and the Response?

@dmarcuse The owner, @seanmonstar, disagrees with the premise of this PR, other than that, this is complete.


Speciation/Organization

Simple, self-use only: folders
Advanced, possibly public: Use a visual AI model fine-tuned on fish to extract low-dimensional feature vectors which are then clustered using insert clustering algorithm here to "create" species for display in the UI.


using v2 url for search api: error w/ py3.

.gnip config contains:
url = https://gnip-api.twitter.com/search/fullarchive/accounts/shendrickson/dev.json
./gnip_search.py -f"from:BrianLehman" json
Exiting with HTTP error code 422
ERROR Message: There were errors processing your request: Unknown parameter:'publisher'
Note: this is only happening when using python 3.

This looks like a difference in behavior between:
yours: https://gnip-api.twitter.com/search/fullarchive/accounts/
shendrickson/dev.json
https://gnip-api.twitter.com/search/fullarchive/accounts/shendrickson/dev.json
works fine: https://data-api.twitter.com/search/fullarchive/accounts/
shendrickson/dev.json
https://gnip-api.twitter.com/search/fullarchive/accounts/shendrickson/dev.json
I will have to look into the different specifications. (I am guessing it
has to do with backward compatibility to 30day search)
On Tue, Sep 20, 2016 at 11:58 AM, Brian Lehman<EMAIL_ADDRESS>wrote:

.gnip config contains:
url = https://gnip-api.twitter.com/search/fullarchive/accounts/
shendrickson/dev.json
./gnip_search.py -f"from:BrianLehman" json
Exiting with HTTP error code 422
ERROR Message: There were errors processing your request: Unknown
parameter:'publisher'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DrSkippy/Gnip-Python-Search-API-Utilities/issues/30,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHRjgXmIxwFDpf18gU7OJRbXyfeVY8nks5qsB7HgaJpZM4KB7hr
.

--
@drskippy
303.219.0022

The code was setting search_v2=True for the old v1 url. Josh helped me find it and I made a pull request.


Q: does offline mode provide same report files of connection mode?

Hi,
Environment information:
Sfgrantreport version -  2<IP_ADDRESS>
OS -  Windows 10
Question:
Does offline mode provide same report files of connection mode?
Findings:

fewer subfolder on the DATA folder. Just DATA/ROLE subfolder, no others (ACCT,CONN,GRANT,ROLE,USER)
fewer subfolder on the RPT folder, no RPT/USER subfolder
fewer .xlsx file on the output-folder, no TAG file.
No data contents on the ALL report file, most of USER related tabs.

Does this caused by the difference between two modes or issue?
If more queries and result csv files required to match with connection mode, please list up all required queries.
Appreciate your help in advance.

Hi there, sorry I didn't notice this earlier. The offline report should provide nearly identical output as the online report. There are a couple of differences I've observed around ACCOUNT objects privileges but they should be tiny.
The TAG file might have to do with the new object type for object level tagging. I've not tested that myself yet, but really both online and offline reports ought to automagically support the TAG since it's just another object type?
Can you give me a file differences report of what you are seeing


[Material3] DropdownMenu themed focused item broken

DropdownMenu themed focused item broken
The style indication of the found and focused/selected item in a DropdownMenu does not use MenuButtonThemeData. Its simulation of the focused state omits the theme.
This makes it impossible to provide a consistent style for the focused/selected item when using a custom theme in a DropdownMenu. One have to live with the default style for the entire menu, or accept a deviant and out of style looking focused/selected item.
Expected results
Expect to be able to theme the found selected item in a DropdownMenu to a style where the selected item would match the style of used custom theme, and do so on all hover/focus/pressed themed MaterialState dependent colors.
Consider these on purpose wild looking MenuThemeData and MenuButtonThemeData, used to visually highlight the functional gaps.

Theme snippet
(For full code sample, see the Issue sample code further below).
  MenuThemeData(
    style: MenuStyle(
      backgroundColor: MaterialStatePropertyAll<Color?>(colorScheme.errorContainer),
      padding: const MaterialStatePropertyAll<EdgeInsetsGeometry?>(EdgeInsets.all(8)),
    ),
  ),
  MenuButtonThemeData(
    style: ButtonStyle(
      backgroundColor: MaterialStateProperty.resolveWith(
          (Set<MaterialState> states) {
        if (states.contains(MaterialState.pressed)) {
          return colorScheme.primary;
        }
        if (states.contains(MaterialState.hovered)) {
          return colorScheme.primary;
        }
        if (states.contains(MaterialState.focused)) {
          return colorScheme.primaryContainer;
        }
        return Colors.transparent;
      }),
      foregroundColor: MaterialStateProperty.resolveWith(
          (Set<MaterialState> states) {
        if (states.contains(MaterialState.disabled)) {
          return colorScheme.onSurface.withOpacity(0.38);
        }
        if (states.contains(MaterialState.pressed)) {
          return colorScheme.onPrimary;
        }
        if (states.contains(MaterialState.hovered)) {
          return colorScheme.onPrimary;
        }
        if (states.contains(MaterialState.focused)) {
          return colorScheme.onPrimaryContainer;
        }
        return colorScheme.onSurface;
      }),
      iconColor: MaterialStateProperty.resolveWith(
          (Set<MaterialState> states) {
        if (states.contains(MaterialState.disabled)) {
          return colorScheme.onSurface.withOpacity(0.38);
        }
        if (states.contains(MaterialState.pressed)) {
          return colorScheme.onPrimary;
        }
        if (states.contains(MaterialState.hovered)) {
          return colorScheme.onPrimary;
        }
        if (states.contains(MaterialState.focused)) {
          return colorScheme.onPrimaryContainer;
        }
        return colorScheme.onSurfaceVariant;
      }),
      overlayColor: MaterialStateProperty.resolveWith(
          (Set<MaterialState> states) {
        if (states.contains(MaterialState.pressed)) {
          return colorScheme.onPrimary.withOpacity(0.12);
        }
        if (states.contains(MaterialState.hovered)) {
          return colorScheme.onPrimary.withOpacity(0.08);
        }
        if (states.contains(MaterialState.focused)) {
          return colorScheme.onPrimaryContainer.withOpacity(0.12);
        }
        return Colors.transparent;
      }),
      shape: ButtonStyleButton.allOrNull<OutlinedBorder>(
        const RoundedRectangleBorder(
          borderRadius: BorderRadius.all(
            Radius.circular(10),
          ),
        ),
      ),
    ),
  ),

Expect the theme to use above defined MenuButtonThemeData ButtonStyle theming and look and behave as shown below:

https://user-images.githubusercontent.com/39990307/228695784-c44ba365-0174-44a7-8d67-d07a727aef44.mov
Actual results
Get a style where the focused (and selected) item has a style that does not used the themed style, it effectively ignores the theme defined by the MenuButtonThemeData theme, concerning its focused states for all theme colors.

https://user-images.githubusercontent.com/39990307/228695848-fa1c1675-ff88-483d-9c05-c3b15666ae14.mov
Discussion
EDIT: The accessibility topic found during creation of this issues and included in this discussion topic previously, have on request been moved to its own issues, see https://github.com/flutter/flutter/issues/123797.
Fix used to demo expected result
An experimental revised and fixed version of _buildButtons(..) function from file dropdown_menu.dart, used to generate the expected result above is included below for reference.
It may be useful as a starting point for an actual fix. It only patches the current implementation concerning it ignoring the theme. It does not address the discussion part above.
This fix also has the same "hack" feel as the original implementation. It uses knowledge about what the M3 token defaults are for a default focused dropdown menu item, as its fallback defaults for the simulated none widget/themed defaults. It does so, since it cannot access the _MenuButtonDefaultsM3 private class in menu_anchor.dart. This is not the first time I have run into a situation where it would be useful to have access to the theme default classes, outside their component class files.
I checked the quick fix below with existing tests in dropdown_menu_theme_test.dart and dropdown_test.dart. It did not break any existing test in them. Existing tests do not capture this issue because they do not even include any customization of DropdownMenu via MenuButtonThemeData. The tests rely on that being covered by MenuItemButton related tests. Since DropdownMenu overrides MenuItemButton default behavior, it needs its own tests of those parts to ensure those overrides do not break expected theming features of used MenuItemButton.
List<Widget> _buildButtons(
  List<DropdownMenuEntry<T>> filteredEntries,
  TextEditingController textEditingController,
  TextDirection textDirection,
  { int? focusedIndex }
) {
  final List<Widget> result = <Widget>[];
  final double padding = leadingPadding ?? _kDefaultHorizontalPadding;
  final EdgeInsetsGeometry effectivePadding;
  switch (textDirection) {
    case TextDirection.rtl:
      effectivePadding = EdgeInsets.only(left: _kDefaultHorizontalPadding, right: padding);
    case TextDirection.ltr:
      effectivePadding = EdgeInsets.only(left: padding, right: _kDefaultHorizontalPadding);
  }
  final ThemeData theme = Theme.of(context);
  final ButtonStyle defaultStyle = theme.menuButtonTheme.style?.copyWith(padding: MaterialStatePropertyAll<EdgeInsetsGeometry>(effectivePadding)) ?? MenuItemButton.styleFrom(padding: effectivePadding);

  for (int i = 0; i < filteredEntries.length; i++) {
    final DropdownMenuEntry<T> entry = filteredEntries[i];
    ButtonStyle effectiveStyle = entry.style ?? defaultStyle;
    final Color focusedBackgroundColor = effectiveStyle.backgroundColor?.resolve(<MaterialState>{MaterialState.focused}) ?? theme.colorScheme.onSurface.withOpacity(0.12);
    final Color focusedForegroundColor = effectiveStyle.foregroundColor?.resolve(<MaterialState>{MaterialState.focused}) ?? theme.colorScheme.onSurface;
    final Color focusedIconColor = effectiveStyle.iconColor?.resolve(<MaterialState>{MaterialState.focused}) ?? theme.colorScheme.onSurfaceVariant;
    final Color focusedOverlayColor = effectiveStyle.overlayColor?.resolve(<MaterialState>{MaterialState.focused}) ?? theme.colorScheme.onSurface.withOpacity(0.12);

    // Simulate the focused state because the text field should always be focused
    // during traversal. Include potential MenuItemButton theme in the focus
    // simulation for all colors in the theme.
    effectiveStyle = entry.enabled && i == focusedIndex
      ? effectiveStyle.copyWith(
          backgroundColor: MaterialStatePropertyAll<Color>(focusedBackgroundColor),
          foregroundColor: MaterialStatePropertyAll<Color>(focusedForegroundColor),
          iconColor: MaterialStatePropertyAll<Color>(focusedIconColor),
          overlayColor: MaterialStatePropertyAll<Color>(focusedOverlayColor),
       )
     : effectiveStyle;

    final MenuItemButton menuItemButton = MenuItemButton(
      style: effectiveStyle,
      leadingIcon: entry.leadingIcon,
      trailingIcon: entry.trailingIcon,
      onPressed: entry.enabled
        ? () {
            textEditingController.text = entry.label;
            textEditingController.selection = TextSelection.collapsed(offset: textEditingController.text.length);
            currentHighlight = widget.enableSearch ? i : null;
            widget.onSelected?.call(entry.value);
          }
        : null,
      requestFocusOnHover: false,
      child: Text(entry.label),
    );
    result.add(menuItemButton);
  }

  return result;
}

Issue sample code

Code sample
// MIT License
//
// Copyright (c) 2023 Mike Rydstrom
//
// Permission is hereby granted, free of charge, to any person obtaining a copy
// of this software and associated documentation files (the "Software"), to deal
// in the Software without restriction, including without limitation the rights
// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
// copies of the Software, and to permit persons to whom the Software is
// furnished to do so, subject to the following conditions:
//
// The above copyright notice and this permission notice shall be included in all
// copies or substantial portions of the Software.
 IN NO EVENT SHALL THE
// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
// OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
// SOFTWARE.
import 'package:flutter/foundation.dart';
import 'package:flutter/material.dart';

// A seed color for the M3 ColorScheme.
const Color seedColor = Color(0xFF6750A4);
// Make M3 ColorSchemes from a seed color.
final ColorScheme schemeLight = ColorScheme.fromSeed(
  brightness: Brightness.light,
  seedColor: seedColor,
);
final ColorScheme schemeDark = ColorScheme.fromSeed(
  brightness: Brightness.dark,
  seedColor: seedColor,
);

// Example theme
ThemeData theme(ThemeMode mode, ThemeSettings settings) {
  final ColorScheme colorScheme =
      mode == ThemeMode.light ? schemeLight : schemeDark;
  return ThemeData(
    colorScheme: colorScheme,
    useMaterial3: settings.useMaterial3,
    visualDensity: VisualDensity.standard,
    menuTheme: settings.useCustomMenu
        ? MenuThemeData(
            style: MenuStyle(
              backgroundColor:
                  MaterialStatePropertyAll<Color?>(colorScheme.errorContainer),
              padding: const MaterialStatePropertyAll<EdgeInsetsGeometry?>(
                EdgeInsets.all(8),
              ),
            ),
          )
        : null,
    menuButtonTheme: settings.useCustomMenu
        ? MenuButtonThemeData(
            style: ButtonStyle(
              backgroundColor: MaterialStateProperty.resolveWith(
                  (Set<MaterialState> states) {
                if (states.contains(MaterialState.pressed)) {
                  return colorScheme.primary;
                }
                if (states.contains(MaterialState.hovered)) {
                  return colorScheme.primary;
                }
                if (states.contains(MaterialState.focused)) {
                  return colorScheme.primaryContainer;
                }
                return Colors.transparent;
              }),
              foregroundColor: MaterialStateProperty.resolveWith(
                  (Set<MaterialState> states) {
                if (states.contains(MaterialState.disabled)) {
                  return colorScheme.onSurface.withOpacity(0.38);
                }
                if (states.contains(MaterialState.pressed)) {
                  return colorScheme.onPrimary;
                }
                if (states.contains(MaterialState.hovered)) {
                  return colorScheme.onPrimary;
                }
                if (states.contains(MaterialState.focused)) {
                  return colorScheme.onPrimaryContainer;
                }
                return colorScheme.onSurface;
              }),
              iconColor: MaterialStateProperty.resolveWith(
                  (Set<MaterialState> states) {
                if (states.contains(MaterialState.disabled)) {
                  return colorScheme.onSurface.withOpacity(0.38);
                }
                if (states.contains(MaterialState.pressed)) {
                  return colorScheme.onPrimary;
                }
                if (states.contains(MaterialState.hovered)) {
                  return colorScheme.onPrimary;
                }
                if (states.contains(MaterialState.focused)) {
                  return colorScheme.onPrimaryContainer;
                }
                return colorScheme.onSurfaceVariant;
              }),
              overlayColor: MaterialStateProperty.resolveWith(
                  (Set<MaterialState> states) {
                if (states.contains(MaterialState.pressed)) {
                  return colorScheme.onPrimary.withOpacity(0.12);
                }
                if (states.contains(MaterialState.hovered)) {
                  return colorScheme.onPrimary.withOpacity(0.08);
                }
                if (states.contains(MaterialState.focused)) {
                  return colorScheme.onPrimaryContainer.withOpacity(0.12);
                }
                return Colors.transparent;
              }),
              shape: ButtonStyleButton.allOrNull<OutlinedBorder>(
                const RoundedRectangleBorder(
                  borderRadius: BorderRadius.all(
                    Radius.circular(10),
                  ),
                ),
              ),
            ),
          )
        : null,
  );
}

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

class IssueDemoApp extends StatefulWidget {
  const IssueDemoApp({super.key});

  @override
  State<IssueDemoApp> createState() => _IssueDemoAppState();
}

class _IssueDemoAppState extends State<IssueDemoApp> {
  ThemeMode themeMode = ThemeMode.light;
  bool longLabel = false;
  TextDirection textDirection = TextDirection.ltr;
  ThemeSettings settings = const ThemeSettings(
    useMaterial3: true,
    useCustomMenu: true,
  );

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      themeMode: themeMode,
      theme: theme(ThemeMode.light, settings),
      darkTheme: theme(ThemeMode.dark, settings),
      home: Directionality(
        textDirection: textDirection,
        child: Scaffold(
          appBar: AppBar(
            title: const Text('DropdownMenu Issue'),
            actions: [
              IconButton(
                icon: settings.useMaterial3
                    ? const Icon(Icons.filter_3)
                    : const Icon(Icons.filter_2),
                onPressed: () {
                  setState(() {
                    settings =
                        settings.copyWith(useMaterial3: !settings.useMaterial3);
                  });
                },
                tooltip: "Switch to Material ${settings.useMaterial3 ? 2 : 3}",
              ),
              IconButton(
                icon: themeMode == ThemeMode.dark
                    ? const Icon(Icons.wb_sunny_outlined)
                    : const Icon(Icons.wb_sunny),
                onPressed: () {
                  setState(() {
                    if (themeMode == ThemeMode.light) {
                      themeMode = ThemeMode.dark;
                    } else {
                      themeMode = ThemeMode.light;
                    }
                  });
                },
                tooltip: "Toggle brightness",
              ),
            ],
          ),
          body: HomePage(
            settings: settings,
            onSettings: (ThemeSettings value) {
              setState(() {
                settings = value;
              });
            },
            longLabel: longLabel,
            onLongLabel: (bool value) {
              setState(() {
                longLabel = value;
              });
            },
            textDirection: textDirection,
            onTextDirection: (TextDirection value) {
              setState(() {
                textDirection = value;
              });
            },
          ),
        ),
      ),
    );
  }
}

class HomePage extends StatelessWidget {
  const HomePage({
    super.key,
    required this.settings,
    required this.onSettings,
    required this.longLabel,
    required this.onLongLabel,
    required this.textDirection,
    required this.onTextDirection,
  });
  final ThemeSettings settings;
  final ValueChanged<ThemeSettings> onSettings;
  final bool longLabel;
  final ValueChanged<bool> onLongLabel;
  final TextDirection textDirection;
  final ValueChanged<TextDirection> onTextDirection;

  @override
  Widget build(BuildContext context) {
    return ListView(
      padding: const EdgeInsets.symmetric(horizontal: 16),
      children: [
        SwitchListTile(
          title: const Text('Text directionality'),
          subtitle: const Text('OFF=LTR  ON=RTL'),
          value: textDirection == TextDirection.rtl,
          onChanged: (bool value) {
            value
                ? onTextDirection(TextDirection.rtl)
                : onTextDirection(TextDirection.ltr);
          },
        ),
        const SizedBox(height: 8),
        const Text('DropdownMenu focused item style broken\n\n'
            'The style indication of the found and selected item in a '
            'DropdownMenu does not use MenuButtonThemeData. Its simulation of '
            'the focused state omits the theme.'),
        SwitchListTile(
          title: const Text('Enable custom menu theme'),
          value: settings.useCustomMenu,
          onChanged: (bool value) {
            onSettings(settings.copyWith(useCustomMenu: value));
          },
        ),
        const Padding(
          padding: EdgeInsets.all(12.0),
          child: DropDownMenuShowcase(),
        ),
        const SizedBox(height: 16),
        const ShowColorSchemeColors(),
      ],
    );
  }
}

class DropDownMenuShowcase extends StatefulWidget {
  const DropDownMenuShowcase({super.key});

  @override
  State<DropDownMenuShowcase> createState() => _DropDownMenuShowcaseState();
}

class _DropDownMenuShowcaseState extends State<DropDownMenuShowcase> {
  String selectedItem = '';
  @override
  Widget build(BuildContext context) {
    return Column(
      crossAxisAlignment: CrossAxisAlignment.start,
      children: <Widget>[
        DropdownMenu<String>(
          initialSelection: selectedItem,
          onSelected: (String? value) {
            setState(() {
              selectedItem = value ?? 'one';
            });
          },
          dropdownMenuEntries: const <DropdownMenuEntry<String>>[
            DropdownMenuEntry<String>(
              label: 'Alarm settings',
              leadingIcon: Icon(Icons.alarm),
              value: 'one',
            ),
            DropdownMenuEntry<String>(
              label: 'Cabin overview',
              leadingIcon: Icon(Icons.cabin),
              value: 'three',
            ),
            DropdownMenuEntry<String>(
              label: 'Surveillance view',
              leadingIcon: Icon(Icons.camera_outdoor_rounded),
              value: 'four',
            ),
            DropdownMenuEntry<String>(
              label: 'Water alert',
              leadingIcon: Icon(Icons.water_damage),
              value: 'five',
            ),
            DropdownMenuEntry<String>(
              label: 'Disabled settings',
              leadingIcon: Icon(Icons.settings),
              value: 'two',
              enabled: false,
            ),
          ],
        ),
      ],
    );
  }
}

/// A Theme Settings class to bundle properties we want to modify on our
/// theme interactively.
@immutable
class ThemeSettings with Diagnosticable {
  final bool useMaterial3;
  final bool useCustomMenu;

  const ThemeSettings({
    required this.useMaterial3,
    required this.useCustomMenu,
  });

  /// Flutter debug properties override, includes toString.
  @override
  void debugFillProperties(DiagnosticPropertiesBuilder properties) {
    super.debugFillProperties(properties);
    properties.add(DiagnosticsProperty<bool>('useMaterial3', useMaterial3));
    properties.add(DiagnosticsProperty<bool>('useCustomMenu', useCustomMenu));
  }

  /// Copy the object with one or more provided properties changed.
  ThemeSettings copyWith({
    bool? useMaterial3,
    bool? useCustomMenu,
  }) {
    return ThemeSettings(
      useMaterial3: useMaterial3 ?? this.useMaterial3,
      useCustomMenu: useCustomMenu ?? this.useCustomMenu,
    );
  }

  /// Override the equality operator.
  @override
  bool operator ==(Object other) {
    if (identical(this, other)) return true;
    if (other.runtimeType != runtimeType) return false;
    return other is ThemeSettings &&
        other.useMaterial3 == useMaterial3 &&
        other.useCustomMenu == useCustomMenu;
  }

  /// Override for hashcode, dart.ui Jenkins based.
  @override
  int get hashCode => Object.hashAll(<Object?>[
        useMaterial3.hashCode,
        useCustomMenu.hashCode,
      ]);
}

/// Draw a number of boxes showing the colors of key theme color properties
/// in the ColorScheme of the inherited ThemeData and its color properties.
class ShowColorSchemeColors extends StatelessWidget {
  const ShowColorSchemeColors({super.key, this.onBackgroundColor});

  /// The color of the background the color widget are being drawn on.
  ///
  /// Some of the theme colors may have semi transparent fill color. To compute
  /// a legible text color for the sum when it shown on a background color, we
  /// need to alpha merge it with background and we need the exact background
  /// color it is drawn on for that. If not passed in from parent, it is
  /// assumed to be drawn on card color, which usually is close enough.
  final Color? onBackgroundColor;

  // Return true if the color is light, meaning it needs dark text for contrast.
  static bool _isLight(final Color color) =>
      ThemeData.estimateBrightnessForColor(color) == Brightness.light;

  // On color used when a theme color property does not have a theme onColor.
  static Color _onColor(final Color color, final Color bg) =>
      _isLight(Color.alphaBlend(color, bg)) ? Colors.black : Colors.white;

  @override
  Widget build(BuildContext context) {
    final ThemeData theme = Theme.of(context);
    final ColorScheme colorScheme = theme.colorScheme;
    final bool useMaterial3 = theme.useMaterial3;
    const double spacing = 4;

    // Grab the card border from the theme card shape
    ShapeBorder? border = theme.cardTheme.shape;
    // If we had one, copy in a border side to it.
    if (border is RoundedRectangleBorder) {
      border = border.copyWith(
        side: BorderSide(
          color: colorScheme.outlineVariant,
          width: 1,
        ),
      );
      // If
    } else {
      // If border was null, make one matching Card default, but with border
      // side, if it was not null, we leave it as it was.
      border ??= RoundedRectangleBorder(
        borderRadius: BorderRadius.all(Radius.circular(useMaterial3 ? 12 : 4)),
        side: BorderSide(
          color: colorScheme.outlineVariant,
          width: 1,
        ),
      );
    }

    // Get effective background color.
    final Color background =
        onBackgroundColor ?? theme.cardTheme.color ?? theme.cardColor;

    // Wrap this widget branch in a custom theme where card has a border outline
    // if it did not have one, but retains its ambient themed border radius.
    return Theme(
      data: Theme.of(context).copyWith(
        cardTheme: CardTheme.of(context).copyWith(
          elevation: 0,
          surfaceTintColor: Colors.transparent,
          shape: border,
        ),
      ),
      child: Column(
        crossAxisAlignment: CrossAxisAlignment.start,
        children: <Widget>[
          Padding(
            padding: const EdgeInsets.symmetric(vertical: 8),
            child: Text(
              'ColorScheme Colors',
              style: theme.textTheme.titleMedium,
            ),
          ),
          Wrap(
            alignment: WrapAlignment.start,
            crossAxisAlignment: WrapCrossAlignment.center,
            spacing: spacing,
            runSpacing: spacing,
            children: <Widget>[
              ColorCard(
                label: 'Primary',
                color: colorScheme.primary,
                textColor: colorScheme.onPrimary,
              ),
              ColorCard(
                label: 'on\nPrimary',
                color: colorScheme.onPrimary,
                textColor: colorScheme.primary,
              ),
              ColorCard(
                label: 'Primary\nContainer',
                color: colorScheme.primaryContainer,
                textColor: colorScheme.onPrimaryContainer,
              ),
              ColorCard(
                label: 'onPrimary\nContainer',
                color: colorScheme.onPrimaryContainer,
                textColor: colorScheme.primaryContainer,
              ),
              ColorCard(
                label: 'Secondary',
                color: colorScheme.secondary,
                textColor: colorScheme.onSecondary,
              ),
              ColorCard(
                label: 'on\nSecondary',
                color: colorScheme.onSecondary,
                textColor: colorScheme.secondary,
              ),
              ColorCard(
                label: 'Secondary\nContainer',
                color: colorScheme.secondaryContainer,
                textColor: colorScheme.onSecondaryContainer,
              ),
              ColorCard(
                label: 'on\nSecondary\nContainer',
                color: colorScheme.onSecondaryContainer,
                textColor: colorScheme.secondaryContainer,
              ),
              ColorCard(
                label: 'Tertiary',
                color: colorScheme.tertiary,
                textColor: colorScheme.onTertiary,
              ),
              ColorCard(
                label: 'on\nTertiary',
                color: colorScheme.onTertiary,
                textColor: colorScheme.tertiary,
              ),
              ColorCard(
                label: 'Tertiary\nContainer',
                color: colorScheme.tertiaryContainer,
                textColor: colorScheme.onTertiaryContainer,
              ),
              ColorCard(
                label: 'on\nTertiary\nContainer',
                color: colorScheme.onTertiaryContainer,
                textColor: colorScheme.tertiaryContainer,
              ),
              ColorCard(
                label: 'Error',
                color: colorScheme.error,
                textColor: colorScheme.onError,
              ),
              ColorCard(
                label: 'on\nError',
                color: colorScheme.onError,
                textColor: colorScheme.error,
              ),
              ColorCard(
                label: 'Error\nContainer',
                color: colorScheme.errorContainer,
                textColor: colorScheme.onErrorContainer,
              ),
              ColorCard(
                label: 'onError\nContainer',
                color: colorScheme.onErrorContainer,
                textColor: colorScheme.errorContainer,
              ),
              ColorCard(
                label: 'Background',
                color: colorScheme.background,
                textColor: colorScheme.onBackground,
              ),
              ColorCard(
                label: 'on\nBackground',
                color: colorScheme.onBackground,
                textColor: colorScheme.background,
              ),
              ColorCard(
                label: 'Surface',
                color: colorScheme.surface,
                textColor: colorScheme.onSurface,
              ),
              ColorCard(
                label: 'on\nSurface',
                color: colorScheme.onSurface,
                textColor: colorScheme.surface,
              ),
              ColorCard(
                label: 'Surface\nVariant',
                color: colorScheme.surfaceVariant,
                textColor: colorScheme.onSurfaceVariant,
              ),
              ColorCard(
                label: 'onSurface\nVariant',
                color: colorScheme.onSurfaceVariant,
                textColor: colorScheme.surfaceVariant,
              ),
              ColorCard(
                label: 'Outline',
                color: colorScheme.outline,
                textColor: colorScheme.background,
              ),
              ColorCard(
                label: 'Outline\nVariant',
                color: colorScheme.outlineVariant,
                textColor: colorScheme.onBackground,
              ),
              ColorCard(
                label: 'Shadow',
                color: colorScheme.shadow,
                textColor: _onColor(colorScheme.shadow, background),
              ),
              ColorCard(
                label: 'Scrim',
                color: colorScheme.scrim,
                textColor: _onColor(colorScheme.scrim, background),
              ),
              ColorCard(
                label: 'Inverse\nSurface',
                color: colorScheme.inverseSurface,
                textColor: colorScheme.onInverseSurface,
              ),
              ColorCard(
                label: 'onInverse\nSurface',
                color: colorScheme.onInverseSurface,
                textColor: colorScheme.inverseSurface,
              ),
              ColorCard(
                label: 'Inverse\nPrimary',
                color: colorScheme.inversePrimary,
                textColor: colorScheme.inverseSurface,
              ),
              ColorCard(
                label: 'Surface\nTint',
                color: colorScheme.surfaceTint,
                textColor: colorScheme.onPrimary,
              ),
            ],
          ),
        ],
      ),
    );
  }
}

/// A [SizedBox] with a [Card] and string text in it. Used in this demo to
/// display theme color boxes.
///
/// Can specify label text color and background color.
class ColorCard extends StatelessWidget {
  const ColorCard({
    super.key,
    required this.label,
    required this.color,
    required this.textColor,
    this.size,
  });

  final String label;
  final Color color;
  final Color textColor;
  final Size? size;

  @override
  Widget build(BuildContext context) {
    const double fontSize = 11;
    const Size effectiveSize = Size(86, 58);

    return SizedBox(
      width: effectiveSize.width,
      height: effectiveSize.height,
      child: Card(
        margin: EdgeInsets.zero,
        clipBehavior: Clip.antiAlias,
        color: color,
        child: Center(
          child: Text(
            label,
            style: TextStyle(color: textColor, fontSize: fontSize),
            textAlign: TextAlign.center,
          ),
        ),
      ),
    );
  }
}

Used Flutter version
Channel master, 3.9.0-19.0.pre.50

Flutter doctor

flutter doctor -v
[✓] Flutter (Channel master, 3.9.0-19.0.pre.50, on macOS 13.2.1 22D68 darwin-arm64, locale en-US)
    • Flutter version 3.9.0-19.0.pre.50 on channel master at /Users/rydmike/fvm/versions/master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4e1ad59f75 (61 minutes ago), 2023-03-30 01:06:46 +0200
    • Engine revision 45467e2a8b
    • Dart version 3.0.0 (build 3.0.0-378.0.dev)
    • DevTools version 2.22.2
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly
      to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/rydmike/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

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

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

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] IntelliJ IDEA Community Edition (version 2022.3.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 72.1.4
    • Dart plugin version 223.8888

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

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 13.2.1 22D68 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 111.0.5563.146

[✓] Network resources
    • All expected network resources are available.

Other Issues Related to DropdownMenu and Menus

[ ] https://github.com/flutter/flutter/issues/131213
[ ] https://github.com/flutter/flutter/issues/131120
[ ] https://github.com/flutter/flutter/issues/130491
[ ] https://github.com/flutter/flutter/issues/128502
[x] https://github.com/flutter/flutter/issues/127672
[x] https://github.com/flutter/flutter/issues/127568
[x] https://github.com/flutter/flutter/issues/126882
[ ] https://github.com/flutter/flutter/issues/123797
[x] https://github.com/flutter/flutter/issues/123631
[x] https://github.com/flutter/flutter/issues/123615
[ ] https://github.com/flutter/flutter/issues/123395
[x] https://github.com/flutter/flutter/issues/120567
[x] https://github.com/flutter/flutter/issues/120349
[x] https://github.com/flutter/flutter/issues/119743

I can reproduce the issue using the code sample provided above.

flutter doctor -v
[✓] Flutter (Channel stable, 3.7.8, on macOS 13.2.1 22D68 darwin-arm64, locale en-GB)
    • Flutter version 3.7.8 on channel stable at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 90c64ed42b (9 days ago), 2023-03-21 11:27:08 -0500
    • Engine revision 9aa7816315
    • Dart version 2.19.5
    • DevTools version 2.20.1

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

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

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

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

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

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

[✓] IntelliJ IDEA Community Edition (version 2023.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 72.1.5
    • Dart plugin version 231.8109.91

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

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 13.2.1 22D68 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 111.0.5563.146

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

• No issues found!

[!] Flutter (Channel master, 3.9.0-19.0.pre.57, on macOS 13.2.1 22D68 darwin-arm64, locale en-GB)
    • Flutter version 3.9.0-19.0.pre.57 on channel master at /Users/nexus/dev/sdks/flutters
    ! Warning: `flutter` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5171031b8f (2 hours ago), 2023-03-30 01:42:08 -0400
    • Engine revision<PHONE_NUMBER>
    • Dart version 3.0.0 (build 3.0.0-378.0.dev)
    • DevTools version 2.22.2
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

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

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

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

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

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

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

[✓] IntelliJ IDEA Community Edition (version 2023.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 72.1.5
    • Dart plugin version 231.8109.91

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

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 13.2.1 22D68 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 111.0.5563.146

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Hi @rydmike, thanks for the detailed issue as always. Can you try to file a new issue for the Accessibility Improvements? We can't guarantee that the accessibility issue and the focus issue will be fixed in the same PR so it would be best if there's a separate issue for it so it can be tracked in the event that this gets closed without touching on the accessibility issue.

@danagbemava-nc for info and as requested, the keyboard accessibility part now has its own issue, see https://github.com/flutter/flutter/issues/123797

The color of the currently selected item in the DropdownMenu is a huge accessibility issue (aside from the keyboard issues), because the color is hard-coded to one of:

very low contrast (opacity 0.12)
the same color as the foreground text

I am a low vision (legally blind) developer and can attest the selected color has very poor contrast, especially because I always use dark backgrounds, and the selection is dark grey on the default surface very dark dark grey.
The following code in dropdown_menu.dart does it:
      final Color focusedBackgroundColor = effectiveStyle.foregroundColor?.resolve(<MaterialState>{MaterialState.focused})
        ?? Theme.of(context).colorScheme.onSurface;
...
      effectiveStyle = entry.enabled && i == focusedIndex
        ? effectiveStyle.copyWith(
            backgroundColor: MaterialStatePropertyAll<Color>(focusedBackgroundColor.withOpacity(0.12))
          )
        : effectiveStyle;

This code appears to have been committed by @QuncCccccc 19 months ago.
If possible, please change this to use MenuButtonThemeData so that we can override the selected item color.
Thank you.

Thanks @tgrushka for bringing attention to this old issue by providing a real world example of how it causes accessibility problems.
The keyboard behavior is also quite problematic imo, but I consider this one more urgent too.

Hey @rydmike and @tgrushka!
Sorry that it took so long to address this so well described issue.
Before polishing a real PR, I would like to share the solution I have started to implement and get your feedbacks, especially to know if it correctly fixes the issue when using a custom style. And also about the default values from _MenuButtonDefaultsM3 because they seem wrong.
Here is the WIP PR where we can discuss in details: https://github.com/flutter/flutter/pull/153159


increase default cache on youtube badges

refs #8605
refs #9237
I've still not managed to catch this happening. If we think it is rate limit-related, lets bump the max age up on these.

Good move updating this. I think I managed to catch it once or twice, and feel pretty confidently it's rate-limit driven based on some digging I did around the time I posted https://github.com/badges/shields/issues/8605#issuecomment-1455163387


[LiveComponent] Fix deprecations / tests

Well, cant win everytime 😅
I'll fix the fix later // DO NOT MERGE :p


[Feature] : Subscription Number Cruncher Calculator

Description
Hey , I would like to add Subscription Number Cruncher Calculator , that calculates the cost of plans for different subscription types and durations.
Kindly assign this task to me under GSSoC'24
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

elaborate please; too vague.
will you be taking just one subscription into account or multiple? can the costs be different if you are taking multiple subscriptions into account? can the durations be different for each?

Yes, what is this calculator about? Pls elaborate properly and if you have any supporting screenshots @aasthakourav20


cannot execute on Raspberry Pi -- all components exit, and loop restart with status code 159

all components freshly downloaded on RPI with Debian10
$docker-compose up -d
$docker ps -a
8d777536b6df   reallibrephotos/librephotos-proxy:latest      "/docker-entrypoint.…"   2 hours ago    Restarting (159) 6 seconds ago                                                librephotos-docker_proxy_1
a5434c282daf   reallibrephotos/librephotos-frontend:latest   "/serve"                 2 hours ago    Restarting (159) 34 seconds ago                                               librephotos-docker_frontend_1
5715aa9e900e   reallibrephotos/librephotos:latest            "/entrypoint.sh"         2 hours ago    Restarting (159) 36 seconds ago                                               librephotos-docker_backend_1
d8c1064f9268   postgres:13                                   "docker-entrypoint.s…"   2 hours ago    Up 56 minutes                     5432/tcp                                    librephotos-docker_db_1
509837c7fec6   redis:6                                       "docker-entrypoint.s…"   2 hours ago    Restarting (159) 37 seconds ago                                               librephotos-docker_redis_1

Could you start it without the -d and paste the console output here. There should be an actual error below that.

My apologies for the incompleteness
$ docker-compose up
Building with native build. Learn about native build in Compose here: https://docs.docker.com/go/compose-native-build/
Starting librephotos-docker_db_1    ... done
Starting librephotos-docker_redis_1 ... done
Starting librephotos-docker_backend_1 ... done
Starting librephotos-docker_frontend_1 ... done
Starting librephotos-docker_proxy_1    ... done
Attaching to librephotos-docker_redis_1, librephotos-docker_db_1, librephotos-docker_backend_1, librephotos-docker_frontend_1, librephotos-docker_proxy_1
db_1        |
db_1        | PostgreSQL Database directory appears to contain a database; Skipping initialization
db_1        |
db_1        | 1970-01-01 00:00:00.000 UTC [1] LOG:  starting PostgreSQL 13.6 (Debian 13.6-1.pgdg110+1) on arm-unknown-linux-gnueabihf, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 32-bit
db_1        | 1970-01-01 00:00:00.000 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
db_1        | 1970-01-01 00:00:00.000 UTC [1] LOG:  listening on IPv6 address "::", port 5432
db_1        | 1970-01-01 00:00:00.000 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1        | 1970-01-01 00:00:00.000 UTC [25] LOG:  database system was shut down at 1970-05-18 02:15:00 UTC
db_1        | 1970-01-01 00:00:00.000 UTC [1] LOG:  database system is ready to accept connections
db_1        | 1970-01-01 00:00:00.000 UTC [29] LOG:  stats collector's time 1970-06-30 23:03:27.634968+00 is later than backend local time 1970-01-01 00:00:00+00
db_1        | 1970-01-01 00:00:00.000 UTC [29] LOG:  stats collector's time 1970-06-30 23:03:27.634968+00 is later than backend local time 1970-01-01 00:00:00+00
librephotos-docker_frontend_1 exited with code 159
librephotos-docker_redis_1 exited with code 159
librephotos-docker_backend_1 exited with code 159
librephotos-docker_redis_1 exited with code 159
^CGracefully stopping... (press Ctrl+C again to force)
Killing librephotos-docker_proxy_1     ... done
Killing librephotos-docker_frontend_1  ... done
Killing librephotos-docker_backend_1   ... done
Killing librephotos-docker_db_1        ... done
Killing librephotos-docker_redis_1     ... done
ERROR: 2
the principal complaint seems to be about this time mismatch between the stats collector and the backend
I did try searching for this error before posting

When googling the error code 159, it returns Raspberry Pi issues with 64 bit docker images. It looks to me like your system does not use 64 bit, but 32 bit. We do not support 32 bit.

Setting 'privileged:true' in docker-compose.yml allowed this to run on so the diagnosis that this was a 32b/64b issue was a false lead,
I then began to experience lots of OOM kills , so I will back off on using librephotos until I can afford an 8Gb Pi


Add index page section to documentation

The current documentation does not describe how to create a index page.  I initially found this confusing, because I expected an index page to be a page rather than a section.  Thus, I tried to access the page content with {{ page.content }} and was very frustrated when I could not.
This addition clarifies that the index page is always a section, even if it does not have any sub-pages.  This should also help people who intend to use Gutenberg to build stand-alone webpages, rather than blogs.
(Also, please let me know if these documentation related pull requests are unwelcome/annoying.  I'm really enjoying using Gutenberg, and I feel that the best way I can help right now—given that I don't (yet) know Rust well enough to contribute code—is by suggesting ways that the documentation could be clearer to address the spots I got stuck.  But if it's not helpful, let me know and I'll knock it off.)

I'm not sure this deserves a special page of its own. Can this be a small subection on https://www.getgutenberg.io/documentation/templates/overview/ before the built-in filter one? It is mentioned in https://www.getgutenberg.io/documentation/templates/pages-sections/#section-variables
I think it can be shorter, for example just saying that the index page is always a section and to refer to the page & section for more details.

(Also, please let me know if these documentation related pull requests are unwelcome/annoying. I'm really enjoying using Gutenberg, and I feel that the best way I can help right now—given that I don't (yet) know Rust well enough to contribute code—is by suggesting ways that the documentation could be clearer to address the spots I got stuck. But if it's not helpful, let me know and I'll knock it off.)

Documentation updates are great, keep them coming!

I moved the info to the templates/overview section as you suggested.  I agree that it's a much better fit there.
I'm not sure I kept it quite as short as you were suggesting, though.  I thought it was helpful to add a bit more context, but let me know if you think that's too much and I can cut it down a bit.

I made the changes you requested.  I also moved a sentence from earlier in the page down to its own section to clarify the nature of built-in templates without adding (much) text.

Thanks!


Using Peer Calls Frontend with Jitsi Meet Backend?

Hello, I'm wondering if is there anyway to use Peer Calls Frontend with Jitsi Meet Backend?
Jitsi Meet backend looks very solid, but in the other hand Peer Calls frontend looks way better than Jitsi Meet frontend.
Thanks in advance!

Hey, thanks for your interest, but I'm afraid it's not possible to use Jitsi Meet as a backend and there are no plans to add support for this.


Unable to do Quick Start due to issues with Hyde

Following the Quick Start, when I do
hugo server --theme=hyde --buildDrafts
I get a large number of errors, all roughly the same:
ERROR: 2016/01/03 template: theme/partials/sidebar.html:4:23: executing "theme/partials/sidebar.html" at <.Site.BaseURL>: BaseURL is not a field of struct type *hugolib.SiteInfo in theme/partials/sidebar.html
ERROR: 2016/01/03 template: theme/partials/head.html:14:39: executing "theme/partials/head.html" at <.Site.BaseURL>: BaseURL is not a field of struct type *hugolib.SiteInfo in theme/partials/head.html
ERROR: 2016/01/03 template: theme/partials/sidebar.html:4:23: executing "theme/partials/sidebar.html" at <.Site.BaseURL>: BaseURL is not a field of struct type *hugolib.SiteInfo in theme/partials/sidebar.html
ERROR: 2016/01/03 Error while rendering 404 page: template: theme/404.html:8:123: executing "theme/404.html" at <.Site.BaseURL>: BaseURL is not a field of struct type *hugolib.SiteInfo

You use an old version of Hyde. Please update.

Thanks for getting in touch, but it feels like this is a question that would be better suited to the Hugo Discussion Forum. We prefer to use GitHub issues only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add some more details if you feel this is a genuine bug.

I got this because the documentation says to use Brew as the easiest option and the Brew version is old. Therefore, this bug should be reopened, right? Or at least a new bug filed to update the version available via Brew. Right? (If no bug exists, I'll file one.)

The Brew version should be up to date. Try a "brew upgrade". This is a case for the discussion forum. We got plenty of real issues and not too many people to handle it. Remember, this is an open source project with people doing free work on their spare time.

I understand what an OS project is and I manage plenty of my own. If a user follows the directions the site provides and it doesn't work, is that not a bug in the documentation versus a support request? What exactly am I doing wrong here? And as far as I know, I had no previous version of Hugo and installed fresh yesterday.

As an FYI, and I'm new to brew, but "brew info hugo" shows hugo: stable 0.13, HEAD

I'm not a homebrew user but a quick look in the repository showed that the latest release v0.15 is the newest listed one.

@digitalcraftsman - right - which is the version you get if you download manually, but not via brew. As I've said, if the issue is "someone needs to push new bits to Brew", I'm happy to file a new report. But right now,a new user (like me :) can't go through the quick start because of this issue.

Brew and Hugo 0.15 is confirmed to work. If you have problems with Brew, please file an issue on their repo.

So are you saying an install from Brew, which according to brew info is 0.13, should work? Or are you saying Brew should install 0.15? Am I using brew info wrong?

Other people had problems with the installations via brew too. According to this thread, do this commands resolve your issue?
brew rm Hugo
brew upgrade
brew install hugo

Did that, and I still get 0.13. brew info hugo still say s0.13 too. brew reports as version 0.9.5.

Ahah - it was brew update, then upgrade, and that got me going. So it seems like the brew CLI is fundamentally at fault here. If a user is told to use brew to install some app, they will always need to brew update first to ensure they have the latest definitions, which makes it seem like a pretty bad flaw in how brew works. Either way, since it seems like more than myself have been hit by this, does it make sense to edit the docs to add a small warning? Even one line would clear it up I think. (And I can file another bug for that.)

See also #824, #1067, #1537 and #1633

Thanks for the great suggestion, @cfjedimaster!   I have just updated the documentation to say brew update && brew install hugo instead of just brew install hugo.  Hope that will prevent other new brew and Hugo users from running into brew-related installation problems.  :wink:

That's perfect - thank you (everyone) for the help. Loving Hugo.
On Tue, Jan 5, 2016 at 12:45 AM, Anthony Fok<EMAIL_ADDRESS>wrote:

Thanks for the great suggestion, @cfjedimaster
https://github.com/cfjedimaster! I have just updated the documentation
to say brew update && brew install hugo instead of just brew install hugo.
Hope that will prevent other new brew and Hugo users from running into
brew-related installation problems. [image: :wink:]
—
Reply to this email directly or view it on GitHub
https://github.com/spf13/hugo/issues/1749#issuecomment-168918107.

--
Raymond Camden, Developer Advocate for MobileFirst at IBM
Email<EMAIL_ADDRESS>Blog : www.raymondcamden.com
Twitter: raymondcamden


Update with latest changes

:tada: This PR is included in version 1.0.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


User defined PDO ID instead of predefined

I'd like to specify my own COB ID for a PDO. In object dictionary editor I set 0x190 for TPDO1 instead of predefined 0x280, but when TPDO is initialized the values is still 0x190, not 0x190 + node ID as I want to. Node ID is added to predefined TPDO COB ID outside initialization and user-specified one is kept "as is". Is that done on purpose? At the moment I use such a workaround in communication reset, just after calling CO_CANopenInitPDO
	uint8_t active_node_id = CO->LSSslave->activeNodeID;
	for(size_t k=0; k < OD_CNT_RPDO; k++){
		CO_RPDO_t* pdo = CO->RPDO + k;
		uint16_t* pdo_can_id = &(pdo->PDO_common.configuredCanId);
		uint8_t  is_valid = pdo->PDO_common.valid;
		if (is_valid){
			//Last 4 bits for node ID. Should be zero or node ID, otherwise it is OD editing error
			if(((*pdo_can_id) & CO_NODE_ID_Msk) == 0){
				*pdo_can_id |= active_node_id;
			} else if (((*pdo_can_id) & CO_NODE_ID_Msk) != active_node_id){
				return retval;
			}
		}
	}

and the same for TPDO, but it seems kinda dirty.
Best,
Serge.

For non-standard behavior you could also make own CO_CANopenInitPDO() and use preDefinedCanId argument according to your needs. If preDefinedCanId is set, node_id will be added to cob_id, if those two are equal. Otherwise custom cob_id can be configured, independent of node_id.


MySQL Exists statement Support

Remove custom exists queries and use jpql to have spring do queries based on the drivers which handle all details
About this change - What it does
Uses JPQL to handle exists requests and removes the native queries.
Resolves: #xxxxx
Why this way

We found during testing that mysql was only saving datetime down to seconds, where  h2 was down to the millisecond.


added gas_griefing PR to the main repo with new tag

added gas_griefing PR to the main repo with new tag

seems perfect now!
Thanks!


Seek .pivotal-keys file and corellate with current git user email to set current api key

Read from ./.pivotal-keys (failover to ~/.pivotal-keys) select a pivotal tracker api key, using the user.email setting in  git --config (checking --local, failover to --global) as a lookup key.
Also solve based on a ~/.pairs / .pairs lookup (see git pair)
e.g.
pivotal-keys:
  - initials: jm
    apikey: FAKEAPIKEYHERE
  - initials: dw
    apikey: FAKEAPIKEYHERE

Done


filter issue

filter attribute is not getting mutated at all. I am using in css filter: blur(5px); and the browser (chrome latest version) fails to parse , since it can read only prefixed -webkit-filter: blur(5px), which works if I write it this way.

"filter: invert()" not also works

@felipeduardo , filter property does not work at all.

Yup, that’s a known issue and happens with all the SVG properties that got new syntax and got adopted into CSS. The reason is that PF sees that they are available without a prefix too, so it thinks they don’t need prefixing.
We could just prefix them blindly, as long as the prefixed version is available, but I’m worried that once browsers start unprefixing them, we will end up using the worse implementation of the two. Also, it might break uses of them in actual SVG, but I haven't tested that.
Ideally, PF should look at the entire definition and check if that’s valid without a prefix, but I’m worried about performance.
In any case, I consider this one of the of the biggest PF issues currently and I really want to find a way to solve it. It bugs me a lot too. :(

Prefixfree is useless due to this bug, as we need prefixer on server-side because of this.

Not really useless, I use it on almost every project of mine, and where it comes to filter and stuff I just manually insert the prefixes.


Added the 'graph groupsettingtemplate get' command solving #442

Added the 'graph groupsettingtemplate get' command solving #442

Coverage remained the same at 100.0% when pulling 6af80a5e2377dad0c63d01371250ffade33d9e98 on waldekmastykarz:graph-groupsettingtemplate-get into 86f8635396eb643e8a3b8016fd2d0d2cfc9c9d37 on SharePoint:dev.

Merged manually