Type specification/inferrence now fails in @jax.jit

Please:

[x] Check for duplicate issues.
[x] Provide a complete example of how to reproduce the bug, wrapped in triple backticks like this:

The following test case has worked for a while, but has recently started failing. It seems to stem from the specification of concrete types np.complex64 and the use of type inference within the function np.result_type(lm, uvw, frequency, np.complex64).
import numpy as np
import jax
import jax.numpy as jnp

@jax.jit
def phase_delay(lm, uvw, frequency):
    out_dtype = jnp.result_type(lm, uvw, frequency, np.complex64)

    one = lm.dtype.type(1.0)
    neg_two_pi_over_c = lm.dtype.type(-2*np.pi/3e8)
    complex_one = out_dtype.type(1j)

    l = lm[:, 0, None, None]  # noqa
    m = lm[:, 1, None, None]

    u = uvw[None, :, 0, None]
    v = uvw[None, :, 1, None]
    w = uvw[None, :, 2, None]

    n = jnp.sqrt(one - l**2 - m**2) - one

    real_phase = (neg_two_pi_over_c *
                  (l * u + m * v + n * w) *
                  frequency[None, None, :])

    return jnp.exp(complex_one*real_phase)

if __name__ == "__main__":
    uvw = np.random.random(size=(100, 3)).astype(np.float32)
    lm = np.random.random(size=(10, 2)).astype(np.float32)*0.001
    frequency = np.linspace(.856e9, .856e9*2, 64).astype(np.float32)

    complex_phase = phase_delay(lm, uvw, frequency)```

[x] If applicable, include full error messages/tracebacks.

$ python test_complex_constant_fail.py
WARNING:absl:No GPU/TPU found, falling back to CPU. (Set TF_CPP_MIN_LOG_LEVEL=0 and rerun for more info.)
Traceback (most recent call last):
  File "test_complex_constant_fail.py", line 32, in <module>
    complex_phase = phase_delay(lm, uvw, frequency)
  File "/home/sperkins/venv/afr/lib/python3.7/site-packages/jax/_src/traceback_util.py", line 165, in reraise_with_filtered_traceback
    return fun(*args, **kwargs)
  File "/home/sperkins/venv/afr/lib/python3.7/site-packages/jax/_src/api.py", line 429, in cache_miss
    donated_invars=donated_invars, inline=inline)
  File "/home/sperkins/venv/afr/lib/python3.7/site-packages/jax/core.py", line 1671, in bind
    return call_bind(self, fun, *args, **params)
  File "/home/sperkins/venv/afr/lib/python3.7/site-packages/jax/core.py", line 1683, in call_bind
    outs = top_trace.process_call(primitive, fun, tracers, params)
  File "/home/sperkins/venv/afr/lib/python3.7/site-packages/jax/core.py", line 596, in process_call
    return primitive.impl(f, *tracers, **params)
  File "/home/sperkins/venv/afr/lib/python3.7/site-packages/jax/_src/dispatch.py", line 143, in _xla_call_impl
    *unsafe_map(arg_spec, args))
  File "/home/sperkins/venv/afr/lib/python3.7/site-packages/jax/linear_util.py", line 272, in memoized_fun
    ans = call(fun, *args)
  File "/home/sperkins/venv/afr/lib/python3.7/site-packages/jax/_src/dispatch.py", line 170, in _xla_callable_uncached
    *arg_specs).compile().unsafe_call
  File "/home/sperkins/venv/afr/lib/python3.7/site-packages/jax/_src/profiler.py", line 206, in wrapper
    return func(*args, **kwargs)
  File "/home/sperkins/venv/afr/lib/python3.7/site-packages/jax/_src/dispatch.py", line 198, in lower_xla_callable
    fun, abstract_args, pe.debug_info_final(fun, "jit"))
  File "/home/sperkins/venv/afr/lib/python3.7/site-packages/jax/_src/profiler.py", line 206, in wrapper
    return func(*args, **kwargs)
  File "/home/sperkins/venv/afr/lib/python3.7/site-packages/jax/interpreters/partial_eval.py", line 1623, in trace_to_jaxpr_final
    jaxpr, out_avals, consts = trace_to_subjaxpr_dynamic(fun, main, in_avals)
  File "/home/sperkins/venv/afr/lib/python3.7/site-packages/jax/interpreters/partial_eval.py", line 1594, in trace_to_subjaxpr_dynamic
    ans = fun.call_wrapped(*in_tracers_)
  File "/home/sperkins/venv/afr/lib/python3.7/site-packages/jax/linear_util.py", line 166, in call_wrapped
    ans = self.f(*args, **dict(self.params, **kwargs))
  File "test_complex_constant_fail.py", line 19, in phase_delay
    n = np.sqrt(one - l**2 - m**2) - one
  File "/home/sperkins/venv/afr/lib/python3.7/site-packages/jax/core.py", line 452, in __array__
    raise TracerArrayConversionError(self)
jax._src.traceback_util.UnfilteredStackTrace: jax._src.errors.TracerArrayConversionError: The numpy.ndarray conversion method __array__() was called on the JAX Tracer object Traced<ShapedArray(float32[10,1,1])>with<DynamicJaxprTrace(level=0/1)>
While tracing the function phase_delay at test_complex_constant_fail.py:4 for jit, this concrete value was not available in Python because it depends on the value of the argument 'lm'.
See https://jax.readthedocs.io/en/latest/errors.html#jax.errors.TracerArrayConversionError

The stack trace below excludes JAX-internal frames.
The preceding is the original exception that occurred, unmodified.

--------------------

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "test_complex_constant_fail.py", line 32, in <module>
    complex_phase = phase_delay(lm, uvw, frequency)
  File "test_complex_constant_fail.py", line 19, in phase_delay
    n = np.sqrt(one - l**2 - m**2) - one
jax._src.errors.TracerArrayConversionError: The numpy.ndarray conversion method __array__() was called on the JAX Tracer object Traced<ShapedArray(float32[10,1,1])>with<DynamicJaxprTrace(level=0/1)>
While tracing the function phase_delay at test_complex_constant_fail.py:4 for jit, this concrete value was not available in Python because it depends on the value of the argument 'lm'.
See https://jax.readthedocs.io/en/latest/errors.html#jax.errors.TracerArrayConversionError

Closing this as I'm now unsure of the source of error. I'll re-open a new issue as I dig further

Thanks for the report. I can reproduce with jaxlib 0.1.76; the jax version doesn't appear to matter.

Shorter repro:
import numpy as np
import jax
import jax.numpy as jnp

@jax.jit
def f():
  return jnp.exp(np.complex64(1j))
f()

I think the issue is that complex dtypes were left out of the list here: https://github.com/google/jax/blob/0382a6a04eddd7506a4ef6bb0c93f0f660ee3df6/jax/interpreters/mlir.py#L243-L247

We're going to make a jax release very shortly incorporating this fix.

We're going to make a jax release very shortly incorporating this fix.

Thanks for the quick turnaround!


Bump immutable collections and objectpool packages to 8.0.0

It turns out that our System.Immutable.Collections package version was already bumped to 8.0.0 with the Roslyn update. This PR bumps our pinned version of System.Immutable.Collections to match, and also bumps Microsoft.Extensions.ObjectPool.

I believe this still needs a review from someone in @dotnet/source-build-internal.

Thanks all!


feat: adds Game Servers realm and cluster operations

[This PR is not ready for review yet--the unit tests fail.]

C# was deprioritized by product team; closing this PR.


Dockerfile / Docker Container

Hey Arey,
Hope you are doing well !
Is there any docker file available for this project in order to deploy it easily ? That would be great.
Cheers,
Luc Michalski

Hi Luc,
I've worked to a docker file and I hope that it matches to your expectation.
Any feedback is welcome.
Regards
Antoine

Amazing Antoine, that's great, I will try it today !
What would you advice to create an API explorer for faceted search ?
Sindice Siren:
https://github.com/sindicetech/siren/tree/master/siren-elasticsearch-demo/src/example/datasets

Luc, have you tried the Docker file?

Hey,
Sorry for the delay, but I was working on some other datasets ^^. I will try it, really precisely now :-)
Can we have a skype as I have a couple of questions for u ? (I am in NYC, Skype: michalski.luc)
Cheers,
Luc Michalski

Hi Luc
For my part, I leave in France. I cannot use Skype at my office. And at home I don't have much time with my kids. I'm sorry.
What are your questions?
Regards
Antoine


using pyodata to get json output structure format same as browser results

From the browser, when I access the URL https://services.odata.org/V2/Northwind/Northwind.svc/Customers?$format=json, I get the JSON response with results and _next  objects. I'm expecting to get a similar output in python v3.9 but the output format is different.
How should I pass the parameter for format=json and where, so I can get the same output structure as what the browser returns with _results field
Here's the example python script and it's response
import pyodata
import requests

SERVICE_URL = 'https://services.odata.org/V2/Northwind/Northwind.svc/Customers'

northwind = pyodata.Client(SERVICE_URL, requests.Session())

theservicedata = getattr(northwind.entity_sets, 'Customers')

data = theservicedata.get_entities().count(inline=True).execute()

for each in data:
    print(vars(each))

Sample Output
{
   "_logger":"<Logger pyodata.service (WARNING)>",
   "_service":<pyodata.v2.service.Service object at 0x7ff5fed4e8e0>,
   "_entity_set":"EntitySet(Customers)",
   "_entity_type":"EntityType(Customer)",
   "_key_props":[
      "StructTypeProperty(CustomerID)"
   ],
   "_cache":{
      "CustomerID":"ERNSH",
      "CompanyName":"Ernst Handel",
      "ContactName":"Roland Mendel",
      "ContactTitle":"Sales Manager",
      "Address":"Kirchgasse 6",
      "City":"Graz",
      "Region":"",
      "PostalCode":"8010",
      "Country":"Austria",
      "Phone":"7675-3425",
      "Fax":"7675-3426",
      "Orders":[

      ],
      "CustomerDemographics":[

      ]
   },
   "_entity_key":"(""ERNSH"")",
   "_etag":"None"
}

Hi @ashdsi
for quite easy question it is not an easy answer. It the end, it would depend on the question why exactly you want to have the JSON response from odata api at hand. I will point out some generic recommendation since there is no one good answere here.

pyodata library was created to NOT work with URLs and JSONs, but wrap odata service from its metadata as python objects api. So if your case is really to request some specific URL, get repsonse as JSON and work later with just the JSON, use a HTTP library, like requests. Pyodata is a wrapper library, so you do not need to handle exactly this in a python code working with some odata APi.
your script is dropping everything that is in the pyodata python object for the odata api response, that is not the raw JSON from the response. print(vars(each)) - this is also not quite the expected usage of pyodata.
have you read the Documentation? Generic how to query and what data to expect? For the specifics of working with _next keys, it is here - https://github.com/SAP/python-pyodata/blob/master/docs/usage/querying.rst#query-server-side-paginations-using-the-__next-field
you may also reference first the tests for the service.py module. JSON response is basically an input, which is transformed by pyodata to tree of objects, referenceable by the "dot notation".
the JSON response is within the library stored here - https://github.com/SAP/python-pyodata/blob/9f2dae53869e117d67e83ebcbe38cb8dee32f156/pyodata/v2/service.py#L141. But this is where it is store AFTER returned by the HTTP networking library of your choice, e.g. mostly Requests, like in your case. This is more important for inner workings of the library and the end API for a python programmer should be the parsed objects. Or again, probably better to use the HTTP networking library directly, if such parsed objects from JSON are for no use to you.

Hi @ashdsi
I am closing this since no response for a week and this is essentially a generic question issue.  Feel free to reopen if necessary.


Apple official documents not being translated

I can't translate Apple Developer documents.
Neither pop-ups nor the shortcut key (⌘+⇧+y) respond.
I feel like this issue could occur elsewhere as well,
but at least for now, it's not happening with anything other than Developer documents.
Version
Web Translator : Version 0.1.32
Safari : Version 17.2.1

Apple Developer Document
StackOverflow

日本語
Appleの公式ドキュメントだけ翻訳ができません。
ポップアップも、ショートカットキー(⌘+⇧+Y)でも反応しません。
他の場所でも同様の問題は発生しそうな気はしますが、
少なくとも、今のところはAppleの公式ドキュメント以外は発生していません。
バージョン
WebTranslator：Version 0.1.32
Safari Version 17.2.1

Thanks for reporting.
This is due to the Content Security Policy response header on Apple's website blocking the CSS in the extension. In fact, the translation functionality is working but is not being displayed as intended. If you scroll to the bottom of the screen after running the translation, you will find elements with no popover style applied.
This problem cannot be easily fixed as it requires replacing all CSS application with JavaScript.
Alternatively, if you use the full-text translation feature, it will work correctly since it does not use CSS.

@KaitoMuraoka Fixed in version 0.1.33 (323). Please install and check it from the TestFlight link below.
https://testflight.apple.com/join/QmZCoDZb

@kishikawakatsumi
Thank you!
I'm really happy that you addressed this issue.

It is currently working without any problems.
I'm growing even fonder of this web extension.
If anything comes up, I will provide feedback via TestFlight.
Feel free to close this Issue.


Add breadcrumbs

I’ve taken a stab at adding breadcrumbs to Primer. @mdo and the team, you guys may want to make a few changes to my implementation, but I thought I would start off the additions.

Not sure I see a need for this breadcrumb in Primer. GitHub.com has one, but it's for our file paths and likely isn't going to be added to Primer given it's limited focus.

@mdo Oh, ok. The docs had said “coming soon,” so I figured someone you guys wanted them as part of Primer and not just GH. Do you want me to close the PR then?

Oh crap, yeah, I totally forgot about that. Hmm, the main problem is that this uses the same base class as our file paths on GitHub.com, but not the same styles or sub-components. We could ship that particular breadcrumb, but it's pretty specific right now. This PR is in great shape for what it's worth—only a few minor nits on the CSS otherwise.
For now I'd say we should punt on this. I'd love a PR to remove that docs callout for now though :stuck_out_tongue_winking_eye:.

@mdo Sure thing! I’ll do that.
However, couldn’t you guys just convert GitHub’s breadcrumbs over to these (probably modifying these a bit)? I personally think it’s better to keep separators in the CSS with padding as opposed to pseudo-spaces, but that’s completely your choice.

@mdo Had totally forgot about this. If you have any interest in this, we could try to salvage it, but otherwise we should probably just :hocho: it.


[SPARK-38016][SQL][DOCS] Fix the API doc for session_window to say it supports TimestampNTZType too as timeColumn

What changes were proposed in this pull request?

This PR fixes the API docs for session_window to say it supports TimestampNTZType too as timeColumn.
Why are the changes needed?

As of Spark 3.3.0 (e858cd568a74123f7fd8fe4c3d2917a), session_window supports not only TimestampType but also TimestampNTZType.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Built the docs with the following commands.
bundle install
SKIP_RDOC=1 SKIP_SQLDOC=1 bundle exec jekyll build

Then, confirmed the built doc.

NOTE: We have a similar issue in window function too but it affects 3.2.0 too. So I'll separate the JIRA ticket and PR.

Thank you @HyukjinKwon and @dongjoon-hyun . Merging to master.


Add none type chip capability handling

#380
Add handling for None type chip capability

Sorry, I deleted my prev reply - I thought there was an issue (seg fault) but I had typo on my cmd (referencing wrong workspace systemdesc). Works good, no more error seen.  This looks a bit strange though, is it intended?
    "chip_capabilities": [
      6,
      "None"
    ],

Sorry, I deleted my prev reply - I thought there was an issue (seg fault) but I had typo on my cmd (referencing wrong workspace systemdesc). Works good, no more error seen. This looks a bit strange though, is it intended?
    "chip_capabilities": [
      6,
      "None"
    ],

Edit: Maybe lets keep this open a bit to get Nick's thoughts. Edit2: chatgpt says this bitflag enum should yield values 0,1,3 but we are seeing 6 above for some reason...
enum ChipCapability: uint32 (bit_flags) {
  None = 0,
  PCIE = 1,
  HostMMIO = 2,
}

You're seeing 6 because with this change you're bitwise or'ing 0b'10 and 0b'100 so it yields 6. If the error went away then we should keep it the way it was. Since it's a bit flag the case 0 should implicitly be handled, I'll close this merge request and issue.

Curious, what's the use of the None type?

Curious, what's the use of the None type?

Remote chips connected via ethernet.

Curious, what's the use of the None type?

Remote chips connected via ethernet.

Would it be plausible to call it something like TT_ChipCapabilityEth?

Curious, what's the use of the None type?

Remote chips connected via ethernet.

Would it be plausible to call it something like TT_ChipCapabilityEth?

Yeah that's a good idea! I'll update the name

+1 for adding an eth attribute.
But back to the core issue, does it work instead of using < and > to use [ and ].  Or we could do this instead:
let assemblyFormat = "`<` (`none` `:` $value^)? `>`";

@jnie-TT, we can close this, fixed with #402 right?

@nsmithtt that's correct, closing this.


Fix issue #184: not_null's dereference operator did not work for smart pointers with c++11

Merged, thank you.

Remember section A.3 GSL Lite test specification of the Readme :)
I made the tests prominently visible here not in the least to spread Kevlin Henney's idea to use predicates for tests. See for example Programming with GUTs by Kevlin Henney.

@martinmoene : Dangit, there was a point in time I thought about updating this, but it seems I forgot eventually. I'll fix in my next PR (which will add quite a number of new tests about unique_ptr and shared_ptr).
Is there a way to generate it automatically? I haven't really looked at the options of LEST yet.

@petamas , I've always generated and updated the list by hand, and (also) often forgot to do so :)
On Windows, I did the equivalent of
cd ...\gsl-lite\test & t.bat & gsl-lite.t.exe -l | winclip -c

and pasted the clipboard at the right spot in Readme.md
t.bat compiles with VC and produces a list of tests in the desired order, whereas tg.bat compiles with gcc and produces a list of tests that is meh.
winclip is part of the outwit tool set by Diomidis Spinellis.

Martin, thanks for bringing this up. I wondered about the list myself (and I also forgot to update it back when I added ExpectsAudit()/EnsuresAudit()).

t.bat compiles with VC and produces a list of tests in the desired order, whereas tg.bat compiles with gcc and produces a list of tests that is meh.

I guess I'll update these sometime so they use CMake rather than invoking cl/g++ directly. Oh, and add t.sh :)

winclip is part of the outwit tool set by Diomidis Spinellis.

(BTW, Windows Vista and newer comes with a built-in clipboard tool called clip. Piping text to clip puts it in the clipboard.)

(BTW, Windows Vista and newer comes with a built-in clipboard tool called clip. Piping text to clip puts it in the clipboard.)

Ah, thanks!

@martinmoene : Thanks, t.bat (and the other steps) worked like a charm. (After I ran it from a Developer Command Prompt - cl is not in my path variable.)
@mbeutel : CMake-ing it sounds nice. :)


can't parse chained unary operators

The parser cannot parse chained unary operator chains. For example, this works:
ghci> parseText exp  "not false"
Right (Unop Not (Bool False))

But this fails:
ghci> parseText exp  "not not false"
Left "lua" (line 1, column 5):
unexpected (`not`,AlexPn 4 1 5)
expecting `nil`, `true`, `false`, number, string, `...`, `function`, ident, `(` or `{`

This is because exp' parser doesn't have opExp as a choice, and adding that causes exp parser to never return because of left-recursive parsing.

This is slightly improved with https://github.com/osa1/language-lua/commit/25ec271fefbd1843ef69b3fab8c0d867fb9bbe0d but the general solution(for mixing different operators, unary and binaries in same expressions etc.) is still not in sight.


Leo add db

Adding db functions to aopy, would appreciate some testing & feedback on real data

add bmi3d as a requirement for aopy
lookup_sessions() function replaces db.get_task_entries(), has the same format but adds some functionality
add lookup_flash_sessions(), lookup_mc_sessions(), lookup_tracking_sessions(), lookup_bmi_sessions() shortcuts
lookup functions return a new wrapper BMI3DTaskEntry instead of working directly with the bmi3d TaskEntry model. can add future enhancements like being able to save links to preprocessed data, etc.
add a couple wrapper utility functions

hi pavi, have you had a chance to test these new functions out? one thing that I think might be missing is a way to lookup entries by their id number directly.

hi pavi, have you had a chance to test these new functions out? one thing that I think might be missing is a way to lookup entries by their id number directly.

Hi Leo, I have some issues installing this branch locally on crab-eating to test on real data. The problematic package is open-ephys-python-tools. here is the error I get:
ERROR: Could not find a version that satisfies the requirement open-ephys-python-tools (from versions: 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5)
ERROR: No matching distribution found for open-ephys-python-tools
I liked the lookup functions in general. Some comments are: using some examples to filter sessions with ecube vs neuropixels recordings would be helpful. Also wondering is record_headstage is a feature?

Something weird was going on with your pip. i ran
conda activate pavi_dev
pip cache purge

and then did
pip install -U pip
pip install open-ephys-python-tools

and it worked.

I tested the dbfunctions on real data in the server in pavi_dev. The changes look great. database_example notebook helps understand what those functions do. Approving the pull request.
Some notes from my observations: it looks like Django version should be <4.2 for the dbfunctions to work. For example, Django versions in the 'default' condo environment is 4.2.1 and this notebook doesn't run in that. Just something to note down. While I see that bmi3d requirements.txt specifies the version of Django to be installed, setup.py doesn't have any and I am not sure if setup.py uses requirements.txt to install packages.
Here is the error message one would see: NotSupportedError: MySQL 8 or later is required (found 5.7.40). error when Django version => 4.2

Please check is tests/test_data.py is passing all tests on your end. 5 tests related to db failed in the server for me.


Debug Julia in VS code ("Some Julia code in the VS Code extension crashed")

Several months ago, everthing was running with Julia (version 1.3) in VS code by clicking "Run and Debug".
However, with the same code, the following error appeared while running the code and I haven't found any solution so far.
"Error: Some Julia code in the VS Code extension crashed
ERROR: KeyError: key 0 not found"
Either updating the latest version (the other problem related to the packages occured so I reset the version of julia 1.3) or change launch.json as following :
"configurations": [

{
    "type": "julia",
    "request": "launch",
    "name": "Launch Julia tests",
    "program": "${workspaceFolder}/XXXXX.jl",
    "stopOnEntry": true
},

Could anybody help me out ? Thank you in advance.

This probably is an issue for the Julia extension, please file it there, thanks


Load Test

Problem
We need a Load Test Suite to be able to answer the following questions:

What is our current limit of "normal usage" users we can attend concurrently.
What are the ideal parameters to set an auto-scale policy in CPU and Memory.

Solution
Extend the current k6 performance tests in place so we can use them as a first Load Test.

Load Test must call a sub-set of methods that represent the current usage of a single user.
Load Test must call all the methods concurrently as opposed to sequentially.
Load Test must should be run with different amount of VU's (10, 25, 50, 100, 150, 200, 500... until been able to answer Question 1)

Alternatives
No response

This link was used in the basis to decide what methods to include as part of the test
https://github.com/MetaMask/metamask-extension/issues/15372


Fix Reply Message for Self Messages

I made the bar next to the reply message line up with the textbox

I would've merged this but you're adding too many rules.
All you need to do was:
#app-mount .cozy-VmLDNB[data-is-author-self="true"] {
	// css...
	.repliedMessage-3Z6XBG {
		padding-right: 28px;
		&::before {
			left: unset;
			right: 2px;
			width: 18px;
			margin: 0;
			border-left: none;
			border-right: var(--spine-width) solid var(--interactive-muted);
			border-radius: 0 6px 0 0;
		}
	}
	// css...
}

Instead of adding 2 new blocks and not utilizing SCSS.


Update CI requirements

Explicitly install ansible for linting.
Use pip to install ansible version.
Cleanup obsolete tox.ini.
Fix meta author to match galaxy namespace.

Signed-off-by: Ben Kochie<EMAIL_ADDRESS>

Odd, it still doesn't like the galaxy namespace.


Feature Request

Hello
After de default deployment only the Network for the connectivity Subscription is build.
What about the networks and routing in the Identity subscription (for the deployment of the Bastion and Azure ARC) and the Management subscription (for the deployment of DC and SyncServers)
It would be very helpful if all vnets and other network components would be deployed to all subscriptions.

Hi @ronaldbok. Can you provide more context please? Which starter module are you using? Would this sit better with the module itself? https://github.com/Azure/terraform-azurerm-caf-enterprise-scale

Hello Jared,
Sorry  i was not clear.
We deployed the ALZ met the hubnetworking deployment.
We need a working network in all Landingzones.
We are looking for a Solution to implement for our customers to deploy the Enterprise scale Landing zone.
The solution must include all basic settings in the subscriptions so that we can deploy the same ALZ to all of our customers.
Your solution is the first one that Realy works, so we like to help get it better.
At this moment we are working on the solution 4 people. If the Basic ALZ is ready for our needs we want to go to the next step and deploy the landingzones for the Applications.
Maybe it is easier to communicate true email or teams my adres is<EMAIL_ADDRESS>Hope to hear from you
Greetings Ronald

Hey @ronaldbok,
We actually have issue with this to accelerate the lz-vending module here #2, this will then allow you to vend landing zones for your applications through a secure CI/CD process just like the ALZ is done today.
The features of that module can be found here https://github.com/Azure/terraform-azurerm-lz-vending
I hope this answers your question!


Envoy's port is not listening in HostNetwork

Description:
Envoy's port is not listening if gw pod is set to use HostNetwork, and also there are some error log in envoy pod.
Repro steps:
Use EnvoyProxy CR to declare gw pod using HostNetwork, like this:
apiVersion: gateway.networking.k8s.io/v1
kind: GatewayClass
metadata:
  name: eg2
spec:
  controllerName: gateway.envoyproxy.io/gatewayclass-controller
  parametersRef:
    group: gateway.envoyproxy.io
    kind: EnvoyProxy
    name: eg2
    namespace: envoy-gateway-system

---
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
  name: eg2
  namespace: envoy-gateway-system
spec:
  shutdown:
    drainTimeout: "1s"
    minDrainDuration: "1s"
  provider:
    type: Kubernetes
    kubernetes:
      envoyService:
        type: ClusterIP
      envoyDeployment:
        replicas: 1
        container:
          resources: {}
        pod:
          hostNetwork: true

---
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: test
  namespace: envoy-gateway-system
spec:
  gatewayClassName: eg2
  listeners:
    - name: test
      protocol: HTTPS
      port: 8899
      tls:
        certificateRefs:
          - kind: Secret
            group: ""
            name: test-crt-secret
      allowedRoutes:
        namespaces:
          from: All

And the gw pod yaml:
# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: v1
kind: Pod
metadata:
  annotations:
    prometheus.io/path: /stats/prometheus
    prometheus.io/port: "19001"
    prometheus.io/scrape: "true"
  creationTimestamp: "2024-03-07T03:12:19Z"
  generateName: envoy-envoy-gateway-system-test-c5654c8e-5788f75495-
  labels:
    app.kubernetes.io/component: proxy
    app.kubernetes.io/managed-by: envoy-gateway
    app.kubernetes.io/name: envoy
    gateway.envoyproxy.io/owning-gateway-name: test
    gateway.envoyproxy.io/owning-gateway-namespace: envoy-gateway-system
    pod-template-hash: 5788f75495
  name: envoy-envoy-gateway-system-test-c5654c8e-5788f75495-qvjpm
  namespace: envoy-gateway-system
  ownerReferences:
  - apiVersion: apps/v1
    blockOwnerDeletion: true
    controller: true
    kind: ReplicaSet
    name: envoy-envoy-gateway-system-test-c5654c8e-5788f75495
    uid: 962cac76-47c1-4a30-9320-427225e593b5
  resourceVersion: "26347853154"
  uid: c636dda3-ff23-4026-893d-f0094f8a479e
spec:
  automountServiceAccountToken: false
  containers:
  - args:
    - --service-cluster envoy-gateway-system/test
    - --service-node $(ENVOY_POD_NAME)
    - |
      --config-yaml admin:
        access_log:
        - name: envoy.access_loggers.file
          typed_config:
            "@type": type.googleapis.com/envoy.extensions.access_loggers.file.v3.FileAccessLog
            path: /dev/null
        address:
          socket_address:
            address: <IP_ADDRESS>
            port_value: 19000
      layered_runtime:
        layers:
        - name: global_config
          static_layer:
            envoy.restart_features.use_eds_cache_for_ads: true
            re2.max_program_size.error_level:<PHONE_NUMBER>
            re2.max_program_size.warn_level: 1000
      dynamic_resources:
        ads_config:
          api_type: DELTA_GRPC
          transport_api_version: V3
          grpc_services:
          - envoy_grpc:
              cluster_name: xds_cluster
          set_node_on_first_message_only: true
        lds_config:
          ads: {}
          resource_api_version: V3
        cds_config:
          ads: {}
          resource_api_version: V3
      static_resources:
        listeners:
        - name: envoy-gateway-proxy-ready-<IP_ADDRESS>-19001
          address:
            socket_address:
              address: <IP_ADDRESS>
              port_value: 19001
              protocol: TCP
          filter_chains:
          - filters:
            - name: envoy.filters.network.http_connection_manager
              typed_config:
                "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
                stat_prefix: eg-ready-http
                route_config:
                  name: local_route
                  virtual_hosts:
                  - name: prometheus_stats
                    domains:
                    - "*"
                    routes:
                    - match:
                        prefix: /stats/prometheus
                      route:
                        cluster: prometheus_stats
                http_filters:
                - name: envoy.filters.http.health_check
                  typed_config:
                    "@type": type.googleapis.com/envoy.extensions.filters.http.health_check.v3.HealthCheck
                    pass_through_mode: false
                    headers:
                    - name: ":path"
                      string_match:
                        exact: /ready
                - name: envoy.filters.http.router
                  typed_config:
                    "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
        clusters:
        - name: prometheus_stats
          connect_timeout: 0.250s
          type: STATIC
          lb_policy: ROUND_ROBIN
          load_assignment:
            cluster_name: prometheus_stats
            endpoints:
            - lb_endpoints:
              - endpoint:
                  address:
                    socket_address:
                      address: <IP_ADDRESS>
                      port_value: 19000
        - connect_timeout: 10s
          load_assignment:
            cluster_name: xds_cluster
            endpoints:
            - load_balancing_weight: 1
              lb_endpoints:
              - load_balancing_weight: 1
                endpoint:
                  address:
                    socket_address:
                      address: envoy-gateway
                      port_value: 18000
          typed_extension_protocol_options:
            envoy.extensions.upstreams.http.v3.HttpProtocolOptions:
              "@type": "type.googleapis.com/envoy.extensions.upstreams.http.v3.HttpProtocolOptions"
              explicit_http_config:
                http2_protocol_options:
                  connection_keepalive:
                    interval: 30s
                    timeout: 5s
          name: xds_cluster
          type: STRICT_DNS
          transport_socket:
            name: envoy.transport_sockets.tls
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
              common_tls_context:
                tls_params:
                  tls_maximum_protocol_version: TLSv1_3
                tls_certificate_sds_secret_configs:
                - name: xds_certificate
                  sds_config:
                    path_config_source:
                      path: "/sds/xds-certificate.json"
                    resource_api_version: V3
                validation_context_sds_secret_config:
                  name: xds_trusted_ca
                  sds_config:
                    path_config_source:
                      path: "/sds/xds-trusted-ca.json"
                    resource_api_version: V3
    - --log-level warn
    - --cpuset-threads
    command:
    - envoy
    env:
    - name: ENVOY_GATEWAY_NAMESPACE
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.namespace
    - name: ENVOY_POD_NAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.name
    image: envoyproxy/envoy:distroless-v1.29-latest
    imagePullPolicy: IfNotPresent
    lifecycle:
      preStop:
        httpGet:
          path: /shutdown/ready
          port: 19002
          scheme: HTTP
    name: envoy
    ports:
    - containerPort: 8899
      hostPort: 8899
      name: test-9f86d081
      protocol: TCP
    - containerPort: 19001
      hostPort: 19001
      name: metrics
      protocol: TCP
    readinessProbe:
      failureThreshold: 3
      httpGet:
        path: /ready
        port: 19001
        scheme: HTTP
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 1
    resources: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /certs
      name: certs
      readOnly: true
    - mountPath: /sds
      name: sds
  - args:
    - envoy
    - shutdown-manager
    - --ready-timeout=11s
    command:
    - envoy-gateway
    env:
    - name: ENVOY_GATEWAY_NAMESPACE
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.namespace
    - name: ENVOY_POD_NAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.name
    image: envoyproxy/gateway-dev:7d48480
    imagePullPolicy: IfNotPresent
    lifecycle:
      preStop:
        exec:
          command:
          - envoy-gateway
          - envoy
          - shutdown
          - --drain-timeout=1s
          - --min-drain-duration=1s
    livenessProbe:
      failureThreshold: 3
      httpGet:
        path: /healthz
        port: 19002
        scheme: HTTP
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 1
    name: shutdown-manager
    readinessProbe:
      failureThreshold: 3
      httpGet:
        path: /healthz
        port: 19002
        scheme: HTTP
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 1
    resources:
      requests:
        cpu: 10m
        memory: 32Mi
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  hostNetwork: true
  nodeName: <IP_ADDRESS>
  preemptionPolicy: PreemptLowerPriority
  priority: 0
  restartPolicy: Always
  schedulerName: default-scheduler
  securityContext: {}
  serviceAccount: envoy-envoy-gateway-system-test-c5654c8e
  serviceAccountName: envoy-envoy-gateway-system-test-c5654c8e
  terminationGracePeriodSeconds: 301
  tolerations:
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
    tolerationSeconds: 300
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
    tolerationSeconds: 300
  volumes:
  - name: certs
    secret:
      defaultMode: 420
      secretName: envoy
  - configMap:
      defaultMode: 420
      items:
      - key: xds-trusted-ca.json
        path: xds-trusted-ca.json
      - key: xds-certificate.json
        path: xds-certificate.json
      name: envoy-envoy-gateway-system-test-c5654c8e
      optional: false
    name: sds
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2024-03-07T03:12:19Z"
    status: "True"
    type: Initialized
  - lastProbeTime: null
    lastTransitionTime: "2024-03-07T03:13:00Z"
    status: "True"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2024-03-07T03:13:00Z"
    status: "True"
    type: ContainersReady
  - lastProbeTime: null
    lastTransitionTime: "2024-03-07T03:12:19Z"
    status: "True"
    type: PodScheduled
  containerStatuses:
  - containerID: containerd://ed7660459ee578a8ae23754f1e040b344e51acd2e076c80ba173193451e0811e
    image: docker.io/envoyproxy/envoy:distroless-v1.29-latest
    imageID: docker.io/envoyproxy/envoy@sha256:76dcbc0509d51001da1c94937b4498bd30ae6eb074d98863336c522311b19fa4
    lastState: {}
    name: envoy
    ready: true
    restartCount: 0
    started: true
    state:
      running:
        startedAt: "2024-03-07T03:12:20Z"
  - containerID: containerd://d5f018ef18676d84fe526fe1a60498a579cd47beded39e3de1645eb55fbd4396
    image: docker.io/envoyproxy/gateway-dev:7d48480
    imageID: docker.io/envoyproxy/gateway-dev@sha256:4b217e42eceab975166ab9676f7ad524fa271abfa1a97fd30b01c87b77d8cbdb
    lastState: {}
    name: shutdown-manager
    ready: true
    restartCount: 0
    started: true
    state:
      running:
        startedAt: "2024-03-07T03:12:20Z"
  hostIP: <IP_ADDRESS>
  phase: Running
  podIP: <IP_ADDRESS>
  podIPs:
  - ip: <IP_ADDRESS>
  qosClass: Burstable
  startTime: "2024-03-07T03:12:19Z"

The envoy should listen 8899 as it is declared in Gateway CR (envoy listens the same port if Gateway's port > 1024), but envoy did not.
Environment:
envoygateway version: v1.0.0-rc.1
Tested both on single node k3s and the cloud hosted Tencent Kubenretes Engine, got the same result.
Logs:
Logs in envoy container:
[2024-03-07 03:12:20.518][1][warning][main] [source/server/server.cc:910] There is no configured limit to the number of allowed active downstream connections. Configure a limit in `envoy.res
ource_monitors.downstream_connections` resource monitor.
[2024-03-07 03:12:35.701][1][warning][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:130] gRPC config: initial fetch timed out for type.googleapis.com/envoy.co
nfig.cluster.v3.Cluster
[2024-03-07 03:12:50.700][1][warning][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:130] gRPC config: initial fetch timed out for type.googleapis.com/envoy.co
nfig.listener.v3.Listener
[2024-03-07 03:12:53.005][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 32s ago
: 14, no healthy upstream
[2024-03-07 03:12:58.650][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 37s ago
: 14, no healthy upstream
[2024-03-07 03:13:11.834][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 51s ago
: 14, no healthy upstream
[2024-03-07 03:13:21.367][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 60s ago
: 14, no healthy upstream
[2024-03-07 03:13:35.482][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 74s ago
: 14, no healthy upstream
[2024-03-07 03:13:50.977][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 90s ago
: 14, no healthy upstream
[2024-03-07 03:14:06.127][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 105s ag
o: 14, no healthy upstream
[2024-03-07 03:14:16.377][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 115s ag
o: 14, no healthy upstream
[2024-03-07 03:14:27.038][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 126s ag
o: 14, no healthy upstream
[2024-03-07 03:14:38.318][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 137s ag
o: 14, no healthy upstream
[2024-03-07 03:14:39.265][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 138s ag
o: 14, no healthy upstream
[2024-03-07 03:14:58.874][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 158s ag
o: 14, no healthy upstream
[2024-03-07 03:15:09.898][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 169s ag
o: 14, no healthy upstream
[2024-03-07 03:15:33.649][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 192s ag
o: 14, no healthy upstream
[2024-03-07 03:15:48.446][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 207s ag
o: 14, no healthy upstream
[2024-03-07 03:16:00.839][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 220s ag
o: 14, no healthy upstream
[2024-03-07 03:16:07.694][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 226s ag
o: 14, no healthy upstream
[2024-03-07 03:16:30.617][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 249s ag
o: 14, no healthy upstream
[2024-03-07 03:16:55.820][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 275s ag
o: 14, no healthy upstream
[2024-03-07 03:17:04.787][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 284s ag
o: 14, no healthy upstream
[2024-03-07 03:17:07.830][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 287s ag
o: 14, no healthy upstream
[2024-03-07 03:17:31.054][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 310s ag
o: 14, no healthy upstream
[2024-03-07 03:17:31.257][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 310s ag
o: 14, no healthy upstream
[2024-03-07 03:17:59.267][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 338s ag
o: 14, no healthy upstream
[2024-03-07 03:18:28.889][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 368s ag
o: 14, no healthy upstream
[2024-03-07 03:18:41.524][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 380s ag
o: 14, no healthy upstream
[2024-03-07 03:18:42.768][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 382s ag
o: 14, no healthy upstream
[2024-03-07 03:19:05.548][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 404s ag
o: 14, no healthy upstream
[2024-03-07 03:19:26.006][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 425s ago: 14, no healthy upstream
[2024-03-07 03:19:34.582][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 433s ago: 14, no healthy upstream
[2024-03-07 03:20:02.878][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 462s ago: 14, no healthy upstream
[2024-03-07 03:20:17.984][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 477s ago: 14, no healthy upstream
[2024-03-07 03:20:23.831][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 483s ago: 14, no healthy upstream
[2024-03-07 03:20:27.603][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 486s ago: 14, no healthy upstream
[2024-03-07 03:20:31.735][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 491s ago: 14, no healthy upstream
[2024-03-07 03:20:48.332][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 507s ago: 14, no healthy upstream
[2024-03-07 03:20:57.674][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 516s ago: 14, no healthy upstream
[2024-03-07 03:21:12.390][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 531s ago: 14, no healthy upstream
[2024-03-07 03:21:42.229][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 561s ago: 14, no healthy upstream
[2024-03-07 03:21:58.696][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 577s ago: 14, no healthy upstream
[2024-03-07 03:22:24.603][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 603s ago: 14, no healthy upstream
[2024-03-07 03:22:48.130][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 627s ago: 14, no healthy upstream
[2024-03-07 03:23:17.094][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 656s ago: 14, no healthy upstream
[2024-03-07 03:23:39.588][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 678s ago: 14, no healthy upstream
[2024-03-07 03:23:52.943][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 692s ago: 14, no healthy upstream
[2024-03-07 03:23:56.546][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 695s ago: 14, no healthy upstream
[2024-03-07 03:24:03.108][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 702s ago: 14, no healthy upstream
[2024-03-07 03:24:12.983][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 712s ago: 14, no healthy upstream
[2024-03-07 03:24:29.579][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 728s ago: 14, no healthy upstream
[2024-03-07 03:24:34.658][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 733s ago: 14, no healthy upstream
[2024-03-07 03:24:37.604][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 736s ago: 14, no healthy upstream
[2024-03-07 03:24:54.716][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 754s ago: 14, no healthy upstream
[2024-03-07 03:25:18.185][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 777s ago: 14, no healthy upstream
[2024-03-07 03:25:48.098][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 807s ago: 14, no healthy upstream
[2024-03-07 03:25:50.520][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 809s ago: 14, no healthy upstream
[2024-03-07 03:26:01.690][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 820s ago: 14, no healthy upstream
[2024-03-07 03:26:30.518][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 849s ago: 14, no healthy upstream
[2024-03-07 03:26:52.494][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 871s ago: 14, no healthy upstream
[2024-03-07 03:27:00.670][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 879s ago: 14, no healthy upstream
[2024-03-07 03:27:26.575][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 905s ago: 14, no healthy upstream
[2024-03-07 03:27:33.402][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 912s ago: 14, no healthy upstream
[2024-03-07 03:27:44.040][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 923s ago: 14, no healthy upstream
[2024-03-07 03:27:59.109][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 938s ago: 14, no healthy upstream
[2024-03-07 03:28:02.022][1][warning][config] [./source/extensions/config_subscription/grpc/grpc_stream.h:193] DeltaAggregatedResources gRPC config stream to xds_cluster closed since 941s ago: 14, no healthy upstream

cc @Xunzhuo

You should set dnsPolicy: ClusterFirstWithHostNet too, the xds_clusters of envoyproxy used service name for looking up control plane:
          "cluster": {
            "@type": "type.googleapis.com/envoy.config.cluster.v3.Cluster",
            "connectTimeout": "10s",
            "loadAssignment": {
              "clusterName": "xds_cluster",
              "endpoints": [
                {
                  "lbEndpoints": [
                    {
                      "endpoint": {
                        "address": {
                          "socketAddress": {
                            "address": "envoy-gateway",
                            "portValue": 18000
                          }
                        }
                      },
                      "loadBalancingWeight": 1
                    }
                  ],
                  "loadBalancingWeight": 1
                }
              ]

When you are using hostNetwork, we need to set dnsPolicy to ClusterFirstWithHostNet too.
Refer to:  https://github.com/envoyproxy/gateway/pull/2374#issue-2059138573

Since we have supported deployment/svc mergepatch, I think we need to remove hostnetwork support on Envoyproxy API or have a more complete implementation for it.
Any thoughts on it @arkodg ?

Yes let's remove it

Let me handle it before GA.

Thanks, change to mergepatch solves this problem:
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
  name: eg2
  namespace: envoy-gateway-system
spec:
  shutdown:
    drainTimeout: "1s"
    minDrainDuration: "1s"
  provider:
    type: Kubernetes
    kubernetes:
      envoyService:
        type: ClusterIP
      envoyDeployment:
        patch:
          type: StrategicMerge
          value:
            spec:
              template:
                spec:
                  hostNetwork: true
                  dnsPolicy: ClusterFirstWithHostNet


Chefspec ignoring environment variables

Chefspec appears to be ignoring environment variables, when running for one cookbook. We have a cookbook that is calling a data bag like so:
default.rb
config_data = data_bag_item('elasticsearch', 'config')['group'][server_group][node.chef_environment]
which I have expanded to:
tmp_data = data_bag_item('elasticsearch', 'config')['group']

tmp_data_1 = tmp_data[server_group]
config_data = tmp_data_1[node.chef_environment]

Example data bag:
"group": {
    "groupA": {
      "prod": {
        "cluster_name": "clusterA",
      },
      "stage": {
        "cluster_name": "clusterStageA",
      },
  }

chefspec:
describe 'role_elasticsearch::ebs' do
  context 'when in stage' do
    let(:chef_run) do
      ChefSpec::SoloRunner.new do |node|
        env = Chef::Environment.new
        env.name 'stage'
        allow(node).to receive(:chef_environment).and_return(env.name)
        allow(Chef::Environment).to receive(:load).and_return(env)
        node.set['name'] = 's-test-blarblar'
// I have also tried using combinations of the following:
        node.set['chef_environment'] = 'stage'
        node.set['node']['chef_environment'] = 'stage'
        node.normal['chef_environment'] = 'stage'
        node.normal['node']['chef_environment'] = 'stage'
      end.converge('role_elasticsearch::ebs')
    end

    before do
      stub_data_bag_item('elasticsearch', 'config').and_return({
          id: 'config',
          install: {
            default: {
            }
          },
          group: {
            GroupA: {
              stage: {}
            }
          }
        })
    end

    it 'will include my recipe' do
      expect(chef_run).to include_recipe('myrecipe')
    end
  end
end

However I am getting the following error when running the tests:
Recipe Compile Error in /var/folders/k5/2wstr0w96w99h0ykf1mltmp80000gn/T/d20161025-2220-7c9e2l/cookbooks/role_elasticsearch/recipes/ebs.rb
===========================================================================

NoMethodError
-------------
undefined method []' for nil:NilClass

Cookbook Trace:
---------------
  /var/folders/k5/2wstr0w96w99h0ykf1mltmp80000gn/T/d20161025-2220-7c9e2l/cookbooks/role_elasticsearch/recipes/ebs.rb:13:in from_file'

Relevant File Content:
----------------------
/var/folders/k5/2wstr0w96w99h0ykf1mltmp80000gn/T/d20161025-2220-7c9e2l/cookbooks/role_elasticsearch/recipes/ebs.rb:

  6:  #
  7:  # All rights reserved - Do Not Redistribute
  8:  #
  9:  server_group = node.name.split('-')[1]
 10:  tmp_data = data_bag_item('elasticsearch', 'config')['group']
 11:
 12:  tmp_data_1 = tmp_data[server_group]
 13>> config_data = tmp_data_1[node.chef_environment]
 14:
 15:  data_size = config_data['data_size'] || 10
 16:  data_iops = config_data['data_iops'] || 101
 17:  data_device = config_data['data_device'] || '/dev/xvdg'
 18:  log_device = config_data['log_device'] || '/dev/xvdh'
 19:
 20:  node.normal['ebs']['volumes'] = [
 21:    {
 22:      'user'         => 'myuser',

Platform:
---------
x86_64-darwin13

F

Failures:

  1) role_elasticsearch::ebs when in stage will include myrecipe recipe
     Failure/Error:
             ChefSpec::SoloRunner.new do |node|

               env = Chef::Environment.new
               env.name 'stage'
               allow(node).to receive(:chef_environment).and_return(env.name)
               allow(Chef::Environment).to receive(:load).and_return(env)

               node.set['name'] = 's-test-blarblar'
               node.set['chef_environment'] = 'stage'
               node.set['node']['chef_environment'] = 'stage'

     NoMethodError:
       undefined method []' for nil:NilClass
     # /var/folders/k5/2wstr0w96w99h0ykf1mltmp80000gn/T/d20161025-2220-7c9e2l/cookbooks/role_elasticsearch/recipes/ebs.rb:13:in `from_file'
     # ./spec/recipes/ebs_spec.rb:23:in block (3 levels) in <top (required)>'
     # ./spec/recipes/ebs_spec.rb:42:in block (3 levels) in <top (required)>'

Finished in 1.43 seconds (files took 2.3 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./spec/recipes/ebs_spec.rb:41 # role_elasticsearch::ebs when in stage will include myrecipe recipe

  No Chef resources found, skipping coverage calculation...

It appears that the node.chef_environment is not set no matter what combination I use.

I'm not familiar with stub_data_bag_item and am instead using https://github.com/chef/chef-vault-testfixtures to point to stubbed data bags in test/integration/data_bags... but..
I have something that looks to be the same as your pattern in production:
let(:chef_run) do
    ChefSpec::SoloRunner.new(platform: 'redhat', version: '7.2') do |node|
      # Chefspec overrides the environment as 'chefspec'. Change the env back
      # to _default.
      env = Chef::Environment.new
      env.name '_default'
      allow(node).to receive(:chef_environment).and_return(env.name)
      allow(Chef::Environment).to receive(:load).and_return(env)

    end.converge(described_recipe)
  end

Have you added a puts "Env: #{node.chef_environment}" in your default.rb to see what value it was receiving? Sometimes the undefined method []' for nil:NilClass errors are coming from somewhere you would have never expected...

chef_environment isn't a typical attribute, so node.chef_environment = "myenvironment" needs to be used instead of node.automatic["chef_environment"] = "myenvironment".  the latter will never work and is not a bug.
in chefspec though that results in:
================================================================================
Error expanding the run_list:
================================================================================

Unexpected Error:
-----------------
Chef::Exceptions::EnvironmentNotFound: Environment 'myenvironment' could not be loaded from disk

System Info:
------------
chef_version=14.1.1
platform=chefspec
platform_version=0.6.1
ruby=ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin16]
program_name=/Users/lamont/.rvm/gems/ruby-2.5.1/bin/rspec
executable=/Users/lamont/.rvm/gems/ruby-2.5.1/bin/ruby_executable_hooks

F

Failures:

  1) test::default
     Failure/Error: cached(:chef_run) { ChefSpec::SoloRunner.new { |node| node.chef_environment = "myenvironment" }.converge(described_recipe) }

     Chef::Exceptions::EnvironmentNotFound:
       Environment 'myenvironment' could not be loaded from disk
     # /Users/lamont/oc/chef/lib/chef/environment.rb:265:in `load_from_file'
     # /Users/lamont/oc/chef/lib/chef/environment.rb:241:in `load'
     # /Users/lamont/oc/chef/lib/chef/node.rb:443:in `apply_expansion_attributes'
     # /Users/lamont/oc/chef/lib/chef/node.rb:431:in `expand!'
     # /Users/lamont/oc/chef/lib/chef/policy_builder/expand_node_object.rb:144:in `expand_run_list'
     # /Users/lamont/oc/chef/lib/chef/client.rb:808:in `expanded_run_list'
     # /Users/lamont/.rvm/gems/ruby-2.5.1/gems/chefspec-7.2.1/lib/chefspec/solo_runner.rb:397:in `expand_run_list!'
     # /Users/lamont/.rvm/gems/ruby-2.5.1/gems/chefspec-7.2.1/lib/chefspec/solo_runner.rb:114:in `converge'
     # ./spec/test_spec.rb:4:in `block (2 levels) in <top (required)>'
     # /Users/lamont/.rvm/gems/ruby-2.5.1/gems/chefspec-7.2.1/lib/chefspec/cacher.rb:50:in `instance_eval'
     # /Users/lamont/.rvm/gems/ruby-2.5.1/gems/chefspec-7.2.1/lib/chefspec/cacher.rb:50:in `block in cached'
     # ./spec/test_spec.rb:7:in `block (2 levels) in <top (required)>'

Finished in 0.02481 seconds (files took 0.94484 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./spec/test_spec.rb:7 # test::default

That results in the need to stub the chef classes directly to work around this issue, which is probably not good UX.

We have instructions on this in the README already, https://github.com/chefspec/chefspec#mocking-out-environments

Yep, I just found those and was coming here to comment and close...


Fix trivial typo from docs

Description
Please include a summary of this pull request in English. If it closes an issue, please mention it here.
Closes: #(issue number)
We recommend to link at least one existing issue for PR. Before your create a PR, please check if there is an issue for this change.
Change(s)

Fix Trivial Typo from the docs/augmentation/transforms/randomerasing

Code Formatting
If you PR to either master or dev branch, you should follow the code linting process. Please check your code with lint_check.sh in ./scripts directory.
For more information, please read the contribution guide in CONTRIBUTING.md.
Changelog
If your PR is granted to dev branch, codeowner will add a brief summary of the change to the Upcoming Release section of the CHANGELOG.md file including a link to the PR (formatted in markdown) and a link to your github profile.
For example,
- Added a new feature by `@myusername` in [PR 2023](https://github.com/Nota-NetsPresso/netspresso-trainer/pull/2023)

Please enable Allow edits and access to secrets by maintainers so that our maintainers can update the CHANGELOG.md.

I missed another typo below the change I made. Please review it :)


Add SmartThingsAccelCluster to binary_sensor

Description:
Adds binary_sensor for acceleration attribute of centralite/smartthings devices. Currently committed devices include Centralite 3321-S and SmartThings multiv4.
Depends on PR #21500.
Checklist:

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

Hi @roblandry,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

This is going to need a rebase


C++ Program either gets caught in infinite loop or get aborted!

I have a multi-file (3 .cpp files and 2 .h files) C++ code that uses new, new[], delete, and delete[] operators to allocate large chunks of memory and performs some floating point operations (requires division by sqrt()). The program compiles and runs well with regular g++ and produces the required output. I now want to convert it to RISC-V instructions.

I first used the GNU RISC-V compiler toolchain to compile the program with following command:
riscv32-unknown-elf-g++ -w -march=rv32imafc -mabi=ilp32f -DPREALLOCATE=1 -mcmodel=medany -fno-common -static -Iinclude/ f1.cpp f2.cpp f3.cpp -o executable
here executable is the compiled binary file.

Since no errors are thrown at compile time, I proceeded to run the whisper simulator as follows:
whisper --isa imafc --target executable --logfile mylog --profileinst prfl
where mylog and prfl are output file paths.

The log file generated exceeds 6 GB in size and it doesn't terminate, so I assume that it is stuck in some infinite loop.

I tried adding the _start() function and tohost variable which didn't work either (same problem as 3 above).

I generated an object dump for executable and captured the (hex) addresses of starting address of main(), its ending address and address of tohost and passed them as parameters to --startpc, --endpc and --tohost respectively, in which case, the program was aborted after 64 illegal operations and ~300 MB of log file.

I think I am making some mistake. Kindly help me fix this issue or share the correct steps to generate the RISC-V assembly instructions for my C++ program.

Hi Anurag,
The commands you used look good.  Maybe we have a bug in whisper.  Would it be possible to share the source files so that we can try to reproduce the problem and fix it.
Thanks,
Joe

cppcode.zip
Please find the code attached in the .zip file. (Please modify the makefil in case you have to use it.)
The code, when compiled and run with regular g++, will currently not produce any output as I have commented out all the print statements.
One thing to note is that I have used inline functions - could that have caused the issue?

Hi Anurag,
The program has a bug in the normalize function:
float* hs = new float[rows];
for (int i=0; i<cols; ++i) {
hs[i] = 0;
//++memwrite;
//++l_memwrite;
}
The cols in the loop should be replaced by rows. The bug causes memory corruption.  Once bug is fixed, code runs fine in whisper.
Joe

Hi Anurag,
The program has a bug that corrupts memory.  The bug is in the normalize
function at line 161 of symm_normalize.h. The code should be:
for (int i=0; i<rows; ++i) {
After fixing the bug, the code ran fine on whisper.
I found the bug by compiling the code for x86 and running the valgrind tool
on the executable:  valgrind  bin/executable
Joe
On Tue, Dec 1, 2020 at 12:24 AM Anurag Banerjee<EMAIL_ADDRESS>wrote:

cppcode.zip
https://github.com/chipsalliance/SweRV-ISS/files/5620613/cppcode.zip
Please find the code attached in the .zip file. (Please modify the makefil
in case you have to use it.)
The code, when compiled and run with regular g++, will currently not
produce any output as I have commented out all the print statements.
One thing to note is that I have used inline functions - could that have
caused the issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/chipsalliance/SweRV-ISS/issues/3#issuecomment-736251729,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASHQX2PZT27SHS5IWZ2PQDSSSD23ANCNFSM4UHRKGFA
.

Hello Dr. Rahmeh,
Thank you for helping me out with this - I feel silly for having made such an obvious out-of-bound-access error.
Further, I also made an error at symm_normalize.h:112 - it should have been D[i] instead of D[j] - but that is more of a logical error.
However, for anyone reading this in future - please also make sure that you have the latest whisper simulator (this repo) and not the older one (westerndigital). In case you are using -march=rv32imafc during compile time and --isa imafc during running whisper, make sure your data is in float datatype - I used sqrt() (returns double) which caused some error for me, but, when I used sqrtf() all was fine. My final log file was about 725 MB in size.
Also, for me, using --newlib was essential while running whisper.

HI Anurag,
No worries.  Thanks for using whisper.  I will remove the old repository.
I will also add notes about double/float issues.
Thanks,
Joe
On Wed, Dec 2, 2020 at 1:41 PM Anurag Banerjee<EMAIL_ADDRESS>wrote:

Hello Dr. Rahmeh,
Thank you for helping me out with this - I feel silly for having made such
an obvious out-of-bound-access error.
Further, I also made an error at symm_normalize.h:112 - it should have
been D[i] instead of D[j] - but that is more of a logical error.
However, for anyone reading this in future - please also make sure that
you have the latest whisper simulator (this repo) and not the older one
(westerndigital). In case you are using -march=rv32imafc during compile
time and --isa imafc during running whisper, make sure your data is in
float datatype - I used sqrt() (returns double) which caused some
error for me, but, when I used sqrtf() all was fine. My final log file
was about 725 MB in size.
Also, for me, using --newlib was essential while running whisper.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/chipsalliance/SweRV-ISS/issues/3#issuecomment-737452564,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASHQXZIWYL2K6V3LK25IH3SS2J7XANCNFSM4UHRKGFA
.


What should commuters do in that chance that the conditions make it too difficult to make it to the midterm tomorrow?

Some of us commute to Boulder from Denver, Longmont, and Fort Collins for class. I know the blizzard is supposed to pass over Boulder, which means the chances of us having class are fairly high. In the worst case scenario, where we get 10 inches in some areas and the storm continues until noon tomorrow, what should the commuters plan to do about the midterm?

We'll have a make-up if necessary. I'm hopeful that everyone will be able to safely get to campus.


#Issue63: Support for CUDA8.0 and related jcuda libraries

#63
cuda 8.0 compatibility,

cuda  8.0 will use mavenized-jcuda folder to compile
versions less than cuda 8.0 (7.5 and 7.0a ) will use mavenized-jcuda-old folder to compile.

Updated code to run jcuda examples which will come by default from mavenized-jcuda shared libraries.
Updated run-example to consider all the arguments.

 Upgrade JCUDA to 8.0 - Ship libraries as well - Sync up with mysterion


feat: integrate SearchApi as a WebSearchEngine and as a Tool

Issue
This implements the integration of SearchApi as a WebSearchEngine which after merging should close https://github.com/langchain4j/langchain4j/issues/1132
Change

cc: @mark-searchapi
General checklist

[x] There are no breaking changes
[x] I have added unit and integration tests for my change
[x] I have manually run all the unit and integration tests in the module I have added/changed, and they are all green
[x] I have manually run all the unit and integration tests in the core and main modules, and they are all green

[ ] I have added/updated the documentation
[ ] I have added an example in the examples repo (only for "big" features)

Checklist for adding new model integration

[ ] I have added my new module in the BOM

Checklist for adding new embedding store integration

[ ] I have added a {NameOfIntegration}EmbeddingStoreIT that extends from either EmbeddingStoreIT or EmbeddingStoreWithFilteringIT
[ ] I have added my new module in the BOM

Checklist for changing existing embedding store integration

[ ] I have manually verified that the {NameOfIntegration}EmbeddingStore works correctly with the data persisted using the latest released version of LangChain4j

@algora-pbc /claim #1132

Hi @Heezer 👋,
I see you are leaving comments and providing suggestions in this PR 👍.
As you already acknowledged here, that PR is the 2nd of 2 PRs opened for the same issue.
As the author of the 1st PR, I’m a bit surprised you are spending so much time reviewing the 2nd PR. It wasn’t even ready for review until a day after I opened my PR.
As part of triaging, @langchain4j added the P2 and P3 labels to my PR on June 3 but those labels weren't added to the 2nd PR until June 6.
Humble Suggestion
Since the project is in dire need of more eyes to review outstanding PRs, perhaps it would be better if you did additional triaging first?
What I’m suggesting is that you go over the 2 PRs side-by-side and decide for yourself which one is more likely to be merged by the langchain4j maintainers based on which one:

implements most of the requirements as stated;
adheres closest to the two existing implementations;
is easier to extend to add support for other SearchApi engines mentioned by the sponsor.

For instance, the assert failure you helpfully pointed out in the 2nd PR had already implemented in my PR.
I think this is a more efficient use of your time because at the end of the day, only one PR will be accepted.
It is the accepted PR that the maintainers will ask its author to make final changes prior to being merged.
So there’s a real risk that the time you’ve already spent reviewing the 2nd PR (before proper triaging) might go unacknowledged by the maintainers, if the 2nd PR gets closed.
Thanks!

Hi @ayewo 👋 , I didn't know at the beginning about your "competition" 😄 in the meantime I'm done with review of #1216, let me review #1215 considering your suggestions, thanks! But I guess the decision what to take won't be mine 😄

Hi @ayewo 👋 , I didn't know at the beginning about your "competition" 😄 in the meantime I'm done with review of #1216, let me review #1215 considering your suggestions, thanks! But I guess the decision what to take won't be mine 😄

Haha 😁, no worries.
Thanks for volunteering your time!

@mark-searchapi
Thanks for your review. I'm furiously working to push an update but ...
I finally got the dreaded error 🙃:
{
  "error": "You have used all of the searches for the month. Please upgrade your plan on SearchApi.io."
}

How do I request additional credits to my account?

@mark-searchapi
I've removed the high coupling with the Google Search engine and added support for 2 different ways to customize a search request.
I'll update the documentation shortly but you can view the 2 styles this module can be used this test file: SearchApiWebSearchEngineIT  (the IT suffix indicates "Integration Tests" I believe).

Implementation seemed to be heavily based on Tavily, but Tavily is a wrapper around an API such as SearchAPI or Google Custom Search API or any other search engine API.
In general, similar comments to #1216 apply. Key aspects:
* Missing public documentation (including usage with OpenAI)

* Results tightly coupled to `google`. We can support `organic_results` array with only `title`, `link` and `snippet`. This way users would be able to use SearchApi with any engine that returns organic results (for instance, `google`, `bing`, `baidu`, `bing_news`, `google_news`, `google_scholar`).

* Parameters tightly coupled to `google`. Apart from query (`q` parameter), `engine`, and `api_key`, user should be free to pass any key-value pairs as custom parameters. This makes the search engine integration future proof as using upcoming search engines (or adapting to query parameter change) won't require updating `langchain4j`.

@mark-searchapi
I've addressed all of your feedback.

Wrt documentation showing OpenAI usage examples, please see searchapi-io.md.

& 3. The issue of tight coupling which you observed in the search results and  search request parameters should also be fixed.

Closing in favor of https://github.com/langchain4j/langchain4j/pull/1216
@ayewo thank you for your efforts!


Add author byline and date to feature articles

We didn't set aside space in the layout/template for a byline to credit the author(s) of a feature article. See e.g. https://beta-di.diginfra.net/beta/het-perceel-als-atoom-van-de-ruimte-nl.html Alternatively, this could go into the colophon, but I feel it should appear here because the feature articles, unlike the regular pages, represent something more like a particular, rather than a collective viewpoint. But admittedly, a debatable point. Low priority.

Should also add when the article was published.

For now, I've just added Erica Renckens at the head of the feature article but @Bas would need to adapt his template so that this appears in a smaller font size.

@wmvanderveen We need to use your interview with Menno as the second feature article. Do you have any good ideas for a graphic/photo that could be used in place of his photo?


load LandscapesBig mode error

model.load(28)
n1 = noiseList(64)
n2 = nImage(64)
for i in range(50):
    print(i, end = '\r')
    model.generateTruncated(n1, noi = n2, trunc = i / 50, outImage = True, num = i)

error
2020-01-27 14:14:23.735268: W tensorflow/core/common_runtime/base_collective_executor.cc:216] BaseCollectiveExecutor::StartAbort Invalid argument: input and filter must have the same depth: 1536 vs 96
[[{{node conv2d_mod_23/Conv2D}}]]
Traceback (most recent call last):
File "/Users/pig/PycharmProjects/StyleGAN2-Tensorflow-2.0/stylegan_two.py", line 646, in
model.generateTruncated(n1, noi = n2, trunc = i / 50, outImage = True, num = i)
File "/Users/pig/PycharmProjects/StyleGAN2-Tensorflow-2.0/stylegan_two.py", line 567, in generateTruncated
generated_images = self.GAN.GE.predict(w_space + [noi], batch_size = BATCH_SIZE)
File "/Users/pig/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/training.py", line 909, in predict
use_multiprocessing=use_multiprocessing)
File "/Users/pig/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/training_arrays.py", line 722, in predict
callbacks=callbacks)
File "/Users/pig/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/training_arrays.py", line 393, in model_iteration
batch_outs = f(ins_batch)
File "/Users/pig/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/keras/backend.py", line 3740, in call
outputs = self._graph_fn(*converted_inputs)
File "/Users/pig/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/eager/function.py", line 1081, in call
return self._call_impl(args, kwargs)
File "/Users/pig/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/eager/function.py", line 1121, in _call_impl
return self._call_flat(args, self.captured_inputs, cancellation_manager)
File "/Users/pig/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/eager/function.py", line 1224, in _call_flat
ctx, args, cancellation_manager=cancellation_manager)
File "/Users/pig/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/eager/function.py", line 511, in call
ctx=ctx)
File "/Users/pig/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/eager/execute.py", line 67, in quick_execute
six.raise_from(core._status_to_exception(e.code, message), None)
File "", line 3, in raise_from
tensorflow.python.framework.errors_impl.InvalidArgumentError:  input and filter must have the same depth: 1536 vs 96
[[node conv2d_mod_23/Conv2D (defined at /anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/ops.py:1751) ]] [Op:__inference_keras_scratch_graph_20999]
Function call stack:
keras_scratch_graph

