Failed to find video URL from teachable site

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 a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2023.02.17 (update instructions) or later (specify commit)
[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

Provide a description that is worded well enough to be understood
I am trying to get the videos in its respective pages assigned to the respective folders, but it cannot even get the URL within the site.
it is not specific to only this site, as it also happens to other teachable pages too.
cookies here: https://pastebin.com/QFTEY9st
please assist, thanks!
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] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
E:\>yt-dlp --cookies cookies.txt --verbose -o "local_path\%(playlist_index)s - %(title)s.%(ext)s" --all-subs --playlist-start 1 -f "[height >=? 300][tbr>200]" teachable:https://my.builtwithscience.com/courses/372909 --verbose
[debug] Command-line config: ['--cookies', 'cookies.txt', '--verbose', '-o', 'local_path\\%(playlist_index)s - %(title)s.%(ext)s', '--all-subs', '--playlist-start', '1', '-f', '[height >=? 300][tbr>200]', 'teachable:https://my.builtwithscience.com/courses/372909', '--verbose']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2023.02.17 [a0a7c01] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.22621-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: none
[debug] Optional libraries: Cryptodome-3.17, brotli-1.0.9, certifi-2022.12.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-10.4
[debug] Proxy map: {}
[debug] Loaded 1782 extractors
[TeachableCourse] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909
[TeachableCourse] 372909: Downloading webpage
[download] Downloading playlist: Intermediate BUILD
[TeachableCourse] Playlist Intermediate BUILD: Downloading 16 items of 16
[download] Downloading item 1 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/33884604
[Teachable] 33884604: Downloading webpage
ERROR: [Teachable] 33884604: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

[download] Downloading item 2 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/5698965
[Teachable] 5698965: Downloading webpage
ERROR: [Teachable] 5698965: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

[download] Downloading item 3 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/5698966
[Teachable] 5698966: Downloading webpage
ERROR: [Teachable] 5698966: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

[download] Downloading item 4 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/32705226
[Teachable] 32705226: Downloading webpage
ERROR: [Teachable] 32705226: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

[download] Downloading item 5 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/5698973
[Teachable] 5698973: Downloading webpage
ERROR: [Teachable] 5698973: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

[download] Downloading item 6 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/5698978
[Teachable] 5698978: Downloading webpage
ERROR: [Teachable] 5698978: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

[download] Downloading item 7 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/5698972
[Teachable] 5698972: Downloading webpage
ERROR: [Teachable] 5698972: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

[download] Downloading item 8 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/5698975
[Teachable] 5698975: Downloading webpage
ERROR: [Teachable] 5698975: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

[download] Downloading item 9 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/5698976
[Teachable] 5698976: Downloading webpage
ERROR: [Teachable] 5698976: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

[download] Downloading item 10 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/5698977
[Teachable] 5698977: Downloading webpage
ERROR: [Teachable] 5698977: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

[download] Downloading item 11 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/5698946
[Teachable] 5698946: Downloading webpage
ERROR: [Teachable] 5698946: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

[download] Downloading item 12 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/5698947
[Teachable] 5698947: Downloading webpage
ERROR: [Teachable] 5698947: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

[download] Downloading item 13 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/5698948
[Teachable] 5698948: Downloading webpage
ERROR: [Teachable] 5698948: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

[download] Downloading item 14 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/5698950
[Teachable] 5698950: Downloading webpage
ERROR: [Teachable] 5698950: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

[download] Downloading item 15 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/5698951
[Teachable] 5698951: Downloading webpage
ERROR: [Teachable] 5698951: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

[download] Downloading item 16 of 16
[Teachable] Extracting URL: teachable:https://my.builtwithscience.com/courses/372909/lectures/5698952
[Teachable] 5698952: Downloading webpage
ERROR: [Teachable] 5698952: Unable to find video URL; 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 "yt_dlp\extractor\common.py", line 693, in extract
  File "yt_dlp\extractor\teachable.py", line 173, in _real_extract

I can confirm that I'm having the same issue.

I am having the same issue with another teachable course.
Let me know if you need my verbose information also.

https://github.com/yt-dlp/yt-dlp/issues/3564


My Contacts - Not possible to edit address

Affected version: 1.0.9
Steps:

Create a contact in the address book.
Choose it.
Try edit address.

Result:
Edit input is closed but the address won't change.
Expected result:

User should be able to edit address.
Wallet should verify if provided address is valid.
Wallet should verify if provided address does not exist already in the address book.

Video: https://share.getcloudapp.com/llu66Rb0

@OlegMakarenko each address in address book should be unique. Currently using editing I'm able to have two contacts with same.
Video: https://share.getcloudapp.com/E0uoQNjY

Fixed in https://github.com/symbol/desktop-wallet/pull/1847

Released in 1.0.11


Test | Addressing Net5 runtime issues

While trying to test the driver against Net5, runtime caught some unobserved issues/warnings

Classes implementing IDisposable should dispose all related fields.
Re-Throwing caught exception from catch block will change the stack, hence should not be done.
Calling overridable methods from constructions are prohibited.
Raising exception from unexpected places such as dispose is not recommended.
BinaryFormatter is not safe and should not be used in all versions of .NETFramework and   netcoreapp 2.1 and upper versions.
Warning CA1416: Platform compatibility this issue came up for tests running on Windows for CspParameters class. In net5.0 and later versions OperatindSystem.IsWindows
 is introduced to get the operating system but the API is not known in lower versions.

In some cases such as overridable methods usage I have moved the method inside a concrete  method and called it from there and that made the driver to compile and run.  I am eager to hear all comments about the changes to improve them and make them better.
Thanks
Update:
I noticed some improvement opportunities in our test lab:
SqlNotificationTest was using ManualResetEvent I have changed them to use ManualResetEventSlim. Reasoning to do so:

ManualResetEventSlim is less expensive than ManualResetEvent.
ManualResetEventSlim is fully managed version of its predecessor.

there are small differences such as kernel related behavior and blocking the thread which may have better effect on our test lab.

/azp run CI-Ub16-SQL17L-TR, CI-Win10-AzureSQLDB, CI-Win10-SQL17W, CI-Win10-SQL19W-Fx48-Core31, CI-Win10-SQL19W-ManagedSNI, CI-Win10-SQL19W-TR


Share to teams initial documentation

Not available in the TOC, creating dark release to be shared with select partners

OPS Build status updates of commit 0994de4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/share-to-teams.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 698b066:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/share-to-teams.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 31dfa8d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/share-to-teams.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 7eceb77:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/share-to-teams-popup.png
:white_check_mark:Succeeded

msteams-platform/share-to-teams.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Develop

Coverage increased (+0.3%) to 86.105% when pulling 5f69a7a3b97dab7b7e470892868a5cc672d4f1b1 on develop into 778a3362a9856ca3155ecaec4b985f4c5d6b905b on qa.

Coverage increased (+0.7%) to 86.482% when pulling 4f3f352d7046194415596021f7318e9c2d4671a9 on develop into 778a3362a9856ca3155ecaec4b985f4c5d6b905b on qa.

Coverage increased (+0.7%) to 86.482% when pulling a5efca095cad9138b4941574605218f685cb2013 on develop into 36072da71a6feeb00af470a3666b3908c9980c57 on qa.

Coverage increased (+0.7%) to 86.482% when pulling a5efca095cad9138b4941574605218f685cb2013 on develop into 36072da71a6feeb00af470a3666b3908c9980c57 on qa.

Coverage increased (+0.7%) to 86.482% when pulling a5efca095cad9138b4941574605218f685cb2013 on develop into 36072da71a6feeb00af470a3666b3908c9980c57 on qa.

Coverage increased (+2.9%) to 88.718% when pulling dded8b5ee5413d487f202654b5b04804345d20df on develop into 36072da71a6feeb00af470a3666b3908c9980c57 on qa.

Coverage increased (+3.2%) to 89.018% when pulling 44d9a1b89fae8432cd3adc901d7d10aaacc438eb on develop into 36072da71a6feeb00af470a3666b3908c9980c57 on qa.


TRAMP errors when opening python files

error in process filter: tramp-handle-insert-file-contents: File ‘/ssh:vm:/tmp/py2RGjwU’ not found on remote host
error in process filter: File ‘/ssh:vm:/tmp/py2RGjwU’ not found on remote host

This may be caused by some weird interaction with vc???
Emacs freezes when this error is shown. By killing Emacs with USR2, I got a line in vc which I then removed and the problem went away?

Incredibly, this seems to have fixed the issue.

-_-


Parameter MessagingExtensionQuery always returns just first CommandId from manifest

I'm using Microsoft Bot Framework V4 SDK to create a messaging extension bot.
I created two commands (searchQuery, processQuery). I would like to call up a configuration page for each command. The problem is that the MessagingExtensionQuery parameter in the OnTeamsMessagingExtensionConfigurationQuerySettingUrlAsync event always returns just the first command Id, I entered in the manifest.
I would have expected that when I click on the 3 dots to open the configuration page, the respective ID of the command would be passed to the event.

Hope you can help.
regads

I am taking a look at this.

@dmvtech any update on this?

Hi @DridiFathi
Apologies for the delay. We are still investigating.

Hi @harald-thoenig
To clarify the behavior a bit. When you say:

when I click on the 3 dots to open the configuration page

Do you mean; when you click on the three dots? Or when you select settings:

If you could please share more information and specifics on how exactly you set up the configuration/configuration page.

@ramfattah

Hi @ramfattah
If I select settings the event OnTeamsMessagingExtensionConfigurationQuerySettingUrlAsync will be triggered. In this event I get the command Id. But this command Id is always the first command Id from manifest. But I like to know on which command the user has selected the settings, then I could provide users different configuration pages per command Id.
I did the implementation of the configuration page exactly as it is described in the git sample "https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/50.teams-messaging-extensions-search/Bots)".

Thanks @harald-thoenig,
I was able to reproduce this issue using C# bot sample 52.teams-messaging-extensions-search-auth-config.
Sharing the steps to reproduce:

