Update relation only if exists

Bug description
When updating users score, I would like to update (increment) the score of the team in the same query.
Instead Prisma throws an Error:
An operation failed because it depends on one or more records that were required but not found.
No 'Team' record was found for a nested update on relation 'Team'.

(It is not required, its optional, see model)
How to reproduce

Create an user with teamId null
Try to update the team relation through the user

Expected behavior
I would expect that prisma handles automatically missing entities, just by ignoring them, like a database would do.
Prisma information
Model
model User {
  id BigInt @id
  score Int @default(0)
  teamId BigInt?
  team Team? @relation("Team", fields: [teamId], references: [id])
}

model Team {
  id BigInt @id
  users User[] @relation("Team")
  score BigInt @default(0)
}

This is the query:
const userUpdate: Prisma.UserUpdateArgs = {
  where: { id: BigInt(userId) },
  data: <Prisma.UserUpdateInput>{
    score: { increment: score },
    team: {
      update: {
        data: {
          score: { increment: score }
        }
      }
    }
  },
  include: {
    team: {
      select: {
        score: true
      }
    }
  }
}

Environment & setup
next.js
Prisma Version
5.11

That is currently how update is supposed to work, to allow the behavior you expect we would need to introduce a new nested operation, potentially called updateIfExists or similar.

That is currently how update is supposed to work, to allow the behavior you expect we would need to introduce a new nested operation, potentially called updateIfExists or similar.

Ok, you don't think that the update operation would be obsolete, if there were updateIfExists? The point is, that its expected behaviour for an optional relation.

@Weakky its a bug, the relation is optional, so its wrong to expect it to exists from the model perspective.

That the relation is optional should be irrelevant here.

Why should it be irrelevant here? Thats exactly the point. You cannot treat normal update and update of a relation the same way.

Ok, you don't think that the update operation would be obsolete, if there were updateIfExists?

From this call:
prisma.user.update({
  team: {
    update: { data: { score }}
  }
})

we, as an ORM can only infer that you want to update user's team score. Even though schema allows relation to be optional, this call by itself does not say us anything on what to do when the record does not exist. In your case ignoring the update is right thing to do. Some other developer on the different project in the different company did this update by mistake and silently ignoring it will hide the error. We should not make a decision to silently ignore potential errors for all of our users and rather allow users to make decision for themselves and we should lean on the safe side as a default. By safe, i don't mean a lack of any errors but rather not doing anything we are not 100% sure we were asked to do.
For you update might be obsolete after updateIfExists will become a thing. For somebody else, existing update behavior might safe hours of debugging.

Ok, you don't think that the update operation would be obsolete, if there were updateIfExists?

From this call:
prisma.user.update({
  team: {
    update: { data: { score }}
  }
})

we, as an ORM can only infer that you want to update user's team score. Even though schema allows relation to be optional, this call by itself does not say us anything on what to do when the record does not exist. In your case ignoring the update is right thing to do. Some other developer on the different project in the different company did this update by mistake and silently ignoring it will hide the error. We should not make a decision to silently ignore potential errors for all of our users and rather allow users to make decision for themselves and we should lean on the safe side as a default. By safe, i don't mean a lack of any errors but rather not doing anything we are not 100% sure we were asked to do. For you update might be obsolete after updateIfExists will become a thing. For somebody else, existing update behavior might safe hours of debugging.

@SevInf Hmm. I would say in some cases probably the user expected a team to be assigned through the relatationship like teamId or anything else it it wasn't there, but this, as a check, would be actually on a totally wrong place from software design perspective. If a relationship is optional then this should be considered as updateMany, where the "related" rows are undefined, unlike an explicit update with a proper identifier.

If a relationship is optional then this should be considered as updateMany, where the "related" rows are undefined, unlike an explicit update with a proper identifier.

Take typescript as an example: user.team.score = 10 is an error if team does not exist.

Thats a good example with Typescript, as it would't allow you to do this in the first place without proper checking before this statement. And if you all agree, that user.update.update.team is an explicit update statement, prisma should actually warn the user, cause team is optional. If prisma is not warning, then it should handle it as an optional update imho.

However, if you want to call it updateIfExists I am fine. You can point me even to the right place to dig into it, I would be happy to provide a PR, I just don't want it go down the priority list by changing the label from bug to feature


Current config for otel-collector results in duplicate label names

This commit https://github.com/SigNoz/charts/commit/e6e32e5c0538c2e771e3e6a9e415c767bafcc400 introduced a change where the scraping the collector metrics is moved from otel-collector-metrics to otel-collector. The collector already adds service_instance_id and service_name to its data point attributes. And Prometheus receiver adds job name as service.name and instance as service.instance.id. When they are finally sanitised, they produce duplicates. While the duplicates are handled by overriding, the different order of values results in different end series. This wasn't an issue earlier because the otel-collector-metrics doesn't have the resource_to_telemetry conversion enabled to true.

@prashant-shahi

cc // @ankitnayan

HotFix for the issue is merged already to the chart.
Ideal fix should be done in conversion_to_telemetry section of clickhousemetricswrite component.


TVM update cycle

It would be great if the documentation could include some information about the update cycle , i.e. how often does TVM assess the information on the local system and process it in the MDATP backend.
Example: When a machine has an older version of Software XYZ that has vulnerabilities, the software is then patched, how long does it take to see this change in the TVM console?

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

ID: 45e827de-5cf9-4506-880f-908d454f5807
Version Independent ID: a9da7cb9-222f-084a-7a1a-36730cf0e669
Content: Weaknesses
Content Source: windows/security/threat-protection/microsoft-defender-atp/tvm-weaknesses.md
Product: w10
Technology: windows
GitHub Login: @DulceMontemayor
Microsoft Alias: dolmont

@officedocsbot assign @jvsam

Hi @alexverboon, thank you for your feedback. As you know, we always strive to give users the best Windows 10 experience by ensuring that contents of the Microsoft Docs are useful, accurate and up-to-date.

...how often does TVM assess the information on the local system and process it in the MDATP backend.

As per the available information, Threat & Vulnerability Management (TVM) "uses the same agentless built-in Microsoft Defender ATP sensors..", hence, devices onboarded to Microsoft Defender ATP automatically report and push vulnerability and security configuration data to the Threat & Vulnerability Management dashboard.
Furthermore, it's emphasized here—and in the Weaknesses doc—that "In the field of discovery, we are leveraging the same set of signals in Microsoft Defender ATP's endpoint detection and response that's responsible for detection, for vulnerability assessment. Since it is real-time, in a matter of minutes, you will see vulnerability information as they get discovered. The engine automatically grabs information from multiple security feeds. In fact, you'll will see if a particular application is connected to a live campaign. It also provides a link to a Threat Analytics report soon as it's available."

When a machine has an older version of Software XYZ that has vulnerabilities, the software is then patched, how long does it take to see this change in the TVM console?

Actually, the Scenarios doc explains it well. It depends on your IT Administrator. When the remediation task is submitted and then accepted, you can view the status of the remediation request on the Remediation tab. Once completed (in your example, a patch has been deployed), the IT Administrator will select Complete Task and this action updates the security task status in both Intune and ATP. Here's a workflow for more information.
Basically, the information is already on this doc set. Is there a specific messaging that you would like to add, Alex?

Hello again @alexverboon, just following up if you have other suggestions related to this doc? So far, the information you seek is already available and if you're okay with the content, we can consider this issue resolved. Thanks.

Hello again @alexverboon, we haven't heard from you but we hope the information we've provided helped. We will now close this issue, however, feel free to re-open if you have suggestions related to this documentation or ideas to make it better for users. Thank you.

@officedocsbot close

Hello again @alexverboon, we haven't heard from you but we hope the information we've provided helped. We will now close this issue, however, feel free to re-open if you have suggestions related to this documentation or ideas to make it better for users. Thank you.

Hello sorry I forgot to follow up on this; my question isn’t really answered; let me rephrase.
I have software ABC version 1.0 installed
TVM finds a vulnerability
I update the software
When will I see the updated status in TVM? That I have now version 1.1 installed as it does seem to take awhile.


XML indent double size for non-tag

Describe the bug
In 63b74a8 a change was introduced in vim/runtime/indent/xml.vim for which if you add text as tag content on a new line the indent applied is twice shiftwidth().
To Reproduce
Detailed steps to reproduce the behavior:

Edit filename.xml
set sw=2
set et
set ts=2
insert ''
insert a newline
Observe: indent for the line is 4, it must be 2
insert a "<"
9: Observe: indent for the line is 4, correct
Describe the error

Expected behavior
Add one single shiftwidth on newline, independently from the tag.
Environment (please complete the following information):

Vim version VIM - Vi IMproved 8.1 (2018 May 18, compiled Jul  8 2019 19:26:28) via Homebrew
OS: Mac OS 10.13.6
Terminal: iTerm2

Additional context
The expected behavior appears before 63b74a8, so it's introduced here:
https://github.com/vim/vim/commit/63b74a8362b14576b21d342dc424d0396ca8ea27#diff-6cbcaa8336a0ca9e5e4bf3f0276ee25d, probably in XmlIndentSum.
I was unable to get the commit log message for that specific change, so I'm unable to tell if this is intentional (and I'd like to see the rationale of it) or a bug.
Workaround for me is to get the code ad the previous version:
https://github.com/vim/vim/blob/314dd79cac2adc10304212d1980d23ecf6782cfc/runtime/indent/xml.vim

