Feature lc plotting

more light curve plotting and spectral plotting

Codecov Report

Merging #5 into master will increase coverage by 0.65%.
The diff coverage is 86.36%.

@@            Coverage Diff             @@
##           master       #5      +/-   ##
==========================================
+ Coverage   79.30%   79.95%   +0.65%
==========================================
  Files          28       31       +3
  Lines        1266     1352      +86
==========================================
+ Hits         1004     1081      +77
- Misses        262      271       +9

Impacted Files
Coverage Δ

cosmogrb/grb/gbm_grb.py
100.00% <ø> (ø)

cosmogrb/utils/plotting/step_plot.py
58.62% <58.62%> (ø)

cosmogrb/lightcurve/light_curve_storage.py
94.02% <95.65%> (+6.38%)
:arrow_up:

cosmogrb/utils/plotting/__init__.py
100.00% <100.00%> (ø)

cosmogrb/utils/plotting/channel_plot.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #5 into master will increase coverage by 0.65%.
The diff coverage is 86.36%.

@@            Coverage Diff             @@
##           master       #5      +/-   ##
==========================================
+ Coverage    79.3%   79.95%   +0.65%
==========================================
  Files          28       31       +3
  Lines        1266     1352      +86
==========================================
+ Hits         1004     1081      +77
- Misses        262      271       +9

Impacted Files
Coverage Δ

cosmogrb/grb/gbm_grb.py
100% <ø> (ø)
:arrow_up:

cosmogrb/utils/plotting/__init__.py
100% <100%> (ø)

cosmogrb/utils/plotting/channel_plot.py
100% <100%> (ø)

cosmogrb/utils/plotting/step_plot.py
58.62% <58.62%> (ø)

cosmogrb/lightcurve/light_curve_storage.py
94.02% <95.65%> (+6.38%)
:arrow_up:

Continue to review full report at Codecov.

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


track issued schema, cred defs and allow query via admin API

Track schemas and cred defs an agent creates via non-secrets records, allow query via admin API.
Signed-off-by: sklump<EMAIL_ADDRESS>

Codecov Report

Merging #245 into master will increase coverage by 0.03%.
The diff coverage is 77.77%.

@@            Coverage Diff             @@
##           master     #245      +/-   ##
==========================================
+ Coverage   74.53%   74.56%   +0.03%
==========================================
  Files         219      222       +3
  Lines       10162    10204      +42
==========================================
+ Hits         7574     7609      +35
- Misses       2588     2595       +7


Please add git to the container

Is your feature request related to a problem? Please describe.
Yes.
I use obsidian-git to sync my two vaults between my GitLab instance and the various computers and devices I use on a daily basis.
Describe the solution you'd like
If git is added to the container, then for anyone who is using git to sync their vault between computers, like myself, then it can be set up and working without needing to fork the container and install it.

Nevermind, figured out that the linuxserver.io container mods work with their base image.
https://github.com/linuxserver/docker-mods/tree/universal-git

Although, I did have to change the config path from /config/.config/obsidian to just /config, since the SSH keys were by default being stored in /config.
Might be a good thing to change the defaults for?

Thanks for this, I have updated the readme to cover this information and updated the path of the directory to just be /config


Move plugins.api into separate module

Problem
The plugins folder contains the API as well as kotlin plugins. By moving the API (we should rename this) into a separate module, this would contribute to #155
Implementation
Create gradle module api with a dependency on the rootProject and kotlin.
Move api package from plugins folder into src/main/kotlin within the api module.

What do you suggest it be named other than API? I think that should be decided on before going forward

If the purpose of the library is to build on top of the existing infrastructure without exposing critical components like networking or the game loop, I think SDK (Software Development Kit) is a more appropriate term.
Here's some examples of existing plugin SDKs (not necessarily related to game development)

https://www.jetbrains.org/intellij/sdk/docs/intro/welcome.html
https://developers.facebook.com/docs/messenger-platform/discovery/customer-chat-plugin/sdk/
https://discordapp.com/developers/docs/game-sdk/sdk-starter-guide

Merge with #180


Button Text in Language Tab of Doordash Clone

Description
The button text in the Language tab of the Doordash Clone application lacks consistent capitalization. Additionally, some of the languages are displayed in their native script/style while others are in English, leading to inconsistency in presentation.
Describe the solution you'd like

The first letter of every word in the button text should be capitalized (e.g., "Swedish" instead of "swedish") for consistency.
Language names in the Doordash Clone should either be uniformly displayed in their native script/style or in English, with clear guidelines applied across the tab.

Willing to work on this issue


Adjust autovacuum parameters

There is an issue in Postgres the stats collector is doing a lot of writes.
Doing some experiments, this seems to get  worse with the number of tables
(with 4k metrics I can get it to do 177M/s!!!).
What happens is that the  autovacuum worker issues a command to get updated
stats every time it checks whether to do a vacuum/analyze operation. This
command rewrites all the stats files in the tmp  dir (4.6M of stuff in my
experiment). In experiments I’ve seen  70 analyzes/s and (70*4.6M and we start
seeing the issue).
This PR fixes the problem by bumping the autovacuum threshold settings. High
threshold settings guarantee that every autovacuum runs takes a longer amount
of time, (e.g. slowing down the 70 analyzes/s number in the example above).
More info about why this problem happens inside PostgreSQL:
The trace inside the autovacuum worker is:
do_autovacuum->table_recheck_autovac->pgstat_fetch_stat_dbentry->backend_read_statsfile->pgstat_send_inquiry
Apparently the stats collector /does/ rate limit the writes of the stats file
normally to once every 500ms but for Autovacuum jobs it rates limits to once
every 10ms! Supposedly this is because autovaccum needs up to date statistics
to prevent it from vacuuming just-vacuumed tables. It’s a poor man’s race
preventor - which obvs causes many other issues.

hmm should we be adding some randomness here?

hmm should we be adding some randomness here?


Stack em up

PR Description 📜
Added a new game called Stack Em Up that I have implemented using HTML, CSS and Javascript.
Fixes #1707

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & 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 have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @srujana-16 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

we already have this game !! 👀

Thank you  @srujana-16 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


[WIP] travis: PHP 5.5+ added, run tests

For PHP 7 it fails due to missing xdebug - maybe add some check to tests?
For PHP 5.6 it fails due to missing Content-type. Probably modified internal method. - I'm working on it

Awesome, thanks for your help :)

Looks like some xdebug incompatibility in naming. Should be fine now :)

Nice! Please squash your commits and I'll merge this in :D

They're separated for purpose, each does one thing.

Sounds good :).  Thanks again!

:+1:  Thanks :)


Not able to install devbox using a script

I'm trying to install devbox inside a docker container, however the --yes flag does not work:
curl -fsSL https://get.jetpack.io/devbox -o install-devbox.sh && chmod +x ./install-devbox.sh && ./install-devbox.sh --yes

=> ERROR [4/5] RUN curl -fsSL https://get.jetpack.io/devbox -o install-devbox.sh && chmod +x ./install-devbox.sh && ./install-de  1.1s
------
 > [4/5] RUN curl -fsSL https://get.jetpack.io/devbox -o install-devbox.sh && chmod +x ./install-devbox.sh && ./install-devbox.sh --yes:
#7 1.062 Devbox 📦 by jetpack.io
#7 1.062   Instant and predictable development environments and containers.
#7 1.062
#7 1.062   This script downloads and installs the latest devbox binary.
#7 1.062
#7 1.062 Confirm Installation Details
#7 1.062   Location:     /usr/local/bin/devbox
#7 1.062   Download URL: https://releases.jetpack.io/devbox
#7 1.062
#7 1.062 ? Install devbox to /usr/local/bin (requires sudo)? [Y/n] ./install-devbox.sh: line 101: /dev/tty: No such device or address
#7 1.062 ✘ Error reading from prompt (re-run with '--yes' option if running in a script)
------
executor failed running [/bin/sh -c curl -fsSL https://get.jetpack.io/devbox -o install-devbox.sh && chmod +x ./install-devbox.sh && ./install-devbox.sh --yes]: exit code: 1

@pomdtr thanks for reporting this. I'll take a look soon.

Thanks ! It looks like the FORCE env variable should be used instead.

Two ways to write the above command to get the desired effect are:
curl -fsSL https://get.jetpack.io/devbox -o install-devbox.sh && chmod +x ./install-devbox.sh && FORCE=1 ./install-devbox.sh

or
curl -fsSL https://get.jetpack.io/devbox -o install-devbox.sh && chmod +x ./install-devbox.sh && ./install-devbox.sh -f

Both options will automatically skip the prompt to install Devbox


napari-app

❓ Questions and Help
Right now pip installing napari gives you access to the napari viewer that can be launched from either a jupyter notebook or from a python script. The viewer contains the core functionality required to view and manipulate images, shapes etc. but does not contain any file I/O, drag and drop, menu bars, or infrastructure for plugins. It is also not possible to launch napari from the command line directly, nor is there yet support for a fully bundled double-clickable app. Adding support for those features is in our future, but we've had various discussions about where they should live and explorations into placing them in different repos.
One approach is that the napari viewer, located on the main napari repo remains as is, and the these features -  file I/O, menu bars, drag and drop, a console, infrastructure for plugins, cli, bundled-app, etc. - all go in a new napari-app repo. The advantage of this approach is that it maintains a separation between complex app code, file I/O, console, and plugin stuff from the viewer, which maintains its relatively light weight dependencies, and could be used by people who don't want those features without any additional burdens. I used to favor this approach and advocated against @jni adding CLI to the napari repo - see here #208. As time has gone on though I now favor and alternative approach.
Another approach is to include file I/O, drag and drop, console, the menu bars, the ability to add plugins, and the ability to launch from the CLI all in the current repo. The actual bundled executable which you download can live in the napari-app repo, but there is zero functionality added in this repo, it's just the place where the do the bundling, and the link to the bundled executable is ultimately hosted elsewhere for people to download (including the readme on the main napari page). The reasons I now favor this view are as follows:

If everything lives in the main napari repo you get the same functionality whether you launch napari from a python script, the jupyter notebook, the CLI, or the double click app. I worry that if we didn't have the integration I described about, we'd basically end up with different versions of napari having different amounts of features that would be completely unclear to a user. For example, image a situation where a user who normally uses the napari app is now interacting with a script someone else made that launches the napari viewer and they try doing drag and drop onto the viewer but it doesn't work. I think this would be very confusing to them, and I don't see why we'd prevent our users who like to launch from scripts from having access to plugins etc as well.

If we have functionality split between napari-app and napari new users and developers will be confused about where to go to for help / where to post issues / where to look in the code. It will add to our maintenance burden by now being responsible for monitoring and curating two repos. It might make installation more confusing too, i.e. you pip install napari expecting the app "functionality" and CLI, but just get the viewer.

It will also make our development cycle more complex as changes and releases now need to be coordinated across two repos, and basic code may end up being duplicated across the repos.

Users would still be able to embed the napari viewer into things without the menubars, they'd just have to deal with something with a slightly larger dependency. We could also make it possible to disable features like drag-and-drop, and the console, if they did not want to expose those features. In this way, nothing is lost by integrating all the functionality into napari apart from a slightly larger install, but if we're having problems with the install of the app we probably need to fix them regardless of if it is one repo or two repos.

These thoughts are just preliminary, and to me this is an 0.2 priority for after SciPy. I'm curious how everyone else feels about this as I know we've gone back and forth on this a fw times already. The post was motivated by a recent PR on menubars #356 from @jni.
Thoughts? @jni @royerloic @kne42 @AhmetCanSolak @kevinyamauchi

Great topic! Generally agree with this direction, and agree with all points 1-4.
However, an additional con of putting everything inside napari is the potential for bloat. One thing I currently love about napari is that it packs a lot of functionality while remaining really lightweight from an installation and UI perspective.
Specifically, I'd be worried about two forms of bloat

installation becoming bulky due to extra, tough dependencies
the UI becoming overly complex and confusing for simpler use cases

The risk of bloat varies across the various features mentioned above, and it of course depends on the implementation -- e.g. pure python fileio vs requiring bioformats and java, a console that is hidden by default and uses the built-in repl vs something more complex.
There are also ways to minimize bloat, like optional dependencies (dask handles this well) and flags to show and hide UI features (sublime text is particularly good here). But it requires careful design and diligence.
A final thought: this is not a one way door. We could start putting some of this functionality into napari-app and move it into napari if it feels clean and minimal. Or we could start putting it into napari and move it out if it becomes too bloated.
Super curious what the rest of the team thinks!

I originally favoured having the CLI in this repo and still do. I really like to give people the ability to pip install napari and then immediately type napari myimage.tif and see their image. As we saw on Twitter, people still don't have a good solution for this and think Fiji is overkill / not nice enough. Of course, this brings us back to bloat — we don't want to hit the point where napari is thrown in the same category as Fiji for this purpose.
Nevertheless, as shown by #356 and https://github.com/napari/napari-app/pull/1 together, working on separate repos is a bit of a pain and unnecessarily slow right for our current alpha development stage. So I suggest going with @sofroniewn's suggestion, while being mindful to stay modular so that things are easy enough to rip out when the time comes. (The work I did splitting up #208 was tedious but not hard at all — the biggest difficulty was in moving over all the infrastructure/install scripts, which is a one-time cost) If people agree, I'll move https://github.com/napari/napari-app/pull/1 to #356, which should make things easier to manage.

Sounds good @jni - moving that stuff over to #356 sounds good too, and I think as we go forward we should just try and keep things modular and be mindful of bloat as @freeman-lab warns

We've merge functionality for launching from the cli into the main repo and are just developing in this repo for now, so I am closing this issue


.Net: VectorStore: Create Talk RAG Demo

As a user I can run a sample which shows how to perform RAG against a PDF document (SK learn document).

See citations for any answers provided
I can click on citation links and be brought to the page in the PDF
I can ask questions in different languages
I can ask questions where the answers come from Images in the PDF
I can ask questions where the answers come from Tables in the PDF

As a developer I can modify a sample to use a different Vector Database with minimal lines of change and then run the sample against multiple PDF documents.

Use N Microsoft Learn site documents
Consider running with a local model

@sorin-costea, agents support templates and plugins just like in the VectorStoreRAG demo app, so a similar approach can be used to augment an agent as is used in the app.
I'm not sure what you mean with assemble the functionality by hand.  Do you mind sharing more details on what you are looking for?
Also note that generating embeddings can take a very long time if you have a lot of data, especially where large document sets need to be indexed.  It may also be an ongoing process if data is re-indexed as it changes.  There are of course off the shelf services available for indexing data, e.g. Azure AI Search indexers: https://learn.microsoft.com/en-us/azure/search/search-indexer-overview.  For enterprise scenarios where a developer needs to build their own, I would expect this to be part of a service that has, active-active characteristics, queuing, failure recovery, etc. matching the requirements of the organization.

@westey-m I'm coming from the integration side. While I use models and their parameters, I prefer to leave that tuning work to some data/AI/ML engineers and focus on building the application. So for me the first class citizen is the agent and its tools to connect with the real world (functions, plugins, you name it). Enterprise application programming the way I experienced it means slapping together many components and data sources, and the enterprise programmers develop and deploy mostly in Java and C#, thus SK was the obvious choice. Now that Autogen should converge, maybe I can hope in some low boilerplate components the way crew.ai (or langchain) are offering, just in a language my team can easily use and integrate in complex solutions (solutions beyond a notebook-size). I thought by just hearing the name that the Foundry would be it but alas, so I'm back to SK and sifting through library code just to figure out why a prompt function ignores the vector storage... So shortly put: 1. I hope documentation will catch up, and 2. I hope there will be a way of less boilerplate. Thank you!

@sorin-costea, are you using the SK agent framework today? See https://learn.microsoft.com/en-us/semantic-kernel/frameworks/agent
It supports plugins the same way as the rest of SK does.  See here: https://learn.microsoft.com/en-us/semantic-kernel/frameworks/agent/agent-functions.
For vector search, we have docs here to show how to turn vector search into a plugin and integrate it into a template:
https://learn.microsoft.com/en-us/semantic-kernel/concepts/text-search/text-search-vector-stores
It uses the higher level text search abstraction, which is described in more detail here:
https://learn.microsoft.com/en-us/semantic-kernel/concepts/text-search
If you have any specific areas that you feel has too much boilerplate it would be great to get your input.  It's probably worth creating a specific issue for it though, so that it can be assigned to folks who are working in that area.
If you want to speak to the team directly, you can also join our office hours:
https://devblogs.microsoft.com/semantic-kernel/microsoft-semantic-kernel-office-hours-update/
Note, due to the holiday season, the next one for EMEA/US will be in January, but it's a great way to provide specific feedback directly or ask questions.

@westey-m Thank you for your time and the links. My problem is, all those examples, and by that I mean really all, are based on code: I build a function, I call it in code, I have a variable with results, I pass it to the next one. All fine and dandy, I can confirm.
Enter agents. All those prompts introduce what to me feels like a level of inacceptable randomness.
Example at hand: RAG search. Yes I can have an handlebars prompt-based agent calling the two functions (search and augmentation) but the output of the first will be passed as a text approximation to the second - thus killing the handlebars variable matching. If there's a way to do RAG without that foreach loop matching the input structures, it's not obvious where it's documented. If there's a way to store the first output in a variable of the active context, again no idea where documented. And anyhow if I have to pass the variables by hand between functions, that's killing the whole point of having a bunch of agents right? Plus when I run more than one agent in chat mode, trying to give them discrete tasks, more often than not the first one will try to be smart and answer already - obviously wrong (temperature doesn't change anything). It all feels random, a true "mixture" of agents. Now of course, I'm fully aware all this might be because of my very very limited knowledge... but I don't even know what to ask, only to explain the issues like this. If anything of this deserves creating an "issue" I'll gladly do and work on it. But I don't know even that.
PS: I'm coming here after some experience with crew.ai which seems to have the above already figured out. Or has anchored me to a incompatible approach.


How to custom a particular word

Actually, I need bold a particular word with another font size.
is it possible with this ActiveLable?

I have same question.

You can use customType
let customType = ActiveType.custom(pattern: "\\swith\\b") //Regex that looks for "with"
label.enabledTypes = [.mention, .hashtag, .url, customType]
label.text = "This is a post with #hashtags and a @userhandle."
label.customColor[customType] = UIColor.purple

Haven't tried the fontSize so I appreciate if you can give me heads up on the fontSize.


[Snyk] Upgrade aws-sdk from 2.1199.0 to 2.1201.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade aws-sdk from 2.1199.0 to 2.1201.0.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 2 versions ahead of your current version.
The recommended version was released 21 days ago, on 2022-08-23.

Release notes

Package name: aws-sdk

2.1201.0 - 2022-08-23See changelog for more information.

2.1200.0 - 2022-08-22See changelog for more information.

2.1199.0 - 2022-08-19See changelog for more information.

    from aws-sdk GitHub release notes

Commit messages

Package name: aws-sdk

3173d0c Updates SDK to v2.1201.0
646f286 Updates SDK to v2.1200.0

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@rmkanda could you disable this automated PR ?

@juanpicado sure. disabled it.

Thanks u you !! 🙃


Make controller optional

Now that all of the configuration is back in the container, we should make the controller an optional param and supply our own, if needed. See the divider param as an example.

Added in #40


Install kerchunk instead of fsspec-reference-maker

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

This is superseded by #4. I'll now close this PR and make this fix there.


Toyota: fill steerFaultPermanent

When the delta of commanded torque and user torque is too high for too long, a permanent LKA fault can occur where you don't get steering for the rest of the drive. The behavior before was to engage but silently not steer.
Also get rid of the code in carcontroller, which is moot code
Examples of LKA_STATE=17 faults: https://imgur.com/a/CsrJ9QW
And this is what a fault from a high steer rate looks like (most common and temporary): https://imgur.com/a/xoT5JY1

This is an immediate disable. Let's check how many immediate disengagements this will now cause before merging.

Out of 2,931,274 segments, there's 7 occurrences of this kind of fault


Investigate / import MCAS results via X2

[ ] Question: How far back do historical MCAS results go in X2?
[ ] Question: What information do we have? i.e. summary stats, item-by-item results
[ ] Question: What is the quality of the data?
[ ] ToDo: Write SQL script to send to John Breslin to export MCAS via X2

@alexsoble: Working on debugging InnoDB error. Not able to access files on MySQL server. Unknown table engine InnoDB.

@alexsoble: Ben helped debug the Unknown table engine InnoDB error.
For future reference:

