add hashes to log lines to prevent tampering

To audit logs.
Other logs are not that critical.

should be optional.


module 'ffi' not found lua

when I was trying to run the example recurrent-visual-attention.lua,  I got a error saying : module 'ffi' not found lua. any ideas ?

It's used when you use rnn with cutorch or cltorch, as far as I know.  But it's builtin to luajit I think.  One idea: are you running using base lua rather than using luajit?
(Details on how ffi gets used:

line ~209 or so of rnn's Module.lua module calls param:storage():data()
storage.data() is defined in FFI.lua file, in both cutorch and cltorch (depending on which you are using)

)

Thanks @hughperkins


Should this project be considered dead?

No offense, just asking myself if @emre is no longer active.
If not, does it make sense to pick a community fork as the successor or simply invite interested contributors? They are already a number of forks

Can you send the links of active forks?

@EugenMayer can you respond to @emre's question? I'm curious as well what forks exist...
As for this project being dead: on the one hand there are 8 open PRs and 17 open issues, which indicates response times are slow, on the other hand storm could be considered rather finished. It does what it should do and does it well. What activity should there be then?

IMHO: One thing is assured, its not finished. It has a lot of enormous quick wins which are very hard to work around right now.
e.g. either fix the status codes or add insert-or-update .. which is basically the single most needed operation when you use storm in automated setups. And to be honest, on non automated, simple setups i guess a lot of people simply use plain old .ssh/config and edit it, thats about it.

to @emre ... asking me which fork is promising seems to be the wrong way to go about it.

Not exactly asked which fork is promising. I wanted to see the active forks. Currently, Github says there are 147 forks and I don't know which one of them is actively maintained and developed.  I don't know any easy way to find out.
Since you have posted this originally:

If not, does it make sense to pick a community fork as the successor or simply invite interested contributors? They are already a number of forks

I thought, there are some active forks you are aware. But, I believe that's not the case?

If you care so little right now and cannot dedicate time to check the forks with your knowledge applied, pick the most active forks and invite them as contributors to this project.

Everyone is free to contribute to the project via pull requests. I have left it stalled for a while but they will be reviewed at some point.

IMHO not many or very few will contribute to a project with that many PRs open and uncommented.

@EugenMayer maybe you should be a little less aggressive about this. @emre built this in his spare time and contributed it as open source. Now he doesn't have time, or maybe he doesn't feel like maintaining this anymore. That's his right.
Instead of complaining about it, and mentioning what features are so sorely missing, maybe you should start contributing those new features.
As for other developers not wanting to contribute because of open PRs and issues, I'd like to see some data/research on this, because it seems like bullshit. Open PRs and issues are in fact a very good reason to contribute so a project. It means your contributions are needed and thus valued.
Lastly, if you're unhappy with the progress of storm, and you think other forks are more ahead and/or provide features you want, you should just do some research yourself to figure out what fork best fits your needs, and start using that fork.

https://github.com/nicolascb/nssh

@EugenMayer As you probably know, open source on GitHub doesn't work that way. If you want a feature or bug you would open an issue about it. And if you can develop that feature, you would open a PR for it. People will review it.
Committing code rarely doesn't mean it is dead, it's simply feature complete and does not need to be updated frequently. If storm was not working I could understand your concern but I don't see any problem with the Storm right now.

I did in a form complain about him not picking up the task to either:
a) find a successor and promote it
b) invite direct contributors to h project to help him not being the


Support installing binaries for multiple platforms

Describe the feature
It would be great if SWC could optionally be installed for multiple platforms at the same time by specifying the binary targets (e.g., MacOS and Linux).
My use case: I have a NextJS application running in Docker. In dev environment, I use a volume for node_modules so that when I install a package in the project on my MacBook, the package is also added in the development container without me having to rebuild the container or run something like docker compose exec nextjs npm i <package>. This has worked well for me and is very convenient. However, currently, it does not work for SWC; if I run npm i -D @swc/cli @swc/core on my MacBook, it uses the binary for MacOS, so the Linux-based container does not get what it needs.
Here's an example of a similar feature that I use for Prisma:
https://www.prisma.io/docs/concepts/components/prisma-schema/generators#binary-targets
Babel plugin or link to the feature description
No response
Additional context
No response

@iacobfred you can just run npm install --ignore-platform to install all the platforms binary

Resolved it by adding it as optional dependency:
   "optionalDependencies": {
        "@swc/core-linux-x64-musl": "~1.2.143"
    }

update
Looks like it does work as long as you specify all of supportedArchitectures details
not just say os
e.g.
supportedArchitectures:
  os:
    - darwin
    - linux
  cpu:
    - x64
  libc:
    - glibc

will install
@swc-core-darwin-x64-npm-1.2.210
@swc-core-linux-x64-gnu-npm
Initially  hadn't specified glibc and the linux optional dep wouldn't install


Save settings to server?

I'm wondering if we want to save chat settings (ie ignored nicks, chat color, etc) to the server. This would require an additional API, not sure if we want to deal with that right now (@jnicol4, I think this is your area?)

Do the settings you have in mind need to be on the server, in the sense that all clients access to other's settings?  If not, local storage might be the better choice.

The reason I suggest this is that this way your username color, ignored list, etc. would be persisted across browsers and computers. They don't "need" to be stored on the server, but it would be nice.


tests: composer-cli compose metadata fails

# composer-cli compose list
0396b0be-410b-44b6-97dd-e317f2b17c52 FINISHED test-blueprint 0.0.2 AWS

# composer-cli --json compose metadata 0396b0be-410b-44b6-97dd-e317f2b17c52
No Content-Disposition header; cannot get filename

exit code 1.
This causes the newly enabled sanity tests in #642 to fail.

osbuild-composer doesn't have the same concept of metadata that lorax-composer did, so this has not been implemented yet, and may not be added. The use case for metadata was that you had everything you needed to recreate a build, it was all of the files from the result directory except for the actual image. I'm not sure this makes sense anymore, and was likely only ever used for debugging things.

@bcl If we decide that metadata doesn't make sense for osbuild-composer or that it is not something we care about we should think along the lines of disabling these commands (probably on the cli side) depending on backend. Otherwise people will run into them like I did and wonder why they fail.

I think we should return the manifests, they have exactly the behavior @bcl describes.

Ah! Great, I didn't realize there was similar data available.

Fixed by #661


Add LICENSE

close #7

@styfle any chance having this merged? It is important for some of our pnpm users to have all deps with license

It looks like now-cli uses apache but nearly all other ZEIT projects use MIT so I think MIT is a good choice for fetch-retry.


Youtube shorts not correctly rendering when copying link from the mobile app

**Youtube shorts don't seem to work when embedding the link from the  mobile app, they work fine when you copy the link from the desktop or mobile web browser,
This is a standard Shorts URL from the YT mobile app
e.g https://youtube.com/shorts/dlry-0801ba?feature=share**
How can I enable support from this kind of URL?

I believe all they need to do is swap shorts for embed in the URL:
https://youtube.com/shorts/dlry-0801ba
becomes
https://youtube.com/embed/dlry-0801ba

Did this fix it? https://github.com/cookpete/react-player/pull/1438


[BUG] Deleting Function app with resource manager sdk creates zombie app service after a undetermined amount of time

Library name and version
Azure.ResourceManager.AppService  1.0.0
Describe the bug
Getting "websites" from the resource group. and retrieving the correct website to delete
Using the delete async method on the website results in a deleted function app.
however after a little bit of time a new app service (with the same name as the existing one) and a default app service plan appear in the resource group.
All actual config from the existing function app is deleted however the app service remains / is created.
Expected behavior
A function app to be deleted and no remainder existing afterwards
Actual behavior
After a wait usually longer than a couple minutes a app service of the same name and a default app service plan appears ( if not already existing)
Reproduction Steps
`
var subscriptionId = "Fill in"
var resourceGroupName = "Fill in"
var resourceNameToDelete = "Fill in"
        var client = new ArmClient(credential, subscriptionId);

        var resourceGroup = client.GetResourceGroupResource(ResourceGroupResource.CreateResourceIdentifier(subscriptionID, resourceGroupName));

        var websites = resourceGroup.GetWebSites();
        var website = websites.Where(s => s.Data.Name == resourceNameToDelete).First();
        await website.DeleteAsync(WaitUntil.Completed, deleteEmptyServerFarm: false);

`
Environment
Azure AppService.
Windows 10,
Visual Studio Version 17.3.6

Note tested this function in the Azure portal and the same result exists. so It could be a general azure problem...

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

I'm trying to reproduce this issue, but based on the comment in this issue, I believe this should be a service issue.

I believe this is the case as well ^ have tested through the portal ui and could recreate the same issue. Microsoft support was very unhelpful so in the end we gave up on building what we needed

This issue is related to the service side and not the SDK side, so we are not able to help you with it. Therefore, we are closing this issue for now. If you need more assistance, please open an Azure support request. We apologize for any inconvenience this may cause you.
We value your feedback and we want to make sure that your problem is solved. If you think that we have misunderstood your issue or closed it incorrectly, please feel free to comment on this thread and reopen the issue. We will be happy to assist you further. Thank you for your understanding and cooperation.


Instrumentation doesn't work (not inserted before op)

I found instrumentation does not work well after this commit 1081a5e8b9a7b7f70fc94ef60e56743afe716265 .
In following example, krnl.runtime_instrument should be inserted before and after onnx.Add op as shown in expected results below, but after the commit, inserted only after the op. The command for reproducing this is onnx-mlir  --printIR --EmitMLIR --instrument-onnx-ops=ALL --InstrumentBeforeOp --InstrumentAfterOp --InstrumentReportTime <following example>
It seems instrumentBefore in this line https://github.com/onnx/onnx-mlir/blob/main/src/Transform/ONNX/InstrumentONNXPass.cpp#L138 is not correct, but I'm still not sure the exact reason. (If I commented out this line, krnl.runtime_instrument is inserted also before the op)
Hi, @manbearian
You are author of this PR https://github.com/onnx/onnx-mlir/pull/1363 . I will continue to investigate this, but can you check this as well ?
func @test_instrument_add_onnx(%arg0 : tensor<10x10xf32>, %arg1 : tensor<10x10xf32>) -> tensor<*xf32> {
  %0 = "onnx.Add"(%arg0, %arg1) : (tensor<10x10xf32>, tensor<10x10xf32>) -> tensor<*xf32>
  "std.return"(%0) : (tensor<*xf32>) -> ()
}

