Who can see what about your sealed record?

"Sealing your juvenile record means that most people and employers won’t see anything at all about your juvenile record." - Who is “most people”? Does not seeing anything at all include the fact that it exists?
-- Question posted on different platform being copied here.

Answer: Good points. Ideas on how to make that more clear would be quite welcome! “Most people” is people who aren’t police officers, judges looking at your case, employers who don’t need federal background checks, etc. "Not seeing anything" means not seeing anything at all, including the fact that it exists.

Gave it a shot. Let me know what you think.


Auto tune proposes doses that do not match the minimal dose of the pump

When running auto tune function, the app proposes doses which are not multiples of the pump minimal possible dose. For example, for OmniPod Dash, the minimal dose is 0,05, but the app proposes to have doses like 0.81 or 0.94 (as in the attached picture).

Noted. Will add a better rounding.


 Nothing about
have you edited the missionfile?: No
Issue:
AI vehicles get oftenly stuck when crossing a bridge, SDK reinforcements included
Screenshots: https://imgur.com/a/XDxXNPF
I found this thread about it
https://forums.bohemia.net/forums/topic/201641-ai-can-not-drive-on-wooden-bridges-on-tanoa/

Solved in the best way possible in the next patch


Add handle exception screen

Please verify the following:

[x] yarn ci:test jest tests pass with new tests, if relevant
[x] README.md has been updated with your changes, if relevant

Describe your PR
As we know, when the app has a JS exception, it will throw White screen instead Red screen in release mode. So i added error screen let user can reload app when some exception was happened. Its look like bellow:

:tada: This PR is included in version 7.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Document phased execution

Why: Sub of #762
What: Update documentation to explain new phased execution flow
Scope of work:

[ ] Update if-docs pages to explain new phased flow
[ ] Update CLI docs to explain new commands and subcommands

Please review the PR 🙏


Broken foreigner sorting at global leaderboard

Describe the bug
At global leaderboards page, foreigner users sorting is "ZZ" not "XX"
To reproduce
Steps to reproduce the behavior:

Go to 'https://takuji.nkrw.dev/leaderboard'
Sort by "Estrangeiro"
See error, which is a blank page, not showing any foreigner users

Expected behavior
Show all foreigner users in page.
Screenshots

I've changed the foreigner country to xx to represent the unidentified country code as defined here
this should work fine
https://takuji.nkrw.dev/leaderboard/std/pp/vn/XX
I think we just need to change the option value on the dropdown menu for it to work correctly


Additional Parameter for Source & Target DB

Would be great if you could add two parameters. One for Source_database and another for destination_database.
Example would be a clone of ABC_RAW.DBO to ABC_CLONE.DBO.
dbt run-operation clone_schema --args "{'source_database': 'abc_raw', 'source_schema': 'analytics', 'detination_database': 'abc_clone', 'destination_schema': 'analytics'}"
Thanks!

Thanks Cody, that's a great point. I'll try to get this done within the next few days.

Resolved in merged PR #10 by @jtalmi. I'll issue a new release soon.


Update Post::create to initialize instances the way Timber 2.0 expects

https://github.com/sitecrafting/conifer/blob/ed2f07db2c8ff0769218df5f71ee0f835f9f4870/lib/Conifer/Post/Post.php#L360
Post::create initializes the posts is creates by instantiating the class directly, but Timber 2.0 expects you to use Timber::get_post

already fixed in the timber-2.x branch/PR.


install error : No such kernel named .net-csharp

when I run the first cell, I got an error :
"NoSuchKernel: No such kernel named .net-csharp"

Good afternoon, indeed, there is a problem. Thanks for the information. The reason is to update Linux in Google Colab. This template is designed for Ubuntu 20.04, and Google Colab is now 22.04. At the moment, the templates are updated and successfully install the C# or F# kernel in Google Colab.


Update Updates “releases”

Automatically generated by Netlify CMS

Deploy preview for netlify-cms-www ready!
Built with commit 873934dd28759a33a9ee71b41225eddabb3f70cd
https://deploy-preview-1379--netlify-cms-www.netlify.com


Wrong type when retrieving multiple related records using fluent API

Bug description
Similar to #5715, but slightly different.
How to reproduce
// BAD -> pieces: Piece[], should be pieces: Piece[] | null
const pieces = await prisma.composer
  .findUnique({
    where: {
      id: composer.id,
    },
  })
  .pieces();

// If the composer is not found, it will be null, even though its type is Piece[].
// TypeError: Cannot read property 'length' of null
consoloe.log(pieces.length);

Expected behavior
pieces must be of type Piece[] | null , or .pieces() must be available only if rejectOnNotFound: true.
Prisma information
model Composer {
  id        String        @id @default(cuid())
  pieces    Piece[]
  createdAt DateTime      @default(now())
  updatedAt DateTime      @updatedAt
}

model Piece {
  id         String        @id @default(cuid())
  composer   Composer      @relation(fields: [composerId], references: [id])
  composerId String
  createdAt  DateTime      @default(now())
  updatedAt  DateTime      @updatedAt
}

Environment & setup

OS: Mac OS
Database: PostgreSQL
Node.js version: 16.5.0

Prisma Version
3.6.0

Happens to me with the following versions:
Environment & setup

OS: Linux / docker alpine
Database: MySQL / MariaDB
Node.js version: 14-alpine

Prisma Version
3.9.1


Make design title not required

Goal
Remove the requirement for design title for lowering steps to purchase.
Requirements
Make it possible to add a design to basket without at title.
Give it a default title of "familietræ" / "family tree" if there is no title.

Closed due to moving issues to Jira


Update tenant-management-check-tenant-creation-permission.md

@kengaderdus
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@kengaderdus fixed.

#sign-off


Rock Paper Scissors Game in Python

I want to add a CLI-based Rock-Paper-Scissors game written in Python to Programming-Basics/Python/Games.

Thanks!


Update to offer management schema

moved "required" from property definition to allOf schema clauses
numerous corrections of typos and some examples that didn't validate
some file formatting (line breaks)

@jbeckert - Thanks for the cleanup and improvements, much appreciated. It will take me some time to review in detail. I will start doing so right away.


Port Reprepro Release Job Recipe for .deb

Description
Reprepro is the one responsible for assembling a private .deb repo. Let's enable it.
Expected Behavior
User can source .deb repo using apt.
Current Behavior
User is unable to source .deb repo using apt.
Associated Data Files
No response

Wiki tested is capable of housing all the publication artifacts. Begin development.

Implemented.


Az PowerShell module path should not be /usr/share

Description
Azure PowerShell is installed as part of this image, but the path chosen makes it very difficult to import as it's not in the default $env:PSModulePath.  This results in needing to reinstall the modules when running in a VMSS in Azure DevOps as the path is inaccessible to the AzDevOps user even when using a fully qualified module path of /usr/share/az_9.3.0/Az/9.3.0/Az.psm1.  This results in extra unnecessary churn since the modules are already in the system.   Please use a path in the default $env:PSModulePath so that it can be easily referenced when using AzureCLI@2 pscore tasks as it's the only way to obtain the service principal credential for passing to the GenerateImageAndResources script.
I understand that building these images in CI isn't exactly supported, but the larger problem exists in the Microsoft hosted agents from what I've seen as well for any AzureCLI@2 pscore task.
recommended paths: /usr/local/share/powershell/Modules, /opt/microsoft/powershell/7/Modules
The issue occurs in Install-AzureModules.ps1 on line 8
# Get modules content from toolset
$modules = (Get-ToolsetContent).azureModules
$installPSModulePath = "/usr/share"

Pipeline code being executed:
try {
    Import-Module /usr/share/az_9.3.0/Az/9.3.0/Az.psm1 # also tried just Az
}
catch {
   Install-Module -Name Az -Scope CurrentUser -Repository PSGallery -Force
   Import-Module Az
 }

Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 18.04
[X] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
3.218.0
Is it regression?
unknown
Expected behavior
Az Powershell module should be importable from AzureCLI tasks
Actual behavior
Module fails to be located, forcing it to reach out to PowerShellGallery.
Repro steps

Use ubuntu:latest MS Hosted or Private agent from runner-images repo
Run a task on AzureCLI@2 that's pscore with the script trying to import Az module
Module isn't found as it's not in the path