Create a configuration file

sudo cp /usr/local/mysql/support-files/my-small.cfn /etc/my.cfn

Uncomment the innodb-related lines in the configuration file
Add the following to the [mysqld] section:

default-storage-engine = innodb
innodb_force_recovery = 6

SQL  query for student_assessment table:
SELECT ASM_STD_OID, ASM_SKL_OID, ASM_ASD_OID, ASM_DATE, ASM_SCALE_SCORE, ASM_PERFORMANCE_LEVEL, ASM_GRADE_LEVEL_CODE FROM student_assessment;

The ASM_ASD_OID seems to be the assessment test but we may need a data dictionary because the values are not self-evident. Let me play with it more and see if I can figure out which one refer to the MCAS reading and math assessments.
SELECT DISTINCT ASM_ASD_OID FROM student_assessment;

Got it. In addition to the student_assessment table, you also need the assessment_definition table to identify the assessment name ASD_NAME e.g., MCAS, DIBELS, MEPA, MELA, SAT, ACT, AP, etc.
SELECT ASD_OID, ASD_NAME, ASD_SUBJECT FROM assessment_definition;
Merge the student_assessment table and assessment_definition table using ASM_ASD_OID and ASD_OID, respectively.

ASD_OID and ASD_NAME are specific to assessment, subject, and year (!) so either we can subset to the specific ASD_OID or we can parse the ASD_NAME for the first word = assessment.  Unfortunately ASD_TYPE is missing for assessments we are interested in i.e., MCAS, STAR.

Joining student_assessment & assessment_definition:
SELECT DISTINCT ASM_STD_OID, ASM_SKL_OID, ASM_ASD_OID, ASM_DATE, ASM_SCALE_SCORE, ASM_PERFORMANCE_LEVEL, ASD_NAME, ASD_SUBJECT,
SUBSTRING_INDEX(SUBSTRING_INDEX(ASD_NAME, ' ', 1), ' ', -1) as ASD_TEST  FROM student_assessment
LEFT JOIN assessment_definition ON student_assessment.ASM_ASD_OID=assessment_definition.ASD_OID;
The variable ASD_TEST identifies the assessment (without the additional subject and/or year information included in ASD_NAME).
@alexsoble: This is for all students in student_assessment, does not exclude INACTIVE students.

@alexsoble: Added assessment_export.sql following the other export structures.

Pulling in MCAS assessment data from X2 as recommended by Uri --- rather than pulling it in from Edwin Analytics' DropBox --- we see many more ASM_PERFORMANCE_LEVEL values. Compared to the 4 levels of {A, P, NI, W} we've pulled in from the Edwin files, the ASM_PERFORMANCE_LEVEL from X2 takes many values.
How do we map these values onto {A, P, NI, W}? @alexsoble

A
ABS
AWR
Advanced
DNT
EMG
F
INC
INE
INP
INV
LEP
MED
NI
NIA
P
P+
PRF
PRG
Proficient
TRN
VAB
W
\N

General Assessment:

W = Warning
NI = Needs Improvement
P = Proficient
A = Advanced

Alternate Assessment:

INP = Incomplete
AWR = Awareness
EMG = Emerging
PRG = Progressing
NIA = Needs Improvement
P_A = Proficient
A_A = Advanced

Others:

ABS = Absent
MED = Medically Documented Absence
TRN = Transferred
LEP = First year LEP
INC = Incomplete
VAB = Void answer
DUP = Multiple answer booklets

Link

