Error on dependency installation

Hello,
I use aws data wrangler in my emr clusters, today I started to have some bootstrap problems with data wrangler, could you help me?
Collecting awswrangler
  Downloading https://files.pythonhosted.org/packages/28/57/debf8f714d5b1a14ce39a6e8bbd1105beaab8490f96c2673fe04bf27cedb/awswrangler-2.4.0-py3-none-any.whl (171kB)
Requirement already satisfied: pandas<1.3.0,>=1.1.0 in /usr/local/lib64/python3.7/site-packages (from awswrangler)
Requirement already satisfied: boto3<2.0.0,>=1.12.49 in /usr/local/lib/python3.7/site-packages (from awswrangler)
Collecting pyarrow<3.1.0,>=2.0.0 (from awswrangler)
  Downloading https://files.pythonhosted.org/packages/62/d3/a482d8a4039bf931ed6388308f0cc0541d0cab46f0bbff7c897a74f1c576/pyarrow-3.0.0.tar.gz (682kB)
    Complete output from command python setup.py egg_info:
    /usr/lib64/python3.7/distutils/dist.py:274: UserWarning: Unknown distribution option: 'long_description_content_type'
      warnings.warn(msg)
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/mnt/tmp/pip-build-00riuili/pyarrow/setup.py", line 624, in <module>
        url='https://arrow.apache.org/'
      File "/usr/lib/python3.7/site-packages/setuptools/__init__.py", line 129, in setup
        return distutils.core.setup(**attrs)
      File "/usr/lib64/python3.7/distutils/core.py", line 108, in setup
        _setup_distribution = dist = klass(attrs)
      File "/usr/lib/python3.7/site-packages/setuptools/dist.py", line 333, in __init__
        _Distribution.__init__(self, attrs)
      File "/usr/lib64/python3.7/distutils/dist.py", line 292, in __init__
        self.finalize_options()
      File "/usr/lib/python3.7/site-packages/setuptools/dist.py", line 476, in finalize_options
        ep.load()(self, ep.name, value)
      File "/mnt/tmp/pip-build-00riuili/pyarrow/.eggs/setuptools_scm-5.0.1-py3.7.egg/setuptools_scm/integration.py", line 26, in version_keyword
        dist.metadata.version = _get_version(config)
      File "/mnt/tmp/pip-build-00riuili/pyarrow/.eggs/setuptools_scm-5.0.1-py3.7.egg/setuptools_scm/__init__.py", line 173, in _get_version
        parsed_version = _do_parse(config)
      File "/mnt/tmp/pip-build-00riuili/pyarrow/.eggs/setuptools_scm-5.0.1-py3.7.egg/setuptools_scm/__init__.py", line 119, in _do_parse
        parse_result = _call_entrypoint_fn(config.absolute_root, config, config.parse)
      File "/mnt/tmp/pip-build-00riuili/pyarrow/.eggs/setuptools_scm-5.0.1-py3.7.egg/setuptools_scm/__init__.py", line 54, in _call_entrypoint_fn
        return fn(root)
      File "/mnt/tmp/pip-build-00riuili/pyarrow/setup.py", line 542, in parse_git
        return parse(root, **kwargs)
      File "/mnt/tmp/pip-build-00riuili/pyarrow/.eggs/setuptools_scm-5.0.1-py3.7.egg/setuptools_scm/git.py", line 95, in parse
        require_command("git")
      File "/mnt/tmp/pip-build-00riuili/pyarrow/.eggs/setuptools_scm-5.0.1-py3.7.egg/setuptools_scm/utils.py", line 151, in require_command
        raise EnvironmentError("%r was not found" % name)
    OSError: 'git' was not found

    ----------------------------------------

Hi @rubenssoto, where are you trying to install?
FYI
For platforms without PyArrow 3 support (e.g. EMR):
pip install pyarrow==2 awswrangler
Or specifically for Glue PySpark Job:

Key: --additional-python-modules
Value: pyarrow==2,awswrangler

We've updated our EMR install instructions on the docs.
Also, consider to freeze the Wrangler version in the bootstrap for productive environments (e.g. awswrangler==2.4.0)


Update flame_audio readme

What could be improved
The readme for flame_audio should have some introduction and some examples since it will show up on pub.dev.
Why should this be improved
To make it easier for users to get started.
Any risks?
No
More information
Current readme: https://github.com/flame-engine/flame/blob/main/packages/flame_audio/README.md

Yo @spydon
I can write the docs and provide the example codes for this. I will open a PR within a few weeks.

Yo @spydon
I can write the docs and provide the example codes for this. I will open a PR within a few weeks.

Great! I'll assign you to the issue.

opened new PR https://github.com/flame-engine/flame/pull/3119 for this issue


New Test ODS-2223

Add New Test ODS-2223:
Verify permissions set as part of Project Sharing do not override Dashboard permission.

Including:

New Keyword: Set RHODS Users Group To rhods-users
New Keyword: Assign Permissions To User in Project
New Keyword: Verify No Permissions For User
'Reload Page If Project Is/Not Listed' Keyword with WHILE and Timeout
Fix 'Create Group' KW to apply new group only if it doesn't exist
Fix 'Delete Group' KW to delete the group only if it already exists
Add Resource ODS.robot to Permissions.resource and set Groups Variables
Add Users names to Suite Variables

Thanks @bdattoma , @FedeAlonso  I resolved the requested issues, and retested:

LGTM, apart for my last comment, I didn't notice earlier sorry. @manosnoam

I cannot count on the suite setup, if previous test could alter the users,
that's why I make sure the users are ready for the test.
I don't see any advantage in changing this logic if it works good, and if
we change the logic, it will require further tests and rebase. I think only
if you see an actual problem in this logic, we should fix it before merging.
On Tue, Jan 9, 2024, 10:40 bdattoma @.***> wrote:

@.**** commented on this pull request.
In
ods_ci/tests/Tests/400__ods_dashboard/415__ods_dashboard_projects/415__ods_dashboard_projects_permissions_mgmt.robot
https://github.com/red-hat-data-services/ods-ci/pull/1101#discussion_r1445781461
:

@@ -76,13 +82,31 @@ Verify User Can Assign Access Permissions To User Groups
Sleep   5s
${USER_C} Should Not Have Access To ${PRJ_USER_B_TITLE}

+Verify Project Sharing Does Not Override Dashboard Permissions

[Tags]                  Tier1                   Sanity                  ODS-2223
[Setup]                 Set RHODS Users Group To rhods-users
Launch Data Science Project Main Page    username=${OCP_ADMIN_USER.USERNAME}    password=${OCP_ADMIN_USER.PASSWORD}
...    ocp_user_auth_type=${OCP_ADMIN_USER.AUTH_TYPE}
Assign Admin Permissions To User ${USER_B} in Project ${PRJ_USER_B_TITLE}
Assign Edit Permissions To User ${USER_C} in Project ${PRJ_USER_C_TITLE}
Remove User From Group    username=${USER_B}    group_name=rhods-users
Remove User From Group    username=${USER_B}    group_name=rhods-admins
Remove User From Group    username=${USER_C}    group_name=rhods-users
Remove User From Group    username=${USER_C}    group_name=rhods-admins
User ${USER_B} Should Not Be Allowed To Dashboard
User ${USER_C} Should Not Be Allowed To Dashboard
[Teardown]              Run Keywords            Set Default Access Groups Settings
...                     AND                     Set User Groups For Testing

I know, but the suite setup already removes users from group. Besides, I'm
suggesting to use ${USER_GROUP_1} for both admin and basic user group
because the USER_B and USER_C you're using are not part of that group.
—
Reply to this email directly, view it on GitHub
https://github.com/red-hat-data-services/ods-ci/pull/1101#discussion_r1445781461,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACLUMWLJADY4E3PUGPZ3ZGLYNT66XAVCNFSM6AAAAABBQS2C6CVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQMJQGY2DSMBXGA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Requesting Write Access

Hi,
I want  requesting to Write Access of it and contribute. Thanks

write access has been given , accept the invitation .


api: API check test should disallow API additions after an api/go1.N.txt is created (currently it does this only after a VERSION file is added)

CL 276454 promoted api/next.txt to api/go1.16.txt, and all API additions in that file were reviewed in #43407.
When we started cutting Go 1.16 RC 1, we found out (via release testing) that there was a skew between api/go1.16.txt and the actual API.
This issue is about improving the process so we notice this sooner, to avoid the possibility of incurring a delay in the RC release process.
CC @golang/release, @ianlancetaylor.

The cause appears to be that as long as the runtime.Version() contains "devel" (which it does until a VERSION file is added on a release branch, something that happens during the rc1 release and its tests), API additions are considered okay, but API removals are not.
The fix here may to be change it so that both API additions and removals are not okay after the go1.N.txt file is made for a given release in development.

The cause appears to be that as long as the runtime.Version() contains "devel" (which it does until a VERSION file is added on a release branch, something that happens during the rc1 release and its tests), API additions are considered okay, but API removals are not.
The fix here may to be change it so that both API additions and removals are not okay after the go1.N.txt file is made for a given release in development.

I have a counter-proposal: remove next.txt entirely, and make API skew fail TryBots at all times.
The current lifecycle of an API change is:

make the API change in a CL, maybe inadvertently
optionally, someone updates next.txt because the all.bash output is getting annoying

this cycle it was @rsc, other cycles next.txt went completely unused

next.txt is copied wholesale into go1.X.txt without review
an issue is opened to review go1.X.txt

This has two major shortcomings: it lets API changes happen inadvertently in the original CL, and lets skew happen after the review. The latter would be addressed by the current proposal, the former wouldn't. The current process also involves manual steps that serve no purpose AFAICT.
If we eliminate next.txt and block any skew, then the lifecycle becomes:

make an API change and add a line to go1.X.txt in the same CL, acknowledging intent to add an API
an issue is opened to review go1.X.txt

If people would prefer not getting heckled by all.bash while experimenting, we can make all.bash just output the diff with no error, and only error out on the builders, so the go1.X.txt file can be changed only once before mailing the CL.

I have a counter-proposal: remove next.txt entirely, and make API skew fail TryBots at all times.
The current lifecycle of an API change is:

make the API change in a CL, maybe inadvertently
optionally, someone updates next.txt because the all.bash output is getting annoying

this cycle it was @rsc, other cycles next.txt went completely unused

next.txt is copied wholesale into go1.X.txt without review
an issue is opened to review go1.X.txt

This has two major shortcomings: it lets API changes happen inadvertently in the original CL, and lets skew happen after the review. The latter would be addressed by the current proposal, the former wouldn't. The current process also involves manual steps that serve no purpose AFAICT.
If we eliminate next.txt and block any skew, then the lifecycle becomes:

make an API change and add a line to go1.X.txt in the same CL, acknowledging intent to add an API
an issue is opened to review go1.X.txt

If people would prefer not getting heckled by all.bash while experimenting, we can make all.bash just output the diff with no error, and only error out on the builders, so the go1.X.txt file can be changed only once before mailing the CL.

Copying @rsc's comment from https://github.com/golang/go/issues/43407#issuecomment-768772820 here:

The api check intentionally doesn't fail on master, only on release branches, to avoid forcing any CL adding API to update next.txt in the same CL (needless merge conflicts). But anyone running all.bash should see it.
We could potentially flip a bit somewhere after the mid-freeze API review to make the test start failing on additions then. But we shouldn't make it fail when the tree is open.

