1.0

Added support for .NET metadata table parsing and .NET manifest resources.
Other small fixes.

Here's a quick code snippet for testing:
pe = pype32.PE(<path_to_file>)
m = pe.ntHeaders.optionalHeader.dataDirectory[14].info

# .NET User Strings
for i in m.netMetaDataStreams["#US"].info: print(i)

# .NET Blobs
for i in m.netMetaDataStreams["#Blob"].info: print(i)

# .NET GUIDs
for i in m.netMetaDataStreams["#GUID"].info: print(i)

# .NET Strings
for i in m.netMetaDataStreams["#Strings"].info: print(i)

# .NET metadata tables - beware, usually lot of data
t = m.netMetaDataStreams["#~"].info.tables
for i in sorted(filter(lambda x: isinstance(x, basestring), t)):
    if not t[i]: continue
    for j in t[i]: print(j)

# .NET manifest resources
for i in m.directory.resources.info: print(i)

Did you test it using Python2 or Python3?.

I only tested it with Python 2.7
On Jun 8, 2015 2:41 AM, "Nahuel Riva"<EMAIL_ADDRESS>wrote:

Did you test it using Python2 or Python3?.
—
Reply to this email directly or view it on GitHub
https://github.com/crackinglandia/pype32/pull/4#issuecomment-109818713.

I tested a bit and everything seems to be working as expected. Ready to be merged. Thank you very much for the awesome work!.


LUCENE-10524 Add benchmark suite details to CONTRIBUTING.md

Today, new contributors are usually unaware of where luceneutil benchmarks are and when/how to run them. Committers usually end up pointing contributors to the benchmarks package when they make perf impacting changes and then they run the benchmarks.
Adding benchmark details to the Lucene repo will also make them more accessible to other researchers who want to experiment/benchmark their own custom task implementation with Java Lucene.
JIRA: https://issues.apache.org/jira/browse/LUCENE-10524
cc: @mocobeta

@gautamworah96 This looks good to me!
I wonder if it makes sense to mention the off-the-shelf https://github.com/apache/lucene/tree/main/lucene/benchmark module here too (I didn't find instruction for running it, but a mention still could be helpful).
I'd also suggest letting @mikemccand know the change, thanks.


Fix unwanted changes to other keybindings

This is a tmux-open keybinding just after (re)loading tmux.conf:
> tmux list-keys

bind-key  -T copy-mode-vi o  send-keys -X copy-pipe-and-cancel "xargs -I {} tmux run-shell -b 'cd #{pane_current_path}; xdg-open \"{}\" > /dev/null'"

Then you execute prefix<c-u> once, it will work, but checking tmux list-keys again, the tmux-open keybinding has changed:
> tmux list-keys

bind-key  -T copy-mode-vi o  send-keys -X copy-pipe-and-cancel "xargs -I {} tmux run-shell -b 'cd #{pane_current_path}; xdg-open {} > /dev/null'"

xdg-open \"{}\"  got replaced by xdg-open {} , and tmux-open won't work for URLs containing & and other special chars anymore until reload. There may be a vulnerability here too (because of &some_bad_command).
Migrated from: https://github.com/tmux-plugins/tmux-open/issues/37.

I think it's due to #119. I think it's possibly not saving/restoring keybinding correctly, like not escaping it right.
cc @thalesmello

Thanks!

@bruno- this won't fix it all for tmux-open though.. In the binding
bind-key  -T copy-mode-vi o  send-keys -X copy-pipe-and-cancel "xargs -I {} tmux run-shell -b 'cd #{pane_current_path}; xdg-open \"{}\" > /dev/null'"

The xdg-open \"{}\" part will not honor URLs containing quotes, which is pretty common, for example:  https://duckduckgo.com/?q="double+quotes". It will strip them and turn it into https://duckduckgo.com/?q=double+quotes.

tmux-copycat will not select it correctly too https://duckduckgo.com/?q=.
tmux-yank has presented no issues on that.


Naive experimental way of trying to move packets (overall BAD)

NOT THE FINAL IMPLEMENTATION
THIS IS EXPERIMENTAL AND MEANT AS PROOF OF CONCEPT TO GET FEEDBACK

I will not merge until @TSKsmiley has reviewed, as he knows the most about TypeScript and the overall structure needs to be good
But @JakobTopholt and @Stormlighter feel free to review as well


Extension bundle version

I'd like to Re-open #37370 as I believe that issue was closed without addressing the feedback.
Where can we see the released versions of the ExtensionBundle? I know that I can see the versions of the individual extension packages included in the bundle here: extensions.json, but how am I supposed to know that currently Microsoft.Azure.Functions.ExtensionBundle is at version 1.*, in other words how do I know that I should write this in host.json:
 "extensionBundle": {
        "id": "Microsoft.Azure.Functions.ExtensionBundle",
        "version": "[1.*, 2.0.0)"
    }

and not:
"extensionBundle": {
        "id": "Microsoft.Azure.Functions.ExtensionBundle",
        "version": "[2.*, 3.0.0)"
    }

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5fb82e02-5c41-239b-4903-aab80ff15215
Version Independent ID: 38f1c69b-f7af-5e13-1cdc-b6b7053d2f7b
Content: Register Azure Functions binding extensions
Content Source: articles/azure-functions/functions-bindings-register.md
Service: azure-functions
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

@martinstenhoff Thanks for your question. We are checking on this and will respond to you soon.

@craigshoemaker  Any inputs in this ?

@craigshoemaker Just following up again in case missed the previous communication.

@martinstenhoff I have assigned this to content author for further review and update as appropriate.

cc @soninaren

You can find the releases for extension bundles at https://github.com/Azure/azure-functions-extension-bundles/releases. We are working to get reference documentation out so that you can find the versions of extension bundles released as well as the extension present in the released versions. Lastly all the client / tools used to create a new function app i.e. Core Tools, Portal, VS Code, Maven should automatically add extension bundle configuration by default. With new versions of extension bundles released they automatically start writing the newer configuration in the host.json.


BW-1411 -Change submission format in CBAS

Note to reviewers: The only change made for this PR is the one to the BeanConfig file. Everything else is a change from a previous PR.


Certificate use non Valid Issuer "Fortinet"

Description
New Certificate is generated on one of our Servers.
This one Server suddenly does not use "LetsEncrypt" as Issuer of the Certificate.
It is issued by "Fortinet" and therefore is not Valid.
It runs for a long time now without any issues and suddenly not anymore.
Is there something I can do to solve or is that an error you have to look at?
Expected behavior
Certificate should be issued by "LetsEncrypt" and be valid in any browser
Log
log-20231117.txt
Platform:

OS: Windows Server 2016 Standard German
Version tried with: win-acme.v<IP_ADDRESS>5.x64.trimmed and win-acme.v<IP_ADDRESS>1.x64.trimmed

This is highly likely to be a configuration issue in your network, not a bug in win-acme.

Could then tell me what in the local network could cause this. so we knwo what we have to change to get it up and running again?

I'm just guessing here, but it looks like perhaps web traffic is hitting a Fortigate network appliance (like a firewall) rather than the real server. Maybe you need a port forwarding rule? It could also be that Fortigate is configured to do SSL inspection, in which case this kind of MITM setup is expected (but then your clients should trust the Fortinet certificate).

I can report that you are right. It was the firewall in the customers network which cause the problem.
Thanks for the right direction and thanks for the great tool that makes the life so much easier.


Add support for template literals in enums

Fixes #30962

One small question:
If this one is accepted do I need to update Handbook - Enums section?
It has line "a literal enum expression (basically a string literal or a numeric literal)". Should it include somethins like "basically a string literal, a numeric literal, or a template literal without placeholders" or it is unnecessary detail/incorrect statement?

@ahejlsberg just wanted to get a :+1: from you on this one before proceeding

You made this comment in the issue:

NoSubstitutionTemplateLiteral should be as good as StringLiteral anywhere here IMO

I agree, but this PR narrowly handles string literals in enum initializers. There are multiple other places in the checker where we look for StringLiteral but not NoSubstitutionTemplateLiteral. It's my opinion we should do all of them or none of them.

It's my opinion we should do all of them or none of them.

Except ES6 imports. Because per spec they aren't allowed there. :(

Oh, I was working in scope of initial issue so this PR only supports enums.
If there are no objections - I will prepare new PR to cover other places and replace this PR.
Just to clarify scopeof expected PR:

Updates only to checker

Add support for NoSubstitutionTemplateLiteral where StringLiteral is supported

Do not add TemplateExpressions at this point

Exceptions:

ES6 imports. Because per spec they aren't allowed there.

Which is already and error "String literal expected."

Is it correct?

I'm finishing my investigation of places where support for NoSubstitutionTemplateLiteral can be added.
Should I create separate issue with list of changes for discussion or draft PR with detailed description would be enough?

Is there a blocker on this issue I could help with?

I've prepared list of places that have different behavior for template literals and regular strings.
Hope that scope described in #31548 will be approved and I'll send new PR (will include this changes too) this week.

Closing this one in favor of https://github.com/microsoft/TypeScript/pull/32064


Assets dir override

Here, I replace the override_assets_prefix mechanism by a mechanism in which the override comes from an alternative local directory

thx !


[Feature] Allow users to save APIs as datasources so that they can be reused

Summary
Users should be able to save an API along with its configuration so that it can be reused.
The configuration that needs to be saved:

Headers
Params
Authorization

Motivation

This will enable users to easily switch API endpoints when they need to move from release to prod endpoints
This will enable users to use a single endpoint multiple times across pages and apps

Additional Context
Any other context or screenshots or API request payload/responses that you
pertain to the feature.

@areyabhishek how is this different from our save API as a datasource feature today?

It's the same one, needs some UX updates. I had created this issue for @aakashDesign

Closing this issue, design shared with API Pane redesign team.

Closing this issue, design shared with API Pane redesign team.


Button with multiple, configurable OUTPUT (VAL).

Hello Igor,
in using OpenDeck to control VST Synthesizer, I don't simply need potentiometers and ON-OFF buttons but I often face the need to control "MULTI STATE" switches with more than just two states (rotary switches).
An example are buttons (or rotary switches) used to choose Oscillator's waves forms, that often permit to choose between triangle, sawtooth, sine wave.
These types of controls are now performed trough sliders but could be, more profitably, managed by buttons with multiple output "VAL". An example, is the LFO slider on ARTURIA CS-80 VST that reacts to the position of a sliders to change between its three states:
MONO: val= 0-83
TRIG:   val= 43-84
FREE:  val=85-127
Considering the high number of button available in the board, but the relatively small number of potentiometer, I would love to avoid using potentiometers for these type of controls, but just address some of the several buttons and configure them so that they sends out not just extreme "VAL" (0 or 127), but also "n" intermediate (configurable) VALs.
I’m not an expert in MIDI and I don’t know if this is something reasonable, but I think it can be useful for the users, that “STEP sliders” like the Yamaha CS80 but also the rotary switches of the Jupiter 8-v, or the three state button of the Farfisa, or the three position sliders of the Oberheim Sem V are controlled by "MULTI VAL BUTTON" (see attached pictures) .
Hope this help…
Best regards and thanks for the nice project.
Nicola

