Improve invitation and login UX for non-SSO users

What we're after: New .gov and .mil users without an existing identity provider can consistently generate and redeem an invitation for themselves and log in correctly
Benefits/why:

Reduce barrier to entry for sandbox evaluations
Improve first impression of cloud.gov for prospective users
Reduce support inquiries

Metrics

Number of self-generated invitations going up from zero
Number of Zendesk and cloud-gov-inquiries threads about initial account setup dropping toward zero

Long since done.


Bump Xcode 12 GM build

Apple released 7208 prematurely today and I was one of the lucky ones to get it before 7209 went live.

😬 I missed this. thanks for the head's up.

@aaronbrethorst if you dont know already, i'd recommend using https://github.com/vineetchoudhary/Downloader-for-Apple-Developers when downloading stuff of the dev portal, much faster.

thanks @cntrump for catching this


Implement Postings Iterator Over Bytes

Closes fabxc/tsdb#18
@fabxc Umm, I think its time to add tests to this. No way for me to know if my changes are working unless I vendor this into Prom and run it. But I have no clue how to test this. Any pointers?

Ran it with Prometheus over-night, looks like its working (blocks have been persisted and able to query well).

Looks good in general 👍
The iterator of the byte slice should be easy enough to write unit tests for. For testing it embedded into the indexWriter it's indeed a bit more complicated. We would probably end up testing symmetry of indexWriter and indexReader, i.e. do I get the same data out that I wrote into it?
That of course doesn't protect against violations of the specified serialization format (not properly specified yet actually) if writer and reader both do it.

Added tests!

👍


[Bug] Drop-In Assets feature - several issues

If you add uncompressed media like JPG or MP4 will will not detect the added media. Soon as I added a ZIP file, the list shows all... ZIP, JPGs, MP4s

But, you still cannot install the JPGs or MP4s, the Install button is grey, only the ZIP has a lit Install button

dragging a PNG doesnt work. I tried dragging the main grid and also directly to the Asset Manager's specific item (Help, etc)... neither work

Dragging the ZIP 'works' and looks like it will install, but it does not install anything or ask what to do with the media (the zip contains multiple images, etc)

what about adding a media upload to the global uploader ?
Associated to png, jpg and mp4, it will ask for which screen the image would be added
Also a flag to choose replace / append mode
Uppon confirmation, the media is added to the medias of the selected game

what about adding a media upload to the global uploader ? Associated to png, jpg and mp4, it will ask for which screen the image would be added Also a flag to choose replace / append mode Uppon confirmation, the media is added to the medias of the selected game

I'm unclear what you are asking... this bug report is specific to Drop-In Assets as show/describe. The prior upload methods work when -not- using Drop-In Asset menu

1a) is certainly a duplicate of #432, it is fixed
Dropping a png in the folder should make it appear immediately
1b), 2) and 3) is as per design so far. There is no global installer for neither images nor videos. If you drag a png onto the tables, it is not reactive. This is same rule from drop-in, it cannot be dragged. And as a result of absence of such an installer, the install button is grey out.

=> and also this is why I suggested to add a media installer, so a popup in which user could select the media type and have it installed. But need more discussion with @syd711  on this

Also please note that you can drop on the table media section

That sums it up. I will just hide the "install" button for these assets to avoid confusion.

Fixed with 3.5.0


upgrade pairing based pdp algorithm to improve security

upgrade pairing based pdp algorithm
move Merkle based pdp algorithm to crypto
fix bug of docs
fix bug of xdb/conf

good


[RAILS] Log the ElasticSearch query as json

Using #inspect on the hash will inspect the values in the hash which
aren't printed according to the JSON spec.
This will change the output from:
{query: {range: {created_at: {gt: Tue, 13 Mar 2018 00:00:00 EET +02:00, lt: Wed, 05 Sep 2018 00:00:00 EEST +03:00}}}}

to:
{"query": {"range":{"created_at":{"gt":"2018-03-13T00:00:00+02:00","lt":"2018-09-05T00:00:00+03:00"}}}}

Which makes it a whole lot easier to copy and paste into Kibana for
testing/profiling.

I have signed the CLA if that is what is holding this up.

@cbarton, the format of the current #inspect is intentional — it's meant for easy "inspection" with a naked eye, where the quotes add unncecessary noise. For a different purpose, like pasting it into Kibana, a regular #as_json should be used?

@karmi If that is the intended introspection method, then I can close this PR. We can't use as_json because then we would still need to strip out the =>, at which point it would be the same as the to_json output.
While I agree that there is slightly less cognitive load in reading through the inspect output, I'd argue that it's negligible for most values except times/dates (as they are expanded). Speaking for myself personally, I tend to find that reading JSON is pretty easy as my brain kind of extracts away the quotes or if its a large structure, I'd pop it into a prettifier to dig in. The current problem is that you cannot use a prettifier and thus you have to dig through a large blob of curly braces (in our use case our queries that we like to debug can be pretty lengthy). Also, if there is a customer that is having difficultly with a particular search result or I am developing a new query, I have to manually recreate the query to ES or transform the inspected version to JSON.
Again, that's just my 2c, so let me know if you want me to close the PR; either is fine by me!


update securitypolicy schema and update validate webhook

update apis securitypolicy:

remove AppliedToPorts from policy schema
remove rule.Priority from policy schema
remove ICMPType and ICMPCode from SecurityPolicyPort
remove Protocol type SCTP
update crd validate webhook:
add portRange validate for securitypolicy
limit at least one AppliedToEndpointGroups should set in policy
limit at least one SecurityPolicyPort should set in rule

@kylezh cc


query all symbols return fewer symbols in the folder?

Hi @felixfbecker thanks for your amazing library, very useful.
At this moment I am trying to integrate php lsp using lsp4j, and want to query all of the symbols from the specified folder.
What I did was to first initialize the server with the root path, and them query using an empty string. Ideally it should return all symbols in the designated folder. However it only returns a small part of all the symbols in the folder.
I've tried to query php-language-server itself: What I did was to point the root folder to src/ in the initialization, and query using an empty string. What I get are a few symbols from LanguageServer\Client\TextDocument and Language\Client.  If I point the root folder to the project's root folder then I get nothing from the query.
I remember a while ago I tried to print out $symbols in Workspace and it indeed only contained a few symbols. Maybe I remembered it incorrectly.
I am trying to get all the symbols. Perhaps you could shed some light on how it might achieve the goal?

Until the most recent version indexing happenend in background, so you may got incomplete results.  Try v4.2 and see if you still experience it.

Thanks @felixfbecker , using v4.2 indeed returns more symbols than before.
I tried to wait a bit after initialization using v3.1, and it is indeed returning more symbols as expected.
One question is that when using v4.2, when I try to query Namespace, Class or Method, the server seems to not able to return anything, resulting a freeze. Waited for a few mins and it is still like this. Wondering if it is a know issue?

Please open a new issue for that


[Bug] Topic unloading during Compaction leads to messages loss and messages redelivery loop

Search before asking

[X] I searched in the issues and found nothing similar.

Version
3.1.0 using official Helm chart
Latest build from master using official Helm chart
Minimal reproduce step
Use 3 bookies, 3 brokers, 3 proxies

Create compacted, partitioned topic with the compaction threshold set to 1GB
Produce 100k of messages of 100 kb size
Create exclusive consumer and start reading
Produce 100k of messages with the same keys
-- wait for the messages to be produced and the compaction to finish
Create new exclusive consumer and read all the messages

What did you expect to see?
Compaction finish successfully.
First consumer receives between 100k - 200k messages
Second consumer receives 100k messages
What did you see instead?

I see in the error logs that the compaction fails.

The first consumer often starts to receive messages, that were already delivered (millions of messages, It never ends)

The second consumer cannot receive all the messages. Sometimes it is able to finish, sometimes is not (falls into the loop)

The backlog of the subscription does not change while the consumers are reading

Reads come from one broker, the backlog is not changing (the screenshot is from my environment/system):

Anything else?
The reproduction steps depends on the used setup, speed of the persistent storage. It's possible that the re balancing or adding new broker affects the steps. I cannot provide reproducible way, as it happens randomly. Nevertheless it happens to us almost every day.
Now, I produced:
30 GB of 30kb files x 2
5 GB of 5MB files x 2
4,6 GB of 130kb files x 2
I reconnected the client and started reading. Client received 5 048 330 messages, but only 661 897 unique.
The consumer summary after 93 minutes:
#93 Processing 1 message(s). Totally received: 5140219, already processed: 5140218 (ACK: 5140218.0, NACK: 0.0, Invalid: 0.0, Failed to ACK/NACK: 0.0
My internal stats:
internal.stats.txt
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

I was able to reproduce it with the topic with 60k messages.

Create the topic, run the compaction (to create subscription)

TOPIC="test-compaction"
kubectl exec --namespace pulsar -t pulsar-toolset-0 -- bin/pulsar-admin topics create-partitioned-topic $TOPIC -p 12
kubectl exec --namespace pulsar -t pulsar-toolset-0 -- bin/pulsar-admin topics compact $TOPIC
kubectl exec --namespace pulsar -t pulsar-toolset-0 -- bin/pulsar-perf produce -bm 1 -r 300 -m 10000 -s 102400 $TOPIC

Connect with the client:

import pulsar

client = pulsar.Client('pulsar://localhost:6650')
consumer = client.subscribe('test-compaction',
                            subscription_name='python-consume',
                            initial_position=pulsar.InitialPosition.Earliest,
                            is_read_compacted=True)

count=0
while True:
    msg = consumer.receive()
    count += 1
    print(count)
    consumer.acknowledge(msg)

client.close()

by invoking:
kubectl port-forward service/pulsar-proxy  6650:6650 -n pulsar &
python3 consumer.py

Run the compaction

kubectl exec --namespace pulsar -t pulsar-toolset-0 -- bin/pulsar-admin topics compact ${TOPIC}

Unlaod the topicc

kubectl exec --namespace pulsar -t pulsar-toolset-0 -- bin/pulsar-admin topics unload ${TOPIC}

The result:

python client fall in infinite loop, I've stopped it after receiving 127557 messages.
after restarting the client, it still receives new messages

Other information:

Pulsar Manager showing out rate and precise backlog:

Messages backlog is not from Gradana (last 10 minutes without changes)

Compacted ledger entries (87051):

➜  chaos-test-pulsar-perf git:(main) ✗ for i in {0..12} ; do kubectl exec --namespace pulsar -t pulsar-toolset-0 -- bin/pulsar-admin topics stats-internal  test-compaction-2-partition-$i |  jq -r ".compactedLedger.entries" ;done
8718
12692
8486
5113
11155
5077
5113
9513
5147
5151
5147
5739

I used topic unloading just to reproduce the issue. In our case it could be cuased by:

during broker restart on OOM on Direct Memory
during brokers scaling (i.e. adding broker)
topics re-balancing (bundles spliting)

I see this issue a lot during broker restart.
Sometimes we observe it without the restarts.

@michalcukierman Whether the consumer always receive duplicate messages even though the message has been acknowledged?
If so, then this is a known issue, as the consumer reads from the earliest position after the consumer reconnects. Refer to: https://github.com/apache/pulsar/pull/11287.

@coderzc, I don't think it's the same issue. We observe two situations:

