More info would be appreciated on the network changes on ASDK 1901

In the release notes it is stated "BGP and NAT components are now deployed on the physical host. This eliminates the need to have two public or corporate IP addresses for deploying the ASDK, and also simplifies deployment."
Since networking is absolute key to get a cloud working it would be appreciated if there were some more info about how this change has been implemented.
We normally set up our ASDKs as routed installations (no VPN and such) so the new 1901 installation is proving to quite the handful to get to work.. :)
(yeah, i know that our way of installation isn't the normal, or probably even supported way. But the end customers LOVE it and it makes the barrier to get them to try it SO much lower)
//Bjorn Andersson, Visolit Sweden (previously known as "TeleComputing sweden")

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

ID: 0f8368a3-49e9-5216-f7cb-f91f6f1122c1
Version Independent ID: 12092beb-efeb-974f-f9fe-5428435b228b
Content: Microsoft Azure Stack Development Kit release notes
Content Source: articles/azure-stack/asdk/asdk-release-notes.md
Service: azure-stack
GitHub Login: @sethmanheim
Microsoft Alias: sethm

@BjornAnd Sorry for leaving this open for so long. Is this still an issue? The ASDK has undergone some changes recently. If so, can you please open a new issue and @ mention me? Thanks again for your feedback. #please-close


Cannot stub Alamofire request in Mockingjay 1.2.1

Mockingjay 1.2.1 not works for Alamofire.
btw, 1.1.1 works well.

Hi @RyogaK,
Would you be able to help me debug what's causing this problem.
Please can you check that protocolClasses in NSURLSessionConfiguration inside NSURLSession returns an array of protocols with MockingjayProtocol being the first result?
If this isn't the case, perhaps you could try explicitly exchanging these methods by calling the following before anything related to NSURLSession happens:
NSURLSessionConfiguration.mockingjaySwizzleDefaultSessionConfiguration()

I can also confirm this is happening. I just spent about 3 hours trying to work out why the stubs in our unit tests were no longer working.
I'm a little busy to dig into it at the moment so have just downgraded to 1.1.1 for now but if I get time this evening I may try and dig a bit deeper and see whats happening in 1.2.1 to cause this.

I've figured out the problem. Please upgrade to version 1.2.2 which has a fix.


Interactive migrations

Durable Objects require some extra coordination on script upload. Before a Durable Object can be created, renamed, deleted, or transferred to another script, a migration must be defined. One of the reasons migrations exist is to avoid accidental data loss. For instance, let's say you upload a new version of your script and don't properly export a Durable Object class; you wouldn't want the data from that class be accidentally deleted.
While this migration mechanism is "safer," its current use in wrangler makes the experience terse. In #337, you can see that when you create a script for the first time, you get an obscure error unless you define migrations in the wrangler.toml. While, in theory, migrations don't happen that often, it's important to make this experience smoother.
If wrangler encounters a particular error(s) on upload, it knows that a migration needs to happen. Then, it should compare the list of previous class exports (from the API) with the list of current class exports (from esbuild's outputs) to determine what to do.
If it detects a class has been added, it should ask:

is this a new class?
is this an existing class that has been renamed?

if so, ask for which class is being renamed.

If it detects a class has been removed, it should ask:

are you sure you want to delete this class? and its data?

Then, it should make an "ad-hoc" migration, meaning that it does not need to update the wrangler.toml. If a user always uses wrangler in an interactive mode, they'll never need to save their migrations in a configuration.
If wrangler is running in non-interactive mode, it should error and print out the migration configuration that needs to be added; assuming that added classes are always new and deleted classes are intended to be deleted.
The new "happy path" is that wrangler detects and guides you through the migration process and you only need to edit your configuration when using wrangler in an interactive environment, like in CI/CD.

IMO initial creation is the 90% use case. Stop deprecating ad-hoc migration, make the message super clear that you just need to run --new-class.

It wasn't our decision to deprecate it. Is this messaging not true anymore?

What I am saying, and what I have said in conversations with you in the past, is that in my opinion deprecating ad-hoc migrations is a mistake. We haven't removed it, we have no concrete plans to remove it. If it makes sense to Ashcon, I think we should just remove any documentation around deprecation and make the workflow for using adhoc migrations once on initial DO creation clearer.  @xortive

Working towards an interactive experience for migrating DOs is what I'd like to see -- interactivity means this is one less thing that needs to be read in the docs to get the initial user experience right. I agree with @koeninger that we should undo the deprecation of the adhoc commands in the meantime, as that's much simpler to implement.
Improving error messaging in the API/wrangler2 is another improvement we should make, and I'm happy to help with.


[istio] pass exclude_labels and labels_mapper to istio metric instance

What does this PR do?
Allow usage of exclude_labels to reduce the number of custom metrics 1.
Motivation
reduce the number of custom metrics
Additional Notes
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

Hi! There is no need to do that. You can already pass exclude_labels, as we copy the instance object just above. It's possible we could improve documentation on that front, though.

Hi @therve

    exclude_labels:
    - destination_service

    exclude_labels:  destination_service

Both are not working as expected. Could you please help me to figure out how to exclude destination_service label?

Hey @kuzaxak! I tested exclude_labels locally and it works for me. My configuration looks like:
init_config:

instances:
  - istio_mesh_endpoint: http://localhost:15090/stats/prometheus
    exclude_labels:
      - destination_service
      - destination_service_name

Here's a sample run after
    {
      "metric": "istio.mesh.request.size.sum",
      "points": [
        [
<PHONE_NUMBER>,
          5900
        ]
      ],
      "tags": [
        "connection_security_policy:unknown",
        "destination_app:unknown",
        "destination_canonical_revision:latest",
        "destination_canonical_service:unknown",
        "destination_principal:unknown",
        "destination_service_namespace:unknown",
        "destination_version:unknown",
        "destination_workload:unknown",
        "destination_workload_namespace:unknown",
        "grpc_response_status:",
        "reporter:source",
        "request_protocol:http",
        "response_code:200",
        "response_flags:-",
        "source_app:details",
        "source_canonical_revision:v1",
        "source_canonical_service:details",
        "source_principal:unknown",
        "source_version:v1",
        "source_workload:details-v1",
        "source_workload_namespace:default"
      ],
      "host": "COMP11430.local",
      "type": "gauge",
      "interval": 0,
      "source_type_name": "System"
    }

FYI it seems that the excluded label value is an exact match. So excluding destination_service_name and destination_service did not exclude destination_service_namespace


API should accept an auth password not in query string

Feature Request
Proposal: [Description of the feature]
InfluxDB API should accept the authentication password somewhere other than in the query string.
Current behavior: [What currently happens]
Password must be passed as a query string parameter.
Desired behavior: [What you would like to happen]
InfluxDB API should accept the authentication password somewhere other than in the query string.
For example, as a basic auth header.
Use case: [Why is this important (helps with prioritizing requests)]
Query strings are often logged by any intermediate proxies. This results in the authentication password being logged in cleartext. This is bad for security.

The InfluxDB API will accept authentication with basic authentication. We don't do digest authentication, but basic authentication should be good enough with SSL. This worked for me:
$ INFLUXDB_HTTP_AUTH_ENABLED=true influxd &
$ curl -XPOST 'http://localhost:8086/query' --data-urlencode "q=CREATE USER admin WITH PASSWORD 'admin' WITH ALL PRIVILEGES"
$ curl -u admin:admin 'http://localhost:8086/query?db=_internal' --data-urlencode "q=SHOW MEASUREMENTS"

Is this working for you? Thanks.

The docs don't mention anything about this: https://docs.influxdata.com/influxdb/v1.0/concepts/api/

I opened influxdata/docs.influxdb.com#532 for us to make the documentation more explicit. The documentation kind of implies it at the beginning by saying we support HTTP authentication, but it requires too much guessing to figure out we mean basic authentication there.
Thanks! We'll have that documentation fixed up soon.


Write a Scala program to print multiplication table

Description
Write a Scala program to print multiplication table
Input  : 2

2 x 1 = 2
2 x 2 = 4
2 x 3 = 6
2 x 4 = 8
2 x 5 = 10
2 x 6 = 12
2 x 7 = 14
2 x 8 = 16
2 x 9 = 18
2 x 10 = 20

How to contribute

Save the solution in printMultiplicationTable.scala file
Add printMultiplicationTable.scala file in print-multiplication-table folder

!assign

Hey @Chirag8023,
This issue has been assigned to you for more than 15 days.
We are unassigning you from this issue.
If you are still interested in contributing to this issue, please get auto-assigned on the issue by commenting !assign again.
Thanks for your contributions :)


More Speech Bubble options

Describe the request
I really like the Speech Bubble feature, and I feel like more customization could be added. For example, an option where the bubble could be 2x shorter, or the speech bubbles could come from the bottom.
Is your feature request related to a problem? Please describe.
I often have names omitted from larger speech bubble images, which is annoying. I need to mock people.
Additional context
I love esmbot - thanks for making it!

The ability to put the speech bubble on the bottom has been implemented with 83ebe6ff0cb1ad7742aba6d9b7cafa8e67fffb07, but has yet to appear in a proper release; being able to manually scale the speech bubble is a good idea though and relatively easy to implement, so I've gone ahead and done that with 17c1b28161af0e0928bdcfc36786a15162be8447.

Thanks! Is there a planned time for the next proper release?

I really wish I could give an approximate date, but unfortunately things have still been a bit rough here in the months since 1.10.3 was released. There have been multiple major changes to the bot since then, and tracking down potential remaining bugs resulting from all of them combined with having to manage other projects, deal with responsibilities IRL, and handle other issues of my own has made it difficult to find a proper time to release.
Things are starting to look up at least a little bit, and I hope to be able to release the next version relatively soon, but with the current state of things it will still probably be a difficult task. However, I intend to change the versioning scheme with this in mind, and once this version is released I feel that things will probably lighten up a bit and that I can start to publish releases more regularly afterwards.


[e2e]: nodejs push main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6453021420
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Mon Oct  9 06:19:26 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6465463284
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Tue Oct 10 06:23:05 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6478717151
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Wed Oct 11 06:23:29 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6491987221
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Thu Oct 12 06:20:16 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6504731866
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Fri Oct 13 06:22:54 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6516017892
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Sat Oct 14 06:21:30 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6522407080
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Sun Oct 15 06:21:15 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6529760537
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Mon Oct 16 06:23:12 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6543278235
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Tue Oct 17 06:23:35 UTC 2023
Tests are passing now. Closing this issue.


$$.shouldHave(texts) method doesn't support tspans in SVG

The problem
After upgrading from 6.15.0 to 6.16.0 to benefit from the speedup of collection assertions we have encountered an issue with our existing tests that use a tspan element.
Details
When calling .shouldHave(CollectionCondition.exactTextsCaseSensitive(texts) against a collection of svg tspan elements we now get errors as tspan doesn't have an innerText attribute. Using the one by one method calling element.getText() in the past handled this fine. This appears to be due to a tspan webelement being a XML node rather than an HTML node.
This is the error thrown
Step failed
java.lang.NullPointerException: Cannot invoke "java.lang.CharSequence.length()" because "this.text" is null
	at java.base/java.util.regex.Matcher.getTextLength(Matcher.java:1769)
	at java.base/java.util.regex.Matcher.reset(Matcher.java:415)
	at java.base/java.util.regex.Matcher.<init>(Matcher.java:252)
	at java.base/java.util.regex.Pattern.matcher(Pattern.java:1134)
	at com.codeborne.selenide.impl.Html.reduceSpaces(Html.java:39)
	at com.codeborne.selenide.impl.Html.equalsCaseSensitive(Html.java:35)
	at com.codeborne.selenide.collections.ExactTextsCaseSensitive.check(ExactTextsCaseSensitive.java:22)
	at com.codeborne.selenide.collections.ExactTexts.check(ExactTexts.java:53)
	at com.codeborne.selenide.CollectionCondition.check(CollectionCondition.java:63)
	at com.codeborne.selenide.ElementsCollection.waitUntil(ElementsCollection.java:172)
	at com.codeborne.selenide.ElementsCollection.should(ElementsCollection.java:145)
	at com.codeborne.selenide.ElementsCollection.shouldHave(ElementsCollection.java:119)

Tell us about your environment

Selenide Version: 6.16.0
Chrome\Firefox\IE Version:  114.0.5735.199
Browser Driver Version:
Selenide-Appium Version:
IOS\Android\WEB version:
Selenium Version:
OS Version: Windows 10

Code To Reproduce Issue
Selenide.$$(".n2_top-distributor-chart svg .c3-axis-x tspan").shouldHave(CollectionCondition.exactTextsCaseSensitive(texts));

I also tested this by calling the following against all the tspans in my page in the Chrome dev console
Calling
Array.from(document.getElementsByTagName('tspan')).map(el => el.innerText)

results in an array full of undefined elements
Calling
Array.from(document.getElementsByTagName('tspan')).map(el => el.textContent)

results in an array of text values for the tspans.

@ben-nc2 Thank you for reporting, will fix it asap. Can you bring some example of such a site?

@asolntsev This site should enable you to run the javascript code samples I provided against it in chrome console https://vanseodesign.com/web-design/svg-text-tspan-element/

Have upgraded and all working smoothly and has brought our overall runtimes down as well which is great, thanks!

@ben-nc2 glad to read it. Thank you for the feedback @


OOM error when executing the  bash scripts/train_backward_Myx.sh

I am using  : 8 * A100 40GB

Hi there. Sorry for the late response. I run the experiment with 4*A100 40GB and didn't encounter the OOM problem. Did you apply the flash-attention?

我在本地也同样遇到oom问题，用了flash-attention，也是跑这个scripts/train_backward_Myx.sh

I also encountered this problem,I test on  4*A100 40GB, set
num_nodes=1
num_gpu_per_node=4
bsz=16
is there any problems？


Boot issue with fed39

I have installed on my internal drive fed39, trying to boot on usb, I can't boot on it. During the build setup of the usb device, I've spotted an error (see screenshot 1 bellow), when trying with uboot cmd is doesnt detect the usb device, I added the entry to grub (successfully) from my internal fed with the usb mount, when I try to boot from the grub I got this error (screenshot 2), then if I try to boot on my internal feb from the first grub entry it saw up almost the same error I need to reboot completly then I can boot on my internal

I try and test this every week or so. I really don't like installing from mkosi from main as it changes so fast. I should probably peg it to a specific commit until they cut a new release. With that said I'm not sure what your're issue it I've never seen that /run/.system-efi issue before.It looks like it's trying to mount your internal efi partition -but it can't for some reason. I'll have some time tomorrow to help you troubleshoot this further.

I just made a number or improvements. Can you try and build the drive again and let me know if it works?

All good now 😊

@leifliddy I have similar issue I think(last commit fa11840)

@1Jo1 I just built the drive and it boots fine.
The last commit was a README file edit, it wouldn't have affect the drive.
I need some more details to troubleshoot your issue:
Can you post the following output? (substitute /dev/sda with your usb device name)
[root@m1 ~]# blkid -s UUID -o value /dev/sda[1-3]
3051-D434
a1492762-3fe2-4908-a8b9-118439becd26
d747cb2a-aff1-4e47-8a33-c4d9b7475df9

If you don't see the exact output, then rebuild the drive without the -w option.
ie
./build -d /dev/sda
Are you building this on a F38 or F39 system?
Are you building this on an aarch64 system or a x86_64 system
What version of mkosi are you using (should be v19)?
Can you post the output of these commands (on the system that you're building the drive with)?
[root@m1 ~]# which mkosi
/usr/bin/mkosi

[root@m1 ~]# mkosi --version
mkosi 19

How are you booting the drive? via u-boot cmds or via (internal) grub?

fedora@jo ~]# blkid -s UUID -o value /dev/sda[1-3]

I dont see any output...even when try ./build -d /dev/sda
I'm using F39 aarch64 (M2 Pro), I'm gonna try to build it on x86_64 when I'm at home
[fedora@jo ~]# which mkosi
/usr/bin/mkosi

[fedora@jo ~]# mkosi --version
mkosi 19

first I tried via u-boot but didnt detect my usb drive, so I tried that via (internal) grub

Do you see your usb device in the lsblk output?
[root@m1 ~]# lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    1  59.8G  0 disk
├─sda1        8:1    1   600M  0 part
├─sda2        8:2    1     1G  0 part
└─sda3        8:3    1  58.2G  0 part

https://gist.github.com/1Jo1/2e4f70fc20a3d982ae1cfb3a304a6ed6 here the logs
fedora@joasahi-fedora-usb   main lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    1  14.4G  0 disk
├─sda1        8:1    1   600M  0 part
├─sda2        8:2    1     1G  0 part
└─sda3        8:3    1  12.8G  0 part

same output

are you running ./build -d /dev/sda as root?
I should probably enforce that in the script....
Can you post the full blkid | grep /dev/sda output?

are you running ./build -d /dev/sda as root? I should probably enforce that in the script....
no as sudo I will try that as root now
Can you post the full blkid | grep /dev/sda output?
sorry my bad just noticed I forgot the sudo fedora@jo ~]# blkid -s UUID -o value /dev/sda[1-3]

fedora@jo~ sudo blkid | grep /dev/sda
/dev/sda2: LABEL="fedora-usb-boot" UUID="a1492762-3fe2-4908-a8b9-118439becd26" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="1aba7cb0-1e28-4ea4-9816-d447dd3e07a0"
/dev/sda3: LABEL="fedora-usb-root" UUID="d747cb2a-aff1-4e47-8a33-c4d9b7475df9" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="43560be4-00b5-4d35-8a5f-371ac75dbd49"
/dev/sda1: LABEL_FATBOOT="EFI-USB-FED" LABEL="EFI-USB-FED" UUID="3051-D434" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="065b647a-4e8d-40e8-89e5-51a68561b77d"

Running scripts that contain tons of privileged commands is a PITA to get to run with sudo. Because unlike a binary file, each individual privileged command within a script needs to be prefix with sudo.
Ok, I'll add the logic to the script now to ensure users are running it as root.....

Running scripts that contain tons of privileged commands is a PITA to get to run with sudo. Because unlike a binary file, each individual privileged command within a script needs to be prefix with sudo.
Ok, I'll add the logic to the script now to ensure users are running it as root.....

true that make sense, I just built the script as root, still the same issue...I will try different usb stick just be safe haha

Try running these command in the uboot shell/prompt
usb reset
usb info
usb storage

Does it see your usb device?

so weird...no storage device

What model/system is this? A mac mini?

Odd, I'm seeing the same issue with my usb drive. I normally just boot from it via the main grub menu (see readme file for more info on that). It's odd that it's not seeing the device from uboot. Maybe something changed with that last uboot update or maybe it's just flaky.

What model/system is this? A mac mini?

macbook pro 14 inch 2023

What!? I can't boot boot it from grub either....one sec. I'm going to reinstall this drive....

Odd, I'm seeing the same issue with my usb drive. I normally just boot from it via the main grub menu (see readme file for more info on that). It's odd that it's not seeing the device from uboot. Maybe something changed with that last uboot update or maybe it's just flaky.

I'm using a usb c/usb a adapter for my usb stick, is that the reason maybe?

No, I'm using the same adapter.

What!? I can't boot it from grub either....one sec. I'm going to reinstall this drive....

interesting, you didnt change much last month, so its probably one of the packages on f39 which causes this issue I guess?

Something odd is happening, it was working fine this morning. I've upgrade a few packages since then. Not sure if that's the cause or not. I need some time to test a few things out and to communicate with the asahi devs as well.....

See if you can join this channel
https://app.element.io/#/room/#asahi:fedoraproject.org
I sorted out the issue....well sort of. The issue is  either with the latest kernel or with m1n1.
If you cd to /boot/efi/m1n1 and rename boot.bin.old to boot.bin it should work.
backup the original boot.bin just in case. Discussing this issue with the devs now....

See if you can join this channel https://app.element.io/#/room/#asahi:fedoraproject.org
I sorted out the issue....well sort of. The issue is either with the latest kernel or with m1n1. If you cd to /boot/efi/m1n1 and rename boot.bin.old to boot.bin it should work. backup the original boot.bin just in case. Discussing this issue with the devs now....

I tried to rename boot.bin.old, but it didnt work, the file size boot.bin.old is the same as boot.bin as I installed fresh fedora asahi linux few hours ago

Can you try this.
Remove the current version of m1n1 with rpm -e --nodeps m1n1
Then install the older version of m1n1
rpm -ivh https://leifliddy.com/asahi-linux/39/aarch64/m1n1-1.4.8-1.fc39.aarch64.rpm
then run update-m1n1 and see if that works.

Can you try this? Remove the current version of m1n1 with rpm -e --nodeps m1n1 Then install the older version of m1n1 rpm -ivh https://leifliddy.com/asahi-linux/39/aarch64/m1n1-1.4.8-1.fc39.aarch64.rpm then run update-m1n1 and see if that works.

it didn't work, I reinstall it via build.sh -d /dev/sda, my usb stick is still missing in u-boot and via grub is the same error

Thanks for trying. I'm sure this will get sorted out. I'll ask marcan to look into this....

This user was having the same issue
https://github.com/leifliddy/asahi-fedora-builder/issues/30
This commit should fix the issue
https://github.com/AsahiLinux/m1n1/commit/90eef7223e5da9bdc7ad7f823e7748326ba862d2
m1n1-1.4.11 should be released soon.

Thanks!
I'm gonna try it later
BTW I can't build anymore as root, I think its this commit https://github.com/leifliddy/asahi-fedora-usb/commit/51a32177777b8cd6f0b856317debc8bc8ed00362

That was a typo, I should have enclosed those conditional statements with parenthesis.
I just pushed out a new change. Can you try again?

It should be good now, can you please try and send me your feedback?

I'm sorry I was in vacation the last two weeks, couldn't test it...had only my thinkpad...
I tried multiple times, it seems that on my M2 Pro the usb device in uboot doesn't show up at all, never did...I tried with a M1 that works perfectly with the same usb device
both have the same m1n1, kernel and uboot version(newest version all)


Right-clicking the script or visibility icons in the editor's scene tree will erroneously give them a "selected" appearance

Godot version: Git https://github.com/godotengine/godot/commit/2d0c07bd5ab363997a210f98fb14d638414dea1a
OS/device including version: Fedora 27
Issue description: Right-clicking the script or visibility icons in the editor's scene tree will erroneously give them a "selected" appearance. This is a purely cosmetic issue; the "selected" appearance disappears if one left-clicks anywhere else in the scene tree panel. See below for screenshots.
Normal selection:

"Fake" selection of the script button (with an unselected node):

"Fake" selection of the script button (with a selected node):

Steps to reproduce: Right-click a script or visibility icon in the editor's scene tree.

Also reproducible with 9f590b460ee8f6e0026b14fbc336b7b7ad977ee0 on Windows 10 x64.
As I think the reason is that there is no difference between LBM and RMB in general (only specific logic for Left/Right click later):
https://github.com/godotengine/godot/blob/d5eba83fd57005c110ef594f90c84016b758a0d5/scene/gui/tree.cpp#L2566-L2568
Then there is a propagate_mouse_event call:
https://github.com/godotengine/godot/blob/d5eba83fd57005c110ef594f90c84016b758a0d5/scene/gui/tree.cpp#L2607
, which 'selects' script/visibility icon.
https://github.com/godotengine/godot/blob/d5eba83fd57005c110ef594f90c84016b758a0d5/scene/gui/tree.cpp#L1707-L1714
Don't know what to do next yet.

I can still reproduce this issue in Godot 3.2.1.

Still exists in Godot 3.4 stable.

No longer exists in 4.3.


(WIP) Add Editable form components

(WIP) Added examples for Editable form using:

contenteditable
<textarea>

@noteed I've added variants with <textarea> and bottom button. The downside of using <textarea> is that the height of the text area does not auto adjust based on the content in it. You'll need to write some javascript in order to adjust the height automatically.

This looks nice, thanks !


about import pytextbelt

I want use pytextbelt, but try to runing python ./cli-sms.py xxx xxx report errors ImportError: No module named pytextbelt, so i try from pytextbelt.pytextbelt import Textbelt, still error.
I try to modify pip packages /pytextbelt/__init__.py
import requests from pytextbelt.pytextbelt import Textbelt
to
import requests from pytextbelt import Textbelt
, it's success.

textbelt lib is not available in the pypi repository. You should manually include the textbelt module in your working directory to make access easier and then import directly.


User already exists when registering using InnoDB

I'm trying to get the login library to work with InnoDB by following this: https://github.com/delight-im/PHP-Auth/issues/137
I changed users.email and users_confirmations.email to varchar(191) but I get a message saying "user already exists" when I attempt to register. Is there anything else I have to do that I missed? I'm still kinda new to using this library so I'm not all too familiar with how it works.

Are you using Auth#register or Auth#registerWithUniqueUsername?
Can you check in your database table users that there is indeed no user with the specified email address (and username)?
Apart from that, in your project directory, you could open vendor/delight-im/auth/src/UserManager.php, and in protected function createUserInternal, inside of catch (IntegrityConstraintViolationException $e) {}, log the full exception with all details and look at it.

Are you using Auth#register or Auth#registerWithUniqueUsername?
Can you check in your database table users that there is indeed no user with the specified email address (and username)?
Apart from that, in your project directory, you could open vendor/delight-im/auth/src/UserManager.php, and in protected function createUserInternal, inside of catch (IntegrityConstraintViolationException $e) {}, log the full exception with all details and look at it.

Whoops, I see what I overlooked now. I was so used to using MyISAM without the foreign key constraints that I forgot I had made a foreign key that wasn't being filled upon user creation. I fixed that up with a default value. Sorry about that! A silly oversight on my part.

No problem, thanks!


guidance - ECS Fargate + CodeDeploy changes in target groups

Hello, I would like a guidance on how to proceed using this ALB module on how to handle changes made by CodeDeploy during a Blue/Green deployment for an ECS Fargate service.
Initially ECS Fargate uses 2 target groups with different weights, usually one with 100% of traffic and other with 0%. Lets call them tg-a and tg-b respectivelly. When CodeDeploy starts a new deploy for this service it creates tasks on tg-b, increases its traffic to 100% and finally removes tg-a.
This creates a configuration drift when we run terraform again, lets says to create new rules.
Is there a way in this module to ignore target group, and rule, changes made by CodeDeploy?
Thanks for your amazing work in this module!

I have having the same issue. Decoupling IaC from CICD must be a common use-case.

+1 for this feature
I came in here looking for the same thing and found this helpful workaround posted in a similar closed issue: https://github.com/terraform-aws-modules/terraform-aws-alb/issues/219#issuecomment-1229595014
I created my target groups and listener outside of the module and it seems to be working. after a blue/green deploy, terraform plan does not show any changes

please open an issue here https://github.com/aws-ia/ecs-blueprints

+1


Dark Mode - Seed backup for LTC wallet not showing seed words

A small problem I had in dark mode.

I am unable to replicate this issue please include screenshots.
Wallet type-LTC-

Seed words-

Ok I just retried and they showed up in dark mode, not sure what happened yesterday.


Allow datatable row to wrap text demanded by ft.Text

windows 10
ft.DataCell(ft.Text(x['Item'],width=170)),
If you are reporting a new issue, make sure that we do not have any duplicates
already open. You can ensure this by searching the issue list for this
repository. If there is a duplicate, please close your issue and add a comment
to the existing issue instead.

GENERAL SUPPORT INFORMATION
The GitHub issue tracker is for bug reports and feature requests.
General support can be found at the following locations:

Flet discussions - https://github.com/flet-dev/flet/discussions
Flet Discord server - https://discord.gg/dzWXP8SHG8
Post a question on StackOverflow, using "flet" tag
-->

Please Describe The Problem To Be Solved
(Replace This Text: Please present a concise description of the problem to be addressed by this feature request. Please be clear what parts of the problem are considered to be in-scope and out-of-scope.)
(Optional): Suggest A Solution
(Replace This Text: A concise description of your preferred solution. Things to address include:

Details of the technical implementation, e.g. Flutter widget solving the problem.
Tradeoffs made in design decisions
Caveats and considerations for the future

If there are multiple solutions, please present each one separately. Save comparisons for the very end.)

Could you be more specific please?

sometimes the column width is not sufficient to accommodate all the text. So the text has to be indented. Datatable rows/datacell has only two lines to indent the text...

Open a new issue, using the new issue-template, and provide all possible informations.


Link ideologies conversation with "sociotechnical imaginaries" concept?

https://github.com/pluralitybook/plurality/blob/2d782e808a8bb0388e27a5fd8cf4a831ef533f71/contents/english/2-0-information-technology-and-democracy-a-widening-gulf.md?plain=1#L174
Wondering if it could be useful to link this discussion with the STS concept of "sociotechnical imaginaries" from Jasanoff:

[sociotechnical imaginaries are] collectively held, institutionally stabilized, and publicly performed visions of desirable futures, animated by shared understandings of forms of social life and social order attainable through, and supportive of, advances in science and technology

From:
Jasanoff, S. (2015). Future imperfect: Science, technology, and the imaginations of modernity. Dreamscapes of modernity: Sociotechnical imaginaries and the fabrication of power, 1-33.
Referenced this in my previous comments here as well.

Another potentially useful reference might be Barbrook & Cameron's "The Californian Ideology" (wiki; link) which I guess I'd position as an earlier articulation & critique of the 90s version of techno-libertarian ideology in SV?

Great idea, I'll fund this a bit and feel free to submit a PR actioning it.

 Gov4Git notices
On Sunday, 28-Apr-24 19:32:19 UTC by Gov4Git dev
Notice qk2mna
Started managing this issue, using the Plural Management Protocol v1,  as Gov4Git concern 904 with initial priority score of 0.000000.
This project is managed by Gov4Git, a decentralized governance system for collaborative git projects.
To participate in governance, install the Gov4Git desktop app.
Notice zxadmr
This issue's priority score is now 0.000000.
The cost of priority is 0.000000.
The projected bounty is now 0.000000.
Notice reqdxz
The set of eligible proposals claiming this issue is empty.

 Gov4Git notices
On Thursday, 01-Aug-24 18:50:15 UTC by Gov4Git dev
Notice shlb44
This issue's priority score is now 16.000000.
The cost of priority is 16.000000.
The projected bounty is now 16.000000.
Notice xw4ezi
The set of eligible proposals claiming this issue is empty.


fix styles server rendering

It was joining the styles by comma, instead of empty strings!

@buzinas Can you add tests for this functionality to avoid regression?


Hold sphinx version back to fix search in our custom theme

We'll see in the preview deployment whether this fixes search.

Confirmed that search works on this preview, and does not work on a preview of another of the open pull requests.


Remove one "impossible" error

fixes #5745

@KevinRansom is something wrong with master? the error for linux build seems unrelated

@forki not that I know.  The error is:
2018-10-09T12:23:11.3515703Z   /home/vsts/work/1/s/src/scripts/scriptlib.fsx(65,25): error FS0041: A unique overload for method 'GetFileName' could not be determined based on type information prior to this program point. A type annotation may be needed. Candidates: Path.GetFileName(path: ReadOnlySpan<char>) : ReadOnlySpan<char>, Path.GetFileName(path: string) : string [/home/vsts/work/1/s/tests/FSharp.Core.UnitTests/FSharp.Core.UnitTests.fsproj]
2018-10-09T12:23:11.3517355Z   /home/vsts/work/1/s/src/FSharpSource.targets(208,5): error MSB3073: The command "mono /home/vsts/work/1/s/packages/FSharp.Compiler.Tools.4.1.27/tools/fsi.exe --exec "/home/vsts/work/1/s/src/scripts/subst.fsx" --in:"/home/vsts/work/1/s/tests/FSharp.Core.UnitTests/FSharp.Core.UnitTests.dll.config" --out:"/home/vsts/work/1/s/tests/FSharp.Core.UnitTests/../../src/../release/net40/bin/FSharp.Core.UnitTests.dll.config" --pattern1:"FSCoreVersion" --replacement1:"<IP_ADDRESS>" --pattern2:"" --replacement2:"" " exited with code 1. [/home/vsts/work/1/s/tests/FSharp.Core.UnitTests/FSharp.Core.UnitTests.fsproj]
2018-10-09T12:23:11.3517711Z
2

At this point I believe the script is running the built compiler, so I suppose there is some possibility they are related.

@KevinRansom #5733 also has this error but with no compiler, so something's wrong in the mono FCS build.

@cartermp indeed it does.

it's noew green after rebase


[BETA] Can't Add New Integration via Cookie Auth

The problem
When I try to add the integration via Field Test login, I get this and cannot continue:

What version of this integration (ha-nest-protect) has the issue?
v0.4.0b4
What version of Home Assistant Core has the issue?
2023.12.4
Device / Model
Nest Protect (Wired)
Diagnostics information
No response
Home Assistant log
Logs
2023-12-27 18:33:55.484 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration nest_protect which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-12-27 18:35:59.771 ERROR (MainThread) [custom_components.nest_protect.pynest] Authentication error: invalid_request
2023-12-27 18:35:59.772 ERROR (MainThread) [custom_components.nest_protect] 400 error while authenticating - {"error":"invalid_request","error_description":"missing user credentials","instance_id":"98732789-6fbc-4978-904b-9ab7734420c2"}. Please create an issue on GitHub.
Traceback (most recent call last):
  File "/config/custom_components/nest_protect/pynest/client.py", line 217, in authenticate
    self.nest_session = NestResponse(**nest_response)
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: NestResponse.__init__() got an unexpected keyword argument 'error_description'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/nest_protect/config_flow.py", line 103, in async_step_account_link
    [issue_token, cookies, user] = await self.async_validate_input(
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/nest_protect/config_flow.py", line 63, in async_validate_input
    response = await client.authenticate(auth.access_token)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/nest_protect/pynest/client.py", line 224, in authenticate
    raise PynestException(
custom_components.nest_protect.pynest.exceptions.PynestException: 400 error while authenticating - {"error":"invalid_request","error_description":"missing user credentials","instance_id":"98732789-6fbc-4978-904b-9ab7734420c2"}. Please create an issue on GitHub.

Additional information
No response

I'm not entirely sure what Field Test means, but that was the issue.
Don't use Field Test unless you know what you're doing I guess.

I will see if we can improve the description for environment, but this error should be different as well. Let me have a look.

Hi, I also tested this method but I don't get issuetoken when I log in. I find that the cookie.
It's a shame to have so much difficulty installing such security equipment in our home automation.

Hi, following my message I managed to integrate my Nest protect, thank you for this version. I did not check Preserve Log.

Any news about this ?  There is another way to integrate it ?

I had no problem integrating it with the beta version.

I had no problem integrating it with the beta version.

Oh where is the beta version ?

Install via HACS:

Open the integration in HACS and click the three dots

Click Redownload
Enable show beta downloads and download the latest beta release

I got the same error using I think the latest beta verison 0.4.0b8
regardless it seem to have worked/authenticated since the data is updating again and showing on the dashboard.
Btw. it would help to have the info about issueToken/oauth2/iframe displayed right in the login dialogue rather than only linking to the readme, to save time, as after a HA reboot it needs to be done again and again. =)


[T3A4][W10-A1]Karen Ang

Accepting this PR without a review because another of your PRs for this tutorial was reviewed in detail.


cadCAD reserve rebalancing

Automated & Systematic Rebalancing comparison in cadCAD

Rule-based for target intervals
Balancer liker with circuit breaker & fee experimentation
CGP62

Not relevant for now, closing


Bootstrap sample class from official documentation not working with zf2 2.5

Hello,
The sample Bootstrap class in the [official documentation] (http://framework.zend.com/manual/current/en/tutorials/unittesting.html#bootstrapping-your-tests) is not working after the 2.5 version.
I have updated my Bootstrap class in order to have my tests running with zf2 2.5. I can provide a diff if necessary.
May Thanks for your work!

This repository is for bugs in ZF2 itself. Please open an issue in the documentation repository: https://github.com/zendframework/zf2-documentation


Line numbers seem to accumulate across files

Here's an invocation of pandaPIparser that encountered a parse error in its problem file:
pandaPIparser domain.hddl p01.hddl
pandaPIparser is configured as follows
  Colors in output: true
  Mode: parsing mode
  Parameter splitting: true
  Conditional effects: exponential encoding
  Disjunctive preconditions as HTN: false
  Replace goal with action: false
  Output: pandaPI format
!Parse error in file p01.hddl in line 235
unexpected KEY_ORDER_TASKS

The entire file p01.hddl is only 27 lines long.  However domain.hddl is 208 lines long.  So I conjecture that the line counter is not reset when pandaPIparser closes domain.hddl and opens p01.hddl.

Yup. I've fixes this issue with commit 1613b83. Your conjecture was fully correct - I did not reset the line number counter of flex. Now we are fully de-initialising flex after the first file has been parsed. This should also remove any potential other problem related to not resetting it correctly.


[GHSA-cwvm-v4w8-q58c] Blind local file inclusion

Updates

Affected products
CVSS
CWEs

Comments

CWE added
CVSS assessment was fixed.

Hi there @stsewd and @Byron! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our highly-trained Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

Wasn't sure about the attack vector being network or local, since it depends on how gitpython is being used, but if you think that's more accurate, I'm :+1:

stsewd

Hello! Thanks for replying. Generally, gitpython package is not exposed on the network level, so that's why I changed the CVSS assessment in this way.

A new version of gitpython was release, but doesn't have a fix for this CVE, the last affected version should be updated to be 3.1.33


dm: tracker panic when pk of downstream table orders behind

What did you do?
to reproduce

downstream create table before sync or the table has no pk on create then add multiple pk later.
tracker will panic when downstream table ddl has, but even if the ddl doesn't satisfy all condition, dm may use the wrong key:

multiple normal index before pk
multiple uk/pk
number of normal index >= number of uk/pk

such as downstream create table below before sync:
create table t(
    a int not null,
    b int not null,
    c int not null,
    d int not null,
    e int not null,
    index (a),
    index(b),
    index(c),
    unique(d),
    unique(e)
);

or add pk after create table in upstream:
create database test;
use test;
create table t(
    a int not null,
    b int not null,
    c int not null,
    d int not null,
    e int not null,
    index (a),
    index(b),
    index(c)
);

alter table t add unique(d);
alter table t add unique(e);
show create table t;
insert into t values(1,1,1,1,1);

code panics since absoluteUKPosition  comes from all indices but index into uk/pk arr:
https://github.com/pingcap/tiflow/blob/2605a84c09587f57f87cfc088e66a769033dcad5/dm/pkg/schema/tracker.go#L569
"Message": "panic error: runtime error: index out of range [3] with length 2",

What did you expect to see?
works
What did you see instead?
panic
Versions of the cluster
occurs in 5.3, reproduced on 5.4/6.0
current status of DM cluster (execute query-status <task-name> in dmctl)
(paste current status of DM cluster here)

closed by #5167


Fix NavBar prevents swipe back on Android

#1134 issuse

@aksonov Can we get a merge on this? Works well for me!

I'm really sorry about missing this PR. Unfortunately I have available time only recently and completed v4 beta based on React Navigation. Feel free to submit PRs for v4 now. I promise I will not miss them again.


Safari [Error] SyntaxError: Can't create duplicate variable: 'typeMap'

Hi,
I'm getting an error in Safari
[Error] SyntaxError: Can't create duplicate variable: 'typeMap'
	write
	(anonymous function)
	promiseReactionJob

Tried minified and non-minified versions of the JS. Doesn't happen in other browsers.
Specifications:

1.0.0 Alpha 9 (but was happening on a 0.5.0 alpha before)
Safari Version 11.0.3 (13604.5.6)
MacOS High Sierra

Happening for me too in the same environment.

I can confirm that disabling AdBlock stops this error happening. Is there any way to work around this without completely disabling AdBlock?
Thanks.


TypeScript: widgets from ds-material are not assignable to UIGenerator.widgets

Current Behavior
I want to use UI-Schema with TypeScript. I get a TypeScript error when trying to assign widgets to UIGenerator.
Steps to Reproduce
Steps:

Use Typescript
import {widgets} from "@ui-schema/ds-material";
<UIGenerator widgets={widgets} />

Context
Type 'MuiWidgetBinding & { [key: string]: ComponentType<{}>; }' is not assignable to type 'WidgetsBindingBase & { [key: string]: ComponentType<{}>; }'.
  Type 'MuiWidgetBinding & { [key: string]: ComponentType<{}>; }' is not assignable to type 'WidgetsBindingBase'.
    Types of property 'types' are incompatible.
      Type '{ string: ComponentType<WidgetProps>; boolean: ComponentType<WidgetProps>; number: ComponentType<WidgetProps>; integer: ComponentType<...>; }' is not assignable to type '{ [key: string]: ComponentType<{}>; }'.
        Property 'string' is incompatible with index signature.
          Type 'ComponentType<WidgetProps>' is not assignable to type 'ComponentType<{}>'.
            Type 'ComponentClass<WidgetProps, any>' is not assignable to type 'ComponentType<{}>'.
              Type 'ComponentClass<WidgetProps, any>' is not assignable to type 'ComponentClass<{}, any>'.
                Types of property 'getDerivedStateFromProps' are incompatible.
                  Type 'GetDerivedStateFromProps<WidgetProps, any> | undefined' is not assignable to type 'GetDerivedStateFromProps<{}, any> | undefined'.
                    Type 'GetDerivedStateFromProps<WidgetProps, any>' is not assignable to type 'GetDerivedStateFromProps<{}, any>'.
                      Types of parameters 'nextProps' and 'nextProps' are incompatible.
                        Type 'Readonly<{}>' is missing the following properties from type 'Readonly<WidgetProps>': onChange, schema, parentSchema, level, and 8 more. TS2322

UIStore.d.ts(50, 5): The expected type comes from property 'widgets' which is declared here on type 'IntrinsicAttributes & UIMetaContext & UIStoreContext & { children?: ReactNode; }'

Your Environment

Tech
Version

UI-Schema
v0.2.0-rc.2

Immutable
v4.0.0-rc.12

-
-

DS-Material
0.2.1

Material-UI
4.11.3

I think the bug is here:
export interface UIMetaContext<> {
    widgets: WidgetsBindingBase & {
        // allow adding any further custom root components
        [key: string]: React.ComponentType
    }
    t?: Translator
    showValidity?: boolean
}

When I changed WidgetsBindingBase to MuiWidgetBinding, I got my code working, but of course it's not a solution.

Hey inexcode!
i've discovered also some problems with those typing, changed the widgetsBinding in develop already, next release should be this weekend. The typings of MuiWidgetsBinding and WidgetsBindingBase are now compatible and more extensible in general.
But thanks for the hint, will remove the now unnecessary (and wrong) typing in UIMetaContext.

Fixed & released in @ui-schema/ui-schema v0.2.0-rc.3 and @ui-schema/ds-material v0.2.2


chore: release 1.2.291

:robot: I have created a release *beep* *boop*
1.2.291 (2024-02-15)
Bug Fixes

build: image metadata publication when git history based policy disabled (11850a8)
bundle: support for --insecure-registry/--skip-tls-verify-registry options (96123cb)
cleanup: git unshallow and sync with remote when git history based policy disabled (d1078a0)
cleanup: image metadata cleanup when git history based policy disabled (3a709ea)
nelm: cycle error if pre+post hook in release (8c40fdb)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/werf/werf/releases/tag/v1.2.291 :sunflower:


PYIC-7571: Fetch all CRI by issuer once

Proposed changes
What changed
Fetch all CRI by issuer once
Why did it change
When running the reconciliation lambda in parallel (more than one lambda execution at once), we were seeing SSM rate limiting errors from powertools. This is weird because it would appear that it's not always respecting the cache.
To avoid this issue this create a new method on the config service which will create a map of all configured issuers for the env to allow a lookup of the associated CRI. We then use this to populate a map for the script which it can refer to throughout the duration of its running.
I've run four parallel exections of this script with this change and experienced no issues. This allowed the checking of the signatures for 100000 identities in less than two minutes.
Issue tracking

PYIC-7571

This is a bit strange - I've also seen some issues confirming powertools caching behaviour when messing about with the TS lambda, but 🤷

I sort of assumed this was because we were pulling using a path prefix - but I've just seen it happen again but for dead normal param. And about 20 seconds after a lambda started. Which sort of makes me thing it's not caching properly at all...


Rerunning playbook halts due to hdfs put.

The playbook for AWS fails to rerun due to a hdfs put throwing “File exists” errors. Not seeing a hdfs put with override capabilities, so using the “ignore_errors” flag pattern seen elsewhere just so the playbook will complete on subsequent runs...

(Other than that, due to having to restart the playbook a couple of times, I was able to get an AWS environment up and running with one command -- which is awesome!)

Thanks for the contribution.  Will verify shortly

Good catch! Thanks for the PR.
Lately, I'm a little reluctant to add ignore_errors without a fail block immediately following. In this case, you could add a register: result to the Upload grok patterns task followed by a fail task that fails if "File exists" isn't in stdout. That would make sure it didn't ignore different types of errors.
Since we're interacting with hdfs immediately prior to the file copy, I think ignore_errors would be okay here, but if you had the time to add the fail block, it would be preferred. It demonstrates the preferred pattern and gives others a better example to follow.
What do you think?

Sounds like a plan @dlyle65535! So, based on what you were saying about the register and the fail block, I found this guy...
http://docs.ansible.com/ansible/playbooks_error_handling.html#controlling-what-defines-failure
Looks like the "ignore_errors + register + the separate fail block w/ the explicit message" pattern can be collapsed into a "register + failed_when" pattern, so something like this maybe...
register: put_result
failed_when: "put_result | failed and 'File exists' not in put_result.stderr"

And then in a completely different direction, looks like the "copyFromLocal" (instead of the put) command supports the force (-f) flag... which would just overwrite the destination without throwing an error.
So thoughts on which you'd prefer...

Separate Fail Block w/ Messaging.
Failed_when that will do a normal fail if it's not a fail exists issue
Use a copyFromLocal w/ the override flag (instead of the put)

From my perspective, #3 would be a good approach. If you have a different opinion, I'm happy to support it.
Thanks for digging into it!

In some of my own branches I had been using hdfs dfs -put -f ... successfully.  I'd recommend that.  I don't really understand the difference between that and copyFromLocal, but either should probably work.
https://github.com/nickwallen/incubator-metron/blob/METRON-80/deployment/roles/metron_streaming/tasks/grok_upload.yml

Nice @nickwallen! Just verified the -f on the -put totally works. And for fun, I looked at the hadoop code and you can see the -copyFromLocal is just an alias for put now...
  public static class CopyFromLocal extends Put {
    public static final String NAME = "copyFromLocal";
    public static final String USAGE = Put.USAGE;
    public static final String DESCRIPTION = "Identical to the -put command.";
  }

And the -put supports all kinds of nice undocumented flags...
  public static class Put extends CommandWithDestination {
    public static final String NAME = "put";
    public static final String USAGE =
        "[-f] [-p] [-l] [-d] <localsrc> ... <dst>";
    public static final String DESCRIPTION =
      "Copy files from the local file system " +
      "into fs. Copying fails if the file already " +
      "exists, unless the -f flag is given.\n" +
      "Flags:\n" +
      "  -p : Preserves access and modification times, ownership and the mode.\n" +
      "  -f : Overwrites the destination if it already exists.\n" +
      "  -l : Allow DataNode to lazily persist the file to disk. Forces\n" +
      "       replication factor of 1. This flag will result in reduced\n" +
      "       durability. Use with care.\n" +
        "  -d : Skip creation of temporary file(<dst>._COPYING_).\n";

I've updated this PR to use the -f instead of the ignore_errors, but it looks like Nick already has the fix in his other branch. Up to you guys on if you want to close this and/or wait for the other commit to make its way over.

No, please go ahead with your fix.  Thanks for all the research.

+1 Thank you for your contribution!
I've opened METRON-89: Rerunning playbook halts due to hdfs.


Hampshire (County of Southampton), UK

Hampshire (County of Southampton) - This was changed in 1959. The correct name is just "Hampshire"
Can "(County of Southampton)" be removed?

Haha, 1959, eh...? Maybe a little dated. I've created the following ticket to update the data set:
https://github.com/country-regions/country-region-data/issues/38


google chrome install

Gets Google chrome to install on travis-ci.org

@bmcculley great! Thank you again. I see on the builds that there are some stuff that we need to fix on tests, but it's very good to have builds going again.


krabby: 0.2.0 -> 0.2.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/yannjor/krabby/releases.
meta.description for krabby is: Print pokemon sprites in your terminal
meta.homepage for krabby is: https://github.com/yannjor/krabby
meta.changelog for krabby is: https://github.com/yannjor/krabby/releases/tag/v0.2.1
Updates performed

Rust version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.2.1 with grep in /nix/store/hh2jh3s48qp8nqap834yzk90rqarhfak-krabby-0.2.1
found 0.2.1 in filename of file in /nix/store/hh2jh3s48qp8nqap834yzk90rqarhfak-krabby-0.2.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

krabby

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hh2jh3s48qp8nqap834yzk90rqarhfak-krabby-0.2.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A krabby https://github.com/r-ryantm/nixpkgs/archive/8f55df5aa879967e9c7f2331e2d8bb5c3da86f01.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/8f55df5aa879967e9c7f2331e2d8bb5c3da86f01#krabby

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hh2jh3s48qp8nqap834yzk90rqarhfak-krabby-0.2.1
ls -la /nix/store/hh2jh3s48qp8nqap834yzk90rqarhfak-krabby-0.2.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

krabby

Maintainer pings
cc @ruby0b for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 354812

x86_64-linux

:white_check_mark: 1 package built:

krabby

aarch64-linux

:white_check_mark: 1 package built:

krabby

aarch64-darwin

:white_check_mark: 1 package built:

krabby


Global Settings: Branding: Private Label: User must reload the page to see the updated title in the browser tab

Setup

Rancher version: v2.7.5
Dashboard version: v2.7.5
Browser type & version: Any

Describe the bug
After updating the 'Private Label' in Branding, the user must reload the page to see the updated title in the browser tab.
To Reproduce

login to Rancher UI as an admin/standard user
go to Global Settings -> Branding (/dashboard/c/local/settings/brand)
update Private Label text (e.g. 'Rancher-e2e')
click 'Apply'
check title in the browser tab (this test passes - title updated)
revert the Private Label text to its original state  (e.g. 'Rancher')
click 'Apply'
check title in the browser tab (this test fails - title not updated)

Result
The user sees the updated title in the browser tag after page reload.
Expected Result
The user should see the updated title in the browser tag in session.
Screenshots

https://github.com/rancher/dashboard/assets/127343932/40b4aec6-9f79-4964-8480-e29603af1228

This may be prioritized if we address other flaky tests first.

@yonasberhe23 I don't see this anymore - can you close this, if this is no longer an issue.

@nwmac I'm also, unable to repo it. I'll close it. thanks!


Exclude folder of selected folder.

How to exclude a specific folder from being included in the project specified?
    Template(Settings settings)
    {
        settings.IncludeProject("Soft.Data");
        settings.OutputFilenameFactory = file =>
        {
            return $"{file.Name.Replace("ViewModel", "GenViewModel").Replace(".cs", ".ts")}";
        };
    }

Answered given on StackOverflow by @frhagn
https://stackoverflow.com/questions/44147475/how-to-exclude-folder-from-typewriter-code-generation/44150854#44150854
${
    Template(Settings settings)
    {
        settings.IncludeProject("Soft.Data");
        settings.OutputFilenameFactory = file =>
        {
            return $"{file.Name.Replace("ViewModel", "GenViewModel").Replace(".cs", ".ts")}";
        };
    }
}
$Classes(c => c.Namespace != "Soft.Data.ViewModels")[
...
]

You can also include/exclude on at class level using attributes. Below is an exclude attribute.
    [TwExclude]
    [AttributeUsage(AttributeTargets.Class | AttributeTargets.Method)]
    public class TwExcludeAttribute : Attribute
    {
    }

In your tst template you would target the attributes as follows:
$Classes(c=> true
            && c.BaseClass != null
            && c.BaseClass == "ApiController"
            && c.Attributes.Any(a=>a.Name=="TwIncludeApi") @types
            && !c.Attributes.Any(a=>a.Name == "TwExclude"))


why close the issue when it happening to almost everybody this day

why close the issue when it happening to almost everybody this day
Originally posted by @Maduflavins in https://github.com/microsoft/vscode/issues/67013#issuecomment-582667425
solved
press control+C, then press "i" to get in the "insert" status, you could edit your file now.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!
Originally posted by @vscodebot[bot] in https://github.com/microsoft/vscode/issues/67013#issuecomment-574725490

And your issue was related to the Vim extension, not Code itself.
I don't understand why you installed it without knowing how VI works first.


Fixed counters passed by pointers, fixed strtok usage on a readonly buffer

This patch fixes usage of dereferenced counters (before the patch the address was incremented instead of the value) and fixes the buffer of test suites tokens where strtok() originally tried to overwrite a readonly buffer. In addition to this the context variable has been updated to be more conformant with the original POSIX specifications (it should be initialized as NULL and never touched out of strtok)

_strdup seems to break method name during reporting (at least on Windows).

reference branch: release-2.0.1


Runtime in develop branch

In develop global_config.yaml seems to run ~4 times slower than in main. Without parallel processing, in develop I'm getting around 2.22s/it, whereas in main I'm getting around 0.62s/it. With parallel processing, there's a similar difference. Any ideas what could be happening here? Something to do with the new data types?

The above performance estimates are no longer up to date


support for .net maui

Are there plans to release .net maui version of ui kit?

I opened a case with Syncfusion and I got them to make it as feature request.
Here's the link to the feature request:
https://www.syncfusion.com/feedback/31760
Please smash that feature request because I want that feature as much as you and I'm sure we're not the only ones. Also, don't close this case until we have a MAUI Version of UI Kit so that more people will see it.


Re convert an edited smash ultimate .eff doesnt work

i tried to edit an .eff file from smash ultimate which works perfectly fine in game.
but when i try to convert that edited .eff again i get this error

also happens with fully unedited files.
how to reproduce
drag ef_mewtwo.eff (for example) into EffectConverter.exe
drag ef_mewtwo folder into EffectConverter.exe
drag ef_mewtwo_NEW.eff into EffectConverter.exe
produces error and doenst convert properly

Fixed as of https://github.com/KillzXGaming/EffectLibrary/commit/8524a4e05603d3377fac40e3515c424dc5d81f68


[PE-D][Tester D] Edit command with incorrect index returns inconsistent error message depending on whether the index is too high or too low

As seen above, when edit command is used with index 0(the list is one-indexed), I get an invalid command format message, whereas when an index such as 6 that is too high(the list has 5 people) is used, I get an invalid person index instead. This could slow down a user's ability to understand what is wrong if they accidentally key in index 0.

Labels: severity.Low type.FunctionalityBug
original: naythee169/ped#5

Can implement this fix

The error are not wrong so we wont be changing this.


Better UX, project and build.sbt generation

user can input project, scala-version and scalatest-version w/ defaults
main and test files generated under chosen project structure (or default)

Thank you!

Thank you!

Thanks for accepting the PR :)


RUMM-387 Add troubleshooting for handling core-ktx module conflicts

Review checklist (to be filled by reviewers)

[x] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[x] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[x] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Not required anymore


Add logging to antiforgery

We should add logging
Some ideas:

Validating a token (verbose)
Validation failure / missing token (warning)

Thinking warning is right for failures, because generally this is a app configuration issue.

Yeah this is hugely important, and I agree with the proposed log levels.

Had some discussion and this is what we came up with.
IsRequestValidAsync(..) will log success (debug) and failure (warning)
ValidateRequestAsync(...) will log success (debug) - failure is covered by an exception
GetAndStoreTokens(...) will log whether a token was reused or generated (debug)

@dougbu would like to also add logging around the decisions to generate or reuse tokens in SetCookieTokenAndHeader, GetTokens->GetTokensInternal and SetCookieTokenAndHeader. Will circle back around to it after he makes the changes to that area he's working on in #23

Done done done done... (like, Beethoven style)


[Doc] join_by_external_commit is missing in the OpenMLS Book

As an important way to join a group, join_by_external_commit is not mentioned in the OpenMLS Book.

This one is just lacking the file in the SUMMARY.md, the fix is on PR #1603.


update travis to run latest supported node version

node 0.11 was actually unsupported by some of the packages (some required 0.10 or 0.12)
Reason for updating to 4.1:

latest that is installed in Travis (although 4.2 is released)
will work even though that we will get warnings from a few dependencies that wants 0.10 or 0.12

the warning
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":">=0.8 <=0.12 || >=1 <=2"} (current: {"node":"4.1.2","npm":"2.14.7"})

I am merging myself, since it's merely a Travis change


[Bug]: Tried towhee example, found an error"NameError: name 'param_scope' is not defined"

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
https://towhee.readthedocs.io/en/main/data_collection/data_collection.html
>>> import towhee
>>> from towhee.functional import DataCollection
>>> class my_add:
...     def __init__(self, val):
...         self.val = val
...     def __call__(self, x):
...         return x+self.val
...
>>> class my_mul:
...     def __init__(self, val):
...         self.val = val
...     def __call__(self, x):
...         return x*self.val
...
>>> with param_scope(dispatcher={
...         'add': my_add, # register `my_add` as `dc.add`
...         'mul': my_mul  # register `my_mul` as `dc.mul`
... }):
...     dc = DataCollection([1,2,3,4])
...     dc.add(1).mul(2).to_list() # call registered operator
...
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'param_scope' is not defined

Expected Behavior
No response
Steps To Reproduce
No response
Environment
- Towhee version(e.g. v0.1.3 or 8b23a93):0.5.1.dev69
- OS(Ubuntu or CentOS):macos
- CPU/Memory:
- GPU:
- Others:

Anything else?
No response

@jingkl the code example is from option.py which contains the Some and Empty. So the code example can pass the unittest, but failed if the user uses this code directly.
We should also include import statement in our doctest code examples.

/kind bug

/milestone 0.6.0

Reopen for verification.
@jingkl

Verified, not fixed

>>> import towhee
>>> from towhee.functional import DataCollection
>>>
>>> dataset = DataCollection.from_zip('https://towhee.io/towhee/image-dataset/media/branch/main/image_dataset.zip', '*/dataset/*.JPEG').unstream()
>>> query = DataCollection.from_zip('https://towhee.io/towhee/image-dataset/media/branch/main/image_dataset.zip', '*/query/*.JPEG').unstream()
>>> dc_data = dataset.image_load().towhee.resnet_image_embedding(model_name='resnet50').select('feature_vector')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/hparam/hyperparameter.py", line 205, in __call__
    return self._callback(self._path, self._index, *args, **kwds)
  File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/functional/data_collection.py", line 652, in wrapper
    return self.map(op)
  File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/functional/data_collection.py", line 26, in wrapper
    return self.factory(func(self, *arg, **kws))
  File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/functional/data_collection.py", line 216, in wrapper
    return creator(*arg, **kws)
  File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/functional/data_collection.py", line 171, in unstream
    iterable = list(iterable)
  File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/functional/data_collection.py", line 389, in inner
    return unary_op(x)
  File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/engine/factory.py", line 93, in __call__
    res = self._op(*arg, **kws)
  File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/engine/operator_registry.py", line 199, in wrapper_call
    return old_call(self, *args, **kws)
  File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/engine/operator_registry.py", line 183, in __call__
    return old_cls(*arg, **kws)
  File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/hub/builtin/operators/computer_vision.py", line 44, in image_load
    import cv2
ModuleNotFoundError: No module named 'cv2'

Verified, not fixed @reiase
>>> import towhee
>>> from towhee.functional import DataCollection
>>> with param_scope() as hp:
...     hp().dispatcher.as_str = str
...     dc = (
...        DataCollection.range(10)
...         .filter(is_prime)
...         .as_str() # map(str)
...     )
...
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'param_scope' is not defined

needs a from towhee.hparam.hyperparameter import param_scope if you are running it locally.

import towhee
from towhee.functional import DataCollection
dataset = DataCollection.from_zip('https://towhee.io/towhee/image-dataset/media/branch/main/image_dataset.zip', '/dataset/.JPEG').unstream()
query = DataCollection.from_zip('https://towhee.io/towhee/image-dataset/media/branch/main/image_dataset.zip', '/query/.JPEG').unstream()
dc_data = dataset.image_load().towhee.resnet_image_embedding(model_name='resnet50').select('feature_vector')
Traceback (most recent call last):
File "", line 1, in
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/hparam/hyperparameter.py", line 205, in call
return self._callback(self._path, self._index, *args, **kwds)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/functional/data_collection.py", line 652, in wrapper
return self.map(op)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/functional/data_collection.py", line 26, in wrapper
return self.factory(func(self, *arg, **kws))
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/functional/data_collection.py", line 216, in wrapper
return creator(*arg, **kws)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/functional/data_collection.py", line 171, in unstream
iterable = list(iterable)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/functional/data_collection.py", line 389, in inner
return unary_op(x)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/engine/factory.py", line 93, in call
res = self._op(*arg, **kws)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/engine/operator_registry.py", line 199, in wrapper_call
return old_call(self, *args, **kws)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/engine/operator_registry.py", line 183, in call
return old_cls(*arg, **kws)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/hub/builtin/operators/computer_vision.py", line 44, in image_load
import cv2
ModuleNotFoundError: No module named 'cv2'

I believe that we moved away from cv2 being a requiremnet. We might need to add checks with messages to prompt cv2 install.

import towhee
from towhee.functional import DataCollection
dataset = DataCollection.from_zip('https://towhee.io/towhee/image-dataset/media/branch/main/image_dataset.zip', '/dataset/.JPEG').unstream()
query = DataCollection.from_zip('https://towhee.io/towhee/image-dataset/media/branch/main/image_dataset.zip', '/query/.JPEG').unstream()
dc_data = dataset.image_load().towhee.resnet_image_embedding(model_name='resnet50').select('feature_vector')
Traceback (most recent call last):
File "", line 1, in
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/hparam/hyperparameter.py", line 205, in call
return self._callback(self._path, self._index, *args, **kwds)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/functional/data_collection.py", line 652, in wrapper
return self.map(op)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/functional/data_collection.py", line 26, in wrapper
return self.factory(func(self, *arg, **kws))
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/functional/data_collection.py", line 216, in wrapper
return creator(*arg, **kws)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/functional/data_collection.py", line 171, in unstream
iterable = list(iterable)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/functional/data_collection.py", line 389, in inner
return unary_op(x)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/engine/factory.py", line 93, in call
res = self._op(*arg, **kws)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/engine/operator_registry.py", line 199, in wrapper_call
return old_call(self, *args, **kws)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/engine/operator_registry.py", line 183, in call
return old_cls(*arg, **kws)
File "/Users/jingjing/miniconda3/envs/tw/lib/python3.9/site-packages/towhee/hub/builtin/operators/computer_vision.py", line 44, in image_load
import cv2
ModuleNotFoundError: No module named 'cv2'

I believe that we moved away from cv2 being a requiremnet. We might need to add checks with messages to prompt cv2 install. I saw that a few of our mixins still use it @reiase

There should be some standard method for handling inner import and module not found, I will move this problem to another issue.

@jingkl
need verify, so reopen this issue.

@jingkl
How about this issue? Is it fixed?

@jingkl How about this issue? Is it fixed?

They removed the example from the documentation, so turn off the issue


ModuleNotFoundError: No module named 'proxmoxer' | On python3 manage.py migrate

(venv) root@netbox:/opt/netbox/netbox# python3 manage.py migrate
Traceback (most recent call last):
File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/base.py", line 414, in run_from_argv
self.execute(*args, **cmd_options)
File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/base.py", line 460, in execute
output = self.handle(*args, **options)
File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/base.py", line 95, in wrapped
saved_locale = translation.get_language()
File "/opt/netbox/venv/lib/python3.9/site-packages/django/utils/translation/init.py", line 210, in get_language
return _trans.get_language()
File "/opt/netbox/venv/lib/python3.9/site-packages/django/utils/translation/init.py", line 65, in getattr
if settings.USE_I18N:
File "/opt/netbox/venv/lib/python3.9/site-packages/django/conf/init.py", line 87, in getattr
self._setup(name)
File "/opt/netbox/venv/lib/python3.9/site-packages/django/conf/init.py", line 74, in _setup
self._wrapped = Settings(settings_module)
File "/opt/netbox/venv/lib/python3.9/site-packages/django/conf/init.py", line 183, in init
mod = importlib.import_module(self.SETTINGS_MODULE)
File "/usr/lib/python3.9/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 790, in exec_module
File "", line 228, in _call_with_frames_removed
File "/opt/netbox/netbox/netbox/settings.py", line 644, in
raise e
File "/opt/netbox/netbox/netbox/settings.py", line 637, in
plugin = importlib.import_module(plugin_name)
File "/usr/lib/python3.9/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 790, in exec_module
File "", line 228, in _call_with_frames_removed
File "/opt/netbox/venv/lib/python3.9/site-packages/netbox_proxbox/init.py", line 40, in
from . import proxbox_api
File "/opt/netbox/venv/lib/python3.9/site-packages/netbox_proxbox/proxbox_api/init.py", line 1, in
from . import (
File "/opt/netbox/venv/lib/python3.9/site-packages/netbox_proxbox/proxbox_api/update.py", line 2, in
from .plugins_config import (
File "/opt/netbox/venv/lib/python3.9/site-packages/netbox_proxbox/proxbox_api/plugins_config.py", line 2, in
from proxmoxer import ProxmoxAPI
ModuleNotFoundError: No module named 'proxmoxer'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/netbox/netbox/manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/init.py", line 446, in execute_from_command_line
utility.execute()
File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/init.py", line 440, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/base.py", line 427, in run_from_argv
connections.close_all()
File "/opt/netbox/venv/lib/python3.9/site-packages/django/db/utils.py", line 212, in close_all
for alias in self:
File "/opt/netbox/venv/lib/python3.9/site-packages/django/utils/connection.py", line 73, in iter
return iter(self.settings)
File "/opt/netbox/venv/lib/python3.9/site-packages/django/utils/functional.py", line 49, in get
res = instance.dict[self.name] = self.func(instance)
File "/opt/netbox/venv/lib/python3.9/site-packages/django/utils/connection.py", line 45, in settings
self._settings = self.configure_settings(self._settings)
File "/opt/netbox/venv/lib/python3.9/site-packages/django/db/utils.py", line 148, in configure_settings
databases = super().configure_settings(databases)
File "/opt/netbox/venv/lib/python3.9/site-packages/django/utils/connection.py", line 50, in configure_settings
settings = getattr(django_settings, self.settings_name)
File "/opt/netbox/venv/lib/python3.9/site-packages/django/conf/init.py", line 87, in getattr
self._setup(name)
File "/opt/netbox/venv/lib/python3.9/site-packages/django/conf/init.py", line 74, in _setup
self._wrapped = Settings(settings_module)
File "/opt/netbox/venv/lib/python3.9/site-packages/django/conf/init.py", line 183, in init
mod = importlib.import_module(self.SETTINGS_MODULE)
File "/usr/lib/python3.9/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 790, in exec_module
File "", line 228, in _call_with_frames_removed
File "/opt/netbox/netbox/netbox/settings.py", line 644, in
raise e
File "/opt/netbox/netbox/netbox/settings.py", line 637, in
plugin = importlib.import_module(plugin_name)
File "/usr/lib/python3.9/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 790, in exec_module
File "", line 228, in _call_with_frames_removed
File "/opt/netbox/venv/lib/python3.9/site-packages/netbox_proxbox/init.py", line 40, in
from . import proxbox_api
File "/opt/netbox/venv/lib/python3.9/site-packages/netbox_proxbox/proxbox_api/init.py", line 1, in
from . import (
File "/opt/netbox/venv/lib/python3.9/site-packages/netbox_proxbox/proxbox_api/update.py", line 2, in
from .plugins_config import (
File "/opt/netbox/venv/lib/python3.9/site-packages/netbox_proxbox/proxbox_api/plugins_config.py", line 2, in
from proxmoxer import ProxmoxAPI
ModuleNotFoundError: No module named 'proxmoxer'
(venv) root@netbox:/opt/netbox/netbox#

I just have execute it :
pip install proxmoxer
pip install pynetbox


Fix CUDAToolkit_ROOT

This pull request primarily focuses on changes to the CUDA toolkit setup and usage in the GitHub Actions workflow and the CMake build system. The most significant changes include setting the CUDAToolkit_ROOT in the GitHub Actions environment, modifying the download and verification of the CUDA SDK in the workflow, updating the CMake command to use the CUDAToolkit_ROOT environment variable, and replacing the CUDA check in CMakeLists.txt to use FindCUDAToolkit.
Changes in GitHub Actions workflow:

.github/workflows/win-gpu-x64-build.yml: Set CUDAToolkit_ROOT in the environment to point to the downloaded CUDA SDK.
.github/workflows/win-gpu-x64-build.yml: Modified the download of the CUDA SDK to store it in the GitHub workspace and added a step to verify the CUDA SDK.
.github/workflows/win-gpu-x64-build.yml: Updated the CMake command in the build step to use the CUDAToolkit_ROOT environment variable.

Changes in CMake build system:

CMakeLists.txt: Replaced the check for CUDA support to use FindCUDAToolkit instead of CheckLanguage, and added a status message if CUDA is not found.


GH Actions

Todos

[x] Run linter action
[x] Run unit-test action
[x] Run build action
[ ] Optional: docker action
[x] Use clear naming for actions
[x] Add actions to branch protection rules for main branch
[x] Add CI batch to readme

Done and live on main.


Request for documentation on renv (via Posit Tech Group)

The Posit Technical Group asked for a guide on how to use renv. Action assigned to me.

Duplicate


AsPublisher Failure Type Alignment with RxSwift

What's Changed?

Updated asPublisher failure type from BridgeFailure to Error. This is in line with the error type that is used upstream by RxSwift. Note that BridgeFailure is still used under the hood and BridgeFailure.bufferOverflow errors can still be thrown (they can be checked against by switching on Error as you would to check against any other specific error type).
Refactored and renamed assertBridgeBufferDoesNotOverflowIfPossible to be usable across publishers with Error failure types. This checks whether or not the failure type is a BridgeFailure.bufferOverflow.
Updated documentation
Updated and added tests

Further Details
Some confusion was caused when flatMapping downstream of an asPublisher as a failure type mismatch would always occur (eg. between Error and BridgeFailure). This was never intended, as the aim of the asPublisher was to perform a like-for-like transformation from an RxSwift Observable.  By mapping the failure type to Error, alignment with the expected upstream RxSwift error type is provided, and the ability to chain further publishers downstream that match the Error failure type is also effortless as an additional mapError is no longer necessary.
For example, if we have a PublishSubject<Int> and want to convert it to a Combine publisher, perform some additional transformation on it before sinking on it, the following compiler error was previously being displayed:
subject
    .asPublisher(withBufferSize: 1, andBridgeBufferingStrategy: .error)
    /// Instance method 'flatMap(maxPublishers:_:)' requires the types 'Publishers.Buffer<BridgePublisher<PublishSubject<Int>>>.Failure' (aka 'BridgeFailure') and 'Error' be equivalent
    .receive(on: scheduler)
    .flatMap { value -> AnyPublisher<Int, Error> in
        Just(value * 2)
            .setFailureType(to: Error.self)
            .eraseToAnyPublisher()
    }
    .sink()
    ....

After the changes, this is now possible since the Error failure types now match between asPublisher and the flatMap:
subject
    .asPublisher(withBufferSize: 1, andBridgeBufferingStrategy: .error)
    .receive(on: scheduler)
    .flatMap { value -> AnyPublisher<Int, Error> in
        Just(value * 2)
            .setFailureType(to: Error.self)
            .eraseToAnyPublisher()
    }
    .sink()
    ....

However, as expected when using combine with mismatching failure types, if we want to perform a transform with a failure type other than Error, we must mapError beforehand as follows:
struct DatedError: Error {
    let error: Error
    let date: Date

    init(_ error: Error) {
        self.error = error
        date = Date()
    }
}

subject
    .asPublisher(withBufferSize: 1, andBridgeBufferingStrategy: .error)
    .receive(on: scheduler)
    .mapError { DatedError($0) } // Map error required to map from generic `Error` type to desired `DatedError` type
    .flatMap { value -> AnyPublisher<Int, DatedError> in
        Just(value * 2)
            .setFailureType(to: DatedError.self)
            .eraseToAnyPublisher()
    }
    .sink()
    ....

Looks good to me. Definite improvement as it makes it effortless to bridge now. Good work.

Will give it a proper review later today.

Sorry didn't mean to hit the requires changes button. All approved, looking forward to using this!


fix(deps): update dependency @actions/github to v5.1.1

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

@actions/github (source)
5.0.3 -> 5.1.1

Release Notes

actions/toolkit
v5.1.1

Export default octokit options #1188

v5.1.0

Add additionalPlugins parameter to getOctokit method #1181
Dependency updates #1180

Configuration
📅 Schedule: Branch creation - "after 6am and before 6pm every weekday" (UTC), Automerge - "after 8am and before 5pm every weekday" (UTC).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: actions/pnpm-lock.yaml
 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

Your pnpm version is incompatible with "/tmp/renovate/repos/github/pleo-io/pleo-spa-cicd/actions".

Expected version: 8.x
Got: 7.30.4

This is happening because the package's manifest has an engines.pnpm field specified.
To fix this issue, install the required pnpm version globally.

To install the latest version of pnpm, run "pnpm i -g pnpm".
To check your pnpm version, run "pnpm -v".

Your Node version is incompatible with "/tmp/renovate/repos/github/pleo-io/pleo-spa-cicd/actions".

Expected version: 16.x
Got: v18.15.0

This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.


Which script was used for Fig.2 in The SpliZ generalizes ‘percent spliced in’ to reveal regulated splicing at single-cell resolution

Dear juliaolivieri , Could you please tell us which script did you use for Fig.2, as lots of scripts were provided in the directory of SpliZ_pipeline/scripts/

Thanks a lot.

ggsashimi?
https://github.com/guigolab/ggsashimi

We used a custom in-house script to generate these plots and unfortunately it is not straightforward to adapt it for general datasets. Our recommendation is to use ggsashimi on your bam files as it would be much simpler.


Auto build fixes

The automictic build fixes for any development moment

This change is a bit big. I fixed the grunt pipeline, I see some other changes (changelog), you can submit those separately.


Wasn't able to use via IPM

I set up a local FHIR server via FHIR tempate.
Having my FHIR server in FHIRSERVER namespace with URL:
http://localhost:32783/fhir/r4/
installed a server as:
do ##class(dc.FhirClient).RegisterServer("Local FHIR Server","http://localhost:32783/fhir/r4/"," "," ")
But UI is not working:

CLI is not working either:
FHIRSERVER>do ##class(dc.FhirClient).RegisterServer("Local FHIR Server","http://localhost:32783do ##class(dc.FhirClient).RegisterServer("Local FHIR Server","http://localhost:32783/fhir/r4/",do ##class(dc.FhirClient).ListResources()

   do irisfhirclient.ListResources(obj.Endpoint,obj.ApiKey,opt)
   ^
 }
 //Active Server data is not defined
<THROW>ListResources+8^dc.FhirClient.1 *%Exception.PythonException <PYTHON EXCEPTION> 246 <class 'requests.exceptions.InvalidHeader'>: Invalid leading whitespace, reserved character(s), or return character(s) in header value: ' '
FHIRSERVER 2d1>

The issue is resolved.
The new release is updated. Please reinstall the application and try.
Thanks


Illegal reflective access

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by io.github.hellocuriosity.ModelForge (file~/.gradle/caches/modules-2/files-2.1/io.github.hellocuriosity/model-forge/0.7.0/5a914fb11f1f98c55a15673356fdab5fb36513c3/model-forge-0.7.0.jar) to field java.lang.String.value
WARNING: Please consider reporting this to the maintainers of io.github.hellocuriosity.ModelForge
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

It seems that the instantiator is being asked to take care of forging instead of an added provider:
        val model: T = instantiator.newInstance() as T

        if (providers.isNotEmpty()) {
            providers[clazz]?.let { return it.get() as T }
        }

Do you have a provider example where this is showing up? The solution might be as easy as putting the provider check first, I mean no need to instantiate all the other stuff if we are using a provider anyway.


Setting Username causes bug

Happening on current master.
When attempting to change Name of account, I get this error:

The log:
fail: PayServer:      BTC (Lightning): Error while contacting app
System.Threading.Channels.ChannelClosedException: The channel has been closed.
   at System.Threading.Channels.AsyncOperation`1.GetResult(Int16 token)
   at BTCPayServer.App.BTCPayAppLightningClient.Listener.WaitInvoice(CancellationToken cancellation) in /Users/andy/Documents/GitHub/app/submodules/btcpayserver/BTCPayServer/App/BTCPayAppLightningClient.cs:line 144
   at BTCPayServer.Payments.Lightning.LightningInstanceListener.Listen(CancellationToken cancellation) in /Users/andy/Documents/GitHub/app/submodules/btcpayserver/BTCPayServer/Payments/Lightning/LightningListener.cs:line 531

I assume this is an UI issue not related to the channel closure. I'll take a look.

I had this exact problem today.


Update NATS.Client.Hosting package as NATS.Extensions.Microsoft.DependencyInjection

Proposed change
Update NATS.Client.Hosting package as NATS.Extensions.Microsoft.DependencyInjection and mark NATS.Client.Hosting obsolete.
Use case
Confusing for new users on NuGet search results. Also x.Extensions.Microsoft.DependencyInjection seems to be the convention.
cc @mrpmorris thanks for the suggestion

I took an initial stab at this here.

thanks @rickdotnet 🥇 really appreciate the contributions!

I took an initial stab at this here.

@rickdotnet, I dropped a few comments but realized it's not a PR. Please feel free to create one and ref both issues if you like 💯

Sure, will clean it up and put something out soon.

Nice 🙂


NETOBSERV-155: Added sampling field to console frontend configuration

Added sampling field to configuration.
To do that I needed to keep a reference to the FlowCollectorSpec object in the console object builder so I added a bit of refactoring to only keep this object and remove ConsolePlugin and Loki reference which are not needed anymore.

/approve


Modrinth ClientSide/ServerSide

The mod's description states that the mod can be used on both sides independently, but the Modrinth "Sides" information states that it is "Unsupported" ClientSide and "Required" ServerSide.
I think that it should be put on "Optional" for both sides to help people find the mod more easily (e.g. if they filter ClientSide mods).

Ye. I think that I work on client but yesterday I realize that it didn't so I changed it on Modrinth and will be return after fix

Alright, should I leave this issue opened until the deployment of the fix or should I close it now ?

I leave it open. That allows us to not forget to fix it :)
I can't fix it right now because it requires architecture refactoring, but currently, I have another project ongoing.

Any news ?

The latest news I publish on my Discord every first week of month (if news exists). Here the latest and if interest here discord invite link https://discord.gg/pbwnMwnUD6

Wait, so #7 is a glitch ? Because it cannot update mods in the client at all

Wait, so #7 is a glitch ? Because it cannot update mods in the client at all

The first versions worked with clients, but then I broke it because I wrote this mod just quickly for a friend. And now the mod is planned to be rewritten next year and release the next update/remake with all the features that I promise on Discord: https://discord.gg/pbwnMwnUD6

Fixed in https://github.com/syorito-hatsuki/ducky-updater-rework/pull/10, soon will be uploaded to Modrinth and CurseForge


Update README.md

Some copy edits based on the existing text but I have a bunch of questions...

A few questions above but really I think this we'd need a short usage guide covering all the commands and/or API endpoints (whatever we recommend or expect to get more usage) to get a better sense of what the tool does and how it looks and feels. Is that coming?