Please report problems at my upstream repository (https://github.com/chrisbra/vim-xml-ftplugin) not here and make sure you test the latest version there first. Thanks.

In the last source code this is resolved, thanks.
Did you already sent a PR to have the latest version included in VIM?

Not yet, was trying to get some feedback first, before sending an update to Bram for distribution with Vim

Am 14.07.2019 um 18:26 schrieb Paolo Mossino<EMAIL_ADDRESS>In the last source code this is resolved, thanks.
Did you already sent a PR to have the latest version included in VIM?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


Error when building .cu files from build.rs through cc-rs

I just tried to build my project with zigbuild and got this error:
  running: "nvcc" "-ccbin=/home/user/.cache/cargo-zigbuild/0.14.3/zigcxx-x86_64-unknown-linux-musl.sh" "-Xcompiler" "-O3" "-Xcompiler" "-ffunction-sections" "-Xcompiler" "-fdata-sections" "-Xcompiler" "-fPIC" "-m64" "-I" "./src/kernels" "-Xcompiler" "-Wall" "-Xcompiler" "-Wextra" "-O2" "-gencode" "arch=compute_86,code=sm_86" "-o" "/home/user/dev/project/target/x86_64-unknown-linux-musl/release/build/project-6c65464849db21e5/out/src/kernels/cuda_kernel.o" "-c" "src/kernels/cuda_kernel.cu"
  cargo:warning=zig: warning: '-x c++' after last input file has no effect [-Wunused-command-line-argument]
  cargo:warning=zig: warning: CUDA version is newer than the latest supported version 11.5 [-Wunknown-cuda-version]
  cargo:warning=zig: error: cannot specify -o when generating multiple output files
  exit status: 1

  --- stderr

  error occurred: Command "nvcc" "-ccbin=/home/user/.cache/cargo-zigbuild/0.14.3/zigcxx-x86_64-unknown-linux-musl.sh" "-Xcompiler" "-O3" "-Xcompiler" "-ffunction-sections" "-Xcompiler" "-fdata-sections" "-Xcompiler" "-fPIC" "-m64" "-I" "./src/kernels" "-Xcompiler" "-Wall" "-Xcompiler" "-Wextra" "-O2" "-gencode" "arch=compute_86,code=sm_86" "-o" "/home/user/rustdev/project/target/x86_64-unknown-linux-musl/release/build/project-6c65464849db21e5/out/src/kernels/cuda_kernel.o" "-c" "src/kernels/cuda_kernel.cu" with args "nvcc" did not execute successfully (status code exit status: 1).

Am I doing something wrong?

Sorry, never used CUDA before, can't offer much help. Feel free to send PR if you find a way to fix it.


feat: enable peer discovery modules by default

This PR will enable any provided peer discovery modules by default if no configuration for the module is supplied/needed.
As before, modules can be explicitly disabled or enabled by passing config.
This enables pre-configured modules (instances) to be passed and enabled without them having to have a tag and an unused config section.

@jacobheun I don't think that peer discovery module validation code is working properly 😟 . I just found problems with the test for it and fixed them and it fails now:
https://github.com/libp2p/js-libp2p/pull/209/commits/f753d61c59661ef339f96c750bca7724a6749d64
I'm not changing any defaults, just allowing modules that don't require any config or have already been configured to still be registered and started. IMHO it's unnecessary to require a developer to pass a preconfigured module instance and also have to set a config value with { enabled: true } somewhere else in the options. I think it is a reasonable expectation that if I pass a module and say nothing about whether it is enabled or disabled then I want it to be enabled.
I don't think we should validate config for each of the discovery modules - that's outside of the scope of this module. We can't know what all the config options are and keep that info up to date. All we could meaningfully do would be to validate a boolean enabled property, which I think should just be optional anyway - hence this PR.

@jacobheun how about now? Is better 😛 ?


Serial ID of mosiac go heading not constant

Hey,
I have a MOSIAC GO heading evaluation kit. When searching for the device using "serial/by-id", I have two names for one device. Only when the connection is established using one of the ids, I am able to receive ROS messages. When using the other id, connection is established but there are no messages.
Moreover,  the id through which the messages are received is not constant and changes between the two upon restart.
How do I fix it and why is it happening?
Thank you!

Hi,
I am sorry to hear that since I am not really sure what is going on. I always use the RNDIS connection, so I am not so familiar with the serial connections. There are indeed two serial devices by design - USB1 and USB2, see manual. On my system assignments to the two /dev/serial/by-id are always constant.
Regarding message reception, I have tried both and have the same experience as you: only on USB2 message reception is possible. But this is also constant.
Maybe you could also contact Septentrio's support for assistance since this seems not to be related to the ROS driver.

With USB1 the streams do show up in the web UI correctly. Strangely enough, after reactivating them manually in the web UI, setup via the driver worked afterwards on both connections.

ok, thank you!


feat: Code blocks with copy button, mdx demo pages, renderToString

Code blocks with copy code button and styled titles
Code block copy code buttons can be disabled with noCopy as a meta string after the code block backticks
Convert some demo pages to mdx for simplicity
Fixes next14 having deprecated usage of react-dom/server imports in the useText hook
Consistent buttons on various pages
Flesh out page structure a bit more on get-started and text

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


Added newFileResponse Support for buffers in memory

newFileResponse only supports loading objects from storage or saved, with this additional function call you can now pass files that are loaded in memory like images which are being processed for example.

I have tried to do the ./format.sh script and installed clang-format, however the script errors out on me, or maybe I am miss understanding the output @an-tao. I created this new PR to avoid all the old changes and hiccups of rebasing, please kindly re-review.
I have also given the maintainers access to edit so they can assist with getting this feature in, thank you!

PR changes made, please re-review when you get the chance, thanks!


Default app_path in setting is not same after built model

Laravel 5.4 with propelLaravel last version
before built :
in configuration the default path is 'phpDir' => app_path('Models'),
but after i built the model it generate file and write namespace like this-> namespace App\Modules;
it's bug that i found.
pls solved this issue or tell me how to fixed
Thank you.

@gtokung , write down path for newely generated model related to root of your application, please. Models obviously uses namespaces so I don't understand what's your concern. Provide actual and expected state and I will can help you.

OK. the problem is when i set config phpDir in config/propel.php  like this  ('phpDir' => app_path('Models'))
and then i build with command => php artisan propel:model:build
it's generate new folder "Models" but the file inside this folder like Users.php it's use namespace like => "namespace App\Modules;"
it should be "namespace App\Models;", Right?
Thank you.

@gtokung , actually namespace should be specified in schema.xml: http://propelorm.org/documentation/reference/schema.html#database-element If you are running initial installation, then init command will try to detect your basic namespace from composer.json file.

Thank You.


Kotlin 1.9.10 -> 1.9.24

Summary
This bumps Kotlin from 1.9.10 to 1.9.24 making it easier to bump to 2.0.0
How It Was Tested
See app running in screeshot below:
Screenshot/Gif

App running with Kotlin 1.9.24

Please, resolve the conflicts @cortinico

@alisen this should now be ready to go 👍

@alisen this should now be ready to go 👍

All checks are failing. Could you try to fix it?

@alisen this should now be ready to go 👍

All checks are failing. Could you try to fix it?

Yup my bad


deprecation warning in php 8.1.2

PHP Deprecated:  preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in /path/to/vendor/apereo/phpcas/source/CAS/Client.php on line 1041
Maybe change null to the empty string on line 1040?
$ticket = (isset($_GET['ticket']) ? $_GET['ticket'] : '');

This issue may have been solved with a recent pull
https://github.com/apereo/phpCAS/pull/415
Can you please check against the current master branch?

Yes, I was looking at the v1.4.0 release and didn't think to look at master. Sorry about that. Looks great, tnx.


chore: update release workflow and install scripts for foundry-zksync usage

Motivation

Updates release workflow to follow upstream pipeline for improved parity. Only includes forge and cast binaries.
Reduces binary size
Also required for install and foundryup scripts to reflect foundry-zksync dev branch
Scripts will be used to setup curl installation step for easy download of foundry-zksync and updated in a subsequent PR

There's a lot of platofrm-specific scripts that I'm assuming are either copied-from or tested. Everthing else lgtm

Copied from upstream, leaving as is for parity.


Use lib_elixir instead of vendoring elixir modules manually

Some notes:

We need to exclude exception modules from lib_elixir
We need to wait until lib_elixir uses httpc or other http module that doesn't require elixir >= 1.13

@doorgan I've replaced Req with httpc on main; if you could give that a shot when you have a moment, I'd appreciate it! (You may have to rm -r _build as well.)

@zachallaun is there a change we can replace the usage of Keyword.validate! here by some manual validation? https://github.com/zachallaun/lib_elixir/blob/dda978a0ac1dc48d075aaec97c3639fc16ab5f13/lib/mix/tasks/compile.lib_elixir.ex#L71-L72
I think it's the only missing bit right now to keep supporting elixir 1.12 in Sourceror, otherwise it seems to be working great!

@doorgan Done! Also introduced some... hackery... to handle a change in the debug_info beam chunk that happened in Elixir 1.15. This is necessary to compile a lib_elixir >= 1.15 on a runtime < 1.15.
I'm sure there are more bugs, but there's one limitation that I haven't figured out a fix for yet, which is that lib_elixir requires OTP 23+.

This is proving a good resource for ironing out kinks! I'll pull this PR later and try to work through the remaining errors.
Re: Mix.Tasks.Format failing, right now namespacing doesn't include the mix app at all, but I think it could!


dummy commit

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.31%. Comparing base (37dc77d) to head (62a6787).

Additional details and impacted files
@@           Coverage Diff           @@
##            stage     #168   +/-   ##
=======================================
  Coverage   81.31%   81.31%
=======================================
  Files          12       12
  Lines        3510     3510
=======================================
  Hits         2854     2854
  Misses        656      656

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


Port the benchmarks to criterion

This makes them run on stable and also shows throughput of the CRC calculating functions, which is a more useful measure than time.

thanks @jonas-schievink


Incorrect/incomplete training loss formula in Paper section 3.3 equation 2?

Hi, there is a problem with equation (2) in section 3.3 of your paper? I read the paper and it says that you use training pairs for variation of the same object between frames. However, your equation 2 show a normal reconstruction loss for one frame. How do you use the paired training data?

It is exactly a normal reconstruction loss. The paired frame is used for the condition  C  but not the input x


openai: Unrecognized request argument supplied:stream_options

Version
0.6.8
Bug
1.When I upgraded from version 0.6.6 to 0.6.8, I encountered the following error message when using OpenAI:

2.Upon comparing version 0.6.6 with 0.6.8, it was found that in the OpenAI 'llm.py' there was additional handling for 'stream_option'. After commenting this out and repackaging, OpenAI could be used normally again.

Additional questions
1."After installing 'mysql-connector-python', does Dify's 'code execution' support connecting to a database?"

sorry

Closing as this isn't the right repository for this issue


amarok: use ffmpeg instead of ffmpeg_3

Motivation for this change
#94003 and #120372
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I get
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded

when playing a song. But that also happens on master.

I get

WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded

when playing a song. But that also happens on master.

A phonon backend needs to be manually installed if you're not on kde. See #103543.

@ryneeverett If you could test whether the package still works after this change, that would be fabulous.

I guess what needs to be tested is the transcoding functionality, but I'm not sure how to even do that.


Feat: ResourceTracker new architecture

This PR is proposed to rework ResourceTracker and upgrade the current resource management architecture for KubeVela controller.
Major Changes

Remove OwnerReference in managed resources. This simplifies the create and update for resources.
Record rendered Resource in ResourceTracker.Spec.ManagedResource. This allows StateKeep after workflow so that configuration drift for applied resources can be prevented.
ResourceTracker deletion will use application controller to reconcile.
Resources in ManagedCluster are directly recorded in ResourceTrackers in Hub Cluster, which means we do not need RT in Managed Clusters anymore.
Add GarbageCollect Policy and ApplyOnce Policy.
a. The former one allows difference resources have various life-cycle. Usually, resources are deleted as soon as the latest application does not use them anymore. Some resources need to be kept until the application is gone. Some might need be kept even if the application is gone.
b. The latter one allows us to prevent configuration-drift by running StateKeep after workflow suspended/terminated/succeed.

Minor Changes

ControllerRevisions are directly recorded in ResourceTrackers.
Addon Application use ApplyOnce by default.
MultiCluster do not need extra gc logic.

Deprecation

AppRollout is not supported anymore. Another PR is called to remove it permanently.
ReosurceTracker.Status is deprecated.

Implementation

Main changes are implemented in pkg/resourcekeeper/ where resource recording, garbage collecting and state keeping are supported. It is recommended for code reviewers to review from here, since other changes are all about making this package work properly.
Lots of tests are fixed and added.

I have:

[x] Read and followed KubeVela's contribution process.
[ ] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[x] Run make reviewable to ensure this PR is ready for review.
[x] Added backport release-x.y labels to auto-backport this PR if necessary.
[x] Add more e2e-test.

I noticed there are some changes on apis/core.oam.dev/v1alpha1. Will it lead to any compatibilities problems?

I noticed there are some changes on apis/core.oam.dev/v1alpha1. Will it lead to any compatibilities problems?

Yes, there will be compatibility problems. ResourceTracker will face an upgrade concerning existing KubeVela system. Some compatibility code and tests will be added.


[in_app_purchase] finishPurchase does not exist

Is there an existing issue for this?

[X] I have searched the existing package issues
[X] I have read the guide to filing a bug

What package does this bug report belong to?
in_app_purchase
What target platforms are you seeing this bug on?
iOS
Have you already upgraded your packages?
Yes
Steps to reproduce
finishPurchase is mentionned in the doc, but does not exist in the package. So, is that still relevant ? If so, where do I need to call this ?

Could you please cite the documentation source along with the use case for finishPurchase? As I can see, it seems to be completePurchase which will invoke finishTransaction on iOS/macOS.

IMHO, this could be a documentation issue. Perhaps, it's completePurchase but I'm not sure.

@stuartmorgan @huycozy I like to pick this up.

@stuartmorgan I have raised a PR, could you please review it when you have time.
https://github.com/flutter/packages/pull/5081


add counter to UI

Adding a counter and balance to the UI

After making these changes, the items available counter does not update after a successful transaction but will update if I reload the page.  Also "Items available: /" is displayed above the Connect Wallet button on fresh reload.


Investigate accessing iOS system fonts

This is what I had found about this before:
http://stackoverflow.com/a/9381326
https://gist.github.com/Jyczeal/1892760

The snippet of code that @tallytalwar mentioned can be used to decode the TTF file in memory on the iOS platform side, an interface to upload this data to the tangram font context is available on this branch https://github.com/tangrams/tangram-es/tree/ios-ttf-blob for testing purposes, in tangram.h:
void addTTFblob(char* _data, size_t _size, const char* _family, const char* _style, const char* _weight);

This API can be revised if this techniques of decoding TTF happens to be working on iOS.
cc @msmollin

Closed via https://github.com/tangrams/tangram-es/pull/1092


Unable to compile in typescript (ionic)

Expected Behaviour
Should compile and run as expected
Actual Behaviour
Module not found: Error: Can't resolve 'phonegap-plugin-push/types'
Reproduce Scenario (including but not limited to)
ionic cordova plugin add phonegap-plugin-push
setup <resource-file src="GoogleService-Info.plist" />
ionc cordova run android
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
android 6
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
one plus 2
Cordova CLI version and cordova platform version
cordova --version   : 8.0.0                             # e.g. 6.0.0
cordova platform version android : 7                     # e.g. 4.1.1

Plugin version
cordova plugin version | grep phonegap-plugin-push  : 2.1.3

Other plugins used:
cordova-plugin-add-swift-support 1.7.2 "AddSwiftSupport"
cordova-plugin-background-fetch 5.4.1 "CDVBackgroundFetch"
cordova-plugin-cocoalumberjack 0.0.4 "CocoaLumberjack"
cordova-plugin-device 2.0.2 "Device"
cordova-plugin-firebase 2.0.5 "Google Firebase Plugin"
cordova-plugin-globalization 1.11.0 "Globalization"
cordova-plugin-inappbrowser 3.0.0 "InAppBrowser"
cordova-plugin-ionic-keyboard 2.1.3 "cordova-plugin-ionic-keyboard"
cordova-plugin-ionic-webview 2.1.4 "cordova-plugin-ionic-webview"
cordova-plugin-network-information 2.0.1 "Network Information"
cordova-plugin-splashscreen 5.0.2 "Splashscreen"
cordova-plugin-statusbar 2.4.2 "StatusBar"
cordova-plugin-whitelist 1.3.3 "Whitelist"
cordova-sqlite-storage 2.4.0 "Cordova sqlite storage plugin"
cordova.plugins.diagnostic 4.0.10 "Diagnostic"
phonegap-plugin-barcodescanner 8.0.0 "BarcodeScanner"
phonegap-plugin-push 2.1.3 "PushPlugin"```

Note: there is a node module callded phonegap-plugin-push inside node_modules and Visual code IDE doesn't show any error. Error occurred only while compiling

@jcesarmobile
At the end of the day the plugin works as a npm module, and the types arrive with the source/bin, and npm/node/typescript/tsc knows how to handle them properly. Setting up multiple/extra layers of build tools like ionic (that provide their own push notification type definitions btw) on top of it will make it nontrivial, and the ecossystem is too big for us to give general directions.
If a minimal reproduction scenario comes up with an issue, we might be able to pinpoint and maybe improve our commonJS/es6-modules model.


Update deprecated config.

'main' found as duplicate, separated to 'series' and 'movies'.
reset_unmatched_scores no longer accepts true/false: https://recyclarr.dev/wiki/upgrade-guide/v6.0/#reset-scores

Thanks for sharing this! I must have missed that reset_unmatched_scores deprecation. I am curious what the issue is with the main instance name? For me it hasn't resulted in any errors 🧐

Thanks for the assist @jahanson!


unsure links outside root resolve to the baseUrl

Published PR with canary version: 1.10.1-canary.102.1448


add existing repos

Suggested new feature or improvement
Add already cloned repositories to the machine configuration.
Scenario
I have a repository already cloned. And I want to add it but right now the only option is to add via URL.
Additional details
No response

See #1049


Call pipeline without vertex input

It would be nice to have a way to call the pipeline without input attributes for vertices.
I have data already loaded on the gpu, and just want to use them as vertex data like this:
layout(set = 0, binding = 0) buffer b {
    vec3 pos[];
} buf;

void main() {
    gl_Position = vec4(buf.pos[gl_VertexIndex], 1);
}

I don't think, there's a way to do that in vulkano yet.
Some Ideas, how this could be done:
Currently this doesn't do anything useful:
struct Vertex;
impl_vertex!(Vertex);

A sequence of such empty vertices could be used instead of memory consuming pseudo vertices.
Another idea would be a way to add a new method to the GraphicsPipelineBuilder similar to vertex_input and vertex_input_single_buffer and may be called ǹo_vertex_input

You can do that by passing a BufferlessDefinition to vertex_input: https://docs.rs/vulkano/0.7.1/vulkano/pipeline/vertex/struct.BufferlessDefinition.html
However that can't be used if you then cast the created pipeline into a GraphicsPipelineAbstract.

Thanks, this looks good. I'll try it.


chore(ci): disable toolchain in go.mod

What this PR does / why we need it:
This unbreaks the CI. Reason for this is that FOSSA Github action doesn't support go 1.21's toolchain directive.
Related issue: https://github.com/Kong/kubernetes-ingress-controller/issues/4635
This aims to prevent failures like this: https://github.com/Kong/kubernetes-ingress-controller/actions/runs/6141226981/job/16661215380
Which issue this PR fixes:

Special notes for your reviewer:

PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[ ] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

There is a problem with go.mod, see

😅 Fixed!


Should be using memmove instead of memcpy?

The function CUnescapeInternal claims that the source/destination pointers may point to the same buffer: https://github.com/abseil/abseil-cpp/blob/0bbebc85cd8dbd382b10698b3cefe9a01e88e76f/absl/strings/escaping.cc#L79
However it uses memcpy in some situations:
https://github.com/abseil/abseil-cpp/blob/0bbebc85cd8dbd382b10698b3cefe9a01e88e76f/absl/strings/escaping.cc#L140
https://github.com/abseil/abseil-cpp/blob/0bbebc85cd8dbd382b10698b3cefe9a01e88e76f/absl/strings/escaping.cc#L173
https://github.com/abseil/abseil-cpp/blob/0bbebc85cd8dbd382b10698b3cefe9a01e88e76f/absl/strings/escaping.cc#L206
https://github.com/abseil/abseil-cpp/blob/0bbebc85cd8dbd382b10698b3cefe9a01e88e76f/absl/strings/escaping.cc#L254
Because of that, if overlapping buffers are passed in, memcpy would be an unsafe choice.
I honestly don't have a way to reproduce the unexpected behavior because I don't have access to an implementation of memcpy that actually takes advantage of not allowing overlapping buffers.
I found this by running formal checking (https://github.com/diffblue/cbmc) on this function, you know, just for fun :)

It looks like this function is never called with leave_nulls_escaped=true, so it is impossible to trigger this behavior.
(We have unreleased code that does call the function with leave_nulls_escaped=true, so I'm patching this for this case, but OSS users are unaffected.)


Make the iOS Forms views non-opaque

By default, the UWP and Android views are not opaque. These patches explicitly change the iOS renderers to copy this behavior.
I split the patches in two because I think the GL one could have some performance impacts.
This would fix #198

@laarmen as soon as you sign the CLA, we can merge


How to become a plugin contributor?

Hi!
Let's say I've developed an incredibly useful plugin for Cerebro (https://github.com/grundiss/cerebro-pluggin-shruggie).
How do I make it searchable/installable for people via plugins Cerebro command?

My bad, found in docs


TypeError: unexpected keyword argument 'force'

I've tried to run /network/demo_wifi_ap_scan.py but I got the following error.

That error happens at this line
https://github.com/sipeed/MaixPy_scripts/blob/6928fe172a77402915850a27c6f8fe04a75b8223/network/demo_wifi_ap_scan.py#L7
I've used the latest firmware v0.3.2 and Maix Dan Doc board.
What is wrong?

http://dl.sipeed.com/MAIX/MaixPy/release/master/maixpy_v0.4.0_6_g715665c/

It's fixed at above firmware. Thank you @Neutree !


Add missing semicolon to locales/en.js blueprint

Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! :smile:

CLA is valid!

Awesome, thanks :+1:


Fix: Sequence numbers are not reset after connection termination

This issue occurred on the RaSTA server side where the server would after a first properly terminated connection discard all incoming packages from subsequent connections of the same client.
This change fixes the described behavior.
Thoughts:

Instead of resetting the channel state after proper connection termination, we should rather enforce a clean state before accepting / connecting a new connection (is is possible that a connection does not terminate 'properly'?)
Does a symmetric behavior exist for the client? is this addresses by this fix as well?

Regarding the build failure: I wasn't able to reproduce it locally. My hypothesis is that there must have been a (very consistent) race condition where some part of the connection was still active and accessed the seq_rx, seq_tx values after them being reset.
I decided to move the zero-initialization to a method called redundancy_channel_init which is called during in the redundancy_channel_connect method (for the RaSTA client). I was thinking about an 'object' lifecycle naming convention alloc, init, free. Since this issue is about server-side behavior, I also added a re-initialization of the mux in rasta_accept. I'm assuming that there is only ever one active connection, otherwise this could be problematic. We should refactor the code to only handle a single connection as a next step.
Then, things got a little wild... I decided to refactor the public API surface and move most of the headers into the internal source tree. That way, consumers of the library are not exposed to the internal data structures and as part of the initial configuration of the library, these data structures are malloced once.


Implement mixin application inference behind the super-mixins flag

In order to land the flutter framework changes suggested in #31984 (issues with mixins) the analyzer needs to support mixin application inference behind the super-mixins flag.
The pull request for flutter https://github.com/flutter/flutter/pull/14392 is blocked on this.

Is the analyzer implementation of this being worked on?  @devoncarew @bwilkerson

Looks like this is at least partially implemented?  Should this be closed, or is it still open pending further iteration?

Regarding the analyzer implementation, I am working on it.  I've filed a separate issue to track the analyzer work: #32146

@kmillikin implemented this in CFE.  @stereotype441 is tracking the analyzer impl in #32146, so closing this one.

One thing to note: this is not yet behind a flag, it is on for Fasta with --strong and can't be disabled.  I'll change that next week by exposing an option in the Fasta API for the VM and plumbing through the flag from the VM.


Remove clear_on_drop dependency

After https://github.com/paritytech/substrate/pull/6676, we no longer need the clear_on_drop dependency in the browser node.

So the root cause of https://github.com/paritytech/substrate/issues/4179 is fixed?

Before #6676, clear_on_drop was a dependency of ed25519-dalek. The root cause of #4179 is that compiling the runtime isn't supposed to compile ed25519-dalek (and thus not clear_on_drop either).


Student ID Card Error

Time Tracking: MA-34
Might be caused by the this attribute in the JSON object returned from MyStudentProfile, "Student_Level_Current": null.

[x] Pull from upstream to get the latest code
[x] Checkout the feature branch
[x] Compile and run the code
[x] Reproduce the bug
[x] Fix the bug
[x] Test locally on a device
[ ] Create Pull Request

ID Card issue in prod fixed by increasing the memory on Lambda Function: "ExtractPIDAuthorizer"
ID Card issue in QA fixed by adding a mapping template to the Lambda function for MyStudentProfile


How did you used LAMB optimizer with ZeRO CPU offload?

Thanks for this great project.
In your blog: https://medium.com/yandex/yandex-publishes-yalm-100b-its-the-largest-gpt-like-neural-network-in-open-source-d1df53d0e9a6, you have used LAMB optimizer and ZeRO offload, but isn't ZeRO CPU offload have to use DeepSpeedCPUAdam for good performace?
And i did not find LAMB optimizer codes in this project code.

Hi! We did use LAMB, but we used ZeRO-3, not ZeRO Offload. Thus, we were able to use the GPU version of LAMB from Apex.
Interestingly, in the case of ZeRO-3, LAMB's behavior is slightly different. But, according to our experiments, this does not affect the quality of training in any way.

Thanks for the detailed reply.


Add bgm_on and bgm_off scripts so I can enable/disable the service without editing user-startup.sh

Would love to just turn on/off the service through the MiSTer menu rather than through FTP/SSH and editing user-startup.sh directly.

Hey. Thanks for the report. I actually added a feature (not on GitHub yet) to let you enable/disable starting on boot from the ini file but I can see now that isn't really going to fix your problem
I think what I'm going to do instead is get rid of the control scripts and make the main bgm script display a basic control GUI similar to my favorites script and the mister ini editor. So you'll be able to edit some ini options from there
This'll be a bit low down the todo list but keep an eye out cause I need to do it to prepare for my web remote idea

This is supported now! Let me know how it goes


glesv2: more services from OpenGL ES 2.0 to prepare for gamnit

This PR adds a few services to the low-level graphics modules to prepare for gamnit.
This is the 2nd PR to use a new style for the glesv2 module. The old code has not yet been fully updated, so the style may vary in the same module. The new style try to stay as close as possible to the names and signatures used by the OpenGL ES 2.0 C API and by webgl.
As usual with this module, for more documentation please refer to the official doc at https://www.khronos.org/opengles/sdk/docs/man/.

+1, but I'm not fan of 1 commit per function, it make the reviewing more complex for me

@privat I had a lot of conflicts when creating this PR, so moving around smaller commits was easier.

indeed, it conflicts with #1709. Wich one should I merge first?

This one please! Then we can ignore the first 3 commits of #1709.  (but git should take care of it... )

please add a commit to magically skip opengl tests on OSX. i..e. add
Error: package `egl` unknown by `pkg-config`, make sure the development package is be installed.

in https://github.com/nitlang/nit/blob/master/tests/sav/Darwin/todo
cf: http://gresil.org/jenkins/job/CI Github OSX/105/testReport/tests.nitcs.lib/glesv/opengles2_hello_triangle/

Added a commit to ignore EGL on OS X.

OK, you can change just the typo in docs, and :shipit: :)


Enable Customize trigger function for Sensors

Hey @Sannma7,
I'm a bit hesitant to merge this just because it's fairly straightforward for consumers to override the default activator of a sensor.
class MyPointerSensor extends PointerSensor {
  static activators = [
    {
      eventName: 'onPointerDown' as const,
      handler: (
        {nativeEvent: event}: PointerEvent,
        options: PointerSensorOptions
      ) => {
        return true;
      },
    },
  ]
}

I'm also unclear how well this approach would scale for consumers if there were multiple activators defined for a given sensor.

I did override the activator in this approach to make my sensor only triggered by a pen.
I opened this pr because I think it's more friendly to consumers to do this without having to dig into source code.
What about just export the AbstractPointerSensor?


WTerrSetter helper class

Helper to create a helper class that can set tiles sides and corners at the same time

This is completed.


K-means clustering algorithm

Description
This is an implementation of Kmeans Clustering algorithm for Boost GIL. The input image filename(absolute/relative) must be passed as a command line argument. During execute ,input the required number of iterations and K value that indicates number of clusters.
I would request the community to kindly provide feedback for my implementation
I would also like to use the implementation of this algorithm for my gil competency test for GSOC 2021.
References
Tasklist

[ ] Add test case(s)
[ ] Ensure all CI builds pass
[ ] Review and approve

are you planning to have it as a competency test only or you wish to get this PR merged in GIL at some point?

are you planning to have it as a competency test only or you wish to get this PR merged in GIL at some point?

Right now I'm just planning to have it as a competency test only but if this passes all the cases then I would like to get this PR merged in GIL.

Keep in mind that any PR needs to conform to these, ideally, before it is even reviewed:

https://github.com/boostorg/gil/blob/develop/CONTRIBUTING.md#pull-requests
https://github.com/boostorg/gil/blob/develop/CONTRIBUTING.md#guidelines

then maybe you should have a look at other PRs and https://github.com/boostorg/gil/blob/develop/CONTRIBUTING.md. In the current state it is nowhere in mergable state.

then maybe you should have a look at other PRs and https://github.com/boostorg/gil/blob/develop/CONTRIBUTING.md. In the current state it is nowhere in mergable state.

Ok I understand, but from the perspective of GSoC, can this serve as competency test for my project in GSoC?

We'll consider it. just link it in your proposal...


merge: dev to master

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


Replace pidof with pgrep

Replace pidof with pgrep and improve bare-metal instructions.

Pgrep will have problems if other processes are running that contain nuodb in name.  You should include ^nuodb$.  Pidof is more reliable
Sent from my iPhone

On Oct 29, 2020, at 9:48 PM, Adrian Suarez<EMAIL_ADDRESS>wrote:

Merged #8 into master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Releases are missing contents of changelog

Releasetool releases are missing the contents of the changelog. https://github.com/googleapis/releasetool/releases

Not sure if this is still happening. The latest one worked.


CLI to bump all versions at once

Context:
As project's dependencies grow, handle all opened PR by each dependency gets difficult and boring. So a way to handle it at once would make our daily job easier.
Solution A:

Have a configuration option to make Dependabot open only one PR with all the versions bumped instead of one by each dependency.

Solution B:

Provide a CLI tool to run it locally for a specific project. So we can bump the versions locally, test, fix, test and then push the new versions.

Duplicate of #1190
Solution A would be satisfied by #1190. It's unlikely we'd take solution B.


Explicitly check if a GVK exists before creating corresponding object reconciler

After upgrading sigs.k8s.io/controller-runtime version to v0.5.0, we can create reconciler successfully even when the resource does not exist in the cluster. Therefore, we explicitly check if the resource exists before creating the reconciler. See detailed discussion in: kubernetes-sigs/controller-runtime#840
Tested: unit tests, GKE cluster

/assign @adrianludwin
/assign @yiqigao217

/hold cancel


improve documents of ACS

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

[x] The PR has modified HISTORY.rst with an appropriate description of the change (see Modifying change log).

Command Guidelines

[x] Each command and parameter has a meaningful description.
[x] Each new command has a test.

(see Authoring Command Modules)

@rjtsdl,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

#4117 #4273

Codecov Report

Merging #4312 into master will decrease coverage by 0.15%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #4312      +/-   ##
==========================================
- Coverage   70.06%   69.91%   -0.16%
==========================================
  Files         475      475
  Lines       29888    29888
  Branches     4620     4620
==========================================
- Hits        20941    20895      -46
- Misses       7464     7505      +41
- Partials     1483     1488       +5

Impacted Files
Coverage Δ

...ure-cli-acs/azure/cli/command_modules/acs/_help.py
100% <ø> (ø)
:arrow_up:

...re-cli-acs/azure/cli/command_modules/acs/custom.py
46.01% <ø> (ø)
:arrow_up:

...e-cli-acs/azure/cli/command_modules/acs/_params.py
76.71% <100%> (ø)
:arrow_up:

...d_modules/azure-cli-interactive/azclishell/util.py
46.8% <0%> (-12.77%)
:arrow_down:

...cli-core/azure/cli/core/commands/_introspection.py
83.11% <0%> (-11.69%)
:arrow_down:

src/azure-cli-core/azure/cli/core/keys.py
83.87% <0%> (-6.46%)
:arrow_down:

...acr/azure/cli/command_modules/acr/_docker_utils.py
15.38% <0%> (-5.77%)
:arrow_down:

.../azure/cli/command_modules/resource/_validators.py
64% <0%> (-4%)
:arrow_down:

...-cli-acs/azure/cli/command_modules/acs/_actions.py
51.92% <0%> (-3.85%)
:arrow_down:

src/azure-cli-core/azure/cli/core/_session.py
78.18% <0%> (-3.64%)
:arrow_down:

... and 13 more

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 9e6df7d...d7c734a. Read the comment docs.


Puma plugin fails with NameError

We've just integrated solid_queue in our Rails app and want to use the puma plugin to run Solid Queue's supervisor. However, with our current puma config, this fails:
/.rvm/gems/ruby-3.3.2/gems/solid_queue-0.3.3/lib/puma/plugin/solid_queue.rb:13:in `block (2 levels) in start': uninitialized constant SolidQueue (NameError)

        SolidQueue::Supervisor.start(mode: :all)
        ^^^^^^^^^^
	from /.rvm/gems/ruby-3.3.2/gems/solid_queue-0.3.3/lib/puma/plugin/solid_queue.rb:11:in `fork'
	from /.rvm/gems/ruby-3.3.2/gems/solid_queue-0.3.3/lib/puma/plugin/solid_queue.rb:11:in `block in start'
	from /.rvm/gems/ruby-3.3.2/gems/puma-6.4.2/lib/puma/events.rb:17:in `block in fire'
	from /.rvm/gems/ruby-3.3.2/gems/puma-6.4.2/lib/puma/events.rb:17:in `each'
	from /.rvm/gems/ruby-3.3.2/gems/puma-6.4.2/lib/puma/events.rb:17:in `fire'
	from /.rvm/gems/ruby-3.3.2/gems/puma-6.4.2/lib/puma/events.rb:46:in `fire_on_booted!'
	from /.rvm/gems/ruby-3.3.2/gems/puma-6.4.2/lib/puma/cluster.rb:495:in `run'
	from /.rvm/gems/ruby-3.3.2/gems/puma-6.4.2/lib/puma/launcher.rb:194:in `run'
	from /.rvm/gems/ruby-3.3.2/gems/puma-6.4.2/lib/puma/cli.rb:75:in `run'
	from /.rvm/gems/ruby-3.3.2/gems/puma-6.4.2/bin/puma:10:in `<top (required)>'
	from /.rvm/gems/ruby-3.3.2/bin/puma:25:in `load'
	from /.rvm/gems/ruby-3.3.2/bin/puma:25:in `<main>'
	from /.rvm/gems/ruby-3.3.2/bin/ruby_executable_hooks:22:in `eval'
	from /.rvm/gems/ruby-3.3.2/bin/ruby_executable_hooks:22:in `<main>'
[95129] ! reaped unknown child process pid=95143 status=pid 95143 exit 1

I've reduced our puma.rb config and also reproduced the issue with a new Rails app.
Steps to reproduce:

Create a new Rails app: rails new "solid_queue" -T --api --no-tests
Add the gem to the Gemfile gem "solid_queue"
Run bundle install
Install with rails generate solid_queue:install
Migrate with rails db:migrate
Modify the puma.rb config:
a. Configure workers to be used, i.e. workers 2
b. Add preload_app! false
Start the app through Puma with bundle exec puma
⚡ See the above name error.

Even without starting the app through puma, I was able to reproduce the error with the following steps:
Steps to reproduce:

Create a new Rails app: rails new "solid_queue" -T --api --no-tests
Add the gem to the Gemfile gem "solid_queue"
Run bundle install
Install with rails generate solid_queue:install
Migrate with rails db:migrate
Modify the puma.rb config:
a. Configure workers to be used, i.e. workers 2
b. Add prune_bundler
Start the app regularly through rails s
⚡ See the above name error.

In our production environment, we use a combination of the puma command with preload_app! false ("replaced" by fork_worker) and prune_bundler for phased restarts. Obviously, this configuration isn't supported by the puma plugin.
Ruby: 3.3.2 +YJIT
Rails: <IP_ADDRESS>
Puma: 6.4.2
Solid Queue: 0.3.3

Even without starting the app through puma, I was able to reproduce the error with the following steps:

Do you mean without using the Solid Queue plugin at all? It just fails when you try to start the app via rails s?

Sorry for not being clear on this. In the original issue report, I provided two different lists of reproduction steps for this issue:

The first list contains a combination of puma settings that is problematic when the web server is started through bundle exec puma but not when it is started with bundle exec rails s.
The second list of reproduction steps shows the erroneous behavior either with bundle exec puma or bundle exec rails s.

Even without starting the app through puma, I was able to reproduce the error with the following steps:

Here, I wanted to highlight that the second list does not require bundle exec puma (as a command), but also shows the erroneous behavior when starting through bundle exec rails s.
In any case, the puma plugin is required to reproduce the issue. Without the Solid Queue plugin for Puma, the error does not occur. Since the Puma plugin is going to be removed with #303, this issue is obsolete and can be closed.

Ah, got it! Sorry, I misunderstood what you meant! 🙏  Thanks a lot for taking the time to clarify. And yes, it's true that with the Puma plugin going away, the issue is no longer applicable. Thanks again.

Like with #243, we're going to keep the plugin in the end, so I'll reopen. Thanks again for your patience!


Wrong detect in python

Just regular tuple detected as color.
Example:

def wrong_detect():
for x in (0, 1, 2):
print(x)

PyCharm 2023:

Can you fix this? Thanks


Add support for progress bars within buttons

Please consider adding support for a progress bar inside of a button:
<button class="btn btn-primary btn-block">
  <progress class="progress progress-striped" value="25" max="100">25%</progress>
</button>

In this case I have added btn-block so the button does not shrink to nothing. A minor tweak to the margin may be all that is required.
.btn .progress {
  margin: 0.313rem 0; /* just playing around this happen to be all I needed */
}

The current (alpha-2) default css has a bottom margin that messes with centering within .btn and the resulting button can effect alignment within a grid.
~Thanks

Just out of interest, is there any example/use case for this sort of construct?

My most immediate interest is a hobby project: http://sk-resource-management-game.meteor.com/, click scav
In another project I have a BS3 project that does a number of uploads that I can count. When I eventually convert it over I would like to use the submit button to show the status of the upload.

We'll pass on supporting this for the time being. Thanks though!


Fix: Window position creeps between executions on scaled monitors

Closes https://github.com/emilk/egui/issues/4442
Refactors active monitor detection so it can be called from multiple locations.

Compare this gif to the one on the issue report.

Investigation notes

WindowSettings.inner_position_pixels and WindowSettings.outer_position_pixels are stored in physical/pixel coordinates.
ViewportBuilder::with_position expects to be passed a position in logical coordinates.
Prior to this PR, the position was being passed from WindowSettings to with_position without any scaling. This was the root cause of the issue.
The fix is to first convert the position to logical coordinates, respecting the scaling factor of the active monitor. This requires us to first determine the active monitor, so I factored out some of the logic in clamp_pos_to_monitor to find the active monitor.

I only tested on 100% and 150% monitors, and an egui_zoom_factor of 1.0 I will do some more testing this weekend!

More testing is complete. This works on other zoom factors and monitor scales too!

Thanks for the additional testing!


making it show a plan with different things happening

stage plan
aws_s3_bucket.dontdelete: Refreshing state... [id=pleasedontdeleteme-2983472938479283]
module.some_ec2_service.aws_instance.this: Refreshing state... [id=i-019b9be1b37b39df4]

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create
  - destroy
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # module.some_ec2_service.aws_instance.this must be replaced
-/+ resource "aws_instance" "this" {
      ~ arn                                  = "arn:aws:ec2:us-east-1:335168714028:instance/i-019b9be1b37b39df4" -> (known after apply)
      ~ associate_public_ip_address          = true -> (known after apply)
      ~ availability_zone                    = "us-east-1a" -> (known after apply)
      ~ cpu_core_count                       = 1 -> (known after apply)
      ~ cpu_threads_per_core                 = 2 -> (known after apply)
      ~ disable_api_termination              = false -> (known after apply)
      ~ ebs_optimized                        = false -> (known after apply)
      - hibernation                          = false -> null
      + host_id                              = (known after apply)
      ~ id                                   = "i-019b9be1b37b39df4" -> (known after apply)
      ~ instance_initiated_shutdown_behavior = "stop" -> (known after apply)
      ~ instance_state                       = "running" -> (known after apply)
      ~ ipv6_address_count                   = 0 -> (known after apply)
      ~ ipv6_addresses                       = [] -> (known after apply)
      + key_name                             = (known after apply)
      ~ monitoring                           = false -> (known after apply)
      + outpost_arn                          = (known after apply)
      + password_data                        = (known after apply)
      + placement_group                      = (known after apply)
      ~ primary_network_interface_id         = "eni-0d082a333eb3f704e" -> (known after apply)
      ~ private_dns                          = "ip-172-31-64-80.ec2.internal" -> (known after apply)
      ~ private_ip                           = "<IP_ADDRESS>" -> (known after apply)
      ~ public_dns                           = "ec2-3-237-64-168.compute-1.amazonaws.com" -> (known after apply)
      ~ public_ip                            = "<IP_ADDRESS>" -> (known after apply)
      ~ secondary_private_ips                = [] -> (known after apply)
      ~ security_groups                      = [ # forces replacement
          + "allow-nothing",
          - "default",
        ]
      ~ subnet_id                            = "subnet-d929a2bc" -> (known after apply)
        tags                                 = {
            "Application" = "some-ec2-service"
            "Name"        = "stage-some-ec2-service"
        }
      ~ tenancy                              = "default" -> (known after apply)
      + user_data                            = (known after apply)
      + user_data_base64                     = (known after apply)
      ~ vpc_security_group_ids               = [
          - "sg-ff42769b",
        ] -> (known after apply)
        # (5 unchanged attributes hidden)

      ~ capacity_reservation_specification {
          ~ capacity_reservation_preference = "open" -> (known after apply)

          + capacity_reservation_target {
              + capacity_reservation_id = (known after apply)
            }
        }

      - credit_specification {
          - cpu_credits = "unlimited" -> null
        }

      + ebs_block_device {
          + delete_on_termination = (known after apply)
          + device_name           = (known after apply)
          + encrypted             = (known after apply)
          + iops                  = (known after apply)
          + kms_key_id            = (known after apply)
          + snapshot_id           = (known after apply)
          + tags                  = (known after apply)
          + throughput            = (known after apply)
          + volume_id             = (known after apply)
          + volume_size           = (known after apply)
          + volume_type           = (known after apply)
        }

      ~ enclave_options {
          ~ enabled = false -> (known after apply)
        }

      + ephemeral_block_device {
          + device_name  = (known after apply)
          + no_device    = (known after apply)
          + virtual_name = (known after apply)
        }

      ~ metadata_options {
          ~ http_endpoint               = "enabled" -> (known after apply)
          ~ http_put_response_hop_limit = 1 -> (known after apply)
          ~ http_tokens                 = "optional" -> (known after apply)
        }

      + network_interface {
          + delete_on_termination = (known after apply)
          + device_index          = (known after apply)
          + network_interface_id  = (known after apply)
        }

      ~ root_block_device {
          ~ delete_on_termination = true -> (known after apply)
          ~ device_name           = "/dev/xvda" -> (known after apply)
          ~ encrypted             = false -> (known after apply)
          ~ iops                  = 100 -> (known after apply)
          + kms_key_id            = (known after apply)
          ~ tags                  = {} -> (known after apply)
          ~ throughput            = 0 -> (known after apply)
          ~ volume_id             = "vol-04449142f8adaf362" -> (known after apply)
          ~ volume_size           = 8 -> (known after apply)
          ~ volume_type           = "gp2" -> (known after apply)
        }
    }

  # aws_s3_bucket.dontdelete will be destroyed
  - resource "aws_s3_bucket" "dontdelete" {
      - arn                         = "arn:aws:s3:::pleasedontdeleteme-2983472938479283" -> null
      - bucket                      = "pleasedontdeleteme-2983472938479283" -> null
      - bucket_domain_name          = "pleasedontdeleteme-2983472938479283.s3.amazonaws.com" -> null
      - bucket_regional_domain_name = "pleasedontdeleteme-2983472938479283.s3.amazonaws.com" -> null
      - hosted_zone_id              = "Z3AQBSTGFYJSTF" -> null
      - id                          = "pleasedontdeleteme-2983472938479283" -> null
      - region                      = "us-east-1" -> null
      - request_payer               = "BucketOwner" -> null
      - tags                        = {} -> null
      - tags_all                    = {} -> null

      - versioning {
          - enabled    = false -> null
          - mfa_delete = false -> null
        }
    }

  # module.some_ec2_service.aws_security_group.this will be created
  + resource "aws_security_group" "this" {
      + arn                    = (known after apply)
      + description            = "Managed by Terraform"
      + egress                 = (known after apply)
      + id                     = (known after apply)
      + ingress                = (known after apply)
      + name                   = "allow-nothing"
      + name_prefix            = (known after apply)
      + owner_id               = (known after apply)
      + revoke_rules_on_delete = false
      + tags                   = {
          + "Name" = "allow-nothing"
        }
      + tags_all               = {
          + "Environment" = "stage"
          + "ManagedBy"   = "terraform"
          + "Name"        = "allow-nothing"
          + "Repo"        = "https://github.com/walkerab/terraform-plus-github-actions"
        }
      + vpc_id                 = (known after apply)
    }

Plan: 2 to add, 0 to change, 2 to destroy.

─────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.

stage plan

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+   create
-   destroy
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # module.some_ec2_service.aws_instance.this must be replaced
-/+ resource "aws_instance" "this" {
      ~ arn                                  = "arn:aws:ec2:us-east-1:335168714028:instance/i-019b9be1b37b39df4" -> (known after apply)
      ~ associate_public_ip_address          = true -> (known after apply)
      ~ availability_zone                    = "us-east-1a" -> (known after apply)
      ~ cpu_core_count                       = 1 -> (known after apply)
      ~ cpu_threads_per_core                 = 2 -> (known after apply)
      ~ disable_api_termination              = false -> (known after apply)
      ~ ebs_optimized                        = false -> (known after apply)
-       hibernation                          = false -> null
+       host_id                              = (known after apply)
      ~ id                                   = "i-019b9be1b37b39df4" -> (known after apply)
      ~ instance_initiated_shutdown_behavior = "stop" -> (known after apply)
      ~ instance_state                       = "running" -> (known after apply)
      ~ ipv6_address_count                   = 0 -> (known after apply)
      ~ ipv6_addresses                       = [] -> (known after apply)
+       key_name                             = (known after apply)
      ~ monitoring                           = false -> (known after apply)
+       outpost_arn                          = (known after apply)
+       password_data                        = (known after apply)
+       placement_group                      = (known after apply)
      ~ primary_network_interface_id         = "eni-0d082a333eb3f704e" -> (known after apply)
      ~ private_dns                          = "ip-172-31-64-80.ec2.internal" -> (known after apply)
      ~ private_ip                           = "<IP_ADDRESS>" -> (known after apply)
      ~ public_dns                           = "ec2-3-237-64-168.compute-1.amazonaws.com" -> (known after apply)
      ~ public_ip                            = "<IP_ADDRESS>" -> (known after apply)
      ~ secondary_private_ips                = [] -> (known after apply)
      ~ security_groups                      = [ # forces replacement
+           "allow-nothing",
-           "default",
        ]
      ~ subnet_id                            = "subnet-d929a2bc" -> (known after apply)
        tags                                 = {
            "Application" = "some-ec2-service"
            "Name"        = "stage-some-ec2-service"
        }
      ~ tenancy                              = "default" -> (known after apply)
+       user_data                            = (known after apply)
+       user_data_base64                     = (known after apply)
      ~ vpc_security_group_ids               = [
-           "sg-ff42769b",
        ] -> (known after apply)
        # (5 unchanged attributes hidden)

      ~ capacity_reservation_specification {
          ~ capacity_reservation_preference = "open" -> (known after apply)

+           capacity_reservation_target {
+               capacity_reservation_id = (known after apply)
            }
        }

-       credit_specification {
-           cpu_credits = "unlimited" -> null
        }

+       ebs_block_device {
+           delete_on_termination = (known after apply)
+           device_name           = (known after apply)
+           encrypted             = (known after apply)
+           iops                  = (known after apply)
+           kms_key_id            = (known after apply)
+           snapshot_id           = (known after apply)
+           tags                  = (known after apply)
+           throughput            = (known after apply)
+           volume_id             = (known after apply)
+           volume_size           = (known after apply)
+           volume_type           = (known after apply)
        }

      ~ enclave_options {
          ~ enabled = false -> (known after apply)
        }

+       ephemeral_block_device {
+           device_name  = (known after apply)
+           no_device    = (known after apply)
+           virtual_name = (known after apply)
        }

      ~ metadata_options {
          ~ http_endpoint               = "enabled" -> (known after apply)
          ~ http_put_response_hop_limit = 1 -> (known after apply)
          ~ http_tokens                 = "optional" -> (known after apply)
        }

+       network_interface {
+           delete_on_termination = (known after apply)
+           device_index          = (known after apply)
+           network_interface_id  = (known after apply)
        }

      ~ root_block_device {
          ~ delete_on_termination = true -> (known after apply)
          ~ device_name           = "/dev/xvda" -> (known after apply)
          ~ encrypted             = false -> (known after apply)
          ~ iops                  = 100 -> (known after apply)
+           kms_key_id            = (known after apply)
          ~ tags                  = {} -> (known after apply)
          ~ throughput            = 0 -> (known after apply)
          ~ volume_id             = "vol-04449142f8adaf362" -> (known after apply)
          ~ volume_size           = 8 -> (known after apply)
          ~ volume_type           = "gp2" -> (known after apply)
        }
    }

  # aws_s3_bucket.dontdelete will be destroyed
-   resource "aws_s3_bucket" "dontdelete" {
-       arn                         = "arn:aws:s3:::pleasedontdeleteme-2983472938479283" -> null
-       bucket                      = "pleasedontdeleteme-2983472938479283" -> null
-       bucket_domain_name          = "pleasedontdeleteme-2983472938479283.s3.amazonaws.com" -> null
-       bucket_regional_domain_name = "pleasedontdeleteme-2983472938479283.s3.amazonaws.com" -> null
-       hosted_zone_id              = "Z3AQBSTGFYJSTF" -> null
-       id                          = "pleasedontdeleteme-2983472938479283" -> null
-       region                      = "us-east-1" -> null
-       request_payer               = "BucketOwner" -> null
-       tags                        = {} -> null
-       tags_all                    = {} -> null

-       versioning {
-           enabled    = false -> null
-           mfa_delete = false -> null
        }
    }

  # module.some_ec2_service.aws_security_group.this will be created
+   resource "aws_security_group" "this" {
+       arn                    = (known after apply)
+       description            = "Managed by Terraform"
+       egress                 = (known after apply)
+       id                     = (known after apply)
+       ingress                = (known after apply)
+       name                   = "allow-nothing"
+       name_prefix            = (known after apply)
+       owner_id               = (known after apply)
+       revoke_rules_on_delete = false
+       tags                   = {
+           "Name" = "allow-nothing"
        }
+       tags_all               = {
+           "Environment" = "stage"
+           "ManagedBy"   = "terraform"
+           "Name"        = "allow-nothing"
+           "Repo"        = "https://github.com/walkerab/terraform-plus-github-actions"
        }
+       vpc_id                 = (known after apply)
    }

Plan: 2 to add, 0 to change, 2 to destroy.


Add parent relative path to JacORB compatibility subsystem

Linux Build 5766 is now running using a merge of d0c0c1890fbef196edefd5ece6b18a548222c983

Windows Build 876 is now running using a merge of d0c0c1890fbef196edefd5ece6b18a548222c983

Linux with security manager Build 752 is now running using a merge of d0c0c1890fbef196edefd5ece6b18a548222c983

Linux with security manager Build 752 outcome was SUCCESS using a merge of d0c0c1890fbef196edefd5ece6b18a548222c983
Summary: Tests passed: 795, ignored: 371 Build time: 0:06:30

Windows Build 876 outcome was SUCCESS using a merge of d0c0c1890fbef196edefd5ece6b18a548222c983
Summary: Tests passed: 2915, ignored: 366 Build time: 0:51:02

Linux Build 5766 outcome was FAILURE using a merge of d0c0c1890fbef196edefd5ece6b18a548222c983
Summary: Tests failed: 1 (1 new), passed: 2914, ignored: 366 Build time: 0:51:57
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.smoke.webservices.WSTestCase.testManagementDescriptionMetrics: java.lang.AssertionError: null
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)