consumer is not able to read all messages, even if the backlog is not empty (messages loss)
consumer is falling into infinite loop (starts to read the same messages in loop, even after sending acks)

In the test above the consumer finally received more than 250k messages, even if the number of produced messages was 60k.
In most of the cases where I see the Issue on our setup I publish around 1mln messages, the consumer reads around 600k-700k and stops receiving unique messages (even if it still receives 1k msg/s, all are duplicated).

Having the script:
trap printout SIGINT
printout() {
    [[ ! -z "$PYTHON_PID" ]] && echo "\nExiting... Killing Python Consumer" && kill -15 $PYTHON_PID
    exit
}

TOPIC="test-compaction-0"
echo "Create topic"
kubectl exec --namespace pulsar -t pulsar-toolset-0 -- bin/pulsar-admin topics create-partitioned-topic ${TOPIC} -p 12
kubectl exec --namespace pulsar -t pulsar-toolset-0 -- bin/pulsar-admin topics compact ${TOPIC}
echo "Produce messages"
kubectl exec --namespace pulsar -t pulsar-toolset-0 -- bin/pulsar-perf produce -bm 1 -r 300 -m 10000 -s 102400 ${TOPIC}

# Compact topic
echo "Compact topic"
kubectl exec --namespace pulsar -t pulsar-toolset-0 -- bin/pulsar-admin topics compact ${TOPIC}

# Unload topic and start reading the results
sleep 10 && echo "Unload topic"
kubectl exec --namespace pulsar -t pulsar-toolset-0 -- bin/pulsar-admin topics unload ${TOPIC}
echo "Start reading"
python3 consumer.py ${TOPIC} &
PYTHON_PID=$!

# Unload topic again (don't know if it's required)
sleep 10 && echo "Unload topic"
kubectl exec --namespace pulsar -t pulsar-toolset-0 -- bin/pulsar-admin topics unload ${TOPIC}
sleep 10 && echo "Unload topic"
kubectl exec --namespace pulsar -t pulsar-toolset-0 -- bin/pulsar-admin topics unload ${TOPIC}
sleep 10 && echo "Unload topic"
kubectl exec --namespace pulsar -t pulsar-toolset-0 -- bin/pulsar-admin topics unload ${TOPIC}

sleep 100000 # wait for CTRL+C

and the python script consumer.py:

import pulsar
import sys

client = pulsar.Client('pulsar://localhost:6650')
consumer = client.subscribe(sys.argv[1],
                            subscription_name='python-consume',
                            initial_position=pulsar.InitialPosition.Earliest,
                            is_read_compacted=True)

count=0
while True:
    msg = consumer.receive()
    count += 1
    print("#", count,  " -> ", msg.message_id())
    consumer.acknowledge(msg)

client.close()

I can see that the messages are delivered in a loop.
The results after greping by the message ID: python3 consumer.py ${TOPIC} | grep "(144,0"
are:

The same message is re-delivered in a loop.
All messages may never be delivered.

It seems to be the same issue as what I said above. If the topic unloads or the broker restarts, the consumer will reconnect to the broker and start reading data from the earliest position again, even if you already acknowledged some messages.
Also, this issue may also occur during the compaction process, and it will cause compacted data to have duplicate messages.
@michalcukierman Can you see if the number of compacted entries is greater than the total number of messages published?

@coderzc It's not a problem with duplicated messages.
Check the comment, I put some numbers there.

Produced messages: 60k
Messages in compacted ledger: 87051
Consumed messages 127k and growing (I stopped at 250k)

So the issue is not about duplicated messages, but the redelivery loop. Sometimes messages loss.
In both cases the backlog (Grafana and topic stats) does not change during the time.
Also, If you have duplicated messages in compacted ledger, you would expect different keys, right?
I get the same key, from the same ledger over and over:
# 306  ->  (144,0,1,-1)
# 5500  ->  (144,0,1,-1)
# 8862  ->  (144,0,1,-1)
# 11079  ->  (144,0,1,-1)
# 12825  ->  (144,0,1,-1)
# 15426  ->  (144,0,1,-1)
# 17804  ->  (144,0,1,-1)
# 19672  ->  (144,0,1,-1)
# 23374  ->  (144,0,1,-1)

so just with the example above I read 23374 messages during a single run probably around 100k during last hour.
The compacted ledger entries is exactly 10k:
➜  chaos-test-pulsar-perf git:(main) ✗ for i in {0..12} ; do kubectl exec --namespace pulsar -t pulsar-toolset-0 -- bin/pulsar-admin topics stats-internal  test-compaction-0-partition-$i |  jq -r ".compactedLedger.entries" ;done
851
835
816
833
803
824
823
837
823
842
843
870

@coderzc

Yes，my means is redelivery loop，since the readPosition will be reset to earliest position after consumer reconnect to broker when topic is unloaded or broker restart.

Can you explain me where is the loop? Reconnection happens once. After that the loop is infinite.

Is it possible that broker bundles load balancing always triggers clients to reconnect and start reading from the beginning?

Is it possible that broker bundles load balancing always triggers clients to reconnect and start reading from the beginning?

Yes, when the broker bundles load balancing, the consumer will reconnect to the broker, and the consumer will start reading from the beginning again.

Thanks, that may be in fact be the cause. I'll test it more and let you know.
In the meantime:

Are there any workarounds for the issue?
Are there plans to fix the behavior?

For now the only options I see are:

Not to use compaction
or disable Load Balancing and make sure that the brokers don't restart to often

There is currently no other way, we will fix this behavior as soon as possible.

There is currently no other way, we will fix this behavior as soon as possible.

we have fixed some issues related the compaction, i don't know if this issue has been fixed. @coderzc


refactor: remove tokenlogger

Purpose

Removes the redundant implementation of TokenLogger.

Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix (`fix`)
[ ] Feature (`feat`)
[ ] Code style update (formatting, local variables) (`style`)
[X] Refactoring (no functional changes, no api changes) (`refactor`)
[ ] Documentation content changes (`docs`)
[ ] Other... Please describe: (`perf`, `test`, `build`, `ci`, `chore`, `revert`)

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Run the project, ensuring APPINSIGHTS_ENABLED is set to true.

Chat with the app

What to Check
Verify that the following are valid

Log messages still appear in Application Insights with message "Token Consumption"

All great, the only thing I'm worried about is whether we could get ourselves in a state where existing customers, their app service will have the old 'APPINSIGHTS_ENABLED' flag set in the app settings, but the code could be the new version. Are we worried @cecheta ? It's just a debugging thing

All great, the only thing I'm worried about is whether we could get ourselves in a state where existing customers, their app service will have the old 'APPINSIGHTS_ENABLED' flag set in the app settings, but the code could be the new version. Are we worried @cecheta ? It's just a debugging thing

True, but I don't think this is the worst thing in the world, they just need to update the env var on their end


Vyper support

It would be nice if TypeChain supported type bindings for Vyper
https://github.com/ethereum/vyper/tree/master/vyper/types

@gakonst I always thought that vyper generates regular ABI files (same standard as solc). What's the difference?

Ah, totally missed the fact that I provide the ABI json and not the source code. NVM.

Would you mind a question? How would you get TypeChain to generate types for Vyper contracts? Thanks in advance.

@FormidablePencil you need to get ABI files from Vyper compilation results. If you use vyper with Hardhat, just use typechain-hardhat plugin.

@krzkaczor I
npx hardhat > "Create an advanced sample project that uses TypeScript" which installed typechain-hardhat and all the necessary dependencies for it to work with solidity.
Then I npm install --save-dev @nomiclabs/hardhat-vyper and put import "@nomiclabs/hardhat-vyper"; in hardhat.config.ts for vyper to work. Vyper and solidity contracts compile properly, using vyper contracts in tests work but the types for vyper fail to generate whereas solidity contracts don't.
Here's the repo with the same steps taken and with the artifacts committed https://github.com/FormidablePencil/types-for-vyper-fail/tree/master/typechain. You'll find that no types nor factories were generated. Maybe hardhat failing to generating *dbg.json in artifacts/contracts/ for vyper contracts has something to do with it but from what I read was that that file was for debugging purposes. Idk. I've been trying to get this to work with little to no luck.

I think you're hitting this problem described in the readme:

Warning: before running it for the first time you need to do hardhat clean, otherwise TypeChain will think that there is no need to generate any typings. This is because this plugin will attempt to do incremental generation and generate typings only for changed contracts. You should also do hardhat clean if you change any TypeChain related config option.

Try hardhat clean and then hardhat compile.

Cleaned and compiled but type issue persisted for vyper.

Quick workaround: use typechain cli directly.
https://github.com/dethcrypto/TypeChain/issues/594

I managed to concoct this command npx typechain --target=ethers-v5 './artifacts/contracts/**/+([a-zA-Z0-9_]).json' --out-dir "./typechain/" which generates the types for all contracts written in Solidity and Vyper but despite the types having been generated they aren't being applied by hardhat. In hardhat.d.ts it looks like hardhat completely ignores those generated files and recompilation on file change doesn't help either. Manually updating this autogenerated file did the trick.
getContractFactory(
  name: <name_of_contract>,
  signerOrOptions?: ethers.Signer | FactoryOptions
): Promise<Contracts.<factory>>;

getContractAt(
  name: <Name_of_contract>,
  address: string,
  signer?: ethers.Signer
): Promise<Contracts.<ContractTypes>>;

Yes. Hardhat.ts is a file generated by hardhat plugin. If you use CLI directly it won't be generated (updated). I would suggest using casts in your code or manually updating the file (or contributing with a fix to hardhat plugin! ;) )

Thanks for your help. I'll work with this solution and let the idea of contributing to hardhat with a fix marinade in my head.

FYI this issue still persists and the above workaround still works.


Corrects color channels in face restoration; Fixes #1167

Our Codeformer and GFPGAN implementations are sending RGB image data to the restoration code, but they expect BGR image data (as used by OpenCV).
The fix is simple; use a cv2 method to convert the image from RGB to BGR before processing, and then back to RGB so we can continue using PIL.
This fixes an until-today unknown flaw in our GFPGAN implementation, which was recognized by user JoshuaKimsey on discord.

I guess there's no harm in using cv2 for this if it's already a project dependency, but does Pillow have any modes that work for this built-in? Maybe BGR;24 or BGR;32?
https://pillow.readthedocs.io/en/stable/handbook/concepts.html#modes

Great find!

I guess there's no harm in using cv2 for this if it's already a project dependency, but does Pillow have any modes that work for this built-in? Maybe BGR;24 or BGR;32?
https://pillow.readthedocs.io/en/stable/handbook/concepts.html#modes

Good catch - I tried "BGR" first and it didn't work, shoulda checked the docs. I'll give this a whirl.

We already use cv2 so there's no particular advantage to doing this in Pillow, but if you want to, go ahead.

I had blue tint on the final rendered image when using restore face on a M1 Mac. After research and messing around I found this solution.
Download the following manually and place them in to their corresponding folder and rename the file as necessary.
https://github.com/sczhou/CodeFormer/releases/download/v0.1.0/codeformer.pth to /stable-diffusion-webui/models/Codeformer/codeformer-v0.1.0.pth
https://github.com/xinntao/facexlib/releases/download/v0.1.0/detection_Resnet50_Final.pth to /stable-diffusion-webui/repositories/CodeFormer/weights/facelib/detection_Resnet50_Final.pth
https://github.com/sczhou/CodeFormer/releases/download/v0.1.0/parsing_parsenet.pth to /stable-diffusion-webui/repositories/CodeFormer/weights/facelib/parsing_parsenet.pt


