Fancy Zones not snap the windows.

The Fancy zones let me configure or select the windows distribution but, at the moment to drag the windows, Nothing happens.
No matter the pre-defined or personalized configuration that I made.
I've disabled all antivirus configuration, more than anything I've done, I have no one antivirus installed.
Please, I appreciate your help a lot.

ℹ Computer information

PowerToys version:
PowerToy Utility:
Running PowerToys as Admin:
Windows build number: [run "winver"]

📝 Provide detailed reproduction steps (if any)

…
…
…

✔ Expected result
What is the expected result of the above steps?
❌ Actual result
What is the actual result of the above steps?
📷 Screenshots
Are there any useful screenshots? WinKey+Shift+S and then just paste them directly into the form

@camilosebas
check if the option "Allow zones to span across monitors" is ON, if it is, turn it off.

Thank your for your response.
Yes this option is active.
[image: image.png]
➡*  When I first shift then drag the window, this gets frozen. Then I
release the mouse, and the window repeats the movement that I made in the
dragging action. *
Do you know how to solve this?
"Help Me, Obi-Wan Kenobi. You're My Only Hope"
El mar., 8 sept. 2020 a las 1:25, Enrico Giordani<EMAIL_ADDRESS>escribió:

@camilosebas https://github.com/camilosebas
check if the option "Allow zones to span across monitors" is ON, if it is,
turn it off.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/6340#issuecomment-688645557,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACAIINHNQQKGGG3J44EF3K3SEXE43ANCNFSM4QVZAMWA
.

--
Atentamente: Camilo Monsalve.com http://www.camilomonsalve.com[image:
Youtube_01.gif] https://www.youtube.com/camilosebas[image:
Facebook_02.gif] https://www.facebook.com/camilomonsalve3D/[image:
Twitter_03.gif] https://twitter.com/camilosebasCel: +57 318 375 77 97

@camilosebas
turn off the "Allow zones to span across monitors" option until we release a fix for it.
The bug is tracked in https://github.com/microsoft/PowerToys/issues/6302

Once I opened the program to check the checkbox, it was already in off mode.
Just for testing, I turn on the checkbox, and I did tests with the notepad
window, without any changes.
I share with you a screenshot.
[image: image.png]
El mar., 8 sept. 2020 a las 9:36, Enrico Giordani<EMAIL_ADDRESS>escribió:

@camilosebas https://github.com/camilosebas
turn off the "Allow zones to span across monitors" option until we release
a fix for it.
The bug is tracked in #6302
https://github.com/microsoft/PowerToys/issues/6302
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/6340#issuecomment-688920436,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACAIINGWLG6UKEWBRV7YWRTSEY6PTANCNFSM4QVZAMWA
.

--
Atentamente: Camilo Monsalve.com http://www.camilomonsalve.com[image:
Youtube_01.gif] https://www.youtube.com/camilosebas[image:
Facebook_02.gif] https://www.facebook.com/camilomonsalve3D/[image:
Twitter_03.gif] https://twitter.com/camilosebasCel: +57 318 375 77 97


RDK-42993 - [RDKE]

RDKServices: Avoid using script/system commands using system functions RDCentral - Helpers - Replace System

Closing this PR since it's on sprint. We will replace it currently only on RDK-E branch.


Rate limiting by IPv6 block

Hello,
First of all, thank you for a great library that helps rate-limiting the number of requests.
Secondly, I'm having an issue with IPv6 addresses. As you might know that a simple /64 block assigned to customer contains millions of IP addresses and simple rate_limit * {remote.ip} 1r/m just doesn't work as that customer could just use another IPv6 address from his own block.
Do you have any suggestions or maybe some kind of a feature might be implemented to solve rate-limiting for the IPv6 by blocks as well?
Thanks!

Hi @divine, glad to hear that this library helps you ;)
In order to rate-limit requests by IPv6 blocks (or more generally, CIDR blocks), the only solution I can come up with is to use the prefix of the IP address for rate-limiting.
For example, for a /64 block, we can use the first 64 bits of the IP as the actual key, by applying a converter cidr_prefix (with an extra parameter 64) to {remote.ip}:
localhost:8080 {
    route /foo {
        rate_limit {remote.ip}|cidr_prefix:64 2r/m

        respond 200
    }
}

While the syntax becomes a little bit more complicated, I think the format of <key>[|<converter>] may be more versatile for other possible conversions.
Any suggestions?

Hello,
Thank you so much for your kind response.
I do like the IPv6 address and trying to use it whenever possible but without rate-limiting, people are trying to abuse the API that we're providing for free.
This looks fine but what about IPv4 addresses? I mean cidr_prefix_v6:64 should be better in terms of separating the two?
Also, this module actually needs a configuration of the white list of trusted proxies, otherwise, this block of code allows bypassing any limitation:
https://github.com/RussellLuo/caddy-ext/blob/dff396f18e757d1a522ae1162bbcf73083f50d3f/ratelimit/ratelimit.go#L193-L195
You get an idea, right? Anyone could just provide a fake X-Forwarded-For header and this module will think that it's another IP address...
Thanks!

This looks fine but what about IPv4 addresses? I mean cidr_prefix_v6:64 should be better in terms of separating the two?

If cidr_prefix is designed to just apply a CIDR mask of leading bits to an IP (like IP.Prefix), it may be agnostic of IP version (IPv4 or IPv6)?

Anyone could just provide a fake X-Forwarded-For header and this module will think that it's another IP address...

Yes, this is the case.

Also, this module actually needs a configuration of the white list of trusted proxies.

I agree that this is a feasible solution, but I'm a little concerned about the increased  responsibility of ratelimit, which should be focused on rate-limiting. I think "configuration of trusted proxies (or trusted addresses)" should be the responsibility of other Caddy module, much like the ngx_http_realip_module module in Nginx.

If cidr_prefix is designed to just apply a CIDR mask of leading bits to an IP (like IP.Prefix), it may be agnostic of IP version (IPv4 or IPv6)?

This is indeed fine but what will happen if I wanted cidr_prefix:64 for IPv6 and cidr_prefix:24 for IPv4, so you'll need to split configurations I think... otherwise the same configuration might be applied to both versions...

I agree that this is a feasible solution, but I'm a little concerned about the increased responsibility of ratelimit, which should be focused on rate-limiting. I think "configuration of trusted proxies (or trusted addresses)" should be the responsibility of other Caddy module, much like the ngx_http_realip_module module in Nginx.

Looks good, does that mean you'll remove that line of code that detects IP addresses from X-Forwarded-For header?
Thanks!

... if I wanted cidr_prefix:64 for IPv6 and cidr_prefix:24 for IPv4

If ratelimit has a matcher, will it be helpful for your use case? For example:
localhost:8080 {
    route /foo {
        @ipv4 {
            remote_ip <IP_ADDRESS>/24  # possible IPv4 addresses or ranges
        }
        rate_limit @ipv4 {remote.host_prefix.24} 2r/m

        @ipv6 {
            remote_ip 2001:db8::1/64  # possible IPv6 addresses or ranges
        }
        rate_limit @ipv6 {remote.host_prefix.64} 2r/m

        respond 200
    }
}

does that mean you'll remove that line of code that detects IP addresses from X-Forwarded-For header?

I find that the builtin placeholder {http.request.remote.host} is just request.RemoteAddr, so you can use it in your case. And I want to keep the {remote.ip} aware of the X-Forwarded-For header for other use cases.
After some more thought, I also think <key>[|<converter>] is complicated. For simplicity, we can just support more keys as below:

{remote.host}  # Existing (X-Forwarded-For unaware)
{remote.host_prefix.<bits >}  # Newly added
{remote.ip}  # Existing (X-Forwarded-For aware)
{remote.ip_prefix.<bits >}  # Newly added

Hello,
Sorry for the late response.

If ratelimit has a matcher, will it be helpful for your use case?

Actually, no and let me explain why.
I'll just be using only one global prefix as a rate limiter : rate_limit {remote.host_prefix.64} 2r/m. No exceptions for all addresses.
After thinking a little bit, maybe it will work if I add all <IP_ADDRESS>/0.
Objections I had it was what if I want to rate-limit global /64 prefix for IPv6 and global /24 prefix for IPv4 what will happen?
I'm seeing a lot of proxies from the same /24 network prefix as well, they look same and it's definitely bots that might create issues later (an example):
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
...
and etc.
Thanks!

Sorry for the late response.

Never mind ;)

I'll just be using only one global prefix as a rate limiter : rate_limit {remote.host_prefix.64} 2r/m. No exceptions for all addresses.
...
Objections I had it was what if I want to rate-limit global /64 prefix for IPv6 and global /24 prefix for IPv4 what will happen?

Suppose that we already have two different keys, say, as below:

{remote.host_v4_prefix.<bits>}
{remote.host_v6_prefix.<bits>}

I'm not sure how to leverage these keys to apply rate-limiting by using only one rate_limit handler, which allows only one <key>. Do you have any ideas?

Hello,
Using different keys will be fine as well, I just wanted to say that one key wasn't enough, otherwise looks good :)
Thank you!

By "using different keys will be fine", do you mean that you will use two rate_limit handlers (one for IPv4, and the other for IPv6)?
It will be very helpful if you can share me the complete Caddyfile configuration in your mind :) Thanks!

If i understand your case correctly, I think the follow configuration should work:
{
  auto_https off
}

:80 {
  route /foo {
    @ipv4 {
      remote_ip <IP_ADDRESS>/0  # All IPv4 addresses
    }
    # Only apply the following limit if it's an IPv4 address.
    rate_limit @ipv4 {remote.host_prefix.24} 1r/m

    @ipv6 {
      remote_ip ::/0  # All IPv6 addresses
    }
    # Only apply the following limit if it's an IPv6 address.
    rate_limit @ipv6 {remote.host_prefix.64} 2r/m

    respond 200
  }
}

This is the result I got on my Mac:
# IPv4 case (1r/m)
$ curl -w "%{http_code}" 'http://localhost/foo'
200
$ curl -w "%{http_code}" 'http://localhost/foo'
429

# IPv6 case (2r/m)
$ curl -g -6 -w "%{http_code}" 'http://[::1]/foo'
200
$ curl -g -6 -w "%{http_code}" 'http://[::1]/foo'
200
$ curl -g -6 -w "%{http_code}" 'http://[::1]/foo'
429

And the corresponding DEBUG logs (for the above two 429s):
DEBUG   http.handlers.rate_limit        request is rejected     {"variable": "{remote.host_prefix.24}", "value": "<IP_ADDRESS>/24"}
DEBUG   http.handlers.rate_limit        request is rejected     {"variable": "{remote.host_prefix.64}", "value": "::/64"}

Hello,
I just wanted to say thank you, it was quite fast with adding that feature.
I have currently deployed with your example configuration and it works like a charm.
The only question I have what if I want to white list some IPv4 adress block like <IP_ADDRESS>/24 (no limits at all)
would another configuration override the global remote_ip <IP_ADDRESS>/0?
{
  auto_https off
}

