Additional values in "set" section of azds.yaml don't seem to be passed to helm charts

Hi
I have a azds.yaml file with following  set section:
install:
  set:
    replicaCount: 1
    image:
      tag: $(tag)
      pullPolicy: Never
    ingress:
      annotations:
        kubernetes.io/ingress.class: traefik-azds
      hosts:
      # This expands to [space.s.]webmvc.<guid>.<region>.aksapp.io
      - $(spacePrefix)webmvc$(hostSuffix)
    inf:
      k8s:
        dns: $(spacePrefix)webmvc$(hostSuffix)

I access to Values.inf.k8s.dns in my helm chart templates, but when launched using azds up the values are not received. If launched helm direcly from CLI with --set inf.k8s.dns=foo.bar everything works as expected.
I have following version of azds CLI:
Azure Dev Spaces CLI (Preview)
0.1.20190228.12
API v2.15

Thanks!

Thanks @eiximenis for reporting the issue. We are working on the fix. Meanwhile you can create a separate values files beside azds.yaml with the section
inf:       k8s:         dns: $(spacePrefix)webmvc$(hostSuffix)
and update the install section of the azds.yaml to include the path of this value file
install:
  values:
  - <New value file name>.yaml

Ok @jikuma!
Unfortunately do not work because it seems that the $(...) expansion do not work outside azds.yaml :(
Thanks!

@eiximenis This should be fixed in the newest version of the CLI (0.1.20190320.5)

@YuzorMa
Tested with 0.1.20190320.5 and it works :)
Closing the issue!

Is it supposed to also work for the values.dev.yaml referenced from the azds.yaml?  I'm not seeing any expansion to $(...) in those files.
My version is:
Azure Dev Spaces CLI
1.0.20190423.8
API v3.2

Currently, variables are only expanded in azds.yaml. I will take this as a feature request

Thank you @jikuma .  I'd appreciate the feature.  I'll just place move the properties with expressions into the azds.yaml for now.


feat: implement row_number window function

The row_number test is failing here but not on my local box.  Any idea what dependencies might be different that Datafusion uses?

The row_number test is failing here but not on my local box. Any idea what dependencies might be different that Datafusion uses?

hmm....i'm not aware of any.  this also passes when i try running locally on my mac


Add issues support to Pulldasher

Makes Pulldasher support receiving information about issues and writing
that information to the database. This allows analysis of issues with
SQL.

Connects #7

deploy_block :+1:  on #8

Connects #7

This looks good to me, just need to see how bad the merge conflict is.

Let's make this happen!

Bam:

merge unconflicted
extracted some logic into a module.
Made some runnable scripts to refresh issues

CR :fire:

un_deploy_block 👍


Fix comment typo in Package.swift

It seems to me that libSwiftPMDataModel instead of libSwiftPM was meant in this context.

@swift-ci please smoke test

Yes, that's correct — it should have been libSwiftPMDataModel.  Thanks for fixing it!


_googleSignIn.signInSilently() is not working

I have copy pasted the whole code from https://pub.dev/packages/google_sign_in#-example-tab- but still I am getting the following error on _googleSignIn.signInSilently()
Exception has occurred.
PlatformException (PlatformException(sign_in_required, com.google.GIDSignIn, The operation couldn’t be completed. (com.google.GIDSignIn error -4.)))

Please have a look into below mentioned code snippet for main.dart file
// Copyright 2019 The Flutter Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

// ignore_for_file: public_member_api_docs

import 'dart:async';
import 'dart:convert' show json;

import "package:http/http.dart" as http;
import 'package:flutter/material.dart';
import 'package:google_sign_in/google_sign_in.dart';

GoogleSignIn _googleSignIn = GoogleSignIn(
  scopes: <String>[
    'email',
    'https://www.googleapis.com/auth/contacts.readonly',
  ],
);

void main() {
  runApp(
    MaterialApp(
      title: 'Google Sign In',
      home: SignInDemo(),
    ),
  );
}

class SignInDemo extends StatefulWidget {
  @override
  State createState() => SignInDemoState();
}

class SignInDemoState extends State<SignInDemo> {
  GoogleSignInAccount _currentUser;
  String _contactText;

  @override
  void initState() {
    super.initState();
    _googleSignIn.onCurrentUserChanged.listen((GoogleSignInAccount account) {
      setState(() {
        _currentUser = account;
      });
      if (_currentUser != null) {
        _handleGetContact();
      }
    });
    _googleSignIn.signInSilently();
  }

  Future<void> _handleGetContact() async {
    setState(() {
      _contactText = "Loading contact info...";
    });
    final http.Response response = await http.get(
      'https://people.googleapis.com/v1/people/me/connections'
      '?requestMask.includeField=person.names',
      headers: await _currentUser.authHeaders,
    );
    if (response.statusCode != 200) {
      setState(() {
        _contactText = "People API gave a ${response.statusCode} "
            "response. Check logs for details.";
      });
      print('People API ${response.statusCode} response: ${response.body}');
      return;
    }
    final Map<String, dynamic> data = json.decode(response.body);
    final String namedContact = _pickFirstNamedContact(data);
    setState(() {
      if (namedContact != null) {
        _contactText = "I see you know $namedContact!";
      } else {
        _contactText = "No contacts to display.";
      }
    });
  }

  String _pickFirstNamedContact(Map<String, dynamic> data) {
    final List<dynamic> connections = data['connections'];
    final Map<String, dynamic> contact = connections?.firstWhere(
      (dynamic contact) => contact['names'] != null,
      orElse: () => null,
    );
    if (contact != null) {
      final Map<String, dynamic> name = contact['names'].firstWhere(
        (dynamic name) => name['displayName'] != null,
        orElse: () => null,
      );
      if (name != null) {
        return name['displayName'];
      }
    }
    return null;
  }

  Future<void> _handleSignIn() async {
    try {
      await _googleSignIn.signIn();
    } catch (error) {
      print(error);
    }
  }

  Future<void> _handleSignOut() => _googleSignIn.disconnect();

  Widget _buildBody() {
    if (_currentUser != null) {
      return Column(
        mainAxisAlignment: MainAxisAlignment.spaceAround,
        children: <Widget>[
          ListTile(
            leading: GoogleUserCircleAvatar(
              identity: _currentUser,
            ),
            title: Text(_currentUser.displayName ?? ''),
            subtitle: Text(_currentUser.email ?? ''),
          ),
          const Text("Signed in successfully."),
          Text(_contactText ?? ''),
          RaisedButton(
            child: const Text('SIGN OUT'),
            onPressed: _handleSignOut,
          ),
          RaisedButton(
            child: const Text('REFRESH'),
            onPressed: _handleGetContact,
          ),
        ],
      );
    } else {
      return Column(
        mainAxisAlignment: MainAxisAlignment.spaceAround,
        children: <Widget>[
          const Text("You are not currently signed in."),
          RaisedButton(
            child: const Text('SIGN IN'),
            onPressed: _handleSignIn,
          ),
        ],
      );
    }
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
        appBar: AppBar(
          title: const Text('Google Sign In'),
        ),
        body: ConstrainedBox(
          constraints: const BoxConstraints.expand(),
          child: _buildBody(),
        ));
  }
}

I want to user firebase as my backend. But before doing so this itself is not working for me.
I could see https://stackoverflow.com/questions/54213860/flutter-google-sign-in-stay-logged-in : here also they are using the same technique.
Please see the following error for your convenience :

Hi @Soumya95
Testing the official example and signInSilently works fine
    _googleSignIn.signInSilently().then((value) => print('signInSilently'));

print
flutter: signInSilently

Make sure you've enable google sign in your authentication in firebase console and don't forget to add SHA-1 key from Authenticating Your Client

flutter doctor -v
[✓] Flutter (Channel dev, 1.19.0-1.0.pre, on Mac OS X 10.15.4 19E287, locale
    en-GB)
    • Flutter version 1.19.0-1.0.pre at /Users/tahatesser/Code/flutter_dev
    • Framework revision 456d80b9dd (3 days ago), 2020-05-11 11:45:03 -0400
    • Engine revision d96f962ca2
    • Dart version 2.9.0 (build 2.9.0-7.0.dev 092ed38a87)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/tahatesser/Code/SDK
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/SDK
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

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

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

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

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

[✓] Connected device (5 available)
    • Taha’s iPhone • 00008020-001059882212002E            • ios            •
      iOS 13.4.1
    • iPhone 11     • B00B6F4E-B1CE-44F3-B81E-3EC6D639B008 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-13-4 (simulator)
    • macOS         • macOS                                • darwin-x64     •
      Mac OS X 10.15.4 19E287
    • Web Server    • web-server                           • web-javascript •
      Flutter Tools
    • Chrome        • chrome                               • web-javascript •
      Google Chrome 81.0.4044.138

• No issues found!

Thank you

Hi @TahaTesser ,
As you could see I have enabled the google sign in form firebase

And I believe SHA-1 key is required only for android (as I could see in Authenticating Your Client). I am using only IOS simulator. Although  i have done it.
Please find the flutter doctor result :
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.17.0, on Mac OS X 10.15.4 19E287, locale en-IN)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
[✓] Android Studio (version 3.6)
[✓] VS Code (version 1.45.0)
[✓] Proxy Configuration

[✓] Connected device (1 available)

• No issues found!

Hi @Soumya95
Just tried to reproduce the iOS using example

Please make sure you've iOS setu done too and GoogleService-Info.plist file in runner
Thank you

Hi @TahaTesser ,
For me the issue is consistent after doing all setup you mentioned. When I run the app using flutter run it does not create any problem but when I start debug using vsCode the issue is still there. If you want I can share with you the whole code base as well. Over there you could see that I have done all the correct settings related to GoogleService-Info.plist
Regards,
Soumya Kanti.

Hi @Soumya95
Also no such issue in debug mode in VSC