update SuperchainERC20 definition

#467  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


build: Starting with Node 11, Use of the legacy url.parse() method is…

This PR contains a:

[ ] bugfix
[ ] new feature
[x] code refactor
[ ] test update
[ ] typo fix
[ ] metadata update

Motivation / Use-Case
Starting with Node 11, Use of the legacy url.parse() method is discouraged. Users should use the WHATWG URL API. Because the url.parse() method  uses a lenient, non-standard algorithm for parsing URL strings, security issues can be introduced.So I tried to make compatibility changes.

Breaking Changes
None

Additional Info
None

Closed in favour of #411


Non-additive feature behavior

This code works:
use static_assertions::const_assert;

fn main() {
    const_assert!(false != true);
}

until any other crate in my dependency graph enables static_assertions' "nightly" feature. Then it breaks my crate's formerly working code. This is not good behavior for a cargo feature. Code that works without a feature must also work with the feature, otherwise you end up with libraries that work in isolation but can't be combined together in one dependency graph.

🤦♂ wow I had never considered this, thank you for letting me know. I suppose the only real solution is to remove the const _ bit until it becomes stabilized in 1.37 (https://github.com/rust-lang/rust/pull/61347).

Closed with the release of 1.0. 😄


jellyfish-wallet to use coinType/purpose/0/account pathing

What kind of PR is this?:
/kind feature
What this PR does / why we need it:
Updated JellyfishWallet to use path "coinType/purpose/0/account" non-hardened derivation with:

coinType support  for BTC/DFI for ICX
purpose support for LIGHT_WALLET and MASTERNODE locked UTXO.
account for addresses within the purpose use case. E.g. light wallet addresses, masternodes.

This won't break compatibility with DeFiCh/wallet because currently we only use one default address.
Where account = 0.
Before:

1129/account/0/0 -> 1129/0/0/0

After:

COIN_TYPE = 1129, default
PURPOSE = 0, default
coinType/purpose/0/account -> 1129/0/0/0

Account and purpose are swapped so the addresses coming out are different. This won't break existing users wallet?

Nevermind read the bottom of the description


Deploy application to Serverless hosting

Issue solved! Deployment done in Vercel. Awaiting to have new host for AWS Lambda.


Small bug fix: duplicate in Gelatinous Cube condition_immunities

What does this do?
Removes a duplicate Blinded condition_immunity with the Deafened condition which is likely the expected value as seen here: https://www.dndbeyond.com/monsters/16869-gelatinous-cube
How was it tested?

N/A - text update, can run tests though if that helps

Is there a Github issue this is resolving?

No

Did you update the docs in the API? Please link an associated PR if applicable.

No

Here's a fun image for your troubles

nice catch, this is great!
My only feedback is a nit (non-blocking feedback/suggestion) regarding the commit message. Commit msg guidelines can be found here: https://github.com/5e-bits/5e-database#contributing
The commit msg on this PR might align with those guidelines better if it read something like...
fix(monster): fix condition_immunities for gelatinous cube

Remove the duplicate `blinded` condition from condition_immunities, and
correctly replace it with an entry for the `deafened` condition.

https://media.wizards.com/2016/downloads/DND/SRD-OGL_V5.1.pdf#page=337

I don't have PR approval perms in this repo, but if I did this would get a big ✅

nice catch, this is great!
My only feedback is a nit (non-blocking feedback/suggestion) regarding the commit message. Commit msg guidelines can be found here: https://github.com/5e-bits/5e-database#contributing
The commit msg on this PR might align with those guidelines better if it read something like...
fix(monster): fix condition_immunities for gelatinous cube

Remove the duplicate `blinded` condition from condition_immunities, and
correctly replace it with an entry for the `deafened` condition.

https://media.wizards.com/2016/downloads/DND/SRD-OGL_V5.1.pdf#page=337

I don't have PR approval perms in this repo, but if I did this would get a big ✅

Yep sure thing, I can update that when I'm back at my desk

oh wait, i can approve 🤔 let's see...

okay i think we still need an adult (@bagelbits 😄 i'm not really sure how to figure out who has perms to run CI and merge in this repo)

nice catch, this is great!
My only feedback is a nit (non-blocking feedback/suggestion) regarding the commit message. Commit msg guidelines can be found here: https://github.com/5e-bits/5e-database#contributing
The commit msg on this PR might align with those guidelines better if it read something like...
fix(monster): fix condition_immunities for gelatinous cube

Remove the duplicate `blinded` condition from condition_immunities, and
correctly replace it with an entry for the `deafened` condition.

https://media.wizards.com/2016/downloads/DND/SRD-OGL_V5.1.pdf#page=337

I don't have PR approval perms in this repo, but if I did this would get a big ✅

Yep sure thing, I can update that when I'm back at my desk

amazing! don't feel like you're limited by my suggestion above, it was mostly meant to be an example of structure / semantics :)

And updated


Add a license

For the most part, I allow people to download, run, install, copy-paste codes from here and use it in any  way useful to them. However, it might be better to make licensing and permission to be more explicit. I create this issue to keep track of various license and their pros and cons.

I'm leaning towards MIT license now. here

Added MIT license file. Let's close this issue.


[FLINK-4027] Flush FlinkKafkaProducer on checkpoints

A user on the mailing list raised the point that our Kafka producer can be made at-least-once quite easily.
The current producer code doesn't have any guarantees
We are using the producer's callbacks to account for unacknowledged records. When a checkpoint barrier reaches the sink, it will confirm the checkpoint once all pending records have been acked.

Thank you for the review @eliaslevy!

👍

Good work @rmetzger. Well documented code and a good idea to solve the problem. I had some comments concerning concurrent accesses to pendingRecords and test stability on Travis. Once we've solved theses points, I think the PR is good to be merged :-)

Thank you for your review @tillrohrmann and @zentol . I tried addressing all your concerns.
Please let me know what you think about it.

Changes look good to me @rmetzger :-) I had only some minor comments. +1 for merging after addressing the comments.


Add hhea

Seems to fit most naturally alongside hmtx. Matches how loca flies with glyf.
Contributes to #138.
We can now ttx fonts whose hmtx is not entirely made up of long metrics (ref https://github.com/googlefonts/fontmake-rs/pull/156#issuecomment-1471750483):
$ cargo run -p fontc -- --source resources/testdata/glyphs2/Mono.glyphs
$ ttx -o - build/font.ttf
# marvel at the hhea numberOfHMetrics 1 and the 3 entry hmtx

DO NOT MERGE until on a released fontations with https://github.com/googlefonts/fontations/pull/290. Should be ok to review.

FYI https://crates.io/crates/write-fonts/0.1.4 is up


Release of pre-built whl on Windows

Hello
How are you?
Thanks for contributing to this project.
Could u release the pre-built whl on Windows 10?
Thanks

Hi @rose-jinyang. Currently windows support is community contributed & experimental. Unfortunately that means a pre-built will not be released. Once it becomes official (TBD) a wheel will be released.


Add Visual Studio 6.0 and Windows 98 SDK .prf/.gdt

Add a .prf that can handle the Visual Studio 6.0 and
Windows 98 SDKs.  This is useful for older applications
that were developed pre-NT and don't quite fit with the modern
Windows SDK headers in VS9 and onwards.
Also add a .gdt which was generated directly from this .prf.
Includes DirectSound, DirectDraw, and Direct3D headers.
Signed-off-by: Shane Peelar<EMAIL_ADDRESS>

Note that this contains a workaround for #927 .  An alternative workaround that works is editing the pshpackN.h files and adding a specific #ifdef for some preprocessor token only Ghidra uses (I used -DGHIDRA and using the syntax that Ghidra accepts there.  For example:
...
#if ... && ! defined(GHIDRA)
  //original behaviour
#endif

#if defined(GHIDRA)
#pragma pack(push, 4)
#endif


Add script to generate the QC MT for relatedness and population inference

Julia is adding v3 to this PR

@mike-w-wilson this is ready for review. I have 1 TODO for discussion though.
As I have it now, the combined v3 and v4 MT is used to determine AF, callrate, and LD-pruning, is that OK, or should they be considered independently and then shared passing variants merged?


RAT poster preview not displayed (404 error)

Where to find the issue

https://www.coronawarn.app/en/faq/results/#red_card_how_to_test "Red Card? How to go through Corona testing"
https://www.coronawarn.app/en/faq/results/#red_card_how_to_test "Rote Karte? So geht es zum Corona Test"

Describe the issue
The preview of the poster "ANTIGEN-SCHNELLTEST? SO TEILEN SIE IHR ERGEBNIS" is not shown when viewing the above FAQ articles.

There is a case mismatch in the filename extension (.png/.PNG) between the HTML image link to https://www.coronawarn.app/assets/documents/DE_CWA_RKI-Plakat_Schnelltests_v2-kl-1.png and the asset stored on https://www.coronawarn.app/assets/documents/DE_CWA_RKI-Plakat_Schnelltests_v2-kl-1.PNG.
Also there are two different versions of the poster in use (v2 and v3). The v2 version contains typos.
Steps to reproduce
Suggestions

Consolidate RAT poster versions into one version and ensure matching case between links and assets
After PRs are merged, manually check success on production website

Also consider to extend Cypress link testing to cover images, since this issue was not flagged by any of the Cypress tests.

Internal Tracking ID: EXPOSUREAPP-13689

PR https://github.com/corona-warn-app/cwa-website/pull/3049 submitted to resolve this issue

This issue is now resolved.
Verification
Successfully checked the following URLs after merge of #3049:
https://www.coronawarn.app/en/faq/results/#rat_partner
https://www.coronawarn.app/en/faq/results/#rat_what_if_positive_result
https://www.coronawarn.app/en/faq/results/#red_card_how_to_test
https://www.coronawarn.app/de/faq/results/#rat_partner
https://www.coronawarn.app/de/faq/results/#rat_what_if_positive_result
https://www.coronawarn.app/de/faq/results/#red_card_how_to_test
The miniature version of the RAT poster (png) is correctly displayed and the links to the full sized poster (pdf) all work correctly.


handle log entries containing version numbers (since chia 2.4.4)

Chia 2.4.4 included a logging format change to insert version numbers prior to the service name.
I've opened https://github.com/Chia-Network/chia-blockchain/issues/18799 (which I don't imagine will be fixed) but also fixed my local chiadog instances.
Here are the fixes which hopefully should work OK with both old and new logging formats - hopefully the regex group is robust enough to handle all possible version strings in future!

Thanks for that! This regex seems safe to add. Would be nice to add a few more tests (even if not super comprehensive) under tests/chia_log/parsers we have some examples of versioned logs here.
For lurkers: It seems that this PR got merged, so there's now also log_backcompat configuration that will make the logs work without this change in chiadog.

I would love to get this merged! Currently I'm manually copying these changes over into chiadog as I've had issues getting the log_backcompat to work, likely because my config is so old and fragile.


DryIoc.ComminServiceLocator.dll nuget package needs updated.

This package hasn't been updated to 4.0.0 https://www.nuget.org/packages/DryIoc.CommonServiceLocator.dll/3.1.0-preview-01

