HL-699 | Batch proposals as manual process to Talpa

Description :sparkles:
Implement backend and frontend for processing applications from Ahjo towards Talpa.

Extract batch views to their own components and files
Implement "accordion" functionality to batch tabs
Send batch back to proposal phase
Send batch to completion (Talpa)

Validate fields with Formik and submit form to backend

Write some backend validations for batches

Testing
Frontend
https://localhost:3100
Backend
docker exec -it --user appuser benefit-backend pytest

Codecov Report

Merging #2031 (e30ff35) into develop (b31561d) will decrease coverage by 15.81%.
The diff coverage is 2.22%.

@@             Coverage Diff              @@
##           develop    #2031       +/-   ##
============================================
- Coverage    34.22%   18.41%   -15.81%
============================================
  Files          744      232      -512
  Lines        14461     5425     -9036
  Branches      3062     1327     -1735
============================================
- Hits          4949      999     -3950
+ Misses        9038     4271     -4767
+ Partials       474      155      -319

Impacted Files
Coverage Δ

...c/components/applicationList/ApplicationList.sc.ts
55.55% <ø> (-4.45%)
:arrow_down:

...mponents/applicationReports/ApplicationReports.tsx
0.00% <0.00%> (ø)

...onents/applicationReports/useApplicationReports.ts
0.00% <0.00%> (ø)

...ents/applicationsArchive/ApplicationsArchive.sc.ts
0.00% <0.00%> (ø)

...onents/applicationsArchive/ApplicationsArchive.tsx
0.00% <0.00%> (ø)

...ents/applicationsArchive/useApplicationsArchive.ts
0.00% <ø> (ø)

...components/batchProcessing/ApplicationsHandled.tsx
0.00% <0.00%> (ø)

.../components/batchProcessing/BatchActionsToAhjo.tsx
0.00% <0.00%> (ø)

...omponents/batchProcessing/BatchApplicationList.tsx
0.00% <0.00%> (ø)

.../src/components/batchProcessing/BatchProposals.tsx
0.00% <0.00%> (ø)

... and 15 more

... and 523 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

API branch is deployed to platta: https://kesaseteli-pr2031.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://handler-pr2031.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://handler-pr2031.dev.hel.ninja :laughing::tada::tada::tada:

API branch is deployed to platta: https://kesaseteli-pr2031.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

API branch is deployed to platta: https://kesaseteli-pr2031.api.dev.hel.ninja/healthz :rocket::rocket::rocket:


Azure Policy Assignment rules are not working against any subscription. Rules processed: 0, failed: 0, errored: 0

I try to use Azure policy assignment data as a rule to check a specific Azure subscription for a compliance
I use the following script:
$outputPath = "$ENV:temp"
$scope = '/providers/Microsoft.Management/managementGroups/mgName'
$targetSubId = 'nnnnnnnn-nnnn-nnnn-nnnn-nnnnnnnnnnnn'

$azPolicyAssignmentData = Export-AzPolicyAssignmentData -Scope $scope -OutputPath $outputPath
$azPolicyAssignmentRuleData = Export-AzPolicyAssignmentRuleData -AssignmentFile $($azPolicyAssignmentData.fullname) -OutputPath "$outputPath\custom-rules"

$context = Set-AzContext -SubscriptionId $targetSubId
$azRuleData = Export-AzRuleData -Subscription $($context.subscription.name) -OutputPath $outputPath

Set-Location $outputPath
$option = New-PSRuleOption -Option @{ 'Rule.includeLocal' = 'true' }
Assert-PSRule -Path 'custom-rules' `
    -InputPath $($azRuleData.FullName) `
    -OutputPath "$outputPath\output.json" `
    -OutputFormat Json `
    -Option $option

It always returns that nothing has been found:
Rules processed: 0, failed: 0, errored: 0
Run 1f66aa572d21c03466f67dcd55b89abba6f3abbc5153ee9cd912f4c54c529a83cf453caea2e5252f9f9fcb674778da9c8bc7fccf5f648afeace3f11134be9637 completed in 00:00:01.4179711
OperationStopped: Index was outside the bounds of the array.
Module versions:
Version Name

2.9.0   PSRule
1.31.3  PSRule.Rules.Azure
For testing purpose:
I exported Azure Policy Assignment data for a specific target subscription and then tried to run "Assert-PSRule" against the same Azure subscription.
Result always is "Rules processed: 0, failed: 0, errored: 0"
From Azure Policies blade I clearly see that there are compliant and non compliant policies.
Am I missing something?

@bbz94 There could be a bug here, but first try setting binding option because this is required with any custom rules. https://microsoft.github.io/PSRule/v2/concepts/PSRule/en-US/about_PSRule_Options/#bindingtargettype
You add this to ps-rule.yaml but to add it to you command line:
$outputPath = "$ENV:temp"
$scope = '/providers/Microsoft.Management/managementGroups/mgName'
$targetSubId = 'nnnnnnnn-nnnn-nnnn-nnnn-nnnnnnnnnnnn'

$azPolicyAssignmentData = Export-AzPolicyAssignmentData -Scope $scope -OutputPath $outputPath
$azPolicyAssignmentRuleData = Export-AzPolicyAssignmentRuleData -AssignmentFile $($azPolicyAssignmentData.fullname) -OutputPath "$outputPath\custom-rules"

$context = Set-AzContext -SubscriptionId $targetSubId
$azRuleData = Export-AzRuleData -Subscription $($context.subscription.name) -OutputPath $outputPath

Set-Location $outputPath
$option = New-PSRuleOption -Option @{ 'Rule.includeLocal' = 'true'; 'Binding.TargetType' = 'resourceType', 'type' }
Assert-PSRule -Path 'custom-rules' `
    -InputPath $($azRuleData.FullName) `
    -OutputPath "$outputPath\output.json" `
    -OutputFormat Json `
    -Option $option

If you're still getting an exception, can you start with:

Confirming that there is a .Rule.jsonc file written to your custom-rules path and it has rules within it.
Confirming that there is a JSON file written to your temp output that containing Azure resources within it.

@BernieWhite
I tried with:
$option = New-PSRuleOption -Option @{ 'Rule.includeLocal' = 'true'; 'Binding.TargetType' = 'resourceType', 'type' }

I still receive the following output:
Rules processed: 0, failed: 0, errored: 0
I verified that rule files do exist in custom-rules folder (In total 307 rules):
Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a---          18.12.2023    10:26         377976 definitions-export-439de130.Rule.jsonc

Any ideas why it does not work?

@bbz94 your process seems fine. Are you able to share your .Rule.jsonc.

@BernieWhite  I will not share the whole file but I can share one of the rules:
  [
    {
        // Synopsis: The Guest Configuration extension requires a system assigned managed identity. Azure virtual machines in the scope of this policy will be non-compliant when they have the Guest Configuration extension installed but do not have a system assigned managed identity. Learn more at https://aka.ms/gcpol
        "apiVersion": "github.com/microsoft/PSRule/v1",
        "kind": "Rule",
        "metadata": {
            "name": "Azure.Policy.eba3fd518936",
            "displayName": "Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity",
            "tags": {
                "Azure.Policy/category": "Security Center"
            },
            "annotations": {
                "Azure.Policy/id": "/providers/Microsoft.Authorization/policyDefinitions/d26f7642-7545-4e18-9b75-8c9bbdee3a9a",
                "Azure.Policy/version": "1.0.1"
            }
        },
        "spec": {
            "recommend": "The Guest Configuration extension requires a system assigned managed identity. Azure virtual machines in the scope of this policy will be non-compliant when they have the Guest Configuration extension installed but do not have a system assigned managed identity. Learn more at https://aka.ms/gcpol",
            "type": [
                "Microsoft.Compute/virtualMachines/extensions"
            ],
            "with": [
                "PSRule.Rules.Azure\\Azure.Policy.Indexed"
            ],
            "where": {
                "field": "properties.publisher",
                "equals": "Microsoft.GuestConfiguration"
            },
            "condition": {
                "field": "resources",
                "allOf": [
                    {
                        "field": "identity.type",
                        "contains": "SystemAssigned"
                    }
                ],
                "where": {
                    "allOf": [
                        {
                            "type": ".",
                            "equals": "Microsoft.Compute/virtualMachines"
                        },
                        {
                            "name": ".",
                            "equals": "[first(split(field('fullName'), '/'))]"
                        }
                    ]
                }
            }
        }
    }
]

I tried to "Assert-PSRule" using this one rule, and the result still is the same:
Rules processed: 0, failed: 0, errored: 0
Run 69f78c9bcdb405439e7eb8c32b66259a3d5a9282 completed in 00:00:01.0382695
OperationStopped: Index was outside the bounds of the array

@bbz94 There looks to be a problem with how this rule is being generated. Thanks for reporting the issue.

@BernieWhite  I'm still getting the same result with the latest module.
Name                            Version
----                            -------
PSRule                          3.0.0
PSRule.Rules.Azure              1.33.1

I'm using following script:
$azPolicyAssignmentData = Export-AzPolicyAssignmentData -Scope $scope -OutputPath $outputPath
$azPolicyAssignmentRuleData = Export-AzPolicyAssignmentRuleData -AssignmentFile $($azPolicyAssignmentData.fullname) -OutputPath "$outputPath\custom-rules"

$context = Set-AzContext -SubscriptionId $targetSubId
$azRuleData = Export-AzRuleData -Subscription $($context.subscription.name) -OutputPath $outputPath

Set-Location $outputPath
$option = New-PSRuleOption -Option @{ 'Rule.includeLocal' = 'true'; 'Binding.TargetType' = 'resourceType', 'type' }
$psRule = Assert-PSRule -Path 'custom-rules' `
    -InputPath $($azRuleData.FullName) `
    -OutputPath "$outputPath\output.json" `
    -OutputFormat Json `
    -Option $option

