Fixing a typo

Fixed a small typo in graph_properties.cc
Fixes the issue #56618

Please fix more than just one single typo. Fix all typos in a file/directory.

Hi @sushreebarsa, As @mihaimaruseac suggested above,  It is better to submit multiple typo fixes in a single PR as the CPU/GPU hours are wasted on CI. Hence, we do not encourage one liner grammatical changes as it is an expensive process. Thank you for your contribution!


Fix broken headings in Markdown files

GitHub changed the way Markdown headings are parsed, so this change fixes it.
See bryant1410/readmesfix for more information.
Tackles bryant1410/readmesfix#1

Codecov Report

Merging #155 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #155      +/-   ##
==========================================
+ Coverage   99.58%   99.58%   +<.01%
==========================================
  Files          10       10
  Lines         480      481       +1
==========================================
+ Hits          478      479       +1
  Misses          2        2


tfrobot: use ninja gridproxy for mainnet network

when the user choose mainnet network override the proxy url to the ninja proxy (unless the user specifies NO_NINJA_PROXY_URL) in the TFPlugin initialization

Verified:
Using tcpdump, requests can be seen when filtering on ninja host:
$ sudo tcpdump host gridproxy.bknd1.ninja.tf --count
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on wlp0s20f3, link-type EN10MB (Ethernet), snapshot length 262144 bytes
23 packets captured
31 packets received by filter
0 packets dropped by kernel

When setting NO_NINJA_PROXY_URL=true:
$ sudo tcpdump host gridproxy.bknd1.ninja.tf --count
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on wlp0s20f3, link-type EN10MB (Ethernet), snapshot length 262144 bytes
0 packets captured
4 packets received by filter
0 packets dropped by kernel

Notice packets captured in both cases.

Note: filtering on gridproxy.grid.tf will result in packets being captured in both cases as relay uses the same IP so it results in tcp requests being captured even when not using gridproxy.grid.tf.

@AbdelrahmanElawady excellent verification


seaport.createOrder don't work

Hello, this is my code but i don't get any error message and seaport dont list my NFT:
`const Seaport = require("@opensea/seaport-js").Seaport;
const ethers = require("ethers").ethers;
const provider = new ethers.providers.JsonRpcProvider(
"https://eth-mainnet.g.alchemy.com/v2/MY_ALKEMY_API_KEY"
);
const signer = new ethers.Wallet("MY_WALLET_PRIVATE_KEY", provider);
const seaport = new Seaport(signer,{seaportVersion:"1.4", apiKey: "MY_OS_API_KEY"});
const offerer = "MY_WALLET_ADDRESS";
async function main(){
const { executeAllActions } = await seaport.createOrder(
    {
    offer: [
        {
        itemType: 2,
        token: "CONTRACT_ADDRESS",
        identifier: "TOKEN_ID",
        },
    ],
    consideration: [
        {
        amount: ethers.utils.parseEther("10").toString(),
        recipient: offerer,
        },
    ],
    },
    offerer
);

const order = await executeAllActions();

}
main()`
Can someone help me?
Thank you in advance

what is the error you're getting? i am able to createOrder() and executeAllActions(), but i get stuck on fulfillOrder()


fix: adding REST endpoint details and domain name for RPC

Added domain name to RPC endpoint
Added REST endpoint.

Kindly review and merge @JeremyParish69
Thanks

Fixed


Enhancementoptimize groupExpressionMatch

Proposed changes
Issue Number: close #xxx
Problem summary
optimize groupExpressionMatch by reducing unnecessary iterator creation.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[x] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[x] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

many conflict and need to rethink how to do it


Can there be some simple installation instructions?

I'm not familiar with C... could you provide the README with some bash commands to execute in order to install the quicklook plugin?
That would help a lot!
Thanks

Install instructions are with the built download - see the releases page for details, just copy matlab.qlgenerator where directed.


Ctrl + x stops working and defaults to ST after some time

Hi Thanks for creating this plugin.
I am facing this problem that after starting ST with your plugin and few others, everything works fine but after some time, Pressing Ctrl+x starts clearing lines.. which i think is default for ST.
I could not figure out exactly how/when it was happening as it seems to be quite random.
But this workflow is consistent :

This happens everytime when i try to undo with ctrl+x, u
expecially after some snippet is evaluated.