Good catch, thanks. Just forgot to publish it. Will do.

Published V4 packages, should be available shortly.


Changed URIs of Thing to be independent of Thing name.

Changed ThingInterface to provide a list of URIs representing the Thing. These URIs can be added (optionally) when it is required to have URI something other than the name. For example, to have a structured URL, the thing might need an URL http://server/building_a/room_1/sensor_thing_x. If metadata does not contain explicit "hrefs" for thing then the URIs are constructed out of the name as before.

Hi Ganesh
It looks like you want to "force" the URIs into a nice logical view of the system. While human-readable URIs are usually nice, since they make a system self-descriptive, they are often misused.
This nice logical view should come from the metadata in the TD.
The URI must be opaque for the client: It MUST NOT make any assumptions on its structure, and hence may not modify them or construct them in some way.

Hi Matthias,
I agree, the URI should not be used to convey heirarchy of things. However, still this change will allow keeping Thing name and uri separate. Right now the uri is formed directly from thing name. I think the Thing name can change, but the URI should remain same. For example the thing name could be "room_1_temperature" whereas the URI could based on some unique identifier for the sensor in the building.

Okay, I see where this is headed. At this point, ThingWeb is a Gateway: it looks like the origin server to the client and maps/translates/converts internally as it wishes. Thus, I can also freely choose its resource structure and pick whatever it likes from the TD---as long as it is unique.
I see no benefit to hardcode this to the href field. Everything apart from the @type definitions can change in the TD, but can easily be propagated.
Side discussion:
With "as long as it is unique," we might have a problem: It is still unclear what the unique identifier is in the TD. Sure the href needs to be unique in the namespace of the thing. However, URIs should be transparent to the user. Currently the assumption is that "name" is unique. Yet it was said that it should be something human readable... In my opinion we need the @id, which is the value that needs to be passed to the Scripting API and is the unique ID inside the JSON-LD to cross-reference.

At the moment the URIs are harcoded to be formed from a binding specific prefix + thing name. I think this anyway needs to made flexible such that gateway code states  what it would like to use instead of thing name (which has no contractual guarantee about uniqueness or immutability).
Now, the question comes about what really identifies things and its interactions - clients and proxies might like to use the thing URI (and URI of each interaction in it). But URIs can be subject to change. On the other hand @id is something which can be constrained. So, coming back to the proposed change - it allows the URIs to be constructed without restricting it to name. If we decide to use the thing id as the suffix of the URI, then the proposed change still enables it.

From what I understood, the first commit adds functionality like:

"when creating a thing via its TD, use the URIs given in the hrefs for the interactions. If there are none, use default URIs we have now for the relative URIs of the interactions."

Sounds useful for me, so I would gladly merge it in.
However, could I ask you to open separate PRs for the later commits (the extended Metadata props, the complex types and the altered internal flow)?
small incremental merges make it easier to merge without breaking the demos and other stuff built on top of thingweb.

I am sorry, this happened because of my inexperience with Git. I have done many more changes in between. This time I will try to organize it into separate pulls, each with small changes.

The plan forward is to continue working on the fork for the BACnet demonstrator. Once it is stable, I will integrate the changes manually into the ThingWeb code base and create manageable PRs from that.


[BUG] if session is timed out, does not prompt new oAuth2.0 for login

Describe the bug
if session is timed out, does not prompt new oAuth2.0 for login
To Reproduce
Steps to reproduce the behavior:

Go to URL after 24 hrs of first login
Click Book button
Shows error

Expected behavior
Should redirect to oAuth2.0 for re login
Screenshots

this has been fixed now. When the user logs in to the app, it will first check if the session is valid or not. If not, they will be redirected to the login page.


SetPixel / SetPixeli is too slow

I have a 3-d int array like:
int[ , , ] = new int[512,512,128];
which  containing 128 images each has 512*512 pixels.
I used SetPixel(i) in a for-loop but the speed is too slow.
Is there any faster way to implement this?

There sure is but it's not an Issue so this will be closed.
Don't use the SetPixel method for mass pixel manipulation. Implement it on your own. See the BitmapConext.CopyPixels method on how to access the pixels in the right order, then look at the SetPixel method.
If you want to use the SetPixel or any other WriteableBitmapEx method, then do it that way inside a BitmapContext scope to avoid an unnecessary overhead:
using (bitmap.GetBitmapContext())
{
	Color c = Colors.Red;
	for (int x = 0; x < bitmap.PixelWidth; x++)
	{
		for (int y = 0; y < bitmap.PixelHeight; y++)
		{
			bitmap.SetPixel(x, y, c);
		}
	}
}

Thank you very much.
Is there any chatting room in gitter.im? Where can I ask questions?

I used the GetBitmapContext() and now it's 4x faster. While the loading is still time-consuming. Any faster way to do this?@teichgraf


Review the Prototype Kit update instructions

What
How users update to a new version of the Prototype Kit is changing in version 13 because of changes to the update script.
Why
Now that changes to the update script make some updates automatic, guidance about how to update a prototype should be reviewed and updated: https://govuk-prototype-kit.herokuapp.com/docs/updating-the-kit
Who
Content designer, developer
Done when

[x] guidance reviewed by content designer and developer
[ ] updates reviewed by team
[ ] final guidance agreed

Updated guidance: https://docs.google.com/document/d/1WQu7PWmua-EdW8RSrp1zpOqxeZKCbJGcWVxp75fp-K8/edit#


Code snippets not showing correctly