Copying @rsc's comment from https://github.com/golang/go/issues/43407#issuecomment-768772820 here:

The api check intentionally doesn't fail on master, only on release branches, to avoid forcing any CL adding API to update next.txt in the same CL (needless merge conflicts). But anyone running all.bash should see it.
We could potentially flip a bit somewhere after the mid-freeze API review to make the test start failing on additions then. But we shouldn't make it fail when the tree is open.

Right, I disagree that forcing something as important as adding an API to explicitly opt-in is bad.
The merge (or revert) conflicts came up before about release notes, but we switched anyway to release notes in CLs, and I didn't hear about much annoyance from it.

Right, I disagree that forcing something as important as adding an API to explicitly opt-in is bad.
The merge (or revert) conflicts came up before about release notes, but we switched anyway to release notes in CLs, and I didn't hear about much annoyance from it.

@FiloSottile After taking some time to think about it carefully, I'm in agreement with the suggestion you made. I, too, now believe there is a good chance that removing our use of next.txt and requiring an api/go1.txt to exist and be complete during the entire development cycle has favorable trade-offs. The attention paid to API review would be happen more evenly during the entire cycle, rather than more towards the end, which feels right. However it will affect all Go developers during the development cycle, and probably needs a little more discussion/feedback than what's happened in this issue so far (and we'd want to communicate it more widely to golang-dev@ to give people a heads up).
I think rather than describing it as a "counter-proposal" (which I interpret to mean we should do something incompatible/in a different direction), it's a suggestion to take two compatible steps in the same direction instead of one smaller step.
Where we currently are, API additions are reported quietly (no loud test failure):

from development tree opening all the way until RC 1

If we make the change originally suggested in https://github.com/golang/go/issues/43956#issuecomment-768578686, it becomes:

from development tree opening all the way until Beta 1

If we make the change later suggested in https://github.com/golang/go/issues/43956#issuecomment-768583420, then:

never

For now, I want to ensure we don't get a repeat of the situation that happened during the Go 1.16 cycle (what this issue was filed about), and it seems everyone's in agreement to disallow silent API additions after Beta 1. Let's do that first, since it's seemingly quick and non-controversial, and consider your suggestion afterwards. It can only apply to a future cycle anyway (too late for 1.17), so we can still consider it before the tree opens for Go 1.18 development.
I mailed CL 315350 which will fix this issue and I think we can get it in before Go 1.17 Beta 1. If that happens, let's follow up with your suggestion in a separate issue (or proposal).
One more thing: if CL 315350 is submitted, implementing your suggestion will become a matter of adding a "api/go1.n.txt" file earlier in the release cycle than Beta 1. If we find it's too disruptive and not helping as expect, we can simply remove that file, and re-add it at Beta 1 again. So it's a small diff to try it and adjust based on findings.


Recurring Events on the 5th Day Name of a Month Goes Onto Next Month if Month does not have 5 of those days

When trying to processes recurring events that meet on the 5th dayname of a month (e.g. each 5th Sunday), the event spills onto the next month.  Fixed this by adding the following code at line 526:
// Prevent 5th dayname of a month from showing up on the next month
// (if it's by month and falls outside the current month, skip the event)

$compare_current_month = date('F', $recurring_timestamp);
$compare_event_month   = date('F', strtotime($event_start_desc));

if($compare_current_month != $compare_event_month){
    $recurring_timestamp = strtotime($offset, $recurring_timestamp);
    continue;
}

Thanks for this. Fancy putting together a PR?

Thanks for the code


Add sourcediving.com to iOS Development Blogs

👋 I made a submission earlier and it was suggested that I should list our site in the directory 🙂
Since we share content for other platforms too, I've filtered the links to iOS only tags 👍

Site
Feed
Twitter

Thanks!

Whoops, thanks for fixing the missing ,!

No problem!


[BUG] manual advance causes text effect triggers to not work

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

create a sandbox object with auto advance disabled
attempt to play dialog in a scene and manual advance with ui_accept (default: enter key)
see that any in text tags get read in plain text

Expected behavior
any tags used should work in both auto and manual advance modes
Platform

OS: Mac OSX
Godot 3.2

Thanks for the bug report, I'll look into it in the future. Right now my living situation is very up in the air and I'm trying to get stable, but as soon as I have the chance, I'll start working on fixing all the bugs reported.

Fixed in 1.5.3, probably even sooner, can't recall, been a long while


Make kubevirt compatible with generic e2e tests

This transitions the KubeVirt platform to use the generic e2e tests. Once this merges I'll revise the kubevirt e2e prow configs to no longer reference the TestKubeVirtCreateCluster test. For now, TestKubeVirtCreateCluster redirects to TestCreateCluster so prow will pass.
You'll notice there's some possible "suspect" logic going on where we create a route and service within the e2e tests for the KubeVirt guest cluster. Since the guest nodes are VMs running on the hypershift infra cluster, we're treating the guest cluster as if it's a subdomain within the infra cluster's *apps dns wildcard record. The route/service is redirecting traffic on a *apps subdomain to our kubevirt VM pods. Eventually we'll get rid of this once we have the cloud-provider-kubevirt component handling proper ingress passthrough for us.
This routing logic used to be isolated to the KubeVirt test only, but now I needed to add it in a generic way that would get applied to all tests when the kubevirt platform is in use.

/test e2e-kubevirt-gcp
The kubevirt test didn't get a chance to run because kubevirt-gcp failed due to a quota issue level=error msg=Error: Error waiting for instance to create: Quota 'N2_CPUS' exceeded.  Limit: 24.0 in region us-central1.

/test e2e-kubevirt-gcp

/test e2e-kubevirt-azure

/test e2e-kubevirt-azure-ovn
/test e2e-kubevirt-gcp-ovn


Florence-2: How to add custom tokens during fine-tuning training?

This is the official way to add:
# processing_florence2.py
tokens_to_add = {'additional_special_tokens': \
    tokenizer.additional_special_tokens + \
    ['<od>', '</od>', '<ocr>', '</ocr>'] + \
    [f'<loc_{x}>' for x in range(1000)] + \
    ['<cap>', '</cap>', '<ncap>', '</ncap>','<dcap>', '</dcap>', '<grounding>', '</grounding>', '<seg>', '</seg>', '<sep>', '<region_cap>', '</region_cap>', '<region_to_desciption>', '</region_to_desciption>', '<proposal>', '</proposal>', '<poly>', '</poly>', '<and>']}

The training was added in this way, and the model was adjusted
model.resize_token_embeddings(len(processor.tokenizer))

The model's output is very good at the beginning, but the latter part looks like gibberish

Perhaps you should consider incorporating a minor modification in the get_model_tokenizer_florence function located at https://github.com/modelscope/swift/blob/main/swift/llm/utils/model.py#L2738.
new_tokens= ["YOUR CUSTOM TOKENS"]
tokenizer.add_tokens(list(new_tokens))
model.resize_token_embeddings(len(tokenizer))


TO PSQL plugin does not update SSLKeys correctly

I'm submitting a ...

bug report

Traffic Control components affected ...

Traffic Ops
Traffic Vault

Current behavior:
When tv.GetDeliveryServiceSSLKeys gets called with the PSQL backend, the actual encrypted value (tc.DeliveryServiceSSLKeys) does not get it's Version field updated appropriately. This manifests in that any DeliveryServiceSSLKeys.Version will be 1 while the corresponding table value is correct.

Expected behavior:
The DeliveryServiceSSLKeys.Version should match the version column on the sslkey table.

Minimal reproduction of the problem with instructions:
Run CiaB or manual recreation:
Might be able to skip DNSSec/URI/URL keys step:

Create CDN

Generate DNSSec Keys

Create DS

Generate SSL Keys
Generate URI Keys
Generate URL Keys

Query the TV DB (with PSQL backend), decode the value and see that the version on the table and the version on DeliveryServiceSSLKeys are not correct in the case of latest

Anything else:

From default CiaB:
SSL Keys JSON:
  {
    "cdn": "CDN-in-a-Box",
    "deliveryservice": "demo1",
    "hostname": "*.demo1.mycdn.ciab.test",
    "key": "demo1",
    "version": 1,
    "certificate": {
      "crt": "...",
      "key": "...",
      "csr": "..."
    },
    "LastUpdated": "2021-06-03T20:40:57.812723Z"
  },
  {
    "cdn": "CDN-in-a-Box",
    "deliveryservice": "demo1",
    "hostname": "*.demo1.mycdn.ciab.test",
    "key": "demo1",
    "version": 1,
    "certificate": {
      "crt": "...",
      "key": "...",
      "csr": "..."
    },
    "LastUpdated": "2021-06-03T20:40:57.812723Z"
  },

Corresponding table records:
id, data, ds, cdn, version, last_update
1,  '...',  demo1, CDN-in-a-Box, 1, 2021-06-03 20:40:57.812723
2,  '...',  demo1, CDN-in-a-Box, latest,  2021-06-03 20:40:57.812723

After talking with @mattjackson220, I realize I have misunderstood the purpose of the double key entry. Two are inserted with different versions on the record so it can be searched. I was under the impression that we were storing the most recent key, and the key before that (which should have different versions).
This is not actually an issue.


opcode || doesn't work

The following program print wrong result
c := false
println("c || !c = ", c || !c)
println("!c || c = ", !c || c)

Expected result:
c || !c =  true
!c || c =  true

Got:
c || !c =  false
!c || c =  false

duplicate of #471,  #465

hi @ldez ,  it is another problem, please take a look at the details

@ldez 471 doesn't fix this problem

The bugs are real legitimate. They concern potentially all operations that return boolean values and that can be used in branch operations.
The bug comes in fact from a wrong optimization, where the result of a boolean operation (assign, compare, etc...) is not stored for future test, but used directly for branching. Unfortunately, that doesn't work with current impelementation of logical or / and operations, which rely explicitely on a stored result to decide.
I fixed the problem for #471 for isNil() and isNotNil() in #473, but I realize that I have to generalize the fix to all boolean operations.
I propose to reopen #471 for that and close other bugs in favor of it. What do you think ?


enhancement request: arrow tool direction. stamp size and background

@pubpub-zz amazing. it is exactly what I need. Just 2 comment to add here.

the arrow tool. I am not sure if it is due to my experience with other annotation tool that the arrow usually start with the tail and end with the arrow head. it seems more logical to me when using arrow to point to something.
the number stamp. it would be nice if it comes with a background color to reduce the distraction from the background. it would be even better if there is a option to change the size of the stamp. Perhaps making it smaller.

If you hit twice the arrow tool, you will change the way the arrow is set. I've selected this way first, as it was more natural to select what you want to indicate. I will try when I will have a little of time an option to select which direction to apply first
I've choosed the easiest option about colors. I will make a proposal in the same idea using multiple depress to get different fillings.

PS : Can you mark as solved the original issue you've raised. It may help people to find my fork.

Absolutely. I didn't aware that the button can be clicked further to change the behavior. Well done.
Another nice to have improvement would be allowing eraser to select an area to remove stroke (select multiple remove). It is particularly useful when the pen stroke is very small.

Hi HungrySnake, can you close also the issue on Geoven's Gink?

done.
On Sun, Aug 16, 2020 at 3:12 PM pubpub-zz<EMAIL_ADDRESS>wrote:

Hi HungrySnake, can you close also the issue on Geoven's Gink?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/pubpub-zz/ppInk/issues/7#issuecomment-674490089, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKHGCQBTDYCHC2SXYJ6WFHTSA6BGTANCNFSM4QAMHQ3A
.

Hi HungrySnake;
Can you have a look at this version bef
ore versioning
ppInk.zip

It works. Thanks.
Found another strange issue with the arrow but the behavior is not consistent.
I hit me a few times that when I click the arrow, the number stamp got selected. I'm not able to reproduce the issue but it happens at least 3 times today.


Is there a way to use this library with Next.js ISR?

See ISR documentation for explanation of ISR.
Main issue is that all the examples assume that entire website is known at build time but this isn't the case if you are using ISR.
Any examples/ideas?

I guess you could try and create an index using the NodeJS APIs.
https://pagefind.app/docs/node-api/
This of course requires that all content is known at build time though, but that is gonna be a requirement for any at build, static, indexed search libraries.


Rename opts to data.

Could we also expand encodeFilters to support operators? Right now it just defaults to "="


Incorrect of implementation of export_command for PNG

Hi! A user raised a question in an internal Tableau Slack channel about issues when using the export command for PNGs. (Link in case you have access to said channel.)
They'd attempt something along the lines of tabcmd export "wb/view" --png -f "output.png, and see an error saying 'ViewItem' object has no attribute png.
I've taken a quick look at the Python code and found that line 147 of export_command.py refers to view_item.png. However, that's not the right attribute after populate_image; it should be view_item.image.
As a barely amateur developer, I'm not very well acquainted with how I'd go and pull, then fix this myself (Git flow-wise), so I thought I'd just bring this up as an issue. The fix is trivial, so if you let me know what that process is, happy to follow standard procedure instead.
Cheers!

This is fixed in the latest release - I'll close this now, but feel free to re-open it if there's anything missing or further work needed.

@jacalata: I'm afraid it doesn't work. Moreover, duplicate logging is still present.

@jacalata thanks for prompt response; it works now


"net::ERR_FILE_NOT_FOUND" when loading explorer

VSCode Version: 1.20.0
OS Version: Window 10

Steps to Reproduce:
when loading customized explorer view, toggle developer tools, it has error
"[vscode installation folder]/resources/app/out/vs/workbench/electron-browser/bootstrap/undefined net::ERR_FILE_NOT_FOUND"
the implementation of the getTreeItem method of TreeDataProvider might return TreeItem with undefined iconPath and command since the interface marks them as nullable, not sure whether this is related.

@ansyral I am not able to reproduce this when I do not provide an iconPath and command. Can you please try again on latest (preferably insiders) and let me know if you see it yet?


Question: will this extension be susceptible to the '50 work items limit' bug?

VSTS Extension you are using
Generate Release Notes (crossplatform)
Where are you running it?
TFS on-premise Version 16.122.27102.1
Version of Extension/Task
1.6.2
Expected behaviour and actual behaviour
My query is, is it likely that this extension will also be affected by the 50 items bug addressed for the PS version of this extension in this issue?
I'm unable to obtain output from this task until a release is run (scheduled for tomorrow)

As per my standard practice I am closing this issue as I think the question is answered as bets I can. If this issue remains a problem please do not hesitate to re-open it


solved issue: cant freeze rcc clock when using spi

solves #65
this PR tackles both when using SPI as well as dma, so there are 2 commits separate,
when called spi enable it requires mutable reference to rcc
    let mut spi1:Spi1 = Spi::new(p.SPI1, (sck, miso, mosi)).enable(
        &mut rcc,
        ClockDivider::DIV8,
        spi::Mode{
            polarity : Polarity::IdleHigh,
            phase : Phase::CaptureOnFirstTransition,
        }
        );

which fails when when freeze is called,
18 |     let clks = rcc.cfgr.sysclk(32.mhz()).freeze();
   |                -------- value partially moved here
...
25 |         &mut rcc,
   |         ^^^^^^^^ value borrowed here after partial move
   |
   = note: partial move occurs because `rcc.cfgr` has type `stm32f7xx_hal::rcc::CFGR`, which does not implement the `Copy` trait

when enabling spi we can use rcc::Enable which solves above issue, now instead of giving mutable reference of rcc to enable function we are giving mutable reference to rccbus to new function same as in i2c.
i am not a professional in this case, feel free to reject this PR if it is wrong

Checks failing for examples, which can't be solved because every other mcu has different rccbus for spi, this is fine because examples created are specific to a single mcu

Thanks for looking at this @7h3qu1rkyb1t! At a glance, this fix seems reasonable to me.
Any thoughts @pftbest or @hannobraun? If not, I'll merge this later this week.

I had a quick glance, and one thing that jumped out to me is that enabling the SPI peripheral clock moved from Spi::enable to Spi::new. Not sure if this is a problem (I don't really have a big-picture overview here, and no time to get re-acquainted right now), but it's certainly misleading.

I think when we create new spi peripheral first thing we need to do is enable peripheral clock, if not we can't configure anything on that peripheral. Here We are not enabling spi, that would be big mistake.
If let say in future we are making some default configuration when the peripheral is created, if peripheral clock enable is en enable state then we all the default configuration added while creating it wont take effect.
Another thing is if anyone creates a peripheral he meant to initiate that peripheral means start the clock

One more thing is i think we need to restructure the api such that every peripheral initiation is same, (if yes may be you can assign that to me). It shouldn't be confusing like i2c doesn't have init or enable but spi do have

I think I wrote this code originally. I don't recall what I thought back then, but there's a reason why I prefer leaving any initialization out of the constructor and doing that in a separate method. I think having a separate constructor each HAL API is wrong, for several reasons which are besides the point here (but which I should definitely take the time to write down at some point).
I think a better approach is for the HAL to wrap pac::Peripherals in its own Peripherals struct. If you do that, you can't have initialization code in the constructor, otherwise you get a lot of unnecessary runtime overhead just for using the HAL. An example of a HAL that works that way is LPC8xx HAL.
I don't think any of it matters here. I'm just providing some background on why the decisions might have been made that way.

Moved clock initiation to enable method

@hannobraun changed initialization as you suggested

Okay then, since nobody objected, I'll merge now. Thank you for the PR, @hardfau18!


Added deploy on tag

Tags are tested to contain the version that they are tagged at.
Copied code from
https://github.com/fossasia/knittingpattern/blob/master/.travis.yml

@artemrizhov You can merge and create a tag to try it out :)

@niccokunzmann Could you please explain how this would change the version number in hanging_threads.__version__?

Sure, this does not change it. It solves #7 which is the second step: deploy if there is a tag. It does not change the version number. It assumes the version number to be there.

Oh, ok, I see. Thanks for explanation.

Oh, it merged into develop which should be removed actually.

Could you please create new PR to master?

Actually I can do this ))) Merged into master in #38.