It generates following rules:
// Synopsis: Deploys the diagnostic settings for Key Vault to stream to a regional Log Analytics workspace when any Key Vault which is missing this diagnostic settings is created or updated.
"apiVersion":"github.com/microsoft/PSRule/v1","kind":"Rule","metadata":{"name":"Azure.Policy.5429c3cd4126","displayName":"Deploy Diagnostic Settings for Key Vault to Log Analytics workspace","tags":{"Azure.Policy/category":"Monitoring"},"annotations":{"Azure.Policy/id":"/providers/Microsoft.Authorization/policyDefinitions/bef3f64c-5290-43b7-85b0-9b254eef4c47","Azure.Policy/version":"3.0.0"}},"spec":{"recommend":"Deploys the diagnostic settings for Key Vault to stream to a regional Log Analytics workspace when any Key Vault which is missing this diagnostic settings is created or updated.","type":["Microsoft.KeyVault/vaults"],"with":["PSRule.Rules.Azure\\Azure.Policy.Indexed"],"condition":{"field":"resources","allOf":[{"allOf":[{"greaterOrEqual":1,"field":"properties.logs[*]","allOf":[{"field":"enabled","equals":"True"},{"field":"category","equals":"AuditEvent"}]},{"greaterOrEqual":1,"field":"properties.metrics[*]","allOf":[{"field":"enabled","equals":"False"}]},{"anyOf":[{"value":false,"equals":false},{"field":"properties.workspaceId","equals":"/subscriptions/a7adf67c-e781-4e8b-b4df-61d2c57f4ece/resourceGroups/rg-mgmt-p-weu-001/providers/Microsoft.OperationalInsights/workspaces/log-mgmt-p-weu-001"}]}]}],"where":{"allOf":[{"type":".","equals":"Microsoft.Insights/diagnosticSettings"},{"name":".","equals":"[parameters('profileName')]"}]}}}},{

I receive following error:
    ____  _____ ____        __
   / __ \/ ___// __ \__  __/ /__
  / /_/ /\__ \/ /_/ / / / / / _ \
 / ____/___/ / _, _/ /_/ / /  __/
/_/    /____/_/ |_|\__,_/_/\___/

Using PSRule v3.0.0-B0153

----------------------------
Explore documentation: https://aka.ms/ps-rule
Contribute and find source: https://github.com/microsoft/PSRule
Report issues: https://github.com/microsoft/PSRule/issues
----------------------------
   WARN  Target object '5b1956westus' has not been processed because no matching rules were found.
   WARN  Target object 'ado-webhooks-kv-prod' has not been processed because no matching rules were found.

Rules processed: 0, failed: 0, errored: 0
Run 11ea7a401de20d382ec734f1056cc9cb4bb2ac2bdeab2779b7cb683791de7bac5443af997e06052f377962f85de96584ec44a8800b64129d89b589a835cb71bb completed in 00:00:01.3090964
OperationStopped: Index was outside the bounds of the array.

Any solution that would help? Your fix did not fix this problem.
Thank you in advance!

Thanks @bbz94 I'll reopen the issue. I can see this is for a different reason, although the exception is the same.

Separate to that, the updated output doesn't seem to be including PSRule.Rules.Azure which is required for the policy rules to work, maybe add a -Module PSRule.Rules.Azure to your command line.

@BernieWhite -Module PSRule.Rules.Azure solved problem.
Thanks.


Tensorflow and the intel camera

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ D435 }

Firmware Version
5.11.6

Operating System & Version
Raspbian Buster

Kernel Version (Linux Only)
(5.10.17-v7l+)

Platform
Raspberry Pi 4

SDK Version
{2.24.0} }

Language
{python}

Segment
{others }

Issue Description
<Hi, I have spent weeks trying to do object detection and  distance measurement with the intel camera. Essentially, the camera will detect and label an object and measure its distance from the camera. The program must use Tensorflowlite for object detection. Has anyone done a similar project or found anything online to help me. I am stuck and desperately need help. I also cannot find any code online for real-time object detection with the intel camera and tensorflow. Does anyone have any ideas on how to get that to work? Thank you and I appreciate any help. >

Hi @garceling   The RealSense SDK has a TensorFlow compatibility wrapper for Python and examples for it that cover object detection and querying the XYZ coordinates of detected objects.
https://github.com/IntelRealSense/librealsense/tree/master/wrappers/tensorflow

Hi, I was following the link you sent above. And i am a beginning so I am confused on which example shows the object detection. I need it to be above to detect the object and also label it as well.

Object detection is introduced in Part 1 of the examples.
https://github.com/IntelRealSense/librealsense/tree/master/wrappers/tensorflow#part-1---object-detection-and-classification
I do not have information on label creation with the SDK's TensorFlow wrapper though.  If labels are a vital requirement, there is alternatively a guide in the link below for using a RealSense camera with TensorFlow to perform custom object detection with s point cloud and then label it.
https://github.com/jediofgever/PointNet_Custom_Object_Detection

Hi, I finally got the object detection and distance measurement to work for the real depth camera. However, it can only measure distance accurately and recognize objects up to 30 m. Is this a issue with the program/ code I am using, or can the intel D345 only have a range of about 30 m.

The D435 camera model's official depth sensing maximum range is 10 meters, though accuracy starts to noticably drift beyond 3 meters from the camera.  This is less of a problem when analysis is based on RGB images, which do not have that depth sensing limitation.
The D455 model has twice the accuracy over distance of the D435 and so has the same accuracy at 6 meters from the camera that the D435 / D435i has at 3 meters.  The D455 has a minimum depth sensing distance of 0.4 meters though compared to the 0.1 m of D435/i, so is less suited to close-range depth sensing.

可以采用pytorch进行目标检测吗

Translation: "Can pytorch be used for target detection?"
Hello @Larry0607  The tutorial in the link below about target detection with pytorch and YOLOv3 may be helpful to you.
你好 @Larry0607 下面鏈接中關於使用 pytorch 和 YOLOv3 進行目標檢測的教程可能對你有所幫助。
https://www.programmersought.com/article/85671177482/

Hello @Larry0607  Do you require further assistance with this case, please?  Thanks!
你好@Larry0607 請問這個案例你需要進一步的幫助嗎？ 謝謝！

sorry I have a question. I am trying to get the intel camera to detect and object and than measure the angle of the object from the camera. I have attached a link to the image of what I want to achieve. Do you know if this is possible with the intel camera?

Hi @garceling   The resources in the link below will hopefully be helpful for answering your question.
https://github.com/IntelRealSense/librealsense/issues/9297

Hi @garceling  Do you require further assistance with this case, please?  Thanks!

Hi, I was playing around with the intel camera and one thing i noticed was that the camera provides an accurate measurement of the distance of objects located at the center. However, for objects located towards the edge of the camera's frame of view, the distance measurement becomes inaccurate. Does this error have to do with my code, or is it related to the intel camera?

If you are using the get_distance instruction in Python then the effect that you describe is a known phenomenon.  More information about this is in the link below
https://github.com/IntelRealSense/librealsense/issues/9134#issuecomment-852000394

Hi thank you, I was also wondering if it is possible to implement object tracking on a live video with the intel realesense camera.

Hi @garceling  Do you require further assistance with this case, please?  Thanks!

Yes sorry to bother you again, but in response to the inaccuracy of the get_distance function you linked me to this solution: https://github.com/IntelRealSense/librealsense/issues/7395#issuecomment-698016942      So i'm still confused. To fix the inaccuracy, do I just add the rs.align code that they have. Sorry, I am super new at this.

It's no trouble at all.  The RealSense user in that link was suggesting to use the script that is beneath the line in that comments that says Please see below my final stream config code that makes me not receive this error.
If you need an example of depth to color alignment code that you can be confident is correct though, you could try the RealSense SDK's own official align-depth2color.py example script.
https://github.com/IntelRealSense/librealsense/blob/master/wrappers/python/examples/align-depth2color.py

Okay thank you, I was wondering if it was possible to feed a pre-recorded video into the intel camera. I want it to be able to measure the distance of objects not just in real-time, but also through a pre-recorded video

You can record camera data into a bag file, which is like a video recording of camera data, and the RealSense SDK treats it as though it is a live camera feed.

Oh okay. So is this a way to convert a mp4 file into a bag file then.

You could read an mp4 video file into OpenCV, which the RealSense SDK is fully compatible with, and access the frames that way.

Hi, I just recorded a bag file. How do I edit my code, so that instead of taking a live stream, it will work with a bag file instead?

Programs that use live-streaming (including the SDK sample programs) can be modified to use a bag file as their data source instead of a live camera by adding the cfg.enable_device_from_file instruction to a script.  An example of a Python version of this adaptation is below:
pipeline = rs.pipeline()
config = rs.config()
rs.config.enable_device_from_file(config, "test.bag")

You could alternatively store the bag's path in a variable:
rs.config.enable_device_from_file(config, filename)

Hi @garceling  Do you require further assistance with this case, please?  Thanks!

Hi @666tua  https://github.com/tensorflow/tensorflow/issues/57375 suggests running the command below before running your code in order to resolve error in PredictCost().
!apt install --allow-change-held-packages libcudnn8=<IP_ADDRESS>-1+cuda11.2


Undercounting of Ge77 in the Baseline Setup

I found that at least in the baseline setup the number of Germanium 77 produced in the simulation and the number reported by the sensitive detector is different. When more than one Germanium 77 is produced in an event, it can occur that one or several of them are not stored. Specifically, this occurs when there are several events in one of the detector volumes. In that case, the most recent one seems to overwrite possible previous ones in the corresponding maps of the primitive scorer. I assume this due to GetIndex() not being defined in any of the primitive scorers and thus returns the copy number of the detector volumes. I think one could solve this issue by defining the GetIndex() function to return, for example, the TrackID.

Comment on the picture: I know there is a lot of additional output. I just added that one to investigate where the bug originated from. ^_^'
This bug became apparent after implementing an alternative way to register Germanium 77 in order to also get information on the neutron that produced it. As it does not use the sensitive detectors, it is not influenced by this bug.

Hello @MoritzNeuberger ! Thanks for the issue post. The assumption from the start was that Ge-77 production ought to be very rare so checks on multiple production events in the same volume were not conducted. That is very helpful. You are right, the GetIndex will overwrite any existing entry, being the key in a std::map. I've had problems with that feature of primitive scorers in other applications. The scorers are very convenient but maybe a little too convenient for some applications. I think you make a good case for changes. Replacing the index with another unique integer like the track ID could work. One wouldn't really expect the same track producing 2 Ge-77 products.
Another approach I've used on a different project after some exasperation with the scorers is to simply go back to the classic SD and Hit objects where the Hit object simply stores anything of interest in one place and conditions are explicit. I can prepare a branch with that and see where that leads. Unfortunately term time has started again and there is little time available but it wouldn't be a big task given that I've done the same thing recently.
On the neutron parent issue, we've put that in the current code by way of Trajectory objects which store literally everything. That is problematic due to storage issues, there is simply so much to store but if you are only interested in the immediate parent neutron then that's maybe a bit too much information.

