WIP: Starting an implementation of a ramp modifier. This is not close to b…

…eing fully implemented, but this is will be helpful for discussion.
@Yurlungur, @jdolence, @chadmeyer, Jeff Peterson (I can't find his handle)

[ ] reversible discussion
[ ] FillEOS finish
[ ] delta e finish
[ ] caching max discussion
[ ] caching alpha discussion
[ ] ctor, other necessary member functions

Some comments below. I'd add that I think when we implement FillEos we should think about it carefully. I imagine we can get something is more performant if you use it, as opposed to the per-var calls, to generate a bunch of quantities at once.

I think the most straightforward way to do this is via lambda. Is the quantity given by the function nlambda() a compile time constant, if so the offsets (pmax_index = nlambda of the underlying eos, alpha index = pmax_index +1, etc.). This seems like the most straightforward way to do things, but there is a problem that it will at best reduce performance by 50% (there will be one pressure evaluation + the other evaluations necessary). However, that loss should only be in the pre-crush phase for irreversible Eos's and I am hoping to put in machinery to avoid all extra calls after the crush phase. @Yurlungur I'm happy to think through a better design with you but passing through lambda seems like a decent option that is not overly burdensome to implement.

I think the most straightforward way to do this is via lambda. Is the quantity given by the function nlambda() a compile time constant, if so the offsets (pmax_index = nlambda of the underlying eos, alpha index = pmax_index +1, etc.). This seems like the most straightforward way to do things, but there is a problem that it will at best reduce performance by 50% (there will be one pressure evaluation + the other evaluations necessary). However, that loss should only be in the pre-crush phase for irreversible Eos's and I am hoping to put in machinery to avoid all extra calls after the crush phase. @Yurlungur I'm happy to think through a better design with you but passing through lambda seems like a decent option that is not overly burdensome to implement.

 But I'm not sure I understand why this should incur a performance hit. I would imagine that would be a significant performance improvement. I was more thinking about computing lambda once at the beginning of FillEos and then not again. Can't we do that?
I must be missing something.

I think the most straightforward way to do this is via lambda. Is the quantity given by the function nlambda() a compile time constant, if so the offsets (pmax_index = nlambda of the underlying eos, alpha index = pmax_index +1, etc.). This seems like the most straightforward way to do things, but there is a problem that it will at best reduce performance by 50% (there will be one pressure evaluation + the other evaluations necessary). However, that loss should only be in the pre-crush phase for irreversible Eos's and I am hoping to put in machinery to avoid all extra calls after the crush phase. @Yurlungur I'm happy to think through a better design with you but passing through lambda seems like a decent option that is not overly burdensome to implement.

 But I'm not sure I understand why this should incur a performance hit. I would imagine that would be a significant performance improvement. I was more thinking about computing lambda once at the beginning of FillEos and then not again. Can't we do that?
I must be missing something.

@Yurlungur I think our comparison baselines are different. Yes, adding the alpha into lambda will be better than not doing so. However, my comparison was against the raw underlying eos call. Suppose you wanted the specific heat and you passed in an alpha that was correct. The solver would have to call the pressure at least once to verify that the passed in alpha was correct before moving to the specific heat call. That means for each call, there is going to be at least 2 eos calls whereas for the underlying eos, there is 1 eos call, that is how I get my factor of 2. Perhaps there is some way to communicate to the underlying eos calls that alpha is converged and skip the extra calls. Again, I think for most ramps, this won't have a huge performance effect across the entirety of the calculation since ramps are typically somewhat short lived.

@Yurlungur I think our comparison baselines are different. Yes, adding the alpha into lambda will be better than not doing so. However, my comparison was against the raw underlying eos call. Suppose you wanted the specific heat and you passed in an alpha that was correct. The solver would have to call the pressure at least once to verify that the passed in alpha was correct before moving to the specific heat call. That means for each call, there is going to be at least 2 eos calls whereas for the underlying eos, there is 1 eos call, that is how I get my factor of 2. Perhaps there is some way to communicate to the underlying eos calls that alpha is converged and skip the extra calls. Again, I think for most ramps, this won't have a huge performance effect across the entirety of the calculation since ramps are typically somewhat short lived.

AH, yes. This is true. This is why I'm so focused on FillEos. I think you can amortize the cost somewhat there. i.e., if you want specific heat (say) Pressure, you can compute alpha first, so you need 3 EOS calls instead of 4 for the naive approach or 2 for the no-ramp case (assuming you pass in the right alpha in the lambda).

I still don't fully understand the Menikoff and Kober approach to energy but it will throw a wrench in things a bit. I agree with @chadmeyer 's comment that we shouldn't emulate other approaches for the sake of emulation but try to have the right approach here and hopefully it can get some proper V&V in the future.
In that spirit, let me think a bit about how to deal with the energy and I may be able to propose some small changes. For the moment, just know that the energy may need to be a function of alpha and perhaps a compaction potential parameter.

I think the energy modification is just a function of alpha (An integral of the potential maybe?)  I’d have to check for sure.

Bits have rotted. We're closing this PR for now.

Do not delete branch---still needed as a reference.

@dholladay00 do we still need this branch? Probably not right?

I'd still like to have it. This shows how to implement a p-alpha model so I'd like to keep this somewhere so that I don't have re-understand the details.


Add Shovel option to specify $all start position

@npiani  This looks like a good idea, I'd be happier if both the commit and prepare parts of the position could be specified.


chore(main): release 2.2.0

:robot: I have created a release beep boop
2.2.0 (2024-11-25)
Features

add translation (#297) (c2df927)
allow reset config to initial state (#296) (bca1c73)
remove redundant custom rules and add rules reported by users (#295) (37a4e62)
unify and beautify the options page style (#294) (1afb2dc)

Bug Fixes

property registered error will be reported if repeatedly navigate to welcome page (#290) (ceeb03f)
style: buttons are not aligned (#300) (47ecd70)
website: card lacks reflective effect (#291) (a41307b)
website: card opacity is 1 when the first screen is loaded (#292) (3acf556)

Miscellaneous Chores

release 2.2.0 (40faa7f)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v2.2.0
:sunflower:


Upgrade to Gradle 7.4.2

see the individual commit messages for further details.
the mentioned warnings from the gradle build are (run the build with --warning-mode all to see them):
The RepositoryHandler.jcenter() method has been deprecated. This is scheduled to be removed in Gradle 8.0. JFrog announced JCenter's sunset in February 2021. Use mavenCentral() instead. Consult the upgrading guide for further information: https://docs.gradle.org/7.4.2/userguide/upgrading_version_6.html#jcenter_deprecation
        at build_4af0033qgyebai2fyambcejr4$_run_closure1$_closure3.doCall([..]\prometheus-exporter-plugin-for-opensearch\build.gradle:88)
        (Run with --stacktrace to get the full stack trace of this deprecation warning.)

See also the Gradle blog post about this: it's probably save to just remove this line as there's already the dependency to maven central in place:
https://github.com/aiven/prometheus-exporter-plugin-for-opensearch/blob/291e3658701c30e06577351c1c3867eb0ad12e0e/build.gradle#L102
i haven't looked into these:
> Task :copyRestApiSpecsTask
Relying on FileTrees for ignoring empty directories when using @SkipWhenEmpty has been deprecated. This is scheduled to be removed in Gradle 8.0. Annotate the property inputDir with @IgnoreEmptyDirectories or remove @SkipWhenEmpty. Consult the upgrading guide for further information: https://docs.gradle.org/7.4.2/userguide/upgrading_version_7.html#empty_directories_file_tree

> Task :forbiddenApisMain UP-TO-DATE
Relying on FileTrees for ignoring empty directories when using @SkipWhenEmpty has been deprecated. This is scheduled to be removed in Gradle 8.0. Annotate the property classFiles with @IgnoreEmptyDirectories or remove @SkipWhenEmpty. Consult the upgrading guide for further information: https://docs.gradle.org/7.4.2/userguide/upgrading_version_7.html#empty_directories_file_tree

> Task :filepermissions UP-TO-DATE
Relying on FileTrees for ignoring empty directories when using @SkipWhenEmpty has been deprecated. This is scheduled to be removed in Gradle 8.0. Annotate the property files with @IgnoreEmptyDirectories or remove @SkipWhenEmpty. Consult the upgrading guide for further information: https://docs.gradle.org/7.4.2/userguide/upgrading_version_7.html#empty_directories_file_tree

> Task :licenseHeaders
Relying on FileTrees for ignoring empty directories when using @SkipWhenEmpty has been deprecated. This is scheduled to be removed in Gradle 8.0. Annotate the property javaFiles with @IgnoreEmptyDirectories or remove @SkipWhenEmpty. Consult the upgrading guide for further information: https://docs.gradle.org/7.4.2/userguide/upgrading_version_7.html#empty_directories_file_tree

@rursprung the @SkipWhenEmpty  deprecations will go away with 2.1.0 update

perfect! sorry, i didn't consider to check that again when i tested the 2.1.0 build as i didn't realise that it was coming from there :/


[release-2.3] build refresh

Addresses:

https://github.com/stolostron/backlog/issues/22116
https://github.com/stolostron/backlog/issues/22155

This PR is waiting for the CRD fix:

https://github.com/stolostron/governance-policy-propagator/pull/209

/auto-cc


Set14 dataset miss Set14_003.img!!!

as shown before

@Jackson-LIMU you could add that image to your dataset, as I remember, it's a gray image, so I remove that. You could add that and then change code to be compatible with gray image.


Incoherent training and validation metrics in recommender system example

In the recommender system examples, the Binary Predictions notebook uses different metrics for training and validation. Training is using MAERegressionOutput within CosineLoss whereas eval_metric is RMSE, as defined in matrix_fact.py
In other examples, when using LinearRegressionOutput, training metric is the same as RMSE. But this is not the case for general output layers. And moreover I don't find a way to use a typical metric as crossentropy for training and validation. This problem is related to https://github.com/apache/incubator-mxnet/issues/6179

proposed labels: "Python", "Example", "Discussion", "Metric"


Typos correction

Dear Geert Jan Bex,
I was going through this awesome repository on Fortran-MOOC. I came across some typos which can be corrected. I am still going through other parts of this repository and will try to suggest further improvement. By the way this is one of the best Fortran resources that I could find in internet. Thanks for making it.
I could not locate a development branch so creating a merge request to master branch.

Thanks for the pull request, unfortunately I can't merge it without changes (see comments).
You point out some good points, I'll correct the typos you mention.

Thank you for your reply. I have taken care of points you have mentioned. Please check.


provide devbox git configuration layer

This is going to replace cnav config from https://github.com/viqueen/codenav
We want a new command git devbox which should let us define the following properties

devbox.sources.root
devbox.workspace
devbox.github.username
devbox.github.personal.token

resolved by #3


FIX: Fix gamma_map

@agramfort I think this should make the test more robust (and restores a broken one!). Let me know if you think it's too lenient.

fine with me but travis is not happy yet

Yeah, seems like the code is broken worse than I expected :(

@agramfort unfortunately I think you'll need to take over. The STCs on my system have a handful of verts per hemi (e.g., (4, 30) for left and right hemi), but on the failed builds they have e.g. (3956, 3972).

...and I can't reproduce locally with my Anaconda setup :(

It appears as though the issue has been magically fixed.


[Content block mixed] - Storybooks QA

General issues
1. Rename it in as:

Content block mixed
    Default
    With link list

from this

2. Heading bottom spacing should be 32px - Styles Package
3. Intro copy has the wrong size token (or no token). It should be this:  Styles Package

4. This is a subheading, please remove the full stop/period/full point.

5. Please make sure the cards respect the content height rules.

6. Please make sure the card link respects the specs. Also, make sure, please, that the max-width of 320px is applied regardless of the viewport.
What its expected to be

What is is

7. The pictograms should be 80px X 80px.

8. Please, make sure the pictogram item component respects the specifications.
What i see:

What I should see:

9. On Gray 100, the caption is the wrong type token:

10. Please align the link list component icons to the containers:
What I see:

What I should see:

Detailed description

Describe in detail the issue you're having.

Is this a feature request (new component, new icon), a bug, or a general
issue?

Is this issue related to a specific component?

What did you expect to happen? What happened instead? What would you like to
see changed?

What browser are you working in?

What version of Carbon for IBM.com are you using?

What offering/product do you work on? Any pressing ship or release dates we
should be aware of?

Steps to reproduce the issue

Step one
Step two
Step three
etc.

Additional information

Screenshots or code
Notes

@DragosRistici 5. This will likely need to be addressed in another issue. The same problem can be observed in the Content Group Cards story.


ch1280 Poc collab

Added modification to client/collab to send/receive changes through serverless central authority (document-collab package)

[ch1280]

[ch2070]

[ch2080]


Artifacts when rendering mitered paths

Attach (recommended) or Link to PDF file here:
test_miter.pdf
Configuration:

PDF.js version: 3.6.126 [3f89a99a5]
Browser & version: Firefox 114.0.1
Operating system: Manjaro Linux
Is a browser extension: No

Steps to reproduce the problem:

view a pdf containing a path with many short connected segments. The path should have its "stroke-linejoin" property set to "miter"

What is the expected behavior? (add screenshot)

What went wrong? (add screenshot)

Configuration:
PDF.js version: 3.6.126 [3f89a99a5]

What about the rest of the Configuration:-section, since you've left out details about both the browser and OS used?

WFM, using PDF.js version 3.8.107 [03059e1f8] in Firefox Nightly 116.0a1 on Windows 11.

What about the rest of the Configuration:-section

fixed

I can confirm that this issue also occurs in the latest Firefox nightly on Android.

I can reproduce the bug with Firefox on mac with the pref gfx.canvas.accelerated set to true.
I filed this bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1841020


invalid_part should have an error code

All algorithms should strive to propagate the correct error code

Parsing is rewritten, this is obsolete


x11: analog triggers for ps4 gamepad

I always wondered why the triggers are button events instead of axes for this pad.
Well, turns out the hardware sends both, but SDLs mapping chose to use the buttons...

Does it also send the button event? I have a game that uses it (on an
actual ps4 too :p )
On 13 February 2016 at 19:22, George Marques<EMAIL_ADDRESS>wrote:

Assigned #3705 https://github.com/godotengine/godot/pull/3705 to @punto-
https://github.com/punto-.
—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/pull/3705#event-549641677.

Yes, of course ^^

awesome!
On 13 February 2016 at 19:30, Hondres<EMAIL_ADDRESS>wrote:

Yes, of course ^^
—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/pull/3705#issuecomment-183766355.


Unsuitable semantics for long running processes

Consider a program which runs indefinitely:

A gcslock.Lock(l, time.Second) fails, for any reason.
The underlying locking goroutine will keep running indefinitely, until it succeeds.

[In the meantime, another path of the program may have successfully acquired and released the lock]

At last, the goroutine initially started in step 1 succeeds.
Inconsistent state. Next gcslock.Lock will never succeed now, until the lock is removed by an external job.

One solution is to simply limit goroutine retries to some max.

Another solution is to stop the locking/unlocking goroutine before returning an error.

Actually, limiting num. of retries of a locking goroutine won't work. I believe the best approach is to always terminate the locking/unlocking goroutine before returning.

So, some code which does something like this in a goroutine?
for {
  err := gcslock.Lock(l, time.Second)
  if err == nil {
    break
  }
}

The timed Lock fails for any reason (e.g. timeout), and some other part of the same program gets and releases the lock. Won't this loop eventually obtain the lock properly? Not seeing the inconsistency.

That example is not a long running process. This one is:
// Loop indefinitely processing one task at a time.
for {
  // Receive a new task from a channel ch.
  task := <- ch
  // Try to obtain a global lock or skip the task, reporting the error.
  if err := gcslock.Lock(l, time.Second); err != nil {
    reportf("lock failed: %v", err)
    // Lock failed so we skip the task and wait for a new one.
    // Unfortunately, the above lock goroutine will keep running,
    // trying to acquire a lock we don't need anymore.
    continue
  }
  execute(task)
}

Most importantly, whenever the above gcslock.Lock(l, time.Second) fails, the underlying gcslock goroutine will needlessly keep trying to acquire the lock and may very well succeed at some point. Meaning, any future "useful" gcslock.Lock(l, time.Second) will never succeed anymore, until the lock is removed by an external process.
This is very similar to what would happen in the case with push-to-publish git lock.
What I think needs to happen instead is for the locking goroutine to stop even if gcslock.Lock returned an error, instead of keep running.

I get it. Thanks for clarifying. I need to stop the goroutine when I get a timeout, something like this:
  case <-time.After(d):
    // stop running goroutine here
    return errors.New("lock request timed out")

Looks like there's no way to externally stop a goroutine but I'm sure there's some trick I can use. Will do some googling.

Exactly, the // stop running goroutine here part is what's missing.
The locking loop needs to be controlled and stopped - it currently never exits.

There's no built-in way to stop a goroutine via some kind of a "goroutine handle" but it can be controlled using a context.WithTimeout or a channel. I would probably use a context with a deadline equal to the d argument passed to gcslock.Lock.

On it, first thing tomorrow am. Thanks!

This looks like exactly my scenario: http://dahernan.github.io/2015/02/04/context-and-cancellation-of-goroutines/

sync.WaitGroup feels like an overkill just for one goroutine:

A WaitGroup waits for a collection of goroutines to finish ...


[ALLUXIO-3301] change watermark.high.ratio default value to 0.95

(https://alluxio.atlassian.net/browse/ALLUXIO-3001)

Build finished. Test PASSed.

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


Add 4xx responses from spec to openapi.yaml and swagger.yaml

What is the problem this PR solves?
This Pull Request adds 404 and 422 as permitted responses to the openapi.yaml and swagger.yaml where contextually appropriate.
Specifically, it adds 422 as an acceptable response to unbinding requests in the openapi.yaml, as documented in the spec:
https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md#unbinding
and as provided in the swagger.yaml:
https://github.com/openservicebrokerapi/servicebroker/blob/master/swagger.yaml#L371-L372
Furthermore, it adds 404 as an acceptable response to the last_operation requests on service instances and service bindings. While not explicitly documented in the spec, 404 is an acceptable response for the parent URIs in question:
/v2/service_instances/:instance_id => https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md#response-4
/v2/service_instances/:instance_id/service_bindings/:binding_id => https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md#response-7
Which suggests that these should also be permitted responses in the case of child responses.
Given that 9de42fd introduces a slight behavioral change in the API, I am happy to revert it if that is deemed appropriate.
Finally, it adds 401 Unauthorized as an acceptable response in the openapi.yaml. This is a permitted response per the spec and the swagger.yaml.
Checklist:

[x] The swagger.yaml doc has been updated with any required changes
[x] The openapi.yaml doc has been updated with any required changes

Thanks for this @treznick!
If we're adding 404s as an acceptable response for last operation calls in the openapi docs, we should probably add them to spec.md too in the appropriate response tables (here and here). I personally don't have any problems with adding 404 responses to those endpoints - @fmui @tinygrasshopper any thoughts?
Let me know if you have any trouble signing the CLA @treznick

@mattmcneeney You're very welcome!
I added 404s as acceptable responses to the tables you mentioned in this commit: 409d097
As for the CLA I am working with legal at my employer to figure out the best way to sign (and whether I can sign as an individual contributor). I will keep you all apprised.

I can confirm that this change won’t break anything in CF, although the error message may suggest that the broker has responded with an invalid code unless we add support for this.

Closing and reopening to retrigger Travis

@mattmcneeney CLA should be signed, can we re-run the checks here? /cc @treznick

Hey @lyubo1 - It still doesn't seem to be working. I tried closing and reopening which usually triggers the check but it still says it's missing

@mattmcneeney @lyubo1 I have signed the CLA. Please let me know if you need anything further.

Perfect, thanks @treznick I can see it's all green now. Time for some reviews! Ping @openservicebrokerapi/osbapi-pmc

ping @fmui


DBZ-4760 Avoid improper Redis OOM error log

@spicy-sauce, any thoughts on this one?

@spicy-sauce, any thoughts on this one?

I saw that usually you won't get this message "EXECABORT Transaction discarded because of: OOM command not allowed when used memory > 'maxmemory'." when Redis runs into OOM but this one ""EXECABORT Transaction discarded because of previous errors.".  The other message will be thrown afterwards...
@sazzad16 WDYY?

@spicy-sauce EXECABORT Transaction discarded because of previous errors. errors can be thrown in many cases. Always logging OOM for all those cases is just wrong and completely misleading.

@spicy-sauce EXECABORT Transaction discarded because of previous errors. errors can be thrown in many cases. Always logging OOM for all those cases is just wrong and completely misleading.

I totally agree with you, but the root issue here is that you cannot identify OOM accurately - is it a Jedis thing?
If EXECABORT Transaction discarded because of previous errors. is thrown while Redis ecnounters OOM and as result the Debezium server crashes, the whole feature is unusable.
Let's take this discussion offline and see what is the best to tackle it.

I totally agree with you, but the root issue here is that you cannot identify OOM accurately - is it a Jedis thing?

Would it look any better when using the Quarkus client, as was suggested in one Jira issue the other day?

Let's take this discussion offline and see what is the best to tackle it.

Do you both work for the same organization? If so, a quick chat may help to speed up things. Ideally, you'd have that discussion on the "dev" channel in the Debezium Zulip. Our motto is "default to open", the more discussions we can have in the public, the better. That way, decision processes become more transparent, and others can raise their voice too.

I totally agree with you, but the root issue here is that you cannot identify OOM accurately - is it a Jedis thing?

No, that's a Redis thing.

I totally agree with you, but the root issue here is that you cannot identify OOM accurately - is it a Jedis thing?

No, that's a Redis thing.

Let me check this and get back to you.

OK, this issue can be indeed considered as a Redis' one. For now, I think we should do the following:

As @sazzad16 stated, it's better not to identify this generic error message as a OOM one as it's might not be the case. But since this exception is thrown also in this case, we should catch it separately and do not throw a DebeziumException that ends up with stopping the Denezium Server.
Before I changed the sink to work with batches (via Pipeline) we could identify the OOM in 100% accuracy. I'll check why it's not the case when working with Pipelines and hopefully a fix will be provided - but since backward compatibility is important, we still need to embrace point number 1.

@sazzad16 Are you OK with me providing a new PR or you'd like to do it? I'll be happy to.

it's better not to identify this generic error message as a OOM one as it's might not be the case. But since this exception is thrown also in this case, we should catch it separately and do not throw a DebeziumException that ends up with stopping the Denezium Server.

@spicy-sauce I think this PR does what you're suggesting because throwing DebeziumException is only being done from else block.
https://github.com/debezium/debezium/blob/67072f0dc67098ac440024315157b0eb4a33458b/debezium-server/debezium-server-redis/src/main/java/io/debezium/server/redis/RedisStreamChangeConsumer.java#L192-L195
If you think this isn't what you're suggesting, I won't mind you creating another PR.

Currently JedisDataException' EXECABORT Transaction discarded because of previous errors. will throw a DebeziumException.
We can either:

Add another if for checking EXECABORT Transaction discarded because of previous errors message, logging it without throwing a DebeziumException.
Change this:

else {
     LOGGER.error("Unexpected JedisDataException", jde);
     throw new DebeziumException(jde);
 }

to
else {
LOGGER.error("Unexpected JedisDataException", jde);
}
But this means that and other JedisDataException will be tolerated, maybe it's preferred, come to think of it.
So yes, just remove line 194 and we are good to go.
Thanks!

@spicy-sauce

Currently JedisDataException' EXECABORT Transaction discarded because of previous errors. will throw a DebeziumException.

Nope. Following is the current code
https://github.com/debezium/debezium/blob/b0765e9492a037738eeaa0dc4739394c14919952/debezium-server/debezium-server-redis/src/main/java/io/debezium/server/redis/RedisStreamChangeConsumer.java#L181-L184
which handles concerned scenario and it does not throw DebeziumException.

So yes, just remove line 194 and we are good to go.

Do you still want this?

@spicy-sauce

Currently JedisDataException' EXECABORT Transaction discarded because of previous errors. will throw a DebeziumException.

Nope. Following is the current code
https://github.com/debezium/debezium/blob/b0765e9492a037738eeaa0dc4739394c14919952/debezium-server/debezium-server-redis/src/main/java/io/debezium/server/redis/RedisStreamChangeConsumer.java#L181-L184
which handles concerned scenario and it does not throw DebeziumException.

Yep, this was OK, but then you said that it's not a good ideal to log an OOM error while it's not always the case.
So you removed the other generic error message which is fine.

So yes, just remove line 194 and we are good to go.

Do you still want this?

But now, in case of getting this EXECABORT Transaction discarded because of previous errors., it will end up with the Unexpected JedisDataException and debezium server will be terminated.
I think that removing line 194 is better (in addition to your change).
Does it make sense?

But now, in case of getting this EXECABORT Transaction discarded because of previous errors., it will end up with the Unexpected JedisDataException and debezium server will be terminated.

@spicy-sauce No.
Please carefully review the codeblock:
https://github.com/debezium/debezium/blob/67072f0dc67098ac440024315157b0eb4a33458b/debezium-server/debezium-server-redis/src/main/java/io/debezium/server/redis/RedisStreamChangeConsumer.java#L177-L196

More specifically,
Following codeblock handles EXECABORT Transaction discarded because of previous errors. and does not end up with the Unexpected JedisDataException:
https://github.com/debezium/debezium/blob/67072f0dc67098ac440024315157b0eb4a33458b/debezium-server/debezium-server-redis/src/main/java/io/debezium/server/redis/RedisStreamChangeConsumer.java#L184-L186
ONLY following codeblock ends up with the Unexpected JedisDataException:
https://github.com/debezium/debezium/blob/67072f0dc67098ac440024315157b0eb4a33458b/debezium-server/debezium-server-redis/src/main/java/io/debezium/server/redis/RedisStreamChangeConsumer.java#L192-L195

Oh, I missed that! sorry!
Great then, we can merge @gunnarmorling
Thanksm @sazzad16!

Sweet, thanks a lot. Applied!


Extend Terraform configs for Azure with more operating systems

What this PR does / why we need it:
This PR extends Terraform configs for Azure with options to choose an operating system other than Ubuntu. The following changes are made:

A new variable os is introduced used to select OS for both control plane nodes and MachineDeployments
A new variable image_references is introduced with references for all operating systems supported on KubeOne and available on Azure. I've used data from machine-controller for this variable
worker_os variable is defaulted depending on the value of os variable
ssh_username variable is defaulted depending on the value of os variable

What type of PR is this?
/kind feature
Does this PR introduce a user-facing change? Then add your Release Note here:
Introduce a new `os` variable (defaults to `ubuntu`) in Terraform configs for Azure to allow choosing an operating system other than Ubuntu

Documentation:
NONE

/lgtm
/approve


Modify github action to push RELEASED database to SIMPLE-binary

Current github action (gen-db.yml) pushes the latest build of the database. we want to modify that action so it only pushes the latest RELEASED version.

https://stackoverflow.com/questions/58475748/github-actions-how-to-check-if-current-push-has-new-tag-is-new-release

Should be straightforward to use on: release instead of on: push.
See the docs for on: release here: https://docs.github.com/en/actions/reference/events-that-trigger-workflows#release


Allow configure gitsigns sign priority

In most cases, gitsigns should always be the rightmost, otherwise, other signs will break the line made of gitsigns.
Allow users to configure the priority.
Before(default priority):

After(priority = 100):

Thanks.

I've updated the code in b0353e32e321141f095b681c47e0e29101007680 so that there is now a separate priority for each type.
Before:
require('scrollview.contrib.gitsigns').setup({
    priority = 100
})

After:
require('scrollview.contrib.gitsigns').setup({
    add_priority = 100,
    change_priority = 100,
    delete_priority = 100,
})


use builtin graceful shutdown

The go http server now has a built-in graceful shutdown: func (*Server) Shutdown.  This is good news, because the BeginShutdown/ConnStateChange stuff in hummingbird/server.go that attempts to implement this is almost certainly beyond saving.
The only thing is I'm not sure about if you still need to call SetKeepAlivesEnabled(false) so connections are closed once they go idle, or if Shutdown() has this functionality built in.

After reading the code it seems like we don't need to call SetKeepAlivesEnabled
https://github.com/golang/go/blob/release-branch.go1.8/src/net/http/server.go#L2718
Also shutdown won't handle hijacked connection(I guess we only use that for Replication) and also Shutdown will probably wait indefinite for connection to get idle. However I guess we can use pass context in Shutdown to handle timeout.


Update Singularity release

Update to Singularity release to fix broken CI

Thanks for the quick and simple fix!


CoffeScript: Not getting all errors

I was trying the coffescript syntax checker and I found out that not syntax errors are beign captured.
To reproduce it write 'function' on any coffee file
Here is the generated error by 'coffee':
SyntaxError: In simpleMapComponent.js.coffee, Reserved word "function" on line 10
 at SyntaxError (unknown source)
 at Lexer.identifierError (/usr/lib/node_modules/coffee-script/lib/lexer.js:458:13)
 at Lexer.identifierToken (/usr/lib/node_modules/coffee-script/lib/lexer.js:80:16)
 at Lexer.tokenize (/usr/lib/node_modules/coffee-script/lib/lexer.js:31:19)
 at Object.compile (/usr/lib/node_modules/coffee-script/lib/coffee-script.js:29:34)
 at /usr/lib/node_modules/coffee-script/lib/command.js:149:33
 at /usr/lib/node_modules/coffee-script/lib/command.js:115:26
 at [object Object].<anonymous> (fs.js:107:5)
 at [object Object].emit (events.js:61:17)
 at afterRead (fs.js:878:12)

Hey, I have made a fix for this - see the commit log above.
I dont actually code coffescript so I cant really say whether the errorformat in the syntax checker needs more work or not.
Ill close off this task and message @lstoll (who wrote the code). If there any more problems then just comment here with the new error and ill reopen the bug.

@scrooloose It worked here (: Thank you!


Anchor test not a directory

I trying to run anchor test  , But an error:
BPF SDK: /Users/xxx/saftware/solana-release/bin/sdk/bpf
cargo-build-bpf child: rustup toolchain list -v
cargo-build-bpf child: rustup toolchain link bpf /Users/xxx/saftware/solana-release/bin/sdk/bpf/dependencies/bpf-tools/rust
error: not a directory: '/Users/xxx/saftware/solana-release/bin/sdk/bpf/dependencies/bpf-tools/rust/lib'

It is not an anchor issue. Most probably you have corrupted solana tool suite due to an update. You need to remove the tool suite completely and reinstall it. At least these directories, maybe some others too:

~/.cache/solana/
~/.local/share/solana

Thanks for your reply。

You need to remove the tool suite completely and reinstall it

How do I remove the suite?


Context menu doesn't open at mouse cursor position

See this image:

When I right click to open the context menu, there's a few pixels in between the mouse cursor and the top-left corner of the context menu. It seems to get worse on the right side of the screen. I would expect the context menu's top-left corner to coincide with the mouse position. I could replicate this in safe mode, but not in google chrome v45.0.2454.99.
System details:
Atom 1.2.0-dev-0145ae3
Debian 9 with Openbox window manager

Came here to open the same issue, I first noticed this after upgrading from Atom 1.0.0 to 1.0.15 (a few days ago).
Additional details
OS: Ubuntu 14.04 (64 Bit)
Atom: 1.0.15
Theme (UI): Seti (but also happens with default themes)

same problem here

Yes, I'm using two monitors, one on the right of the monitor Atom is on. My monitors are aligned at the top, though. The issue is much worse with Atom on the right monitor.

okay :) I was close, then it has to do something with resolution of monitors. Maybe there is function in code which align context menu according to desktop size.

The weird thing is, though, that I have the same problem in the vertical direction. The lower I click in the Atom window, the more the vertical offset to the menu is. This can even cause the menu to go completely off-screen. And I definitely don't have a monitor "below" my monitor with Atom.

yeah I know :) I have same exact problem. Ill remove atom and delete all folders and stuff and try to install it without dual monitors. I had no problem with old version.

I'm experiencing this too. Ubuntu Mate, dual monitors.

@Dumr Well... context-menu.coffee:8 is just passing an electron BrowserWindow (I think it's that one, but please correct me if I'm wrong) instance to electron's Menu class' popup method, which should map to Menu::Popup, but I don't know C++ and I don't really understand what's going on after that :fearful:...

okay with latest build from source from github it works for me now.

Nope, still happening for me. Which branch did you build?

fdb1642 or in other words 'v1.1.0-beta1'

It's still present on the master branch on my machine. I'll try 1.1.0-beta1

I have the exact same isse on Ubuntu 15.04, dual monitor setup.

Just upgraded to 1.0.19 and the offset is even worse than before.

I reckon it's the same bug that exists in Chromium, and has now landed into Atom as well.  :P

So is this a problem with Atom or Ubuntu?

Just saying they are related, maybe. No other software affected in my case.

@rnyberg adjusting the scaling does not fix it.
@lightradius there's a similar bug in Chrome/Chromium. I'd say it is a Atom issue on Ubuntu rather than a Ubuntu issue.

@kevingimbel I'm running on Ubuntu 14.04 and setting scaling to 1 works for me. I reckon it's separate issue then.

There have been a few reports in this thread that 1.1.0-beta1 has fixed the problem for some people. If you can, try out the beta, or wait until 1.1.0 stable is out before chiming in that you also have this problem. By all means please update this thread if you are seeing similar issues in 1.1.0 though.

I'm seeing this issue in 1.1.0.
OS: Ubuntu 14.04 (64 Bit)
Atom: 1.0.15
Monitor Configuration: two identical 24" monitors at 1920x1200 with scale for menu & title bars set to 0.875
On the left-hand monitor (where I do most of my editing), the context menu appears about 3" to the right and 1.5" below the mouse pointer.
If I move the editor to the right-hand monitor, I can't see the context menu at all.
Resetting the scaling to 1.0 does not fix the issue - now the menu appears about 2.5" to the right & either 1.5" above or below the pointer, depending on whether I'm near the bottom or top of the screen.

Quick Update: I've tried the 1.2.0-beta0 release and the issue is still present.
OS: Ubutnu 14.04
Atom: 1.2.0-beta0
A possible workaround, for me, is setting the internal, smaller screen to display at 1,12x scale and the external to ~0.75x scale. Then the context menus appear in the correct position. However, this isn't a real fix or solution because the UI of everything becomes rather blurry/ugly when using this setup.
I believe this issue is somewhat related to Chrome/Chromium since the I see a similar issue in those browsers.

+1 I have the same behavior
OS: Devuan Jessie
Atom: 1.0.15
I have the nvidia proprietary drivers, I don't know if that is related....

OS: Ubuntu 14.04 x64
Atom: 1.2.4
Display: two identic 24" 16:9 HD panels
I'm able to reproduce the issue on my system, but only if I set the menu scale of the primary monitor to something other than 1. Having atom on another monitor and this very monitor's scale on, say, 0.875,  the context menu is aligned correctly. On the other hand, if the primary monitor gets scaled, no matter where atom is open, the context menu pops up away from the cursor again.

Setting my second monitor's scale to 1.12 in Ubuntu's display settings solved the issue for me.
I have no idea why, but the context menu is now aligned with the mouse cursor.

Additional information here:
https://discuss.atom.io/t/right-click-menu-misaligned/22050

I'm facing the same issue although I'm using only one monitor.
System:
GPU: nVidia GTX 560 (Assus)
Driver: 358.16
OS: Arch Linux
Kernel: <IP_ADDRESS> LTS
Atom: 1.3.2

Having the same Issue. BUT when i do a rightclick in the first 1/5th of the window (about the default size of the tree-view) or up to the menu entrie "Find" (Menu Bar) it opens on the correct screen. Any clicks further to the right open up on the next monitor to the right.
System:
GPU: nvidia GTX970
Monitors: 3
Driver: 361.28
OS: Arch Linux
Kernel: 4.4.5-1
Atom 1.5.4

I just upgraded to Atom v1.9.0-dev-c95412b and now the issue is gone!

:tada:
If anyone can still reproduce this on 1.9.0 please comment here!


CLI should have/surface error message if Docker is not running

Feature Request
Desired behaviour
Currently CLI will fail if Docker is needed for a workflow, but not running. There is no error message indicating this is the problem. Cromwell engine potentially outputs a related error message that shows when running Cromwell manually, but Dockstore CLI doesn't surface this to the user. This feature is more relevant for users who need to manually start up Docker, like in Docker Desktop for Mac.
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 1.6
┆Issue Number: DOCK-239

Implementor can consider tackling at the same time as #1876

Is this is issue that came from Vincent?
Hi -- I had the misfortune of attempting to use the CLI when my docker
desktop had died.  The error messages were not particularly helpful and only
when I tried to use cromwell manually did I come to an understanding
of the situation.  Perhaps the CLI could check for running docker and
fail with a clear message if such is not found?
dockstore workflow launch --entry github.com/vjcitn/dsdemo:master --json dsdemoInputs.json
Downloading Dockstore to /Users/stvjc/.dockstore/self-installs/dockstore-client-1.6.0-alpha.5.jar now...
https://github.com/ga4gh/dockstore/releases/download/1.6.0-alpha.5/dockstore-client-1.6.0-alpha.5-shaded.jar
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100   631    0   631    0     0   1561      0 --:--:-- --:--:-- --:--:--  1565
100 46.2M  100 46.2M    0     0  1853k      0  0:00:25  0:00:25 --:--:-- 1253k
Creating directories for run of Dockstore launcher in current working directory: /var/folders/5_/14ld0y7s0vbg_z0g2c9l8v300000gr/T/1549206345936-0
Provisioning your input files to your local machine
Calling out to Cromwell to run your workflow
java jar /Users/stvjc/.dockstore/libraries/cromwell36.jar run /var/folders/5_/14ld0y7s0vbg_z0g2c9l8v300000gr/T/1549206345936-0/run1.wdl --inputs /var/folders/5_/14ld0y7s0vbg_z0g2c9l8v300000gr/T/foo1724821479851536343json
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.access$200(DefaultExecutor.java:48)
at org.apache.commons.exec.DefaultExecutor$1.run(DefaultExecutor.java:200)
at java.lang.Thread.run(Thread.java:745)
10:06:30.640 [main] ERROR io.github.collaboratory.wdl.WDLClient - Problem running cromwell:
java.lang.RuntimeException: problems running command: java jar /Users/stvjc/.dockstore/libraries/cromwell36.jar run /var/folders/5_/14ld0y7s0vbg_z0g2c9l8v300000gr/T/1549206345936-0/run1.wdl --inputs /var/folders/5_/14ld0y7s0vbg_z0g2c9l8v300000gr/T/foo1724821479851536343json
at io.dockstore.common.Utilities.executeCommand(Utilities.java:142)
at io.dockstore.common.Utilities.executeCommand(Utilities.java:88)
at io.github.collaboratory.wdl.WDLClient.launch(WDLClient.java:202)
at io.dockstore.client.cli.nested.WorkflowClient.launch(WorkflowClient.java:439)
at io.dockstore.client.cli.nested.AbstractEntryClient.processEntryCommands(AbstractEntryClient.java:236)
at io.dockstore.client.cli.Client.run(Client.java:706)
at io.dockstore.client.cli.Client.main(Client.java:608)
Caused by: org.apache.commons.exec.ExecuteException: problems running command: java jar /Users/stvjc/.dockstore/libraries/cromwell36.jar run /var/folders/5_/14ld0y7s0vbg_z0g2c9l8v300000gr/T/1549206345936-0/run1.wdl --inputs /var/folders/5_/14ld0y7s0vbg_z0g2c9l8v300000gr/T/foo1724821479851536343json (Exit value: 1)
at io.dockstore.common.Utilities.executeCommand(Utilities.java:138)
... 6 common frames omitted
Cromwell exit code: 1
10:06:30.661 [main] ERROR io.dockstore.client.cli.ArgumentUtility - org.apache.commons.exec.ExecuteException: problems running command: java jar /Users/stvjc/.dockstore/libraries/cromwell36.jar run /var/folders/5_/14ld0y7s0vbg_z0g2c9l8v300000gr/T/1549206345936-0/run1.wdl --inputs /var/folders/5_/14ld0y7s0vbg_z0g2c9l8v300000gr/T/foo1724821479851536343json (Exit value: 1)
at io.github.collaboratory.wdl.WDLClient.launch(WDLClient.java:209)
at io.dockstore.client.cli.nested.WorkflowClient.launch(WorkflowClient.java:439)
at io.dockstore.client.cli.nested.AbstractEntryClient.processEntryCommands(AbstractEntryClient.java:236)
at io.dockstore.client.cli.Client.run(Client.java:706)
at io.dockstore.client.cli.Client.main(Client.java:608)

Punting for now, currently in backlog

Verified on Dockstore 1.7.0-beta.3.  A warning message displays if Docker is not running when launching a workflow with the Dockstore CLI.


Can't find the letsencrypt logs

I'm looking for the location of the letsencrypt or dehydrated logs. When using certbot, logs were stored in /var/log/letsencrypt/letsencrypt.log where I was able to see the response from letsencrypt in the case that I'd hit a rate limit, or some error had occurred. I'm not able to find that using lua-resty-auto-ssl. Can you point me in the right direction?

Errors like rate-limits are logged to the nginx error log, so you should find those entries there. Does that work for you?

Yep, that works for me. I hadn't thought to check those logs yet. Thank you for the quick response!


[opencv4, opencv4[gtk], gtk:x64-linux] build failure

Host Environment

OS: Linux x64, Ubuntu 18.04
Compiler: gcc 10.1, CMake 3.18

To Reproduce
Steps to reproduce the behavior:
./vcpkg install opencv4
./vcpkg install gtk
Failure logs
opencv4 install-x64-linux-dbg-out.log
gtk config-x64-linux-dbg-err.log
Additional context
I've rebuilt glib:x64-linux but it didn't affect opencv build process, also see these comments

@cenit Could you please take a look?
Thanks.

Related: #12275

/usr/include/gstreamer-1.0/gst/gst.h:27:10: fatal error: glib.h: Нет такого файла или каталога
   27 | #include <glib.h>
      |          ^~~~~~~~

Sorry, I forgot that logs are on russian. :)
It says "no such file or directory"

I removed gtk feature of opencv from the 4.3 update. I didn't inspect its history, but somehow it was mismanaged, because vcpkg gtk is broken on osx/Linux (custom CMakeLists.txt is not so portable) and opencv can use gtk only on osx/Linux, so there was no way it was a working or tested feature.
Fixing gtk on Linux would require abandoning the custom CMakeLists.txt and using its native build toolchain. Something very interesting and important, but beyond the scope of an opencv PR

Hmm I can't repro this issue now, is this resolved?

yes, gtk feature has been restored when we moved from custom cmakelists to meson build


[Bug]: Seeing crashes during OAuth flow when network errors occur

Description
I've had a few crashes reported with this package in the stacktrace:
Crashed: com.apple.main-thread
0  flutter_web_auth_2             0x54d8 $s18flutter_web_auth_226SwiftFlutterWebAuth2PluginC6handle_6resultySo0E10MethodCallC_yypSgctFy10Foundation3URLVSg_s5Error_pSgtcfU_ + 1452
1  flutter_web_auth_2             0x5984 $s10Foundation3URLVSgs5Error_pSgIegng_So5NSURLCSgSo7NSErrorCSgIeyByy_TR + 192
2  AuthenticationServices         0x24d74 <redacted> + 592
3  flutter_web_auth_2             0x70c4 $s18flutter_web_auth_226SwiftFlutterWebAuth2PluginC6handle_6resultySo0E10MethodCallC_yypSgctF015$syXlSgIeyBy_ypO7Iegn_TRyXlSgIeyBy_Tf1ncn_nTf4nng_n + 3348
4  flutter_web_auth_2             0x5534 $s18flutter_web_auth_226SwiftFlutterWebAuth2PluginC6handle_6resultySo0E10MethodCallC_yypSgctFTo + 84
5  Flutter                        0x5d61dc (Missing UUID 4c4c441f55553144a1682f45551c1451)
6  Flutter                        0x435a4 (Missing UUID 4c4c441f55553144a1682f45551c1451)
7  libdispatch.dylib              0x2320 _dispatch_call_block_and_release + 32
8  libdispatch.dylib              0x3eac _dispatch_client_callout + 20
9  libdispatch.dylib              0x126a4 _dispatch_main_queue_drain + 928
10 libdispatch.dylib              0x122f4 _dispatch_main_queue_callback_4CF + 44
11 CoreFoundation                 0x98c28 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
12 CoreFoundation                 0x7a560 __CFRunLoopRun + 1992
13 CoreFoundation                 0x7f3ec CFRunLoopRunSpecific + 612
14 GraphicsServices               0x135c GSEventRunModal + 164
15 UIKitCore                      0x39d6e8 -[UIApplication _run] + 888
16 UIKitCore                      0x39d34c UIApplicationMain + 340
17 Runner                         0x7904 main + 5 (AppDelegate.swift:5)
18 ???                            0x1ecbcedec (Missing)

In several of the reports, it seems a network request in the oauth flow has thrown a 404:

This package is being used transitively via oauth2_client 3.2.2.
Minimal Reproduction

Depend on oauth_client ^3.2.1
Initiate oauth flow
Have error (404) returned by an endpoint in oauth flow
See error

Exception or Error
See description
Expected Behaviour
The package should gracefully handle network failures.
Screenshots
No response
Additional context
No response
Device
iPhone 14 Pro
OS
iOS 16.5.1
Browser
N/A
Flutter version
3.13.6
flutter_web_auth_2 version
2.2.1
Checklist

[X] I have read and followed the entire troubleshooting guide and it has not provided the solution I need.
[X] I have provided all the information I can.

Please see if https://github.com/teranetsrl/oauth2_client/pull/178 fixes these issues. If not, I am open for PRs

Thanks, I'll give that a shot and see if I see any new instances of the crash. If you prefer to close this and have me re-open if I have more crashes, feel free to do so!

You're welcome :)
I think, I will leave this open for the time being. Maybe other people have the same problem and are jumping on the same bandwagon.

I can't say whether this was working (I think I had a regression after a while but not 100% sure), but unfortunately this did break my login functionality because of this PR (specifically the introduction of silentAuth). It makes it so the JSON can't be deserialized. I had to revert the dependency override for now.

@rundfunk47 Have you made sure that the other approaches still work as expected? Probably the local storage approach is not functioning correctly anymore, could you check that please? Otherwise, I might have to disable your changes for now

@ThexXTURBOXx @btrautmann
If I understand this correctly, the issue is that silentAuth: json['silentAuth'] does not default to false when deserialising, but crashes because there is no value? Or are you referring to another issue @ThexXTURBOXx ?

@btrautmann Is that the issue? I thought you were maybe referring to something else?

Sorry, I'm a little confused. Here's the series of events as I understand it:

I was experiencing errors that occurred (to the best of my understanding) when users experienced network errors in the OAuth flow, so I opened this issue.
Per the suggestion above, I used a dependency override to point my dependency on oauth2_client at https://github.com/ThexXTURBOXx/oauth2_client.git, which IIRC used a more recent version of flutter_web_auth2
From what I can tell looking at Crashlytics, this seemed to work (I don't see any recent errors like the original one reported
I recently upgraded Flutter and in doing so, ran a dart pub upgrade, which bumped flutter_web_auth_2 from 3.0.4 to 3.1.0
The bump from 3.0.4 to 3.1.0 introduced a breaking change which broke my login flow (I found out after the app was already in production). See the image of the stacktrace below.
I identified this PR as the culprit.

Due to the above, I removed the dependency override as I wanted to fix the app in production. This resolved the issue (since I'm now using the older version of flutter_web_auth2.

so I'm assuming changing:
FlutterWebAuth2Options.fromJson(Map<String, dynamic> json)
      : this(
          preferEphemeral: json['preferEphemeral'],
          debugOrigin: json['debugOrigin'],
          intentFlags: json['intentFlags'],
          windowName: json['windowName'],
          timeout: json['timeout'],
          landingPageHtml: json['landingPageHtml'],
          silentAuth: json['silentAuth'],
        );

to
FlutterWebAuth2Options.fromJson(Map<String, dynamic> json)
      : this(
          preferEphemeral: json['preferEphemeral'],
          debugOrigin: json['debugOrigin'],
          intentFlags: json['intentFlags'],
          windowName: json['windowName'],
          timeout: json['timeout'],
          landingPageHtml: json['landingPageHtml'],
          silentAuth: json['silentAuth'] ?? false,
        );

will likely fix the latter issue? I can create a PR for that 🙂

Yes, I suspect that will fix the issue :)

@rundfunk47 That should not be the problem as the preferEphemeral bool works without any problems.
@btrautmann Could you please share any exceptions or logs? If that really is the problem, then there should be some exceptions

Maybe, this might be a fix anyway. I will try out soon!

I just uploaded 3.1.1, which should fix this issue. Please confirm whether this is the case @btrautmann

Could you please share any exceptions or logs? If that really is the problem, then there should be some exceptions

I posted the logs/Exception above. I'll give the new version a shot some time today.

Yes, sorry, I overlooked them at first, but found them afterwards. They are related to a problem I fixed once, but reintroduced with 3.1.0

Just checked, and yeah, that fixed it on both platforms 👍 Thank you for the quick turnaround!

Perfect, thank you very much for the feedback! :)


Added links to website, preprint and google form :)

yes please, as it includes the links!

you might need to change the google form links and add your new stuff.

@mamuerie @alkastrinogiannis would introducing changes on the .md files create any issues?


Added support for auto-creating the collection if it does not exist

This is very ugly, but the component doesn't have a way to check if a collection exists. Anyone has any ideas?

FYI, in our pipeline the collection is defined by https://github.com/megacamelus/camel-assistant-manifests/blob/main/etc/kubernetes/apps/assistant/qdrant.yaml, if another collection is needed, also add it to the manifest

FYI, in our pipeline the collection is defined by https://github.com/megacamelus/camel-assistant-manifests/blob/main/etc/kubernetes/apps/assistant/qdrant.yaml, if another collection is needed, also add it to the manifest

Ahhh, thanks for the heads up. This can be handy soon ...
For now I am holding this PR a bit. I'm adding collection info support on Camel to make this implementation cleaner.

Looking good. I'll wait for the snapshot deploy to finish before merging this, otherwise it will break for everyone without the latest Camel build.


[WIP]Optimize GEMM for TSV110

Hi, fellows!
I benchmarked sgemm performance on<EMAIL_ADDRESS>x 24Cores (square matrix from 128 to 4096 ). There seems to be a gap between the best case (28.3 GFLOPS) and the theoretical peak of the chip (41.6 GFLOPS), still have room for optimization.

@craft-zhang , Thank you for the work.
I think you need use ldp instruction.

@craft-zhang , Thank you for the work.
I think you need use ldp instruction.

Thx for the advice.

going by recent experience, just matching the GEMM P and Q factors in param.h to per-core L2 cache size would probably help. but it needs someone with the hardware to test


Public Site: Browse: Authors page not working

The Authors page should show a list of authors and a (short) summary of the dataset for each author.

Authors data structure needs to be revisited! Temp fix to this problem was to ng-if-away the links to the page.


Save log from Megahit

Check Documentation
I have checked the following places for your error:

[x] nf-core website: troubleshooting
[x] nf-core/metatdenovo pipeline documentation

Description of the bug
The standard output and error from the Megahit process is not caught by a named file output from the process.
Expected behaviour
A log file should be saved in results/megahit.

I fixed this issue. It will be present in the next PR


Ask weakly

Hello, I would like to ask:
Why don't laravel frameworks add annotation grammar like spring? Do you think annotation grammar like spring framework is good?

Annotation was a thing in early 5 version, as you can see here.
You can still use annotation through a package: https://github.com/LaravelCollective/annotations

It's better to discuss it at :
https://github.com/laravel/ideas/issues
I remember Taylor received a lot complain from community when he added that at laravel 5.0


[Experiment] Cross Frameworks Controls

What if we can create drawn controls and be able to use them independently of the UI framework? In this way, a control for example DataGrid created for WinUI could be used in .NET MAUI or perhaps Avalonia without problems.
What would we need?

Create libraries for WinUI, Avalonia etc where GraphicsView (view that exposes the Canvas where to draw) is implemented in each platform using the best option (WinUI, SkiaSharp etc).
Each framework has different options for expressing bindable properties. We need to resolve this point. There would be interesting options such as generating code etc.

What is the benefit? Imagine that a drawn DataGrid control is created in the Windows Community Toolkit. Voila, having it effortlessly in the .NET MAUI Community Toolkit (even sharing the code) and other frameworks would be just amazing!.

Implementing a control once and then sharing it among all UI frameworks would be wonderful. We have all written and re-written the exact same control so many times over the years it's a lot of wasted time. That said, you can't do this level of abstraction with ONLY a graphics stack. Granted, the graphics stack is a lot of it (a composition layer like in WinUI would go a long way to write once).
The other missing pieces are pretty major: Binding, Event model (INotifyPropertyChanged, etc), Input, Styling, Localization etc, Popups/Windowing. A control needs all of these pieces which have nothing to do with just drawing itself. Microsoft has gone a lot of different directions over the years and WPF/Silverlight/UWP/WinUI/Xamarin.Forms/MAUI now have differences in all layers.
As I've thought about this same problem over the years the best idea I had is to create a 'Control Description Language' and then compile that for each framework independently. The 'Control Description Language' would have abstraction layers for all of the pieces mentioned above.
The end goal would be to create a packaged control that could be dropped into a framework just like a component is dropped into a system modelling application. For example, all models are written in the heavily math/physics based Modelica language which is commonly shared among physics-based simulation software. Modelica is so powerful it can model all domains -- electrical/thermal/mechanical/etc. A 'Control Description Language' must be equally powerful.
Bottom line: I don't think you realize how complicated this would be and don't think it's possible with your ideas. You need all features of the UI framework to implement a control. It would have been better to standardize on UWP.

Well, you are right that my proposal it is not as detailed as it should, I will update it.
In each platform, in addition to allowing drawing, it would be necessary to have an abstract API to manage interaction events (touch, etc this already is implemented). You are right that it would also take quite a few more options in the abstraction layer to cover other details. Although I think that, being able to define a control in an abstract way with its properties, styles, interaction, it would allow many cases and it would already be an interesting proposal, it would not cover everything, more options would be needed in the abstraction layer.
Regarding differences such as DependencyProperty vs BindableProperty etc my idea was to use source generators to allow defining a property, marking it and  generate the necessary code for each platform.
It is certainly a complex idea that requires a much more detailed Spec, I will update it. Thanks for the feedback :).

This area has always been an interest of mine. Rewriting the same control a few times will tend to start one thinking about what can be done differently :)

Regarding differences such as DependencyProperty vs BindableProperty etc my idea was to use source generators to allow defining a property, marking it and generate the necessary code for each platform.

I have the least concern about this :) WinUI is already generating property code automatically from IDL files.

It is certainly a complex idea that requires a much more detailed Spec, I will update it. Thanks for the feedback :)

I think my overall point is simply that all UI frameworks started with a similar concept of sharable controls. Whether or not it's cross-platform or cross-framework is actually irrelevant to the point I'm making. In the pursuit of enabling fully featured, shareable controls, UI frameworks inevitably require a lot of features that grow into... well... the UI framework itself. In other words you need the full complexity of a UI framework like UWP to write fully-featured/sharable controls. So my point is spec-wise you should be scoping to include almost all areas of UWP itself -- a task much bigger than one person can do as well. In the end though, perhaps the correct approach all along is simply to use the UI framework syntaxes and conventions that already exist -- i.e. UWP like the Uno Platform. This was really the point of UWP all along.
With massive amounts of code generation, abstraction layers and a control description language all of your goals should be possible. I'm just not convinced yet it's actually practical or doable. Plus in my mind we want to avoid:

Let's also not forget Maui.Graphics.Controls is a direct result of the difficulty maintaining a UI framework that uses native implementations of each platform. It is better to do things only once and only very low-level (input, pixel rendering) is per-platform. So by proposing this you are ironically repeating some of the same mistakes Xamarin Forms made that you are working to fix by Maui.Graphics.Controls.
Bottom line: I don't mean to discourage this idea and it is possible. However, it requires a seriously committed team and almost perfect strategy to execute successfully. It would take an all of Microsoft effort between the various teams (WPF,WinUI,Maui). If successful though, it would push UI development forward a generation, just like WPF did back in the day.

I basically agree with @robloo. To me, the most important goal is being able to use ONE standard everywhere. Without all the issues XForms has, trying to use native controls.
.Net just needs MAUI to have the option of using this "render to bitmap" approach EVERYWHERE. No more native controls. No more messing with slightly different versions of XAML.
Demonstrate that. Show that MAUI could (if you want it to) use Graphics.Controls to render to a bitmap. Ignoring the UI widgets available in the local environment.
Most importantly, show that working in a browser. That's where Microsoft's offerings are weakest vs. the competition (Flutter; ReactJS).
Najak3d and I started to make a demo showing MAUI as a GUI on top of a 3D game engine. (First Urho3D, with Unity planned next.)
But we are stopped by this issue.
If I can't get the basics to work, then there is no point spending time with these technologies, until the moving parts (.net 6, Windows Desktop Apps, MAUI, VS 2022) come together, sometime next year.
Its a shame.

@jsuarezruiz I think we need partial properties
I tried to use private fields, but not used fields do not look very nice
for example:
// source
public partial class TestView : ContentView
{
    [CrossProperty]
    private readonly string? title; // unused
}

// generated
public partial class TestView
{
    public static readonly BindableProperty TitleProperty = BindableProperty.Create(nameof(Title), typeof(string), typeof(TestView), null);

    public string Title
    {
        get => (string)GetValue(TitleProperty);
        set => SetValue(TitleProperty, value);
    }
}

can you have any thoughts?

@jsuarezruiz I think we need partial properties
I tried to use private fields, but not used fields do not look very nice
for example:
// source
public partial class TestView : ContentView
{
    [CrossProperty]
    private readonly string? title; // unused
}

// generated
public partial class TestView
{
    public static readonly BindableProperty TitleProperty = BindableProperty.Create(nameof(Title), typeof(string), typeof(TestView), null);

    public string Title
    {
        get => (string)GetValue(TitleProperty);
        set => SetValue(TitleProperty, value);
    }
}

can you have any thoughts?

can it render to web as well directly without any css/html ?

@jsuarezruiz, @hintsofttech's question is very important. Any answer regarding it?

@jsuarezruiz, @hintsofttech's question is very important. Any answer regarding it?

Maui.Graphics has a WebGL implementation https://github.com/dotnet/Microsoft.Maui.Graphics/tree/main/src/Microsoft.Maui.Graphics.Blazor and GraphicsControls makes use of this library for drawing. I have done small tests (related with other platforms, like Linux etc). It would be necessary to create and map what is necessary to launch .NET MAUI Apps on the web and complete some implementations beyond the Canvas where draw (touch events, etc). It could be a technically possible option. However, this library is experimental. The main goal right now is to validate the interest. The progress I make is in spare time and mainly oriented to keeping everything up to date working, fixing bugs and/or solving the questions and topics related to its validation (performance, accessibility, etc). So the answer is, yes, it could reach the web, linux or other platforms but at the moment it is an experimental library and the efforts are now more oriented towards its validation.

Thank you very much, that's good news.

That said, you can't do this level of abstraction with ONLY a graphics stack.

I don't agree with this at all.

The other missing pieces are pretty major: Binding, Event model (INotifyPropertyChanged, etc), Input, Styling, Localization, Popups/Windowing, Text formatting, etc. A control needs all of these pieces which have nothing to do with just drawing itself. Microsoft has gone a lot of different directions over the years and WPF/Silverlight/UWP/WinUI/Xamarin.Forms/MAUI now have differences in all layers.

Binding/Event model: not the responsibility of a graphics layer. Dotnet has the ability to allow any binding approach to be specified, in a completely type safe way (i.e. much better than the platforms you mention which all use a pre-generics approach). The graphics layer doesn't need to know about it. It only needs to define settable properties (if mutation is the approach).
Input: An interesting one. We are working on keyboard input but the options are either to draw the keyboard or to allow a user to plug in a native keyboard.
Styling/localization/text formatting: the drawn control chooses what options to give the user; no limitations here.
Popups/Windowing: not the responsibility of drawn controls. Drawn controls only render things inside these.

You can disagree all you want but I know what a graphics stack should be. If you throw everything into it, it's not a graphics stack anymore and it is instead a framework where you are breaking separation of concerns.
Its good to be optimistic. But looking at what Maui is today, what Microsoft has done in the past, the resources you have on the team, etc I highly doubt you will come anywhere close to this proposal.
Prove me wrong and I'll engage more. Otherwise I'm stepping away so as not to waste time.
Finally, introducing generics in more places is neat and there are certainly some areas that can be modernized.


Payload field that is sending to the remote server is always empty

Callback URL documentation says that payload field contains "a string containing all build messages". During during fixing #522 I found that this field is always empty:
POST / HTTP/1.1
Host: <IP_ADDRESS>:8888
User-Agent: Go-http-client/1.1
Content-Length: 216
Content-Type: application/json
Accept-Encoding: gzip

{"labels":{"io.k8s.display-name":"my-test-app","io.openshift.s2i.build.image":"java:8","io.openshift.s2i.build.source-location":"/data/src/github.com/openshift/source-to-image/s2i-test"},"payload":"","success":true}

@bparees Do you know how we can collect all build messages? We're logging them via glog and they're printed to the stdout/stderr. Show we create another one special logger? Or how it's going to be?

@php-coder collect them where?

@bparees In the Message field of the Result object.

I think you should just set a message for each execution step indicating success/failure and the error.  i don't think it needs to be an exact replica of what you'd see on stderr/stdout from the CLI.
(I doubt anyone is even using this feature, it's another "never should have been implemented" idea.)

nope, nobody uses that. i can confirm it. just as result.success isn't that used as well (one or two places, the rest looks for result == nil of err != nil ). i wanted to use that instead of buildinfo in the beginning.

by the way, can we deprecate fields like that? since we don't use them and they aren't of any value?
or something like:
// Messages is a list of messages from build process.
// NOTE: Field deprecated, will be removed in a future version
Messages []string

@PI-Victor we can, but we don't have a great process in place for ultimately removing them.  In this case, making it "work" is probably the path of least resistance.

edit: i actually fixed the result.success, forgot about that.

How it was broken?

@php-coder it wasn't broken. but rather not implemented for layered strategy for example. i know we check one place for success = true, otherwise i don't know where else we do it.
we also don't use it in origin. we only check for err when we get the build result.

ok, i can make it work, the question is, what "messages" should the build process surface. are we talking about failures or just just something else (we have glog in place for that already) the api docs arent' very specific.

nvm about my previous comment.

@coreydaley let's just drop the field and change the doc.  i doubt anyone is even using this callback feature anyway.


Remove netappcore3.1 replace w/ net6.0 + net7.0

:x: Build ExtendedXmlSerializer <IP_ADDRESS>-dpjtyrfu failed (commit https://github.com/ExtendedXmlSerializer/home/commit/36483ce6c9 by @Mike-E-angelo)

:white_check_mark: Build ExtendedXmlSerializer <IP_ADDRESS>-jotirxlu completed (commit https://github.com/ExtendedXmlSerializer/home/commit/f34e76b1a7 by @Mike-E-angelo)
Install it by running the following command in Package Manager Console:
Install-Package ExtendedXmlSerializer -Version <IP_ADDRESS>-jotirxlu -Source https://ci.appveyor.com/nuget/extendedxmlserializer-preview

Problems with the above command?  You may be running into this known issue here:
https://github.com/NuGet/Home/issues/7189

:white_check_mark: Build ExtendedXmlSerializer <IP_ADDRESS>-jboikloy completed (commit https://github.com/ExtendedXmlSerializer/home/commit/62daae94ad by @Mike-E-angelo)
Install it by running the following command in Package Manager Console:
Install-Package ExtendedXmlSerializer -Version <IP_ADDRESS>-jboikloy -Source https://ci.appveyor.com/nuget/extendedxmlserializer-preview

Problems with the above command?  You may be running into this known issue here:
https://github.com/NuGet/Home/issues/7189


added .env so main API will work, along with a pickled model in the d…

…ata folder and a (non-functional) illustration API
Description
Replace with description of PR
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Change Status

[ ] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

Has This Been Tested

[ ] Yes
[ ] No
[ ] Not necessary

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] There are no merge conflicts

looks good

looks good


owners: move junr03 to emeritus

Signed-off-by: Jose Nino<EMAIL_ADDRESS>

Thank you so much Jose for everything you have done over the years. The project would not be what it is today without. Maybe one day we will see you back. :)

😢 it's been great working with you these last few months, Jose. You'll be missed. Although "maintainer emeritus" is a dope title 😆
PS: Can you remove yourself from lyft_maintainers.yml too?

Will do in a different PR @jpsim!

It's been an amazing journey @junr03. :)


CU Trooper squads erroring despite having skip hull breach stat

me turn/time. Both are 1 shot from death, so its not like camouflage all of a sudden started in.
My mechs almost stand on them, more or less flat terrain. I had clear LoS the round before, now nothing.
dratax — 01/10/2022
screenshots and logs would be helpful
FayaAOP (Jens) — 01/10/2022
Cant SS but i got logs.
Attachment file type: archive
RogueLogs.zip
9.69 MB
Its the start of a fresh round.
I have to GTAoE to hit them.
I moved my mechs and VtoL now right next to them and nothing happens lol
And after checking the health/armor, i cannot damage them with AoE.
Harkonnen — 01/10/2022
@FancyRaptor if i read the log correctly, this is CU squad/Hul breach bug
but i have alredy added this
{
"durationData": {
"duration": -1
},
"targetingData": {
"effectTriggerType": "Passive",
"effectTargetType": "Creator"
},
"effectType": "StatisticEffect",
"Description": {
"Id": "BreachImmunity",
"Name": "BreachImmunity",
"Details": "Immune to Hull Breach",
"Icon": "uixSvgIcon_ability_precisionstrike"
},
"statisticData": {
"statName": "CBTBE_HullBreachImmunity",
"operation": "Set",
"modValue": "true",
"modType": "System.Boolean"
},
"nature": "Buff"
}
to a gear all PAs have
FayaAOP (Jens) — 01/11/2022
At the time of the log i have <IP_ADDRESS>, if thats in there then it does not fully work.
In another mission i had a non working vehicle, inside a minefield like the BA if that matters, but this time it counted towards the mission.

RogueLogs(1).zip


[REQUEST] Utakata no Uchronia (switch)

+1

+1

https://github.com/0xDC00/scripts/commit/4dc98e93bab6c88f2d1ce298f0e1f07e5e5e2ece


Recreating Linux VM without temp disk withough going through snapshots

The page advises that, due to potential issues in Windows hosts, even on Linux hosts it is forbidden to directly convert from an instance type with a temporary disk to an instance type without. The temp disk is often /dev/disk/cloud/azure_resource-part1 mounted on /mnt.
To manually work around the limitation, the page suggests to create a snapshot of the disks and recreate the VM manually into the new instance type from the snapshot.
In my experience it proved easier to delete the VM manually, selecting only the OS disk for deletion. Terraform then took care of attaching any remaining hard disks when recreating the instance.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 491f3079-7fe0-9bba-dde4-89b5de7eb8e7
Version Independent ID: ca05a139-92b7-299a-dd2e-a8a62e82937d
Content: FAQ Azure VM sizes with no local temporary disk - Azure Virtual Machines
Content Source: articles/virtual-machines/azure-vms-no-temp-disk.yml
Service: virtual-machines
Sub-service: sizes
GitHub Login: @brbell
Microsoft Alias: brbell

@nemobis Thank you for your feedback!  We are reviewing the documentation and will get back to you shortly.

@lauradolan brbell is listed as the doc owner for this, but that appears to be out of date.

#reassign: iamwilliew

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing. We are closing this issue for now, but feel free to comment here as necessary. #please-close

@cynthn Thanks for the update. Would it help to post a pull request?


can access host machine in wsl2

Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.
If you have a feature request, please post to the UserVoice.
If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.
Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues.  Please direct all Windows crashes and security issues to<EMAIL_ADDRESS> Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".
Please fill out the below information:

Your Windows build number: Microsoft Windows [Version 10.0.18990.1]

What you're doing and what's happening:

xxx@xxx:/mnt/c/Users/a$ ping <IP_ADDRESS>                                                                                PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
^C
--- <IP_ADDRESS> ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9326ms

What's wrong / what should be happening instead: it can access the host machine
some informathion here:

with wsl2

xxx@xxx:/mnt/c/Users/a$ ip a                                                                                1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 62:a3:bd:cb:c7:d6 brd ff:ff:ff:ff:ff:ff
3: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether aa:ec:d2:e5:ae:c3 brd ff:ff:ff:ff:ff:ff
4: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/sit <IP_ADDRESS> brd <IP_ADDRESS>
5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:15:5d:00:65:a8 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/20 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::215:5dff:fe00:65a8/64 scope link
       valid_lft forever preferred_lft forever
xxx@xxx:/mnt/c/Users/a$ ifconfig
  eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::215:5dff:fe00:65a8  prefixlen 64  scopeid 0x20<link>
        ether 00:15:5d:00:65:a8  txqueuelen 1000  (Ethernet)
        RX packets 427  bytes 57899 (57.8 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 80  bytes 6833 (6.8 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 12  bytes 468 (468.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 12  bytes 468 (468.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

xxx@xxx:/mnt/c/Users/a$ ip route                                                                                default via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/20 dev eth0 proto kernel scope link src <IP_ADDRESS>
xxx@xxx:/mnt/c/Users/a$ netstat -arn                                                                                Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
<IP_ADDRESS>         <IP_ADDRESS>     <IP_ADDRESS>         UG        0 0          0 eth0
<IP_ADDRESS>     <IP_ADDRESS>         <IP_ADDRESS>   U         0 0          0 eth0

with windows 10

PS C:\Users\a> ipconfig
Windows IP Configuration

Ethernet adapter 以太网:

   Connection-specific DNS Suffix  .   :

Ethernet adapter vEthernet (以太网):

   Connection-specific DNS Suffix  .  :

Ethernet adapter vEthernet (WSL):

   Connection-specific DNS Suffix  .  :
PS C:\Users\a> ping <IP_ADDRESS>

Pinging <IP_ADDRESS> with 32 bytes of data:
Reply from <IP_ADDRESS>: bytes=32 time<1ms TTL=64
Reply from <IP_ADDRESS>: bytes=32 time<1ms TTL=64
Reply from <IP_ADDRESS>: bytes=32 time<1ms TTL=64

Ping statistics for <IP_ADDRESS>:
    Packets: Sent = 3, Received = 2, Lost = 1 (33% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

also I was confused about use dig commad in wsl2:
xxx@xxx:/mnt/c/Users/a$ dig @<IP_ADDRESS> onedrive.com
; <<>> DiG 9.11.3-1ubuntu1.8-Ubuntu <<>> @<IP_ADDRESS> onedrive.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58430
;; flags: qr rd ad; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;onedrive.com.                  IN      A

;; ANSWER SECTION:
onedrive.com.           0       IN      A       <IP_ADDRESS>
usw2.akam.net.          0       IN      A       <IP_ADDRESS>
use1.akam.net.          0       IN      A       <IP_ADDRESS>
eur2.akam.net.          0       IN      A       <IP_ADDRESS>
ns1-221.akam.net.       0       IN      A       <IP_ADDRESS>
ns1-224.akam.net.       0       IN      A       <IP_ADDRESS>
use4.akam.net.          0       IN      A       <IP_ADDRESS>
eur5.akam.net.          0       IN      A       <IP_ADDRESS>
usc5.akam.net.          0       IN      A       <IP_ADDRESS>
usc5.akam.net.          0       IN      AAAA    2600:1480:d000::41

;; Query time: 55 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Mon Sep 30 15:42:24 CST 2019
;; MSG SIZE  rcvd: 324

with the result, I think it can access host with 53 port, but :
xxx@xxx:/mnt/c/Users/a$ telnet <IP_ADDRESS> 53                                                                                Trying <IP_ADDRESS>...

this was also failed.

Strace of the failing command, if applicable:  (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here).

For WSL launch issues, please collect detailed logs.

See our contributing instructions for assistance.

have the same problem.

after disabled windows firewall, wsl2 can connect to host

#4139


vcpkg_build_msbuild is broken if TRIPLET_SYSTEM_ARCH is different from x64

On my machine (I did not double checked on a second machine at the moment) it seems that the vcpkg_build_msbuild command is broken for all triplets for which TRIPLET_SYSTEM_ARCH is different from x64 .
In particular it seems that the msbuild command is not found because the PATH contains the directories of Visual Studio tools only if TRIPLET_SYSTEM_ARCH is equal to x64 .
I checked this by adding a message(STATUS "PATH : $ENV{PATH}") debug print.
PATH for x64-uwp :
-- PATH : C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files (x86)\MSBuild\14.0\bin\amd64;C:\Program Files (x86)\MSBuild\14.0\bin\amd64;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\amd64;C:\windows\Microsoft.NET\Framework64\v4.0.30319;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\VCPackages;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Team Tools\Performance Tools\x64;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Team Tools\Performance Tools;C:\Program Files (x86)\Windows Kits\8.1\bin\x64;C:\Program Files (x86)\Windows Kits\8.1\bin\x86;C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\x64\;C:\windows\system32;C:\windows;C:\windows\system32\Wbem;C:\windows\system32\WindowsPowerShell\v1.0\

PATH for x64-windows-static :
-- PATH : C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files (x86)\MSBuild\14.0\bin\amd64;C:\Program Files (x86)\MSBuild\14.0\bin\amd64;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\amd64;C:\windows\Microsoft.NET\Framework64\v4.0.30319;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\VCPackages;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Team Tools\Performance Tools\x64;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Team Tools\Performance Tools;C:\Program Files (x86)\Windows Kits\8.1\bin\x64;C:\Program Files (x86)\Windows Kits\8.1\bin\x86;C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\x64\;C:\windows\system32;C:\windows;C:\windows\system32\Wbem;C:\windows\system32\WindowsPowerShell\v1.0\

PATH for arm-uwp :
-- PATH : C:\windows\system32;C:\windows;C:\windows\system32\Wbem;C:\windows\system32\WindowsPowerShell\v1.0\

PATH for x86-windows :
-- PATH : C:\windows\system32;C:\windows;C:\windows\system32\Wbem;C:\windows\system32\WindowsPowerShell\v1.0\

In theory the problem should be reproducible by tryng to build a port that uses vcpkg_build_msbuild for the x86-windows , for example with a vcpkg install box2d:x86-windows.
I wonder if this problem depends on something on my machine, because the chakracore port use  vcpkg_build_msbuild as well, and it should be one of the few ports tested in the CI system described in https://github.com/Microsoft/vcpkg/issues/72#issuecomment-293119922 .

e4c5ef656607a1165566b338f5a85f907a627f86 changes the way we set the environment with vcvarsall.bat, so this might be a regression. Are you using the latest vcpkg?
For the triplet (x86-windows) that is not working, try using:
vcpkg env --debug --triplet x86-windows
This will change the console to the environment vcpkg uses to do the builds (use exit to go back to your original environment). --debug will also display extra information, so we can see if something fails in this step*. If it works, use:
path
to display the PATH variable.

*I think this will probably fail in your machine, and hopefully we can get some info as to why.

Installing ode and other ports  vcpkg_build_msbuild seems to be working fine in a new vcpkg installation, so probably there was something wrong in my enviroment back when I opened the issue, or there was some  issue in  vcpkg that has been solved since then. I think we  can close this issue now.


[BEAM-13275] Removed the explicit selenium dependency from setup

The dependency can be transitively installed through needle, no need to
fix it in setup.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Not a binary change, the dependency is only used in an Interactive Beam integration test, not executed by github pre- or post- submits.


Cleaning up monomorphize

Cleaening up some of the monomorphize functions. @gabizon103 might find this interesting.
NOTE: MonoSig and MonoDeferred are unfortunately not going to be merged here (I tried, believe me) mainly because MonoSig is mutated all the time but much of MonoDeferred requires it to stay referenced, so merging the two causes a bunch of "mutably borrowed while alreaedy immutably borrowed" issues.

Is this ready for review? If so, LGTM!


/share doesn't recognize logged in account

Screenshots
https://cloud-cpxjw5qwj-hack-club-bot.vercel.app/020230505-2038-22.5587033.mp4
(I know, I need to delete and rename some games)
when you enter a link via /share, Sprig doesn't recognize that you are logged in

This does not happen anymore. Please re-open if it does!


[AIRFLOW-2563] Fix PigCliHook Python 3 string/bytes use

Make sure you have checked all steps below.
JIRA

[X] My PR addresses the following Airflow JIRA issues and references them in the PR title. F

https://issues.apache.org/jira/browse/AIRFLOW-2563

Description

[X] This PR fixes PigCliHook's Python 2-style use of strings where Python 3 requires (or returns) a bytes-like object.

Tests

[X] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Trivial bug fix

Commits

[X] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[X] No new files or functionality.

Code Quality

[X] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

Merging #3594 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master    #3594   +/-   ##
=======================================
  Coverage   76.85%   76.85%
=======================================
  Files         204      204
  Lines       15522    15522
=======================================
  Hits        11930    11930
  Misses       3592     3592

Impacted Files
Coverage Δ

airflow/hooks/pig_hook.py
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

The failing test appears to have been a flake (Travis reports a 10 minute period of no output on an unrelated test; all tests pass on my fork).

Please link to your fork instead of retriggering every time.

Sure, sorry about that!

Travis: https://travis-ci.org/jakahn/incubator-airflow
Fork: https://github.com/jakahn/incubator-airflow

Just bumping since it's been ~2 weeks

LGTM +1