[4.2][Migrator] Use Version::getCurrentLanguageVersion() as latest version

Cherry-pick of #16209 reviewed by @nkcsgexi
Instead of using hardcoded number, use version::Version::getCurrentLanguageVersion() as the latest supported Swift language version.

@swift-ci Please test


Allow colon characters in bucket names

Unfortunately there is no straight forward way to test this, since localstack does not permit colon names in bucket names either.
https://github.com/localstack/localstack/blob/e8680021583a49697320ae1d65b5683082d0f00c/localstack-core/localstack/services/s3/utils.py#L499-L503

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

4 of 4 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 92.263%

Totals

Change from base Build<PHONE_NUMBER>9:
0.01%

Covered Lines:
2051

Relevant Lines:
2223

💛  - Coveralls

Thank you!


Run this project

Hi everyone,
How run this project with Mac M1 after install opencv-python pycocotools matplotlib onnxruntime onnx?
And if i add new image? How can I predict the result of the new image?

Hi, it should be similar to run sam on Mac m1, you can read this article for more information.
For adding new images, you can modify demo_hq_sam.py(https://github.com/SysCV/sam-hq/blob/main/demo/demo_hqsam.py), following our provided image examples in this file.  and then excute python demo/demo_hqsam.py.

Thanks for support


Add support for negative hexadecimal numbers

Current implementation segfaults on negative numbers. Fix this issue by supporting them.
Note: While I think the generic implementation works, I am not so confident about the rewrite rules & inlinable annotations.
May require some update to the doc in #10.

You mean to rely on the overflow? I am not sure this is a good idea. E.g. GHC will gladly accept -0x01 :: Int8 but will warn on 0xff :: Int8, and rightly so.
But I see this is the behaviour of printf. Also, it does not allow to format as -0x01.
I will give it a try.

Done:
runBuffer (\b -> b |>& (-1 :: Int8)) == "ff"

The idea is to create RULES to use the same implementation for Words and Ints; Ints are casted to their corresponding Words.
But for other types, it is not clear how to optimize this. So I adapted the code from the printf function in base to handle those types using Integer.

Rebased on #15. I added the tests and benchmarks of the previous implementation of this PR.
I also optimised dropNibble for common integer sizes. I left a commit with an alternative optimization using rules for discussion only.
When this PR is ready, all commits should be squashed.

LGTM, waiting for you to mark as ready.
If you do not mind, I'd prefer to merge unsquashed history here.

If you do not mind, I'd prefer to merge unsquashed history here.

I do not mind, if you think this is useful. I wonder if we should add tests using non-base integers such as in  wide-word, for completeness.

You can test Int30, but let's avoid additional dependencies.

I added a test for Int30. It required fixing Int30, to handle negative values. This the same fix as in #17.

@Bodigrim I made a mistake with Int30 and it looks the CI is looping, but I have no way to cancel it 😅

Fixed. Implementation seems correct, but there may be optimization opportunities.
I deactivated test for Decimal with Int30, since they now need the fix in #17.

Note to self: ensure coverage using general IntN n from #17.

Rebased. The test now uses random signed integer sizes in range (8, 64). We could use the same approach with unsinged integers. My experiments with tests should be squashed; I left them for now in case we need them for discussion.

Looks good, please rebase and rearrange commits as you wish them merged.

@Bodigrim rebased. I reworked the commit history, but I kept the attempt with rewrite rules as your required.
I also added tests for unsigned  numbers with random sizes. They should probably added to decimal builder as well, but let’s keep focus.

Great stuff!


Dont work

It doesn't work. I deployed your project in vs to look at the code for the sake of my interest, as a result I got about 80+ errors in the terminal

Hi! I just tried to install the dependencies, and after running the project, everything worked fine. Could you provide an errors log?

I get npm ERR! code EINVALIDTAGNAME
npm ERR! Invalid tag name ">=^16.0.0" of package<EMAIL_ADDRESS>Tags may not have any characters that encodeURIComponent encodes.
I can't fix

@xuanchinh97 try
npm install --legacy-peer-deps

I used Node version v17 at first, then I used Node version v16, npm version  8.1.2
npm install --legacy-peer-deps
npx browserslist@latest --update-db
npm install caniuse-lite
npm audit fix
npm audit fix --force
npm start
it work for me


[Bug]: imagePullSecrets is not set in Pod spec for Pooler

Is there an existing issue already for this bug?

[X] I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

[X] I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

[X] I have read the troubleshooting guide and I think this is a new bug.

Contact Details
<EMAIL_ADDRESS>Version
1.23.2
What version of Kubernetes are you using?
1.29
What is your Kubernetes environment?
Self-managed: kind (evaluation)
How did you install the operator?
Helm
What happened?
We do have PULL_SECRET_NAME set in the operator configuration and expect it to be using for pulling images.
For cluster instances everything works fine, but Pooler's pod spec has no imagePullSecrets when poolers are deployed, causing inability to pull the image:
Expected:
  containers:
    - name: pgbouncer
      image: >-
        <image>
      command:
        - /controller/manager
        - pgbouncer
        - run
 ...
    seccompProfile:
      type: RuntimeDefault
  imagePullSecrets:
    - name: postgresql-pooler-ro-pull
  schedulerName: default-scheduler
  tolerations:
    - key: node.kubernetes.io/not-ready
...

Actual:
  containers:
    - name: pgbouncer
      image: >-
        <image>
      command:
        - /controller/manager
        - pgbouncer
        - run
 ...
    seccompProfile:
      type: RuntimeDefault
  schedulerName: default-scheduler
  tolerations:
    - key: node.kubernetes.io/not-ready
...

At that time, a Secret named postgresql-pooler-ro-pull are present in the Namespace, restarting Pooler's pod or Pooler's Deployment fixes the issue.
It looks like operator creating Pooler's Deployment before the pull-secret, so pods has no imagePullSecrets set.
Cluster resource
No response
Relevant log output
{"level":"info","ts":"2024-08-15T13:53:49Z","msg":"Creating deployment","controller":"pooler","controllerGroup":"postgresql.cnpg.io","controllerKind":"Pooler","Pooler":{"name":"postgresql-pooler-ro","namespace":"some-namespace"},"namespace":"some-namespace","name":"postgresql-pooler-ro","reconcileID":"b9cbb6b0-c695-447e-b0f6-c4ecfa08b2cc"}
{"level":"debug","ts":"2024-08-15T13:53:49Z","logger":"pooler_pull_secret","msg":"creating image pull secret for service account","controller":"pooler","controllerGroup":"postgresql.cnpg.io","controllerKind":"Pooler","Pooler":{"name":"postgresql-pooler-ro","namespace":"some-namespace"},"namespace":"some-namespace","name":"postgresql-pooler-ro","reconcileID":"b9cbb6b0-c695-447e-b0f6-c4ecfa08b2cc","caller":"internal/controller/pooler_update.go:304"}

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hello @PhantomPhreak, the imagePullSecret should be tied to the serviceaccount

Hello @PhantomPhreak, the imagePullSecret should be tied to the serviceaccount

Hi @armru,
does it mean some additional operator configuration is required?

Hello @PhantomPhreak , the image pull secret should have been added on the service account linked to the pod, not on the Pod itself, anyway I've opened a PR to improve this behavior https://github.com/cloudnative-pg/cloudnative-pg/pull/5344


Ruby 3 / Rails 7 compatiblity

[x] Bump dependencies including eth 0.5X
[x] Dockerized app
[ ] Fix specs
[ ] Replace Blockexplorer (API no working anymore) by bitcoinexplorer ?
[ ] Fix cucumber

Currently having trouble with /address not returning detailed transactions' outputs https://github.com/janoside/btc-rpc-explorer/issues/439
We might need to look for another explorer blockchain.info (cant find their testnet anymore) or blockchair


instancer: add --ignore-overlap-errors option

This is to be able to ignore tricky glyphs that sometimes trip up Skia PathOps.Simplify operation.
We have no idea how to fix this upstream (short of having the glyphs redrawn), and perfect is the enemy of good..
Works around https://github.com/fonttools/fonttools/issues/2363 and https://github.com/google/fonts/issues/3365
/cc @nathan-williams

(I remember working around this by falling back to booleanOperations at some point...)

but booleanOperations doesn't support quadratic curves as far as I know

I think you're right about that.


get post list from list of files in subfolder

postsList = ["20160114.html", "20160115.html"];
should be a list of all files in subfolder "/posts"

can't be done with jquery, let's stick to the basics for now :)