@alexsoble: The `state_id' is not consistent between the assessment file and the {attendance, behavior, student} files. Need to look into this. Sorry I missed this until now.

@alexsoble: Think the solution is that we need to pull the following variables from the {attendance, behavior, student} files. We can review this together.

student: STD_OID
student_attendance: ATT_STD_OID
student_conduct_incident: CND_STD_OID

Relates to #80

@marimuraki No sweat! Was planning on talking with you about this today. :relaxed:

@marimuraki: https://github.com/codeforamerica/somerville-teacher-tool/commit/776aeab58ad914efc215d3bb274f6bacd0f10bf7
I think we should use state IDs instead of local IDs for students. More reliable and extensible.

@marimuraki
A few that seem to be missing from the MAP: DNT (guessing that's Did Not Test), F, INV, P+

@alexsoble: Are these values also in MCAS?

P+: Above Proficient
INV: Invalidated
F: Failing
DNT: Did Not Test

Reference

Reference

Since we don't have MCAS growth information in the most recent export, we should:

[ ] See if growth information is stored somewhere unexpected in X2 and add it to the export
[ ] If not, see if Somerville can add MCAS growth scores to X2 student_assessment table
[ ] If neither of the above works, use scaled score and drop growth score

@alexsoble: growth scores are "SGP is in the other score field, asmFieldB001" - John Breslin


resolution problem

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version: Google Chrome (ver 118.0.5993.70)
Operating system and its version: PC
PDF.js version: 3.11.0
Is a browser extension:

Steps to reproduce the problem:

The resolution drops when load pdf from the window screen
Need a way to adjust the font on the pdf page

What is the expected behavior? (add screenshot)
https://github.com/mozilla/pdf.js/assets/59465364/6433d72a-a347-4b22-830c-36df3726be6e
What went wrong? (add screenshot)
https://github.com/mozilla/pdf.js/assets/59465364/b7dccca2-74d0-411d-a779-3cc6e88569b9
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Attach (recommended) or Link to PDF file here:

This part of the ISSUE_TEMPLATE is always required in order for any issue to be actionable/valid.

Web browser and its version: Google Chrome (ver 118.0.5993.70)

Does it work better in Mozilla Firefox, since that's the primary development target for this library?

Operating system and its version: PC

Sorry, but that's not an OS name/version.

PDF.js version: 3.11.0

Unfortunately that version number doesn't actually exist; please find the latest releases at https://mozilla.github.io/pdf.js/getting_started/#download


Added -3.2 to dummy and scala-tuples-in-kotlin modules

@asm0dey
(oops, ignore the commit name)

You can always change the name of commit with --amend ;)


Fix Issue 13781 - Tuple assign should be @nogc

https://issues.dlang.org/show_bug.cgi?id=13781
@9rnsr explains why Tuple.opAssign isn't deduced to be @nogc:
"'swap' is used from the opAssign template function in Tuple, but swap checks (hasElaborateAssign!T || !isAssignable!T) and it would see the signature of T.opAssign. On mutual function calls, attributes are inferred as non-@nogc by default. It's a design so this is not a compiler bug.
The correct fix is to mark std.algorithm.swap function as @nogc."

Auto-merge toggled on


fix: Change project recipe project.api_identities.api description

Changes

Update description to field added at #916

Thanks, it seems I misunderstood what "roles" actually did. Another reason why it was worth adding a description to this field.

Thanks @ernestognw !


document using our dev-scripts for cluster setup

We have minishift instructions and another ticket to add minikube instructions, but we should also document using our dev-scripts since that is our preferred environment now that it works.

Those scripts are actually openshift-specific, so we'll need an alternative just using minikube. We have a ticket for that already.


Error: failied to determine memory area for node

I'm getting following error message using your script:
WARNING: failed to determine memory area for node: open /sys/devices/system/node/node0/memory_failure/state: no such file or directory
Its an infinitive loop and i need to abort.
System is running in EFI mode and does has entries in the folder, but not "state"
❯ ls /sys/devices/system/node/node0/memory_failure/ delayed  failed  ignored  recovered  total

hey @chdrsto my script never interacts with this path so one of the sub commands used must interact with this and it seems more like a memory issue, where in the script are you getting this issue?
i find this odd as my script does not modify anything in memory, it just edits config files

Hi @HikariKnight , it's not the vfio-setup script but rather ls-iommu causing this error which is pulled via vfio-setup.
If I manually execute it, then I get the same error

conveniently i am the developer of ls-iommu, i am wondering then what your hardware is and if you have anything in /sys/kernel/iommu_groups/
as there might be a bug or incompatibility with the pci library i use in ls-iommu

@chdrsto conveniently i am the developer of ls-iommu, i am wondering then what your hardware is and if you have anything in /sys/kernel/iommu_groups/ as this is the only location ls-iommu is looking at.
as there might be a bug or incompatibility with the pci library i use in ls-iommu, might need to make some kind of exception for it.

HW is an old MacPro 6,1 "trashcan".
I just checked in /sys/kernel/iommu_groups/
❯ ls -alh /sys/kernel/iommu_groups/
total 0
drwxr-xr-x 106 root root 0  6. Mai 08:41 .
drwxr-xr-x  16 root root 0  6. Mai 08:41 ..
drwxr-xr-x   3 root root 0  6. Mai 08:41 0
drwxr-xr-x   3 root root 0  6. Mai 08:41 1
drwxr-xr-x   3 root root 0  6. Mai 08:41 10
drwxr-xr-x   3 root root 0  6. Mai 08:41 100
drwxr-xr-x   3 root root 0  6. Mai 08:41 101
drwxr-xr-x   3 root root 0  6. Mai 08:41 102
drwxr-xr-x   3 root root 0  6. Mai 08:41 103
drwxr-xr-x   3 root root 0  6. Mai 08:41 11
drwxr-xr-x   3 root root 0  6. Mai 08:41 12
drwxr-xr-x   3 root root 0  6. Mai 08:41 13
drwxr-xr-x   3 root root 0  6. Mai 08:41 14
drwxr-xr-x   3 root root 0  6. Mai 08:41 15
drwxr-xr-x   3 root root 0  6. Mai 08:41 16
drwxr-xr-x   3 root root 0  6. Mai 08:41 17
drwxr-xr-x   3 root root 0  6. Mai 08:41 18
drwxr-xr-x   3 root root 0  6. Mai 08:41 19
drwxr-xr-x   3 root root 0  6. Mai 08:41 2
drwxr-xr-x   3 root root 0  6. Mai 08:41 20
drwxr-xr-x   3 root root 0  6. Mai 08:41 21
drwxr-xr-x   3 root root 0  6. Mai 08:41 22
drwxr-xr-x   3 root root 0  6. Mai 08:41 23
drwxr-xr-x   3 root root 0  6. Mai 08:41 24
drwxr-xr-x   3 root root 0  6. Mai 08:41 25
drwxr-xr-x   3 root root 0  6. Mai 08:41 26
drwxr-xr-x   3 root root 0  6. Mai 08:41 27
drwxr-xr-x   3 root root 0  6. Mai 08:41 28
drwxr-xr-x   3 root root 0  6. Mai 08:41 29
drwxr-xr-x   3 root root 0  6. Mai 08:41 3
drwxr-xr-x   3 root root 0  6. Mai 08:41 30
drwxr-xr-x   3 root root 0  6. Mai 08:41 31
drwxr-xr-x   3 root root 0  6. Mai 08:41 32
drwxr-xr-x   3 root root 0  6. Mai 08:41 33
drwxr-xr-x   3 root root 0  6. Mai 08:41 34
drwxr-xr-x   3 root root 0  6. Mai 08:41 35
drwxr-xr-x   3 root root 0  6. Mai 08:41 36
drwxr-xr-x   3 root root 0  6. Mai 08:41 37
drwxr-xr-x   3 root root 0  6. Mai 08:41 38
drwxr-xr-x   3 root root 0  6. Mai 08:41 39
drwxr-xr-x   3 root root 0  6. Mai 08:41 4
drwxr-xr-x   3 root root 0  6. Mai 08:41 40
drwxr-xr-x   3 root root 0  6. Mai 08:41 41
drwxr-xr-x   3 root root 0  6. Mai 08:41 42
drwxr-xr-x   3 root root 0  6. Mai 08:41 43
drwxr-xr-x   3 root root 0  6. Mai 08:41 44
drwxr-xr-x   3 root root 0  6. Mai 08:41 45
drwxr-xr-x   3 root root 0  6. Mai 08:41 46
drwxr-xr-x   3 root root 0  6. Mai 08:41 47
drwxr-xr-x   3 root root 0  6. Mai 08:41 48
drwxr-xr-x   3 root root 0  6. Mai 08:41 49
drwxr-xr-x   3 root root 0  6. Mai 08:41 5
drwxr-xr-x   3 root root 0  6. Mai 08:41 50
drwxr-xr-x   3 root root 0  6. Mai 08:41 51
drwxr-xr-x   3 root root 0  6. Mai 08:41 52
drwxr-xr-x   3 root root 0  6. Mai 08:41 53
drwxr-xr-x   3 root root 0  6. Mai 08:41 54
drwxr-xr-x   3 root root 0  6. Mai 08:41 55
drwxr-xr-x   3 root root 0  6. Mai 08:41 56
drwxr-xr-x   3 root root 0  6. Mai 08:41 57
drwxr-xr-x   3 root root 0  6. Mai 08:41 58
drwxr-xr-x   3 root root 0  6. Mai 08:41 59
drwxr-xr-x   3 root root 0  6. Mai 08:41 6
drwxr-xr-x   3 root root 0  6. Mai 08:41 60
drwxr-xr-x   3 root root 0  6. Mai 08:41 61
drwxr-xr-x   3 root root 0  6. Mai 08:41 62
drwxr-xr-x   3 root root 0  6. Mai 08:41 63
drwxr-xr-x   3 root root 0  6. Mai 08:41 64
drwxr-xr-x   3 root root 0  6. Mai 08:41 65
drwxr-xr-x   3 root root 0  6. Mai 08:41 66
drwxr-xr-x   3 root root 0  6. Mai 08:41 67
drwxr-xr-x   3 root root 0  6. Mai 08:41 68
drwxr-xr-x   3 root root 0  6. Mai 08:41 69
drwxr-xr-x   3 root root 0  6. Mai 08:41 7
drwxr-xr-x   3 root root 0  6. Mai 08:41 70
drwxr-xr-x   3 root root 0  6. Mai 08:41 71
drwxr-xr-x   3 root root 0  6. Mai 08:41 72
drwxr-xr-x   3 root root 0  6. Mai 08:41 73
drwxr-xr-x   3 root root 0  6. Mai 08:41 74
drwxr-xr-x   3 root root 0  6. Mai 08:41 75
drwxr-xr-x   3 root root 0  6. Mai 08:41 76
drwxr-xr-x   3 root root 0  6. Mai 08:41 77
drwxr-xr-x   3 root root 0  6. Mai 08:41 78
drwxr-xr-x   3 root root 0  6. Mai 08:41 79
drwxr-xr-x   3 root root 0  6. Mai 08:41 8
drwxr-xr-x   3 root root 0  6. Mai 08:41 80
drwxr-xr-x   3 root root 0  6. Mai 08:41 81
drwxr-xr-x   3 root root 0  6. Mai 08:41 82
drwxr-xr-x   3 root root 0  6. Mai 08:41 83
drwxr-xr-x   3 root root 0  6. Mai 08:41 84
drwxr-xr-x   3 root root 0  6. Mai 08:41 85
drwxr-xr-x   3 root root 0  6. Mai 08:41 86
drwxr-xr-x   3 root root 0  6. Mai 08:41 87
drwxr-xr-x   3 root root 0  6. Mai 08:41 88
drwxr-xr-x   3 root root 0  6. Mai 08:41 89
drwxr-xr-x   3 root root 0  6. Mai 08:41 9
drwxr-xr-x   3 root root 0  6. Mai 08:41 90
drwxr-xr-x   3 root root 0  6. Mai 08:41 91
drwxr-xr-x   3 root root 0  6. Mai 08:41 92
drwxr-xr-x   3 root root 0  6. Mai 08:41 93
drwxr-xr-x   3 root root 0  6. Mai 08:41 94
drwxr-xr-x   3 root root 0  6. Mai 08:41 95
drwxr-xr-x   3 root root 0  6. Mai 08:41 96
drwxr-xr-x   3 root root 0  6. Mai 08:41 97
drwxr-xr-x   3 root root 0  6. Mai 08:41 98
drwxr-xr-x   3 root root 0  6. Mai 08:41 99

@chdrsto Ah i never seen one of those in person.
i know the pci library we use in ls-iommu had problems with pci addresses that were outside of the standard 4 hexadecimal address space in /sys/bus/pci/devices and we had to make an exception for the 10000 pci address since that was some kind of non standard intel specific pci address.
im curious if you have something similar there if you can ls the location :thinking: it might give me some clues

sure, your help is appreciated:
❯ ls -alh /sys/bus/pci/devices/
insgesamt 0
drwxr-xr-x 2 root root 0  6. Mai 08:41 .
drwxr-xr-x 5 root root 0  6. Mai 08:41 ..
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:00.0 -> ../../../devices/pci0000:00/0000:00:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:01.0 -> ../../../devices/pci0000:00/0000:00:01.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:02.0 -> ../../../devices/pci0000:00/0000:00:02.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:03.0 -> ../../../devices/pci0000:00/0000:00:03.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:04.0 -> ../../../devices/pci0000:00/0000:00:04.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:04.1 -> ../../../devices/pci0000:00/0000:00:04.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:04.2 -> ../../../devices/pci0000:00/0000:00:04.2
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:04.3 -> ../../../devices/pci0000:00/0000:00:04.3
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:04.4 -> ../../../devices/pci0000:00/0000:00:04.4
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:04.5 -> ../../../devices/pci0000:00/0000:00:04.5
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:04.6 -> ../../../devices/pci0000:00/0000:00:04.6
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:04.7 -> ../../../devices/pci0000:00/0000:00:04.7
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:05.0 -> ../../../devices/pci0000:00/0000:00:05.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:05.1 -> ../../../devices/pci0000:00/0000:00:05.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:05.2 -> ../../../devices/pci0000:00/0000:00:05.2
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:05.4 -> ../../../devices/pci0000:00/0000:00:05.4
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:11.0 -> ../../../devices/pci0000:00/0000:00:11.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:16.0 -> ../../../devices/pci0000:00/0000:00:16.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:1b.0 -> ../../../devices/pci0000:00/0000:00:1b.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:1c.0 -> ../../../devices/pci0000:00/0000:00:1c.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:1c.1 -> ../../../devices/pci0000:00/0000:00:1c.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:1c.2 -> ../../../devices/pci0000:00/0000:00:1c.2
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:1c.4 -> ../../../devices/pci0000:00/0000:00:1c.4
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:1d.0 -> ../../../devices/pci0000:00/0000:00:1d.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:1e.0 -> ../../../devices/pci0000:00/0000:00:1e.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:1f.0 -> ../../../devices/pci0000:00/0000:00:1f.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:00:1f.3 -> ../../../devices/pci0000:00/0000:00:1f.3
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:02:00.0 -> ../../../devices/pci0000:00/0000:00:02.0/0000:02:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:02:00.1 -> ../../../devices/pci0000:00/0000:00:02.0/0000:02:00.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:06:00.0 -> ../../../devices/pci0000:00/0000:00:03.0/0000:06:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:06:00.1 -> ../../../devices/pci0000:00/0000:00:03.0/0000:06:00.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:0b:00.0 -> ../../../devices/pci0000:00/0000:00:1c.0/0000:0b:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:0c:00.0 -> ../../../devices/pci0000:00/0000:00:1c.1/0000:0c:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:0d:00.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:0d:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:0e:00.0 -> ../../../devices/pci0000:00/0000:00:1c.4/0000:0e:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:10:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:11:01.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:01.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:11:02.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:02.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:11:08.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:08.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:11:09.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:09.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:11:0a.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:0a.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:12:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:01.0/0000:12:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:14:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:02.0/0000:14:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:15:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:02.0/0000:14:00.0/0000:15:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:15:03.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:02.0/0000:14:00.0/0000:15:03.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:15:04.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:02.0/0000:14:00.0/0000:15:04.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:15:05.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:02.0/0000:14:00.0/0000:15:05.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:15:06.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:02.0/0000:14:00.0/0000:15:06.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:16:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:02.0/0000:14:00.0/0000:15:00.0/0000:16:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:17:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:02.0/0000:14:00.0/0000:15:03.0/0000:17:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:18:01.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:02.0/0000:14:00.0/0000:15:03.0/0000:17:00.0/0000:18:01.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:19:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:02.0/0000:14:00.0/0000:15:03.0/0000:17:00.0/0000:18:01.0/0000:19:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:1a:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:02.0/0000:14:00.0/0000:15:03.0/0000:17:00.0/0000:18:01.0/0000:19:00.0/0000:1a:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:1b:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:02.0/0000:14:00.0/0000:15:03.0/0000:17:00.0/0000:18:01.0/0000:19:00.0/0000:1a:00.0/0000:1b:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:1b:00.1 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:02.0/0000:14:00.0/0000:15:03.0/0000:17:00.0/0000:18:01.0/0000:19:00.0/0000:1a:00.0/0000:1b:00.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:5b:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:09.0/0000:5b:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:5c:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:09.0/0000:5b:00.0/0000:5c:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:5c:03.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:09.0/0000:5b:00.0/0000:5c:03.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:5c:04.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:09.0/0000:5b:00.0/0000:5c:04.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:5c:05.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:09.0/0000:5b:00.0/0000:5c:05.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:5c:06.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:09.0/0000:5b:00.0/0000:5c:06.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:5d:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:09.0/0000:5b:00.0/0000:5c:00.0/0000:5d:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:a2:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:0a.0/0000:a2:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:a3:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:0a.0/0000:a2:00.0/0000:a3:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:a3:03.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:0a.0/0000:a2:00.0/0000:a3:03.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:a3:04.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:0a.0/0000:a2:00.0/0000:a3:04.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:a3:05.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:0a.0/0000:a2:00.0/0000:a3:05.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:a3:06.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:0a.0/0000:a2:00.0/0000:a3:06.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:a4:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:0a.0/0000:a2:00.0/0000:a3:00.0/0000:a4:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:a5:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:0a.0/0000:a2:00.0/0000:a3:03.0/0000:a5:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:a6:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:0a.0/0000:a2:00.0/0000:a3:03.0/0000:a5:00.0/0000:a6:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:a6:03.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:0a.0/0000:a2:00.0/0000:a3:03.0/0000:a5:00.0/0000:a6:03.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:a6:04.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:0a.0/0000:a2:00.0/0000:a3:03.0/0000:a5:00.0/0000:a6:04.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:a6:05.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:0a.0/0000:a2:00.0/0000:a3:03.0/0000:a5:00.0/0000:a6:05.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:a7:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:0a.0/0000:a2:00.0/0000:a3:03.0/0000:a5:00.0/0000:a6:00.0/0000:a7:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:a8:00.0 -> ../../../devices/pci0000:00/0000:00:01.0/0000:10:00.0/0000:11:0a.0/0000:a2:00.0/0000:a3:03.0/0000:a5:00.0/0000:a6:03.0/0000:a8:00.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:08.0 -> ../../../devices/pci0000:ff/0000:ff:08.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:08.3 -> ../../../devices/pci0000:ff/0000:ff:08.3
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:08.4 -> ../../../devices/pci0000:ff/0000:ff:08.4
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:09.0 -> ../../../devices/pci0000:ff/0000:ff:09.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:09.3 -> ../../../devices/pci0000:ff/0000:ff:09.3
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:09.4 -> ../../../devices/pci0000:ff/0000:ff:09.4
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0a.0 -> ../../../devices/pci0000:ff/0000:ff:0a.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0a.1 -> ../../../devices/pci0000:ff/0000:ff:0a.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0a.2 -> ../../../devices/pci0000:ff/0000:ff:0a.2
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0a.3 -> ../../../devices/pci0000:ff/0000:ff:0a.3
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0b.0 -> ../../../devices/pci0000:ff/0000:ff:0b.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0b.3 -> ../../../devices/pci0000:ff/0000:ff:0b.3
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0c.0 -> ../../../devices/pci0000:ff/0000:ff:0c.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0c.1 -> ../../../devices/pci0000:ff/0000:ff:0c.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0c.2 -> ../../../devices/pci0000:ff/0000:ff:0c.2
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0c.3 -> ../../../devices/pci0000:ff/0000:ff:0c.3
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0c.4 -> ../../../devices/pci0000:ff/0000:ff:0c.4
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0c.5 -> ../../../devices/pci0000:ff/0000:ff:0c.5
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0d.0 -> ../../../devices/pci0000:ff/0000:ff:0d.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0d.1 -> ../../../devices/pci0000:ff/0000:ff:0d.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0d.2 -> ../../../devices/pci0000:ff/0000:ff:0d.2
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0d.3 -> ../../../devices/pci0000:ff/0000:ff:0d.3
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0d.4 -> ../../../devices/pci0000:ff/0000:ff:0d.4
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0d.5 -> ../../../devices/pci0000:ff/0000:ff:0d.5
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0e.0 -> ../../../devices/pci0000:ff/0000:ff:0e.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0e.1 -> ../../../devices/pci0000:ff/0000:ff:0e.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0f.0 -> ../../../devices/pci0000:ff/0000:ff:0f.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0f.1 -> ../../../devices/pci0000:ff/0000:ff:0f.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0f.2 -> ../../../devices/pci0000:ff/0000:ff:0f.2
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0f.3 -> ../../../devices/pci0000:ff/0000:ff:0f.3
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0f.4 -> ../../../devices/pci0000:ff/0000:ff:0f.4
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:0f.5 -> ../../../devices/pci0000:ff/0000:ff:0f.5
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:10.0 -> ../../../devices/pci0000:ff/0000:ff:10.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:10.1 -> ../../../devices/pci0000:ff/0000:ff:10.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:10.2 -> ../../../devices/pci0000:ff/0000:ff:10.2
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:10.3 -> ../../../devices/pci0000:ff/0000:ff:10.3
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:10.4 -> ../../../devices/pci0000:ff/0000:ff:10.4
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:10.5 -> ../../../devices/pci0000:ff/0000:ff:10.5
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:10.6 -> ../../../devices/pci0000:ff/0000:ff:10.6
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:10.7 -> ../../../devices/pci0000:ff/0000:ff:10.7
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:11.0 -> ../../../devices/pci0000:ff/0000:ff:11.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:13.0 -> ../../../devices/pci0000:ff/0000:ff:13.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:13.1 -> ../../../devices/pci0000:ff/0000:ff:13.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:13.4 -> ../../../devices/pci0000:ff/0000:ff:13.4
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:13.5 -> ../../../devices/pci0000:ff/0000:ff:13.5
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:13.6 -> ../../../devices/pci0000:ff/0000:ff:13.6
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:16.0 -> ../../../devices/pci0000:ff/0000:ff:16.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:16.1 -> ../../../devices/pci0000:ff/0000:ff:16.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:16.2 -> ../../../devices/pci0000:ff/0000:ff:16.2
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1c.0 -> ../../../devices/pci0000:ff/0000:ff:1c.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1c.1 -> ../../../devices/pci0000:ff/0000:ff:1c.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1c.2 -> ../../../devices/pci0000:ff/0000:ff:1c.2
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1d.0 -> ../../../devices/pci0000:ff/0000:ff:1d.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1d.1 -> ../../../devices/pci0000:ff/0000:ff:1d.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1d.2 -> ../../../devices/pci0000:ff/0000:ff:1d.2
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1d.3 -> ../../../devices/pci0000:ff/0000:ff:1d.3
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1d.4 -> ../../../devices/pci0000:ff/0000:ff:1d.4
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1d.5 -> ../../../devices/pci0000:ff/0000:ff:1d.5
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1e.0 -> ../../../devices/pci0000:ff/0000:ff:1e.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1e.1 -> ../../../devices/pci0000:ff/0000:ff:1e.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1e.2 -> ../../../devices/pci0000:ff/0000:ff:1e.2
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1e.3 -> ../../../devices/pci0000:ff/0000:ff:1e.3
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1e.4 -> ../../../devices/pci0000:ff/0000:ff:1e.4
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1e.5 -> ../../../devices/pci0000:ff/0000:ff:1e.5
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1e.6 -> ../../../devices/pci0000:ff/0000:ff:1e.6
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1e.7 -> ../../../devices/pci0000:ff/0000:ff:1e.7
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1f.0 -> ../../../devices/pci0000:ff/0000:ff:1f.0
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1f.1 -> ../../../devices/pci0000:ff/0000:ff:1f.1
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1f.2 -> ../../../devices/pci0000:ff/0000:ff:1f.2
lrwxrwxrwx 1 root root 0  6. Mai 08:41 0000:ff:1f.3 -> ../../../devices/pci0000:ff/0000:ff:1f.3

hey @chdrsto, since i couldn't see anything suspicious with the pci addressses i checked the ghw issue tracker, it seems like this is a bug upstream in ghw which is the library ls-iommu uses to get hardware info.
a fix was pushed 1 hour ago, however due to caching i will not be able to update the dependencies for ls-iommu before tomorrow and push a new version which vfio-setup can download for quickpassthrough.
to get vfio-setup to download the new version of ls-iommu when i have pushed the updated version to https://github.com/hikariknight/ls-iommu, just delete the tar.gz file from the utils folder, this will get the script to download the latest version as i never wrote in a proper version check in the bash version of this project.

hey @chdrsto can you try out the new release of ls-iommu https://github.com/HikariKnight/ls-iommu/releases/tag/2.2.2 and see if that fixes it for you, just place the binary inside the utils folder :)


The sequence of this page is misleading, admin may accidentally apply to all users blocking some users whilke actually intending only a small user test

You explain the feature works with Conditional Access and start with explaining the scope from SharePoint to all off O365, but you do not have any note of caution, that the steps under 'Block Access' respectively 'Limit Access' create an immediately-on Conditional Access policy for All Users.
This can create situations, where while testing this, valid users get locked out before someone notices and scopes the Test-policy to the test-group first. Please add a note of caution to go to the conditional Access policy and adjust scope as needed immediately after putting the setting into effect

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

ID: 2f2abda5-9273-1a56-91b6-e4e77d5706b0
Version Independent ID: 6a85f2a5-b892-55f7-b49a-4ab15f1e8b73
Content: SharePoint and OneDrive unmanaged device access controls for administrators - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/control-access-from-unmanaged-devices.md
Service: sharepoint-online
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

Hello @fmiltner
The article currently states for Block Access and Limit Access procedures:

Selecting this option disables any previous conditional access policies you created from this page, and creates a new conditional access policy that applies to all users.

Please kindly let me know if I understood you correctly,

Hm, then I was successfully able to miss it - but in brackets under point 3 and only indirectly as setting it resets previously created rules? I feel that deserves a forth point "check the CA policy created and adjust per your needs"

@fmiltner I'll propose to give more emphasis to the sentence through an important note.

Thanks! and maybe along that important note make aa remark to cross-check for interference with other existing CA policies and services (e.g. when you deploy it as-is you break certain PowerAutomate actions for all users in the tenant (example being https://docs.microsoft.com/en-us/connectors/sharepointonline/#get-file-content - so some careful scoping considerations are needed.


feat: always grant service ID 'Service ID creator' access

Description

removed the variable add_service_id_creator_role and by default now always grant service ID 'Service ID creator' access

Release required?

[ ] No release
[ ] Patch release (x.x.X)
[x] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Bluetooth: Mesh: Fixes LPN poll timeout gradually grow

POLL_TIMEOUT_MAX should use CONFIG_BT_MESH_LPN_POLL_TIMEOUT
instead of CONFIG_BT_MESH_LPN_INIT_POLL_TIMEOUT. The described
algorithm to grow the poll timeout implemented in function
poll_timeout does not work with this implementation.
Fixes: #30338
Signed-off-by: Lingao Meng<EMAIL_ADDRESS>

Is this a regression or has it always been broken? If it's a regression it would be good to reference the commit that broke it in the commit message.

According to the link bug description this is a regression since: https://github.com/zephyrproject-rtos/zephyr/commit/3b4d58aa4bb05a7b30bb720132bbfa35ea90be7d


linstor: enable discard for Linstor storage pools

Description
This PR enables qemu discard support for Linstor storage pools

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI
[ ] test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[x] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?
Tested in a Linstor cluster
How did you try to break this feature and the system with this change?

@blueorangutan package

@sureshanaparti a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11282

@blueorangutan test

[SF] Trillian test result (tid-11618)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 40689 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9770-t11618-kvm-ol8.zip
Smoke tests completed. 91 look OK, 3 have errors, 17 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_01_list_sec_storage_vm
Error
0.01
test_ssvm.py

test_02_list_cpvm_vm
Error
0.01
test_ssvm.py

test_03_ssvm_internals
Error
0.01
test_ssvm.py

test_04_cpvm_internals
Error
0.01
test_ssvm.py

test_05_stop_ssvm
Error
0.01
test_ssvm.py

test_06_stop_cpvm
Error
0.01
test_ssvm.py

test_07_reboot_ssvm
Error
0.01
test_ssvm.py

test_08_reboot_cpvm
Error
0.01
test_ssvm.py

test_09_reboot_ssvm_forced
Error
0.01
test_ssvm.py

test_10_reboot_cpvm_forced
Error
0.01
test_ssvm.py

test_11_destroy_ssvm
Error
0.01
test_ssvm.py

test_12_destroy_cpvm
Error
0.01
test_ssvm.py

test_13_ss_nfs_version_on_ssvm
Error
0.01
test_ssvm.py

test_static_role_account_acls
Error
0.01
test_staticroles.py

ContextSuite context=TestVMWareStoragePolicies>:setup
Error
0.00
test_storage_policy.py

all_test_templates
Skipped
---
test_templates.py

all_test_update_security_group
Skipped
---
test_update_security_group.py

all_test_usage_events
Skipped
---
test_usage_events.py

all_test_usage
Skipped
---
test_usage.py

all_test_vm_autoscaling
Skipped
---
test_vm_autoscaling.py

all_test_vm_deployment_planner
Skipped
---
test_vm_deployment_planner.py

all_test_vm_life_cycle
Skipped
---
test_vm_life_cycle.py

all_test_vm_lifecycle_unmanage_import
Skipped
---
test_vm_lifecycle_unmanage_import.py

all_test_vm_snapshot_kvm
Skipped
---
test_vm_snapshot_kvm.py

all_test_vm_snapshots
Skipped
---
test_vm_snapshots.py

all_test_volumes
Skipped
---
test_volumes.py

all_test_vpc_ipv6
Skipped
---
test_vpc_ipv6.py

all_test_vpc_redundant
Skipped
---
test_vpc_redundant.py

all_test_vpc_router_nics
Skipped
---
test_vpc_router_nics.py

all_test_vpc_vpn
Skipped
---
test_vpc_vpn.py

all_test_host_maintenance
Skipped
---
test_host_maintenance.py

all_test_hostha_kvm
Skipped
---
test_hostha_kvm.py

@blueorangutan package

@sureshanaparti a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11294

@blueorangutan test

@DaanHoogland a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

[SF] Trillian test result (tid-11625)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 46015 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9770-t11625-kvm-ol8.zip
Smoke tests completed. 109 look OK, 2 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

ContextSuite context=TestISOUsage>:setup
Error
0.00
test_usage.py

test_01_migrate_VM_and_root_volume
Error
80.14
test_vm_life_cycle.py

test_02_migrate_VM_with_two_data_disks
Error
52.78
test_vm_life_cycle.py

test_08_migrate_vm
Error
47.10
test_vm_life_cycle.py


_plugins/_sql/_explain is not working as described in documentation

Description
Endpoint _plugins/_sql/_explain is not working as described in documentation.
Documentation states:

Description
To translate your query, send it to explain endpoint. The explain output is OpenSearch domain specific language (DSL) in JSON format. You can just copy and paste it to your console to run it against OpenSearch directly.
Explain query:
>> curl -H 'Content-Type: application/json' -X POST localhost:9200/_plugins/_sql/_explain -d '{
  "query" : "SELECT firstname, lastname FROM accounts WHERE age > 20"
}'

Result:
{
  "from": 0,
  "size": 200,
  "query": {
    "bool": {
      "filter": [{
        "bool": {
          "must": [{
            "range": {
              "age": {
                "from": 20,
                "to": null,
                "include_lower": false,
                "include_upper": true,
                "boost": 1.0
              }
            }
          }],
          "adjust_pure_negative": true,
          "boost": 1.0
        }
      }],
      "adjust_pure_negative": true,
      "boost": 1.0
    }
  },
  "_source": {
    "includes": [
      "firstname",
      "lastname"
    ],
    "excludes": []
  }
}

But this is actually not true.
To Reproduce
RUN:
POST _plugins/_sql/_explain
{
 "query": "SELECT * FROM tracardi-rule"
}

And you get something like:
{
  "root": {
    "name": "ProjectOperator",
    "description": {
      "fields": "[metadata]"
    },
    "children": [
      {
        "name": "OpenSearchIndexScan",
        "description": {
          "request": """OpenSearchQueryRequest(indexName=tracardi-rule, sourceBuilder={"from":0,"size":200,"timeout":"1m","_source":{"includes":["metadata"],"excludes":[]}}, searchDone=false)"""
        },
        "children": []
      }
    ]
  }
}```