I have this issue too. Note that 1536 is 16 * 96. Could this be an issue with BATCH_SIZE?

tensorflow.python.framework.errors_impl.InvalidArgumentError: input and filter must have the same depth: 1536 vs 96
Same problem here. Changing the batch size to 1 helped solving this issue.

Unfortunately there is no output image created. @pyrator : What dimensions and format do your images have? Thanks.

I ran the section of code to generateTruncated using one of preexisting
models, LandscapeBig.zip. This is model 28. I commented out the section to
evaluate and train and then amended the model.load parameter to 28.
I'm not sure how necessary it is to have your own data in place in the data
subfolder as these are for training I believe, but I had used 256 by 256
images.
The problem was when I tried to train the code crashes eventually with a
GPU (unfortunately it;s only a 1050 Ti) - possibly some sort of GPU memory
issue, and it would take an extremely long time with a CPU, which I tried
but it looked like it was going to take many days.
so here's my snippet of code
if name == "main":
model = StyleGAN(lr = 0.0001, silent = False)
#model.evaluate(0)

#while model.GAN.steps < 1000001:
#    model.train()

model.load(28)

n1 = noiseList(64)
n2 = nImage(64)
for i in range(50):
    print(i, end = '\r')
    model.generateTruncated(n1, noi = n2, trunc = i / 50, outImage =

True, num = i)
On Sat, 8 Feb 2020 at 14:03, derveit<EMAIL_ADDRESS>wrote:

tensorflow.python.framework.errors_impl.InvalidArgumentError: input and
filter must have the same depth: 1536 vs 96
Same problem here. Changing the batch size to 1 helped solving this issue.
Unfortunately there is no output image created. @pyrator
https://github.com/pyrator : What dimensions and format do your images
have? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/manicman1999/StyleGAN2-Tensorflow-2.0/issues/5?email_source=notifications&email_token=AAUZPLGD32NE5KOHEEJWKBLRB23R3A5CNFSM4KL4GW3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELFSPPA#issuecomment-583739324,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAUZPLFXGWCNUINBN7MYMB3RB23R3ANCNFSM4KL4GW3A
.

Same problem. If you set the batch size to 1 then it works.
But a fix is needed.


JS: Make LogChannel public

What
Made LogChannel an export. It was previously part of the public API, but I seem to have made it not exported at some point.
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using examples from latest main build: rerun.io/viewer
Using full set of examples from nightly build: rerun.io/viewer

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!

PR Build Summary
Recent benchmark results
Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

Don't want to waste CI time on this


Blog app - controllers specs

In this pull request, I completed the following tasks

[ ]  Add RSpec as a gem to the project
[ ]  Create a Request spec file for all the controllers

Thanks so much for the review @t-yanick


Validation inside of state block causes error [MongoMapper]