:80 {
  route /foo {
    @ipv4 {
      remote_ip <IP_ADDRESS>/0  # All IPv4 addresses
    }

    @ipv4local {
      remote_ip <IP_ADDRESS>/24  # Local network IPv4 addresses
    }

    # Only apply the following limit if it's an IPv4 address.
    rate_limit @ipv4 {remote.host_prefix.24} 1r/m

    # Apply no limits?
    rate_limit @ipv4local {remote.host_prefix.24} ??

    @ipv6 {
      remote_ip ::/0  # All IPv6 addresses
    }
    # Only apply the following limit if it's an IPv6 address.
    rate_limit @ipv6 {remote.host_prefix.64} 2r/m

    respond 200
  }
}

Thanks!

Caddy supports a not matcher, you can try this configuration for IPv4 case:
@ipv4 not remote_ip <IP_ADDRESS>/24  # All IPv4 addresses except local network
rate_limit @ipv4 {remote.host_prefix.24} 1r/m

Hello,
I do really appreciate your help, this works like a charm!
Enabled IPv6 back and deployed to production for a few million of users.
Thank you so much!

Hello,
Sorry for reopening this again but looks like somebody was able to bypass remote.host_prefix and looking at documentation https://caddyserver.com/docs/modules/http.matchers.remote_host this is definitely possible.

http.matchers.remote_host matches based on the remote IP of the connection. A host name can be specified, whose A and AAAA DNS records will be resolved to a corresponding IP for matching.
Note that IPs can sometimes be spoofed, so do not rely on this as a replacement for actual authentication.

So I don't think that remote host is what I should be using as the number of connections is not rate limited:
741 175.100.x.x
1312 209.212.x.x

741 & 1312 are the total number of connections.
My caddy config:
@ipv4 {
  remote_ip <IP_ADDRESS>/0  # All IPv4 addresses
}
# Only apply the following limit if it's an IPv4 address.
rate_limit @ipv4 {remote.host_prefix.32} 8r/s

@ipv6 {
  remote_ip ::/0  # All IPv6 addresses
}
# Only apply the following limit if it's an IPv6 address.
rate_limit @ipv6 {remote.host_prefix.64} 8r/s

After that I've modified rate limit plugin it and disabled using "X-Forwarded-For" here:
https://github.com/RussellLuo/caddy-ext/blob/ec2542243d48581e135db2f1c344bab48c8839a8/ratelimit/ratelimit.go#L245
and now everything looks quite good.
@ipv4 {
  remote_ip <IP_ADDRESS>/0  # All IPv4 addresses
}
# Only apply the following limit if it's an IPv4 address.
rate_limit @ipv4 {remote.ip_prefix.32} 8r/s

@ipv6 {
  remote_ip ::/0  # All IPv6 addresses
}
# Only apply the following limit if it's an IPv6 address.
rate_limit @ipv6 {remote.ip_prefix.64} 8r/s

Thanks!

Hello, I think these plugin names are confusing here ;)
In our discussion there are two types of plugins in Caddy:

Matchers

http.matchers.remote_ip (STANDARD)
http.matchers.remote_host (NON-STANDARD, see here)

Placeholders

{remote.host} (STANDARD, shorthand of  {http.request.remote.host})
{remote.host_prefix} (NON-STANDARD, implemented by ratelimit)
{remote.ip} (NON-STANDARD, implemented by ratelimit)
{remote.ip_prefix} (NON-STANDARD, implemented by ratelimit)

The evaluation of {remote.host_prefix} is as below:
https://github.com/RussellLuo/caddy-ext/blob/ec2542243d48581e135db2f1c344bab48c8839a8/ratelimit/ratelimit.go#L242-L243
As you can see, the second parameter false means that  the forwarded flag is disabled. Thus when calculating the client IP, the X-Forwarded-For header will be ignored:
https://github.com/RussellLuo/caddy-ext/blob/ec2542243d48581e135db2f1c344bab48c8839a8/ratelimit/ratelimit.go#L267-L271
In conclusion, I think {remote.host_prefix should work as expected 😄

Hello,
Thank you so much for your kind reply and explanation!
Understood now but I think somehow somebody was bypassing host_prefix limit or just the problem is with the /32* prefix and the limit doesn't work in that case as expected?
*rate_limit @ipv4 {remote.ip_prefix.32} 8r/s
Thanks!

After that I've modified rate limit plugin it and disabled using "X-Forwarded-For" here:
https://github.com/RussellLuo/caddy-ext/blob/ec2542243d48581e135db2f1c344bab48c8839a8/ratelimit/ratelimit.go#L245
and now everything looks quite good.

In theory, your modified version of {remote.ip_prefix.<bits>} should behave just the same as {remote.host_prefix.<bits>}, since the only difference between them is the forwarded flag.

741 175.100.x.x
1312 209.212.x.x

741 & 1312 are the total number of connections.

Here are some questions I think we need to figure out:

Where did these IP come from in the requests?  Were they passed via the X-Forwarded-For header?
Can we try to do some experiments locally by sending requests with the same IPs, and see what will happen? (Furthermore, we can also enable the DEBUG mode, and then watch the DEBUG logs.)

Hello,
Sorry about the late reply but everything has been working like a charm! Well the issue I had wasn't related to this plugin.
I'll report if any issues will arise.
Thank you!

Glad to hear that! Feel free to open new issues if needed :)


Inheriting to DOM Objects like HTMLElement or CSSDeclaration causes browser console errors?

I can't seem to inherit HTMLELement or CSSDeclaration classes to create something like pure C# css or making custom HTMLElements with specific behaviors
I think its a bug in Bridge or something I am doing wrong?

Hey, This is because HTMLElement class' don't exist and are converted into the raw javascript operation's.
for instance:
var x = new HTMLDivElement();

var x = document.createElement("div");

Closing this as there has not been any feedback from the reply provided for some time now.


Receiving support?

Hi there! This isn't a issue but I didn't know where to ask!
Are you accepting donations or supports? Because may you get some extra support for wechat, but there is no donate button o something like that.
I don't trying to spam you, but I want to invite you to beerpay.io, a simple platform to monetize open source projects, like electronic-wechat.
I know that the open source is free, but it's okay if someone want to contribute in other way.
Thanks for this work!

@Francolpm I'm sure you wouldn't have Alipay and WeChat pay integrated. So your service does not really help. -.-


Fix read issue caused by u32 overflow

Heyo; not doubting, just surprised - do you have any example game paths that trip this behavior?


chore: run apt-get update before running other commands

Things added/changed:

Run sudo apt-get update before running other commands on the Gitpod Dockerfile.

Isn't an apt-get upgrade necessary after an update?

Isn't an apt-get upgrade necessary after an update?

Sometimes, not all of the packages are updated, even on the first start, AFAIK.

@Panquesito7 I know that this was already merged, but I would like to know why do you think this change is needed? Is it recommended to run sudo apt-get update before executing the https://nim-lang.org/choosenim/init.sh script?

curl might not be up to date.

sudo apt-get update only updates the package index. In this case sudo apt-get upgrade is needed.
A side remark: in my opinion having a not updated curl' is a smaller problem than using sudo` in a docker file.

I will check Docker's security recommendations tomorrow.

After thinking about it, I have a strong opinion: this change should be reverted. The reasons are as follows:

apt-get update updates the index (and this is not needed in this case),
adding upgrade in order to update installed packages like curl does not make sense: this should be done inside the image gitpod/workspace-base.

@dlesnoff @Panquesito7 if you agree with me, I will make a suitable PR.

I revert it, and I wait for a better suggestion.


[FormRecognizer] Consider handling failed status for receipts and content operations

Summary
When starting or polling results from a RecognizeCustomForms Operation, it's known that the service may return a successful HTTP status code even when the operation itself has failed. This is already being handled and a RequestFailedException is being thrown in these scenarios.
https://github.com/Azure/azure-sdk-for-net/blob/8f5c50cb3b65bfa0544c76867464252b2bd02d1a/sdk/formrecognizer/Azure.AI.FormRecognizer/src/RecognizeCustomFormsOperation.cs#L120-L126
However, there are no known scenarios in which Receipts/Content recognition operations can behave the same way. In case such scenarios exist, they must be handled as well.
Goals

Understand the possible error scenarios that can be returned from the service when running Content/Receipts recognition operations.
If necessary, update the client code so it can handle the aforementioned scenarios.
Create tests to validate the changes.
Make sure existing tests still pass reliably.

Duplicate of: https://github.com/azure/azure-sdk-for-net/issues/11473


Out of memory when processing packets

TO DUPLICATE
1 - Install on *nix system.
2 - Place interface in mon mode and permisc
3 - Start the remoteID app
4 - Open HTOP
5 - With each packet that is processed - Memory keeps creeping up until mem is gone, then swap will fill, then system will lock.
Can't put my finger on the cause yet.

Updated my version of python and that appeared to make the issue go away - Closing this item.

perfect, thanks


PointerBuf::append should have a generic param

pub fn append(&mut self, other: &PointerBuf) -> &PointerBuf

I think it'd be nice to be able to append a Pointer or PointerBuf here. AsRef<Pointer> maybe?

Great idea! Generally we should have APIs that take a &Pointer take the more general AsRef<Pointer>, like std::path does with &Path 👍


Store the list which contains scores in the database

e.g. [[u'\u6c49\u8bed\u4e0e\u4e2d\u56fd\u4f20\u7edf\u6587\u5316', '2.0', '85']]

serialize the list and then save it.
the_list = [u'\u6c49\u8bed\u4e0e\u4e2d\u56fd\u4f20\u7edf\u6587\u5316', '2.0', '85']
pickled_list = pickle.dumps(the_list)
...save in the database...

...pick it out from database...
pickled_list = ...
the_list = pickle.loads(pickled_list)

how-do-i-store-a-dict-list-in-a-database
the-best-way-to-store-a-python-list-to-a-database

Now I use json. Because I don't know how to pickle _ElementUnicodeResult objects.
for example:
tree =

Now I use json. Because I don't know how to solve the problem "can't pickle _ElementUnicodeResult objects".
for example:
from lxml import html
import requests
import pickle
r = requests.get('url')
tree = html.fromstring(r.text)
the_list = tree.xpath('//ul[@class="entries']/li/text()')
pickled_list = pickle.dumps(the_list)

TypeError: can't pickle _ElementUnicodeResult objects


can not delete replica

Hello,
I have a freeipa master running on in adelton/freeipa-server docker.
I managed to create a replica, using another adelton/freeipa-server.
I stopped the replica docker. When I tried to re-run it, I got this message:

A replication agreement for this host already exists. It needs to be removed.
Run this on the master that generated the info file:
% ipa-replica-manage del ipa2.quartzbio.com --force

So I entered into the master server docker using docker exec, and typed:
% kinit admin
% ipa-replica-manage del ipa2.quartzbio.com --force  -v

