Update Update-Recipient.md

Issue #6670

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

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Update-Recipient.md
:white_check_mark:Succeeded
View (exchange-ps)

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

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

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Update-Recipient.md
:white_check_mark:Succeeded
View (exchange-ps)

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


No external connectivity

I recently added multus to one of my pods as per the below but have realised that I can only communicate externally (google.com, etc.) via the flannel plugin. This is confirmed when I use a ping -I net2 google.com. I am easily able to communicate with anything on <IP_ADDRESS>/24 (net0 also resides here) and vice-versa.
Is this intended? This may also be more of a CNI plugin question...
Snippet from pod:
annotations:
  k8s.v1.cni.cncf.io/networks: '[
    { "name": "flannel-conf" },
    { "name": "macvlan-conf" }
  ]'

macvlan.conf:
apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
  name: macvlan-conf
  namespace:
spec:
  config: '{
    "cniVersion": "0.3.0",
    "type": "macvlan",
    "master": "net0",
    "mode": "bridge",
    "mtu":9000,
    "ipam": {
      "type": "static",
      "addresses": [
        {
          "address": "<IP_ADDRESS>/24",
          "gateway": "<IP_ADDRESS>"
        }
      ],
      "routes": [
        { "dst": "<IP_ADDRESS>/0" }
      ],
      "dns": {
        "nameservers": [ "<IP_ADDRESS>" ]
      }
    }
  }'

IP addresses from pod:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
3: eth0@if13: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 9000 qdisc noqueue
    link/ether de:5f:d0:15:c0:72 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::dc5f:d0ff:fe15:c072/64 scope link
       valid_lft forever preferred_lft forever
5: net1@if14: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 9000 qdisc noqueue
    link/ether 32:35:7b:7b:61:f7 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 scope global net1
       valid_lft forever preferred_lft forever
    inet6 fe80::3035:7bff:fe7b:61f7/64 scope link
       valid_lft forever preferred_lft forever
6: net2@if2: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 9000 qdisc noqueue
    link/ether 9a:f8:2c:c4:04:3b brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 scope global net2
       valid_lft forever preferred_lft forever
    inet6 fe80::98f8:2cff:fec4:43b/64 scope link
       valid_lft forever preferred_lft forever

What's the routing look like in the pod? It sure smells like something external -- if the interface is created, it's likely not Multus that's in play anymore, and it's something on the other end of the connection that's causing you some problems.

Please see the below for the route in the pod. I've also included the systemd interface config for net0 on the host/node if that helps. net0 is also the only 'physical' NIC on the host. Thanks!
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         <IP_ADDRESS>      <IP_ADDRESS>         UG    0      0        0 eth0
<IP_ADDRESS>       *               <IP_ADDRESS>   U     0      0        0 net2
<IP_ADDRESS>      <IP_ADDRESS>      <IP_ADDRESS>     UG    0      0        0 eth0
<IP_ADDRESS>      *               <IP_ADDRESS>   U     0      0        0 eth0
<IP_ADDRESS>      *               <IP_ADDRESS>   U     0      0        0 net1

Interface config:
[Match]
Name=net0

[Link]
MTUBytes=9000

[Network]
Address=<IP_ADDRESS>/24
Gateway=<IP_ADDRESS>
DNS=<IP_ADDRESS>
IPForward=ipv4

The issue was with my initial yaml for multus as I forgot that flannel was included and was specified to be the default route. Thanks!

@Elegant996 So your solution was to remove to default-configuration in the "node" multus-yaml file at /etc/cni/net.d/00-multus.conf?


Upgrade typescript tools version on mobile-app from 1.5 to 1.8.

Updated TypeScript tools version. This will avoid Visual Studio Update 1 & Update 2 developers from getting the dialog alerting them to having a older version of type script tools in this project.  The dialog happens automatically and by default. Only the solution with with the mobile-app project in it will be effected.

I imagine that users of Visual Studio Update 1 & 2 would get alerted about this when they first open the solution with the mobile-app. Visual Studio 2015 Update 1 included 1.6 and 1.7 releases of the TypeScript tools. Visual Studio 2015 Update 2 includes TypeScript 1.8.  The latest version (1.8) can be downloaded separately at https://www.microsoft.com/en-us/download/details.aspx?id=48593. These typescript tools updates brings significant enhancements to TypeScript's type system and enables support for the polymorphic type, intersection types, local type declarations, generic type aliasing, and user-defined type guard functions. It also completes ES6 support in TypeScript by adding ES6 Generators and ES6 Class expressions, and brings support for new ES7 feature proposals like ES7 Exponentiation operator and ES7 Async functions. The compiler now highlights common bugs such as unreachable code, missing return statements, and unused labels.

Thanks @SteveKennedy for your contributions!
Generally yes, separate 'small' Pull requests are best so we can review and accept separately.
If you need reference for how to have more than one pull request at a time I believe one of @stevejgordon @dpaquette and @MisterJames have documented that (cc @BillWagner )
If you separate or pull back the second part of this PR we can review and accept each PR.
Thanks!

I don't know what I'm doing.  I tried reverting the second commit.  Ultimately, only the first commit changes are now in this PR.  There's some line break/spacing issue in the SiteAdminControllerShould.cs that I couldn't seem to revert.

I closed this pull request and will open a new one with the (cleaner) changes.

Hi @SteveKennedy. You might find this tutorial helpful.
http://www.davepaquette.com/archive/2016/01/24/Submitting-Your-First-Pull-request.aspx
I put it together based on my own struggles when I was getting started with GitHub and Pull Requests. If you have any questions, feel free to reach out. We can always do a screenshare and work through issues together.


Format Identifier

Summary
This PR makes use of the new range on Identifier introduced by #5194 to provide a FormatIdentifier implementation and uses it across the code base.

Test Plan
cargo test

Current dependencies on/for this PR:

main

PR #5255   👈

This comment was auto-generated by Graphite.


How to properly escape values for $GITHUB_ENV file

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/actions/learn-github-actions/workflow-commands-for-github-actions#environment-files
What part(s) of the article would you like to see updated?
I'm missing explanation how to properly escape values written to $GITHUB_ENV file. It would be also helpful to describe how this file is read.
Additional information
I'm writing this issue based on my current experience.
I'm trying to set environment variable with value which starts with $ and so far I haven't been able to do so.
Please see following workflow file as example: https://github.com/klinki/github-actions-for-packages/blob/main/.github/workflows/test-env-vars.yml

Edited by maintainer
Content Plan
Here is the writer's content plant  for this issue

Thanks for opening this issue! I'm not sure how to do this either, but I agree it would be helpful to document. I reached out to  the Actions team to ask.

Update: You can use single quotes instead of double quotes to achieve this. e.g. This worked for me:
    steps:
      - shell: pwsh
        run: |
          echo 'action_state=$yellow' >> $GITHUB_ENV
      - shell: pwsh
         run: |
           echo  IT IS '${{ env.action_state }}'

You or anyone else is welcome to open a PR to add this information to the docs.

Hi @skedwards88 / @ramyaparimi
I am interested in this issue. Can you plz assign me?

Can I add it? :) if @klinki isn't making a PR then I can work on this :).

@ArkaprabhaChakraborty please feel free to work on this, it has been a while and I'm quite out of a loop of this particular issue now.


Kabyle translations

Kabyle traslations are not synched yet. Translation is complete on crowdin

I have finished to check all translations in crowdin, so i hope we are going to use ProtonMail in kabyle very soon, thank you.


Back action

-It’s not going back when I swipe left to right.

Also, the back button has a very small reaction area. Needs to be looked at and made uniform for the whole app.

This needs to be for all Back buttons. The system action of
swipe from left to right (for iOS) and
bottom system back button (for Android)

Also, the back button has a very small reaction area. Needs to be looked at and made uniform for the whole app.

For this, I already did changes in my last months commits as Muneer suggested "hitSlop" property for the large touchable area and it's working fine. For reference, I just attaching one screenshot here

-Verified this on Dev app version 1.3.2(168)


Strong name support for Confluent.SchemaRegistry.Serdes

Hi guys,
Thank you for a cool project!
Description
I need Strong Named sign. I can see the Kafka project has Strong name sign. However, Confluent.SchemaRegistry.Serdes doesn't have it.
How to reproduce
Include Confluent.SchemaRegistry.Serdes into a strong named project. You will see the error.

Currently we are using
    <PackageReference Include="Confluent.Kafka" Version="1.0.0-RC3" />
    <PackageReference Include="Confluent.SchemaRegistry.Serdes" Version="1.0.0-RC3" />

We can switch Confluent.Kafka to strong named one. but not ConfluentSchemaRegistry.Serdes.

thanks for asking, we're tracking this request internally.

done - all packages are now signed.


I want to install deis with three machines,

how can i vagrant up three coreos on three ubuntus.

Closing this issue as the question has been answered. In the future, you'll probably get more responses if you post in the mailing list as there are more eyes watching it.
Thanks!


allow custom theming for all components

Try to implement this behavior with a vue mixin and pass the style data as object prop.

get styles of root element (of a component)
add passed custom styles object to it

closed, because of simplicity of design


Is it possible to make line take full available space instead of fixed?

+1 on this

@ma7moud3osman Would you consider taking this issue? I think I was the original intent of this issue #20 but since LineType.lineLength is not nullable we can't work our way around 🤔


[HW] Nilesh Gaikwad | Workshop Spring Stargate

Name: Nilesh Gaikwad
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/gaikwadnilesh/
Attach the homework step I screenshots below:

Attach the homework step II screenshots below:

Hey Nilesh Gaikwad, great job! Congrats! Here is your badge! https://api.badgr.io/public/assertions/qvaiT2vcQP2MuOZuCcgQkA


Fails to skip invalid rule

read the rule (Sa4) as a valid rule where the valid one should be with lower s (sa4). this invalid rules exists in InsidePro-HashManager.rule file that cames in hashcat rules folder.
this is my command I used to clean my file that contain this and similar rules that start with S:
[ruleprocessorY.exe --optimize-no-op -r ".\input.rule" --hashcat-input --hashcat-output > ruleprocessorY_out.rule]

It marks the Sa4 rule as valid because the S rule exists as a custom rule in ruleprocessorY.
The S rule will perform the same operation as 's' except that it will do so on the 'first occurrence' of a string instead of all.
This means that only the first a will be replaced by 4 in your example, instead of all a's.

I realize this might not be your expected behaviour so feel free to add on if you have any questions / remarks and otherwise close the issue.

Yes, I expected that the rule should be removed/converted because I used [--hashcat-input --hashcat-output] in my command which should mean to (read and output) only hashcat valid rules OR convert input rules into valid hashcat rules in output file.
Or maybe I'm not understanding the command!.

The above commit should resovle this issue.

The above commit should resolve this issue.

Seeing the thumbs up, I'll take it as resolved. Closing the issue.


Add Profile.json