Sorry, but I did`t get clearly. Are you using in your pipelines Windows or Ubuntu images?

I'm using Windows, and will be using MacOS in the future.
OP was using Ubuntu, but I don't.

There are instances when using the Azure CLI task is preferred over using the AzurePowerShell task.  For example when you need to access the service principal credentials, which can only be done with AzureCLI.  I may be barking up the wrong tree here, but it seems to me that this is more easily/quickly resolved with the addition of something like a symlink or changing to a default path than having the ADO team update the task.

@cumpstey @icornett hey!
Apart from what @sergei-pyshnoi has mentioned, we can not install the modules different way because we may install lots of Az versions in parallel  and they and their dependencies conflict between each other


migrate to sbt/launcher to using sbt 1 but target old JVM

Ref https://github.com/sbt/sbt/pull/4470

I'm not understanding what this is about. Is it still relevant?

Yea. It's been fixed I think - https://github.com/sbt/launcher/blame/1.x/project/build.properties


CAMEL-17866: fix CamelSqlGeneratedKeyRows issue.

CamelSqlGeneratedKeyRows is not populated if already exists because input
headers were overwriting the new output header.
Change code to set headers on input message instead of using deprecated
getOut() method. Ensure that input body is set to null in case of EMPTY_RESULT
on SelectOne queries.

Thanks @oscerd; I'll merge when the pr build check is done. The checkstyle failure is not due to my changes.


feat: SWA 86 Photo upload

The type of this PR is: TYPE
SWA-85 Photo Upload process on submission flow

[x] Implementation of the designs

[ ] Add functionality

Open topics

[ ] Should we have CTAButtons as separate part of the app or not?

This PR resolves []
Description

PR Checklist (tick all before merging)

[ ] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[ ] I have tested my changes on iOS and Android.
[ ] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[ ] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added an app state migration, or my changes do not require one. (What are migrations?)
[ ] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against e9625d09e61601bcfe82920f9ef8a4624aefdcd0

Replaced by https://github.com/artsy/eigen/pull/6021

replaced by https://github.com/artsy/eigen/pull/6021


How to just capture screenshot of the window?

Right now, headless.take_screenshot('./somefile.jpg') works great!
But the saved file has all the Menubar, address bar, scrollbar attached.
Is there any other function call or params that can be passed to just capture the content window only without the Menubars,status bar, scroll bar, ..etc.??

Currently there is no way to do it via headless. Maybe you can figure it out yourself if you definitely need it. Headless uses import utility from imagemagick and it can accept window id or name (see - man - http://www.imagemagick.org/script/command-line-options.php?ImageMagick=op7slcr8l6l27lekiqiif8e6t2#write), you can pass id/name to take_screenshot method and put it instead of root. (See - https://github.com/leonid-shevtsov/headless/blob/master/lib/headless.rb#L118)


Rumble support?

Does inputs support the rumble functionality in most gamepads? I realize that's output rather than input but it still seems appropriate.
Thank you for the library! I'm using it to write a scratch 2.0 extension so our CoderDojo can have kids use the full functionality of the gamepads; currently we're limited to mapping buttons to keyboard keys and one of the sticks to the mouse with third party software.
All I'm missing is rumble functionality.
One question though, is there a list of what all the ev_types and codes mean? For example, I currently completely ignore SYN_DROPPED and others, only use events with types Key and Absolute actually. I'm not sure how robust this 🙈 approach is.

Oh and how about sixaxis support? This'd just be a bonus though.

Your extension sounds great.
Rumble support on the Xbox controller should be possible since I have used that before.
Sixaxis should work over USB, Bluetooth support is on my TODO list.
Your approach is probably fine. Ignore events that you do not care about. I throw everything that evdev gives into InputEvent objects (and emulate that behaviour on Windows+Mac), sync and dropped etc are a bit over-specific for users to care about.

So Rumble already works on Windows.
import inputs
gamepad = inputs.devices.gamepads[0]
gamepad.set_vibration(1,1)
to stop it
gamepad.set_vibration(0,0)

Oh, cool. Most kids'll be running windows anyway. Just makes it harder for me to test 🤷♂. Is the speed variable between 0 and 1, or multiples of 1?

Seems like it's between 0 and 1. Could you throw a NotImplementedException instead of/in addition to printing that the feature is not supported? Rn it's hard to programmatically verify whether the function works or not so I have to duplicate the platform check.

Ok will do. I just managed to make rumble work on Linux so will tidy up that and add it to inputs soon.

So the code is now in github version, it will be in a new release on pypi in a week or two.

Oh, well that could've saved me some work. I just implemented all the timing necessary around the set(x,y)/set(0,0) calls : )
Is the method synchronous? Can it be cancelled?  Can I read data while rumbling?
Btw, by sixaxis I didn't mean the controller but the rotation/acceleration sensing, is that supported? I couldn't find it in the data but maybe I didn't look hard enough.

Thank you for the work btw, it's very much appreciated.

Ok the whole topic of asyncio and inputs is something I am thinking about for a future task. For now I have made the delay and stop be in a subprocess.
So now using gamepad.set_vibration(left_motor, right_motor, duration) should not block you reading data when rumbling.
If you call gamepad.set_vibration and want to stop it earlier than duration, then you can call gamepad._stop_vibration_win()

Hmm, so if (0, 0, 0) works, would (x, y, z) also work, where those are different from the previous call?
Did you miss the sixaxis part of my question?

Well the Xbox 360 controller has no motion detection. The playstation ones do, they probably report those events on Linux. I have it in my todo list to study those controllers (also see #29 ).

If you use gamepad.set_vibration(left_motor, right_motor, duration), then a new call will override the previous call, however, on Windows, it is theoretically possible to get a race condition if you do:
start A - duration 3 secs
start B - duration 5 secs
end A - happens killing the last 2 seconds of B

So you can either manage the delays yourself by using the _start and _stop methods, or let the user figure it out. I think with scratch the user can replay and see (I am a scratch fan too).
However, if it proves a problem, I can look into killing A's reset when B happens.

Hey @zeth:
So I've been looking at integrating a Logitech Wireless Gamepad F710 for a Raspberry Pi project I'm working on.  I didn't want to implement the interface to the gamepad if I could avoid it, and was pleasantly surprised to find this project.  I was able to test the gamepad and have very precise data coming in as I test all of the buttons and such.  Though I don't need it, I also attempted to test rumble support -- it didn't work.
Here is my traceback:
>>> pads[0].set_vibration(1, 1, 1000)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/pi/.virtualenvs/lawnrover/lib/python3.5/site-packages/inputs.py", line 2983, in set_vibration
    self._set_vibration_nix(left_motor, right_motor, duration)
  File "/home/pi/.virtualenvs/lawnrover/lib/python3.5/site-packages/inputs.py", line 2969, in _set_vibration_nix
    code = self.__get_vibration_code(left_motor, right_motor, duration)
  File "/home/pi/.virtualenvs/lawnrover/lib/python3.5/site-packages/inputs.py", line 2963, in __get_vibration_code
    buf_conts = ioctl(self._write_device,<PHONE_NUMBER>, inner_event)
OSError: [Errno 14] Bad address

As I have studied the voodoo that is going on there, it appears that you had implemented the ff_rumble_effect, however, when calculating the _IOW Linux macro, you came up with<PHONE_NUMBER>.  When I did a similar exercise (based upon Linux C code here: https://github.com/torvalds/linux/blob/master/include/uapi/linux/input.h), I came up with<PHONE_NUMBER>.  Simply changing the constant to my calculated value allowed the rumble feature to work for me quite nicely.
HOWEVER, the magic number in the code doesn't really contribute to solid software maintainability.  Additionally, as I studied what is occurring in this code, it appears that a new rumble object is defined and sent to the gamepad every time you call set_vibration.  On my device, it starts to fail with a memory error after about 4-5 repeated calls.
>>> pads[0].set_vibration(1, 1, 500)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/pi/lawnrover/inputs.py", line 3223, in set_vibration
    self._set_vibration_nix(left_motor, right_motor, duration)
  File "/home/pi/lawnrover/inputs.py", line 3191, in _set_vibration_nix
    code = self.__get_vibration_code(left_motor, right_motor, duration)
  File "/home/pi/lawnrover/inputs.py", line 3185, in __get_vibration_code
    buf_conts = ioctl(self._write_device,<PHONE_NUMBER>, inner_event)
OSError: [Errno 28] No space left on device

Now, I definitely understand that voodoo and am willing to help, however, don't want to stick my nose where it doesn't belong.  I can certainly cobble together a PR, but from what I can tell (studying this code: https://github.com/flosse/linuxconsole/blob/master/utils/fftest.c), it appears that there are varying rumble mechanisms supported by various gamepads.  Coming up with a universal rumble pattern may be tricky and so a more dynamic definition based upon connected devices might make more sense.  This is probably why the rumble PR you submitted worked for you but not for me (though from what I can read on the struct definition, I still think you would have calculated the same magic number as I did, so I am not sure why mine is different).
Anyway - how would you like to proceed?  How can I help?


Linking large number of cell suspensions to an analysis file

Dataset/group this task is for:

conservedCellTypesHumanMouse #563

Link to Ingest
Spreadsheet (Drive)
see related dev ticket: ebi-ait/dcp-ingest-central#590
Description:
This dataset is a big SMART-seq experiment with 49418 cell suspensions, with managed access data. Therefore, there are no FASTQ files available, and the authors have published a count matrix file that has to be linked to all the cell suspensions. The resulting string is not accepted by Excel at the corresponding cell, as it is too large.
See meeting summary by Irene and Amnon
Alternatives (arbitrarily ordered):

Leave “analysis file.cell suspension id” empty, load the spread sheet and update the links to sequence file using the api
Add a worksheet to represent the link between an analysis file and sequence file.
Use “synthetic” cell suspension ids for each cell type and patient (despite the experiment having just a single cell suspension per individual cell)

a more details analysis of the solutions is in the meeting summary.
If loading the data to ingest is urgent, we'll start with 2, otherwise - we shall choose 1.

Ingest yields an "out of RAM" error when trying to upload the spreadsheet.
Tests performed

Upload the spreadsheet with the correct information - Causes Ingest to break
Upload the spreadsheet with invalid metadata (not allowed values at specimen_from_organism.preservation_storage.storage_method) - It does not break, Ingest shows the status "Metadata Invalid"

There is another issue beyond the memory issue, it seems..

this will be picked up on the Stanford meeting to discuss this. the work can be revised afterwards.

Still pending discussion with the UCSC wranglers

We agreed on aggregating the cell suspensions per donor and cell type and including as supplementary material the metadata.csv file provided by the authors, with all the information of a cell level. It has to be clear that that file is available and what information contains. As this only includes analysis files, would not affect the pipelines downstream.
This would change in this specific situation how we model an SS2 dataset, making it similar to a 10X modeling.


add Portugal, Poland, Spain, Switzerland, UK, Austria, Italy, Germany

Before merge make sure the following checklist is complete:
Portugal

[x] Missing symlink
[x] Manually correct MT translation: Precinct -> Distrito

Poland

[ ] forms are a copy of Switzerland, including Canton as administrative region. This needs to be updated. Then, we'll need another PR with the updated region name. Currently it is using the string for US State.
[x] Missing symlink

Spain

[x] Missing symlink

Switzerland

[x] Done!

UK

[ ] test that filters work for UK which doesn't have an administrative region (US state, CA province, FR department, etc.) for its form

Austria

[x] Manually correct MT translation: Federal State -> Bundesland (Nate)
[x] Missing symlink

Italy

[x] Missing symlink

Germany

[x] Manually correct MT translation: State -> Land (Nate)
[x] Confirm that German states should be called "Land" rather than "Bundesland" as in Austria (Nate)

For all of the above we should also be testing that the data loads, language navigation, form navigation, maps, and filtering.

wait, it says before merge, ensure the checlist is done. I haen't odne that. :-/

@awong-dev just commented out UK / Poland. I'll follow up on the Poland form + UK state filter tomorrow


Cookies import doesn't work, cannot add the integration

Hello,
After upgrade to the latest current version (v3.2.2), the integration stopped working. Reinstalled it and tried to add it again, but it always fails with this:
Logger: custom_components.alexa_media.config_flow
Source: custom_components/alexa_media/config_flow.py:203
Integration: Alexa Media Player (documentation, issues)
First occurred: 3:47:06 PM (28 occurrences)
Last logged: 4:10:09 PM

Unknown error: load_cookie() got an unexpected keyword argument 'cookies_txt'

Tried paste all 4 lines of alexa.amazon.com data from exported 'cookies.txt' contents to the integration's "Cookies.txt data" field - fail.
Tried to add exported 'cookies.txt' file contents into<EMAIL_ADDRESS>- same result.
I wanted to rollback to the version prior to 3.1.0, but it does not appear in the HACS reinstallation list.
Please advise how can I fix this?

Please fill out the template.

I am not really sure what template I should fill out. Could you please clarify that for me? Thanks.

The bug report template.

Describe the bug
Cannot add alexa_media_player integration
Steps to reproduce the behavior:
Configuration > Integrations > "+ button" > Alexa media player
then filled up the requested data as follows:
email address<EMAIL_ADDRESS>(existing user)
Password: my_password
2FA Code: current 2FA code
Amazon region: amazon.com
check "Advanced debuging" checkbox
Cookies.txt data: pasted the cookies.txt lines containing "alexa.amazon.com" (4 lines)*

Also tried instead to add exported 'cookies.txt' file contents containing "alexa.amazon.com" lines into<EMAIL_ADDRESS>as suggested in the manual. Same result.

Expected behavior
Succesfully adding integration
Screenshots
n/a
System details
Home Assistant 0.114.6
Hassio (Yes/No): Yes
alexa_media version: v3.2.2
Logs
Logger: custom_components.alexa_media.config_flow
Source: custom_components/alexa_media/config_flow.py:203
Integration: Alexa Media Player (documentation, issues)

Unknown error: load_cookie() got an unexpected keyword argument 'cookies_txt'

Additional context
Before upgrading alexa_media to v3.1+ when cookie import was first introduced, everything worked fine.

Your alexapy is outdated. Please make sure you didn't manually install it ever in the custom_components directory.

You were absolutely right. I did have alexapy manually installed some while ago for some experiment in hassio's /config/alexapy directory, but I didn't think that would anyhow affect this as it was installed in another directory. And strange that reinstall or downgrade of the alexa media player integration did not help. Anyways I removed all stuff related to alexapy and reinstalled the integration - and after everything worked straight away.
Thank you very much for your help pointing out my own mistake.


Increase map tilt to 90 degrees

Is your feature request related to a problem? Please describe.
Current tilt limitation (60 degrees) does not allow to see a full perspective without zooming out. Mapbox doesn't have such a limitation.
Describe the solution you'd like
Remove tilt limitation.
Describe alternatives you've considered
Keep as is
Additional context
Add any other context or screenshots about the feature request here.

We increased the maximum allowed value in MapLibre GL JS.

@wipfli I searched for an issue / PR but couldn't find one. Do you know what it was changed to?

I think the trick is to look for "pitch" and not for "tilt"

https://github.com/maplibre/maplibre-gl-js/pull/574

Allowing lower zoom level tiles to load in the distance would help with this: https://github.com/maplibre/maplibre-native/pull/2958


前端日志获取超时，重新编译之后可以看到，过一段时间就消失了

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

有日志么

有日志没

有日志么

没有啊

有日志么

没有啊  get remote log timeout


Virtctl: cancel migrate

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

The command `migrate-cancel` was added to virtctl. It cancels an active VM migration.
Usage: `virtctl migrate-cancel vminame`

Hello,
Some comments/questions:

Some functional tests for virtctl migrate_cancel are to be added later.
Current implementation gets a list of migrations, finds the active one and deletes it. Is there a way to get the active migration from the VMI without searching for it ?
The list of migrations is filtered for a specific VMI. Is there a way to enhance the filter to only return the active migration?

Some comments/questions:

Some functional tests for virtctl migrate_cancel are to be added later.
Current implementation gets a list of migrations, finds the active one and deletes it. Is there a way to get the active migration from the VMI without searching for it ?

Nope. There's info about a migration on the VMI, but that info is only set once the migration target pod is ready. The only way (with how things currently work) to reliably cancel a migration is to perform the list call using the label selector like you've done.

The list of migrations is filtered for a specific VMI. Is there a way to enhance the filter to only return the active migration?

yes. you'd need to add a label to the migration objects in the mutation webhook at CREATE time, then remove that label in the migration controller once the migration reaches a finalized state.
This likely isn't necessary. Realistically I think we should start cleaning up (garbage collecting) old migrations so the per vmi migration list never grows very log to begin with.

/hold

What changed on v3:

git rebase origin/main
rename 'errml' to 'err' and 'miglist' to 'migrations'
functional tests added, reusing existing migration-delete tests and adding  cancelling the migration with virtctl

What changed on v2:

git rebase origin/main
rename 'migrate_cancel' to 'migrate-cancel'

/unhold

What changed on v4:

git rebase origin/main
replace It() and function calls with a table for testing different values of a parameter (with/out virtctl)

I slightly changed the string to make the line shorter. If it's important I'll change it back

Currently (as it was from v1) several cancel-migrations with delete/virtctl are added. That means more tests but also test time is a bit longer. If a single virtctl test is enough, the last two patches can be dropped.
If preferred, I can squash the last patch (move code into a function) into the previous 2 patches (test migration cancellation with virtctl).

/retest

/ok-to-test

DO we also have a userguide update for this new change?

Hi @fabiand,
Currently, the user manual mentions neither 'virtctl migrate' nor 'virtctl migrate-cancel'.
I can add those to e.g. docs/operations/live_migration.md

@fabiand, I sent a PR for the user-guide


diagrams

should add something like https://github.com/tgdwyer/WebCola or https://github.com/cpettitt/dagre-d3
for automatic layout of diagrams.  also possible to do something more like visio eg http://www.jointjs.com/ https://github.com/sporritt/jsplumb/ seems related
http://www.draw2d.org/draw2d/ and http://gojs.net/latest/index.html look cool but not open source.

There is some similar tools in the JavaScript world that take a markdown approach to describing and generating flow charts and diagrams.
Mermaid does both Flowcharts and Sequence diagrams - https://knsv.github.io/mermaid/#mermaid
Flowcharts - http://flowchart.js.org/
Sequence Diagrams - https://bramp.github.io/js-sequence-diagrams/

thanks for the ideas!

I was wondering if I wanted to fork and try building support for Mermaid in.  Would it be preferred to be built as a new cell type?  Because mermaid allows you to quickly draw diagrams using a markdown like syntax.
 %% Subgraph example
 graph TB
         subgraph one
         a1-->a2
         end
         subgraph two
         b1-->b2
         end
         subgraph three
         c1-->c2
         end
         c1-->a2

Will produce the following diagram.

btw, if you do this I would be interested in a pull request!  we have a standard CLA...


.NET DateTime always mapped to SQL datetime type loosing accuracy

A .NET DateTime value is always mapped to SQL datetime type loosing accuracy at least in the case, that the MS SQL type of the value is datetime2(7).
See DatabaseType.cs lines 50 and 68. For full accuracy it would be necessary to change the target type in the mapping to DbType.DateTime2 for DateTime and DateTime? type, in case that the target database tables corresponding column type is datetime2.

Hi, i noticed there is a possibility by introducing our own derived DatabaseType class and change the type mapping for DateTime and DateTime? there to DbType.DateTime2. But this would affect the whole database and we have a mixture of datetime and datetime2 columns. Will this still work? It would be nice if there would be a method in the mapping like WithSqlDbType(DbType dbType) so it is possible to do this for a single column and not for all columns in the database.
Best,
Michael

Is it fine to use following approach as workaround for the above mentioned solution (while introducing something like a mapping method WithSqlDbType(DbType dbType) is still the preferred implementation)?
internal class DateTimeValueService : EntityServiceBase<DateTimeEntity, int>, IDateTimeValueService
{
	public DateTimeValueService(IDbFactory dbFactory) : base(dbFactory)
	{
	}

	public override DateTimeEntity AddOrUpdate(DateTimeEntity entity)
	{
		throw new Exception("Do not use this method, use 'AddOrUpdateUsingDateTime2' instead!");
	}

	public override IQueryable<DateTimeEntity> Get()
	{
		throw new Exception("Do not use this method, use 'GetUsingDateTime2' instead!");
	}

	public DateTimeEntity AddOrUpdateUsingDateTime2(DateTimeEntity entity)
	{
		SetDateTimeDbTypesToDbTypeDateTime2();

		DateTimeEntity dateTimeEntity = base.AddOrUpdate(entity);

		RestoreDbTypes();

		return dateTimeEntity;
	}

	public IQueryable<DateTimeEntity> GetUsingDateTime2()
	{
		SetDateTimeDbTypesToDbTypeDateTime2();

		IQueryable<DateTimeEntity> dateTimeEntities = base.Get();

		RestoreDbTypes();

		return dateTimeEntities;
	}

	private DbType _dbTypeForDateTime;
	private DbType _dbTypeForNullableDateTime;

	private void SetDateTimeDbTypesToDbTypeDateTime2()
	{
		IDatabase database = GetDatabase();

		_dbTypeForDateTime = database.DatabaseType.LookupDbType(typeof(DateTime), null)
			.GetValueOrDefault(DbType.DateTime);
		_dbTypeForNullableDateTime = database.DatabaseType.LookupDbType(typeof(DateTime?), null)
			.GetValueOrDefault(DbType.DateTime);

		database.DatabaseType.AddTypeMap(typeof(DateTime), DbType.DateTime2);
		database.DatabaseType.AddTypeMap(typeof(DateTime?), DbType.DateTime2);
	}

	private void RestoreDbTypes()
	{
		IDatabase database = GetDatabase();

		database.DatabaseType.AddTypeMap(typeof(DateTime), _dbTypeForDateTime);
		database.DatabaseType.AddTypeMap(typeof(DateTime?), _dbTypeForNullableDateTime);
	}
}

I'm pretty sure we use both DateTime and DateTime2 and it wasn't this much work, infact I think it just worked with both.
I think we only cared about the date component going back to 0001 though.
There is a way to have each column specify the dbtype then you could have a mapper set the type. I'll have a look and see how we did it.

Hi, did you have time to take a look meanwhile?

Sorry for the delay, this is how it can be done.
    public class DateTime2Attribute : Attribute
    {

    }

    public class Test
    {
        [DateTime2]
        public DateTime MyDate { get; set; }
    }

    public class MyMapper : DefaultMapper
    {
        public override Func<object, object> GetToDbConverter(Type destType, MemberInfo sourceMemberInfo)
        {
            if (sourceMemberInfo.GetCustomAttribute<DateTime2Attribute>() != null)
            {
                return x => new SqlParameter("_", x) {SqlDbType = System.Data.SqlDbType.DateTime2};
            }

            return base.GetToDbConverter(destType, sourceMemberInfo);
        }
    }

    public class MyDb : Database
    {
        public MyDb(string connectionString, DatabaseType databaseType, DbProviderFactory provider) : base(connectionString, databaseType, provider)
        {
            Mappers.Add(new MyMapper());
        }
    }


docs: custom block needs to be adapted

I think since the newest release 0.5.1 the https://github.com/abersheeran/asgi-ratelimit#custom-block-handler is not correct anymore. I'm not sure about it but it seems to me it has to be adapted to the new setup, at least I had to do it today at work on mine
I'll try to come up with a test and change docs when time permits if someone doesnt figure it out before L_)

Ah, this is my negligence. Thanks for pointing out.
After you test and fix the document, if you think it is okay, you only need to publish a new tag 0.5.2, and the GitHub action will automatically push the new package to PyPi.

if you think it is okay, you only need to publish a new tag 0.5.2, and the GitHub action will automatically push the new package to PyPi.

Supplement: You can use python script/upload.py to ensure that __version__.py, pyproject.toml and git tags are updated at the same time.


feat: dynamic file imports

Closes #1405

How can the failing tests be fixed, @marvinhagemeister?

Any idea how to fix the failing tests, @marvinhagemeister?


Addign Open Vocabulary Segmentation to Demo

Hello!
Thank you for this great work! I was wondering if there is any easy way to extend the demo to include open-vocab segmentation?
Thank you!
Josh

@joshmyersdean  Hello, thanks again.
Our model aims to understand the mask-level region, including semantic categroy and short/long description, instead of directly outputing masks.

Thank you!


manifest cjhange chatgpt.com/*

in manifest it should be
chatgpt.com/*
instead of
chat.openai.com/*

thanks @imranaalam!


Adding y-care London event

This doesn't seem to be working. Can someone check for me?
Ta
Pete

(it just had an extra comma after the last event object)


[MariaDB/MySQL] export data from data editor in new table generate incorrect table DDL

DBeaver 7.3.1
Step to reproduce:

Open table data editor
Select "Export data" from data editor.
Choose as target MySQL/MariaDB database
Create new table name
See Target DDL

Result: some types mapped incorrect and without attributes (column length)

This syntax is incorrect for table creating.

Fixed

Fixed

verified

verified


Not able to reproduce results for FB15k-237

Can you please let know the hyperparameters you used for the results mentioned in paper.
When running with default hypermarater, I was not able to reproduce results.
Please find mrr metric value below, with default hyperparameter.
300
0.0010591120226308703
Validation:
Number of data points: 35070
Hits @10: 0.5104362703165098
Hits @3: 0.3603364699173082
Hits @1: 0.24342743085258056
Mean rank:<PHONE_NUMBER>24665
Mean reciprocal rank: 0.33071295056716465
Test:
Number of data points: 40932
Hits @10: 0.5053259063813154
Hits @3: 0.3573487735756865
Hits @1: 0.23783347991791265
Mean rank:<PHONE_NUMBER>1158017
Mean reciprocal rank: 0.32585497990251716
Please find below hyperparameters used for FB15K-237:
experiment = Experiment(model_name, num_iterations=300, batch_size=128, learning_rate=0.001,
decay_rate=0.99, ent_vec_dim=200, rel_vec_dim=200, cuda=True,
input_dropout=0.3, hidden_dropout=0.3, feature_map_dropout=0.2,
in_channels=1, out_channels=32, filt_h=1, filt_w=9, label_smoothing=0.1)

Hi, I just added a table with hyperparameter values for each dataset to the README. Hope this helps.

Thanks a lot.
I was able to reproduce results.


[version] Display version when booting operator

Operator shows it's version when it starts. This version information
is embedded inside the binary while building it. It is a good
practice to show the operator version when it is booting up.
Fixes https://github.com/habitat-sh/habitat-operator/issues/348

@krnowak I did not understand the part where you are saying

And our release steps will need to be extended with a check for a proper version of the operator.

I did not understand the part where you are saying

@surajssd: Basically, when doing a release of the operator, we want to make sure that the version it prints is something like v0.7.2, not v0.7.2-31-g9eae1e5d nor v0.7.2-31-g9eae1e5d-dirty nor v0.7.2-dirty.

@krnowak

And our release steps will need to be extended with a check for a proper version of the operator.

this is done :-)

LFAD if tests pass.


Can't use Function.prototype.bind on phantomjs 1.9

Hi,
I'm running prerender on Heroku (with a 2X dyno so 1GB of RAM) and using it for an Ember app. If a page is loaded a few times in quick succession, prerender fails to render my app properly on the third or fourth time. (Running the latest code from your repo v3.22.5.)
The issue seems to be coming from this:
phantom stdout: TypeError: 'undefined' is not a function (evaluating 'RegExp.prototype.test.bind(/^(data|aria)-[a-z_][a-z\d_.\-]*$/)')
This error happens everytime even when it's working, but then other errors pop up and the Ember app doesn't render at all. Is it maybe because this error is happening everytime that it eventually fails altogether?
Not really sure what to do to investigate this further or resolve the issue. Any help is appreciated. Thanks!

Edited original post to properly reflect what's happening after investigating a bit more.

Discovered from http://stackoverflow.com/a/34160714 that I need phantomjs 2.
I tried to use the phantomjs branch https://github.com/prerender/prerender/pull/266 from this repo but had to fork it and set it to create the phantom with --web-security=no to get around https://github.com/amir20/phantomjs-node/issues/345 and set its phantomjs to a fork of thoop's phantomjs fork and set phantomjs to 2.1.1 so it could download an available file from https://bitbucket.org/ariya/phantomjs/downloads/.
Overall, not a fun little hack, but it seems to work.
Feel free to close this issue, or close it once you're supporting phantomjs 2, since other people might have this problem where they can't prerender JS with Function.prototype.bind in it.

We actually have a shim that should load bind if it's not available, so it should be working in 1.9.8.
https://github.com/prerender/prerender/blob/master/lib/injections/bind.js
--web-security=no isn't great to run with security-wise, which is why we haven't upgraded to 2.1 yet.

Any idea why I was getting that error then on the latest prerender if the shim should handle it?
Also, out of curiousity, what does --web-security=no expose me to exactly? Is it something I should be concerned about?

web-security=no allows all requests to other domains and disables CORS. Since you are loading only pages on your website, that shouldn't be an issue, but it could be a possible attack vector.
You didn't have the disable injections flag set, did you? Otherwise, the bind shim should be loaded every time.

Thanks, good to know.
And nope, I don't have that flag set. Odd that it doesn't appear to be working for me.
I'm not too familiar with how prerender works, so I may be way off but the only thing I can think of is that the code that's erroring out isn't code that I include myself. I put a single line of Javascript to call Segment (https://segment.com/), which then has a Zendesk integration enabled. So it's technically getting added to the page later by Segment. Could that be it?

Hmm, I don't think so. Any javascript should execute just fine and if that injection was happening then bind would work too.

Weird then. I'll stick with my workaround for now, and once the issue with phantomjs 2 gets worked out and you're able to use it, I'll try switching back.

I just merged a new change into master to support PhantomJS 2.1 so this issue shouldn't be a problem any more. Feel free to reopen if you try it out and run into prototype.bind issues!

Working much better now. Thanks, @thoop.
I'm happy the restart-heroku hack is gone too. Nice work.

Yeah that restart shouldn't be needed anymore since we restart phantomjs after a certain number of iterations but let me know if you end up running into anything.


[BUG] HashAggregateSuite failure when AQE is enabled

Describe the bug
HashAggregateSuite has two failing test cases (SortAggregateExec is translated correctly ENABLE_HASH_OPTIMIZE_SORT=true and SortAggregateExec is translated correctly ENABLE_HASH_OPTIMIZE_SORT=false) when AQE is enabled
Steps/Code to reproduce bug
These tests are currently not run when AQE is enabled. Simply remove the conditional code in these tests that disables it.
Expected behavior
The test should execute without error and produce the correct result.
Environment details (please complete the following information)
Running mvn clean verify on desktop (Ubuntu).
Additional context
N/A

This was resolved in https://github.com/NVIDIA/spark-rapids/pull/469


Enable helm-tool linter and schema generator

Enabling these two features that were added in the Helm module:
https://github.com/cert-manager/csi-driver-spiffe/blob/cd2a498532c20cc4813012f16c4f36fbe91d2f76/make/00_mod.mk#L52-L53

/approve


Live or Hot reload

Not seeing a way to run live reload or hot module replacement in dev?

Hi,
There is no live reload, you should reload page manually.
npm run dev - watches your files and compiles but does not reload a page

Thanks for the quick response!  Wish I had more time to contribute right now, would be a nice feature. :)

You are welcome 👍
About live reload feature I would suggest making it optional. As for me, I do not use it as want to have a control when reloading a page :)
e.g. npm run dev:reload


enable-profiling & enable-debug don't work

In what area(s)?
/area runtime
What version of Dapr?

1.5.x

Expected Behavior
Actual Behavior

As per documentation ( https://v1-5.docs.dapr.io/operations/troubleshooting/profiling-debugging/ )  I should be able to set the annotation dapr.io/enable-profiling: "true"   and then kubectl port-forward divideapp-6dddf7dc74-6sq4 7777:7777
Does not work
Also
( https://v1-5.docs.dapr.io/developing-applications/debugging/debug-k8s/debug-daprd/ )
Setting annotation dapr.io/enable-debug: 'true' should be able to kubectl port-forward nodeapp-78866448f5-pqdtr 40000:40000
Does not work

Can you try adding the following annotation and see if you can port-forward?
dapr.io/sidecar-listen-addresses: "<IP_ADDRESS>"


Py3k unicode collapse

A step towards an alternative version of #1782 which conserves existing Python 2 behaviour : see comment there
An adjusted version of @QuLogic
"f9cc0f9 py3k: Use Unicode in coord collapse."
Make it unicode only in Python 3.
TO TEST :
python3 -m unittest iris.tests.unit.coords.test_Coord.Test_collapsed fails before this, succeeds after
NOTE :
As the second commit effectively reverts some changes from the first one,  it probably makes good sense to squish before merging.

@QuLogic  string_type_fmt is only set if self.bounds is not None?

Good spot !
I hope the latest fixes it, and I added a test.  It seems we no test coverage for collapsing a string coord without bounds.  No great surprise really, as they aren't common in real files.


Golaz/misc fixes

A number of small improvements and fixes.

@zshaheen : this PR includes code to control plot size with mpl by specifying figure size (inches) and resolution (dpi).
self.figsize = [8.5, 11.0]
self.dpi = 150

The default that I selected will give png figures with size very similar (but not identical) to vcs. If you want, there is an opportunity to better unify vcs and mpl here by redefining how you set the vcs canvas size:
canvas_size_w = figsize[0]*dpi
canvas_size_h = figsize[1]*dpi

The best would be to do this in the plotting functions where canvas_size is needed and remove the canvas_size_{w,h} parameters.


Beta09 - Fixed copyright and time units in iso2dfd sample

Description
Deleted year from copyright
Fixed time unit in iso2dfd
Please delete options that are not relevant. Add a 'X' to the one that is applicable.

[ X] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

I ran the code and confirmed time units are correct in output
Visually inspected copyright in License.txt file

[ X] Command Line
[ ] oneapi-cli
[ X] Visual Studio
[ ] Eclipse IDE
[ ] VSCode

Checklist for Moving samples:
Links and Details can be found in the samples WG Teams Files.

[ ] Review sample design with domain reviewers https://github.com/oneapi-src/oneAPI-samples/wiki/Reviewers-and-Domain-Experts
[ ] Implement coding guidelines and ensure code quality.
[ ] Adhere to sample.json specification. https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-specification
[ ] Run jsonlint on sample.json to verify json syntax. www.jsonlint.com
[ ] Adhere to readme template
[ ] Ensure/create CI test configurations for sample (ciTests field) https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-ci-test-object
[ ] Enforce format via clang-format config file
[ ] Review DPC++ code with Paul Peterseon. (GitHub User: pmpeter1)
[ ] Review readme with Tom Lenth or Joe Oster. (GitHub User: JoeOster)
[ ] Tested using Dev Cloud when applicable
[ ] Implement fixes for ONSAM Jiras
[ ] If you have new dependencies/binaries, inform Samples Project Manager Swapna R Dontharaju (@srdontha) or @JoeOster

@JoeOster Hi, could you please clarify the request? I'm using "dpc_common" functions for timing. Thanks for reviewing.

@JoeOster Hi, could you please clarify the request? I'm using "dpc_common" functions for timing. Thanks for reviewing.

My apologies, I must have clicked into wrong file, it is showing today.


[TA] upgrade version

Prepare the October patch release

API change check
API changes are not detected in this pull request.


add camera name

Adds Camera Name to setupbase.
Default Camera should be named Main if not stated otherwise

Closed, because it is already done.


How much gain did self-distillation bring?

Hello,
Thank you for your outstanding work! This is my first time encountering self-distillation applied to event-based motion deblurring, and I am very curious about the performance improvements it provides. Specifically, I would like to know what the PSNR/SSIM values would be if only a single training stage were used.
Thank you, and I look forward to your reply!

Hi, thanks for your question. Self-distillation is used to improve the generalization ability across spatial and temporal dimensions. We have conducted related experiments, and some results are reported in Section 4.3 of our paper, specifically models #3 (one-stage) and #6 (two-stage) in Tab. 3 and Fig. 6. Hope this helps :)

Thank you for your reply. I understand your work better now.


feat(@ngtools/webpack): show warning when a TS compilations contains …

…unused files
When a tsconfig without includes or files all files under the rootDir will be included in the compilation. This results in redundant files to inserted as part of the ts compilation which in some cases might reduce the compilation drastically.
Related to: TOOL-949

Note: tests to be added
Also without implementing this https://github.com/angular/angular-cli/pull/15030 for VE the warning will be shown all the time.
This is because by default we do include redundant files in the compilations. There are;

app.server.module.ts
server.ts
main.server.ts
environment.prod.ts

Also, seeing this all current projects will have this warning.

We may want to ignore anything involved in file replacements.

Only the last one, is in fileReplacement but, why should we ignore it? It is in the compilation because of the non strict includes that we currently have as otherwise they won’t be part of the compilation.

As discussed we should only enable this for Ivy.


Investigate usage of Podman

@BeritJanssen  @drikusroor
The issue has been investigated and wiki (02. Start the application) updated.


Adds test support without cocoapods

Addresses #414
Like #422 this does not use cocoapods as to not create an xcworkspace. For now this uses XCTest but  could be moved to Quick and Nimble if everyone likes it better.

Looks good!
I think we should add tests for the beziers too, and add edge cases (viewport encloses beginning/end of a large dataset, instead of being fully zoomed out)
But this is a good start!

For sure. I was just putting the infrastructure in place.

Can't auto-merge, I think it clashes with the tvOS project changes

Alright. I'll rebase and make things work.

That should fix it

Compiles fine and runs just fine :-)

@petester42 thanks! :+1: :rocket:

How do we re-generate those images?
While adding rotation support to labels, I have removed some "predefined" values that were there to adjust drawing quirks. Now we control the drawing more accurately and do not need those. But things have changed on a pixel level and all tests fail :(

In setup add record = true. An example can be seen here. It's in objective-c but it's the same thing.

Possibly all test can have it written but set to no just to make it easier to understand.

Thanks :-)


logging to ILogger on config error

Should help address https://github.com/Azure/azure-webjobs-sdk/issues/1126 by making sure we're logging to both TraceWriter and (a default) ILogger if we have an error while building the configuration.

@fabiocav -- ping

@mamaso / @fabiocav -- can one of you take a quick look at this?


Introduce Blob.DataAsync

This is a replacement for #47
I need this function for my refactor (related work: https://github.com/go-gitea/git/pull/93, https://github.com/go-gitea/gitea/pull/2990, https://github.com/go-gitea/gitea/issues/2669).

Ping @bkcsoft

LGTM

LGTM

Hm, so how can I update this in the main gitea repo? Or should I wait for #93 to be merged?

Execute govender update code.gitea.io/git on your gitea feature branch.


Remove moot version property from bower.json

Per bower/bower.json-spec@a325da3

Why was this closed?

Hey @kkirsche , the version property has already been removed: https://github.com/pa7/heatmap.js/blob/develop/bower.json


[Aborea] add darkmode

rolltemplate is still missing
Changes / Comments
add darkmode
rolltemplate is still missing
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[x] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[x] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.

I would advise not minifying your css. It's probably the cause of your roll templates failing.

I would advise not minifying your css. It's probably the cause of your roll templates failing.

there is currently no darkmode class for the chatbar, that's what i mean by my statement. In light mode everything works fine.
I don't know why the interpreter should have a problem with minifying, it doesn't care how it is written. only humans read it harder but that's why there is the sass file.


Proposal: Add native support to bitstring

This is the companion PR of elixir-ecto/ecto#4328

Would you be able to update mix.exs so it points to your ecto branch? Basically change this part:
{:ecto, git: "https://github.com/elixir-ecto/ecto.git"}
to
{:ecto, git: "https://github.com/gigitsu/ecto.git", branch: "bitstring branch"}
Then run mix deps.update ecto
That way we could ensure the unit tests pass :)

Don! Sort of :)
There wasn't any {:ecto, git: "https://github.com/elixir-ecto/ecto.git"} in the repo but only {:ecto, "~> 3.11.0"} ( here ). Furthermore, the bitstring branch is only on my fork so I temporarily changed the main repo and branch just to verify the tests passes.
I wasn't sure ho to do this.

I believe we will have an issue casting to the bitstring type. I was playing around with it and it seems like you must specify the number of bits when casting. If you omit it in postgres, like `::bit`` it will silently only take one bit.
Not sure atm what the best thing to do is. The only thing I can think is forcing a size when casting, like {:bitstring, n}. But would want to hear Jose's opinion before going down the route.