Rename takes kwargs

[x] Tests added (for all bug fixes or enhancements)
[x] Tests passed (for all non-documentation changes)
[x] Fully documented, including whats-new.rst for all changes and api.rst for new API (remove if this change should not be visible to users, e.g., if it is an internal clean-up, or if this is part of a larger project that will be documented later)

Looks good to me! Feel free to merge


Docs/docker-compose guide

I use docker-compose for my local development setup because minikube is too resource intensive for my team. Ambassador on top of docker-compose is a fast way to experiment with different features really quickly. While there are differences between how a kuberenetes and docker-compose environment operate all Ambassador features work in both.
The reason I am opening this PR is two fold:

To make it easy for more people to discover how useful Ambassador is
To continue the docker-compose support (though not for production use)

It seems like the travis-ci check has been running into issues for a couple of days:
openssl aes-256-cbc \
    -K $encrypted_95ce0d75e6f7_key \
    -iv $encrypted_95ce0d75e6f7_iv \
    -in kubernaut-config.json.enc \
    -out ~/.config/kubernaut/config.json \
    -d
iv undefined

Thanks! @nbkrause can you try out this tutorial please?

It seems like the travis-ci check has been running into issues for a couple of days:
openssl aes-256-cbc \
    -K $encrypted_95ce0d75e6f7_key \
    -iv $encrypted_95ce0d75e6f7_iv \
    -in kubernaut-config.json.enc \
    -out ~/.config/kubernaut/config.json \
    -d
 iv undefined

This is due to a secret that is not public.

@nbkrause I have addressed your comments in the latest commit though I used the shorthand version for port mapping eg 8080:80. I can use the longhand version if you desire.


Simultaneous Wheel Homing

Currently wheels home one by one. This take a lot of time and should eventually be replaced with a homing procedure that homes all the wheels simultaneously. This can be done by moving the homing logic within the rover_drive_system.hpp file. This should be done after we get slip ring homing mechanism completed.

Refer to #171 for how to implement this to be non-blocking. But if blocking is found to be okay (since the rover should come to complete stop) then any implementation should be fine.


Remove patch_skia.py and its related patch.

