realloc was always behind in size 1/2

Because size is increased in the lines after the realloc, the realloc always contained one bit less as stored in the enc variable.

nice catch!
cc @jwerle

:+1:


Fixed port forwarding command.

/fixed #353

This change is

/assign @abhi-g

Thanks Sarah.
/lgtm
/approve

Not sure why the netlify deployment failed. There are no errors in the log. Possibly a fluke ..


Add BLE Scanner app

A simple application that allows scanning for nearby BLE devices using NRF.findDevices
Modifications/feedback very welcome!

I was working on the exact same thing right now, but I didn't think to use the .menu instead of drawString.  Awesome, it's working great!

Thanks! Just merging - should go live in a few minutes,

Cheers!


Add missing golang example for sshkey.md

Proposed changes
Add missing golang example for sshkey.md

Thanks for the submission! The examples are code generated, so I think we'd need to do something extra here to preserve this on subsequent updates. @stack72 is there any mechanism for doing so?

hi @leezen , any news on this one? 😄

Hi @dirien
I'm working on a mechanism in https://github.com/pulumi/pulumi-terraform-bridge/issues/364 to allow this to happen :)
P.

I'll close out this PR as we'll want to submit the example against a different repo.


SignInManager needs a ConfirmEmailAsync API that also accepts user's password

I know there's already a confirm email on the UserManager, but imagine this scenario:
I want my email verification page to require the user's password (in addition to the code) -- people enter wrong email addresses all the time and we need a way to protect against the wrong email recipient from using the code to pwn the account.
So before I can verify the code, I also need to verify the password. Now I can call CheckPassword on the UserManager, but that level in the API does not provide me brute force protection. So I need an API on the SignInManager that will do the brute force checks on the password without trying to force 2fa or check that the email is already confirmed (because we're in the middle of confirming the email).
So the SignInManager could have an API that accepts the user, code, and password.
This email verification is hard stuff.

Sounds like what you really want is just a way to just CheckPassword that doesn't do SignIn or TwoFactor on SignInManager, but optionally will still count against lockouts/login failures
  Task<SignInResult> SignInManager.CheckPasswordAsync(user, password, lockoutOnFailure)

fe60304df54c43030d3eacfd9073e6a36990db05


bugfix: prevent dfgettask metrics < 0

Signed-off-by: yeya24<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
Add a check before deleting supernode dfget tasks
Ⅱ. Does this pull request fix one issue?

fixes #853
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
No
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #854 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #854      +/-   ##
==========================================
+ Coverage   39.64%   39.64%   +<.01%
==========================================
  Files         109      109
  Lines        6429     6434       +5
==========================================
+ Hits         2549     2551       +2
- Misses       3672     3675       +3
  Partials      208      208

Impacted Files
Coverage Δ

supernode/daemon/mgr/dfgettask/manager.go
48.21% <100%> (+0.46%)
:arrow_up:

hack/boilerplate/check-boilerplate.go
33.33% <0%> (-3.26%)
:arrow_down:

supernode/daemon/mgr/progress/progress_delete.go
0% <0%> (ø)
:arrow_up:

dfget/config/config.go
91.76% <0%> (ø)
:arrow_up:

cmd/dfdaemon/app/root.go
63.63% <0%> (+1.29%)
:arrow_up:

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 7057063...0c79930. Read the comment docs.

LGTM


Post to Teams does not seem to work

Hi
I am trying to add the playbook https://github.com/Azure/Azure-Sentinel/tree/master/Playbooks/Post-Message-Teams to post in a Teams Channel for every new incident.
Although i deploy the playbook successfully when i run trigger  it always fail on the Alert - Get incident step with 404 resource not found are there any special permissions needed ?
What am i missing?  Any info from someone that already deploy it ?
Thanks in Advanced

One addition when i try to run the playbook in the incident i get this error message:
ExpressionEvaluationFailed. The execution of template action 'For_each' failed: the result of the evaluation of 'foreach' expression '@body('Alert_-_Get_incident')?['value']' is of type 'Null'. The result must be a valid array.

Hi @akefallonitis  are you triggering the playbook from the logic app resource? or from Azure Sentinel?
ExpressionEvaluationFailed. The execution of template action 'For_each' failed: the result of the evaluation of 'foreach' expression '@Body('Alert_-_Get_incident')?['value']' is of type 'Null'. The result must be a valid array.
this implies the get incident returned null, which would happen if the sentinel trigger is null.  you can not trigger these playbooks from logic apps as they wouldnt have any data from the sentinel trigger.  you need to do it from azure sentinel in one of your incidents.

Hi @dicolanl and thanks for your answer
I have tried both triggering from Sentinel and Logic app.
It only work from sentinel when i remove the for each statement

ahh ok.  Let me look at it and we can update by removing the loop.

So the loop is not needed ?

Nope.. ;)


ConnectError::Sasl

On trying to connect with Azure Iot hub, I get the Sasl exception: SaslCode::Sys
What does this error code mean?

according to spec it is Connection authentication failed due to a system error.
you can enable trace logging, it may give more info

Thx for the quick response.
Enabling tracing did not really show much more, so I added a few more traces.
-> The Sasl Outcome seems to return the SASL sys error.

This is probably a misconfiguration on my part.
So one more question:

If the URL azure iot hub requests is of the following format:
-> 'amqps://username:sas_token@hostname/operation'
How do you translate it in all the params.  Im just not sure about what the 'authz_id' param means.

Posted an issue on Azure: Link

authn_id should be set to key name
password is key itself,
        let auth = ntex_amqp::client::SaslAuth {
            authz_id: ByteString::from_static(""),
            authn_id: key_name,
            password: key,
        };

        let mut c = ntex_amqp::client::Connector();
        c.hostname(hostname);
        c.connect_sasl(hostname, auth)

Thx for the reply. I have tried a few options, and will now wait for a reply on Azure & Discord. I will post the solution here if I find the solution. This more a problem with Azures unclear docs :(. I will keep the issue open for now so I can post the solution later.
Thx for your time, have a good day 👍 .

I just found the solution to the problem, so here is the soltion (I was quite stupid actually :p)
The problem is a combination of Azure and my code. The url_encode is not needed. Also, Access keys generated on Azure use the wrong signature. If found this out by sniffing through the python code.
This is the final code, which can successfully connect 👍
You can generate the correct SAS token with this:
`
pub mod azureiothub {
use std::fmt::Error;
use std::ops::Add;
use chrono::Duration;
use hmac::{Hmac, Mac, NewMac};
use log::trace;
use sha2::Sha256;
use base64;
// Azure Iot Hub
pub struct Client{
    // The azure client
}
impl Client{
    // The client methods
}

pub enum GenSasTokenException{
    DECODEBASE64,
    INVALIDKEYLENGTH,
}

pub fn hostname(iot_hub_name: String) -> String{
    format!("{}.azure-devices.net", iot_hub_name)
}

pub fn generate_sas_token(key: String, device_id: String, hub_name: String, validity_days: i64) -> Result<String, GenSasTokenException>{
    // Generate a VALID SAS token
    // Recoded from the rust azure SDK (mqtt) and the generate_sas_token function (Python SDK)
    let b64_key = base64::decode(&key);
    if b64_key.is_err(){
        // Failed to decode
        trace!("Failed to decode base64 key.");
        return Err(GenSasTokenException::DECODEBASE64)
    }
    // Continue
    // Is the key the right length?
    let check_hmac = Hmac::<Sha256>::new_from_slice(&b64_key.unwrap());
    if check_hmac.is_err(){
        // Failed the length
        trace!("The length of the key is invalid.");
        return Err(GenSasTokenException::INVALIDKEYLENGTH)
    }
    // Continue
    // Create the expire date.
    let mut time_now = chrono::offset::Utc::now();
    // Add the amount of days
    let mut add_days = Duration::days(validity_days);
    let mut time_now_plus_day = time_now.add(add_days);
    // Now lets generate the token.
    let expiry_timestamp = time_now_plus_day.timestamp();
    let hub_url = format!("{}.azure-devices.net%2Fdevices%2F{}", hub_name, device_id);
    //  Coded to_sign
    let to_sign = format!("{}\n{}", &hub_url, &expiry_timestamp);
    println!("{}", to_sign);
    // Safe to unwrap --> Check before
    let unwrapped_key = base64::decode(&key).unwrap();
    // Start generation
    let mut mac  = Hmac::<Sha256>::new_from_slice(&unwrapped_key).unwrap();
    // SIGN GEN
    mac.update(to_sign.as_bytes());
    let mac_result = mac.finalize();
    let signature = base64::encode(mac_result.into_bytes());
    let pairs = &vec![("sig", signature)];
    let token_result = serde_urlencoded::to_string(pairs).unwrap();
    // Build up token signature
    let full_token = format!(
        "SharedAccessSignature sr={}.azure-devices.net%2Fdevices%2F{}&{}&se={}&skn={}",
        hub_name,
        device_id,
        token_result,
        expiry_timestamp,
        device_id
    );
    return Ok(full_token)
}

}
mod test {
use std::process::exit;
use crate::azureiothub::generate_sas_token;
#[test]
fn gen_token(){
    let token = generate_sas_token(String::from("PrimairyKeyHere"),
                       String::from("devicename"),
                       String::from("hubname"), 365);
    if token.is_err(){
        println!("Failed");
        exit(1);
    }
    else {
        println!("Token: {}", token.unwrap_or(String::from("")));
    }
}

}`
The correct code to connect is this :
`let auth = ntex_amqp::client::SaslAuth {
authz_id: ByteString::from_static(""),
authn_id: authenticator_id.into(),
password: password.into()
};
let mut driver = client::Connector::new()
    .connector(RustlsConnector::new(Arc::new(tls_config)));
driver.hostname(hostname);
let result = driver.connect_sasl(address, auth).await;

`
This code will work for Azure Iot Hub, with TLS 1.2


Waypoint: Stand in Line - unable to use splice instead of shift?

Challenge Waypoint: Stand in Line has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:42.0) Gecko/20100101 Firefox/42.0.
The challenge is probably wanting the user to use shift() rather than splice(0,1) but it seems like the solution should still pass. Below is my code with the successful line commented out and the unsuccessful splice code uncommented. This fails the first two tests and passes the third.
My code:
// Setup
var myArr = [];

function queue(arr, item) {
  // Your code here
  arr.push(item);
  item = arr.splice(0,1);
  // item = arr.shift();
  return item;
}

// Display Code
console.log("Before: " + JSON.stringify(myArr));
console.log(queue([2], 1)); // Modify this line to test
console.log("After: " + JSON.stringify(myArr));

Most likely because splice() returns an array of what was spliced, the tests are looking for item to NOT be in an array.

Most likely because splice() returns an array of what was spliced, the tests are looking for item to NOT be in an array.