This is now implemented.
There are 4 new options for button configuration:

Multi value IncReset Note
Multi value IncDec Note
Multi value IncReset CC
Multi value IncDec CC

When the button is configured in any of these modes, "On velocity/control value" is treated like "step" value between two values. For example, if first option is selected, and "On Velocity" is set to 31, this is the output from the button (single message per button press, newest to oldest even):
21:7:58-Note On 48 vel 127 CH 1
21:7:58-Note On 48 vel 124 CH 1
21:7:58-Note On 48 vel 93 CH 1
21:7:57-Note On 48 vel 62 CH 1
21:7:57-Note On 48 vel 31 CH 1
21:7:56-Note On 48 vel 127 CH 1
21:7:56-Note On 48 vel 124 CH 1
21:7:55-Note On 48 vel 93 CH 1
21:7:54-Note On 48 vel 62 CH 1
21:7:54-Note On 48 vel 31 CH 1

Once the value reached 127, next press will start from configured velocity (step) value.
Second option is different - once the button reaches max value, next press will decrement the value until 0 is reached. This is more akin to how the actual multi-position switches behave:
21:13:56-Note On 48 vel 127 CH 1
21:13:55-Note On 48 vel 124 CH 1
21:13:55-Note On 48 vel 93 CH 1
21:13:55-Note On 48 vel 62 CH 1
21:13:54-Note On 48 vel 31 CH 1
21:13:54-Note On 48 vel 0 CH 1
21:13:54-Note On 48 vel 3 CH 1
21:13:53-Note On 48 vel 34 CH 1
21:13:53-Note On 48 vel 65 CH 1
21:13:53-Note On 48 vel 96 CH 1
21:13:52-Note On 48 vel 127 CH 1
21:13:52-Note On 48 vel 124 CH 1
21:13:51-Note On 48 vel 93 CH 1
21:13:51-Note On 48 vel 62 CH 1
21:13:50-Note On 48 vel 31 CH 1

This option isn't available for current OpenDeck board - it will be available on new ones later this year. For now the option works on any other supported board (Arduino/Teensy).

Wow!!!! Love that!
Thanks a lot for your effort. I really appreciate it.
I hope that this new feature will be appreciated by your customers as well. I think it's really a good one.
By the way, using your device, I think it's really an interesting piece of hardware.
Nicola


Implemented: Static UI for the all pages #8zc8jn

Merging it for now. There are some UI issues to be fixed that can done in a separate PR.


fix twitter.refresh_token error

Problem
Error: Missing valid authorization header occurred in the current code, so the python every_other_dogs.py run failed.
Solution
Pass the auth param that was created with HTTPBasicAuth.
Result
It works fine.

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


build fails with python37 on windows 10

Please upload wheel file for python37 - amd64.

fatal error C1047: The object or library file 'build\extra\iconv-1.14.win64\lib\iconv_a.lib' was created with an older compiler than other objects; rebuild old objects and libraries LINK : fatal error LNK1257: code generation failed

can someone upload the wheel?

created a pull request to fix the issue https://github.com/mehcode/python-xmlsec/pull/116
The issue was that 3rd-party dependencies were compiled with an old version of visual studio, so I recompiled them with vs2017 (available here https://github.com/talebi1/libxml2-win-binaries/releases/tag/master)
Until the pull request is merged, you can:
git clone https://github.com/talebi1/python-xmlsec.git
cd python-xmlsec
pip install .

git clone https://github.com/talebi1/python-xmlsec.git
cd python-xmlsec
pip install .

I tried this but no luck. Any ideas when a wheel might be available for x64?

Repeating my comment from here:

I have built windows wheels for xmlsec. Add my PyPI index when installing:
pip install python3-saml --extra-index-url=https://hoefling.io/pypi

I will prepare a PR for xmlsec that resolves the issue with windows wheels. In the meantime, passing additional index should be good enough for a workaround. See also my answer on SO for more details.

A new version 1.3.7 was released today. One of the notable changes includes pushing prebuilt wheels for Windows on PyPI, so the issue with building Windows wheels locally should be resolved. Install as usual:
pip install xmlsec

Should you experience any issues with prebuilt wheels on Windows, please don't hesitate to open a new issue.


Update defender-for-apis-deploy.md

The pricing pages have been updated and published for Defender for APIs, removing the note

@dcurwin

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


improve OS X build instruction

hold on ... some unexpected error...

Yeah, it should work. I am now reopening it.

one question, is clang-omp available by default? It would be great people still get non omp version compiled when it is not available

Answer: No. clang-omp is provided by third party.
To clearfy, the shipped clang in os x does not support openmp. But you should be able to get no-openmp xgboost using default clang.
And if you want to use openmp, you HAVE TO use third-party clang  / self-compiled clang / third-party gcc / self-compiled gcc, as well as the openmp runtime library. And I think it is most convenient to use homebrew, a package manager on os x, to download clang-omp and libiomp.

One more thing: no gcc is provided in os x by default. gcc and g++ are set to be aliases as clang and clang++ by default
So... if you think it better to "keep everything default" (so no openmp on os x), you can just ignore my makefile chang suggestion.

I mean, it is great to have instruction on openmp, the only thing we want to make sure is that when no_omp=1 was set, everything compiled in default way by using https://github.com/dmlc/xgboost/blob/master/build.sh

Then, you could remove my changes in Makefile.

@fyears I think the instructions is good and it should be merged in. Can you update the PR to remove the changes in makefile? Thanks


chore(deps): update dependency prettier to v1.15.2

chore(deps): update dependency prettier to v1.15.2

From ed74e15b38abd627b6f4b4f7d67da2f702e64124 Mon Sep 17 00:00:00 2001
From: Renovate Bot<EMAIL_ADDRESS>Date: Sun, 18 Nov 2018 17:03:36 +0000
Subject: [PATCH] chore(deps): update dependency prettier to v1.15.2

package.json | 2 +-
yarn.lock    | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/package.json b/package.json
index b6b87e2..60cf75c 100644
--- a/package.json
+++ b/package.json
@@ -22,7 +22,7 @@
"@types/request": "2.48.1",
"jest": "21.2.1",
"jest-playback": "1.0.1",

"prettier": "1.14.3",

"prettier": "1.15.2",
"prettier-config-ikatyang": "1.1.1",
"ts-jest": "21.2.4",
"ts-node": "4.1.0",
diff --git a/yarn.lock b/yarn.lock
index 3af52b3..b65dc39 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -2584,9 +2584,9<EMAIL_ADDRESS>version "1.1.1"
resolved "https://registry.yarnpkg.com/prettier-config-ikatyang/-/prettier-config-ikatyang-1.1.1.tgz#9ccab4bc2d441e4c68b58dbe8f1a4e18213c3f2d"

<EMAIL_ADDRESS>
version "1.14.3"
resolved "https://registry.yarnpkg.com/prettier/-/prettier-1.14.3.tgz#90238dd4c0684b7edce5f83b0fb7328e48bd0895"
<EMAIL_ADDRESS>

version "1.15.2"
resolved "https://registry.yarnpkg.com/prettier/-/prettier-1.15.2.tgz#d31abe22afa4351efa14c7f8b94b58bb7452205e"

<EMAIL_ADDRESS>version "21.2.1"


webpanel

Hey! I configured the panel, but the bots are not displayed

i am using ubuntu 20.04

Make sure the file permissions on the .db file and parent folders have the correct permissions and ownership.


BUG: symbolic layer triggers device creation

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):linux ubuntu 16.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:n/a
TensorFlow installed from (source or binary):binary
TensorFlow version (use command below):b'v1.13.0-rc2-0-gc865ec5621' 1.13.0-rc2
Python version:3.7
Bazel version (if compiling from source):n/a
GCC/Compiler version (if compiling from source):n/a
CUDA/cuDNN version:10.0 / 7.4.2
GPU model and memory:gtx960M

Describe the current behavior
The following code:
import tensorflow as tf
a = tf.placeholder(tf.float32, [100, 100, 100, 100])
b = tf.layers.Conv2DTranspose(3, 3, data_format='channels_first')
output = b.apply(a)

prints:
2019-02-20 10:20:05.505595: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2019-02-20 10:20:05.578782: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:998] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-02-20 10:20:05.579477: I tensorflow/compiler/xla/service/service.cc:150] XLA service 0x55fd579f65d0 executing computations on platform CUDA. Devices:
2019-02-20 10:20:05.579513: I tensorflow/compiler/xla/service/service.cc:158]   StreamExecutor device (0): GeForce GTX 960M, Compute Capability 5.0
2019-02-20 10:20:05.606095: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz
2019-02-20 10:20:05.606746: I tensorflow/compiler/xla/service/service.cc:150] XLA service 0x55fd57b39b00 executing computations on platform Host. Devices:
2019-02-20 10:20:05.606785: I tensorflow/compiler/xla/service/service.cc:158]   StreamExecutor device (0): <undefined>, <undefined>
2019-02-20 10:20:05.607093: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1433] Found device 0 with properties:
name: GeForce GTX 960M major: 5 minor: 0 memoryClockRate(GHz): 1.0975
pciBusID: 0000:01:00.0
totalMemory: 1.96GiB freeMemory: 1.92GiB
2019-02-20 10:20:05.607118: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1512] Adding visible gpu devices: 0
2019-02-20 10:20:05.608205: I tensorflow/core/common_runtime/gpu/gpu_device.cc:984] Device interconnect StreamExecutor with strength 1 edge matrix:
2019-02-20 10:20:05.608229: I tensorflow/core/common_runtime/gpu/gpu_device.cc:990]      0
2019-02-20 10:20:05.608240: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1003] 0:   N
2019-02-20 10:20:05.608504: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1115] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 1742 MB memory) -> physical GPU (device: 0, name: GeForce GTX 960M, pci bus id: 0000:01:00.0, compute capability: 5.0)

It can be seen that it initializes the GPU devices. However this should not happen in symbolic functions.
Initializing the GPU devices has many side effects.
It can lead to different types of failures, such as https://github.com/tensorflow/tensorflow/issues/8136#issuecomment-361727732. The largest side effect is that: any GPU-related flags given to a tf.Session created after device initialization will not take effect.
It will also make it much harder to use horovod because horovod requires initializing the GPU in specific ways (with visible_device_list). If a graph with Conv2DTranspose was created before creating the session (which is the standard way of using TF 1.0), horovod will fail to initialize the session. (cc @alsrgv ).
This bug exists for Conv2DTranspose, but not for Conv2D.
This bug exists in 1.13.0rc0. It does not exist in 1.12.0

This bug was introduced in https://github.com/tensorflow/tensorflow/commit/8ef3e7c8c053cb6dad530e13c478bbd406ea2c95.
In fact, the entire keras/backend.py file heavily relies on looking at the available devices.

