Problem with startup trying to do IPv6

So I have run this in a docker on a server and it runs fine, but I am trying to run this in a container runner (cloud foundry)
on docker image latest
I have looked at the scripts and based on the logs IPv6 shouldn't be configured, but then the nginx server gives and IPv6 error,
Is the Docker build file(s) available in version control so I can modify it to just do basic IPv4?

"Is the Docker build file(s) available in version control so I can modify it to just do basic IPv4?"  By this I mean can I get a copy of your build stuff to build my own without the IPV6.  I don't to modify your stuff.  Ie do a git fork over to my own git repository to do some custom modifications for myself.

Running into the same issue as well.

Added this few days ago. openspeedtest/Nginx-Configuration#2 Some people need IPV6, you can edit the Nginx configuration and disable IPV6.

Would be more convenient if there were an ENV variable we could add in compose to indicate if the IPv6 should be enabled / disabled.

@dlhace @RoboMagus Please check this https://github.com/openspeedtest/Docker-Image
Please send a pull request if you can improve this docker image.

Looking at the base image you're using there's already a file that checks at startup for the availability of an IPv6 interface: /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh. However it looks at the default.conf file.
I would propose modifying that script to work on the openspeedtest config file, and the ports it uses.
However I'm currently not able to modify and more importantly, test these proposed changes. Perhaps in a couple of weeks I might be able to open up a PR.

You can modify OpenSpeedTest-Server.conf and mount the file to the container.
to disable ipv6 remove or comment the following lines.
listen [::]:3000;
listen [::]:3001 ssl;

@dlhace @RoboMagus
Image Updated with Fix https://github.com/openspeedtest/Docker-Image/pull/2


Implement basic unit testing

This helps with issue #69
This also adds another dependency, mockito, for the easy creation of mocks,
this helps with the testing, because you don't need to start a bukkit server
This also fixes a bug in the Adfinder that allowed you to bypass the filter when
using uppercase for the url

Thank you very much for this :)
feel free to add more to it :)
I hope to make a fork for it to be able to be used with sponge or as a forge mod :)


Removed deprecated _pegasus_properties

Thanks @dachengx for catching this. This is not used anywhere and the functionality has been fully covered by this.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 91.524%

Totals

Change from base Build<PHONE_NUMBER>3:
0.06%

Covered Lines:
1663

Relevant Lines:
1817

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 91.524%

Totals

Change from base Build<PHONE_NUMBER>3:
0.06%

Covered Lines:
1663

Relevant Lines:
1817

💛  - Coveralls


Doc fixes

The first commit fixes an old warning in the changelog. (Had to temporarly add keep_warnings=True  to conf.py to see where it was coming from)
The second commit fixes the warning about the static path. It may be fixed by adding a .gitkeep in the _static dir, instead or adding a favicon if you prefer.
The last commit was done after a colleague tried to use path.glob to do a recursive globbing. He got confused because he followed the link to the stdlib doc and did not understand why therecursive was not allowed.
We could add a note to explain that because path is compatible with Python2, and just delegates to the glob stdlib, we can't add a recursive argument to the Path.glob() method.
Or maybe we can just keep the note to redirect readers to the walk() methods.
Your call :)

Thanks!


add timeLocked locking type (0x03)

This new Locking Type is an extension to the SingleSignature input lock, in that it still just allows a single signature by the intended receiver, but on top of that it cannot be used as a new input prior to the timestamp defined by the included time-lock.
Feature originally requested by threefoldfoundation/tfchain#57

Made a first attempt as can be seen in 8e3865cbc4227accdb895f55b18ddea9d4db9413.
Is not complete:

no unit tests yet;
no json support yet;

Has its flaws:

how to prevent from getting stack overflows in stacked input locks?

Perhaps too generic for what we need:

what if we just support a static new input lock type,
which simply combines a public key with a time lock?

Perhaps what we need instead is to first resolve #250, so that we than can support a time lock as a stand alone unlock type, which can be used in combination with another input lock (.e.g SingleSignature).

Should be resolved once #259 and #264 are resolved.


Manually bootstrap local nodes graph on fresh sync

Through recent testing, local neutrino nodes have a hard time bootstrapping the network graph at first. Not many peers and unable to find edges.
I suggest we make a connectPeer call to some well known/connected nodes to help get these new nodes off the ground. Only on fresh sync for local wallets, as LND will try to reconnect and keep a connection with previously established peers after a first connection, so no need to do it every single time a user launches the app.
We can use our existing suggested nodes list for the time being that we use for the suggested channels list.

@JimmyMow I created a PR to do this, but in my testing I found that it isn't needed. With latest version of lnd (which we now bundle) the bootstrapping happens automatically as soon as the sync has completed. Within a minute, the node graph already knows about over 150 nodes, and this continues to grow very quickly so it's possible to start creating channels very soon after opening the app already.

Ok cool. I will close this for now then @mrfelton


Finished TODOs in LogoutInputData and LogoutInteractor.

Finished TODOs in LogoutInputData and LogoutInteractor.

LogoutInputData.java:

added a private String instance attribute to hold username, set to argument provided in constructor, and added getter method

LogoutInteractor.java:

added logic in constructor to populate private LogoutUserDataAccessInterface and LogoutOutputBoundary from arguments
added logic in execute() method to set username in DAO to null and prepare successful logout view with the username of logging out user


Feature Request: Enhancing style of scroll bar

Is your feature request related to a problem? Please describe.
The scroll bar doesn't  match the theme of the website
Describe the solution you'd like.
I would like to add customized scroll bar for this website
Additional context (if any)
No response

@TG922 Go ahead 🚀

can i work on this issue?

Since @TG922 seems inactive, you can go ahead and work on this @the-illuminatus 👍

Can I work on it??

@codeboyfriend Go ahead 🚀

Aiit, I'll make a PR soon

@codeboyfriend I'm sorry that this repository is no longer a part of Hacktoberfest.
For Hacktoberfest'22, I've decided to go ahead with a more user-friendly repository for beginners.
Please check out the repository. Here is the link:
https://github.com/varunKT001/awesome-javascript-projects

I'll start working on it right away. Will make a pull request soon
On Sun, Oct 2, 2022, 11:19 AM Varun Tiwari @.***> wrote:

Assigned #62
https://github.com/varunKT001/tomper-wear-ecommerce/issues/62 to
@codeboyfriend https://github.com/codeboyfriend.
—
Reply to this email directly, view it on GitHub
https://github.com/varunKT001/tomper-wear-ecommerce/issues/62#event-7501771645,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUW6ZMN2LDP3MXD7ZBELPFDWBFOSVANCNFSM5UBV2A2Q
.
You are receiving this because you were assigned.Message ID:
@.***
com>


[Feature] Local LLM Support

Would like to be able to run this with local llm stacks like litellm or ollama etc.
Could you provide a parameter to specify llm and base url

I personally use LM Studio for my local LLM server and would love to use it with this as well.
hopefully the dev can use this example python code for future development.
Example: reuse your existing OpenAI setup
from openai import OpenAI
Point to the local server
client = OpenAI(base_url="http://localhost:1234/v1", api_key="not-needed")
completion = client.chat.completions.create(
model="local-model", # this field is currently unused
messages=[
{"role": "system", "content": "Always answer in rhymes."},
{"role": "user", "content": "Introduce yourself."}
],
temperature=0.7,
)
print(completion.choices[0].message)

We're about to add Ollama support to LlamaIndexTS first, see https://github.com/run-llama/LlamaIndexTS/pull/305 - then it could be used in chat-llamaindex

We're about to add Ollama support to LlamaIndexTS first, see run-llama/LlamaIndexTS#305 - then it could be used in chat-llamaindex

Some things are missing fo the class Ollama to fit into the current implementation, at least the maxTokens metadata entry and the tokens() method.

We're about to add Ollama support to LlamaIndexTS first, see run-llama/LlamaIndexTS#305 - then it could be used in chat-llamaindex

Some things are missing for the class Ollama to fit into the current implementation, at least the maxTokens metadata entry and the tokens() method.

I've tried to make it work, unsuccessfully, with LiteLLM by setting export OPENAI_BASE_URL=https://ollama.mydomain.tld/v1 and changing
diff --git app/client/platforms/llm.ts app/client/platforms/llm.ts
index ddc316f..d7be7c8 100644
--- app/client/platforms/llm.ts
+++ app/client/platforms/llm.ts
@@ -31,11 +31,9 @@ export interface ResponseMessage {
 }

 export const ALL_MODELS = [
-  "gpt-4",
-  "gpt-4-1106-preview",
-  "gpt-4-vision-preview",
-  "gpt-3.5-turbo",
-  "gpt-3.5-turbo-16k",
+  "mixtral",
+  "mistral",
+  "phi",
 ] as const;

And then creating a new bot using one of those models, but that didn't work. Before, when using gpt models but with the env set, it reached LiteLLM. But then with other models there's a 500 in /api/llm (of chat-llamaindex).
Any clues? Or other ways to make it work.,

I've managed to make it work, with LiteLLM (and Ollama behind it) by setting export OPENAI_BASE_URL=https://litellm.mydomain.tld/v1 and changing
diff --git app/client/platforms/llm.ts app/client/platforms/llm.ts
index ddc316f..a907ee7 100644
--- app/client/platforms/llm.ts
+++ app/client/platforms/llm.ts
@@ -36,6 +36,9 @@ export const ALL_MODELS = [
   "gpt-4-vision-preview",
   "gpt-3.5-turbo",
   "gpt-3.5-turbo-16k",
+  "mixtral_default",
+  "mistral",
+  "phi",
 ] as const;

 export type ModelType = (typeof ALL_MODELS)[number];

And then creating a new bot using one of those models, and adjusting its params.

@m0wer thanks! cool hack! Yes Ollama currently doesn't have tokens() implemented, that's why SummaryChatHistory is not working with it. But SimpleChatHistory should.
You can try setting sendMemory to false for your bot, see:
https://github.com/run-llama/chat-llamaindex/blob/aeee808134a9b267d22d3d48900ba7393e37cdbc/app/api/llm/route.ts#L167C1-L169

llamaindexTS there is a list of valid OpenAI model names so the type check fails.
This example doesn't work with mixtral? https://github.com/run-llama/LlamaIndexTS/blob/main/examples/ollama.ts
Should work as it's using model: string

