How to capture meta-mappings (mappings of mappings into SSSOM)

We frequently have the situation where we take an external mapping provided as a spreadsheet (e.g. from NCIT, SNOMED, etc) and wish to convert it to SSSOM for further processing. The question is what to best do about the metamodel mapping. Let's say we have this raw data:

HPO Term
MPO Term
Mapping

HP:123
MP:123
EXACT

HP:124
MP:124
BROAD

It seems wasteful to import this as:

subject_id
object_id
predicate_id

HP:123
MP:123
someCrazyNamespace:EXACT

HP:124
MP:124
someCrazyNamespace:BROAD

Rather we would like something like:

subject_id
object_id
predicate_id

HP:123
MP:123
skos:exactMatch

HP:124
MP:124
skos:broadMatch

Where do we capture that
someCrazyNamespace:EXACT ---> skos:exactMatch

👍  In a separate SSSOM file? Which we somehow link to this one.
👀  In the description field?
🎉  In a new element somewhere?

I notice these kinds of questions are relevant everywhere, like LinkML etc, but just thinking out loud now. Any ideas anyone?

I would not try to capture this.
Here is my 2 cents:
Producing another SSSOM file with SKOS properties rather than the original ones would means "creating a new set of mappings" with provenance/source the ones produced originally.
Then a bunch of metadata must change.
The commitment/responsibility of going from someCrazyNamespace:EXACT to skos:exactMatch must come with a bunch of new metadata and in best case scenario curation.
Except if NCI or SNOMED natively adopt these SKOS properties then "standardizing" their data/mappings will mean producing new data.

So @graybeal you would merely write a comment or provide a link to the python script to document the translation rules?


Add a more clear timeout message. Closes #2294

Since there isn't currently a way to tell whether the test tried to return a promise or not where we throw the timeout error, I simply went with the suggestion by @dasilvacontin.

The Travis failure happened in npm install. Is there a way to re-👊  it?

Rerun and passed. Thanks!


Radio group component

Create simple <Fieldset /> and <Legend /> atoms
Create <RadioGroupField /> and <Form.RadioGroupField /> components
Remove <Form.RadioField /> since it's not used as a standalone component

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Consolidated bundling [bounty: $250]

Only bundle the necessary third-party browserified node.js deps when they're actually needed to fully convert a collection.

https://www.bountysource.com/issues/72323804-consolidated-bundling-bounty-250

bookmoons/consolidate-bundling has something for this, but I think it conflicts with an open PR. Will return to this after that's closed.

Hello, is this still needed?

@alromh87: Thanks for reaching out! I don't think so, but let me check and get back to you.


[NuGet.org Bug]: The README Markdown parser does not render HTML that is mixed with Markdown

Impact
It's more difficult to complete my work
Describe the bug
The README Markdown parser does not render HTML that is mixed with Markdown. This will break the display for many users.
Repro Steps
Add the following readme file to a package. HTML will not be rendered.
https://raw.githubusercontent.com/SixLabors/ImageSharp/master/README.md
Expected Behavior
I expect the readme to be rendered in the same manner as GitHub is capable.
Screenshots

Additional Context and logs
No response

@JimBobSquarePants, thank you for providing feedback and suggestion. We noticed that there are some gaps on NuGet.org, comparing to GitHub markdown flavor. We are having a plan to provide customers with better markdown rendering experience aligning with GitHub markdown. More feedback and suggestions are really helpful for us.

Thanks for opening this! We're tracking this work with https://github.com/NuGet/NuGetGallery/issues/8644. I'll close this off for now, but please let us know if you have additional suggestions or questions!


fix(core): Rootstock

Purpose

Properly calculates the gas cost in our heuristic using the call data cost of 68 per non-zero byte on Rootstock since they do not implement EIP-2028
Standardizes the way we handle using the 80% block gas limit on Rootstock and Scroll and uses a boolean in the SPHINX_NETWORKS array to implement that
Moves the buffer we add on the gas limit for action execution on Rootstock out of the executeActionsViaManagedService function and into the relayer service
Adds support for Rootstock testnet.  I'm ok with supporting this and was able to find a functional node provider for it. I would prefer people to run into issues with the gas limit on a testnet rather than mainnet
I also added a minor unrelated thing to this PR: A check that the user has a compatible NodeJS version installed. I've ran into this issue a few times (because I have Node 14 as my default globally). The current error the user encounters if they do not use at least 16.16.0 is functionally impossible to debug.

I've created another ticket to handle increasing the max batch size and/or reducing the buffers we add to our estimates to maximize the size of contract that is deployable on Rootstock using our system. I think we should come back to that if people run into issues using our system on Rootstock, or if Rootstock finishes with implementing EIP-2028.

If the user uses the Deploy CLI command on any network that doesn’t support EIP-2028 (e.g. Rootstock), would the transactions fail due to EthersJS underestimating them? If so, we can just address this issue later. Want to make a ticket or should I?

Have you checked that a live network deployment via the website works on Rootstock?

Just curious, does EthersJS automatically calculate the gas correctly when executing via the website on non-EIP 2028 networks? If it doesn’t, how do we fix that?

Just curious, does EthersJS automatically calculate the gas correctly when executing via the website on non-EIP 2028 networks? If it doesn’t, how do we fix that?

It does not. See this comment:
https://github.com/sphinx-labs/sphinx/pull/1480/files#r1499987207

Have you checked that a live network deployment via the website works on Rootstock?

yes


fixed you.com

i have fixed you.com code for my package and here is that code, you can use this code in your package
from re import findall
import cloudscraper
from uuid import uuid4
from requests.exceptions import RequestException
import json

class YouChatAPI:
    """
    This class provides methods for interacting with the You.com chat API.
    """

    def __init__(self):
        self.scraper = cloudscraper.create_scraper()  # Create a Cloudscraper session

    def create_request(self, query):
        try:
            # Prepare the request parameters
            response = self.scraper.get(
                "https://you.com/api/streamingSearch",
                headers={
                    "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>",
                    "Accept": "text/event-stream",
                    "Accept-Language": "en-US,en;q=0.9,en-IN;q=0.8",
                    "Referer": "https://you.com/search?q=hi&fromSearchBar=true&tbm=youchat",
                    "Connection": "keep-alive",
                    "DNT": "1",
                },
                cookies={
                    "uuid_guest_backup": uuid4().hex,
                    "youchat_personalization": "true",
                    "youchat_smart_learn": "true",
                    "youpro_subscription": "false",
                    "ydc_stytch_session": uuid4().hex,
                    "ydc_stytch_session_jwt": uuid4().hex,
                    "__cf_bm": uuid4().hex,
                },
                params={
                    "q": query,
                    "page": 1,
                    "count": 10,
                    "safeSearch": "Moderate",
                    "mkt": "en-IN",
                    "domain": "youchat",
                    "use_personalization_extraction": "true",
                    "queryTraceId": str(uuid4()),
                    "chatId": str(uuid4()),
                    "conversationTurnId": str(uuid4()),
                    "pastChatLength": 0,
                    "isSmallMediumDevice": "true",
                    "selectedChatMode": "default",
                    "traceId": str(uuid4()),
                    "chat": "[]"
                },
            )

            # Check for successful response
            if response.status_code != 200:
                raise RequestException(f"Request failed with status code {response.status_code}")

            if "youChatToken" not in response.text:
                raise RequestException("Unable to fetch the response.")

            # Extract the youChatToken value
            return response.text

        except RequestException as e:
            print(f"An error occurred: {e}")
            raise

    def extract_youchat_tokens(self, response_text):

        tokens = []
        for line in response_text.split('\n'):
            if line.startswith('data: ') and 'youChatToken' in line:
                data = json.loads(line[6:])
                token = data.get('youChatToken', '')
                if token:
                    tokens.append(token)
        return ''.join(tokens)

# Example usage
if __name__ == "__main__":
    from rich import print
    completion = YouChatAPI()
    prompt = "Who is Abhay Koul"
    try:
        result = completion.create_request(prompt)
        tokens = completion.extract_youchat_tokens(result)
        for t in tokens:
            print(t, end="", flush=True)
    except Exception as e:
        print("Error:", str(e))

Hi! Thank you very much for the offer; it's very tempting. However, I can't understand one thing: what's wrong with my version? Maybe you noticed some bug or something like that? My script works correctly just like yours 🤔
Although, to be honest, I do need to update the scripts a bit and add some processing.

Hi! Thank you very much for the offer; it's very tempting. However, I can't understand one thing: what's wrong with my version? Maybe you noticed some bug or something like that? My script works correctly just like yours 🤔 Although, to be honest, I do need to update the scripts a bit and add some processing.

I have add cloudflare bypass to it

Sure, thank you very much. In version 1.2.1, I will add your code to my package. Should I credit you in any specific way? (reference)
You’re helping improve the project.

 It's your choice how you'd like to credit me. I'm just happy to contribute to the project


Tabs blinking

Tabs started to blink since I installed AnyDesk on Debian 9 (stretch) 64-bit
Gnome version 3.2.2
When I installed Anydesk I had Dbeaver 6.3.0, so I updated to 7.0.4 but the problem still remains.
I shared a video to ilustrate the problem.
https://www.youtube.com/watch?v=6MUmDqYOHQE