File: get-started/08_using_compose.md
on https://docs.docker.com/get-started/08_using_compose/#defining-the-app-service there are snippets referencing the code,
they are not shown as intended. I see tags and header shown (```yaml hl_lines=”7 8” version: “3.7”). I am using chrome

Thanks for the report. This will be fixed in #11958.

This is fixed through https://github.com/docker/docker.github.io/pull/11947, which was merged, so let me close this one; thanks for contributing!!

This is fixed through https://github.com/docker/docker.github.io/pull/11947, which was merged, so let me close this one; thanks for contributing!!


Icon Request: Table

I would love a table icon!
https://fontawesome.com/icons/table?style=regular

Added!

Thank you!


[WIP] Add blog article “Maximize pod up-time in Kubernetes by utilizing PriorityClass and PodDisruptionBudget”

Hi Team,
Hope you are doing well, I am planning to write an article on "how to maximize pod uptime by utilizing PDB and PC in conjunction".
The TOC which I am thinking is something like this:

What is disruption?
What are PriorityClass and PodDisruptionBudget?
How to use PriorityClass and PodDisruptionBudget in combination to manage pod scheduling and availability?
Some use-cases?
Hands-on example?
Limitations and considerations?
Conclusion?

Motivation/Why this topic?

One of the readers came back to me after reading this article "https://kubernetes.io/blog/2023/01/12/protect-mission-critical-pods-priorityclass/" asking if they both work together.

I thought that this may be a good subject for a piece of writing. However, since this is sort of an addition to the prior article, I'm not sure whether it would be a worthy addition from the standpoint of publishing.
Additionally, I'm not sure if a second article will be of that much importance or if we should revise the earlier one.
Please let me know your thoughts on this so that I can start writing something on it or should delete this PR.
Thank you,
Sunny

Explicit hold to avoid accidental merges.
/hold

/retitle [WIP] Maximize pod up-time in Kubernetes by utilizing PriorityClass and PodDisruptionBudget
/hold cancel

/retitle [WIP] Add blog article “Maximize pod up-time in Kubernetes by utilizing PriorityClass and PodDisruptionBudget”

Hello @sunnybhambhani .
Are you planning to update this pull request or should I close it?

Hello @sunnybhambhani , please note that since there has been no activity on this PR from ~4 months, I'm closing it.
A couple of suggestions on how you can continue work on this, if you have bandwidth in the future.

Socialize your idea on the #sig-docs-blog Slack channel OR during one of the regular/monthly SIG meetings.
Once you gain consensus, open a PR.

/remove-lifecycle stale
/close


UnixPB: Correct gcc_7 conditions

Noticed the discrepancy awhile ago. I'm going to try running the change through the vagrantPlaybookCheck job as I'm not sure the condition is necessary required anymore. As can be seen from the below link, the gcc_7 task is run despite it not being intended to, but the build still succeeded: https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/OS=CentOS6,label=infra-vagrant-1/464/consoleFull
It's been succeeding in CentOS7 and CentOS8, so it's worth testing them too.

https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/478/

The above VPC run through failed as nasm wasn't installed, due to not being able to detect a version of gcc7. I checked the vagrant VMs and they haven't got them installed, so I'll remove this line entirely from the conditions: - ansible_architecture != "CentOS" and ansible_architecture != "x86_64"

Rerunning VagrantPlaybookCheck : https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/479/
I also took the opportunity to enter a comment explaining why we don't have a checksum for the gcc_7 binary we download.

All is well with the above VPC run

The only change seems to be the comment?

I've also removed the  - ansible_architecture != "CentOS" and ansible_architecture != "x86-64" from the tasks :-)

@karianna Do the two previous comments resolve your rejection of this?


Suggestion: default name of packages folder to .alpackages

I want to suggest to change the default name of the packages folder to .alpackages
Changing the name from packages to alpackages to make it crystal clear this is a folder used by the AL language extension.
Adding a leading dot makes the folder to stay on top instead of mixed up with other folders that are created by the developer, e.g. folders containing AL objects or other files that must be included with the output. The folders with a leading dot (like the .vscode folder) are considered to be folders that contain files which are essential for the development environment but excluded from output.

Good suggestion.
In the meanwhile you can change the default location by adding the following setting to your user or workspace settings:
"al.packageCachePath": "./.alpackages"

Yep, already did that in my current workspace. ;-)
Looks so nice, thanks for supporting the idea!


fix: Escape backslashes in Neo4jCsvPublisher

Summary of Changes
This is basically a re-do of #191.
Neo4jCsvPublisher currently imports data by crafting Cypher queries through string building. Problems occur in string literals when the original strings contain backslashes: literal values like \n would be converted to a newline, while a literal that is not a valid escape sequence (e.g., \_) will result in an error decoding the Cypher query.
This issue was identified and addressed in #191, but the final, accepted fix doesn't actually do anything. The confusion seems to stem from the way Python outputs string literals in a REPL-like environment:
>>> '\\'
'\\'
>>> print('\\')
\

>>> '\_'
'\\_'
>>> '\_'.replace("\\", "\\") # the accepted fix from #191
'\\_'
>>> print('\_'.replace("\\", "\\")) # note: this didn't really work!
\_

>>> print('\_'.replace('\\', '\\\\')) # the original proposal in #191 and what is done in this PR
\\_

This is a quick fix to make importing more robust (any description that contains a backslash is currently an issue in some form), but I'm of the mindset that a proper solution would be to use query parameters in these import statements rather than hardcoding string literals and trying to escape any relevant sequences. (Note that there are still ways to break these queries, e.g., by including a null byte in a string. I don't know how to solve all such problems through a string builder approach.)
Tests
n/a
Documentation
n/a
CheckList
Make sure you have checked all steps below to ensure a timely review.

[X] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[X] PR includes a summary of changes.
[X] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[X] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[X] PR passes make test

Is there any chance this can get reviewed soon? I'm hoping to contribute a Redash dashboard extractor soon, but at the moment, the extractor includes some hacks to get around this bug.
Thanks!

@jonhehir  sorry for the slip, feel free to direct ping next time .


Added my data

please add hactoberfest accepted while merging the pr.
thank you!

Please resolve the merge conflicts and update the PR. @Sashi2002

Resolved the merged conflicts and updated the PR.
Thank you!

Good job @Sashi2002
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐

SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


How to reduce latency?Now is 1 second

I use ffmpeg to publish stream. The command is like this
ffmpeg -f avfoundation -i "1" -vcodec libx264 -preset ultrafast -acodec libfaac -f flv rtmp://localhost:1935/live/myStream

2.Then one screen's browser open a webpage has stopwatch
online stopwatch
3.My another screen's browser open ssr player for play stream.
4.I take a photo contains 2 screen.And I find the latency is about 1 second.

The srs.conf has below property. RTMP降低延迟
    gop_cache       off;     queue_length    10;     min_latency     on;     mr {         enabled     off;     }     mw_latency      100;     tcp_nodelay     on;

I know it will be difficult. But to my application, reduce every 100 milliseconds, is a great improvement.

The latency is introduced by your encoder and player.

HI! :)
I'm working with VMIX to make a p2p stream for conference's and the vmix encoder have 7 seconds of delay!!
Working with OBS at 0 buffer and playing the stream with VLC i have from 2 to 3 seconds using the realtime.conf settings. 2 Seconds for a live conference can be high.. any way to reduce to 1 or less?
Thank you.

Don't use VLC,  use ckplayer


Fix reference to old spec

The multiple files section in Data Resource references a v1 spec:
https://github.com/frictionlessdata/datapackage/blob/cc38c417c5f3e35dfdcfa5090bc09852b6ca3cee/content/docs/standard/data-resource.md?plain=1#L89-L91
It should be updated to reference Table Dialect.

Suggestion:

All files in the array MUST be the same in terms of structure, format, dialect, etc. Implementations MUST be able to concatenate the files in the simplest way and treat the result as one large file.

I don't think it's necessary to reference Table Dialect, but just include "dialect" in the list of things that should be the same (not similar).


[Backend] Finding bugs in backend setup

Task
Check out the backend-setup branch, go through the codebase. Play around the codebase. Try to find bugs in the codebase.
How to report a bug
Once you find a bug, create a new issue and tag the mentors @jackfrost13 @Kajol-Kumari with the following pieces of information.

Description
Steps to reproduce the bug
Cause of the bug
Possible solutions

This issue can be assigned to multiple people
Special points for finding bugs

Hey I would like to work on it. If it is no assigned to anyone yet then please consider me so that I could start immediately.

Hey I would like to work on it. If it is not assigned to anyone yet then please consider me so that I could start immediately.(GSSoC 21)

If you find any bugs please open an issue with a brief discussion and steps to reproduce it and tag us!

Sure thankyou! @jackfrost13

@codebuzzer01 Update?

can you please assign this issue to me? GSSOC'22 participant)

Hi is this still open? I'd like to be assigned to it under GSSOC'22

@Kajol-Kumari can you please assign this issue to me? GSSOC'22 participant)

@himanshu1221  i want to work in this issue under JWOC


Release v1.11.1

Added

Add missing support for Custom email provider in EmailProviderManager #452 (duedares-rvj)

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

Project coverage is 95.81%. Comparing base (49eb8e1) to head (ef537b4).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #453   +/-   ##
=======================================
  Coverage   95.81%   95.81%
=======================================
  Files          51       51
  Lines        8461     8461
=======================================
  Hits         8107     8107
  Misses        236      236
  Partials      118      118

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


rtr doesn't allow us to express backend_port?

What We Did
I ran the following:

rtr register $(cat /tmp/rt.json) --api https://api.system-domain.com/ --skip-tls-verification --client-id tcp_emitter --client-secret 'REDACTED' --oauth-url https://uaa.sys-domain.com/

Where the contents of the JSON file are:

[{"route":"tcp.system-domain.com","port":1034,"backend_port":3306,"ip":"<IP_ADDRESS>","ttl":60,"log_guid":"mysql_instance"}]

What Happened
$ nc -v tcp.system-domain.com 1034
> Connection to tcp.pcf.hooliroof.com port 1034 [tcp/activesync] succeeded!
[No response]

What We Expected
$ nc -v tcp.system-domain.com 1034
Connection to tcp.pcf.hooliroof.com port 1034 [tcp/activesync] succeeded!
Q
5.7.24-26-log�
kb%

(ie, the standard greeting string from a MySQL server).
What we think is going on
The rtr documentation doesn't include backend_port in the documentation, and we worry that via rtr there's no way to specify this important piece of information to complete the loop.
We were able to get the expected behavior by calling the API directly:
#!/usr/bin/env bash

curl -vvv -H "Authorization: bearer REDACTED" \
  -X POST http://api.system-domain.com/routing/v1/tcp_routes/create -d '
[{
  "router_group_guid": "xxx-yyy",
  "port": 1034,
  "backend_ip": "<IP_ADDRESS>",
  "backend_port": 3306,
  "ttl": 120,
  "modification_tag":  {
    "guid": "qqq-ggg",
    "index": 1
  }
}]'

Thanks @menicosia
We looked through it and unfortunately rtr doesn't support TCP routing commands. We want to know why you are trying to use CLI instead of HTTP API so we can see whether there is a need to add TCP routes support to rtr. Also, PRs are welcome!
Thanks!
@mike1808 and @rodolfo2488 , CF Networking Program Members

Hi! I was using rtr as a way of exploring/spiking out how TCP Router
would work in our product. The CLI was convenient for doing a spike, but
ultimately wasted a bit of time because it seems to do the thing, but after
we wrestled with it a little bit, we realized that in fact it does not. :(
Instead we spent a reasonable amount of time puzzling over the API and got
things working with curl directly. This is more in-line with what we’d do
in production code, as I don’t think we’d prefer to call the CLI.
In general if the CLI could work for roughing things out in this way, our
use of routing’s release would go more smoothly.
On Mon, Jul 8, 2019 at 15:55 Rodolfo Sanchez<EMAIL_ADDRESS>wrote:

Thanks @menicosia https://github.com/menicosia
We looked through it and unfortunately rtr doesn't support TCP routing
commands. We want to know why you are trying to use CLI instead of HTTP API
so we can see whether there is a need to add TCP routes support to rtr.
Also, PRs are welcome!
Thanks!
@mike1808 https://github.com/mike1808 and @rodolfo2488
https://github.com/rodolfo2488 , CF Networking Program Members
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry/routing-api-cli/issues/11?email_source=notifications&email_token=AABU6TFMAR3WAQ7JO3ZRZ23P6PAU5A5CNFSM4H3M4ZYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZOSN6A#issuecomment-509421304,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABU6TGPBQJXST2G5OSPKB3P6PAU5ANCNFSM4H3M4ZYA
.

--
Marco Nicosia
Product Manager
Pivotal Software, Inc.
<EMAIL_ADDRESS>c:<PHONE_NUMBER>

Hi @menicosia , we are sorry to hear about the time wasted trying to work with the cli. Unfortunately, we do not have plans to work on this, and given the amount of other prioritized work, it is unlikely this gets added.
From an external perspective, would it be helpful if we added a loud note in the README specifying that tcp routing commands don't work? Otherwise, PR's are always welcome.
Thanks,
@mike1808  and @KauzClay ,  CF Networking Program Members

We have updated the README with a note on the status of this project. We are closing the issue, but please re-open if you have other questions
Thanks,
@KauzClay and @tcdowney , CF Networking Program Members


Fix shallow when comparing arrays of objects

I noticed shallow returns false when comparing identical arrays of objects, e.g.:
shallow(
  [
    { foo: 'bar' },
    { asd: 123 }
  ],
  [
    { foo: 'bar' },
    { asd: 123 }
  ],
)

This returns false using the latest version, but I think this should be treated as equal.
I also added some tests for shallow while I was messing around :)

Thanks for opening this up, but I don't think it's how shallow works. It's like deepequal.
https://www.npmjs.com/package/shallowequal works like this:
> shallow = require('shallowequal');
[Function: shallowEqual]
> shallow(
...   [
...     { foo: 'bar' },
...     { asd: 123 }
...   ],
...   [
...     { foo: 'bar' },
...     { asd: 123 }
...   ],
... )
false

btw, I'd like to have your test to be merged in..

Yes you are right, it's cool that we can pass a custom equality function which is super useful!
I just found shallow a bit weird, as comparing object works fine:
expect(shallow(
  { foo: 'bar', asd: 123 },
  { foo: 'bar', asd: 123 }
)).toBe(true);

Comparing arrays works fine:
expect(shallow(
  [1, 2, 3],
  [1, 2, 3]
)).toBe(true);

So why comparing arrays of objects does not work?
// This fails currently
expect(shallow(
  [
    { foo: 'bar' },
    { asd: 123 }
  ],
  [
    { foo: 'bar' },
    { asd: 123 }
   ],
)).toBe(true);

But I respect the decision of the maintainers, thought it would be a good addition for zustand users.
Feel free to revert the shallow related changes and merge the tests if you find them useful!

But I respect the decision of the maintainers

To be fair, this is not my preference at all. As I understand, it's the definition of shallow equal.

thought it would be a good addition for zustand users.

What you are suggesting is deep equal.
My preference here is instead of adding deepequal helper, we encourage to use existing libraries.
https://lodash.com/docs/4.17.15#isEqual should work.
import isEqual from 'lodash.isequal'

  useStore(someSelector, isEqual)

Feel free to revert the shallow related changes and merge the tests if you find them useful!

Thanks. Will do.


Suppress info messages

Weights and Biases version: 0.8.5
Python version: 3.7.3
Operating System: Linux

Description
WANDB prints a lot infos to the jupyter cell like:
INFO - wandb.run_manager - file/dir modified: /home/ubuntu/Projects/XX/XX/wandb/run-20190729_122935-r8x77nbl/wandb-summary.json
INFO - wandb.run_manager - file/dir modified: /home/ubuntu/Projects/XX/XX/wandb/run-20190729_122935-r8x77nbl/wandb-history.jsonl
INFO - wandb.run_manager - file/dir modified: /home/ubuntu/Projects/XX/XX/wandb/run-20190729_122935-r8x77nbl/model-best.h5

Is there a way to suppress these messages?
What I Did
Read the entire doc, but did not found something related

This shouldn't be happening in the most recent release.  Is there anything special about your jupyter environment or instructions on how I could recreate it?

@vanpelt I am using W&B in my own pytorch pipeline and I am very particular with the output on my stdout. I really need to suppress all terminal outputs from W&B. Is there a kwarg or a global settings for the functions to suppress this?? Really need it.

Hey @AakashMallik are you running in Windows or Unix?  Also are you always running python from the command line or within a jupyter kernel?  If it's unix and the command line, you can disable stdout mirroing by adding this before your call to wandb.init:
from wandb import io_wrap
def redirect_noop(self):
    pass
io_wrap.FileRedirector.redirect = redirect_noop

If it's one of the other scenarios, let me know and I'll share some code.

Hey @AakashMallik are you running in Windows or Unix? Also are you always running python from the command line or within a jupyter kernel? If it's unix and the command line, you can disable stdout mirroing by adding this before your call to wandb.init:
from wandb import io_wrap
def redirect_noop(self):
    pass
io_wrap.FileRedirector.redirect = redirect_noop

If it's one of the other scenarios, let me know and I'll share some code.

Silly me. Just found this thread https://github.com/wandb/client/issues/337
Now I am setting the env variable from the pipeline itself. All good now. Thanks for your reply.

Hi, I have the same problem, and I'm running on ipython. I suppose it's the same as jupyter. I tried setting os.environ['WANDB_SILENT'] = 'true', but that did not work either. @vanpelt, you have some code to share that may solve the problem?

Actually, I found that the info can be suppressed following the instructions here: https://docs.wandb.com/library/integrations/jupyter#disable-info-messages-from-wandb-in-jupyter

We're working on a big new release that will address this issue for good.  It's due out at the end of the month!

Hey folks,
This issue has been resolved in the present wandb package.
Closing this thread.
Please feel free to comment on this thread if the issue persists any longer. :smile:


HTTPS with Licode. Error during WebSocket handshake: Unexpected response code: 404

Hello !
Thank you for sharing your licode project, is very useful !!
I have problem with https and licode. Its caused because webRTC api doesnt support now video over normal http. Im ussing this fast start up tutorial:
http://licode.readthedocs.io/en/stable/from_source/
And i want to access to server from exterior of local network.

I change licode_config with:
config.erizoController.hostname = '';
config.erizoController.port = 443;
// Use true if clients communicate with erizoController over SSL
config.erizoController.ssl = true;
config.erizoController.listen_ssl = true;

I generate certificates with openssl (.key and .cert). I reference them on licode_config.

I use ngrok for exposing local server behind NATs and firewalls to the public internet over secure tunnels. I redirect traffic to uri generated to localhost:3001.

I can now access to local web camera and audio but I have this error:
erizo.js:6055 WebSocket connection to 'wss://<IP_ADDRESS>/socket.io/?EIO=3&transport=websocket' failed: Error during WebSocket handshake: Unexpected response code: 404

What is the problem? if I change <IP_ADDRESS> and set ngrok uri i have also problems.
Thank you so much in advance :))
Sara.

Replace the wss:// with https:// and open the URL in a new tab so you can confirm the self signed certificate warning and then the error will gone.
Please use the forum for asking questions.


Add device_class property to Systemmonitor sensor

Description:
Add the device_class property for the last_boot sensor.
Related issue (if applicable): fixes #19325
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

#2302

I'm still having this issue on 0.86.3.  None of the format options from https://github.com/home-assistant/home-assistant-polymer/pull/2087 seem to work
        type: entities
        title: HA Docker
        show_header_toggle: false
        entities:
          - entity: sensor.uptime
            name: HA Docker Uptime
            format: relative

Displays as


Error debugging and build in Git PowerShell command and Import Android Studio 1.1.0

I want to use this project for build an application.So when i clone it to my repository and making build i get build failed with an exception that "Cannot evaluate module ime : Configuration with name 'default' not found". I create my own release key for key store in android studio 1.1.0 and here is  location E:\GitHubCloneProject\AddSubmoduleAndroidStudio\CloneProject\java\keystores\android.jks
and also set  ANDROID_HOME=E:\Android Sdk   in  my system environment variable.
Here the link is given that i follow the procedure for initialize,update and add submodule.
https://github.com/austimkelly/my-android-project/wiki/How-to-Use-the-Project
My git repository url is
https://github.com/amirulcse10022/CloneProject
Also some screen shot given below what i actually try.

when i try to import in my android studio i get the error " Can not invoke method readLine() on null Object". I use gradle 2.2.1 version.  Here some screen shot given below.

please suggest me why i can't build properly and unable to import in my android studio 1.1.0.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/12839533-error-debugging-and-build-in-git-powershell-command-and-import-android-studio-1-1-0?utm_campaign=plugin&utm_content=tracker%2F493413&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F493413&utm_medium=issues&utm_source=github).

duplicate.


URL Cleanup

This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener).
HTTP URLs that Could Not Be Fixed
These URLs were unable to be fixed. Please review them to see if they can be manually resolved.

[ ] http://xslthl.sf.net (301) with 4 occurrences could not be migrated:
(https result AnnotatedConnectException).
[ ] http://exslt.org/common (404) with 1 occurrences could not be migrated:
(https result SSLHandshakeException).

Fixed URLs
Fixed But Review Recommended
These URLs were fixed, but the https status was not OK. However, the https status was the same as the http request or http redirected to an https URL, so they were migrated. Your review is recommended.

[ ] http://<IP_ADDRESS>/ (AnnotatedConnectException) with 2 occurrences migrated to:
https://<IP_ADDRESS>/ (https result AnnotatedConnectException).
[ ] http://<IP_ADDRESS>:8080 (ConnectTimeoutException) with 1 occurrences migrated to:
https://<IP_ADDRESS>:8080 (https result ConnectTimeoutException).
[ ] http://<IP_ADDRESS> (ConnectTimeoutException) with 1 occurrences migrated to:
https://<IP_ADDRESS> (https result ConnectTimeoutException).
[ ] http://<IP_ADDRESS> (ConnectTimeoutException) with 1 occurrences migrated to:
https://<IP_ADDRESS> (https result ConnectTimeoutException).
[ ] http://<IP_ADDRESS>:31991 (ConnectTimeoutException) with 1 occurrences migrated to:
https://<IP_ADDRESS>:31991 (https result ConnectTimeoutException).
[ ] http://<IP_ADDRESS>:32060 (ConnectTimeoutException) with 1 occurrences migrated to:
https://<IP_ADDRESS>:32060 (https result ConnectTimeoutException).
[ ] http://<IP_ADDRESS>:32123 (ConnectTimeoutException) with 1 occurrences migrated to:
https://<IP_ADDRESS>:32123 (https result ConnectTimeoutException).
[ ] http://dataflow-server.cfapps.io (ReadTimeoutException) with 2 occurrences migrated to:
https://dataflow-server.cfapps.io (https result ReadTimeoutException).

Fixed Success
These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended.

[ ] http://cloud.spring.io/spring-cloud-dataflow/ with 1 occurrences migrated to:
https://cloud.spring.io/spring-cloud-dataflow/ (https result 200).
[ ] http://cloud.spring.io/spring-cloud-skipper/ with 2 occurrences migrated to:
https://cloud.spring.io/spring-cloud-skipper/ (https result 200).
[ ] http://docs.spring.io/spring-boot/docs/current/reference/html/howto-logging.html with 1 occurrences migrated to:
https://docs.spring.io/spring-boot/docs/current/reference/html/howto-logging.html (https result 200).
[ ] http://docs.spring.io/spring-cloud-dataflow-server-kubernetes/docs/current-SNAPSHOT/reference/htmlsingle/ with 1 occurrences migrated to:
https://docs.spring.io/spring-cloud-dataflow-server-kubernetes/docs/current-SNAPSHOT/reference/htmlsingle/ (https result 200).
[ ] http://docs.spring.io/spring-cloud-dataflow/docs/ with 4 occurrences migrated to:
https://docs.spring.io/spring-cloud-dataflow/docs/ (https result 200).
[ ] http://github.com/ with 1 occurrences migrated to:
https://github.com/ (https result 200).
[ ] http://stackoverflow.com with 1 occurrences migrated to:
https://stackoverflow.com (https result 200).
[ ] http://stackoverflow.com/tags/spring-cloud-dataflow with 2 occurrences migrated to:
https://stackoverflow.com/tags/spring-cloud-dataflow (https result 200).
[ ] http://waffle.io/spring-cloud/spring-cloud-dataflow-server-kubernetes with 2 occurrences migrated to:
https://waffle.io/spring-cloud/spring-cloud-dataflow-server-kubernetes (https result 200).
[ ] http://bit.ly/Celsius-GA-stream-applications-rabbit-docker with 1 occurrences migrated to:
https://bit.ly/Celsius-GA-stream-applications-rabbit-docker (https result 301).
[ ] http://kubernetes.io/docs/user-guide/configmap/ with 1 occurrences migrated to:
https://kubernetes.io/docs/user-guide/configmap/ (https result 301).
[ ] http://kubernetes.io/docs/user-guide/prereqs/ with 1 occurrences migrated to:
https://kubernetes.io/docs/user-guide/prereqs/ (https result 301).
[ ] http://kubernetes.io/docs/user-guide/secrets/ with 1 occurrences migrated to:
https://kubernetes.io/docs/user-guide/secrets/ (https result 301).
[ ] http://repo.spring.io/ with 1 occurrences migrated to:
https://repo.spring.io/ (https result 302).

Ignored
These URLs were intentionally ignored.

http://docbook.org/ns/docbook with 4 occurrences
http://docbook.sourceforge.net/xmlns/l10n/1.0 with 2 occurrences
http://localhost:8761/eureka/ with 1 occurrences
http://localhost:8888 with 1 occurrences
http://www.w3.org/1999/XSL/Format with 2 occurrences
http://www.w3.org/1999/XSL/Transform with 6 occurrences
http://www.w3.org/1999/xlink with 1 occurrences

merged


x/tools/go/types/typeutil: wrong computed method set

What version of Go are you using (go version)?

$ go version
go version go1.13.7 linux/amd64

What did you do?
package main

import (
	"fmt"
	"go/ast"
	"go/importer"
	"go/parser"
	"go/token"
	"go/types"
	"log"
	"reflect"

	"golang.org/x/tools/go/types/typeutil"
)

const input = `
package abc

type Conn struct {
	frameReader
	PayloadType int
}

type frameReader interface {
	PayloadType() byte
}
`

var fset = token.NewFileSet()

func main() {
	f, err := parser.ParseFile(fset, "hello.go", input, 0)
	if err != nil {
		log.Fatal(err)
	}

	conf := types.Config{Importer: importer.Default()}
	info := &types.Info{Types: make(map[ast.Expr]types.TypeAndValue)}
	pkg, err := conf.Check("cmd/hello", fset, []*ast.File{f}, info)
	if err != nil {
		log.Fatal(err)
	}

	ct := pkg.Scope().Lookup("Conn").Type()

	var cache typeutil.MethodSetCache
	var methetset = cache.MethodSet(ct)
	fmt.Println(methetset)
		// MethodSet {
		// 	method (cmd/hello.Conn) PayloadType() byte
		// }

	fmt.Println(reflect.TypeOf(Conn{}).NumMethod())
		// 0
}

type Conn struct {
	frameReader
	PayloadType int
}

type frameReader interface {
	PayloadType() byte
}

What did you expect to see?
Type Conn has no methods.
What did you see instead?
Type Conn has one method.

But Conn does have a method, from the embedded frameReader type.  Why should it have no methods?

But reflect says it hasn't.

Did you reverse "what did you expect to see" and "what did you see instead"?
Hmmm, looks like you did.  When I run the program, it prints 0 for NumMethod.

Oh, sorry, I get it now.  The method should be hidden by the field of the same name.  The reflect package sees that, but golang.org/x/tools/go/types/typeutil does not.
We appreciate the bug reports, but it will save time if you can say more clearly what the issue is, rather than leaving us to work it out.  Thanks.

CC @griesemer

Smaller reproducer: https://play.golang.org/p/TRM-fN9nvVd
The primary function types.LookupFieldOrMethod correctly reports a field, but types.NewMethodSet returns the method. Looks like a bug in the method set computation.
(As an aside, types.NewMethodSet is not directly used by go/types, so there's no danger of go/typesdirectly being compromised by this - it was requested forx/tools/go/types/typeutil`. I should have said no at that time... :-)