@ShaggyTech is correct. Thanks and happy coding!

@ShaggyTech is correct. Thanks and happy coding!

Thanks ShaggyTech! I did ask in the help room but it's a bit hectic in there at the moment

Thanks ShaggyTech! I did ask in the help room but it's a bit hectic in there at the moment


Back button want is not setting permanent in PageHeader.

Hi Sir,
I am using Template10 Hamburger menu template. In this we have setting page whic set page back button as per setting. But I want to set back button permanent in page header and if I click on logout then  backbutton should be collapsed over login page. Could You please help me this small issue.

Just remove the XAML markup for the back button location from
SettingsPage.xaml. That will prevent users from reconfiguring it.
On 9/26/16, Pawan Kumar Verma<EMAIL_ADDRESS>wrote:

Hi Sir,
I am using Template10 Hamburger menu template. In this we have setting page
whic set page back button as per setting. But I want to set back button
permanent in page header and if I click on logout then  backbutton should be
collapsed over login page. Could You please help me this small issue.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/Windows-XAML/Template10/issues/1241

--
Thanks,
CJ

But I want to set it in always page header

If I understand your question correctly, the Back button is set automatically for you when there is a back navigation. But when you land on your login page (I assume that this has a top menu link) you want it not to appear.
In that case, for the login page menu button (corresponding HamburgerButtonInfo control) set the ClearHistory="True" so that navigation history is cleared and the Back button doesn't show up.

this way is fine if I am using Logout button in primary icons then How can I do it.

What's the question?

controls:PageHeader.PrimaryCommands

</controls:PageHeader.PrimaryCommands>
I am using Logout button in this way, So how Can do on its click clear the history

I got answer :) :)  NavigationService.ClearHistory() I can use right ?

I am assuming your Logout button is in HamburgerMenu rather than in PageHeader. Couldn't you move it to HamburgerMenu where it's done for you automatically?
In my opinion, Logout is more suited as a secondary menu in HamburgerMenu (that way the user can reach it from anywhere) and I don't understand why it ends up in the PageHeader.

ok , its fine I have done it. Apart from this there was one issue also regarding elipsis button which on appear automatically when we use PrimaryCommands. I want to hide this elipssis icon and and wanto use custom icon. have any way?

elipsis will be there as long as there is a AppBarButton in PageHeader. Tapping on elipsis will reveal the AppBarButton caption (in addition to revealing secondary menus hence why it's still there). No elipsis implies no AppBarButton in PageHeader.

No, I don't think the ellipsis can be disabled.
On 9/26/16, Pawan Kumar Verma<EMAIL_ADDRESS>wrote:

ok , its fine I have done it. Apart from this there was one issue also
regarding elipsis button which on appear automatically when we use
PrimaryCommands. I want to hide this elipssis icon and and wanto use custom
icon. have any way?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/Windows-XAML/Template10/issues/1241#issuecomment-249499159

--
Thanks,
CJ

There should be any way.

Nothing is impossible if you have the time and resources but it's much easier and sensible to use frameworks/tools like T10 as they were intended to be used. Yes, you can tweak here and there on the edge cases but for most part, we have to respect how the framework is intended to be used.
Or you can re-write T10 as you like to create your own (why I say nothing is impossible) but pause and think before you do that.

if I use Appbar in that case I am able to hide the elipssis button with the following lines of code.

But this one is not working for template10 I am not getting why.

Because the PageHeader is not an AppBar - T10's creators decided that
the ellipsis button was useful in a high enough % of cases to warrant
making it non-toggleable. You happen to be one of that small % who
find that counter-productive.
On 9/26/16, Pawan Kumar Verma<EMAIL_ADDRESS>wrote:

if I use Appbar in that case I am able to hide the elipssis button with the
following lines of code.

But this one is not working for template10 I am not getting why.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/Windows-XAML/Template10/issues/1241#issuecomment-249503091

--
Thanks,
CJ

This is T10 anti-pattern if I can call it that.  Not sensible to seek help to undo what T10 and the host platform do for us.  Where disabling a feature is considered sensible, T10 (or platform) usually provide programmable options. In this case, the . . . button has a job to do -- to reveal caption and staying put.
Please re-read my comment above.

if I enhance the pageheader content then  its possible or not ?

Did we not spell it out for you? No. It isn't possible, and
considering the important function it serves, it shouldn't be
possible.
On 9/26/16, Pawan Kumar Verma<EMAIL_ADDRESS>wrote:

if I enhance the pageheader content then  its possible or not ?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/Windows-XAML/Template10/issues/1241#issuecomment-249505055

--
Thanks,
CJ

I am handling it with following lines of code.
controls:PageHeader.Content

<Grid.ColumnDefinitions>

</Grid.ColumnDefinitions>

<Button.Flyout>

<MenuFlyoutItem.Template>

</MenuFlyoutItem.Template>

<MenuFlyoutItem.Template>

</MenuFlyoutItem.Template>

</Button.Flyout>

        </controls:PageHeader.Content>

This is why T10 provides a default implementation which is perfect for
(almost) anything.
You've just blown the complexity factor of your code out of the
water... to remove ONE button (which is actually pretty useful).
Wouldn't it have been simpler to do it in a standard fashion using
PrimaryCommands?
On 9/26/16, Pawan Kumar Verma<EMAIL_ADDRESS>wrote:

I am handling it with following lines of code.
controls:PageHeader.Content

<Grid.ColumnDefinitions>

</Grid.ColumnDefinitions>

<Button.Flyout>

<MenuFlyoutItem.Template>

</MenuFlyoutItem.Template>

<MenuFlyoutItem x:Name="RoutesInProgress"
HorizontalAlignment="Center"
FlowDirection="LeftToRight"
Padding="80,8,80,8"
Text="Routes In Progress">
<MenuFlyoutItem.Template>

</MenuFlyoutItem.Template>

<MenuFlyoutItem x:Name="LogOut"
HorizontalAlignment="Center"
FlowDirection="LeftToRight"
Padding="80,8,80,8"
Text="Logout" />

</Button.Flyout>

        </controls:PageHeader.Content>

--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/Windows-XAML/Template10/issues/1241#issuecomment-249505908

--
Thanks,
CJ

If the default implementation is not right for you, just use CommandBar and add your functionality to it. You can even copy our starter code if you want from source.


error on image

https://iiif.bdrc.io/bdr:I1NLM2232_001::I1NLM2232_0010001.jpg/full/,600/0/default.jpg

@TBRC-Travis @jimk-bdrc I'm describing the issue just FYI. No action to take on your part, except perhaps https://github.com/buda-base/asset-manager/issues/125 in the future. What happens is:

the URL of the image requests the IIIF server to produce a 600px wide version of the image instead of the original, this means that the IIIF server must decode the JPG, resize it to fit the requested size, and reencode it
because Java image processing is... bad... we can't extract the ICC profile of a decoded picture without a very big hit on performance (in Python this would be a non-issue)
so we resort to a hack where we read at most the first x bytes of the original image, try to find the ICC profile in there, then go back to the beginning of the bytes (the reset function) and then decode the image
this works when x is large enough to go to the end of the header where the ICC profile is
in that case (because of the thumbnail), x wasn't large enough
I've raised x from 40k to 60k, which solves this issue

There's an implicit request here to extract and store this information from inside audit tool. It's intriguing, and should be part of a general ingest step. I'll flesh this out in asset-manager#125

Here's another failure: https://iiif.bdrc.io/bdr:I8LS26144::I8LS261440003.jpg/full/,500/0/default.jpg


cURL error 35: Unknown SSL protocol error in connection

Hello i'm trying to send post to external https url using guzzle and i'm getting the following error
ConnectException in CurlFactory.php line 186:
cURL error 35: Unknown SSL protocol error in connection to www.netcommercepay.com:443 (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)
and this is my request:
$client = new Client();
$response = $client->post('https://www.netcommercepay.com/iPAY/', [
	'form_params' => [
			'payment_mode' => $payment_mode,
			'txtAmount' => $txtAmount,
			'txtCurrency' => $txtCurrency,
			'txtIndex' => $txtIndex,
			'txtMerchNum' => $txtMerchNum,
			'txthttp' => $txthttp,
			'signature' => $signature,
		]
]);

i tried to add CURLOPT_SSLVERSION and CURLOPT_PROTOCOLS and still returning error
any solution?

Can you try sending a request from cli as well? I had this issue in the past, but there was something with the cURL build in my case.

I think this is a problem with netcommercepay.com and not Guzzle; Their DNS doesn't seem to be resolving at all, I've tried ping'ing, scanning, tracert, DNS/Reverse DNS look ups etc. and the server doesn't give any response.
http://downforeveryoneorjustme.com/netcommercepay.com also showing that it's down.
Try contacting their support and see what's going on?

Probably?

yes the reason was from netcommerce i tried another url and it worked fine i think netcommerce does not support curl or something


Move core/profiling/timers_preciseclock.h to core/support/ such that we

have a gpr public function which returns cycle clock.

Looks like include paths in basic_timers.c need to be updated.

You are right. Done.
On Tue, Aug 25, 2015 at 8:28 AM, Craig Tiller<EMAIL_ADDRESS>wrote:

Looks like include paths in basic_timers.c need to be updated.
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/3048#issuecomment-134626517.

And it looks like this needs a merge with head.

done.

Fixed.
Really sorry for the inconveniences...


[VERSION TRACK] v3.1.0 Known Issues & Bugs

Known Bugs - v3.1.0
This issue is an umbrella issue to keep track of bugs in the current version.  You can reply directly here, but opening a new issue would make life easier for us.
Issue List

[x] Depend flag not working correctly.  Fixed.

v3.2.0 Roadmap

[x] Right click accessible depend / required by list.
[x] Color code for collections

Full Changelog

If it is possible. Can the mods of these categories be listed here?

sounds good to me - I'll drop it in there later today or tomorrow.

Maybe a very thin, contrasting frame for additional windows?

When loading, it is stalling out

W10. Colour: Steel blue.

Night Light: Off
Display Orientation: Landscape

Maybe it's because of the scale? I have it set to 125%.

From the information I am getting from the electron folks, it is the difference of Win10 vs. Win11 - for instance, this is what it looks like on my screen (win11)

But even on my display, I don't have any real control over the border color - and if I enable the "Accent color border" accessibility feature on win11, it does not update the electron window.

Clear. Thanks for the answer. If this is the case, then there is no need to waste time.
It's just that when I need to close an additional window, on the background of the main window, I always look for the borders and the "x" button for several seconds. )))
Don't waste time.

Aye.  I have been messing around and I can't manage to get any sort of border on the window content that looks even almost alright - the limitation is that the bottom border does not want to behave at all, and the right side border really, really does not want to appear on the correct side of the scrollbar.  Sorry about that, I really thought this was going to be a simple edit.

On Wednesday, August 23, 2023 at 11:11:27 AM CDT, J.T. Sage<EMAIL_ADDRESS>wrote:

Aye. I have been messing around and I can't manage to get any sort of border on the window content that looks even almost alright - the limitation is that the bottom border does not want to behave at all, and the right side border really, really does not want to appear on the correct side of the scrollbar. Sorry about that, I really thought this was going to be a simple edit.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
Here are my logs in regards to the app stallingMessage ID: @.***>

Has there been any progress on this issue of stalling out while loading mods?  Currently I can only use the last folder I chose as active.  Even if I uninstall this app and put mods in the games mod folder
On Wednesday, August 23, 2023 at 11:11:27 AM CDT, J.T. Sage @.***> wrote:
Aye. I have been messing around and I can't manage to get any sort of border on the window content that looks even almost alright - the limitation is that the bottom border does not want to behave at all, and the right side border really, really does not want to appear on the correct side of the scrollbar. Sorry about that, I really thought this was going to be a simple edit.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Welcome back after the break. I hope you're doing well.

Welcome back after the break. I hope you're doing well.

thanks.  been a very hectic couple of weeks - still not really calmed down, but I am hoping to have some more time.  Fwiw, there is a RC that dropped, in theory, it should fix some of the parser crashes, probably.  Or at least give a little more info on when and why it's happening.
The rest of the todo list is pretty short - i wouldn't mind implementing #177, and I have a report that when there is a "missing" removable collection in the list, the sort collection window isn't doing what it should.

I saw nothing bad but good. )
Maybe I'll check it more closely this weekend.

