Yahoo Exchange failing on appveyor

1) Yahoo XChange forex rates should only return currencies of interest:
     SuperagentPromiseError: cannot GET http://query.yahooapis.com/v1/public/yql (400)
      at C:\projects\yappy\lib\superagent-bluebird-promise.js:72:19
      at Request.callback (C:\projects\yappy\node_modules\superagent\lib\node\index.js:800:3)
      at IncomingMessage.<anonymous> (C:\projects\yappy\node_modules\superagent\lib\node\index.js:997:12)
      at emitNone (events.js:73:20)
      at IncomingMessage.emit (events.js:167:7)
      at endReadableNT (_stream_readable.js:906:12)
      at nextTickCallbackWith2Args (node.js:455:9)
      at process._tickCallback (node.js:369:17)

Added some logging and now its working!  I bet its a timeout issue.
Will leave this open for a while.


can I compile DCN using cuda version later than 10.2

Hi I tried to compile the project with a cuda version 11.0 and get an error
" File "/home/ztchen/Projects/NLSPN_ECCV20/src/model/modulated_deform_conv_func.py", line 13, in
import DCN
ImportError: libcudart.so.10.2: cannot open shared object file: No such file or directory"
Is the DCN compilation tied to cuda10.2?
Thanks

Hi.
From my experience, the DCN compilation works with CUDA 11.3


core-api: add another set of composability plumbing

Hey, I just made a Pull Request!
More work on top of #3471
Fixes #3419, fixes #3421
The routing API in core has a stability index of 2, so a couple of changes here required deprecation even if there hasn't ever been any real reason to use any of the deprecated symbols. In particular the createSubRoute method I kept along with deprecation notice, but it straight up throws an error if called and the return type is set to any. There's never been a reason to call the method, but I wanna make it very clear what's up in case it does end up breaking any build out there.
This still doesn't add any actual functionality, and the only change to public API is the addition of the optional params option for createRouteRef.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)

Well there we go, deprecation was needed because the AbsoluteRouteRef type ended up being used as the type of any RouteRef that plugins exported :grin:


import log4javascript as 3rd party library

Hi,
I really like your project, clean and neat.
I'm trying to build a log service of my own that usses 'log4javascript';
I added this library to vendor.ts and to my service.
but when I run it, I get an error:
log4javascript is not defined.
Here is my code:
import { Injectable } from '@angular/core';
import  {Logger} from 'log4javascript';
@Injectable()
export class MyLoggerService {
log:any;
constructor() {
this.log=Logger;
let ajaxAppenderInfo = new log4javascript.AjaxAppender('http://localhost:8989/api/log/info');
ajaxAppenderInfo.setThreshold(log4javascript.Level.INFO);
this.log.addAppender(ajaxAppenderInfo);
this.log.info('Init Info logger');

}
info(message){
this.log.info(message);
}
}
Thank you in advance :)
Amit

You need https://www.npmjs.com/package/@types/log4javascript

I've done it ofcourse. the error is at run time.
when I get to the service Constructor it didn't yet upload 'log4javascript' library.

Ok.. this iw weird I succeed by changing the row from import {Logger} from 'log4javascript';
to
import * as log from 'log4javascript';
this is suck .
thank you for the answer.

The problem is that log4javascript is not ready for ES6 imports (which is what TS uses). That library is like a year and a half old, so the author would need to update it to "modern tools".


Drop header image

IBM Cloud toolchain: Delivery Pipeline deployed sample-devops-studentXX-myapp to test, including commit 509d360169de6a6d5ffc1a92ef2214f3b2043403

IBM Cloud toolchain: Delivery Pipeline deployed sample-devops-studentXX-myapp to prod, including commit 509d360169de6a6d5ffc1a92ef2214f3b2043403


Sync ietf-datastores with the version provided by libyang

Here's how it's failing with the most recent libyang: https://zuul.gerrit.cesnet.cz/t/public/build/f59ad09409ab4320b7cc3b91d5f49924

Hi,
right, sorry. Although I do not think require the latest libyang in this old server is desired so the solution here is probably to remove the test that fails.
Regards,
Michal

I think that those who cannot update to latest libyang can just stay on an oldish Netopeer2. I've deliberately bumped the libyang requirements to the latest because that's what I'm testing against, and I don't think that a full bisection run for finding out which version exactly introduced this would be worth the hassle.

I agree, that is why I suggested removing the single test altogether, which should make it, again, not dependent on any libyang version.

I think that the test is reasonable because it can guard against possible future regressions in libyang. It should be low-maintenance because I do not expect changes to that IETF model now that it's been released. I understand that your interest in maintenance of legacy code is not big :), but this is a patch which solves a real problem. (And yup, we will eventually move to the non-legacy branches, it's just ENOTIME for now.)

Well, ultimately I can fix it any way I want but I do not really understand why you think your change is the most correct one. The test itself is a rather useless one considering there are filtered tests following it and, most importantly, requires an exact answer from the server, which, as happened now, is a maintenance problem. It depends on an exact set of internal libyang modules and their revisions, which may easily change in future. Also, like I said before, this change now requires the latest libyang, which is an overkill for such legacy code.
So, I will simply remove that one test to fix this unless you can give me a really good reason why I should not.
Regards,
Michal

I missed the fact that there are more fine-grained tests for other libs in the library, so I agree with you, this looks like something that can be safely removed.

Okay, should work now without the test.
Regards,
Michal


renovate: fix typo

