feat: avoid multiple types of select calls

Currently there are two scenarios when a select operation type is found:

When an include has a select within it
When a select has a relation in it

This means that there is a situation where it is not possible to reason about what to do with a select because the two scenarios look the same based on the available information; both have the include operation as the parent.
BREAKING CHANGE: remove the calls for include selects
Extensions that relied on calls with the "select" operation for select objects within an include will no longer be able to use that call. Instead use the parent "include" operation to modify the selected fields, or use the "select" operation for the relation within that select object.

Hi @olivierwilkinson, great library. Are you still maintaining the library and plan to merge this PR?


Is there a way to run a headless electron instance with selenium web driver?

I started a little bit of a journey to figure out if I can use nightwatchjs to run selenium tests. Knowing about nightmarejs - another test runner that runs a headless version of electron to run its tests - I wondered if I could run my selenium tests against electron.
I was able to run electron with the chrome driver, as indicated in the electron docs, but couldn't figure out how to make it headless. It seems that the binary option in the configuration that needs to be passed down to selenium cannot use xvfb-maybe, it needs the actual binary.
Any thoughts on this? Could it be achieved?
PS: Link to the nightwatchjs discussion

You could give binary a wrapper script or program that sets things up and then launches the app.
That is what spectron uses to pass in custom arguments and environment variables to Chromedriver.
https://github.com/kevinsawicki/spectron/blob/master/lib/launcher.js

@vladnicula Run nightmarejs itself under xvfb-maybe


Doesn't work on Astro 2.6

I moved my project to a newer version of Astro (2.6) and all the solid-icons (except the hamburger one which I used for the navbar) I've used appear in the DOM but are invisible. I didn't have this issue with the older version of Astro 2.3

Hi thanks for waiting, can you take a look at the 1.0.10 version? recently i sent a solution for that.

Now it works good. Thank you for fixing this issue


Honda: HR-V 2023 (Taiwan version)

Checklist