I believe we will have an issue casting to the bitstring type. I was playing around with it and it seems like you must specify the number of bits when casting. If you omit it in postgres, like ::bit it will silently only take one bit.
Not sure atm what the best thing to do is. The only thing I can think is forcing a size when casting, like {:bitstring, n}. Though we would have to make the schema type that was well, in case casting is done to the field type. Other than that the only thing I can think of is to disallow casting to it. Would want to see what Jose thinks before choosing an option.

Yeah you need to specify the size when casting a bit column in Postgres. I'd like to be able to specify a size when casting.

Another thing I just realized we need to think about is literals. I think we always have to tag them in Ecto like with binaries: https://github.com/elixir-ecto/ecto/blob/23c40e3d9b95ac4238b5417c4e3bb7329a0cc8b0/lib/ecto/query/builder.ex#L774
And then handle them specially in the adapter like we do for binary: https://github.com/elixir-ecto/ecto_sql/blob/master/lib/ecto/adapters/postgres/connection.ex#L1013
This just popped into my head though I didn't have time to play around with it yet. But we need to consider it.

Another thing I just realized we need to think about is literals. I think we always have to tag them in Ecto like with binaries: https://github.com/elixir-ecto/ecto/blob/23c40e3d9b95ac4238b5417c4e3bb7329a0cc8b0/lib/ecto/query/builder.ex#L774
And then handle them specially in the adapter like we do for binary: https://github.com/elixir-ecto/ecto_sql/blob/master/lib/ecto/adapters/postgres/connection.ex#L1013
This just popped into my head though I didn't have time to play around with it yet. But we need to consider it.
This is used, for example, when you do something like this from q in query, where: q.bitstring_field == <<4::4>>