Description
Added my profile in the src/data repo
Related Issues
[Include any related issues or pull requests that this PR addresses or is related to. Use GitHub's shorthand syntax to link to them, like #1234.]
Changes Proposed
[Describe the changes you've made in detail. Be specific and include any relevant code snippets.]
Checklist

[x] I have read and followed the contribution guidelines.
[x] All new and existing tests passed.
[ ] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

@shubhsharma19 Thank you so much for your contribution! Your efforts are greatly appreciated and will go a long way in improving our project. Please feel free to share it with others and help us grow even further!


fix: Suppress errors on is_callable

Reproduction case https://github.com/NotGeri/yii-test
The is_callable is triggering a warning in this case. As we already put it into a try/catch, I'm ok with suppressing eventual errors here as well.

Thank you again, just wanted to confirm that the fix seems to work fine. Really appreciate the quick help!


[proxima-direct-core] #29 remove Serializable interface from readers and writers

All fixed and verified on live pipeline. When approved, I'll swuash it.

This closes O2-Czech-Republic#29


Feature Request: pass tree-relative path to customHash

The documentation for customHash reads

customHash - Default: none - If set, overrides the md5 checksum calculation with the result of calling customHash(buffer). If it is not a function, customHash is used as the hash value. If it is set to null, fingerprinting is skipped and only prepending occurs.

The code actually calls it two different ways:

in getDestFilePath, this.hashFn(file, tmpPath), where file is the contents of the file as a string
in writeRailsManifest, this.hashFn(contents)

I'm trying to use broccoli-asset-rev to build a CSS library and I'd like to emit

my-library/index.css to my-library/index-1.2.3.css based on process.env.TAG
every other asset with an md5 hash

Additionally, because the md5 hash function is a closure-local, I can't get access to it. I could just copy the implementation, but I'd love if it made available, say as a third argument.
I would write something like
tree = assetRev(tree, {
  customHash: function(contents, inputPath, defaultHashFn) {
    if (process.env.TAG && path === 'my-library/index.css') {
      return process.env.TAG;
    }
    return defaultHashFn(content, inputPath);
  }
});

I'm happy to make a PR if you think this sounds reasonable. If you have any alternative suggestions for this use-case, I'm happy to tweak the API as well.

I'm not necessarily against it, but it seems like it complicates the API a little bit, when you could just include the 3 line hashing yourself in your custom function.
if (procesnt.env.TAG ...) {

}

var md5 = crypto.createHash('md5');
md5.update(buf);
return md5.digest('hex');

Including the hashing function as a third argument is a minor point. I don't mind losing that.
The core was that I wanted the signature of customHash to be (contents, treeRelativePath) so I could use a different function for a subset of resources. Although I suppose I could get the same effect via
indexCss = funnel(tree, { files: [ 'my-library/index.css' ] });
versionedIndexCss = assetRev(indexCss, { customHash: process.env.TAG });

everythingElse = funnel(tree, { exclude: [ 'my-library/index.css' ] });
fingerprintedElse = assetRev(everythingElse);

tree = mergeTrees([ versionedIndexCss, fingerprintedElse ]);

but that's a bit more work both for me and for the computer.

Isn't the path already being passed in?

Sort of. It's passing in the full filesystem path rather than the tree-relative path. I don't have access to the exact tempdir prefix, so I can't easily strip it off. It's also not documented, so I worry that the feature might go away.

It's not going to go away. Can you check for something like indexOf('my-library/index.css') ?

Yeah I can.

It's honestly a fault in the documentation. I need to do a full audit as there are a few features here and there that are permanent but still undocumented.


torcx: add a torcx-generator multicall alias

This adds initial CLI support for a systemd generator called torcx-generator, via multicall argv[0] switch (aliased to torcx apply).
It introduces a multicall package based on rkt one, but with direct cobra support and optional proc self-exe symlink following.

For reference, moving to generators means that some options previously provided as command-line and envinronmental flags will need to be moved to a config file. I'll followup to do that in a later PR.


Integration test

Integration tests upgraded to latest model, and  totally working!
Depreciated items in example updated

Needed for latest flutter versions

They seemed to be used all over theplace in the new framework
https://docs.flutter.dev/cookbook/testing/integration/introduction#4-write-the-integration-test
overall I’m looking at how to future proof this plugin, like how the depreciated parts are now unsupported outright.


[Help] TOC Size

Is the TOC designed to be that small ?

It can be improved for sure, as long as it stays out of the way.
It is so small because we use the Bootstrap grid. On smaller screens, the grid gets too small to fit TOC, in which case TOC looks ugly.
I opted for a quick and dirty solution, i.e. reduce the font size.
What's better?

Use CSS grid and make layout flexible
If grid is small to fit the TOC then hide it and show it only when user clicks a button.

What's better?
1. Use CSS grid and make layout flexible

2. If grid is small to fit the TOC then hide it and show it only when user clicks a button.

Giving recommendation is easy, But I can't say anything for now, since I'm unable to give that PR my self. :)

I have added it to 2019-Q4. It is dependent on #429

:tada: This issue has been resolved in version 5.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


#357 Retry all REST requests on 409 errors

Fixes #357
This uses a different approach than what was proposed in the issue, but the effect should be mostly the same. I drafted up the retrying(() -> kafkaConnectApi.getConnectorConfig(conectorToPatch)) patch but realized that this would still have to be manually applied to all REST calls that could result in a 409 response, which seemed fairly brittle.
I did some research and it looks like we can get retry logic with our auto-generated REST client for free by bringing in a small extra dependency: https://quarkus.io/guides/smallrye-fault-tolerance
Since the API for describing retriable requests with this library is based on exception class, I added custom subclasses to the KafkaConnectException to help us distinguish between retriable and non-retriable operations. We could theoretically create a RetriableKafkaConnectException umbrella class for those, but that feels a little premature, especially since some exceptions may be retriable for only a subset of requests that throw them.
I was able to get 10 consecutive green integration test runs locally with this patch.

Oooh, that's lovely! Much more elegant indeed, great find, and great improvement 🥳 !


Bugsnag not working with laravel 5.4

Hi I recently update to laravel 5.4 , but bug snag seems to use old function of laravel.
I am getting following error.
PHP Fatal error:  Call to undefined method Illuminate\Events\Dispatcher::firing() in /home/vagrant/Code/googleadwords/vendor/bugsnag/bugsnag-laravel/src/BugsnagServiceProvider.php on line 70
PHP Stack trace:
PHP   1. {main}() /home/vagrant/Code/googleadwords/artisan:0
PHP   2. Illuminate\Foundation\Console\Kernel->handle() /home/vagrant/Code/googleadwords/artisan:36
PHP   3. Illuminate\Foundation\Console\Kernel->bootstrap() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:115
PHP   4. Illuminate\Foundation\Application->bootstrapWith() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:270
PHP   5. Illuminate\Events\Dispatcher->fire() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:210
PHP   6. Illuminate\Events\Dispatcher->dispatch() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:172
PHP   7. Illuminate\Events\Dispatcher->Illuminate\Events\{closure}() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:199
PHP   8. Bugsnag\BugsnagLaravel\BugsnagServiceProvider->Bugsnag\BugsnagLaravel\{closure}() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:332
PHP Fatal error:  Call to undefined method Illuminate\Events\Dispatcher::firing() in /home/vagrant/Code/googleadwords/vendor/bugsnag/bugsnag-laravel/src/BugsnagServiceProvider.php on line 70
PHP Stack trace:
PHP   1. {main}() /home/vagrant/Code/googleadwords/artisan:0
PHP   2. Illuminate\Foundation\Console\Kernel->handle() /home/vagrant/Code/googleadwords/artisan:36
PHP   3. Illuminate\Foundation\Console\Kernel->bootstrap() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:115
PHP   4. Illuminate\Foundation\Application->bootstrapWith() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:270
PHP   5. Illuminate\Events\Dispatcher->fire() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:210
PHP   6. Illuminate\Events\Dispatcher->dispatch() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:172
PHP   7. Illuminate\Events\Dispatcher->Illuminate\Events\{closure}() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:199
PHP   8. Bugsnag\BugsnagLaravel\BugsnagServiceProvider->Bugsnag\BugsnagLaravel\{closure}() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:332
PHP   9. Illuminate\Foundation\Bootstrap\HandleExceptions->handleShutdown() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php:0
PHP  10. Illuminate\Foundation\Bootstrap\HandleExceptions->handleException() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php:119
PHP  11. App\Exceptions\Handler->report() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php:80
PHP  12. Illuminate\Foundation\Exceptions\Handler->report() /home/vagrant/Code/googleadwords/app/Exceptions/Handler.php:42
PHP  13. Bugsnag\PsrLogger\AbstractLogger->error() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php:71
PHP  14. Bugsnag\PsrLogger\MultiLogger->log() /home/vagrant/Code/googleadwords/vendor/bugsnag/bugsnag-psr-logger/src/AbstractLogger.php:58
PHP  15. Illuminate\Log\Writer->log() /home/vagrant/Code/googleadwords/vendor/bugsnag/bugsnag-psr-logger/src/MultiLogger.php:38
PHP  16. Illuminate\Log\Writer->writeLog() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Log/Writer.php:175
PHP  17. Illuminate\Log\Writer->fireLogEvent() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Log/Writer.php:201
PHP  18. Illuminate\Events\Dispatcher->dispatch() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Log/Writer.php:297
PHP  19. Illuminate\Events\Dispatcher->Illuminate\Events\{closure}() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:199
PHP  20. Bugsnag\BugsnagLaravel\BugsnagServiceProvider->Bugsnag\BugsnagLaravel\{closure}() /home/vagrant/Code/googleadwords/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:332
Script php artisan clear-compiled handling the post-install-cmd event returned with error code 255

Any help in this regard will greatly appreciated.

Thanks for the report, @rashid-ali4u. What version of bugsnag-laravel are you using?

This problem should have been in the v2.3.0 release I think. Specifically, by: https://github.com/bugsnag/bugsnag-laravel/pull/186

That was my thought as well, but wanted to make sure.

I was using 2.2 version , which was working fine with laravel 5.3. when i updated to laravel 5.4 it did not work. I tried updaating bugsnag version to 2.4 but it did not work.
"require": {
"php": ">=5.5.9",
"laravel/framework": "5.4.",
"laracasts/flash": "^1.3",
"lusitanian/oauth": "~0.3",
"proengsoft/laravel-jsvalidation": "^1.2",
"camroncade/timezone": "^0.1.0",
"sendgrid/sendgrid": "^4.0",
"illuminate/html": "^5.0",
"barryvdh/laravel-debugbar": "^2.0",
"nikolajlovenhardt/laravel-google-ads": "dev-master",
"league/oauth2-google": "^1.0",
"pda/pheanstalk": "~3.0",
"goodby/csv": "^1.2",
"google/apiclient": "^2.1.2",
"guzzlehttp/guzzle": "~6.0",
"arcanedev/log-viewer": "^3.9",
"bugsnag/bugsnag-laravel": "2.4",
"salsify/json-streaming-parser": "^6.0",
"flynsarmy/csv-seeder": "1.",
"league/flysystem-aws-s3-v3": "^1.0",
"dusterio/laravel-aws-worker": "^0.1.9"
},
"require-dev": {
"fzaninotto/faker": "~1.4",
"mockery/mockery": "0.9.",
"phpunit/phpunit": "~5.7",
"symfony/css-selector": "3.1.",
"symfony/dom-crawler": "3.1.*",
"doctrine/dbal": "^2.5"
},

"bugsnag/bugsnag-laravel": "2.4",

That version constraint means exactly <IP_ADDRESS> when composer resolves it. You should probably use ^2.4 or 2.4.*.

I just updated it to  2.4 . But still there is error.

Are you fixing this bug?

Are you fixing this bug?

I can't replicate this. Version 2.4.x does not have code like is shown in your stack trace. It is possible your server is caching an old version of the file.

Thank You , After clearing my cache It is working fine.


Coalescence

I've found this and thought that it is maybe interesting for this project.
https://blog.dottxt.co/coalescence.html#org25a7abb

Interesting! Unfortunately there's not much humanify can do, as it's using llama.cpp for inference under the hood. This would need to be implemented in llama.cpp side, but unfortunately there seems not to be that much interest:
https://github.com/ggerganov/llama.cpp/issues/5292

I see thank you for the explanation.


Matplotlib tests

This PR attempts to improve test coverage for the plotting routines by leveraging the pytest-mpl plugin. The idea here is for the tests to compare the matplotlib output to reference pngs and compare the RMS difference between the two plots (https://github.com/astrofrog/pytest-mpl).
This adds some additional complexity to the test framework because:

an additional dependency
reference plots have to be generated for any new plotting tests (not a big deal via py.test --mpl-generate-path=tests/reference_plots
RMS values are pretty sensitive to things like text placement, which looks like it might vary between matplotlib releases (this issue is mitigated by tuning the reference tolerance)

But the benefits are:

strong test coverage for the plotting routines (both that they produce output and that the result is close to the test reference)
weak constraints on the generate_data routines -- the plot_period_transactions routine relies on the the generate_data code, which wasn't really getting called during testing before. This is a rather indirect way of testing that code, and it doesn't really verify that the routines are providing the correct output other than that the resultant plots are similar to what is expected. However, this should still be enough to detect gross regressions at test time on code that wasn't really being covered before.

I use a different matplotlibrc file locally, that has different styles (mostly default colours). How will these tests behave for that?
(pulling locally to test now)

Hm, so I also think because my default DPI is much higher, I get errors like:
ValueError: operands could not be broadcast together with shapes (600,800,3) (2400,3300,3)

However, I think it's great that TravisCI can now test the images (and it's :green_apple:!). I'm okay forgoing locally testing (and when I do, I can change my default matplotlibrc) so that remote testing is more correct.
:+1: great additions, I didn't know about this lib until now!

Hmm, a local matplotlibrc file would make this a bit more tricky.
I think you could generate your own local reference plots like:
py.test --mpl-generate-path=tests/my_reference_plots

Then when you want to test the plotting routines you could just point to those reference plots:
py.test --mpl --mpl-baseline-path tests/my_reference_plots tests/test_plotting.py

But conveniently, if you just run
py.test

without the --mpl flag, the plotting tests will be run, but they'll only check that the code runs and won't compare the images.


MAIN B-20627 Fix circleci tests and bump dependency

B-20627
INTEGRATION PR-#13866
Summary
The package otelhttp:v.0.43.0 is outdated and needs to be bumped up to the latest version otelhttp:v.0.55.0.
Normally this is managed through dependabot automatically but each time dependabot attempted the bump there were test failures in circlci. You can find the trail of failed PRs by going here. The latest results show that the dependency bump was failing one of the automated tests run by circleci, server_test.
It appears that the test is failing due to the use of deprecated methods http.server.request_content_length and http.server.response_content_length. OpenTelemetry-Go Contrib removed these in otelhttp:v0.49.0 release. It appears that the new methods that need to be used are http.server.request.size and http.server.response.size.
After these tests have been fixed, the package should be able to upgraded in the go.mod file to the latest version otelhttp:v.0.55.0 with all circleci tests passing.
Verification Steps for the Author
These are to be checked by the author.

[x] Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

[ ] Has the branch been pulled in and checked out?
[x] Have the BL acceptance criteria been met for this change?
[x] Was the CircleCI build successful?
[ ] Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test

Login to GitHub.
Open up a DRAFT pull request for MAIN-B-20627-Fix-circleci-tests-and-upgrade-dependency to be merged into main.
Scroll down to the automated tests and wait for the server_test to finish.
Verify the test has passed.

[!NOTE]
Make sure to make the pull request a draft.

Screenshots

Good from my end. Not sure if there is a separate checklist/requirement check for MAIN merges

Didn't see anything on my end kind of just seemed like a copy and paste according to https://transcom.github.io/mymove-docs/docs/getting-started/development/how-to-create-and-submit-PR

@deandreJones I think everything should be good to go for main.


fairseq.data.iterators | Data loading buffer is empty or nearly empty. This may indicate a data loading bottleneck, and increasing the number of workers (--num-workers) may help.

❓ Questions and Help
Before asking:

search the issues.
search the docs.

What is your question?
How can I solve this problem? This warning shows up after a few iterations and it stops training:
fairseq.data.iterators | Data loading buffer is empty or nearly empty. This may indicate a data loading bottleneck, and increasing the number of workers (--num-workers) may help.
Code

#!/bin/bash
#SBATCH --account=XXXXXX
#SBATCH --gres=gpu:v100l:1       # Number of GPUs (per node)
#SBATCH --mem=100G               # memory
#SBATCH --time=06-59:59           # time (DD-HH:MM)
#SBATCH --job-name=script_ca-es
#SBATCH --output=script_ca-es.out
CUDA_VISIBLE_DEVICES=0 fairseq-train data-bin_ca-es/tokenized_ca-es/ --arch transformer --save-dir checkpoints_ca-es  --share-decoder-input-output-embed     --optimizer adam --adam-betas '(0.9,0.98)' --clip-norm 0.0 --lr 5e-4 --lr-scheduler inverse_sqrt --warmup-updates 4000 --dropout 0.3 --weight-decay 0.0001 --criterion label_smoothed_cross_entropy --label-smoothing 0.1 --max-tokens 4096 --eval-bleu --eval-bleu-args '{"beam": 5, "max_len_a": 1.2, "max_len_b": 10}' --eval-bleu-detok moses --eval-bleu-print-samples --best-checkpoint-metric bleu --maximize-best-checkpoint-metric
What have you tried?
I've changed the --num-workers when preparing the preprocessing step.
What's your environment?

fairseq Version (e.g., 1.0 or master):
PyTorch Version (e.g., 1.0): 1.4
OS (e.g., Linux): Linux
How you installed fairseq (pip, source): git clone
Build command you used (if compiling from source):
Python version: 3.6.3
CUDA/cuDNN version: 8.0.44
GPU models and configuration:
Any other relevant information:

Hmm, it was previously printing these too frequently, but that should have been fixed in 14ee059. Can you confirm you're using a commit more recent than that?

Hmm, it was previously printing these too frequently, but that should have been fixed in 14ee059. Can you confirm you're using a commit more recent than that?

I'm using an older version I believe since I downloaded this about 3 weeks ago. Do I just reclone the github to have the updates on my current system?

Yep recloning works

@fenimi Hi! Have you solved this problem？

Hi! I'm still running, I haven't encountered it yet. Like I said it runs for a while before giving errors. I'll post an update when the training is complete

Hi, so regarding the errors, I no longer get the error. However, after loading the last checkpoint, it stops printing anything which I find strange.  It prints this out:
2020-07-05 19:40:49 | INFO | fairseq.trainer | loading train data for epoch 9
2020-07-05 19:40:57 | INFO | fairseq.data.data_utils | loaded 49747362 examples from: data-bin_multi-left-right/multilingual-left-right/train.left-right.left
2020-07-05 19:41:05 | INFO | fairseq.data.data_utils | loaded 49747362 examples from: data-bin_multi-left-right/multilingual-left-right/train.left-right.right
2020-07-05 19:41:05 | INFO | fairseq.tasks.translation | data-bin_multi-left-right/multilingual-left-right train left-right 49747362 examples
I'm not sure why though.
It is still running the model and in about 24 hours nothing has been printed.

Hi, so regarding the errors, I no longer get the error. However, after loading the last checkpoint, it stops printing anything which I find strange. It prints this out:
2020-07-05 19:40:49 | INFO | fairseq.trainer | loading train data for epoch 9 2020-07-05 19:40:57 | INFO | fairseq.data.data_utils | loaded 49747362 examples from: data-bin_multi-left-right/multilingual-left-right/train.left-right.left 2020-07-05 19:41:05 | INFO | fairseq.data.data_utils | loaded 49747362 examples from: data-bin_multi-left-right/multilingual-left-right/train.left-right.right 2020-07-05 19:41:05 | INFO | fairseq.tasks.translation | data-bin_multi-left-right/multilingual-left-right train left-right 49747362 examples
I'm not sure why though.
It is still running the model and in about 24 hours nothing has been printed.

I solved this problem by using an old version（v0.9.0), and it works well, although this is not the best solution.

Hi, so regarding the errors, I no longer get the error. However, after loading the last checkpoint, it stops printing anything which I find strange. It prints this out:
2020-07-05 19:40:49 | INFO | fairseq.trainer | loading train data for epoch 9 2020-07-05 19:40:57 | INFO | fairseq.data.data_utils | loaded 49747362 examples from: data-bin_multi-left-right/multilingual-left-right/train.left-right.left 2020-07-05 19:41:05 | INFO | fairseq.data.data_utils | loaded 49747362 examples from: data-bin_multi-left-right/multilingual-left-right/train.left-right.right 2020-07-05 19:41:05 | INFO | fairseq.tasks.translation | data-bin_multi-left-right/multilingual-left-right train left-right 49747362 examples
I'm not sure why though.
It is still running the model and in about 24 hours nothing has been printed.

I solved this problem by using an old version（v0.9.0), and it works well, although this is not the best solution.

