Python: CreateGraphRequest doesn'

Describe the bug
A clear and concise description of what the bug is.
https://github.com/microsoft/semantic-kernel/blob/ca55eeee1b1f24f68d164294827ab3405d1717ee/dotnet/src/Connectors/Connectors.Memory.Weaviate/Http/ApiSchema/CreateGraphRequest.cs#L23C67-L23C80
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform

OS: [e.g. Windows, Mac]
IDE: [e.g. Visual Studio, VS Code]
Language: [e.g. C#, Python]
Source: [e.g. NuGet package version 0.1.0, pip package version 0.1.0, main branch of repository]

Additional context
Add any other context about the problem here.

Duplicate: https://github.com/microsoft/semantic-kernel/issues/4877


Update REQUEST-903.9003-NEXTCLOUD-EXCLUSION-RULES.conf with SEARCH Method for image gallery

Method SEARCH is needed for Nextcloud image gallery. If not set, images are not shown and you get the error
[Wed Oct 11 11:55:13.159009 2023] [security2:error] [pid 1587527:tid<PHONE_NUMBER>78176] [remote xxx.xxx.xxx.xxx.:46886] [client xxx.xxx.xxx.xxx] ModSecurity: Access denied with code 403 (phase 2). Match of "within %{tx.allowed_methods}" against "REQUEST_METHOD" required. [file "/usr/local/pd-admin2/httpd-2.4/conf/coreruleset-current/rules/REQUEST-911-METHOD-ENFORCEMENT.conf"] [line "44"] [id "911100"] [msg "Method is not allowed by policy"] [data "SEARCH"] [severity "CRITICAL"] [ver "OWASP_CRS/3.3.5"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [tag "paranoia-level/1"] [tag "OWASP_CRS"] [tag "capec/1000/210/272/220/274"] [tag "PCI/12.1"] [hostname "xxx"] [uri "/remote.php/dav/"] [unique_id "ZSZxAZ2_w6VradUXudZIrgAAOhA"]
Additional Info:
Apache 2.4.57
modsecurity 2.9.7
coreruleset-3.3.5
Nextcloud 27.1.2

Hi @Sumeragi85. Please note that you are sending PR to the discontinued branch of CRS (v3.3/master).
All rule exclusion packages were discontinued and are no longed developed or maintained. All of them were replaced by plugins - for Nextcloud, see here. Try this new plugin and, if you are still having problems, send a PR to the nextcloud-rule-exclusions-plugin repository. Thank you.

Hi @azurit and thank you for your response. Did not see that version 3.3 is EOL. Website and doc still shows 3.3.5 as current and thought 4.0 is still in dev. Is there a roadmap available?
Anyhow. I just tested your suggested way. Installed coreruleset 4.0 with the Nextcloud plugin and it works like charm :)

We are only fixing major and security bugs for 3.3, all development is taking place in 4.0.
Feel free to close this PR if everything works for you, thank you.


Basic mode and extended mode

In basic mode, only common markdown and GFM are supported. Content created is fully supported on GitHub.
In extended mode, all markdown extension syntax is supported, such as flowchats, latex math...etc.
Two modes should be switchable in preferences modal.

Won't implement.
Because it's up to the user whether to use advanced features. By default the editor support lots of features, users are not required to use all of them.


Add change trigger on raw_id_fields for m2m

Looks like the change function is not triggered if the field value is changed when using the raw_id_fields (popup).
Adding the trigger by overwriting dismissRelatedLookupPopup is necessary until django admin fixes this.
Similar to how dismissAddAnotherPopup is changed as well.
Open to feedback on how to do this better

Coverage remained the same at 89.588% when pulling 7b3cc335c22bc5b22010569c05b6641ed6fdf73f on leibowitz:add_change_trigger into e7fe61b3edc6c81a2da5343a1fad7c7bdacea1cf on digi604:master.

Thanks!


Publishing complex app dependencies to AppSource

This might be related or its atleast is happening in the same repo as #328 was.
To recap, we have the following structure.
RepoA
- AppA
- AppB
- AppC
- AppD

Each app is its own project because AppA and AppB are not dependent, it might make sense to release them independently.
But from a marketing perspective that currently doesn't make sense.
The dependencies are as following:
AppA <-
        AppC  <- AppD
AppB <-

pardon my ascii...
We've currently only released AppD to AppSource. The rest are libaries.
Firstly if I run the "Publish to AppSource" workflow with the default settings I get the error AppSourceProductId needs to be specified in AppA... AppB... AppC.... It would be good to be able exclude Projects from release. So that I don't need to think about all these little details when releasing any of the 50+ apps. Because thinks like this are bound to be forgotten.
Now comes the Issue:
If I only run the workflow for the project I want to release I don't get any errors but AppA AppB and AppC won't be include as libaries. The worklfow then only updates the main app without any warnings.
This might actually break stuff if the main app is updated but the libraries won't.
To be honest I get why this is a difficult problem to solve. Because Al-Go has no clue which of the dependencies exsits in AppSource and which need to be includes as libraries.
This currently means we need to publish manually or reverting back to only use one Project per repo - which I really don't want to do because, I will have to revert these changes later again.

@freddydk did you have time to have a look at this issue?

Not yet - but this week hopefully

As a temporary fix we've now published all the apps to AppSource. But this isn't a viable longterm solution. Maybe I'm missing something, but how does AL-GO determine if dependencies need to be included as libraries or if its already present in AppSource?

@freddydk any updates?

Time flies, working on issues this week - will prioritize this.

In your example above, AppA, AppB, AppC are only uploaded to AppSource as libraries to AppD?
i.e. - they don't have their own productId.

No A,B,C are Dependencies to D. But yes you are right they don't have productIds. But the Issues is the same if you have dependencies you get from github packages. When you need to download your dependencies you wont have any information about the product id.

Do you have generateDependencyArtifact set to true?
That won't solve the entire problem though.
I think the solution to this is as follows:

Set generateDependencyArtifact = true and include dependencies as libraries when submitting (not sure whether that happens today).
Have a project setting explaining which dependencies to include in your submission (* would be default and grab all dependencies used for building). There could also be a exclusion list (if you want to include all but one 3rd party dependency)

Agree?

Yes I'm already using generateDependencyArtifact.
I guess thats to most generic approch to handling it.
But I don't like if I have to duplicate settings. It would be cool to include a property in the nuspec file and be able to get if from the .AL-Go/settings.json if possible.

If I know which App has a product ID I know that I don't need to include it and it's dependencies right?


Added global filter for CSRF check

Added global filter and removed annotations per action.

@ccsalazarr-commercetools looks good! Have you checked all forms still work properly? Unfortunately we don't have webtests yet to check that for us :(


Run tests

Hi,
Thank you so much for your work! It's of great help.
I have some problems regarding testing models. I notice there're codes for test, but I don't know where to run them. I wonder if you could help me with it. Thanks a lot!!

Hi @wanggsz, thanks!
To evaluate the final performance, please use the test_model function in the evaluate.py script located at pathfinding/models/dhc/.
The script supports the fire library for command-line arguments, which means that you can run something similar to poetry run python3 pathfinding/models/dhc/evaluate.py test_model '[(40, 4, 0.1), (80, 4, 0.1), (40, 8, 0.1), (80, 8, 0.1), (40, 16, 0.1), (80, 16, 0.1), (40, 32, 0.1), (80, 32, 0.1),  (40, 4, 0.3), (80, 4, 0.3),  (40, 8, 0.3), (80, 8, 0.3),  (40, 16, 0.3), (80, 16, 0.3), (40, 32, 0.3), (80, 32, 0.3)]' 337500 to test the model with the provided id (337500  in this example; weights must be located in the /models dir) on a set of provided maps.
You can append a True/False flag at the end of the command to choose between MovingAI maps and regular random maps from the original paper. For MovingAI maps, the command would be something like poetry run python3 pathfinding/models/dhc/evaluate.py test_model '[(32, "Berlin_0_256.map", "Berlin_0_256.map.scen")]' 337500 False
There's also a function to visualize the performance on a single map instance: https://github.com/acforvs/dhc-robust-mapf/blob/main/pathfinding/models/dhc/visualize.py#L64 for random maps and https://github.com/acforvs/dhc-robust-mapf/blob/main/pathfinding/models/dhc/visualize.py#L133 for MovingAI maps


ARROW-7991: [C++][Plasma] Allow option for evicting if full when creating an object

Allow the client to pass in a flag during object creation specifying whether objects should be evicted or not.

cc @pcmoritz @robertnishihara

Thanks for the PR, the logic looks good to me! Let's make sure we do not break backwards compatibility of the PlasmaClient API though and move the evict_if_full argument to the end and have a default value of true (same for CreateAndSeal and CreateAndSealBatch). For consistency we should do the same for PlasmaClient::Impl.


[JS] Topic: Tutorial for JavaScript Operators Fixed #202

Description 📜
Created a tutorial for operators in JavaScript.
Fixes #202

Type of change 📝

[ ] Audio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Video (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev (Flutter, Java, Kotlin)
[ ] Backend Dev (Java, .NET, Python)
[ ] C/CPP
[ ] Competitive Programming
[ ] Cyber Security
[ ] DSA
[ ] Database
[ ] Datascience with Python
[ ] Datascience with R
[ ] Frontend Dev (HTML, CSS, JS)
[ ] Frontend Dev (React, Angular, Vue)
[ ] Golang
[ ] Interview Prep
[ ] Java
[x] JavaScript
[ ] MERN
[ ] Machine Learning
[ ] Open Source
[ ] Python
[ ] Rust
[ ] Statistics
[ ] UI/UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@paramsiddharth as you suggested in todays meet I have close my previous PR,and created a fresh PR made changes as you told me.

@paramsiddharth Please review changes.

@Himanshu664 very well structured. I have reviewed and approved it. Keep it up:-)


wrong resolution discovered by hyperion

[x] I confirm that this is an issue rather than a question.

Bug report
Hyperion shows wrong resolution for grabbers other than framebuffer - it means X11 and XCB
It worked correctly through years, including updates os Libreelec and hyperion and now -failed.
Today, after I've observed issue, I updated libreelec to <IP_ADDRESS> and Hyperion - to 2.0.16 - no effect.
Some screenshots here.
This what I can see (and its not expected)

This is effect seen on hyperion side.

In real world only part of my leds work, the most pf them is located next to black areas of display, so - they do nothing. However I can watch my videos on entire screen.
Steps to reproduce
Just try to set correct resolution for my device - it is fixed on wrong values.
What is expected?
Hyperion should read correct values of resolution and/or should let me set it manually.
The correct values are 1360x768
What is actually happening?
This is stable situation - but still wrong.
I've tried to:

export settings,
change width/height values for framegrabber to correct ones
import settings back
restart hyperion and reboot OS
No effect, however when I exported settings once again, I can see there correct, expected values. Hyperion GUI still shows 3280x1080 and work with it.

System

Hyperion 2.0.16 (same on 2.0.15)
OS: Libreelec: 12.0.1 (same on 12.0.0)
Kernel: Linux 6.6.46
Hardware: Dell Wyse 5060 with Radeon R5E and two Displayports. Due to Dell websites it does not support 3280x1080 resolution or double 1640x1080 https://www.dell.com/support/manuals/pl-pl/wyse-5040/thinos_8.5_ag/configuring-the-general-display-settings?guid=guid-e6986f35-28c2-459b-89f2-b75bf66891dd&lang=en-us

What LibreElec variant did you install?
Capturing via X11 normally requires Legacy Generic PC (for older PCs and NVIDIA GPUs).
Framegrabber is not a capture option any longer, since LibreElec changed their window manger with Matrix (v 10)

This is Legacy Generic variant - it was the only way to have hyperion running. I've installed version 11 more than year ago and it worked well till now, also through online updates.

This the following something that could be relevant for you?
https://forum.libreelec.tv/thread/28485-how-to-automatically-change-resolution-after-switching-tvs/
As it kicked in when switching versions and Hyperion is using data presented from the OS, I would assume it is related to LibreElec.
If you cannot resolve, I would suggest you check with the LibreElec forum.

Issue didn't start after update. I tried to update LE and Hyperion when observed the issue, with hope that it will solve problem. Issue started just like that with unknown reason.
But: there is no issue between LE and TV. It shows the same all the time (1360x768) and works perfectly with TV. The only part of system which fails is hyperion.
Of course I can ask on LE forum, but - is there a way to force resolution on hyperion side?

I've  found it!
The issue is outside of hyperion, kodi and libreelec. It's closer to hardware, some kind of hung up.
I completely forgot about one thing: few month ago I've connected HDMI wireless transmitter (with converter of course) to the second DisplayPort. From time to time I use FullHD projector with it.
So starting from this July I had:

DP1 with 1360x768 TV
DP2 with 1920x1080 transmitter

This worked great till now and without any reason - failed. With completely no action performed, including any connections or turning projector on/off.
I've checked:
xrandr
Screen 0: minimum 320 x 200, current 3280 x 1080, maximum 16384 x 16384
DisplayPort-0 connected primary 1360x768+0+0 (normal left inverted right x axis y axis) 1600mm x 900mm
1360x768      60.02*+
[...]
DisplayPort-1 connected 1920x1080+1360+0 (normal left inverted right x axis y axis) 708mm x 398mm
1920x1080     60.00*+  50.00    59.94    30.00    24.00    29.97    23.98
[...]
Looks like Screen 0 changed its primary display.
Now just disconnected transmitter and connected back and looks that DP-1 does not determine final resolution. I can see:
Screen 0: minimum 320 x 200, current 1360 x 768, maximum 16384 x 16384
DisplayPort-0 connected primary 1360x768+0+0 (normal left inverted right x axis y axis) 1600mm x 900mm
1360x768      60.02*+
[...]DisplayPort-1 connected (normal left inverted right x axis y axis)
1920x1080     60.00 +  50.00    59.94    30.00    24.00    29.97    23.98
1920x1080i    50.00
1280x1024     75.02    60.02
1440x900      59.90
1360x768      60.02
1280x720      60.00    50.00    59.94
1024x768      75.03    70.07    60.00
800x600       72.19    75.00    60.32    56.25
720x576       50.00
720x480       60.00    59.94
640x480       60.00    59.94
None is marked by star "*".
Probably I could fix my issue using command:
xrandr --output DisplayPort-0 --primary
I'll check it next time...

Great that you identified the root cause of the issue!


fail if no version is provided

Users should provide a specific version, although if they choose to use latest that's fine too.

Squash commits, into
Require redpanda_version, and require cert variables in a TLS setup


Adding data directory and my_file.csv

I want to share my data with my folks in master.

You're missing with a change

Now you can merge! 😁


[STY] use scientific-python best practice recommendations

Codecov Report
Patch and project coverage have no change.

Comparison is base (862be38) 78.92% compared to head (4245ce8) 78.92%.
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #100   +/-   ##
=======================================
  Coverage   78.92%   78.92%
=======================================
  Files           6        6
  Lines         726      726
=======================================
  Hits          573      573
  Misses        153      153

Files Changed
Coverage Δ

cohort_creator/cohort_creator.py
69.48% <ø> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Missing comma in Fallback Policy Doc

Rasa Core version: master
Python version:  3.6
Operating system (windows, osx, ...): linux and os x
Issue:
Looks like comma is missing from Fallback Policy Doc
    fallback = FallbackPolicy(fallback_action_name="utter_default",
-                             core_threshold=0.3
+                             core_threshold=0.3,
                              nlu_threshold=0.3)

I can do quick PR if this make sense.

Yes that would be great :+1:


Fix "Error using base32 encoding #64"

Coverage remained the same at 100.0% when pulling d166c6e9dc93df50ed5ce7f002f0740fdd611880 on railsstudent:master into 2b3b947e08f198fb6133546b17a594f0df93a8da on speakeasyjs:master.

Coverage remained the same at 100.0% when pulling d166c6e9dc93df50ed5ce7f002f0740fdd611880 on railsstudent:master into 2b3b947e08f198fb6133546b17a594f0df93a8da on speakeasyjs:master.

Coverage remained the same at 100.0% when pulling d166c6e9dc93df50ed5ce7f002f0740fdd611880 on railsstudent:master into 2b3b947e08f198fb6133546b17a594f0df93a8da on speakeasyjs:master.

Test case?

What kind of test cases are needed? I can write test cases that don't throw error, however, I don't have actual inputs to validate digest returned is correct.

The test case is running Speakeasy in the browser. I wrote base32 to return a native JavaScript Array instead of a Node Buffer, hence issue #64
Speakeasy doesn't officially support the browser, so I would consider this a temporary hotfix in lieu of implementing a more major enhancement.


Fix baseswim link in README

Just a small update to the readme to get the baseswim link pointing to the right place. Perhaps original the intent was to pull the baseswim repo into the upring org at some point? That probably would be the better solution.

Thanks!!


Can't Run Nadeko

So I set up NadekoBot on my Windows PC today. I followed the guide perfectly but somehow when I try to run NadekoBot, a few seconds after the command prompt pops up, i get the error "dotnet has stopped working."
This is what is written on the CMD.
Project Discord.Net (.NETStandard,Version=v1.3) was previously compiled. Skippin
g compilation.
Project Discord.Net.Commands (.NETStandard,Version=v1.3) was previously compiled
. Skipping compilation.
Project NadekoBot (.NETCoreApp,Version=v1.0) was previously compiled. Skipping c
ompilation.
01:17:32 NadekoBot | Starting NadekoBot v1.0-rc2
01:17:33 ShardedDiscordClient | Shard #0 initialized.
01:17:34 ShardedDiscordClient | Shard #0 logged in.
Unhandled Exception: System.PlatformNotSupportedException: The WebSocket protoco
l is not supported on this platform.
at System.Net.WebSockets.WebSocketHandle.CheckPlatformSupport()
at System.Net.WebSockets.ClientWebSocket..ctor()
at Discord.Net.WebSockets.DefaultWebSocketClient.d__24.
MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNot
ification(Task task)
at Discord.Net.WebSockets.DefaultWebSocketClient.d__23.MoveNext
()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNot
ification(Task task)
at Discord.API.DiscordSocketApiClient.d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at Discord.API.DiscordSocketApiClient.d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNot
ification(Task task)
at Discord.API.DiscordSocketApiClient.d__21.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNot
ification(Task task)
at Discord.WebSocket.DiscordSocketClient.d__70.MoveNext
()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Discord.WebSocket.DiscordSocketClient.d__70.MoveNext
()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNot
ification(Task task)
at Discord.WebSocket.DiscordSocketClient.d__69.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNot
ification(Task task)
at NadekoBot.ShardedDiscordClient.<b__71_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNot
ification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at NadekoBot.NadekoBot.d__41.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNot
ification(Task task)
at NadekoBot.NadekoBot.d__42.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNot
ification(Task task)
at NadekoBot.Program.Main(String[] args)
NadekoBot has been succesfully stopped, press any key to close this window. #

you can't run it on windows7 or older, that's one of the first lines in the guide. :\

I didn't noticed that. Thanks for the reply :+1:


feat: allow run skipped tests

Description
Solves #150
Type of Change

[x] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

Am I missing something, or should this check be passing? 🤔
Error: Unknown scope "dart_package" found in pull request title "feat(dart_package): allow run skipped tests". Use one of the available scopes: dart_package, deps, flutter_package, pana, semantic_pull_request, spell_check.

I've removed the scope, the issue might be related to #118


Plunker generation is broken when there are images on demo

Bug, feature request, or proposal:
Bug/Proposal.
What is the expected behavior?
I'd expect to see demo without anything broken in plunker.
What is the current behavior?
Actually if you click in "Edit in Plunker" button in this page, the generated plunker will be "broken", in other words, without any images.

See #6754

@donroyco not really related. The plunker itself is working... the problem is that this Card example has some images and it isn't being projected to the plunker... that's isn't something new, I'm just wondering if the images could be passed together with the plunker generation.

It is relates, because that issue addresses the main issue here: how can we manage to get stable Plunker examples, because the broke  images you're referring to, worked in the past.

Closed with #6990


kedro-airflow: Extend grouping strategies

Description
https://github.com/kedro-org/kedro/issues/3094 lists a number of pain points experienced by users while deploying their Kedro projects to MLOps platforms. Each kedro node is assigned to a task 1:1.
#241 added the --group-by-memory flag to make it possible to group nodes that share MemoryDatasets between them into one airflow task.
This ticket is to propose extending the grouping strategies offered by kedro-airflow
There's some strategies we can consider -

by pipeline
by tags (https://getindata.com/blog/deploying-kedro-pipelines-gcp-composer-airflow-node-grouping-mlflow/ written by @Lasica)
by namespace(?)

Suggestion

Change the design of --group-by-memory to something like --grouping-stratergy=<nodes/pipeline/memory>/--group-by=<> to take input. This will make it easy for us to add grouping strategies in the future depending on what users actually want/need.
Gather user input on what grouping strategies would be useful

Discussed briefly in Tech Design on 15/5/24:

Grouping by non-persistent datasets is not the ideal way to determine the grouping of nodes into tasks - generating DAGs based on the state of catalog.yml has some downsides:

Catalog at the time of creating DAGs does not have to be the catalog used during deployment
A dataset being MemoryDataset can also differ based on what configuration environment we're using

Recommended grouping strategy should be namespaces but it's not widely adopted.

Follow up actions:

Release the feature introduced in #241 as it is now, if we decide on a different way forward, we can always make a breaking change to kedro-airflow
Investigate adoption and simplification to the usage of Namespaces

Based on the discussion above, closing this to focus on the adoption of namespaces on Kedro side.


Analysis/APIv2 Meetings Endpoints [ENG-421]

Purpose
Initial analysis of moving some meetings endpoints to V2 to support meetings being emberized
Discovery Questions:

Be on the same page about whether we are matching existing functionality. This analysis PR attempts to duplicate v1 behavior in v2, rather than moving to an overhaul (like turning meetings into collections)
General consensus on whether it's ok to break conventions in API for easier sorting/filtering since these are temporary endpoints or if we need more work on sorting related counts or filtering embedded fields, for example.

Meetings

Can meeting submissions count be top level attribute (since this is a temporary private endpoint and sorting this is super easy), or do we need to get sorting working for sorting related counts?
Sorting on city? (easy b/c location is top-level attribute)
Sorting on date? ( assume start date, easy b/c top-level attribute)
Sorting/filtering on meeting name (top level attribute -easy

Meeting Submissions

Filter/sort title - easy b/c node title is top level attribute
Filter/sort author -  Can we make author_name a top-level attribute for easier sorting/filtering? Or what about actually sorting/filtering on creator (since these are created via email, the majority of the time creator/author would be the same).  Otherwise we need to get sorting/filtering on embedded attributes to work.
Filter/sort category - This is actually the presence of a certain tag on the project - poster or talk, usually.  Should we create a custom attribute for this (serializer method field), or should we filter tags field.
date_created - easy to sort on, already top level attribute
Download count - currently surfacing on file relationship, but we could also make top-level attribute for easier sorting

Needed
Meeting

[x] Title [Conference title]
[x] Conference submissions [public/non deleted nodes with conference endpoint tag]
[x] Location
[x] Start Date
[x] End Date
[x] Field names
[x] logo url
[x] meeting url
[x] Search on meeting name
[x] Sort name
[x] Sort # submissions (provided count is top level attribute)
[x] Sort location
[x] Sort start date

Meeting Submission

[x] [Title] - Node title, link
[x] [Author]  First bibliographic contributor name, link
[x] [Category] Tags (to get poster, talk)
[x] [Date Created] date_created
[x] [Downloads] download count of first file, download link
[x] Sort title
[X] Sort author lastname (provided author_name is top level attribute)
[ ] Sort category
[X] Sort date create
[ ] Sort download count
[x] Search title
[ ] Search author
[x] Search category (really searching tags)

Changes
New Endpoints (all private endpoints, b/c expecting this to get refactored when meetings become collections)

_/meetings/
_/meetings/{meeting_id}/?related_counts=submissions
_/meetings/{meeting_id}/submissions/?fields[nodes]=tags,title,contributors,date_created,submission_download_count,meeting_submission

Meeting submission (using NodeSerializer w/ sparse fieldsets)
http://localhost:8000/_/meetings/SPSP2018/submissions/?fields[nodes]=tags,title,contributors,date_created,submission_download_count,meeting_submission
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/vnd.api+json
Vary: Accept

{
    "data": [
        {
            "relationships": {
                "meeting_submission": {
                    "data": {
                        "type": "files",
                        "id": "5cb3694a51a1fe0175109141"
                    },
                    "links": {
                        "related": {
                            "href": "http://localhost:8000/v2/files/5cb3694a51a1fe0175109141/",
                            "meta": {
                                "download_count": 2
                            }
                        }
                    }
                },
                "contributors": {
                    "links": {
                        "related": {
                            "href": "http://localhost:8000/v2/nodes/gn9qp/contributors/",
                            "meta": {}
                        }
                    }
                }
            },
            "links": {
                "self": "http://localhost:8000/v2/nodes/gn9qp/",
                "html": "http://localhost:5000/gn9qp/"
            },
            "attributes": {
                "date_created": "2019-04-09T22:58:00.344445",
                "tags": [
                    "churn",
                    "ecology",
                    "lethal",
                    "navigable",
                    "SPSP2018",
                    "talk",
                    "weather"
                ],
                "title": "Cosmic constant classification corvidae radiation fauna nervous system luminous."
            },
            "type": "nodes",
            "id": "gn9qp"
        }
    ],
    "meta": {
        "total": 1,
        "per_page": 10,
        "version": "2.14"
    },
    "links": {
        "self": "http://localhost:8000/_/meetings/SPSP2018/submissions/?fields%5Bnodes%5D=tags%2Ctitle%2Ccontributors%2Cdate_created%2Csubmission_download_count%2Cmeeting_submission",
        "first": null,
        "last": null,
        "prev": null,
        "next": null
    }
}

Meeting detail
http://localhost:8000/_/meetings/SPSP2018/?related_counts=submissions

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/vnd.api+json
Vary: Accept

{
    "data": {
        "relationships": {
            "submissions": {
                "links": {
                    "related": {
                        "href": "http://localhost:8000/_/meetings/SPSP2018/submissions/",
                        "meta": {
                            "count": 1
                        }
                    }
                }
            }
        },
        "links": {
            "self": "http://localhost:8000/_/meetings/SPSP2018/",
            "html": "http://localhost:5000/view/SPSP2018"
        },
        "attributes": {
            "end_date": "2018-03-03T00:00:00",
            "name": "2018 SPSP Annual Convention",
            "info_url": "http://meeting.spsp.org/",
            "location": "Atlanta, GA",
            "field_names": {
                "mail_message_body": "Presentation abstract (if any)",
                "add_submission": "poster or talk",
                "submission1_plural": "posters",
                "meeting_title_type": "Posters & Talks",
                "mail_subject": "Presentation title",
                "submission2_plural": "talks",
                "mail_attachment": "Your presentation file (e.g., PowerPoint, PDF, etc.)",
                "submission2": "talk",
                "submission1": "poster",
                "homepage_link_text": "Conference homepage"
            },
            "logo_url": "http://meeting.spsp.org/sites/default/files/2018logo-web-banner.png",
            "start_date": "2018-03-01T00:00:00"
        },
        "type": "meetings",
        "id": "SPSP2018"
    },
    "meta": {
        "version": "2.14"
    }
}

QA Notes

Documentation

Side Effects

Ticket
https://openscience.atlassian.net/browse/ENG-421

@mfraezz, some analysis for Monday's meeting - backend will be straightforward - will still need to figure out how to best represent meeting submissions and to make sure the counts are optimized

initial analysis complete - will pick up again once this work has been prioritized and put into a sprint

Going to close analysis ticket and put up a new PR

Will be finished in https://github.com/CenterForOpenScience/osf.io/pull/9025


Bring analyzers from roslyn-analyzers?

The Roslyn team has created an analyzers project: https://github.com/dotnet/roslyn-analyzers
Their license is the same as ours (Apache v2). There is an opportunity to bring some of their analyzers here, the ones we find interesting, of course, with some modifications.
What do you think? Let's discuss it.

What's the logic behind duplicating analyzers?  There's already some here that are done by code analysis, which I don't understand either.

The Code Analysis ones don't run with Roslyn (at least yet).
For me, the logic is that people can come to one place to get analyzers. But that is up for debate, that is why I created this issue.

@giggio Your ideia is copy analyzer to CC ?

Copy and adapt.

Ok.


parameter setting about dinov2 vision transformer when using dinov2_vitb14_pretrain.pth

When i use the dinov2_vitb14_reg4_pretrain.pth or dinov2_vitb14_pretrain.pth
the number of hidden layers is required to be 1370 (as restricted by the pretrained model)
assuming that the size of input image is 224×224 and the patchsize is 14
I noticed that:
self.num_tokens = 1
self.pos_embed = nn.Parameter(torch.zeros(1, num_patches + self.num_tokens, embed_dim))
in the class DinoVisionTransformer
which means I have to set the self.num_tokens to 1114, because the num_patches=(224/14)2=256
does num_tokens have specific meaning or it could be calculated by other parameters?
Thanks

Thanks， I  have found the problem，the num_token is set to 1, the same as VIT, but the input size of image should be 518, so that there are 37×37 patches with size of 14×14，the dimension of hidden layer is exactly 1370.


Collection of Notion Apps and Libraries

Hey Samuel,
wow. Amazing project!
i have started to create a open source project that lists open source projects around the new notion api.
https://github.com/MaaxGr/open-source-notionapi-apps
I have added your Next.JS Blog App to the integration list. Is that okay for you?
Keep going on the amazing work! :)
Kind Regards
Max

Great, thanks! :)


Code crashes on start without --disable-chromium-sandbox

Type: Bug
This started within the last week while I was working on python code in a Jupyter notebook in VS Code using Anaconda.
VS Code refused to start. the application would launch, then show that the window terminated unexpectedly (reason: 'crashed', code: '-1073741502') and suggested New Window and Close. New Window repeated the crash.
The issue did not resolve itself after uninstalling VS Code and VS Code Insiders or after deleting the app data folders for both.
Running vs code from the command line via --disable-chromium-sandbox does allow the IDE to open, but does not permently resolve the issue for me.
VS Code version: Code 1.80.2 (2ccd690cbff1569e4a83d7c43d45101f817401dc, 2023-07-27T20:40:28.909Z)
OS version: Windows_NT x64 10.0.22621
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 9 5950X 16-Core Processor             (32 x 3400)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
63.91GB (30.68GB free)

Process Argv
--disable-chromium-sandbox --crash-reporter-id fa8b709c-77a8-4221-9bf8-f7f06d462491

Screen Reader
no

VM
0%

Extensions (101)

Extension
Author (truncated)
Version

vscode-css-formatter
aes
1.0.2

ng-template
Ang
16.1.4

gitkraken-glo
axo
1.1.2

toml
be5
0.6.0

vscode-icontheme-nomo-dark
be5
1.3.6

armview
ben
0.4.6

markdown-mermaid
bie
1.19.0

language-hugo-vscode
bud
1.3.1

vscode-pandoc
Chr
0.4.3

npm-intellisense
chr
1.4.4

path-intellisense
chr
2.8.4

angular-schematics
cyr
5.4.2

vscode-markdownlint
Dav
0.51.0

vscode-eslint
dba
2.4.2

dendron
den
0.123.0

dendron-markdown-shortcuts
den
0.12.1

dendron-paste-image
den
1.1.1

python-environment-manager
don
1.0.4

xml
Dot
2.5.1

gitlens
eam
14.1.1

prettier-vscode
esb
9.19.0

copilot
Git
1.99.296

copilot-chat
Git
0.4.1

vscode-pull-request-github
Git
0.68.1

gitkraken-authentication
git
1.0.3

live-sass
gle
6.0.6

gc-excelviewer
Gra
4.2.57

vscode-power-mode
hoo
3.0.2

rest-client
hum
0.25.1

vscode-tfs
iva
0.7.2

better-seo
jan
2.0.1

Angular2
joh
16.0.1

vscode-insertdatestring
jsy
2.3.1

vscode-fix-checksums
leh
1.1.0

sort-typescript-imports
mic
1.4.1

azure-pipelines
ms-
1.208.0

azure-dev
ms-
0.7.0

vscode-apimanagement
ms-
1.0.6

vscode-azureappservice
ms-
0.25.0

vscode-azurecontainerapps
ms-
0.5.1

vscode-azurefunctions
ms-
1.12.1

vscode-azureresourcegroups
ms-
0.7.5

vscode-azurestaticwebapps
ms-
0.12.2

vscode-azurestorage
ms-
0.15.3

vscode-azurevirtualmachines
ms-
0.6.5

vscode-bicep
ms-
0.19.5

vscode-cosmosdb
ms-
0.19.4

vscode-docker
ms-
1.26.0

vscode-logicapps
ms-
1.2.9

csdevkit
ms-
0.2.100

csharp
ms-
2.0.312

dotnet-interactive-vscode
ms-
1.0.4313020

vscode-dotnet-runtime
ms-
1.6.0

vscodeintellicode-csharp
ms-
0.1.26

vscode-edge-devtools
ms-
2.1.3

data-workspace-vscode
ms-
0.5.0

mssql
ms-
1.20.0

sql-bindings-vscode
ms-
0.4.0

sql-database-projects-vscode
ms-
1.2.0

isort
ms-
2023.10.1

python
ms-
2023.12.0

vscode-pylance
ms-
2023.7.40

jupyter
ms-
2023.6.1101941928

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-ai
ms-
0.32.2

vscode-ai-remote
ms-
0.30.0

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

remote-containers
ms-
0.299.0

remote-wsl
ms-
0.80.2

azure-account
ms-
0.11.5

azurecli
ms-
0.5.0

powershell
ms-
2023.6.0

resharper9-keybindings
ms-
1.1.0

vscode-node-azure-pack
ms-
1.2.0

vscode-typescript-next
ms-
5.2.20230729

wordcount
ms-
0.1.0

vsliveshare
ms-
1.0.5877

azurerm-vscode-tools
msa
0.15.10

debugger-for-edge
msj
1.0.15

vscode-sanddance
msr
4.1.0

angular2-inline
nat
0.0.17

angular-console
nrw
18.5.0

vetur
oct
0.37.3

vuehelper
oys
0.1.0

material-icon-theme
PKi
4.29.0

vscode-yaml
red
1.14.0

LiveServer
rit
5.7.9

synthwave-vscode
Rob
0.1.15

vue-vscode-snippets
sdr
3.1.1

character-count
ste
0.1.1

code-spell-checker
str
2.20.5

even-better-toml
tam
0.19.2

vscode-status-bar-format-toggle
tom
3.1.1

intellicode-api-usage-examples
Vis
0.2.7

vscodeintellicode
Vis
1.2.30

application-insights
Vis
0.4.2

volar
Vue
1.8.8

vscode-todo-highlight
way
1.0.5

markdown-all-in-one
yzh
3.5.1

(25 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
vscaac:30438847
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
3biah626:30602489
f6dab269:30613381
a9j8j154:30646983
showlangstatbar:30737416
vsctsb:30748421
a2ce3375:30757347
pythonfmttext:30731395
pythoncmv:30756943
fixshowwlkth:30771522
hideindicator:30785051
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonnoceb:30797650
e537b577:30795824
dsvsc013:30795093
dsvsc014cf:30797590
cmakestatusbarv2:30779594

Here's a relevant section from the verbose logs:
[3596680:0730/134536.024:INFO:electron_api_web_frame_main.cc(235)] Attempt to setup WebFrameMain connection while render frame is disposed
Renderer process crashed - see https://www.electronjs.org/docs/tutorial/application-debugging for potential debugging information.
[main 2023-07-30T17:45:36.043Z] CodeWindow: renderer process gone (reason: crashed, code: -1073741502)
I was able to modify my startup arguments in Configure Runtime Arguments to add "disable-chromium-sandbox": true, which allows the application to startup normally, however I'd very much like assistance with repairing the chromium sandboxing as I understand that to be an important feature for security purposes.

Can you provide the crash logs following the steps at https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-a-crash-report, thanks!

Since updating and restarting a few times this week, this issue no longer seems to persist. Whatever impacted my computer to not support the sandbox appears to have been resolved even without the "disable-chromium-sandbox": true, setting. I'm going to close this and hope that the information on my temporary workaround helps anyone who encounters it in the future.


Documentaton: explain how to use as an swc plugin only

Hi there!!!
The project looks amazing!! Thanks for you effort creating this!
I was wondering how can we integrate this with our custom tools or bundlers, for example with rspack or rsbuild.
For example, in rsbuild you can configure swc plugins:

Would be really good to document/explain how to use it as a swc plugin outside of nextjs.
I assume that the plugin lives in stylex-rs-compiler,  maybe just need to document how to use it and what options we have there?
Again, thanks for the package!
Best.

Hi @GiancarlosIO,
Thank you for your interest in this project.
I opened a PR with the updated documentation of the SWC plugin. I hope it is now a little clearer how to work with it.
If there are any other suggestions or corrections, I am open to dialogue.
In the future, there are plans to write plugins for various bundlers and compilers. If you can help with this, I will be grateful.
P.S.,
If you need to extract CSS during build, then I recommend paying attention to @stylexswc/rs-compiler. It requires a little more configuration to work with, but it provides a more convenient way to interact with metadata, as it was specified in the RFC. Inside the compiler, the same SWC plugin code is used.

Hi @kimhung222,
Could you please provide the minimum reproduction of this bug. This may help in solving the problem.
By the way, with what version and what package does this behavior occur?

Hi @Dwlad90
You can reproduce by using your nextjs-app-router with the plugin boilerplate and then remove the import .global.css in layout.tsx. You can start Dev Server then change some styles, you will see some weird issues

I checked the StyleX issues and found that this is a known problem.
One of the possible solutions was proposed here, which was implemented in an alternative community plugin that solves this problem for the original library.
@SukkaW, maybe you would be interested in supporting this project and opening a PR with your plugin, or I could use your plugins code as a base for an existing one?
It should be quite simple after implementing your suggestion and using NAPI-RS as a bridge between JavaScript and Rust.

@SukkaW, maybe you would be interested in supporting this project and opening a PR with your plugin, or I could use your plugins code as a base for an existing one?

My stylex-webpack only needs a transformer function of (inputCode: string, inputSourceMap: object) => { code: string, map: object }. That's why I previously proposed a standalone transformer.
But Next.js' built-in swc loader is customized and doesn't support the standard swc plugin. So we need to use @swc/core.

My stylex-webpack only needs a transformer function of (inputCode: string, inputSourceMap: object) => { code: string, map: object }. That's why I previously proposed a standalone transformer. As long as it is possible to implement this shape of transformer it is doable.

Starting with version 0.3.0, the plugin uses the standalone transformer napi-rs with a built-in SWC, instead of the previous version with the swc-plugin.
At the moment, there are two nextjs plugins: standalone transformer and SWC plugin, which is deprecated and not recommended for use.
The transformer is written with same APIs as the StyleX babel plugin, so I think that it is possible to rewrite the plugin without any problems, using your approach. It is similar to your other plugin style9-webpack, which works stable for a long time.
Example of the standalone transformer usage:
  import { transform } from '@stylexswc/rs-compiler';

  // ... some code

  let { code, metadata, map } = transform(filename, inputCode, this.rsOptions);

  // ... some code

P.S.
How to solve this problem with the SWC plugin remains an open question.

BTW I encoutered a weird issue.
When I removed the global.css import from layout.tsx. The dev server didn't work, the compiler did not apply the style change. I must change next.config and restarted the dev server to see the style applied, Or I must use "use client" directive to see it works.
But when I import global.css into the layout.tsx. It worked again. This weird issues cost me someday to figure out. I think it would be better if you have instruction and warning to user to increase the experience with this plugin.

Hi @kimhung222,
A new @stylexswc/nextjs-plugin has been uploaded to NPM, you can try it starting with version0.5.0-rc.1


Does not work when map renderer is set to SVG?

Seems when the renderer option is set to svg() leaflet-textpath breaks.
Specifically line 78 in leaflet.textpath.js:
var svg = this._map._renderer._container;
This could either be a problem with leaflet not setting ._map._renderer or textpath reading ._container from the wrong field.

We had the same problem. All our polylines were in custom panes, so to solve the problem we added one of the polylines to the deafult leaflet polyline pane.

@JamesHearts, @Nttz if you replace all occurrences of  this._map._renderer._container with this._renderer._container it seems to fix this issue (moving my lines to the default pane was not an option).
Have not done extensive tests but seems to work so far. Only just started testing with this plugin so can't realy test much yet.

Can confirm this is still an issue for me, and has not been fixed.


Edge vsphere

This adds the edge-vsphere image type for x86_64 and
aarch64. It is based on the edge-raw-image but produces
a .vmdk image in order to upload the artifact to vSphere.
This image has Ignition support.
This has been moved from osbuild/osbuild-composer#3539
This pull request includes:

[x] adequate testing for the new functionality or fixed issue (I think so?)
[ ] adequate documentation informing people about the change such as

[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

From the latest review over the osbuild-composer repo:
Made changes on VMDK so that the NewVMDK function also takes a imgOstreePipeline *RawOSTreeImage, and changed the VMDK struct accordingly to accommodate that (it has a Pipeline instead of a RawImage) + cleanups related to that.
On ostree_raw we explicitly fail if a compression type is specified with the VMDK format.

Simply changed the commit message names since there is no longer an internal folder :smiling_face_with_tear:

Rebased on main and removed the manifest files from the PR.

The new image type depends on pulling an ostree commit, which I haven't set up yet (working on it now).  Can you add the new image type to the skip list here, please?
https://github.com/osbuild/images/blob/e61dd46dc12ae17910743e4432a4ab0ce2f0dc00/test/cases/generate-build-config#L24-L32

The new image type depends on pulling an ostree commit, which I haven't set up yet (working on it now). Can you add the new image type to the skip list here, please?
https://github.com/osbuild/images/blob/e61dd46dc12ae17910743e4432a4ab0ce2f0dc00/test/cases/generate-build-config#L24-L32

Rebased on main, added the  edge-vsphere image to that list and also added a missing , after edge-ami on the list above.

it looks like the edge-vsphere tests aren't being skipped yet: https://gitlab.com/redhat/services/products/image-builder/ci/images/-/jobs/4686776024#L6252

Yes, the manifest generation needs to happen for all image types before it decides which ones to skip, so there needs to be a config for it.  Sorry, forgot to mention it.  I'll add it now.


Set input value to use ISO format by default

If we don't add a layer of abstraction to format the date client side, the input value will be submitted directly to the server. As a result, I think we should not be using the display format but rather a standardized ISO-8601 format.
to: @jeffsee55 @airbnb/webinfra

Coverage increased (+0.04%) to 86.541% when pulling 920a0807c54d3a80fdf7acfee93f0cede3aea9a5 on maja-set-input-default-value-to-use-iso into fa3da300e911eff452cbd070a2983cc89f4a7593 on master.

I just realized this won't actually work for custom display formats.

@ljharb let's try again. Lol. This is messier, but also less broken. PTAL?

Coverage increased (+0.06%) to 87.228% when pulling 54af82241d6213e7789d0cb552f29b3ee31fbc80 on maja-set-input-default-value-to-use-iso into f931a82049186d79fd447996e7791f95c8451da4 on master.

Coverage increased (+0.06%) to 87.228% when pulling 54af82241d6213e7789d0cb552f29b3ee31fbc80 on maja-set-input-default-value-to-use-iso into f931a82049186d79fd447996e7791f95c8451da4 on master.

Coverage increased (+0.06%) to 87.228% when pulling 7eb9654f83dc0853fce00b9575315d5d50e813ad on maja-set-input-default-value-to-use-iso into d01cd54c5ab996e783991ce91c9c99b6cb02a005 on master.


Help with testing AD code

I've recently been writing a load of test code, initially for the EFMembershipService.  This uses an in-memory sqlite database, and now has pretty much 100% coverage on that service.
I have now split my tests into general IMembershipService stuff, and EF-specific stuff.
This has allowed me to create a test class for ADMembershipService, which would allow us to run the same tests against both providers, which could be great for finding subtle differences.
However, I've now come to the point where I'd need an AD server to work against.  What are the people who work on the AD code doing in this regard?   I installed AD LDS on a server here, but I'm not sure it's doing anything, nor how to configure it, nor if it's even what I need.
Clearly an AD test is never going to run in appveyor, but it could still be a useful thing to run interactively.
Any suggestions about a simple testing approach would be appreciated.

Does this help you? http://brockallen.com/2013/10/22/announcing-thinktecture-embeddedsts-a-simple-local-sts-for-asp-net-applications/

It might, if only I knew what it was!  Interesting anyway.

And i had posted this before: http://www.forumsys.com/tutorials/integration-how-to/ldap/online-ldap-test-server/

I've seen that one - I'll explore it properly.


BrokenBarHCollection has been removed from matplotlib in 3.7

mir_eval.display.piano_roll does not work for matplotlib>=3.7 because it uses BrokenBarHCollection that has been remove in  matplotlib 3.7 ( see https://matplotlib.org/stable/api/prev_api_changes/api_changes_3.7.0.html)

Should have been fixed in #380, display no longer used BrokenBarHCollection


Add edge list methods to get edgelist from graph objects

This commit adds 2 new methods, edge_list() and weighted_edge_list(),
to the PyDiGraph (and PyDAG) and PyGraph classes for getting an edge
list from a graph object. They return a list of tuples that represent
all the edges in the graph.

Coverage decreased (-0.6%) to 89.724% when pulling 066a45cbcbc3e4a910ce6934baf5ed367c86cfee on mtreinish:add-edgelist-methods into 12ecedfed7d5e053a1b3016f3336bd4244365938 on Qiskit:master.


Trigger breakpoint exception action in debug mode

The trigger action 0 (Raise a breakpoint exception) is legal in debug mode. This will be a problem if we:

enable debug for partition A
set trigger to raise exception in address of partition B

The adversary could take advantage of breakpoint exception action to tamper partition B, since the exception behavior is not subject to current debug control knob.
Proposal to mitigate:
Disallow the trigger being set to action 0, in debug mode.

Other actions seem fine. Even if the adversary leaves footprint in trigger, the action will not take effect.

This seems not necessary. There are two scenarios:

M-mode is under debug
M-mode is not under debug  but a specific supervisor domain is under debug

Scenarios 1 is everything goes - M-mode is the root of trust for the supervisor domains and the debugger has no restrictions.
For scenario 2, the triggers are context switched by the M-mode. When a supervisor domain executes, the M-mode will only have triggers corresponding to the active supervisor domain active. The external debugger cannot interfere here as a) when M-mode is doing the context switching (or any other work when in M-mode), the external debugger cannot interfere with the M-mode actions b) when a supervisor domain that does not have  external debug allowed is executing the external debugger cannot interfere and setup any triggers not authorized by M-mode as external debug is blocked. For supervisor domains where external debug is allowed, the debug mode can setup triggers for that supervisor domain. However, those triggers will not be active when any other supervisor domain executes since the M-mode will context switch them.

@AoteJin if the resolution @ved-rivos described above seems reasonable, then please ack so we can close this issue

The only scenario of interest is #2.
The fact is that triggers are normally not part of context switch. Moreover,  the hart could not program the trigger to enter debug mode. That is, the so-called context switch will be that security monitor scrubs all triggers and debugger reprogram triggers whenever it enters debug mode.
It turns out to be an awkward programming model.

Note that trigger context switch is needed anyway because the triggers may be setup by the supervisor domain itself for self hosted debug. A word switch needs to switch the triggers of one supervisor domain with another. This would be optimized by the implementation - for example, if the neither the incoming or outgoing supervisor domains had triggers programmed by self hosted debug and neither had supervisor domain external debug enabled - then no switching of triggers is needed. This world switch will need to switch a bunch of other state such as the HPM CSRs, Control Transfer Records, all of the S* CSRs, x registers, f registers, v registers, etc.

Please note that the hart cannot program trigger action to enter debug mode. That is, the hart cannot restore trigger context.
Trigger is machine mode resource in RISV-V. Self-host debugger leverages ebreak other than trigger.

Please note that the hart cannot program trigger action to enter debug mode. That is, the hart cannot restore trigger context.

The triggers are programmable using the Trigger registers accessed using the Sdtrig CSRs by selecting the triggers using tselect. The Sdext CSRs are accessible from M-mode and Debug Mode. The scontext and hcontext are also accessible at lower privileges. The root domain security manager (RDSM) executes in machine mode. The RDSM is the entity that provides the SBI for the supervisor domains (SDs) to program triggers and is the entity that does world switching of the SD. The RDSM as part of the world switch will context switch the trigger registers.

I think Aote is referring specifically to the tdata1.dmode bit, which can only be set to 1 from debug mode, and, when set, causes all CSRs associated with that trigger to be writable only from debug mode.  If the debugger sets that bit, the RDSM can no longer modify that trigger.  Maybe the secure debug extension needs to alter this behavior to say that all modes above that enabled for debug can write to triggers with dmode=1?

Yes, that was the expectation that when M-mode external debug is not enabled the dmode=1 triggers should not allowed. But that should not require restricting action=0 as that would disallow self-hosted debug in SDs.

This will be a problem if we:

enable debug for partition A
set trigger to raise exception in address of partition B

When do you execute the operation 2?
In secure debug, partition may only set the triggers within its memory regions (text, data, etc).
Therefore, partition A should not set trigger to raise exception in address of partition B, right ?

Summarizing the expected external debug security behaviors:

When medbgen is 0 and privilege is M
a) dmode field of triggers is read-only zero.
b) Abstract commands and haltreq from external debugger stay pending while privilege is M
c) All trigger matching is suppressed
When  SDEDBALW=0 and medbgen=0 and privilege is less than M
a) Abstract commands and haltreq from external debugger stay pending.
When  SDEDBALW=1 and medbgen=0 and privilege is less than M
a) haltreq can transition to Debug Mode.
b) Abstract commands and program buffer execution can access S and unprivileged CSRs.
c) Access to M-mode CSRs other than the Sdtrig CSRs is not allowed.
d) Memory accesses occur with either S or U privilege (as if MPRV or aamvirtual is 1 ).

