Dark theme issue

Good evening,
I have an issue with the dark theme. When the accordion is expanded everything looks ok:

But when the accordion is closed, the dark theme is wrong:

Any idea why? How can i resolve this issue, and even better. how can i customize the element?
Thanks!

I will test it and update this
but you can publish the views and edit them if you want, and PRs always welcome :)

but its not happening here:
https://demo.larazeus.com/admin/components-demo/accordion
maybe you already published the views? and need to update them?

Hi @atmonshi I havent published the views until you told me, and i published them out of curiosity. There is something wrong, as it says dark:gray-900 but instead i see white (or something whitish).
I havent touched the library at all, just installed it and used it as per manual.
What went wrong?

are you sure about adding this:
https://larazeus.com/docs/accordion/v1/getting-started/installation#content-theme
and run npm run build


🏆Ranklist and Certificate Info

Hi enthusiastic contributors,
Congratulations🎉 and Thank you for contributing and making the Hacktoberfest a success for you and for us.
Time for celebration 🥳:
Please take a moment to share your achievements and the dedication you've displayed throughout the month of October. Showcase your accomplishments on LinkedIn, allowing your network to appreciate the positive impact you've made. 📈
Be sure to mention the repository - SarthakKeshari/calc_for_everything (github.com) 📚, highlighting the specific features you've skillfully integrated into it.
I'd be honored to extend my personal congratulations, so if you wish to include me in your celebration 🎊, do not hesitate to tag me in your posts on LinkedIn - Sarthak Keshari | LinkedIn

Contribution Certificate
All the contributors are requested to fill the Google form. Form will be active till 10th of November, 2023.
https://forms.gle/oQ5NPE2KP3fkQDwn6

🏆 Special Certificate for Top 3 contributors of this repository
🥉Collect 5 points and earn your Open-Source Contributor Certificate
🥈Collect 25 points and earn your Open-Source Contributor Certificate - (Finisher)
🥇Collect 50 points and earn your Open-Source Contributor Certificate - (Extra Miler)

Help us reach more contributors 😇
Click the star icon on the repository main page. ⭐

Ranklist

Rank
Githib Handle
Points Scored

1
@maskboyAvi
95

2
@Upadhyay-Harshit
80

2
@nipun221
80

3
@imsoumik03
55

3
@anushka-srivastava22
55

4
@dvtushar
50

4
@Deathanni
50

4
@syash7202
50

5
@7twik
45

5
@ravishrivas
45

6
@Saksham-245
40

6
@uttkarsh1m
40

6
@PrachiDev11
40

7
@Rida-Nuha
35

8
@Akash0420
30

8
@Sk783
30

8
@Satvik-Garg
30

9
@Sam-bhav-20
25

9
@Celebi07
25

9
@aniketsinha5552
25

9
@rishirohilla
25

9
@divyansh-4
25

9
@sikehish
25

10
@DanishGBU
20

10
@capsy14
20

10
@sachinsingh2020
20

10
@munfaridzahera
20

10
@remonix
20

10
@its-kumar-yash
20

10
@girisha-pawan
20

10
@tejxv
20

11
@hiren2599
15

11
@govardhanshah456
15

11
@farhanalws4u
15

11
@dfordp
15

11
@DeexithParand2k2
15

11
@Ayushlion8
15

11
@mr-kadyan
15

11
@chinmayr633
15

11
@ashishnallana
15

11
@aditya962
15

11
@Rishika631
15

12
@VincentPaulV
10

12
@Vimal-Dubey
10

12
@shrinidhihegde3
10

12
@shreyashsingh-101
10

12
@Saifullah00
10

12
@plon-Susk7
10

12
@Kris0011
10

12
@ArnabBCA
10

12
@Pasqua101
10

12
@Ayush-Vish
10

12
@ctln23
10

12
@aditish11
10

12
@IshaanShettigar
10

13
@vendhan-ds
5

13
@tmsagarofficial
5

13
@tiwari00ayush
5

13
@TANYA03GUPTA
5

13
@srronaksingh
5

13
@Musak2
5

13
@Heramb4270
5

13
@atharvsawant2003
5

13
@abhijithhegde
5

13
@Ahasasjain
5

13
@XronTrix10
5

13
@shivanshhgit
5

13
@real-varshney
5

Thanks and Regards,
@SarthakKeshari

Hi all,
Points will continue to be added till 31st October.
Final ranklist will be released on 2nd November


GetNearbyContainers to List, added kgDrawers support

<3

Couldn't find any issues in my testing.


Option to restrict ICE candidates

I would be great if it was possible to restrict list of ICE candidates.
Currently my home assistant instance is hosted as docker container and is connected through 2 networks:

IoT vlan
nginx reverse proxy network

As a result 3 candidates are presented to the browser (about:webrtc in  firefox)

IoT vlan (ok)
nginx reverse proxy (not ok)
public ip (ok)

This is probably a reason why sometimes I have issue with the video, but refreshing the page often helps.

I can see you have a code on JS side that is supposed to remove docker IP's.
However it does not work for my IP of <IP_ADDRESS> (IP is not static in this subnet)

I don't understand what you mean about "nginx reverse proxy network". Nginx proxies only HTTP(S) port. WebRTC uses other UDP ports for transmit video data.
It's not a problem when you have "wrong" ICE candidates. The WebRTC will check all of them.

nginx reverse proxy network - refereed to docker network that only purpose is to connect nginx container with other containers requiring proxy.
You are right that this is not critical. I'm trying to solve this minor annoyance on the asterisk side.

You Hass container should use network host mode (whole network access without proxing).

Probably should add, that it already works/ed (without host network). I've migrated to rtsp to webrtc due to the fact that it allows me to neatly avoid some other issues with SIP card ;)
Feel free to close this issue, and thank you for your work!


Fixed various bugs canonicalizing arrays

In https://github.com/ioam/holoviews/pull/1524 I made some fixes for grid based interfaces but seemingly also introduced a bug. This PR finally addresses these issues correctly. Unit tests to follow.

Ready to merge when tests pass, previous unit test was not checking the exact array values so the accidental flipping wasn't detected.

Looks good and the tests are passing. Merging.


fix: elevate priviledges for custom publish jobs

https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token
https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#adding-permissions-settings

id-token: write is basically "get an oauth token for authenticating with package managers like pypi"
packages: write is basically "publish to github packages" (for docker images)

Both of these are reasonable to provide to all publish jobs, and it's not really a security risk to do so, imo.


Handle hash error and char-convert warning

Hi Ken (@0vm) this PR is intended to investigate #1.

See also #1

Thank you for the PR, much appreciated, I had only tested it on v143, so it is good that you made this so others do not face the same issue!


Touch ID is not working after 2.0.1 (iPhone 8)

(iPhone 8, 11.3.1)
It works right after rebooting, but the moment I lock my phone, it requires my password to unlock my device, reverted back to 2.0.0 for now.
Thanks for your effort pwn.

this seems to be a very rare by-product of the mp exploit, I had this on Electra with my iPhone 7. For me after rebooting and re-jb it worked again.
@Cryptiiiic has also experienced this issue


Settings invalid api url for valid url

add 'a' to meloona api url,
https://api.meloona01.digma.systemsa
apache url validator treats it as invalid, I think it checks that the host is available

install this
https://mega.nz/file/1vkGlJTL#yU-SJLlIilF0mx5qwpPOd3BM8iKZqOJLEQUStR76rrQ
you may need to install the c compiler


Load PMLB colon data

Description
Get the Princess Margaret Living Bank data following up Nhu-An Pham email
3 more cohorts (colon, lung and pancreas) - to be sent end of August
Acceptance criteria

[x] transform data
[x] colon data is in GitLab repo
[ ] colon metadata and data validated and loaded

Email sent

I have recieved the Lung cohort metadata. I am confirming with Nhu-an that this data is ready for release mid-September. The associated mut and cna data is on the cbioportal.ca and needs to be extracted using the cbioportal json

Lung cohort is not ready for release. However, just received the pancreas cohort that can be released in the next data set.

Well done and great news @Afollet ! a very productive week 👍

Placed metadata in git repo "data_quarantine".  Transferred to updated template. All models with POP will need to be prepended with "PMLB_" as requested. There is an unamed model that will need to be resolved. This data is going to be concatonated with the existing PMLB data.
There is molecular characterizations for this data on cbioportal.ca. I have contacted the developer at PMLB to request permission be granted to my user to retrieve these from the Swagger API. They will then need to be parsed using the cbioportal JSON parsing pipeline in the PDX Finder app.
I have request the sampleplatform.xlsx sheet associated with this data set and the information needed for the Word press pages.

Loaded the Colon data into the repo

close this one, create a separate ticket for pancreas and lung data @zperova

Waiting for Sample Platform, correspondence for cbioportal, and documents for word press pages.

close this one, create a separate ticket for pancreas and lung data @zperova

this comment should be ignored, as ended up modifying the ticket.

Recieved and added sampleplatform data to the repo for the Colon dataset

There are additional mappings needed here @zperova

I have been granted access to the data sets and will export them to templates. The wordpress page is here: http://dev.pdxfinder.org/platform/pmlb-crc/

For the task of parsing the data a new ticket has been made #322

@Afollet I believe we need to remove the first sentence from the Wordpress pages for better reading experience. Also I am not sure the title is the best fit for this type of page.

updated page looks very nice, thank you @Afollet

@zperova This ticket is done.
I would like to have one last review of all the data I loaded before the release.

great, thanks @Afollet


Line endings in copyrightText are not normalized

The file header analyzer normalizes line endings in the source text to \n for comparison with the expected copyright text. However, the line endings coming from the settings file are not normalized in the same way, so if a user writes \r\n in stylecop.json it will never match the files.

I can't reproduce this in test or production code.


Replace "Team" by "User" everywhere

At the moment, fuzzy land talks about "Teams" everywhere. Since we are a person (individual) ctf and not a team ctf, I propose to change "Team" to "Discoverer" or "Player" or "Hacker" or "User", or similar.
Replacing it in the template should be enough,
I dont think we should touch the database models etc.

Any opinion on this?

Replaced strings in the theme in b17fe27. URLs remain the same for now.


Fixes formatting errors in README_EN.md

Some headers, code blocks, formatting, and links were broken during the automated translation to English, which made the content difficult to read. These issues are now fixed.

Thx


Retro for the Gatsby theme website building process

As an IBM.com library website creator with the Carbon Gastbt Theme,

I need a way to record all the things that work well, does not work well, during the website developing process

so that I can share the findings with the Carbon Team and contribute to making the Carbon Gatsby Theme better.

Tasks