Thank you

Hi @TahaTesser, I am also facing some what same issue. Scenario
1- First time opening App from installation, it is showing error on _googleSignIn.signInSilently();
2- Later on opening App again, it is working totally fine. (Only & only problem occuring 1st time).
Here is my code-
import 'package:flutter/material.dart';
import 'package:google_sign_in/google_sign_in.dart';
import 'dart:async';

GoogleSignIn _googleSignIn = GoogleSignIn(
  scopes: [
    'https://www.googleapis.com/auth/userinfo.email',
    'https://www.googleapis.com/auth/userinfo.profile',
  ],
);

class LoginPage extends StatefulWidget {
  @override
  _LoginPageState createState() => _LoginPageState();
}

class _LoginPageState extends State<LoginPage> {

  Future<void> _handleSignIn() async {
  try {
    await _googleSignIn.signIn();
  } catch (error) {
    print(error);
  }
}

  Future<void> _handleSignOut() => _googleSignIn.disconnect();

  GoogleSignInAccount _currentUser;

  @override
  void initState() {
    super.initState();
    _googleSignIn.onCurrentUserChanged.listen((GoogleSignInAccount account) {
      setState(() {
        _currentUser = account;
      });
    });
    _googleSignIn.signInSilently();
  }

  @override
  Widget build(BuildContext context) {
    if(_currentUser == null){
      return Scaffold(
        // code here
      );
    }
    else{
      return Scaffold(
        // code here
      );
    }
  }
}


Do we have plan to support ConfigMap

Hi,
Do we have plan to support ConfigMap such as in kubernetes.
I can create a resource to store my configs, of course. But it will be wonderful if we have a ConfigMap.

configmap should be provided by kube-apiserver, it's out-of-scope of an aggregated apiserver


Status active characteristic not available on switches

Describe The Bug:
During startup, when getting the switches for pause and schedule the service is sending an error the characteristic is not normally available. This has normally been avoided by the testCharacteristic method being called before attempting to add or get the characteristic.
To Reproduce:
Start up the plugin.
Expected behavior:
The characteristic should be added without the error.
Logs:
[Dobby@Pause@Status Active] Characteristic not in required or optional characteristic section for service Switch. Adding anyway.
[Dobby@Dobby@Status Active] Characteristic not in required or optional characteristic section for service Switch. Adding anyway.

Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.

Screenshots:

Environment:

Plugin Version:
Homebridge Version:
Node.js Version:
Operating System:

Related to #197


Close #268 - refactored entire benchmark program for TypeBox

@sinclairzx81 Refactored entire benchmark program and it would be very suitable for TypeBox.
Especially, concentrated on assertType() function and make it to occurs type error always. As you know, if assert only one object, measurement result would be weirdo because property access sequence of validator libraries are all different. Therefore, target values for the assertType() benchmark are wrapped by an Array.

@samchon Awesome!
Yeah, happy to see heaps of error data run for the assert test (as that would run invoke both .Check() and .Errors() and be a more comparable test overall). It think having error cases would also be able to highlight validation disparities across the libraries being run (which is a good REALLY good thing to help encourage validation alignment)
Nice work!
PS: You should totally consider setting up these benchmarks as a standalone project. Currently, only https://github.com/moltar/typescript-runtime-type-benchmarks exists in this space, and it only asserts on simple structures, and only for passing test cases. It also doesn't make distinctions between AOT, JIT and Dynamic validation. So there's room for innovation there.
Would be an awesome reference point for developers.

I'll make a new PR and will show how benchmark result has been changed.
Especially, the new benchmark program is extremely optimized for the JIT environment.
Therefore, dramatic enhancement on your TypeBox would be.


Fix ncon

remove linalg.operations.ncon
change ncon_interface.ncon to accept Tensor and backend arrays instead of Node and backend-arrays.

Codecov Report

Merging #819 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #819   +/-   ##
=======================================
  Coverage   98.44%   98.44%
=======================================
  Files         128      128
  Lines       21609    21600    -9
=======================================
- Hits        21273    21265    -8
+ Misses        336      335    -1

Impacted Files
Coverage Δ

tensornetwork/linalg/operations.py
96.15% <ø> (-0.31%)
:arrow_down:

tensornetwork/linalg/tests/test_operations.py
99.31% <100.00%> (ø)

tensornetwork/ncon_interface.py
96.57% <100.00%> (+0.38%)
:arrow_up:

tensornetwork/tests/ncon_interface_test.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update aa19367...eeb8751. Read the comment docs.


Change format

I want this type format:
2011-11-04 00:05:23.000 - 2011-11-04 00:05:23.014, executed in 14ms
https://github.com/jupyterlab/jupyterlab/issues/13953#issuecomment-1424647293
Can we configure this in easy way? Or can be done this settings around in options Jupyter nbextensions as #nbextensions_configurator?

Possible configuration would be really nice 👍

Thanks for the idea. We'd be happy to accept a PR that makes this opt-in.


Integrate sample notebooks with binder

[ ] update notebooks to work with data available via url
[ ] update converstion to percent format with validation
https://mybinder.org/

Done in OpenDP library


Error with initializer file content_security_policy

I am getting this error on a new project build:
app/config/initializers/content_security_policy.rb:20:in `<top (required)>': undefined local variable or method `_r' for main:Object (NameError)

