Move counter cache update back into transaction

Currently, the counter cache update happens outside of the transaction in the after_commit hook. This is to avoid a historical deadlock issue in Postgres. However, this should be fixed in Postgres 9.3, according to this and the release notes.
Given that, it should be optional in counter_culture whether the update should happen in or outside of the transaction. It should default to inside the transaction.

cc @DavidMikeSimon

Hi all, any news about this?

No news, no. Feel free to work on it though! 😄 I've never worked with the test_after_commit gem, so no ideas there. How are you trying to use it?

I think it's even simpler than that. It'd just need a method that conditionally yields directly or calls execute_after_commit.

@magnusvk Check out #145. Let me know if you'd like me to add any specs, but I'm not really sure how to reliably test what happened inside and outside of an ActiveRecord transaction.

This is no longer the case in the just-released version 1.0.0. Thank you @kulte for the pull request.

I'm experiencing deadlocks using MySQL & counter_cache at scale (database under heavy load with many concurrent requests competing to update the counters).
Any chance the "execute_after_commit" option can be added back? I don't understand why it was removed from 2.x in the first place. Seems that whether to update the counters inside or outside of the transaction should be left to the user to decide, right?
I cannot revert to the 1.x branch because I need other improvements in the 2.x branch (i.e. bug fixes for discard integration).

Sorry you're having issues with this. Interestingly, this issue was first added because of deadlock issues with Postgres. It's somewhat ironic that it's now MySQL causing a similar issue.
In any case, the history of removing this comes from a bugfix to allow multiple saves in one transaction, see 81dfbf55495b59afab844bbd0ff14fbff3cb922b. Plus, in the absence of issues like this with the database layer, I don't see why you'd ever want to push the counter cache update outside of the transaction. But then again, you are seeing database issues.
To address your immediate issue, you could probably run a fork of current master with 7639b08569851ebafda1f6f3dceccf0dcab15bda reverted relatively easily. Now that's not a great long-term solution, obviously, but just throwing that out there.
If you can figure out how to write a test for this behavior, I think I'd probably be down to re-add this functionality, given that the original code for this was quite straightforward.
This is the first I'm hearing of this issue, so not sure how widespread it is, but of course still would be good to figure out how to address this for you. @jbritten

Thank you for summarizing the history of this change and work-around suggestions. Ironically, I received another deadlock exception while reading your reply.
Would you be okay with me opening a new issue to track adding back the execute_after_commit feature?

Yeah good call to move this to a new issue!

On Jul 1, 2019, at 10:28 AM, Justin Britten<EMAIL_ADDRESS>wrote:
Thank you for summarizing the history of this change and work-around suggestions. Ironically, I received another deadlock exception while reading your reply.
Would you be okay with me opening a new issue to track adding back the execute_after_commit feature?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


Do not mangle "Content" and "Meta" classes

As "Content" and "Meta" classes are used to display the object property name in json-formatter we shouldn't uglify it

Codecov Report

Merging #281 into 2.x will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              2.x     #281   +/-   ##
=======================================
  Coverage   76.54%   76.54%
=======================================
  Files          39       39
  Lines         759      759
=======================================
  Hits          581      581
  Misses        178      178

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 4447ec2...f8dd7e2. Read the comment docs.


Can I use the operating system now?

l am new in github so if I  made any mistake in asking this, I am sorry. I just want to know that can I use the beta version.

 Don’t use it as a replacement for your existing os, because there could be bugs that can damage the computer.


Add support for the InlineFormSets

Add the ConvenientBaseInlineFormSet variant to support the InlineFormSets.

Thank you for your contribution! 👍🏻
I have added some documentation for other developers.


Hit error 'This request looks like it might be automated. '

It hits error in the line: await client.create_tweet(comment_content['text'], reply_to=new_tweet.id, media_ids=comment_media_ids)
Error:
twikit.errors.CouldNotTweet: {'message': "Authorization: This request looks like it might be automated. To protect our users from spam and other malicious activity, we can't complete this action right now. Please try again later. (226)", 'locations': [{'line': 18, 'column': 3}], 'path': ['create_tweet'], 'extensions': {'name': 'AuthorizationError', 'source': 'Client', 'code': 226, 'kind': 'Permissions', 'tracing': {'trace_id': '282baea6b4e205d1'}}, 'code': 226, 'kind': 'Permissions', 'name': 'AuthorizationError', 'source': 'Client', 'tracing': {'trace_id': '282baea6b4e205d1'}}
My source code:
# Function to upload media and check file type
async def upload_and_check(file_path : str):
    with open(file_path, 'rb') as f:
        binary = f.read()
    kind = filetype.guess(binary)
    if kind is None:
        raise Exception(f"Cannot guess file type for {file_path}")
    return await client.upload_media(file_path, wait_for_completion=True)

async def random_delay():
    print("Wait 10-20 seconds...\n")
    delay = random.uniform(10, 20)
    await asyncio.sleep(delay)

"""
Sample for post_content:
{
    "text": "Some post content",
    "images": [
        "media\\20240803231338\\test.jpg"
    ],
    "videos": []
}

Sample for comment_contents:
{
    "text": "Some comment content",
    "images": [],
    "videos": ["media\\20240803231338\\test.mp4"]
}
"""
async def create_post_and_comment(post_content: dict[str, any], comment_contents: list):
    post_media_ids: List[str] = []
    for image in post_content['images']:
        post_media_ids.append(await upload_and_check(image))

    for video in post_content['videos']:
        post_media_ids.append(await upload_and_check(video))

    new_tweet = await client.create_tweet(post_content['text'], media_ids=post_media_ids)

    print(f"Created new post: {post_content['text']}\n")

    await random_delay()

    # Create comments under the new tweet
    for comment_content in comment_contents:
        comment_media_ids: List[str] = []
        for image in comment_content['images']:
            comment_media_ids.append(await upload_and_check(image))

        for video in comment_content['videos']:
            try:
                comment_media_ids.append(await upload_and_check(video))
            except Exception as e:
                print(f"Error uploading video: {e}")
                continue  # Skip this video and continue

        await client.create_tweet(comment_content['text'], reply_to=new_tweet.id, media_ids=comment_media_ids)

        print(f"Created new comment: {comment_content['text']}\n")

        await random_delay()
    # Log out
    await client.logout()

Is there any solution?

I just hit this too. However, searching and other interactions are fine

Same for me. any solution?
twikit.errors.CouldNotTweet: {
    "message": "Authorization: This request looks like it might be automated. To protect our users from spam and other malicious activity, we can't complete this action right now. Plea se try again later. (226)",
    "locations": [{"line": 18, "column": 3}],
    "path": ["notetweet_create"],
    "extensions": {
        "name": "AuthorizationError",
        "source": "Client",
        "code": 226,
        "kind": "Permissions",
        "tracing": {"trace_id": "205xxxxxxxfca"},
    },
    "code": 226,
    "kind": "Permissions",
    "name": "AuthorizationError",
    "source": "Client",
    "tracing": {"trace_id": "2053xxxxxdfbfca"},
}

After update is already fixed for me


if role=search, only allow tagName=form

Expected:
an error should be thrown if the role=search and the tagName is not form.
Actual:
no error is thrown and the item renders.
Screenshots
code:

rendered:

Resolved by referenced commits


OCM-4646 | fix: better messages for options prompts

Related issue: OCM-4646

LGTM

ahh, the combination of using Sprintf and += confused me, but yeah looks better now, thanks!


Async docs

This improves performance for slow networks by pulling all the md's at once asyncronously.
The docs are still broken because content is missing so I haven't been able to do a full test.

Merged in master w/ docs content.
Fixed some bugs, should be good to go.

Also added the static site for gh pages into this same PR


load options when creating a new project

This a POC demonstrating how we could expose load options, as in #168
Here, I have provided functionality for one option, SkipValidation. If this approach is accepted, I could write the code for all the other options.
Here is an example of how it is used in docker-lock.
I would love feedback / thoughts.
Thanks!

@ndeloof please let me know if there is anything that I can do to get this merged. Thanks!


feat(android): apply navigation handler to loadUrl calls

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Docs
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Checklist

[x] This PR will resolve #___
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[x] I have added a convincing reason for adding this feature, if necessary
[x] It can be built on all targets and pass CI/CD.

Other information

I waffled on whether to make external function public on the WebViewClient and have the WebView call it, but ultimately it just seemed more direct to add an external function to the WebView that binds to the same rust function.


Conditional Step to skip checkout in azure pipeline?

I don't want to perform checkout process again on each run of azure devops pipeline.

@hassaan4 You can use checkout: none in your YAML file to avoid syncing the sources, as described here:
https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema#checkout
But it sounds like you want to get the sources the first time, but not on subsequent runs?
If you are using a Microsoft-hosted agent, then you are getting a fresh image each time and so any previously fetched sources aren't available. If you are using a self-hosted agent, you can set clean: false, also in the checkout step, and if there haven't been any updates to the code, everything shoud be up to date and nothing will be fetched.
Do either of those options sound like they might work for you?


Japanese locale

Removed Japanese as an option for preferred language for those that select Japan as their country.

PR is approved. Not going to merge until immediately before the next deployment in case an emergency bugfix for unrelated issues is necessary before Japanese users have had sufficient time to save copies of their report.


Bring over the calendar selection from 1.7.x (no Rome)

as a query builder
with admin
when i select the time rage for my query
then i would like to be able to select an arbitrary start and end time using a calendar
we will need to ensure the range function of the query uses start and stop time if selected

an option:
https://github.com/Hacker0x01/react-datepicker


puppet-rsyslog populates client.conf with deprecated parameters even though rsyslog v7 and above support them.