[ ] Set up a Gatsby Theme website development retro - Jeff, Wonil, Jacob, and Jenny.
[ ] Create a list of the retro items to share with the Carbon Team.

Acceptance criteria

[ ] Share the outcome with the Carbon Team.

Items to be recorded from #191

I reached out to Roberta for facilitating the retro session and she agreed - Thank you @roberta!👏 👏 👏
The session scheduled for Thursday 02/19.
Trello board set up for the session can be viewed [here](https://trello.com/b/kl8YLD9d/gatsby-website-creation-process-retrospective0

Gatsby website creation process retrospective session completed and follow up with the team via Slack.
Next step: Jacob and I will meet and create issues for the action items as needed.

task issues created for the action items:
#1756, https://github.com/carbon-design-system/ibm-dotcom-library-website/issues/370, https://github.com/carbon-design-system/ibm-dotcom-library-website/issues/371, https://github.com/carbon-design-system/ibm-dotcom-library-website/issues/372, https://github.com/carbon-design-system/ibm-dotcom-library-website/issues/373


Update crosstest reference text

This updates references to the crosstest repo to use conformance instead.
Note that the Docker image used for crosstests still uses an old bufbuild image. This is because the test proto packages have changed in the new repo and switching to use one of the new images would cause all existing code to break. This will be fixed in a follow-up PR.

@rebello95 I closed #158 and am going to split it up into two separate PRs. This one can be landed first, which updates most of the text and references to use conformance but does not use the new images and new proto packages. Then, I can look into a follow-up PR as to why the new images won't pass tests.


Redesign bind system

The current bind internals are a bit messing and have a few areas where failure could be easily introduced in the future. This must be remedied in addition to moving from (FunctionName, Key) to (Key, FunctionName). This has already been done cosmetically with https://github.com/ForLoveOfCats/SkyOfSteel/commit/7c3708112796186059d872db1d0d2cd4babffd42 but the internal behavior has not changed. This is important as (Key, FunctionName) allows us (by implying to the user) that multiple keys can be bound to the same action but only one action per key (which is required for controller support as the system should allow the keyboard and controller to both drive the same actions).

This is done


[Firmata] "sendSysex" doesn't work properly

I followed this tutorial https://github.com/ms-iot/remote-wiring/blob/develop/advanced.md to setup a very simple custom command. "FirmataConnectionReady" works properly when initializing Firmata the first time, but Firmata.sendSysex doesn't work when sending custom command. below are the codes:
On Arduino Side - >
define ALL_PINS_COMMAND 0x42
void sysexCallback(byte command, byte argc, byte *argv)
{
byte mode;
byte slaveAddress;
byte data;
int slaveRegister;
unsigned int delayTime;
switch (command) {
case ALL_PINS_COMMAND:
Firmata.sendString("Hello from arduino!");
break;
... ...
...
C# Side - >
const byte ALL_PINS_COMMAND = 0x42;
... ...
public void SendSysexCommandHandler(object arg)
{
if(Firmata.connectionReady()) <----------- return true
{
byte b = 1;
Firmata.sendSysex(ALL_PINS_COMMAND, new byte[] { b }.AsBuffer());
}
}

Hey EdgarSun! can you clarify what behavior you are seeing when you run the above? Are you sending the sysex but not receiving the string reply?
For debugging, I would suggest:

Verify that you have subscribed to the StringMessageReceived event in RemoteDevice. This event will be invoked when a sendString is received from the device.
Modify the Arduino sketch to use digitalWrite to manually light an LED when ALL_PINS_COMMAND is received. This will help us identify if the trouble is with sendSysex or with the string reply.

I put some debug codes in sysexCallback, it works well when initializing firmata the first time, because I can got the command message from "StringMessageReceived" event handler in c#.
Logs:
Received string message from arduino: 240
Received string message from arduino: 107
Received string message from arduino: 107
Connected arduino!

The problem is there was not any command message received when when running below codes:

For debugging:

Verify that you have subscribed to the StringMessageReceived event in RemoteDevice.
-> Yes, this event's hooked up correctly, I can get string message at the beginning when initializing firmata

Modify the Arduino sketch to use digitalWrite to manually light an LED
-> Sorry, I don't have a LED for testing digitalwrite. But it seems the function "sysexCallback" was not triggered any longer when executing "Firmata.sendSysex()" on c# side.

So you are getting some messages from the Arduino when it first initializes, but you are never seeing the "Hello from Arduino" string come back when a sysex message is sent to the Arduino ( and it is assume this code should be invoked on Arduino side)?
switch (command) {
case ALL_PINS_COMMAND:
Firmata.sendString("Hello from arduino!");
break;

We want to identify the point of failure... and I think its a bit weird that your string data is 240, 107, 107 since 240 doesn't correspond to an ascii character...so lets first make sure you can receive strings at all. Add this around your loop() section:
long lastStringMessageSent = millis();

loop()
{
  if( ( millis() - lastStringMessageSent ) > 1000 )
  {
    Firmata.sendString( "Ping from Arduino!" );
    lastStringMessageSent = millis();
  }

  //... (rest of loop)
}

This will send a "heartbeat" ping every 1 second with a string message. Once you get your app connected to the Arduino, you should see "Received string message from arduino: Ping from Arduino!" printed every 1 second.
If that works, add a Firmata.sendString call that is invoked when the sysexCallback is first called. If that works, but you still don't see the "Hello from Arduino" message coming through, then something may be wrong with the way ALL_PINS_COMMAND is defined.

Hello,
I wanted to confirm that I have similar issue - Firmata sending works for about a second, and then stops.
Amusingly, receiving data sent from Arduino to PC works ad perpetuum.

Pull request #92 seems to fix this. To work with the current version (1.3) you should add a frush() call after each sendSysex.

Closing based on above pull request


How to "save" Connection pid between queries?

I am writing backend storage for Erl db abstraction lib kvs.
There is start fun in kvs, that establish connection with mongoDB. How I can store connection, to re-use for future queries?
I understand that result of connection is PID of connection process, but what is next?
How mongodb-erlang suggest that external apps will use it? any recommendation?

mc_worker hold connection socket with database. So it can be started and stored.
As for me - most of the time I use poolboy with mc_worker workers.
But if you do not need a pool - just start mc_worker by hand (or with the help of mongo:connect) and store the result pid.
After connecting you can use mongo module's api.

and store the result pid.

as far a I got it's up to me where and how I will store connection PID. Am I right?

Yes, you are right.

Thanks


Add dinooliva and rghetia to code owners.

Adding more people for code reviews and maintenance.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@e24dd5e). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1777   +/-   ##
=========================================
  Coverage          ?   81.84%
  Complexity        ?     1977
=========================================
  Files             ?      291
  Lines             ?     9221
  Branches          ?      891
=========================================
  Hits              ?     7547
  Misses            ?     1380
  Partials          ?      294

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 e24dd5e...faa54eb. Read the comment docs.


web: Deal better with very long status names

Cosmetic stuff only for the web views. We have quite long Status names (and options hashes), and without this the Statuses list is almost unusable.
Greetings,
-ch

I think dealing with long status names is a good idea but your implementation seems very specific to your usecase so I cant pull it in.


Updated dependencies and unlocked cargo --bin target

Planned to use this broker for my home automation project but looks like some more work needs to be done.
Tested broker on macos with MQTTBox load tests and got connection errors:
15:51:10 [INFO] ☄   new tcp connection from <IP_ADDRESS>:59107
15:51:10 [INFO] ✨   mqtt connection successful. id = "49611e25-9b20-4b2b-b158-639c2ce109701520351460842"
15:51:10 [ERROR] network incoming handle error = InvalidMqttPacket
15:51:10 [ERROR] disconnecting client: "49611e25-9b20-4b2b-b158-639c2ce109701520351460842"
15:51:11 [INFO] ☄   new tcp connection from <IP_ADDRESS>:59108
15:51:11 [INFO] ✨   mqtt connection successful. id = "49611e25-9b20-4b2b-b158-639c2ce109701520351460786"
15:51:11 [ERROR] network incoming handle error = InvalidMqttPacket
15:51:11 [ERROR] disconnecting client: "49611e25-9b20-4b2b-b158-639c2ce109701520351460786"
15:51:11 [INFO] ☄   new tcp connection from <IP_ADDRESS>:59109
15:51:11 [INFO] ☄   new tcp connection from <IP_ADDRESS>:59110
15:51:11 [INFO] ✨   mqtt connection successful. id = "49611e25-9b20-4b2b-b158-639c2ce109701520351460784"
15:51:11 [INFO] ✨   mqtt connection successful. id = "49611e25-9b20-4b2b-b158-639c2ce109701520351460777"
15:51:11 [ERROR] network incoming handle error = InvalidMqttPacket
15:51:11 [ERROR] disconnecting client: "49611e25-9b20-4b2b-b158-639c2ce109701520351460784"
15:51:11 [ERROR] network incoming handle error = InvalidMqttPacket
15:51:11 [ERROR] disconnecting client: "49611e25-9b20-4b2b-b158-639c2ce109701520351460777"
15:51:11 [INFO] ☄   new tcp connection from <IP_ADDRESS>:59111
15:51:11 [INFO] ✨   mqtt connection successful. id = "49611e25-9b20-4b2b-b158-639c2ce109701520351460827"
15:51:11 [ERROR] network incoming handle error = InvalidMqttPacket
15:51:11 [ERROR] disconnecting client: "49611e25-9b20-4b2b-b158-639c2ce109701520351460827"
15:51:11 [INFO] ☄   new tcp connection from <IP_ADDRESS>:59112
15:51:11 [INFO] ✨   mqtt connection successful. id = "49611e25-9b20-4b2b-b158-639c2ce109701520351460842"
15:51:11 [ERROR] network incoming handle error = InvalidMqttPacket
15:51:11 [ERROR] disconnecting client: "49611e25-9b20-4b2b-b158-639c2ce109701520351460842"

@sashao Are you seeing those errors before your changes? Your changes fix the errors?

but looks like some more work needs to be done

Yeah. This used to work. I thought to keep this project on hold since I feel that I'm putting a lot of work in understanding tokio and dealing with huge hard to read errors. I think I'll resume this work once async/await is stable.

My changes are not fixing mentioned connection issues.
They where seen before updating dependencies and after that.


OpenRewrite JPMML rule

Related to kie-issues#56, after complete enablement of jakarta namespace there will be two versions of jpmml-model: javax one (1.5.1) and jakarta one (1.6.4).
Some code in drools repository (kie-pmml-trusty, kie-dmn) needs code modifications to adapt to different versions.
Regardless of final management decision, there will be the need to automatically convert from one version to the other.
Scope of this POC is to evaluate feasibility of automatic javax -> jakarta conversion (jpmml 1.5.1 -> 1.6.4), implementing an OpenRewrite recipe.
If the final decision would be to do the other way around, then the recipe would just need to be "inverted", otherwise it would be good as it is.

I thought about this a bit. Another option would be to extract the PMML modules to a separate repository. As far as I heard, not many users are using it. What do you think please? I mean instead of investing into maintenance component, moving it elsewhere and make it up to date if someone requests it.

The problem is not only for kie-pmml-trusty - also kie-dmn module uses directly jpmml-model. So, the problem will stay the same

Yes, but is anyone using this integration? Calling PMML from DMN.

Yes, this happen - I've been asked different times, in the last years, about that - just two days ago for the last time

The PR is done to the Tristan's repository - https://github.com/radtriste/drools/pull/28

Fixed by https://github.com/radtriste/drools/pull/32


Add make_pub_crate code action to ra_editor

implement #170

Does this handle items which are already pub in some capacity gracefully. Looking at the code, I'd guess not

Yep, I think ideally we should not make this intention available if there's already an existing visibility. To implement this, you'll need to get the FnDef, StructDef etc ancsetor of keyword and check if it has visibility.

@DJMcNab @matklad
Thanks for your reviewing.
I'll fix it in this week.

How does this handle e.g unsafe fn foo()? I would say rather than using previous sibling, you should get the parent declaration then see if it has a Visibility

@DJMcNab Thank you for pointing out my overlooking.
I've changed to check parent declaration. CC: @matklad

LGTM, thanks @h-michael !
bors r+


Implement staticColor prop for ActionButton and ToggleButton

Implements the new staticColor option for ActionButton and ToggleButton, which can be set to white or black. This is useful when the button is placed over a color background, and will be needed for ActionBar.
The implementation makes use of CSS vars to avoid duplicating all of the classes many times. In addition it uses the mix-blend-mode property to knock out the text in the selected version so that it becomes whatever color is behind the button automatically!
This also implements halo focus rings for emphasized toggle buttons.

O, would you mind running chromatic against it, and maybe adding some of the static ones to chromatic?


Stabilize new naming conventions

Idea

Files/Directories: PascalCase
Types/Classes: PascalCase
Variables: snake_case
Class (non-struct) Member Variables: snake_case_
Functions: camelCase
Class (non-struct) Methods: camelCase_

Reasoning/Explanation

Variables use snake_case since they tend to be shorter than functions.
Why not the m prefix?

We need to use m_ for snake_case and m for camelCase.
m_ and m are inconsistent.
m_snake_case is longer than snake_case_.

Class Members and non-members (and struct members) are distinguished by the _ suffix, which is similar to Google's C++ Coding Style.

The difference is that we apply this pattern to methods as well.

Only class members have the _ suffix because they have methods, and within methods, variables/functions and members are hard to be distinguished. (Structs won't have methods. => this is different from Google's)

Steps to apply this new policy

Apply Class vs Struct style.
Apply the new Class (non-struct) Methods naming convention.
Apply the new Class (non-struct) Member Variables naming convention.
Apply the new Variables naming convention.

See also

https://github.com/poac-dev/poac/blob/bca4bbde7c9eaea9245e53807d49c322583bf187/CONTRIBUTING.md#naming-conventions-under-construction
https://github.com/poac-dev/poac/pull/1035#discussion_r1843078361
https://llvm.org/docs/CodingStandards.html#name-types-functions-variables-and-enumerators-properly
https://llvm.org/docs/Proposals/VariableNames.html

This naming convention can be problematic when we want to refer to a member variable via methods:
class A {
    int some_thing_;

public:
    int someThing_(); // ok, but depending on the variable name, it might be difficult to read the connection?
                      // Also, somewhat annoying when we want to grep the original variable?
    int getSome_thing_(); // violates camelCase_
    int get_some_thing_(); // violates camelCase_


Update ELM to STU3

CQL STU3 makes several changes to ELM. Incorporate these changes in the model info tooling and the translator.
See STU comments:

1483
1500
1580

Included in the 1.3 CQL Ballot release.


Disable dependabot labels

No changes needing a change description found.

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


CI: Remove experimental tag from Python 3.11

Remove the continue-on-error setting from the GitHub Actions CI for Python 3.11. The aiohttp dependency now has Python 3.11 wheels available, on which the CI previously failed.
Also updates the used actions, checkout and setup-python, to their latest versions.

Hi, sorry but I'm going to decline this PR, because I have already made the 3.11 build mandatory in 9c10841


Add /success-stories

h/t to Michael Thorne! cc @hollomancer

Whoa, it turns out successes already existed. Totally forgot about it: https://operationcode.org/successes.

Poses a problem and breaks slightly.

This commit fixes this.


Optimize Hand / Hand Order

Description of the bug
I think this is a bug. I noticed that multipliers in hand in "any" order don't cause the score to change.
Steps To Reproduce
https://efhiii.github.io/balatro-calculator/?h=YADSFyFGJAAVyYADpzQAFSJAAtNColgIwU0EQHAcAgADgACgAFAACgAF
Expected behavior
Moving glass card to the right/left of polychrome cards - shouldn't that change the score? It doesn't. However, the score itself IS the optimized score. It just doesn't show the hand in the order it's supposed to.

No. multiplication is commutative.  Duh, that does make sense. My fault.


yuzu: 1557 -> 1569, yuzu-ea: 3864 -> 3897

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

The perf uplift on Steam Deck seems to be pretty noticeable, and the frametimes are a lot more consistent too.


Scheduler treats services with no selector as matching every pod

(What it actually means is that they have user-provided endpoints and should match no pods.)
GetPodServices in cache/listers.go is untested and gets this wrong. Noticed while working on #6518.
The severity of this bug is low, it just means scheduler will attempt to spread all pods.

That is, a nil selector = no pods; an empty selector = all pods.


XhrIo Progress Events

Commit cbed1691c558fe35aa533fc6a1e0b647fb426fb9 added support for progress events in XhrIO, then 2d963940fc0b8f6beca6f3554b4b00d1eca14e9b reverted that change.
Is there any plan to reintroduce these changes?
Progress events would be very nice to have. Is there a better alternative?

Had some trouble reverting the rollback internally. The blockers have been removed and we're going to try to get this change in next week. Stay tuned.

@joeltine can you reference this issue in the change when it drops? (Or put another way, I'd like a way for github to notify me when this drops so I can encourage clojurescript authors to depend on a later version of google closure library) :)

Still more blockers on this internally :(. It's being worked on though. May take longer than we thought.

Progress events are now supported as of https://github.com/google/closure-library/commit/42162f3d5ccbb2f59e3c8a9780ec2924e919dd91

Had to rollback this one twice internally, but I think we finally got it to stick with https://github.com/google/closure-library/commit/1e0c8103ae97a0e568e63bf5d6906597b25a4544

Thanks so much @joeltine  :)


kubeapi using a lot of memory after rc upgrade and downgrade

What kind of request is this (question/bug/enhancement/feature request):
Hello, after trying to upgrade Rancher from 2.5.3 to 2.5.4-rc4 to test some new features, my kubeapi pod is now using an insane amount of memory to the point of making the server swap. I must admit I upgraded the wrong way by just bumping the rancher image version but I reverted to the last stable version quickly after.
Steps to reproduce (least amount of steps as possible):
Change the rancher image tag to 2.5.3 to 2.5.4-rc4 and then back again.
Result:
Apiserver now consume almost 21g of ram, without erroring. Here is the output of top :
    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
  16649 root      20   0   28.0g  21.0g  22664 S 120.5  66.9  95:04.66 kube-apiserver

root       16649  259 73.3 29372576 24154020 ?   Ssl  16:28 110:41 kube-apiserver --requestheader-username-headers=X-Remote-User --requestheader-extra-headers-prefix=X-Remote-Extra- --audit-log-format=json --audit-policy-file=/etc/kubernetes/audit-policy.yaml --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --audit-log-path=/var/log/kube-audit/audit-log.json --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --etcd-servers=https://<IP_ADDRESS>:2379 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --authentication-token-webhook-config-file=/etc/kubernetes/kube-api-authn-webhook.yaml --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy --service-account-lookup=true --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --service-node-port-range=30000-32767 --runtime-config=policy/v1beta1/podsecuritypolicy=true --allow-privileged=true --profiling=false --authorization-mode=Node,RBAC --audit-log-maxbackup=10 --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --audit-log-maxage=30 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --bind-address=<IP_ADDRESS> --secure-port=6443 --cloud-provider= --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --authentication-token-webhook-cache-ttl=5s --anonymous-auth=false --audit-log-maxsize=100 --requestheader-allowed-names=kube-apiserver-proxy-client --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --service-cluster-ip-range=<IP_ADDRESS>/16 --storage-backend=etcd3 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --requestheader-group-headers=X-Remote-Group --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --etcd-prefix=/registry --advertise-address=<IP_ADDRESS>

Other details that may be helpful:
Here are some logs from the apiserver :
E1215 16:32:00.768425       1 writers.go:105] apiserver was unable to write a JSON response: http: Handler timeout
E1215 16:32:00.768464       1 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"http: Handler timeout"}
E1215 16:32:00.770349       1 writers.go:118] apiserver was unable to write a fallback JSON response: http: Handler timeout
I1215 16:32:00.771563       1 trace.go:116] Trace[341323014]: "List" url:/apis/project.cattle.io/v3/namespaces/p-6d96k/apprevisions,user-agent:rancher/v0.0.0 (linux/amd64) kubernetes/$Format,client:<IP_ADDRESS> (started: 2020-12-15 16:30:26.808342778 +0000 UTC m=+610.711367561) (total time: 1m33.963166189s):
Trace[341323014]: [1m33.958388977s] [1m33.958288719s] Listing from storage done
E1215 16:32:29.501052       1 writers.go:105] apiserver was unable to write a JSON response: http: Handler timeout
E1215 16:32:29.501501       1 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"http: Handler timeout"}
E1215 16:32:29.503388       1 writers.go:118] apiserver was unable to write a fallback JSON response: http: Handler timeout
I1215 16:32:29.505927       1 trace.go:116] Trace[1957932699]: "List" url:/apis/project.cattle.io/v3/namespaces/p-6d96k/apprevisions,user-agent:rancher/v0.0.0 (linux/amd64) kubernetes/$Format,client:<IP_ADDRESS> (started: 2020-12-15 16:30:27.158635375 +0000 UTC m=+611.061660158) (total time: 2m2.347153381s):
Trace[1957932699]: [1m30.700387271s] [1m30.700258424s] Listing from storage done
Trace[1957932699]: [2m2.347147984s] [31.646760713s] Writing http response done count:40314
I1215 16:32:31.501421       1 trace.go:116] Trace[1350214230]: "Delete" url:/apis/management.cattle.io/v3/namespaces/c-pw82h/clusterscans (started: 2020-12-15 16:32:30.393008848 +0000 UTC m=+734.296033653) (total time: 1.108335826s):
Trace[1350214230]: [1.108335826s] [1.108335826s] END
I1215 16:32:52.662667       1 trace.go:116] Trace[1741135867]: "List etcd3" key:/project.cattle.io/apprevisions/p-6d96k,resourceVersion:,limit:0,continue: (started: 2020-12-15 16:31:27.245284603 +0000 UTC m=+671.148309404) (total time: 1m25.417336394s):
Trace[1741135867]: [1m25.417336394s] [1m25.417336394s] END
I1215 16:32:55.270235       1 trace.go:116] Trace[860992201]: "List etcd3" key:/project.cattle.io/apprevisions/p-6d96k,resourceVersion:,limit:0,continue: (started: 2020-12-15 16:31:27.244741401 +0000 UTC m=+671.147766188) (total time: 1m28.025442219s):
Trace[860992201]: [1m28.025442219s] [1m28.025442219s] END
E1215 16:32:55.270645       1 writers.go:105] apiserver was unable to write a JSON response: http: Handler timeout
E1215 16:32:55.270675       1 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"http: Handler timeout"}
E1215 16:32:55.272007       1 writers.go:118] apiserver was unable to write a fallback JSON response: http: Handler timeout
I1215 16:32:55.273095       1 trace.go:116] Trace[491962487]: "List" url:/apis/project.cattle.io/v3/namespaces/p-6d96k/apprevisions,user-agent:rancher/v0.0.0 (linux/amd64) kubernetes/$Format,client:<IP_ADDRESS> (started: 2020-12-15 16:31:27.244611362 +0000 UTC m=+671.147636147) (total time: 1m28.028388454s):
Trace[491962487]: [1m28.025689036s] [1m28.025574496s] Listing from storage done
I1215 16:32:58.131720       1 trace.go:116] Trace[1058721744]: "List etcd3" key:/project.cattle.io/apprevisions/p-6d96k,resourceVersion:,limit:0,continue: (started: 2020-12-15 16:31:26.814834292 +0000 UTC m=+670.717859262) (total time: 1m31.316809788s):
Trace[1058721744]: [1m31.316809788s] [1m31.316809788s] END
E1215 16:32:58.134110       1 writers.go:105] apiserver was unable to write a JSON response: http: Handler timeout
E1215 16:32:58.134155       1 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"http: Handler timeout"}
E1215 16:32:58.154535       1 writers.go:118] apiserver was unable to write a fallback JSON response: http: Handler timeout
I1215 16:32:58.155928       1 trace.go:116] Trace[1113098809]: "List" url:/apis/project.cattle.io/v3/namespaces/p-6d96k/apprevisions,user-agent:rancher/v0.0.0 (linux/amd64) kubernetes/$Format,client:<IP_ADDRESS> (started: 2020-12-15 16:31:26.814596541 +0000 UTC m=+670.717621370) (total time: 1m31.341205461s):
Trace[1113098809]: [1m31.317290641s] [1m31.31710342s] Listing from storage done

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.5.3
Installation option (single install/HA): single install

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Hosted
Machine type (cloud/VM/metal) and specifications (CPU/memory): Quad-Core AMD Opteron(tm) Processor 2376 / 32Gb
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.4", GitCommit:"d360454c9bcd1634cf4cc52d1867af5491dc9c5f", GitTreeState:"archive", BuildDate:"2020-11-25T13:19:56Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:43:34Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client:
 Version:           19.03.13-ce
 API version:       1.40
 Go version:        go1.15.2
 Git commit:        4484c46d9d
 Built:             Sat Sep 26 12:04:46 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          19.03.13-ce
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.15.2
  Git commit:       4484c46d9d
  Built:            Sat Sep 26 12:03:35 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.4.3
  GitCommit:        269548fa27e0089a8b8278fc4fc781d7f65a939b.m
 runc:
  Version:          1.0.0-rc92
  GitCommit:        ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Soved, the old monitoring was stuch in the "deleting" state for some reason. I delete the finalizer and force deleted the app. RAM usage of API server has fallen from 30Go+ to a more reasonable 6Go.


