Window funnel

Proposed changes
add window_funnel aggregate function for doris
Issue Number: close #xxx
Problem Summary:
The function can be used by like below:
window_funnel(window, mode, timestamp_column, event1, event2, ... , eventN)

window is the length of time window
mode is reserved for future, not used for now
timestamp_column specifies column of DATE or DATETIME type
evnetN is boolean expression like eventID = 1004

window_funnel searches the longest event chain happened in order (event1, event2, ..., event N) along the timestamp_column with length of window.
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

link: https://github.com/apache/incubator-doris/pull/8299


Allow to organize by priority prefix header file

I have a case where boost/asio has to be included before wxWidgets headers in Windows.
Just because windows.h includes <winsock.h> and asio require <winsock2.h> but winsock2.h can not be included after winsock.h (Microsoft joke....)
So using the property COTIRE_PREFIX_HEADER_INCLUDE_PRIORITY_PATH allow us to organize the prefix headers
For example if COTIRE_PREFIX_HEADER_INCLUDE_PRIORITY_PATH is set to path1;path2 any header matching path1 will be put at the top of header list, the any matching path2.... Any remaining header are left untouched

Thanks for the patch. I plan on merging it with the upcoming 1.7 release of cotire.


[FR] Possibility to save more than one Brother printer / configuration

Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

Problem statement
Two scenarios:

the labels in the label printer are changed to ones of different size
I want to use label printers in different locations, both brother

At the moment, this requires me to reconfigure the plugin. Having different configurations to choose from would be great.
Suggested solution
Add a plugin configuration which points to the same backend, but has a different key - and thus different configuration options.
Describe alternatives you've considered
This could also be done by constant reconfigurations...
Examples of other systems
No response
Do you want to develop this?

[ ] I want to develop this.

@miggland this seems off-topic to me, please submit issues with a plugin to the right plugin https://github.com/inventree/inventree-brother-plugin

Is it something to be solved by the Brother plugin though?

Isnt it possible to enable the plugin multiple times? I remember seeing these Button in Django admin. But I have no idea if it will work so easily.

I'm not sure how we would add multiple "copies" of a plugin like you are requesting.
What if we updated the plugin to allow the tape width to be automatically selected based on the dimensions of the label being printed?

Tonight I also thought about Auto selecting the tape size based on the stocklocation type (no idea how to store the type). E.g. I have little drawers with different sizes which each also need different label sizes.

I think a cleaner solution would be:

Allow the brother-printer-plugin to auto-detect the width of the label (based on the label template) and select the tape accordingly
Configure the different labels to match different locations

You can configure each label template with "filters" to match certain items. e.g. for a stocklocation label, filter like name="boxes" (or something similar)

That would solve the first part - but what about having multiple printers?
Isn't label_instance actually useful here?
https://github.com/inventree/InvenTree/blob/1d4a20d1d4cfbdae590f2215fad9c1790898c475/InvenTree/plugin/base/label/label.py#L18

You can configure each label template with "filters" to match certain items. e.g. for a stocklocation label, filter like name="boxes" (or something similar)

Filtering by name would not fit my needs, as I'm having different drawers which are all named the same, but differ in the size so the label slot is also longer.

I think a way of allowing multiple "instances" of a plugin would provide the functionality you need here. I'm just not sure how to implement that or if it is even possible. @matmair any ideas?

At the moment, changing the key (eg on http://ubuntuvm:8000/api/plugin/18/) is allowed, but this plugin then forgets its metadata, so it is no longer recognised.
I imagine having multiple instances isn't only relevant for label printers - potentially, API calls (external site with different user names?), schedules with different command arguments,... could be further examples.
..I've started on something which might work. I'll keep you posted :)

The current system is not designed to support multiple instances and I think implementing that would be a bad idea as it would make plugin development harder.
You could add a model that holds plugin instances and reference settings to that. But that would require plugin creators to be aware of the possibility that the same plugin is running at the same time. The second you start writing config files etc. it gets tricky as plugins might interfere with each other.
Therefore I think this should be handled by the plugin in question.
As for the examples that @miggland listed: API calls are often limited, a single plugin should handle those to ensure call-limits are not broken; you can dynamically name your schedules - that is core functionality; I do not think a valid point towards multiple instances in core plugins is made. In theory, it could be added as a mixin or just be a 3rd party mixin - that is also possible.

This does seem like it's an untenable approach with the current system. My suggestion would be to adjust the tape width setting each time you change the tape in the printer.

And what happens to printers who are able to cut the tape as long as you want?

@wolflu05 sorry, not sure what you mean here. Can you expand a bit?

I am sorry to bring this up again but this is clearly a discussion about https://github.com/inventree/inventree-brother-plugin - a plugin which has its own repo for discussions.
If we start mixing core-project and plugin issues the noise will become unmaintainable with a growing number of plugins.

@SchrodingersGat I would suggest writing a conclusion - i.e. that something needs to change or not - and then locking this as off-topic.

@matmair fair point!
@miggland if you have any further discussion of this please direct over to the plugin repo. Multiple plugin instances is in the "too hard basket" for now.

I agree it's not easy, but I can't see that it'll be a problem for plugin developers (who as a programmer assumes their code will only ever run in one instance??). I think putting multiple configurations in each plugin is the wrong way to go, meaning each plugin developer will have to solve the same problem...
I've fixed my problem by downloading the PDF and printing it via command line. Much easier, and more flexible (plus, gets around the installation problem in the current stable branch..)

@wolflu05 sorry, not sure what you mean here. Can you expand a bit?

@SchrodingersGat There are label printer which print from a coil of presized labels which have fix dimensions [1]. But there are also labels which are on a tape and the printer cut it as long as you want [2].

[1]  product
[2]  product

Hope this makes it clear. So tape labels can be as long as you want that the labels be. And you said, the I have to adjust the labels size each time I chains the coil of labels.
Ideally I want to save the kind of storage box for a stock location and decide on that how long my tape should be.

I agree it's not easy, but I can't see that it'll be a problem for plugin developers (who as a programmer assumes their code will only ever run in one instance??). I think putting multiple configurations in each plugin is the wrong way to go, meaning each plugin developer will have to solve the same problem...

I can fully agree to that. I think this is a problem where every plugin developer has to deal with. What about defining an option ALLOW_MULTIPLE_INSTANCES next to name, slug and description as plugin class variable? So the developer can say no, my plugins my interfer with each other if there are multiple instances or no, they might work fine with different configs. Otherwise each plugin developer has to implement the AppMixin to create some kind of array system which holds different configs as it's not possible with the SettingsMixin. And even if it would be possible, I think it's much easier for a developer to just set a ALLOW_MULTIPLE_INSTANCES = True.
These are my thoughts on this topic and I think, this issue needs to be reopened.

Ok i locked this now as this was continuing to be about a specific plugin

@wolflu05 it takes 4 lines to create multiarray settings.
If this is of interest please create a clean FR with all details.
Our target audience for plugins is the general user base. Plugins should be easy to create and share even for ppl. not to familiar with debian. That is why there are so many domain-specific mixins: do keep the plugins small and easy to understand. The goal is an octoprint-like plugin scene in which InvenTree is the reliable base but plugins solve niche problems.


Fix pylint error R0917.

See:

https://pylint.readthedocs.io/en/latest/user_guide/messages/refactor/too-many-positional-arguments.html
https://github.com/pylint-dev/pylint/commit/de6e6fae34cccd2e7587a46450c833258e3000cb

Thanks!
I usually completely waive many of the stylistic "too many xyz" Pylint violations. Looks like Pylint has introduced a few more variants.
Will be doing some more in-depth cleanup, but this is good to merge.


Add average functions for fix16 and fix32

Loving the SDK by the way 😄.

No particular reason. I have just used this in the past. I think your way is better (1 less instruction and preserving high over low seems better). I will change.


Encapsulate Arrays inside Variables

Hey @maxencefaldor! This is a very cool project, I love it.
Just wanted to give you a heads up that in the next release of Flax, all state is required to be inside Variables. This solves some issues regarding attributes changing from being state or not due to the type. As an easy fix you can encapsulate Array inside nnx.Param or create a custom nnx.Variable type e.g.
self.kernel_fft = nnx.Param(jnp.fft.fft2(jnp.fft.fftshift(kernel_normalized, axes=(0, 1)), axes=(0, 1)))