Thanks for the great summary!
The point is exactly with 3.c. Let’s say only partition A is debuggable by external debugger and the external debugger can legally set trigger to:

Enter debug mode in partition A
Exception in partition A
Enter debug mode in partition B
Exception in partition B
The case 1,2,4 can take effect when there is no trigger context switch.
However the case 1 is not able to be context switched by hart (case 3 won’t take any effect, so don’t care)
That’s why it is suggested to disallow debug mode set trigger to trap.

I dont understand what the issue with 3.c. Orthogonal to context switching of triggers, when M-mode debug by external debugger is not allowed, external debugger should not be allowed to modify M-mode CSRs.

In case #3, I think we want to say that M-mode can write to tdata* when tdata1.dmode=1.  That ensures that the RDSM can switch the trigger state established by the S-mode debugger.

The behavior for medbgen=0 is covered by 1a...The 3c is additive to 1a.

Beeman suggested a change to 1a to instead of requiring dmode to be ROZ to allow M to write to dmode=1 triggers when medbgen is 0. Updating the summary:

When medbgen is 0 and privilege is M
a) M-mode can read and write triggers - including triggers with dmode=1 - without restrictions
b) Abstract commands and halt request from external debugger stay pending while privilege is M
c) All trigger matching is suppressed (similar to how MIE or MTE would suppress them)
When SDEDBALW=0 and medbgen=0 and privilege is less than M
a) Abstract commands and halt request from external debugger stay pending.
When SDEDBALW=1 and medbgen=0 and privilege is less than M
a) Halt request can transition to Debug Mode.
b) Abstract commands and program buffer execution can access S and unprivileged CSRs.
c) Access to M-mode CSRs other than the Sdtrig CSRs is not allowed.
d) Memory accesses occur with either S or U privilege (as if MPRV or aamvirtual is 1 ).

