Favourited cards do not show expiration date and cvc

Hello,
First of all, thanks for the extension. I use it everyday and helps me a lot.
This issue is about the favourite feature. I do not have the adyen drop-in payment flow so I do not benefit from the Prefill button, so I manually copy the card number, cvc and expiration date to test my checkout. I currently can not use favourites because when I do the cvc and expiration date are replaced by the brand logo, so I have no way of copying the CVC and EXP date.
My suggestion: Keep the CVC and expiration date and make it so when you click at the field you copy the value. You can still keep the brand logo at the end of everything maybe.
I will be happy to submit a PR if you like this idea, let me know :)
Thanks again.

Hello @mglavall, thank you very much for the great feedback and the suggestions, we appreciate your help to make the extension better.
On principle submitting a PR would be great, but the extension is still in an early phase and we are already working on some changes, I hope we can soon have a stable version and accept your contributions.
Nevertheless your suggestions are great and we want to take them on board ASAP:

show CVC and date in the Favourites
also allow copy (in the clipboard) of each field when clicking on it (in this case you would copy each field just with a click and paste it where you need it)

We are already working on it! Please reach out if you have more feedback and suggestion.

@mglavall we have implemented this, still to reviewed/finalised but it would be great if you can check the branch and load the extension from the source code


MQTT broker password and usernames

Can you support mosquitto brokers with usernames and passwords?

I'm sure that wouldn't be that hard, feel free to submit a pull request with changes for consideration

I think it's a little beyond me I'm afraid.

That's a shame because it really would be very easy

Hello hardillb, Or maybe other developers,
My mosquitto/mqtt  broker is set up with username and password.
I do understand that if someone is a developer and understand coding in python, it wouldn't be that hard to implement this username and password. I'm not a developer too. Not at all. But I like to experiment with code. But in this case this did not help me at all.
I found out that you have to implement something like:
username_pw_set(username=username,password=password);
But I do not understan how and where.
I tried to add ", String username, String password" but that did not work either.
It would be great if someone could help me with this code, and implement this!
(I create a docker instance, and try to run it as docker container)

As I said before, submit a PR and I'll look at it, but I've not really touched this code (which was purely intended as a tool to explore Ikea's interface) in 5 years.
You've found an example that clearly shows what needs changing, so take that and apply it this code and learn a little while your at it, but I have no interest in doing it for you.


[Tracking Issue] Identify and throw errors for currently-unsupported (but planned) features.

There are many features we would like to add, and there are many problems that we're aware of. Not all of these features can be built, nor problems resolved, before a first release.
Nevertheless, we can strive to identify unsupported features, and let the user know that they're attempting to do something which is currently unsupported, but planned. I.e. we should add code which identifies known pitfalls and gives the user a human-readable and contextual error, instead of some opaque, technical error.
This tracking issue can be an ever-growing list of such unsupported features. Each item in the list should be an issue which seeks to programmatically identify unsupported patterns, and throw an informative error in such cases.
For each case, we should assess whether the time & effort needed to identify and throw an error is more or less time than implementing the feature properly.

The simulator identifies contract re-entrancy.

If Contract A calls contract B, but later in the simulation Contract A is called by B (or C or D etc), this could cause re-entrancy errors.
If a private function of Contract A calls a private function of Contract A (e.g. a recursive call), the simulator should identify cases where further state changes are made after the call (because such state changes could cause state ordering errors). "State changes" includes getting, nullifying or inserting notes after the call.
If a public function of Contract A calls a public function of Contract A (e.g. a recursive call), the simulator should identify cases where further state changes are made after the call (because such state changes could cause state ordering errors). "State changes" includes getting, nullifying or inserting notes, and reading and writing public state, after the call.
Note: Contract A should still be able to make a private -> internal public call to itself, and make further private state changes after such a call.
The eventual fix will be to track the execution order of state transitions, logs, and enqueued function calls, but this 'ordering' work will take some time.
Until we do the eventual fix, we should identify this pattern and throw an error.

### Document limitations
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/1652
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/1654
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/1679

### Add informative error messages
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/1653
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/1603

### Tests to replicate bugs/limitations
* [ ] https://github.com/AztecProtocol/aztec-packages/issues/1615
* [ ] https://github.com/AztecProtocol/aztec-packages/issues/1616
* [ ] https://github.com/AztecProtocol/aztec-packages/issues/1617

### Working around these bugs
* [ ] https://github.com/AztecProtocol/aztec-packages/issues/1624
* [ ] https://github.com/AztecProtocol/aztec-packages/issues/1622
* [ ] https://github.com/AztecProtocol/aztec-packages/issues/1623
* [ ] https://github.com/AztecProtocol/aztec-packages/issues/1629
* [ ] https://github.com/AztecProtocol/aztec-packages/issues/1655

If a private function of Contract A calls a private function of Contract A (e.g. a recursive call), the simulator should identify cases where further state changes are made after the call (because such state changes could cause state ordering errors). "State changes" includes getting, nullifying or inserting notes after the call.

After discussing with @spalladino, I don't think this is an issue that a user could experience today because while the kernel is not strict on private state ordering, the simulator is. The simulator will never let you get or nullify a note that does not exist yet.

If a public function of Contract A calls a public function of Contract A (e.g. a recursive call), the simulator should identify cases where further state changes are made after the call (because such state changes could cause state ordering errors). "State changes" includes getting, nullifying or inserting notes, and reading and writing public state, after the call.

I think the same is true for the simulator in public (the simulator is as strict as it needs to be), but the problem is that the public kernel does have constraints to ensure public state updates make sense in-sequence. Since the public kernel doesn't always execute things in execution order, it may think that it is enforcing proper ordering of public state updates, but what it is actually doing is rejecting a perfectly valid sequence of public state updates.
So, could we just temporarily remove the public kernel constraints that ensure a series of public state updates make sense in sequence? Maybe, but it is also the job of the final public kernel to turn the "final" state value that should be injected in the public data tree. That value must still be correct.

Closing, as all but one complete, and we can just track that one issue.


Create deploy.yml

Testing

Trade-offs

Dependencies

Screenshots

Checklist for PR creator

[ ] If any new components were added, there are exported from packages/index.ts
[ ] If this PR is associated with a JIRA, it is mentioned in commit message footer ("Closes …")
[ ] If this PR contains breaking changes, is stated in commit message body ("BREAKING CHANGE: …")
[ ] Info for applicable sections above is provided

Let's not merge on Friday afternoon in case the deployment does go wrong 😅


[Distributed] Prevent overloading on async in distributed methods, for wire compat

Description: In order to be better for wire compatibility, we actually encode the YaK (async throws) distributed thunk based names for the distributed accessible functions. This currently leads to crashes if one does overload on "just asyncness". After discussing if we should allow these overloads (#59831) or ban them (this PR) we came to the conclusion this is better for distributed calls. This PR bans async overloading on distributed methods.
Risk: Low, prevents a crash by preventing bad declarations.
Review by: @DougGregor
Testing: PR testing
Original PR: #59831
Radar: rdar://96179707

@swift-ci please test

This PR does not change the mangling strategy, but just prevents a compile time crash when declaring conflicting methods, as such, it can land a bit later if it has to.

@swift-ci please test Linux

Tho it seems this missed the train -- heh my bad.
Thankfully it does not affect mangling or ABI in any way; it is just a "nicer error message"

@swift-ci please test

Thanks for review Doug!


ShEnableHooks and ShDisableHooks in shadow_hook.cpp

why
HypercallNumber::kShEnablePageShadowing and
HypercallNumber::kShDisablePageShadowing
are missing?

Hey, did you pull down files recursively?
$git clone --recursive https://github.com/tandasat/DdiMon.git

Yes.
And HypercallNumber in HyperPlatform/util.h there is no kShEnablePageShadowing and kShDisablePageShadowing

That is weird. Can you manually checkout 374db11ecefd1f00acccbc34fec6c1013e6f080c in DdiMon/HyperPlatform?


Remove call_user_func(), call_user_func_array() and constant()

Codecov Report

Merging #1760 (6933151) into master (32cfcfc) will decrease coverage by 14.53%.
The diff coverage is 38.98%.

@@              Coverage Diff              @@
##             master    #1760       +/-   ##
=============================================
- Coverage     87.87%   73.34%   -14.54%
- Complexity     7822     7824        +2
=============================================
  Files           267      267
  Lines         22520    22367      -153
=============================================
- Hits          19790    16404     -3386
- Misses         2730     5963     +3233

Flag
Coverage Δ

5-max
73.34% <38.98%> (-14.54%)
:arrow_down:

7.4
73.34% <38.98%> (-14.54%)
:arrow_down:

agnostic
73.34% <38.98%> (-0.03%)
:arrow_down:

mysql
?

pgsql
?

sqlite
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...l/Generator/Behavior/Delegate/DelegateBehavior.php
92.53% <ø> (+2.68%)
:arrow_up:

...stedSet/NestedSetBehaviorObjectBuilderModifier.php
100.00% <ø> (+2.61%)
:arrow_up:

...Sortable/SortableBehaviorObjectBuilderModifier.php
99.11% <ø> (ø)

src/Propel/Generator/Builder/Om/ObjectBuilder.php
85.61% <0.00%> (-8.78%)
:arrow_down:

src/Propel/Runtime/Collection/ArrayCollection.php
0.00% <0.00%> (-90.33%)
:arrow_down:

...Runtime/Collection/ObjectCombinationCollection.php
0.00% <0.00%> (-72.10%)
:arrow_down:

...l/Runtime/Connection/ProfilerConnectionWrapper.php
0.00% <0.00%> (ø)

src/Propel/Runtime/Connection/StatementWrapper.php
40.62% <0.00%> (-21.88%)
:arrow_down:

src/Propel/Runtime/Formatter/ArrayFormatter.php
0.00% <0.00%> (-85.87%)
:arrow_down:

src/Propel/Runtime/Util/PropelModelPager.php
0.00% <0.00%> (-65.12%)
:arrow_down:

... and 120 more

Continue to review full report at Codecov.

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


Any common feature libraries out there?

** Question : **
I arrived here and am interested in leveraging this platform in addition to and as a compliment terratest, but I don't want to start from scratch in writing features and I can't find any reference at all in the readme to a sample library or folder of already-existing tests/features. I could copy-paste all the examples from the .md example files but that seems like more work than it should be. Is there any shared library of common features/test out there? If not, is there any interest in starting such a library?
As a new user, or as someone trying to pitch this to a peer, I would love to be able to run pip install and then run the code. It seems the new user experience is hampered right now by having to start from scratch with features. (Apologies in advance if this is available somewhere obvious and I just missed it.)
Thanks!

Spot on! I was just working on this :)
You are so right and this becomes a common request from many other people.
I will give priority and start with small then grow bigger and more diverse on the tests

FANTASTIC! I think this would be an amazing resource!
I find that one of the most awesome things about Terraform is also one of its most dangerous: people can use libraries of Terraform scripts (open and closed source) to deploy infrastructures that they themselves don't need to fully understand. I love that deploying and inspecting other people's terraform architectures is also a great way to learn those architectures. But you know as they say, with great power comes great ... um... need for automated testing. :)
Seriously, though, I love this concept and we're all better at this stuff when we're learning from each other. I'm morbidly excited to give this a spin and see what tests my scripts will fail! :)