I really wish these were easier to validate :(

Ok I've found a config validator I'll try to run from now on :|


Fix addMetrics() of ShardedLRU

Wrong test cases caused the bug to be ignored.

I have completed signing the Contributor Agreement. Check, please.

Good spot and thank you for the fix!

released v0.13.0


Generic parts of cargotest as a separate crate?

I was looking at how cargo tests are working, and I really like it. I'd like to do something similiar for my own projects, and seems like a big part of cargotest is actually quite generic. I wonder if there are any plans, or previous work that would made it into a library.

Sure! I probably won't actively extract these pieces, but you're more than welcome to!


Add QR code to PDFs for verification

Is your feature request related to a problem? Please describe.
When a PDF is generated from the wallet there is no way to identify the PDF as being sourced from a Verifiable Credential.
Describe the solution you'd like
The LCW has the ability to generate a link to verifier plus for the credential. We could use this functionality to add a QR code to the PDF that will contain that link.  We could consider asking the user if they would like a url added to their PDF.
Describe alternatives you've considered
We could also consider using CBOR (?) to pack the data into the PDF and signing it but that's probably outside the scope of this because a link to verifier plus is far more usable.
Additional context
One of the challenges is that we provide the user with an option to create and destroy a URL. Do we use this url in the DPF and have them create it before exporting or do we keep this functionality separate? Also, links stored in the verifier plus db expire in one year. If we add a url to the PDF, would it be. different one every time the PDF is generated

Added a priority label because issuing of diplomas is imminent and we will want the PDFs to be verifiable.

Team meeting: https://docs.google.com/document/d/1cxKjKE6AfHxvPxYVYkgs6sXrs2Wk5OywWNAGwy1NXls/edit

On hold until team meets again

Currently blocked by: https://github.com/digitalcredentials/web-verifier-plus/issues/126

Dev team meeting: Have it function in the same way as the Post to LinkedIn option

Implementation details for this ticket: For wallet on share screen:

Check if credential is verified, then
Check if credential has renderMethod field, then
Check if this method has html embedded or a link to an html file
If there is custom html provided by the issuer via a template, in the export to PDF code, look through html for a qr code tag provided by the DCC (let's call it qr_code), so that if we search for {qr_code}, we replace what's in the curly braces with an img element of a QR code of the share link.

Goal is to replace any QR codes provided in a custom html template, NOT to add them.

Updated title to reflect work done on PDF fix; QR code implementation now implemented in #650.


Add NET 5 and NET Core 3.1 support.

The demo seems to work targeting with NET 5. Some of the fancy versioning and build scripts may brake with the assembly info modifications.
The project format is changed to the new SDK format:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <ProductVersion>9.0.30729</ProductVersion>
    <OutputType>WinExe</OutputType>
    <!--<TargetFramework>net45</TargetFramework>-->
    <!--<TargetFramework>netcoreapp3.1</TargetFramework>-->
    <TargetFramework>net5.0-windows</TargetFramework>
    <ApplicationManifest>app.manifest</ApplicationManifest>
    <ApplicationIcon>ookii.ico</ApplicationIcon>
    <AssemblyTitle>Ookii.Dialogs.WinForms.Sample</AssemblyTitle>
    <Company>augustoproiete.net</Company>
    <Product>Ookii.Dialogs.WinForms</Product>
    <Copyright>Copyright (c) 2009-2021 Ookii Dialogs Contributors</Copyright>
    <GenerateAssemblyConfigurationAttribute>false</GenerateAssemblyConfigurationAttribute>

Just uncomment the other target and comment the other. The NuGet is targeting all the three different ones. 🙂

Hi,
The forms seem to be editable with the NET 5 config:

It says changes have happened, but actually nothing has changed:

I'll have a look at your suggestions tomorrow and make the necessary edits. 👍

Awesome! Thanks again :tada:

Thanks @VPKSoft I was able to do some tests over the weekend, and looks good.
There's a couple of things that need to be ironed out before a release, but I'm happy to merge it as-is for now and continue improving in future commits/PRs.
As you pointed out, the build script is now broken because it tries to update the AssemblyVersionInfo.cs which you renamed so it can no longer find it. The final solution will be to get the build script closer to the one that ookii-dialogs-wpf is using where the version is passed to DotNetCoreBuild.
There's also a number of warnings that need to be resolved (most of them cause by .NET 5):

Build warnings (click to expand)

"C:\ookii-dialogs-winforms\Ookii.Dialogs.WinForms.sln" (Rebuild target) (1) ->
"C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj" (Rebuild target) (2) ->
"C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj" (Build target) (2:7) ->
(CoreCompile target) ->
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\SafeHandles.cs(25,6): warning SYSLIB0003: 'SecurityPermissionAttribute' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\SafeHandles.cs(25,25): warning SYSLIB0003: 'SecurityAction' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\SafeHandles.cs(94,10): warning SYSLIB0004: 'ReliabilityContractAttribute' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\SafeHandles.cs(94,30): warning SYSLIB0004: 'Consistency' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\SafeHandles.cs(94,63): warning SYSLIB0004: 'Cer' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\SafeHandles.cs(33,10): warning SYSLIB0004: 'ReliabilityContractAttribute' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\SafeHandles.cs(33,30): warning SYSLIB0004: 'Consistency' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\SafeHandles.cs(33,63): warning SYSLIB0004: 'Cer' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\SafeHandles.cs(41,6): warning SYSLIB0003: 'SecurityPermissionAttribute' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\SafeHandles.cs(41,25): warning SYSLIB0003: 'SecurityAction' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\SafeHandles.cs(61,6): warning SYSLIB0003: 'SecurityPermissionAttribute' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\SafeHandles.cs(61,25): warning SYSLIB0003: 'SecurityAction' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\ExtendedForm.cs(285,10): warning SYSLIB0003: 'SecurityPermissionAttribute' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\ExtendedForm.cs(285,57): warning SYSLIB0003: 'SecurityAction' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\ExtendedForm.cs(285,120): warning SYSLIB0003: 'SecurityPermissionFlag' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\NativeMethods.cs(58,9): warning SYSLIB0004: 'ReliabilityContractAttribute' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\NativeMethods.cs(58,29): warning SYSLIB0004: 'Consistency' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\NativeMethods.cs(58,62): warning SYSLIB0004: 'Cer' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\NativeMethods.cs(228,37): warning SYSLIB0004: 'ReliabilityContractAttribute' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\NativeMethods.cs(228,57): warning SYSLIB0004: 'Consistency' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\NativeMethods.cs(228,90): warning SYSLIB0004: 'Cer' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialDialog.cs(397,10): warning SYSLIB0003: 'SecurityPermissionAttribute' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialDialog.cs(397,29): warning SYSLIB0003: 'SecurityAction' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialDialog.cs(397,64): warning SYSLIB0003: 'SecurityPermissionFlag' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialDialog.cs(438,10): warning SYSLIB0003: 'SecurityPermissionAttribute' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialDialog.cs(438,29): warning SYSLIB0003: 'SecurityAction' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialDialog.cs(438,64): warning SYSLIB0003: 'SecurityPermissionFlag' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialDialog.cs(512,10): warning SYSLIB0003: 'SecurityPermissionAttribute' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialDialog.cs(512,29): warning SYSLIB0003: 'SecurityAction' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialDialog.cs(512,64): warning SYSLIB0003: 'SecurityPermissionFlag' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(34,10): warning SYSLIB0003: 'SecurityPermissionAttribute' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(34,29): warning SYSLIB0003: 'SecurityAction' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(34,64): warning SYSLIB0003: 'SecurityPermissionFlag' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(44,10): warning SYSLIB0003: 'SecurityPermissionAttribute' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(44,29): warning SYSLIB0003: 'SecurityAction' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(44,64): warning SYSLIB0003: 'SecurityPermissionFlag' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(54,10): warning SYSLIB0003: 'SecurityPermissionAttribute' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(54,29): warning SYSLIB0003: 'SecurityAction' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(54,64): warning SYSLIB0003: 'SecurityPermissionFlag' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(65,10): warning SYSLIB0003: 'SecurityPermissionAttribute' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(65,29): warning SYSLIB0003: 'SecurityAction' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(65,64): warning SYSLIB0003: 'SecurityPermissionFlag' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\NativeMethods.cs(506,10): warning SYSLIB0004: 'ReliabilityContractAttribute' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\NativeMethods.cs(506,30): warning SYSLIB0004: 'Consistency' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\NativeMethods.cs(506,63): warning SYSLIB0004: 'Cer' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(76,10): warning SYSLIB0003: 'SecurityPermissionAttribute' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(76,29): warning SYSLIB0003: 'SecurityAction' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(76,64): warning SYSLIB0003: 'SecurityPermissionFlag' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(87,10): warning SYSLIB0003: 'SecurityPermissionAttribute' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(87,29): warning SYSLIB0003: 'SecurityAction' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialException.cs(87,64): warning SYSLIB0003: 'SecurityPermissionFlag' is obsolete: 'Code Access Security is not supported or honored by the runtime.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\NativeMethods.cs(510,10): warning SYSLIB0004: 'ReliabilityContractAttribute' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\NativeMethods.cs(510,30): warning SYSLIB0004: 'Consistency' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\NativeMethods.cs(510,63): warning SYSLIB0004: 'Cer' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\NativeMethods.cs(756,37): warning SYSLIB0004: 'ReliabilityContractAttribute' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\NativeMethods.cs(756,57): warning SYSLIB0004: 'Consistency' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\NativeMethods.cs(756,90): warning SYSLIB0004: 'Cer' is obsolete: 'The Constrained Execution Region (CER) feature is not supported.' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\CredentialDialog.cs(468,34): warning CS8073: The result of the expression is always 'false' since a value of type 'IntPtr' is never equal to 'null' of type 'IntPtr?' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]
  C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\ProgressDialog.cs(564,31): warning CS8073: The result of the expression is always 'false' since a value of type 'IntPtr' is never equal to 'null' of type 'IntPtr?' [C:\ookii-dialogs-winforms\src\Ookii.Dialogs.WinForms\Ookii.Dialogs.WinForms.csproj]

If you fancy sending PRs to fix the above feel free, if not I'll get to them at some point in the next week or two, no worries.

Disable SYSLIB0003 and SYSLIB0004 rule check (features not supported in .NET 5)
Fix incorrect IntPtr null check

@VPKSoft your changes have been merged, thanks for your contribution :+1:

I might create another PR if I have the time. I'm currently converting my own packages and probably need to publish few NuGets from repositories created by others, which are not maintained anymore. Just prefix the package with unofficial. 🙂 But great that this is progressing - the WinForms basic folder browser dialog just is quite unusable 👍


Syntax error: word unexpected (expecting ")") on Raspbian

Getting this error when I run npm run local on Raspbian.
Syntax error: word unexpected (expecting ")")
Gateway child process exited with code = 2

I get the same error.

Raspbian is not currently supported, however this scenario is a pri 1 task in our backlog and should be supported shortly. For NPM to only supported operating systems are Ubuntu and Windows.

@ksaye Please try latest version(1.1.4) of azure-iot-gateway, it starts to support Debian Jessie and Raspbian.


ThreadX Context Save/Restore of Floating Point Registers for Cortex-R5

I'm working on setting up ThreadX with Cortex-R5F on Xilinx Ultrascale+ R5F. I've noticed some data corruption associated with using floating point registers on memcpy and now looking at  _tx_thread_context_save for R5 port, it seems like it doesn't save context floating point registers.
There are some references to VFP support on other processor ports but isn't much documentation to go off.
Is it possible to use hard floating point math on R5 with ThreadX?

Some of the other ARM ports seem to have support for using TX_ENABLE_VFP_SUPPORT then using tx_thread_vfp_enable to enable it, but the R5 is missing is the extension define here:
https://github.com/eclipse-threadx/threadx/blob/master/ports/cortex_r5/gnu/inc/tx_port.h#L197
Like for the A9:
https://github.com/eclipse-threadx/threadx/blob/master/ports/cortex_a9/gnu/inc/tx_port.h#L199

Funny, seems related to our #382 two weeks  before your report, we are on the same problematics
Our Quick and Dirty solution is , for now, building in softFP...


EDU-447 Auto image resize

Closes https://educandu.atlassian.net/browse/EDU-447
and looks like:

Wow, what an elegant and simple solution without libraries etc. :cupid: :+1:


[DOCFIX] Added FAQ to docs

@calvinjia

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13326/
Test PASSed.

@yupeng9 Thanks for adding back this page. Could you enforce the 100 character/line limit and run it through a word processor for grammar/spelling?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13357/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13379/
Test PASSed.

LGTM, thanks for cleaning up this doc and adding it back!


TelemetryConverter configuration throws InvalidOperationException using the provided appsettings sample

Description
Configuring the "telemetryConverter" appsettings section with the sample provided in the README ("telemetryConverter": "Serilog.Sinks.ApplicationInsights.TelemetryConverters.TraceTelemetryConverter, Serilog.Sinks.ApplicationInsights") causes a System.InvalidOperationException to be thrown.

Reproduction
Program.cs
var configuration = new ConfigurationBuilder()
    .SetBasePath(Directory.GetCurrentDirectory())
    .AddJsonFile("appsettings.json")
    .Build();

var logger = new LoggerConfiguration()
    .ReadFrom.Configuration(configuration)
    .CreateLogger();

logger.Information("Hello, world!");

Console.ReadLine();

appsettings.json
{
  "Serilog": {
    "Using": [
      "Serilog.Sinks.ApplicationInsights"
    ],
    "MinimumLevel": {
      "Default": "Debug",
      "Override": {
        "Microsoft": "Information"
      }
    },
    "WriteTo": [
      {
        "Name": "ApplicationInsights",
        "Args": {
          "restrictedToMinimumLevel": "Information",
          "telemetryConverter": "Serilog.Sinks.ApplicationInsights.TelemetryConverters.TraceTelemetryConverter, Serilog.Sinks.ApplicationInsights"
        }
      }
    ],
    "Enrich": [ "FromLogContext" ],
    "Properties": {
      "Application": "Sample"
    }
  }
}

Relevant package, tooling and runtime versions
[net6.0]:
Top-level Package                                        Requested   Resolved

Microsoft.Extensions.Configuration.FileExtensions      6.0.0       6.0.0
Microsoft.Extensions.Configuration.Json                6.0.0       6.0.0
Serilog                                                2.11.0      2.11.0
Serilog.Settings.Configuration                         3.3.0       3.3.0
Serilog.Sinks.ApplicationInsights                      3.1.0       3.1.0

Transitive Package                                           Resolved

Microsoft.ApplicationInsights                              2.12.0
Microsoft.Extensions.Configuration                         6.0.0
Microsoft.Extensions.Configuration.Abstractions            6.0.0
Microsoft.Extensions.Configuration.Binder                  2.0.0
Microsoft.Extensions.DependencyInjection.Abstractions      2.0.0
Microsoft.Extensions.DependencyModel                       3.0.0
Microsoft.Extensions.FileProviders.Abstractions            6.0.0
Microsoft.Extensions.FileProviders.Physical                6.0.0
Microsoft.Extensions.FileSystemGlobbing                    6.0.0
Microsoft.Extensions.Options                               2.0.0
Microsoft.Extensions.Options.ConfigurationExtensions       2.0.0
Microsoft.Extensions.Primitives                            6.0.0
Microsoft.NETCore.Platforms                                1.1.0
Microsoft.NETCore.Targets                                  1.1.0
System.Diagnostics.DiagnosticSource                        4.6.0
System.IO                                                  4.3.0
System.Reflection                                          4.3.0
System.Reflection.Primitives                               4.3.0
System.Runtime                                             4.3.0
System.Runtime.CompilerServices.Unsafe                     6.0.0
System.Runtime.Handles                                     4.3.0
System.Runtime.InteropServices                             4.3.0
System.Text.Encoding                                       4.3.0
System.Text.Encodings.Web                                  6.0.0
System.Text.Json                                           6.0.0
System.Threading.Tasks                                     4.3.0

Additional context
Using this alternative configuration fixes the problem but it seems not right
"Serilog.Sinks.ApplicationInsights.Sinks.ApplicationInsights.TelemetryConverters.TraceTelemetryConverter, Serilog.Sinks.ApplicationInsights"

I think you can take a look at this https://stackoverflow.com/questions/67672174/how-to-set-telemetryconfiguration-for-application-insights-for-serilog-via-appse.
In it, you can find the configuration set as
"telemetryConverter": "Serilog.Sinks.ApplicationInsights.Sinks.ApplicationInsights.TelemetryConverters.TraceTelemetryConverter, Serilog.Sinks.ApplicationInsights"

I think you can take a look at this https://stackoverflow.com/questions/67672174/how-to-set-telemetryconfiguration-for-application-insights-for-serilog-via-appse. In it, you can find the configuration set as "telemetryConverter": "Serilog.Sinks.ApplicationInsights.Sinks.ApplicationInsights.TelemetryConverters.TraceTelemetryConverter, Serilog.Sinks.ApplicationInsights"

Hello David, thanks for your reply!
I'm aware that adding an extra pair of "Sinks.ApplicationInsights makes the "telemetryConverter" work (see Additional context), but it doesn't seem right...
If this is the expected behaviour then the documentation should be updated.

The suggested link to the stack overflow question above may work for a net core web app project, but using a net core worker service requires we use "Microsoft.ApplicationInsights.WorkerService" package instead of "Microsoft.ApplicationInsights.AspNetCore" package, and this doesnt have an option to set for "EnableActiveTelemetryConfigurationSetup = true", so what is the solution please? I cant update this sink to ver. 4+ until we have a solution that is explained clearly and people can follow, please help...

Has this been fixed in 4.0? Our previous Sinks.ApplicationInsights.Sinks.ApplicationInsights broke after update and after removing the duplicate the app starts again normally

Ah now I understand what's going on! Yes, thanks @spaasis - this is a breaking change in 4.0, the README is referring to the v4.0 configuration. Upgrading to v4 or later will fix this.
I've added the missing note to the "breaking changes" section of the release notes:
https://github.com/serilog-contrib/serilog-sinks-applicationinsights/releases/tag/v4.0.0


Stick axes scaling incorrectly.

The values of both scaled left and right stick x and y values currently range from -1.0 .. 0.9999695 instead of the -1 .. 1 one would expect.

Thanks. I've merged your pull request.


exploitdb: 2024-03-06 -> 2024-03-07

Diff: https://gitlab.com/exploit-database/exploitdb/-/compare/refs/tags/2024-03-06...2024-03-07
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

1 package built:

exploitdb


How to Provide User specific Permissions

i have  two types of roles gm and sysadmin every user will belong to gm or either sysadmin how can i make   user(gm role) should not have access to user management

Start by reading the guide and permissions.


fix: send and cancel btn tooltips

Carbon applies the iconDescription as a tooltip for buttons that use icons. This label is attached as an aria-label to the svg component within the button, not the actual button. We need a test id to get the buttons for tests, while also ensuring the tooltips are not undefined for the user. I didn't want to put an aria-label on the button as well as the svg, so this solution fixes the tooltips while also ensuring tests pass.

Recommend merging with base branch before merge, otherwise lgtm!!


Species Starting XP

Having a way to populate starting XP from species when you drag it onto a character sheet would be very nice. Is this a possibility?
Thank you for all your hard work!

Done, will be released in 1.810. Thanks for the suggestion!


Invalid MEX-file with load_xdf()

From https://github.com/sccn/eeglab/issues/132
I am getting an error when I work with xdimport.
Warning: Escaped character '\U' is not valid. See 'doc sprintf' for supported special characters.
Warning: Invalid MEX-file 'C:
We've tried to seperate the load_xdf folder alone from EEGLab. The problem is in the load_xdf_innerloop.C file at about line 327 that works with MEX files. It worked about a week ago.

Closing in favour of #50


add mdrec to the rosdep

Signed-off-by: Masaya Kataoka<EMAIL_ADDRESS>add mdrec to the rosdep

I want to add mdrec to the rosdep. (markdown -> html conversion tool)
https://pypi.org/project/mdrec/

No response for a month, so I'm going to close this out.  Feel free to reopen if you still want to get this rosdep key in.


Automatically convert image to tensors in TF data pipeline

In https://github.com/lancedb/lance/blob/main/python/python/lance/tf/data.py
users should be able to specify they want an image column to be read as a tensor.

This is now covered for encoded images and fixed shape tensors. Variable shape tensors have their own issue https://github.com/lancedb/lance/issues/1387.


Apple/gov

Description

Fetch proposal from LCD and Save the voting power when someone vote/ deposit/ submit proposal
close #29  #28
Checklist

[ ] Targeted PR against correct branch.
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit tests.
[ ] Re-reviewed Files changed in the Github PR explorer.

Codecov Report

Merging #33 into master will increase coverage by 4.60%.
The diff coverage is 87.30%.

@@            Coverage Diff             @@
##           master      #33      +/-   ##
==========================================
+ Coverage   64.88%   69.49%   +4.60%
==========================================
  Files          10       11       +1
  Lines         487      613     +126
==========================================
+ Hits          316      426     +110
- Misses        128      136       +8
- Partials       43       51       +8

Impacted Files
Coverage Δ

database/gov.go
87.30% <87.30%> (ø)

Continue to review full report at Codecov.

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


Moving bpf dir

Fixes #376
There's a TODO to check if go-bindata was compiled against go1.7.4, otherwise the generated files will always be different if go-bindata was compiled against go1.8 for example.

This pull request is now managed with CodeReviewHub. Refresh.

Rest looks good to go from my side.


Fix simultaneous using of long strings vectors and vectors of trivial type values for ODBC

9b4c5484faa4a753b6bdee19673f41912c5b5835 makes the error (sorry) when fetching a vector of trivial type values by a single row. Because vectors of trivial type values binded directly as a pointer to the first element (long string and other types converted in odbc_vector_into_type_backend::exchange_rows()).

Fixed.

Merged with another minor renaming, thanks.


subsys/storage/flash_map: remove unnecessary includes

Those files includes soc.h header which exists not for all boards. soc.h consists soc-depended defenitions and need to be included by soc-depended sources

What board does not have this file?

soc.h doesn't exists for arm64 boards: xenvm, ti-sitara, qemu_cortex_a53, qemu_virt_arm64 and others.
Files in this commit doesn't depend on soc.h.
I understand - another way to fix this issue - create empty soc.h. Is it correct way you guess?

Done


Remove unused imports

Not a big deal, but the unused imports are noisy :)

Thanks a lot! Can you merge with main?

My pleasure.  Done.


[BUG] ion-select-options appear behind the pane, select itself doesnt.

Describe the bug
Not sure if it is a bug, but i have a pane with an ion-select... and regardless of the interface i use (alert, popover or action-sheet), the options appear behind the modal. The select itself is showing on the pane, but the options aren't showing.
I looked for options to change the z-index, but haven't been successful. I'm using Ionic / Angular and I guess it's in the shadow DOM.
Expected behavior
I expect the selectable options to appear in front of the the pane, regardless of the interface used.

@woutersteven2020 thank you, I'll check.


Added animation on landing page

Description
This PR fixes #51
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Please share a screenshot of how the page looks after your changes

I am handling some merge conflicts now, I will merge yours once those are resolved, do share a small video/screenshot

Ok

@san-coding Have a look at this.

Thanks @AwsmNinad25 , I will soon merge it

Is it responsive ?

@AwsmNinad25 there was a sticky modal button on the top right corner, I am unable to see that in your video

@AwsmNinad25 I think you might have to wait and make some changes , because @SayantaniDeb is working on the making the nav bar sticky and moving the sticky button to the nav bar or to the bottom right corner, once she completes these two tasks, you can fetch and make your changes, sorry for the inconvenience caused, multiple people working on the landing page is causing merge conflicts, lets wait for @SayantaniDeb to finish, looking forward to merging your PR, the animations look beautiful🎉

@san-coding

Is it responsive ? and is it possible to add the same animations to the customer registration, browse products, and the footer ?

Yup this is responsive and yes it is possible to add animation to customer registration, browse products, and the footer.

@san-coding

Is it responsive ? and is it possible to add the same animations to the customer registration, browse products, and the footer ?

Yup this is responsive and yes it is possible to add animation to customer registration, browse products, and the footer.

is that button on the top right corner present ?

@AwsmNinad25 I think you might have to wait and make some changes , because @SayantaniDeb is working on making the nav bar sticky and moving the sticky button to the nav bar or to the bottom left corner, once she completes these two tasks, you can fetch and make your changes, sorry for the inconvenience caused, multiple people working on the landing page is causing merge conflicts, so don't push anymore commits to this PR, lets wait for @SayantaniDeb to finish, then you can merge those changes and commit your changes to it, looking forward to merging your PR, the animations look beautifultada

Yes, sure I'll wait no problem

@san-coding

Is it responsive ? and is it possible to add the same animations to the customer registration, browse products, and the footer ?

Yup this is responsive and yes it is possible to add animation to customer registration, browse products, and the footer.

is that button on the top right corner present ?

no. it isn't

The nav bar was sticky but no sign of that corner button.

Yeah please wait for a while, It was a mistake on my part , I merged a PR which undid those changes, that's why it doesn't show up, @SayantaniDeb will soon open her PR, I will merge that and then we can work on this, thank you for your patience

I will merge this now and check if everything works , will revert if there is an issue

Thank you for your time and effort, everything works fine and the animations look amazing 🎉, I request you to open pull request to add animations for forms , browse products and the footer (try to bring out the animations when we scroll down , if possible)


Feat/setup hello api

Implemented Changes

[x] Setup API Rails Project
[x] Setup PostgreSQL as a database
[x] Create a table, Model, and controller for Greeting
[x] Render a JSON with a generic Greeting
[x] /greetings endpoint included as well

Dear code reviewer: You can check the pull request for the front-end here:
https://github.com/Diegogagan2587/hello-react-front-end/pull/1

Hi @Diegogagan2587, are you available for a quick huddle on slack?  Your  app setup looks okay but I can't see your greeting displayed on the frontend, I would like to confirm the issue is not from my end


fix(select): add RTL support to the select component (#2042)

Closes #2042
📝 Description
Add RTL support to the select component.
⛳ Current behavior (updates)
The select component currently lacks support for right-to-left (RTL) direction.
🚀 New behavior
This PR addresses the RTL support issue in the select component, ensuring correct rendering in RTL environments.
💣 Is this a breaking change (Yes/No):
📝 Additional Information

@mrbadri could you make the Listbox items to be RTL as well?


Add estimate moved docs ratio unit test.

@geirst : please review

@toregge please merge after merge stop is lifted.


Enhancement: Use Facebook video live stream in chat instead of text messages

It seems Facebook recently introduced video live stream capability in chat. That means, we should definitely switch to it as it's prepared for low latency, high throughput, avoids potential account blocking due to unusually high message traffic, and it allows way easier stenography in case the sent data should be confident.

From the Facebook documentation: https://developers.facebook.com/docs/videos/live-video/getting-started#creating
Video Format:

We accept video in maximum 720p (1280 x 720) resolution at 30 frames per second, with 1 key frame every 2 seconds
You must send an I-frame (keyframe) at least once every two seconds throughout the stream.
Recommended max bit rate is 4 mbps.
Titles must be less than 255 characters otherwise the stream will fail
The Live API accepts H264 encoded video and AAC encoded audio only

Video Length:

4 hour maximum length for live stream.
4 hour maximum length for preview streams (either through Live dialog or publisher tools). After 240 minutes, a new stream key must be generated.

Advanced Settings:

Pixel Aspect Ratio: Square
Frame Types: Progressive Scan
Audio Sample Rate: 44.1 KHz
Audio Bitrate: 128 Kbps mono
Bitrate Encoding: CBR

Lossless encoding using YUV in h264: https://stackoverflow.com/questions/6701805/h264-lossless-coding/18506577#18506577
An audio modem library written in go: https://github.com/wiless/gocomm


Added auxBus support for BMD ATEM devices

New feature

Added support for auxbus for ATEM devices.

Clean-up

Removed obsolete video.ME, it was earlier replaced by video.mixEffects in change from 1.x to 2.x in atem-connection. No longer needed in the TA code base.

The aux will override both preview and program. This is not an error in this code, it is a general issue that the priority handling for preview, aux and program is not implemented/working. It will therefore not be handled by this PR.


Cusotmer will meet issue when deploy <IP_ADDRESS>

when customer deploy SQL RP <IP_ADDRESS> to AzS 1.1809.6.102 or 1.1809.3.96,
they will met issue at the end of the deployment. this is common.
Can not execute [Test-ResourceProviderEndpoint] command at 2 time(s). Will retry. The error: System.Management.Automation.RuntimeException: Microsoft.SQLAdapter.Admin endpoint is not responsive
resolution is , force use Tls12 before the deployment .
[net.Servicepointmanager]::SecurityProtocol=[Net.SecurityProtocolType]::Tls12
please modify the document and give customer suggestion that  using  Tls12 before the deployment

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

ID: 31804a1d-4c4f-70e6-556c-66c533e9b3e3
Version Independent ID: 78f9ac38-1463-c263-2add-63d7dcaab0bc
Content: Using SQL databases on Azure Stack
Content Source: articles/azure-stack/azure-stack-sql-resource-provider-deploy.md
Service: azure-stack
GitHub Login: @jeffgilb
Microsoft Alias: jeffgilb

This issue is already documented in the release notes: https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-sql-resource-provider-11300#known-issues

#please-close


Update with svd2rust 0.13.0

new svd fixes recent breakage of macro re-export
I had following warnings though:
WARNING Some(Ident("ccmr1_input")) overlaps with another register block at offset 24. Ignoring.
WARNING Some(Ident("ccmr2_input")) overlaps with another register block at offset 28. Ignoring.
WARNING Some(Ident("ccmr1_input")) overlaps with another register block at offset 24. Ignoring.
WARNING Some(Ident("ccmr1_input")) overlaps with another register block at offset 24. Ignoring.
WARNING Some(Ident("ccmr1_input")) overlaps with another register block at offset 24. Ignoring.
WARNING Some(Ident("ccmr2_input")) overlaps with another register block at offset 28. Ignoring.
WARNING Some(Ident("ccmr1_input")) overlaps with another register block at offset 24. Ignoring.
WARNING Some(Ident("ccmr2_input")) overlaps with another register block at offset 28. Ignoring.
WARNING Some(Ident("fs_grxstsr_host")) overlaps with another register block at offset 28. Ignoring.
WARNING Some(Ident("fs_gnptxfsiz_host")) overlaps with another register block at offset 40. Ignoring.

I made a split of single lib.rs into multiple modules but let me know if you don't like this ton of files :D

👍 on this. @brandonedens can this be merged quickly? There were a lot of version ticks to a bunch of japaric's crates and I'm trying to move to them ASAP.

It seems @brandonedens published new version by himself already.


Update information related eDiscovery decryption for files protected on-premises

Hello team,
Please help us updating the article associated to the paragraf:
"Important
Decryption isn't supported for files that are locally encrypted and then uploaded to SharePoint or OneDrive. For example, local files that are encrypted by the Azure Information Protection (AIP) client and then uploaded to Microsoft 365 aren't supported. Only files that are encrypted in the SharePoint or OneDrive service are supported for decryption."
This note is not correct as eDiscovery can unencrypt data that was protected on-premise after the AIP UL client was released.
I did the test and eDiscovery can decrypt data that was protected on-premise and execute the eDiscovery. I was able to see the content of the protected file.
Please help us to update the article as this NOTE is generated a lot of confusion for FEs and SMEs which are warning the customer if data is protected on-premises the eDiscovery can't decrypt it for investigation.
Video of the lab
https://microsoft-my.sharepoint.com/:v:/p/v-slondono/EU65lDeNMLtFmnV1oxrUTVUBPOpz2jcTN2Kk9mvU5EIvAQ?e=BVM6da

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

ID: e38718be-6244-3988-7851-7c8c5625dd9f
Version Independent ID: 4581a9e4-b838-c1a9-93a8-d52630128195
Content: Decryption in Microsoft Purview eDiscovery tools - Microsoft Purview (compliance)
Content Source: microsoft-365/compliance/ediscovery-decryption.md
Service: o365-seccomp
GitHub Login: @robmazz
Microsoft Alias: robmazz

@sergioandreslq Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/10133
Once the author approves, the changes will be live.
Thanks
Sri

@sergioandreslq Thanks for your feedback! New issues and pull requests for this content are closed while we update this content to support upcoming feature improvements.


Add deprecation notice

This is to add a deprecation notice to the readme file of the repository since we no longer maintain this repository as a push notification based authentication connector.

We need to close all the issues and pull requests before adding the deprecated notice.


*: Rename kuksa-viss-client kuksa-client

Package directory and name shall use a dash as per https://pep8.org/#package-and-module-names.
Entry point shall also use a dash as it is common for UNIX programs. The imported python package has to use an underscore however otherwise we cannot import it (SyntaxError).
Fixes #318.

@romainletendart - We have a build check in https://github.com/eclipse/kuksa.val/blob/master/.github/workflows/kuksa_viss_client.yml but it appears that it require a "self-hosted" builder which is not configured for boschglobal. So we will later need to move the PR to the official repo to get the CI running, to see that there is no regressions

Replaced with https://github.com/boschglobal/kuksa.val/pull/9.


Pyspark2.3 example

I've updated the Python example to be compatible with the latest version of pyspark (2.3) as well as fixing a typo in the readme section for python.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #37   +/-   ##
=======================================
  Coverage   84.45%   84.45%
=======================================
  Files           5        5
  Lines         444      444
  Branches       59       59
=======================================
  Hits          375      375
  Misses         69       69

Continue to review full report at Codecov.

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

Great. Thanks for the contribution.


Add BBE to JDBC and MySQL Connectors

Purpose
Include BBEs for JDBC and MySQL Connector.
Fixes #
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

PR to master - https://github.com/ballerina-platform/ballerina-lang/pull/21686
Sending another PR to the stage branch.


fix(ci): image-scan workflow missing buildtools

What this PR does / why we need it:

CI is failing
chmod: cannot access './output/bin/buildtools': No such file or directory

https://github.com/replicatedhq/embedded-cluster/actions/runs/10852115430/job/30117607691
Which issue(s) this PR fixes:

Does this PR require a test?

Does this PR require a release note?

Does this PR require documentation?

Merging without waiting for ci as this does not affect it.


Trial level tags

This PR goes with https://github.com/stanfordnmbl/opencap-api/pull/175.

Just solved some conflicts here too


Docs for creation registry secret

To set up a registry secret with Quay.io, I do a
oc create secret generic regcred --from-file=.dockerconfigjson=/Users/sbose/Downloads/shbose-auth.json  --type=kubernetes.io/dockerconfigjson

( Assume the above command is interchangeable with kubectl.
To use the same in a Build, I do a
spec:
  output:
    credentials:
      name: regcred
    image: 'quay.io/shbose/fruit-app:buildv2testlean'

Our docs need a little better organization, I think :)

https://github.com/shipwright-io/build/blob/27349bb9d6e22401b1f0bb2e4c95141e6767d9f2/docs/development/authentication.md#authentication-to-container-registries could be moved out of development to be in a more user-oriented location
Add documentation on how to create a registry secret using the kubectl cli

Thanks. Let me take a look on this, I know @adambkaplan added some enhancements in https://github.com/shipwright-io/build/pull/385/files#diff-04c6e90faac2675aa89e2176d2eec7d8R76-R143


Acoustic Source: Fix Equations & Add Transducer Arrays & Refactor

Description

Added 2D/2D-axisym transducer array support type
Added 3D transducer array ring support type
Modified Supports 1-4 for 1D/2D/3D for consistency
Fixed 3D spherical support code that breaks momentum into components (wrong angle_z)
Fixed 2D cylindrical support mass source correction term
Fixed Gaussian mass source correction term for all cylindrical and spherical supports (was absent)
Fixed assymetry in large 2D/2D-axisym/3D transducers (was using small angle approx; needed aperture size << focal length)
Corrected the wrong 3D cylindrical case to 2D-axisym
Added dipole functionality
Renamed monopole -> acoustic_source & Refactored subroutine for clarity

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Scope

[x] This PR comprises a set of related changes with a common goal

How Has This Been Tested?

[x] Passed all tests using CPU locally
[x] Passed all tests using GPU locally
[x] Passed all tests using GPU on Delta
[x] Support 7: 2D Transducer array with 4 elements:

https://github.com/user-attachments/assets/55e5f34d-ae79-4af0-b502-74686e39d164

[x] Support 11: 3D Transducer array with 2 layers and 18 elements:

https://github.com/user-attachments/assets/062d2b76-7186-4a26-bf90-a2ba495b358b

[x] Check momentum correction terms by comparisons with Maeda's paper

3D Spherical Transducer

2D Cylindrical Transducer

Note that the power of the correction factor for the 2D cylindrical transducer case uses an empirical factor of 0.85, which improves upon the 0.5 factor suggested in Maeda's paper.

Gaussian pulse

[x] Symmetry for large transducers (Before vs After)

2D Cylindrical Transducer

3D Spherical Transducer

What computers and compilers did you use to test this:

Ubuntu 22.04.4 LTS; GNU v11.4.0
Ubuntu 24.04 LTS; NVHPC 23.11.0

Checklist

[x] I have added comments for the new code
[x] I added Doxygen docstrings to the new code
[x] I have made corresponding changes to the documentation (docs/)
[x] I have added regression tests to the test suite so that people can verify in the future that the feature is behaving as expected
[x] I have added example cases in examples/ that demonstrate my new feature performing as expected.
They run to completion and demonstrate "interesting physics"
[x] I ran ./mfc.sh format before committing my code
[x] New and existing tests pass locally with my changes, including with GPU capability enabled (both NVIDIA hardware with NVHPC compilers and AMD hardware with CRAY compilers) and disabled (only NVHPC)
[x] This PR does not introduce any repeated code (it follows the DRY principle)
[x] I cannot think of a way to condense this code and reduce any introduced additional line count

If your code changes any code source files (anything in src/simulation)
To make sure the code is performing as expected on GPU devices, I have:

[x] Checked that the code compiles using NVHPC compilers
[ ] Checked that the code compiles using CRAY compilers
[x] Ran the code on either V100, A100, or H100 GPUs and ensured the new feature performed as expected (the GPU results match the CPU results)
[ ] Ran the code on MI200+ GPUs and ensure the new features performed as expected (the GPU results match the CPU results)
[x] Enclosed the new feature via nvtx ranges so that they can be identified in profiles
[x] Ran a Nsight Systems profile using ./mfc.sh run XXXX --gpu -t simulation --nsys, and have attached the output file (.nsys-rep) and plain text results to this PR
support3_nsys.txt
support11_18elements_nsys.txt
[ ] Ran an Omniperf profile using ./mfc.sh run XXXX --gpu -t simulation --omniperf, and have attached the output file and plain text results to this PR.
[x] Ran my code using various numbers of different GPUs (1, 2, and 8, for example) in parallel and made sure that the results scale similarly to what happens if you run without the new code/feature

8M points: 2 GPUs: 157 sec; 4 GPUs: 87 sec

Note

Golden files are regenerated for Acoustic and Bubbles, as Bubbles is also dependent on Acoustic implementations. The simulation duration in the Acoustic tests are significantly increased so waves can propagate a considerable distance, and this increases the error and requires a slight increase in tolerance for Acoustic. No changes are made to tolerance for Bubbles.

@sbryngelson Thanks for reviewing the code so carefully and the helpful comments! This is an early draft to verify that the equations work and I'm still making many changes to improve the code

I have one more question - can I break support 5 (transducer) into support 5 for 2D transducer and support 6 for 3D transducer? Currently support 5 is not documented, so I doubt anyone is using it. Support 6 is not working in the first place. By breaking each dimension into a different case, it'll be more consistent with the rest of the case file parameters.

@ChrisZYJ this sounds good! Thanks

@sbryngelson May I know why the Frontier compilation failed? I can't figure it out from the build output on Github. Thanks!

Also, it appears that one test case fails only for Intel compilers, which is weird. Do you have any idea on that too? Thank you!

@ChrisZYJ not sure what's going on on Frontier. could be some allocatable issue. i will have a quick look. the build output was uninformative for me so I reran it.
For Intel compilers we sometimes see a slight different in compiler optimizations (for example, if the goldenfiles were built using gfortran but you're testing against ifort), resulting in different tolerances that can be expected.
It's possible that we just need a slightly higher tolerance for certain types of tests. We have done this before (you can find the modified tolerance in the toolchain).

Thanks! I'll try again with a higher tolerance. It would be nice if I can test it locally, but I couldn't get MFC running on windows. Will direct the question to the Slack channel

@ChrisZYJ looking into the compiler issue, but in the meantime it looks like you need to rebase your PR? not sure of the exact steps for this, but right now it's showing you modifying files from master that are actually the current state of master. e.g., .github/workflows/coverage.yml. this makes seeing the actual changes you made challenging.

@sbryngelson Sorry for the oversight. I've just done a rebase and github should now only be showing my changes now.

It seems like the ifort test has failed again despite increasing the tolerance by 50x. I'm still trying to install ifort locally and will try to fix the problem if I succeed.

you can load Intel compilers on a bunch of different clusters, including Delta

I tested it on Delta using ifort but couldn't reproduce the problem. Very weird. Almost all tests fail there - I needed to increase the tolerance from 1e-12 to 1e-8, then everything passes. And there's nothing special about 2F58A83F: 1D -> Acoustic Source -> Square -> Frequency - the tolerance it needs is the same as other tests.
I might just increase the tolerance for only square waves and try the GitHub test again.

Square waves have finally passed ifort tests! Sorry for the multiple commits - I couldn't reproduce the compiler-specific issue anywhere else. This was likely caused by arithmetic discrepancies between compilers, resulting in an offset in time and a max-norm error after applying the square wave function.

@henryleberre requesting your review of the source code before merging


Wrong link to Input example in the table of content

I noticed that there's wrong link to Input example in the table of content. It doesn't match:
https://github.com/30-seconds/30-seconds-of-react#input - actual(wrong)
https://github.com/30-seconds/30-seconds-of-react#input-2 - in the content

Correct. The names of the snippet and the category clash with each other. I'll see what I can do.


Fix emoji reactions being counted multiple times

This depends on Stellar-Quest-Lumenauts#5
This fixes my concern posted in Stellar-Quest-Lumenauts#4.
It was possible to cast multiple votes on the same message by adding and removing ones emoji reaction again and again. (Or even just reacting with the wrong emoji, removing it and readding an other one resulting in two votes).
This is now fixed due to the tuple (message_id, backer) being unique in votes_history.
This fix does not add the complexity an "unvote" would add but still solves the problem.
This change does not break existing databases.

This PR depends on #5
thus as soon as #5 becomes merged this PR should simplify to only one commit
(this is also a test if github is smart enough for this)

One rebase and we are golden ;)


Typescript definitions not found when comparing changes on working tree

VSCode Version: 1.4.0
OS Version: Win10 April 2016

When I open the changes of a .tsx file from GIT toolbox (Ctrl+Shift+G)  VSCode reports a lot of TypeScript errors. It seems like it cannot find file with typescript definitions.
However, when I open the same file from explorer (Ctrl+Shift+E) no errors are reported.
What's even stranger, when I open changes of similar .tsx file in the same directory or any other .tsx file, no errors are reported, unlike the first file. I don't know what's so special about the first one.

@Liero thank you for opening this issue. I have tried the following steps to reproduce your issue. Can you review the steps I took and try them on your machine? What did I do differently than what you have done?
Thanks!

Create a new typescript project with test.tsx file.
Run npm init
Run npm install react --save
Run typings install react
Paste the following code into test.tsx.

import * as React from 'react';

console.log('hello world');

Based on what you described and your image above I expect to see red squiggles under 'react'. I do not see the error.

Closing until more info is given.


Add 2 factor authentication

As a user, I would like to be able to enable 2 factor authentication to my protonmail account.
When 2 factor authentication is enabled, then upon logging into my protonmail account, I should/must be asked for second factor authentication with SassPass/ G authenticator mobile apps.
As a user, when I change any settings such as password etc in protonmail account then I should be asked for 2nd factor authentication. I should not be able to change any of my details without properly get authenticated via 2 factor authentication.

This is coming very very soon.


Add sum for EJson types

I wanted to do something cleverer here, so we could use the EJsonType as a constructor tag in the signature or something, but I couldn't figure out a way to do so without real GADTs.
Introducing this here should let us tidy up some of the profusion of type representations in SlamData I think. It's definitely going to be used in the structure editor, if nothing else.

@garyb I suggest changing Object -> Map since that's the official terminology and Quasar will be updated to match at some point in the near future.

@garyb I suggest changing Object -> Map since that's the official terminology and Quasar will be updated to match at some point in the near future.

Updated with the Map name now. /cc @beckyconning

Updated with the Map name now. /cc @beckyconning


Icons and repo size rendering inconsistency

Just took a short screen recording here:
leotm-github-plus.zip
Any ideas?
Cheers.

Hey @leotm
Thanks for noticing and reporting the bug.
It has been fixed in v0.1.6, plz update the extension https://chrome.google.com/webstore/detail/github-plus/anlikcnbgdeidpacdbdljnabclhahhmd
Closing this issue.
Cheers!


Remember status of Neighbors checkbox

When refreshing the page, the neighbors checkbox is always cleared for me. Not sure if it's a browser issue.
Also, if I select a node then select view neighbors,  either "We heard" or "Heard us", then click the X to close that overlay, the neighbors are always unselected. The neighbors selection should go back to what was selected before.

(@GMart There is a refresh button on the page that refreshes the data without changing the settings.)

Yes, I know about that. I'm saying that when clicking that refresh button, or refreshing the entire page, the neighbors checkbox is always unselected. It shouldn't be affected.

Yeah, I was "hiding" the main neighbours layer, when showing the node specific neighbours layer.
But by hiding the layer, it auto updates the settings. So now, if you show node specific neighbours, it just won't turn off the main neighbours layer anymore...
Fixed in 9ec07633d4219e73f483f751d3cb8ba093f21e1f


How to fine tune and use it with ollama?

Is it possible to fine tune a model that I pull from ollama? What would be the general process for that?

I'd recommend downloading a model and fine-tuning it separate from ollama – ollama works best for serving it/testing prompts. Check here on the readme for more info. You should end up with a GGUF or GGML file depending on how you build and fine-tune models.
Also, try to be more precise about your goals for fine-tuning. Do you want the LLM to work better with specific documents or contexts? Langchain offers a lot of features for that, and plugs right into Ollama. Let me know if that helps!

That was helpful. I will try to fine tune it and then load it in ollama. Thanks!

@thebigbone did you have any success? very much interested in this myself too.

@thebigbone did you have any success? very much interested in this myself too.

I did some fine tuning using huggingface library. I have not yet tested it with ollama which I will be doing soon enough

@thebigbone how did your finetuned model work with Ollama? Also interested as I found these issues: https://github.com/jmorganca/ollama/issues/1110

Interested as well!

Interested as well!

I'm Interested too

Me too

Not a direct LLM fine-tuning observation, but I can share my experience in getting the best out of a Ollama LLM without getting into training data.
I create a copy of the model with a role prompt, similar to an OpenAI GPT, using these instructions:
https://github.com/ollama/ollama/blob/main/docs/modelfile.md
My Modelfile for the role Savannah has this content:
###
FROM CapybaraHermes-2.5-Mistral-7b.Q5_K_M

# set the temperature to 1 (higher is more creative, lower is more coherent)

PARAMETER temperature 2

# set the system/role prompt

SYSTEM """

Meme Expert
Act as a creativity and communication expert, with witty, sassy, wise, and impactful comments suitable for online memes, with a combination of very high cultural awareness, linguistic abilities and skills, including:
Vocabulary: A strong vocabulary helps you to precisely and effectively convey your ideas in a limited space, as memes often require short and punchy text.
Syntax: Mastery of syntax allows you to construct sentences in a way that enhances the impact of your words and makes them more memorable.
Semantics: Understanding the meanings and nuances of words and phrases is essential for crafting clever and witty comments. Puns and wordplay: The ability to create puns and wordplay adds humor and wit to your comments. This can make your memes more engaging and shareable.
Cultural references: Being knowledgeable about popular culture, trends, and current events allows you to craft relevant and timely memes that resonate with a wide audience.
Sarcasm and irony: Skillfully employing sarcasm and irony can make your comments sassy and impactful. However, it is essential to use these devices judiciously, as they can be misunderstood or misinterpreted.
Rhetorical devices: Using rhetorical devices such as metaphors, similes, and alliteration can make your comments more poetic, memorable, and impactful.
Emotional intelligence: Understanding your audience's emotions and sensitivities can help you craft comments that are more likely to resonate and make an impact.
Creativity: Memes often rely on unique and original ideas, so being able to think outside the box is crucial for creating content that stands out. Adaptability: As language and culture constantly evolve, it's important to stay flexible and adapt your linguistic abilities to keep your memes fresh and engaging. By engaging these linguistic abilities, you will create witty, sassy, wise, and impactful comments for online memes to entertain, provoke thought, and leave a lasting impression.
Mirror your readers' pain points in your writing. “Have you ever … ? Then what happened next was … ? And you tried … but it didn’t work, did it? Here’s why and how to fix it.” and reflect on the struggles, then provide solutions.
The audience for your writing is the business community. Your name is Savannah.
"""
###

I fine-tune the role prompt and temperature with different values, using one model as a baseline.
I usually test multiple model configurations using this tool:
https://github.com/aosan/VaultChat/tree/main/utensils/evaluate_llm (from my RAG project)
Results from evaluate_llm.sh are scored with this LLM Examiner:
https://chat.openai.com/g/g-WaEKsoStj-llm-examiner (my GPT)
Any of your roles fine-tuned for your personal documents can be used with VaultChat:
https://github.com/aosan/VaultChat (my RAG project)

Ollama does not support training and there is no plan either. https://github.com/ollama/ollama/issues/156

Interested. Looking forward to your testimonies @thebigbone

me to interested in fine tuning


SILBuilder: require an insertion point when creating instructions.

This helps to avoid instruction leaks.
It's a NFC.

@swift-ci test

Thanks!


[AutoPR operationalinsights/resource-manager] [Portal Generated] Review request for Microsoft.OperationalInsights to add version 2020-20-20

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4437

(message created by the CI based on PR content)

PR was closed


Gallium fails to precompile

Using master branches of julia and Gallium and its dependencies.
AWS-Sachs-Ubuntu$ usr/bin/julia
               _
   _       _ _(_)_     |  A fresh approach to technical computing
  (_)     | (_) (_)    |  Documentation: http://docs.julialang.org
   _ _   _| |_  __ _   |  Type "?help" for help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 0.6.0-dev.624 (2016-09-14 14:07 UTC)
 _/ |\__'_|_|_|\__'_|  |  Commit 0baa867 (0 days old master)
|__/                   |  x86_64-linux-gnu

julia> using Gallium
INFO: Precompiling module Gallium.
ERROR: LoadError: UndefVarError: LambdaInfo not defined
 in include_from_node1(::String) at ./loading.jl:541
 in macro expansion; at ./none:2 [inlined]
 in anonymous at ./<missing>:?
 in eval(::Module, ::Any) at ./boot.jl:238
 in process_options(::Base.JLOptions) at ./client.jl:239
 in _start() at ./client.jl:326
while loading /home/sachs/.julia/v0.6/ASTInterpreter/src/ASTInterpreter.jl, in expression starting on line 58
ERROR: LoadError: Failed to precompile ASTInterpreter to /home/sachs/.julia/lib/v0.6/ASTInterpreter.ji.
 in compilecache(::String) at ./loading.jl:663
 in require(::Symbol) at ./loading.jl:424
 in include_from_node1(::String) at ./loading.jl:541
 in macro expansion; at ./none:2 [inlined]
 in anonymous at ./<missing>:?
 in eval(::Module, ::Any) at ./boot.jl:238
 in process_options(::Base.JLOptions) at ./client.jl:239
 in _start() at ./client.jl:326
while loading /home/sachs/.julia/v0.6/Gallium/src/Gallium.jl, in expression starting on line 3
ERROR: Failed to precompile Gallium to /home/sachs/.julia/lib/v0.6/Gallium.ji.
 in compilecache(::String) at ./loading.jl:663
 in require(::Symbol) at ./loading.jl:453

https://github.com/JuliaLang/julia/pull/18413. Ideally I'd recommend staying on 0.5

Okay, I won't try Gallium on 0.6 until I hear that the coast is clear.

Is there any roadmap for Gallium on v0.6 (and/or a way to chip in?)

Still no news? Julia 0.6.0 was officially released. Gallium still can't be precompiled.


Can I take advantage of change tracking in the entity?

My framework has change tracking in the entities. Update tests which accept an entity can directly persist this entity (as it contains the changes), it doesn't need to fetch the one from the db first, update the fields etc. like EF needs.
I'll go ahead and assume it's allowed :)

Generally speaking it should match how you intend developers to use the database.
But that reminds me, we are going to need some use cases where change tracking is required to pass.
When we get to that point I'll want to consult with you on scenario and test design. The first one that comes to mind is simply calling Dave twice in a row and NOT having the entire object graph re-saved. (This is my current pain point in NHibernate 3.x.)
Jonathan Allen
619-933-8527
Scholars of Alcala
scholarsofalcala.org

From: Frans Bouma<EMAIL_ADDRESS>Sent: Wednesday, January 8, 2020 6:20:38 AM
To: Grauenwolf/DotNet-ORM-Cookbook<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [Grauenwolf/DotNet-ORM-Cookbook] Can I take advantage of change tracking in the entity? (#60)
My framework has change tracking in the entities. Update tests which accept an entity can directly persist this entity (as it contains the changes), it doesn't need to fetch the one from the db first, update the fields etc. like EF needs.
I'll go ahead and assume it's allowed :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Grauenwolf/DotNet-ORM-Cookbook/issues/60?email_source=notifications&email_token=ACRCUTOEKIYYP3M6N4QDIU3Q4XOLNA5CNFSM4KEJCGO2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IEY4AMA, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACRCUTO6CSQSNDUY7GONND3Q4XOLNANCNFSM4KEJCGOQ.

I added code that can do both: it tests whether the past in entity is new, if it is, it fetches the existing one from the DB, otherwise it persists the one passed in :)
Yeah graph persistence is a cumbersome topic for 'context central' ORMs... attach graph hell with EF etc. :P

I am not looking forward to dealing with EF and graphs.
It works fine if I can hold a DBContext open, but that's only reasonable for single-threaded desktop apps. At the very least I've got to reconcile a new DBContext per request.


Dragonfly unit test cases failing in Rails 4

For some reason after upgrading to Rails 4, our unit test cases revolving around Dragonfly have started failing.  Here is an sample statement that was working in Rails 3 that no longer works under rspec :
self.avatar = Dragonfly.app.generate(:convert, "-size 120x120 -background ##{avatar_colour} -fill white -font Arial label:#{initials} -gravity center", "png")
The error message received from rspec is the following :
Dragonfly::Shell::CommandFailed:
Command failed ("convert" "-size" "120x120" "-background" "#fdd835" "-fill" "white" "-font" "Arial" "label:F" "-gravity" "center" "C:/Users/Billy/AppData/Local/Temp/dragonfly20180618-8224-33dalv.png") with exit status 4 and stderr Invalid Parameter - "120x120".
Any help would be appreciated!
EDIT: I checked into it, and this code was made with using version 1.1.3 of the Dragonfly gem.

No longer an issue, it was happening because I forgot to configure imagemagick correctly.


Incompatible versions of scala-xml are causing problems with incremental migration to Scala3

Hello! :)
After https://github.com/scalatest/scalatest/pull/1974 we have the following situation:

