[FEATURE] Filter genuine email

Description
Security Feature
In your application anyone can enter using temporary or disposable email.
Use Case
It will allow only genuine users only.
It will help to avoid any bot.
Proposed Solution
I will add a feature so that no one could create an account using temporary or disposable email.
Additional Information
Assign me this work under GSSoC24, I will implement it.
Attachments
No response

@pankaj-bind kindly let us know the approach and ETA

I will use an API which is free it will first checks is the email genuine or not, if yes then it proceeds otherwise, breaks operation and shows a popup "invalid email".
It's a part of frontend, it does not affects backend.
It is not like email verification using OTP.
e.g<EMAIL_ADDRESS>(this is a genuine email) and<EMAIL_ADDRESS>(This is a temporary or disposable email). My solution identifies this.
I have tried this, and this feature is very unique.

Okay go for it! pankaj-bind.
Just make sure you follow the guidelines


DB migration fails into mysql

Actual behaviour
I created a new miniflux 1.2.1. and imported my old version 1.1. db.sqlite in the new profile. The new database is a fresh mysql server.
Importing in a new sqlite database is working
Mysql Target:
php scripts/migrate-db.php --sqlite-db=./db.sqlite --admin=1

Create user
Copy user settings
Copy feeds
Copy items
SQLSTATE[HY000]: General error: 1366 Incorrect string value: '\xF0\x9F\x98\x89"/...' for column 'content' at row 1

Sqlite Target:
php scripts/migrate-db.php --sqlite-db=./db.sqlite --admin=1

Create user
Copy user settings
Copy feeds
Copy items
Copy favicons
Copy groups
2

Expected behaviour
Importing should complete without errors in mysql
Steps to reproduce

Create new mysql database
Install Miniflux 1.2.1
3.use the import script to import data
see failure : SQLSTATE[HY000]: General error: 1366 Incorrect string value: '\xF0\x9F\x98\x89"/...' for column 'content' at row 1

Configuration

Miniflux version: 1.2.1
Database type and version: Mysql
PHP version: 5.6
Browser: Firefox, iOS, Safari, Iexplore

I believe this is because mysql's utf8 charset is only 3 bytes, the charset utf8mb4 supports proper 4 bytes. Moving everything to utf8mb4 would cause problems with the index size being greater than 767 bytes for the columns indexed on a VARCHAR(255).
Perhaps a new schema version that changes the character set for the text type columns (url, title, author, content) in the items table would suffice? I believe it would look something like this, haven't actually tested it though. Apologies for the mysql implementation problems @fguillot.
const VERSION = 2;

function version_2(PDO $pdo)
{
    $pdo->exec('ALTER TABLE items CHANGE url url TEXT NOT NULL CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;');
    $pdo->exec('ALTER TABLE items CHANGE title title TEXT NOT NULL CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;');
    $pdo->exec('ALTER TABLE items CHANGE author author TEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;');
    $pdo->exec('ALTER TABLE items CHANGE content content LONGTEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;');
}

Are you planning to integrate this in the code repo or should i fork and test it?

Yes, the schema should use utf8 with 4 bytes. You could test on your side and make a pull-request.

