Unable to download video from TikTok, Error Unable to extract sigi state

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
Malaysia
Provide a description that is worded well enough to be understood
I'm unable to download or fetch video data from TikTok. I've updated yt-dlp to version 2024.3.10. I even tried to downgrade to version 2023.12.30 but the issue still happen.
Error
[TikTok] Extracting URL: https://www.tiktok.com/@catplanet6/video/7309135341791792426?is_from_webapp=1
[TikTok]<PHONE_NUMBER>791792426: Downloading video feed
WARNING: [TikTok] Expecting value in '': line 1 column 1 (char 0). Retrying... (attempt 1 of 4)
[TikTok]<PHONE_NUMBER>791792426: Downloading video feed
WARNING: [TikTok] Expecting value in '': line 1 column 1 (char 0). Retrying... (attempt 2 of 4)
[TikTok]<PHONE_NUMBER>791792426: Downloading video feed
WARNING: [TikTok] Expecting value in '': line 1 column 1 (char 0). Retrying... (attempt 3 of 4)
[TikTok]<PHONE_NUMBER>791792426: Downloading video feed
WARNING: [TikTok]<PHONE_NUMBER>791792426: Failed to parse JSON (caused by JSONDecodeError("Expecting value in '': line 1 column 1 (char 0)")); please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U; trying with webpage
[TikTok]<PHONE_NUMBER>791792426: Downloading webpage
ERROR: [TikTok]<PHONE_NUMBER>791792426: Unable to extract sigi state; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U

Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
yt-dlp -vU https://www.tiktok.com/@catplanet6/video/7309135341791792426\?is_from_webapp\=1\&sender_device\=pc
[debug] Command-line config: ['-vU', 'https://www.tiktok.com/@catplanet6/video/7309135341791792426?is_from_webapp=1&sender_device=pc']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[088add956] (pip)
[debug] Python 3.11.2 (CPython arm64 64bit) - macOS-14.2.1-arm64-arm-64bit (OpenSSL 1.1.1u  30 May 2023)
[debug] exe versions: ffmpeg 6.1.1 (setts), ffprobe 6.1.1
[debug] Optional libraries: Cryptodome-3.18.0, brotli-1.0.9, certifi-2023.05.07, mutagen-1.46.0, sqlite3-3.43.2, websockets-11.0.3
[debug] Proxy map: {}
[debug] Loaded 1886 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>[debug] Downloading _update_spec from https://github.com/yt-dlp/yt-dlp/releases/latest/download/_update_spec
ERROR: You installed yt-dlp with pip or using the wheel from PyPi; Use that to update
[TikTok] Extracting URL: https://www.tiktok.com/@catplanet6/video/7309135341791792426?is_from_webapp=1&sender_device=pc
[TikTok]<PHONE_NUMBER>791792426: Downloading video feed
WARNING: [TikTok] Expecting value in '': line 1 column 1 (char 0). Retrying... (attempt 1 of 4)
[TikTok]<PHONE_NUMBER>791792426: Downloading video feed
WARNING: [TikTok] Expecting value in '': line 1 column 1 (char 0). Retrying... (attempt 2 of 4)
[TikTok]<PHONE_NUMBER>791792426: Downloading video feed
WARNING: [TikTok] Expecting value in '': line 1 column 1 (char 0). Retrying... (attempt 3 of 4)
[TikTok]<PHONE_NUMBER>791792426: Downloading video feed
WARNING: [TikTok]<PHONE_NUMBER>791792426: Failed to parse JSON (caused by JSONDecodeError("Expecting value in '': line 1 column 1 (char 0)")); please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U; trying with webpage
[TikTok]<PHONE_NUMBER>791792426: Downloading webpage
ERROR: [TikTok]<PHONE_NUMBER>791792426: Unable to extract sigi state; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
  File "/Users/J0W432431K/.pyenv/versions/3.11.2/lib/python3.11/site-packages/yt_dlp/extractor/common.py", line 715, in extract
    ie_result = self._real_extract(url)
                ^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/J0W432431K/.pyenv/versions/3.11.2/lib/python3.11/site-packages/yt_dlp/extractor/tiktok.py", line 700, in _real_extract
    sigi_data = self._get_sigi_state(webpage, video_id)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/J0W432431K/.pyenv/versions/3.11.2/lib/python3.11/site-packages/yt_dlp/extractor/tiktok.py", line 52, in _get_sigi_state
    return self._search_json(
           ^^^^^^^^^^^^^^^^^^
  File "/Users/J0W432431K/.pyenv/versions/3.11.2/lib/python3.11/site-packages/yt_dlp/extractor/common.py", line 1277, in _search_json
    json_string = self._search_regex(
                  ^^^^^^^^^^^^^^^^^^^
  File "/Users/J0W432431K/.pyenv/versions/3.11.2/lib/python3.11/site-packages/yt_dlp/extractor/common.py", line 1263, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)

install nightly
if you installed with homebrew:
brew uninstall yt-dlp
brew install --HEAD yt-dlp

or if you installed with pip:
python3 -m pip install -U --pre yt-dlp[default]

dupe of pinned issue

Thank you @bashonly 😊


"invalid channel state" error

Hi!
I'm getting a bug that I get to reproduce only on some rabbitmq installations (ie: it doesn't happen on the docker official images, but does happen on the rabbitmq version in CentOS package manager).
Cargo.toml:
[dependencies]
lapin = "0.27.0-beta.5"

Code:
let url = "amqp://user:PassWord9+@<IP_ADDRESS>:5672/%2f";
let conn = Connection::connect(&url, ConnectionProperties::default()).wait()
    .map_err( |e| format!("RabbitMQ consumer failed to connect to {}", &url) )?;

let channel = conn.create_channel().wait()
    .map_err( |e| format!("RabbitMQ consumer failed to create a channel: {}", e) )?;

let mut queue_declare_options = lapin::options::QueueDeclareOptions::default();
queue_declare_options.durable = false;
queue_declare_options.auto_delete = true;
let queue = channel.queue_declare("queue_name", queue_declare_options, FieldTable::default()).wait()
    .map_err( |e| format!("RabbitMQ consumer failed to declare a queue: {}", e) )?;

channel.queue_bind("queue_name", "exchange_name", "rk", Default::default(), FieldTable::default());

let consumer = channel.basic_consume(&queue, "consumer-tag", BasicConsumeOptions::default(), FieldTable::default()).wait()
    .map_err( |e| format!("RabbitMQ consumer failed to call basic_consume(): {}", e) )?;

The code fails on the line that calls basic_consume:
RabbitMQ consumer failed to call basic_consume(): invalid channel state: Error

Any ideas on what could this be?

Could you run it with RUST_LOG=trace (after initialising env_logger)?
On Sat 21 Sep 2019 at 20:29, unterkontrolle<EMAIL_ADDRESS>wrote:

Hi!
I'm getting a bug that I get to reproduce only on some rabbitmq
installations (ie: it doesn't happen on the docker official images, but
does happen on the rabbitmq version in CentOS package manager).
Cargo.toml:
[dependencies]
lapin = "0.27.0-beta.5"
Code:
let url = "amqp://user:PassWord9+@<IP_ADDRESS>:5672/%2f";let conn = Connection::connect(&url, ConnectionProperties::default()).wait()
.map_err( |e| format!("RabbitMQ consumer failed to connect to {}", &url) )?;
let channel = conn.create_channel().wait()
.map_err( |e| format!("RabbitMQ consumer failed to create a channel: {}", e) )?;
let mut queue_declare_options = lapin::options::QueueDeclareOptions::default();
queue_declare_options.durable = false;
queue_declare_options.auto_delete = true;let queue = channel.queue_declare("queue_name", queue_declare_options, FieldTable::default()).wait()
.map_err( |e| format!("RabbitMQ consumer failed to declare a queue: {}", e) )?;
channel.queue_bind("queue_name", "exchange_name", "rk", Default::default(), FieldTable::default());
let consumer = channel.basic_consume(&queue, "consumer-tag", BasicConsumeOptions::default(), FieldTable::default()).wait()
.map_err( |e| format!("RabbitMQ consumer failed to call basic_consume(): {}", e) )?;
The code fails on the line that calls basic_consume:
RabbitMQ consumer failed to call basic_consume(): invalid channel state: Error
Any ideas on what could this be?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sozu-proxy/lapin/issues/212?email_source=notifications&email_token=AABWNXUJVDPYJBMCFJABUJ3QKZRXBA5CNFSM4IY7ESU2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HM22P5Q,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABWNXSOEWXHMXGF3SYXVBDQKZRXBANCNFSM4IY7ESUQ
.

Sure! I'll be posting the log ASAP

I turned out that the exchange name was incorrect
[2019-09-23T16:53:37Z TRACE lapin::connection] will handle frame: Method(1, Channel(Close(Close { reply_code: 404, reply_text: ShortString("NOT_FOUND - no exchange \'amq.common-exchange\' in vhost \'/\'"), class_id: 50, method_id: 20 })))

So, no bug at all (:

Well, lapin should have given you this error
On Mon 23 Sep 2019 at 19:02, unterkontrolle<EMAIL_ADDRESS>wrote:

I turned out that the exchange name was incorrect
[2019-09-23T16:53:37Z TRACE lapin::connection] will handle frame: Method(1, Channel(Close(Close { reply_code: 404, reply_text: ShortString("NOT_FOUND - no exchange 'amq.common-exchange' in vhost '/'"), class_id: 50, method_id: 20 })))
So, no bug at all (:
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sozu-proxy/lapin/issues/212?email_source=notifications&email_token=AABWNXVE7ULHBXSJGPUVM4TQLDZCZA5CNFSM4IY7ESU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7LRW2A#issuecomment-534190952,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABWNXUYDJKKWZYIP66JNO3QLDZCZANCNFSM4IY7ESUQ
.

Ah, I see that you didn't wait() after queue_bind(). This wait would have given you the proper error.
I should add some annotation about not using a Confimation I guess


error  : Le SDK 'Microsoft.NET.Sdk' spécifié est introuvable

Hello,
I'm trying to get the .exe but can't compile without error...
I've installed dotnet-sdk-2.1.518-win-x64.exe, apparently is not good, can you explain what i'l need please?
Thanks

If you just want the pre-compiled .exe you can head over to the release section. Otherwise you need the dotnet 3.1 and higher sdk

Ok thanks found release, it's good 👍


(3.0.52) drag/drop of instance method ends up on class side

Pre drag drop screenshot:

Where'd _persistentPreferenceDict method go? Post drag drop screenshot (drop target RwgsPlatform):

It's on class side:

@LisaAlmarode - Can you help me characterize this bug?  I tried use cases with the class methods in the example, hierarchy view & classes view, variants of the methods existing (or not). No luck.

This is maddening. It looks like in the method RowanClassService>>savemethodSource:category:, the RowanClassService's #meta instance variable is unreliable and becomes nil as the side effect of some other operation.  It would be nice if modifications to instance variables such as meta use the accessor meta: rather than there being side effects, following proper standards like that make debugging much easier.
A similar problem is easier to reproduce on the class side (although not completely reliable)  Try creating a new class method, clicking on a different package and back to the package and class of the added method, then dragging the class method to a subclass.  meta is usually nil which results in an instance method getting created.
For the instance side, I've been able to reproduce by going to the class side and doing things like removing class methods or displaying senders, which has some side effect on the RowanClassService, and then going to the instance side and dragging a method to a super class or subclass.

Have a fix to try in 3.0.53. We weren't setting meta properly before method compile.
See JadeiteProjectsBrowserPresenter>>onDropOnClassList:

I don't think I can reproduce it.  Hard to be sure...


Make inform dialogues behaviour the same on the whole wallet

I was faced with a problem that the dialogues behaviour is different in different places of wallet and it looks strange.
Some of them are closed if the user clicks outside the dialogue BUT some don't close after clicks.

Please, add examples


Convert browse store to Vuex ts store module

Browse makes use of ES6 Map to cache the search results. Map cannot be reactive under Vue 2.0. Use Vue.set method on an object as a state property so that vuex can properly respond to the changes.
Can switch browse store to ts intermediary to ease the migration.

Finished with 77828c95c53359bede877244a87b908439bab44c


Organisms

Description
infer_organism :

Added min_match_factor_validator in a separate module utils.py.
For every run creating a file for user with count match percentage for all organisms.
Added more input parameters :

min_match : minimum match percentage that top organism needs to have.
factor : factor by which first organism is greater than the second.

Unit tests :

Wrote unit tests for infer_adapter

Fixes # (issue)
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[X] Documentation update

Checklist

[X] I have performed a self-review of my own code
[X] My code follows the existing coding style, lints and generates no new
warnings
[X] I have added type annotations to all function/method signatures, and I
have added type annotations for any local variables that are non-trivial,
potentially ambiguous or might otherwise benefit from explicit typing.
[X] I have commented my code in hard-to-understand areas
[X] I have added ["Google-style docstrings"] to all new modules, classes,
methods/functions or updated previously existing ones
[X] I have added tests that prove my fix is effective or that my feature
works
[X] New and existing unit tests pass locally with my changes and I have not
reduced the code coverage relative to the previous state
[X] I have updated any sections of the app's documentation that are affected
by the proposed changes

Hi @uniqueg , you can change any Documentation, Description, any function name where ever you want.


Support for metrocluster

In a Metrocluster configuration, a switchover/site failover causes Trident to fail, e.g. you can't provision any new volumes. Apparently, Trident looks for the vServer name. However, that name changes in case of a Metrocluster switchover and a "-mc" suffix is added to the original vServer name. Once a switchback is issued, the name is reverted to the original one and then Trident starts working again. So dynamic volume provisioning fails while in switchover (either planned as part of a maintenance activity or unplanned in a real disaster event). Adding the "-mc" suffix is standard Ontap behaviour in a Metrocluster environment and shouldn't cause a Trident failure. Trident should assume that in a metrocluster switchover state, any vServer name with a "-mc" suffix is identical to the original vServer).
Logs during MCC switchover look like this:
time="2019-03-23T09:15:51Z" level=warning msg="Kubernetes frontend has no record of the updated storage class; instead it will try to create it." storageClass=blockip time="2019-03-23T09:15:51Z" level=error msg="Kubernetes frontend couldn't add the storage class: Trident initialization failed; problem initializing storage driver 'ontap-nas': error initializing ontap-nas driver: could not create Data ONTAP API client: error reading SVM details: API status: failed, Reason: Specified vserver not found, Code: 15698" storageClass=blockip storageClass_parameters="map[backendType:ontap-san fsType:xfs provisioningType:thin]" storageClass_provisioner=netapp.io/trident
time="2019-03-23T09:15:51Z" level=warning msg="Kubernetes frontend has no record of the updated storage class; instead it will try to create it." storageClass=premium time="2019-03-23T09:15:51Z" level=error msg="Kubernetes frontend couldn't add the storage class: Trident initialization failed; problem initializing storage driver 'ontap-nas': error initializing ontap-nas driver: could not create Data ONTAP API client: error reading SVM details: API status: failed, Reason: Specified vserver not found, Code: 15698" storageClass=premium storageClass_parameters="map[backendType:ontap-nas provisioningType:thin snapshots:true storagePools:ontapnas_<IP_ADDRESS>:aggr1_dpp501001]" storageClass_provisioner=netapp.io/trident
time="2019-03-23T09:15:51Z" level=warning msg="Kubernetes frontend has no record of the updated storage class; instead it will try to create it." storageClass=standard time="2019-03-23T09:15:51Z" level=error msg="Kubernetes frontend couldn't add the storage class: Trident initialization failed; problem initializing storage driver 'ontap-nas': error initializing ontap-nas driver: could not create Data ONTAP API client: error reading SVM details: API status: failed, Reason: Specified vserver not found, Code: 15698" storageClass=standard storageClass_parameters="map[snapshots:true storagePools:ontapnas_<IP_ADDRESS>:aggr1_dpp509004 backendType:ontap-nas provisioningType:thin]" storageClass_provisioner=netapp.io/trident
(I can provide access to a NetApp internal test lab to reproduce this if required.)

I believe this could be solved by updating the backend with the new vserver name using the "tridentctl update backend  -f <backend_json_file>".
Could you share the setup details.

Any update here? When can we expect this?

No, still tracking as an uncommitted roadmap item.

I work for one of your customers, and we experienced this issue during an unplanned failover. It resulted in nearly half an hour of downtime due to troubleshooting and having to reconfigure and disable/enable the plugin on all nodes.

In my professional life, I have a customer that is running into a simmilar issue. Hence, is there any update on this matter; as this Issue has been "Open" for quite some time now?
Reading through the documentation, I'm left wondering whether it would be an option to update Trident's backend configuration so that:

the "managementLIF" parameter is included;
the "svm" parameter is left out.

The documentation states that the "svm" parameter's value is derived if a management LIF is specified. Thus, somewhat likely the "-mc" suffix in the Storage Virtual Machine's name would no longer matter in such scenario.
As I currently have no combination of a NetApp MetroCluster and Trident at my disposal, I would appreciate it if someone would be able to validate this.

In my professional life, I have a customer that is running into a simmilar issue. Hence, is there any update on this matter; as this Issue has been "Open" for quite some time now?
Reading through the documentation, I'm left wondering whether it would be an option to update Trident's backend configuration so that:

the "managementLIF" parameter is included;
the "svm" parameter is left out.

The documentation states that the "svm" parameter's value is derived if a management LIF is specified. Thus, somewhat likely the "-mc" suffix in the Storage Virtual Machine's name would no longer matter in such scenario.
As I currently have no combination of a NetApp MetroCluster and Trident at my disposal, I would appreciate it if someone would be able to validate this.

Update:
In the meantime, the end customer confirmed the above can be used as workaround. Leaving the "svm" parameter out of Trident's backend configuration indeed ensures the "-mc" suffix is derived while in Switchover. However each MetroCluster Switchover/Switchback still requires an update of de backend configuration (same file can be used).
The above will do the trick for our end customer for now. Also, I hope posting this back will help others. However, we'll still be looking forward to see this "enhancement" incorporated in a future version of Trident so that we no longer need to act manually upon MetroCluster Switchover/Switchback.

Hello,
any Update on this :) ?