Oops, that was a last minute rubocop failure.
How do things work if you replace: lambda(_r) {
With this: lambda(_) {

Working now - Thanks


Fix shellcheck warnings

Fix shellcheck warnings and remove erroneous tabs.

Thanks for the request @particleflux , I'm going to have to hold off on merging this until I can test it myself.


envoy: Handle rules with wildcard endpoint selectors

Signed-off-by: Romain Lenglet<EMAIL_ADDRESS>

@jrajahalme You can try cherry-picking the commit. I'm working on a unit test.

Does this mean that we will always have to ensure parity across NPDS vs. the internal Cilium policy engine?

@ianvernon Do you mean in terms of feature set? It can lag behind for now.

test-me-please

test-me-please

@jrajahalme I made a logical mistake re: the wildcard endpoint selectors handling. I can't just blindly return an empty remotePolicies list. Some of the identities may be rejected by a fromRequires. So I'm thinking of changing the function signatures to pass:

the map of all identities
the set of denied ingress identities
the set of denied egress identities

That way, I can still do the wildcard optimization in the case the set of denied identities is empty.

Implemented that new logic.

test-me-please

test-me-please


Fix sources not setting Event::transactional

Pull request
Description

Fix sources not setting Event::transactional
Ensure sinks only emit ack/fail insights when the event is transactional, so we spare some processing if it is not needed.
Fix kafka onramp origin_url not containing the partition id, although the docs state it should.

Related

Related Issues: fixes #868

Checklist

[x] The RFC, if required, has been submitted and approved
[x] Any user-facing impact of the changes is reflected in docs.tremor.rs
[ ] The code is tested
[x] Use of unsafe code is reasoned about in a comment
[x] Update CHANGELOG.md appropriately, recording any changes, bug fixes, or other observable changes in behavior
[x] The performance impact of the change is measured (see below)

Performance

main
transactionality

272.4MB/s
295.3 MB/s

Coverage decreased (-0.07%) to 81.852% when pulling 5e9d59b1bca4f765d5011bff8d2124ec752dc69b on transactionality into 19cf1239fe1becf8a97103de027f487fbc8647f9 on main.

I love it!!! 🚀 👍

I love it too. It'd be nicer if the coverage went up though 🤓
On Wed, 24 Mar 2021, 21:55 Heinz N. Gies, @.***> wrote:

[image: grafik]
https://user-images.githubusercontent.com/119093/112381990-916d6180-8ceb-11eb-9e3e-bcf77bbbd052.png
I love it!!! 🚀 👍
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tremor-rs/tremor-runtime/pull/870#issuecomment-806180195,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABX5MVL2T477MT4OE57PZ3TFJGUJANCNFSM4ZX6Y4NA
.

All jokes aside, I don't see any code that would explain a 20% perf improvement, any idea how it improved?

20mb/s in those numbers so 7.8%?
On Wed, 24 Mar 2021, 22:14 Heinz N. Gies, @.***> wrote:

All jokes aside, I don't see any code that would explain a 20% perf
improvement, any idea how it improved?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tremor-rs/tremor-runtime/pull/870#issuecomment-806190202,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABX5MUHUKHQ7TXQPMIKYX3TFJIZ3ANCNFSM4ZX6Y4NA
.

20mb/s in those numbers so 7.8%?

Ja too late for math, but I don't see then 7.8%  either so I'm curious :D

Seems to be local fluctuation due to whatever background noise through other processes on my machine. Also got a run on my branch with 255MB/s. Gonna do some more runs.

Jep, all noise, consider the throughput roughly the same for this benchmark.


Update meta.yaml

Resdk is now avalaible on Conda-Forge
https://github.com/conda-forge/resdk-feedstock

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@conda-forge-admin, please rerender

I'm also pretty positive that when this PR would be merged, https://github.com/conda-forge/catboost-feedstock/pull/83, this Orange3-Bioinformatics could be tested following the typical  testing method.
test:
  imports:
    - orangecontrib
    - orangecontrib.bioinformatics
  commands:
    - pip check
  requires:
    - pip

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

ping @conda-forge/orange3-bioinformatics

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I was asked to ping @conda-forge/orange3-bioinformatics and so here I am doing that.

ping @JakaKokosar

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender


Can I use this plug-in with PSTCollectionView?

Can I use this plug-in with PSTCollectionView?

That should be possible. I don't know of PSTCollectionView, but CSStickyHeaderFlowLayout is simply a layout object for UICollectionView. So if PSTCollectionView can use a UICollectionViewLayout object then probably yes.


Stable version

If the version is stable enough for production use, could you make a version tag following this format https://getcomposer.org/doc/02-libraries.md#tags

Let's use #174.


Templatize: remove slots when hiding children

Fixes #4977. When templatized content is hidden (via _showHideChildren) as in dom-if top level <slot> elements are now removed instead of being hidden. This ensures that assigned nodes are not displayed in false-y dom-if elements.

While it works, it does feel weird to remove these slots. Would this solution still work if you change the light dom nodes?


Support Hashtag Urls

It would be great if you also have a way to have Hashtag urls i.e instead of:
http://developit.github.io/
http://developit.github.io/active
http://developit.github.io/completed

it should be:
http://developit.github.io/#/
http://developit.github.io/#/active
http://developit.github.io/#/completed

I mean currently we have some companies where we develop some apps and their browsers won't work nicely with these native urls.

I'm definitely open to adding this, as a fallback when pushState is not available. Just need to make sure didn't add bloat, but it should be an issue.


PP-5779 (PATCH) Backfill force emit live and card brand label

Depends on https://github.com/alphagov/pay-connector/pull/1870.
Forces emission of PaymentCreated and PaymentDetailsEntered events. This will apply new schema to all Ledger events allowing transactions to be built with up to date info.
Key changes to HistoricalEventEmitter.java .

@kbottla thanks for the comments, have updated in https://github.com/alphagov/pay-connector/pull/1871/commits/3616035a48167f792d838db992b28a69f2b9abff


modify the year

Ⅰ. Describe what this PR does
modify the year in ./pkg/utils/webhook/generator/util.go
Ⅱ. Does this pull request fix one issue?

fixes #XXXX
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

/lgtm


Label collision error on not rendered tile

TANGRAM VERSION:
v0.14.2
ENVIRONMENT:
Its happening in all major browsers.
TO REPRODUCE THE ISSUE, FOLLOW THESE STEPS:
I am afraid, I wont be able to reproduce this issue on a live example, but I will try to describe it.
This is the error that happens: Tangram v0.14.2 [error]: Error for style group 'collision' for tile kne_label/18/145372/90245/18 canBePlaced. TypeError: Cannot read property 'layout' of undefined.
It brokes in function canBePlaced:
canBePlaced: function canBePlaced(object, tile) {
        var exclude = arguments.length > 2 && arguments[2] !== undefined ? arguments[2] : null;

        var label = object.label;  --> this is null
        var layout = object.label.layout; --> this is undefined
        ....

The function expect, there is always object.label, but but in some special case, object label is null, and then it throws 'cannot read property 'layout' of undefined.
We are displaying simple polygons with text label in the cetroid which is separate geometry. We have clickable functionality on polygons so when you click a polygon in map, it is highlighted programaticaly trough config and scene (basicaly just enabling different style for the same geometry filtered by the clicked id of polygon). The described error happens when you pan too quick and click in the map where there is still no tile data loaded. In this case canBePlaced function get null label.
Maybe its very specific error bound only to our functionality, but anyway I wanted to log it here, if someone else will experiece it. I have fixed it in our app by modifing tangram canBePlacecd by returning the function if label is null. For us its basicaly enoug, but It would be nice if you evaluate it as relevant issue and fix this case it in the library. Thanks.

Thank you for the report - it definitely sounds like a bug, as that property should never be missing as far as I'm aware of. But in order to debug, it would be very helpful to have a working example.
Do you have an example scene and map location you can post that exhibits this issue? If you prefer, you could send privately as well.

hi, I have managed to create a simplified demo example of the issue.  You will have to pan around qucikly while clicking in the map for triggering highlight of the polygon.
http://tangram_error.ai-maps.com/

we have also jumped to another error, which is throwing sometimes in Firefox browser when you work (move, pan, zoom) with map example I posted...It seems to be leaflet error but maybe it has some connection to tangram.

Its failing in this leaflet function:
// Returns the element's class.
function getClass(el) {
	return el.className.baseVal === undefined ? el.className : el.className.baseVal;
}```

and one last issue related to my map example, sometimes we experience missing tiles, its mostly 1-3 tiles of whole viewoport that are just blank with no data rendered. But when you zoomin/zoomout or clik for feature info, the missing tiles get reloaded fine. There is no error or warning from tangram in this case, so we are not sure if its tile service source problem, or something in tangram...have you ever experiened something like this?

Thanks, we'll take a look as soon as we can.


feat: buildCustomTx stringified number value

Description

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

Testing

Engineering

Operations

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #4203

PR #4204

PR #4205

PR #4152

PR #4287   👈

This comment was auto-generated by Graphite.


Removing x-ms-flatten property

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[x] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[x] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[x] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

We are facing issue because of x-ms-flatten in our CLI/PS and .NET SDKs in deserialization of objects.

Looks good to me.

@mayankagg9722 added comment

Is such change not considered breaking? Any downstream SDK that respects the x-ms-flatten extension will change the shape of its generated properties. Why is this change made in the existing API version rather than a new one?

Hey Mikhail,
We have not generated any sdk so far. This came out as part of generating the first sdk and was breaking .net sdk. Hope that helps.
Thanks
Sumit
Sent from mobile

From: Mikhail Shilkov @.>
Sent: Saturday, April 17, 2021 1:01:29 AM
To: Azure/azure-rest-api-specs @.>
Cc: Sumit Malhotra (BACKUP) @.>; Comment @.>
Subject: Re: [Azure/azure-rest-api-specs] Removing x-ms-flatten property (#13929)
Is such change not considered breaking? Any downstream SDK that respects the x-ms-flatten extension will change the shape of its generated properties. Why is this change made in the existing API version rather than a new one?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F13929%23issuecomment-821516404&data=04|01|sumit.malhotra%40microsoft.com|5468869bd8314b4f3e1b08d9010e3c56|72f988bf86f141af91ab2d7cd011db47|1|0|637541982954004387|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=0oQia3n9OutdGbe%2B2Jwmu%2FXFP061%2BEypTfcPG28v4g8%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAN6VGSNP6UOCSAPKFCGREWTTJCGBDANCNFSM425MQI6A&data=04|01|sumit.malhotra%40microsoft.com|5468869bd8314b4f3e1b08d9010e3c56|72f988bf86f141af91ab2d7cd011db47|1|0|637541982954004387|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=rgcpedszTM71FarGXDOxfUcP0yupJoDywcGHFmu6pAI%3D&reserved=0.

Well, you are not the only client of these specifications.
I'm working on Pulumi Azure provider and this is a problematic change for us. Microsoft has published a breaking change policy but this kind of changes doesn't help us trust it, to be honest...

Hey Mikhail,
Thanks for the feedback. That is a valid concern. I will pass this on to the azure sdk team and we will make sure to address this in a more structured way.
Sent from mobile

From: Mikhail Shilkov @.>
Sent: Saturday, April 17, 2021 1:30:18 AM
To: Azure/azure-rest-api-specs @.>
Cc: Sumit Malhotra (BACKUP) @.>; Comment @.>
Subject: Re: [Azure/azure-rest-api-specs] Removing x-ms-flatten property (#13929)
Well, you are not the only client of these specifications.
I'm working on Pulumi Azure providerhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpulumi%2Fpulumi-azure-native&data=04|01|sumit.malhotra%40microsoft.com|6bad3dc9a9344c4cfedf08d9011242d0|72f988bf86f141af91ab2d7cd011db47|1|0|637542000267625981|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=iuJgcJ0ZQRwGdk1sOHpfTNToJgcW6NfSIFjfJn3LYq4%3D&reserved=0 and this is a problematic change for us. Microsoft has published a breaking change policy but this kind of changes doesn't help us trust it, to be honest...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F13929%23issuecomment-821529799&data=04|01|sumit.malhotra%40microsoft.com|6bad3dc9a9344c4cfedf08d9011242d0|72f988bf86f141af91ab2d7cd011db47|1|0|637542000267635934|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=YQvCee2jVeluOocWTr1BtBkwvCf%2FQ%2Bo48WPWzJqAYYQ%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAN6VGSMRFFN73KL3WTBM6XDTJCJNFANCNFSM425MQI6A&data=04|01|sumit.malhotra%40microsoft.com|6bad3dc9a9344c4cfedf08d9011242d0|72f988bf86f141af91ab2d7cd011db47|1|0|637542000267635934|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=I7M7AhL%2FkeGHdWYhRDdSpaRjXUomrE3XgIDTbHNVpks%3D&reserved=0.


Issue while testing  - Resource already exists

I tried testing on Magento 2.4.1 with cashfree payment gateway, I reached the payment page and I decided to cancel the order, it took me back to the cart page which was perfect as expected. But know whenever I am trying to click the payment gateway option, it takes me to error page which mentions "Resource already exists".
Let me know if you need more information.

@gmalhotra02 we have update our extension. Please refer to updated one.


updated readme badge links, updates devdependencies

Current coverage is 12.82% (diff: 100%)

Merging #29 into master will not change coverage

@@             master        #29   diff @@
==========================================
  Files            23         23
  Lines           803        803
  Methods          75         75
  Messages          0          0
  Branches        221        221
==========================================
  Hits            103        103
  Misses          700        700
  Partials          0          0

Powered by Codecov. Last update cce09fb...8750366


Make paths relative from config.root

If we merge https://github.com/antfu/vite-plugin-glob/pull/5 then I would propose this:
// Pre-transform
import.meta.importGlob('/**/*.page.js')

// Post-transform today
{
  "../../../../../examples/vue/renderer/_default.page.client.js": () =>
    import("../../../../../examples/vue/renderer/_default.page.client.js")
}

// Post-transform proposal (`config.root` being `'/examples/vue/'`)
{
  "/renderer/_default.page.client.jsx": () =>
    import("../../../../../examples/vue/renderer/_default.page.client.jsx")
}

This is what Vite does today.

Is that when the glob is / the so as the object key, or has it always been relative to /? Or maybe it's worth making it configurable?

Yes Vite does that when the glob starts with /. (Less sure otherwise.)
Regardless of Vite, I'd say that a sensible default is to preserve the glob syntax:
import.meta.importGlob('/**/*.js')
// Post-transform
{ "/path/to/some.js": () => import(/* ... */) }

import.meta.importGlob('./**/*.js')
// Post-transform
{ "./path/to/some.js": () => import(/* ... */) }

// We currently don't support that syntax, but in case we want to in the future:
import.meta.importGlob('**/*.js')
// Post-transform
{ "path/to/some.js": () => import(/* ... */) }

I'd say that this is what I would expect as a user.
Proposal: https://github.com/antfu/vite-plugin-glob/pull/7. It also includes a new option filePathsRelativeToRoot.

Implemented by https://github.com/antfu/vite-plugin-glob/pull/7.


Improve handling of default values

Thank you for pointing out this deficiency! I will not merge this code however, since I disagree with you on None being a sensible value for the host, port or base path fields. Instead I'll see to it, that the documentation is updated to point out that the defaults for these fields are ipfshttpclient.DEFAULT_{HOST,PORT,BASE} respectively.
Thanks for proposing this however.


Some builds relying on v4 images are not reproducible

Contracts that reference older versions of the Rust framework require - at build time, when the meta crate is invoked - some dependencies which were not strictly referenced by the meta crate itself (back then). Newer versions of these dependencies have been released in the meantime. And these newer dependencies - which (unfortunately) satisfy the (loose) versioning constraints of the (old) meta crate are not compatible with the Rust versions that were hard-coded in the Docker images of v4*. Thus, trying to reproduce such builds lead to errors such as:
error: package `clap_derive v4.4.7` cannot be built because it requires rustc 1.70.0 or newer, while the currently active rustc version is 1.66.0-nightly
Either upgrade to rustc 1.70.0 or newer, or use
cargo update -p<EMAIL_ADDRESS>--precise ver
where `ver` is the latest version of `clap_derive` supporting rustc 1.66.0-nightly

A fix is on the works: an additional Docker image of v4, compatible with (at least) v4.1.4.

#41
#42

Commands to adjust the Cargo.lock of a Cargo workspace that contains the contract in question (whose build needs to be reproduced), so that it's compatible with the Rust versions hard-coded within Docker images of v4*.
cargo update -p colored --precise 2.0.4
cargo update -p anstyle --precise 1.0.1
cargo update -p anstyle-parse --precise 0.2.1
cargo update -p anstyle-query --precise 1.0.0
cargo update -p clap --precise 4.3.11
cargo update -p clap_derive --precise 4.3.2
cargo update -p clap_lex --precise 0.5.0
cargo update -p clap_builder --precise 4.3.11
cargo update -p ignore --precise 0.4.20
cargo update -p ruplacer --precise 0.8.1

Example of problematic build that was fixed as described above:
https://github.com/multiversx/mx-exchange-sc/pull/795


Great package, but..

It needs to be able to do it automagically on save before it would save me any real time

Oh god sorry. I didn't know someone open an issue on my project. I miss the notification somehow.
I agree with you on this one. I think i've tried to do that and fallback to the save solution. I don't remember the reason though. My guess is that i have not found the correct api to do that.
I've moved on some other project for now as this one serves my need. I don't encounter any weird irregular whitespace  anymore since i'm using it.
Feel free to send a PR if you know how to pull it off. Or if you can point me to the vscode API that will allow us to do that, i'll may considerate and investigate it

This issue should be closed ! No!

I think that this issue should stay open in case someone want to do it. It will be a great feature to have.


refactor(projects): use assets collections for detail view

Current dependencies on/for this PR:

main

PR #118   👈

This stack of pull requests is managed by Graphite.


[eas-cli] Fix expo-updates package version detection for canaries

Why
Currently canaries fail these version checks since their versions are of the form 0.0.1-canary-20240109-93608d8 (semver 0.0.1). We've been investigating changing the canary versioning scheme, but it's a bit more complex than anticipated. Instead, just handle the current canary versioning scheme.
How
If canary is in the version, assume that it has features (for now).
Test Plan
Inspect.

/changelog-entry bug-fix Fix expo-updates package version detection for canaries


Game End screen only appears on Player screen, after timing out from moderator

not sure what this means

It had to do with the game end screen not coming up for a confusingly long
amount of time.
On May 23, 2016 12:55 PM, "Jordan Pailthorpe"<EMAIL_ADDRESS>wrote:

not sure what this means
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/engagementgamelab/emerging-citizens/issues/29#issuecomment-221030455

think this is linked to #53 or #31


Error when running jest test on the component spec file using

Describe the bug
After using this package my component tests started failing with the following error
To Reproduce
Steps to reproduce the behavior:

jest test

FAIL apps/my-app/src/app/auth/login/login.component.spec.ts                                                                                ● Test suite failed to run                                                                                Jest encountered an unexpected token                                                                                This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.                                                                                By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".                                                                                Here's what you can do:                                                                                • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.                                                  • If you need a custom transformation specify a "transform" option in your config.                                                                                • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.                                                                                You'll find more details and examples of these config options in the docs:                                                                                https://jestjs.io/docs/en/configuration.html                                                                                Details:                                                                                D:\MYapp\mayapp-rocket-shorts-ng7\node_modules\ngx-envconfig\index.js:1                                                                                ({"Object.":function(module,exports,require,__dirname,__filename,global,jest){export { ConfigModule } from './src/config.module';                                                                                ^^^^^^                                                                                SyntaxError: Unexpected token export                                                                                at ScriptTransformer._transformAndBuildScript (node_modules/@jest/transform/build/ScriptTransformer.js:471:17)                                                               at ScriptTransformer.transform (node_modules/@jest/transform/build/ScriptTransformer.js:513:25)                                                                              at Object. (apps/my-app/src/app/auth/login/login.component.ts:1162:25)`
I have been trying to fix this from hrs. But not able to.
I am on angular v7.
I tried upgrading from jest 23.6.0 to 24.7.1
tried upgrading from jest-preset-angular 6.0.2 to 7.1.0
upgrading angular-builders/jest from 7.2.1 to 7.4.2
But this error still persists on both the earlier and the later vesions stated above.
Can you give me an example of how we can use this package and still write a working jest test.

The following ticket fixed this.
https://github.com/thymikee/jest-preset-angular/issues/277#issuecomment-497636861
I was getting this issue because of the use of this preset.


[BUG] Tab header disaligned and with double stroke

Description
The image below shows two issues. In red, the tab header is not aligned with the border of the tab widget. In blue, I believe that there shouldn't be a grey stroke below the "Tab 1" and that "Tab 2" shouldn't have a double stroke (making it look like a thicker border).

Prerequisites

Qt version: 6
Theme: Dark, Light
OS: Windows 10

The misalignment is confirmed in widgets.py, however, the double border is intentional to make the difference between the active and inactive tab more obvious.

This still affects it at 2x scale so it's clearly not an artifact (which should be fixed even if it was).

These are the new images of how the tabs looks.

Great, thanks!

Thanks for your patience by the way on this.


It's all in 3.0

I'm currently doing 2.2 for University work but this tutorial page has recently changed to 3.0 completely, even when I scroll to different versions on the left-hand side, it's all the same tutorial for 3.0.

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

ID: 583ae3e7-5915-f22b-e54c-6c100cf2a7da
Version Independent ID: 95f2549e-29f9-e31a-b4d0-432b971643ff
Content: Tutorial: Create a web API with ASP.NET Core
Content Source: aspnetcore/tutorials/first-web-api.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@KyleAdo  sorry about that. We should be able to restore the 2.x version  in a few hours.

@KyleAdo  thanks for bringing this to our attention. I've restored the 2.2 version. It should be live in about 10 minutes.

Thank you very much Rick!


aiogram_dialog.exceptions.IncorrectBackgroundError:

aiogram_dialog.exceptions.IncorrectBackgroundError: Detected background access to dialog manager. Please use background manager available via manager.bg() method to access methods from background tasks. Help PLS

dp = Dispatcher(bot, storage=storage)
Delete parametr run_tasks_by_default=True

I have no idea why there exists option run_tasks_by_default.
Using middlewares you control where dependcies are initialized and where they are released. Background tasks are working outside of lifecycle of those dependencies, so you cannot use them (they can be released at that moment).
That's what you exacltly see when you try to access dialog_manaer from background task: it is already released and so cannot be used in task.


add --moveto option

dup files can move to new dir

Good feature. But this tool is designed to be non-destructive. As the name suggests, it just goes and finds duplicates. You're more than welcome to send bug-fixes or enhancements as long as they don't move or rename or delete any files.
For this pull request, I request you to maintain your fork.


i18n(es): update framework components

added alpineJS to installing integrations section  added alpine integration to the code example

What kind of changes does this PR include?

Translated content
Changes to the docs site code

Description

added AlpineJS to the installing integrations section
deleted content inside parenthesis at the end of the first paragraph of the "Installing Integrations" section
added alpine() to the integrations code example

Great job @glopzel! Also, thank you @kevinzunigacuellar 💜


Remove dependency on ConsumerParameters from DemARKs

This breaks with HARK master

I'm stumped on something. In the Chinese Growth DemARK, there is the following use of ConsumerParameters:
import HARK.ConsumptionSaving.ConsumerParameters as IncomeParams

LowGrowthIncomeDstn  = constructLognormalIncomeProcessUnemployment(IncomeParams)

The entire ConsumerParameters module is being passed to this function here.
I wonder which of the parameters dictionaries would be most appropriate to use as the input to this function.
Related to https://github.com/econ-ark/HARK/issues/538

Well that's weird.
On Thu, Mar 19, 2020 at 1:14 PM Sebastian Benthall<EMAIL_ADDRESS>wrote:

I'm stumped on something. In the Chinese Growth DemARK, there is the
following use of ConsumerParameters:
import HARK.ConsumptionSaving.ConsumerParameters as IncomeParams
LowGrowthIncomeDstn  = constructLognormalIncomeProcessUnemployment(IncomeParams)
The entire ConsumerParameters module is being passed to this function here.
I wonder which of the parameters dictionaries would be most appropriate to
use as the input to this function.
Related to econ-ark/HARK#538 https://github.com/econ-ark/HARK/issues/538
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/econ-ark/DemARK/issues/109#issuecomment-601306333,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKRAFLEYA7SBR2G7PWHPWTRIJHILANCNFSM4LPK4UNA
.

Maybe the reason why it was done this way is that if a parameters dictionary is passed in to that function, one gets this error:
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-9-3b531f79638d> in <module>
     13     'T_retire' : 0                 # Period of retirement (0 --> no retirement)
     14 }
---> 15 LowGrowthIncomeDstn  = constructLognormalIncomeProcessUnemployment(income_params)[0][0]
     16
     17 # Remember the standard deviation of the permanent income shock in the low-growth state for later

~/projects/econ-ark/HARK/HARK/ConsumptionSaving/ConsIndShockModel.py in constructLognormalIncomeProcessUnemployment(parameters)
   2759     '''
   2760     # Unpack the parameters from the input
-> 2761     PermShkStd    = parameters.PermShkStd
   2762     PermShkCount  = parameters.PermShkCount
   2763     TranShkStd    = parameters.TranShkStd

AttributeError: 'dict' object has no attribute 'PermShkStd'

Yeah, the constructLognormalIncomeProcessUnemployment function is weird.
The usual thing that gets passed to it is an entire IndShockConsumerType
instance, which has attributes for all of the things the function is
looking for. When Dave Low made this example application, he must have
decided that passing the parameter file itself was a sufficient workaround.
I've never noticed that he did it that way!
On Thu, Mar 19, 2020 at 4:12 PM Sebastian Benthall<EMAIL_ADDRESS>wrote:

Maybe the reason why it was done this way is that if a parameters
dictionary is passed in to that function, one gets this error:

AttributeError                            Traceback (most recent call last)
 in
13     'T_retire' : 0                 # Period of retirement (0 --> no retirement)
14 }
---> 15 LowGrowthIncomeDstn  = constructLognormalIncomeProcessUnemployment(income_params)[0][0]
16
17 # Remember the standard deviation of the permanent income shock in the low-growth state for later
~/projects/econ-ark/HARK/HARK/ConsumptionSaving/ConsIndShockModel.py in constructLognormalIncomeProcessUnemployment(parameters)
2759     '''
2760     # Unpack the parameters from the input
-> 2761     PermShkStd    = parameters.PermShkStd
2762     PermShkCount  = parameters.PermShkCount
2763     TranShkStd    = parameters.TranShkStd
AttributeError: 'dict' object has no attribute 'PermShkStd'
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/econ-ark/DemARK/issues/109#issuecomment-601393746,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKRAFJ6SRHRF7UP4OQJH7TRIJ4CBANCNFSM4LPK4UNA
.

fixed in https://github.com/econ-ark/DemARK/pull/110


Problems while selecting the property uniquely in Configurations screen while installation

How was this patch tested?
Tested manually

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1523/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1548/
Test FAILed.
Test FAILured.

2255648 [INFO] Ambari Web ......................................... SUCCESS [03:10 min]


More than one file was found with OS independent path 'lib/armeabi-v7a/libijkplayer.so'. If you are using jniLibs and CMake IMPORTED targets, see https://developer.android.com/studio/preview/features#automatic_packaging_of_prebuilt_dependencies_used_by_cmake

More than one file was found with OS independent path 'lib/armeabi-v7a/libijkplayer.so'. If you are using jniLibs and CMake IMPORTED targets, see https://developer.android.com/studio/preview/features#automatic_packaging_of_prebuilt_dependencies_used_by_cmake
请问这是什么原因导致的呢，看文档好像不需要下载.so包吧，也没找到

你的项目是不是依赖了 ijk ，和gsy 的ijk冲突了

谢谢，解决了


Mobile nav links aren't showing in tutorial

📝 Issue Description
Mobile nav links aren't showing because:
.nav-links {
  display: none;
}

📋 On which page(s) it occurs
https://docs.astro.build/en/tutorial/3-components/3/
🤔 Expected Behavior
On mobile view the nav links should be showing
👀 Current Behavior
On mobile view the nav links aren't showing
🖥 Browser
Chrome
📄 Additional Information
No response

Sorry it should be tagged "Incorrect Content Report" instead of bug, but can't change it back.

Hey 1codingguy 👋 , mobile nav links are displayed underneath the hamburger menu which is addressed in https://docs.astro.build/en/tutorial/3-components/4/. Safe to say the content is correct


Displaying extra command on tab completion (zsh)

You cannot delete it with backspace.

This might be fixed by 0.2.0. Let me know if it still happens when you upgrade.

It still happens.

😢

Please retry with 0.3.1.

same 😭

It's fixed when I tried the master branch.

Same problem here!

Dropping a bit on info: This happens with certain ZSH themes, not all of them. It might have to do with how some themes modify the shell prompt.

I'm using ZSH too and reproduce this bug except when I remove every special unicode characters from the prompt (like the ➜ in robbyrussell theme or the "fat-arrow" in Powerline-like themes).

Cann't reproduce on current master(https://github.com/zeit/hyperterm/commit/7398593bc36b9624db25f3faee21c3a35b1ca415) with zsh + robbyrussell theme , seems like fixed?

I think it is, can't reproduce either on latest versions.

Same problem here with last master and zsh 5.2.
Also for me, like @MattKetmo, removing any special unicode char from prompt fixes the issue!

I used "pure" theme and it also unicode char in the prompt. Same problem occured. Removing theme solved this issue.

Same problem here, ZSH theme "avit".

same problem here<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Same issue here!
<EMAIL_ADDRESS><EMAIL_ADDRESS>With hyperzsh theme: https://github.com/tylerreckart/hyperzsh

Fixed by adding this to my .zshrc
# You may need to manually set your language environment
export LANG=de_AT.UTF-8

Seems fixed


Ability to specify user and group during Install

I'm not. sure if there is a way of doing this through the module but if there is I can't find it. I can see a global owner and group but I'm not sure that these are the way to do this.


wasm_sgx didn't run *.wasm which generated by wasm-pack

I try to run a wasm file in enclave of sgx, It failed.
The wasm file is generated by wasm-pack, and it is writed by rust.
Here is the source code:
use wasm_bindgen::prelude::*;

// When the `wee_alloc` feature is enabled, use `wee_alloc` as the global
// allocator.

#[wasm_bindgen]
pub fn greet() {
    println!("Hello, wasmsgx!");
}

the cargo.toml is
[package]
name = "wasmsgx"
version = "0.1.0"
authors = ["webb.shi<EMAIL_ADDRESS>edition = "2018"

[lib]
crate-type = ["cdylib", "rlib"]

[features]
default = ["console_error_panic_hook"]

[dependencies]
wasm-bindgen = "0.2.63"

# The `console_error_panic_hook` crate provides better debugging of panics by
# logging them with `console.error`. This is great for development, but requires
# all the `std::fmt` and `std::panicking` infrastructure, so isn't great for
# code size when deploying.
console_error_panic_hook = { version = "0.1.6", optional = true }

# `wee_alloc` is a tiny allocator for wasm that is only ~1K in code size
# compared to the default allocator's ~10K. It is slower than the default
# allocator, however.
#
# Unfortunately, `wee_alloc` requires nightly Rust when targeting wasm for now.
wee_alloc = { version = "0.4.5", optional = true }

[dev-dependencies]
wasm-bindgen-test = "0.3.13"

[profile.release]
# Tell `rustc` to optimize for small code size.
opt-level = "s"

and the error log is
WASM module instantiate failed: allocate memory failed

Does wamr support rust-wasm now? If yes ,what should I do to run this demo? Thanks a lot!

Hi, it seems that the heap size configured for sgx enclave is not enough, could you please cd enclave-sample, modify file Enclave/Enclave.config.xml, enlarge HeapMaxSize:
<HeapMaxSize>...</HeapMaxSize>

and then
make clean && make

and run iwasm again? Thanks.

Hi, it seems that the heap size configured for sgx enclave is not enough, could you please cd enclave-sample, modify file Enclave/Enclave.config.xml, enlarge HeapMaxSize:
<HeapMaxSize>...</HeapMaxSize>

and then
make clean && make

and run iwasm again? Thanks.

It worked! Really appreciate for your help! :smile:


[Bug] Using composable in intercept from useIntercept throws error

What happened?
Can't use composables in intercept callback since update to 1.0.0-RC.2
In shopware-pwa version 0.9.2 is could use the following in an interceptor:
const { intercept } = useIntercept()

intercept(
        INTERCEPTOR_KEYS.SESSION_SET_SHIPPING_METHOD,
        async ({ shippingMethod }) => {
          const { switchState } = useUIState({
            stateName: "SW_STORE_LOCATOR_MODAL_STATE",
          })
          switchState(true)
        }
      )

this will result in the following error in version 1.0.0-RC.2: Uncaught (in promise) Error: [useSharedState] sharedStore is not injected into Vue instance
This because i can't initialize any composable in the callback what means i need to call it outside the intercept callback:
The following code works:
      const { intercept } = useIntercept()
      const { refreshCart } = useCart()
      const { switchState } = useUIState({
        stateName: "SW_STORE_LOCATOR_MODAL_STATE",
      })

      intercept(
        INTERCEPTOR_KEYS.SESSION_SET_SHIPPING_METHOD,
        async ({ shippingMethod }) => {
            switchState(true)
        }
      )

It's is not the biggest problem but is it not more efficient to be able to call any composable only when the event is fired like in version 0.9.2?
I didn't tested version s between 0.9.2 and 1.0.0-RC.2 but i think it has to do with the removed rootContext.
Steps To Reproduce

install version 1.0.0-RC.2
listen to an event with useIntercept
use and initialize a composable in the intercept callback body
call event
see error in debugger

Is there an existing issue for this?

[X] I have searched the existing issues

Version
Latest stable (generated by CLI)
Which element is affected?
composables, plugins
Environment
- OS: Macos Big Sur
- Node: 14.16.1
- Shopware API: <IP_ADDRESS>
- Shopware PWA version: 1.0.0-RC.2

Relevant log output
Uncaught (in promise) Error: [useSharedState] sharedStore is not injected into Vue instance

AFFECTS FUNCTIONS IN CUSTOM COMPOSABLES
When using the following piece of code i also get the error from above.
const someComposable = () => {
  const { cart } = useCart()

  const loadSomeProduct = (product) => {
    const { product } = useProduct({ product })
  }
}

Here the error No Vue Instance Detected will be thrown. in the useProduct composable while useCart works perfectly.


fix: tests external validation

#86

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

v1.31.0
GitHub release

Your semantic-release bot :package::rocket:


Using a templated legend: "{{value}}" in a tabarray doesn't update the tab names for enums

Weirdly it still seems to honour the "Item {{idx}}" template for the tabs:

In the example below, it works fine if "items[].slot" does not have an enum (ie not a select field - same problem with "type: radios" as an aside).

{
    "schema": {
        "type": "object",
        "properties": {
            "items": {
                "type": "array",
                "items": {
                    "type": "object",
                    "title": "Items",
                    "description": "List of items",
                    "properties": {
                        "slot": {
                            "title": "Slot",
                            "type": "string",
                            "enum": [
                                "hand",
                                "head",
                                "chest",
                                "legs",
                                "feet",
                                "hands"
                            ]
                        },
                        "item": {
                            "title": "Item",
                            "type": "string"
                        }
                    }
                }
            }
        }
    },
    "form": [
        {
            "key": "items",
            "type": "tabarray",
            "items": [
                {
                    "legend": "{{value}}",
                    "type": "section",
                    "items": [
                        {
                            "key": "items[].slot",
                            "valueInLegend": true
                        },
                        "items[].item"
                    ]
                }
            ]
        }
    ]
}

That doesnot work again! Value of enumed-field (select) in tabarray cant be used in legend for some reason :(

Му form, where this problem is in the third-level sub-tabarray ("providers")
try03.txt

I'm closing this issue since it is probably outdated — Please reopen if you still need help on this. Thanks


Deprication warning with RSpes 3.4.2

When using with RSpec 3.4.2 I'm getting those deprecation warnings:
`failure_message_for_should_not` is deprecated. Use `failure_message_when_negated` instead. Called from /home/vagrant/.gem/ruby/2.3.0/gems/rspec-padrino-0.2.2/lib/rspec/padrino/matchers/redirect_to.rb:26:in `block in <module:RedirectTo>'.

`failure_message_for_should` is deprecated. Use `failure_message` instead. Called from /home/vagrant/.gem/ruby/2.3.0/gems/rspec-padrino-0.2.2/lib/rspec/padrino/matchers/redirect_to.rb:22:in `block in <module:RedirectTo>'.

After having a fast look into the RSpec changelog, this was added with 3.0.0.beta2.

closed via #15

Thanks for your report.


Error: cannot import name 'etree' from 'lxml'

When trying to execute
`from unstructured.partition.auto import partition
elements = partition("example-docs/layout-parser-paper.pdf")`
I get the above mentioned error. However, import lxml works just fine. For some strange reason, the "etree" submodule cannot be imported.
The exaxt error message was: "ImportError: cannot import name 'etree' from 'lxml' (/usr/lib/python3/dist-packages/lxml/init.py)".

Hi @codingbutstillalive - thanks for reporting this. What lxml and Python version are you using?
Found this issue that may be helpful. They suggest the following:
pip uninstall lxml
pip install --no-binary lxml

Do you know what Python version and operating system is running on Paperspace vs. Colab?

Searching around for other occurrences of this error has led me to suspect the compiled binary extension that contains etree doesn't match something about the Python version that's trying to import it.

Here some people were able to solve it by reinstalling or finding and installing the correct pre-compiled binaries for their system and Python version.
Here and here it's suggested that there is more than one installation of Python and lxml and the user should try getting rid of one of them, although these are on Windows.
Here same type of suggestions, possibly multiple installations of lxml.

From your traceback it looks like it's looking in your system Python packages for lxml. Maybe that's a clue? Did you install it into a virtual or conda environment and it's importing from the wrong place?
In any case I would check for multiple installations of lxml and conflicting Python environments (maybe check the PYTHONPATH environment variable to see where it's looking for packages and in what order). If you find other installations of lxml, remove them and try installing again into the desired environment.

I did some research and I found this - though I was using another container image, I suppose the way how paperspace maintains stuff in them might still be the same:
"Whereas paperspace installs packages using conda. The question is will this mess up things? The answer to this question is no. The place where you need to use conda/mamba is the stuff that uses the GPU. Especially, for PyTorch or TensorFlow. Conda/mamba has a way of installing the CUDA toolkit requirements so that we don’t need to worry about installing the CUDA SDK separately. Conda maintains the CUDA versions as they need to mesh properly with the PyTorch version."
Could this maybe explain it?

It's a clue there might be a conda environment. So it's possible the lxml installation you want is in a conda environment, and it's trying to import from the system Python environment.

Yes. That seems to be the case.
How would I then install detectron2? The manual only describes installation with pip. I am not quite sure :)

In theory conda should be able to handle and keep track of packages installed into a conda environment with pip (although in practice this hasn't always been the case when I've used conda) so you should just be able to follow the instructions from the documentation after activating your conda environment. As a last resort, you could install the detectron2 conda package on conda-forge. Note this isn't the version we recommend (0.6 was released in November 2021 and there hasn't been a release since) and I don't have any experience with this packaging but if nothing else works it's something to try.
You didn't specifically say that this was a problem, but I'll just mention that detectron2 needs to be installed after torch is installed, which is why we don't put it in the requirements to be installed concurrently with torch.

I could in fact solve the issue. But then I encountered a new one.
The lxml issue seemed to have been related to the version.
The version installed as a dependency of detectrom was 4.5 instead of 4.9.
When I removed and re-installed, it got solved.
So installation succeeded. But when running the code, there was a message
that "detectron was probably not correctly installed".
I assume this could be the case because the Torch version pre-installed on
Paperspace might not be compiled with the same CUDA version like detectron
and pip cannot detect and act on this. I read something along these lines
on the poetry github page concerning detectron.
Maybe I need to use another than the default git repository URL? I saw you
provide different pre-compiled wheels for it, right?
How can I determine which would match to each other?
qued @.***> schrieb am Sa. 29. Apr. 2023 um 19:31:

In theory conda should be able to handle and keep track of packages
installed into a conda environment with pip (although in practice this
hasn't always been the case when I've used conda) so you should just be
able to follow the instructions from the documentation after activating
your conda environment. As a last resort, you could install the detectron2
conda package https://anaconda.org/conda-forge/detectron2 on conda-forge.
Note this isn't the version we recommend (0.6 was released in November 2021
and there hasn't been a release since) and I don't have any experience with
this packaging but if nothing else works it's something to try.
You didn't specifically say that this was a problem, but I'll just mention
that detectron2 needs to be installed after torch is installed, which
is why we don't put it in the requirements to be installed concurrently
with torch.
—
Reply to this email directly, view it on GitHub
https://github.com/Unstructured-IO/unstructured-inference/issues/90#issuecomment-1528834937,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACM6OHGGK35SZKZEB3RZWILXDVF5ZANCNFSM6AAAAAAXMOCD3Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

In theory conda should be able to handle and keep track of packages installed into a conda environment with pip (although in practice this hasn't always been the case when I've used conda) so you should just be able to follow the instructions from the documentation after activating your conda environment. As a last resort, you could install the detectron2 conda package on conda-forge. Note this isn't the version we recommend (0.6 was released in November 2021 and there hasn't been a release since) and I don't have any experience with this packaging but if nothing else works it's something to try.
You didn't specifically say that this was a problem, but I'll just mention that detectron2 needs to be installed after torch is installed, which is why we don't put it in the requirements to be installed concurrently with torch.

I could in fact solve the issue. But then I encountered a new one. The lxml issue seemed to have been related to the version. The version installed (as a dependency of detectron?) was 4.5 instead of 4.9. When I removed and re-installed lxml, it got resolved. So installation succeeded. But when running the code, there is now an error message that "detectron was not correctly installed". I assume this could be the case because the Torch version pre-installed on Paperspace might not be compiled with the same CUDA version like the one detectron2 used and pip cannot detect and act on this. I read something along these lines on the poetry github page concerning detectron2. Maybe I need to use another than the default git repository URL? I saw you provide different pre-compiled wheels for it, right? How can I determine which would match each other?

I assume this could be the case because the Torch version pre-installed on Paperspace might not be compiled with the same CUDA version like the one detectron2 used and pip cannot detect and act on this.

That sounds pretty close to me, although I'm not sure if CUDA is involved. As far as I know detectron needs to be matched with the torch version (which is why torch needs to be pre-installed when installing detectron). I don't know if switching to a different detectron version will work, my impression is that detectron is capable of using whatever version is installed (within reason) when installing, but then you have to stick with that version when using detectron. So my guess would be detectron is mixed up about which installed torch version it should be "matched" with.
What I would want to do in your situation is set up a clean virtual environment with no interference from other installed components, but I don't know how much trouble that is to set up on your Paperspace machine.

I did this using venv. And the installation still didn’t fully work. It is
really some nasty thing.
thanks for your help nevertheless. I will actually give it up by now.
qued @.***> schrieb am Do. 4. Mai 2023 um 20:28:

I assume this could be the case because the Torch version pre-installed on
Paperspace might not be compiled with the same CUDA version like the one
detectron2 used and pip cannot detect and act on this.
That sounds pretty close to me, although I'm not sure if CUDA is involved.
As far as I know detectron needs to be matched with the torch version
(which is why torch needs to be pre-installed when installing detectron). I
don't know if switching to a different detectron version will work, my
impression is that detectron is capable of using whatever version is
installed (within reason) when installing, but then you have to stick with
that version when using detectron. So my guess would be detectron is mixed
up about which installed torch version it should be "matched" with.
What I would want to do in your situation is set up a clean virtual
environment with no interference from other installed components, but I
don't know how much trouble that is to set up on your Paperspace machine.
—
Reply to this email directly, view it on GitHub
https://github.com/Unstructured-IO/unstructured-inference/issues/90#issuecomment-1535222722,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACM6OHHY5GZBD2GMN32DZ63XEPYNJANCNFSM6AAAAAAXMOCD3Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

@codingbutstillalive Incidentally, we no longer require installation of detectron2, as long as you can install the ONNX runtime you should be able to use the detectron2 model. Closing issue in light of the update.


Add getPath method to every record

I've been listing through some articles and lots of issues here on Github but I haven't found answer to idea I've got.
If I edit some record in the list somewhere deep in structure tree and pass it on to some store / action creator, in the store I have to somehow find this record again to edit something inside it or maybe delete it. Sure, I can use cursor to simplify this step but I would have to loop through records in the list in order to find that particular record according to ID or something.
Passing on index of this record along with ID (which is needed for API fetch) seems kind a strange to me...
So I got and idea that it would be nice if I had some getPath() method on record, or just record.path because then I could just do in my store something like:
updateById(id, record.getPath(), {name: 'john doe'})

updateById(id, path, updateObj) {
   state = state.updateIn(path, prev => prev.merge(updateObj))
}

Instead of:
updateById(id, {name: 'john doe'})

updateById(id, updateObj) {
  state = state.updateIn(findPathWithLoopById(id), prev => prev.merge(updateObj)))
}

Since we have to loop through whole json or some other structure when we do immutable.fromJS() there would be no impact on performance, right?
Or I would appreciate if you point me to some other solution for this which is already out there and I miss it.
Thank you so much for all the great work you have done!

A single record can be used in many different lists and immutable structures, so which path to return? If you move the record, do you want to change the path in the immutable record?
If you want a simpler lookup, you could maintain a separate map from id to path. Or you could change your data structure so you have an ordered map from id to record rather than a list (you can always get the list back if you need it using toList()).

@tomwidmer thank you for your reply!
Well yes, yes and yes:)
I think that most of the use cases are that you want to map your immutable state to some react components, get some update action and than find entity to be updated back in the tree using id.
Well maybe I am just looking for some best practices in this area.
And to you note with map with ids as keys: I would love to do it, but we have JSON here, which does not allow to have explicitly indexed arrays nor I can't use object with ids in keys because they don't maintain order :(

The records themselves do not know where they exist within a parent (or multiple parents!)


Update sbt-assembly to 2.1.4

About this PR
📦 Updates com.eed3si9n:sbt-assembly from 2.1.1 to 2.1.4
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (2.1.1).
You might want to review and update them manually.
website/static/img/undraw_docusaurus_react.svg
website/yarn.lock

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.eed3si9n", artifactId = "sbt-assembly" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.eed3si9n", artifactId = "sbt-assembly" }
}]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Superseded by #765.