Most of the code should work as Variables behave as proxies over their inner value and can be passed to JAX functions. The main difference is that to update them you must use .value:
self.kernel_fft.value = new_value

Best,
Cristian

Hey @cgarciae,
I am glad that you appreciate the library and thank you for opening this issue!
I have tried to wrap all state inside nnx.Param but I get this error:
>       state_fft_k = jnp.dot(state_fft, self.reshape_c_k)  # (y, x, k,)
TypeError: Argument 'Param(
E      value=Traced<ShapedArray(float32[3,3])>with<DynamicJaxprTrace(level=3/0)>
E    )' of type <class 'flax.nnx.variablelib.Param'> is not a valid JAX type.

I would like to avoid manually doing self.reshape_c_k.value everywhere. Do you have a solution?

Can you please post this issue on the JAX repo and explain that you would like to treat the Param as a jax.Array?
The issue is that we are using the __jax_array__ protocol to avoid users having to type .value but JAX doesn't have full coverage for __jax_array__ in their APIs so its very important that users show their interest in JAX improving their support for __jax_array__.


Conditional assertions

Hi, thanks for this great project. Is there a way to specify conditional assertions that if an annotation exists, it conforms to some regex?
I have this test:
suite: test service
templates:
  - service.yaml
tests:
  - it: DNS hostname is within length limit
    asserts:
      - matchRegex:
          path: metadata.annotations["external-dns.alpha.kubernetes.io/hostname"]
          pattern: "^(.{3,52}$"

But if annotation is not set, the test fails with unknown path metadata.annotations["external-dns.alpha.kubernetes.io/hostname"]. But I want the scenario of annotation not set to be valid as well.
I did not find anything in the documentation on this topic, is it even supported?

Hello @jankoada,
Thanks for the suggestion.
Will look into it.
Greetings,
@quintush

@quintush I am wondering if we can add a flag in the test cases to make them optional, as in if they fail we throw a warning but the overall test suite doesn't fail because of it. If this seems like a possible way to do it, I can take up the work on this feature.


Implement logging in core-http.

This PR takes a stab at implementing the logging guidelines for core-http, similar to #4926 but without any breaking changes.
Presently, there are two logging-related functionality in core-http:

The logPolicy, which logs requests and responses which go through the pipeline. This PR brings such logging in line with the guidelines with the exception of query string sanitization which is coming later today. The logPolicy is inserted into the pipeline and checks whether info logging is enabled before doing any work. It also uses a custom JSON replacer function in an attempt to be as efficient as possible.
The httpPipelineLogger, which is for policies themselves to use to log by exposing a log() method. I believe this should be deprecated in favor of using core-logging directly. However I've left this functionality in for now as it's possible KeyVault and Storage are using this today.

I've also updated the core logger to be more visibly pedantic when a requested log level isn't known (e.g. if a user tries debug instead of verbose).
To Do:

[ ] Many more tests for header sanitization
[ ] Body sanitization and a test
[ ] Query string sanitization and test
[ ] Options to disable sanitization for query strings, parameters, or body. KeyVault Clients should use this to allow x-ms-keyvault-network-info, x-ms-keyvault-region, and x-ms-keyvault-service-version.

@ramya-rao-a FYI I believe this PR is good to go, though there is some keyvault failure I don't quite understand. @sadasant is helping me uncover the issue.

The strange errors before were due to some il-advised changes to the deserialization policy. With those changes removed, things work better.
I'm not sure why there are two sets of checks running, it looks like the first half are from before the rebase/force push. The latter set is all green, so I believe this is good for someone to pick up from here.
@ramya-rao-a to confirm, you'd like to merge this and file an issue with the todo list above? I have enabled pushing from contributors so we can use this PR to bring it the rest of the way as well. Up to you!

@ramya-rao-a @bterlson I added query object/URI filtering in commit 043a466; let me know if you think I should add some more test cases for filtering as a whole.
Should I also add body filtering or can that wait until a later PR?  Overall I'm good with the level of logging coverage at this point, any more would probably be overkill since the pipeline and ServiceClient logging gives us good visibility already.
If we're OK with the current state of things, I'll run the code formatter one more time and get this merged tomorrow.

Chatted with @bterlson offline, will remove body contents from logging and try to find a more complete set of whitelisted headers/query params tomorrow.

OK, I think this is finally ready to go.  I've moved out the change in keyvault-secrets/src/index.ts and will make a separate PR to add the logPolicy for all 3 KeyVault libraries.

Merging this now, will continue with adding logging to keyvault-* in my next PR.


Set the upper limit during the run time.

Thinking more about it, adding runtime range check will significantly increase the complexity of the tool. There are similar tools (eg. xbacklight) that already do that. The purpose of this tool was to be simpler an so it will remain.
So this issue won't be implemented.


#114: Preliminary UI with info bars

Also:

Standardize the names of the extension method files (.Extensions.cs instead of .extensions.cs).

These changes are merged into the feature branch feature\spam.


Add zsh reference to README

This should document some of the cool features of zsh that are not present in bash, and also the plugins in the .zshrc.

This won't be doable until #129 is finished.


Add ncp-sim to allow_failures group.

Moving ncp-sim travis check to allow_failures group until spurious failures are resolved [1, 2].
This issue is tracked in #517.

LGTM :+1:


Proposal: Convert DE votes into ratings about product phase

What is the problem you are seeing? Please describe.
The criteria for up and down votes on DE are not transparent.
How is this problem misaligned with goals of app mining?
The scores of DE are not objective, voters tend towards favoring own apps they are invested in. The impact of the votes of a single voter are too high.
What is the explicit recommendation you’re looking to propose?
Let votes on DE state in which phase they think an app is (number between 0 and 50 (as a slider?)). The following phases are available:
Idea Phase (pre-seed)
MVP Phase (seed)
Product Market Fit Phase (series A)
Growth Phase (Series B, etc.)
The closer the app toward number 15 the higher the score.
Long term considerations
Number 15 can be adjusted in the future depending on the needs of the ecosystem.
Additional context
Upvotes are contained in the score of Product Hunt.
This was broad up by @kasstawi in https://github.com/blockstack/app-mining/issues/34#issuecomment-468036375

@paulamlb could you please comment on this?

Hi @friedger ! I don't see the problem that you mentioned exactly as a bug, but an inherent property arising from a community vote of this kind. The idea of imposing a specific set of criteria - although it might make a lot of sense for a different App Reviewer - is misaligned with the core intent of our platform as a space for free and democratic decision-making. You are right that having specific criteria is definitely important for the overall ranking though, and that is why Democracy Earth is not the only App Reviewer. So this is one part of the question.
We do agree that there is space for improvement in terms of balancing out the impact of a voter deciding to allocate all his votes on a single app. In that sense, we are considering the path of quadratic voting, which makes the cost of votes exponentially expensive: 1 vote costs 1, 2 costs 4, 3 costs 9, and so forth. The idea here is that the voter pays with his vote credits for the externality that he is imposing on the ecosystem due to his intense preference, thus leading to a more balanced result in the end and more rational decision-making from voters. In addition, we are also looking into ways of providing more information about the apps inside the platform and reformulating the way we display them - all with the intention of bringing more rationality to the voting process. We find mechanism design and game theoretical approaches to be the most valuable when it comes to making results as fair as possible while maintaining the democratic nature of the platform.

Thank you for taking the time to review my proposal. I understand that the change is not desirable.

Thank you for your proactive engagement @friedger . We highly appreciate ideas coming from the community as we continue refining our platform (some of the best features so far came from community input!). Whenever possible and aligned with our decentralization goals, we will surely implement them :)


Feature Request: Display instruction account names when IDL is present

Understanding and debugging transactions would be much easier, especially for program developers, if the explorer displayed the account names from the IDL (see images).

This is a great idea & one I would love to see a PR for!
Specifically, I'd love to see account names / descriptors from instruction cards "upcasted" to labels on the accounts table


NSPrivacyAccessedAPICategoryDiskSpace

