selection window  not displayed correctly

Hi,
When I do z= for example to select a translation for a word, the selection window is really partially displayed and I can only see from number 35 onwards.
These are my settings:
[Tabline]
Visible = true
[MiniMap]
Visible = false
[SideBar]
 Visible = false
 DropShadow = false
 Width = 200
 AccentColor = "#5596ea"

[Editor]

ExtTabline  = false
ExtCmdline = false
ExtPopupmenu = false

Could it be fixed?
Thanks

The exact problem is that it is on the background instead of foreground

Can confirm that it works


Cookie is not accessible by registerApolloClient

The GraphQL context setup in the handler always returns undefined pages that use the getClient() functions. The getClient() is set with the code below.
import { ApolloClient, HttpLink, InMemoryCache } from '@apollo/client';
import { registerApolloClient } from '@apollo/experimental-nextjs-app-support/rsc';
import { headers } from 'next/headers';

export const { getClient } = registerApolloClient(() => {
  const link = new HttpLink({
    uri: 'http://localhost:3000/api/graphql',
    credentials: 'same-origin',
  });

  // headers();
  return new ApolloClient({
    cache: new InMemoryCache(),
    link,
  });
});

The context is set in the startServerAndCreateNextHandler() this way
const handler = startServerAndCreateNextHandler<NextRequest>(apolloServer, {
  context: async (req) => {
    const fakeSessionToken = req.cookies.get('fakeSession');
    console.log('fakeSessionToken', fakeSessionToken);

    return {
      req,
      fakeSessionToken,
    };
  },
});

Every console.log of the context.fakeSessionToken on every query returns undefined when the query only uses the getClient() function. The fakeSessionToken is also undefined within the context when the query is a getClient()
The expected result of fakeSessionToken is logged into the console whenever a mutation operation is performed.
How to reproduce
Repro Repository

Clone the above repository

git clone https://github.com/Eprince-hub/graphql-context-repro.git

Move into the folder and run the project

cd graphql-context-repro

Install dependencies

pnpm i

Start the project

pnpm dev

OR: Run all the above commands with
git clone https://github.com/Eprince-hub/graphql-context-repro.git && cd graphql-context-repro && pnpm i &&  pnpm dev

Visit the website at http://localhost:3000/
Open up your console so that you can see the console.logs
Click on the login button to create the cookies
Click on the View animals navigation to move to the animals page
NOTE: This page uses getClient() query, so the fakeSessionToken context will be undefined even though it exists on the browser
Navigate to the Create animal and click on the Create Animal button
NOTE: The fakeSessionToken will have the expected value at this time

The home/login and the create animal pages use mutation and always log the correct value of the cookies to the console, but the /animals that use the getClient() always logs undefined. In my main project, this behavior is the same for all the pages, where only getClient() is used
Expected behavior

That context returns the cookie's value also when being accessed by the getClient() function
That all resolvers should get the correct value for the context at all time, instead of the undefined

This causes many issues when we need to authenticate a user via the context object on queries.
I think it is slightly related to this issue https://github.com/apollographql/apollo-client-nextjs/issues/21, but not exactly

If you use React Server Components, you send a request from your server to your server. These requests do not automatically contain any cookies, as they would be sent from a browser to the server.
You will need to manually load these cookies in a custom setContext link by calling the cookies function of Next.js and manually set the cookies that you want to forward in that link.

@phryneas, Thank you so much for your reply. Following the documentation here I tried to set the context in the Apollo client like this
const browserCookies = setContext(() => {
  return {
    headers: {
      cookies: cookies().get('fakeSession'),
    },
  };
});

export const { getClient } = registerApolloClient(() => {
  const link = new HttpLink({
    uri: 'http://localhost:3000/api/graphql',
    credentials: 'same-origin',
  });

  headers();
  return new ApolloClient({
    cache: new InMemoryCache(),
    link: browserCookies.concat(link),
  });
});

But I am still getting it as undefined, maybe this is not the right way to do it
Can you please, let me know the right way to get this work? Must I send the cookies with the request? I would appreciate it if there is an example that can clear things out a little bit more

I believe you would need to do something along the lines of
const browserCookies = setContext(() => {
  return {
    headers: {
      cookie: `fakeSession=${cookies().get('fakeSession')};`
   },
  };
});

Thanks for the feedback. Helped a lot. Setting up the getClient() as shown below solved my issue
const browserCookies = setContext(() => {
  return {
    headers: {
      cookie: `fakeSession=${cookies().get('fakeSession')?.value}`,
    },
  };
});

export const { getClient } = registerApolloClient(() => {
  const link = new HttpLink({
    uri: 'http://localhost:3000/api/graphql',
    credentials: 'same-origin',
  });

  return new ApolloClient({
    cache: new InMemoryCache(),
    link: browserCookies.concat(link),
  });
});

I can now set the cookie context in the handler and have access to it in every resolver
const handler = startServerAndCreateNextHandler<NextRequest>(apolloServer, {
  context: async (req) => {
    const fakeSessionToken = req.cookies.get('fakeSession');
    console.log('fakeSessionToken', fakeSessionToken);
    return {
      req,
      fakeSessionToken,
    };
  },
});

With this update, I will be closing this issue, as I am not having the problem anymore
Thank you🙏


feat: update packages

updated primary package
updated dependabot.yml to target the development branch

Closes #56

:tada: This PR is included in version 2.1.0-beta.2 :tada:
The release is available on:

npm package (@develop dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[BUG]: drizzle-kit CLI pull/introspect schemaFilters parameter is ignored

Report hasn't been filed before.

[X] I have verified that the bug I'm about to report hasn't been filed before.

What version of drizzle-orm are you using?
0.36.4
What version of drizzle-kit are you using?
0.28.0
Other packages
No response
Describe the Bug
The drizzle-kit introspect CLI parameter schemaFilters is ignored, e.g.
npx drizzle-kit introspect --url "postgresql://postgres:postgres@<IP_ADDRESS>:54322/postgres" --dialect postgresql --schemaFilters pgmq --out test

outputs
Pulling from ['public'] list of schemas

Have the same issue.


Display Trådfri Smart Plug as Plug

Hello,
I bought a Trådfri smart plug and connected it to homebridge-hue via deConz. In the home app on my iPhone it shows as a light.
Currently I have a fan connected to it. Is it possible to change the device type in the configuration?

Yes, create an outlet resourcelink.

Yes, create an outlet resourcelink.

@ebaauw can you send me an example?

@ebaauw can you send me an example?

I've written up a Wiki: https://github.com/ebaauw/homebridge-hue/wiki/Resource-Links

I've written up a Wiki: https://github.com/ebaauw/homebridge-hue/wiki/Resource-Links


Binary Text Classification

How to finetune KnowBERT for binary text classification tasks?
For example, given a sequence of words predict its polarity.
Thanks!

The Words-In-Context model is an example of binary classification -- predict whether the usage of a word in two contexts is the same sense or not.  See wic_dataset_reader.py and wic.jsonnet.

Thanks for you reply!
Can you explain the following lines in kb/evaluation/wic_dataset_reader.py:
# get the indices of the marked words
# index in the original tokens
idx1, idx2 = [int(ind) for ind in tokens[2].split('-')]
offsets_a = [1] + token_candidates['offsets_a'][:-1]
idx1_offset = offsets_a[idx1]
offsets_b = [token_candidates['offsets_a'][-1] + 1] + token_candidates['offsets_b'][:-1]
idx2_offset = offsets_b[idx2]

fields['index_a'] = LabelField(idx1_offset, skip_indexing=True)
fields['index_b'] = LabelField(idx2_offset, skip_indexing=True)

I didn't understand them, are they related to the WiC task?
Thanks!

Yes these are related to the WiC task -- it's code to find the indices of the marked word in each sentence (see Table 1 of https://arxiv.org/abs/1808.09121)

So, the following is a valid data reader to load a single sentence and finetune the model using it, right?
from typing import Iterable
from allennlp.data.dataset_readers.dataset_reader import DatasetReader
from allennlp.data.fields import LabelField
from allennlp.data.instance import Instance
from kb.bert_tokenizer_and_candidate_generator import TokenizerAndCandidateGenerator
from allennlp.common.file_utils import cached_path

@DatasetReader.register("x")
class XDatasetReader(DatasetReader):
    def __init__(self,
                 tokenizer_and_candidate_generator: TokenizerAndCandidateGenerator,
                 entity_markers: bool = False):
        super().__init__()
        self.label_to_index = {'1': 1, '0': 0}
        self.tokenizer = tokenizer_and_candidate_generator
        self.tokenizer.whitespace_tokenize = True
        self.entity_markers = entity_markers

    def text_to_instance(self, line) -> Instance:
        raise NotImplementedError

    def _read(self, file_path: str) -> Iterable[Instance]:
        """Creates examples for the training and dev sets."""

        sentences = list()
        labels = list()

        with open(cached_path(file_path + '-x.csv'), 'r') as file:
            reader = csv.reader(file)

            for row in reader:
                sentences.append(row[1].strip())

        with open(cached_path(file_path + '-y.csv'), 'r') as file:
            reader = csv.reader(file)

            for row in reader:
                labels.append(int(row[1]))

        assert len(labels) == len(sentences), f'The length of the labels and sentences must match. ' \
            f'Got {len(labels)} and {len(sentences)}.'

        for line, label in zip(sentences, labels):
            text_a = line

            token_candidates = self.tokenizer.tokenize_and_generate_candidates(text_a)
            fields = self.tokenizer.convert_tokens_candidates_to_fields(token_candidates)
            fields['label_ids'] = LabelField(self.label_to_index[label], skip_indexing=True)

            instance = Instance(fields)

            yield instance

Also, I have one final question about training_config/downstream/wic.jsonnet  file, can I remove the num_steps_per_epoch option or I should calculate and put it?
Thanks!


Run specs also on TruffleRuby on Travis CI

This is just for testing. @ioquatix let me know if you will accept this as-is it or you would need something else.
TruffleRuby would work on Travis finally. https://github.com/travis-ci/travis-build/pull/1604

Coverage remained the same at 69.164% when pulling 4bbfa57262c3cc3893dfbffa5bf19dbe48e2aa03 on deepj:travis-truffleruby into 4f5c3d0568de11f912c15af0bb089847fc0afc15 on socketry:master.

Coverage remained the same at 69.164% when pulling 4bbfa57262c3cc3893dfbffa5bf19dbe48e2aa03 on deepj:travis-truffleruby into 4f5c3d0568de11f912c15af0bb089847fc0afc15 on socketry:master.

Excellent.


Allow virtual cards receipts to be uploaded while processing

On Slack:

Feature request, sorry if this has been made before: What I find super tough right now about keeping up with uploading receipts is that you can’t upload receipts while the charge is “Processing”. So I can’t use the card and then immediately upload the documentation. I have to remember to check back in 2-4 days if its settled yet

On our side, we must make sure that there's no risk of concurrency issues between the admin edit and the update triggered by the payment webhook event.

the pain point is a bit related to the one in this issue: https://github.com/opencollective/opencollective/issues/5696
of smoothing out the processes for Assignees when they 1) complete a purchase; 2) receive an email notification asking for a receipt upload; 3) upload a receipt
I would like to consider how to improve this very thoughtfully, taking into consideration that the Admins who take the responsibility of being card Assignees often have many other tasks on their plates. So anything we can do to alleviate their burdens would be ideal.
To consider: what a virtual card purchase looks like in practice.