Clone sample 52.teams-messaging-extensions-search-auth-config into your local environment.
In file manifest.json, replace the commands section with the following:
 "name": {
   "short": "Messaging Extension Auth",
   "full": "ME Auth for Search, Action and link unfurling"
 },
 "description": {
   "short": "ME Authentication for Search, Action and Link unfurling",
   "full": "ME Authentication sample code for all authentication merged"
 },
 "accentColor": "#FFFFFF",
 "composeExtensions": [
   {
     "botId": "<<YOUR-MICROSOFT-APP-ID>>",
     "canUpdateConfiguration": true,
+      "commands": [
+        {
+          "id": "searchQuery",
+         "type": "query",
+          "title": "Search",
+          "description": "Perform a search",
+          "initialRun": false,
+          "fetchTask": false,
+          "context": [
+            "commandBox",
+            "compose",
+            "message"
+          ],
+          "parameters": [
+            {
+              "name": "searchQuery",
+              "title": "Search",
+              "description": "Your search query",
+              "inputType": "text"
+            }
+          ]
+        },
+        {
+          "id": "processQuery",
+          "type": "query",
+          "title": "Tasks",
+          "description": "Task lists",
+          "initialRun": true,
+          "fetchTask": false,
+          "context": [
+           "commandBox",
+            "compose",
+            "message"
+          ],
+          "parameters": [
+            {
+              "name": "processQuery",
+              "title": "Process",
+              "description": "ProcessList",
+              "inputType": "text"
+            }
+          ]
+        },
+        {
+          "id": "SignOutCommand",
+          "type": "action",
+          "title": "Sign Out",
+          "description": "Sign out from authenticated services.",
+          "initialRun": false,
+          "fetchTask": true,
+          "context": [
+            "commandBox",
+            "compose"
+          ],
+          "parameters": [
+            {
+              "name": "param",
+              "title": "param",
+              "description": ""
+            }
+          ]
+        }
+      ],
     "messageHandlers": [
       {
         "type": "link",
         "value": {
           "domains": [
             "*.botframework.com"
           ]
         }
       }
     ]
   }
 ],
 "permissions": [
   "identity"
 ],
 "validDomains": [
   "*.githubusercontent.com",
   "*.ngrok.io",
   "*.botframework.com"
 ]
}

Notice we have 3 command ids: searchQuery, processQuery, and SignOutCommand

Install and Run the bot in Teams channel. From my end, I set up ngrok tunneling solution.
In the bot sample code, put break point on method OnTeamsMessagingExtensionConfigurationQuerySettingUrlAsync
In Teams, at the top nav search bar, @ mention the Messaging Extension Auth app.
Select Tasks, and at the bottom right of the drop down, click the three dots ...

Notice the MessagingExtensionQuery query parameter in method OnTeamsMessagingExtensionConfigurationQuerySettingUrlAsync always returns the first command Id searchQuery instead of processQuery.

Hey @JuanAr, we are reaching out to see if there is status update on this.
Thanks.

Hey @JuanAr, we are reaching out to see if there is status update on this.
Thanks.

Hi @ramfattah, this issue is on our backlog. We'll be tackling it next week.
Thanks.

We reproduced the issue and found that it's the MSTeams client the one sending the wrong commandId in the property value of the activity (documentation here).
We consider this issue can be closed as there's nothing to fix on the SDK.

Thank you @ceciliaavila.
Closing as this issue is not related to Bot Framework SDK.

Reopening, will notify Teams during sync meetings.


Launch Pashto books in prod

Must finish QA bug first. QA before launch. Sorry for brevity!

Putting on hold and moving back to the Backlog. We're going to have to try to come up with a way to make these books mobile-friendly because we learned from #974 that all we get is the dimensions of the image and nothing else!


Fix If-Unmodified-Since - Incorrect condition

Adds tests to https://github.com/aspnet/StaticFiles/pull/144
@Tratcher

:shipit:


Where clause seemingly ignored on relation

Laravel Version: 5.1.16 / 5.3.30
PHP Version: 7
Database Driver & Version: 10.1.19-MariaDB Homebrew, MySQL

Description:
I added some where clauses to my User model relationship:
$this->hasMany(Credit::class)->where("expires_at", "=", null)->orWhere("expires_at", ">=", $date)

I noticed that this started brining back credit records that didn't belong to the user, a credit has a status, if I then added an extra where clause on to find credits of a specific status:
$credits = $user->credits()->where("status", "=", "available")

$credits would have instances of the Credit model where the status was different to that of the where clause
Steps To Reproduce:
model Credit belongs to User
model User has many credits
And the above where/orWhere clause to the model, subsequent where clauses have no effect.
Please note, changing the model relationship where to be:
return $this->hasMany('Quuu\Credit')
    ->where(function($query) {
      $query->where("expires_at", "=", null)
      ->orWhere("expires_at", ">=", \Carbon\Carbon::today());
    });

seems to fix the issue, but it seems like an easy trap to fall in and it's super confusing as to why the secondary where clause of status took no effect, is this an issue or my understanding of the way laravel retrieves records?

Yes you need to use closure to add extra OR conditions or you'll end up having records wher eonly the conditions after OR applied.

@themsaid thanks for that, I noticed and fixed the issue... shouldn't other where conditions added after the query had been built restrict it further though?


cpu - cpu version of gpu_specter should be fully correct

This should likely be addressed after Issues #4 and #5 have been addressed.
Before transitioning the code from cpu to gpu, it should have uniform array and patch sizes and should be fully correct.

@sbailey : I missed this in the PR review / code walkthrough of your recent refactor but it looks like there's a typo here (results should be result):
https://github.com/sbailey/gpu_specter/blob/7f60a4860e5e475668758fe599ac24ea86ce526e/bin/spex#L246-L249
Hopefully saves you some head scratching...


[BUG] disableCorrelationHeaders does not work as expected

Description/Screenshot
Documentation for disableCorrelationHeaders attribute says

If false, the SDK adds two headers ('Request-Id' and 'Request-Context') to all dependency requests to correlate them with corresponding requests on the server side. Default is false.

But the mentioned header Request-Id is sent only if attribute enableCorsCorrelation is set to true and Request-Context is sent only if  enableCorsCorrelation is set to true and appId is not undefined.
Steps to Reproduce

OS/Browser: win 11, edge
SDK Version [e.g. 22]: "@microsoft/applicationinsights-clickanalytics-js": "^3.2.1"
How you initialized the SDK: npm

Expected behavior
I expect that Request-Id and Request-Context will be sent when disableCorrelationHeaders is false.

The current logic (by design) for the two configs is:

if disableCorrelationHeaders is set to true, regardless of other settings, correlation headers will not be added.
if disableCorrelationHeaders is set to false and enableCorsCorrelation is set to false, correlation headers will not be added.
if disableCorrelationHeaders is set to false and enableCorsCorrelation is set to true, correlation headers will be added based on correlationHeaderExcludePatterns, correlationHeaderDomains and correlationHeaderExcludedDomains

thank you for clarification


bug(drag-and-drop): When using *DragPreview directive, the dragging position is wrong

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
When I use the drag preview directive *cdkDragPreview for my horizontal list, the dragged item position is wrong
Possibly related #16171
Reproduction
StackBlitz link
Expected Behavior
*cdkDragPreview dragging position should be the same as the dragging position is without using cdkDragPreview
Actual Behavior
The dragging position always started from the pointer edge, giving a undesired behavior
Environment

Angular: v16
CDK/Material: v16
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): All

In what sense is the position wrong? The Stackblitz is the same as #27750 which seems like a different issue.

It sounds like this is more of a feature request, updated the description to reflect that


feat: (opt-in): terminate handling of work when the request has already timed out

Overhead-free (or at least very cheap).
The “timeout” gunicorn config means drastically different things for
sync and non-sync workers:
Workers silent for more than this many seconds are killed and restarted.
Value is a positive number or 0. Setting it to 0 has the effect of
infinite timeouts by disabling timeouts for all workers entirely.
Generally, the default of thirty seconds should suffice. Only set this
noticeably higher if you’re sure of the repercussions for sync workers.
For the non sync workers it just means that the worker process is still
communicating and is not tied to the length of time required to handle a
single request.
So.  For cases where threads = 1 (user set or our defaults), we’ll use
the sync worker and let the regular timeout functionality do its thing.
For cases where threads > 1, we’re using the gthread worker, and timeout
means something completely different and not really user-observable.  So
we’ll leave the communication timeout (default gunicorn “timeout”) at 30
seconds, but create our own gthread-derived worker class to use instead,
which terminates request handling (with no mind to gunicorn’s “graceful
shutdown” config), to emulate GCF 1st gen.
The arbiter spawns these workers, so we have to maintain some sort of
global timeout state for us to read in our custom gthread worker.
In the future, we should consider letting the user adjust the graceful
shutdown seconds.  But the default of 30 seems like it’s worked fine
historically, so it’s hard to argue for changing it.  IIUC, this means
that on gen 2, there’s a small behavior difference for the sync workers
compared to gen 1, in that gen 2 sync worker workloads will get an extra
30 seconds of timeout to gracefully shut down.  I don’t think monkeying
with this config and opting-in to sync workers is very common, though,
so let’s not worry about it here; everyone should be on the gthread path
outlined above.

Looks great!


Have a warning while starting rtsp stream to enable it first

Is your feature request related to a problem? Please describe.
As described inside https://github.com/fuatakgun/eufy_security/issues/76#issuecomment-968369109 there are new ways how to start streaming with RTSP disabled (Previously it was auto-enabled/disabled)
Describe the solution you'd like
Print warning when using the old way, with explanation what to do. Update documentation.
Describe alternatives you've considered
Ask implementer or revers engineer it. Here I mean to discover how behavior changed
Additional context
It's related to bug: https://github.com/fuatakgun/eufy_security/issues/76#issuecomment-968369109

please get latest version, this should work now


rustRegistry: 2017-06-25 -> 2017-06-27