**Expected behavior**
I expect to find legit query that I could run against _search endpoint

Please, see documentation update in https://github.com/opensearch-project/documentation-website/pull/830.


Terminal command to load session.

Hello. I used to use obsession for my sessions management. But it is slightly slow...
May I use possession the same way as obsession?
I normally do :Obsession in session which I want to track and than i do nvim -S if I want restore session for current dir and just nvim if I doesn't.
How can I do it with possession?

Hi, one thing that vim-obsession does differently (as far as I understand) is that it saves session files in the current directory. possesion uses a common directory for all sessions (e.g. ~/.local/share/nvim/possession/) and the current code would require quite a bit of refactoring if the common directory approach is a no-go for you.
But if you would be ok with common directory, than the potential workflow could be:

in setup {...} set autosave.current = true
use PossessionSave yoursessionname to save the session; it will  now also be auto-saved before quitting nvim due to autosave.on_quit = true
when  you want to start nvim using the session for current dir you would use a command like PossessionLoadCwd that would check existing sessions and find a best match based on cwd, then load it

To make this work we would need to implement the metioned PossessionLoadCwd command. Available sessions can be found using as_list() and then session.cwd can be checked. There are even some helper functions in query.lua that could be used, probably some combination like M.group_by(M.by_root_dir(current_dir), sessions) and then find best match (closest to cwd).
What do you thing of such a workflow vs what you are currently using?

