Rules scripting

Please have a look at the individual commit messages for the details.

@oss-review-toolkit/kotlin-devs, while this is still a draft, could some of you maybe confirm that this offers proper syntax hightlighting and auto-completion in IntelliJ for evaluator/src/main/resources/rules/no_gpl.rules.kts now (but not for examples/example.rules.kts; that is expected as that script is not part of any module)?

@oss-review-toolkit/kotlin-devs, while this is still a draft, could some of you maybe confirm that this offers proper syntax hightlighting and auto-completion in IntelliJ for evaluator/src/main/resources/rules/no_gpl.rules.kts now (but not for examples/example.rules.kts; that is expected as that script is not part of any module)?

Does not work for me. After Gradle sync I got:
"No script runtime was found in the classpath: class 'kotlin.script.templates.standard.ScriptTemplateWithArgs' not found. Please add kotlin-script-runtime.jar to the module dependencies."
If I apply the suggested fix it adds implementation(kotlin("script-runtime")) to the evaluator module but then I get compilation errors like Unresolved reference: PackageRule.

Does not work for me.

Could you additionally try to build from the command line once, then do a Gradle sync from the IDE, and then open the script file again?

If I apply the suggested fix it adds implementation(kotlin("script-runtime")) to the evaluator module but then I get compilation errors like Unresolved reference: PackageRule.

That's an odd suggestion... none of the examples at https://github.com/Kotlin/kotlin-script-examples has that dependency.

Could you additionally try to build from the command line once (I usually do this via ./gradlew :cli:run --args="--version"), then do a Gradle sync from the IDE, and then open the script file again?

Works very well for me after building it from command line.

Could you additionally try to build from the command line once (I usually do this via ./gradlew :cli:run --args="--version"), then do a Gradle sync from the IDE, and then open the script file again?

Works very well for me after building it from command line.

Same here, very nice.

I'd like to move examples.rules.kts to a Kotlin module so that completion works. What do you guys think about simply replacing the overly simplistic no_gpl.rules.kts with examples.rules.kts as a resource? Should we then symlink this to the examples directory, even if that might break things for Windows users?

I'd like to move examples.rules.kts to a Kotlin module so that completion works. What do you guys think about simply replacing the overly simplistic no_gpl.rules.kts with examples.rules.kts as a resource? Should we then symlink this to the examples directory, even if that might break things for Windows users?

Does this solution only work within this Gradle project, or is it possible to create a minimal Gradle project that depends on the evaluator to have working completion? If it is possible I would prefer such a project and put it in the examples folder.
And I would not like a symlink, I would rather have a file that contains something like "// See: path/to/evalutor.rules.kts".

is it possible to create a minimal Gradle project that depends on the evaluator to have working completion?

It should indeed be possible to create a "rules-only" project by depending on the scripting-utils artifact, and I like the idea to create such an example. However, I'll do that in a separate PR then.


Advertising ID may not be fetched before events sent

Spotted by @hamidp

Advertising ID is always fetched (if it can) when the Subject is created.  It will always be set before any events can be sent.

Closing.  Refer to above comment.


Adding new SilentLogs to remove message from the console

Closing as the PR has become out of date with the main branch and comments have not been addressed.


KRunner (KDE "Run Command") global keybinding broken after upgrade to 20.03 (+ workaround)

Describe the bug
After upgrading from 19.09 to 20.03, the KRunner global keybinding (alt+space) no longer works.
To Reproduce
Steps to reproduce the behavior:

Upgrade to 20.03
Boot into KDE Plasma
Press Alt+Spacebar
eerie and uncomfortable silence, nothing happens

Expected behavior
The command runner dialog should come up at the top of the screen.
Screenshots
N/A
Additional context
The problem appears to be that the global keybinding entry was changed somehow, in the "Global Shortcuts" KDE settings panel.
The keybinding was still set for "Run Command":

But there is now also a "KRunner" entry in "Application Launchers", which did not have any keybindings set, despite exposing the same actions:

Assigning the keybinding to "KRunner" instead of "Run Command" fixes the issue.
Notify maintainers
@nyanloutre @ttuegel
Metadata

system: "x86_64-linux"
host os: Linux 5.4.41, NixOS, 20.03.1896.025deb80b24 (Markhor)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.3.4
channels(sven): ""
channels(root): "nixos-20.03.1896.025deb80b24"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

Works for me on 21.11 without any workarounds.


CatVariant not handling allele "*" in gatk-haplotype-joint

I am trying bcbio on an exome trio using joint calling with various callers. My run of gatk-haplotype-joint is failing with the following error.
##### ERROR stack trace
htsjdk.tribble.TribbleException: The provided VCF file is malformed at approximately line number 649: unparsable vcf record with allele *, for input source: /media/jawhite/Data/662-exome-trio/work/joint/gatk-haplotype-joint/trio-bwa-j/1/trio-bwa-j-1_0_15543565.vcf.gz
	at htsjdk.variant.vcf.AbstractVCFCodec.generateException(AbstractVCFCodec.java:793)
	at htsjdk.variant.vcf.AbstractVCFCodec.checkAllele(AbstractVCFCodec.java:578)
	at htsjdk.variant.vcf.AbstractVCFCodec.parseSingleAltAllele(AbstractVCFCodec.java:618)
	at htsjdk.variant.vcf.AbstractVCFCodec.parseAlleles(AbstractVCFCodec.java:548)
	at htsjdk.variant.vcf.AbstractVCFCodec.parseVCFLine(AbstractVCFCodec.java:342)
	at htsjdk.variant.vcf.AbstractVCFCodec.decodeLine(AbstractVCFCodec.java:285)
	at htsjdk.variant.vcf.AbstractVCFCodec.decode(AbstractVCFCodec.java:263)
	at htsjdk.variant.vcf.AbstractVCFCodec.decode(AbstractVCFCodec.java:60)
	at htsjdk.tribble.TabixFeatureReader$FeatureIterator.readNextRecord(TabixFeatureReader.java:150)
	at htsjdk.tribble.TabixFeatureReader$FeatureIterator.next(TabixFeatureReader.java:183)
	at htsjdk.tribble.TabixFeatureReader$FeatureIterator.next(TabixFeatureReader.java:125)
	at org.broadinstitute.gatk.tools.CatVariants.execute(CatVariants.java:300)
	at org.broadinstitute.gatk.utils.commandline.CommandLineProgram.start(CommandLineProgram.java:248)
	at org.broadinstitute.gatk.utils.commandline.CommandLineProgram.start(CommandLineProgram.java:155)
	at org.broadinstitute.gatk.tools.CatVariants.main(CatVariants.java:317)
##### ERROR ------------------------------------------------------------------------------------------
##### ERROR A GATK RUNTIME ERROR has occurred (version 3.2-18-g478145d):
##### ERROR

Line 649 does indeed have an ALT entry of A,*, presumably generated by HaplotypeCaller. I looked at the CatVariants code on Github, and it appears to handle * alleles for ALT in the current version. Is this a version problem? I haven't figured out how to upgrade the htsjdk version that bcbio uses.

Sorry about the issue and thanks for reporting it. We package the MIT licensed parts of the GATK in a separate script/jar to avoid needing to install GATK when running non-variant calling parts of the GATK code. This package was, as you noticed, out of date and on version 3.2. I updated it to 3.4-46 to match the latest release so it should hopefully work cleanly for you now if you upgrade with:
bcbio_nextgen.py upgrade -u development --tools

Hope this gets everything running cleanly for you. Thanks again for the report.


Ability to limit which named values are extracted[FEATURE REQ]

Please describe the feature.
We use extract to extract a single api. Currently as part of that extract it extracts all the named values, not just the ones used by the single api. This means I can accidently publish someone elses named values.
A config setting to specify which named values I want to extract would help
The same for policy fragments, backends, etc. would be helpful.

You can achieve that by using a .gitignore file. You can also utilize the codeowners feature in GitHub or the azure devops policy. Please refer to the docs section that talks about supporting multiple api teams.
Please always ensure that you read the docs before opening bugs/feature requests.

I have read the docs about multiple teams and discussed this with our Microsoft fast track engineer. It doesn't support this feature at all. Perhaps I haven't explained it properly...
I am working on API-A, another dev is working on API-B.
API-B uses the named value "api-b-namedvalue". API-A does not use this named value.
If I extract only API-A it will still extract api-b-namedvalue, and if I then publish that to prod I will publish its dev value to Prod!
At the moment I need to add extra commands to my pipeline to delete the api-b-namedvalue folder and always be on the lookout for new named-values create by other devs sneaking in there
A .gitignore file won't really help, I would still need to detect these newly added named values and manually add them to the gitignore file. I also don't see how a policy would help.

oh hang on I think I get what you're saying, I could whitelist the folders I want in the .gitignore, yeah that might work. I'll have a try


feat(icons): add spwn icon & language

Fixes #3026
Changes proposed:
Add spwn icon and the language id.

I'm going ahead and closing this PR, as I'm not happy with the fact that this "SVG" is just an  tag. Someone would have to make it from scratch and I don't have the skills to do so.


IndexKey refactoring

Let’s have nested IEntityIndexKey.Component instead of Indexed, so we can use it same as StateMachine

IndexTag<T, TUnique> added


error with steamCMD on M1 Mac mini

hello i am trying to install the container on docker on M1 Mac mini and I have an error with steamCMD

May 31 09:15:04 /supervisord: valheim-updater /opt/steamcmd/steamcmd.sh: line 38: 372 Segmentation fault $DEBUGGER "$STEAMEXE" "$@"
May 31 09:15:04 /supervisord: valheim-updater ERROR - Failed to download Valheim server from Steam - retrying later - check your networking and volume access permissions

Any one has an ides on how to solve this ?

the latest version of docker allows emulation for X86 instructions --> I managed to launch the valheim-server-docker container using the option

--platform linux/amd64


WIP: update to v223

update dependencies to v223. This does not build yet, probably because we are building with jdk11, but some class files requiring jdk17:
ERROR: /Users/jast/workspace/bazel-intellij/common/ui/properties/BUILD:12:13: Building common/ui/properties/libproperties.jar (7 source files) failed: (Exit 1): java failed: error executing command external/remotejdk11_macos/bin/java -XX:-CompactStrings '--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED' ... (remaining 17 arguments skipped)
common/ui/properties/src/com/google/idea/common/ui/templates/AbstractView.java:18: error: cannot access AncestorListenerAdapter
import com.intellij.ui.AncestorListenerAdapter;
                      ^
  bad class file: bazel-out/darwin-fastbuild/bin/external/intellij_ue_2022_3/_ijar/sdk/lib/app-ijar.jar(/com/intellij/ui/AncestorListenerAdapter.class)
    class file has wrong version 61.0, should be 55.0
    Please remove or make sure it appears in the correct subdirectory of the classpath.

obsoleted by #4019


Help and Version commands for CL

I think it would be helpful to provide a way for users to know which version of bbc-a11y they have installed and to get some help prompts in the CL. Currently bbc-a11y help and bbc-a11y version both try to test those as URLs, and bbc-a11y alone reports there is no a11y.js config file and offers a link to the github.
I believe such things are fairly common practice and would be useful to implement or improve.

Hi @EmmaJP
I think the following commands give you what you're after, and are fairly standard naming.
> bbc-a11y --help

 Usage: bbc-a11y [options] <urls>

  Options:

    -V, --version              output the version number
    -i, --interactive          show browser window and leave open for debugging
    -m, --manual               include manual tests
    -w, --width <pixels>       override viewport width
    -c, --config <config>      path to config file
    -r, --reporter <reporter>  json or [path to custom reporter module]
    --coverage <list|table>    lists all tests with a description of each test
    -h, --help                 output usage information

> bbc-a11y --version
2.1.0

However, I acknowledge this isn't actually documented anywhere, so I've opened https://github.com/bbc/bbc-a11y/pull/264 to add it.
Please take a look at that PR and let me know if that helps.

Totally me having holiday brain and forgetting to put a double dash in front of a command ... but definitely helpful to have it in the documentation! Thanks.