iOS 7 support

Any chance of supporting iOS 7? A quite large share of our user base still uses it.
Thanks,

Hi. I haven't got any plans for the project to support less that iOS 8.


Add hal::soft::offset_servo implementation

Take a servo implementation and remap the definition of it position values. For example, take a servo that can move from 0 degs to 90 degs. If an application needs to control a servo from -45 deg to +45 deg, then the offset_servo implementation simply maps 0 to -45 degs and 90 to 45 deg. Making zero 45 degrees. This implementation should be done with addition only as to not distort the range of the input servo.

.take


Use the last Go version for travis CI

[ ] Link to issue, e.g. Resolves #NNN
[ ] Documentation added (if applicable)
[ ] Tests added
[x] Branch rebased on top of current master (git pull --rebase origin master)
[x] Changes squashed to a single commit (described here)
[x] Build is green in Travis CI
[x] You have certified that the contribution is your original work and that you license the work to the project under the Apache 2 license

Resolves #
Changes proposed in this pull request:

use the last Go version for travis CI

/cc @nats-io/core

Coverage increased (+0.07%) to 92.277% when pulling 0eebccbed8d1f2883ae07d2ac2967911dea38b91 on msoap:patch-1 into 3b0b139158165e1801394a893d66fe7e80ca58dd on nats-io:master.