Mod Assistant is showing mods needing update but when I goto "find on Modhub" its the same version. When I download I then end up with 2 of the same versions of the mod. Then happens when downloading manually directly from the website or from in game.  Is there something I'm doing wrong??

Mod Assistant is showing mods needing update but when I goto "find on Modhub" its the same version. When I download I then end up with 2 of the same versions of the mod. Then happens when downloading manually directly from the website or from in game. Is there something I'm doing wrong??

Short answer, nope, you are good.
Longer answer - what you are probably running into is that I have to cache those versions from modhub - Giants does not provide any sort of public API to pull the data - and in the interest of being a good internet citizen, I only ask modhub what is new a half dozen times a day (maybe less).  So there is some built in lag there - couple that with the fact that the list of versions only updates in the Mod Assistant when you start it, and you sometimes see a false report like this.  Having tested that specific mod, if you close and reopen Mod Assistant it should be happy with that version again.  If you are curious, you can double click that entry (before you restart), and I suspect that Mod Assistant will tell you that it thinks the newest version is <IP_ADDRESS> - I use a similar check that the game does, and don't really compare if the version you have is older, I just check to see if it's different.

Maybe it will be more convenient/clearer if the “mod processing” window is in the foreground when clearing the cache?

Maybe it will be more convenient/clearer if the “mod processing” window is in the foreground when clearing the cache?

I totally missed this last one on the update.  Yeah, I'll look at fixing the window focus when that pops up - the progress window is actually part of the main window these days, not an overlay (it's a bit more stable this way) - but clicking something like clear cache should indeed focus the main window while it happens.


feat: add OP message prove

Closes: #1899

I looked over this and, similar to Fred, could find only nitpicks and minor stuff. Looks good overall. :+1:
Will leave the final approve to Fred.


Migrate to Swift 3

Hi,
What is the ETA for a Swift 3 version of RxDataSources?
Cheers.

https://github.com/RxSwiftCommunity/RxDataSources/releases/tag/1.0.0.beta.1

Thank you :)


mattermost/mattermost-utilities seems to be corrupted

When running npm install in MatterfossWeb, I get the following error which prevents progress:
npm WARN tarball tarball data for mmjstool<EMAIL_ADDRESS>(sha512-tOQxRIV2NMvoK22EhuL/tm6tV7i1n1qEuY1YL2ic+YmyC8pbEcMKBWf77KDKxjcWIPl0GwX6ud8cocoRBMTw3g==) seems to be corrupted. Trying again.
npm WARN tarball tarball data for mmjstool<EMAIL_ADDRESS>(sha512-tOQxRIV2NMvoK22EhuL/tm6tV7i1n1qEuY1YL2ic+YmyC8pbEcMKBWf77KDKxjcWIPl0GwX6ud8cocoRBMTw3g==) seems to be corrupted. Trying again.
npm ERR! code EINTEGRITY
npm ERR! sha512-tOQxRIV2NMvoK22EhuL/tm6tV7i1n1qEuY1YL2ic+YmyC8pbEcMKBWf77KDKxjcWIPl0GwX6ud8cocoRBMTw3g== integrity checksum failed when using sha512: wanted sha512-tOQxRIV2NMvoK22EhuL/tm6tV7i1n1qEuY1YL2ic+YmyC8pbEcMKBWf77KDKxjcWIPl0GwX6ud8cocoRBMTw3g== but got sha512-S4cjFlwc4y/a+E4u4w+yzKeo+4eOyJcqVQGnUWWvm51RxCZ3tvSM7UImLfziCTPjECY/TL//aRQQ246b4iuxgA==. (687270 bytes)

npm ERR!

The following modules are needed to npm run build, in addition to those in package.json:
body
execa
bin-build
bin-wrapper
imagemin-mozjpeg
exec-buffer

so removing the package-lock.json is not a complete fix.

Looks like the MM has force-pushed their repo and caused this error, I believe I have a build locally which contains the correct version so I can just vendor it.

Hey, any progress on resolving that? Can't build web right now because of that, getting EINTEGRITY despine on package-log.json remove :(


make tables accessible in mobile view.

Notes for Reviewers
This PR fixes #10704
This PR make tables used at various pages of references scrollable.
https://github.com/meshery/meshery/assets/89309144/1c174d14-86b1-4e0c-a035-894ac177ec64
changes made at:
https://docs.meshery.io/reference/rest-apis
https://docs.meshery.io/reference/error-codes
https://docs.meshery.io/reference/mesheryctl
Signed commits

[x] Yes, I signed my commits.

🚀 Preview for commit 70e0b704f7c63932ccd5ae2e3e0fa972f526804a at: https://661c34b000cb3bb092a135bc--meshery-docs-preview.netlify.app

Thankyou for this @Aseem22 checks are failing, also video format if not supported

@Aseem22 Let's discuss this in Meshery dev call today. Add this as an agenda item to the meeting minutes, if you would :)

@Aseem22 Let's discuss this in Meshery dev call today. Add this as an agenda item to the meeting minutes, if you would :)

Thanks @vishalvivekm. This issue has been discussed this monday on website meeting. I recieved some feedback which I am working on currently.

@Aseem22 Let's discuss this in Meshery dev call today. Add this as an agenda item to the meeting minutes, if you would :)

Thanks @vishalvivekm. This issue has been discussed this monday on website meeting. I recieved some feedback which I am working on currently.

@Aseem22
Do you have any updates on the issue ?
let's discuss this on today's website meeting at 5:30 PM IST. I am adding this as an agenda item. Please Join https://meet.layer5.io/websites if you are available during the meet.

PR abandoned.


Docker is only sort of working

Spinning up 2 of each container when running the docker compose, i suspect it is because it auto generates a docker_compose file as well as the one i have created, i will investigate further.

Apparently it has decided to work as expected today so i am closing this issue :P


added friendlier build messages closes #54

This confused me for a few minutes mostly because i had fuse installed but not libfuse-dev this should be a more helpful message to people with this problem.

Linux is not just Ubuntu.  On Fedora the package is fuse-devel, for instance.  This block also covers BSD.
It already knows whether you're on osx or something else, at least, so it doesn't need to offer suggestions for both.

Your comments make sense. Before I change the code some more, I want to make sure you'll be happy with the changes. I made some line comments, let me know what you think.

On OS X I knew I had to install osxfuse but on Ubuntu 15.10 I was confused for a few minutes.
I ended searching the issues on this repo and I was able to figure out that I had to install libfuse-dev.
:+1: for having a more helpful message!

I just played around with build.rs and found that lib probing can be greatly simplified since OSXFUSE also provides fuse.pc. This way, we can use probe_library("fuse") on any platform.
I don't think we should give OS-specific instructions how to install FUSE in build.rs. Ubuntu and Fedora might be common, but there are so many Linux distributions and package names are not standardized. Maybe we should add some more detailed instructions to README.md though.


Can not Forwarding from www to non-www version while using SSL with modcluster

I configured httpd with modcluster and I want to redirect www to non-www version while using SSL but it did not work.
My current configuration work as follow
http://www.qoosi.com => https://qoosi.com ( not work )
http://qoosi.com => https://qoosi.com ( work)
https://www.qoosi.com => https://qoosi.com ( not work)
Here is the configuration for modcluster and a virtual host listen on port 80 to forward from http to https:
<IfModule manager_module>
    Listen <IP_ADDRESS>:6666
    ManagerBalancerName wfycluster
    <VirtualHost <IP_ADDRESS>:6666>
        AllowDisplay On
        ServerAdvertise On
        KeepAliveTimeout 300
        MaxKeepAliveRequests 0
        AdvertiseFrequency 5
        ServerAdvertise On <IP_ADDRESS>:6666
        AdvertiseGroup <IP_ADDRESS>:23364
        EnableMCPMReceive On
        ProxyPassMatch ^/sas/ !

       ProxyPass / balancer://wfycluster stickysession=JSESSIONID|jsessionid nofailover=on
       ProxyPassReverse / balancer://wyfcluster
       ProxyPreserveHost on
#static asset
alias /sas  /var/www/html/sas
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn
SSLEngine on
SSLProtocol all -SSLv2
SSLCipherSuite HIGH:MEDIUM:!aNULL:!MD5:!SEED:!IDEA
SSLCertificateFile /etc/httpd/ssl/qoosi_com.crt
SSLCertificateKeyFile /etc/httpd/ssl/qoosi_com.key
#SSLCertificateChainFile /etc/pki/tls/certs/server-chain.crt
SSLCACertificateFile /etc/httpd/ssl/qoosi_com.ca-bundle
#SSLVerifyClient require
#SSLVerifyDepth  10

<Files ~ "\.(cgi|shtml|phtml|php3?)$">
    SSLOptions +StdEnvVars
</Files>
<Directory "/var/www/cgi-bin">
    SSLOptions +StdEnvVars
</Directory>
BrowserMatch "MSIE [2-5]" \
         nokeepalive ssl-unclean-shutdown \
         downgrade-1.0 force-response-1.0

</VirtualHost>

See http://httpd.apache.org/docs/current/mod/mod_ssl.html#sslproxyengine


Fixed variable naming and file naming

BPM variable which was not defined and was used in case of bpm.
Folder name and file name were not same leading to creation of new file.
To avoid that changed the naming.