doc(usage fix) corrected invalid struct types.

The original usage is correct as of 400f776b4f21e16f10cf4ea4daaba42c6d9bb947, however it could be confusing since a version with these changes hasn't been published to crates.io, sorry!


About the behavior of openFilterWindow when using autocmd and keymap

Problems summary
The behavior is different when opening the filter manually and when opening the filter with autocmd.
Expected
There are the following differences when running openFilterWindow with autocmd and when running openFilterWindow manually using the configured keymap.

autocmd

The list of items will not be updated until you confirm what you entered in the cmdline.

keymap

The list of items is updated to sync with the input in cmdline

I would like to unify the behavior with keymap or autocmd.
Ideally, the behavior when using keymap is the best, but as far as I have checked the specifications,
I think that the behavior when using autocmd is the expected behavior.
Environment Information

ddu-ui-ff version (SHA1): 5749699

denops.vim version (SHA1): https://github.com/vim-denops/denops.vim/commit/9dd9ae9da9b8d65916dd44e0e4d881665397de63

deno version(deno -V output): deno 1.43.6

OS: Arch Linux

neovim/Vim :version output:

NVIM v0.10.0
Build type: Release
LuaJIT 2.1.1713484068

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/share/nvim"

Run :checkhealth for more info

VIM - Vi IMproved 9.1 (2024 Jan 02, compiled May 26 2024 00:11:37)
Included patches: 1-445
Compiled by Arch Linux
Huge version without GUI.   Test call ddu#start(#{sources: ['file_rec']})

How to reproduce the problem from neovim/Vim startup (Required!)

Vim

vim -N -u .vimrc
:Test
Enter something from there to search

At this time, it will not synchronize with the input and the item list will not be updated until the input is confirmed.

Comment out the autocmd that automatically opens openFilterWindow with Ddu:uiDone
One more steps 1 to 2.
Run openFilterWindow with i by keymap

At this time, the item list will be updated in sync with the input.

neovim

nvim -u .vimrc
Perform the same operations 2 to 6 as in Vim and the same behavior will occur

Reproduced...

autocmd User Ddu:uiDone ++nested
  \ call ddu#ui#do_action("openFilterWindow")

It must be async_action().


Categories

Hi,
What happens when the scale in conventions need to use a category instead of a measure (using another scale instead of a linear scale) ? Is there an option for this ?
Regards,
Rezpe

You can replace the provided c.x with anything you want. For instance:
var xLogScale = d3.scaleLog().domain([1, 1000]).range(c.x.range())

If you still want to use c.drawAxis, pass the new scale to c.xAxis:
c.xAxis.scale(xLogScale)`
c.drawAxis() // draws log axis

Awesome,
Thx !!!!!


Bug: tsdbrelay socket: too many open files

Expected behaviour

tsdbrelay should forward all connections to opentsdb instantly

Current behaviour

we get a huge bunge of messages like this from tsdbrelay:
2020/03/04 11:28:51 http: Accept error: accept tcp [::]:14242: accept4: too many open files; retrying in 5ms 2020/03/04 11:28:51 http: proxy error: dial tcp <IP_ADDRESS>:4242: socket: too many open files 2020/03/04 11:28:51 http: proxy error: dial tcp <IP_ADDRESS>:4242: socket: too many open files 2020/03/04 11:28:51 http: Accept error: accept tcp [::]:14242: accept4: too many open files; retrying in 5ms 2020/03/04 11:28:51 http: Accept error: accept tcp [::]:14242: accept4: too many open files; retrying in 10ms 2020/03/04 11:28:51 http: Accept error: accept tcp [::]:14242: accept4: too many open files; retrying in 20ms 2020/03/04 11:28:51 http: Accept error: accept tcp [::]:14242: accept4: too many open files; retrying in 5ms 2020/03/04 11:28:51 http: proxy error: dial tcp <IP_ADDRESS>:4242: socket: too many open files 2020/03/04 11:28:51 http: proxy error: dial tcp <IP_ADDRESS>:4242: socket: too many open files 2020/03/04 11:28:51 http: Accept error: accept tcp [::]:14242: accept4: too many open files; retrying in 5ms 2020/03/04 11:28:51 http: proxy error: dial tcp <IP_ADDRESS>:4242: socket: too many open files 2020/03/04 11:28:51 http: Accept error: accept tcp [::]:14242: accept4: too many open files; retrying in 5ms 2020/03/04 11:28:51 http: proxy error: dial tcp <IP_ADDRESS>:4242: socket: too many open files

Steps to reproduce

we are forwarding like: 80k datapoints per sec / which was very irregular
and since we took out tsdbrelay the ingestion rate stabilized.

Context
we have 6 tsdbs on our hadoop/hbase data nodes
each of 'em has 96 gb of ram from which tsdbs get 8 hadoop(hdfs) gets 4 and hbase gets 32
all of the nodes are equipped with ssds
on each tsdb async network io is turned to false.
tsdbrelay is configured like this:
/app/tsdbrelay/tsdbrelay -b bosun:8070 -t <IP_ADDRESS>:4242 -l :14242 -redis redis:6379 -db 0
Logs

see above

Thanks for reporting. Can you please add a bit more detail about your setup? What system are you running your Bosun on and if it's a Linux, please can you post the contents of /proc/sys/fs/file-max and the output of ulimit -n?

good morning,
ulimit -n:
65535
cat /proc/sys/fs/file-max:
8143410
we are running on rhel 7. and opentsdb 2.4
kind regards

any news on that?

I'm suspecting it might have to do with the HTTP client and the maximum nymber of idle connections that it allows. 🤔 The default seems to be 2:

const DefaultMaxIdleConnsPerHost = 2
https://golang.org/pkg/net/http/#pkg-constants

We could try increasing MaxIdleConnsPerHost, i.e. something like this:
http.DefaultTransport.(*http.Transport).MaxIdleConnsPerHost = higher_value, but I'll need to look at the implications and whether that would actually fix your problem.

okay....so if you have anything to test i would push it to my infra :-)


KAFKA-10515: Properly initialize nullable Serdes with default values

Also introduced the notion of WrappingNullableSerdes (aligned to the concept of WrappingNullableSerializer and WrappingNullableDeserializer) and centralized initialization in WrappingNullables.
The added integeration test KTableKTableForeignKeyJoinDistributedTest tests wether all serdes are now correctly set on all stream clients.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

The remaining failing tests do not seem to be related to this PR.

@vvcephei This PR should fix the NPE mentioned in KAFKA-10515. Somehow there are some failing tests that are totally unrelated. Can someone review this PR?

@thake can you rebase this PR then ping us here so we can review it?
Thanks!

Hi @thake , I'm really sorry, I missed your earlier ping. I'll review it.
As Bill said, it will need to be rebased (or you can merge trunk in) to resolve those merge conflicts.

@vvcephei no problem.
I just tried to rebase this on the current master and noticed the introduction of the distinguishment between ProcessorContext and StateStoreContext. As both interfaces do not share a common super-interface, I am forced to duplicate a lot of my code. Would it be possible to create a Super-Interface like "TaskContext":
public interface TaskContext {
    /**
     * Returns the application id.
     *
     * @return the application id
     */
    String applicationId();

    /**
     * Returns the task id.
     *
     * @return the task id
     */
    TaskId taskId();

    /**
     * Returns the default key serde.
     *
     * @return the key serializer
     */
    Serde<?> keySerde();

    /**
     * Returns the default value serde.
     *
     * @return the value serializer
     */
    Serde<?> valueSerde();

    /**
     * Returns the state directory for the partition.
     *
     * @return the state directory
     */
    File stateDir();

    /**
     * Returns Metrics instance.
     *
     * @return StreamsMetrics
     */
    StreamsMetrics metrics();

    /**
     * Returns all the application config properties as key/value pairs.
     *
     * <p> The config properties are defined in the {@link org.apache.kafka.streams.StreamsConfig}
     * object and associated to the ProcessorContext.
     *
     * <p> The type of the values is dependent on the {@link org.apache.kafka.common.config.ConfigDef.Type type} of the property
     * (e.g. the value of {@link org.apache.kafka.streams.StreamsConfig#DEFAULT_KEY_SERDE_CLASS_CONFIG DEFAULT_KEY_SERDE_CLASS_CONFIG}
     * will be of type {@link Class}, even if it was specified as a String to
     * {@link org.apache.kafka.streams.StreamsConfig#StreamsConfig(Map) StreamsConfig(Map)}).
     *
     * @return all the key/values from the StreamsConfig properties
     */
    Map<String, Object> appConfigs();

    /**
     * Returns all the application config properties with the given key prefix, as key/value pairs
     * stripping the prefix.
     *
     * <p> The config properties are defined in the {@link org.apache.kafka.streams.StreamsConfig}
     * object and associated to the ProcessorContext.
     *
     * @param prefix the properties prefix
     * @return the key/values matching the given prefix from the StreamsConfig properties.
     */
    Map<String, Object> appConfigsWithPrefix(String prefix);
}

Thanks, @thake .
Ah, sorry about that: it was my change, and now I feel extra guilty for not reviewing and merging your fix in a timely fashion.
It was intentional not to link those two interfaces with a supertype. I assume that the duplication you're concerned about is in WrappingNullables? I wonder if you can avoid passing in the context to those utility methods and only pass in the contextKeySerializer, etc. You could simply getting these at the call site by adding some more extractors to ProcessorContextUtils.
Since this was my fault to begin with, I'm also happy to take a crack at it next week if it proves to be a pain.
For what it's worth, I quite like your approach in this PR.
Thanks again,
-John

@vvcephei You were right. Duplication in WrappungNullables was my biggest concern. I've refactored it in the way you proposed it. It was not a big deal :) So have no worries!
Just a suggestion regarding the API of SateStoreContext and ProcessorContext: Wouldn't it be possible to extract the properties that belong to the context of the task into a seperate entity (TaskContext) and provide getter in StateStoreContext and ProcessorContext to retrieve the TaskContext? Designing it this way would still decouple StateStoreContext and ProcessorContext but at the same time, it would be easier to write common code that only needs to have information from the TaskContext. This would also transport the semantics of the relationships between Task, Processor and State to the "context" level. I know that this is late feedback on this refactoring since the KIP has already been accepted, but I just wanted to share my thoughs on this before it is a public API.

Thanks for the feedback, @thake . Your perspective makes perfect sense. It would certainly simplify our internal code, and it would also help to organize the API a little more. There are a few reasons I leaned more toward the "flat" API:

Immediate concern: The KIP to get lost in the weeds of designing a whole hierarchy of contexts and deciding where each member should reside. As it is the KIP already took an incredibly long time to converge, and splitting out StateStoreContext dragged us into a new round of proposals about reorganizing the "record context" (which became Record and RecordMetadata). We were down to the wire for 2.7 at that point, and shipping something seemed better than shipping nothing.
Long-term concern: I was afraid I'd be creating a situation in which every single update to any context would kick off a whole new round of bikeshedding about which part of the hierarchy the new thing should belong to, or whether we need a new level in the hierarchy, etc. etc. It seems like having two completely independent kinds of context (for state stores and for processors) would drive people to think only of where something new is needed, not where it belongs, avoiding the abstract philosophical discussions that programmers are prone to.
Related long-term concern: Coupling: the notion of "context" is similar, but not identical across state stores and processors. It has already happened that we realized that something shared needed to be restricted to just one of the context. If there were any kind of shared interface (like a super-interface or a common interface as a member, like getTaskContext()), then we would have more challenges in "un-sharing" a member versus just being able to deprecate an un-shared member where it is inappropriate.
Usability: The idea of organizing information for users has two sides. On one hand, it might be nice to be able to say "ah, this is a task property, so I know to look for it in the "TaskContext." But on the other hand, if you need (for example) the configured serde, and you don't see it in your Context, and you've forgotten that it's filed away under "task context", then you'll have to go hunting for it. Then, once you find it, you'll have to try to remember for the future where it's kept, occupying precious mental space that you could be using for other stuff. There's an art to striking a balance between a "wide" API and a "deep" one: a flat interface with just a few members is trivially easy to use, but a flat interface with too many members is a burden.  It doesn't feel like we have too many members in either StateStoreContext or ProcessorContext now, so I'm hesitant to organize further at all.

A moderate amount of duplication in the internal code is the price we pay for these trade-offs. If the duplication itself looked too extensive or risky, then that would be another argument to converge the types, but so far, it doesn't seem too bad.
Anyway, time will tell if this was the right tradeoff. We can always shuffle stuff around in the future. Does this all seem to make sense?

The code should now be ready for review.

Thanks both for your initial feedback and your reply. I'd certainly never pass up the opportunity to hear such concerns or ideas, especially before a release, and I really appreciate that you took the time to raise them.
Also, thanks for your contribution in this PR!

Hello @thake ,
I don't mean to bother you, but just wanted to check if you're able to follow up on the last round of review. We have until Wednesday to make the 2.7.0 code freeze.
Thanks again,
-John

Sorry for not giving any timely response. I'm currently on vacation but I will do my best to update the PR tomorrow.

Thanks, @thake ! Sorry to disturb your vacation.
Please let me know if you want me to finish up this PR for you. If it helps, I could incorporate your responses to my PR, then merge it into your PR, then take care of the other minor remarks I made in review before merging.
I feel like I owe it to you after taking so long to review it. But I also don't want to usurp you, if you prefer to do it yourself.
Thanks,
-John

@vvcephei everything should now be ready for a 2nd review. Your changes have been applied and the comments worked in.

Great! Thanks @thake . I'll take a look now.

Unrelated test failure: Build / JDK 11 / org.apache.kafka.streams.integration.EosBetaUpgradeIntegrationTest.shouldUpgradeFromEosAlphaToEosBeta[true]

Merged to trunk! I'm cherry-picking to the older branches now...

cherry-picked to 2.7

Looks like there are a bunch of merge conflicts for 2.6, probably because trunk/2.7 are post-KIP-478.
I think since 2.7 is in progress right now, we could just stop here. If you want to have this in 2.6 and before, can you send a new PR for it, @thake ?

Sounds reasonable. What is the time line for the next release on 2.6?

Created #9467 for branch 2.6

Thanks. I haven't seen any messages since Mickael volunteered on 1 Oct, so I guess there's still time to sneak it in :)
I'll take a look at #9467 now.


Bug bounty test - PLEASE DO NOT APPROVE. wkybzj

Bug bounty test - PLEASE DO NOT APPROVE. wkybzj

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


⚠ Bofrost.fr has degraded performance

In ef11c51, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1237 ms

Resolved: Bofrost.fr performance has improved in b6ece2e after 12 minutes.


Can't use blocklist_ip

I am getting an error 'undefined method `blocklist_ip' for Rack::Attack:Class' when I put the following in rack_attack.rb.
Rack::Attack.blocklist_ip("<IP_ADDRESS>")
Rack::Attack.blocklist_ip("<IP_ADDRESS>")
I have looked for help and I am unsuccessful finding any. I saw some things about the cache but I don't understand with the documentation that I have seen.