I'm guessing we'll have to stick with https://github.com/horovod/horovod/blob/master/examples/keras_imagenet_resnet50.py#L59 in a preamble for any Keras API usage.

3 weeks with no response?

@qlzh727 Are you a good person to look at this?

I am quite occupied right now with some RNN work, but I will reroute this to the correct owner.

It's not obvious to me how one would get around this given that checking devices triggers initialization code if the device is not already initialized. NHWC vs. NCHW device compatibility issues are one of the more common difficulties encountered, hence why we check for it. Ultimately, I think @alsrgv's solution is probably correct: if you need to set specific process level config it will have to be done at the very start.
That said, if you can think of a better solution feel free to suggest it or open a PR.

Device initialization is not the only issue here.
A summary of the cause:
Certain Keras layers call the following function:
def _has_nchw_support():
  explicitly_on_cpu = _is_current_explicit_device('CPU')
  gpus_available = bool(_get_available_gpus())
  return not explicitly_on_cpu and gpus_available

in keras/backend.py. When the function returns False but the layer is called with NCHW format, the layer will apply some format conversions, such as transpose.
There are at least three issues with this approach:

The function _has_nchw_support is clearly wrong.
Many of the involved ops supports NCHW on CPUs with MKL build, and on TPUs.
Consequences: These Keras layers do not behave properly (transpose may be added) on CPUs with MKL build or on TPUs.

Graph construction should be conceptually independent of execution.
-- This IMHO is the core beauty of a graph computation framework.
By looking at available devices for graph construction, it is making an implicit assumption that the graph will be executed on the same device, which is often not a valid assumption.
Consequences: These Keras layers do not behave properly if the graph is not executed on the same device. Examples include:
(1) Creating a graph for deployment (on different machines)
(2) Architecture search (where some worker generates graphs and other workers run it)
(3) Distributed graph with heterogeneous workers, where the whole graph can be constructed on one single worker.
The automatic format conversion, if needed, should be done on the execution level instead.

Looking at GPU devices has side effects. This is an unfortunate fact.
Consequences: After constructing the graph with these Keras layers, users cannot create sessions with custom configs, and as a result cannot use Horovod, set memory fraction, and many others.
Workaround: Create session before graph. But this would break the define-and-run standard paradigm of TF 1.0. Most code using TF is not written like this.

My recommendations:

The first issue obviously needs to be addressed.
For backward compability with previous versions, adds a switch so that these layers do not look at devices when called from tf.layers, but can look at devices when called from tf.keras.layers.
I personally prefer to see the code crash (rather than secretly transpose many times) when there are no appropriate kernels registered on the devices.
In the long run it's best to not look at devices at all and transform the graph in execution.

The implementation of
def _has_nchw_support():
  explicitly_on_cpu = _is_current_explicit_device('CPU')
  gpus_available = bool(_get_available_gpus())
  return not explicitly_on_cpu and gpus_available

appears to have more bugs than what I pointed out above: it does not handle DeviceSpec which makes valid code to crash, reported in https://github.com/tensorflow/tensorflow/issues/27259 and https://github.com/tensorflow/tensorflow/pull/23197.
These issues do not exist in TF 1.12 when the implementation of Conv2DTranspose is not backed by Keras.

Hi There,
We are checking to see if you still need help on this, as you are using an older version of tensorflow which is officially considered end of life . We recommend that you upgrade to the latest 2.x version and let us know if the issue still persists in newer versions. Please open a new issue for any help you need against 2.x, and we will get you the right help.
This issue will be closed automatically 7 days from now. If you still need help with this issue, please provide us with more information.

@ppwwyyxx,
Sorry for the delayed response. When we execute the code,
import tensorflow as tf
a = tf.placeholder(tf.float32, [100, 100, 100, 100])
b = tf.layers.Conv2DTranspose(3, 3, data_format='channels_first')
output = b.apply(a)

using the latest version of Tensorflow with slight modifications with respect to Compatibility, we see that GPUs are no more initialized.
Please find the Gist of the working code. Thanks!


Specgen

Description
Depends on https://github.com/ConduitIO/conduit-commons/pull/131 and https://github.com/ConduitIO/evolviconf (we should clean up that repo and release it so we depend on a released tag).
This contains the new specgen tool which extracts the connector specification into a YAML file. It should always be in the root of the repository and called connector.yaml (or connector.yml).
Usage
After this PR is merged and released, the developer should be able to install the tool using:
go install github.com/conduitio/conduit-connector-sdk/specgen

It should be added in a connector repository in the tools.go file as an import instead of paramgen:
  import (
- 	_ "github.com/conduitio/conduit-commons/paramgen"
+ 	_ "github.com/conduitio/conduit-connector-sdk/specgen"
  )

In the connector.go file it should be added in a go:generate directive, it shouldn't need any flags, just simply:
//go:generate specgen

When upgrading an existing connector to use specgen, you should update the code according to the code changes described in the chapter below, and then generate the initial connector.yaml so that the existing specification is copied over. After that, you can delete the spec.go file and change the connector.go file according to this:
//go:embed connector.yaml
var specs string

var Connector = sdk.Connector{
	NewSpecification: sdk.YAMLSpecification(specs),
	NewSource:        NewSource,
	NewDestination:   NewDestination,
}