so case 1 above needs to be specified in the broader secure ext. debug spec - (1a is the main behavior change).
case 2 and 3 are specific to supervisor domains and should be added to this spec
please correct if I am interpreting this incorrectly.

Agree that 2 and 3 behavior should be specified as part of SEDBGALW description. Something like the following:

When M-mode external debug is enabled, all supervisor domains may also be debugged by an external debugger irrespective of the configuration held in SEDBGALW field of msdcfg register.
When M-mode external debug is disabled, whether execution at privilege modes less than M may be debugged by an external debugger depends on the configuration held in SEDBGALW field of msdcfg register.

When SDEDBALW=0, external debug is disallowed. Abstract commands and halt request from the debug module are suppressed and stay pending.

When SDEDBALW=1 then external debug of privilege modes less than M is allowed, and:
** A halt request may transition the hart to Debug Mode.
** Abstract commands and program buffer execution can access state of privilege modes less than M.
** Read and Write of Sdtrig CSRs is allowed.
** Debugger memory accesses occur with either S or U privilege (as if aamvirtual is 1 and MPP != M-mode).

I think we are finally on the same page and acknowledge the issue.

a) M-mode can read and write triggers - including triggers with dmode=1 - without restrictions

Beeman's suggestion is a valid approach. But it actually mandates all security monitor implementation to include trigger save/restore which leaves the responsibility to SM implementor , and it could be costly when trigger number scales up.
I would propose another solution. Instead of making dmode writable in machine mode by hart, the external debug security could prohibit debug mode to set trigger to raise exception.
The upsides are:

SM do not need to save/restore triggers if self-hosted debugger do not use trigger (with ebreak only)
It meets the the need of external debugger and self-hosted debugger with minimum effort
It more secure to prohibit than allow it. (M mode write to dmode/action to enter debug mode is a potential DoS attack surface)

SM do not need to save/restore triggers if self-hosted debugger do not use trigger (with ebreak only)

We should not preclude self-hosted debugger the ability to do data breakpoints or code breakpoints using triggers.

It doesn't rule out the self-hosted debugger using trigger. It just points out a common practice that self-hosted debuggers do (e.g. ptrace uses ebreak for watchpoints and breakpoints). In this cases, trigger context switch can be saved.

It meets the the need of external debugger and self-hosted debugger with minimum effort

The security monitors will need to context switch triggers as part of world switch. This is no more effort that switch any other CSRs such as HPMs.

It is not generally true. HPM is only visible to sub-machine mode if it is enabled in mcounteren. Moreover, trigger context switch overhead could be 6x times of HPM (assuming 64 triggers).

It more secure to prohibit than allow it. (M mode write to dmode/action to enter debug mode is a potential DoS attack surface)

Please explain the DoS attack by M-mode switching triggers with dmode=1. The very act of allowing external debug for any SD is however a DoS attack because a debugger can enter debug mode from the debug allowed SD and then never resume blocking execution of all other SDs. Due to this, SMs will mostly not support running any SD with external debug allowed in production mode as a policy. The ability to debug a SD using external debug would have to be explicitly authorized as a policy to avoid such cases in production. But that is orthogonal.