@aaronsteers you can pull features from a git repository, see https://github.com/eerkunt/terraform-compliance/pull/283. I don't have a library to offer you right now, but this would at least save you from copying Markdown if you found one!

@aaronsteers
We do have a place to share commonly used features now! Please check out user-friendly-features.

@aaronsteers
We do have a place to share commonly used features now! Please check out user-friendly-features.

@Kudbettin - This is fantastic! Exactly what I was hoping for. (Closing as resolve.)
Thanks!!

@Kudbettin - This is fantastic! Exactly what I was hoping for. (Closing as resolve.)
Thanks!!


Custom JSON formatting attributes on models are ignored

This is because in order to add the HAL objects to the model it is converted to a dynamic, so when it comes to serialization time there is no class definition to read custom serialization attributes from.
Not a major issue, but thought it was worth mentioning somewhere as it took me a while to realise why they weren't having effect!

+1 this needs fixing

This might need a change to how we approach things - as implemented, it is serialiser-agnostic, it simply swaps your model out for a dynamic.


bootstrap for coreOS blocks on missing libselinux-python

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
bug report
Environment:

Cloud provider or hardware configuration:
VMs on own hardware

OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):
machine running kubespray:
Linux 4.16.3-301.fc28.x86_64 x86_64
NAME=Fedora
VERSION="28 (Cloud Edition)"
ID=fedora
VERSION_ID=28
PLATFORM_ID="platform:f28"
PRETTY_NAME="Fedora 28 (Cloud Edition)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:28"
HOME_URL="https://fedoraproject.org/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=28
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=28
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Cloud Edition"
VARIANT_ID=cloud

target machines:
Linux 4.14.48-coreos-r2 x86_64
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1745.7.0
VERSION_ID=1745.7.0
BUILD_ID=2018-06-14-0909
PRETTY_NAME="Container Linux by CoreOS 1745.7.0 (Rhyolite)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"

Version of Ansible (ansible --version):
ansible 2.6.0
config file = /Users/maxx/.ansible.cfg
configured module search path = [u'/Users/maxx/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/Cellar/ansible/2.6.0/libexec/lib/python2.7/site-packages/ansible
executable location = /usr/local/bin/ansible
python version = 2.7.15 (default, Jun 17 2018, 12:46:58) [GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-9<IP_ADDRESS>)]

Kubespray version (commit) (git rev-parse --short HEAD):
4092f96d
Network plugin used:
weave
Copy of your inventory file:
node1 ansible_host=<IP_ADDRESS>
node2 ansible_host=<IP_ADDRESS>

# ## configure a bastion host if your nodes are not directly reachable
bastion ansible_host=<IP_ADDRESS>:2022 ansible_user=username

[kube-master]
node1
node2

[etcd]
node1
node2

[kube-node]
node1
node2

[kube-ingress]
node1
node2

[k8s-cluster:children]
kube-master
kube-node
kube-ingress

Command used to invoke ansible:
ansible-playbook -i inventory/cluster/hosts.ini cluster.yml
Output of ansible run:
https://gist.github.com/mvernimmen/68bef73ad0d2a03acbcaec3f39df9563
Anything else do we need to know:
I'm trying to install to 2 coreos nodes, while using one of those hosts as a bastion host. This is because I'm remote to that network and don't have a vpn connection that allows me to reach those hosts on the internal network. Instead I need to access them via public IP addresses.
The problem is that after having configured all.yml and k8s-cluster.yml according to https://github.com/kubernetes-incubator/kubespray/blob/master/docs/coreos.md ansible returns "msg": "Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!"
I expected kubespray to fix that for me as part of the bootstrap.
If this is not considered a bug I would appreciate a pointer to fix this manually.
thank you!

I think I interpreted the message "Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!" as requiring libselinux-python on the target hosts, but it means it needs the library installed on the host running kubespray.
Can anyone confirm?

AFAIK ansible and python are not installed on the provisioned server, so you should try to install that package on your host.

yes I fixed it by doing that, it all worked out.


Need kick map implementation

For the simulation of Insertion Devices in synchrotron radiation light sources it is common to model the impact of them by introducing a "kick map" of the element.
It would be useful to also have it in XSuite.

Is this already available in some other simulation codes?

Yes indeed. At least of the two codes I know of:
AT : https://atcollab.github.io/at/p/api/at.lattice.idtable_element.html
ELEGANT: https://ops.aps.anl.gov/manuals/elegant_latest/elegantsu234.html#x245-25000010.124

Would you have a working AT example that one could benchmark against?


Syntax erros when cloning the build

Hey there,
I am trying to get into gamehacking and since I love metin 2 and was using this cheat a few years back and now I saw this source I figured that I would use this to further my skills.
I would appreciate @KoMaR1911 if you could provide me with the dependencies you used. I already figured out this much:
Dependencies: "DirectX8 (d3d8.h and d3d8xd.h), Cpython and Boost. Visual studio 2019 with the SDK set to 10.0.17134.0."
After this I only have syntactical errors left, why is that? No matter if I clone latest repo or use one of the other 3 sources you uploaded, all of them have syntactical erros, could it be that I have used the wrong libraries (outdated) and that's what's causing random syntax errors to appear?
I would be really glad if anyone could shine a little bit of insight on this.

UPDATE:
Did you modify any preprocessor definitions? I am guessing so, if so could you elaborate on which and why?


Real-Time Synchronization of movement

Describe the bug
myCobot reads the slider values and does not run smoothly.
To Reproduce
I set up an OSC server in python and send values using the pymycobot module.
Here is a part of the function. However, I just use prepared functions.
def sync_angle(self, _angles, _speed):
        self.arm.sync_send_angles(_angles, _speed)

Here is a video recording of the operation of the slider and the actual movement.
At 1 minute and 7 seconds, I try to move the slider while holding it, but mycobot does not move smoothly.
https://www.youtube.com/watch?v=13HlRCM19ws
Expected behavior
It is expected that the position and angle of myCobot will move smoothly according to the position of the slider.
It is also hoped that a tracking device such as Leap Motion can be used to synchronize the position of the mycobot with the position of one's hand by continuously sending values in real time.
Screenshots
Recording Video:
https://www.youtube.com/watch?v=13HlRCM19ws
Desktop (please complete the following information):

OS: Windows 10 Home
Python 3.8.5
pymyCobot 2.4.1
python-osc 1.7.4
OSC signal from Touch Designer 2021.12380

Additional context
myCobot is Tranponder mode.

This sync method relies on is_in_position(), but is_in_positon is not so stable.
Serial communication contains packet loss and delay, so this may be the reason why mycobot can not run smoothly.

@zlj-zz
Thank you very much for your feedback.
I am using the official Transponder program. The rate is 115200, it means fastest. So you mean that in order to achieve smoother movement, the Transponder program needs to be modified or the signals sent by the python program need to be better controlled.
In addition,  I just saw a couple of samples that realize the smooth movement (1, 2). One of them uses ROS, while the other one looks like it implements the original program.
Do they cover packets and delays, and the losses therein?
I have checked the script to control myCobot from ROS. However, it looks like it just sends_radians here. Is there something else you are doing on the ROS side?
Do you have any ideas on how to send signals from python to myCobot to make it run smoothly?

@tkdsym2
The probability of packet loss is very small.The question is on is_in_position().
According to my current test, this method cannot return to true immediately after the manipulator reaches the point.
The manipulator may not be able to reach the target point completely due to the large force distance, and the error between the real angle and the target angle is too large (for example > 5mm), so is_in_position() can not judge the position successfully. So you may need to wait until the timeout (the default is 7S).
If you want to achieve a function similar to tracking, then I believe your data should be continuous and the time interval is very short.So you may not need to use this method. You can try to send data continuously (e.g. angles), as follows:
while True:
    angles = queue.get() # Getting data from a queue.
    mycobot.send_angles(angles, 90)
    time.sleep(.05)

It should also be noted that the time taken to send the data itself is about 5ms(e.g. send_angles() or something).

@zlj-zz
Thank you very much for your great feedback, and I am sorry to be late.
I had been trying to use your example. However, the movement of myCobot was the same.
I just pushed my codes using Processing instead of TouchDesigner. It is easier and more simple than using TouchDesigner. The code just sends one angle based on the parameter from the slider on Processing program.
Could you please see if what I am doing is the same as what you have shown me? Also, it would be great if you could actually run the code to see what is happening.
thanks!

I am sorry, I don't have a Processing environment.
But I looked at your code and it didn't look like a problem.
But the following code will read the serial port 9 times, too much fast reading may lead to empty data return. It seems that once is enough.
    while True:
                if connection:
                    simpleClient.send_message('/util/status/angles', arm.get_arm_status()['angles'])
                    simpleClient.send_message('/util/status/coords', arm.get_arm_status()['coords'])
                    simpleClient.send_message('/util/status/radians', arm.get_arm_status()['radians'])
                    # print('{}'.format(arm.get_arm_status()))

                asyncio.sleep(0.01)

BTW. Do you have any other questions? This doesn't seem to be tracking.

If there is no activity for a long time, this issue will be closed.


Build broken using Love12 AppImages

