[$1000] Pin/Unpin Offline - Chat returns to previous status when returning online after reload

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:
Pinned Offline

Navigate to a conversation that is not near the top on the LHN list
Disable the internet connection
Click/tap on the pin icon on the top right
Verify the conversation is now pinned to the top of LHN
Refresh the page or Refresh the page or force-kill and relaunch the app
Enable the internet connection and refresh the page in Web

Unpin Offline

Disable the internet connection
Unpin the conversation
Refresh the page or Refresh the page or force-kill and relaunch the app
Enable the internet connection and refresh the page in Web

Expected Result:
Pinned Offline - Conversation is still pinned to the top of LHN
Unpin Offline - Conversation is still unpinned and in it's original location in LHN
Actual Result:
Pinned Offline - Conversation returns to its previous status - Unpinned in it's original location
Unpin Offline - Conversation returns to its previous status - Pinned to the top of LHN
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[x] iOS / native (IPAD)
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.15-6
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43995119/3e7ac33f-fae8-4b0f-bf3b-2c47ddd897f5
https://github.com/Expensify/App/assets/43995119/4df3a72f-9be7-436e-98dd-570c2a270b10
Expensify/Expensify Issue URL:
Issue reported by: Applause Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~013d665287b7e170b5
Upwork Job ID:<PHONE_NUMBER>409548800
Last Price Increase: 2023-05-26

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

Not a blocker: https://expensify.slack.com/archives/C07J32337/p1684368975366959

@mvtglobally Can we retest this one? I am not seeing this issue at all on the first two platforms I tried...
Are the test steps correct or could anything be more specific?

@marcaaron The issue is quite inconsistent. repro on Mac/Chrome/Safari
I will ask to re-test

@slafortune I'm going OOO this week. Could you please do me a favor and sometime tomorrow:

Unassign me from this issue
Re-add the Engineering label so a new assignee is picked
Assign me again
If we don't figure it out by the time I get back I'll unassign whoever got assigned

Thanks!

@marcaaron The issue is quite inconsistent. repro on Mac/Chrome/Safari I will ask to re-test

Were you able to reproduce this again? I'm not seeing it either

I'm gonna close this until we have a more reliable reproduction. Doesn't seem like anyone else has reported this and it's been a couple of weeks now.

Issue is reproduced on build <IP_ADDRESS>
https://github.com/Expensify/App/assets/93399543/767e3c48-05dd-4e0c-9a02-4765caf97161

@kbecciv @aimane-chnaif is it consistently reproducible or not?

I can't reproduce this (running in the main branch)

Closing again. Unless we have a reliable reproduction I don't think this is worth prioritizing.


deactivate jdk8 in plugin test cases

Fix #360
Proposed changelog entries

Remove jdk8 support for plugin tests in Jenkinsfile

Hi @mPokornyETM , for this issue, should there be any other code or config changes other than updating the Jenkinsfile and the pom.xml?
Because the CI still shows the java 8 step in the tests stage.

Because changes to the Jenkinsfile may involve privileged operations on the repository, they are only evaluated on ci.jenkins.io when the submitter of the pull request has write permission to the repository.  You're seeing Java 8 continue to be evaluated because the Jenkinsfile change is being ignored.  That prevents malicious actors from submitting pull requests that subvert the Jenkinsfile to do things that it should not do.

Because changes to the Jenkinsfile may involve privileged operations on the repository, they are only evaluated on ci.jenkins.io when the submitter of the pull request has write permission to the repository. You're seeing Java 8 continue to be evaluated because the Jenkinsfile change is being ignored. That prevents malicious actors from submitting pull requests that subvert the Jenkinsfile to do things that it should not do.

Interesting. And what we can do to deactivate Java8 Support?

Interesting. And what we can do to deactivate Java8 Support?

Merge this pull request as is and watch the CI job on the master branch, or have a maintainer submit a new pull request that includes at least the Jenkinsfile change from this pull request.

Great, in that case @niranjanib  pls update contributing too. Us there Java 11 instead of 8.
https://github.com/jenkinsci/lockable-resources-plugin/blob/master/CONTRIBUTING.md

Because changes to the Jenkinsfile may involve privileged operations on the repository, they are only evaluated on ci.jenkins.io when the submitter of the pull request has write permission to the repository.  You're seeing Java 8 continue to be evaluated because the Jenkinsfile change is being ignored.  That prevents malicious actors from submitting pull requests that subvert the Jenkinsfile to do things that it should not do.

That makes sense, thank you for elaborating @MarkEWaite


DE25540 - Always show filter menu; allow for new HM API routes

Two main things being accomplished here:

Always show the filter menu for all users, and display an empty-state message for those that don't have anything relevant to show.
Use both old and new HM API routes - see https://git.dev.d2l/projects/CORE/repos/lp/pull-requests/5307/overview

Acceptance Criteria:

Filter menu shows for all users, regardless of number of enrollments, or number of department/semester enrollments
Filter menu shows empty state message for users without any department/semester enrollments
Works with both master as well as the changes implemented in https://git.dev.d2l/projects/CORE/repos/lp/pull-requests/5307/overview (note that the returned results will differ slightly; this is intentional)

Side note: I've thought over unit tests, didn't come up with any good ones - mostly I'm removing functionality here (the somewhat-complex filter menu hiding system), so not much complexity got added.


docs(examples): edit README for multiple examples

Query Suggestions with recent searches
Query Suggestions with recent searches and categories
React InstantSearch
Recently viewed items
Voice search

Should be the last one and I stop bother you :)

@clemfromspace Should we merge this?


Add ability to call molecule as a python module

Fixes: #1522

Thanks for the PR. Wonder if/where this should be in the docs as well?

Sorry, GitHub decided by itself to close this PR so I ended up creating a new one after switching to a feature branch. Lets do it at https://github.com/ansible/molecule/pull/1545 -- i fixed the comments.

Oh, you @ssbarnea probably force pushed the PR-bound branch in your fork, which was master to match upstream, which rendered a diff with zero changes. It's probably the reason GH closed it. FTR.


HugginFace API Google Colab not working.

While I am trying to LogIn a website, it gives the following issues:

The page is not being updated after Clicking on Button( specifically Continue button for login).
After clicking on the LogIn button it gives the error as shown in the screenshot.

Please suggest what is going wrong here.

@11PRiyansh  Can you share some debug logs or the full code here so that we can investigate and help.

Thanks for the reply, but I managed to solve it. However, the page doesn't load after an action( for example: click on the log in button).
It does click on the button but the page doesn't load/change to the next page(profile).
Solution:
I have to explicitly command "wait for 1 sec" for it to load/go to the next page. Is this behavior expected?

Are you saying that the screenshot is not updating after the click? So how do you got to know that it is clicked ?
Also can you check for error or any logs ??
Can you also share which LLM you are using ??

Yes, that is what I mean.
I know because of the color of the Button before and after the click changes. (Gets darker as it usually gets after a click).
There aren't any errors as it successfully executes the command.
I am using the default LLM mentioned in Huggingface.py file: "NousResearch/Nous-Hermes-2-Mixtral-8x7B-DPO"

Hmm it might be because the model did not understand the request.
Can you try using GPT-3.5 or GPT4?

The request is being understood and executed, as when I command "wait for 1 second" it loads the next page correctly.

Hi @11PRiyansh,
Unfortunately LaVague is still very much a project in progress and not a finished project, so some instructions on certain websites will not work currently, especially when it comes to logging in. We will add a page to the docs on how to increase chances of success through prompt engineering - sometimes manually adding a delay can be a solution as you say.
We are currently focusing all our efforts on improving AI performance and speaking with the community on how to improve results, so expect results to improve over time!
If you see any other improvements or have any specific suggestions or tips, please let us know! I'll close this in the meantime.


Inconsistent Gateway Listener Processing

gateway.spec.listeners[].port is processed by the infra and xds IRs. The infra IR uses this port as the port number of the Kube Envoy service. The xds IR uses this port to create the Envoy listener. For the Kube provider, the Envoy listeners should be created from the container ports, e.g. 8080 and 8443, of the Envoy deployment instead of gateway.spec.listeners[].port.

cc: @arkodg

Good catch, this is a big gotcha with listener.port, that it should be the port that the listener is available on from the outside.

this is being tracked via https://github.com/envoyproxy/gateway/issues/192

@arkodg i feel there is a subtle difference between this issue and the one you linked. This issue is a bug in the current state of how the translators process gateway ports. The linked bug is how to handle arbitrary ports. This issue must be resolved for RC1 while the linked issue can be resolved post v0.2.0.


Shared Session/Session Conflict issue

Environment

mod_auth_openidc version <IP_ADDRESS> and 2.3.1 so it should exist for all
Apache version 2.4.10
platform/distro Oracle Linux 6

Expected behaviour
During High load openin module should generate different session ID for different request and maintain correct headers in SHM Cache.
Actual behaviour
On very high load where login is like 400+ user login/second session id generated for two different users are same. If we run load test for many (5-10) hours I can see 1-2 occurrence of this happening.
Minimized example
During debug logs for two different request same session id was generated.

User1 [Fri Mar 01 15:20:01 2019] [debug] [pid 83207] src/cache/common.c(628): [client IP:44020] oidc_cache_set: enter: 64746bf8-3c5f-11e9-a559-5f2a1f420858 (section=s, len=1697, encrypt=0, ttl(s)=1199, type=shm)

-User2  [Fri Mar 01 15:20:01 2019] [debug] [pid 83207] src/cache/common.c(628): [client IP:40775] oidc_cache_set: enter: 64746bf8-3c5f-11e9-a559-5f2a1f420858 (section=s, len=1697, encrypt=0, ttl(s)=1199, type=shm)
Configuration and Apache server log files
Let me know what config's are necessary.
I tried downloading code and analyzed how the mod_auth_oidc_session cookie is being created. I saw the session id is nothing but the value of apr_uuid_get function from apache util. As per the uuid implementation it can have conflicts in a very close time stamp, which is what my guess is. Is there any other way this session cookie be created so that it makes sure there for any reason it has no conflict.
Thanks