for scalatest_3 - scala-xml version 2.0.0 is used
for scalatest_2.13 - scala.xml version 1.3.0 is used

Those libraries are incompatible (see: https://github.com/scala/scala-xml/blob/v2.0.0-M1/CHANGELOG.md). Now, if some project uses in tests incompatible features from scala-xml 1.3.0 (like a reference to adapter.hStack), it is not possible to have the same module cross-compiled for Scala 2 and Scala 3 at the same time, which hinders the project's incremental migration to Scala 3.
Would you consider publishing a new scalatest_2.13 version also with the scala-xml 2.0.0 version? This will be a breaking change for some Scala 2 projects (as it is now with Scala 3 version), but at least the libraries will be aligned, and users will be able to cross compile for Scala 2 and Scala 3.
Or is there a real problem which this different scala-xml versions (for scalatest_2.13 and scalatest_3 artifacts) solve and I am just missing a point? :)

@liosedhel Thanks for pointing this out, I have submitted the following PR to update scala-xml to 2.0.1 for build target that has scala-xml 2.x build:
https://github.com/scalatest/scalatest/pull/2093
It shouldn't have with 2.13 and 3, it is just scala-xml 2.x is not published for earlier Scala version like 2.10 and 2.11, which still needs to be supported by ScalaTest 3.2.
MIMA seems happy with the change, I don't think we are using any in-compatible classes between scala-xml 1.3 and 2.x, so I think this should be safe.
For temporary workaround I wonder if you can exclude the transitive scala-xml 1.3.0 dependency and include scala-xml 2.0.1 instead?