I haven't tested this outside of my app, but here's a snippet of the code:
  state_machine :status, :initial => :draft do

    state :published do
      validate :some_validation
    end

  # ....

    event :publish do
      transition [:draft] => :published
    end
  end

When I do this, validations run but the record is never marked as invalid if they fail (valid? returns true).  When using publish! I get:
StateMachine::InvalidTransition:
       Cannot transition status via :publish from :draft

Removing the validation makes everything work fine.

Hey @RipTheJackker -
Validations don't run until the state is entered.  If you call valid? prior to calling publish!, the validation won't run since the object isn't yet in the published state.  As well, if you upgrade to version 1.1.0, you'll find that the exception that gets raised also includes the failure reason (such as a failed validation).  If you inspect the object after calling publish! you should see the errors that were added from your some_validation method.
Hope this helps!


Redux-form with Material-ui DropDownMenu

I'm trying to use redux-form with Material-ui's DropDownMenu, but I am unable to get the DropDownMenu to display the user's selection. The actions are firing when the user selects an option and it is writing to state correctly, but it isn't updating DropDownMenu's display of the user's selection.
I think this is because of the way that DropDownMenu is defining their properties. They define them as follows:

displayMember   string default: text
DropDownMenu will use text as default value, with this property you can choose another name.

valueMember   string default: payload
DropDownMenu will use payload as default value, with this property you can choose another name.