NETOBSERV-1507: some arch still missing fentry hook types fallback to kprobe [BP 1.5]

Signed-off-by: Mohamed Mahmoud<EMAIL_ADDRESS>(cherry picked from commit 43038f3ee6b1ab1c8f2da34413e26fdca6dd6b05)
Description

Dependencies

n/a
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.

[ ] Will this change affect NetObserv / Network Observability operator? If not, you can ignore the rest of this checklist.
[ ] Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
[ ] Does this PR require product documentation?

[ ] If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.

[ ] Does this PR require a product release notes entry?

[ ] If so, fill in "Release Note Text" in the JIRA.

[ ] Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.

[ ] If so, make sure it is described in the JIRA ticket.

QE requirements (check 1 from the list):

[ ] Standard QE validation, with pre-merge tests unless stated otherwise.
[ ] Regression tests only (e.g. refactoring with no user-facing change).
[ ] No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

/lgtm

/approve


Recheck consul connection in case of bootstrap race (master)

#792 (for master branch)
Standardizing on service port check == 0 to determine if service is in race condition with config-seed population in Consul.
Signed-off-by: Trevor Conn<EMAIL_ADDRESS>

Other than the two questions posted above, the PR LGTM 👍


Fix decode tx in plutus minting

[x] I have introduced AnyScript that could be either Timelock or Plutus script. They are both parsed in Compatibility
[x] I have added the integration test bits to show the case that minting causes decodeTransaction failure just because of the absense of treatment scripts like AnyScript introduces
[x] swagger, core unit tests, and other places updated
[x] I have also fixed the issue when both minting/burning are in the same tx. Now they are treated correctly.