Just like the statement "machine mode shall not enable debug for machine mode itself", the glitching could happen during trigger context switch or when self-hosted debugger uses trigger.

It is not generally true. HPM is only visible to sub-machine mode if it is enabled in mcounteren. Moreover, trigger context switch overhead could be 6x times of HPM (assuming 64 triggers).

If HPM are made available to lower mode - and there is mcounteren and the Smcdeleg that were fast tracked for a reason - then they need to be switched. If they were not delegated then they dont need to be switched. Similarly triggers that are used for self hosted debug need to be switched and if a  SD is under external debug the triggers need to be switched. If the SD is not under external debug or is not running a self hosted debugger then the triggers do not need to be switched. The cost of trigger context switch is not material - in production use there will be no SD with external debug enabled and running gdb in the OS is rare.

Just like the statement "machine mode shall not enable debug for machine mode itself", the glitching could happen during trigger context switch or when self-hosted debugger uses trigger.

Glitching can be done at various times and to affect variety of security states - for instance when programming MTT for memory isolation, when switching satp of the supervisor domain, or when switching GPRs of the supervisor domain. It is likely more productive to glitch settings of say satp or stvec than glitching triggers. Glicthing could be used to affect the privilege mode itself. But this is straying away from the topic and not relate to triggers.

all - please see the PR #35 queued related to this issue.