Disagreement in contamination estimations with/without raw data

Hi team at Celda,
I am processing some scRNA data through decontX as part of my QC pipeline and have a quick query about the inclusion of raw data.
I have run the same data through decontX with and without specifying the raw data and get drastically different contamination estimates.
Attached is an image of the same cells being compared against each other regarding their contamination estimates (x-axis is with the raw data included and y-axis is without raw data)
with_without_raw_decontX.pdf
As you can see, this figure makes it tricky to define a contamination cut-off from which to retain my cells i.e. cells satisfying a 0.3 or lower threshold (without raw considered) may have a high contamination estimate when the raw is considered.
This is a HTO-dataset where there are 4 samples contained within; could this have play a role into the effect I am seeing here? If so, would you recommend me demultiplexing the 4 samples first (most likely at the fastq level so that I can re-run through cell ranger and generate filtered and raw directories) and running decontX on each one separately?

Hi @dlee598, thanks for trying out or tool! Here are a few questions and thoughts:

Did you do any sorting (FACS or bead based) on your samples before loading into the 10X. If cell populations were excluded, they may not be present in the filtered matrix but their ambient material may still be present in the raw matrix droplets. So that could be a reason why you are seeing discrepancies.

It is also a bit strange that you don't get any cells with zero or low contamination by either method.  Note that you can supply your own cell type labels to decontX if the heuristic decontX clustering method does not capture all the cell types you want.