I have reason to believe the GoogleMobileAds framework is triggering the privacy sensitive API usage alert, while we can work-around this by marking one of the respective NSPrivacyAccessedAPITypeReasons, I don't know that any of the justifications apply for GoogleMobileAds's usage of the API so cannot in good faith make this declaration.
I note that the Firebase Crashlytics 10.22.0 release "removed calls to statfs in the Crashlytics SDK to comply with Apple Privacy Manifests. This change removes support for collecting Disk Space Free in Crashlytics reports".
Can we confirm if there are disk usage related API calls within the GoogleMobileAds framework and that we can get them removed ahead of 1st May when Apple begins enforcing this policy?
Thanks

Same here.
GoogleMobileAds is indeed triggering privacy sensitive alert for NSPrivacyAccessedAPICategoryDiskSpace.
Using https://github.com/Wooder/ios_17_required_reason_api_scanner I can see
Used symbols in binary ./Development - Debug-iphonesimulator/GoogleMobileAds.framework/GoogleMobileAds: NSFileSystemFreeSize, NSFileSystemSize, NSUserDefaults

Any update on this please?

@all
We are aware of the warnings. This is something Apple will have to fix.

To the googleAdds Team,
Thank you for the update.
Just to confirm, are we correct in understanding that your usage of this particular API doesn't necessitate declaration, and that the issue lies with Apple's implementation?
If this is the case, it's imperative that we gather accurate data to substantiate our position. Since we are ultimately responsible for integrating the SDK into our applications, we need to be able to clearly articulate why certain requirements imposed by Apple are not applicable.
Please ensure that we have access to this data in the event that our application uploads are rejected.
Thank you for your attention to this matter.

Starting in version 11.2.0, the SDK's framework distributes a PrivacyInfo.xcprivacy declaring the usage reasons for these APIs. You can view the declarations by downloading the SDK manually and finding this file. The bug is that App Store Connect is not pulling in those declarations for static frameworks, and think the declarations are missing.


Add prjoxide and nextpnr-nexus

https://github.com/gatecat/prjoxide
Used building bitstreams for Lattice Crosslink NX parts.

Images impl/nexus and impl/prjoxide are available now.


Add a name field to the ControllerStrategy

This field can be used for labels, events, log messages etc.

Needs more detail before moving to ready for work.

Not needed anymore


CommandHandler performs expensive queue check if requestQueueSize != Integer.MAX_VALUE

The second most expensive hot spot in our application is a check lettuce performs in CommandHandler when requestQueueSize has been configured:

This happens in:
https://github.com/lettuce-io/lettuce-core/blob/master/src/main/java/com/lambdaworks/redis/protocol/CommandHandler.java#L288
        if (clientOptions.getRequestQueueSize() != Integer.MAX_VALUE
                && commandBuffer.size() + queue.size() >= clientOptions.getRequestQueueSize()) {
            throw new RedisException("Request queue size exceeded: " + clientOptions.getRequestQueueSize()
                    + ". Commands are not accepted until the queue size drops.");
        }

The JavaDoc for the queue, which in this case is java.util.concurrent.ConcurrentLinkedDeque says:
     *
Beware that, unlike in most collections, this method is
     * NOT a constant-time operation. Because of the
     * asynchronous nature of these deques, determining the current
     * number of elements requires traversing them all to count them.
     * Additionally, it is possible for the size to change during
     * execution of this method, in which case the returned result
     * will be inaccurate. Thus, this method is typically not very
     * useful in concurrent applications.

Options to fix this could be to manually count command enqueue and dequeue

Good catch. I pushed a changed version to https://github.com/lettuce-io/lettuce-core/tree/issue/507-expensive-size.
Do you want to give it a try?
<dependency>
  <groupId>biz.paluch.redis</groupId>
  <artifactId>lettuce</artifactId>
  <version>4.4.0-SNAPSHOT</version>
</dependency>

<repositories>
  <repository>
    <id>sonatype-nexus-snapshots</id>
    <url>https://oss.sonatype.org/content/repositories/snapshots</url>
    <snapshots>
      <enabled>true</enabled>
    </snapshots>
  </repository>
</repositories>

@mp911de the environment where I observed this (with like 1million pending commands) does not permit "trying". others are not really affected that much, but from a code review perspective i think the change should do the trick. thanks for taking care.

That's fixed now.

much appreciated


Evaluating current tenant selection panel

This is the current tenant selection panel. We have adopt some requests from https://github.com/opendistro-for-elasticsearch/security-kibana-plugin/issues/615 that adding an option to save tenant selection and adding search/sort functions.

Any experience improvement?

Could we remember the tenant choice implicitly without any user input (no checkbox needed)?

Could we remember the tenant choice implicitly without any user input (no checkbox needed)?

Could you provide a reason for it?

Notes from discussion between PM and Eng...

Do we prompt users on very first login for tenant selection? Yes
Do we implicitly remember selection (aka do we remove the checkbox)? Yes
What is the default selection? Private

I can be wrong, but I think that this panel should be disabled in case we set opendistro_security.multitenancy.enabled: false Right now this panel appears on every login and breaks the ability to create reports.
Here is a panel that we see on each and every login:

and here is how the report looks like:

We have a system where each user only has access to one tenant.  For this we have disabled the global and private tenants.
If a user can only select one tenant in the UI then I feel that it would be reasonable to not present the user with a redundant tenant selection UI and take the user straight to the only tenant that they can access.

Are there any further thoughts on making improvements around the tenant selection box?  It seems to me that there are a lot of outstanding usability issues around this and I think there are some big wins that could be had here.

Do not present tenant box if only one tenant is available to the user (as above) and https://github.com/opensearch-project/security-dashboards-plugin/issues/519
Do not show tenant box if multitenancy is disabled https://github.com/opensearch-project/security-dashboards-plugin/issues/728
Set a default tenant for a new user or role https://github.com/opensearch-project/security-dashboards-plugin/issues/679 https://github.com/opensearch-project/security-dashboards-plugin/issues/74
Allow easier switching of tenants https://github.com/opensearch-project/security-dashboards-plugin/issues/103

Here are some of thoughts on tenants:

If a role has access to single tenant, in this example "customers"

Then when a user logs in with that role, they are automatically in that "Customer" tenant by default.

Since this user/role only has access to a single tenant, then the "Switch tenant" button should not even show up:

If the user/role has access to more than one tenant then when the user logs in then the user should be greeted with a similar screen to select the desired tenant (I might be spoiled with how Elastic does Spaces :smile: ). Maybe the "Select your tenant" modal could be changed to show a box/card per tenant including Global and Private:

When a user/role only has one tenant and logs in they are automatically logged in on the Global tenant even though global is disabled for that tenant, (maybe a bug?):

If Global and Private are disabled, Is there any reason to show them as disabled? Why not just not show them at all?

Right now if a user wants to change tenants it is a little hard to find. Elastic has it next to their "hamburger" menu, which makes it more accessible :

Moving objects from one tenant to another is more complex than it should be. So far the only way I have seen to do something like this with OpenSearch Dashboards is to export/download the objects I want to move to my device, switch tenant and then re-upload/import them on the saved object screen. It would be nice to be able to copy objects from one tenant to another using the OpenSearch Dashboard UI. Elastic does have something that does this:

It would be nice to be able to upload an icon per tenant. But that is just cosmetics :laughing: .

I know this is a lot and it is probably worth multiple GitHub issues, but I really want to switch to OpenSearch and this is the last blocker in my list to convince the company I work for. Let me know if you want me to create multiple issues for the things I have posted here! :+1:

@yuxitang-amzn is this  feature implemented in any of the versions or it is planned in future releases? Could anyone confirm on this .

The tenant selection features have changed since this report, and among other things tenant selection is remembered between logins (in the same browser). Closing this in favor of (and linking to) #53 for the workflow update suggestions from @derek-diaz as moving objects between tenants is in our radar. Thanks!

Hi @davidlago. I am using version 2.13.0 but everytime user logout, he has to switch tenant. This checkbox cited on this does not appears to it.
Is there any other configuration that I have to set for the role or user?


Changes for the Example notebook

These are changes that are needed in the "ietfdata" code to make the analysis notebook work as intended. They mainly consist of minor additions/changes to error handling of the borderline cases and introducing some imap keepalives during download (also I changed policy to be policy.default in message_from_bytes and message_from_binary file).

Changes rolled into #100.


Unable to use file provider in IngressRoute