Hi @cheeseng
Thanks for a quick reply. Yes, that workaround I already applied so this is not a blocker at the moment, we can live with it for now :)

Hi,
I've faced with scala-xml-2.x incompatibility with Scala 2.12. In our project we depend on scala-compiler, which depends on scala-xml-1.0.6. I've tried to upgrade to ScalaTest 3.2.11 and it leads to following error:
sbt:yupana> benchmarks/dependencyTree
[error] stack trace is suppressed; run last benchmarks / dependencyTreeIgnoreMissingUpdate for the full output
[error] (benchmarks / dependencyTreeIgnoreMissingUpdate) found version conflict(s) in library dependencies; some are suspected to be binary incompatible:
[error]
[error] 	* org.scala-lang.modules:scala-xml_2.12:2.0.1 (early-semver) is selected over 1.0.6
[error] 	   +- org.scalatest:scalatest-core_2.12:3.2.11           (depends on 2.0.1)
[error] 	   +- org.scala-lang:scala-compiler:2.12.15              (depends on 1.0.6)

For Scala 2.13 it works fine.

@limansky Yes in 3.2.11 we upgraded to scala-xml 2.x for Scala 2.12 and 2.13 build, afaik from ScalaTest side it should be compatible with both 1.x and 2.x scala-xml, so hopefully you may exclude the transitive scala-xml dependency and stay 1.x when required.