@ved-rivos I am confused with your statement. It is something like I was saying preventing debug mode to raise exception is 10 points better than making dmode writable by M-mode, while you arguing that it is only 5 points better.
But overall, if it is better and we should buy in the better one. If you don't think so, probably we could focus on the aspects that making dmode writable overweights?

But overall, if it is better and we should buy in the better one. If you don't think so, probably we could focus on the aspects that making dmode writable overweights?

M-mode being able to write dmode=1 triggers is a functional requirement. Otherwise the M-mode will not be able to context switch between a external debug enabled SD and a non-external debug enabled SD. Consider two SDs - A and B - where A is external debug enabled and B is not. B has triggers established by self hosted debug and A has triggers established by external debug. When switching from B to A and vice versa, the RDSM needs to replace the triggers of A with B or B with A.
Given that 1 is functionally a requirement, additionally restricting breakpoint action to be written by an external debugger is not required.
On the argument that RDSM could save time switching the triggers e.g., leave the external debug triggers of A in place when running B, implies that when B actually requests a self hosted trigger the RDSM has to lazily go swap the external debuggers triggers. This adds complexity to RDSM since now it needs to remember which SD ran before B to do this action.
Lazy switching of triggers adds additional burdens to ensure that even if the triggers are suppressed that they dont have any side effects - e.g. if the hit bits update on due to A's triggers being left in place when B executes - even if it does not cause a debug mode entry or breakpoint, it is side channel because it lets the external debugger know - through the hit bits - which trigger was matched in B. The original described scenario "enable debug for partition A; set trigger to raise exception in address of partition B" - implies that matching triggers and updating hit bits is okay - as long as the debug mode entry is suppressed which is not true.

Considering external debugging of any SDs is not a production scenario and context switch time when a SD is under debug is not an issue and the ability to write dmode=1 is a MUST have requirement for functionally being able to switch triggers of a external debug enabled SD with those of a non external debug enabled SD, adding further ISA to restriction action=0 being not programable when done by debug mode is not necessary.

@joxie @AoteJin please see PR #35
if it looks ok we can close this issue and merge that PR.

closing since proposed spec change is included in PR #35 PTAL


Add proper STM tracker detection

I fixed a few things in the STM tracker detection:

All ST2 versions from 2.2 to 2.4 write the version number as 2.21, so I changed the text to Scream Tracker 2.2 - 2.4 if the minor version is at least 21.
Added separate tracker names for BMODSTM, WUZAMOD!, and SWavePro in the "tracker name" field. Other values are treated as "Unknown".

I'm not very familiar with C++, so feel free to let me know if I messed up or could have done something better.

Looks good in general. However, as this string should generally identify a software, "WUZAMOD!" is the odd one out here: BMOD2STM and SoundWave Pro are clearly identifiable programs, but I'm not quite sure which program uses the "WUZAMOD!" signature. No matter how much I search, I cannot find any references to which program would write such files, just various software packages announcing that they now support these magic bytes.

Added in r21810. I have my doubts the WUZAMOD mystery will be lifted anytime soon, so let's just keep it as-is for now and revisit it when there is more information available.


[CAFV-217] Support TKG 1.6.1 vm creation with CPI 1.4 common core

Description
Please provide a brief description of the changes proposed in this Pull Request
This PR utilizes CPI 1.4 common core and supports TKG 1.6 vm creation.
Checklist

[ x] tested locally
[ n/a] updated any relevant dependencies
[ n/a] updated any relevant documentation or examples

API Changes
Are there API changes?

[ ] Yes
[ x] No
@lzichong @sakthisunda @Anirudh9794

This change is

As a note, some PR's above were cherry-picked to match new function definitions in CPI 1.4 common core


运行出错，作者是什么环境运行的。