Do you want to request a feature or report a bug?

Bug

What did you do?
I want to be able to route some traffic to a service that exists outside of Kubernetes. So, I created a file provider with the following config
    [http.services]
      [http.services.gateway-legacy.loadBalancer]
        [[http.services.gateway-legacy.loadBalancer.servers]]
          url = "http://gateway-lagacy.mydomain.internal/"

Then, in a IngressRoute im trying to reference gateway-legacy in a rule such as
  - match: PathPrefix(`/legacy`)
    kind: Rule
    services:
    - name: gateway-legacy@file
      providerName: file
      namespace: file
      port: 8001

I tried using  providerName: file or namespace: file or gateway-legacy@file but no combination works.
In the logs I get
error msg="Cannot create service: service not found default/gateway-legacy@file" ingress=entry-www-de namespace=default servicePort=8001 serviceName=gateway-legacy@file providerName=kubernetescrd

How am I supposed to route outside the cluster?

What did you expect to see?
I should be able to use a file provider in IngressRoute
What did you see instead?
error msg="Cannot create service: service not found default/gateway-legacy@file" ingress=entry-www-de namespace=default servicePort=8001 serviceName=gateway-legacy@file providerName=kubernetescrd

Output of traefik version: (What version of Traefik are you using?)

Version:      2.0.4
Codename:     montdor
Go version:   go1.13.3
Built:        2019-10-28T20:23:57Z
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml, provider, platform, ...)?
    [http.services]
      [http.services.gateway-legacy.loadBalancer]
        [[http.services.gateway-legacy.loadBalancer.servers]]
          url = "http://gateway-lagacy.mydomain.internal/"

Hi @crhuber , thanks for your feedback.
As we want to keep the Github Issues tracker for bugs and feature requests, not for support,
could you switch the discussion in our Community Forum at https://community.containo.us/ and mention me in the community forum topic so i'll be able to help you immediately?
Don't hesitate to state, first, the problem you are trying to solve at high level, because it is not clear if you want to route from Traefik pod to web services inside Kubernetes, outside Kubernetes, a mix of both? Depending on this statement, I'll give you (in the community forum) a description of 2 different solutions with pro and cons.
As a tip, it looks like there is a confusion between "namespace" and "service" objects in Traefik, which are different than "namespace" and "service" in Kubernetes. If you create an IngressRoute object, then it defines a Traefik Router internally. The IngressRoute mention a "service" which is a Kubernetes service. This will map to a Traefik Service.
When you use file provider, you have to define a Traefik router and a traefik service, which does NOT map at all to a Kubernetes object: there is a strict partition. Same for the "namespace" xxx@file which is a Traefik namespace, while the namespace: referenced in the IngressRoute are Kubernetes namespace objects.

Hi! I'm Træfiker :robot: the bot in charge of tidying up the issues.
I have to close this one because of its lack of activity :disappointed:
Feel free to re-open it or join our Community Forum.


Recommended Interval To Reload Proxies

What is the recommended interval to reload proxies from File or API (in minute)?
I have tested the bot and it worked, except that I lost the views after some days. From reading other issues here, I am now making some changes:

now I am setting multiple urls and search items
I have changed the playback speed from 3 to 1
not running on headless mode
my proxy list has 100 entries from the proxy royal premium
now I changed bandwidth quality from low to normal
and was curious as to what is the proxy reload interval? my current setting for this is 10minutes, what is the recommended?

Thanks!!!

it's something called proxy refresh that the proxy provider offers. like after every 60 minutes your proxy provider will assign you a new proxy list. you can set that time in this script too so that script can get that new proxy list.
one thing I point out is if you use 100 proxy say for a month youtube will see that your views are repeating from the same IP. This script does a lot of things to make it look legit, to humanize everything. So, I suggest getting new proxies at a certain interval that suits you the best.


Add source to nuget packages

Figure out how to add the source to the nuget packages or how to use some other way to enable package consumers to step through the code use to build.

I searched a bit and didn't really find a solution that would work cross-platform and as seamless as I would like it to work. The issues I have with the solutions I found is that consumers of the packages have to explicitly take action to able to see the source. I was hoping there was a better solution.
I wouldn't mind including the source with the nugets if consumers could somehow step through them.
Also: It wouldn't be the end of the world if this didn't make it into 1.4, I was hoping for an easy fix for this.

This may also be relevant here:
https://github.com/dotnet/sourcelink

I'm going to try this and see what it does.

@JoeCooper Did you manage to look at sourcelink? does that look like something we could use here?

Hey, sorry. I had to jump off this project and onto another client for a bit. I'm drowning in work at the moment :/

This is interesting and relevant here:
https://twitter.com/KirillOsenkov/status/1007052524946255872?s=19


[20.09] kismet: 2020-04-R2 -> 2020-09-R2

Motivation for this change
Backport of #97928
ZHF: #97479
cc @NixOS/nixos-release-managers
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

The commit you referenced in the commit message was the original, and this was rebase-merged into master.

Otherwise, WFM non-nixos linux x86_64

Sorry, didn’t see that. Fixed now?


favicon in Tab bar

Favicons are used by web browsers to show a graphical representation of the site being visited at the left side of the browser's address bar.
<!-- added favicon will be displayed on title bar-->
  <!--link rel="shortcut icon" type="image/png" href="img/portfolio/profile.png"/-->
  <link rel='shortcut icon' href='img/portfolio/profiletitle.ico' type='image/x-icon' />

Add this inside <head></head> tag, before TITLE.

Right Tab is with Favicon, made it look better.


Skip no rows error log

Description:
When new host requests for IP, an error -  Unable to fetch IPAddress for reference nginx-ingress/nginx-ingress-service_svc with error sql: no rows in result set is seen. This is confusing to end users.
Changes Proposed in PR:

Skipping to log this error

/azp run


Board Review: Form Recognizer

The Basics

Service team responsible for the client library: Azure SDK Team
Link to documentation describing the service: https://docs.microsoft.com/en-us/azure/cognitive-services/form-recognizer/overview
Contact email: @mayurid

About this client library

Name of the client library: Form Recognizer
Languages for this review: .NET and Python
Link to the service REST APIs: https://github.com/Azure/azure-rest-api-specs/blob/master/specification/cognitiveservices/data-plane/FormRecognizer/preview/v2.0/FormRecognizer.json
and https://westus2.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v2-preview/operations/AnalyzeWithCustomForm

Artifacts required (per language)
We use an API review tool (apiview) to support .NET and Java API reviews.  For Python and TypeScript, use the API extractor tool, then submit the output as a Draft PR to the relevant repository (azure-sdk-for-python or azure-sdk-for-js).
.NET

Upload DLL to apiview.  Link: https://apiview.dev/Assemblies/Review/cf2c57b3d4c44ef08c2e8284f7441a2d/b2661333916f4f86b5b08da0ebce2fae
Link to samples for champion scenarios: https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/formrecognizer/Azure.AI.FormRecognizer/samples

Python

Upload the api as a Draft PR.  Link to PR: https://apiview.dev/Assemblies/Review/36ac7c8c633d4bf6a45ee8672243f195
Link to samples for champion scenarios: https://github.com/Azure/azure-sdk-for-python/tree/master/sdk/formrecognizer/azure-ai-formrecognizer/samples

Champion Scenarios
A champion scenario is a use case that the consumer of the client library is commonly expected to perform.  Champion scenarios are used to ensure the developer experience is exemplary for the common cases.  You need to show the entire code sample (including error handling, as an example) for the champion scenarios.
Recognize and extract field values from custom forms

Target audience: LOB developers (~90%)
Code samples: .NET | Python

Recognize and extract field values from US Receipts

Target audience: Day 0 developers, LOB developers (~30%)
Code samples: .NET | Python

Recognize and extract OCR Content and Tables from Forms

Target audience: LOB developers (~20%)
Code samples: .NET | Python

Train a model from custom forms

Target audience: Data Scientists (~50%)
Code samples: .NET | Python

Manage custom models

Target audience: Data Scientists (~50%)
Code samples: .NET | Python

Agenda for the review
A board review is generally split into two parts, with additional meetings as required
Part 1 - Introducing the board to the service:

Review of the service (no more than 10 minutes).
Review of the champion scenarios.
Get feedback on the API patterns used in the champion scenarios.