I attempted to tag bitstrings similarly to binaries, but I couldn't find a reliable way to differentiate between them. My only option is to check whether the size is a multiple of 8 (indicating a binary) or not (indicating a bitstring), but this appears to be a weak distinction. Do you have any ideas?
Nevertheless, I also suspect that binary literals might suffice for bitstrings as well. I'll do some integration tests to verify this.

I attempted to tag bitstrings similarly to binaries, but I couldn't find a reliable way to differentiate between them. My only option is to check whether the size is a multiple of 8 (indicating a binary) or not (indicating a bitstring), but this appears to be a weak distinction. Do you have any ideas?
Elixir has is_binary to differentiate between the two

I attempted to tag bitstrings similarly to binaries, but I couldn't find a reliable way to differentiate between them. My only option is to check whether the size is a multiple of 8 (indicating a binary) or not (indicating a bitstring), but this appears to be a weak distinction. Do you have any ideas?

Could you point to some of the places where you'd need to make such a distinction but not know the underlying type? I can take a look.

The process to tag literal starts with:
# literals
  def escape({:<<>>, _, args} = expr, type, params_acc, vars, _env) do
    valid? = Enum.all?(args, fn
      {:"::", _, [left, _]} -> is_integer(left) or is_binary(left)
      left -> is_integer(left) or is_binary(left)
    end)

    unless valid? do
      error! "`#{Macro.to_string(expr)}` is not a valid query expression. " <>
             "Only literal binaries and strings are allowed, " <>
             "dynamic values need to be explicitly interpolated in queries with ^"
    end

    {literal(expr, type, vars), params_acc}
  end