The shorthand methods (such as #blocklist_ip) were added in rack-attack 5.2.0. What version are you using?

Thanks for getting back to me. I am using 5.0.1. I tried using the shorthand..
class Rack::Attack
Rack::Attack.blocklist_ip("<IP_ADDRESS>")
Rack::Attack.blocklist_ip("<IP_ADDRESS>")
...
end
I get the error undefined method "blocklist_ip" for Rack::Attack:Class.
When I change it to blocklist("<IP_ADDRESS>") there is no error.
Is this the proper usage without the "_ip"?

I upgraded to 5.4.0...
Thanks for the help. It is working now.

Cool.
Thank you @lmansur and @Beengie!


Automated Package Upgrade

:tada: This PR is included in version 7.0.68 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Same label for positive and negative cases

Hi,
Thank you for your interesting work. I have a question about the label used for the contrastive loss. Why positive and negative cases have the same label as 0 (lines 309, 297, 303)? It must be 0 for positive and 1 for negative pairs?
Another question about the result of Scaffold published in your paper. This code does not have Scaffold. So, did you run it from https://github.com/Xtra-Computing/NIID-Bench?
Thank you in advance for your feedback.

Hi @nthhiep ,
Note that logits is a matrix with 2 columns. The first column is the positive pair and the second column is the negative pair. Then, by setting the label to 0 and using cross-entropy loss, we can compute the contrastive loss.
Yes, you may run Scaffold from https://github.com/Xtra-Computing/NIID-Bench, which is implemented by our understanding on the Scaffold paper.


Incorrect value documented for the 'interfaceId' property.

The interfaceId property documented in the table in the Device Properties section includes the following text in the description.
This property is set at 'dtmi:azure:iot:deviceUpdateModel;1' for device using DU agent version 0.8.0.
This value is not correct. It should be dtmi:azure:iot:deviceUpdate;1. NOTE that the value shown in the example located under the table IS correct.

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

ID: 4d112a2b-ef70-719f-aabe-b4632f796986
Version Independent ID: faf2ebf1-6dac-3ab8-7005-f59e0e7fa56f
Content: Understand how Device Update for IoT Hub uses IoT Plug and Play
Content Source: articles/iot-hub-device-update/device-update-plug-and-play.md
Service: iot-hub-device-update
GitHub Login: @ValOlson
Microsoft Alias: valls

@BillArmstrong Thanks for the feedback! We are currently investigating and will update you shortly.

Thanks for bringing this to our attention. I have created a PR with the update, changes will be live shortly.
Thanks for improving our documentation! Just so you know, it's also possible to make these changes yourself, if you are interested. Doing so will improve our documentation, and it will add you as a contributor to the document.
In case you're interested, these are the steps to do so:

Navigate to the page of interest
Select the "Edit" button at the top right of the page
Select the "Pencil" icon on the right
Modify the text within the text box in markdown format - more info: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
Name your file change and provide a description, if necessary
Select "Propose file change"
Select "Create pull request" on the 'Comparing changes' page
Select "Create pull request" on the 'Open a pull request' page
You can find a GIF that demonstrates the end-to-end process for submitting changes here: https://aka.ms/editsqldocs.


Genio Motion Sensor

Device normal info

Brand: Mirabella Genio
Model: Genio Motion Sensor

Device info (please complete the following information, which can be found in log):
like this:
{
"active_time":<PHONE_NUMBER>,
"biz_type": 18,
"category": "qt",
"create_time":<PHONE_NUMBER>,
"icon": "smart/icon/1531813512w71nvvv9wkm_0.jpg",
"id": "21146343500291c0ee43",
"ip": "xxxxxxxxxxxxxxxx",
"lat": "30.30286857361191",
"local_key": "c17a130a2f325610",
"lon": "120.0639743842656",
"model": "",
"name": "Genio Motion Sensor",
"online": true,
"owner_id": "12386163",
"product_id": "p0y7ucexietpcqlq",
"product_name": "Genio Motion Sensort",
"status": []
"sub": false,
"time_zone": "+10:00",
"uid": "eu1589623177329OFGIL",
"update_time":<PHONE_NUMBER>,
"uuid": "21146343500291c0ee43"
},
"success": true,
"t":<PHONE_NUMBER>220
}
No Home Assistant Log as the device didn't come across to Home Assistant.
I can give more info from Tuya API explorer if needed.

@sambarlick The device id p0y7ucexietpcqlq is standardized now, try again.

@sambarlick The device id p0y7ucexietpcqlq is standardized now, try again.

Thank you.
The device is now in Home assistant but similarly with the Door/Window Sensor in my other thread, the status isn't being updated and the tamper alarm didn't come through.

@sambarlick look this https://github.com/tuya/tuya-home-assistant/issues/63#issuecomment-874537514

@tsutsuku I set up the notifications API as stated in the other thread, but the motion sensor state is still not updating. The door/window sensor is working.

I'm still not getting the motion state updating, only the battery state. I re-paired my sensor changed batteries and even ran it on usb power, still nothing. This is obviously not using the notification service that the door/window sensor uses.


Filer on String values

How should we do a string filter ?
neither of these works! (item().LoadType is a filed from my table from DB that I load on a lookup before the filter operation.
@equals(string(item().LoadType),string('F'))
@equals(item().LoadType,'F')

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

ID: bfc163f0-2883-6a20-fc06-f84715aa2912
Version Independent ID: ccf25bc7-a643-71b0-0a0d-f51461689747
Content: Filter activity in Azure Data Factory
Content Source: articles/data-factory/control-flow-filter-activity.md
Service: data-factory
GitHub Login: @sharonlo101
Microsoft Alias: shlo

@iLikeAzureSQL Thank you for reaching out and bringing this to our notice. At this time we are reviewing the ask and will provide an update as appropriate

@iLikeAzureSQL I was able to use the below expression and  it worked. Could you please check your 'Items' expression in Filter Activity settings.
Items : @activity('Lookup1').output.value
Condition: @equals(item().Name,'John')

Here is the output of my Lookup1 Acitivity (which will be the input to MyFilterActivity):
{     "count": 20,     "value": [         {             "Name": "John"         },         {             "Name": "Mike"         },         {             "Name": "Alice"         },         {             "Name": "Andy"         },         {             "Name": "Anny"         },         {             "Name": "John"         },         {             "Name": "Mike"         },         {             "Name": "Alice"         },         {             "Name": "Andy"         },         {             "Name": "Anny"         },         {             "Name": "John"         },         {             "Name": "Mike"         },         {             "Name": "Alice"         },         {             "Name": "Andy"         },         {             "Name": "Anny"         },         {             "Name": "John"         },         {             "Name": "Mike"         },         {             "Name": "Alice"         },         {             "Name": "Andy"         },         {             "Name": "Anny"         }     ],     "effectiveIntegrationRuntime": "DefaultIntegrationRuntime (West US 2)" }

@iLikeAzureSQL Just checking to see if the above comment was helpful. And, if you have any further query do let us know.

@iLikeAzureSQL We are closing this issue as we have not heard back from you. You can always re-open the issue if you think that is appropriate.


Circular introscope exporting for non-Jest environments

With "enable": true all the imports of a file will lead to transpiling it, which makes it impossible to test second level modules (those which import functions from others with introscope enabled).

The PR does not fix it fully :(


[Bug]: Contact Sensor not working with HomeBase 3

What happened?
I have recently got a new HomeBase S380. I moved all my motion and contact sensors from the HomeBase 2 (where they worked perfectly) to the new S380 with exactly the same configuration. Notifications are enabled. Motion sensors work perfectly fine, contact sensors do not work at all. When enabling debug mode, I see the contact sensor recognized and loaded as a device, but then no further log entry when opening the contact sensor, yet I see this and get the notification from Eufy.
Seems the push notification from Eufy for contact sensors are not making it/being recognized by the plugin.
Please can you help out?

Device Type
Contact Sensor (Supported)
Plugin Version
v2.0.x (Supported)
HomeBridge Version
v1.4.x (Supported)
NodeJS Version
v12 (Supported)
Operating System
Raspbian 10+ (Supported)
Relevant log output
[02/02/2023, 09:05:29] Homebridge v1.6.0 (HAP v0.11.0) (Homebridge 451E) is running on port 51358.
[2/2/2023, 9:05:32 AM] [EufySecurity-2.1.4] DEBUG: EufyClient connected true
[2/2/2023, 9:05:32 AM] [EufySecurity-2.1.4] DEBUG: CameraMaxLivestreamDuration: 30
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] DEBUG: Found Station T8030P23223805C2 HomeBaseNew HB3 <IP_ADDRESS>
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] INFO:  You're using guest admin account with this plugin! This is recommanded way!
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] DEBUG: This device is not a station. Generating a new UUID to avoid any duplicate issue
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] DEBUG: HomeBaseNew UUID: 1f90daed-495a-4e0a-a95f-53b829e06fde
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] DEBUG: HomeBaseNew Constructed Station
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] DEBUG: HomeBaseNew manual alarm will be triggered only in these hk modes: 0,1,2,3
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] DEBUG: HomeBaseNew Mapping for station modes: [{"hk":0,"eufy":1},{"hk":1,"eufy":0},{"hk":2,"eufy":3},{"hk":3,"eufy":63}]
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] INFO:  Updating accessory: HomeBaseNew
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] DEBUG: Found Station T8410P3121280CCE Chester’s Bedroom INDOOR_PT_CAMERA <IP_ADDRESS>
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] INFO:  You're using guest admin account with this plugin! This is recommanded way!
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] DEBUG: This device is not a station. Generating a new UUID to avoid any duplicate issue
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] DEBUG: Chester’s Bedroom UUID: 73d99e56-9801-4771-af05-077886fda238
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] DEBUG: Chester’s Bedroom Constructed Station
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] DEBUG: Chester’s Bedroom manual alarm will be triggered only in these hk modes: 0,1,2,3
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] DEBUG: Chester’s Bedroom Mapping for station modes: [{"hk":0,"eufy":1},{"hk":1,"eufy":0},{"hk":2,"eufy":3},{"hk":3,"eufy":63}]
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] INFO:  Updating accessory: Chester’s Bedroom
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] DEBUG: Found Station T8410P3121280FD2 Cellar camera INDOOR_PT_CAMERA <IP_ADDRESS>
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] INFO:  You're using guest admin account with this plugin! This is recommanded way!
[2/2/2023, 9:05:43 AM] [EufySecurity-2.1.4] DEBUG: This device is not a station.  Push notifications are on for Eufy; I do get the notifications from the Eufy app but it doesn't come through to HomeKit.