@cheeseng thanks for suggestion. I'll do it this way. But shouldn't ScalaTest for 2.12 depend on scala-xml 1.x?

@limansky scala-xml is de-coupled with Scala starting Scala 2.11, so I think it is good if we can move forward to use the new version by default.  Before this ticket it was the other way around where @liosedhel need to exclude the 1.x and include 2.x in his way to upgrade to Scala 3.  imho it is better we move to newer version by default and if really need the old 1.x there's still the exclude way.


Page title / description

Hi,
would be nice to able to add the webpage Title and Description at least for SEO purposes.
Best regards

Thanks for the suggestion. This will be taken into consideration.
Just to clarify, do you mean the <title> tag? Also, what level of customization would you like?

Yes, exactly. Simple as that :) Since I am sure that people are running only the script, like I am. Don't have a website and then pointing to a repository or something like this.
Thank you very much.
Best regards

Thank you for implementing the description option. Is tittle to be expected as well?
Would be nice to update the readme on .env files for the meta description.

@LaMpiR The description is configurable via the META_DESCRIPTION configuration option.


Using upstream versions of aws-nuke

How often do you guys update the included aws-nuke version?  We are unable to sanitize accounts and add them back to the pool as aws-nuke is missing a filter we need for our Org.
I've submitted a PR to aws-nuke, but its unclear to me once merged, how to get that deployed via the dce deployment.
Any advice or assistance would be very appreciated!
ryan