where the operator :<<>> is matched (here)
Then literal(expr, type, vars) is called that, in turn, calls quoted_type(expr, vars)
defp literal(value, expected, vars),
    do: do_literal(value, expected, quoted_type(value, vars))

...

def quoted_type({:<<>>, _, _}, _vars), do: :binary`

that returns :binary.
Eventually, the literal is tagged with type :binary:
defp do_literal(value, _, current) when current in [:binary],
    do: {:%, [], [Ecto.Query.Tagged, {:%{}, [], [value: value, type: current]}]}

(it happens here)
In this process, I can't find a neat way to distinguish between bitstrings and binaries, since the operator for both types is the same (:<<>>) and some bitstrings are also a valid binary (eg. is_binary(<<5>>) = true)
I need that type: current to be :bitstring if I want convert it into a Postgres bit literal here.

Thanks that's really helpful. I will take a closer look.

I'll need to play with this to see if bitstrings are possible in sqlite. I think I'll have to use BLOB for this. If not, I'll have to make it just raise an exception saying it is unsupported.

In this process, I can't find a neat way to distinguish between bitstrings and binaries, since the operator for both types is the same (:<<>>) and some bitstrings are also a valid binary (eg. is_binary(<<5>>) = true)

@Gigitsu I think the best we can do here is check is_binary on the literal and if it's true call it :binary and if not :bitstring. And if the user really wants to treat it as :bitstring they can wrap it in type/2 like type(^<<5>>, :bitstring). I'm not seeing any other way.

I'll need to play with this to see if bitstrings are possible in sqlite. I think I'll have to use BLOB for this. If not, I'll have to make it just raise an exception saying it is unsupported.

@warmwaffles from a quick Google search, it seems that in SQLite bitwise operators works on numeric types and not on BLOB so I wonder if it could be the right choice to use a numeric type, otherwise raise an exception.

@Gigitsu I think the best we can do here is check is_binary on the literal and if it's true call it :binary and if not :bitstring. And if the user really wants to treat it as :bitstring they can wrap it in type/2 like type(^<<5>>, :bitstring). I'm not seeing any other way.

@greg-rychlewski I believe I'm facing my knowledge limitations on Elixir macro on this. :)
Both here
  def escape({:<<>>, _, args} = expr, type, params_acc, vars, _env) do
    valid? = Enum.all?(args, fn
      {:"::", _, [left, _]} -> is_integer(left) or is_binary(left)
      left -> is_integer(left) or is_binary(left)
    end)

    unless valid? do
      error! "`#{Macro.to_string(expr)}` is not a valid query expression. " <>
             "Only literal binaries and strings are allowed, " <>
             "dynamic values need to be explicitly interpolated in queries with ^"
    end

    {literal(expr, type, vars), params_acc}
  end