Hi- I have been using love with a custom AppImage, (specifically, the latest love-12 AppImage generated from github actions).
The new Love-12 appImages contain liblove-12.so as opposed to liblove.so, which is breaking makelove.
I'm not sure why this was renamed, I've asked on the love discord.
I had a discussion with Sasha, turns out liblove has always been named this way. I think it's just because I got the extracted appimage from the github CI, why there were issues.
What do you think about this? Would it be worth making the liblove detection a bit more generic to detect different versions....?
I also suspect that this was the cause of #38
(For reference, here is a tree of the new extracted appimage for love 12)
appimage/
    squashfs-root/
        love.desktop
        .DirIcon
        AppRun
        love.svg
        license.txt
        share/
            mime/
                packages/
                    love.xml
            applications/
                love.desktop
            pixmaps/
                love.svg
            lua/
                5.1/
            luajit-2.1.0-beta3/
                jit/
                    p.lua
                    dump.lua
                    dis_mips.lua
                    dis_mipsel.lua
                    bc.lua
                    bcsave.lua
                    dis_arm.lua
                    dis_mips[....]el.lua
                    v.lua
                    dis_arm64be.lua
                    dis_ppc.lua
                    dis_x64.lua
                    zone.lua
                    vmdef.lua
                    dis_arm64.lua
                    dis_mips64.lua
                    dis_x86.lua
            icons/
                hicolor/
                    scalable/
                        mimetypes/
                            application-x-love-game.svg
        lib/
            libluajit-5.1.so.2
            liblove-12.0.so
            libogg.so.0
            libvorbisfile.so.3
            libfreetype.so.6
            libtheoradec.so.1
            libbrotlidec.so.1
            libvorbis.so.0
            libmodplug.so.1
            libz.so.1
            libbrotlicommon.so.1
            libopenal.so.1
            libSDL2-2.0.so.0
        bin/
            love