purchase is made (either by Assignee, or another Admin who can view the same card details)
email is sent asking for receipt upload
the Assignee must locate the receipt (either in their own email, or from another Admin who used the card)
the Assignee needs to wait till the purchase has cleared before they can upload

perhaps having a single page where Assignees can manage all virtual card transactions (view: pending, completed, still needs receipts) would be a good idea?

perhaps having a single page where Assignees can manage all virtual card transactions (view: pending, completed, still needs receipts) would be a good idea?

As an admin on an org with multiple virtual cards, I can say this would be super helpful! It's a bit discombobulating right now to find and flip through virtual card charges and find things that need action

Fyi, I think we're seeing customers uploading receipts while in processing. Or is it just editing the Expense? I had to make this patch for this reason https://github.com/opencollective/opencollective-api/pull/7754

nope https://opencollective.com/octobox/expenses/91729

@znarf : With regard to our discussion about uploading the receipt after using the virtual card. I was thinking now that we send an email notification virtualcard.purchase.hbs at authorization (after https://github.com/opencollective/opencollective-api/pull/7815) we could add a line in this email notifying the user that they could upload the receipt if they wish to do so (with a link to the appropriate expense) ? 🤔

Allow virtual cards receipts to be uploaded while processing

To come back at the root issue, just wanted to confirm this is already allowed.
@SudharakaP yes, we should change the wording and they something like "you can already attach a receipt if you have one".
But on the other end, we should make sure to not ask for a receipt later on if there is already one attached.

nope https://opencollective.com/octobox/expenses/91729

@BenJam I just worked with Virtual Cards charges that were processing today and could upload receipts.
https://opencollective.com/opencollective/expenses/92348 https://opencollective.com/opencollective/expenses/92342

@SudharakaP yes, we should change the wording and they something like "you can already attach a receipt if you have one".
But on the other end, we should make sure to not ask for a receipt later on if there is already one attached.

This is tackled at, https://github.com/opencollective/opencollective/issues/5951

Closing. Can be reopened if someone is not able to upload receipts while processing.


:sparkles: add cluster dashboard

Summary

Related issue(s)
Fixes #

Can you add a banner to say this is an experimental feature?

No,
Could we add some description in https://github.com/stolostron/rhacm-docs/pull/6450
Or just in the dashboard description?

both are fine for me. Please follow up. Thanks.


[Event Request] Table 38 "Purchase Header" - OnRecreatePurchLinesOnBeforeTransferSavedFields

We are migrating our code from NAV 2018 to BC16.4. In the table 38 Purchase Header, in the procedure RecreatePurchLines, we used to add a lot of our code. To do so, we need a IsHandled Flag and an event publisher here :

With this integration event :

Do you think it could be possible ?
Thanks for your work.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Haproxy reload not correctly in service loadbalance

we encounter the problem just like this haproxy-issue-48, and post a new issue. The old haproxy process will influence the new one that make the service visiting not stable. Until now I cannot find a solid solution and we make a little change when haproxy reload by -sf. if the old haproxy process still running, then kill it by kill -9 <pid>. It seems work fine but I don't know it would or not cause some bad affect when a lot of service create or modified. Did you have any suggestions or solutions that have no side effects?

@ZhuPeng we should already be reaping them (https://github.com/kubernetes/contrib/blob/master/service-loadbalancer/service_loadbalancer.go#L621) what image version are you using? @aledbf

@bprashanth I don't think the processes in question are zombies (I've been experiencing the same, or a similar issue). As far as I understand, the StartReaper routine will only reap zombie processes, i.e. ones which have terminated themselves.
I think the real issue is that the reloading process goes wrong, because two insances of the haproxy_reload script are allowed to execute simultaneously, and it's not designed for concurrency. Wrapping the script in a flock "mutex" solved the issue for me, I've been unable to reproduce a problem after that. I can send a PR with this if you approve.

@bprashanth what @pesho mention could be the reason (simultaneous reloads) but then that would mean that this ratelimiter is not working properly.

@aledbf this ratelimiter doesn't seem to protect against concurrent execution at all, unless I'm misunderstanding it. Doesn't it allow a "burst" of reloadQPS (10) simultaneous executions?

Doesn't it allow a "burst" of reloadQPS (10) simultaneous executions?

@pesho you are right. I forgot to check the definition and it's using 10 for both parameters

Ah, yeah the ratelimiter will only limit qps. The main sync loop of the service loadbalancer (https://github.com/kubernetes/contrib/blob/master/service-loadbalancer/service_loadbalancer.go#L459) shouldn't actually have multiple goroutines in there trying to reload haproxy (the work queue enforces that: https://github.com/kubernetes/contrib/blob/master/service-loadbalancer/service_loadbalancer.go#L492). However it sounds like we might be running into:
Service 1 changes
Serviceloadbalancer execs reload -s
Haproxy waiting on connections to terminate for soft reload
Service 2 changes
Serviceloadbalancer execs reload -s over the old haproxy
@pesho please send a pr if you've fixed it.

Submitted PR #327

@bprashanth  I self-build the service-loadbalance images using the souce code makefile, and I checkout it has proc.StartReaper().
@pesho I test your PR, but it seems not work. I use the version the contrib provided, which was 1.6 . What version of haproxy are you using?

@ZhuPeng can you test #328?

The test haproxy version was 1.6.0. I saw the master branch haproxy was upgrade to 1.6.2, but I cannot visit the www.haproxy.org.
I patched the PR 328, and the pods running log was below
I1214 09:40:57.412236       1 service_loadbalancer.go:567] Creating new loadbalancer: {Name:haproxy ReloadCmd:./haproxy_reload Config:/etc/haproxy/haproxy.cfg Template:template.cfg Algorithm: startSyslog:false lbDefAlgorithm:roundrobin exec:0x17ed660 reloadLock:0xc82022c0c0}
E1214 09:40:57.412380       1 service_loadbalancer.go:247] Get : unsupported protocol scheme ""
I1214 09:40:57.442721       1 service_loadbalancer.go:482] Sync triggered by service default/elasticsearch
I1214 09:40:57.442777       1 service_loadbalancer.go:444] Found service: {Name:elasticsearch:9200 Ep:[<IP_ADDRESS>:9200 <IP_ADDRESS>:9200] BackendPort:9200 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.442816       1 service_loadbalancer.go:444] Found service: {Name:elasticsearch-discovery:9300 Ep:[<IP_ADDRESS>:9300 <IP_ADDRESS>:9300] BackendPort:9300 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.442828       1 service_loadbalancer.go:400] No endpoints found for service kubernetes, port {Name: Protocol:TCP Port:443 TargetPort:{Kind:0 IntVal:443 StrVal:} NodePort:0}
I1214 09:40:57.442848       1 service_loadbalancer.go:444] Found service: {Name:mysql:3306 Ep:[<IP_ADDRESS>:3306] BackendPort:3306 FrontendPort:3306 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.442862       1 service_loadbalancer.go:444] Found service: {Name:newdeploy-master:8080 Ep:[<IP_ADDRESS>:8080] BackendPort:8080 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.442876       1 service_loadbalancer.go:444] Found service: {Name:nginxsvc:18080 Ep:[<IP_ADDRESS>:18080 <IP_ADDRESS>:18080] BackendPort:18080 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.442893       1 service_loadbalancer.go:444] Found service: {Name:nginxsvc:18443 Ep:[<IP_ADDRESS>:18443 <IP_ADDRESS>:18443] BackendPort:18443 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.453114       1 service_loadbalancer.go:302] haproxy -- cat: can't open '/var/run/haproxy.pid': No such file or directory
[WARNING] 347/094057 (22) : config : 'option forwardfor' ignored for frontend 'mysql:3306' as it requires HTTP mode.
[WARNING] 347/094057 (22) : config : 'option forwardfor' ignored for backend 'mysql:3306' as it requires HTTP mode.
I1214 09:40:57.453138       1 service_loadbalancer.go:482] Sync triggered by service default/elasticsearch-discovery
I1214 09:40:57.453171       1 service_loadbalancer.go:444] Found service: {Name:nginxsvc:18080 Ep:[<IP_ADDRESS>:18080 <IP_ADDRESS>:18080] BackendPort:18080 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.453195       1 service_loadbalancer.go:444] Found service: {Name:nginxsvc:18443 Ep:[<IP_ADDRESS>:18443 <IP_ADDRESS>:18443] BackendPort:18443 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.453211       1 service_loadbalancer.go:444] Found service: {Name:elasticsearch:9200 Ep:[<IP_ADDRESS>:9200 <IP_ADDRESS>:9200] BackendPort:9200 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.453224       1 service_loadbalancer.go:444] Found service: {Name:elasticsearch-discovery:9300 Ep:[<IP_ADDRESS>:9300 <IP_ADDRESS>:9300] BackendPort:9300 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.453238       1 service_loadbalancer.go:400] No endpoints found for service kubernetes, port {Name: Protocol:TCP Port:443 TargetPort:{Kind:0 IntVal:443 StrVal:} NodePort:0}
I1214 09:40:57.453252       1 service_loadbalancer.go:444] Found service: {Name:mysql:3306 Ep:[<IP_ADDRESS>:3306] BackendPort:3306 FrontendPort:3306 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.453267       1 service_loadbalancer.go:444] Found service: {Name:newdeploy-master:8080 Ep:[<IP_ADDRESS>:8080] BackendPort:8080 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.463282       1 service_loadbalancer.go:302] haproxy -- [WARNING] 347/094057 (28) : config : 'option forwardfor' ignored for frontend 'mysql:3306' as it requires HTTP mode.
[WARNING] 347/094057 (28) : config : 'option forwardfor' ignored for backend 'mysql:3306' as it requires HTTP mode.
I1214 09:40:57.463304       1 service_loadbalancer.go:482] Sync triggered by service default/kubernetes
I1214 09:40:57.463337       1 service_loadbalancer.go:444] Found service: {Name:elasticsearch-discovery:9300 Ep:[<IP_ADDRESS>:9300 <IP_ADDRESS>:9300] BackendPort:9300 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.463357       1 service_loadbalancer.go:400] No endpoints found for service kubernetes, port {Name: Protocol:TCP Port:443 TargetPort:{Kind:0 IntVal:443 StrVal:} NodePort:0}
I1214 09:40:57.463372       1 service_loadbalancer.go:444] Found service: {Name:mysql:3306 Ep:[<IP_ADDRESS>:3306] BackendPort:3306 FrontendPort:3306 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.463385       1 service_loadbalancer.go:444] Found service: {Name:newdeploy-master:8080 Ep:[<IP_ADDRESS>:8080] BackendPort:8080 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.463400       1 service_loadbalancer.go:444] Found service: {Name:nginxsvc:18080 Ep:[<IP_ADDRESS>:18080 <IP_ADDRESS>:18080] BackendPort:18080 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.463415       1 service_loadbalancer.go:444] Found service: {Name:nginxsvc:18443 Ep:[<IP_ADDRESS>:18443 <IP_ADDRESS>:18443] BackendPort:18443 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.463431       1 service_loadbalancer.go:444] Found service: {Name:elasticsearch:9200 Ep:[<IP_ADDRESS>:9200 <IP_ADDRESS>:9200] BackendPort:9200 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.473505       1 service_loadbalancer.go:302] haproxy -- [WARNING] 347/094057 (34) : config : 'option forwardfor' ignored for frontend 'mysql:3306' as it requires HTTP mode.
[WARNING] 347/094057 (34) : config : 'option forwardfor' ignored for backend 'mysql:3306' as it requires HTTP mode.
I1214 09:40:57.473529       1 service_loadbalancer.go:482] Sync triggered by service default/mysql
I1214 09:40:57.473573       1 service_loadbalancer.go:444] Found service: {Name:elasticsearch:9200 Ep:[<IP_ADDRESS>:9200 <IP_ADDRESS>:9200] BackendPort:9200 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.473598       1 service_loadbalancer.go:444] Found service: {Name:elasticsearch-discovery:9300 Ep:[<IP_ADDRESS>:9300 <IP_ADDRESS>:9300] BackendPort:9300 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.473611       1 service_loadbalancer.go:400] No endpoints found for service kubernetes, port {Name: Protocol:TCP Port:443 TargetPort:{Kind:0 IntVal:443 StrVal:} NodePort:0}
I1214 09:40:57.473626       1 service_loadbalancer.go:444] Found service: {Name:mysql:3306 Ep:[<IP_ADDRESS>:3306] BackendPort:3306 FrontendPort:3306 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.473640       1 service_loadbalancer.go:444] Found service: {Name:newdeploy-master:8080 Ep:[<IP_ADDRESS>:8080] BackendPort:8080 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.473654       1 service_loadbalancer.go:444] Found service: {Name:nginxsvc:18080 Ep:[<IP_ADDRESS>:18080 <IP_ADDRESS>:18080] BackendPort:18080 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.473669       1 service_loadbalancer.go:444] Found service: {Name:nginxsvc:18443 Ep:[<IP_ADDRESS>:18443 <IP_ADDRESS>:18443] BackendPort:18443 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.483849       1 service_loadbalancer.go:302] haproxy -- [WARNING] 347/094057 (40) : config : 'option forwardfor' ignored for frontend 'mysql:3306' as it requires HTTP mode.
[WARNING] 347/094057 (40) : config : 'option forwardfor' ignored for backend 'mysql:3306' as it requires HTTP mode.
I1214 09:40:57.483875       1 service_loadbalancer.go:482] Sync triggered by service default/newdeploy-master
I1214 09:40:57.483911       1 service_loadbalancer.go:444] Found service: {Name:elasticsearch:9200 Ep:[<IP_ADDRESS>:9200 <IP_ADDRESS>:9200] BackendPort:9200 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.483936       1 service_loadbalancer.go:444] Found service: {Name:elasticsearch-discovery:9300 Ep:[<IP_ADDRESS>:9300 <IP_ADDRESS>:9300] BackendPort:9300 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.483949       1 service_loadbalancer.go:400] No endpoints found for service kubernetes, port {Name: Protocol:TCP Port:443 TargetPort:{Kind:0 IntVal:443 StrVal:} NodePort:0}
I1214 09:40:57.483965       1 service_loadbalancer.go:444] Found service: {Name:mysql:3306 Ep:[<IP_ADDRESS>:3306] BackendPort:3306 FrontendPort:3306 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.483980       1 service_loadbalancer.go:444] Found service: {Name:newdeploy-master:8080 Ep:[<IP_ADDRESS>:8080] BackendPort:8080 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.483994       1 service_loadbalancer.go:444] Found service: {Name:nginxsvc:18080 Ep:[<IP_ADDRESS>:18080 <IP_ADDRESS>:18080] BackendPort:18080 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.484017       1 service_loadbalancer.go:444] Found service: {Name:nginxsvc:18443 Ep:[<IP_ADDRESS>:18443 <IP_ADDRESS>:18443] BackendPort:18443 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.494184       1 service_loadbalancer.go:302] haproxy -- [WARNING] 347/094057 (46) : config : 'option forwardfor' ignored for frontend 'mysql:3306' as it requires HTTP mode.
[WARNING] 347/094057 (46) : config : 'option forwardfor' ignored for backend 'mysql:3306' as it requires HTTP mode.
I1214 09:40:57.494211       1 service_loadbalancer.go:482] Sync triggered by service default/nginxsvc
I1214 09:40:57.494272       1 service_loadbalancer.go:444] Found service: {Name:elasticsearch:9200 Ep:[<IP_ADDRESS>:9200 <IP_ADDRESS>:9200] BackendPort:9200 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.494297       1 service_loadbalancer.go:444] Found service: {Name:elasticsearch-discovery:9300 Ep:[<IP_ADDRESS>:9300 <IP_ADDRESS>:9300] BackendPort:9300 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.494310       1 service_loadbalancer.go:400] No endpoints found for service kubernetes, port {Name: Protocol:TCP Port:443 TargetPort:{Kind:0 IntVal:443 StrVal:} NodePort:0}
I1214 09:40:57.494326       1 service_loadbalancer.go:444] Found service: {Name:mysql:3306 Ep:[<IP_ADDRESS>:3306] BackendPort:3306 FrontendPort:3306 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.494341       1 service_loadbalancer.go:444] Found service: {Name:newdeploy-master:8080 Ep:[<IP_ADDRESS>:8080] BackendPort:8080 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.494356       1 service_loadbalancer.go:444] Found service: {Name:nginxsvc:18080 Ep:[<IP_ADDRESS>:18080 <IP_ADDRESS>:18080] BackendPort:18080 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.494372       1 service_loadbalancer.go:444] Found service: {Name:nginxsvc:18443 Ep:[<IP_ADDRESS>:18443 <IP_ADDRESS>:18443] BackendPort:18443 FrontendPort:80 Host: Algorithm:roundrobin SessionAffinity:true CookieStickySession:false}
I1214 09:40:57.504112       1 service_loadbalancer.go:302] haproxy -- [WARNING] 347/094057 (52) : config : 'option forwardfor' ignored for frontend 'mysql:3306' as it requires HTTP mode.
[WARNING] 347/094057 (52) : config : 'option forwardfor' ignored for backend 'mysql:3306' as it requires HTTP mode.

 The logs and processes were not always same, sometime it would running well.