Motivation for this change
Index update.
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Thanks!


Extend Device Context with CPU info

Description
https://github.com/getsentry/team-mobile/issues/77
We have to add those properties on the Dart data classes

Already done by https://github.com/getsentry/sentry-dart/pull/838
iOS and Android should just start adding it


About slow loading of vscode's intellisense

TS Template added by @mjbvz
TypeScript Version: 4.2.4
Search Terms

completionInfo
updateGraphWorker

Issue Type: Performance Issue
for the details, Please view the video: https://ftp.bmp.ovh/imgs/2021/05/fb81bd04e2cc2043.gif
my device is a Raspberry Pi 4B
and the demo code: https://github.com/kljzndx/Test-Demos/tree/react-bootstrap
VS Code version: Code 1.56.2 (054a9295330880ed74ceaedda236253b4f39a335, 2021-05-12T16:44:43.567Z)
OS version: Linux arm64 5.10.17-v8+

System Info

Item
Value

CPUs
unknown (4 x 1500)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onrasterization: disabled_softwareskia_renderer: enabled_onvideo_decode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
4, 2, 1

Memory (System)
3.71GB (0.72GB free)

Process Argv
--no-sandbox --unity-launch --crash-reporter-id ce9b433d-3b3a-435c-bd09-1d48bd532e79

Screen Reader
no

VM
0%

DESKTOP_SESSION
LXDE-pi

XDG_CURRENT_DESKTOP
LXDE

XDG_SESSION_DESKTOP
lightdm-xsession

XDG_SESSION_TYPE
x11

Process Info
CPU %	Mem MB	   PID	Process
    1	   144	 27403	code main
    0	    42	 27405	   zygote
    1	   125	 27440	     gpu-process
    0	    42	 27406	   zygote
    2	    83	 27962	     window (Issue Reporter)
    0	    68	 27444	   utility
    0	   121	 27523	   shared-process
    0	    68	 27560	     ptyHost
    0	     0	 28037	     /bin/sh -c /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0	     0	 28038	       /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0	   266	 27781	   window (App.tsx - Test-Demos - Visual Studio Code)
    0	   121	 27805	     extensionHost
    0	   140	 27890	       electron_node tsserver.js
    0	   209	 27893	       electron_node tsserver.js
    1	    95	 27916	         electron_node typingsInstaller.js typesMap.js
    0	    68	 28005	       /usr/share/code/code /usr/share/code/resources/app/extensions/json-language-features/server/dist/node/jsonServerMain --node-ipc --clientProcessId=27805
    0	    68	 27806	     watcherService
    0	    68	 27852	     searchService

Workspace Info
|  Window (App.tsx - Test-Demos - Visual Studio Code)
|    Folder (Test-Demos): 14 files
|      File types: json(2) tsx(2) svg(2) gitignore(1) md(1) html(1) ts(1)
|                  lock(1)
|      Conf files: package.json(1) tsconfig.json(1);

Extensions: none
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
vspre833:30267464
pythonptprofiler:30281270
vshan820:30294714
pythondataviewer:30285071
vscus158:30286553
vscgsv2:30301612
vscorehovct:30302760
bridgeflight:30302069
vscod805:30301674

Thanks @kljzndx
@sheetalkamat Near the end of the logs, I see a long running updateGraphWorker request that seems to block completions:
    {"seq":242,"type":"request","command":"completionInfo","arguments":{"file":"/home/pi/web/react/Test-Demos/src/App.tsx","line":8,"offset":19,"includeExternalModuleExports":true,"includeInsertTextCompletions":true}}
Info 1026 [08:47:55.453] Starting updateGraphWorker: Project: /home/pi/web/react/Test-Demos/tsconfig.json
Info 1027 [08:47:55.514] Finishing updateGraphWorker: Project: /home/pi/web/react/Test-Demos/tsconfig.json Version: 45 structureChanged: false Elapsed: 61.04459900036454ms
Info 1028 [08:47:55.515] Different program with same set of files:: structureIsReused:: 2
Info 1029 [08:47:55.516] getCompletionData: Get current token: 0.07451799884438515
Info 1030 [08:47:55.516] getCompletionData: Is inside comment: 0.04390699975192547
Info 1031 [08:47:55.517] getCompletionData: Get previous token 1: 0.3083330001682043
Info 1032 [08:47:55.517] getCompletionData: Get previous token 2: 0.2187219988554716
Info 1033 [08:47:55.518] getCompletionsAtPosition: isCompletionListBlocker: 0.04529600031673908
Info 1034 [08:48:01.752] getCompletionData: Semantic work: 6234.125678000972
Info 1035 [08:48:01.799] getCompletionsAtPosition: getCompletionEntriesFromSymbols: 44.96493599936366
Perf 1036 [08:48:01.802] 242::completionInfo: elapsed time (in milliseconds) 6349.3794
Info 1037 [08:48:01.803] response:
    {"seq":0,"type":"response","command":"completionInfo","request_seq":242,"success":true,"performanceData":

I dont think this is updateGraph sionce that seems to finish in 61ms
Its the
Info 1034 [08:48:01.752] getCompletionData: Semantic work: 6234.125678000972

This is the expected performance given the hardware.

我不认为这是硬件性能的问题，因为好像只有这个叫做 “react-bootstrap” 的库会使 ts-server 这么慢，别的库基本上都是立刻响应的
--------------Translate by DeepL-------------
I don't think it's a hardware performance problem, because it seems that only this library called "react-bootstrap" will make ts-server so slow, other libraries are basically immediately responsive

I'm sure this is fast enough hardware to run faster projects quickly, but slower projects exist and React is one of them


Validate Key Usage on server certificates

We added validation for the Extended Key Usage extension on server certificates, however there is another extension, Key Usage, that might also indicate restrictions on certificate usage. We should investigate which flags should be required, and how Kestrel should accept handle server certificates that don't have these flags. e.g. should we restrict, warn, or allow?

No plans to implement this in 2.x


Fix jacfwd

I just found that jacfwd breaks if there are no static outputs from the Jacobian. E.g. it fails on the simple neural network on the home page. This fixes that (without the change, the new tests would fail, they would encounter an error because eqx.combine is call on a pytree and a None object)

Actually, I think it's more complicated than this. (Possibly even undefined?) The jacobian should be something that is shaped as output x input, but here static_out is something that is shaped according to (the static part of) just output.
I think we need to define these operations in a different way altogether.

Hmmm, maybe a silly question but what's the actual need for static output? The input is already parsed to be dynamic and the output of the function has to be array types (already if you output a string or something it will fail, since jax.jacfwd doesn't know how to interact with it). Like suppose a simple example where one would probably expect jax and equinox to be the same (i.e. all jax types, no filtering actually needed)
def cond_fun(val):
    x = val
    return jnp.mean(x) <= 5

def body_fun(val):
    x = val
    return x**2

def f(x):
    return jax.lax.while_loop(cond_fun, body_fun, x), 1.0

x = jnp.array([1.0, 2.0])
print("eqx", eqx.filter_jacfwd(f)(x))
print("jax", jax.jacfwd(f)(x))

will yield
eqx (Array([[ 4.,  0.],
       [ 0., 32.]], dtype=float64), 1.0)
jax (Array([[ 4.,  0.],
       [ 0., 32.]], dtype=float64), Array([0., 0.], dtype=float64, weak_type=True))

(this is independent of my PR, since this PR only effects if _static_out is None, but _static_out is not None here).
If we just get ride of static out and return out directly (e.g. return _dynamic_out, (_static_out, _aux) -> return _out, (None, _aux)) then we see
eqx (Array([[ 4.,  0.],
       [ 0., 32.]], dtype=float64), Array([0., 0.], dtype=float64, weak_type=True))
jax (Array([[ 4.,  0.],
       [ 0., 32.]], dtype=float64), Array([0., 0.], dtype=float64, weak_type=True))

Yup. This is what I mean about probably needing to change the definition of filter_jac{fwd,rev}.
The resulting Jacobian is a "nested PyTree", whose structure/array-shapes are formed by composing the PyTrees of the outputs and inputs. But indeed if we have a string as both input and output, then there is no obvious way to compose these.
I suspect we can define this either for the case when the inputs may have static elements, or for the case where the outputs have static elements, but not both.

Yes, that makes sense. Personally, I lean towards just not allowing/supporting outputs to have static elements (seems like if you needed static outputs then there is a way for the user to combine them at the end). Static inputs are ubiquitous and seem essential to support.

SGTM!

I removed the static filtering and added a warning about it in the docs

LGTM! Thank you for spotting this, and for the fix! :)


grafana failed to get metrics from prometheus on ocp 4.4

Somehow podMetadata info in Prometheus CR is not set on OCP 4.4. And it leads to services of both prometheus and alertmanager fail to find endpoints by their selectors.
Before looking into Prometheus Operator, it makes sense to use only necessary labels as service selectors

Somehow podMetadata info in Prometheus CR is not set on OCP 4.4. And it leads to services of both prometheus and alertmanager fail to find endpoints by their selectors.
Before looking into Prometheus Operator, it makes sense to use only necessary labels as service selectors


Add basic constants to Color class

Some useful predefined colors like Black, White and Transparent might be useful to add as constants to the Color class. Other constants such as the ones defined by QColor or XNA might also be useful but that might be too out of scope.

I do not know how to implement it but probably this helps:
http://www.adp-gmbh.ch/win/programming/graphic/color.html


Fix ADT filtering

Closes #378
This PR fixes the ADT filtering bug, with some aspects up for discussion during review. I took the approach outlined in the corresponding issue:

If both of the cleanTagCounts output columns discard and zero.ambient have NAs, totally bail on filtering (rather that just "skipping" filtering on cells with NA - I thought a uniform approach would be cleaner).

In this case, metadata(processed_sce)$adt_scpca_filter_method is given a value of No filter, as the kids say these days.
The colData column processed_sce$adt_scpca_filter is given a value of NULL.
log1p normalization will be performed here on all cells