Sorry for the long delay. I have been on vacation, then quit my job and lots of stuff has been happening.
I am a bit confused as to how it worked in the past, as there seems to be a dedicated branch for official AppImages that (I guess) worked well with just checking for liblove.so (https://github.com/pfirsich/makelove/blob/master/makelove/linux.py#L234).
That whole liblove check is only relevant when shared_libraries is defined in the config, right? So it's not super, super broken, I think? Would you be willing to contribute the necessary fixes? I'd probably replace that block with something like this:
so_target_dir = find_liblove([
    appdir("lib/"), # pfirsich-style AppImages
    appdir("usr/lib"), # Official AppImages (since 11.4)
])
if so_target_dir == None:
    sys.exit("Could not find liblove.so in AppDir. The AppImage has an unknown format.")

and do find_liblove like this maybe?
def find_liblove(search_dirs: list[str]):
    is_liblove = lambda fname: fname.startswith("liblove") and fname.endswith(".so")
    for search_dir in search_dirs:
        if any(is_liblove(f) for f in os.listdir(search_dir)):
            return search_dir
    return None

This is not tested or anything. And you can do it a different way too, if you want.

Hello, how did you manage to put own custom version of LÖVE? I'm also using LÖVE 12 from the Github Actions page and trying to build with makelove gives me this error: Invalid value for parameter 'love_version'. Expected: One of [11.5, 11.4, ...]. Couldn't find in the makelove-full.toml example file how to do this.


Blockmodification always inserts br after block

Its troublesome to hit delete at blockend to remove this clutter. Please look into it. I strongly doubt this is a browser issue. All chromium browsers i tested on windows demonstrate the same issue. Win10. Edge. Chrome. Brave.

My setup uses a toolbar button to trigger the modifyBlocks method.
my formatting methods all look somewhat like this:
app.formatH2 = function(){
		if (!squire.hasFormat("h2")) {
			squire.modifyBlocks(function(fragment){
				fragment.querySelectorAll("h1,p,h3").forEach(function(block){
					const h = d.createElement("h2");
					h.append(...block.childNodes);
					block.replaceWith(h);
					return h;
				})
				return fragment;
			})
			squire.focus();
		}
	}

Expected outcome is that a block level element such as the h$ and p is replaced by another block level element so that visually and element transforms into another paragraph type.
instead .modifyBlocks also inserts a br after the inserted element.
beforeclick:

content...

afterclick:

content...

my toolbar looks like this:

<button></button>

the buttons fire their events with a common "click" event handler with the useCapture set to false at all times.

I can't reproduce this, sorry.

Will you allow me to clean things up and try with your latest update?


Issue with cdk blueprint version 1.4 when upgrading EKS version v1.21 to v1.23

Describe the bug

Lambda log:
2022-11-04T16:23:17.763Z	f84f8eb0-31d1-4010-910b-935142fb2d11	INFO	onUpdate: {
    "updates": {
        "replaceName": false,
        "replaceVpc": false,
        "updateAccess": false,
        "replaceRole": false,
        "updateVersion": true,
        "updateEncryption": true,
        "updateLogging": false
    }
}

2022-11-04T16:23:17.764Z	f84f8eb0-31d1-4010-910b-935142fb2d11	ERROR	Invoke Error 	{
    "errorType": "Error",
    "errorMessage": "Cannot update cluster encryption configuration",
    "stack": [
        "Error: Cannot update cluster encryption configuration",
        "    at ClusterResourceHandler.onUpdate (/var/task/cluster.js:1:2102)",
        "    at ClusterResourceHandler.onEvent (/var/task/common.js:1:680)",
        "    at Runtime.onEvent [as handler] (/var/task/index.js:1:1434)",
        "    at Runtime.handleOnceNonStreaming (/var/runtime/Runtime.js:73:25)"
    ]
}

Expected Behavior
Upgrade successfully
Current Behavior
Failed
Reproduction Steps
Run cdk deploy
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.50.0
EKS Blueprints Version
1.4.0
Node.js Version
v18.9.1
Environment details (OS name and version, etc.)
macOS 13.0
Other information
No response

I've ran into the exact same error while simply updating @aws-quickstart/eks-blueprints from 1.3.0 to 1.4.0

This looks like a regression from this change https://github.com/aws-quickstart/cdk-eks-blueprints/pull/516.
We are hitting the same error after upgrading from 1.3.0 -> 1.4.0.
According to this https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/1234, I think a cluster created previously than 1.4.0 will have issues.
cc @pflorek

Is there a workaround for this? I'd like to upgrade from 1.3.0 to 1.5.2, but I'm getting this error. I'd rather not create a new cluster in production.

I think I got past this okay, but it's a bad hack. I sub-classed GenericClusterProvider, copied the createCluster code into an overridden method, and hard-coded the secretsEncryptionKey to undefined.
@shapirov103 I'll switch to your upgrade path when it's done. If you want me to take a stab at it, I'm happy to do so, but you might point me to the spot where you think this option should be set. I've not yet contributed to this project, so I'm not intimately familiar with all the code.

Example of creating unencrypted cluster:
    const stack = blueprints.EksBlueprint.builder()
      .account("123456789012")
      .region("us-east-1")
      .useDefaultSecretEncryption(false)
      .build(app, "east-test-1");


Custom Spectrogram sizes using audio frontend

Hi I was wondering if it is possible to customise audio frontend to allow for different sample rates, stride size's and duration size's.
Also is audio frontend faster than ulab's fft

I just hard coded the spectrogram settings used on the reference example.
It's 100% possible to create a config object for the various settings and use it to change the settings used.
https://github.com/mocleiri/tensorflow-micropython-examples/blob/2c4573dbaf41dd391a15276bbe4bd9368ae169c4/micropython-modules/microlite/audio_frontend.c#L82
I.e. make a micropython config object to hold the settings and pass through into the reference example audio frontend at that point.
I didn't know enough at the start about how to use ulab to make the spectrogram.
You would probably need to retrain the network using the ulab spectrogram.  I guess confirm the spectrogram is the same between bumpy ulab.
If you try using ulab I'd be happy to include it as one of the examples.


test: make DebugInfo.macro pass on Windows

The path separator on Windows is \ which is encoded as \5C.  Account for
this in the test.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @adrian-prantl

@swift-ci please smoke test and merge


html引入editor error

请教下，html如何引入editor

引入后，就直接报错了

This issue is stale because it has been open for 60 days with no activity.


FIX: get_pins_name_from_net

Generally, it is more usefull to just retrieve all the pins that are connected to a net, rather than checking if a specific pin belongs to this net. Nevertheless, with the new code you can do both. Also, i fixed the format of the returned name, because the component was not mentioned i.e. FCHIP-B11, but only B11 instead. Problem is that B11 also belongs in BGA-B11 and you cannot identify which of the two it references.


[BUG]- Socket Hang Up

@ckhow, I resolved this by closing another instance of the chia daemon running. I'd recommend checking what processes are using the port.
In Powershell: Get-Process -Id (Get-NetTCPConnection -LocalPort 55400).OwningProcess
On Linux: ss -atp | grep ":55400"


Compile Error

@leinxx   @Zardinality @JiahuiYu
At the beginning, these two errors appear.

After changing the two header files, the following error occurs

This problem has puzzled me for a long time. Is there any suggestion? Thank you.

I think it's because your Tensorflow include the file cuda.h in this manner:
#include "cuda/include/cuda.h"

You can try to make the file visible by adding cuda/include in your LD_LIBRARY_PATH and include cuda.h instead.
For nsync_cv.h problem, try to use the flag -I $NSYNC_INC in g++ commands to include the path.

@knmac
Thank you for your advice, I have solved the previous problem ,mainly the latter error :
g++:error:deform_psroi_pooling_op.cu.o :no such file or directory

@yfnn
I didn't solve this problem, can't find a solution

那你实现可变性卷积了吗

那你实现可变形卷积了吗

@leinxx @Zardinality @JiahuiYu
At the beginning, these two errors appear.

After changing the two header files, the following error occurs

This problem has puzzled me for a long time. Is there any suggestion? Thank you.
How to solve the problem in the first picture？I have the same problem，thank you。

I compiled successfully with gcc-4.9 and g++-4.9, no error.

@yfnn
我编译通过了，在ubuntu gcc5  python3

@YZ-510
I still have one issue as follows.
g++: error: deform_conv.cu.o: No such file or directory
I use familiar command "nvcc -std=c++11 -ccbin=/usr/bin/g++-7 -c -o deform_conv.cu.o deform_conv.cu.cc" to solve the first issue, but there are some errors like this,
In file included from deform_conv.cu.cc:68:0:
deform_conv.h:66:10: fatal error: third_party/eigen3/unsupported/Eigen/CXX11/Tensor: No such file or directory
#include "third_party/eigen3/unsupported/Eigen/CXX11/Tensor"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
How can I solve this?

It's my make.sh, I use gcc-4.9 and g++-4.9:
nvcc -std=c++11 -ccbin=/usr/bin/g++-4.9 -c -o deform_conv.cu.o deform_conv.cu.cc -I $TF_INC -I $NSYNC_INC -I /usr/local -D
GOOGLE_CUDA=1 -x cu -Xcompiler -fPIC -L /usr/local/cuda-8.0/lib64/ --expt-relaxed-constexpr -arch=$ARCH
if you install tf using already-built binary, or gcc version 4.x, uncomment the three lines below
g++-4.9 -std=c++11 -shared -o deform_conv.so deform_conv.cc deform_conv.cu.o -I
$TF_INC -I $NSYNC_INC -fPIC -lcudart -L $CUDA_HOME/lib64 -D GOOGLE_CUDA=1 -Wfatal-errors
-I$CUDA_HOME/include -L $TF_LIB -ltensorflow_framework -D_GLIBCXX_USE_CXX11_ABI=0

@yfnn It's my make.sh, I use gcc-4.9 and g++-4.9:
nvcc -std=c++11 -ccbin=/usr/bin/g++-4.9 -c -o deform_conv.cu.o deform_conv.cu.cc -I $TF_INC -I $NSYNC_INC -I /usr/local -D
GOOGLE_CUDA=1 -x cu -Xcompiler -fPIC -L /usr/local/cuda-8.0/lib64/ --expt-relaxed-constexpr -arch=$ARCH
g++-4.9 -std=c++11 -shared -o deform_conv.so deform_conv.cc deform_conv.cu.o -I
$TF_INC -I $NSYNC_INC -fPIC -lcudart -L $CUDA_HOME/lib64 -D GOOGLE_CUDA=1 -Wfatal-errors
-I$CUDA_HOME/include -L $TF_LIB -ltensorflow_framework -D_GLIBCXX_USE_CXX11_ABI=0

@YZ-510  I am using g++-4.9, and on doing make in terminal, I am getting the following error:
**python setup.py build_ext --inplace
running build_ext
skipping 'utils/bbox.c' Cython extension (up-to-date)
skipping 'utils/nms.c' Cython extension (up-to-date)
skipping 'nms/cpu_nms.c' Cython extension (up-to-date)
skipping 'nms/gpu_nms.cpp' Cython extension (up-to-date)
skipping 'pycocotools/_mask.c' Cython extension (up-to-date)
rm -rf build
sh make.sh
/usr/local/lib/python2.7/dist-packages/tensorflow/include
deform_psroi_pooling_op_gpu.cu.cc:15:0: warning: "CUDA_1D_KERNEL_LOOP" redefined
#define CUDA_1D_KERNEL_LOOP(i, n)
^
In file included from deform_psroi_pooling_op_gpu.cu.cc:10:0:
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_kernel_helper.h:30:0: note: this is the location of the previous definition
#define CUDA_1D_KERNEL_LOOP(i, n)
^
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_device_functions.h(523): error: calling a constexpr host function("real") from a device function("CudaAtomicAdd") is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_device_functions.h(524): error: calling a constexpr host function("imag") from a device function("CudaAtomicAdd") is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_device_functions.h(530): error: calling a constexpr host function("real") from a device function("CudaAtomicAdd") is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_device_functions.h(531): error: calling a constexpr host function("imag") from a device function("CudaAtomicAdd") is not allowed. The experimental flag '--expt-relaxed-constexpr' can be used to allow this.
/usr/local/lib/python2.7/dist-packages/tensorflow/include/google/protobuf/arena_impl.h(57): warning: integer conversion resulted in a change of sign
/usr/local/lib/python2.7/dist-packages/tensorflow/include/google/protobuf/arena_impl.h(304): warning: integer conversion resulted in a change of sign
/usr/local/lib/python2.7/dist-packages/tensorflow/include/google/protobuf/arena_impl.h(305): warning: integer conversion resulted in a change of sign
deform_psroi_pooling_op_gpu.cu.cc(172): warning: variable "transSize" was declared but never referenced
4 errors detected in the compilation of "/tmp/tmpxft_0000248b_00000000-7_deform_psroi_pooling_op_gpu.cu.cpp1.ii".
g++: error: deform_psroi_pooling_op.cu.o: No such file or directory
/usr/local/lib/python2.7/dist-packages/tensorflow/include/google/protobuf/arena_impl.h(57): warning: integer conversion resulted in a change of sign
/usr/local/lib/python2.7/dist-packages/tensorflow/include/google/protobuf/arena_impl.h(304): warning: integer conversion resulted in a change of sign
/usr/local/lib/python2.7/dist-packages/tensorflow/include/google/protobuf/arena_impl.h(305): warning: integer conversion resulted in a change of sign
/usr/local/lib/python2.7/dist-packages/tensorflow/include/google/protobuf/arena_impl.h(57): warning: integer conversion resulted in a change of sign
/usr/local/lib/python2.7/dist-packages/tensorflow/include/google/protobuf/arena_impl.h(304): warning: integer conversion resulted in a change of sign
/usr/local/lib/python2.7/dist-packages/tensorflow/include/google/protobuf/arena_impl.h(305): warning: integer conversion resulted in a change of sign
/usr/local/lib/python2.7/dist-packages/tensorflow/include/google/protobuf/generated_message_reflection.h(685): warning: variable "unused" was set but never used**

4 errors detected in the compilation of "/tmp/tmpxft_0000248b_00000000-7_deform_psroi_pooling_op_gpu.cu.cpp1.ii".
g++: error: deform_psroi_pooling_op.cu.o: No such file or directory
Did anyone solve this?

@appyfizzA
nvcc -std=c++11 -ccbin=/usr/bin/g++-4.9 -c -o deform_psroi_pooling_op.cu.o deform_psroi_pooling_op_gpu.cu.cc
-I $TF_INC -I $NSYNC_INC -I /usr/local -D GOOGLE_CUDA=1 -x cu -Xcompiler -fPIC -L /usr/local/cuda-8.0/lib64/ --expt-relaxed-constexpr -arch=$ARCH
Replace -D GOOGLE_CUDA with -L /usr/local/cuda-8.0/lib64/

Thank you, it ran without error.


Discussion: Stable and unique identifier / label for each Grounded Atom

For indexing within a Space, having a unique identifier for each atom is desirable.  However there are a number of additional considerations assigning these identifiers for grounded atoms.
In a discussion between myself and @vsbogd, we uncovered a tension about what this identifier fundamentally represents; and I believe that tension is rooted in a deeper split between two different conceptual kinds of grounded atom types.
1.) Some grounded atoms represent simple values.  For example wrappers around primitive types in the host language.  These are like the OpenCog Classic atoms; they're conceptually immutable and changing them is functionally equivalent to replacing them with a different atom of the same type but with a different value.
2.) Other grounded atoms represent complex mutable data structures.  For example atom types that wrap Spaces.  We may wish to expose monads to mutate these atoms so MeTTa will be a more "functional" language (see https://github.com/trueagi-io/hyperon-experimental/issues/390) but that's aside from this discussion.  Irrespective of how we track and integrate updates, I don't think we want a change to a complex atom to cause a change its identifier, because this will create considerable bookkeeping complexity and cost.
I believe therefore that the desiderata for the identifiers for the different atom types are different.
For type 1. grounded atoms:

I think we want the identifiers to be computable from each atom's contents.
We'd like the identifiers to be stable regardless of the machine it's computed on (for a future distributed atom space)
This type of identifier is conceptually like a hash

For type 2. atoms:

I think we want the identifiers to be assigned when the atom is created, and not changed by mutating the atom.
These identifiers are volatile, and shouldn't be relied upon across machines, or even runs of the program.

One option is to conceptually separate these types of identifiers in two, by adding a new interface to the Grounded trait, along the lines of:
fn stable_id(&self) -> Option<Some64BitType>;

Therefore, grounded atoms that return a value here can be assumed to be of type 1, and atoms that return None will be assumed to be volatile data structures.
What do you think, @Necr0x0Der and @Adam-Vandervorst?

I think the first type can be best thought of as "symbols with an algebra on top".
I.e., normal symbols don't support any operations, and these do, but other than that they should be treated the same.
The "conceptual hash" can be acheived in a vareity of ways, like flag bits of integers (like Haskell) (or a temporary less messy approach), prefix trees with integer leaves for strings, but the real issue is user-defined types.
Users are bad at writing hash functions, and even worse at writing datastructures eliminating the need for them.
CZ2 uses namespaces, but this assumes that all values of a given type are unique unless explicitely unified. That is, two classes (even if they share the same value) are considered different (for user types). This is different from built in types in CZ2 like ints and strings, which are content-addressed.
So even though we may like these two to be seperate, it may not be easy to rely upon for arbitrary grounded atoms.
For networked systems, we may also want to look at longer identifiers, like OpenCog classic's UUIDs.
There's also the option of being explicit: have a MeTTa function value that returns the values associated with an id, in the case we don't do content-addressing by default.

I think the first type can be best thought of as "symbols with an algebra on top".

That's a very good point!  Rather than trying to shoe-horn two conceptually different types of object into Grounded Atom, it might be better to extend Symbol Atom so certain subclasses of symbol atoms can have custom parsing, stringification for display, and native operations that can interact with them.  I like this idea a lot.

Yes, though the "functional programming interpretation" would lay the responsibility on the functions. I.e. instead of symbols overwriting (OOP term) it'd be implementing support for symbols.
Concretely, say you have integer addition add and  HDC bind xor, it'd be the add's responsibility to load the integers from the symbol identifiers (which would just be cast or a bitwise op), compute it, and wrap it back in an identifier, and xor's responsibility to load hypervectors from a store using an index parsed from the identifier, do the calculation, store the result, and put the new index (along with it's type identifier) back into an symbol.
Ultimately the two ways of looking at the problem are equivalent, "extending functions to support" is the MeTTa way, but I wouldn't mind a performant backend diverging from it and just dispatching the right methods.
It's worth it to ponder how both options scale to pre-compiled libraries, network stuff, JIT, and more future directions.