In ../templates/client.conf.erb, puppet-rsyslog populates /etc/rsyslog.d/client.conf with old style parameters rather than the newer style:
Everybody gets emergency messages
.emerg       :omusrmsg:
In Rsyslog documentation, http://www.rsyslog.com/doc/v8-stable/compatibility/v7compatibility.html, the notes say that rsyslog version 7 supports omusrmsg rulesets.  puppet-rsyslog checks for version 8 or higher instead of version 7.  It populates version 7 rsyslog configuration files with older style parameters.
Everybody gets emergency messages
<% if @rsyslog_version and @rsyslog_version.split('.')[0].to_i >= 8 -%>
.emerg       :omusrmsg:
<% else -%>
*.emerg       *
<% end -%>
I recommend that the version checked is "7" rather than "8" so that users of rsyslog v7 and higher aren't nagged with:
please change syntax, 'cron' will not be supported in the future [try http://www.rsyslog.com/e/2184 ]

This is fixed in the current master and will be released soon


addition of config property

property config was not defined

what does it solve?

what does it solve?

on my develop branch it showed me a list of errors including variables not declared, which lead back to properties not defined, but most likely there is something wrong on my side...

I am new to open source and wanted to contribute to CodeIgniter , I did not know it. I'll take it into consideration. Thank you for your support.


where is preprocess_datasets.py?

Fixed.

Thanks!

@nkolot , sooorry bother you again. json file seems also missed. Could you please upload them?

Sorry for that, I fixed it. The config.json I added in the folder data is essentially the same config file that  the training code automatically dumps when you start training.


[Bug]: Deadlock between DockerClientFactory and RyukResourceReaper with JUnit 5 parallel tests

Module
Core
Testcontainers version
1.20.1
Using the latest Testcontainers version?

I'm attempting to run tests in parallel with JUnit 5. One test spins up a static ComposeContainer with .withLocalCompose(true) and another spins up a static KafkaContainer. This leads to a deadlock on startup, where one thread acquires the lock on RyukResourceReaper and then fails to acquire the lock in DockerClientFactory, while the other thread does the opposite.
Relevant log output
Kafka container thread:
"testcontainers-lifecycle-0" #35 [41731] daemon prio=5 os_prio=31 cpu=207.18ms elapsed=23.45s tid=0x000000012225ba00 nid=41731 waiting for monitor entry  [0x00000001735fa000]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at org.testcontainers.utility.RyukResourceReaper.maybeStart(RyukResourceReaper.java:74)
	- waiting to lock <0x000000060201f118> (a org.testcontainers.utility.RyukResourceReaper)
	at org.testcontainers.utility.RyukResourceReaper.init(RyukResourceReaper.java:42)
	at org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:232)
	- locked <0x000000060201ee60> (a [Ljava.lang.Object;)
	at org.testcontainers.DockerClientFactory$1.getDockerClient(DockerClientFactory.java:106)
	at com.github.dockerjava.api.DockerClientDelegate.authConfig(DockerClientDelegate.java:109)
	at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:329)

Compose container thread:
"testcontainers-lifecycle-1" #37 [37891] daemon prio=5 os_prio=31 cpu=3.14ms elapsed=23.41s tid=0x0000000122254600 nid=37891 waiting for monitor entry  [0x0000000173a12000]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:185)
	- waiting to lock <0x000000060201ee60> (a [Ljava.lang.Object;)
	at org.testcontainers.DockerClientFactory$1.getDockerClient(DockerClientFactory.java:106)
	at com.github.dockerjava.api.DockerClientDelegate.authConfig(DockerClientDelegate.java:109)
	at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:329)
	at org.testcontainers.utility.RyukResourceReaper.maybeStart(RyukResourceReaper.java:78)
	- locked <0x000000060201f118> (a org.testcontainers.utility.RyukResourceReaper)
	at org.testcontainers.utility.RyukResourceReaper.registerLabelsFilterForCleanup(RyukResourceReaper.java:51)
	at org.testcontainers.containers.ComposeDelegate.registerContainersForShutdown(ComposeDelegate.java:247)
	at org.testcontainers.containers.ComposeContainer.start(ComposeContainer.java:125)
	- locked <0x000000060201f2a8> (a java.lang.Object)

Additional Information
No response

Hi @pkwarren, can you please provide a project that reproduces the issue?

Here's an example repo showing the problem: https://github.com/pkwarren/testcontainers-issue-9120

Thanks for sharing @pkwarren. I did some changes because the docker-compose.yml file was not found and also had to set version but can not reproduce the issue. Do you mind taking a look?

the docker-compose.yml file was not found

It should be here: https://github.com/pkwarren/testcontainers-issue-9120/blob/main/docker-compose.yml

also had to set version

I don't follow - where did a version need to be specified?

can not reproduce the issue. Do you mind taking a look?

If you could provide more specifics on what you're doing and any errors you're seeing I'd be happy to update the example project. For me just running ./mvnw clean verify hangs - if you use jstack to look at the PID of the launched Maven surefire process you can see the deadlock.

the docker-compose.yml file was not found

I had to change from ComposeContainer("docker-compose.yml") to ComposeContainer(new File ("docker-compose.yml"))

I don't follow - where did a version need to be specified?

I was talking about version in docker-compose.yml file. But executing again, I don't need it anymore.
I jus wanted to make sure we have the same code to reproduce. After that, just ran ./mvnw clean verify and everything executed successfully. I am also running on Mac M1 Pro.