Result

  func @test_instrument_add_onnx(%arg0: memref<10x10xf32>, %arg1: memref<10x10xf32>) -> memref<10x10xf32> {
    %0 = memref.alloc() {alignment = 16 : i64} : memref<10x10xf32>
    affine.for %arg2 = 0 to 10 {
      affine.for %arg3 = 0 to 10 {
        %1 = affine.load %arg0[%arg2, %arg3] : memref<10x10xf32>
        %2 = affine.load %arg1[%arg2, %arg3] : memref<10x10xf32>
        %3 = arith.addf %1, %2 : f32
        affine.store %3, %0[%arg2, %arg3] : memref<10x10xf32>
      }
    }
    "krnl.runtime_instrument"() {opID =<PHONE_NUMBER>299159040 : i64, tag = 14 : i64} : () -> ()
    return %0 : memref<10x10xf32>
  }

Expected result: Insert two krnl.runtime_instrument before and after onnx.Add op.

 func @test_instrument_add_onnx(%arg0: memref<10x10xf32>, %arg1: memref<10x10xf32>) -> memref<10x10xf32> {
    "krnl.runtime_instrument"() {opID =<PHONE_NUMBER>299159040 : i64, tag = 13 : i64} : () -> ()
    %0 = memref.alloc() {alignment = 16 : i64} : memref<10x10xf32>
    affine.for %arg2 = 0 to 10 {
      affine.for %arg3 = 0 to 10 {
        %1 = affine.load %arg0[%arg2, %arg3] : memref<10x10xf32>
        %2 = affine.load %arg1[%arg2, %arg3] : memref<10x10xf32>
        %3 = arith.addf %1, %2 : f32
        affine.store %3, %0[%arg2, %arg3] : memref<10x10xf32>
      }
    }
    "krnl.runtime_instrument"() {opID =<PHONE_NUMBER>299159040 : i64, tag = 14 : i64} : () -> ()
    return %0 : memref<10x10xf32>
  }

I think InstrumentONNXPass.cpp#L72-L75) should be updated as follows. I will create PR for this.
    this->instrumentBefore = actions & (1 << onnx_mlir::InstrumentBeforeOp);
    this->instrumentAfter = actions & (1 << onnx_mlir::InstrumentAfterOp);
    this->reportTime = actions & (1 << onnx_mlir::InstrumentReportTime);
    this->reportMemory = actions & (1 << onnx_mlir::InstrumentReportMemory);

I think InstrumentONNXPass.cpp#L72-L75) should be updated as follows. I will create PR for this.
    this->instrumentBefore = actions & (1 << onnx_mlir::InstrumentBeforeOp);
    this->instrumentAfter = actions & (1 << onnx_mlir::InstrumentAfterOp);
    this->reportTime = actions & (1 << onnx_mlir::InstrumentReportTime);
    this->reportMemory = actions & (1 << onnx_mlir::InstrumentReportMemory);

Yes, the values in the enum are shift amounts, not the actual bit values.
This is brain-fart on my part when writing the code.
Would be good to add some tests for this to avoid similar bugs/regressions in the future.

Would be good to add some tests for this to avoid similar bugs/regressions in the future

would a lit test catch this?

@manbearian Thanks for your comments!
@AlexandreEichenberger Yes. The lit test in PR https://github.com/onnx/onnx-mlir/pull/1601 catches this. The first krnl.runtime_instrument()  is not output in the current main, but will be fixed by PR1601.


Fixing the number of times our unit tests are run

Fix as per discussion in https://github.com/GoogleCloudPlatform/kubernetes/pull/5707#discussion_r30097801.
Right now our unit tests are running 3 times when run locally and 4 times when run on shippable or travis.
This fix brings back that number to 2 everywhere.

cc @lavalamp

LGTM

Shippable bug fixed. Both travis and shippable are finally green!!
Can I haz a merge, please?

Reviewing now


feature-request: cross-browser height function

hmm. you mean like $("...").height()?

Yup, exactly.
—
@tjmehta
On Tue, Apr 21, 2015 at 11:00 AM, Rico Sta. Cruz<EMAIL_ADDRESS>wrote:

hmm. you mean like $("...").height()?
Reply to this email directly or view it on GitHub:
https://github.com/rstacruz/dom101/issues/1#issuecomment-94890286


Using dynamic variables in live mode for UI steps - to investigate

Found a bug as above. Minimum replication cases -
a = 'element_identifier'
click `a`
..
// returns cannot find element_identifier

b = 'element_identifier.png'
click `b`
// returns cannot find element_identifier.png

(check_tx(params)) will be evaluated immediately instead of being passed as string for evaluation by eval(), thus the dynamic variable string combination won't be formed correctly.
The same for (is_sikuli(params)) and call_sikuli(abs_intent,abs_params) which are designed for processing steps directly instead of passing through eval().
Solution might be to do an eval("'" + params + "'") before using params to check if the element specified by variable exists, and subsequently uses that in the call_sikuli() call.
Consideration will be making sure the fix does not compromise existing uses cases / scripts.

The cause of the bug is due to changes made in https://github.com/kelaberetiv/TagUI/issues/465 where various special characters are escaped in order for them to usable in live mode. However, as single ' is now escaped, it is not working as originally intended to process the dynamic variables correctly.
To figure out if there is a way to have both features working. This was missed as there is limited resource for the project, and automated test is focused on translation to correct positive test cases of TagUI steps (in src/test folder positive_test and positive_test.signature).
And live mode does not have such tests developed.

Solution found - using a placeholder for single quote ' in parse_variables in tagui_header.js.
For example [SINGLE_QUOTE_FOR_VARIABLE_HANDLING]. And then convert this placeholder back to ' in escape_bs() in tagui_header.js. This will ensure that single quotes added for dynamic variable evaluation will not be escaped and ended up being treated as a \', which renders the variable evaluation invalid.
Preliminary tests seems ok, to do further tests before committing.

Secondary testing is ok. Going to commit.

PR for fix committed and available from cutting edge version - https://github.com/kelaberetiv/TagUI#set-up


Update ReadMe.md

added CV to file

Nice work!
Please take a screenshot of the merged PR and upload it to Google Classroom!


Added GitHub links and removed extra code

Pull Request
Description
Added GitHub links and removed extra code
Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
I've used the code to create a draft email and it's working properly.
The link "https://raw.githubusercontent.com/keploy/student-program/main/assets/bottom.png" will be working once this PR gets merged
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings
[x] I have tagged the reviewers in a comment below incase my pull request is ready for a review
[ ] I have signed the commit message to agree to Developer Certificate of Origin (DCO) (to certify that you wrote or otherwise have the right to submit your contribution to the project.) by adding "--signoff" to my git commit command.

@nehagup please review the code.
The link "https://raw.githubusercontent.com/keploy/student-program/main/assets/bottom.png" is currently broken, but it will start working once this PR gets merged :)


Is there a tf-serving document updated for tf2 ?

URL(s) with the issue:
Please provide a link to the documentation entry, for example:
https://www.tensorflow.org/tfx/serving/serving_advanced
Description of issue (what needs changing):
This documment use tf1 function , Is there a new version for tf2 ?

@DachuanZhao Please post this issue here as this issue is more suited to Tensorflow serving not here. Thanks!

@DachuanZhao Please post this issue here as this issue is more suited to Tensorflow serving not here. Thanks!

ok ，I will close this issue .


[Core] Verify test Generation in both autorest.csharp upgrading pipeline of sdk repo and Autorest.CSharp itself

This is not a feature-request, but it's for asking opinion from Azure Core and EngSys team that whether I can start to work on these features :)
API Change Needed
No
Background and motivation
Background
Right now, there is test generation feature in mgmt autorest.CSharp. The generated tests can be seen at https://github.com/Azure/autorest.csharp/tree/d6dd66df44128e4c7b09025e1debd824e2482468/test/TestProjects/MgmtKeyvault/tests/Generated/Mock
Currently these generated tests are mock tests that can be execute under the mock-service-host(https://github.com/Azure/azure-sdk-tools/tree/main/tools/mock-service-host). And meanwhile, we are in the procedure to generate live test based on swagger api scenario (https://github.com/Azure/azure-rest-api-specs/tree/main/documentation/api-scenario).
Motivation
We want the test Generation feature can be verified in 1) sdk repo when upgrading autorest.CSharp & 2) autorest.csharp TestProjects.
API / Feature Proposal
Feature1: verify Test Generation in SDK repo when upgrading autorest.CSharp
The "dotnet build /t:GenerateTest" has been supported in Autorest.CSharp, we want it's invoked in autorest.CSharp pipeline for all released Packages just like that now we are using "dotnet build /t:GenerateCode" to verify generated source code. (There is flag to control whether we enabled testGeneration for a single RP)
Feature 2: verify Test Generation result in TestProjects in Autorest.CSharp
We want to create some testProjects in AutorestCSharp which can verify generated api-scenario test.  Since there will be ARM-Template invocations in generated test, we come up two options to make these testProjects compilable in autorest.CSharp:

option 1: adding Faked Azure.ResourceManager.Resources and TestFramework classes in Autorest.CSharp, like we did here https://github.com/Azure/autorest.csharp/tree/feature/v3/src/assets/TestFramework
option 2: Release TestFramework into nuget, and adding real Azure.ResourceManager.Resources and TestFramework as dependencies of Autorest.CSharp. Since these packages in turn depend on Autorest.CSharp, there may be potential cyclic dependency issues doing this.

Would you please share your opinion on Feature1 and which option should I go for Feature2? Thanks!
Time Constraints and Dependencies
Sooner is better.
Stakeholders
@m-nash , @ArcturusZhang, @ArthurMa1978 , @lirenhe