Ok, on the GeSD branch I can see several Ge-77 isotope productions in a single event at times. That confirms your observation. A bit of code cleaning and the change to a SD object and a stored Hit object looks a lot cleaner to me. The Ge-77 filter is now in the SD explicitly coded. Not flexible but then it isn't meant to be flexible either.
The multi-production as such is quite re-affirming. It means the volume and placement of individual crystals does play a role. The next set of code changes will hence adapt the geometry to a more realistic placement of smaller Ge crystals instead of the lump 250kg blocks currently in the setup. That should have an effect on the number of multi-production events.

The baseline and alternative geometries now have a suitable Ge array each. Biased running still gives a sizeable fraction of multiple Ge-77 production, apparently, to be checked. The Ge crystal units now have roughly 2.67 kg hence are significantly smaller units. A PR #37 has been submitted to address this current issue.


stm32: clock_control: Enforce HCLK prescaler value

STM32 clock control subsystem allows to configure a different
frequency value for core clock (SYSCLK) and AHB clock (HCLK).
Though, it is HCLK which is used to feed Cortex Systick timer
which  is used in zephyr as reference system clock.
If HCLK frequency is configured to a different value from SYSCLK
frequency, whole system is exposed to desynchro between zephyr clock
subsytem and STM32 HW configuration.
To prevent this, and until zephyr clock subsystem is changed to be
aware of this potential configuration, enforce AHB prescaler value
to 1 (which is current default value in use for all STM32 based
boards).
On STM32H7, enforce D1CPRE which fills the same role as ABH precaler.
On STM32MP1, the equivalent setting is done on A7 core, so it is
not exposed to the same issue as long as SYS_CLOCK_HW_CYCLES_PER_SEC
is set with the 'mlhclk_ck' clock frequency value. Update
matching boards documentation.
Fixes #17188
Signed-off-by: Erwan Gouriou<EMAIL_ADDRESS>

Adding the backport tag since this is valid on 1.14 branch as well.
Though, commit will have to be reworked since STM32H7 is not supported on 1.14

@dbkinder, doc updated, txs for the review


fusion design in vite project that can't be built

Describe the bug

[@alifd/next] vite project import fusion design UI framework,then get mistake  node_modules/@alifd/next/types/drawer/index.d.ts:13:18 - error TS2430: Interface 'DrawerProps' incorrectly extends interface 'HTMLAttributesWeak'.
Types of property 'onVisibleChange' are incompatible.
Type '((visible: boolean, reason: string) => void) | undefined' is not assignable to type '((visible: boolean, type: string | object, e?: {} | undefined) => void) | undefined'.

Libarary Info(please complete the following information):
Libarary: [@alifd/next]

Version [1.25.19]

To Reproduce
Steps to reproduce the behavior:
1、pls. take a look at this online demo https://stackblitz.com/edit/vitejs-vite-ajpyen?file=src%2FApp.tsx
2、open a new terminal to run "npm run build",then you will see the mistake info
Expected behavior
when run "npm run build",there is no mistake and can packaged ok
** Error message**
Paste the error message here.
Additional context
Add any other context about the problem here.

The build failure is not related to vite-plugin-imp
you can try to comment out vite-plugin-imp and run npm run build
export default defineConfig({
  plugins: [
    react(),
    // vitePluginImp({
    //   libList: [
    //     {
    //       libName: '@alifd/next',
    //       style: (name: string) => {
    //         return<EMAIL_ADDRESS>    //       },
    //     },
    //   ],
    // }),
  ],
});

it will get the some error.
I guess this is a related with @alifd/next
if you want to avoid this error, you can try to modify the build script in package.json to:
"build": "vite build"

just remove tsc  and it will build successfully.


/chargetranks command and /charsetrank added and noModelChange bool

@all-contributors please add @karl-police for code


RecycleItemWorker implemented (runs on every tick)

Simple RecycleItemWorker implementation. Doesn't add any more features on top of already existing code.
Adds a different call to bot.item_count_inventory('all'), which returns the count of every item in the inventory.

You are kinda stepping on @surceis toes here @douglascamata. Haha https://github.com/PokemonGoF/PokemonGo-Bot/pull/1143

@TheSavior I saw that, but that one's code looks gigantic and has more features. This keeps the features we have with simple code.

I'm worried that if we merge this one, then we won't get those additional features. I like iterative PRs, but @surceis has put in a bunch of work so I want to be supportive and make sure we can get it in.

Sure, you can merge this. Then i can try to PR only info at start with not only pokeballs?

Alright. Sounds good. Thanks @surceis!

:+1:

@TheSavior I'll move the RecycleItemsWorker(self).work() to inside work_on_cells method, like in @Surceis's PR.

@douglascamata, get your butt on slack! 👮

{ "101": { "keep" : 50 }, "102": { "keep" : 50 }, "103": { "keep" : 50 } }

Just in case, what if we have 50 of each balls (150 in sum), and want to keep only a powerful balls, and when they gone (powerful) to keep weaker one (previous), but when powerful is exist and greater than "keep" value, remove weaker one? Can this be solved?

👍

@Sourceis: nope, this is a complicated but interesting situation.

:+1:

I git pull dev version now always try
Cleaning up Pokemon Bag using the release config
[05:32:35] Pokemon Bag has been cleaned up!


Move from net8.0 prerelease to main

Update ETA is today: https://github.com/Yellow-Dog-Man/Resonite-Issues/discussions/2539#discussioncomment-10246785

Update has been released, merging this.


[Bug]: React SDK. useThemeParams's result isn't being updated

Telegram Application
Telegram Desktop
Describe the Bug
I assume that when colors are being changed in the super app the resulting object from the hook should also be updated but it is not
To Reproduce
Assumed that we use this hook somewhere in our app and set, for example, textColor from the result to some element.
Steps to reproduce the behavior:

Open mini app
Change color scheme in the mini app
Nothing happens in the mini app

Expected Behavior
Result of the useThemeParams hook is always up-to-date. Meaning that color of the text, in our case, is being updated instantaneously

I wasn't able to reproduce the problem.
Make sure, you are using the latest version of the package.

Checked in the mini application here
This mini app source code working with theme

Changing theme in Telegram desktop updates the colors inside the mini app


Replaced with prop-types and RN upgrade

React Native version upgrade to 0.63.2
Replaced ViewProptypes with prop-types  - Fixes #355
Since ViewPropTypes now is deprecated on the latest version of react-native-web

up!

Please merge it,

@oblador can you take care of it?

This is needed for the package to work with React Native Web!

I'm using this branch now with RNW and it works great. Hoping it gets merged.

@ianmartorell Thank you so much for the review 😄

@oblador Is this good to go ?

@oblador Bump to see if we can get this merged and released 😄

@oblador Can we please get this merged and released :)

@oblador Can we please get this merged and released :)

@oblador Can we get this PR merged?

@oblador Can we get this PR merged?

I personally after install the npm package should manually change this line to resolve the error on the web app
@oblador please merge it 🥇

I personally after install the npm package should manually change this line to resolve the error on the web app
@oblador please merge it 🥇

If you are tired of waiting and having to fix this manually, you install from JijoBose branch as a workaround:
yarn add https://github.com/JijoBose/react-native-collapsible.git#bug/proptype

Superseded by #399


ERROR: Your GPU does not support Int8 Matmul!

nvidia-smi

+-----------------------------------------------------------------------------+
| NVIDIA-SMI 515.65.01    Driver Version: 515.65.01    CUDA Version: 11.7     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  Tesla P40           Off  | 00000000:02:00.0 Off |                  Off |
| N/A   29C    P8    10W / 250W |     24MiB / 24576MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  Tesla P40           Off  | 00000000:03:00.0 Off |                  Off |
| N/A   26C    P8     9W / 250W |     40MiB / 24576MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
+-----------------------------------------------------------------------------+

python -m bitsandbytes

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++ DEBUG INFORMATION +++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

++++++++++ POTENTIALLY LIBRARY-PATH-LIKE ENV VARS ++++++++++
'CONDA_EXE': '~miniconda3/bin/conda'
'CONDA_PREFIX': '~/miniconda3'
'CONDA_PYTHON_EXE': '~/miniconda3/bin/python'
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

WARNING: Please be sure to sanitize sensible info from any such env vars!

++++++++++++++++++++++++++ OTHER +++++++++++++++++++++++++++
COMPILED_WITH_CUDA = True
COMPUTE_CAPABILITIES_PER_GPU = ['6.1', '6.1']
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++ DEBUG INFO END ++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Running a quick check that:
    + library is importable
    + CUDA function is callable

SUCCESS!
Installation was successful!

=============================================
ERROR: Your GPU does not support Int8 Matmul!
=============================================