selectedIndex   number default: 0
Index of the item selected.

onChange   function(event, selectedIndex, menuItem)
Fired when a menu item is clicked that is not the one currently selected.

I've defined my component as follows:
class Department extends Component {
    constructor(props) {
        super(props);
    }

    render() {
        return (
        let {fields: { department }, handleSubmit, closeDialog, openDialog, resetForm } = this.props;
        const departments = constants.departments.map(( dep ) => {
            return {
                value : dep,
                label : dep
            }
        });
        <DropDownMenu valueMember="value"
                  displayMember="label"
                  placeholder="Department ..."
                  menuItems={departments}
                  {...department} />
        );
    }
}

Department = reduxForm({
    form          : 'dep',
    fields        : [
        'department'
    ]
})(Department);

export default Department;

Any ideas on what I'm doing wrong? Or can I not use this component with redux-form?
Thank you!

I use material-ui with redux-form just fine, though I don't have any particular experience with DropDownMenu. You should be able to use any component as long as the API matches redux-form's assumptions. Redux-form is only going to communicate with the value and onChange props, which you might need to customize since you're playing around with valueMember and displayMember. Try creating a wrapper component that changes the API for redux-form's sake and transforms and passes the appropriate things along to DropDownMenu.

I have struggled mightily with material-ui Select fields.  The conclusion I finally came to was to use version 0.13.4 of material-ui.  This was based on the subset of material-ui components I was using and the material-ui creators also say the SelectField in 0.14.0 is a mess and they are right.  Half the fields are deprecated but still work yet, the alternative correct composability features do not work.  Use  SelectField instead of DropDownMenu if you can use 0.13.4 version of material-ui.  All this being said with not checking if things have changed in material-ui in the last week or so.
Here is an example of how I use it.  The ContentTypes variable is just an array of {id,name} fields.  The contentType variable is the redux-form field. err
<SelectField {...contentType}
floatingLabelText="Content Type"
valueMember="id"
displayMember="name"
menuItems={[{'id': '', 'name': ''}, ...ContentTypes]}
errorText={errorText(contentType)}
/>