llamaindexTS there is a list of valid OpenAI model names so the type check fails.
This example doesn't work with mixtral? https://github.com/run-llama/LlamaIndexTS/blob/main/examples/ollama.ts
Should work as it's using model: string

Yes that works. But what I'm trying to do is to get the complete https://chat.llamaindex.ai/ to work with local LLMs. So either I fake the OpenAI API with litellm or I extend the class Ollama from LlamaIndexTS to support the missing methods.

To make it work with Ollama I had to adapt my reverse proxy settings and do the following changes:
diff --git app/api/llm/route.ts app/api/llm/route.ts
index aa3066c..de9a806 100644
--- app/api/llm/route.ts
+++ app/api/llm/route.ts
@@ -4,7 +4,8 @@ import {
   DefaultContextGenerator,
   HistoryChatEngine,
   IndexDict,
-  OpenAI,
+  LLMMetadata,
+  Ollama,
   ServiceContext,
   SimpleChatHistory,
   SummaryChatHistory,
@@ -120,6 +121,33 @@ function createReadableStream(
   return responseStream.readable;
 }

+class OllamaCustom extends Ollama {
+    maxTokens: number;
+
+  constructor(init: Partial<OllamaCustom> & {
+    model: string;
+  }) {
+    super(init);
+    this.maxTokens = init.maxTokens || 2048;
+  }
+
+  get metadata(): LLMMetadata {
+    return {
+      model: this.model,
+      temperature: this.temperature,
+      topP: this.topP,
+      maxTokens: this.maxTokens,
+      contextWindow: this.contextWindow,
+      tokenizer: undefined,
+    };
+  }
+
+  tokens(messages: ChatMessage[]): number {
+    let tokens = 10;
+    return tokens;
+  }
+}
+
 export async function POST(request: NextRequest) {
   try {
     const body = await request.json();
@@ -146,11 +174,14 @@ export async function POST(request: NextRequest) {
       );
     }

-    const llm = new OpenAI({
+    const llm = new OllamaCustom({
+      baseURL: "https://ollama.mydomain.tld",
       model: config.model,
       temperature: config.temperature,
       topP: config.topP,
+      contextWindow: config.maxTokens,
       maxTokens: config.maxTokens,
+      requestTimeout: 5 * 60 * 1000,
     });

     const serviceContext = serviceContextFromDefaults({
diff --git app/client/platforms/llm.ts app/client/platforms/llm.ts
index ddc316f..33273c9 100644
--- app/client/platforms/llm.ts
+++ app/client/platforms/llm.ts
@@ -31,11 +31,11 @@ export interface ResponseMessage {
 }

 export const ALL_MODELS = [
-  "gpt-4",
-  "gpt-4-1106-preview",
-  "gpt-4-vision-preview",
-  "gpt-3.5-turbo",
-  "gpt-3.5-turbo-16k",
+  "mistral",
+  "mixtral_default",
+  "dolphin-mixtral:8x7b-v2.7-q4_K_M",
+  "llava",
+  "phi",
 ] as const;

 export type ModelType = (typeof ALL_MODELS)[number];
diff --git package.json package.json
index 0ba2c1b..b6dfdfb 100644
--- package.json
+++ package.json
@@ -38,7 +38,7 @@
     "dotenv": "^16.3.1",
     "emoji-picker-react": "^4.4.12",
     "encoding": "^0.1.13",
-    "llamaindex": "0.0.0-20231110031459",
+    "llamaindex": "0.0.44",
     "lucide-react": "^0.277.0",
     "mermaid": "^10.3.1",
     "nanoid": "^5.0.2",

see https://github.com/run-llama/chat-llamaindex/pull/77 for how to use a Ollama


How is the Hostname of the root service in TrafficSplit going to be resolvable?

Consider the following example.
apiVersion: split.smi-spec.io/v1alpha3
kind: TrafficSplit
metadata:
  name: canary
spec:
  service: website.com
  backends:
  - service: website-v1
    weight: 90
  - service: website-v2
    weight: 10

When a service in K8s curls http://website.com, since website.com is just a hostname for a root service that K8s is not aware of, how would this be resolvable? Are users expected to configure DNS for the domain website.com here?

The service must be a service in the same namespace. website.com is not valid as it is not a k8s resource.

The service must be a service in the same namespace. website.com is not valid as it is not a k8s resource.

Thanks for clarifying, I was wondering if the spec allows for creating aliases to service.

Would you mind explaining your use case a little bit more? Doing a traffic split from website.com to two internal services doesn't seem like something anyone would want to do?

Would you mind explaining your use case a little bit more? Doing a traffic split from website.com to two internal services doesn't seem like something anyone would want to do?

I've read about a few use cases where users of Istio have tried to use the hosts in VirtualService as an alias for actual K8s services, so was wondering how it fits here.
I am still a bit confused, consider the following example where website is a k8s service running in the namespace website-ns. Given the following traffic split, how would a service foo running in the namespace foo-ns do a traffic split for website? For website to be resolvable via DNS, the FQDN must be such that the queries from foo to website are resolvable. Would this mean the service foo be aware of the namespace website belongs to for the domain in the HTTP request to resolve to a valid IP?

I'm still super confused. website has an FQDN of website.website-ns.svc.cluster.local. That is resolvable via. DNS because it is exported by default either with kube-dns or coredns.
If you're talking about public DNS, let's say website.com, you would write an Ingress resource. This would contain the mapping from website.com to website. The ingress controller would then look up the endpoints to website in the website-ns namespace and forward the request there. Notice that no DNS lookups actually happened inside the ingress controller. If the ingress controller implemented TrafficSplit, it would then lookup the leaf services, fetch the endpoints for those and do load balancing. If a service mesh was on the outbound side of the ingress controller, it would do something basically the same.

I am not referring to an external endpoint, but in-cluster. Was just wondering whether there is a way for apps to not care about the namespace of destination services, website in this example by using an alias. If the user decides to change the namespace for the website service, a service foo making HTTP requests to website would need to be aware of its namespace to use an FQDN that is resolvable as website.website-ns.svc.cluster.local.

Yes, that is a limitation of k8s.

Yes, that is a limitation of k8s.

So much for decoupling app logic from networking :-)

@grampelberg , one clarification - do the backends in a split have to be a k8s service or can they just be deployments with selector app=<root-service> ?

Backends must be service resources as well.

Backends must be service resources as well.

In that case, even though a client of the website service is making requests to http://website.website-ns.svc.cluster.local, when a split with a different backend service is applied, for ex website-v2 as the backend for apex website, the client would still continue using the root service FQDN in HTTP requests but the service mesh implementation should use the website-v2 backend to redirect traffic.
In other words, the clients always use the FQDN of the root service, and the service mesh implementation needs to split traffic to the correct backend. So the IP in the request packet originating from the client might not correspond to the actual backend defined by the Split, but just used to resolve to a service IP, after which the service mesh implementation does the magic. Is this correct?

That is correct.

We should document this for clarity. Thanks @grampelberg for clarifying.

@grampelberg , I think spec.service should just be an FQDN that is resolvable within the cluster.

@shashankram I am very strongly against that. At the bare minimum it would need to be named something different (fqdn maybe). How do the endpoints get updated? Where does the implementation fetch data from?

I don't think the service mesh implementation should worry about the FQDN at all. The service mesh implementation would fetch the endpoints for a top level service from its backends. Making the top level service an FQDN would be clear and avoid weird use cases where a leaf and top level service are the same, which could imply recursion.
We should rename spec.service to spec.host, and let the users worry about how that is resolvable - whether they want to create a top level service just for resolving to an IP the service mesh implementation doesn't use, or bring their own DNS for it.

@grampelberg could you reopen this issue while this is still in discussion. I can't seem to reopen it.

I don't think the service mesh implementation should worry about the FQDN at all.

Yup, this is why I'm uninterested in doing this. If you'd like to make this proposal, please open a separate issue or PR. I'd like to know what problem you're solving as I have a long list of reasons why spec.host is a bad idea in absence of problems being solve.

Consider the following split
apiVersion: split.smi-spec.io/v1alpha3
kind: TrafficSplit
metadata:
  name: canary
  namespace: website-ns
spec:
  service: website
  backends:
  - service: website-v1
    weight: 90
  - service: website-v2
    weight: 10

The assumption here is that website is a k8s service. The problem with this assumption is that clients have to hardcode a service name, that might no longer be even relevant. In this example, spec.service could be anything, it could even be website-1, and website-1 could be versioned out with clients still referencing it, which is misleading. Moreover clients in different namespaces would need to access the website service using their FQDN website.website-ns. So just referencing the service name for spec.service is not enough. Clearly spec.service needs to be FQDN here.

Clients have to hardcode FQDNs though, what's the benefit?

Clients have to hardcode FQDNs though, what's the benefit?
In your example, you'd just create a new traffic split (which you would have to do whether you're using FQDNs or not).
The downside to using FQDNs is that they must match. Some questions that come from that:

What happens if someone's using a non-standard DNS name for their cluster (foo.local)?
How do you choose between someone's client saying website vs website.default vs website.default.svc.foo.local? All three would need new traffic splits to support each, and would fail in transparent ways to the users.

This would be true even if the clients are in a different namespace than website.

A client in foo namespace  trying to access website in website-ns namespace would need to access it using FQDN website.website-ns.
A client in website-ns namespace would access website using FQDN website
A client in a different cluster would need to access website using website.website-ns.svc.<cluster>

So depending on the location of the client, different splits would be required. If spec.service is FQDN of the form service.namespace.cluster.domain, all clients can use the same FQDN.

How does the implementation discover what it should be load balancing?

The implementation would do load balancing based on the backends specified for the top level FQDN. The backend are services with endpoints.

How does validation happen?

No validation is required for the FQDN. It should be the user's responsibility to ensure the FQDN is resolvable by the client. One important thing to note here is that the FQDN would resolve to some IP, doesn't matter what, its the backends for the FQDN that the traffic would be routed too. This
is still the case with spec.service being a service, as noted in our discussion above.

How is policy implemented? Would it be possible to have an attacker send traffic transparently?

Could you explain the scenario more in detail?

I'll reiterate, I'd really love to know what the problem is that you're trying to solve. I suspect that there's a creative way we can get a solution to that without opening pandora's box for TrafficSplit implementations and use cases.

I'm super confused. Maybe we could get on a call some time and chat through it? Might be a great topic to bring up during the next community call!

Sorry @grampelberg for not clearing this up.
Let's take one question at a time. What are your confusions?

It just feels like there's some misunderstandings that'll require a higher bandwidth conversation is all. I basically have a ton of questions and so far I'm just getting more confused =( I'm in slack if you're interested, though next week would probably work better for me.

Let's chat over slack next week!


Allow the customer to optionally set the created_at field . Improve datastore tests.

Pull request check list

[X] Proper tests/regressions included?
[ ] Documentation updated?

Affected functionality
Allowing the customer to optionally set the created_at field while using now() as the default value when not provided, providing flexibility for specific use cases where the customer wants to control the creation timestamp. This can be also useful for testing.
On the other hand, the Datastore layer continues not allowing the customer to set the updated_at field which aligns with the typical practice of using the current timestamp as the indicator of when a record was last modified. This ensures the integrity of the auditing process, as it prevents tampering with the timestamp for auditing purposes.
Description of change
Enabled setting the created_at field when inserting a new entity (TrustDomain, Relationship, JoinToken, Bundle).
Improved the Datastore tests to enhance consistency, streamline Datastore instance cleanup, and make various minor improvements.
Which issue this pull requests fixes

The changes are OK, but I don't understand the real necessity of allowing the user to control the created_at. Can you explore more this use case? Also, do you think we need to create some validations regarding the timestamp? Such as the time cannot be in the future?

The most obvious use-case for me and the reason I'm adding this flexibility is for testing purposes. For example, you added a test that creates a TrustDomain setting the created_at expecting that it would be stored in the DB with the time you set:
td := &entity.TrustDomain{
              Name:      spiffeid.RequireTrustDomainFromString(tdName),
              CreatedAt: time.Now().Add(time.Duration(i+1) * time.Minute),
	}
td = createTrustDomain(ctx, t, ds, td)

Well, currently this is not happening, it is always set as the default now(), which feels kind of surprising.
In general the business layer won't deal with the created_at and just pass empty, and the Datastore layer will set it as the default which is now(). On the other hand, for testing purposes, I want to set it as anything I want, even in the future, like you were trying in your code.


Docs.MS Release Updates for azure_communication_sms

Update docs metadata and targeting for release of azure_communication_sms

Docs Build status updates of commit c6d6b3d:
:clock10: Full build: the average full build time is 179 min(s) 49 sec(s), this is based on the last 576 build(s) for this repository.

Docs Build status updates of commit c6d6b3d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/communication-sms-readme-pre.md
:warning:Warning
View (azure-python) View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.call_http.yml
:warning:Warning
View (azure-python-preview)
Details

ci-configs/packages-preview.json
:white_check_mark:Succeeded

docs-ref-services/communication-sms-readme-pre.md

Line 13: [Warning-h1-not-first] Markdown content is not allowed before {0}.
Line 13: [Warning-h1-not-first] Markdown content is not allowed before {0}.
Line 21: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 21: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 37: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 37: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 42: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 42: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 74: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 74: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 78: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 78: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 82: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 82: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.call_http.yml

[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.call_http) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.yml.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a431815:
:clock10: Full build: the average full build time is 180 min(s) 5 sec(s), this is based on the last 581 build(s) for this repository.

Docs Build status updates of commit a431815:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/communication-sms-readme-pre.md
:warning:Warning
View (azure-python) View (azure-python-preview)
Details

docs-ref-services/mgmt-communication-readme-pre.md
:warning:Warning
View (azure-python) View (azure-python-preview)
Details

docs-ref-services/communication-chat-readme-pre.md
:warning:Warning
View (azure-python) View (azure-python-preview)
Details

docs-ref-services/communication-administration-readme-pre.md
:warning:Warning
View (azure-python) View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.task_any.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.task_all.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.new_uuid.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.continue_as_new.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.call_http.yml
:warning:Warning
View (azure-python-preview)
Details

ci-configs/packages-preview.json
:white_check_mark:Succeeded

docs-ref-services/communication-sms-readme-pre.md

Line 13: [Warning-h1-not-first] Markdown content is not allowed before {0}.
Line 13: [Warning-h1-not-first] Markdown content is not allowed before {0}.
Line 21: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 21: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 37: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 37: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 42: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 42: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 74: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 74: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 78: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 78: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 82: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 82: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.

docs-ref-services/mgmt-communication-readme-pre.md

Line 21: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 21: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 27: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 27: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.

docs-ref-services/communication-chat-readme-pre.md

Line 13: [Warning-h1-not-first] Markdown content is not allowed before {0}.
Line 13: [Warning-h1-not-first] Markdown content is not allowed before {0}.
Line 22: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 22: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 85: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 85: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 141: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 141: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 398: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 398: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 402: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 402: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 406: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 406: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.

docs-ref-services/communication-administration-readme-pre.md

Line 13: [Warning-h1-not-first] Markdown content is not allowed before {0}.
Line 13: [Warning-h1-not-first] Markdown content is not allowed before {0}.
Line 21: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 21: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 33: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 33: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 41: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 41: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 48: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 48: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 50: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 50: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 52: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 52: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.task_any.yml

[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.task_any) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.yml.

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.task_all.yml

[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.task_all) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.yml.

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.new_uuid.yml

[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.new_uuid) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.yml.

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.continue_as_new.yml

[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.continue_as_new) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.yml.

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.call_http.yml

[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.call_http) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.yml.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


ANN: Upcoming API changes for 0.4.0 re: registerPanel

So, I've realized the Panels are kind of registered wrong.
Right now, you register a component and that one is what you toggle on/off. It can be whatever in reality, and if you pass in something like a empty div with text as a child and no styling, it'll inject just that, "breaking" the game UI
Instead, the registerPanel API will change to accept:

Maybe a title (or maybe it'll take the title from the ID)
Definitely the contents of a panel
Maybe additional styling for the panel

So instead of passing in a panel, HookUI will create the panel and you'll pass in the contents of the panel
This issue will also contain potentially other API changes that will happen for 0.4.0, but not sure exactly if there will be more for now.

Seems like I'll get to this today.
The good news is that you'll be able to continue to use your existing code for 0.4.0 without having to change anything, so mod authors don't have to stress about people updating to 0.4.0 while the players do so.
Then probably for 0.5.0 it'll be incompatible by then, but hopefully this should be making the whole process a lot easier for both players and mod authors :)


Icarus Adventure System - Freude schöner Götterfunken

Sheet
Name: Freude schöner Götterfunken
System: Icarus Adventure System
Changes / Comments
Added an option to change the style to high contrast.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[yes ] Does the pull request title have the sheet name(s)? Include each sheet name.
[no] Is this a bug fix?
[no] Does this add functional enhancements (new features or extending existing features) ?
[yes] Does this add or change functional aesthetics (such as layout or color scheme) ?

Character Sheet Info Roll20 Internal Use only.


Crashes when enabled HTTP/2 priority

Set  proxy.config.http2.stream_priority_enabled to enable HTTP/2 priority processing.  Within an hour we had two core files.
(gdb) bt
#0  0x00002aea8ec411d7 in raise () from /lib64/libc.so.6
#1  0x00002aea8ec428c8 in abort () from /lib64/libc.so.6
#2  0x00002aea8c15e277 in ink_abort (message_format=0x2aea8c186fe0 "%s:%d: failed assertion `%s`") at ../../../../trafficserver/lib/ts/ink_error.cc:99
#3  0x00002aea8c15b3c7 in _ink_assert (expression=0x852f77 "node->parent != nullptr", file=0x852e60 "../../../../trafficserver/proxy/http2/Http2DependencyTree.h", line=319)
    at ../../../../trafficserver/lib/ts/ink_assert.cc:37
#4  0x00000000006abd99 in Http2DependencyTree::Tree<Http2Stream*>::_change_parent (this=0x2aeaa9c96fb0, node=0x2aeaa940cf00, new_parent=0x2aeaaa4f8370, exclusive=false)
    at ../../../../trafficserver/proxy/http2/Http2DependencyTree.h:319
#5  0x00000000006ab42e in Http2DependencyTree::Tree<Http2Stream*>::reprioritize (this=0x2aeaa9c96fb0, node=0x2aeaaac35780, new_parent_id=0, exclusive=true)
    at ../../../../trafficserver/proxy/http2/Http2DependencyTree.h:305
#6  0x00000000006a3d2d in rcv_priority_frame (cstate=..., frame=...) at ../../../../trafficserver/proxy/http2/Http2ConnectionState.cc:423
#7  0x00000000006a615f in Http2ConnectionState::main_event_handler (this=0x2aeed40e5080, event=2253, edata=0x2aea968b4910) at ../../../../trafficserver/proxy/http2/Http2ConnectionState.cc:927
#8  0x0000000000551968 in Continuation::handleEvent (this=0x2aeed40e5080, event=2253, data=0x2aea968b4910)
    at /var/builds/workspace/157188-v3-component/BUILD_CONTAINER/rhel7-gcc6_2/label/DOCKER-HIGH/app_root/_build/ats_build/../../trafficserver/iocore/eventsystem/I_Continuation.h:153
#9  0x000000000069e6a1 in send_connection_event (cont=0x2aeed40e5080, event=2253, edata=0x2aea968b4910) at ../../../../trafficserver/proxy/http2/Http2ClientSession.cc:58
#10 0x00000000006a0b09 in Http2ClientSession::do_complete_frame_read (this=0x2aeed40e4de0) at ../../../../trafficserver/proxy/http2/Http2ClientSession.cc:494
#11 0x00000000006a0cf9 in Http2ClientSession::state_process_frame_read (this=0x2aeed40e4de0, event=100, vio=0x2aedfc23fdf0, inside_frame=false)
    at ../../../../trafficserver/proxy/http2/Http2ClientSession.cc:531
#12 0x00000000006a02be in Http2ClientSession::state_start_frame_read (this=0x2aeed40e4de0, event=100, edata=0x2aedfc23fdf0) at ../../../../trafficserver/proxy/http2/Http2ClientSession.cc:424
#13 0x000000000069fa1e in Http2ClientSession::main_event_handler (this=0x2aeed40e4de0, event=100, edata=0x2aedfc23fdf0) at ../../../../trafficserver/proxy/http2/Http2ClientSession.cc:324
#14 0x0000000000551968 in Continuation::handleEvent (this=0x2aeed40e4de0, event=100, data=0x2aedfc23fdf0)
    at /var/builds/workspace/157188-v3-component/BUILD_CONTAINER/rhel7-gcc6_2/label/DOCKER-HIGH/app_root/_build/ats_build/../../trafficserver/iocore/eventsystem/I_Continuation.h:153
#15 0x00000000007e84b6 in read_signal_and_update (event=100, vc=0x2aedfc23fca0) at ../../../../trafficserver/iocore/net/UnixNetVConnection.cc:144
#16 0x00000000007eb4ec in UnixNetVConnection::readSignalAndUpdate (this=0x2aedfc23fca0, event=100) at ../../../../trafficserver/iocore/net/UnixNetVConnection.cc:1095
#17 0x00000000007c2aea in SSLNetVConnection::net_read_io (this=0x2aedfc23fca0, nh=0x2aea94644cf0, lthread=0x2aea94641010) at ../../../../trafficserver/iocore/net/SSLNetVConnection.cc:607
#18 0x00000000007dfdfd in NetHandler::waitForActivity (this=0x2aea94644cf0, timeout=39999854) at ../../../../trafficserver/iocore/net/UnixNet.cc:497
#19 0x000000000080d670 in EThread::execute_regular (this=0x2aea94641010) at ../../../../trafficserver/iocore/eventsystem/UnixEThread.cc:272
#20 0x000000000080d837 in EThread::execute (this=0x2aea94641010) at ../../../../trafficserver/iocore/eventsystem/UnixEThread.cc:325
#21 0x000000000080c46c in spawn_thread_internal (a=0x1f36db0) at ../../../../trafficserver/iocore/eventsystem/Thread.cc:85
#22 0x00002aea8dfd4dc5 in start_thread () from /lib64/libpthread.so.0
#23 0x00002aea8ed0376d in clone () from /lib64/libc.so.6

and
(gdb) bt
#0  0x00002b4ada5d61d7 in raise () from /lib64/libc.so.6
#1  0x00002b4ada5d78c8 in abort () from /lib64/libc.so.6
#2  0x00002b4ad7af3277 in ink_abort (message_format=0x2b4ad7b1bfe0 "%s:%d: failed assertion `%s`") at ../../../../trafficserver/lib/ts/ink_error.cc:99
#3  0x00002b4ad7af03c7 in _ink_assert (expression=0x852f4e "entry->index < _v.length()",
    file=0x852eb0 "/var/builds/workspace/157188-v3-component/BUILD_CONTAINER/rhel7-gcc6_2/label/DOCKER-HIGH/app_root/_build/ats_build/../../trafficserver/lib/ts/PriorityQueue.h", line=142)
    at ../../../../trafficserver/lib/ts/ink_assert.cc:37
#4  0x00000000006abbb6 in PriorityQueue<Http2DependencyTree::Node*, PriorityQueueLess<Http2DependencyTree::Node*> >::erase (this=0x2b5278167c60, entry=0x2b552f7ba3c0)
    at /var/builds/workspace/157188-v3-component/BUILD_CONTAINER/rhel7-gcc6_2/label/DOCKER-HIGH/app_root/_build/ats_build/../../trafficserver/lib/ts/PriorityQueue.h:142
#5  0x00000000006ab659 in Http2DependencyTree::Tree<Http2Stream*>::deactivate (this=0x2b4b4d432ac0, node=0x2b4b4e0a8be0, sent=0)
    at ../../../../trafficserver/proxy/http2/Http2DependencyTree.h:405
#6  0x00000000006a6feb in Http2ConnectionState::delete_stream (this=0x2b568b05b9a0, stream=0x2b527ac33ac0) at ../../../../trafficserver/proxy/http2/Http2ConnectionState.cc:1163
#7  0x00000000006a4272 in rcv_rst_stream_frame (cstate=..., frame=...) at ../../../../trafficserver/proxy/http2/Http2ConnectionState.cc:490
#8  0x00000000006a615f in Http2ConnectionState::main_event_handler (this=0x2b568b05b9a0, event=2253, edata=0x2b4b383a4910) at ../../../../trafficserver/proxy/http2/Http2ConnectionState.cc:927
#9  0x0000000000551968 in Continuation::handleEvent (this=0x2b568b05b9a0, event=2253, data=0x2b4b383a4910)
    at /var/builds/workspace/157188-v3-component/BUILD_CONTAINER/rhel7-gcc6_2/label/DOCKER-HIGH/app_root/_build/ats_build/../../trafficserver/iocore/eventsystem/I_Continuation.h:153
#10 0x000000000069e6a1 in send_connection_event (cont=0x2b568b05b9a0, event=2253, edata=0x2b4b383a4910) at ../../../../trafficserver/proxy/http2/Http2ClientSession.cc:58
#11 0x00000000006a0b09 in Http2ClientSession::do_complete_frame_read (this=0x2b568b05b700) at ../../../../trafficserver/proxy/http2/Http2ClientSession.cc:494
#12 0x00000000006a0cf9 in Http2ClientSession::state_process_frame_read (this=0x2b568b05b700, event=100, vio=0x2b4e42ddcb30, inside_frame=false)
    at ../../../../trafficserver/proxy/http2/Http2ClientSession.cc:531
#13 0x00000000006a02be in Http2ClientSession::state_start_frame_read (this=0x2b568b05b700, event=100, edata=0x2b4e42ddcb30) at ../../../../trafficserver/proxy/http2/Http2ClientSession.cc:424
#14 0x000000000069fa1e in Http2ClientSession::main_event_handler (this=0x2b568b05b700, event=100, edata=0x2b4e42ddcb30) at ../../../../trafficserver/proxy/http2/Http2ClientSession.cc:324
#15 0x0000000000551968 in Continuation::handleEvent (this=0x2b568b05b700, event=100, data=0x2b4e42ddcb30)
    at /var/builds/workspace/157188-v3-component/BUILD_CONTAINER/rhel7-gcc6_2/label/DOCKER-HIGH/app_root/_build/ats_build/../../trafficserver/iocore/eventsystem/I_Continuation.h:153
#16 0x00000000007e84b6 in read_signal_and_update (event=100, vc=0x2b4e42ddc9e0) at ../../../../trafficserver/iocore/net/UnixNetVConnection.cc:144
#17 0x00000000007eb4ec in UnixNetVConnection::readSignalAndUpdate (this=0x2b4e42ddc9e0, event=100) at ../../../../trafficserver/iocore/net/UnixNetVConnection.cc:1095
#18 0x00000000007c2aea in SSLNetVConnection::net_read_io (this=0x2b4e42ddc9e0, nh=0x2b4ae1507cf0, lthread=0x2b4ae1504010) at ../../../../trafficserver/iocore/net/SSLNetVConnection.cc:607
#19 0x00000000007dfdfd in NetHandler::waitForActivity (this=0x2b4ae1507cf0, timeout=19999267) at ../../../../trafficserver/iocore/net/UnixNet.cc:497
#20 0x000000000080d670 in EThread::execute_regular (this=0x2b4ae1504010) at ../../../../trafficserver/iocore/eventsystem/UnixEThread.cc:272
#21 0x000000000080d837 in EThread::execute (this=0x2b4ae1504010) at ../../../../trafficserver/iocore/eventsystem/UnixEThread.cc:325
#22 0x000000000080c46c in spawn_thread_internal (a=0x1fd3800) at ../../../../trafficserver/iocore/eventsystem/Thread.cc:85
#23 0x00002b4ad9969dc5 in start_thread () from /lib64/libpthread.so.0
#24 0x00002b4ada69876d in clone () from /lib64/libc.so.6

I believe this is fixed now.


 Unfortunately, now that that rainy day has come it looks like Spotify has gone for the jugular and torched all the pip repositories that this project relies upon:
https://pypi.python.org/pypi/spotify-ripper/2.10.3
and
https://pypi.python.org/pypi/spotify-ripper/1.4.1
are totally gone and pip install spotify-ripper does absolutely nothing.
Is there any place I can find the script here on the github? I apologize but python isn't really a strong point of mine; I'd really appreciate good instruction.
Thank you for taking on this project!

Hi Kezzsim,
try pip install spotify-ripper-morgaroth.
I hope to help you.
Regards,
Celson Simon

Hi Celson!
That worked! Someone should update the read me with that pip link!
Thank you~
Kezzsim


Filter only project directories

I have an issue with a project that uses folder named "bin" for other purposes (it's actually a part of javascript assets).
Can you make the script remove "bin" and "obj" folders only in top level .NET project directories (they always contain *.csproj / *.vbproj files)?

I overlooked your question unfortunately. You probably solved this long ago.
Some projects might have output folders set to other locations and there may be build scripts used that put files to some subfolder structure - such feature would be too restrictive for general use.
Thanks for the suggestion.


adding data refresh indication

@Velua
this is first a question on possabilities.
IF we have a process that pulls fresh data every few seconds, can this be indicated on the data table (and later on protection table as well)?
see example:

Yes it's possible, though how frequently would we want it to update? The more frequent the more concurrent request seats we're going to be utilising over time.

as a way to show and indicate to the user that data is updating on the main data table, we would like to implement the same logic as the protection tab rewards animation.
on load - numbers should run up
every 15 seconds, numbers should run the diff between current and new value
this should ONLY be done on the statistics section on the data page.
the specifics from the claim rewards task:
Data movement
in order to show movement, we would like to use some type of increasing number effect.
on refresh/load: start all values at 0 and grow them to the number they should be. Claimable should take 3sec while total rewards should take 5sec to load.
total rewards: if we automatically refresh the data every 15 seconds, break the delta increase and increase the value over a 15sec time span.
claimable rewards:
when user claims rewards, count down to 0 in a span of 3 seconds.
if we automatically refresh the data every 15 seconds, break the delta increase and increase the value over a 15sec time span.
code sample to the effect: https://codepen.io/duvander/pen/KXOpXw

@Ran73Cohen is this still open?

@Ran73Cohen is this still open?

We can merge this but do we want the 15 seconds refresh or not?


LegendHelper CreateLegendAtFigureRight and CreateLegendAtFigureBottom need refactoring and updating

These functions need to use common code.
Why is there a check if the LegendOptions is not none?  Should this be an error?  Or at least provide a warning?
Provide option to change other offset (x/y).

This now raises an error.


convert_bits Iterator

When writing out an object as a bech32 string via fmt it seems we currently have to first encode the [u8] into a Vec<u5> and only then we can call encode_without_checksum_to_fmt. This is a bit wasteful, ISTM it wouldn't take a whole log of change to build a version of convert_bits that returns an iterator rather than a Vec, and allows avoiding the intermediate allocation.

I think this has been resolved by the recent crate re-write, likely can be closed.


Get PSP-Palette working from Silicon Mac Processor

Closing this issue as it is not relevant to this repo.


Why do we minimize "profit" in objective function?

Hello, I again tried to deep into theory and julia code to understand how objective function work.
    # Objective function
    function fn(v)
        if !all(v .== r.v)
            find_arb!(r, v)
            r.v .= v
        end

        acc = 0.0

        for (Δ, Λ, c) in zip(r.Δs, r.Λs, r.cfmms)
            acc += @views dot(Λ, v[c.Ai]) - dot(Δ, v[c.Ai])
        end

        return f(r.objective, v) + acc
    end

Accumulator accumulates sum of differences between how much we "accept" and how much we "give", e.g. (Λ - Δ)*c.Ai is our profit.
The optimizer minimizes this function, so the less fn(v) the better.
As far is f(r.objective, v) is zero if trade is valid, the best v for optimizer is when acc is zero. Why shouldn't we subtract acc here or adding 1 / acc? E.g. why for optimizer better to find solution with profit against solution when profit is zero?
As I understand, each find_arb should not return (0, 0), because the optimizer will find such v. Λ = 0, Δ = 0 in physical meaning is "we won't trade here". But in Uniswap V3 cfmm (0, 0) when we going out of ticks. So optimizer will find solution when we going out of liquidity if it exists.

I got it, the main reason finding minimum profit - is to find "real" prices, because when profit is 0 then the blockchain is stabilized.


execute tpcds.sh error

executing on kslave2 ./start_gpfdist.sh 9001 /data/hawq/segment/pivotalguru_1
Started gpfdist on port 9001
executing on kslave2 ./start_gpfdist.sh 9002 /data/hawq/segment/pivotalguru_2
Started gpfdist on port 9002
executing on kslave2 ./start_gpfdist.sh 9003 /data/hawq/segment/pivotalguru_3
Started gpfdist on port 9003
executing on kslave2 ./start_gpfdist.sh 9004 /data/hawq/segment/pivotalguru_4
Started gpfdist on port 9004
executing on kslave2 ./start_gpfdist.sh 9005 /data/hawq/segment/pivotalguru_5
Started gpfdist on port 9005
executing on kslave2 ./start_gpfdist.sh 9006 /data/hawq/segment/pivotalguru_6
Started gpfdist on port 9006
executing on kslave1 ./start_gpfdist.sh 9001 /data/hawq/segment/pivotalguru_1
Started gpfdist on port 9001
executing on kslave1 ./start_gpfdist.sh 9002 /data/hawq/segment/pivotalguru_2
Started gpfdist on port 9002
executing on kslave1 ./start_gpfdist.sh 9003 /data/hawq/segment/pivotalguru_3
Started gpfdist on port 9003
executing on kslave1 ./start_gpfdist.sh 9004 /data/hawq/segment/pivotalguru_4
Started gpfdist on port 9004
executing on kslave1 ./start_gpfdist.sh 9005 /data/hawq/segment/pivotalguru_5
Started gpfdist on port 9005
executing on kslave1 ./start_gpfdist.sh 9006 /data/hawq/segment/pivotalguru_6
Started gpfdist on port 9006
psql -v ON_ERROR_STOP=ON -f /pivotalguru/TPC-DS/04_load/051.insert.call_center.sql | grep INSERT | awk -F ' ' '{print $3}'
psql:/pivotalguru/TPC-DS/04_load/051.insert.call_center.sql:1: ERROR:  External scan error: There are more external files (URLs) than primary segments that can read them (COptTasks.cpp:1756)

I can't reproduce this error.  Can you share your hawq-site.xml file?


remove base weight annotations

Remove base weight annotation as described in this issue #10327
Polkadot address: 12ZNas89oEagaxLVNbpqmvfMxdrGrqN7gJKSpwthTUPZsrku

bot merge


Support for auto-scanning files

Would be nice to have an auto scanning all style files for variables in the project.
Reason: we have a lot of components with custom css properties in separate files.
Therefore maintaining the list manually in the settings doesn't work well in that case..
Solution: chokidar + glob (to limit directories for performance if needed). Wdyt?

Tried this in the settings, doesn't work or works partially..
    "cssvar.files": [
        "src/renderer/**/*.css",
        "src/renderer/**/*.scss",
    ],

This plugin, as of now, works only with pure css files. SCSS files are supported only if there's no sass specific code present in the file.
Anyways, good idea, will try to find solution for this

Got excited but then sad when noticed it doesn't work for SCSS. :( Also our files vary for each project so it's a pain defining them all the time. When I define it like this:
"cssvar.files": ["content/themes/**/*.css"],

I get:
Failed to parse CSS variables in files`

Are you folks using some custom postcss plugins??
If so, this plugin is kept minimum, as of now, and uses postcss parser, without any plugins, thus any rule not part of W3 CSS specification will through a parser error.
I am plaaning to support a config to provide postcss plugin in future, but faced some issues with implementing it, so have deferred the task for now.
Will update here, once I add the support for postcss plugins

Yes, using stylelint + postcss + etc. But it's not exactly clear to me why this plugin should support those as long as it just trieds to fetch CSS vars from the files.

To fetch variables from CSS files, the plugin needs to parse the files passed in cssvar.files, where if the files are not pure CSS, the parser will throw an error.
That's the reason I mentioned before this plugin doesn't support Sass or any custom variant of CSS, to keep the plugin small and less complex.
But, I will in future add support to provide Postcss Plugins
I hope this clears your doubt @ronilaukkarinen

Ah, OK, thanks for the clarification. Those CSS files I defined are pure CSS files understandable by browsers though.

Can you provide me with a sample file if possible? This will help me to debug the issue, if any!

I have released v1.1 which adds support for CSS extensions like SCSS syntax and more.
Latest release now supports the following:

@use "file" syntax
@import "file" syntax
Some custom SCSS/SASS syntax in CSS, use Postcss Plugin as mentioned here: Plugin Customization
If your project is entirely built with SCSS or some other CSS extension, use PostCSS syntax as mentioned here: Syntax Customization


Link to Appliance not working

Link to: http://suse.github.io/docs/setups/2_appliance.html on http://suse.github.io/Portus/ is not working

It's http://port.us.org/docs/setups/2_appliance.html now. Where did you find this link ?

Found it at the bottom of the page on the word appliance:
We provide also a ready to go appliance based on openSUSE.

We fixed that in the commit 7147f2f79e2134e2d78b58c0f9d2aa298939831c. But the real problem is that for some reason, in our github pages setup, suse.github.io/Portus is not redirecting to port.us.org :/ Let me investigate on this.

But until that is not fixed, just use http://port.us.org ;)

I think @eotchi is the only one who can help us.

AFAIK this has been fixed. Feel free to re-open if this is not the case.


Add wrappers for clGetHostTimer and clGetDeviceAndHostTimer

Coverage remained the same at 83.688% when pulling aafe71dd19ff04a69f9200217785920c599d080f on jszuppe:pr_device_host_timers into 23ce38e1b2efd935238abd910c170e6eaa71bbd9 on boostorg:develop.

Coverage remained the same at 83.688% when pulling b43adb45177a42579ce956bcc442441d9dd38fb5 on jszuppe:pr_device_host_timers into 23ce38e1b2efd935238abd910c170e6eaa71bbd9 on boostorg:develop.

Looks good, just one comment, I think these new device methods can be marked const.

You're right, it's done.

Coverage remained the same at 83.688% when pulling 8f0b1bbc3f1ef47ece41abed1542194cc4ee0001 on jszuppe:pr_device_host_timers into 23ce38e1b2efd935238abd910c170e6eaa71bbd9 on boostorg:develop.

Thanks! Merged!


Websocket disconnect not passing WebSocketConnect.Error

Hey, looks like WebSocketConnect.Error is never actually used in the code, so the first branch never happens here:
WebSocket.connect[F, Msg[F]](apiSocketUrl, KeepAliveSettings.default):
  case WebSocketConnect.Error(_) => ???
  case WebSocketConnect.Socket(ws) => ???

I tried to implement automatic reconnect and found this. Also noticed that WebSocketConnect.Socket(ws) is indeed called when connection actually gets lost.

Actually I was able to implement reconnect by handling WebSocketEvent.Close. Still not sure if that WebSocketConnect.Error case is ever called thought, but doesn't harm me.

In practice websocket errors are pretty useless, see:
https://github.com/http4s/http4s-dom/blob/726af7c65e4bf345b66a192bf05c5a28b2fdacd1/dom/src/main/scala/org/http4s/dom/WebSocketClient.scala#L76-L78


Android Studio or VSCode not showing any iPhone in device list

I connected many physical device and none of them showing in device list.
Some weeks earlier this function was working
What can I do to make it works again?
Thanks

/Users/szalok/Work/flutter/bin/flutter doctor --verbose
[✓] Flutter (Channel stable, v1.9.1+hotfix.6, on Mac OS X 10.15.1 19B88, locale hu-HU)
• Flutter version 1.9.1+hotfix.6 at /Users/xxxx/Work/flutter
• Framework revision 68587a0916 (3 months ago), 2019-09-13 19:46:58 -0700
• Engine revision b863200c37
• Dart version 2.5.0
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at /Users/xxxx/Work/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.2
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.2.1, Build version 11B500
• CocoaPods version 1.8.3
[✓] Android Studio (version 3.5)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 42.1.1
• Dart plugin version 191.8593
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
[✓] VS Code (version 1.40.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.7.1
[!] Connected device
! No devices available
! Doctor found issues in 1 category.


Adds HOST and PORT env variables to react app so websocket

Adds HOST and PORT env variables to react app so websocket can use them instead of window.location.
This addresses the issue listed here: https://github.com/facebookincubator/create-react-app/issues/853
This can be tested by adding a .env file to an app with the following content:
HOST=<IP_ADDRESS>
PORT=3000

Then run the app by visiting http://localhost:3000. If you look at the network requests, you will see the websocket is using <IP_ADDRESS> and not localhost.

Added CLA

So does this fix the problem with pow specifically

I don't use pow so I can't answer for certain. Maybe @thom-nic could chime in.
But I think it should because create react app would be listening on localhost:3000 for the websocket and that is what would be requested from the react app as long as its specified under host/port env vars.
Currently if its getting served through foo.dev via window.location, the web socket would get denied by the pow server.

OK, tagging it for consideration for 0.10.
I don't understand the issue very well yet so it would help if more people could chime in.

The issue is if you are running a separate web server as your main backend for a project and are proxying requests to the react app bundle.js through it.
As I said in the issue, I was able to overcome this issue by implementing a websocket proxy on my server, so its not crucial for me anymore, but it seems to make sense. To assume that window.location is the server hosting the websocket seems optimistic. But I see your point about create react app only for simple setups.

When building a WordPress theme using React you need to run a separate web server (Apache or Nginx) as the main backend.

This is going to be helpful for me as well as I'm trying to use react-create-app with a Django backend where I need to serve the index.html server side (mainly to pass some initial data and settings to React). At the moment I have the problem where the websocket is trying to connect to http://localhost:8000 (Django) instead of http://localhost:3000 (Webpack dev server)

Yes that sounds like it would solve my initial request.  I took to heart that create-react-app is for trivial setups and quickly ejected and customized things, so I can't say I'm facing the original situation anymore.

Can we also have publicPath changed from / to http://${process.env.HOST}:${process.env.PORT}/. This would enable fetching the hot module chunks without hard reloading.

Thanks for making this PR! I ran into an issue with developing chrome extensions where window.location.protocol is set to chrome-extension: causing an error with SockJS.
This can be fixed by adding the following:
var connection = new SockJS(url.format({
-  protocol: window.location.protocol,
+  protocol: process.env.REACT_APP_SOCKJS_PROTOCOL || window.location.protocol,
...
}));

How about changing this line to procotol: process.env.HTTPS ? 'https' : 'http'? That would fix your problem too, @dmk255, right?

@sktt That's even better. I also agree that this should probably be done for publicPath too.

@sktt That's even better. I also agree that this should probably be done for publicPath too.

Edit: After doing some more development around chrome extensions I've realized that the above proposal will not cover all situations. Chrome will not allow external dependencies (e.g. <script src='https://localhost:3000/foo.js'>) to access its chrome storage (chrome.storage). The dependencies that access those APIs need to be loaded via the chrome-extension:// protocol.
Given this, I believe publicPath should default to @sktt 's proposal but have the ability to be overridden by another environment variable e.g. REACT_APP_PUBLIC_PATH.
In the chrome extension use case, a developer needs SockJs to point to the localhost but the injected scripts to source from chrome-extension://mhleglpkaimohejeochljenlpohnpnph/ (their given app id).
I'm happy to clarify further if there are any questions about this use case.

Problem about publicPath: webpack dev server uses it both for hot chunks
and assets. :s
On Mon, 8 May 2017 at 00:33, Daniel Kezerashvili<EMAIL_ADDRESS>wrote:

@sktt https://github.com/sktt That's even better. I also agree that
this should probably be done for publicPath too.
Edit: After doing some more development around chrome extensions I've
realized that the above proposal will not cover all situations. Chrome will
not allow external dependencies (e.g.

There is also suggestions about configuring this from the script tag such
as #1994. However, publicPath depends on the host and port too for assets
and hot chunks so with that, configless, approach the publicPath must be
set on runtime by also setting webpack_public_path which could be
confusing while you'd expect it to be by the webpack config
On Mon, 15 May 2017 at 14:38, SciSci<EMAIL_ADDRESS>wrote:

@scisci commented on this pull request.
In packages/react-scripts/config/env.js
https://github.com/facebookincubator/create-react-app/pull/1588#discussion_r116478834
:

@@ -29,7 +29,12 @@ function getClientEnvironment(publicUrl) {
// For example, <img src={process.env.PUBLIC_URL + '/img/logo.png'} />.
// This should only be used as an escape hatch. Normally you would put
// images into the src and import them in code to get their paths.

 'PUBLIC_URL': publicUrl

 'PUBLIC_URL': publicUrl,

 // Useful for allowing the hot dev websocket to connect to the host

 // specified in the env file, instead of window.location, which could

 // be wrong if the dev server is being proxied.

 'HOST': process.env.HOST || '',

 'PORT': process.env.PORT || ''

I believe it needs to be configured somehow. The .env file was the only
place that I knew of that allowed this, that's why I chose to put it there.
I wasn't aware that variables could be shared in another way but if you
point me in the direction of an example I could change this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebookincubator/create-react-app/pull/1588#discussion_r116478834,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABXj8Jm38sY2eujoXdv7Dn54_T5vyfwtks5r6EcngaJpZM4MFEXK
.

As it doesn't seem we're going to do #1994 how do we get this PR over the line? If we're not using env vars what else are we going to use? Config in package.json?

Package.json seems like the best place, could mirror the devServer
section of a webpack config
On Fri, 19 May 2017 at 13:53, David Burrows<EMAIL_ADDRESS>wrote:

As it doesn't seem we're going to do #1994
https://github.com/facebookincubator/create-react-app/pull/1994 how do
we get this PR over the line? If we're not using env vars what else are we
going to use? Config in package.json?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/facebookincubator/create-react-app/pull/1588#issuecomment-302683159,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABbefGROPaXzuX0Wnjz-yQ06k2QzZgdks5r7YLQgaJpZM4MFEXK
.

@Timer any input on how to proceed with this PR?

One note: in create react app readme there is this line:
Use environment variables to inject the right server host and port into your app.
So I don't see the aversion to these env variables

@scisci the problem is here - it doesn't look for the env variables at the moment https://github.com/facebookincubator/create-react-app/blob/master/packages/react-dev-utils/webpackHotDevClient.js#L161

@roborourke, this pull request solves that problem. That's what it was made to do. Check the changes to webpackHotDevClient.js

Okay, looking at this again, I'm confused - the Advanced Config section of the ReadMe specifically says we can set the HOST and ENV vars to define where the CRA server is listening.
I just can't see why @Timer wants to not use env vars when this PR doesn't actually use any new env vars, just the one's already available?

Sorry for the lack of communication here; I've been a little tight on time!

Okay, looking at this again, I'm confused - the Advanced Config section of the ReadMe specifically says we can set the HOST and ENV vars to define where the CRA server is listening.

@gaearon and I had a conversation and agreed that these are not environment variables we want to expose to the application; meaning if someone used process.env.HOST in their app we don't want it to be inlined.

Use environment variables to inject the right server host and port into your app.

This is referring to the REACT_APP_* flavor of environment variables; the impact of HOST and PORT is at development time, not application time. Even then, this is a suboptimal way of doing this as there are other solutions.

Let me go ahead and take a look at this real quick.

This config is purely for dev time webpack reload behaviour - our deployed app doesn't need to reload so we should never be using any of these vars in the build process.
Just for reference, PR #1994 has some more detail on what this is trying to do - both these PR's are basically trying to do the same thing, but @sktt seemed to think this way would be a more complete solution.

@gaearon and I had a long conversation about this & related elements.
Considering the end-goal, we realized all of this is going to require some architectural changes (in the context of CRA moving forward).
I'll draw up a proposal issue here soon, which addresses other problems as well.

@Timer what kind of architectural changes needed?

For anyone who want to use this feature now: I use a (very hacky) script to apply the changes from #1994 and introduce a new env variable PUBLIC_PATH. This is, of course, only a temporary solution until the architectural changes are in place.
https://gist.github.com/madebyherzblut/aef2377081aab39b9a780a418115d671

https://github.com/facebookincubator/create-react-app/issues/3071 is a related issue that has clearly propped up after history looks to have repeated itself

it seems that this feature is still not added...

@Timer no plans to add this in 2.x anymore?

We didn't switch yet to Create React App here because of this issue.
We use (unfortunately) different backends to serve the legacy php frontend and react app and need to specify ws host/port to benefit from hot reloading

After 2 years, I still don't understand what the issue with the original PR was. Why was there architectural changes needed? The PR only uses PORT and HOST env. variables if they are there and if not then falls back to window.location.
Since then, I have seen many universal/ssr projects either fork react-dev-utils for this, or the replace-string build time hack provided above. I don't like either approach as I would like to not think about keeping an up-to-date react-dev-utils or monkey patching it.
@Timer @gaearon If you guys can please provide some guidance here it would be greatly appreciated.

Superseded by https://github.com/facebook/create-react-app/pull/7750


correct some comments

What type of PR is this?
/kind document

What this PR does / why we need it:
correct some comment spelling and grammar
Which issue(s) this PR fixes:

Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

/ok-to-test


Update to Windows UI Library 2.1

Update Calculator project to Windows UI Library 2.1 (Release Notes). As part of this update, we should thoroughly test all user scenarios to check for possible UX regressions. A particularly exciting feature introduced in 2.1 that affects us is Shadows:

With Windows 10 May 2019 Update, many of our common controls add elevation by using z-depth and shadow by default. The NavigationView and TeachingTip controls in WinUI 2.1 will also have default shadows when running on an OS with Windows 10 May 2019 Update.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.


crash if mode tries to delete slide that was already deleted

File "c:\python34\lib\site-packages\kivy\clock.py", line 406, in tick
   ret = callback(self._dt)
 File "c:\python34\lib\site-packages\mpfmc\uix\slide.py", line 220, in remove
   del self.mc.active_slides[self.name]
KeyError: 'slide_76'

fixed


x/build/cmd/gerritbot: does not respect codereview.cfg for fixing commit messages

https://go-review.googlesource.com/112277, which came from PR golang/vgo#4, said "Fixes #24099." The git-codereview tool would have read the vgo repo's codereview.cfg and automatically rewritten that line to say "Fixes golang/go#24099." This helps both authors and reviewers, neither of whom have to think about this anymore. The PR-bot should do the same, because as a reviewer I certainly don't want to lapse back into being in charge of catching this trivial but common mistake. Because the bot did not fix the commit message, the eventual submit did not close the issue.

/label help wanted

FYI git-codereview has the logic to fix this. This issue is solely about gerritbot. Russ' initial comment is mistaken. git-codereview does indeed do this. But since this is a PR, I am guessing the submitter did not use git-codereview, hence it got missed out.


Refactor input/output types

Currently, we have two types for input topics and extra output topics. However, we could use the same type but just distinguish if role is set or not because role is mandatory for extra types. The same can be applied to input pattern and output type. See https://github.com/bakdata/kpops/blob/aa44fdf6520a4ef9c520b27cfdb94e9fc35cd079/kpops/components/base_components/pipeline_component.py#L117

I would do the following:
Output topics

Default type is output
If role is set, type is inferred to be extra

This would mean that the user only needs to specify a type for error topics
Input topics

default type is input
Add an input topic type pattern
If role is set, type is inferred to be extra-pattern if type is pattern, else extra

I would not remove any functionality, just set some defaults and add the pattern type here

There should be the following types for from:

input (can be default if not specified)
pattern

If role is specified, it is treated as extra input topics/extra input patterns
For to we need the following two types:

output (can be default if not specified)
error

If role is specified for the first, it is trated as extra output topics, for error it is a misconfiguration


[SMALLFIX] Move loading cluster default configuration into beforeConnect

Add beforeConnect in AbstractClient so different implementation client can choose the right preparation based on their type

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20701/
Test PASSed.


Make homepage it's own type

This is to prevent the overwriting of homepage translation urls to be blank, since we're using a different format for these translation urls. Felt cleanest to make them their own type and put in a separate folder, but not sure if it will work. Putting up a PR lets me test on Netlify deploys.

I think it worked? Sites not broken, but doesn't seem right on admin end. I don't know if that's just because admin preview is still a little wonky on netlify or what.


Try to load trusted conv meta if we find no participants in the mention hud WIP

Kind of already done. WIP because I may switch it to detect this case in selectConversation and request the trusted meta there. any thoughts @keybase/react-hackers?

How does this play out if it does miss? Is the HUD just sitting blank for like a second before everything pops in?

@keybase/react-hackers  this is ready

Loading state seems pretty key, this could hit the network and be slow.


Changed how GameServer POD names are generated

Instead of generating name based on GS prefix, we take GS name as-is.
This is safe, since Pods are owned by Gameservers, so their lifetime is a subset of that of GS, thus we won't have accidental pod name collisions.
This fixes #490

We will need to add a section here in the gameservers controller, such that if k8serrors.IsAlreadyExists(err) - then continue through, otherwise we're going to end up in an infinite backoff if the pod already exists, as the error will keep getting rethrown.

We will need to add a section here in the gameservers controller, such that if k8serrors.IsAlreadyExists(err) - then continue through, otherwise we're going to end up in an infinite backoff if the pod already exists, as the error will keep getting rethrown.

Done.


GROOVY-8840: use inferred type for subscript if operand is placeholder

https://issues.apache.org/jira/browse/GROOVY-8840
map/list/array[complex expression] may not resolve all generics for "complex expression".  This can prevent matching DGM getAt(List, int) for [] since "complex expression" needs to resolve to int/Ineteger to make the match.

Merged. Thanks


fix sqlite + lowest points export

SQL was abandoned for .csv approach on disk, lowest points reimplemented in another PR


unMock()

Might be a more intuitive way to overwriteRoutes to explicitly unmock first then remock after.
Could also have a replaceMock() method, or maybe allow a third/fourth parameter to specify that a reused name is intended to overwrite a mock
Another possibility is editMock(), where an existing mock has additional optios added to it
Imagine a basic mock for a host with some options, editMock could add extra options, e.g. a query string.

For now I've implemented removeRoutes() which accepts a list of names.
replaceRoute() is a nice idea, but not a priority for now so closing until a real user actually asks for it


[DDS] Can't access debug web app on localhost but works on <IP_ADDRESS>

Steps to reproduce:
# create a web project
dart create -t web myapp
cd myapp
dart pub global activate webdev

start debug daemon (since that's what vscode seems to be doing)
webdev daemon web:8080

This starts the web app at <IP_ADDRESS>:8080
If I change the browser address to localhost:8080 it crashes the daemon with below error
[{"event":"daemon.log","params":{"log":"[INFO] Received request for entrypoint at http://localhost:8082/main.dart.bootstrap.js"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Loading debug metadata..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Loaded debug metadata (sound null safety)"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Injected debugging metadata for entrypoint at http://localhost:8082/main.dart.bootstrap.js"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Initializing expression compiler for main.dart.bootstrap.js with sound null safety: true"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Updating dependencies..."}}]
Unhandled exception:
WebSocketException: Connection to 'http://<IP_ADDRESS>:62716/v5_zz3h5jg0=/ws#' was not upgraded to websocket
#0      _WebSocketImpl.connect (dart:_http/websocket_impl.dart:1011:41)
dart-lang/webdev#1      WebSocket.connect (dart:_http/websocket.dart:320:22)
dart-lang/webdev#2      new IOWebSocketChannel.connect (package:web_socket_channel/io.dart:80:28)
dart-lang/webdev#3      connect (package:web_socket_channel/src/_connect_io.dart:15:24)
dart-lang/webdev#4      new WebSocketChannel.connect (package:web_socket_channel/src/channel.dart:115:16)
dart-lang/webdev#5      _defaultWebSocketBuilder (package:dds/src/dds_impl.dart:51:27)
dart-lang/webdev#6      DartDevelopmentServiceImpl.startService (package:dds/src/dds_impl.dart:78:40)
dart-lang/webdev#7      DartDevelopmentService.startDartDevelopmentService (package:dds/dds.dart:97:19)
<asynchronous suspension>
dart-lang/webdev#8      DebugService.startDartDevelopmentService (package:dwds/src/services/debug_service.dart:154:12)
<asynchronous suspension>
dart-lang/webdev#9      DevHandler._createAppDebugServices (package:dwds/src/handlers/dev_handler.dart:466:7)
<asynchronous suspension>
dart-lang/webdev#10     DevHandler.loadAppServices (package:dwds/src/handlers/dev_handler.dart:241:21)
<asynchronous suspension>
dart-lang/webdev#11     Dwds.debugConnection (package:dwds/dart_web_debug_service.dart:61:30)
<asynchronous suspension>
dart-lang/webdev#12     AppDomain._handleAppConnections (package:webdev/src/daemon/app_domain.dart:62:29)
<asynchronous suspension>

ps, I am on mac. Not sure if this is related to dart-lang/webdev#233 and dart-lang/webdev#402 since they are able to access on localhost but not on <IP_ADDRESS> but it's opposite in my case.
Also here's my /etc/hosts
<IP_ADDRESS>	localhost
<IP_ADDRESS>	broadcasthost
::1             localhost

I'm able to get a crash, but I'm not seeing it in DDS:
[{"event":"daemon.connected","params":{"version":"0.4.2","pid":47303}}]
[{"event":"daemon.log","params":{"log":"[INFO] Connecting to the build daemon..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Generating build script..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Generating build script completed, took 401ms"}}]
[{"event":"daemon.log","params":{"log":"[INFO] "}}]
[{"event":"daemon.log","params":{"log":"[INFO] Precompiling build script......"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Precompiling build script... completed, took 7.7s"}}]
[{"event":"daemon.log","params":{"log":"[INFO] "}}]
[{"event":"daemon.log","params":{"log":"[INFO] Starting daemon..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Initializing inputs"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Building new asset graph..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Building new asset graph completed, took 1.0s\n"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Checking for unexpected pre-existing outputs...."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Checking for unexpected pre-existing outputs. completed, took 1ms\n"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Initializing inputs"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Building new asset graph..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Building new asset graph completed, took 1.0s"}}]
[{"event":"daemon.log","params":{"log":"[INFO] "}}]
[{"event":"daemon.log","params":{"log":"[INFO] Checking for unexpected pre-existing outputs...."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Checking for unexpected pre-existing outputs. completed, took 1ms"}}]
[{"event":"daemon.log","params":{"log":"[INFO] "}}]
[{"event":"daemon.log","params":{"log":"[INFO] Setting up file watchers..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Setting up file watchers completed, took 5ms"}}]
[{"event":"daemon.log","params":{"log":"[INFO] "}}]
[{"event":"daemon.log","params":{"log":"[INFO] Registering build targets..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Starting initial build..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Starting resource servers..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Serving DevTools at http://<IP_ADDRESS>:51570\n"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Serving `web` on http://<IP_ADDRESS>:8080\n"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Starting chrome with user data directory: /Users/bkonyi/myapp/.dart_tool/webdev/chrome_user_data"}}]
[{"event":"daemon.log","params":{"log":"[INFO] About to build [web]..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Running build..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] 1.0s elapsed, 0/2 actions completed."}}]
[{"event":"daemon.log","params":{"log":"[INFO] 2.0s elapsed, 0/2 actions completed."}}]
[{"event":"daemon.log","params":{"log":"[INFO] 3.1s elapsed, 6/8 actions completed."}}]
[{"event":"daemon.log","params":{"log":"[INFO] 4.1s elapsed, 1291/1291 actions completed."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Running build completed, took 4.1s\n"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Caching finalized dependency graph..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Caching finalized dependency graph completed, took 140ms\n"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Succeeded after 4.3s with 15 outputs (1727 actions)\n"}}]
[{"event":"daemon.log","params":{"log":"[INFO] ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Received request for entrypoint at http://<IP_ADDRESS>:8080/main.dart.bootstrap.js"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Loading debug metadata..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Loaded debug metadata (sound null safety)"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Injected debugging metadata for entrypoint at http://<IP_ADDRESS>:8080/main.dart.bootstrap.js"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Initializing expression compiler for main.dart.bootstrap.js with sound null safety: true"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Starting..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Debug service listening on ws://<IP_ADDRESS>:51622/YtZm9zPHIQM=/ws\n"}}]
[{"event":"app.start","params":{"appId":"pdj07uerloikPm38p+GKEg==","directory":"/Users/bkonyi/myapp","deviceId":"chrome","launchMode":"run"}}]
[{"event":"app.started","params":{"appId":"pdj07uerloikPm38p+GKEg=="}}]
[{"event":"app.debugPort","params":{"appId":"pdj07uerloikPm38p+GKEg==","port":44456,"wsUri":"ws://<IP_ADDRESS>:51622/YtZm9zPHIQM=/ws"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Updating dependencies..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Updated dependencies."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Received request for entrypoint at http://<IP_ADDRESS>:8080/main.dart.bootstrap.js"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Loading debug metadata..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Loaded debug metadata (sound null safety)"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Injected debugging metadata for entrypoint at http://<IP_ADDRESS>:8080/main.dart.bootstrap.js"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Initializing expression compiler for main.dart.bootstrap.js with sound null safety: true"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Updating dependencies..."}}]
[{"event":"app.start","params":{"appId":"pdj07uerloikPm38p+GKEg==","directory":"/Users/bkonyi/myapp","deviceId":"chrome","launchMode":"run"}}]
[{"event":"app.started","params":{"appId":"pdj07uerloikPm38p+GKEg=="}}]
[{"event":"app.debugPort","params":{"appId":"pdj07uerloikPm38p+GKEg==","port":44456,"wsUri":"ws://<IP_ADDRESS>:51622/YtZm9zPHIQM=/ws"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Updated dependencies."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Received request for entrypoint at http://localhost:8080/main.dart.bootstrap.js"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Loading debug metadata..."}}]
[{"event":"daemon.log","params":{"log":"[INFO] Loaded debug metadata (sound null safety)"}}]
[{"event":"daemon.log","params":{"log":"[INFO] Injected debugging metadata for entrypoint at http://localhost:8080/main.dart.bootstrap.js"}}]
Unhandled exception:
Instance of 'AppConnectionException'
#0      DevHandler._startLocalDebugService (package:dwds/src/handlers/dev_handler.dart:182:7)
<asynchronous suspension>
#1      DevHandler.loadAppServices (package:dwds/src/handlers/dev_handler.dart:234:28)
<asynchronous suspension>
#2      Dwds.debugConnection (package:dwds/dart_web_debug_service.dart:59:30)
<asynchronous suspension>
#3      AppDomain._handleAppConnections (package:webdev/src/daemon/app_domain.dart:64:29)
<asynchronous suspension>

We could be seeing the WebSocketException coming from DDS if DWDS fails to accept the connection from DDS due to a crash / bad state. Given that this is a failure to upgrade to a websocket connection, I doubt this is a DDS error.
FYI @elliette @annagrin


typo-fixes: miscellaneous typo fixes

Miscellaneous typo fixes observed while studying the repository.
This fix is not attached to an issue.  Let me know if I need to attach to an issue.

+1 to fixing all uses of Unixly
Note: RC is not "resource manipulator" - it is the "Resource Compiler" - that is what RC stands for.

+1 for 'Windows Resource Compiler" (with capitals).

Let me know if I need to attach to an issue.

It is perfectly legal to create a pull request without having an associated issue. In this case, all discussion will take place on the pr thread (if necessary).

Oh well, "Windows resource compiler" might look better in the context. Choose whatever you prefer.

The PR has been updated with the proposed changes.  Thank you very much for the feedback!

@levitte @paulidale I can merge if you like. BTW: we didn't decide on which branches this should go. My suggestion: master and 1.1.1, ok?

Yes, master and 1.1.1 seems good.  And feel free to merge. :-)

I would recommend squashing it all into one commit, btw...

Editorial note: I will squash the two commits and replace the commit's subject line by the more concise title of this pull request:
typo-fixes: miscellaneous typo fixes

Done. Thank you, @agnosticdev!


fix: chunking fails with detection_class_prob in metadata

Fixes chunking when detection_class_prob appears in Element metadata.
Currently, when detection_class_prob appears in Element metadata, Elements will only be combined by chunk_by_title if they have the same detection_class_prob value (which is rare). This is unlikely a case we ever need to support and most often results in no chunking.
detection_class_prob is now included in the chunking list of metadata keys excluded for similarity comparison.
Testing
Unit test added that currently breaks due to changes in to detection_class_prob but with this change passes since detection_class_prob is excluded from chunking similarity comparison.

So the current logic is to start a new section when any metadata field changes? This makes sense for page numbers, and maybe 1 or 2 fields that I can't think of right now, but is this something we should whitelist rather than blacklist? It seems more likely we would not want this behavior for most new metadata fields.

Related: https://github.com/Unstructured-IO/unstructured/issues/1286 .
IMO, inverse operations of composite elements to get the original will be important. one could "re-index" without saving things twice, for instance, or get high granularity detail about any sub-element in a downstream app.

yes, totally agree on both of these points (whitelist and inverse operations of composite elements). just a quick fix here so that chunking still works out of the box when inference is used (triggering detection_class_prob)

hopefully test coverage still keeps us honest with those changes.


An error occurred (InvalidArgument) when calling the PutBucketNotificationConfiguration operation: Configuration is ambiguously defined. Cannot have overlapping suffixes in two rules if the prefixes are overlapping for the same event type..

I'm running into this error when running cdk. Sorry for being silly, but how I can update or configure new bucket notification prefix if having conflict??
CdkClamAVStack | 55/58 | 9:02:31 AM | CREATE_FAILED        | Custom::S3BucketNotifications          Received response status [FAILED] from custom resource. Message returned: Error: An error occurred (InvalidArgument) when calling the PutBucketNotificationConfiguration operation: Configuration is ambiguously defined. Cannot have overlapping suffixes in two rules if the prefixes are overlapping for the same event type..
Current Code:
`
export class CdkClamAVStack extends Stack {
constructor(scope: Construct, id: string, props?: StackProps) {
super(scope, id, props);

const directBucket = Bucket.fromBucketName(
  this,
  process.env.DATA_BUCKET || `havendirect-${process.env.ENV_TIER}-data`,
  process.env.DATA_BUCKET || `havendirect-${process.env.ENV_TIER}-data`,
);

const sc = new ServerlessClamscan(this, 'rClamscan', {
  acceptResponsibilityForUsingImportedBucket: true,
  buckets: [directBucket],
});

new CfnOutput(this, 'oBucketName', {
  description: 'The name of the input S3 Bucket',
  value: directBucket.bucketName
})

}
}
`

That's a limitation of S3 event triggers. You would have to remove the existing event trigger for the prefix for this solution to work. This AWS premium support article can guide you through that if you choose to remove the existing trigger.

That's a limitation of S3 event triggers. You would have to remove the existing event trigger for the prefix for this solution to work. This AWS premium support article can guide you through that if you choose to remove the existing trigger.

May I know what is the prefix for this solution that is overlapping the prefix?

The construct is  designed to set a trigger over the entire bucket and is currently not configurable

This still seems to be an issue with the (Java) CDK 2.xx library.   Note, I reviewed and confirmed that I did not have any existing event notifications on the bucket before running the CDK deploy task (running the generated CloudFormation script).

@editasmedicinedev Is your CDK application adding any other modifications to the S3 bucket?
Can you share a code snippet that reproduces the issue?

@dontirun - Apologies, I've cleaned up my code and rerun the stack and it no longer produces that error and not sure if I could (or have time) to convert it back.  I'd consider it "not reproducible".  Thank you for asking.  I had moved from the AWS Java CDK 1.x to 2.x stack and running into issues which weren't a problem before.  I'm getting a different error:
Received response status [FAILED] from custom resource. Message returned: Error: An error occurred (InvalidArgument) when calling the PutBucketNotificationConfiguration operation: Unable to validate the following destination configurations.
Since this is different than the one reported here, I will see if there's a different, related issue and not pollute this closed issue.  I had solved the issue (using the CDK 1.x) based upon a fix from this old issue (https://github.com/aws/aws-cdk/issues/6376).


Various updates

Publish appender.par
Add tool for flattening images
cc @nkubala

thanks. what's up with travis?

@KingEmet This is just publishing what we have internally, so let's not hand edit it here.
@jonjohnsonjr Can you fix oci_compat in the mono-repo to unblock this?

@jonjohnsonjr Can you fix oci_compat in the mono-repo to unblock this?

Grabbed the fix from the monorepo.

@jonjohnsonjr this looks good to go now, thanks for the fix!


No variant change if CMS 4.5.0 is activated

h2. Description
CMS-Extensions 4.5.0
Shopware <IP_ADDRESS>
PHP 8.2.23
Firefox and Chrome

The same constellation with CMS 4.4.0 works fine.
Update to CMS extensions 4.5.0.
Open the Shop and select a variant product
Click on different variant options.
Price and Product number will not change.

The report is now 6 days old. Neither a fix has been provided nor has the current version 4.5.0 been withdrawn.

[public]

Status Change: Open

This issue is ready for implementation.
[created from CMS-484, comment 509124]

[public]

Status Change: In Progress

Work on this issue has started. It is now being implemented.
[created from CMS-484, comment 509125]

[public] We have not been able to reproduce this behaviour in the latest version of Shopware, and updating your core shopware version will resolve it. Please create a new ticket with more information if you think this is a general behaviour. Otherwise, please contact our support team or visit the forum.
[created from CMS-484, comment 510549]

It is extremely perplexing that the mentioned issue, which occurs in every Shopware version below <IP_ADDRESS>, was not sufficiently tested with the corresponding versions. For instance, this error is reproducible in version <IP_ADDRESS>, as already reported by the original submitter.
It is surprising that a current Shopware version was used for analysis instead of testing the specifically affected version. To clarify the situation, I have set up a test system:
Details of the test system
Shopware Version: <IP_ADDRESS>
URL: https://cmsbug.enerspace.dev/Variantenprodukt/SWDEMO10005.1
Installed plugins: CMS Extensions, Shopware 6 Demo Data, Shopware Commercial, Shopware Store
It is essential that error analyses are conducted using the actually affected versions to ensure accurate feedback and solutions.
Thank you for your attention and support in further processing this matter.

[public]

Status Change: In Progress

Work on this issue has started. It is now being implemented.
[created from CMS-484, comment 511236]

[public]

FixVersion Change: 4.6.0

This issue will be / was solved in Shopware version 4.6.0.
[created from CMS-484, comment 517285]