@touchhowling thank you for making these changes, I am merging it now.


Scrubber function

Hello!
For example I have 3 series. Is it possible to display tooltip only for 2 of them?

Hmmmm I don't think it's possible currently...

Hey, we're closing this because it's been a while and we're trying to avoid zombie issues. If the problem persists, please open a new issue (and don't forget, your issue is much more likely to be fixed if you provide a working CodePen : easier for us, faster for you !).
Thanks again for helping us making n3-charts awesome.
--
Sébastien & Christoph


buildDepsOnly for #![no_std]

buildDepsOnly creates a blank src/lib.rs with mkDummySrc.  This will fail to compile for #![no_std] targets such as thumbv7em-none-eabi because of the absence of a panic handler.
My workaround is to add sed -i '1s/^/#![no_std]/' src/lib.rs to the top of buildPhaseCargoCommand.  A full example of this is avaliable here.
This works, but I wish it was more elegant:

Should #![no_std] targets be supported in crane?  I am not sure if this is within the scope of crane.
If this is in scope, how should this be implemented?  There are many possible solutions, I would be interested to hear your ideas!

Thanks for the report @newAM ! I believe #126 should address this issue if you are interested in testing it out locally


PT Run Crash

Microsoft PowerToys version
0.37.2
Running as admin

[X] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce
Just tried doing an ALT + Space to open a program.
✔ Expected Behavior
PT Run to appear.
❌ Actual Behavior
Showed the "Something has went wrong" box and has given instructions to upload attached logfile.
2021-06-14.txt
Other Software
No response

Thanks! Tracked by #9619


Add more types of suicides

When a player uses the suicide command it'll do something context sensitive near them (e.g. stick their head in a microwave). Having more types would be nice. The interface to use is ISuicideAct

Would be cool if there was an actual UI thing for suicide. Even typing suicide in the text chat would be better than doing it in the console.

https://www.youtube.com/watch?v=qkIf9M7G3vA


Dependency napari_workflows not specified in requirements or setup.cfg

This seems to depend on https://github.com/haesleinhuepf/napari-workflows by @haesleinhuepf, but when installing the plugin, this dependency is not automatically installed.

Hi @VolkerH ,

This seems to depend on [...] napari-workflows

I don't think so. Can you tell us why you think so? 🙃

I think so because I got an error message that said it was missing and after installing it it worked :)
However, I just reproduced it and the proplem seems to be one level down the dependency chain, namely in napari_tools_menu. Just pretend I opened the issue there.
File ~/miniconda3/envs/spacem-maldi-control/lib/python3.8/site-packages/napari_tools_menu/__init__.py:95, in make_gui.<locals>.worker_func(*iargs=(<Labels layer 'Labels'>, <Shapes layer 'Shapes'>, Viewer(axes=Axes(visible=False, labels=True, col...ings._transform_active_layer at 0x7fee2b218ee0>})), **ikwargs={})
     93 # determine scale of passed data
     94 scale = None
---> 95 from napari_workflows._workflow import _get_layer_from_data
     96 for passed_data in iargs:
     97     layer = _get_layer_from_data(viewer, passed_data)

ModuleNotFoundError: No module named 'napari_workflows'

Ah, I see. Thanks for reporting @VolkerH ! I'll take care of this in napari-tools-menu.


refactor: old course theme removed

Pre-Flight checklist

[ ] Screenshots and design review for any changes that affect layout or styling

[ ] Desktop screenshots
[ ] Mobile width screenshots

[ ] Testing

[ ] Code is tested
[ ] Changes have been manually tested

What are the relevant tickets?
closes https://github.com/mitodl/ocw-hugo-themes/issues/986
What's this PR do?

Removes old course theme

How should this be manually tested?

Checkout this branch
Build any course locally
Verify that the course builds successfully
Now test the course thoroughly and verify that everything is on point
Repeat this for multiple courses

@MAbdurrehman12 👍 Looks good.
Do you also want to delete content_header.html (and keep content_header_v2.html), etc. ? I think that would make sense.

Ahh.. thanks for pointing this out. Will do that


Add WAR for XLA NCCL bug causing OOMs

A stopgap for https://github.com/NVIDIA/JAX-Toolbox/issues/346

The jax ARM build issue still exists. I think it would be preferred to wait for @yhtang's fix for the ARM build before merging this since this should fix many of the CI failures and it would be good to confirm that in the presubmit

If one arch CI pass, I would merge it. This fix stuff, so it is really useful to have it now.
If one arch CI pass, we have a strong enough signal that this small PR is good.
This PR is independent of arch normally.

Triggering manually a full presubmit from jax at an 11/01 commit (last known working nightly was 11/03): https://github.com/NVIDIA/JAX-Toolbox/actions/runs/6801767976

All tests pass except ViT8G2N which is a strict improvement in the CI. We can chase fixing that next.


Live-update the url when parameters are changed

When copying/pasting a shareable url into the browser, and then changing parameters, the url no longer reflects the current state of the screen. It would be a nice enhancement for the url to always reflect the currently selected parameters rather than having to click "Share" to get a new url.
Thanks for this tool; it's amazing!

Hi there I am also developing same application which reflect status I think you need to use the  React Router module  file which we create at assign to update as per given dependances

I can try to solve it


Pretrained model weights missing

Hi @ZhengJun-AI,
Can you provide pretrained model weights?

Sorry, I don't focus on this topic anymore.


Example 3

Example 3 is incorrect, it includes the output of the command.  Instead of :
Set-NAVServerUser DynamicsNAV90 -UserName USER1 -NewUserName USER2 -ChangePasswordAtNextLogOn -Password (Read-Host "Enter password for USER2" -AsSecureString)Enter password for USER2: ************
It should read:
Set-NAVServerUser DynamicsNAV90 -UserName USER1 -NewUserName USER2 -ChangePasswordAtNextLogOn -Password (Read-Host "Enter password for USER2" -AsSecureString)

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

ID: 5681b0a1-cd84-19c8-bd3d-af9f9b1fcf51
Version Independent ID: a93713b8-b619-36d3-5a1d-cac11be91966
Content: Set-NAVServerUser (Microsoft.Dynamics.Nav.Management)
Content Source: businesscentral-ps/Microsoft.Dynamics.Nav.Management/Set-NAVServerUser.md

Thanks for the feedback! The example has been fixed and an update will be published soon.


HighCmd Mode 3: Target Position Walking & Position

Hi. May I know the functionality of this "Target Position Walking" and how it is controlled by "position + ypr[0]"?

Sorry,our current SDK does not support mode3


Enable Sourcegraph

I want to use Sourcegraph for bedrock-ansible code search, browsing, and usage examples. Can an admin enable Sourcegraph for this repository? Just go to https://sourcegraph.com/github.com/roots/bedrock-ansible. (It should only take 30 seconds.)
Thank you!

I figured why not and went through the process. But unfortunately Sourcegraph requires read and write access for hooks and commit statuses. For some reason GitHub also includes that access for my private organizations which for some reason allow 3rd party access (and I don't manage them). For that reason I'm not comfortable giving Sourcegraph access.
Hopefully I'm not mistaken about this:


Add in the ability to bring your own tokenizer

Per your information in the Haystack Discord, using the adapter with an OpenAI compatible endpoint, and saw it could be useful to bring your own tokenizer if necessary.
The code works as is, but a GPTQ model I've been testing uses the transformers library's AutoTokenizer to create a tokenizer specific to the model (in this case, the auto-tokenizer is creating an instance of transformers.models.llama.tokenization_llama_fast.LlamaTokenizerFast). In this particular case, the encode function returns the list of ids as the result of the call, instead of passing back an object with ids as an attribute.
Using Tokenizer.from_pretrained on this model does work, so I'm not married to the PR, but still thought it would be useful. The only bit I'm not particularly thrilled with is line 218, where I'm making a naive assumption that those are the only two scenarios - a list returned natively by the encoder, or an object with the ids attribute.

I see the value in being able to bring your own tokenizer. I chose tokenizers as it powers the "Fast-Tokenizers" of the transformers library, meaning nearly everything on the hub should be be supported. We should only need to pass in a custom tokenizer if the model you use implements a unique tokenizer, which would ship the tokenization code in the same repo as your model.

Alright, LGTM 👍


Load failure for encrypted EPUB3 Navigation Document, Content Filter Chain out of date with late registration of Content Module

Support for encrypted NavDoc was introduced here:
https://github.com/readium/readium-sdk/commit/bdcbdc6d18d83bc50c62ab0c69d0b0e84a3f26e2#diff-db92dd69cdd7ce3a59e70ae293050d98
...but this only works for EPUB Containers/Packages loaded (unpacked) after the Content Filter registration. Unfortunately the LCP Content Module sub-system requires loading of the License which occurs after the EPUB is opened, so the Content Filter registration occurs too late. As a result the Nav Doc cannot be parsed because of its scrambled encrypted byte stream. LibXml does not crash (fails silently).
I am fixing this now (update: fixed, see comment below)
Also see:
https://github.com/readium/readium-sdk/issues/221

Fixed in feature/lsd branch:
https://github.com/readium/readium-sdk/commit/d42485f0577511eb3f745e5a8f60959a9e397c6f

On the client side (LCP content module): https://github.com/readium/readium-lcp-client/commit/d354426021d154aa8d2aaff41e904dcc80bf575d

@mmenu-mantano @jmgeffroy CC-ing you guys as I know you looked into the encrypted NavDoc issue :)

Reminder, fixed in feature/lcp:
https://github.com/readium/readium-sdk/commit/d42485f0577511eb3f745e5a8f60959a9e397c6f
...and recently API slightly changed to address the same problem with Media Overlays (encrypted SMIL files):
https://github.com/readium/readium-sdk/commit/24e004ae197e3bd90a5c5c1e67901810396e7d6e
See related issue:
https://github.com/readium/readium-sdk/issues/272


Permanent freezing of someone's TON in L1CrossDomainMessenger

Describe the bug
We can lock someone's TON in L1CrossDomainMessenger by setting their allowance amount in L1CrossDomainMessenger to 1.
    const sendTx = await (
        await l2CrossDomainMessengerContract
        .connect(l2Wallet)
        .sendMessage(someoneWallet, '0x', 200000, { value: 1 })
    ).wait()

Configuration
Severity: CRITICAL
Impact
Permanent freezing of funds

I think we are discussing the same on https://github.com/tokamak-network/tokamak-thanos/issues/243

@Zena-park if this is an duplicate issue as @nguyenzung mentioned, can you close it? or if you think it is not, leave a comment?

Yes, that's the same thing.
I'll close the issue.


Missing spacy/data/en/en_core_web_md-2.0.0/vocab/lexemes.bin