This will ensure that the specifications are read from connector.yaml, making it the source of truth for the connector specifications.
Code changes in connectors
This PR changes a few things in the SDK, which will make it necessary to update the connector code. The good news is that it actually simplifies things.
No more Parameters
Neither the Source nor Destination interfaces require the Parameters method anymore. In fact, they were completely removed and are not used anymore. Connectors are expected to fetch the parameter specifications from the YAML file instead.
No more Configure
The Configure method was removed from Source and Destination. This simplifies the interfaces and does not require explicit parsing of the config anymore. Instead, the SDK will take care of parsing the config returned from the interfaces in Config.
Introduced Config
Config replaces both Parameters and Configure in Source and Destination. The connector should return the struct representing the connector configuration as a pointer. The pointer is required so that the SDK can parse the configuration map into that value, making the parsed configuration visible to the connector.
The returned config struct needs to implement SourceConfig / DestinationConfig. Both look the same, they allow the config (but don't require) to implement a method Validate. This will be called by the SDK after parsing the configuration, in case there are any further manual validations that need to happen. This essentially replaces Configure and makes it clear that it should only execute validations.
Note that the defined config struct should normally embed sdk.DefaultSourceMiddleware / sdk.DefaultDestinationMiddleware, so that the middleware is attached to the connector:
type MyConfig struct {
	sdk.DefaultSourceMiddleware
	// other fields ...
}

Another improvement is that the developer can't really "forget" to add the middleware, since the config needs to embed sdk.UnimplementedSourceConfig / sdk.UnimplementedDestinationConfig, not doing so will result in a compile-time error. So they need to either embed it directly (resulting in no middleware) or embed the default middleware struct mentioned above, which already includes the unimplemented config.
Middleware
Source/destination middleware implementations were drastically simplified because of these changes. The middleware is now essentially just a config struct, which needs to be embedded in the connector config. The parameters are automatically parsed when parsing the config, since they are pointers to fields in the config struct defined in the connector. This means that the middleware now doesn't have to manually implement Parameters and Configure, it is all done using specgen and the SDK.
The default middleware is defined in sdk.DefaultSourceMiddleware / sdk.DefaultDestinationMiddleware, which needs to be embedded by the config struct defined in the connector. That config struct now dictates which middleware will wrap the source/destination. If the developer wants to overwrite any defaults in the middleware, they can do so by setting the corresponding values when instantiating the connector:
type Source struct {
	sdk.UnimplementedSource

	config MyConfig
}

func NewSource() sdk.Source {
	return sdk.SourceWithMiddleware( // Extract the middleware from the config and wrap the source
		&Source{
			config: MyConfig{
				DefaultSourceMiddleware: sdk.DefaultSourceMiddleware{ // Change defaults in the default middleware
					SourceWithSchemaExtraction: sdk.SourceWithSchemaExtraction{
						PayloadEnabled: lang.Ptr(false), // Set default value to false
						KeyEnabled:     lang.Ptr(false), // Set default value to false
					},
				},
			},
		},
	)
}

// Config returns a pointer to the config struct. Values will be automatically populated by the SDK.
func (s *Source) Config() sdk.SourceConfig {
	return &s.config
}

Normally, when the developer doesn't need to overwrite any defaults, this can be simplified:
func NewSource() sdk.Source {
	return sdk.SourceWithMiddleware(&Source{})
}

Open work
What's still missing in this PR:

[ ] Rename connector field in the YAML file to specification.
[ ] Order parameters based on whether they are required and alphabetically as a second-order function.
[X] ~Update the validation function to use struct tags instead of requiring the parameter specifications (NOTE: this part needs to be done in conduit-commons and will affect processors as well, although positively).~

Kept it simple for now and used the same validation strategy we used before (using parameters from the specification), only that it's executed in the SDK. We can change this in the future, since this is now an internal thing in the SDK.

[X] Make sure that Validate is called on SourceConfig / DestinationConfig and make sure that the same method is called for all middleware configs as well.

Kept this simple as well, if the developer overwrites the Validate method in their own connector they need to call the middleware Validation method as part of the implementation. It's called out in the documentation.

[ ] Acceptance tests need to be uncommented and adjusted, same goes for the benchmark and probably a lot of the test files.
[ ] Tests, a lot of tests...

Related to https://github.com/ConduitIO/conduit/issues/1523.
Quick checks:

[X] I have followed the Code Guidelines.
[X] There is no other pull request for the same update/change.
[ ] I have written unit tests.
[ ] I have made sure that the PR is of reasonable size and can be easily reviewed.

Connectors are expected to fetch the parameter specifications from the YAML file instead.

@lovromazgon I guess you're referring to connector internals (e.g. when Conduit is asking a connector for the specs, the connector will, through the SDK, parse connector.yaml and reply with the specs)?


Catalog of My Things - Ruby Group Capstone

PR Summary: Catalog of My Things - Ruby Group Capstone
In this set of tasks, the team collaboratively worked on creating a comprehensive cataloging system for various items, including Books, Music Albums, and Games, while ensuring data integrity, user interaction, and data preservation through file storage and SQL databases.
Group Task:

Developed the Item class in a separate .rb file with constructor methods for defining properties visible in the diagram.
Created custom setter methods for 1-to-many relationship properties, moving them away from the constructor.
Implemented methods including:

can_be_archived?() in the Item class to evaluate whether an item is older than 10 years.
move_to_archive() in the Item class, utilizing the can_be_archived?() method to change the archived property.

Established a main.rb file as the console app entry-point with user options, parameter input, and a quit mechanism.

Team-Member-#1: @iamsjunaid

Designed the Book class in a separate .rb file, defining properties in the constructor method.
Constructed the Label class associated with the Item class, setting up properties in the constructor.
Implemented methods such as:

add_item() in the Label class to append an Item instance to the collection, and update its properties accordingly.
can_be_archived?() in the Book class, overriding the parent method and considering additional conditions.

Created unit tests for all methods and options:

Listing all books and labels.
Adding a book.

Ensured data persistence by saving collections in .json files.
Constructed a schema.sql file with tables reflecting the class structures.

Team-Member-#2: @luigirazum

Developed the MusicAlbum class in a separate .rb file, setting properties in the constructor.
Established the Genre class linked to the Item class, defining properties in the constructor.
Implemented methods including:

add_item() in the Genre class to add an Item instance to the collection, updating properties accordingly.
can_be_archived?() in the MusicAlbum class, overriding the parent method and considering an extra condition.

Created unit tests for all methods and options:

Listing all music albums and genres.
Adding a music album.

Ensured data persistence by saving collections in .json files.
Created a schema.sql file with tables mirroring the class structures.

Team-Member-#3: @DebyGrey

Developed the Game class in a separate .rb file, initializing properties in the constructor.
Created the Author class associated with the Item class, defining properties in the constructor.
Implemented methods such as:

add_item() in the Author class to add an Item instance to the collection, updating properties accordingly.
can_be_archived?() in the Game class, overriding the parent method and considering an additional condition.

Created unit tests for all methods and options:

Listing all games and authors.
Adding a game.

Ensured data persistence by saving collections in .json files.
Constructed a schema.sql file with tables reflecting the class structures.

Collectively, the team successfully translated project requirements into specific tasks, implemented these tasks across various classes, and ensured efficient user interaction and data preservation.
Watch the presentation of the project clicking 👉 🎥Video Presentation

thanks @ridwanediallo. 👍


[YUNIKORN-2449] add PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=1 to CI

What is this PR for?
Add PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=1  into yarn install command in CI
What type of PR is it?

[ ] - Bug Fix
[x] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/projects/YUNIKORN/issues/YUNIKORN-2449
How should this be tested?
Test in CI
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

the action of installing dependencies works well.
1m 33s
Run PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=1 yarn install
  PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=1 yarn install
  shell: /usr/bin/bash -e {0}
yarn install v1.22.21
[1/4] Resolving packages...
[2/4] Fetching packages...
warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
Done in 93.68s.

will merge it.

This seems to have been done elsewhere. Closing.


knife user create fails with local mode

Hi,
I'm using chefdk-0.10.0-1.el7.x86_64 and trying to create users in localmode for testing chef-vault.
In Chef12 the syntax is:
knife user create USERNAME DISPLAY_NAME FIRST_NAME LAST_NAME EMAIL PASSWORD (options)

So I run this with the -z option:
bash-4.3$ knife user create quick quick Edward Quick<EMAIL_ADDRESS>secret -z
ERROR: The data in your request was invalid
Response: Must specify "name" in JSON

I tried changing username to name but I still got the same response.
{
  "username": "quick",
  "display_name": "quick",
  "first_name": "Edward",
  "last_name": "Quick",
  "email"<EMAIL_ADDRESS>  "password": "secret",
  "create_key": true
}

This issue sounds similar to issue 3010 but in my case it's trying to create users in local mode.
Am I doing something wrong here, or is this a bug?
Thanks,
Ed

you're probably better off just creating the json manually yourself, the backing store for chef-zero is just the filesystem.

It seems that the solution to this on chef-server is to use chef-server-ctl user-create which means that knife and chef-server are just broken for this command with chef-12 server.  It looks like localmode is just being faithful to this brokenness.  There's nothing to fix in knife right now.  There's also nothing to fix in chef-zero/local-mode right now.  So I think this would have been better submitted as a bug against the server:  http://github.com/chef/chef-server/issues/new.

Thanks, that's exactly what I did in the end and submitted a PR for test-kitchen but I still think this should work with knife user create -z

Ok thanks lamont-granquist, I will leave this for now as I have a workaround.


chore: editor plugin rendering without wrapper

@ala-n, @PolinaVolchetskaya , @Sisha3342 , @nattallius

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Switching traveler gender does not refresh multipliers on Overview tab

Switching traveler gender on Talent tab will properly refresh the UI and show the updated charged attack multipliers. Doing this on the Overview tab will not refresh the UI, and the multipliers will be stuck at the original value

No longer replicable in latest release.


Ranged Expert, the Light Property, and Hand Crossbows

I picked up Ranged Expert for my rogue, wanting to do the classic sword and hand crossbow look, but I noticed something odd - the bonus action attack always showed up, and did not add my character's ability modifier. This was strange, but I figured it was a change on the mod's part since I lacked Two Weapon Fighting.
However, I eventually checked, and realized that it was actually the Crossbow's Light property that was doing this; with just a hand crossbow in my character's hands, the bonus action attack only shows up one I actually take the attack action, and more importantly adds the ability modifier as usual. It seems like the Light property on the hand crossbow is being interpreted like a melee weapon would, allowing TWF, and this is overriding the usual bonus action attack from Ranged Expert.
Unsure if this is intended behavior or not.

Thanks for the detailed explanation. Will share with @EnderWiggin

do you have a save we can use for QA?

Ranged expert adds bonus attack with one handed ranged weapon after you make an attack, so that's why attack appears then. It isn't present before because you can dual wield fight only with melee

That's what I'm saying, though - when I equip a light melee weapon and a hand crossbow, both attacks show up immediately, and it acts like I'm using TWF with two melee weapons. I'm not sure if it's because I've respecced the character, because they're multiclassed, or what - but it's consistent.
Equipping a rapier instead of a shortsword fixes the problem, so it appears to be connected to the melee weapon. Though then I can't use the crossbow until that bonus action attack is enabled, which is a bit of a shame.
handcrossbow.zip

oh... Game doesn't actually check if weapon is melee or not when deciding to add dual-wield bonus attack - it just checks if they are light

@EnderWiggin , as we already patch RefreshFightingStyles() I added a test to deactivate TWF is main or off hand are one handed ranged:
                    if (mainHandSlot.EquipedItem != null && ValidatorsWeapon.IsRanged(mainHandSlot.EquipedItem) &&
                        ValidatorsWeapon.IsOneHanded(mainHandSlot.EquipedItem))
                    {
                        isActive = false;
                    }

                    if (offHandSlot.EquipedItem != null && ValidatorsWeapon.IsRanged(offHandSlot.EquipedItem) &&
                        ValidatorsWeapon.IsOneHanded(offHandSlot.EquipedItem))
                    {
                        isActive = false;
                    }


Add size hint to serialization path

This is a mostly straightforward change to Value serialization. Previously, buffers used in serialiazation were preallocating capacity based on the size of a value, not the number of bytes it will use when serialized. This is described in two issues:

#579
#385

I've fixed this by adding a new method to Value, size_hint. It's documented in the code, which I'll inline here:
pub trait Value {
    fn serialize(&self, buf: &mut Vec<u8>) -> Result<(), ValueTooBig>;
    /// A *hint* to callers indicating how much memory the serialized
    /// form of this `Value` will take. This hint is not defined as a
    /// lower bound, upper bound, nor is an exact size. Every implementation
    /// is free to return the "best guess" available.
    /// The default impl returns `std::mem::size_of::<i32>()` as every Value
    /// at minimum has an i32 sized tag.
    fn size_hint() -> usize {
        std::mem::size_of::<i32>()
    }
}

I've then implemented this method on a bunch of Value impls. The ranges tend to be either exact or optimistic. For example, i8 can be exact:
impl Value for i8 {
    fn serialize(&self, buf: &mut Vec<u8>) -> Result<(), ValueTooBig> { /*...*/ }

    fn size_hint() -> usize {
        size_of::<i32>() + size_of::<Self>()
    }
}

In other cases we know a lower bound but may optimize for slightly above that lower bound:
impl Value for &str {
    fn serialize(&self, buf: &mut Vec<u8>) -> Result<(), ValueTooBig> { /*...*/ }
    fn size_hint() -> usize {
        // 1i32 for the tag, 3i32 for additional characters. This optimizes
        // for the likely case that strings will rarely be empty, and likely
        // be at least a few characters
        4 * size_of::<i32>()
    }
}

In the case of &str the true lower bound is size_of::<i32>(), but typically strings aren't empty, and once you allocate 4 bytes it's reasonable to just allocate 16 and handle what is probably the majority case.
I only used this method in ValueList, basically. I'm not sure if it should be somewhere else too to preallocate.
The results are alright.
main
serialize_lz4_for_iai
  Instructions:               10459
  L1 Accesses:                13456
  L2 Accesses:                   32
  RAM Accesses:                 156
  Estimated Cycles:           19076

fix
serialize_lz4_for_iai
  Instructions:                9838 (-5.937470%)
  L1 Accesses:                12605 (-6.324316%)
  L2 Accesses:                   32 (No change)
  RAM Accesses:                 157 (+0.641026%)
  Estimated Cycles:           18260 (-4.277626%)

Ultimately I think that all of these individual allocations can be removed and, instead, a single buffer could be used. But this is a relatively small, non-breaking change, and it improves memory usage.
Pre-review checklist
(idk what Fixes annotations are, but)
Fixes: https://github.com/scylladb/scylla-rust-driver/issues/579

[X] I have split my patch into logically separate commits.
[X] All commit messages clearly explain what they change and why.
[X] I added relevant tests for new features and bug fixes.
[X] All commits compile, pass static checks and pass test.
[X] PR description sums up the changes and reasons why they should be introduced.
[?] I added appropriate Fixes: annotations to PR description.

What is the motivation behind making size_hint an associated function instead of a method?
As far as I understand, making it a method would allow hints to be more precise, e.g. it would be possible to take &str lenght into account when computing its size hint.

@colin-grapl - can you respond to the review comments?

Hey, sorry, not long after this PR the company I worked for (and founded) was dissolved. I'm no longer working on anything Scylla related.

You have shown results from the serialize_lz4_for_iai benchmark, but I can't find it. Could you point me to it or tell what it does?

https://github.com/bheisler/iai
It was an iai benchmark that I no longer have access to.


RP Throttling may be per-subscription

The article says "The resource provider throttles per region of the resource in the request and per principal ID."
and then lists the limits from Storage RP.   However, Storage Resource Provider (SRP) throttles requests based on subscription...
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#storage-resource-provider-limits
Would be great to get this corrected/clarified.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 3fb31632-581a-56fc-6ee8-5877388bb0b2
Version Independent ID: 09bc0fef-0e2b-a4dc-c74d-9883c8815be3
Content: Request limits and throttling - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/request-limits-and-throttling.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@ashishsinghbhu
Thanks for your feedback! We will investigate and update as appropriate.

@ashishsinghbhu - thanks for this feedback. I have clarified the article to state that within each subscription, RPs throttle per region. The update will get published later today.
#please-close


Updated not implemented and missing target messaging for LT examples.

What does this Pull Request accomplish?
Adds the common exception handling to the LTE examples so it gives reasonable info to the user when either

The server isn't running / couldn't be found
A method that was called isn't implemented (service isn't present / toggled on)