It could be a known issue with GTK3 on Ubuntu (https://bugs.eclipse.org/bugs/show_bug.cgi?id=517671)
Could you try proposed workaround (export GTK_IM_MODULE=ibus)?

I'm like the same problem here.
Linux Mint 19.3
Cinnamon version 4.4.8
DBeaver Community 7.0.5

Sorry about the late response!
I tried adding export GTK_IM_MODULE=ibus to the /etc/profile file and it worked for me. (After reboot the system)
So, thanks uslss very much.
Ps: I'm not a good english speaker. Sorry if I had misspellings.

@facundonrs @uslss
This worked for me.
On the Linux Mint I used the file /~/.profile.
Thanks very much.


Content type 'application/x-www-form-urlencoded' not supported by  modifyRequestBody funcation

HI!
I want Modify  'application/x-www-form-urlencoded'  post data in modifyRequestBody; but  this not supported ? have other method  modify  post data;
I'm try other way, like this:
public class ModifyFormeGatewayFilter implements GatewayFilter {
@Override
public Mono<Void> filter(ServerWebExchange exchange, GatewayFilterChain chain) {
    ServerHttpRequest request=exchange.getRequest();
    HttpMethod method=request.getMethod();
    if (MediaType.APPLICATION_FORM_URLENCODED.includes(request.getHeaders().getContentType())) {

        exchange.getFormData().flatMap(map->
        {
            for(Map.Entry<String,List<String>> entry :map.entrySet()){
                for (String value : entry.getValue()) {
                }
            }
            return chain.filter(exchange);
        });
    }

    return chain.filter(exchange);

}}
why map.entrySet() is empty ; map can't get data
Thanks !

.route("user_route",r->r.path("/user")
.filters(
//                                f->f.filter(new  ToUppercaseGlobalFilter())
//                                .filter(new ThrottleGatewayFilter())
f->f.setRequestHeader("Content-Type", MediaType.APPLICATION_FORM_URLENCODED_VALUE)
.modifyRequestBody(User.class,User.class,((serverWebExchange, user) -> {
user.setUsername("xxxxxx");
return  Mono.just(user);
}))
)
.uri("lb://smweb"))
org.springframework.web.reactive.function.UnsupportedMediaTypeException: Content type 'application/x-www-form-urlencoded' not supported
at org.springframework.web.reactive.function.BodyInserters.lambda$null$11(BodyInserters.java:329) ~[spring-webflux-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at java.util.Optional.orElseGet(Optional.java:267) ~[na:1.8.0_144]
at org.springframework.web.reactive.function.BodyInserters.lambda$bodyInserterFor$12(BodyInserters.java:325) ~[spring-webflux-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at org.springframework.cloud.gateway.filter.factory.rewrite.ModifyRequestBodyGatewayFilterFactory.lambda$apply$2(ModifyRequestBodyGatewayFilterFactory.java:67) ~[spring-cloud-gateway-core-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at org.springframework.cloud.gateway.filter.OrderedGatewayFilter.filter(OrderedGatewayFilter.java:44) ~[spring-cloud-gateway-core-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at org.springframework.cloud.gateway.handler.FilteringWebHandler$DefaultGatewayFilterChain.lambda$filter$0(FilteringWebHandler.java:115) ~[spring-cloud-gateway-core-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:45) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.Mono.subscribe(Mono.java:3080) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.drain(MonoIgnoreThen.java:172) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoIgnoreThen.subscribe(MonoIgnoreThen.java:56) [reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.Mono.subscribe(Mono.java:3080) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.drain(MonoIgnoreThen.java:172) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoIgnoreThen.subscribe(MonoIgnoreThen.java:56) [reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:150) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxSwitchIfEmpty$SwitchIfEmptySubscriber.onNext(FluxSwitchIfEmpty.java:67) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoNext$NextSubscriber.onNext(MonoNext.java:76) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.innerNext(FluxConcatMap.java:271) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxConcatMap$ConcatMapInner.onNext(FluxConcatMap.java:803) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:108) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxSwitchIfEmpty$SwitchIfEmptySubscriber.onNext(FluxSwitchIfEmpty.java:67) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1083) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:144) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:108) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoNext$NextSubscriber.onNext(MonoNext.java:76) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxFilterWhen$FluxFilterWhenSubscriber.drain(FluxFilterWhen.java:262) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxFilterWhen$FluxFilterWhenSubscriber.onNext(FluxFilterWhen.java:131) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxDematerialize$DematerializeSubscriber.onNext(FluxDematerialize.java:114) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxDematerialize$DematerializeSubscriber.onNext(FluxDematerialize.java:42) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxFlattenIterable$FlattenIterableSubscriber.drainAsync(FluxFlattenIterable.java:391) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxFlattenIterable$FlattenIterableSubscriber.drain(FluxFlattenIterable.java:633) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxFlattenIterable$FlattenIterableSubscriber.onNext(FluxFlattenIterable.java:238) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onNext(FluxPeekFuseable.java:179) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1068) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoCollectList$MonoBufferAllSubscriber.onComplete(MonoCollectList.java:117) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.DrainUtils.postCompleteDrain(DrainUtils.java:131) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.DrainUtils.postComplete(DrainUtils.java:186) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxMaterialize$MaterializeSubscriber.onComplete(FluxMaterialize.java:134) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxFlattenIterable$FlattenIterableSubscriber.drainAsync(FluxFlattenIterable.java:321) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxFlattenIterable$FlattenIterableSubscriber.drain(FluxFlattenIterable.java:633) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxFlattenIterable$FlattenIterableSubscriber.onComplete(FluxFlattenIterable.java:255) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onComplete(FluxMapFuseable.java:138) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1070) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoCollectList$MonoBufferAllSubscriber.onComplete(MonoCollectList.java:117) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxFlatMap$FlatMapMain.checkTerminated(FluxFlatMap.java:773) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxFlatMap$FlatMapMain.drainLoop(FluxFlatMap.java:543) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxFlatMap$FlatMapMain.drain(FluxFlatMap.java:523) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxFlatMap$FlatMapMain.onComplete(FluxFlatMap.java:409) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxIterable$IterableSubscription.slowPath(FluxIterable.java:266) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxIterable$IterableSubscription.request(FluxIterable.java:202) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxFlatMap$FlatMapMain.onSubscribe(FluxFlatMap.java:332) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxIterable.subscribe(FluxIterable.java:140) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxIterable.subscribe(FluxIterable.java:64) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxFlatMap.subscribe(FluxFlatMap.java:97) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoCollectList.subscribe(MonoCollectList.java:59) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoMapFuseable.subscribe(MonoMapFuseable.java:59) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoFlattenIterable.subscribe(MonoFlattenIterable.java:101) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxMaterialize.subscribe(FluxMaterialize.java:40) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoCollectList.subscribe(MonoCollectList.java:59) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoPeekFuseable.subscribe(MonoPeekFuseable.java:74) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoFlattenIterable.subscribe(MonoFlattenIterable.java:101) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxDematerialize.subscribe(FluxDematerialize.java:39) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxDefer.subscribe(FluxDefer.java:55) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxFilterWhen.subscribe(FluxFilterWhen.java:68) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoNext.subscribe(MonoNext.java:40) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoMap.subscribe(MonoMap.java:55) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:60) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoSwitchIfEmpty.subscribe(MonoSwitchIfEmpty.java:44) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoMap.subscribe(MonoMap.java:55) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.Mono.subscribe(Mono.java:3080) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:418) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onSubscribe(FluxConcatMap.java:210) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxIterable.subscribe(FluxIterable.java:140) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxIterable.subscribe(FluxIterable.java:64) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:121) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoNext.subscribe(MonoNext.java:40) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoSwitchIfEmpty.subscribe(MonoSwitchIfEmpty.java:44) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:60) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:60) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoPeekTerminal.subscribe(MonoPeekTerminal.java:61) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:150) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1083) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoZip$ZipCoordinator.signal(MonoZip.java:247) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoZip$ZipInner.onNext(MonoZip.java:329) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.Operators$ScalarSubscription.request(Operators.java:1640) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoZip$ZipInner.onSubscribe(MonoZip.java:318) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoJust.subscribe(MonoJust.java:54) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.Mono.subscribe(Mono.java:3080) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoZip.subscribe(MonoZip.java:128) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:60) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoPeekTerminal.subscribe(MonoPeekTerminal.java:61) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoPeekFuseable.subscribe(MonoPeekFuseable.java:74) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoOnErrorResume.subscribe(MonoOnErrorResume.java:44) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoOnErrorResume.subscribe(MonoOnErrorResume.java:44) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoOnErrorResume.subscribe(MonoOnErrorResume.java:44) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.Mono.subscribe(Mono.java:3080) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.drain(MonoIgnoreThen.java:172) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoIgnoreThen.subscribe(MonoIgnoreThen.java:56) [reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoPeekFuseable.subscribe(MonoPeekFuseable.java:70) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.core.publisher.MonoPeekTerminal.subscribe(MonoPeekTerminal.java:61) ~[reactor-core-3.1.8.RELEASE.jar:3.1.8.RELEASE]
at reactor.ipc.netty.channel.ChannelOperations.applyHandler(ChannelOperations.java:380) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE]
at reactor.ipc.netty.http.server.HttpServerOperations.onHandlerStart(HttpServerOperations.java:398) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE]
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) ~[netty-common-4.1.25.Final.jar:4.1.25.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404) ~[netty-common-4.1.25.Final.jar:4.1.25.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:465) ~[netty-transport-4.1.25.Final.jar:4.1.25.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884) ~[netty-common-4.1.25.Final.jar:4.1.25.Final]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_144]

@spencergibb  can help me?