I used your code to alter the database and then I tried a new import..
Same problem as before.. :-(

ssh-aaa@xxx:/www/htdocs/444/feed2$ php scripts/migrate-db.php --sqlite-db=/www/htdocs/444/feed2/db.sqlite --admin=1

Create user
Copy user settings
Copy feeds
Copy items
SQLSTATE[HY000]: General error: 1366 Incorrect string value: '\xF0\x9F\x98\x8D H...' for column 'content' at row 1

Here is the database after the "alter code"

The database connection might need to be in utf8mb4: https://github.com/miniflux/miniflux/blob/master/app/core/database.php#L50

I've put together a PR for this in #628

I tested the PR and it worked fine for the import. Thank you very much!
One additional question: Is there a part of the code, that deletes the items entrys with the status "removed" from time to time? My database has about 10.000 items which are already removed but still in the database.

Will close this when the PR is approved

@Fake4d items marked as "removed" are deleted when they are not in the XML feed anymore.
Closing this issue, thanks for the contribution!


Update Code Snippet header icon

Replaces the Code Snippet header  text (</>) with the actual Code Snippet icon.
Fixes #683
Before:

After:

Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

Just looking at your screenshot it seems like the icon is the wrong color in dark mode. It looks white instead of the off white/grey that the text next to it is (shouldn't it match the color the icon is in the side bar?). I'll check it out and try it myself in the morning

Just looking at your screenshot it seems like the icon is the wrong color in dark mode. It looks white instead of the off white/grey that the text next to it is (shouldn't it match the color the icon is in the side bar?). I'll check it out and try it myself in the morning

good catch. it's been updated. thanks


CB-13704 Use Preconditions with message in Authz module and Crn, CrnI…

…nternalBuilder classes
See detailed description in the commit message.

I used global find + replace, so other modules can be affected too this change.


Add gettxhistory RPC method

What current issue(s) does this address, or what feature is it adding?
Adds gettxhistory RPC method which returns a list of every tx in the associated wallet in JSON format, including block_index and blocktime
This PR helps address issue #189
How did you solve this problem?
Trial and Error.
How did you make sure your solution works?
Unittest
Are there any special changes in the code that we should be aware of?
No
Please check the following, if applicable:

[x] Did you add any tests?
[x] Did you run make lint?
[x] Did you run make test?
[x] Are you making a PR to a feature branch or development rather than master?
[x] Did you add an entry to CHANGELOG.rst? (if not, please do)

Coverage increased (+0.03%) to 80.263% when pulling 54dd30c1d04d9ee0185f32473f74906f2f426f63 on jseagrave21:gettxhistory into cfc83611648a1edac152e8580fac0e10fa382503 on CityOfZion:development.

I added block_index and blocktime to this method to help a user sort and filter the results. I am thinking about sorting through transactions when filing taxes. I think this method will be very helpful. Please let me know if you have any thoughts or recommendations. cc @localhuman @ixje

I would prefer that any non standard RPC methods ( methods not implemented in neo-cli RPC ) to not be in the core RPC implementation.  Could you make an extended version of JsonRpcApi with this additional method ( along with #598 and #573 ).  We could then add a switch in np-api-server to optionally start the extended JsonRpcApi.


feat: add support for HTML, Markdown and Typst files

Continuing #117, as per our discussion.
This PR adds parsers for HTML, Markdown and Typst files, which are used in the CLI to support different file types. Auto detection per file is used by default, which will just choose a parser based on the file's extension.
I think the parsers are working OK, but wanted to open this PR as soon as possible so you can let me know what you think, and to see if you have some files that maybe this doesn't work great for.
I decided to take the same path that pyLanguagetool took for Markdown files, by first converting them to HTML, and then using a separate library for parsing that (html_parser in our case). I figured we'd probably want support for HTML eventually anyway, but you can let me know if you think I should take a similar approach to the HTML and Typst parsers.
As for the HTML and Typst parsers, I've inserted some "placeholders" in place of e.g. code blocks, links etc., which LanguageTool ignores, e.g. _code_, _math_, _link_. This seems to work well enough but if you have any other ideas on how to tackle these let me know and I can have a look.

Any idea what's going on with the tests? cargo nextest run --all-features --no-capture doesn't produce any failures for me locally

Hi @Rolv-Apneseth, thanks for your PR!
See my comments and let me know what you think :-)

Hey @jeertmans, I'll get back to this in a couple days, thanks for the review though

Hi @Rolv-Apneseth, thanks for your PR!
See my comments and let me know what you think :-)

Hey @jeertmans, I'll get back to this in a couple days, thanks for the review though

No issue, Merry Christmas and happy end of year!

No issue, Merry Christmas and happy end of year!

Thanks, you too :)

Any idea what's going on with the tests? cargo nextest run --all-features --no-capture doesn't produce any failures for me locally

Looks strange! Sometimes, the online version of the LT API returns different results than the one you can host locally. Did you run tests on a self-hosted API?

Looks strange! Sometimes, the online version of the LT API returns different results than the one you can host locally. Did you run tests on a self-hosted API?

Yes, it was with a self-hosted API. Looks like these errors are on the current v3 branch too though (#117), so I don't think these changes are related.


Remove PrismJS

Remove the dependency of PrismJS.
Just use the built-in code highlighting of Hugo.

It's not as easy as I thought.
If syntax highlighting is embed into the code block contents, there is no straight forward ways to copy code blocks.
PrismJS renders highlighting on the fly when page is rendered in the browser.
The code block contents are intact.
Hugo renders syntax highlighting when generating HTML files. All syntax hints are already embed into HTML classes or inline CSS. No plain text codes are available after rendering. It makes copy plain text contents of the code blocks harder to implement.

There is a reference implementation here.
https://github.com/CaiJimmy/hugo-theme-stack
Run a JavaScript function to extract the plain text content of highlight code block and put it into clipboard when copy button is pressed.
It still needs some JavaScript codes but seems to be much less.


DAO Market & Regulator lesson

Write ClosedMarketRegulator contract as regulator with reject default lot policy
Write EtherMarketAgent contract with auto ether->token->ether conversion
Write missed builders

Update behaviour in https://github.com/airalab/core/commit/f7340ea589a5c40492c2977d05ee80d5d8acb966

https://github.com/airalab/learning-center/commit/8b8827decd701bc2ef774232980cb262f5127204


Unable to run the PRO version.

I've purchased the pro version. I placed this in my app.module.ts file:
import { TooltipModule } from './components/tooltip/tooltip.module';
@NgModule({
imports: [
TooltipModule
],
But when I run the app I get this error:
ERROR in ./src/app/components/tooltip/tooltip.component.sass
Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
SassError: Invalid CSS after "...(27,31,35,.15);": expected 1 selector or at-rule, was "host: {"
on line 12 of C:\Users\xxx\xxx\xxx\xxx\xxx\src\app\components\tooltip\tooltip.component.sass

ip-light-border-color: rgba(27,31,35,.15);

@noxiousmobile Hey. Try to download the version for Angular 7 from the same link.


use agent and remove unused pool variable

Problem
The documentation describes the use of a POOL variable in the library to use your hosted agent. This POOL variable is actually never used and the vmimage is set hard for the pipeline.

Solution
Replaced the hard reference with the $(Agent) that is being used by other parts of the code and is defined in your second library
Tests
Run the 02 pipeline
Notes
Should also be removed from the documentation cause it is doing nothing documentaion

Hi @ErickSegaar
The POOL parameter is used for the automatic configuration of the deployer to automatically register the deployer as an agent.
https://github.com/Azure/sap-automation/blob/dcd55edef8754a893e12c2f839ca5c3798415da0/deploy/terraform/terraform-units/modules/sap_deployer/templates/configure_deployer.sh.tmpl#L484
I can make that more visible in the documentation.
//Kimmo

Ok, missed that one when I searched for it. Shall I update the PR with the POOL environment variable back in it. But remain the $(agent) for the running of the pipeline?

Yes please
//Kimmo
From: Erick Segaar @.>
Sent: Wednesday, June 8, 2022 1:27 PM
To: Azure/sap-automation @.>
Cc: Kimmo Forss @.>; Assign @.>
Subject: Re: [Azure/sap-automation] use agent and remove unused pool variable (PR #175)
Ok, missed that one when I searched for it. Shall I update the PR with the POOL environment variable back in it. But remain the $(agent) for the running of the pipeline?
—
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fsap-automation%2Fpull%2F175%23issuecomment-1149739541&data=05|01|kimmo.forss%40microsoft.com|f2981c3d64634a8556e208da49396ad2|72f988bf86f141af91ab2d7cd011db47|1|0|637902808223594952|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Ckja0CyBNIVoqBoai87FLNToRPvoGkrRS8U3SsuNtLE%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGCOMTHTQ5IFH5R3332QEIDVOBYPDANCNFSM5YF6U56Q&data=05|01|kimmo.forss%40microsoft.com|f2981c3d64634a8556e208da49396ad2|72f988bf86f141af91ab2d7cd011db47|1|0|637902808223594952|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=dWG98pkpHlpsEyPzoLyMSxofy9Tq8Og7Dy%2BaKmNToa8%3D&reserved=0.
You are receiving this because you were assigned.Message ID<EMAIL_ADDRESS>

Ok cleaned it up


Max simultaneous connections flag for server

This is my proposed solution for #709
Allow optional flag to limit the number of clients that can connect at one time.

This change is

Hi @nphyatt thanks for the PR! We're currently refactoring a lot of the cli and tests on another branch, so this will likely need to change before we can merge it. Hang tight :)

@deontologician just updated this PR and merged in the latest next branch. Tests all seem to pass. Any thoughts on whether or night this PR can be merged?

Looks good to me, merging.
I'll also merge this into the plugins branch now, but it'll be pretty much completely rewritten.
Thanks for the help, @nphyatt!


Added support for custom user data in

Added support for custom user data in mdns_discovery_recv and mdns_query_recv callbacks.

This is a feature implementation for https://github.com/rampantpixels/mdns/issues/5

Looks good, thank you!


“PHP Toolbox” extension

Description
This is a collection of commands to help PHP developers. The initial version includes two commands:

A unix timestamp helper for converting timestamps to formatted dates and quickly copying common timestamps
A php date format helper to search, build, and save date format strings

Screencast
PHP Date Format Helper
https://github.com/raycast/extensions/assets/21592/6c6f1dc7-a216-486d-94d7-f0fdf8c6f4f7
Unix Timestamp Helper
https://github.com/raycast/extensions/assets/21592/98620c2e-0345-482b-b1f7-3ab736ed961c
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Something like this?
https://github.com/raycast/extensions/assets/21592/96b7749a-2b5f-4d70-8c3a-2855d777c562


pan, tilt and zoom movement

I installed the module on Saturday for a job and it worked first time. Is there a way to change the movement controls so they work on a hold down principle or even a toggle I am used to using Pan,Tilt and Zoom controls where they only operate if you hold down the button and this module moves the camera until you press a seperate stop button. Also is there a way to have a Speed Up and Down button I noticed you can set the speed but is there a way to put in a speed up and down?
Great work thanks.

Could you put the movement command in the Key Down section of a button and the stop command in the Key Up section?

I believe this functionality has been in place for a while but this issue never was closed. I'm closing it now.


feat(InputMenu/SelectMenu): allow create-item prop

🔗 Linked issue

#1289
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[x] 👌 Enhancement (improving an existing functionality)
[x] ✨ New feature (a non-breaking change that adds functionality)
[x] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Re-adds creatable to SelectMenu (maybe this should also exist in InputMenu too).
Let me know if this was intentionally left out (@benjamincanac)
📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

/cc @sandros94

I first left it out because I thought to let the users define it using the items prop for more flexibility but now that I think of it the filtered results are not exposed.

I just tried the docs examples for both InputMenu and SelectMenu, when clicking the Add ... I get this warning:
[Vue warn]: Invalid prop: type check failed for prop "modelValue". Expected String | Number, got Boolean with value true.

I just tried the docs examples for both InputMenu and SelectMenu, when clicking the Add ... I get this warning:
[Vue warn]: Invalid prop: type check failed for prop "modelValue". Expected String | Number, got Boolean with value true.

Thanks for pointing out - sorry I wasn't 100% sure of how to use the component-code prose for the docs. It should be fine now!

What is the intent behind the create event? To add to the initial array?
There is an error inside, it's typed with the value but receives the event (from the @select on the ComboboxItem). Maybe we should have the event and the value?

What is the intent behind the create event? To add to the initial array?

Yes, I think its an explicit event for any developer to know when the create has happened.

There is an error inside, it's typed with the value but receives the event (from the @select on the ComboboxItem). Maybe we should have the event and the value?

Hmm, I suppose the better type for it is V extends string ? Record<V | '[label] (should be keyof T)', string> : string

No I meant, the first parameter you receive when using @create is an Event not the item value.

No I meant, the first parameter you receive when using @create is an Event not the item value.

Oh! My bad. I think that will also contain the target value as string too!

@ineshbose For the docs, don't you think it would be better in the examples section? We could demonstrate a real example with @create event.

@ineshbose For the docs, don't you think it would be better in the examples section? We could demonstrate a real example with @create event.

Does that replace the currently added section or in addition to that? Quite indecisive when writing docs myself, so if you've got ideas - fire away! 😄

Sure, I'll take care of it 😊

Before I start the docs, how are we supposed to get the created item from the @create event? 🤔

Before I start the docs, how are we supposed to get the created item from the @create event? 🤔

it would be similar to onSelect! Value should be e.target.value

Thanks @ineshbose!


assertJsonMatches may be too strict

Hi,
I am still using this lib to recreate my functional tests. I used to use self::assertSame($expectedErrors, $apiErrors) to test if my form errors are the one I expect (I test on api endpoint, not on the symfony type)
When migrating I use the assertJsonMatches('errors', $expectedErrors) method on the browser.
I have a difference between the two assertion methods. The first one (based on phpunit) did not take order in account. The second method (based on zendstruck/assert lib) did it. Which is a bit annoying as I don't care of order of my errors, I only need to know if they are all present.
Is it something I am the only one with this need? Maybe we could change this behavior to have the same as the phpunit's assertSame method?
What do you think?

PHPUnit's assertSame doesn't take array order into account?

Just double checked it again...
It does. And my legacy code uses assertEquals... So I confused and probably didn't check well the first time :roll_eyes:
Closing.

I do think there could be some improvements here. What you describe sounds like a common use case.
Possibly related' https://github.com/zenstruck/browser/issues/35

Yes it might be easier indeed. But not that important to me.
Thanks.


Tone.Players onload callback doesn't fire when there's more than one player

Describe the bug
Players.onload callback doesn't seem to be invoked if the Players object is constructed with more than one audio file / buffer.
To Reproduce
The code snippet below is taken from Players.test.ts.
I imagine that if you added a second item to the url audio buffer map and ran the test, that the onload callback would not fire & the test would fail.
		it("can pass in additional args in the second parameters", (done) => {
			const players = new Players({
				test: "./audio/sine.wav",
			}, {
				onload: () => {
					expect(players.player("test").buffer.loaded).to.be.true;
					expect(players.volume.value).to.be.closeTo(-12, 0.1);
					players.dispose();
					done();
				},
				volume: -12,
			});
		});

Expected behavior
I expected the onload callback to be fired when both/all buffers have been loaded.
What I've tried
With just one item in the map, I verified that the onload callback fires. With more than one, it doesn't seem to work. In my personal code, I even replaced the audio file of the second player to be the same audio file as the first player, and the onload callback never fired.
  const audioSamples = new Tone.Players({
    sampleA: "assets/some_valid_url.m4a",
    sampleB: "assets/some_valid_url.m4a", // `onload` never called even if I use the same file!
  }, {
    onload: () => {
     // this line never seems to fire.
      console.log('loaded audio');
    },
    onerror: (e) => {
      console.log('players error ', e);
    },
  });

Update:
This could be an issue with ToneAudioBuffers-- I don't see any test that confirms that onload is called when multiple urls are provided. (https://github.com/Tonejs/Tone.js/blob/master/Tone/core/context/ToneAudioBuffers.test.ts)
In the meantime, I'm going to await Tone.ToneAudioBuffers.loaded() since that seems pretty close to what I need right now.

I want to work on this issue , please assign it to me.


Update the template README with the install instructions for nuget.org

dotnet new -i Microsoft.PowerShell.Standard.Module.Template

to install the template from nuget.org
Then you can use it as described in the readme.

@JamesWTruher + @SteveL-MSFT small README change when you get a chance.


fix(docs): incorrect formatting trigger example

I noticed that the current docs have a malformed second example for Triggers.
This properly tags the code block as HCL which fixes the issue. You can test yourself by copying and pasting the full file into the HashiCorp Doc Preview Tool

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 75.96%. Comparing base (c429944) to head (41dfc24).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #566      +/-   ##
==========================================
- Coverage   76.05%   75.96%   -0.09%
==========================================
  Files          86       86
  Lines        7107     7107
==========================================
- Hits         5405     5399       -6
- Misses       1368     1374       +6
  Partials      334      334

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Reminder about OpenFL install?

There's link to the relevant web page (on the web site) but maybe there should be a link in the README on the project page as well?
I fiddled around for a bit before I remembered to run haxelib run openfl setup.
It's a little thing, but there's a good chance beginners will forget this.

Good call! I've added placeholder openfl setup instructions to the website. I'll update the live site with the next library update, which should hopefully be today:
https://github.com/TerryCavanagh/haxegon.com/commit/a78924b1ff265a74e0ae6e58d40cd8a697706d9c


Smart Card Driver and Static Driver Verifier (SDV)

What results should be expected when running Static Driver Verifier (SDV) against the Smart Card Sample Driver (SmartCrd.sln)?
I am working with Visual Studio 2017 and the Windows 10 WDK.  Both this sample driver and my current proprietary smart card driver pass the Microsoft Code Analysis (VS2017) tests without errors or warnings.  To avoid the test timeout result I have attempted configuring the test to use a single processor thread and maximum time and memory settings.
I have reproduced the Main UI Page from SDV below:

(1) Should I expect that no Driver Entry Points were found?  Why is this?
(2) What is the root cause for the Timeout result?  Can other configuration options be made to prevent the timeout?
I am seeing similar results in my proprietary Smart Card Driver; i.e., No Entry Points Identified and all test rule sets time out.
Thank you.

so what the solution?


TST: fix incorrect signal.sosfilt tests

This caused failures on macOS arm64 with NumPy main, because clongdouble arrays started to be passed to np.linalg.eigvals.
This code, as the deleted comment in cast_sos2tf said, does not actually work with long double dtypes, nor with object. So trying to cast to complex128, call the functionality, then cast back, doesn't really make sense as a test. Hence simply delete the unsupported dtypes from the tests.
This fixes the macOS failures in the wheel build (xref gh-19605).

On windows they are the same, on *nix they are not unfortunately.

They're not the same - they have the same memory layout, but they are still distinct dtypes. Behavior is going to still differ, that was the initial problem with these tests - numpy.linalg simply does not support long doubles, but we tried to sneak them in; now NumPy's validation seems to have improved a bit and things fail.

Ah I was replying to Tyler but didn't see your comment coming in, sorry about that.

No worries! I'm sharing your pain by the way @ilayn, working on the Windows wheel builds by trying to build everything from source against NumPy main ... not enjoying it much so far:)

I'll carry my views on reprs being the same but the data underneath not being the same over to the NumPy PR then. g prints as float64 on the problem platform.

Sounds good. We should also clean up use of these one-character typecodes throughout SciPy at some point, they're too annoying (as this issue shows).


argo: 2.2.1 -> 2.4.0

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

@GrahamcOfBorg build argo

@GrahamcOfBorg build argo

you need to be whitelisted for ofborg to run your commands :)

@GrahamcOfBorg build argo


nimble/sm: Use privacy device mode as default

In order to not brake existing applications lets use privacy
device mode instead of network mode which is default in the
Controller accorting to BT 5 specification.

test please


Adjusted log level

Adjusted log level for packages in FINISHED state.

This now has conflicts after #131. But this PR did not resolve the given issue, which was fixed in #129, so this PR is no longer needed.


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


AWS Explorer shows error loading credentials file when contents changed externally

Expected Behavior
When credentials file is changed externally, contents should be re-read and used appropriately without any dialog.
Current Behavior
Also described in #806
When running Visual Studio with the AWS Explorer extension, anytime the credentials file is changed externally an error message pops up:

"Error loading AWS profiles: The process cannot access the file  because it is being used by another process."
This does not appear to affect functionality (although if the profile secret changed the profile is reset to none).  The file is successfully used.
This error message can sometimes be hidden and leave the VS UI in a partially usable state resulting in much confusion.
Possible Solution
Change the way this error is handled, retry, open file with different file access, etc.  If this code is available publicly I would be happy to examine and modify.  I'm unable to find it.
Steps to Reproduce (for bugs)

Open Visual Studio 2017 with AWS Toolkit installed.
Modify the credentials file externally, simply opening in VSCode and pressing save is enough.
Note the error message that appears in all instances of Visual Studio.

Context
At my organization we use a tool that keeps the credentials file fresh with tokens retrieved from a secret manager.  This message pops up every hour as these tokens are refreshed and serves as a lovely annoyance.
In my particular case, I actually own the code that is modifying the file and have attempted all means possible of sharing it.  I'm currently opening and writing the file like this:
using (FileStream fileStream = new FileStream(awsPath + "/credentials", FileMode.OpenOrCreate, FileAccess.Write, FileShare.ReadWrite | FileShare.Delete))
using (StreamWriter writer = new StreamWriter(fileStream))
{
    //...
    await writer.WriteLineAsync(stuff);
}

Your Environment

Operating System and version: Win 7
Visual Studio version: 2017 - 15.9.9
AWS Toolkit for VS 2017 <IP_ADDRESS>

For now I have decompiled the plugin and simply removed the error message popup.  This solves my immediate frustration but is neither a long term nor an elegant fix.
The fact that the plugin does in fact read the correct profile information but still display the error makes me think:

the error is caused by an unintentional attempt to write back to the file
the filewatcher is triggered both when the external program opens and closes the file - whereby the plugin succeeds the second time

+1

We have a tweak to the toolkit's behavior on this going on in the next release.

+10 If that tweaked behavior sees the profile's token changed, leaves it selected, and updates any instances of it being used (open windows).  Currently when the secret is expires, all open windows stop working - even though the token was updated in the credentials file.
Regardless, thanks for the prompt response on this @normj !

The fix we have queued up for the next release will address the file locking issue which the file is being written to by an outside process. It won't address new credentials be written for an existing profile which as you saw leads to windows open in the toolkit with expired credentials.
Out of curiosity can I hear more about your workflow for having the credentials file be updated? The reason I ask is the latest version of the AWS SDK for .NET added support for profiles that our using a credential process to feed the credentials into the calling process. I'm trying to get a credential file lock issue fix out soon so we won't have time to get the toolkit updated to the latest SDK but I'm to get it updated soon. Once it does if you switched your workflow to be a credential process provider that would solve the expired credentials issue. Here is more information about credential process provider. https://github.com/awslabs/awsprocesscreds

I pushed out version <IP_ADDRESS> that has changes to reduce the contention reading the credentials file. I would appreciate hearing feedback on the changes.

This is great stuff @normj.  Looking forward to upgrading the machine at the office to see if that fixes.  Currently running a recompiled version to just hide the dialog, but I'll try and get desktop services to upgrade me to the latest this week.  Security is tight where I work so it takes some time to get an admin login for the install.
In the meantime I'll investigate this credential process provider.  That looks perfect for integrating our workflow.
We use Vault for secret storage and the AWS secrets engine to retrieve STS Tokens which have a ttl of 60 mins.  I have a background process that waits for expiry, then updates the credentials file with the latest token.  It's nearly identical in functionality to using consul-template to update files with credentials from Vault.
I could potentially make a lightweight executable to provide credentials; serving as a credential process provider.  I wasn't aware of that approach.  I would have to rethink the Vault authentication, but definitely doable.
Thanks for the quick response.  I'll get you feedback on this issue ASAP, and ping you on another channel if I come up with a decent Vault integration strategy that might be able to serve a larger audience via the labs awsprocesscreds repo.


Problem running basic intro script

Hi, if I run this

I'm getting the following problem

Any idea what's wrong? Everything is installed ok

Seems like return_tensors=True at line 47 in generator_helpers.py might be the issue.
https://colab.research.google.com/drive/1_TWgvLe2QimCYTR2BoxpzB4iWV-QQViG?usp=sharing
(To reproduce, execute once to crash, from error logs follow the path to generator_helpers.py and comment out line return_tensors=True argument. Save the change and restart the notebook to run again.)
@tongshuangwu , hope this should work fine for now!

Thank you both! Unfortunately I couldn't really reproduce the error; When I ran the code it doesn't really crash.
Could you please let me know what's your environment? Seems to run well on my ubuntu machine, with transformers==4.5.1 or 4.8.2?

Yes, you are right, seems to be an issue with transformers version. Latest version 4.12.5 causes the error.

Ah, gotcha. I merged your pull request, so hopefully now it works!


Env var suggested in link output does not match with the actual env var inside the component pod

/kind bug

What versions of software are you using?
Operating System:
Supported
Output of odo version:
master
How did you run odo exactly?
$ odo create nodejs frontend --context tests/examples/source/nodejs/ --project test123
$ odo url create --port 8080 --context tests/examples/source/nodejs/
$ odo push --context tests/examples/source/nodejs/

$ odo create python backend --context tests/examples/source/python/ --project test123
$ odo url create --context tests/examples/source/python/
$ odo push --context tests/examples/source/python/

$ odo link backend --component frontend --project test123 --context tests/examples/source/python/
 ✓  Component backend has been successfully linked to the component frontend
The below secret environment variables were added to the 'frontend' component:
· COMPONENT_BACKEND_HOST
· COMPONENT_BACKEND_PORT
You can now access the environment variables from within the component pod, for example:
$COMPONENT_BACKEND_HOST is now available as a variable within component frontend

$ oc get pods -n test123
NAME                    READY   STATUS      RESTARTS   AGE
backend-app-1-9pp4k     1/1     Running     0          13m
backend-app-1-deploy    0/1     Completed   0          13m
frontend-app-1-deploy   0/1     Completed   0          17m
frontend-app-2-bfqsk    1/1     Running     0          8m17s
frontend-app-2-deploy   0/1     Completed   0          8m34s

$ oc exec frontend-app-2-bfqsk -n test123 -- echo $COMPONENT_BACKEND_HOST

$ oc exec frontend-app-2-bfqsk -n test123 -- echo $COMPONENT_BACKEND_PORT

$

$ oc exec frontend-app-2-bfqsk -n test123 -- env
PATH=/opt/app-root/src/node_modules/.bin/:/opt/app-root/src/.npm-global/bin/:/opt/app-root/src/bin:/opt/app-root/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
TERM=xterm
HOSTNAME=frontend-app-2-bfqsk
DEBUG_PORT=5858
ODO_S2I_SRC_BIN_PATH=/tmp
[...]
COMPONENT_BACKEND_HOST=backend-app
COMPONENT_BACKEND_PORT=8080
[...]
FRONTEND_APP_PORT=tcp://<IP_ADDRESS>:8080
BACKEND_APP_SERVICE_PORT_8080_TCP=8080
BACKEND_APP_PORT_8080_TCP_ADDR=<IP_ADDRESS>
[...]
FRONTEND_APP_SERVICE_PORT_8080_TCP=8080
BACKEND_APP_SERVICE_PORT=8080
BACKEND_APP_PORT=tcp://<IP_ADDRESS>:8080
[...]
FRONTEND_APP_SERVICE_PORT=8080
FRONTEND_APP_PORT_8080_TCP=tcp://<IP_ADDRESS>:8080
FRONTEND_APP_PORT_8080_TCP_PROTO=tcp
FRONTEND_APP_PORT_8080_TCP_ADDR=<IP_ADDRESS>
BACKEND_APP_SERVICE_HOST=<IP_ADDRESS>
BACKEND_APP_PORT_8080_TCP_PROTO=tcp
KUBERNETES_SERVICE_PORT=443
BACKEND_APP_PORT_8080_TCP_PORT=8080
FRONTEND_APP_PORT_8080_TCP_PORT=8080
BACKEND_APP_PORT_8080_TCP=tcp://<IP_ADDRESS>:8080
FRONTEND_APP_SERVICE_HOST=<IP_ADDRESS>
container=oci
[...]

Actual behavior
No such env var
Expected behavior
$ odo link backend --component frontend --project test123 --context tests/examples/source/python/
 ✓  Component backend has been successfully linked to the component frontend
The below secret environment variables were added to the 'frontend' component:
· BACKEND_APP_SERVICE_HOST
· BACKEND_APP_SERVICE_PORT
You can now access the environment variables from within the component pod, for example:
$BACKEND_APP_SERVICE_HOST is now available as a variable within component frontend

Any logs, error output, etc?
$ cat tests/examples/source/nodejs/.odo/config.yaml kind: LocalConfig
apiversion: odo.openshift.io/v1alpha1
ComponentSettings:
  Type: nodejs
  SourceLocation: ./
  SourceType: local
  Ports:
  - 8080/TCP
  Application: app
  Project: test123
  Name: frontend
  Url:
  - Name: frontend-8080
    Port: 8080

$ cat tests/examples/source/python/.odo/config.yaml
kind: LocalConfig
apiversion: odo.openshift.io/v1alpha1
ComponentSettings:
  Type: python
  SourceLocation: ./
  SourceType: local
  Ports:
  - 8080/TCP
  Application: app
  Project: test123
  Name: backend
  Url:
  - Name: backend-8080
    Port: 8080

Ahh, got it.
The suggested link output variable are being populated in the component pod.


Grow out of zero-ver?

The title says it all... Should this project grow out of ZeroVer?

Partly related, would it make sense to move this to PyPA? I first built this partly to prove a point ("come on this is so easy please stop bothering pip maintainers") and never planned to do very much about it.


Permissions error when checking Go-lang directory

TASK [fubarhouse.golang : Go-Lang | Ensure directory is writable] *******************************************************************************************************************
fatal: [$USER]: FAILED! => {"changed": false, "msg": "There was an issue creating /usr/local/go as requested: [Errno 13] Permission denied: '/usr/local/go'", "path": "/usr/local/go"}
Do I need to add become=True to the role specifically? or is there another work around?  Is this the proper location for the installation on a Mac?

It's actually a good point - I can't recall if brew is currently supported but I feel it should be added.
The question has come up a couple of times lately (short answer is yes)... I'll put it on my list of things to tackle as I'm trying to give this one and rust some attention lately.
https://github.com/fubarhouse/ansible-role-golang/issues/156#issuecomment-929650177


SES time zone

Support decoding time zones in the following format Fri, 26 Jun 2020 03:04:03 -0500 (CDT)
Motivation:
Currently if an email is received with the common header date which includes the timezone in alphabetical form in brackets after the numeric timezone the date does not decode, and SES.Event does not decode.
Modifications:
Code changes include cropping text after any open bracket found in the date string before passing it through the dateFormatter. I don't know of a dataFormat string that will support the above format. If there is one obviously it would be better to use that instead.
Result:
SES.Event decodes even when it holds a date in the above format

orthogonal to these changes but we should add a link to SES event from https://github.com/swift-server/swift-aws-lambda-runtime#integration-with-aws-platform-events

Added the link in

thanks @adam-fowler


Update swf path config to use the right config key

Coverage remained the same when pulling 50da686239be900e6452222690b845204b30d9f6 on egdelwonk:patch-1 into f0263698a4123376bb46bbd814fd968f48b9def1 on zeroclipboard:master.


keywords - adding a comma after a word raises an error

commas are used to separate keywords, however, if the user adds a comma accidentally after a word and nothing more, they get an error. The comma should be deleted instead.

Fixed..


Node Sass does not yet support your current environment

This is mostly a copy of the #1764 and npm rebuild node-sass actually helps.
But
the issue here is that I need to search for how-to-fix that error. It should, at least, show message try to run 'npm rebuild node-sass', or better ask user is he wants to do rebuild and rebuild by button click or answer yes in the console.
Currently the issue #1764 is not fixed. It is like "hey, we have workaround here, search by yourself".
P.S. in my case it just started to show the message after node and npm update. So the message "does not yet supported" is wrong in the root.

It literally tells what command to run in the console output. I don't know
what else you could expect.
On Thu., 26 Apr. 2018, 8:12 pm Anton Konovalov<EMAIL_ADDRESS>wrote:

This is mostly a copy of the #1764
https://github.com/sass/node-sass/issues/1764 and npm rebuild node-sass
actually helps.
But the issue here is that I need to search for how-to-fix that error. It
should, at least, show message try to run 'npm rebuild node-sass', or
better ask user is he wants to do rebuild and rebuild by button click or
answer yes in the console.
Currently the issue #1764 https://github.com/sass/node-sass/issues/1764 is
not fixed. It is like "hey, we have workaround here, search by yourself".
P.S. in my case it just started to show the message after node update. So
the message 'does not yet supported' is wrong in the root.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2351, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWNRdwKrZIrOB8PjO_fH9R5Rp7aEiks5tsZ2FgaJpZM4Tk5QS
.

Absolutely any time you update a major version of Node you should reinstall
your node_modules.
On Thu., 26 Apr. 2018, 8:51 pm Michael Mifsud<EMAIL_ADDRESS>wrote:

It literally tells what command to run in the console output. I don't know
what else you could expect.
On Thu., 26 Apr. 2018, 8:12 pm Anton Konovalov<EMAIL_ADDRESS>wrote:

This is mostly a copy of the #1764
https://github.com/sass/node-sass/issues/1764 and npm rebuild node-sass
actually helps.
But the issue here is that I need to search for how-to-fix that error. It
should, at least, show message try to run 'npm rebuild node-sass', or
better ask user is he wants to do rebuild and rebuild by button click or
answer yes in the console.
Currently the issue #1764 https://github.com/sass/node-sass/issues/1764 is
not fixed. It is like "hey, we have workaround here, search by
yourself".
P.S. in my case it just started to show the message after node update. So
the message 'does not yet supported' is wrong in the root.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2351, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWNRdwKrZIrOB8PjO_fH9R5Rp7aEiks5tsZ2FgaJpZM4Tk5QS
.

It literally tells what command to run in the console output. I don't know
what else you could expect.

It doesn't. Or if it does - it hard to find.
It shows link to node-sass releases to understand which envs node-sass supports.

Absolutely any time you update a major version of Node you should reinstall
your node_modules.

Usually people doesn't update node that often to know what should be done each update.
And the error which node-sass shows is just incorrect and doesn't trying to help to solve it.

I'd say that the error message is correct in case  it shown something like this "current node-sass package was built for node lower version and can't be run in this version. You need to do rebuild with command npm rebuild node-sass". That's a correct error handler with correct advice how to solve problem.

There are a couple different conditions here.

user has an older version of node-sass, and updates to a new (unsupoprted) version of Node

This is your case.

Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (64)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.8.3

We tell to user that they're now on a version of Node that isn't supported. Their only option is to use a version of Node that is supported. They're given a link to see what version are supported.

use has a new version on node-sass, and updates to a new (supported) version of Node

Error: Missing binding /Users/xzyfer/Projects/Sass/node-sass/vendor/darwin-x64-64/binding.node
Node Sass could not find a binding for your current environment: OS X 64-bit with Node.js 10.x
Found bindings for the following environments:

OS X 64-bit with Node.js 9.x

This usually happens because your environment has changed since running npm install.
Run npm rebuild node-sass --force to build the binding for your current environment.

Here they are told that they're using different version of Node than when they ran npm install. They can fix their issue by running a command.
Note: the command show is wrong. I will fix this. I should be npm rebuild node-sass

In the first case, we can't tell the user to just run npm rebuild node-sass. Doing a rebuild on an unsupported Node version will

attempt to download a binary that cannot exist, then
fallback to doing a local compilation

Local compilations suck, are slow, and quite possibly will not work between major version updates because the V8 APIs change.
The users only option is to use a supported version, or update node-sass itself.

Now if you think there is a way to more clearly communicate those issue then we're open to suggestions. But please don't over simplify the problem. There are no easy answers here.

So, the Node 10 is unsupported (I have scrolled to the very bottom on the releases page) and it have shown to me the first variant. But the rebuild have fixed the issue. Why if it is unsupported? Was it a fallback to doing a local compilation which worked despite of quite possibly will not work between major version updates?
As of the first variant of the message - Unsupported environment with OS X 64-bit for me is like "Oh, your Mac OS does not yet supported". And I like "Wtf, it worked before, environment the same". So by environment or Unsupported runtime (64) (is this about node?) it probably should show more human-readable variant. So, technically I know, that the problem was in that I've updated Node, but in this certain message I do not understand this.
Moreover, the link to releases with list of releases and some barely readable names does not help either. But the list at the very bottom helps.
The thing here is that you know that there is a Supported Environments section at the bottom. But users who seeing this page first time - doesn't. They scroll list a bit, sees list of files, understands that it is release page (I quite familiar with github) and closes the page.

Unsupported runtime (64)

Every version of Node has a "module version". This is the 64 we show in error above. This number relates to the Node ABI. When the number changes we need to re-build a new binary for the binary to be compatible with Node.
We maintain a mapping of these version numbers to human readable Node version names. We even call the function getHumanNodeVersion. There here is that we cannot know what that number will be until a new version Node is released.

Local compilations suck, are slow, and quite possibly will not work ...

Sometimes you get lucky and it's fine. Sometimes it wont. It depends on what things changed in that version of Node. If the Node C++ APIs changed in a not backwards compatible way then we need to update our C++ code to be compatible.
This situation is getting better thanks to the new N-API that just went stable in Node 10. So in the future, local compilation will be more reliable between Node versions, but will still be slow and suck!

Unsupported runtime (64)

This number relates to the Node ABI

Got it. So by coincidence, I thought that it is related to 64-bit and does not really matters and the whole string is about OS I am running.

For more information on which environments are supported please see:

I'd change the link to section (not sure, is it possible in release details) here, or, at least, change message to For more information look for the 'Supported Environments' section on the page:.

Sometimes you get lucky and it's fine.

So you can't say here, will it be lucky for everyone who now will update node version to 10, or not, correct? Or if in 10th version nothing were changed on C++ APIs - rebuild will work for everyone, despite 10 version is unsupported? I kinda lost here.
Probably you can't say, as if you could, than it probably will be supported.

You've some raise good points. About the visibility of the supported environments.
The recent GitHub release page redesign has moved the release assets above the changelog copy. This big list of jibberish links is overwhelming, and doesn't signal there's anything to see below.
It would be good if we could make these more visible, and obvious.

I thought that it is related to 64-bit

That also matters. It's listed as either x64 64-bit, or x86 or ia32 for 32-bit.

For more information look for the 'Supported Environments' section on the page

The complication with this is that the supported environments are specific to particular releases. Alternative could be a better structure changelog instead of GitHub releases.

So you can't say here, will it be lucky for everyone who now will update node version to 10, or not, correct?

It means that nothing changed in V8 that broke the C++ APIs we use. Which means anyone who runs a rebuild will be able to successfully compiled the node-sass C++ code locally , if they have the correct compiler too chain to do so. Most Windows and linux users will not be default.
The thing is we can't know if there will be a breaking C++ API change until that version of Node is released.

Probably you can't say, as if you could, than it probably will be supported

When we say unsupported, we mean is for that node-sass + Node version combination

we don't test it in CI so there might be issues in the C++ code
we don't have binaries you can just download so npm install and npm rebuild node-sass will fail to download the binary and fallback to trying to compile locally.

Note: once we migrate our C++ to the new N-API it's much less likely new versions of Node will break our C++ code.

I had to downgrade my homebrew installation to get things to work.
Also, because brew hasn't updated to list node@9 yet, easiest thing to do was to (forcefully) downgrade to node@8.

npm install node-sass@latest is usually the easiest solution.
On Fri., 27 Apr. 2018, 1:43 am Willem Labu<EMAIL_ADDRESS>wrote:

I had to downgrade my homebrew installation to get things to work.
Also, because brew hasn't updated to list node@9 yet, easiest thing to do
was to (forcefully) downgrade to node@8.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2351#issuecomment-384689823,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWJbxzIn788aSflAZFqJHDhjZShpEks5tsesvgaJpZM4Tk5QS
.

Hey, sorry if this is not the correct issue to raise this in but...
I am in the process of sorting out all of my dependencies that use an outdated version of Boom - you guys are one of them, but there's no recent version that solves/updates this.
You guys in the midst of updating to a later version that doesn't have security issues?

This is definitely not the right place. Search the closed issues for the security issue or wiat for v5

Great, It could be great to migrate as now: Node.js remove version dependencies


Razor CompilationFailedExceptions contain design-time-missing content and incorrect line/column information

For instance:  I have an exception that fails with:
Additional information: C:\GIT\DataPoint\Source\DataPoint.Web\shell\default_shelllayout.cshtml(28,36): error CS0115: 'ASPV__shell_default__shelllayout_cshtml.ExecuteAsync()': no suitable method found to override
... but opening that file up with a text editor, I see that line # 28 looks like:
        </div>

... and furthermore, I don't have any calls to ExecuteAsync()  in the markup.  There are assorted calls to RenderSectionAsync that this is probably related to, but the end user shouldn't have to guess about this.
** Update:

I noted that the markup causing the issue is contained in CompiledContent property of the exception.  The exception text still directs me to the original, not compiled file, but at least the needed data is already there.

From @mattgal

@pranavkm please comment

We need mostly a doc that shows what a minimal base type should look like. @danroth27
Need to make it show up in helios/and diagnostics middleware

This should get addressed as part of https://github.com/aspnet/Mvc/issues/2321


Upload speeds of 400-600KB/s using <IP_ADDRESS> on a QNAP TS-664

First, thank you so much for making this resource available. It is a huge help and time savings! :)
I am curious if I've overlooked something obvious during the container setup causing very slow upload speeds to Crashplan and would appreciate someone else's opinion.
Environment info.

ISP: 1Gbps synchronous.
TS-664 (QTS <IP_ADDRESS>8) with both 2.5Gbe ports trunked to 1Gbps ports on an Ubiquiti switch. Everything between the switch and ISP also at 1Gbps.
Running www.speedtest.net within BrowserStation on the TS-664 shows 660Mbps down and 913Mbps up.
Crashplan container has no CPU limits and no memory limits defined. There are 32GB of memory installed in the TS-664.
Crashplan app inside the container has no WAN/LAN limits defined.
Crashplan container is given read-only access to a shared folder on the NAS containing content to save to Crashplan.

I installed the image in container station (v<IP_ADDRESS>2) a couple days ago and I am seeing extremely slow upload speeds of ~400-600KB/sec. I'm curious if it's something simple I overlooked in the setup. The particular backup job it is running right now is only 140GB and it is saying it will take 3.6 days to complete it.
Container station reports the container is using 2% CPU and 15% memory.
As I was writing this, I did just notice in the advanced settings CRASHPLAN_SRV_MAX_MEM is set to 1024M. Though I'm seeing no indication the container itself is out of memory, I wonder if a particular process inside it would benefit from an increase in this setting.
Sync jobs in QNAP's Hybrid Backup Sync 3 (e.g. from OneDrive to the TS-664 HDDs) have no trouble utilizing our ISP speed, so whatever this is seems like something I've accidentally self-inflicted on the container itself.
Thank you for any ideas.

I now see Crashplan's suggestion that 1024M should be fine up to the first 1TB or 1,000,000 files, so I'll leave that alone.

Upon further research, this may be typical, so I'll close this unless there's anything worth considering.
https://support.crashplan.com/hc/en-us/articles/8629577647885-Backup-speed-does-not-match-available-bandwidth-Enterprise-#01GB5RAYMP2HY9SF062XSKPRJ9
"CrashPlan app users can expect to back up about 10 GB of information per day on average if the user's computer is powered on and not in standby mode. "

Yes, upload speed to CrashPlan servers is known to be slow...!


Including scripts with include_dir_merge_list doesn't work

Home Assistant release (hass --version):
0.46.1
Python release (python3 --version):
3.5.1
Component/platform:
script
Description of problem:
If I try to include a script directory from the main config file with !include_dir_merge_list, I get no error but the scripts are not loaded.
Expected:
The files in the directory should be merged and included.
Problem-relevant configuration.yaml entries and steps to reproduce:
script: !include_dir_merge_list scripts/

Additional info:
It works with !include_dir_named and separate script files. This would be sufficient for me, if I could get an error message when using !include_dir_merge_list. It took too long until I realized what the problem is.

Assuming, you have a directory scripts inside the .homeassistant directory, it should be script: !include_dir_merge_named scripts or script: !include_dir_merge_list scripts depending on how you have saved the yaml files.

This is not an issue, this is how it is supposed to work.  Scripts are not added as lists, they are added as dictionary items (as per the documentation).
Should be !include_dir_merge_named - which definitely works as I use this in my configuration.

Oh, I understand now, thanks. I did not realized that scripts are not in a list but in a dictionary. I could not find this in the docs either. Maybe an example or a paragraph about this at https://home-assistant.io/docs/configuration/splitting_configuration/ or at https://home-assistant.io/components/script/ could help.
I was just copying my automations config (split-up), and used only one script. The config was ok by the checker script and there were no errors in the log. But the script was not loaded. So I had this:
script: !include_dir_merge_list scripts/
And only one file in scripts directory with this content:
test_script:
  alias: "Test Script"
  sequence:
    - delay: '00:01:00'

Basically, if a component looks like this it is a 'dictionary':
(note that the sub items are 'named' - first_script, second_script etc)
script:
  first_script:
    name: 'wonderful script
    other_option: xyz
    sequence:
      - item 1
      - item 2

  second_script:
    name: 'fabulous script
    other_option: abc
    sequence:
      - item 1a
      - item 2a

Then if a component looks like this it is a 'list':
(note that the sub items are preceded by hyphens, not names, so are 'listed')
automation:
  - alias: First Automation
    hide_entity: True
    initial_state: 'off'
    trigger:
      - platform: state
    [...]

  - alias: Second Automation
    hide_entity: True
    initial_state: 'off'
    trigger:
      - platform: state
    [...]

Based on this, when you split your configuration you will know whether to merges the directories as 'named' or 'list'.
It is explained in the docs, but maybe my explanation is better?  Let me know if it's clearer (or how I could clear it up more??) and I'll update the docs when I get chance.

Thanks for the explanation, I understand how it works. But an end-user has to notice by himself looking at the examples that scripts are in a map not in a list. This is not written in the docs. No one would think that scripts and automations are stored differently, because they are basically the same kind of things. I think simply mentioning the difference for example in a quoted paragraph on those two pages I linked is enough.
Thanks in the name of newborn HASS users!


Add mul and mul_ to BatchedArray

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (0c3a53a) 100.00% compared to head (1926eee) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #345   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           14        14
  Lines         1470      1481   +11
  Branches       160       162    +2
=========================================
+ Hits          1470      1481   +11

Files Changed
Coverage Δ

src/redcat/array.py
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix broken links

Unsure if this is the correct fix, but https://developers.mattermost.com/integrate/ seems to be a broken page

Thanks @amyblais. The links were updated as part of https://github.com/mattermost/docs/pull/4170/files and as they were existing links I didn't think to validate them. Thanks for picking this up!

Thanks @amyblais. The links were updated as part of https://github.com/mattermost/docs/pull/4170/files and as they were existing links I didn't think to validate them. Thanks for picking this up!


WIP: arm tests

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 52.41%. Comparing base (0613ce6) to head (a8f7a16).
Report is 5 commits behind head on main.

:exclamation:  There is a different number of reports uploaded between BASE (0613ce6) and HEAD (a8f7a16). Click for more details.
HEAD has 3 uploads less than BASE

Flag
BASE (0613ce6)
HEAD (a8f7a16)

oats-test
1
0

k8s-integration-test
1
0

integration-test
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1138       +/-   ##
===========================================
- Coverage   81.98%   52.41%   -29.58%
===========================================
  Files         141      141
  Lines       11588    11595        +7
===========================================
- Hits         9501     6078     -3423
- Misses       1561     5112     +3551
+ Partials      526      405      -121

Flag
Coverage Δ

integration-test
?

k8s-integration-test
?

oats-test
?

unittests
52.41% <ø> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

VM tests on ARM are too slow, as we need to emulate the architecture and kvm is not available.


Remove unused config cargo create

What
Remove the config cargo create dep.
Why
cargo +nightly udeps --all-targets, says it is unused. And afaict it has never been used. I think it was added accidentally in https://github.com/stellar/soroban-tools/pull/275, can you confirm @willemneal ?
Known limitations
[TODO or N/A]

We had added it with plans to use it, but indeed never did. Good catch!


Fix auto routing to storybook

Currently, the links of storybook are directing to the old storybook structure and not pointing to the new story structure. We should fix each component to route to its exact story location.

@jcfilben we need this one on our radar

Linked to https://github.com/grommet/grommet/issues/4651


recreate your experiments

Hello,
I am trying to recreate your experiment on the en-de NC11 corpus, and was wondering: did you just split the NC11 corpus into train,dev and test sets, and then clean just the train set?
Because after downloading the NC11 corpus, it appears it has 242,770 sentences, where as 238,843 + 2,169 + 2,999 ( the number of sentences in the train, dev and test sets accordingly, according to table 4 in the appendix) adds up to 244,011, so I was wondering what could account for the missing ~2000 sentences.
Thanks!

Yes, the training set was cleaned for Pascal.
You cannot clean the evaluation sets (dev & test) as, for one thing, results wouldn't be comparable.


[Chore]: document update and build time optimize

What changes were proposed in this pull request?

update README.md to reflect JDK requirement
exclude json-smart in hadoop-common
update CONTRIBUTION.md to change the project name and polish wording

Why are the changes needed?

For the first two changes:

When building uniffle locally, I noticed that it requires JDK1.8 to build and suspicious maven-default-http-blocker for json-smart.
[WARNING] net.minidev:json-smart/maven-metadata.xml failed to transfer from http://<IP_ADDRESS>/ during a previous attempt.
This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced.
Original error: Could not transfer metadata net.minidev:json-smart/maven-metadata.xml from/to maven-default-http-blocker (http://<IP_ADDRESS>/): transfer failed for http://<IP_ADDRESS>/net/minidev/json-smart/maven-metadata.xml

For the third change:

Before I'm making a PR, I found the project name in CONTRIBUTING.md is not changed yet. Thus, this commit
also updates the CONTRIBUTING.md and makes some amend to the doc.
Does this PR introduce any user-facing change?
NO
How was this patch tested?
No new tests are required.

Codecov Report

Merging #45 (02f4998) into master (ae674a6) will decrease coverage by 0.96%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #45      +/-   ##
============================================
- Coverage     56.87%   55.91%   -0.97%
+ Complexity     1207     1131      -76
============================================
  Files           152      143       -9
  Lines          8429     8054     -375
  Branches        816      786      -30
============================================
- Hits           4794     4503     -291
+ Misses         3376     3299      -77
+ Partials        259      252       -7

Impacted Files
Coverage Δ

...er/impl/UploadedStorageHdfsShuffleReadHandler.java
76.31% <0.00%> (-5.27%)
:arrow_down:

.../java/org/apache/uniffle/server/ShuffleServer.java
68.90% <0.00%> (-3.37%)
:arrow_down:

...org/apache/uniffle/server/ShuffleFlushManager.java
76.70% <0.00%> (-1.71%)
:arrow_down:

...e/uniffle/server/storage/SingleStorageManager.java
65.57% <0.00%> (-1.64%)
:arrow_down:

...pache/hadoop/mapreduce/task/reduce/RssFetcher.java
89.06% <0.00%> (-1.57%)
:arrow_down:

.../apache/uniffle/coordinator/ClientConfManager.java
91.54% <0.00%> (-1.41%)
:arrow_down:

...org/apache/spark/shuffle/writer/AddBlockEvent.java

.../org/apache/spark/shuffle/writer/WriterBuffer.java

...ava/org/apache/spark/shuffle/RssShuffleHandle.java

.../java/org/apache/spark/shuffle/RssSparkConfig.java

... and 5 more

Continue to review full report at Codecov.

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


workspace 1.64

Rust 1.64 is out and that could be the opportunity to make use of the workspace features ?
Checklist

[ ] An issue to be fixed by this PR is listed above.
[ ] New tests are added to ensure new features are working. End-to-end tests are usually in the ./frb_example/pure_dart example, more specifically, rust/src/api.rs and dart/lib/main.dart.
[x] The code generator is run and the code is formatted (e.g. via just refresh_all).
[ ] If this PR adds/changes features, documentations (in the ./book folder) are updated.
[ ] CI is passing.

spoiler alert : locally test-pure-web fails with a conversion error like :
00:01 +30 ~2 -3: dart call handleOptionBoxArguments [E]
  Error: expected a bigint argument

  pkg/flutter_rust_bridge_example.js 268:39  _assertBigInt
  pkg/flutter_rust_bridge_example.js 1011:5  __exports.new_box_autoadd_i64_0
  main.web.dart.js 12080:23                  LegacyJavaScriptObject.new_box_autoadd_i64_0$1
  main.web.dart.js 11495:43                  Object.new_box_autoadd_i64_0$1$x
  main.web.dart.js 24900:16                  FlutterRustBridgeExampleSingleBlockTestPlatform.api2wire_exotic_optionals$1
  main.web.dart.js 24605:53                  FlutterRustBridgeExampleSingleBlockTestImpl_handleOptionBoxArguments_closure.call$1
  main.web.dart.js 23285:20                  FlutterRustBridgeExampleSingleBlockTestPlatform.executeNormal$1$1
  main.web.dart.js 25023:48                  <fn>
  main.web.dart.js 3302:15                   _wrapJsFunctionForAsync_closure.$protected
  main.web.dart.js 14563:12                  _wrapJsFunctionForAsync_closure.call$2

00:11 +61 ~2 -7: chrono feature Duration [E]
  Error: expected a bigint argument

  pkg/flutter_rust_bridge_example.js 268:39  _assertBigInt
  pkg/flutter_rust_bridge_example.js 881:5   __exports.wire_duration
  main.web.dart.js 12044:23                  LegacyJavaScriptObject.wire_duration$2
  main.web.dart.js 11546:43                  Object.wire_duration$2$x
  main.web.dart.js 24814:16                  FlutterRustBridgeExampleSingleBlockTestImpl_duration_closure.call$1
  main.web.dart.js 23285:20                  FlutterRustBridgeExampleSingleBlockTestPlatform.executeNormal$1$1
  main.web.dart.js 25023:48                  <fn>
  main.web.dart.js 3302:15                   _wrapJsFunctionForAsync_closure.$protected
  main.web.dart.js 14563:12                  _wrapJsFunctionForAsync_closure.call$2
  main.web.dart.js 14551:32                  _awaitOnObject_closure.call$1

It's not on master I already checked, and it's surely because of my changes here but any idea where BigInt conversion breaks ? @Desdaemon

spoiler alert : locally test-pure-web fails with a conversion error like :
00:01 +30 ~2 -3: dart call handleOptionBoxArguments [E]
00:11 +61 ~2 -7: chrono feature Duration [E]

It's not on master I already checked, and it's surely because of my changes here but any idea where BigInt conversion breaks ? @Desdaemon

spoiler alert : locally test-pure-web fails with a conversion error like :
00:01 +30 ~2 -3: dart call handleOptionBoxArguments [E]
00:11 +61 ~2 -7: chrono feature Duration [E]

Not sure what's happening here, looks similar to #703 though js-sys is not updated here yet.

That wouldn't fix the BigInt assertion failure, but I noticed that the CI runs in 1.63, cargo workspace new features are fresh from 1.64.
See in the workflow run :
 The package requires the Cargo feature called `workspace-inheritance`, but that feature is not stabilized in this version of Cargo (1.63.0 (fd9c4297c 2022-07-01)).

CI fails for this :
strategy:
      matrix:
        cargo_toolchain_version:
          - stable
          - 1.55.0 # ❌ < 1.64

The package requires the Cargo feature called `workspace-inheritance`, but that feature is not stabilized in this version of Cargo (1.63.0 (fd9c4297c 2022-07-01)).

Can I remove it @fzyzcjy ?

Looks yes

@fzyzcjy really weird:

Yeah I know where the problem comes from.
So CI uses actions/cache@v3 and none of the cache keys have changed, as far as the CI sees, since the Cargo.lock hasn't changed for example.

I'm gonna get back at it this afternoon but honestly I'm starting to turn around in circles lol

Take your time!
Maybe firstly make it work locally?

Thing is, it already works locally 😅. But to be honest I always run test-pure-web because when I run test-pure locally I get the same error as #715

Ok so we're left with 2 errors that I'm not familiar with, and also give a bit obscure answers when searched online:

flutter with iOS (any device)
obviously the error is with Cargo Lipo[INFO  cargo_lipo::lipo] Creating universal library for flutter_rust_bridge_example
cp: target/universal/debug/libflutter_rust_bridge_example.a: No such file or directory

flutter with desktop (Windows / Linux)
obviously the error is with CMake and Corrosion[        ] CMake Error at
D:/a/flutter_rust_bridge/flutter_rust_bridge/frb_example/with_flutter/build/windows/_deps/corrosion-src/cmake/Corrosion.cmake:326 (add_library):
[        ]   add_library cannot create target "flutter_rust_bridge_example" because
[        ]   another target with the same name already exists.  The existing target is
[        ]   an interface library created in source directory
[        ]   "D:/a/flutter_rust_bridge/flutter_rust_bridge/frb_example/with_flutter/windows".
[        ]   See documentation for policy CMP0002 for more details.

Any hint ?

cp: target/universal/debug/libflutter_rust_bridge_example.a: No such file or directory

Maybe debug to see which files are generated?
And enable more debug logs

flutter with desktop (Windows / Linux)

/cc @Desdaemon who made that part :)

@fzyzcjy I'm currently trying to change cp because locally cargo lipo build into root target, but not sure.

@fzyzcjy I'm currently trying to change cp because locally cargo lipo build into root target, but not sure.

Ok so apparently it fixes iOS jobs (failing iPhone 12 Pro Max Simulator (15.2) is a false-positive, see its output).

any idea on how to fix Corrosion related issue @Desdaemon ?

oh I think I know :
error from Flutter (Windows) integration test / flutter_windows_test :
[        ] CMake Error at D:/a/flutter_rust_bridge/flutter_rust_bridge/frb_example/with_flutter/build/windows/_deps/corrosion-src/cmake/Corrosion.cmake:326 (add_library):
[        ]   add_library cannot create target "flutter_rust_bridge_example" because
[        ]   another target with the same name already exists.  The existing target is
[        ]   an interface library created in source directory
[        ]   "D:/a/flutter_rust_bridge/flutter_rust_bridge/frb_example/with_flutter/windows".
[        ]   See documentation for policy CMP0002 for more details.

and looking at frb_example/with_flutter/windows/rust.cmake :
set(CRATE_NAME "flutter_rust_bridge_example")

not sure with which artifact it conflicts because I've never used CMake 😅

Based on the tests in the corrosion repo, you may have to change the import path to the workspace manifest (!) and specify the member crate to import.

Honestly I have no idea how it works, so I'm guessing something like :
corrosion_import_crate(MANIFEST_PATH ${CMAKE_CURRENT_SOURCE_DIR}/Cargo.toml CRATES flutter_rust_bridge_example) in top declaration of CMakeLists.txt. I'm gonna give it a try.

That's weird that subosito/flutter-action@v2 fails so often at retrieve 3.3.1-x64, don't you think so ?

Unknown CMake command "corrosion_import_crate".

Well ... 😅

sorry for all the CI runs, it seems that glob(s) are ignored in workspace's exclude (as in 64a13407cab47b49dc8bc7b6c943ef001d08be1d and c9dc31bdbd9c0fa1c1d5173b9a2a62c2f57988cd), or I wrote these wrong. also I couldn't find the list of generated crates by corrosion.

also I couldn't find the list of generated crates by corrosion.
found it

so ok the issues were :

@Desdaemon was right, basically an additional setting needed to be added to corrosion_import_crate, but I was confused at first and the files that needed to be updated were all rust.cmake, not CMakeLists.txt.
in CI tests for Linux and Windows, corrosion is checkout from github and contains itself a lot of cargo projects. For some reason that I can't tell, [workspace]'s exclude property doesn't take into account glob(s), or I made a typo, but honestly usually corrosion or corrosion/**/* or corrosion/* should have been fine. Once found out, I just added all corrosion projects path manually, so beware that if in the future corrosion create some new internal project, subsequent Linux / Windows CI runs will fail for the same reason.

if this CI run goes fine, we're probably ready for a review @fzyzcjy.
the PR has became a little bit of a mess with all these oddities, so 2 options regarding the reusable workflows.

I leave it the way it is, and we can still refactor the rest later
I revert reusable workflows completely, keeping ci.yml as close as it was before (plus the fixes, of course)

Is there any reason not to use needs  directive in Github workflows ?
I mean you could save a lot of CI time.
For example, run Mergeable + Codacy Static Code Analysis + CI / Dart Linter + CI / Rust linter + CI / Build and run Rust + CI / Valgrind. Then once they're all successful, run all CI / Run codegen ... and all CI / ... integration tests.

I am still busy working on https://docs.google.com/document/d/1FuNcBvAPghUyjeqQCOYxSt6lGDAQ1YxsNlOvrUx0Gko/edit# so may not have time to review the PR now. Maybe @Desdaemon can provide some reviews :)

Good job! Looks like the CI system has been modified a lot :)

Actually mainly a couple missing scaffold actions (e.g. like Install Rust toolchain or some missing toolchain components here and there), forcing override and 1.64.0 for Rust toolchain all over the place, and especially disabling cache (then re-enabling it) to force the CI to really use 1.64.0 everywhere. Looking back I think I was a bit too prompt to implement it. A couple of weeks from now it would have been the chosen stable by default, cache would have been naturally updated seamlessly.

I noticed the manifest .release files haven't been updated in a while, I'm about to commit them. @Desdaemon we should surely double-check that post-release scripts are ok, to avoid CI failure once merged (I'm gonna do it, but it doesn't hurt if we are both checking).

LGTM 😉
only point left, + your review(s) 🙂 🙏 🚀

Good job!

I will release a new version when having some time :) Still quite busy working on the open sourced https://github.com/fzyzcjy/flutter_smooth


Remove IndexVariable.name

As discussed in #947, we should remove the IndexVariable.name attribute. It should be fine to use an IndexVariable anywhere, regardless of whether or not it labels ticks along a dimension.

Am I missing something, or is there no IndexVariable.name attribute anymore?


Add Carob

Insert URLs to the project here:
https://github.com/reagro/carob

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as 'Good First Issue' of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.

@rhijmans @egbendito @cedricngakou


Deploy to a subfolder?

Is there a way to deploy to a subfolder, e.g. http://apps.com/tracker? I tried this:
  // Configure environment
  "env": {
    "ROOT_URL": "http://apps.com/tracker"
  },

But it doesn't quite work. And once I click on a link to a detail page, I would expect it to go to http://apps.com/tracker/vELwe6rB3YbEf5grR but instead it goes to http://apps.com/vELwe6rB3YbEf5grR.
Is there an elegant way to do this?

Hi, this will be really valuable if possible. Better to be able to use one domain with subdomains instead of buying a new domain for every app

@ffxsam did you figure this out?

@nathanmarks Nope, and I don't think it's possible due to how routes work. Unless there's some way to tell Iron Router that the root is /subfolder rather than /.


[FixCode] Apply coercion fixits on return statement and initialization.

We saw manual migration is necessary on these cases to add 'as Type'. This patch starts
to issue compiler fixits on return statement and initialization just like in other type-mismatch
cases.

Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

…n as well. rdar://27891589 rdar://27891426
We saw manual migration is necessary on these cases to add 'as Type'. This patch starts
to issue compiler fixits on return statement and initialization just like in other type-mismatch
cases.

@swift-ci Please smoke test and merge

@swift-ci test macOS


IE11 Script Error on Microsoft Graph oauth page

When running the example, the login window shows a script error:
Object doesn't support this property or method "startsWith" (Screenshot)
As far as I can tell, the login dialog opens an Internet Explorer instance and navigates to the URL specified in the error (https://login.microsoftonline.com/common/oauth2/v2.0/authorize) and indeed visiting this URL in IE produces the same error. (Screenshot 2)
Clicking on "OK" to abort the script results in a blank page.
This issue breaks my app as no login is possible. Two days ago on Monday 7th the same code worked as expected.

Thanks for your interest in Microsoft Graph! We are archiving this sample, so I'm closing this issue. For a replacement C# console app sample, please see https://github.com/microsoftgraph/msgraph-training-dotnet-core. We apologize for any inconvenience.


Fix/outline symbols

Coverage remained the same at 49.194% when pulling c26403673d906d383a9b1262647014668de82104 on fix/outline-symbols into 925a4dbef2b568cb058310ecb814e0ea427fbbfc on master.


Easier Alternatives - Feature Suggestion

Hello once again! :D I'm incredibly happy with the newest update, it fixed absolutely everything. I felt a little adrift, honestly. No bugs for me to report D:
Anyways! I've come to notice something I'd like, and it's partially inspired by what @Isslea mentioned in #2: Multiple-word alternatives. There's a few use-cases on my mind, though they're all related.
The most common one is rather simple: Sometimes my cards say "I'm", and sometimes they say "I am". When I want the card to allow both, I usually do this:
"I'm happy., I am happy."
Another method I use for alternatives is a mixture of slashes and brackets which works beatifully nowadays:
"I went to the cinema/movie (theater)."
Now, both of those work. They're just. It could be better.

So much for the situation, now for the actual feature suggestion. Particularly for reasonably common cases like "I'm/I am", I wonder if you might be able to do another setting so that I can specify in the config particular strings of characters which should be treated as identical. I imagine the setting to look something like this:
{
    ...
    "Identical Strings":
        ["I'm", "I am"],
        ["xy", "xz"]
}

The specific case of I'm vs. I am feels so ridiculously common that I am really hoping for this one to be implemented. Hell, if the feature works out as I hope it will, then you could also specify that " not" (mind the extra space) can also be "n't". or [" is", "'s"], [" are", "'re"], and so on. The same for similar features in other languages.

I had half an essay typed up here but then decided to scrap it and instead just give the summary: You already implemented multiple-word alternatives, probably by sheer accident, see my movie theater example above. My feature suggestion, too, aims to make them easier on the user - basically, to save me from having to type a whole bucketload of brackets. If you ever were to do more work on that topic, on multiple-word alternatives, I would hope that focus remains: that the new feature will make the plugin easier on the user, to make the plugin work with the user's cards, instead of the user having to adjust their cards for the plugin.
To think that the issue is still this long after I approximately halved it. Umm. Whoops? But, oh well. If nothing else, I hope that shows how much I'd appreciate this. ...And how tired I am of brackets!
Right. Thanks a lot for all the hard work you do! Looking forward to hearing what you think about this!

I'm glad to hear it's been working out! :)
I think after making that previous  change, your idea should be pretty easy to do, and it seems like it would be pretty useful. Let me think about it for a bit and figure out the best way to do it! I think I should be able to make it so that you can configure a list of strings which would be treated as being effectively the same like you suggested.

Ok, I added it under a config option called "Equivalent Strings"! This is what your example config would look like:
{
    ...
    "Equivalent Strings": [
        ["I'm", "I am"],
        ["xy", "xz"]
    ],
    ...
}

Also for alternatives containing spaces, I went to the [cinema/movie theater] is also supported (as suggested in #2). However, the text inside the brackets is still considered optional, so this might not be ideal. I might add another config option in the future to support this better.
Please let me know if you see any issues!


Update CLI extensions available doc

Update CLI extensions available doc.
Triggered by Azure/azure-cli-extensions - TRAVIS_BUILD_ID=629206880
https://github.com/Azure/azure-cli-extensions/commit/f30a59736b3743775793477d97dd7432f1d5f52a

Docs Build status updates of commit 3a151a6:
:clock10: Full build: the average full build time is 7 min(s) 9 sec(s), this is based on the last 323 build(s) for this repository.

Docs Build status updates of commit 3a151a6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Split facilitator servlet for easier maintenance

The FacilitatorServlet class is over 2000 lines now. It can be split over multiple smaller classes with static methods (almost all methods of the servlet class are static already).

The FacilitatorServlet has been split into the following classes:

ContentFlood (handling dice rolls)
ContentNewRound (handling the creation of a new round)
ContentTaxes (handling tax calculation)
PopupBuyServlet (handling the popup for allowing/rejecting of house buy)
PopupSellServlet (handling the popup for allowing/rejecting of house sell
PopupStayServlet (handling the popup for allowing/rejecting of house stay)
TablePlayer (filling the player information tables)
TableHouse (filling the house information tables)
TableNews (filling the news table)
TableFlood (filling the flood information table)

The FacilitatorServlet itself just handles the state machine and the popups related to the state progress with warnings about the number of active players and players' progress.


Fix issue with non-US keyboards and Alt+Gr key combinations

Many non-US keyboards including my Hungarian one requires AltGr (right Alt) to be held to enter certain special characters. That AltGr also acts as Ctrl+Alt.
There's a problem where certain special characters are caught by the alt/ctrl commands and do a special action rather than type the desired character. E.g. pressing AltGr+B should result in { on the Hungarian keyboard, but is caught by Alt+B to move to the previous word instead.
This change should fix this issue by demanding that the modifier keys pressed are exact (only Alt, only Ctrl or only Shift) rather than being lenient to allow for other modifiers to be pressed at the same time too.
I couldn't find any unit test files for adding tests.

Ta!


TypeError: Cannot read property 'then' of undefined     at l.$scope.getLogin

Hi i am using angularJs v1.3.13, not sure why above error is coming almost same code is working fine in other project here is my code
(function () {
'use strict';
angular
    .module('MyModule').controller("LoginController", ['$scope', 'loginService', '$location',
    function ($scope, loginService, $location) {

        $scope.getLogin = function (login) {
            $scope.error = false;

            loginService.getLogin(login).$promise.then(

                function (data) {
                    $location.url('Employee/AccountSummary');

                },
                function (err) {
                    $scope.error = true;
                }
            );
        };

    }]);

}());
Please suggest where is the issue.
Thanks

Issue resolved, problem was my repository was not returning proper JSON, Thanks any ways.


[Feature Request] rfc6052 support

It would be nice to have support for rfc6052 addresses, which follow a pretty weird format.
Two commands (rfc6052-pack and rfc6052-extract) would be handy.
Heres an at-a-glance view of how this addressing scheme works:
+--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|PL| 0-------------32--40--48--56--64--72--80--88--96--104---------|
+--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|32|     prefix    |v4(32)         | u | suffix                    |
+--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|40|     prefix        |v4(24)     | u |(8)| suffix                |
+--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|48|     prefix            |v4(16) | u | (16)  | suffix            |
+--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|56|     prefix                |(8)| u |  v4(24)   | suffix        |
+--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|64|     prefix                    | u |   v4(32)      | suffix    |
+--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|96|     prefix                                    |    v4(32)     |
+--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+

Example syntax could be:
$ cidr rfc6052-pack <prefix>/<mask> <ipv4> [<suffix>]
$ cidr rfc6052-extract <address>/<mask>

The first command would return an IPv6 address, and the second would return an IPv6 prefix, an IPv4 address, and an optional suffix. (or just error, if its invalid)

I realize that this is the wrong language, but I do have an implementation of this hiding away here if you are curious: https://github.com/ewpratten/protomask/tree/ewpratten/reorg2/libs/rfc6052/src

Hello @ewpratten, I appreciate you bringing up this issue. Personally, I'm not well-acquainted with rfc6052, and I plan to dedicate some time to thoroughly understand it. In the meantime, could you share a few use cases and elaborate on why you believe integrating rfc6052 would add value to cidr? Additionally, does rfc6052 take into account both IPv4 and IPv6 (the intention behind cidr is to be agnostic to both IPv4 and IPv6, offering features that naturally support both) ? I'll also be doing my research on this topic. Thanks again!