Comments

Issue Number
adp-1610

I have adjusted Plutus e2e tests and added/enabled e2e tests for minting/burning in single tx. They're passing locally for me against this branch. Running also here -> https://github.com/input-output-hk/cardano-wallet/runs/5836563610?check_suite_focus=true.
I think we should probably add integration tests or property tests for mint/burn in the same tx.

Running e2e flow against the branch -> https://github.com/input-output-hk/cardano-wallet/runs/5850438060?check_suite_focus=true

bors r+


introduce log-target constant to more frame pallets

use the LOG_TARGET constant for more frame pallets.
get's us closer to: #12873

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable-int
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2246661

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2246655

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable-int
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2246714

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2246708


[CVAT integration] Add Exchange Oracle example

Description

This PR replaces/adds the old CVAT integration example with a new one, that allows to annotate bounding boxes and points.
Summary of changes

examples/cvat/exchange-oracle is completely replaced with a new implementation

How test the changes

No unit tests added yet, it needs to be done.
Related issues
Keywords for linking issues

Operational checklist

[ ] All new functionality is covered by tests
[ ] Any related documentation has been changed or added

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.3 out of 4 committers have signed the CLA.:white_check_mark: eugenvoronov:white_check_mark: simulacrum6:white_check_mark: portuu3:x: zhiltsov-maxYou have signed the CLA already but the status is still pending? Let us recheck it.