oh okay, thank you for that information.

I installed fairseq from commit 9f92b05 (master HEAD as of now) and am still encountering the same data iterator warnings as the OP. This warning still persists even after increasing --num-workers from 5 up to 20. The script still runs fine but every ~500 updates or so it returns the same warning. Could this be solely attributed to data loading issues or perhaps something else?
Following is the base command I was executing, you can just ignore the shell variables as they are just used for naming stuff:
fairseq-train \
      "data/wmt16_en_de_bpe32k/bin" \
      --arch "$arch" --share-all-embeddings \
      --optimizer adam --adam-betas '(0.9, 0.98)' --clip-norm 0.0 \
      --lr 0.001 --lr-scheduler inverse_sqrt --warmup-updates 4000 --warmup-init-lr 1e-07 \
      --dropout 0.3 --weight-decay 0.0 \
      --criterion label_smoothed_cross_entropy --label-smoothing 0.1 \
      --max-tokens 3584 --fp16 --update-freq 16 \
      --keep-last-epochs 10 --patience 3 --num-workers 5 \
      --save-dir "./models/${arch}.wmt16.de-en.${unix_epoch}" \
      --tensorboard-logdir "./models/${arch}.wmt16.de-en.${unix_epoch}"

PS: I can also verify that I was not receiving this warning in the v0.9.0 release.