Are you trying to decontaminate the HTO/cite-seq data or the RNA data?

You should probably do the demultiplexing after alignment and running CellRanger so UMIs can be appropriately handled. Each cell should have a relatively higher level of an HTO ADT. Seurat has a good tutorial for demultiplexing HTOs.

Lastly, I am going to move this to a Discussion thread as I am not sure it is an issue with the code itself.


Add support for Ubuntu 64-bit

This means that you can add your ssh public key to the file which saves you some time by not having to copy and putting it in the .ssh directory of a freshly installed RPi.

On 23 Aug 2021, at 15:31, Alexander Golubev @.***> wrote:
@agolubev commented on this pull request.
In akka-pi-os-dhcp-32.yml https://github.com/lightbend/Pi-Akka-Cluster/pull/166#discussion_r693974303:

 plain_text_passwd: akkapi

ssh-authorized-keys: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDkrgM1almJcqu6FaKDrscUVghlJOO6m7wayVnmH0bQEv4uQQ9SZmkCegrGJ63iMI8X0xUShkwYLippePpj0RiucL1e9/FtzqSdu6IHaPFJg7w5G6cEV2c1mvyJRHpi86+Yt3t4z67aSw77uAWkNFKShtSEbePfF5WX/LGknxRND6f3db+SmmOSy5w5qgC4GmG31gnJX6j7s0xWRiMicyYdGzKOKB4VkQi2YY7bj7hwri4EUHgIZlYuxST57L68CyTVwnF8c39dK6xflea4fkn+3TlNakFw0rrP3iqy8bkaU2cHnMyWIsYF4fbec1JnKngtIGiungvV9QTJzTpMF7ufEFiYl2uzCZgZGhmXsFDo9WoMjKHTJcbM0cm2OWWOrllOGdY2V580szaJR293jQx0OvNhxA3kTAe1aNmpBOfWhhjxxQsPCaPeHTdNG2L3iN9gYT8mms84ENO7OSUYsiMYMas9EMybyYY3Mvd4NUruIxlRgT84kpgyecC/8iQJwvI7vkdZRLlzQ0B614VCA3RH27ZULODSCPz2oFHFfHrMvdxGa4FTYJCWQFBAltWuPjQ8wmNdnKWX85jlc9MPlJ5WK8VIC1f5hVJd6qjSt009WNEt/y6h9xb5qixgZmBRkGpNe/2fyzx1sn0gyVm90wQXDSoT1fWhxZKJciPuHMvYcw== @.***
Does this mean we need to import another piece of keys for a local user to be able to log in? Meaning we don't need to generate key with https://github.com/lightbend/Pi-Akka-Cluster/blob/master/docs/Hypriot-OS-Course-Preparation-Instructions.md#configure-password-less-login https://github.com/lightbend/Pi-Akka-Cluster/blob/master/docs/Hypriot-OS-Course-Preparation-Instructions.md#configure-password-less-login ?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/lightbend/Pi-Akka-Cluster/pull/166#pullrequestreview-736126069, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVNB7ARYH2MAM3SUNRB2ADT6JEUNANCNFSM5CKER4SQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67794

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67799

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/90935

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107308


[WIP] Container ssa annotate success

Fixes https://github.com/ManageIQ/manageiq/issues/15013

@miq-bot assign enoodle

@moolitayer can you review this?
@enoodle what does it take to finalize this?

I think compliancy cannot change from this point of view, since we only annotate openshift images, so that's fine:
https://github.com/ManageIQ/manageiq/pull/15031/files#diff-b65b69c5edaddcf64ef4a666f394489eL746

we only annotate openshift images

Technically that doesn't matter because other scanning tools have the same privilege to the cluster and may annotate all images in any namespace. We'll deal with this later once this PR is merged, but I wanted to clarify.

My main problem with this PR is that it is not working currently.. I must have not defined something important for the policy. @moolitayer @cben if you could take a look and maybe give me a hint it would be nice. Also, is there a point of contact in ManageIQ for policies that we could ask for advice?

What happens when you call the action method directly, does it work?
I can probably help with the policy, also take a look at log/policy.log

This is now successfully annotating compliant images and also adds the quality summary from https://github.com/ManageIQ/manageiq/issues/15212
This is still WIP becuase I need to understand how to map the severity levels critical, important, moderate, low to the ones returned from OpenSCAP High, Medium, Low. Any advice?

Is there a documentation for what the logic is behind High, Medium, Low ?
@isimluk can you please remind me who is our contact for OpenSCAP

can you please remind me who is our contact for OpenSCAP?

@mpreisler

documentation for what the logic is behind High, Medium, Low ?

This is a good question. I missed that this mapping is happening. I don't see why we don't just pass the results through to the MIQ user unless we are trying to simplify (3 states vs 4?). But any interpretation we do moves us away from an "OpenSCAP provider" to an "MIQ provider (fed by OpenSCAP results)".
Any change here would break backwards compatibility with the policy. Workaround would be to carry logic "critical OR high" in the policy.