and here
  # Tagged
  def quoted_type({:<<>>, _, _}, _vars), do: :binary
  def quoted_type({:type, _, [_, type]}, _vars), do: type

the expr is an AST {eg. {:<<>>, [line: 1], [1, 2, 3]}) so I cannot use is_binary on that, it always returns false.
I need to transform the AST into actual code to test it with is_binary, don't I?
My other option is to add a case match here like this
    defp expr(%Ecto.Query.Tagged{value: binary, type: :binary}, _sources, _query)
         when is_binary(binary) do
      ["'\\x", Base.encode16(binary, case: :lower) | "'::bytea"]
    end

    defp expr(%Ecto.Query.Tagged{value: binary, type: :binary}, _sources, _query)
         when is_bitstring(binary) do
      ["'\\x", Base.encode16(binary, case: :lower) | "'::bytea"]
    end

but the tagged type will always be :binary

def escape({:<<>>, _, args} = expr, type, params_acc, vars, _env) do
...

I think we can leave this one as is, it should just catch that users are not supplying variables (i.e. <<var>> or  <<var::1>>). It doesn't look to me like it matters if it's a binary or bitstring.
 def quoted_type({:<<>>, _, _}, _vars), do: :binary

The only way I know to check here is using Code.eval_quoted. Like this:
def quoted_type({:<<>>, _, _} = expr, _, _vars) do
  if is_binary(Code.eval_quoted(expr)) do
    :binary
  else
    :bitstring
  end
end

Though I don't know how bad this is considered and would need a second opinion. It might be ok since we know it is a literal. There might also be a better strategy than the one I'm suggesting but I need to think more and possibly get other opinions.
defp expr(%Ecto.Query.Tagged{value: binary, type: :binary}, _sources, _query)
       when is_binary(binary) do
    ["'\\x", Base.encode16(binary, case: :lower) | "'::bytea"]
  end

Yes, we will have to create a clause like this for bitstring. Because that encoding will fail for non-binaries and also that representation will not be allowed to be cast to bit types in Postgres.

def quoted_type({:<<>>, _, _} = expr, _, _vars) do
  if is_binary(Code.eval_quoted(expr)) do
    :binary
  else
    :bitstring
  end
end

There's another complication with this. Our current checks don't guard against dynamic bit size. We allow stuff like this
size = 3
<<2::size(size)>>

It shouldn't be in use today because only size = 8 would work. So if we go this route we might also need to guard against dynamic size. Otherwise we can't determine the type at compile time.

I think we can leave this one as is, it should just catch that users are not supplying variables (i.e. <<var>> or <<var::1>>). It doesn't look to me like it matters if it's a binary or bitstring.

I totally agree.

The only way I know to check here is using Code.eval_quoted. Like this:

I don't like the idea of using Code.eval_quoted very much, I'd prefer to leave :binary for both :binary and :bitstring at this stage.

defp expr(%Ecto.Query.Tagged{value: binary, type: :binary}, _sources, _query)
       when is_binary(binary) do
    ["'\\x", Base.encode16(binary, case: :lower) | "'::bytea"]
  end

Yes, we will have to create a clause like this for bitstring. Because that encoding will fail for non-binaries and also that representation will not be allowed to be cast to bit types in Postgres.

I would differentiate :binary from :bitstring only here, adding a new clause with when is_bitstring(...) guard, leaving type: :binary in function sign.

It shouldn't be in use today because only size = 8 would work. So if we go this route we might also need to guard against dynamic size. Otherwise we can't determine the type at compile time.

Should we allow a syntax like this:
size = 3
<<2::size(^size)>>

with the ^ operator for dynamic size?

I would differentiate :binary from :bitstring only here, adding a new clause with when is_bitstring(...) guard, leaving type: :binary in function sign

Let's get Jose's opinion before making any change here. Because we will be tagging it with the wrong type and passing it to every adapter, not just the built-in ones.

I would differentiate :binary from :bitstring only here, adding a new clause with when is_bitstring(...) guard, leaving type: :binary in function sign.

Let's get Jose's opinion before making any change to this part. Maybe what you are saying is the best way. But at the same time we'd be passing the wrong type through the Ecto planner and out to all the adapters (not just the built-in ones).

That's ok, let's wait for Jose's opinion. In the meantime I'll ad some integration tests

The other way I can think of is we already iterate through the bitstring here:
valid? = Enum.all?(args, fn
      {:"::", _, [left, _]} -> is_integer(left) or is_binary(left)
      left -> is_integer(left) or is_binary(left)
    end)

So we could also determine at this point whether the sum of the sizes is divisible by 8 or not by tracking the remainder after each iteration and adding some pattern matches to size. Though we'd have to guard against variable sizes and raise the same message as if the value was variable:
unless valid? do
      error! "`#{Macro.to_string(expr)}` is not a valid query expression. " <>
             "Only literal binaries and strings are allowed, " <>
             "dynamic values need to be explicitly interpolated in queries with ^"
    end

i.e. if any part of the literal is variable, interpolate the entire thing (^<<..>>)

The other way I can think of is we already iterate through the bitstring here:
valid? = Enum.all?(args, fn
      {:"::", _, [left, _]} -> is_integer(left) or is_binary(left)
      left -> is_integer(left) or is_binary(left)
    end)

So we could also determine at this point whether the sum of the sizes is divisible by 8 or not by tracking the remainder after each iteration and adding some pattern matches to size. Though we'd have to guard against variable sizes and raise the same message as if the value was variable:
unless valid? do
      error! "`#{Macro.to_string(expr)}` is not a valid query expression. " <>
             "Only literal binaries and strings are allowed, " <>
             "dynamic values need to be explicitly interpolated in queries with ^"
    end

i.e. if any part of the literal is variable, interpolate the entire thing (^<<..>>)

Yeah I agree, I was experimenting exactly with that, but we should consider that there are different kinds of size definitions, eg <<1::1, 2::size(2), 3::bits(3), 4::integer, ...>> . I cannot find exhaustive documentation about these modifiers.

Yeah I have the same problem. I would need Jose's input on that.

Regardless, I think we have to consider modifying the checks here:
valid? = Enum.all?(args, fn
      {:"::", _, [left, _]} -> is_integer(left) or is_binary(left)
      left -> is_integer(left) or is_binary(left)
    end)

Because this will fail for something like this << <<1::1>>::bitstring  >>

Could Code.eval_quoted be potentially dangerous? There could be anything in ::size(..) modifier.

Yeah, that's why I mentioned we'd need to block user input and only accept literals. But given the multitude of modifiers I don't know how feasible this is. Or if it would be considered an unacceptable risk either way.
Basically none of the options are looking too appealing right now:

eval_quoted
passing the wrong type to adapters
tracking the size remainder

I'm hoping by continuing to discuss/think about it a better way becomes clear.