Windows以外のサポート

このプロジェクトはWindowsにしか対応していないようです。
Source.cppから#include <Windows.h>を削除して
https://github.com/Nyagamon/HCADecoder/blob/e26b4d3a8bb450224ede3527d522c0330f7bf02b/Source.cpp#L6
Ubuntu 18.04からgcc clHCA.{cpp,h} Source.cpp -o hcbを実行するとこうなります。
ちなみに復号化.batなどがgitにアップロードされていませんが意図的なものでしょうか？
clHCA.cpp: In member function ‘bool clHCA::PrintInfo(const char*)’:
clHCA.cpp:70:6: error: ‘fopen_s’ was not declared in this scope
  if (fopen_s(&fp, filenameHCA, "rb")) {
      ^~~~~~~
clHCA.cpp:70:6: note: suggested alternative: ‘fopen64’
  if (fopen_s(&fp, filenameHCA, "rb")) {
      ^~~~~~~
      fopen64
clHCA.cpp: In member function ‘bool clHCA::Decrypt(const char*)’:
clHCA.cpp:318:6: error: ‘fopen_s’ was not declared in this scope
  if (fopen_s(&fp, filenameHCA, "r+b"))return false;
      ^~~~~~~
clHCA.cpp:318:6: note: suggested alternative: ‘fopen64’
  if (fopen_s(&fp, filenameHCA, "r+b"))return false;
      ^~~~~~~
      fopen64
clHCA.cpp: In member function ‘bool clHCA::DecodeToWavefile(const char*, const char*, float, int, int)’:
clHCA.cpp:469:6: error: ‘fopen_s’ was not declared in this scope
  if (fopen_s(&fp, filenameHCA, "rb"))return false;
      ^~~~~~~
clHCA.cpp:469:6: note: suggested alternative: ‘fopen64’
  if (fopen_s(&fp, filenameHCA, "rb"))return false;
      ^~~~~~~
      fopen64
clHCA.cpp: In member function ‘bool clHCA::DecodeToWavefileStream(void*, const char*, float, int, int)’:
clHCA.cpp:504:6: error: ‘fopen_s’ was not declared in this scope
  if (fopen_s(&fp2, filenameWAV, "wb")) { delete[] data1; return false; }
      ^~~~~~~
clHCA.cpp:504:6: note: suggested alternative: ‘fopen64’
  if (fopen_s(&fp2, filenameWAV, "wb")) { delete[] data1; return false; }
      ^~~~~~~
      fopen64
clHCA.cpp:586:23: error: invalid conversion from ‘void (*)(float, void*)’ to ‘void*’ [-fpermissive]
  void *modeFunction = DecodeToWavefile_DecodeMode16bit;
                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
clHCA.cpp:588:24: error: invalid conversion from ‘void (*)(float, void*)’ to ‘void*’ [-fpermissive]
  case 0:modeFunction = DecodeToWavefile_DecodeModeFloat; break;
                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
clHCA.cpp:589:24: error: invalid conversion from ‘void (*)(float, void*)’ to ‘void*’ [-fpermissive]
  case 8:modeFunction = DecodeToWavefile_DecodeMode8bit; break;
                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
clHCA.cpp:590:25: error: invalid conversion from ‘void (*)(float, void*)’ to ‘void*’ [-fpermissive]
  case 16:modeFunction = DecodeToWavefile_DecodeMode16bit; break;
                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
clHCA.cpp:591:25: error: invalid conversion from ‘void (*)(float, void*)’ to ‘void*’ [-fpermissive]
  case 24:modeFunction = DecodeToWavefile_DecodeMode24bit; break;
                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
clHCA.cpp:592:25: error: invalid conversion from ‘void (*)(float, void*)’ to ‘void*’ [-fpermissive]
  case 32:modeFunction = DecodeToWavefile_DecodeMode32bit; break;
                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
clHCA.cpp: In member function ‘void clHCA::clCipher::Init56(unsigned int, unsigned int)’:
clHCA.cpp:808:15: warning: narrowing conversion of ‘(int)(((unsigned char)((int)t1[1])) ^ ((unsigned char)((int)t1[6])))’ from ‘int’ to ‘unsigned char’ inside { } [-Wnarrowing]
   t1[1],t1[1] ^ t1[6],
         ~~~~~~^~~~~~~
clHCA.cpp:809:9: warning: narrowing conversion of ‘(int)(((unsigned char)((int)t1[2])) ^ ((unsigned char)((int)t1[3])))’ from ‘int’ to ‘unsigned char’ inside { } [-Wnarrowing]
   t1[2] ^ t1[3],t1[2],
   ~~~~~~^~~~~~~
clHCA.cpp:810:9: warning: narrowing conversion of ‘(int)(((unsigned char)((int)t1[2])) ^ ((unsigned char)((int)t1[1])))’ from ‘int’ to ‘unsigned char’ inside { } [-Wnarrowing]
   t1[2] ^ t1[1],t1[3] ^ t1[4],
   ~~~~~~^~~~~~~
clHCA.cpp:810:23: warning: narrowing conversion of ‘(int)(((unsigned char)((int)t1[3])) ^ ((unsigned char)((int)t1[4])))’ from ‘int’ to ‘unsigned char’ inside { } [-Wnarrowing]
   t1[2] ^ t1[1],t1[3] ^ t1[4],
                 ~~~~~~^~~~~~~
clHCA.cpp:811:15: warning: narrowing conversion of ‘(int)(((unsigned char)((int)t1[3])) ^ ((unsigned char)((int)t1[2])))’ from ‘int’ to ‘unsigned char’ inside { } [-Wnarrowing]
   t1[3],t1[3] ^ t1[2],
         ~~~~~~^~~~~~~
clHCA.cpp:812:9: warning: narrowing conversion of ‘(int)(((unsigned char)((int)t1[4])) ^ ((unsigned char)((int)t1[5])))’ from ‘int’ to ‘unsigned char’ inside { } [-Wnarrowing]
   t1[4] ^ t1[5],t1[4],
   ~~~~~~^~~~~~~
clHCA.cpp:813:9: warning: narrowing conversion of ‘(int)(((unsigned char)((int)t1[4])) ^ ((unsigned char)((int)t1[3])))’ from ‘int’ to ‘unsigned char’ inside { } [-Wnarrowing]
   t1[4] ^ t1[3],t1[5] ^ t1[6],
   ~~~~~~^~~~~~~
clHCA.cpp:813:23: warning: narrowing conversion of ‘(int)(((unsigned char)((int)t1[5])) ^ ((unsigned char)((int)t1[6])))’ from ‘int’ to ‘unsigned char’ inside { } [-Wnarrowing]
   t1[4] ^ t1[3],t1[5] ^ t1[6],
                 ~~~~~~^~~~~~~
clHCA.cpp:814:15: warning: narrowing conversion of ‘(int)(((unsigned char)((int)t1[5])) ^ ((unsigned char)((int)t1[4])))’ from ‘int’ to ‘unsigned char’ inside { } [-Wnarrowing]
   t1[5],t1[5] ^ t1[4],
         ~~~~~~^~~~~~~
clHCA.cpp:815:9: warning: narrowing conversion of ‘(int)(((unsigned char)((int)t1[6])) ^ ((unsigned char)((int)t1[1])))’ from ‘int’ to ‘unsigned char’ inside { } [-Wnarrowing]
   t1[6] ^ t1[1],t1[6],
   ~~~~~~^~~~~~~
clHCA.h:1:9: warning: #pragma once in main file
 #pragma once
         ^~~~
clHCA.h:6:1: error: unknown type name ‘class’
 class clHCA {
 ^~~~~
clHCA.h:6:13: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token
 class clHCA {
             ^
Source.cpp: In function ‘int main(int, char**)’:
Source.cpp:111:13: error: ‘MAX_PATH’ was not declared in this scope
   char path[MAX_PATH];
             ^~~~~~~~
Source.cpp:113:13: error: ‘path’ was not declared in this scope
    strcpy_s(path, sizeof(path), argv[i]);
             ^~~~
Source.cpp:113:13: note: suggested alternative: ‘putw’
    strcpy_s(path, sizeof(path), argv[i]);
             ^~~~
             putw
Source.cpp:113:4: error: ‘strcpy_s’ was not declared in this scope
    strcpy_s(path, sizeof(path), argv[i]);
    ^~~~~~~~
Source.cpp:114:15: error: ‘strrchr’ was not declared in this scope
    char *d1 = strrchr(path, '\\');
               ^~~~~~~
Source.cpp:114:15: note: suggested alternative: ‘struct’
    char *d1 = strrchr(path, '\\');
               ^~~~~~~
               struct
Source.cpp:118:4: error: ‘strcat_s’ was not declared in this scope
    strcat_s(path, sizeof(path), ".wav");
    ^~~~~~~~
Source.cpp:118:4: note: suggested alternative: ‘static’
    strcat_s(path, sizeof(path), ".wav");
    ^~~~~~~~
    static

https://github.com/y2361547758/hca.js
https://github.com/OpenCGSS/DereTore


doesn't work

I've been trying to figure this out for the last day or two with no luck. I receive the same error.

I seem to be getting a different error now,
`                         pip install -r extensions\Memoir\requirements.txt --upgrade
13:22:53-633010 ERROR    Failed to load the extension "Memoir".
Traceback (most recent call last):
File "E:\Oobabooga\text-generation-webui\modules\extensions.py", line 37, in load_extensions
extension = importlib.import_module(f"extensions.{name}.script")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "E:\Oobabooga\text-generation-webui\installer_files\env\Lib\importlib_init_.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1204, in _gcd_import
File "", line 1176, in _find_and_load
File "", line 1147, in _find_and_load_unlocked
File "", line 690, in _load_unlocked
File "", line 940, in exec_module
File "", line 241, in _call_with_frames_removed
File "E:\Oobabooga\text-generation-webui\extensions\Memoir\script.py", line 27, in
from extensions.Memoir.commandhandler import CommandHandler
File "E:\Oobabooga\text-generation-webui\extensions\Memoir\commandhandler.py", line 7, in
from extensions.Memoir.commands.urlhandler import UrlHandler
File "E:\Oobabooga\text-generation-webui\extensions\Memoir\commands\urlhandler.py", line 2, in
from bs4 import BeautifulSoup
ModuleNotFoundError: No module named 'bs4'
Running on local URL:  http://<IP_ADDRESS>:7860
`

Unfortunately, nothing helped.

pip install beautifulsoup4

I still got an error after this, but I ended up updating/reinstalling all extensions from the update_wizard_windows.bat and it started working just fine. Thank you for your help!

Unfortunately, nothing helped.

See my reply above. I had the same error until I updated/installed everything.

Hmm, could be an update doing it. From here https://pypi.org/project/python-on-whales/ looks like it was released Apr 24. I will review a clean install and see if I can figure it out. It seems that docker has been the thorn in many peoples side on install, I may have to release one that doesn't use docker and just uses the qdrant binaries. Do you have docker desktop installed?

I have docker installed. Once I ran an update for all extensions it's been working just fine, so I haven't able to pinpoint the issue. It doesn't seem to be docker related, at least on my end. Either way, your recent updates solved all of the problems I've been having for the last few days. It's been working properly as of the last few hours.

Unfortunately, nothing helped.

See my reply above. I had the same error until I updated/installed everything.

Of course I installed and double-checked all updates and dependencies, but it still didn't work in my case.

Oops.. now I see where my mistake was. Everything works well. Sorry!


ORCA screen reader is not announcing the whole suggested information when we are typing in the copilot chat box: A11y_VS Code extension for API Center_Copilot Chat_ScreenReader.

"Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier."
Please do not close this bug. This bug should only be closed by Trusted Tester after verification.
GitHub Tags
#A11yTCS; #A11yMAS; #A11ySev2; #WCAG1.3.1; #GH_VSCodeextensionforAPICenter_Linux_Apr2024; #DesktopApp; #VS Code Extension for API Center; #ORCA; #Linux; #FTP; #Element:Dropdown;
Actual Result:
ORCA screen reader is not announcing the whole suggested information when we are typing in the copilot chat box
Expected Result:
NVDA/Jaws should announce the whole suggested information when we are typing in the copilot chat box. for ex. if we are typing @apicenter in the copilot chat then screen reader should also announce Build, consumer and consume great APIs.
Environment Details:
Application Name: VS Code Extension for API Center
OS: Windows 11 Enterprise 23H2 (OS build 22631.3296)
Screen reader: ORCA
Repro Steps:

Start ORCA screen reader.
Create an API center in azure portal.
Open Visual studio Code.
Tab till Chat option in the left side panel and press enter.
Type @apicenter in chat box.
Verify whether the ORCA screen reader is not announcing the whole suggested information when we are typing in the copilot chat box.

User Impact:
Screen reader will not know about the whole information if the screen reader is not announcing it.
Attachment:

External issue. This UI control is from GitHub Copilot Chat: https://github.com/microsoft/vscode-copilot-release

@formulahendry As per the C+AI accessibility testing external bug process primary team need to file the bug to VSCode team & share us the external bug ID.

This issue is caused by UI of GitHub Copilot Chat extension, not related to UI of API Center extension.

Opened bug in vs code repo: https://github.com/microsoft/vscode/issues/212320

#FirstParty:Bug212320; #External: #External:VS Code;

Closing this bug as "This issue is caused by UI of GitHub Copilot Chat extension, not related to UI of API Center extension".


Hinge loss issue

Hinge loss does not seem to work unless y_cal is re-indexed from zero.
alphas_cal = hinge(model.predict_proba(X_cal), model.classes_, y_cal)
KeyError: 0
The above exception was the direct cause of the following exception:
KeyError                                  Traceback (most recent call last)
 in <cell line: 1>()
----> 1 alphas_cal = hinge(model.predict_proba(X_cal), model.classes_, y_cal)
/usr/local/lib/python3.10/dist-packages/crepes/extras.py in hinge(X_prob, classes, y)
69     if y is not None:
70         class_indexes = np.array(
---> 71             [np.argwhere(classes == y[i])[0][0] for i in range(len(y))])
72         result = 1-X_prob[np.arange(len(y)),class_indexes]
73     else:
/usr/local/lib/python3.10/dist-packages/crepes/extras.py in (.0)
69     if y is not None:
70         class_indexes = np.array(
---> 71             [np.argwhere(classes == y[i])[0][0] for i in range(len(y))])
72         result = 1-X_prob[np.arange(len(y)),class_indexes]
73     else:
/usr/local/lib/python3.10/dist-packages/pandas/core/series.py in getitem(self, key)
1005
1006         elif key_is_scalar:
-> 1007             return self._get_value(key)
1008
1009         if is_hashable(key):
/usr/local/lib/python3.10/dist-packages/pandas/core/series.py in _get_value(self, label, takeable)
1114
1115         # Similar to Index.get_value, but we do not fall back to positional
-> 1116         loc = self.index.get_loc(label)
1117
1118         if is_integer(loc):
/usr/local/lib/python3.10/dist-packages/pandas/core/indexes/base.py in get_loc(self, key)
3653             return self._engine.get_loc(casted_key)
3654         except KeyError as err:
-> 3655             raise KeyError(key) from err
3656         except TypeError:
3657             # If we have a listlike key, _check_indexing_error will raise
KeyError: 0

Thanks for pointing this out; it seems to be due that the label vector is a pandas.series and not a NumPy array, which causes a problem with (integer) indexing. This has been fixed in the just released v. 0.7.0.
Best regards,
Henrik


Firefox issue

Firefox doesn't render this correctly on http://techweek.dcu.ie/CFT/

I presume you mean spacing on the left and right correct?

Look at the words on the first few lines


Support new query to fetch gallery pages

For example on https://main--helix-sportsmagazine--headwirecom.hlx.page/golf-news-tours, the XXL cards should display gallery links instead of article links

cc @DriftingSands

This is already fixed


nixos/doc: remove mention of test log

Motivation for this change
The test log isn't created with the Python test harness.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

would be nice to still have access to the logs documented somehow. do you know if nix-store --read-log result works?

would be nice to still have access to the logs documented somehow. do you know if nix-store --read-log result works?

Nice catch, it does work. I'll close this PR and open a new one changing it to that.


[LOCAL, DOCKER]:  Browse all brews in database

For local installs only, it would be useful to be able to see all brews in the database, regardless of the brew's author.
This may be possible by wrapping a path definition in server.js in an if block that checks for non-production environments; e.g. NODE_ENV == 'local' || NODE_ENV == 'docker'

How would you see this working? As an endpoint or a change to the brew listing page?


Trim source paths in final Go binaries [phab:D846]

Created by schroederc at 2016-04-20 22:20:10:

shahms commented inline (context lost during migration) at 2016-04-20 22:27:10:
does this not work if you omit "$PWD/" from the GOROOT?

schroederc commented inline (context lost during migration) at 2016-04-20 22:32:55:
It will remove $PWD either way but using GOROOT_FINAL makes it use the standard /usr/local/go prefix instead of external/local_goroot.

shahms commented inline (context lost during migration) at 2016-04-20 22:39:33:
Sure, but in general the less "$PWD" we have in our scripts/build rules the better.  If go will build fine with a relative GOROOT, we should prefer that.  There are absolutely situations where we'll have to form absolute paths using PWD, but those should generally be limited to circumstances in which we have to change directory manually to work around the failings of an external tool rather than the default assumption.

schroederc wrote at 2016-04-20 22:48:06:
Remove $PWD

schroederc commented inline (context lost during migration) at 2016-04-20 22:48:27:
If you just want $PWD gone, that's fine.

shahms wrote at 2016-04-20 22:49:22:
lol, thanks :-)

shahms accepted this revision at 2016-04-20 22:49:22

schroederc closed via commit 84be8ae6a4c1c9d4f9e8851774df39b20ec2b9b9 at 2016-04-20 22:50:33


Make matchers more consistent

should be... vs shouldBe should be unified. And I would prefer to have a consistent syntax in usual function call style OR DSL style (without dots and parenthesis), but not both. See my post.

The expect.kt library is not bad, although I would prefer a single style and having having a separate negation (not) would be nice. Another thing that I would change is the and , since it adds some clutter (though readable) and looks bad with line breaks. But I think this lib could be an inspiration.
I like it, when the tested value is in the front of the line.
What do you think of a syntax like this?
false.should.not.beTrue

"".should.beEmpty

"james".should
    .haveLength(5)
    .startWith("j")
    .contain("me")

I like the chaining aspect. I like the fact with dot syntax you can do more, because its less ambiguous to the compiler. I also like the fact that expect.kt offers several styles, even though you don't like this (doesn't really matter if we have .should and .is or whatever?)

I added a reply in the groups, that I sent ages ago but didn't seem to appear @helmbold

I've added an attempt to make the DSL more readable. There's still a bit more left to do, but wanted to see what you think first.
https://github.com/kotlintest/kotlintest/blob/issue138/src/test/kotlin/io/kotlintest/matchers/MatcherDsl.kt

I like the DSL, it is clean and readable. Some thoughts:

1 shouldBe beGreaterThan(0) and beLessThan(2) I think the first Be (in shouldBe) shouldn't be there?
I wonder, whether the and is worth it, although it looks very nice and readable. Have you considered how it looks/works with line breaks?
I think it would be useful to have a separate not. But in both cases (shouldNot and should not) it could be ambiguous, since it could be confusing what parts are actually negated. That would be better if we had two variants of each matcher (e. g. contain and notContain).
How would you express a parameterless matcher: beTrue or beTrue()?

"hello world" shouldNot startWith("hello") and endWith("world") and include("!")
"hello world" shouldNot
    startWith("hello") and
    endWith("world") and
    include("!")

"hello world".shouldNot.startWith("hello").endWith("world").include("!")
"hello world".shouldNot
    .startWith("hello")
    .endWith("world")
    .include("!")

Yes, duplicate 'be' is just a mistake
Works with line breaks as such

    "hello world" should
        startWith("hello") and
        endWith("world") and
        include("")

shouldNot is better because should not won't parse without something else in there too. We can provide inverted matchers like notContain as well, so then the user can choose whatever they want.
I don't think it really matters, you can choose.

There is an issue I'm trying to work around. In order to support and and or we need to return some kind of builder object from the should function, since in Kotlin the compiler will not consider a look ahead when parsing infix functions. Which means the should function cannot be the function that invokes the matcher (it has to return a matcher accumulator of some sort and can't do both things). I work around this by having the should function add the accumulator to the list of matchers in the spec class, which it then can invoke after the test function itself returns. However, this won't work with inspectors, as they expect the matchers to throw exceptions. One solution would be to have any code in an inspector wrap itself around any matchers added, kind of like the interceptors.

I wouldn't use the spec class for the matcher DSL. This would introduce a strange dependency in the code. I would design the matchers so that we could release them separately (what could be a good idea for users of other test frameworks). I'd prefer a different syntax if it is not possible to achieve the aspired solution.

And, by the way, I wouldn't introduce or, since it would need to have some grouping then. If such a logic is really needed in a test, it could be expressed with usual Kotlin constructs and only the result could be tested with matchers.

Another nice assertions lib (for JavaScript) is Chai

I think shouldBe should test for idenentity:
infix fun <T> T.shouldBe(any: Any?): Unit = shouldEqual(any)
infix fun <T> T.shouldEqual(any: Any?): Unit

Identity??
On 18 Jan 2017 20:20, "Christian Helmbold"<EMAIL_ADDRESS>wrote:

I think shouldBe should test for idenentity:
infix fun  T.shouldBe(any: Any?): Unit = shouldEqual(any)infix fun  T.shouldEqual(any: Any?): Unit
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kotlintest/kotlintest/issues/138#issuecomment-273589856,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtZGgMH-hRoMCN23SJ7Tq_yNkWi8eW3ks5rTnPvgaJpZM4Lk__m
.

If we have shouldEqual we should use shouldBe to check referential equality (or identity): a === b

They're just synonyms. We can't keep changing semantics on people.

Just looked at Chai and it looks similar to the others. Its what you'd write if you couldn't use infix methods, as you can't in Javascript. I mean it looks fine, but it offers 3 different styles and you said you prefer having only one style - which one of those do you like the most?
I am all for trying to tidy things up, but I do think a lot of the discussion here is just "it's not the way I'd have written it" which is not a valid reason for making people change all the tests they've written using the matchers from KotlinTest 1.x.
I think that unless there's a good reason to change things (and there might well be lots of good reasons and I'm totally in favour of us debating it) that we should keep it the same. I actually like the scalatest style and I'm sure others do, and others won't including yourself.