@aweiteka

I missed that this mapping is happening.

I missed it too, Sorry.
Do you agree to {"Low" => "low", "Medium" => "moderate", "High" => "critical"} mapping? We have to skip one state, because we are coming out of the 3-state OpenSCAP results, and I feel like everything might be considered "important" if your definition of important is wide enough.

The severity is not coming from @OpenSCAP but from the NIST XCCDF specification. There are actually 5 possible states. See https://scap.nist.gov/specifications/xccdf/xccdf_element_dictionary.html#severityEnumType
Could we just use this as it is?

@mpreisler We need to send it as detailed here: https://github.com/adellape/openshift-docs/blob/master/security/container_content.adoc#container-content-scanning
I will use your link to make a 1-1 map of those 5 seventies that both have. Thank you.

@aweiteka @moolitayer Can you please take another look?

I will update this when https://github.com/ManageIQ/manageiq-providers-openshift/pull/23 is merged because some functions should be moved to the Openshift::ContainerManager::ContainerImage class.

@moolitayer @simon3z Can you take another look at this?

@gtanzillo Can you review this please? It can be changed with respect to https://github.com/ManageIQ/manageiq/pull/16213 if needed.

@aweiteka Please take a look

ping @Fryguy @agrare  can you please take a look?
@miq-bot add_label bug gaprindashvili/yes

@miq-bot add_label gaprindashvili/yes bug

@enoodle the bot was missing a comma

What release is this planned for? Any instructions how to port it back to old version of CF?

@mjudeikis It is aimed for gaprindashvili. As for backports, because it is based on https://github.com/ManageIQ/manageiq-providers-openshift/pull/41 which itself is based on other gaprindashvili PRs since the repositories split, backporting will not be trivial.

@enoodle Is this replacing action_container_image_annotate_deny_execution with action_container_image_annotate_scan_results?

@chessbyte Yes, it is based on a change in
https://github.com/ManageIQ/manageiq-providers-openshift/pull/41

@gtanzillo who can take a look

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1458678

@gtanzillo I updated the miqAction tests that were effected by this, but couldn't find any tests for miq_policy_sets.yml , do you know of any?

:tada:

Gaprindashvili backport details:
$ git log -1
commit 3ec3b2e1852e8a7883a96eaeb6607e1d158bc3f6
Author: Gregg Tanzillo<EMAIL_ADDRESS>Date:   Mon Nov 20 09:24:08 2017 -0500

    Merge pull request #15031 from enoodle/container_ssa_annotate_success

    Container ssa annotate success
    (cherry picked from commit 9835af3b3e53525a3dbb6745b4718866890edd4f)

    https://bugzilla.redhat.com/show_bug.cgi?id=1515438


feat:adding a web assembly playground for the examples

Updated the Miden Assembly Playground from here to accept inputs (stack_init and advice_tape) and to work with all our initial examples.

Thank so much for your review @grjte. The two non-working examples should work when we rabase and merge.