Hi @jsquire and reviewers,
Allow me to clarify that this  actually is not a feature-request, but it's for asking opinion from Azure Core and EngSys team. I will start these work if you think they are good ideas (may need help on TestFramework part).
The two features are ideas I comes up together with @m-nash and @ArcturusZhang.
Since the Feature1 is adding feature in SDK pipeline and Feature2 is common part of Autorest.CSharp, we want to ask your opinion that whether these are right direction.
Looking forward to any suggestions. Thanks.

Thank you for the clarification, @changlong-liu.    I've reclassified and reached out to stakeholders for discussion.

A few questions:
Feature 1:

In the SDK repo, the generated code validation is to ensure that generated code is not out of sync with the referenced swagger. Could you explain what the value of this is for test code?

Feature 2:

Could you clarify what we intend to validate with these tests specifically? In the current form, they appear to just validate that the various API calls don't throw.
Should these mock tests be marked with the RecordedTest attribute and inherit from RecordedTestBase? I'd expect mock tests to not be recorded.

If yes, is it intentional that the tests are hard coded to Record mode?

nits:
I believe ServicePointManager.ServerCertificateValidationCallback only applies to full framework. Also, you may want to look at HttpPipelineTransportOptions

Hi @christothes , thanks for taking look at the test generation.
Below are my thinking:
Feature 1:

Adding test validation to SDK repo can ensure the generated test are good in new autorest.CSharp for all released packages.

Both Feature1 and Feature2 intend to prevent the test generation from falling behind the source code generation. While Feature1 provide full coverage on released package, and Feature2 provide short development circle with TestProjects.
Feature2:

Yes, currently it is mainly for validating that the serialization and deserialization don't throw.  And since these test are generated with swagger examples and api scenario, we potentially can add response asserts in these generated tests.
With RecordedTest, these mock test can be executed in pipeline without a mock-service-host started in pipeline. And we have code to execute mock test in Playback mode when mock-service-host can't be found https://github.com/Azure/azure-sdk-for-net/blob/main/common/ManagementTestShared/Redesign/MockTestBase.cs#L18.

I believe ServicePointManager.ServerCertificateValidationCallback only applies to full framework....

Thank you, Christopher! That's exactly as your said, the HttpPipelineTransportOptions will really help!


Flag --incompatible_disable_starlark_host_transitions will break rules_scala in Bazel 7.0