After part 1, you may schedule additional meetings with architects to refine the API and work on implementation.
Part 2 - the "GA" meeting

Scheduled at least one week after the APIs have been uploaded for review.
Will go over controversial feedback from the line-by-line API review.
Exit meeting with concrete changes necessary to meet quality bar.

Thank you for your submission

Action items
.Net
CustomFormModel properties

Remove RequestedOn and rename completedOn
(one proposal: trainingCompletedOn, trainingRequestedOn)

Useful to have createdOn property exposed and training duration

recognizeOptions param

Understand how will API work in containerized scenario

StartRecognizeContentFromUri(Uri, formUrl)

Change to formUri

Look into overload or different names for StartRecognizeContent and StartRecognizeContentFromUri

Python

FormField: check to see if there's formfields that aren't texts

Sample: method ConvertStringField() should throw exception instead of returning null when FieldValueType is not a string


fix(workflows): fix loops queries

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1042  👈
#1041
#1040
#1039
#1038
#1037
#1034
#1033
#1032
main

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

Join @MasterPtato and the rest of your teammates on  Graphite


buildkite-agent: 2.6.6 -> 2.6.9

Motivation for this change
Various upstream bug fixes.
https://github.com/buildkite/agent/releases/tag/v2.6.7
https://github.com/buildkite/agent/releases/tag/v2.6.8
https://github.com/buildkite/agent/releases/tag/v2.6.9
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

@GrahamcOfBorg build buildkite-agent

Failure on aarch64-linux (full log)
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/k72r4m0waz14jk00gbxblkbqzi8fhzyx-buildkite-agent-2.6.9-bin
shrinking /nix/store/k72r4m0waz14jk00gbxblkbqzi8fhzyx-buildkite-agent-2.6.9-bin/bin/.buildkite-agent-wrapped
strip is /nix/store/skd6ix5ipkyhxzq7naylj4digawakl4j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/k72r4m0waz14jk00gbxblkbqzi8fhzyx-buildkite-agent-2.6.9-bin/libexec  /nix/store/k72r4m0waz14jk00gbxblkbqzi8fhzyx-buildkite-agent-2.6.9-bin/bin
patching script interpreter paths in /nix/store/k72r4m0waz14jk00gbxblkbqzi8fhzyx-buildkite-agent-2.6.9-bin
checking for references to /build in /nix/store/k72r4m0waz14jk00gbxblkbqzi8fhzyx-buildkite-agent-2.6.9-bin...
wrapper script /nix/store/k72r4m0waz14jk00gbxblkbqzi8fhzyx-buildkite-agent-2.6.9-bin/bin/buildkite-agent contains a forbidden reference to /build
builder for '/nix/store/45yf2sj3vzzd323brq14hqcfrnv69b4g-buildkite-agent-2.6.9.drv' failed with exit code 1
error: build of '/nix/store/45yf2sj3vzzd323brq14hqcfrnv69b4g-buildkite-agent-2.6.9.drv' failed

Failure on x86_64-linux (full log)
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/gbjf94zhl8ldza3fij9cj0m723n08gdn-buildkite-agent-2.6.9-bin
shrinking /nix/store/gbjf94zhl8ldza3fij9cj0m723n08gdn-buildkite-agent-2.6.9-bin/bin/.buildkite-agent-wrapped
strip is /nix/store/adidfx4pa7vmvby0gjqqmiwg2x49yr27-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/gbjf94zhl8ldza3fij9cj0m723n08gdn-buildkite-agent-2.6.9-bin/libexec  /nix/store/gbjf94zhl8ldza3fij9cj0m723n08gdn-buildkite-agent-2.6.9-bin/bin
patching script interpreter paths in /nix/store/gbjf94zhl8ldza3fij9cj0m723n08gdn-buildkite-agent-2.6.9-bin
checking for references to /build in /nix/store/gbjf94zhl8ldza3fij9cj0m723n08gdn-buildkite-agent-2.6.9-bin...
wrapper script /nix/store/gbjf94zhl8ldza3fij9cj0m723n08gdn-buildkite-agent-2.6.9-bin/bin/buildkite-agent contains a forbidden reference to /build
builder for '/nix/store/2cx91saqhij3h3ig50drvvhm4v0sw5zr-buildkite-agent-2.6.9.drv' failed with exit code 1
error: build of '/nix/store/2cx91saqhij3h3ig50drvvhm4v0sw5zr-buildkite-agent-2.6.9.drv' failed

cc @rvl

On my machine:
checking for references to /tmp/nix-build-buildkite-agent-2.6.9.drv-0 in /nix/store/9pzysxn3jzrqj8gnjbrbvh3v6i2m79jk-buildkite-agent-2.6.9...

I think it might be finding /build due to the name of this package.

Success on x86_64-darwin (full log)
Partial log (click to expand)
/nix/store/l5a2qvkx78rpfl24p350x9fil65scyh9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/scripts/utils/publish-debian-package.sh: interpreter directive changed from "/bin/bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/l5a2qvkx78rpfl24p350x9fil65scyh9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/templates/0.2/bootstrap.sh: interpreter directive changed from "/bin/bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/l5a2qvkx78rpfl24p350x9fil65scyh9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/templates/1.0-beta.1-6/bootstrap.sh: interpreter directive changed from "/bin/bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/l5a2qvkx78rpfl24p350x9fil65scyh9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/templates/bootstrap.sh: interpreter directive changed from "/bin/bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/l5a2qvkx78rpfl24p350x9fil65scyh9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/github.com/kr/pty/mktypes.bash: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/l5a2qvkx78rpfl24p350x9fil65scyh9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/golang.org/x/sys/unix/mkall.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/l5a2qvkx78rpfl24p350x9fil65scyh9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/golang.org/x/sys/unix/mkerrors.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/l5a2qvkx78rpfl24p350x9fil65scyh9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/google.golang.org/grpc/codegen.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/l5a2qvkx78rpfl24p350x9fil65scyh9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/google.golang.org/grpc/coverage.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/m60222dzm40h03n3jmydrzqj1f5wv2ii-buildkite-agent-2.6.9-bin

@GrahamcOfBorg build buildkite-agent

Success on x86_64-linux (full log)
Partial log (click to expand)
/nix/store/1zg8z695wb5g1zjdpbjwg04l62p8s0y9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/scripts/utils/publish-debian-package.sh: interpreter directive changed from "/bin/bash" to "/nix/store/fcxliihmhm2ak9z4890gk0qw63zsbrcx-bash-4.4-p12/bin/bash"
/nix/store/1zg8z695wb5g1zjdpbjwg04l62p8s0y9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/templates/0.2/bootstrap.sh: interpreter directive changed from "/bin/bash" to "/nix/store/fcxliihmhm2ak9z4890gk0qw63zsbrcx-bash-4.4-p12/bin/bash"
/nix/store/1zg8z695wb5g1zjdpbjwg04l62p8s0y9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/templates/1.0-beta.1-6/bootstrap.sh: interpreter directive changed from "/bin/bash" to "/nix/store/fcxliihmhm2ak9z4890gk0qw63zsbrcx-bash-4.4-p12/bin/bash"
/nix/store/1zg8z695wb5g1zjdpbjwg04l62p8s0y9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/templates/bootstrap.sh: interpreter directive changed from "/bin/bash" to "/nix/store/fcxliihmhm2ak9z4890gk0qw63zsbrcx-bash-4.4-p12/bin/bash"
/nix/store/1zg8z695wb5g1zjdpbjwg04l62p8s0y9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/github.com/kr/pty/mktypes.bash: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/fcxliihmhm2ak9z4890gk0qw63zsbrcx-bash-4.4-p12/bin/bash"
/nix/store/1zg8z695wb5g1zjdpbjwg04l62p8s0y9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/golang.org/x/sys/unix/mkall.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/fcxliihmhm2ak9z4890gk0qw63zsbrcx-bash-4.4-p12/bin/bash"
/nix/store/1zg8z695wb5g1zjdpbjwg04l62p8s0y9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/golang.org/x/sys/unix/mkerrors.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/fcxliihmhm2ak9z4890gk0qw63zsbrcx-bash-4.4-p12/bin/bash"
/nix/store/1zg8z695wb5g1zjdpbjwg04l62p8s0y9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/google.golang.org/grpc/codegen.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/fcxliihmhm2ak9z4890gk0qw63zsbrcx-bash-4.4-p12/bin/bash"
/nix/store/1zg8z695wb5g1zjdpbjwg04l62p8s0y9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/google.golang.org/grpc/coverage.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/fcxliihmhm2ak9z4890gk0qw63zsbrcx-bash-4.4-p12/bin/bash"
/nix/store/1m5iy7yhnl69prz4kfqz96819xm8g0z0-buildkite-agent-2.6.9-bin