Otherwise, first try to filter on discard. If this column has NA's, fall back to filtering on zero.ambient

sizeFactors are calculated here for normalization under this circumstance, as before

I also found another tab-related bug (!) wherein log1p normalization was not actually put back into the SCE object after calculation, so that's good! I moved this code back out of the if.

One note here: for the case of No filter, I could have just calculated log1p directly on the SCE object, rather than the "code detour" to ensure filtered out cells have NA normalized values. But I could add an if before entering the normalization to check if no filter was performed, and then just straight up do a logcounts(altExp(sce)) <- log1p(counts(altExp(sce)).

I then updated the QC report accordingly.

I added more logic for some of the output in cite.rmd; rather than only checking for has_processed, we need to also check that generally check that !is.null(processed_sce$adt_scpca_filter).
I also rearranged some text to better match the final context.

I'm attaching two versions of a rendered QC report on a library that first caught this error:

SCPCL000706_qc.html.txt is the QC report as usual run through the full workflow
qc_report-no-filtering.html.txt is a modified version of the above. To create this notebook, I manually modified the processed SCE so that processed_sce$adt_scpca_filter <- NULL and metadata(processed_sce)$adt_scpca_filter_method <- "No filter" and directly rendered the report (not via the workflow).

I know this may be a lot to digest here, so please let me know where I can clarify!! Tagging everyone for review since it would be good to have a couple eyes on this, I think.

I hadn't tested yet actually, just coming back to do that now! Will accept suggestions and then give it a full go to be extra sure!


Spelling mistake

"Enteprise" should be "Enterprise"

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

ID: 24796ccb-a3a7-c8c5-829d-ede6e06ff7c4
Version Independent ID: 1282c601-0457-f28a-7ad1-c373739d7004
Content: Mobile device management MDM for device updates - Windows Client Management
Content Source: windows/client-management/mdm/device-update-management.md
Product: w10
Technology: windows
GitHub Login: @ManikaDhiman
Microsoft Alias: dansimp

@tju-pwsh : Thank you for notifying the community about this typo. This one is solved as of the PR #5658 and its commit https://github.com/MicrosoftDocs/windows-itpro-docs/commit/9639b3dd972a795fb828eb96a25ef5c9c7cf0c10 . The change will appear on the docs.microsoft.com page after some days, when the next sync from Github to the public pages is done.


Added the ability to override the java version for Sponge

java -jar -Dsponge.override.java.version=1.8.0_40 -jar ...
Can now be used to override the java version in the version
check. This is done to allow users who have invalidly versioned
versions of Java to still run the server.
Fixes  #660

I personally think this should simply skip the check completely (at their own risk) instead of requiring to add a version that is checked instead.

My original thought was they could specify their actual current Java version (or our bare minimum requirement) and then if there's a change that requires a new Java version you have to change your startup script again, verifying that everything is still OK in the process.
---- On Thu, 21 Apr 2016 22:00:57 -0700<EMAIL_ADDRESS>wrote ----
I personally think this should simply skip the check completely (at their own risk) instead of requiring to add a version that is checked instead.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

Closing in favour of #684


Send resumed in ready payload instead of resume.

Changes
This changes the resume field to resumed to be inline with what Lavalink clients should expect, as per the implementation documentation at https://lavalink.dev/api/websocket.html#ready-op
Why
During my testing, my client was looking for a resumed field but was not seeing it, and throwing an error causing the websocket connection to be immediately terminated with no attempt at reconnecting. I don't believe this is the duty of clients to change as this server markets itself as being generally compatible with clients, thus the core implementation should at least match that.
Checkmarks

[x] The modified endpoints have been tested.
[x] Used the same indentation as the rest of the project.
[x] Still compatible with LavaLink clients.

Additional information
N/A.

Thanks for the PR.
Just one thing: Could you update the commit message based on our contributing repository?

Done.


Add Hugo - Best practices

Hi @budparr thank you for maintaining this awesome list.
I'm the maintainer of the Hugo - Best practices collection. This is a combination of front-end best practices and helpful snippets to get Hugo running fast and with good scores. Maybe this might be usefule for the awesome list.
Best regards
Sebastian

Thanks!


Uses simpler padding interface

This function works just fine for what we're trying to do here.

Going to leave this here in case we ever want to go this route.


any plan about converting coffee scripts to es6?

thank you!

The n1 team is working towards this goal.

@roughsoft We've been doing it over time—it's just tens of thousands of lines of code and lots of room for error, so it'll probably be a while. Going to close this issue for now because it isn't a bug or feature request!

thanks very much,i very like n1 and es6 !


Ipython notebook tutorial for irradiance is out of date?

Hi -
It looks like the Ipython notebook tutorial irradiance.pynb has code to compute the ineichen model as follows:
irrad_data = pvlib.clearsky.ineichen(times, tus.latitude, tus.longitude, tus.altitude)
irrad_data.plot()
Which gives an error:
Traceback (most recent call last):
File "compute_ghi.py", line 41, in
tus.longitude, tus.altitude)
File "//anaconda/lib/python2.7/site-packages/pvlib/clearsky.py", line 113, in ineichen
cos_zenith = np.maximum(tools.cosd(apparent_zenith), 0)
File "//anaconda/lib/python2.7/site-packages/pvlib/tools.py", line 26, in cosd
res = np.cos(np.radians(angle))
TypeError: ufunc 'radians' not supported for the input types, and the inputs could not be safely coerced to any supported types according to the casting rule ''safe''
It looks like the clearsky.ineichen takes solar zenith angle as the first argument? However, this code does reproduce what is seen in the middle figure of out[11] of irradiance.pynb for linke turbidity = 2.0, all other code being the same:
irrad_data = tus.get_clearsky(times, model='ineichen', linke_turbidity=2)

The API changed in version 0.4. I thought this tutorial worked with the new version of pvlib (it does have a note at the top saying that it should) but I guess I missed something or forgot to commit a change.
There's a very similar example in the documentation that does work...
http://pvlib-python.readthedocs.io/en/latest/clearsky.html#examples
Do you want to make a pull request with the change? You'll want to use the notebook's "Restart and run all" command until it works through the end.


CVE-2023-25330 (Critical) detected in mybatis-plus-<IP_ADDRESS>.jar

Discussed in https://github.com/baomidou/mybatis-plus/discussions/5408

Originally posted by lizhh123 June 15, 2023
hi there is an vulnerability(CVE-2023-25330) in mybatis-plus-<IP_ADDRESS>, do you have any plan to fixed it?
Details:
An enhanced toolkit of Mybatis to simplify development.
Library home page: https://github.com/baomidou/mybatis-plus
Path to vulnerable library: baomidou/mybatis-plus/<IP_ADDRESS>/mybatis-plus-<IP_ADDRESS>.jar
Dependency Hierarchy:
mybatis-plus-boot-starter-<IP_ADDRESS>.jar (Root Library)
    ❌ mybatis-plus-<IP_ADDRESS>.jar (Vulnerable Library)

Found in base branch: main
Vulnerability Details
A SQL injection vulnerability in Mybatis plus below <IP_ADDRESS> allows remote attackers to execute arbitrary SQL commands via the tenant ID valuer.
Publish Date: 2023-04-05
URL: CVE-2023-25330
CVSS 3 Score Details (9.8)
Base Score Metrics:
Exploitability Metrics:
    Attack Vector: Network
    Attack Complexity: Low
    Privileges Required: None
    User Interaction: None
    Scope: Unchanged
Impact Metrics:
    Confidentiality Impact: High
    Integrity Impact: High
    Availability Impact: High</div>

@yuxiaobin

no


BIGTOP-3217. Added smoke tests for Livy

Added smoke tests for Livy. Tested the test on my local env.
Related JIRA: BIGTOP-296: Add Apache Livy (incubating) to Bigtop stack
$ ../../gradlew livy:test -Psmoke.tests

> Task :bigtop-tests:smoke-tests:livy:test
Now testing...

BUILD SUCCESSFUL in 45s
6 actionable tasks: 6 executed

PR looks pretty good @akitanaka. Let me spend more time to test it. If no problem I'll commit.


Remove DeprecationWarning of np.bool

Summary
Details and comments

please, please, merge it, the code litters a lot now.


Support React 17 as a peer dependency

Hello !
I can't install mdxp in my app that uses React 17 (unless I install --force).
Would it be possible to add React 17 in the list of supported versions for React as a peer dependency ?
I know this isn't a common use case, but MDXP is the only react presentation library that I can use somewhat easily inside another app (and with MDX). And since React 17 has very few breaking changes, this shouldn't be too risky.

I cannot guarantee MDXP will work correctly with React 17, as I never tested this.
Thus not allowing React 17, which is a major release, (without --force), is exactly the behaviour I want.
If you are willing to try running MDXP with React 17, you should use the --force arguments, which is exactly what it is meant for.
I don't have a lot of time to work on MDXP right now, but once I do, I will probably go through the entire codebase and try to update each of the packages to their newest versions.


Changing tokensMaxItems results in incorrect display type on searchContainer

I change tokensMaxItems on the tokenize options based on a user option.  Unfortunately changing maxItems to > $('li.token', this.tokensContainer).length results in the search container being display:list-item.
This is because jQuery show on searchContainer guesses the correct display type and reverts to display:list-item instead of display:inline-block.
This can be resolved by replacing show/hide with a class to set display:none.

Old version
Fixed with new css, try the last one


Nq/chkt 1680 release flow improvements

This will need to be merged to master for further testing. The release process uses a manual dispatch workflow, and for that to appear in the "Actions" tab, the workflows must be on master.
I will create a new branch once this is merged to run some dry-run tests using the workflows.
Test this locally

ensure commitizen is installed on your system.
create some commits with [fix:|feat:|BREAKING CHANGE:] depending on the test you want to run.
run cz bump
check that PrimerSDK.podspec, .cz.toml and version.swift reflect the new version.
revert the bump commit
delete the new tag
repeat

Here is an example commit for a bump.


Make timeout configurable using flags