Hi there, I'm using<EMAIL_ADDRESS>with redux-form. It plays well in most situation, however, when using SelectField component, its value couldn't be set correctly by redux-form. May be it's relevant to the signature of onChange props? SelectField using 3 params when calling onChange, and the 1st parameter (event) seems not matching the assumption of normal event.

redux-form@v6 has an example using Material UI
In the future, we recommend that you ask questions on StackOverflow first, and file issues if you’re confident the bug is in the library.


Decision threshold for distance below two meters

Where to find the issue
In solution_architecture.md under the topic LIMITATIONS: "we assume that an attenuation <50dB translates to a distance below two meters".
Describe the issue
Assuming an attenuation of 50dB to be the decision threshold may not be sufficient. Measurements we have done during a master students project at TU Berlin show that the decision threshold (path loss) should be much higher to catch all contacts below a distance of two meters. You can have a look on our measurement data as well as on our measurement report for details. If you have further questions or remarks regarding the measurements feel free to answer here or contact us privately.
Questions

Are there measurements planned or done to determine the decision threshold?
If yes, is it possible to publish those measurements or results on how precisely the distance can be estimated?
Are there any correction steps planned to normalize the attenuation for example based on the smartphone model?

From reading the Apple / Google specs I got the impression that the 50dB attenuation threshold is mentioned in the description of attenuationDurations, but the app has no influence on this. You have to work with Google / Apple to modify that. All the app can do is configure ENExposureConfiguration.
Any correction steps have to be done by Apple / Google inside their frameworks, because all the relevant data points never reach the app.
What we know already today, however, is that the Associated Encrypted Metadata (which contains the TX power value) is apparently not considered a fixed value, but recorded and stored by the Google framework for every single BLE reception. So we could anticipate that they probably try to detect the state of the mobile phone (on a table, in a pocket, driving in a car, ...) and
a) potentially change TX power based on that, and/or
b) send the state in the currently reserved space of the AEM (2 bytes), so that the receiving device can use this for a better estimation,
in future versions of the framework.