I would appreciate a lot if someone made this work :(

I just saw it work for the first time after I logged into the Eufy account I created for this plugin on my phone too instead of using my main Eufy account there. I don't understand the push notification flows sufficiently, but maybe Eufy only pushes to accounts with an active session?


Factor out LinearGradient and RadialGradient

Making this file self-contained to ease RTL conversion.

Cool, LGTM


Fixing creation of new namespace losing context of Superform::Rails::Form::…

…Field
Similar to #7 namespace creation loses context of Superform::Rails::Form::Field when creating child namespace.

These changes fix an issue I'm currently experiencing.
Basic example:
class ProposalsForm < Superform::Rails::Form
  def view_template(&)
    namespace :settings do |settings|
      render settings.field(:locale).input
    end
  end
end

I expected this to produce:
<input id="proposal_settings_locale" name="proposal[settings][locale]" value="current value is properly set" type="text">

On 0.4.5 I'm running into this issue:
NoMethodError in ProposalsController#edit
undefined method `input` for an instance of Superform::Field

With the changes of this PR I'm able to get the expected output, and there's no error.
@bradgessler Any chance we can get this integrated? Thank you for having a look! 😊

Yep, my ask is to slim down the PR. This one introduces a new test framework, etc.
If somebody can modify this PR or open another one with just this change I'd be happy to review it.
I'm not opposed to adding testing; my ask there is the same, introduce it in its own PR.

@bradgessler see #43 😊


test: Add parsing test for version cli args

Description
Add Unit tests to verify the command line is parsed as expected.

Motivation and Context
Needed to check exactly how yargs parsed the command line. Related to #569 and #575

How Has This Been Tested?
It is only a test.

Types of changes

[x] Chore (change that has absolutely no effect on users)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

@ghiscoding,
If there isn't some strange side-effect I was not expected, I don't believe the errors have anything to do with me adding some more unit test. Might be related to this being a PR from a fork.

@ghiscoding,
This PR was only to demonstrate how I tested my assumptions about how the command line was parsed.

yeah I saw that too, I'm not sure why this is happening considering that version is mocked to return null and that is why I added my unit tests directly in the version-command.spec.ts in my other PR. It might be the move to Vitest that caused this, I don't know. I could take a look later after work. I just got 20min to check some other things over lunch but now it's over... I left a comment & question in the PR I've opened if you could review and reply. Thanks
https://github.com/lerna-lite/lerna-lite/blob/60afb34009b862ea4f3f4a02c80c0c298076c16a/packages/cli/src/cli-commands/__tests__/cli-version-commands.spec.ts#L3-L4

So I ended up splitting the first PR #575 I had to keep only conventional-prerelease code change (without your suggestion) as a new PR #577. If you think that --dry-run should still be covered then feel free to add code for that in this PR or a separate PR (if you do, then you probably want to revisit PR #575 to copy over the unit tests I had for it)


Add back stddef.h

Add back stddef.h
Description

Need to add back stddef.h in bt_hal_avsrc_profile.h

Checklist:

[ ] I have tested my changes. No regression in existing tests.
[ ] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks


codegen on pull: Codegen when pulling in another frontend

Is your feature request related to a problem? Please describe.
When doing amplify pull, if codegen is present in the main project (also with apiId), execute a codegen il the project that is pulling amplify.
Describe the solution you'd like
Would be great if CLI generates all graphql types and statements when pulling in another frontend (even when codegen is added with apiId).

Closing as a duplicate of #5251

Closing as a duplicate of #5251


Find Importers: Add missing break in relative paths logic

Jsonnet is weird with relative paths
Given two envs in their own folder. The two following imports in env1/main.jsonnet will work: ../env2/main.jsonnet and ../../env2/main.jsonnet, so we have to try all of them
The logic does so in a loop. Without a break, the logic worked when the match was found on the first case (and correct one) but failed on the second

Re-requesting review. I changed the logic and added a test

I have cherry-picked the test (without the changes to pkg/jsonnet/find_importers.go) on top of main, and the test PASSes, but it should fail, right?

Yeah, because there was another logic error 🤦. The .. were cutoff and not replaced by an absolute path: https://github.com/grafana/tanka/blob/main/pkg/jsonnet/find_importers.go#L170
But you're right, I think this requires a test that used to fail but now passes. I know how to do one. Let me do that now

I have cherry-picked the test (without the changes to pkg/jsonnet/find_importers.go) on top of main, and the test PASSes, but it should fail, right?

I added a test that does fail on the previous code, but now passes

Thanks for the comments @jvrplmlmn! It helped find another bug and greatly improve the tests


Email Existence Check and Verification Code During Sign-up

:red_circle: Title: Email Existence Check and Verification Code During Sign-up
:red_circle: Issue Description:
During the sign-up process, the system does not check whether the entered email ID exist or not. Moreover, if the email ID exists, there should be an additional step to send a verification code to the email, ensuring that the person entering it owns the email account.
:red_circle: Enhancement Aim:
Check the existence of the email ID during sign-up.
If the email exists, send a verification code to the email for ownership validation.
Allow the user to proceed with the sign-up only after entering the correct verification code.
:red_circle: Changes:
Add a validation check to verify if the email ID is already registered.
If the email exists, prevent further sign-up actions until the user enters the verification code sent to their email.
Display an error message such as "This email ID is already registered. A verification code has been sent to your email to confirm ownership."
Implement a feature to send a verification code to the email ID.
Add input fields to enter the verification code during the sign-up process.
Screenshots 📷

the email entered DOESNT exist at all.
✅ Details to Include When Taking the Issue:
Name: Siddhant Gureja
Participant Role: Hacktoberfest
Happy Contributing! 🚀
Wishing you all the best on your open-source journey. Enjoy! 😎

Assigned @sidgureja7803, make sure that you adhere to project coding standards and format. Good luck!

@PorePranav i have written the code for email verification
I have added some files in the backend
and made some changes in the frontend as well ( App.jsx ), but i am not able to test the changes in my local system as  I am facing some issues while running the server ( backend ) folder. In the .env fie, I have added API keys for Razaorpay and for DATABASE and JWT secret key as well. still i am not able to run it.
Please help

@PorePranav i have written the code for email verification I have added some files in the backend and made some changes in the frontend as well ( App.jsx ), but i am not able to test the changes in my local system as I am facing some issues while running the server ( backend ) folder. In the .env fie, I have added API keys for Razorpay and for DATABASE and JWT secret key as well. still i am not able to run it. Please help

Can you share any logs that you might have, or the error you are getting?

this is the error, I am getting on console when i try to sign up on my local system.

   @PorePranav this is the error, I am getting on console when i try to sign up on my local system.

Could you please show the server logs along with the API Request body and headers? That would help me pin point the exact issue.


Feature/launch with firecloud

Add Launch with FireCloud button to WDL workflows that do not have import statements.

Codecov Report

Merging #222 into develop will increase coverage by 0.51%.
The diff coverage is 75%.

@@             Coverage Diff             @@
##           develop     #222      +/-   ##
===========================================
+ Coverage    60.08%   60.59%   +0.51%
===========================================
  Files          114      115       +1
  Lines         3477     3578     +101
  Branches       451      475      +24
===========================================
+ Hits          2089     2168      +79
- Misses        1157     1180      +23
+ Partials       231      230       -1

Impacted Files
Coverage Δ

src/app/shared/dockstore.model.ts
100% <100%> (ø)
:arrow_up:

src/app/shared/firecloud.service.ts
72.72% <72.72%> (ø)

src/app/search/elastic-search-client.ts
100% <0%> (ø)
:arrow_up:

src/app/container/launch/tool-launch.service.ts
96.55% <0%> (+1.55%)
:arrow_up:

...er-workflow/register-checker-workflow.component.ts
60% <0%> (+2.02%)
:arrow_up:

src/app/shared/file.service.ts
31.81% <0%> (+5.15%)
:arrow_up:

src/app/shared/launch.service.ts
85% <0%> (+5.68%)
:arrow_up:

src/app/workflow/launch/workflow-launch.service.ts
81.08% <0%> (+7%)
:arrow_up:

...c/app/container/dockerfile/dockerfile.component.ts
58% <0%> (+13.26%)
:arrow_up:

Continue to review full report at Codecov.

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


Replace all references of pulumi.io to www.pulumi.com

After TGWMO2019, many older links (both emitted from the CLI and within the docs) would benefit from being updated.

Page: https://www.pulumi.com/docs/quickstart/aws/install-pulumi/
=== Pulumi is now installed! 🍹 ===
+ If you're new to Pulumi, here are some resources for getting started:
      - Getting Started Guide: https://pulumi.io/quickstart

The link redirects to https://www.pulumi.com/docs/quickstart/ but this should probably be updated to reflect the new URL.

Retitled, as this is a more general thing we need to fix up. We made changes in the pulumi-service repo, but we need to make similar changes in pulumi/pulumi and finally in this one, too.

We also need to update the description of the pulumi/docs repo. I'd do it, but I don't think I have the necessary GH permissions.

I updated the URL ... if you meant for something more, please feel free to
file an issue my way.
On Mon, Jul 15, 2019 at 7:31 AM Justin Van Patten<EMAIL_ADDRESS>wrote:

We also need to update the description of the pulumi/docs repo. I'd do
it, but I don't think I have the necessary GH permissions.
[image: Screen Shot 2019-07-15 at 7 30 41 AM]
https://user-images.githubusercontent.com/710598/61223980-92ef2580-a6d2-11e9-9bdb-4bf212823b29.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pulumi/docs/issues/1311?email_source=notifications&email_token=AB77TQULJ6ORHT3SBWRNRK3P7SC5RA5CNFSM4H7KFUF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ54EUA#issuecomment-511427152,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB77TQVZKVU56E52Q4NKLUTP7SC5RANCNFSM4H7KFUFQ
.

Need to update all our repos.
Note: There are a handful of pulum.io "short links" that we want to continue using for now:

https://pulumi.io/help/outputs
https://pulumi.io/help/stack-reference
https://pulumi.io/oa5g1o
https://pulumi.io/ws0cq2
https://pulumi.io/xdv72s

https://github.com/pulumi/pulumi-terraform/pull/425

Should be fixed from the linked PRs, though there are still old references in the library repos. We'll let those slide for the time being.


Problem with sending data with exceptions on Sentry

Hi there.
I have a problem with python Sentry SDK
When I want to capture an exception with the capture_exception method,  I set a context with set_context and pass all the extra data to it as a dict and in the sentry web panel, I can't find fields which have None values or in some exceptions, some fields are missing, Sentry will remove these fields. how can I send a JSON object with an exception?

@kurama-cube please use the forum as discussed in https://github.com/getsentry/sentry/issues/15215


⚠ Bofrost.fr has degraded performance

In 23a7b4d, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1484 ms

Resolved: Bofrost.fr performance has improved in 3a8f37b.


fix + feat: FormInputDatePicker

make format prop work
remove unnecessary BFormInput
id fix
remove unnecessary code
add prop showNowButton
dateFormat prop accept only string

This cannot be merged. It fundamentally changes the whole concept of how this element should work. But you can make a new element out of it.


FreeBSD service command does not output "unrecognized"

google_oslogin_control uses "unrecognized" to determine if a service exists. FreeBSD does not output this string; instead (for the mythical bob service) it outputs
bob does not exist in /etc/rc.d or the local startup
directories (/usr/local/etc/rc.d), or is not executable

The impact of this is that the attempt to restart a non-existent service fails triggering a roll back of all the changes made.
The line is:
 if ! service "$service" status 2>&1 | grep -q unrecognized; then

A fix is to use a grep invocation that relies on a regex instead of a straight text match.
if ! service "$service" status 2>&1 | grep -Eq "unrecognized|does not exist"; then

Made a pull request to address with your suggested fix. We just made a new release so it might not make it to our master branch for a little while.


douglas willamis repo

@DouglasWillamis thnx for contributing, try this year, and make sure you follow me and star this repo for updates about special swags I will be giving.
Contribute in October for Hacktoberfest 2020


SVG not fully rendered on iOS with latest versions

Description
Rendering in "react-native-svg": "15.6.0"

I made this SVG in Figma recently and tried using it in my app. I was on<EMAIL_ADDRESS>at the time. So I tried upgrading yesterday to 15.5.0 and to my surprise it worked on android but not iOS, so something was fixed in 15.3.0...15.5.0 that caused the SVG in the snack to start working on Android. It does still not work in iOS. It works on web. The issue is that the bottom right QR-icon is not rendered as shown on the attached image. The right hand render of the image is the expected state, the left hand shows how it renders previously on android.
I tried today before submitting this bug with version 15.6.0 and as you can see in the top screenshot it is still buggy.
Steps to reproduce

Use ./components/Icon.jsx from https://snack.expo.dev/@stefanwallin/react-native-svg-not-rendering-fully-on-ios with<EMAIL_ADDRESS>as in the snack.
STATUS: iOS :x: & Android :x: is not rendering the bottom QR-icon.
Update<EMAIL_ADDRESS>(expo go does not support > 15.2.0 yet)
STATUS: iOS :x: is not rendering the bottom QR-icon, but Android ✅ WORKS

Snack or a link to a repository
https://snack.expo.dev/@stefanwallin/react-native-svg-not-rendering-fully-on-ios
SVG version
15.6.0
React Native version
0.74.5
Platforms
Android, iOS
JavaScript runtime
Hermes
Workflow
React Native
Architecture
Fabric (New Architecture)
Build type
Debug app & dev bundle
Device
Real device
Device model
iPhone 13 mini
Acknowledgements
Yes

same issue. Even for web it does this.

same issue. Even for web it does this.

Haven't tested explicitly with web, but 15.2.0 (in the snack) works on the snack web preview (Brave, Version 1.68.141 Chromium: 127.0.6533.120 (Official Build) (arm64))

If you switch page from 1 to another using routes. It breaks.

I've seen the same issue. SVGs work fine on iOS in version 15.0.2 and 15.0.3 but when updating to 15.0.4 or bigger they stop rendering some of the parts.

Hello @facuacostag, @djaffer.
Can you provide any examples?

@StefanWallin I'm not sure about the problem because when I changed that line: <G mask="url(#a)"> <G>
here is the full example:
const Icon = () => {
  const width = 200;
  const height = 200;
  const color = 'black';
  return (
    <Svg width={width} height={height} viewBox="0 0 475 599" fill="none">
      <G clipPath="url(#a)">
        <Mask
          id="a"
          width={147}
          height={147}
          x={391}
          y={333}
          maskUnits="userSpaceOnUse"
          style={{
            maskType: 'luminance',
          }}>
          <Path fill="#fff" d="M538 333H391v147h147V333z" />
        </Mask>
        <G mask="url(#a)">
          <Path
            fill={color}
            d="M458.4 382h-6.1v-12.3h6v6.2h12.3v6.1h-6.1v6.1h-6.1V382zm12.2 73.5v-6.1h-6.1v6.1h6.1zm-6.1-91.9v-6.1h-12.3v6.1h6.2v6.1h6.1v-6zm49-6.1v36.8h-6.1V388h-24.5v-30.6h30.6zm-6.1 24.5v-18.4H489V382h18.4zm-85.8 12.3h-6.1v6h12.3v-6h-6.2zm0 18.3h6.1v6.1h6.2v-18.3h-6.1v6.1h-12.3v12.3h6.1v-6.2zm30.6 6.1V431h6.2v-12.3h-6.1zm24.6-61.2h-6.2v18.4h6.1v-18.4zm0 30.6V382h-6.2v6.1h6.1zM495 376h6.1v-6.1h-6v6zm-61.2-6.1h-6.1v6h6v-6zm12.2-12.3v30.6h-30.6v-30.6H446zm-6.1 6.1h-18.4V382H440v-18.4zm55.1 30.6v6.2h-6v-6.1h-12.3v6h-6v-6h-18.4V388H446v6.1h-6v6.2h6.1v12.2h6.1v-6.1h6.2v12.3h6.1v-12.3h18.4v6.1h-12.3v6.1H483v6.2h6.1v-18.4h6.1v6.1h6.1V425h6.2v-6.1h6.1v-6.2h-6.1v-6.1h-6.1v-6.1h6v-6.1h-12.2zm-67.4 49h6.2v-6h-6.1v6zm-12-18.3h30.6v30.6h-30.6V425zm6.1 24.5H440V431h-18.4v18.4zm73.5-18.4V425H489v6.1h6.1zm0 6.1H489v6.1h-6.1v-6h-6.1V431h6v-6.1h-12.2v-6.1h-6.1V431h-6.1v6.1h-6.1v18.4h6v-6.1h6.2v-6.1h12.3v12.2h6v-6.1h6.2v6.1h12.3v-6.1h6v-6.1h-12.2V437zM440 418.7h6.1v-6H440v6zm61.3 12.3v6.1h6v6.1h6.2V425h-6.1v6.1h-6.1zm12.2 24.5v-6.1h-6.1v6.1h6.1zm0-49v-6.1h-6.1v6.1h6.1zm-12.3-61.3h24.6v24.6H538V333h-36.8v12.3zm-98 24.6v-24.6h24.6V333H391v36.8h12.3zm24.6 98h-24.6v-24.6H391V480h36.8v-12.3zm98-24.6v24.6h-24.5V480H538v-36.8h-12.3z"
          />
        </G>
      </G>
      <Path
        fill={color}
        fillRule="evenodd"
        d="M247.3 22.2A52 52 0 01284 43a51 51 0 018.5 39.7c-10.1 46.6-19.2 87-27.8 125.5A7273 7273 0 00214.4 445v.2c-5 50.8.1 80.3 11 97.5a46.6 46.6 0 0014.6 14.7c-73.8-8.2-107.5-11.1-151.8-15L58.5 540C16.4 536.3 11 470.5 11 447c0-179 0-180.5 3.5-376 .3-16 21.1-49 44-49h181c2.6 0 5.2 0 7.8.2zm20.6.9c16.8 1.4 30.2 4.8 35.6 13.9 8.2 13.9 6.5 34 6.5 34h43c5.7 0 14.5 12.8 14 18.5-12.3 126.7-15.7 179.6-19 230.8-2.3 36.5-4.6 72.2-10 133.2-4.3 48-20.5 107.5-66.5 107.5l-13.3-1.5a43.6 43.6 0 01-28.5-19.4c-10-15.7-15.3-43.7-10.3-94.2 17.7-92 33-160.2 50.1-236.5 8.7-38.4 17.7-79 27.8-125.6a56 56 0 00-9.2-43.7 53.7 53.7 0 00-20.2-17zm46.3 447.6c-4 30.9-22.1 54-40.5 51.7-18.3-2.4-30-29.4-26-60.4s22.2-54 40.6-51.7c18.3 2.4 30 29.4 26 60.4zM69 176c-19.9-1-35.8 15.7-36.5 35.5C29 312 29 320.5 29 375c0 17.8 10.8 31.1 28.5 32.5 43.7 3.6 73.5 5.6 106 7.7l12 .8c16.2 1.1 29.2-10.5 32-26.5l3.3-18.6c11.6-66.5 14.1-81 24.7-151.4 2.7-18-5.8-40-24-40-75 0-75.5 0-142.5-3.5zm234 52.3h-3.6V221h3.5v3.6h7.2v3.6h-3.6v3.5h-3.6v-3.6zm7 0h3.6v3.5h-3.5v-3.6zm0-3.6V214h3.6v10.7h-3.5zm-3.5-3.6h-3.6v-3.5h-3.5V214h7.1v7.1zm3.6 49.9v-3.6h-3.6V264h7.1v7.1h3.6v-3.6h3.6v3.6h7v-3.6h3.6v3.6h3.6v-3.6h-3.6V264h3.6v-10.7h-3.6v-3.6h3.6v-3.5h-3.6v-3.6h3.6V239h-3.6v-3.5h3.6V214h-17.8v17.8h14.2v3.6h-7v3.5h-3.6v-3.5h-7.2v3.5h-3.5v-3.5h-10.7v-3.6h-3.6V214H278v17.8h17.8v3.6h-3.6v3.5h3.6v7.2h-3.6v3.5h3.6v-3.5h3.6v-3.6h3.5v7.1h-3.5v7.2h3.5v3.5h-3.5V271h3.5v-3.6h3.6v3.6h3.6zm-3.6-21.4v7.2h-3.6v-7.2h3.6zm3.6 0v-3.5h7v-3.6h-10.6v7.1h3.6zm7 3.6v-3.6h-7v3.6h7zm3.6 0h-3.5v3.6h-3.6v3.5h3.6v3.6h3.6v-3.6h3.5v3.6h7.1v-3.6H328v-3.6h3.5v-3.5H328V246h-3.6v-3.6h-3.6v10.7zm0 0h3.6v3.6h-3.6v-3.6zm10.7-14.3v3.6H328v-3.6h3.5zm0-10.7v-10.6h-10.6v10.7h10.6zm-49.8 7.2H278v3.5h7.1v3.6H278v7.1h3.6v-3.5h3.5v3.5h3.6V239H285v-3.5h-3.5zm42.7-10.7h3.6V221h-3.6v3.6zm-35.6-3.6H285v3.6h3.6V221zm3.6-3.5h-10.7v10.7h10.6v-10.7zm-7.2 46.3h3.6v-3.6H285v3.6zm-7.1-10.7h17.8V271H278v-17.8zm3.6 14.2h10.6v-10.6h-10.6v10.6z"
        clipRule="evenodd"
      />
      <Path
        fill={color}
        d="M450.4 321a2.5 2.5 0 105 0h-5zm-51.3-79l25 14.4v-28.8L399 242zm56.3 79c0-12.5.2-23.8 0-33.6-.3-9.8-1-18.4-3-25.4-2.1-7.1-5.5-12.9-11-16.8-5.6-3.8-13-5.7-22.8-5.7v5a34 34 0 0119.9 4.8c4.3 3.1 7.2 7.7 9 14a101 101 0 012.9 24.3c.2 9.7 0 20.8 0 33.4h5z"
      />
      <Defs>
        <ClipPath id="a">
          <Path
            fill="#fff"
            d="M0 0h147v147H0z"
            transform="translate(391 333)"
          />
        </ClipPath>
      </Defs>
    </Svg>
  );
};

Does it solve the problem?

Interesting! Thanks... I wonder why Figma outputted that. I'm no SVG expert. So not sure who's "In the wrong"...

I'm going to try to look dipper into that issue, and if I find any others solutions I'll let you know ;)