I don't like the idea to mix up symbols and grounded atoms in a hard-coded way. Symbols should be fully interpretable in MeTTa. If you want an algebra over symbols, don't implement it in an opaque way in some imperative language. Implement it in MeTTa. Of course, there are always intermediate cases, when we want both symbol-like behavior and efficient computations. But this can be done in other ways without introducing substructures to symbols. Once again, we already have expressions for describing symbolic structures.
While there is indeed some variety of grounded atoms, it's not a dichotomy.  For example, numbers as grounded atoms are not mutable, but it makes not too much sense to search for very particular number in an efficient way (if there is such a need, turn these numbers into symbols). In contrary, states are intentionally mutable, but we may want them to be efficiently searchable. A whole neural network wrapped in a grounded atom can have hash, but not only for searching but for fast comparison (e.g. we've loaded a network to GPU and want to check if this is the same network or not, when we want to switch to another checkpoint). We may want to search for images in a huge collection. But it is a different use case from retrieving a MeTTa expression containing a grounded atom wrapping an image. Hashing, indexing, retrieval for grounded atoms cannot be done in a universal way, and we cannot demand to craft a hashing function for each type of the grounded data as Adam mentioned.
We do want to make searching for grounded atoms fast in some cases, but there are different options. First of all, different spaces may do indexing in different ways (e.g., DAS), and we cannot require them to do this in one way. It is not a bug, but a feature, because different spaces are optimized for different use cases. If one wants to have a space for images, then not just a special hash, but special retrieval mechanisms will be implemented for them (which may or may not retrieve not identical but just similar images, for example). As a consequence, hashes are optional for grounded atoms and if they have IDs, this IDs live inside corresponding spaces. If we want grounded atoms with global UUIDs, the answer will be not to introduce this as a requirement to any grounded atom, but to introduce a special grounded atom, which wraps any data with the requirement for it to have a hash function.
Thus, the right question is what use cases we have for the in-RAM space, and wouldn't it better to solve these cases by other approaches?..
In general, I imagined that each type of grounded atom may (optionally) have its own retrieval mechanism. If it has, it is responsible for creating an index and search within this index (it is an extension of custom pattern matching from individual grounded atoms to their types). Relying on the retrieval mechanisms designed for symbolic expressions by providing hashes for individual atoms is a weak approach. I'm not sure, though, to what extent custom indexes for grounded atom types is easy to introduce into the current implementation.

Based on the above, I go down the following chain of logic.  Please correct me if I've made some leaps that don't logically follow.
1.) A Space is fundamentally responsible for keeping track of its atoms
2.) Grounded atom interfaces are broadly customizable and it's not realistic to shoehorn all grounded atoms into something like a 64bit GUID.
3.) Linearly calling Grounded::match_ on all atoms in a space for each query is a non-starter.
Therefore:
4.) Grounded atoms can only be matched in a Space if either A.) The space is aware of the particular structure of the GroundedAtom type, and is thus able to index it. or B.) The GroundedAtom is embedded in an expression that otherwise matches a query, and narrows down the possible atoms to a very small set.
But a big class of GroundedAtoms should be efficiently indexable in the default Space implementation.  So we're back to an optional interface, as was proposed initially.

1.) A Space is fundamentally responsible for keeping track of its atoms

I'd say, yes. I'd say, definitely yes, if we consider specific grounded atom types as a part of some space (atm, it is not precisely technically true, but still conceptually true).

2.) Grounded atom interfaces are broadly customizable and it's not realistic to shoehorn all grounded atoms into something like a 64bit GUID.

I'd say, yes. At best, we can ho have a global ID for all atoms for some concrete default or broadly used type of space (say, DAS, but not necessarily), if this is a particular feature of this space. But I'd say that this should not be the case for the in-RAM space of the interpreter.

3.) Linearly calling Grounded::match_ on all atoms in a space for each query is a non-starter.

Linearly calling it is definitely not scalable. There is a benchmark for a not hashed State for this
https://github.com/trueagi-io/hyperon-experimental/blob/main/lib/benches/states.rs
Apparently, it is feasible only for rather small spaces.

4.) A.)

Kind of yes. Words are a little bit vague, so it depends on precise meaning of "space is aware".

4.) B.)

yes

But a big class of GroundedAtoms should be efficiently indexable in the default Space implementation. So we're back to an optional interface, as was proposed initially.

Yes, but the question is in details. The interface should be optional. Big classes of GroundedAtoms can be responsible for indexing and retrieval. The indexing and retrieval mechanism for such big classes should not be hardcoded in the default Space implementation. It should be kept modular and customarily extensible.  Is an index built by a custom GroundedAtom type a part of a Space -- this is where the wordings become a little vague.
In any case, there can be a default indexing / querying implementation, which requires only hashes from those GroundedAtom types, which are ok with it.  Thus, one can implement just a hash function and be happy. However, the Space querying mechanism should not rely on these hashes. Instead, it should delegate querying to GroundedAtom types. The tricky thing is that adding / removing atoms should also require calling corresponding methods of such GroundedAtom type implementations. One may propose to go further and create another more basic implementation of such a generic class without indexing. In this case, all grounded atom types will have the same (obligatory, but with two default simplified implementations) interface. I'm not sure what are computational overheads and inconveniences in this approach, so I'm not insisting on it.

1.) A Space is fundamentally responsible for keeping track of its atoms

Actually this is vague for me. What does "keeping track" specifically means here?

2.) 3.)

I agree with Alexey's answers above.

4.) A)

It is a question to what degree atomspace should be aware of a structure. I see few different degrees of awareness here:

Space is aware that atom has some custom index, space is responsible to pass to the atom's type all the necessary information to support this index (for instance whether atom of this type was removed or added). Space keeps the content of the index as part of itself but space doesn't know how this index works, thus the index itself is a blackbox for the space.
Space implements specific algorithms to index grounded atoms of the specific types (for instance specific kind of space to keep and search images).

In the first case we have more universal space implementations and move grounded atoms indexing into a separate abstraction "grounded atom type", but any space can work with any kind of grounded atom. In the second case we have more specific space implementations and handling grounded atoms with different indexing logic under a single space becomes tricky and requires making space implementation more and more complex.
Thinking about using DAS in the first case DAS implementation need somehow keep index with unknown structure inside and keep it in a distributed manner which is not possible without additional knowledge about internal index structure. In a second case DAS should implement many indexes for the grounded atoms in a distributed manner.

adding @andre-senna in the thread

I am seeing a common theme connecting this thread with https://github.com/trueagi-io/hyperon-experimental/issues/408 ,
https://github.com/trueagi-io/hyperon-experimental/issues/409, the part of this comment concerning unwieldy StateAtom usage:
https://github.com/trueagi-io/hyperon-experimental/pull/433#issuecomment-1722134412 , @ngeiswei 's issue here: https://chat.singularitynet.io/chat/pl/kzpzkioextryfnnmas9zzk5c5o  and certainly other issues / points of confusion.
Basically they all come down to names for certain grounded atoms, and when a grounded atom is mixed up with a symbol.
This might be controversial, but how about letting grounded atoms have an Optional string name.  Spaces resolve symbols matching the name (in the appropriate context) as references to the grounded atom.

This might be controversial, but how about letting grounded atoms have an Optional string name?

Assigning some name to the atom can be done implementing #134 (and I was going to implement it). Another question is how to construct and add (= <name> <grounded>) expression for the new grounded atom. It can be easily done from Rust or Python calling space.add_atom() thus I think it makes adding names for the grounded atoms unnecessary. And we could implement a variant of bind! which doesn't modify the tokenizer but instead adds such equality to the atomspace.

I am seeing a common theme connecting this thread with...

Yes

This might be controversial, but how about letting grounded atoms have an Optional string name?

Please, see my comment.
https://github.com/trueagi-io/hyperon-experimental/issues/409#issuecomment-1742055716
While grounded atoms with optional names is a possible partial solution, I believe that we need to take other aspects into consideration. From the AGI-ish / cognitive architecture perspective, both symbols can be built on top of subsymbolic patterns and subsymbolic data / functions can originate from "compiling" symbolic declarative knowledge. Thus, I'd prefer to have a more flexible and rich mechanisms (possibly partly describable in MeTTa itself) for associating symbols and grounded atoms than having string names or hash-like identifiers optionally attached to grounded atoms.


Adding proponent version of csv export

Issue #: https://github.com/bcgov/met-public/issues/2136 https://github.com/bcgov/met-public/issues/2133
Description of changes:

Backend changes to extract comment data for proponent. This will include comments that are viewable by the public i.e. approved comments and comments that are set as display in report settings.
Changed the notification util to check for single tenant environment to create the site url
Front end changes to move the export to csv button to the "Read all comments" page and add a drop down on the button to either select staff/proponent version to download.
Added new template for proponent version

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

Codecov Report

Merging #2209 (b4b5d95) into main (43df78a) will decrease coverage by 0.18%.
The diff coverage is 41.17%.

@@            Coverage Diff             @@
##             main    #2209      +/-   ##
==========================================
- Coverage   68.78%   68.61%   -0.18%
==========================================
  Files         469      469
  Lines       15232    15279      +47
  Branches     1183     1182       -1
==========================================
+ Hits        10477    10483       +6
- Misses       4555     4596      +41
  Partials      200      200

Flag
Coverage Δ