Right now the HTTP client timeout is hardcoded.
We should make it configurable using flags.

Whatever this is hardcoded to (5 seconds?), it's way too short - I can't complete the login process with the IdP, and oauth2c already fails with
  ERROR   401: access_denied


fix: ios config setup fixes

Story: https://app.shortcut.com/smileid/story/xxx
Summary
Fix config setup issues

can we merge this now, please?


Add logging for debugging

Hi!
I just want to check before creating a PR.
I would like to add some more logging to make debugging easier, for example in our test/Q&A-environments there is special requirements for the HttpClient to be able to render the pages since they are protected. At the moment it will only be a empty string but it's hard to know why.
I'm thinking that we can add something like this:

Making sure that we use _logger.IsEnabled() to avoid boxing when the log-level is not enabled.
I'm wondering:
1. Is this a good idea?
I think so =D
2. What log level(s) should we use?
I think that we should use "debug" to indicate things that are truly debug. Like which URL we're trying to fetch etc. But maybe use information when the page returns something other than 200?
Let me know and I'll create a PR.

Didn't even know that IsEnabled function, but after reading about it shortly, it sounds like a good idea, especially if we end up adding lots of debug messages :)
I think messages like these should be debug, also the information you have further down.

Hi!
I've read about it and it saves some of the boxing when the parameters are boxed so I guess it avoids som allocations id the call is not needed. I've noticed that they use it in Core in some placed.
I'll create a PR an keep it all on Debug-level - I agree it's sometimes annoying to get the log filled with random "stuff"
=D


Fix #1218

Don't check for len of NoneType
Cases where _analyst_trend_details is an empty dataframe are handled  in the try - except below.

You need to change target to dev. See #1084


added troubleshooting section to the readme file

Description
This PR does the following:

Adds a troubleshooting section to the README file to assist users with common issues encountered during installation and server setup.
Provides FAQs to address frequent questions regarding the local database and support contact.

Related Issues

Fixes #576

Changes
List the detailed changes made in this PR:

Added a new troubleshooting section covering:

Common installation issues
Problems with starting the server
Issues related to dependencies
Frequently asked questions (FAQs)

Testing Instructions
Detailed instructions on how to test the changes:

Pull this branch.
Check out the README file to review the newly added troubleshooting section.
Ensure that the troubleshooting instructions accurately reflect common issues and provide clear resolutions.

Screenshots (if applicable)

not applicable.

Additional Context

This PR is based on the feedback received from users facing installation issues. The added troubleshooting section aims to streamline the onboarding process and reduce confusion for new users.

Checklist
Make sure to check off all the items before submitting:

[x] I have performed a self-review of my code.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[x] I am working on this issue under GSSOC.

Description
This PR does the following:

Adds a troubleshooting section to the README file to assist users with common issues encountered during installation and server setup.
Provides FAQs to address frequent questions regarding the local database and support contact.

Related Issues

Fixes [Documentation Update]: Add a Troubleshooting Section to README #576

Changes
List the detailed changes made in this PR:

Added a new troubleshooting section covering:

Common installation issues
Problems with starting the server
Issues related to dependencies
Frequently asked questions (FAQs)

Testing Instructions
Detailed instructions on how to test the changes:

Pull this branch.
Check out the README file to review the newly added troubleshooting section.
Ensure that the troubleshooting instructions accurately reflect common issues and provide clear resolutions.

Screenshots (if applicable)

not applicable.

Additional Context

This PR is based on the feedback received from users facing installation issues. The added troubleshooting section aims to streamline the onboarding process and reduce confusion for new users.

Checklist
Make sure to check off all the items before submitting:

[x]  I have performed a self-review of my code.
[x]  I have commented on my code, particularly in hard-to-understand aras.
[x]  My changes generate no new warnings.
[x]  I am working on this issue under GSSOC.

Kindly add some screenshot or screen recording of the features you have added. @vaishnavipal1869

@vaishnavipal1869 Add a screenshot of the troubleshooting section you have added in the markdown file.

@vaishnavipal1869 Add a screenshot of the troubleshooting section you have added in the markdown file.

hello @Suman373 , Since my changes were purely related to documentation, I believe a screenshot may not be necessary in this case. However, if a screenshot is still required, I can provide one of the README file showing the updates. Please let me know how you'd prefer to proceed.

@vaishnavipal1869 Add a screenshot of the troubleshooting section you have added in the markdown file.

hello @Suman373 , Since my changes were purely related to documentation, I believe a screenshot may not be necessary in this case. However, if a screenshot is still required, I can provide one of the README file showing the updates. Please let me know how you'd prefer to proceed.

Although you have made documentation changes, a screenshot for the updated markdown file especially your changes is necessary. I have checked it so you don't have to update the PR but make sure to add it from next time onwards. Anyway, nice work ! We look forward to more contributions from your side 👍

@Trisha-tech you may verify and merge it

@vaishnavipal1869 Add a screenshot of the troubleshooting section you have added in the markdown file.

hello @Suman373 , Since my changes were purely related to documentation, I believe a screenshot may not be necessary in this case. However, if a screenshot is still required, I can provide one of the README file showing the updates. Please let me know how you'd prefer to proceed.

Although you have made documentation changes, a screenshot for the updated markdown file especially your changes is necessary. I have checked it so you don't have to update the PR but make sure to add it from next time onwards. Anyway, nice work ! We look forward to more contributions from your side 👍

Apologies for not including the screenshots earlier. If you'd like, I can add them right away—just let me know how you'd like me to proceed. I appreciate the feedback and will make sure to include them in future updates

@vaishnavipal1869 Add a screenshot of the troubleshooting section you have added in the markdown file.

hello @Suman373 , Since my changes were purely related to documentation, I believe a screenshot may not be necessary in this case. However, if a screenshot is still required, I can provide one of the README file showing the updates. Please let me know how you'd prefer to proceed.

Although you have made documentation changes, a screenshot for the updated markdown file especially your changes is necessary. I have checked it so you don't have to update the PR but make sure to add it from next time onwards. Anyway, nice work ! We look forward to more contributions from your side 👍

Apologies for not including the screenshots earlier. If you'd like, I can add them right away—just let me know how you'd like me to proceed. I appreciate the feedback and will make sure to include them in future updates

Its okay ! 😊


issue with tableView

First of all I want to congratulate you on your effort. It still has a small bug though. The first section header of a section is being shown but not at the top. In attachment you can see the error. I used the default UITableViewController.
sample1 kopie.pdf

Thanks for reporting issue! e I'll work to resolve this issue. Please wait for a little while. :cry:

@grandM
Finally, I found a bug :smile:
If tableview has sectionInset, first section header got out of top position.
(or If set Adjust Scroll View Inset in storyboard.
I'll work to resolve this issue. Please wait for a little while!!


JsonData Updates: Add WriteTo(), ==operators, and PR FB

This is a follow-up to https://github.com/Azure/azure-sdk-for-net/pull/32613 that addresses:

[x] Support for writing to a stream: https://github.com/Azure/azure-sdk-for-net/pull/32613#discussion_r1038652662
[x] Adding equality operators to match cast operators: https://github.com/Azure/azure-sdk-for-net/pull/32613#discussion_r1047430154
[x] Misc test clean-up and other missed PR feedback.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Core.Experimental


Why do attachments from the user get rehosted on the server?

When sending an attachment from the modmail to the user, it gets relayed as an attachment, however when going from the user to the modmail, it gets rehosted on the server and linked to. There's an issue with my server where the attachments aren't accessible, probably a firewall issue, but doesn't it just get relayed it as an attachment? I assume you have a reason for this.

Nevermind, just found this comment in the code.

Get a local URL for all attachments so we don't rely on discord's servers (which delete attachments when the channel/DM thread is deleted)

I got the firewall fixed, but it doesn't embed the image in the message. Is this the normal behavior?

I figured out that the message was being sent before the attachment was ready to be served. Adding a 100ms delay to all messages fixes it and properly embeds the preview. However, it'd be better to only delay the ones with attachments. Where would be the best place to insert a setTimeout?

Check this commit, it works but is not very clean. Is there a better way to do it.

Since the attachment saving functions return a promise, one possible way would be to store the promise for each attachment in a Map of attachment id => promise, and then have a function attachmentReady(attachmentId) which returns that promise. This should probably be done in attachments.js. I'll add this after work today!

This should be solved in the latest version. Can you give it a try?

Closing this as the issue should have been fixed in an earlier update.


Change references to numba.pydata.org to https

Changing links from
http://numba.pydata.org/...
to
https://numba.pydata.org/...

Thanks for the PR! In my opinion this is a good thing. The addition of s has caused one flake8 error due to an over-long line - if you could resolve it, I can queue the PR up for review.


[HOLD for payment 2023-07-14] Web -  First cell of magic input field is not focused on clicking 'Didn't receive a magic code' link

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:
Action Performed:

Navigate to staging sign-in page
Enter email > click on continue
Wait for the 30 second time out to finish
Enter wrong magic code
Click on 'Didn't receive a magic code' link

Expected Result:
The first cell of the magic code input field should be focused
Actual Result:
The first cell of the magic code input field is not focused
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.36-4
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/e9bb9e61-b1fe-4462-a8ad-247c4cb85ab2
https://github.com/Expensify/App/assets/93399543/1689d50f-ffb9-443d-8e61-bebfc51e6609
Expensify/Expensify Issue URL:
Issue reported by: @Natnael-guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1688554945270799
View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

Looking to see if this is related to https://github.com/Expensify/App/pull/21724

After a failed validation, we decided to blur the input

In this case, there was no failed validation. The user just requested for a new code.

Because if you type one single number it'll auto-submit because you have 6 digits in the input

Oh, interesting. Why does it auto-submit when only a single digit has been entered?

Get an error by submitting wrong code

Even if you don't submit a code at all and then click resend code, the input is blurred.

@HezekielT All good, please create the PR. Thanks! The fix looks you outlined here looks like it will fix this!

Cp'd! Removing the blocker label.

We have already validated the AdHoc build, but here are some screenshots from the staging build:

We have already validated the AdHoc build, but here are some screenshots from the staging build:

This was a regression from https://github.com/Expensify/App/pull/21724
No payments required here. I think we are good to close this out.

Hello @MariaHCD, I have reported this issue.

@zanyrenney this deploy blocker was a regression and was already fixed here. We just need to pay out the reporting bonus to @Natnael-Guchima.

No problem. Thanks @MariaHCD

Let's update the existing regression test here. Specifically, I've just added steps 12 & 13
Online

1. Navigate to https://staging.new.expensify.com/
2. In the email field, enter a gmail email address for a new account
3. Press continue
4. Verify there's a welcome message - "It's always great to see a new face..."
5. Verify there’s a message saying that a Magic Code has been sent to the email address
6. Verify there’s a button to resend the Magic Code
7. Navigate to the email inbox of the account and open the validation email
8. Copy the code
9. Enter a incorrect the code in the magic code field
10. Verify there's a user friendly message that the code is incorrect or to request a new code
11. Verify the field turns red and the user is unable to proceed
12. Wait for `Request magic code in xx:xx` timer to finish and click on `Didn't receive magic code?` option.
13. Verify that the error is cleared, the field is no longer red and the first input of the magic code input is focused

Nice catch, @HezekielT! Updated.

Added the issue for the regression test.

https://github.com/Expensify/App/issues/22258#issuecomment-1623102933 as per this comment, creating an upwork job specifically for reporting bonus.

Invited you: https://www.upwork.com/jobs/~011861274c564ee819 @Natnael-Guchima

Invited you: https://www.upwork.com/jobs/~011861274c564ee819 @Natnael-Guchima

I have applied to the job. Thanks @zereraz

That is all paid!


Add PEM encoded to README

Fixes #6

Thank you for this suggestion.
My knowledge is a bit short on that, but when looking at the top 5 results of "how to create ssh key" in Google none of them mention that encoding .
If that's the default encoding when your run ssh-keygen command to create your keys, I think it might confuse people.

Okay-okay.
When I read "people" I run away as I'm an expert.


Unable to find a shell with Terminator

I'm running Terminator 1.91 and running in to the issue using both Firefox & Chrome. When starting a session on EVE-NG it just opens a Terminator screen showing Unable to find a shell
Please let me know if any additional information/logging should be provided

Do you use Debian-based distro? Do you set Terminator as default for your session or edit eve-ng-integration/eve-ng-integration.desktop file?
Is this x-terminal-emulator -e telnet route-server.he.net command opens Terminator with telnet session?

Yes I'm running Ubuntu 18.04. Terminator is my default terminal.
The command opens Terminator and connects to the Telnet host without anny issues.

Terminator has weird behavior when it is launched as x-terminal-emulator:
-e, --command=COMMAND
       Runs  the specified command instead of your default shell or profile specified com‐
       mand. Note: if Terminator is launched as x-terminal-emulator -e  behaves  like  -x,
       and the longform becomes --execute2=COMMAND

To override it run the following commands:
mkdir -p ~/.local/share/applications/
cp -f /usr/share/applications/eve-ng-integration.desktop ~/.local/share/applications/
sed -i 's/^Exec=/&env OVERRIDE_TERMINAL_CMD="terminator -e" /' ~/.local/share/applications/eve-ng-integration.desktop

Unfortunately this does not work, now no Terminator window is openend

Check ~/.local/share/applications/eve-ng-integration.desktop file, it should contains:
[Desktop Entry]
Name=EVE-NG Integration
Exec=env OVERRIDE_TERMINAL_CMD="terminator -e" eve-ng-integration %u
TryExec=eve-ng-integration
Type=Application
Categories=Network;
MimeType=x-scheme-handler/telnet;x-scheme-handler/capture;x-scheme-handler/docker;
X-KDE-Protocols=telnet,capture,docker
NoDisplay=true

Also, see and run commands from Click on a node does not open an app (opens another app) in all browsers

This worked, thank you for the help!


K2-24 tutorial does not converge

I did a fresh conda environment and installed exoplanet and dependencies. I ran the K2-24 tutorial in a downloaded notebook and I get the following from the sample
with model:

    trace = sampler.sample(draws=2000)

Sampling 4 chains: 100%|██████████| 8000/8000 [00:37<00:00, 215.91draws/s]
ERROR:pymc3:The chain contains only diverging samples. The model is probably misspecified.
WARNING:pymc3:The acceptance probability does not match the target. It is 0.0, but should be close to 0.9. Try to increase the number of tuning steps.
ERROR:pymc3:There were 1999 divergences after tuning. Increase `target_accept` or reparameterize.
WARNING:pymc3:The acceptance probability does not match the target. It is 9.77952587176284e-17, but should be close to 0.9. Try to increase the number of tuning steps.
ERROR:pymc3:There were 1907 divergences after tuning. Increase `target_accept` or reparameterize.
WARNING:pymc3:The acceptance probability does not match the target. It is 0.006233605808817455, but should be close to 0.9. Try to increase the number of tuning steps.
ERROR:pymc3:There were 1918 divergences after tuning. Increase `target_accept` or reparameterize.
WARNING:pymc3:The acceptance probability does not match the target. It is 6.736254608770937e-15, but should be close to 0.9. Try to increase the number of tuning steps.
ERROR:pymc3:The gelman-rubin statistic is larger than 1.4 for some parameters. The sampler did not converge.
ERROR:pymc3:The estimated number of effective samples is smaller than 200 for some parameters.

The summary output is similarly bad

  | mean | sd | mc_error | hpd_2.5 | hpd_97.5 | n_eff | Rhat
-- | -- | -- | -- | -- | -- | -- | --
42.363591 | 0.000301 | 0.000030 | 42.363218 | 42.364071 | NaN | 7.343693
20.885450 | 0.000205 | 0.000021 | 20.885138 | 20.885673 | 2.018893 | 12.642319
0.063015 | 0.000591 | 0.000059 | 0.062178 | 0.063959 | NaN | 6.166608
0.046068 | 0.000590 | 0.000059 | 0.045105 | 0.046691 | 2.028321 | 10.391917
29.863008 | 2.787906 | 0.278459 | 25.333686 | 33.197244 | 2.035109 | 8.949308
24.414847 | 2.274746 | 0.227115 | 22.034980 | 28.812748 | NaN | 3.937818
0.119697 | 0.069082 | 0.006903 | 0.004913 | 0.187045 | 2.018684 | 12.257648
0.228654 | 0.043500 | 0.004344 | 0.166656 | 0.279087 | NaN | 9.578997
0.575165 | 0.042205 | 0.004219 | 0.522428 | 0.645138 | NaN | 7.824198
0.607800 | 0.057467 | 0.005744 | 0.519003 | 0.679079 | 2.014646 | 13.941053

Just getting back to this and I'm now getting the same problem again. Very strange! It seems to have something to do with omega. It's true that there can be numerical issues with the Angle distribution in some edge cases, but that should be vanishingly unlikely and I'm having trouble diagnosing. I'll keep digging and let you know!

Ugh - I'm having issues with this again. Disregard for now.

After many months of work, I have now gotten to the bottom of this. It was a lot of different factors contributing, but the main thing was instability of the function that computes the times of the contact points for the transit. It's not perfect now, but at least it knows when it's wrong now. Here's the most up to date tutorial (you'll see that everything looks good): https://exoplanet.dfm.io/en/latest/tutorials/together/
And I'm about to release v0.1.6 that fixes all this. Let me know if you run into anything else!

Great! Thanks Dan. I also notice a big speedup for the planet I'm working with.

Strangely enough, I also just ran into this same issue (with 1/4 chains getting stuck, though for a 28 parameter fit to a triple star, not a transiting exoplanet system). Turns out I am on theano v1.0.4 as well, though I arrived here by default after a fresh conda install a few days ago. Will try an updated theano version.

This definitely isn't the same problem and probably isn't related to the Theano version. It probably isn't even an exoplanet issue (it's normally something to do with modeling choices), but open a new issue if you can't get it sorted!

Thanks for the quick reply! I ran the chains again (exact same model, tuning params, and starting points) and nothing stuck this time. It seems to be somewhat of a transient behavior.
This did only start happening once I complexified my model with more parameters, so you're probably right that it's something to do with modeling choices.


preact-compat React.Children.toArray falsey value handling incompatible with react

The component <Demo title="Hello, World!" > 		<div/> 		<div/> 		{null} 		{false} 		{undefined} </Demo> will have 5 children(counting all falsey values) in preact-compat while only 2 in react.
react
https://codepen.io/anon/pen/xLQWXG
preact-compat
https://codepen.io/anon/pen/wqQmqy

This is resolved in Preact X :tada: Make sure to alias preact/compat instead of preact-compat.


Filter out MACS results with zero peaks

I'm getting this error when I'm running ChIP-Seq Best Practice v1.0 with nextflow v 0.31.1, on Uppmax/ bianca.
ERROR ~ Error executing process > 'chippeakanno (ALBB13_137_H3K27me3_peaks)'

Caused by:
  Process `chippeakanno (ALBB13_137_H3K27me3_peaks)` terminated with an error exit status (1)

Command executed:

  post_peak_calling_processing.r /usr/local/lib/R/library /home/jacke/bin/chipseq/blacklists/hg19-blacklist.bed genes.gtf <a lot of data sets here..>

Command exit status:
  1

Command output:
  (empty)

Command error:
      parLapplyLB, parRapply, parSapply, parSapplyLB

  The following objects are masked from ‘package:stats’:

      IQR, mad, sd, var, xtabs

  The following objects are masked from ‘package:base’:

      anyDuplicated, append, as.data.frame, cbind, colMeans, colnames,
      colSums, do.call, duplicated, eval, evalq, Filter, Find, get, grep,
      grepl, intersect, is.unsorted, lapply, lengths, Map, mapply, match,
      mget, order, paste, pmax, pmax.int, pmin, pmin.int, Position, rank,
      rbind, Reduce, rowMeans, rownames, rowSums, sapply, setdiff, sort,
      table, tapply, union, unique, unsplit, which, which.max, which.min

  Loading required package: S4Vectors

  Attaching package: ‘S4Vectors’

  The following object is masked from ‘package:base’:

      expand.grid

  Loading required package: IRanges