Add opensearch support

Advice I have seen online suggests to turn on "compatibility mode" in OpenSearch. But I did not have any luck with this approach. I have managed to get OpenSearch working with stac-fastapi-elasticsearch by downgrading elasticsearch[async] from 7.17.9 to 7.13.4,  before compatibility checks. This required refactoring the query syntax to an older version. For example...
7.17.9
await client.indices.create(
        index=index_by_collection_id(collection_id),
        mappings=ES_ITEMS_MAPPINGS,
        settings=ES_ITEMS_SETTINGS,
        ignore=400,  # ignore 400 already exists code
    )
    await client.close()

7.13.4
await client.indices.create(
        index=index_by_collection_id(collection_id),
        body={"mappings":ES_ITEMS_MAPPINGS,
              "settings": ES_ITEMS_SETTINGS},
        ignore=400,  # ignore 400 already exists code
    )
    await client.close()

As python clients move apart, OpenSearch support would require a separate database_logic.py (and maybe a separate repo?) that is configured to use the opensearch-py library.

Summarizing @philvarner from the STAC Community Meetup:
Something we should probably do is break apart those implementations so that there is one for each and they share almost everything except they have a wrapper around the clients. Like a stac-fastapi-*search repo with interchangeable OpenSearch and Elasticsearch wrapper modules.
A little bit of work to implement but worth it to make completely compatible.