Success on aarch64-linux (full log)
Partial log (click to expand)
/nix/store/admhlpzq990wjhviv605libbpz9macz9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/scripts/utils/publish-debian-package.sh: interpreter directive changed from "/bin/bash" to "/nix/store/shjmvsnwrlg7rd8m0kzgpygqq4if312z-bash-4.4-p12/bin/bash"
/nix/store/admhlpzq990wjhviv605libbpz9macz9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/templates/0.2/bootstrap.sh: interpreter directive changed from "/bin/bash" to "/nix/store/shjmvsnwrlg7rd8m0kzgpygqq4if312z-bash-4.4-p12/bin/bash"
/nix/store/admhlpzq990wjhviv605libbpz9macz9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/templates/1.0-beta.1-6/bootstrap.sh: interpreter directive changed from "/bin/bash" to "/nix/store/shjmvsnwrlg7rd8m0kzgpygqq4if312z-bash-4.4-p12/bin/bash"
/nix/store/admhlpzq990wjhviv605libbpz9macz9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/templates/bootstrap.sh: interpreter directive changed from "/bin/bash" to "/nix/store/shjmvsnwrlg7rd8m0kzgpygqq4if312z-bash-4.4-p12/bin/bash"
/nix/store/admhlpzq990wjhviv605libbpz9macz9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/github.com/kr/pty/mktypes.bash: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/shjmvsnwrlg7rd8m0kzgpygqq4if312z-bash-4.4-p12/bin/bash"
/nix/store/admhlpzq990wjhviv605libbpz9macz9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/golang.org/x/sys/unix/mkall.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/shjmvsnwrlg7rd8m0kzgpygqq4if312z-bash-4.4-p12/bin/bash"
/nix/store/admhlpzq990wjhviv605libbpz9macz9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/golang.org/x/sys/unix/mkerrors.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/shjmvsnwrlg7rd8m0kzgpygqq4if312z-bash-4.4-p12/bin/bash"
/nix/store/admhlpzq990wjhviv605libbpz9macz9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/google.golang.org/grpc/codegen.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/shjmvsnwrlg7rd8m0kzgpygqq4if312z-bash-4.4-p12/bin/bash"
/nix/store/admhlpzq990wjhviv605libbpz9macz9-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/google.golang.org/grpc/coverage.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/shjmvsnwrlg7rd8m0kzgpygqq4if312z-bash-4.4-p12/bin/bash"
/nix/store/3jm8wxg7yyncf2l7c7aw4v31jr1vcaxj-buildkite-agent-2.6.9-bin

Success on x86_64-darwin (full log)
Partial log (click to expand)
/nix/store/zmns68wcv616y01i82pciw5s71s53fmn-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/scripts/utils/publish-debian-package.sh: interpreter directive changed from "/bin/bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/zmns68wcv616y01i82pciw5s71s53fmn-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/templates/0.2/bootstrap.sh: interpreter directive changed from "/bin/bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/zmns68wcv616y01i82pciw5s71s53fmn-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/templates/1.0-beta.1-6/bootstrap.sh: interpreter directive changed from "/bin/bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/zmns68wcv616y01i82pciw5s71s53fmn-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/templates/bootstrap.sh: interpreter directive changed from "/bin/bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/zmns68wcv616y01i82pciw5s71s53fmn-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/github.com/kr/pty/mktypes.bash: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/zmns68wcv616y01i82pciw5s71s53fmn-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/golang.org/x/sys/unix/mkall.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/zmns68wcv616y01i82pciw5s71s53fmn-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/golang.org/x/sys/unix/mkerrors.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/zmns68wcv616y01i82pciw5s71s53fmn-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/google.golang.org/grpc/codegen.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/zmns68wcv616y01i82pciw5s71s53fmn-buildkite-agent-2.6.9/share/go/src/github.com/buildkite/agent/vendor/google.golang.org/grpc/coverage.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/bash"
/nix/store/zqvfrm30l7sn5vrvlw8m5f5g979p1bn3-buildkite-agent-2.6.9-bin


Init_options documentation was written with malice

I wear an hour trying to figure out why this is not working*:
def init_options(self):
    self.options['createSearchChoice'] = 'Your_js_function'

http://django-select2.readthedocs.org/en/latest/ref_widgets.html#django_select2.widgets.Select2Mixin.init_options

This documentation is a lie. According to that, putting a function in that way should work. In fact, in order for the function to work, you must put it this way:
    def init_options(self):
        self.options['createSearchChoice'] = '*START*Your_js_function*END*'

createSearchChoice should always be a function. In the example, a string is returned.
Sorry, I have the crystal ball in the workshop to read the Select2 documentation.

What are you trying to do? I don't really get your point?