Loading required package: GenomeInfoDb
  Loading required package: ChIPpeakAnno
  Loading required package: grid
  Loading required package: Biostrings
  Loading required package: XVector

  Attaching package: ‘Biostrings’

  The following object is masked from ‘package:base’:

      strsplit

  Loading required package: VennDiagram
  Loading required package: futile.logger

  Warning message:
  In read.dcf(con) :
    URL 'http://bioconductor.org/BiocInstaller.dcf': status was 'Couldn't resolve host name'
  Loading required package: rtracklayer
  Loading required package: doParallel
  Loading required package: foreach
  Loading required package: iterators
  Error in S4Vectors:::normalize_names_replacement_value(value, x) :
    attempt to set too many names (2) on IRanges object of length 0
  Calls: annotatePeakInBatch ... names<- -> names<- -> names<- -> names<- -> <Anonymous>
  Execution halted

I used the following command to run:
nohup nextflow run /home/jacke/bin/chipseq \
    --singleEnd \
     --reads '*.fastq.gz' \
     --genome GRCh37 \
     --project sens2017533 \
     --macsconfig 'macssetup.config' \
     -resume \
     -with-trace \
     -with-dag flowchart.pdf \
      --broad \
     --blacklist_filtering \
     -profile uppmax \
     -with-singularity /home/jacke/bin/singularity_images/nfcore-chipseq.img &

And most, but not all, MACS 2 jobs have finished ok.
EDIT: Two of the peak files from MACS contain no peaks. That is probably what gives the error.

Closed in favour of https://github.com/nf-core/chipseq/issues/35


Doesn't work with static LNURL paymentlinks

App doesn't work with static LNURLs, which makes it nearly useless as a POS device because you don't know what customers are presenting, Boltcard or regular NTAG 21x with static link. Please integrate LNURL in this great app!

Hi @tscharly, help me understand - this PoS app is nearly useless because it doesn't support static LNURLw links?
Is it correct that Static LNURLws are mainly for "gift cards" ?  are static LNURLw's really that useful?

With LNURLw links you can use simplest and cheapest NTAGs as a payment device. Of course it's insecure, but quick and cheap. At a bar of a bitcoin-event people present all kinds of NFC-devices to pay for their beer and mainly they have LNURLws stored at them.

Static LNURLw links are ok as one time use gift cards only.
They need to be swept in full due to the lack of replay protection.
It's also overkill using an NFC card for a static in most cases when they could be a printed QR code.
Dynamic LNURLw links (i.e. bolt cards) are a different thing - they enable multiple use payment cards.
The additional active features of NXP NTAG 424 DNA cards are fully used to enable this.
I think we should avoid 'insecure'. I note that bolt cards are also quick and cheap.

Static LNURLw links now supported in version https://github.com/boltcard/bolt-card-pos/releases/tag/v1.5.0

Great, thanks!


Open debugger in situ upon error

Install appropriate restarts around assertion code when supervising their execution.
Introduce TESTCASE-INTERACTION-MODE which governs interaction patterns when failures are encountered on an assertion test.
This is to address #4.
@lukego Does this branch make your work with KONS-9 easier?

Caution, rebased!

Rather use the branch break-into-the-debugger-upon-error.


Make the panels sized by percentage

How would this work for existing projects where the panel width is already set as small, medium, large or full? We could end up with two properties for controlling panel width in the editor which would be confusing.

Can't those existing sizes map to percentage e.g.
Small = 20%
Medium = 50%
Large = 75%
Full = 100%

And then deprecate the current panelsize and add a new mandatory property containing percentages.
It will require some code in each model to figure it out, but yes, it would be very good.

It was how it would look in editor that worried me - I get how it would work in page models.
The deprecated properties will still show up in editor in existing projects & then by adding a mandatory property you'd end up with this on lots of pages in existing projects

I know we have deprecated things before but this seems a bit clunky considering how many pages & projects this will appear in

Hi all,
This was raised at the Edinburgh event and from memory I think it was more to do with how the panels react when responsive is on...
So rather than having a 60% option @FayCross I took from it that it was how small, medium, etc are interpreted to make sure that small for example stays at 25% of the total width as you expand the LO...

Yes, I agree, but it is definitely an improvement.
We can also follow John's proposal, and reading back, I think that's what Ron is suggesting as well.

Oh ok, all the panels where you select whether it's small, medium or large are all responsive already (40%, 60%, 80%). But there are other kinds of pages where panels are used where I think there's a max size set (e.g. morph images?) These do need looking at. I misunderstood and thought it was about sizing the pages with full height panels (like navigators)

Are you happy @FayCross that this one is fixed?


Improve Report type

Feature description
Some days ago I was looking how CSN handle reports and I've noticed that they all let users select a category (or more then one) from a list of existent categories. I think it should be good to standardise this thing on Desmos.
Currently we only have a generic type field (which name is IMO a little bit confusing) that can be any string.
In the long, when there will be a variety of apps using Desmos this will result in a lot of confusions with possibly tons of different categories.
Implementation proposal
To improve it, I'm actually thinking about something like this:
enum Reason {
  option (gogoproto.goproto_enum_prefix) = false;

  NUDITY = 0;
  VIOLENCE = 1;
  INTIMIDATION = 2;
  HARASSMENT = 3;
  SUICIDE = 4;
  SELF_HARM = 5;
  FAKE_INFORMATION = 6;
  SPAM = 7;
  UNAUTHORIZED_SALES = 8;
  TERRORISM = 9;
  OTHERS = 10;
}

// Report is the struct of a post's reports
message Report {
  option (gogoproto.equal) = true;
  option (gogoproto.goproto_stringer) = true;

  // ID of the post for which the report has been created
  string post_id = 1 [
    (gogoproto.customname) = "PostID",
    (gogoproto.jsontag) = "post_id",
    (gogoproto.moretags) = "yaml:\"post_id\""
  ];

  // Identifies the type of the reports
  repeated Reason reasons = 2
      [ (gogoproto.jsontag) = "reasons", (gogoproto.moretags) = "yaml:\"reasons\"" ];

  // User message
  string message = 3 [
    (gogoproto.jsontag) = "message",
    (gogoproto.moretags) = "yaml:\"message\""
  ];

  // Identifies the reporting user
  string user = 4
      [ (gogoproto.jsontag) = "user", (gogoproto.moretags) = "yaml:\"user\"" ];
}

I'm just giving an example here and maybe there are better ways to handle this, just pointing this out.
Thoughts? @RiccardoM @dadamu

@bragaz I agree this change. Categorizing reasons in this way would be useful.
By the way, I have a question about what will happen next after reporting. There is not any action, especially deleting the post after reporting in the current version. I am worried about that there will be a lot of posts violating the rights of others.

To be honest, I'm not in favor of including all possible reports types as hard-coded. Instead, I think it would be much better to put those possible types as chain parameters so that the governance will be able to add more if needed without us having to release a new version of Desmos all together. For this reason, I would delete the enum and simply add a method that's like
func (k Keeper) IsValidReportType(ctx sdk.Context, reportType string) bool {
  types.Contains(k.GetParams(ctx).ReportTypes, reportType)
}

@RiccardoM So add them as params with a proposal to add more through gov right?

@RiccardoM So add them as params with a proposal to add more through gov right?

Yeah exactly

Great then. I will take care of this

Closing this as it will be discussed when we create a x/reports module ADR


Broken links

There are some broken links in the documentation:

The link  to "generation pipeline documentation" is broken
The link  to "OSRM detailed documentation" is also broken

To reproduce the issue, go to page "https://github.com/loggi/loggibud/blob/master/docs/quickstart.md" and clink on the cited links.

Fixed by https://github.com/loggi/loggibud/commit/610bd2b59c7de7911e3f82fc6df7f2800f880cd5
Thanks for the report.


Symbolic Tensors

The Keras interface works fine but I had to change the Binary Encoding.
TensorFlow’s Graph Mode relies on Symbolic Tensors, which act as placeholders without actual data during initial model checks. When using model.fit, TensorFlow first uses these Symbolic Tensors to traverse and verify the computation graph, ensuring compatibility across all operations. Only after this validation process, when the graph structure is confirmed as sound, does TensorFlow pass real data through the model to perform actual training. This approach allows TensorFlow to optimize and catch issues before handling real inputs.
Therefore, we have the following problems (probably more) when dealing with Symbolic Tensors:

We cannot use NumPy functions on Symbolic Tensors;
We cannot access data contained in Symbolic Tensors (because they are empty);
We cannot iterate over Symbolic Tensors (because they are empty);
We cannot use "if" statements if Symbolic Tensors are involved;

We need to work around these problems by using native TensorFlow functions.
For instance, instead of an "if" statement we must use tf.cond.
However, the issue that I have encountered with the Binary Encoding (which has forced me to redefine this encoding) could be a sign of a deeper problem: we might need to define each encoding (or every other component of the QuantumModel) depending on the frontend that we use.
This is due to the fact that Symbolic Tensors force us to use native TensorFlow functions, that could be not compatible with PyTorch.

You can force eager execution with run_eagerly=True in model.compile https://www.tensorflow.org/api_docs/python/tf/keras/Model#run_eagerly
This is probably not recommended for the sake of pure speed, but we could just do that for those layers that are problematic, at least for the moment.


-OAuthAuthentication on Exchange 2010

Parameter OAuthAuthentication is not supported on Exchange Server 2010. Please correct "Applies to" section.

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