@ZhuPeng the output from the log and number of haproxy processes is ok. After that output do you see more reloads? Can you post a picture of the haproxy console (port 1936)?

Haproxy was restarting several times in one second.

That is correct. From the log you see "Sync triggered by" that implies a reload and that means a new process. The old ones should die after a while.

The output logs have no more reloads, I think these are all my service in kubernetes.
This was not the same pods that I mentioned above, but it has the same problem. And when I visit this website, the pid will change randomly.
# pxname,svname,qcur,qmax,scur,smax,slim,stot,bin,bout,dreq,dresp,ereq,econ,eresp,wretr,wredis,status,weight,act,bck,chkfail,chkdown,lastchg,downtime,qlimit,pid,iid,sid,throttle,lbtot,tracked,type,rate,rate_lim,rate_max,check_status,check_code,check_duration,hrsp_1xx,hrsp_2xx,hrsp_3xx,hrsp_4xx,hrsp_5xx,hrsp_other,hanafail,req_rate,req_rate_max,req_tot,cli_abrt,srv_abrt,comp_in,comp_out,comp_byp,comp_rsp,lastsess,last_chk,last_agt,qtime,ctime,rtime,ttime,
default-backend,localhost,0,0,0,0,,0,0,0,,0,,0,0,0,0,no check,1,1,0,,,,,,1,2,1,,0,,2,0,,0,,,,0,0,0,0,0,0,0,,,,0,0,,,,,-1,,,0,0,0,0,
default-backend,BACKEND,0,0,0,0,400,0,0,0,0,0,,0,0,0,0,UP,1,1,0,,0,9373,0,,1,2,0,,0,,1,0,,0,,,,0,0,0,0,0,0,,,,,0,0,0,0,0,0,-1,,,0,0,0,0,
stats,FRONTEND,,,1,2,2000,187,19391,8381193,0,0,0,,,,,OPEN,,,,,,,,,1,3,0,,,,0,1,0,1,,,,0,187,0,0,0,0,,1,1,188,,,0,0,0,0,,,,,,,,
stats,BACKEND,0,0,0,0,200,0,19391,8381193,0,0,,0,0,0,0,UP,0,0,0,,0,9373,0,,1,3,0,,0,,1,0,,0,,,,0,0,0,0,0,0,,,,,0,0,0,0,0,0,0,,,0,0,0,5,
httpfrontend,FRONTEND,,,0,0,2000,0,0,0,0,0,0,,,,,OPEN,,,,,,,,,1,4,0,,,,0,0,0,0,,,,0,0,0,0,0,0,,0,0,0,,,0,0,0,0,,,,,,,,
elasticsearch-discovery:9300,<IP_ADDRESS>:9300,0,0,0,0,,0,0,0,,0,,0,0,0,0,no check,1,1,0,,,,,,1,5,1,,0,,2,0,,0,,,,0,0,0,0,0,0,0,,,,0,0,,,,,-1,,,0,0,0,0,
elasticsearch-discovery:9300,<IP_ADDRESS>:9300,0,0,0,0,,0,0,0,,0,,0,0,0,0,no check,1,1,0,,,,,,1,5,2,,0,,2,0,,0,,,,0,0,0,0,0,0,0,,,,0,0,,,,,-1,,,0,0,0,0,
elasticsearch-discovery:9300,BACKEND,0,0,0,0,200,0,0,0,0,0,,0,0,0,0,UP,2,2,0,,0,9373,0,,1,5,0,,0,,1,0,,0,,,,0,0,0,0,0,0,,,,,0,0,0,0,0,0,-1,,,0,0,0,0,
elasticsearch:9200,<IP_ADDRESS>:9200,0,0,0,0,,0,0,0,,0,,0,0,0,0,no check,1,1,0,,,,,,1,6,1,,0,,2,0,,0,,,,0,0,0,0,0,0,0,,,,0,0,,,,,-1,,,0,0,0,0,
elasticsearch:9200,<IP_ADDRESS>:9200,0,0,0,0,,0,0,0,,0,,0,0,0,0,no check,1,1,0,,,,,,1,6,2,,0,,2,0,,0,,,,0,0,0,0,0,0,0,,,,0,0,,,,,-1,,,0,0,0,0,
elasticsearch:9200,BACKEND,0,0,0,0,200,0,0,0,0,0,,0,0,0,0,UP,2,2,0,,0,9373,0,,1,6,0,,0,,1,0,,0,,,,0,0,0,0,0,0,,,,,0,0,0,0,0,0,-1,,,0,0,0,0,
newdeploy-master:8080,<IP_ADDRESS>:8080,0,0,0,0,,0,0,0,,0,,0,0,0,0,no check,1,1,0,,,,,,1,7,1,,0,,2,0,,0,,,,0,0,0,0,0,0,0,,,,0,0,,,,,-1,,,0,0,0,0,
newdeploy-master:8080,BACKEND,0,0,0,0,200,0,0,0,0,0,,0,0,0,0,UP,1,1,0,,0,9373,0,,1,7,0,,0,,1,0,,0,,,,0,0,0,0,0,0,,,,,0,0,0,0,0,0,-1,,,0,0,0,0,
nginxsvc:18080,<IP_ADDRESS>:18080,0,0,0,0,,0,0,0,,0,,0,0,0,0,no check,1,1,0,,,,,,1,8,1,,0,,2,0,,0,,,,0,0,0,0,0,0,0,,,,0,0,,,,,-1,,,0,0,0,0,
nginxsvc:18080,<IP_ADDRESS>:18080,0,0,0,0,,0,0,0,,0,,0,0,0,0,no check,1,1,0,,,,,,1,8,2,,0,,2,0,,0,,,,0,0,0,0,0,0,0,,,,0,0,,,,,-1,,,0,0,0,0,
nginxsvc:18080,BACKEND,0,0,0,0,200,0,0,0,0,0,,0,0,0,0,UP,2,2,0,,0,9373,0,,1,8,0,,0,,1,0,,0,,,,0,0,0,0,0,0,,,,,0,0,0,0,0,0,-1,,,0,0,0,0,
nginxsvc:18443,<IP_ADDRESS>:18443,0,0,0,0,,0,0,0,,0,,0,0,0,0,no check,1,1,0,,,,,,1,9,1,,0,,2,0,,0,,,,0,0,0,0,0,0,0,,,,0,0,,,,,-1,,,0,0,0,0,
nginxsvc:18443,<IP_ADDRESS>:18443,0,0,0,0,,0,0,0,,0,,0,0,0,0,no check,1,1,0,,,,,,1,9,2,,0,,2,0,,0,,,,0,0,0,0,0,0,0,,,,0,0,,,,,-1,,,0,0,0,0,
nginxsvc:18443,BACKEND,0,0,0,0,200,0,0,0,0,0,,0,0,0,0,UP,2,2,0,,0,9373,0,,1,9,0,,0,,1,0,,0,,,,0,0,0,0,0,0,,,,,0,0,0,0,0,0,-1,,,0,0,0,0,
mysql:3306,FRONTEND,,,0,0,2000,0,0,0,0,0,0,,,,,OPEN,,,,,,,,,1,10,0,,,,0,0,0,0,,,,,,,,,,,0,0,0,,,0,0,0,0,,,,,,,,
mysql:3306,<IP_ADDRESS>:3306,0,0,0,0,,0,0,0,,0,,0,0,0,0,no check,1,1,0,,,,,,1,11,1,,0,,2,0,,0,,,,,,,,,,0,,,,0,0,,,,,-1,,,0,0,0,0,
mysql:3306,BACKEND,0,0,0,0,200,0,0,0,0,0,,0,0,0,0,UP,1,1,0,,0,9373,0,,1,11,0,,0,,1,0,,0,,,,,,,,,,,,,,0,0,0,0,0,0,-1,,,0,0,0,0,