They were only necessary before moving to M45. The hook that applied it
to the tree was already removed in 9eff35de ("Roll Chromium
45.0.2454.85"), but the script and patch were left behind.

ping @darktears

rs=me


added login page accessible from index`

PR Title/Tagline
Issue Number(s): #3 .
Added a login page without styling
How to Test

run yarn dev, (if yarn failed be sure to run npm install . for all possible packages)
click on log in in the index page

Work done
[ x ] The page is routed to /login
[ x ] The page has a header labeled "Login"
[ x ] The page has a text field labeled "Email"
[ x ] The page has a text field labeled "Password"
[ x ] Typing in the password text field will censor the text
[ x ] The page has a button labeled "Login"
[ x ] The actual page component should live in the src/screens/ directory

It was a mistake when deleting package-lock, I've added it back


Merge cleanups with master

Merging this, since this is final.

cc @geohacker @batpad Merged cleanups with master.


Proper means to reference multiple mvn profiles

According to http://maven.apache.org/guides/introduction/introduction-to-profiles.html multiple profiles are referenced as a comma separated list:
"This option takes an argument that is a comma-delimited list of profile-ids to use."

Can one of the admins verify this patch?

I think both works, but I personally prefer -Popenshift,openshift-it as well :-)

[test]

merged: 7ea11a0deb23aec6fbaa1ae43b5c050a156167e6


1xN tensors are not visualizable

Describe the bug
Logged 1xN tensors don't seem to be visualizable (potentially related to https://github.com/rerun-io/rerun/issues/3709?)
import torch
import rerun as rr

rr.init('tensor-viz', spawn=True, strict=True)
rr.log('1x10', rr.Tensor(torch.zeros(1, 10))

Screenshots

Rerun version

rerun_py 0.15.0-rc.1 [rustc 1.74.0 (79e9716c9 2023-11-13), LLVM 17.0.4] x86_64-unknown-linux-gnu release-0.15.0-rc.1 3c298fd, built 2024-04-02T21:34:01Z

Additional context

A workaround I stumbled upon is first logging a 2xN tensor to the same entity path and then overwriting it with the original 1xN tensor, which makes the 1xN tensor show up in the viewer:
rr.log('1x10', rr.Tensor(torch.zeros(2, 10)) # dummy 2xN
rr.log('1x10', rr.Tensor(torch.zeros(1, 10)) # original

Thanks for the report. I could reproduced both the issue and the workaround on main.


Dcos 15262

Testing DCOS-15262

@orsenthil ignore this - testing mergebot change, but need to send an @ notification

@mesosphere-mergebot ping


Inconsistencies in (de?)referencing buffers for fd_socket_tx writes (send_80211_* functions)

Some of the send_80211_* writes use & (address-of), and some of them don't.
For example:
In send_80211_associationrequest it uses "&wltxbuffer"
https://github.com/ZerBea/hcxdumptool/blob/d45799b6c81e60824fa68e0952623ce6ef2cd9d1/hcxdumptool.c#L1146
but in send_80211_eap_request_id (right below), it does not. (just "wltxbuffer")
https://github.com/ZerBea/hcxdumptool/blob/d45799b6c81e60824fa68e0952623ce6ef2cd9d1/hcxdumptool.c#L1169
I'm pretty sure these all should NOT be using &, but I am not 100% on that. Changing them does not create any compiler warnings, and since it is just reads, valgrind or other tools would not throw any errors.
Either way, the inconsistency in them seems like an issue to me.
~/hcxdumptool$ grep 'write(fd_socket_tx' ./hcxdumptool.c
if((write(fd_socket_tx, &wltxnoackbuffer, ii)) == ii) return;
if((write(fd_socket_tx, &wltxbuffer, ii)) == ii) return;
if(write(fd_socket_tx, wltxbuffer, ii) == ii) return;
if(write(fd_socket_tx, wltxbuffer, ii) == ii) return;
if(write(fd_socket_tx, &wltxbuffer, ii) == ii) return;
if(write(fd_socket_tx, &wltxbuffer, ii) == ii) return;
if((write(fd_socket_tx, &wltxbuffer, RTHTX_SIZE + MAC_SIZE_NORM + AUTHENTICATIONRESPONSE_SIZE)) == RTHTX_SIZE + MAC_SIZE_NORM + AUTHENTICATIONRESPONSE_SIZE) return;
if((write(fd_socket_tx, &wltxnoackbuffer, ii)) == ii) return;
if((write(fd_socket_tx, &wltxnoackbuffer, RTHTXNOACK_SIZE + MAC_SIZE_NORM + AUTHENTICATIONREQUEST_SIZE)) == RTHTXNOACK_SIZE + MAC_SIZE_NORM + AUTHENTICATIONREQUEST_SIZE) return;
if((write(fd_socket_tx, &wltxbuffer, RTHTX_SIZE + MAC_SIZE_NORM + AUTHENTICATIONREQUEST_SIZE)) == RTHTX_SIZE + MAC_SIZE_NORM + AUTHENTICATIONREQUEST_SIZE) return;
if((write(fd_socket_tx, &wltxnoackbuffer, ii)) == ii) return;
if((write(fd_socket_tx, &wltxnoackbuffer, ii)) == ii) return;
if((write(fd_socket_tx, &wltxnoackbuffer, RTHTXNOACK_SIZE + MAC_SIZE_NORM + PROBEREQUEST_UNDIRECTED_SIZE)) == RTHTXNOACK_SIZE + MAC_SIZE_NORM + PROBEREQUEST_UNDIRECTED_SIZE) return;
if((write(fd_socket_tx, &wltxnoackbuffer, RTHTXNOACK_SIZE + MAC_SIZE_NORM + 2)) == RTHTXNOACK_SIZE + MAC_SIZE_NORM +2) return;
if((write(fd_socket_tx, &wltxnoackbuffer, RTHTXNOACK_SIZE + MAC_SIZE_NORM + 2)) == RTHTXNOACK_SIZE + MAC_SIZE_NORM +2) return;
if((write(fd_socket_tx, &wltxnoackbuffer, RTHTXNOACK_SIZE + MAC_SIZE_NORM + 2)) ==RTHTXNOACK_SIZE + MAC_SIZE_NORM +2) return;
if((write(fd_socket_tx, &wltxnoackbuffer, RTHTXNOACK_SIZE + MAC_SIZE_NORM + 2)) == RTHTXNOACK_SIZE + MAC_SIZE_NORM +2) return;

It looks like these were part of a big change 7 months ago ( 311e093 ) and would explain my (perceived) change in hcxdumptool attack performance around that time. If it was sending "garbage" ( just data/pointers in the GOT? ) instead of actual packet data, that would probably massively impact things.

You're right. Thanks.
I'll fix that.

Ugly (nasty) copy and paste error.
Should be fixed, now.

I ended up doing some tests to see which was the right one... & or not. Both seem to have the same behavior and output (strace to verify). I ended up comparing the output bytecode... and the compiler appears to be smart and results in the same exact code for both situations(&wltxbuffer and wltxbuffer). I would not have expected that.
Anyway, the same issue also appears on some of the memcpys before the writes. For example in send_80211_authenticationresponse ( https://github.com/ZerBea/hcxdumptool/blob/90a1e3a7cf628e042bdc7b291437ad664e48151a/hcxdumptool.c#L1267 ) there isn't an &, but in send_80211_associationresponse ( https://github.com/ZerBea/hcxdumptool/blob/90a1e3a7cf628e042bdc7b291437ad664e48151a/hcxdumptool.c#L1248 ) there is.

Looks like gcc is a way too smart.
But anyway. that need a fix. I'll check that.

Should be fixed by latest commit, now.


Refactored the 404 page

Fixed #111 I have Refactored the 404 page and added a button to link back to the Homepage, created a new Pull Request because other one is creating conflict issues.

LGTM merging


[Settings] Mouse Utilities: Icons missing

@jaimecbernardo , @niels9001
The colored utility icons are missing in installer. they aren't there in the final ux of 0.51.0.
Originally posted by @htcfreek in https://github.com/microsoft/PowerToys/pull/14496#issuecomment-983006002

This is fixed in 0.53, get it at https://aka.ms/installPowerToys


Use isJobTracked() when sorting out blacklist

Originally cherry-picked from PR https://github.com/DataDog/jenkins-datadog-plugin/pull/23 submitted by @dmabamboo

Looks good, thanks @dmabamboo !


Environmental variables in markdown not replaced in bundle

Is your feature request related to a problem? Please describe.
In the documentation says that is possible to use environmental variables inside MD files:
https://redocly.com/docs/developer-portal/guides/environment-variables/#step-1-define-the-variable,
but it is not clear if redocly-cli replace them during bundling.
Also it is not clear how to write MDX files and include them in the project
Describe the solution you'd like
Would be great a step-by-step tutorial and complete source code example that show this feature
Additional context
I've tried to add environmental variables inside /docs/info-description.md
My openapi.yaml file:
openapi: 3.0.0
info:
  version: 1.1.0
  title: My API
  contact:
    email<EMAIL_ADDRESS>    url: 'https://my-company.com'
  x-logo:
    url: 'my-company.com/logo.png'
  description:
    $ref: ../docs/info-description.md

My /docs/info-description.md

  Additional file

My .env.development
DOC_BUCKET=my-bucket
APP_DOMAIN=my.app
STAGE_NAME=dev

Hi @web-fu
Let us check it, please.

@web-fu
Unfortunately, I was not able to replicate this issue from our side with the given example.
I have inserted both the aforementioned HTML link and markdown style link, they are working as expected. Here is my md file:

  Additional file

Markdown link:

[basic markdown knowledge](https://{{process.env.DOC_BUCKET}}.my-company.com/{{process.env.STAGE_NAME}}/{{process.env.APP_DOMAIN}}/files/myfile.pdf)

And both links render correctly:

Thus, is there a chance you could provide us with additional details regarding this use-case?

Hi, I am using redocly - cli without any premium subscription.
I'm not sure if is a bug, or I miss some steps, so if you could provide a working demo I can check it.
Also, if you want I can create a repository, but I'm not sure this would be helpful

Hi @web-fu,
Kindly note, that the aforementioned environment variables are available only for our premium product (both API docs and developer portal). Since you are using only Redocly CLI, it is the expected behavior.
Hope it helps.


Stop OIDC flow when remote writing with bad auth header

When handling remote write requests, if the Authorization
header isn't present, we don't want to redirect users back
to the identity provider for login.
The reason behind this is that tenants can overload the
identity provider in case they have bad configuration.
We want to be friendly and help prevent this issue from
happening.
Signed-off-by: Douglas Camata<EMAIL_ADDRESS>

Summarizing the recent changes after applying review's feedback:

Check on content of the Authorization header removed.
No redirect to login in both Prometheus remote write and Loki log push endpoints. Traces already don't have the login redirect (it runs on the gRPC middleware stack).
The core logic is separate from the OIDC authenticator middleware to avoid injecting knowledge about what's behind authentication into the authenticator.

@matej-g @esnible @PhilipGough looks like the Github feature for re-requesting a PR view is a bit messed up. This is ready for another look from you.

By the way, I can give a try to adding a test for this in another PR. I am afraid it will take too long and add too much modification to a single PR though, @matej-g

thanks for adding this!

By the way, I can give a try to adding a test for this in another PR. I am afraid it will take too long and add too much modification to a single PR though, @matej-g
^ I'd vote for adding a test on this PR too

To be able to write tests for this using the e2e framework, we need https://github.com/observatorium/up/pull/44 to be merged.

@PhilipGough: can you please re-review the PR? I fixed your last comment. :)


Discord server is down?

Hi there,
I don't know where to ask so I ask here.
Yesterday, I was downloading images from Discord when I was suddenly splashed out by the server.
I can't get back in anymore, the invitation here on Github doesn't work, even if I use another Discord account. What's going on?

anyone knows?

Thank you for not answering.
I discovered on my own that either I have been banned or there is a malfunction preventing me from re-entering.
In case I was banned, it would have been nice to at least know why. Goodbye.


Sorting sometimes is unstable

Occassionally (but rarely), import-sort's output is unstable. If I run it, two import lines get flipped. But if I run it again, it flips them back. It's been pretty hard to reproduce, but here is an example:
// @flow

import { athing } from 'common-tags';
import conf from 'config';
import a1 from 'controllers/a1';
import b1 from 'controllers/b1';
import c1 from 'controllers/c1';
import d1 from 'controllers/d1';
import e1 from 'controllers/e1';
import e2 from 'controllers/e2';
import e3 from 'controllers/e3';
import f1 from 'controllers/f1';
import l1 from 'controllers/l1';
import o1 from 'controllers/o1';
import p1 from 'controllers/p1';
import s1 from 'controllers/s1';
import u1 from 'controllers/u1';
import w1 from 'controllers/w1';
import type {
  NextFunction as Next,
  $Request as Req,
  $Response as Res,
} from 'express';
import express from 'express';
import { stuff } from 'lib/s1';
import { morestuff } from 'lib/s2';
import { omit } from 'lodash';
import { isNil, pick } from 'lodash/fp';
import e4 from 'm/e4';
import e5 from 'm/e5';
import r1 from 'm/r1';
import s2 from 'm/s2';
import u2 from 'm/u2';
import u3 from 'm/u3';
import m1 from 'moment';

The problem happens in the imports from express. Note that one is a "type import" and one is not. These just keep getting flipped with every re-run of import-sort. If you remove any of the other imports from this file to minify the example, this suddenly becomes stable…
Here's the .importsortrc config:
{
  ".js": {
    "parser": "babylon",
    "style": "module"
  }
}

I'm using import-sort 4.2.0.
Any help would be appreciated!

I'm getting the same thing. Only the following 2 lines are affected. Flips back and forth on each run. Disabling for now.
import { CAMERA } from './UI/permissions.js'
import type { Permission } from './UI/permissions.js'

"import-sort-cli": "^4.2.0",
"import-sort-parser-babylon": "^3.2.0",
"import-sort-style-module": "^3.0.0",
...
"importSort": {
    ".js, .es": {
      "parser": "babylon",
      "style": "module"
    }
  },

@renke Do you have any idea what could be causing this?

It always happens around cases where there are two import lines for the same module: one with a type import, and one with a normal import, i.e.
import { A } from 'x';
import type { B } from 'x';

im having a similar weird bug in an angular module, the item starting with "F" is at the top and leaves a return gap between the rest of the imports. see screenshot:

Anyone have any work arounds?

Possibly related to known bug #59 . Give @b1f6c1c4/import-sort a try.


Failed to train the model with provided command

Hi @yuvalkirstain
Thanks for your nice contribution!
I tried to train the model by the official command:
accelerate launch --dynamo_backend no --gpu_ids all --num_processes 8  --num_machines 1 --use_deepspeed trainer/scripts/train.py +experiment=clip_h output_dir=output

but there are some errors:
ValueError: When using `deepspeed_config_file`, the following accelerate config variables will be ignored: ['gradient_accumulation_steps', 'gradient_clipping',
'zero_stage', 'offload_optimizer_device', 'offload_param_device', 'zero3_save_16bit_model', 'mixed_precision'].
Please specify them appropriately in the DeepSpeed config file.
If you are using an accelerate config file, remove others config variables mentioned in the above specified list.
The easiest method is to create a new config following the questionnaire via `accelerate config`.
It will only ask for the necessary config variables when using `deepspeed_config_file`.
[01:26:13] ERROR    failed (exitcode: 1) local_rank: 0 (pid: 1527604) of binary: /usr/bin/python3

Thank you so much for opening this issue! This seems like an accelerate issue that I am not able to reproduce, so let us try to solve it together :)
I suggest that you first make sure that you remove your <cache_dir>/huggingface/accelerate if it exists and try again. If this does not work, then try this (taken from the accelerate/deepspeed guide):

Run accelerate config:

$ accelerate config
-------------------------------------------------------------------------------------------------------------------------------
In which compute environment are you running?
This machine
-------------------------------------------------------------------------------------------------------------------------------
Which type of machine are you using?
multi-GPU
How many different machines will you use (use more than 1 for multi-node training)? [1]:
Do you wish to optimize your script with torch dynamo?[yes/NO]: NO
Do you want to use DeepSpeed? [yes/NO]: yes
Do you want to specify a json file to a DeepSpeed config? [yes/NO]: yes
Please enter the path to the json DeepSpeed config file: ds_config.json
Do you want to enable `deepspeed.zero.Init` when using ZeRO Stage-3 for constructing massive models? [yes/NO]: yes
How many GPU(s) should be used for distributed training? [1]:4
accelerate configuration saved at ds_config_sample.yaml

Content of the accelerate config:

compute_environment: LOCAL_MACHINE
deepspeed_config:
  deepspeed_config_file: ds_config.json
  zero3_init_flag: true
distributed_type: DEEPSPEED
downcast_bf16: 'no'
dynamo_backend: 'NO'
fsdp_config: {}
machine_rank: 0
main_training_function: main
megatron_lm_config: {}
num_machines: 1
num_processes: 4
rdzv_backend: static
same_network: true
use_cpu: false

And then try to run the script again.
Please update me on how it goes?

This issue is fixed when I remove the <cache_dir>/huggingface/accelerate, thanks for your help!

Hi @liming-ai @yuvalkirstain , I am facing the same issue but I have one main question: in the config, you have deepspeed_config_file: ds_config.json, do we have to get this ds_config.json from somewhere (example: https://github.com/lucidrains/routing-transformer/blob/master/examples/enwik8_deepspeed/ds_config.json) or if I don't have it, the script still will work?

@vishaal27 did you try running it and had an exception? the repo is verified so following the instructions should allow you to run.

Yes, thanks, it worked but I now have an issue with the gradient accumulation steps so I opened another issue for it.


CDI-588 More literals for built-in annotations

Inject, Vetoed, Specializes, TransientReference
also polish the spec wording

+1

+1 for me. Could you please rebase your branch for a clean merge. Thx

@antoinesd Rebased.


Store page status code into cache.

Proposed changes in this pull request
(Reopen #6732 - Branch rebased to develop.)
Some extensions can have error pages directly in cms administration. Such pages are cached. For this purpose, it is also necessary to save the status code of the corresponding error, otherwise HTTP 200 is set.

thank you for reopening the PR to develop @zbohm 👍
Would you also be able to add an entry to the CHANGELOG once https://github.com/divio/django-cms/pull/6755 gets merged?

Coverage remained the same at 78.215% when pulling f659d04323e0027d9d229fb2961ce27259a59cf2 on zbohm:cache-page-status-code into 7dc241e086d6d13cab69390ebba2eb2635c7a5f7 on divio:develop.

Changelog updated. Rebased to divio/develop.

@zbohm getting back on this PR in hope to merge it, there are comments we would need you to address before we can merge.
=> moving this to 3.9.x as it is considered a fix.


Updates

chore: add recommended fields topackage.json: bugs, homepage, contributors
chore: bump devDeps (and switch to Babel 7 with non-deprecated replacement of babel-preset-es2015, @babel/preset-env)
chore: use an eslint-recommended file extension (json) (and for Babel)
chore: specify engines

Requires esm now for ava (unless were to use Node's implementation): https://github.com/avajs/ava/blob/master/docs/recipes/es-modules.md
BREAKING CHANGE:
Had not been indicating supported engine.
I wasn't sure the engine specify. While Babel might take care of the syntax, one might need to add https://github.com/mysticatea/eslint-plugin-node to check the builtins (if not using core-js). Assuming that is, you even want Babel anymore.
Note that I changed the repository to a full link not only to silence an inadequate package.json validator, but because full links can be useful in IDEs (e.g., in Atom, I can click "cmd-O" on a URL under the cursor to open it).
Planning to add a couple PRs, but thought I'd get things started here.

Coverage remained the same at 100.0% when pulling 9a796d7c845271c801257219775d7734db3a3a2e on brettz9:updates into 8f6fbae7d3a38fbb651366fade8a37002b680de5 on dustinspecker:master.

Thank you! These are awesome! Great commits too - makes this easy to review. Yeah, I'd totally be cool with having Babel removed going forward.

On second thought though, since the code is currently using ESM in source, unless there is a compelling reason to switch now to Rollup (or if time passes so as to use Node ESM), maybe it is easier to leave as is?


Update pull_request_template.md

This point in the checklist :
(I have added my name in the contributors list at the end of README.md file.)
is obsolete. So it is wise to remove it.
@QAZIMAAZARSHAD please assign this to me under DCP21

Yesterday you said it helps you in remembering git commands.
I want to tell, you can do these changes without using git quickly.
Just open the pull request template file in your repo, remove the line, commit changes, make PR. And its done.

@QAZIMAAZARSHAD Yes I know that method as well but I heard that it was like a shortcut or bad practice.

@QAZIMAAZARSHAD Yes I know that method as well but I heard that it was like a shortcut or bad practice.

Yaa in the case of many changes it causes difficulty in merging and few other problems like unnecessary indentations etc.

@QAZIMAAZARSHAD Ok then i will update it online for these small changes


fix: can't go to location but move cursor when use at argument

Now I see what you mean, it doesn't get scrolled to changed position. You can just use editor.revealRange(editor.selection), on the other hand let's change implementation

I'll handle change here to align behavior

@tjx666 I changed implementation so you can use peek or goto as goToMode arg


Document some tips and tricks for hardware setup with the Pi

There are a number of things I need to document more formally elsewhere (to save my future self and others time in hardware-related setup with the Pi and accessories)... but for now, I'll just add them here, in this issue.
A good power supply is essential
I bought a decent, name-brand 6-port 2A-per-port (except for a couple) power supply to power all the Pis in the Dramble. I could've also gone with a PC 5V PSU and hacked the power to the Pi through GPIO pins (a lot of cluster builds do this, since it's easier to custom wire and doesn't require a mess of micro USB cables).
But either way, you need to get clean, 2A or greater power to the Pi, or you're going to run into weird issues, like random restarts, USB device issues, network flakiness, etc.
If you ever run into strange issues with your Pi, check your power supply. For other Pis I've been using Samsung and Apple 2A chargers (like the one that comes with an iPad), and they have worked great for a couple years!
Increasing Current available for USB devices to 1.2A
I have an SSD that seems to require something like 300-500mA of current to function properly. Mix that with a 40 mA USB keyboard and a 100-200mA WiFi dongle, and the default 600mA supplied over the Pi's bus is a bit cramped. To prevent plugging in of certain medium-high powered USB devices from crashing your Pi or taking down other USB devices, there's a /boot/config.txt parameter that allows you to double the default current on USB. To enable this mode:

$ sudo nano /boot/config.txt
Add the line max_usb_current=1 and save the file.
Reboot the Pi.

This hack is only available on the Raspberry Pi B+ and later Pis (like the Pi 2 model B). Also, I have an open question (and another) asking whether there are any real downsides to setting this value to 1. For now, I'm only setting this value for Pis where I need to power an external HDD/SSD drive.
Tips for getting WiFi to connect automatically and reliably
See this guide, which I posted to Midwestern Mac's blog: Setting up an 802.11n WiFi adapter on the Raspberry Pi. Shows how to connect using WPA Supplicant, and how to prevent the WiFi from going into standby mode.
Tips for fixing a botched microSD card
If you accidentally break your Pi by editing the wrong file or breaking configuration somewhere on the microSD card you use to boot the Pi, you can usually just pull it and mount it on another workstation, edit the file to revert the change, and pop it back in your Pi.
I wrote a guide for mounting a Raspberry Pi's ext4-formatted microSD card in Ubuntu 14.04 on a Mac, and the process for other platforms is similar (use a VM, make it easy).
You can also re-image the entire SD card, and that's generally what I do if I've botched things too badly (easy to rebuild things when the configuration's all done in Ansible :).

Moved to the wiki: https://github.com/geerlingguy/raspberry-pi-dramble/wiki/Tips-and-Tricks


The text on Get Started Button on Homepage becomes illegible on hovering

🐛 Bug Report
On hovering, the background color of the button becomes nearly identical to the text color, hampering readability
Have you read the [Contributing Guidelines on Pull Requests]
yes

Hi @N-Shar-ma
Would you like to work on it?

@HarshCasper Sure, I would love to!


energy storage brakes monohierarchy

Description of the issue
energy storage is defined as: Energy storage is a function of an artificial object that has been engineered to contain energy for conversion as usable energy later.
It is currently a subclass of both energy carrier disposition and function.
Ideas of solution
It is not clear whether this is a bug or an intentional violation of mono-hierarchy.

Either delete 'subclass of' 'energy carrier disposition'
or improve definition and add an editor note explaining the violation.

Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

Btw, while touching energy storage, these small typos in its subclass methanation gas storage could be solved: A methanation gas storage is a energy storage that uses carbon dioxide and hydrogen from electrolysis to produce methane and store this. The methane can then be used to produce electricity or heat in a gas generator.

Take a look here: https://github.com/OpenEnergyPlatform/ontology/issues/209
Let's add an editor note.

I am still not convinced by this contruct. We made energy storage also a disposition, but I cannot find a single instance where we use it as disposition (so no axiom 'has disposition' some 'energy storage'). If we don't use it, what is the purpose of having a non mono-hierarchical energy storage?
However, here is a proposal for the editor note with the example in #209 and #276 describing the current state:
The energy storage function is not only a function but also an energy carrier disposition. E.g. a battery is both an artificial object that has an energy storage function but at the same time is a material entity that contains energy for conversion as usable energy and thus has an energy carrier disposition. However, the latter are not axiomatised.

For notice, there is now also a second issue caring about energy storage: #1262

I would delete 'subclass of' 'energy carrier disposition'. I don't see a necessity to violate the monohierarchy.
If we want to express that every entity with an energy storage function has also an energy carrier disposition, we could do that with a general class axiom (similar to the other axioms in energy carrier disposition).
'material entity' and ('bearer of' some 'energy storage') SubClassOf 'has disposition' some 'energy carrier disposition'
Once the axioms from #1262 are integrated, an alternative would be 'energy storage object' 'has disposition' some 'energy carrier disposition'.

Discussed today in OEO dev 46. PR #1348 will solve this issue completely.


Filter and download files by extension

The problem
I have a list of files in a webpage with extension pdf, zip and gz to download from a website. Is there a way in selenide to download only the pdf files from this list.
I tried downloading in Chrome using:
$().download(using(HTTPGET).withFilter(withExtension("pdf")).

However, it still downloads the files with zip and gz.
Is withExtension not supposed to filter based on the extension?
Tell us about your environment

Selenide Version: 6.10.1
Chrome Version:  109.0.5414.87
Browser Driver Version: 109.0.5414.74
Selenium Version: 4.6.0
OS Version:

Hi @Soumendu-Khilar

withExtension("pdf") is needed when you download files using FOLDER or PROXY methods. Because in these methods, the browser can receive multiple downloads at the same moment, and needs to choose one of them. That's where filter may help.
But when you download the file using HTTPGET method, Selenide downloads the single file explicitly using URL. The single URL cannot trigger downloading multiple files. That's why filter is not needed here.

If calling $("#button1").download() triggers downloading zip or gz, it means that you chosed the wrong button.


[hikogui] update to version 0.7.0

Update hikogui to version 0.7.0.
This library was called ttauri, which is a port in vcpkg already, but was renamed.
The port files where simply copied and modified for the new version, therefor the port file may have old statements in them.

What does your PR fix?

no fixes.

Which triplets are supported/not supported? Have you updated the CI baseline?

no changes: x64-windows-static

Does your PR follow the maintainer guide?

Yes.

Yes.
If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

@takev, thanks for the PR, could you update ttauri instead of adding a new port of hikogui?

@takev, thanks for the PR, could you update ttauri instead of adding a new port of hikogui?

We need both ports: hikogui as proposed, and ttauri as an empty port depending on hikogui. Cf. proj vs. prj4.

@dg0yt I have updated the pull request to make ttauri empty and depended on hikogui.
It does not make much sense to create polyfills, as many things have changed. Also both ttauri and hikogui are still pre-version-1.


Warning: React.createElement: type should not be null && Error: Element type is invalid:

First off thanks for this very well-written component for tag input. I'm struggling to get this working with my project, I've verified the version on npm works with a greenfields project (tested using https://github.com/unicorn-standard/starter-kit) but something in my project is leading to these two errors in the browser console and the app failing to run anytime I include a  in my render functions:
Error1: Warning: React.createElement: type should not be null, undefined, boolean, or number. It should be a string (for DOM elements) or a ReactClass (for composite components). Check the render method of InputTest.
Error2: Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. Check the render method of InputTest.
I'm using webpack, ES6, TS2, React 0.15/React-Router/React-DOM (I tried with 0.14 as well but same error). Any ideas on what I'm doing wrong? Google results indicate a myriad of possible causes none of which seem to have resolved the issue for me, thanks in advance for any help!

Thanks for reporting this.
It's strange, there is no InputTest component on the codebase. Are you sure the error comes from this package? Can you provide a small test app to reproduce this issue? I can't reproduce it.
Thanks
On Wed, 14 Dec 2016 at 23:43, Dan W <notifications<EMAIL_ADDRESS>wrote:
First off thanks for this very well-written component for tag input. I'm struggling to get this working with my project, I've verified the version on npm works with a greenfields project (tested using https://github.com/unicorn-standard/starter-kit) but something in my project is leading to these two errors in the browser console and the app failing to run anytime I include a in my render functions:
Error1: Warning: React.createElement: type should not be null, undefined, boolean, or number. It should be a string (for DOM elements) or a ReactClass (for composite components). Check the render method of InputTest.
Error2: Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. Check the render method of InputTest.
I'm using webpack, ES6, TS2, React 0.15/React-Router/React-DOM (I tried with 0.14 as well but same error). Any ideas on what I'm doing wrong? Google results indicate a myriad of possible causes none of which seem to have resolved the issue for me, thanks in advance for any help!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/mvader/react-categorized-tag-input/issues/20, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABQFF55B8gbU7bgh9vuhW1t_an3ncqY1ks5rIHD7gaJpZM4LNgRv.

Hi @mvader thanks for the quick response, I should have clarified InputTest was just a simple wrapper component I had TagInput within. I figured out what was wrong with the help of some of my colleagues, will leave it here for future Googlers 👍  -
If you are trying to use this component with Typescript, the import syntax of:
import TagInput from '...' will fail at runtime and will lead to the errors mentioned in my OP. To resolve the issue you must change the import syntax as such: import * as TagInput from '...' and the issue will be resolved.
We were hypothesizing that the need for this might be because the code built for distribution via NPM is non-ES6, possibly with some flavor of UMD for modules but that was just a hypothesis. Hope this saves someone a headache down the line 😄

Oh, it might be because of that. I will try to look into it when I have some time. Maybe it's just a typescript thing but it's worth the check.
Thanks!


Investigate OpenID foundation's RP conformance testing process

Context
As part of the follow-up to the recent Cloudflare Bot Fight mode incident where legitimate requests from our RPs were being blocked by Cloudflare managed challenges (see postmortem), we wanted to investigate the feasibility of completely writing our own SDKs instead of wrappign them around existing certified SDKs (like Panva's openid-client).
Given that the sgID flow is currently fairly basic, actually writing the code is easy. But we want to have basic guarantees on:

Security
Conformance to the OIDC spec

For security, we can set regular VAPTs for our SDKs. For conformance to the OIDC spec, we discovered that the OpenID foundation made available RP conformance testing suites which are available to the public (see their docs).
If conformance testing turns out to be fairly easy / straightforward, then there should be no blockers towards us writing our own SDKs.
Proposed follow-up action
Evaluate the conformance testing process to see how onerous it is

As discussed, @raynerljm to evaluate the feasibility of building the conformance test into our CI/CD pipeline


refactor: Replace q with bluebird.

Bluebird is faster, more spec compliant and has a much better set of built in tooling.
Replaces #1440

I signed it!

@zzo after I have merged this, I will start with the refactoring of file_list.js on the canary branch, that way we can hopefully ship it together with 0.13
By the way I'm still missing write access to this repo since this morning :(

lemmie now when the canary is pushed to npm :)


Prettier Formatting for Twitter Tooltips

As suggested by @KararTY in Twitch chat, this PR adds <style> tags to the rich Twitter tooltips introduced in #38.
This leads to "better" behavior on some Tweets (e.g. https://twitter.com/QuoteRed/status/312215975040778240) but could potentially be annoying for other Tweets (e.g. https://twitter.com/ianchaffee/status/311940617217392640). I do not believe this is much of a problem though since you can "just" hover off a Tweet that produces a large tooltip.
Additionally, we now truncate numbers larger than one million to one decimal place (for followers, likes, and retweets). This also mimics Twitter's behavior.

Depends on how well I can get screenshots working on sway. 😛

@RAnders00 I updated the original post to include tooltip screenshots of the mentioned Tweets.


Log rule bug

@StCostea Once this is merged are you planning to make similar changes to Enterprise Gateway to use the new rule? That would be highly desirable I would think.

@cmebarrow I started to check EE (but did not finish) and did not find any situation where this is required. But yes, we do need to update EE also. After the merge for this PR I will do it.
As for the comments, sorry about that, the previous PR that I closed had the issue connected. I will connect this one also.

Sorry, it seems it was the wrong issue. :(

@StCostea Looks good. Please resolve the build failure then I or @dpwspoon can merge. Build failure was [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.11:check (validate) on project test.util: Failed during checkstyle execution: There are 4 checkstyle errors. -

I don't see the error in Travis. I will try to rebuild locally.


AppViewManager is renamed into ViewUtils since angular2 beta 16

Angular 2 Beta 16 CHANGELOG

AppViewManager is renamed into ViewUtils and is a mere private utility service.

https://github.com/angular/material2/search?utf8=✓&q=AppViewManager

Removed references to AppViewManager in #378


iOS 15 compatibility

Can you make the app compatible with iOS 15? There a lot of old iOS devices which would benefit from it. I'm tryin to run it on iPhone 7 which is stuck at iOS 15.8.1.

I'm using too many new APIs to support even iOS 16, primarily the Observation and SwiftData stuff.


Come up with a name/URL for this project

It can't be "https://mdc-feedback-stage.herokuapp.com" forever. Who wants to own this? @mathias-gibson?

i can own it, but I'll probably need to organize a brainstorming sesh on it:
step - step, flow, map
feedback - loop, follothru,

Eh on bastardized spellings in the name of being cute, so I'd veto follothru, even though I like how it sounds and I recognize that "followthrough" isn't as visually catchy. Adding a 'w', though --  followthru?
I like the idea of loop, but I think that's too generic. MDCLoop? DadeLoop? CountyLoop? /shrug
For STEP: PermitFlow, EventFlow, something flow.

for the dashboard, we could just be straightforward and call it MDC PIC Dashboard, MDC Building Dashboard
for step, is step not good enough itself, since the acronym happens to be apt for a wizard/workflow? OD we want something more generic and less specific to special events? (or go with something about a journey/process/path/guide/sherpa/compass/tour/stream/rudder, maybe guidebook or pathway?

PGH is using Sherpa, so not that.
On Tue, Aug 18, 2015 at 3:33 PM, Mathias Gibson<EMAIL_ADDRESS>wrote:

for the dashboard, we could just be straightforward and call it MDC PIC Dashboard, MDC Building Dashboard
for step, is step not good enough itself, since the acronym happens to be apt for a wizard/workflow? OD we want something more generic and less specific to special events? (or go with something about a journey/process/path/guide/sherpa/compass/tour/stream/rudder, maybe guidebook or pathway?
Reply to this email directly or view it on GitHub:
https://github.com/codeforamerica/mdc-feedback/issues/130#issuecomment-132376305


Test added Apr 14

Added MF test
TC-MF-1.6
Modified scripts
TC-BI-1.1
TC-ETHDIAG-1.1
TC-OO-2.1
TC-PCC-2.1
TC-PCC-2.2
TC-PCC-2.3
TC-PCC-2.4
TC-WIFIDIAG-1.1
Added auto generated files
Attached execution logs for reference :
Execution_log.txt

Fast-tracking test changes.


Change xrefs GO:0043770 demethylmenaquinone methyltransferase activity and related

Cleaning up IMG: cross references #18908
@hdrabkin what do you think about merging those ? Last 3 are pz
GO:0043770 demethylmenaquinone methyltransferase activity
0 annotations wikipedia mentions EC <IP_ADDRESS>
GO:0102094 S-adenosylmethionine:2-demethylmenaquinol methyltransferase activity
0 annotations
GO:0102955 S-adenosylmethionine:2-demethylmenaquinol-7 methyltransferase activity
1 annotation IEA EC mapping
GO:0102027 S-adenosylmethionine:2-demethylquinol-8 methyltransferase activity
0 annotations
Thanks, Pascale

a quionine and quionol are different;
Also note diff substrates for 55 and 56
We had a similar type of thing a couple of weeks ago where it turns out that on quionine had to be converted to a quionol by a separate enzyme.

Cleaning up IMG: cross references #18908

Do not merge
GO:0043770 is this rhea
RHEA:26466 | a 2-demethylmenaquinone + S-adenosyl-L-methionine = a menaquinone + H(+) + S-adenosyl-L-homocysteine
GO:0102955 is this rhea
RHEA:33255 | 2-demethylmenaquinol-7 + S-adenosyl-L-methionine = H(+) + menaquinol-7 + S-adenosyl-L-homocysteine
GO:0102027 is this RHEA
RHEA:30063 | 2-demethylmenaquinol-8 + S-adenosyl-L-methionine = H(+) + menaquinol-8 + S-adenosyl-L-homocysteine
All of these map to same EC in RHEA
EC <IP_ADDRESS>

(actually that EC maps to 11 different RHEA entries based on differences in substrates.
https://www.rhea-db.org/searchresults?q=EC%3A<IP_ADDRESS>
Note that this RHEA is less specific for the -ol substrates.
THE RHEA 26466 is the more generic for the -one substrates

RHEA:42640
a 2-demethylmenaquinol + S-adenosyl-L-methionine = a menaquinol + H(+) + S-adenosyl-L-homocysteine

GO:0102094 S-adenosylmethionine:2-demethylmenaquinol methyltransferase activity
Added
RHEA:26466

OK I didn't merge, but I am not convinced those are really different activities. 3 out of the 4 terms cite the same 2 papers (PMID:1444716 and PMID:9045837), describing the the Escherichia coli ubiE gene, as if it could have slightly different substrates:
https://www.rhea-db.org/searchresults?q=<IP_ADDRESS>
Thanks, Pascale


Help(er functions?) to make easier to work with HTTPQueryParamMatch in CEL

We want to implement what is feasible with HTTPQueryParamMatch in Wasm... today you can "only" get to request.query... which is... leaving a whole lot on the CEL expression author to do on their own. Can we make this easier on them?

Maybe a good start is to expose a Map<String, String>, possibly thru request.query_params, or a helper function parseQueryParams(request.query) that'd split and url_decode the whole string? Would a Map suffice for implementing Predicates based of HTTPQueryParamMatch?

Duh! Looks like we raced for that one... see #126


[python-package] Accesing and modifying lightgbm values in model_string fails in callback.

Description

I'm not sure if I'm doing something wrong or if it's a bug. I want to change values inside the last tree built each iteration, and the only way I've found to do this is by updating the model_string (If there is another method, please advise). The problem is that when using the callback API I encounter OSError: exception: access violation reading 0x0000000000000008 when calling
-> 3557 _safe_call(_LIB.LGBM_BoosterUpdateOneIter(
   3558     self._handle,
   3559     ctypes.byref(is_finished)))

In
--> 266 booster.update(fobj=fobj)

after the first callback is done.
Reproducible example

Let's say I want to update the threshold (in the code called split_conditions, like in xgboost), by providing an array to switch inplace:

import numpy as np
from sklearn.datasets import make_regression
import lightgbm as lgb
from sklearn.metrics import mean_squared_error

X, y = make_regression(n_samples=10000, n_features=10)
dataset = lgb.Dataset(data=X, label=y, free_raw_data=False)

## Utils
from typing import List
import re

def get_split_conditions(booster: lgb.Booster, tree_idx: int) -> List[float]:
    model_str = booster.model_to_string()
    pattern = rf"Tree={tree_idx}\n.*?\nthreshold=([\-0-9. ]+)"
    match = re.search(pattern, model_str, re.DOTALL)
    if match:
        thresholds = match.group(1).split()
        thresholds = [float(val) for val in thresholds]
        return thresholds
    else:
        return None

def set_split_conditions(
    booster: lgb.Booster,
    tree_idx: int,
    split_conditions: List[float],
    copy: bool = False,
):
    model_str = booster.model_to_string(num_iteration=-1)
    pattern = rf"Tree={tree_idx}\n.*?\nthreshold=([\-0-9. ]+)"
    match = re.search(pattern, model_str, re.DOTALL)
    if match:
        old_threshold = match.group(1)
        model_str = model_str.replace(
            old_threshold, " ".join(str(val) for val in split_conditions)
        )

    if copy:
        return lgb.Booster(model_str=model_str)
    else:
        booster.model_from_string(model_str=model_str)
        return booster

def my_callback(env):
    model = env.model
    epoch = env.iteration
    n_trees = model.num_trees()

    # Print second to last tree to see if the conditions were updated
    if epoch > 0:
        print("Second to last tree", get_split_conditions(model, tree_idx=n_trees - 2))

    # Get conditions
    sc = get_split_conditions(model, tree_idx=n_trees - 1)
    # +1 to them for testing
    sc2 = [t + 1 for t in sc]

    # Print before, set them with the new ones, print after
    print("Before", sc)
    set_split_conditions(
        split_conditions=sc2, booster=model, tree_idx=n_trees - 1, copy=False
    )
    # booster.model_from_string(booster.model_to_string())  # <- If I comment the above and don't change anything this works
    print("After", get_split_conditions(booster=model, tree_idx=n_trees - 1))

params = {"metric": "mse", "max_depth": 3}
booster = lgb.train(
    params=params, num_boost_round=3, train_set=dataset,
    callbacks=[my_callback],
    keep_training_booster=True
)

Environment info
LightGBM version or commit hash: 4.0.0 (failed in previous versions too)
Command(s) you used to install LightGBM
`pip install lightgbm`

Additional Comments

If I do it in an iterative manner, things seem to work well, however I prefer to use the callback:
NUM_BOOST_ROUND = 3
for epoch in range(NUM_BOOST_ROUND):
    print("Num trees", model.num_trees())

    if epoch == 0:
        model = lgb.train(
                params=params, num_boost_round=1, train_set=dataset,
        )
    else:
        model = lgb.train(
            params=params, num_boost_round=1, train_set=dataset, init_model=model,
        )

    if epoch > 0:
        print("Second to last tree", get_split_conditions(model, tree_idx=model.num_trees() - 2))

    sc = get_split_conditions(model, tree_idx=model.num_trees() - 1)
    # +1 to them
    sc2 = [t + 1 for t in sc]

    # Print before, set them with the new ones, print after
    print("Before", sc)
    set_split_conditions(
        split_conditions=sc2, booster=model, tree_idx=model.num_trees() - 1, copy=False
    )
    print("After", get_split_conditions(booster=model, tree_idx=model.num_trees() - 1))

Add this
        booster.model_from_string(model_str="".join([line for line in x if "tree_sizes" not in line]))```
The reason is that this tree sizes key in the string somehow keeps track of the size of the file and helps parse it on load.  If it is missing, then it is not used.  But if it is there and the model string has been modified, it will die.

Unfortunately you then run into the problem of the booster's buffers being dropped when you simply build the booster from the string.  For example:

booster._Booster__is_predicted_cur_iter
[False]
Finished loading model, total used 1 iterations
booster._Booster__is_predicted_cur_iter
[]


Project w/ 2 app targets loses linked libraries to 2nd app after Xcode modification

I have a moderately complex XcodeGen set up involving multiple internal libraries/frameworks and produces multiple application targets. It works great, until you try to modify the project in Xcode (e.g. by adding a new file). Xcode then ends up stripping the libraries from all but the first application target(!)
Simplified Reproduction
I've created a simplified example project to illustrate the issue:
XcodeGenBugExample.zip

Download the .zip, use make to run xcodegen on the 3 included projects

➜  XcodeGenBugExample
 make
⚙  Generating plists...
⚙  Generating project...
⚙  Writing project...
Created project at /Users/mthole/XcodeGenTest/LibraryA/LibraryA.xcodeproj
⚙  Generating plists...
⚙  Generating project...
⚙  Writing project...
Created project at /Users/mthole/XcodeGenTest/LibraryB/LibraryB.xcodeproj
⚙  Generating plists...
⚙  Generating project...
⚙  Writing project...
Created project at /Users/mthole/XcodeGenTest/App/App.xcodeproj

Open the App.xcodeproj, and examine the App1 and App2 targets. They both link to the libLibraryA.a and libLibraryB.a libraries. All is well.

Go and add a new .swift file to the App target. (Or do a number of other Xcode operations that trigger whatever re-evaluation is happening...). I added File.swift to the App1 and App2 targets.

Examine the App1 and App2 targets. Notice that App2 is now missing both libLibraryA.a and libLibraryB.a. Sadface!

We expect App1 and App2 to still be linked to both libraries. Mysteriously, only App1 is!?
Next Steps
I've been using Xcode 12.4. If anyone has any ideas, I'm happy to help investigate further here.

This seems to be related to projectReferences. If I smash everything into a single .xcodeproj, I cannot reproduce this. (That's not a tenable workaround for my real life use case, unfortunately.)
e.g. a project defined like this behaves as expected
name: App

options:
  minimumXcodeGenVersion: 2.18
  xcodeVersion: 12.4
  deploymentTarget:
    iOS: 13.0

projectReferences:
  LibraryA:
    path: ../LibraryA/LibraryA.xcodeproj
  LibraryB:
    path: ../LibraryB/LibraryB.xcodeproj

targets:
  App1:
    type: application
    platform: iOS
    sources:
      - path: App.swift
    dependencies:
      - target: LibraryA/LibraryA
      - target: LibraryB/LibraryB
  App2:
    type: application
    platform: iOS
    sources:
      - path: App.swift
    dependencies:
      - target: LibraryA/LibraryA
      - target: LibraryB/LibraryB

Just wanted to bump this and say I've tested with XcodeGen 2.24.0, but the exact same behavior remains.

This is really problematic! Is there somewhere I can start looking to fix this.

I also want to bump this. I have a similar project structure and am seeing the same behavior described in this issue. I'm running Xcode 14.2 and Xcodegen 2.35.0.

I was able to reproduce with current latest (2.35.0) version. I'll investigate and hopefully find the root cause and create a PR.

I was able to reproduce with current latest (2.35.0) version. I'll investigate and hopefully find the root cause and create a PR.

@mthole, I am investigating a fix for this. However, I am not familiar with Xcodegen's source code -yet-.
Q: when one adds the file, isn't Xcode the one changing the pbxproj file? That is, if you rerun xcodegen, the libraries will make it back to the pbxproj file.

@mthole I am investigating this. Unfortunately, I am not familiar -yet- with Xcodegen's source code. I did try a sort of brute force approach to understanding the issue.
I performed several tests to that effect and this one stands out:

using you starter project, I generated the pbxproj file using xcodegen.
I removed and added back the two libs in BUILD PHASES' section "Link Binary with Libraries" for target APP2. I did nothing else. This resulted in Xcode modifying the pbxproj.
I added a new file. This resulted in no lost references. This tells me that something about that pbxproj is causing Xcode to not strip the libraries references.

Here is a patch that shows the changes made by Xcode in step 2.
The next step would be to identify what is wrong in the xcodegen-generated pbxproj.

@mthole since you may be familiar with the generator for this file, does anything stand out?

@mthole since you may be familiar with the generator for this file, does anything stand out?

Sorry, nothing jumps out immediately. I've lost most of the context I had here back in 2021.


Force quits but doesn't throw any useful error

After applying a simple stable-fast Unet like this

ComfyUI force quits with no apparent error except a few warnings
Using xformers attention in VAE
Working with z of shape (1, 4, 32, 32) = 4096 dimensions.
Using xformers attention in VAE
missing {'cond_stage_model.clip_l.text_projection', 'cond_stage_model.clip_l.logit_scale'}
left over keys: dict_keys(['alphas_cumprod', 'alphas_cumprod_prev', 'betas', 'log_one_minus_alphas_cumprod', 'model_ema.decay', 'model_ema.num_updates', 'posterior_log_variance_clipped', 'posterior_mean_coef1', 'posterior_mean_coef2', 'posterior_variance', 'sqrt_alphas_cumprod', 'sqrt_one_minus_alphas_cumprod', 'sqrt_recip_alphas_cumprod', 'sqrt_recipm1_alphas_cumprod', 'cond_stage_model.clip_l.transformer.text_model.embeddings.position_ids'])
triton not installed, skip
Requested to load SD1ClipModel
Loading 1 new model
Requested to load AutoencoderKL
Loading 1 new model
Requested to load BaseModel
Loading 1 new model
  0%|                                                                                | 0/30 [00:00<?, ?it/s]enable_xformers_memory_efficient_attention() is not available. If you have enabled xformers by other means, ignore this warning.
F:\automatic\venv\lib\site-packages\sfast\jit\overrides.py:21: TracerWarning: Converting a tensor to a Python number might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  return func(*args, **kwargs)
F:\automatic\venv\lib\site-packages\sfast\jit\overrides.py:21: TracerWarning: Converting a tensor to a Python list might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  return func(*args, **kwargs)
F:\automatic\venv\lib\site-packages\sfast\jit\overrides.py:21: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  return func(*args, **kwargs)
F:\automatic\venv\lib\site-packages\sfast\jit\overrides.py:21: TracerWarning: torch.tensor results are registered as constants in the trace. You can safely ignore this warning if you use this function to create tensors out of constant variables that would be the same every time you call this function. In any other case, this might cause the trace to be incorrect.

Removing stable-fast and inference works correctly
Torch 2.1.2 cu118
Windows 11
xformers installed

Same here gets stuck on Ksampler.

Have restart server to get out.