Provide GuiFloatValueBox()

Sometimes people need to be able to view and edit float values

Yeah, I agree but that's actually a quite complex function, the "dot" possition depends on the locale of the system and could be difficult to manage properly.

I tried to make this today because i needed it myself, but i got stuck because when editing the float value's decimal places (pressing backspace), on the next function call they are printed out again. I think this needs some external text memory where you first edit the text and then update the value. @raysan5 pls let me know what you think, im trying to help but idk if this is the right approach

@benjibst Afaik, approach should be similar to GuiValueBox() but parsing the value as a float (instead of int) and probably limiting it to 3 decimal positions.

@danielchasehooper I made this now, on my profile you can find a fork to raylib and raygui if you still need it. the usage is a bit different, you have to provide a data buffer when you call the function where it stores the string representation of the float.

@raysan5 i made a pull request for this, would you mind taking a look?

Related PR https://github.com/raysan5/raygui/pull/356. We can continue the discussion in there.


Negative caching TTL (RFC 2308)

Looks like the current behavior of caching negative results is to always use a fixed TTL, as configured in cache_neg_ttl.
It would be nice if the TTL can be determined according to RFC 2308 - Negative Caching of DNS Queries (DNS NCACHE), using the MINIMUM field in SOA records. Many domains have an actual negative TTL set to much longer than 60 seconds, so implementing this should reduce the number of queries that have to be sent upstream.