I have a use case for something like this. I'd like to be able to quickly quit nvim and re-enter right where i left off for when i make updates to my nvim config.

@Justinfan827 Would saving temporary session work? You would work on something, then quit, this would save tmp session, then you can open nvim and use PossessionLoad tmp.  I'm suggesting this soultuion, as I don't think I'll have time to work on CWD-based session in the near future.


Deprecate in favor of 'static' repo (?)

Due to the fact that some hand written extensions may be wanted, the differentiation between boilerplate static content seems a bit too much to justify a repo with 4 files. An folder 'internal' could be sufficient. I like to separate things neatly, but spamming repos, I hate.
Any random thoughts welcome.

... Still no good idea, but static stuff seems to grow ...


Update and enrich installation guide

I hope everything is correct. I did not work out what exactly the syslog role is doing/changing, so this paragraph is kept rather short.

Thanks!


Introduce stats exporters

Allow multiple exporters to be registered and report view data
on globally registered exporters.
Fixes #73.

/cc @bogdandrutu
Currently a draft and but this is what I am thinking about for the exporters and the subscription model.

@bogdandrutu, can you take a look now?


Add some extra framework to allow using Apple accelerate

Sam,
I see that we are using 4-byte integers for array indexing in MKL, Blas and Lapack and hopefully in the code that calls them. At this point is that a good long-term decision? If it is best short term, then I think we should throw an exception whenever the size of a constructed vector requires an index that does not fit into the 4-byte integer. It could happen.
Looks good.
Best
Terry

From: inakleinbottle @.>
Sent: 12 September 2023 11:24
To: datasig-ac-uk/RoughPy @.>
Cc: Subscribed @.***>
Subject: Re: [datasig-ac-uk/RoughPy] Add some extra framework to allow using Apple accelerate (PR #36)
Merged #36https://github.com/datasig-ac-uk/RoughPy/pull/36 into develop.
—
Reply to this email directly, view it on GitHubhttps://github.com/datasig-ac-uk/RoughPy/pull/36#event-10344875573, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABQWN6YLXSE66BIAUVQYNL3X2AZ7BANCNFSM6AAAAAA4US26UY.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


MathJax single aggregated JS file, grunt build script

See email discussion:
https://groups.google.com/forum/#!msg/readium-dev/lGWYDvSMwdY/BnA-s-hp8XIJ
Peter Krautzberger @pkra
"I should have a grunt file for you later this week so that you can do single-file builds yourself"

Readium cloud-reader and Chrome extension/packaged-app now fetch the latest (v2.5.1) MathJax single-file build directly from Peter Krautzberger's GitHub repository https://github.com/pkra/MathJax-single-file via NPM dependency (don't forget to invoke the build task npm run prepare).
Code checkin: https://github.com/readium/readium-js-viewer/commit/ab88cb281455d416e0c1406db687ec70e007879f