Hope to make it work, as it makes me disable your plugin. :(

I am having the same problem. This behavior prevents using of any command starts with ctrl-x, like Save. Another problem I have is the ctrl-v, instead of page down it keep doing Paste.

Is this st2 or st3? Is it still a problem?

I ran into this same issue today.  On Windows, I installed ST3 build 3103 and then sublemacspro and started editing files as a trial run before buying a license.  Periodically when saving files on an unregistered ST3 it pops up a dialog box asking if you would like to buy a license now.  As soon as that happens the ctrl-X key binding reverts to ST3 (windows cut) and won't come back until you disable/enable sublemacspro.
I ended up buying a license.  Now no more pop-ups and no more ctrl-X unbinding.

This bug is still occurring for me on windows. I have purchased a license but the functionality still seems to time out. Any ctrl+x,{anything} commands no longer function (line gets cleared, then the following key combo is executed independently.  I need to do a full remove/install to get it working again.

I wish I could help you guys. Is it just sublemacspro plugin that stops working?

Actually I realized that it was a pop up for the SFTP plugin (which I have not gotten around to purchasing) that was breaking ctrl+x (after purchasing the ST3 license). Fortunately with the SFTP pop up, closing the window causes sublemacs to resume functioning (whereas with the ST3 popup you needed to remove/install the package ). I guess this must be a ST3 issue...


feat(#minor): mm-finance; added matic mm-finance subgraph

Added support for mm-finance polygon subgraph. Deploys on merge because it syncs super fast.
For deploy (and readme subgraph link) to work, the subgraph needs to be created first at the hosted service. I've named itmm-finance-polygon. I've tried to do it from the graph-cli but can't get it to work, might not be possible? If you could check @this-username-is-taken 💪
Demo of the sync: https://subgraphs.messari.io/subgraph?endpoint=https://api.thegraph.com/subgraphs/name/jaimehgb/mm-finance-polygon&tab=protocol

Great work!


Vimeo: Dolby Vision HEVC style dvh1.08.03 prints "WARNING: Unknown codec"

Checklist

[ x] I'm reporting a site feature request
[ x] I've verified that I'm running youtube-dl version 2021.06.06
[ x] I've searched the bugtracker for similar site feature requests including closed ones

Description

HLG type of Dolby Vision is now supported by Vimeo
https://vimeo.com/601088734
https://www.engadget.com/vimeo-dolby-vision-support-171019651.html
https://vimeo.zendesk.com/hc/en-us/articles/115015301027-Watching-HDR-Videos
Yet that is just RPU (without EL) Dolby Vision of profile 8. Why it is not supported, it is just hevc?
 And it is just useless AVC.

ok so close the issue then...

https://user-images.githubusercontent.com/31514790/132992690-2d37d172-0914-40c6-971d-2952fbec2f36.mp4
How this looks like (HEVC so will play only in Chromium Edge).
That is on  my account here: https://vimeo.com/manage/videos/603250902


feat(minimal-blog): allow customization of texts

Hi! 👋
I've been adopting this theme to a personal project but since it's in Brazilian Portuguese, I felt the need to customize some of the texts.
Please let me know if this is a desired change or if any of the changes can be improved.

Hi, thanks for the PR!
Unfortunately I won't merge it as I don't want to increase the API surface more than necessary. Since you shadow both these files I'd advise to do that instead. The shadowing API can be a bit daunting at the beginning, reading the docs should give you some help :)
Thanks for using the theme!

Hi @LekoArts, no worries. I have one question though: Is it possible to shadow the templates? I did with the hero and bottom sections easily - as stated in the README, but failed to do it with the post layout, for example.


CompilationDependencyResolver should operate on known list of CSX files

OmniSharp finds the CSX files once, we can avoid the extra scanning.
Also, OmniSharp allows users to exclude paths from scanning and we should respect that (at the moment we will find those CSX files).
fixes #279

LGTM. Have you tested this from OmniSharp too? 😀

I will after we merge 😄


fix: upgrade to version 3.1.102

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign daveconde
You can assign the PR to them by writing /assign @daveconde in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign daveconde
You can assign the PR to them by writing /assign @daveconde in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
f0a1f946315c4a82669d0044383d0b0d6ec878c3
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
f0a1f946315c4a82669d0044383d0b0d6ec878c3
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
f0a1f946315c4a82669d0044383d0b0d6ec878c3
link
/test kube

tls
f0a1f946315c4a82669d0044383d0b0d6ec878c3
link
/test tls

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
f0a1f946315c4a82669d0044383d0b0d6ec878c3
link
/test kube

tls
f0a1f946315c4a82669d0044383d0b0d6ec878c3
link
/test tls

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/retest

/retest

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

tls
f0a1f946315c4a82669d0044383d0b0d6ec878c3
link
/test tls

kube
f0a1f946315c4a82669d0044383d0b0d6ec878c3
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

tls
f0a1f946315c4a82669d0044383d0b0d6ec878c3
link
/test tls

kube
f0a1f946315c4a82669d0044383d0b0d6ec878c3
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/retest

/retest

/test kube

/test kube

🎉

🎉

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
f0a1f946315c4a82669d0044383d0b0d6ec878c3
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
f0a1f946315c4a82669d0044383d0b0d6ec878c3
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


Add option to ignore install_cran_packages.sh and install_pip_packages.sh

Currently these two scripts always get generated and are placed in the same directory as environment.yml. Add option to ignore the generation of these two files

In the newest version, they are simply not executed. Should fix #5 first.

Maybe that's the solution?
https://stackoverflow.com/a/72395091/8792159
Possibly also interesting for the neurodocker folks?

Or that, or that

Both of them seem to work, so one can either do this:
CONDA_BASE=$(conda info --base)
source $CONDA_BASE/etc/profile.d/conda.sh

or this:
eval "$(conda shell.bash hook)"`

after this, we use RScript -e to run R-code from bash:
conda activate test_pip && Rscript -e "install.packages(c('PMA','lme4'),repos = 'https://cloud.r-project.org')"

we also define repos = 'https://cloud.r-project.org' because otherwise we would get stuck with choosing mirror

Implement this:
def write_cran_installation_script(df,yaml_name,cran_mirror="https://cloud.r-project.org"):

    '''Create a file 'install_cran_packages.sh' that activates the environment
    and installs all CRAN-packages in that environemnt'''

    # subset dataframe to CRAN-packages
    df = df.loc[(df['language'] == 'R') & (df['package_manager'] == 'cran'),:]

    # parse list of CRAN-packages to a single string with packages separated by comma
    cran_packages = ','.join(f"'{package}'" for package in df['package_name'])

    # write bash script
    # 1.) Activate conda environment from within bash-script suggested here:
    # https://github.com/conda/conda/issues/7980#issuecomment-472648567
    # # 2.) Use RScript to install packages within conda environment. Use default mirror
    # otherwise script will halt because we would have to choose one:
    # https://stackoverflow.com/questions/50870927/using-install-packages-inside-a-shell-script-through-terminal-to-automatically
    with open('install_cran_packages.sh','w') as f:
        f.write('#!/bin/bash\n')
        f.write("CONDA_BASE=$(conda info --base) && source $CONDA_BASE/etc/profile.d/conda.sh\n")
        f.write(f"conda activate {yaml_name} && Rscript -e \"install.packages(c({cran_packages}),repos=\'{cran_mirror}\')\"")


workflows: Update build and deploy to 0.0.6

This adds support for build and deploy of ESR tags.
Change-type: patch
Signed-off-by: Alex Gonzalez<EMAIL_ADDRESS>

@resin-jenkins retest this please

@resin-jenkins retest this please

@balena-ci I self-certify!

@resin-jenkins test this please

@resin-jenkins test this please

@resin-jenkins retest this please


Out of range error in paired end mode

Hi,
I've been trying to use strobealign from source using the current head, and have ran into a few issues. Maybe the solution is just wait for the stable release 😉
The first is trying to use the pre-generated index approach with  strobealign ARS.fa.sti R1.fq.gz R2.fq.gz --use-index. I get this error, so presumably it just isn't picking up the fact its an index file and not a fasta file.
strobealign: FASTA file must begin with '>' character, not 'S')

The second one is if I run with just a normal fasta reference and paired reads, and then get a range error a couple minutes into alignment. This doesn't appear to happen when using the single end mode, so might be related #16?
This is strobealign v<IP_ADDRESS>-529-gbd661fe
Estimated read length: 149 bp
Time reading references: 3.59 s
Indexing ...
  Time generating seeds: 68.38 s
  Time sorting seeds: 68.68 s
  Time generating flat vector: 4.68 s
  Time generating hash table index: 46.21 s
Total time indexing: 189.08 s
Running in paired-end mode
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::substr: __pos (which is 18) > this->size() (which is 17)

Best,
Alex

Hi Alex,
As for the first issue, I will simply wait for @marcelm's answer. He is doing most of the development at the moment, particularly with the separate indexing.
As for the second issue, do you get the same error if you use the last release 0.7.1?
To track down the second issue, it would be great if we could get access to the reads and genome. Is it possible?
Best,
Kristoffer

I tried with the release v0.7.1 and that also has the same error.
The short reads are available here and this is the reference.

Hi, thanks for trying out strobealign! We should soon be close to a somewhat stable release; thanks for reporting issues, that really helps us.
With --use-index, you should not provide the name of the .sti file, but the name of the FASTA file. Strobealign will add the .sti extension to get the name of the index file. I’ll make this clearer in the documentation.
I’ll have a look at your data, thanks for posting it.

Thanks for the great test case! I was able to reproduce the problem now. It should be fixed by PR #187 (branch has-shared-substring).

Yep, just pulled that PR and it works now on 2 datasets that failed before with that error, so this looks resolved.
Thanks!
P.S.
I was piping the results through multiple samtools commands to mark duplicates, but the whole process was 2.55x faster and used 20% less memory when swapping out bwa-mem2, so this aligner is seriously fast!

Thanks for reporting! Any feedback is welcomed :)


Trailing space in input causes "command not understood"

A trim should be run over prop.input.command to ensure trailing spaces entered during the heat of battle are ignored.

@chrisbrownie, thanks for the report :smile:


Release v0.8.1

New release for removal of derivative (backwards compatible) and smallvec change (also backwards compatible):

https://github.com/sigp/ethereum_ssz/pull/38

CI failed to publish due to a race: ethereum_ssz_derive was not available for download when ethereum_ssz tried to publish. And re-running CI does not work in this case to fix it. We should maybe add a delay
I've manually published ethereum_ssz for now


Is it possible to have a django cronjob only be ondemand?

RUN_EVERY_MINS=0 will make it run every time, deleting Schedule doesn't error out but fails according to the traceback in the cron job logs, and deleting code errors out.
I want to standardize some of my django management commands all to use django_cron, but I don't want to run them on a schedule.
Is it possible to create a django cronjob that only runs if I explicitly run it through python manage.py runcrons 'some_cron_job'?

The best way to set this up would be to set RUN_EVERY_MINS = None and remove the cron from CRON_CLASSES.
When you want to call the cron, pass in the force option:
python manage.py runcrons 'some_cron_job' --force

Oh yeah, forgot about None. Thanks @msopko81 .


Add URI paths for cluster stats filtering.

Description
Documentation change for new cluster stats URI path for filtering requested metrics.
Issues Resolved
Closes https://github.com/opensearch-project/documentation-website/issues/8527
Version
_List the OpenSearch version to which this PR applies, e.g. 2.18
Frontend features
If you're submitting documentation for an OpenSearch Dashboards feature, add a video that shows how a user will interact with the UI step by step. A voiceover is optional.
Checklist

[ ] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@Naarcha-AWS Can you please let me know what would be the next steps for this PR or any action is pending on me?

@Naarcha-AWS Can you please let me know what would be the next steps for this PR or any action is pending on me?

@SwethaGuptha: No other action is required on your part at this time! There's a chance we might have a couple of follow up questions about the PR, but we'll ping you directly on a comment if that's the case.

@natebower: Implemented your review. Let me know if I missed anything.


Unmounting the scss file added to Angular.json

Question
Hello, I'd like to understand how I could unmount the CSS that we added to the angular.json file.
This is what I have in my Angular.json file.
"styles": [
              "src/styles.scss"
            ],

My setup basically loads whether the Angular application or a React application depending on the route.
Basically, what I see is that the styles added to this main styles.scss are still in the DOM after the Angular app gets unmounted.
How can I remove that?
Environment

Libs:
- @angular/core version: 16.2.1
- single-spa-angular version: 9.0.1

We faced the same issue, solved it with wrapping the selectors in the global styles in additional selectors.
They do not unmount, but at least they affect only what they should.
app-root, .cdk-overlay-container {
   ...rest of styles
}

https://single-spa.js.org/docs/ecosystem-angular/#unmountable-styles


Downsample RGB colors for viewers who can't see them

With the latest Minecraft client, we can send texts in any RGB color, rather than the previous space of only 16.
Full color isn't supported by every viewer of our text -- commonly used console libraries convert to ANSI based on legacy color codes, and we target clients all the way back to MC 1.8.
When unsupported colors are passed to the legacy serializer, it fails locally with an exception.
When unsupported colors are sent to players, the color will be stripped entirely and players will see white text.
Users of the API could only avoid these issues by tracking the capabilities of every individual version they target, or by not using RGB at all.
I've added some API, currently on NamedTextColor, to find the nearest legacy color from any RGB color, but it is not yet used in any of the serializers. I'm also not entirely satisfied with the algorithm used -- it tends to favor the grays, as relatively "average" colors numerically.
How should the different serializers handle it?

This is done.


wis2box does not restart properly when VM or docker-system restarts

Currently a restart results in only a subset of the services restarting and the proxy ends up bouncing as it does not find the required endpoints.
The docker-compose.yml files for wis2box should be updated to allow all wis2box-services to restart properly when the docker-host-system restarts.

2024-07-24:

@maaikelimper to check w/ @alimand on status/updates

2024-08-19:

fixed in main branch


Geocell user guide

Geocell user guide
!story G18.4
!component docs

OSSIMGeoCell__User_Manual__1.8.18.doc resides on Google Drive and is shared with several individuals.  Dennis should have a copy.

I have the OSSIMGeoCell user Guide

We have not changed anything in OSSIMGeoCell user Guide. Only work on this doc was clean up by mpg.


Rework Upgrade Report support

What needs to be done
The Upgrade Report creation should be simplified.
It basically consists of a template and some logic that finds matches and provides them to the template and the condition which defines if the section should be rendered. The condition is in most cases true if matches were found.
Why it needs to be done
The Spring Boot upgrade report requires multiple classes and defining the sections in Asciidoctor syntax through a fluent API. this is cumbersome and time-consuming.
Implementation
The template for each section should be provided in the recipe YAML.
One class per section should be defined which is data provider and condition.

The report creation with AsciidoctorJ fails when the default charset is set to US-ASCII (as set by the JDK I used) and the error complains about incompatible encodings of UTF-8 and US-ASCII. The cause seems to be RubyString which uses the default encoding and fails if the template encoding is not the same.
https://github.com/jruby/jruby/issues/6588
https://github.com/asciidoctor/asciidoctorj/issues/815
The problem is solved when either the file is encoded using US-ASII (no option)
Or setting export JAVA_TOOL_OPTIONS=-Dfile.encoding="UTF-8"

[ ] Add precondition check and inform users when Charset.defaultCharset() is not UTF-8


Feature Request: CLI switch to merge multi-dex files into one classes.dex

It now seems to be fairly commonplace to split dex files in APK's
Naturally, this can be used to deter people trying to de-compile an APK, as many users will not know that they need to smali->jar the other folders if they want to view all of the classes
I've found that with a multi-dex APK, I can manually copy the smali'ed files into the main smali folder and have it merge everything together into one classes.dex on rebuild
It would be really nice to have a command line switch option in order to have this done automatically when de-compiling/re-compiling in case there was multiple dex files, I looked into the Androlib.java and see where it could be done, however I think it would be a valuable addition to Apktool in general!

Some applications split for organization, but most split apks are because the dex method limit has been reached and they have no other option. If we hit the method limit then a single dex file is useless. This means Apktool shouldn't try and merge multi-dex apks together.
Apktool is not meant to repair or modify apk's in this regard. Its goal and is to provide a nearly 1 to 1 match from decoded to original.

Okay, thanks for the clarification, I'll modify it on my end for my use case :+1:  :)


Add timer for surface finding

Pull Request instructions:

Please follow the update protocol
Answer the questions below in detail. Your responses will be emailed to experimenters.
If the experimenters must do anything new, provide detailed step by step instructions on the wiki
If computer maintainers need to manually update anything, provide detailed step by step instructions
Use markdown syntax in order for your comments to be rendered reliably in the email: "1." instead of "1)", use four spaces for indents.
If you use the keyword "skip email" in the title, it will skip the email updates
Merges from "develop" into "production_testing" should use the keyword "production merge" in the title for reliable indexing of updates
Merges from "production_testing" into "main" should use the keyword "update main"

Describe changes:
Add a timer for ephys recording when the condition type is set to "surface finding." The recording will automatically prompt the user for confirmation to terminate once the timer ends. Additionally, the user will have the option to manually stop the recording at any time during the session.
What issues or discussions does this update address?
It's more convenient to have a timer for the "surface finding".
Describe the expected change in behavior from the perspective of the experimenter
No
Describe any manual update steps for task computers
No
Was this update tested in 446/447?
Tested in 323_Ephys3

This seems like an ephys specific feature, and not a behavior feature.

I would say they are behavior+ephys features. We are using the GUI to control the start/stop of OpenEphys GUI. The advantage is that we can retrieve the settings from OpenEphys, which are used to generate the session metadata.

We need a clear plan for what ephys+behavior features are going to be in the GUI, and what will be dedicated software. We are adding significant complexity to the GUI to handle unusual ephys situations that would be easier to maintain in a separate piece of software

We need a clear plan for what ephys+behavior features are going to be in the GUI, and what will be dedicated software. We are adding significant complexity to the GUI to handle unusual ephys situations that would be easier to maintain in a separate piece of software

@alexpiet

The new function adds a few simple lines to control the start/stop of Open Ephys, which is straightforward and similar to the timer used in the fiber photometry baseline signal.

The primary reason for using the GUI to control Open Ephys is metadata generation. By doing so, we can automatically retrieve the settings from Open Ephys for that session and generate the metadata seamlessly. While I’m open to an independent solution without the GUI—such as what @KanghoonJ is working on with SIPE—the timeline for that is uncertain. We shouldn’t let the pursuit of a "perfect" solution hinder our current experiments, especially since we don’t know if it will indeed be perfect. Otherwise, we’ll be unable to obtain session metadata for ephys recordings, preventing us from uploading and analyzing the data.

I'm not asking for a perfect solution - I want a plan for a solution. If we can't have stand-alone ephys control (or its slow to be available), then we need a plan for how ephys and behavior interact. Otherwise the code gets messy and hard to maintain very quickly.

@alexpiet
I feel that the influence of this PR might be a bit overstated. The functionality is quite straightforward, similar to a timer used in photometry or the start/stop functions for photometry or a camera. While these standalone systems (e.g., Spinnaker software) have their own controls, they still need to communicate with the behavior GUI for synchronization.
What we’re doing here follows the same principle. The ephys system remains standalone, but we’re using the behavior GUI to control its start/stop and to extract parameters for metadata generation.
Were you perhaps referring to a different aspect? I’m having difficulty understanding how such a simple function could make the GUI gets messy and hard to maintain very quickly.
Additionally, what kind of plan do you want? Who do you think we should involve in a discussion to ensure we approach this issue effectively?

Its not this PR alone, its the multiplicative effect of new features that are added without a larger plan. For example your other open PR about disabling manifest upload for ephys. Bugs get created when this little features don't align properly. We haven't been planning things out well, and as a result we are buried under technical debt. Lets try to improve our software development going forward
A plan looks like a written document of how the GUI and ephys tools should interact. Detailing:

Who maintains these features? Ephys rigs are highly customizable, we can't be in a position where we have complex code that covers all ephys configurations.
What is the specific data model that describes when ephys recordings start/stop
Feedback from all ephys users would be valuable.

Its not this PR alone, its the multiplicative effect of new features that are added without a larger plan. For example your other open PR about disabling manifest upload for ephys. Bugs get created when this little features don't align properly. We haven't been planning things out well, and as a result we are buried under technical debt. Lets try to improve our software development going forward. Note that I'm trying to impose this same degree of planning on the rest of the GUI too. Micah is working on adopting the data models from Aind.Behavior.Services, to help organize the code.
A plan looks like a written document of how the GUI and ephys tools should interact. Detailing:

Who maintains these features? Ephys rigs are highly customizable, we can't be in a position where we have complex code that covers all ephys configurations.
What is the specific data model that describes when ephys recordings start/stop
Feedback from all ephys users would be valuable.

I understand your concerns, and I’m open to discussing specific ways to improve the system.
I believe this concern is being overemphasized. These features are straightforward and unrelated to the core functionality of the ephys software. They simply serve as start/stop functions, much like those used for photometry and camera control.
If this level of concern applies here, do you also have plans to propose updates to the photometry and camera systems for consistency?


ColorPaper cant generate different color in the cycle running

Thanks, i added a patch to resolve that and you may reinstall the repo using:
!pip install git+https://github.com/sparkfish/augraphy

To enable a random color augmentation, you can use ColorPaper(hue_range=(0, 255), saturation_range=(0,255)).
Some examples on random color augmented images using a same parameters above:

thanks


Merge upstream

Also includes https://github.com/cloudfoundry/stratos/pull/4421

Codecov Report

Merging #408 into master will increase coverage by 0.14%.
The diff coverage is 44.11%.

@@            Coverage Diff             @@
##           master     #408      +/-   ##
==========================================
+ Coverage   56.20%   56.34%   +0.14%
==========================================
  Files         891      891
  Lines       29209    29143      -66
  Branches     4232     4217      -15
==========================================
+ Hits        16416    16421       +5
+ Misses      12793    12722      -71


Support /opt/homebrew/bin/brew homebrew patth

I've encountered an issue with the setup script that currently checks for Homebrew only in its default installation path for Intel Macs (/usr/local/bin/brew). As Apple Silicon Macs use a different default path (/opt/homebrew/bin/brew), the script fails to recognize Homebrew installations on these newer machines.

Thanks for fixing this!


blog tweaks

Description
last tweaks to blog
Checklist:

[ ] I have reviewed the style guide.
[ ] If blogging, I have reviewed the blogging guide.
[ ] I have manually confirmed that all new links work.
[ ] I added aliases (i.e., redirects) for all filename changes.
[ ] If making css changes, I rebuilt the bundle.

@usrbinkat, I'll leave here comments for the blog (current version I am reading is: http://pulumi-hugo-origin-pr-3361-c13afd83.s3-website.us-west-2.amazonaws.com/blog/mlops-huggingface-llm-aws-sagemaker-python/ )

Intro: Good job on framing the problem more concretely. I do wish we are explaining the concept and speaking of the outcome more clearly in the intro.
ex: you are saying - running LLM on sagemaker is a popular deployment option. Why? Why do people do that, what does it help them achieve? what's the outcome of that job?
ex: "(IaC) offers a reliable and easy to duplicate deployment practice." generic statement, that doesn't give much value. The next sentence hints at you can use Python to write app and iac code.
is this the only reason why engineers should switch to our way of building? Not sure I would based on how it's written. Does not make technically convincing argument.

second para "Pulumi makes AI/ML Easy?"
are we asking? it looks like a doubtful statement. Write it with conviction
maybe this is a silly comment, but why do we link to a generic Pulumi Templates blog, and don't link to the template in question?

Instructions -  I may be off mark here, do engineers find a list of code instructions helpful? i don't think this is the interesting part of the blog - this makes the blog read like a tutorial or a code recipe. The login, the project setup, the destroy command, and so on... - should this be in the readme? you can still link to all these code instructions, and in the blog focus on the teaser, the WOW factor to get people excited to build

part 3 where you show the sagemaker endpoints is good - i see what resources are provisioned and how, how long it took. Though you are warning in the copy it can take up to 20min? is that something else? file shows sub 6min.

Test endpoint - i think the section that's supposed to be the WOW, reads like a formality
OK, we are helping people create an endpont and test the endpoint. What happened? Was that easy, hard, magical, expected, no one else can do that?

conclusion - i wouldn't anchor on Pulumi Python and MLOPS as The Thing. I don't think we should pigeonhole ourselves into a category. Why not keep it broad-ish? And more generic like, AI Infrastructure?
FWIW:

MLOps gets 12.6 million google searches
AI Infrastructure gets 664 million searches
go bigger (even if MLOps is the pedantically correct term, it's for a more niche audience)

the goal of our python/AI series is to show folks that we are accelerant for engineers spinning up AI efforts (whether you are building AI apps, LLMs, using AI internally to ship, whatever), we will help you accelerate these efforts with our unique approach, that's the premise


Some SVG problems

I'm currently getting a warning:
usage stroke-width: <length-percentage> | inherit | initial

But it can also be just <length>, see https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/stroke-width, for example.

Another one I just've spotted.
unknown SVG property: stroke-miterlimit

https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/stroke-miterlimit

Please try again with CSS::Module 0.6.4 which fixes stroke-width. stroke-miterlimit was added recently and should also now work.

The test suite is now as pure as an angel! :) Thank you!


wrap error response into exception

Signed-off-by: Zhongnan Su<EMAIL_ADDRESS>Description
[Describe what this change achieves]
Issues Resolved
#295
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #309 (e61b69f) into main (7f5ed9b) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #309   +/-   ##
=========================================
  Coverage     99.90%   99.90%
  Complexity     2691     2691
=========================================
  Files           256      256
  Lines          6533     6533
  Branches        422      422
=========================================
  Hits           6527     6527
  Misses            5        5
  Partials          1        1

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 7f5ed9b...e61b69f. Read the comment docs.


/wss/p2p protocol not supported?

I would like to verify if a node is configure properly for usages of substrate-connect. I usually starts with a Substrate node to verify it can indeed connect to the new node. However it seems like it just doesn't work with /wss/p2p multi addr at all?
I tried this
docker run --rm parity/polkadot:v0.9.27 --reserved-only --reserved-nodes=/dns/polkadot-connect-7.parity.io/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o -lsub-libp2p=trace
and getting error
2022-08-13 08:20:50.703 TRACE tokio-runtime-worker sub-libp2p: Libp2p => Reach failure for Some(PeerId("12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o")) through "/dns/polkadot-connect-7.parity.io/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o": Other(Custom { kind: Other, error: Other(A(A(A(A(MultiaddrNotSupported("/ip4/<IP_ADDRESS>/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o")))))) })
2022-08-13 08:20:50.703 TRACE tokio-runtime-worker sub-libp2p: Libp2p => Reach failure for Some(PeerId("12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o")) through "/dns/polkadot-connect-0.parity.io/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o": Other(Custom { kind: Other, error: Other(A(A(A(A(MultiaddrNotSupported("/ip4/<IP_ADDRESS>/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o")))))) })
2022-08-13 08:20:50.703 TRACE tokio-runtime-worker sub-libp2p: Libp2p => Dial failure for PeerId("12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o")
2022-08-13 08:20:50.703 TRACE tokio-runtime-worker sub-libp2p: PSM <= Dropped(12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o, SetId(0))
2022-08-13 08:20:50.703 TRACE tokio-runtime-worker sub-libp2p: Libp2p => Failed to reach PeerId("12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o"): An error occurred while negotiating the transport protocol(s) on a connection: [("/dns/polkadot-connect-7.parity.io/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o", Other(Custom { kind: Other, error: Other(A(A(A(A(MultiaddrNotSupported("/ip4/<IP_ADDRESS>/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o")))))) })), ("/dns/polkadot-connect-0.parity.io/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o", Other(Custom { kind: Other, error: Other(A(A(A(A(MultiaddrNotSupported("/ip4/<IP_ADDRESS>/tcp/443/wss/p2p/12D3KooWEPmjoRpDSUuiTjvyNDd8fejZ9eNWH5bE965nyBMDrB4o")))))) }))].

@tomaka can you help here?

I'm not responsible for anything networking anymore, and haven't been for at least 6 months

This issue has been mentioned on Polkadot Forum. There might be relevant details there:
https://forum.polkadot.network/t/community-bootnodes-and-snapshot-providers/630/4

https://github.com/paritytech/substrate/issues/12217#issuecomment-1373337145 I was confused by the same fact here as well.

Looks like Substrate is just not configured with TLS support. Not sure why it wasn't done.
@xlc however, keep in mind that for substrate-connect you'd need to add polkadot-connect-7.parity.io certificate to your browser's trust chain. Otherwise, the TLS handshake will fail. Also, substrate-connect now supports WebRTC and we're close to merging it in Substrate https://github.com/paritytech/substrate/pull/12529. With WebRTC, you don't need to do any extra configuration work. You can read more here.

This doesn't really have anything to do with substrate-connect. I was trying to use the substrate based polkadot node to connect and it doesn't work.

We have updated our nodes with ssl now. https://github.com/paritytech/polkadot/pull/6534
And it seems to work with the polkadot binary.
./polkadot --chain polkadot --reserved-only --reserved-nodes=/dns/polkadot-boot.dwellir.com/tcp/443/wss/p2p/12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ
./polkadot --chain kusama --reserved-only --reserved-nodes=/dns/kusama-boot.dwellir.com/tcp/443/wss/p2p/12D3KooWFj2ndawdYyk2spc42Y2arYwb2TUoHLHFAsKuHRzWXwoJ

v0.9.36

So I've just checked with latest master both addresses ^:
2023-01-12 13:05:32.671 TRACE tokio-runtime-worker sub-libp2p: Libp2p => Reach failure for Some(PeerId("12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ")) through "/dns/polkadot-boot.dwellir.com/tcp/443/wss/p2p/12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ": Other(Custom { kind: Other, error: Other(A(A(A(A(MultiaddrNotSupported("/ip4/<IP_ADDRESS>/tcp/443/wss/p2p/12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ")))))) })
2023-01-12 13:05:32.671 TRACE tokio-runtime-worker sub-libp2p: Libp2p => Dial failure for PeerId("12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ")
2023-01-12 13:05:32.671 TRACE tokio-runtime-worker sub-libp2p: PSM <= Dropped(12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ, SetId(0))
2023-01-12 13:05:32.671 TRACE tokio-runtime-worker sub-libp2p: Libp2p => Failed to reach PeerId("12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ"): Failed to negotiate transport protocol(s): [(/dns/polkadot-boot.dwellir.com/tcp/443/wss/p2p/12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ: : Unsupported resolved address: /ip4/<IP_ADDRESS>/tcp/443/wss/p2p/12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ: Unsupported resolved address: /ip4/<IP_ADDRESS>/tcp/443/wss/p2p/12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ)]

both result in error.

with latest release it does connect via /ws (NOT /wss) because it discovers the /ws address
2023-01-12 14:56:08.894 TRACE tokio-runtime-worker sub-libp2p: Addresses of PeerId("12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ"): ["/dns/polkadot-boot.dwellir.com/tcp/443/wss", "/dns/polkadot-bootnode.dwellir.com/tcp/30333/ws", "/dns/polkadot-boot.dwellir.com/tcp/443/wss", "/dns/polkadot-bootnode.dwellir.com/tcp/30333/ws"]

with latest master it only discovers /wss
2023-01-12 14:03:39.599 TRACE tokio-runtime-worker sub-libp2p: Addresses of PeerId("12D3KooWKvdDyRKqUfSAaUCbYiLwKY8uK3wDWpCuy2FiDLbkPTDJ"): ["/dns/polkadot-boot.dwellir.com/tcp/443/wss", "/dns/polkadot-boot.dwellir.com/tcp/443/wss", "/dns/polkadot-boot.dwellir.com/tcp/443/wss"]

and refuses to connect

Interesting. I guess we need to continue using ws for substrate nodes then?

I guess we need to continue using ws for substrate nodes then?

Until we resolve this, yes.

I guess we need to continue using ws for substrate nodes then?

Until we resolve this, yes.

I will create another PR that includes both ws and wss then. Thanks for looking this up @melekes !

I guess we need to continue using ws for substrate nodes then?

Until we resolve this, yes.

It would be nice to solve this in the next days to get this into the next polkadot release.

CC @melekes

I think there's a bug in libp2p (or Substrate) where it uses the address with IP/port instead of an address with domain name (polkadot.io) and /wss fails because it needs domain name https://github.com/libp2p/rust-libp2p/blob/a12425885196a55d5003dc8917ef5b4a08324cad/transports/websocket/src/framed.rs#L534

It would be nice to solve this in the next days to get this into the next polkadot release.

Agree, but I still have no idea about the source of bug. My hypothesis was the way we construct the transport (DNS wrapping TCP/WS) prevents WS transport from receiving original addresses (containing DNS names) melekes@ae133bb. But after I added the second instance of WS along with DNS transport, nothing has changed. So it must be something else :(

This was something I also noticed while debugging a reverse proxy problem some time ago. Here is an example of a request where I would have expected a domain name instead of IP in the host header.

Okay, I think I've figured it out.


Links to "Microsoft snapshot tools for SAP HANA on Azure"

This page has at least 3 links to a Github repo which are 404.  The links should point to https://github.com/Azure/hana-large-instances-self-service-scripts/blob/master/latest/Microsoft Snapshot Tools for SAP HANA on Azure Guide.md

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

ID: 29783ec4-2f12-6b8b-2e1d-dfc94597ea1b
Version Independent ID: a4f35717-0606-26a5-543b-618e88e3596e
Content: HANA failover procedure to a disaster site for SAP HANA on Azure (Large Instances)
Content Source: articles/virtual-machines/workloads/sap/hana-failover-procedure.md
Service: virtual-machines-linux
GitHub Login: @saghorpa
Microsoft Alias: saghorpa

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

I have created a PR with the update, changes will be live shortly.
https://github.com/MicrosoftDocs/azure-docs-pr/pull/104012
Thanks for bringing this to our attention. We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


Cleanup unnecessary log statements Closes #2130

Integration test logs

Logs
Add passing integration test logs here

Example query results

Results
Add example SQL query results here (please include the input queries as well)

Hello @cbruno10, Here are a few insights about the Log details with the log level set to DEBUG.

If we set the log level to DEBUG we still receive the logs with level INFO.

I can see there are a lot of logs with the INFO level from Steampipe SDK itself.

Sample log output when a query fails due to bad creds for a single account(I can see the logs with level ERROR)

Logs
    2024-03-18 07:40:36.680 UTC [ERROR] steampipe-plugin-aws.plugin: [ERROR]<PHONE_NUMBER>322: getCallerIdentityUncached: status=failed connection_name=aws api_error="operation error STS: GetCallerIdentity, https response error StatusCode: 403, RequestID: 62a137d5-11e6-4b8b-8e34-2710598468bd, api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details."
    2024-03-18 07:40:36.680 UTC [ERROR] steampipe-plugin-aws.plugin: [ERROR]<PHONE_NUMBER>322: getCommonColumnsUncached: status=failed connection_name=aws region=global error="operation error STS: GetCallerIdentity, https response error StatusCode: 403, RequestID: 62a137d5-11e6-4b8b-8e34-2710598468bd, api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details."
    2024-03-18 07:40:36.680 UTC [ERROR] steampipe-plugin-aws.plugin: [ERROR]<PHONE_NUMBER>322: aws_account.listAccountAlias: common_data_error="operation error STS: GetCallerIdentity, https response error StatusCode: 403, RequestID: 62a137d5-11e6-4b8b-8e34-2710598468bd, api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details."
    2024-03-18 07:53:42.092 UTC [ERROR] steampipe-plugin-hubspot.plugin: [ERROR] listAllPropertiesByObjectType: api_error="403 Forbidden"
    2024-03-18 07:53:51.139 UTC [WARN]  steampipe-plugin-docker.plugin: [WARN]  ConnectionData updateWatchPaths - error resolving source path Dockerfile: failed to get directory specified by the source Dockerfile: relative paths require a module with a pwd
    2024-03-18 07:53:51.139 UTC [WARN]  steampipe-plugin-docker.plugin: [WARN]  ConnectionData updateWatchPaths - error resolving source path compose.yml: failed to get directory specified by the source compose.yml: relative paths require a module with a pwd
    2024-03-18 07:53:54.489 UTC [WARN]  steampipe-plugin-terraform.plugin: [WARN]  ConnectionData updateWatchPaths - error resolving source path tfplan.json: failed to get directory specified by the source tfplan.json: relative paths require a module with a pwd
    2024-03-18 08:19:56.547 UTC [ERROR] steampipe-plugin-hubspot.plugin: [ERROR] listAllPropertiesByObjectType: api_error="403 Forbidden"
    2024-03-18 08:19:59.867 UTC [WARN]  steampipe-plugin-terraform.plugin: [WARN]  ConnectionData updateWatchPaths - error resolving source path tfplan.json: failed to get directory specified by the source tfplan.json: relative paths require a module with a pwd
    2024-03-18 08:20:00.885 UTC [WARN]  steampipe-plugin-docker.plugin: [WARN]  ConnectionData updateWatchPaths - error resolving source path Dockerfile: failed to get directory specified by the source Dockerfile: relative paths require a module with a pwd
    2024-03-18 08:20:00.885 UTC [WARN]  steampipe-plugin-docker.plugin: [WARN]  ConnectionData updateWatchPaths - error resolving source path compose.yml: failed to get directory specified by the source compose.yml: relative paths require a module with a pwd
    2024-03-18 08:20:39.106 UTC [WARN]  steampipe-plugin-docker.plugin: [WARN]  ConnectionData updateWatchPaths - error resolving source path Dockerfile: failed to get directory specified by the source Dockerfile: relative paths require a module with a pwd
    2024-03-18 08:20:39.107 UTC [WARN]  steampipe-plugin-docker.plugin: [WARN]  ConnectionData updateWatchPaths - error resolving source path compose.yml: failed to get directory specified by the source compose.yml: relative paths require a module with a pwd
    2024-03-18 08:20:42.789 UTC [WARN]  steampipe-plugin-terraform.plugin: [WARN]  ConnectionData updateWatchPaths - error resolving source path tfplan.json: failed to get directory specified by the source tfplan.json: relative paths require a module with a pwd
    2024-03-18 08:20:47.441 UTC [ERROR] steampipe-plugin-hubspot.plugin: [ERROR] listAllPropertiesByObjectType: api_error="403 Forbidden"

I have captured the log details with by running the queries with the following combinations with DEBUG level:

Log output for a single query with a single connection(Tables: aws_ec2_instance).

single-query-plugin-2024-03-18.log

Log output by joining two tables with a single connection(Tables: aws_ec2_instance & aws_ebs_volume).

join-two-tables-plugin-2024-03-18.log

Log output by joining three tables with a single connection(Tables: aws_ec2_instance, aws_vpc_subnet & aws_vpc_security_group).

join-three-tables-plugin-2024-03-18.log

Log output for a single query with 3 accounts in an aggregator connection(Tables: aws_ec2_instance).

agg-3-conn-plugin-2024-03-18.log

Note: The logs with level INFO are from Steampipe SDK.
If you need any further information please let me know.
Thanks!


Fix ukernel/x86 issues discovered by #12818

query_tile_sizes/x86_64 was not wired up. Tests relying on tile size auto-selection were falling back to generic tile size and hence to generic code.
There was a plain bug in the avx512 pack kernel for 16x16 tiles of 32bit elements --- i.e. accumulator tiles.
The pack_test was not covering this 16x16 32bit accumulator tile format, which is why the bug was not discovered until the query_tile_sizes fix made e2e VMVX tests (and the new benchmark in #12818) run into it.

The test failure  (CI / cross_compile_and_test (linux, riscv_32... is a timeout. If it happens again we could consider filtering out slower CPU targets (emulatodrs?) from certain large e2e tests.

I think the failure case (timeout) is the one you disabled in another change.


Update explanation for the scope of permissions in the provided code examples for token authentication

Why:
The original docs indicate that in Example 1 permissions are defined with scope at workflow level and Example 2 permissions at scoped at job level. In reality, for both examples permissions are defined at job level. See also this comment.
What's being changed (if available, include any code snippets, screenshots, or gifs):
~Since Example 1 is re-usable, I've chosen to modify Example 2, which now has permissions defined at the workflow level. I've also changed the explanation further down the docs to indicate that in Example 1 permissions are scoped at the job level while in Example 2 permissions are scoped at the workflow level.~
Edit: In order to keep best practice for limiting scope, I've updated the explanation for the use of permissions in the code snippets to clarify that in both examples permissions are defined at job scope rather than workflow scope.
Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

👋 @adimitris Thanks so much for noticing this discrepancy and opening this PR! We checked in with our engineering team and the code examples were reviewed earlier this year to change the scope from the workflow to the job, since best practice is to limit scopes (see https://github.com/github/docs/pull/25519).
Because of this, we'd like to leave the code example as is, but update the contextualizing text so it matches what's now in the examples. Let us know if you'd be willing to update this PR to make that change!

Great

👋 @adimitris Thanks so much for noticing this discrepancy and opening this PR! We checked in with our engineering team and the code examples were reviewed earlier this year to change the scope from the workflow to the job, since best practice is to limit scopes (see #25519).
Because of this, we'd like to leave the code example as is, but update the contextualizing text so it matches what's now in the examples. Let us know if you'd be willing to update this PR to make that change!

Thank you for the feedback @meowius. I've reverted my original changes and have updated the text to clarify that in both examples permissions are defined at the job's scope rather than the workflow's, for best practice.


Add udf-examples jar to databricks build

After #1393 a new udf-examples jar needs to be added in order for some of the integration tests to pass.  This was handled automatically in integration_tests/run_pyspark_from_build.sh but the databricks build does not use that script.
This updates the databricks build script to copy the udf-examples jar in addition to the sql-plugin jar.

@tgravescs are there init script changes necessary on the databricks cluster side as well?

build


multi-attribute login feature enabled IS setup which has [tenant_mgt] enable_email_domain= true config, doesn't support multi-attribute login feature properly

Describe the issue:
Having the following deployment.toml config (which is related to Using Email Address as the Usernamehttps://is.docs.wso2.com/en/latest/guides/identity-lifecycles/enable-email-as-username/) overwrites the multi-attribute login configurations
[tenant_mgt]
enable_email_domain= true

How to reproduce:

Download IS-6.0.0

Create a user in IS, giving a username, email and mobile number

Go to https://localhost:9443/myaccount

Try login with username

Login should be successful

Notice the login portal

Then configure the multi-attribute login as mentioned in https://is.docs.wso2.com/en/latest/guides/login/multi-attribute-login/#enable-multi-attribute-login (configure [usernme, email and mobile claims](http://wso2.org/claims/username,http://wso2.org/claims/emailaddress,http://wso2.org/claims/mobile as Allowed Attribute Claim List. Configure regex patterns for those claims as well)

Then try login in to https://localhost:9443/myaccount using username, mobile, emailaddress@ as login identifier. Login will be successful

Notice the login identifier placeholder as well

add the following config to deployment.toml and restart the server (still multi-attribute login feature is enabled)

[tenant_mgt]
enable_email_domain= true

Then try login in to https://localhost:9443/myaccount using username, mobile, email address. User will be able to log in using email address only
Also notice the login identifier placeholder

If the username or mobile is used "Invalid username! Username should be an E-Mail address." error will be shown

Expected behavior:
Conflicting feature configs should be documented properly. Also need to analyse the IS flows if email as username feature is enabled and multi-attribute login feature is enabled.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: IS 6.0.0

This issue can be resolved partially by adding the following config. This resolves not being able to login with mobile number and username. However, the placeholder in the login form will still be displayed as 'Email address'. Hence, the UI bug should be addressed and this config should be documented in the guide.
[tenant_mgt]
enable_email_domain = true
disable_email_domain_validation = true

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Add persistence.affix option to Harbor chart

Address issue: https://github.com/rancher/rancher/issues/20694
Problem:
Global registry uses existing PVCs from previous release, even storageclass changed on
re-enabling. Because the PVC names remain the same. In helm style, release name is usually used to avoid resources
conflicts. But we want to keep app name consistent and the release name
is bound to the app name.
Solution:
Add the option to specify affix for PVC names. UI can set a random
alphabet-number string to it on enabling, and keep it on updates. So
that every time registry is enabled, fresh PVCs are used.

LGTM.

Per https://github.com/rancher/rancher/issues/20694#issuecomment-501862669, we should delete PV/PVCs on disabling, so we don't need this identifier.


pico-sdk: Rename adc_read() to adc_read_pico()

adc_read() that defined in adc.h of PICO-SDK conflicts with zephyr's ADC API.
Rename it to avoid compile errors.
PICO-SDK doesn't reference adc_read() from itself,
so we can change the definition only.
Signed-off-by: TOKITA Hiroshi<EMAIL_ADDRESS>

Hi, @petejohanson, @andrei-edward-popa,
I'm sorry to bother you while you're busy, but could you please give me a review?
(I couldn't assign as reviewers, so please comment.)

@stephanosio @carlescufi @nashif @anangl I think we should merge this patch, despite the maintenance headache it implies. CI results are available in the zephyr PR linked above. Any objections?

Not to nitpick (nitpico?), But would prefixing it be more standard? pico_adc_read?

Hi, @petejohanson
Thank you for reviewing.

Not to nitpick (nitpico?),
😆

But would prefixing it be more standard? pico_adc_read?

Change #1 is avoiding conflict using by prefixing.
I should fix same as it.
Thanks for insightful pointing out!

May I suggest to create a list of such patches either in the README.md, the CONTRIBUTING.md, or a new file such that these patches won't be forgotten in future sdk updates.
Including the MHZ to PICO_MHZ patch of the first PR and the renaming of adc_read() in this PR for now.

I think we should merge this patch, despite the maintenance headache it implies. CI results are available in the zephyr PR linked above. Any objections?

Given the status quo that Zephyr functions are not prefixed with a Zephyr-specific prefix, agreed.


Cannot read property 'filterProps' of undefined - Occurs during build (Next.js/React)

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
_app.js
import NavBar from './navbar'
return (

      <React.Fragment>

          <title>LabDocket</title>
          <meta name="viewport" content="minimum-scale=1, initial-scale=1, width=device-width" />

        <ThemeProvider theme={theme}>
          <CssBaseline />
          <NavBar />

            <Component {...pageProps} />

          <NavBottom />
        </ThemeProvider>
      </React.Fragment>

  )

navbar.js
import { makeStyles } from '@mui/styles';
//import { styled } from '@mui/styles';

//const useStyles = styled((theme) => ({
const useStyles = makeStyles((theme) => ({
  root: {
    flexGrow: 1,
  },
  menuButton: {
    marginRight: theme.spacing(2),
  },
  title: {
    flexGrow: 1,
  },
}), { name: "MuiExamle_ComponentiAppBar" });

export default function NavBar() {
  const classes = useStyles();

if (signedInUser == true) {
    return (

        <AppBar position="static">
          <Toolbar>
            <Tabs value={value} onChange={handleChange} variant="scrollable" aria-label="Static Top Buttons Menu">
              <Tab label="HOME" icon={<HomeIcon />} {...a11yProps(0)} />
              {signedInUser && (<Tab label="NEW REQUEST" icon={<AddBoxIcon />} {...a11yProps(1)} />)}
              {signedInUser && (<Tab label="MY REQUESTS" icon={<AssignmentIcon />} {...a11yProps(2)} />)}
              {signedInUser && (<Tab label="CALENDAR" icon={<EventIcon />} {...a11yProps(3)} />)}
              {signedInUser && (<Tab label="MANAGER" icon={<SupervisorAccountIcon />} {...a11yProps(4)} />)}
              {signedInUser && (<Tab label="ADMIN" icon={<SettingsIcon />} {...a11yProps(5)} />)}
              <Tab label="LOGIN" icon={<PersonIcon />} {...a11yProps(6)} />
            </Tabs>
          </Toolbar>
        </AppBar>
        <TabPanel value={value} index={0}>
        </TabPanel>
        <TabPanel value={value} index={1}>
          <Request />
        </TabPanel>
        <TabPanel value={value} index={2}>
        </TabPanel>
        <TabPanel value={value} index={3}>
          <LabCalendar />
        </TabPanel>
        <TabPanel value={value} index={4}>
          <Manager />
        </TabPanel>
        <TabPanel value={value} index={5}>
          <Admin />
        </TabPanel>
        <TabPanel value={value} index={6}>
          <Account />
        </TabPanel>

    );
  }

When I reverse the commented sections, the build fails with "Cannot read property 'filterProps' of undefined"
Error Message on Build:
Error occurred prerendering page "/list-requests". Read more: https://nextjs.org/docs/messages/prerender-error
TypeError: Cannot read property 'filterProps' of undefined
    at componentCreator (/home/jausfeld/LabTracker/node_modules/@mui/styles/node/styled/styled.js:86:15)
    at NavBar (/home/jausfeld/LabTracker/.next/server/chunks/1257.js:3085:21)
    at d (/home/jausfeld/LabTracker/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:33:498)
    at bb (/home/jausfeld/LabTracker/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:36:16)
    at a.b.render (/home/jausfeld/LabTracker/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:42:43)
    at a.b.read (/home/jausfeld/LabTracker/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:41:83)
    at Object.exports.renderToString (/home/jausfeld/LabTracker/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:52:138)
    at Object.renderPage (/home/jausfeld/LabTracker/node_modules/next/dist/server/render.js:621:45)
    at Object.defaultGetInitialProps (/home/jausfeld/LabTracker/node_modules/next/dist/server/render.js:301:51)
    at Function.getInitialProps (/home/jausfeld/LabTracker/.next/server/pages/_document.js:525:20)
info  - Generating static pages (49/49)

Expected Behavior 🤔
I should be able to use styles.
Steps to Reproduce 🕹
Steps:

Create an AppBar
Import styled, and use it as shown above
Load AppBar in _app
npm run build
All pages (located in pages folder) fail on build with styled, but do not with makeStyles

Context 🔦
I cannot say this has negatively effected the build as I am not really using the full functionality of styled vs makeStyles vs withStyled.  It was tricky to track down as it was a massive list of errors, but beyond that it was not much trouble.  I do not fully understand why this is failing.  The docs reference both @mui/styles and @mui/system with regards to importing styled however it's not clear which module to use, when, and why.  So for now, I'm just reporting the finding as it might be helpful at some point.
Your Environment 🌎
Ubuntu desktop with Visual Studio Code.

It doesn't look like this bug report has enough info for one of us to reproduce it.
Please provide a CodeSandbox (https://material-ui.com/r/issue-template-latest), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

I have added a bit more contextual code around the setup and usage, but, unless I am missing something key this is pretty much all there is that would be of interest.  I have also included the error message (there are 49 others just like it).  In the end, all I did was swap makeStyles for styled and the build proceeded without error.  Now in testing, the menu icons are all black (they were light grey before), and when selected they are the same blue as the menu (they were white before).  I need to track down where these color settings are as I did not need to specify this before but that seems to be the only negative aspect to the swap.  I have included screenshots of the menus for comparison if that is helpful.
Current (makeStyles):

Previous (styled)


Login data restart

Great app, but when Homey restarts the app forgets the login data. You have to go to settings and re-login.
I use Facebook to log in.
Homey 0.10.1.

Hello,
I don't have facebook, so was unable to test this, however I can't reproduce this issue using google sign in.
Would you be able to test this with a google login instead of facebook, and report back what the outcome was?

No reaction from OP, closing issue.


Documentation missing: Which Raspberry Pi's are supported?

Hi,
could you provide a list of RPi's that are known to work with the library?
If there are special tweaks necessary for other than RPi4, that would also be helpful.
Yours
S

Hi,
Sorry, I do not have any other RPis at hand to test it. If you have a different model and would like to volunteer, I'm happy to help with the setup.
Based on some findings while looking into the clock stretching bug, I think all older RPis must use software I2C as their hardware I2C is inherently broken. Other than this limitation (and having to provide a software I2C interface to the library), I do not see any problems with running this on older Pis.

@RequestForCoffee Ok, I just ordered my SCD-30. Don't know how long shipping will take, but I want to use it with a Rpi3. I will get back to you with success or fail reports. I was hoping that the complications re. clock stretching could somehow be overcome.

I think they can be overcome by simply using software I2C on the GPIO pins. LMK if you run into any troubles there or think you might benefit from some API adjustments in the library to support this usecase.
I'll keep this issue around in the meantime.

I have tested it in raspberry pi P1 and appears to works correctly. I plan to mount in a zero W model

I can confirm that it works with a Raspberry Pi Zero W.


Add files via upload

(aktualisiert bis gle)

This pull request overlapped with #2 and was therefore merged with it in commit 4d58e41836d8faa51dbfa7c5dd54fe2d39c75276.


We need a demo of the functionality.

https://user-images.githubusercontent.com/629190/192168757-00c055e1-4cdd-4a6a-9d2a-2597dffb6d6b.mov

Let me try again:
https://user-images.githubusercontent.com/629190/192169091-66803a78-0cb3-4d40-bf3d-0b5ec1ad32fd.mp4

One more time.
https://user-images.githubusercontent.com/629190/192169786-64f47935-4aa0-4dac-bfd4-2fc28818afe4.mov


Fix Fulltrustprocess on Windows 10 < 2004

Resolved / Related Issues
Items resolved / related issues by this PR.

Closes #6585
Closes #6609
Closes #6501

Details of Changes
Add details of changes here.

Named pipe connection between UWP and fulltrustprocess is now being open from the UWP side. Fixes FTP not working on Windows 1809 (and I think 1903/1909 as well)

~Could someone verify that it's good on Windows 11 too?~
Validation
How did you test these changes?

[x] Tested on Windows 10 1809 & 21H1 & Windows 11 (thanks @nvi9)
[x] Tested minimizing/restoring the app
[x] Tested with multiple open instances of Files
[x] Tested when fulltrustprocess is running as admin

It seems that gave92 enjoys coping the mechanism from RX-Explorer but even do not want to simply give a star on it.
He always follows the changes as RX-Explorer did for a long while.
Learning from RX-Explorer is totally ok but I think it deserves one star if someone got the ideas (many times) from it.
That's all. Thanks.

@zhuxb711 you're right, I took quite a bit of inspiration from RX_Explorer (in particular for NamedPipe connection instead of AppService and for FileOperations using shell). I'll make sure to credit you amazing work better in the future.

@gave92 Very appreciate! A star is really a simple action~(⁎⁍̴̛ᴗ⁍̴̛⁎)

It seems that gave92 enjoys coping the mechanism from RX-Explorer but even do not want to simply give a star on it.
He always follows the changes as RX-Explorer did for a long while.
Learning from RX-Explorer is totally ok but I think it deserves one star if someone got the ideas (many times) from it.
That's all. Thanks.

@zhuxb711 Sorry about that!


Refactor proxy model for cbsceneinventory

Would this simplify it?

This makes more sens. I did not try to move if not rows to the top of the function :+1:


fix: bump versins to the latest

Bump versions to the latest;
    "@sap/xsenv": "^4.2.0",
    "@sap/xssec": "^3.6.0",
    "passport": "^0.6.0"

Addreses security issues.
Removed package.lock to allow users pull the correct version for their respective node versions.

@theStiggySpd please review


Visual Studio Code crashes if big file's contrent is copied

VSCode Version: 1.28.2
OS Version: Windows 10 Pro (up to date); i7-3770 processor; 16GB of RAM

Steps to Reproduce:

Obtain or create big .csv file Size: 79.6MB 13522 lines of content.
Open VS Code
Drag&Drop the .csv file into VS Code window
Select all file's content with Ctrl+A
Copy all the content with Ctrl+C

Does this issue occur when all extensions are disabled?: Yes (Checked)
VS Code version screen:

let's track it in https://github.com/microsoft/vscode/issues/61911


Feedback API

Overview

Interactive Documentation: https://developfeedback.covercrop-data.org

The Feedback API provides an interface to create Github Issues in any repository in the precision-sustainable-ag company.
This request will return a 201, with a status of 'failed' if the repository property is not a valid repository that already exists in the precision-sustainable-ag company.  When an issue fails to be created in Github, a Slack notification will be posted in thefailed-feedback-logs channel.
Endpoints

/v1/issues - Creates an issue, and posts it to a repository in the precision-sustainable-ag company.

Example
HTTP Request

POST https://developfeedback.covercrop-data.org/v1/issues

payload
{
  "repository": "dst-feedback", // make sure to check with Mikah / Brian / Adam to  verify which repo we want to post this to.
  "title": "string",
  "name": "string",
  "email": "string",
  "comments": "string",
  "labels": [
    "string"
  ]
}

Ex. Response
{
  "type": "string",
  "data": {
    "status": "success", // this will either be 'success' or 'failed' depending on the outcome of the request to Github.
    "payload": { // this is the issue saved in the database, to ensure no data loss in case of Github request failure.
      "id": 0,
      "repository": "string",
      "title": "string",
      "name": "string",
      "email": "string",
      "comments": "string",
      "labels": [
        "string"
      ]
    }
  }
}

Ex. Javascript Request
const requestPayload = {
  "repository": "dst-feedback",
  "title": "Example Issue",
  "name": "John Doe",
  "email"<EMAIL_ADDRESS>  "comments": "This is an example issue.",
  "labels": ["bug"]
};

fetch('https://developfeedback.covercrop-data.org/v1/issues', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json'
  },
  body: JSON.stringify(requestPayload)
})
  .then(response => response.json())
  .then(body => {
    if (body.data.status === 'success') {
      console.log('Feedback successfully sent to Github!');
      console.log(body.data.payload);
    } else {
      console.log('Failed to send Feedback to Github.');
    }
  })
  .catch(error => console.error(error));

@ssharm1524  lmk if you need any additional information / help!

Is there any kind of authentication on this endpoint?

no, it is currently public.

@brianwdavis I did build out the functionality in the dst-data-entry-auth-api to add public, domain controlled authorization for a service to service communication. it just is not currently implemented in the feedback api. I can probably add it in in about by EoD tomorrow and update this ticket if you would like?


[CI Environment] Removed AVM from non-AVM pipeline triggers

Removed AVM from non-AVM pipeline triggers
@eriqua - I haven't tested it yet (as I'd need to merge first, which I will eventually) but wanted to collect your thoughts first.

Moving to draft until we tackle this topic


Added flow capability to animations

You can now use flow (like flow.js) directly in animations.

flow [cell] # toggles flow
flow [cell] start
flow [cell] stop

Additionally templatized buttons to simplify code.

Thanks, this will be merge via the main repo in the next release.


feat(ingest): Add Source from Vertica

Adding a Metadata Ingestion Source Guide:

[x] 1. Set up the configuration model
[ ] 2. Set up the reporter
[x] 3. Implement the source itself

[x] add get_view_definition
[x] add get_column
[x] support DATE column type
[x] support TIMESTAMP column type
[x] support UUID column type

[x] 4. Set up the dependencies
[x] 5. Enable discoverability
[ ] 6. Write tests

[ ] unit test
[ ] integration test

[ ] 7. Write docs
[x] 8. Add SQL Alchemy mapping (if applicable)
[ ] 9. Add logo

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.

Errors regarding TIMESTAMP and DATE types have been resolved. 👏
Regarding the TIMESTAMP type error
It seems that the function could not be called due to the timezone argument defined within sqlalchemy_vertica.
The error is avoided by defining new def TIMESTAMP_WITH_TIMEZONE and def TIME_WITH_TIMEZONE.
The following is a reference:
https://github.com/alexryndin/sqlalchemy-vertica/commit/9612580071fc85e79f272d670bc9c552fddf2b19
Regarding the DATE type error
I changed it so that args = () for DATE type, since we cannot pass arguments to DATE type.

Should I create a new branch and merge into it instead of the main branch?

When this feature will be released on new version?


merge pad2d and pad

whoops I meant to PR this to local repo
But I'll just continue here.

actually all this failed CI is embarrassing, gonna close it and open later haha


Update docs to mention Free tier cancelation/account deletion ability

I believe we now enable self-serve account cancelation/deletion for Free tier accounts:

Relevant URLs

_https://docs.influxdata.com/influxdb/cloud/account-management/offboarding/#cancel-service_

Thank you, @bckeene - this PR @mluu12 is working on will resolve this issue.

Hi @bckeene, this issue was solved with #2997!


wren segfaults on deeply-nested expressions

$ python3 -c 'N = 1000000; print("System.print" + "(" * N + "1" + ")" * N)' > foo.wren
$ ./wren foo.wren
zsh: segmentation fault  ./wren foo.wren
$

Yeah, we probably just need to set a max expression nesting depth so that we don't overflow the C stack. This is one of the limitations of doing a recursive descent parser.

Also, I’m not sure if you consider this a bug, but it can’t read source from a pipe:
$ ./wren <(python3 -c 'N = 1000000; print("System.print" + "(" * N + "1" + ")" * N)')
Could not read file "/proc/self/fd/11".


arvindkgs: A quick and practical example of Hexagonal Architecture in Java

Code for evaluation article - "A quick and practical example of Hexagonal Architecture in Java"

Closing as per guidelines


[Question]: offline mode

Please check the following before submitting a new issue.

[X] I have searched the existing issues.
[X] I have carefully read the documentation.

Please select for which platform(s) you need help

[X] Android
[X] iOS
[ ] Linux
[ ] macOS
[ ] Web
[ ] Windows

Your question
Is it possible to get a location through this package even if there is no internet? , my application works without internet , I need to go to the mountainous areas and get the location from there , there is no internet , how much does this package support it ?
Version
10.1.0

Dear @axroromonov,
It depends a lot on the settings and platform that you use, however, in general it should be possible to determine a location without internet. The phone then uses GPS, cellphone network or Wifi to determine the location.
Kind regards,


fixed bug due to data race condition

filled username placeholder in left sidebar in home dashboard
adapted mongo query in graph component

could you explain a bit more what the race condition is about?

could you explain a bit more what the race condition is about?

for the logged-in user, the email address is not available although data can be observed in the mini mongo which is filled via the child component of a vocabulary list. Tried to create an event emitter from child to parent such the dashboard (Parent component) only gets to query after the indication where the child has rendered his view, in this case, it is the vocabulary list component but it still doesn't work.


Clarify how to handle light/dark mode logo

Right now it's not very clear how to handle switching the logo fill color based on light / dark mode. For the time being I'm using fill="currentColor", but would be great if I can customize which fill colors get rendered for light mode / dark mode.
Possible solution can be to use a function for logo in theme.config.tsx that gets passed the current state of light or dark. Then we can manually switch the rendered logos or colors based on that state. Or some other method for accessing the color scheme value... 🤔

not nextra-related issue, you can handle it in whatever you want a solution, tailwindcss classes or CSS styles

Possible solution can be to use a function for logo in theme.config.tsx that gets passed the current state of light or dark. Then we can manually switch the rendered logos or colors based on that state. Or some other method for accessing the color scheme value... 🤔

no need to overcomplicate

I'm also looking into this problem, and I found that you can use useTheme hook to retrieve the current theme.
import { useTheme } from 'nextra-theme-docs'

const { theme, systemTheme } = useTheme()

if (theme == 'system') {
  var current = systemTheme
} else {
  var current = theme
}

I'm using Nextra3, so I'm not sure whether Nextra has this hook.


[resotocore][fix] Mark deprecated API endpoints

Code of Conduct
By submitting this pull request, I agree to follow the code of conduct.

Codecov Report
Patch coverage has no change and project coverage change: -0.06 :warning:

Comparison is base (44ba660) 89.09% compared to head (d54b09a) 89.04%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1581      +/-   ##
==========================================
- Coverage   89.09%   89.04%   -0.06%
==========================================
  Files          82       82
  Lines       13022    13022
==========================================
- Hits        11602    11595       -7
- Misses       1420     1427       +7

Flag
Coverage Δ

resotocore
89.04% <ø> (-0.06%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

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


More improvements to auto Pr

User forks from ciBot
Remove automerge, it only works with a repo scoped PAT

Signed-off-by: Itxaka<EMAIL_ADDRESS>

Codecov Report

Merging #273 (6548659) into main (415f610) will decrease coverage by 0.10%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #273      +/-   ##
==========================================
- Coverage   74.99%   74.88%   -0.11%
==========================================
  Files          46       46
  Lines        4751     4751
==========================================
- Hits         3563     3558       -5
- Misses        919      924       +5
  Partials      269      269

Impacted Files
Coverage Δ

pkg/http/client.go
85.29% <0.00%> (-14.71%)
:arrow_down:

Continue to review full report at Codecov.

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


178 baseline cadenza challenge task 2

PR for Cadenza 1 Task 2

@ns-rse, @jonbarker68
This is the PR for the CAD1 Task2.
It may need some changes.But need to merge very soon

We have a new error in test_full_CEC2_pipeline.py
=========================== short test summary info ============================
FAILED tests/regression/test_full_CEC2_pipeline.py::test_full_CEC2_pipeline - IndexError: invalid index to scalar variable.

@ns-rse ,
Does mypy change some defaults?
I am trying to commit some changes and stuff I didn't change are complaining now, e.g.,
recipes/cad1/task2/data_preparation/build_scene_metadata.py:136: error: No overload variant of "__getitem__" of "list" matches argument type "str"  [call-overload]
recipes/cad1/task2/data_preparation/build_scene_metadata.py:136: note: Possible overload variants:
recipes/cad1/task2/data_preparation/build_scene_metadata.py:136: note:     def __getitem__(self, SupportsIndex, /) -> Any
recipes/cad1/task2/data_preparation/build_scene_metadata.py:136: note:     def __getitem__(self, slice, /) -> List[Any]
recipes/cad1/task2/data_preparation/build_scene_metadata.py:155: error: No overload variant of "__getitem__" of "list" matches argument type "str"  [call-overload]
recipes/cad1/task2/data_preparation/build_scene_metadata.py:155: note: Possible overload variants:
recipes/cad1/task2/data_preparation/build_scene_metadata.py:155: note:     def __getitem__(self, SupportsIndex, /) -> Any
recipes/cad1/task2/data_preparation/build_scene_metadata.py:155: note:     def __getitem__(self, slice, /) -> List[Any]

I think this is in relation to the np.random.choice of a list in get_random_dict_item()
Do you know how can I solve this?

Do you know how can I solve this?

I think this is traceable to np.random.choice.__getitem__() as that is the core of get_random_dict_item(). This thread provided some insight/improved my understanding.
I'm not entirely sure how to resolve it though. For now I'd add # type: ignore on those lines given the time constraints of getting this out.

Do you know how can I solve this?

I think this is traceable to np.random.choice.__getitem__() as that is the core of get_random_dict_item(). This thread provided some insight/improved my understanding.
I'm not entirely sure how to resolve it though. For now I'd add # type: ignore on those lines given the time constraints of getting this out.

Ok, The conflict was that the function read_json could return the dictionary or just the keys.
I change the function to return just the dictionary and use list(.keys()) when needed

Ok, The conflict was that the function read_json could return the dictionary or just the keys. So, mypy complains because the variable brir could be a dict or a list.
I change the function to return just the dictionary and use list(.keys()) when needed

Ah, good work figuring that out, thanks.

This all looks good to me but I'd refactor somewhat to move details of the car acoustics processing out of the evaluate_scene function and down into the car_scene_acoustics module.  This is largely about communication: i.e. the car acoustics is something that has been fixed and given to entrants and is separate from decisions about evaluation e.g HAAQI, HASPI etc.  So the evaluate function should be taking the radio signal, passing it through some external function to generate hearing aid outputs, and then applying metrics to those hearing aids.

@groadabike The test is failing because enhance_song() takes config as an option from which it extracts the sample rate.
Probably the easiest fix is to setup a config of type DictConfig as a @pytest.fixture in conftest.py and have test_enhance_song() take that as an argument.
Although reading it closer I think on the waveform is being correctly passed in to enhance_song() within test_enhance_song().

@groadabike The test is failing because enhance_song() takes config as an option from which it extracts the sample rate.
Probably the easiest fix is to setup a config of type DictConfig as a @pytest.fixture in conftest.py and have test_enhance_song() take that as an argument.
Although reading it closer I think on the waveform is being correctly passed in to enhance_song() within test_enhance_song().

Thank you @ns-rse ,
They request me some changes. And changed the enhance function but forgot to update the test.

Looks good. Nice work with separating the car acoustics and the evaluations! One tiny typo in a comment noted. 👍


Unable to Create Registered Targets in Target Group

Describe the bug
When attempting to create a target group of type 'ip' in VPC, the target group is created but the registered target is not created. No errors are reported in the pipeline; however, the deployed targets do not reflect in the specified account.
To Reproduce
Define a target group in the VPC block with the following specifications, specify an IP address from the subnets of the virtual private cloud (VPC) in another account separate from where the target group is deployed.
- name: tg-alb-perimeter-dev00
      port: 80
      protocol: HTTP
      protocolVersion: HTTP1
      type: ip
      healthCheck:
        enabled: true
        port: 80
        protocol: HTTP
        targets:
         - "<IP_ADDRESS>/8" #for-example

Expected behavior
The registered target should be successfully created in the specified VPC account.
Please complete the following information about the solution:

[x] Version: [v1.6.0]

To get the version of the solution, you can look at the description of the created AWS CloudFormation stack used to install the LZA (AWSAccelerator-InstallerStack). For example, "(SO0199) Landing Zone Accelerator on AWS. Version 1.5.1.". If the description does not contain the version information, you can look at the Parameters of the stack for the RepositoryBranchName as that should contain the version number.

[x] Region: [e.g. eu-west-2]
[x] Was the solution modified from the version published on this repository? No
[ ] If the answer to the previous question was yes, are the changes available on GitHub?
[x] Have you checked your service quotas for the services this solution uses? Yes
[x] Were there any errors in the CloudWatch Logs? No

Hi @pamelaeteng26! Thank you for using the Landing Zone Accelerator on AWS solution. I was able to replicate the issue you described and I've opened a bug report for this. I will keep communication on this issue open. If you have any other questions or concerns, please do not hesitate to contact us.

Thank you


Change README.md

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (245512d) 100.00% compared to head (1a4f13b) 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main       #42   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           21        21
  Lines          239       239
=========================================
  Hits           239       239

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


bug: window is not defined

on jwt token validation encountered:
error: Uncaught Error: Uncaught ReferenceError: window is not defined
    at WorkerImpl.#poll ($deno$/web/workers.ts:210:17)

Hi @alexanderGalushka does this error only appear when using Deno.bundle(). I could not replicate this error using the normal deno run or deno test command. I am a little bit confused because the window.btoa etc. functions still exist in the latest deno version. Would you be so kind and tell me exactly how to replicate the error?
Additionally I just found out that there is a base64 module in the deno standard library now. I guess we both agree that it would be better to use this module from now on. If that is the case, let me know if you wanna adapt your PR.

@timonson yeah, interesting, I run the code in the bundle which is the wrapped into the web worker

@timonson if you can merge PR #5 for it would be great, it will unblock my work for now and we can looking into using the std base64 module


fix: build and scan workflow

Summary of changes:

Fixed working dir in build and scan workflow.

Invalid branch name. Closing.


Ensure oak index while updating an index defnition doesn't copy over property types

The title of the issue is a little vague, so let me mention a concrete example. If nodetype index is updated by ensure oak index then declaringNodeTypes and propertyNames properties in updated index definition get type String[] even though even the source information (ensure oak index index templates) had Name[]. This leads to nodetype getting ignore by Oak.
/cc @davidjgonzalez

Fwiw, opened OAK-4636 so that oak can be more resilient or avoid such situations. In either case, this issue should still be fixed imho.

By Node[] you mean Name[]?
Bascislly the copy operation is normalizing ensure definition Name property types to Strings? Agree should be fixed here. Strange this is first notice of it. I expect it has something to do w use of value maps to quickly move the properties over.

acs-aem-commons-content-2.6.5-SNAPSHOT-min.zip
acs-aem-commons-content-2.6.5-SNAPSHOT.zip

Fixed


Swift 4 support

Also fixed a bug where mixed title text attributes were being overwritten with the unfolded value.

@weiran  作者并没有同步到swift4吧？ 大神请指教一下可以吗

ci failed

Not sure why the CI is failing to build, will try again with Xcode 9.3 updates.

👍


Why I can't vote?

Discussed in https://github.com/snapshot-labs/snapshot/discussions/767

Originally posted by metrox-eth September 29, 2021
Suggest answers below or vote for an answer.

y i am not voteing power

Please create a ticket with more details at https://discord.snapshot.org


Cleaning up the repository from CLUECupla and CLUEGPU

As announced in the key4hep meeting, here the cleanup.
BEGINRELEASENOTES

k4Clue with the latest improvements is now available only for C++
The GPU version was currently not working so we have decided to remove it from this package and fix it in the short-term future in the kalos/clue standalone repository.
Similarly with the cupla version, we are restructuring the standalone repo to make use of the alpaka library instead
The idea is to get both versions directly from the standalone repository when it is fully integrated in the stack
ENDRELEASENOTES

Hi @jmcarcell could you please look into why the downstream test fails?
Thank you!

It's a known issue, don't worry about that since this PR only affects this repo

Dear @andresailer @tmadlener
Do you have any approximate idea about the merge of this PR?

It's a known issue, don't worry about that since this PR only affects this repo

@jmcarcell Can we fix this issue? Is this https://github.com/key4hep/key4hep-actions/issues/1 ?

Yes I'll get on it and yes, it's that one


Cannot place order in saleor demo's storefront

What I'm trying to achieve
Place an order on the demo store to reproduce another bug. :wink:
Steps to reproduce the problem

Create a cart with an item;
Follow the checkout until the summary page;
Try to hit "Order & Pay";
A server error should occur.

System information
Host: demo.getsaleor.com
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Accept-Language: en,en-GB;q=0.8,en-US
Accept-Encoding: gzip, deflate, br
Referer: https://demo.getsaleor.com/en/checkout/summary/

It has been fixed now.

It's back.

There is a problem with address anonymization. The error being thrown is:
MultipleObjectsReturned
get() returned more than one Address -- it returned 2!

and it happens in store_user_address function in this line:
address, _ = user.addresses.get_or_create(**address.as_data())

Apparently, multiple similar addresses in the database became the same after anonymization. Therefore Django cannot distinguish between them. For now, I've cleared and recreated the database. Quick fix around that would be to use filter instead of get.

Looks like the address is being duplicated during the address creation as when deleting the duplicate one from account details, the checkout doesn't crash anymore.
I will take a look if I have 5 minutes later today.

Should be fixed now. I'll deploy the new version of demo within next few days.