Rasa NLU version:
rasa-core           0.9.0
rasa-nlu            0.12.3
Operating system :
Linux 16.04
Content of model configuration file:
slots:
  location:
    type: text
  mood:
    type: text
  information:
    type: text
  adjective:
    type: text

# intention the bot is able to recognize from the sentences
intents:
 - greet
 - goodbye
 - inform

# entities he may be able to extract
entities:
 - location
 - mood
 - information
 - adjective

# actions the bot can take
actions:
 - utter_greet
 - utter_goodbye
 - utter_ask_location
 - actions.ActionWeather
 - utter_joy
 - utter_fear
 - utter_anger
 - utter_sadness
 - utter_disgust
 - utter_shame
 - utter_guilt

templates:
  utter_greet:
    - 'Hello! How can I help?'
  utter_goodbye:
    - 'Talk to you later.'
    - 'Bye bye :('
  utter_ask_location:
    - 'In what location?'
  utter_joy:
    - 'Am so happy for you'
  utter_fear:
    - 'you shouldn be afraid'
  utter_anger:
    - 'Calm down, everything gonna be alright'
  utter_sadness:
    - 'be a tough guy'
  utter_disgust:
    - 'I understand, this is disgusting, we should get over it'
  utter_shame:
    - 'Ridicule does not kill'
  utter_guilt:
    - 'You must not feel guilty, feel proud'

Issue:
I try to link the front end developed with Flask to its back end developed with rasa_nlu, which used to work well. Yet, when launching rasa_nlu I get this error:
(MoodEnv) mike@mike-thinks:~/Programing/Rasa/Moodbot$ python run_app.py
Traceback (most recent call last):
  File "run_app.py", line 6, in <module>
    nlu_interpreter = RasaNLUInterpreter('./models/nlu/default/weathernlu')
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/rasa_core/interpreter.py", line 221, in __init__
    self._load_interpreter()
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/rasa_core/interpreter.py", line 237, in _load_interpreter
    self.interpreter = Interpreter.load(self.model_directory)
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/rasa_nlu/model.py", line 276, in load
    skip_validation)
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/rasa_nlu/model.py", line 303, in create
    model_metadata, **context)
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/rasa_nlu/components.py", line 398, in load_component
    cached_component, **context)
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/rasa_nlu/registry.py", line 131, in load_component_by_name
    return component_clz.load(model_dir, metadata, cached_component, **kwargs)
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/rasa_nlu/utils/spacy_utils.py", line 126, in load
    nlp = spacy.load(model_name, parser=False)
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/spacy/__init__.py", line 15, in load
    return util.load_model(name, **overrides)
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/spacy/util.py", line 112, in load_model
    return load_model_from_link(name, **overrides)
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/spacy/util.py", line 129, in load_model_from_link
    return cls.load(**overrides)
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/spacy/data/en/__init__.py", line 12, in load
    return load_model_from_init_py(__file__, **overrides)
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/spacy/util.py", line 173, in load_model_from_init_py
    return load_model_from_path(data_path, meta, **overrides)
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/spacy/util.py", line 156, in load_model_from_path
    return nlp.from_disk(model_path)
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/spacy/language.py", line 653, in from_disk
    util.from_disk(path, deserializers, exclude)
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/spacy/util.py", line 511, in from_disk
    reader(path / key)
  File "/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/spacy/language.py", line 641, in <lambda>
    self.vocab.from_disk(p) and _fix_pretrained_vectors_name(self))),
  File "vocab.pyx", line 377, in spacy.vocab.Vocab.from_disk
  File "/usr/lib/python3.5/pathlib.py", line 1151, in open
    opener=self._opener)
  File "/usr/lib/python3.5/pathlib.py", line 1005, in _opener
    return self._accessor.open(self, flags, mode)
  File "/usr/lib/python3.5/pathlib.py", line 371, in wrapped
    return strfunc(str(pathobj), *args)
FileNotFoundError: [Errno 2] No such file or directory: '/home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/spacy/data/en/en_core_web_md-2.0.0/vocab/lexemes.bin'

Here is the code I run to get it:
from rasa_core.channels import HttpInputChannel
from rasa_core.agent import Agent
from rasa_core.interpreter import RasaNLUInterpreter
from rasa_slack_connector import SlackInput

nlu_interpreter = RasaNLUInterpreter('./models/nlu/default/weathernlu')
agent = Agent.load('./models/dialogue',interpreter = nlu_interpreter)

# With Slack
# https://api.slack.com/apps/AASPDV196/oauth?
#input_channel = SlackInput('OAuth Access Token','Bot User OAuth Access Token', 'Verification Token',True)

#agent.handle_channel(HttpInputChannel(5004,'/',input_channel))

# With inner app
agent.handle_channel(HttpInputChannel(5000,'/',input_channel))

And this even after reinstalling spacy and its language model for the english language.
(MoodEnv) mike@mike-thinks:~/Programing/Rasa/Moodbot$ pip install rasa_nlu[spacy]
Requirement already satisfied: rasa_nlu[spacy] in ./MoodEnv/lib/python3.5/site-packages (0.12.3)
Requirement already satisfied: pyyaml in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (3.12)
Requirement already satisfied: matplotlib in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (1.5.3)
Requirement already satisfied: typing in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (<IP_ADDRESS>)
Requirement already satisfied: tqdm in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (4.11.2)
Requirement already satisfied: numpy>=1.13 in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (1.13.1)
Requirement already satisfied: six in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (1.10.0)
Requirement already satisfied: klein in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (17.2.0)
Requirement already satisfied: packaging in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (17.1)
Requirement already satisfied: gevent in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (1.2.1)
Requirement already satisfied: cloudpickle in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (0.5.3)
Requirement already satisfied: future in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (0.16.0)
Requirement already satisfied: jsonschema in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (2.6.0)
Requirement already satisfied: requests in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (2.14.2)
Requirement already satisfied: boto3 in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (1.4.4)
Requirement already satisfied: pathlib in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (1.0.1)
Requirement already satisfied: simplejson in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (3.11.1)
Requirement already satisfied: scipy; extra == "spacy" in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (1.1.0)
Requirement already satisfied: spacy>2.0; extra == "spacy" in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (2.0.11)
Requirement already satisfied: scikit-learn; extra == "spacy" in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (0.19.1)
Requirement already satisfied: sklearn-crfsuite; extra == "spacy" in ./MoodEnv/lib/python3.5/site-packages (from rasa_nlu[spacy]) (0.3.5)
Requirement already satisfied: pytz in ./MoodEnv/lib/python3.5/site-packages (from matplotlib->rasa_nlu[spacy]) (2018.4)
Requirement already satisfied: cycler in ./MoodEnv/lib/python3.5/site-packages (from matplotlib->rasa_nlu[spacy]) (0.10.0)
Requirement already satisfied: pyparsing!=2.0.0,!=2.0.4,!=2.1.2,>=1.5.6 in ./MoodEnv/lib/python3.5/site-packages (from matplotlib->rasa_nlu[spacy]) (2.2.0)
Requirement already satisfied: python-dateutil in ./MoodEnv/lib/python3.5/site-packages (from matplotlib->rasa_nlu[spacy]) (2.7.3)
Requirement already satisfied: incremental in ./MoodEnv/lib/python3.5/site-packages (from klein->rasa_nlu[spacy]) (17.5.0)
Requirement already satisfied: werkzeug in ./MoodEnv/lib/python3.5/site-packages (from klein->rasa_nlu[spacy]) (0.14.1)
Requirement already satisfied: Twisted>=13.2 in ./MoodEnv/lib/python3.5/site-packages (from klein->rasa_nlu[spacy]) (18.4.0)
Requirement already satisfied: greenlet>=0.4.10 in ./MoodEnv/lib/python3.5/site-packages (from gevent->rasa_nlu[spacy]) (0.4.13)
Requirement already satisfied: botocore<1.6.0,>=1.5.0 in ./MoodEnv/lib/python3.5/site-packages (from boto3->rasa_nlu[spacy]) (1.5.95)
Requirement already satisfied: jmespath<1.0.0,>=0.7.1 in ./MoodEnv/lib/python3.5/site-packages (from boto3->rasa_nlu[spacy]) (0.9.3)
Requirement already satisfied: s3transfer<0.2.0,>=0.1.10 in ./MoodEnv/lib/python3.5/site-packages (from boto3->rasa_nlu[spacy]) (0.1.13)
Requirement already satisfied: murmurhash<0.29,>=0.28 in ./MoodEnv/lib/python3.5/site-packages (from spacy>2.0; extra == "spacy"->rasa_nlu[spacy]) (0.28.0)
Requirement already satisfied: plac<1.0.0,>=0.9.6 in ./MoodEnv/lib/python3.5/site-packages (from spacy>2.0; extra == "spacy"->rasa_nlu[spacy]) (0.9.6)
Requirement already satisfied: preshed<2.0.0,>=1.0.0 in ./MoodEnv/lib/python3.5/site-packages (from spacy>2.0; extra == "spacy"->rasa_nlu[spacy]) (1.0.0)
Requirement already satisfied: cymem<1.32,>=1.30 in ./MoodEnv/lib/python3.5/site-packages (from spacy>2.0; extra == "spacy"->rasa_nlu[spacy]) (1.31.2)
Requirement already satisfied: thinc<6.11.0,>=6.10.1 in ./MoodEnv/lib/python3.5/site-packages (from spacy>2.0; extra == "spacy"->rasa_nlu[spacy]) (6.10.2)
Requirement already satisfied: regex==2017.4.5 in ./MoodEnv/lib/python3.5/site-packages (from spacy>2.0; extra == "spacy"->rasa_nlu[spacy]) (2017.4.5)
Requirement already satisfied: ujson>=1.35 in ./MoodEnv/lib/python3.5/site-packages (from spacy>2.0; extra == "spacy"->rasa_nlu[spacy]) (1.35)
Requirement already satisfied: dill<0.3,>=0.2 in ./MoodEnv/lib/python3.5/site-packages (from spacy>2.0; extra == "spacy"->rasa_nlu[spacy]) (<IP_ADDRESS>)
Requirement already satisfied: python-crfsuite>=0.8.3 in ./MoodEnv/lib/python3.5/site-packages (from sklearn-crfsuite; extra == "spacy"->rasa_nlu[spacy]) (0.9.5)
Requirement already satisfied: tabulate in ./MoodEnv/lib/python3.5/site-packages (from sklearn-crfsuite; extra == "spacy"->rasa_nlu[spacy]) (0.8.2)
Requirement already satisfied: constantly>=15.1 in ./MoodEnv/lib/python3.5/site-packages (from Twisted>=13.2->klein->rasa_nlu[spacy]) (15.1.0)
Requirement already satisfied: Automat>=0.3.0 in ./MoodEnv/lib/python3.5/site-packages (from Twisted>=13.2->klein->rasa_nlu[spacy]) (0.6.0)
Requirement already satisfied: zope.interface>=4.4.2 in ./MoodEnv/lib/python3.5/site-packages (from Twisted>=13.2->klein->rasa_nlu[spacy]) (4.5.0)
Requirement already satisfied: hyperlink>=17.1.1 in ./MoodEnv/lib/python3.5/site-packages (from Twisted>=13.2->klein->rasa_nlu[spacy]) (18.0.0)
Requirement already satisfied: docutils>=0.10 in ./MoodEnv/lib/python3.5/site-packages (from botocore<1.6.0,>=1.5.0->boto3->rasa_nlu[spacy]) (0.14)
Requirement already satisfied: msgpack-numpy==0.4.1 in ./MoodEnv/lib/python3.5/site-packages (from thinc<6.11.0,>=6.10.1->spacy>2.0; extra == "spacy"->rasa_nlu[spacy]) (0.4.1)
Requirement already satisfied: wrapt in ./MoodEnv/lib/python3.5/site-packages (from thinc<6.11.0,>=6.10.1->spacy>2.0; extra == "spacy"->rasa_nlu[spacy]) (1.10.11)
Requirement already satisfied: termcolor in ./MoodEnv/lib/python3.5/site-packages (from thinc<6.11.0,>=6.10.1->spacy>2.0; extra == "spacy"->rasa_nlu[spacy]) (1.1.0)
Requirement already satisfied: msgpack-python in ./MoodEnv/lib/python3.5/site-packages (from thinc<6.11.0,>=6.10.1->spacy>2.0; extra == "spacy"->rasa_nlu[spacy]) (0.5.6)
Requirement already satisfied: cytoolz<0.9,>=0.8 in ./MoodEnv/lib/python3.5/site-packages (from thinc<6.11.0,>=6.10.1->spacy>2.0; extra == "spacy"->rasa_nlu[spacy]) (0.8.2)
Requirement already satisfied: attrs in ./MoodEnv/lib/python3.5/site-packages (from Automat>=0.3.0->Twisted>=13.2->klein->rasa_nlu[spacy]) (18.1.0)
Requirement already satisfied: setuptools in ./MoodEnv/lib/python3.5/site-packages (from zope.interface>=4.4.2->Twisted>=13.2->klein->rasa_nlu[spacy]) (20.7.0)
Requirement already satisfied: idna>=2.5 in ./MoodEnv/lib/python3.5/site-packages (from hyperlink>=17.1.1->Twisted>=13.2->klein->rasa_nlu[spacy]) (2.6)
Requirement already satisfied: toolz>=0.8.0 in ./MoodEnv/lib/python3.5/site-packages (from cytoolz<0.9,>=0.8->thinc<6.11.0,>=6.10.1->spacy>2.0; extra == "spacy"->rasa_nlu[spacy]) (0.9.0)
en-core-web-sm 1.2.0 has requirement spacy<2.0.0,>=1.7.0, but you'll have spacy 2.0.11 which is incompatible.
tensorflow 1.8.0 has requirement numpy>=1.13.3, but you'll have numpy 1.13.1 which is incompatible.
rasa-core 0.9.0 has requirement coloredlogs~=10.0, but you'll have coloredlogs 7.3 which is incompatible.
rasa-core 0.9.0 has requirement ConfigArgParse~=0.13.0, but you'll have configargparse 0.12.0 which is incompatible.
rasa-core 0.9.0 has requirement fakeredis~=0.10.0, but you'll have fakeredis 0.8.2 which is incompatible.
rasa-core 0.9.0 has requirement fbmessenger~=5.0, but you'll have fbmessenger 4.3.1 which is incompatible.
rasa-core 0.9.0 has requirement flask~=1.0, but you'll have flask 0.12 which is incompatible.
rasa-core 0.9.0 has requirement graphviz~=0.8.0, but you'll have graphviz 0.7.1 which is incompatible.
rasa-core 0.9.0 has requirement networkx~=2.0, but you'll have networkx 1.11 which is incompatible.
rasa-core 0.9.0 has requirement requests~=2.15, but you'll have requests 2.14.2 which is incompatible.

