Benefit from name change

Just a suggestion but IMO K-9 Mail is not a name that is easy to remember and I think K-9 Mail  would benefit from changing it to something simpler. I don't have any suggestions yet but will tell you if I think of some.

Your argument doesn't convince me a name change would be a good idea.


Added support for swarm api "Node" field on container

See: https://docs.docker.com/swarm/swarm-api/

LGTM

Hey, thanks for the PR and sorry for the delay.
This library use a generation tool for the low level API, which is based on the swagger (OpenAPI) standard.
Can you edit the docker-swagger.json file as the root of the repository instead of the generated files ?
If you don't know how to do it, don't hesite to ask for help !
Thanks again,

Maybe you should emphasize that in "CONTRIBUTING"... (or have I missed something?)

Maybe you should emphasize that in "CONTRIBUTING"... (or have I missed something?)

Yes it lacks information about it, i'm actually rewriting the /containers/json /container/create part will do the change to CONTRIBUTING in a latter PR

I make the change on 1.24 master along with all the API endpoint for Swarm, CONTRIBUTING.md has been updated to reflect how to work on this repo.
I did not tag this as i want feedback first, but you can test it by using 1.24@dev version in your composer.
Thanks for this PR, i hope the last changes will be good for you.


Switch playpen version to "beta".

Fix #107

r? @brson
(rust_highfive has picked a reviewer for you, use r? to override)


Update dependencies

To help developers realize they should merge into staging before they merge into v2. And to help consumers realize staging might be unstable.
I should probably update the README, but because most people are using this action by referencing byu-oit/github-action-tf-plan-analyzer@v2, the merge into v2 is the big one.
Ideally, we'd want developers to:

Merge into staging
When ready, cut a release tag (v2.0.4)
When ready, promote to v2


Greek Alphabets not getting rendered

Description
The capitalised form of greek alphabets are not getting rendered in the latest version.

$ Alpha Beta Gamma Nu $
Reproduction URL
No response
Operating system
Linux
Typst version

[X] I am using the latest version of Typst

https://github.com/typst/typst/blob/d84a7e423b53e9b5740720270b132da60c8a3fea/crates/typst/src/symbols/sym.rs#L870-L895
I found that this has been not configured correctly.

I guess the characters dont have seperate capital letters defined


Detect combination keys like ctrl+s or ctrl+p

i want to detect ctrl+s i have found a function butt that just detect single key.
below is code for detect single key . my requirement is as above

code sample
import 'package:flutter/material.dart';

import 'package:flutter/foundation.dart';
import 'package:flutter/services.dart';

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

/// This is the main application widget.
class MyApp extends StatelessWidget {
  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      home: Scaffold(
        appBar: AppBar(title: const Text(_title)),
        body: MyStatefulWidget(),
      ),
    );
  }
}

/// This is the stateful widget that the main application instantiates.
class MyStatefulWidget extends StatefulWidget {
  MyStatefulWidget({Key key}) : super(key: key);

  @override
  _MyStatefulWidgetState createState() => _MyStatefulWidgetState();
}

/// This is the private State class that goes with MyStatefulWidget.
class _MyStatefulWidgetState extends State<MyStatefulWidget> {
  // The node used to request the keyboard focus.
  final FocusNode _focusNode = FocusNode();
// The message to display.
  String _message;

// Focus nodes need to be disposed.
  @override
  void dispose() {
    _focusNode.dispose();
    super.dispose();
  }

// Handles the key events from the RawKeyboardListener and update the
// _message.
  void _handleKeyEvent(RawKeyEvent event) {
    setState(() {
      if (event.logicalKey == LogicalKeyboardKey.keyQ) {
        _message = 'Pressed the "Q" key!';
      } else {
        if (kReleaseMode) {
          _message =
              'Not a Q: Key label is "${event.logicalKey.keyLabel ?? '<none>'}"';
        } else {
          // This will only print useful information in debug mode.
          _message = 'Not a Q: Pressed ${event.logicalKey.debugName}';
        }
      }
    });
  }

  @override
  Widget build(BuildContext context) {
    final TextTheme textTheme = Theme.of(context).textTheme;
    return Container(
      color: Colors.white,
      alignment: Alignment.center,
      child: DefaultTextStyle(
        style: textTheme.headline4,
        child: RawKeyboardListener(
          focusNode: _focusNode,
          onKey: _handleKeyEvent,
          child: AnimatedBuilder(
            animation: _focusNode,
            builder: (BuildContext context, Widget child) {
              if (!_focusNode.hasFocus) {
                return GestureDetector(
                  onTap: () {
                    FocusScope.of(context).requestFocus(_focusNode);
                  },
                  child: const Text('Tap to focus'),
                );
              }
              return Text(_message ?? 'Press a key');
            },
          ),
        ),
      ),
    );
  }
}

Hi @abdulrehmananwar
This is currently possible, I updated you _handleKeyEvent function to detect the combination of CTRL + C and CTRL + V. You can test it by replacing your _handleKeyEvent function with the one bellow:
  void _handleKeyEvent(RawKeyEvent event) {
    // capture keys pressed in combination with CTRL
    if (event.isControlPressed) {

      if (event.logicalKey == LogicalKeyboardKey.keyC) {
        setState(() => _message = 'Pressed: CTRL + C');
      } else if (event.logicalKey == LogicalKeyboardKey.keyV) {
        setState(() => _message = 'Pressed: CTRL + V');
      }

    }
  }

Hi @abdulrehmananwar
This is currently possible, I updated you _handleKeyEvent function to detect the combination of CTRL + C and CTRL + V. You can test it by replacing your _handleKeyEvent function with the one bellow:
  void _handleKeyEvent(RawKeyEvent event) {
    // capture keys pressed in combination with CTRL
    if (event.isControlPressed) {

      if (event.logicalKey == LogicalKeyboardKey.keyC) {
        setState(() => _message = 'Pressed: CTRL + C');
      } else if (event.logicalKey == LogicalKeyboardKey.keyV) {
        setState(() => _message = 'Pressed: CTRL + V');
      }

    }
  }

Thanks so much for resolving this issue

Thanks so much for resolving this issue


Add more structure rook code

This PR aims to structure rook code as it was done for kubernetes
The RookBase class is inherited by various implementation of
rook (upstream, ses etc...) and imported as RookCluster

@brunoleon I had to revert this. It broke the caasp deployement due to missing files. See https://github.com/SUSE/rookcheck/pull/72

Please open another PR


Update scalafmt-core to 3.0.8

Updates org.scalameta:scalafmt-core from 3.0.7 to 3.0.8.
GitHub Release Notes - Version Diff
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!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, early-semver-patch, semver-spec-patch

Codecov Report

Merging #208 (aa73f99) into main (1241e2f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #208   +/-   ##
=======================================
  Coverage   88.85%   88.85%
=======================================
  Files          91       91
  Lines        2772     2772
  Branches       70       70
=======================================
  Hits         2463     2463
  Misses        309      309

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 1241e2f...aa73f99. Read the comment docs.


black screen brick