Why should this Pull Request be merged?
Matches other RFmx examples.
Fixes AB#1869076
What testing has been done?
Ran validate_examples.py for LTE. Before it had the grpc error messages. Now for both situations it uses our common wording.

Server not running:
-- Validating: nirfmxlte
 -> Running black line-length 100
All done! ✨ 🍰 ✨
2 files would be left unchanged.
 -> Running mypy
Success: no issues found in 2 source files
 -> Running example: acp-single-carrier.py
Failed to connect to server on localhost:31763
 -> Running example: ul-modacc-single-carrier.py
Failed to connect to server on localhost:31763
PS C:\dev\reckenro-git\grpc-device\source\codegen>

LTE toggle turned off:
-- Validating: nirfmxlte
 -> Running black line-length 100
All done! ✨ 🍰 ✨
2 files would be left unchanged.
 -> Running mypy
Success: no issues found in 2 source files
 -> Running example: acp-single-carrier.py
The operation is not implemented or is not supported/enabled in this service
 -> Running example: ul-modacc-single-carrier.py
The operation is not implemented or is not supported/enabled in this service
PS C:\dev\reckenro-git\grpc-device\source\codegen>


Crash in AuthUI.getInstance() while Signin

Android device: vivo X9
Android OS version: 6.0.1
Google Services version: 3.1.2
Firebase/Play Services SDK version: 11.8.0
FirebaseUI version: 3.1.3

The problem:
Crash in AuthUI.getInstance() while signin
Crash report
Fatal Exception: java.lang.NullPointerException
Attempt to invoke virtual method 'com.google.android.gms.tasks.Task com.google.android.gms.common.api.GoogleApi.zzb(com.google.android.gms.common.api.internal.zzdd)' on a null object reference
com.google.android.gms.internal.zzdvv.zzb (Unknown Source)
com.google.android.gms.internal.zzdwc.setFirebaseUIVersion (Unknown Source)
com.google.firebase.auth.FirebaseAuth.setFirebaseUIVersion (Unknown Source)
com.firebase.ui.auth.AuthUI.getInstance (AuthUI.java:192)
com.firebase.ui.auth.AuthUI.getInstance (AuthUI.java:179)

Code to reproduce
        startActivityForResult(AuthUI.getInstance()
                .createSignInIntentBuilder()
                .setLogo(R.mipmap.ic_launcher)
                .setIsSmartLockEnabled(false)
                .setAvailableProviders(
                        arrayListOf(AuthUI.IdpConfig.Builder(AuthUI.GOOGLE_PROVIDER).build()))
                .setTheme(R.style.LoginTheme)
                .setLogo(R.drawable.logo)
                .build(),
                requestCode)

When you use Android emulators, it's common that they don't have Play Services installed with all the functionalities. You can prevent the app from crashing by checking if Google Play Services APIs are available (just prevent, not a real fix):
public boolean isGooglePlayServicesAvailable(Activity activity) {
    GoogleApiAvailability googleApiAvailability = GoogleApiAvailability.getInstance();
    int status = googleApiAvailability.isGooglePlayServicesAvailable(activity);
    if(status != ConnectionResult.SUCCESS) {
        if(googleApiAvailability.isUserResolvableError(status)) {
              googleApiAvailability.getErrorDialog(activity, status, 2404).show();
        }
        return false;
    }
    return true;
}

Then, you can (if you want) include an alternative sign-in method, such as a simple Email/Password screen.

Hey all.
A fix for this bug has been submitted internally, so this should be fixed in the next 1-2 Firebase Auth SDK releases depending on the release cycle.
I am going to close this issue here since there's nothing more FIrebaseUI can do, thanks for everyone who reported it!

@samtstern does it also solve #396 ?

@jemshit yes I believe those issues are related.

I am still experience the problem .

Firebase ui version 3.2.2
Code that produce error
startActivityForResult(
AuthUI.getInstance()
.createSignInIntentBuilder()
.setTheme(R.style.AppTheme)
.setAvailableProviders(
Arrays.asList(
new AuthUI.IdpConfig.GoogleBuilder().build(),
new AuthUI.IdpConfig.FacebookBuilder().build()))
.build(),
RC_SIGN_IN);

Error in Crashlitic: http://crashes.to/s/a24b2c9ae71

@plugie the fix is not yet released.

@samtstern - any update on the release of this bug fix? It's been about 1.5 months since the last comment here

Yeah, this has been fixed in 3.3.

@samtstern
try to run it without the theme, if it solves the problem move the theme above the providers. for instance when i moved the smart lock it stop crashes on the phone.
i am confused in "move the theme above the providers" do you mean take this method to above or what ? please explain
"when i moved the smart lock " where did you moved ? i dont have smart lock but it occurs
thanks


How OpenStack uses VPC scenario and APIs?

We are designing and implementing VPC APIs (especially for L3 routing) to replace Neutron in OpenStack. I have a question regarding the replacement from a cloud user perspective. In what scenario a cloud user can use VPC APIs in OpenStack environment instead of Neutron?

@Eric-Yuan Could you help to answer this question? Thanks.


Fix link to Design Principles in PTransform Style Guide

The href to Design Principles was broken in the PTransform Style Guide in the documentation.
The href was changed to point to the Contribution Guide.
As per discussion in mailing list<EMAIL_ADDRESS>
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

Test Failure:
- ./generated-local-content/beam/release/2016/06/15/first-release.html
  *  External link https://issues.apache.org/jira/browse/BEAM/ failed: response code 0 means something's wrong.
             It's possible libcurl couldn't connect to the server or perhaps the request timed out.
             Sometimes, making too many requests at once also breaks things.
             Either way, the return message (if any) from the server is: Couldn't connect to server

This is not related to the change in this PR.

R: @mxm

Run Website PreCommit

Run Website PreCommit

Link checks fail. I've manually verified that the new link works :)

Thank you @mxm :metal:


refactor: move package_order to rezplugin system

I was trying to write a new package orderer and discovered that it is not part of the rezplugin system.  This refactor moves the orderers defined in package_order.py to rezplugins.package_order plugins.  Function have been added to package_order.py to remain backward compatible so if a user was directly importing an orderer it should still work.

Hi @cfxegbert. Can you please explain the rationale behind this change? Context is important for us. It helps us document why things were changed, by who, the pros, cons, etc.

This was moved to the rez plugin system so a new package order could be written without having to modify the rez source code.  Before a developer would have to patch the source code and apply the patch every release.  By moving to the plugin system new package orders could be added without modifing the source.

I could also add the rez plugin hooks and not move the existing package orders if you think that would be better.

Scanline VFX is strongly in support of this feature.


Make separate hugr-passes crate, depending on hugr

Already there are some passes implemented in the hugr crate that should be moved out, such as constant_fold_pass and transform_all_cfgs, and more are in the pipeline: #978 #945 #818 #561 . These should be moved into a separate crate, to avoid bloating the hugr crate and ensure that we have an API suitable for users to write their own passes.

This may require adding a hugr-internal (or hugr-core) crate too, that exposes HugrView and related traits. See #294

The only real issue here is that we need to make HugrMut pub. Is that objectionable?

The only real issue here is that we need to make HugrMut pub. Is that objectionable?

HugrMut is already pub. (Not sure how long that has been the case.) So I don't think there are any blockers?


Unit test demonstrating unsafe usage of IntCountsHistogram on write path, and corresponding fix

NetflixOSS » Hystrix » Hystrix-pull-requests #123 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » Hystrix » Hystrix-pull-requests #124 SUCCESS
This pull request looks good


Fix for [FLINK-4894] [network] Don't request buffer after writing to partition

This re-opens #2690.
After merging, we noticed that the test were broken by the changed hasData check. This is reverted here and the clearCurrentBuffer has been updated to correctly reset the position and limit.
I'm mainly re-opening this to wait for Travis. In release-1.1 it's already fixed. If someone has spare time and wants to look at the changes again, feel free to do so.

+1
Merging this...


No path path provided error since version 2.6.2