Just to note anyone else using the latest version 4, that this bug is correct. The commit that changed this is 36bac0570f6e1c16d27980f8b06ea8e91b9cefd2 – you can see there that the documentation for e.g. HeavySelect2TagWidget changes JSFunctionInContext('django_select2.createSearchChoice') to django_select2.createSearchChoice but the code changes JSFunctionInContext('django_select2.createSearchChoice') to *START*django_select2.createSearchChoice*END*. You need those START/END in order for the string to not be escaped when passed to the browser, as you can see at https://github.com/applegrew/django-select2/commit/36bac0570f6e1c16d27980f8b06ea8e91b9cefd2#diff-ef58fc8cd3b94144380352baed83bbe5R219
As to what we are trying to do – we have a widget that has server-side auto complete plus allows you to add a new entry if not present (e.g. like what #4 wanted); plus AutoHeavySelect2Mixin's init hard coded data_view but we needed a Django namespace, so we work around that. It worked fine in 4.2.2 but broke when upgraded to 4.3.2 before this was spotted.

@dracos updating to version 5 took me less than an hour in a 100kloc Django project. I must highly recommend it, for there is no more support for version 4.


GitVersionControlSystem. getAvailableVersions() should include heads as well as tags

Expected Behavior
Given a Git repository with various tags and a master branch several commits ahead of those tags, it should be possible to reference the master branch as a source dependency, e.g. {organization}:{artifact}:master
Current Behavior
Only tags are available as artifact versions. Attempting to build against masterproduces the error:
FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':war'.
> Could not resolve all task dependencies for configuration ':runtimeClasspath'.
   > Could not find any version that matches {organization}:{artifact}:master.
     Searched in the following locations:
       - Git repository at {repo}
     Required by:
         project :

The proximate cause seems to be a ModuleVersionResolveException thrown in VcsDependencyResolver, but the underlying cause is this line in GitVersionControlSystem.getAvailableVersions(), which passes heads=false to getRemoteRefs().
Context
I can't use the development version of a project as a dependency.
Steps to Reproduce

Fork the repository https://github.com/NCEAS/ezid.
Clone the fork and run gradle init --type pom.
Commit and push the changes to the fork.
In a Gradle Java project:

in build.gradle, add compile 'edu.ucsb.nceas:ezid:master' as a dependency

in settings.gradle, add:
sourceControl {
  gitRepository({HTTP URL for the fork}) {
    producesModule("edu.ucsb.nceas:ezid")
  }
}

run gradle build

Note: You can work around this by tagging the master head revision and moving the tag when it changes, but that goes against the spirit of Git tags.

Fixed typo in original report — I'd typed git init when I meant gradle init.

@adammurdoch looking at the history of GitVersionControlSystem.getAvailableVersions(), it seems like this was disabled deliberately in 6d600ee in January 2018 (and then refactored later that year in e50e6ce).

Changed source dependency resolution to match only tags, rather than all references such as branches, when selecting a version.
This removes the accidental support for declaring a dependency on a branch, pending an actual implementation.

Was there a problem with the "accidental support" for branch dependencies, and is there another feature request for it somewhere?

@adammurdoch do you remember what the issue was with branch dependencies?

According to the blog article introducing source dependencies, the following should do what you want:
dependencies {
    compile 'edu.ucsb.nceas:ezid' {
        version {
            branch = 'master'
        }
    }
}

(Haven't tested it myself)


chore: promote test15 to version 0.0.9

chore: promote test15 to version 0.0.9
this commit will trigger a pipeline to generate the actual kubernetes resources to perform the promotion which will create a second commit on this Pull Request before it can merge

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign q1323829945
You can assign the PR to them by writing /assign @q1323829945 in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@q1323829945: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

verify
55e8b320c03dd617542689fdeb97ef1965b8b3fd
link
/test verify

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


[DOCFIX] Update doc: docs/_data/table/en/ReadType.yml of the Chinese version

Update doc: docs/_data/table/en/ReadType.yml of the Chinese version

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/13445/
Test PASSed.


Fix link preview size

Details
Size of link previews was very big, this PR reduces it for both mobiles and desktops.
Fixed Issues

$ https://github.com/Expensify/App/issues/23179
PROPOSAL: https://github.com/Expensify/App/issues/23179#issuecomment-1642264461
Tests

You can use the following links to compare the size of link previews - facebook.com, youtube.com, cnn.com.

Send one or more of the links above in a chat.
Open the same chat on testing environment (staging for QA) and on prod (new.expensify.com).
Compare the size of link previews in testing and prod environment, size of preview should be lesser now.
Here is the exact change in size -
Before -
Large screen (web/desktop app) - max width = 350px, max height = 350px
Small screen (apps/browsers) - max width = 180px, max height = 180px but this was only being applied on browser (chrome/safari) and not on apps because of wrong logic in code
After -
Large screen (web/desktop app) - max width = 240px, max height = 240px
Small screen (apps/browsers) - max width = 340px, max height = 180px now applied on both browsers (chrome/safari) and apps

[x] Verify that no errors appear in the JS console

Offline tests

Same as above.
QA Steps

Same as above.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
Before followed by after

Mobile Web - Chrome
Before followed by after - Here, mobile styles were being applied before as well, CNN preview was smaller because, max width was smaller (180px) and image also maintains the aspect ratio. Now, we have increased max width to 340px on mobile, so height is also allowed to be more (still less than max height 180px though).

Mobile Web - Safari
Before followed by after - Here, mobile styles were being applied before as well

Desktop
Before followed by after -

iOS
Before followed by after - Image also maintains the aspect ratio which also affects the width, height. See the formula.

Android
Before followed by after -

Thanks for spinning this up! So after seeing this, I feel like we might want to make the max-height on desktop even smaller. Perhaps we just go with what mobile has at 180?

Nice, let's do that then. Thanks for being flexible here!

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/dangrous in version: 1.3.50-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/puneetlath in version: 1.3.50-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/dangrous in version: 1.3.51-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.51-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Separate chain calls

Q
A

Readability fix
according to https://github.com/yiisoft/docs/issues/155, chain calls must be put on separate lines.

Thanks but not applicable anymore and hurts readability in this case.


[IRGen] Simplify createGOTEquivalent().

Make this function take a LinkEntity describing what we're creating a GOT
entry for, to simplify callers a bit.
Fixes rdar://problem/45789091

@swift-ci please test and merge


Debug chroot

debuggin

what the hell

Out of curiosity, anything I messed up?

Best I can tell, no. Must be some weird GHA thing


Feature editor

Test URLs:

https://feature-editor--henkel-raqn-guide--felipesimoes.hlx.page/web-guide/en/

Closed


Internal Error Query Proposals - Address Does Not Exist

Issue type
Internal error quering proposals and address does not exist error if I try to vote.
Akash version

0.6.1 (note the above command should be 'akashd version' - at least on my system anyway.)
Akash token balance

[
{
"name": "SkyNet",
"type": "local",
"address": "akash1z5xmrfmxy8kw5l5f0cu9s96qc7v7pu7q3pmv7h",
"pubkey": "akashpub1addwnpepqfg8e06m0zkzndmxh5v7h3hepenpzq2jqq2vv0wdlry62w40dk69q374a6t"
},
{
"name": "master",
"type": "local",
"address": "akash1g9ny5klw83a0r3kzvd6xmlhntq9qeyjulq2xck",
"pubkey": "akashpub1addwnpepq2zsnzc9r8tv9pgdjvlwu2hsn2ug6ef6hkc8h94f2c403yhkj46j5u2kd8u"
}
]
The second command resulted in the following error:
akashctl query account SkyNet
ERROR: decoding bech32 failed: invalid bech32 string length 6
What happened
I ran the following commands with the following errors:
akashctl query gov proposal 3 --chain-id centauri -o json
ERROR: internal error
akashctl query gov votes 3 --chain-id centauri -o json
ERROR: failed to fetch proposal-id 3: internal error
akashctl tx gov vote 3 abstain --chain-id centauri --from SkyNet
Enter keyring passphrase:
ERROR: unknown address: account akash1z5xmrfmxy8kw5l5f0cu9s96qc7v7pu7q3pmv7h does not exist
What did you expect to happen
To be able to query the proposals and vote
How to reproduce it

Run the above three commands
Environment

akashd (server) <- I don't understand what to do.  I configured for testnet on my MPS server
ubuntu <IP_ADDRESS>
Anything else we need to know?

Next steps
You may join developer chat for community support.

I have since found the solution.


static height removed

Overview
Static heights removed and.
Scroll area adjustmets.
Feature relevant tickets
AF-155

Checklist before submitting

[ ] Meaningful commits and code rebased on develop.
[ ] Update CHANGELOG
[ ] If this PR adds feature that should be tested for regressions when
deploying to staging/production, please add brief testing instructions
to the deploy checklist

There are some problem when decrease the height of the screen:

Also, in all scroll areas except in the project list one, there are a space extra in the scroll bar:


@ character inputted both on keyDown and keyUp in TextField (OS X, AZERTY layout)

Issue details
On OS X, using AZERTY layout (@ key is just under Escape key), when writing into a TextField, the "@" character gets written both when the key is pressed and when it's released. It also happens with "#", which is on the same key (need to press the shift modifier to write it).
Note : this doesn't happen with LWJGL 3, only with version 2, but I felt it would be worth creating an issue for it as it seems LWJGL isn't 100% supported yet for libgdx.
The key is there : https://cdn.discordapp.com/attachments/348552152387551244/586096396021792768/20190606_093726.jpg
Reproduction steps/code
Will happen in any TextField on OS X using AZERTY layout.
Version of LibGDX and/or relevant dependencies
1.9.9
LWJGL version 2
Please select the affected platforms

[ ] Android
[ ] iOS (robovm)
[ ] iOS (MOE)
[ ] HTML/GWT
[ ] Windows
[ ] Linux
[X] MacOS

I guess that this is a LWGL2 Problem and not related to how libGDX handles the received input.
If this is the case you are probably out of luck, since LWJGL2 is EOL.

You will likely need to look into what you can do to fix this in the lwjgl2 backend. I don't use Mac and don't usually work on Mac specific bugs. If you provide a fix I can test that Windows is still working right.

LWJGL2 is getting old and no longer maintained. Consider using LWJGL3, if possible.


MIoU on Pascal VOC is about 0.7 with 50 epoches

Thank you for your sharing.
I have tried to retrain the model on Pascal VOC dataset, but the miou is only about 0.7 after 50 epoches and it hardly increased, may I know is it correct? or should I continue the training for 160 epoches?

Our model converged by epoch 64.
Either let it run a little bit more or try again.

Thank you for your reply and help, I rerun it again and the results seems better. I don't understand the printed logger information on the "bench", e.g., ... bench: [iou: 0.8000 (0.7500); ] ..., so, which value is the MIoU?

The first value is the mIoU. The second value is the average over the entire epoch (if the first value is higher than the second value it means the model is improving).


Request: Document Recommendations for missing vim-sexp mappings

Thanks for all your work on this plugin!
I see in #49 and #53 that nvim-paredit isn't intended to be a drop-in replacement for vim-sexp. However, I suspect this is still how most users will see it, so I suggest being a bit more explicit about this in the README.
In particular, as a user I'd really appreciate a list of all the vim-sexp features that nvim-paredit doesn't include and some recommendations on how to replicate them.
I think this is a complete list of what's missing:

sexp_flow_to_prev_close
sexp_flow_to_next_open
sexp_flow_to_prev_open
sexp_flow_to_next_close
sexp_flow_to_prev_leaf_head
sexp_flow_to_next_leaf_head
sexp_flow_to_prev_leaf_tail
sexp_flow_to_next_leaf_tail
sexp_move_to_prev_top_element
sexp_move_to_next_top_element
sexp_select_prev_element
sexp_select_next_element
sexp_indent
sexp_indent_top
sexp_insert_at_list_head
sexp_insert_at_list_tail
sexp_convolute

Let me know what you think, and thanks again.

Sorry for taking so long to reply!

Thanks for all your work on this plugin!

You are welcome :)

Yes fair enough I think this is probably a good idea. I don't think I'll have the time to really document ways to replicate these behaviours as they aren't really features I personally use - but I would be happy to accept contributions to that effect.
In the interim I'd be happy to include this list in docs. I plan to do some work on this plugin in the coming weeks and can address this partially then.


Infinite reload with differentDomains: true

Version
@nuxtjs/i18n: 8.0.0-alpha.3
nuxt: 3.0.0-rc.11
Nuxt configuration

[ ] Applies to a site deployed to a static server (site generated with nuxt generate)
[x] Applies to a site deployed to a server with a Node backend

@nuxtjs/i18n configuration
i18n: {
        locales: [
            {
              code: 'en',
              domain: mydomain.com
            },
            {
              code: 'fr',
              domain: mydomain.fr
            }
        ],
        differentDomains: true,
        defaultLocale: 'fr',
        vueI18n: {
            legacy: false,
            locale: 'fr',
            messages: {
                en: {
                    welcome: 'Welcome'
                },
                fr: {
                    welcome: 'Bienvenue'
                }
            }
        }
    }

Steps to reproduce
I use pm2 to manage the app execution.
Set differentDomains: true in i18n config, run yarn build, and launch app with pm2. Access the app via FR or EN domain, the refresh loop begins.
When differentDomains is set to false, the issue doesn't appear.
In the doc I see "// TODO: 🚧 This feature is not implemented yet.", but it seems working because when I access app with FR or EN domain, my content is in correct language, but the refresh loop make the UI unusable.
Thanks.

detectBrowserLanguage: false can help you until they will fix

Unfortunately, this setting doesn't change anything, refresh loop persists.

Seeing the same thing - already have detectBrowserLanguage: false

sorry, for late reply.
Unfortunately, I could not reproduce this issue in v8.0.0-beta.2 😞
Could you give us to your reproduction repo with github repo or stackblitz please? 🙏
And We hope you would like to try to use v8.0.0-beta.2, wheather this issue will be reproduced

@kazupon still seeing this in beta 3
This is my config:
  i18n: {
    strategy: 'no_prefix',
    differentDomains: true,
    detectBrowserLanguage: false,
    baseUrl: process.env.LOCALE === 'de' ? process.env.SITEURL_DE : process.env.SITEURL,
    locales: [
      {
        name: 'nederlands',
        code: 'nl',
        iso: 'nl-NL',
        file: 'nl.json',
        domain: process.env.SITEURL,
      },
      {
        name: 'deutsch',
        code: 'de',
        iso: 'de-DE',
        file: 'de.json',
        domain: process.env.SITEURL_DE,
      },
    ],
    langDir: 'assets/i18n/',
    defaultLocale: process.env.LOCALE,
    lazy: true,
  },

Same problem

This is my config.
Doesn't work with both detectBrowserLanguage: {...} and detectBrowserLanguage: false
export default defineNuxtConfig({
  modules: ['@nuxtjs/i18n'],
  i18n: {
    locales: [
      {
        code: 'en',
        domain: 'mysite.test:3000',
      },
      {
        code: 'de',
        domain: 'mysite.testde:3000',
      },
    ],
    trailingSlash: true,
    differentDomains: true,
    defaultLocale: 'en',
    strategy: 'prefix_and_default',
    detectBrowserLanguage: false,
    // detectBrowserLanguage: {
    //   useCookie: false,
    //   redirectOn: 'root',
    //   fallbackLocale: 'en',
    //   // alwaysRedirect: true,
    // },
    vueI18n: {
      legacy: false,
      messages: {
        en: {
          welcome: 'Welcome',
        },
        de: {
          welcome: 'Willkommen',
        },
      },
    },
  },
})

I've just released<EMAIL_ADDRESS>edge version
I believe this issue is fixed.
you can try to use it.

Thank you @kazupon
It works perfectly

@maxsolovev what is your config? Same as above? For me the redirect loop persists.

Yes, it's same. But there were problems with routing.
screencast


Change mobs to not drop items if they die by suffocation

Will this apply to player suffocation for consistency?

I believe a better solution would be making wild animals panic after being pushed.


FLPATH-431: Delete Tibco

What this PR does / why we need it:
At the moment isn't possible to get Tibco dependency from Maven Central.
The current implementation follows official Tibco doc .
To fix FLPATH-431 this commit deletes dependency and code related to Tibco.
Once we'll find a solution, this commit can be reverted.
Fixes # FLPATH-431
Change type

[ ] New feature
[x] Bug fix
[ ] Unit tests
[ ] Integration tests
[ ] CI
[ ] Documentation
[ ] Auto-generated SDK code

Impacted services

[x] Workflow Service
[ ] Notification Service

Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.

@lshannon @RichardW98 @masayag can you please review this PR?
Are the changes what you expected?

/lgtm

/approve


Clicking on Your Plan doesn't show the enrolled plans

Added an enrollment page and a dynamic progress bar as well


Hello_Queue_Function_Test is failing

Test Name:	FunctionApp.IntegrationTest.Tests.HelloQueueFunctionTest.Hello_Queue_Function_Test
Test FullName:	FunctionApp.IntegrationTest.Tests.HelloQueueFunctionTest.Hello_Queue_Function_Test
Test Source:	C:\CODE\POC\AzureFunctionsV2IntegrationTest\src\FunctionApp.IntegrationTest\Tests\HelloQueueFunctionTest.cs : line 28
Test Outcome:	Failed
Test Duration:	0:00:21.821
Result StackTrace:
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at FunctionApp.IntegrationTest.Tests.HelloQueueFunctionTest.When_The_HelloQueue_Function_Is_Invoked() in C:\CODE\POC\AzureFunctionsV2IntegrationTest\src\FunctionApp.IntegrationTest\Tests\HelloQueueFunctionTest.cs:line 42
at TestStack.BDDfy.Processors.AsyncTestRunner.Run(Func`1 performStep)
at TestStack.BDDfy.Processors.ScenarioExecutor.ExecuteStep(Step step)
at TestStack.BDDfy.Processors.ExceptionProcessor.Process(Story story)
at TestStack.BDDfy.Engine.Run()
at TestStack.BDDfy.BDDfyExtensions.BDDfy(Object testObject, String scenarioTitle, String caller)
at FunctionApp.IntegrationTest.Tests.HelloQueueFunctionTest.Hello_Queue_Function_Test() in C:\CODE\POC\AzureFunctionsV2IntegrationTest\src\FunctionApp.IntegrationTest\Tests\HelloQueueFunctionTest.cs:line 30
Result Message:	System.Net.Http.HttpRequestException : Response status code does not indicate success: 500 (Internal Server Error).
Is there a step needed to run this?
The function is working fine.
Tx

Hi @lcpautotester, can you please pull the repo changes and try again?
I have added a local.settings.json file into the repository, with references to the Azure Storage emulator. Assuming you run the storage emulator when you run the test, this should hopefully resolve your issue.
If it still doesn't work, then please note this repo has been published as an accompaniment to this blog post. Please check the post to make sure you are following all the steps in there, and also confirm you have installed the Azure Functions core tools into your global NPM scope by using the command npm install -g azure-functions-core-tools.


Fix pylance errors

[ ] func type is broken: https://github.com/demergent-labs/kybra/issues/229
[x] Stub file not found for "kybra" on the main Kybra import

Essentially a duplicate of https://github.com/demergent-labs/kybra/issues/229