ID: 7da3b3b1-12d9-608f-7379-f13d988d0fe2
Version Independent ID: feaa10b4-067a-5ac9-6df3-c3c84567fb2f
Content: Set-WebServicesVirtualDirectory (exchange)
Content Source: exchange/exchange-ps/exchange/client-access-servers/Set-WebServicesVirtualDirectory.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@AndreyNov, since April, 2018, the Exchange cmdlet reference topics are single sourced between Exchange 2010, Exchange 2013, Exchange 2016, (now) Exchange 2019, Exchange Online, Office 365 Security & Compliance Center, and Exchange Online Protection. The value of single-sourcing these topics is enormous, as there are hundreds of cmdlets available and shared between the various environments.
Near the top of the topic is an Applies To: tag that sets the first level of "where is this cmdlet available?". For Set-WebServicesVirtualDirectory, it says this:

Applies to: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019

The next level is at the parameter description itself. Even though the cmdlet is available across different versions of Exchange, it's likely that not all parameters are available in all versions, so check the Applies To value in the parameter description. For the OAuthAuthentication parameter, the Applies To: information looks like this:

Applies to: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019

So, there's no indication that OAuthAuthentication in Set-WebServicesVirtualDirectory applies to Exchange 2010. And, the topic hasn't been updated since September, so someone didn't sneak in and fix it after you left your comment but before this response.

Hello Chris,
Good explanation. Thank you!
Sorry for my mistake.


Remove not substituted arguments

Proposal to not add not substituted arguments if they a not in route.  I think this not need here, in UrlGenerator::generate() has the separate argument for query string. If it ok, I can make PR.
https://github.com/yiisoft/router-fastroute/blob/2a570aa9d99743bee69faf34c9b712b6d7dd2941/src/UrlGenerator.php#L300-L303
What steps will reproduce the problem?
// routes
Route::get('/view/{mode}')->name('view');

$urlGenerator->setDefaultParameter('mode', 'simple');
$urlGenerator->setDefaultParameter('type', 'any');

$urlGenerator->generate('view');

What is the expected result?
/view/simple
What do you get instead?
/view/simple?type=any
Additional info

Q
A

Version
3.0.0

PHP version
8.0

Operating system

Please do. It makes sense.


Training model from checkpoint in RASA NLU

Issue:
For very large datasets training the model can take a lot of time. Currently with 380,000 data points my RASA NLU takes over 2 hours. A lot of problems with that as my actual production data set would be even bigger than that.
Looked inside the library but didn't really find any method/option to continue training on top of an existing model. Would be much better to generate models iteratively

This isn't possible with the libraries we use right now. We are working on speeding up rasa nlu training/making it less memory intensive though.
Can I ask why you have 380,000 examples? how many intents do you have?

Reasons for these many data points:

We have two intents but query shapes that have multiple entities of the same type (think of a grocery list with multiple products, counts and brands).

The product list is around 400-500 products which leads to 10s of millions of combinations, we are using chatito to generate synthetic data.

To make it work we used a subset of all possibilities because chatito cannot generate the entire training data without requiring significant changes and training time was too much.

As per our last set of testing even the subset is working fine but we aren't sure how little is too little.

I would highly recommend you switch to using lookup tables instead for extracting your entities.
especially for just 2 intents there is no need to generate so much synthetic data.


Add Simplified Chinese Translation

Just like the title!

Thanks for your PR! I will merge it when I habe time :)

Your change will be released in 1.18.2-<IP_ADDRESS>

Thank you!


Allow people to upload a picture from device as a profile picture

Added select image from user device. Tested with Web and partially tested with xnft(on web instead of the extension).
It is using Infura IPFS. Needed to setup Infura Account. I don't see the app using environment variables on building, so I have coded those keys in src/utils/ipfs/index.tsx, line 4-6.
Outcome Screenshot

@cylim Thanks a lot for opening this PR, I will review in the coming days.


respect optional fields in protobuf emitter

Respect optional in protobuf emitter
The current implementation doesn't consider optionality of fields
model Test {
  @field(1)
  test?: boolean;
}

resulted in
message Test {
  bool test = 1;
}

This PR fixes this, so the output is as expected:
message Test {
  optional bool test = 1;
}

@microsoft-github-policy-service agree

Just had a call with our backend team, and this turns out to be more complex.
The optional keyword behaviour is not always the same and depend from the client language as well.
So this can be solved only with decorators because there's no constant connection between the open api optional filed definition and protobuf optional keyword presence.
Closing it for now and will try to find the time to make it through decorators.


Trouble installing: Can't find OpenGL

Thanks for this project, I am eager to try it out, but  am unable to install it currently.  Its not building and giving error while running Cmake, saying OpenGL missing. It seems to be a common issue which is fixed after installing basic openGL libraries, but here its not the case.
My system:
Ubuntu 22.04 (jammy)
Python 3.10

I was able to compile it by setting the library path in CMakeLists.txt before it tries to find openGL in system. Probably with cuda and nvidia, it changed the default path and needed to explicitly set it
set(OPENGL_gl_LIBRARY /usr/local/cuda-11.7/nsight-compute-2022.2.1/host/linux-desktop-glibc_2_11_3-x64/Mesa/libGL.so)


Write a better README

As for now README is quire poor. Need to add better examples and featured images pictures.

Can i help with this enhancement.

@vvanarasi sorry, almost finished the work for this issue. Generated some better featured images and changed README to be more attractable. Just haven't pushed yet.


Adding a Docker image

Adding a Docker image to give the option of trying out the server as a container.
Please feel free to provide any feedback!

Don't really see a huge advantage to doing this – not enough need for a Docker image here. Thanks for the suggestion though!

If anyone reading this is interested, I have a similar project with a Dockerfile here: https://github.com/styfle/react-server-example-tsx/blob/master/Dockerfile


Adding TargetFrameworks to the list of data retreived from NuGet packages

Successor to #79
Original PR description:

Per a conversation about adding target framework information to the component detection data, this is a PR that shows what that could look like.
Things get slightly tricky here since packages declare target frameworks through the dependency declarations in the nuspec, as well as the folder structure of the package. This hasn't been through much testing beyond the unit tests, but they've been augmented to test some potential patterns.
I mainly want to get some feedback on this before I spend much more time on testing. I can potentially test this against all NuGet.org packages pretty easily, which also gives us a test oracle since they calculate target frameworks as well.
Things that might need consideration:

Addition of NuGet.Packaging as a dependency
how the data is plumbed through the NuGetComponent (I followed the Authors example as an array of >additional strings)
Removal of async from ProcessFile (nothing in there was async when I finished)
Shifting more responsibility to NuGetNuspecUtilities even through it's not strictly nuspec-related >anymore.
Using the nuspec reader rather than bespoke XML parsing

I'm open to any and all feedback here.

Thanks for rebasing/bumping this, @JamieMagee ! When I first wrote this, this was very much intended to be a draft to start a conversation on how target framework info could be added to component detection. I'm very happy to engage in whatever capacity is most helpful in seeing progress here.

Hi guys
Any progress on this in the near future? I actually would love to read more properties from the .nupkg/.nuspec...

copyright
urls
licencse
authors
...basically all the main props in a nuspec

@JamieMagee is this still needed?

It definitely is needed by me :)

Closing due to staleness/large number of conflicts. There is active work ongoing to improve detection for NuGet in this area that will cover the issues raised by this PR.


expanded columns not taking up all the space

How to reproduce this bug:

Create .row.expanded
create .small-12.large-7.columns and .small-12.large-5.columns

What should happen:
Split the columns perfectly into the width of container
What happened instead:
1px of whitespace is leftover on the right side of the columns.
If I then change the large-5 max-width and flex properties from
flex: 0 0 41.66667%;
max-width: 41.66667%;

to
flex: 0 0 41.668%;
max-width: 41.668%;

Then the tiny whitespace is eliminated. Any ideas to why this happens?
UPDATE
This only happens in chrome, and only on certain screen sizes / screens.. might just be a browser bug..

Please provide test case,
You can fork these below codepen's to provide a test case.
6.3.0

CodePen with Foundation 6.3.0 and MotionUI
CodePen with Foundation 6.3.0, Flexbox grid and MotionUI

6.3.1

CodePen with Foundation 6.3.1 and MotionUI
CodePen with Foundation 6.3.1, Flexbox grid and MotionUI

No test case provided. Closing.


Template editor navigation and property reordering

Hi, Large templates are often hard to navigate while editing.  I have 2 wishes that would make editing easier:

That the left pane lists the labels of each property instead of just "Property template".
A property ordering mechanism (e.g. a way of pushing property templates up or down)

It would be nice to have "make first" reordering option.
Also simply a "return to top of page" or even better "top of property list" and "bottom of property list" would improve things


Enable-WriteCore-feature-for-dnsresolver

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.DnsResolver


Support custom timeout_commit in testing mode

Summary
Since v3, timeout commits are now dictated by the application. This has made it difficult in the case of testing, where we and others want to be able to have short timeouts. Both sovereign and eiger have reported this being problematic for them.
Proposal
Introduce either an environment variable or a flag to force set the timeout commit. We may want to consider this to also set the square size as well. If we're concerned about misuse on a live network we can add chainID checks.

Furthermore, we might want to, if it's not too breaking, to rename the current timeout_commit and timeout_propose in the config.toml (or at least the go struct) to something else so as to avoid confusion. Most teams may still be setting these values and think it will change the times

Introduce either an environment variable or a flag to force set the timeout commit. We may want to consider this to also set the square size as well.

We have the OVERRIDE_MAX_SQUARE_SIZE env variable which can override the max square size at binary build time so we could add another for overriding timeout_commit.
Alternatively, we could override the timeout_commit when the chain_id is test similar to how we override the upgrade height delay to 3 here.

Furthermore, we might want to, if it's not too breaking, to rename the current timeout_commit and timeout_propose in the config.toml (or at least the go struct) to something else so as to avoid confusion. Most teams may still be setting these values and think it will change the times

IMO we should deprecate the config timeout_commit and timeout_propose in v3.x.x and remove them in v4.x.x.

Related: https://github.com/celestiaorg/celestia-app/issues/4023