[x] added entry to CarInfo in selfdrive/car/*/values.py and ran selfdrive/car/docs.py to generate new docs
[x] test route added to routes.py
[x] route with openpilot: 495ad4581a73fe31|2023-10-25--20-14-20
[ ] route with stock system:

Difference vs HR-V 2023:

It's missing HONDA_BOSCH_ALT_BRAKE_SIGNAL

@eFiniLan any problems with this port?

@eFiniLan any problems with this port? We can just add the FW to the HONDA_HRV_3G platform

Hey man,  thanks for reviewing it, I only been to that car once for 30 mins so I'm not able to provide any further data/information.
I'll close it for now :)


Building from OpenBLAS 0.3.21 error due to LAPACK_FORTRAN_STRLEN_END

Hello,
I have a c function that use dpbrtf as follows
 dpbtrf_("U", n_, order_, Ab, ldab, info)

The program compiled and openblas was provided by the debian repo of my distribution:
libopenblas-dev/stable,now 0.3.13+ds-3 amd64  [installé]
  Optimized BLAS (linear algebra) library (dev, meta)

And it runs fine (assessed with some handcrafted tests). I try to use the last openblas version (0.3.21) : the compilation was fine but when I try to compile my program with the new openblas library I got an error because of missing argument:
gcc -I /opt/OpenBLAS/include/ -L /opt/OpenBLAS/lib/ -O3 -Wall -pedantic -fpic -shared -o shared_function.so ref_c_func.c -lopenblas -fopenmp -lgfortran
ref_c_func.c: In function ‘batch_cholesky_banded’:
ref_c_func.c:579:7: error: too few arguments to function ‘dpbtrf_’
  579 |       dpbtrf_("U", n_, order_, Ab, ldab, info);
      |       ^~~~~~~
In file included from /opt/OpenBLAS/include/lapack.h:11,
                 from ref_c_func.c:5:
/opt/OpenBLAS/include/lapack.h:12304:42: note: declared here
12304 | #define LAPACK_dpbtrf_base LAPACK_GLOBAL(dpbtrf,DPBTRF)
      |                                          ^~~~~~
/opt/OpenBLAS/include/lapacke_mangling.h:12:39: note: in definition of macro ‘LAPACK_GLOBAL’
   12 | #define LAPACK_GLOBAL(lcname,UCNAME)  lcname##_
      |                                       ^~~~~~
/opt/OpenBLAS/include/lapack.h:12305:6: note: in expansion of macro ‘LAPACK_dpbtrf_base’
12305 | void LAPACK_dpbtrf_base(
      |      ^~~~~~~~~~~~~~~~~~

When I check in lapack.h, I see that when LAPACK_FORTRAN_STRLEN_END is defined it adds a new parameter to the function dpbtrf_ (from lapack.h)
#define LAPACK_dpbtrf_base LAPACK_GLOBAL(dpbtrf,DPBTRF)
void LAPACK_dpbtrf_base(
    char const* uplo,
    lapack_int const* n, lapack_int const* kd,
    double* AB, lapack_int const* ldab,
    lapack_int* info
#ifdef LAPACK_FORTRAN_STRLEN_END
    , size_t
#endif
);
#ifdef LAPACK_FORTRAN_STRLEN_END
    #define LAPACK_dpbtrf(...) LAPACK_dpbtrf_base(__VA_ARGS__, 1)
#else
    #define LAPACK_dpbtrf(...) LAPACK_dpbtrf_base(__VA_ARGS__)
#endif

I try to comment the line #define LAPACK_FORTRAN_STRLEN_END : the program now compile but I get a segmentation fault.
I don't know how to handle this point: I search but I did not find what is the meaning of the parameter size_t and how to provide this value to the function ?
I am aware of the FAQ to replace the library (https://github.com/xianyi/OpenBLAS/wiki/faq#replacing-system-blasupdating-apt-openblas-in-mintubuntudebian).
ps: the objective of using compiled version of openblas is to use my program on another computer were I cannot install packages.

Ok my bad, when I build the openblas library with the option FC=gfortran I do not have any segmentation fault and I got correct result.
Still, I need to comment the line #define LAPACK_FORTRAN_STRLEN_END before compiling my program.
I don't understand why there is one more parameter with the function per default now ?

This is a change introduced with recent LAPACK version 3.10 (which OpenBLAS imports from the Reference-LAPACK project (also known as "netlib").
The background is that string handling differs between C and Fortran such that the Fortran compiler needs to be told the length of each string argument via extra arguments added at the end of the list. Many old codes do/did not fo this for single-character arguments, and it was argued that this meant relying on undefined behaviour.
see #2154 and related https://github.com/Reference-LAPACK/lapack/issues/339

Many thanks @martin-frbg for your explanation. However, I am not sure about the correct way to modify my code:

Should I add 1 (or any number, but from the lapack.h it seems to be 1)  at the end of my call to dpbtrf such as  dpbtrf_("U", n_, order_, Ab, ldab, info, 1)
Or comment the definition of LAPACK_FORTRAN_STRLEN_END is a correct way to handle this change. But in that case, as far as I understand, we do no tell to the copmpiler the length of the strings ?

The correct way should be to add the "1" for the length of the "U" argument at the end of your dpbtrf line, but as you wrote you could also comment the definition of LAPACK_FORTRAN_STRLEN_END to stay with the old behaviour (which has been implicated in a few otherwise unexplained problems as seen in the Reference-LAPACK issue ticket and others mentioned therein).
Some discussion happened in https://github.com/Reference-LAPACK/lapack/issues/604 - from that two possible solutions would be to (a) always use the corresponding LAPACKE interface instead of calling a LAPACK function directly or (b) have your own code check if LAPACK_FORTRAN_STRLEN_END is defined and supply arguments accordingly

Thanks @martin-frbg. I close the issue.
Best wishes


fixed syntax errors

Fixed syntax errors found in "/management/commands/graph_transitions.py" after running mypy.

Thank  you for the support! I personally don't use this feature, and everything in the graph transition drawing is community maintained


Jceks File Not Supporting in Python 2.7.5

I am getting below error though we have jks version 19.0.0 and javaobj = 0.4.0.Does any one face this problem while calling jks.KeyStore.load(), though I am giving correct  store password
cc: @danpker @cory-parr
Python 2.7.5
Type "help", "copyright", "credits" or "license" for more information.

import jks
jks.KeyStore.load('file_name.jceks',"pass_phrase")
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/site-packages/jks/util.py", line 92, in load
try_decrypt_keys=try_decrypt_keys)
File "/usr/lib/python2.7/site-packages/jks/jks.py", line 525, in loads
entry.decrypt(store_password)
File "/usr/lib/python2.7/site-packages/jks/jks.py", line 320, in decrypt
raise UnexpectedAlgorithmException("Unexpected algorithm used for encrypting SealedObject: sealAlg=%s" % sealed_obj.sealAlg)
jks.util.UnexpectedAlgorithmException: Unexpected algorithm used for encrypting SealedObject: sealAlg=PBEWithMD5AndTripleDES

@mahmoud
FYI Can you help me out.

That's a bit bizarre, given this line: https://github.com/kurtbrose/pyjks/blob/629742006ee24477d7c649b279b43e054f46b088/jks/jks.py#L303
Seems like it'd have you covered.
If I were you, I'd do a pdb.post_mortem() or run with python -m pdb and find out why that string is not comparing as equal. Maybe something to do with a library version? Post a pip freeze just in case.

@mahmoud
I've just modified below code in jks.py to typecast <class 'javaobj.v1.beans.JavaString'> to <type 'str'>.
<         if sealed_obj.sealAlg == "PBEWithMD5AndTripleDES":
---
>         if str(sealed_obj.sealAlg) == "PBEWithMD5AndTripleDES":

Previously:
type of sealed_obj.sealAlg =<class 'javaobj.v1.beans.JavaString'>
after change:
type of sealed_obj.sealAlg =<type 'str'>
Modified code is compatible python3 as well.
Is this modification acceptable?

@mahmoud can you closed this seems jira 61 have solutions and commit also

Sure, sounds good. Thanks!


Filter by Tag

I'd like to filter the news by tag but it doesn't work this way:
<property name="news" type="smart_content">
<meta>
  <title lang="en">Latest FAQ</title>
</meta>

<params>
  <param name="provider" value="news"/>
  <param name="max_per_page" value="5"/>
  <param name="page_parameter" value="p"/>
  <param name="tags_parameter" value="faq"/>
</params>
</property>

Is this possible at all?

Currently we don't have any "resolveFilter" in the SmartContent component yet these would have to be added in the "NewsDataProvider.php", like for example in the SnippetSmartContent component

Welll... I played around a bit, seems to work with
<params>
    <param name="provider" value="news"/>
    <param name="max_per_page" value="5"/>
    <param name="page_parameter" value="p"/>
    <param name="properties" type="collection">
        <param name="tag" value="FAQ"/>
    </param>
</params>

Would be great to have that manageable by the client, but i'm happy if it works that way.
Thank you for that bundle!

I've digged deeper into that filter issue. To get it to work I've added several methods in my repository class which are responsible for ordering and filtering for types (I made this to filter nearly every custom field, e.g. date comparison), tags and categories. See https://github.com/manuxi/SuluEventBundle/blob/afb1fab9f23f7b5a10e2ccd0c1987d31a1eac8fa/src/Repository/EventRepository.php#L221 - I think this would fit in your repository class with few adjustments...


Question: Do you want input/suggestions or are you treating this as read only?

Do you want input/suggestions or are you treating this as read only?

I would love suggestions, Let me know your inputs

Read only by now, nice reference!

@elmonkeylp Thanks, But I still think there is room for Improvement.


DXVK:

WineD3D:

System information

GPU: NVIDIA GeForce GTX 1660 Ti
Driver: 470.62.02
Wine version: Proton Experimental
DXVK version: v1.9.2

Apitrace file(s)

https://drive.google.com/file/d/1tkXJhBGzQyp-sUM7OW2fWcnxu78Qtqdf/view?usp=sharing (captured with WineD3D)

Log files

d3d9.log: game_d3d9.log

The vertex shader uses the LIT instruction with negative inputs. DXVK implements this with POW which is undefined on negative inputs and produces NANs for the tex coord.

So how to fix it? I have same issue for Fallout 4 on Windows

The issue in Euro Truck was fixed by us and it'll just work with any somewhat recent DXVK build.
Fallout 4 is a different game that uses a different graphics API. It's completely unrelated. If you want us to take a look, open a new issue and provide the necessary information (logs & apitrace).


Move sidecarContainers to be first in the list of containers

This fixes https://github.com/minicloudlabs/helm-charts/issues/93

Thank you.


Broken link for tf.debugging.assert_same_float_dtype

URL(s) with the issue:
Please provide a link to the documentation entry, for example:
https://github.com/tensorflow/docs/blob/r2.0/site/en/api_docs/python/index.md
Description of issue (what needs changing):
The link for tf.debugging.assert_same_float_dtype is dead
Clear description
The previous link leads to: https://github.com/tensorflow/docs/blob/r2.0/site/en/api_docs/python/tf/debugging/assert_same_float_dtype
The new link must be:
https://github.com/tensorflow/docs/blob/r2.0/site/en/api_docs/python/tf/debugging/assert_same_float_dtype.md
(The .md file extension is missing in the link)
Submit a pull request?
Yes, will be updating the issue soon enough

Hi, @theadityasam , I just checked https://github.com/tensorflow/docs/blob/r2.0/site/en/api_docs/python/index.md , let's call that index, and none of the links work. It's not only for assert_same_float_dtype, they do however work when I append '.md at the end. I guess this means a complete modification of the contents of the file /docs/index.md.
Please update your title as well as per the issue.

Is it okay if I look into this instead? Should be pretty easy for me.

Hey @Rubix982
Sure, work on the issue. I saw your PR, from what I gather, the index.md is generated by some script and I guess it's not as simple as adding .md to the url's(not really sure about that, need to ask the code owners once). Also, I believe the API docs were moved to the TF website and were deprecated in the previous versions.

@theadityasam
As there is a PR to monitor the issue, please confirm if we may move this to closed status.

Don't think it's right to close the issue until the PR is merged

@theadityasam PR successfully merged at https://github.com/tensorflow/docs/pull/1517 . This issue can be closed now.

Thanks


Merging in my additional decorator changes

Coverage remained the same at 100.0% when pulling a8260477a3464b9fdfd47357c65567ca05b01f45 on katylouise:katylouise/decorators into 3c9f66a6bf8e7fad53e0f91594b0dc0272a5572b on ukparliament:master.

Coverage remained the same at 100.0% when pulling 6c810a5bb8a4b56f17c50483117acada39a61695 on katylouise:katylouise/decorators into 3c9f66a6bf8e7fad53e0f91594b0dc0272a5572b on ukparliament:master.

Coverage remained the same at 100.0% when pulling 76f20aff8e18f2258f8fba8d8f52c1f13d6e437f on katylouise:katylouise/decorators into 3c9f66a6bf8e7fad53e0f91594b0dc0272a5572b on ukparliament:master.


Expand restore docs to cover questions raised by users

:nut_and_bolt: Description: What code changed, and why?
Cover user questions raised around restoring Automate in several scenarios:

Restore to a host on which Automate is already installed.
Restore to a host with a different FQDN than the one on which the backup was taken.
Restore in an airgapped environment.

:chains: Related Resources
:+1: Definition of Done
:athletic_shoe: How to Build and Test the Change
:white_check_mark: Checklist

[ ] I have read the CONTRIBUTING document.
[ ] Tests added/updated?
[ ] Docs added/updated?
[ ] All commits have been signed-off for the Developer Certification of Origin.

:camera: Screenshots, if applicable


Use separate SDG outputs for each phase of phased training

Instead of using the single messages jsonl file when testing phased training, we should be using the data-mixed separate outputs designed for the separate knowledge and skills training phases.

This is marked as a draft because I have no way to test it locally and CI doesn't actually test phased training yet. But, this is an idea of how I think this phased training test needs to be updated to work with SDG's new data mixing output.

This is still relevant,but also requires further work (or a separate PR) to get CI to actually run a phased training job. We could add this to the e2e-nvidia-a10g-x4 workflow, although that would substantially increase the time it takes to complete.

Closing this as CI has evolved a lot since this was opened.


How to start/stop autoplay with swiper without directive

I am trying to stop swiper autoplay when mouse is hovering and resume when its away. I am not using the directive method of swiper because i needed some fine grain control of template.
I am using swiper using config interface like below:
Template:

		<app-swipe-item class="swiper-slide" *ngFor="let product of products" [product]="product"></app-swipe-item>

Config:
swiperConfig: SwiperConfigInterface = {
	direction              : 'horizontal',
	slidesPerView          : 'auto',
	slidesPerGroup         : 1,
	keyboard               : true,
	loop                   : true,
	loopFillGroupWithBlank : false,
	preloadImages          : true,
	lazy                   : false,
	observer               : true,
	autoplay: {
		delay               : 4000,
		disableOnInteraction: false,
	},
}

Hover Function:
onSwiperHover( hover: boolean ) {
	if ( hover ) {
		this.swiperConfig.autoplay = false;
	} else {
		this.swiperConfig.autoplay = true;
	}
}

This works fine but it resets the autoplay duration. That means everytime i hover off - it takes 4000ms to start slide again. This also includes me crossing over the object when moving mouse to some other part of screen if the swiper was in its way.
I am trying to understand how to use the proper startAutoplay() and stopAutoplay() methods but so far no luck. Any thoughts?

Changing configuration re-initializes Swiper. You should use the Swiper api calls, see readme and example app how to get reference to the Swiper instance.

@sconix I tried going through the examples, The directive based approach is straight forward but the component based approach i cant seem to understand much about. Can you please point me to some specific example you are referring to.

I found a way, not sure if its the best approach though.
Added a local template variable:

@ViewChild('swiperEl') swiperEl: ElementRef;

onSwiperHover( hover: boolean ) {
	if ( hover ) {
		this.swiperEl.nativeElement.swiper.autoplay.stop();
	} else {
		this.swiperEl.nativeElement.swiper.autoplay.start();
	}
}

That works as well but I was referring to the example app provided in this repo. It has examples of using directive reference for both directive and component.


Bell does not show the raiders

In vanilla, the bell shows the raiders with an outline. This does not work in FactionCraft.

Fixed 1.0.3


Use of GetAwaiter().GetResult() causes deadlock inside specflow tests using SingleNodeReplicaSet

While updating my test code to use MongoSandbox i've come across a deadlock introduced by some changes to MongodProcess.cs
I believe it's a due to the use of GetAwaiter().GetResult() in ConfigureAndWaitForReplicaSetReadiness()
Here is the minimal replication
https://github.com/rbev/MongoSandboxIssueReplication/tree/4426f20576c089e0cd03c53a048285a5a645cf3a
    [When(@"specflow starts a MongoSandbox")]
    public async Task WhenSpecflowStartsAMongoSandbox()
    {
        await Task.Delay(200);
        using var db = MongoRunner.Run(new MongoRunnerOptions()
        {
            UseSingleNodeReplicaSet = true
        });
    }

I'll note that a workaround seems to be to wrap the call in another task, so it might just need ConfigureAwait(false) added to it.

Thanks @rbev for raising the issue, it has been fixed in v1.0.1


Fix: Fixed issue where pinned applications were executed in %windir%\System32

Resolved / Related Issues

[X] Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
Closes #14405

Validation
How did you test these changes?

[X] Did you build the app and test your changes?
[ ] Did you check for accessibility? You can use Accessibility Insights for this.
[ ] Did you remove any strings from the en-us resource file?

[ ] Did you search the solution to see if the string is still being used?

[ ] Did you implement any design changes to an existing feature?

[ ] Was this change approved?

[X] Are there any other steps that were used to validate these changes?

Pin C:\Windows\System32\WindowsPowerShell\v1.0\powershell_ise.exe
Execute pinned powershell_ise.exe
The program will now be executed in C:\Windows\System32\WindowsPowerShell\v1.0, not C:\Windows\System32

I have not checked, but this may resolve #12950 and #14419 as well.

doesn't fix #14419 for me, likely doesn't fix #12950 either but I can't test that

Thank you for checking. It means #12950 and #14419 are different issues.


Attach APK to release?

Hi Peter,
would you consider attaching the .apk file with your releases/ here on Github – so people running Google-free devices w/o Playstore access can grab your app? I'd then even offer to add it here, so your users can get updates automatically using the F-Droid client.
Thanks in advance!

Hello there,
Sorry for the delay. I attached the APK for the last release and will do so in the future, it's actually a good idea.
As for F-Droid, I'll pass on that since I'm not really interested in being listed in those kind of repo. I want PlayStore to be the only "officially supported" way to get the app.
Thanks

First thanks! So just to make sure I understood you correctly: Would you answer the question on whether I may include your app in my repo with a "No" – or would it be OK for you if I include it? I hope for the latter. Just to resolve possible doubts: There are no extra steps involved for you. With the .apk attached to the releases here, I'd take care for the rest. No obligations for you :)

Yes you read correctly, I don't wanna be listed in your F-Droid repo.
I want PlayStore to stay the only way to get automatic updates and new features. If people want to have the APK without the PlayStore it's now available here, and it should be enough :)

Not the answer I was hoping for, but I of course respect it. Thanks anyhow for making it available via the releases page :)


Fix FakeS3 to support copying of objects with prefixes

Previously the implementation consistently returned 404's because the source key could not be found in the bucketContent

Codecov Report

Merging #61 (9e701c0) into master (54bac5b) will not change coverage.
The diff coverage is 0.00%.

@@            Coverage Diff            @@
##             master      #61   +/-   ##
=========================================
  Coverage     59.16%   59.16%
  Complexity      625      625
=========================================
  Files           342      342
  Lines          3394     3394
  Branches        263      263
=========================================
  Hits           2008     2008
  Misses         1215     1215
  Partials        171      171

Impacted Files
Coverage Δ

.../org/http4k/connect/amazon/s3/endpoints/copyKey.kt
89.47% <0.00%> (ø)

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 54bac5b...9e701c0. Read the comment docs.


crypto/tls: improve server-side (lack of) renegotiation docs and error message

What version of Go are you using (go version)?

$ go version
go version go1.13.5 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
amd64/linux
What did you do?

I am unable to renegotiate successfully using TLS 1.2 to a Go server I wrote. https://play.golang.org/p/Q39eh8PVAOP. After starting the server, I connect using openssl:
openssl s_client -connect <IP_ADDRESS>:10000 -tls1_2. Following a successful handshake, and some test messages going through, I start a renegotiation by sending R in the openssl client session. The renegotiation fails because the Go server expects a helloRequestMessage as the first message in the renegotiation while theopenssl client sends a clientHelloMessage as the first message in the renegotiation.
What did you expect to see?
A successful renegotiation as demonstrated when running the same server using openssl s_server -key /home/vagrant/easy-rsa/easyrsa3/pki/private/server.key -cert /home/vagrant/easy-rsa/easyrsa3/pki/issued/server.crt -accept 10000.
And output from renegotiation on the client:
R
RENEGOTIATING
depth=0 CN = server
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 CN = server
verify error:num=21:unable to verify the first certificate
verify return:1

What did you see instead?
On the server:
$ go run test.go
2019/12/26 15:30:25 New connection
2019/12/26 15:30:26 tls: received unexpected handshake message of type *tls.clientHelloMsg when waiting for *tls.helloRequestMsg
exit status 1

On the client:
---
R
RENEGOTIATING
4684979820:error:140043F2:SSL routines:CONNECT_CR_SRVR_HELLO:sslv3 alert unexpected message:/BuildRoot/Library/Caches/com.apple.xbs/Sources/libressl/libressl-47.11.1/libressl-2.8/ssl/ssl_pkt.c:1200:SSL alert number 10
4684979820:error:140040E5:SSL routines:CONNECT_CR_SRVR_HELLO:ssl handshake failure:/BuildRoot/Library/Caches/com.apple.xbs/Sources/libressl/libressl-47.11.1/libressl-2.8/ssl/ssl_pkt.c:585:

@FiloSottile

We only support renegotiation on the client side. Go servers don't support renegotiation.
The error message and the docs can be improved.

Moving to backlog milestone.


Rename project to a more generic name

The current project name (conventional-changelog-lint) implies that this tool is designed to be used with conventional-changelog. Regardless of whether thats true or not, the tool itself has potential for broader applications.
A good name would be something like commitlint.

Hey @gajus, thanks for your suggestion!
I chose the name due to the fact this tool uses conventional-commits-parser under the hood, which basically limits it to conventional-changelog semantics.
To hold true to the commitlint name this would have to be broadened quite a bit and replace  conventional-commits-parser with a custom parser, possibly using natural language processing.
Most likely this is a sizeable chunk of work which I'm currently not planing to invest into this topic. Given we can muster some collaboration effort and fill the broader scope I'd rename the project.

To hold true to the commitlint name this would have to be broadened quite a bit and replace conventional-commits-parser with a custom parser, possibly using natural language processing.
[..]
Given we can muster some collaboration effort and fill the broader scope I'd rename the project.

Do you have specific rules in mind that you think would be required to move from the current project scope to commitlint?
It seems that you already have quite a broad coverage. Even compared to services such as https://gitcop.com/, conventional-changelog-lint implements more rules.

I think this of this more as a matter of entanglement with conventional-changelog semantics than of the perceived absolute rule coverage. Perhaps this is not as relevant as I first thought – I'd have to search for a commit convention that could not be linted with this to prove my point. :trollface: What type of convention are you testing via conventional-changelog-lint in your projects?

What type of convention are you testing via conventional-changelog-lint in your projects?

https://gist.github.com/gajus/b57fd0ce6cc6de09867bbc331c4ddaf0#file-conventional-changelog-lintrc-json
Basically, Angular convention minus the scopes.

Thought about splitting the angular convention in distinct parts - the scopes could be one of them...

Will rename to commitlint or gitlint eventually. Things to do before this:
[ ] https://github.com/marionebl/conventional-changelog-lint/issues/7
[ ] https://github.com/marionebl/conventional-changelog-lint/issues/17
[ ] https://github.com/marionebl/conventional-changelog-lint/issues/18
[ ] https://github.com/marionebl/conventional-changelog-lint/issues/19

Done!


Add option for search field to specify ONLY title, author, or abstract

Hi Devin,
Please consider adding this feature. I think it will improve the search feature!
Currently you can search all 3 at once, but if I were to type "LLM" as if I wanted to see titles that include "LLM", it pulls up primarily papers involving author Jessical Hullman

I would suggest turning on the match case option, or turn on the regex option and search \bLLM\b. Both are toggle buttons inside the search bar.

Regex option:
https://vispubs.com/?searchText=%5Cbllm%5Cb&useRegex=true
Match case option:
https://vispubs.com/?matchCase=true&searchText=LLM

Closing for now since I think the current features can solve this specific request.
Please reopen if something cannot be solved with the current features.


Selecting area highlights wrong section in Canary UI

Background
When the page is scrolled while viewing a chrome trace, the selection highlighting is offset from the actual tracks being selected.
For example, if I begin selecting the track where the arrow is, the selection box while dragging will appear where the red box is

This can be reproduced on the latest canary by opening the example chrome trace, opening some of the panel containers to get a scroll bar, scroll slightly down and then try selecting either of the first two tracks in the first panel container.
Workaround
This appears to be fixed by reverting this change: https://github.com/google/perfetto/commit/64e41ec3ae7a65c5186f6901c572403bdd480b3e

Thanks for the report! Looking at the bug

Doesn't look like anything to do with layerX as far as I can tell: selection is performed correctly, the issue is that while you're doing the selection the box is displayed incorrectly. Rendering is done in this function, probably some assumption that was correct does not hold anymore: https://crsrc.org/c/third_party/perfetto/ui/src/frontend/panel_container.ts;l=420?q=panel_container.ts

Pending fix: https://r.android.com/2089347

Fixed in 625c0da53fbd4efd26d5a6878a91264b4feb2d35


Commit 88c8564eb58d28768165fde0d6ab9e88b42ddc8f deleted python3-pyqt5

Is this intentional? The commit message only mentions qtwebkit and ruby, nothing to do with python3-pyqt5

Probably not intentional, but it depends on sip3 which was removed in:
https://git.openembedded.org/meta-openembedded/commit/?id=4dc1c6e16b31d30aca05c52fa0209c74eedd6842
so someone needs to resolve these issues before it can be built again.


[FEATURE] Disable automatic resizing of the canvas

At the moment it's not possible to disable automatic resizing of the canvas. Besides that there is a bug in the automatic resizing, I don't want the functionality at all for my project.
Would it be a good idea to add a parameter 'IgnoreResizing' / 'DisableAutomaticResizing' to the canvas? Setting the value to 'true' will not load the SizeWatcher JavasScript at all: https://github.com/mono/SkiaSharp/blob/3c721d250969ba6d0617827a3aa1d4f15fe95747/source/SkiaSharp.Views.Blazor/SkiaSharp.Views.Blazor/SKCanvasView.razor.cs#L70
I could add the functionality if you are open for it? Thanks in advance!

AutoResize might be a better parameter name. Usually names are such that true is the enabled state.

why would you want to disable automatic resizing?

why would you want to disable automatic resizing?

Because sometimes you have the requirement of a fixed width and height for the canvas. I stumpled upon this issue searching for options on how to set width and height to a specific value but did not find any. Then I had a look at the source code just to see that JSInterop is overriding my initially set width and height settings. So, I am in the same boat as @Code-Chops requiring the auto size thing to be controllable.

You should not set width/height of the canvas directly, and instead use the styles:
<SKGLView OnPaintSurface="OnPaintSurface" style="width:100px; height:100px;" />

In order to not have a blurry canvas, we need to change the stile to be <style-size> * <screen-density>:
https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API/Tutorial/Optimizing_canvas#scaling_for_high_resolution_displays

@mattleibow Yep, the inline style solution is also discussed in https://github.com/mono/SkiaSharp/issues/2038 and specifically comment https://github.com/mono/SkiaSharp/issues/2038#issuecomment-1129008602 provides a ruleset that avoids the automatic resizing, at least visually, the internal services are still running. I think the issue can be closed.


How do I get the address of the variable name in the stack frame local variable?

I have access to PdbScope，I'm trying to get the values of some simple local variables，It would be nice if someone could provide a small example。
thanks thanks thanks

This is not supported in ClrMD.  You will have to use ICorDebug for that, which is not something owned by this project.


Using ownership .tag() method causes unwanted save on object being tagged.

So in my current Rails project we're using acts-as-taggable-on.
https://github.com/mbleigh/acts-as-taggable-on
There are many accounts in the system and each account has many events.
 These things can be tagged and the tags need to be owned by the event so as to not bleed over into another event's tag cloud.
acts-as-taggable-on has support for this. From it's readme some sample code:
class User < ActiveRecord::Base
acts_as_tagger
end
class Photo < ActiveRecord::Base
acts_as_taggable_on :locations
end
@some_user.tag(@some_photo, :with => "paris, normandy", :on => :locations)
The problem I'm experiencing is that when I call a method like this it is causing a .save method to be called on @some_photo. This screws me over since I'd pref to keep track of a transient string to manage the human editable tag list and execute the official tagging after_save -- but if doing the official tagging in after_save causes a save I end up with a execution loop and crash Ruby (or throw a more friendly exception on Ruby 1.9.3).
I don't think observers would help me since they sit atop the save callbacks too.
I feel like this is a bug in acts-as-taggable-on (in that using the .tag() method causes a side effect .save to be called on the passed in attributes but I'm hopeful to work around it if I can cause there don't seem to be alot of other tagging modules being actively worked on and I'd pref not to write my own.
Any feedback or suggestions welcome.

@zorn i will add skip_save option, so save will be skipped and you will be able to perform that when you want.

Cool. That's pretty much what I did in my fork.
https://github.com/zorn/acts-as-taggable-on/commit/53c2ade0cac524263005c1aadc5cfa9f55ddcc52


Use stack instead of recursion for List iterator

Otherwise, it causeses "RanegeError: Maximum call stack size exceeded"
when the list is long (e.g., 2000+)

Pull Request Test Coverage Report for Build 1428

11 of 11 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 77.608%

Totals

Change from base Build 1426:
0.02%

Covered Lines:
10225

Relevant Lines:
12667

💛  - Coveralls


Investigate if a Kalman filter is useful

Ref https://en.wikipedia.org/wiki/Kalman_filter
Eg. To smooth out jittery or sudden value changes

@licaon-kter any explanations here?

I'm not familiar with this algorithm. Could you elaborate a bit on the problem/use case that this would benefit?

Not sure if needed really (in theory GPS data is already Kalman filtered to a degree).

Makes sense. Will tag as wontfix for now. The Android geolocation provider seems to be quite stable and accurate, and accuracy does increase as more fixes are obtained already.


randFullName is in Address docs.

Is this a regression?
No
Description
randFullName is apparent in the address funcs section in the docs (and link is broken)

Please provide a link to a minimal reproduction of the bug
https://ngneat.github.io/falso/docs/address#randfullname
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in
No response
Anything else?
No response
Do you want to create a pull request?
No

It should be fine now. Thanks.


Distribute test utility functions

Describe the problem
As a consumer of MRTK I would like to be able to easily write integration tests that utilize MRTK systems. For example, simply triggering a button click requires the scene is setup and configured propertly. Internal tests have utility functions here and here. Unfortunately, those functions are difficult to access as they are not distributed as packages and come with the internal test suite which depends on nearly every other part of the code base.
Describe the solution you'd like
I would like all test utility functions to be packaged with the tools.
Describe alternatives you've considered
I've looked into better ways to mock inputs. For example, if Interactable implemented an IClickable interface, then I could have provided dumbed down version for testing. I wasn't able to come up with an easy way to mock this particular dependency though.

This is actually something that we're looking at right now with some of our NuGet packages - i.e. the test infrastructure that we have (around showing hands, moving things, etc) is pretty handy for writing tests and preventing regressions and has been a big part of what allows us to prevent random things from breaking.
Definite +1 here for making this possible.
@FreakTheMighty specifically are you looking for maybe a .unitypackage containing the test infra that we have?

A unitypackage would be fine. I'm sure somewhere there's discussion about moving to UPM, but I'll take it however the rest of the framework is distributed.

We are considering adding the testing utilities to the Tools package (unitypackage, nuget initially). Would that work?

I'm not terribly familiar with what else is in the tools package, but seems like a fine place to me. The developer experience I'm looking for is the relatively easy installation of these utility functions.

@davidkline-ms chat with @CDiaz-MS on what's she's working on, it's not adding to the Tools package (which itself has a ton of things that you may not actually be interested in if you're just writing tests)


Spider: Creve Coeur Stormwater Committee

URL: https://crevecoeurcitymo.iqm2.com/Citizens/Calendar.aspx?From=1%2F1%2F1900&To=12%2F31%2F9999
Spider Name: cc_stormwater
Agency Name: Creve Coeur Stormwater Committee
See the contribution guide for information on how to get started

I'll start on this issue


Where is scale2x.pth?

The following code was executed in colab.

!python -m waifu2x.web
FileNotFoundError: [Errno 2] No such file or directory: '/content/nunif/waifu2x/pretrained_models/swin_unet/art/scale2x.pth'

How can I get the file scale2x.pth?
Can't I use it with COLAB in the first place?

from README

Download pre-trained models.
python -m waifu2x.download_models
This command downloads the pre-trained models to waifu2x/pretrained_models.

You can also download it manually from the link in the Release section.
https://github.com/nagadomi/nunif/releases/tag/0.0.0 (waifu2x_pretrained_models_20230202.zip)

I tried waifu2x.web with Colab. It seems to work.
Install
!git clone https://github.com/nagadomi/nunif
%cd nunif
!pip3 install -r requirements.txt
!python -m waifu2x.download_models
!python -m waifu2x.web.webgen.gen

Running waifu2x.web as a background task (larger image size limit)
!mkdir -p tmp/
!python -m waifu2x.web --port 8812 --max-pixels 16777216 --max-body-size 100 > ./tmp/server.log 2>&1 &

Show inline Web UI on Colab notebook
from google.colab import output
output.serve_kernel_port_as_iframe(8812, "")

Thank you very much. It worked. Sorry for the late reply. It was very helpful.


@conda-forge-admin, please add user @bnavigator

Additional comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @bnavigator in conda-forge/slycot-feedstock#54.


Rebuild ManilaShares list

We're currently not able to trigger a shareCleanup reconciliation loop when the top-level CR is updated and a ManilaShare entry is removed. In the effort of adding the shareCleanup feature in [1], we need to fix the openstack-operator code to rebuild a fresh version of ManilaShares from the existing CR.
Similarly to Cinder [2], this also fixes a regression for users who wants multiple shares with different backends after the initial deployment.
Jira: https://issues.redhat.com/browse/OSPRH-6525
[1] https://github.com/openstack-k8s-operators/manila-operator/pull/79
[2] https://github.com/openstack-k8s-operators/openstack-operator/commit/ede5a0645f17b2b5e4a06ac8c660f9cdd7507424

/test openstack-operator-build-deploy-kuttl

recheck

I think you'd have to rebase to get https://github.com/openstack-k8s-operators/openstack-operator/pull/1084 ?

I think you'd have to rebase to get #1084 ?

aah makes sense! thank you!

recheck

Tested locally and I can see the new reconciliation loop being triggered now when we delete a share.

/test openstack-operator-build-deploy-kuttl


Possibility to Set default timezone

All of my dates I'm using are in UTC, if I want to compare them with the holidays I always need to change the timezone.
So I think setting a default timezone either globally Yasumi::defaultTimezone or during creation as an extra parameter Yasumi::create(Germany::class, 2017, 'de_DE', 'UTC') would be very helpful.
As long as the default timezone is not set, it uses the timezone provided by the initialize method.
I'll create a PR once this is approved. :-D

The reason for the timezone not being configurable is that holidays should be calculated for the timezone (i.e. country) they are taking place in. If what you are suggesting would be done, then a strange situation occurs that for example Christmas may have already started (or finished) from the perspective of the other timezone.
Although that technically is correct, semantically has little meaning. You can consider for example New Year (Change at 00:00). If I would set New Year Midnight in Germany to a different timezone (for example Asia/Tokyo, which is UTC+9 hours), then the results would be that midnight has taken place already, where in reality it is still 9 hours before (UTC).
This is the primary reason, why a timezone isn't configurable, and any time conversation should be taken place outside this API.
Hope it makes sense :)
Cheers! Sacha

I can't be the only one who stores dates as UTC in the database and relies on the frontend to decide which timezone the users in.
As I said before all I want is to make the timezone decision myself. As of now that is impossible, because everything happens in the initialize method and I can't change that value by Inheritance or even Reflection.
PS: I don't want to compare Germany New Years Eve with the Japanese one ;-)

Sure, I store my dates in UTC as well. I am not familiar with your business case, so let me show you what I do in one of my projects.
I am sending a message to users when they login and that day is a public holiday. In this example I am using Japan's Mountain which takes place on August the 11th.
// User logged in on 2018-08-10 at 21:34:14 UTC (This is 2018-08-11 06:34:14 in Asia/Tokyo)
$login_date = Carbon::parse('2018-08-10 21:34:14', 'UTC'); // Date comes from the database

$japan = Yasumi::create('Japan', 2018);
$mountainDay = $holidays->getHoliday('mountainDay');

if($login_date->greaterThan($mountainDay)) {
    // Send the user an e-mail
}

The above example is a bit simplified of course and I am using the Carbon library for parsing and handling dates. In this case Carbon is taking care of the timezone conversions.
As you can see, there is no need for me to tell Yasumi what timezone I am using.
If you have an example of yourself, that would be great. So I can understand better your scenario/case.
Cheers! Sacha

Sorry I should have added my business case earlier:
For calculating vacation days, I need to know which days are holidays in date ranges.
This is of course a simplified version of my code and should only represent an example for this case:
use Carbon\Carbon;
use Yasumi\Provider\Germany\NorthRhineWestphalia;
use Yasumi\Yasumi;

// These dates get returned from the ORM so I can't just change the timezone
$dateStart = Carbon::parse('2019-01-01 00:00:00', 'UTC');
$dateEnd = Carbon::parse('2019-01-04 00:00:00', 'UTC');

// count weekdays in range
$dayCount = $dateStart->diffInWeekdays($dateEnd, false);

// First holiday would be newYearsDay (2019-01-01T00:00:00+01:00)
$provider = Yasumi::create(NorthRhineWestphalia::class, 2019, 'de_DE');
foreach ($provider as $holiday) {
    $carbonHoliday = Carbon::instance($holiday);
    // for new years this would return false as newYearsDay converted to UTC would be 2018-12-31T23:00:00+00:00
    if ($carbonHoliday->between($dateStart, $dateEnd)) {
        $dayCount--;
    }
}
echo $dayCount;

This would return 4 instead of the correct 3 workdays in range.

Thanks for the example. Very helpful. So if I understand correctly, the expected number of vacation days is 4, however your returns 3.
The reason is that the time of your $dateEnd is '00:00:00', which means start of the day, but isn't a full day. When doing a date comparison, this date will not be included, because also the date to check against has a time value of 00:00:00.
If you this after the $dateEnd..... line:
$dateEnd->endOfDay();
you will get 4 vacation days.

No, the expected number of vacation days should be 3 as '2019-01-01' is new years day and "between" $dateStart and $dateEnd.
But it returns 4, because of comparing 2 different timezones to each other. It has nothing to do with $dateEnd->endOfDay();
This code actually works correctly, if all dates use the same timezone.

Sorry then misunderstood you first example. However, if I run your original example again, I get 3 days as output. (as you expected).

Yeah should have tested the example. So the end date actually needs to be endOfDay.
I fixed the example, which still doesn't change my issue though.

Today I've spent more time understanding your example and did some experimentation.
Still I am confused what your business case is. Your initial date range returns 3 weekdays (January 1st, 2nd and 3rd). The second part of your example where you use Yasumi, you reduce the number of days in case the day in your day range happens to be a holiday. This part is I believe not needed, as for 2019 January 1st falls on a weekday. Should a holiday fall in the weekend, it isn't counted either because it is not a weekday.
Apart from your proposal regarding the timezone, you would not need to this check with Yasumi at all.
Also, I've tried many varieties with timezone conversions, and you will always have an offset of 1 hour. Keep in mind that Yasumi returns only a single point in time (the start time of that event), and not a date range. Just checking a DateTime instance against a date range with different timezones, is too simplified. If you do, you also then need to check the end time of the event.
Your proposal (as I understand) would basically mean you do a force override of the local timezone of the Holiday instance. This might solve your problem/business case, but would result in other issues when using the instance for the local timezone again. Feels to me that you would then swap out the timezone depending on the circumstance, which is in my opinion unmanageable.
Happy to hear your feedback/thoughts.
Cheers! Sacha

Hi Sacha,
I try it from a business perspective now with no code. :wink:
Employee John has 25 vacation days each year.
John plans a vacation from 2019-04-15 to 2019-04-28 which are 14 days in total. But he would only use 8 of his vacation days, because the 19th and 22nd are public holidays and he only works from monday to friday.
John also went on a vacation from the 2019-01-01 to 2019-01-04 which are 4 days in total, but the 1st is a public holiday, so he only used 3 vacation days.
So he has 14 vacation days left.
The first vacation gets calculated correctly and my code returns the proper amount of vacation days used, because the public holidays are not on the first or last day of the vacation.
The second vacation gets calculated with 4 days instead of the actual 3 vacation days used.
This is because I compare the Holiday (with the 'Europe/Berlin' timezone) against the vacation (with the 'UTC' timezone).
The problem is that the holiday date 2019-01-01T00:00:00+01:00 is not inside the vacation date range of 2019-01-01T00:00:00+00:00 and 2019-01-04T23:59:59+00:00.
All I do in the code is check if any of the holidays are inside of the vacation date range and reduce the number of vacation days used for the vacation. In my example I didn't add the logic which checks if its a weekday or not to simplify the example.
I hope this helps to better understand my problem. :smile:

Hi Moritz,
Thank you very much for providing your business case. It indeed helped me much better understanding what you want to achieve.
As said, DateTime instances - and also Yasumi's Holidays - are a single point in time and not a date range. For your example, it is irrelevant what the start time of a holiday is, however since you get the dates from an external source (with the time element), you also then need to provide an end time.
That would make it a bit more complex when checking whether a date falls into a date range or not.
As a matter of fact, Yasumi's API has a function that will help with your case: isWorkingDay. This function will check if the given date is a working day or not. It actually ignores the time element of the date and has logic for the weekend days as well (Supporting all countries).
Please have a look at this gist I've created for you: https://gist.github.com/stelgenhof/14a14e1ab2d3123cf81aaff866ecda49
Taking a bit of a different approach and using the isWorkingDay function, It calculates perfectly all the remaining days (and consumed days) in your business case. The gist may look a bit complicated but contains just some helper functions to format the output nicely in your shell.
Cheers! Sacha

Hi Sacha,
Thank you for the gist! That works for me.

@IceShack Thanks! Good to hear it works for you. I'll go ahead and close this issue and the PR.
Cheers! Sacha


Concurrent Spatial and Channel SE

Paper
Implement SE version from Concurrent Spatial and Channel ‘Squeeze &
Excitation’ in Fully Convolutional Networks
TODOs

[x] develop the model in a scalable way (using *Block syntax and nn modules)
[x] draw the model on figma
[x] write doc
[x] test the model
[x] get (if possible) the pretrained weights

done with #94


Please refer to net.minecraftforge.oredict.RecipeSorter

[22:26:00] [Client thread/INFO] [FML]:   Unknown recipe class! shedar.mods.ic2.nuclearcontrol.StorageArrayRecipe Modder please refer to net.minecraftforge.oredict.RecipeSorter

Repost from: MyM-ModpackTeam/B2B#6
Weirdly enough it says shedar on there making me think of going https://bitbucket.org/shedar/ic2-nuclear-control/ But this Github is where the IC2 forum post links me to. Sorry if this is the incorrect place to post.

Right place, yes. Shedar is the original creator of the mod. I'm the unofficial maintainer (but I'm mostly lazy nowadays).

I can fix this :) Later today probably

Thank you. Probably was not game breaking, I just hate red in my logs. Muahaha


Changes to git sync configurations are not detected

Git sync setup works great, however if change is made in the UI and a different repository is selected as git sync destination, the provider does not detect drift next time plan is ran.
Is this a limitation of the API?

Hi @stan-yago, can you please share more details?

Example terraform configuration (steps to reproduce)
Error faced

@rijajoo Sure the terraform code to setup git connector and link the connector to an app
`resource "harness_git_connector" "git_connector" {
name   = "${local.github_repo_name}-git-connector"
url    = github_repository.app_repo.ssh_clone_url
branch = local.branch
commit_details {
author_name     = var.harness_committer.commit_author
author_email_id = var.harness_committer.commit_email_id
message         = var.harness_committer.commit_message
}
usage_scope {
application_id          = harness_application.harness_app.id
environment_filter_type = "NON_PRODUCTION_ENVIRONMENTS"
}
usage_scope {
application_id          = harness_application.harness_app.id
environment_filter_type = "PRODUCTION_ENVIRONMENTS"
}
url_type             = "REPO"
generate_webhook_url = true
ssh_setting_id       = harness_ssh_credential.ssh_creds.id
}
resource "harness_application_gitsync" "git_sync" {
app_id       = harness_application.harness_app.id
connector_id = harness_git_connector.git_connector.id
branch       = local.branch
enabled      = true
}`
Now if a change in the UI is made to point the harness app to a different git repository, then when re-running terraform plan the expectation is that this change would be detected so that it could be reverted with apply.


Publishing to subgroups

I may have identified a bug, though as always, more likely a user error. When the org/groupId is set to w.x.y.z in the build.sc file and I own the groupId w.x.y on Maven/Sontatype/whatever.
I'm getting this error now: Could not find staging profile for groupId: edu.cornell.ncrn.ced2ar. I've uploaded to this groupId before using maven/pom, but the issue might be that the top level groupId associated with the profile is actually just edu.cornell.ncrn.
So I thought on this line ( https://github.com/lihaoyi/mill/blob/master/scalalib/src/mill/scalalib/publish/SonatypeHttpApi.scala#L39 ), maybe it should be checking that profile("name").str is a substring of groupId (rather than equal to it). But I tested it out locally (hopefully correctly using mill/out/dev/launcher/dest/run) using the change .find(profile => profile("name").str.startsWith(groupId) and got the same error. So, I'm not sure what to investigate next.

I had it backwards, this is fixed by #441

Fixed in #441


Option to set/force isTerminal to be true.

I've wrapped the standard os.Stdout/os.Stderr io.Writer options, and also use io.MultiWriter for potentially multiple output targets. I do this because I have a layer of text processing to take place before output hits the terminal. With the latest updates to this library (and logrus) logging is now downgraded because io.Writer is not an *os.File but instead my custom wrapping type. Perhaps this is really an issue with logrus but it seems like it would be nice to force terminal status.

Disregard.
I posted an issue to add an interface that I can implement to determine if my custom type is a Terminal or not. This is definitely not something this formatter should worry about. Not only that, but my custom type no longer needs to do color processing, I can move that into hooks. But I still use io.MultiWriter and would want to implement (myself) whether or not to report if the multi-writer is a terminal or not.

=)


Katana for macOS

changes are up

Great, there are tho few little things that I'd fine tuning. But before that I think we should make a decision: how many framework do we want to create?
I guess we can go for:

KatanaIOS
KatanaMacOS
KatanaIOSElements
KatanaMacOSElements

or for
I guess we can go for:

Katana (both iOS and macOS)
KatanaElements (both iOS and macOS)

for a mix

Katana (both iOS and macOS)
KatanaIOSElements
KatanaMacOSElements

when skyping we were leaning towards the second options but I still see both targets. is that WIP or you changed your mind? what are pros and cons? TBH I'm not 100% convinced on what's the best solution.

No strong opinion for what concern the framework composition.
Maybe having Katana that is able to work both on iOS and Mac would be better.
The only doubt I have is about testing (because I'm ignorant probably). Can we test katana both on iOS and Mac?

I agree having one single Katana framework for iOS and macOS is better. For what concern the tests we can have them but we need to: a. restructure the tests to not include UIView like now (maybe using a fake View) or b. add tests for the macOS part

I'll try to list hear what I feel it's missing so we have a TODO list before we merge in master. Feel free to challenge it.

[x] Update the readme
[ ] Update the pod spec
[ ] Test the integration with Carthage
[ ] Write macOS test target
[ ] Write macOS elements target (with View and Button)
[ ] Make sure CI test both platform
[ ] Create a simple Demo (or update HN to support both platform)

added test for macOS (tests for deallocation are not passing @lucaquerella, please have a look)

added View and Button Elements for macOS
updated the Katana macOS Coordinate System to match iOS
updated the demo for macOS


add OpenBSD support

Description
add OpenBSD support, as described in the title.
Motivation and Context
Simply I want to use Contour-terminal on OpenBSD.
I have to test sj3 (Japanese Kana-Kanji converter) tty client with status-line capable terminal emulator, and I found contour.
How Has This Been Tested?
Tested with OpenBSD-current/amd64 and libunicode/boxed-cpp (by private ports).
To check changes are not harm for other platforms, I also build modified code on Void Linux.
Both OpenBSD and Void Linux could not support Qt6. Only Qt5 works.
Checklist:
Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[ ] I have read the CONTRIBUTING document in my spoken language, and understand the terms
[ ] I have updated (or added) the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] I have gone through all the steps, and have thoroughly read the instructions

well, it is not the time to put 'x' in all the boxes yet.
CONTRIBUTING.md is 404, early to add OpenBSD support to documents, and test method is simply "pass the compile" or not.

Wow. This is awesome! Manyh thanks, @jg1uaa for your very valuable contribution. I will have a closer look ASAP. :)

Hi @jg1uaa
As you can see from actions: this changed breaking some other platform, the reason being is that libxcb installed separately and not as a part of X11, so you need to distinguish between openbsd and all other os, you can do something like this:
if(${CMAKE_SYSTEM_NAME} MATCHES "OpenBSD")
    set(OPENBSD TRUE)
endif()

and then
        if(NOT(WIN32) AND NOT(APPLE) AND NOT(OPENBSD))
            target_link_libraries(contour Qt5::X11Extras xcb)
        endif()
        if(OPENBSD)
            target_link_libraries(contour Qt5::X11Extras X11::xcb)
        endif()

Also, if you want us to keep an eye on openbsd builds you can add openbsd github action using:
https://github.com/vmactions/openbsd-vm
And we already have one for freeBSD
https://github.com/contour-terminal/contour/blob/4c71d0cce2e63a23859a1cf7b389dc9e872384a1/.github/workflows/build.yml#L288-L321

I am planning to use libunicode and boxed-cpp as OpenBSD-ports and today I posted them.
https://marc.info/?l=openbsd-ports&m=171961710727187&w=2
https://marc.info/?l=openbsd-ports&m=171961232324802&w=2
If they are added to ports (and released with new revision, OpenBSD-7.6), build.yml and install-deps.sh can be fixed.

@jg1uaa May thanks.
I think there's not much left.
Would you mind adding a changelog entry to metainfo.xml? Because that's actually a good thing worth mentioning. For example at around:
https://github.com/contour-terminal/contour/blob/4c71d0cce2e63a23859a1cf7b389dc9e872384a1/metainfo.xml#L107-L112
And secondly, would you mind adding the bits for ensuring we keep building on openBSD by adding it to build.yml? It is probably best done by somebody who knows openBSD best. We really value this contribution. I think it's best preserved by making sure we retain support in the future as good as it would work today :)

libunicode and boxed-cpp is now at OpenBSD ports. Avilable for OpenBSD-current and future coming OpenBSD-7.6.
http://cvsweb.openbsd.org/ports/devel/boxed-cpp/
http://cvsweb.openbsd.org/ports/textproc/libunicode/
to test on vmactions, we have to wait release of OpenBSD-7.6, fix termbench-pro (it has  related problem) and prepare some stuff (build.yml, metainfo.xml, install-deps.sh).

Thanks for the update, termbench-pro is optional dependency and can be disregarded for the packaging I think. We have new release coming soon so we can switch to packaged versions of libunicode and boxed-cpp later, install-deps.sh script will fetch them locally when needed, so i think that we can create action to build contour to merge this PR without the need to wait for next release

@jg1uaa  I added openbsd github action and added info about openbsd support, do you want to add something to this PR? otherwise we can merge it

currently there is nothing to add this PR. thanks!


CCD code of N-glycan modifications

Hi,
I'm looking to model a protein sequence including some modifications: N-glycosylation of some Asn residues.
I tried to input this by using CCD code "NAG" or "ASN_NAG" and the specified residue number, but this did not correctly attach a N-glycan.
What is the correct input for N-glycan modifications of the protein sequence input?
Thanks,
Jelle

Hi Jelle,
The CCD described in the modifications field of the JSON will replace the residue in the original sequence, and currently, only a single CCD replacement is supported. To address your issue, you should input a separate "ligand" and use the covalent_bonds field to describe the covalent bond from NAG to ASN.
You can find more details about covalent_bonds here: covalent_bonds
Here is an example of 7ZAV:

{
"sequences": [
{
"proteinChain": {
"sequence": "ETGDATCHQVRSFFQRLQPGLKWVPETPVPGSDLQVCLPKGPTCCSRKMEEKYQLTARLNMEQLLQSASMELKFLIIQNAAVFQEAFEIVVRHAKNYTNAMFKNNYPSLTPQAFEFVGEFFTDVSLYILGSDINVDDMVNELFDSLFPVIYTQMMNPGLPESVLDINECLRGARRDLKVFGSFPKLIMTQVSKSLQVTRIFLQALNLGIEVINTTDHLKFSKDCGRMLTRMWYCSYCQGLMMVKPCGGYCNVVMQGCMAGVVEIDKYWREYILSLEELVNGMYRIYDMENVLLGLFSTIHDSIQYVQKNGGKLTTTIGKLCAHSQQRQYRSAYYPEDLFIDKKILKVAHVEHEETLSSRRRELIQKLKSFINFYSALPGYICSHSPVAENDTLCWNGQELVERYSQKAARNGMKNQFNLHELKMKGPEPVVSQIIDKLKHINQLLRTMSVPKGKVGTKHHHHHH",
"count": 1
}
},
{
"ligand": {
"ligand": "CCD_NAG",
"count": 2
}
}
],
"modelSeeds": [],
"assembly_id": "1",
"covalent_bonds": [
{
"left_entity": "1",
"left_position": "96",
"left_atom": "ND2",
"left_copy": 1,
"right_entity": "2",
"right_position": "1",
"right_atom": "C1",
"right_copy": 1
},
{
"left_entity": "1",
"left_position": "213",
"left_atom": "ND2",
"left_copy": 1,
"right_entity": "2",
"right_position": "1",
"right_atom": "C1",
"right_copy": 2
}
],
"name": "7zav",
"model_seeds": [
101
]
}

Thanks for your clear answer!


Raise an exception if the block arity is nonzero and isn't same with capture parameter length

ref #1868
As @ujifgc said, I stopped adjusting captures at runtime.
Instead, an exception will be raised if the arity is wrong.
Please push commits into this branch if you have more friendly error message.

Thank you for great reviewing and fixing!


Workspace pod FailedScheduling event not being properly caught

Description
In some cases, a workspace deployment's pod will trigger the FailedScheduling event and DWO will not be able to properly catch it.
So far, this seems to occur when a workspace requests more memory or CPU than is available on any node on an OpenShift cluster.
What I have observed is that, although DWO sees the pod's FailedScheduling event, the event.count is set to 0. DWO then checks to see if the event.count is higher than the threshold required to report an error. Since the threshold is 1 (i.e. event.count must = 1 for an error to be reported), the error is never reported, and eventually, the workspace times out.
I have been trying to narrow down the exact cause of this bug, but have been unsuccessful thus far.
However, here are my current findings:

This issue seems to be consistently reproducible on OpenShift 4.11 and 4.12. On OpenShift 4.10, the FailedScheduling event is sometimes properly caught, and in other cases, the workspace times out.

When this bug occurs (on OpenShift 4.10, 4.11 & 4.12) the event.count is set to 0 and event.series is nil (so event.series.count is unusable)

This issue does not occur on Minikube v1.27.1 with Kubernetes v1.25.2

When testing, the event.count was set to 1 upon first encountering the FailedSchedulingevent, and the count increments with each occurrence of the event. The event.series is nil.

The event.count field has been deprecated in Kubernetes v1.25, and instead the event.series.count field is supposed to be used. However, in my testing on Minikube, the event.series field was still nil.

The new event API is k8s.io/api/events/v1 (and the deprecated one which is currently in use in DWO comes from k8s.io/api/core/v1)

I have tried using k8s.io/api/events/v1 but encountered the same behaviour as k8s.io/api/core/v1: on affected OpenShift versions, event.count is set to 0 and event.series is nil. There is also auto-generated code to convert back and forth between core v1 events and events v1 (here and here)

The default Kubernetes scheduler (which is also used by OpenShift, unless configured otherwise) seems to use the following event recorder implementation, which does not initialize the event count field (thus, we'd expect event.count to be initialized to 0, but oddly, this is not the case on Kubernetes v1.25).

The call stack seems to be: kube-scheduler executes runCommand -> Setup is called, which executes options.Config() -> The kube-scheduler's event broadcaster is initialized as an event broadcaster adapter. The event broadcaster adapter checks if the cluster supports k8s.io/api/events/v1 resources (i.e. the new events API), and if so, an events/v1 EventBroadcaster will be used (otherwise a core/v1 events EventBroadcaster is used). In my testing on OpenShift 4.11 and Minikube, k8s.io/api/events/v1 resources were supported, so the new event API should be in use by the EventBroadcaster.
Continuing the call stack: The kube-scheduler obtains an (event) recorderFactory from the k8s.io/api/events/v1 EventBroadcaster. This recorderFactory is used by the kubernetes scheduler struct: a map of scheduling profiles to frameworks allows the association of pods to the k8s.io/api/events/v1 event recorder when a pod is being scheduled. Finally, when the scheduler's failure handler is run, the FailedScheduling event is created using the k8s.io/api/events/v1 event recorder.

Other notes:

@ibuziuk reported that the FailedScheduling event was being caught correctly (on CRC 4.10.14 I believe) when it was caused by a disk pressure issue. I am not sure whether there is something particular about disk-pressure warnings that cause them to be caught, or if this is a case of the FailedScheduling event being sometimes caught on OpenShift 4.10
I haven't been able to find any Kubernetes or OpenShift bugs directly related to this issue. However, I did find this https://github.com/elastic/beats/issues/31126 which describes a similar issue with the event count being set to 0.

I considered using a similar approach to this PR, however this could still lead to breaking DWO's detection of the FailedMount event,  as we allow 3 FailedMount events to occur before reporting an error.
I'm not sure if it is easy to reproduce the FailedMount event for testing purposes, but if its event count is being correctly set and incremented, then the above approach could suffice.

We could add extra checks (after checking pod events) for the pod.status.conditions to see if the PodScheduled condition is set to False with the Unschedulable reason, and fail the workspace if this condition is found. However, this seems less fine-grained than checking pod events. Perhaps there's another way to determine if a pod will not be able to be scheduled, other than checking pod events and pod status conditions?

How To Reproduce
Apply either of the following devworkspaces to an OpenShift 4.11 or 4.12 cluster (on 4.10, this issue may or may not occur), and see that they will time out rather than fail immediately:
kind: DevWorkspace
apiVersion: workspace.devfile.io/v1alpha2
metadata:
  name: theia-next-high-cpu
spec:
  started: true
  template:
    projects:
      - name: web-nodejs-sample
        git:
          remotes:
            origin: "https://github.com/che-samples/web-nodejs-sample.git"
    components:
      - name: theia
        plugin:
          uri: https://che-plugin-registry-main.surge.sh/v3/plugins/eclipse/che-theia/next/devfile.yaml
          components:
            - name: theia-ide
              container:
                env:
                  - name: THEIA_HOST
                    value: <IP_ADDRESS>
                memoryRequest: 2Gi
                memoryLimit: 16Gi
                cpuRequest: 4000m
                cpuLimit: 8000m
    commands:
      - id: say-hello
        exec:
          component: theia-ide
          commandLine: echo "Hello from $(pwd)"
          workingDir: ${PROJECTS_ROOT}/project/app

kind: DevWorkspace
apiVersion: workspace.devfile.io/v1alpha2
metadata:
  name: theia-next-high-mem
spec:
  started: true
  template:
    projects:
      - name: web-nodejs-sample
        git:
          remotes:
            origin: "https://github.com/che-samples/web-nodejs-sample.git"
    components:
      - name: theia
        plugin:
          uri: https://che-plugin-registry-main.surge.sh/v3/plugins/eclipse/che-theia/next/devfile.yaml
          components:
            - name: theia-ide
              container:
                env:
                  - name: THEIA_HOST
                    value: <IP_ADDRESS>
                memoryRequest: 32Gi
                memoryLimit: 64Gi
                cpuRequest: 500m
                cpuLimit: 2000m
    commands:
      - id: say-hello
        exec:
          component: theia-ide
          commandLine: echo "Hello from $(pwd)"
          workingDir: ${PROJECTS_ROOT}/project/app

When checking the workspace pod with kubectl/oc or the OpenShift UI, you can see that the pod is pending and that an event similar to the following has occurred:
0/6 nodes are available: 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }, 6 Insufficient cpu. preemption: 0/6 nodes are available: 3 No preemption victims found for incoming pod, 3 Preemption is not helpful for scheduling.

Expected behaviour
The FailedScheduling event should be caught and reported, and the workspace should be failed immediately.
Additional context
Downstream issue

@AObuchow thank you for your investigation. I believe we need to report the issue to OpenShift BZ if the event count is not initialized / incremented correctly.
on the DWO end in order to mitigate the issue I would propose to have smth like UnrecoverablePodConditions and track Unschedulable in a similar fashion we track UnrecoverableEvents @l0rd @amisevsk wdyt?
status:
  phase: Pending
  conditions:
    - type: PodScheduled
      status: 'False'
      lastProbeTime: null
      lastTransitionTime: '2022-11-15T13:56:48Z'
      reason: Unschedulable
      message: >-
        0/15 nodes are available: 3 node(s) had taint
        {node-role.kubernetes.io/infra: }, that the pod didn't tolerate, 3
        node(s) had taint {node-role.kubernetes.io/master: }, that the pod
        didn't tolerate, 9 Insufficient memory.
  qosClass: Burstable

I don't recall why we didn't initially have an implementation that looks at pod conditions as well as deployment conditions, but this approach makes sense to me.

Looking at the pod condition looks like a great idea.
I also think that checking that event.count is higher than a threshold is not required. A FailedScheduling should be reported as early as possible to the developer by the dashboard (and eventually let the developer decide to wait / retry / cancel).

I also think that checking that event.count is higher than a threshold is not required. A FailedScheduling should be reported as early as possible to the developer by the dashboard (and eventually let the developer decide to wait / retry / cancel).

The reason we have the threshold mechanism is that we were seeing random workspace failures due to occasional FailedMount events -- see https://github.com/devfile/devworkspace-operator/issues/778. However, if count is never being incremented anymore, that functionality likely does not work anyways.
Another solution here might be to use thresholds of 0 instead of 1; that would amount to not checking the threshold at all.

The fix for this issue (https://github.com/devfile/devworkspace-operator/commit/0cad9a076dc13cacad5f681b79b8dbdb6aeb7c6d) is effectively obsolete from the fix for https://github.com/devfile/devworkspace-operator/issues/987. However, https://github.com/devfile/devworkspace-operator/commit/0cad9a076dc13cacad5f681b79b8dbdb6aeb7c6d has the downside that, the user will be unable to ignore the FailedScheduling event if they chose to do so (because the PodUnschedulable condition will still be caught).
Thus, I think it's worth reverting the work done in https://github.com/devfile/devworkspace-operator/commit/0cad9a076dc13cacad5f681b79b8dbdb6aeb7c6d as it has no added benefits, and has the disadvantage of preventing users from ignoring the FailedScheduling event.


OSS Documentation

OSS ticket here: https://github.com/NASA-IMPACT/active-maap-sprint/issues/746
So far:

created new directory under "System Reference Guide" for the Docs site for the OSS documentation
general oss doc
document on data sharing/doi minting/licensing

I'm sure these will need some more work and additions, but figured I'd push what I have so far for feedback

Overall this first version only covers Software/Code.
There's one paragraph about data and DAACs that's very incomplete. We can aim to put that in the next round of edits.
Core to Data is requirements of NASA funding, options for data storage (I think I made a list in the ticket), and what to do when a DAAC will not take your data.

Overall this first version only covers Software/Code.
There's one paragraph about data and DAACs that's very incomplete. We can aim to put that in the next round of edits. Core to Data is requirements of NASA funding, options for data storage (I think I made a list in the ticket), and what to do when a DAAC will not take your data.

Is next round of edits after we merge this first version? If so, I'll go ahead and remove the sentence about DAACs (unless the whole NASA-funded paragraph should be removed for now)

Thank you for your efforts @smk0033 ..This looks great. I have finished my review.

Removed sentence about DAAC submission until next edits


Visual preview of the apps

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
We could provide a mini-preview of what the apps are about.
Examples 🌈

Figma

Google Drive

Motivation 🔦
This could help quickly make an edit on the relevant page. I have faced this challenge many times. When I open https://master--toolpad.mui.com/_toolpad/apps, I always have to think twice about what's the name of the app that I'm looking for. A visual preview would help.
An alternative solution would be to:

have folders to organize work #1398
have "favorites", like Metabase or Notion

Context
See https://github.com/mui/mui-toolpad/discussions/1376#discussioncomment-4217245

@bytasv Let's do this later, as discussed here: https://github.com/mui/mui-toolpad/discussions/1376#discussioncomment-4280382
I am moving it back to Todo


File Locksmith documentation is missing

Provide a description of requested docs changes
The newly added File Locksmith utility has a 'Learn more about File Locksmith' link, which (ultimately) goes to https://learn.microsoft.com/en-gb/windows/powertoys/file-locksmith
That page is missing at the time of release of PowerToys v0.64.0

Dup for #21622 (sorry)


Question about train image size

Hello, @zhreshold ,I have used my own trainset  to train , my image size is (3,1280,200). I want to know which parameter works best, can you tell me some skills for tuning。Thank you very much.

You image is too wide, which won't work for ssd as it will resize to 300x300, then the image is distorted quite a bit.
I would cut the image into several parts and train use default parameters should be fine.

Thanks for your reply! It can detect character in the image without cutting the image, but if the character is too close, it will appear reapeat box. In my own dataset, if I cut the image,may be some character will be cut,it will affect the performance.So, do you have any other suggestions?Thank you very much . @zhreshold

I would try different aspect ratio other than 1:1 and train a new model for the specific usage

Thank you very much！ @zhreshold

Hi, @zhreshold I have met a problem , when I run demo.py for one hundred images, it takes 45ms in average,but when I run demo.py image by image ,it takes 180ms per image. Is there is a solution for this?

It is normal because each time it will load the network and parameters when you enter demo..py
Solution is to keep the detector, and call detect_and_visualize each time when you want to detect new images.

Yes,I have done like you says. Each time call detect_and_visualize, I have locate the problem, in detector.py, the code "detections = self.mod.predict(det_iter, reset=False).asnumpy()", I have found foward only take 10ms, but asnumpy() take around 100ms, I want to know the reason ,can you give me a  solution? @zhreshold

I think forward time is not accurate because the process is asynchrous until you call the asnumpy().
Launching executor takes time, so I think it's reasonable.

Thank you very much! @zhreshold
I have now used ssd for real-time detection, now I have met a few questions:
**1.**when I call im_detect image by image, then  python generate too many threads and continue increase, which cause slow speed, how can we solve this problem?
**2.**when I use vgg_ssd_512 network and 512 data-shape, detcection cost 150ms around image by image, and then I make predict parameter reset=False, it cost 100ms around , but I want more improvement, reduce more time for the real-time detection, is there any solutions?

I suppose there is somewhere speed up can happen, but you need to figure out the bottleneck


Code release date?

When will the code be released ?

Dear Hab2Verer,
I've been quite busy lately because I'm currently facing the deadline for submitting my paper. Once these few days pass and I have more free time, I will upload my code.
Best regards, Xiaoyi Han
At 2024-10-31 22:02:52, "Hab2Verer" @.***> wrote:
When will the code be released ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

@XiaoyiHan6
Good luck with your paper
I will be waiting for you.
Best
Hab

@XiaoyiHan6
Hello
I hope you have made progress with your paper.
Any news about the code release?
I really need it :)
Best of luck
Hab

Dear hab2verer,
I hope this message finds you well.
I wanted to inform you that I have not yet had the opportunity to organize the code for our recent project. However, I have posted the specific timeline for when I will be doing so on our website. If you are particularly interested in the progress of this project, please feel free to visit the link I've provided to stay updated.
Thank you very much for your interest and support in my project.
Best regards,
Xiaoyi Han
My Web: https://xiaoyihan6.github.io/FSD/
At 2024-11-18 17:08:06, "Hab2Verer" @.***> wrote:
@XiaoyiHan6
Hello
I hope you have made progress with your paper.
Any news about the code release?
I really need it :)
Best of luck
Hab
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


Dependabot Alerts (and other dashbards) from Github Cloud enterprise not showing results due to bad SPL

Describe the bug
Data for dependabot alerts gathered from Github Webhooks returns no results despite their being data in the index.
To Reproduce
Steps to reproduce the behavior:

Set-up a Github Webhook to push to Splunk via HEC as per the instructions
View Dependabot Alerts under the Advanced Security tab

Expected behavior
Data related to dependabot alerts should be shown, there is nothing shown.
Desktop (please complete the following information):

OS: OSX 12.4
Browser Brave
Version 1.39.122

Additional context
The issue is due to the fact that the events sent in the Webhook do not contain an "eventtype" field which is the first field the base search filters on hence it gets no results. It's not even documented on the official docs: https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#repository_vulnerability_alert
To fix it, for Github Cloud at least, I had to change base search to match on the valid actions values and that and action.id field is set as follows:
`github_webhooks` action IN ("create", "dismiss", "resolve") | where isnotnull("action.id") | | eval action='action',...

This seems to be a persistent problem with a lot of the other dashboards that the basesearch is looking for some qualifier that doesn't exist.

I believe the issue is as per the description in PR #39


Upgrading to Credhub 1.0.0

Upgrading to Credhub 1.0.0
https://github.com/pivotal-cf-experimental/kubo-deployment/issues/99
[#145644667]

Does it solve #94 ?

Yes this solves #94


Anyone had any luck with the new OpenAI package as a lambda layer

I haven't found anyone that has been able to do this yet.

@bennyhartnett try this: https://github.com/FullStackWithLawrence/aws-openai

I haven't found anyone that has been able to do this yet.

Hi,
I've created AWS Lambda Layer for the latest version of openai. You can find its .zip over the below-attached repo link. Also, I've shared steps to create a custom lambda layer for any of your desired openai and python version.
Repo Link: https://github.com/syedfaiqueali/aws-lambda-layer-openai
Thanks!


changes to collect metrics from Prometheus with benchmark run outside of kepler-model-server

Users might want to run a custom benchmark outside of kepler-model-server and collect metrics using kepler-model-server to train model subsequently.
Collect metrics (only query Prometheus to fetch metrics in the specified time window)
NATIVE="true" ./script.sh custom_collect

Validate the collected metrics
NATIVE="true" ./script.sh validate customBenchmark

Train custom benchmark metrics
NATIVE="true" ./script.sh custom_train

Note that Prometheus is queried to collect both kepler provided power consumption and node-exporter provided CPU utilization metrics (like node_cpu_seconds_total) for each cluster node.

Thank you for the PR. It is promising to extend the custom metrics for validation and train.
I think we don't need to create a new function for them. We can add an option for specifying start-time,end-time  directly in addition to interval. In stead of saving only query result (like idle.json), we have custom_benchmark.json and custom_query_response.json when start_time end_time are specified with startTimeUTC/startTimeUTC in json as you defined.
For the custom_metrics, is it the same as PROM_THIRDPARTY_METRICS introduced in https://github.com/sustainable-computing-io/kepler-model-server/pull/185?


Update pipeline log messages: remove verbose messages; add timing messages

I'm considering making updates to the pipeline to make it faster to process papers. To determine the effort required to speed up the pipeline, I'd like to collect more detailed timing information about key steps in the paper processing pipeline.
This PR adds log statements to the commands for locating entities that can be used to measure the time it takes to:

Insert color macros into the TeX
Compile the TeX
Raster the TeX to images
Difference the images
Locate entities in the image diffs

These steps will be performed up to thousands of times for a single paper, so strategic improvements to pipeline performance can be aided by knowing which one of these steps usually takes the longest.
Log statements are added both at the start and end of each of the steps above to make it possible for our log analysis scripts to measure the of that step as the difference in timestamps between the start and end log message.
I have also removed a couple of overly verbose log messages from the project which have never really served a purpose in helping me (or as far as I know, anyone else) debug.

Are you planning to run these locally or do you want the output on the S2 pipeline side as well? I'm mainly wondering if we should ignore DEBUG if this is going to be emitted 1k+ times per paper. Eventually that will add up in terms of $ on CloudWatch storage / retrieval.

Are you planning to run these locally or do you want the output on the S2 pipeline side as well? I'm mainly wondering if we should ignore DEBUG if this is going to be emitted 1k+ times per paper. Eventually that will add up in terms of $ on CloudWatch storage / retrieval.

Are you planning to run these locally or do you want the output on the S2 pipeline side as well? I'm mainly wondering if we should ignore DEBUG if this is going to be emitted 1k+ times per paper. Eventually that will add up in terms of $ on CloudWatch storage / retrieval.

 While I could envision wanting to run this on the S2 pipeline, I think I would only need to do it for a small subset of papers at a time when we're trying to debug or profile something specific. What this suggests to me is that perhaps we should ignore DEBUG by default, though provide the ability to enabled DEBUG through a configuration or command line parameter for the deployed pipeline. What would you think of that?

Are you planning to run these locally or do you want the output on the S2 pipeline side as well? I'm mainly wondering if we should ignore DEBUG if this is going to be emitted 1k+ times per paper. Eventually that will add up in terms of $ on CloudWatch storage / retrieval.

 While I could envision wanting to run this on the S2 pipeline, I think I would only need to do it for a small subset of papers at a time when we're trying to debug or profile something specific. What this suggests to me is that perhaps we should ignore DEBUG by default, though provide the ability to enabled DEBUG through a configuration or command line parameter for the deployed pipeline. What would you think of that?


使用第三方代网页授权时，若component_access_token过期或无效会自动刷新

Codecov Report

Merging #404 into master will decrease coverage by 0.18%.
The diff coverage is 31.57%.

@@            Coverage Diff             @@
##           master     #404      +/-   ##
==========================================
- Coverage   72.72%   72.54%   -0.19%
==========================================
  Files          74       74
  Lines        2673     2684      +11
==========================================
+ Hits         1944     1947       +3
- Misses        729      737       +8

Impacted Files
Coverage Δ

wechatpy/component.py
69.86% <31.57%> (-1.67%)
:arrow_down:

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 49252b6...7d8ae30. Read the comment docs.

Codecov Report

Merging #404 into master will decrease coverage by 0.18%.
The diff coverage is 31.57%.

@@            Coverage Diff             @@
##           master     #404      +/-   ##
==========================================
- Coverage   72.72%   72.54%   -0.19%
==========================================
  Files          74       74
  Lines        2673     2684      +11
==========================================
+ Hits         1944     1947       +3
- Misses        729      737       +8

Impacted Files
Coverage Δ

wechatpy/component.py
69.86% <31.57%> (-1.67%)
:arrow_down:

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 49252b6...7d8ae30. Read the comment docs.


Joystick enumeration is off..

Thanks for raising your issue here! 🙂
Before you submit the issue however, we'd like you to consider the follow points.

We like to use the issue tracker for confirmed issues.
If you're stuck with SFML, please use the forum to get help.

Subject of the issue
I'm using Attract Mode (https://github.com/mickelson/attract), which is build on the SFML framework...
Joystick enumeration seems to be off.. basically same issue that SDL has:
https://github.com/libsdl-org/SDL/issues/4688
Is there anyway to control this in SFML?

SDL and SFML have different implementation, it's rather tricky to compare the two

Can you provide more information on what "seems to be off" means exactly?
What do you expect, what are you actually getting?
How can things be reproduced?
What joysticks/gamepads are you using?
What OS have you tested this on?

Can you provide more information on what "seems to be off" means exactly?
Controllers are shifted.. js0 -> Player 4, js1 -> Player 1, js2 -> Player 2, js3 -> Player 3
What do you expect, what are you actually getting?
Same as above
How can things be reproduced?
Plug a multijoystick controller
What joysticks/gamepads are you using?
PC-Jamma (http://www.bartoxsystems.com/?page_id=48)
What OS have you tested this on?
GroovyArcade - Arch based..


Add .NET Standard 2.0 target

Targeting .NET Standard 2.0 is the recommended way of supporting multiple framework implementations.
Even though the guidelines say otherwise though, the other targets were left untouched for compatibility.
(why .NET Standard 2.0 too? so .NET Standard libs can reference it)

Closing because .NET Standard 2.0 was included in the latest commit.


Add python3-numba

Please add the following dependency to the rosdep database.
Package name:
Python3 numba package.
Package Upstream Source:
https://github.com/numba/numba
Purpose of using this:
Numba provides high-performance numerics by generating machine code from python syntax.
Distro packaging links:

Debian: https://packages.debian.org/

https://packages.debian.org/sid/python3-numba

Ubuntu: https://packages.ubuntu.com/

https://packages.ubuntu.com/focal/python3-numba

Thanks for you work @nuclearsandwich !


Remove unused faker from the dependencies

faker is not used in the code base.
$ npx depcheck
Unused dependencies
* faker

This unused dependency simply adds bloat.

Can any maintainer confirm this (just in case)? I would appreciate this getting attention due to faker not being maintained anymore, but still gaining a lot of traffic.

I've not looked at the code in a while but we use faker indirectly via json-schema-faker: https://github.com/apigee-127/sway/blob/e9ad6e81af41f526567e9d5a0f150e59e429e513/lib/helpers.js#L28 to allow for Parameter#getSample to generate an example for a Parameter's schema.  If faker is no longer maintained, either we need to find a replacement or we need to remove the ability to register custom format generators and likely sample generation.

I'm a team member from the faker-js/faker library which is considered the official fork from the old faker package. Other team members are already working on migrating the faker package in  json-schema-faker (see here).
So your lib really just needs to remove the faker package from your dependencies in the package.json file.


Use tab-based indenting in XHTML code sample

Format XHTML code, to match the tab-based indenting used in all other code samples in this repo.

They appear to be spaces, and there 3 for the first level and 5 for the second.

They appear to be spaces, and there 3 for the first level and 5 for the second.


Add pointer events

This exists to work around a conflict in the Flutter engine where
multiple Listeners at different levels in the widget hierarchy cannot
work together.
See https://github.com/flutter/flutter/issues/76525 et al

I was trying to hook up the ability to drag an item outside of the DragAndDropLists widget and still be able to scroll the outer scrollview around (in my case, the DragAndDropLists widget is embedded in a page that's doing a lot of other things as well, so the ability to scroll the entire page while dragging was critical). It would be nice to remove this after the Flutter team fixes the fundamental issue with multiple listeners not cooperating.


Sharing some love

This is by far second of the cleanest code I've ever encountered.

Thanks @ahmgeek

It's just based on two common design patterns:

Template Method - for implementation providers
Strategy Pattern - execution providers with different implementation

@kirillshevch thanks for sharing this, I also noticed using some dry-* libs which I admire, I really liked how the code looks.
Thanks again.


how can we keep a popover alive while the popover is being hovered?

I'm trying to trigger manually the popover using trigger="manual" with a hover event:
<template>

    <popover title="Title" trigger="manual" v-model="show">
    <template slot="popover">

Popover content

      </template>
    </popover>

    <btn type="primary" @mouseover="show=true" @mouseleave="show=false">Toggle Popover</btn>

</template>

Well, I understand why the popover is being closed due when I leave the button I set show to false.
So my question is: Where do I have to place that @mouseleave event in order to prevent closing the popover when it is being hovered?

you can add @mouseenter.native & @mouseleave.native to <popover>.

I've found an alternative for this:
<popover trigger="hover" title="Title">
    Toggle Popover
    <template slot="popover">

Popover content

     </template>
 </popover>

Basically, we can use trigger="hover" to prevent closing the popover when it is being hovered
You can check this here: https://plnkr.co/edit/RSjhazfxqBhaNqcKijXe?p=preview