(MoodEnv) mike@mike-thinks:~/Programing/Rasa/Moodbot$ python -m spacy download en_core_web_md
Collecting https://github.com/explosion/spacy-models/releases/download/en_core_web_md-2.0.0/en_core_web_md-2.0.0.tar.gz
  Downloading https://github.com/explosion/spacy-models/releases/download/en_core_web_md-2.0.0/en_core_web_md-2.0.0.tar.gz (120.8MB)
    100% |████████████████████████████████| 120.9MB 3.7MB/s
Requirement already satisfied (use --upgrade to upgrade): en-core-web-md==2.0.0 from https://github.com/explosion/spacy-models/releases/download/en_core_web_md-2.0.0/en_core_web_md-2.0.0.tar.gz in ./MoodEnv/lib/python3.5/site-packages

    Linking successful
    /home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/en_core_web_md
    -->
    /home/mike/Programing/Rasa/Moodbot/MoodEnv/lib/python3.5/site-packages/spacy/data/en_core_web_md

    You can now load the model via spacy.load('en_core_web_md')

(MoodEnv) mike@mike-thinks:~/Programing/Rasa/Moodbot$ python -m spacy link en_core_web_md en

    Link 'en' already exists
    To overwrite an existing link, use the --force flag.

Hm I can't see your nlu config file, but looks like you're trying to link en_core_web_md to en, which didn't work because the link already exists. Try running it again with the --force flag


Bug fix/rewrite imports

So, I've made adding the commands a little bit more modular! It's a super neat solution since you can't really do reflection in JS like you can with C#.
The basic format for adding another command would be to create a file with the name of the command such as sad.js and then filling it in with
module.export = {
    name: 'sad',
    description: '',
    respond(cmd, args, socket, client, config, rooms) {
    ....Server Stuff Here....
     }
}

Then when you boot the server up, /sad will work properly. No other configurations will need to be made.
This should be a fix for #4
I'm sure there could be more work done on this, but would like to get an initial look at this solution and get some feedback on it!
Main bread and butter is in protocol.js on lines 148-159

Closing this for now until project picks up speed


Drop rule for in-addr.arpa

Can't see a valid reason for this rule to exist:
/.in-addr.arpa$/              REJECT  Generic - Please relay via ISP

Hi, Quanah. Is there no potential for that string to show up in an EHLO?

Hm, looking at are logs, we get both valid and spam emails that have .in-addr.arpa as part of their address. :/  I.e., the rule itself seems overly broad, as it catches anything with that address space.

Who sends valid email with a poorly configured rDNS PTR?   That's almost insane as few places would easily accept it.

Thanks, guys. I concur this is an overly aggressive rule and have removed it.
Updated version is committed. Closing this thread. :)

I strongly object.   So far zero evidence has been provided to show legitimate email being sent that is blocked by that rule.  We do have evidence, and history, to show that the rule in question blocks SPAM and Viruses.   I find it very disheartening that it was so easy to get a well established rule so easily discarded.

At the risk of sounding cheeky, jimpop, this would have been much more helpful feedback to me than your earlier comment of merely "Who sends valid email with a poorly configured rDNS PTR? That's almost insane as few places would easily accept it." I didn't understand what you were trying to communicate.
I hope you'll be less disheartened that I'm happy to put the rule back in, until such time as legitimate evidence can be provided that it's actually blocking legit email.
I appreciate your insight and input -

We have legitimate emails being blocked by it, as I already stated.  Since we removed the rule, spamhaus has been blocking those ranges where it's actually invalid, which is preferable in our case.  The specific end group that we encounter this with is a security firm (Netragard).
Nov  9 08:31:17 edge02 postfix/smtpd[50403]: NOQUEUE: reject: RCPT from unknown[<IP_ADDRESS>]: 554 5.7.1 <4.0-<IP_ADDRESS>.in-addr.arpa>: Unverified Client host rejected: Generic - Please relay via ISP<EMAIL_ADDRESS><EMAIL_ADDRESS>proto=ESMTP helo=<mail.netragard.com>

in fact, RBLs blocked every in-addr that was invalid before even getting to this rule.  So it was only rejecting valid email.
Nov  9 08:10:35 edge01 postfix/postscreen[6524]: NOQUEUE: reject: RCPT from [<IP_ADDRESS>]:53116: 550 5.7.1 Service unavailable; client [<IP_ADDRESS>] blocked using zen.spamhaus.org<EMAIL_ADDRESS><EMAIL_ADDRESS>proto=ESMTP, helo=<<IP_ADDRESS>.in-addr.arpa>
Nov  9 10:30:33 edge02 postfix/postscreen[19838]: NOQUEUE: reject: RCPT from [<IP_ADDRESS>]:2106: 550 5.7.1 Service unavailable; client [<IP_ADDRESS>] blocked using b.barracudacentral.org<EMAIL_ADDRESS><EMAIL_ADDRESS>proto=ESMTP, helo=<<IP_ADDRESS>.in-addr.arpa>

I'd also note in the case where valid email was being blocked, the helo was correct (mail.netragard.com).  markup ate it though.  Here it is one again in a code block:
Nov  9 08:31:18 edge02 postfix/smtpd[50403]: NOQUEUE: reject: RCPT from unknown[<IP_ADDRESS>]: 554 5.7.1 <4.0-<IP_ADDRESS>.in-addr.arpa>: Unverified Client host rejected: Generic - Please relay via ISP<EMAIL_ADDRESS><EMAIL_ADDRESS>proto=ESMTP helo=<mail.netragard.com>

Those may be legitimate emails, but they are being sent from a misconfigured system(s).   It's not proper to ask everyone else to lower their shields in order to accommodate someone else's  misconfigued system(s).

Those may be legitimate emails, but they are being sent from a misconfigured system(s).

In a perfect world, maybe. However, the system itself may not be misconfigured at all, but they are certainly using network services from someone who doesn't delegate rDNS to the company to setup as they please. This isn't too unusual in my own experience, in fact I've found it to be all too common. Trying to convince your SP to update rDNS can be difficult or sometimes nearly impossible.
Penalizing a company because they happen to end up w/rDNS ending in in-addr.arpa seems like an overly broad stroke to impose on everyone.  I doubt there's any good data to show if a rDNS name ending like this is proven to be more or less spammy than so many other possible names so ultimately it is just a judgement call.
My preference would be that this list not take such a broad stroke in the fight against spam. RBLs help take over for whatever gaps this may leave, but at least those with no rDNS control get a chance while we still get the benefit of all the other rules that remain.

So why is the project called fqrdns.pcre, why not just call it misc.pcre?