Maybe some things are just a matter of taste, but we should try to be as consistent as possible - and that was my original intention (e. g. should be... vs shouldBe). Now is the best time to change such things, since I expect that the adoption would increase significantly after 2.0 release (not overnight, of course).

I agree its best to lock it down now, and I also agree that should be vs shouldBe is noise. That can go.

I thought about parameterless matchers like isTrue and prefer functions over properties here, because it is easy to remember that we're always using function and because it has a side effect (throwing an exception).
Example: isTrue() instead of isTrue

Agreed

So looking over our matchers again and I'm ok with it. I'm personally not that bothered about should and shouldBe being aliases - it means you can write whichever sounds more grammatically correct.
I've removed the 'be' keyword, and the keyword interface itself. That's noise which we don't need. This means all matchers must simply be a function which returns a Matcher<T> instance, and we drop any ideas of doing fancy this should have length 10 in favour of just this should haveLength(10).
I'm in favour of closing this now.

We have still this inconsistency with shouldBe and should be.... You can write things like this: "x" shouldBe beEmpty<String>(), whereas x" should beEmpty<String>() is not possible.
I think we should only provide should and shouldNot.

Yes you can, but you'd have to be a fool to do that. We can't stop people being fools and we shouldn't try.

How would you test for an empty string? As mentioned above "x" should beEmpty<String>() doesn't work, but that would be the obvious way (despite the possible unnecessary type parameter).