In part3, section IV, setop 10(update sysnand to 11) in a friend nn3ds didn't work, always have an error y the beginning process, so we tried to force the update through the FieldRunners restore firmware, but we failed and now we have a black screen brick :'(, we already tryed every method of the Troubleshooting guide bur didn't work, thanks in advance for any idea!

I'm going to need more details than that.

sorry for the lack of information, this last monday I'm follow your guide step by step, part 1(nn3ds with 11.0 firmware, downgraded with FieldRunners method) and 2 done successfully but when I restore my Sysnand Backup(9.2) the instruction in the section IV step 10 its update to the last version(11.0, 11.1 now.), I tried like a hour but update process always fail and my friend(the nn3ds owner) decided to "force" the update with the backup that we made with field runners, that was a big mistake and we brick(black screen) the nn3ds, we tried every troubleshoting method but all failed and the console didn't reponse :/, thanks in advance for any idea!

Do you have A9LH already installed? If yes, can you boot any payloads?

In theory I have it, but I only triedto load Hourglass but didn't work, do you recommend try with another payload?

Try booting Decrypt9

It sounds like he reflashed his 11.0 NFIRM backup to his sysNAND or used dgtool while having A9LH installed
That's a hard brick right there either way.

I agree @jaxrogers2. Personally, @moking1987, you shouldn't have tried anything which the guide doesn't say.
Try booting w/o the SD card.

Running dgTool while on a9lh = guaranteed brick.


Add the ability to add dependencies to lanes

I added the ability to create dependencies between lanes, see this simple example:

And here it is in action:

I have now added the ability to modify the lane context before the dependencies are run as well. Here's how that looks in a Fastfile:

Maybe someone can come up with a nicer syntax for that? It would definitely be useful I think, but I'm not 100% sure how to do this

:star2:

I had an idea: why do we have its own depends_on block? That requires other lanes to be executed before the actual lanes runs. But it's all about switching lanes, right?
How about we offer a way to switch the lane something like
  desc "Publish a beta build"
  lane :beta do
   certs
   puts "preparing some things"
   build(is_adhoc_build: true)
    # ... Upload to Hockey/Crashlytics/Testflight
  end

This solves our parameter problem and also allows us to do things between 2 lanes are being executed.

Thanks again @milch, I'll close this pull request for now :+1:


[Kernel] Flashinfer correctness fix for v0.1.3

Reported by @felixzhu555 , is_profile_run is buggy in flashinfer backend, which will fail flashinfer v0.1.3. This PR fixes this, and update CI flashinfer version to v1.0.3.

/ready

CI failure seems like a real bug
[2024-08-09T04:52:05Z]   File "/usr/local/lib/python3.10/dist-packages/flashinfer/prefill.py", line 791, in begin_forward
--
  | [2024-08-09T04:52:05Z]     self._wrapper.begin_forward(
  | [2024-08-09T04:52:05Z] RuntimeError: CHECK_EQ(paged_kv_indptr.size(0), batch_size + 1) failed. 1 vs 257

@LiuXiaoxuanPKU It's bugs


doc(index): Update stable

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Which  function is blocking  and which  function is non-blocking?

hello，
I know that cosocket is non-blocking and some stages cannot be used.
I know that luasocket is blocked.
Which  function is blocking  and which  function is non-blocking of Your library?  thanks！

Hello,
Sorry for the delay, I missed this issue. The goal of this project is to always deliver a non-blocking socket, unless your application is in a phase that does not support non-blocking sockets (e.g. init, timer...). If you request a socket in those phases, you will get a warning log (https://github.com/thibaultcha/lua-resty-socket/blob/master/lib/resty/socket.lua#L159) and you can assume the socket will be blocking. That does not matter in the init phase, which is the primary use-case for this library (fallback to LuaSocket in the init phase so that libraries you are using that call ngx.socket.tcp() do not need to be updated to support LuaSocket fallback themselves).


Support ASU9RLS

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
The ASU9RLS3Y is reported by the integration as not supported. I am using the FGLAir app without problems for years now.
Describe the solution you'd like
Support above AC
Describe alternatives you've considered
None
Additional context
None

The ASU9RLS3Y is reported by the integration as not supported.

Hi @chheiss I'm sorry probably I miss something but where's reported that is not supported?

It says: This device is not supported by FujitsuHVAC.

Sorry, is it in this integration reported?

@chheiss I suppose you're referring to this issue: https://github.com/home-assistant/core/issues/125379
In HA 2024.9.0 there's a new integration support for FGLair device. I'm not the maintainer for that HA official integration, you should ask to @crevetor (https://github.com/crevetor).


LiveShare fix

Fix #5887
Do not directly cast to TIn or TOut in implementation of ILanguageServiceProviderCallback, since we no longer have a guarantee that the types passed in will match the types in the version of Microsoft.VisualStudio.LanguageServer.Protocol that we reference. We now convert between the LiveShare types and ours by going through the JSON format, which is stable and backwards compatible.

I've relaunched the build that failed and it passed the second time, though it doesn't show it here.


Add support for YouTube mobile layout

Todo:

[ ] Detect ytm-app tag
[ ] Add settings to video container
[ ] Add missing settings styling
[ ] Test performance on mobile devices

The YouTube settings in the mobile layout are incompatible

The YouTube settings in the mobile layout are incompatible


Crash

Somehow the server crashes after more than 3 zombies start following and fighting you, the log:
FCNPC_MeleeAttack(npcid); 					FCNPC_GoToPlayer(npcid, i);
=========================== FCNPC Exception Handler ============================
Signal 11 (Segmentation fault), address is 2ba9 from f54fe66a

Backtrace:
  #0 in plugins/FCNPC.so(_ZN17CExceptionHandler24ExceptionHandlerCallbackEiP9siginfo_tPv+0x126) [0xf54f9fd6]
  #1 in [0xf77c6d50]
  #2 in plugins/FCNPC.so(_ZN11CPlayerData8GetStateEv+0xa) [0xf54fe66a]
  #3 in plugins/FCNPC.so(_ZN11CPlayerData11GetPositionEP7CVector+0x22) [0xf55001f2]
  #4 in plugins/FCNPC.so(_ZN11CPlayerData16UpdateMovingDataE7CVectorfbff+0x5a) [0xf5500b8a]
  #5 in plugins/FCNPC.so(_ZN11CPlayerData7ProcessEv+0x892) [0xf55037b2]
  #6 in plugins/FCNPC.so(_ZN14CPlayerManager7ProcessEv+0x39) [0xf5504449]
  #7 in plugins/FCNPC.so(_ZN7CServer7ProcessEv+0x4f) [0xf5506c1f]
  #8 in plugins/FCNPC.so(ProcessTick+0x23) [0xf5508153]
  #9 in ./samp03svr() [0x80d1ce2]

Information:
  System: GNU/Linux
  SA-MP: 0.3.7 R2-1
  FCNPC: 1.7.2

Functions:
  FUNC_CPlayerPool__DeletePlayer: 0x80d0a90
  FUNC_CPlayer__Kill: 0x80cb220
  FUNC_CPlayer__EnterVehicle: 0x80cc1c0
  FUNC_CPlayer__ExitVehicle: 0x80cc340
  FUNC_CPlayer__SpawnForWorld: 0x80ccfc0
  FUNC_GetVehicleModelInfo: 0x80d5d30
  FUNC_CConsole__GetIntVariable: 0x80a0070
  FUNC_ClientJoin_RPC: 0x80b0030

Pointers:
  VAR_ServerAuthentication: 0x81aa8a8
  VAR_NetVersion: 0xfd9

Offsets:
  OFFSET_RemoteSystemManager: 0x334
  OFFSET_RemoteSystemSize: 0xc69
  OFFSET_RemoteSystem__ConnectMode: 0xc62
  OFFSET_RemoteSystem__Unknown: 0xc67
=========================== FCNPC Exception Handler ============================

Can you show your pwn code?

http://acesamp.com/code.html

Try to move FCNPC_GoTo function call to the FCNPC_OnSpawn.

I see ColAndreas being used inside do while loop. Try replacing that or adding safety count to avoid server overload that could explain segmentation fault. The only time you would need to use (do)while loop is if you want to pause your app until some criteria has been met, or you want your code to be executed at least once (but then you would add safety against infinite loop and CPU overload).

I found a problem, you go to infinity loop.
Change this line:
while(mZ < 0.001 || distanceM > 2.0 && unBreak < 20);

to this:
while((mZ < 0.001 || distanceM > 2.0) && unBreak < 20);


⚠ Bofrost.at has degraded performance

In beaa6b8, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1992 ms

Resolved: Bofrost.at performance has improved in 244ba92 after 6 minutes.


Must ignore .svg images as non-bitmap assets

Many websites combine .png and .svg graphix for some reasons.
Retinajs when applied tryes to load @2x.svg. But that makes no sence. Leads to wasted requests.
Must totally ignore vector mime-types.

You can exclude svg images replacing line 42 in src/retina.js
original:
                    if (image.src) {

replaced:
                    if (image.src && !!!image.src.match(/\.svg$/i)) {

Definitely I can patch the code for my own use. And I did so. But other people should do the same, so i have opened this issue. Get it right.

Can't this be fixed? I mean I'd pull request it but you have the change right there. SVG obviously should be ignored.

Retina.js is no longer being maintained (last commit was over a year ago), and no maintainers are coming to the forefront, so I'd suggest you create a fork if you want a change.


AWS S3 Sample project missing

I'm following this AWS tutorial made by Amazon:
https://youtu.be/cJG-nLw0FJE?t=225
They use the AWS S3 Sample project from AWS Tools for Visual Studio
However the project no longer appears to exist. How can I access this project now from VS 2019 Community?

Hi @niico100 , the sample projects have been removed from the Toolkit since that video was posted.
If you create a regular C# Console application and add NuGet package references for the AWS SDK (for example S3 is AWSSDK.S3), there is .NET sample code in the S3 docs that you can add to your project and explore. For example, this page shows how you can list the objects within an S3 bucket.

Not quite as super convenient but good enough thx.


Unmet peer Depency

install following Docs http://docs.apollostack.com/apollo-client/angular2.html
if installed npm install angular2-apollo --save npm say cannot install apollo-client
after npm install apollo-client --save can install apollo-client but you run build app says  node_modules/apollo-client/QueryManager.d.ts(6,60): error TS2307: Cannot find module 'graphql'.
After this error i'm install Graphql on npm install graphql --save Error still same
node_modules/apollo-client/QueryManager.d.ts(6,60): error TS2307: Cannot find module 'graphql'.

Typings for graphql are missing so try to run:
typings i -S graphql

Thanks @kamilkisiela
Problem solved but new error  Same folder QueryManager.d.ts
pollingTimers: {
[queryId: string]: NodeJS.Timer | any;
};
apollo-client/QueryManager.d.ts(16,28): error TS2503: Cannot find namespace 'NodeJS'

@SerkanDayicik Yes :) In one of the recent releases of apollo-client there was a change that requires to install typings for nodejs.
typings i -SG env~node

You can always take a look at the example projects that use apollo-client.

GitHunt | Angular2
GitHunt | React

@kamilkisiela  Problem solved i try angular.rc.5 on apollo client but no luck Typings error coming all time maybe try starter project and update angular latest version thank you

@SerkanDayicik You can checkout my starter kit for angular2-apollo.
https://github.com/kamilkisiela/angular2-apollo-starter

But yes, RC5 breaks everything :) I'm going to work on it soon.


[Experiment] Test libsql

Libsql is a fork of sqlite which provides more interesting features like built-in replication and remote access.
Not sure how stable it is on Uptime Kuma, going to find out here.
https://github.com/tursodatabase/libsql

Close as the libsql knex adapter currently is quite buggy. The connection pool is not working correctly.


Audit for ptr_guaranteed_<cmp>

Description of changes:
Completes the audit for ptr_guaranteed_<cmp>. These behave as regular pointer comparison at runtime.
Resolved issues:
Part of #727
Call-outs:

Testing:

How is this change tested? Adds 2 tests.

Is this a refactor change? No.

Checklist

[x] Each commit message has a non-empty body, explaining why the change was made
[x] Methods or procedures are documented
[x] Regression or unit tests are included, or existing tests cover the modified code
[x] My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

The PR is ready to review again.
We had a discussion where we agreed that these intrinsics should be implemented as regular comparison instead of being over-approximated, otherwise we get nondet. results for comparison like ptr::is_null. This has been noted in both the Kani documentation and code.

Merging this PR now, but if you have any other concerns please let me know and I'll take care of them.


Update HDK to support config structure + use latest jit-engine

@kurapov-peter @Garra1980 @ienkovich I removed the pytest changes from this PR so we could get our main branches resynced. I put the pytest work in alex/pyhdk_github_actions for now.


Feat: Add Dark mode

Describe the feature
In this feature, I want to add a dark mode option to your website, allowing users to switch the theme from light to dark.
Add ScreenShots
https://github.com/Anushkabh/krishiconnect/assets/115486960/470a43a4-e7d4-4f3d-a003-d23197d3ecd1
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

I would like to work on this . Please could you assign me this issue under GSSOC'24

@Anushkabh  kindly assign me this issue under GSSOC'24.


test_client cannot connect with nginx-quic becauseof validate token failed

Discussed in https://github.com/alibaba/xquic/discussions/87

Originally posted by innocenceman February 16, 2022
What happened?
xquic client connect to nginx-quic failed, and there is a error "quic garbage token while handling initial packet" in error.log
xquic was built with boringssl, and the client is test_client, client show "conn errno:11" in the end.
Steps To Reproduce
download nginx-quic with version release-1.21.6, build and install it, run nginx
with nginx.conf:"listen 8443 http3 reuseport".
use test_client(command line: ./test_client -a xxx.xxx.xxx.xxx -p xxxx -G -l e -u https://www.xxxxx.com/) to request nginx-quic server.
thanks
xquic.zip

how does the token was generated? if it was not generated by nginx-quic, that might be happen, and shall be deleted.

as well as the transport parameter and the session ticket, just if they are from another implementation

I don't know how how does the token was generated, is xquic doing that in handshake? it look likes not generated by nginx-quic.
and i use chromium client(quic_client) connect to nginx-quic, is ok, is there somthing wrong to use Xquic?

token was generated during the previous connection with NEW_TOKEN frame from server. xquic has its own way to generate a NEW_TOKEN, and it is not compatible with other implementations. I think you might connected to test_server before and then use xquic's NEW_TOKEN in the connection to the nginx-quic server.

I don't know how how does the token was generated, is xquic doing that in handshake? it look likes not generated by nginx-quic. and i use chromium client(quic_client) connect to nginx-quic, is ok, is there somthing wrong to use Xquic?

Yes, i have connected with test_server before nginx-quic, and I found the "xqc_token" file in the root directory,when i delete it, it is successed to connect with nginx-quic.Thank you for your answer.
And there is another question, Is the xquic token format standard?
Why is it incompatible with other software?
Is there a document that to learn it?

token was generated during the previous connection with NEW_TOKEN frame from server. xquic has its own way to generate a NEW_TOKEN, and it is not compatible with other implementations. I think you might connected to test_server before and then use xquic's NEW_TOKEN in the connection to the nginx-quic server.

I think there should be a note here in Testing-zh.md or somthing another file, It will cause problems for other users.

xquic has its own way to generate a NEW_TOKEN, and it is not compatible with other implementations

it's noted in Troubleshooting-zh.md, but your idea is much better

NEW_TOKEN and Retry token is not defined by rfc9000, implementations will define their own tokens.
8.1.1.  Token Construction
A token sent in a NEW_TOKEN frame or a Retry packet MUST be
constructed in a way that allows the server to identify how it was
provided to a client.  These tokens are carried in the same field but
require different handling from servers.


Refactor publisher_config

Changes

Collect the publisher configurations in the ConfigRoot in publish struct variable.
Rename init in model_nodejs to init_nodejs to be clear.
Refactor the code to take the publisher configuration from a file if existed otherwise set it with the old values as default values.
Remove unwanted function calls and variables that are no longer used.
Make sure that all variables are named correctly after refactor.
Get NodeJS configurations from a file if existed otherwise set it with the old values as default values.
Get Site configurations from any JSON file start with site_ or sites and  append all configurations in SiteConfig array

Related Issue
#17

probably a mistake
but I saw the other branch was just further than this one?


Support Server Policies

Have had a look through open issues. Not sure if it's been mentioned before.
https://docs.microsoft.com/en-us/windows-server/networking/dns/deploy/dns-policies-overview
At the moment, we are looking at implementing a policy for a specific use case. However it's all PowerShell configured. I was considering writing a custom script that DSC could run for certain servers to "self configure" but then started digging in to the DSC resource.
Has anyone been looking at this at all? I've not written a DSC resource before but can make an attempt at it.

A contribution would be welcome indeed. More than happy to support such an effort :)

Thank you @indented-automation
So, I have forked this off, created a folder (MSFT_xDnsServerClientSubnet) and created the file MSFT_xDnsServerClientSubnet.psm1 here https://github.com/1800Zeta/xDnsServer/tree/DnsServerPolicies/DSCResources/MSFT_xDnsServerClientSubnet
Do I need to have all aspects of DNS Policies working before I look to do a PR or once I am happy this works will just this be OK for now? Sorry for the Q's first time doing this
Thanks

@indented-automation once I have completed the Zone Scopes, the next task is to modify the Resource Records. Which one should I use? DNSRecord or DNSARecord? I saw some discussion on these two resources and would like to double check. Thank you

As per your question. xDnsRecord is the one that replaces xDnsARecord. xDnsARecord will be removed on the next release.
Where are we with this issue? Is there still something we are tracking with it? I see several PR's have been merged that references this one.

I'm closing this issue for now, please reopen if something else must be discussed in this issue. If there are more resources that should be created, please open new issues, one per resource to propose using the template for resource proposals.


[vNext Tokens] Use new token system for FluentButton

Platforms Impacted

[x] iOS
[ ] macOS

Description of changes
This converts FluentButton to use the new token system. It's one of the most complex controls in the library (competitive with Avatar), which means updating it requires the most churn, but also has the largest binary size improvement (spoiler: we're saving well over a half megabyte!).
Quick rundown of notable changes:

Deleted generated MSFButton tokens.
Revamped ButtonDemoController to properly store the MSFButton objects being presented.

Verification
In addition to the considerations below, the following were tested:

Pixel-perfect alignment, with the exception of known bug fix for inter-element padding.
Color swapping (blue to green, light to dark).
Proper large content viewer for floating buttons.

Before
After

31,767,518 bytes (30.3 MB)
31,143,070 bytes (29.7 MB)

Delta: 624,448 bytes, or ~610 KB 🥳
Pull request checklist
This PR has considered:

[x] Light and Dark appearances
[x] iOS supported versions (all major versions greater than or equal current target deployment version)
[x] VoiceOver and Keyboard Accessibility
[ ] Internationalization and Right to Left layouts
[x] Different resolutions (1x, 2x, 3x)
[x] Size classes and window sizes (iPhone vs iPad, notched devices, multitasking, different window sizes, etc)
[x] iPad Pointer interaction
[x] SwiftUI consumption (validation or new demo scenarios needed)
[ ] Objective-C exposure (provide it only if needed)

Microsoft Reviewers: Open in CodeFlow

(Apologies if you saw an unrelated change merge into this branch; it's been removed!)


Async routes/handlers halt in dev but work in non-dev when using got

I'm building a fresh app with an external lib that depends on got, a node HTTP library.
I had already tested that lib in Deno and it works. esm.sh and Deno do their thing, and there are no issues with the lib or got.
But I found a strange behavior while building my app in Fresh with it. The lib works while in non-dev (deno run -A main.ts) but doesn't in dev (deno task start). In dev the request halts and doesn't resolve or throw, leaving Fresh in a suspended state. i.e., if I add the lib to the page middleware or handler, the page never loads. In non-dev everything just works as expected.
Debugging it seems the issue is caused by got. I've put this repo where you can repro the issue. The additional files over a fresh fresh install are in routes/got and routes/fetch. The got routes work only in non-dev, while fetch works in dev and non-dev.

After playing around with esm.sh params, adding ?target=deno seems to solve the issue for this lib (and got). In dev everything works as expected.
Still, it would be nice to have an error message while in dev. It took me a while to figure out what was happening. Feel free to close the issue if you want.


Can't close JFXDrawer when one of its elements is clicked

Hello!
I'm trying to close a JFXDrawer when one of the elements in its JFXListView is clicked. Unfortunately, when I click an element, the closing animation plays but the JFXDrawer re-opens itself immediately after the end of the animation.
My implementation is close to the demo folder of this repo, with the following changes:
In MainController.java, after the initialization of the context attribute:
        ...
        context.register("drawer", drawer);

        // set the default controller
        ...

In SideMenuController.java, replace the bindNodeToController method with:
        ...
        private void bindNodeToController(Node node, Class<?> controllerClass, Flow flow, FlowHandler flowHandler) {
            flow.withGlobalTaskAction(node.getId(), () -> {
                JFXDrawer drawer = (JFXDrawer) context.getRegisteredObject("drawer");
                drawer.close();
            });
        }
        ...

Am I doing something wrong? Is there another way to implement this feature? I'm using Java 11 with OpenJFX 11 and JFoenix 9.0.8
Thanks,
William

Hello,
Maybe someplace in your code, you are recalling the open/toggle method.

Hello,
The rest of the code is strictly identical to the one in the demo folder. I only have one other toggle/open in the code (in the MainController.init method, inside the titleBurgerContainer.setOnMouseClicked) but it isn't called when I click an element of the JFXListView.
I have just found out that sometimes, randomly, the drawer behaves the right way. It isn't dependent to the element clicked but happens more often the first times I click one of them.

@WilliamAboucaya can provide SSCCE demonstrating the issue?

@jfoenixadmin Sure! It is available in this repo: [https://github.com/WilliamAboucaya/jFoenixBugSSCCE/tree/master]

Try removing sideMenuFlowHandler.handle(newVal.getId()); it might solve the issue.
I'll close this issue as it seems related to DataFX usage.
Regards,

Thanks for the reply but this is not solving the issue, it is just disabling the bugged feature.
I will try to find a solution and eventually post it on this issue.
Regards,


[Bug Fix] "tooltip is not a function" in analytics V2

Addresses: https://github.com/restarone/violet_rails/issues/1609
Demo Clip
https://github.com/restarone/violet_rails/assets/25191509/f8368c2b-e072-4b5c-b9e9-bff3ee17c42a

@alis-khadka I noticed that the Shortcuts button (to show expansion for web/forum etc) does not work in any other view than Analytics V2. It looks like Bootstrap JS is not loading everywhere in the CMS admin. Could you take a look?

patch PR: https://github.com/restarone/violet_rails/pull/1612


Feature request: Healthy Food Data Analysis and Prediction

Is your feature request related to a problem? Please describe.
This will provide a detailed analysis of nutritional content, and their cultural significance also.
Describe the solution you'd like
I will use Matplotlib and Pandas for the analysis and machine learning algorithms for the prediction.
Describe alternatives you've considered
I will use different-different algorithms for the best prediction.
Approach to be followed (optional)
A clear and concise description of the approach to be followed.
Additional context
Add any other context or screenshots about the feature request here.

Hey @avii-07, can you share the progress of this project?

I will submit it today


Docker images for GitLab CI

Link to suggestion
https://gitlab.com/quarto-forge/docker
Targeted section
Continuous integration / Continuous deployment
Describe your suggestion
This is shameless self promotion. :-D
This is a collection of Docker images for people that want to use Quarto in GitLab CI.
Checklist

[X] checked if your suggestion is not already listed in Awesome Quarto list.
[X] checked if it can fit in an existed section or open a discussion to suggest any new sections..
[X] checked when it's a repository if it's maintained (archived repository will be rejected).

Thanks for the suggestion!
Could you develop a bit the purpose of your Docker images in the context of Quarto and also how it differs (or not) from the Docker images from https://rocker-project.org/ which now include Quarto along with several other tools?

Could you develop a bit the purpose of your Docker images in the context of Quarto

I wanted a "small" image to build documents to HTML and other formats.

how it differs (or not) from the Docker images from https://rocker-project.org/

rocker is a great project and I got inspiration from it. rocker is focus on R and R Studio. I'm also looking at Python.

Ok, I'll need to think more about this, because it might require a new section and some other item might also be needed into that section.

I don't think I am not going to add Docker images (this one or others) to Awesome Quarto, since it's not focused on Quarto.


"Keras.wrappers"  in 'python IDLE 3.12.0'

I was trying to apply a L layer neutral network training and testing with a dataset, however there is some issues when importing keras.wrappers (keras.models and keras.layers were fine when I try to import them)
In CMD I have exercised:
pip install --upgrade keras
pip install --upgrade tensorflow
pip install --upgrade scikit-learn
pip show keras #version 3.3.3
pip show tensorflow #Version: 2.16.1
pip show scikit-learn #Version: 1.5.0
In python
from keras.models import Sequential #no problem running this code
from keras.layers import Dense #no problem running this code
problem starts here:
from keras.wrappers.scikit_learn import KerasClassifier
#ModuleNotFoundError: No module named 'keras.wrappers'
from tensorflow.keras.wrappers.scikit_learn import KerasClassifier
#ModuleNotFoundError: No module named 'tensorflow.keras.wrappers'
from keras.scikit_learn import KerasClassifier
#ModuleNotFoundError: No module named 'keras.scikit_learn'
I have sklearn also installed,  to use the cross_val_score model, does that conflict with installation package with keras/tensorflows?

tried different codes to import keras.wrappers but all failed, the versions of keras, tensorflow and scikit_learn are the most updated, please help xDDDDD

@minqichen12138,
Could please try to install scikeras using pip install scikeras and then import from scikeras.wrappers import KerasClassifier?

from scikeras.wrappers import KerasClassifier

it works!!! thank you !!!!

It is still not working for me, I isntalled scikeras but it is still giving errors

ImportError                               Traceback (most recent call last)
Cell In[20], line 1
----> 1 from scikeras.wrappers import KerasClassifier
File /opt/anaconda3/lib/python3.11/site-packages/scikeras/wrappers.py:35
33 from scikeras.utils import loss_name, metric_name
34 from scikeras.utils.random_state import tensorflow_random_state
---> 35 from scikeras.utils.transformers import ClassifierLabelEncoder, RegressorTargetEncoder
38 class BaseWrapper(BaseEstimator):
39     """Implementation of the scikit-learn classifier API for Keras.
40
41     Below are a list of SciKeras specific parameters. For details on other parameters,
(...)
124         The number of features seen during fit.
125     """
File /opt/anaconda3/lib/python3.11/site-packages/scikeras/utils/transformers.py:12
10 from sklearn.base import BaseEstimator, TransformerMixin
11 from sklearn.exceptions import NotFittedError
---> 12 from sklearn.pipeline import make_pipeline
13 from sklearn.preprocessing import FunctionTransformer, OneHotEncoder, OrdinalEncoder
14 from sklearn.utils.multiclass import type_of_target
File /opt/anaconda3/lib/python3.11/site-packages/sklearn/pipeline.py:16
13 import numpy as np
14 from scipy import sparse
---> 16 from .base import TransformerMixin, _fit_context, clone
17 from .exceptions import NotFittedError
18 from .preprocessing import FunctionTransformer
ImportError: cannot import name '_fit_context' from 'sklearn.base' (/opt/anaconda3/lib/python3.11/site-packages/sklearn/base.py)

above is on macOS

@whitemountainanalytics , Could you please create a new issue. Thanks

same question
ImportError: cannot import name '_fit_context' from 'sklearn.base' (/opt/anaconda3/lib/python3.11/site-packages/sklearn/base.py)


Access variables in certain resource or variable file using ${my_resource.My Variable} syntax

If several resource and/or variable file have same variables, the ones in the file imported first are taken into use. Actually, we need those variables have their own namespaces to distinguish each other. Maybe support "private variable" or operation like "module.variable" to distinguish variables have the same name.

Changing variable priorities is not possible because it would be massive backwards incompatible change.

Private variables would be nice, but I'm afraid that would be too big change to be implemented in the near future. The main problem would be that they'd require some kind of a special syntax.

Accessing variables defined in a certain variable/resource file using syntax like ${my_resource.Variable Name} (or perhaps something like ${my_variable::Variable Name} to separate this from the extended variable syntax) would probably be the easiest solution. Unfortunately the original source of variables isn't available currently, so also this is going to require quite a big changes. We already have some related changes targeted to RF 2.9 so I'll tentatively assign this to that milestone.

${my_variable::Variable Name}, is it possible to support syntax like ${SELF::Variable Name}? so it means only search variable from local resource file

${SELF::Variable Name} or some other special syntax to refer variables in the same file would be a good idea.

I prototyped implementing this and found out that a real implementation requires so big internal changes that we don't have time for them in RF 2.9 scope. We are going to have RF 3.0 still this year and this will be one of the critical issues in that.

if this gets implemented sometime, please check if it is feasable to add support for custom names for resources. Eg.
Import Resource path/to/resource.txt AS my_resource

Then you can use
${my_resource.variable name}

Because this will then solve the problem with duplicate resource filenames. See
https://groups.google.com/d/msg/robotframework-users/0Cb215YSnG4/mWpGHi5dwUwJ

That's a good idea. Should probably be a separate issue, but naturally this one is a precondition because otherwise such support wouldn't give any benefits. Instead of AS we probably should use WITH NAME that also libraries support. If AS is considered much better, we should then change libraries to use it too.

no, i was confused. my intention was to use the same syntax as for the library imports. so "with name" is fine.

No time for this in 3.0.

I don't have time for this in RF 3.1. Descoping.


Action-SpigotMC#136:  Check if ncc can be replaced with esbuild

Thanks in your interest in contributing to this project!
Due to inactivity, I'll be closing this Draft PR.


nagios-style check for jetstream responder found

The nats server check connection mode is really helpful.  I'd like a Jetstream equivalent.
If I can supply a context or creds for a monitoring account, and also --js-domain, as I can now, to target which jetstream leafnode I'm talking to, then a nats CLI mode which can check for there being a jetstream responder will let me monitor jetstream being "up" and plug this into any NAGIOS-compatible setup.
A bonus would be if it can take the max available space for disk/mem and the used space and transition into warning state if the available space is less than a given percentage (CLI-overrideable in the usual manner).

Sounds to me like these are the same - account info end point will tell us its up and also the metrics, so seems I can combine them into one.
Good idea, will add.

$ nats server check js --help
...
      --mem-warn=75             Warning threshold for memory storage, in percent
      --mem-critical=90         Critical threshold for memory storage, in percent
      --store-warn=75           Warning threshold for disk storage, in percent
      --store-critical=90       Critical threshold for memory storage, in percent
      --streams-warn=-1         Warning threshold for number of streams used, in percent
      --streams-critical=-1     Critical threshold for number of streams used, in percent
      --consumers-warn=-1       Warning threshold for number of consumers used, in percent
      --consumers-critical=-1   Critical threshold for number of consumers used, in percent

Merged in https://github.com/nats-io/natscli/pull/169


Make astroturf framework agnostic

I want to use astroturn in solid-js.

I found the 'jsxPragma: false' fit my need.


Port to Vaadin 13

I have started with a Polymer 2 based web component and it seems to be ok to load Cleave through that web component and attach it to a TextField

Master is now for Vaadin 13. Alpha level still, but moving forwards.


Feature Request - Add search button

Steps to reproduce
Expected Behavior
Positive Test Case
Actual Behavior

Add a search button that will allow users to "re-search" their criteria for another area.  This is necessary when the user changes the extent of the map.


Support subscribing with keypaths in Swift 4

It would be nice to be able to subscribe to more specific items in the state using keypaths added in Swift 4.  Example of how they were adopted in The SDKs here: https://developer.apple.com/library/content/documentation/Swift/Conceptual/BuildingCocoaApps/AdoptingCocoaDesignPatterns.html#//apple_ref/doc/uid/TP40014216-CH7-ID12

Hi, @kdawgwilk. Could you explain a little more how the use of keypaths would improve the library? Thanks!

Yeah so here is a brief example:
Goal
Be able to subscribe with finer grain using KeyPaths like this:
store.subscribe(self, to: \AppState.someSubState.property)

Implementation Example
Added Store.swift method:
open func subscribe<V, S: StoreSubscriber>(
    _ subscriber: S, to keyPath: KeyPath<State, V>
) where S.StoreSubscriberStateType == V {
    // If the same subscriber is already registered with the store, replace the existing
    // subscription with the new one.
    if let index = subscriptions.index(where: { $0.subscriber === subscriber }) {
        subscriptions.remove(at: index)
    }

    let value = state[keyPath: keyPath]
    print("Value being observed: \(value)")

    // Details left out
}

The complete implementation might look like this?
``swift
open func subscribe<V: StateType, S: StoreSubscriber>(
_ subscriber: S, to keyPath: KeyPath<State, V>
) where S.StoreSubscriberStateType == V {
// If the same subscriber is already registered with the store, replace the existing
// subscription with the new one.
if let index = subscriptions.index(where: { $0.subscriber === subscriber }) {
subscriptions.remove(at: index)
}
// Create a subscription for the new subscriber.
let originalSubscription = Subscription<State>()
let transformedSubscription = Subscription<V>()

let subscriptionBox = SubscriptionBox(
    originalSubscription: originalSubscription,
    transformedSubscription: transformedSubscription,
    subscriber: subscriber
)

subscriptions.append(subscriptionBox)

if let state = self.state {
    originalSubscription.newValues(oldState: nil, newState: state)
}

}

FYI: I also support this in my library https://github.com/svdo/ReRxSwift.

@kdawgwilk thanks! Yeah, I think store.subscribe(self, to: \AppState.someSubState.property) would be a small but nice syntax improvement to the current way of subscribing using the closure.

Is this being proposed to be alongside the existing selection method, or instead of? The one thing this lacks is selection of multiple portions of state at once. Otherwise it looks good. If the proposal is in addition to the existing selection methods then I would recommend moving this to a PR, and using #if swift(>=4.0) to ensure we don't break 3.2 compatibility.

Uh, that's true. I wouldn't use it unless it would replace the current implementation, improving it somehow. If that's not the case I'd rather keep a minimal API surface.

This addition would not support multiple selections and if that was needed it would be best to just subscribe to a substate that contains everything you need.  I am not sure if there would be a way to receive changes to more than a single subscription endpoint.  Since the item you subscribe to is passed as a single method parameter.  It would interesting to see if you could subscribe twice and implement two different methods that would get called for each specific item that was subscribed.  Does the current implementation support subscribing to more than one substate?

AFAIK, I think current implementation doesn't support subscribing to more than one substate. I also prefer not to keep both implementation at the same time. Maybe this proposal good for v5.0 (don't know is there a plan for that) as breaking change.

Right now you can return whatever you want from the select function when you create a subscription. There, you have access to your whole state, and you can map it to an object including only the substates you care about for that subscription. Note that this doesn't mean you subscribe more than once.

Ah that makes sense, I am not sure how a similar concept would be possible using keypaths

Since there was no progress on this for a year, I'll close the issue for now.


Control the headers that the proxy backend forwards to the target

The proxy backend uses https://github.com/chimurai/http-proxy-middleware to implement the proxy functionality. However, in its current state, it forwards all request headers to the proxy-target. This includes headers that are not meant for the other API, like Cookie, but also others that are injected by identity-proxies (X-Auth-Request-User, X-Auth-Request-*, ...).
Feature Suggestion
Configure the proxy middleware to not forward certain headers.

Possible Implementation
There are different approaches for solving this:

Hard code a list of non-forwarded headers (Cookie).
Make it configurable and decide about a reasonable default.

One option could be to specify a custom onProxyReq handler and modify the request. This should of course not override the values that are added in the headers config.

If we agree on a solution, we would be happy to contribute the implementation.

Looks like headers are copied unconditionally, https://github.com/http-party/node-http-proxy/blob/9b96cd725127a024dabebec6c7ea8c807272223d/lib/http-proxy/common.js#L43`
I would imagine it makes sense to explicitly have to allow headers, except for a couple of defaults like Host, Accept, etc.

I would imagine it makes sense to explicitly have to allow headers

So are we going into the direction of an allow list with a predefined set of safe headers? If yet, than I guess we can do an implementation.

Since the Host header is already rewritten to the target by default so this should be safe to forward.

I would definitely prefer an allowlist as well.

I say we

I would imagine a sane set to always allow headers would be any header crucial to the proxying functionality, like Host, along with the headers that are allowed by default in CORS?

CORS is a great idea. I tried to find references on what headers might be safe in such scenarios, but didn't found the right google search for that. But https://fetch.spec.whatwg.org/#cors-safelisted-request-header seems like a good start.


Replace ts-mockito with jest-mock-extended

Discussed in https://github.com/archimedes-projects/archimedes-js/discussions/5

Originally posted by esuca July 27, 2021
In almost all of the projects that we use archimedes-js we also use ts-mockito for mocking commands, queries, etc.
A few months ago I discovered and used in a few projects jest-mock-extended library, which provides type-safe mocking extensions for Jest, allowing us to use the Jest APIs for all of our mocks.
jest-mock-extended is downloaded almost 160.000 times per week and has a more active development than ts-mockito.
Today I had a conversation with @cesalberca about replacing ts-mockito with jest-mock-extended in new projects and he suggested creating a new discussion here for all.
Code example:
class FirstQry {
  constructor() {
  }

  execute(param: { foo: boolean }) {
    return param.foo ? 'isFoo' : 'notFoo'
  }
}

class SecondQry {
  constructor(private firstQry: FirstQry) {
  }

  execute(foo: boolean) {
    return this.firstQry.execute({ foo })
  }
}

test('mocking example with ts-mockito', () => {
  const firstQryMock = mock(FirstQry)
  const secondQry = new SecondQry(instance(firstQryMock))

  when(firstQryMock.execute(deepEqual({ foo: false }))).thenReturn('mocked')

  const result = secondQry.execute(false)
  expect(result).toBe('mocked')

  verify(firstQryMock.execute(deepEqual({ foo: false }))).once()
})

test('1. mocking example with jest-mock-extended following its documentation example', () => {
  const firstQryMock = mock<FirstQry>()
  const secondQry = new SecondQry(firstQryMock)
  // @ts-expect-error mockReturnValue or mockReturnValueOnce expect the return value to be 'isFoo' or 'notFoo'
  // firstQryMock.execute.mockReturnValueOnce('mocked')
  firstQryMock.execute.mockReturnValue('mocked')

  const result = secondQry.execute(false)
  expect(result).toBe('mocked')
  expect(firstQryMock.execute).toHaveBeenCalledTimes(1)
  expect(firstQryMock.execute).toHaveBeenCalledWith({ foo: false })
})

test('2. mocking example with jest-mock-extended using calledWith to match an object argument', () => {
  const firstQryMock = mock<FirstQry>()
  const secondQry = new SecondQry(firstQryMock)
  // @ts-expect-error mockReturnValue expect the return value to be 'isFoo' or 'notFoo'
  firstQryMock.execute.calledWith(myDeepEqual({ foo: false })).mockReturnValue('mocked')

  const result = secondQry.execute(false)
  expect(result).toBe('mocked')
  expect(firstQryMock.execute).toHaveBeenCalledTimes(1)
  expect(firstQryMock.execute).toHaveBeenCalledWith({ foo: false })
})

export const myDeepEqual: <T>(expectedValue: T) => Matcher<T> = expectedValue =>
  new Matcher(actualValue => JSON.stringify(actualValue) === JSON.stringify(expectedValue))

Advantages of jest-mock-extended over ts-mockito:

Provides a familiar Jest like API. We don't need to learn another library.
With ts-mockito we need to wrap our mock with the instance() method to make it work. Sometimes we forget to wrap it and ts-mockito does not warn us about it. With jest-mock-extended there is no need for a wrapper, we can pass directly the mock.
ts-mockito verify error message does not include the actual calls with the arguments, it only provides us basic error message with the expected times call and the actually called times, making debugging harder.
Supports mocking interfaces, functions, deep objects, and class instances.
Provides complete Typescript type safety for interfaces, argument types, and return types.

Disadvantages of jest-mock-extended over ts-mockito:

By default ts-mockito is matching the arguments by reference, and when we want to match for arguments equality, deepEqual() method is used. ts-mockito's deepEqual is not documented yet.
Most of the time with jest-mock-extended expecting an argument matching is not necessary, because we can mock directly the function call and later assert that was called correctly as shown on the first jest-mock-extended test. But if we need it, the behaviour of jest-mock-extended is the same as ts-mockito and we could use any of the available jest matchers, like, containsValue('value') or create our own deepEqual method as I did on the second jest-mock-extended test.
jest-mock-extended uses the Jest assertion API and there is no toHaveBeenCalledWithOnce() assertion method that combines the
toHaveBeenCalledTimes(n) and toHaveBeenCalledWith(value) into one single assertion... There is something similar, but not as semantic: expect(firstQryMock.execute).toHaveBeenNthCalledWith(1, { foo: false }). We could wrap it with our own assertion to give it a better naming.

These disadvantages are more limitations of the Jest API than of the library itself... And all of them have an easy workaround.
After using it in a few projects, I noticed that the tests code is cleaner and the debugging is easier because of better assertions error messages and the IDEs integration with the Jest APIs.
What do you think about using jest-mock-extended in new projects?

@esuca It seems that jest-mock-extended doesn't support mocking getters or object's properties. We need that functionality. Are there any workarounds?


S3E16 AMC Meeting (CV) Announcement

AMC Meeting Announcement

S3E16
Season 3 Episodes 16

Date
7-10 pm, Sunday

Location
821, 8th floor, BUPT Research Building

Chairman
@gaojiuy

Vice-chairman
@Leona08

Previous Meeting

Minutes
Link

Blog
S3E12 (Season 3 Episodes 12)

Issue
#407

Agenda
1. Poster

Presenter
Paper

@gaojiuy
Visualizing Deep Neural Network Decisions: Prediction Difference Analysis

3. After Party
Everyone will be welcome. You can join or not join as you want (not required by the AMC), and change your mind at any time.

After Party will be started right after all the meeting agenda had been fulfilled.
We will find a bar and drink beers and talk whatever we want. (we can expect that it will be related to meeting topics of the day)
The bill will be paid AA

Confirmed Attendees

Role
People List

🧓 Chair
@gaojiuy

🧑 Vice-chair
@Leona08

📰 Posters
@gaojiuy

Poster - Deep Learning in Spiking Neural Networks (Round 1) #431
@gaojiuy


Add 'make android' target and document it

This is a bit hacky but hides some of the ugly cruft from the instructions.

LGTM


Don't use regenerator in babel-preset-es2015 for newer Node.js versions

Split out of https://github.com/sindresorhus/ava/pull/333.
Only Node.js 0.10 needs regenerator, but it's currently included for any Node.js version.
Someone needs to do a pull request to babel-preset-es2015 and auto-detect generator support and conditionally include regenerator (preferred solution) or add an option for toggling regenerator.
// @thejameskyle @jamestalmage

What do you think about using a post install script ?
Noticed the following discussion: https://github.com/npm/npm/issues/7340

@thedev This isn't about having regenerator as a dependency. We just don't want the runtime overhead of using regenerator when it's not needed for newer Node.js versions which supports generators.

Someone needs to do a pull request to babel-preset-es2015 and auto-detect generator support and conditionally include regenerator (preferred solution) or add an option for toggling regenerator.

The Babel preset would not accept a pull request for that, just because the environment that is running Babel supports generators does not mean the targeted environment will.
If you want to create a preset babel-preset-node-feature-detection that tests for support for everything before running it, that would likely be the best solution. However, it should warn heavily that you should not distribute the generated code with it (we don't want npm filled with node version specific modules).

@thejameskyle That's a good point. I just considered our case of live transpiling. Would you be open to add an option to the preset for toggling regenerator? We really don't want to have to maintain our own presets.

https://phabricator.babeljs.io/T2756

@sindresorhus: Check out hax/babel-features. I'll turn it into a preset if you want. Or we could just use it directly.

@sindresorhus: Actually, I went ahead and turned that into a preset anyway: babel-preset-features. It's a drop-in replacement for babel-preset-e2015, I'll submit a PR.

I ran into the same issue, went with https://github.com/alekseykulikov/babel-preset-es2015-node5 for now

@tmaximini What issue? The only difference should be one of performance. If you've got other issues let us know.

Closing in favor of #148.

@jamestalmage performance always matters, and it's always good to have as much as possible a generated code side-by-side with the source one.
If we have native support, we should always use it, there is absolutely no reason to use something ugly and gross on top of something that already exists and performs well.
I can understand people using bluebird instead of the native Promise, for example, but using a feature like regenerator, only if targeting browsers.
Another great difference: Debugging is terrible with regenerators, and it's awesome with native generators.


Confusion on embedding.deepgl adaptation

There exists a 1.0.2 tag, but the project seems to only build a 1.0.1 version of the jar file. Also, whether I download the existing 1.0.1 release or build the 1.0.2 tagged version of the code, then upload the jar file into the plugins folder, and update the neo4j.conf file as such:
dbms.security.procedures.whitelist=regression.*,embedding.*
dbms.security.procedures.unrestricted=regression.*,embedding.*

I'm getting a ProcedureNotFound error. It seems as if others are able to utilize the embedding.opengl procedures with some degree of success. I'm genuinely curious as to what I'm doing wrong.

I'm seeing the same problem. Here's the debug.log output from my Neo4j 3.5.0 instance.
In particular, Neo4j seems to have trouble loading embedding.DeepGL from the jar, along with a bunch of other jars/classes. Interestingly, the regression.* procedures do load successfully (according to CALL dbms.procedures()).
I've also tried installing this plugin on Neo4j 3.4.7 and 3.3.7 with the same results.

@djsauble  I have the exact problem. I can see the regression.* procedures but not the embedding.* ones. Did you find a solution for this?

Nope, I gave up. Their test suite isn't runnable either (has dependencies on test data that isn't part of the repo), so it's difficult to tell where the problem is.

Hey,
You need to install the graph algorithms library to have the embedding procedure show up. I updated the readme to explain how to do that.
Cheers, Mark

@djsauble @mneedham Thank you for the replies. I will check it again now and let you know how it goes.


Thankyou card bug fix

What
Bug fix for unresponsive thank you cards in the thank you page. I introduced this when I added project categories into the cards, and missed a spot that needed to be updated to reflect the new data source type 😭We actually had a test for this scenario that would have failed, but the test file wasn't added to the list of sources, so it wasn't run. This PR fixes the bug and adds the ThanksProjectDataSourceTests into the framework test target.
I've also removed the DiscoveryPostcardCell view from the DiscoveryPage storyboard. We don't use this anymore because we have a DiscoveryPostcardCell.xib that we reuse in the thank you page. Tested on both the regular discover view and the thank you screen.
Why
https://trello.com/c/oRcheQCq/763-ios-post-pledge-thank-you-page-project-recommendation-cards-are-unresponsive
See 👀
Original PR: https://github.com/kickstarter/ios-oss/pull/347
Video:

Could you perhaps add a link to the PR where the type was added?

@justinswart added the PR link to the description!

 iOS post-pledge Thank you page: project recommendation cards are unresponsive


Go to 1.19.3

This is a very good mod. I would like to see it on the latest version

I have no plans to work on a 1.19.3 version. Out of time reasons I only work on the latest versions of my mods.


Added ability to set Transaction Behavior and use Tags with MaintenanceAttribute

Added the ability to set the TransactionBehavior for a maintenance migration and added the ability to Tag a maintenance migration. I needed this functionality because as part of our QA database migration, we wanted to load the majority of the database from a backup and this has to be done outside of a transaction with SQL Server.
I added unit test for all the added functionality and some of the existing maintenance functionality. The code has also been tested in our QA database migrations.

@unrealguard Looks great, will try to pull it asap

@unrealguard Thanks


[node-agent] Fix warning on failing lease updates

How to categorize this PR?

/area quality
/kind enhancement
What this PR does / why we need it:
When GNA fails to update its lease, it prints a needless warning to its logs.
Warning: Reconciler returned both a non-zero result and a non-nil error. The result will always be ignored if the error is non-nil and the non-nil error causes reqeueuing with exponential backoff. For more details, see: https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/reconcile#Reconciler

This PR removes this warning.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

NONE

/test pull-gardener-e2e-kind-ha-multi-zone-upgrade


then warning creates messy logs for thenable APIs

The recent addition of warnings when then is called with a non function argument is creating messy test output over at Knex. The basic issue here is that query objects are thenables that proxy to a real promise which gets created. Since Promise.longStackTraces turns on debugging, we're getting loads of warnings about empty thens in the integration tests.
The easy fix here is just to revert the warning, but I understand if there was a compelling reason to do it. We could also use promise.then.apply(promise, arguments) in place of explicitly passing the two callbacks to promise.then. I'd prefer not to go that route since it's harder to read/understand.

I don't see how this is a bluebird problem in any way. The warning is justified, and knex is doing weird things it shouldn't. The fix is to stop doing weird things, not to complain to bluebird to remove the warnings. I've NEVER had good results trying to wrap or fiddle with the "then" method of a promise, or providing a pretend/pseudo promise by providing a then method. I don't understand what knex is trying to do well enough to suggest a viable alternative, but I can see that it's doing something that will only cause pain.

@myndzi I totally see why this is our problem. We have every obligation not to break backwards compatibility and I'm against any reasoning that blames the users of the library for a breaking change.
When we introduced the warnings we could not come up with reasonable workflow issues (We considered cloning a promise).
@bendrucker there will be a hook that allows you to opt-out of these warnings (but it's planned for 3.0 for better debuggability). I'm afraid it's not there yet - I wonder if it can be backported to 2.9.*
In the interim I suggest a revert in 2.9.x - what do you think @petkaantonov ?

@bendrucker why would you .then() a transaction or a target() without arguments?

It's not a breaking change though?
The code is apparently calling .then() to get an instance of a promise derived from the source (where the '.then' method had been replaced); it seems to want to execute some code before executing the .then handler, but it doesn't want to execute that code until the .then method is called, thus the whole wrapping thing.

@benjamingr A hook sounds perfect. There are a number of cases where you might end up calling then without arguments. One is if you want to get at a Bluebird helper method that's not proxied, e.g. query.then().get(0). Another would be returning inside a promise:
promise.then(function () {
  return query;
});

So query.then is implicitly called with no arguments in that case. This totally goes away when applying arguments from the thenable's then to the actual promises's then instead of manually passing them.
In general I'm of the opinion that warnings should always be opt-in and libraries should throw when something's wrong and never write to the console. So in this case my ideal solution (not Knex's, but the one that fits best with how I write things) would be to change the philosophy around warnings. A user could opt in, a la strict mode, to have Bluebird throw in cases like this.

Also this is purely a cosmetic issue right now with the test logs. It's not going to affect users of Knex.

@bendrucker You could just call ._then? It's forced to retain same api signature across all versions, even major.

If you're considering reverting and saving for 3.0 I'll wait on that. Otherwise I'll drop in a fix and probably just end up applying the arguments.

@bendrucker note that you did opt into the debug build when you enabled long stack traces. Like petka said in v3 we'll have finer grained control.
I'm for reverting this and introducing it in a major for breaking workflows.

@petkaantonov any update on reverting this in 2.x? There has been a release since the issue opened and I want to know if you decided one way or the other.

Well I don't see any reason to revert this, the fix is simple for knex and people will use 2.x for a while.

Fair enough. I've fixed it in knex.


Some Videos can't play on IE 9-11 and Edge

eg this video: https://www.pictshare.net/09ddab5430.mp4
Plays well in all major browsers except for all MS ones. It's strange since the video seems to be h264 encoded (which is the only codec MS Browsers understand)
Some videos only work in MS browsers after they have been resized by PictShare. This points to a codec problem but both videos state they are h265 encoded

this is now fixed since 40a6ac45ded8ff2f0f1fbae2f5697120efed3273 it seems it was a bug in the mp4 serving function


Video about this wonderful tool [ this is not an issue ]

I manage a Youtube channel about Proxmox VE.
I stumbed across this project about VDI SPICE over PVE.
So I made video about it (Brazilian Portuguese only! Sorry! But you can enable subs!)
I hope you enjoy it.
Thanks
https://www.youtube.com/watch?v=kxm-JtnLWmc

Very cool, thanks!


Black Dashed Stroke - VERY noticeable in 3D

Hi
Bar and columns are rendered with a black stroke on them.  Zero Values are given a dashed stroke.
If you hover over a column/bar the colours change, then on mouse-out they change to the correct colour.
http://jsfiddle.net/jsfUserName/aqmo6x3c/
I have created the above fiddle to demonstrate - the dashed stroke is also noticeable on your demo.
I'm using draggable points version: 1.1.3.
It looks like the issue is caused on line 182
point.graphic.attr(point.shapeArgs.height < 3 ? {
                        'stroke': 'black',
                            'stroke-width': 2,
                            'dashstyle': 'shortdot'
                    }

Thank you for the fix and acting so quickly


Error: Cannot find module 'undefined' on Updates screen

Prerequisites

[x] Can you reproduce the problem in safe mode?
[x] Are you running the latest version of Atom?
[x] Did you check the debugging guide?
[x] Did you check the FAQs on Discuss?
[x] Are you reporting to the correct repository?
[x] Did you perform a cursory search to see if your bug or enhancement is already reported?

Description
When browsing the Updates section of the Settings tab, I get an error message. This error isn't 100% consistent, and it appears more consistently the first time I load the Updates section of the Settings tab. Sometimes, it also appears when I click the "Check for Updates" button.
Message: Fetching outdated packages and themes failed.
More output:
npm
module.js:340
    throw err;
          ^
Error: Cannot find module 'undefined'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at cb (C:\Users\mrausch\AppData\Local\atom\app-1.6.0\resources\app\apm\node_modules\npm\lib\npm.js:286:7)
    at C:\Users\mrausch\AppData\Local\atom\app-1.6.0\resources\app\apm\node_modules\npm\lib\npm.js:375:14
    at C:\Users\mrausch\AppData\Local\atom\app-1.6.0\resources\app\apm\node_modules\npm\lib\config\core.js:82:7
    at Array.forEach (native)
    at C:\Users\mrausch\AppData\Local\atom\app-1.6.0\resources\app\apm\node_modules\npm\lib\config\core.js:81:13
    at f (C:\Users\mrausch\AppData\Local\atom\app-1.6.0\resources\app\apm\node_modules\npm\node_modules\once\once.js:17:25)

Steps to Reproduce

Open Settings tab
Click on "Updates"
It will do an initial "Check for Updates"

Expected behavior: Check for package and theme updates.
Actual behavior: Displays an error message.
Versions
Atom 1.6.0
apm  1.6.0
npm  2.13.3 (This is not what I'm actually running. See below.)
node 0.10.40 (This is not what I'm actually running. See below.)
python 2.7.11
git 2.7.0.windows.1
visual studio
Node v4.4.0
npm 3.7.2

@awayken Thank you for the thorough report.

@ZombieHippie Any insight into what might be going on? Is there any additional info I can provide?

@awayken here is our first clue, which is the require which is undefined: https://github.com/npm/npm/blob/v2.13.3/lib/npm.js#L286
We can do more investigating where this onload script is.

I don't seem to be getting this error any longer. I'm going to close this issue unless I start to see the issue pop up again.


Docker on Ubuntu 14.04.3 always getting "[8] System error: no such file or directory"

I had Docker working three weeks ago, but now I can't get anything except
no such file or directory
Error response from daemon: Cannot start container 7d3cb483971037da163fd8d220100728f51e055e7d0ae811a70bf2ef32564552: [8] System error: no such file or directory

docker version
Client:
 Version:      1.8.2
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   0a8c2e3
 Built:        Wed Oct  7 17:48:28 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.8.2
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   0a8c2e3
 Built:        Wed Oct  7 17:48:28 UTC 2015
 OS/Arch:      linux/amd64

docker info
Containers: 1
Images: 2
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 4
 Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-66-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 4
Total Memory: 7.74 GiB
Name: footscray
ID: IWMM:MCLX:3H5C:V4QA:JQA2:TVBM:F3PX:4VC4:45XZ:C6AT:TB75:QQNG

uname -a
Linux footscray 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Am running on localhost.
docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world

535020c3e8ad: Pull complete
af340544ed62: Pull complete
Digest: sha256:a68868bfe696c00866942e8f5ca39e3e31b79c1e50feaee4ce5e28df2f051d5c
Status: Downloaded newer image for hello-world:latest
no such file or directory
Error response from daemon: Cannot start container b834de00b11decea01b36d1105352eca423bf708dda4b14016bab8fecd5bff41: [8] System error: no such file or directory

At first I'd used the wget method to install docker, but then I removed everything and used the method described in the docs https://docs.docker.com/installation/ubuntulinux/

+1 same problem here.

FWIW, I've tried changing the storage driver to both vfs and devicemapper without any success.
Also, when updating yesterday I pulled Docker 1.8.3 - but am still getting the same result.

I wonder if this is somehow related to AppArmor, see a similar issue on Debian here: https://github.com/docker/docker/issues/14931 (which contains some instructions on debugging the issue)

Ah! I read that issue but also couldn't find any issues within my dmesg logs.
But I have discovered something that works - it's worth noting that my docker and AppArmor skills are rudimentary, so I'm not 100% sure of what's going on here.
When I first applied the AppArmor solution (aa-complain, per session) it worked. I then disabled the profile in general for consistency across reboots (as advised on the Ubuntu wiki):
sudo ln -s /etc/apparmor.d/docker /etc/apparmour.d/disable/docker

When I deleted the entry in /etc/apparmour.d/disable, and just have the aa-complain set, docker starts to work again.
For reference, I set up a VM of Ubuntu 15.04 this AM and had exactly the same problem - this was how I found the solution.

Thanks for reporting back @datakid and good to hear you were able to resolve it.
/cc @ewindisch

For those who may still be facing this issue. I've recently discovered that this happens on my Windows machine if I do not explicitly set my .sh, Dockerfile, and docker-compose.yml line endings to UNIX LF format (default is CRLF).. Might be worth giving that a shot if you're running a Windows machine.

Same error was for me on Windows. Changhing from CRLF to LF fixed the issue.

@dsifford @aldarund does that apply to both the Dockerfile and docker-compose.yml? If so, please open a new issue for docker and compose https://github.com/docker/compose/issues
We may not support CRLF line-endings, but (if possible), adding a better error message would be good

@thaJeztah Looking back at my .gitattributes file, it appears that I only ended up changing the line endings on the Dockerfile and the .sh files that my build process depends on. I don't think Compose is effected by this.

@dsifford in that case, it may actually be the .sh files that cause the problem, I think I've see that happening on Linux, but not 100% sure. If it's the .sh files that cause the problems, I don't think we can change anything on that, but if it's the Dockerfile, that would be something we can control

@thaJeztah You make a good point. Let me give that a shot now and report back.

@thaJeztah Your suspicion was correct. Docker is not to blame for this issue.
After running a few tests, the error message (below) could only be invoked by changing the line endings in the .sh files to CRLF. Having CRLF endings on the Dockerfile and/or the docker-compose.yml file did not produce the error.
The error message:
ERROR: Cannot start container 057540c349f83925271f6c8d132d120975c3479370b43072cadc7bfd4a847014: [8] System error: no such file or directory

@dsifford awesome, thank you so much for testing!

I experienced a similar issue on Windows that appears to have been resolved by converting everything from CRLF to LF.  A more descriptive error message would be useful.

@jpblair unfortunately, that issue is in Linux itself, you'll have the same problem on a bare-metal Linux system when trying to run a shell script that has CRLF. I.e., it's not Docker specific

dos2unix was also my savior. Man!


docs(guide): copy over html files, not markdown files

Failure is a bug in nightly rustc compiling regex crate.


xt/word-variants.t failures

The problem
Looks like all the failures are meta- related.
$ xt/word-variants.t 2>&1 | grep -v "^ok" | tee variants.out
1..396
not ok 10 - doc/Language/about.pod6 «Meta-» found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/about.pod6 «Meta-» found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 11 - doc/Language/classtut.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/classtut.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 21 - doc/Language/faq.pod6 «Meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/faq.pod6 «Meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 23 - doc/Language/glossary.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/glossary.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 31 - doc/Language/ipc.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/ipc.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 38 - doc/Language/modules-extra.pod6 «META » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/modules-extra.pod6 «META » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 39 - doc/Language/modules.pod6 «META » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/modules.pod6 «META » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 40 - doc/Language/mop.pod6 «Meta-» found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/mop.pod6 «Meta-» found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 42 - doc/Language/nativetypes.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/nativetypes.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 45 - doc/Language/objects.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/objects.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 47 - doc/Language/operators.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/operators.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 49 - doc/Language/packages.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/packages.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 50 - doc/Language/performance.pod6 «Meta-» found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/performance.pod6 «Meta-» found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 52 - doc/Language/pod.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/pod.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 55 - doc/Language/quoting.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/quoting.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 56 - doc/Language/rb-nutshell.pod6 «meta  » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/rb-nutshell.pod6 «meta  » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 61 - doc/Language/structures.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/structures.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 68 - doc/Language/testing.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/testing.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 69 - doc/Language/traits.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/traits.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 70 - doc/Language/traps.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/traps.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 71 - doc/Language/typesystem.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Language/typesystem.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 84 - doc/Type/Attribute.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Type/Attribute.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 111 - doc/Type/CompUnit.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Type/CompUnit.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 126 - doc/Type/Distribution/Path.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Type/Distribution/Path.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 51
not ok 175 - doc/Type/Metamodel/AttributeContainer.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Type/Metamodel/AttributeContainer.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 36
not ok 176 - doc/Type/Metamodel/C3MRO.pod6 «Meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Type/Metamodel/C3MRO.pod6 «Meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 36
not ok 177 - doc/Type/Metamodel/ClassHOW.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Type/Metamodel/ClassHOW.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 36
not ok 179 - doc/Type/Metamodel/CurriedRoleHOW.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Type/Metamodel/CurriedRoleHOW.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 36
not ok 180 - doc/Type/Metamodel/EnumHOW.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Type/Metamodel/EnumHOW.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 36
not ok 183 - doc/Type/Metamodel/MethodContainer.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Type/Metamodel/MethodContainer.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 36
not ok 185 - doc/Type/Metamodel/Naming.pod6 «Meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Type/Metamodel/Naming.pod6 «Meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 36
not ok 186 - doc/Type/Metamodel/PackageHOW.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Type/Metamodel/PackageHOW.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 36
not ok 189 - doc/Type/Metamodel/Primitives.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Type/Metamodel/Primitives.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 36
not ok 199 - doc/Type/Mu.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Type/Mu.pod6 «meta-» found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 36
not ok 395 - doc/Type/independent-routines.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized.
# Failed test 'doc/Type/independent-routines.pod6 «meta » found. We prefer ｢meta｣): Certain words should be normalized. '
# at xt/word-variants.t line 36
# You failed 35 tests of 396

This is still #2966. I couldn't get around to it. Thanks for the reminder, anyway.

No need to close, really. I can close the other one when the test is OK, I'll close this one when all those errors are fixed (or whoever). Really appreciate that.

not closed... Still a bit to go.


Azure Regional Non-Pairs Is Confusing

It's confusing to call them non-pairs. They should be called non-standard pairs or something like that.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: aa1995a6-8f18-c6ea-fff6-6c8f7b05d2f5
Version Independent ID: 8abbbb3f-2d03-1395-acea-197a6b2a7c7e
Content: Cross-region replication of Azure NetApp Files volumes
Content Source: articles/azure-netapp-files/cross-region-replication-introduction.md
Service: azure-netapp-files
GitHub Login: @b-juche
Microsoft Alias: b-juche

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Thanks, @elfcounsel!  Checking with our SMEs before making this update.  Due to an impending doc update freeze, changes might wait a week to show.  Will provide status.
If you are an ANF team member, feel free to reach out with further comments through<EMAIL_ADDRESS>or<EMAIL_ADDRESS>

Thanks again, @elfcounsel!  This change has been implemented through PR 159264 https://github.com/MicrosoftDocs/azure-docs-pr/pull/159264
ETA for publishing is May 25 (due to current publishing freeze).

#sign-off


Vim extension in VS Code: unable to jump into braces, parentheses and brackets from beginning of sentence ci[ or ci(

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.63.2
OS Version: NT x64 10.0.19041

Steps to Reproduce:

Install / enable extension: Vim emulation for Visual Studio Code v1.21.10
Install / enable extension: Python v2021.12.1559732655
Create a python file: test.py
Enter a sample line in the file: This is a test sentence with a (sample) word in parentheses.
Save the file
In Vim normal mode press the 0 key to go to the beginning of the sentence
In Vim normal mode press the key sequence: ci(

The cursor does not jump to after the ( parenthesis and does not remove the word sample and change to insert mode. In the Vim editor, this key sequence works.
Note: when the cursor is on the opening or closing parenthesis or inside the parenthesis pair then the ci( key sequence does work.

/causedByExtension


Maximum number of tables viewable is limited

Describe the bug
I can't see the full list of tables in one region.  There are 118 tables, I'm guessing I can only see the first 100.
To Reproduce
Steps to reproduce the behavior:

Run dynamodb-gui-client
configure a dynamodb database/endpoint with 100+ tables
click on the table selector
scroll to the bottom and verify the entire list of tables is there

Expected behavior
The entire list should be visible but only the first 100 or so are visible.
There are no errors listed on the console.
Desktop (please complete the following information):

OS: MacOS Mojave
Browser electron
Version : 3.0.10 (3.0.10) (electron?)
Version: either 3b328aa116bd9e1487bc1d707c971bfc29458f2a or what was installed with npm install -g dynamodb-gui-client. which would be dynamodb-gui-client-2.0.3.tgz.

Table list rendered via element-ui el-select element and has scroll box. I rendered 150 tables and have not seen any problem there. Check if you have all 118 tables in your database.

Look, this is how i get table list from dynamodb in my code.
try {
    data = await state.dbInstance.listTables().promise();
}

And the array of tableNames, which i get from response i am just storing in application state. There are no maximum number of tablenames, that i can store in selectbox. This is just GUI, it is just showing what it receives from simple dynamodb calls.

So you’re not paginating?
On Dec 11, 2018, 1:58 AM -0500, Misak Poghosyan<EMAIL_ADDRESS>wrote:

Look, this is how i get table list from dynamodb in my code.
try {
data = await state.dbInstance.listTables().promise();
}
And the array of tableNames, which i get from response i am just storing in application state. There are no maximum number of tablenames, that i can store in selectbox. This is just GUI, it is just showing what it receives from simple dynamodb calls.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I'll try to figure out whats the problem, but i think this is not the application issue.


Data loss when opening Godot 3 scenes in Godot 4

Godot version
v4.1.beta1.official [828ec2c5d]
System information
Godot v4.1.beta1 - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2070 SUPER (NVIDIA; <IP_ADDRESS>47) - AMD Ryzen 7 3700X 8-Core Processor (16 Threads)
Issue description
In Godot 4.1rc1, opening .tscn files formatted for Godot 3 doesn't upgrade them properly--if a node has a property whose name was changed in Godot 4, the property is destroyed rather than upgraded (reset when the scene is opened, removed when the scene is saved).
Examples I've found are TextureRect and TouchScreenButton. When I open scenes containing those, I find that the TextureRect's positioning has been reset to 0,0 (because margin_ properties were renamed to offset_) and the TouchScreenButton's graphics have been removed (because normal and pressed were renamed to texture_normal and texture_pressed).
Expected behavior is that, instead of vanishing into the aether, properties with changed names are updated to their new names when loaded in Godot 4, respecting the type of the node and making any changes required to preserve data in the new API.
Steps to reproduce

In Godot 3, open the repro project labeled "Godot3" and the scene named GD3Scene.tscn.
Observe that the TextureRect is roughly in the middle of the scene's screen outline, with its anchors far above and to the left.
Inspect GD3Scene.tscn in a text editor. Observe that the node named "TextureRect" has properties margin_left, margin_top, etc.
Copy GD3Scene.tscn into the repro project labeled "Godot4."
In Godot 4.1, open project "Godot4" and the copied scene.
Observe that the TextureRect is at the top-left of the screen outline, touching its anchors.
Without modifying anything, save the scene.
Inspect the saved version of GD3Scene.tscn in a text editor. Observe that "TextureRect" has lost all properties except texture.

Minimal reproduction project
GD4 Scene Convert Problem.zip

Are you using the converter? It sounds like you don't

Yes, I did run the converter. The converter didn't touch the scene files, at least not the properties I indicated.

Superseded by https://github.com/godotengine/godot/issues/78930.


Problem during pip installation

Hi,
Trying to install Piexif I got the following error. My environment is Anaconda under Python 3.7.
It seems to desire Python 2.6. I had not this problem in a previous installation but ssl evolved rapidly ...
What is the solution to install Piexif ?
François-Régis Chalaoux
$ pip install piexif
You are using pip version 7.1.0, however version 19.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Collecting piexif
/Users/xxxx/anaconda3/envs/Drone/lib/python2.6/site-packages/pip/vendor/requests/packages/urllib3/util/ssl.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
InsecurePlatformWarning
/Users/xxx/anaconda3/envs/Drone/lib/python2.6/site-packages/pip/vendor/requests/packages/urllib3/util/ssl.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
InsecurePlatformWarning
Could not find a version that satisfies the requirement piexif (from versions: )
No matching distribution found for piexif

Thats your linux
try reinstall pip


Burp plugin installation not working

Hi Team,
I've followed the steps mentioned in
https://github.com/DefectDojo/Burp-Plugin but getting error "Error connecting to DefectDojo , double check the URL"
I've enter DefectDojo : https:10.10..:8083.
Please help to resolve this.

Moving this issue to the Burp Plugin repo as it's maintained there.

Just, hint, are you using self signed certs?
Dubravko

If the server is https and the certificate self-signed this is indeed an issue. We could add an option for bypassing it but I don't feel comfortable doing this as the server's certificate should be trusted.
I've tested with http://localhost:8080 and a trusted ssl cert for https://ip:443 and it's always worked.


Support callback, custom config key and publishing for parameters.

Description
See #4429 for details.
Fixes #4429
Checklist

Is this feature complete?

[ ] Yes. Ready to ship.
[X] No. Follow-up changes expected to support new manifest value

Are you including unit tests for the changes and scenario tests if relevant?

[X] Yes
[ ] No

Did you add public API?

[X] Yes

If yes, did you have an API Review for it?

[X] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[X] No

[ ] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[ ] No

[X] No

Does the change require an update in our Aspire docs?

[X] Yes

Link to aspire-docs issue: none yet

[ ] No

Microsoft Reviewers: Open in CodeFlow

Any thoughts on supporting a Func<IServiceProvder, Task> variant?

Thanks once again for the contribution @davidebbo

@mitchdenny per discussion with @davidfowl, we decided not to tackle async at this time, though this could be a future thing (it does look hard!).
Note that per https://github.com/dotnet/aspire/issues/4429#issuecomment-2335197079 and discord chat, we'll be making some design changes for publishing the value, so I'll be evolving the PR.

/azp run

/azp run

cc @vhvb1989 @ellismg

Filed https://github.com/Azure/azure-dev/issues/4359

@davidebbo @davidfowl @mitchdenny is it safe to asume that a default.value will never be set as secure ?, like:
"param-with-value": {
      "type": "parameter.v0",
      "value": "{param-with-value.inputs.value}",
      "inputs": {
        "value": {
          "type": "string",
          "secret": true,
          "default":{
            "value": "default value for param"
          }
        }
      }
    },

See the "secret": true,  there.
I am working on making azd to fail on this case as per: https://learn.microsoft.com/azure/azure-resource-manager/bicep/linter-rule-secure-parameter-default

But I am wondering if the AppHost is even allowing this or not?  (maybe is blocked in AppHost so I don't even need to worry)?

@vhvb1989 we do not block it today, but I agree that we should. So I think we should allow:
var foo = builder.AddParameter("foo", value: "somesecret", secret: true);

as this only uses the value at runtime, but not:
var foo = builder.AddParameter("foo", value: "somesecret", publishValueAsDefault: true, secret: true);

which results in having the secret in the manifest.
@davidfowl @mitchdenny do you agree? If so, can make a follow-up change to prevent this. e.g. an error like the 'publishValueAsDefault' and 'secret' flags are mutually exclusive, to prevent saving a secret to the manifest

I sent #5891 to make this change.

@vhvb1989 This is now blocked in AppHost, so you should not encounter this unless people mess with their manifest by hand,


⚠ Turnos 24x7 has degraded performance

In 58b6e8b, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 935 ms

Resolved: Turnos 24x7 performance has improved in 3921585.


fix docker release

Description
fix docker releases
Related Issue

Fixes release blocker introduced by #1941

Motivation and Context

docker releases do not work

@micbar merged, can we have a new RC tag?

yes, will prepare an rc2