Document task naming

I looked through the published documentation (https://tokio.rs/blog/2021-12-announcing-tokio-console, docs.rs pages for subscriber and console), and they mention that tasks can be named, but they don't mention how. I would e.g. expect maybe some way to name a spawned, maybe via a method on JoinHandle, but there doesn't seem to be such a thing...

Tasks can be named using an unstable Tokio API: https://github.com/tokio-rs/tokio/issues/4114
Currently, I believe Tokio's documentation is built on docs.rs without unstable features enabled. This means they don't show up in the docs.rs documentation. This should probably be fixed; we should probably build the documentation with the unstable features included, but flagged as unstable, so that users know that --cfg tokio_unstable is required to use those APIs.
The console docs don't currently include task::Builder API because it's a tokio API, rather than a console-subscriber one. But we should probably mention that it exists and how to use it.
I'm transferring this issue to the Tokio repository, though, because I think the most important change is probably to ensure that unstable features are visible in the docs.rs documentation.


formatting fails for files containing classes with constructors

Formatting within eclipse silently fails when the file contains:
shared class TestFormatter {
shared new () {}
}

Oops, we don’t support default constructors…

Should be better now :)

Ha, that was quick!


Function to set the vanityURL property on the user

Is your feature request related to a problem? Please describe.
I can listen for change on the vanityURL and can access it, but I'm not able to change it.
Describe the solution you'd like.
An easy function to change the vanityURL. Ex.: client.setVanityURL('newurl');