It is correct that the two fixed attenuation buckets are not ideal. Therefore two threshold values were introduced, forming three custom attenuation buckets.
Those new buckets are already used in the calculation of the combined risk (see solution architecture document), figure 13.

Dear @niclasku,
the previous answers already state precisely what has already been done on our side (and what can by done on top of the Apple/Google framework). In the end, it's up to Apple and Google to integrate and continue developing their framework based on research data. We will continue to do our best to incorporate and document additional aspects that we can influence - as already outlined by @tklingbeil.
As a consequence, we will close this issue now.
Mit freundlichen Grüßen/Best regards,
SW
Corona Warn-App Open Source Team

Thank you for the detailed answers! You are right that the framework does not allow anyone to modify the attenuation directly. However it is possible to set weights for the eight different attenuation ranges with attenuationLevelValues and the thresholds for the three attenuation buckets with attenuationDurationThresholds. Those configuration values will affect attenuation risk, exposure score and therefore the combined risk score. I am interested in the following (hopefully better formulated) questions:

How do you determine the attenuationLevelValues and attenuationDurationThresholds?
Are you able to test the configuration and are you going to test it?
Are you going to provide a test report on how precise the risk score would be for an ideal environment?

Dear @mh-, @tklingbeil,  @SebastianWolf-SAP,
for the documentation of this issue:
We are glad that you "acknowledged" this issue at least in the documentation & improved this issue 12 hours ago in this commit via lowering the threshold to 58 db.
Another problem still exists: without device-specific calibration, RSSI values can have different meaning on different devices. Eg. measuring 58dB on a Samsung Galaxy has a different meaning to measuring the same value on an iPhone.
Best Regards!

