Bottom sheet doesn't open when I re-route to back to its parent component(Homepage)

Hi, need help here, been battling this for weeks now.
My bottemsheet is placed in the homepage, so it contains links to some other pages on the app, when I open the bottomsheet and click on a link, it routes to that page.
But when I go back to my homepage, and try to open the bottomsheet again. it doesn't respond. The bottomsheet doesn't come up.
Until I refresh the app and start over, so the bottomsheet only comes up once. After usage, it doesn't again.
Packages:
"react-native-raw-bottom-sheet": "^2.2.0"
 "expo": "^45.0.0"
 "react-native": "0.68.2"

And here is the core of my BottomSheet component:
<View
      style={{
        flex: 1,
        justifyContent: "center",
        alignItems: "center",
        backgroundColor: "#000",
      }}
    >

      <RBSheet
        ref={ref}
        closeOnDragDown={false}
        dragFromTopOnly={true}
        closeOnPressMask={true}
        height={300}
        customStyles={{
          wrapper: {
            backgroundColor: 'rgba(0, 0, 0, 0.6)',
          },
          container: {
            borderTopLeftRadius: 20,
            borderTopRightRadius: 20,
          },
          draggableIcon: {
            backgroundColor: "#000"
          }
        }}
      >
        <FlatList
          data={nav}
          horizontal={false}
          numColumns={numOfColumns}
          sx={{
            maxWidth: '100%',
            marginLeft: 'auto',
            marginRight: 'auto',
            paddingLeft: 10,
            paddingRight: 10,
          }}
          columnWrapperStyle={{
            flex: 1,
            justifyContent: 'flex-start',
          }}
          renderItem={
            ( {item} ) => (
              !remove?.includes( item?.name ) ?
              (
                <NavItem
                  n={
                    !remove?.includes( item?.name ) ?
                    item : undefined
                  }
                  closeBottomSheet={() => {
                    return ref?.current?.close()
                  }}
                  as={ Platform.OS !== 'web' ? View : null}
                  tabStyle={{
                    // ...item?.style,
                    width: 100,
                    height: 100,
                    padding: 15,
                    color: '#000',
                    marginTop: 10,
                    fontFamily: theme.customFonts.Lato[ "normal" ],
                    textTransform: 'capitalize',
                    textAlign: 'center',
                    alignSelf: 'baseline',
                  }}
                />

              ) : null
            )
          }
          keyExtractor={ item => item?.name}
        />

      </RBSheet>
    </View>

I also got the same issue on other screen but on Home Screen  its working fine  while re route from any component to Home screen

I have the same problem

please ans i am facing same issue and apply all the things its not working

please ans i am facing same issue and apply all the things its not working

This package is stale, hasn't been updated in 4years. I suggest you use gorhom bottom-sheet

I believe that by calling the close() method before navigating, we can resolve this issue.


Making drag interface on density sorter more obvious

@pjanik, re: the discussion here, these are the changes I made to improve the UI of the density picker. Like Amy pointed out, this doesn't do much in terms of scaling on different devices, but I'm not sure the best way to handle that. In Geniverse, we just applied a scale factor on top of the whole page, but I realize you've made GEODE more responsive, so I'm curious what your thoughts are.
Specifically, the changes are: adding a hamburger menu and changing cursor to indicate drag-ability. Also adding helper text.

Much easier with the FontIcon! Fixed up the code and merged, thanks @pjanik


Refactor DBIC into a better place and streamline usage

Refactor DBIC test harness into a more modular location, and remove lazy load behaviour so that its configuration can be pillaged for creating DBConnections. Remove any references to DBIC Schema loader, we will use the DBIC schema to generate the database rather than the other way around.

Pull Request Test Coverage Report for Build 27

133 of 150 (88.67%)  changed or added relevant lines in 34 files are covered.
38 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.4%) to 25.873%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

modules/Bio/EnsEMBL/Xref/Schema/ResultSet/DependentXref.pm
3
6
50.0%

modules/Bio/EnsEMBL/Xref/Schema/ResultSet/Xref.pm
3
7
42.86%

modules/Bio/EnsEMBL/Xref/DB.pm
42
52
80.77%

Files with Coverage Reduction
New Missed Lines
%

modules/Bio/EnsEMBL/Xref/FetchFiles.pm
1
10.96%

modules/Bio/EnsEMBL/Xref/DBSQL/BaseAdaptor.pm
37
2.58%

Totals

Change from base Build 17:
0.4%

Covered Lines:
274

Relevant Lines:
1059

💛  - Coveralls

@markmcdowall the Moose dependency doesn't seem to be an issue, Travis's been happy with the equivalent version included in the test directory.

@avullo that's odd as when I tried running the code locally without Moose installed I got the following error:
Can't locate Moose.pm in @INC (you may need to install the Moose module)

Perhaps Travis includes Moose as part of the base package of perl modules by default

Travis has Moose, DBI, and a few other key packages cached by default. You're right, when Prem told me he had added stuff to the cpanfile, I presumed wrongly that Moose was in there along with DBIC. I'll add it.

Ah, well spotted :+1:


Category not updating

Steps to reproduce
Library -> a category -> Update -> nothing happens
Expected behavior
When u update a category, all comics in that category should update and have no. of new chaps on their covers.
Actual behavior
Previously, only frequently read comics(around 70) would update, not every comic in the category.
Understandable cuz i have a lot in a category.
Now, it doesn't even update frequently read comics, I have update each one manually.
sorry for poor quality, but it conveys the issue.
https://github.com/user-attachments/assets/164ee6e0-b1e5-4b26-969b-d40ffefa7208
Crash logs
App version: 0.17.0 (standard, 38d5fc9, 8, 2024-10-26T17:39:14Z)
Android version: 12 (SDK 31; build SKQ1.211019.001 test-keys)
Device brand: Redmi
Device manufacturer: Xiaomi
Device name: excalibur (excalibur_in)
Device model: Redmi Note 9 Pro Max
WebView: Android System WebView 130.0.6723.58
i shared twice via share crash logs option, they all have same data
Mihon version
17
Android version
Android 12
Device
Redmi note 9 pro
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 0.17.0.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Nothing is wrong with it. Join our discord for further support


Print response types better

Response classes should have a toString option to easily see what’s going on and/or override swift’s print function to print better response object messages

Refer to https://github.com/momentohq/client-sdk-swift/pull/99 for implementing the CustomStringConvertible interface, cleaner approach