Flipping this incompatible flag is failing for the Bazel IntelliJ plugin project because of its dependency on rules_scala. The error is:
ERROR: Traceback (most recent call last):
	File "_/external/io_bazel_rules_scala/scala/private/common_attributes.bzl", line 71, column 56, in <toplevel>
		"_code_coverage_instrumentation_worker": attr.label(
Error in label: 'cfg = "host"' is deprecated and should no longer be used. Please use 'cfg = "exec"' instead.
ERROR: Error computing the main repository mapping: at _/external/io_bazel_rules_scala/scala/scala.bzl:34:5: at _/external/io_bazel_rules_scala/scala/private/rules/scala_test.bzl:5:5: initialization of module 'scala/private/common_attributes.bzl' failed

The flag is documented here: https://github.com/bazelbuild/bazel/issues/17032.
More details and references listed here: https://github.com/bazelbuild/intellij/issues/4211

Thanks, @mai93, for reminding!


SIMPLYE-261 - Municipality and consortium management

Description
Goal

Possibility to customize lanes for each Kimppa (aka consortium)
All Kimppas share the same collections, i.e.:
-> License pools shared between all Kimppas
-> All patrons will have access to the same works regardless of Kimppa
Easy handling for municipality and Kimppa data and mapping. Mapping done based on municipality code received during sign in.

Available data

Municipality code for patron and admin during authentication
Two 3rd party APIs:

Kirkanta, https://api.kirjastot.fi/

Provides list of cities and Kimppas

Kansallinen koodistopalvelu, https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=362&versionKey=440

Provides list of municipality codes and names. The authentication system uses these codes to define the users' municipality

Solution

One library per Kimppa (+ default library) configured in circulation

Each library configured with list of member municipalities

Patrons and admins automatically assigned to library during sign in
Unauthenticated users will see the default library lanes
Collections defined for default library apply to all other libraries
New monitor script (ekirjasto_consortium_monitor) to automatically keep libraries (i.e. Kimppas) synced with Kirkanta data

Other notes

No database changes needed
No changes to authorization logic for list/lane management
Some municipalities don't belong to a Kimppa
Users with "turvakielto" have municipality code 000, i.e. they won't belong to any Kimppa

Motivation and Context
https://docs.google.com/document/d/1oq9_YBgfY5JMh_zDROZyDHts5FZfH_PQ1FRz1IVxv-k/edit#heading=h.y5cwsxdy2zq5
https://jira.lingsoft.fi/browse/SIMPLYE-261 - Prepare the data foundation to handle municipality and library patron info
https://jira.lingsoft.fi/browse/SIMPLYE-262 - Implement the mapping between municipalities and libraries
https://jira.lingsoft.fi/browse/SIMPLYE-263 - Implement custom lane management for local librarians
Checklist

[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.

Some updated information:

Municipalities without a kimppa should be set into their own 1-municipality kimppa.
Patrons with turvakielto should not get access to the service at the moment. Loikka is expected to handle that aspect, as well as patrons from municipalities not taking part in the E-kirjasto service.

@sylvain-degeilh-lingsoft, thanks for the update!

Municipalities without a Kimppa should be set into their own 1-municipality kimppa.

This one is already supported, as we can manage a library for those municipalities manually, without automatic sync. If needed, can be automated further with a separate PR.


Make layout rounding more resilient to floating point errors.

What does the pull request do?
If the value passed to LayoutHelper.RoundLayoutValueUp has a floating point precision error (e.g. 79.333333333333343 in the test case) then when it's multiplied by dpiScale and rounded up, it will be rounded up to the a value one greater than it should be, causing #8866. Fix this by rounding the input value to an arbitrary 8 decimal places.
Also fixes what I assume is a copypasta in BorderRenderHelper that caused #8867,
Fixed issues
Fixes #8866
Fixes #8867

You can test this PR using the following package version. 11.0.999-cibuild0023535-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0023633-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]


JBallerina sprint - Week 09 - 2019

BIR Model

[x] Support for import packages in BIR

[x] #13986 Import module declarations in BIR
[x] #14026 Module resolution capability to JVM Codegen

[ ] Type def support in BIR (record, object , union type, public type alias)
[ ] Global variables support in BIR

[ ] Strand Implementation

Values and types

[x] Iterator design
[ ] Futures design
[ ] Channels design
[x] Tables design
[] "map" and "array" implementation

[x] https://github.com/ballerina-platform/ballerina-lang/pull/14039
[x] https://github.com/ballerina-platform/ballerina-lang/pull/14031
[x] https://github.com/ballerina-platform/ballerina-lang/pull/14077
[x] https://github.com/ballerina-platform/ballerina-lang/pull/14071

Error handling Design

[x] Error Type and values, Trap, Panic and Stacktrace

[x]  #13882 JVM stdlib refactor

Compile ballerina modules to .jar

[x] #14036 Update build command to build modules with jvmTarget flag
[x] Compile imported modules to a single jar

@SupunS @manuranga @lankavitharana @vinok88 @warunalakshitha @sameerajayasoma

Refer this [doc](https://docs.google.com/document/d/1sLrgBLfCQVnzWswg5wXudzbVoiCq1n_oojLVRQnEWjs/edit?usp=sharing for) for values and types designs.


[question] Each program's settings as submodule

Hello!
I have my dotfiles structured, but sometimes I am at new computer and I would just like to install my vim settings in there. As I do not want to download all my dotfiles, I have another git repo for my vim configuration files.
I was wondering if I should do this to all my program configs (i.e. submodule each folder in my ~/.config folder). Am I crazy? Do you think I can integrate this workflow to dotbot? I would really like to know what kind of problems I could be running into for doing that, if you know any of it.
Also, thanks for dotbot! It's amazing to know that my problem was already solved by you. Congratuations!

My two cents (plus tax where applicable)

sometimes I am at new computer and I would just like to install my vim settings in there

When I migrated to dotbot, I faced this problem as well. I have a handful of machines that require their own specific programs and configurations. Even when I start a fresh VM, there are a core set of files that I want: vim, bash, and a few core programs. Someone here, I forget who, and the dotbot docs suggest that you can use different install + install.conf files to manage multiple machine configurations. For me, this became too much to keep track of and also would've created a repo that may have been larger than what I wanted.
So I've followed the advice that @anishathalye uses and has offered to others before. I now have two repos that contain the core/"common" files that I would need on pretty much any machine and a second repo for machine specific files where each machine has its own branch. You could go this route as well. I've even got some of my other repos for scripts and things as submodules so they can be automatically installed on new machines.
Also look into using git clone with the --branch, --depth, --single-branch, and --shallow-submodules options to further reduce the amount data cloned by limiting how much of the history to copy. DISCLAIMER I've only used --branch option before so I don't know how pushing new commits with the additional options will be affected.

I was wondering if I should do this to all my program configs (i.e. submodule each folder in my ~/.config folder)

looks at own ~/.config directory
I've got at least 30 subdirectories. Of those, I'm probably tracking more than I should. They're all relatively small in their own right so managing them as separate submodules would be too much effort. It's easier for me to manage them as separate branches in the machine specific repository and just cherry pick the commits across branches if I needed changes on more than one machine.

Without trying to pull the "greybeard card", I've been maintaining my config files in some form of SCM since long before dotbot, and well before git even (anyone remember rcs?), which is to say I've tried a lot of different approaches, and in the end, I've always reverted back to additional host- or distro-specific conditional configuration blocks into my shell config files (e.g. if [[ $(hostname) == foobar ]]) and host- or distro-specific versions of config files for things like tmux (e.g. ~/.tmux-{linux,darwin}).
Why?  In the end, I found it was easier to maintain cross-platform similarity by using conditional blocks or alternative versions of files loaded only in certain cases than to maintain multiple repositories.  Inevitably, I would find something I wanted on one system that I forgot to copy over from another, so back to a single source for all platforms/hosts.  This has worked well for me while simultaneously working on Linux, Solaris, Windows (cygwin or wsl), and MacOS.
For example in my current dotbot.yml, I have:
    ~/.gitconfig-local:
      path: ~/.gitconfig-${DBOT_TARGET_DISTRO}
      if: '[ -n "$DBOT_TARGET_DISTRO" ]'

And then in my ~/.gitconfig, I can simply:
[include]
  path = ~/.gitaliases
  path = ~/.gitconfig-local

Note that to make that work, I set `` in my wrapper script around dotbot:
# This variable is used in the `dotbot.yml`.  If not set, default to `uname`:
export DBOT_TARGET_DISTRO=${DBOT_TARGET_DISTRO:-$(uname | tr '[A-Z]' '[a-z]')}

Thank you, @etkeys and @eengstrom! Your experiences are really valuable to me. I am sure I'm studying those git commands I am currently not aware of, @etkeys. They will surely be useful to my workflow. I believe I am mainly implementing @eengstrom's solution. I started doing part of it today, and it was pretty easy to follow in that direction. I also did not know I could use environment variables inside the yaml so easily. Awesome, guys!

Personally, I use a variation on
https://github.com/anishathalye/dotbot/wiki/Tips-and-Tricks#how-can-i-have-different-groups-of-tasks-for-different-hosts-with-different-configurations - The more complicated option.
It's flexible enough to cover pretty much everything I need


preact backend

All 3 of those are lighter by a wide margin, while maintaing same symantics. 200 kb bundle is no good.

Apparently preact has a layer for compatibility with react.

It should be fairly straightforward to create a new backend as long as it has -

Purescript bindings
A virtual-dom

For libraries that have a virtual-dom already, it's the first part (purescript bindings) which is usually the largest hurdle. Preact is a drop-in replacement for React, so it should be a lot easier to create Purescript bindings for it, if they don't exist already.
Once we have Purescript bindings, I would be happy to help out with any new backend projects, or even build those backends myself.

Nerv is probably a better candidate as it's faster and is compatible first, and preact loses speed with used with compatibility layer.

I'm going to close this, and open an umbrella issue for alternative backends.

Closing this in favor of the umbrella issue.


RP-4 B image creation seems to have failed...

Description
HW: Raspberry Pi 4 B
SW: core-image-base created using kas as mentioned in the README
Build: Suceded, with no errors.
Steps to reproduce the issue:

clone this repo
and run kas build meta-raspberrypi/kas-poky-rpi.yml
Output of images folder

~/work/yocto/build/tmp/deploy/images/raspberrypi4$ ls *.bz2
core-image-base-raspberrypi4-20201216125949.rootfs.tar.bz2  core-image-base-raspberrypi4.tar.bz2
core-image-base-raspberrypi4-20201216125949.rootfs.wic.bz2  core-image-base-raspberrypi4.wic.bz2

Is this the expected outcome of the build?
I copied the *.wic.bz2 to a 16GB SD Card using Balena Etcher, but that doesn't boot.

I am doing something totally wrong here?
Do i need any other additional steps to get a valid image which i can use to boot RP4?

did you create the SD card image, when you mount it on your PC what is the content of the SD card.

did you create the SD card image, when you mount it on your PC what is the content of the SD card.

There is no sdimg created from dunfell branch

I re created the yocto environment from scratch and built the core-image-base.
It looks like the image works only with bmaptool and not with Etcher.
I am closing this issue, thank you for your directions.


[example/nRF5] Fix lighting app typo

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


A Sun port i did on a whim, using the system compiler...

bench32_sun.txt
bench64_sun.txt
Some benchmarks taken on the lone system I own that has AES and AVX in the FPA.
Used the default system compiler (Sun C++ v5.15) for this, and have some local patches in my own repo. Probably of very little general interest, just wanted to post some recent stats.

Seems pretty slow compared to an i7/i9 - what kind of CPU is this?
- Casey

It's an AMD Opteron 6386, Bulldozer core
On July 10, 2019 6:08:15 PM CDT, Casey Muratori<EMAIL_ADDRESS>wrote:

Seems pretty slow compared to an i7/i9 - what kind of CPU is this?
- Casey
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/cmuratori/meow_hash/issues/62#issuecomment-510263733

Oh, OK - that's an old CPU, so that is actually in line with what I would expect (although I haven't profiled Bulldozer CPUs specifically myself).
- Casey


dynamic load module - [closed]

In GitLab by @liyanq528 on Apr 18, 2019, 07:59
Merges dynamic_module -> dev

In GitLab by @wknet123 on Nov 13, 2019, 11:43
closed


trickle-ice case

Case modified for url structure test when iceserver creation.

Make a branch instead of a fork.
Since you made a nice modification of trickle-ice, instead of a brutal copy, you should PR the changes on this page instead of a copy (.../content/peerconnection/trickle-ice/...)
DO NOT push pages that use an adapter local to the repo. EVER. Instead include a version from our CDN. See the include from the original trickle-ice

You created a second pull request, please close this one

OK i will, just found another bug trying to fix and then test the "hascredential" problem.


flight-search-calendar

-Grey out past dates in the calendar and disable them
-The goal is to make only current and future days available for the user to pick.

Done!


Design System Users Research

What
Research into Design System users - those who work in service teams building citizen facing and internal services to understand the context in which they work. Focussing on users who aren’t very experienced in their discipline or those whose use of the Design System is limited through lack of knowledge, limited access or lower digital capability.
Why
The context in which users work greatly affects their ability to access the Design System, learn about how to use it and access support from the community to help them understand how to make the best use of it.
In the absence of any formal Design System training, access to community support is essential for optimal use of the DS. Users learn from each other, seek answers to questions and problems, discuss issues and share examples of work. Community support can be provided by other users in the community, as well as the Design System team. It is something which exists with the encouragement of the Design System team, but is largely external to it.  Users access support through channels such as Slack and GitHub.
Who
User researcher
### Plan research
- [x] Write research plan
- [ ] Book in analysis sessions
- [ ] Book in Show and Tell

### Recruit
- [ ] Recruit participants
- [ ] Gain and record consent
- [ ] Agree and book research sessions

### Research
- [ ] Do interviews
- [ ] Collate findings

### Analyse and Share
- [ ] Analyse
- [ ] Create artefacts
- [ ] Write sharing deck
- [ ] Share insights at Show and Tell

Closed as duplicate of #3730


Map API is not getting configured correctly

Type of issue

[x] Bug
[ ] New feature
[ ] Improvement

Description
My subscription do not have any usage of Map API but still when i try to kick new deployment I get warning that I will need to fix it manually later. I have tried with two different subscriptions I have.
Steps to reproduce

Create a solution with a subscription with less than 2 MAP APIs in use.

Expected behavior
Solution should get created with Map API enabled.

This is fixed since we moved to Azure Maps


Fix crash on isinstance(some_obj, Exception)

isinstance("", Exception)
causes Cython to generate a call to PyException_Check() which does not exist.  I think the correct call is PyExceptionClass_Check().

Thanks for the PR. This isn't quite what we want, PyExceptionClass_Check checks whether this is a type that subclasses Exception, not whether this is an instance of Exception. FWIW PyExceptionInstance_Check isn't right either, as it lets classic instances through (which are OK to raise, but not valid here).
This issue has already been fixed. https://github.com/cython/cython/issues/1496 Hoping to put out a bugfix release once I resolve the CentoOS issue.

Awesome, thanks for letting me know.  We've been pulling our hair out to track this down.. :)
Do you know if you are going to release soon, or do we need to work around the issue?

I hope to release today.
On Wed, Oct 26, 2016 at 10:33 AM, Jerry Seutter<EMAIL_ADDRESS>wrote:

Closed #1501 https://github.com/cython/cython/pull/1501.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cython/cython/pull/1501#event-837424965, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAdqgQf_ZMpdpo0Nz9sSYS42LLNxf8W3ks5q348DgaJpZM4KhaUc
.


Replace user delete API

Right now, we are deleting using the user email address which is inefficient. Instead, we can delete using mongo collection ID.

done, need review


Patch 2

Summary
Fixed the typo in both files
Fixes #30685 (if available)

Hi @BillWagner
I created a small PR with one failed check. I am not able to figure out the issue. I would be thankful if you could help me out here as I am pretty sure it won't take much of your time.
Thanks :)

Hi :wave: @mudassir014
This sample requires Visual Studio for the build. To fix the build error, you need to add a snippets5000.json file to this folder that specifies building with VS.  You can find an example here


Bug 1853601: Retry conflicting catalog source pod update after fetching latest pod spec

Description of the change:
Updating the catalog source pod was intermittently failing due to resource version conflicts. This change retries the update after fetching the latest spec of the catalog source pod.
Motivation for the change:
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /docs
[ ] Commit messages sensible and descriptive

I think we may need to update the object more before patching it, see #1641 for an example of a test with a similar server-side apply that passes locally, but would not patch successfully without the additional metadata.

/retest

/retest

/retest

/hold
Put a hold on this PR temporarily to ensure nothing getting merged into master while the new resolver PR is running CI. Would like to have that PR getting in first.

/hold cancel

This PR failed tests for 1 times with 2 individual failed tests and 4 skipped tests. A test is considered flaky if failed on multiple commits.

totaltestcount: 1
flaketestcount: 2
skippedtestcount: 4
flaketests:

classname: End-to-end
name: 'Subscription creation if not installed'
counts: 3
details:

count: 3
error: |4-
/home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/subscription_e2e_test.go:52

	Error Trace:	subscription_e2e_test.go:59
	            				runner.go:113
	            				runner.go:64
	            				it_node.go:26
	            				spec.go:215
	            				spec.go:138
	            				spec_runner.go:200
	            				spec_runner.go:170
	            				spec_runner.go:66
	            				suite.go:62
	            				ginkgo_dsl.go:226
	            				ginkgo_dsl.go:214
	            				e2e_test.go:54
	Error:      	Received unexpected error:
	            	E2E bug detected: configmaps "mock-ocs" already exists