Hi, we encounter the following error since we updated our project to version 2.6.2 (for now we've reverted our conf to version 2.6.1 which is working).
Here is the error we encountered (we've changed nothing in our configuration to see this appear).
Fatal error: Uncaught exception 'Zend\View\Exception\RuntimeException' with message
'No base path provided' in vendor\zendframework\zend-view\src\Helper\BasePath.php:38

Stack trace:
#0 [internal function]: Zend\View\Helper\BasePath->__invoke('css/styles.less')
#1 vendor\zendframework\zend-view\src\Renderer\PhpRenderer.php(393): call_user_func_array(Object(Zend\View\Helper\BasePath), Array)
#2 module\Application\view\layout\layout.phtml(15): Zend\View\Renderer\PhpRenderer->__call('basePath', Array)
#3 module\Application\view\layout\layout.phtml(15): Zend\View\Renderer\PhpRenderer->basePath('css/styles.less')
#4 vendor\zendframework\zend-view\src\Renderer\PhpRenderer.php(501): include('C:\\dev_tools\\wa...')
#5 vendor\zendframework\zend-view\src\View.php(205): Zend\View\Renderer\PhpRenderer->render(O in vendor\zendframework\zend-view\src\Helper\BasePath.php on line 38

Is their something we've misconfigured in our project ? Or this a critical bug which have to be fixed ?
Thanks.

Ok, I finally found the cause of the problem, because of 2 other Zend bugs we forced the versions of zendframework/zend-view (2.5.3) and zendframework/zend-cache (2.5.3).
If we let zend-view and zend-cache be updated to the last version then it works.
So I close this issue.


[24.x] [WFLY-14880] Upgrade Bouncycastle temporary disable tests for CI

Belongs to https://issues.redhat.com/browse/WFLY-14880
Temporary disable tests to fix CI of https://issues.redhat.com/browse/WFCORE-5461
Undo (enable tests again) will be done with commit in WFLY-14880 changes.
Upstream: https://github.com/wildfly/wildfly/pull/14398

I'm merging this PR without waiting for the CI as all it does is @Ignoring some tests


Id4_bertco_submission

Please have a look to the bertco_ID4_submission commit.
The others are dublicates from previous PRs.
I have a discussion with @supermario about branching problems and we aligned that my PR will includes dublicate files from previous PRs, because at the begining I choose to make PR from the main branch, but I had to create another branch, not using existed Main branch.

rejected:ID4
reason:We cannot fully verify this submission. It looks like you are trying to submit ID4, however, it seems like we cannot find the transaction between your account and Concordium Test Account.

rejected:ID4
reason:We cannot fully verify this submission. It looks like you are trying to submit ID4, however, it seems like we cannot find the transaction between your account and Concordium Test Account.


Release wheels only for python 3.6+

Since setuptools 51.0.0, #2435 has dropped the support of python version 3.5 or lower. However the wheel is named in python 3 generic version setuptools-51.0.0-py3-none-any.whl . Is it possible to release only python 3.6+ wheels so that the older version will pick up the version 50.3.2 for compatibility?

Just checked the latest pip should help choose the right version on the python compatibility. Not an issue anymore.

For more details, the older pip, e.g. pip 9.0.3, failed to parse the data-requires-python in PEP-503. After upgrading the pip version, the latest setuptools installed in, for example Python 3.5, is 50.3.2 at the moment.


misc_history crashes when using proc_appendCnt with cell array input

misc_history crashes when using proc_appendCnt (or proc_appendEpo) with cell array input, since it assumes the first argument to be a struct, not a cell of structs.

eeg_file= fullfile(BTB.DataDir, 'demoMat', ...
'VPkg_08_08_07', 'calibration_motorimageryVPkg');
[cnt, mrk, mnt] = file_loadMatlab(eeg_file);
[cnt_all, mrk_all]= proc_appendCnt({cnt, cnt, cnt}, {mrk, mrk, mrk});

How should this case be handled? Checking that all cnt's have the same 'history' field?

Claimed!
I would change proc_appendCnt rather then misc_history..
I would simply check them sequentially. Is that what you mean?
Or do you really want to check if they have exactly the same history field?
I would simply change cnt = misc_history(cnt); to
if iscell(cnt)
    cnt=cellfun(@misc_history,cnt,'UniformOutput',0);
else
    cnt = misc_history(cnt);
end


Play 2.9.x java 17

Branch of play-2.9.0 (#5648) configured for Java 17 instead of Java 11
Make sure to run bin/build-dev or your container will continue to run Java 11

Created a new cleaner branch


ADDON-35089: Resolved ES Lint failures

ADDON-35089

Fixed/Verified ESlint and proptypes related failures/warnings

:tada: This PR is included in version 5.0.0-develop.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


Research where to host the Report after we have all metrics

Evaluate options to host data after we are able to pull to Who

comments from previous Issue

We have choosen to use Github pages due the best results against what is available for us


Dashboard directly from dataset?

This page states that one can create a dashboard from a dataset, but this doesn't seem to be documented anywhere, nor do I see an option in the service to pin directly from a dataset to a dashboard.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 88b71635-b53c-d810-b40a-8c67ae1edba0
Version Independent ID: 8de35da5-401a-7834-11de-7f4e8af35ca9
Content: Intro to dashboard tiles for Power BI designers - Power BI
Content Source: powerbi-docs/create-reports/service-dashboard-tiles.md
Service: powerbi
Sub-service: pbi-reports-dashboards
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Thanks for your comment, @otravers. This issue has been assigned to the doc author for review.

Hi, @otravers -- good catch! I've updated the article to remove "dataset." Change should be live later today, Mon July 18.


_latest Hive view & integrate with latest Metaflow

Coverage increased (+0.03%) to 97.775% when pulling 36570dbf903c8b3a0eae8e9568c69f247b5c8c5f on tz/latest_view into a7660d5ada900d08e8fefb18976a27194134f1ff on tz/hive.


[DOCS]: Windows Desktop installer has undocumented / missing command-line switches

Description
The "AnythingLLMDesktop.exe" installer seems to take /currentuser, but doesn't have a /?, /h or /help file (I was looking for silent install. 'AnythingLLMDesktop.exe /currentuser /S' acts like it's silent-installing but doesn't actually install)
"%LOCALAPPDATA%\Programs\AnythingLLM\Uninstall AnythingLLM.exe" can take /currentuser and /S for silent uninstall.

Undocumented! I didnt even know that existed 😆!
Either way, we use Electron-builder so the NSIS installer has the typical args (except apparently the ones you expect?)
A silent install would require /D for the path or else it cannot continue
\AnythingLLMDesktop.exe /currentuser /S /D="C:\Users\USER\AppData\Local\Programs\AnythingLLM"


management: Use Realm.objects.get instead of get_realm.

The Realm.DoesNotExist exception will never be raised if we pass a string_id as in that case zerver.models.get_realm function would be used for fetching. realm.zerver.models.get_realm uses filter query so the exception will not be raised even if there are no realm which matches the query.

Added tests and merged as 8230948bbe351f94a9becca5ab4ceffab9bbf3fb

Thanks @hackerkid!  Good catch on this, but next time, I'd encourage you to write the test while you're at it; this sort of subtle case is an ideal circumstance where a test would be useful.


Add minimal token validation

It's exceptionally normal error that token expires. Emit local error if it happens with token payload to help request a new token.

Seems something wider in scope is desired so I'm closing this one. I'm leaving behind the branch though the JWT unpacking is well documented.


fix: make sure the proposed schema is valid before calling it

This PR will make sure that the provided JSON Schema is effectively valid before trying to use it to validate the payload.
Closes #324
SO-234

We're going to make this happen in Graphite.


Move the actual path policies into a public package 'policies'

This will allow them to be used along with the
blueprints.CheckMountpointsPolicy() function outside of images itself.

For a followup: I think we'll also have to make things in internal/pathpolicy/ public.  Right now, if you want to call blueprint.CheckMountpointsPolicy(), the second argument needs to be a *pathpolicy.PathPolicies, which is a private type, so you can only use the policies that are already defined:
	blueprint.CheckMountpointsPolicy(bp.Customizations.Filesystem, policies.MountpointPolicies)

I can imagine it'd be useful for callers to also be able to define their own policies.  We might want to have different ones in BIB.


Settings editor should show "no results" when searching

Do a search that returns no results
Weird empty screen

Glad that VSCode Bot works & provides relevant results otherwise I was opening same issue 😂

@roblourens that's exactly what I had in mind, keep it simple/consistent

👍


[cupertino] Text is rendered black (so not visible) by default in dark mode

Steps to Reproduce

main.dart.zip
Text is incorrectly rendered as black in dark mode, while it should be white.
While the app, when run in bright mode (selected by the ios settings), is rendered correctly,
when dark mode is enabled, text is invisible.
In order to reproduce the problem, in the simulator enable the dark mode from the developer settings of the simulator (iOS 13.3 tested).

Target Platform: iOS
**Target OS version/browser: iOS 13.3 **
**Devices: iPhone 11Max (Simulator), Dark mode enabled **
Logs

$flutter analyze
Analyzing testapp...
No issues found! (ran in 2.2s)

[✓] Flutter (Channel stable, v1.12.13+hotfix.5, on Mac OS X 10.15.2 19C57, locale it)
    • Flutter version 1.12.13+hotfix.5 at /Users/andrea/Downloads/flutter
    • Framework revision 27321ebbad (4 weeks ago), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/andrea/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = /Users/andrea/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.3, Build version 11C29
    • CocoaPods version 1.8.3

[!] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

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

[✓] Connected device (2 available)
    • iPhone di Andrea  • b2d46b5c5c0fc643cee1d68900c98493c96c1fea • ios • iOS 13.3
    • iPhone 11 Pro Max • 09A9F5B2-3BA2-4B84-AAF1-902ABF57466E     • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-3 (simulator)

Code to reproduce:
import 'package:flutter/cupertino.dart';

void main() => runApp(CupertinoStoreApp());

class CupertinoStoreApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return CupertinoApp(
      home: CupertinoStoreHomePage(),
    );
  }
}

class CupertinoStoreHomePage extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return CupertinoPageScaffold(
      navigationBar: CupertinoNavigationBar(
        middle: const Text('Cupertino Store'),
      ),
      child:  SafeArea(child: Text("Here text is expected to be white")),
    );
  }
}

looks like this is in the pipeline to be looked at. In the meantime, however, are there any workarounds? Is there a property I can override in the dark mode theme to get colors to render correctly?

Setting the TextStyle on each Text widget like this seems to be working:
Text("[text]", style: CupertinoTheme.of(context).textTheme.textStyle)
This is however far from an ideal solution, as it has to be set on every Text object.

It looks like setting the app theme manually to dark does  fix the problem but the app will always stay is darkmode
      theme: CupertinoThemeData(brightness: Brightness.dark),

You can force the color to the appropriate value by CupertinoDynamicColor.resolve(CupertinoColors.label, context), but it seems like text styles like CupertinoTheme.of(context).textTheme.navTitleTextStyle may not automatically adapt their colors... Which leads to CupertinoNavigationBar and such displaying black text in dark mode.

Persists with current master 1.21.0-6.0.pre.117

flutter doctor -v
[✓] Flutter (Channel master, 1.21.0-6.0.pre.117, on Mac OS X 10.15.6 19G73, locale en-GB)
    • Flutter version 1.21.0-6.0.pre.117 at /Users/nevercode/dev/flutter
    • Framework revision 7ec2d360bc (2 hours ago), 2020-07-29 23:25:38 -0700
    • Engine revision a9910e409c
    • Dart version 2.10.0 (build 2.10.0-1.0.dev 24c7666def)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/nevercode/Library/Android/sdk
    • Platform android-29, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.9.1

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

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

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

[✓] Connected device (6 available)
    • Redmi Note 7 (mobile)       • 6345c469                                 • android-arm64  • Android 9 (API 28)
    • Nevercode’s iPhone (mobile) • b668e524315069f3db3661ac11ff1f66afafebdb • ios            • iOS 13.6
    • iPhone 11 Pro Max (mobile)  • 55C8466B-5367-492B-8EFE-EC45D980571F     • ios            • com.apple.CoreSimulator.SimRuntime.iOS-13-6 (simulator)
    • macOS (desktop)             • macos                                    • darwin-x64     • Mac OS X 10.15.6 19G73
    • Web Server (web)            • web-server                               • web-javascript • Flutter Tools
    • Chrome (web)                • chrome                                   • web-javascript • Google Chrome 84.0.4147.105

• No issues found!

This problem is still present today, as of flutter 1.22.3.
flutter --version
Flutter 1.22.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 8874f21e79 (12 days ago) • 2020-10-29 14:14:35 -0700
Engine • revision a1440ca392
Tools • Dart 2.10.3

@LongCatIsLooong I'd like to fix this (my case is for navigation bar titles). Should we do this for Cupertino widgets individually in the style of https://github.com/flutter/flutter/blame/1aafb3a8b9b0c36241c5f5b34ee914770f015818/packages/flutter/lib/src/cupertino/nav_bar.dart#L1331? Or is there a way to more broadly apply text style light/dark defaults in the way Material currently does it?

@guidezpl If I remember correctly this happens because CupertinoApp doesn't have a MediaQuery so it can't resolve the text color? What I had in mind was to let WidgetsApp.textStyle take a lazy builder (of type TextStyle Function(BuildContext) ), and defer the color resolution to WidgetsApp.build, but that's a breaking change so I was a bit reluctant.

I'm using a MaterialApp rather than a CupertinoApp to support both platforms.  I don't know if that's an anti-pattern. I'm relying on the implicitly generated CupertinoTextThemeData, which seems incorrect. I'll file a separate issue about that.