One other comment: I wonder whether rather than putting the playground into the root of the repo it should go into something like /wasm-playground (or just /playground) directory. This would enable us to add other things in the future (e.g., CLI mentioned in #9). Maybe the structure of the repo could be something like:
├─ bench-cli
├─ examples
└─ playground

What do you guys think?

Thanks @bobbinth !
I think it makes sense. Maybe we can merge this PR as is and I open a issue to change the structure and add the CLI?

One other comment: I wonder whether rather than putting the playground into the root of the repo it should go into something like /wasm-playground (or just /playground) directory.

I agree with the structure suggestion too, but I think it's ok to merge this once the small points are addressed so there's something to show for the discussion today. Please update here with the issue link for restructure + CLI once you've created it @Dominik1999

Thanks @grjte
here is the issue for changing the repo structure: https://github.com/0xPolygonMiden/examples/issues/11


Handling void by nullish coalescing operator

TypeScript Version:  4.0.2
Search Terms: nullish coalescing, void
Code
type PossiblyVoid = () => void | boolean;
let empty : PossiblyVoid = () => { }
let coalesced : boolean = empty() ?? true;

Expected behavior:
Should not throw a compilation error
Actual behavior:
Nullish-coalescing operator does not treat void variables as undefined, even though in JS a function that does not return anything is the same as the one returning undefined.
I am not entirely sure this is a bug, but intuitively it feels like is should behave in a different way. If not, could you please shed some light on the reasons behind it?
Playground Link:
https://www.typescriptlang.org/play?ts=4.0.2#code/C4TwDgpgBACg9gZwQSwEYBsQDU7ICZQC8UAFAJREB8UAbrgQD5SpxzoQCGAdgNwBQ7YFAgBbMKCgAuWIhQZs9IqQqFqAbygBfARCEBjOB3YI9EAtJZtOXJaPEhyUAPxOowAE4BXCPyA

This is working as intended (see #26234). Imagine:
ffunction func(): any {
    const d = Math.random();
    if (d < 0.25)
        return 1;
    if (d < 0.5)
        return "-";
    if (d < 0.75)
        return { a: 1};
    return 0;
}

type PossiblyVoid = () => void | boolean;
let empty : PossiblyVoid = func;
let coalesced : boolean = empty() ?? true;

Playground.
The declared func is assignable to PossiblyVoid type but the real value of coalesced will be 1 | "-" | { a: 1} | 0 instead of a boolean.

Expanding on what @j-oliveras said:
A function returning void doesn't mean it returns nothing, but it returns something that should not be used for anything.
If you intend to have a "nothing" value you should use undefined.

All right, I get it now.
The problem I have with () => undefined is that a function must have an explicit return statement, so a function like function fn() : undefned {} does not compile (even though JS adds an automatic return undefined to it.

Actually, I found an issue that describes this: #36288

A function returning void doesn't mean it returns nothing, but it returns something that should not be used for anything.

In that case, how come the ternary and or operators work?
function func(): any {
    const d = Math.random();
    if (d < 0.25)
        return 1;
    if (d < 0.5)
        return "-";
    if (d < 0.75)
        return { a: 1};
    return 0;
}

type PossiblyVoid = () => void | boolean;
let empty : PossiblyVoid = func;
const emptyReturn = empty();
let nullishCoalesced : boolean = emptyReturn ?? true;  // error
let orCoalesced : boolean = emptyReturn || true;  // ok
let ternaryCoalesced: boolean = emptyReturn ? emptyReturn : true;  // ok

Playground

Expanding on what @j-oliveras said:
A function returning void doesn't mean it returns nothing, but it returns something that should not be used for anything.
If you intend to have a "nothing" value you should use undefined.

Theoretically true, but actually writing a void-returning function that has any value other than undefined is tricky.
function testOne(): void {
  return 1; // type 'number' is not assignable to type 'void'
}

function testTwo(): void {
  console.log('void');
} // returns 'undefined'

function testThree(): void {
  return undefined;
} // returns 'undefined'

function testFour(): void {
  return;
} // returns 'undefined'

function testFive(): boolean | void {
  return;
}

function testSix(): boolean | void {
  return true;
}

function testSeven(): boolean | void {
  return 1; // type '1' is not assignable to type 'boolean | void'
}

The only way I can figure out to make it happen is:
function test(cb: () => any): void {
  return cb();
}

function callback(): boolean {
  return true;
}

test(callback);

But since we disallow any, it can't actually happen for us. The example works with any but not with unknown or never.
If you disallow any, is there any scenario where void != undefined?

@jdforsythe

The only way I can figure out to make it happen is: [...] This just kind of disables the type check, and since we disallow any, it can't actually happen for us. The example works with any but not with unknown or never.

The example works with void: function test(cb: () => void): void { return cb(); }

We use an explicit | void for certain functions to force developers to handle the undefined scenario.

Frankly, then you're abusing void. If you want to force the developers to handle the undefined scenario, then use undefined. void does not mean undefined. In a way void is the same as any, at least when it comes to possible values to deal with.

@MartinJohns
Indeed, we are abusing void, however using type undefined does not provide any benefit.
function isPositive(input: number): true | undefined {
  if (input < 1) {
    return undefined;
  }

  return true;
}

// val is type `true`
const val = isPositive(-1);

Adding the | undefined doesn't change anything about the types. There's no warning that val might be undefined, and in essence any type T is T | undefined
const bool: true = undefined;

There's some inconsistency in the behavior for void. It seems TypeScript only has a problem testing for truthiness if the type is simply void but not if it's unioned with another type. In fact, it can be completely wrong.
const maybeVoid = (): void | number => Math.random() < 0.5 ? alwaysVoid(callback) : 0;

const alwaysVoid = (cb: () => void): void => cb();
const callback = (): boolean => true;

function try1() {
  const rec = alwaysVoid(callback);

  if (!rec) { // An expression of type 'void' cannot be tested for truthiness
    return;
  }
}

function try2() {
  const rec: number | void = maybeVoid();

  if (!rec) {
    console.log('number | void, but actually can only be number here', rec);

    return;
  }

  console.log('number, but actually can only be void here', rec);
}

In try2 TypeScript has no problem checking truthiness of !rec even though it could be void, and in this case gets it exactly backwards. Inside the if block, it types rec as number | void even though it could only be a number (0) there, and after the if it types rec as number even though it can only be void (true).

Adding the | undefined doesn't change anything about the types. There's no warning that val might be undefined, and in essence any type T is T | undefined

It makes a difference if you enable strictNullChecks, a feature existing since TypeScript 2.0 (released in 2016).


end to end testing of react-native-svg components using testID

I don't see much mention of testing and it looks like testID, supported by react-native components, is not used as a prop. I'm looking in to implementing this. Are others doing so or is there an existing open issue that addresses the testing of react-native-svg components?

@phosphene I would love to have any kind of testing available, your contributions would be more than welcome! ❤Ideally we would run tests with most of the files from https://github.com/web-platform-tests/wpt/tree/master/svg on each commit. A bit more info:
https://github.com/w3c/svgwg/wiki/Testing

Great. The first order of business for end to end testing is to either add the testID prop to react-native-svg components or to add a  "one-off prop pass-through" for testID. Or we can pass "the entire props through". The second option "is more extensible for any future props that are desired" but could open us to other issues.
I'm having trouble right now passing through testID. I can investigate what the issue is with that. Or perhaps you see the solution/issue right away?
testID is supported core react-native components.
https://facebook.github.io/react-native/docs/view#testid
https://github.com/peacechen/react-native-modal-selector/pull/48

To clarify. Here is another project that implemented prop pass through, so this pull request may serve as an example.
https://github.com/peacechen/react-native-modal-selector/pull/48

Hey there. I'm sorry to say I've been engaged in other work.
On Sat, Dec 8, 2018, 8:26 PM Mikael Sand<EMAIL_ADDRESS>wrote:

@phosphene https://github.com/phosphene Any progress on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/react-native-community/react-native-svg/issues/776#issuecomment-445510244,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALwff5q2dOlNNas3NTRsf9p7_BEVwi1ks5u3JD2gaJpZM4WlubQ
.

Alright, no worries. Anyway, would be great to get some regression tests, and perhaps even compare against the reference images used by firefox and chrome etc. If anyone is interested, already investigating other react-native modules how they do testing of their iOS and Android native code and documenting it here would be great. Then there would be a clear path forwards as soon as someone has time to look at this.
I guess the expo and react-native codebases might be the main ones to look at. But, at least hopefully, someone knows about some well tested native module and can suggest/link to it here. Ideally something showing a ci setup running unit, integration and acceptance tests for native code in both android and ios. And if someone knows about a provider who gives this for free to open-source projects, that would certainly simplify things, alternatively perhaps someone could sponsor it? I would assume this library has provided its fair share of value to various native app stakeholders. I wonder what it would take to get them to provide even a bit monetary compensation for more stability and reliability in a relatively critical component. Especially when it would go straight to running costs of providing automated testing.

I tried setting up some end-to-end tests here in case you're interested: https://github.com/msand/react-native-svg-e2e

thanks! I will check it out.
On Sat, Mar 2, 2019 at 9:33 PM Mikael Sand<EMAIL_ADDRESS>wrote:

I tried setting up some end-to-end tests here in case you're interested:
https://github.com/msand/react-native-svg-e2e
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/react-native-community/react-native-svg/issues/776#issuecomment-468990792,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALwfTPGBKR7nAuXTeJGL50Wx7hOc32rks5vS162gaJpZM4WlubQ
.

Having a bit of trouble getting e2e test to work on android in travis-ci and bitrise. Works fine locally on both android and ios. And, now I think I found a workaround for travis at least: https://travis-ci.org/msand/react-native-svg-e2e/builds/501950972
But haven't got android tests to work on bitrise a single time yet. Also opened an issue in the detox repo: https://github.com/wix/Detox/issues/1194

Interesting.
On Tue, Mar 5, 2019 at 10:42 AM Mikael Sand<EMAIL_ADDRESS>wrote:

Having a bit of trouble getting e2e test to work on android in travis-ci
and bitrise. Works fine locally on both android and ios. And, now I think I
found a workaround for travis at least:
https://travis-ci.org/msand/react-native-svg-e2e/builds/501950972
But haven't got android tests to work on bitrise a single time yet. Also
opened an issue in the detox repo: wix/Detox#1194
https://github.com/wix/Detox/issues/1194
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/react-native-community/react-native-svg/issues/776#issuecomment-469802175,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALwfVPTCj-SbsXvECza4cazuBfARzK4ks5vTrqygaJpZM4WlubQ
.

Managed to get x86 and x86_64 android images running on travis using the latest android emulator canary, which now works in headless mode without hardware acceleration / kvm support: https://travis-ci.org/msand/test_emulators/builds/502382369

Got android working on bitrise now as well: https://app.bitrise.io/build/c31c1a40907cd137

Hi, I think that i'm looking to do what @phosphene was looking to do. here with Appium, so testID is good for ios but i guess accesibilityLabel would fit on android. properties that exist on RN Views or TouchableOpacities, but not on the native SVG elements. Any hint on how to achieve a good extension? i see that there are mixins with Touchable all around, could this be used to help?

ok. so ios side is not too difficult:
https://github.com/galkahana/react-native-svg/tree/feature/add-appium-detox-testID-support
but on android these are not even views...it's a canvas. wonder how i can orchestrate things like contentDescription and viewTag to match RN interpretations of testID and accessibilityLabel

Did the android part as well.
PR is here - https://github.com/react-native-community/react-native-svg/pull/1359
Hopefully i got the invalidation part right. not sure it's required in this case, would love a note on this. I mean i'm sure it's not harmful, but not sure if actually required.

Created a new PR to extend the previous one - https://github.com/react-native-community/react-native-svg/pull/1372
This one takes care of something that was problematic when using svg elements on android in appium. you couldn't interact or see the elements in appium desktop or secript.
The PR sets the right accessibility values to correct this.


Update README.md

Partially addresses https://jira.cfops.it/browse/PCX-1934.

Not really sure why it canceled your review, but updated the wording.
Could you merge when you have a chance?

yeah I guess it does it so that the new commits have to be reviewed. merging


Weird behaivor on highlighting

Sometimes this happens

When open a blade file happens, also when you use autocomplete with tags like @if
It breaks the highlight of opening/ending tags, those html are outer of any blade directive
Sometimes when you close and reopen the file, it starts working again
other times it starts working again after change something(like adding an space)

Also when i use autocomplete, it automatically reformat indentation of other blade tags on the same file

Hi,
I think there are some issues on htnl embedding, this might be a bit difficult to fix. I think similar highlight errors can appear when you include html code in raw php file. I will have to see if there are some tricks for this.
The indentation is also a issue yet to be solved.
I will keep you in touch when I progress on this part.

Also on select opening tag it highlight closing tag

But selecting closing tag doesn't highlight opening tag

Also on select opening tag it highlight closing tag
But selecting closing tag doesn't highlight opening tag

Also happens with @can and @canany

same for
@verbatim
@endverbatim

@unless (Auth::check())
@endunless

@isset($records)
@endisset

@empty($records)
@endempty

@auth
@endauth

@guest
@endguest

@while (true)
@endwhile

@forelse ($users as $user)
@empty
@endforelse


feat(backend): Add locked property to User object in SDK

Description

Adds a locked property to the User class in the SDK.

Checklist

[x] npm test runs as expected.
[x] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[x] (If applicable) Documentation has been updated

(clerk-docs PR #1280)

Type of change

[ ] 🐛 Bug fix
[x] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Hey @iamjameswalters thanks for the contribution, could you rebase from latest main ?

Hey @iamjameswalters thanks for the contribution, could you rebase from latest main ?

Sure, I've rebased!


set kernel type for imported notebooks

Imported .ipynb files are automatically started with a IPython 3 kernel. Sometimes this should be IPython 2. Allow the user to select which type of kernel their .ipynb should be run with.

To be clear, I mean before the notebook is open... Not using Toolbar --> Kernel --> Change Kernel

JupyterHub is not involved in loading notebooks, that is handled by the single-user IPython server. Notebooks written with IPython 3 store the kernel in their metadata, and will load the appropriate kernel. Notebooks written with IPython 2 or earlier will start with the server's default kernel. This, too, is configurable via KernelManager.default_kernel_name if you want to change the default to Python 2 for your own environment.

Thank you, can you tell me how to set this in IPython 3?


CMake flow - automate registering of .conf tests with CTest

Add cmake script to automatically pick up .conf file for every module.
Conf file names should be:

<module_name>*.conf - for test-to-pass tests
ttf_<module_name>*.conf - for test-to-fail tests
<module_name>_<test_group>*.conf - for TTP tests belonging to a particular test group
ttf_<module_name>_<test_group>*.conf - for TTF tests belonging to a particular test group

Implementation merged in #366


[PE-D] Adding a new person disallowed

Adding a new person weird090II that does not exist in the list, but there was an error message showing it already exist.

Labels: severity.High type.FeatureFlaw
original: gigituang/ped#2

To update UG on unique person condition

To update UG on unique person condition

Specifically to mention that the phone number and name needs to be unique.


Fix uninitialized member in TestRegistry

Fixes #545.

fixed by https://github.com/philsquared/Catch/commit/2b688e1cef85025ed71a0dc885118bb2318c21a0

Sorry - I hadn't spotted this PR before.
I fixed it a slightly different way, anyway.


Periodic CPU load within Tomcat when JRI running

The Tomcat service process generates high CPU load every 10 seconds (for about 1-2 seconds) whenever JasperReportsIntegration is active (Running=true). This originates from periodically reloading all jar-Files under
"...JasperReportsIntegration\WEB-INF\lib"
due to your setting Reloadable="true" in
"...JasperReportsIntegration\META-INF\context.xml"
Please provide an improved context.xml as an installation default file. Nevertheless JRI is a great tool!
Regards
Peter

Hi Peter, thanks for investigating this one with me. It is not really a bug but creates way too much work on the Tomcat.
I have fixed this and will include it into the next release of JRI.

Just to properly document the issue. The spike was due to Tomcat re-scanning all *.jar files in the JasperReportsIntegration.war/WEB-INF/lib directory. This was due to the parameter reloadable="true" in the <Context definition.
This has been fixed in the context.xml file.


feat(contract): add extra Multicall helper methods

Motivation

Multicall has some extra helper methods such as getBlockHash or getBlockNumber.
Solution
Add these methods to Multicall in the same style of the already present eth_balance_of. Decided against adding the allow_failure param on most of these helper calls as they are base opcodes included in all EVM implementations (except BASEFEE) so they shouldn't fail if we're using the base Multicall contract.
Also did some small docs changes and refactoring.

PR Checklist

[x] Added Tests
[x] Added Documentation
[x] Updated the changelog

reasonable, lgtm
but should we prefix these calls with add_?

Makes sense, following add_call, but changing eth_balance_of would be a breaking change


Update MD file on new branch 2017-00-02_16-11-06

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTest.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[#1576] Fixes unexpected premature close on chunked responses

Purpose
Fixes #1576 (unexpected premature close errors on chunked responses)
Changes
It corrects a false assumption about split of the 'LAST CHUNK' marker between the previous and current buffer. The new solution concatenates last bytes of the previous buffer with all bytes from the current buffer (if that holds less then 5 bytes) and does the check on that.
Additional information

[ ] I updated readme
[ ] I added unit test(s)

fix #1576

I would love to test out this PR, we suffer quite a lot from a premature close issue in node-fetch in the storybook pipeline:

https://app.circleci.com/pipelines/github/storybookjs/storybook/33011/workflows/b3ef4e9b-4a44-46e6-8c9a-d2075054d683/jobs/444562/parallel-runs/5
https://app.circleci.com/pipelines/github/storybookjs/storybook/32962/workflows/e512522a-96ed-4a4d-aef9-e1770dc08076/jobs/444380/parallel-runs/2
https://app.circleci.com/pipelines/github/storybookjs/storybook/32892/workflows/67f913a0-332d-4382-8966-c902c2c3c4b1/jobs/444017/parallel-runs/2
https://app.circleci.com/pipelines/github/storybookjs/storybook/32690/workflows/a2cfb5d9-79ce-488d-af9a-e282a96310a7/jobs/443167/parallel-runs/2
https://app.circleci.com/pipelines/github/storybookjs/storybook/35150/workflows/a3f13eb6-bf9b-4e3b-9d9e-d6594277eaac/jobs/454236/parallel-runs/5

Not sure if it is related, but we have no clue how to fix it.

This PR should be merged. We suffer the same problem, and this patch fixed it. It must be released in npm (3.x.x and 2.x.x), thanks!

@LinusU would you maybe be so kind to assign other reviewers in case you don't have the time right now?

+1


read s3 bucket region sent by server

https://issues.redhat.com/browse/ECOPROJECT-272
Signed-off-by: Yaron Dayagi<EMAIL_ADDRESS>

@jakub-dzon please review


KeyboardTextField issues in 7.x

Hey Daniel,
Congrats on the 7.0 release!
Everything seems to work after the update except for the KeyboardTextField.
In 7.0, it registers itself as an alternate proxy when it becomes the first responder on appearance, and you can type in the field, but it doesn't unregister itself on disappearing (it resigns as the first responder, though).
I'm binding a standard SwiftUI FocusedState to the view and set it to false to end editing, and everything worked fine before the update.
After the 7.1 update, my KeyboardTextField doesn't appear at all, and I get an error: [View] First responder issue detected: non-key window attempting reload - allowing due to manual keyboard.
Here are some code excerpts:
@FocusState private var isTextFieldFocused: Bool
unowned var controller: KeyboardInputViewController
VStack {
if showTextField {
KeyboardTextField(text: $userKeyboardInput, controller: controller)
.focused($isTextFieldFocused)
}
SystemKeyboard(controller: controller, autocompleteToolbar: .none)
}
.onChange(of: showTextField) { value in
                isTextFieldFocused = value
                }

I also tested
.onAppear { isTextFieldFocused = true }
.onDisappear { isTextFieldFocused = false }

And it worked in earlier versions but didn't make any difference in 7.x.
I'd appreciate any help!

Hi @maxgrev
Thank you! The 7.0 version involved quite a bit of work, so I'm happy to hear that most things work. I just released a 7.1 that improves things further.
Sorry to hear about the broken KeyboardTextField. I will look into it and see if I can track down what happens.
Just to clarify - you wrote After the 7.1 update 2 hours ago.
I will look into this asap and hope to have a fix out soon!

Hi again @maxgrev
Ok, a short update - I tried adding a text field, but as you said it didn't show up. If I however add a background color and border style in the configuration block, the text field shows up:
private struct MyView: View {

    @State
    private var text = ""

    unowned var controller: KeyboardInputViewController

    var body: some View {
        VStack(spacing: 0) {
            Color.red.frame(height: 1)
            KeyboardTextField("Test", text: $text, controller: controller) {
                $0.backgroundColor = .systemBackground
                $0.borderStyle = .roundedRect
            }.padding(3)
            Color.red.frame(height: 1)
            KeyboardTextView(text: $text, controller: controller) { _ in
                //$0.backgroundColor = .systemBackground
                //$0.borderStyle = .roundedRect
            }.frame(height: 80).padding(3)
            Color.red.frame(height: 1)
            SystemKeyboard(controller: controller)
        }
    }
}

As you can see, this is however not required for the text view, so I'm not sure what has changed for the text field, since I haven't changed the configuration block.
I will add these configurations to the default configuration. Until then, you can add the background color and border style to your own code.
I see that neither the text field or text view no longer unregisters as the proxy when they loose focus. I will investigate why this happens and will try to have a 7.1.1 out shortly.

Hi again @maxgrev
I found the solution to the focus problem. Somehow, checking the input proxy like this no longer works:
func handleResignFirstResponder() {
    guard controller?.textInputProxy === self else { return }
    controller?.textInputProxy = nil
}

Removing the guard check makes it work again.
Very strange, since I'm (99%) positive that it used to work. I will fix this and release a patch update, which I hope to have out soon.

Hey @danielsaidi, thanks for your quick response!
And yes, I meant 7.1. The textField started having the unregistering issue in 7.0, but it was in 7.1 when it stopped showing up altogether.
The background and borderStyle don't help, btw (I already had them before). It appears if you add it as you did, but the conditional appearance doesn't work and throws this error:
[View] First responder issue detected: non-key window attempting reload - allowing due to manual keyboard (first responder window is <UIRemoteKeyboardWindow: 0x14b8a3c00; frame = (0 0; 393 852); opaque = NO; autoresize = W+H; layer = <UIWindowLayer: 0x600000349230>>, key window is <UIWindow: 0x149f3ae30; frame = (0 0; 393 852); gestureRecognizers = <NSArray: 0x600000239800>; layer = <UIWindowLayer: 0x6000002c0a80>>)

Here's an example:
@FocusState private var isTextFieldFocused: Bool
@State private var showTextField: Bool = false
VStack {
 Button("Show Text Field") { showTextField.toggle() }
  if showTextField {
 KeyboardTextField(text: $userKeyboardInput, controller: controller)
 .focused($isTextFieldFocused)
  }
}

@maxgrev
I have added a new demo keyboard to the demo app, that adds the two text input views above a system keyboard:
https://user-images.githubusercontent.com/429927/224187420-f108c258-d074-45ac-be78-c52c62f6bd79.MP4
I have also added a custom focused modifier, that takes a custom done button that slides in when the view becomes focused and can be tapped to make the view lose focus.
I will look into the conditional view problem now.

@maxgrev Sorry for spamming, but using a conditional input field works for me.
I modified the new demo's keyboard view to look like this:
struct DemoKeyboardView: View {

    @State
    private var text1 = ""

    @State
    private var text2 = ""

    @State
    private var isShown = false

    @FocusState
    private var isFocused1: Bool

    @FocusState
    private var isFocused2: Bool

    unowned var controller: KeyboardInputViewController

    var body: some View {
        VStack(spacing: 0) {

            if isShown {
                KeyboardTextField("Type text here...", text: $text1, controller: controller)
                    .focused($isFocused1, doneButton: doneButton)
                    .padding(3)
            }

            Button(isShown ? "HIDE" : "SHOW") { isShown.toggle() }

            KeyboardTextView(text: $text2, controller: controller)
                .focused($isFocused2, doneButton: doneButton)
                .frame(height: 80)
                .padding(3)

            SystemKeyboard(
                controller: controller,
                autocompleteToolbar: .none
            )
        }.buttonStyle(.plain)
    }

    func doneButton() -> some View {
        Image(systemName: "x.circle.fill")
    }
}

And this works, as you can see here:
https://user-images.githubusercontent.com/429927/224188355-68aed116-60ce-4a0d-b762-a56984f75840.MP4
Tapping the show button presents the text field, which can then be focused. Tapping return or the done button returns focus to the main app.

I will release this as a 7.1.1 tomorrow, but please take a look at the new demo and see if you can break it, so that I can fix that before releasing 👍

Challenge accepted and.. done-ish!
I modified your code a bit:
struct DemoKeyboardView: View {

    @State
    private var text1 = ""

    @State
    private var text2 = ""

    @FocusState
    private var isFocused1: Bool

    @FocusState
    private var isFocused2: Bool

    @State private var showTextField: Bool = false

    unowned var controller: KeyboardInputViewController

    var body: some View {
        VStack(spacing: 0) {
            Button("Show Text Field") {
                showTextField.toggle()
            }
            if showTextField {
                KeyboardTextField("Type text here...", text: $text1, controller: controller)
                    .focused($isFocused1, doneButton: doneButton)
                    .padding(3)
                    .onAppear {
                        isFocused1 = true
                    }
                    .onDisappear {
                        isFocused1 = false
                    }
            }
            KeyboardTextView(text: $text2, controller: controller)
                .focused($isFocused2, doneButton: doneButton)
                .frame(height: 80)
                .padding(3)

            SystemKeyboard(
                controller: controller,
                autocompleteToolbar: .none
            )
        }.buttonStyle(.plain)
    }

    func doneButton() -> some View {
        Image(systemName: "x.circle.fill")
    }
}

Strangely enough, it's working now, but I still get the same First responder issue detected error on appearance.

Oh, wait, I missed your latest comment where you added conditionals. Looks like the issue isn't conditional appearance, but making the textField first responder. I played around with DispatchQueue.main, but it doesn't make a difference. It's strange that there was no such error in earlier versions. I'll play around a bit more, maybe there's some workaround that I don't see yet.

Hey @danielsaidi, can't find a workaround, still getting this first responder warning in the console whenever I make the text field focused – on appearance or manually. It works, though. Are you going to push 7.1.1 today so I can ship the update?

Hey, I will continue with this soon and release the 7.1.1 in a few hours. I just wanted to take a look at the warning one extra time before I did. Do you think it's ok to ignore the warning or should we aim to fix it?

Hi again @maxgrev - I pasted your code and run the new demo keyboard as debug target, but I actually don't get the warning you posted. I do get the good ol' [External] -[UIInputViewController needsInputModeSwitchKey] was called before a connection was established to the host application. This will produce an inaccurate result. Please make sure to call this after your primary view controller has been initialized. warning every time a text field is focused, but everything seems to work great now, so I'll continue with the patch release.

Ok, 7.1.1 is out - hope it works for you 👍

Happy to hear it! Very strange with the warning, though. Let me know if you find out what's causing it.

Hi Daniel, I just wanted to say how much I appreciate your work on the library. I'm currently working on a small app that utilizes it.
However, I've run into an issue with my KeyboardTextField. The only ways I've found to lose focus are by setting the FocusState to false using a button or by using the doneButton. I noticed that some apps, like Google keyboard, allow users to lose focus simply by tapping on a text field within the visible app. Is there a way to achieve this functionality or is relying on the doneButton or a custom button my only option? I've been struggling with this for several days now and would appreciate any advice you could offer. 😓

Hi @acrosa
Thank you, happy to hear that you like it!
Would it be possible for you to create this as a separate issue? Thanks 👍


libmkl_intel_lp64.so.2: cannot open shared object file: No such file or directory

my prerequisites are fulfilled however when i try to execute the cpu_spmv i get the following error
error while loading shared libraries: libmkl_intel_lp64.so.2: cannot open shared object file: No such file or directory
when i "somehow" fix it, i get another one and it goes on. what can i do?

I created a bash script to add dynamic libraries so the program cpu_spmv can find it
here's it's
=== add_dynamic_libs.sh ===
#!/bin/bash

export LD_LIBRARY_PATH="$(echo $HOME)/intel/oneapi/mkl/2023.2.0/lib/intel64/:$LD_LIBRARY_PATH"

export LD_LIBRARY_PATH="$(echo $HOME)/intel/oneapi/mkl/2023.2.0/lib/intel64/:$LD_LIBRARY_PATH"

export LD_LIBRARY_PATH="$(echo $HOME)/intel/oneapi/compiler/2023.2.0/linux/compiler/lib/intel64_lin/:$LD_LIBRARY_PATH"

sudo ldconfig

open your terminal on the project folder and type
$ make cpu_spmv
$ source add_dynamic_libs
$ ./cpu_spmv --mtx="..."

then it works fine


Update Globals “site_data”

Automatically generated by Netlify CMS

👷 Deploy Preview for benevolent-muffin-215770 processing.

Name
Link

🔨 Latest commit
6b1220efa4c03c82428ef864b25f3eda98bee487

🔍 Latest deploy log
https://app.netlify.com/sites/benevolent-muffin-215770/deploys/628483a4b920760008507cde


Added 4 orgs to the list

IBM-Bluemix, watson-developer-cloud, IBM-Watson, ibm-research

merged; thanks


Store dataset creation date in meta.json

For normal uploads this value will be set to the dataset upload time.  For admin user-proxy uploads this value may be provided.  This is to maintain user dataset creation dates from the legacy system.
This change will require an update to the cache-db schema to store the new meta value.

UPDATE
Due to crossed wires a bad attempt was made to implement this.  That attempt involved accepting a creation date override value on the user-proxy dataset upload admin endpoint and writing it to the vdi.datasets.created field in postgres.  That is a misuse of the field and does not implement the base requirements.  Additionally, the date in the postgres table is not synchronized cross campus as it does not appear in MinIO.

UPDATE
We will be keeping the bad implementation that repurposed the vdi.datasets.created column to track datasets' original creation date.  Now to track the insert date of the dataset record into postgres, we will add a new column to the vdi.datasets table: vdi.datasets.inserted.

Preparation

[x] Update the schema in the vdi-internal-db repo
[ ] Update vdi-component-common to add the new field to the dataset meta pojo
[ ] Add a temporary, one-off migration script to VDI to update the existing postgres instances to avoid needing the database volumes to be dropped.
[ ] Wire the new inserted column into the VDI service
[ ] Update the plugin handler server to use the new vdi-component-common version and tag a new release
[ ] On a branch, update the plugin base image to use the new plugin handler server version
[ ] On a branch, update the bigwig plugin to use the branched base image
[ ] On a branch, update the biom plugin to use the branched base image
[ ] On a branch, update the example plugin to use the branched base image
[ ] On a branch, update the genelist plugin to use the branched base image
[ ] On a branch, update the isasimple plugin to use the branched base image
[ ] On a branch, update the rnaseq plugin to use the branched base image

Deployment

[ ] Bulk delete all datasets in dev VDI via the API
[ ] merge the plugin base image branch to main and tag new version
[ ] update bigwig plugin branch to use new base image tag, merge to main
[ ] update biom plugin branch to use new base image tag, merge to main
[ ] update example plugin branch to use new base image tag, merge to main
[ ] update genelist plugin branch to use new base image tag, merge to main
[ ] update isasimple plugin branch to use new base image tag, merge to main
[ ] update rnaseq plugin branch to use new base image tag, merge to main
[ ] merge vdi service update branch to main

Cleanup
Once VDI has been redeployed on both campuses and the migration script has succeeded...

[ ] Remove migration script from VDI service


Add option for vertical slide center alignment

Clear and concise description of the problem
Right now, if I want to vertically center my slides (e.g. for text content that may vary in height between slides), I need to do a bit of a hack because of the shadow root element methods used.
onMounted(() => {
  nextTick(async () => {
    const sheet = new CSSStyleSheet
    sheet.replaceSync(`.swiper-wrapper { align-items: center; }`)
    sc.value.shadowRoot.adoptedStyleSheets.push(sheet)
  })
})

This is because we are unable to simply specify classnames and apply classes when they are within a shadow root element.
Suggested solution
It seems that there are a few discussions about this over the years so I imagine it would be a very useful and hopefully quick fix to add an option for vertical centering, just like there is one for horizontal centering.
The option centeredSlides is not clear in the reference. It suggests slides will be centered, but it only appears to center horizontally.
To avoid a breaking change and applying align-items: center; to .slider-wrapper - how about we add a new option, vCenteredSlides which simply adds this css style? Otherwise I think it'd work fine. And I don't think it'd clash even if users select to apply dynamic height resizing between the slides.
Any thoughts?
I did see some issues which were just asking for help a long time ago and they were directed to Stack Overflow. But didn't spot any relating to this way of fixing the solution or the proposal of a new API option.
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Would you like to open a PR for this feature?

[X] I'm willing to open a PR

You can use injectStyles parameter like so:
...
injectStyles: [`.swiper-wrapper { align-items: start }`],
...

https://swiperjs.com/element#injecting-styles

Thank you, sorry for missing it and perhaps this issue will help others who come across this issue. Tidy fix.

since there is an api command for horizontal centering, it would be cohesive to have one for vertical too.


Complex Loss Functions Inside TrainingLoop

Thanks to @xihui-wu's talk earlier today, I learned about the TrainingLoop struct. I had essentially replicated this functionality in a messier way in my code, so I'm looking at it to see if I could replace my train loop with this cleaner implementation. I believe the only issue I might face is with respect to the loss function.
The current loss function takes as parameters only the model's output and the target: public typealias F = @differentiable(Output, @noDerivative Target) -> Tensor<Float> from here. This covers a huge majority of supervised training situations, but there are situations where we might want more complicated loss functions. For example, how might we mask the output and the target for each sample when we calculate the loss, as done in this paper:

at each time step the model tries to predict the full, uncorrupted input vectors xt; however, only the predictions on the masked values are considered in the Mean Squared Error loss.

Another situation that comes to mind is a loss that requires some third, external set of values. Perhaps this is an RL agent whose current loss is a function of recent past losses. Another example could also be a risk-adjusted metric where "risk" depends on some external value that is not static.
Is my reading of the code correct that these types of loss functions are not currently supported? If so, could the protocol be reasonably modified to optionally support such complex loss functions?
Many thanks!

@xanderdunn thanks for your post! TrainingLoop is currently in iterations to develop to cover more and more use cases.
To answer you first question in supervised learning scenario - generally speaking, if you want to customize loss function by manipulating on output and label, you can write your loss function like what BERT-CoLA does here. For your mask case, you might be able to do similarly,  or do sth inside the model like BERT attention does here ?
Secondly, yes, when the loss function depends on some training-state-depended value, some work are do needed to allow for it. Specially RL, it is a different world, we are considering providing different TrainingLoop variations for it.
cc @BradLarson

Thanks @xihui-wu.  Writing custom loss functions is straightforward, but the challenging part is a training loop that is compatible with loss functions that take more than just logits and labels as parameters. In the linked example the labels have type Tensor<Int32>. Could this instead be a struct that contains multiple tensors? Such a struct could contain both the labels and the masks, for example.
Your BERT attention link points to the same link as the BERT-CoLA example, but I think you're referring to this attention mask that is applied here to the attention scores? This masks the inputs into the model, but it doesn't mask the outputs and the targets for calculating the loss as done in the Transformer representation learning paper I linked above.

Thanks for correcting the link. You are welcome to try if making it into a struct together with some changes in TrainingLoop works. Again our current TrainingLoop implementation isn't in a final form, and more flexibility may be needed for RL and other applications! At some point we might look at having composable training loop pieces so that loops could be more flexible, but that be some ways off. We're open to having the current training loop be expanded to fit other use cases.


Wrong formatting of the examples in the API docs

I think this should be formatted as a code block? https://ocr-d.de/core/api/ocrd/ocrd.workspace.html, under both  "Example" headlines.

Hard to say what syntax exactly our rST dialect expects here. Maybe we are just missing 4 characters of extra indentation?


[Jsontracer] Add ruler to render timeline of bar-graph

This will render ruler to show timeline of bar-graph
ONE-vscode-DCO-1.0-Signed-off-by: Junyeong Yang<EMAIL_ADDRESS>

from draft #126
from issue #94


ag-grid isn't only for angular

According to documentation, ag-grid means agnostic grid and supports angular 1 or 2, react, vue, etc. I think mentioning it under angular is misleading.

Improved

:+1: Looks much better. What about mentioning React ?

Done


[ML Kit translate] Feature request : support macos

Hi, FlutterFire, which is an unofficial Firebase plugins repository for Flutter apps started supporting more and more macos plugins for Fluttter Desktop apps. Would it be possible to support macos as well ?
In an effort to do so I tried to port an ios plugin to macos but I'm getting this error : The platform of the target 'Runner' (macOS 10.11) is not compatible with 'Firebase/MLNaturalLanguage (6.12.0)', which does not support 'macOS'..

Adding macOS support for ML Kit is unlikely to happen in the near future. Currently the closest thing is to use Firebase Storage to download TF Lite models on macOS.

Thank's for the hint I'll do that then. Do you know where I can find the source code of Ml kit to get all the urls/or some firebase storage code I can port in order to download the models?

ML Kit is not open-source, but Firebase Storage is. The source code for Storage is here, and its documentation is here.
Many of ML Kit's models are available on the TF Lite website here.


Forcing float conversion because sometimes the input was a string.

This causes a problem with Python 3 because comparing a string and a float
is an error.

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
Closes #814
What are the significant changes in functionality due to this change request?
This changes the output because comparing a string to a float is different than comparing two floats.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?

Merging....  Checklist passed...


receive: create a gRPC remote_write endpoint

I understand the compatibility reasons for creating a remote_write endpoint that adheres to the Prometheus standard. Would you consider enabling a gRPC endpoint to enable pushing metrics from arbitrary gRPC sources? Ideally it would use a gRPC Stream to improve performance.

I think I would want something like this to be experimental, but if we can prove it to have a significant improvement over the existing one, then I'd even go a step further and attempt to make Prometheus send remote write via gRPC.

I've started work on this here: https://github.com/blockloop/thanos/tree/bjones/receive/use-grpc


Adopt the binary-compatibility-validator

Keep in mind that this is a binary API dumper and NOT actually a binary compatibility validator. Reviewers need to still be vigilant to validate backwards compatibility as part of the review process.


Filtering by lv_name on existing snapshot check

Fixes Bug: #12

LGTM, but we need @swapdisk's approval

LGTM, but lint failed with line too long error.

🤦 I forgot to enable the workflows on my fork. Should be fixed now.