/home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/vendor/github.com/stretchr/testify/require/require.go:1005

meandurationsec: 0.03773066666666667
classname: End-to-end
name: 'Operator Group cleanup csvs with bad owner operator groups'
counts: 1
details:

count: 1
error: |4-
/home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/operator_groups_e2e_test.go:1800

	Error Trace:	operator_groups_e2e_test.go:2040
	            				runner.go:113
	            				runner.go:64
	            				it_node.go:26
	            				spec.go:215
	            				spec.go:138
	            				spec_runner.go:200
	            				spec_runner.go:170
	            				spec_runner.go:66
	            				suite.go:62
	            				ginkgo_dsl.go:226
	            				ginkgo_dsl.go:214
	            				e2e_test.go:54
	Error:      	Received unexpected error:
	            	timed out waiting for the condition

/home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/vendor/github.com/stretchr/testify/require/require.go:1005

meandurationsec: 614.088057
skippedtests:
classname: End-to-end
name: 'Catalog image update'
counts: 1
details: []
meandurationsec: 0.027671
classname: End-to-end
name: 'Subscription updates existing install plan'
counts: 1
details: []
meandurationsec: 0.465978
classname: End-to-end
name: 'Subscriptions create required objects from Catalogs Given a Namespace
when a CatalogSource is created with a bundle that contains prometheus objects
creating a subscription using the CatalogSource should have created the expected
prometheus objects'
counts: 1
details: []
meandurationsec: 15.307669
classname: End-to-end
name: 'Subscriptions create required objects from Catalogs Given a Namespace
when a CatalogSource is created with a bundle that contains prometheus objects
creating a subscription using the CatalogSource should install the operator
successfully'
counts: 1
details: []
meandurationsec: 9.294765

/retest

/retest

/retest

/retest

/retest

/retest

/lgtm
/test e2e-aws-console-olm

/retest

/retest

/retest

/retest

/retest

/lgtm

/retest

/retest

/lgtm

/retest

/retest

/test e2e-gcp

/test e2e-gcp

/cherry-pick release-4.5

/cherry-pick release-4.4


Refactoring util functions

Changes include:

a get_gcm_grid_spec function to get the definition of the spatial grid for a gcm
change the open_era5 function to handle multiple variables
new file paths.py to store all functions that generate paths for caching/storing
a rechunk_zarr_array_with_caching function that handles multiple variables and caches

@norlandrhagen @orianac a review here would be appreciated, thanks!


use numpy matrices when dense

context: #22
problem: sparse matrices class are slower when the content is dense.
observation: numpy martrices and scipy.parse have almost the same interface
solution: implement the initialisation of matrices such that numpy matrices are used when "type=='dense'"
blocked by #23

follow up: try out different kinds of scipy sparse matrices and find out which are faster under which conditions


Unable to require username AND email for new accounts

I saw an earlier comment that solved this problem #58 - that requires adding fields manually.
Is this still the preferred solution? Or is there a simple option setting for this now?
Great package! Thanks.

Have you had a look at this?

I also tried to setup AccountsTemplates to show both the username and the email. But even if I do it like described here, I still get a combined username and password field. But I want to have both fields separately, since both are needed for my application.


Possibility to open list on save only

ATM this is more a question rather than an issue.
Is it possible to open vim window on save only, and keep loclist error reporting while editing?

You can set g:ale_open_list to 'on_save', if that's what you mean. That might do what you want. See :help g:ale_open_list.


ScreenMetricsChanagedEventArgs(ScreenMetrics) Constructor

I hope that's just a typo, but I'm thinking maybe not. Unfortunate.
https://docs.microsoft.com/en-us/dotnet/api/xamarin.essentials.screenmetricschanagedeventargs

@Pooglz Can you clarify your issue? Is there something wrong with the content?

"Chanaged" everywhere should be "Changed"

@Pooglz Thanks for your feedback. I submitted a PR to correct it.


Uncaught TypeError: Cannot read properties of undefined (reading 'bun')

Environment
browser, edge
Reproduction
Upgrading from 3.3.3 to 3.4.2
Describe the bug
After upgrading from 3.3.3 to 3.4.2 I get this error upon starting the nuxt app:
Uncaught TypeError: Cannot read properties of undefined (reading 'bun') at index.mjs:1:2785
Reverting back to 3.3.3: no issues anymore
Additional context
No response
Logs
No response

Thanks for report. Should be solved in 3.4.3

Wow, that's what I call lightspeed! Many thanks


Critical Action Button in Web Components

can you add a link to the specs when they are ready? my team may have availability to work on this @enowak1031

Hey @ryan-henness-trimble Please refer to https://docs.google.com/document/d/1fdoD60sLyEywfnXk_zpGlCeR5ZAUGKEVS6TU4UR9Xx8/edit for the specs
please correct me if it is not the correct document @enowak1031

@ryan-henness-trimble is your team planning to work on this issue?

Follow the specs from https://docs.google.com/document/d/1fdoD60sLyEywfnXk_zpGlCeR5ZAUGKEVS6TU4UR9Xx8/edit and the styleguide.

@ryan-henness-trimble is your team planning to work on this issue?

Our availability is low at the moment - we won't plan on taking this one on

@ryan-henness-trimble We are in the process of planning out when we'll tackle it 👍

Create a new property on the modus button which adds the press/hold/progress indicator as described for the critical action button.  Just like Danger and Special, we will call out this variant as Critical Action Button, which is specifically a Danger button with this property set to true. We won't implement this property if the color isn't set to danger.  That is something that can be added later if a strong need is brought up. We should make it clear in the writeup that this property only affects danger buttons.

Accessibility Report: I raised concern about including this before but this 'hold down button' paradigm is not accessible and I don't think this PR should be merged.

Right now holding down the button does nothing on an iPad.
The action is not announced to screen readers
The long-press action is already in use on Windows with touch screens and works everywhere, including web browsers. The effect of executing custom action on long press can be therefore unpredictable and it could depend on the operating system and/or browser.

Unless you have some solid workaround of this problem, you should not ignore this shortcoming, especially when designing web UI, which is expected to be platform independent. Without solid workaround available, I would categorize the severity of this problem as a stopper.
Long-pressing a button isn't a known action on web for desktops, it simply doesn't exist and you won't see it in other style guides.
Instead, please consider asking the user to confirm the action again. Smashing Magazine posted an excellent article 'How To Manage Dangerous Actions In User Interfaces' last week with ideas:
https://www.smashingmagazine.com/2024/09/how-manage-dangerous-actions-user-interfaces/

@coliff I think we should add the button and add a warning label both in Storybook and on the style guide that it might not be accessible. I created a separate issue to address this: #2961


androidx migrated release