Wrapping another MaterialApp widget on top of CupertinoApp would appear to solve this problem for now:
class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: CupertinoApp(
        home: MyHomePage(),
      ),
    );
  }
}

This way, all default Text will render correctly in both light mode and dark mode.
However, there is a side-effect for putting MaterialApp as the root widget: it will make CupertinoAlertDialog always render in light mode.

Wrapping another MaterialApp widget on top of CupertinoApp would appear to solve this problem for now:
class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: CupertinoApp(
        home: MyHomePage(),
      ),
    );
  }
}

This way, all default Text will render correctly in both light mode and dark mode.
However, there is a side-effect for putting MaterialApp as the root widget: it will make CupertinoAlertDialog always render in light mode.

Placing a DefaultTextStyle widget somewhere near the top of the widget tree is also a good workaround. Just remember it needs to be one level lower than the CupertinoApp, or else it cannot find the inherited theme using its build context.
class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return CupertinoApp(
      home: Builder(
        builder: (BuildContext context) {
          return DefaultTextStyle(
            style: CupertinoTheme.of(context).textTheme.textStyle,
            child: MyHomePage(),
          );
        },
      ),
    );
  }
}

Placing a DefaultTextStyle widget somewhere near the top of the widget tree is also a good workaround. Just remember it needs to be one level lower than the CupertinoApp, or else it cannot find the inherited theme using its build context.
class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return CupertinoApp(
      home: Builder(
        builder: (BuildContext context) {
          return DefaultTextStyle(
            style: CupertinoTheme.of(context).textTheme.textStyle,
            child: MyHomePage(),
          );
        },
      ),
    );
  }
}

Aren't navigation bar components already wrapped in a DefaultTextStyle widget and should have the correct text color?

Yes, navigation bar works.
However, the problem still exists with Flutter 1.25.0-8.3.pre • channel beta

Aren't navigation bar components already wrapped in a DefaultTextStyle widget and should have the correct text color?

Yes, navigation bar works.
However, the problem still exists with Flutter 1.25.0-8.3.pre • channel beta

Does this problem still exists??

Does this problem still exists??

Yes, I can confirm this problem still exists with Flutter 2 stable and iOS 14.4 (I had to apply the workaround)

This bug is still happening in the latest stable Flutter, version 2.0.5.
I wasted time debugging this issue.  And now my project's code is more complicated because of the additional unnecessary Builder.
$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.0.5, on Mac OS X 10.15.7 19H524 darwin-x64, locale en)
[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0-rc2)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.1)
[✓] IntelliJ IDEA Community Edition (version 2021.1)
[✓] VS Code (version 1.49.2)
[✓] Connected device (2 available)

• No issues found!

Bug demo:
import 'package:flutter/cupertino.dart'
    show
        Center,
        CupertinoPageScaffold,
        CupertinoApp,
        CupertinoPage,
        CupertinoThemeData,
        Text;
import 'package:flutter/widgets.dart' show runApp, Navigator;

void main() {
  runApp(
    CupertinoApp(
      theme: CupertinoThemeData(),
      title: 'App1',
      home: Navigator(
        pages: [
          CupertinoPage(
              title: 'Home',
              child: CupertinoPageScaffold(child: Center(child: Text('Home'))))
        ],
        onPopPage: (route, result) => true,
      ),
    ),
  );
}

Same problem here, flutter 2.12

flutter doctor -v
<details>
[✓] Flutter (Channel master, 2.6.0-12.0.pre.185, on macOS 12.0 21A5534d darwin-x64, locale en-GB)
    • Flutter version 2.6.0-12.0.pre.185 at /Users/tahatesser/Code/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 91dd3276fd (2 days ago), 2021-10-02 10:18:03 -0700
    • Engine revision 6f4143e800
    • Dart version 2.15.0 (build 2.15.0-172.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/tahatesser/Code/SDK
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/tahatesser/Code/SDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

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

[✓] Android Studio (version 2020.3)
    • 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.10+0-b96-7281165)

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

[✓] Connected device (3 available)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E • ios            • iOS 15.0 19A346
    • macOS (desktop)        • macos                     • darwin-x64     • macOS 12.0 21A5534d darwin-x64
    • Chrome (web)           • chrome                    • web-javascript • Google Chrome 94.0.4606.61
    ! Error: Taha’s iPhone is busy: Making the device ready for development. Xcode will continue when Taha’s iPhone is finished. (code -10)

• No issues found!

It's almost 2 years after bringing up this issue, and it's still not working correctly on Flutter 2.8.0-3.2.pre.

I probably found where is the issue. The _effectiveColor is wrong, because "brightness" setting, which is get from Theme or MediaQuery, returns light, because Theme is null, and at that time when defaultTextStyle is initialized in CupertinoApp, the MediaQuery is not existing, thus it returns by default light. Sadly, I couldn't figure out, why is MediaQuery not initialized, and I couldn't find out how MaterialApp handles this, and since this is my first time digging into the internals of Flutter, I have no idea how to fix this ☹

@gamelaster After looking into all the Cupertino widgets in detail, the real issue is that many simply don't properly resolve CupertinoDynamicColor (and thus, if passed a CupertinoDynamicColor don't display the correct version in dark mode)
I feel like a real solution would be to go through and fix all of these one-off resolution issue, but that's kind of a nightmarish headache from the standpoint of updating all the tests... which is why I haven't worked on a PR.

@cpboyd Hi and thank you for your fast reply 😊
Interesting thing is, that I didn't found any other widgets, which had issues with brightness settings. Also, the Text is not Cupertino widget, so how we would fix color resolving here?
I tested passing CupertinoColors, without using CupertinoDynamicColors.resolve, as you said, it always returns a default color.
But this same behavior is also in Material, isn't?
Thanks

Hi @mleonhard did you tried my workaround? Does it solve some issues, or it still happens?
Anyway, it still seems like Flutter team doesn't maintain the Cupertino (almost) at all, also the documentation for Cupertino is very weak ☹

For now what I did was to write a code that checks if my app is on dark mode. If it is, it changes the text color to white, else it uses the default text color.  (Of course I used riverpod for the state management)
I can show a sample if you want.

I found proper workaround, which should fix all the problems (since this might happen also in other color configurations):
return MediaQuery.fromWindow(
  child: CupertinoApp(
    useInheritedMediaQuery: true,
    home: // ...
  )
);

Why this workaround works? I find out, that in time, when defaultTextStyle in CupertinoApp is initialized, MediaQuery is not initialized, thus it will return (by default) Light Mode. I would like to create PR, although, this is my first time digging into the internals and I doubt my solution will be the correct. Anyway, this workaround is quite elegant, so I will use it until this will be fixed.

This is a better solution than any other specified above. Please do raise a PR to know more about this change from the flutter devs.

Any progress on this?

@ivirtex as far as I know, no ☹

Usually I handle this sort of problem by manually setting the brightness on the CupertinoThemeData using WidgetsBindingObserver.  Then built-in widgets seem to pick up the correct light/dark mode stylings, and I can also query the theme for the brightness myself like CupertinoTheme.of(context).brightness.  Example below.
Does that fix everyone's main visual problem here, or am I missing more details?
I definitely understand that needing to set that up manually is not ideal, and the fact that it is different from Material is a mistake in the API design.  Any real solution to this issue should make Cupertino behave exactly like Material in this regard, and my workaround here would be redundant.

Code
import 'package:flutter/cupertino.dart';

void main() => runApp(const CupertinoHomePage());

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

  @override
  State<CupertinoHomePage> createState() => _CupertinoHomePageState();
}

class _CupertinoHomePageState extends State<CupertinoHomePage> with WidgetsBindingObserver {
  Brightness _brightness = Brightness.light;

  @override
  void initState() {
    super.initState();
    WidgetsBinding.instance.addObserver(this);
    _brightness = WidgetsBinding.instance.window.platformBrightness;
  }

  @override
  void didChangePlatformBrightness() {
    if (mounted) {
      setState(() {
        _brightness = WidgetsBinding.instance.window.platformBrightness;
      });
    }

    super.didChangePlatformBrightness();
  }

  @override
  void dispose() {
    WidgetsBinding.instance.removeObserver(this);
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return CupertinoApp(
      theme: CupertinoThemeData(
        brightness: _brightness,
      ),
      home: const CupertinoPageScaffold(
        navigationBar: CupertinoNavigationBar(
          middle: Text('Cupertino App'),
        ),
        child: SafeArea(
          child: Text('Here text is expected to be white in dark mode, black in light mode.'),
        ),
      ),
    );
  }
}


[BUG]  formio Submission Grid column shows [object Object]

Hello everyone!
In this case, I use with "SubmissionGrid" component and the type field is the "Select" component.
How can I resolve this issue?

We're currently addressing a backlog of GitHub issues. Closing this thread as it is outdated. Please re-open if it is still relevant. Thank you for your contribution!

@jeriah-formio I currently ran over this problem in Version 4.11

@BeateBoettcher
I'm sorry, version<EMAIL_ADDRESS>I'm having difficulty even finding this version published anywhere.


Update authorization docs to line up with contract examples

Preview is available here:http://soroban-docs-pr106.previews.kube001.services.stellar-ops.com/


Switch to buffer causes error (void-function ivy-rich-pad)

Observed behavior
Open any file from a project. In a separate split window run (SPC b B). The following error occurs.