@StefanWallin I'm not sure about the problem because when I changed that line: <G mask="url(#a)"> to <G>
Does it solve the problem? Or maybe I missed something.
This did solve the problem for me, but not quite sure what way it's "supposed" to be.

@StefanWallin I'm not sure about the problem because when I changed that line: <G mask="url(#a)"> to <G>
Does it solve the problem? Or maybe I missed something.

This did solve the problem for me, but not quite sure what way it's "supposed" to be.

Let's keep it open, and maybe folks can send some examples of how we can reproduce that issue.

Mask is not working when you put values as number or string for width, height, x and y inside the mask or its children or inside the children of the G with mask prop.
it's working for me when I use percentage only, or when I remove them.
@bohdanprog

@yousefArb
It already merged PR and should solve the problem.

linearGradient doesn't work on web unless you refresh.

Hi Dev,
I was previously using version 15.6.0 in my React Native CLI project, but I encountered issues with some SVGs not rendering properly on iOS, although they worked fine on Android. I then upgraded to version 15.7.1, but the problem persisted.
After checking in Expo, I found that the SVGs were rendering correctly there. Upon examining the version that Expo is using, I discovered it was 15.2.0. After downgrading to that version, my SVGs started working fine again.
It seems there might be a regression or compatibility issue in versions 15.6.0 and 15.7.1 affecting iOS rendering when using SvgXml.
Thanks for looking into this!