I was playing around with this some more. It is contrived but illustrates that assigning the wrong type can leak into unwanted places in otherwise valid queries. Something like this would not work because the planner would try to cast the parameter <<1::1>> to binary
from p in Post, where: <<1::1>> == ^<<1::1>>

I am wondering if something like this might work. We change the quoted_type function to this:
def quoted_type({:<<>>, _, _}, _vars), do: :bitstring

And then the literal functions to this:
@always_tagged [:bitstring]

defp do_literal(value, _, current) when current in @always_tagged do
  type =
    if current == :bitstring do
      quote do: is_binary(unquote(value)) && :binary || :bitstring
    else
      current
    end
  {:%, [], [Ecto.Query.Tagged, {:%{}, [], [value: value, type: type]}]}
end

That would make sure we are backward compatible (binary literals still tagged with :binary) and also the casting of the parameters would work because it would cast to same bitstring instead of same binary. Which covers both cases.
I didn't look carefully enough to see if there are other cases to consider. But maybe this is a path worth pursuing.

I am wondering if something like this might work. We change the quoted_type function to this:
def quoted_type({:<<>>, _, _}, _vars), do: :bitstring

And then the literal functions to this:
@always_tagged [:bitstring]

I also thought about using :bitstring instead of :binary when the operator :<<>> is matched, because every binary is also a bitstring but the vice-versa isn't true. But then again I would have differentiated the type in ecto_sql with a clause here:
defp expr(%Ecto.Query.Tagged{value: binary, type: :bitstring}, _sources, _query)
       when is_binary(binary) do
  ...
end
defp expr(%Ecto.Query.Tagged{value: bitstring, type: :bitstring}, _sources, _query)
       when is_bitstring(binary) do
  ...
end

and we were not sure about to do this.

defp do_literal(value, _, current) when current in @always_tagged do
  type =
    if current == :bitstring do
      quote do: is_binary(unquote(value)) && :binary || :bitstring
    else
      current
    end

  {:%, [], [Ecto.Query.Tagged, {:%{}, [], [value: value, type: type]}]}
end

That would make sure we are backward compatible (binary literals still tagged with :binary) and also the casting of the parameters would work because it would cast to same bitstring instead of same binary. Which covers both cases.

I'm not sure I understand this, since @always_tagged [:bitstring] also current will be always :bitstring so
if current == :bitstring do
  quote do: is_binary(unquote(value)) && :binary || :bitstring
else
  current
end

will always run the first branch, am I missing something?
Finally, type would be a quoted expression, is it interpreted before it comes here?

will always run the first branch, am I missing something?

For the same reason we have @always_tagged as a list and use current in @always_tagged instead of current == @always_tagged . It might change if we decide there is a reason to.

Finally, type would be a quoted expression, is it interpreted before it comes here?

Yes. The builder functions are used at compile time and the connection string is evaluated at runtime.

But then again I would have differentiated the type in ecto_sql with a clause here:

This is normal. We will have to differentiate them in any solution we choose because their representation in the query will be different.

But then again I would have differentiated the type in ecto_sql with a clause here:

Then we are breaking 3rd party adapters. If there is a way to handle it in a backward compatible way before it gets to the adapters what's your reason for preferring this?

Hi @greg-rychlewski, I encountered some issues when trying to run integration tests on an ARM processor (Apple M2). I modified the Earthfile to use the linux/amd64 architecture for Docker images of databases and to use the correct architecture when downloading MSSQL client tools. Now, it seems to be working both on my local machine and in CI.
However, I'm unable to use PostgreSQL 9.5 locally because the Alpine 3.4 Docker image only exists for amd64, preventing me from installing an arm64 version of PostgreSQL 9.5.
I'll add a section in the readme for this.

@Gigitsu There are some conflicts here as well. Thank you.

@greg-rychlewski rebased also here

It looks to me like the TDS driver doesn't support bitstrings, so we don't have to worry about supporting them: https://hexdocs.pm/tds/readme.html#data-representation
For MyXQL you're right something weird is going on. When I test the driver directly outside of Ecto I also get weird behaviour. But don't understand the issue completely yet.

I would say don't support it for MyXQL or TDS. Then for the Ecto integration test separate it out into its own test and tag it like @tag :bit_type and in the test helpers for MyXQL/TDS the tag can be excluded.
We should get @josevalim 's opinion too though. For reference, this test returns empty list in MyXQL, which is why I think there is some kind of encoding issue
MyXQL.query!(c.conn, "CREATE TABLE test_prepared_schema_change (x bit(3))")
MyXQL.query!(c.conn, "INSERT INTO test_prepared_schema_change VALUES (?)", [<<2::size(3)>>])

{:ok, query} = MyXQL.prepare(c.conn, "", "SELECT * FROM test_prepared_schema_change where x = ?")
assert {:ok, _, result} = MyXQL.execute(c.conn, query, [<<2::size(3)>>])
assert result == []

@greg-rychlewski weird, we have a test for encoding and decoding bit strings here:
https://github.com/elixir-ecto/myxql/blob/v0.6.4/test/test_helper.exs#L123
https://github.com/elixir-ecto/myxql/blob/v0.6.4/test/myxql/protocol/values_test.exs#L198
but maybe it's a problem for SELECTs somehow.

I noticed for select that I am returned a binary. It seems like maybe the size is being ignored?
MyXQL.query!(c.conn, "select ?", [<<2::size(3)>>])

%MyXQL.Result{
  columns: ["?"],
  connection_id: 1372,
  last_insert_id: nil,
  num_rows: 1,
  num_warnings: 0,
  rows: [[<<2>>]]
}

Yeah I got the impression looking into the MyXQL history that this is a tough topic. For example: https://github.com/elixir-ecto/myxql/issues/91.
My first impulse was to try and figure out the issue, but given the complexity maybe we go ahead with this PR for now without MySQL and then add it in later once we figure it out.

Agreed.

My first impulse was to try and figure out the issue, but given the complexity maybe we go ahead with this PR for now without MySQL and then add it in later once we figure it out.

I agree too.
So my next step is to remove the MySQL implementation ad do an integration test only for Postgres, am I right?

@Gigitsu Yeah you can keep the test in Ecto because that's where all the other types are. But you could pull the :bitstring tests into their own test and tag them with @tag :bitstring_type. And then in ecto_sql integration test helper files for MySQL and TDS you ignore the tag.
And then last thing is to add literal support in Ecto and then catch the tagged value here in the postgres adapter.

Hi @greg-rychlewski, I've removed everything related to bitstring from MySQL and TDS adapters.
I've also created a new schema specifically for the bitstring tests (sorry for the lack of creativity in naming this table and its fields; any suggestions are welcome) and I've isolated these tests to run only for Postgres.
Now everything seems to work. Please let me know if there is anything I forgot.
Additionally, I've updated the Earthfile to make it compatible with ARM (Apple Silicon in my case) CPUs. However, I only have experience with Docker and haven't used Earthly before, so please take a look at it.

And then last thing is to add literal support in Ecto and then catch the tagged value here in the postgres adapter.

I almost forgot this, I work on it

thanks @Gigitsu !

Thank you!


Raw value support

In Modest, it's possible to retrieve the raw value (undecoded text) of a node using myhtml_tree_node_t.token.element_begin and myhtml_tree_node_t.token.element_length.
Is it possible in lexbor? I see lxb_html_token_t.text_start but it looks like such data is not available after the parsing.

@rushter
Practice has shown that no one uses this.

Is it possible in lexbor? I see lxb_html_token_t.text_start but it looks like such data is not available after the parsing.

You are right, the token contains the information you need, but after building the tree, you do not have access to the token, it is destroyed (and generally one token using for all parsing).
Positions from the token can be saved to the DOM Node, but it seems this is meaningless information that will only take up memory.
It may be possible to add a certain debug field to the DOM Node in which to save such information if an additional flag is specified before parsing HTML?
I don't know how to do it "beautifully" yet.

Thanks. That's not a big deal.


Change docs to use fs's mkdir

Node have builtin mkdir with recursive option
Better to use that instead of some dependency
https://github.com/facebook/jest/blob/db643a1cc8b8ff02b524ff258074ea8c92012af6/docs/Puppeteer.md#L61

GitHub's Terms of Service


HHH-18056 Support for JPA 32 table options

https://hibernate.atlassian.net/browse/HHH-18056

I missed TableGenerator#options in the original list on the Jira.  Do you think you could do that here?
Or should we create a new Jira?  We'll need to account for SequenceGenerator#options as well, so could group those that way instead.

@sebersole  let's create another Jira, already started working on Column options :P

Here you go :)
https://hibernate.atlassian.net/browse/HHH-18096

Thanks


Create Konserter “index-1”

Automatically generated by Netlify CMS

👷 Deploy Preview for xenodochial-jang-0ad7f2 processing.
🔨 Explore the source changes: 9266cfdb4d7d3265cfcd6adccba2c0900615f238
🔍 Inspect the deploy log: https://app.netlify.com/sites/xenodochial-jang-0ad7f2/deploys/6139ac412e67d7000778f847


spring-cloud: add location to Apps operation

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/hellokangning/azure-cli-extensions.git@hkn/spring-app-location#subdirectory=src/$EXT&egg=$EXT"

add to S168


Improve how runner parses env var file

Only split by the first "=" when parsing lines from the deepspeed environment file.

@liamcli, thanks so much.


Breast Cancer Diagnosis Prediction Using Explainable AI Algorithms

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Project Title : Breast Cancer Type Detection using Explainable AI
:red_circle: Aim : The main objective of this project is to predict whether a tumor is benign or malignant using machine learning models and explain the model’s decisions using LIME (Local Interpretable Model-Agnostic Explanations). The dataset used in this project is the Breast Cancer Dataset available from Kaggle.
:red_circle: Dataset : https://www.kaggle.com/datasets/yasserh/breast-cancer-dataset
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name : inkerton
GitHub Profile Link :  inkerton
Email ID<EMAIL_ADDRESS>Participant ID (if applicable):
Approach for this Project : To add explainable AI models in the repo since this is a newly emerging field.
What is your participant role? (Mention the Open Source program) GSSOC

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Can you elaborate more on the approach? Didn't get the explainable AI approach!!

Explainable Ai is the set of a;gorithms that explains the working behind a prediction like how did the Ai came to the conclusion that its a tumor and not just a ump or a ball of mass. The explaination of behind the process is termed as Explainable AI.

Already present in this repository, hence closing this issue as a duplicate entry.