Hi, would it possible to create a release with the current androidx migrated code?
Due to restrictions by F-Droid we (https://github.com/MarcusWolschon/osmeditor4android/) can only include dependencies that are published on one of the major binaries repos, so without a release I have to fork the project and publish it myself, which is a royal PITA and a waste of time.
Thank you for your consideration.

Hi, I can try but not earlier than that Saturday. I accept PRs though.
On Thu, Mar 26, 2020, 10:36 Simon Poole<EMAIL_ADDRESS>wrote:

Hi, would it possible to create a release with the current androidx
migrated code?
Due to restrictions by F-Droid we (
https://github.com/MarcusWolschon/osmeditor4android/) can only include
dependencies that are published on one of the major binaries repos, so
without a release I have to fork the project and publish it myself, which
is a royal PITA and a waste of time.
Thank you for your consideration.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sevar83/indeterminate-checkbox/issues/10, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA5FVJOZD6VWPFADNRJTZTRJMH2HANCNFSM4LUBTSPQ
.

No problem, I didn't want to indicate that you had to hurry. We've just started with the migration, and while it "in principle" works with the "jetifier" it would be nice to to have to rely on it. Thanks.

bump?

I think this repo is dead, I would suggest checking out https://github.com/topjohnwu/indeterminate-checkbox,
he forked it and updated everything.

@cyb3rko unluckily the fork requires switching themes, which is something that is not planned short term for our project,

fyi I'm now using this in my build.gradle: implementation 'com.github.sevar83:indeterminate-checkbox:965fdc7c20'
This just takes the library built from the currently latest commit on master (965fdc7c20)

fyi I'm now using this in my build.gradle: implementation 'com.github.sevar83:indeterminate-checkbox:965fdc7c20'
This just takes the library built from the currently latest commit on master (965fdc7c20)

fyi I'm now using this in my build.gradle: implementation 'com.github.sevar83:indeterminate-checkbox:965fdc7c20'
This just takes the library built from the currently latest commit on master (965fdc7)

The question is if f-droid would accept that, typically they want libs from well known binary repos.

fyi I'm now using this in my build.gradle: implementation 'com.github.sevar83:indeterminate-checkbox:965fdc7c20'
This just takes the library built from the currently latest commit on master (965fdc7)

The question is if f-droid would accept that, typically they want libs from well known binary repos.

The question is if f-droid would accept that, typically they want libs from well known binary repos.

The service is provided by JitPack link to master snapshot description, so I think it should work.

The question is if f-droid would accept that, typically they want libs from well known binary repos.

The service is provided by JitPack link to master snapshot description, so I think it should work.


Add xfsprogs to v1.6 Kubernetes image

Rancher versions:
rancher/server: v1.6.21
Ability to use XFS requires XFS binaries in rancher/k8s image. In 2.x those are already included.

Tested with v1.6.22-rc3. Created a Kubernetes setup. From the Kubelet container shell observed that xfs is installed.
root@soumyak8s16test3:/# apt list --installed|grep xfs

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

xfsprogs/now 4.3.0+nmu1ubuntu1.1 amd64 [installed,local]
root@soumyak8s16test3:/# xfs_
xfs_admin      xfs_copy       xfs_estimate   xfs_fsr        xfs_info       xfs_logprint   xfs_metadump   xfs_ncheck     xfs_repair
xfs_bmap       xfs_db         xfs_freeze     xfs_growfs     xfs_io         xfs_mdrestore  xfs_mkfile     xfs_quota      xfs_rtcp


IP addresses in mixer logs are not readable

Describe the bug
IP addresses in mixer logs are not readable. (Not Envoy logs)
Examples:
sourceIp:	 CjQpPQ==
destinationIp:	 AAAAAAAAAAAAAP//CjRD8w==
Istio config resources are defaults as provided by helm charts.
For example this is still present:
apiVersion: config.istio.io/v1alpha2
kind: logentry
metadata:
  name: accesslog
  namespace: istio-system
spec:
  variables:
    sourceIp: source.ip | ip("<IP_ADDRESS>")
    destinationIp: destination.ip | ip("<IP_ADDRESS>")
    <...>

Expected behavior
I expected to see the string representation of the IP Address.
Steps to reproduce the bug
Run any workloads on the mesh. View the mixer access logs.
Version
Istio 1.1.0
Kubernetes v1.11.6-gke.2
Installation
helm template + (some processing of yaml) + kubectl apply
Environment
GKE

cc @gargnupur

The fix is not there in release 1.1 but we will try to include it in patch release of 1.1
https://github.com/istio/istio/pull/12502

Oh bummer

I'm going to close this issue, as the fix is in master and release-1.1 and will be part of the 1.1.2 release, scheduled for release on 4/1/2019.

@douglas-reid: I think this is not fixed completely.. It is fixed in stackdriver adapter but for the issue reported here, it should be fixed in stdio adapter too... I will work on a fix for that...

PR in review for fix in stdio adapter: https://github.com/istio/istio/pull/12850#issuecomment-477329496

Closing as fix is in master and release-1.1 now and will be a part of 1.1.3 release.

ETA for 1.1.3 is 4/15


Conflicting CTRL Key

Reproduce:

Open terminal
Do anything and close/exit terminal
Press CTRL -> Terminal opens
Loss in sales revenue

Please, do not ever use CTRL to open up the pop-up command menu. Whenever I press CTRL, it opens up the terminal and often inhibits keybindings, especially splitting tabs and copy pasterino.
EDIT: only way to stop it is to close the terminal through ESC

:+1:

+1 @isis97  Any update on this! ?

I found a way to change this (probably not intended way)
Here is a visual aid: http://i.imgur.com/Pv4tsWW.png
I went in and edited the source code in atom-terminal-panel/keymaps/atp.cson
changed the keymaps to something other then just ctrl
saved and closed atom editor and opened it again
This seams to remap these keybindings to whatever you want, I don't know if atom has some sort of intended way to remap these though, I know this is not an ideal solution.

I just found this as well.
However, only after pressing the exit button, not after pressing the close button.
I guess the command that waits for toggle-autocompletion is left over after exit is triggered, but not after close?

This is really becoming a major nuisance to me. Every time after using the panel once, the likelihood that the terminal keeps coming up every time I press Ctrl is close to 100%.
It's an awesome package, but this is like the Coolaid man breaking through the wall three times per minute while I am trying to work.
I'd rather not switch to a different terminal package again, so just checking if anybody is working on this?

Hi,
I'm not sure what others see, but the issue persists.
Still the exact same behavior.
Was the new version of the package not published, perhaps?

@batjko Yeah, the changes have been applied to the repository but they haven't been released as a new package version yet.

I just uninstalled and disabled atom-terminal panel. Got really sick of it. Whoever created that package kind of didn't give a daymn about programmer productivity.


INSTALLSTR is always stripped ?

This issue was originally created at: 2008-04-21 04:23:56.
This issue was reported by: cournape.
cournape said at 2008-04-21 04:23:56

Hi,
I noticed a strange behavior with custom strings for the Install builder:

env = Environment(INSTALLSTR = "INSTALL      $SOURCE")

obj = env.Object("youpla.c")
env.Install("youpla", obj)

When run, the INSTALLSTR is taken into account, but the whitespaces are "stripped", and scons displays:

INSTALL youpla.o

Instead of

INSTALL      youpla.o

I did not observe this behavior with any other builders (CC, CXX, FORTRAN, etc... It seems the problem is linked to the fact that Install is not created through the Action(action, actionstring) idiom).

stevenknight said at 2008-05-22 09:48:07

Target milestone and reassign per bug party triage.
Greg to investigate whether this behavior is consistent with other Builders.  If not, it may be a simple matter of performing a raw (white-space preserving) substitution on the string.

gregnoel said at 2009-03-05 17:43:46

Issue #1123 and issue #2018 are variants of the same basic problem, which would be solved when https://scons.org/wiki/SubstQuoteEscapeCache is implemented.  Suggest 2.x p3 +subst draft choice.

gregnoel said at 2009-03-19 00:26:16

Bug party triage.  Collect issues involving substitution or quoting problems under a "subst" keyword.

Changing the way strFunc in install.py calls the subst package does allow it not to strip spaces, and thus can address this issue. However, is that what we want?  After suitable import statement:
     if installstr:
-        return env.subst_target_source(installstr, 0, target, source)
+        return env.subst_target_source(installstr, SUBST_RAW, target, source)

That would match the default strFunction() in Action.py for CommandAction().
I think that's reasonable!


vm-operator pod failed to start due to error parsing Kubernetes version

vm-operator pod cannot start because Kubernetes version is not type on int
here's log error message from pod
"msg":"cannot setup manager","error":"cannot set kubernetes server version: cannot parse kubernetes server minor version: \"20+\" as uint: strconv.ParseUint: parsing \"20+\": invalid syntax","stacktrace":"main.main\n\t./main.go:43\nruntime.main\n\truntime/proc.go:255
and this is output from kubectl version command
erver Version: version.Info{Major:"1", Minor:"20+", GitVersion:"v1.20.12-gke.1500", GitCommit:"d32c0db9a3ccd0ac73b0b3abd0532505217b376e", GitTreeState:"clean", BuildDate:"2021-11-17T09:30:02Z", GoVersion:"go1.15.15b5", Compiler:"gc", Platform:"linux/amd64"}

Hello, can you try to upgrade operator  to the v.0.23.2+ version? It contains needed fix.

worked for me thank you!


Version the API

Add a version prefix to the routes for API stability and ease of upgradability.
Consumers of the API may also like to be able to inspect an endpoint for supported versions.
Suggestion brought up during the EthereumJS team retreat. @ricmoo

Closing in favor of #28
thanks!


[Edit projects][UI]

Break edit/update wizard into multiple forms. Add 'Next' button to move between cards. Attach separate 'submit' functions to each next button

Add a change event to each 'Card' which triggers when an input is changes and shows a 'Save Changes' button?

Moving this to a later sprint as it will roll into the new UI styles.


Create oelint-adv.yml

The tool looks good, but we maintain tags in https://github.com/analysis-tools-dev/static-analysis/blob/master/data/tags.yml and only create new ones if we have more than one tool per tag. This is to avoid having too many relatively empty tags. Are there any existing tags where oelint would be a good fit? Alternatively, do you know any other tools that would fit for one or more of the added tags?
If the answer to these two questions is no, then I'd be fine with adding a more general embedded tag.

@mre unfortunately there isn't much tooling around in this area - so I'm okay with your suggestion and have added that to the tag list

Thanks, looks good to me. 😊


Set CUDA context before loading NVRTC kernels

I've come across an esoteric runtime failure in some of my runs:
RuntimeError: /tmp/pip-req-build-z55m7lkv/transformer_engine/common/util/rtc.cpp:114 in function operator(): CUDA Error: invalid device context

Under specific conditions, the CUDA context is not set in non-main threads (e.g. the PyTorch autograd thread) before we compile NVRTC kernels and load them to the device. I haven't fully figured out what triggered this edge case, although it seems related to https://github.com/NVIDIA/NeMo/pull/8030. This change fixes the runtime error for me though.

/te-ci

/te-ci

/te-ci

The test failures were retriggered and passed. Merging.


Hide the time picker

The time picker is not relevant to this app. When the SDK supports it, hide it.

This has landed in the SDK, we can now:
import { nerdlet } from 'nr1'

nerdlet.setConfig({ timePicker: false });


Fix bug with metadata-type not work since 2.7.5 describe in issue #5667

What is the purpose of the change
Fix bug with metadata-type not work since 2.7.5 describe in issue #5667
Brief changelog

Add METADATA_TYPE_KEY in CommonConstants
When getting WritableMetadataService, "metadata-type" and "metadata" are both supported for compatible.

Verifying this change

Before this PR, the following config does not work
<dubbo:application name="demo-provider" metadata-type="remote"/>
After this PR, metadata are published to metadata center.

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

Well.


Add automerge action

Add automerge action to automatically merge pull requests.

Apparently it doesn't do what I was looking for. Sad.


chore(deps): update

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Fix reveal output change

Fix  #130
Test: run yarn cli mint-nft 1.txt --satsbyte 1  and transfer 0.00002000 tBTC

Before the fix:

All the extra sats were paid to the miner
https://mempool.space/testnet/tx/5f043edf705dba9e88b80e48e0c9461298efd61845183edae148578e85133273

After the fix:

Fee rate is 1 and the remaining sats are sent to the funding address
https://mempool.space/testnet/tx/e534158a0f7d9ab7bd1b0e52ed54c9e42a7e52f2656ce1658f4d91dc03df8bc3

Please rebase and submit again

Please rebase and submit again

Done. And I also try to fix #153 since this issue makes me unable to test my code.
I tested with https://mempool.space/testnet/tx/6bd038f356e970c5cdc649e7d9b84a7320e0f4d3a5ca37b6fb21686f78e81ac1
Please review them @atomicals

Please rebase and submit again

Please rebase and submit again

Done

@atomicals Please review

Can you please check if this still needed and rebase if needed?

@atomicals  is still needed, and I've done a rebase.

Before fix: all extra sats burn: https://mempool.space/testnet/tx/476b48dcf816cc2bcd5f6f7abdb6a5ad65cb2ccf0b1c773101786dee5518fa4f
After fix:  a change is added:
https://mempool.space/testnet/tx/5adfb1e24247a2304c837c3d2b9e12e4d8648dc1be47c2e3969a17f8c8a62d3b


Align JSR NPM package tarball paths with registry.npmjs.org

Some private registries require that upstreams have an identical tarball path layout as the upstream NPM registry. JSR does not currently do this, which means JSR is unable to be used as an upstream for these private registries.
This is known to affect Google Artifact Registry and JFrog Artifactory.

Is this something that is supported with demo 2.0?
I'd love to try it out but I need to be able to use artifactory as the registry to proxy/cache dependencies so we don't get rate limited.


[IMPROVEMENT] [BACKPORT] [v1.2.5] Prevent PVC provisioning if there is insufficent storage

What's the test to develop? Please describe
https://github.com/longhorn/longhorn/issues/3529
Additional context
Add any other context or screenshots about the test request here.

@mantissahz Please help verify this fix. Thank you.

Verified Passed on v1.2.x-head by:
1.a. Disable scheduling on all nodes
1.b. Create a volume on UI
1.c. Create PV/PVC for the volume
1.d. Check the PV annotation "longhorn.io/volume-scheduling-error: nodes are unavailable"
2.a. Disable all disks and on all nodes
2.b. Create a volume on UI
2.c. Create PV/PVC for the volume
2.d. Check the PV annotation "longhorn.io/volume-scheduling-error: disks are not available"
3.a. Create a volume on UI. The request size exceeds the disk available size.
3.b. Create PV/PVC for the volume
3.c. Check the PV annotation "longhorn.io/volume-scheduling-error: insufficient storage"
Create the volume by two methods:

https://github.com/longhorn/longhorn/blob/v1.2.x/examples/csi/example_pv.yaml
https://github.com/longhorn/longhorn/blob/v1.2.x/examples/pod_with_pvc.yaml


Support stringizing enumerations in C++ layer for describing mapped enumeration

I searched issues but I didn't see anything about stringizing enumeration while generating native C++ sources.
In my case, I need to get the enumerations' description to show to upper layer. I'm not sure that whether there is the same demand for others?
To achieving this, one way is to define the enumeration strings manually, the second way is to stringize enumerations automatically in djinni. In my opinion, the second way is preferred be cause: it can get the string mapped to enum easily, and also, if djinni plans to support metaprogramming, it will be helpful.
For example, defining enum In djinni file:
Version = enum {
    v_1_0;
    v_2_0;
    v_3_0;
}

it will produced C++ hpp:
enum class Version : int {
    V_1_0,
    V_2_0,
    V_3_0,
};

If I want to return the description of certain enumeration, it needs to define a enumeration string table to achieve this:
static const char *VersionStrs[] = {
    "V_1_0",
    "V_2_0",
    "V_3_0",
};

const char *toString(Version v) {
    return VersionStrs[v];
}

But the works above are bored and horrible if there are so many enumerations, so I suggest to auto generating the codes above into enum hpp files, the expected new hpp file for enum:
expected new produced C++ hpp for enum maybe look like:
enum class Version : int {
    V_1_0,
    V_2_0,
    V_3_0,
};

struct VersionHelper {
    static const char *toString(Version v) {
        const static char *__enumStrings[] = {
            "Version::V_1_0",
            "Version::V_2_0",
            "Version::V_3_0",
        };

        return (((int)v) >= (int)(sizeof(__enumStrings)/sizeof(__enumStrings[0])) || ((int)v) < 0) ?
            "INVALID_VALUE" : __enumStrings[(int)v];
    };
};

So is it possible to stringize enumerations automatically in djinn or support it with a djinni compiling option?
thanks~

made pull-request which is solving this issue


Use existingMongoose in buildSchema

Not doing it makes my project with Mongoose v5 crash. The fix can be useful to anybody
that doesn't use Typegoose's mongoose version

This makes Typegoose usable in the frontend without importing Mongoose at all.

LK"I
Hi There,
Can you give example on how to your typegoose Models with the frontend??

You can't. The only thing you can do is share the type with the frontend

Can you give an example how/why this pull request should be used?
PS: and fix the merge conflicts?

Unfortunately, I don't have the time for that. It's been a while since I last touched the code base.

LK"I
too bad, had to do this myself.. :)
i've tweaked the code to support both server/client!
typegoose-frontend
hopefully someone can create a pull request and integrate this to typegoose


fix: Return error when EF not set

Closes #82

#87  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tazarov and the rest of your teammates on  Graphite


Implement logic for Store Item Endpoint

Description
Item should track the User who created it through an Author field
What to do

Add author field to model
Add author rule to ItemStoreRequest.php
Add logic to Item Controller Store function
Add author field to ItemFactory

Hey team! Please add your planning poker estimate with ZenHub @IanjhPhillips @JasonGadoury @pascwhale @RobertoNittolo


How to ensure config items get updated once they were changed in Sail system? The same way as viper?

I'm starting to learn and use sail in my own project, a litter question: How to ensure config items get updated once they were changed in Sail system? The same way as viper?
Thanks a lot.
BTW,is there a commuincate way except github, I want to do some contribute to Sail once get started

@cestlive  Hi, I'm so sorry for not seeing this issues for a long time.  the answer of your question:  the sail-client will link the Sail sever use gRPC streaming. so when the config updated,  It will automatic updates.
By the way, the sail-client use viper at the bottom.
I'm still work in Sail, I have many exciting ideas to implement. If you want to connect me, my email is<EMAIL_ADDRESS> telegram: feng950704.
Best regards~


Component stops updating when you change the url before onReady

It seems that the component stops updating when you change the url before the onReady event of the player.
I'm building something where you can press a "next video" button, when used normally there is no problem however when you spam the button the component stops changing videos.
It also happens when I update the video in "componentDidMount"; I load the player with the url '' (empty string) and then load the actual url from sessionStorage in componentDidMount because componentDidMount happens very rapidly after the initialization of the component it changes the video url before the onReady and stops the component from updating.

I can consistently reproduce this error using this code. I expect this to load the video Rick Astley - Never Gonna Give You Up but instead it loads the first video Trolling Saruman.
import React from 'react';
import ReactDOM from 'react-dom';
import YouTube from './react-youtube/src/YouTube.js';

export default class Test extends React.Component {
	state = {
		video: 'http://youtu.be/KaqC5FnvAEc'
	};

	constructor( props ) {
		super( props );
	}

	componentDidMount() {
		this.setState({video: 'http://youtu.be/dQw4w9WgXcQ'});
	}

	onReady( event ) {
		console.log( "onReady", event, this.state );
	}

	onPlay( event ) {
		console.log( "onPlay", event, this.state );
	}

	onPause( event ) {
		console.log( "onPause", event, this.state );
	}

	onEnd( event ) {
		console.log( "onEnd", event, this.state );
	}

	onError( event ) {
		console.log( "onError", event, this.state );
	}

	render() {
		const opts = {};

		return(
			<div>
				<YouTube
					url={this.state.video}
					opts={opts}
					onReady={::this.onReady}
					onPlay={::this.onPlay}
					onPause={::this.onPause}
					onEnd={::this.onEnd}
					onError={::this.onError}
				/>
			</div>
		);
	}
}

ReactDOM.render(
	<Test />,
	document.getElementById('app')
);

I'm gonna debug this some more and hopefully figure out what is going wrong here...

Very weird, will dig into this today!

Hey thanks for responding :)
It seems that the issue comes from not correctly destroying the player...
When it gets loaded really quickly the first time this piece of code doesn't happen because of the delay before the createPlayer callback
 if (this._internalPlayer) {
      this._internalPlayer.destroy();
 }