[SuperEditor][SuperTextField] Remove NonReparentingFocus and FocusWithCustomParent (Resolves #1963)

In the past, we had some issues when trying to share the editor focus with popovers displayed in overlays, because they are not in the same subtree. Because of the different subtrees, the popover focus wasn’t naturally a child of the editor focus in the focus tree.
To work around that, we introduced NonParentingFocus, which is used solely by SuperTextfield to avoid natural focus reparenting, and FocusWithCustomParent to make it possible to force the popover focus node to be a child of the editor focus node.
Since them, Flutter introduced OverlayPortal, which makes it possible to share focus with widgets displayed in the overlay, and added a parentNode property to Focus, with the same purpose as our FocusWithCustomParent .
With these Flutter changes, our widgets aren’t necessary anymore. Even if developers use SuperEditor and show popovers using OverlayEntry, they can setup focus sharing by wrapping the popover with a Focus and setting the new parentNode property.
We already have a number of tests related to focus sharing, including tests that use OverlayEntry and they are still pass after removing NonParentingFocus from the SuperTextField subtree.
The usage of OverlayEntry is the only thing I can think that could cause problems with focus sharing. But since we can setup focus sharing by using a regular Focus, I believe it’s safe for us to just remove NonParentingFocus and FocusWithCustomParent.
However, while I was testing I got the following crash when showing the URL field in the demo app popover toolbar:
00:08 +502 -2: /Users/angelosilvestre/dev/super_editor/super_editor/test/super_editor/supereditor_selection_test.dart: SuperEditor selection by default keeps IME connection open when it loses primary focus (on Linux)
══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
The following assertion was thrown building SuperTextFieldKeyboardInteractor(state:
_SuperTextFieldKeyboardInteractorState#dd121):
Tried to make a child into a parent of itself.
'package:flutter/src/widgets/focus_manager.dart':
Failed assertion: line 1013 pos 12: 'child != this'

The relevant error-causing widget was:
  SuperTextFieldKeyboardInteractor
  SuperTextFieldKeyboardInteractor:file:///Users/angelosilvestre/dev/super_editor/super_editor/lib/src/super_textfield/desktop/desktop_textfield.dart:465:14

When the exception was thrown, this was the stack:
#2      FocusNode._reparent (package:flutter/src/widgets/focus_manager.dart:1013:12)
#3      FocusAttachment.reparent (package:flutter/src/widgets/focus_manager.dart:255:14)
#4      _FocusState.didChangeDependencies (package:flutter/src/widgets/focus_scope.dart:575:23)
#5      StatefulElement._firstBuild (package:flutter/src/widgets/framework.dart:5630:11)
#6      ComponentElement.mount (package:flutter/src/widgets/framework.dart:5457:5)
...

This happens because there are places where we are using the same FocusNode that we use to setup focus sharing as the SuperTextField focus node. For example:
Focus(
  focusNode: textFieldFocusNode,
  parentFocusNode: editorFocusNode,
  child: SuperTextField(
    focusNode: textFieldFocusNode,
  )
)

SuperTextField also places a Focus widget in the tree, so it seems we are violating a Flutter rule by using the same FocusNode in two different Focus widgets. It makes sense, since there is a focus tree a node can’t be child of itself.
To solve this, we should use a different FocusNode to setup focus sharing. For example:
Focus(
  focusNode: popoverFocusNode,
  parentFocusNode: editorFocusNode,
  child: SuperTextField(
    focusNode: textFieldFocusNode,
  )
)

It’s possible that apps have this same pattern, so this change can cause apps to crash.
Some existing tests related to focus sharing:
https://github.com/superlistapp/super_editor/blob/76c6562fd5e1665cb978886cfb9df2d5bad5cbb0/super_editor/test/super_editor/supereditor_popover_focus_test.dart#L12-L13
This test shows a popover in an OverlayEntry:
https://github.com/superlistapp/super_editor/blob/76c6562fd5e1665cb978886cfb9df2d5bad5cbb0/super_editor/test/super_editor/supereditor_popover_focus_test.dart#L107-L122
Another test:
https://github.com/superlistapp/super_editor/blob/76c6562fd5e1665cb978886cfb9df2d5bad5cbb0/super_editor/test/super_editor/supereditor_selection_test.dart#L616C38-L654
This test sets up focus sharing with a different subtree without an OverlayEntry. This is one of the tests that failed because we are passing textFieldFocus to two Focus  widgets.

cc @knopp

This looks great. It's probably a bad idea to have multiple focus attachments for a single node so it's good to fix that too.


uploading two images instead of one

guys when iam uploading an image in inpaint section of collab it uploads two copies of same image side by side

you need to check with the A1111 guys https://github.com/AUTOMATIC1111/stable-diffusion-webui/


🚀 | Support ntag NFC Chips with rc522

Feature
Extend the Mfrc522Reader class to support cheap NFC chips like ntag215. This might require switching to another library. The currently used pi-rc522 seems not to support the newer ntag chips. There are several other libraries, that might support the ntag type chips as well as the currently supported s50/s70 types.
I don't have experience with RFID/NFC or the phoniebox it self. But I'm happy to share my current workaround or help implementing a more general solution. Maybe some more experienced users/devs want to jump in for discussion.
(I will link related Issues later).
User perspective
From reading the docs (before #2372) here in the repo and/or the description of the RC522 users (like me) might expect all NFC tags are supported as long as the frequency matches. The ntag type chips seem to be very common on the market. For users who got some of these it should be possible to use them without touching the code.
Further information
I managed to use the phoniebox with ntag type chips by adding a reader based on the mrfc522 library with some copy pasted code from their examples and other github issues to work around Auth errors. This could be at least a preliminary solution for users who only want to use this type of chips:
class Mfrc522NtagReader(object):
    def __init__(self):
        from mfrc522 import MFRC522
        self.device = MFRC522()

    def readCard(self):
        while True:
            reader = self.device
            status, _ = reader.MFRC522_Request(reader.PICC_REQIDL)
            if status != reader.MI_OK:
                sleep(0.1)
                continue
            status, backData = reader.MFRC522_Anticoll()
            buf = reader.MFRC522_Read(0)
            reader.MFRC522_Request(reader.PICC_HALT)
            if buf:
                card_id = "".join([str(i) for i in buf])
                logger.info(card_id)
                return card_id

    @staticmethod
    def cleanup():
        GPIO.cleanup()

I have adjusted the Reader class and setup script accordingly to switch between the current reader and this workaround.

Thanks for your feature request.
The current Phoniebox implementation for rc522 readers seems to have issues with tags, which require(?) authentication.
The GitHub repo of the used rc-522 library seems to have more recent activity than pypy

Looking at our code in V2 the implementation might be too simple, just ignoring auth? @AlvinSchiller

@lukruh I think you are currently referring to V2 implementation (using Reader.experimental.py), so I tagged the issue accordingly.
Nevertheless we need to check V3 as well.

Looking at https://github.com/MiczFlor/RPi-Jukebox-RFID/blob/future3%2Fdevelop/src%2Fjukebox%2Fcomponents%2Frfid%2Fhardware%2Frc522_spi%2Frc522_spi.py#L100-L131 the V3 has the same (maybe too simple?) implementation.

Documentation has been updated (see #2372 and #2474) that ntags are currently not supported. Nevertheless we should try to fix this.

Documentation has been updated (see #2372 and #2474) that ntags are currently not supported. Nevertheless we should try to fix this.

If pi-rc522 library supports ntags and we need to improve our implementation this should be the way to go from my point of view.
The mfrc522 library seems to support it, but there is no activity for almost 4 years, so I'm not sure, if this helps us in the future.
We also need to consider the RPi.GPIO issue for Raspberry Pi OS Bookworm, see https://github.com/MiczFlor/RPi-Jukebox-RFID/issues/2313#issuecomment-2030579144

Looking at our code in V2 the implementation might be too simple, just ignoring auth? @AlvinSchiller

Yes, it looks like the case is just not covered, also in v3.

If pi-rc522 library supports ntags and we need to improve our implementation this should be the way to go from my point of view.
The mfrc522 library seems to support it, but there is no activity for almost 4 years, so I'm not sure, if this helps us in the future.
We also need to consider the RPi.GPIO issue for Raspberry Pi OS Bookworm (at least for V3), see https://github.com/MiczFlor/RPi-Jukebox-RFID/issues/2313#issuecomment-2030579144

Agree in all points 👍

If pi-rc522 library supports ntags and we need to improve our implementation this should be the way to go from my point of view.
The mfrc522 library seems to support it, but there is no activity for almost 4 years, so I'm not sure, if this helps us in the future.
We also need to consider the RPi.GPIO issue for Raspberry Pi OS Bookworm, see https://github.com/MiczFlor/RPi-Jukebox-RFID/issues/2313#issuecomment-2030579144

I have a working update for pi-rc522 that does work for ntag215 and the classic cards.  Ntag cards tend to cause more read errors (could also be cheap tags being crappy).  I modified it based on the pattern from this other repo. I'd prefer to find the official docs laying out the sequence of events but this works.  I'll put together an MR for pi-rc522 and see how that goes, that repo is pretty dead aside from a readme change

Would anyone be willing to take a look at something?  I am running into some weird behavior and I'm not sure what is going on.
When I run daemon_rfid_reader.py, I can see my new class getting loaded correctly and it picks up the ntag215 chips (less reliably than the mifare 1k card but that could be an antenna size/quality problem on this tags).  Since the debug version updates the settings files the same way, I can actually see the ntag215 uids showing up on the web page for registering new cards.
HOWEVER, the service does not seem to be having the same luck - I can see the log for my custom class getting loaded, but it looks like the cards are not being detected as often.  I think it might be just an issue with 2 instances trying to control the reader over the gpio and we end up not sending the messages in the right order for the ntag cards.  I've tried stopping the service (need to try full disable) - but it's weird that on boot I don't seem to get the same results as in debug

I've hit a wall.  I can't understand why the wait_for_tag() method works correctly in debug but not when I run the script normally.  Could be a timing issue that needs to be resolved between the two.  Here is the doc that outlines the comms, and honestly it looks like the existing code should have handled 7 byte (but not 10) UIDs. I ordered a stack of classic cards in the mean time

Do you have a branch or a PR yet?
It would probably help, if people could look at the code to help.

Yeah let me clean things up.  I am going to separate my changes, revert the repo and diff things.  It's just bizarre. I think most of the code to properly grab NTag 21x UIDs is there (maybe minus another select command).  I got frustrated with whatever was happening with Python debug vs normal and decided to look into .NET IoT libraries.
I am writing this now looking at my cheap MRFC522 spitting out NTag215 UIDs like crazy, and handling the classics just fine.  This works for me for now because I can just mimic the script behavior with the dll, but I'll take another look at the python piece since I don't want to leave everyone hanging

Diffing the current pi rfc522 library against the working c# libraries, a few things stand out

The python class doesn't really use the RST pin we send in aside from pulling it high in the constructor
-- The c# class does a hard reset on construction, pulling it low then high

The python class writes a reset to the device on construction
--The c# class has a SoftReset that does this but it isn't called in my working example

The way the python library initializes the device via writes is very different than the c# class
--c# source

I have zero idea what we're using the IRQ pin for.  I did some digging and, although the threads are a little stale, so are most libraries that exist for this device - and most signs point to the library not really supporting it (arduino mfrc522 library), or threads about how MicroPython supports interrupts but circuit python doesn't. The python library allows it, but doesn't provide an example.  Maybe this is a shortcoming of the NET libraries, but it isn't used and works fine.

The libraries diverge quick from there.  The C# library handles cascading internal to the Select command, and again the registers/values look.  I'm a few years removed from working with hardware and rarely use python, but I can't imagine there differences aren't leading to problems.  If you check out the class ESPHome uses alongside it's python, the c class write similar values to the c# source, and I haven't seen threads for Home Assistant complaining about it

To clarify: NTAG213 tags (13, not 15) seem to work in current master.
(after applying the workaround from #2387, wich was also required for me to read MIFARE Classic tags)

Here the part of the nxp mfrc522 documentation corresponding to the interrupts
8.4 Interrupt request system (3) (4) The MFRC522 indicates certain events by setting the Status1Reg register’s IRq bit and, if activated, by pin IRQ. The signal on pin IRQ can be used to interrupt the host using its interrupt handling capabilities. This allows the implementation of efficient host software. 8.4.1 Interrupt sources overview Table 18 shows the available interrupt bits, the corresponding source and the condition for its activation. The ComIrqReg register’s TimerIRq interrupt bit indicates an interrupt set by the timer unit which is set when the timer decrements from 1 to 0. The ComIrqReg register’s TxIRq bit indicates that the transmitter has finished. If the state changes from sending data to transmitting the end of the frame pattern, the transmitter unit automatically sets the interrupt bit. The CRC coprocessor sets the DivIrqReg register’s CRCIRq bit after processing all the FIFO buffer data which is indicated by CRCReady bit = 1. ). The ComIrqReg register’s RxIRq bit indicates an interrupt when the end of the received data is detected. The ComIrqReg register’s IdleIRq bit is set if a command finishes and the Command[3:0] value in the CommandReg register changes to idle (see Table 149 on page 70 The ComIrqReg register’s HiAlertIRq bit is set to logic 1 when the Status1Reg register’s HiAlert bit is set to logic 1 which means that the FIFO buffer has reached the level indicated by the WaterLevel[5:0] bits. The ComIrqReg register’s LoAlertIRq bit is set to logic 1 when the Status1Reg register’s LoAlert bit is set to logic 1 which means that the FIFO buffer has reached the level indicated by the WaterLevel[5:0] bits.
The ComIrqReg register’s ErrIRq bit indicates an error detected by the contactless UART during send or receive. This is indicated when any bit is set to logic 1 in register ErrorReg
Table 18. Interrupt sources
List of register bits indicating the cause for the interrupt.

From my point of view the first thing that needs to be done, is checking if the irq system needs to be activated.
The next question is, which kind of interrupt is send, when an interrupt occurs.
Hence the status register’s would need to be read out.
However the table 8 doesn't hint that there actually is an interrupt that indicates a card nearby.
However, I probably won't find the time to dig into this one.
As for the authentication, I think both libraries are supporting it. For a better understanding you need to dig into the protocol of the rfid Chips. In the end it comes down to sending som hex code via the rc522, like when getting the last 4 bytes of the uid of a 7 byte uid

For just making the Reader read cards the IRQ is NOT needed with any library, see #2387

Ah, now I see how these two issues are related. I'm just building my first Phoniebox and just ran into the #2387 issue with my existing Tonuino tags (small paper stickers underneath wooden tokens) which report as ISO 14443-3A NXP - NTAG213 in NFC Tools.
I then tried a random NFC card from my wallet (my company id card actually) which reports as ISO 14443-4 NXP - Mifare Classic 1k and it also did not work, despite it being a Mifare Classic tag.
Now I also found the plain white card that came shipped with my RC522 reader and this works even with IRQ! It seems to be a different variant of Mifare Classic: ISO 14443-3A NXP - Mifare Classic 1k.
Maybe I will find some time this week to dig into the RC522 specs and the python library code, but no promises...

After adding
self.clear_bitmask(0x13, 0x04)

at https://github.com/ondryaso/pi-rc522/blob/master/pirc522/rfid.py#L499 (/usr/local/lib/python3.9/dist-packages/pirc522/rfid.py on the phoniebox) I am getting IRQs from the reader with my empty NTAG213 tags :tada:
This will clear the RxNoErr bit in the RxModeReg register which defaults to 1 = "an invalid received data stream (less than 4 bits received) will be ignored and the receiver remains active"
That will have an effect on ComIrqReg register's RxIRq bit ("receiver has detected the end of a valid data stream. If the RxModeReg register’s RxNoErr bit is set to logic 1, the RxIRq bit is only set to logic 1 when data bytes are available in the FIFO"), which in turn is one of the interrupt sources.

Do you want to open a PR at https://github.com/ondryaso/pi-rc522 to fix this upstream?
This would be the easiest solution, we would avoid to fork the upstream repo.

After adding
self.clear_bitmask(0x13, 0x04)

at https://github.com/ondryaso/pi-rc522/blob/master/pirc522/rfid.py#L499 (/usr/local/lib/python3.9/dist-packages/pirc522/rfid.py on the phoniebox) I am getting IRQs from the reader with my empty NTAG213 tags 🎉

I'll give it a whirl.  I have a pack of NTAG215 little disc tags I bought for some esphome projects so I'd like those to work but I think from what I've seen 213/215 are similar (7 byte UID) just the 215 has more storage

Unfortunately, the bitmask change was not enough to get NTAG215 UIDs to be read correctly. I'm willing to offer up the .NET code I have that is working if others need it.  The other thing I considered was leveraging the c code that's out there for rc522 to put together a library Reader.py can just call directly and skip pirc522

Unfortunately, the bitmask change was not enough to get NTAG215 UIDs to be read correctly. I'm willing to offer up the .NET code I have that is working if others need it. The other thing I considered was leveraging the c code that's out there for rc522 to put together a library Reader.py can just call directly and skip pirc522

Is your .Net code using the interrupt pin?
Because I'm currently asking myself whether we should spend time on an interrupt system, which we most probably do not necessarily need.

Do you want to open a PR ... to fix this upstream?
Definitely, but only after testing a bit more to be sure that this actually fixes the issue.
I'm still not entirely sure what the heck the library is doing there in wait_for_tag().

Because I'm currently asking myself whether we should spend time on an interrupt system, which we most probably do not necessarily need.
I think that would be the sane way to go.

My hope for an interrupt-based solution was to save CPU cycles (currently the workaround with commented-out wait_for_tag() currently uses ~20% CPU on my Raspi 3B+ according to htop) and act only if the reader triggers a GPIO event via the IRQ pin.
But according to the datasheet (and https://arduino.stackexchange.com/a/76285) the rc522 actually does not seem to support a direct "interrupt when tag detected", only interrupts for e.g. the TX queue reaching a certain length.
The pi-rc522 library implementation of wait_for_tag() also does not seem to passively wait for a GPIO event but uses some active polling mechanism: There is an infinite loop that every 100 ms completely reinitializes the reader and transmits some radio data until either a "receiver interrupt request (RxIRq bit)" is received or an optional timeout (not used by RPi-Jukebox-RFID) is reached.
So I guess it should be safe to just ignore wait_for_tag() and just directly poll for tag IDs in Reader.py.

But according to the datasheet (and https://arduino.stackexchange.com/a/76285) the rc522 actually does not seem to support a direct "interrupt when tag detected", only interrupts for e.g. the TX queue reaching a certain length.

I got the same understanding, so I was already wondering how the wait_for_tag() is implemented and then, why your solution works. Now that i took a look in the implementation, the first thing done seems to be a complete reset of the reader (self.init()) and at the end, it waits for an event waiting = not self.irq.wait(0.1); according to the threading-doc

Wait until notified or until a timeout occurs. If the calling thread has not acquired the lock when this method is called, a RuntimeError is raised.

After adding
self.clear_bitmask(0x13, 0x04)

at https://github.com/ondryaso/pi-rc522/blob/master/pirc522/rfid.py#L499 (/usr/local/lib/python3.9/dist-packages/pirc522/rfid.py on the phoniebox) I am getting IRQs from the reader with my empty NTAG213 tags 🎉

I tested the code as well. With my NTAG215 it's not working.
maybe at this point it's wise to bring up an old issue i had.
with my first setup the uids could not be read completely. the issue was, that i only got a complete answer from the tag from time to time. Other people with a similar issue suggested that the main issue was the lack of power. The rfid reader was just not capable of providing enough energy to get a first and then in almost no time the second answer from the tag, providing the full uid. After buying a new rfid reader, the issue was gone.
Keeping that in mind, the previously working setup may be a result of voltage drops. If I'm not mistaken, the irq-pin is pulled down to indicate an interrupt. Hence, it may be possible that issue now appears, because I have a better power source keeping the irq stable while it wasn't stable beforehand resulting in a working setup (even my old rfid-reader is working with my workaround) ¯\(ツ)/¯ .

Unfortunately, the bitmask change was not enough to get NTAG215 UIDs to be read correctly. I'm willing to offer up the .NET code I have that is working if others need it. The other thing I considered was leveraging the c code that's out there for rc522 to put together a library Reader.py can just call directly and skip pirc522

Is your .Net code using the interrupt pin? Because I'm currently asking myself whether we should spend time on an interrupt system, which we most probably do not necessarily need.

No, the .NET MFRC522 implementation does not use the interrupt pin, nor is it even something you can pass/set via a constructor or property.  Here is the source.
I questioned the need for the IRQ pin in my post as well after getting all my tags read fine through the .NET code.  At the same time I was doing this, I was looking at languages for a Pi Pico project and came across the differences in MicroPython and CircuitPython - one main one being a lack of true interrupt support in CircuitPython.  I started wondering if the interrupt was never being caught or something


process the registration data and update to user object.

Fix #2848

@zyhfish Can you retarget this to 9.4.x release?  My attempt to change it brought in many other items

Hi @mitchelsellers , created #2851 to target to 9.4.x branch and close this, thx


fix(validate-assignment): do not validate extra fields when vaidate_assignment is on

Change Summary
Do not validate extra fields when validate_assignment option is set to True.
This prevent KeyError to be raised when trying to add an extra field.
Also, it seems more logical to validate only those fields that are explicitly set for the model.
See related bug description for details.
Related issue number
https://github.com/samuelcolvin/pydantic/issues/723
Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable
[x] change description file added to changes/,
see changes/README.md for details
on the format

change description file added to changes/

As I'm basing off of v0.32 I decided to update the HISTORY.rst instead.
Is it OK, @samuelcolvin?

All checks started to fail after rebased off v0.32...
They used to pass went my branch pointed to master. :thinking:

Please base of the v0.32 branch.

@samuelcolvin It is already based off of v0.32 branch. But I modified the PR to target v0.32 instead of master.
IS that enough?

great, thanks.
Since this isn't a new bug I assume it isn't critically urgent. I'll wait a few days in case anyone else finds problems with v0.32, then release.

Since this isn't a new bug I assume it isn't critically urgent.

We a actually a little bit blocked by it. :sweat_smile:
But I guess it can definitely wait till Monday.

Okay, I'll release now.

There's a minor typo there. :sweat_smile:
In the History and commit/PR name:
do not validate extra fields when vaidate_assignment is on, #724 by @YaraslauZhylko
It should be vaLidate_assignmet...

will fix.

Cool!

https://github.com/samuelcolvin/pydantic/issues/723?


ImportError: cannot import name 'Initialize' from 'qiskit.circuit.library.data_preparation'

Environment

Qiskit Terra version: 0.45.1
Python version: 3.10
Operating system: Windows

What is happening?
I am trying to run the Pytket AerBackend, and it requires importing :
from pytket.extensions.qiskit import AerBackend
However, when I run this I get the following error :
Traceback (most recent call last):   Cell In[53], line 1     from pytket.extensions.qiskit import AerBackend   File /opt/conda/lib/python3.10/site-packages/pytket/extensions/qiskit/__init__.py:18     from .backends import (   File /opt/conda/lib/python3.10/site-packages/pytket/extensions/qiskit/backends/__init__.py:16     from .ibm import IBMQBackend, NoIBMQCredentialsError   File /opt/conda/lib/python3.10/site-packages/pytket/extensions/qiskit/backends/ibm.py:37     from qiskit.primitives import SamplerResult  # type: ignore   File /opt/conda/lib/python3.10/site-packages/qiskit/primitives/__init__.py:55     from .base import BaseEstimator   File /opt/conda/lib/python3.10/site-packages/qiskit/primitives/base/__init__.py:17     from .base_estimator import BaseEstimator   File /opt/conda/lib/python3.10/site-packages/qiskit/primitives/base/base_estimator.py:95     from ..utils import init_observable   File /opt/conda/lib/python3.10/site-packages/qiskit/primitives/utils.py:25     from qiskit.circuit.library.data_preparation import Initialize ImportError: cannot import name 'Initialize' from 'qiskit.circuit.library.data_preparation' (/opt/conda/lib/python3.10/site-packages/qiskit/circuit/library/data_preparation/__init__.py)
How can we reproduce the issue?
Just run :
from pytket.extensions.qiskit import AerBackend
What should happen?
Well it should pass this, and allow for running the pytket code.
Any suggestions?
I ran this, and it didn't give an issue, but I can't use this as I still need this to be fixed through the package or pytket import won't work :
from qiskit.circuit.library.data_preparation.initializer import Initialize

I'm not able to reproduce this error using qiskit==0.45.1 and pytket-qiskit==0.47.0. Does the plain import
from qiskit.circuit.library.data_preparation.initializer import Initialize

work for you? If not you might not be using 0.45.1.

I am using IBM Quantum Lab. I can try to make a virtual env externally, I usually just use the notebook online and it's never had any issues to be honest.

I'm not able to reproduce this error using qiskit==0.45.1 and pytket-qiskit==0.47.0. Does the plain import
from qiskit.circuit.library.data_preparation.initializer import Initialize

work for you? If not you might not be using 0.45.1.

This works. The one that has the issue doesn't.

It's alright, I'll try to create a virtual env using conda. If the issue persists there I'll reopen this issue.
Thank you for the prompt response and kind support. Please feel free to close this for now if you wish.


Trying to figure out web_sys::AudioWorkletProcessor

Summary
I'd like to create and register an AudioWorkletProcessor using Rust.  I'm still not sure if it's possible.
Additional Details
I've also put up a question on StackOverflow.
I'm currently stuck on having to extend AudioWorkletProcessor for the sake of overriding the process() function.  And I'm also not yet sure if it's going to be possible to access AudioWorkletGlobalScope.  On top of all this, I have no idea if it will play well with webpack / or any other bundler.  This is what I've got so far:
use wasm_bindgen::prelude::*;
use web_sys::{ AudioWorkletGlobalScope };

#[wasm_bindgen]
pub fn create_worklet_node() {
  AudioWorkletGlobalScope::register_processor(/* MISSING ARGUMENTS */);
}

#[wasm_bindgen]
extern "C" {
  #[wasm_bindgen(extends = web_sys::AudioWorkletProcessor)]
  type MyAudioWorkletProcessor;
}

#[wasm_bindgen]
impl MyAudioWorkletProcessor {
  pub fn process() {
    // this would throw an error if I was doing it right... :/
  }
}

Potential Incentive
I think that multi-threaded audio processing is an extremely good example of the power of wasm, so I'd probably not be the only person who could really use an example of how to set up an AudioWorklet using Rust.
Thanks for this project!

I think this is covered by https://github.com/rustwasm/wasm-bindgen/issues/210, so I'm going to close this in favor of that.
(although if it's got pieces which aren't part of that, please feel free to file a new issue!)


Is there Vim whose command can be customized

Is there a Vim release whose command can be customized by use of Vim itself or other executable tool e.g.
change
:q
become : <ESC key press> or :K
Thanks before

Maybe you could try an abbrevation:
cnoreabbrev <expr> q getcmdtype() == ':' && getcmdpos() == len('q') + 1 ? 'K' : 'q'

For more info, see:

:help :cnoreabbrev
:help :map-expression
:help getcmdtype()
:help getcmdpos()
:help len()

For more questions, visit the google mailing list, the irc channel, or vi.stackexchange.com.

The commands in Vim are divided into two parts: builtin commands (start with lower case letter) and user commands (start with upper case). The user commands may be (re, un)defined freely. The builtin commands not.
There are some tricks however. With command-line input, as mentioned above, or with auto-commands. E.g. instead of overwriting builtin quit command you may choose to do something useful during, say, QuitPre event. And this would work also for ZZ or ZQ and such.

Thanks so much, indeed useful, appreciated.


Allow for specifying storageClassName for etcd PVC

Currently, consumers of the KCP Helm chart are unable to specify a StorageClass to use with the Etcd StatefulSet. This isn't a big deal in local dev environments. However with larger deployments where you need different storage types (e.g. SSDs), this can be problematic unless you change the default storageclass for the cluster - which has it's own impacts.
This changeset enables specifying the storageClassName for the underlying volumeClaimTemplate via the values.yaml or Helm override arg. I've explicitly opted to only use the storageClassName property if it's been set in the values.yaml, rather than specifying a default value in the values.yaml file. That way the current behavior continues to work and operators that need a more advanced setting are enabled to specify the target storageClass via the values.yaml.
How has this been tested
I tested these changes against two clusters, kind and GKE. With the kind cluster, there's simply just the 1 StorageClass that is included and available. Due to this, kind was used to test the basic case of not overriding the default behavior.
Kind

Created the cluster and installed cert-manager, which resulted in the following resources in the cluster:

k get pods -A                                                           ○ kind-kind
NAMESPACE            NAME                                         READY   STATUS    RESTARTS   AGE
cert-manager         cert-manager-654496659-grxcb                 1/1     Running   0          18s
cert-manager         cert-manager-cainjector-6cbfdd7697-t2srl     1/1     Running   0          18s
cert-manager         cert-manager-webhook-59786477cf-xpsmm        1/1     Running   0          18s
kube-system          coredns-6f6b679f8f-mf75j                     1/1     Running   0          3m41s
kube-system          coredns-6f6b679f8f-v298v                     1/1     Running   0          3m41s
kube-system          etcd-kind-control-plane                      1/1     Running   0          3m48s
kube-system          kindnet-6g2hd                                1/1     Running   0          3m41s
kube-system          kube-apiserver-kind-control-plane            1/1     Running   0          3m48s
kube-system          kube-controller-manager-kind-control-plane   1/1     Running   0          3m48s
kube-system          kube-proxy-mvgkg                             1/1     Running   0          3m41s
kube-system          kube-scheduler-kind-control-plane            1/1     Running   0          3m48s
local-path-storage   local-path-provisioner-57c5987fd4-5ldpq      1/1     Running   0          3m41s

k get storageclass                             11s ○ kind-kind
NAME                 PROVISIONER             RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
standard (default)   rancher.io/local-path   Delete          WaitForFirstConsumer   false                  11s

Created the following myvalues.yaml in order to closely following the local dev instructions

bat myvalues.yaml
───────┬─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
       │ File: myvalues.yaml
───────┼─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1   │ externalHostname: kcp-front-proxy.upbound-system.svc

Installed KCP into the kind cluster using the command from the README

helm install kcp ./charts/kcp --values ./myvalues.yaml --namespace kcp --create-name
space
NAME: kcp
LAST DEPLOYED: Wed Aug 28 12:29:52 2024
NAMESPACE: kcp
STATUS: deployed
REVISION: 1
TEST SUITE: None

Once pods were up and healthy, verified the deployment

 k -n kcp get pods                                                                     ○ kind-kind
NAME                               READY   STATUS    RESTARTS      AGE
kcp-644f6bb8df-qhztm               1/1     Running   0             3m
kcp-etcd-0                         1/1     Running   0             3m
kcp-etcd-1                         1/1     Running   1 (73s ago)   106s
kcp-etcd-2                         1/1     Running   0             102s
kcp-front-proxy-7677c784fd-z2mf8   1/1     Running   0             3m

k get storageclass                                                                    ○ kind-kind
NAME                 PROVISIONER             RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
standard (default)   rancher.io/local-path   Delete          WaitForFirstConsumer   false                  5m18s

k -n kcp get pvc                                                                       ○ kind-kind
NAME                   STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   VOLUMEATTRIBUTESCLASS   AGE
etcd-data-kcp-etcd-0   Bound    pvc-81887157-5ed6-4056-96db-8eb465a7bc94   8Gi        RWO            standard       <unset>                 79s
etcd-data-kcp-etcd-1   Bound    pvc-9344a510-d378-4b0a-8a44-b005e95d3d4c   8Gi        RWO            standard       <unset>                 10s
etcd-data-kcp-etcd-2   Bound    pvc-6744606c-f4a9-4c36-88d7-685cf62d76e6   8Gi        RWO            standard       <unset>                 5s

GKE

Created the cluster and installed cert-manager, which resulted in the following resources in the cluster:

k get pods -A                                                  27s ○ cluster-2
NAMESPACE         NAME                                                  READY   STATUS    RESTARTS   AGE
cert-manager      cert-manager-69f6576f94-z4psq                         1/1     Running   0          101s
cert-manager      cert-manager-cainjector-7746bc4d84-2xqzn              1/1     Running   0          101s
cert-manager      cert-manager-webhook-996bcb478-crncc                  1/1     Running   0          101s
gke-managed-cim   kube-state-metrics-0                                  2/2     Running   0          5m43s
gmp-system        collector-pb8z5                                       2/2     Running   0          4m14s
gmp-system        collector-qmzzv                                       2/2     Running   0          4m15s
gmp-system        collector-rs2xt                                       2/2     Running   0          4m15s
gmp-system        gmp-operator-7fb5bc5476-b9fjp                         1/1     Running   0          5m15s
kube-system       event-exporter-gke-7c4fd479b6-wqm6t                   2/2     Running   0          5m38s
kube-system       fluentbit-gke-dk66z                                   3/3     Running   0          4m42s
kube-system       fluentbit-gke-fr8tk                                   3/3     Running   0          4m40s
kube-system       fluentbit-gke-zq5q9                                   3/3     Running   0          4m40s
kube-system       gke-metrics-agent-67tjg                               3/3     Running   0          4m42s
kube-system       gke-metrics-agent-pnq7w                               3/3     Running   0          4m43s
kube-system       gke-metrics-agent-zb65l                               3/3     Running   0          4m40s
kube-system       konnectivity-agent-94f4cdb75-5c7dw                    2/2     Running   0          4m15s
kube-system       konnectivity-agent-94f4cdb75-qknjs                    2/2     Running   0          5m26s
kube-system       konnectivity-agent-94f4cdb75-rwpsd                    2/2     Running   0          4m15s
kube-system       konnectivity-agent-autoscaler-67d4f7d5f-k57dd         1/1     Running   0          5m24s
kube-system       kube-dns-5954f95c5-gwxt2                              5/5     Running   0          4m16s
kube-system       kube-dns-5954f95c5-sqnnz                              5/5     Running   0          5m50s
kube-system       kube-dns-autoscaler-79b96f5cb-2glc2                   1/1     Running   0          5m49s
kube-system       kube-proxy-gke-cluster-2-default-pool-470bfea5-8hqh   1/1     Running   0          4m39s
kube-system       kube-proxy-gke-cluster-2-default-pool-470bfea5-kjm9   1/1     Running   0          3m48s
kube-system       kube-proxy-gke-cluster-2-default-pool-470bfea5-zzbz   1/1     Running   0          4m36s
kube-system       l7-default-backend-db86fddff-46rjp                    1/1     Running   0          5m21s
kube-system       metrics-server-v0.7.1-6767545bf-5gvkv                 2/2     Running   0          4m12s
kube-system       pdcsi-node-bdhb5                                      2/2     Running   0          4m42s
kube-system       pdcsi-node-k9ksb                                      2/2     Running   0          4m40s
kube-system       pdcsi-node-w78np                                      2/2     Running   0          4m41s

k get storageclass                                             ○ cluster-2
NAME                     PROVISIONER             RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
premium-rwo              pd.csi.storage.gke.io   Delete          WaitForFirstConsumer   true                   5m9s
standard                 kubernetes.io/gce-pd    Delete          Immediate              true                   5m9s
standard-rwo (default)   pd.csi.storage.gke.io   Delete          WaitForFirstConsumer   true                   5m9s

Updated the myvalues.yaml to include the storageClass override

bat myvalues.yaml
───────┬─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
       │ File: myvalues.yaml
───────┼─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1   │ externalHostname: kcp-front-proxy.upbound-system.svc
   2   │ etcd:
   3   │   storageClassName: premium-rwo

Installed KCP into the kind cluster using the command from the README

helm install kcp ./charts/kcp --values ./myvalues.yaml --namespace kc
p --create-namespace
NAME: kcp
LAST DEPLOYED: Wed Aug 28 13:02:46 2024
NAMESPACE: kcp
STATUS: deployed
REVISION: 1
TEST SUITE: None

Once pods were up and healthy, verified the deployment

 k -n kcp get pods                                                                   ○ cluster-2
NAME                               READY   STATUS    RESTARTS   AGE
kcp-5c5f89646c-h654r               1/1     Running   0          3m
kcp-etcd-0                         1/1     Running   0          3m
kcp-etcd-1                         1/1     Running   0          107s
kcp-etcd-2                         1/1     Running   0          95s
kcp-front-proxy-7f6b547dd6-h8stm   1/1     Running   0          3m

k get storageclass                                                                  ○ cluster-2
NAME                     PROVISIONER             RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
premium-rwo              pd.csi.storage.gke.io   Delete          WaitForFirstConsumer   true                   8m8s
standard                 kubernetes.io/gce-pd    Delete          Immediate              true                   8m8s
standard-rwo (default)   pd.csi.storage.gke.io   Delete          WaitForFirstConsumer   true                   8m8s

-n kcp get pvc                                                                    ○ cluster-2
NAME                   STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   VOLUMEATTRIBUTESCLASS   AGE
etcd-data-kcp-etcd-0   Bound    pvc-975ea596-5fb5-430a-8d50-a4bde82bbe14   8Gi        RWO            premium-rwo    <unset>                 2m16s
etcd-data-kcp-etcd-1   Bound    pvc-e75a5900-543d-4171-b6c7-d2848d242277   8Gi        RWO            premium-rwo    <unset>                 63s
etcd-data-kcp-etcd-2   Bound    pvc-cf990027-7adf-4e79-ad58-4d33fc8cd63a   8Gi        RWO            premium-rwo    <unset>                 51s

/ok-to-test


Unable to query table vanta_computer

Describe the bug
Queries on the table vanta_computer raise this error:
graphql: Cannot query field `requiresLocationServices` on type `Organization`

Steampipe version (steampipe -v)
Steampipe v0.20.12
Plugin version (steampipe plugin list)
Example: v0.2.0
To reproduce
select id from vanta_computer;

Output:
Error: graphql: Cannot query field "requiresLocationServices" on type "Organization". (SQLSTATE HV000)

[no data]

Expected behavior
Query should return data without any error.
Additional context
Queries on table vanta_user work without any issue (therefore session_id is correctly set).

Perhaps Vanta has changed the fields in their API?
Here is the code in question if anyone would like to try updating it:
https://github.com/turbot/steampipe-plugin-vanta/blob/69b2bc127c04ac2f3e1888754c644b68d770e41f/api/workstation.go#L69
Looking through the code, it's not clear to me that we're even including that field in the response?

Fields changed in their API: probably.
There's a warning about this on their site.
I hoped to be able to get the API call in the traces, but no success:
$ STEAMPIPE_LOG_LEVEL=TRACE steampipe query 'select id from vanta_computer'
2023-09-26 13:32:57.101 UTC [TRACE] steampipe: parse complete after 1 decode passes
2023-09-26 13:32:57.101 UTC [TRACE] steampipe: ensureInstallDir /home/user/.steampipe
2023-09-26 13:32:57.103 UTC [TRACE] steampipe: nothing to migrate in /home/user/.steampipe/internal/update-check.json
2023-09-26 13:32:57.103 UTC [TRACE] steampipe: No memory limit set
2023-09-26 13:32:57.104 UTC [TRACE] steampipe: no modfile exists in workspace folder - NOT creating pseudoresources and only loading resource files from top level folder
2023-09-26 13:32:57.104 UTC [TRACE] steampipe: parse complete after 1 decode passes
2023-09-26 13:32:57.104 UTC [TRACE] steampipe: parse complete after 1 decode passes
2023-09-26 13:32:57.104 UTC [TRACE] steampipe: Workspace load took 0ms
2023-09-26 13:32:57.105 UTC [TRACE] steampipe: telemetry.Init service 'steampipe', tracingEnabled: false, metricsEnabled: false
2023-09-26 13:32:57.105 UTC [TRACE] steampipe: metrics and tracing disabled' - returning
2023-09-26 13:32:57.113 UTC [TRACE] steampipe: SQLInfoMap >>> map[dbname:steampipe host:localhost port:9193 sslcert:/home/user/.steampipe/db/14.2.0/data/server.crt sslkey:/home/user/.steampipe/db/14.2.0/data/server.key sslmode:verify-ca sslrootcert:/home/user/.steampipe/db/14.2.0/data/root.crt user:steampipe]
2023-09-26 13:32:57.113 UTC [TRACE] steampipe: PSQLInfo >>> [user=steampipe dbname=steampipe sslmode=verify-ca sslrootcert=/home/user/.steampipe/db/14.2.0/data/root.crt sslcert=/home/user/.steampipe/db/14.2.0/data/server.crt sslkey=/home/user/.steampipe/db/14.2.0/data/server.key host=localhost port=9193]
2023-09-26 13:32:57.124 UTC [TRACE] steampipe: Pinging
2023-09-26 13:32:57.128 UTC [TRACE] steampipe: created local client 0xc0008a6960
2023-09-26 13:32:57.128 UTC [TRACE] steampipe: ensureSessionSearchPath
2023-09-26 13:32:57.128 UTC [TRACE] steampipe: session search path will be updated to

Error: graphql: Cannot query field "requiresLocationServices" on type "Organization". (SQLSTATE HV000)

+----+
| id |
+----+
+----+

2023-09-26 13:33:17.604 UTC [TRACE] steampipe: DbClient.Close &{0 0 0 0xc0008a65a0 0xc0009b01e0 <nil> <nil> <nil> <nil> 0 1<PHONE_NUMBER>00 0<PHONE_NUMBER>0<PHONE_NUMBER>0 0xc00033b6e0 {0 {0 0}} 0xc00033b740}
2023-09-26 13:33:17.604 UTC [TRACE] steampipe: local client close complete
2023-09-26 13:33:17.604 UTC [TRACE] steampipe: shutdown local service query
2023-09-26 13:33:17.611 UTC [TRACE] steampipe: SQLInfoMap >>> map[dbname:steampipe host:localhost port:9193 sslcert:/home/user/.steampipe/db/14.2.0/data/server.crt sslkey:/home/user/.steampipe/db/14.2.0/data/server.key sslmode:verify-ca sslrootcert:/home/user/.steampipe/db/14.2.0/data/root.crt user:root]
2023-09-26 13:33:17.611 UTC [TRACE] steampipe: PSQLInfo >>> [sslrootcert=/home/user/.steampipe/db/14.2.0/data/root.crt sslcert=/home/user/.steampipe/db/14.2.0/data/server.crt sslkey=/home/user/.steampipe/db/14.2.0/data/server.key host=localhost port=9193 user=root dbname=steampipe sslmode=verify-ca]
2023-09-26 13:33:17.631 UTC [TRACE] steampipe: Pinging
2023-09-26 13:33:17.642 UTC [TRACE] steampipe: ShutdownService not closing database service - 1 steampipe client connected

The plugin-YYYY-MM-DD.log:
2023-09-26 13:33:17.176 UTC [WARN]  steampipe-plugin-vanta.plugin: [WARN]<PHONE_NUMBER>942: waitForPendingItem timed out waiting for pending transfer (vanta-1695735177942) 0xc0001f3d70 indexBucketKey: index__vanta_vanta_computer, item key vanta_vanta_computer_id_-1
2023-09-26 13:33:17.602 UTC [ERROR] steampipe-plugin-vanta.plugin: [ERROR]<PHONE_NUMBER>942: vanta_computer.listVantaComputers: query_error="graphql: Cannot query field \"requiresLocationServices\" on type \"Organization\"."
2023-09-26 13:33:17.602 UTC [WARN]  steampipe-plugin-vanta.plugin: [WARN]<PHONE_NUMBER>942: doList callHydrateWithRetries (vanta-1695735177942) returned err graphql: Cannot query field "requiresLocationServices" on type "Organization".
2023-09-26 13:33:17.602 UTC [WARN]  steampipe-plugin-vanta.plugin: [WARN]<PHONE_NUMBER>942: QueryData StreamError graphql: Cannot query field "requiresLocationServices" on type "Organization". (vanta-1695735177942)
2023-09-26 13:33:17.602 UTC [WARN]  steampipe-plugin-vanta.plugin: [WARN]<PHONE_NUMBER>942: streamRows for vanta-1695735177942 - execution has failed (graphql: Cannot query field "requiresLocationServices" on type "Organization".) - calling queryCache.AbortSet
2023-09-26 13:33:17.602 UTC [WARN]  steampipe-plugin-vanta.plugin: [WARN]<PHONE_NUMBER>942: executeForConnection vanta returned error graphql: Cannot query field "requiresLocationServices" on type "Organization".
2023-09-26 13:33:17.602 UTC [WARN]  steampipe-plugin-vanta.plugin: [WARN]<PHONE_NUMBER>942: error channel received graphql: Cannot query field "requiresLocationServices" on type "Organization".

The database-YYYY-MM-DD.log:
2023-09-26 13:32:57.116 UTC [795805] LOG:  connection received: host=<IP_ADDRESS> port=47530
2023-09-26 13:32:57.122 UTC [795805] LOG:  connection authorized: user=steampipe database=steampipe application_name=steampipe_705d SSL enabled (protocol=TLSv1.2, cipher=ECDHE-RSA-AES256-GCM-SHA384, bits=256)
2023-09-26 13:33:17.603 UTC [WARN]  hub: stream receive error rpc error: code = Unknown desc = graphql: Cannot query field "requiresLocationServices" on type "Organization". (0xc0000ea240)
2023-09-26 13:33:17.603 UTC [795805] ERROR:  rpc error: code = Unknown desc = graphql: Cannot query field "requiresLocationServices" on type "Organization".
2023-09-26 13:33:17.603 UTC [795805] STATEMENT:  select id from vanta_computer
2023-09-26 13:33:17.604 UTC [795805] LOG:  disconnection: session time: 0:00:20.488 user=steampipe database=steampipe host=<IP_ADDRESS> port=47530
2023-09-26 13:33:17.616 UTC [795830] LOG:  connection received: host=<IP_ADDRESS> port=40600
2023-09-26 13:33:17.627 UTC [795830] LOG:  connection authorized: user=root database=steampipe application_name=steampipe_705d SSL enabled (protocol=TLSv1.2, cipher=ECDHE-RSA-AES256-GCM-SHA384, bits=256)
2023-09-26 13:33:17.640 UTC [795830] LOG:  disconnection: session time: 0:00:00.024 user=root database=steampipe host=<IP_ADDRESS> port=40600

@e-gineer: indeed removing the line 69 seems to solve the issue


v0.3.2

Add nextState
Remove Tick and After
Modify README.md
Initilize EOD
Add external transitions (experimental)

close #16 #15 #14 #13 #12

@sato22
Please review the updated develop branch with your examples?

Update v0.4.0
These can be written on a diagram

entry-do-exit on state
guard-action on transition

Comment out DeviceInput and DeviceOutput funcs


[Algo]: Add euclidean-gcd in Java

Add division-based, recursive and extended Euclidean Algorithm using Java.

I am on this.


Release armdatafactory v0.1.0

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

/azp run prepare-pipelines

/azp run go - armdatafactory - ci

/azp run go - armdatafactory - ci

We have similar compile error in this package like in security

/azp run go - armdatafactory - ci


Canvas art

Zero To Mastery - Canvas 2022 🎉🎉
👉 Please remove the below and replace with your own values, leaving the headers where they are. 👈
PR contains:
A happy face(Please be as descriptive as possible) 🤜
Breaking changes
None
Screenshots

I have made the changes requested


Icon request: Codecov

URL for the brand / site / app
https://about.codecov.io/
Logo resources for the icon
No response
Anything else?
No response

No 2FA with this either.

No 2FA with this either. I made account and checked myself.
If you ever gonna submit non-2FA related issue request again, I'll ban you. I know I have said that many times, but I mean it.

when i have added i don't know about that you only include services which have 2fa support.
and you no need to say thank i really don't want to spam i just want to have those svg icons but now i understand. you look at my other requests and i have shared there svg files also hence it will be easier for you to upload.


File is shared as an attachment

Hello
I have an issue with Importing the "_chat.txt" into Telegram
Telegram doesn't recognise the file as a chat history and import it,
instead it shares it as an attachment
I compressed _chat.txt and named the archive "Whatsapp Chat - xxxx.zip"
(replacing xxxx with the name of the user whose chat I'm importing)
I transfer the file from my MacOS to my phone
I navigate to where I saved the file, and tap on it. I choose the "Share" option,
select the Telegram app.
I select the contact and send the file.
and it sends the ".zip" file as an attachment.
It doesn't import it as chat history.
I also tried sharing only the "_chat.txt",
but it sends it as an attachment the same
Could you help me, please?
Thank you

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Hi,
I was able to replicate your issue when I compressed the "_chat.txt" file locally on my iPhone. This suggests that the problem might be related to the compression software you're using on your Mac. I recommend trying WinRAR or 7-Zip for compression instead.
Another possible cause could be the format of the "_chat.txt" file. Ensure the content is formatted correctly, similar to this:
[03.05.2024, 15:19:36] Sender: Message

Let me know if this helps!

hi! i encountered the same problem. i tried to compress the file in different ways(winrar and 7-zip too, the file format is also correct), but it keeps sending as a ".zip" file instead of importing into the chat history

It seems like the issue might be related to how Telegram is handling the file. As a next step, try exporting another chat as a .json file and follow the same process. Additionally, create a test group on Telegram with no participants and try importing the chat into that group. This might help determine if the issue is with the file or the specific chat. Let me know how it goes!

I think, there were some changes in whatsapp export naming (and telegram import takes them into account).
You need to rename the resulting _chat.txt into "WhatsApp Chat with .txt", before packing it. Pack it and rename the archive into "WhatsApp Chat with .zip" as well. After that, my archive was finally recognized by telegram as history (telegram explicitly shows "choose dialog to import" instead of common share file) and imported correctly.
@Suberbia Thanks for a really useful tool!