X86 win10电脑安装vmare虚拟ubuntu22,
python3.10
pip22
git clone项目，pip安装, playwright install，然后python3 ./mail.py出错了
root@debian:~/Electricity-Tracker# python3 ./main.py
Traceback (most recent call last):
File "/root/Electricity-Tracker/./main.py", line 58, in
print(main_instance.run(retry_times=retry_times, retry_interval=retry_interval))
File "/root/Electricity-Tracker/./main.py", line 42, in run
amount = self.scraper.fetch_data()
File "/root/Electricity-Tracker/scraper/electricity_scraper.py", line 35, in fetch_data
self.loading_slide()
File "/root/Electricity-Tracker/scraper/electricity_scraper.py", line 86, in loading_slide
self.page.locator("canvas").nth(0).screenshot(path='slide.png')
File "/usr/local/lib/python3.10/dist-packages/playwright/sync_api/_generated.py", line 17582, in screenshot
self._sync(
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_sync_base.py", line 109, in _sync
return task.result()
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_locator.py", line 530, in screenshot
return await self._with_element(
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_locator.py", line 115, in _with_element
handle = await self.element_handle(timeout=timeout)
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_locator.py", line 315, in element_handle
handle = await self._frame.wait_for_selector(
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_frame.py", line 322, in wait_for_selector
await self._channel.send("waitForSelector", locals_to_params(locals()))
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_connection.py", line 61, in send
return await self._connection.wrap_api_call(
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_connection.py", line 482, in wrap_api_call
return await cb()
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_connection.py", line 97, in inner_send
result = next(iter(done)).result()
playwright._impl._api_types.TimeoutError: Timeout 30000ms exceeded.
=========================== logs ===========================
waiting for locator("canvas").first
root@debian:~/Electricity-Tracker#

X86 win10电脑安装vmare虚拟ubuntu22, python3.10 pip22 git clone项目，pip安装, playwright install，然后python3 ./mail.py出错了
root@debian:~/Electricity-Tracker# python3 ./main.py
Traceback (most recent call last):
File "/root/Electricity-Tracker/./main.py", line 58, in
print(main_instance.run(retry_times=retry_times, retry_interval=retry_interval))
File "/root/Electricity-Tracker/./main.py", line 42, in run
amount = self.scraper.fetch_data()
File "/root/Electricity-Tracker/scraper/electricity_scraper.py", line 35, in fetch_data
self.loading_slide()
File "/root/Electricity-Tracker/scraper/electricity_scraper.py", line 86, in loading_slide
self.page.locator("canvas").nth(0).screenshot(path='slide.png')
File "/usr/local/lib/python3.10/dist-packages/playwright/sync_api/_generated.py", line 17582, in screenshot
self._sync(
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_sync_base.py", line 109, in _sync
return task.result()
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_locator.py", line 530, in screenshot
return await self._with_element(
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_locator.py", line 115, in _with_element
handle = await self.element_handle(timeout=timeout)
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_locator.py", line 315, in element_handle
handle = await self._frame.wait_for_selector(
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_frame.py", line 322, in wait_for_selector
await self._channel.send("waitForSelector", locals_to_params(locals()))
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_connection.py", line 61, in send
return await self._connection.wrap_api_call(
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_connection.py", line 482, in wrap_api_call
return await cb()
File "/usr/local/lib/python3.10/dist-packages/playwright/_impl/_connection.py", line 97, in inner_send
result = next(iter(done)).result()
playwright._impl._api_types.TimeoutError: Timeout 30000ms exceeded.
=========================== logs ===========================
waiting for locator("canvas").first
root@debian:~/Electricity-Tracker#

看上去是网络问题，可以多试几次

本issue长时间未回复，暂时关闭，如果还有疑问可以再次open或者发新issue


Add speaker images and update devent.toml file

Add speaker images and add speaker info into the devent.toml file.

Thanks @domoberzin
Can you also add the Twitter handles for the speakers? (you can do this in a follow up PR)


Minified version not updated?

It looks like minified version has not been updated to 2.3.4, nor on github, nor on npm.

I installed version 2.3.4 from npm and also found the minified versions to be at version 2.3.3. I don't think this can be fixed.
However, I recommend checking out the beta of vex 3, which you can get with npm i<EMAIL_ADDRESS>This repo has been updated, as well as all of the docs. Let me know what you think!


Disable console logs

Is it possible to disable the console logs?

Which console.logs are you talking about?

It's the browser's console log. The one you get on opening the app's dev tools > console.

Can you please post a screenshot what you exactly mean?
Sentry does't do any console.log by default, only if you enable debug: true

@akashnimare These consoles are empty, so which logs exactly are you referring to? Ideally, could you please point to the origin of the log so we can figure out where it might be coming from (the file and line number on the right of a log, once it's there)?
Thanks!

That's just for showing the console thing. Can you share your email or something so that I can directly share the sentry logs and other info as well?

@akashnimare in case you're asking how to prevent the entire developer tools window from showing, this is not related to the Sentry SDK. Electron does this.

@akashnimare sure thing, please send them over to<EMAIL_ADDRESS>

in case you're asking how to prevent the entire developer tools window from showing, this is not related to the Sentry SDK. Electron does this.

@untitaker ah, no this is not what I want. I'll make myself a bit more clear in the email.

We have just released v3.0.0 of the SDK which includes a lot of changes and improvements since this issue was opened.
If you can still reproduce this with v3, please open a new issue and I'll look into it.


Controls always hide on fullscreen

The autoHideControls feature is not working properly on fullscreen mode.
When setting the pin button to false it will hide the controls and they wont show anymore.
Also this needs some improvement to handle show / hide interactions on fullscreen mode

I'm taking this one 🤓

Fix: https://github.com/btzr-io/Villain/pull/147


couldint Open Blob Containers

Unable to retrieve child resources.
Details:
["RestError:AuthorizationPermissionMismatchThis request is not authorized to perform this operation using this permission.\nRequestId:360e6e5d-401e-00ec-4def-7e36ef000000\nTime:2020-08-30T17:02:37.3294355Z"]

@AmeenMS what type of resource are you trying to access?

blob container (ADLS Gen2)
blob container (non-ADLS Gen2)
queue
file share
table

Closing due to lack of follow-up by the original issue author. Please open a new issue if you are still having problems.


[QUESTION] Does connection string support links?

What if I prefer to store my db file in a cloud, how should I provide connection string if possible?

@a-a-k This is currently not supported. LiteDB only supports local files.


is it possible to read an internal md file and extracte?

Hi,
Thanks for the great work. Do help me a lot.
I am wondering how to make it read the internal links and give feedback, like:
Please read [[tempfile]] and give me the abstract.

Thanks for the advice.

https://docs.text-gen.com/_notes/3-+Templates/subpages/Handlebar+Templates#`read`


windows-2019.box could not be found

running make all or make 2 errors out with
Bringing machine 'winw1' up with 'virtualbox' provider...
==> winw1: Box './windows-2019.box' could not be found. Attempting to find and install...
    winw1: Box Provider: virtualbox
    winw1: Box Version: >= 0
The box './windows-2019.box' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Vagrant Cloud, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://vagrantcloud.com/./windows-2019.box"]
Error: The requested URL returned error: 404

It looks like #112 introduced this file but doesn't add it to the repo.  What is an an example of what this file looks like?
/sig windows
/cc @knabben @FriedrichWilken

Active

start


Incorrect SpellID string translation

When creating a new macro or attempting to import an existing macro the spell ID of certain abilities is being incorrectly translated leading to the wrong ability being saved.
Examples I have found are:
Backstab is being saved as Sinister Strike.
Shadowstrike is being saved as Ambush.

Yep - its actually not a bug.  GSE stores the BASE Ability.  It has been doing this for procs and talents for a while.  It now uses Blizzards internal library to find that out and it works across specs.  When you /cast Sinister Strike it will use Backstab based on your spec.  Does the same thing with Flash Heal and Shadowmend etc.  This was introduced in #724


How do I close not toggle the reveal?

The only method I see is:
self.revealViewController().revealToggleAnimated(true)
But this can also open the menu. What if I only want to close it?

 revealViewController().setFrontViewPosition(.left, animated: true)


Restrict to only GPT-3.5?

Thanks for this awesome project.
I've looked at settings and environment variables (and also some code), but can't find a way to restrict Chatbot UI to only use gpt-3.5-turbo (not GPT-4). I'm planning on having a publically available chatbot for my organization, and limiting to gpt-3.5-turbo would make it fit better within our budget.
I'm not sure whether this is a support request or a feature request, but I'm adding it anyway.

All you need to do is to comment out the gpt-4 references in file /types/openai.ts
See below:
import { OPENAI_API_TYPE } from '../utils/app/const';
export interface OpenAIModel {
id: string;
name: string;
maxLength: number; // maximum length of a message
tokenLimit: number;
}
export enum OpenAIModelID {
GPT_3_5 = 'gpt-3.5-turbo',
GPT_3_5_AZ = 'gpt-35-turbo',
// GPT_4 = 'gpt-4',
// GPT_4_32K = 'gpt-4-32k',
}
// in case the DEFAULT_MODEL environment variable is not set or set to an unsupported model
export const fallbackModelID = OpenAIModelID.GPT_3_5;
export const OpenAIModels: Record<OpenAIModelID, OpenAIModel> = {
[OpenAIModelID.GPT_3_5]: {
id: OpenAIModelID.GPT_3_5,
name: 'GPT-3.5',
maxLength: 12000,
tokenLimit: 4000,
},
[OpenAIModelID.GPT_3_5_AZ]: {
id: OpenAIModelID.GPT_3_5_AZ,
name: 'GPT-3.5',
maxLength: 12000,
tokenLimit: 4000,
},
// [OpenAIModelID.GPT_4]: {
//   id: OpenAIModelID.GPT_4,
//   name: 'GPT-4',
//   maxLength: 24000,
//   tokenLimit: 8000,
// },
// [OpenAIModelID.GPT_4_32K]: {
//   id: OpenAIModelID.GPT_4_32K,
//   name: 'GPT-4-32K',
//   maxLength: 96000,
//   tokenLimit: 32000,
// },
};

Many thanks! (bows)

I have the opposite problem - only 1 model is available in the drop-down menu for models in the UI. I just cloned the repo yesterday and haven't commented out anything.

Hi, I have the 4.0 API, and I followed your method to modify the code in the GitHub repository. Now the web page correctly displays the GPT-4 model, and I've successfully engaged in conversation with it. However, it keeps insisting that it's GPT-3, and it can't answer the current time. Am I missing some sort of setting?

@Itangalo You can use LiteLLM to fix your issue: https://github.com/BerriAI/litellm
LiteLLM - allows you to use any LLM as a drop in replacement fot gpt-3.5-turbo + You can set a $ budget per user or per session
from litellm import BudgetManager, completion
budget_manager = BudgetManager(project_name="test_project")
user = "1234"

# create a budget if new user user
if not budget_manager.is_valid_user(user):
    budget_manager.create_budget(total_budget=10, user=user)

# check if a given call can be made
if budget_manager.get_current_cost(user=user) <= budget_manager.get_total_budget(user):
    # call gpt-3.5
    response = completion(model="gpt-3.5-turbo", messages=[{"role": "user", "content": "Hey, how's it going?"}])
    budget_manager.update_cost(completion_obj=response, user=user)
else:
    response = "Sorry - no budget!"


Release version 0.1.2

mrack now generates output with modules for:
ansible-inventory
pytest-multihost
implemented static provider to create resource from static VMs
added tests for static provider
list and ssh actions
added some minor fixes

Signed-off-by: Tibor Dudlák<EMAIL_ADDRESS>

Thanks Tibor.
I'd do minor changes:
New features:

mrack now generates output with modules for:
ansible-inventory
pytest-multihost
added a static provider to create resources from static VMs
added list action to print resources from DB
added ssh action to connect quickly to VMs in DB

Bug fixing and testing:

added tests for static provider
added various minor fixes

Was thinking it as a text for an official release.
Do you plan to click the "releas" button in GitHub and created tag, etc... ?

Thanks Tibor.
I'd do minor changes:
New features:
* mrack now generates output with modules for:
  ansible-inventory
  pytest-multihost

* added a static provider to create resources from static VMs

* added list action to print resources from DB

* added ssh action to connect quickly to VMs in DB

Bug fixing and testing:
* added tests for static provider

* added various minor fixes

Was thinking it as a text for an official release.

Updated

Do you plan to click the "releas" button in GitHub and created tag, etc... ?

Yes that's correct


updated owner tag

since #0001 is your new tag and that I guess
Please describe the changes this PR makes and why it should be merged:
Semantic versioning classification:

[ ] This PR changes the adds extra commands to the bot
[x ] This PR improves existing commands
[ ] This PR only includes non-code changes, like changes to documentation, README, or images to memes / reactions

Oh woops I missed that when I changed it. Thanks!

no prob mate~


Emit cluster version in monitoring

Follow on from PR 321 as the history was messed up

Please see PR 377 for a ready to review & merge PR.


Add "quoted newlines" optional config when creating GBQ table

Added quoted newlines" optional config: allow_quoted_newlines

allow_quoted_newlines: Indicates whether to allow quoted data sections that contain newline characters in a CSV file. The default value is false. (Read more: https://stackoverflow.com/a/33698962/8884544)

Thanks, @waligob .
I think we also need to create a new release version?

Thanks, @waligob . I think we also need to create a new release version?

That's right. https://github.com/phillymedia/vestapol/pull/53 will bump the version. After that is merged, we can create a release to publish the new artifact to PyPi. Finally, we can update the package in inq-data-resources by running poetry update vestapol


11/18/2018 18:52 : Create Pull Request for branch master -> prTesting1_2018111818

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestRef1.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.


WIP: Reduce using reporootpath directly

This PR introduces a new sub package modules/git/storage.

related to #25070


Invalidate CloudFront cache after production builds

The default (and current) TTL for objects in the CloudFront cache is 1 day, which means that users could be seeing day-old content.  We need to implement a way to invalidate the cache after each production build, but no on other builds, like ones for PRs.

This is hopefully addressed by PR #107, but we won't know for sure until the PR is merged.

The command to invalidate the cache is returning this error:
"AWS key missing in the configuration file (RuntimeError)"
It may be that I created the encrypted auth file incorrectly somehow.

This is working now I think. Closing.


New worker fails to connect until master restart

Issue description

When existing worker tries reconnecting to master occasionally an exception is shown on master host:

locust-1  | Traceback (most recent call last):
locust-1  |   File "src/gevent/greenlet.py", line 908, in gevent._gevent_cgreenlet.Greenlet.run
locust-1  |   File "/opt/venv/lib/python3.10/site-packages/locust/runners.py", line 1090, in client_listener
locust-1  |     self.clients[msg.node_id].state = STATE_SPAWNING
locust-1  |   File "/opt/venv/lib/python3.10/site-packages/locust/runners.py", line 639, in __getitem__
locust-1  |     return self._worker_nodes[k]
locust-1  | KeyError: 'worker.perf.local_881aaac5d5124549a12e8ccc01c3d36b'
locust-1  | 2023-02-20T12:22:08Z <Greenlet at 0x7fa740e77f60: <bound method MasterRunner.client_listener of <locust.runners.MasterRunner object at 0x7fa740dea4a0>>> failed with KeyError
locust-1  |
locust-1  | [2023-02-20 12:22:08,909] locust.perf.local/CRITICAL/locust.runners: Unhandled exception in greenlet: <Greenlet at 0x7fa740e77f60: <bound method MasterRunner.client_listener of <locust.runners.Ma
sterRunner object at 0x7fa740dea4a0>>>
locust-1  | Traceback (most recent call last):
locust-1  |   File "src/gevent/greenlet.py", line 908, in gevent._gevent_cgreenlet.Greenlet.run
locust-1  |   File "/opt/venv/lib/python3.10/site-packages/locust/runners.py", line 1090, in client_listener
locust-1  |     self.clients[msg.node_id].state = STATE_SPAWNING
locust-1  |   File "/opt/venv/lib/python3.10/site-packages/locust/runners.py", line 639, in __getitem__
locust-1  |     return self._worker_nodes[k]
locust-1  | KeyError: 'worker.perf.local_881aaac5d5124549a12e8ccc01c3d36b'

After that no new workers are able to connect to master.
Master restart is required.

Fix proposal
runners.py:1090:
try:
    self.clients[msg.node_id].state = STATE_SPAWNING
except KeyError:
    logger.warning(f"Got spawning message from unknown worker {msg.node_id}. Asking worker to quit.")
    self.server.send_to_client(Message("quit", None, msg.node_id))

Also encounter same issue, in my scenario, when I add a bunch of new workers to an exist test run, the issue occurs, BTW, --enable-rebalancing is enabled in my master.

Sounds like a good fix, please make a PR!

https://github.com/locustio/locust/pull/2309


Tolerate a zero length ticket nonce

TLSv1.3 draft-21 requires the ticket nonce to be at least 1 byte in length.
However NSS sends a zero length nonce. This is actually ok because the next
draft will allow zero length nonces anyway, so we should tolerate this.

I already pushed this before @kaduk's comment, so closing. If there are any follow on actions it will have to be a different PR.


Switch to Virtual First

This switches to virtual first delivery for our materials. The existing
ILT courseware is moved to Legacy content. The Virtual courseware is
promoted to being the way that we deliver courses, with two variants.
The only difference between local/virtual deliveries right now is the
one slide about introducing the virtual platform. But maintaining the
two variants means that we can re-chunk as needed to meet the delivery
requirements.
This should be released on Wednesday or Thursday, so no trainings are
affected.
TRAINTECH-1563 #resolved #time 1h

tested at http://<IP_ADDRESS>, but we should do the run-through before release


How to get audio data to use from microphone.

Hi, I'm working on iOS application which is written in Swift 5.
I'm looking to create A weight bandpass filter.
My query is that currently, I am receiving audio samples through a microphone using tap.
How can I use a High bandpass filter on an audio stream coming from the microphone to evaluate dB value?

Hi, Novocaine has an example of how to receive audio samples from the microphone.
Applying a bandpass filter (example in the README) and measure the level like this: https://github.com/bartolsthoorn/NVDSP#measure-db-level-ranging-from--510f-to-00f


Deprecate g:completion_max_items in favour of 'pumheight'

g:completion_max_items is equivalent to the native option 'pumheight'.
See :h 'pumheight'.

Don't know about pumheight until today...Thanks for the information! Will deprecate that.

Close by #111


Mouse cursor triggers highlight after using up/down keys on top/bottom suggestion

I'm able to reproduce this one in the Scrollable container example at http://react-autosuggest.js.org/ on chrome for mac and windows
Steps to reproduce the issue

Focus on the input field
Move cursor to somewhere in the list of countries
Press up twice with the top suggestion selected or down with the bottom suggestion selected

Observed behaviour: Highlighted suggestion becomes the suggestion under the current position of the mouse cursor
Expected behaviour: Mouse should not affect the highlighted suggestion

@greglboxer  Hi, I have a same issue like you. Did you resolve this problem eventually? Thank you. #687

Is there any update on this issue or any workaround to solve this issue?


[Bug] Got possible overflow when edging the maximum size of ZSM.

System:
AuthenticAMD_-_AMD64_Family_25_Model_33
GPU Irrelevant.NULL
Windows 10 Pro 22H2 (19045.3448)
Windows Feature Experience Pack 1000.19044.1000.0
Software:(CRC32)
MELODIUS.PRG (69bb7449)
x16emu.exe (57683F78) win64.R44
Symptom:
After loading and when loading the data, no more respond to keyboard "Space Bar"  input, and Break key will not drop into the BASIC.
But it will keep playing, and notes sounds fine.
How to repeat:
Unzip attachment, run following in PowerShell
".\x16emu.exe -fsroot .\melodius\ -ram 2048"
Then enter LOAD "MELODIUS.PRG", navigate to ZSM folder, load "out2.zsm".
There you have it.
My guess is it overflowed somewhere and wiped something out. When loading "out.zsm" which is only 20KiB smaller, it works fine.
I don't think it's the emulator hates AMD CPU, but there has been some that does, so just in case.

cx16emu.7z.zip

A new file, this time it will just lock up, or play very slowly depends on mood.
out.overflow2.zsm.7z.zip

At 2014KiB, everything works Hunkydory.
out.candi4.7z.zip

I'll release candidate 4. 😂


Ricorx7 fork

These changes were very close to Tawns that I merged into #dev. I added the joystick install docs here. https://github.com/wroscoe/donkey/blob/dev/docs/parts/controllers.md


get_add_actions(False) Throws index out of bounds

Environment
Delta-rs version: 0.10.1
Binding: Python
Environment:

Cloud provider: None
OS: Windows, could also repo on Linux (Azure Websites)
Other:

Bug
What happened:
import deltalake

d = deltalake.DeltaTable("data/delta/mail/path")
print(d.get_add_actions(False))

throws:
thread '<unnamed>' panicked at 'index out of bounds: the len is 0 but the index is 0', rust\src\table_state_arrow.rs:494:39
stack backtrace:
   0:     0x7ffde2af5ebc - BrotliDecoderVersion
   1:     0x7ffde2b1f38b - BrotliDecoderVersion
   2:     0x7ffde2af1069 - BrotliDecoderVersion
   3:     0x7ffde2af5c6b - BrotliDecoderVersion
   4:     0x7ffde2af8729 - BrotliDecoderVersion
   5:     0x7ffde2af83df - BrotliDecoderVersion
   6:     0x7ffde2af8c2e - BrotliDecoderVersion
   7:     0x7ffde2af8b1d - BrotliDecoderVersion
   8:     0x7ffde2af6ae9 - BrotliDecoderVersion
   9:     0x7ffde2af8820 - BrotliDecoderVersion
  10:     0x7ffde2c52965 - BrotliDecoderVersion
  11:     0x7ffde2c52ae4 - BrotliDecoderVersion
  12:     0x7ffde01ddcb2 - PyInit__internal
  13:     0x7ffddfd1f43f - BrotliDecoderSetParameter
  14:     0x7ffddfd0d7be - BrotliDecoderSetParameter
  15:     0x7ffddfd16731 - BrotliDecoderSetParameter
  16:     0x7ffe19ad6282 - PyUnicode_ToDecimalDigit
  17:     0x7ffe19a4f52b - PyObject_Vectorcall
  18:     0x7ffe19a508d4 - PyEval_EvalFrameDefault
  19:     0x7ffe19acbbd3 - PyMapping_Check
  20:     0x7ffe19acb453 - PyEval_EvalCode
  21:     0x7ffe19aef83e - PyArena_Free
  22:     0x7ffe19aef7ba - PyArena_Free
  23:     0x7ffe19be4666 - PyThread_tss_is_created
  24:     0x7ffe19b3ac89 - PyRun_SimpleFileObject
  25:     0x7ffe19b71a18 - PyRun_AnyFileObject
  26:     0x7ffe19b7165b - PySys_GetSizeOf
  27:     0x7ffe19b71517 - PySys_GetSizeOf
  28:     0x7ffe19b0442c - Py_RunMain
  29:     0x7ffe19b042bd - Py_RunMain
  30:     0x7ffe19a8e76d - Py_Main
  31:     0x7ff7a1371230 - <unknown>
  32:     0x7ffe970f7614 - BaseThreadInitThunk
  33:     0x7ffe984e26b1 - RtlUserThreadStart
Traceback (most recent call last):
  File "c:\Projects\DataHub\DataAnalyticsAPI\test.py", line 4, in <module>
    print(d.get_add_actions(False))
          ^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Projects\DataHub\DataAnalyticsAPI\.venv\Lib\site-packages\deltalake\table.py", line 612, in get_add_actions
    return self._table.get_add_actions(flatten)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pyo3_runtime.PanicException: index out of bounds: the len is 0 but the index is 0

The same does not happen with flatten=True
What you expected to happen:
Well, it should work ;)

@aersam thanks for reporting. Is this table empty?

No. But it has column mapping, could that be the issue? The stats contains stats for the physical column names, it seems. I do not query the table using delta-rs, but I need the metadata from it (I use the metadata to generate some sql for a system that supports parquet but not delta)

Ok, thats sad ;) I can live with it for now as it works with flatten=True, however I think there are valid use cases for using delta-rs mostly for metadata. Eg, I could completely write a duckdb view with column mapping and deletion vectors support by just having the metadata complete from delta-rs.

I think there are valid use cases for using delta-rs mostly for metadata

I don't disagree. We might be able to fix this function to work for a wider range of tables.

Closing because now #1835 is a new error with 0.13


Fix Clojars bug from v0.1.2

v0.1.2 had a bug where the incorrect source dirs were being compiled into the JAR. This fixes it by adding the :src-dirs args to the Makefile target

Looks like clean doesn't clear out target, should it?

@milt https://github.com/yetanalytics/colossal-squuid/pull/15/commits/a017d4abdc6a5e33cc16651eb962906281566ced


[BUG] The library update section is messed up.

Steps to reproduce

Open aniyomi.
Update anime library.
Have at least one anime or manga where expect two or more chapters to release.

Expected behavior
The new episodes that are updated at the same time should have been under the same time stamp. Like this

Actual behavior
The time stamp getting before every episodes it updated. Like this-

Crash logs
No crash.
Aniyomi version
App version: <IP_ADDRESS>-7801 (standard, 58817c724, 125, 2024-07-16T21:32:24Z)
Android version
13 (SDK 33; build lineage_cheeseburger-userdebug 13 TQ3A.230901.001 c666ad56da) Android build ID: lineage_cheeseburger-userdebug 13 TQ3A.230901.001 c666ad56da
Device
Device brand: OnePlus Device manufacturer: OnePlus Device name: OnePlus5 (OnePlus5) Device model: ONEPLUS A5000
Other details
I'm not sure if it's also happens with manga updates.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extension's repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Fixed in https://github.com/aniyomiorg/aniyomi/commit/c83ebf322f48d41ca1ad0105262160ecb7cde991


Allow POST request to support JSON as the content type

I believe this change is incorrect as described in https://code.djangoproject.com/ticket/19124. Use request.body instead.

So the only way to know if our request contain JSON data is to check the body? This is a bit explicit.