It's not possible to change your vanity URL through the client protocol.
You can do this with node-steamcommunity: https://github.com/DoctorMcKay/node-steamcommunity/wiki/SteamCommunity#editprofilesettings-callback


Add cursor shim support for non-fullscreen windows

Thanks! This looks good but could you please add the new parameter to the jsdoc comment?

Cool, I've tweaked the docs a bit more in #123. Will merge that instead.


fix(core): reapply resolve.symlinks: false

Motivation
Fix #6257. Since the Webpack bug is fixed, we can now reapply this config.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Removed the real path resolution in our dogfooding
Related PRs
#5126

@slorber This config doesn't work with PNPM. Should we just make it configurable instead?

😅
The webpack config is good enough but having this by default can be useful to avoid users form thinking about it. I think it's @felipecrs that mentioned this recently somewhere.
I don't know what might be the problem with pnpm unfortunately

PNPM uses hard links for all packages because they keep a global package storage. Webpack resolve.symlinks: false is known to fail with symlinked packages (similarly with npm link).

Also, the conversation you've been looking for is in that linked PR in the description. You seem to like injecting configuration with a plugin? Maybe we can promote this to a webpack.resolveSymlinks option?

PNPM uses hard links for all packages because they keep a global package storage.

Does it mean resolve.symlinks: false will never work with pnpm in any case?
Ping @zkochan, can you help us figure this out please?