@JonasDaWi You are right that device-specific calibration makes sense. It has to be done by Apple / Google, though, because the CWA app has no chance to look at single beacon transmissions / receptions, this is all encapsulated in the Google / Apple framework. The app can only assume that Google / Apple do their best effort to estimate the actual attenuation as good as possible.

@mh-

It has to be done by Apple / Google, ...

Why?
Do they have an order for this?
Do they have an order to provide something to have a calibration-app, to make use of a large community to help?

@keugens What do you mean by "order"? I believe Apple / Google provide the Exposure Notifications Framework on their own account, they pay for that themselves.

Order in the sense: the client specifies what he needs.

@mh-
Do you think this is a new or unexpected issue?
For me not, if I am looking to the Singpore app, for example.

If we trust in what was said the Corona-Warn-App press conference even the whole "It's on Apple and Google"-Topic becomes obsolete, since it was explicitly stated (by Dr. Müller, SAP) that the German development team deeply cooperated with the engineers at Apple and Google in order to improve the functionality of this app. We should therefore not primarily concentrate on having discussions if Apple and Google have an order for this or not but more if the Corona-Warn-App team is somehow aware of this issue and if they even tried to address it towards Apple/Google. So however an official response would be suitable that tells us whether Apple/Google have been contacted regarding device specific corrections and if yes, whether a better solution approach is on its way or was denied (with or without any reason).
In addition it is very shady that this issue asked for official precision measurements, was never answered in that way but closed a day after its creation as if nobody wants to admit that the classification reliability is way worse as expected. But suddenly at the press conference precision measurements were mentioned that promise 80% classification precision, however again neither with sharing on how the measurements were performed nor how they got these numbers. The phrase "will be published within the next weeks" is not only suspicious because just days ago nobody knew about the measurements but also focusing the fact, that everything else was published on time and almost every other measurement that has been shared on the internet states a significantly worse reliabilty for the use of Bluetooth in distance estimation, especially in real-world scenarios.

Dear colleagues,
first, it's of course a combination of efforts by many parties - Google/Apple, the Robert-Koch-Institute, Fraunhofer IIS and many more. From our side, we can only repeat our statements that we will continuously update the parameters which we can influence. We also added the configuration values now explicitly to the risk assessment document, see https://github.com/corona-warn-app/cwa-documentation/issues/307
Moreover, the other statement also still remains true: "We will continue to do our best to incorporate and document additional aspects that we can influence". At the point of time when we closed the issue no detailed documentation about the respective precise measurements was planned - this is still the case. But we will continue to ask the responsible teams if and in which form they might be able to document their findings publicly which lead to the configuration values.
On the other hand, we have the cwa-wishlist repository for such requests in place by now. Consequently, we will reopen this ticket and move it to this repo for voting, further discussions etc.
Mit freundlichen Grüßen/Best regards,
SW
Corona Warn-App Open Source Team


Update links to repository to virtee org

Ref #24

If you think I should modify the author and author_email in setup.cfg to something more generic like "The VirTEE community" or something like that, let me know and I'll add it (the author appears in the PyPI page on the left side).

@fitzthum @dubek  I changed the settings to require 2 approvals before merging. If you think 1 is more appropriate, feel free to change.

If you think I should modify the author and author_email in setup.cfg to something more generic like "The VirTEE community" or something like that, let me know and I'll add it (the author appears in the PyPI page on the left side).

Either or is fine.


Rank all product lists according to user preferences

All lists of products in "choose" mode in Smoothie should be ranked and filtered according to the selected user preferences, with tabs ( #35 ) to separate matching and non-matching products, with colored product cards ( #33 ) and logos of the selected preferences ( #32 ).
This should apply in particular to:

List of scanned products (when accessing "my personalized ranking)"
Any saved list of products (e.g. products scan history)
Search results
List of products in a category (e.g. from category browser).

@stephanegigandet UX question: when I run searches on a group or a a keyword, am I supposed to

see first a "not ranked" page, then click on "personalized rankings" to get the list of ranked products (like right now)
directly see the list of ranked products with tabs and colors?

Another UX question: which actions/buttons lead to "List of scanned products (when accessing "my personalized ranking)" and "Any saved list of products (e.g. products scan history)". I guess that's a UX question worth an issue or two.

@stephanegigandet UX question: when I run searches on a group or a a keyword, am I supposed to

see first a "not ranked" page, then click on "personalized rankings" to get the list of ranked products (like right now)
directly see the list of ranked products with tabs and colors?

Another UX question: which actions/buttons lead to "List of scanned products (when accessing "my personalized ranking)" and "Any saved list of products (e.g. products scan history)". I guess that's a UX question worth an issue or two.

Fixed by #67.

Fixed by #67.