Added an option to select architecture to install.

[x] Have you signed the Contributor License Agreement?
[x] Are you working against an Issue?

Related to #906.
This PR adds a option, --architecture, to winget install. This option allows the user to (you guessed it) tell winget what architecture they want to install. If the architecture isn't available, winget does the same thing it would do if there wasn't a installer entry for the user's platform (No applicable installer error). The user is only allowed to provide architectures their system can run (if they ask for arm64 on x64, a CommandException is thrown).
This may have implications for upgrades (I'm not 100% sure on whether upgrade checks the architecture of the currently installed version. If it doesn't, winget might upgrade a 32-bit version to a 64-bit version even if the user didn't want that). If it breaks too much stuff I can close this.
Tested: manually. If I need to write unit tests I can.

Microsoft Reviewers: Open in CodeFlow

Issue #906 was intended to include adding this to settings so a user wouldn't necessarily need to specify on the command line. I wouldn't close that issue until we have a setting (preference and requirement) for architecture. We also may have some pain if we run into a situation where we have an x64 package that requires an x86 dependency and the user has a setting to require only x64 architecture.

Absolutely love the original title

Issue #906 was intended to include adding this to settings so a user wouldn't necessarily need to specify on the command line.

My memory was dim, I thought that issue was purely for adding the argument. Unlinked, sorry.

Absolutely love the original title

TIL that GitHub uses the branch name to name a PR if you didn't specify a title 😄

/azp run

This may have implications for upgrades (I'm not 100% sure on whether upgrade checks the architecture of the currently installed version. If it doesn't, winget might upgrade a 32-bit version to a 64-bit version even if the user didn't want that).

I wanted upgrade to take that into account, but is difficult to determine the true architecture of an installed package based on ARP data alone.  This is actually something we should store in the tracking catalog that I've recently added; the preference/requirement and the architecture itself.  That way we can at try to honor the original request during upgrade.  I don't expect you to do that as part of this change though.
@denelon, are you ok with taking just the command line argument, or do you want the settings implemented as well so as to have a more complete feature?

I think this is a great enhancement al by itself. I'd suggest accepting the feature as implemented, and we will keep the feature open until we build the settings and integrate that with the other work being done.
@jedieaston you rock! This is a fantastic enhancement, and I'm sure will be very well received. I've noticed the ask for 64bit adobe in another manifest. I love being able to eliminate the x64 and x86 variants of the "same" package. We still need to think about what this means in terms of an upgrade when the preferred architecture isn't available in the latest version, but that is a solvable problem.


KV: add add/update functions, unit tests

Improvements to the KV support to match the kernel.

Merge this?


Refactoring the External API and adding a Matcher API

Description

So the external api provided by MockAdapter is essentially inverting the dependency graph i.e.

final dio = Dio(BaseOptions());
final dioAdapter = DioAdapter(dio: dio);

Here the adapter is  forced to  be responsible for setting itself as the httpclientadapter. This creates a few issues while using DI libraries one of which is Dio needs to be instantiated before the adapter despite the adapter not depending of the Dio instance.
it would be great if instead the task of setting the adapter is externalized i.e.
final dio = Dio(BaseOptions());
final dioAdapter = DioAdapter();
dio.httpClientAdapter = dioAdapter;

DioAdapter relies on an internal request matching logic which essentially relies on the entire signature to be equal. Sometimes we may desire the request matching  to be simpler like say just consider path and not the entire request including headers etc.
Current implementation can be improved by externalising matching

We can have an external interface like this
abstract class HttpRequestMatcher{

  bool matches(RequestOptions ongoingRequest, Request matcher);
}

and supplemented by passing an instance to the adapter like this
class DioAdapter extends HttpClientAdapter with Recording, RequestHandling {

  @override
  final HttpRequestMatcher matcher;

  DioAdapter({
    required this.matcher,
  });

This would allow us to have a few matchers like this prebaked into the library and let the users create their own custom matchers as well.
class UrlPathMatcher implements HttpRequestMatcher{

  @override
  bool matches(RequestOptions ongoingRequest, Request matcher) {
    return doesRouteMatch(ongoingRequest.path, matcher.route);
  }
}

Happy to hear your thoughts on this.

Resolved by: #125


Enable standalone Synapse runner

What would you like to be added:
I would like the Synapse runner to support an option to execute workflows as a CLI tool, independent of the Synapse server API. This enhancement would allow the runner to handle workflow state internally without requiring interaction with the API, effectively enabling standalone execution.
By default, the standalone runner should return only the final output of the workflow. However, an option to enable "verbose" mode or detailed logs with task execution history would be valuable for debugging or in-depth analysis.
Why is this needed:
This feature is essential for several reasons:

Facilitate Compliance Tests: By allowing workflows to run in isolation, users can more easily integrate the Synapse runner into CI/CD pipelines to verify compliance with the Serverless Workflow CTK.
Broaden Accessibility: Reducing the dependency on the API makes it easier for new users and contributors to experiment with workflows, accelerating adoption and feedback for the project.
Simplify Testing: It provides a lightweight way for users to test workflows without needing to deploy the full Synapse infrastructure, including a server and database.

This enhancement would significantly improve the usability and flexibility of the Synapse runner while expanding its potential use cases.

Closed by https://github.com/serverlessworkflow/synapse/pull/470


Tomboy-ng icon not displaying in Taskbar Windows 10

Tomboy-ng icon not displaying in Taskbar (right side) in Windows 10. I am using the latest version .35a. I have tried several suggestions found on internet to fix icons not displaying on Taskbar to no avail. Any suggestions?

By default, Windows hides the systray icons under a angle bracket that points up (for lack of a better name). It's on the task bar, towards rhs. If it's there, you can set it to display always, if not there, please let me know....
Davo

I guess the user has found the icon.


Enable auto-generation of Lotman policies

This gives caches the ability to inform Lotman of known namespaces, which Lotman can use to automatically create a (currently toothless) purge policy.
A lot of the work here involved figuring out how to specify named lot policies through our yaml config. Examples of what I came up with can be found in docs/parameters.yaml. Outside of that, some changes involved figuring out how to merge local config with potentially-discovered config.
Until Pelican actually uses the new purge code with the Lotman purge plugin, none of this really does much other than set up a database. For now, this lets us set up most of the lot config in a cache through Pelican, and then the last bits for testing purge stuff need to be configured manually. Until then, the actual purge ordering portion of a policy isn't plumbed into anything -- eventually it will modify XRootD config directly.
Finally, I still haven't worked out completely how to manage expiration/deletion of lots. I'll save that for another PR, potentially in the next release cycle.

For testing this PR, I'd recommend configuring a cache with some lotman policy and a few defined lots, of which at least one should should be an existing namespace. The cache should start up and create the lotman sqlite database, and the tester should be able to verify the values are correctly merged, that a lot is created for each top-level namespace (e.g. for /chtc but not for /chtc/PROTECTED), and that cache disk space is evenly across lots' dedicated_GB field for lots that didn't provide a config override.

@CannonLock, this one also requires a ping for you -- there's a new PolicyDefinitions object from parameters.yaml that replaces the old Lots object.

Also note that tests will continue to fail until the Harbor outage is fixed.

@jhiemstrawisc I've looked through your changes and they seem correct, but I need to do another run and look at the sql database

Cannon is going to open a followup PR with the new parameter validation code, so I'm merging even though this currently fails that action.


Add spec version to tables for the admin

The admin screen needs to be updated to include the spec version for all of the submitted apps.
Web page - admin.html

Not sure, but I think this is redundant with the new web app.


Added @hollystyles' fix for Issue #415

Fixes the problem with permissions when trying to use an external editor to edit old entries on Windows.

Nice one, thanks!


Update README.md

.queue.defrost requires a callback, so this PR updates the documentation to reflect that fact.

Thanks for bringing this up @sebworks! However, I actually submitted a PR just 30 minutes before you yesterday that brings a bigger overhaul to the README and that makes this update obsolete.
The idea is for us to use generated documentation, making it less likely that we will overlook updating the docs, since the documentation code will be written in the source code. You're welcome to look at the updated README (that will hopefully land soon) here


Fixed build error in Xcode 9.

Will this ever be merged?

@Lejdborg @Frugghi Please merge this PR, now that iOS 11 and XCode 9 have been released.

Yeah sorry, I totally forgot to merge this!


VS Reformats my source code when I type, even though I told it not to

Even though I have this turned off in Tools / Options, since installing the nodejs tools for VS, VS is now reformatting my code (changing indentation, adding whitespace) whenever I type ; and during other operations.
This is very annoying.  My code is written the way I want and VS should never be fiddling around with my code simply because I'm typing.
I tried toggling the option in case it simply ignored the setting on first time install, but that didn't help.
This is really, really, really annoying.  Now I have to undo every time VS decides to reformat my code which is all the time that I'm typing.  Grrr.

Did you turn it off in JavaScript formatting options or Node.js formatting options? They are confusinfly in different spots at the moment.

You've got all the formatting options duplicated?!?!?

Yeeeahhhh... its pretty non-ideal... To provide a little more context...
They diverged when we stopped using the JS language service available in the rest of VS in favor of our own Node.js engine that does static analysis because JSLS didn't scale well to the large node projects people were building. So our formatter and intellisense actually behaves differently and requires different options.
See #67 for more info (and please contribute to the discussion there.)

Is this also why Ctrl+SPACE doesn't show intellisense suggestions if I delete all the characters in the "complete intellisense when I type these characters" box?
I just want to type my code and only use intellisense when I ask for it.  I find the constant popping up of "suggestions" annoying and distracting.  I certainly don't want to be typing code, such as calling a method that doesn't yet exist because I'm about to write it, and have the open parent on my as-yet-non-existing method call tell intellisense to change my existing correct code into incorrect code.  This is the most annoying thing about intellisense in IDEs, is that they don't let me simply write correct code without constantly molesting it along the way.
When I've done training classes, it was uniformly the case that people who relied on intellisense to "complete" their code every step of the way took the longest to complete any given exercise.  Intellisense should be an assistant, not a crutch and certainly not a backseat driver constantly nagging me to turn here or turn there when I know exactly where I'm going.

Also, apparently, once I've deleted all those characters from that box, there's no way to reset it to the default without resetting all my options to the defaults globally?  that sucks.  But maybe that's just VS sucking.

Hrm... suggestions for fs module are not being provided, but it is providing suggestions for async module.

I can't reproduce the issue you mentioned with ctrl+space after removing the commit characters - do you have a consistent repro on your end?
The 'fs' issue may be related to #63, so try deleting the ntvs_analysis.dat file in your project folder to fix the 'fs' not experiencing completions issue.
Thanks for explaining your philosophy on IntelliSense. What we have now (showing completions on dot) is indeed consistent with the experience in the rest of Visual Studio, but that doesn't necessarily mean we can't add an option to only show IntelliSense on ctrl+space, so we'd need to investigate further if we wanted to change that behavior.
Re: commit characters - good call - this setting makes more sense in C# than it does in javascript. Would you be happy if we just simplified it to enter/tab to commit by default?

@LegalizeAdulthood Also - totally random comment since I just realized you work for Daz 3D. Thank you so much for your work - Bryce and Daz Studio were my favorite applications and sparked my interest in computer graphics when I was growing up :smiley:

@mousetraps Does it commit on TAB/ENTER?  From the way the settings box is worded, it looks as if it only commits on those special characters.  I'm a bit more anti-intellisense than most people, so I'm probably not the person to decide what the defaults should be; if most people want the intellisense crutch and want that box populated with basically every punctuation character, then the defaults should cater to the most popular request IMO.
I saw it while working on a nodejs script to convert some homebrew help files to RST format for use with Sphinx.  The code should be here:
https://github.com/LegalizeAdulthood/iterated-dynamics/commit/7c22b1454eb48bf7c9264cf13e46341b79709bd4

By the way, I just realized there's already an option for this - if you uncheck "auto list members" and also remove the commit characters, you should get the behavior you're looking for.

Thx again for the feedback. See #310.

@LegalizeAdulthood check out the latest dev build, which defaults to requiring tab/enter to trigger a completion:
https://github.com/Microsoft/nodejstools/releases
To get the settings you want (no isense appearing), you'll want to uncheck:

Text Editor > Node.js > Statement Completion > Auto list members


AdamaxOpt: Adds Adamax Optimizer with eager mode

This PR adds Adamax Optimizer with eager mode

This change is

Review status: 0 of 7 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

src/math/optimizers/adamax_optimizer.ts, line 45 at r1 (raw file):

      protected learningRate: number, private beta1: number,
      private beta2: number,
      /** @deprecated */ specifiedVariableList?: Node[], epsilon = 1e-8) {

we're missing a decay here (to be TF compatible). It looks like this is just how much the learning rate decays at each time step.
https://www.tensorflow.org/api_docs/python/tf/keras/optimizers/Adamax

src/math/optimizers/adamax_optimizer.ts, line 50 at r1 (raw file):

    this.eps = keep(scalar(epsilon));
    // b1, b2 keep initial value of beta* hyperparameters.
    this.b1 = keep(scalar(this.beta1));

call this beta1, beta2, accBeta1, etc and make accB1 a variable

src/math/optimizers/adamax_optimizer.ts, line 99 at r1 (raw file):

  }

  _disposeAndUpdateBeta() {

don't make this a function, just do it inside the tidy() above
Also, make the beta values variables.

Comments from Reviewable

Review status: 0 of 7 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

src/math/optimizers/adamax_optimizer.ts, line 99 at r1 (raw file):
Previously, nsthorat (Nikhil Thorat) wrote…
don't make this a function, just do it inside the tidy() above
Also, make the beta values variables.

just accB1 as a variable, to be clear.

Comments from Reviewable

@nsthorat Actually, the learning rate decay here is something not mentioned in the paper. Should we still add it?

Yeah let's still add it to be TF compatible.

Review status: 0 of 6 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

Comments from Reviewable

One more merge with master :)

Review status: 0 of 6 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

Comments from Reviewable

Hey @ManrajGrover, can you run the unit tests? I changed something with dl.variable() which will make your tests fail. See what I had to do here:
https://github.com/PAIR-code/deeplearnjs/commit/0627b39e1910bd1c0fe7670f12a6fe65831636a7

Review status: 0 of 6 files reviewed at latest revision, 2 unresolved discussions, some commit checks pending.

Comments from Reviewable


direct product for matrices

Hello! Sorry for asking a question here, but I'm new to AngouriMath and I cannot find an implemention of direct product for matrices. So perhaps it would be a feature request.
Actually I'm not sure about the name 'direct product' because I learned it from a physics textbook rather than a mathematical one. So I have made a possible implemention:
static Entity.Matrix DirectProduct(Entity.Matrix left, Entity.Matrix right)
{
    return MathS.Matrix(
        left.RowCount * right.RowCount,
        left.ColumnCount * right.ColumnCount,
        (i, j) =>
        {
            var (iLeft, iRight) = Math.DivRem(i, right.RowCount);
            var (jLeft, jRight) = Math.DivRem(j, right.ColumnCount);
            return left[iLeft, jLeft] * right[iRight, jRight];
        });
}

Well I could just use the previous code but it will be nice if I can directly get it from AngouriMath.

Oh I have finally found TensorProduct through the implemention of TensorPower.
But... why it's a static method? There seems to be no other methods like that. Perhaps the static keyword is mis-added?

This one? Shouldn't be static

@WhiteBlackGoose Thanks for your comment.
Actually I mean TensorProduct. However it seems to be a intentional design. #384
By the way, are there any news about Tensors? Or it is completely considered to be not planned? #152

Tensors used to be part of AM, but I think now it's only matrices.


adding multiple objects in authorizationQueryStringParameters doesnot show login page

we have added 2 objects on the authorizationQueryStringParameters, after adding those it shows only whitepage after building the app.
we added another object on the authorizationQueryStringParameters because the token we are generating before throws 401 when upon hitting our API. it seems that we need to add the resourceUri on the link generated upon login to fix the 401 issue.
we added this
authorizationQueryStringParameters: [{param: 'domain_hint', value: 'my-tenant-guid'}, {param: 'resource', value: 'resource-value'}];
can you help me?

Hello!
I tried creating a test app with a fresh install in both Android and iOS, and initialized MSAL with the default configuration:
function cb(msg) {console.log(msg);}
cordova.plugins.msalPlugin.msalInit(cb, cb);

Then I called SignInInteractive with what you provided, with my own tenant ID modified for my own Azure Portal instance:
cordova.plugins.msalPlugin.signInInteractive(
     cb,
     cb,
     {
          authorizationQueryStringParameters: [
               {param: 'domain_hint', value: 'my-tenant-guid'},
               {param: 'resource', value: 'resource-value'}
          ]
     }
);

I didn't expect it to work completely given I don't have any custom resources configured, but on both Android and iOS I got the authenticator window with a message:

When you called SignInInteractive, did you wrap authorizationQueryStringParameters in an object as above? Were there any errors thrown in the console?

@collab-appsdev Remove User.Read from your default scope and set your singular scope in your msalInit function to {Enter Your AppId GUID here}/User.Read, this will give you a token that has the appid as the audience which should get rid of that 401.


feat: add LizardByte org

I guess this will resolve #14 for me.

I fixed LizardByte! Most of its packages were already in the db, just hadn't gotten to sunshine yet.


Unable to build opencv with python 3.12 on Jetson Orin Nano due to subprocess exited with error: AttributeError: module 'pkgutil' has no attribute 'ImpImporter'

Setup:

Set environmental variable export PYTHON_VERSION=3.12
Run ./build.sh --name=my_container build-essential cmake cuda cudnn gstreamer numpy onnx opencv protobuf:cpp pycuda python pytorch tensorrt tensorflow2 torch2trt torchvision

What works

Just running ./build.sh --name=my_container build-essential cmake cuda cudnn gstreamer numpy onnx opencv protobuf:cpp pycuda python pytorch tensorrt tensorflow2 torch2trt torchvision works but it installs for python 3.8

Error
error.txt
Shortened version below:
  Installing build dependencies: finished with status 'error'
error: subprocess-exited-with-error

× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.
The command '/bin/sh -c /tmp/opencv/opencv_install_deps.sh &&     pip3 install --no-cache-dir    opencv-contrib-python~=${OPENCV_VERSION}     || /tmp/opencv/build.sh' returned a non-zero code: 1
Traceback (most recent call last):
  File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/cuauv-jon/Documents/jetson-containers/jetson_containers/build.py", line 103, in <module>
    build_container(args.name, args.packages, args.base, args.build_flags, args.simulate, args.skip_tests, args.test_only, args.push, args.no_github_api)
  File "/home/cuauv-jon/Documents/jetson-containers/jetson_containers/container.py", line 143, in build_container
    status = subprocess.run(cmd.replace(_NEWLINE_, ' '), executable='/bin/bash', shell=True, check=True)
  File "/usr/lib/python3.8/subprocess.py", line 516, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'DOCKER_BUILDKIT=0 docker build --network=host --tag py312:r35.4.1-cp312-opencv --file /home/cuauv-jon/Documents/jetson-containers/packages/opencv/Dockerfile.pip --build-arg BASE_IMAGE=py312:r35.4.1-cp312-numpy --build-arg OPENCV_VERSION="4.8.1" --build-arg OPENCV_PYTHON="4.x" --build-arg CUDA_ARCH_BIN="7.2,8.7" /home/cuauv-jon/Documents/jetson-containers/packages/opencv 2>&1 | tee /home/cuauv-jon/Documents/jetson-containers/logs/20240429_172346/build/py312_r35.4.1-cp312-opencv.txt; exit ${PIPESTATUS[0]}' returned non-zero exit status 1.

The issue is a result of the an incorrect version of pip being used in the build process.  see this link for more on that.  I don't know how to fix it as far as Dustynv's building scripts.  I am suffering the same error.  https://stackoverflow.com/questions/77364550/attributeerror-module-pkgutil-has-no-attribute-impimporter-did-you-mean


Cloud Spanner tests are failing with gax 4.0.4

All the tests in Node js Spanner client library is failing with the release of 4.0.4 version
Environment details

gax-nodejs version: 4.0.4

Error
TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
at SessionPool._createSessions (/workspace/src/session-pool.ts:740:19)
at runNextTicks (internal/process/task_queues.js:60:5)
at listOnTimeout (internal/timers.js:526:9)
at processTimers (internal/timers.js:500:7)
at SessionPool._fill (/workspace/src/session-pool.ts:820:7) {
generatedMessage: false,
code: 'ERR_ASSERTION',
actual: /workspace/src/session-pool.ts:740
[sessions] = await this.database.batchCreateSessions({
Steps to reproduce

Clone nodejs-spanner library git@github.com:googleapis/nodejs-spanner.git
Upgrade package.json "google-gax": "4.0.4"
run npm test

Looks like this problem is being fixed in https://github.com/grpc/grpc-node/pull/2586.


add-theme script for design-tokens

Requested feature from Slack for an option to use our cli @digdir/designsystemet to add scaffold new themes to design-tokens with our predefined json structure.
One obvious parameter would be theme name and colors, which again would need interop with private Token Studio files 🤔
For example npx @digdir/designsystemet add-theme Altinn --colors "#0062BA, #1E2B3C, ##F45F63, #E5AA20, #1E98F5"

This is no longer relevant due #2374 support updating or adding new themes based on name


"New" launcher, bootstrap.xml compatible

Fundamentally re-think how launcher operates and
bootstrapping the games is managed and configured.
This brings it significantly closer to how the original
bootstrap is doing the job: launcher now utilizes the
data (structures) provided by the bootstrap.xml configuration
file. This creates compatibility with vanilla data dumps
and original stock images. Note that bemanitools does not
include any code or means to run DRM'd data, only decrypted.
But, this allows users to keep decrypted dumps as stock as
possible which means:

No copying around of property files anymore
Keep the modules/ folder with the binaries
Have bemanitools binaries separate in the data
No need to edit/customize the original configuration files

A list of key features of the "new" launcher:

Boostrap games by following the configuration provided by
stock game's bootstrap.xml files
Custom launcher.xml configuration file that adds further
launcher configurable features, composability of
bootstrap.xml configuration(s) as well as configuration
overriding/stacking of selected types of configurations,
e.g. eamuse config, avs-config. The latter eliminates
the need for modifying stock config files in the prop/
folder
Unified logging system: launcher and AVS logging uses
the same logger, all output can now be in a single file
Original features such as various hook types still
available

Move everything to new launcher.xml configuration
files. Adjust the bootstrapping of launcher in the
.bat files. Features such as copying the default
props/ files to nvram are now handled by launcher.
Using the PATH variable, bemanitools binaries can
live in their own dedicated bemanitools/ subfolder
next to props/ and modules/ now. All original
binaries are expected to be kept in a modules/
folder like on stock data.
Due to the significant architectural changes, this also
breaks with any backwards compatibility to existing
launcher setups. Thus, users need to migrate by re-applying
the new configuration format and migrating their config
parameters accordingly.
Further migration instructions and updated documentation
will be provided upon release.

Remark: This is currently not rebased to https://github.com/djhackersdev/bemanitools/pull/278 which is pre-work required for the major refactoring. Just the last two commits account for the actual refactoring work relevant in this PR. I will rebase accordingly to clean-up the history once https://github.com/djhackersdev/bemanitools/pull/278 is merged.

These are still open TODOs and feedback that are not addressed by this PR but will be followed-up to once this is merged.

add development build container
rework logging system, issues with non-async logging and lagging the game (stdout and file must be written async),
implement features such as log ration etc. as outlined by the bootstrap logging config
have some sort of migration guide to switch to the new launcher. part of that should be proper
documentation about how to use the launcher the configuration xml file and what you can do
with it with various use-case examples
align layout of distribution files, different for games such as iidx, jubeat and sdvx
config format with stacking and overriding doesn't work here:

    <fs>
        <nr_filesys __type="u16">16</nr_filesys>
        <nr_mountpoint __type="u16">1024</nr_mountpoint>
        <nr_mounttable __type="u16">32</nr_mounttable>
        <nr_filedesc __type="u16">1024</nr_filedesc>
        <link_limit __type="u16">8</link_limit>
        <root>
            <device __type="str">.</device>
        </root>
        <mounttable_selector __type="str">boot</mounttable_selector>
        <mounttable>
            <vfs name="boot" fstype="fs" src="D:/LDJ/contents/dev/raw" dst="/dev/raw" opt="vf=1,posix=1"/>
            <vfs name="boot" fstype="fs" src="D:/LDJ/contents/dev/nvram" dst="/dev/nvram2" opt="vf=0,posix=1"/>
            <vfs name="boot" fstype="nvram2" src="/dev/nvram2" dst="/dev/nvram" opt="nr_mirror=4"/>
        </mounttable>
    </fs>

vfs nodes are being replaced as they are not unique by node name -> add tag __replace="true" or something similar to


Add documentation for IMessageMonitor

This adds XML documentation to IMessageMonitor.

Could you use the review functionality rather than lots of individual Add single comment uses? It means I only get one email for a code review instead of N 😄

Could you use the review functionality rather than lots of individual Add single comment uses? It means I only get one email for a code review instead of N 😄

Ah sure, will do from now 🙂

@gkinsman I've updated, I've kept to the use of "subscriber" now rather than receiver to keep it obvious which are subscriber and which are publisher related.

Sorry for the delay on this one @yetanotherchris, always appreciate documentation updates! Thanks 🙂

Sorry for the delay on this one @yetanotherchris, always appreciate documentation updates! Thanks 🙂


Missing ./configure line added to README

Added the missing line.

Already added it, thanks!

I also merged by version check comment from later in the document into the instructions. There were a couple subtle bugs a few versions ago in Verilator that would cause weird failures during simulation.


Color detection in TFMobile demo

Hello,
First of all Thank you very much for the great demo and awesome tutorial it makes implementing Tensorflow in android very easy.
I need one help with this,
I have this requirement of detecting the traffic signal, I have a dataset and I have created a model for that and in the general case, it works great.
What I want is to detect what color of the traffic signal is lightened, It means is it Green or Red?
I have added dataset which has two types of images of green and red lightened traffic signals but it is just detecting a traffic signal.
Can anyone help me with this or guide how can I achieve this?

@hcchengithub can you help in this?


Feature/student homepage daniel

Just about done with Student Homepage feature. Ready for review.

Going to switch to this branch real quick and fix the potential merge conflict, has to do with App.js and how the student dashboard isn't pulled with PR.

Going to switch to this branch real quick and fix the potential merge conflict, has to do with App.js and how the student dashboard isn't pulled with PR.

going to need another pull from main before merging to be up to date with recent pushes.

going to need another pull from main before merging to be up to date with recent pushes.


Cleanup of the Tuya integration

Cleanup unused imports
remove old "from typing"
Added docstrings
sort imports
format with black
Added missing types
Misc cleanups

Thank you for your contribution.


Friends and Family list.

-Even after the success message Your are now the Keeper of’, it still does not appear on this list.

If I try again, it says contact exists.

Unable to replicate, will require order of actions to arrive at the issue.


Input background color

how to change background color through attribute in md input

why did you closed, i suppose its a issue for different background color for input boxes rather then white.and also changing the color of the placeholder text

@ashokacharya Please follow the issue template. This issue falls under "Request for support", which will be closed.

if the background of the input be transparent ,and we can change the text and placeholder color with attribute value then it can be more productive for different designs

@jelbourn so please i am stuck in the issue,i tried to change the components but i dont want to make its work flow dirty, where should i get the answer can you sent me the link for support

@jelbourn

@ashokacharya The components are really not production ready at the moment. You can still style individual elements with CSS, so something like
md-input input {
   /** whatever you want here */
}

would probably do what you want for now.

Yes its working on ViewEncapsulation.None but not in Emulated .i think css load  after content is loaded or something, also for buttons theme doesnot work in emulated ,anyway thanks .i will make it work


[🐞 BUG]: randon order in evaluator table (heuristic test)

Description 📝
Randon order in usability percentage evaluator table, the calculus is right but the order is not
Link 🔗
.
Steps to Reproduce 🔄
.
Screenshots 📸
.
Expected Behavior 🤔
.
Actual Behavior 😱
.
Environment 🌍
.
Additional Information ℹ
No response

Can I have this issue @KarinePistili


Travis should test on Node 6

Node 6 is the latest version. It might be helpful to run Travis tests on the latest version.
It's pretty similar to Node 4, so I understand if this PR is rejected.

Changes Unknown when pulling b18c760339007db0d42658a738ed296e5e74c0c6 on EvanHahn:patch-1 into ** on chancejs:master**.

This is great, happy to accept it, though I'm not sure if it'll pass as is

I'll try to fix it. Do you want me to squash commits?

Do you want me to squash commits?

I leave it up to you, not a big deal either way. Thanks!

Ugh, having an issue installing Phantom (it's hanging copying a file). I'll see if I can't sort this out.

This is fixed as of my recent revamp of the testing infrastructure!


yarn execution in the frontend directory yields error

As per:
https://github.com/automacoin/frontend/blob/master/documentation/manual-index.md
$ yarn
00h00m00s 0/0: : ERROR: There are no scenarios; must have at least one.

$ yarn --version
0.32+git

I think it is something related to your configuration. Same issue here https://github.com/yarnpkg/yarn/issues/2821#issuecomment-284181365 apparently. Sorry for the long delay.


SIGSEGV in target incompatible with --linux_perf*

$ honggfuzz -f TMP -n1 -P --linux_perf_branch -- ./target
...
[W][25777] arch_checkWait():250 Persistent mode: pid=25779 exited with status: SIGNALED, signal: 11 (Segmentation fault)
Size:3913 (i,b,hw,edge,ip,cmp): 0/0/2829/11339/72/35475, Tot:0/0/4440/12670/89/36621
[F][25777] arch_perfCreate():120 The PERF FD is already initialized, possibly conflicting perf types enabled

The exit code is 1.

Thanks for the report, this should be fixed at HEAD with https://github.com/google/honggfuzz/commit/636ffba7ccd2b7b934685ae0fa2f37ef368385d9

Confirmed. Thanks.


Is Go's gzip implementation deterministic?

Originally asked in the kubernetes slack.

is gzip (and more specifically go's impl) deterministic?

Wrote a quick PoC to test it. It is deterministic; we ran this gist a few times (each for 5k iterations) and only got identical hashes.


ipfsFactory - Tests that require more than one IPFS node

Some API calls require more than one node to be active, otherwise they fail or timeout (also considered failure), for example: name, DHT and swarm tests.
Our current:
var test = require('interface-ipfs-core')

var common = {
  setup: function (cb) {
    cb(null, yourIPFSInstance)
  },
  teardown: function (cb) {
    cb()
  }
}

// use all of the test suits
test.all(common)

Needs to be upgraded to:
var test = require('interface-ipfs-core')

var common = {
  setup: function (cb) {
    cb(null, ipfsFactory)
  },
  teardown: function (cb) {
    cb()
  }
}

// use all of the test suits
test.all(common)

Where ipfsFactory has a method to spawn a new node
ipfsFactory.spawnNode((err, node)

More, since we already learned from js-ipfs-api and js-ipfs that is useful to spawn nodes with custom configs (e.g: mdns off; no boostrap nodes, etc). What we really need is
ipfsFactory.spawnNode(config, (err, node)

Happening here -> https://github.com/ipfs/interface-ipfs-core/pull/57


Get net::ERR_CACHE_OPERATION_NOT_SUPPORTED error when fetch epub with external epub link

This issue is a Bug
Expected Behaviour

I hope Readium will help me to fix this bug

Steps to reproduce

Use Chrome and readium-js-viewer fetch epub external link
Sometimes, I will got ERR_CACHE_OPERATION_NOT_SUPPORTED only one request.
Disable cache will prevent this bug!?

Test file(s)

Product

Readium cloud reader app

latest development build uploaded at https://readium.firebaseapp.com OR a custom integration (list public deployment URL, if any)
Chrome 72.0.3626.96
macOS High Sierra 10.13.6

Additional information

This bug only appears on chrome.
This bug on macOS mojave and chrome latest version doesn't appear.

I suspect this problem has something to do with the cache strategy implemented in readium-js to handle binary Blob URIs when loading zipped EPUB containers (as opposed to exploded/unzipped publications, which is the recommended mode of operation for the cloud/web reader). See:
https://github.com/readium/readium-js/blob/master/js/epub-fetch/resource_cache.js
https://github.com/readium/readium-js/blob/999d7c32bcdd1184bcc248312267c6e744d737b9/js/epub-fetch/publication_fetcher.js#L36
https://github.com/readium/readium-js/blob/999d7c32bcdd1184bcc248312267c6e744d737b9/js/epub-fetch/content_document_fetcher.js#L28


Dropdown boxes should mirror image layer list

Requested feature
Dropdown boxes should mirror the image layer list. Currently the dropdown box is reversed when selecting a layer in the workflow select widget.
Use case
This will make it easier for users to correlate a napari layer with a layer selection in the workflow select widget.
If this change is NOT made...
Check all that apply, by entering an x inside the brackets:

[x] Everything's fine! But it would be cool if this work happened at some point in the future.

fixed in branch https://github.com/AllenCell/napari-allencell-segmenter/tree/bugfix/reverse_layer_list_dropdown


Missing tensorboardX dependency

Thanks for releasing this.
The separate dependencies for GPU vs CPU vs Mac is very nice.
You need to add tensorboardX. I guess it should go in base.txt but not entirely sure.

Hi @nlothian !
You are definitely right. Fixed this ussue. Thanks for help!


TypeError: el.inputmask is undefined

Hi,
I'm getting following Exception in JS Console in Firefox:

TypeError: el.inputmask is undefined: 1089:114

and in Chrome:

TypeError: Cannot read property '_valueGet' of undefined: 1089

I'm using jquery.inputmask.bundle.js
Can you please fix this?

@MaciejOrman ,
Which version do you use?

The newest.
19.10.2016 18:03 "Robin Herbots"<EMAIL_ADDRESS>napisał(a):

@MaciejOrman https://github.com/MaciejOrman ,
Which version do you use?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RobinHerbots/Inputmask/issues/1424#issuecomment-254859317,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGtR1-UJXtnj08MnEV_6cvJeQV-rexPmks5q1j9agaJpZM4KbHll
.

Which Mask do you use? Can you create a jsfiddle

@MaciejOrman ,
Can you retry with the current version on github

With Version 3.3.4-53 of jquery.inputmask.bundle.js I'm becoming the Exception not any more. Thanks Robert :)


Preset instructions for SP511E to be updated for new JSON API commands

The current instructions  to setup the mechanical buttons on the SP511E controller are depreciated,
You will need to make presets for each button action to make the "M" button cycle through effects create on preset with API Command of FX=~ and save to ID 100. Then make a second preset with FX=~- and save to 101. To cycle speed with the "S" button, you want to take bigger steps. The API commands would be SX=~16 and SX=~-16.
Text to be updated for new JSON support from (0.11+) onwards.

Thanks for the feedback.  But not only is the HTTP API not deprecated, but the JSON API still does not have ~ incrementing and decrementing.  AirCookie plans on adding it, maybe it will make it in before 0.13 is released.


NFR #1

Please do comment as I am not very sure if all of these can be considered NFRs. I might have also missed out some.

Use Mainstream OS wherever we talk about system requirements.
This term is mentioned in Glossary and hence can be used as an convention


Add To Home shortcut not working for some Launchers

We added the "add to home" shortcut functionality, originally captured in #224
Since then, some users have reported that it's not working for them. Let's capture some data about which Launchers are not working to see if it's specifically a Launcher problem or something else.
Reported Launchers

Fastkey launcher
Launcher3 (Android 7.0 / Blackview 6000)

I can confirm that the two launchers mentioned here as well as Apolo launcher are not working for me on a Samsung Galaxy S8 (8.1) and a Google Pixel XL (9.0).

Tested on a Samsung S6 (Android 7.0)
✅ Fastkey
✅ Apolo
Tested on a Pixel 2 (Android 9.0)
👎FastKey
👎Apolo
It seems that the shortcut is created, but not on the Launcher you'd expect - it adds it to the default Pixel Launcher every time you create one.
I don't know what the solution is yet, though.

I tested this further and when using Fastkey launcher, the shortcut is not crested - both on DuckDuckGo and Google Chrome for Android. It's interesting that it works for @cdrussell on Samsung S6 though.
I've also shared this GitHub issue link with the developers of Fastkey on email, to share any ideas they might have.

@arunsathiya what OS version are you using? I suspect the problem only exists on newer versions of Android, maybe Oreo and newer.

@CDRussell I am on Android 8.1.0 at the moment. Also noting that it's a OnePlus 5, which might be offering a flavoured version of Android, not stock.

I looked into this some more and it appears that ShortcutManagerCompat.isRequestPinShortcutSupported(context) returns false when using launchers that do not support the add to home feature (which includes the launchers we confirmed as not working on Android 8+; it seems to return true on older Android versions using said launchers, however).
Since other competing browsers seem to also have this issue with the launchers we've tested, and given @CDRussell's  experience with the add to home feature behaving unpredictably on certain launchers (i.e. making a shortcut on an inactive launcher - not cool!), I think maybe it would be best to either do the ShortcutManagerCompat.isRequestPinShortcutSupported(context) check on button click and handle it there or update the view model canAddToHome = true to use the result of ShortcutManagerCompat.isRequestPinShortcutSupported(context) instead of true, which I believe will effectively "grey it out" for unsupported configurations, though I have not tested this.
If you like these ideas and do not have time to implement/test them, I would be happy to implement and thoroughly test these approaches.
For reference: https://developer.android.com/reference/android/support/v4/content/pm/ShortcutManagerCompat

Thanks for the info, @In2deep73. You are very much right that we should be checking ShortcutManagerCompat.isRequestPinShortcutSupported(context) which we aren't currently doing.
This will return false when the current Launcher doesn't support the shortcut. If your favourite Launcher doesn't currently support them, that's an issue for the Launcher to resolve (if it wants to), and there's nothing further we can do to force it on them.
So it seems there are two parts of this problem:

The app needs to check ShortcutManagerCompat.isRequestPinShortcutSupported(context)
Launchers themselves need this permission com.android.launcher.action.INSTALL_SHORTCUT to support shortcuts. If anyone is raising an issue with a Launcher about this issue, point them to that permission; there may be more work required by the Launchers, but that's for them to support.

I have created a PR for the changes this app needs: #382. If anyone could test that branch out, I'd be most grateful.

@arunsathiya if you want to follow-up on your email to Fastkey, tell them they likely need to add this permission com.android.launcher.action.INSTALL_SHORTCUT.
The permission is only used on newer OS versions (Oreo and newer, I think) so that's why Fastkey shortcuts work on older OS versions but not on newer ones.

Fixed by #382
Thanks again all for your help in raising, diagnosing and solving the problem! 🎉

@CDRussell I shall do that, thanks for getting to the bottom of this and fixing it! 🏆


Add missing init.py

The init.py files are required to make Python treat the directories as containing packages; this is done to prevent directories with a common name, such as string, from unintentionally hiding valid modules that occur later (deeper) on the module search path. In the simplest case, init.py can just be an empty file, but it can also execute initialization code for the package or set the all variable, described later.

Hei @jaydensmith could you please merge and release. Missing this file seems to make this package behave in unexpected ways. We had no issues with Django itself but Celery tasks were not loading correctly because of this file missing.
This is a required file and would make it a proper package.
If there is anything I can do to help please let me know.

No worries, I've merged it now.

@jaydensmith the release actually had no changes. Not sure if github removed this empty file but init.py is still not there even though the pull requested added it.
Could you add it and make a release once more please? Might be that github is behaving in unexpected ways here.


Undefined is not an object (React.PropTypes.func)

I'm having the same problem:
#15
I do not feel like changing the version of react native. There is another solution?
my version:
"react-native": "0.52.0"

this may be helpful for you https://reactjs.org/blog/2017/04/07/react-v15.5.0.html#migrating-from-react.proptypes

Thank you for answering my question.
I did not understand how I can resolve the error.
All I did was:
npm install react-native-emoticons
and
import Emoticons from 'react-native-emoticons';
img of erro
I really need to sort this out. I can not reduce version because it will break the other dependencies.

I was able to solve the problems. The library is already working fine with the latest version of react native (not the latest. and the 0.52).
I suggest changing the library so people do not have to reduce the version of react native.
The modified files were:
react-native-emoctions/tab.js
react-native-emoctions//package.json
The modifications were:
In file react-native-emoctions//package.json
BEFORE
"react-native-scrollable-tab-view": "^0.6.7",
AFTER
 "react-native-scrollable-tab-view": "^0.8.0",
"create-react-class": "^15.6.3", //new

In file react-native-emoctions//package.json
BEFORE
class TabBar extends React.Component {
...
static propTypes = {
        goToPage: React.PropTypes.func,
        activeTab: React.PropTypes.number,
        tabs: React.PropTypes.array,
    };
...
}
export default TabBar;

//AFTER
import PropTypes from 'prop-types';

class TabBar extends React.Component {
.....
}

TabBar.propTypes = {
    goToPage: PropTypes.func,
    activeTab: PropTypes.number,
    tabs: PropTypes.array,
};
export default TabBar;

By changing the tab.js file to the new structure of PropTypes (external library) and updating and inserting the dependencies of the package.json file, the library works without errors.

You are  correct. I just miss it.  I'll fix it later. Thanks a lot.

@renatosistemasvc .Thank you.
I apply the modification but I have the error ;Cannot read property 'type' of undefined

@WapiMukki Show me an error image. Or a console.log..
I'm using it without any problem. Show more details to find out what's happening.

You are correct. problem fix it.
Thank you

even though react-native-scrollable-tab-view to latest  problem still remaining.any guidance? thanks guys

我用的0.55.4的版本，也出现这个错误。
安装时出现这个错误
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^
4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fse
vents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@
1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}
应该是版本太低导致的
使用时出现这个错误！
Undefined is not an object (React.PropTypes.func)
但是不知道怎么解决

I stumbled on this GH issue looking for a fix to this same error for a non-native ReactJS project. For what its's worth, I just "fixed" it by downgrading from "react": "^17.0.1" to "react": "^15.4.1". I'm thinking it might be deeper than the react-native package...


Add documentation for new NFT RPCs

Signed-off-by: danieljperry<EMAIL_ADDRESS>

Opened as a new PR due to docs site reorg.


Device request: Lidl HG08164

Could you add this device?
I will include device interview once i receive the device.
https://www.zigbee2mqtt.io/devices/HG08164.html

Here is the interview. If a PR with the implementation would work faster please let me know and i will work on that. Either way thanks in advance
  "ids": {
    "modelId": "TS004F",
    "manufacturerName": "_TZ3000_rco1yzb1"
  },
  "endpoints": {
    "endpointDescriptors": [
      {
        "endpointId": 1,
        "applicationProfileId": 260,
        "applicationDeviceId": 260,
        "applicationDeviceVersion": 0,
        "_reserved1": 1,
        "inputClusters": [
          0,
          1,
          3,
          4,
          6,
          4096,
          57345
        ],
        "outputClusters": [
          25,
          10,
          3,
          4,
          5,
          6,
          8,
          4096
        ]
      }
    ],
    "endpoints": {
      "1": {
        "clusters": {
          "basic": {
            "attributes": [
              {
                "acl": [
                  "readable",
                  "reportable"
                ],
                "id": 0,
                "name": "zclVersion"
              },
              {
                "acl": [
                  "readable",
                  "reportable"
                ],
                "id": 1,
                "name": "appVersion"
              },
              {
                "acl": [
                  "readable",
                  "reportable"
                ],
                "id": 2,
                "name": "stackVersion"
              },
              {
                "acl": [
                  "readable",
                  "reportable"
                ],
                "id": 3,
                "name": "hwVersion"
              },
              {
                "acl": [
                  "readable",
                  "reportable"
                ],
                "id": 4,
                "name": "manufacturerName"
              },
              {
                "acl": [
                  "readable",
                  "reportable"
                ],
                "id": 5,
                "name": "modelId"
              },
              {
                "acl": [
                  "readable",
                  "reportable"
                ],
                "id": 6,
                "name": "dateCode"
              },
              {
                "acl": [
                  "readable",
                  "reportable"
                ],
                "id": 7,
                "name": "powerSource"
              },
              {
                "acl": [
                  "readable",
                  "writable",
                  "reportable"
                ],
                "id": 65502
              },
              {
                "acl": [
                  "readable",
                  "reportable"
                ],
                "id": 65533,
                "name": "clusterRevision"
              },
              {
                "acl": [
                  "readable",
                  "reportable"
                ],
                "id": 65534,
                "name": "attributeReportingStatus"
              },
              {
                "acl": [
                  "readable",
                  "reportable"
                ],
                "id": 65504
              },
              {
                "acl": [
                  "readable",
                  "reportable"
                ],
                "id": 65505
              },
              {
                "acl": [
                  "readable",
                  "reportable"
                ],
                "id": 65506
              },
              {
                "acl": [
                  "readable",
                  "reportable"
                ],
                "id": 65507
              }
            ]
          },
          "powerConfiguration": {},
          "identify": {},
          "groups": {
            "commandsGenerated": "UNSUP_GENERAL_COMMAND",
            "commandsReceived": "UNSUP_GENERAL_COMMAND"
          },
          "onOff": {
            "attributes": [
              {
                "acl": [
                  "readable",
                  "writable",
                  "reportable"
                ],
                "id": 32772,
                "reportingConfiguration": {
                  "status": "NOT_FOUND",
                  "direction": "reported"
                }
              }
            ],
            "commandsGenerated": "UNSUP_GENERAL_COMMAND",
            "commandsReceived": "UNSUP_GENERAL_COMMAND"
          },
          "touchlink": {
            "commandsGenerated": "UNSUP_GENERAL_COMMAND",
            "commandsReceived": "UNSUP_GENERAL_COMMAND"
          }
        },
        "bindings": {
          "identify": {},
          "groups": {
            "commandsGenerated": "UNSUP_GENERAL_COMMAND",
            "commandsReceived": "UNSUP_GENERAL_COMMAND"
          },
          "onOff": {
            "attributes": [
              {
                "acl": [
                  "readable",
                  "writable",
                  "reportable"
                ],
                "id": 32772,
                "reportingConfiguration": {
                  "status": "NOT_FOUND",
                  "direction": "reported"
                }
              }
            ],
            "commandsGenerated": "UNSUP_GENERAL_COMMAND",
            "commandsReceived": "UNSUP_GENERAL_COMMAND"
          },
          "touchlink": {
            "commandsGenerated": "UNSUP_GENERAL_COMMAND",
            "commandsReceived": "UNSUP_GENERAL_COMMAND"
          },
          "ota": {
            "attributes": [],
            "commandsGenerated": "UNSUP_GENERAL_COMMAND",
            "commandsReceived": "UNSUP_GENERAL_COMMAND"
          },
          "time": {},
          "scenes": {},
          "levelControl": {}
        }
      }
    }
  }

Sorry for not responding here, it's been supported in the tuya app since before.. the Lidl app will support it in next release.

Please compare: https://github.com/JohanBendz/com.lidl/issues/17


Google Play APK download panics

Description
I've been trying to download an APK from the Google Play Store using apkeep but sadly encountered an error.
I used the following command:
apkeep -a com.instagram.android -d GooglePlay -u<EMAIL_ADDRESS>-p 'VYsAAtDzQSZ57LCE25SdKQVHZqnQsTVs2u3rmPqkAY9ph' .

Note: The username and password are altered, but contain the same type of characters as the username and password I use for the account in question, since after looking at the error it seems like the password encryption function fails with my username or password, so I figured providing credentials with the same character set could help with debugging the issue.
Anyway, running the command results in the following error:
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /home/marvin/.cargo/registry/src/github.com-1ecc6299db9ec823/gpapi-0.2.3/src/lib.rs:128:64
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

With Rust Backtrace:
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /home/marvin/.cargo/registry/src/github.com-1ecc6299db9ec823/gpapi-0.2.3/src/lib.rs:128:64
stack backtrace:
   0:     0x55aac0fef0c0 - std::backtrace_rs::backtrace::libunwind::trace::h34055254b57d8e79
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/../../backtrace/src/backtrace/libunwind.rs:90:5
   1:     0x55aac0fef0c0 - std::backtrace_rs::backtrace::trace_unsynchronized::h8f1e3fbd9afff6ec
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:     0x55aac0fef0c0 - std::sys_common::backtrace::_print_fmt::h3a99a796b770c360
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/sys_common/backtrace.rs:67:5
   3:     0x55aac0fef0c0 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h32d1f94a80615d18
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/sys_common/backtrace.rs:46:22
   4:     0x55aac101122c - core::fmt::write::h306731c068f7162c
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/core/src/fmt/mod.rs:1110:17
   5:     0x55aac0fe95e5 - std::io::Write::write_fmt::hd2fa90334eee2a21
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/io/mod.rs:1588:15
   6:     0x55aac0ff111b - std::sys_common::backtrace::_print::h5abaa2601a852287
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/sys_common/backtrace.rs:49:5
   7:     0x55aac0ff111b - std::sys_common::backtrace::print::h8d81445442bb638f
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/sys_common/backtrace.rs:36:9
   8:     0x55aac0ff111b - std::panicking::default_hook::{{closure}}::hcfe804496a9fa747
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/panicking.rs:208:50
   9:     0x55aac0ff0bf1 - std::panicking::default_hook::hbea8e3ccf2ba8901
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/panicking.rs:225:9
  10:     0x55aac0ff17e4 - std::panicking::rust_panic_with_hook::h7ee9e1a2d0f8975a
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/panicking.rs:622:17
  11:     0x55aac0ff1297 - std::panicking::begin_panic_handler::{{closure}}::h8ab3b4491718b2c7
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/panicking.rs:517:13
  12:     0x55aac0fef5bc - std::sys_common::backtrace::__rust_end_short_backtrace::hd489062ffa586a9f
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/sys_common/backtrace.rs:141:18
  13:     0x55aac0ff1229 - rust_begin_unwind
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/panicking.rs:515:5
  14:     0x55aac0b652e1 - core::panicking::panic_fmt::hca6330e3e14086b4
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/core/src/panicking.rs:92:14
  15:     0x55aac0b6522d - core::panicking::panic::h1a48d878ff3dcd40
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/core/src/panicking.rs:50:5
  16:     0x55aac0beb8ed - gpapi::Gpapi::login::{{closure}}::h6672c5a304ac6268
  17:     0x55aac0bf30d1 - <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h4de8fc0f50538533
  18:     0x55aac0c26779 - tokio::runtime::enter::Enter::block_on::h5a168d8b4a0b10b9
  19:     0x55aac0b9aedf - tokio::runtime::Runtime::block_on::h06014407f50a2936
  20:     0x55aac0bb6dda - apkeep::main::hbfb9de017ffc11c2
  21:     0x55aac0c779c3 - std::sys_common::backtrace::__rust_begin_short_backtrace::h8caefb424b900ce0
  22:     0x55aac0c77a19 - std::rt::lang_start::{{closure}}::h091082558be5e806
  23:     0x55aac0ff1de9 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h2aabc384aab89b7b
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/core/src/ops/function.rs:259:13
  24:     0x55aac0ff1de9 - std::panicking::try::do_call::hc5fcacb7a85fc7b1
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/panicking.rs:401:40
  25:     0x55aac0ff1de9 - std::panicking::try::hb5d9603af3abbe3a
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/panicking.rs:365:19
  26:     0x55aac0ff1de9 - std::panic::catch_unwind::h98fe6ac3925e64b4
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/panic.rs:434:14
  27:     0x55aac0ff1de9 - std::rt::lang_start_internal::h22ac7383c516f93e
                               at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/rt.rs:34:21
  28:     0x55aac0bb6ef2 - main
  29:     0x7f3f3ed910b3 - __libc_start_main
  30:     0x55aac0b65abe - _start
  31:                0x0 - <unknown>

System Specifications
OS: Ubuntu 20.04
Virtualization: KVM/QEMU
CPU: AMD EPYC-Rome (8) @ 3.593GHz
CPU Architecture: x86_64

I just experimented a bit and it seems to be related to the combined length of the username and password. If the combined character length of the username and password exceeds 86 the panic happens, anything below works without issues.

Interesting, thank you for the report.  I'll look into this / issue a fix next week.

The underlying error is encountered when calling https://docs.rs/openssl/0.10.36/openssl/rsa/struct.Rsa.html#method.public_encrypt

error:0409A06E:rsa routines:RSA_padding_add_PKCS1_OAEP_mgf1:data too large for key size:../crypto/rsa/rsa_oaep.c:62:

I guess we have to figure out how Google encrypts the login, and what padding to use when a large username/password combo is encountered.

This happens in the Python https://github.com/NoMore201/googleplay-api/ (which I've modeled the Rust google play API dependency on) as well.  Filed bug here: https://github.com/NoMore201/googleplay-api/issues/151

With https://github.com/EFForg/apkeep/commit/5a360edabb7656b8ec731d0de1e04e63c9bca6c3, the panic should no longer happen and a useful error message will display to the user.  This doesn't solve the underlying issue, though I'm not yet sure how.  I'd need to see documentation on how Google expects longer credentials to be encrypted.
Feel free to open another issue if you wish, though I can't do much about it.


Expose cpu/ram keys on Instance for Heapster stats

how an Instance looks now
{
  "id": "0",
  "base_name": "elasticsearch-0",
  "name": "elasticsearch-020160422134458",
  "status": "STARTED"
}

how an Instance will look
{
  "id": "0",
  "base_name": "elasticsearch-0",
  "name": "elasticsearch-020160422134458",
  "status": "STARTED",
  "cpu": {
    "usage": 2,
    "limit": 250
  },
  "ram": {
    "usage":<PHONE_NUMBER>,
    "limit":<PHONE_NUMBER>
  }
}

Coverage decreased (-0.1%) to 17.586% when pulling 516bfa4f6590c452d474c00b57d6e2cb914b0e66 on instance_stats into f00483d27e16217625e565704845510fabfbc38c on master.


Email error handling

Quietly fail when SMTP exceptions occur, logging the exceptions to Elmah, but continuing.

This is part of, but not all of Issue #140.  We'd still need to figure out why emails are failing from the preview site (or state that they should not be working at this point).

Ship it! I didn't realize MailMessage was disposable. Doh! :)


Generated interface resolvers seem to be too narrowly typed

Describe the bug
It’s possible I’m using the generated resolver types incorrectly, but I’m following Apollo’s javascript example for resolving graphql interfaces, and I’d expect to able to do something similar, but in typescript with graphql-code-generator; i.e., a resolver for an interface type should be able to determine what concrete type of the interface should be returned.
E.g. in js:
const resolvers = {
  Book: {
    __resolveType(parent, context, info){
      if(parent.classes){
        return 'TextBook';
      }

      if(parent.colors){
        return 'ColoringBook';
      }

      return null;
    },
  },
  …
};

Unfortunately, the generated typescript resolver doesn’t allow me to check what possible types it can be. parent is typed to Book which has no information about subtypes.  The typescript equivalent is below.
If there’s a different pattern I should be using, please let me know!
To Reproduce
Steps to reproduce the behavior:

My GraphQL schema:

interface Book {
  title: String
}

type TextBook implements Book {
  title: String
  cost: Float
}

type ColoringBook implements Book {
  title: String
  colors: [String]
}

My codegen.yml config file:

schema: "src/schema.graphql"
generates:
  src/types/server-graphql-types.ts:
    plugins:
      - typescript
      - typescript-resolvers:
        useIndexSignature: true

Generated code:

export type ResolversParentTypes = {
  Query: {};
  Book: Book;
  TextBook: TextBook;
  ColoringBook: ColoringBook;
  …
};

export type BookResolvers<
  ContextType = any,
  ParentType extends ResolversParentTypes[“Book”] = ResolversParentTypes[“Book”]
> = {
  __resolveType: TypeResolveFn<
    "TextBook" | "ColoringBook",
    ParentType, // Because Resolvers uses the default BookResolver type, ParentType is `ResolversParentTypes[“Book”]`
    ContextType
  >;
  title?: Resolver<
    ResolversTypes[“String”],
    ParentType,
    ContextType
  >;
};

export type Resolvers<ContextType = any> = {
  Book?: BookResolvers;
}

Expected behavior

I would expect to be able to do this:
const bookResolver: BookResolvers = {
  __resolveType(parent, _context, _info) {
      if (parent.__typename === "TextBook")
        return "TextBook";
      else if (parent.__typename === "ColoringBook") {
        return "ColoringBook";
      }

      return null;
    }
}

But __typename doesn’t exist on parent. Since ParentType is typed to ResolversParentTypes[“Book”], the only available field will be title.
Environment:

apollo-server: 2.9.16
@graphql-codegen/...: 1.12.2
NodeJS: 12.9.1

#3618

Fixed in v1.13.1 🎉


Light and Dark mode button

light and dark mode functionality. We can show it on first page for MVP purposes

Added!


How can a developer find messages between reviewer and developer for future reference?

The messages that are code and block specific don't seem to be easily retrievable using Azure Devops tool.   I need to see what those comments are from time to time without having to dig through emails to find the pertinent review.

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

ID: 6e0d4140-d512-8c58-0f35-dac14e355cdf
Version Independent ID: b1dc4511-a1f5-0b0e-1af0-9bc2b177fb35
Content: Suspend work, fix a bug, and conduct a code review - Azure Repos
Content Source: docs/repos/tfvc/day-life-alm-developer-suspend-work-fix-bug-conduct-code-review.md
Product: devops
Technology: devops-code-tfvc
GitHub Login: @apawast
Microsoft Alias: sdanie

@fordunka Thank you for the feedback.
Please see if this post addresses your issue.
Else, you will need to start a new thread with the product team here.

Closing the issue now, please comment below if there are any questions.


Is there an existing issue for this?

[X] I have searched the existing issues

Description
test
Steps To Reproduce
test
Public Sample App
No response
Environment
Production
Severity
Low (Inconsistent UI/UX)
Issue video log
No response
Version
Cloud

Closing this as it does not have an appropriate label associated with a pod


deps: Move com_googlesource_googleurl top-level BUILD file to a sub-dir

When trying to use GURL as URL parser (a minimal initial integration effort (PoC on linking) of it can be observed in https://github.com/envoyproxy/envoy/pull/11670), I faced the following error on macOS and Windows:
ERROR: An error occurred during the fetch of repository 'com_googlesource_googleurl':
   java.io.IOException: Error extracting

Since from the downloaded archive, http_archive tries to extract build dir while the BUILD file is already extracted (the case for BUILD file is extracted before the build directory from the tarball or vice-versa) hence http_archive throws an error. It happens only for systems with a case-insensitive filesystem e.g. used by Windows and macOS.
Currently, I used a temporary repackaged archive (by renaming BUILD to BUILD.bazel).
cc. @danzh2010 @htuch
Previous discussion: https://github.com/envoyproxy/envoy/pull/10599#discussion_r402638477.
$ ls -la /private/var/tmp/_bazel_dio/ec97df638f335f38ea0eb318d327853e/external/com_googlesource_googleurl/
total 736
drwxr-xr-x    9 dio  wheel     288 Jun 20 13:19 .
drwxr-xr-x  207 dio  wheel    6624 Jun 20 13:19 ..
-rw-r--r--    1 dio  wheel   43267 Mar 25 01:17 AUTHORS
-rw-r--r--    1 dio  wheel       8 Mar 25 01:17 BUILD
-rw-r--r--    1 dio  wheel    1559 Mar 25 01:17 LICENSE
-rw-r--r--    1 dio  wheel     908 Mar 25 01:17 README.md
-rw-r--r--    1 dio  wheel     204 Mar 25 01:17 WORKSPACE
drwxr-xr-x   12 dio  wheel     384 Jun 20 13:19 base
-rw-r--r--    1 dio  wheel  314942 Jun 20 13:19 googleurl_dbf5ad147f60afc125e99db7549402af49a5eae8.tar.gz

Complete error log on macOS on CI:
  2020-06-21T06:41:59.7730360Z INFO: Repository com_googlesource_googleurl instantiated at:
2020-06-21T06:41:59.7745840Z   no stack (--record_rule_instantiation_callstack not enabled)
2020-06-21T06:41:59.7746720Z Repository rule http_archive defined at:
2020-06-21T06:41:59.7747550Z   /private/var/tmp/_bazel_runner/b961792e7cffa44c65ef18ea8508602b/external/bazel_tools/tools/build_defs/repo/http.bzl:336:16: in <toplevel>
2020-06-21T06:41:59.7823820Z ERROR: An error occurred during the fetch of repository 'com_googlesource_googleurl':
2020-06-21T06:41:59.7825520Z    java.io.IOException: Error extracting /private/var/tmp/_bazel_runner/b961792e7cffa44c65ef18ea8508602b/external/com_googlesource_googleurl/googleurl_dbf5ad147f60afc125e99db7549402af49a5eae8.tar.gz to /private/var/tmp/_bazel_runner/b961792e7cffa44c65ef18ea8508602b/external/com_googlesource_googleurl: /private/var/tmp/_bazel_runner/b961792e7cffa44c65ef18ea8508602b/external/com_googlesource_googleurl/build (Not a directory)

Can we fix GURL upstream to make it compatible with Bazel? This seems like something they would likely accept.

@htuch do you mean against https://src.chromium.org/viewvc/chrome/trunk/src/url/? I think what we have right now is a snapshot. I'm not sure about the procedure. I can observe copyright of Chromium Authors for BUILD file here: https://github.com/dio/googleurl/blob/4d7b1f126466ef48b3fe148d08db73385721adf7/build/BUILD#L1 But I'm afraid I couldn't search that on any public repos.


Bug in com.azure:azure-identity since 1.4.0 causing AccessToken to appear expired in AccessTokenCache

After upgrade the version of the azure-identity-spring from version 1.8.0 to 1.10.0 we got the problem that sugested the access token would expire immediately. The reason for that ist the change in the MSIToken class in this changeset:
https://github.com/Azure/azure-sdk-for-java/commit/3b57be8364e18f7c23f14323508761a1688ded94
@JsonProperty(value = "expires_on")
@JsonAlias("expires_in")
private String expiresOn;
The added annotation maps the wrong field from the JSON token expires_in to the atribute expiresOn. So the Values is somewhat in the year 1970 which is already expired.
Logs:
...
15.11.2021 12:34:07.555 [ INFO] [main] AzureManager - Fetching EventHubNamespace with name '' ...
15.11.2021 12:34:08.757 [ INFO] [main] ManagedIdentityCredential - Azure Identity => Managed Identity environment: AZURE VM IMDS ENDPOINT
15.11.2021 12:34:08.758 [ INFO] [main] ManagedIdentityCredential - Azure Identity => getToken() result for scopes [https://management.core.windows.net//.default]: SUCCESS
15.11.2021 12:34:08.758 [ INFO] [main] ChainedTokenCredential - Azure Identity => Attempted credential ManagedIdentityCredential returns a token
15.11.2021 12:34:08.759 [ INFO] [main] AccessTokenCache - Acquired a new access token.
15.11.2021 12:34:12.778 [ INFO] [main] AzureManager - Fetching EventHubNamespace with name '' finished in 5 seconds
15.11.2021 12:34:38.796 [ INFO] [parallel-1] ManagedIdentityCredential - Azure Identity => Managed Identity environment: AZURE VM IMDS ENDPOINT
15.11.2021 12:34:38.797 [ INFO] [parallel-1] ManagedIdentityCredential - Azure Identity => getToken() result for scopes [https://management.core.windows.net//.default]: SUCCESS
15.11.2021 12:34:38.798 [ INFO] [parallel-1] ChainedTokenCredential - Azure Identity => Attempted credential ManagedIdentityCredential returns a token
15.11.2021 12:34:38.798 [ INFO] [parallel-1] AccessTokenCache - Acquired a new access token at<PHONE_NUMBER> seconds after expiry. Retry may be attempted after 30 seconds.
15.11.2021 12:35:08.820 [ INFO] [parallel-1] ManagedIdentityCredential - Azure Identity => Managed Identity environment: AZURE VM IMDS ENDPOINT
15.11.2021 12:35:08.821 [ INFO] [parallel-1] ManagedIdentityCredential - Azure Identity => getToken() result for scopes [https://management.core.windows.net//.default]: SUCCESS
15.11.2021 12:35:08.821 [ INFO] [parallel-1] ChainedTokenCredential - Azure Identity => Attempted credential ManagedIdentityCredential returns a token
15.11.2021 12:35:08.821 [ INFO] [parallel-1] AccessTokenCache - Acquired a new access token at<PHONE_NUMBER> seconds after expiry. Retry may be attempted after 30 seconds.
15.11.2021 12:35:09.676 [ INFO] [main] AzureManager - Fetching StorageAccount with name '' ...
15.11.2021 12:35:38.843 [ INFO] [parallel-1] ManagedIdentityCredential - Azure Identity => Managed Identity environment: AZURE VM IMDS ENDPOINT
15.11.2021 12:35:38.843 [ INFO] [parallel-1] ManagedIdentityCredential - Azure Identity => getToken() result for scopes [https://management.core.windows.net//.default]: SUCCESS
15.11.2021 12:35:38.844 [ INFO] [parallel-1] ChainedTokenCredential - Azure Identity => Attempted credential ManagedIdentityCredential returns a token
15.11.2021 12:35:38.844 [ INFO] [parallel-1] AccessTokenCache - Acquired a new access token at<PHONE_NUMBER> seconds after expiry. Retry may be attempted after 30 seconds.
15.11.2021 12:35:39.352 [ INFO] [main] AzureManager - Fetching StorageAccount with name '' finished in 29 seconds
15.11.2021 12:36:08.863 [ INFO] [parallel-1] ManagedIdentityCredential - Azure Identity => Managed Identity environment: AZURE VM IMDS ENDPOINT
15.11.2021 12:36:08.863 [ INFO] [parallel-1] ManagedIdentityCredential - Azure Identity => getToken() result for scopes [https://management.core.windows.net//.default]: SUCCESS
15.11.2021 12:36:08.863 [ INFO] [parallel-1] ChainedTokenCredential - Azure Identity => Attempted credential ManagedIdentityCredential returns a token
15.11.2021 12:36:08.864 [ INFO] [parallel-1] AccessTokenCache - Acquired a new access token at<PHONE_NUMBER> seconds after expiry. Retry may be attempted after 30 seconds.
15.11.2021 12:36:08.952 [ INFO] [main] EventHubTemplate - Started EventHubTemplate with properties: {checkpointConfig=CheckpointConfig{checkpointMode=RECORD, checkpointCount=0, checkpointInterval=null}, startPosition=LATEST}
15.11.2021 12:36:09.388 [ INFO] [main] FunctionConfiguration$FunctionBindingRegistrar - Functional binding is disabled due to the presense of @EnableBinding annotation in your configuration
15.11.2021 12:36:09.456 [ INFO] [main] BeanFactoryAwareFunctionRegistry - Looking up function 'supply' with acceptedOutputTypes: []
15.11.2021 12:36:10.162 [ INFO] [main] EndpointLinksResolver - Exposing 1 endpoint(s) beneath base path '/actuator'
15.11.2021 12:36:10.479 [ INFO] [main] EventDrivenConsumer - Adding {logging-channel-adapter:_org.springframework.integration.errorLogger} as a subscriber to the 'errorChannel' channel
15.11.2021 12:36:10.480 [ INFO] [main] PublishSubscribeChannel - Channel 'ScanService.errorChannel' has 1 subscriber(s).
Here is the test which proves that the worn value is taken:
public class MSITokenTest {
private static final SerializerAdapter SERIALIZER_ADAPTER = JacksonAdapter.createDefaultSerializerAdapter();
private static String result = "{\n" +
"  "access_token": "eyJ0eXAi...",\n" +
"  "refresh_token": "",\n" +
"  "expires_in": "3599",\n" +
"  "expires_on": "1506484173",\n" +
"  "not_before": "1506480273",\n" +
"  "resource": "https://management.azure.com/\",\n" +
"  "token_type": "Bearer"\n" +
"}";
@Test
public void msiTokenTest() throws IOException {
MSIToken msiToken = SERIALIZER_ADAPTER.deserialize(result, MSIToken.class, SerializerEncoding.JSON);
//Assertions.assertEquals(OffsetDateTime.MAX, msiToken.getExpiresAt());
System.out.println("msiToken: " +msiToken.getExpiresAt());
    MSITokenNoAnnotation msiTokenNoAnnotation = SERIALIZER_ADAPTER.deserialize(result, MSITokenNoAnnotation.class, SerializerEncoding.JSON);
    //Assertions.assertEquals(OffsetDateTime.MAX, msiTokenNoAnnotation.getExpiresAt());
    System.out.println("msiTokeNoAnnotation" + msiTokenNoAnnotation.getExpiresAt());
}

}
The second class a copy of MSIToken without the added annotation:
public final class MSITokenNoAnnotation extends AccessToken {
private static final OffsetDateTime EPOCH = OffsetDateTime.of(1970, 1, 1, 0, 0, 0, 0, ZoneOffset.UTC);
@JsonProperty(value = "token_type")
private String tokenType;

@JsonProperty(value = "access_token")
private String accessToken;

@JsonProperty(value = "expires_on")
//@JsonAlias("expires_in")
private String expiresOn;

/**
 * Creates an access token instance.
 *
 * @param token the token string.
 * @param expiresOn the expiration time.
 */
@JsonCreator
public MSITokenNoAnnotation(
    @JsonProperty(value = "access_token") String token,
    @JsonProperty(value = "expires_on") String expiresOn) {
    super(token, EPOCH.plusSeconds(parseDateToEpochSeconds(expiresOn)));
    this.accessToken = token;
    this.expiresOn =  expiresOn;
}

@Override
public String getToken() {
    return accessToken;
}

private static Long parseDateToEpochSeconds(String dateTime) {
    ClientLogger logger = new ClientLogger(MSITokenNoAnnotation.class);
    DateTimeFormatter dtf = DateTimeFormatter.ofPattern("M/d/yyyy H:mm:ss XXX").withLocale(Locale.US);
    // This is the format for app service on Windows as of API version 2017-09-01.
    // The format is changed to Unix timestamp in 2019-08-01 but this API version
    // has not been deployed to Linux app services.
    DateTimeFormatter dtfWindows = DateTimeFormatter.ofPattern("M/d/yyyy h:mm:ss a XXX").withLocale(Locale.US);
    try {
        return Long.parseLong(dateTime);
    } catch (NumberFormatException e) {
        logger.verbose(e.getMessage());
    }

    try {
        return Instant.from(dtf.parse(dateTime)).getEpochSecond();
    } catch (DateTimeParseException e) {
        logger.verbose(e.getMessage());
    }

    try {
        return Instant.from(dtfWindows.parse(dateTime)).getEpochSecond();
    } catch (DateTimeParseException e) {
        logger.verbose(e.getMessage());
    }

    throw logger.logExceptionAsError(new IllegalArgumentException("Unable to parse date time " + dateTime));
}

}
The error appears in the AccessTokenCache class wherre the token is validating if it is allready expired (method retrieveToken)
Java version 15.0.2

Thank you for reporting the issue, @g2vinay can you please investigate.

@rudolfbartel Thank you for reporting this issue.
I am investigating this issue and will update here soon.

@g2vinay Cool, thx

@rudolfbartel
This issue should be fixed in 1.4.2 version of azure-identity.
You can upgrade to that version.
Let me know if you see any other problems and we can reopen this issue.

@g2vinay
Thanks a lot
Yes, I did a test run, so it looks very good. Since this is a transient dependency of azure-identity-spring when this dependency will be adjusted?


Use DASK to iteratively parallelise the data loading and analyse large runs

Modify the atmorep_read_data interface to run with DASK arrays that can be easily parallelised.
Bottleneck at the moment: we run out of memory when reconstructing more than 45000 local samples. This means ~ 20 dates in global forecast.

parallel data loading prototype is finished, but missing features are:

[ ] target for global forecast
[ ] source for global forecast
[ ] ensemble for global forecast
[ ] other masking / forecast modes
[ ] baseline chunk loading performance comparison
[ ] debug dask issues on HPC
[ ] tune dask


refactor the code of the HashJoin

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
(This section helps Arrow developers understand the context and why for this feature, in addition to  the what)
From the bug #4247, there are bugs for hash join for right semi/anti join.
The current code base has many match path for each Join_type, each join_type has different logic and path, it easy to produce the bugs when we add feature in the HashJoin.
Proposal:
split vectorization HashJoin to three phase:

get the result of matched equal join : left_idx and right_idx
apply non_equal filter to left_idx and right_idx and get the filter_left_idx with filter_right_idx
according to the Join Type to construct the result

according to the matched `filter_left_idx` and `filter_right_idx` to get the result
match join_type{
   inner_join:
   left_join:
   right_join:
   full_join:
   left_semi: set the left bitmap
   left_anti:  set the left bitmap
   right_semi: set the right bitmap, and get the result from the right bitmap(set_bit)
   right_anti:: set the right bitmap, and get the result from the right bitmap(not_set_bit)
}

Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

After this merged https://github.com/apache/arrow-datafusion/pull/4355, I will start this task

Thanks @liukun4515 for driving the effort to improve the hash join implementation! Makes sense to me to structure it this way. This will help make it easier to change/improve the implementation later on.

The current code base has many match path for each Join_type, each join_type has different logic and path, it easy to produce the bugs when we add feature in the HashJoin.

Yes, I agree.

split vectorization HashJoin to three phase:

get the result of matched equal join : left_idx and right_idx
apply non_equal filter to left_idx and right_idx and get the filter_left_idx with filter_right_idx
according to the Join Type to construct the result

For HashJoin, there are two big phases: build and probe:

For build phase, we don't care JoinType almost

For probe phase, JoinType is the direction.  So how about spitting match paths at the beginning of probe phase
 match join_type {
     inner => probe_inner_join(),
     left => probe_left_join(),
     ....
 }

In each probe method, we can process non-equi conditions and equi conditions. Non-equi conditions's results depend on JoinType

Probe phase has many common stage.
In the vectorization has join, the first stage is to get the left/right indices which are match the on join condition.
Next, use the left/right indices to generate the batch result according to the join type. But some special join type should maintain the left side bitmap to generate the result finally, for example left/full/leftanti/leftsemi.


[TF2.2] Mixed Ragged and tensors inputs breaks function tensors spec names

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): linux
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): tf2.2 rc3
TensorFlow version (use command below):2.2 rc3 collab
Python version: google collab
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

Describe the current behavior
I'm trying to save a model with two inputs:

one ragged
one tensor

both are embedded into a 3 dim vector and then summed up together. If we save that model it breaks because the tensors names are not well defined.
inp_tensor = Input(shape=[], ragged=False, dtype=tf.int32)
inp_ragged = Input(shape=[None, ], ragged=True, dtype=tf.int32, name='test')

out = Embedding(10, 3)(inp_tensor)
out2 = Embedding(10, 3)(inp_ragged)
out2 = Lambda(tf.reduce_sum, arguments=dict(axis=1))(out2)
summed = Add()([out, out2])
m = Model([inp_tensor, inp_ragged], summed)
m.save('/tmp/test')

ValueError: If specifying TensorSpec names for nested structures, either zero or all names have to be specified.

If we debug we find out that the non ragged tensor has a name while the two others have name=None. I tried to name the ragged_input to fix that but the issue stays the same.
/usr/local/lib/python3.6/dist-packages/tensorflow/python/framework/func_graph.py(1196)_get_defun_inputs()
   1194     specified_names = [arg.name for arg in tensor_specs if arg.name]
   1195     if specified_names and len(specified_names) < len(tensor_specs):
-> 1196       raise ValueError("If specifying TensorSpec names for nested structures, "
   1197                        "either zero or all names have to be specified.")
   1198

ipdb> specified_names
['inputs/0']
ipdb> tensor_specs
[TensorSpec(shape=(None,), dtype=tf.int32, name='inputs/0'), TensorSpec(shape=(None,), dtype=tf.int32, name=None), TensorSpec(shape=(None,), dtype=tf.int64, name=None)]

Describe the expected behavior
We should be able to save that model, the same model with two ragged inputs can be saved !
Standalone code to reproduce the issue
https://colab.research.google.com/gist/tanguycdls/200096266d1cb0c5a6c83cbb416c1279/untitled4.ipynb

I tried in colab with TF 2.1 and i am not seeing any issue. However i am able to reproduce the issue in colab with TF 2.2.0-rc3. Please, find the gist here.Thanks!

Facing same issue with 2.2.0

@shkarupa-alex seems to be fixed in the latest tf-nightly :) !
https://colab.research.google.com/gist/tanguycdls/200096266d1cb0c5a6c83cbb416c1279/untitled4.ipynb#scrollTo=qWJanvalyxiJ
I'm going to do some thorough tests to be sure.

@shkarupa-alex Agree with @tanguycdls . Looks like this was resolved in tf-nightly. Please take a look at the gist. Thanks!
Please verify once and close the issue if this was resolved for you. Thanks!

Yes, it's working now

I am closing this issue as this was resolved. Thanks for the confirmation.

fyi closed by that commit: https://github.com/tensorflow/tensorflow/commit/d1a6976039c769423814f690661fd2c1b471b08c


[Go Live][Apr 24]

Push to live

Docs Build status updates of commit 2649912:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.vscode/settings.json
:white_check_mark:Succeeded

msteams-platform/assets/images/teams-toolkit-v2/first-msgext/hw-folder-structure-mex.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/first-tab/hw-folder-structure-tab.png
:white_check_mark:Succeeded

msteams-platform/assets/images/teams-toolkit-v2/first-tab/hw-folder-structure-tab1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-23.png
:white_check_mark:Succeeded
View

msteams-platform/sbs-gs-javascript.yml
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-SDK.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


v0.0.1-alpha10 same as v0.0.1-alpha09

Has anyone else seen this? I recently updated my build.gradle implementation to the newest version and when I rebuild the project/perform gradle sync, I see the alpha10 library in my project, but checking out the source reveals the files are in the same state as they were in the alpha09 version.

Some screenshots of the project and the files that I saw were modified in the release notes but seemed to not be modified in the new alpha10 package.
Checking the maven repo shows alpha10 being the latest version too so a little confused here.

Not sure about your comparison criteria but neither DefaultParam nor AndroidClockFactory were changed in the v0.0.1-alpha10. At least it seems so from the diff.

Yup I figured this had to be my fault. When looking at the latest release, there is a link to commits that have happened since this release and I was looking at that diff. My apologies and thanks for the response!


fix: QnA authoring issue

Description
Remove duplicate pre-created resource from bot template.

Task Item
close #4512

Screenshots

Coverage remained the same at 55.065% when pulling bc6423a6c9b72ab22355510aededda21a2a95b0d on zhixzhan/qna-fix into 83c08046a8f6969da1ee70fad6d22c5f9961c51e on main.

Besides fixing the pre-setup of the bot sample, we also need to update the logic to avoid creating duplicate trigger by default, right?

Besides fixing the pre-setup of the bot sample, we also need to update the logic to avoid creating duplicate trigger by default, right?

Yes, I asked Lu, we don't need create duplicate trigger every time, I'm going to revert changes in bot sample, add a check before create trigger.

Besides fixing the pre-setup of the bot sample, we also need to update the logic to avoid creating duplicate trigger by default, right?

Yes, I asked Lu, we don't need create duplicate trigger every time, I'm going to revert changes in bot sample, add a check before create trigger.

I still removed the pre-created code from sample bot,  that will keep new created bot always fresh.

@zhixzhan can you provide a more descriptive title for this pull request?

@zhixzhan can you provide a more descriptive title for this pull request?

Sure, updated, sorry for that.


feat: RDS variableMap support

Addresses Issue https://github.com/bboure/serverless-appsync-simulator/issues/120
by providing RelationaDataLoader with a simple variableMap injector.

CC: @alichherawalla

@bboure 🚀

@all-contributors add @katesclau  and @alichherawalla for code

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Mysql 5.5 default CURRENT_TIMESTAMP not work

In the "skusku_cart" table the default field value "CURRENT TIMESTAMP" not work in you have 5.5 mysl version or lower.

fixed in ec8ed6f


[terminal] Fixes VT sequence OESC 4 to also support setting color via #RRGGBB and #RGB.

Adds support for setting color via OSC 4 ; INDEX ; #RRGGBB ST. This format is also supported by XParseColor and at least one application is making use of it (kfc).
Thanks @subnut for the hint.
Reference: https://github.com/contour-terminal/contour/issues/221#issuecomment-1025982122

Will it be possible to add #RGB too?

Will it be possible to add #RGB (e.g. #FFF for white) too? It also seems to be common.

I added that too (and tests). just after I have read you on Discord and before I've read you in here. :-)

setting via #RGB will shift the 4-bit value 4 bits to the left and dup it. so OSC 4 ; 7 ; #abc ST is equivalent to OSC 4 ; 7 ; #aabbcc ST. So your cases above are covered, too.


feat(2890253029): display chain name on wallet button

Description of the Changes
Please add a detailed description of the change, whether it's an enhancement or a bugfix.
If the PR is related to an open issue please link to it.
Checklist

[ ] Changes have been done against master branch, and PR does not conflict
[ ] New unit / functional tests have been added (whenever applicable)
[ ] Test are passing in local environment
[ ] Docs have been updated
[ ] PR title is follow the Conventional Commits convention: <type>[optional scope]: <description>, e.g: fix: prevent racing of requests

This change is

:tada: This PR is included in version 1.6.0-dev.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


fix(package): Include typescript source

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add a Vim9 script disassemble test for an interface with static members

I never learned vim's regex flavor in any detail. When I saw the \_s* yesterday, I had no idea what was going on. I dug a little deeper after seeing thisPR , finally found it, and had to read it a few times before I caught that \_ means include new line.
Is there a toolkit around to assist in tasks like converting disassemble output to a test? I wouldn't be surprised if there's a slew of things like that; maybe hiding on Bram's system. Speaking of which, there's the convention where follow on lines of function args are shifted to the right until they almost bump into the end. Is there a format/indent setting/option for that?


Feature/OperationHealth

Full-scale refactoring of existing code to match Java best practices.
Complete Javadoc documentation with consistent style.
Cleaner comments across the project.
Warnings cleanup.
Typos cleanup.

Addressing requested changes


Request: Could the Windows DLL versions without installer be delivered in ZIP format?

@JeromeMartinez Could the DLL versions without installer be delivered in ZIP format?
The reason of a such request is that Maven plugins, not sure about Gradle plugin, support natively TAR, ZIP, GZ but 7Z is not.
So it should be more simple for the projects to get an updated version directly from your site as soon as it is available also if the project got not maintained anymore..
Regards

Idea behind 7z usage is to lower disk and network usage, having 7z+ZIP increases disk usage, having only IP increases network usage.
How "get updated"? do you mean Maven scripts can download, unpack and put the DLL at the right place?

Yes.
I didn't intended to support the 2 format for the DLL versions without installer, only ZIP but it add 2MB for the 2 files.
So it depend on the download frequency of these files and i will forget about it if that make your bandwidth usage grow up.
I was just hoping that these DLL versions was not downloaded a lot but my assumption could be totally wrong.

No worry if it is an issue for you, as we could always continue to kept the version used in a repository like Sourceforge or Bintray without problem. I was just wondering.
Call it a "questionnable request" 😉

Reopened because the request makes sense, was just asking for more details about how it would be used.

The idea was that our build system would download, unpack and deploy the library in the correct location in our "binary bundle".
I objected however, because I don't want the builds to link to things that we don't know will stay there "forever". I've been bitten by this too many times: if you need to build an old version for some reason and check out an old commit/tag, the build fails because some of the URL's aren't valid anymore. That can be a real hassle to get around, and chances are that the person trying to build doesn't even know enough the build system to fix it.
According to @Sami32 you delete old versions when you need the disk space, which is perfectly understandable, but it would mean that older builds would fail. Therefore I think it's better that we host the binaries somewhere were links are "guaranteed" to remain valid.
The ideal solution would probably have been to store them somewhere like the archive.org Open Source Software Collection.

@nadahar Sorry, it seem that i was wrong. I just discovered that link:
https://mediaarea.net/download/binary/libmediainfo0/
Until now did only knew the SNAPSHOT one and the VideoHelp one that keep trace of the GUI versions only with rare exceptions.
So i discovered at the same time that the DLL JavaScript versions was alreadly using the ZIP format.

Enable ZIP creation in source code, release engine, download page update (for next release).

Thank you very much :smiley:
Have a nice day.

As a side note, the License.html file found here and there are 4 years old outdated.
There are fine in https://mediaarea.net/download/binary/libmediainfo0/.

I objected however, because I don't want the builds to link to things that we don't know will stay there "forever".

We try to keep it "forever", we would break this rule only if we have a very good reason to do so.

According to @Sami32 you delete old versions when you need the disk space,

We move them from our CDN, but links stay same, so no issue on your side (a bit slower than before but I think you would not care about losing few hundreds of milliseconds in that case).

@JeromeMartinez Thanks for the info. That changes things. The download speed for old builds are of importance, I don't expect it to be a frequent even.

As a side note, the License.html file found here and there is 4 years old outdated.

Fixed, thanks for report.


build: upgrade yarn to v4.1.1, upgrade dependency minor versions

Summary
Upgrades the version of Yarn from 4.0.2 to 4.1.1 and updates the engines field in package.json
Added

n/a

Changed

.yarn/releases/*
added .yarnrc.yml to .prettierignore since it is auto-generated

Deprecated
n/a
Removed
n/a
Fixed
n/a
How to test

yarn to install dependencies

Closing to split into multiple PRs