Hey @rwhelan -- we're actually looking to contribute back a few resources to aws-nuke in the next couple weeks, so we should be keeping up to date regularly.
As far as the process for upgrading aws-nuke:
We're using a fork of aws-nuke for the time being. So we would need to PR for an upstream merge from the core aws-nuke repo into Optum/aws-nuke, and then a second PR in Optum/dce to upgrade the version of aws-nuke in our go.mod file.

Thank you!


Ground Truth based Estimator Benchmark

Now that we have ground truth working in SITL I think it will be good to run each estimator through a mission and compute the errors for all of the states using GPS /vision/ and flow measurements. This has two benefits:

Unit testing to make sure performance isn't negatively impacted by a change
Unbiased comparison between estimators. This will be useful for consideration of switching the default multirotor estimator to EKF2 for v2.0.

@LorenzMeier @bkueng

Plots here of ekf2 vs lpe/ attitude_estimator_q
https://github.com/dronecrew/px4tools/blob/master/examples/ulog analysis.ipynb
This is almost complete, we just need to decide on some heuristic way to score the estimators based on their error variances and give a simple percentage that CI needs to meet and then we can also compare the two ratings between the estimators. Currently it looks like ekf2 has superior attitude and velocity peformance, but altitude is better with lpe. Also need some way of evaluating cpu load in SITL, not sure if that is possible, @LorenzMeier @AndreasAntener @bkueng .