This issue is still being tracked as an uncommitted roadmap item. If this request is considered a high priority by you please contact your NetApp account team and let them know.

@gnarl
When we evaluate NetApp/Trident on Metro Cluster with NetApp Japan member, we occurred same problem.
So we can’t proceed to install Metro Cluster to our data center.
I hope that the issue fix.

Hi @ysakashita,
The work to provide a change to detect and handle an MCC switchover isn't currently scheduled on the Trident roadmap. Please work with your NetApp account team to  communicate the priority for this change.

@gnarl Sure. I understood that it was a priority issue of roadmap, not a technical's one. I  already discussed the priority for our business impact with NetApp Japan account team.

Hi @gnarl
We have experienced a similar incident during a Metrocluster failover recently.
Does the Trident documentation state somewhere that connections will not survive such a scenario - I tried digging through the but was unable to find anything ?

Hi @pkris,
Unfortunately I am unable to answer that question as Trident hasn't been qualified against MCC switchover. The recent activity on this GitHub Issue has put focus on MCC compatibility and we'll keep this issue updated when new information is available.

Hi @pkris,
I have more information regarding MCC now. During a MCC switchover existing connections should not be affected. During a switchover all data and management LIFs are migrated to the ONTAP cluster that is now active. Per the above stated workaround the only thing that needs to be updated is the SVM name in the Trident backend config. This change is needed so that Trident can communicate with the MCC ONTAP cluster that is currently active.
Hope this helps.

Hi @gnarl
Thanks for the update.
So the current state of the Trident driver stack does not allow for client-side transparency to failover events in the upstream Metrocluster - would that be a fair conclusion with the current state of things?
Any thoughts on how a client cluster utilizing the Trident driver could become aware of the need to apply the workaround (updating the svm name in the backend config) - i.e. know that a failover has occured upstream?
Cheers

Hi, same here at several customers. MCC Switchover and SVM-DR is working fine, but  restarting the trident pods is needed. Please try to fix this issue.

@gnarl Thanks for the hint. Indeed we configured our backend without SVMs names, using fqrn for svm connection, aggregate wildcards etc. so we do not need to update any backend configs. Easiest was is to just restart the trident pods to initiate a "rescan".