Could add str shouldBe emptyString ()
On 18 Mar 2017 13:35, "Christian Helmbold"<EMAIL_ADDRESS>wrote:

How would you test for an empty string? As mentioned above "x" should
beEmpty() doesn't work, but that would be the obvious way
(despite the possible unnecessary type parameter).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kotlintest/kotlintest/issues/138#issuecomment-287546764,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtZGiUZAhhZyu7valnsBHAGequzztmQks5rm92pgaJpZM4Lk__m
.

I wouldn't add emptyString, since this is not really better than beEmpty<String>. I thought of using a star projection in fun <T> beEmpty(): Matcher<Collection<T>>, but I didn't find a way to do it. In principle Collection<*> would be sufficient.
But my main point is, that "x" should beEmpty<String>() doesn't compile, and that we have the confusing alternatives of should be... and shouldBe.

I know why you were bringing it up :)
On 18 Mar 2017 21:40, "Christian Helmbold"<EMAIL_ADDRESS>wrote:

I wouldn't add emptyString, since this is not really better than
beEmpty. I thought of using a star projection in fun
beEmpty(): Matcher<Collection>, but I didn't find a way to do it. In
principle Collection<*> would be sufficient.
But my main point is, that "x" should beEmpty() doesn't compile,
and that we have the confusing alternatives of should be... and shouldBe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kotlintest/kotlintest/issues/138#issuecomment-287576888,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtZGlkby8b4BYX20jROyz9XlhHqz0jGks5rnE9kgaJpZM4Lk__m
.

What's wrong with adding an emptyString matcher. Although you could use the collection matcher, there's no problem with having one just for string that means it reads easier for someone reading the code?

Adding emptyString as a special case would be a little inconsistency and would affect learnability. Why not emptyList then ... ?

It's not a special case anymore than String itself is a special case. I'd be happy to have emptyList too. What's wrong with extra options if that means that the tests read clearer? What's the disadvantage to adding them - some kind of purity that means nothing?

I want to avoid that someone wonders about a missing method like emptyThing. If we just provide the generic method, empty<Thing>() is obvious. Actually I'd prefer empty(), since it is not important whether it is a String, a List or some other type. And using a type parameter separates the important empty from the less important type.
However that is not the point I want to make. I could live with emptyString(), emptyList() and so on. What is important, is that we have a way to make "x" should beEmpty<String>() compile and that we remove shouldBe.

Ok, if we remove shouldBe then what do we do about 3 shouldBe lessThan(4) ?
3 should beLessThan(4) which is less readable imho.
I don't know it's important to not have should and shouldBe. There's many different ways of doing things in Java, Kotlin and Scala. That's part of a powerful language.
I do,
option.foreach(builder.add)
You do
option.foreach { x => builder.add(x) }
Your friend does
option match {   case Some(x) => builder.add(x)   case _ => }
The great thing about should and shouldBe is that we can let the user choose which one is more readable for their test. When it comes to custom matchers, we should probably add shouldHave as well!
I'm of the school that you cannot stop bad developers abusing things, so why try? That's not the job of a good library. A good library should stop you making mistakes, not try to stop you deliberately making a hash of it, as that's impossible.

I have to admit that 3 shouldBe lessThan(4) looks better than 3 should beLessThan(4). So, yes, maybe we need a bigger API here. But let's make sure that all imaginable combinations are working.

As long as we have a grammar of the form:
assertion:= value keyword matcher | value 'shouldBe' value
value:= literal of T | variable of T
keyword:= 'should' | 'shouldBe' | 'shouldHave' | 'shouldSomethingElse'
matcher:= Matcher<T>

Then I think its regular.

@helmbold its been a week just discussing this should vs shouldBe. I want to release KotlinTest 2 before Kotlin 1.2 comes out :)
You seem a bit happier with shouldBe. Lets release?

shouldBe would be ok, but the API is still not satisfying. And it is still not possible to write "" shouldBe empty(), "" shouldBe emptyString() or "" shouldBe empty<String>(). Take a look at the unhelpful syntax completion suggestions for " " shouldBe.

Even if you'd provide a . you won't get helpful code completion:

You get much better code completion with the good, old AssertJ.
I see the matchers API as a weakness of KotlinTest. If you want to release KotlinTest 2.0 in a few days (and I want to get it out of the door, too!), I'd vote for separating the matchers API and realsing KotlinTest 2.0 without matchers.
I've experimented with a more "classic" (and less DSL-style) approach like this:
list.should.contain(2).haveSize(3).equal(listOf(1, 2, 3)).beEmpty

However my matcher library is far from being complete.

Well the matchers auto completed until you made them all top level
functions :)
On 27 Mar 2017 20:21, "Christian Helmbold"<EMAIL_ADDRESS>wrote:

shouldBe would be ok, but the API is still not satisfying. And it is
still not possible to write "" shouldBe empty(), "" shouldBe emptyString()
or "" shouldBe empty(). Take a look at the unhelpful syntax
completion suggestions for " " shouldBe.
[image: shouldbe]
https://cloud.githubusercontent.com/assets/5079980/24373385/868672bc-1331-11e7-85a3-8b6aeacaca93.png
Even if you'd provide a . you won't get helpful code completion:
[image: shouldbe2]
https://cloud.githubusercontent.com/assets/5079980/24373769/bfea4ff0-1332-11e7-953a-fe8ae36d2ef2.png
You get much better code completion with the good, old AssertJ.
I see the matchers API as a weakness of KotlinTest. If you want to release
KotlinTest 2.0 in a few days (and I want to get it out of the door, too!),
I'd vote for separating the matchers API and realsing KotlinTest 2.0
without matchers.
I've experimented with a more "classic" (and less DSL-style) approach like
this:
list.should.contain(2).haveSize(3).equal(listOf(1, 2, 3)).beEmpty
However my matcher library is far from being complete.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kotlintest/kotlintest/issues/138#issuecomment-289557411,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtZGo9FPeVoLMqP-5KZCreiK715uL_hks5rqAwrgaJpZM4Lk__m
.

That is a bad side effect, I hadn't thought of. However, I think the structural improvement was right. Think, for example, if someone wants to use another matcher lib and doesn't want to be confused by the shipped matchers. But the result in the current form is not satisfying. I see several options:

leave it as is (besides minor improvements)
redesign the matchers API (and delay KotlinTest 2.0 further)
remove the matchers API and deliver it separately and improve/redesign the API after KotlinTest 2.0

Kotlintest 2 is already released as we couldn't wait any longer. I
mentioned it in the issues on github and I also spoke about it in the
gitter room. I'm sorry if we crossed our wires on it and you didn'tsee the
discussion. I thought you might have beeb away or something.
But onto the main discussion. I think our matchers are the key part of the
product. The specs are nice but even junit isn't that bad for laying out
tests. It's about the whole experience and matchers are a part of that
along with table testing and eventually and so on.
People can still easily use other matchers with no issue and I don't think
we should worry about other products over our own. We should be aiming for
kotlintest matchers to be the default go to option in Kotlin and if not why
not. Are they not good enough. If so lets improve them not think about
removing them or splitting them. Imo of course.
On 28 Mar 2017 7:02 pm, "Christian Helmbold"<EMAIL_ADDRESS>wrote:

That is a bad side effect, I hadn't thought of. However, I think the
structural improvement was right. Think, for example, if someone wants to
use another matcher lib and doesn't want to be confused by the shipped
matchers. But the result in the current form is not satisfying. I see
several options:

leave it as is (besides minor improvements)
redesign the matchers API (and delay KotlinTest 2.0 further)
remove the matchers API and deliver it separately and
improve/redesign the API after KotlinTest 2.0

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kotlintest/kotlintest/issues/138#issuecomment-289854293,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtZGuWy8r9JTW4vuGNByiWOluz-odhoks5rqUs5gaJpZM4Lk__m
.

I've somehow missed the 2.0 release (and didn't expect it, since the 2.0 branch is still there and there were open issues). I think we can close this issue now.

We just needed to get the release out as we had loads of changes just building up. We can still have the discussion about matchers and then make changes in 2.1 2.2 3.0 or 100.0 if any are needed.


How would I make webpack resolve a remotely hosted modules?

How would I get webpack to fetch and bundle remotely hosted js modules.
Here's an example of what I'm trying to achieve. Imagine this file
https://example.com/static/js/main.js
import * as core from 'https://example.com/static/js/core.js'
... more imports

And 'https://example.com/static/js/core.js'
import * as models from 'https://example.com/static/js/models.js';
import * as models from '/static/js/api.js'; // would resolve to https://example.com/static/js/api.js
import * as redux from 'https://cdn.example.com/redux.js';

So here's the thing, I'd like to be able to bundle https://example.com/static/js/main.js in a way that it fetches and bundle the models.js files and possibly include or exclude redux with a regex as it's on a cdn.
This way I could tell the browser to load it from the cdn or pack it the same way it would fetch and load models.js
When I try to run webpack, it simply fail with a resolve Error and I didn't see how I could resolve and fetch the files asynchronously.