Because the player gets created twice on the same element the youtube iframe api returns an empty player object the second time, this empty player gets set as the _internalPlayer and then the actual player that is on the page doesn't get propperly destroyed which makes all subsequent players also fail.
In my app this also happens when i click the

Huge, huge thanks for taking the time to check this out! #29 definitely needs to go through soon I've been putting it off for too long.
And honestly, if you want to do the rewrite I'm all for it. It'd legit be my first time accepting a PR that extensive so we'd both be learning in the process!. But either way, that rewrite is inevitable and shouldn't take too long so don't to waste your time with the other solutions (as much as I seriously appreciate you thinking them out!).
I'll create a branch to explore it right now. If you're up for it, join in

Thank you :D
I already ported the basic functionality (playing videos, haha), and will commit them to the rewrite branch soon.

remote: Permission to compedit/react-youtube.git denied to tjallingt.
:cry:
I attempted to update the dependencies and fix the tests as well but ran into some nasty problems...
Not sure whether I can manage to rewrite the tests by myself as I have almost no experience writing tests and due to the abstraction of the youtube api by youtube-player I'm not sure how to do most of the tests anyway.

Oops that's mybad, I should have mentioned. You need to open a pull request, so we can do something like this.
Check this out for the general idea. This guide walks you through the process a little more in depth. Just copy/paste the changes you've made and push them to your fork, then open a pull request and all that
If you have any questions, let me know! We can talk more about the code in the PR. And I wouldn't worry about the tests for now, going to have to rewrite them too so it's all good

I managed, thanks for the help :D


App Rejection when used KingFisher

Hey Hi,
First of all, thank you so much for such a great library.
So , I have submitted app to apple review , there it got rejected with following reason
Performance - 2.5.1 Your app uses or references the following non-public APIs: 1. imageCache The use of non-public APIs is not permitted
So from the reason , we can conclude , that apple has problem with imageCache keyword which may be apple is using somewhere in their own framework and is not documented or is not exposed to developers. So , Apple treat imageCache as non-public API.
Then I searched my complete project for keyword "imageCache". I came to know that kingfisher is using this and that might be the reason of rejection.
So, it would be very helpful if you guys can change the "imageCache" to something different or if you guys can suggest something in this regard.
This would help me in re-submitting the app for review.

Hi,
Only ImageCache is used as a very basic type name in Kingfisher and there is no imageCache property/syntax in Kingfisher. This (ImageCahce as type name) should never trigger a static analysis failing in private API.
Since there is no other report on this kind of rejecting until now, I believe it is more likely a bug of Apple's system or only your case (if you are using the letter-case imageCache in your code.)
Have you argued it with Apple's guys for it?