.route("userInfo_route",r->r.path("/userInfo").uri("lb://smweb"))
this way post  application/json data ;   cause ：
WARN 3176 --- [ctor-http-nio-2] .a.w.r.e.DefaultErrorWebExceptionHandler : Failed to handle request [POST http://<IP_ADDRESS>:8080/userInfo]: Response status 415 with reason "Content type 'application/json' not supported"

Is there an alternate way to modify the request body for application/x-www-form-urlencoded content type?. Any reference would be helpful.
I get this error message.
{
    "timestamp": "2018-07-09T05:04:46.277+0000",
    "path": "/test",
    "status": 500,
    "error": "Internal Server Error",
    "message": "Content type 'application/x-www-form-urlencoded' not supported"
}

I upload excel file adm come across the similar issue. Is there any solution


Fix second level caching for queries with multiple joins

The $metadata of the main entity is not always the metadata you need here, for example when you do join A with B and then B with C. For the second join it was using the metadata from A.

@krispypen can you add a test case please ?

@FabioBatSilva I added a test case for it.


Date picker shows in Chrome but not Firefox

A date picker has been implemented on the edit card dialog.  This shows up on Chrome, but not on Firefox

The date picker is provided by the browser as the input type is set to date. We'll need a polyfill for the browsers that don't support it.

Not an issue for now then.


BlobClient().upload_blob(file) gets a 403

Code that is run
log.info("Begin Upload: {file} as {name} {type}".format(file=repr(file), name=name, type=content_type))
write_url = self._create_write_url(name) # produces a full url with SAS token with write permissions.
content_settings = ContentSettings(
    content_type=content_type,
    content_disposition="inline",
)
try:
    with BlobClient(write_url, logging_enable=True, retry_policy=ExponentialRetry(initial_backoff=2, retry_total=10)) as client:
        if type(file) is str:
            with open(file, 'rb') as f:
                client.upload_blob(f, content_settings=content_settings)
        else:
            client.upload_blob(file, content_settings=content_settings)
except:
    log.exception("Failure while uploading {file}".format(file=repr(file)))

Server Response:
<?xml version="1.0" encoding="utf-8"?>
<Error>
  AuthenticationFailed
  <Message>
    Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
    RequestId:***
    Time:2019-07-23T23:00:12.1569153Z
  </Message>
  <AuthenticationErrorDetail>Signature fields not well formed.</AuthenticationErrorDetail>
</Error>

The blob url I passed is valid and works with manual PUT requests. The debug logs show that the sas token on the url is url-decoded and the final PUT request is made using the (invalid) decoded sas token signature.

Hi @alexperovich thanks for reporting the bug. CCing @annatisch & @mayurid to help route this further

Thanks @alexperovich - we are aware of this and have a fix under review now.
This fix should be released in our next preview release.
The specific line with the fix is here:
https://github.com/Azure/azure-sdk-for-python/pull/6442/files#diff-19efb00002f2454f98f0c2539aeae6f3R274
Thanks again!

Hi @alexperovich - Preview 2 of storage has been released that should resolve this issue.
Can you confirm whether that's the case?
https://pypi.org/project/azure-storage-blob/12.0.0b2/

I'm assuming this is now fixed - please let me know if it needs to be reopened :)

I haven't had a chance to try it yet. I will let you know if I this issue isn't fixed.


drop packets with version numbers that don't match the session's version

Depends on #2480.

Codecov Report

Merging #2481 into master will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #2481      +/-   ##
==========================================
+ Coverage   85.80%   85.81%   +0.01%
==========================================
  Files         123      123
  Lines        9442     9463      +21
==========================================
+ Hits         8101     8120      +19
- Misses        994      996       +2
  Partials      347      347

Impacted Files
Coverage Δ

qlog/types.go
86.32% <100.00%> (+0.60%)
:arrow_up:

session.go
74.13% <100.00%> (+0.15%)
:arrow_up:

Continue to review full report at Codecov.

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


controlsd: adds steer saturated event prematurely

The previous logic checked the actuators output, considering torque rate limits. We should continue to do the same.
@jnewb1 can you use process replay on a few segments with these events to make sure there's no (or expected minimal) diff after fixing?
This core logic should not regress in refactors. I'm not sure how we want to go about testing for similar bugs in the future (more process replay segments, fuzzed segments, or event unit tests), but we should at least consider how things might regress first.
https://connect.comma.ai/7852e9f76b7e6e8a/1710495866768/1710495950510

I like the idea of more process replay segments. We should try to hit 100% codecov for the core services. Perhaps we do process replay on fuzzed segments?

(for example this part is never hit in any of our tests, even process replay


Move all members of utils.helpers to more descriptive locations and either make public or make part of individual modules

Move create_on_off_val ... to its own submodule and make public
Move path helpers to their own module and rework to use importlib_resources rathat than importing qcodes
Move abstract_method to its own submodule and rename so its more obvious that this is  not the std lib abstract decorator

bors merge


PDF Appendix should be selectable for copy/paste

I was directed here by a member on community.aras.com.
I would really like to be able to copy/paste the sample code, but it is in a PDF that is rendered as an image, and thus not selectable.
Seems a bummer to introduce human error when attempting to complete this proof-of-concept as we're trying to add emailing to our Innovator.

This one depends on your PDF viewer. I was able to select it without problems. But of course, this one is a good enhancement.
Quick and dirty:
Innovator inn=this.getInnovator();
string tempDir = "C:\\temp\\ArasEmail\\";
Item doc= inn.newItem("Document","get");
Item docFile = inn.newItem("Document File","get");
Item file = inn.newItem("File","get");
doc.setID(this.getID());
doc.setAttribute("select","created_by_id,item_number,description,state");
doc.addRelationship(docFile);
docFile.setRelatedItem(file);
doc=doc.apply();
docFile = doc.getRelationships("Document File");
Item innAdm= inn.newItem("User","get");
innAdm.setAttribute("select","first_name,last_name,email");
innAdm.setProperty("login_name","admin");
innAdm=innAdm.apply();
Item toUser= inn.newItem("User","get");
toUser.setAttribute("select","email");
toUser.setID(doc.getProperty("created_by_id"));
toUser=toUser.apply();
string from_user=innAdm.getProperty("email");
string from_userN = innAdm.getProperty("first_name")+ " " + innAdm.getProperty("last_name");
string to_user=toUser.getProperty("email");
string emBody= "Document Number: " + doc.getProperty("item_number") + "
State: ";
emBody += doc.getProperty("item_number") + "
Description" + doc.getProperty("item_number") + "";
System.Net.Mail.MailAddress SendFrom = new System.Net.Mail.MailAddress(from_user,from_userN);
System.Net.Mail.MailAddress SendTo = new System.Net.Mail.MailAddress(to_user);
System.Net.Mail.MailMessage MyMessage = new System.Net.Mail.MailMessage(SendFrom, SendTo);
MyMessage.Subject = "Files for Document Number: " + doc.getProperty("item_number");
MyMessage.IsBodyHtml = true;
MyMessage.Body = emBody;
if (docFile.getItemCount()>0)
{
string[] fileArr = new string[docFile.getItemCount()];
for (int i=0;i<docFile.getItemCount();i++)
{
Item f = docFile.getItemByIndex(i).getRelatedItem();
f.checkout(tempDir);
string sAttach =tempDir + f.getProperty("filename");
System.Net.Mail.Attachment myAttachment = new System.Net.Mail.Attachment(sAttach);
MyMessage.Attachments.Add(myAttachment);
fileArr[i]=sAttach;
}
CCO.Email.setup_smtpmail_server_and_send(MyMessage);
System.Threading.Thread.Sleep(2000);
MyMessage.Attachments.Dispose();
for (int j=0;j<docFile.getItemCount();j++)
{
FileInfo fileInfo = new FileInfo(fileArr[j]);
fileInfo.Delete();
}
}
return this;

Geez, thanks @AngelaIp AngelaIp. I was just getting on here to share and saw that you had pasted. This includes small improvements - Notably, when the body is being built here it just gets the same property over and over - it does getProperty("item_number") for every propery so that status would also be set to "item_number". The code also mixes camelCase and snake_case for variable initialization. I consolidated it to camel...
`Innovator inn = this.getInnovator();
string tempDir = "C:\temp\ArasEmail";
Item doc = inn.newItem("Document", "get");
Item docFile = inn.newItem("Document File", "get");
Item file = inn.newItem("File", "get");
doc.setID(this.getID());
doc.setAttribute("select", "created_by,item_number,description,state");
doc.addRelationship(docFile);
docFile.setRelatedItem(file);
doc = doc.apply();
docFile = doc.getRelationships("Document File");
Item innAdmin = inn.newItem("User", "get");
innAdmin.setAttribute("select", "first_name,last_name,email");
innAdmin.setProperty("login_name", "admin");
innAdmin = innAdmin.apply();
Item toUser = inn.newItem("User", "get");
toUser.setAttribute("select", "email");
toUser.setID(doc.getProperty("created_by_id"));
toUser = toUser.apply();
string fromUser = innAdmin.getProperty("email");
string fromUsername = innAdmin.getProperty("first_name") + " " + innAdmin.getProperty("last_name");
string toUserEmail = toUser.getProperty("email");
string messageBody = "Document Number: " + doc.getProperty("item_number") + "Created By:" + doc.getProperty("created_by") + "State: " + doc.getProperty("state") + "Description: " + doc.getProperty("description") + "";
System.Net.Mail.MailAddress SendFrom = new;
System.Net.Mail.MailAddress(fromUser, fromUsername);
System.Net.Mail.MailAddress SendTo = new;
System.Net.Mail.MailAddress(toUser);
System.Net.Mail.MailMessage MyMessage = new;
System.Net.Mail.MailMessage(SendFrom, SendTo);
MyMessage.Subject = "Files for document number: " + doc.getProperty("item_number");
MyMessage.IsBodyHtml = true;
MyMessage.Body = messageBody;
if (docFile.getItemCount() > 0) {
string[] fileArray = new string[docFile, getItemCount()];
for (int i = 0; i < docFile.getItemCount(); i++) {
Item f = docFile.getItemByIndex(i).getRelatedItem();
f.checkout(tempDir);
    string sAttach = tempDir + f.getProperty("filename");
    System.Net.Mail.Attachment myAttachment = new System.Net.Mail.Attachement(sAttach);
    MyMessage.Attachments.Add(myAttachment);
    fileArray[i] = sAttach;
}
CCO.Email.setup_smtpmail_server_and_send(MyMessage);
System.Threading.Thread.Sleep(2000);
MyMessage.Attachments.Dispose();
for (int i = 0; i < docFile.getItemCount(); i++) {
    FileInfo fileInfo = new FileInfo(fileArr[i]);
    fileInfo.Delete();
}

}
return this;
`

@AngelaIp you're obviously very active around Aras as it was your post on community that had me checking out this repo.
Could this code be improved by pulling the temp dir somehow from the settings of the Innovator instance? Something like:


Wrong focus after reload

Plugin works perfectly, except that it insists it focusing the SWI Console tab instead of the tab that triggered the save action.

As a work around, open the "swi.py" file, search for the function "def find_view" and comment out (using #) the window.focus_view(v) call. Currently, this is on line 913.

Can you please try this in the latest release (st3-1.6.4)? I can't reproduce anything like this and the relevant code has changed substantially in the last week or so.
Please do reactivate if it still happens, with some steps I can use to reproduce. thanks


remove debug output and fix exit code

node without a proper process.exit will exit with a non-zero exit code, resulting in npm reporting an error even though everything went fine

`❯ npm run takeoff                                                                                [18-04-26 19:30:13]

<EMAIL_ADDRESS>takeoff /Users/dh/Projects/kangacoach/react-base
takeoff

? What do you want to create? component
? component-name foo
? Choose a destination for the component element
🚀  Houston, lift of in 3..2..1
✔ Created files for station component
🎉  Done
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>takeoff: takeoff
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>takeoff script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
╭─────────────────────────────────────╮
│                                     │
│   Update available 5.5.1 → 6.0.0    │
│     Run npm i -g npm to update      │
│                                     │
╰─────────────────────────────────────╯
npm ERR!      /Users/dh/.npm/_logs/2018-04-27T17_39_56_112Z-debug.log`

I investigated a little into that and identified the error in another package. Added a PR there to fix the issue (https://github.com/entwicklerstube/taskler/pull/2).
I still like the Idea to have a non zero exit code it things go south and the removal of the debug code is a good idea anyway. So I will just remote the process.exit(0) as it is not necessary.

the issue will be fixed when the upstream package accepts the mentioned PR. merging.


Fix binder by excluding conda default channel

The configuration file for the server extension was being overridden by the _nb_ext_conf package from the default channel.

Merging as a temporary workaround.


Trailing space with JSX (esnext) causes indent fix bug

OSX 10.10.5
node 5.6.0
jscs 2.10.1
jscs --fix with this code
const a = (

)

and these settings
{
    "esnext": true,
    "disallowTrailingWhitespace": true,
}

The trailing space after the
 causes the next line to be over indented. Here's the result:
const a = (

)

Every time you run jscs fix, the indent gets longer. Eventually jscs crashes when the indent get extremely long:
Security context: 0x11d58de3ac1 <JS Object>
    2: _fix [node_modules/jscs/lib/rules/disallow-trailing-whitespace.js:~81] [pc=0x2eb144609558] (this=0x2d79d4358ca9 <JS Object>,file=0x14aaf8575161 <JS Object>,error=0x14c1f0aecbd9 <an Object with map 0x2ab353e251b1>)
    3: /* anonymous */(aka /* anonymous */) [node_modules/jscs/lib/string-checker.js:136] [pc...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
[1]    54121 abort      node_modules/jscs/bin/jscs --fix

Appears to be fixed in 3.0


Update broken KEP links

Branch selection: fix to existing content
KEPs have moved to the kubernetes/enhancements repository. Update all links pointing to kubernetes/community .

Something's funky with the CLA process - I'm not sure what "Gaming-PC Trade Co .,ltd" is and the Contact form on the website didn't work right. I am currently employed by Google.
Test: the "subproject" link on https://deploy-preview-15806--kubernetes-io-master-staging.netlify.com/blog/page/81/ does not lead to a 404.

@riking Do you want to double check your CLA issue, or you are okay for this one to be merged?

The commit email address is @google.com, so I think it'll be fine.

Your CLA is okay now and the change LGTM. Thanks for the good catch!
/lgtm

/assign @shavidissa
for approval.

/lgtm

/assign @makoscafee
Second attempt at OWNERS approval

/approve


Ramda.assoc cannot be typed correctly

Ramda.assoc(), by analogy with Clojure's assoc, takes a key, a value, and an object, and returns a copy of the object with that key and value added. (Ramda functions are also curried, but that's orthogonal to this issue.)
The most reasonable way to type assoc() I could come up with is the following, which doesn't work correctly:
declare function assoc<K: string, V, O>(key: K, val: V, src: O): O & { [K]: V };

let assocd = assoc('a', 'one', { b: 2 });
(assocd.a: string);
(assocd.b: number);
// This should be an error, but it's not, because the type of `assocd` now has
// an indexer property `{[string]: string}`.
(assocd.foo: string);

It appears that K becomes bound to string, and not the more specific type 'a'. Notice that constraining K to 'a' fixes the problem:
declare function assoc<K: 'a', V, O>(key: K, val: V, src: O): O & { [K]: V };

let assocd = assoc('a', 'one', { b: 2 });
(assocd.a: string);
(assocd.b: number);
// $ExpectError: This is now an error, because the type of `assocd` no longer
// uses an indexer property.
(assocd.foo: string);

I'm not certain where or if there's a shortcoming in Flow here, but it would be nice to be able to type assoc properly.

Interestingly, a generic does appear to be able to get a literal type. For instance:
declare function foo <T>(a: T): {foo: T};
(foo('a'): {foo: 'a'});
// $ExpectError: `T` is bound to the literal type `'a'`, so the return value is known to be `{foo: 'a'}`.
(foo('a'): {foo: 'b'});

But, the other way around:
declare function bar <T>(a: T): {[T]: 'bar'};
(bar('a'): {a: 'bar'});
// This passes, but should fail. Flow does not require the property to be `'a'`.
(bar('a'): {b: 'bar'});

As before, bounding T to the literal 'a' makes it work for this specific case:
declare function bar <T: 'a'>(a: T): {[T]: 'bar'};
(bar('a'): {a: 'bar'});
// $ExpectError: The property is correctly required to be the literal `'a'`.
(bar('a'): {b: 'bar'});

So, while a generic can take a literal type, using it in an indexer property appears to force it to a primitive type, unless the generic is bounded so that that's not possible.


Docker cross compilation for Raspberry Pi 2/3/4 (Debian Buster) fails

[x] I confirm that this is an issue rather than a question.

Bug report
I tried cross compiling Hyperion for armv7l with three different machines (2x Ubuntu and  1x Debian) with docker, but every time, the exact same error appeared.
Steps to reproduce
Install Docker freshly according to those instructions: https://docs.docker.com/engine/install/ubuntu/ or https://docs.docker.com/engine/install/debian/
Add the current user to the docker group sudo usermod -aG docker $USER
Restart the machine
wget -qN https://raw.github.com/hyperion-project/hyperion.ng/master/bin/scripts/docker-compile.sh && chmod +x *.sh && ./docker-compile.sh -i armv7l -t buster
What is expected?
Successful compilation/compiled binaries
What is actually happening?
CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
  list sub-command REMOVE_ITEM requires two or more arguments.
Call Stack (most recent call first):
  /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
  /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
  /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
  /usr/share/cmake-3.16/Modules/CMakeDetermineCXXCompiler.cmake:111 (CMAKE_DETERMINE_COMPILER_ID)
  CMakeLists.txt:5 (PROJECT)

(it actually appears 20 times until it finally stops)
Strangely, wget -qN https://raw.github.com/hyperion-project/hyperion.ng/master/bin/scripts/docker-compile.sh && chmod +x *.sh && ./docker-compile.sh -i x86_64 -t buster works just fine.
System
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

and
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.2 LTS
Release:        20.04
Codename:       focal

I can confirm the error. I will take care of the problem this week. Thank you for your issue report.

The problem has been fixed. Thanks again. 👍🏻


config: ~/teuthology.yaml no_check_package_signatures hint

If no_check_package_signatures is true, the tasks installing
packages (install, ceph-deploy, ...) are authorized to skip the package
signatures verifications.
Set this as the default for a cluster dynamically generated by the
OpenStack backend.
http://tracker.ceph.com/issues/13249 Refs: #13249
Signed-off-by: Loic Dachary<EMAIL_ADDRESS>

Refer to this link for build results (access rights to CI server needed):
http://jenkins.ceph.com//job/teuthology-pull-requests/1880/
Test PASSed.

Could we call this check_package_signatures and default to True?

@zmc I'll do that

re-pushed !

Refer to this link for build results (access rights to CI server needed):
http://jenkins.ceph.com//job/teuthology-pull-requests/1896/
Test PASSed.


[v1.2][ISSUE-306]Add diversity analysis.

What changes were proposed in this pull request?
Add diversity analysis function.
Why are the changes needed?
support the new capability
How was this patch tested?
UT

Hi, @yao531441 , this PR is not completed yet, is that correct?

Hi, @yao531441 , this PR is not completed yet, is that correct?

Yes, I found that some functions are implemented in Chaojun's PR, so I will modify my pr after his pr merged.

Thanks, let's discuss on today's meeting

@yao531441 , you missed to add 'spacy' in setup.py


sign with the .p12 file

How to sign with the .p12 file?

The filename extension for PKCS #12 files is .p12 or .pfx So it should work like this:
$xmlSigner->loadPfxFile('filename.p12', 'password');

or load a p12 from a string:
$xmlSigner->loadPfx('p12 content', 'password');


(PUP-9155) Make puppet cert error when args are passed

In Puppet 6 we replaced puppet cert with puppetserver ca. We tried
to make puppet cert error when it was used, but accidentally only
caused the error message to print when no subcommands or args were
passed. This commit updates puppet cert to error helpfully in all cases.

Those test failures seem unrelated to this, is that a known issue?

Those tests are also currently failing on the master branch. You're right that they're completely unrelated. I believe they're being looked at.

CLA signed by all contributors.

Do we want to wait till those tests are fixed, or can this be merged?


localForage 1.2.2 + webpack 1.5.3 doesn't want to collaborate

Hello. It seems that this PR don't fix problem of using localForage with webpack. I've created gist to illustrate problem https://gist.github.com/ALF-er/83325c24019de4edc851 (just place file index.html in ./src/ dir and main.js in ./src/js/ dir).
If I run "npm run dev" (it just copy index.html in ./dist/ dir, compile main.js with webpack and then run webpack-dev-server for ./dist/) I get:
WARNING in ./~/localforage/src/localforage.js
Critical dependencies:
332:20-336:22 the request of a dependency is an expression
 @ ./~/localforage/src/localforage.js 332:20-336:22

ERROR in ./~/localforage/src/drivers/localstorage.js
Module not found: Error: Cannot resolve module 'localforageSerializer' in C:\dev\projects\wp_lf_test\node_modules\localforage\src\drivers
 @ ./~/localforage/src/drivers/localstorage.js 70:16-59

ERROR in ./~/localforage/src/drivers/websql.js
Module not found: Error: Cannot resolve module 'localforageSerializer' in C:\dev\projects\wp_lf_test\node_modules\localforage\src\drivers
 @ ./~/localforage/src/drivers/websql.js 63:16-59

If in main.js uncomment second line (and comment first ofc) then it builds w/o errors but in browser console I get localForage.getItem - undefined function...
Maybe you can suggest something?

I don't really know much at all about webpack, any ideas @k88hudson?
-tofumatt
On 9 Feb 2015 04:49, "Illia Segeda"<EMAIL_ADDRESS>wrote:

Hello. It seems that this PR don't fix problem of using localForage with
webpack. I've created gist to illustrate problem
https://gist.github.com/ALF-er/83325c24019de4edc851 (just place file
index.html in ./src/ dir and main.js in ./src/js/ dir).
If I run "npm run dev" (it just copy index.html in ./dist/ dir, compile
main.js with webpack and then run webpack-dev-server for ./dist/) I get:
WARNING in ./~/localforage/src/localforage.js
Critical dependencies:
332:20-336:22 the request of a dependency is an expression
@ ./~/localforage/src/localforage.js 332:20-336:22
ERROR in ./~/localforage/src/drivers/localstorage.js
Module not found: Error: Cannot resolve module 'localforageSerializer' in C:\dev\projects\wp_lf_test\node_modules\localforage\src\drivers
@ ./~/localforage/src/drivers/localstorage.js 70:16-59
ERROR in ./~/localforage/src/drivers/websql.js
Module not found: Error: Cannot resolve module 'localforageSerializer' in C:\dev\projects\wp_lf_test\node_modules\localforage\src\drivers
@ ./~/localforage/src/drivers/websql.js 63:16-59
If in main.js uncomment second line (and comment first ofc) then it builds
w/o errors but in browser console I get localForage.getItem - undefined
function...
Maybe you can suggest something?
—
Reply to this email directly or view it on GitHub
https://github.com/mozilla/localForage/issues/344.

cc @sokra
The problem seems to be due to Webpack not being able to tell if localStorage.js is a CommonJS or AMD file as it tries to be both.
Looks similar to https://github.com/webpack/webpack/issues/424.

The problem is afaict that localforageSerializer is not known as AMD module when it is required. I'm not experienced with AMD modules, but can't you just use relative paths?
You could also just switch the if clause and check for ModuleType.EXPORT first . Webpack supports both module syntaxes and uses the first it encounters.

At the moment I use require("imports?require=>false!localforage") as suggested in https://github.com/webpack/webpack/issues/424. But it would be nice if this could be solved.

Having same problem. Also, using imports-loader does not solves problem. (Since it assigns var require as false, https://github.com/mozilla/localForage/blob/master/src/localforage.js#L6 throws exception. (I think Webpack could not statically analyze require() call inside expression)
I would like to fix this problem as well, but I ended up using IDB polyfill.

This seems like a duplicate of #290. Anyway, I'm having the same problem and have been unable to work around this. Any help appreciated.

I've used:
module: {
        loaders: [{
            test: /localforage\/dist\/localforage.js/,
            loader: 'exports?localforage',
        }]
},
alias: { 'localforage': 'localforage/dist/localforage.js'}

seems to work ok

Nice. We should either add a test for it or add it to README/wiki.
On Tue, Jun 23, 2015, 19:06 Josip Janžić<EMAIL_ADDRESS>wrote:

I've used:
module: {
loaders: [{
test: /localforage/dist/localforage.js/,
loader: 'exports?localforage',
}]
},
alias: { 'localforage': 'localforage/dist/localforage.js'}
seems to work ok
—
Reply to this email directly or view it on GitHub
https://github.com/mozilla/localForage/issues/344#issuecomment-114558558
.

I'm still struggling with this, the webpack config tweaks suggested above don't seem to help.
I'm getting this error:
WARNING in ./~/localforage/src/localforage.js
Critical dependencies:
333:24-54 the request of a dependency is an expression
 @ ./~/localforage/src/localforage.js 333:24-54

ERROR in ./~/localforage/src/drivers/localstorage.js
Module not found: Error: Cannot resolve module 'localforageSerializer' in /Users/henrik/Sites/foo.bio/node_modules/localforage/src/drivers
 @ ./~/localforage/src/drivers/localstorage.js 70:16-59

ERROR in ./~/localforage/src/drivers/websql.js
Module not found: Error: Cannot resolve module 'localforageSerializer' in /Users/henrik/Sites/foo.bio/node_modules/localforage/src/drivers
 @ ./~/localforage/src/drivers/websql.js 63:16-59

You're right, I missed this part of the config:
        noParse: [
            /localforage\/dist\/localforage.js/
        ]

so the whole thing is:
module.exports = {
    module: {
        loaders: [{
            test: /localforage\/dist\/localforage.js/,
            loader: 'exports?localforage',
        }],
        noParse: [
            /localforage\/dist\/localforage.js/
        ]
    },
    resolve: {
        alias: {
            'localforage': 'localforage/dist/localforage.js'
        }
    }
};

@janza: Hi, I've modified my webpack.config.js as suggested by you and I can no longer see the errors that @HenrikJoreteg was seeing. However, now I'm getting the following -
ERROR in ./js/stores/SurveyStore.js
Module not found: Error: Cannot resolve module 'exports' in /Users/asrinivasan/Code/react-surveyman/js/stores
 @ ./js/stores/SurveyStore.js 13:0-22

The SurveyStore looks like this -
var localForage = require('localforage');

Any help?

you need to install exports-loader: npm i -S exports-loader

Thanks @janza. Although I'm now using another localStorage lib I'll give this a shot and report if there are any issues. Thanks again!

Thanks @janza it works as expected :)

Any chance you ca check if #415 fixes this?

webpack 1.11.0, localforage 1.2.7
Still get
WARNING in ./~/localforage/src/localforage.js
Critical dependencies:
334:24-54 the request of a dependency is an expression
 @ ./~/localforage/src/localforage.js 334:24-54

ERROR in ./~/localforage/src/drivers/localstorage.js
Module not found: Error: Cannot resolve module 'localforageSerializer' in C:\dev\projects\trill\node_modules\localforage\src\drivers
 @ ./~/localforage/src/drivers/localstorage.js 70:16-59

ERROR in ./~/localforage/src/drivers/websql.js
Module not found: Error: Cannot resolve module 'localforageSerializer' in C:\dev\projects\trill\node_modules\localforage\src\drivers
 @ ./~/localforage/src/drivers/websql.js 63:16-59

for me =(

Can you try with the latest master instead? 1.2.7 wouldn’t have this fix.

tofumatt

On Mon, Aug 10, 2015 at 1:15 PM, Illia Segeda<EMAIL_ADDRESS>wrote:

webpack 1.11.0, localforage 1.2.7
Still get
WARNING in ./~/localforage/src/localforage.js
Critical dependencies:
334:24-54 the request of a dependency is an expression
 @ ./~/localforage/src/localforage.js 334:24-54
ERROR in ./~/localforage/src/drivers/localstorage.js
Module not found: Error: Cannot resolve module 'localforageSerializer' in C:\dev\projects\trill\node_modules\localforage\src\drivers
 @ ./~/localforage/src/drivers/localstorage.js 70:16-59
ERROR in ./~/localforage/src/drivers/websql.js
Module not found: Error: Cannot resolve module 'localforageSerializer' in C:\dev\projects\trill\node_modules\localforage\src\drivers
 @ ./~/localforage/src/drivers/websql.js 63:16-59

for me =(
Reply to this email directly or view it on GitHub:
https://github.com/mozilla/localForage/issues/344#issuecomment-129424792

@ALF-er OOOOoooops!, my bad.
The actual webpack changes are in a commit that I didn't push.
Now that the PR is merged, I will do a rebase as soon as I'm home. Sorry for the inconvenience/false positive.

Oops, haha! 😂

tofumatt

On Mon, Aug 10, 2015 at 8:04 PM, Thodoris Greasidis
<EMAIL_ADDRESS>wrote:

@ALF-er OOOOoooops!, my bad.
The actual webpack changes are in a commit that I didn't push.
Now that the PR is merged, I will do a rebase as soon as I'm home. Sorry for the inconvenience/false positive.
Reply to this email directly or view it on GitHub:
https://github.com/mozilla/localForage/issues/344#issuecomment-129567955

Just opened #417 that directs webpack to use the dist file of the repo.
This should remove the need of aliasing the module in your webpack configuration.
Tested with webpack v1.11 on the how-to-repo MattKunze/localforage-webpack.
Any feedback will be much appreciated.

So, after npm install<EMAIL_ADDRESS>and setup webpack to run localForage.js thru babel-loader I got this:
ERROR in ./~/localforage/src/localforage.js
Module build failed: ReferenceError: Unknown plugin "system-import-transformer"
    at PluginManager.subnormaliseString (C:\dev\projects\trill\node_modules\babel-core\lib\transformation\file\plugin-manager.js:147:13)
    at PluginManager.add (C:\dev\projects\trill\node_modules\babel-core\lib\transformation\file\plugin-manager.js:190:40)
    at File.buildTransformers (C:\dev\projects\trill\node_modules\babel-core\lib\transformation\file\index.js:237:21)
    at new File (C:\dev\projects\trill\node_modules\babel-core\lib\transformation\file\index.js:139:10)
    at Pipeline.transform (C:\dev\projects\trill\node_modules\babel-core\lib\transformation\pipeline.js:164:16)
    at transpile (C:\dev\projects\trill\node_modules\babel-loader\index.js:12:22)
    at Object.module.exports (C:\dev\projects\trill\node_modules\babel-loader\index.js:69:12)
 @ ./src/app/utils/OfflineStorageUtils.js 11:19-41

Can try using the branch in #417? Hopefully, you shouldn't have to do any configuring or use babel at all, since package.json should direct webpack to use the dist files.

@thgreasi i just tried setting "webpack" to dist/localforage.js as per your fix. I'm still seeing issues:
WARNING in ./~/localforage/dist/localforage.js
Critical dependencies:
2603:24-54 the request of a dependency is an expression
 @ ./~/localforage/dist/localforage.js 2603:24-54

WARNING in ./~/localforage/dist/localforage.nopromises.js
Critical dependencies:
1920:24-54 the request of a dependency is an expression
 @ ./~/localforage/dist/localforage.nopromises.js 1920:24-54

WARNING in ./~/localforage/dist/localforage.min.js
Critical dependencies:
7:24233-24247 the request of a dependency is an expression
 @ ./~/localforage/dist/localforage.min.js 7:24233-24247

WARNING in ./~/localforage/dist/localforage.nopromises.min.js
Critical dependencies:
7:19049-19063 the request of a dependency is an expression
 @ ./~/localforage/dist/localforage.nopromises.min.js 7:19049-19063

ERROR in ./~/localforage/dist/localforage.js
Module not found: Error: Cannot resolve 'file' or 'directory' ./../utils/serializer in /Users/henrik/Sites/hubflow-redux/node_modules/localforage/dist
 @ ./~/localforage/dist/localforage.js 1596:24-56 1918:24-56

It keeps going for a bit..

Here is my test branch of @MattKunze's localforage-webpack.
It uses the branch of PR #417.
I'm just running webpack in terminal and the index.html page seems to be working.
I think I'm not doing using magic webpack configuration for localforage to work.
Am I doing something wrong?
Any chance I can reach some of the configuration of your app?

@HenrikJoreteg all I get in terminal is:
~/Desktop/localforage-webpack$ webpack
Hash: 34b97eaf37c1224e529b
Version: webpack 1.11.0
Time: 105ms
    Asset    Size  Chunks             Chunk Names
bundle.js  102 kB       0  [emitted]  main
   [0] ./index.js 148 bytes {0} [built]
    + 3 hidden modules

Added grunt to the test repo and realized that it was already using webpack/script-loader. I hope that importing localforage with something like: require('script!localforage'); isn't too bad at the moment.

Just pushed an extra commit to PR #417, that adds webpack bundling tests.

so, can anyone please test and merge this if it's really working? :D thaaanks

#417 has been merged into master, but I think we have yet to release it under a new tag.
v1.2.7 should work for now.
We are probably going for a proper fix in v1.3.

Looks like this should now be fixed in 1.2.10. #439 fixed it up, if there's an issue let me know (be sure to following the README's guide to using it in 1.2.10: https://github.com/mozilla/localForage/tree/1.2.10#browserify-and-webpack


Issue with Compatibility with Advanced Solar High Resolution - LsHallo

Hello, I have contacted the other mod author for the same reason. It seems that your logistic robots don't recognize LsHallo's solar or accumulators and will not place nor pick up them from a logistic network, or my inventory.
Thank you for taking the time to read!

its a compatibility error, possible fix in future

please recheck compatibility to confirm if the new changes are working


Make map_src public on error types

Closes #1297

Codecov Report
Attention: Patch coverage is 40.00000% with 6 lines in your changes missing coverage. Please review.

Project coverage is 87.91%. Comparing base (70f3e14) to head (d85c48e).

Files with missing lines
Patch %
Lines

src/error.rs
40.00%
6 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1686      +/-   ##
==========================================
- Coverage   88.01%   87.91%   -0.10%
==========================================
  Files          16       16
  Lines        5805     5811       +6
==========================================
  Hits         5109     5109
- Misses        696      702       +6

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


Added missing parslet dependency to gemspec

parslet is a dependency of the sdp gem: https://github.com/turboladen/sdp/blob/master/sdp.gemspec, and I dont think it should be added here; that would mean maintaining the dep in 2 places.  You can see there that the version spec is ~>1.1.0.
I think I recently ran into what Im guessing youre running in to, where youve got parslet ~>1.1.0 installed, as well as >=1.2.0, and requiring rtsp is complaining about the parslet dependencyis that right?  If thats the case, Im not sure what the right fix is (as it seems to me the RubyGems wasnt finding the right version of the gem to require); as a (poor) workaround, I just uninstalled the parslet versions >= 1.2.0.  Do you have a better suggestion?
On Oct 31, 2011, at 11:43 AM, tindron wrote:

You can merge this Pull Request by running:
git pull https://github.com/tindron/rtsp patch-1
Or you can view, comment on it, or merge it online at:
https://github.com/turboladen/rtsp/pull/6
-- Commit Summary --

Added missing parslet dependency to gemspec

-- File Changes --
M rtsp.gemspec (1)
-- Patch Links --
https://github.com/turboladen/rtsp/pull/6.patch
https://github.com/turboladen/rtsp/pull/6.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/turboladen/rtsp/pull/6

Never mind--you're right!  I forgot about transport_parser!


Characters lost over USB-serial link.

Some characters are lost sometimes in the serial terminal.  Workaround: execute the command again. The
frequency of occurence of this varies between operating systems and seems to be worse on Windows. At
this time, this is considered a minor cosmetic issue and no plans are in place to fix it short-term.

Closing as will not fix as a workaround is available.


Add ability to specify installed shell

This PR changes the install.sh script to make it possible to specify which shell to install for, e.g. ./install.sh bash or ./install.sh zsh.
It also fixes the bug where running uninstall.sh does not remove the comment line # Source function script for 'venv' command from the rc files.
Closes #7
Closes #27

Closed in favour of https://github.com/SallingGroup-AI-and-ML/venv-cli/pull/29


Add CC-BY-SA license and links in footers

Per #634 , this adds a LICENSE.md, a note in CONTRIBUTING.md, and footers in all languages on the site referencing the Creative Commons Attribution-ShareAlike 3.0 License.
@dougwilson  @jasnell @mikeal

+1
On Jun 30, 2016 4:29 PM, "Rand McKinney"<EMAIL_ADDRESS>wrote:

This adds a LICENSE.md, a note in CONTRIBUTING.md, and footers in all
languages on the site referencing the Creative Commons
Attribution-ShareAlike 3.0 License.
@dougwilson https://github.com/dougwilson @jasnell
https://github.com/jasnell @mikeal https://github.com/mikeal
You can view, comment on, or merge this pull request online at:
https://github.com/expressjs/expressjs.com/pull/664
Commit Summary

Add CC-BY-SA license and links in footers
Add license file and update footers

File Changes

M CONTRIBUTING.md
https://github.com/expressjs/expressjs.com/pull/664/files#diff-0 (3)
A LICENSE.md
https://github.com/expressjs/expressjs.com/pull/664/files#diff-1
(123)
M _includes/footer/footer-de.html
https://github.com/expressjs/expressjs.com/pull/664/files#diff-2 (3)
M _includes/footer/footer-en.html
https://github.com/expressjs/expressjs.com/pull/664/files#diff-3 (3)
M _includes/footer/footer-es.html
https://github.com/expressjs/expressjs.com/pull/664/files#diff-4 (3)
M _includes/footer/footer-fr.html
https://github.com/expressjs/expressjs.com/pull/664/files#diff-5 (3)
M _includes/footer/footer-it.html
https://github.com/expressjs/expressjs.com/pull/664/files#diff-6 (3)
M _includes/footer/footer-ja.html
https://github.com/expressjs/expressjs.com/pull/664/files#diff-7 (3)
M _includes/footer/footer-ko.html
https://github.com/expressjs/expressjs.com/pull/664/files#diff-8 (3)
M _includes/footer/footer-pt-br.html
https://github.com/expressjs/expressjs.com/pull/664/files#diff-9 (3)
M _includes/footer/footer-ru.html
https://github.com/expressjs/expressjs.com/pull/664/files#diff-10
(3)
M _includes/footer/footer-sk.html
https://github.com/expressjs/expressjs.com/pull/664/files#diff-11
(3)
M _includes/footer/footer-uk.html
https://github.com/expressjs/expressjs.com/pull/664/files#diff-12
(3)
M _includes/footer/footer-uz.html
https://github.com/expressjs/expressjs.com/pull/664/files#diff-13
(3)
M _includes/footer/footer-zh-cn.html
https://github.com/expressjs/expressjs.com/pull/664/files#diff-14
(3)
M _includes/footer/footer-zh-tw.html
https://github.com/expressjs/expressjs.com/pull/664/files#diff-15
(3)
M css/style.css
https://github.com/expressjs/expressjs.com/pull/664/files#diff-16
(6)

Patch Links:

https://github.com/expressjs/expressjs.com/pull/664.patch
https://github.com/expressjs/expressjs.com/pull/664.diff

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/expressjs/expressjs.com/pull/664, or mute the thread
https://github.com/notifications/unsubscribe/AAa2ecJUmslm7A5RB09CaR23f0sQ68Q1ks5qRFFAgaJpZM4JCr6w
.


AzureDataStudioPostgresExtension_Manage_Settings_DeveloperTool:There is no name defined for the Enable start debugging checkbox.

https://msdata.visualstudio.com/Database Systems/_workitems/edit/1276726

ADS
Version: 1.32.0-insider (user setup)
Commit: 991b9af
Date: 2021-08-06T05:23:36.445Z
VS Code: 1.56.0
Electron: 12.0.7
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19043
Extension
PostgreSQL 0.2.7
Repro Steps:
Launch the application-Azure Data Studio and install extension PostgreSQL.
Tab till new connection button and press enter.
Tab till connection type dropdown and select postgresql.
Fill out the required details and tab till connect button and press enter.
Tab till manage button and press enter.
Tab till settings button and press enter.
Tab till search field and type pgsql.
Tab till Enable start debugging checkbox.
Open developer tool using ctrl+shift+I and check if the name is defined for the checkbox.
Actual:
There is no name defined for the Enable start debugging checkbox.
Expected:
The name should be defined as Enable start debugging checkbox
User Impact:
Screen Reader users will get wrong information regarding the checkbox

@nasc17 this is a vscode feature, please open an issue in VSCode repo and resolve your bug against it.


Modifications for GSD ensemble use case

Create a branch for modifications to run the NOAA/ESRL/GSD ensemble use case.
At some point this will probably meld with HWT branch based off issue #111

An initial release of the HRRR ensemble use case for GSD is implemented.
Current review, testing and evaluation has begun by GSD
This implementation only supports the requirements from the initial
ensemble surface use case which was verification by initialization times.
KEEPing the feature_112_gsd_ensemble  branch during T and E.
feature_112_orig_ensemble_test branch was removed
The obs_error_table.txt file changed from MET version 7.1_beta6 to 8.0
Added support for this change to the branch
commit 4f395f75642a81

We were not able to produce repeatable results since we did not have
a seed set in the random number generator.
Added the rng random number generator to the Ensemble Stat config file
and a seed entry in order to produce repeatable output.
Changed the output flag to BOTH to produce individual statistical output
files.
I was able to produce the same results when comparing MET 8.0 output from
Jeff Beck's original scripts vs. the Calling MET from the METplus.
I only confirmed F00 and F36.  Handing over to Jeff Duda for validation of results.

This issue has been completed and feature_112_gsd_ensemble branch has been deleted.
Refer to #191 for continued work on gsd ensemble.


test(c/driver): fix clang-tidy warnings

Fixes #1927.

It doesn't look like it's that easy to ignore directories, but the "right" way to do it might be to run clang-tidy in nanoarrow and perhaps ignore the nanoarrow headers here (or if warnings are OK, just live with the warnings for now). The nanoarrow repo is undergoing lots of general tidying at the moment and I can make sure clang-tidy is a part of that ( apache/arrow-nanoarrow#537 ).

Yeah, I was trying to figure out how to just ignore Nanoarrow. I suppose we could invoke jq to remove it from the compilation database... :grimacing:

I think the actual errors might be solved by ensuring that the correct standard library is installed? I see that the first google result here is one of your blog posts, but perhaps the symlink fix isn't working anymore (or is still picking up the wrong -std library?)

D'oh...


Add dev-project-launcher extension

Description
Adding new extension Dev Porject Launcher which basically helps you to easily open your projects with JetBrains IDE's or VSCode. This extension also let's you customize the IDE shortcuts and provides and easy navigation through directories
Note: This is the first version of this extension, the idea is to have a start point so I can add more features if the extension add some value to the community.
The command receives the base path (the path which will be used to display projects) by argument

Screencast
Navigate through your projects 🧭

Customize your IDE shortcuts ⌨

Open your project/file with any IDE ⚡

Checklist

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

Hi! thanks for reviewing this really appreciate it 🙌. The main use case is to "Open any development project with vscode editor or jetbrain IDE"(for now that is the scope, in the future I want to let the users add their own favourite text editor/IDE to be able to open projects with it)
This is mainly to avoid the following repetitive workflow:

Open your text editor/IDE and then select the project that I want to work on
Open the terminal, cd into the project and then open it with the text editor/IDE

Sounds a bit like Projects extension, could you check that out - it might do most of what you want to

I have been trying to figure out how to use this tool and how it can benefit users. Can you show me a screencast of how you'd use it?


KAFKA-4936: Add dynamic routing in Streams

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

\cc @bbejeck @vvcephei

@mjsax my current solution is to test
if (partitioner instanceof WindowedStreamPartitioner && ((WindowedStreamPartitioner) partitioner).topic() == null) {
                    partition = ((WindowedStreamPartitioner) partitioner).partition(topic, (Windowed) key, value, partitions.size());

at runtime, which should work but a bit ugly. I think it is OK for this PR itself.

Agreed -- didn't want to imply to fix it with this PR. But might be worth to fix properly with a follow up KIP.

Agreed -- didn't want to imply to fix it with this PR. But might be worth to fix properly with a follow up KIP.

Sounds good, I'll create a JIRA.

@mjsax while working on the window stream partitioner along with merging single topic to topic extractor, I realized the root cause is because in StreamPartitioner interface we do not pass in the topic name, which makes less sense while we are adding dynamic routing to sink node since the topic name would not be able to always pre-known.
So I'm modifying this and include it as part of the public API changes in the KIP wiki. Will ask for recasting the vote.

@guozhangwang Sounds good to me!

@mjsax @bbejeck updated PR for reviews again. Also updated the description for the core changes.

@mjsax updated on comments again.

One last thing: we need to update the docs accordingly.

Yup, that's my plan once the KIP is accepted, and the public changes are final.

I've addressed the meta comment on SinkNode#topicName to make its retruned value nullable.


Cap long lines

I'm having issues where I have very long variables (like a spreadsheet loaded in memory) and so when TBVaccine prints that, I lose everything else in my console buffer. Here is a quick and dirty hack to cap line length. It works by dropping ANSI sequences from long variable lines, and cap  their length at 79*4 chars (approx. 4 output lines). A note is added to the line that there is more un-printed data.
(I can't figure out how to get decent lengths with normal string slicing on strings with ANSI codes embedded. For example, the output line |     __annotations__ = {} clocks in with a length of 148 (!) due to ANSI control codes.)
The downside of dropping ANSI sequences like this is that the line won't be coloured....

P.S. I think the variable printing is an awesome addition! Thanks for adding it!

This looks good to me, can you post a screenshot with the before and after so I can see how it looks on your data? Thanks!

Before (~1,500 lines in this case):

After:

(before, when I was testing it, none of the variable lines where being color-ed, so I wasn't worried about losing that formatting)

(I figure out what is going on with the colours... initializing colorama means that colours beyond the basic 16 aren't displayed)

Looks great, just a minor typo and we're good to merge, thank you!

Thank you!


Installation - Dotnet core on windows throw error while running run.bat

This happened after fresh installation of wexflow-4.0-windows-dotnet-core. Wexflow wasn't installed on my machine. I followed this guide and after double clicking on run.bat, it throw error

Unhandled Exception: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Wexflow-dotnet-core\Database\Wexflow.db'.

Turns out it was expecting Database directory in C:\Wexflow-dotnet-core directory. I created Database folder manually and then again started run.bat and this time around it worked successfully.
@aelassas Seems like install.bat should create this directory.

Yes, this is a bug that I will fix in the version 4.2.

@youngsmith1  I fixed this issue in the version 4.2 that I've just released.
Can you test on your side and tell me if it's fixed?

@youngsmith1 Can I close this issue?

@aelassas I have tested version 4.2 and is working fine now. Database directory is created this time around. i am closing this issue.


Users should be able to delete their SSH key(s) from the list.

Right now to delete any SSH key(s) from the list of SSH key management user has to run this command: rm ~/.ssh/key_name*
As a user, I wanna be able to delete key(s) with the button click.
delete or - buttons can be placed on the opposite of each key.

Fixed in Master.

Changes have been already done

I saw that. Looks good, I think it's a straightforward solution. Two minor improvements:

Make the buttons a little bit bigger, so there is more padding either side of the text (maybe another 10-20 px). Right now it's too crowded.

The Remove Key button should only be active when a key is selected. If no key is selected, it should be disabled, with grey text not black. (Don't make it such a light grey that it cannot easily be read by the user, though.) If the button is active when no key is selected from the list, what happens when you click it? Nothing should happen, so better to disable the button.

Tested the fix on Debian, Windows, MacOS, and Ubuntu.
Fixed in prod


Command to export a project for Linux

Add a new export command to export the project as a distributable package for the Linux platform.
Options:

TODO

Parameters:

Name of the target platform

Constraints:

Target platform must be Linux.
Project must be already built. Otherwise, provide a tip on how to use build

This issue can be bring forward thank to #44 . The scope is extended to the current platform (i.e. Linux > Linux, Windows > Windows, ...) since support for other operating system was added after the creation of this issue.
New requirements:

[ ] export <binary> command must chain all actions that are required to create the final package:

building source code;
processing assets;
packaging bundles;
creating an archive (e.g. zip, tar.gz) or a container image.

[ ] the optimal permutation for release (i.e.release + monolithic) is used by default. However, additional options allow to set any other possible permutation. If it isn't already installed, the permutation must be added to the current engine version;
[ ] user can append additional options to skip one or more of these phases, such as --no-build or --no-process. This allows to re-use the same files that were already created in a previous run;
[ ] by default all assets are packaged into bundles, splitting the ones that are related to the project (game_<platform>.pak) from the ones that are specific for the engine (engine_<platform>.pak);
[ ] if a user needs of a more complex splitting layout, a export assets command opens the GUI of AssetBundler. The generated files can then be passed as option of export <binary> skipping the second and third phases automatically.


can't compare arrays with null elements

How to reproduce:
val ar1 = ArrayAnyRef
val ar2 = ArrayAnyRef
val eq = java.util.Arrays.equals(ar1, ar2)
the Arrays.equals calls a method $dp_equalsOZ, where there is:
if (((!(!(instance && instance.$classData))) || (instance === null))) {
return instance.equalsOZ(x0)
which runs into 2nd line when instance is null.

Thanks for the report.
For code snippets, you can use triple-backticks to correctly format them:
```scala
val ar1 = Array[AnyRef]
```

renders as
val ar1 = Array[AnyRef]


[bug 1196244] Remove admin.autodiscover from url conf.

https://docs.djangoproject.com/en/1.8/ref/contrib/admin/#discovery-of-admin-files

Tested it locally and admin entries still exists. LGTM
r+ :rabbit:


ESP32 DevKitC - [MQTTEcho] ERROR:  MQTT echo failed to connect with error 1.

I am running these steps in order to connect to MQTT broker from the AWS ESP32 example:
https://docs.aws.amazon.com/freertos/latest/userguide/getting_started_espressif.html
When esp32 is trying to connect to MQTT broker it is showing [MQTTEcho] ERROR:  MQTT echo failed to connect with error 1.
System information

ESP32 DevKitC V1
Operating System Linux
Version of Amazon FreeRTOS (run git describe --tags to find it): v1.4.6-58-ga81bf209
Project MQTT Sub pub Demo

Expected behavior
Demo should connect to MQTT broker
Screenshots or console output
I (8534) WIFI: SYSTEM_EVENT_STA_GOT_IP
2 840 [IP-task] vDHCPProcess: offer c0a8046aip
3 841 [main] WiFi Connected to AP. Creating tasks which use network...
4 842 [main] Write certificate...
I (8554) PKCS11: Initializing NVS partition: "storage"
5 846 [main] Write device private key...
6 856 [main] Creating MQTT Echo Task...
7 856 [MQTTEcho] MQTT echo attempting to connect to XXXXXXXXXX-ats.iot.us-east-1.amazonaws.com.
8 856 [MQTTEcho] Sending command to MQTT task.
9 857 [MQTT] Received message 10000 from queue.
10 1858 [IP-task] Socket sending wakeup to MQTT task.
11 2358 [MQTT] About to close socket.
12 2358 [MQTT] Socket closed.
13 2358 [MQTT] Stack high watermark for MQTT task: 4696
14 2358 [MQTT] Notifying task.
15 2358 [MQTT] Received message 0 from queue.
16 2358 [MQTTEcho] Command sent to MQTT task failed.
17 2358 [MQTTEcho] ERROR:  MQTT echo failed to connect with error 1.
18 2358 [MQTTEcho] MQTT echo test could not connect to broker.
19 2358 [MQTTEcho] Sending command to MQTT task.
20 2359 [MQTT] Received message 20000 from queue.
21 2359 [MQTT] Notifying task.
22 2360 [MQTTEcho] Command sent to MQTT task passed.
23 2360 [MQTTEcho] MQTT echo demo finished.
24 2360 [MQTTEcho] ----Demo finished----
I am testing the connection from my computer using mosquitto_pub client and the connection is successful:
$ mosquitto_pub -d --cafile AmazonRootCA1.pem --cert esp32-reedswitch-aws-certificate/27eb999b86-certificate.pem.crt --key esp32-reedswitch-aws-certificate/27eb999b86-private.pem.key -h XXXXXXXX-ats.iot.us-east-1.amazonaws.com -p 8883 -m "test message" -t "freertos/demo/echo" -q 1
Client mosqpub/14670-g4560 sending CONNECT
Client mosqpub/14670-g4560 received CONNACK
Client mosqpub/14670-g4560 sending PUBLISH (d0, q1, r0, m1, 'freertos/demo/echo', ... (12 bytes))
Client mosqpub/14670-g4560 received PUBACK (Mid: 1)
Client mosqpub/14670-g4560 sending DISCONNECT
I've already cleaned up the certificate, thing and policy using the command BASE_DIRECTORY/tools/aws_config_quick_start/SetupAWS.py cleanup but it is still showing the same MQTT failed to connect with error 1.
Thank you!

Hi, thanks for reaching out - I'm sorry to hear that you're having issues.
MQTT broker connection problems are often related to device credentials, so would you mind double-checking a few values in your current setup? If you ran SetupAWS.py cleanup to clear the credentials out of your configuration files, some of these values might be empty until you run SetupAWS.py setup again.

In the demos/common/include/aws_clientcredential.h file, do the MQTT endpoint, Thing name, and WiFi credential values all look correct?

In demos/common/include/aws_clientcredential_keys.h, do you see the certificate and RSA private key which were configured for your device and which worked with your mosquito client connection?

Can you verify that the setup script created a 'Thing' record in your AWS 'IoT Core' dashboard? (Click 'Manage' on the left sidebar to view all of your Things.)

Thank you for your patience, and feel free to let us know if any of those questions are unclear.

hi @WRansohoff, this is the content of aws_clientcredential.k:
#ifndef AWS_CLIENTCREDENTIAL__H
#define AWS_CLIENTCREDENTIAL__H
#include "aws_clientcredential_keys.h"
#define clientcredentialIOT_THING_NAME "mythingname"
#define clientcredentialMQTT_BROKER_PORT 8883
#define clientcredentialGREENGRASS_DISCOVERY_PORT 8443
#define clientcredentialWIFI_SSID       "myssid"
#define clientcredentialWIFI_PASSWORD   "myssidpassword"
#define clientcredentialWIFI_SECURITY   eWiFiSecurityWPA
#endif
my aws_clientcredential_key.h is:
/*
#ifndef AWS_CLIENT_CREDENTIAL_KEYS_H
#define AWS_CLIENT_CREDENTIAL_KEYS_H
#include <stdint.h>
/*
#define keyCLIENT_CERTIFICATE_PEM
"-----BEGIN CERTIFICATE-----\n"
"MIIDWjCCAkKgAwIBAgIVAMZGI52JduxC6yIvir4ccTPoJIkmMA0GCSqGSIb3DQEB\n"
...
"j0AZLKTdyH+YUBxY+H0/5ohH4LQtbjbZ0wicnl8wvxih1DO+rW2RQhNHME4ezA==\n"
"-----END CERTIFICATE-----\n"
/*
#define keyJITR_DEVICE_CERTIFICATE_AUTHORITY_PEM  NULL
/*
#define keyCLIENT_PRIVATE_KEY_PEM
"-----BEGIN RSA PRIVATE KEY-----\n"
"MIIEowIBAAKCAQEAo6T61BDyXjjCL5Afj/dCEQlz5q0hPtm5wwCkrO4gbtCbRLZj\n"
...
"ur4oKUxXiEH15GAPo9HIenR3i256FSq7Xz3ufDRgScEdKb50oLFo\n"
"-----END RSA PRIVATE KEY-----\n"
/* The constants above are set to const char * pointers defined in aws_demo_runner.c,
extern const char clientcredentialCLIENT_CERTIFICATE_PEM[];
extern const char* clientcredentialJITR_DEVICE_CERTIFICATE_AUTHORITY_PEM;
extern const char clientcredentialCLIENT_PRIVATE_KEY_PEM[];
extern const uint32_t clientcredentialCLIENT_CERTIFICATE_LENGTH;
extern const uint32_t clientcredentialCLIENT_PRIVATE_KEY_LENGTH;
#endif /* AWS_CLIENT_CREDENTIAL_KEYS_H */
`
The setup script created the thing, certificate and policies. I can see it from my IoT Core Console.
Thanks

Okay, that does look correct - and just to make sure, in the aws_clientcredential.h file, there should also be a line which looks like this, with the correct AWS region:
static const char clientcredentialMQTT_BROKER_ENDPOINT[] = "xxxx-ats.iot.[region].amazonaws.com";
If your mosquito client is still able to publish a message successfully, then it sounds like the AWS permissions are probably set up correctly with your endpoint and certificates.
So just to double-check, could you also verify that the IDF_PATH environment variable is not set when you build the ESP32 demo project? There is a specific version of ESP-IDF included in the Amazon FreeRTOS repository under lib/third_party/mcu_vendor/espressif/esp-idf, and sometimes issues can emerge if a different version of the toolchain is already installed and being used.
Thanks for your patience.

hi @WRansohoff
aws_clientcredential.h is:
grep MQTT_BROKER aws_clientcredential.h
static const char clientcredentialMQTT_BROKER_ENDPOINT[] = "XXXXXXX-ats.iot.us-east-1.amazonaws.com";
Before compiling amazon-freertos I unset the variable with: unset IDF_PATH
Compilation shows warnings,  but my ESP32 get flashed with no issues. ESP32 connects successfully to my wifi and it fails when connecting to mqtt broker.

Huh, that does all look like it should work - which version of the Amazon FreeRTOS repository are you using? (You can check the commit hash that you're on with git rev-parse HEAD.)

Hi @WRansohoff, it is: git rev-parse HEAD
f0c0efc79bcd2f506186e47b6f2989eb58b25ed6

Hi, are you still having issues? Could you let me know what the policy attached to your thing's certificate is?
To use the echo demo we have users configure the policy from https://docs.aws.amazon.com/freertos/latest/userguide/get-started-freertos-thing.html:
{
    "Version": "2012-10-17",
    "Statement": [
    {
        "Effect": "Allow",
        "Action": "iot:Connect",
        "Resource":"arn:aws:iot:<aws-region>:<aws-account-id>:*"
	},
    {
        "Effect": "Allow",
        "Action": "iot:Publish",
        "Resource": "arn:aws:iot:<aws-region>:<aws-account-id>:*"
    },
    {
         "Effect": "Allow",
         "Action": "iot:Subscribe",
         "Resource": "arn:aws:iot:<aws-region>:<aws-account-id>:*"
    },
    {
         "Effect": "Allow",
         "Action": "iot:Receive",
         "Resource": "arn:aws:iot:<aws-region>:<aws-account-id>:*"
    }
    ]
}

Please make sure this is correct. We typically have connection errors when this is the case.
Although it is not recommended, you can also allow everything just to narrow down that your policy is indeed the issue:
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "iot:*"
      ],
      "Resource": "*"
    }
  ]
}


Added Dispatchers.Main coroutine scope when invoking listener.onDownloadStart()

In the function download(_: String, _: String) of PdfDownloader.kt, listener.onDownloadStart() was being invoked in the Dispatchers.IO coroutine context.

This is resulting in Exception if the observer of this callback wants to make some UI change on main thread.

Added Dispatchers.Main coroutine scope when invoking onDownloadStart() callback.

Hi, is there any update on the Pull Request?


"Array is empty" error message from ExecutionDistance class in utbot-summary module

Description
For many summary test generation the following message "Array is empty" is raised
To Reproduce
Generate tests without mocks for the Stats class from guava-26
Expected behavior
Tests are supposed to be generated.
Actual behavior
Tests are not generated and the mentioned earlier exception is found

@Markoutte did you have this exception?

Looks like yes

Some extr acontext: If we use concrete execution not in the end of analysis, the engine produces UtExecution with the empty paths, because ConcreteExecutor doesn't know hot to translate bytecode to soot.

@sergeypospelov thanks, looks like now we have a temporary solution and it should be revisited in the nearest future

Fixed in the #567


"Moldova-Sulița" is listed in the drop-down menu

Description:
"Moldova-Sulița" is listed in the drop-down menu alongside its corresponding county according to the law
Precondition:
The website is up an running.

Step 1
Type "Moldova-Sulița" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Moldova-Sulița, SUCEAVA".