You seem to like injecting configuration with a plugin? Maybe we can promote this to a webpack.resolveSymlinks config option?

If we add a shortcut, I'd rather add webpack.configure first ?
Not as convenient but generic and reusable in other cases.

If we add a shortcut, I'd rather add webpack.configure first ?

Cool as well

Going to close this. I think the plugin lifecycle is sufficient and with inline plugin modules, the bar to creating a plugin is extremely low.


minor tweaks to code

i'm going to open this pull request and feed you some tweaks a few at a time.  if you merge this one then i'll just open another so that as i update my branch you can see the changes.

That's great, thanks for the help. I'll leave it open and let me know when you're done!

btw, my ide strips trailing ws - sorry about that.

ok - that's the end of my tweaks.  please look over them as i haven't actually run the code and you'll need to do another build.

Ben, thanks for the updates.  I was able to run with your code, I did not see any problems.


Certainly not intentional. I'd rather pick just python3 or just python2, but there was a general hesitation to enforce python3 as the default python. I've been using pip2 and pip3 respectively but it sounds like we need to make sure the default pip lines up with the default python.


codeunit 7204 "CDS Setup Defaults" - Event Publisher OnBeforeResetCustomerAccountMapping

in procedure ResetCustomerAccountMapping

START Code on Top of procedure
OnBeforeResetCustomerAccountMapping(IntegrationTableMappingName, EnqueueJobQueEntry, IsHandled);
if IsHandled then
exit;
<< END Code