Hey,
No I have not argued it with Apple's guys for it.
But I have confirmed , that imageCache is not used in project code.
Let me argue with Apple , may be they can give exact insight into it.
Thanks for this qiuck response.

@Sunitadaffodil Sure!
Please let me know the result so I could see whether we should do something on it.

I can say that in my previous version of application I also used erlier version of Kingfisher and I had no problems uploading my application. Now I converted to Swift 3, should I be scared? Which version of Kingfisher you are using?

@Sunitadaffodil Hi, any progress on it? Does it still gets rejected?

Hi, my app is now approved by Review Team. But its strange , that they rejected app previously.

:) So I am closing this.
It is not surprising since they are also human and could make mistake on this time to time.


Update userguide with command summary

Pull Request Test Coverage Report for Build 320

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.119%

Totals

Change from base Build 319:
0.0%

Covered Lines:
2567

Relevant Lines:
3204

💛  - Coveralls


isXenograft

This concept is currently being used out in the wild but is not found in the schema. It seems sufficiently useful, and no term of same meaning already exists in schema.
Recommendation: add concept to schema

Should add as specified in https://github.com/nf-osi/nf-metadata-dictionary/issues/141


Hello-rails-react

In this project, I

[ ] created a new Rails app called hello-rails-react with PostgreSQL database,
[ ] installed needed node dependencies,
[ ] created a babel.config.js in the root folder,
[ ] updated webpack.config.js to include the babel-loader,
[ ] created a table for storing messages and created 5 different greetings.
[ ] created an API endpoint that selects a random greeting from the greetings table,
[ ] created a static view that will be the root of the app.
[ ] created the App component with react-router and rendered it in the static view.
[ ] created the Greeting component that displays a greeting,
[ ] settled up a route for the Greeting component,
[ ] created a store, an action, and a reducer that connects to the API endpoint to get the random greeting, and
[ ] displayed the random greeting in the Greeting component.

Thank you 🙌


Additional newlines printed with with st2 execution get

(original issue https://github.com/StackStorm/st2contrib/issues/556)
Looks like we get additional newlines printed when displaying the execution results. Seems to be specific to the CLI, as the JSON output looks OK.
vagrant@bwcvagrant:~$ cat localfile.txt
#### BLAH BLAH BLAH
###  & stuff...
#
vagrant@bwcvagrant:~$ st2 run core.local cmd='cat /home/vagrant/localfile.txt'
.
id: 597429e2bb0f185e19233cc5
status: succeeded
parameters:
  cmd: cat /home/vagrant/localfile.txt
result:
  failed: false
  return_code: 0
  stderr: ''
  stdout: '#### BLAH BLAH BLAH

    ###  & stuff...

    #'
  succeeded: true
vagrant@bwcvagrant:~$ st2 execution get 597429e2bb0f185e19233cc5 -j
{
    "id": "597429e2bb0f185e19233cc5",
    "parameters": {
        "cmd": "cat /home/vagrant/localfile.txt"
    },
    "result": {
        "failed": false,
        "return_code": 0,
        "stderr": "",
        "stdout": "#### BLAH BLAH BLAH\n###  & stuff...\n#",
        "succeeded": true
    },
    "status": "succeeded"
}
vagrant@bwcvagrant:~$ st2 --debug execution get 597429e2bb0f185e19233cc5
2017-07-23 04:46:16,468  DEBUG - Using cached token from file "/home/vagrant/.st2/token-st2admin"
# -------- begin<PHONE_NUMBER>73264 request ----------
curl -X GET -H  'Connection: keep-alive' -H  'Accept-Encoding: gzip, deflate' -H  'Accept: */*' -H  'User-Agent: python-requests/2.14.2' -H  'X-Auth-Token: b3f77ab505e24b4fbac96d13656aec48' 'http://<IP_ADDRESS>:9101/v1/executions/597429e2bb0f185e19233cc5?exclude_attributes=trigger_instance'
# -------- begin<PHONE_NUMBER>73264 response ----------
{
    "status": "succeeded",
    "start_timestamp": "2017-07-23T04:45:22.624375Z",
    "log": [
        {
            "status": "requested",
            "timestamp": "2017-07-23T04:45:22.637000Z"
        },
        {
            "status": "scheduled",
            "timestamp": "2017-07-23T04:45:22.720000Z"
        },
        {
            "status": "running",
            "timestamp": "2017-07-23T04:45:22.797000Z"
        },
        {
            "status": "succeeded",
            "timestamp": "2017-07-23T04:45:22.943000Z"
        }
    ],
    "parameters": {
        "cmd": "cat /home/vagrant/localfile.txt"
    },
    "runner": {
        "runner_module": "local_runner",
        "uid": "runner_type:local-shell-cmd",
        "enabled": true,
        "name": "local-shell-cmd",
        "runner_parameters": {
            "sudo": {
                "default": false,
                "type": "boolean",
                "description": "The command will be executed with sudo."
            },
            "timeout": {
                "default": 60,
                "type": "integer",
                "description": "Action timeout in seconds. Action will get killed if it doesn't finish in timeout seconds."
            },
            "cmd": {
                "type": "string",
                "description": "Arbitrary Linux command to be executed on the host."
            },
            "kwarg_op": {
                "default": "--",
                "type": "string",
                "description": "Operator to use in front of keyword args i.e. \"--\" or \"-\"."
            },
            "env": {
                "type": "object",
                "description": "Environment variables which will be available to the command(e.g. key1=val1,key2=val2)"
            },
            "cwd": {
                "type": "string",
                "description": "Working directory where the command will be executed in"
            }
        },
        "id": "5887bd70bb0f1834bc628d64",
        "description": "A runner to execute local actions as a fixed user."
    },
    "elapsed_seconds": 0.299195,
    "web_url": "https://bwcvagrant/#/history/597429e2bb0f185e19233cc5/general",
    "result": {
        "failed": false,
        "stderr": "",
        "return_code": 0,
        "succeeded": true,
        "stdout": "#### BLAH BLAH BLAH\n###  & stuff...\n#"
    },
    "context": {
        "user": "st2admin"
    },
    "action": {
        "runner_type": "local-shell-cmd",
        "name": "local",
        "parameters": {
            "cmd": {
                "required": true,
                "type": "string",
                "description": "Arbitrary Linux command to be executed on the local host."
            },
            "sudo": {
                "immutable": true
            }
        },
        "tags": [],
        "enabled": true,
        "entry_point": "",
        "notify": {},
        "uid": "action:core:local",
        "pack": "core",
        "ref": "core.local",
        "id": "5887bd70bb0f1834bc628d6b",
        "description": "Action that executes an arbitrary Linux command on the localhost."
    },
    "liveaction": {
        "runner_info": {
            "hostname": "bwcvagrant",
            "pid": 3681
        },
        "parameters": {
            "cmd": "cat /home/vagrant/localfile.txt"
        },
        "action_is_workflow": false,
        "callback": {},
        "action": "core.local",
        "id": "597429e2bb0f185e19233cc4"
    },
    "id": "597429e2bb0f185e19233cc5",
    "end_timestamp": "2017-07-23T04:45:22.923570Z"
}
# -------- end<PHONE_NUMBER>73264 response ------------

id: 597429e2bb0f185e19233cc5
status: succeeded (0s elapsed)
parameters:
  cmd: cat /home/vagrant/localfile.txt
result:
  failed: false
  return_code: 0
  stderr: ''
  stdout: '#### BLAH BLAH BLAH

    ###  & stuff...

    #'
  succeeded: true
vagrant@bwcvagrant:~$ st2 --version
st2 2.3.1
vagrant@bwcvagrant:~$

I have this fixed in #3872 . It also fixes the newline issue, which I think was an unintentional regression. I can't say the same for this issue, as the duplicate newlines is literally incorporated into the test fixtures LMFAO
In any case, this should be fixed when that's merged.


Clicking on the "Get Started, It's Free!" button 404 error

http://cryptoeconomics.study/docs/en/getting-started/welcome returns error 404

Sorry! That link should be https://cryptoeconomics.study/docs/en/sync/getting-started-welcome. Will fix shortly

fixed


Issues/8607/review missed

Proposed Changes

Fixes #8607
Change 1: In the ManagePatients.tsx file, I added a condition that displays:
Time left for review if the review is upcoming.
Missed since [X] days if the review time has passed
Change 2
More?

@ohcnetwork/care-fe-code-reviewers
Merge Checklist

[ ] Add specs that demonstrate bug / test a new feature.

[ ] Ensure that UI text is kept in I18n files.

[ ] Update product documentation.

[ ] Prep screenshot or demo video for changelog entry, and attach it to issue.

[X] Request for Peer Reviews

[ ] Completion of QA

Summary by CodeRabbit

New Features

Enhanced patient review notifications with clear indicators for missed ("Review Missed") and upcoming ("Review Due in") reviews, improving user awareness.
Improved phone number management with validation for primary and emergency contact numbers.
Refactored search functionality to allow searching by patient name, IP/OP number, and phone numbers using new input components.
Introduced a new Badge component with additional styling variants, including a new "success" variant, for improved visual clarity and accessibility.

Bug Fixes

Streamlined code by removing unnecessary commented-out sections, improving maintainability.

Also make sure to edit the title to be human friendly 👍

I’ve made the required changes. Should I go ahead and raise a new PR for them, or should I update the existing one instead? Let me know how to proceed.

update existing PR

I made the required changes please review my code.

@Jacobjeevan can you look into the PR

Closing as stale, feel free to reopen once changes made.

Hi @rithviknishad,
I have made the necessary changes. Could you please reopen the PR?
Thank you!


Can't load plugin (windows 8.1)

Don't know why but he cant load the vlc plugin, i got win8.1 vlc's lastest version with full features installed, i see it on the folder C:/Programs x86/VideoLan/VLC/npvlc.dll but I always get the error on getting external player because internal one doesn't work...
Nice project, got my point in favor! ;)

@Zanatus please test our latest flixtor release