Reformat src files with erlfmt

Overview
Plenty of time is spent on formatting comments in PRs.
This PR changes all .erl files in src to the erlfmt formatted versions.
Testing recommendations

Run dev/format-all.py and get the same PR contents (and a Hashes match output).
Related Issues or Pull Requests

See the most recent https://github.com/apache/couchdb/pull/3553#issuecomment-841322154 .
Checklist

[ ] Code is written and works correctly
[ ] Changes are covered by tests
[ ] Any new configurable parameters are documented in rel/overlay/etc/default.ini
[ ] A PR for documentation changes has been made in https://github.com/apache/couchdb-documentation

I propose to employ a unified scale so we can collect feedback on the same formatting changes.
This would allow us to make better decisions. I also expect people to complain more than praise therefore I propose a skewed scale.
I propose to rate the changes based on following scale:
-5 - -1 - a scale from negative 5 to negative 1 how badly I disagree with the change. Where -5 is I cannot stand it and -1 is I don't like it but can tolerate.
0 - neutral - I don't really care
+1 - I like the change even if I am not used to it.
+2 - this is a great

Thank you all for the very quick feedback!
According to https://github.com/WhatsApp/erlfmt#comparison-with-other-erlang-formatters , erlfmt is meant to be opinionated with little to no configuration available. If we believe this PR is a net-negative change, I'll close it. If we think erlfmt is not right for us, but exploring another formatter is worth it, please let me know.

Nice work @bessbd.

I like that it is consistent and it auto-formats the code that is a big plus and it removes a good amount of back-and-forth during reviews

Good call to check the hashes before and after, that's a neat trick!

Some erlfmt choices are odd, such as putting -> on a line by itself. I don't like it but not a deal breaker compared to other benefits

In general I would prefer 80 columns (that is configurable erlfmt --print-width=80) but if most people would want to stick with the default 100 that's ok too. It seems, based on how case nesting is reformatted (always indented with 4 spaces) some places like auth handlers end up being squished to the right even with 100 columns. With 80 it would be worse so I can live with 100 columns.

I don't like the spacing between functions as much, I prefer one line between function head clauses, and two lines between functions. However, if erlfmt means having consistency I am ok sticking with erlfmt's way.

Based on @iilyak's scale (-5...+2), I'd go with +1 as an average of my choices. But also think we should wait perhaps until erlfmt reaches 1.0 and maybe gather more feedback (possibly with a post on dev@couchdb?). Also wonder if there any chance convincing erlfmt authors to change their mind about a few of the most disliked features here such as -> being on its own line.
Another issue is being able to cherry-pick commits between 3.x and main. We have two recent PRs, for example, (Erlang 24 support and a pending one for moving chttpd/httpd settings around) that would apply neatly to both branches, but if we reformat one branch those won't apply as easily. Not a deal breaker, but perhaps we would run erlfmt on both main and 3.x at the same time and maybe coordinating with pending PR authors.

Also wonder if there any chance convincing erlfmt authors to change their mind about a few of the most disliked features here such as -> being on its own line.

@nickva : to avoid being blocked on an action on their side, we can just do the reformat here and re-apply the formatter once they make the changes that are beneficial to us. Wdyt?

@bessbd  yeah that would work. We can always re-apply the formatting. Good point.
The last thing is perhaps to coordinate with any pending PR authors as this might make it difficult for them to rebase, specifically thinking about this one https://github.com/apache/couchdb/pull/3567 but there may be others too.

There are erlfmt-format (which formats all files) and erlfmt-check. Do we have commands to command files in specific directory or to format a specific file? Can you document them somewhere?

There are erlfmt-format (which formats all files) and erlfmt-check. Do we have commands to command files in specific directory or to format a specific file? Can you document them somewhere?

Added a few lines to 02c48e8 .

As Paul's involuntary amanuensis he says "go for it" but asks if we've confirmed that the abstract syntax tree is unaffected (i.e, the changes are purely cosmetic and make no difference to the compiled artifacts).

As Paul's involuntary amanuensis he says "go for it" but asks if we've confirmed that the abstract syntax tree is unaffected (i.e, the changes are purely cosmetic and make no difference to the compiled artifacts).

erlfmt verifies internally that the AST has not been modified, except for comments and code locations.  If it is modified erlfmt would throw an error.  If you find such cases, please report an error, so we can fix it.

As Paul's involuntary amanuensis he says "go for it" but asks if we've confirmed that the abstract syntax tree is unaffected (i.e, the changes are purely cosmetic and make no difference to the compiled artifacts).

erlfmt verifies internally that the AST has not been modified, except for comments and code locations. If it is modified erlfmt would throw an error. If you find such cases, please report an error, so we can fix it.

@awalterschulze : does that mean the proof I do in https://github.com/apache/couchdb/pull/3568/files#diff-f2ea7984714072018b8a19daabd2dbc8df9f662af94849ffa7eb60b54bc711f0 is unnecessary and can be removed? Same thing for tests, we can run erlfmt on those files and they are guaranteed to be "identical"?

As Paul's involuntary amanuensis he says "go for it" but asks if we've confirmed that the abstract syntax tree is unaffected (i.e, the changes are purely cosmetic and make no difference to the compiled artifacts).

erlfmt verifies internally that the AST has not been modified, except for comments and code locations. If it is modified erlfmt would throw an error. If you find such cases, please report an error, so we can fix it.

@awalterschulze : does that mean the proof I do in https://github.com/apache/couchdb/pull/3568/files#diff-f2ea7984714072018b8a19daabd2dbc8df9f662af94849ffa7eb60b54bc711f0 is unnecessary and can be removed? Same thing for tests, we can run erlfmt on those files and they are guaranteed to be "identical"?

It depends how rigorous you want to be.
erlfmt does it on the AST level, see https://github.com/WhatsApp/erlfmt/blob/master/src/erlfmt.erl#L459
you seem to be doing it on the beam level.
I think both have merit, but it depends how rigorous you need to be.

@awalterschulze ah! that's excellent, thank you.
@bessbd any extra checking seems unnecessary then (and would potentially give false negatives).

@awalterschulze after playing around in an editor with some erlfmt formatted CouchDB code, I find it all pretty readable, and generally an improvement, with only one real exception. CouchDB style has evolved to put a blank line between function clauses, and 2 blank lines between functions. After formatting, these get changed to no 0 and 1 respectively. I wonder if your team would consider respecting the original format for this case as well as the others you already honor here?

@awalterschulze after playing around in an editor with some erlfmt formatted CouchDB code, I find it all pretty readable, and generally an improvement, with only one real exception. CouchDB style has evolved to put a blank line between function clauses, and 2 blank lines between functions. After formatting, these get changed to no 0 and 1 respectively. I wonder if your team would consider respecting the original format for this case as well as the others you already honor here?

Thank you @jaydoane it is really great to hear that you find erlfmt to be a general improvement.
Sorry for taking so long to get back to you, but we needed to give this some thought.
The problem with preserving the spacing for this case though, is it would result in a lot of inconsistency caused by users.
If anything this would need to be an enforced style, but that would need to be configured and erlfmt does not to config.
We want erlfmt to enforce an opinionated style.
We did consider this format before as the opinionated style, as we very much liked this idea from Elixir.
But we found this style is uncommon in erlang code bases.
I hope that makes sense.

We did consider this format before as the opinionated style, as we very much liked this idea from Elixir.
But we found this style is uncommon in most erlang code bases.

@awalterschulze Thanks, and I appreciate the nuances of the argument.
When I first started with Erlang, I only ever recall seeing 1 empty line between functions and 0 between function clauses. However, in CouchDB it's essentially the standard (as sporadically enforced/suggested by emilio), and I've come to find it much more readable than the more common format.
IMO, just because it's uncommon, doesn't mean it's worse.
And if erlfmt opinionatedly enforced that style, just think how much more common it could become!  ;)

IMO, just because it's uncommon, doesn't mean it's worse.

Yeah I agree.   I am not saying our style is better.
We tried to mostly enforce the style that already exists in the erlang community, to increase chances of adoption rather than create a new better style.  We didn't achieve this in all cases, but this is at least what we tried to do.
We believe standardizing is more important than the exact style chosen.
I hope that makes some sense.

Being a new hire and contributor, I highly advocate for a universal standard for formatting. I spend a lot of time on formatting and use the format of other source code to make formatting decisions (often incorrectly). Not to mention having a wonderful script to handle the formatting for me.

Thank you all for the reviews and contribution! I'm about to merge this.