There is a very simple fix for this. If the code logging into the SVM simply accepts both the normal SVM name and the SVM-mc name but checks the UUID of the SVM to make sure this it has remained the same (and I'm assuming that the SVM UUID is registered somewhere), then things will just work. UUID's between the primary MetroCluster SVM and it's site failover secondary SVM-mc are identical.
I can't really see why this should be terribly difficult to implement or why it has been laying around for 3 years.  The MetroCluster platform could well use the bump in Trident functionality as it is the flagship high-availability system. The idea that one has to update perhaps dozens of backend configurations really does lack the necessary automation for high-availability operations.
One could even make this configurable which changes to the SVM name are acceptable (i.e. altSvm spec field) and provide an additional UUID field (altUuid spec field) for SVM-DR setups.

The solution shamziman proposed makes a lot of sense and there are many companies using a MetroCluster, therefore this Issue definitely requires more attention.

Transparent MCC failover support has been enabled in Trident with commit de27a8d. This support requires that the Trident backend configuration file use the SVM IP for management LIF IP address.
Addressing some of the previous comments, upon investigation it was not possible to use the SVM UUID. Sending ZAPI calls to the cluster LIF doesn't work since the SVM still responds to some API calls even though it doesn't have data LIFs. Most of the
Sending ZAPI calls to the SVM LIF was found to work as desired, for the failover scenario, if the API call is tunneled to the correct SVM. Many ZAPI calls that Trident uses are tunneled directly to the SVM and ZAPI tunneling requires the SVM name as the UUID is not supported.
Our investigation did find that the ONTAP REST API implementation does support use of the SVM UUID but we were waiting on REST API fixes available in ONTAP 9.11.1 GA release prior to implementing support for MCC failover using the REST API. The REST API support in Trident continues to be in beta until we've worked through the remaining API gaps with the ONTAP teams.
The reason why the metrocluster APIs were not used is because they require cluster admin access. We strongly recommend that customer us the ONTAP vsadmin user/role when configuring Trident for security reasons. Most use cases are such that storage of cluster credentials in a Kubernetes cluster should not be considered a secure practice.

Is the change to use the REST API and fetch the SVM UUID something that you all will be tracking internally or does one need to open an issue here?
Using an IP address in the field for managementLIF eliminates some options wrt. being able to migrate SVM's to new IP addresses, so I'm hoping that this will eventually be addressed by tracking the UUID of the SVM when this information becomes available via API call.

Hello, @shamziman.  Yes, the planned MCC support with REST involves sending all API calls using the SVM UUID.  That solution won't work with ZAPI, hence the current requirement to provide the SVM LIF address with MCC backends.


Mini issues

Hi Void and Contributors! Kudos to your team work!!
I was going through this platform using an android phone and found these two.

The "data science" and "devops" fields are next to each other while rest of the fields are listed in vertical list format.
The scaling seems bit out of order towards the left side of the screen.

Please ignore if this was not something to be reported. Thank You!

Thanks for reporting @JSinfant.
@PriteshKiri Will this be fixed with your alignment changes?

@codewithvoid you can assign me

Hello @devvsakib, if the issues are resolved in the merged PR, please close this issue as completed.

@RakeshSangem
i solved but he told me to revert change, so i just added my profile json. im not fixing this bug

hello can i take this issue

@celomary yes please. thank you!


Suppress Riot-Android device notifications if detected activity in other device

At now Riot-Android play sound notifications always on new messages, so if I actively use desktop Matrix client - my device rings very often, so I must turn notifications off, and give back to on when I go away from desktop computer.
For solve this problem - will be good to have mode in Riot-Android to detect user activity on other linked device in account, and temporary auto suppress notifications on this device if activity on other device is detected some time ago.

Seems this must be done also in Matrix server API, so I created issue https://github.com/matrix-org/matrix-doc/issues/1119

https://github.com/vector-im/riot-android/issues/1283 / https://github.com/vector-im/riot-web/issues/469

btw:
~at now~ currently
~Riot-Android play sound notifications~ Riot-Android plays sound notifications
~for solve~ to solve
~will be good to~ it would be good to
~temporary auto suppress notifications~ temporarily auto suppress notifications
Hth :)