interesting, I would not expect such relatively low numbers to collide; I'm not sure what to make of this:
apr_uuid_get uses a system provided underlying random generator, e.g. on LInux it uses /dev/urandom; it may be that your random generator does not have enough entropy; are you perhaps running in a VM or container?

Thanks Zanbelt for your thought on it.
To answer your question, yes we are on VM and the point is in the cloud world, I think most of us using openid might be using VM's.
Now my point is if this algorithm can even have 1 conflict, to have such an algorithm is not safe to use as session value. Since there can be many sensitive products trying to use this module and even 1 such conflict can give nightmares. Any such session sharing switches user identity to someone else and take whole system as that.
Is there any option we can update this module to have some configurable parameter so that session include something more than just random generated string,  like sub and re encrypt with some algorithm to become a session value.
Let me know your thoughts or if you have seen in past any way to make sure UUID generation is really unique at least within some hour's.
Thanks

you're asking the impossible: your system does not have a more random generator than /dev/urandom and ultimately mod_auth_openidc runs on your system...

Hans, appreciate your quick response.
Yes, I am looking into what can be done from system level.
But is it a wise choice to use just a random key generator which can have conflicts to use as session identifier for a web security module!!!
I believe, it must have some kind of additional mechanism to make sure it doesn't have conflicts.

please suggest a mechanism to create more randomness than /dev/urandom can do on the same system... (and we'll both be millionaires)

I definitely want to be millionaire, just currently my focus is not there though!!!
I understand we can't get more randomness in system but with current solution we have chances of conflict as documented by UUID algorithms.
As suggested earlier in my opinion this is what we can do:
Get the same random_string and append or prepend it with userid/sub and encrypt with some SHA algorithm. Field to prepend/append can be some of config so if different open ID systems give username in different fields it can be controlled.
Pros of doing same:
1.This way for two users even if we have got same UUID they will differ from each other and will be unique session id. Even if same user is trying to get 2 session for same application within those nano seconds he will still see same application and no authenticity of application get's screwed with it.
2. We still have something used as session which can't be easily mimicked as it is more than 128 bits.
Cons:
We are attaching some identifiable information in session cookie if someone know how to decrypt it might see whose session is it!! But does it matter as if someone has session cookie of someone they must be able to replay some request on server with that cookie that can give this information anyhow.
Session cookie might be some bytes long, but for the matter of security I am sure no one in world will mind that!!!.
Let me know your thoughts.

Really the problem is in your system or in your measurements.
You should fix the system entropy otherwise you'll be in trouble with other random values such as nonce's, state values, jti etc.; the 64 bit uuid is good enough in itself.
The con you mention is definitely a no-go.

Hans Cons which is wrote is choice of implementer to see what security is important for.
Shared session even if it is one user is not worth taking risk!!!
Instead of taking it as positive feedback to improve module, you are just putting it on server.
How do you know only my one server is bad where as I have myself replicated on 3 different servers with different CPU/RAM and just same OS flavor and still this issue stands true.
Will hope that someday, you feel this as useful thread and you reopen this case back and get a solution.
Thanks

I do want to thank you for your contribution, this is useful indeed and I guess I should be more verbose about why I'm closing this:
Firstly I don't think you fully grasp what random number generation means, please have a look at something like Coursera's Cryptography I or similar.
Secondly, your suggestion would push the problem down a little bit as clashes between user id's and sub values across different providers may easily occur.
Thirdy, on a true random system this error would occur 1 out of 2^64 times. In your case it happens after 400 * 3600 * 10 times on average which is about<PHONE_NUMBER>007 times faster than expected... So you must agree with me that either

apr_uuid_get is terribly broken in itself
your systems's /dev/urandom is not generating enough entropy (since that's being used underneath)
your measurements are off

I hope you see why I don't see a problem with this module.  Also: as you point out this module is in use by many many enterprise users and they've done much more extensive experiments that what you've done so far, all with good results.
I actually expect 3 over 2.. If you still expect 1. you can take this discussion to the libapr project but all projects using apr_uuid_get would horribly be broken if this were true.

Hans, thanks for your insight.
I am very stubborn student and when it comes to learning/solving issue I do my best to do it.
Short story is, yes this is happening. I am part of enterprise where I am getting this issue so that means one of enterprise is seeing this.
Measurements would have been wrong if this has happened once and I am assuming it, so it is not.
I have logs from apache where two different request from front end while creating session have got same key.
Now I am taking few action items for me:

Why we are seeing this noise on only our servers (so far I have got on three different servers which are sized at 8x24 or 6x32) and why entropy is less for our flavor of linux/system?
How other products use this random value, do they use it as is or it become salt for some algorithm with some more mix which is what I was asking.
What UUID algorithm apr_uuid_get uses as there are many way's these things can be generated and few have more conflicts than others. ref: https://en.wikipedia.org/wiki/Universally_unique_identifier Section Collision is something which is interesting

I understand for you this issue is invalid, but I will definitely come back with more evidences and reasons. It might be our apache setup or something is wrong with our server and it might be learning for others to know if they ever see it.
Thanks again and I really appreciate your insights.

Hi Hans
I know it has been over a month with any update from me on this case.
Here is what I have found so far based on limited time and availability.
I looked at code for apr module and found there is routine behind apr_uuid_get, where it tries to get entroy from system using apr_os_uuid_get or using some custom routine which is timestamp based. At this time I think it is somehow not even using system entropy rather an fallback apache function.
Our web team used to install every thing from source, so we thought of installing one Apache/oidc using source and one server we installed using RPM and binary which I think most of world might be doing.
We ran same test using these two servers and we found that Apache/OIDC install  from source is having similar issue where as apache installed using binary didn't had this issue.
Next step, we did is comparing libraries for each executable using ldd command and found that one library which is not included while compiling oidc/apache module from source is lib_uuid and currently our web team is trying to find any documentation to link this while compiling and run more test.
Hans, do you have any special compilation parameters or configuration which you use so that rpm have linkage to /lib64/libuuid.so?
I will keep you posted with what exact issue we found with installation as this might help other's understand that there can be issue like that.
Just a thought!! can there be warning while installing OIDC module if system finds that it has no libuuid module linked while using in Apache etc?

just to close the loop on this: it is caused by custom built  libapr libraries that are not compiled against libuuid; I don't think mod_auth_openidc should cater for all custom built library versions, but to avoid this specific (simple) case l I'll change the code to no longer rely on apr_uuid_get but use apr_generate_random_bytes instead


boards: support for ST Nucleo L452RE-P

This is my first PR so please be kind :)
I wanted to add support for a new development board, the ST Nucleo L452RE-P. There's already support for the L452RE (note the missing P), so I've pretty much copied everything and modified the things that differed:

The User LED is in PB13
The MCU supports SMPS. It's not being used by Zephyr at the moment, but I made sure to add a note in the docs highlighting this difference.

In the process of adding this new board I've detected some minor errors in the L452RE documentation which I've fixed.
Finally, according to the user manual, the Zephyr console should be connected to LPUART1 instead of UART2. The pins are the same and I've made sure it works, however I haven't modify this neither in the mux nor in the DT because the corresponding alternate function is not defined in pinmux_stm32l4x.h.

Thanks for the feedback, I like the idea of putting the two boards inside the same folder. I'll get to it ASAP.

Please @ABOSTM check if the DTs are okay now (good idea btw).

See here for explanation how to fix the failing Compliance check (change summary message body missing).

I've just pushed the fixes, however before closing the PR I ran a test and I'm getting the following error:
➜ west build -b nucleo_l452re_p -- -G'Unix Makefiles'
-- west build: generating a build system
Including boilerplate (Zephyr base): /home/xxxxxx/zephyr/cmake/app/boilerplate.cmake
-- Application: /home/xxxxxx/app
-- Zephyr version: 2.3.99 (/home/xxxxxx/zephyr)
-- Found Python3: /usr/bin/python3.8 (found suitable exact version "3.8.3") found components: Interpreter
-- Board: nucleo_l452re_p
-- Found toolchain: zephyr (/home/xxxxxx/zephyr-0.11.2)
-- Found west: /home/xxxxxx/.local/bin/west (found suitable version "0.7.2", minimum required is "0.7.1")
-- Found dtc: /home/xxxxxx/zephyr-0.11.2/sysroots/x86_64-pokysdk-linux/usr/bin/dtc (found suitable version "1.5.0", minimum required is "1.4.6")
-- Found BOARD.dts: /home/xxxxxx/zephyr/boards/arm/nucleo_l452re/nucleo_l452re_p.dts
Error: nucleo_l452re_p.dts.pre.tmp:510.1-9 syntax error
FATAL ERROR: Unable to parse input tree
CMake Error at /home/xxxxxx/zephyr/cmake/dts.cmake:202 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  /home/xxxxxx/zephyr/cmake/app/boilerplate.cmake:510 (include)
  /home/xxxxxx/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  /home/xxxxxx/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate)
  CMakeLists.txt:4 (find_package)

-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: /usr/bin/cmake -DWEST_PYTHON=/usr/bin/python3 -B/home/xxxxxx/app/build -S/home/xxxxxx/app -GNinja -DBOARD=nucleo_l452re_p '-GUnix Makefiles'

Any clues of what's going on?

Error: nucleo_l452re_p.dts.pre.tmp:510.1-9 syntax error

Above line gives you a hint where to look for more details. The file is located under zephhyr/build and something in line 510 is wrong.

Alright, it turns out I had to remove #include <st/l4/stm32l452Xe.dtsi> from the dts because it's already in the common DT. Thanks for your help!
If the CI passes, the PR should be over unless you want me to modify the image.

Thanks for this first PR @crespum!
Thanks @ABOSTM and @martinjaeger for the reviews.


Face Network error pop-up on new issue on Codeberg

Description

https://codeberg.org/Benjamin_Loison/firefox/issues/new
Removing the issue content removes the network error (as I tried opening a new tab and fill exactly the same title and content and it did not work but after removing the content it worked) and can fill it afterwards without any issue (I verified with Ctrl + Shift + R). I also verified that submitting again title and content still raise the issue while if remove content it does not raise it anymore.
Note that do not have an issue with the attachment despite the error.
Note that this workaround adds an unwanted entry to the issue body history.
Gitea Version
Not read.
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Not read.
Database
None

Now face:

Do not confuse with Benjamin-Loison/PrismLauncher/issues/2.


Galleries with more than 25 photos have a buggy behaviour

Our PWA is breaking galleries in groups of 25 photos, but the galleries are not connected between them.
You should be able to navigate from photo 25 to photo 26 as orignally they all belong to the same gallery.

@orballo example url: https://www.diariomotor.com/competicion/noticia/los-mejores-momentos-de-las-6-horas-de-spa-francorchamps-en-mas-de-100-fotos-y-tres-videos


FBO Handler, Multiple Mapping of FBO's cause hang in TCMU ring

With the FBO handler up for review, if there are multiple FBO's mapped then it spams the below message. If there is just one mapping then it will print the message once and complete and not print it out anymore. Also to clarify... the multiple FBO mappings do not all have to go to a single adapter. It can be to different adapters under a fabric, it will still spam as long as there are more than one FBO's mapped.
[  412.403771] ABORT_TASK: Sending TMR_TASK_DOES_NOT_EXIST for ref_tag: 192
[  413.258837] 0 completions handled from timeout
[  445.256997] 0 completions handled from timeout
[  478.278934] 0 completions handled from timeout
[  511.300729] 0 completions handled from timeout
[  544.324653] 0 completions handled from timeout
[  577.221766] 0 completions handled from timeout
[  610.246212] 0 completions handled from timeout
[  643.270132] 0 completions handled from timeout
[  662.995546] kmemleak: 3 new suspected memory leaks (see
/sys/kernel/debug/kmemleak)
[  676.293653] 0 completions handled from timeout
[  709.316839] 0 completions handled from timeout
[  742.275807] 0 completions handled from timeout
[  774.387752] ABORT_TASK: Sending TMR_TASK_DOES_NOT_EXIST for ref_tag: 192
[  775.234585] 0 completions handled from timeout
[  807.233261] 0 completions handled from timeout

As an update... I have commented out all the async code within the FBO handler and the issue is still there. So it does not have anything to do with how it is multithreaded.

So in regards to the email i sent you about the backport question...
I realized that I was running my own kernel without all the necessary backports before taking some of your target_user_core patches... so running on Yakkety, I experienced something different...
It no longer spams indefinitely but instead does:
[  408.534896] 0 completions handled from timeout
[  408.534933] ABORT_TASK: Sending TMR_FUNCTION_COMPLETE for ref_tag:<PHONE_NUMBER>6256462952
[  433.110715] 0 completions handled from timeout
[  441.508710] ABORT_TASK: Found referenced ibmvscsis task_tag:<PHONE_NUMBER>6256464840
[  443.350643] 0 completions handled from timeout
[  443.350675] ABORT_TASK: Sending TMR_FUNCTION_COMPLETE for ref_tag:<PHONE_NUMBER>6256464840
465.878471] 0 completions handled from timeout
[  465.878518] ABORT_TASK: Sending TMR_FUNCTION_COMPLETE for ref_tag:<PHONE_NUMBER>6256465312
[  470.940765] ibmvscsis: connection lost with outstanding work
[  476.118398] 0 completions handled from timeout
[  476.118531] ibmvscsis 3000000e: build_response: error copying to client, rc -11, flags 0x5c4, state 0x40
[  500.694172] 0 completions handled from timeout
[  500.694210] ibmvscsis 3000000e: build_response: error copying to client, rc -11, flags 0x5c4, state 0x40
So the interesting thing is it closes the connection with fabric

I take the previous comment, back... when i rebooted and tried it again, it just spammed indefinitely.

Closing the issue, its a ibmvscsi target kernel bug.


New Project Idea : Human Emotion detection

Hey, so i am a little new to the project and was not exactly sure if the addition that i wished to make went hand in hand with the overall goal of this project but a few days earlier i was working on a project which required me to detect human emotions. The model was built using the Kaggle notebooks and the data set that i used was FER2013 competition data. So it would be great if you could let me know if i can work on making that a part of this project.
If you would like any more information from my end, please let me know.  Let me know.

@AM1CODES, Do you want to complete this? Let me know.

What should I make the PR or wait ??

@AM1CODES, Do you want to complete this? Let me know.

@Rishikeshrajrxl Yea i would like to work on it. I had created the issue as i wanted to work on it.

@AM1CODES, @sudipg4112001, You both will be doing this issue individually. and after submission, both will get the points

Okay.

@AM1CODES, @sudipg4112001, You both will be doing this issue individually. and after submission, both will get the points

Okay..

@Rishikeshrajrxl I haven't made the PR yet, so will there be an problem? because this issue has been closed and you allowed both of us to PR for this issue.


Inference channels in "testConfig.cfg"

Hi Konstantinos,
Thank you for posting such a nice work here. Really amazed by the power of your architecture.
I found an interesting point when I perform the testing on the brats datasets and my own datasets. Just for illustration purpose, I am using testConfig.cfg file as configuration for testing on the brats datasets. Inside this file, there is one place to define how many channels are being used for inputs as shown below.
channels = ["./testChannels_flair.cfg", "./testChannels_t1c.cfg"]
I found that the trained model will provide different segmentation masks if I switch the order of the channels list files like what is shown below.
channels = [ "./testChannels_t1c.cfg","./testChannels_flair.cfg"]
Supposedly, if the model reads the whole two lists from the channels, the inferred mask shouldn't make any differences if switching the order of channels lists. However, it seems to me that the model only reads the first channel while making the inference.  Another hint indicating that the model only reads the first channel is that by looking at the log information, it prints that only 1st channel has been loaded.
Segmenting subject with index #1 ~~~~~~~~~~~~~~~~~~~~
Loading subject with 1st channel at:
In addition, the number of input channel is defined correctly in the modelConfig.cfg.
numberOfInputChannels = 2
Could you please take a look if my understanding is correct or not, and if so, how to solve this issue and which part of code needs to be revised? Thank you very much for your time!
Best regards,
Alice

Hello Alice,
When a net takes multi-channel input, it takes them in a particular order. E.g. if at training you provide T1/T2, in the input layer it will learn a set of filters for T1, and another for T2. If at testing you switch the order you provide them, T2/T1, the network is still the same, and thus it applies the filters it previously learnt for T1 on the T2, and the ones learnt for T2 to T1. So it is absolutely expected that its behaviour changes (and breaks down). So, no. The same order that you use for training you should be 100% certain you give the same order at testing.
The fact that you see in the logs only info about loading 1 modality per patient, is because I wanted to indicate which case is being loaded, but not fill the logs with multiple lines per patient, so not report in the logs the loading of each single modality per case, just the 1st one.
If you want a proof for yourself, train one in T1/T2, test with T1/T2, and then in another experiment corrupt yourself the T2 (eg apply noise). You ll see that the model breaks, indicating that it uses all images.
Behaviour is as expected. Will close issue.

Hi Konstantinos,
Thank you for your explanation which really helped me to understand the structure better.


The problem was solved.

Great!


github workflows: install protobuf compiler

prost 0.11 no longer bundles protoc, so explicit
installation is required
Signed-off-by: Eliad Peller<EMAIL_ADDRESS>

Addressed in https://github.com/kflansburg/k8s-cri/commit/5c0d25d83f5923ed20e2a020979d7b8e649d2e62


create new CostSurface and CostSurfacePuData entities in dbs [MRXN23-93]

Creates CostSurface and CostSurfacePuData entities in dbs
NOTE: WIP, lots of refactor pending (including proper naming), mostly related to level up all-things-cost-surface to its own module, update tests etc.
superseeds #1435
Overview
Adds a new table in each DB via 2 new migrations, along with it's entity representation.
Testing instructions
Check that once you run the app, those new tables are created, and the required constraints are in place
Feature relevant tickets
MRXN23-93
Checklist before submitting

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

Hey @hotzevzl thanks for the review, overall:|

Yes, there are changes made that are missing in this stage of the PR
All the naming is tmp until we bring everything to top level, which was decided to do in this PR after sync-ing with @KevSanchez
There are domain-related suggested changes that I don't fully understand so:

Let's sync about it