Hi @MuneebQureshi1,
Can you provide an example of your svg? It can help us to find the problem.
Thank you.

Here is my example svg.

@bohdanprog Here is my example svg.
<svg width="23" height="22" viewBox="0 0 23 22" fill="none" xmlns="http://www.w3.org/2000/svg">
<mask id="mask0_1189_3236" style="mask-type:luminance" maskUnits="userSpaceOnUse" x="2" y="9" width="18" height="13">
<path d="M2.6875 9.24609H19.3615V21.2501H2.6875V9.24609Z" fill="white"/>
</mask>
<g mask="url(#mask0_1189_3236)">
<path d="M18.1154 19.7112C18.1154 19.9939 17.8862 20.2192 17.6087 20.2192H14.0537C13.7724 20.2192 13.5483 19.9887 13.5483 19.7112V14.4172C13.5483 13.5731 12.8657 12.8892 12.0255 12.8892H9.99206C9.15185 12.8892 8.46925 13.5731 8.46925 14.4172V19.7112C8.46925 19.9939 8.24129 20.2192 7.96382 20.2192H4.39585C4.11317 20.2192 3.88912 19.9887 3.88912 19.7112V9.50879H2.87305V19.7112C2.87305 20.554 3.55434 21.2392 4.39585 21.2392H7.9508C8.79101 21.2392 9.4736 20.554 9.4736 19.7112V14.4172C9.4736 14.1345 9.70157 13.9092 9.97903 13.9092H12.0125C12.2939 13.9092 12.5179 14.1397 12.5179 14.4172V19.7112C12.5179 20.554 13.2005 21.2392 14.0407 21.2392H17.5957C18.4359 21.2392 19.1185 20.554 19.1185 19.7112V9.50879H18.1024L18.1154 19.7112Z" fill="#BF6212"/>
</g>
<mask id="mask1_1189_3236" style="mask-type:luminance" maskUnits="userSpaceOnUse" x="0" y="0" width="23" height="10">
<path d="M0 0H22.0005V9.91321H0V0Z" fill="white"/>
</mask>
<g mask="url(#mask1_1189_3236)">
<path d="M11.9909 0.504069C11.4139 0.0103626 10.5828 0.0103626 10.0057 0.504069L0 9.11983L0.660446 9.89361L10.67 1.27785C10.8641 1.11501 11.1416 1.11501 11.3305 1.27785L21.3414 9.89361L22.0005 9.11983L11.9909 0.504069Z" fill="#BF6212"/>
</g>
</svg>

I guess that issue should be resolved, here is how it looks in iOS:

@bohdanprog please, can you confirm this svg rendered properly with your fix ?
it should be like this

but I got this

the problem is with this tag 👇
<g filter="url(#filter0_d_272_19623)">
<path d="M85.8874 15.0156C83.9295 15.1394 82.094 15.9442 80.8091 17.306C80.6867 17.4298 80.5643 17.5536 80.442 17.7393C79.2794 19.1012 78.4229 20.8963 78.4229 22.8153V80.6317C78.4229 86.0172 74.1399 90.3503 68.8168 90.3503H22.0713V22.382C22.1937 20.4011 22.9279 18.6059 24.2128 17.306C25.62 15.8823 27.5168 15.0156 29.6583 15.0156H76.7097H85.6427C85.7039 15.0156 85.7651 15.0156 85.8874 15.0156Z" fill="url(#paint0_linear_272_19623)"/>
</g>

this is the svg code 👇
<svg width="121" height="124" viewBox="0 0 121 124" fill="none" xmlns="http://www.w3.org/2000/svg">
<ellipse cx="58.5" cy="51" rx="47.5" ry="48" fill="#EAEEF9"/>
<path d="M112.236 31.0882C114.491 31.0882 116.319 29.2443 116.319 26.9699C116.319 24.6954 114.491 22.8516 112.236 22.8516C109.981 22.8516 108.152 24.6954 108.152 26.9699C108.152 29.2443 109.981 31.0882 112.236 31.0882Z" fill="#EAEEF9"/>
<path d="M118.211 15.0156C119.751 15.0156 120.999 13.7564 120.999 12.2031C120.999 10.6498 119.751 9.39062 118.211 9.39062C116.67 9.39062 115.422 10.6498 115.422 12.2031C115.422 13.7564 116.67 15.0156 118.211 15.0156Z" fill="#EAEEF9"/>
<path d="M16.6731 10.4464C19.5334 10.4464 21.8521 8.10791 21.8521 5.22321C21.8521 2.33851 19.5334 0 16.6731 0C13.8129 0 11.4941 2.33851 11.4941 5.22321C11.4941 8.10791 13.8129 10.4464 16.6731 10.4464Z" fill="#EAEEF9"/>
<path d="M77.0764 24.7342H51.6846V15.0156H84.9693C85.0305 15.0156 85.0917 15.0156 85.1529 15.0156C90.3536 15.1394 94.5754 19.4726 94.5754 24.7342H83.5621" fill="#CCD4E2"/>
<g filter="url(#filter0_d_272_19623)">
<path d="M85.8874 15.0156C83.9295 15.1394 82.094 15.9442 80.8091 17.306C80.6867 17.4298 80.5643 17.5536 80.442 17.7393C79.2794 19.1012 78.4229 20.8963 78.4229 22.8153V80.6317C78.4229 86.0172 74.1399 90.3503 68.8168 90.3503H22.0713V22.382C22.1937 20.4011 22.9279 18.6059 24.2128 17.306C25.62 15.8823 27.5168 15.0156 29.6583 15.0156H76.7097H85.6427C85.7039 15.0156 85.7651 15.0156 85.8874 15.0156Z" fill="url(#paint0_linear_272_19623)"/>
</g>
<path d="M69.1213 28.2633H55.2322C54.7427 28.2633 54.3145 27.83 54.3145 27.3348C54.3145 26.8396 54.7427 26.4062 55.2322 26.4062H69.1213C69.6108 26.4062 70.0391 26.8396 70.0391 27.3348C70.0391 27.83 69.6719 28.2633 69.1213 28.2633Z" fill="#B3BFD3"/>
<path d="M48.6868 28.2633H30.576C30.0865 28.2633 29.6582 27.83 29.6582 27.3348C29.6582 26.8396 30.0865 26.4062 30.576 26.4062H48.748C49.2375 26.4062 49.6658 26.8396 49.6658 27.3348C49.6658 27.83 49.2375 28.2633 48.6868 28.2633Z" fill="#B3BFD3"/>
<path d="M60.3112 37.4235H42.2615C41.772 37.4235 41.3438 36.9902 41.3438 36.4949C41.3438 35.9997 41.772 35.5664 42.2615 35.5664H60.3112C60.8006 35.5664 61.2289 35.9997 61.2289 36.4949C61.2901 36.9902 60.8618 37.4235 60.3112 37.4235Z" fill="#B3BFD3"/>
<path d="M36.4498 37.4235H30.576C30.0865 37.4235 29.6582 36.9902 29.6582 36.4949C29.6582 35.9997 30.0865 35.5664 30.576 35.5664H36.4498C36.9392 35.5664 37.3675 35.9997 37.3675 36.4949C37.3675 36.9902 36.9392 37.4235 36.4498 37.4235Z" fill="#D4DBEC"/>
<path d="M69.1222 46.5875H58.0477C57.5582 46.5875 57.1299 46.1542 57.1299 45.659C57.1299 45.1638 57.5582 44.7305 58.0477 44.7305H69.1222C69.6117 44.7305 70.04 45.1638 70.04 45.659C70.04 46.1542 69.6729 46.5875 69.1222 46.5875Z" fill="#D4DBEC"/>
<path d="M52.725 46.5875H30.576C30.0865 46.5875 29.6582 46.1542 29.6582 45.659C29.6582 45.1638 30.0865 44.7305 30.576 44.7305H52.725C53.2145 44.7305 53.6428 45.1638 53.6428 45.659C53.6428 46.1542 53.2757 46.5875 52.725 46.5875Z" fill="#B3BFD3"/>
<path d="M60.3114 55.7477H48.1356C47.6461 55.7477 47.2178 55.3144 47.2178 54.8192C47.2178 54.3239 47.6461 53.8906 48.1356 53.8906H60.3114C60.8009 53.8906 61.2292 54.3239 61.2292 54.8192C61.2904 55.3144 60.8621 55.7477 60.3114 55.7477Z" fill="#B3BFD3"/>
<path d="M42.813 55.7477H30.576C30.0865 55.7477 29.6582 55.3144 29.6582 54.8192C29.6582 54.3239 30.0865 53.8906 30.576 53.8906H42.8742C43.3637 53.8906 43.792 54.3239 43.792 54.8192C43.792 55.3144 43.3637 55.7477 42.813 55.7477Z" fill="#D4DBEC"/>
<path d="M69.1217 64.9078H60.617C60.1275 64.9078 59.6992 64.4745 59.6992 63.9793C59.6992 63.4841 60.1275 63.0508 60.617 63.0508H69.1217C69.6112 63.0508 70.0395 63.4841 70.0395 63.9793C70.0395 64.4745 69.6724 64.9078 69.1217 64.9078Z" fill="#B3BFD3"/>
<path d="M55.1114 64.9078H40.8553C40.3658 64.9078 39.9375 64.4745 39.9375 63.9793C39.9375 63.4841 40.3658 63.0508 40.8553 63.0508H55.1114C55.6009 63.0508 56.0292 63.4841 56.0292 63.9793C56.0292 64.4745 55.6009 64.9078 55.1114 64.9078Z" fill="#D4DBEC"/>
<path d="M35.532 64.9078H30.576C30.0865 64.9078 29.6582 64.4745 29.6582 63.9793C29.6582 63.4841 30.0865 63.0508 30.576 63.0508H35.532C36.0215 63.0508 36.4498 63.4841 36.4498 63.9793C36.4498 64.4745 36.0215 64.9078 35.532 64.9078Z" fill="#B3BFD3"/>
<path d="M60.3115 74.0719H51.868C51.3785 74.0719 50.9502 73.6386 50.9502 73.1434C50.9502 72.6482 51.3785 72.2148 51.868 72.2148H60.3115C60.801 72.2148 61.2293 72.6482 61.2293 73.1434C61.2905 73.6386 60.8622 74.0719 60.3115 74.0719Z" fill="#B3BFD3"/>
<path d="M46.3006 74.0719H30.576C30.0865 74.0719 29.6582 73.6386 29.6582 73.1434C29.6582 72.6482 30.0865 72.2148 30.576 72.2148H46.3006C46.7901 72.2148 47.2184 72.6482 47.2184 73.1434C47.2184 73.6386 46.7901 74.0719 46.3006 74.0719Z" fill="#D4DBEC"/>
<path d="M48.2579 82.6758H60.6173C60.6173 84.7805 61.4739 86.6994 62.82 88.0613C64.1661 89.485 66.0628 90.2897 68.1431 90.2897H12.5258C10.4455 90.2897 8.54874 89.4231 7.20267 88.0613C5.85659 86.6994 5 84.7805 5 82.6758H41.5887C41.5887 82.6758 48.3803 82.7377 48.2579 82.6758Z" fill="#CCD4E2"/>
<path d="M101.318 76.747L93.5928 68.9619L95.3638 67.1758L103.083 74.967L101.318 76.747Z" fill="#858B9B"/>
<path d="M104.004 79.4835L98.08 73.5092C97.5853 73.0103 97.5853 72.1973 98.08 71.6984C98.5746 71.1995 99.3808 71.1995 99.8754 71.6984L105.799 77.6727C106.294 78.1716 106.294 78.9846 105.799 79.4835C105.305 79.9824 104.498 79.9824 104.004 79.4835Z" fill="#858B9B"/>
<path d="M103.582 79.8678L95.961 72.1813C95.7838 72.0027 95.7838 71.7132 95.961 71.5284L97.9091 69.5636C98.0862 69.385 98.3732 69.385 98.5564 69.5636L106.178 77.2502C106.355 77.4288 106.355 77.7183 106.178 77.9031L104.23 79.8678C104.047 80.0464 103.76 80.0464 103.582 79.8678Z" fill="url(#paint1_linear_272_19623)"/>
<path d="M84.8474 43.875C76.7617 43.875 70.209 50.4837 70.209 58.6384C70.209 66.7869 76.7617 73.4017 84.8413 73.4017C92.9269 73.4017 99.4796 66.793 99.4796 58.6384C99.4796 50.4837 92.9269 43.875 84.8474 43.875ZM84.8474 70.6671C78.3557 70.6671 73.0976 65.2779 73.0976 58.6322C73.0976 51.9865 78.3557 46.6035 84.8474 46.6035C91.3391 46.6035 96.5971 51.9927 96.5971 58.6384C96.5971 65.284 91.333 70.6671 84.8474 70.6671Z" fill="url(#paint2_linear_272_19623)"/>
<defs>
<filter id="filter0_d_272_19623" x="0.0712891" y="4.01562" width="107.816" height="119.336" filterUnits="userSpaceOnUse" color-interpolation-filters="sRGB">
<feFlood flood-opacity="0" result="BackgroundImageFix"/>
<feColorMatrix in="SourceAlpha" type="matrix" values="0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 127 0" result="hardAlpha"/>
<feOffset dy="11"/>
<feGaussianBlur stdDeviation="11"/>
<feColorMatrix type="matrix" values="0 0 0 0 0.397708 0 0 0 0 0.47749 0 0 0 0 0.575 0 0 0 0.27 0"/>
<feBlend mode="normal" in2="BackgroundImageFix" result="effect1_dropShadow_272_19623"/>
<feBlend mode="normal" in="SourceGraphic" in2="effect1_dropShadow_272_19623" result="shape"/>
</filter>
<linearGradient id="paint0_linear_272_19623" x1="53.9586" y1="13.2731" x2="53.9586" y2="91.1625" gradientUnits="userSpaceOnUse">
<stop stop-color="#FDFEFF"/>
<stop offset="0.9964" stop-color="#ECF0F5"/>
</linearGradient>
<linearGradient id="paint1_linear_272_19623" x1="95.8233" y1="74.7169" x2="106.313" y2="74.7169" gradientUnits="userSpaceOnUse">
<stop stop-color="#B0BACC"/>
<stop offset="1" stop-color="#969EAE"/>
</linearGradient>
<linearGradient id="paint2_linear_272_19623" x1="70.1956" y1="58.6416" x2="99.485" y2="58.6416" gradientUnits="userSpaceOnUse">
<stop stop-color="#B0BACC"/>
<stop offset="1" stop-color="#969EAE"/>
</linearGradient>
</defs>
</svg>