Sorry for my English :(


Duplicated machine on deployment request using version 0.3.0

Describe the bug
Deploying a VM from a template, contained in a vSphere 6.7 U2 content library, consistently results in a duplicated virtual machine exception. It might be because of a duplicated POST request to the API, if I'm understanding the debugging output correctly.
How to reproduce
You can find below some example code I'm using to reproduce the error:
(I'm verifying there are no virtual machines before executing it)
# Client connection
client_config = ::VSphereAutomation::Configuration.new.tap do |c|
  c.host = host
  c.username = user
  c.password = pass
  c.scheme = 'https'
  c.verify_ssl = false
  c.verify_ssl_host = false
  c.debugging = true
end
client = ::VSphereAutomation::ApiClient.new(client_config)
client.default_headers['Authorization'] = client_config.basic_auth_token
session_id = ::VSphereAutomation::CIS::SessionApi.new(client).create('').value
client.default_headers['vmware-api-session-id'] = session_id

# Target
target_host_id = "host-28"
folder_id = "group-v1050"
resource_pool = "resgroup-194"
target = VSphereAutomation::VCenter::VcenterOvfLibraryItemDeploymentTarget.new(
  host_id: target_host_id,
  resource_pool_id: resource_pool,
  folder_id: folder_id
)

# Deployment
name = "test-machine"
datastore_id = "..."
template_id = "..."
network_mapping = [{:key=>"bridged", :value=>"network-o1060"}]

deploy_spec = VSphereAutomation::VCenter::VcenterOvfLibraryItemResourcePoolDeploymentSpec.new(
  name: name,
  accept_all_EULA: true,
  default_datastore_id: datastore_id,
  network_mappings: network_mapping,
  storage_provisioning: VSphereAutomation::VCenter::VcenterOvfDiskProvisioningType::THIN
)
deploy = VSphereAutomation::VCenter::VcenterOvfLibraryItemDeploy.new(
  deployment_spec: deploy_spec,
  target: target
)

VSphereAutomation::VCenter::OvfLibraryItemApi.new(client).deploy(template_id, deploy)

Output
The machine gets created, but it returns a "virtual machine" duplication error:
Calling API: OvfLibraryItemApi.deploy ...
HTTP request body param ~BEGIN~
{"target":{"resource_pool_id":"resgroup-194","host_id":"host-28","folder_id":"group-v1050"},"deployment_spec":{"name":"test-machine","accep$
_all_EULA":true,"network_mappings":[{"key":"bridged","value":"network-o1060"}],"storage_provisioning":"thin","default_datastore_id":"datast$re-39"}}                                                                                ~END~

Found bundle for host vcsa-jil.vmware.local: 0x5563b9d6fd10 [can pipeline]
Re-using existing connection! (#6) with host vcsa-jil.vmware.local
Connected to vcsa-jil.vmware.local (<IP_ADDRESS>) port 443 (#6)
POST /rest/com/vmware/vcenter/ovf/library-item/id:69eb2a19-bfe2-4b5e-85e8-c367f05008d7?~action=deploy HTTP/1.1
Host: vcsa-jil.vmware.local
User-Agent: SDK/0.3.0 Ruby/2.3.8 (linux; ; x86_64)                                                                                Content-Type: application/json
Authorization: Basic ...
vmware-api-session-id: ...
Accept: application/json
Content-Length: 288

upload completely sent off: 288 out of 288 bytes                                                                                Connection died, retrying a fresh connect                                                                                Curl_http_done: called premature == 0
Closing connection 6
TLSv1.2 (OUT), TLS alert, Client hello (1):
Issue another request to this URL: 'https://vcsa-jil.vmware.local/rest/com/vmware/vcenter/ovf/library-item/id:69eb2a19-bfe2-4b5e-85e8-c367f$
5008d7?~action=deploy'
Hostname vcsa-jil.vmware.local was found in DNS cache
  Trying <IP_ADDRESS>...
TCP_NODELAY set
Connected to vcsa-jil.vmware.local (<IP_ADDRESS>) port 443 (#7)
ALPN, offering http/1.1
Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
successfully set certificate verify locations:
  CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
SSL re-using session ID
TLSv1.2 (OUT), TLS handshake, Client hello (1):
...some binary output...
SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
ALPN, server did not agree to a protocol
old SSL session ID is stale, removing
Server certificate:
 ...
POST /rest/com/vmware/vcenter/ovf/library-item/id:69eb2a19-bfe2-4b5e-85e8-c367f05008d7?~action=deploy HTTP/1.1
Host: vcsa-jil.vmware.local
User-Agent: SDK/0.3.0 Ruby/2.3.8 (linux; ; x86_64)
Content-Type: application/json
Authorization: Basic ...
vmware-api-session-id: ...
Accept: application/json
Content-Length: 288

upload completely sent off: 288 out of 288 bytes
oHTTP/1.1 200 OK
Date: Wed, 25 Sep 2019 11:36:56 GMT
Content-Type: application/json
Transfer-Encoding: chunked

Curl_http_done: called premature == 0
Connection #7 to host vcsa-jil.vmware.local left intact
HTTP response body ~BEGIN~
{"value":{"error":{"errors":[{"category":"SERVER","error":{"@class":"com.vmware.vapi.std.errors.already_exists","messages":[{"args":["VirtualMachine","test$
machine"],"default_message":"An object of type \"VirtualMachine\" named \"test-machine\" already exists.","id":"com.vmware.vdcs.util.duplic$
te_name"}]}}]},"succeeded":false}}
~END~

API called: OvfLibraryItemApi#deploy
Data: #<VSphereAutomation::VCenter::VcenterOvfLibraryItemDeployResult:0x00005563b61774f0 @value=#<VSphereAutomation::VCenter::VcenterOvfLibr
aryItemDeploymentResult:0x00005563b6176a78 @succeeded=false, @error=#<VSphereAutomation::VCenter::VcenterOvfLibraryItemResultInfo:0x00005563
b6175e20 @errors=[#<VSphereAutomation::VCenter::VcenterOvfOvfError:0x00005563b61752b8 @category="SERVER"<EMAIL_ADDRESS>std.errors.already_exists", :messages=>[{:args=>["VirtualMachine", "test-machine"], :default_message=>"An object of type \"VirtualMachine\"
named \"test-machine\" already exists.", :id=>"com.vmware.vdcs.util.duplicate_name"}]}>], @warnings=[], @informatio
n=[]>>>
Status code: 200
Headers: {"Date"=>"Wed, 25 Sep 2019 11:36:56 GMT", "Content-Type"=>"application/json", "Transfer-Encoding"=>"chunked"}

=> #<VSphereAutomation::VCenter::VcenterOvfLibraryItemDeployResult:0x00005563b61774f0
 @value=
  #<VSphereAutomation::VCenter::VcenterOvfLibraryItemDeploymentResult:0x00005563b6176a78
   @error=
    #<VSphereAutomation::VCenter::VcenterOvfLibraryItemResultInfo:0x00005563b6175e20
     @errors=
      [#<VSphereAutomation::VCenter::VcenterOvfOvfError:0x00005563b61752b8
        @category="SERVER",
        @error=
<EMAIL_ADDRESS>          :messages=>
           [{:args=>["VirtualMachine", "test-machine"],
             :default_message=>"An object of type \"VirtualMachine\" named \"test-machine\" already exists.",
             :id=>"com.vmware.vdcs.util.duplicate_name"}]}>],
     @information=[],
     @warnings=[]>,
   @succeeded=false>>

Versions

Ruby: tried with different versions from 2.3 to 2.6 with the same result
vSphere Automation SDK: tried with different versions up to 0.3.0
OS: linux

Additional notes
I wonder if this may be connected to a retry on the http client. Not sure if that output message means it is actually issuing another request:
Issue another request to this URL: 'https://vcsa-jil.vmware.local/rest/com/vmware/vcenter/ovf/library-item/id:69eb2a19-bfe2-4b5e-85e8-c367f$
5008d7?~action=deploy

It seems that the "typhoeus" dependency was removed in >= 0.4.0, not sure if that might fix the problem I'm finding. However, I haven't been able to test those versions because I'm getting NotFound errors, similar to the ones described in #57.

Now that #57 has been fixed, please give v0.4.3 a try and see if that fixes the issue for you. Thanks for reporting @carlossm!

Thank you for the fix.
Now with the latest version, it seems I'm getting an EOF error instead of the "duplicated machine":
pry(main)> VSphereAutomation::VCenter::OvfLibraryItemApi.new(client).deploy(template_id, deploy)
Calling API: OvfLibraryItemApi.deploy ...
Request Body:
{"target":{"resource_pool_id":"resgroup-194","host_id":"host-28","folder_id":"group-v1050"},"deployment_spec":{"name":"test-machine-8","acce
pt_all_EULA":true,"network_mappings":[{"key":"bridged","value":"network-o1060"}],"storage_provisioning":"thin","default_datastore_id":"datas
tore-39"}}

EOFError: end of file reached
lib/ruby/2.6.0/net/protocol.rb:225:in `rbuf_fill'
lib/ruby/2.6.0/net/protocol.rb:191:in `readuntil'
lib/ruby/2.6.0/net/protocol.rb:201:in `readline'
lib/ruby/2.6.0/net/http/response.rb:40:in `read_status_line'
lib/ruby/2.6.0/net/http/response.rb:29:in `read_new'
lib/ruby/2.6.0/net/http.rb:1509:in `block in transport_request'
lib/ruby/2.6.0/net/http.rb:1506:in `catch'
lib/ruby/2.6.0/net/http.rb:1506:in `transport_request'
lib/ruby/2.6.0/net/http.rb:1479:in `request'
lib/ruby/2.6.0/net/http.rb:1472:in `block in request'
lib/ruby/2.6.0/net/http.rb:920:in `start'
lib/ruby/2.6.0/net/http.rb:1470:in `request'
lib/ruby/gems/2.6.0/gems/vsphere-automation-runtime-0.4.3/lib/vsphere-automation-runtime/api_client.rb:71:in `call_api'
lib/ruby/gems/2.6.0/gems/vsphere-automation-vcenter-0.4.3/lib/vsphere-automation-vcenter/api/ovf_library_item_api.rb:123:in `deploy_with_http_info'
lib/ruby/gems/2.6.0/gems/vsphere-automation-vcenter-0.4.3/lib/vsphere-automation-vcenter/api/ovf_library_item_api.rb:82:in `deploy'
(pry):48:in `<main>'

Any ideas?

I'll take a look. Not sure what's causing it.

FYI...we just updated to vCenter 6.7U3 and are still seeing the same issue.

@carlossm @NJSchulz Could you take a look at v0.4.4 and set a timeout to see if that allows the deploy to finish properly. You can configure it through the Configuration object
configuration = VSphereAutomation::Configuration.new.tap do |c|
  c.timeout = 100000
  ... the rest of your configuration details ...
end

FYI @jrgarcia, I ran some tests with the timeout option set, but it seems we still get the 'end of file' exception with any version 0.4.*. With the latest version the backtrace is similar to the one I already mentioned:
end of file reached
/.rbenv/versions/2.6.5/lib/ruby/2.6.0/net/protocol.rb:225:in `rbuf_fill'
/.rbenv/versions/2.6.5/lib/ruby/2.6.0/net/protocol.rb:191:in `readuntil'
/.rbenv/versions/2.6.5/lib/ruby/2.6.0/net/protocol.rb:201:in `readline'
/.rbenv/versions/2.6.5/lib/ruby/2.6.0/net/http/response.rb:40:in `read_status_line'
/.rbenv/versions/2.6.5/lib/ruby/2.6.0/net/http/response.rb:29:in `read_new'
/.rbenv/versions/2.6.5/lib/ruby/2.6.0/net/http.rb:1509:in `block in transport_request'
/.rbenv/versions/2.6.5/lib/ruby/2.6.0/net/http.rb:1506:in `catch'
/.rbenv/versions/2.6.5/lib/ruby/2.6.0/net/http.rb:1506:in `transport_request'
/.rbenv/versions/2.6.5/lib/ruby/2.6.0/net/http.rb:1479:in `request'
/.rbenv/versions/2.6.5/lib/ruby/2.6.0/net/http.rb:1472:in `block in request'
/.rbenv/versions/2.6.5/lib/ruby/2.6.0/net/http.rb:920:in `start'
/.rbenv/versions/2.6.5/lib/ruby/2.6.0/net/http.rb:1470:in `request'
/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/vsphere-automation-runtime-0.4.6/lib/vsphere-automation-runtime/api_client.rb:71:in `call_api'
/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/vsphere-automation-vcenter-0.4.6/lib/vsphere-automation-vcenter/api/ovf_library_item_api.rb:123:in `deploy_with_http_info'
/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/vsphere-automation-vcenter-0.4.6/lib/vsphere-automation-vcenter/api/ovf_library_item_api.rb:82:in `deploy'


Expected a macro identifier for a pound literal expression

I'm trying something similar to the doc's
 "123🦄456".replacingFirstMatch(of: #"\d+"#, with: "")
//=> "🦄456"

But I get a build error:

Wrong Syntax: "...".replacingAllMatches(of: #Setup#, with: "")
Correct Syntax: "...".replacingAllMatches(of: #"Setup"#, with: "")


Error when trying to uglify object with key defined via square brackets

If I try to uglify this:
var foo = {bar: "key"};
var obj = {
    [foo.bar]: 3
};

I get the following error:
{ SyntaxError: Unexpected token: punc ([)
    at JS_Parse_Error.get (eval at <anonymous> (C:\Users\USER\Desktop\conveuro\node_modules\uglify-js\tools\node.js:20:1), <anonymous>:71:23)
    at formatError (util.js:610:16)
    at formatValue (util.js:514:18)
    at formatProperty (util.js:801:11)
    at formatObject (util.js:617:17)
    at formatValue (util.js:579:18)
    at formatProperty (util.js:801:11)
    at formatObject (util.js:617:17)
    at formatValue (util.js:579:18)
    at inspect (util.js:294:10)
        message: 'Unexpected token: punc ([)',
        filename: 'foo.js',
        line: 3,
        col: 4,
        pos: 42 },
     plugin: 'gulp-uglify',
     fileName: 'C:\\Users\\USER\\Desktop\\conveuro\\extension\\content-script\\_src\\js\\foo.js',
     showStack: false }

And this is perfectly valid JavaScript. If I execute it in the console, the value of obj would be {key: 3}.
I use version 3.0.1 of the plugin, which is the latest.

This requires you to use a version of UglifyJS that supports ES Harmony features. Check out the README for more details.

Hi @terinjokes. I had a look to the README but I still don't know how to fix this issue. I tried installing this but didn't work:
"uglify-js": "git+https://github.com/mishoo/UglifyJS2.git#harmony"


Update to DataFusion 33

Which issue does this PR close?

Closes #.
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

FYI @r4ntix


Italian translation

Added IT translation even to align the website translation with app.ens.

This is very awesome, I would love to get involved with what you guys are building.  Either official or unofficial is cool with me


IE had been lock cant use this solution to use IE mode

[Enter feedback here]
after 6.29 system lock IE driver so when we use IEDriverServer to extend path Edge

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

ID: de9fa537-f960-f6f9-a39f-5ea14b41f01f
Version Independent ID: de9fa537-f960-f6f9-a39f-5ea14b41f01f
Content: Use Internet Explorer Driver to automate IE mode in Microsoft Edge - Microsoft Edge Development
Content Source: microsoft-edge/webdriver-chromium/ie-mode.md
Product: microsoft-edge
Technology: devtools
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Thanks for the feedback and sorry about the delay replying. I think you will get more help by posting your feedback to this repository instead: https://github.com/MicrosoftEdge/EdgeWebDriver/issues
Can you create a new issue there and describe the problem you are experiencing?
Thanks, and sorry for the inconvenience.


Feature request:  Change default authentication provider for user registration.

Feature request:  Change default authentication provider for registration.
At the moment there are two mechanisms for creating an account:

An admin creates one manually.
If enabled anybody can run through the account registration procedure to create an account with LOCAL authentication.

This means that either users have to wait for a sysadmin to creat an account for them, or that sysadmins have no control over who signs up for an account.  It also means that user driven registration always uses local authentication and never an alternative (eg LDAP).
It would be good if gitea could allow anyone with a valid login (eg: a valid LDAP login) to create themselves an account.

Possible further extensions to this:

A user attempting to log in with with a username and password which do not match a gitea user but will authorise with LDAP could be bounced to a pre-authorised account registration page ("Just add full name and email address to complete")

Gitea could enforce that that gitea usernames and authentication provider (LDAP) usersnames match - at least for registration.

There is already an open issue to provide a bootstrap config that enables ldap or other authentication sources directly from the beginning. Than nobody will be able to register on the wrong place

Are you referring to  #209?  That's quite a different issue.

Are you referring to  #209?  That's quite a different issue.  #209 is about automating setup from the point of view of the sysadmin during installation.  This issue is about allowing users to set themselves up on an established and running instance where they already have a single-sign-on user-name and password.

LDAP-authentication is already possible when the admin goes through the installation-process so I don't really see the issue here?

On Thu, Jan 19, 2017 at 10:26:12AM -0800, Philip Couling wrote:

It would be good if gitea could allow anyone with a valid login (eg: a valid LDAP login) to create themselves an account.

This is already supported. Anyone with LDAP gets an account automatically
created upon first login. We disabled the registration and used a custom
template to provide a link to the external LDAP registration page.
Works fine.

@couling did we respond to your concern ? Can this be closed ? (spring cleanup)


Tokens being covered by object (door, furniture, painting ...) after UNDO

This bug is easily reproduce, when you have token on top of doors and furniture component.
Token should always been on top of  as you need to click on them to be able to activate them.
Steps to reproduce :

start a scenario with  token on top of doors and/or furniture component (example: A strain on reality)
do any action, then undo it
token are now under the furniture component, and cannot be selected (see capture)

No solution to fix it, you have to restart the game.

Valkyrie Version
Brynhildr 2.1.0 (but I'm sure it can be reproduced in 2.0)

I've seen this in 1.6.1 for sure.

So first of all, this issue happens when UNDOing, and when loading a quest.
This is basically the same action.
When loading a quest, the application is using the token order provided in the save file.
The first item loaded is on the bottom, the last one is on top.
For example : if a token of action is defined before a token of door, then the token of door will be on top.
It means the order used by the scenario to define objects/token is quite important.
The token that should be clickable should be defined last.
There is no easy way to identify token that should be on top from just other token in the code.
So I don't see any solution on app side yet.
@scrubbless in your case, you should make sure that the items with actions are defined after the doors and others items.
If someone has an idea for a fix,  please share !

The doors are placed in events then the tokens. But token order in the editor is listed based on when tokens were created.
That's a lot of reordering to do.
Could you bring all tokens that have events assigned (event=xxxx) to the top?

I would prefer to find a way to save the token items in the same order that they are displayed while playing.
I'm afraid reordering based on the event assigned may break something for someone else.

The problem is, how do you find this out? Tokens and Events are not sequencial and you can't always follow the event chain order to find a sequence.
Some event chains will place the same token too.
I guess you could just tag tokens every time they are placed with a number.
Then place them in lowest to highest order

After some time thinking and a bit of documentation reading, I found out the reason for this issue and the fix.
The reason : the type Dictionary<T1, T2> used to store the list of board items does not retain order.
The fix : The class OrderedDictionary does not exist unfortunately.
So I've added a 'sister' List of object name, and use this to write the savegame.
Tested and approved on "a strain for Reality".


Cannot work after install it by follow installation tutorial : WIN 10/VS2015

Hi!
I am trying to run bonobo git server on my win 10. I have already install VS 2015 and IIS tools.
I converted the 5.2.0 zip to an application. But I run http://localhost/Bonobo.Git.Server, I have a blank page with no error.
I have any idea.
Thanks for your help.

@CTotophe It's a bit beyond the developers on the project to be able to help with general IIS setup issues - you'll need to find a basic guide on getting ASP.Net applications running under IIS.
You shouldn't need Visual Studio to get Bonobo running, and that's a very complex tool if you're not familiar with it.
You might find that running dism /online /enable-feature /featurename:NetFx4Extended-ASPNET45 at a Administrator command prompt helps, but I think probably you've got something simple wrong in the IIS setup.

@willdean I understand, I think too that the problem is IIS config. I will continue to search.
I know that Bonobo shouldn't need Visual Studio. I would like work visual studio and GIT. Actually, I work with subversion.
Thank @willdean

@willdean I understand, I think too that the problem is IIS config. I will continue to search.
I know that Bonobo shouldn't need Visual Studio. I would like work visual studio and GIT. Actually, I work with subversion.
Thank @willdean

@willdean I resolved my problem, I reinstall all IIS components.
Thanks :)

Cool!  Thanks for letting us know


Prepare Awkward for Dask (kernel-level DAG)

I used "cherry-pick" to select the commits from this PR that are relevant beyond the prototype. Since the "kernel-level thing" will not be a DAG (https://github.com/ContinuumIO/dask-awkward/discussions/2), we don't want all of these changes, but a few of them are general fix-ups, not specific to the prototype.


fix: set node engine minimum

fix: set node engine minimum

:hammer_and_wrench: Type Of Change

[x] Fix
[ ] Feature
[ ] Refactoring
[ ] Documentation

:book: Description
While we use node 18, it doesn't mean it's actually required to use our library. Used ls-engines to determine what our actual node required version is and set it to that.

Isn't it better to keep >=16?
I don't think we need to set it as low as 12.
This might bring us issues in the future if we add something that's newer that 12, right?

It's not really accurate, and even setting it at 16 we might have that same issue in the future. However, we could probably use this library to automate a simple check for whenever our minimum version changes. I'll try doing this.

Merging for now to unblock ubervoice. Will create subsequent PR for the automated check.


Improved Sample app

Feature request for Cloudinary React Native SDK
Improved Sample app
Explain your use case
Need an improved sample app to demonstrates the SDK capabilities
Describe the problem you’re trying to solve
Give developers an easy way to understand the SDK usage through a sample app
Do you have a proposed solution?
Build an improved sample app

See: https://github.com/cloudinary/cloudinary-react-native/tree/master/example

@mensonones Would you like to work on improving the sample application?

@mensonones Would you like to work on improving the sample application?

yes! I can create an example of image upload, or do you have something specific in mind?


"Post an Adaptive Card to a ..." connector update breaks approval flow

Hi,
one customer complained that he wasn't able to use the Teams approval which is posting adaptive cards to a team. The adaptive card is displayed, but you can't click any action.
I#ve checked the Approval flow and it seems that the action was "redesigned".
Before (another tenant is still using the "old" action):

Now:

If i click on "Edit adaptive card" the card designer opens and an error states that the json is not valid.

I assume that the connector update broke the function. I will now try to figure out how i can rebuild the card with this designer. Are other affected by this issue also, or is this an single issue?

Sorry, there was no connector update. The new view came from the experimental features setting in flow. I will now debug the original issue and create a new issue if there is a general failure.


@loadable/babel-plugin doesn't work with dynamic imports

🐛 Bug Report
function loadable(chunkName) {
    return require('@loadable/component').default(() => import(/* webpackChunkName: "
   [request]" */ `../pages/${chunkName}`));
}

To Reproduce
UnhandledPromiseRejectionWarning: Invariant Violation: loadable: SSR requires
`@loadable/babel`, please install it

Hello @Confetti7, can you please submit a new issue with more detail and a repro example. I am sorry but with this one I can't help you.


Add option on conf file

Hi,
I add couple of parameters needed to custom a a configuration backup backup.

I am going to simplify the role's configuration in order to remove these pesky variables, but thanks for your contribution.


[FLINK-18971] Support to mount kerberos conf as ConfigMap and Keytab …

…as Secrete
What is the purpose of the change
Support to mount kerberos conf as ConfigMap and Keytab as Secrete
Brief change log

Add "kubernetes.kerberos.krb5-conf.path" Config option, which specify the local location of the krb5.conf file to be mounted on the JobManager and TaskManager for Kerberos.
Introduce KerberosMountDecorator

Verifying this change
This change added tests and can be verified as follows:

Existing UTs and IT cases.
KerberosMountDecoratorTest

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? docs

@flinkbot run azure

@xintongsong Thanks for the review. Comments addressed.


docs(quickstart): should create namespace before apply yaml files

In quickstart, if we directly apply yaml files, it will raise namespace-not-found errors. It'd be better if we add create namespace command.

Thanks for your participation. FYI, if the namespace can be automatically created when the YAML is applied, better user experience may be provided. You can add the YAML created the namespace in the kmesh code repository, for details:
apiVersion: v1
kind: Namespace
metadata:
   name: kmesh-system

Thanks for your participation. FYI, if the namespace can be automatically created when the YAML is applied, better user experience may be provided. You can add the YAML created the namespace in the kmesh code repository, for details:
apiVersion: v1
kind: Namespace
metadata:
   name: kmesh-system

sure, i can create a pr in kmesh for that

Pls update the PR description.


Fix Travis deployment again.

Apparently, the deploy script has to be invoked as a script instead of inline Bash.

bors r+


Graphs: Implement A* Algorithm in Java

@akgmage assign me i will solve

@akgmage I would like to work on this issue


Daily tasks check is all or non

I have a CalDAV server that I imported tasks from to Errands, when I mark a task as done, it counts it as done forever and removes all the future listings of the task.
Expected behavior
it should mark only today's task as done.

What CalDAV server do you use? Nextcloud or something different?

A local one with Radicale

It's probably because Errands does not support recurrent tasks yet. It will in next releases.

Closing as it will be worked on for #90


feat: Avoid cli setup checks when not required

In order to optimize startup time, especially when only issuing a non
cloud-cli required command, collie now only checks cloud cli configuration
when required.
Should mitigate or at least lessens @JohannesRudolph startup time issue.

Thanks for taking this up so quickly. I think this is a step in the right direction and certainly fixes the use cases I described.
However I wonder if we can go even further. Some ideas:

make an "optimistic" assumption that the CLIs are installed when they are also configured (test cli is installed when running collie configure, when it fails with another command fall back on the standard error handling for CLI invocations)
run the checks concurrently (capture the promises returned by checkCli then await Promise.all(...). For example, gcloud --version takes ~1s on my machine and it's easy to see why invoking all three CLIs serially takes so long.

Thanks for taking this up so quickly. I think this is a step in the right direction and certainly fixes the use cases I described.
However I wonder if we can go even further. Some ideas:

make an "optimistic" assumption that the CLIs are installed when they are also configured (test cli is installed when running collie configure, when it fails with another command fall back on the standard error handling for CLI invocations)
run the checks concurrently (capture the promises returned by checkCli then await Promise.all(...). For example, gcloud --version takes ~1s on my machine and it's easy to see why invoking all three CLIs serially takes so long.

sounds like a bigger refactoring.
sounds like a quick win. @tfelix could you pick this up in this PR?

sounds like a quick win. @tfelix could you pick this up in this PR?

Thanks Johannes I merge this now then.


io_uring_opcode_supported should be compiled

As it stands now, io_uring_opcode_supported is currently a static inline function in the liburing.h header file.
This is fine for C and C++ code. However, it makes this library more difficult to use from languages like Rust or from other language's FFIs.
The function appears trivial but relies on the struct definition.
io_uring_opcode_supported should be compiled and appear in the resulting .a/.so.

We can probably probably weak versions of the static inline ones. What do you currently do for the other functions, like io_uring_cqe_seen() or io_uring_cq_advance()?

What I'm doing now in my Rust project is just creating an intermediate .c file that contains stuff like:
#include <liburing.h>

int rio_io_uring_opcode_supported(const struct io_uring_probe *p,
                                  int op)
{
  return io_uring_opcode_supported(p, op);
}

and then I'll compile this to a static archive which I link against in the final binary.

Related: https://github.com/axboe/liburing/issues/660#issuecomment-1328533871 ...

@axboe I ran into the same issue calling liburing from Julia.
I am guessing that the same issue will effect each new language that wants to interface with liburing.
Would you consider adding a C file to the library with functions something like _noinline__io_uring_prep_poll_add() to wrap each of the static inline functions ?
The alternatives are:

Each language interface library builds its own C wrapper for the static inline functions
Each language interface library translates the content of the static inline functions into the target language.

Either of these alternatives increase the risk of errors due to repetition of work.
It would be really great to be able to talk to liburing directly from non-C languages without relying on a hand-coded shim, or patch set that ends up being out of date.

Actually, @axboe, I can implement whatever changes you'd like here. I've been consistently wrapping all these liburing functions in my Rust code and it's easier to just fix it at the source.

Just do what will work for you, I suspect the other use cases are identical or very similar.

@cmazakas, are you suggesting that you will submit a PR to axboe/liburing that contains the  rio_io_uring_*() functions from your rio/src/liburing/lib.c ?
This would be great!
(I assume the rio_ prefix will be changed to something else.)

If you are concerned about performance it would maybe make more sense to reimplement inline functions natively in Rust? However I'm not sure what the caveats would be with upgrading the library, and so you might need some additional automated testing here

@DylanZA, the problem I encountered when I started along the path of translating inline functions was that I quickly arrived at macro code that is all magical gcc attributes built-in functions (see below).
It might end up being worthwhile to translate this code at some point to avoid an extra C-function call.
However, the primary goal is to get algorithmic level performance improvements by using io_uring's async notification and buffer sharing features.
https://github.com/axboe/liburing/blob/9bdeca7004ab10883437ed1a4bb016fa58fd60f6/src/include/liburing/barrier.h#L70-L72
https://github.com/gcc-mirror/gcc/blob/9a265c974cd85b8eae5ea607185e689f063db4a1/gcc/ginclude/stdatomic.h#L129-L135
#define atomic_store_explicit(PTR, VAL, MO)				\
  __extension__								\
  ({									\
    __auto_type __atomic_store_ptr = (PTR);				\
    __typeof__ ((void)0, *__atomic_store_ptr) __atomic_store_tmp = (VAL);	\
    __atomic_store (__atomic_store_ptr, &__atomic_store_tmp, (MO));	\
  })

I was more or less thinking about actually turning the static inline into a macro and then creating an extra archive file that contains all the symbols.
Basically, define the macro to be empty, include the liburing.h header in a source file and then compiling that and turning it into a library that'd live alongside liburing.a
To this end, existing liburing users aren't affected and "us" (the FFI folk) now have an archive that exports all the symbols we want.
I have yet to experiment with this though to test its viability.

Alright, I have a small branch going right now with a simple static archive being generated
https://github.com/cmazakas/liburing/tree/liburing-ffi
Seems like everything is able to link (haven't run any binaries yet) and objdump seems to confirm that everything is being exported.
I'll add support for shared objects next and then I think it should be good to go!


Fixed test coverage step name, Added Codecode and removed from Travis

Description

Clarified Go test coverage vs. codecov
Added codecov as a Github Action
Removed codecov comment from Travis

Fixes # (issue)
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[X] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I run make pre-commit to check fmt/vet/lint/test-no-fdo

fail on lint-[2022-09-23T18:39:13.800Z] ['error'] There was an error running the uploader: No coverage files located, please try use -f, or change the project root with -R

/retest

Codecov Report
Base: 31.58% // Head: 35.59% // Increases project coverage by +4.00% :tada:

Coverage data is based on head (263439b) compared to base (36b00ae).
Patch coverage: 36.59% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1511      +/-   ##
==========================================
+ Coverage   31.58%   35.59%   +4.00%
==========================================
  Files          46       58      +12
  Lines        5676     8600    +2924
==========================================
+ Hits         1793     3061    +1268
- Misses       3627     5140    +1513
- Partials      256      399     +143

Impacted Files
Coverage Δ

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

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

logger/logger.go
2.32% <ø> (-0.31%)
:arrow_down:

main.go
0.00% <0.00%> (ø)

pkg/clients/client.go
0.00% <ø> (ø)

pkg/dependencies/main.go
0.00% <0.00%> (ø)

pkg/models/base.go
100.00% <ø> (ø)

pkg/models/commits.go
0.00% <0.00%> (ø)

pkg/models/events.go
0.00% <0.00%> (ø)

pkg/models/installers.go
0.00% <0.00%> (ø)

... and 95 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[PCL]Build failed

Host Environment

OS: Windows 10
Compiler: MSVC 2022

To Reproduce
Steps to reproduce the behavior:
`./vcpkg install  pcl[core,opengl,vtk]:x64-windows
Failure logs
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:155 (message):
Command failed: D:/vcpkg/downloads/tools/cmake-3.21.1-windows/cmake-3.21.1-windows-i386/bin/cmake.exe --build . --config Release --target install -- -v -j7
Working Directory: D:/vcpkg/buildtrees/pcl/x64-windows-rel
See logs for more information:
D:\vcpkg\buildtrees\pcl\install-x64-windows-rel-out.log
Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:102 (vcpkg_execute_build_process)
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:41 (vcpkg_cmake_build)
ports/pcl/portfile.cmake:73 (vcpkg_cmake_install)
scripts/ports.cmake:142 (include)
install-x64-windows-rel-out.log

Thanks for posting this issue. This is a bug of Visual Studio 2022, if you need use pcl in your project, you can use low version of Visual Studio. We will fix this error in furture.

Closed this due to duplicate with #19561, please pay attention of #19561.