but it hangs forever.
I also tried
%ipa-replica-manage list
ipa2.quartzbio.com: master
ipa.quartzbio.com: master

% ipa-replica-manage list-ruv
ipa.quartzbio.com:389: 4
ipa2.quartzbio.com:389: 3

% ipa-replica-manage disconnect ipa2.quartzbio.com ipa.quartzbio.com --force
this one hangs too.

In the meantime I setup the replica using another name. But why isn't is working ?
Best,

I stopped the replica docker. When I tried to re-run it, I got this message:
A replication agreement for this host already exists. It needs to be removed.

Could you show the full output that you got, leading to this message?

Could you show the full output that you got, leading to this message?

Checking forwarders, please wait ...
WARNING: DNS forwarder <IP_ADDRESS> does not return DNSSEC signatures in answers
Please fix forwarder configuration to enable DNSSEC support.
(For BIND 9 add directive "dnssec-enable yes;" to "options {}")
WARNING: DNSSEC validation will be disabled
Warning: skipping DNS resolution of host ipa2.quartzbio.com
Warning: skipping DNS resolution of host ipa.quartzbio.com
Using reverse zone(s) 0.17.172.in-addr.arpa.
A replication agreement for this host already exists. It needs to be removed.
Run this on the master that generated the info file:
    % ipa-replica-manage del ipa2.quartzbio.com --force
FreeIPA server configuration failed.
make: *** [run] Error 123

I've checked on 4.2 that when replica.example.com is down
ipa-replica-manage del replica.example.com

after about a minute proceeds with
Connection to 'replica.example.com' failed: Timeout exceeded
Forcing removal of replica.example.com
Skipping calculation to determine if one or more masters would be orphaned.
Deleting replication agreements between replica.example.com and master.example.com
Failed to get list of agreements from 'replica.example.com': Timeout exceeded
Forcing removal on 'master.example.com'
Any DNA range on 'replica.example.com' will be lost
Deleted replication agreement from 'master.example.com' to 'replica.example.com'
Background task created to clean replication data. This may take a while.
This may be safely interrupted with Ctrl+C
Failed to cleanup replica.example.com DNS entries: no matching entry found
You may need to manually remove them from the tree

Does it get stuck for you for long minutes?

Is the issue still present?

Hi,
Sorry I was in vacations. I'll check and test again on monday.
On Fri, Nov 27, 2015 at 4:16 PM, Jan Pazdziora<EMAIL_ADDRESS>wrote:

Is the issue still present?
—
Reply to this email directly or view it on GitHub
https://github.com/adelton/docker-freeipa/issues/40#issuecomment-160158169
.

In my freeipa master,  inside the docker:
 docker exec -ti freeipa bash
bash-4.3# ipa-replica-manage list
Directory Manager password:

ipa2.example.com: master
ipah.example.com: master
ipamidgard.example.com: master
ipa.example.com: master
bash-4.3# ipa-replica-manage del ipamidgard.example.com
Directory Manager password:

Connection to 'ipamidgard.example.com' failed:
Unable to delete replica 'ipamidgard.example.com'

In that case ipamidgard.example.com does not exist anymore. But I'm unable to remove it.

I tried again today:
ipa-replica-manage del ipa2.quartzbio.com --force  -v
Connection to 'ipa2.quartzbio.com' failed:
Forcing removal of ipa2.quartzbio.com
Skipping calculation to determine if one or more masters would be orphaned.
Deleting replication agreements between ipa2.quartzbio.com and ipa.quartzbio.com, ipamidgard.quartzbio.com, ipah.quartzbio.com
Failed to get list of agreements from 'ipa2.quartzbio.com':
Forcing removal on 'ipa.quartzbio.com'
Any DNA range on 'ipa2.quartzbio.com' will be lost
Deleted replication agreement from 'ipa.quartzbio.com' to 'ipa2.quartzbio.com'

Then it hangs forever.
I could not find anything in the logs, but I do not really know where to look for.
I also tried:
# ipa-replica-manage list
ipa2.quartzbio.com: master
ipah.quartzbio.com: master
ipamidgard.quartzbio.com: master
ipa.quartzbio.com: master

and then:
# ipa-replica-manage del ipa2.quartzbio.com --force  -v --no-lookup
ipa.quartzbio.com' has no replication agreement for 'ipa2.quartzbio.com'

ipa-replica-manage list host
# ipa-replica-manage list ipa.quartzbio.com
ipah.quartzbio.com: replica
ipamidgard.quartzbio.com: replica

# ipa-replica-manage list ipah.quartzbio.com
ipa.quartzbio.com: replica

# ipa-replica-manage list ipamidgard.quartzbio.com
Failed to get data from 'ipamidgard.quartzbio.com':

Finally I tried disconnect:
ipa-replica-manage disconnect ipa.quartzbio.com ipamidgard.quartzbio.com
Failed to get list of agreements from 'ipamidgard.quartzbio.com'

I don't have any clever idea or advice. Could we bring this to the freeipa-users mailing list?

I forgot to post this:
it seems to work if I use the --cleanup option:
ipa-replica-manage del ipa2.quartzbio.com --force --cleanup

Actually it does not clean the DNS (reverse?) 0.17.172.in-addr.arpa. I can see old PTR and NS entries that seem to prevent me from setting up the replica:
trying to run the replica docker for ipah

Using reverse zone(s) 0.17.172.in-addr.arpa.
A replication agreement for this host already exists. It needs to be removed.

But on the master (and also on another replica):
# ipa-replica-manage list
ipas.quartzbio.com: master
ipa.quartzbio.com: master

In your test on 4.2 with replica.example.com, did it work ?
Have you tested with ipa-replica-manage list ?

Using the lastest-systemd, I could delete the old replica data, by running multiple times
ipa-replica-manage del -fvc server

then
ipa-replica-manage clean-ruv ruv


feat: added github star button

Added github star button with star count to Top Right

Hey @aigdonia Great job!
I would prefer to style it to fit our design.
Take a look at this PR:
https://github.com/origranot/url-shortener/pull/90
I would like to combine it together :)

Maybe you should place the button a bit higher, as a navbar.


App should launch on machine startup

Not yet sure how to make this a preference, will look into later.

sometimes the easiest solution is to wait 4 years until someone else builds a framework that does it for you. Closed in #14


Is there a way to suppress Invalid # noqa directive on  warnings?

They clog up the output of the check command.

Can I ask why you want to suppress it, rather than address the warnings? Are the warnings invalid?

not every noqa is a ruff noqa somtimes I'm telling pycharm not to underline my code with # noqa: pycharm
especially in the http endpoints test when doing response.json() since apparently it's impossible to type it correctly:
https://stackoverflow.com/questions/76858314/how-to-properly-type-client-post-response-in-django-test

workaround | grep -v ^warning

Hey @Vulwsztyn it sounds like you're looking for the external setting.

@zanieb I do not see how I can suppress this message with this setting. I do not have e.g. # noqa: VXXX so as to suppress V by this settings. I have # noqa: PyCharm or # noqa bla bla reasoning

You should be able to pass whatever you want to external. E.g., external = ["PyCharm"] should be supported.

@charliermarsh unfortunately that doesn't work because the error is that the noqa statement is invalid due to its format
https://github.com/astral-sh/ruff/blob/1ae67f44872c2c08ffe21a907a35765374c1cde8/crates/ruff_linter/src/noqa.rs#L249


[BUG] Add missing line of code to elementIsVisibleInViewport

Description

Snippet : elementIsVisibleInViewport
The innerWidth and innerHeight was not assigned in code snippet, so adding them.
What does your PR belong to?

[ ] Website
[x] Snippets
[ ] General / Things regarding the repository (like CI Integration)

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (non-breaking improvement of a snippet)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Lodash Backlog

[ ] I added the prefix [UPDATE: method.md] or [ADD: method.md]
[ ] I have referenced the method to the lodash backlog.

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have checked that the changes are working properly
[x] I have checked that there isn't any PR doing the same
[x] I have read the CONTRIBUTING document.

@iamsoorena I don't think we should worry about those, Travis CI will rebuild the files anyways and these are just line endings that were changed. Am I missing anything else?

@Chalarangelo you are right.

I was about to ask if I need to revert those changes. 😄
This was my first open source PR. Thank you!


OllamaModels - list running models api/ps

Change

Add a new method to OllamaModels to list currently loaded/running models.
Modify the old DTOs OllamaModel and OllamaModelCard to add missing fields.
Add a new dependency to pom.xml - jackson-datatype-jsr310 - to properly parse dates.
General checklist

[X] There are no breaking changes
[X] I have added unit and integration tests for my change
[X] I have manually run all the unit and integration tests in the module I have added/changed, and they are all green
[ ] I have manually run all the unit and integration tests in the core and main modules, and they are all green

[ ] I have added/updated the documentation
[ ] I have added an example in the examples repo (only for "big" features)
[ ] I have added/updated Spring Boot starter(s) (if applicable)

Checklist for adding new model integration

[ ] I have added my new module in the BOM

Checklist for adding new embedding store integration

[ ] I have added a {NameOfIntegration}EmbeddingStoreIT that extends from either EmbeddingStoreIT or EmbeddingStoreWithFilteringIT
[ ] I have added my new module in the BOM

Checklist for changing existing embedding store integration

[ ] I have manually verified that the {NameOfIntegration}EmbeddingStore works correctly with the data persisted using the latest released version of LangChain4j

Running Ollama in Docker returns the date in UTC without an offset. Running it locally, in my case, returns an additional offset. I have fixed the OllamaDateDeserializer to support both cases.


NTR:  neutral amino acid, sodium: L-arginine antiporter activity

Please provide as much information as you can:

Suggested term label:
neutral amino acid, sodium: L-arginine antiporter activityy

Definition (free text)
Enables the transfer of a solute or solutes from one side of a membrane to the other according to the reaction: L-arginine(in) + neutral amino acid(out) + Na(+)(out) = L-arginine(out) + neutral amino acid(in) + Na(+)(in).

**Reference, in format PMID:10903140

Gene product name and ID to be annotated to this term

Parent term(s)
solute:cation antiporter activity

Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?

Synonyms (please specify, EXACT, BROAD, NARROW or RELATED)

Cross-references

For enzymes, please provide RHEA and/or EC numbers.

Can also provide MetaCyc, KEGG, Wikipedia, and other links.

Any other information

trying to find a CHEBI id for 'neutral amino acid' to see if I can find a RHEA or if I can request one.

Neutral amino acids are the amino acids that possess an equal number of amino and carboxylic acid groups. The groups attached to the amino acid, apart from the carboxylic acid groups and amino acid groups, may be either polar or non-polar.
note this def has to be pH dependent; in GO we use the form that exists at pH 7.3
I thought maybe 'non-polar amino acid', but
non-polar amino acids; CHEBI:25588
Nonpolar amino acids include alanine (Ala), leucine (Leu), isoleucine (Ile), proline (Pro), tryptophan (Trp), valine (Val), phenylalanine (Phe), and methionine (Met). The side chains of these amino acids are long carbon chains or carbon rings,