Closing as it may be an issue more related to enhanced-resolve


Water Sensors- WBS

Rep 1 Cover never made the initial connection. Do we know if this node is printing data? Rep 2 Cover went offline 07/02/2022. Rep 1 and 2 Bare went completely offline on 07/13/2022. Device status shows data from 2 nodes 07/18/2022, one Rep 1 and one Rep 2 but this is not reflected in the chart view on the tech dashboard. Do we know if this site has the data from the meantime between 07/02 and present-day as well as 07/13 and present-day for the sensors to which it applies? Please update what we know below.

Sent Ryan the following:
Gateway is only connected to nodes #18001812 and #18001833
Check to see that the other two nodes are turned on and everything is connected
Print off the logs for this field from the nodes and gateway and email them to Ethan
Try resetting the nodes and gateway to see if that resolves the issue

The node for BT-1 is not connecting to the gateway for some reason. It's allocated to the correct gateway in the field.
Instructed Bryan (tech for this site) to leave it alone and that he'll have to come back every so often and manually download the data.


Section "Add parameters to Completion rule" needs to be fixed to match the real portal

In the section "Add parameters to Completion rule" it was not clear to me if I should be deleting the rule I crated as part of the previous quick start I did, or keep it and modify it.
Also it says "1. Add a new Condition and select Required parameter. Select both OnOff and SubjectDevice". But when I look at "New Condition" window in the portal I see 4 options. None of them are "Required parameter". I see "updated parameters", "confirmation was denied", "confirmation was successful"  and "update last command".
Not clear to me what I should do now.
Thanks,
Darren

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

ID: 172ca5fe-18be-3fa8-38e8-b72461192abc
Version Independent ID: f6f45c1b-9cf9-986a-01ad-5b2d73992911
Content: Quickstart: Create a Custom Command with Parameters (Preview) - Speech service - Azure Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/quickstart-custom-speech-commands-create-parameters.md
Service: cognitive-services
Sub-service: speech-service
GitHub Login: @don-d-kim
Microsoft Alias: donkim

@dargilco we will review your feedback and get back to you shortly. Thanks.

@don-d-kim please take note of the above feedback for doc enhancement.


Create a fallback to the supported_servers file, and read the server list from a local file

Describe the bug
Asian users sometimes have issues while performing requests to the GitHub to read the supported_servers.json, in that case we can read the local file as a fallback.
To Reproduce
Steps to reproduce the behavior:

Open 4RTools
Block requests to supported_servers.json

Expected behavior
Setting a timeout or rescue exception when performing a request to the supported_servers, once receives an error, instead of stop the application, try to read a local file as a fallback.
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
N/A

Workin on it.

#126


[Help needed] Tab Indicator at the top

Tried many ways, but none worked. Can somebody help me in showing the tab indicator at the top instead of showing it like by default at the bottom.
Something like this:

react-native: 0.63.3
react-native-tab-view: 2.15.2
react-native-gesture-handler: 1.8.0
react-native-reanimated: 1.13.1

Fixed by adding top:0 to indicatorStyle prop


clicking the a element reloads page (ngRoute),  instead of pointing to anchor.

When clicking on any link. AngularJS intercepts and routes me to a completely different page (in my case, a 404-page as there are no routes matching the links.)
I would like to know if this library takes cares of that, or what do you suggest to stop the routing event ?
Thanks.

Maybe I ask which directive you are using?

mac-scroll-spy-target
mac-scroll-spy-anchor

mac-scroll-spy-target and mac-scroll-spy-anchor shouldn't affect anchor behavior. The two directives only monitor the top offset of each anchor and highlight the target when user scroll into view.
Can you post a code sample to places like plunkr? Thanks.

Let me clarify that everything works good. My question is if some of your directives handle the ui-route behavior suppression, that is, rather than letting the router to redirect after clicking URL, the link should point to the anchor. So question is, should I workaround that myself?

None of the directives prevent default from happening so you will have to add the suppression yourself.

Closing this issue. Please reopen if more help is needed.


Flaky receive unit test