Hello @yousefArb,
I guess here you can find the answer to your question.

here

Which react native svg versions are you using?

#2422 (comment) @bohdanprog Which react native svg versions are you using?

I ran your example from the main branch.
I believe we are going to release a new version soon.

The problem is still there. I have to get 2 copies of the same image with different names. It doesn't load in a different route page when using react native navigations.

@djaffer Can you provide a repro of how we can reproduce that problem?


Provide an arm64 image on Docker Hub

Could you possibly provide an arm64 image on Docker Hub? Right now I am able to use this project on an arm64 system, but I need to build it myself, which is less convenient. It also requires a few changes to build successfully due to grpcio limitations. There are 2 options:

Add linux-headers package before installing the requirements, as it's needed to build the grpico wheels which are not available for arm64 alpine/musl systems. Unfortunately, while this works, it takes a very long time to build.
Switch to a slim-buster base python image instead of alpine, which has the necessary wheels pre-built already. While the resulting image will be larger, the build time is much smaller.

For a single use (i.e. building manually) the 2nd option makes more sense. However, if add an arm64 image build as part of CI/CD for Docker Hub (not sure how it's set up here) the 1st option is probably better.

Hi there, could you please elaborate on how you're currently using this project in your system? Do you also use Reva or do you use local storage?
Currently we do not support arm64, but a priori it is not complex to extend the CI for this build, especially now that it is based on standard GitHub actions.

Hi, I'm using wopiserver for OwnCloud Infinite Scale integration setup as shown in this example docker-compose. It does seem to use Reva, although I'm not too sure how it works in general. Everything else in that setup provides arm64 images, the only thing that currently needs to be build manually is wopiserver.

I see, indeed you're using Reva behind oCIS.
I'd invite you to extend the release.yml CI script to build an extra image on top of the 2 existing ones, maybe only on tags (so even if it takes a long time it's not for every single commit). As said arm64 is currently not supported and we don't plan to make and test such build, but I'm happy to review a PR for it.

I've submitted the PRs of my attempt, not sure if it's correct as I've never worked with GitHub CI before and wasn't able to test it.
Also, since opening this issue I've actually switched the oCIS host to a x86 host, as the arm64 host I had was not powerful enough to run it well. Hopefully the PRs work well, but if not, perhaps someone else can take over them in the future if they need an arm64 image.

hi @Tomaszal
oCIS already builds ARM compatible docker containers which include Reva.
https://hub.docker.com/layers/owncloud/ocis/2.0/images/sha256-4afac6637e393be506bb11797bac3928496fada21fb49e6adcf4f67ee5590a78?context=explore

Hi @micbar, I'm aware that oCIS already has an ARM image and it works great on its own. However, as I understand, an ARM wopiserver image is still needed to integrate OnlyOffice/Collabora with oCIS, as shown in this example.


Weird Unmovable scroll bar in the tablist section

I have checked the following:

[X] I use the newest version of bruno.
[X] I've searched existing issues and found nothing related to my issue.

Describe the bug
There's a scrollbar-like bar appearing in my request tablist. (Check Screenshot)
noticed this too in v1.16.1
.bru file to reproduce the bug
No response
Screenshots/Live demo link

On which OS, mac, windows of linux ?

On which OS, mac, windows or linux ?

Linux.

has anyone else the problem ?
i don't but i am on windows

On which OS, mac, windows or linux ?

Linux.

Looks like a custom theming problem. Are you using native or flatpak variant? I'd hope flatpak will not be affected regardless of what customisations are happening in the DE.

Looks like a custom DE theming problem

wow, don't know why i didn't think it could be my theme. I'll try to remove it entirely to see if it's the cause. (my theme is Adwaita)

Are you using native or flatpak variant?

Hyprland is my WM and I use the native variant of bruno or at least the one that's in the nixpkgs repository.

I saw those scrollbars after upgrading Electron to version 29. They were caused by weird Bruno styling and the Chrome update.
Maybe the variant from NixOS also upgraded Electron.
I will try to look into it tomorrow.

I saw those scrollbars after upgrading Electron to version 29 on my Lazer fork. They were caused by weird Bruno styling and the Chrome update.

ahhh, I see.

Maybe the variant from NixOS also upgraded Electron. @noornee Could you open Bruno's Chrome DevTools and check the Chrome / Electron version?

Sure. I just did and yep, you're right.
The electron version on my machine is v.29

I will try to look into it tomorrow.

Alrightt, Thank you!

I looked into the Nix build file: https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/br/bruno/package.nix and the electron version in indeed overwritten:
https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/br/bruno/package.nix#L100-L112

Woww, pheww!.
Guess I'm going to open an issue in the nixpkgs repository to tell them to pin a specific version of electron for bruno.
Thanks for narrowing out the source of this bug @Its-treason 🕵
By chance, do you know the version of electron that bruno uses or atleast the last working electron version that didn't affect bruno's request tablist ui?
I modified the bruno package file and tried to build it locally using electron v28 on my machine but i had some errors that i couldn't stay to resolve, was running late to school. I'll look into it properly when i get home though. my best bet is that it's because i replaced every occurrence of the word electron with electron_28 and it messed some things up

I managed to reproduce it using the latest version of electron and I see how to fix it, I am making a PR

I managed to reproduce it using the latest version of electron and I see how to fix it, I am making a PR

that's awesome!

Can I ask you @Its-treason to review my PR ?

Closing this issue as resolved. Please use the v1.26.2 version of bruno which contains the fix.


[environment] can't update environment variables

Steps to reproduce
Install powershell from microsoft store

[environment]::setEnvironmentVariable('TEST_URL','http:url','User')

Expected behavior
$env:TEST_URL

output: http:url
Actual behavior
$env:TEST_URL

output is empty
Environment data

Name                           Value
----                           -----
PSVersion                      7.1.0
PSEdition                      Core
GitCommitId                    7.1.0
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

I believe it is MSIX sandbox limitation.

@iSazonov
Right，Please provide the necessary description in the instructions.