python: /mmfs1/gscratch/zlab/timdettmers/git/bitsandbytes/csrc/ops.cu:379: int igemmlt(cublasLtHandle_t, int, int, int, const int8_t*, const int8_t*, void*, float*, int, int, int) [with int FORMATB = 3; int DTYPE_OUT = 32; int SCALE_ROWS = 0; cublasLtHandle_t = cublasLtContext*; int8_t = signed char]: Assertion `false' failed.
Aborted (core dumped)

Same problem with my P40. I was under the impression the P40 supported all the int8 operations and Cuda Compute v6.1

The Int8 Matmul feature relied on Int8 Tensor Cores and as such your GPUs were not supported. This changed with the commit de535889348c5406eb34d9f7e0c362cadb113be5 which is already pushed to pip in the latest 0.37.0 version. So if you update it should work for you now.
Please reopen this issue if you encounter any problems.

I have update to 0.38.1 version, but this problem still exists.

Having the same issue here


Segmentation fault (core dumped)

The following error occurs.
I am using Ubuntu 22.04, and I utilized the provided conda environment.
Loaded checkpoint 'checkpoints_v2/converter/checkpoint.pth'
missing/unexpected keys: [] []
OpenVoice version: v2
Segmentation fault (core dumped)

Same problem with version 2. I get pass that part but runs into another problem. `****\env\lib\site-packages\torch\nn\modules\conv.py:456: UserWarning: Plan failed with a cudnnException: CUDNN_BACKEND_EXECUTION_PLAN_DESCRIPTOR: cudnnFinalize Descriptor Failed cudnn_status: CUDNN_STATUS_NOT_SUPPORTED (Triggered internally at ..\aten\src\ATen\native\cudnn\Conv_v8.cpp:919.)
return F.conv2d(input, weight, bias, self.stride,

Text split to sentences.
Hello

0%|                                                                                | 0/1 [00:00<?, ?it/s]Some weights of the model checkpoint at bert-base-uncased were not used when initializing BertForMaskedLM: ['bert.pooler.dense.bias', 'bert.pooler.dense.weight', 'cls.seq_relationship.bias', 'cls.seq_relationship.weight']

This IS expected if you are initializing BertForMaskedLM from the checkpoint of a model trained on another task or with another architecture (e.g. initializing a BertForSequenceClassification model from a BertForPreTraining model).
This IS NOT expected if you are initializing BertForMaskedLM from the checkpoint of a model that you expect to be exactly identical (initializing a BertForSequenceClassification model from a BertForSequenceClassification model).
0%|                                                                                | 0/1 [00:01<?, ?it/s]
Error during audio generation: too many dimensions 'str'`


[release-1.24] Backports for 2022-11

Backport fixes for the following issues to the release-1.24 branch:

#6146
#6421
#6422
#6273
#6304
#6423
#2955
#6377
#6424
#6377
#5184
#6358
#5562
#6401
#5562
#6401
#6425

Containerd config version 1 is deprecated #6421
Validation containerd version is updated to version 2
$ sudo cat /var/lib/rancher/k3s/agent/etc/containerd/config.toml

version = 2

[plugins."io.containerd.internal.v1.opt"]
  path = "/var/lib/rancher/k3s/agent/containerd"
[plugins."io.containerd.grpc.v1.cri"]
  stream_server_address = "<IP_ADDRESS>"
  stream_server_port = "10010"
  enable_selinux = false
  enable_unprivileged_ports = true
  enable_unprivileged_icmp = true
  sandbox_image = "rancher/mirrored-pause:3.6"

[plugins."io.containerd.grpc.v1.cri".containerd]
  snapshotter = "overlayfs"
  disable_snapshot_annotations = true

[plugins."io.containerd.grpc.v1.cri".cni]
  bin_dir = "/var/lib/rancher/k3s/data/bda98296b1b7b58d8e7be25d03b6a6999bc6b5c5d2de8482b0d48aee4348ae08/bin"
  conf_dir = "/var/lib/rancher/k3s/agent/etc/cni/net.d"

[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
  runtime_type = "io.containerd.runc.v2"

[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
  SystemdCgroup = true

Confirmed the deprecated error message does not appear in the containerd.log file. Also, there are no additional errors in the log file. sudo grep deprecated /var/lib/rancher/k3s/agent/containerd/containerd.log

Confirmed crictl commands are still working:

$ sudo crictl -r unix:///run/k3s/containerd/containerd.sock ps -a
CONTAINER           IMAGE               CREATED             STATE               NAME                     ATTEMPT             POD ID              POD
52c3fd35dfb44       288889429becf       24 minutes ago      Running             traefik                  0                   299e59a5956b3       traefik-859c5c9f65-pwqx6
33d84b798c844       dbd43b6716a08       24 minutes ago      Running             lb-tcp-443               0                   2733772ebd9d8       svclb-traefik-5571a82a-xjx5j
189edf4ec4db3       dbd43b6716a08       24 minutes ago      Running             lb-tcp-80                0                   2733772ebd9d8       svclb-traefik-5571a82a-xjx5j
3f20300ec09fd       38b3b9ad736af       24 minutes ago      Exited              helm                     1                   f38bddf2af704       helm-install-traefik-lghch
df036be4abdb1       38b3b9ad736af       24 minutes ago      Exited              helm                     0                   33ae5dc03551d       helm-install-traefik-crd-g689r
2d227d89a9932       e57a417f15d36       24 minutes ago      Running             metrics-server           0                   7062ee59cc728       metrics-server-84f8d4c4fc-dx5vd
20110bac88a53       a81c2ec4e946d       24 minutes ago      Running             coredns                  0                   56cef96c3e213       coredns-7b5bbc6644-skjt6
5f7c28f2effa3       9621e18c33880       24 minutes ago      Running             local-path-provisioner   0                   71f6511c53792       local-path-provisioner-687d6d7765-kc4hf

Deploy controller stuck at the server could not find the requested resource when manifest includes removed resource #6273 (In progress...)
other text

Bump dynamic listener to v0.3.5 #6423 (In progress...)

Enable http3 support for Traefik  #5184 (In progress...)
other text

Create by default traefik ingressClass when creating a cluster #5562
$ helm ls -A
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /etc/rancher/k3s/k3s.yaml
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /etc/rancher/k3s/k3s.yaml
NAME       	NAMESPACE  	REVISION	UPDATED                                	STATUS  	CHART               	APP VERSION
traefik    	kube-system	1       	2022-11-10 22:01:11.833979543 +0000 UTC	deployed	traefik-19.0.000    	2.9.4
traefik-crd	kube-system	1       	2022-11-10 22:00:57.82742362 +0000 UTC 	deployed	traefik-crd-19.0.000

$ kubectl get ingressClass -A
NAME      CONTROLLER                      PARAMETERS   AGE
traefik   traefik.io/ingress-controller   <none>       20m

Bump packaged coredns version #6425
CoreDNS version bumped to 1.9.4
$ kubectl describe pod/coredns-7b5bbc6644-skjt6 -n kube-system | grep -i "1.9.4"
    Image:         rancher/mirrored-coredns-coredns:1.9.4
  Normal  Pulling    11m   kubelet            Pulling image "rancher/mirrored-coredns-coredns:1.9.4"
  Normal  Pulled     11m   kubelet            Successfully pulled image "rancher/mirrored-coredns-coredns:1.9.4" in 4.851318932s

$ kubectl get all -l k8s-app=kube-dns -n kube-system -o wide
NAME                           READY   STATUS    RESTARTS   AGE   IP          NODE              NOMINATED NODE   READINESS GATES
pod/coredns-7b5bbc6644-skjt6   1/1     Running   0          12m   <IP_ADDRESS>   ip-172-31-45-77   <none>           <none>

NAME               TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)                  AGE   SELECTOR
service/kube-dns   ClusterIP   <IP_ADDRESS>   <none>        53/UDP,53/TCP,9153/TCP   12m   k8s-app=kube-dns

NAME                      READY   UP-TO-DATE   AVAILABLE   AGE   CONTAINERS   IMAGES                                   SELECTOR
deployment.apps/coredns   1/1     1            1           12m   coredns      rancher/mirrored-coredns-coredns:1.9.4   k8s-app=kube-dns

NAME                                 DESIRED   CURRENT   READY   AGE   CONTAINERS   IMAGES                                   SELECTOR
replicaset.apps/coredns-7b5bbc6644   1         1         1       12m   coredns      rancher/mirrored-coredns-coredns:1.9.4   k8s-app=kube-dns,pod-template-hash=7b5bbc6644

Validated using k3s RC v1.24.8-rc1+k3s1
k3s version v1.24.8-rc1+k3s1 (67fce205)
go version go1.18.8

Replicated using v1.24.7+k3s1

k3s version v1.24.7+k3s1 (7af5b167)
go version go1.18.7

Update embedded helm-controller version #6422 (In Progress)

Race condition in agent controller and load of rolebinding manifest #6304

Replication logs

INFO[0007] Cluster-Http-Server 2022/11/13 13:49:02 http: TLS handshake error from <IP_ADDRESS>:49176: remote error: tls: bad certificate
INFO[0007] Waiting to retrieve kube-proxy configuration; server is not ready: https://<IP_ADDRESS>:6443/v1-k3s/readyz: 500 Internal Server Error
DEBU[0007] Wrote ping
DEBU[0007] Tunnel authorizer failed to get Kubelet Port: nodes "ip-172-31-35-19" is forbidden: User "system:k3s-controller" cannot get resource "nodes" in API group "" at the cluster scope
W1113 13:49:02.740970    1561 reflector.go:324] k8s.io/client-go@v1.24.7-k3s1/tools/cache/reflector.go:167: failed to list *v1.Endpoints: endpoints "kubernetes" is forbidden: User "system:k3s-controller" cannot list resource "endpoints" in API group "" in the namespace "default"
E1113 13:49:02.740999    1561 reflector.go:138] k8s.io/client-go@v1.24.7-k3s1/tools/cache/reflector.go:167: Failed to watch *v1.Endpoints: failed to list *v1.Endpoints: endpoints "kubernetes" is forbidden: User "system:k3s-controller" cannot list resource "endpoints" in API group "" in the namespace "default"

Validation logs does not show the error

I1113 13:54:55.759583    2083 kubelet.go:376] "Attempting to sync node with API server"
I1113 13:54:55.759637    2083 kubelet.go:267] "Adding static pod path" path="/var/lib/rancher/k3s/agent/pod-manifests"
I1113 13:54:55.759686    2083 kubelet.go:278] "Adding apiserver pod source"
I1113 13:54:55.759726    2083 apiserver.go:42] "Waiting for node sync before watching apiserver pods"
I1113 13:54:55.771693    2083 kuberuntime_manager.go:239] "Container runtime initialized" containerRuntime="containerd" version="v1.6.8-k3s1" apiVersion="v1"
I1113 13:54:55.772510    2083 server.go:1177] "Started kubelet"

Update kine/sqlite version #6424

Confirmed via go.mod in release-1.24 branch with commit 67fce20561b06618b82c45b09a719d17ba8efc8e: https://github.com/k3s-io/k3s/blob/67fce20561b06618b82c45b09a719d17ba8efc8e/go.mod#L91
Confirmed via go.mod in release-1.24 branch with commit 67fce20561b06618b82c45b09a719d17ba8efc8e: https://github.com/k3s-io/k3s/blob/67fce20561b06618b82c45b09a719d17ba8efc8e/go.mod#L95

fsGroup does not work with local-path volume #6401 (In Progress)

Validated as part of patch checks with RC v1.24.8-rc3+k3s1


Update GitHub Actions CI

Hi. Thanks for the library! I want to help to actualize the library, it will be a Pull Request series. It's worth starting with CI actualization.

update actions/checkout to v4
replace actions-rs/cargo with using cargo directly
replace unmaintained actions-rs/toolchain by dtolnay/rust-toolchain

Node 16 has reached its end of life, prompting us to initiate its deprecation process for GitHub Actions. Our plan is to transition all actions to run on Node 20 by Spring 2024. https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

Thank you for your PR. It is very well documented, I see no issues, only change I made is removing the additional profile parameter from the toolchain installation. I'll merge this.


How to access drawCount info?

Hey, I can't success to trace the drawCount info from https://github.com/pixijs/pixi-haxe/blob/dev/src/pixi/core/renderers/webgl/WebGLRenderer.hx#L38
Is it the number of draw call ?
How do you access it from the app/Application.hx class ?

Should be accessible via renderer instance https://github.com/pixijs/pixi-haxe/blob/dev/src/pixi/plugins/app/Application.hx#L123

Yeah that's what I thought, but trace(renderer.drawCount); into an update loop always ouput undefined on my side.

I am sure it works. Remember the property is only available in WebGL Renderer. It will be undefined in canvas.

Well, I've this output Pixi.js 4.0.0 - WebGL - http://www.pixijs.com/, so normally I'm in WebGL mode right?

yes it's webgl mode. I checked in v3 and it works. Could be an issue with v4.

Yeah, seems to be https://github.com/pixijs/pixi.js/issues/2568

this was marked for v5, so closing it


doc(Logic/Small/Defs): document Small.{u, max u v} instance

Counterintuitively, we're able to state this theorem before we're able to make it into an instance in an entirely different file.

bors merge


Logging: Remove dbClient global variable

Fixes #2070

Refactored support-logging by creating two new interfaces: Criteria and Persistence. These interfaces are necessary because the container needs an external interface to reference (Persistence) and Persistence depends on a parameter called a MatchCriteria which then itself needs an interface to not have a dependency on the main logging package.

Moved all non-superflous controller logic out of router.go. Since this is a huge change and the primary driver of the source lines of code change, I have made one commit where I move code without changing anything, and the second commit with functional changes. This should allow the changes to be parsed.

Removed dbClient Persistence global.

To verify, run the unit and black box tests.
Signed-off-by: Brandon Forster<EMAIL_ADDRESS>

Codecov Report

Merging #2186 into master will increase coverage by 0.29%.
The diff coverage is 69.55%.

@@            Coverage Diff             @@
##           master    #2186      +/-   ##
==========================================
+ Coverage   39.17%   39.46%   +0.29%
==========================================
  Files         177      178       +1
  Lines       12655    12746      +91
==========================================
+ Hits         4957     5030      +73
- Misses       7428     7444      +16
- Partials      270      272       +2

Impacted Files
Coverage Δ

internal/support/logging/init.go
0% <0%> (ø)
:arrow_up:

internal/support/logging/mongo.go
0% <0%> (ø)
:arrow_up:

cmd/support-logging/main.go
0% <0%> (ø)
:arrow_up:

internal/support/logging/types.go
86.53% <100%> (ø)
:arrow_up:

internal/support/logging/criteria.go
93.54% <60%> (-6.46%)
:arrow_down:

internal/support/logging/rest_logging.go
72% <72%> (ø)

internal/support/logging/file.go
69.01% <73.68%> (ø)
:arrow_up:

internal/support/logging/router.go
90% <89%> (+15.78%)
:arrow_up:

Continue to review full report at Codecov.

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

These interfaces are necessary because the container needs an external interface

FWIW the dependency injection container does not require interfaces; it does support concrete types.

These interfaces are necessary because the container needs an external interface

FWIW the dependency injection container does not require interfaces; it does support concrete types.

Right, but before this PR, there is an unexported interface and two implementations both in the logging package. There is no way to reference that interface in the container without a cyclical dependency unless the interface is moved to its own package. That's what I was trying to say; sorry I was unclear.

There's some questions around whether or not we should be logging to a database; it's useful for development, less so for production.  Thinking here is ELK stack (or similar) would substitute for support-logging.  Ask is to hold off merging this work until I return, review, and resolve the database logging question.

@AnthonyMBonafide @michaelestrin Rebased and feedback addressed.

Approved.  Setting aside until https://github.com/edgexfoundry/edgex-go/pull/2196 is merged.  Expect merge conficts that will require additional work.  Closing PR to ensure it is not accidentally merged.  Will use this work for follow-on PR that is rebased over merged #2196 and that addresses the anticipated merge conflicts.


assertSessionHasErrors doesn't work with named MessageBag (only with "default")

Laravel Version: 5.4.21
PHP Version: 7.1.1

Description:
When doing test using assertSessionHasErrors method the test will fail if you validate the request using MessageBag with your own name (not "default") even thought the validation rules are set and validation works in browser.
Steps To Reproduce:
In my controller in store method I have:
$this->validateWithBag('answer', request(), [
    'body' => 'required'
]);

When I do assert in my test file like this:
$response->assertSessionHasErrors('body');
it fails with message "Session missing error: body".
It pass when in controller I change to:
$this->validate(request(), [
    'body' => 'required'
]);

I am using named MessageBag as I have two forms on one page with textarea field (both called "body").

As for now I've solved this issue with the below solution but propably there is a better way.
In Illuminate\Foundation\Testing\TestResponse.php I changed the line 544 (in assertSessionHasErrors method) from:
PHPUnit::assertTrue($errors->has($value), "Session missing error: $value");
to:
PHPUnit::assertTrue(collect($errors->getBags())->first()->has($value), "Session missing error: $value");

Added this as a feature in a PR for 5.5: https://github.com/laravel/framework/pull/19172


GPU on EKS Blueprint with Time slicing and MIG examples

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

Add a new blueprint for ai-ml/gpu-on-eks with p5 node groups and karpenter provisioner
Add Website Doc for deploying and running Training examples
Add examples for Time slicing and MIG with GPUs
Show the logging and observability for these examples (Can be Part2 PR)
Use Custom AMI with

Describe the solution you would like

Describe alternatives you have considered

Additional context

Closing this issue as this feature is covered by JARK stack and JupyterHub blueprints


fix: Remove performance limitation when using Java Virtual Threads

Multiple, potentially lengthy read and write methods use the synchronized keyword. This will pin virtual threads, preventing them from being detached from carrier platform threads during these operations. This prevents virtual threads from providing the concurrency and throughput they were designed for when using this library.
Per Oracle... Pinning does not make an application incorrect, but it might hinder its scalability. Try avoiding frequent and long-lived pinning by revising synchronized blocks or methods that run frequently and guarding potentially long I/O operations with java.util.concurrent.locks.ReentrantLock.
This commit replaces the synchronized keyword with a ReentrantLock on select methods. Not all synchronized keywords are gone, only the ones on methods that obviously might take a while. I was conservative as I'm new to the codebase.
A more complete explanation is available in this article.

Thank you for bringing raising this issue. Virtual threads are something we're going to look at in 2024.
Unfortunately, I think this PR is not comprehensive enough to cover the threading and synchronization expectations much of the library internals assume today.
I've created https://github.com/googleapis/java-storage/issues/2308 as a public tracking issue for the feature request of improving Virtual Thread Compatibility.
Apologies, we can't accept this contribution at this time.
PS: If you are running into contention issues on ReadChannel specifically, you could try ReadChannel.setChunkSize(0) which will remove any intermediary buffering and give a near non-blocking read semantic. For WriteChannel we don't have a similar path, as the chunk based processing and retry loop introduces backpressure with the tradeoff of reliability.

Hey @BenWhitehead
Thanks for your comment. I'm a little unclear on why this is being rejected. This is a one for one, zero impact replacement of the synchronized keyword with ReentrantLock based directly on Oracle's recommendations which solves a performance (not a contention or buffering) issue for Goggle customers. Suggest you review the referenced article for a more detailed description.

I reviewed the Oracle article linked in the issue. And while superficially things should be okay, historically we have found issues in the JDK itself and had to work on getting them fixed and/or working around the constraints they present (for example, we've found cases where the jdk was erroneously sending multiple http requests instead of just one, cases where decompression would stop part way through without an error). This also applies to the intermediary libraries our clients depend on as well.
With the level of existing threading, synchronization, native code cross library compatibility layers and other complexities in the library we need to take a deeper investigation of our client and its dependencies to ensure there is not anything adverse lurking in the shadows. This is something that is on our radar for next year. There is some work already happening around virtual threads and java 21 compatibility that we don't yet have publicly shareable dates on.
I apologies for not being able to accept this contribution right now, but there is other due diligence we are still doing around virtual threads.

"historically we have found issues in the JDK itself"
This level of - I can only call it - paranoia is disappointing. Every contribution is rejectable on those grounds, so you might as well remove "Contributions to this library are always welcome" from the README. No change is provably safe if you doubt the ability of the platform to execute it according to its own specification. 1 + 1 might one day be 3.
If this is your opinion, then you should never change any line ever again.

I echo @michaelboyles feeling. Disappointing to say the least, especially since the changes are so trivial they're inspectable for correctness, let alone the unit and integrations test which I ran with positive results. Just FUD on Google's part IMO.

Hi @PhilBoutros and @michaelboyles,
I thank you for raising this request, but we aren't ready for this change just yet. @BenWhitehead has created a tracking issue calling out that it's on our teams radar (https://github.com/googleapis/java-storage/issues/2308).
I'm closing this pull request and our team will discuss prioritization. Stay tuned.


proposal: Go 2: Error handling check/with

The proposal:
The overview of the error handling problem described here is spot on. The verbosity of error handling can make it tough to spot bugs. However, the design didn't allow for much flexibility in that the check used the most recent, in-scope handle. That doesn't provide a lot of flexibility to users. We can do better, by treating handle as a function (one that either takes a single error argument, or variadic args with the requirement the last arg is the error to check).
I propose we introduce 2 new keywords, check and with:
When we check a return value, we can specify how we want to handle it, like so:
func myFunc() error {
   check doSomething() // return if error

   check doSomething with func(err error) {return fmt.Errorf("error doing something %w", err)}
}

More information and examples in the template below

Would you consider yourself a novice, intermediate, or experienced Go programmer?

5+ YOE with Go in production/enterprise

What other languages do you have experience with?

Java, C, python, dart/typescript/javascript,

Would this change make Go easier or harder to learn, and why?

Easier, minimal new complexity, while readability is greatly increased

Has this idea, or one like it, been proposed before?

Yes, many error proposals exist

If so, how does this proposal differ?

At this point, all of the various error proposals are slightly nuanced. I believe this proposal offers better flexibility in specifying the error handler, while maintaining clear readability.
Is this change backward compatible?

Adds new keywords

Show example code before and after the change.
See the example from the this previous draft's overview for the before.
After:
func formattedError(fmtStr string) func(err error) error {
	return func(err error) error{
		return fmt.Errorf(fmtStr, err)
	}
}

func CopyFile(src, dst string) (err error) {
        handler := formattedError(fmt.Sprintf("copy %s %s: %w", src, dst))
        r := check os.Open(src) with handler
        defer r.Close() with handler // could alternatively call formattedError directly.

        w := check os.Create(dst)
        defer w.Close()

        check io.Copy(w, r) with func(err error) error {return os.Remove(dst)}
        check w.Close() with func(err error) error { return os.Remove(dst)}
        return nil
}

How many tools (such as vet, gopls, gofmt, goimports, etc.) would be affected?

anything that parses go code.

What is the compile time cost?

Likely minimal. Not sure if this would cause issues with unbounded lookahead though

What is the run time cost?

Depends on implementation/negligible
How would the language spec change?
As described

Orthogonality:

how does this change interact or overlap with existing features?
check would look similar to a return. Take some time to wrap our heads around that, but a welcome improvement to the current 3-liner.

Is the goal of this change a performance improvement?

No

Does this affect error handling?

Yup!

If so, how does this differ from previous error handling proposals?

Again differences are nuanced but a cleaner syntax (IMO), and an expressive with check that allows flexibility in determining the handle function.
Is this about

generics?

No

Thanks for the suggestion, but based on the discussion above, and the emoji voting, this is a likely decline.  Leaving open for four weeks for final comments.

No further comments.


Bug fix for Settings toLowerCase causes issues for Turkish locale

When I try to connect my local clickhouse server,
I had this issue and found out related this thread https://youtrack.jetbrains.com/issue/DBE-9900
Fix #463

@rewebcan, could you change target to develop so that I can merge?

@rewebcan, could you change target to develop so that I can merge?

Fixed in 47747d1a60935ec5028571438bbfa31dd8498aed.

Fixed in 47747d1a60935ec5028571438bbfa31dd8498aed.


Bugfix/badlinktrackhubdoc

Highlighted by Ann Zweig we were pointing to the wrong docs.

Sorry didn't realise that was going to bring in a load of postreleasefix code in. Sorry


Table row or cell with overflow setting breaks popup placement

CodePen demo

https://codepen.io/anon/pen/dJweJm
Steps to reproduce the problem

Have a table row or cell with any overflow, even overflow: auto;

What is the expected behavior?
pop is below ref
What went wrong?
pop is on top of ref
Any other comments?
Breaks on all browsers so far.

This is fixed in v2
https://codepen.io/FezVrasta/pen/wvBoGpN


will it work on arm (aarch64) ?

hi !
i have installed unsloth on my raspberry pi 4b. but it needs torch with cuda.
no cuda - no gain ?

Ye sadly it must have a NVIDIA GPU


Customize HOSTname for NGINX to UWSGI connection

Is your feature request related to a problem? Please describe
I am trying to get DefectDojo to run in AWS Fargate. I almost got it to work, however due to how Fargate network configuration works within a Fargate Task containing multiple containers I run into the following problem. Fargate works with a local-loopback so connection should work on <IP_ADDRESS>. I got the communication from the Celery nodes to RabbitMQ working by overriding the Name: DD_CELERY_BROKER_HOST with Value: <IP_ADDRESS>
Describe the solution you'd like
I would like a variable called DD_UWSGI_HOST for the container defectdojo/defectdojo-nginx which overrides the default hardcoded uwsgi and results the error on startup:
nginx: [emerg] host not found in upstream "uwsgi:3031" in /run/uwsgi_server:1
Describe alternatives you've considered
nvt
Additional context
nvt

Never mind, made a boo boo
https://github.com/DefectDojo/django-DefectDojo/blob/master/Dockerfile.nginx
DD_UWSGI_HOST :-)


Update scala3-library to 3.1.3-RC1-bin-20220126-8ae2962-NIGHTLY

Updates org.scala-lang:scala3-library from 3.1.2-RC1-bin-20220121-7ce60e1-NIGHTLY to 3.1.3-RC1-bin-20220126-8ae2962-NIGHTLY.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala3-library" } ]

labels: library-update, early-semver-pre-release, semver-spec-pre-release, commit-count:1

Superseded by #1116.


feat(NumberTheory/EulerProduct/DirichletLSeries): use infinite product and L-series

This is a follow-up to #12161.
It adds HasProd and tsum versions of the Euler Product statements for the Riemann zeta function and Dirichlet L-series (in the latter case, also replacing the explicit infinite sum by L ↗χ s).
See this Zulip thread.

For some reason, I tend to not think of apply in this situation...
Thanks for the speed-up!

maintainer merge

Congratulations :-) It's funny that we had special values of zeta at negative integers before we had resolved the issue of the definition of an infinite product :-)
bors merge


2023 08 15

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.
Breaking change in KustoClusterPatch causes build to fail.
Please assist with this fix.
Tests haven't been recorded yet due to inability to build.

@t-abebchuk:  Our automation is recognizing you as a community member.  Please review the Azure SDK onboarding documentation and ensure that your GitHub organization membership and permissions are correct before moving this out of draft.

Azure SDK onboarding (Microsoft internal)
Azure SDK onboarding assistance (Microsoft internal)

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


Fixed wrong namespace (s/testns1/testns2)

fix small mistake - s/testns1/testns2

let me skip review as it's small fix


xfail tests for UB

OK, I don't want to actually merge this right now, I just want it sitting here where people can see it.
@rsas and @zhengyangl, please issue a pull req to my branch if you find an interesting test case where souper's UB model prevents it from doing this right thing. We'll use these to help us get UB right.

I recall having a couple of those, I'll try to find them again.


Fix: CVE-2024-41131 by updating ImageSharp from 3.1.4 -> 3.1.5

See: https://github.com/neozhu/CleanArchitectureWithBlazorServer/security/dependabot/7

thank you


How do I include ID, when returning models?

I have a user model defined as:
export class User extends Model {
    protected table: string = "users";
    protected primaryKey: string = "id";

    id!: string;
    name!: string;
    email!: string;
    password!: string;

    hidden: string[] = ["password"];

    toJSON() {
        return {
            id: this.id,
            name: this.name,
        }
    }
(...)

Is it possible to include the id, when returning the model via express, without using the ToJson function?
I expected everything but the items in "hidden" to be returned
I've tested with two models - including the one above, both missing ids when returned via http routes

In fact, you don't need to define the toJSON method, you can directly use the model instance
const user = await User.query().first();
res.json(user);

Here is an example using typescript+express to see if it can solve your problem.
https://github.com/sutandojs/sutando-examples/tree/main/typescript/rest-express

My problem was that "id" was returned as null, most likely because they were mapped wrong due to not being a int but a string
Adding these two:
(...) Model (...)
keyType = 'string';
incrementing = false;

fixed the problem


NPM installation of  "npm install yo -g" fails for spfx framework SET up ( OnPrem)

Target SharePoint environment
SharePoint Server 2019 (on-premise)
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[X] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details
Node.js     v8.11.3
NPM         5.6.0

Corporate Network Behing Proxy.
Describe the bug / error
I am trying to install the sharepoint framework for 2019 ( OnPrem). Initially,  was unable to install packages and after running the npm config commands was successful in installing gulp package.

npm config set proxy
npm config set https-proxy
npm config set registry

The real problem comes when i try to install Yo package.
npm install yo –g
The above command runs and gets installed however, while sanity check, The following error is thrown. I am not getting any Authentication Required error while installing "gulp",. However, when i try to install yo packages, am getting the authentication error messages. attaching a screenshot

Is there any step which am missing ?
Steps to reproduce

Install NodeJS 8.11.3
npm install gulp -g
3.npm install yo -g

Expected behavior
Expecting the installation to complete sucessfully and able to create clientside webparts using yoman templates.

It looks like the got node module is making a call and the request is failing as am behind Corporate Network Behind Proxy.
I did look at the index file as highlighted in the screenshot and noticed that there is no code for proxy support. When i digged into the got module on the web, found out that proxy support was added but looks like those changes didnt get pushed.
https://github.com/alexsantos/got/blob/proxy-from-env/index.js  Line 223.
As it has references to other modules, Wondering how to fix this to make it work.
Also, Which yo template is ideal for setting up development for 2019 environment.
I have
Node : 8.11.3
NPM : 5.6
Yo : 3.1.1

You can try to (It worked for me with SPFx 1.4.1)

install Node 10 (I’m using nvm for switching the Node versions)
remove node_modules
(maybe cleared npm cache - but I’m not sure now)
npm install (it needs to compile dependencies according to used Node version)
gulp trust-dev-cert (to solve Proxy issue)
gulp serve
and cross your fingers …

Sorry - this issue appears to be unrelated to SPFx, and is simply trying to install the yeoman package.  That's outside the scope of this issues list.


Add refresh support for documentColor

Implementing color swatch support for XAML in VS Code runs into some limitations. VS Code does not seem to support streaming progress for the documentColor request.

Colors in XAML documents are based on syntax (i.e. #AARRGGBB) as well as semantic information (e.g. {StaticResource MyColor}).
The second issue is quite a big problem for us since there is no refresh support in the LSP spec for when color information needs to be refreshed (for when the semantic information becomes available or when the MyColor value in a different document gets updated for example).

Similar to recently added refresh support for folding ranges in the proposed 3.18 spec we would like to add refresh support for document colors. The support needs to take into consideration following scenarios:

VS Code startup scenario. Refreshing active XAML document after LSP server gets fully initialized and XAML file is associated with a project (as opposite to being a loose XAML file). For example, if MainPage.xaml is active document when starting VS Code then it takes few seconds for LSP to recognize that it is part of MyApp.csproj and initialize Microsoft.CodeAnalysis.Compilation. In this case we need to refresh active document.
Editing ResourceDictionaries. Editing color values in App.xaml or Colors.xaml - (e.g. <Color x:Key='MyColor'>#123455</Color>) will affect color swatches in MainPage.xaml (e.g. <Button BackgroundColor='{StaticResource MyColor}'/>). In this case we need to refresh all but current document. More specifically, we want to avoid refreshing current document because it already gets refreshed as user types

blocked pending https://github.com/microsoft/vscode/issues/227697


extensions: WikiLinks doesn't conform to its spec

[[Links/With/Subdir/Do/Not/Work]]
[[Links/With/Title|Neither]]

@raliste, please read the documentation to see what is supported: https://python-markdown.github.io/extensions/wikilinks/.
It does work as we do have tests that validate its behavior: https://github.com/Python-Markdown/markdown/blob/master/tests/extensions/wikilinks.txt.
If there are documented features that don't work, please provide clear examples and explain how you are attempting to use it.  Then we can look into an appropriate fix.
Keep in mind, this extension has been around for a while, and I don't think it is claimed anywhere that it is a 1:1 support for wiki links, only that it targets links in the style [[My Wiki Link]].  If it is working as documented, but falls short of your desired features, it might be something to consider writing your own extension for as I'm pretty sure we are currently in a feature freeze for the time being until a 3.0 release.  At that time, extensions are planned (or at least where planned) to be split out into separate repos leaving core Markdown features being the only thing shipped by default.  All other extensions would be installed à la carte.   At that time new features might be considered. This plan may or may not still be planned, but in general, new features are on hold.

@facelessuser summed things up well. The WikiLinks extension is not intended to match the behavior of any spec from any wiki system. It is only expected to match its own documentation. If I were inclined to make any changes to the extension it would be to remove it entirely. As there are no reported bugs (differences between the documented behavior and actual behavior), I'm closing this as wontfix.


RAM-efficient shuffling in dataset

System information

TensorFlow version (you are using): 1.12.0
Are you willing to contribute it (Yes/No): Maybe, if I get some direction

Describe the feature and the current behavior/state.
Currently to shuffle datasets, shuffle() needs to read shuffle_buffer worth of records into memory. If the records are ~large and the dataset contains ordered/consequitve/correlated records then the user may need to pre-shuffle and/or split the data and/or commmit a good chunk of ram for shuffling the records sufficiently to avoid overfitting to features present in the particular part of the dataset.
It would be possible to trade off reading the dataset just once in order to shuffle more efficiently in terms of memory usage. For example, the ram-efficient dataset shuffler could read the dataset multiple times starting from offsets 0 .. N and skip over N records on each pass.
Will this change the current api? How?
It would add a new method to tf.data.Dataset, or maybe an option/experiment for shuffle().
Who will benefit with this feature?
Anyne training on sequential (I guess correleated) datasets where individual records are on large enough to become a limiting factor for large shuffle_buffer sizes.

IIUC, your proposal relies on the existence of an efficient implementation of skip / seek for the dataset to be shuffled. Unfortunately, not all dataset types meet this requirement. For instance, TFRecordDataset -- commonly used for storing data at rest -- does not support efficient skip/ seek and to seek to an offset, you need to sequentially read all the data up to that offset.
The good news is that you could achieve RAM-efficient shuffling using existing tf.data API:
# `dataset` stores the dataset to shuffle
dataset = dataset.window(N).flat_map(lambda x: x.shuffle(M))

This will partition the dataset into windows of size N and shuffle each of them using buffer of size M.


Ref doesn't work on functional components.

Version
2.5.2
Reproduction link
https://jsfiddle.net/d2pj7wuo/
Steps to reproduce
Open the JSFiddle link, then check the console.
What is expected?
The child functional component can be attached by this.$refs , or give a warning in development environment when attribute ref is set on a functional component.
What is actually happening?
this.$refs of parent componet is an empty object.

There's a similar issues for React stateless components. A functional component will not actually generate a VueComponent instance, instead of attaching the dom element directly, a warn or an error thrown may be a better choice.

我只是克隆你的vue, git在我的本地电脑，然后发出一个错误。I did'n remember The details about the error

win10+ github client+right mouse key+git clone=I get vue but show an error,and nothing changed about vue source

am I clearly say

god i just smal lsource  code

@sqal how about using a functional component without a render function? That's also not working for me.


Allow to configure Maximum Transmission Units

This is especially important in case of UDP, where each packet needs to fit into a single IP datagram (there is no control flow mechanism to ensure that packets are "whole").

Codecov Report

Merging #4 into master will increase coverage by 1.18%.
The diff coverage is 88.46%.

@@            Coverage Diff             @@
##           master       #4      +/-   ##
==========================================
+ Coverage   89.58%   90.76%   +1.18%
==========================================
  Files           4        5       +1
  Lines          48       65      +17
==========================================
+ Hits           43       59      +16
- Misses          5        6       +1

Flag
Coverage Δ

#1_8_otp19
90.76% <88.46%> (+1.18%)
:arrow_up:

#1_8_otp21
90.76% <88.46%> (+1.18%)
:arrow_up:

Impacted Files
Coverage Δ

lib/telemetry_metrics_statsd/formatter.ex
100% <100%> (ø)
:arrow_up:

lib/telemetry_metrics_statsd.ex
87.5% <75%> (+0.83%)
:arrow_up:

lib/telemetry_metrics_statsd/event_handler.ex
91.66% <85.71%> (+0.36%)
:arrow_up:

lib/telemetry_metrics_statsd/packet.ex
92.85% <92.85%> (ø)

Continue to review full report at Codecov.

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


Tooltip Attempt

My proposal for simple authorable tooltips. No tests. I think @Blainegunn will write them.
https://tooltip--milo--adobecom.hlx.page/drafts/cmillar/tooltip?martech=off

@narcis-radu I think you're 100% right and I think we need to write a lot more JS to be much better about detecting screen edges and when the tooltip will be outside those bounds. I'm going to let people smarter than me tackle that. My only contribution here is where I think the code should live and what the AX is like.

@Blainegunn at the very least I think we fix the z-index issue @narcis-radu raised.


Token list takes a noticeable few seconds to load

Originally reported by @bcmdarroch
Overview
Token list takes a noticeable few seconds to load. Noticed this after we merged the token details pages.

this as been resolved by moving to a table angular component
will continue to get faster when we replace the control menus as well


Algogia's DocSearch not very precise

Hey,
I tried to search through the docs and I saw this:

In the main Styles menu, Algolia doesn't show correctly nested pages as Border Colors, Background Colors etc...
Any fix @LukyVj? :)

Hey @HapLifeMan ! Thanks for opening the issue!
It's something that can be fixed! I let my colleague @maxiloc ( aka docsearch specialist :) ) respond to you with a solution!
Let me know if I can do anything else!

Hey, I updated the config. I did a mistake when I first configured it. Should be fixed and live now.
Feel free to ping me if you see other relevance issue.

Thank you everything is good now :D

@maxiloc Huge thanks for your help here! 🙇


Candle factory fix

Coverage increased (+0.2%) to 99.247% when pulling ca46327ea2bec54bd582f36f8285b83308b218e6 on candle-factory-fix into 419ce674119c88f4c279d23fd95ebf13a6175f37 on master.


move development dependencies to devDependencies

closes https://github.com/mayashavin/cloudinary-api/issues/43

duust in the wind

Sorry @chrillep my GitHub notifications are a mess, I don't receive any notification for this at all :(

Sorry @chrillep my GitHub notifications are a mess, I don't receive any notification for this at all :(

I know its far from easy to manage


Run Task... fuzzy match quick pick performance degrades with a large number of tasks

Issue Type: Bug
I am working on a large code base that uses a script to auto-generate many build and test targets.  I am creating an extension that will create new tasks from this large target list.  The extension is based on the task-provider-sample in the vscode-extension-samples.
The generated task list is well over 5000 entries and the performance of the fuzzy matcher in the Run Task...quick pick is too slow -- the system freezes for several seconds after the first key press.
The Go to File... fuzzy match quick pick does not seem to have this problem.
My current work around is to filter the original target list but I would prefer not to.  Can this be fixed?


Modified hompage and additional new changes🥳

added favicon and also a background simple interface.
Rethough of no complexity to be in place>>>
Just simple for integration with the API for login and registration. functionality

Also @Mu-Gee check on the static/css/styles.css its not present:
Tried creating it in root dir but not working,,
Same in root app not working.
💯 check on it ,,

THis one is able to be merged: Thus merging it 👍🏿

Also @Mu-Gee check on the static/css/styles.css its not present: Tried creating it in root dir but not working,, Same in root app not working. 💯 check on it ,,

Remember I told you I went on sabattical for a week or two, will be unavailable till weekend.

No problem
On Sun, 27 Aug 2023, 16:47 MuGee, @.***> wrote:

Also @Mu-Gee https://github.com/Mu-Gee check on the
static/css/styles.css its not present: Tried creating it in root dir but
not working,, Same in root app not working. 💯 check on it ,,
Remember I told you I went on sabattical for a week or two, will be
unavailable till weekend.
—
Reply to this email directly, view it on GitHub
https://github.com/Ndegwadavid/CareConnect/pull/10#issuecomment-1694673449,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZXSXPPLOE5SE3SJVIJBCT3XXNFYFANCNFSM6AAAAAA4AKEOZI
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


[Refactor] Convert jsx to typescript (tsx)

Typescript provide better support when developing especially type checking and IDE integration. This PR contain rewrite and some fixes of jsx into tsx file.
New features:

Add webpack/ts alias for consistent local module resolution

Changes:

Fix warning from tailwindcss build

Codecov Report

Merging #65 into master will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##              master       #65   +/-   ##
===========================================
  Coverage     100.00%   100.00%
  Complexity        38        38
===========================================
  Files             10        10
  Lines            143       143
===========================================
  Hits             143       143

Continue to review full report at Codecov.

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


Add github issue and pull request template

This is part of the work to adopt github issue for issue management. Will use similar template as bookkeeper.

PR https://github.com/apache/distributedlog/pull/147 is for this


Loose typings for find with arrays of mismatching props

Describe the bug
Mikro-ORM uses the IN predicate whenever your filter is an array of props:
em.fork().find(Chat, [{ owner: 1, recipient: 3 }, { owner: 1, recipient: 4 }])

translates to
select "c0".* from "chat" as "c0" where ("c0"."owner_id", "c0"."recipient_id") in ((1, 3), (1, 4))

So far so good, but what about arrays of mismatching props?
em.fork().find(Chat, [{ owner: 1, recipient: 3 }, { owner: 2 }])

It should either forbid it via typings or treat it like an $or:
em.fork().find(Chat, { $or: [{ owner: 1, recipient: 3 }, { owner: 2 }] })

which translates to
select "c0".* from "chat" as "c0" where (("c0"."owner_id" = 1 and "c0"."recipient_id" = 3) or "c0"."owner_id" = 2)

Instead typings allow that and it translates to the following query
select "c0".* from "chat" as "c0" where ("c0"."owner_id", "c0"."recipient_id") in ((1, 3, '{"c0.owner":2}'))

which obviously errors out (unequal number of entries in row expressions).
To Reproduce
Steps to reproduce the behavior:

em.fork().find(Chat, [{ owner: 1, recipient: 3 }, { owner: 2 }])

Expected behavior
This should either error out via stricter typings or treat it like an $or.
Versions

Dependency
Version

node
v18.15.0

typescript
5.0.3

mikro-orm
5.6.16

your-driver
postgresql

Using the same props but with a mix of IDs and array of IDs leads to a similar problem:
em.fork().find(Chat, [{ owner: 1, recipient: 3 }, { owner: 1, recipient: [4, 5] }])

translates to
select "c0".* from "chat" as "c0" where ("c0"."owner_id", "c0"."recipient_id") in ((1, 3), (1, 4, 5))

which errors out (unequal number of entries in row expressions)

Would be good to test this on v6, I wont be doing any refactoring of types in v5, but I guess this works the same in there.
I would also appreciate complete repro, e.g. I have no idea what your entities look like.

I will likely have many more because I'm rewriting my dataloader to accomodate for the whole of the filter syntax and I'm encountering lots of edge cases, like https://github.com/mikro-orm/mikro-orm/issues/4222

I have no idea what your entities look like
Chat has a composite key on owner+recipient.

I would also appreciate complete repro
I will eventually do so, not sure if I will manage to do now because I'm tight on time and I won't be able to work on this for the whole of the next week.

Chat has a composite key on owner+recipient.

I want to see code, not words, I am sure you understand that :)
Also keep in mind the typings are best effort, it will never work exactly the same.

Here is the repro: https://github.com/darkbasic/mikro-orm-repro-4220


Anmol Kapoor - Implementing the RedditController

Justification
This PR closes #9.
Implementation
I modeled my implementation to the example controllers in other tests in the repository.
Testing
To test this change, you can run the following commands:
git checkout ak-redditController
mvn test | grep RedditControllerTest

Acceptance criteria

[X] The reddit  controller is fully implemented according to the instructions in https://ucsb-cs156.github.io/f22/lab/team01/
[X] Appropriate tests are in place for the reddit controller

Should this PR's changes be a part of the ak-reddit branch (#18) instead of this new one?

Should this PR's changes be a part of the ak-reddit branch (#18) instead of this new one?

No, this works fine I think and it's probably better practice, I think either way it's fine.


Add support for GCP compute instances

This lays the groundwork for general GCP support for cloud-nuke with
support for deleting compute instances.
Add the gcp package and CLI argument to nuke GCP resources.

#42
Hi,
I am not an expert in Go or GCP so please let me know if I'm doing anything weird.
I tried to follow the conventions in the AWS example as much as possible, but the GCP libraries are different which made some simplifications in the data structures possible but required some extra state here and there.
Feedback on the approach would be appreciated.

I've implemented the feedback and ready for the next round of review.

This code looks great to me, thanks @acrisci.
@josh-padnick Could you review the GCP specifics? If it looks good, feel free to merge. Note that you'll need to configure the CircleCI build to work with GCP.

Ok I took a fresh look at it and it turns out what actually needed to be done was to lock golang.org/x/sys at a specific version required by grpc. I'm not sure how I got it to work the other way.
Anyway I think this works now.

Hi @acrisci, many thanks for this contribution. I just made a fix to the tests so please merge in the latest master and fix conflicts so that we can get this PR shipped. Thanks you!!!

Yeah all that's needed is to fix the build errors. I got pulled onto another project but I should be back on this soon.

has this PR fallen behind?

@innovia The way things turned out for me, I don't really have a use for this. I feel bad about not finishing it, but being merged with a maintainer with no use case might be worse. And plus the build errors were kind of annoying.
I think the approach I used here is good and I hope someone else who may need this takes it on and benefits from the work I've done here.


deps: updates wazero to v1.7.0

This will update wazero to v1.7.0. The v1.7.0. release marks a milestone in the wazero project, replacing our old compiler architecture with a new optimizing compiler backend.. It also introduces experimental support to the thread spec.
We will officially announce the final v1.7.0 release in just a few days, during Wasm I/O, after which we will undraft this PR and update it to the latest tag.
Let me know if you'd rather merge this PR before the official release. This draft PR is intended to let your CI checks run and verify everything is in order before our final release.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I'm not in a hurry. We can merge this PR after the announcement.

the pr has been updated to v1.7.0 final

Thanks!


how to next/prev buttons.

I need to display prev button on top of list (max of 3 items show) and next button under lists.
I see some code push on it, but nothing in docs:

https://listjs.com/docs/pagination

Ideally I have a function next()/prev() that I call in click. Help?

I found top/bottom nav css. will try

I found top/bottom nav css. will try

Can you share some links please?


Poor image zooming

When you open any image and zoom in, it becomes blurry instantly no matter what quality an image had initially. It's quite noticeable on the long images (there is not enough zoom scale even available).

Examples
pxview (second img)

original

pxview

original

In my assumption (not really familiar with React Native), it's because of shrinking image dimensions to the phone ones.
https://github.com/alphasp/pxview/blob/060291f5eff513035db68776c27e05a36210c7f4/src/components/PXPhotoView.js#L6-L11

Example: https://www.pixiv.net/artworks/81086615
pxview

downloaded image in a separate gallery app

Thanks for your bug report. I never notice it untill you open this issue... 😅


Don't commit final output files to  device-compose-files/*.yml

When reviewing https://github.com/NebraLtd/helium-miner-software/pull/341, I noticed that we are committing the output files from the generator to device-compose-files/*.yml. This doesn't make any sense to me. We should simply generate these files on the fly and then throw them away. I don't see any need to commit them.

This was done intentionally for audit purposes

See discussion on #272 for discussion

Oops pushed the wrong button there.
General gist was that it's useful to have these user-readable in the repo and there's no real reason not to...

We already spit them out to the stdout on the Actions flow so we have a paper trail of them already.

Yeah but that's not publicly available

closing this as doesn't seem to cause any harm


Uncaught Exception: The Internet connection appears to be offline.: (null)

An uncaught exception was reported.
Info:
OS: darwin
Arch: x64
GPMDP Version: 3.0.0
Time: Thu Mar 10 2016 09:21:46 GMT-0800 (PST)
Error:
The Internet connection appears to be offline.: (null)
Error: The Internet connection appears to be offline.: (null)
    at Error (native)

This issue was created automatically inside the uncaughtException handler

Client side network issues.
Will not be reported in 3.1.0


Lutron Caseta firmware updte ?

I think Lutron update his firmware...
The HA component stop working : https://github.com/home-assistant/home-assistant/issues/15421
Why get_lutron_certificate.py, if i dump the json result of the test request, i got that :
{'Header': {'StatusCode': '204 NoContent', 'Url': '/device/status/deviceheard'}, 'CommuniqueType': 'SubscribeResponse'}

I can try rebooting mine this weekend and see if I can get it working again.

"SubscribeResponse" sounds familiar. Are you running the get_lutron_certificate from this repo or the one in the Home Assistant docs? I originally put it in the Home Assistant documentation, but then copied it over to this repository when I needed to update it for the last firmware update, but somebody else did the update for Home Assistant that time and the documentation didn't get updated to use the new script. I was going to do that when adding component registry support, but I wanted to also close out #22 for sure.
My bridge disconnected at 6:30 today, and due to #19 I had to restart Home Assistant but my lights are still working for now. I'll still try rebooting this weekend to see if there's a new update that breaks it.

quick fix :
in  [ /srv/hass/lib/python3.6/site-packages/pylutron_caseta/smartbridge.py  ]  line 50 :
ssl_context.verify_mode = ssl.CERT_OPTIONAL
instead of
ssl_context.verify_mode = ssl.CERT_REQUIRED

I know that "it works for me" isn't terribly useful, but I thought I'd add a data point.
I brought up a new instance of HASS.IO/HASSOS (on RPi) for testing on Wednesday (7/11). After reading about this issue yesterday, I copied my Lutron certs from my production machine to the new HASS.IO setup and rebooted. The Lutron component configured correctly.  Note that I generated the certs on May 3, 2018 using the script in gurumitts repository.
Of course now I'm afraid to reboot my production machine .

When rerunning the script, make sure you remove any keys from last time. It tries to skip steps which isn't what you want if your certificates have changed.

im having the same issue, and i just used the updated script to generate new certs, but still get the same error message

When rerunning the script, make sure you remove any keys from last time. It tries to skip steps which isn't what you want if your certificates have changed.

Just tried it again after deleting all the cert and key files to double check, still have the same problem. :/

@jumblies where is the file located that you modified on hass.io installation?

@kalex1114 , I'm sure there's a better way, but this worked for me to find the file:
sudo find / -name smartbridge.py
In my case:
/var/lib/docker/overlay2/33803716ead58faca8ab56c49f6f362ec5059a86aef9cc8d81f8c150e40d23d8/diff/usr/lib/python3.6/site-packages/pylutron_caseta/smartbridge.py
/var/lib/docker/overlay2/e72b09633dfb75d1f9673de9b44a0bed9fd446e1f5aee22884dccdc4e2acfa70/merged/usr/lib/python3.6/site-packages/pylutron_caseta/smartbridge.py

They are linked, so editing one was sufficient.
Hope that helps.

Can you try adding server_hostname='' to smartbridge.py like I did in 618deda instead of ssl_context.verify_mode = ssl.CERT_NONE? That fixes it for me.
Interestingly, I could only reproduce this issue on my desktop. My Home Assistant server is running an older version of the Home Assistant docker container and doesn't seem to be affected. It looks like a problem only if you're using a newer version of Python.
I wouldn't blame the engineers at Lutron. It would be nice if they had official APIs or libraries or even just a channel for communicating this kind of information, but these things would cost the company money and the number of people buying these switches to use in this way isn't going to be very compelling to the business. It looks like they're trying to implement a new feature and our unofficial client happened to break.
If you wanted to and your router supports it, it looks like you could completely remove your bridge's internet connection to stop firmware updates coming from outside and still control the bridge locally. I don't know if the phone app would ever try to push firmware updates over the local network.

@kalex1114
I'm sorry I can't help with that one.  Tried Hassio and really didn't like it so I run mine on metal on an Orange Pi Zero.
@mdonoughe
I'll try that and report back.
Sorry about the rant, I just get tired of it changing so frequently.  I really like the hardware and I was too hard on them.  It's good kit.    I'm also spoiled by Tasmota and MQTT which by comparison is VERY easy to troubleshoot.  When lutron fails, all I can do is sigh and stare a little white square that is a mystery to me.

@mdonoughe
this fixed it for me. Thanks!

For what it's worth, in my case, things seem to have fixed themselves once I updated to 0.73.2.

0.73.2 didn't fix it for me, had to do the workaround (ssl.CERT_NONE)

Interesting; I'm on 0.89.2 and had to apply the @mdonoughe server_hostname fix

Had the same issue after upgrading from 0.63.1 to 0.90.1, and the server_hostname='' change fixed this for me!


Add serialization context

(De)serialization should generate context, that can be reused for faster operation with smaller memory footprint. This PR introduces breaking changes - less output bytes for value types.