As far as I understand fqrdns.pcre is mostly intended to block servers with dynamic and generic rDNS. So /.in-addr.arpa$/ is generic. In my own experience almost every ISP do change rDNS on consumer request. In most cases it is just mail system administrator ignorance. Many of that systems (not all of them) are potential spam and viruses sources due to poor configuration. I'm very sure every generic rDNS should be blocked unless there is a really good reason not to.
As readme says:

If it blocks a sender you know to be legit and from whom you need to receive mail I recommend whitelisting that source instead of removing an expression below as a means to solve the problem.

Why not to create white list for known legitimate servers as part of the fqrdns.pcre project?
Presumable it should be a CIDR table.

@moisseev: A whitelist is beyond the scope of this project, but if you or anyone else wants to start one here on Github, I'm more than happy to link to it from the README as as complementary project. :)

Just so I can keep track (and by saying this, I'm not saying it's a democracy... I'm just trying to see where everyone is coming from), @quanah & @plobbes believe this entry should be removed, while @jimpop-at-gmail-dot-com & @moisseev believe it should stay. After discussing and considering, have any of you been swayed the other way?
I'm wondering if it might be useful to also start/move this discussion on the Postfix users list, or perhaps even better, make a post over there inviting others who wish to chime in to do so here.
My general hope for this file is for it to continue in the same spirit as when Stan Hoeppner originally started it, where the rules lean conservative, while more aggressive blocking (or more liberal whitelisting) can be handled individually by the mail admin after-the-fact.

My opinion is the same.  The rule is necessary, and in-line with the project's goal.  Further, it is far easier for 1 or 2 people to remove the rule, rather than requiring 4000 or 5000 other users to add the rule after they download an updated version of fqrdns.pcre.

Received this feedback via email from Noel Jones of the Postfix Users list:

The greatest feature of fqrdns.pcre is its goal of zero false
positives.  Don't break that.  Remember, you're deciding for
everyone what what mail they won't receive.  Individual users are
still free to add their own stricter rules.

Generalized rules that aren't known 100% safe should be avoided.  At
the time in-addr.arpa PTR was added to the list, there were no known
ISPs using those for legit hosts.  Now there are, so it's reasonable
to remove that entry. As an alternative, a "38.in-addr.arpa DUNNO"
whitelist entry might be sufficient for now, but removing the
offending rule completely is the safe course.  Again, individual
users are free to be more strict with their local rules.

The "zero false positive" thought process would basically invalidate any and all of the rules.  Any and everybody can come up with an excuse to show how a rule causes them some inconvenience.

So I guess the question boils down to: is this rule doing more harm than good?
And what are the chances that a system that gets "caught" by this line wouldn't have been caught by something else (RBL, normally-used Postfix restrictions, etc.)?
The goal of zero false positives will likely never be reached by anything, but it's still the ideal for which to strive.
It's clear we're not going to reach consensus. I'm just looking for more people to chime in. Real world data and examples carry more weight in my mind vs. "what if" scenarios.

Just don't forget that DNSBLs are after-the-fact (aka after some spam has started spewing), whereas NXDOMAIN and fqrdns.pcre are before the spew can begin.

I don't want perfection to be the enemy of the good. We'll never achieve perfection, but that doesn't mean we shouldn't try for good.
I think the best approach, which is in-line with the original intent of the project, will always be the most conservative one, then allow individual admins to add their own more restrictive rules, based on their needs.
I haven't made a decision yet, but I will say that I'm inclined to believe the argument that when Stan originally added in-addr.arpa PTR to this list, there were no known ISPs using those for legitimate hosts. I'm also inclined to believe that's no longer the case, which is a believable argument for removal from a list whose primary purpose is supposed to be avoiding false positives, even at the cost of allowing a few more things through to be dealt with by other means in subsequent steps.
If the ./in-addr.arpa$/ is removed from the file, that isn't the same as whitelisting those hosts. That doesn't mean mail from those systems will automatically get through. It simply means that they won't automatically be blocked.
I've asked for real-world examples, not hypothesis. So far, I've only seen log file examples of valid mail that was being blocked by this rule. I haven't seen examples of invalid mail that have been allowed by this rule -- and that wouldn't have also been blocked by standard Postfix best practices.
I'd love to see some examples of that, if any of you have them.
I accept that the original README says:

If it blocks a sender you know to be legit and from whom you need to receive mail I recommend whitelisting that source instead of removing an expression below as a means to solve the problem.

But "a sender you know to be legit and from whom you need to receive mail " is different than "multiple senders that could be legit and from whom you might receive mail," particularly when things have changed since the origin of the file so that in-addr.arpa hosts now might be valid.
So if you have real-world examples of invalid in-addr.arpa mail that wouldn't be stopped by basic Postfix preventative measures, for which the fqrdns.pcre file would have been your only reasonable hope, now is the time to share them. :)

This is really getting out of hand.  in-addr.arpa is generic, fqrdns.pcre exists to block generic.  Competent MTA admins know how to properly accept and deliver email without opening holes in their process.
I've tired of explaining the above, so I'll just avoid fqrdns.pcre updates because apparently it's easier to get a rule removed than it is to explain what a generic addr is.

@jimpop-at-gmail-dot-com I've tried to be polite to you, and listen to all inputs (including yours) before making a decision. You came out of the gates with a rude and dismissive tone, and don't seem to have backed down from it.
"Getting out of hand" seems a tad excessive. Stan had the "benefit" of being able to make changes to the file without version history, and would have simply pushed out changes as he saw fit. When I volunteered to take this over, I put it here on GitHub so the process would be more open, and therefore I'm voluntarily open to more scrutiny in my stewardship of the list.
I'm also tired of you explaining the above.. but only because of your insulting tone, and not your expertise -- which I value, as I do that of any others who are generous enough to share it here.

@jimpop-at-gmail-dot-com: Additionally, as I try to look past your complaints to the content of comments, I note that you didn't provide what I asked for, which is real-world examples of situations where removing this line would be detrimental, rather than esoteric and hypothetical scenarios. I've given you a path to get what you want. I don't understand why you're not taking it.

I would think, likely keeping the list as is, and splitting into 3 new ones, this being a combination of the 3, and the 3 other ones based on how likely false positives are to result, would be a good idea, and let people opt themselves how risky to be. As there really is no right choice to be made.
Given the results on my system, I get the following:
269 Blocked via RBL's
1 Blocked due to invalid ptr name (not valid dns name, invalid chars in name, not blocked from this rule, false positive)
6 Blocked due to pipelining
3 Blocked due to invalid from address
1173 Blocked due to this rule, 6 of them cause the dns server is missing the . on the end, but all still spam.
These are the results based on the last year of the company mailserver, and the last 3 months of my personal server.

@patrickdk77 First, thank you for taking the time to dig in your log files to produce some data.
Second, just to confirm, you saw only one false positive from this rule out of 1452 connections? Any rough idea of how many of those 1,173 would have been snagged by other methods?
One false positive out of that many connections really isn't a lot. Very helpful info.
Your idea about splitting the list into a Goldilocks-style approach (Baby Bear, Mama Bear, Papa Bear) with varying levels of risk is an interesting one. What criteria would you propose for determining what types of rules belong on which list? What type of performance penalty would occur if Postfix had to evaluate three PCRE files vs. only one?

No, the 1 false positive was not cause of this rule, but could have
been, It was blocked by other rules, before it hit this list.
It was blocked cause the dns ptr named contained a / char in it.
N/A.xxx.xxx.in-addr.arpa
Quoting Steve Jenkins<EMAIL_ADDRESS>
@patrickdk77 First, thank you for taking the time to dig in your log
files to produce some data.
Second, just to confirm, you saw only one false positive from this
rule out of 1452 connections? Any rough idea of how many of those
1,173 would have been snagged by other methods?
One false positive out of that many connections really isn't a lot.
Very helpful info.
Your idea about splitting the list into a Goldilocks-style approach
(Baby Bear, Mama Bear, Papa Bear) with varying levels of risk is an
interesting one. What criteria would you propose for determining
what types of rules belong on which list? What type of performance
penalty would occur if Postfix had to evaluate three PCRE files vs.
only one?

Reply to this email directly or view it on GitHub:
https://github.com/stevejenkins/hardwarefreak.com-fqrdns.pcre/issues/4#issuecomment-157063496

Ahhh... ok. So there's no evidence in your log files that you blocked any valid mail as a result of this rule being in the file.

Yes, based on my results, all 1173 where NOT snagged by other rules, as I filtered those out above, 1452 total attempts would match this rule, but only 1173 made it to this rule.
The 1 false positive, would have been snagged by this rule, BUT it also matched other rules before it got this far.
Sorry, just reading this on the website now, the email ticket update I got seemed to truncated the question, and I didn't see all of it.
As far as the issues that could happen with multible lists, I see no issues, yes there will be more effect to process 3 vs 1, but not much, just open/read commands. If people do it like I do atleast, I have an update script that collects the rules, sanity checks them, and compiles them into 1 or a few files, to get published to my servers. So the effect for me, would be 0, as I would be preprocessing them.
The real slowdown is how many regex lines have to be evaluated, I imaging using IF clauses to exclude large sets of regex lines will cause much more benefit. But I have to double check, if this is valid in these maps, and not specific to header checks.

There already are a couple of IF statements in the PCRE file, though they're pretty simple. It first checks to see if certain key words (like dynamic) appear, and if they do, it checks against that subset. If not, it checks against the manually entered hosts in the bottom half of the file.

As an update, I am considering the idea of expanding this project into three separate PCRE files:a primary fqrdns.pcre file (that leans heavily toward avoiding false positives), a fqrdns-plus.pcre file that contains rules that would be deemed "slightly" more aggressive and that have been migrated from the primary file (such as the iana rule under discussion here) that is wanted by some but not by others, and a fqrdns-max.pcre file that contains far more general rules that seek to block the vast majority of dynamic hosts.
To tinker with this idea, I've created a "develop" branch of this project and populated it with a first draft of what such files might look like. Again, this is an experiment, but one in which I welcome polite and thoughtful feedback.

New three-file approach has been running fine for over 18 months, so I've merged it to the master branch.


Split engine subsystems into modules

Closes #4.
Also fixes a few shutdown crashes and adds some QoL thingies.

This ain't done yet, build scripts need updating.


Authentic Falls over to 404 Not Found when "install" is clicked on package installer

I have an issue that seems to only be with Authentic Theme.  Whenever I try to install a package from Apt using the Software Packages Installer, (Pic1) I get a 404 NOT FOUND (Pic3) error after pressing install on the file list (Pic2)

If I change the theme back to the old webmin theme the package will install without fault.  I've re-installed my server to try to correct this issue with no luck.  Can you help me with this?
Server is a HP DL160 G6 with 32Gb RAM
OS is Ubuntu Server 18.04.2 LTS
Authentic Theme is 19.34 Beta4

Hi,
There was a bug in this regard in Webmin version 1.900.
Please update to the latest Webmin version 1.910.

Okay, it's fixed now on the latest dev version.
Please update.

It's was the theme bug, that disrespected redirects from progressive output. It was introduced due to making browser history work with progressive pages. It was very very tricky part to implement correctly.
Sorry about that.
We will release new theme version in few days and new Webmin version to address this and few other ongoing issues.

:)
Looking forward to seeing it fixed.  Thanks for your time.
Ian
------ Original Message ------
From: "Ilia Rostovtsev"<EMAIL_ADDRESS>To: "authentic-theme/authentic-theme"
<EMAIL_ADDRESS>Cc: "Gizepi64"<EMAIL_ADDRESS>"Author"
<EMAIL_ADDRESS>Sent: 19/05/2019 12:15:53
Subject: Re: [authentic-theme/authentic-theme] Authentic Falls over to
404 Not Found when "install" is clicked on package installer (#1346)

Okay, it's fixed now on the latest dev version.
Please update.

It's was the theme bug, that disrespected redirects from progressive
output. It was introduced due to making browser history work with
progressive pages. It was very very tricky part to implement correctly.
Sorry about that.
We will release new theme version in few days and new Webmin version to
address this and few other ongoing issues.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/authentic-theme/authentic-theme/issues/1346?email_source=notifications&email_token=AB6OOPMGVNFJTIJBLTS5IK3PWEZGTA5CNFSM4HNQJC5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVW77JQ#issuecomment-493748134,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB6OOPOLJ2QSGVAUMRY24WLPWEZGTANCNFSM4HNQJC5A.

Ian, you can already update it to latest development version, using theme configuration.


Versioning the docs per release

We should consider how to implement versioned docs (that is, release documentation in sync with Atmo / SCN releases). While making documentation versions for all (earlier) releases is certainly important and useful for many reasons, it comes with a couple important pitfalls that need to be mitigated. A few of these:

Search engine index de-sync (people arriving at earlier versions of the docs when searching for something)
Atmo + SCN versioning needs (what should be the version in e.g. the URL, sync version numbers across Atmo / SCN, how to refer to a specific release etc.)

Alternatively, we can consider tracking breaking changes to functionality (e.g. language support, Runnable API features etc.) in the docs until a consistent versioning is established (e.g. at 1.0).

Docusaurus's built in versioning support

At today's dev meeting, we decided to move forward with versioning the docs. I think I'd like pair with someone to get started on this since I don't have prior experience instantiating versioning.

I'm afraid the issue is less on the documentation side here, but more on the dev side (and particularly on Reactr's side).
The main issue is that we don't have a common agreed-upon and documented versioning strategy, afact! Such versioning strategy should talk about how are various things (such as Reactr, the Runnable APIs in Reactr, public facing interfaces and APIs of Atmo, Sat, SCN's APIs) are versioned, what dependencies exist in-between, how often are new versions released, what constitutes to breaking changes and more.
Once we have this information, we may start versioning the docs - either on their own, layering on a versioning scheme that then is linked to all these tool versions (e.g. Docs 1.0.3 - updates related to Reactr 15, SCN 3.4, dis and dat...). Or we can just pin the docs to a given tool version.
These cross-references and pinning is important because we want the docs - the APIs, the guides, the code snippets - to correlate with the actual tool versions and ensure that they work. Then, when (inevitably) a backwards-incompatible change is made to these tools, we:

want to be able to update the documentation, examples, code snippets etc. so that they work with the new version
if possible we want to keep the older documentation versions accessible so those, who are still using the older versions of these tools can still access them

From today's dev rel meeting notes:

Oscar: lots of feelings
- Moving docs into into their own repo made tracking docs-up-to-date-ness harder
- Release cadence is going to be hard!
- Me & Connor has slightly different ideas
- Want to release early and often esp. for OSS
Oscar: everything is, and will be semver!
Connor:

maybe we will be able to release on schedule (OSS) but we are not there yet
we’ll try to do timeline estimates

Being really transparent about the timeline, even if it can change

Jess: the planning should be visible
Oscar: we have a running log!
Flaki: using the running logs as fodder for content!

more comms between dev ↔ devrel here

Flaki: do you have documentation on the versioning and interactions between the projects?

Oscar:

Planning to keep these fairly independent
Sometimes (e.g. security updates)

Connor:

It’s not worth putting in the effort into versioning until General Availability

Hopefully this year for Reactr + Atmo


refinements to --list-workloads

If a user types nb --list-workloads <path>, then they should get a list of workloads contained in the path. If the path is a found directory, it should include all workloads within the directory. If the path is a workload file, then it should only include that workload's scenarios in its output.
We may also want to square up the terms between workloads and named scenarios.
Presently, when a user types --list-workloads, they see a list of workloads and scenarios, when they are really interested in the scenarios.
Is there a good case to have --list-workloads and --list-scenarios?

Actually, today --list-workloads only shows workloads that have scenarios.

Yes, but isn't the intent by the user in this case to see the scenarios in the workloads specifically?

I've added a --list-scenarios that takes on the responsibility above, and refined the output to be easier to read. Additionally, --list-workloads now just gives a simple list.


add breadcrumbs

above the h1 add a component with the current breadcrump path to the page.

most likely this can be handled with the data provided to Layout already


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-22-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1159

Questions ?
Please refer to the Backport tool documentation


A research for generating PR checklists in Pull Request Template

Dear maintainers:
Our team is currently developing a tool for automatically generating PR checklists in Pull Request Template. The tool generates a set of PR rules based on the contribution guidelines in your project, which external contributors may be expected to adhere to. Below are the results of our generation:
Test: Require tests, changes with tests are prioritized.
Documentation: Enhance documentation.
Style: Not strict rules.
Branch: Rebase on the default branch.
Title: Provide a clear and descriptive title.
Description: Detail to reproduce the problem
Commit Message: Limited, imperative mood.
Contributing: Refer to the provided Code of Conduct for guidance.
We hope you and your team can provide feedback on our generated output.
Best regards.

Oh.mm! This is a good work. I will inform other members to add the checklist in our work.

I’m really confused here. @Kazaf123, you aren’t involved with the project, for one.
@baishuotong the text you’ve provided aren’t really rules in a programmatic sense, and some of them are just wrong - style, for example, is incredibly strict and critical.


cardano-node.exe: user error (open: IO error: Failed to create dir: [...]

Hi,
I use Windows 10 64-bit and I've propably found a bug in the Daedalus Wallet. I have stucked on "Connecting to network" screen and going through logs, in cardano-node.log file, I spotted line:
cardano-node.exe: user error (open: IO error: Failed to create dir: cardano-node.exe: user error (open: IO error: Failed to create dir: C:\Users\Pawe�\AppData\Roaming\Daedalus\DB-1.0\blocks\index: No such file or directory)
I've tried running the wallet with administrator rights but it did not help. After looking for similar problems online I found out that this may be due to non-ascii characters in path (user folder name). After renaming the user folder the application started to work normally (I've got connected, syncing started, etc.). So I guess that this could be related to improper handling of unicode characters.

yup you are right :) just tested it myself

cc @fersel

thanks, we have an issue for that. Will be fixed in one of the nearest updates.


retun epty webpage

Hi brother, I just clone and run your project and it returns an empty page!
I like to learn your project would give me some detail of your project

Can you see any console errors?
On Sat, Nov 28, 2020 at 8:05 PM 5sfayas<EMAIL_ADDRESS>wrote:

[image: Screenshot from 2020-11-28 20-34-32]
https://user-images.githubusercontent.com/31242580/100518701-28e8fa80-31b9-11eb-9e90-597d928d4154.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/naveedaheer/Sale-Purchase-Stock-Inventory-App-in-React/issues/1#issuecomment-735241818,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEJRRSL7IVE7TL3K4FLCPKDSSEGSDANCNFSM4UF26TLQ
.

It returned the login page and but not allowing me to go!
need to learn reducer and increaser interact for point of sale any suggestion could you give me


lake: could not materialize package

While working on mathlib branch bump/nightly-2024-09-11 (see https://github.com/leanprover-community/mathlib4/pull/16716) we used the new Reservoir dependency syntax, but received the error message:
$ lake update LeanSearchClient
error: leanprover-community/LeanSearchClient: could not materialize package: dependency has no explicit source and was not found on Reservoir

This error is both going to be reasonably common (whenever someone doesn't understand how reservoir works), and is not actionable.
Could we please add:
"

To see why it is not on Reservoir, visit https://...
If you did not intend to use Reservoir, and the dependency is available on GitHub, please replace your require line with

require foo from git "https://github.com/org/repo" @ hash

or otherwise with the https URL for the git repository of this package.
"

If the first bullet point is complicated to implement, we should implement the 2nd and 3rd bullet points in the meantime.
We could do even more here:

explain why it is not on reservoir?
check if it is on github and then be more specific in the help

@jcommelin, I took the liberty of rewriting. :-)

As an aside, in regards to this particular error, note that a package can use both an explicit source (i.e., from git) and still provide a Reservoir require. For example:
require "leanprover-community" / "LeanSearchClient"
  from git "https://github.com/leanprover-community/LeanSearchClient.git" @ "main"


Support SDK container builds from worker

Description
SDK container builds are a nice feature of .NET (starting from .NET 7) that lets you get rid of a Dockerfile. The worker should support this approach and provide productive defaults.
The Web SDK does this today: https://github.com/dotnet/sdk/blob/df20c62f59589aec18ae09ff01754e5d97efe59a/src/WebSdk/Publish/Targets/Microsoft.NET.Sdk.Publish.props#L14-L16
We should ensure the same occurs for isolated worker projects by including the same from worker SDK builds (when TFM >= net7.0).
Our props/target should also include the right default ContainerBaseImage, etc. See @baronfel's gist: https://gist.github.com/baronfel/e97f46933d05365ea93d7855af742e58
Note that I think it is generally preferred these days that _TargetFrameworkVersionWithoutV be replaced with $(TargetFrameworkVersion.TrimStart('vV')) or other MSBuild built-ins for versioning.
This work has general benefits but is also needed for .NET Aspire work.

I had some success just playing around with using the following for constructing the tag portion:
<ContainerBaseImage>mcr.microsoft.com/azure-functions/dotnet-isolated:$(AzureFunctionsVersion.TrimStart('vV'))-dotnet-isolated$(TargetFramework.TrimStart('net'))</ContainerBaseImage>

https://github.com/Azure/azure-functions-dotnet-worker/issues/2641 is related and should be addressed before or as part of any work here. Acceptance criteria for this item should include builds from Linux.

Update: This should not be gated on #2641. Based on initial investigation there, it seems like this work would help. However, we should still ensure test coverage from both Windows and Linux.

This was fixed in https://github.com/Azure/azure-functions-dotnet-worker/pull/2671, which for some reason did not auto-close this even though they were linked...