Pushed updates to fix the ComposeContainer constructor usage and switched the container in docker-compose.yml to be Kafka (in case we're running into a race condition and starting up nginx is too fast to repro the problem). Hopefully this will allow you to see the same behavior I'm seeing.
I'm on the latest version of Docker desktop (v4.33.0) if it matters.


feat: ai-proxy support custom error handler by cover DefaultErrorHandler

Ⅰ. Describe what this PR did
解决如 https://github.com/alibaba/higress/issues/1532 描述的问题，允许替换错误处理部分，添加自定义逻辑
Ⅱ. Does this pull request fix one issue?

https://github.com/alibaba/higress/issues/1532
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

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

Project coverage is 43.52%. Comparing base (ef31e09) to head (8db8e45).
Report is 206 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1537      +/-   ##
==========================================
+ Coverage   35.91%   43.52%   +7.61%
==========================================
  Files          69       76       +7
  Lines       11576    12320     +744
==========================================
+ Hits         4157     5362    +1205
+ Misses       7104     6622     -482
- Partials      315      336      +21

see 69 files with indirect coverage changes

----
🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles


post easier-to-install deliverables such as R libraries and/or installers

from ODOT:

We are curious if the modules and other github materials will ultimately be available as R libraries or if the plan is to host them on GitHub indefinitely
Wondering about how the install directions will be laid out in the future and if the idea will be to create a wrapper or some other kind of batch process to make it easier on folks less familiar with R

response:

yes, eventually a more user friendly set of resources will be available, but for now, we're focused on the VE developer, which assumes sufficient knowledge of R to run the install commands in the READMEs.

I think that when we get to the point that there are about half a dozen modules, we should put prebuilt packages in the repo. These would be windows build only. Mac and Linux users would need to build their own. Also, the early packages show how packages can be customized with regional data. This is an important concept of VisionEval and one that reviewers need to pay attention to. That is why packages take a while to build. Perhaps we should have a simple users guide on how to build packages from source files using R Studio.

We'll plan to do this as part of the user-oriented development work related to the GUI/visualizer/documentation.


gpu_nfdhook memory amount reading from sysfs

This adds reading of the GPU memory amount from the sysfs. As a
fallback the environment variable GPU_MEMORY_OVERRIDE remains.
Another environment variable GPU_MEMORY_RESERVED can be used to
reserve a dedicated byte amount outside of kubernetes usage.
Signed-off-by: Ukri Niemimuukko<EMAIL_ADDRESS>

Codecov Report

Merging #482 into master will increase coverage by 0.33%.
The diff coverage is 78.78%.

@@            Coverage Diff             @@
##           master     #482      +/-   ##
==========================================
+ Coverage   58.30%   58.64%   +0.33%
==========================================
  Files          30       30
  Lines        2094     2118      +24
==========================================
+ Hits         1221     1242      +21
- Misses        808      810       +2
- Partials       65       66       +1

Impacted Files
Coverage Δ

cmd/gpu_nfdhook/main.go
0.00% <0.00%> (ø)

cmd/gpu_nfdhook/labeler.go
71.84% <81.25%> (+0.95%)
:arrow_up:

pkg/deviceplugin/server.go
85.82% <0.00%> (+2.23%)
:arrow_up:

Continue to review full report at Codecov.

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


feat: add support for JSON format in output

centos-package-cron does not currently have the ability to output results in a machine-readable format (e.g. for automated checks).
This pull request implements a -j / --json flag to format output as JSON.
Current output
The following security advisories exist for installed packages:

Advisory ID: adv id
Severity: Important
Packages:
* libgcrypt-1.5.3-4.el7
References:

The following packages are available for updating:

libgcrypt-1.5.3-4.el7 from updates

Change logs for available package updates:

libgcrypt-1.5.3-4.el7
stuff

JSON output
{
    'advisories':[{
        "advisory_id": "adv id",
        "packages": ["libgcrypt-1.5.3-4.el7"],
        "severity": "Important"
    }],
    'updates':[{
        "name":"libgcrypt-1.5.3-4.el7",
        "source":"updates",
        "changelog": "stuff"
    }]
}

Contributors
Alex Wilson (@mrwilson)
Narayan O'Hanlon (@nryn)
Sarah Young (@sarahseewhy)
Stephen Geller (@stephengeller)

Thanks a lot for these changes! This opens up a lot of possibility.


[#4126] improvement(core): Remove MetalakeAdmin API

What changes were proposed in this pull request?
Remove MetalakeAdmin API.
Why are the changes needed?
Fix: #4126
Does this PR introduce any user-facing change?
Remove API. But this API isn't released.
How was this patch tested?
Existing tests.

@yuqi1129 @jerryshao Could you help me review this pull request?

@yuqi1129 @jerryshao Gently ping.

@jerryshao Gently ping.


msrest dependency conflict with other sdk libs

Package Name:  azure-storage-blob
Package Version: latest (12.14.1)
Operating System: Ubuntu
Python Version: 3.7

Describe the bug
I have a project, where I want to use this lib and the azure-storage-blob lib. I'm having a dependency conflict since this lib requires "msrest>=0.7.1,<0.8.0".
This is the error I'm getting:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
azure-devops 6.0.0b4 requires msrest<0.7.0,>=0.6.0, but you have msrest 0.7.1 which is incompatible.

To Reproduce
pip install azure-storage-blob && pip install azure-devops
Expected behavior
No dependency conflict.
Additional context
In the changeslog.md https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/storage/azure-storage-blob/CHANGELOG.md of the azure-storage-blob lib, I saw that msrest will be removed as a requirement in the next release (12.15.0b1). However it is not released yet. Would this version solve my problem when it is released?

Thank you for the feedback @nidhaloff. We will investigate and get back to you.

Hi @nidhaloff Nidhal, in our upcoming release, 12.15.0b1, we have eliminated the dependency on msrest altogether so you should no longer have this issue if you use that version. That version is scheduled for release early next month (February) but is a preview release if that is an issue for you. The official release of 12.15.0 should come a few weeks after that and will also remove the msrest dependency.

Hi @nidhaloff Nidhal, in our upcoming release, 12.15.0b1, we have eliminated the dependency on msrest altogether so you should no longer have this issue if you use that version. That version is scheduled for release early next month (February) but is a preview release if that is an issue for you. The official release of 12.15.0 should come a few weeks after that and will also remove the msrest dependency.

Nice! Thanks


Add compiler/cpp/lex.yythriftl.cc to gitignore.

I've accidentially checked that file in in another PR. So this commit
adds that file to the .gitignore.
Might be that this is only a temporary file, as I got some compiling issues.
Should be ignored anyway.

Tracked in THRIFT-3074
Please have a look at our contribution guide


Fix the issue of reporting UnexpectedEof when client disconnected immediately

Closes #354
Description
This issue occurred when client disconnected immediately without sending a Terminate message.
As client closed the socket directly, the server side could only receive a zero byte for client close.
Is it a feature that change user experience?
no
Client output
This issue could be reproduced as @alex-dukhno 's comment in #354 when running compatibility tests, or run the below groovy script.
groovysh
groovy:000>

:grab org.postgresql:postgresql:9.4-1205-jdbc42
import groovy.sql.Sql

dbConf = [
  url: "jdbc:postgresql://localhost:5432/test?gssEncMode=disable&sslmode=disable&preferQueryMode=extendedForPrepared",
  user: "postgres",
  password: "postgres",
  driver: "org.postgresql.Driver",
]

db = Sql.newInstance(dbConf)

Then exit directly as below (or CTRL + C) without calling db.close().
groovy:000>:exit

The log message [protocol] client disconnected immediately should be displayed with this fix.

Hi @alex-dukhno , please wait me to fix the test. Thanks.

Will try to figure out the failed cargo-deny.

Pull Request Test Coverage Report for Build 297683996

13 of 16 (81.25%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 88.456%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/protocol/src/lib.rs
9
12
75.0%

Totals

Change from base Build 294000850:
-0.04%

Covered Lines:
7908

Relevant Lines:
8940

💛  - Coveralls


Switch from localhost to <IP_ADDRESS>

The container is a binary only container without /etc/hosts or /etc/resolv.conf which will hit the dns server to resolv localhost -> <IP_ADDRESS>
We had the case that there was a VM named localhost in the cloud and when hitting the DNS to resolv localhost we got the IP from this vm instead of <IP_ADDRESS>.
Took hours to find this issue :(

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

/ok-to-test

/retest

@gianrubio
Done so i'm looking forward to see this merged :)


Issues with Json parse..

I´m using python3 and after few modifications and run the virustotal.py script I got the following error message:
if json_data['results']['response_code'] == 1 and
KeyError: 'results'*
I have googled and I didn't found any possible solution or workaround for this, any idea?

@francsam01 I don't know if you are still interested in an answer to this but I modified the project and was not able to recreate the error you mentioned. My fork is https://github.com/notmyhash/virustotal-api-hashcheck if you are still interested.


ci: adding Amarna static analysis for Cairo

Trail of Bits just released Amarna, a static analysis tool for Cairo (as is Slither for Solidity).
This PR adds a new CI job to run the analysis tool on our Cairo code.

Just experimenting, TBH I don't fully know what will it do 😂

1009 new alerts 🙈


"Descope" OLM delivered operators

Feature Request

Note: This issue mostly consists of select snippets from a document @ecordell drafted a while back. I've curated the important bits to frame the problem for further discussion.

Scoping, Descoping, What?
In short, when we talk about "scope" in OLM, we're talking about how OLM handles the privileges granted to an operator and its users with respect to the namespaces an admin configures it to install; i.e. the opinionated behavior of RBAC generation around ClusterServiceVersions, their InstallModes, and OperatorGroups.

Note: see the OperatorGroup docs for more details.

Problem
APIs in a kubernetes cluster are cluster-scoped. They are visible via discovery to any user that wishes to see them. Even operators that agree on a particular GVK may have differences of opinion in how those objects should be admitted to a cluster, or how conversion between API versions should happen.
With Operator Framework, we want to build an ecosystem of high-quality operators that can be re-used across different projects, whether they’re in the same cluster or not. But re-using operators compounds the scoping problems within a cluster - it increases the likelihood that more than one “opinion” about an API exists in the cluster.
History
When OLM was first written, CRDs defined only the existence of a GVK in a cluster. Operators developed for OLM could only install in a namespace, watching that namespace - this delivered on the self-service, operational-encoding story of operators. The same operator could be installed in every namespace of a cluster.
Privilege escalation became a concern - since operators are run with a service account in a namespace, anyone with the ability to create workloads in that namespace could escalate to the permissions of the operator. This made service provider/consumer relationships a difficult sell for operators in OLM.
At the same time, CRDs continued to add features. With version schemas and admission and conversion webhooks, CRDs no longer simply registered a global name for a type, and operators in separate namespaces had lots of options to interfere with one another if they shared the same CRD. OLM also expanded to support APIServices in addition to operators based on CRDs, and so required a notion of cluster-wide operators.
To address these concerns, a notion of scoping operators was introduced via the OperatorGroup object. An OperatorGroup would specify a set of namespaces within a cluster in which all operators installed would share the same scope. OLM would ensure that only one operator within a namespace owned a particular CRD to avoid collision problems, and more installation options were provided to allow separating operators from their managed workloads.
Proposal
Entirely remove the notion of scoping from OLM; i.e. "descope".
This means that:

Only one operator that provides an API -- e.g. via CRD or APIService -- may be installed simultaneously
OLM stops being opinionated about how privileges are granted to operators and users; i.e. OperatorGroups, InstallModes, and today's generated RBAC are deprecated and removed
Operator authors and admins use more traditional means -- e.g. (cluster)Roles/RoleBindings -- to declare cluster privileges for both operators and their users

It does not mean that:

Every operator needs to have permission to do its job in every namespace
Every user in a cluster needs to have permission to use the operator's APIs
Only one controller pod needs to run for that api in a cluster
Only one controller can be installed to manage an API (i.e. ingress-style)
More sophisticated privilege generation cannot be used; e.g. FeatureBinding

Design!?
The specifics of how we will achieve descoping will need an enhancement proposal to be made clear. Such a proposal will, at minimum, need to cover:

Deprecation of related APIs; e.g. OperatorGroups, ClusterServiceVersions, etc
Migration of existing operator content; i.e. How does an author define a scoped -> descoped operator upgrade? what does a cluster admin need to do?
If/how existing "scope user stories" can be achieved after "descoping"; e.g. config management
How does Operator Discovery work without a first-class concept of scoping?

Is there any proposal yet or draft of one?


A way to disable MKL?

Hey i am running on an ARM system where MKL doesn't exist as such. BLASBenchmarksCPU automatically (init) running mkl related code is not elegant. What would be a good way to handle this?

Hey, just wondering, is it working with the way "Example 2" is suggesting or the problem occurs when the package is "starting"? [https://julialinearalgebra.github.io/BLASBenchmarksCPU.jl/stable/usage/]

No the error happens before that. During using in the init function.

Stacktrace:
 [1] error(s::String)
   @ Base ./error.jl:33
 [2] compilecache(pkg::Base.PkgId, path::String, internal_stderr::IO, internal_stdout::IO, ignore_loaded_modules::Bool)
   @ Base ./loading.jl:1466
 [3] compilecache(pkg::Base.PkgId, path::String)
   @ Base ./loading.jl:1410
 [4] _require(pkg::Base.PkgId)
   @ Base ./loading.jl:1120
 [5] require(uuidkey::Base.PkgId)
   @ Base ./loading.jl:1013
 [6] require(into::Module, mod::Symbol)
   @ Base ./loading.jl:997

LoopVectorization will still crash on the A64FX, so Octavian at least won't work.

Thanks for supporting FUGAKU! :-)

I hope to see FUGAKU and more vector-CPU super computers succeed in the future!
The issue that LoopVectorization/Octavian has looks like it'd need some digging to get into/isolate.
I hope to replace the current code base, hopefully within the next few months, and thus would hope that those issues can be resolved/avoided at that time.

Great to hear that! And thank you again for making the appropriate changes to BLASBenchmarksCPU.jl so it can be run on Arm! AFAIK, FUGAKU is open for trials with projects screening per submission throughout the whole year. Heaving the opportunity, can I ask some very basic questions about BLAS libraries?
So far I used mostly OpenBLAS shipped natively with Julia. Following your advice provided at Julia discourse I also used MKL.jl with Julia 1.7 (Yeah, I know how it sounds, however, it was a very good advice). When I was using MKL instead of OpenBLAS with some of Julia packages I did not have to change anything in the code of the packages. It was as easy as writing "using MKL" and I understand I was doing calculations with MKL instead of OpenBLAS.
Is it the same with Octavian.jl? Or do I have to rewrite the code of the package in order to use Octavian.jl?
And also, I am hearing that on Arm, particularly Arm Performance Version of BLAS and BLIS is heaving a good performance. If I would like to try any of them (Arm Performance Version of BLAS or BLIS), how do I make it work with Julia on Arm? Should I build _jll and pin this _jll in Julia package mode? Is there maybe any tutorial that you are aware of / maybe you could point me to any resource on this topic?
And the last question, is it correct to assume that Octavian.jl if/when working on Arm / vector-CPUs could bring significant performance increase?

I address the questions i can answer.

Is it the same with Octavian.jl? Or do I have to rewrite the code of the package in order to use Octavian.jl?
Octavian exports as only public function is matmul!(C, A, B[, α, β, max_threads]) (according to docs). which means it doesn't change the definition of *(A::AbstractMatrix, B::AbstractMatrix) or similar calls. MKL.jl does that. This is a change that would need to be done by one person once. Without that an algorithmic rewrite of your code would be necessary.

How do I make  Arm Performance Version of BLAS work with Julia on Arm?
If it doesn't exist already, you need to write an equivalent to MKL.jl or BLIS.jl.

Should I build _jll and pin this _jll in Julia package mode?
A _jll (which is a reproducible build instruction of the binaries for a selection of targets) is not enough alone. You will need to write a Julia wrapper which provides definitions for *(A::AbstractMatrix, B::AbstractMatrix) and many other calls. Since the API is probably quiet similar you can adapt from  MKL.jl, OpenBLAS or BLIS.jl

How do I make  BLIS work with Julia on Arm?
Try the package BLIS.jl see if it works and passes tests, if not make it work. (Details depend on failure mode)

Is there maybe any tutorial that you are aware of / maybe you could point me to any resource on this topic?
Look at the source code of similar packages and watch Developing Julia packages if you didn't already, although the recommendation to use TravisCI is outdated.

And the last question, is it correct to assume that Octavian.jl if/when working on Arm / vector-CPUs could bring significant performance increase?
In Julia as it's now, probably not, as Julia likes to emit NEON vector instructions which don't utilize the SVE vector registers. If Julia can be made to emit competitive SVE code then it is likely that Octavian with some tuning is competitive on A64FX.

On Julia 1.7+, the LinearAlgebra BLAS libraries use libblastrampoline:
julia> LinearAlgebra.BLAS.libblas
"libblastrampoline"

Which is what allows swapping BLAS implementations at runtime.
For this to work with a library like Octavian, it'd have to provide all the appropriate ccalls.
gemm is the building block of many more complicated BLAS/LAPACK algorithms, so it'd be interesting to see what the performance of LAPACK would be if you swap out OpenBLAS's gemm for Octavian (or even raw LV), which does much better at small sizes.
Longer term, these can be implemented in Julia, but I will be prioritizing rewriting LV before working on LinearAlgebra, as the rewrite will (a) help compile times and (b) make implementing many algorithms much easier.

If Julia can be made to emit competitive SVE code then it is likely that Octavian with some tuning is competitive on A64FX.

This requires setting the min-SVE bits arg, but that seems to be causing crashes.

Thanks a lot for all the information! As for the Arm Performance Version of BLAS and writing a wrapper really I do not think its right for me to do it. As for BLIS I see that it probably performs better on Neoverse N1 than OpenBLAS that I used for testing (pls see here https://github.com/flame/blis/blob/master/docs/Performance.md). I hope to have the oportunity to carry some of the tests further with BLIS in the near future. I think I can say that Julia on Neoverse N1 was already competitive to x86 and GPU with standard OpenBLAS or at least this is my current understanding. As for potential competitive performance on A64fx I'm optimistic to do some tests in the near future.

gemm is the building block of many more complicated BLAS/LAPACK algorithms, so it'd be interesting to see what the performance of LAPACK would be if you swap out OpenBLAS's gemm for Octavian (or even raw LV), which does much better at small sizes.

I do not have precise knowledge regarding the sizes of matrices. The tests I was doing are related to AI trainings. Pls find the summary, including results on Arm architecture at this link (https://ibmb2.s3.eu-de.cloud-object-storage.appdomain.cloud/test_results_comments_git.txt). The file might not be available long term as I am sometimes deleting all objects there. I would be really happy to carry the tests suggested above in near (or medium / long term) future when my time permits (optimistic about it, however, sometimes there are some constraints) even if the setup would not be appropriate for the above mentioned AI problem. As for the technical requirements, I might need some advice then, as for now I have to admit that even after re-reading the posts, I would not know how to do it.


Total Row always appear at bottom

Hello, is there a way to always get the total row to always appear at the bottom of the able after the last row and not have all the whitespace resulting form the new height of the table being smaller than the original size of the table?

This spacing issue occurs when we dynamically change the data results of the table and they are less than the original amount

As per your example
https://facebook.github.io/fixed-data-table/example-filter.html
Is there a way to have the table border resize with the table so it doesn't stay at the bottom?


occm: Fix LoadBalancer deletion when the underlying LoadBalancer does…

… not exist (#1913)
cherry pick #1913

What this PR does / why we need it:
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

NONE

/approve

@jichenjc , thanks for the cherry-pick!

/lgtm

/override openstack-cloud-csi-cinder-e2e-test-release-123
/override openstack-cloud-csi-manila-e2e-test-release-123
Both components are not affected by those changes.


read_dir miss some files in multiple file directories

I use fs.open_dir("$path").await.unwrap().read_dir().await.unwarp() to list all files in a directory. It will always miss some files in multiple file directories. I tries reconnecting to server, rebooting the servers, rewriting the files, using other network environment. It will trigger this issue steadily.
Reproduction code
#[tokio::main]
async fn main() -> Result<(), Box<dyn Error>> {
    let url = "SECRET";

    let session = SessionBuilder::default()
        .user("ymz".to_owned())
        .keyfile("SECRET")
        .connect(url)
        .await?;

    let mut child = session
        .subsystem("sftp")
        .stdin(Stdio::piped())
        .stdout(Stdio::piped())
        .spawn()
        .await?;

    let sftp = Sftp::new(
        child.stdin().take().unwrap(),
        child.stdout().take().unwrap(),
        Default::default(),
    )
    .await?;

    let mut fs = sftp.fs();
    fs.set_cwd("/home/ymz/sftp_test/");
    let dir = fs.open_dir("./test_list_rich_dir/").await.unwrap().read_dir().await?;
    let mut actual = vec![];
    for entry in dir {
        actual.push(entry.filename().to_owned());
    }
    actual.sort_unstable();
    println!("{:?}", actual);

    Ok(())
}

shell output
[".", "..", "file-0", "file-1", "file-10", "file-100", "file-11", "file-12", "file-13", "file-14",
 "file-15", "file-16", "file-17", "file-18", "file-19", "file-2", "file-20", "file-21", "file-22",
 "file-23", "file-24", "file-25", "file-26", "file-27", "file-28", "file-29", "file-3", "file-30",
 "file-31", "file-32", "file-33", "file-34", "file-35", "file-36", "file-37", "file-38", "file-39",
 "file-4", "file-40", "file-41", "file-42", "file-43", "file-44", "file-45", "file-46", "file-47",
 "file-48", "file-49", "file-50", "file-51", "file-52", "file-53", "file-54", "file-55", "file-56",
 "file-57", "file-58", "file-59", "file-6", "file-60", "file-61", "file-62", "file-63", "file-64",
 "file-65", "file-66", "file-67", "file-68", "file-69", "file-7", "file-70", "file-72", "file-73",
 "file-74", "file-75", "file-76", "file-77", "file-78", "file-79", "file-8", "file-80", "file-82",
 "file-83", "file-84", "file-85", "file-86", "file-87", "file-88", "file-89", "file-9", "file-90",
 "file-91", "file-92", "file-93", "file-94", "file-95", "file-96", "file-97", "file-98", "file-99"]

ssh terminal screenshot

We can see that it misses file-5, file-71, file-81. In multiple tests conducted, these three files were always lost.
According to my tests, as long as the number of files in the directory is greater than 100, this error will be generated. If there are only 90 files, it will run correctly.

Thanks for reporting this bug!
I will investigate the problem and push a fix for this ASAP.

I think it's likely I misunderstood the SSH_FXP_READDIR: One single request may not return every dir entries.
It is design after unix syscall after all, so no wonder its
I would change the implementation to issue multiple SSH_FXP_READDIR until it returns an empty Box.
That also means I will have to break the API so that ReadDir would instead implements futures_utils::Stream which you would have to poll to get the next entry and is lazy just like iterator.
This new API will be similar to tokio::fs::ReadDir.
@silver-ymz If you would like me to keep the existing API, feel free to inform me and tell me the rationale behind it.

It's okay to break the API. The project I contributed also uses a polling-based API. I think it's easy to modify my code to adapt to the new API.

Good to hear that!


Replace ComposeThread

One common issues alpha testers have reported with the app is that it's too easy to accidentally create a thread that already exists. I tried to solve this with the "existing threads" panel in ComposeThread, but I think we'll need to fundamentally rethink this, because most people still miss it.
I think I like what Facebook Messenger does. When you hit the compose button, it pops up a modal with a TagInput at the top. As you add users to the TagInput, the area in the modal below the TagInput becomes a MessageList. If a thread with the users you've selected already exists, that thread's MessageList is displayed. If there is no such thread yet, it effectively shows what we call a "pending" thread, which gets created as soon as you send the first message.

Clicking new thread button should open a thread composer.
Thread composer on Android should be displayed as a full-width modal, with content that initially is slightly smaller and then grows to fill all the available space.
https://drive.google.com/file/d/18e-sIYrGS_A0QK3BXBOqeTXmnpdu4Mow/view?usp=sharing
Thread composer on iOS should be displayed as full-width modal, which is displayed above the rest of the app. The modal should not take the whole vertical space: there should be a gap at the top and the rest of the app (with slightly reduced size) should be displayed beneath it. Modal should appear from the bottom, and main app screen should shrink and move down, below the status bar.

Thread composer should consist of user search component and message list.
User search component allows searching for users and selecting multiple entries - just like in friend / block list.
When a thread with exactly the same set of members, as selected in the search component, exists, then it should be displayed, otherwise a pending thread should be displayed.
Sending a message in a pending thread should create a real thread.
Sending a message in any thread should open it in a usual way (outside the thread composer).
Open questions:
What should we do if there are couple of matching threads? We can probably display a list of them.
On iOS selecting users is achieved by a checklist, but I guess we should use the same approach as on Android (like tag input).
On iOS the thread was displayed only after selecting users and clicking done (tested on iPhone 8), but I think we should display a message list instead, just like on Android.
Tasks:

Create a modal (we can split this task by OS)
Create a thread composer component with search component
Modify message list so that it can be displayed inside the composer
Display the list in the composer
Handle sending a message: send a message and open list view outside the modal
Handle sending a message: create a real thread
Open thread composer after clicking new thread button
Remove old thread composer

Some thoughts:

I don't have permissions to see the Google Drive link you sent. In the future, if you want to embed a video into a GitHub comment, you can convert it to an animated GIF and then embed the GIF. But might be too much work for you.

We don't need to match the individual platform behavior 100%. For simplicity we can pick the same approach for iOS/Android. Unless React Navigation makes it easy to match the platform behavior, in which case we might as well.

It's worth noting that the "user search component" should display iff (a) the tag list is empty, or (b) the text input is non-empty.

Let's make sure we only "autocomplete" threads that don't have parent threads.

What should we do if there are couple of matching threads? We can probably display a list of them.

Hmm, displaying a list of matching threads seems like it will be challenging in terms of UX. At a higher level, our approach here should make it unlikely that there are multiple matching threads going forward, since the UI will make it impossible to create a second matching thread if one already exists. So if there are multiple matching threads, I think we can simply select the oldest one.

On iOS selecting users is achieved by a checklist, but I guess we should use the same approach as on Android (like tag input).

For some reason the experience you're seeing in Messenger on iOS is a bit different from what I'm seeing. I see a tag input without checkboxes. Let's definitely plan on taking the tag input approach, without any checkboxes.

On iOS the thread was displayed only after selecting users and clicking done (tested on iPhone 8), but I think we should display a message list instead, just like on Android.

I agree, and also worth noting that on my iPhone, Messenger doesn't have a "done" button. It seems to work like how you're describing the Android version.

Another thought: I wonder if we could make the transition from "ComposeThread" to "MessageList" cleaner if we actually used the same React Navigations screen for both.
Some implications:

The tab bar would stay visible, although this won't matter much since the keyboard will be in front of it
The default animation will be different from what we see in Messenger. Standard behavior will be to show the MessageList in the same way we normally do. We could consider a different style of animation if React Navigation supports it and we feel it looks better
The transition from "pending thread" to "real thread" should be more clean if we don't need to change React Navigation screens

@palys-swm, what do you think?

I'm not sure if I understand if we actually used the same React Navigations screen for both correctly. Do you mean, that we should have only one route (Chat.Screen MessageListRouteName) for both message list and thread composer, maybe with a param and based on that param we decide which thread to display and whether we should display a search component?
If that's correct, then the transition should be really smooth (as we only change the params). We can decide to always display message list as a "modal" (full width and height, but showing from the bottom and dismissible by down gesture).
Regarding the tab bar, hiding it behind the keyboard is not a solution: it's possible for a device to have a physical keyboard. What we can do, is to hide the tab bar for a certain path / params. But we should think whether hiding the tab bar is really necessary.
I think that overall it might be a good idea: the experience should be improved.

We can decide to always display message list as a "modal" (full width and height, but showing from the bottom and dismissible by down gesture)

For the standard MessageList animation (when we select a thread from the ThreadList) I think I would prefer to keep the current behavior.
The more I think about it, the more I wonder if having a modal animation even makes sense. We could keep the same behavior but just keep it as a standard StackNavigator card: showing from the right, and dismissable by swiping to the left. What do you think?

Regarding the tab bar, hiding it behind the keyboard is not a solution: it's possible for a device to have a physical keyboard. What we can do, is to hide the tab bar for a certain path / params. But we should think whether hiding the tab bar is really necessary.

If we take the "standard StackNavigator card" approach, I think we could avoid worrying about the tab bar.

Agree, this is probably the simplest solution

Hmm, displaying a list of matching threads seems like it will be challenging in terms of UX. At a higher level, our approach here should make it unlikely that there are multiple matching threads going forward, since the UI will make it impossible to create a second matching thread if one already exists. So if there are multiple matching threads, I think we can simply select the oldest one.
There will be an option for multiple matching threads to be created: whenever a user leaves (or joins) a thread, there's an opportunity for this thread to have the same set of users as one another. It might even happen that the thread was older than the original and would appear as a search result instead.

That makes sense. I think it's okay to accept that we'll autocomplete the older of the two threads in this edge case


Feature: Added option to set default column sizes

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

Closes #9867

Comments

I set the default widths for columns at 200 (this is used when the user resets layout options). Is this ok?
When resetting layout options, page needs to be swapped in order to see changes (I'm not sure about how to proceed to fix this).

Validation
How did you test these changes?

[x] Built and ran the app

Last commit is to avoid 0px but still visible columns.

I set the default widths for columns at 200 (this is used when the user resets layout options). Is this ok?

What did we use before?

When resetting layout options, page needs to be swapped in order to see changes (I'm not sure about how to proceed to fix this).

This can be left as it is for now but we should track it in an issue, I had the same issue with #10089

What did we use before?

Actually we're already using it, I hadn't seen it

It looks like settings the widths as the default resets the overrides. Steps to reproduce

Reset preferences
Navigate to a directory (eg. folder 1) and change the columns widths
Navigate to a different directory (eg. folder 2) and set the column widths as the default
Go back to the folder 1 and see that it's now using the column widths from folder 2

I'll investigate further, but actually everything seems to work
https://user-images.githubusercontent.com/102259289/193914994-9b3d7c1d-8d34-4246-878d-5782899b20bf.mp4

I tried both recloning the repository and testing on a different device (Win10) but I'm still not able to reproduce this bug

I can't reproduce it either


Renaming file should rename class

Addresses part of #109.
Currently since there isn't an event to listen which indicates a rename of file completion,  Listening to workspacechange event. Will have to come back and put the right events.
This addresses the first requirement that the namespace needn't have to follow folder structure.

You want to sync with the latest changes.

This is a great start, a couple of additional comments:

You want to make sure that any non-CPS/Roslyn API that you call is done on a UI thread

I think you'll want a couple of interfaces/components in-between that make testing this thing easy. At the moment, you're going to have to figure out how to mock VisualStudioWorkspace to unit test this.

Be mindful of any mutable state that you have - every component in CPS is free-threaded, any state that you mutate you need make sure is thread-safe.

I added few Unit Tests and did bit of refactoring to make the testable.
pls review when you have a moment

Sorry, I ended up in meetings all afternoon. Will look at this tomorrow morning.

I went through the new commits one-by-one and added comments, sorry if I added comments to no longer existent/changed code.

:+1:
Can you make sure there's items/bugs on:

Adding VB support
Extending the pattern (generics, etc)
Moving from workspace changes -> language service notification
Introducing a base class that verifies something is in UI thread.


[xcodeproj] IDE issues with test projects / xcodeproj

I'm working to add a new way to speed up rules_ios builds that use frameworks, AKA virtual frameworks ( #277 ). On the Xcode side  hitting a few hiccups with test projects today. I've attempted to get a baseline of what is already working in rules_ios but, most of the example projects are broken from the IDE's perspective. This includes debugging, jump to definition, and other features.
To reproduce:
git clone git@github.com:bazel-ios/rules_ios.git
cd rules_ios
bazel run tests/ios/xcodeproj:Test-Imports-App-Project
open tests/ios/xcodeproj/Test-Imports-App-Project.xcodeproj

I've noticed that rules_ios requires a build to copy some files into derived data. I tried doing a build of the app in the test project TestImports-App inside of Xcode as well.
Debugger

Set a breakpoint inside of the main file
Run the program
observe that breakpoints don't resolve - see attached screenshot

Source editor

Open the file empty.swift
Navigate to the interface of a symbol from "SomeFramework"
observe it navigating to a generated location

I think this is a known issue: we did not do some treatment that we do in downstream project that enabled debugging in sample projects.  (specifying search paths in build settings etc.)
One thing to try is to manually set things under build setting under xcode such as framework search paths and you might get debugger running again.

Yep it looks like there's a few issues in the samples causing both indexing and debugging to not work.
That said, I think there's a few issues to or next steps to break out:

getting the examples working so devs can iterate on features in a small use caes
levering the examples to use as integration test cases
increasing the coverage on IDE indexing in general
ensuring that the incantation of the downstream project isn't busted

For me, I filed this issue less around 2, 3, 4, and more on 1. As a maintainer, It was hard to come up with a baseline for what is and what isn't working then make changes to it. XCHammer has a nice methodology and extensive test suite for this by evaluating compiler invocations in a build. Pt 4 is more difficult but definitely achievable depending on how the test is structured


JCS-216 - Redundant cast call

Replace class.cast whit explicit Cast

Hi,
the rational to use .class.cast instead of () is it enables to use a function (so is consistent with other programming style) but also to debug it properly at need "directly" whereas with a standard cast it is hardcoder to do.
So overall I think we should keep it if possible.

HI @arturobernalg
I don't  really understand about "enables to use a function". I think the use does't change.
TY

@arturobernalg .class.cast is a function in java.lang.Class class, as any java method which is the reason it was preferred for this part of the code over instanceof/() casting which is a language feature directly translated to a bytecode instruction.

@arturobernalg .class.cast is a function in java.lang.Class class, as any java method which is the reason it was preferred for this part of the code over instanceof/() casting which is a language feature directly translated to a bytecode instruction.

Hi @rmannibucau
suena razonable


Lates version should be marked differently

@bosko-m we agreed on our call on Friday that the latest version will be marked orange like the other active tabs;

env: PROD
Test passed.


Incorrect regex example in index signature

https://github.com/kcl-lang/kcl-lang.io/blob/6ce704886cdc58a2b71319c27b8e09c4e19671f9/docs/reference/lang/tour.md?plain=1#L2202-L2212
Check error was expected for "foo.bar", but it didn't occur.
Additionally, this part seems to be missing in the Chinese version of the documentation.

Good Catch! 👍 The right code should be as follows:
import regex

schema DataMap:
    [attr: str]: str
    check:
        regex.match(attr, r'^[-_a-zA-Z0-9]+$')

data = DataMap {
    key1 = "value1"
    "foo.bar" = "value2"  # check error
}


Consider allowing us to modify the suffix convention for the Numeric Id scrubbing

https://github.com/VerifyTests/Verify/blob/87f359db743d50b53682c1b945c78c6d0e52c8a3/src/Verify/Serialization/CustomContractResolver.cs#L165
We still have some legacy stuff which is using XyzID and that causes problems. If we could configure the convention, perhaps a Func<string, bool> (where string input is the property name) property on the settings we could override, that'd be great.

hows this https://github.com/VerifyTests/Verify/pull/433/files?

That's awesome, thanks Simon. Should've realised it'd be on a MemberInfo :P
If I can reproduce the issue with the id incrementing this will work very well.

this is deployed (pending nuget updating its cache)


its not working on newer version of leetcode

Please review previous closed issues before filling out a new one! Duplicate issues will be closed without comment.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

when ever i try to submit my code on leet code of new verson its not push to git hub , but its working on older ui of leetcode

I am also facing the same issue!!

I found this and it works on new version: chrome-extension://mhanfgfagplhgemhjfeolkkdidbakocm/welcome.html


Doc updates bad param and explicitly remove 1.x - fixes #731

This PR updates the documentation to fix two issues reported by @bollinenisravan

The quickstart listed -v as an option on the create-domain script in domain-in-image, but it is not a valid option in that script.

If you do not remove the 1.x CRD, create domain will fail with a version incompatibility error:

Error from server (BadRequest): error when creating "/scratch/output/uidomain/weblogic-domains/uidomain/domain.yaml": the API version in the data (weblogic.oracle/v2) does not match the expected API version (weblogic.oracle/v1)

Just as a point of learning, we have tests for upgrading the v1 / v1.1 CRD to v2.0, but the test doesn't include having existing v1 Domains.  This appears to make a difference.  Since we weren't going to be backward compatible with v1 / v1.1, we didn't include 1.0 as a valid storage format and since there were existing Domain resources then the CRD update fails.


Document the recommended training period

How long should we spend training each location?
30 seconds? 5 minutes? Etc.?
Can we expect accuracy to go up as we spend more time?

I think 5 minutes - but yeah the accuracy should go up a little bit if you do spend more time. There are WiFi fluctuations that can be pretty rampant.


wip/ji/conn-dialog

Eh it's hard to respond to general comment on github /rant

IMO we should refactor File->Options dialog now, because it may confuse user (especially the option "Enable network server"). It should say something like "Enable API server", but feel free to pick a better name for this.

As far as I understand if we move to our new server architecture we will want to "fix" the previous network API and protobuf.

I'm not sure where lies the problem and is it only Windows specific problem, but when I try to start the server and it fails for whatever reason I can't see full process output if it crashes (including the most interesting part - stacktrace of exception that caused process to crash).


No raspi_config service in Arch ARM

Thanks a lot for PiShrink.
Nevertheless, the "expand' function does not work in my distro on the first boot (Arch ARM) because raspi_config app does not exist ?
Are you planning to update your script to take this into consideration and making your script multi-distro ?
Thanks

It no longer uses raspi_config so you should be set


"Hangu", "Buhalnița", "Chirițeni", "Grozăvești" and "Ruginești" are listed in the drop-down menu

Description:
"Hangu", "Buhalnița", "Chirițeni", "Grozăvești" and "Ruginești" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Hangu" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Hangu, NEAMȚ (Hangu)" and "Comuna Hangu, NEAMȚ".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Buhalnița" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Buhalnița, NEAMȚ (Hangu)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Type "Chirițeni" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Chirițeni, NEAMȚ (Hangu)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Type "Grozăvești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Grozăvești, NEAMȚ (Hangu)".

Step 8
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 9
Type "Ruginești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Ruginești, NEAMȚ (Hangu)".


First of several submits for buildah manpages

This creates the directory, the Makefile and the first manpage for buildah.  I wanted to get the first one in place to make sure I was doing the right formatting and to make sure I wouldn't break a build/test process somewhere.

Overall this looks good, I am happy you did it in Markdown, I think we should have links to the man pages from the README.md so that going to the github page can take you to describe how the subcommands work.
Only concern, I have is that I believe we are still working on the CLI so changes to Manpages are going to happen until we settle the CLI.

Tom Please review my other pull requests for CLI, I think we need to get together with @nalind tomorrow and continue talking about how a user would use this tool

Thanks Dan.  I think I've reviewed all the other related commits.  Ok to merge this in now gents?  I anticipate needing to go back and touch up this particular .md as things evolve, I just want to get structure set up if that's ok.


Deploy to now.sh

If it's doable, it would probably we worth it ($) to port this to a serverless architecture with a hosted mongo instance.
now.sh is a good choice for stability, performance, and price.

Stein already had a hosted version available at https://steinhq.com, with the server sponsored by our friends at DigitalOcean. Is there a use case of yours it does not suffice for?

From: sg<EMAIL_ADDRESS>Sent: Friday, August 30, 2019 5:40:10 AM
To: SteinHQ/Stein<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [SteinHQ/Stein] Deploy to now.sh (#7)
If it's doable, it would probably we worth it ($) to port this to a serverless architecture with a hosted mongo instance.
now.sh is a good choice for stability, performance, and price.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/SteinHQ/Stein/issues/7?email_source=notifications&email_token=AEW4RMRM7LOVFVB2KMZRGU3QHBQOFA5CNFSM4ISH5FY2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HIKP2UQ, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEW4RMQLS5GMKLA5JLHFYTTQHBQOFANCNFSM4ISH5FYQ.


[Question]: run with local models

Is your feature request related to a problem? Please describe.
I want to run my models locally, rather than online.
Describe the solution you'd like
No response
Additional context
No response

Hi @qiling1345, thanks for your support.
Currently, MInference supports loading local models. You can use it as follows. Please note that the model_name parameter should correspond to the appropriate Hugging Face model name instead of the local path.
local_path = "xxx"
model = AutoModelForCausalLM.from_pretrained(local_path)

# Need to use the actual model name in the HF repo
model_name = "Qwen/Qwen2-7B-Instruct"
minference_patch = MInference("minference", model_name)
model = minference_patch(model)

thank you！

你好@qiling1345， 感谢您的支持。
目前MInference支持加载本地模型，你可以按照如下方式使用，注意参数model_name要对应到合适的Hugging Face模型名，而不是本地路径。
local_path = "xxx"
model = AutoModelForCausalLM.from_pretrained(local_path)

# Need to use the actual model name in the HF repo
model_name = "Qwen/Qwen2-7B-Instruct"
minference_patch = MInference("minference", model_name)
model = minference_patch(model)

Will you support CodeQwen1.5-7b-base or [DeepSeekCoder6.7b-base]

你好@qiling1345， 感谢您的支持。
目前MInference支持加载本地模型，你可以按照如下方式使用，注意参数model_name要对应到合适的Hugging Face模型名，而不是本地路径。
local_path = "xxx"
model = AutoModelForCausalLM.from_pretrained(local_path)

# Need to use the actual model name in the HF repo
model_name = "Qwen/Qwen2-7B-Instruct"
minference_patch = MInference("minference", model_name)
model = minference_patch(model)

Will you support CodeQwen1.5-7b-base or [DeepSeekCoder6.7b-base]

Hi @luo647, thanks for your suggestion. We'll try to support DeepSeek v2 in the next version.


find suitable pitch recognition library

2 points

@salvadb23 found a Javascript library for measuring sound amplitude. We can match the user's voice over the song's amplitude to determine if they are equal. Watch the video here: https://youtu.be/2O3nm0Nvbi4


Fix CI failures

As of version 20210510.0 of GH actions Ubuntu 20.04 image GCC 11 was added. Parts of the GCC 11 library used by clang (not sure how) make Yosys build fail. This PR solves that by uninstalling GCC 11 prior to Yosys compilation.

The problem is that gcc-11 is already in the ubuntu-latest image provided by GH actions. At some point it was added there as indicated by the update to the relevant readme: https://github.com/actions/virtual-environments/commit/f20496e05dd68a662c8b4b169fe68f29b3afd77d#diff-6be9f9ce03ba57ca01e4ae937d5c2bb04893520fdf391ea87eb46acbc43ecdc5R17
The problem may be solved by changing the environment in the yaml but I don't know how to and whether it is possible to use a specific version of it.

Right, I think though that you can still set the default gcc to use for compilation, and use gcc-9. E.g.:
export CC=gcc-9
export CXX=g++-9

I can just switch to use GCC for Yosys build. That would use the default GCC 9. I tested that and with it everything builds correctly. If you agree to that solution I can just do that.
Now it's built by clang (by default). And the problem is clang. When you run it inside the CI with -v it reports:
clang version 10.0.0-4ubuntu1
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/10
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/11
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/9
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/10
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/11
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/9
Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/11
Candidate multilib: .;@m64
Selected multilib: .;@m64

And IMO the problem is Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/11. I'm not sure why and how clang uses pieces of the GCC library. The only solution I found is to not have GCC 11 or more precisely libgcc-11.

All right, I think that we might run the test using the same compiler used when building the conda packages, at least we have consistency between the two.
Unsure which is the best option at this point, but, given that, given that we may not easily control what gcc version is used in Clang, removing gcc-11 might still be valid.

@acomodi Hmm, I can see that conda packages are built using GCC (apparently a "conda" version of it) on Linux: https://github.com/hdl/conda-eda/blob/321475f1486f19b66f416f34ff288ab97c211124/syn/yosys/makefile-conda-config.patch#L10
So maybe we should switch to GCC (v9) here too ?

I think moving to GCC (v9) is cleaner than removing clang-11.

Ok, I'll do that


Responsive theme does not work

But using the responsive template doesn't generate any html files, just a bunch of folders with css and js files.
Originally posted by @ADmad in https://github.com/phpDocumentor/phpDocumentor2/issues/2114#issuecomment-524851700

As you mentioned here I did have php-xsl missing. A warning about the missing extension would have been nice.
But even after installing the required extension still don't get any html files. There are numbers errors like this:
[2019-08-27 00:30:57] php.WARNING: Warning: XSLTProcessor::transformToUri(): No stylesheet associated to this object {"exception":"[object] (ErrorException(code: 0): Warning: XSLTProcessor::transformToUri(): No stylesheet associated to this object at phar:///srv/sites/cake-apps/cakephp/phpDocumentor.phar/src/phpDocumentor/Transformer/Writer/Xsl.php:291)"} []

The warning should be in. I will check why you didn't get it.
It looks like the phar is failing to write or fetch a file. but that needs more time from my side. I will have a look. And report when I got something.
Thanks again for creating an issue.

We decided to drop support for xsl templates. Because they are hard to maintain. And we need to reduce the amount of maintenance time.
So closing this issue.


Add TUD Nanobiology programme

Add the TU Delft Nanobiology programme to helpers/programmes_helper.py.
Its id should be tud-nb.

'tud-nb': Programme(         'tud-nb',         'Nanobiology,         'TU Delft',         '<:TUD:555817896203255824>',         500     )
Does <:TUD:555817896203255824>  and 500 need to change ?

'tud-nb': Programme( 'tud-nb', 'Nanobiology, 'TU Delft', '<:TUD:555817896203255824>', 500 )
Does <:TUD:555817896203255824> and 500 need to change ?

Yes, the number of places has to be changed to the correct value. Would you like to work on this issue?

@WrightKD Yes, the number of places has to be changed to the correct value. Would you like to work on this issue?

@martinmladenov Yes. I'll make a change

Please see the PR #15


Fix firewall rule building which caused rule_exists to not match

When build_firewall_rule was running it was including double quotes around the comment, i.e.:
firewall_rule << "-m comment --comment "#{new_resource.description}" "
INPUT -i lo -p tcp -m tcp -m comment --comment "open_loopback" -j ACCEPT
However the iptables-save commands strip double quotes if there is no whitespace as:
INPUT -i lo -p tcp -m tcp -m comment --comment open_loopback -j ACCEPT
This causes rule_exists? to not match and duplicate entries were made on every chef run. This patch corrects that by detecting if the comment contains whitespace and adds double quotes otherwise leaving them out.

Hello,
What OS/iptables-save version are you testing this on?
I'm on RHEL6.6, and it always adds quotes:
$ sudo iptables-save
Generated by iptables-save v1.4.7 on Tue May 19 10:16:33 2015
...
-A OUTPUT -p tcp -m tcp -m multiport --dports 25 -m comment --comment "smtp-out" -j ACCEPT
-A OUTPUT -p tcp -m tcp -m multiport --dports 25 -m comment --comment "test" -j ACCEPT
I'm guessing this is a OS dependent thing you could do the same as the firewalld version, which matches on optional quotes, if they are there or not, it will match them.
https://github.com/opscode-cookbooks/firewall/blob/master/libraries/provider_firewall_rule_firewalld.rb#L180
Kind Regards

It appears that in Ubuntu with iptables, comments without a space are stripped of quotes, and it also doesn't normalize the CIDR (e.g. <IP_ADDRESS> does not get /32 appended).
I did another release with the fix in https://github.com/opscode-cookbooks/firewall/commit/1a5a3526f33b8354780d7025e91b75973b0bb5c4.


Unsolved identifier 'YPFilterDescriptor'

Hi, I am new to swift and working on a instagram app. I want to integrate your filter function to the app.
I follow your instructions and it tells me "use unsolved identifier 'YPFilterDescriptor'.
I try:

check my pod version and update to the latest
import YPFilterDescriptor

Still doesn't work. Could you tell me how to solve this issue? Thanks for your help

@JKCai Glad you chose YPImagePicker for your instagram-like app, this should be a perfect fit 👌
Could you tell us a little bit more info about your environment please ?
Environment (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Xcode Version [e.g. 9.4.1]
Swift Version [e.g. 4.1]
Version of YPImage picker used? (your Podfile)

Thanks!

@s4cha Thanks for the reply!
My environments are:
Device:  iPhone7 plus
OS:         IOS11.4.1
Xcode Version 9.4.1
Swift Version 4.1
Version of YPImage picker used?  - I am not sure of this one. In my pod file, I just type "pod 'YPImagePicker' ", I did not specify the version. Should I add a version at the end? like "pod 'YPImagePicker', ~3.4.1 "?

For anyone looking, the new class name is YPFilter

@nderkach Thanks for chiming in!
Indeed the name has been renamed to YPFilter, you can find a example of custom filters here https://github.com/Yummypets/YPImagePicker/issues/282
Hope this helps :)

@JKCai I personally think it's a good idea to "fix" a library to a set version (latest is 3.5.3). This prevents changes from happening every time you call pod update 💥

Closing for lack of activity. Feel free to reopen if needed :)


Improve osd description with configless mode

Mention slurm configless mode in architecture and operations.
fix #28

👍


Currently You dont know if a host is active

Hosts can be registered via the api but if you lose connection to the host you cannot tell via the ui. I think we should address this.

FIxed with new ui

I'm going to reopen this issue.  I think there are situations where the state is not reflected properly.  This is a short coming in the backend.  Needs more investigation.  This must be tested with admin and user account.

Also nothing changed in the UI to fix this, it's always (supposed to have) been showing a combination of the host and the agent's state.

I don't know if you see agents correctly.


nanovg and monomer can build on darwins

I think haskell packages nanovg and monomer were marked with badPlatforms with darwin were due to mesa cannot build on darwin. https://github.com/NixOS/nixpkgs/pull/272166 fix mesa build on darwin. I tested build a monomer app on aarch64-darwin, the app renders correctly afaict
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This is an autogenerated file. Please locate the lines corresponding to those packages in the hackage2nix-configuration/main.yaml file next to it and adapt them accordingly. Then run maintainers/scripts/haskell/regenerate-hackage-packages.sh.

Both files still seem a bit inconsistent.
Please also follow the contributing guide lines and squash everything into one commit.

Both files still seem a bit inconsistent. Please also follow the contributing guide lines and squash everything into one commit.

Sorry about that. there are some  webkitgtk changes. I am not sure about them. I think this is ready for another look. thank you for your time

Mark this PR a draft.
Rebase your commit onto haskell-updates and force push.
Change the base of this pr to haskell-updates
Unmark draft.

Then maybe rerun the script and hopefully the webkit changes disappear.

Oh, damn. I should have said cherry-pick your commit on top of haskell-updates, not rebase it.

should i just open a PR to haskell-update branch ?

should i just open a PR to haskell-update branch ?

In theory this PR is still salvagable, but you can also just open a new one.


[Improvement-#9680][task-plugin] add hive sql log listener, print MapReduce progress log and obtain application_id allows developers to better track tasks

Purpose of the pull request

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

@EricGao888 plz close this pull request.

@EricGao888 plz close this pull request.

May I ask why you want to close this pull request? BTW, why did u close #11562 and opened a new one? You could directly update the PR.

@EricGao888 There is a code conflict. The conflict is completely different from my previous code

@EricGao888 hi bro,I have submitted the code, can you help me look at it。

@EricGao888 There is a code conflict. The conflict is completely different from my previous code

FYI you could resolve the conflicts by rebasing your code, see: https://github.com/sevntu-checkstyle/sevntu.checkstyle/wiki/Development-workflow-with-Git:-Fork,-Branching,-Commits,-and-Pull-Request


Unable to get local issuer certificate

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.27.1
Regression From
It was at some point, but I don't know which one.  Haven't used it in awhile
Architecture
i86
Storage Explorer Build Number
20221220.2
Platform
Windows
OS Version
Windows 10
Bug Description
I get a message that says "Could not access resources for this tenant.  You may need to re-authenticate".  I tried re-authenticating but get the same message.
Error Details:
"message": ""{\n  \"name\": \"Error\",\n  \"message\": \"unable to get local issuer certificate\",\n  \"stack\": \"Error: unable to get local issuer certificate\\n    at TLSSocket.onConnectSecure (node:_tls_wrap:1532:34)\\n    at TLSSocket.emit (node:events:527:28)\\n    at TLSSocket._finishInit (node:_tls_wrap:946:8)\\n    at ssl.onhandshakedone (node:_tls_wrap:727:12)\",\n  \"code\": \"UNABLE_TO_GET_ISSUER_CERT_LOCALLY\"\n}""
}
About screen:

Steps to Reproduce

Launch the application
click on my account

Actual Experience

Expected Experience
Get logged in and see my Storage Accounts
Additional Context
I have another user in my company that is getting the same error.  Are there any specific certficates we need to put on our machines?

Hi @markpisc please consider enabling system proxy: https://learn.microsoft.com/en-us/azure/storage/common/storage-explorer-network#use-system-proxy-preview

Thank you very much!!  That fixed it.
Mark Collins
Sr. IT Application Software Developer
Daikin Applied
Preferred method of contact, in order:
Microsoft Teams
612.581.7433 (cell)
763.553.5307 (office)
<EMAIL_ADDRESS>| www.daikinapplied.comhttp://www.daikinapplied.com
From: Matthew Rayermann @.>
Sent: Wednesday, December 28, 2022 11:34 AM
To: microsoft/AzureStorageExplorer @.>
Cc: Collins, Mark W. @.>; Mention @.>
Subject: Re: [microsoft/AzureStorageExplorer] Unable to get local issuer certificate (Issue #6389)
Hi @markpischttps://github.com/markpisc please consider enabling system proxy: https://learn.microsoft.com/en-us/azure/storage/common/storage-explorer-network#use-system-proxy-preview
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/AzureStorageExplorer/issues/6389#issuecomment-1366813269, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALWDWDCS5J532TQGZNGS6V3WPR2XJANCNFSM6AAAAAATHDKHSQ.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Issue about the generated occupancy map.

Hey! Thanks for your awesome work here!
I have a question as below:
When I visualize the agent_view and corresponding RGB (from obs) in model. Semantic_Mapping.forward, I found that the generated occupancy map is opposite to the occupancy of the actual scene in RGB. For example, in the figure below, the generated object A in the generated map is on the right side of the agent, while in the real RGB it is on the left. Several other major objects can also be seen from the red two-way arrows.

At first, I thought that after applying the rotated and translated operation behind, this situation would disappear. But when I continue to visualize translated, it seems that this situation still exists (shown as below). Can you explain why this is? Thanks!

hello, may I ask that, can you get an occupancy map which has the same shape as ground-truth? I mean, besides the problem you mentioned, does semantic mapping module work well?

You just need to flip the visualization vertically. The mapping code logic is correct.


add service account heapster

kubernetes does not set the heapster serviceaccount as a default serviceaccount,so i think we should add this serviceaccount

This change is

I signed it!

Hmm... I though this was already created.
cc @luxas

https://github.com/master/heapster/blob/master/deploy/kube-config/influxdb/heapster.yaml

oh,i did not use this file.thanks.i closed this pull request


Element type is not valid.

I got this error
http://i.imgur.com/MhK0FT1.png

Fixed the react-router": "4.0.0-alpha.6",. This resolved the issue.

Updated react router from v4.0.0-aplha.6 to v4.1.1 (now using react-router-dom instead of react-router)


@710leo   您好，请问一下/opt/go/src/github.com/unrolled/render (from $GOPATH) sender/ring.go:4:2: cannot find package "stathat.com/c/consistent" in any of: 	/usr/local/go/src/pkg/stathat.com/c/consistent (from $GOROOT) 	/opt/go/src/stathat.com/c/consistent (from $GOPATH) 这个是什么错误啊，谢谢

@kobe1996  https://www.google.com.hk/search?q=cannot+find+package


Make as_fillable_container() and as_fill_item() not mutate their inputs

This is a follow-up to https://github.com/posit-dev/py-shiny/pull/861#discussion_r1418189057. Also closes #577.
This PR makes it so that as_fillable_container() and as_fill_item() do not modify their inputs.

@schloerke On a related note, I was looking at the functions tag_prepend_class(), tag_remove_class() tag_add_style() because they also mutate their input objects. Then I realized that those functions now exist as methods on the Tag class in htmltools. The methods mutate the object and return the object, but that feels more OK than outside functions that mutate the input and return it.
Is there any reason not to switch to those methods from htmltools? That would remove the need for those functions, and also make the code feel less weird.

@wch I was looking into switching to the .add_class() method for appending the fillability classes. I was coming at this from the perspective of not putting utility classes first in the markup. I started working on making that change earlier today, but if it makes sense to roll that into this PR, I think that'd be a good change.

I've removed the tag_ functions in favor of the Tag methods, and also made the fill classes come at the end.


Graph abstractions

Prepona was a huge inspiration in separating the graph abstraction from graph data storage. The question is how should we approach that to benefit from this separation to its fullest, but keeping the usage and API as convenient as possible.
Kind of obvious cases are having simple graph and multigraph. Somewhat orthogonally allowing and disallowing self-loops. Should we have four structs (LoopFreeSimpleGraph, SimpleGraph, LoopFreeMultiGraph, MultiGraph or is there a different, more flexible approach to tackle this (a marker type, constructor argument)?
Another level would be having graph types that would guarantee some certain property, like BipartiteGraph, TreeGraph, ConnectedGraph. This information may be exploited by using a simpler and faster algorithm that works only on certain classes of graph. There would be possibly some kind of indirection through traits (Bipartite, Tree, ...), which would be required by the algorithms, so that different implementations of the same property can be used.
There may be also tricks like starting with a sparse-friendly storage and switching to a dense one once the edge/vertex ratio exceeds a threshold.
Any other ideas?

The loop question might be approached with a marker type and a "property" trait. Similarly to EdgeType marker type, there could be a Loops marker type (with WithLoops, WithoutLoops) and there would be such an impl:
impl<...> LoopFree for SimpleGraph<..., WithoutLoops> {}

Or consts generics could be used having const Loops: bool and using SimpleGraph<..., false>.
Generally, there could be simply a set of property traits:

LoopFree
Bipartite, Tree, ...
Finite (see #3 )
...

(The naming in this comment is completely ad hoc)

Progress has been made in 4ae82fafac4ef34387b30cbd56f26adbdc4acebc and 42616e453773f59bdbe7fed8ac0b7fb175bcf48d.
The Guarantee trait is supposed to contain all interesting properties a graph can have (it is expected to grow throughout time). The properties must be such that it is always safe (in a sense of algorithms correctness) to return false as a default. In other words, if a property returns false, that should not break any algorithm. Essentially, a property is an additional guarantee over a general graph.


MMIs and positronic brains now talk like pAIs in plushies

About the PR

Title.
Why / Balance

Lot of people in the discord really wanted the feature! It makes sense as well, pAIs are basically the same as MMIs and brains.
Technical details

Just added the necessary component so their name will get overwritten.
Media

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Changelog

:cl: Beck Thompson

add: When MMIs and positronic brains are inserted into plushies, their names will be updated to the plushies name (Exactly the same way pAIs do).

Good idea. Could you rephrase the changelog a little so it is more clear for players who don't know about the voice name change?

I mean, sure, why not?
Tested in-game fine


feat: bundle and push all journeys to kibana

#470
Adds the subcommand push to the Synthetics CLI that would do the following

Goes over each journey file and bundles that particular journey along with relevant files that are imported by the particular journey
Creates a archived file for each journeys maintaining the local path (to help with Stack traces when invoked via HB)
creates a base 64 encoded string that would be sent to Kibana as application/octet-stream request

To run locally

Install the deps and build the files by npm run build

npx @elastic/synthetics push .examples/todos...

TODO

[ ] Define monitor DSL that would let users override the id, schedule, location, etc. which would be sent along with the request
[ ] Add kibana.id and kibana.auth options and send the request to Kibana endpoint along with monitor information.

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-03-31T22:30:03.042+0000

Duration: 14 min 1 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
149

Skipped
2

Total
151

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

Notes from latest Refinement

Purse the monitor.use API for the DSL

We are fine with running the journey in --dry-run mode, It would gives us an idea in understanding the step names and a cleaner API for declarative syntax.
We discussed the other option that would gives us the opportunity to figure out defaults without running Journeys, but decided against it.

journey(
  { name: 'check if title is present', schedule: '@every1m' }, // First proposal
  ({ page, params, monitor }) => {
    monitor.use({.      // Second proposal
      id: 'blah',
      schedule: '@every1m',
    });
    step('launch app', async () => {
      await page.goto(params.url);
    });
  }
);

Using Kibana auth for pushing monitors

Have a meeting scheduled with the Kibana Security team to understand the scope of work required to make the API tokens work, But worse case we would go with the User credentials.

I have changed the way monitor.use API defined here and went exposing monitor object through the package as it offered better DX, extensibility and customization capabilities. Added more details on the PR - #493

npx @elastic/synthetics

@lucasfcosta I will make the monitor read-only in a separate PR.


Can't specify sql dialect when creating comparisons without settings

What happens?
If you are trying to create a Comparison using dictionary levels without having a Settings object, then such ComparisonLevels will not have an associated _sql_dialect, which causes problems for instance in as_dict(), when trying to generate an output_column_name. We cannot remedy this currently by including the sql dialect in the dictionary at any point.
Encountered during the course of #1117 in creating null/exact levels using InputColumn.
To Reproduce
from splink.input_column import InputColumn
import splink.spark.spark_comparison_level_library as cll
from splink.comparison import Comparison

lat_col = "ll"
lat = InputColumn(lat_col, sql_dialect="spark")

lat_l, lat_r = lat.names_l_r()

null_level = {
    "sql_condition": f"{lat_l} IS NULL OR {lat_r} IS NULL",
    "label_for_charts": "Null",
    "is_null_level": True,
}

comp = {
    # no output_column_name (which is allowed), so it needs to be auto-generated
    'comparison_description': 'LL exact vs else',
    'comparison_levels': [
        null_level,
        cll.exact_match_level("ll"),
        cll.else_level()
    ],
}

cc = Comparison(comp)
# error here when trying to generate output_column_name due to incorrect sql parsing
print(cc.as_dict())

leads to an error Invalid expression / Unexpected token. parsing the line  `ll_l` IS NULL OR `ll_r` IS NULL as the fact that we are using the spark dialect does not get propagated to sqlglot.parse_one.
This can manifest also when creating a linker during deepcopying the settings - see also #1019.
Noteworthy that this does not cause an error using older environments with e.g. sqlglot==5.1.0
OS:
macOS
Splink version:
3.7.0.dev1
Have you tried this on the latest master branch?

[X] I agree

Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?

[X] I agree

May be relevant: https://github.com/moj-analytical-services/splink/issues/1055


Add backoff for GC attempts on backups

A user reported that they were hitting AWS API limits as a result of Ark continually trying to GC a backup for which one of the snapshots had already been manually deleted.
I think what's happening here is:

GC controller is regularly re-syncing, i.e. re-adding all backups to queue
if an item in the queue has expired, GC controller creates a DeleteBackupRequest for it
since the creation of the DBR succeeds, the backup is not re-added back to the GC queue
GC controller re-syncs and adds it back to the queue
etc.

We should be backing off on re-issuing DeleteBackupRequests for backups if prior DBRs have not successfully deleted the backup.
Separately (already being tracked elsewhere) we shouldn't fail a DBR if one of the snapshots has already been deleted.

Sounds like a good idea. We should maybe also consider removing the backup informer event handler in the gc controller. That allows us to immediately check if a backup is deleted whenever the backup is added or updated. I'm not sure that's particularly valuable, especially given we have the periodic resync that checks all backups.
FYI the default rate limiter we're using is the max of:

a per-item exponential backoff that starts at 5ms and caps at 1000s
an overall token bucket for the entire queue, that fills 10 tokens/second up to a capacity of 100

This means that for unique backups, we'd be able to sustain processing 10 per second (and it could burst up to 100 at a time, if the bucket is full of tokens). For an individual, specific backup, it would wait 5ms, then 10ms, 20ms, 40ms, 80ms, ... up to 1000s.

We discussed this and don't believe it's an issue since the conversion to DeleteBackupRequests. Please let us know if anyone is having problems and we can revisit.


dash shell is broken

Windows Build Number
10.0.19042.867
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
Linux version 5.4.72-microsoft-standard-WSL2 (oe-user@oe-host) (gcc version 8.2.0 (GCC))
Distro Version
Ubuntu 20.04.2 LTS
Other Software
No response
Repro Steps

run chsh -s /bin/sh (/bin/sh points to dash on my system)
open new Windows Terminal tab and obtain -sh: 6: export: Files/PowerShell/7:/mnt/c/tools/ruby30/bin:/mnt/c/Python39/Scripts/:/mnt/c/Python39/:/mnt/c/WINDOWS/system32:/mnt/c/WINDOWS:/mnt/c/WINDOWS/System32/Wbem:/mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/:/mnt/c/WINDOWS/System32/OpenSSH/:/mnt/c/Program: bad variable name error

Expected Behavior
No error expected.
Actual Behavior
-sh: 6: export: Files/PowerShell/7:/mnt/c/tools/ruby30/bin:/mnt/c/Python39/Scripts/:/mnt/c/Python39/:/mnt/c/WINDOWS/system32:/mnt/c/WINDOWS:/mnt/c/WINDOWS/System32/Wbem:/mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/:/mnt/c/WINDOWS/System32/OpenSSH/:/mnt/c/Program: bad variable name error is reported every time I log in.
Diagnostic Logs
No response

It can be fixed with replacing 6-th line in /etc/profile.d/apps-bin-path.sh with export PATH="$PATH:${snap_bin_path}"

That is the correct fix. Looks like that file is part of the snapd package. The launchpad page is here.

I've reported this issue here.