Hey @jonhealy1 I wonder if we can merge our work. I have been working on a fork of your add_opensearch branch here: https://github.com/AtomicMaps/stac-fastapi-elasto-opensearch/tree/add-opensearch

Hi that would be really good. What are you thinking for how a User chooses which db they want? I was playing around with a couple of things but don't have anything really good yet. The first thing I thought was just an env variable.

What you have looks really good. I see you're using an env variable to switch too. It's probably the easiest way. I have another branch where I was fooling around with having a separate setup.py for opensearch so we could publish stac-fastapi-opensearch on pypi but I haven't got everything working yet.

Thanks. Yeah, I could not think of a better way than using an environment variable.
Separate setup.py files sounds good. I am finishing up some debugging then should have a version that passes all the tests up in an hour or so

Just pushed updates that pass tests on both ES and OS. How would two setup.py files work?

What you have looks really good. I am thinking maybe we should merge what you have and then think about going from there. I am not quite sure how it would work right now.

I have something I am working on now. Three packages. A core package with common code like core.py, then a package each for elasticsearch and opensearch. Basically app.py injects the right DatabaseLogic to the core package. https://github.com/stac-utils/stac-fastapi-elasticsearch/tree/common_core/stac_fastapi

@jamesfisher-gis I tried to add you to a reviewer on this pr - https://github.com/stac-utils/stac-fastapi-elasticsearch/pull/186. I think you probably need to be added via stac-utils. How do you feel about adding your opensearch changes to this branch?

Nice. I am not in the stac-utils organization yet. I'm happy to join and help with maintaining this project.
I will submit a PR with my changes in an hour and request to merge into the add-opensearch branch.

Nice. I am not in the stac-utils organization yet. I'm happy to join and help with maintaining this project.

let me see what I can do about that.

That would be great. Can you add your changes to this branch instead - https://github.com/stac-utils/stac-fastapi-elasticsearch/tree/common_core. I know it's not ideal but I think it's a really good solution.

Nice. I am not in the stac-utils organization yet. I'm happy to join and help with maintaining this project.

let me see what I can do about that.

Invited you with the Maintain permission level, which should allow you do most anything you need to.

@philvarner I still can't add James as a reviewer - maybe it's just a temporary glitch

@philvarner I still can't add James as a reviewer - maybe it's just a temporary glitch

I just accepted the invite. It should work now

Working now!

I think we should maybe look at merging this before we merge in the opensearch code. https://github.com/stac-utils/stac-fastapi-elasticsearch/pull/177 What do you think? It would mean updating the opensearch logic

Finishing this opensearch work will be a major accomplishment and we will definitely release a new version of the project.

I think we should maybe look at merging this before we merge in the opensearch code. #177 What do you think? It would mean updating the opensearch logic

Yeah, sounds good. It looks good to me. I will sync those changes with the add_opensearch tomorrow.


Support network address types in PostgreSQL

Provide parsers, serializers, tests and docs for the https://www.postgresql.org/docs/current/datatype-net-types.html
As an example, see the string types support in PostgreSQL https://github.com/userver-framework/userver/blob/develop/postgresql/include/userver/storages/postgres/io/string_types.hpp

Added in 157b902cfcfa489574aa7a5d9b16de309f4029a1


Be more specific regarding the cached loader.

Be more explicit about not needing to enable the cached.Loader manually, unless using some custom loaders.
While an explicit setting is better than an implicit one, I still think the documentation should mention that this optimization is already there for free, unless a custom loader has to be used, in which case the developer will come accross that bit of django documentation anyway.

Merged in fc0cf64ac6615905ee6207314b935df3e979f287 - thanks @minusf!


Show HMM logo for each family (if available)

Is your feature request related to a problem? Please describe.
For example, the page
https://ampsphere.big-data-biology.org/family?accession=SPHERE-III.003_141
could have the logo
Describe the solution you'd like
See the logo.

The HMMLogo and SeqLogo are available for download.
Do you mean explicitly showing it on the family page?

Frankly, I don't see as much point in downloading them as in showing them.