RFC 2308 is broken by design due to the SOA TTLs not being decreased by caching resolvers unlike RR TTLs.
When multiple caches are chained, which is always the case with dnscrypt-proxy, a negative response will always be cached way longer than expected.
dnscrypt-proxy can also use multiple servers simultaneously. If only due to qname minimization, we had many reports of names returning NXDOMAIN with a resolver, and returning a proper RRSET with another.
Having a fixed, reasonable value for the negative TTL may lead to sending additional queries, but reduces the number of "it doesn't work" complains.
This can be tuneable, though. Maybe we should respect RFC 2308, but provide min and max properties to force it to be within a range. Is it something you can implement?

Interesting, I did not know that peculiarity about SOA TTLs, and it does make sense to use a short TTL in that case.

Is it something you can implement?

Probably not, unfortunately. My lack of knowledge in golang is only the first obstacle. :-/


Test notebooks on free account

To check for any issues users on this will see

Blocked by #1

ViT and BERT-L OK.

Testing notebooks on free accounts looks good for initial run throughs.

text_classification.ipynb has not been run (#1), therefore has not been tested on a free account.
If we remove text_classification.ipynb, or run it through with the required HF login (#10), then this is complete.


offer AUR distribution of poac to Arch Linux users on README.md

poac is now available in Arch User Repository. (#195)
This request will add a sentence offering AUR distribution of poac to README.md
Installation in Arch Linux can be done with the command like the following.
~ $ yay -S poac

Thank you for contributing.
Currently, master branch is broken and protected, so I'll merge this PR using my administrator privilege.
Also, I saw your other contribution. Thank you again for your support, and I'll respond when I have enough time.
FYI: The latest branch is develop, so if you want to contribute to poac codes, please use develop branch.


Update Rust to version 1.34.0

No apparent regression.

It sounds like there's going to be a point release very soon to fix some compiler crashes, so let's hold off until 1.34.1 is available


Alerts not working in 0.10.4

[ X ] bug
[ ] feature request
[ ] enhancement

Expected behavior
The examples in clarity site to be working.
Actual behavior
I've taken example directly from the clarity site about alerts, which use only DOM elements without angular components.
The concrete example:

...

Acknowledge
Reset to green

This is resulting into:
Error: Uncaught (in promise): Error: No provider for AlertIconAndTypesService!
Error: No provider for AlertIconAndTypesService!
at injectionError (reflective_errors.ts:73)
Reproduction of behavior
Plunker: https://plnkr.co/edit/lOYm5CHP52BW0x0GveVB?p=preview
Environment details

Angular version: 2.0.X

Clarity version:

OS and version:

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

https://plnkr.co/edit/CFowzx?p=preview
You are using a static alert inside of an Angular app. See this answer for this stackoverflow question for more information: https://stackoverflow.com/a/46024788/7376162

Thanks!
I understand the problem and the fix.
Seems that I've been looking at the three places in the doc where this is wrong and I spent a lot of time in research. Please check here:
https://vmware.github.io/clarity/documentation/alerts
Section: "Types"
See the code example - there is no 'static' class next to the .alert-item.
At least as result I've migrated all our alerts to the angular implementation.

@zivanov123: Thanks for notifying us of the issue. We will make sure we update our docs to use the .static class. If you use Clarity Angular too, then using the Angular Alerts component is the best option.

@adityarb88 No problem. Please also fix it here:
https://vmware.github.io/clarity/news/0.10.0-alpha.2

@adityarb88
It is already in our docs.

@zivanov123
You only need to use the .static class when you are using non-Angular Clarity alerts inside of a Clarity Angular application.

This is not a standard way of doing things. The vast majority of the time you should use clr-alert instead of building an alert with just HTML inside a Clarity Angular app

Putting the .static class on straight DOM (not angular application) is unnecessary and would only serve to assist people who insist on not using clr-alert and don't read the existing documentation.

Yes, I saw that but I was not sure why it was written, since the examples were stating another thing :)
Thanks for fixing!


Cannot start server on Linux AMD64

I carefully followed the instructions at https://github.com/mozilla/mentat/blob/rust/README.md#building
$ git status
On branch rust
Your branch is up-to-date with 'origin/rust'.

cargo build and cargo test --all apparently worked fine... however:
$ cargo run serve
error: a bin target must be available for `cargo run`

Are the instructions outdated? Did I do something wrong?

cargo --version
cargo 0.18.0 (fe7b0cdcf 2017-04-24)

just installed rust in order to try out mentat, using https://www.rustup.rs/

Hi!
The instructions are outdated. #448 just moved the stub server code out of the main path to help minimize footprint.
Right now the minimal Rust API, using Conn, as expressed in the top-level tests, is the best way to try this out.
I'll keep this issue open to track fixing the docs.
Thanks!

Fixed in https://github.com/mozilla/mentat/commit/953f9f773496f5c63d76a2cba60e43b8d68dd7f5.

Thanks! Do I understand correctly that Mentat currently only implements a Rust library which provides a data store embedded in a Rust project?
(AOT querying a Mentat server with EDN over TCP or similar?)

Thanks! Do I understand correctly that Mentat currently only implements a Rust library which provides a data store embedded in a Rust project?

That's the principle vehicle, but @fluffyemily is building a CLI to expose a human-oriented interface over in https://github.com/mozilla/mentat/projects/3, and it would be easy (if not something we'll do anytime soon) to expose /transact and /query endpoints via an HTTP/Socket service.


Tensorboard shows an empty graph section

Hi,
I want to see the graph with my new mrt_trainer. I see the graph using the Xent trainer, but when I switch to mine trainer, the section remains empty, although no "No graph definition files were found." message shows up. The graph exists though, meaning I know it computes loss, gradients etc. The difference to the Xent is, that even though I have num_of_sessions=1, I have two iterations for session_results in the execute(). Could that require some adjustments in order to visualize the graph?
Best,
Stoyan

Hi,
I suspect this might be a bug, but I don't see how. @jlibovicky could you take a look at that?
Jindra

Hi, I don't think these things are related. The graph needs to be built before anything is executed, it has nothing in common in the way the particular nodes of the graph are later executed. When you look into the experiment directory, is the graph definition there?

Hi,
no, I don't see it. But I also don't see it for the xent model. This is what I have in the directory, the same is for both models:

It should be in the events file. It's a binary file, but you can view the strings inside e.g. using the strings command and have a look if you see names of the graph nodes. Another clue could the size of the file, if its significantly smaller than the other one, it may mean the graph definition inside is missing.

Hi,
the mrt-model file is actually 3 times bigger then for the xent-model...
I was not sure what the lines mean, but I think what I see among other things are names in the defined name scopes and such lines are presented in both files. I'll upload a screenshot again.

Then the graph is definitely in the events file. In that case, I would suspect it is a TensorBoard issue due to the graph size.


Support UI UT

Coverage remained the same at 55.309% when pulling 2d89bc2974b51d1fc7d9d5d0147fab498b280451 on wy65701436:gas-scanner into 301fe2c766391872dc453d8d4edca99844056064 on vmware:master.

Coverage remained the same at 55.309% when pulling f26040872a0f545a92592bbf561f55885a895466 on wy65701436:gas-scanner into 301fe2c766391872dc453d8d4edca99844056064 on vmware:master.

Coverage increased (+0.05%) to 55.355% when pulling<PHONE_NUMBER>f1288b2333c20d6be1e70429034a40 on wy65701436:gas-scanner into 301fe2c766391872dc453d8d4edca99844056064 on vmware:master.

Coverage remained the same at 55.309% when pulling 1d0721fdfca72b57703f6a94a913ca68bd1258b1 on wy65701436:gas-scanner into 301fe2c766391872dc453d8d4edca99844056064 on vmware:master.

Coverage remained the same at 55.309% when pulling 1d0721fdfca72b57703f6a94a913ca68bd1258b1 on wy65701436:gas-scanner into 301fe2c766391872dc453d8d4edca99844056064 on vmware:master.


Enter verify code to login to wecom token

Enter verify code to login to wecom token
Recently, some wecom account requires a verify-code to login to desktop client. It looks like this:

To make these accounts usable, we implemented verify-code event and verify-code entering method in @juzi/wechaty ASAP. You should note that currently we can only ensure the experience of node version wechaty. We don't have enough resources to push to iterate for other versions. To make full use of your token, we recommend you to use node version of wechaty. ( @juzi/wechaty has only node version provided. )
Dependencies
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Types
export enum VerifyCodeStatus {
  UNKNOWN = 0,
  WAITING = 1, // Waiting for input
  EXPIRED = 2, // Not implemented yet, now you should judge from the error message of verify-code enter method
}

export enum VerifyCodeScene {
  UNKNOWN = 0,
  LOGIN = 1,
}

type WechatyEventListenerVerifyCode = (
  id: string, // verify-code id. When logging in, it is the same with the key of the qr code
  message: string, // message, currently fixed to '请输入企业微信手机端展示的验证码，以继续登录'
  scene: PUPPET.types.VerifyCodeScene, // scene, now the only scene is LOGIN
  status: PUPPET.types.VerifyCodeStatus // scene, now the only status implemented is WAITING
 ) => void | Promise<void>

 // listen to the event
bot.on('verify-code', async (id: string, message: string, scene: types.VerifyCodeScene, status: types.VerifyCodeStatus) => {
  // code here
})

Methods
async enterVerifyCode (
  id: string,
  code: string,
): Promise<void> // enter verify-code

async cancelVerifyCode (
  id: string,
): Promise<void> // cancel verify-code ( will cause the qrcode to refresh )

async refreshQrCode (): Promise<void> // force qrcode to refresh

Notice
When the verify-code event is pushed, the scan event will continue to be pushed （ status 4 Confirmed ）。bot developer should check the id of  verify-code event, and check it with the qrcode of scan event. qrcode is string like https://wx.work.weixin.qq.com/cgi-bin/crtx_auth?key=${qrcodeKey}&wx=1. The qrcodeKey and the id of verify-code event should be the same. If not, it means a new qrcode has been pushed and you should scan again.
Example
Entering verify-code
const store = {}

bot.on('scan', (qrcode: string, status: types.ScanStatus) => {
  if (status === types.ScanStatus.Waiting) {
    // New qrcode
    store.qrcodeKey= getQrcodeKey(qrcode)
  }
}).on('verify-code', async (id: string, message: string, scene: types.VerifyCodeScene, status: types.VerifyCodeStatus) => {
  if (status === types.VerifyCodeStatus.WAITING && scene === types.VerifyCodeScene.LOGIN && id === store.qrcodeKey) {
    const verifyCode = await getVerifyCode() // get verify-code from some async methods, e.g. console input
    try {
      await bot.enterVerifyCode(id, verifyCode) // if no error was caught, it means the verify-code is correct, and the login event should be expected
      return
    } catch (e) {
      console.log(e.message)
      // if there is error, please handle according to the message. Currently you can input 3 times.
      // message keyword: 验证码错误输入错误，请重新输入
      // message keyword: 验证码错误次数超过阈值，请重新扫码
      // currently no ```EXPIRED``` event will be pushed, you should decided from the error message.
    }
  }
})

Refresh Qrcode
await bot.cancelVerifyCode(store.qrcodeKey) // cancel the verify-code according to the key. You'll need to scan again, instead of just refresh the verify-code
await bot.refreshQrCode() // force refresh qrcode

Misc
Please note that the corresponding doc are subjected to change without editing this issue. Please follow the Feishu Doc. Please also expect our TSS (Token Self Service) platform, where you can buy and renew token, and also get latest doc. Coming soon.

How to trigger the scene?

If the verify-code did not show up after you scan the qrcode, then you don't have to bother.