So I'm thinking Neutral amino acids at pH 7.3, the R group would have no charge?
@amorgat does RHEA have a 'neutral amino acid' entry? I might not be searching correctly

I think "neutral" would be all of the nonpolar ones plus glutamine, asparagine, serine, threonine, and cysteine - uncharged but polar side chains.
Question: does the transporter studied in PMID: 10903140 really interact roughly equally with this full range of amino acids, and if not, do you need to find a grouping term for the full range of neutral amino acids to deal with this term request, or only one to cover the range shown in the paper?
But you'd still need a grouping term for the subset that this transporter does handle, so my evasion may not help.

Or maybe here multiple annotations are needed. By analogy, Human ALDOB can convert fructose 1,6-bisphosphate to glyceraldehyde 3-phosphate + dihydroxyacetone phosphate fructose-bisphosphate aldolase activity and can also convert fructose 1-phosphate to glyceraldehyde + dihydroxyacetone phosphate
fructose-1-phosphate aldolase activity - one gene product, 2 activities, 2 GO terms, and no attempt in GO to make a grouping term to merge them into a single annotation.

I'm also thinking of multiple annotations to whatever specific amino acid might do.

Hi,
I hesitated to ask a new term GO for each amino acid for which a Rhea has been created from this PMID:10903140, namely L-leucine[Rhea:70831], L-glutamine[Rhea:70835], L-histidine[Rhea:70839] and L-cysteine[Rhea:70847].
Finally SLC7A6 transports very specific amino acid, it is not a SLC transporter with a large spectre, probably better to create  a specific term for each amino acid describes above.
I hope that helps

So, I could create the term, and define 'neutral amino acid' based on the def above (Neutral amino acids are the amino acids that possess an equal number of amino and carboxylic acid groups.)
taken from https://byjus.com/question-answer/give-an-example-of-neutral-amino-acid/
Therefore, apart from the carboxylic acid and amino acid groups, the groups linked to the amino acid might be non-polar or polar.
but needs to be pH7.3-friendly.
So at 7.3, zwitterionic forms for glycine, tyr, phe, ser, thr, leu, ile, val

I think the parent should be 'GO:0005295 neutral L-amino acid:sodium symporter activity'

Also need to remove the LD from GO:0140893 neutral amino acid, sodium:proton antiporter activity since this is not defining a neutral amino acid

Hi Harold,
ok but finally according to your definition of a neutral amino acid, this tem will only match L-leucine[Rhea:70831], so it will miss me  the 3 others L-glutamine[Rhea:70835], L-histidine[Rhea:70839] and L-cysteine[Rhea:70847].
It's probably better to create a term for each amino acid describes above, what do you think?
thanks

Can this one be closed if we do not need this grouping term?


⚠ TiendaEnLinea has degraded performance