This behaviour is normal. $env:VAR only retrieves values from the current process environment.
Updating a user-scope environment variable never updates the current process environment; you have to do that explicitly, in either of the following ways:
$env:TEST_URL = [Environment]::GetEnvironmentVariable('TEST_URL', 'User')
# or
[Environment]::SetEnvironmentVariable('TEST_URL', [Environment]::GetEnvironmentVariable('TEST_URL', 'User')

You can also opt to simply set it in the current process environment first, or do both at once:
# current environment first
$env:TEST_URL = 'http:url'
[Environment]::SetEnvironmentVariable('TEST_URL', $env:TEST_URL, 'User')

# both at once
[Environment]::SetEnvironmentVariable('TEST_URL', ($env:TEST_URL = 'http:url'), 'User')

@vexx32

There may still be an MSIX specific limitation in play here, but the steps in the issue description will not work as expected in any version of PowerShell.

The ‘reopen shell’ operation that I missed in the issue description
Now, i can understand MSIX specific limitation.
run command in powershell installed from msix, and reopen shell and see $env:TEST_URL

run command in windows powershell, and reopen shell and see $env:TEST_URL

If you open new session it is as any process works and as @vexx32 said it is not MSIX specific.

@iSazonov This is MSIX specific. The MSIX sandbox virtualizes some registry access. [Environment]::SetEnvironmentVariable('TEST_URL', 'http:url', 'User') writes the value to the User registry, which is virtualized. So the change is not persistent across sessions.


[Snyk] Upgrade eslint from 8.31.0 to 8.32.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade eslint from 8.31.0 to 8.32.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 22 days ago, on 2023-01-15.

Release notes

Package name: eslint

8.32.0 - 2023-01-15Features

fc20f24 feat: add suggestions for redundant wrapping in prefer-regex-literals (#16658) (YeonJuan)

Bug Fixes

b4f8329 fix: ignore directives for no-fallthrough (#16757) (gfyoung)

Documentation

17b65ad docs: IA Update page URL move (#16665) (Ben Perlmutter)
5981296 docs: fix theme switcher button (#16752) (Sam Chen)
6669413 docs: deploy prerelease docs under the /docs/next/ path (#16541) (Nitin Kumar)
78ecfe0 docs: use inline code for rule options name (#16768) (Percy Ma)
fc2ea59 docs: Update README (GitHub Actions Bot)
762a872 docs: Update README (GitHub Actions Bot)

Chores

2952d6e chore: sync templates/*.md files with issue templates (#16758) (gfyoung)
3e34418 chore: Add new issues to triage project (#16740) (Nicholas C. Zakas)

8.31.0 - 2022-12-31Features

52c7c73 feat: check assignment patterns in no-underscore-dangle (#16693) (Milos Djermanovic)
b401cde feat: add options to check destructuring in no-underscore-dangle (#16006) (Morten Kaltoft)
30d0daf feat: group properties with values in parentheses in key-spacing (#16677) (Francesco Trotta)

Bug Fixes

35439f1 fix: correct syntax error in prefer-arrow-callback autofix (#16722) (Francesco Trotta)
87b2470 fix: new instance of FlatESLint should load latest config file version (#16608) (Milos Djermanovic)

Documentation

4339dc4 docs: Update README (GitHub Actions Bot)
4e4049c docs: optimize code block structure (#16669) (Sam Chen)
54a7ade docs: do not escape code blocks of formatters examples (#16719) (Sam Chen)
e5ecfef docs: Add function call example for no-undefined (#16712) (Elliot Huffman)
a3262f0 docs: Add mastodon link (#16638) (Amaresh  S M)
a14ccf9 docs: clarify files property (#16709) (Sam Chen)
3b29eb1 docs: fix npm link (#16710) (Abdullah Osama)
a638673 docs: fix search bar focus on Esc (#16700) (Shanmughapriyan S)
f62b722 docs: country flag missing in windows (#16698) (Shanmughapriyan S)
4d27ec6 docs: display zh-hans in the docs language switcher (#16686) (Percy Ma)
8bda20e docs: remove manually maintained anchors (#16685) (Percy Ma)
b68440f docs: User Guide Getting Started expansion (#16596) (Ben Perlmutter)

Chores

65d4e24 chore: Upgrade<EMAIL_ADDRESS>(#16729) (Brandon Mills)
8d93081 chore: fix CI failure (#16721) (Sam Chen)
8f17247 chore: Set up automatic updating of README (#16717) (Nicholas C. Zakas)
4cd87cb ci: bump actions/stale from 6 to 7 (#16713) (dependabot[bot])
fd20c75 chore: sort package.json scripts in alphabetical order (#16705) (Darius Dzien)
10a5c78 chore: update ignore patterns in eslint.config.js (#16678) (Milos Djermanovic)

    from eslint GitHub release notes

Commit messages

Package name: eslint

d8c8ede 8.32.0
99ad3d4 Build: changelog update for 8.32.0
17b65ad docs: IA Update page URL move (#16665)
b4f8329 fix: ignore directives for no-fallthrough (#16757)
5981296 docs: fix theme switcher button (#16752)
6669413 docs: deploy prerelease docs under the `/docs/next/` path (#16541)
2952d6e chore: sync templates/*.md files with issue templates (#16758)
78ecfe0 docs: use inline code for rule options name (#16768)
3e34418 chore: Add new issues to triage project (#16740)
fc2ea59 docs: Update README
fc20f24 feat: add suggestions for redundant wrapping in prefer-regex-literals (#16658)
762a872 docs: Update README

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (ef73899) compared to base (11bb451).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##            master       #55   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines          126       126
  Branches        11        11
=========================================
  Hits           126       126

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

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


Append release notes to changelog instead of overwrite

Hello!
I'm wondering if there's a way to simply append the latest release notes to the changelog instead of overwriting the entire changelog. I'm asking because, at the beginning of the project, I didn't follow the correct commit message format, resulting in most of them being unrecognized. My solution was to manually update the changelog for those incorrect commit messages. I thought it would update the changelog based on the previous version, but it instead overwrites the entire changelog, causing the unknown section to reappear. If this is not currently possible, I believe it could be a beneficial feature, as it would make the changelog neater (I've noticed that the changelog for this repo also includes an unknown section in earlier versions).
Thank you in advance!

@Rebekah-Chuang, unfortunately there is not a current method for only prepending the latest release information. I do believe there was a previous ticket that mentioned this but it seems nothing specifically came of it. I  agree it would be a useful feature to provide methods of adoption of this project to an existing project.

Hi @codejedi365, sorry for the late response, thank you so much for replying, I think the ticket you mentioned was #722. Hope to see this feature in the future!

@Rebekah-Chuang, given the complexities discussed in #722, I'm not sure if or when this feature would actually be solved, but there's may be an alternative.
You could use the changelog template directory, to write a custom template which does not loop through all of the versions as the provided default does.  Jinja2 also provides the ability to import other files and macros. Potentially, you could correct your changelog for the previous versions and store that as a file such as 3.x_CHANGELOG.md. Then in your custom changelog template abort the loop when the version matches 3.x and just import the other file and append it. This is a bit exploratory as I have not done this myself but thinking about it now I believe it accomplishes what you need.

Still in the backlog however as I'm reviewing the changelog architecture and the performance of PSR, I am finding this issue to be one of more importance and I might of devised a way to make this a reality. Hopefully over the next few months I can implement a solution.

I have found a solution that works for re-introducing the placeholder version update for changelogs using jinja. It will be released as a default changelog variation (toggled by a config option, changelog.mode) soon in v9. If you have a custom template configuration, you will need to modify your templates for the newly provided context variables for use.
My plan is to converted the placeholder functionality back to the default in v10. Stay tuned.

:tada: This resolution has been included in version 9.10.0 :tada:
The release is available on:

PyPi package
GitHub release

Check out the Changelog Templates in the documentation to learn about the "update" mode.


Resolve warnings by check_colors.vim

:so $VIMRUNTIME/colors/tools/check_colors.vim

---------------
    colors_name: OK
       filetype: Should not define: cssBraces diffAdded gitmessengerEndOfBuffer graphqlName helpHyperTextJump htmlArg jsonQuote markdownBold phpVarSelector pythonFunction r
ubyDefine sassClass shFunction swiftIdentifier typescriptAjaxMethods vimContinue xmlAttrib yamlKeyValueDelimiter
---------------

Hmm... do I  really have to remove those definitions? I think that the default linking structure of Vim is not perfect in all cases so I want to fine-tune them for the best user experience...🤔

I'll think about it later.

Related: https://github.com/vim/vim/issues/4996#issuecomment-537394559


Update croatia zambia phone formats

This pull request updates mobile, landline and special phone number formats for Croatia and Zambia , it is based on the information from
https://github.com/googlei18n/libphonenumber/blob/master/resources/PhoneNumberMetadata.xml

Coverage increased (+0.003%) to 99.178% when pulling c0a38dfa9cf9e3bb2132864772e7a7ba39d203b6 on surgeventures:update-croatia-zambia into f2e897d9673f5fc3a4f14273d5a3843a86b939cf on floere:master.

@floere Is there a chance to merge it this week?

@floere Ping

@saner @ronin Croatia fails on Phony.refute.plausible?('+385 91 123456') # Too short and Phony.refute.plausible?('+385 21 1234567') # Too long. Any ideas?

@saner @ronin For now I've adapted the plausibility specs for Croatia to the definition. Please let me know if they are correct.

Thanks so much, @saner! 😊 Released in 2.15.45 🚀

Thanks @floere!


Is it possible that PINs starting with 0 don't work?

Hi, I'm setting up my Precursor. I've run ./factory-reset.sh three times now, the first time set a pin starting with 4 (4 digits), which worked fine on future unlocks. I ran ./factory-reset again today after a git pull because I was getting a confusing message about the ecup version being old, not letting me get on wifi. So I did that and set the PIN to another four digit code -- 0101. It wouldn't accept it on future unlocks. I thought I had mistyped it, so did ./factory-reset a third time and this time turned on the "show password as I type" and ensured it was 0101, and it will not accept it again on future unlocks. Is there a chance something about this PIN is not working?

It's not the 0-led PIN, just any PIN. I can't seem to get it to remember the pin. My process:
(0) Pull the latest xous-core, cd into tools
(1) Connect USB C cable
(2) In ubuntu20, run sudo ./factory-reset.sh -s
(3) When that finishes, hit the reset button
(4) Unplug USB
(5) On the device, type ecup auto
(6) Plug in USB again to reboot the device
(7) Menu-> initialize root keys
(8) Type a pin of 0101 and then the more secure password
(9) Reboot, try 0101, it does not accept it

Ah right. When you say "it does not accept the PIN" on reboot, this is because it's popping up a box that's offering you to format the PDDB?
In which case, this is actually the "expected behavior" but poorly explained by the UX. Basically once you have provisioned the root keys, the device will try to mount its storage. However, the storage needs to be cryptographically wiped before use, which is a long process - about 10-15 minutes -- so we don't link it to the root key provisioning process.
So I think what you're seeing here is that dialog box which is asking you to to provision the PDDB. It uses the less secure PIN just to tie the basic system storage down, but then you would layer more secure passwords onto deniable Bases that would contain data that truly needs securing. Once you've got the PDDB initialized, that dialog box won't pop up a failure, and instead, it'll just go away.
To wit, the only function of the PDDB at the moment is to store your wifi SSID and password -- we haven't put much user-friendly infrastructure in place to deal with new cryptographic Bases or other properties yet.

Hm right, I just tried to reproduce it and I don't get a prompt to enter a PIN on reboot. Is it easy for you to take a photo of the prompt that's asking you for a PIN on reboot? It shouldn't ask for that until you've done something to the PDDB.

Ah. I see one bug. A recent change to the factory reset script skipped the part where the PDDB is also wiped, so that would contribute to your confusion. I've gone and fixed that.

Aha! I think I understand it all now. And yep, I just pulled the latest and went through it all again and everything works as expected. Thanks so much !!


Cb 286 run m gottschalkii samples through rna seq pipeline on tower

What type of PR is this? (check all applicable)

[x] 🐛 Bug Fix
[x] 🔥 Performance Improvements

Description
Some fixes I needed to make to run the M. gottschalkii samples through the pipeline on the Tower:

increased sortmerna's default min memory requirements so that it doesn't choke at the end of the task.
made the channel for the pre-made silva db index reusable so that it's not exhausted on the first sample.

Jira Task
CB-286.
Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📕 notebook(s)
[x] 🙅 no documentation needed

Code Quality

[x] 🎯 The code is properly formatted and adheres to the project's style guide
[x] 🎯 The code runs without any errors or exceptions

Compute Environment
The Tower.
Testing
None needed. See complete run here and the MultiQC report here.

AM I reading the MultiQC report correctly, that there are only ~5% unique reads? Is this expected due to the read depth or does it indicate a problem with the library prep or sequencing?

Yes, I think you're reading it correctly. I'm still working on interpreting it myself, but I do think high levels of duplication are to be expected because of the read depth (in addition to it being RNA-Seq). The DupRadar graph gives some good insight to this:

Of the three samples, it seems like sample 82 has a lower quality library than the other two.


chore: Merge chore_release_7.0.1 so far into edge

Merging chore_release-7.0.1 so far into edge, to try to fix G-code testing. I'm hoping the failures on edge are just the same ones that https://github.com/Opentrons/opentrons/pull/13670 fixed for chore_release-7.0.1.
Review requests
I manually resolved conflicts in these files:

app/src/organisms/Devices/PipetteCard/__tests__/PipetteOverflowMenu.test.tsx
app/src/organisms/Devices/PipetteCard/index.tsx

Make sure those look sensible.

Reminder to self to do a normal merge, not a squash merge.