feat(control): add autonomous emergency braking module (backport #2793)

Description

backport: https://github.com/autowarefoundation/autoware.universe/pull/2793
replace motion_utils to tier4_autoware_utils because it does not exist
add boost_polygon_utils

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Codecov Report

:exclamation: No coverage uploaded for pull request base (beta/v0.3.15@8d49017). Click here to learn what that means.
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@               Coverage Diff               @@
##             beta/v0.3.15     #330   +/-   ##
===============================================
  Coverage                ?   10.00%
===============================================
  Files                   ?      501
  Lines                   ?    40475
  Branches                ?     8293
===============================================
  Hits                    ?     4049
  Misses                  ?    32911
  Partials                ?     3515

Flag
Coverage Δ

differential
10.00% <0.00%> (?)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


mysensors scene controller not appearing

Just upgraded to 0.10.1.
My mysensors scene controller which previously worked and appeared in the top of HA does not appear any more. It doesn't give an error or anything in the logfiles. It just doesn't work anymore.

The only thing that has changed since last time is a bug fix about the
location of the persistence file path:
https://github.com/balloob/home-assistant/commit/452348a7f9c449543623da9e6724da60a46b6882
On Mon, Dec 28, 2015 at 12:20 PM, sander76<EMAIL_ADDRESS>wrote:

Just upgraded to 0101
My mysensors scene controller which previously worked and appeared in the
top of HA does not appear any more It doesn't give an error or anything in
the logfiles It just doesn't work anymore
—
Reply to this email directly or view it on GitHub
https://github.com/balloob/home-assistant/issues/812.

--
PaulusSchoutsen.nl
It's nice to be important but it's more important to be nice.

Solved. I had to resend the presentation message which makes sense but I am pretty sure I didn't have to do this with previous upgrades.


Exclude private fields (preceded with _) from typedocs [0.15 XMR]

This issue requests generating typedocs without private fields, which are preceded by _.

Resolved with #146


Fix PWA on Android

Chrome doesn't want to play nice and it shows a banner at the top, signaling that we're not getting a Trusted Web Activity when launching the app.

Should be fixed with 07b661a.


GHA badge needs branch argument

Otherwise it just shows the status of the latest CI build, whether or not it was merged. I hardcoded main here but maybe there's a template?

Hm, GitHub seems to suggest that the default URL actually points to the default branch.

yep, check out https://github.com/beacon-biosignals/KeywordSearch.jl (I just put it in a failing state by closing and reopening a failing PR without merging it)

Ah wait, the default branch has not had any commits run on it, due to a misconfiguration on my end. That's probably the issue.

If it turns out to still need the branch attached, I'll add it to #243 which I'm trying to get merged soon. and has a {{{BRANCH}}} template


[omniorb] omniidl does not work  due to missing python files

Describe the bug
omniidl fails to run because it cannot access required python files
Environment

OS: Windows (but probably it will fail in all OS)
Compiler: MSVC 19.39.33523

To Reproduce
Use omniidl
Failure logs
omniidl: ERROR!

omniidl: Could not open Python files for IDL compiler
omniidl: Please put them in directory F:\vcpkg\installed\x64-windows\tools\omniorb\bin
omniidl: (or set the PYTHONPATH environment variable)

omniidl: (The error was 'No module named 'omniidl'')

ninja: build stopped: subcommand failed.

Solution
This lines are required in portfile.cmake
file(COPY
      "${CURRENT_BUILDTREES_DIR}/${TARGET_TRIPLET}-rel/lib/python/omniidl"
    DESTINATION
      "${CURRENT_PACKAGES_DIR}/tools/${PORT}/bin"
    )

file(COPY
    "${CURRENT_BUILDTREES_DIR}/${TARGET_TRIPLET}-rel/lib/python/omniidl_be"
  DESTINATION
    "${CURRENT_PACKAGES_DIR}/tools/${PORT}/bin"
  )

Probably needs the changes from https://github.com/microsoft/vcpkg/pull/36270


fix for hdr post processes

Fixes #2111
I confirm I have signed the Contributor License Agreement.

similar discussion, but perhaps not completely relevant to this:
https://github.com/playcanvas/engine/pull/2504
But to be safe, can you please test your solution with both alpha on and off, and possibly even antialising on and off. This is the easiest to test from the Editor by changing graphics settings and reloading project.

@mvaligursky - I modified an engine example and post process script locally to repro the bug and test the fix - I also tested using the project linked from #2111 running with a locally built engine with this fix in - and I also just flipped on "Transparent Canvas" option and tested again and no errors pop up with this fix.


Add a custom baseline config tool

Users should be able to create a custom baseline configuration which can be used to compare test results against a specific baseline to verify performance. This provides an easy PASS/FAIL system indicating whether a cluster has been properly configured or not. Additionally, a configurable tolerance should added to accept values within an acceptable range.
Closes #8
Signed-Off-By: Robert Clark<EMAIL_ADDRESS>

Example of default behavior when a result doesn't meet performance criteria using a custom config:
$ bobber parse-results --custom-baseline docs/sample_baseline.yaml dgx_station_results/

...

================================================================================
Baseline assessment
Comparing against a custom config
================================================================================
 1 System(s)
--------------------------------------------------------------------------------
  FIO Bandwidth Read (GB/s)
    Expected: 1.2, Got: 1.595, Result: PASS
  FIO Bandwidth Write (GB/s)
    Expected: 1.0, Got: 1.232, Result: PASS
--------------------------------------------------------------------------------
  FIO IOPS Read (k IOPS)
    Expected: 100.0, Got: 136.5, Result: PASS
  FIO IOPS Write (k IOPS)
    Expected: 100.0, Got: 135.0, Result: PASS
--------------------------------------------------------------------------------
  NCCL Max Bus Bandwidth (GB/s)
    Expected: 230, Got: 79.86500000000001, Result: FAIL
--------------------------------------------------------------------------------
  DALI 800x600 standard jpg (images/second)
    Expected: 2000, Got: 2694.595, Result: PASS
  DALI 3840x2160 standard jpg (images/second)
    Expected: 300, Got: 430.854, Result: PASS
  DALI 800x600 tfrecord (images/second)
    Expected: 2000, Got: 2665.653, Result: PASS
  DALI 3840x2160 tfrecord (images/second)
    Expected: 300, Got: 376.862, Result: PASS
--------------------------------------------------------------------------------
1 tests did not meet the suggested criteria!
See results above for failed tests and verify setup.

Example of using a heavy tolerance to allow all results to PASS using a custom config:
$ bobber parse-results --custom-baseline docs/sample_baseline.yaml dgx_station_results/ --baseline-tolerance 70

...

================================================================================
Baseline assessment
Comparing against a custom config
Allowing a tolerance of 70% below expected to PASS
================================================================================
 1 System(s)
--------------------------------------------------------------------------------
  FIO Bandwidth Read (GB/s)
    Expected: 1.2, Got: 1.595, Result: PASS
  FIO Bandwidth Write (GB/s)
    Expected: 1.0, Got: 1.232, Result: PASS
--------------------------------------------------------------------------------
  FIO IOPS Read (k IOPS)
    Expected: 100.0, Got: 136.5, Result: PASS
  FIO IOPS Write (k IOPS)
    Expected: 100.0, Got: 135.0, Result: PASS
--------------------------------------------------------------------------------
  NCCL Max Bus Bandwidth (GB/s)
    Expected: 230, Got: 79.86500000000001, Result: PASS
--------------------------------------------------------------------------------
  DALI 800x600 standard jpg (images/second)
    Expected: 2000, Got: 2694.595, Result: PASS
  DALI 3840x2160 standard jpg (images/second)
    Expected: 300, Got: 430.854, Result: PASS
  DALI 800x600 tfrecord (images/second)
    Expected: 2000, Got: 2665.653, Result: PASS
  DALI 3840x2160 tfrecord (images/second)
    Expected: 300, Got: 376.862, Result: PASS
================================================================================


Clients arent connecting to cluster running new version

I am upgrading a production vernemq cluster from 1.12.3 to 1.12.5 (master commit 85db5a1)
On 1.12.3, at any given point in time we had around ~60k clients connected. Each client had about 2-4 subscriptions.
This was working well, and we could publish messages to them with only occasional hiccups.
After pulling 85db5a1 and building from source, everything appeared to go well, and the cluster formed properly, but none of the machines in the field are connecting to the cluster now.
Environment

VerneMQ Version: 1.12.5 (commit 85db5a1)
OS: Ubuntu 20.04.3
Erlang/OTP version (if building from source): Erlang/OTP 22 erts-10.6.4
VerneMQ configuration (vernemq.conf)

allow_anonymous = off
allow_register_during_netsplit = on
allow_publish_during_netsplit = on
allow_subscribe_during_netsplit = on
allow_unsubscribe_during_netsplit = on
coordinate_registrations = on
max_inflight_messages = 20
max_online_messages = 1000
max_offline_messages = 1000
max_message_size = 0
upgrade_outgoing_qos = off
listener.max_connections = 200000
listener.nr_of_acceptors = 10
listener.tcp.default = <IP_ADDRESS>:1883
listener.vmq.clustering = <redacted-privateIP>:44053
listener.http.default = <IP_ADDRESS>:8888
systree_enabled = on
systree_interval = 20000
graphite_enabled = off
graphite_host = localhost
graphite_port = 2003
graphite_interval = 20000
shared_subscription_policy = prefer_local
plugins.vmq_passwd = on
plugins.vmq_acl = on
plugins.vmq_diversity = off
plugins.vmq_webhooks = off
plugins.vmq_bridge = off
metadata_plugin = vmq_swc
vmq_acl.acl_file = /usr/lib/vernemq/etc/vmq.acl
vmq_acl.acl_reload_interval = 10
vmq_passwd.password_file = /usr/lib/vernemq/etc/vmq.passwd
vmq_passwd.password_reload_interval = 10
vmq_diversity.script_dir = /usr/share/vernemq/lua
vmq_diversity.auth_postgres.enabled = off
vmq_diversity.postgres.ssl = off
vmq_diversity.postgres.password_hash_method = crypt
vmq_diversity.auth_cockroachdb.enabled = off
vmq_diversity.cockroachdb.ssl = off
vmq_diversity.cockroachdb.password_hash_method = bcrypt
vmq_diversity.auth_mysql.enabled = off
vmq_diversity.mysql.password_hash_method = password
vmq_diversity.auth_mongodb.enabled = off
vmq_diversity.mongodb.ssl = off
vmq_diversity.auth_redis.enabled = off
vmq_bcrypt.pool_size = 1
log.console = file
log.console.level = info
log.console.file = /var/log/vernemq/console.log
log.error.file = /var/log/vernemq/error.log
log.syslog = off
log.crash = on
log.crash.file = /var/log/vernemq/crash.log
log.crash.maximum_message_size = 64KB
log.crash.size = 10MB
log.crash.rotation = $D0
log.crash.rotation.keep = 5
nodename = mqtt1@<redacted-privateIP>
distributed_cookie = <redacted>
erlang.async_threads = 64
erlang.max_ports = 262144
erlang.process_limit = 500000
leveldb.maximum_memory.percent = 70
listener.tcp.name.allow_anonymous_override = off
listener.tcp.allowed_protocol_versions = 3,4,5,131,132
listener.ssl.name.allow_anonymous_override = off
listener.ssl.require_certificate = off

Cluster size/standalone: 4 Machines in cluster, mqtt1 - mqtt4

Expected behaviour

Clients connect to cluster running 1.12.5

Actual behaviour

Clients do not connect to the new cluster. Below im pasting some console logs as well as error logs for one of the machines

(console.log) There is a ton of these:
2022-06-15 21:14:55.924 [warning] <0.1639.0>@vmq_mqtt_fsm:check_user:581 can't authenticate client {[],<<"mqttjs_375ea0e2">>} from <IP_ADDRESS>:24315 due to plugin_chain_exhausted
2022-06-15 21:14:57.571 [warning] <0.1663.0>@vmq_mqtt_fsm:check_user:581 can't authenticate client {[],<<"mqttjs_375ea0e2">>} from <IP_ADDRESS>:52511 due to plugin_chain_exhausted
2022-06-15 21:14:57.749 [warning] <0.1664.0>@vmq_mqtt_fsm:check_user:581 can't authenticate client {[],<<"mqttjs_fa38c793">>} from <IP_ADDRESS>:59118 due to plugin_chain_exhausted
2022-06-15 21:14:59.253 [warning] <0.1679.0>@vmq_mqtt_fsm:check_user:581 can't authenticate client {[],<<"mqttjs_fa38c793">>} from <IP_ADDRESS>:8029 due to plugin_chain_exhausted
2022-06-15 21:15:00.705 [warning] <0.1680.0>@vmq_mqtt_fsm:check_user:581 can't authenticate client {[],<<"mqttjs_fa38c793">>} from <IP_ADDRESS>:21733 due to plugin_chain_exhausted
2022-06-15 21:15:01.536 [warning] <0.1682.0>@vmq_mqtt_fsm:check_user:581 can't authenticate client {[],<<"mqttjs_375ea0e2">>} from <IP_ADDRESS>:1309 due to plugin_chain_exhausted
2022-06-15 21:15:03.034 [warning] <0.1683.0>@vmq_mqtt_fsm:check_user:581 can't authenticate client {[],<<"mqttjs_375ea0e2">>} from <IP_ADDRESS>:5351 due to plugin_chain_exhausted
2022-06-15 21:15:04.791 [warning] <0.1684.0>@vmq_mqtt_fsm:check_user:581 can't authenticate client {[],<<"mqttjs_fa38c793">>} from <IP_ADDRESS>:5554 due to plugin_chain_exhausted
2022-06-15 21:15:06.245 [warning] <0.1697.0>@vmq_mqtt_fsm:check_user:581 can't authenticate client {[],<<"mqttjs_fa38c793">>} from <IP_ADDRESS>:44244 due to plugin_chain_exhausted
2022-06-15 21:15:07.067 [warning] <0.1708.0>@vmq_mqtt_fsm:check_user:581 can't authenticate client {[],<<"mqttjs_375ea0e2">>} from <IP_ADDRESS>:26197 due to plugin_chain_exhausted
2022-06-15 21:15:11.012 [warning] <0.1748.0>@vmq_mqtt_fsm:check_user:581 can't authenticate client {[],<<"mqttjs_375ea0e2">>} from <IP_ADDRESS>:61382 due to plugin_chain_exhausted
2022-06-15 21:15:12.985 [warning] <0.1766.0>@vmq_mqtt_fsm:check_user:581 can't authenticate client {[],<<"mqttjs_fa38c793">>} from <IP_ADDRESS>:53179 due to plugin_chain_exhausted
2022-06-15 21:15:14.157 [warning] <0.1771.0>@vmq_mqtt_fsm:check_user:581 can't authenticate client {[],<<"mqttjs_375ea0e2">>} from <IP_ADDRESS>:46487 due to plugin_chain_exhausted

(error.log)
CRASH REPORT Process <0.469.0> with 0 neighbours exited with reason: {listen_error,{{127,0,0,1},1883},eaddrinuse} in ranch_acceptors_sup:listen_error/5 line 96
2022-06-15 21:11:35.849 [error] <0.457.0> Supervisor {<0.457.0>,ranch_listener_sup} had child ranch_acceptors_sup started with ranch_acceptors_sup:start_link({{127,0,0,1},1883}, ranch_ssl, logger) at undefined exit with reason {listen_error,{{127,0,0,1},1883},eaddrinuse} in context start_error
2022-06-15 21:11:35.849 [error] <0.433.0>@vmq_ranch_config:reconfigure_listeners_for_type:219 can't reconfigure mqtts listener({127,0,0,1}, 1883) with Options [{max_connections,200000},{nr_of_acceptors,10},{mountpoint,[]},{depth,1},{eccs,[sect571r1,sect571k1,secp521r1,brainpoolP512r1,sect409k1,sect409r1,brainpoolP384r1,secp384r1,sect283k1,sect283r1,brainpoolP256r1,secp256k1,secp256r1,sect239k1,sect233k1,sect233r1,secp224k1,secp224r1,sect193r1,sect193r2,secp192k1,secp192r1,sect163k1,sect163r1,sect163r2,secp160k1,secp160r1,secp160r2]},{require_certificate,false},{tls_version,'tlsv1.2'},{use_identity_as_username,false},{allowed_protocol_versions,[3,4,131]},{allow_anonymous_override,false}] due to eaddrinuse

Heres a screenshot of my verne console on 1.12.3, showing clients (Yes, I know there is a version mismatch, i forgot to screenshot before I upgraded 2 of the machines. I wanted to show that there are indeed clients connected on the old version)

Heres a screenshot of my vernemq console on 1.12.5 commit 85db5a1, once all 4 machines in the cluster were upgraded

Its also important to note, that I swapped the metadata_plugin from vmq_plumtree to vmq_swc
The new cluster (running commit 85db5a1) that used vmq_plumtree would show subscriptions, yet it would also not show any clients connected.

For now, I've reverted back to 1.12.3 backups, and the cluster is restored to a working state. I am going to keep monitoring releases and commits and try to find one that can run a stable cluster in ^1.12.5

This issue does appear to be resolved - I needed to specify the location of my certs in verne.conf (This apparently was not necessary on 1.12.3)
I also updated OTP from 22 to 25, and re-built vernemq with the higher version of erlang. This potentially contributed as well.


Add support for test execution metrics

Java projects in Sonar have the following metrics, which this plugin does not yet provide:

(Number of) Unit Tests
Unit Test Errors
Unit Test Failures
Skipped Unit Tests
Unit Test Success (%)
Unit Test Duration

It would be nice if this plugin would also support these.
My guess is that for Java projects it uses JUnit test execution reports to get these metrics. We could add this functionality to this plugin in the same way as has been done for LCOV.
Users could generate JUnit test reports. There is a Karma reporter for this.

Duplicate


Forbid impossible pattern matching on generic capabilities

This changes the capability rules for pattern matching from
"some possible instantiation of the operand is a subtype of some possible instantation of the pattern"
to
"every possible instantiation of the operand is a subtype of every possible instantiation of the pattern".
In practice this makes the compiler issue an error when a pattern can only ever match for some reification of the generic capability. Code that uses this kind of pattern matching should now use iftype instead.
This doesn't fix any safety issues.

Forgot about that one. Merging now.


Document that dev-dependencies are used when building examples

@bors: r+ 22a5d4acf8336e1f910f25725256dce508869542

:hourglass: Testing commit 22a5d4a with merge 935df0f...

:broken_heart: Test failed - cargo-win-msvc-64

@bors: retry

:zap: Previous build results for cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32 are reusable. Rebuilding only cargo-mac-64, cargo-win-msvc-64...

:sunny: Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64


[BUG]: Transformers getting pre-transformed data.

transform function should be split into getters and setters in order to be able to add types to something.
so for example, lets say we have type Object but i want to know why kind of object it is when i am dealing with it then it would get the get return type.
or lets say that i want to store this object as a string instead and retrieve it back as an object i could specify type, get and set functions.

I don't fully understand your suggestion.  When you say add "types" what do you mean?  Do you mean add extra attributes/properties or do you mean map the type of an attribute value.
There are 3 possible transform hooks. See below. Two work on the entire record. One works on field by field.
In all, you can map the actual value or its type to and from the database.
The schema transform is:
        value = field.transform(this, 'write', field.name, value)

I can't seem to find the params.transform in the doc. The signature is:
        rec = params.transform(this, 'write', rec, params)

You can also apply a table level hook via the intercept Table construct param.
        rec = this.table.intercept(this, op, rec, params)

these in some way do not serve the purpose.  so let me illustrate in some way Dynamo-Onetable accepts Date as a type, but the underlying data type is a string. so there is convenience to having the storage data type be different than the one utilized in the application.
perhaps an example will illustrate the point.  The following should work but it doesnt for multiple reasons, the value is validated to be a string before it is transformed and if it did Typescript would not know whether the value accessed is a string or ParseOptions because they are intertwined in one function.
parseOptions: {
type: String,
required: true,
map: 'pa',
transform: (
_model: any,
op: string,
_name: any,
parseOptions: string | ParseOptions
): string | ParseOptions => {
console.log('TRANSFORM');
  return op == 'read'
    ? JSON.parse(parseOptions as string)
    : JSON.stringify(parseOptions as ParseOptions);
},

},

here is what i am saying it should be like.
parseOptions: {
    type: String,
    required: true,
    map: 'pa',
    get: (  _model: any,
      op: string,
      _name: any,
      parseOptions: string): ParseOptions => JSON.parse(parseOptions)
      set: (  _model: any,
      op: string,
      _name: any,
      parseOptions: ParseOptions): string => JSON.stringify(parseOptions)
  },

Thanks. That helps.
One question. You seem to be indicating that the 4th parameter 'params' is of a different type for read vs write. Isn't the 4th parameter always just the value?  I'm not sure I understand why you have JSON.parse(parseOptions as string) vs parse(parseOptions as ParseOptions) (what is ParseOptions?).
I'd like to capture the underlying issues and then consider solutions.  While your solution certainly has merit, I want to really understand all of the underling issues to make sure we are addressing them all. As we already have 3 transform options, I'd really like to rationalize them and get a unified, more flexible solution that meets all the needs.
Looks like the issues are:

The field.transform for write is invoked AFTER that value is already transformed by the inbuilt type transformers. This happens in Model.transformWriteAttribute
The field.transform for read is invoked ONLY and bypasses the inbuilt type transformers in Model.transformReadAttribute.  The schema transformer should be consistent with read vs write.
The field.transform is not receiving the field information which contains the schema field type,
The params.transform gets called AFTER the field.transform. i.e. both get called whereas params.transform should take precedence.

Are there others I've missed?

The answer to your question is, the get should expect the underlying data type and transform it to the desired and the set should receive the desired data type and transform it to the underlying data type.
ParseOptions in that case would be the type of object i want to work with. In the case of a date it could me a moment instance instead of the normal date object.
It could be that i want to save a string but in reality it represents a RegEx, so I set the value to a RegEx, the transform executes which takes it from a RegEx to a string and when i retrieve it back from the DB the string gets turned into a RegEx.

I understand that and agree that is the purpose of the transform function. To allow users to do exactly that.
The reason you are not getting the stored data as you wish is the schema transformer is conflicting with the inbuilt transformers. If you define a transformer, it should be invoked ONLY and bypass the inbuilt transformers.
So the signature for the "value" parameter on read would be ANY as you could store the data type anyway you wish. Similarly the return value could be any type. You can transform any to any.
Given that, I would have thought that read vs write would be symmetrical. Why are two functions required (get & set) ?

For Typescript purposes ,i thought it would be nice to have it nicely typed.

But if the value can be any and the return value can be any?

Right, seeing l some inference would need to happen to set the model type correctly

I'll change the designation to BUG and we'll fix the clashing with the inbuilt transformers. Then could you see if that will work as you need. I'm happy to revisit after we fix the core bug where your transformer gets pre-transformed data.

Fixed in 1.8.1. The schema field.transform will be invoked without any of the inbuilt transformations.


keyring/env-var looks for exec: "dbus-launch": executable file in $PATH on centos host

Describe the bug
A clear and concise description of what the bug is.
Error: command 'kam bootstrap --service-repo-url $SERVICE_REPO_URL --gitops-repo-url $GITOPS_REPO_URL
--image-repo $GITOPS_REPO_URL --dockercfgjson $DOCKERCONFIGJSON_PATH --git-host-access-token
 $GITHUB_TOKEN --output bootstrapresources --push-to-git=true', expected to succeed, exited with exit code: 1

Command stdout:
Checking dependencies
 •  Checking if Sealed Secrets is installed with the default configuration  ...

 ✓  Checking if Sealed Secrets is installed with the default configuration [237ms]
 •  Checking if ArgoCD Operator is installed with the default configuration  ...

 ✓  Checking if ArgoCD Operator is installed with the default configuration [442ms]
 •  Checking if OpenShift Pipelines Operator is installed with the default configuration  ...

 ✓  Checking if OpenShift Pipelines Operator is installed with the default configuration [510ms]
Adding .git to https://github.com/kam-bot/taxi-87
Adding .git to https://github.com/rhd-gitops-example/taxi

Command stderr:  ✗  unable to use access-token from keyring/env-var: exec: "dbus-launch": executable file not
 found in $PATH, please pass a valid token to --git-host-access-token

Details log - https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/redhat-developer_kam/87/pull-ci-redhat-developer-kam-master-v4.5-integration-e2e/1333827600312700928#1:build-log.txt%3A943
To Reproduce
Steps to reproduce the behavior:
Locally its bit difficult to reproduce for now. You can apply /test all to my pr https://github.com/redhat-developer/kam/pull/87 and wait for job ci/prow/v4.5-integration-e2e to fail.
I will create a separate issue to track the work around how to replicate same environment like prow CI uses from our host machine
NOTE: Prow uses this test container - https://github.com/redhat-developer/kam/blob/master/openshift-ci/build-root/Dockerfile
Expected behavior
keyring/env-var should not look for "dbus-launch": executable on centos host
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

/kind bug

ping @bigkevmcd

I tried the same docker file that prow uses and build my custom container to reproduce the issue. Surprisingly i could not reproduce the issue, i mean kam bootstrap command does not report dbus error and the command works as expected.
Steps i executed

Sipnned up a 4.5 cluster

Copy kubeconfig, kubeadmin-password and the auth file generated by the step https://github.com/redhat-developer/kam/blob/master/docs/journey/day1/prerequisites/quay.md - <username>-robot-auth.json in the same dir where you want a Dockerfile to build the image.

$ cat Dockerfile

# Dockerfile to bootstrap build and test in openshift-ci

FROM registry.svc.ci.openshift.org/openshift/release:golang-1.14

RUN yum -y install dnf httpd-tools sudo

RUN wget https://openshift-release-artifacts.svc.ci.openshift.org/4.5.0-0.nightly-2020-12-02-105352/openshift-client-linux-4.5.0-0.nightly-2020-12-02-105352.tar.gz

RUN tar -xf openshift-client-linux-4.5.0-0.nightly-2020-12-02-105352.tar.gz

RUN cp oc /usr/local/bin/

COPY kubeadmin-password .

COPY kubeconfig .

COPY <username>-robot-auth.json .

From the same dir build the contaiiner image

$ docker build --file Dockerfile -t docker.io/customcontainer .

Run the container

$ docker run -it customcontainer

Then in the container run the command

[root@930243aa5c33 origin]# cd ../.. && mkdir redhat-developer && cd redhat-developer/ && git clone https://github.com/redhat-developer/kam && cd kam/ && git fetch origin pull/87/head:pull_87 && git checkout pull_87 && mkdir auth && cp ../../openshift/origin/kubeadmin-password auth/ && cp ../../openshift/origin/kubeconfig auth/ && make prepare-test-cluster && make bin && cp bin/kam /usr/local/bin/

Do a kubeadmin login into the cluster

[root@930243aa5c33 kam]# oc login -u kubeadmin -p

Run the command

[root@930243aa5c33 kam]# kam bootstrap --service-repo-url https://github.com/amitkrout/taxi --gitops-repo-url https://github.com/amitkrout/gitops.git --image-repo quay.io/amitkrout/taxi --dockercfgjson ../../openshift/origin/<username>-robot-auth.json --git-host-access-token <token> --output resources

Checking dependencies

 ✓  Checking if Sealed Secrets is installed with the default configuration [1s]
 ✓  Checking if ArgoCD Operator is installed with the default configuration [2s]
 ✓  Checking if OpenShift Pipelines Operator is installed with the default configuration [2s]
Adding .git to https://github.com/amitkrout/taxi

Completing Bootstrap process

 ✓  Authentication tokens encrypted in secrets
 ✓  Pipelines tracker has been configured
 ✓  OpenShift Pipelines resources created
 ✓  Openshift Route for EventListener created
 ✓  Created dev, stage and CICD environments
 ✓  Bootstrapped OpenShift resources successfully

 Next Steps:
 Please refer to https://github.com/redhat-developer/kam/tree/master/docs to get started.

I need to check with test-platform team on how they are building the container image

I am able to reproduce it locally with kam-bot github user, but surprisingly when i am using my github user token bootstrap does not complain any error.
i am following exactly the same step as mentioned here at https://github.com/redhat-developer/kam/issues/104#issuecomment-737729323, instead of step 8 i am using the command
# kam bootstrap --service-repo-url https://github.com/kam-bot/taxi --gitops-repo-url https://github.com/kam-bot/gitops.git --image-repo quay.io/kam-bot/taxi --dockercfgjson ../../openshift/origin/kam-bot-kambot-auth.json --git-host-access-token ***** --output resources

ping @bigkevmcd

The repository referred to in the service repository must exist.

I'm going to close this out, the issues were around env-vars misconfigured in the test.


Small refactor of do_payout_stakers method

Remove unneeded closure

@Mr-Leshiy afaik this is intended and preferred: https://newbedev.com/why-should-i-prefer-option-ok-or-else-instead-of-option-ok-or


Payment method for Mural Required

Describe the issue
We were using a trial version of Mural (after moving from Miro & Draw.io) & that trial is expiring on Oct 25.
We will need a credit card to pay for the 2 member licenses
Work with Sid to secure the credit card
Which Sprint Priority is this issue related to?
The 'Milestone' should clearly list Sprint Priorities - which one is this issue related to?
Additional context
Add any other context, attachments or screenshots
Definition of done
Credit card in place for Mural

Approval request sent to Meara for processing.

Mural upgrade complete with p-card details in place.


[Feature] - Provide terminal links for ESLint output

Terminal Link providers are able to convert terminal links into file links which let VSCode navigate to the correct place.
Eslint could expose a TerminalLinkProvider which converts text like:
/Users/[user]/projects/playground/src/scripts/index.esm.ts
  32:27  warning  'config' is already declared in the upper scope on line 19 column 8  no-shadow

into a clickable link which takes you directly to the source

Actually that should already work for files that are relative to the workspace folder.

Im talking about turning this bit
32:27  warning  'config' is already declared in the upper scope on line 19 column 8  no-shadow into a link. Are you saying that’s something this extension already provides?

@jasonb01 actually no. I thought you are talking about the file link itself.

The reason I ask is because sometimes I get a lot of lines like that, but only 1 file line at the top. So being able to click these and they take me directly to the issue would be nice

Prefixing file://would be a simple start. Next, prepend the line info with the full path. So the OP example would be
file:///Users/[user]/projects/playground/src/scripts/index.esm.ts#32
  32:27  warning  'config' is already declared in the upper scope on line 19 column 8  no-shadow

This is already identified as a link in the Output panel

Just found that is works already. I configure Eslint > Lint Task: Optionsto contain-f unix` to get output like
/some/file/full/path.ts:345:7

with which a ctrl+click brings me to the line with the error.

This is now supported by default in VS Code:
https://code.visualstudio.com/updates/v1_80#_multiline-and-range-link-formats


Prep for Release v0.25.13

This PR does the following:

Prep for Release v0.25.13

Tugboat has finished building the preview for this pull request!
Link:

https://pr929-1s94qzs4cucuoewii9f96vnbilshdnnk.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6247174f7dc9604ba3cd447a


[Question]: How to update the patterns library

What is your question?
My computer is windows, I updated fabric using go language and now it works fine with the existing patterns.
The problem is that I have added a couple of system files to the .config/fabric/patterns file that someone else shared with me. The purpose of these patterns is to convert English to Chinese. They work in older python versions.
The filenames are only lowercase letters and _.  I have tried the following, none of them work.

using fabric --updating in bash
shutting down and trying again.
use fabric --setup to install again. This time the patterns I put in still exist in the patterns folder, but still nothing.

pls help

Did you try git pull?

Did you try git pull? I just updated few minutes before I read your issue. Merged latest updates with my local unique patterns.你尝试过 git pull 吗？我在阅读你的问题几分钟前刚刚更新。将最新更新与我的本地独特模式合并。

I'll try it right now.

Did you try git pull? I just updated few minutes before I read your issue. Merged latest updates with my local unique patterns.

I didn't clone the repository yet. I will try it.

Did you try git pull? I just updated few minutes before I read your issue. Merged latest updates with my local unique patterns.

wow, it really works. Thank you very much.

I clone the repository first.
Using the following code to local it in a file (for example c:\Users\ss\fabric)
git clone https://github.com/danielmiessler/fabric.git

2.I put my local pattern in this file ~.config\fabric\patterns
Then I

The following code help me copy the patterns provided in this repository
xcopy /E /I C:\Users\ss\fabric\patterns C:\Users\Joey.config\fabric\patterns


Clearing interrupt pending bits

As with most interrupt controllers (that I've worked with), the clearing of the pending bit for an edge-triggered interrupt can be optimized by clearing it automatically when software commits to handle the interrupt.
There are two such points in CLIC:

when the hardware takes a vectored interrupt (after the handler table has successfully been read, and before executing the first instruction of the handler), and
when reading xNXTI.
If there's ever a need to read xNXTI without committing to service the interrupt (not the case in any of the examples so far), one possibility is to create a second CSR that is functionally identical to xNXTI except that it doesn't clear the interrupt's pending bit.

This saves two instructions in the vectored case, and three instructions in the non-vectored case.
Note that example code shows sw x0, INTERRUPT_FLAG, a0 in both cases.  This expands to an AUIPC; SW sequence and works for the vectored case (except that sw needs to be sb, if I understand the memory map).  Spelling out the sequence clarifies instruction count and timing (and using LUI makes the code relocatable):
LUI  a0, %hi(clicintip)        # Section 14.2 mentions this LUI
SB   x0, INTERRUPT_NUMBER(a0)  # for vectored, interrupt number is implied

The non-vectored case needs to add the interrupt number to the clicintip[] address (which requires an extra register thus a bit of re-ordering of surrounding instructions to get a1) and takes up 3 instructions:
LUI  a1, %hi(clicintip) # Section 14.2 mentions this LUI
ADD  a1, a1, a0         # for non-vectored, interrupt number in a0
SB   x0, 0(a1)

Related areas the spec might clarify:

Whether the pending bit is the lsbit (bit 0) of its one-byte register.
Whether this pending bit can be set (triggering the interrupt) by writing a 1 to it.
The method for clearing edge-triggered interrupts, in the early parts of the spec (which right now mention clicintip[] without further details).

The assembler pseudoinstruction sw x0, INTERRUPT_FLAG, a0 is syntactic sugar for
1: auipc a0, %pcrel_hi(INTERRUPT_FLAG)
   sw x0, %pcrel_lo(1b)(a0)

Ah, thank you.  (I didn't find any documentation that covers this syntax.)
I updated my comment accordingly.

As you requested the proposal now automatic clears clicintip for edge-triggered interrupts at entry for Selective Hardware Vectoring (SHV) mode and on executing a modifying  mnxti instruction typically just before exiting that interrupt handling.
For level triggered interrupts the clicintip state should be cleared by writing to the device causing the interrupt.
I believe the revised text now answers your request for clarification:
"The method for clearing edge-triggered interrupts, in the early parts of the spec (which right now mention clicintip[] without further details)."
For clarification request "Whether this pending bit can be set (triggering the interrupt) by writing a 1 to it.".
It is partly answered as clicintip can be directly written:
"clicintip[i] is a read-write register. Software-based (direct) writes to these pending bits have priority over hardware-based writes (triggers)." and
"Note: During normal operation, software does not need to clear pending bits because CLIC hardware already supports automatic clearing of pending bits for edge-triggered interrupts. As for level-triggered interrupts, they should be cleared at interrupt sources (devices) so no need to clear the pending bits. Therefore, software usually only needs to modify pending bits in the initialization process or testing. "
What isn't answered is if software setting clicintip triggers an interrupt.
As far as I can tell the text is silent on this point.
I am surprised and disappointed that your remaining question was not answered.
"Whether the pending bit is the lsbit (bit 0) of its one-byte register."
I will raise a separate issue including this last concern.
Sifive used bit zero for its original proposal.

Re: "Whether this pending bit can be set triggering the interrupt"
The spec does imply it is possible:
"To select an interrupt to present to the core, the CLIC hardware combines the valid bits in
clicintattr.mode and clicintctl to form an unsigned value, then picks the global maximum across
all pending-and-enabled interrupts based on this value."
However. the spec should be stipulate whether software setting the pending bit does indeed make the interrupt pending.
For consistency within the model I believe it should.

Pending bit is located in bit 0 (LSB).
Writing pending bits with SW will definitely set/clear edge-triggered interrupts.
In contrast, for level-triggered interrupts, SW writing to pending bits is ignored completely.

As a side note, in the course of our group discussion, some members expressed that setting pending bits to activate level-triggered interrupts is a useful feature for testing. Another suggestion was to define it as “undefined” to give each company the freedom to decide whether they need this testing feature. However, we finally concluded that writing to pending bits for level-triggered interrupts will be ignored for the following reasons:

This “sticky-bit” behavior is against the traditional concept of level-triggering, so it can create confusion for users.
To have this sticky property, an extra latch is needed so the HW cost will increase.
SW interrupt handler will need an extra step to manually clear this bit in addition to the mandatory clearance of the external level-device. This extra step may be easily forgotten and also add more instructions and latency.
Defining the writing behavior entirely as “undefined” can create nightmare for compatibility and compliance tests.
Lastly, users can easily add a simple external testing module if they really need this testing feature.

Clarified in the spec with commit 740e39a.


Advanced DNS metrics e2e is flaky

Describe the bug
Need to investigate why sometimes the correct advanced DNS metrics not showing up during e2e

Advanced DNS metrics sometimes doesn't show up right away after a single curl request, but they will show up if we make a subsequent curl request. The resulted metrics have the correct count that include both request.


Very outdated 4.0 code

linear_interpolate() was replaced by lerp()
the class is now called CharacterBody3D
velocity is now the actual value within the class
and many other stuff that i missed

move_and_slide_with_snap() is not found in base self either.


Add Defer Prop

Recreating this PR due to the master branch deletion. If the previous PR was closed on purpose, I apologize for the noise.
Original description: I felt inspired by Livewire 3 Lazy feature which automatically fetched the data on page load. I think there's a ton of value in Inertia's current Lazy prop feature, but I think there are also scenarios where adding a Defer prop feature which automatically loads Lazy data on page load.
This works in tandem with https://github.com/inertiajs/inertia/pull/1617. It works by extending the Lazy feature but also informs the front-end on page load which deferred properties should be loaded automatically. These properties will then automatically trigger a reload with those properties automatically added in the only attribute.
This reduces the amount of front-end code required to pull this off. To add a long-running API query to be deferred, it would look like this:
return Inertia::render('Organizations/Index', [
            'filters' => Request::all('search', 'trashed'),
            'organizations' => Inertia::defer(
                fn () =>
                Auth::user()->account->organizations()
                ->orderBy('name')
                ->filter(Request::only('search', 'trashed'))
                ->paginate(10)
                ->withQueryString()
                ->through(fn ($organization) => [
                    'id' => $organization->id,
                    'name' => $organization->name,
                    'phone' => $organization->phone,
                    'city' => $organization->city,
                    'deleted_at' => $organization->deleted_at,
                ])
            ),
        ]);

These deferred properties will only ever be loaded automatically after page loads/navigations. Otherwise, they behave just the same as Lazy props.

@adrum Really appreciate you sharing this idea, but I'm going to close this one for now for the reasons stated in your other PR:
https://github.com/inertiajs/inertia/pull/1617#issuecomment-2133398269
Once we've figured out an async story in Inertia I'd plan to loop back to this 👍


CoinGeckoClient() constructor is a thread leaker

The no-arg CoinGeckoClient constructor creates a new HttpClient but never closes it. This is not just to be pedantic, it causes problems in reality. The utility function it uses to create the HttpClient makes it with the first engine found by ServiceLoader, which in my case is CIO. A CIOEngine starts a dispatcher with some threads, and these are never stopped, leading to a thread leak (as seen by a huge number of "ktor-cio-dispatcher-worker-N" threads) and an inevitable crash.
I would suggest making CoinGeckoClient implement AutoCloseable and closing the automatically constructed HttpClient in its close method (but not an externally provided HttpClient). If that's not possible I'd suggest deprecating the no-arg constructor or adding a big fat warning to its documentation.

Fixed in v1.0.0-rc01

Appreciate the fast fix. Shame there isn't a stable closable interface, but at least that sounds like they're working on it?

Looks like it will be stable in Kotlin 2.0: https://youtrack.jetbrains.com/issue/KT-55777/Unresolved-kotlin.AutoCloseable-in-JVM#focus=Comments-27-7285243.0-0


Cotary Create: Schemes Preview

The code for the preview showing the overview of the schemes config is needlessly complicated and doesn't appear to be entirely functional.

@Flash-Git can you include links to said code?

@dOrgJelli Sure!
Mainly this file.

Reopening to redo changes for #401


Trailing slashes should be ignored

If I set up a route "/foo", it is ignored when the path is "/foo/". Bug or intended behaviour?

Hi @axefrog. It is not a bug, route matching is strict. However, I will support a few options in the near future:

Strict path matching (as for now)
Trailing slashes ignored
Trailing slashes ignored and path rewritten to the matached route path

Looking forward to this :). :+1:

+1

0.5.0 released, with support for optional trailing slash. trailingSlash option can be set to a truthy or falsy value:

truthy for optional trailing slash and URL will be rewritten to its intended format
falsy for strict URL matching (default)


运行程序之后采集失败

core-1  | INFO:     Started server process [19]
core-1  | INFO:     Waiting for application startup.
core-1  | INFO:     Application startup complete.
core-1  | 2024-07-13 13:33:55.431 | INFO     | insights:pipeline:45 - publish date is 20240303, too old, skip
core-1  | 2024-07-13 13:33:55.632 | INFO     | insights:pipeline:45 - publish date is 20240303, too old, skip
core-1  | 2024-07-13 13:33:55.650 | INFO     | insights:pipeline:45 - publish date is 20240628, too old, skip
core-1  | 2024-07-13 13:33:55.878 | INFO     | insights:pipeline:45 - publish date is 20180409, too old, skip
core-1  | 2024-07-13 13:33:56.063 | INFO     | insights:pipeline:45 - publish date is 20180409, too old, skip

这不是运行失败，这已经运行成功了，只是抓取到的信源太旧，目前是设定只抓取前三天的信息

how to change this?

core/insights/init.py  更改这里面的 expiration_date


Better TN checking; better handle renamed DCS repos

Pull Request Test Coverage Report for Build 448

11 of 98 (11.22%)  changed or added relevant lines in 4 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.5%) to 50.865%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

resource_container/ResourceContainer.py
7
13
53.85%

webhook.py
2
24
8.33%

preprocessors/preprocessors.py
1
60
1.67%

Files with Coverage Reduction
New Missed Lines
%

preprocessors/preprocessors.py
3
33.04%

Totals

Change from base Build 443:
-0.5%

Covered Lines:
3177

Relevant Lines:
6246

💛  - Coveralls


Merge from private/auth-master

Features include

Allows the app to handle continue URL natively.
Allows the app to set language code, e.g., for sending password reset email.

@paulb777 Yes my bad. I believe all is fixed now.


evaluateOptions not working if file name != promptfooconfig

Describe the bug
The evaluateOptions is not effective if my promptfoo config file is different from  promptfooconfig.yaml
To Reproduce

With a promptfooconfig.yaml set evaluateOptions: { repeat: 2, cache: false } and write a test
Execute promptfoo eval or promptfoo eval -c promptfooconfig.yaml
The test is well repeated 2 times and the cache is disabled
Rename promptfooconfig.yaml into promptfooconfig-test.yaml
Execute promptfoo eval -c promptfooconfig-test.yaml
The test is executed only once, and the cache is enabled

Expected behavior
I expect that the evaluateOptions are effective if my promptfoo config file is different from promptfooconfig.yaml
System information (please complete the following information):

Promptfoo version: 0.90.1

I also ran into this issue!

This issue no longer presents for me on the latest version of the code.

Can confirm that this issue still presents on the latest code. I am going to take a swing at this.


Issue with RuneLite's 'Always on top' setting

I installed the plugin and my client froze, not responding when I clicked it, even after restarting - I couldn't move the window. Looking at the processes in Task Manager I could see it was throwing up a pop-up for the plugin. I have RuneLite's Always on top setting enabled, so I suspect it's due to that.
I was able to maximise the warning pop-up in the back ground (via the process in Task Manager) so I can click on the OK/Cancel buttons, but this is very user-unfriendly.
Other pop-ups, such as those shown when using the Inventory Setups plugins work fine with Always on top enabled.

The warning should now show above Runelite in the next update. 630be04


QA: Wrong spaces

Spaces appear due to formatting and the compiler misunderstands the expression.
How to fix?

Here too

provide plain code for testing

Code  https://pastebin.com/C6zLK1M3

technically, there is no pawn code formatter, this extension use javascript formater, so there are limitations... I tried to fix it, but it does not work out. so, you can either not use formatter or use it within it's limits... if you can fix, will appreciate the PR.
I am closing this issue, as for mentioned reason. I can't help it, sorry.


User Claims Going to Wilderness

I have a user who created three subdivisions within his claim and then gave two to two other users and kept one for himself. He deleted them all and afterward one of the users had a blank claim and the owner had a blank claim, but the third user did not.
Their blank claims were under worlds>wilderness>basic for some reason.

Reproduce on clean server and provide exact steps.

Unable to reproduce.


Bottom Bar overlays part of the layout

After the latest update, the bottom bar is taking up part of the bottom layout (see how the FAB is overlapped), I guess because it isn't pushing it up?

What does your XML / Java look like?

And are you using the version 1.1.5? I think this bug was introduced a couple versions before that, but I just might've fixed it again in 1.1.5.

This was on 1.1.5
here is the code:
appBar = BottomBar.attach(this, savedInstanceState);
        appBar.noNavBarGoodness();

        if (findViewById(R.id.main_container) != null) {

            MainAppFragment mainAppFragment = new MainAppFragment();
            mainAppFragment.setArguments(getIntent().getExtras());

            HelpFragment helpFragment = new HelpFragment();
            helpFragment.setArguments(getIntent().getExtras());

            SubscriptionFragment subscriptionFragment = new SubscriptionFragment();
            subscriptionFragment.setArguments(getIntent().getExtras());

            AboutFragment aboutFragment = new AboutFragment();
            aboutFragment.setArguments(getIntent().getExtras());

            appBar.setFragmentItems(getSupportFragmentManager(), R.id.main_container,
                    new BottomBarFragment(mainAppFragment, R.drawable.ic_home, "Home"),
                    new BottomBarFragment(helpFragment, R.drawable.ic_help, "Help"),
                    new BottomBarFragment(subscriptionFragment, R.drawable.ic_card_giftcard, "Subscription"),
                    new BottomBarFragment(aboutFragment, R.drawable.ic_info, "About"));

<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:tools="http://schemas.android.com/tools"
    android:id="@+id/main_container"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:orientation="vertical"
    tools:context=".ui.MainActivity">

</LinearLayout>

Update: Updated to 1.1.7 and all is good now


Select only the results of the search

When you make a search :

If you click on the checkbox on the left of the search it should select only the result of the search and not all the options :

@freddidierRTE set selectAllOnlyVisible: true to enable this feature.

It works , thanks !


docker

how can i setup docker mail server.please give me a tutorial

In the Wiki of the project you find a lot of documentation.

Same as @Josef-Friedrich.


Call drawGrid() and drawCells() prior to the first invocation of tick().

Summary
This PR adds a drawGrid() and drawCells() call just before the
first call to requestAnimationFrame() in order to ensure that the initial
state of the universe is drawn prior to executing a Universe.tick() call.
Explain the motivation for making this change. What existing problem does the pull request solve? 🤔
If this is not done, the initial state of the universe is never drawn,
which can be confusing for those looking to implement the exercises where a
specific starting set of cells is desired.

[x] 👯 This PR is not a duplicate
[x] 📬 This PR addresses an open issue (#118)
[x] ✅ This PR has passed CI

Added a PR here: https://github.com/rustwasm/wasm_game_of_life/pull/37

Also, I've updated the later code in interactivity.md to account for the source change mentioned above.


Logging of used options may be confusing: e.g. [Renderer=Harfbuzz,Renderer=Basic].

Description
Investigating some issue with polyglossia I am confused by log file: it says
Package fontspec Info: Font family 'STIXTwoText(1)' created for font
(fontspec)             'STIXTwoText' with options
(fontspec)             [Renderer=Harfbuzz,Renderer=Basic].

...

Package fontspec Info: Font family 'STIXTwoMath-Regular(0)' created for font
(fontspec)             'STIXTwoMath-Regular' with options
(fontspec)             [Renderer=Harfbuzz,Renderer=Basic,BoldItalicFont={},Itali
cFont={},SmallCapsFont={},Script=Math,FontAdjustment={\__um_luatex_copy_fontdime
ns:
(fontspec)             },Extension={.otf}].

and although it is quite certain it is Harfbuzz it is confusing. Can both at same time make sense (naive question, if answer is yes then my ticket is irrelevant).
Check/indicate

[ ] Relevant for XeTeX
[x] Relevant for LuaTeX
[ ] Issue tracker has been searched for similar issues?
[ ] Links to <tex.stackexchange.com> discussion if appropriate

Minimal example demonstrating the issue
\documentclass{article}

\usepackage{polyglossia}
\setmainlanguage{english}

\usepackage{unicode-math}

\setmainfont{STIXTwoText}

\setmathfont{STIXTwoMath-Regular}[Extension=.otf]

\begin{document}

$\cos\alpha\leq\sin\gamma\approx\tan\pi$

$\sum \cos x \prod \sin y \lim\tan z$

\showoutput
\end{document}

Further details

Imho the problem is with polyglossia. It is adding the harfbuzz option unconditionally to every font.
It would make much more sense to either use harfbuzz only with the scripts where it is the better choice (for latin scripts node mode is normally better for the hyphenation), or at least to restrict it to the text font families:
\documentclass{article}

\usepackage[luatexrenderer=none]{polyglossia}
\defaultfontfeatures[\rmfamily,\sffamily,\ttfamily]{Renderer=Harfbuzz} %better
%\defaultfontfeatures{Renderer=Harfbuzz} %your log

\setmainlanguage{english}

\usepackage{unicode-math}

\setmainfont{STIXTwoText}

\setmathfont{STIXTwoMath-Regular}[Extension=.otf]

\begin{document}

$\cos\alpha\leq\sin\gamma\approx\tan\pi$

$\sum \cos x \prod \sin y \lim\tan z$
\end{document}

Imho the problem is with polyglossia. It is adding the harfbuzz option unconditionally to every font.

Yes, and with cmap (at version 1.0j or 1.0h and earlier with luatex85) this has effect that copying-pasting operator names (cos) from pdf (obtained via lualatex) gives unexpected result. I felt I was not competent enough to open ticket at polyglossia. I thank @zauguin who explained to me source of the problem in this unconditional usage of HarfBuzz by recent polyglossia.

Yes, and with cmap (at version 1.0j or 1.0h and earlier with luatex85) this has effect that copying-pasting operator names (cos) from pdf (obtained via lualatex) gives unexpected result.

Sorry: cmap is not relevant here. I in fact spend quite some time a few hours ago about this but for some strange reason wrote the contrary of what I knew already. Well I will open a ticket at polyglossia if not already done.


Contact admin url in Django footer fixed to point to Angular

Contact admin url in Django footer fixed to point to Angular

Codecov Report

Merging #1004 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1004   +/-   ##
=======================================
  Coverage   88.82%   88.82%
=======================================
  Files         108      108
  Lines        2505     2505
  Branches       28       28
=======================================
  Hits         2225     2225
  Misses        277      277
  Partials        3        3

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 e0da50b...74be8ef. Read the comment docs.


Reduce memory in classification metrics when average='micro'

What does this PR do?
Fixes #1279
When average='micro' in multiclass classification we do not need to form the full [n_class, n_class] confmat to do the calculations. This PR introduces a much simpler reduction that scales much better when n_class is a large number.
Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure to update the docs?
[ ] Did you write any new necessary tests?

PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

LGTM, can we add a simple test-case asserting that this is actually used properly?

Do you want test for memory consumption?
Because tests for correctness is already covered by the tests that are already in place.

Do you want test for memory consumption?

would be great :)