In 51e9dd9, TiendaEnLinea (https://www.fahorro.com/) experienced degraded performance:

HTTP code: 200
Response time: 5281 ms

Resolved: TiendaEnLinea performance has improved in eda9ea2.


Combo button in Disclosure: Audit and update the info accordingly to the Menu buttons docs

This Combo button section will need to be updated once the Menu button docs are ready to be published.
Link: https://carbondesignsystem.com/patterns/disclosures-pattern/#combo-button

o

o


A script that pulls release notes into yml does not see different level of bullets

See, for example, this .yml:
https://github.com/Azure/azure-sdk/blob/000bfda0b100192733b7ca2626465734a40be225/_data/releases/2022-10/cpp.yml#L74-L83
And compare it to the original .md, which has two different levels of bullets:
https://github.com/Azure/azure-sdk-for-cpp/blob/0d6624fdaaeaf5afed2684014021c19d2b876581/sdk/storage/azure-storage-files-datalake/CHANGELOG.md?plain=1#L17-L26

I suspect it this is a bug at https://github.com/Azure/azure-sdk/blob/main/eng/scripts/Generate-ReleaseNotes.ps1#L85 which trims the lines. We might need to correctly remove the spacing from the from instead of just trimming everything.

Here is the latest example - bullets nesting is lost, "Other Changes" section is lost:
https://github.com/Azure/azure-sdk/blob/c7c10549eb6f3df34199d0eb86cd06f07875955d/_data/releases/2023-02/cpp.yml#L10-L39 vs https://github.com/Azure/azure-sdk-for-cpp/blob/6a53e4122f74937ff81ef736407128c548e4417c/sdk/core/azure-core/CHANGELOG.md?plain=1#L15-L57


Release web 2023 01 01

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

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

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
April
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
April
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

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

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

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[X] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

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

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

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

@rohinisharma be sure to resolve the issues listed here: https://github.com/Azure/azure-rest-api-specs/pull/23567#issuecomment-1509234700
You may have to run some tools locally as I've done in past PRs

Tenant/Provider level APIs that are outside the subscription context must discuss the scenario with PAS team. Partners can send an email to the following email ids to kick start the review.
SARBACRev<EMAIL_ADDRESS>

@sjanamma
Linter errors are not part of the changes I am introducing. Also, could you explain how these changes are outside the subscription context? I am adding the /subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/{location}/usages endpoint, which requires a subID.


Date focus issue

When we just enter date without entering month and year and tabbing out and tab in to the same field then the focus is on year always.Its not coming to the place where we last entered .

Using the version 3.3.11


Update README.md

Few changes

@sourabhbit I don't need this README.md to be modified.
Thanks for your valuable time and contribution.


SecurityGroupRule not being proper created, In fact, it's stuck forever

What happened?
I'm trying to create a composition that has a SecurityGroup followed by a SecurityGroupRule. The former is created fine, but even referencing it into the latter by ID, or any tags, it got stuck indefinitely.
Describing the object, I can see this error:
Message:               async create failed: failed to create the resource: [{0 waiting for Security Group (sg-xxxxxxxxxxx) Rule (sgrule-xxxxxx) create: couldn't find resource  []}]

It detects and reads the SG just fine, but looking at the console, the sgrule was never created, even if it generates a new id.
On logs of the EC2 Family provider I can see this running forever:
crossplane-aws-upbound-ec2-4bad1441a535-5d794694c9-2cphp package-runtime 2023-12-27T09:11:12Z     DEBUG   provider-aws    Diff detected   {"uid": "ef7fd987-4c15-4458-9eb3-b219a9f3b938", "name": "loki-efs-tr6kg", "gvk": "ec2.aws.upbound.io/v1beta1, Kind=SecurityGroupRule", "instanceDiff": "*terraform.InstanceDiff{mu:sync.Mutex{state:0, sema:0x0}, Attributes:map[string]*terraform.ResourceAttrDiff{\"description\":*terraform.ResourceAttrDiff{Old:\"\", New:\"Allow from Internal Network\", NewComputed:false, NewRemoved:false, NewExtra:interface {}(nil), RequiresNew:false, Sensitive:false, Type:0x0}, \"from_port\":*terraform.ResourceAttrDiff{Old:\"\", New:\"2049\", NewComputed:false, NewRemoved:false, NewExtra:interface {}(nil), RequiresNew:true, Sensitive:false, Type:0x0}, \"protocol\":*terraform.ResourceAttrDiff{Old:\"\", New:\"tcp\", NewComputed:false, NewRemoved:false, NewExtra:\"tcp\", RequiresNew:true, Sensitive:false, Type:0x0}, \"security_group_id\":*terraform.ResourceAttrDiff{Old:\"\", New:\"sg-xxxxxxx\", NewComputed:false, NewRemoved:false, NewExtra:interface {}(nil), RequiresNew:true, Sensitive:false, Type:0x0}, \"security_group_rule_id\":*terraform.ResourceAttrDiff{Old:\"\", New:\"\", NewComputed:true, NewRemoved:false, NewExtra:interface {}(nil), RequiresNew:false, Sensitive:false, Type:0x0}, \"self\":*terraform.ResourceAttrDiff{Old:\"\", New:\"false\", NewComputed:false, NewRemoved:false, NewExtra:interface {}(nil), RequiresNew:true, Sensitive:false, Type:0x0}, \"source_security_group_id\":*terraform.ResourceAttrDiff{Old:\"\", New:\"\", NewComputed:true, NewRemoved:false, NewExtra:interface {}(nil), RequiresNew:true, Sensitive:false, Type:0x0}, \"to_port\":*terraform.ResourceAttrDiff{Old:\"\", New:\"2049\", NewComputed:false, NewRemoved:false, NewExtra:interface {}(nil), RequiresNew:true, Sensitive:false, Type:0x0}, \"type\":*terraform.ResourceAttrDiff{Old:\"\", New:\"ingress\", NewComputed:false, NewRemoved:false, NewExtra:interface {}(nil), RequiresNew:true, Sensitive:false, Type:0x0}}, Destroy:false, DestroyDeposed:false, DestroyTainted:false, RawConfig:cty.NilVal, RawState:cty.NilVal, RawPlan:cty.NilVal, Meta:map[string]interface {}(nil)}"}
crossplane-aws-upbound-ec2-4bad1441a535-5d794694c9-2cphp package-runtime 2023-12-27T09:11:12Z     DEBUG   provider-aws    Async create starting...        {"trackerUID": "ef7fd987-4c15-4458-9eb3-b219a9f3b938", "resourceName": "loki-efs-tr6kg", "tfID": ""}
crossplane-aws-upbound-ec2-4bad1441a535-5d794694c9-2cphp package-runtime 2023-12-27T09:11:12Z     DEBUG   provider-aws    Creating the external resource  {"uid": "ef7fd987-4c15-4458-9eb3-b219a9f3b938", "name": "loki-efs-tr6kg", "gvk": "ec2.aws.upbound.io/v1beta1, Kind=SecurityGroupRule"}
crossplane-aws-upbound-ec2-4bad1441a535-5d794694c9-2cphp package-runtime 2023/12/27 09:12:08 [TRACE] Waiting 10s before next try
crossplane-aws-upbound-ec2-4bad1441a535-5d794694c9-2cphp package-runtime 2023/12/27 09:12:18 [TRACE] Waiting 10s before next try
crossplane-aws-upbound-ec2-4bad1441a535-5d794694c9-2cphp package-runtime 2023/12/27 09:12:28 [TRACE] Waiting 10s before next try

How can we reproduce it?
The composition has many resources, but even reducing it to just SG and SGRule is giving me the issue:
apiVersion: apiextensions.crossplane.io/v1
kind: Composition
metadata:
  name: security-group
spec:
  writeConnectionSecretsToNamespace: crossplane
  compositeTypeRef:
    apiVersion: platform.xxxxx.internal/v1alpha1
    kind: xSecurityGroup
  patchSets:
    - name: AwsParameters
      patches:
        - fromFieldPath: spec.region
          toFieldPath: spec.forProvider.region
    - name: SecurityGroupParameters
      patches:
        - fromFieldPath: metadata.name
          toFieldPath: spec.forProvider.name
    - name: SecurityGroupStatus
      patches:
        - type: ToCompositeFieldPath
          fromFieldPath: status.atProvider.id
          toFieldPath: status.filesystem.securityGroupId
          policy:
            fromFieldPath: Required
  resources:
    base:
    - name: efs-security-group
      base:
        apiVersion: ec2.aws.upbound.io/v1beta1
        kind: SecurityGroup
        spec:
          forProvider:
            name: # patched
            description: Allow access to EFS from the clusters private network
            vpcIdRef:
              name: workloads
      readinessChecks:
        - matchCondition:
            status: 'True'
            type: Ready
          type: MatchCondition
      patches:
        - patchSetName: SecurityGroupParameters
          type: PatchSet
        - patchSetName: AwsParameters
          type: PatchSet
        - patchSetName: SecurityGroupStatus
          type: PatchSet

    - name: efs-sg-rule-2049
      base:
        apiVersion: ec2.aws.upbound.io/v1beta1
        kind: SecurityGroupRule
        spec:
          forProvider:
            securityGroupIdSelector:
              matchControllerRef: true
            description: Allow access to EFS from private network
            fromPort: 2049
            toPort: 2049
            protocol: tcp
            type: ingress
            cirdBlocks:
              - <IP_ADDRESS>/8
            description: Allow from Internal Network
      readinessChecks:
        - matchCondition:
            status: 'True'
            type: Ready
          type: MatchCondition
      patches:
        - patchSetName: AwsParameters
          type: PatchSet

What environment did it happen in?

Crossplane Version: 1.14.5
Provider Version: 0.46.1
Kubernetes Version: 1.27
Kubernetes Distribution: EKS

did you tried
https://marketplace.upbound.io/providers/upbound/provider-aws-ec2/v0.46.1/resources/ec2.aws.upbound.io/SecurityGroupEgressRule/v1beta1
and
https://marketplace.upbound.io/providers/upbound/provider-aws-ec2/v0.46.1/resources/ec2.aws.upbound.io/SecurityGroupIngressRule/v1beta1

@haarchri It worked, thanks!
Is https://marketplace.upbound.io/providers/upbound/provider-aws/v0.46.1/resources/ec2.aws.upbound.io/SecurityGroupRule/v1beta1 deprecated and I missed something?

@sergenyalcin we could deprecate the resource ? Wdyt


Rename adbnx_adapter main method names

I'd like to rename some of the methods to keep things consistent with potentially upcoming adapters 👀 :

create_networkx_graph() becomes adb_to_nx()
create_networkx_graph_from_arangodb_collections() becomes adb_to_nx_from_collections()
create_networkx_graph_from_arangodb_graph() becomes adb_to_nx_from_graph()
create_arangodb_graph() becomes nx_to_adb()

Happy to take feedback on this 🚀

SGTM and LGTM

@aMahanna I'd advocate for a bit more verbosity so that the method names are a bit clearer at first glance?
e.g. adb_to_nx() could become arangodb_to_networkx(), and adb_to_nx_from_collections() could become arangodb_to_networkx_from_collections() etc.

Ah sounds good! Will update 👍

To avoid an extra release, which I would argue is unnecessary here, I've changed the destination of #35 to point to feature/batch-insertion.
Merge process will go as follows:

#35 merges into feature/batch-insertion (where #30 is active)
#30 merges into master

Here is the confirmed list of changes I will be making:
Public methods (increased verbosity):

create_networkx_graph() becomes arangodb_to_networkx()
create_networkx_graph_from_arangodb_collections() becomes arangodb_collections_to_networkx()
create_networkx_graph_from_arangodb_graph() becomes arangodb_graph_to_networkx()
create_arangodb_graph() becomes networkx_to_arangodb()

Protected methods (increased verbosity):

_prepare_adb_vertex() becomes _prepare_arangodb_vertex()
_prepare_adb_edge() becomes _prepare_arangodb_edge()
_identify_nx_node() becomes _identify_networkx_node()
_identify_nx_edge() becomes _identify_networkx_edge()
_keyify_nx_node() becomes _keyify_networkx_node()
_keyify_nx_edge() becomes _keyify_networkx_edge()

Private methods (reduced verbosity, given that the package user will not be interacting with this logic)

__fetch_arangodb_docs() becomes __fetch_adb_docs()
__insert_arangodb_vertex() becomes __insert_adb_vertex()
__insert_arangodb_edge() becomes __insert_adb_edge()
__insert_networkx_node() becomes __insert_nx_node()
__insert_networkx_edge() becomes __insert_nx_edge()


Image Scanning Tools

https://github.com/i3-training/DevSecOps-Training/commit/40da4d16d6ed6a135a469ec1ec9a09844b6c4d43


Generate docs of enums and rpc clients, some refactoring

This implements generating doc comments for enum types, enum values, rpc types,
and rpc methods.
Existing code for generating doc comments is refactored: the comment generator
handles trailing whitespace so we don't have to handle it in the call sites.
Comment generator is documented with the invariants: it never returns an empty
string (returns null instead) and never returns lines with trailing
whitespace.
To be able to test comment generating, a new kind of golden file test is added.
The difference from the other golden file tests is that this file is compiled
from .proto source instead of from a hand-crafted descriptor. This is because
attaching comments to proto field and types by hand is difficult and error
prone.
Fixes the comment part of #900.

@sigurdm for field comments, any thoughts on which accessors should have the comments copied?
Currently for a field x we generate these public members:

get x
set x
hasX
clearX

The documentation is currently copied only to get x, but deprecation annotations are added to all of these (in master branch, not with #908).
If duplicating potentially large comment blocks 4 times is not a problem I think we should add docs to all.

@sigurdm for field comments, any thoughts on which accessors should have the comments copied?

Really good question. I don't think the setter should have it: https://dart.dev/effective-dart/documentation#dont-write-documentation-for-both-the-getter-and-setter-of-a-property
Perhaps the hasX should just have a referring comment along the lines of:

Checks for presence of [X].
True if [X] has been set.

And clearX:

Unsets [X].

Makes sense, and thanks for the reference.
In that case I think we don't have to change anything in this PR.
I'm not sure if "clearX" and "hasX" docs are necessary, but if we want them we can add them separately.


Addressing iss #20

Moving package.json to root dir & updating paths

*:all.yml test:

*:db.yml test:


运行app.py的时候报错

前置确认

网络能够访问openai接口 #351
python 已安装：版本在 3.7 ~ 3.10 之间，依赖已安装
在已有 issue 中未搜索到类似问题
FAQS 中无类似问题

问题描述

简要说明、截图、复现步骤等，也可以是需求或想法
运行app.py的时候报错

终端日志 (如有报错)
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 159, in _new_conn
    conn = connection.create_connection(
  File "/usr/lib/python3/dist-packages/urllib3/util/connection.py", line 84, in create_connection
    raise err
  File "/usr/lib/python3/dist-packages/urllib3/util/connection.py", line 74, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 662, in urlopen
    self._prepare_proxy(conn)
  File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 950, in _prepare_proxy
    conn.connect()
  File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 314, in connect
    conn = self._new_conn()
  File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 171, in _new_conn
    raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.VerifiedHTTPSConnection object at 0x7fe1f22d3190>: Failed to establish a new connection: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in send
    resp = conn.urlopen(
  File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 719, in urlopen
    retries = retries.increment(
  File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='login.weixin.qq.com', port=443): Max retries exceeded with url: / (Caused by ProxyError('Cannot connect to proxy.', NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fe1f22d3190>: Failed to establish a new connection: [Errno 111] Connection refused')))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/fang/.local/lib/python3.8/site-packages/itchat/utils.py", line 134, in test_connect
    r = requests.get(config.BASE_URL)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 75, in get
    return request('get', url, params=params, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 60, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646, in send
    r = adapter.send(request, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/adapters.py", line 510, in send
    raise ProxyError(e, request=request)
requests.exceptions.ProxyError: HTTPSConnectionPool(host='login.weixin.qq.com', port=443): Max retries exceeded with url: / (Caused by ProxyError('Cannot connect to proxy.', NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fe1f22d3190>: Failed to establish a new connection: [Errno 111] Connection refused')))

You can't get access to internet or wechat domain, so exit.

环境

操作系统类型 Linux (Mac/Windows/Linux)：
Python版本 3.8.10( 执行 python3 -V )：
pip版本 20.0.2 ( 依赖问题此项必填，执行 pip3 -V)：

代理需要分流/规则模式，不然无法访问wx

我和你遇到同样的问题，代理已设置规则模式。并且不挂代理依然会有此问题。


Add Bira to Contributers list

First commit

@bira91, I'm quite elated about your PR. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a PR and learned that I merged it?


Adding merge function as an optional input for KeyZipper

Stack from ghstack:

-> #76

Fixes #44 by adding merge function as an optional input for KeyZipper. It allows user to specify how the items yielded from the DataPipes will be combined before they are yielded.
This PR changes the default behavior when keep_key=True and that may be BC breaking.
Previously, when keep_key=True, the output will be (key, item1, item2), now it will default to (key, (item1, item2). It is possible to leave the default behavior unchanged.
Note that KeyZipper may be renamed to IterZipper in #50 to provide users with better clarity.
Differential Revision: D31820203

@nivekt has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.


Add documentation about timing of transition execution

Feature request from discussion with @davidkpiano
Description:
There was a gitter discussion starting Aug 13 16:19 about confusion around the order of evaluation related to transitions.  @davidkpiano clarified in summary as:
The order is:
  * Do all microsteps (handle raised events, assign actions, transient transitions)
  * Transition to next state
  * Execute actions
Even if that wasn't the order, you should always assume that actions are fire-and-forget and happen asynchronously. They're side-effects, after all
What do your actions look like? If it impacts the condition test, then it sounds like it should be assign(...) (if affecting the context) or raise(...) (if doing something else that might cause a state transition)
The solution is simple but might be a tiny more tedious: ➕ add another intermediate state

It was suggested this could be moved into a discussion in the documentation (possibly with the interpreter section) to make it clear to users what to expect.
Adding here at @davidkpiano 's request.

I realise this when I wrote something like
const machineOpts = {
  actions: {
    exitActive: (context, event) => {
      console.log('exitActive');
    },
    enterIdle: assign((context, event) => {
      console.log('enterIdle');
      return context;
    }),
  },
};

and the result when transiting from active to idle flipped because assign() is executed first, as shown on the console result.
enterIdle
exitActive

This doc above helped me.


Nokogiri doesn't have remove method

I'm getting this error from my email template:
undefined method `remove' for #<Hpricot::Elem:0x007fe99a8bec60>

It comes from this line. When I switch to using nokogiri, the error goes away. It seems like this line was added for nokogiri and wasn't checked against Hpricot.
Can anyone confirm this?

Good catch. I'm thinking of no longer supporting hpricot since it is declared dead. In any case, it still is advertised as supported and thus this is a legit bug. Just looked around, this seems to be the solution:
link.parent.children.delete(link)

I'd be happy to accept a PR :wink:

I'm still getting that Hpricot error even though I've specified Premailer-rails to use nokogiri in configs:
#config/initializers/premailer_rails.rb
Premailer::Rails.config.merge!(adapter: :nokogiri

#rails c
Premailer::Rails.config
=> {:input_encoding=>"UTF-8", :generate_text_part=>true, :adapter=>:nokogiri}

A separate gem uses Hpricot, so it's in my Gemfile.lock.

I think that's just how Premailer works. Doesn't it say in the README (this gem) that Hpricot is used when both are loaded?
Sent from my iPhone

On 29 Jan 2016, at 15:47, Eric Fields<EMAIL_ADDRESS>wrote:
I'm still getting that Hpricot error even though I've specified Premailer-rails to use nokogiri in configs:
#config/initializers/premailer_rails.rb
Premailer::Rails.config.merge!(adapter: :nokogiri
#rails c
Premailer::Rails.config
=> {:input_encoding=>"UTF-8", :generate_text_part=>true, :adapter=>:nokogiri}
A separate gem uses Hpricot, so it's in my Gemfile.lock.
—
Reply to this email directly or view it on GitHub.

Yeah, so Premailer is to blame?

Yep. Actually I just checked an there is an :adapter config. Try setting that to :nokogiri.

Didn’t work. I actually forked the gem that was using hpricot and adapted it to nokogiri… No hpricot in Gemfile.lock and now I’m all good…
Thanks for your help.

On Jan 30, 2016, at 9:33 AM, Philipe Fatio<EMAIL_ADDRESS>wrote:
Yep. Actually I just checked an there is an :adapter config. Try setting that to :nokogiri.
—
Reply to this email directly or view it on GitHub https://github.com/fphilipe/premailer-rails/issues/149#issuecomment-177192920.

Any news on this ?

@kaluznyo the problem is with premailer itself. The :adapter flag will work so long as you don't have hpricot in your Gemfile.lock. But if some other gem pulls in hpricot, it uses that no matter what.
@fphilipe feel free to close this issue since it's a premailer problem.

@ericdfields Shouldn't that have been "Feel free to fix this since it's a premailer problem"? Why woud the issue be closed with no solution?

@caJaeger https://github.com/premailer/premailer/ is where the fix needs to happen. Out of scope for this gem.

@ericdfields Ah, I did not realize there was a different gem!


Enough already

All the license and product names change so much.
When is the name changing again?
When are the license names changing
How is anyone supposed to keep your products straight when you change the names of the all the time.
This is getting ridiculous.

@EtherMadness
Thanks for your feedback! We will investigate and update as appropriate.

@EtherMadness
We are going to close this thread. if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


[multi-stage] [debug-ability] Propagate exception error message

Currently, exception is just passed as an error block.
However, this exception message can be annotated on where it is problematic.
Say if something is wrong in AggregateOperator, we can throw exception with message "AggreagteNode runs into error etc"

i think a RPC-stacktrace-like error message is useful


Property type considerations

At the moment, it appears like there are three allowed kinds of properties:

strings
32-bit integers
booleans

The second two of these look reasonable. However, I think it would be prudent to distinguish between a string that is actually a string value (something like https://github.com/YosysHQ/yosys/blob/master/techlibs/nexus/cells_sim.v#L95, Lattice use these a lot) and a string value that is actually containing a bitvector (e.g. encoded as a Verilog constant).
Without that difference being stored; I don't think it will be possible to reliably go back to a Verilog netlist from an interchange netlist - the original value could have either been the bitvector 16'h1234; or actually a string "16'h1234" (equivalent to a much longer bitvector containing the ASCII values of those characters).
Yosys originally made a similar design mistake in its JSON format and now we have to live with a somewhat horrible escaping scheme involving postfixed spaces for disambiguation: https://github.com/YosysHQ/yosys/blob/master/backends/json/json.cc#L403-L405

String properties require quotes if they are quoted strings.  My processing of Yosys JSON might be messing this up.  So for example:
EX #(.PROP1("TRUE"), .PROP2(16'h1234)) ex();

Should actually be encoded as:
{
  .key = "PROP1"
  .textValue = "\"TRUE\""
},
{
  .key = "PROP2"
  .textValue = "16'h1234"
}

That make sense?

Yes, that makes sense. I hadn't actually checked that the JSON frontend was doing.
I'm still not sure if encoding two fundamentally different types of property into a string is the best option with access to all the power of a proper schema; storing bit vector parameters as a vector of bytes/32-bit words/etc would seem easier to work with to me.

storing bit vector parameters as a vector of bytes/32-bit words/etc would seem easier to work with to me.

This immediately runs into problems with LUTs (64-bits) and BRAM init strings (256-bits).  As a future extension, we could add a varint property field, but I think operating on verilog encoded strings is probably the right short-term answer.

This immediately runs into problems with LUTs (64-bits) and BRAM init strings (256-bits).

Yes, that's why I suggested a vector of bytes/words

I think operating on verilog encoded strings is probably the right short-term answer.

Don't have a massive problem with this provided that the semantics are well defined so we don't end up in a situation where different tools have slightly different ideas of what Verilog encoded string means (ime these kinds of differences tend to cause big problems with EDIF interoperability).

I think operating on verilog encoded strings is probably the right short-term answer.

Don't have a massive problem with this provided that the semantics are well defined so we don't end up in a situation where different tools have slightly different ideas of what Verilog encoded string means (ime these kinds of differences tend to cause big problems with EDIF interoperability).

So the initial solution here is to require that user supplied primitive cell parameters follow the default parameters of the library definition!  So if the device database primitive cell default is 64'b0, then it is required that the parameter use verilog binary bit strings.  If the default is 256'h0, then it is required that use verilog hex bit strings.  This is something that I've been planning on writing up in a docs folder, but wanted to get a basic non-timing driven P&R up and running before doing so.

I think operating on verilog encoded strings is probably the right short-term answer.

Don't have a massive problem with this provided that the semantics are well defined so we don't end up in a situation where different tools have slightly different ideas of what Verilog encoded string means (ime these kinds of differences tend to cause big problems with EDIF interoperability).

I've tried to address this in #19, take a look with that in mind.


AttributeError: 'Config' object has no attribute 'logging_format'

Describe the bug
I have installed behaveX and ran the command -> behavex -t @testtag --parallel-processes 4 --parallel-scheme scenario
Getting  -> AttributeError: 'Config' object has no attribute 'logging_format'. Can i please know how to resolve the issue
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Hi @Arwin-CTM, We are not being able to reproduce this issue in latest BehaveX version. Are you still experiencing it?
Thanks!


Failed to submit code for unknown reason

Yep, this one again. So there's a special code for people who played one of CNE's other games that is shutting down soon. It's not available to everybody. It's only available on Steam and I guess only to those who played the other game. I'm on EGS and whenever I run the code redeemer, I just get "Failed to submit code for unknown reason" and it is stuck on this code. No matter how many times I refresh, it tries to redeem that code again and I get this error.
The Discord link to the code in question is: https://discord.com/channels/357247482247380994/358044869685673985/947992113843409016

Same issue, perhaps having the option to skip any code post that you have reacted to already would suffice for this and be flexible for any future instances of a similar occurrence.

Fixed in 1.6.3

Can definitely confirm it works! Thanks for the quick turnaround!


PR for issue #81 + new modifiers + planner tweaks

The PR contains a collection of new modifiers and tweaks that I need to make the custom profile I'm developing. But I think those changes/additions can be useful for others, so here they are. I made sure nothing will change for existing profiles, and tried to do this with the minimal amount of alterations (and even tried to keep your unusual code formatting, VS really don't like it :-p).
CHANGES :
Issue #81
Added an optional "modifier_degen" field to rule, that allow to specify a separate set of modifiers for the degeneration rate.
I tried to check "modifiers_degen" in all places where rules modifiers existence was checked, but this may need to be reviewed.
Modifiers changes / addition

Added a "mod_comfort_space_limiter" modifier, that must be used together with living_space and comfort modifiers. It alter comfort factor to act as a secondary bonus against living_space (try it !).
Added a "crew_count" modifier
Added a "inverse" modifier :

Return 1/other modifiers
Division by zero rule : return 0.0 if divided modifier equal 0.0
Order-dependant, will apply the inverse on previous modifiers :
ex : modifier = volume,inverse,temperature // equal (1/volume)*temperature

Sim.TempDiff now return the signed (not absolute) temperature difference, but the "temperature" modifier still return the absolute value. This is to allow the two following modifiers :
"mod_temperature_pos" : return 1 if the temperature difference is positive, 0.0 otherwise
"mod_temperature_neg" : return 1 if the temperature difference is negative, 0.0 otherwise
This allow to make manage a climatization rule where heating and cooling are treated differently

Planner changes

Environment section : temperature difference now show relative (signed) temperature instead of absolute temperature
Stress section better accommodate the absence of comfort / pressure modifiers, and modified the formula for time to breakdown to account for the eventual presence of an input in the living_space rule. This allow to create a stress rule where the degen accumulation reset when living_space is above ideal.
The comfort tooltip now doesn't show comfort factors who have their factor equal to 0.0 in the settings.cfg (this allow to customize which factors are used).

First of all, thanks a lot for your continuous contributions to this project.
I see that you are growing familiar with the codebase, and in general I like what you are doing here.
I just added a couple comments in the changes about minor performance issues.
Now, you are probably aware I'm about to refactor/rewrite a lot of stuff.
One of the potential things is the modifier, that I want to improve.
I already got a 'generic expression parser' done.
Its very fast, and the only limitation is that it doesn't support operator precedence.
So I was thinking to introduce the concept of a 'modifier-expression'.

it is a mathematical function that return a scalar value
it can access a set of 'environment variables'
it can access resource amount, capacity, level, rate
it can use basic unary and binary operators, sqrt, min/max/clamp and sin/cos
it can order operations using parenthesis

That way you can write modifier-expressions like:
modifier = max(env.temperature - 295, 5) - 5

to get temperature above survival range.
Note how the actual settings of survival range just become a part of the modifier.
Or you could write a modifier-expression like:
modifier = Atmosphere.rate > 0

that will evaluate to 1.0 when something is pressurizing the habitat, and 0.0 otherwise.
Or this one:
modifier = Atmosphere.level > 0.9

that is 1.0 if pressure is ~90 kPA, and 0.0 otherwise.
This new 'modifier-expressions' concept is also going to be used in two other (awesome) new things that are coming: a new telemetry system where arbitrary modifier-expression readings are provided by parts/rules,  and a new alert system where arbitrary modifier-expression conditions are checked by parts/rules.
The new telemetry system in particular is going to be relevant here. You have already understood the fundamental impossibility of providing the current planner analysis panels in a generic rule-driven framework. Therefore the current planner panels are a sort of 'hack', good enough but show its limitations as soon as the user start specifying rules very different than the ones I developed against. I hope the new telemetry system may completely replace the planner panels too.
This is all very early-design / experiments. I'm really interested in what you think about these proposed improvements. Best!

Thanks for the reviewing of my code. I'm a hobbyist programmer and while I usually succeed in making things work, I'm really struggling to find the most efficient/fast/clean way of doing it, so your remarks are super useful.
All this is meant to be an implementation proposal, not a real PR. It would require a testing / fixing / optimization pass as well as a rebasing on your dev branch.
The modifier change seems a good idea, indeed having to maintain duplicates of functional code for flight and editor (planner) situations is not ideal. My tough on this when I discovered how all this work is that ideally, the "Vessel" reference in the "vessel_info" class should be allowed to be null. Then all the functions used to calculate the "vessel_info" properties should be able to perform with the actual vessel being optional.
This is what I did for the Habitat static function that calculate atmospheric flux and use the root part skinTemp when loaded to account for reentry heat. This allow me to use the same function in planner and vessel_info:
double Habitat.atmo_flux(CelestialBody mainBody, double altitude, double surface, double env_temperature, Vessel v = null)
That allow me to use it like that in vessel_info :
Habitat.atmo_flux(v.mainBody, v.altitude, surface, temperature, v)
And like that in the planner :
Habitat.atmo_flux(env.body, env.altitude, surface, env.temperature)
Then in the function, to illustrate :
some_value = (v == null) ? fallback_value_for_planner : value_when_loaded;
Unless I misunderstand what you are proposing, it seems to me that this is what you are trying to do  : an unified vessel variables cache that would be indifferent to the game context (editor/flight loaded/flight unloaded). If this happen and together with your (awesome) "modifier-expression" idea, this could indeed allow a config-driven planner (and in-flight monitor) UI system. Another thing that I was thinking is that processes and rules should be merged in a single system. Maybe this is too much but here is some prospective work for an unified system, using habitat thermal control as an example :
Rules
{
  // a VesselValue is like a resource, excepted it isn't stored in a part but by vessel
  // when docking, the resulting vessel get the sum of the two vessels amount & capacity
  // the capacity modifier allow to determine factor to split the stored amount between the two vessels after undocking
  VesselValue
  {
    name = neg_kjoule             // this can be used like a resource in modifier-expression (amount/capacity/level...)
    title = kJ                    // name of the value to display in the GUI
    capacity = neg_kjoule_amount  // modifier used to calculate max amount of VesselValue, if unspecified capacity = amount at all times
  }

  Modifier
  {
    name = neg_kjoule_amount
    expression = env.volume * 100000.0 * 25.0 // min temperature is ideal temperature - 25 K
  }

  // heat losses from environment
  ValueInput
  {
    name = heat losses          // reference/id to use in the GUI
    value = neg_kjoule          // value to add
    rate = 1.0
    interval = 1.0
    modifier = watt_flux_neg
  }

  // heat gains from environment
  ValueOutput
  {
    name = heat gains
    value = neg_kjoule
    rate = 1.0
    interval = 1.0
    modifier = watt_flux_pos
  }

  // calculate net thermal flux (kW) for the habitat (real formula would more complex)
  Modifier
  {
    name = net_flux
    expression = ((5,67E-08 * env.surface * env.temperature * env.temperature * env.temperature * env.temperature) - (5,67E-08 * env.surface * 0.5 * env.temperature * env.temperature * env.temperature * env.temperature ) + (env.crew_count * 30.0)) * 0.001
    // would be great to be able to do pow(env.temperature,4.0)
  }

  Modifier
  {
    name = watt_flux_pos
    expression = (net_flux > 0.0) * net_flux
  }

  Modifier
  {
    name = watt_flux_neg
    expression = (net_flux < 0.0) * net_flux * -1.0 // is abs(net_flux) possible ?
  }

  // used to determine the amount of ECLSS heater available, for use in the ProcessControler module
  // no capacity specified : capacity is ignored (made equal to the amount at all times)
  VesselValue
  {
    name = _heater               // this can be used like a resource in modifier-expression (amount/capacity/level...)
    title = ECLSS heater
  }

  // the heater should not remove more heat than the stored heat !
  Modifier
  {
    name = heater_output
    expression = min(neg_kjoule.amount, _heater)
  }

  // ECLSS heater input
  ResourceInput
  {
    name = heater
    resource = ElectricCharge
    rate = 1.0
    modifier = heater_output
  }

  // ECLSS heater output
  ValueInput
  {
    name = heater
    value = neg_kjoule
    rate = 1.0
    interval = 1.0
    modifier = heater_output
  }

  // a KerbalValue is like a resource, excepted it isn't stored in a part but by each Kerbal on the vessel
  KerbalValue
  {
    name = kerbal_neg_temp             // this can be used like a resource in modifier-expression (amount/capacity/level...)
    capacity = kerbal_neg_temp_amount  // modifier used to calculate the capacity
    ksc_reset = true                   // is the KerbalValue amount set to 0.0 when the kerbal get back to KSC
    vessel_reset = true                // is the KerbalValue amount set to 0.0 when the vessel the kerbal is in is modified
  }

  Modifier
  {
    name = kerbal_neg_temp_amount
    expression = 60 * 60 * 24   // 24 hours to death at min temperature
  }

  ValueInput
  {
    value = kerbal_neg_temp
    rate = 1.0
    interval = 1.0
    modifier = hab_neg_temp_input
  }

  Modifier
  {
    name = hab_neg_temp_input
    expression = pow(neg_kjoule.level,5.0)
  }

  ValueOuput
  {
    value = kerbal_neg_temp
    rate = 1.0
    interval = 1.0
    modifier = hab_pos_temp_output
  }

  Modifier
  {
    name = hab_neg_temp_output
    expression = neg_kjoule.level < 0.01
  }

  Event
  {
    text = $ON_VESSEL$KERBAL froze to death   // the text to show on screen
    timewarp_break = true                     // does the event stop timewarp
    unfocused_show = true                     // does the text show up if this isn't the current vessel
    modifier = neg_temp_death                 // modifier-expression that trigger the event when turning from false to true
    consequence = death                       // death/breakdown/none
  }

  Modifier
  {
    name = pos_temp_death
    expression = kerbal_pos_temp.amount == kerbal_pos_temp.capacity
  }

  Modifier
  {
    name = watt_flux_pos
    expression = info.tempertature * info.
  }

  PlannerPanel
  {
    title = Thermal control                 // name of the panel
    section = 3                             // where to put it in the planner window
  }

  PlannerLine
  {
    panel = Thermal control                 // the line should be in this panel
    title = Environment flux (kW)           // the line left text
    value = net_flux                        // the line right text, modifier or use "" to evaluate as a string
  }

  PlannerLine
  {
    panel = Thermal control      // the line should be in this panel
    title = death by freezing    // the line left text
    value = freezing_time        // the line right text, modifier or use "" to evaluate as a string
    value_format = duration      // returned value is Lib.HumanReadableDuration(value)
    color = #ff0000              // color of the value
    visible = freezing_isvisible // modifier-expression that determine visibility
  }

  PlannerLine
  {
    panel = Thermal control        // the line should be in this panel
    title = temperature is stable  // the line left text
    color = #00ff00                // color of the value
    visible = tempstable_isvisible // modifier-expression that determine visibility
  }

  Modifier
  {
    name = freezing_time
    expression = (neg_kjoule.capacity / neg_kjoule.rate) + (60 * 60 * 24)
  }

  Modifier
  {
    name = freezing_isvisible
    expression = neg_kjoule.rate > 0.0
  }

  Modifier
  {
    name = tempstable_isvisible
    expression = (neg_kjoule.rate == 0.0) && (pos_kjoule.rate == 0.0)
  }

Another  GUI example for stress :
Rule
{
  ...

  Event
  {
    text = The crew is feeling gravity again // the text to show on screen
    timewarp_break = false                   // does the event stop timewarp
    unfocused_show = false                   // does the text show up if this isn't the current vessel
    modifier = gravity_message               // modifier-expression that trigger the alert when turning from false to true
    consequence = none                       // death/breakdown/none
  }

  Modifier
  {
    name = gravity_message
    expression = env.firm_ground == 1.0
  }

  PlannerLine
  {
    title = breakdown                       // the line left text
    value = 1.0 / (degen modifier formula)  // the line right text, modifier-expression or use "" to evaluate as a string
    value_format = duration                 // returned value is Lib.HumanReadableDuration(value)
    visible = info.comfort < 0.2            // modifier-expression that determine visibility
  }
  PlannerLine
  {
    title = comfort              // the line left text
    value = "poor"               // the line right text, modifier-expression or use "" to evaluate as a string
    color = #ff0000              // color of the value
    visible = info.comfort < 0.2 // modifier-expression that determine visibility
  }
  PlannerLine
  {
    title = comfort
    value = "modest"
    color = #ff8300
    visible = (info.comfort >= 0.2) && (info.comfort < 0.4)
  }
  ...
  PlannerTooltip
  {
    line_title = comfort      // show tooltip on Rule_UI_line whose title = comfort
    title = firm ground       // the line left text
    value = info.firm_ground  // the line right text, modifier-expression or use "" to evaluate as a string
    value_format = boolean    // returned value is Lib.HumanReadableBoolean(bool value) {return value ? "true" : "false";}
    color = #00ff00           // color of the value
  }
  ...
}

@gotmachine That's very good ideas and I feel the need to speed-update you on what's going on, so we can design this together. I'll create a new issue with the proposed changes to the mod architecture and we'll discuss there.


Default application consistent

Hi, on https://docs.microsoft.com/en-us/azure/site-recovery/azure-to-azure-how-to-enable-replication#enable-replication , when setting up the replication policy, the default app consistency frequency is every 4 hours, and not 60 minutes.

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

ID: 8e22f219-b22a-b9d4-b0b7-e080b134da8d
Version Independent ID: b2e66450-6b64-c541-c4d3-c6caeaecac4e
Content: Configure replication for Azure VMs in Azure Site Recovery
Content Source: articles/site-recovery/azure-to-azure-how-to-enable-replication.md
Service: site-recovery
GitHub Login: @asgang
Microsoft Alias: asgang

I believe
App-Consistent Snapshopts for VMware VMs the default value is : 1 Hr/60 Mins
App-Consistent Snapshots for Azure VMs the default is : 4 hrs

thanks for the feedback. I have fixed it in the docs https://github.com/MicrosoftDocs/azure-docs-pr/pull/80370

#please-close


Change the look of the table of aquivalences

For the table of equivalences, I used the same class (index.md -> Natural deduction -> the table) in the marker .

thanks!


Add aframe.city as origin trial webvr chromium

https://docs.google.com/forms/d/e/1FAIpQLSfO0_ptFl8r8G0UFhT0xhV17eabG-erUWBDiKSRDTqEZ_9ULQ/viewform

Submitted, waiting for tokens

<!-- Origin Trial Token, feature = WebVR, origin = https://kfarr.github.io, expires = 2017-05-15 --> <meta http-equiv="origin-trial" data-feature="WebVR" data-expires="2017-05-15" content="AmAdZNFX1keXWZiueeAH+WSzafYGoA/HyelNj/sTv1pObswLtVd54HMlOrfkF7c++Jh4D+9othc0wbyHEyRpRQYAAABOeyJvcmlnaW4iOiJodHRwczovL2tmYXJyLmdpdGh1Yi5pbzo0NDMiLCJmZWF0dXJlIjoiV2ViVlIiLCJleHBpcnkiOjE0OTQ4NTQ5ODh9">
and
<!-- Origin Trial Token, feature = WebVR, origin = https://aframe.city, expires = 2017-05-15 --> <meta http-equiv="origin-trial" data-feature="WebVR" data-expires="2017-05-15" content="AnyUPdMHJNPye+131zHEPd/WHDS23zaNUov4aZtnIW2XVNgwQsHIYOywbpTZ+RdzFaLW7OhWlPHhQVP1JuIMrgIAAABKeyJvcmlnaW4iOiJodHRwczovL2FmcmFtZS5jaXR5OjQ0MyIsImZlYXR1cmUiOiJXZWJWUiIsImV4cGlyeSI6MTQ5NDg1NDk4OH0=">
ready to be added to index

closing this for now, not needed as daydream specific input isn't even supported anyway


Change conf files group ownership to ddagent

What does this PR do?
Try to force the configuration file ownership to dd-agent when using the import script.
Motivation
There are cases where configuration files are created with sudo, causing them to be owned by root with world readable perms. Since the upgrade script moves these configuration files and changes their perms to 0640, the dd-agent user no longer has permission to read the file and the Integration won't run on Agent start.
Additional Notes
Anything else we should know when reviewing?

@nmuesch If I read the code correctly, this change may make the import command fail on the platforms where the dd-agent user and group don't exist (basically macOS and Windows), or am I missing something?

@olivielpeau Good catch. You're right. I think I've mitigated this in this PR - https://github.com/DataDog/datadog-agent/pull/1460


Instance rotation?

I'm trying to horizontally rotate instances in an i3dm tile to an angle (instance pointing north = 0, east = 90, south = 180, west = 270) but can't get it working in Cesium. In my case every instance has an own rotation angle.
I'm trying things out with defining NORMAL_UP and NORMAL_RIGHT unit vectors per instance but either the instances are drawn but not rotated (so pointing north), or the instances are not drawn at all.
Any pointers/samples how to get this working?

a function something like this? https://github.com/PrincessGod/objTo3d-tiles/blob/master/lib/obj2I3dm.js#L166

@bertt can you post your question to the Cesium community forum? https://community.cesium.com/
We use GitHub issues for tracking bug reports and feature requests.

ok see https://community.cesium.com/t/instance-rotation/10163

ok see https://community.cesium.com/t/instance-rotation/10163

how to set the size of every instance in an i3dm tile？such as a box ,there are two instance in an i3dm tile, but different size，different length or different width or different height or  both?

In the feature table there is scale (1 value for all directions) and scale_non_uniform (vector3) defined per instance.

thank u！
yes，i‘m thinking about the 'scale_non_uniform',but the direction of some instance is wrong ,like this:

the directions are defined in NORMAL_UP and NORMAL_RIGHT

the directions are defined in NORMAL_UP and NORMAL_RIGHT

first time, i set NORMAL_UP and NORMAL_RIGHT and not set 'scale_non_uniform' , it is not wrong.
second time, i set NORMAL_UP and NORMAL_RIGHT, also set 'scale_non_uniform' , it is wrong
im confused.


Display error

in ensemble options interface，everything can't be displayed completely

the same issue, UVR version 5.4.
My OS is Windows 10 Home 21H2.
I set the system scaling to 124%, maybe this is the cause of the issue.

I have found the solution to this issue:
This issue is caused by Windows system custom scaling, my 124% scaling for example.
You will solve this issue simply by the following two steps:

Disable your system's custom scaling. For example, disable 124% and replace it with one of the Windows default scalings.
Due to my resolution is 1080p, 100% will make icons and texts too small and difficult to read, I chose 125% instead.
After this, you will see the display issue is gone, but the window of UVR becomes blur. To solve this, right click on the UVR.exe and go to the Properties menu. Open its High DPI settings, and enable all the options in this menu.
Then you can enjoy a clear and full displayed UVR.
Hope this is helpful to you!

This has been addressed. Please download the latest version of UVR.
Link:
https://github.com/Anjok07/ultimatevocalremovergui#installation


Add KIC information for plugin ordering

Where is the problem?
https://docs.konghq.com/kubernetes-ingress-controller/latest/references/custom-resources/#kongplugin,https://docs.konghq.com/gateway/3.0.x/kong-enterprise/plugin-ordering/get-started/
What happened?
KIC 2.6 added support for plugin ordering, but we haven't written docs for it yet.
What did you expect to happen?
The KIC CRD references (https://docs.konghq.com/kubernetes-ingress-controller/latest/references/custom-resources/#kongplugin and https://docs.konghq.com/kubernetes-ingress-controller/latest/references/custom-resources/#kongclusterplugin) show the format of the Ordering field in Kong(Cluster)Plugins.
The plugin ordering guide (https://docs.konghq.com/gateway/3.0.x/kong-enterprise/plugin-ordering/get-started/) shows an example KongPlugin resource equivalent to the admin API examples.
Tracked in the docs repo, but will be written by someone from the Kubernetes team.
Code of Conduct and Community Expectations

[X] I agree to follow this project's Code of Conduct
[X] I agree to abide by the Community Expectations

@rainest Is https://github.com/Kong/docs.konghq.com/pull/4667 everything that we need ? If so can we close this one?


Incorrect file extension in source map when using eval-source-map

Bug report

What is the current behavior?

When using "devtool": "eval-source-map", the generated source map contains invalid file extension .js.js instead of just .js. The same behaviour is seen for .jsx files, the extension is .jsx.js.
The following is the source map JSON post converting it from the data URI format. See the value of file attribute.

{
  "version": 3,
  "file": "./index.js.js",
  "mappings": "AAAA;AACA;AACA;AACA;AACA;AACA",
  "sources": ["webpack://source-map/./index.js?41f5"],
  "sourcesContent": [
    "// Sum of two numbers\nfunction sum(a, b) {\n  return a + b;\n}\n\nconsole.log(sum(7, 8));\n"
  ],
  "names": [],
  "sourceRoot": ""
}

If the current behavior is a bug, please provide the steps to reproduce.
Code and instructions in this sample repo: https://github.com/sidx1024/eval-source-map-webpack-bug-repro

What is the expected behavior?

When using "devtool": "eval-source-map", the generated source map should have the correct file extension .js.

Other relevant information:
webpack version:  v5.74.0
Node.js version: v14.18.3
Operating System: MacOS
Additional tools: N/A

Thank you for the report, PR welcome

I'll try to fix this bug


CloudFront with Web Application Firewall?

** Which Category is your question related to? **
Amplify Console Hosting
If I'm using the Amplify Console to host a Static Website, where is it stored? It doesn't look like there is an S3 bucket being used by the Amplify Console to host the website?
If we use the Amplify CLI add hosting, it will use an S3 bucket, does the Amplify Console do something similar, but we just can't access it?

@blazinaj Hi, you can chain your customize CloudFront distribution in front of the managed CloudFront distribution. You have to pass '_DISABLE_L2_CACHE: true' environment variable to CodeBuild to disable service CloudFront chain.

Thank you very much. That is what I needed. What does the _DISABLE_l2_CACHE: true do exactly?

When I'm creating a CloudFront distribution, do I put the full amplify url as the Origin Domain Name Name?

Thank you very much. That is what I needed. What does the _DISABLE_l2_CACHE: true do exactly?

Disable the L2 cache will disable one layer of CloudFront that AWS Amplify Console used for instant deployment. As CloudFront allows 2 maximum CloudFront chaining together, you have to disable it and add your customize distribution.
Yes. You have to input the full domain name points to AWS Amplify domain

Thank you!
I got it hooked up through my custom CloudFront distribution. How do I make it so that the production.abcxyz.amplifyapp.com URL doesn't just bypass my custom CloudFront/WAF?

@blazinaj Hi, for the WAF feature the original URL is still public. The workaround can't disable the original domain. Right now, you can only use basic auth to ensure its security.

Ah, thank you very much. That's what I needed to know. I'll submit a feature request for that.

If we are also using a custom domain with our Console app, should this CloudFront/WAF workaround work?  If so, what would I use for the Origin in the CloudFront Distribution - our custom domain name or the Console generated domain?  I tried our custom domain and traffic did not seem to get routed properly through Cloudfront to get to the Console app.  It seems to just go straight to the Console app.

Hi,
I have the same situation of previous message (dave-moser), custom domain, and I want to protect it with WAF and IpFiltering with IPSet. Could somebody answer if the @garyleefight workaround and the configuration indicated by @blazinaj should work with custom domains added in the Amplify Console?
thank you

If anyone comes across this later, what we have done is to have custom cloudfront with a customized WAF. We added a custom name to the cloudfronts cname. The original domain name of Amplify is not customized (hence the customization of the domain name happens in cloudfront). We added access control to Amplify, so anyone with the original public URL cannot access amplify directly. We then added an authorization header as the custom header to cloudfront origin, so that we can access the amplify app s3 static pages from the cloudfront domain.

@kraichura I am trying to take your approach my amplify cloudfront is protected via the amplify restricted access, I have created a second cloudfront with the necessary WAF rules however I am having trouble bridging it to the amplify cloudfront. My authorization headers are not bypassing the restriction, can you share the Origin Custom Headers you used and if any special cache or origin request policies came into play ? Thanks.

I adopted Amplify in December of 2018 just after it was introduced at re-Invent.  In the beginning "it was" possible to directly manipulate the CloudFront distribution and S3 deployment bucket. In my humble opinion Amplify was the answer to the microservices architecture that was booming since 2011. Shortly after Kubernetes came about in June 2014, Serverless came on the scene after AWS Lambda's debut in 2014 and out of beta in October 2015 .  All are just abstractions from its predecessors.
To the point..... I believe that control is purposely being abstracted away in lieu of easy drag and drop options. To solve this as developers I feel we need to learn more and sometimes go backwards. I have used Amplify heavily since its debut and had to learn many other technologies to implement custom features like VPC's, CloudFront templates, Lambda and SQL/NoSQL. Try these other services to build your own solutions or maybe give the serverless Framework a try...

any solution to this other than creating a custom CloudFront?

Any news on this? WAF is clearly essential for a lot of question (geo filtering, firewalling, etc...) and the double distribution is certainly not an acceptable professional solution...


Update makedeps to use new URL

Fixes #10
This adds the ability to more easily set the version of boost and download from the new URL at jfrog artifactory.
Additional guards were added in the script.

Thank you for your contribution!