similar to procedure ResetItemProductMapping in codeunit 5334 "CRM Setup Defaults"
to OnBeforeResetItemProductMapping

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Feature/sparse multiply

Moving from stan-dev/stan#1405

Jenkins, retest this please.

Jenkins, test this please.

Sorry to bring this up now (in which case it would be okay to merge now and revisit later) but the most typical use-case for this is going to be X * beta where X is fixed. So, ideally it would be better to validate X once and reduce the amount of checking when T1 is double.

To deal with the fixed X case would I need to specialize this for doubles and write a functor to cache the fact that checks had been done once or is there some simpler solution?  Is there another function that this is done for that I could follow? Or are you suggesting writing a separate checking function that can be used on the data and leave the responsibility up to the user?  I think I could get it done either way before or after this is merged.

Whatever is easiest that avoids unnecessary checking. I think it would be
fine to expose a check_csr_matrix(...) function that the user could call in
transformed data and that Stan can call when T1 is a var. Then specialize
the multiplication when T1 is a double to not call check_csr_matrix(...)
and just check the vector that post-multiplies it.
On Sun, Aug 16, 2015 at 12:43 PM, Krzysztof Sakrejda <
<EMAIL_ADDRESS>wrote:

To deal with the fixed X case would I need to specialize this for doubles
and write a functor to cache the fact that checks had been done once or is
there some simpler solution? Is there another function that this is done
for that I could follow? Or are you suggesting writing a separate checking
function that can be used on the data and leave the responsibility up to
the user? I think I could get it done either way before or after this is
merged.
—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/math/pull/112#issuecomment-131580406.

I very strongly prefer validated calls that provide informative
error messages.  Whatever you do, it shouldn't be possible for
the code to segfault and crash R or Python.
There's no way to guarantee in Stan that any argument is the
output of any other function.  If a function can take a transformed
data object, it can take a data object that doesn't get checked.
The only validation for functions from the outside is the shape
of the argument (int, real, vector, row vector, matrix, plus array
of same) but not its size --- that all has to be built into the
function itself.
And yes, you can always specialize for double values if that can
be made more efficient.  But it's not necessary in a first version.
The key is to get the interface down, get the unit tests in place,
and then you can optimize later.

Bob

On Aug 16, 2015, at 1:09 PM, bgoodri<EMAIL_ADDRESS>wrote:
Whatever is easiest that avoids unnecessary checking. I think it would be
fine to expose a check_csr_matrix(...) function that the user could call in
transformed data and that Stan can call when T1 is a var. Then specialize
the multiplication when T1 is a double to not call check_csr_matrix(...)
and just check the vector that post-multiplies it.
On Sun, Aug 16, 2015 at 12:43 PM, Krzysztof Sakrejda <
<EMAIL_ADDRESS>wrote:

To deal with the fixed X case would I need to specialize this for doubles
and write a functor to cache the fact that checks had been done once or is
there some simpler solution? Is there another function that this is done
for that I could follow? Or are you suggesting writing a separate checking
function that can be used on the data and leave the responsibility up to
the user? I think I could get it done either way before or after this is
merged.
—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/math/pull/112#issuecomment-131580406.

—
Reply to this email directly or view it on GitHub.

On Sun, Aug 16, 2015 at 11:27 PM, Bob Carpenter<EMAIL_ADDRESS>wrote:

There's no way to guarantee in Stan that any argument is the
output of any other function. If a function can take a transformed
data object, it can take a data object that doesn't get checked.
The only validation for functions from the outside is the shape
of the argument (int, real, vector, row vector, matrix, plus array
of same) but not its size --- that all has to be built into the
function itself.

That is why I am saying we need to expose check_* functions so that they
can be called once on constants by the user in transformed data. If users
choose not to call the check_* function and then crash the interface, I
have negative sympathy for them.

And yes, you can always specialize for double values if that can
be made more efficient. But it's not necessary in a first version.
The key is to get the interface down, get the unit tests in place,
and then you can optimize later.

It is hard to optimize check_range(). I'm not sure if the compiler inlines
that, but I guess we can write a version that takes an int[] and only
requires one function call. Either way, we are still doing as many index
checks here as we are doing multiplications and additions in the
dot_product.

I think it will make sense to do an optimized version but for now I'm just going to do the coeffRef changes, linting, and get it in.  I won't be out of the woods with my other work for another couple of weeks and I don't want this to get left dangling again.