Seems like a lot of these changes are nice improvements, but some (like the 2 I've flagged) are much more intrusive. How much control do we have over the opinions of erlfmt?

Hi! You can disable formatting of a top-level expression with: ```erlang
%% erlfmt-ignore

To disable formatting for the whole file, add this magic comment as first line: ```erlang
%%% % @format

You might also be interested by 'respecting original format' hints.

I had attempted to format the 3.x branch. It has a lot more files than main (500+)
As a fun experiment I had performed a beam-level check too. As mentioned above by @rnewson, it did lead to false positives as 3.x fabric imports eunit.hrl, which uses ?LINE macros. Then, any module which imports from fabric.hrl and has tests or asserts in it, had failed the check.


helm template generates manifests without namespace

What is the bug?
When used with helm template like this:
helm template airflow airflow-stable/airflow -f custom_values.yaml --namespace=airflow

The chart will generate manifests that, for the most part, don't contain namespace: key (RoleBinding is the only one I can see that will contain namespace).
This is problematic because helm template | kubectl apply -f - will result in a different state than helm install whcih can be surprising to users.
What are your Helm values?
This happens even without custom_values
What is your Helm version?:
$ helm version
version.BuildInfo{Version:"v3.4.1", GitCommit:"c4e74854886b2efe3321e185578e6db9be0a6e29", GitTreeState:"clean", GoVersion:"go1.14.11"}

Other
Fix for this can be to include the following in all templates:
namespace: {{ .Release.Namespace }}

I am inclined to agree with @bacongobbler (a core maintainer of helm) in his comment: https://github.com/helm/helm/issues/5465#issuecomment-473942223. His idea is that we shouldn't create a situation where users have to use the same namespace in helm template and kubectl apply.
The current state of this chart should allow you to use: helm template | kubectl create --namespace foo -f -
However, I am not 100% sure this will work properly because {{ .Release.Namespace }} is included in rbac/airflow-rolebinding.yaml#L18, meaning helm template will reference Role objects in the default namespace.
I'm not sure if there is something we can do about this?

However, I believe you should deploy things on Kubernetes (including this chart) with a tool like Argo-CD, which does not have this issue.

Thanks for looking into this!

I am inclined to agree with @bacongobbler (a core maintainer of helm) in his comment: helm/helm#5465 (comment). His idea is that we shouldn't create a situation where users have to use the same namespace in helm template and kubectl apply.

I agree, I think you shouldn't have to provide namespace to kubectl apply if you use helm. To ensure that many charts use namespace: {{.Release.Namespace}} in templates. This method also fixes inconsistency where state resulting from helm install --namespace X differs from helm template --namespace X output.
If you look at the issue you linked many PRs that mention it actually implemented namespace: {{.Release.Namespace}} method.

The current state of this chart should allow you to use: helm template | kubectl create --namespace foo -f -
However, I am not 100% sure this will work properly because {{ .Release.Namespace }} is included in rbac/airflow-rolebinding.yaml#L18, meaning helm template will reference Role objects in the default namespace.

Yes you're right things will break unless you explicitly use --namespace parameter for both helm template and kubectl apply.

I'm not sure if there is something we can do about this?

We can fix this by including namespace: {{.Release.Namespace}} in all templates. This is a very simple and low risk change, many charts do exactly that.
An alternative solution used by some charts is to set namespace in the values file and include that in the templates.
If you're OK with one of the solutions I'd be happy to submit a PR.

However, I believe you should deploy things on Kubernetes (including this chart) with a tool like Argo-CD, which does not have this issue.

Yes I do use gitops tooling for deployments but some tools are still affected by this problem.

This is still the case. I'd be happy to submit PR if the project is OK with using the namespace: {{.Release.Namespace}} workaround

@jacekn since the current state isn't really breaking anything, and the author of helm doesn't intend namespaces to be hard coded, I don't see a reason to change it.
Unless there is something which is broken as a result?

@jacekn since the current state isn't really breaking anything, and the author of helm doesn't intend namespaces to be hard coded, I don't see a reason to change it.
Unless there is something which is broken as a result?

The problem does not affect everyone but the chart is currently broken for some use cases.
If somebody runs helm template --namespace mynamespace | kubectl apply they end up with broken airflow. That's because RoleBinding will refer to the ServiceAccount in the mynamespace but the ServiceAccount and other resources will actually be deployed to the default namespace specified in the kubeconfig.
Those using tools like flux v1 (gitops) to apply k8s manifests have to use helm template with --namespace and then manually edit manifests to add namespace to each resource.
Impact of above is reduced usability. I understand that ideally best practices should be followed closely but in this case that reduces usability of the chart. From what I can see it's quite common for charts to include namespace in manifests. In the stable chart repo 149 out of 282 charts do that so it's certainly very common approach.


CentOS/RHEL RPM

Hello! We created rpm for this daemon and init script, so maybe you mention our repo for rhel users in readme?
http://vortex-rpm.org -- repo
https://github.com/vortex-rpm/bloomd -- spec for bloomd

@penpen Could you update rpm for the latest release of bloomd ?


Docs: update README on how to install the package

Spartak UI was published to the npm registry.
This required updating the project README with a new section on how to install it using npm and yarn package managers.
🙌 Contributions are welcome! Leave a comment if you want to help with this issue.

'm new to open-sourcing and I have no clue about what I should be doing. Can anyone guide me? I have basic knowledge of java
let me know in which way I can help you.

I'm new to open-sourcing and I have no clue about what I should be doing. Can anyone guide me? I have basic knowledge of java
let me know in which way I can help you.

Hello @jaswanthg76! Thanks for your interest in contributing to the project.
I'll guide you through your first contribution.
This issue doesn't require coding, but to update a markdown file – README.md.

Open the link above and click on the Raw button and get familiar with the structure of the document.
Read this documentation page on how to write and format markdown files.
This project is for the JavaScript ecosystem and there are two widespread package managers npm and yarn. Read the docs on how to install packages from npm registry. You can also look at the other JavaScript projects and what they "How to install" sections say.

In the end, we should have two commands for npm and yarn package managers that install the Spartak UI package from the registry.
When we agree on the content for a new section, I will help you to create a pull request and contribute.
Let me know if you have any questions.

@shdq : Since no one is assigned to this task till now, I have completed this task and created a new pull request. Please review.
https://github.com/shdq/spartak-ui/pull/69

Welcome @Hari0006 👋
Thank you for your time and willingness to contribute. Although it is a minor change, I would appreciate it if you could discuss your proposed changes here in the issue before opening a pull request. This will help prevent the rejection of your future contributions not only in this project but also in others.
I will review your pull request and provide comments there, if necessary. Let's continue our conversation in the pull request.

@shdq : Sure, I will follow this best Practice in future contributions.

@Hari0006 congratulations on your first contribution! 🎉🎊
By making this contribution, you have not only added value to the project but have also become an integral part of the open-source community. I encourage you to continue exploring and learning in this exciting world of software development.
Once again, congratulations on this achievement, and thank you for being a part of our growing community of developers. Keep up the fantastic work! 👍


Runs handle_deps as prepreq for images

Issue #, if available:
Description of changes:
Most builds with deps like this need them for their images. The way it was it would only run the target during the build target so if someone ran make images it would fail due to missing the deps.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest


Upgrade client libraries to require Java 7

https://github.com/wildfly/wildfly-core/pull/1171

We have to go to JDK 7 because some of the dependencies require 7. But we're making the minimum possible move.


Possible ReDoS in Crypto or Investment Spam

Positive ReDoS test results are obtained in both patterns, their integration in chatbots risks the availability of the service.
(earn|mak|made).*?[\d.,]+?k
[\d.,]+?k.*?profit

Evidence is attached

Tool: Devina.io

Thanks for your report, @J020203.
In this case, the expression is analyzed by the Discord automod directly, so no problems on our side regarding availability for any bots. Also, I believe they only search for the first match, so I don't think this would cause an issue for Discord either.


Added Basics of Site

Added the bare bones of the site to the repository including Bootstrap
files.

...done?


Fix Readme

Fix anonymous classes in Readme

Hi @cypressious, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Thanks for the contribution!


change default keyboard shortcuts

After a recent update, I found that I wasn't able to change tabs in my browser, terminal, messaging client, and other programs, using the Ctrl+PgUp and Ctrl+PgDn shortcuts.
It turned out that during the update, QRedshift overrode those shortcuts without my knowledge—I was able to figure this out only after scouring the internet until I found someone else who'd had the same problem and managed to figure it out.  Like them, I was worried something had broken.
The Ctrl+PgUp and Ctrl+PgDn shortcuts are the default way to alternate between tabs in nearly every program I've ever used that has tabs (and in many cases it's hard-coded).  QRedshift should not override any system-level keyboard shortcuts, much less these.  At worst it should tell the user that there are new shortcuts available that need to be set.  QRedshift is the sort of program you expect to set up once and ignore unless something changes, and not the sort of program you expect to make it impossible to switch between tabs just because there's a new version.
Note: this functionality was added in #9 based on #8.

I will remove that o next release, was a big mistake... that happens... =D

Fixed https://github.com/raphaelquintao/QRedshift/commit/e78d13da7e158f9891df4e9fdd1ca53a1885ecda#diff-fdf323b43304316f2a5ef56a0fbb6487d222e35617efeb0f8309fb7cdf00c8fc


Juggernaut/add cw20 support

This is a draft pull Request (Work in Progress!)

used cw20::Balance instead of String in InitMsg::denom and Config::denom
Changed handle_bond to accept native of cw20 balance. That means accepting sender: HumanAddr, amount: cw20::Balance instead of info: MessageInfo.
handle_bond is now accepting incoming tokens using a switch on config.denom. Kept the current logic for native case.
Update handle_claim to release either native token (as now) or cw20-token (used unimplemented!() now, implemented using a match case.
@ethanfrey please review these changes.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you for reviewing. I will come up with the optimized code in the next commit.

I got a notification, but the last commit was 12 days ago.
Happy to review if there is some new code pushed.


Update azure-percept-devkit-container-release-notes.md

Published released notes for Jan sprint release.

@tsampige : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

#sign-off

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Digitalocean logo upload + PR139 Updates

[x] Create image upload in modal
[x] Upload image to Digital ocean in route
update model
[x] Display image in product attribute timeline css
[x] PR139 remove blobs in models
[x] PR139 migration changes + this PR migration changes for models
[x] PR139 hexadecimal URL changes
[x] PR139 hyphenate supplier_product changes
[x] PR140 Changes

Migrations Tested and successful
File upload works and Displays company logo - upload service will be updated in future PR
Previous PR Comments changed/fixed in this PR

Image Input in Add Modal

Image in View Modal


chore: add ci action

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation update
[x] CI

Checklist

[x] I have performed a self-review of my own code.
[x] My code is commented, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] New and existing unit tests pass locally with my changes.
[ ] Any dependent changes have been merged and published in downstream modules.

Further Comments

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:

The review I left doesn’t seem to be a critical issue, so I will approve it.
Thank you!

I love your work, overlay-kit! Let's go🚀


Static DAG visualisation with graphviz

NOTE: not ready for PR yet, will finalize
NOTE2: my first serious PR, don't judge too quickly
Description
adds luigi.tools.staticviz module, that generates a static (png, pdf, svg) visualization of Luigi Dag
Discussed in #2328

Motivation and Context
In many cases, it is useful to render your task graph as a diagram - for documentation or presentation purposes. staticviz does exactly that - you can render your graphs on the fly (to README.md, for example), apply fancy styles for the presentations - or store it as an svg  and hand out to a professional designer.
Have you tested this? If so, how?

work in progress
has no interaction with the main body of code

Tasks and Goals

[x] proof of concept (only supports Python 3)
[ ] fix environments
[ ] make it work on Py 2.7
[ ] add tests
[ ] add support for non-unified styles, add default style (or styles)
[ ] add support for subgraphs, multiple end-points, complex layouts
[ ] beg for PR

@Casyfill Where there any developments of this feature in a different PR?