Click to expand
Debugger entered--Lisp error: (void-function ivy-rich-pad)
  (ivy-rich-pad str ivy-rich-switch-buffer-name-max-length)
  (propertize (ivy-rich-pad str ivy-rich-switch-buffer-name-max-length) 'face (cond ((string-match-p "^ *\\*" str) 'font-lock-comment-face) ((and buffer-file-truename (not (file-in-directory-p buffer-file-truename (doom-project-root)))) 'font-lock-doc-face) (t nil)))
  +ivy*rich-switch-buffer-buffer-name("ListZipper.hs")
  apply(+ivy*rich-switch-buffer-buffer-name "ListZipper.hs")
  ivy-rich-switch-buffer-buffer-name("ListZipper.hs")
  ivy-rich-switch-buffer-transformer("ListZipper.hs")
  (cond (buf (ivy-rich-switch-buffer-transformer str)) ((and (eq ivy-virtual-abbreviate 'full) ivy-rich-switch-buffer-align-virtual-buffer) (ivy-rich-switch-buffer-virtual-buffer str)) ((eq ivy-virtual-abbreviate 'full) (propertize (abbreviate-file-name str) 'str 'ivy-virtual)) (t (propertize str 'face 'ivy-virtual)))
  (let ((buf (get-buffer str))) (require 'ivy-rich) (cond (buf (ivy-rich-switch-buffer-transformer str)) ((and (eq ivy-virtual-abbreviate 'full) ivy-rich-switch-buffer-align-virtual-buffer) (ivy-rich-switch-buffer-virtual-buffer str)) ((eq ivy-virtual-abbreviate 'full) (propertize (abbreviate-file-name str) 'str 'ivy-virtual)) (t (propertize str 'face 'ivy-virtual))))
  +ivy-buffer-transformer("ListZipper.hs")
  mapcar(+ivy-buffer-transformer ("ListZipper.hs" "*doom*" "*scratch*" "*Messages*"))
  ivy--format(("ListZipper.hs" "*doom*" "*scratch*" "*Messages*"))
  ivy--exhibit()
  ivy--minibuffer-setup()
  #f(compiled-function () #<bytecode 0x4503466d>)()
  read-from-minibuffer("Switch to buffer: " nil (keymap (keymap (3 keymap (11 . ivy-switch-buffer-kill))) keymap (33554443 . scroll-down-command) (33554442 . scroll-up-command) (11 . previous-line) (escape . abort-recursive-edit) (26 closure ((map keymap (33554443 . scroll-down-command) (33554442 . scroll-up-command) (11 . previous-line) (escape . abort-recursive-edit) #2 (6 . forward-word) (2 . backward-word) (21 . backward-kill-sentence) (23 . backward-kill-word) (1 . move-beginning-of-line) (12 . ivy-alt-done) (67108896 . ivy-call-and-recenter) (3 keymap (19 . ivy-rotate-sort) (1 . ivy-toggle-ignore) (15 . ivy-occur)) (67108903 . ivy-avy) (33554464 . ivy-restrict-to-matches) (15 . +ivy-coo-hydra/body) (22 . yank) (prior . ivy-scroll-down-command) (next . ivy-scroll-up-command) (7 . minibuffer-keyboard-quit) (right . ivy-forward-char) (32 . self-insert-command) (18 . evil-paste-from-register) (19 . counsel-minibuffer-history) (remap keymap (describe-mode . ivy-help) (kill-ring-save . ivy-kill-ring-save) (kill-whole-line . ivy-kill-whole-line) (kill-line . ivy-kill-line) (scroll-down-command . ivy-scroll-down-command) (scroll-up-command . ivy-scroll-up-command) (end-of-buffer . ivy-end-of-buffer) (beginning-of-buffer . ivy-beginning-of-buffer) (kill-word . ivy-kill-word) (forward-char . ivy-forward-char) (delete-char . ivy-delete-char) (backward-kill-word . ivy-backward-kill-word) (backward-delete-char-untabify . ivy-backward-delete-char) (delete-backward-char . ivy-backward-delete-char) (previous-line . ivy-previous-line) (next-line . ivy-next-line)) (9 . ivy-partial-or-done) (10 . next-line) (27 keymap (122 . undo) (1 . ivy-read-action) (15 . ivy-dispatching-call) (111 . ivy-dispatching-done-hydra) (105 . ivy-insert-current) (106 . ivy-yank-word) (114 . ivy-toggle-regexp-quote) (16 . ivy-previous-line-and-call) (14 . ivy-next-line-and-call) (118 . yank) (112 . ivy-previous-history-element) (110 . ivy-next-history-element) (10 . ivy-immediate-done) (13 . ivy-call)) (mouse-3 . ivy-mouse-dispatching-done) (mouse-1 . ivy-mouse-done) (down-mouse-1 . ignore) (13 . ivy-done)) (map keymap (33554443 . scroll-down-command) (33554442 . scroll-up-command) (11 . previous-line) (escape . abort-recursive-edit) #2 (6 . forward-word) (2 . backward-word) (21 . backward-kill-sentence) (23 . backward-kill-word) (1 . move-beginning-of-line) (12 . ivy-alt-done) (67108896 . ivy-call-and-recenter) (3 keymap (19 . ivy-rotate-sort) (1 . ivy-toggle-ignore) (15 . ivy-occur)) (67108903 . ivy-avy) (33554464 . ivy-restrict-to-matches) (15 . +ivy-coo-hydra/body) (22 . yank) (prior . ivy-scroll-down-command) (next . ivy-scroll-up-command) (7 . minibuffer-keyboard-quit) (right . ivy-forward-char) (32 . self-insert-command) (18 . evil-paste-from-register) (19 . counsel-minibuffer-history) (remap keymap (describe-mode . ivy-help) (kill-ring-save . ivy-kill-ring-save) (kill-whole-line . ivy-kill-whole-line) (kill-line . ivy-kill-line) (scroll-down-command . ivy-scroll-down-command) (scroll-up-command . ivy-scroll-up-command) (end-of-buffer . ivy-end-of-buffer) (beginning-of-buffer . ivy-beginning-of-buffer) (kill-word . ivy-kill-word) (forward-char . ivy-forward-char) (delete-char . ivy-delete-char) (backward-kill-word . ivy-backward-kill-word) (backward-delete-char-untabify . ivy-backward-delete-char) (delete-backward-char . ivy-backward-delete-char) (previous-line . ivy-previous-line) (next-line . ivy-next-line)) (9 . ivy-partial-or-done) (10 . next-line) (27 keymap (122 . undo) (1 . ivy-read-action) (15 . ivy-dispatching-call) (111 . ivy-dispatching-done-hydra) (105 . ivy-insert-current) (106 . ivy-yank-word) (114 . ivy-toggle-regexp-quote) (16 . ivy-previous-line-and-call) (14 . ivy-next-line-and-call) (118 . yank) (112 . ivy-previous-history-element) (110 . ivy-next-history-element) (10 . ivy-immediate-done) (13 . ivy-call)) (mouse-3 . ivy-mouse-dispatching-done) (mouse-1 . ivy-mouse-done) (down-mouse-1 . ignore) (13 . ivy-done)) t) nil (interactive) (condition-case nil (progn (call-interactively (function undo))) (error nil))) (6 . forward-word) (2 . backward-word) (21 . backward-kill-sentence) (23 . backward-kill-word) (1 . move-beginning-of-line) (12 . ivy-alt-done) (67108896 . ivy-call-and-recenter) (3 keymap (19 . ivy-rotate-sort) (1 . ivy-toggle-ignore) (15 . ivy-occur)) (67108903 . ivy-avy) (33554464 . ivy-restrict-to-matches) (15 . +ivy-coo-hydra/body) (22 . yank) (prior . ivy-scroll-down-command) (next . ivy-scroll-up-command) (7 . minibuffer-keyboard-quit) (right . ivy-forward-char) (32 . self-insert-command) (18 . evil-paste-from-register) (19 . counsel-minibuffer-history) (remap keymap (describe-mode . ivy-help) (kill-ring-save . ivy-kill-ring-save) (kill-whole-line . ivy-kill-whole-line) (kill-line . ivy-kill-line) (scroll-down-command . ivy-scroll-down-command) (scroll-up-command . ivy-scroll-up-command) (end-of-buffer . ivy-end-of-buffer) (beginning-of-buffer . ivy-beginning-of-buffer) (kill-word . ivy-kill-word) (forward-char . ivy-forward-char) (delete-char . ivy-delete-char) (backward-kill-word . ivy-backward-kill-word) (backward-delete-char-untabify . ivy-backward-delete-char) (delete-backward-char . ivy-backward-delete-char) (previous-line . ivy-previous-line) (next-line . ivy-next-line)) (9 . ivy-partial-or-done) (10 . next-line) (27 keymap (122 . undo) (1 . ivy-read-action) (15 . ivy-dispatching-call) (111 . ivy-dispatching-done-hydra) (105 . ivy-insert-current) (106 . ivy-yank-word) (114 . ivy-toggle-regexp-quote) (16 . ivy-previous-line-and-call) (14 . ivy-next-line-and-call) (118 . yank) (112 . ivy-previous-history-element) (110 . ivy-next-history-element) (10 . ivy-immediate-done) (13 . ivy-call)) (mouse-3 . ivy-mouse-dispatching-done) (mouse-1 . ivy-mouse-done) (down-mouse-1 . ignore) (13 . ivy-done)) nil ivy-history)
  ivy-read("Switch to buffer: " internal-complete-buffer :matcher ivy--switch-buffer-matcher :preselect "*scratch*" :action ivy--switch-buffer-action :keymap (keymap (3 keymap (11 . ivy-switch-buffer-kill))) :caller ivy-switch-buffer)
  ivy-switch-buffer()
  funcall-interactively(ivy-switch-buffer)
  call-interactively(ivy-switch-buffer nil nil)
  command-execute(ivy-switch-buffer)

System information

Click to expand

OS: darwin (x86_64-apple-darwin17.5.0)
Emacs: 26.1 (May 30, 2018)
Doom: 2.0.9 (develop ee9174861328739fbfa866162bef748c160ab076)
Graphic display: t (daemon: nil)
System features: JPEG RSVG IMAGEMAGICK NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS
Details:elc count: 1
uname -a:  Darwin LF02Q331602A90M.local 17.5.0 Darwin Kernel Version 17.5.0: Fri Apr 13 19:32:32 PDT 2018; root:xnu-4570.51.2~1/RELEASE_X86_64 x86_64
modules:   (:feature (evil +everywhere) file-templates (lookup +devdocs +docsets) spellcheck syntax-checker workspaces :completion (ivy +fuzzy) :ui doom-dashboard (doom-modeline +new) evil-goggles hl-todo nav-flash neotree (popup +all +defaults) unicode vi-tilde-fringe vc-gutter window-select (pretty-code +iosevka) :editor :emacs ediff electric eshell imenu term vc :tools gist macos make magit pdf tmux upload wakatime :lang (cc +irony +rtags) common-lisp clojure data erlang elixir elm emacs-lisp go (myhaskell +intero) lspjava javascript lua markdown nix ocaml (org +attach +babel +capture +export +present) perl purescript python rest ruby rust scala sh swift web :collab :config)
packages:  n/a
exec-path: (~/.cargo/bin/ /usr/local/bin/ /usr/bin/ /bin/ /usr/sbin/ /sbin/ ~/.gem/bin/ ~/.cargo/bin/ ~/.local/bin/ ~/bin/ ~/.sdkman/candidates/springboot/current/bin/ ~/.sdkman/candidates/gradle/current/bin/ ~/Library/Android/sdk/tools/ ~/Library/Android/sdk/platform-tools/ ~/n/bin/ /usr/local/Cellar/emacs-plus/26.1/libexec/emacs/26.1/x86_64-apple-darwin17.5.0/)

Please update your plugins (with bin/doom update). The ivy-rich plugin replaced a function with ivy-rich-pad and Doom was forced to update.

Oh thanks that fixed the problem.


Respect COQBIN on calling coq_makefile (examples)

Thanks.

@JasonGross I've been merging these patches, but now I'm wondering if they mess with opam. Does opam set this variable? If it doesn't and the user sets this variable, then won't this break opam builds?


tests: use unambiguous timestamps, fixes #1185

Closes #1185
Detailed explanation in #1185.

I see a number of cases of 1999-1-1 in tests that we'd probably want to change if we wanted to give everything a timestamp and time zone.

Interesting, maybe they're fine then.

Ah good call, probably a good idea to change that one then at least.