metapi
76.92% <41.17%> (-0.41%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

met-web/src/apiManager/endpoints/index.ts
100.00% <ø> (ø)

...nents/comments/admin/reviewListing/Submissions.tsx
81.39% <ø> (-3.52%)
:arrow_down:

met-web/src/services/commentService/index.tsx
36.36% <ø> (-2.10%)
:arrow_down:

met-api/src/met_api/services/comment_service.py
68.20% <14.28%> (-13.81%)
:arrow_down:

met-api/src/met_api/models/comment.py
73.22% <33.33%> (-1.98%)
:arrow_down:

met-api/src/met_api/utils/notification.py
64.28% <75.00%> (+1.78%)
:arrow_up:

met-api/src/met_api/resources/comment.py
79.24% <76.47%> (-10.50%)
:arrow_down:

met-api/src/met_api/utils/enums.py
100.00% <100.00%> (ø)


Error on build eas project

Build/Submit details page URL
No response
Summary
I'm trying to run the eas build command but unexpectedly, even logging into the apple developer account, I get a cookie error in the terminal...
I looked at several posts on github but nothing helped me... I've tried uninstalling eas and installing it, deleting cookies, running eas install --fix, deleting all modules, changing the password, using vpn but NONE of it has helped.
Managed or bare?
Bare
Environment
EAS CLI 7.1.3 environment info:
System:
OS: Windows 11 10.0.22631
Binaries:
Node: 20.10.0 - C:\Program Files\nodejs\node.EXE
npm: 10.2.3 - C:\Program Files\nodejs\npm.CMD
Utilities:
Git: 2.42.0. - /c/Program Files/Git/cmd/git
npmPackages:
expo: ~50.0.6 => 50.0.6
expo-updates: ~0.24.10 => 0.24.10
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.73.4 => 0.73.4
react-native-web: ~0.19.6 => 0.19.10
Project workflow: managed
Error output
√ How do you want to validate your account? ... device / sms
√ Please enter the 6 digit code ... 762385
√ Valid code
√ Logged in and verified
Authentication with Apple Developer Portal failed!
Cookie not in this host's domain. Cookie:developer-mdn.apple.com Request:developer.apple.com
Error: device:create command failed.
Reproducible demo or steps to reproduce from a blank project
eas build -p ios --auto-submit

Duplicate https://github.com/expo/eas-cli/issues/2224#issue-2128657151


NIFI-8764 Refactored UnpackContent to use Commons Compress and Zip4j

Description of PR
NIFI-8764 Refactors UnpackContent to use Apache Commons Compress for reading standard Zip files and Zip4j for reading encrypted Zip files.  The presence of a value in the Password property results in using Zip4j, otherwise Apache Commons Compress will be used.  This approach provides greater compatibility for compression algorithms supported in Apache Commons Compress that are not supported in Zip4j, while also maintaining support for decryption of password-protected Zip files as implemented for NIFI-7777.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[X] Have you written or updated unit tests to verify your changes?
[X] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

+1 LGTM, thanks for the improvement! Merging to main


Set up Heroku pipeline

For development, staging, and production.
https://devcenter.heroku.com/articles/pipelines

Alright – all set up!


-n not work

i want it download with 5 connections but it download with 2 connections .
./hget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.8.10.tar.xz -n 5
INFO: Resolve ip: <IP_ADDRESS>
INFO: Start download with 2 connections
INFO: Download target size: 87.7 MB
linux-4.8.10.tar.xz-0 800.15 KB / 43.86 MB [>--------------------]   1.78% 2m57s
linux-4.8.10.tar.xz-1 735.48 KB / 43.86 MB [>--------------------]   1.64% 3m13s
INFO: Interrupted, saving state ...

yes ,  seems -n not work

./hget [file_to_download] -n 2  not works
./hget -n 2 [file_to_download]  works for me

Flags in Go have certain behavior. There is a quote from the docs:

Flag parsing stops just before the first non-flag argument ("-" is a non-flag argument) or after the terminator "--".

So I suggest that it would not be fixed because of the Go package design.

so it seems that this is just usage problem, so i will close this issue

This is still an issue.
Even when running hget --help its indicated that it's acceptable to use the flags after the URL.


Consider domain-fronted dp5-based presence tracking

See: http://cacr.uwaterloo.ca/techreports/2014/cacr2014-10.pdf
This protocol is the complement to the identity info we may get from social networks, or even from a manual copy-paste connection.  It gives you the long term ability to track a known users presence (online-ness) and transmit a status (your IP and listening webRTC info) without the server being able to link users or know who is friends with whom.
this seems like basically what we want. The only trick is that the server portion of dp5 needs to be hosted somewhere accessible.  We could initially consider a domain-fronted location for such a service, or longer term look into what is involved in a more distributed incarnation of the server component of this protocol.
There's a recent talk on this with some additional resources here: https://www.youtube.com/watch?v=oSnYmMHp-o8

Reference code implementation: git://git-crysp.uwaterloo.ca/dp5


Support custom UniversalResolver for ENS resolution

Description
Currently, Viem has added support for custom UniversalResolver, as shown in https://github.com/wagmi-dev/viem/blob/main/src/actions/ens/getEnsAddress.ts
export type GetEnsAddressParameters = Prettify<
  Pick<ReadContractParameters, 'blockNumber' | 'blockTag'> & {
    /** Name to get the address for. */
    name: string
    /** Address of ENS Universal Resolver Contract. */
    universalResolverAddress?: Address
  }
>

Type GetEnsAddressParameters support passing custom universalResolverAddress
However, Wagmi doesn't support custom UniversalResolver yet, as shown in https://github.com/wagmi-dev/wagmi/blob/main/packages/core/src/actions/ens/fetchEnsAddress.ts
export type FetchEnsAddressArgs = {
  /** Chain id to use for Public Client. */
  chainId?: number
  /** ENS name to resolve */
  name: string
}

Type FetchEnsAddressArgs doesn't support passing custom universalResolverAddress
This pull request adds custom UniversalResolver support, as shown in

Core: https://github.com/Opti-domains/wagmi/tree/universal-resolver/packages/core/src/actions/ens
React: https://github.com/Opti-domains/wagmi/tree/universal-resolver/packages/react/src/hooks

export type FetchEnsAddressArgs = {
  /** Chain id to use for Public Client. */
  chainId?: number
  /** ENS name to resolve */
  name: string
  /** Universal Resolver contract address */
  universalResolverAddress?: `0x${string}`
}

Type FetchEnsAddressArgs now support passing custom universalResolverAddress
export function useEnsAddress({
  cacheTime,
  chainId: chainId_,
  enabled = true,
  name,
  scopeKey,
  universalResolverAddress,
  staleTime = 1_000 * 60 * 60 * 24, // 24 hours
  suspense,
  onError,
  onSettled,
  onSuccess,
}: UseEnsAddressArgs & UseEnsAddressConfig = {}) {
  const chainId = useChainId({ chainId: chainId_ })

  return useQuery(
    queryKey({ chainId, name, scopeKey, universalResolverAddress }),
    queryFn,
    {
      cacheTime,
      enabled: Boolean(enabled && chainId && name),
      staleTime,
      suspense,
      onError,
      onSettled,
      onSuccess,
    },
  )
}

useEnsAddress now supports passing custom universalResolverAddress
Benefits
Benefits of supporting custom UniversalResolver include but are not limited to

Supporting resolving of custom wildcard subdomain in Wagmi (ENSIP-10: Wildcard Resolution)
Supporting the development and adoption of ERC-3668: CCIP Read: Secure offchain data retrieval and ENS Layer2 and offchain data support which require custom gateway urls.
Allow dapp to voluntarily adopt a newer version of UniversalResolver before it is officially released by the ENS DAO (ENS has pushed an update to UniversalResolver but hasn't released it yet: https://github.com/ensdomains/ens-contracts/blob/dev/contracts/utils/UniversalResolver.sol)
Allow ENS name resolution on other chains, especially EVM-compatible ones such as Arbitrum and Optimism.

An example of utilizing a custom universal resolver address in Wagmi can be found in Opti.domains's Rainbowkit customization that has added ENS name resolution support on the Optimism chain.
https://github.com/Opti-domains/rainbowkit/tree/universal-registry
These benefits will apply to apps and libraries using Wagmi, such as Rainbowkit.
Additional Information

[X] I read the contributing docs (if this is your first contribution)

Your ENS/address: chomtana.eth, optidomains.eth

Appreciate you working on this! Currently, working on an update to Wagmi that will all passing through all Viem action parameters to Wagmi Core actions and Wagmi React hooks. Once that is ready, it will capture this.


PDF links are not recognised and not added to the metadata

Describe the bug
When we try to load a PDF file with links that was generated by Word then the links are not recognised. In comparison when we load the unstructured sample PDF the links are extracted. When we use a tool such as pdfx we can see that the links are in the document.
To Reproduce
Load attached PDF file with unstructured
Expected behavior
Extract the link 'Klick Here' with link to 'https://ebay.com'
Screenshots

pdf-link.pdf
embedded-link.pdf

We do use unstructured version 0.12.3

We can read the links. We had to set the threshold to a lower value:
https://github.com/Unstructured-IO/unstructured/blob/dd6576c603da10f42b39a71d13aef7fcc8b99528/unstructured/partition/pdf.py#L1179

What would be potential side effects of setting a lower threshold value?

Currently it seems this cannot be passed as a parameter, but would be nice to allow to configure this from the outside if needed?

I have refactored 'threshold' to 'annotation_threshold' and made it an optional parameter in '_process_pdfminer_pages' by keeping the default at 0.9.
With that we do have the option to make it configurable. It would be very helpful if @christinestraub you could merge that. We do have automated deployments which makes it complicated and cumbersome to workaround.
https://github.com/Unstructured-IO/unstructured/pull/2537
Thanks!

Is there any interest to address this? I know sometimes open-source projects are like this. Dead slow and nobody cares.
Do we need to consider forking or move to another library?
There is a bug, you labeled it as a bug, so you I assume you acknowledge there is a problem. There is a MR, the change is damn simple, you only need a single minute to read it.
Would be great if somebody can comment somehow. Otherwise we can assume while it's a great library it's not really maintained. If you want to an open source library accepting community MR please have capacity to review them!
"We don't care" would also already be a comment.

Hi @MiXiBo @sjoerd222888 thanks for your contribution to address this issue. I have been involved in working on urgent tasks . I have time to look at your PRs now and will update you as soon as possible.

addressed by PR #2537.


Fix issue with using a callable as a learning rate.

Closes #19411.

CLA issues, will open a new one.


Look into direnv for software development environments

direnv is a tool that is apparently useful to set environment variables and enter development shells upon entering specific directories. This could be useful in order to automatically open dev shells with certain projects. So far, it's unclear how exactly this would work and whether this is even the right place to add the tool. Maybe this needs to actually be added to coding projects instead of the system configuration. But it's definitely worth checking out.

Closed with af2fdb1


T64979: Weighted Normal

Ticket from blender issue tracker:
https://developer.blender.org/T64979

I'm hopeful that this might be a duplicate of #436 which I think got fixed today (but I didn't test the fix myself yet).

Closing here & in blender issue tracker, fix is now merged in blender master


Emmet increment/decrement by 0.1 Error

VSCode Version: 1.14.2
OS Version: MacOS 10.12.6

Steps to Reproduce:

Emmet Increment/Decrement by 0.1

Reproduces without extensions: No

Nice catch @sou-lab !
Thanks for logging the issue. Fixed with https://github.com/Microsoft/vscode/commit/9b6cc9f774f424b4e8a91d4a2d3d4ad8efb9cfb9
Looks like you have set emmet.useNewEmmet to true
Please do try out rest of the emmet commands and file issues if you find any
I intend to set emmet.useNewEmmettotrue` by default in the next update (1.15)

Thank you for support😃
I try Insiders on Monday.

Err. This issue is not fixed when using hex-color codes(I'm hunting for edge cases 👅).
Having this:
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <meta http-equiv="X-UA-Compatible" content="ie=edge">
    <title>Document</title>
    <style>
        body {
            background-attachment: fixed;

            color: #231230;
        }
    </style>
</head>
<body>

</body>
</html>

Select the code:

Decrement it by 0.1:

Not bad, isn't it?

@jens1o Am confused... what is not fixed?

Hex-Colors can't be decremented by 0.1 nor incremented at all, because Hex Colors only can be three or six digits number prepended by a #. So it's not possible to decrement them by this step, so I would expect an error message.
Personally, I would like that the steps will be converted to hex number and then let the math happen. At the moment, emmet does not care about different number systems.

Updated to show error message if unable to evaluate given expression

Err, that's not fixing this problem? You can still increment hex color codes, can't you?

So it's not possible to decrement them by this step, so I would expect an error message.

I was addressing the error message part of your comment
We can use #31681 which you logged to track the hex color code issue

Okay.


Built-in protection policy targeted users

Hello, I have a question about the Built-in protection policy.
In the docs, it says that by default, the Built-in protection policy will be applied to all receipents.
Will the policy be applied for users without a MDO license as well?
For example, lets say a company with 10,000 users buys only 500 MDO licenses for a POC
In this case, will the built-in protection policy be applied to all 10,000 users or just 500 users?
If its going to be applied for all users, will it be applied right after the license gets enabled?
Since the Built-in protection policy is set to "Block" for Safe attachment policies,
cutomers might be surprised when the POC affects all users rather than the specified users.
Thank you

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

ID: 4f6f1cf3-a121-3c6e-9380-79440f4c6671
Version Independent ID: 9b1bc5d1-8ecc-d0f9-092e-325c6acff4fe
Content: Preset security policies - Office 365
Content Source: microsoft-365/security/office-365-security/preset-security-policies.md
Product: m365-security
Technology: mdo
GitHub Login: @chrisda
Microsoft Alias: chrisda

@ShawnHag, I believe MDO licensing is a requirement. I'm not sure if it's a code/technical requirement, or an 'honor system' kind of requirement. I'm pretty sure that users don't get MDO protection of any kind unless they're assigned an MDO/E5 license, so I doubt that Built-in protection is any different.

@ShawnHag Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

Thank you for reply!
Sorry for the late response.. I was away for few days.
I will try this out and see if it gets applied for non-license users..


same package name in multiple fidl files

I check the latest Version 0.2.1 and run into some trouble with the processor. The process checks that the package.name  is not defined in multiple files. But as I understand Franca IDL this is a valid syntax. The package.name is the scope of the interfaces and typecollections and I can split a scope over multiple files.
Attached please find 2 fidl files. Your validator told me a circular dependency. But the official CommonAPI Generator accept these fidls files.
fidl_validator.py  -I packages Hello.fidl  definitions.fidl
ERROR: Circular dependency for package 'myPackage'.
As I understand franca_processor.py the problem is that you use the package.name as the key name of an package. If you take a look into my franca_validator.py I use the fidl file name as the key name. I am not sure that the fild file in the import instruction is just the file name or is it a path. I assume it is a path. The franca user guide does not sepcify the import instruction completely.
import myPackage.MyTypes.* from "definitions.fidl"
franca_processor.py Line 339
self.packages[package.name] = package
franca_validator.py Line 34
abs_path = os.path.abspath(fspec)
self.packages[abs_path] = fpackage
best regards
jens
fidl.tar.gz

You are correct - using the same package name in multiple files is valid Franca syntax.
The decision, not to support this in the first release of the processor module was intentional so that the implementation can be simplified. This is currently stated in the README as a limitation. Supporting packages, spread across multiple files is not very hard but requires validation that there are no duplicate member definitions in multiple files.
I would like to still use the package name as a key in the packages dictionary. Instead, packages, declared in multiple files can be merged together by the processor.
I can give this a try in the next few days if you help with validating the correct behavior afterwards.

Sorry I miss reading the updated limitations.
I realy like the idea of merging packages, declared in multiple files together. This is better then my approach in franca_validator.py. I can support you in validating the behavior.

This turned out to be much easier than I expected. The dev branch now interprets correctly the example that you provided.
Looking forward to your feedback.

Released with v0.3.0 .


Add systick and delay functionality

This implements a delay milliseconds function, and the HAL for the systick peripheral.
It is not complete yet. It is missing:
mtimer compare register functionality
Delay for us, s, etc.
I believe the delay_ms function needs some work to make more accepting of other types.
I've tested this and it works on my nano, however  I did not test different clocking speeds yet.

Great! Review today. Thanks )


missing Attribute _hamiltonian_dot_nocheck in 'me' method

'me' method is not working because of missing Attribute: _hamiltonian_dot_nocheck.

fixing in next version


Speech endpoint in UK South returns 401 unauthorized

Despite being marked as available in UK South, the Speech API returns authentication failure when executing the quickstart code.
ErrorCode=AuthenticationFailure
ErrorDetails="HTTPAPI result code = HTTPAPI_OK. HTTP status code = 401."

The status page says that the service is up and running, and with credentials from West Europe it works.
To Reproduce
Execute the quickstart C# code with key and region from a subscription in UK South.
I actually tried it with the following F# script but it should be the same:

open System
open Microsoft.CognitiveServices.Speech

[<EntryPoint>]
let main argv =
    Console.Write "type something you want to speak: "
    let line = Console.ReadLine()
    let config = SpeechConfig.FromSubscription("mykey", "uksouth")
    config.SpeechSynthesisVoiceName <- "en-US-GuyNeural"
    use synthetizer = new SpeechSynthesizer(config)
    let task = line |> synthetizer.SpeakTextAsync
    task.Wait()
    match task.Result.Reason with
        | ResultReason.Canceled ->
            let cancellation = SpeechSynthesisCancellationDetails.FromResult task.Result
            if CancellationReason.Error = cancellation.Reason then
                printfn "ERROR: ErrorCode=%A" cancellation.ErrorCode
                printfn "ERROR: ErrorDetails=%A" cancellation.ErrorDetails
        | _ -> printfn "Everything OK"
    0

Version of the Cognitive Services Speech SDK
1.6.0 (as NuGet package)
Platform, Operating System, and Programming Language

OS: Linux 5.1.15, Arch
Hardware - x64
Programming language: F#, C#

I can not reproduce this problem. The C# quickstart code (and the 1.6 version of the SDK) work fine for me with in the uksouth region with a uksouth subscription key, with a westeurope subscription key it works against the westeurope region.
You can't mix regions/keys ...
Wolfgang

Thanks for the reply. I believe I did not mix keys and regions. I'll try again between today and tomorrow and let you know if this is is still happening or close the issue.

It works now, on Windows. There must be something wrong with the configuration of my Linux box. Closing for now. Thanks anyway!


Permission request + Wrong CSW status

Experiencing similar problem as #124:
When not using intent-filter and only requesting permission inside MainActivity, the application works fine. The problem is that with usbManager.requirePermission() the user "default checkbox" selection is not saved and the permission dialog keeps opening each time USB device is attached.
Now I tried adding intent-filter with USB_DEVICE_ATTACHED action code which by documentation should save permission choice that user selected the first time.
The first time USB is attached the code works like it should - but each next time USB attaches, the library throws me:
E/UsbDocumentProvider: error setting up device
    java.io.IOException: Unsuccessful Csw status: 1
        at com.github.mjdev.libaums.driver.scsi.ScsiBlockDevice.transferCommand(ScsiBlockDevice.java:184)

Any ideas why this would happen?
I understand if library was throwing this in both cases (using intent-filter and just requesting for permission) but what bothers me is that when manually requesting for permission, library works as supposed but when using filter-intent not.

Did you try the delay with sleeping proposed in issue #124 ?

Yes, also tried that with no success.
Tried from 1 second to 5 and also on both .init and when searching. No luck.
Any other idea?

In some other thread, they suggested ignoring the CSW status overall. Apparently, everything still works fine. But this is obviously wrong specification-wise. Maybe there is also a bug related to parsing the CSW status. Did you try different pen drives?

Sorry didn't yet. Only tried with single one, also tried reformatting it few times FAT, FAT32 and still the same.
Will try it out with different one and report back here.

Same here, Unsuccessful Csw status: 1. I tried with a 5 seconds delay from permission request to .init(), but it doesn't change. I'm using an USB-C "hub", where you can simultaneously attach USB pen drives or SD card. AUMS sees both, but the USB pen drive works, and the SD card reader throws that error.

Hey @lorenzos I havent tried sd card readers in while, but I remember that lots of them caused troubles :/
Did you try removing this check completely?

@magnusja I did not. If I clone the repo locally and load "libaums" folder as a local gradle module, it should work as it is? Doesn’t require additional building steps, etc? Thanks.

Yes that should work

@magnusja Just tried, unfortunately removing the check doesn't bring me far: I immediately get a Could not read from device, result == -1 errno 88 Socket operation on non-socket :sob:

Yes I tried to get some more error information because Android API only throws an exception with no information at all but it seems that the errno from C is not really related to the USB error.

Hi @magnusja
I had been testing your library and got into the similar problems:
Unsuccessful Csw status: 1
durning the transfer of the TEST_UNIT_READY command.
It occurred only when using card reader device. When using the USB pen drive there was no problem. I discovered there is by default LUN set to the 0. In the case of the card reader device every physical slot has its logical unit assigned. So if I change the LUN then corresponding card reader port starts working.
Right now there is no possibility to choose the LUN in the code. If you agree with that I would like to help you with implementation of this functionality. But I have no time for waste so I want to consult it before I apply for the pull request so we prevent some useless steps.
I suggest to add some methods into ScsiBlockDevice for setting LUN and getting information about it. Or adding another layer of abstraction and adding the container of some class representing its ports into the ScsiBlockDevice. Also durning the initialization there should be the process of recognition of those ports. Any other solution? What do you think?

I wish I had seen your post earlier @lukasniedoba.
I also debugged for a while today and came to the same result as you.
I made a pretty easy fix for it. It works, but it's ugly.
There is certainly a better solution than this fix. Removed hardcoded LUN

Hey @lukasniedoba , @timcrid ,
thanks for the support! I am always happy to take PRs. The LUN thing has been on my list for a while now.
@timcrid Your solution works but is probably a little hacky :D
@lukasniedoba The best solution imho would be if the user of the library does not really need to change anything. He or she just sees an additional device for each inserted SD card. Maybe additional partitions of a particular device would also be fine. In terms of implementation I am not a 100% sure. If on device level we would need some kind of wrapper around the ScsiBlockDevice which creates a new device for each LUN and returns it to the user. This probably needs some refactoring on device handling. The other option would be to just create a new partition for each LUN. Maybe it would also be possible to implement the notion of "subdevices" for  ScsiBlockDevice when it turns out it is an SD card reader. What do you think?

Looking at the code, maybe it makes sense to hook in here: https://github.com/magnusja/libaums/blob/develop/libaums/src/main/java/com/github/mjdev/libaums/UsbMassStorageDevice.java#L230
And just loop over the max LUNs and create a new mass storage device for each LUN.

@timcrid @lukasniedoba can you please try this: https://github.com/magnusja/libaums/pull/201

Hey @magnusja
Nice work!
I tried it with a normal USB stick and with a USB card-reader and it works fine.

awesome :) will merge, will be in the next release


Deleting a user from the database.

Deleting via command:

/comedianremove @username

Need to do:

method for db;
method for api;
test for bd;
test for api.

DeleteStandupUser deletes standup_users entry from database
func (m *MySQL) DeleteStandupUserByUsername(username, channelID string) error {
	_, err := m.conn.Exec("DELETE FROM `standup_users` WHERE username=? AND channel_id=?", username, channelID)
	return err
}


Hackerman Created

Hackerman finished. Its possible that in the future I would need to add a velocity cap, but its working for now

@Galaxy25 Still got some merge errors.

I'm getting ready to merge and updating the change log - please @me if any other changes are pushed.


Add exclusion of the tests in CLI

Which components does the task require to be changed?
snforge
Description
We should add a regex which would make it able to exclude certain file/path/test name patterns
We should also investigate how other tools approach this

Hey!
I'd like to work on it please

@julienbrs feel free to submit a PR (or propose changes in a comment so we can give you some tips before you work on this)

Will submit a PR tomorrow

cc @Arcticae PR opened, would be awesome to have any thoughts on it


[5.7] fix a crash/hang in SimplifyCFG.

Jump threading in an unreachable CFG region can lead to a crash (in an assert compiler) or hang (in an no-assert compiler) in ValueBase::replaceAllUsesWith.
Unfortunately I couldn't come up with an isolated SIL test case.
rdar://92267349

@swift-ci test

Cherry-pick of #58387


Word Count usage example

This should demonstrate how the industry standard example "word count" would look with our scalaz-analytics API.
For reference:
Spark:
https://github.com/databricks/learning-spark/blob/master/mini-complete-example/src/main/scala/com/oreilly/learningsparkexamples/mini/scala/WordCount.scala
https://github.com/apache/spark/blob/master/examples/src/main/scala/org/apache/spark/examples/streaming/HdfsWordCount.scala
Flink:
https://github.com/apache/flink/blob/master/flink-examples/flink-examples-batch/src/main/scala/org/apache/flink/examples/scala/wordcount/WordCount.scala

Taking a stab at it.


Tutorial 2 fails in spod.get_data

Hello,
when running the tutorial 2,in the line 138 'data = spod.get_data(data)'  and the error shows up. Could anyone give me a hand to solve it?
Best wishes!
XUxu
The error log is shown as below:
Reconstructed data saved in: D:\spod\PySPOD-main\tutorials\tutorial2\spod_results\nfft730_novlp0_nblks10\coeffs_0_365\reconstructed.npy
Elapsed time: 0.45338940620422363 s.
C:\ProgramData\anaconda3\envs\spodProject\lib\site-packages\matplotlib-3.9.0-py3.9-win-amd64.egg\matplotlib\cbook.py:1762: ComplexWarning: Casting complex values to real discards the imaginary part
return math.isfinite(val)
C:\ProgramData\anaconda3\envs\spodProject\lib\site-packages\matplotlib-3.9.0-py3.9-win-amd64.egg\matplotlib\cbook.py:1398: ComplexWarning: Casting complex values to real discards the imaginary part
return np.asarray(x, float)
C:\ProgramData\anaconda3\envs\spodProject\lib\site-packages\matplotlib-3.9.0-py3.9-win-amd64.egg\matplotlib\cbook.py:1762: ComplexWarning: Casting complex values to real discards the imaginary part
return math.isfinite(val)
C:\ProgramData\anaconda3\envs\spodProject\lib\site-packages\matplotlib-3.9.0-py3.9-win-amd64.egg\matplotlib\cbook.py:1398: ComplexWarning: Casting complex values to real discards the imaginary part
return np.asarray(x, float)
Traceback (most recent call last):
File "C:\Program Files\JetBrains\PyCharm 2023.3.2\plugins\python\helpers\pydev\pydevd.py", line 1534, in _exec
pydev_imports.execfile(file, globals, locals)  # execute the script
File "C:\Program Files\JetBrains\PyCharm 2023.3.2\plugins\python\helpers\pydev_pydev_imps_pydev_execfile.py", line 18, in execfile
exec(compile(contents+"\n", file, 'exec'), glob, loc)
File "D:\spod\PySPOD-main\tutorials\tutorial2\tutorial2.py", line 138, in
data = spod.get_data(data)
File "C:\ProgramData\anaconda3\envs\spodProject\lib\site-packages\pyspod-2.0.0-py3.9.egg\pyspod\spod\base.py", line 826, in get_data
d = d[...,np.newaxis]
File "C:\ProgramData\anaconda3\envs\spodProject\lib\site-packages\xarray-2024.6.0-py3.9.egg\xarray\core\dataarray.py", line 876, in getitem
return self.isel(indexers=self._item_key_to_dict(key))
File "C:\ProgramData\anaconda3\envs\spodProject\lib\site-packages\xarray-2024.6.0-py3.9.egg\xarray\core\dataarray.py", line 1501, in isel
ds = self._to_temp_dataset()._isel_fancy(
File "C:\ProgramData\anaconda3\envs\spodProject\lib\site-packages\xarray-2024.6.0-py3.9.egg\xarray\core\dataset.py", line 3029, in _isel_fancy
new_var = var.isel(indexers=var_indexers)
File "C:\ProgramData\anaconda3\envs\spodProject\lib\site-packages\xarray-2024.6.0-py3.9.egg\xarray\core\variable.py", line 1033, in isel
return self[key]
File "C:\ProgramData\anaconda3\envs\spodProject\lib\site-packages\xarray-2024.6.0-py3.9.egg\xarray\core\variable.py", line 797, in getitem
dims, indexer, new_order = self._broadcast_indexes(key)
File "C:\ProgramData\anaconda3\envs\spodProject\lib\site-packages\xarray-2024.6.0-py3.9.egg\xarray\core\variable.py", line 642, in _broadcast_indexes
return self._broadcast_indexes_outer(key)
File "C:\ProgramData\anaconda3\envs\spodProject\lib\site-packages\xarray-2024.6.0-py3.9.egg\xarray\core\variable.py", line 724, in _broadcast_indexes_outer
return dims, OuterIndexer(tuple(new_key)), None
File "C:\ProgramData\anaconda3\envs\spodProject\lib\site-packages\xarray-2024.6.0-py3.9.egg\xarray\core\indexing.py", line 434, in init
raise TypeError(
TypeError: invalid indexer array, does not have integer dtype: array(None, dtype=object)
python-BaseException

@MemorXuxu Thank you for raising this issue. Do you have a minimum reproducible example?

@MemorXuxu Thank you for raising this issue. Do you have a minimum reproducible example?

Hello,Mengaldo
I run the tutorial 2 (https://github.com/MathEXLab/PySPOD/tree/main/tutorials/tutorial2)under folder test and it cannot run successfully, The error occor at data = spod.get_data(data)  at line 136.
Moreover, the version of numpy is 1.26.4. And I find that the newer version of numpy (2.0.0) cannot be used. I guest whether the version of numpy is wrong since the requirement of pyspod doesn't exist.

@MemorXuxu Thank you for raising this issue. Do you have a minimum reproducible example?

Interestingly,  the code in test_tutorial can run scuccessfully while the single tutorial  under Tutorial folder can't since the code between them is different. I think it's a small mistake and I believe the code under test is rigth!

@MemorXuxu Thank you for spotting this!
Do you want to contribute suggesting the modification needed?

@mengaldo
It's OK if it's convient ^_^. BTW,it's a great library and I'm happy that I can make a small contribution to it.

Another question, I don't whether I should create a new issus or not. When the SPOD is all calculated, how can I save all the state in JupyterBook or Python. When I need to post-processing the result, I need to perform all the calculation again which costs much time. However, in the result folder, there are many results(.npy) and I think it's the finally result of SPOD. Is it possible to just specify the results_dir data  or anything eles to reload these results for postprocessing and visualization.

@MemorXuxu  Thank you!
Yes, you should be able to save the results and reload them for post processing, without recalculating them every time.
Not sure however whether we show how.
To do this, we should load the .npy files of the modes, and the .npz file with the frequencies, and manually plot the modes, using the routines in post processing.

@mengaldo Thank you.
And the tutorial of climate (2D ) may have some issues due to the dataset is close, so it's hard to downlaod the E20C_MONTHLYMEAN00_1900_2010_MEI.nc file. For the 2D sPOD with two variables, 1000 snapshots. What's the size of the data, 21000yx or 1000xy2?
Best wishes!
Memorise

@mengaldoThank you very much!


Update Sass to title case

Small fix to update the project to use title case rather than all caps.
Note: http://sassnotsass.com/

Thanks!


WIP Adapt charm to support COS integration

Applicable spec: ISD-075 (private)
Overview
The PR adapts the charm to install Promtail and send metric logs to Loki by using  the loki_push_api integration.
Rationale
To implement the COS integration as specified in the spec, the GitHub Runner charm needs to be adapted to send the metrics to Loki.
Juju Events Changes
New:

LokiPushApiEndpointDeparted
LokiPushApiEndpointJoined

Library Changes
Two new libraries fetched:

charms.observability_libs.v0.juju_topology
charms.loki_k8s.v0.loki_push_api

Checklist

[x] The charm style guide was applied
[x] The contributing guide was applied
[x] The changes are compliant with ISD054 - Managing Charm Complexity
[x] The documentation is generated using src-docs
[x] The documentation for charmhub is updated.
[x] The PR is tagged with appropriate label (urgent, trivial, complex)

Marked the PR as complex due to significant new feature added. @canonical/is-devops-leadership please provide feedback.

Do you think any other modifications to public interfaces are required? I'm thinking about potentially:

creating the logs temporary file system/ directory
Reading the logs after the runner finished
Submitting the logs to promtail

Can you add a screenshot of the dashboard for reference ?

I removed Promtail to send the logs directly to Loki. The PR description has also been updated.

After feedback from the Observability team, I changed the implementation to use the cos-agent integration. I have updated the PR description.