I attach files encounter some error, and the pdf file was email to you.


Skip reordering positional arguments for include_* in RSpec/SortMetadata

fixes #1435
The arguments to include_examples is not regular metadata, it's arguments passed to the shared groups.
We should not reorder positional arguments, and reordering hash arguments can also have side effects, e.g. for .each and keys.first.
See 2.3 of this reference.
It might make sense to still reorder metadata of configuration-level include_context, but I'd rather skip that.

Before submitting the PR make sure the following are checked:

[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[-] Updated documentation.
[x] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
[x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

🤷♂
I don’t have a strong opinion here, as I’m not a heavy metadata user.


Parsing banner from CNXN response

A banner is somewhat like this:
recovery::ro.product.name=meizu_16thPlus_CN;ro.product.model=16th Plus;ro.product.device=16thPlus;features=cmd,stat_v2,shell_v2

reference: system/core/adb/adb.cpp

Thanks :)


#1978 HasDatabaseUpgradeTag

Summary
Adds HasDatabaseUpgradeTag() procedure to make the setters and getters the same.
Work Item(s)
Fixes #1978
Fixes AB#550241

@TKapitan, should we try to reel this one in? Not much pending, the way I see it. Nikola even approved.


Add a ForwardingLogicalPlan to reduce some boiler plate code

Summary of the changes / Why this improves CrateDB
Checklist

[x] User relevant changes are recorded in CHANGES.txt
[x] Touched code is covered by tests
[x] Documentation has been updated if necessary
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

My previous comment was wrong (also the link wasn't working), nothing to improve here, please ignore, sry.


Crash on join

When I taps to sign server crashes with error Internal server error, please fix it

PocketMine-MP 1.14.3

Upload server log


Train a Smooth Normalizing Flow with a score matching loss

Now that we have a prototype of a working C^k coupling layer (by #10), we can try to see if we can build a full flow that can be trained with the score.
This issue is to document our tests and results.

So if I try to get the score with loss=(score_hat - score)^2,  log_bound=4 (meaning that max(a) approx 54) and activation function=sin, I have this :

I think because of the behavior of both the forward/inverse ldj :

So I tried with log_bound=2  (max(a) approx 7)  and min_density_lower_bound=4e-1 ( in order to have smoother forward/inverse ldj)

but it still doesn't work.
So I computed the grad(ildj) and grad(grad ildj)

and the grad(grad ildj) degenerates so the optimization seems to not be possible

hummmmm interesting.... Which bijector is this? the cubic ramp?

yup

x^5

x^7

x^9

not great.... I'm trying out their simple NonCompactAffineSigmoid to see what that does. It doesn't use a ramp at all, just a rescaling of a sigmoid function

You mean this :

?

Humm yeah I think.
It seems to work decently, but our newton method to find the root fails from time to time, and it blows up during training... I'm trying to see what can be done to improve that....

Ok, I've merged my code for this bijector above ^^^^^
Did you get a nicely working configuration?

Yup so I used 3 CL and an exponential decay of the learning rate each 1000 updates.  notebook
Here are the results for 10 000 updates  (I saved the contour plot each 1000 updates to see the evolution) :

loss = nll

loss = score

loss = score + nll

loss = 2*score + nll

loss = score + 2*nll

nice :-D  ok so it looks like this model can be fitted to the target distribution quite well under an NLL. The score kinda works.... but is having a hard time with getting the relative amplitude of the two modes correctly.
In your combination experiment I guess you need to downweight the score loss a lot more, the value of the score loss is probably much larger than that of the NLL, by orders of mag, which means that most likely it dominates the 2 losses during training.
Because the NLL gives you a perfect result in this test, you won't be able to see an improvement with adding the score loss. So, I think you can try the following:

Use a fixed batch of examples (e.g. 128)
Train with NLL alone and observe that it overfits a lot
(optional) Train with score loss alone and see how it looks
Train different models with the NLL as the main loss but gradualy adding a small amount of score loss, and see if it starts improving things.

I had 2 mins so I did a quick try with just 64 data points:

Training with NLL alone:

Training with NLL + score/1000:

\o/


Document flutter run --machine protocol

I'm building support for Flutter apps in Dart Code, but I'm struggling to find much info on the protocol for flutter run --machine. I found this page but it just says "allows the use of JSON commands" without detailing what they are.
I presume it's a subset of the daemon protocol but it would be good to know exactly which subset if so.

This is a @devoncarew question. :)

It's largely the app domain from the protocol, but agree that we should improve the docs here.

@devoncarew Does this mean things like showMessage won't come from flutter run? (not a bad thing; I have no good way to route them to the status bar / toasts!).
Some info on shutting down might be good too (I think when I just killed the process it didn't always close the app on the emulator, though shutting down gracefully is causing me issues too!).

Does this mean things like showMessage won't come from flutter run? (not a bad thing; I have no good way to route them to the status bar / toasts!).

Yup, you won't see that from flutter run --machine.

Some info on shutting down might be good too

Makes sense. For that, app.stop should work, and will terminate the process when finished. Killing the process should work as well - we catch the signal in flutter_tools, and kill the app on the device (the same as doing a ctrl-c on the cli).

I think when I just killed the process it didn't always close the app on the emulator

If you are seeing this, we should open a bug - we do want the app to close on the device/emulator when the flutter_tools process goes away.

I've raised #10556 about not always terminating cleanly.
Another quick question - if wsUri is not provided, what's the correct way to use port? Should I connect to ws://<IP_ADDRESS>:${n.port}/ws?

wsUri should always be provided - we used to only provide port, but switched to passing wsUri as well (which is the better field to pull from)

Ok; the daemon page suggesting I might not get wsUri but if you changed long ago enough that we can assume everyone is newer, I'll just drop the port stuff.

Ah, yeah, I'll update that. There was a few week overlap w/ version skew for this field between clients and flutter_tools, but we're long past that.

(updated)

Another thing worth documenting - which types of messages should be shown to the user? There's a lot of stuff coming back (app.log, app.progress and also non-JSON messages) but it's not clear which are things that are expected to be shown to the user and which are not (I don't want to just spam the output log junk).
I was perviously ignoring all of the non-JSON messages but then noticed that the "No devices connected." message comes through like that, so it I don't send them to the debug output, the user wouldn't know why the app is silently not launching (there appears to be no other output in this case).

makes sense re: updating the docs
For flutter run --machine, app.log messages should be shown as regular stdout, and app.progress messages should be translated into the platform specific progress UI. For vscode, this may mean having a flutter contribution to the status line (like we do for dart analysis)?

@devoncarew I don't know how easily I can route back to the status bar from the debug adapter, but I'll have a dig.
You didn't mention the output that doesn't come wrapped in JSON - there are some strings just written raw to stdout like No devices connected. when trying to run with no devices - should these be filed as bugs and changed to json, or considered the same as app.log?

Things that aren't wrapped in json should just be passed through to the console's stdout.
Which items are you seeing as app.log events? Could you paste a few samples in here?
In terms of the progress display, I think we're just trying to get a good sense of progress to the users, esp. when things might take a while. If it's convenient to map that to an IDEs built-in progress mechanism, so much the better. Otherwise, perhaps just printing <status message>... at start, and <status message> finished. at stop?

(also, definitely very useful to have a 2nd implementor through this area; tells us a lot about what and how to document!)

Which items are you seeing as app.log events?

I dunno, you just said to output them in the console so I was agreeing. I was curious why there would be some sent as JSON (app.log) and some sent raw if they're expected to be handled the same way by integrators (I wondered if the raw output ones were just mistakes writing to output not considering --machine?).

In terms of the progress display, I think we're just trying to get a good sense of progress to the users, esp. when things might take a while. If it's convenient to map that to an IDEs built-in progress mechanism, so much the better.

Yeah, I'd like to put them in the status var if they've been crafted with that in mind. I'm trying to reduce the amount of stuff being spewed into the console output and I guess this stuff (which probably only matters for the short period of time while it's happening) is a good candidate for moving. I've opened https://github.com/Microsoft/vscode/issues/28551 to try and found out how best to get this to the status bar.

(also, definitely very useful to have a 2nd implementor through this area; tells us a lot about what and how to document!)

:-) Is posting issues/ideas here (flutter GH issues) the preferred way to discuss these things?

Works for me. We can use the items here as notes the next time we update the protocol docs.

It'd also be good to have some guidance on what needs to be done after a hot reload - it's not clear what state persists, needs resetting, etc.
For example, based on https://github.com/Dart-Code/Dart-Code/issues/318#issuecomment-310635478 it seems that breakpoints need to be re-sent. However it doesn't seem like Observatory is restarted; so are there other things I need to re-send to Observatory? (I'm actually wondering why I even need to re-send breakpoints - why are they being lost if Observatory is staying alive?)

Based on info I can find (inc https://github.com/flutter/flutter-intellij/issues/273) it seems like only breakpoints will need resending. Can anyone confirm if that's right (eg I don't need to resend setLibraryDebuggable, exception pause modes, etc?)

Yeah, just breakpoints. The script that represents the old version of the library is still around in the VM, with the breakpoints associated with it that you had previously sent. You need to send new breakpoints for the reloaded library(ies), that will resolve against the new scripts for any reloaded libraries.
For IntelliJ, we choose to:

pass in the pause after reload flag
when we get the (newer) paused event (I believe PausePostRequest), we unset all the current breakpoints, reset all the breakpoints, and issue a resume for that isolate

The script that represents the old version of the library is still around in the VM, with the breakpoints associated with it that you had previously sent.

Ah, this makes a little more sense now.
I did try hacking something together earlier but when I tried to send a resume I got back that the isolate wasn't paused. I wasn't handling the new event (I was assuming the response from the hot reload request was good enough) so maybe that's just a timing issue and switching to that event will resolve it.

@devoncarew Is PausePostRequest only used for this? Is it valid for me to always clear/resend all breakpoints then a Resume when that happens (without having to track whether I'd just sent a restart request)? (I ask because the flutter code sending the request and the observatory code are somewhat disconnected)

I added in stuff for re-sending breakpoints; but still hitting same problem. It seems like after the PausePostRequest the isolate is resuming itself (before I do it?!)

[5:32:35 PM]: <== {"jsonrpc":"2.0","method":"streamNotify","params":{"streamId":"Debug","event":{"type":"Event","kind":"PausePostRequest","isolate":{"type":"@Isolate","fixedId":true,"id":"isolates\/467906369","name":"app.flx$main","number":"467906369"},"timestamp":1498235540430}}}
[5:32:35 PM]: ==> {"id":"474","method":"removeBreakpoint","params":{"isolateId":"isolates/467906369","breakpointId":"breakpoints/1"}}
[5:32:35 PM]: ==> {"id":"475","method":"addBreakpointWithScriptUri","params":{"isolateId":"isolates/467906369","scriptUri":"file:///m:/Coding/Applications/flutter/examples/stocks/lib/main.dart","line":65}}
[5:32:35 PM]: ==> {"id":"476","method":"removeBreakpoint","params":{"isolateId":"isolates/467906369","breakpointId":"breakpoints/2"}}
[5:32:35 PM]: ==> {"id":"477","method":"addBreakpointWithScriptUri","params":{"isolateId":"isolates/467906369","scriptUri":"package:stocks/main.dart","line":65}}

################ Why did this happen?
[5:32:35 PM]: <== {"jsonrpc":"2.0","method":"streamNotify","params":{"streamId":"Debug","event":{"type":"Event","kind":"Resume","isolate":{"type":"@Isolate","fixedId":true,"id":"isolates\/467906369","name":"app.flx$main","number":"467906369"},"timestamp":1498235536850}}}

[5:32:35 PM]: <== {"jsonrpc":"2.0","method":"streamNotify","params":{"streamId":"Debug","event":{"type":"Event","kind":"BreakpointRemoved","isolate":{"type":"@Isolate","fixedId":true,"id":"isolates\/467906369","name":"app.flx$main","number":"467906369"},"timestamp":1498235540433,"breakpoint":{"type":"Breakpoint","fixedId":true,"id":"breakpoints\/1","breakpointNumber":1,"resolved":true,"location":{"type":"SourceLocation","script":{"type":"@Script","id":"objects\/154","uri":"file:\/\/\/m:\/Coding\/Applications\/flutter\/examples\/stocks\/lib\/main.dart","_kind":"script"},"tokenPos":350}}}}}
[5:32:35 PM]: <== {"jsonrpc":"2.0", "result":{"type":"Success"},"id":"474"}
[5:32:35 PM]: <== {"jsonrpc":"2.0","method":"streamNotify","params":{"streamId":"Debug","event":{"type":"Event","kind":"BreakpointAdded","isolate":{"type":"@Isolate","fixedId":true,"id":"isolates\/467906369","name":"app.flx$main","number":"467906369"},"timestamp":1498235540440,"breakpoint":{"type":"Breakpoint","fixedId":true,"id":"breakpoints\/3","breakpointNumber":3,"resolved":false,"location":{"type":"UnresolvedSourceLocation","scriptUri":"file:\/\/\/m:\/Coding\/Applications\/flutter\/examples\/stocks\/lib\/main.dart","line":65}}}}}
[5:32:35 PM]: <== {"jsonrpc":"2.0", "result":{"type":"Breakpoint","fixedId":true,"id":"breakpoints\/3","breakpointNumber":3,"resolved":false,"location":{"type":"UnresolvedSourceLocation","scriptUri":"file:\/\/\/m:\/Coding\/Applications\/flutter\/examples\/stocks\/lib\/main.dart","line":65}},"id":"475"}
[5:32:35 PM]: <== {"jsonrpc":"2.0","method":"streamNotify","params":{"streamId":"Debug","event":{"type":"Event","kind":"BreakpointRemoved","isolate":{"type":"@Isolate","fixedId":true,"id":"isolates\/467906369","name":"app.flx$main","number":"467906369"},"timestamp":1498235540441,"breakpoint":{"type":"Breakpoint","fixedId":true,"id":"breakpoints\/2","breakpointNumber":2,"resolved":false,"location":{"type":"UnresolvedSourceLocation","scriptUri":"package:stocks\/main.dart","line":65}}}}}
[5:32:35 PM]: <== {"jsonrpc":"2.0", "result":{"type":"Success"},"id":"476"}
[5:32:35 PM]: <== {"jsonrpc":"2.0","method":"streamNotify","params":{"streamId":"Debug","event":{"type":"Event","kind":"BreakpointAdded","isolate":{"type":"@Isolate","fixedId":true,"id":"isolates\/467906369","name":"app.flx$main","number":"467906369"},"timestamp":1498235540445,"breakpoint":{"type":"Breakpoint","fixedId":true,"id":"breakpoints\/4","breakpointNumber":4,"resolved":false,"location":{"type":"UnresolvedSourceLocation","scriptUri":"package:stocks\/main.dart","line":65}}}}}
[5:32:35 PM]: <== {"jsonrpc":"2.0", "result":{"type":"Breakpoint","fixedId":true,"id":"breakpoints\/4","breakpointNumber":4,"resolved":false,"location":{"type":"UnresolvedSourceLocation","scriptUri":"package:stocks\/main.dart","line":65}},"id":"477"}
[5:32:35 PM]: ==> {"id":"478","method":"resume","params":{"isolateId":"isolates/467906369"}}

The PausePostRequest is only sent when an isolate pauses as a result of a reload (w/ the pause: true param). It is a type of a pause, so I'd very very surprised if the isolate unpauses itself automatically :) Not clear why it's resuming above. There are no other clients connected to the VM?

I don't believe so; but I'll have a dig through to ensure there's no way I could be opening a second connection. I've tried restarting everything and pulling latest Flutter code but that didn't help.

I added logging to the code that connects to observatory and it does seem to only be being done once :(

@devoncarew I can repro the same behaviour in a simple script.. I'll tidy it up and raise an issue.

I've raised #10934 with a script and logged output showing this behaviour (the script is really simple; it just waits for 10 secs after the app restarts and issues a reload, which results in a PausePostRequest immediately followed by a Resume.

@devoncarew Just implementing a command to open the timeline (https://github.com/Dart-Code/Dart-Code/issues/381).. Looks like currently we get {ip}:{port}/ws back as the wsUri from app.debugPort but to open Observatory/Timeline I need to take that off.
Is it safe for me to just check if it ends with /ws and remove that (uri.substring(0, uri.length - 3)) or is there the possibility this format will change in the future? (for ex., would I be better stripping back to the root?)

Oh, and I need to change the protocol from ws to http too. Would it better if the browser-friendly Observatory address was provided to avoid clients having to do parsing?
(For now I'm just implementing it as described above, seems like the chances of it changing are slim).

You should also get back a baseUri field as well. You can use that, and won't have to rely as much in munging the ws: url.

@devoncarew Isn't baseUri different; used for breakpoints on the device?

"baseUri":"file:///Users/danny/Library/Developer/CoreSimulator/Devices/C76BB178-2046-4302-B25B-0A747ECAA276/data/Containers/Data/Application/CCFE1472-7C21-4A5B-B733-022D49ADEEEB/tmp/test_breakpointskIQNRi/test_breakpoints/"

Ah, yeah, absolutely. It's been a while since I was in the code; baseUri should be used for breakpoints, and your best bet for building an observatory url is using wsUri: https://github.com/flutter/flutter-intellij/blob/ebf310549c5282a3db257cac2c16608b9fe7233b/src/io/flutter/run/daemon/FlutterApp.java#L98

@devoncarew Cool, thanks for confirming. Seems like my implementation is pretty much the same as IntelliJ, so should be ok :-)
if (uri.endsWith('/ws')) {
	var browserFriendlyUri = uri.substring(0, uri.length - 3);
	if (browserFriendlyUri.startsWith('ws:'))
		browserFriendlyUri = "http:" + browserFriendlyUri.substring(3);
	this.sendEvent(new Event("dart.observatoryUri", { observatoryUri: browserFriendlyUri.toString() }));
}

I've also updated the note on the flutter run to have a link to the daemon page.


proposal-promise-allSettled

Search Terms
esnext, allSettled, Promise

Suggestion
https://github.com/tc39/proposal-promise-allSettled is Stage 3 now

Checklist
My suggestion meets these guidelines:

[ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[ ] This wouldn't change the runtime behavior of existing JavaScript code
[ ] This could be implemented without emitting different JS based on the types of the expressions
[ ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[ ] This feature would agree with the rest of TypeScript's Design Goals.

Giving this a bump since I intend to add this to the node type definitions.

Also, the description for this issue says Stage 3, but it was moved to Stage 4 roughly 2 months ago (https://github.com/tc39/proposals/blob/master/finished-proposals.md). It should probably be added to es2020, and not esnext.

This is already supported in Node 12.9.0, I think it should be added to TS natively. There's a @types definition for this but I didn't manage to get it to work though...

Why I can try these types in the playground
http://www.typescriptlang.org/play/index.html?target=99&module=5&ts=3.9.0-dev.20200215&ssl=2&ssc=20&pln=2&pc=1#code/MYewdgzgLgBAhjAvDACgJxAWwJYQKYB0cANsQMp5RTF4AmAFANrpa6Fp4QjEBue9ARgCUAXSEBYAFBSgA

The playground has a constant single dts file for all the lib files. This hasn't been updated per version, and I've not got around to an expensive to download but more accurate version yet - you can follow https://github.com/microsoft/TypeScript-Website/issues/82 for updates there


socket.io v4 support ?

https://github.com/socketio/socket.io/releases/tag/4.0.0
Does it work with socket.io-client-cpp ?

Hi! Yes, the v4 only contains a few breaking changes at the API level on the server-side, so the current C++ client is compatible. The compatibility table was updated.
Reference: https://socket.io/docs/v4/migrating-from-3-x-to-4-0/

I confirm :) Thanks for your work and your support


Adds a list of Best Practices for Plugin Authors

Description
This PR adds a list of best practices that should be followed by the plugin developers.
Issues Resolved
https://github.com/opensearch-project/opensearch-plugins/issues/65
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Merged, thanks.


Buildfixes atop the Ventura merge (in #4633)

This picks the Ventura merge commit and buildfixes it for OpenBSD.
Draft pr, so that the commits can be picked back on #4633 -- I don't know off the top of my head if you can get Github to chain prs from someone else.

Closing older PRs with conflicts after our swift-foundation merge (#5001).


Scrollbar cleanups

If the Scaffold's scrollableKey isn't specified just track all scroll notifications. In many simple cases there's just one Scrollable and so the scrollableKey isn't strictly needed.
If a ScrollNotification arrives for a non ExtentScrollBehavior, just ignore it. OverscrollIndicator does this.
Also some gratuitous renames.


Change key

Description
Creates workaround for 'id' key output in recommendations.py for a necessary change to "googleId"
Fixes:
'id' json key name was problematic for web backend

As was mentioned in our Pull Request Review session, PR's should probably be limited to one feature or bug fix. So I think next time, the content based modeling notebook should be in its own PR.

Left an unfinished notebook in repository, presumably from another branch. Closing this pull request and opening another without notebook


ISPN-13777 NullPointerException in JGroupsTransport when metrics are …

…not avaiable
https://issues.redhat.com/browse/ISPN-13777

LGTM

Merged, thanks


Typo Correction

An attempt to resolve issue #1309

OPS Build status updates of commit 1c11a26:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit 1c11a26:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit 1c11a26:
:warning: Validation status: warnings

File
Status
Preview URL
Details

toc.json
:warning:Warning

Details

bread/toc.json
:warning:Warning

Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

docs/best-practices/caching.md
:white_check_mark:Succeeded
View

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\lo30\toc.json'.

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\lo30\bread\toc.json'.

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\lo30\building-blocks\extending-templates\toc.json'.

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

@MikeWasson Can you please review this PR.


[FEATURE]: Migrate from React CRA to NextJs 14 with App Router Typescript

Description
The objective is to migrate our current React application, built with Create React App (CRA), to Next.js 14, utilizing its new App Directory Routing (App Router) and TypeScript. This migration is targeted to take full advantage of Next.js’s latest features like the new routing system, which simplifies pages and layouts handling, and enhances SEO and performance through built-in optimizations. TypeScript will be integrated to enforce type safety, improving the maintainability and robustness of our code.
Steps to Implement

Initialize a New Next.js 14 Project: Set up a new project with Next.js 14 and TypeScript configurations.
Understand and Implement App Router: Explore the capabilities and configuration of the App Router in the app/ directory. Adjust our current routing logic to fit this new model.
Migrate Existing Components: Adapt and migrate existing React components to the new structure, ensuring they comply with TypeScript types and Next.js optimizations.
Update Build & Deployment Configurations: Modify existing build processes and deployment strategies to accommodate Next.js.

Additional Information

Compatibility checks with current dependencies will be performed to ensure smooth integration.
We will monitor the migration's impact on performance and SEO closely.

Have you read the Code of Conduct?
Yes, I have read and agree to adhere to the Code of Conduct.
Would you like to work on this issue?
Yes, I am ready to lead the migration to Next.js 14 with App Router and TypeScript.
Screenshots
No response
Additional information
No response
Do you want to work on this issue?
Yes
Have you read the Code of Conduct?


Issues with some requests

The screenshot is the error information I receive when I attempt to request song from YouTube videos. This started to occur recently

Windows: Open update_deps.bat
Linux: Run python3.5 -m pip install --upgrade -r requirements.txt
Mac: Open update_macdeps.command in Terminal

You can also update ytdl manually using the command sudo pip install -U youtube-dl.


Move to ITRB

Put the runner on prod ITRB asap
We will also want testing and staging ITRB versions soon
The local instance can remain as dev

Workflow runner is currently deployed on ITRB on prod, test, and staging. All three are also registered on SmartAPI.


Unable to Login in IDC APP

I need to  implement TEAM in my Sandbox environment following these steps:
https://aws.amazon.com/pt/blogs/security/temporary-elevated-access-management-with-iam-identity-center/
https://aws-samples.github.io/iam-identity-center-team/docs/deployment/prerequisites.html
To workaround AWS CodeCommit depreciation I've just connect my gitlab to AWS amplify and edited the script to ignore aws codecommit commands.
Let me show my amplify.yaml
version: 1
backend:
  phases:
    build:
      commands:
        - sudo yum install python3-pip.noarch -y
        - pip3 install pipenv
        - python3 -m venv app
        - curl -sL https://rpm.nodesource.com/setup_18.x | bash -
        - sudo yum install -y nodejs
        - export PATH="/bin/python3.9:$PATH"
        - virtualenv app
        - npm i graphql-ttl-transformer<EMAIL_ADDRESS>--prefix /root/.amplify/lib
        - amplifyPush --simple --allow-destructive-graphql-schema-update
frontend:
  phases:
    preBuild:
      commands:
        - npm init -y
        - npm install
        - npm install react-scripts --save && npm ls react-scripts
        - npm ci
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: build
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Now i've the application deployed, AWS application created and integrated with cognito, but i'm not able to login due the error below
Troubleshooting the login we cand find the code are generated and redirect URI working correctly. But the sigin process cannot finalize.

Uncaught (in promise) DOMException: Failed to execute 'replaceState' on 'History': A history state object with URL 'https://main.d11r99we6v7d2t.amplifyapp.com/' cannot be created in a document with origin 'https://main.d3bu0pd1ntvgxt.amplifyapp.com' and URL 'https://main.d3bu0pd1ntvgxt.amplifyapp.com/?code=0c9ce37b-96b8-42d8-958f-de3a0108ce2c'.
    at e.<anonymous> (https://main.d3bu0pd1ntvgxt.amplifyapp.com/static/js/main.6c6ec0a7.js:2:445688)
    at https://main.d3bu0pd1ntvgxt.amplifyapp.com/static/js/main.6c6ec0a7.js:2:285204
    at Object.throw (https://main.d3bu0pd1ntvgxt.amplifyapp.com/static/js/main.6c6ec0a7.js:2:285309)
    at s (https://main.d3bu0pd1ntvgxt.amplifyapp.com/static/js/main.6c6ec0a7.js:2:284098)

below my environment variables
IDC_LOGIN_URL=https://XXXX.awsapps.com/start
REGION=sa-east-1
TEAM_ACCOUNT=Management Account (LAB Purposes)
ORG_MASTER_PROFILE=oraex-root
TEAM_ADMIN_GROUP="TEAM Admins"
TEAM_AUDITOR_GROUP="TEAM Auditors"
TAGS="project=iam-identity-center-team environment=prod"
CLOUDTRAIL_AUDIT_LOGS=read_write

I've checked my Cognito user pool and working fine! but when I click to login in TEAM APP i'm not redirected to application
Anyone can help?

I've solved the problem just adjusting teamplte.yaml to point to my Gitlab.
AWSTemplateFormatVersion: 2010-09-09
Description: CloudFormation Template for Amplify-GitLab Integration

Parameters:
  Login:
    Type: String
    Description: IAM IDC Login URL
  CloudTrailAuditLogs:
    Type: String
    AllowedPattern: (read_write|read|write|none|arn.*)
    Description: Which events should be logged on the TEAM Application Cloudtrail
      Lake EventDataStore.  Acceptable values are "read","write","read_write",
      and "none".  You may also enter the arn of an existing Cloudtrail Lake
      EDS.
    Default: read_write
  teamAdminGroup:
    Type: String
    Description: TEAM application Admin group
  teamAuditGroup:
    Type: String
    Description: TEAM application Auditor group
  tags:
    Type: String
    Description: TEAM application tags
    Default: 'project=iam-identity-center-team environment=prod'
  teamAccount:
    Type: String
    Description: TEAM deployment account ID
  customAmplifyDomain:
    Type: String
    Description: Custom domain for the TEAM application
    Default: ''
  GitLabURL:
    Type: String
    Default:

Conditions:
  IsEmptyCloudTrailAuditLogs: !Equals
    - !Ref CloudTrailAuditLogs
    - ''

Resources:
  TriggerAmplifyBuild:
    Type: Custom::TriggerAmplifyBuild
    Properties:
      ServiceToken: !GetAtt TriggerBuildLambda.Arn
      appId: !GetAtt AmplifyApp.AppId
      branchName: main
      branch: !GetAtt AmplifyBranch.Arn

  AmplifyRole:
    Type: AWS::IAM::Role
    Metadata:
      cfn_nag:
        rules_to_suppress:
          - id: W9
            reason: This is the main Amplify service role.
    Properties:
      AssumeRolePolicyDocument:
        Version: 2012-10-17
        Statement:
          - Effect: Allow
            Principal:
              Service:
                - amplify.amazonaws.com
            Action:
              - sts:AssumeRole
      Path: /
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/AdministratorAccess

  AmplifyApp:
    Type: AWS::Amplify::App
    Properties:
      Name: TEAM-IDC-APP
      Repository: !Ref GitLabURL
      Description: Temporary Elevated Access Management Application
      CustomRules:
        - Source: /<*>
          Status: 404
          Target: /index.html
        - Source: </^[^.]+$|\.(?!(css|gif|ico|jpg|js|png|txt|svg|woff|ttf|map|json)$)([^.]+$)/>
          Status: 200
          Target: /index.html
      EnvironmentVariables:
        - Name: AMPLIFY_DESTRUCTIVE_UPDATES
          Value: true
      OauthToken: "**TOKEN**"
      BuildSpec: |-
        version: 1
        backend:
          phases:
            preBuild:
              commands:
                - '# 12.0.1 Updates auth lambdas to node18'
                - npm i -g<EMAIL_ADDRESS>                - '# Update deployment parameters with helper script'
                - node parameters.js
            build:
              commands:
                - npm i -S graphql-ttl-transformer graphql-ttl-transformer-v2-beta
                - '# Execute Amplify CLI with the helper script'
                - update-alternatives --install /usr/bin/python3 python3 /usr/local/bin/python3.9 11
                - /usr/local/bin/pip3.9 install --user pipenv==2023.6.12
                - amplifyPush --simple --allow-destructive-graphql-schema-update
        frontend:
          phases:
            preBuild:
              commands:
                - npm ci
            build:
              commands:
                - npm run build
          artifacts:
            baseDirectory: build
            files:
              - '**/*'
          cache:
            paths:
              - node_modules/**/*
      Tags:
        - Key: Name
          Value: TEAM
      IAMServiceRole: !GetAtt AmplifyRole.Arn

  AmplifyBranch:
    Type: AWS::Amplify::Branch
    Properties:
      BranchName: main
      AppId: !GetAtt AmplifyApp.AppId
      EnableAutoBuild: true
      EnvironmentVariables:
        - Name: SSO_LOGIN
          Value: !Ref Login
        - Name: TEAM_ACCOUNT
          Value: !Ref teamAccount
        - Name: CLOUDTRAIL_AUDIT_LOGS
          Value: !If
            - IsEmptyCloudTrailAuditLogs
            - read_write
            - !Ref CloudTrailAuditLogs
        - Name: TEAM_ADMIN_GROUP
          Value: !Ref teamAdminGroup
        - Name: TEAM_AUDITOR_GROUP
          Value: !Ref teamAuditGroup
        - Name: TAGS
          Value: !Ref tags
        - Name: AMPLIFY_CUSTOM_DOMAIN
          Value: !Ref customAmplifyDomain
        - Name: _CUSTOM_IMAGE
          Value: amplify:al2
      Tags:
        - Key: Branch
          Value: main

  TriggerBuildLambda:
    Type: AWS::Lambda::Function
    Properties:
      Handler: index.handler
      Runtime: python3.9
      Role: !GetAtt AmplifyLambdaRole.Arn
      Timeout: 120
      Architectures:
        - arm64
      Code:
        ZipFile: |
          import json
          import cfnresponse
          import boto3
          import logging
          from botocore.exceptions import ClientError
          client = boto3.client('amplify')
          logger = logging.getLogger()
          logger.setLevel(logging.INFO)
          def handler(event, context):
              logger.info("Received event: %s" % json.dumps(event))
              appId = event['ResourceProperties']['appId']
              branchName = event['ResourceProperties']['branchName']
              result = cfnresponse.SUCCESS
              try:
                  if event['RequestType'] == 'Create' or event['RequestType'] == 'Update':
                      response = client.start_job(
                          appId = appId,
                          branchName = branchName,
                          jobType='RELEASE'
                      )
                  elif event['RequestType'] == 'Delete':
                      pass
              except ClientError as e:
                  logger.error('Error: %s', e)
                  result = cfnresponse.FAILED
              cfnresponse.send(event, context, result, {})

  AmplifyLambdaRole:
    Type: AWS::IAM::Role
    Properties:
      Path: /
      AssumeRolePolicyDocument:
        Version: 2012-10-17
        Statement:
          - Effect: Allow
            Principal:
              Service: lambda.amazonaws.com
            Action: sts:AssumeRole
      Policies:
        - PolicyName: AmplifyLambdaPolicy
          PolicyDocument:
            Version: 2012-10-17
            Statement:
              - Sid: AllowLogging
                Effect: Allow
                Action:
                  - logs:CreateLogGroup
                  - logs:CreateLogStream
                  - logs:PutLogEvents
                Resource: '*'
              - Sid: startBuild
                Effect: Allow
                Action:
                  - amplify:StartJob
                Resource: '*'

Outputs:
  DefaultDomain:
    Value: !GetAtt AmplifyApp.DefaultDomain

@danilouchoa Are you using public gitlab or privately hosted gitlab for this deployment?

@danilouchoa Are you using public gitlab or privately hosted gitlab for this deployment?

Take a time to read this article.
https://aws.amazon.com/pt/blogs/mobile/deploying-a-web-application-using-aws-amplify-gen-2-with-gitlab-as-the-repository-on-aws/
the steps are basically:

Create Cloud Formation Template pointing to your Gitlab.
Run scripts

https://aws-samples.github.io/iam-identity-center-team/docs/deployment/deployment_process.html
I'm using private repository.

@danilouchoa Are you using public gitlab or privately hosted gitlab for this deployment?

@AliHamzaX
Take a time to read this article.
https://aws.amazon.com/pt/blogs/mobile/deploying-a-web-application-using-aws-amplify-gen-2-with-gitlab-as-the-repository-on-aws/
the steps are basically:

Create Cloud Formation Template pointing to your Gitlab.
Run scripts

https://aws-samples.github.io/iam-identity-center-team/docs/deployment/deployment_process.html
I'm using private repository.

@danilouchoa Are you using public gitlab or privately hosted gitlab for this deployment?

@AliHamzaX
Take a time to read this article.
https://aws.amazon.com/pt/blogs/mobile/deploying-a-web-application-using-aws-amplify-gen-2-with-gitlab-as-the-repository-on-aws/
the steps are basically:

Create Cloud Formation Template pointing to your Gitlab.
Run scripts

https://aws-samples.github.io/iam-identity-center-team/docs/deployment/deployment_process.html
I'm using private repository.

Thank you so much for your help and I will implement it. Appreciated.


[cluster-test] Update naming of --premainnet to --vasp

Motivation
Since arg --premainnet sometimes caused misleading, change it to --vasp, which can enable CT uses public FNs instead of localhost not only on premainnet but also mainnet
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/libra/developers.libra.org, and link to your PR here.)

@snakech should we land this? just requires what looks like a cargo fmt

/land

/land

:broken_heart: Test Failed - commit-workflow

:broken_heart: Test Failed - commit-workflow

/land

/land


maxCacheItems not respected for offline usage on Android

Platform
Flutter Mobile
Obfuscation
Disabled
Debug Info
Enabled
Doctor
[✓] Flutter (Channel stable, 3.13.9, on macOS 14.0 23A344 darwin-arm64, locale
en-AT)
• Flutter version 3.13.9 on channel stable at /Users/user1/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision d211f42860 (4 weeks ago), 2023-10-25 13:42:25 -0700
• Engine revision 0545f8705d
• Dart version 3.1.5
• DevTools version 2.25.0
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at /Users/hgadalrab/Library/Android/sdk
• Platform android-34, build-tools 34.0.0
• Java binary at: /Applications/Android
Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build
17.0.6+0-17.0.6b829.9-10027231)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 15A507
• CocoaPods version 1.14.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2022.3)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build
17.0.6+0-17.0.6b829.9-10027231)
[✓] Connected device (3 available)
• sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64  • Android 14 (API 34) (emulator)
• macOS (desktop)             • macos         • darwin-arm64   • macOS 14.0 23A344 darwin-arm64
• Chrome (web)                • chrome        • web-javascript • Google Chrome 119.0.6045.159
[✓] Network resources
• All expected network resources are available.
• No issues found!
Version
7.13.2
Steps to Reproduce

to be used offline

Future start() async {
await SentryFlutter.init(
(options) {
options
..dsn = dsn
..addIntegration(LoggingIntegration(minEventLevel: Level.FINE));
},
);
Timer.periodic(const Duration(seconds: 3), (timer) {
_logger.fine('new message at ${DateTime.now()}');
});
}
Expected Result
maximum outbox files/events are 30 (default maxCacheItems)
Actual Result
no limit is applied
Are you willing to submit a PR?
None

Hi!
How did you test this?
Does it only happen on Android?

I only tested on iOS. I will try to test the same behaviour on iOS.
To test it, I ran the code mentioned in the "Steps to Reproduce" in the main method. I tested this on an android emulator, and checked the app's cache folder under /data/user/0/com.package.name/cache/sentry/outbox/

just check if this issue still occurs in v8. The way it should work in v8 is it enriches the envelopes itself, and rely on Android just for sending them, while now it saves the envelopes to disk (without checks on maxCacheItems) and rely on Android to enrich them and send them

@stefanosiano Just checked. We are not doing anything with options.maxCacheItems within the Flutter SDK, except passing it down to native. On V8 Android the envelopes are calling the native API directly, and we are not just writing to disk anymore. Logs also indicate that errors/attachments were dropped when trying to reproduce the issue reported by @hgadalrab. So this issue should be resolved in once V8 is released.
D/Sentry  ( 8620): 	"discarded_events": [
D/Sentry  ( 8620): 		{
D/Sentry  ( 8620): 			"reason": "cache_overflow",
D/Sentry  ( 8620): 			"category": "error",
D/Sentry  ( 8620): 			"quantity": 4
D/Sentry  ( 8620): 		},
...

This will be fixed in v8


:jack_o_lantern: Hacktoberfest 2022: More snapshot tests

The purpose of this issue is to not only make this app more well-tested, but introduce you to automated testing, jest, and snapshot tests.

The main package can use more snapshot tests. Check out https://github.com/spenserblack/steamdown/blob/main/CONTRIBUTING.md#updating-steamdown for some docs on how to manage snapshot tests and useful links.

Hey can you elaborate a little more about the issue, I can learn and work on this if you like.

Sure! Basically, right now there is only one Markdown file (basic.md) that gets a snapshot test here: https://github.com/spenserblack/steamdown/blob/60348665d351b9a91bc4c72e6f39b510c0858e3b/packages/steamdown/tests/snapshots.spec.ts#L7-L12
These snapshot tests can be used to guarantee the stability of outputs. As long as the snapshot test passes, you know the output hasn't changed for the input. The snapshots are here. You don't need to worry about creating snapshots -- they will be created automatically for new tests.
Basically, all you need to do is

create a new Markdown file with some useful test scenarios in packages/steamdown/__tests__/input
Register that test file by adding its filename (without the .md extension) on this line


feat: Add a check for an uncommitted Containerfile

This was brought up by @bayou-brogrammer in our discord. With people moving from starting point to BlueBuild, they might have some changes in their Containerfile that they might not want to lose.
Some basic requirements:

If the file is dirty, the CLI should:

allow a force flag to just brute force it
error out and give a message that they should either commit the file or add force flag

Check if the file is in .gitignore, if it is don't bother with the check

We could also have a check for a label or comment in the file that indicates to the tool that it was generated. This way we don't bombard the user with an error everytime and is only used when migrating to BlueBuild from starting point.

Good idea


[ORCA-171] Create container registry credentials for Wave service

In preparation of using Wave, we need to authenticate all requests to container registries. I identified the 4 most commonly used registries: Docker Hub, Quay.io, GHCR, and ECR. The first three have their credentials stored in LastPass, and I manually ported them over to Secrets Manager (documented in CONTRIBUTING.md). The ECR credentials are account-specific, so I authored a CloudFormation stack that creates an IAM user and grants it a minimal set of ECR permissions. I haven't tested whether this works with Wave yet.
It hurts having stacks that are so similar in the various infra-* subfolders, but I don't see any way around it because each account has its own administrator role that needs access to the workflows-infra KMS key.
Edit: I intentionally did not update the Tower configuration script to use these credentials since that should be tackled in a separate PR.

Good question! As a Tower user, the easiest way of allowing Tower to pull private container images is to grant one of these service accounts read-access to the relevant container repositories. This isn't a perfect solution, because as Brad found out, you can't add collaborators on a container repository on Docker Hub if you're not paying a subscription.
Another method is for the user to add their own container registry credentials to the Tower workspace. This is complicated by the fact that users don't have edit-access to Tower workspace credentials. This is intentional because we decided early on that we want to control the Tower workspace from this repository. We could revisit this decision to improve the user experience for using private containers.
None of this is documented because I don't want users to access private containers before we investigate how Wave handles them. Once we are comfortable with that, we can document what I've shared above.


What is the minimal viewconfig?

@pkerpedjiev : Either it should be easy to start the server running from a minimal view config, or we should reference one in the documentation. (Slightly prefer the former, but I think you see it differently, and that's ok.) Particularly if it's in the documentation, it should be as concise as possible. I don't know what values the software can fill in itself, and which will error down the line, but here's what I have right now:
{
  "editable": true,
  "zoomFixed": false,
  "trackSourceServers": [
    "/api/v1"
  ],
  "exportViewUrl": "/api/v1/viewconfs/",
  "views": [
    {
      "uid": "TODO-if-I-remove-this-ui-has-no-controls",
      "initialXDomain": [
        5.960464477539063e-8,
<PHONE_NUMBER>
      ],
      "autocompleteSource": "/api/v1/suggest/?d=OHJakQICQD6gTD7skx4EWA&",
      "genomePositionSearchBoxVisible": true,
      "chromInfoPath": "//s3.amazonaws.com/pkerp/data/hg19/chromSizes.tsv",
      "tracks": {
        "top": [],
        "left": [],
        "center": [],
        "right": [],
        "bottom": []
      },
      "initialYDomain": [
        841428571.4285713,
<PHONE_NUMBER>.571429
      ],
      "layout": {
        "w": 6,
        "h": 12,
        "x": 0,
        "y": 0,
        "i": "aa",
        "moved": false,
        "static": false
      }
    }
  ],
  "zoomLocks": {
    "locksByViewUid": {},
    "locksDict": {}
  },
  "locationLocks": {
    "locksByViewUid": {},
    "locksDict": {}
  }
}

Most glaringly, the UID does not need to correspond to anything on the server, but if it's removed, the UI just won't load.
How much shorter can the whole thing be?

You should be able to take out the layout section. If removing the view uid causes the UI to not load, then that's a glaring bug. It should be auto-assigned if it's not present. The view uids are used to set zoom and location lock (links) between views, so if none are present then the view uid is extraneous.

https://github.com/hms-dbmi/higlass-server/issues/11 asks for validation, and figuring out the minimum is implicit in that. (Not so important if we start with a largely empty tool.)


Surprised by the performance of Triton!

I did a benchmark to check the time cost (us) of cublas and triton on various shapes, I find that triton kernel is faster than cublas on most of the times.
Is that a normal case?  Anyone got the same result? Thank you !
The numbers in the sheet is the time cost (us), not peak computation throughput.

Does cublas do any grid tuning? If not triton probably has an advantage.

Does cublas do any grid tuning? If not triton probably has an advantage.

https://github.com/triton-lang/triton/blob/main/python/tutorials/03-matrix-multiplication.py
This is the script I use to do the benchmark.  I modified it to return time cost instead of the throughput.
Does it use tuning? I think not. But seems most people use cublas this way?

Does cublas do any grid tuning? If not triton probably has an advantage.

I'm curious, does cublas  need tuning? seems it will auto tune to find a best algorithm.

cuBLAS relies on heuristics to find the best kernel based on the input parameters. Heuristics return the best kernels 90+% of the time.
You can autotune on top of this using cublasLtMatmulAlgoGetHeuristic, an example can be found here.
For more information, check out this developer blog.

blog

Thank you!
I read the cublas manual, it seems on SM80 and later GPUs, there is no need to tune gemm?
cublasGemmAlgo_t type is an enumerant to specify the algorithm for matrix-matrix multiplication on GPU architectures up to sm_75. On sm_80 and newer GPU architectures, this enumarant has no effect. cuBLAS has the following algorithm options:

Hi @sleepwalker2017, sorry I dropped the ball on this.
What you're seeing from the manual is cuBLAS shifting efforts to cuBLASLt for power-usage of GEMMs a few year ago. This was for better flexibility and the addition of fusions.
Think of it this why cublasGemmAlgo_t + cublasGemmEx is for sm75 and below; cublasLtMatmulAlgoGetHeuristics is for sm80+.

Hi @sleepwalker2017, sorry I dropped the ball on this.
What you're seeing from the manual is cuBLAS shifting efforts to cuBLASLt for power-usage of GEMMs a few year ago. This was for better flexibility and the addition of fusions.
Think of it this why cublasGemmAlgo_t + cublasGemmEx is for sm75 and below; cublasLtMatmulAlgoGetHeuristics is for sm80+.

Thank you. But most llm inference frameworks invoke cublas directly without tuning. Seems there is big potential improvement here?


Steam interface for ios/andoid?

Hi,
I would like to create an iOS app that allows me to log in steam and do things like idle game hours. Where should I start for basic implmentation?

I can't help you with this.


Correctly handle  bind: Address already in use

Hello!
Thanks for your clean and nice code!
But I've got this error about already running another instance:
Start server
Wait for server shutdown
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  bind: Address already in use
Aborted

From my point of view it's pretty useful thing to handle this case explicitly.

Does Config::reuse_address solve this (server.config.reuse_address=true; before start)? Also have a look at #26, where we discussed this.

When looking closer I saw that reuse_address is true by default. My bad, but could you explain more closely how you would like to handle the exception?

Hello!
I just need some human friendly error in this case instead of program exited by system_thrown.

If I'm not misunderstanding, I would place the server.start() in a try block, and handle the error in its catch block.

Right! That's what I'm looking for. I think it's nice to have all cases handled in your server.

In my opinion, the user of the library should handle such exceptions appropriate to the application. I do not think I will change that, sorry.

So I could agree with your point of view. Otherwise library could be bloated by useless code. Thanks! Will do it in my code.


Add a linter to the project

This'll help keep code clean across the app and remove gotchas for people new to Python.
There's a few different options, though:

Flake8
Pylint
Black

Plus others that I'm not aware about. Thoughts? I've only used flake8, and while it's useful, I don't like it as much as a tool like eslint (the other linter that I've a good amount of experience with).

I hear good things about Black.

Black is a formatter, not a linter. I imagine Prettier is going to be the same.

We also need to add MyPy to utilize typing.

I'mma make that a separate issue.


Add config option for ANSIBLE_COLLECTIONS_PATH

closes #153

Gonna wait a couple days on this one, I'm researching something else that might play a part here.

cool, sure!


TWEAK: Installing build-essential and git

Making things slightly more efficient.

Coverage remained the same at 27.428% when pulling 2f938267f0a8b455ef8861036277036b97f61421 on drwasho:master into 23a2fb56033966d3e46c1cc6b47c643b30da0205 on OpenBazaar:master.


Can't not be use in BL4.0

When I click the Exr Auto Saver button, Render layers and EXR-MultiLayer appear. However, there is no link between them.
EXR-MultiLayer only have one yellow point called Image. No more little yellow point anymore. (Light-diffuse/glossy/transmission checkbox have been click.)

Hi,
I found a fix for this. The "node.width_hidden" was removed from the api of Blender. I modify the script to comment it.
Now it's working but just solved the crash, some part of the api change too like the "Warning: 'Exr_Auto_Pass_Saver_Panel' does not contain 'PT' with prefix and suffix".
Here the file modified for Blender 4.0. I'll pass trought when I will have more time to solve all the problem when I'll have time ;)
Just unistall the previous one, unzip it, and install this python file.
Matt
Exr_auto-pass_saver.zip


New theme: hugo-theme-diary

Theme submission
Please make sure that you have read the theme submission guidelines before submitting a theme. The guidelines provide all relevant information and requirements that have to be fulfilled before the submission. Please tick the relevant boxes for your theme in the checklist below:
Link to my theme repository: https://github.com/AmazingRise/hugo-theme-diary
I made sure that...

[x] the repository contains a good README.md describing my theme
[x] an open source license has been added to LICENSE.md
[x] all metadata have been added to theme.toml
[x] screenshots have been added in the images/ folder with the required dimensions
[x] in case I'm using a customized demo via the exampleSite folder that

[x] https://example.com is set as base url in exampleSite/config.{toml, yaml, json} to avoid the abuse of unused domains
[x] I tested that my theme's demo works with the content directory of gohugoio/HugoBasicExample

[x] I tested my theme against the gohugoio/HugoBasicExample

[x] I've checked the developer tools' console in my browser for error messages

[x] in case my theme is using Hugo Pipes features like toCSS and PostCSS that I have committed the /resources directory with all generated assets, for my theme to work in the basic version of Hugo

N.B. By submitting a theme to the Hugo Themes Showcase you understand that you need to maintain your theme. You will need to keep an eye on whether your theme's demo generates on the Hugo website, whenever there is a new release. We are a very small team and we just cannot keep up opening issues in the various theme repositories to notify authors. Whenever a theme demo breaks and remains broken then at some point it will be removed from the list without prior warning. If you no longer wish to maintain a theme please let us know.
Feel free to ask questions. We're glad to help.

Hello @AmazingRise
Thanks for porting this theme. However as per the theme submission guidelines before adding your theme to this repo you need to do the following:

The thumbnail images/tn.png features part of the theme layout. You need to make it feature the entire viewport while retaining the dimensions 900 x 600 pixels

-Over here you have a comment that contains scripts reference with syntax used in Hexo. Please remove these lines as this syntax is invalid in Hugo.

Over here you reference various scripts from third party CDNs. We discourage the use of external CDNs. You need to include these assets in the theme repo and reference them accordingly.

In the same file as above you load Google Fonts through the proprietary Typekit platform. I do not think that this is proper in an Open Source theme. Please load these fonts through Google Fonts not Typekit (cc: @digitalcraftsman )

You do not provide a layout for section and your theme throws a WARN. Please include the following: disableKinds = ["section"] in exampleSite/config.toml to fix the warning.

You need to generate and commit your theme's resources again as the ones included in the theme repo are out-of-date and therefore the theme demo fails to generate with the basic version of Hugo. Whenever you perform changes you will always need to regenerate and commit the resources directory in the theme repo.

Once you do the above please let me know.

@onedrawingperday
I've fixed all the issues you mentioned above.
Thanks very much for your detailed feedback. ;)

You need to generate and commit your theme's resources again as the ones included in the theme repo are out-of-date and therefore the theme demo fails to generate with the basic version of Hugo. Whenever you perform changes you will always need to regenerate and commit the resources directory in the theme repo.

And as for the last point you mentioned, I found two files are out-of-date.
So I've removed those files in the last commit.
Now the folder resource is with the latest generated files.

Hello @AmazingRise
Thank you for making the changes. No the demo generates fine.
There is only one small detail. As I mentioned above you need to remove this comment that contains Hexo syntax.

Hi, @onedrawingperday
Thanks for the feedback.
Just now I found that the local file was without Hexo comments, so I made the commit again.
Suddenly I realized that your link was reffered to an old commit, in which I hadn't removed the comment.😂 You may be too tired to review the code.
Look at the file in the latest commit.
Thank you for your hard work!
Best wishes.

@AmazingRise
Thanks. I added the theme to the repo in  15c96a3

@digitalcraftsman
This is a port of the Hexo theme  SumiMakito/hexo-theme-Journal
It is a minimal blogging theme.

@AmazingRise I've promoted your theme on Hugo's official Twitter account.

@AmazingRise
Your theme's demo is now broken because you haven't regenerated and commited the resources in the latest update.
Once you do so please let me know.

@onedrawingperday
Hi, thanks for the feedback.
I'm sure the resource file
I moved the resource folder from exampleSite to the root of repository, as you can see here.
I think the issue may be caused by the path. So I moved the two files back.
(resources/_gen/assets/scss/hugo-theme-diary/scss/ → exampleSite/resources/_gen/assets/scss/scss/)
Now the issue may be fixed, at least the generateThemeSite.sh said no errors found. :)


test_default_c4 FIX

So real issue was that @' was required so fift delays proj_data word
resolution till execution phase.
Otherwise if not defined it will fail at interpretation phase even
though it's in separate continuation block.

Gj