Rework the Database

In part of the ongoing development process, I propose reworking the database import process to improve efficiency and maintain data integrity. Currently, users are required to delete the entire dataset before sending a rebuilding, request which can be time-consuming. Instead, Im sure alot of end users would  recommend implementing an incremental update approach:

Incremental Updates: Modify the import process to identify changes since the last import. Only new or updated data should be processed, minimizing the need for a full reimport.

Selective Deletion: When necessary, selectively delete outdated records based on the changes detected during the import. This approach ensures that existing data remains intact while accommodating necessary updates.

Im sure this request has been brought to your attention , so i figure i would post this as a issue(request).

Incremental database updates are not in the scope for me. It would greatly increase complexity of the import process.
I know that it might be inconvenient for people with larger databases that get updated frequently, however for my own personal usecases this is not an issue.
However since many people asked for it, I will leave this issue open in case someone wants to try implementing it and/or discuss possible solutions.

...discuss possible solutions.

My best guess would be to add something like
    // Incremental Updates
    const lastImportTime = await this.getLastImportTime(); // Retrieve the last import time from the database
    await this.updateLastImportTime(Date.now()); // Update the last import time after a successful import

    // Selective Deletion
    const outdatedRecords = await this.getOutdatedRecords(lastImportTime); // Retrieve outdated records based on the last import time
    await this.deleteOutdatedRecords(outdatedRecords); // Delete outdated records

which can be stored in the postgress datebase for future reference
CREATE TABLE import_status (
  id SERIAL PRIMARY KEY,
  last_import_time TIMESTAMP DEFAULT NOW()
);

an alternative to this might just be using hydrus version number seeing how you're already using that in your index.ts
const { version } = hydrus.prepare('SELECT version FROM version;').get();
    if(version < MIN_HYDRUS_VER) throw new Error(`Unsupported Hydrus version(min: v${MIN_HYDRUS_VER}, current: v${version}), Update Hydrus to the newest version.`);

which could be a safe approach to allowing the user to import changes between versions without the need of a full on rebuild.
As far as me actually implementing this... I honestly wouldnt know where to start .

Incremental database updates are not in the scope for me. It would greatly increase complexity of the import process.
I know that it might be inconvenient for people with larger databases that get updated frequently, however for my own personal usecases this is not an issue.

ill just close this out as not planned , took me almost 2 weeks to get what you were saying 😂


Pylint unable to import tensorflow.keras

Issue Type: Bug
This import statement
import tensorflow.keras as keras

is marked by pylint as Unable to import even though tensorflow.keras exists. This is a common problem, see https://github.com/tensorflow/tensorflow/issues/26813
Tensorflow version: 2.1
Extension version: 2020.2.64397
VS Code version: Code 1.43.0 (78a4c91400152c0f27ba4d363eb56d2835f9903a, 2020-03-09T19:34:44.548Z)
OS version: Darwin x64 19.3.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz (4 x 2300)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
6, 5, 4

Memory (System)
8.00GB (0.10GB free)

Process Argv
.

Screen Reader
no

VM
0%

This is likely https://github.com/PyCQA/pylint/issues/3080
If you are using anaconda, activate the environment first then start code  . from there.

Actually, I don't think it is the same problem. Activating the environment first also does not help. Here is a snapshot of the behavior.

Actually, it seems to be this problem: https://github.com/PyCQA/pylint/issues/2603
Doesn't seem like there is a solution out there though ;/
PyCharm does not have these issues.


⚠ Samsung has degraded performance

In e7d0170, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2582 ms

Resolved: Samsung performance has improved in 494ddc6.


Pipeline automation: create, run, delete

moved pipeline delete to main test
ran flake8, added environment variables
added clarifying comments
moved test def to top of definitions, added delete test case

closing in favor of #31596


react-player demo is not working for audio files in IOS!

I'm opening demo page in IOS and it's not working in.
I have a propblem in 'play() event of simple audio tag is react context and I decide to use react-player as a sample.
but It is not working in IOS too!
https://cookpete.com/react-player/

Things are always going to be awkward on mobile. On iOS it seems like it can take a few taps of pause/play and user interaction to get working. It will never be perfect. ReactPlayer may not be the library for you if iOS is your focus.


Bullet-Proof Beacon

Make it want to reconnect, handle more exceptions, better use of watchdog? etc.

Try setting watchdog. Probably other issues exist... Not sure how to solve otherwise.

Try setting watchdog. Probably other issues exist... Not sure how to solve otherwise.

Try setting watchdog. Probably other issues exist... Not sure how to solve otherwise.


tutanota-desktop: 3.98.15 -> 3.98.17

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/tutanota-desktop/versions.
meta.description for tutanota-desktop is: "Tutanota official desktop client"
meta.homepage for tutanota-desktop is: "https://tutanota.com/"
meta.changelog for tutanota-desktop is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.98.17 with grep in /nix/store/k1mr4x0x0dxq9dkzf92yqv9w540jlq4b-tutanota-desktop-3.98.17
found 3.98.17 in filename of file in /nix/store/k1mr4x0x0dxq9dkzf92yqv9w540jlq4b-tutanota-desktop-3.98.17

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
tutanota-desktop

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/k1mr4x0x0dxq9dkzf92yqv9w540jlq4b-tutanota-desktop-3.98.17 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A tutanota-desktop https://github.com/r-ryantm/nixpkgs/archive/475ad0ff72db9129546363da8a50d8fa6631ba9a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/k1mr4x0x0dxq9dkzf92yqv9w540jlq4b-tutanota-desktop-3.98.17
ls -la /nix/store/k1mr4x0x0dxq9dkzf92yqv9w540jlq4b-tutanota-desktop-3.98.17/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

tutanota-desktop

Maintainer pings
cc @WolfangAukang for testing.

Result of nixpkgs-review pr 185002 run on x86_64-linux 1

1 package built:

tutanota-desktop


Add husky to pre-lint any commits, remove unused imports

Description
Adds a rule to lint any commits prior to pushing. This should fix cases where work is pushed up but not linted, failing CI. TODO: should we add running tests here?
Category
[Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation]
Why these changes are required?
What is the old behavior before changes and new behavior after changes?
Linting was not done automatically and developer cycles were needed to remember to manually run that command
Issues Resolved
[List any issues this PR will resolve (Is this a backport? If so, please add backport PR # and/or commits #)]
Fix: https://github.com/opensearch-project/security-dashboards-plugin/issues/1805
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@cwperks this address this comment as well: https://github.com/opensearch-project/security-dashboards-plugin/pull/1824#discussion_r1522123256

Thank you @derek-ho! This makes the commit process consistent with OSD core.
OSD Core has an issue filed around unused imports. If the issue is fixed in core, would those rules transitively apply to the security-dashboards-plugin?

This PR is already making unused imports error the linting process by adding the "unused-imports" plugin to the eslintrc.js file - I didn't manually remove those imports, it was automatically done as part of the pre-commit hook.


Test that repeated push_verify is not a no-op

Phew! If repeated push_verify was a no-op I think that'd definitely be a bug :).
Wouldn't be opposed to adding a unit test here.

Originally posted by @apoelstra in https://github.com/rust-bitcoin/rust-bitcoin/issues/1153#issuecomment-1201479629

Looks like we have a unit test that tests this already.

    #[test]
    fn script_builder_verify() {
        let simple = Builder::new()
            .push_verify()
            .into_script();
        assert_eq!(simple.to_hex(), "69");
        let simple2 = Builder::from(vec![])
            .push_verify()
            .into_script();
        assert_eq!(simple2.to_hex(), "69");

        let nonverify = Builder::new()
            .push_verify()
            .push_verify()
            .into_script();
        assert_eq!(nonverify.to_hex(), "6969");

Nice, didn't notice it.


Fix android lifecycle error

To whom it may concern,
I found there is a android lifecycle mistake. Here is my correct version.
Thanks for your awsome project.
Regards,
Johnny

Thank you @j796160836!

@g-ortuno Can we push an update to the Play Store so that everyone gets the fix?
It will be useful for web bluetooth codelabs at the Chrome Dev Summit in particular.

@beaufortfrancois oops, I missed this. Will do.

(gentle ping)

@beaufortfrancois New version published to the store.

:+1:


Any way to set naming convention for specific properties starting with one-lowercase-letter

If we have a field name in Json like FIELD One, it would be named as fIELDOne in the generated class by jsonschema2pojo. This causes issues while using PropertyDescriptor which follows Java naming convention to extract the property name from its accessors methods (i.e for the exampled field, accessor methods would be getFIELDOne() and setFIELDOne() which will make the property name as FIELDOne (because as both the 2 first letters of FIELD are capitalized, the Java Bean thinks FIELD is something like URL)
It's required for jsonschema2pojo to treat the Json properties starting with 2 capitalized letters, the same way the Java Bean specification does. (naming FIELD One as FIELDOne, not fIELDOne)
You can read more about an issue case this incompatibility made, here
Is there any quick fix for now?
Thanks

Which version of jsonschema2pojo are you using?
We rectified this naming edge case in https://github.com/joelittlejohn/jsonschema2pojo/issues/756

I have added jsonschema2pojo using maven, the version is 1.0.1

Which version of jsonschema2pojo are you using?
We rectified this naming edge case in #756

Hi, Any update on this?

It is still broken in 1.0.2
@joelittlejohn I believe that regression was introduced with #850
It can be observed that assertions eg.
assertThat(nameHelper.getGetterName("URL", new JCodeModel().INT, NODE), is("getURL"));
assertThat(nameHelper.getSetterName("URL", NODE), is("setURL"));

guarding given expected behavior in NameHelperTest::testGetterNamedCorrectly and NameHelperTest::testSetterNamedCorrectly were modified  to:
assertThat(nameHelper.getGetterName("URL", new JCodeModel().INT, NODE), is("getUrl"));
assertThat(nameHelper.getSetterName("URL", NODE), is("setUrl"));


AS in select query

I want to select fields from the table with AS key word,How can i use?
SELECT party_id AS "OrganizationId" FROM party_relation;

CREATE VIEW foo AS
SELECT party_id AS "OrganizationId" FROM party_relation;

Then this will be accessible at the route /foo.

Ideally you'll keep party_relation will in an underlying private schema, and foo in a schema called 1 which will be the publicly visible interface to the first version of your api.

Let's reopen this issue if creating the view doesn't solve your problem.