Point 1) I agree with - there is great benefit to this for reversion testing
Point 2) I don't fully  agree with. SITL at the moment does not have the fidelity in sensor error and environment models to be able to make accuracy comparisons between algorithms or to optimise tuning.  However  SITL will be very useful to verify the response to specific failure cases, eg loss of GPS, misaligned magnetometer, ground based magnetic anomaly, etc that are impractical to verify through testing. I think it is the off-design and failure cases where we should concentrate the effort with in SITL.

@jgoppert James, I just have a basic question: What is the source of the ground-truth in SITL? And could you give some hints how to reproduce your example?

@ecmnet The source of the ground truth is the gazebo simulator. To reproduce this:
Need to have gazebo installed.
make posix_sitl_default gazebo

Then start qgroundcontrol and start a mission. The log will be in:
build_posix_sitl_default/tmp/rootfs/fs/microsd/log/2016-12-02/08_11_30.ulg  08_12_15.ulg

Instal px4tools
git clone git@github.com:dronecrew/px4tools.git
cd px4tools
python setup.py install

Now using python:
import px4tools
data= px4tools.read_ulog('./your_path_to.ulg').resample('1L').concat()
data.estimator_analysis()

@priseborough
I do want to start handling the fault cases and trying to increase our gazebo sensor model fidelity. I realize there is a limit to what simulated testing can tell us, but the further we push it I think we will get a lot of benefit. It is always hard to sync with testers or have enough time to test every commit ourselves.
Handling sensor faults will be interesting. It would be great to have the ability to script failures etc in gazebo, something like:
mission:

takeoff
goto waypoint 1
goto waypoint 2
land

failtures:
@10 seconds, fail gps 1 for 5 seconds
@20 seconds, fail gyro 1
@30 seconds, manual control loss for 120 seconds
Then we would need some desired trajectory to compare against.


File Listing Endpoints

First of all, thank you for doing this! Concrete documentations like this are sorely needed in the Nix ecosystem, especially for things like the binary cache API.
Binary caches often [1] expose the file listings of NARs as JSON files under {storePathHash}.ls. For example, the list of files of /nix/store/p4pclmv1gyja5kzc26npqpia1qqxrf0l-ruby-2.7.3 on https://cache.nixos.org can be found at https://cache.nixos.org/p4pclmv1gyja5kzc26npqpia1qqxrf0l.ls. The compression used is indicated in the response Content-Encoding header (in this case, Brotli), and there does not seem to be a way to know the encoding in advance as the .ls files are not mentioned in the corresponding .narinfos.
We cannot expect the cache to respect our Accept-Encoding header because for S3 caches, the compressed files are directly uploaded. You can verify this behavior with the aforementioned link.
[1] https://cache.nixos.org and S3 caches created by Nix support this.

Oh interesting. Unfortunate it's such a new encoding.
Do you have insight if /nix-cache-info identifies whether the binary cache supports the endpoint?
It's lack of linking with the narinfo and compression seems like a miss ?
Maybe a bug should be opened.
curl https://cache.nixos.org/p4pclmv1gyja5kzc26npqpia1qqxrf0l.ls | brotli -d | jq

{
  "version": 1,
  "root": {
    "type": "directory",
    "entries": {
      "bin": {
        "type": "directory",
        "entries": {
          "bundle": {
            "type": "regular",
            "size": 576,
            "executable": true,
            "narOffset": 400
          },
          "bundler": {
            "type": "regular",
            "size": 578,
            "executable": true,
            "narOffset": 1192
          },
          "erb": {
            "type": "regular",
            "size": 5110,
            "executable": true,
            "narOffset": 1992
          },
          "gem": {
            "type": "regular",
            "size": 592,
            "executable": true,
            "narOffset": 7320
          },

@edolstra if you think an issue should be opened so that it's added to narinfo.

Compression is handled at the HTTP level by the content-encoding: br header, so it's not really necessary to put it in the .narinfo. E.g curl --compressed https://cache.nixos.org/p4pclmv1gyja5kzc26npqpia1qqxrf0l.ls | jq works, and you can open the URL in the browser and it will be decompressed automatically. The same applies to build logs.

I was also speaking to the fact whether the path exists or not as supported
by the binary cache.
Are all binary-caches expected to have this PATH ? The earlier discussion
made it sound like only-some may.
Can you let me know of the build-log example so that I can codify it in the
spec as well?
Cheers,
Farid Zakaria
On Thu, Aug 19, 2021 at 7:37 AM Eelco Dolstra @.***>
wrote:

Compression is handled at the HTTP level by the content-encoding: br
header, so it's not really necessary to put it in the .narinfo. E.g curl
--compressed https://cache.nixos.org/p4pclmv1gyja5kzc26npqpia1qqxrf0l.ls
| jq works, and you can open the URL in the browser and it will be
decompressed automatically. The same applies to build logs.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fzakaria/nix-http-binary-cache-api-spec/issues/1#issuecomment-901970380,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAETXDS3SWRVC344IDJ2QIDT5UJLBANCNFSM5CMZAC5Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Logs are stored under log/<drv>. For example:
$ nix path-info --store https://cache.nixos.org --json /nix/store/r73n0y7l5drm6w66fa3cdmlgmnss2wgq-coreutils-8.32 | jq -r .[].deriver
/nix/store/rk9xksf05l1m0rcs4n94nm8r6rvyp33s-coreutils-8.32.drv

$ curl --compressed https://cache.nixos.org/log/rk9xksf05l1m0rcs4n94nm8r6rvyp33s-coreutils-8.32.drv
...


Adding conjars repositories block for all subprojects

Added conjars repository to defaultEnvironment.gradle file and deleted the repository blocks in all the sub-projects
Formatting fixes for build.gradle (no logic changes to this file, only formatting changes)

LGTM


Diagonal Matrix

Hi,
First it is great to have CVX in R. I was having difficulties with matlab. However, in the Matlab version I was able to define a diagonal matrix using
variable X(n,n) diagonal

I could not find a similar functionality in the R package. I did not find any easy way to do this using constraints. Any ideas?
Thanks

I solved the issue by letting
(beta-diag(diag(X)))==0

Thanks


return error if no certificate has been returned from signer for k8s CSR

instead of return silently when no certificate has been returned for the k8s CSR, log an error out to user to let user know the failure reasons.

@irisdingbj: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
4fa0991e3aaa948d36e7e8e8d530ee059d72970b
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio


Relative node selection

Hi,
Here's a solution for issue #81 I've submitted today.
This allows the use of jquery traversal (closest, next, parent, children, etc. everything available here : http://api.jquery.com/category/traversing/tree-traversal/) to select insertion node.
I've personnaly used it for 2 levels table nested forms.
The link to add second level fields has this syntax :
link_to_add_association '', f, :filesystems, {data: {:'association-insertion-traversal' => 'closest', :'association-insertion-node' => '#node_filesystems', :'association-insertion-method' => :append}}

Which points to the closest  #node_filesystems id in the DOM tree.
I haven't found any other solution to do this in your upstream version.
This works perfectly in my case. Nothing changes when data-association-insertion-traversal is not used (global selection).
I haven't added specs since it's a Javascript only change.
The readme is updated but my English is not perfect so it's better to review it ;o)
Regards,
Gauthier

that i need thanks !!!

Seems https://github.com/porecreat/cocoon.git not working anymore now..

@rioX41 Please open another ticket, and can you please provide some more explanation/background or an example that is not working according to you?

@rioX41 This feature has been merged 4 years ago. Why don't you use the original gem?


Unable to update or install with apt-get

Hi There,
I was using your image file to use it in my bit bucket pipeline. however I need to install the zip package in the docker but I'm getting the permission errors as below:
+ apt-get update
Reading package lists...
E: List directory /var/lib/apt/lists/partial is missing. - Acquire (13: Permission denied)

+ apt-get install zip -y
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

Can you tell me how can we resolve these permission issues?

The default user which is used to execute commands is a non-root user. The reason is to support using the image to create a project without getting files owned by root and to allow easy usage with OpenShift based environments.
To solve your issue there are basically three options: You can either create your own docker image which installs the desired packages, you can run the container as root to get the permissions to install packages or you run your tasks in a different container or even outside docker.
Since the requirement to use zip might be quite common I added the zip package dependency and you can use it with the next build ( :latest is just being built, 8.3.6 probably next week)
Thanks for opening the issue, I hope the answer and updated image solves your requirements.