On Aug 17, 2015, at 12:20 AM, bgoodri<EMAIL_ADDRESS>wrote:
On Sun, Aug 16, 2015 at 11:27 PM, Bob Carpenter<EMAIL_ADDRESS>wrote:

There's no way to guarantee in Stan that any argument is the
output of any other function. If a function can take a transformed
data object, it can take a data object that doesn't get checked.
The only validation for functions from the outside is the shape
of the argument (int, real, vector, row vector, matrix, plus array
of same) but not its size --- that all has to be built into the
function itself.

That is why I am saying we need to expose check_* functions so that they
can be called once on constants by the user in transformed data. If users
choose not to call the check_* function and then crash the interface, I
have negative sympathy for them.

I know you have negative sympathy for them, but it makes our software
look bad and it makes it hard to debug what's happening.  I feel just as
strongly that we should avoid anything that crashes R or Python.  Now if
you want to call Stan out-of-process, I'd be a little less upset about
Stan crashing, but still don't think it'd be ideal.

And yes, you can always specialize for double values if that can
be made more efficient. But it's not necessary in a first version.
The key is to get the interface down, get the unit tests in place,
and then you can optimize later.

It is hard to optimize check_range(). I'm not sure if the compiler inlines
that, but I guess we can write a version that takes an int[] and only
requires one function call. Either way, we are still doing as many index
checks here as we are doing multiplications and additions in the
dot_product.

I'm OK with that.  The checks will be less costly because they don't
have implications for autodiff.  We can coax the compiler into generating
assembly that takes the pass case as the default so we never pay for
branch mispredictions unless an error's found.

Bob

@sakrejda, I took care of the cpplint errors.

@syclik, thanks for fixing the cpplint errors, it looks like I managed to clean up the rest. Is merging all that's left to do for this?

Is there a corresponding Stan manual request?  Is there anything this is waiting for before merging?

@bob-carpenter As far as I know this is ready to be merged.  We've gone through a few rounds of changes on what the function should be so I was waiting to see this get merged before I do a stan pull request and manual pull request.  The stan pull request should be fairly straightforward following issue 1565 and ditto for the manual.

@bgoodri said at the meeting this is good.


Base url option for #90

This is my PR for #90. Tried to make it as simple as possible along with tests and documentation.

Looks good. Once the tests pass, I'll merge it in. Thanks your your help!


x/website: syscall/js missing

If I go here, everything is normal:
https://golang.org/pkg/syscall
but if I go here, I am greeted with a blank page:
https://golang.org/pkg/syscall/js

As a workaround, this seems to do it:
https://pkg.go.dev/syscall/js

it's available if you specify the proper os/arch https://golang.org/pkg/syscall/js/?GOOS=js&GOARCH=wasm


Bump SpecialFunctions?

Can ArbNumerics use SpecialFunctions v1?
latest version is v1.1.0

change made, merge pending (thank you)


[Coverity CID :198877]Null pointer dereferences in /subsys/net/ip/net_if.c

Static code scan issues seen in File: /subsys/net/ip/net_if.c
Category: Null pointer dereferences
Function: net_if_ipv4_select_src_addr
Component: Networking
CID: 198877
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

*** CID 198877:    (FORWARD_NULL)
/subsys/net/ip/net_if.c: 2432 in net_if_ipv4_select_src_addr()
2426     		if (dst_iface) {
2427     			src = net_if_ipv4_get_ll(dst_iface, NET_ADDR_PREFERRED);
2428     		}
2429     	}
2430
2431     	if (!src) {
>>>     CID 198877:    (FORWARD_NULL)
>>>     Passing null pointer "dst_iface" to "net_if_ipv4_get_global_addr", which dereferences it.
2432     		src = net_if_ipv4_get_global_addr(dst_iface,
2433     						  NET_ADDR_PREFERRED);
2434     		if (src) {
2435     			return src;
2436     		}
2437
/subsys/net/ip/net_if.c: 2432 in net_if_ipv4_select_src_addr()
2426     		if (dst_iface) {
2427     			src = net_if_ipv4_get_ll(dst_iface, NET_ADDR_PREFERRED);
2428     		}
2429     	}
2430
2431     	if (!src) {
>>>     CID 198877:    (FORWARD_NULL)
>>>     Passing null pointer "dst_iface" to "net_if_ipv4_get_global_addr", which dereferences it.
2432     		src = net_if_ipv4_get_global_addr(dst_iface,
2433     						  NET_ADDR_PREFERRED);
2434     		if (src) {
2435     			return src;
2436     		}
2437


Allow setting multiple methods per endpoint at once

Is your feature request related to a problem? Please describe.
Creating an endpoint configuration per method is very verbose.
Describe the solution you'd like
Allow method configuration variable to accept array, for example:
["GET", "POST", "PUT"]
Describe alternatives you've considered
Using multiple configuration files with templates should work but again, very verbose

Hi @amrellafy,
Thanks for your input. Verbosity can be solved with templating, snippets, and meta generators. There are many ways to overcome this "user" problem, but every combination of endpoint and method must be a different entry for the KrakenD internals.


⚠ RPC server - Avalanche has degraded performance

In 59efbce, RPC server - Avalanche ($AVALANCHE_RPC_URL) experienced degraded performance:

HTTP code: 500
Response time: 56 ms

Resolved: RPC server - Avalanche performance has improved in bb4f941 after 6 minutes.


differentiate reconstructed symbol table based entries

I realized that when the debuginfo is missing for a symbol table entry, ddbug still outputs the entry with whatever it finds in the symbol table.
This is great! However, it did mislead me by thinking the debuginfo was emitted (when it wasn't), and this was something I was specifically investigating.
Is it possible to add for these cases something like a (no debug info) field or (reconstructed) or something, in order to flag it?

It should be putting these in a <symtab> unit.

Ah, I didn't even check for that/would have suspected it.

We can close then I guess, makes sense. To be clear anything not found in dwarf stuff is put into synthetic  unit, whose values/members are extracted directly from the binaries symbol table, yes?
Would be nice to have a blurb about this somewhere, but not sure where that would go

To be clear anything not found in dwarf stuff is put into synthetic unit, whose values/members are extracted directly from the binaries symbol table, yes?

Yes.
I do need to write some sort of documentation/manual that explains things like this.
I understand your use case, but it's possibly a bit specialized. I think the issue is you're coming from an angle of wanting to debug the DWARF generation, instead of just wanting to extract information (which is mostly what I use it for). I could add an option to disable usage of the symbol table, but I probably don't want to do anything more intrusive than that.

One thing you could do is if you know which unit the entry is in, then you could pass an option to ddbug to only display that unit.

yea, unit maybe could work, but honestly your time is probably spent elsewhere and other features. now that i know about symtab unit, i just know what to look out for


Postfinance Test account

it is possible to gain access to Swiss Postfinance testplatform to test EBICS
It is free of charge and open.
https://isotest.postfinance.ch/corporates/register
https://testplattform.postfinance.ch/corporates/register
here is some documentation.
https://testplattform.postfinance.ch/corporates/help
https://www.postfinance.ch/content/dam/pfch/doc/prod/pay/FS_EBICS_Parameterblatt_Software_479.07_de.pdf
I am open to do some testing and verification as we have a live account.
V.

Sorry for the late reply!
Be my guest, additional proven tests are more than welcome!

Do you need any help with testing/setting up?


MAINT: removed unused import sys

sys module was imported but not used in
https://github.com/scipy/scipy/blob/74f4e5a0b67817946528c5cf9cbe7d8a21f3b1be/scipy/sparse/linalg/eigen/lobpcg/lobpcg.py#L15

Tests all pass, merging. Thanks @Gotham13121997

Hey @ev-br I found couple more unused imports. Should I create individual pull requests or remove them all in one??

Maybe lump them together

Yeah i thought so but they are around 160 instances. I think I will go
about them module wise. It will be better.
On Sun, 23 Sep 2018, 01:01 Evgeni Burovski<EMAIL_ADDRESS>wrote:

Maybe lump them together
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/scipy/scipy/pull/9301#issuecomment-423767716, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AZNjHAak44mWMGzAIhePYtKIyPjLK3Qtks5udpAPgaJpZM4W1UAs
.

Yeah i thought so but there are around 160 instances. I think I will go about them module wise. It will be better.

Just try and group them a little please. We have ~15 modules; 15 PRs on this kind of cleanup is a bit much.

sure
On Sun, 23 Sep 2018, 08:10 Ralf Gommers<EMAIL_ADDRESS>wrote:

Yeah i thought so but there are around 160 instances. I think I will go
about them module wise. It will be better.
Just try and group them a little please. We have ~15 modules; 15 PRs on
this kind of cleanup is a bit much.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/scipy/scipy/pull/9301#issuecomment-423787473, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AZNjHFqzjAaBd3j_YwhlhtNcn5M6ttPSks5udvSQgaJpZM4W1UAs
.


Failed to start profiler - Failed to start session: An exception occurred while executing a Transact-SQL statement or batch.

Azure Data Studio Version: 1.25.2

Steps to Reproduce:

Connect to server.
Go to database
Press Alt + P

Error: Failed to start session: An exception occurred while executing a Transact-SQL statement or batch.

It is failing for this server, but working for another server I connect to.

I tried the workaround shared in https://github.com/microsoft/azuredatastudio/issues/6353. I ran the script on the server and tried starting the profiler again in Azure Data Studio, but it failed with the same issue.

I tried the workaround shared in https://github.com/microsoft/azuredatastudio/issues/6353. I ran the script on the server and tried starting the profiler again in Azure Data Studio, but it failed with the same issue.

@kraay do you see any error message in the "Help->Toggle Developer Tools" Console log?

I wasn't able to repro this with the latest build/extension.  Please add additional context to the issue, such as error logs etc., if you are still experiencing this problem.  Thanks!


Update dependencies to work with React Native

We make some calls to a few libraries that are incompatible with React Native ( child_process and fs for instance ) and others that need to be explicitly required for the dependency manager to find them (http, https).
Projects for React Native won't build with these dependencies missing.

How'd you end up solving this? By adding dependencies?

Hi @phillipwei - it has been some time and we are unsure if this issue has ben resolved for you. If it is, just know that we have worked with our Engineering team to prioritize goals for the SDK and this is on our long term road map. If we are to add this functionality, we will be sure to reopen the issue and solve accordingly.


URGENT: Tamilnadu API not working

The API for Tamilnadu has only been returning an empty list. Issue first noticed on the morning of June 18.
Even on covidbedsindia.in itself, the map hasn't been showing any hospitals in Tamilnadu since this issue
The source website (https://stopcorona.tn.gov.in/beds.php) is working perfectly though

Has been fixed, thank you!