**Full logs to relevant components**:
--- FAIL: TestReloader_DirectoriesApply (3.01s)
    reloader_test.go:256: Performing step number 0
    reloader_test.go:256: Performing step number 1
    reloader_test.go:256: Performing step number 2
    reloader_test.go:256: Performing step number 3
    reloader_test.go:256: Performing step number 4
    reloader_test.go:256: Performing step number 6
    reloader_test.go:343: reloader_test.go:343:

        	exp: 5

        	got: 6
       ```

Why is it receive unit test in the title? (: Looks like reloader to me

Yeah.. you're right.
I actually thought it was the receiver. Would edit right away @bwplotka

Seems like there's an ongoing thread for this issue in #2622
Would close this for now.


terraform plugin crashes via slow cloning or sth while cloning existing template

│ Error: Plugin did not respond
│
│   with proxmox_vm_qemu.first-tf-vm,
│   on main.tf line 19, in resource "proxmox_vm_qemu" "first-tf-vm":
│   19: resource "proxmox_vm_qemu" "first-tf-vm" {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ApplyResourceChange call. The plugin logs may contain more details.
╵
Stack trace from the terraform-provider-proxmox_v2.9.14 plugin:
panic: interface conversion: interface {} is string, not float64
goroutine 81 [running]:
github.com/Telmate/proxmox-api-go/proxmox.NewConfigQemuFromApi(0xc000142718, 0xc9d509?)
github.com/Telmate/proxmox-api-go@v0.0.0-20230319185744-e7cde7198cdf/proxmox/config_qemu.go:584 +0x4605
github.com/Telmate/terraform-provider-proxmox/proxmox.resourceVmQemuCreate(0xc000357080, {0xb66f60?, 0xc00031c370})
github.com/Telmate/terraform-provider-proxmox/proxmox/resource_vm_qemu.go:972 +0x2c4d
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).create(0xdd7840?, {0xdd7840?, 0xc0004d0f90?}, 0xd?, {0xb66f60?, 0xc00031c370?})
github.com/hashicorp/terraform-plugin-sdk/v2@v2.25.0/helper/schema/resource.go:695 +0x178
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).Apply(0xc000194ee0, {0xdd7840, 0xc0004d0f90}, 0xc0000b1040, 0xc000356f00, {0xb66f60, 0xc00031c370})
github.com/hashicorp/terraform-plugin-sdk/v2@v2.25.0/helper/schema/resource.go:837 +0xa85
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).ApplyResourceChange(0xc000423ed8, {0xdd7840?, 0xc0004d0e70?}, 0xc00009a410)
github.com/hashicorp/terraform-plugin-sdk/v2@v2.25.0/helper/schema/grpc_provider.go:1021 +0xe8d
github.com/hashicorp/terraform-plugin-go/tfprotov5/tf5server.(*server).ApplyResourceChange(0xc0002d8320, {0xdd7840?, 0xc0004d0450?}, 0xc0001be230)
github.com/hashicorp/terraform-plugin-go@v0.14.3/tfprotov5/tf5server/server.go:818 +0x574
github.com/hashicorp/terraform-plugin-go/tfprotov5/internal/tfplugin5._Provider_ApplyResourceChange_Handler({0xc6bc20?, 0xc0002d8320}, {0xdd7840, 0xc0004d0450}, 0xc0001be070, 0x0)
github.com/hashicorp/terraform-plugin-go@v0.14.3/tfprotov5/internal/tfplugin5/tfplugin5_grpc.pb.go:385 +0x170
google.golang.org/grpc.(*Server).processUnaryRPC(0xc00025a1e0, {0xddb420, 0xc0004824e0}, 0xc0000fa000, 0xc0004317a0, 0x128f7a0, 0x0)
google.golang.org/grpc@v1.53.0/server.go:1336 +0xd23
google.golang.org/grpc.(*Server).handleStream(0xc00025a1e0, {0xddb420, 0xc0004824e0}, 0xc0000fa000, 0x0)
google.golang.org/grpc@v1.53.0/server.go:1704 +0xa2f
google.golang.org/grpc.(*Server).serveStreams.func1.2()
google.golang.org/grpc@v1.53.0/server.go:965 +0x98
created by google.golang.org/grpc.(*Server).serveStreams.func1
google.golang.org/grpc@v1.53.0/server.go:963 +0x28a

main.tf:
terraform {
required_providers {
proxmox = {
source  = "telmate/proxmox"
version = ">=1.0.0"
}
}
required_version = ">= 0.14"
}
provider "proxmox" {
pm_api_url   = " "
pm_user      = " "
pm_api_token_id = " "
pm_api_token_secret = " "
pm_tls_insecure = true
}
resource "proxmox_vm_qemu" "first-tf-vm" {
name       = "second-tf-vm"
target_node = "virt"
clone      = "174-templ"
storage    = "vm_stor"
cores      = 2
memory     = 2048
}

Hi Reckon911, did you ever find a solution for this issue? :-)

@WadDyORedDy , no, I'm newbie in tf, and I don't find any solution for this
Is it my mad? Can you help me?

I don't understand why the plugin doesn't respond and I don't understand how it works under the hood. Usually I just get an error at the terraform plan stage, but here with terraform apply. The VM deployed

@Reckoner911 - I just checked issue 1074 and there is a solution.
Update your provider to use the latest version. You might need to fiddle a little with the proxmox_vm_qemu resource.
I'm still trying some stuff, and I'm stuck in a pxeboot-loop on the VM, but it's created and works with the newest version. Remember to use "terraform init -upgrade" when using a new version :-) I'll keep you updated if I get it to work - right now it seems like my network-block needs some looking into.

@WadDyORedDy
Thanks so much, I'll gonna try do this in while workday

@Reckoner911 - I got it to work.
First of all, I'm using version 3.0.1-rc3.
My main.tf looks like this:
resource "proxmox_vm_qemu" "debian-template" {
    name = "terraform-vm-1"
    desc = "Terraform created VM from debian-template"
    vmid = "UNIQUE ID"
    target_node = "node03"

    agent = 0
    bootdisk = "scsi0"
    clone = "debian-template"
    cores = 1
    sockets = 1
    cpu = "host"
    memory = "2048"

    disks {
      scsi {
        scsi0 {
          disk {
            size = "32G"
            storage = "local-lvm"
          }
        }
      }
    }
}

I'm also using a provider.tf and credentials.auto.tfvars.
I've used issue #977 and #1074 as references. Also a fair bit of searching for specific issues - but now it works :-)
It seems like the disks {} block is important along with bootdisk, or else the VM will go into a PXE-boot loop (no PXE-boot on my side).

@WadDyORedDy
I see that this is still open and encountered this problem today.
I got the same result either in terraform or opentofu :
Terraform v1.9.8 + provider registry.terraform.io/telmate/proxmox v2.9.14
OpenTofu v1.8.4 + provider registry.terraform.io/telmate/proxmox v2.9.14
Trying to use :
proxmox = {
source = "Telmate/proxmox"
version = ">= 3.0.0"
}
gets me :
│ Could not retrieve the list of available versions for provider telmate/proxmox: locked provider registry.terraform.io/telmate/proxmox 2.9.14 does not match

│ configured version constraint >= 3.0.0; must use terraform init -upgrade to allow selection of new versions
For reference, here is my main.tf :
`terraform {
required_providers {
proxmox = {
source = "Telmate/proxmox"
version = ">= 3.0.0"
}
}
}
provider "proxmox" {
pm_api_url = "https://<IP_ADDRESS>:8006/api2/json"
pm_user    = "root@pam"
pm_password = "secret"
pm_tls_insecure = true
}
resource "proxmox_vm_qemu" "rocky9" {
name = "terraform-vm-1"
desc = "tf create from rocky template"
vmid = "1000"
target_node = "pve3"
agent = 0
clone = "test0"
cores = 1
sockets = 1
cpu = "host"
memory = "2048"

disk {
  size = "10G"
  type = "virtio"
  storage = "local-lvm"
}

network {
model  = "virtio"
bridge = "vmbr0"
}
os_type = "cloud-init"
}
`

Ok I downloaded the 3.0.1-rc4 and used it locally.
Seems like the problem will be indeed solved in the next version as I was able to use it without problem.


can you please provide the plugin for 7.13.2 Elasticsearch

can you please provide the plugin for 7.13.2 Elasticsearch

@ezhilrean sorry for delayed response.
I don't know why I have hade notifications turned off 🤔
I have just released versions up to 7.14.0 😉


unable to cut/copy/paste items within or across collections

This feature has been introduced in V#1.0.42


Creation & traversal Linked list in C programming

Thanks for merging but,
Still project is excluded from hacktoberfest 22


Updates for string changes

Coverage remained the same at 82.927% when pulling a208e5a0de60bea660d018920bf2d4bfa31d14b0 on jmm/string_updates into c97753662de7f8dbf2230d8929df0c5930e5e3b3 on master.


Get Calendar items from Exchange 2010 SP3 RU7

Version (e.g. 1.0, dev-master): dev-master
PHP version: 7.0
Microsoft Exchange version: Exchange 2010 SP3 RU7
Description of problem:
I try to connect to the calendar of a user and get all events between 2 dates.
User credential are valid, i connect to the OWA with it.
Thanks for your help.
Example request:
<?php
require_once '../public_html/lib/vendor/autoload.php';

use \jamesiarmes\PhpEws\Client;
use \jamesiarmes\PhpEws\Request\FindItemType;
use \jamesiarmes\PhpEws\ArrayType\NonEmptyArrayOfBaseFolderIdsType;
use \jamesiarmes\PhpEws\Enumeration\DefaultShapeNamesType;
use \jamesiarmes\PhpEws\Enumeration\DistinguishedFolderIdNameType;
use \jamesiarmes\PhpEws\Enumeration\ResponseClassType;
use \jamesiarmes\PhpEws\Type\CalendarViewType;
use \jamesiarmes\PhpEws\Type\DistinguishedFolderIdType;
use \jamesiarmes\PhpEws\Type\ItemResponseShapeType;

class EwsExchange
{
    private $host;
    private $username;
    private $password;
    private $version;
    private $client;

    public function __construct($myhost, $user, $pass)
    {

        $this->host = $myhost;
        $this->username = $user;
        $this->password = $pass;
        $this->version = 'VERSION_2010_SP2';
//        $this->client = new Client($this->host, $this->username, $this->password, $this->version);
    }

    public function connect()
    {
        $this->client = new Client($this->host, $this->username, $this->password, $this->version);
//		print_r($this);
        return $this->client;
    }

	public function CalendarItemsShow($start_date, $end_date)
    {
		$request = new FindItemType();
		$request->ParentFolderIds = new NonEmptyArrayOfBaseFolderIdsType();

		$folder_id = new DistinguishedFolderIdType();
		$folder_id->Id = new DistinguishedFolderIdNameType();
		$folder_id->Id->_ = DistinguishedFolderIdNameType::CALENDAR;
//		print_r($folder_id);
		$request->ParentFolderIds->DistinguishedFolderId[] = $folder_id;

		$request->CalendarView = new CalendarViewType();
		$request->CalendarView->StartDate = $start_date;
		//$request->CalendarView->StartDate = '2016-01-28T12:00:00Z';
		$request->CalendarView->EndDate = $end_date;

		$result = $client->FindItem($request);
		$items = $result->ResponseMessages->FindItemResponseMessage->RootFolder->Items->CalendarItem;

		// If there is only one item, no array is created.
		$items = (is_array($items) ? $items : array($items));

		$item_ids = array();
		foreach ($items as $item) {
			$item_ids[] = $item->ItemId->Id;
		}

		// Use a Client::GetItem operation here to get the full items.

	}
}
?>

Example response:

PHP Fatal error:  Uncaught Error: Call to a member function FindItem() on null in /home/c2adentaire/tools/include/EwsExchange.php:63
Stack trace:
#0 /home/c2adentaire/tools/sync_exchange_v2.php(47): EwsExchange->CalendarItemsFind(Object(DateTime), Object(DateTime))
#1 {main}
thrown in /home/c2adentaire/tools/include/EwsExchange.php on line 63

Additional details:
foreach($users as $user)
{
	if ($user['exchange_login'] && $user['exchange_password'])
	{
		$exchange=new EwsExchange($EXCHG_HOST, $user['exchange_login'], $user['exchange_password']);
		echo $user['nom'].' '.$user['prenom']."\n";
		$cli = $exchange->connect;
//		print_r($cli);
		$exchange->CalendarItemsFind(new DateTime('May 1 00:00:00'), new DateTime('June 1 00:00:00'));
//		$exchange->CalendarItemsShow('2018-05-01T00:00:00Z', '2018-06-01T00:00:00Z');
	}
}

noboby can't help me ?

Nobody to help, find an other way to solve my problem.


no-paths CLI option missing in v3.0.x

At some stage between v3 betas and release, the no-paths CLI option seems to have gone AWOL. Looking through the source there was a bit of reorganisation during the RC cycle, and it seems to not have survived this process (I could not find the specific commit which caused this).
I'm not sure if this was a purposeful omission as the 2.5.3 CLI docs seem to be the most recent, and this still references it, and not finding the exact commit, I could not see if the comment said "removing this because [reason]".

I didn't go away, but formatters settings changed drastically since RC. The way you configure any formatter now is either with --format-settings:
behat --format-settings='{"paths": false}'

or with BEHAT_PARAMS environment variable:
export BEHAT_PARAMS='{"formatters": {"pretty": {"paths": false}}}'

Check https://github.com/Behat/Behat/blob/master/features/format_options.feature for examples

Cool, thanks for the clarification. But from a software stability standpoint, it did "go away" in the sense that the functionality stopped working after upgrading. Different functionality that does the same thing is... different ;-) However I get that this is fine according to semver when bumping full revisions.
Perhaps the issue should actually remain open, as I think there is still possibly a shortfall in the docs, at least as far as transitioning from 2.x to 3.x? I did google a lot, and had a superficial (too superficial as it turns out!) look through the source code to find out if it had just changed, but found nothing so assumed it had been removed. Is there some "upgrading from 2.x to 3.x" doc I didn't find?
Above all else, thanks for the quick heads-up, as it gets me moving forward again. And thanks for putting the effort into Behat! :-)


Created Shortest Common Supersequence

Description
Created Shortest Common Supersequence Solution
Fixes #1274
Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings

@Isha307 add  test case


Custom class name

Allow to override python class name, something like:

#[py::class(MyClass)]
struct test {
}

added following syntax:

#[py::class(name=MyClass)]
struct test {
}


Full IPv6 support for Docker and Docker Compose

Today it is possible to activate IPv6 in Docker. But it has a lot of hassles

It impossible to automate this with docker-compose properly.
Docker still want's to do his thing with ip aliases and NAT/PAT
even when i set a route to the network and bridge, this has to be done after each reboot of the machine

Docker came up in the year 2013 without proper IPv6 support. Even LXC has a better IPv6 handling than docker and is older. As IPv6 handles things different than IPv4, also Docker should handle it different and allow to reach public IPv6 addresses attached to containers directly, configure the underlying system automatically (or just listen to IPv6 ND). With this in mind, the purpose of IPV6 as a fully routable networkaddress can be achieved.
Lastly, Docker Compose should get a flag to assign a static IPv6 automatically to a container. This is useful for public DNS entries and saves a lot of hassles when assigning IPv6 addresses manually.

I can confirm, I have had a huge headache trying to get Docker to publish ports 80 and 443 to ipv4 and ipv6 addresses on the host.
I solved this with: https://github.com/robbertkl/docker-ipv6nat
I am in full support of making this easier in Docker.

I can confirm, I have had a huge headache trying to get Docker to publish ports 80 and 443 to ipv4 and ipv6 addresses on the host.
I solved this with: https://github.com/robbertkl/docker-ipv6nat
I am in full support of making this easier in Docker.

I came across this problem on docker for windows
https://github.com/docker/for-win/issues/10820
I'd suggest that before achieving Full IPv6 support host.docker.internal on docker for windows should be able to connect to IPv6 listerners


New municipalities as of January 2019 need to be updated/added

Since January 2019, 7 new municipalities were created, replacing 15 existing ones. Their territories are simple unions of previously existing municipalities. The details are here : https://overheid.vlaanderen.be/informatie-vlaanderen/gemeentelijke-fusies

Can you make sure the database update gets pushed to https://www.tableaumapping.bi ?

Thanks!

Hi @Korneelmans
The last changes to this repository are from 5 years ago and we lack resources to keep actively maintaining it.
However, as we explained in this README we got the municipalities geojson file from another source. It could be worth checking whether the original publisher has made the changes you are looking for.
If not, please note that the LICENCE file we added to this repository is very permissive. So feel free to use the geojson file we shared and adapt it to your needs.

Hi !
Just chiming in to let you know that there are now great resources available freely on https://www.geo.be and https://data.gov.be/.
This dataset in particular https://www.geo.be/catalog/details/fb1e2993-2020-428c-9188-eb5f75e284b9?l=fr (or equivalently https://data.gov.be/fr/dataset/fb1e2993-2020-428c-9188-eb5f75e284b9) contains administrative boundaries for several levels (as well as other economic sectors boundaries, etc.).


Key stuck on alt+tab from Windows

Windows build number:
22621.2213
Your Distribution version:
20.04
Your WSL versions:
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.2213
Steps to reproduce:

Press key down in Windows app
Alt+tab to switch to WSLG
Release key

Perform steps 2 and 3 before the keyboard repeat kicks in
WSL logs:
pulseaudio.log
stderr.log
weston.log
WSL dumps:
No response
Expected behavior:
Pressing alt+tab to switch from a Windows window to a WSLG window behaves the same as switching between Windows windows
Actual behavior:
Pressing alt+tab to switch from a Windows window to a WSLG window sometimes drops an input from the keyboard, which is noticeable primarily when it's a key up input, because a key gets stuck repeating until I press another key.
This is difficult to reproduce consistently, I think it happens when something in the Windows app is interfering with input, for example it's unresponsive in some way.

This may be the same issue: https://github.com/microsoft/wslg/issues/1029