After some discussion with Celio, I removed all HMM logos and only display sequence logo on the family page.
I think we can also make it downloadable as SVG file if needed (#37).


Could not pass event PlayerItemConsumeEvent

Another little error, was being spammed quite a bit. https://pastebin.com/raw/m3HUCr90

Server version: Paper 1.12.2-b1550
OldCombatMechanics version: 1.7.0-b57

Not quite sure, as it happened to a random player and I just managed to spot the error while going through some logs. Don't have much info on this.

@AfkF24 This issue should now be fixed in test build 58. Please try the new build.

Yup, seems to be fixed. Thanks!


Ensure we get the correct URL if you are using Pro

The code seems to compare the string "pro" with the class constant
License.PRO - this fix should take care of that mis-match.
Thanks for the useful software! Very much appreciated.

Thanks you too. Any help is appreciated.

The code seems to compare the string "pro" with the class constant License.PRO - this fix should take care of that mis-match.
Thanks for the useful software! Very much appreciated.

Thanks you too. Any help is appreciated.


KeepInventory

Me and my friends are playing on a server and we are trying to disable this mod because we can't override this mod with gamerule keepinventory. Is there a way to override this command? Because with keepinventory on, the player keeps the items and can dupe the inventory by right clicking the gravestone. Im not sure if this is the mod's intention or my fault. Please help. ty

Are you using the latest version of the mod. It should have been fixed in that version

Yes, I believe this is the latest version included within the mudpack.

The latest version is 2.0.0-beta.7. Update to that version and your problem will be fixed


added design UI

Issue #416

Related Issue
Closes #416

Description
The change of UI of website is done on figma
Some sections are maintained as it is as it is enhancing the website , few changes of different sections are done.
Screenshots
Attaching FIGMA URL : https://www.figma.com/file/e5hMnBmdVbLFvQROyzeAuD/SSIT?type=design&node-id=0%3A1&mode=design&t=nOrtm3rqE8bBLZiK-1
Checklist

[x] My code adheres to the established style guidelines of the project.
[x] I have included comments in areas that may be difficult to understand.
[x] My changes have not introduced any new warnings.
[ ] I have conducted a self-review of my code.

The design file is in asset folder named as desktop 1


[CommonHTML] Anomaly caused by accented character inside \text{}

I have come across an anomaly in MathJax for which I tried to furnish the proverbial minimal example but failed. I can nevertheless furnish a page without apparent problems, indicate the very slight change that will trigger the problem and screenshots of both.
The page is https://cdi2tp.math.tecnico.ulisboa.pt/praticas/3
To see the problematic area expand the last "Solução" by clicking the black triangle to its left. You will see something like this.

If one adds an acute accent to character a in the word contrario in the begin{cases}\end{cases} structure, then one gets what follows.

My attempts at replicating this in simpler circumstances have failed miserably so far.

Thanks for reporting this.
I see the problem in Chrome and Firefox; it only seems to affect the CommonHTML output. We'll look into it.

MathJax doesn't know the bounding boxes for characters that are not in the MathJax fonts (like the accented letters), and so it must measure them in order to determine their size.  But when an element is in a container with display:none (as contents of the <details> element effectively are), the browser doesn't lay out the content, and returns 0 for any measurement MathJax makes.  This means MathJax gets the wrong size for those characters when they are typeset while they are not visible.
The HTML-CSS output jax moves the math to a non-hidden location in this case, but CommonHTML doesn't.  Perhaps that should be done here as well.

The issue1353 branch of my fork of MathJax includes a work-around.

=> Merged

=> In test suite
MathMLToDisplay/Characters/issue1353.html


Update prod-rucio-daemons.yaml

Doubles reaper pods to observe deletion rate changes during DC24 pre-test

Hello @Panos512
I advise we should consult @ericvaandering, given that there is a comment line above it asking us not to.
https://github.com/dmwm/rucio-flux/blob/81e2a4eda9e48736ad334a432781956ab566d6ff/apps/production/prod-rucio-daemons.yaml#L1
Is the current deletion rate insufficient for the tests?

Thanks @dynamic-entropy. @ericvaandering has said that we can safely double or even triple this number. This has helped a lot with deletions actually: https://monit-grafana.cern.ch/d/mtQFDScGk/cms-fts-metrics?orgId=11&refresh=5m&var-vo=cms&var-group_by=dst_rse&var-src_rse=All&var-dst_rse=All&var-fts_server=All&var-activity=Data Challenge&var-protocol=All&var-bin=60s&from=1702458000000&to=now&viewPanel=62

Then what does the comment warn against? and why? (Should it be removed?)
If there is more work to do, I believe it should help. But the intention of my question is, is it needed?
Also, I do not think the plot says that it helped.
Here's a plot for last 3 hours of deletion, binned at 1 hr, there has not been any significant deletion since your change.
https://monit-grafana.cern.ch/d/mtQFDScGk/cms-fts-metrics?orgId=11&refresh=5m&var-vo=cms&var-group_by=dst_rse&var-src_rse=All&var-dst_rse=All&var-fts_server=All&var-activity=Data Challenge&var-protocol=All&var-bin=1h&from=now-3h&to=now&viewPanel=62


Line length bug

This is a very small bug! I'm ending up with a DKIM header like this:
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=example.com; q=dns/txt; s=mail4096;
 bh=BVXqYirX/sH5OLE4KG5IvoBFi4B8iEGJdptQWgW0fqI=;
 h=from:reply-to:subject:date:message-id:to:mime-version;
 b=Hv9uydidKVE9TPoKAp9KEA/GfLMFQ8V0id53H2Q6gzm8JyBsjgaUbKPYhYHDUwJUHFpaZ8W8K6/D
 LpjHkejg8HWiX4mnGks1KXVshDmaJJCCd0k0gJP5KU5VG3OFU3M3NuOJ+U845L+2HJ8wFX6Q6ELH
 a3QPIZy5PfMIFTuVWOCcQgES36aZl8cR5y2ebnD8ovP7irKZW0+v0+tto1Oj22QrXcvHHT4Oai2E
 m1cn/EUhwb/4Te7bEgzSbwbFy8AhWsycz9DvVtEN2+hJ21rgOW4Uw+INaMI6bz6LbV2e5ny2VuYf
 4k0hPNHb+whomEzfA2c0895v/dcd91NE4FwOMis4MqBCjQhaansOuxHeTumWrJZ1n63iYIG2m1PQ
 kdTID0w0VH1JauWZHDdRvRmr59fFA7I/L/hTkF9rNClsV4/fn9EVojEQpqC1Gy+gEU17RJJ8ttUW
 J+OiyDFUSqyk/LNyTH3DqcddhkE7P7a1RQfuWccQe15b2B6VcXUCikZJ3/UUgwBCOoULzHx8N5Be
 3lFts1caWcSXdmAWd4irK5I0ym623EvjWai4VFEGuPdDegkeFyGw1lTE6x+Qk40rU+CUfhIoOhRc
 vkwWiAz7JdbW1q5tb4Tl0Wq1a+3rTIf4l/aST/5IzPPQqzwdVjxHCHUdQ+9ZlGRuPtwOMMSBll8=

The first line of the signature is 2 chars longer than the rest, ending up at 79 chars in this example, 1 char over spec. I suspect you're wrapping the signature value to 76 chars and then appending it to the header chunk returned from dkim-signer's generateDKIMHeader function, which ends with the extra b=. The rest of the lines end up as 77 chars because of the leading FWS, but that is within limits.

Good catch. Released v1.0.4 that fixes this issue. 77 bytes is an awkward length anyway, so I changed it to make sure all lines are not longer than 76 bytes. Actual change can be seen here: https://github.com/andris9/dkim-signer/commit/b24db1af973891145b7c68635b66b9f1a9ffe9ce#diff-5057dc1827f0157a2ae0197d424e4417L57

Btw. Usually I like to keep my lines not longer than 76 even though 78 would be valid as well. Quoted-printable content requires lines to be 76 bytes, base64 does not require it but is easier to handle as 76 divides with 4 and switching between different lengths for content and headers doesn't seem reasonable.

That's great, looks perfect now, thanks.


Cleanup Ripple button example

Closes
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

Added a couple more polish items:

Made it so you can click multiple times and a new ripple appears each time without waiting for the last ripple to finish. This is done by making each ripple have a unique key derived from the coordinates.
Added the example to the Button docs page.
Show ripple in screenshot.


fix(docs/cache): replace 'clone' in arguments table by 'makeCacheKey'

I just replace 2nd 'clone' option in arguments table of 'cache' hook by 'makeCacheKey'.
There was 2 options named 'clone'

Thank you!


Correction for raw affiliation Centre d'histoire du XIXe siècle; Sorbonne Université

Correction needed for raw affiliation Centre d'histoire du XIXe siècle; Sorbonne Université
raw_affiliation_name: Centre d'histoire du XIXe siècle; Sorbonne Université
new_rors: 02en5vm52;04zjb4t38;00mpxgs49;04hrxxd90
previous_rors: 02en5vm52;04zjb4t38;00mpxgs49
works_examples: W2052277749;W4214791089;W2970925488;W4312208075;W2740702740
contact: d3b0ca11d296127d1ee9acc83816aaf5:e17570c8b118e1028e2cc01ba0 @ sorbonne-universite.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-01. The new affiliations should be visible within the next 7 days.


组播源失效

foodie_hotel_url = "http://www.foodieguide.com/iptvsearch/hoteliptv.php"链接失效了
湖南电信 page: 1 results num: 0
湖南电信:No results found
湖北联通 page: 1 results num: 0
湖北联通:No results found
重庆联通 page: 1 results num: 0
重庆联通:No results found
山东联通 page: 1 results num: 0
山东联通:No results found
浙江电信 page: 1 results num: 0
浙江电信:No results found
江苏电信 page: 1 results num: 0
江苏电信:No results found
河北联通 page: 1 results num: 0
河北联通:No results found
北京电信 page: 1 results num: 0
北京电信:No results found
四川电信 page: 1 results num: 0
四川电信:No results found
青海联通 page: 1 results num: 0
青海联通:No results found
海南电信 page: 1 results num: 0
海南电信:No results found
福建电信 page: 1 results num: 0
福建电信:No results found
内蒙古电信 page: 1 results num: 0
内蒙古电信:No results found
江西电信 page: 1 results num: 0
江西电信:No results found
山西电信 page: 1 results num: 0
山西电信:No results found
湖北电信 page: 1 results num: 0
湖北电信:No results found
重庆电信 page: 1 results num: 0
重庆电信:No results found
广东电信 page: 1 results num: 0
广东电信:No results found
天津联通 page: 1 results num: 0
天津联通:No results found
新疆电信 page: 1 results num: 0
新疆电信:No results found
河南联通 page: 1 results num: 0
河南联通:No results found
山东电信 page: 1 results num: 0
山东电信:No results found
安徽电信 page: 1 results num: 0
安徽电信:No results found
黑龙江联通 page: 1 results num: 0
黑龙江联通:No results found
云南电信 page: 1 results num: 0
云南电信:No results found
吉林电信 page: 1 results num: 0
吉林电信:No results found
河北电信 page: 1 results num: 0
河北电信:No results found
浙江联通 page: 1 results num: 0
浙江联通:No results found
上海电信 page: 1 results num: 0
上海电信:No results found
贵州电信 page: 1 results num: 0
贵州电信:No results found
北京联通 page: 1 results num: 0
北京联通:No results found
广西电信 page: 1 results num: 0
广西电信:No results found
天津电信 page: 1 results num: 0
天津电信:No results found
陕西电信 page: 1 results num: 0
陕西电信:No results found
山西联通 page: 1 results num: 0
山西联通:No results found
辽宁联通 page: 1 results num: 0
辽宁联通:No results found
甘肃电信 page: 1 results num: 0
甘肃电信:No results found
内蒙古联通 page: 1 results num: 0
内蒙古联通:No results found
宁夏电信 page: 1 results num: 0
宁夏电信:No results found
Foodie hotel search:   0%|          | 0/26 [00:00<?, ?it/s]
Foodie hotel search:   4%|▍         | 1/26 [00:27<11:19, 27.18s/it]
Foodie hotel search:   8%|▊         | 2/26 [00:30<05:11, 12.96s/it]
Foodie hotel search:  12%|█▏        | 3/26 [00:31<02:50,  7.43s/it]
Foodie hotel search:  15%|█▌        | 4/26 [01:02<06:15, 17.06s/it]
Foodie hotel search:  19%|█▉        | 5/26 [01:04<04:01, 11.50s/it]
Foodie hotel search:  23%|██▎       | 6/26 [01:05<02:36,  7.85s/it]
Foodie hotel search:  27%|██▋       | 7/26 [01:26<03:55, 12.38s/it]
Foodie hotel search:  31%|███       | 8/26 [01:28<02:42,  9.00s/it]
Foodie hotel search:  35%|███▍      | 9/26 [01:29<01:49,  6.43s/it]
Foodie hotel search:  38%|███▊      | 10/26 [01:51<03:00, 11.26s/it]
Foodie hotel search:  42%|████▏     | 11/26 [01:54<02:11,  8.78s/it]
Foodie hotel search:  46%|████▌     | 12/26 [01:55<01:28,  6.29s/it]
Foodie hotel search:  50%|█████     | 13/26 [02:17<02:22, 10.96s/it]
Foodie hotel search:  54%|█████▍    | 14/26 [02:19<01:40,  8.34s/it]
Foodie hotel search:  58%|█████▊    | 15/26 [02:19<01:05,  6.00s/it]
Foodie hotel search:  62%|██████▏   | 16/26 [02:41<01:47, 10.78s/it]
Foodie hotel search:  65%|██████▌   | 17/26 [02:45<01:16,  8.51s/it]
Foodie hotel search:  69%|██████▉   | 18/26 [02:46<00:50,  6.27s/it]
Foodie hotel search:  73%|███████▎  | 19/26 [03:13<01:27, 12.53s/it]
Foodie hotel search:  77%|███████▋  | 20/26 [03:16<00:58,  9.75s/it]
Foodie hotel search:  81%|████████  | 21/26 [03:18<00:37,  7.45s/it]
Foodie hotel search:  85%|████████▍ | 22/26 [03:38<00:44, 11.12s/it]
Foodie hotel search:  88%|████████▊ | 23/26 [03:41<00:26,  8.84s/it]
Foodie hotel search:  92%|█████████▏| 24/26 [03:42<00:13,  6.52s/it]
Foodie hotel search:  96%|█████████▌| 25/26 [04:02<00:10, 10.47s/it]
Foodie hotel search: 100%|██████████| 26/26 [04:06<00:00,  8.44s/it]
广东 page: 1 results num: 0
广东:No results found
北京 page: 1 results num: 0
北京:No results found
湖南 page: 1 results num: 0
湖南:No results found
湖北 page: 1 results num: 0
湖北:No results found
浙江 page: 1 results num: 0
浙江:No results found
上海 page: 1 results num: 0
上海:No results found
天津 page: 1 results num: 0
天津:No results found
江苏 page: 1 results num: 0
江苏:No results found
山东 page: 1 results num: 0
山东:No results found
河南 page: 1 results num: 0
河南:No results found
河北 page: 1 results num: 0
河北:No results found
山西 page: 1 results num: 0
山西:No results found
陕西 page: 1 results num: 0
陕西:No results found
安徽 page: 1 results num: 0
安徽:No results found
重庆 page: 1 results num: 0
重庆:No results found
福建 page: 1 results num: 0
福建:No results found
江西 page: 1 results num: 0
江西:No results found
辽宁 page: 1 results num: 0
辽宁:No results found
黑龙江 page: 1 results num: 0
黑龙江:No results found
吉林 page: 1 results num: 0
吉林:No results found
四川 page: 1 results num: 0
四川:No results found
云南 page: 1 results num: 0
云南:No results found
香港 page: 1 results num: 0
香港:No results found
内蒙古 page: 1 results num: 0
内蒙古:No results found
甘肃 page: 1 results num: 0
甘肃:No results found
海南 page: 1 results num: 0
海南:No results found

并不是失效，而是该网站限制了访问，导致获取不到结果。你可以试一下本机访问查询也会大概率被限制请求的，目前默认配置已经关闭该来源，后续会移除该来源。


Make our invoke tasks work with python3 (in addition to python2)

Motivation
Python3 all the things.
Additional Notes
You can find the explanation of each change on its own commit.

You also need this https://github.com/DataDog/datadog-agent/pull/3136

After some out-of-band discussion it probably makes sense for a better casual developer UX to support both python's - at least for the time being. The reasoning being that python2 is required by Agent6 at build time (the embedded python) - forcing yet another python on the box is something we can avoid our contributor if we remain backward compatible.
This is naturally an easy problem to solve and nothing we can't address with documentation, but it adds an additional step and requirement for our contributors on py2-only boxes. On the other hand forcing a specific python version on a user working on the DCA or the puppy agent isn't great either, so we should probably aim to remain py2/3 compatible for now.

You also need this #3136

I put the .decode() call inside get_root(), so this is not needed.