Copy-DbaLogin - Dynamically changing default database if missing

Type of Change

[x] Bug fix (non-breaking change, fixes #6860 )
[ ] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[x] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Allow users to copy logins that have weird default databases
Approach
Check for DB existence, replace with master if not found, display a warning.

Relevant tests pass 💯

thank youuuuu!


Can CascadeClassifier be created with an xml string instead of a file location?

I am using the OpenCVSharp4 wasm runtime with Blazor WenAssembly and I am having trouble creating a CascadeClassifier using a relative link to the xml file. I am guessing it is because the OpenCVSharp is assuming it's a local file, but it's a relative http path.
So my question:
Can CascadeClassifier be created with an xml string instead of a file location?
Thank you.

The native C++ CascadeClassifier does not seem to have a function to initialize from an XML string.
https://github.com/opencv/opencv/blob/b4b35cff15041c9a2795c749a8dfcffc317acefc/modules/objdetect/include/opencv2/objdetect.hpp#L232
This internal OpenCV implementation may be helpful: https://github.com/opencv/opencv/blob/8b4fa2605e1155bbef0d906bb1f272ec06d7796e/modules/objdetect/src/ cascadedetect.cpp#L934

Thank you for the fast reply. I will take a look and see if I can figure out a way.

Looking at modules\objdetect\src\cascadedetect.cpp CascadeClassifierImpl::load and CascadeClassifierImpl::read I can see how to make a FileStorage, then get the root FileNode with GetFirstTopLevelNode, and then use the CascadeClassifier.Read(FileNode fileNode) method to load it. But the created CascadeClassifier throws an exception if I call DetectMultiScale on it. Any help is appreciated.
var newfs = new FileStorage(".xml", FileStorage.Modes.Memory | FileStorage.Modes.Write);
newfs.Open(xmlString, FileStorage.Modes.Read | FileStorage.Modes.Memory);
if (newfs.IsOpened())
{
    // The below line returns the xmlString I wrote so it looks like it worked
    //var xmlTest = FileStorage.ReleaseAndGetString();
    RootNode = newfs.GetFirstTopLevelNode();
    if (RootNode != null)
    {
        var cascade = new CascadeClassifier();
        if (cascade.Read(RootNode))
        {
            // gets here without any problems
            // but errors when I try top use the CascadeClassifier (I have verified grayImage is valid)
            var faces = cascade.DetectMultiScale(grayImage, 1.3, 5);
            // never gets here ...
        }
    }
}

I just tested in a fresh .Net 7 console project and the above code is working. Full example below.
using OpenCvSharp;

using var srcImage = Cv2.ImRead(@"media\test-image-1.jpg");
using var grayImage = srcImage.CvtColor(ColorConversionCodes.BGR2GRAY);
var xmlString = File.ReadAllText(@"haarcascades\haarcascade_frontalface_default.xml");
var newfs = new FileStorage(".xml", FileStorage.Modes.Memory | FileStorage.Modes.Write);
newfs.Open(xmlString, FileStorage.Modes.Read | FileStorage.Modes.Memory);
if (newfs.IsOpened())
{
    // The below line returns the xmlString I wrote so it looks like it worked
    //var xmlTest = FileStorage.ReleaseAndGetString();
    var RootNode = newfs.GetFirstTopLevelNode();
    if (RootNode != null)
    {
        var cascade = new CascadeClassifier();
        if (cascade.Read(RootNode))
        {
            // gets here without any problems
            // but errors when I try top use the CascadeClassifier (I have verified grayImage is valid)
            var faces = cascade.DetectMultiScale(grayImage, 1.3, 5);
            // gets here in .Net 7 console app but not wasm app
            var count = faces.Length;
        }
    }
}

The exception it causes in Blazor wasm can't be caugght with a try catch block. It show and error in the console though
dotnet..0o06bbrt2r.js:5 Uncaught (in promise) Error: Assert failed: Value is not an Error number
    at eo (dotnet..0o06bbrt2r.js:5:29152)
    at b.javaScriptExports.complete_task (dotnet..0o06bbrt2r.js:5:59170)
    at dotnet..0o06bbrt2r.js:5:28913

I'll keep digging.

I think it may be an issue with the OpenCVSharp4 wasm runtime as that is the key difference. I wrote a minimal Blazor wasm app to test as identical code as possible in Blazor wasm and .Net console app both using .Net 7 and the same version of OpenCVSharp4. The only difference was the runtime and it is working in the console app.
I also think I found a bug in OpenCVSharp4 wasm. Cv2.ImDecode, and Mat.FromImageBytes are returning the wrong type of Mat. See below example code for me details. Identical files were used in both test apps.
(I define CONSOLEAPP in my console app)
#if CONSOLEAPP
var xmlString = File.ReadAllText(@"haarcascades\haarcascade_frontalface_default.xml");
var srcImageBytes = File.ReadAllBytes(@"media\test-image-2.png");
using var srcImage = Cv2.ImDecode(srcImageBytes, ImreadModes.Color);
var matType = srcImage.Type().ToString();
// matType == "CV_8UC3"
#else
var xmlString = await httpClient.GetStringAsync(@"haarcascades/haarcascade_frontalface_default.xml");
var srcImageBytes = await httpClient.GetByteArrayAsync(@"media/test-image-2.png");
using var srcImage = Cv2.ImDecode(srcImageBytes, ImreadModes.Color);
var channels = srcImage.Type().ToString();
// matType == "CV_8UC1" - Should be "CV_8UC3"
#endif


QSApp.com is down

Combined with the lack of any ticket closures since May, does this signal that Quicksilver is no longer under active development?

No, it just means something funny is going on with our registrar.

 It is for me.


Fix StopIteration Exception for django-bootstrap3 field without choices

When using ChainedModelChoiceField for a field which has no choices,
in conjunction with django-bootstrap3, a StopIteration Exception is
thrown while trying to identify the default empty label. Replace
This commit is the same functional diff as SerhiyRomanov@275c46098a4151a806652b885454310a9addfd05
for #198 but reapplied against current master.

Applied to the wrong repository, whoops.


add voices #141 #23

Added a drop-down menu to select the voices.
Thanks for contributing. Your contribution might help someone understand the concepts better.
However, to make sure things are working properly, here's a checklist. Just make sure you check them.

[x] I am reading these checkboxes.
[x] Read contribution guidelines
[x] Screenshots

This is awesome :sunglasses:
I love it :heart:
Could you just reduce the text box size,it looks a bit too big.

Ok sure However in my opinion that's ok...

Yes
But i'm not a big fan of this

Plus users only change voice once or twice. They shouldnt have to see things that they dont use very often. So a lesser size would work .

@gauthamzz I decreased the font-size but that doesn't work. So, I changed the css to overflow-y: hidden that worked.
with small text and simple box

with css overflow property

yeah that works.
so you cant make the text box smaller, its fine . we can do that as another issue

@gauthamzz completed.

Great work, thanks :+1:


[feature request] default = None for nullable fields that evaluate to Optional[T] in Python model

Ariadne has been very useful for our team which uses GraphQL backed by Python services.
When we add new fields to a type, existing records in our underlying database (DynamoDB) do not have the new attribute - so we run into a ValidationError (missing) when creating a Python object with newly generated Pydantic model. The fix for this would be to add the default = None for attributes that are Optional, which allows creation of the model class instance to continue even if the new attribute is not in the old record.
Is there already a way to do this that we're not leveraging properly?
# In schema.graphql which is our config `schema_path`
type Location {
  locationId: ID!
  parentId: ID
  name: String
  fullName: String
}

# In queries.graphql which is our config `queries_path`
fragment Location on Location {
  locationId
  parentId
  name
}

After running codegen we get:
# generated/fragments.py
class Location(BaseModel):
    locationId: str
    parentId: Optional[str]
    name: Optional[str]

We'd like:
# generated/fragments.py
class Location(BaseModel):
    locationId: str
    parentId: Optional[str] = None
    name: Optional[str] = None

Thank you for the idea! It looks like it will be easy to implement. I'm adding this to my list of things to work on right now.


Update dependencies to address security issues

See https://github.com/ceph/teuthology/network/alerts
@kshtsk, do you have any interest and/or ability to give this branch a little testing, to make sure it doesn't break things on your end? These looked fine on ours:
http://pulpito.ceph.com/yuriw-2019-06-04_22:25:38-smoke-mimic-distro-basic-smithi/
http://pulpito.ceph.com/yuriw-2019-06-04_22:26:36-smoke-master-distro-basic-smithi/

Who am I to naysay pip-compile?  Looks....to me.

@zmc I will try and run the deployment test for it.

https://github.com/ceph/teuthology/commit/629f343dde18c2fad371bca0963b731c6e85b079 broke ceph-cm-ansible on Trusty.  Hitting https://github.com/ansible/ansible/issues/43246.
I don't know if it matters all that much.  Just thought it merited documenting.

@djgalloway wonder if trusty can be outdated already, it is 14.04 its, as I understand?

I'm fine with it but it's not really my call :innocent:


single sign on

does/will beast http/websocket support any kind of single sign on (e.g. spnego)?

No, but someone else can write it as a library using Beast's message container and then people could import it. Maybe you could do that!

Is this still an issue?

This ticket was just a question and you gave an answer -> issue closed.


indexed data not match with https://sancho.cexplorer.io/

I indexed the Sanchonet network, but I noticed that the hash from block 1,304,463 does not match the data on sancho.cexplorer.io.
My Indexed Data:
Block: 1304494
Slot: 5
Block Data: "binary data"
Previous Block: 1304463
Epoch: 301
Transaction Count: 26092729
Transaction Data: "binary data"
VRF Result: 0
Hash: \xda0c4f19c2a1c9c13ce1aff369198029dbd29156d34b690f1f238e86d638d798

Data from sancho.cexplorer.io:

There are two different hashes. Can you help me resolve this discrepancy?

This format clearly presents your issue and includes all necessary details for someone to understand and help you.

It looks like at the time you created your issue, the cexplorer sanchonet was stuck on a fork and stopped syncing blocks. I tried checking in again to see if the issue persists, but it looks like their sanchonet support is unavailable at the moment


implement flange.from_os_env()

for quick creation of flange object based only on env vars

done in 0.0.4


Test case 15 failed

I got this when trying cpanm Sentry::Raven:
t/11-generic-event.t ...... ok
t/12-specialized-event.t .. ok
t/13-service-call.t ....... ok
t/14-does-not-die.t ....... ok

    #   Failed test at t/15-error-handler.t line 58.
    #          got: '8'
    #     expected: '7'

    #   Failed test at t/15-error-handler.t line 60.
    #          got: 'Sentry::Raven::__ANON__'
    #     expected: 'main::c'

    #   Failed test at t/15-error-handler.t line 61.
    #          got: 'Sentry::Raven'
    #     expected: 'main'

    #   Failed test at t/15-error-handler.t line 62.
    #          got: '/home/wqmisc/.cpanm/work/1598799198.18017/Sentry-Raven-1.13/blib/lib/Sentry/Raven.pm'
    #     expected: 't/15-error-handler.t'

    #   Failed test at t/15-error-handler.t line 63.
    #          got: 'Raven.pm'
    #     expected: '15-error-handler.t'

    #   Failed test at t/15-error-handler.t line 64.
    #          got: '239'
    #     expected: '34'
    # Looks like you failed 6 tests of 6.

#   Failed test 'stacktrace'
#   at t/15-error-handler.t line 65.
# Looks like you failed 1 test of 5.

Perl version is 5.16.2

Looking into this now.  My guess is older perl stack traces look a little different...

I'm not sure what is different in your case.  Perhaps something is different about your perl build or environment.  I cannot reproduce this, but I can make the tests more general which should allow you to get farther.  This will be in version 1.14 which is going out shortly.


Fix spurious CI Failure

Seen in master CI run: https://github.com/wcampbell0x2a/backhand/actions/runs/6999776418/job/19039512489
running 3 tests
test test_non_standard_be_v4_1 ... FAILED
test test_custom_compressor ... ok
test test_non_standard_be_v4_0 ... ok

failures:

---- test_non_standard_be_v4_1 stdout ----
Fetching file squashfs_v4.nopad.unblob.bin ...[/cargo/git/checkouts/test-assets-af055f640a5e3329/ebe2e7d/src/lib.rs:137] &tfile.url = "https://wcampbell.dev/squashfs/testing/test_custom/squashfs_v4.nopad.unblob.bin"
  => Success
thread 'test_non_standard_be_v4_1' panicked at backhand-test/tests/non_standard.rs:58:10:
called `Result::unwrap()` on an `Err` value: StdIo(Custom { kind: InvalidInput, error: "corrupt deflate stream" })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    test_non_standard_be_v4_1

test result: FAILED. 2 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.23s

Another: https://github.com/wcampbell0x2a/backhand/actions/runs/6938385541/job/18874024737

Related for debugging this, add a Cross.toml with:
[build.env]
passthrough = [
    "RUST_LOG",
]

Following bash script will run until it finds it. Maybe it's a external library problem?
while cargo clean && rm -rf backhand-test/test-assets && cross build --no-default-features --features gzip --target x86_64-unknown-linux-musl --release --locked --workspace && CROSS_CONTAINER_OPTS="--network host" RUST_LOG=trace cross test --workspace --release --no-default-features --features gzip --target x86_64-unknown-linux-musl --locked --features __test_unsquashfs -- --skip slow; do :; done

024-01-09T02:39:40.481824Z  INFO backhand::filesystem::writer: Writing Inodes
2024-01-09T02:39:40.481857Z TRACE backhand::metadata: time to compress
2024-01-09T02:39:40.482419Z TRACE backhand::metadata: new metadata start: 0x42
2024-01-09T02:39:40.482425Z TRACE backhand::metadata: LEN: 00
2024-01-09T02:39:40.482436Z TRACE backhand::metadata: len: 40
2024-01-09T02:39:40.482441Z  INFO backhand::filesystem::writer: Writing Dirs
2024-01-09T02:39:40.482459Z TRACE backhand::metadata: time to compress
2024-01-09T02:39:40.482983Z TRACE backhand::metadata: new metadata start: 0x42
2024-01-09T02:39:40.482995Z TRACE backhand::metadata: LEN: 00
2024-01-09T02:39:40.483000Z TRACE backhand::metadata: len: 40
2024-01-09T02:39:40.483011Z  INFO backhand::filesystem::writer: Writing Frag Lookup Table
2024-01-09T02:39:40.483045Z  INFO backhand::filesystem::writer: Writing Id Lookup Table
2024-01-09T02:39:40.483065Z  INFO backhand::filesystem::writer: Finalize Superblock and End Bytes
2024-01-09T02:39:40.483074Z  INFO backhand::filesystem::writer: Writing Padding
2024-01-09T02:39:40.483130Z  INFO backhand::filesystem::writer: Writing Superblock
2024-01-09T02:39:40.483140Z  INFO backhand::filesystem::writer: Writing Finished
2024-01-09T02:39:40.483155Z  INFO backhand::filesystem::writer: Success
2024-01-09T02:39:40.483256Z  INFO non_standard: calling from_reader
2024-01-09T02:39:40.483280Z  INFO backhand::squashfs: Reading Compression options
2024-01-09T02:39:40.483290Z  INFO backhand::squashfs: compression_options: None
2024-01-09T02:39:40.483303Z  INFO backhand::squashfs: Reading Inodes
2024-01-09T02:39:40.483317Z TRACE backhand::reader: offset: Ok(79)
2024-01-09T02:39:40.483328Z TRACE backhand::metadata: [00, 00]
2024-01-09T02:39:40.483331Z TRACE backhand::metadata: len: 0x00
2024-01-09T02:39:40.483334Z TRACE backhand::metadata: compressed
thread 'test_non_standard_be_v4_1' panicked at backhand-test/tests/non_standard.rs:58:10:
called `Result::unwrap()` on an `Err` value: StdIo(Custom { kind: InvalidInput, error: "corrupt deflate stream" })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Closed with https://github.com/wcampbell0x2a/backhand/pull/412


added patient schema from csv-generator #64

This is my first crack at a functional patient data JSON Schema per https://github.com/CDCgov/prime-central/issues/64 - I've added it to CSV Generator also but wanted to pump it in here for review and possible integration with other features.
I've done an initial attempt at syncing all the Patient records specifically from the airtable.

Gonna go ahead and merge this and we can keep iterating as needed.


Python backport: add log_any()

What
Note: best reviewed commit by commit—ignore "Codegen" commits.
This PR is a first step towards a codegen'd python backport, and introduce rr.log_any(). It also introduce slight modifications to the (generated) Python SDK, including:

metadata to archetype's fields (exploited by log_any())
added base classes for Archetypes and Components
added splat() helper to InstanceKeyArray

Note that my next PR will consist of a much more heavy-handed pass over the generated Python.
I made the decision for rr.log_any() because rr.log is already a (de facto public) sub-package and I'd rather break things around this at a latter stage, at which point we can rename rr.log_any() into rr.log().
Also included:

api_demo updated to log 2D points with the new API
super basic test of log_any()

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested demo.rerun.io (if applicable)

PR Build Summary
Docs preview
Examples preview

@teh-cmc Any idea why CI fails? I'm pretty much certain that the codegen is in sync (it was on my computer).

@teh-cmc Any idea why CI fails? I'm pretty much certain that the codegen is in sync (it was on my computer).

As far as I can tell they're not:
$ rm -f crates/re_types/source_hash.txt && cargo b -p re_types
removed 'crates/re_types/source_hash.txt'
   Compiling re_types v0.8.0-alpha.0 (/home/cmc/dev/rerun-io/rerun/crates/re_types)
    Finished dev [optimized + debuginfo] target(s) in 1.16s

$ git diff

diff --git a/crates/re_types/source_hash.txt b/crates/re_types/source_hash.txt
index 017beb2a4..bfb98aa5f 100644
--- a/crates/re_types/source_hash.txt
+++ b/crates/re_types/source_hash.txt
@@ -1,4 +1,4 @@
 # This is a sha256 hash for all direct and indirect dependencies of this crate's build script.
 # It can be safely removed at anytime to force the build script to run again.
 # Check out build.rs to see how it's computed.
-e32e0f115b22080f35f06fb73b486eeb390c4c47deee6c04012621ab5fca0d09
\ No newline at end of file
+b7927e46605c38a4659f7c90a026f6ce5903e84428414549725107993a4af38a
\ No newline at end of file


Changed vstest log file path to absolute in TranslationLayer.E2ETest …

…sample program.
Added default run parameters to TranslationLayer.E2ETest sample program.
Modified TranslationLayer.ConsoleParameters.LogFilePath to properly handle relative paths, or absolute paths.

This is a fix for #872, including a direct fix for the sample program's incorrect usage of the API, and an improvement to the API itself to allow usage of relative paths.

@JakenVeina,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@JakenVeina thanks for the fix! It looks good to me, have suggested a minor change.

@JakenVeina, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

@dotnet-bot test Windows_NT / Release Build please


HDDS-7366. Coordinate on demand and background container scanners.

What changes were proposed in this pull request?

Update scan timestamps in the on demand and background container scanners.
Skip scanning containers in the on-demand and background scanners that were recently scanned based on their timestamp. Previously this only happened in the background scanner.
Rename the three scanner classes with more descriptive names to distinguish them.
The scanners should not have issues if they happen to run on the same container at the same time.

Container state is updated under the container write lock in KeyValueHandler#markContainerUnhealthy
Container timestamp is updated under the same write lock in KeyValueContainer#updateDataScanTimestamp
Container file checksum is checked by loading a separate copy of the file from disk into memory (KeyValueContainerCheck#fastCheck). Container file updates are done atomically in KeyValueContainer#writeToContainerFile.

What is the link to the Apache JIRA
HDDS-7366
How was this patch tested?
Unit tests for all 3 scanners were added and expanded. Each scanner now has a dedicated unit test class which includes its metrics tests and other mock based unit tests. Integration testing of the scanners will be handled in HDDS-8553.

@sumitagrawl could you help review?

@sumitagrawl please remove unnecessary details from the commit message when merging PRs
commit feed38e73690952e8073a5e5986d8c89e50eb6a0
Author: Ethan Rose<EMAIL_ADDRESS>Date:   Thu May 25 01:41:13 2023 -0700

    HDDS-7366. Coordinate on demand and background container scanners. (#4726)

    * Use timestamps to throttle scans

    * Updated unit test for on demand scanner support of timestamps

    * Unit tests pass after refactor and additions

    * Revert findbugs

    * Change variable to static final

    * Combine log messages to helper methods

    * Checkstyle

    * Restore findbugs exclude from master and include renames


Adding tests for the match_groups method for authentication

Added tests for earlier functionality of match_groups
including the new fix there for Central Admin where
match_groups only matches returns groups from current
region.

/cc @jvlcek  crossing-T's dotting-I's,  to cover the fixes made yesterday to match_groups for Central Admin with groups in multiple regions of same name.  Thanks.

👍  LGTM @abellotti


Adaptation Towards Multi-Task Inference

Checklist

I have searched related issues but cannot get the expected help. ☑
I have read related documents and don't know what to do. ☑

Describe the question you meet
I have a dataset with multiple outputs, namely car color and model, and I have adapted the CrossEntropy function to allow for k-dimensional cls_score. It is currently training. However I am lost in how to adapt the model for it to correctly return multiple predicted labels (predicted color and predicted model).
I did not find any example of this in the documentation, could anyone point me towards an example of multi-task classification with mmcls?
I am training on the vit32 model.
Post related information

Other code you modified in the mmcls folder.

Here is my modified CrossEntropyLoss class, other than the Dataset class it is the only modification done:
@LOSSES.register_module(force=True)
class MultiTaskCrossEntropyLoss(nn.Module):
    """Cross entropy loss.
    Args:
        num_tasks (int): Number of k dimensions. The input on the foward will
        be reshaped into B x C/num_tasks x num_tasks. Defaults to 1.
        use_sigmoid (bool): Whether the prediction uses sigmoid
            of softmax. Defaults to False.
        use_soft (bool): Whether to use the soft version of CrossEntropyLoss.
            Defaults to False.
        reduction (str): The method used to reduce the loss.
            Options are "none", "mean" and "sum". Defaults to 'mean'.
        loss_weight (float):  Weight of the loss. Defaults to 1.0.
        class_weight (List[float], optional): The weight for each class with
            shape (C), C is the number of classes. Default None.
        pos_weight (List[float], optional): The positive weight for each
            class with shape (C), C is the number of classes. Only enabled in
            BCE loss when ``use_sigmoid`` is True. Default None.
    """

    def __init__(self,
                 num_tasks=1,
                 use_sigmoid=False,
                 use_soft=False,
                 reduction='mean',
                 loss_weight=1.0,
                 class_weight=None,
                 pos_weight=None):
        super(MultiTaskCrossEntropyLoss, self).__init__()
        self.use_sigmoid = use_sigmoid
        self.use_soft = use_soft
        assert not (
            self.use_soft and self.use_sigmoid
        ), 'use_sigmoid and use_soft could not be set simultaneously'

        self.reduction = reduction
        self.loss_weight = loss_weight
        self.class_weight = class_weight
        self.pos_weight = pos_weight

        if self.use_sigmoid:
            self.cls_criterion = binary_cross_entropy
        elif self.use_soft:
            self.cls_criterion = soft_cross_entropy
        else:
            self.cls_criterion = cross_entropy

        self.num_tasks = num_tasks

    def forward(self,
                cls_score,
                label,
                weight=None,
                avg_factor=None,
                reduction_override=None,
                **kwargs):
        assert reduction_override in (None, 'none', 'mean', 'sum')
        reduction = (
            reduction_override if reduction_override else self.reduction)

        if self.class_weight is not None:
            class_weight = cls_score.new_tensor(self.class_weight)
        else:
            class_weight = None

        # only BCE loss has pos_weight
        if self.pos_weight is not None and self.use_sigmoid:
            pos_weight = cls_score.new_tensor(self.pos_weight)
            kwargs.update({'pos_weight': pos_weight})
        else:
            pos_weight = None

        ##

        ## RESHAPE OF THE INPUT FOR MULTI TASK LOSS CALCULATION
        if self.num_tasks > 1:
          dims = cls_score.shape
          cls_score = cls_score.reshape(dims[0], int(dims[1]/self.num_tasks), self.num_tasks)

        loss_cls = self.loss_weight * self.cls_criterion(
            cls_score,
            label,
            weight,
            class_weight=class_weight,
            reduction=reduction,
            avg_factor=avg_factor,
            **kwargs)
        return loss_cls

It seems that your model output a [batch, task1_channel + task2_channel ....... ] vector. if you want to get the prediction of your model, you must add a  MultiTaskHead like ClsHead, notice the simple_test function.

It seems that your model output a [batch, task1_channel + task2_channel ....... ] vector. if you want to get the prediction of your model, you must add a MultiTaskHead like ClsHead, notice the simple_test function.

Thanks for the reply. Since I'm working with VIT32, I added a MultiTasksVisionTransformerClsHead class. The class is shown below. Would that be all I need for multi task inference? I noticed I would not be able to use mmcls.apis.inference_model correctly, since https://github.com/open-mmlab/mmclassification/blob/643fb192cdad25a2faf0237059ef5bf97c65b5c8/mmcls/apis/inference.py#L86 of inference.py gets only the first position of the output.
Here is my MultiTaskVisionTransformerClsHead:
    def simple_test(self, x, softmax=True, post_process=True):
        """Inference without augmentation.
        Args:
            x (tuple[tuple[tensor, tensor]]): The input features.
                Multi-stage inputs are acceptable but only the last stage will
                be used to classify. Every item should be a tuple which
                includes patch token and cls token. The cls token will be used
                to classify and the shape of it should be
                ``(num_samples, in_channels)``.
            softmax (bool): Whether to softmax the classification score.
            post_process (bool): Whether to do post processing the
                inference results. It will convert the output to a list.
        Returns:
            Tensor | list: The inference results.
                - If no post processing, the output is a tensor with shape
                  ``(num_samples, num_classes)``.
                - If post processing, the output is a multi-dimentional list of
                  float and the dimensions are ``(num_samples, num_classes)``.
        """
        x = self.pre_logits(x)
        cls_score = self.layers.head(x)

        if cls_score is not None:
          dims = cls_score.shape
          cls_score = cls_score.reshape((dims[0], int(dims[1]/num_tasks), int(num_tasks)))

        if softmax:
            pred = (
                F.softmax(cls_score, dim=1) if cls_score is not None else None)
        else:
            pred = cls_score

        if post_process:
            return self.post_process(pred)
        else:
            return pred

No, a MultiTaskVisionTransformerClsHead is not enough for multi task inference. you are right that mmcls.apis.inference_model should be modified. the post_process in head and mmcls.apis.test should be modified too.
It is recommended to use a MutilTaskHead, which contains a list of heads, each head predicts a task. it would be friendly if the classes_numbers  in the tasks are different, and the post_process and loss need not be modified. this MutilTaskHead could return a dict in head.simple_test; and you can handle the dict output in mmcls.apis.inference_model  and mmcls.apis.test, so that your modification does not affect other codes in mmcls.

@Ezra-Yu @victoic please check https://github.com/open-mmlab/mmclassification/pull/675, this is my first contribution so i would be glad to have your feedbacks on this !
Thanks

I'm working on multi-task learning too, I wonder if your experiment is supported by literature. Could you please share some ?  @victoic

This issue will be closed as it is inactive, feel free to re-open it if necessary.


/etc/default/docker ignored

BUG REPORT INFORMATION
Description
The file /etc/default/docker is ignored by systemctl while launching Docker (via service or init.d).
Steps to reproduce the issue:

Install Docker via the official way on Ubuntu 16.04
Change something in /etc/default/docker (like enable IPv6)
Restart Docker

Describe the results you received:
The changes are not applied, I need to modify /etc/systemd/system/multi-user.target.wants/docker.service to enable my modifications.
Describe the results you expected:
Apply the change present on /etc/default/docker after rebooting the service.
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Client:
 Version:      17.03.1-ce
 API version:  1.27
 Go version:   go1.7.5
 Git commit:   c6d412e
 Built:        Fri Mar 24 00:45:26 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.03.1-ce
 API version:  1.27 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   c6d412e
 Built:        Fri Mar 24 00:45:26 2017
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:
Containers: 12
 Running: 2
 Paused: 0
 Stopped: 10
Images: 106
Server Version: 17.03.1-ce
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 134
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 4ab9917febca54791c5f071a9d1f404867857fcc
runc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.4.0-64-generic
Operating System: Ubuntu 16.04.2 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.945 GiB
Name: runner02.srv.nautile.tech
ID: VSXG:WSWQ:QXDH:WZ57:GZKO:BEL6:VZ2B:BMLJ:NKVV:5OYY:CMGN:EFIZ
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):
Xen Ubuntu 16.04 virtual machine

That's expected; that file is only used for Sysvinit and upstart; https://github.com/docker/docker/blob/v17.03.1-ce/contrib/init/sysvinit-debian/docker.default#L1-L8
To specify daemon options;

the recommended approach is to use a daemon.json configuration file (this works, irregardless of the init system in use (https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-configuration-file)
use systemd drop-in files (never directly modify the main unit file; doing so will prevent it from being updated when updating docker); https://docs.docker.com/v1.13/engine/admin/systemd/#/custom-docker-daemon-options

I'll close this issue, because this is not a bug, but feel free to comment after i closed

@thaJeztah Thanks for your anwser. It's clear now. :smile:


Instructions

I've found this library while looking at https://github.com/material-foundation/material-color-utilities. I plan on using it to generate a palette from an image, either read raw or through the use of the image crate's DynamicImage struct.
I'm currently searching for code in other repos that use this library, but it would be nice if you could provide some instructions on at least the basic usage of this library.

Same I'd really like some basic getting started docs as well.


AIR 32 Support?

Hello!
Is Adobe AIR 32 supported? I'm currently using Flex SDK 4.6 and extracted the AIR SDK v32 in there and set it as my SDK in FD, but I can only use AIR 28.

What version of the editor are you using?

I'm using <IP_ADDRESS>

Try using the development version from here http://flashdevelop.org/downloads/builds/

Oh I didn't know that there's a development version. Thank you!


⚠ Bofrost.at has degraded performance

In 05b9e00, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2247 ms

Resolved: Bofrost.at performance has improved in 21980f5 after 13 minutes.


Notify PM or SDK owner when not release some language SDK

Notify PM or SDK owner when service team chose not to release one or more languages SDK.
Currently we only record the reason in dataverse.
We should send an e-mail or record it in issue or some where.

Hi @josefree , create an issue to track the requirement. We may need more discuss how to achieve it.

@ladonnaq who should we email? you if it is Data lane and Josephine if it is ARM?

@ladonnaq who should we email? you if it is Data lane and Josephine if it is ARM?

Just use the APEX group alias -<EMAIL_ADDRESS> Then we will investigate and get Josephine or others involved if needed.

I will review and look into the requirement for this in Feb 2024.  Sending email to the azsdkapex alias will be suitable.  Also, want to touch base with Josephine to see if she  would like to added to the alias.

I found official documentation for this process here: https://eng.ms/docs/products/azure-developer-experience/onboard/request-exception
@ladonnaq  could you follow up on this and make sure @josefree and you are in agreement?
Feel free to edit the documentation in case things change.

From  @josefree:

Please select an appropriate reason for not utilizing the Azure SDK pipeline for the SDK release in a specific language.
We (the service owner) allocate resources to develop and deliver the SDK in the specific language manually.
We (the service owner) are assured that the service will not be used in a client environment involving the specific language.
Others, please specify________________

From @josefree:

Please select an appropriate reason for not utilizing the Azure SDK pipeline for the SDK release in a specific language.
We (the service owner) allocate resources to develop and deliver the SDK in the specific language manually.
We (the service owner) are assured that the service will not be used in a client environment involving the specific language.
Others, please specify________________

I assume we should ask only one attestation for all non-selected languages. We can send an email to<EMAIL_ADDRESS>and other service partner parties involved in the release plan.

One more question: @ladonnaq and @josefree Can you please confirm if we need this email notification for language exception change for both TypeSpec and OpenAPI based SDK release or only for TypeSpec?

Solution:

Release planner will prompt user to attest the reason for no choosing a language if any tier 1 language is not selected.
Store this info in Dataverse table along with other information like release plan ID. Add a new column Notified in dataverse and set it to false for attestation records.
Create a cloud flow that gets triggered whenever there is a new attestation record created.
Cloud flow will process the attestation and send an email to<EMAIL_ADDRESS>and other service partner parties and mark notified as processed.

One more question: @ladonnaq and @josefree Can you please confirm if we need this email notification for language exception change for both TypeSpec and OpenAPI based SDK release or only for TypeSpec? We can remove language selection from current management plane SDK release request app and keep it uniform.

@praveenkuttappan - As I understand release plans for stable SDKs (generated using TypeSpec or OpenAPI) should include all tier 1 languages and if not, then it would be an exception requiring justification.  @josefree Is this your expectation?

Done in Dev for management plane app

@ladonnaq is the process the same for data plane? same email template and everything?

The SDK policies published on GitHub show inconsistencies between the language requirements for Beta and Stable SDKs.  I highlighted the relevant content in the screenshot below.

It is illogical to require only two languages for Beta SDKs while mandating support for all tier-1 languages for Stable SDKs. Additionally, the APEX requirements for Beta SDKs mandate the release in all tier-1 languages.
I recommend updating the Beta SDK policies to require support for all tier-1 languages. If a Service team needs to stagger the language releases due to time constraints, they can request an exception. We will then use a different release plan to track and ensure the requirement is met.
Once the policy is updated, we should be able to leverage the same UI, back-end, and email template. The email should go to the azsdkapex alias and probably the arch board help desk.

Data plane conversation moved to https://github.com/Azure/azure-sdk-tools/issues/9387


Added cl_khr_fp16 extension support for test_vector_swizzle from basic

According to issue description (basic section):
https://github.com/KhronosGroup/OpenCL-CTS/issues/142

Reviewing, thanks.


Extend SIF metadata

Hi,
It would be great if we could extend the current metadata to incorporate more information on e.g. the gate time.
For reference, I include here the "Acquisition info" that Andor Solis lists for a measurement I took, and the 66-line header for the same file:
measurement_info.txt:
Filename:                     measurement.sif
Date and Time:                Fri Jul 28 13:51:04.409 2023
Software Version:             4.32.30000.0
Temperature (C):              -25
Model:                        DH334T-18F-63
Data Type:                    Counts
Acquisition Mode:             Kinetics
Trigger Mode:                 External
Exposure Time (secs):         3
Number of Accumulations:      1
Number in Kinetics Series:    20
Readout Mode:                 Full Vertical Binning
Horizontal binning:           1
Extended Data Range:          off
Horizontally flipped:         false
Vertical Shift Speed (usecs): 6.5
Pixel Readout Rate (MHz):     1
Clock Amplitude:              Normal
Serial Number:                ICCD-06390
Pre-Amplifier Gain:           4x
Trigger level (V):            1
Termination:                  50 ohms
Inverted:                     false
Intelligate:                  off
Insertion delay:              normal
Gain level:                   2500
Integrate on chip:            on
IOC frequency (Hz):           5e+05
IOC number of pulses:         1
PIV Mode:                     off
Output A Width (nsecs):       10
Output A Delay (nsecs):       0
Output A Polarity:            Negative
Gate Mode:                    DDG on
Gate Width (nsecs):           10
Gate Delay (nsecs):           0
Gate Delay Step (nsecs):      0
Gate Width Step (nsecs):      0
Spurious Noise Filter Mode:   No Filter
Photon counted:               false
Data Averaging Filter Mode:   No Filter
KY328i:
Serial Number:                KY-4231
Wavelength (nm):              561.47
Grating Groove Density (l/mm):599.566
Grating Blaze:                650NM
Output Flipper Port:          Direct
Input Side Slit Width (um):   50
Side Iris Steps:              50

measurement.sif header:
Andor Technology Multi-Channel File
65538 1
65567 0 0 1<PHONE_NUMBER> -25 � � �   0 3 3.0221 3.0221 1 � 3.0221 1e-06 0 1 2500 0 0 1e-08 0 0 � � 1 0 5 0 0 0 0 0 0 1 500000 0 6.5e-06 0 4 6390 1 1 -999 0 0 0 0 0 5 4 32 30000 0 0 1 1000 0 0 0 550 0 0 0 0 0 0 0 0 0 1 1 13
DH334T-18F-63
 1024 1024 69
C:\asdasdasdasd\measurement.sif
65538 2048
<line 8 with non-ascii characters omitted>
<line 9 with non-ascii characters omitted>
<line 10 with non-ascii characters omitted>
<line 11 with non-ascii characters omitted>
<line 12 with non-ascii characters omitted>
<line 13 with non-ascii characters omitted>
65538    � 0.027 0
65540 1 1 561.47 1 1 599.566 650NM
1 50
1 0 0 0 0  0 0 0 0 0 0 10
0 KY328i
0 10
0 10
0 0
65537 0 500 1200
0 999 999

65539 1 5 2500 0 0 0 10000 1 2000000 1 100 0 0 100 0 0
1 1 0 10000
0 1 0 2000
0 1 0 2000
1 0 0

-1
65538 0 1024 1024 1024 1024 1 1 1 1
65540  �  �  �
529.93812442523 0.061715845778342 -2.28349748230931e-07 -5.07163560661353e-11
0 1 0 0
0 1 0 0
422
13
13
1
10
Wavelength6
Counts12
Pixel number65541 1 1024 1024 1 20 1 20480 1024
65538 1 1024 1024 1 1024 1 0
         0
         0
         0
         0
         0
         0
         0
         0
         0
         0
         0
         0
         0
         0
         0
         0
         0
         0
         0
         0
0

measurement.sif.zip
measurement_info.txt

#34 implements changes that would partially fix the current incomplete metadata. @fujiisoup Could we create a new release with the proposed changes?

Could we create a new release with the proposed changes?

Yes, I will. Let's finalize the PR.

I found the following XML-structured metadata at the end of the SIF file:
<?xml version="1.0" ?>
<Signals>
    <Signal>
        <TInstaImageData>
            <PreAmpGainText>4x</PreAmpGainText>
            <SpectrographSerial>KY-4231</SpectrographSerial>
            <mSec>616</mSec>
            <DIRECT_IRIS_PRESENT>0</DIRECT_IRIS_PRESENT>
            <DIRECT_IRIS_POSITION>-1</DIRECT_IRIS_POSITION>
            <SIDE_IRIS_PRESENT>1</SIDE_IRIS_PRESENT>
            <SIDE_IRIS_POSITION>50</SIDE_IRIS_POSITION>
            <FullSerialNumber>ICCD-06390</FullSerialNumber>
            <DARKTHRESHOLD>-999</DARKTHRESHOLD>
        </TInstaImageData>
        <TInstaImage>
            <IRIGAvailable>0</IRIGAvailable>
        </TInstaImage>
        <TCalibImage>
            <TCalibImageData />
            <TAndorImage>
                <TAndorImageData>
                    <ImageFormat>0</ImageFormat>
                    <ReadoutPort>-1</ReadoutPort>
                    <ExposureWindowHeight>0</ExposureWindowHeight>
                    <LineScanSpeed>0</LineScanSpeed>
                    <AlternatingReadoutDirection>0</AlternatingReadoutDirection>
                    <ScanSpeedControl>0</ScanSpeedControl>
                    <ReadoutDirection>-1</ReadoutDirection>
                    <FastKineticsStorageMode>0</FastKineticsStorageMode>
                    <FastKineticsTimeScanMode>-1</FastKineticsTimeScanMode>
                    <TickInterval>10</TickInterval>
                    <PIVMode>0</PIVMode>
                    <ExtendedDynamicRange>0</ExtendedDynamicRange>
                </TAndorImageData>
            </TAndorImage>
        </TCalibImage>
    </Signal>
</Signals>
<References />
<Backgrounds>
    <Background>
        <TInstaImageData>
            <PreAmpGainText>4x</PreAmpGainText>
            <SpectrographSerial>KY-4231</SpectrographSerial>
            <mSec>0</mSec>
            <DIRECT_IRIS_PRESENT>0</DIRECT_IRIS_PRESENT>
            <DIRECT_IRIS_POSITION>-1</DIRECT_IRIS_POSITION>
            <SIDE_IRIS_PRESENT>1</SIDE_IRIS_PRESENT>
            <SIDE_IRIS_POSITION>50</SIDE_IRIS_POSITION>
            <FullSerialNumber>ICCD-06390</FullSerialNumber>
            <DARKTHRESHOLD>-999</DARKTHRESHOLD>
        </TInstaImageData>
        <TInstaImage>
            <IRIGAvailable>0</IRIGAvailable>
        </TInstaImage>
        <TCalibImage>
            <TCalibImageData />
            <TAndorImage>
                <TAndorImageData>
                    <ImageFormat>0</ImageFormat>
                    <ReadoutPort>-1</ReadoutPort>
                    <ExposureWindowHeight>0</ExposureWindowHeight>
                    <LineScanSpeed>0</LineScanSpeed>
                    <AlternatingReadoutDirection>0</AlternatingReadoutDirection>
                    <ScanSpeedControl>0</ScanSpeedControl>
                    <ReadoutDirection>-1</ReadoutDirection>
                    <FastKineticsStorageMode>0</FastKineticsStorageMode>
                    <FastKineticsTimeScanMode>-1</FastKineticsTimeScanMode>
                    <TickInterval>10</TickInterval>
                    <PIVMode>0</PIVMode>
                    <ExtendedDynamicRange>0</ExtendedDynamicRange>
                </TAndorImageData>
            </TAndorImage>
        </TCalibImage>
    </Background>
</Backgrounds>
<Lives />
<Sources />
�������SIFX

This seems to also be useful metadata.

As for the XML metadata, I'm not sure how many edge cases there are (multiple signals, references or backgrounds?). I think there are two options:

Flattening this metadata (e.g. keys such as Signal_0_ PreAmpGainText)
Convert it to a dict structure.

Do you have any preference?

Hi @mruijzendaal
I like this option:

Flattening this metadata (e.g. keys such as Signal_0_PreAmpGainText)

I think we can just ignore edge cases. If someone really needs these metadata, they may implement it.


Fix merge logic for node affinities

What this PR does / why we need it:
This PR brings the following changes and improvements:

[x] Fix merge logic for node affinities, so now node affinities between policy and pod spec are "strategically" merged using cartesian product of the NodeSelectorTerms
[x] Set ReinvocationPolicy: Never so that kupid mutating webhook is not invoked twice in the same mutation chain, thus avoiding multiple appends to the same policy
[x] Add leader election capability to kupid controller manager so that it can be run in active-passive HA mode
[x] Use structured JSON logger, with ISO8601 time encoder
[x] Make development and deployment of kupid easier by including deploying/removal of cert-manager within make [un]deploy-with-certmanager Make target

Which issue(s) this PR fixes:
Fixes #25
Special notes for your reviewer:
Release note:

Fix merge logic for node affinities, so now node affinities between policy and pod spec are "strategically" merged using cartesian product of the `NodeSelectorTerms`.

Set `ReinvocationPolicy: Never` so that kupid mutating webhook is not invoked twice in the same mutation chain, thus avoiding multiple appends to the same policy.

Add leader election capability to kupid controller manager so that it can be run in active-passive HA mode.

Use structured JSON logger, with ISO8601 time encoder.

Make development and deployment of kupid easier by including deploying/removal of [cert-manager](https://cert-manager.io/docs/) within `make [un]deploy-with-certmanager` Make target.

/assign @unmarshall @ashwani2k PTAL

/assign

Note to reviewers to test the PR:

Checkout the PR branch locally
Target any Kubernetes cluster with k8s version >= v1.22
Run make deploy-with-certmanager to deploy cert-manager as well as the kupid extension
Watch the kupid pod logs to ensure that kupid reacts to changes to PSPs, CPSPs as well as other pod-group resources deployed in the cluster
Deploy a ClusterPodSchedulingPolicy for mutating nodeAffinity for statefulset pods (sample resource provided here)
Deploy a statefulset with nodeAffinity different from the policy, and ensure from kupid logs that it mutates the statefulset
Ensure that the statefulset is mutated correctly

You may use the following examples to test the PR:
NodeAffinity present on the pod spec:
nodeAffinity:
  requiredDuringSchedulingIgnoredDuringExecution:
    nodeSelectorTerms:
    - matchExpressions:
      - key: a
        operator: In
        values:
        - A
      - key: b
        operator: In
        values:
        - B
    - matchExpressions:
      - key: c
        operator: In
        values:
        - C

NodeAffinity defined by the ClusterPodSchedulingPolicy:
nodeAffinity:
  requiredDuringSchedulingIgnoredDuringExecution:
    nodeSelectorTerms:
    - matchExpressions:
      - key: d
        operator: In
        values:
        - D
    - matchExpressions:
      - key: e
        operator: In
        values:
        - E
      matchFields:
      - key: metadata.name
        operator: In
        values:
        - F

Expected correctly merged nodeAffinity with this PR (note that the affinity terms are merged using cartesian product, which means that the policy specified by Kupid is truly enforced on the pod spec, so a true strategic merge patch happens here):
nodeAffinity:
  requiredDuringSchedulingIgnoredDuringExecution:
    nodeSelectorTerms:
    - matchExpressions:
      - key: d
        operator: In
        values:
        - D
      - key: a
        operator: In
        values:
        - A
      - key: b
        operator: In
        values:
        - B
    - matchExpressions:
      - key: e
        operator: In
        values:
        - E
      - key: a
        operator: In
        values:
        - A
      - key: b
        operator: In
        values:
        - B
      matchFields:
      - key: metadata.name
        operator: In
        values:
        - F
    - matchExpressions:
      - key: d
        operator: In
        values:
        - D
      - key: c
        operator: In
        values:
        - C
    - matchExpressions:
      - key: e
        operator: In
        values:
        - E
      - key: c
        operator: In
        values:
        - C
      matchFields:
      - key: metadata.name
        operator: In
        values:
        - F

Wrongly merged nodeAffinity, prior to this PR (observe here that the affinity rules are simply appended to each other, causing the scheduler to perform an OR amongst these NodeSelectorTerms and choose any one for scheduling the pod, which is incorrect):
nodeAffinity:
  requiredDuringSchedulingIgnoredDuringExecution:
    nodeSelectorTerms:
    - matchExpressions:
      - key: a
        operator: In
        values:
        - A
      - key: b
        operator: In
        values:
        - B
    - matchExpressions:
      - key: c
        operator: In
        values:
        - C
    - matchExpressions:
      - key: d
        operator: In
        values:
        - D
    - matchExpressions:
      - key: e
        operator: In
        values:
        - E
      matchFields:
      - key: metadata.name
        operator: In
        values:
        - F

Please also change the replicas count to 2 or 3 to test the HA mode of Kupid introduced in this PR with leader election capabilities.
In order to test the interplay of kupid webhook with other mutating webhooks such as GRM from gardener, please run kupid as an extension in the gardener local setup and deploy a HA seed and then a HA shoot and observe the effect on the etcd-main statefulset deployed as part of the shoot control plane.

/unassign


Cleanup issues reported by error prone

We had a few reported small issues on the codebase from the recent introduced google error prone.
This should eliminate any issues, and I am making sure these won't happen again

i'll get this merged


Rename-DbaLogin - Fix #6245

Type of Change

[X] Bug fix (non-breaking change, fixes #6245 )
[ ] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[X] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Warn if the login doesn't exist instead of throwing null error
Approach
Check if the login was found
Screenshots

Please put a title on that issue of you would.


Does not build on ubuntu

I run into the following error:
failed to run custom build command for `termios v0.0.0 (file:///home/marcus/rust/termios.rs)`
Process didn't exit successfully: `/home/marcus/rust/termios.rs/target/build/termios-15d1c7c8305a8ca0/build-script-build` (status=11)

I think rust-bindgen recently reverted back to dynamic linking to LLVM by default, that's likely the cause of the error that you are seeing.
Right now rust-bindgen is not building with the latest nightly, once that gets fixed upstream I'll take a look into this issue.

I send a PR to rust-bindgen updating to the latest nightly, and also switched to my fork that statically links to libclang. Can you give try using master? (The travis build passed)

Sorry for my late response. I've pulled master, but get the following error messages when compiling:
/usr/bin/ld: cannot find -lLLVMBitReader /usr/bin/ld: cannot find -lLLVMCore /usr/bin/ld: cannot find -lLLVMLTO /usr/bin/ld: cannot find -lLLVMLinker
and about 20 more like them..

Do you have the libclang-3.5-dev and llvm-3.5-dev packages installed? They are required for the bindgen dependency. (The .travis.yml has instructions on how to install them on Ubuntu 12.04).

Yup, I do. This problem most likely just something I caused myself, so I'll close this issue. Thanks for the help though!

I finally got it to work by the way :fireworks:

@marcusklaas how did you managed this?

Sorry, I truly have no idea any more. I am super disappointed to find out I was (am?) one of those people that report that they have fixed something, but now how.


Create AstId for builtin_derive macro in tests

This moves them closer to the builtin_macro tests
bors r+

changelog skip


ZeroDivisionError: float division by zero on black

from rgb_cie import Converter
converter = Converter()
converter.rgbToCIE1931(0, 0, 0)

Then there is:
ZeroDivisionError: float division by zero

I thought I would trick the function to give it a color closest to black: (1,1,1), however, the function returns the same value for white: (255, 255, 255):
In [1]: converter.rgbToCIE1931(1, 1, 1)
Out[1]: [0.33618074375880236, 0.3603696362840742]

In [2]: converter.rgbToCIE1931(255, 255, 255)
Out[2]: [0.33618074375880236, 0.3603696362840742]

So basically there are two issues:

ZeroDivisionError, easy to fix
getClosestPointToPoint() returns identical values for "black" and "white"

Any ideas on how to fix the second one? I couldn't find any point near "black" from the hue color map:
http://www.developers.meethue.com/documentation/core-concepts
Maybe turn it off? ;-)

I fixed the divide by zero error by adding a simple conditional.
Regarding your second issue, I don't think this is actually a bug.  An XY value really just represents a hue, so if you wanted "close to black" you'd take the XY value for white and set brightness as low as possible.

That's right! Thanks for fixing it!


Separated the arrays and tutorials in main page

I also fixed the back button in certain tutorials, since it wasn't redirecting to the main page like it was supposed to
@JenniferYu8 Could you take a look at this and let me know what you think?

Love it!!! There's quite a big space between the demos and the tutorials in the main page; would it be possible to either bring them closer together or add something to take up the space (e.g. bit by bot).
Also, the titles on each page look a bit too close to the top; if you could move them down a bit, that'd be great!


Prepare v1.1.1 release

New release due to https://github.com/Shopify/themekit/pull/767
Warn Checklist

[x] This changes the interface and requires a Major/Minor version change.
[ ] I have :tophat:'d these changes by using the commands I changed by hand.
[ ] I have added a dependancy to the project.
[x] I have considered any potential impact on node-themekit

[x] Update ThemeKitVersion in src/release/release.go and commit.
[x] Make the release tool go install ./cmd/tkrelease
[x] run git tag <version> && git push origin --tags && git push
[x] Update the changelog.txt with the date of the version release
[x] Release using tool

[x] build all distributions make all
[x] release tkrelease -k="AWS_ACCESS_KEY" -s="AWS_SECRET_KEY" vX.X.X

[x] If releasing a different version than in src/release/version.go you can use -f to force, sometimes this is necessary for specific issue tags like v0.0.0-issue432 when trying to debug a issue.
[x] Using beta/alpha tags on the version number will stop themekit from automatically updating to that version. It would have to be typed in specifically like theme update --version=v1.0.4-rc1

[x] On GitHub create a new release for the tag and take note of any relevant changes.

[x] Include a brief summary of all the changes
[x] Include links to the Pull Requests that introduced these changes

[x] Update the [documentation website]

[x] run make serve_docs
[x] update any changes to the API
[x] commit changes

[x] Update themekitversion in docs config docs/_config.yml to update the download links,
then run make md5s to generate the checksums for the new files. Add these to the docs/_config.yml
file as well.
[ ] Update Chocolatey package in the choco folder

[ ] Update the version in choco/themekit.nuspec
[ ] Update the version and checksums in choco/tools/chocolateyinstall.ps1
[ ] Run choco pack in a window VM
[ ] Log into chocolatey.org (use the<EMAIL_ADDRESS>credentials) and submit an update for approval

[x] Update themekit.rb formula for homebrew

[x] run make sha to generate the SHA256 for the darwin build
[x] update the link and sha in the homebrew formula

[ ] Notify the maintainer of the AUR themekit package https://aur.archlinux.org/packages/shopify-themekit-bin
of an update so they can release a new version.

Thanks for all the work you do on ThemeKit, I'm really excited about the changes for using checksums on uploads and downloads.
Do you have any idea on the time frame for this release to get pushed to Chocolatey?

Hi @NickH-nz, I ran into some Windows VM issues but I'm hoping to get it released very soon.
In the meantime, you should be able update to the newer version by running theme update.

Thanks for the response.
I had tried theme update but ran into an error about the binary not being able access itself. Turns out it just needed to be run as admin, but the error message was different than what I'd expected for a permissions issue.

Ok – if you run into this again, a note of the exact error would be helpful.
(The updated Chocolatey release is now available: https://chocolatey.org/packages/themekit )


Convert services to daemons in snap

We want to convert all of the services to daemons so that the snap is able to start up on boot automatically and systemd can manage services going down and coming back up, etc. which currently the snap does not do at all.

Currently, due to a bug in snapd (see launchpad bug # 1796125), service ordering is not respected on installation of a snap. This affects the security services, most of which such as kong, the vault-worker, etc. are not tolerant of having their dependency services not started up when they start up and so for Delhi, we will manage the dependencies manually by putting all of the security services into a single, forking daemon.
Additionally, due to another bug in snapd, services can't be disabled from the install hook, and as such when the snap is installed all services startup immediately, whether they were disabled in the install hook or not. A fix for this is in flight and should land for snapd 2.36, but since in the meantime all of the EdgeX services (with the exception of security services) are able to wait for their dependencies when they start up, it's okay to have all of the services startup on install.
Once the fix lands in 2.36, then folks installing the snap will only have the minimal set of services startup as intended.
I will file a separate issue post-Delhi to handle the security services being split up into individual services.

This has landed in Dehli (#722), but is not yet in master, so adjusting labels accordingly.


Consider adding a role to modify attribute source

When using the role isam-ansible-roles/add_attribute_source it does not change the value of attribute_source_value if the attribute source already exists.
Removing the attribute source and adding it again is tedious because you have to detach it from the definitions first.
It'll be handy if I could easily change the value of attribute_source_value for a given attribute source.

Please create a new set_attribute_source that uses the set() function. That will add if does not exist and modify if it already exists and a change is needed.


Fix for intermittent ssh error.

This update enables full structure retrieval of network interfaces, both PFs and VFs.
Using this approach one can easily determine network interface status (bound, unbound etc), retrieve used/unused driver.
Signed-off-by: Orest Voznyy<EMAIL_ADDRESS>

This change is

@rbbratta @lijenni
Could you please review this change. Thanks.

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Decrypt on PHP

Is there any way of decrypting with php. the encrypting code generated with this bundle on des?

I didn't test on php, just test on java and nodejs

have add php support


feat: overlay header labels override

Signed-off-by: Akiff Manji<EMAIL_ADDRESS>Summary of Changes
Adds override for credential and connection label in credential header branding (to be used with OCA)
Related Issues
N/A
Pull Request Checklist
Tick all boxes below to demonstrate that you have completed the respective task. If the item does not apply to your this PR check it anyway to make it apparent that there's nothing to do.

[ ] All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this);
[ ] Updated LICENSE-3RD-PARTY.md for any added dependencies or vendored components;
[ ] Updated documentation as needed for changed code and new or modified features;
[ ] Added sufficient tests so that overall code coverage is not reduced.

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!
Pro Tip 🤓

Read our contribution guide at least once; it will save you a few review cycles!
Your PR will likely not be reviewed until all the above boxes are checked and all automated tests have passed.

PR template adapted from the Python attrs project.

@amanji Update and merge?


New Sample Date compress format

Q
A

Bug fix?
no

New sample?
yes

Related issues?

What's in this Pull Request?
This sample provide a different style to provide Date in a compress way such us align days and month and display year parallel as vertical.
Guidance
You can delete this section when you are submitting the pull request.

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to 'master' branch.

Thanks for your contribution! Sharing is caring.

Very cool format @aaclage! 💜🧡😍


Promenade integration is fragile

Forgetting to push promenade documents as part of design results in hard to debug failures at the tail end of node deployment

This is fixed with the bootaction refactoring.


Layers

Thanks!

Are these layers for the velocyto implementation? I.e. spliced and unspliced count data layers. And is this then also usable for different layers of data processing?
Or am I missing the point entirely here?

This is just being built up, but yes, the layers have the same constraints as in loom files and are meant to enable the transformation of loom files to AnnData objects without loss of information. Here's the stub of the docs: https://anndata.readthedocs.io/en/latest/anndata.AnnData.layers.html. Here's the very first draft https://github.com/theislab/scvelo of our stochastic RNA velocity package... There will be more information on this very soon. :smile:

I'm not that familiar with loom files, but it definitely sounds good ;).
So I guess every tool and plotting function would need a layers argument to determine which layer it should work on? At least if layers is implemented in a sufficiently general way to be used for data processing layers as well.
Any idea on the timeline for this? Then I could adapt the tutorial to work with this.

In principle, everything works already. @VolkerBergen and @Koncopd have all the info on this.


Removed submodules.

Move 3rd party RangeTree and WpfRangeControls components to Contrib folder.
Fixed TestCharacterSheet unit test to pass.

Simple as that. dist-release working again.

Fixed TestCharacterSheet unit test to pass.

Did you simply comment out all checks? In that case, shouldn't you rather comment out the entire test (so it doesn't show "Test passed" when there was nothing being tested)?

Didn't have time to read everything again about life cycle of Unit
Tests. I implemented those tests like ages ago, so I've chosen most time
efficient solution.
And I'd like to get that basic test working again in timeline of few days.

More important part is the sub-module stuff.
I would like to have it reviewed asap, as I have ready next pull with simple Item Filter editor I'd like to use in Prophecy league :p
The reasons why I didn't make DLLs out of them:

ability to hot-fix and improve stuff, simply full  control over code
not fan of having lot of tiny DLLs for each 3-5 source files and having CLR to link them all on each launch. We have like 180+ files in project, that's 36 DLLs/subprojects for each 5 files :p

I'm not against using DLL isolation for our app. Actually I'd like to have some UI and other larger logical chunks separated, but there should be line, which goes into DLL and which don't.
"Contrib" folder is common mechanism from old GNU days. It was used for years, and still being used. Just have to include README, LICENCE and other files required by licence of contributed piece of work.

I'm fine with having the submodule files in a subfolder. DLLs were just my first idea and I thought it were more files.
This unit test is running on my pull request branch so it shouldn't be "disabled" like this for long.

Hmm, I made a release a couple days ago, so unless something broke the unit
tests were all working
On May 30, 2016 1:00 AM, "brather1ng"<EMAIL_ADDRESS>wrote:

I'm fine with having the submodule files in a subfolder. DLLs were just my
first idea and I thought it were more files.
This unit test is running on my pull request branch so it shouldn't be
"disabled" like this for long.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/EmmittJ/PoESkillTree/pull/328#issuecomment-222435211,
or mute the thread
https://github.com/notifications/unsubscribe/AHIbbSt6xi9lU9akUGm-UDtMs2mS7-45ks5qGpkBgaJpZM4IpSg4
.

It's not disabled, it just always passes, as it doesn't have data to
compare now.
I wrote down wrong comment. I didn't touch TestCharacterSheet class at
all. Just commented out lines in test data (Build.xml).
The test was failing for me, didn't do proper investigation, but my
guess was that tree URL in Build.xml didn't work with current tree.
Doesn't really matter.
Rather be safe than sorry when you gonna do release with new tree.

So now please focus on submodule part :)

The themes for WpfRangeControls are not applied (open the Equipment tab, there is no scroll bar). This is probably a mix of Themes/Generic.xaml not being in the project root and these styles partially being overwritten in our resources. The best solution would be to put WpfRangeControls into its own project.

Thanks, missed that.
Styles are not applied automatically, you have to reference them in XAML
directly or make them compile into application resources.
No need for project to apply styles.  So best solution is to add 1 line
to App.xaml.

Styles are not applied automatically, you have to reference them in XAML directly or make them compile into application resources.

That's not true, styles located in Themes/Generic.xaml are applied automatically. That file is generally used for default styles of new controls, like in this case. That's why it would work if it's in its own project. However, what you did seems to work either, so I don't mind.

Well, the only reason they were applied before, was thanks to ThemeInfo
attribute set to ResourceDictionaryLocation.SourceAssembly for its assembly.
So, ok i missed out the third method, and that's direct compilation into
assembly using ThemeInfo attribute.
Still, nothing automatic here :)

Is ok to merge it now?

Looks good to me. Don't know if anyone else wants to look over it.

Well, endorsement from you is enough ;)
Only that XAML styling stuff was real issue, and that was fixed.


ES6 and general cleanup

Fix some behavioral issues
Add support for ES6
Cleanup shitty code

oops wrong repo sorry


Rewrite Tracking Links (AMP Phase)

Task/Issue URL: https://app.asana.com/0/72649045549333/1201286795398788/f
Tech Design URL: https://app.asana.com/0/481882893211075/1201299313936485/f
CC: @bwaresiak
Description:
This PR adds support for extracting the canonical URL from AMP links
Steps to test this PR:

Navigate to https://privacy-test-pages.glitch.me/privacy-protections/amp/
Open the links on the page. The loaded url should match the "Expected" url from the test page.
Paste https://www.bbc.com/news/world-asia-china-19432800.amp into the address bar. The loaded page should be https://www.bbc.com/news/world-asia-china-19432800
Paste https://www.bbc.com/news/world-asia-china-19432800.amp into another app such as notes or reminders. Open the link with DDG as the default browser. The loaded page should be https://www.bbc.com/news/world-asia-china-19432800

Device Testing:

[x] iPhone SE (1st Gen)
[x] iPhone 8
[x] iPhone X
[x] iPad

OS Testing:

[x] iOS 13
[x] iOS 14
[x] iOS 15

Internal references:
Software Engineering Expectations
Technical Design Template
When ready for review, remember to post the PR in MM

Thanks, this looks much better when embedded in TabViewController. I've dropped in few more comments after looking at this more carefully. Also tets are not passing, but it looks it's because of linter warnings
BrokenSiteInfo.swift:49:1: Line Length Violation: Line should be 150 characters or less: currently 164 characters (line_length)

Thanks, this looks much better when embedded in TabViewController. I've dropped in few more comments after looking at this more carefully. Also tets are not passing, but it looks it's because of linter warnings
BrokenSiteInfo.swift:49:1: Line Length Violation: Line should be 150 characters or less: currently 164 characters (line_length)

Swore I pushed that fix

@bwaresiak  I've addressed your comments.
1/ This is expected as AMP only applies to the destination link. The site itself handles all other content (when clicking other links etc.).
2/ This is expected but if you have concerns we can take this one to Asana
3/ Fixed.
4/ Fixed/


Fix nextjs error

This fix passes -b flag to force Next.js to use Bun instead of Node.js
These shebang comments force it to use Node but with the -b flag this is skipped

https://github.com/user-attachments/assets/60a37cc5-60e6-4d4c-8e25-36b11b932411
/claim #1052
/closes #1052

/approve
nice!


What format setting is responsible for this?

VSCode Version: 1.8.0
OS Version: Sierra

Sorry if this is the wrong place but can't find anything about this.
What format option is reponsable for this?

I do not think we expose any option to control this formatting option currently. Formatting always seems to insert a space.
Is this a formatting option that you would find useful? If so, would you also expect this option to apply to other block statements and before function bodies?

YES PLEASE!
it should be something like insertSpaceBetweenClosingParenthesisAndOpeningBraces
while(something) {, function() {, if(something) {, etc.

Tracking this on the TypeScript side with https://github.com/Microsoft/TypeScript/issues/13038
Thanks


syscall: x/tools broken on FreeBSD by FreeBSD 12 support CL

The x/tools subrepo seems to be broken after CL 138595. /cc @paulzhol
2018/10/10 14:30:05 goimports: scanning directory /tmp/workdir/go/src: open /tmp/workdir/go/src/cmd/compile/internal/ssa/testdata : no such file or directory
2018/10/10 14:30:05 goimports: scanning directory /tmp/workdir/go/src: open /tmp/workdir/go/src/runtime/msan	: no such file or directory
2018/10/10 14:30:05 goimports: scanning directory /tmp/workdir/go/src: open /tmp/workdir/go/src/math/randamd6E: no such file or directory
--- FAIL: TestFindImportInternal (0.00s)
    fix_test.go:1443: findImportGoPath("race", Acquire ...) = "", false; want "internal/race", false
2018/10/10 14:30:05 goimports: scanning directory /tmp/workdir/go/src: open /tmp/workdir/go/src/runtime/testdata.go: no such file or directory
2018/10/10 14:30:05 goimports: scanning directory /tmp/workdir/go/src: open /tmp/workdir/go/src/runtime/testdata.go: no such file or directory
2018/10/10 14:30:05 goimports: scanning directory /tmp/workdir/go/src: open /tmp/workdir/go/src/runtime/msan	: no such file or directory
2018/10/10 14:30:05 goimports: scanning directory /tmp/workdir/go/src: open /tmp/workdir/go/src/runtime/internaldefs3_liCH: no such file or directory
2018/10/10 14:30:05 goimports: scanning directory /tmp/workdir/go/src: open /tmp/workdir/go/src/math/randamd6E: no such file or directory
2018/10/10 14:30:05 goimports: scanning directory /tmp/workdir/go/src: open /tmp/workdir/go/src/cmd/compile/internal/ssa/testdata : no such file or directory
2018/10/10 14:30:05 goimports: scanning directory /tmp/workdir/go/src: open /tmp/workdir/go/src/runtime/testdata.go: no such file or directory
2018/10/10 14:30:05 goimports: scanning directory /tmp/workdir/go/src: open /tmp/workdir/go/src/cmd/compile/internal/ssa/testdata : no such file or directory
2018/10/10 14:30:05 goimports: scanning directory /tmp/workdir/go/src: open /tmp/workdir/go/src/runtime/testdata.go: no such file or directory
2018/10/10 14:30:05 goimports: scanning directory /tmp/workdir/go/src: open /tmp/workdir/go/src/runtime/internaldefs3_liCH: no such file or directory
FAIL
FAIL	golang.org/x/tools/imports	0.468s

See https://build.golang.org/?repo=golang.org%2Fx%2Ftools#short and https://go-review.googlesource.com/c/go/+/138595#message-71a4da926fb9669d319aa4b34fd9d548de32dc23.
/cc @bradfitz @bcmills @heschik

Looks like the null termination is broken when converting the FreeBSD 12 structs to the FreeBSD 11 structs.
I guess we're lacking test coverage of some system call(s) in std.

convertFromDirents11 seems to be broken but only occasionally. I'm investigation.
Unsurprisingly that test works on FreeBSD 12.


pulse_dispersion_scan.m: Too many output arguments error

When I run the pulse_dispersion_scan.m example in either MATLAB R2016b or R2020b, I get the following errors:
Error using LaserPulse/polynomialPhase
Too many output arguments.
Error in LaserPulse/subsref (line 23)
efield = pulse.(ref(1).subs);
Error in pulse_dispersion_scan (line 15)
p.polynomialPhase([2000 100 0 0])
I see someone on the Mathworks site is also experiencing a similar issue, and some of the other examples (such as pulse_autocorrelation.m and pulse_chirp_scan.m) give me similar errors.
Thanks for any help you can give with this issue - I can't wait to use your code for some simulations!

thank you for letting me know!
there was a bug in the customized subsref operator; I reverted to the default one and now at least in my matlab2015a the example scripts seem to work.
Please let me know if you find other bugs!

Thank you!! That’s fixed the problem for me.
-Christin
On Wednesday, November 4, 2020, Alberto Comin<EMAIL_ADDRESS>wrote:

thank you for letting me know!
there was a bug in the customized subsref operator; I reverted to the
default one and now at least in my matlab2015a the example scripts seem to
work.
Please let me know if you find other bugs!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/albeco/LaserPulse/issues/3#issuecomment-721967747,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAUJP4HX4S7PKPNDYEOTLJ3SOG47FANCNFSM4TKNKKQQ
.

May I also ask a question about usage? Do you happen to have a reference
that talks about how to propagate a pulse through a lens?
Thanks!
On Wednesday, November 4, 2020, Alberto Comin<EMAIL_ADDRESS>wrote:

thank you for letting me know!
there was a bug in the customized subsref operator; I reverted to the
default one and now at least in my matlab2015a the example scripts seem to
work.
Please let me know if you find other bugs!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/albeco/LaserPulse/issues/3#issuecomment-721967747,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAUJP4HX4S7PKPNDYEOTLJ3SOG47FANCNFSM4TKNKKQQ
.

Hi

usage: I typically used the LaserPulse code a library for simulations in nonlinear/ultrafast optics, which often involve Fourier transforming forth and back, zero padding, etc..

-propagation through a lens: the LaserPulse code currently accounts only for the pulse broadening effect (see the .propagate() method. It is possible to store the wavefront information by initializing the pulse with a multi-dimensional arrays; but there is no dedicated method for it. A very good reference is: https://www.photonics.ethz.ch/fileadmin/user_upload/Courses/NanoOptics/focus3.pdf;


feat: [#493] optimize session

📑 Description
RelatedTo https://github.com/goravel/goravel/issues/493

@coderabbitai summary

✅ Checks

[ ] Added test cases for my code

I have another question, what is the use of _token in session?

I have another question, what is the use of _token in session? It seems to just set but not used.

I initially started implementing session-based CSRF verification middleware but later dropped the idea. The _token is typically used for CSRF protection. (and result was session module)


fix: Fix transaction fields serde names

Pretty self-explanatory I think, it works for me now.

Hi @marcusbuffett, I apologize for the delayed response. Thank you for your contribution!


[BUG] Objects size metrics is incorrect

Description
Objects size metric produces incorrect value
Steps to reproduce the issue
Maximum value on the dashboard is around 179 kb
Describe the results you expected
Should match the size of the maximum file streamed.
System information
0.0.2

False alert.


MAISTRA-2441: Restore proxyEnv support

Restore missing proxyEnv support for injection

Seriously? We are forcing American English?

/test unit


Fixing CRLF problem on Windows

On Windows newline is represented as CRLF ('\r\n').
When file is open in "r' (not "rb") mode, the \rs are omitted and fread returns number of actual bytes read which might be smaller than file size.
In this case validation in the wren code will fail.
This patch changes the way validation is done to prevent the problem without complicating lexer.

I definitely appreciate not wanting to complicate the lexer, but I think the language grammar probably should specify that \r is an ignored whitespace character. That way, if you open a Windows (i.e. \r\n) file on a Unix machine, it still does the right thing.
This was a mistake on my part. I think the right thing to do is to fopen with "rb". That way the behavior isn't platform-specific. I can fix the lexer if you want or you're welcome to. You'll basically just be handling \r around line 788 in wren_compiler.c.


docs: Added configuration for Minio as paperclip storage backend.

This can be closed via https://github.com/minio/cookbook/pull/108

Please remove the bullet mark in the explore further section of the cookbook.

@GarimaKapoor please review https://github.com/minio/cookbook/pull/109

I'm using minio for storing attachments, any one have an idea about how much hardware capacity should i have for this depending how much users i have!
for example: for this 3 cases:

10 users
200 users
1M users
thank you!

@ZennouRachid we can best answer this on https://slack.minio.io - please join us there.. Thanks

// cc @NitishT can you review?


Update audioframe_lockbuffer_1248676457.md

@drewbatgit : PR passed checklist review. Please evaluate further and approve/merge if appropriate. Thanks!


PTX Reintegration and Passing Tests

Making progress on getting the tests passing, so opening a draft pull request. Will cleanup once all the tests are passing.

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/codegen/linearizer.py             1               1
tinygrad/ops.py                            2               2
tinygrad/renderer/assembly.py            204               0
tinygrad/renderer/assembly_ptx.py         90               0
tinygrad/runtime/ops_cuda.py               3               3
------------------------------------------------------------
total                                    300               6
------------------------------------------------------------
lines added in the tinygrad folder: 294

is this working with gpuocelot ?

Had to fix the runtime args, but it is now. Actually passing more tests with PTX=1 CUDACPU=1 than PTX=1 alone.

It occurred to me that in cases where e.g. PTX doesn't support the instruction with a specific type and an additional casting instruction is needed, I've been putting this in assembly.py as an additional asm instruction (which is probably not what we want if this is going to be shared with other asm backends). It seems plausible that this could all be moved to assembly_ptx, but at some level we have to deal with this in assembly.py or as some kind of pre-pass so that we can have all of the DEFINE_REGISTER instructions we need.

Should just be two more code changes to get all the tests passing, then the change I mentioned above and cleanup. I don't have write access for tests.yml to add to CI. Otherwise, should be able to get it wrapped up in the next couple days if not tonight.

So it looks like with just PTX, the CUDA env variable isn't required, but with CUDACPU=1 it is, so I never actually properly tested gpuocelot before. I can't get it to build on my machine though, so I can't actually get it to run with or without PTX.
The only thing that should be left is fixing overflow/underflow. Basically, PTX doesn't wrap on under/overflow when converting from float, which is exacerbated by the fact that linearizer always sets the Token.dtype to float for ConstOp. So the easiest solution is just to always cast to int first before casting to uint, but it seems strange to add a hacky extra instruction so that we can get worse overflow/underflow behavior?

Could someone with write access add PTX to test.yml? Something like the patch below

Patch
diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
index 8ac1e08..19e7cee 100644
--- a/.github/workflows/test.yml
+++ b/.github/workflows/test.yml
@@ -199,7 +199,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        backend: [llvm, clang, gpu, cuda]
+        backend: [llvm, clang, gpu, cuda, ptx]

     name: Tests on (${{ matrix.backend }})
     runs-on: ${{ matrix.backend == 'gpu'  && 'ubuntu-20.04' || 'ubuntu-latest' }}
@@ -218,7 +218,7 @@ jobs:
           path: '~/.cache/pip'
           key: ${{ matrix.backend }}
       - name: Set env
-        run: printf "${{ matrix.backend == 'llvm' && 'ENABLE_METHOD_CACHE=1\nLLVM=1' || matrix.backend == 'clang' && 'CLANG=1\nENABLED_METHOD_CACHE=1' || matrix.backend == 'gpu' && 'GPU=1' || matrix.backend == 'cuda' && 'FORWARD_ONLY=1\nJIT=1\nOPT=2\nCUDA=1\nCUDACPU=1\n'}}" >> $GITHUB_ENV
+        run: printf "${{ matrix.backend == 'llvm' && 'ENABLE_METHOD_CACHE=1\nLLVM=1' || matrix.backend == 'clang' && 'CLANG=1\nENABLED_METHOD_CACHE=1' || matrix.backend == 'gpu' && 'GPU=1' || matrix.backend == 'cuda' && 'FORWARD_ONLY=1\nJIT=1\nOPT=2\nCUDA=1\nCUDACPU=1\n' || matrix.backend == 'PTX' && 'PTX=1'}} " >> $GITHUB_ENV
       - name: Find faster apt mirror
         uses: vegardit/fast-apt-mirror.sh@v1
       - name: Install packages (gpu)
@@ -229,12 +229,12 @@ jobs:
           sudo apt-get update -y && \
           sudo apt-get install -y intel-oneapi-runtime-compilers intel-oneapi-runtime-opencl
       - name: Install packages (cuda)
-        if: matrix.backend == 'cuda'
+        if: matrix.backend == 'cuda' || matrix.backend == 'ptx'
         run: |
           sudo apt-get update -y && \
           sudo apt-get install -y --no-install-recommends git g++ cmake ninja-build llvm-15-dev zlib1g-dev libglew-dev flex bison libfl-dev libboost-thread-dev libboost-filesystem-dev nvidia-cuda-toolkit-gcc
       - name: Cache gpuocelot
-        if: matrix.backend == 'cuda'
+        if: matrix.backend == 'cuda' || matrix.backend == 'ptx'
         id: cache-build
         uses: actions/cache@v3
         env:
@@ -243,7 +243,7 @@ jobs:
           path: ${{ github.workspace }}/gpuocelot/ocelot
           key: ubuntu22.04-gpuocelot-19626fc00b6ee321638c3111074269c69050e091
       - name: Clone/compile gpuocelot
-        if: matrix.backend == 'cuda' && steps.cache-build.outputs.cache-hit != 'true'
+        if: (matrix.backend == 'cuda' || matrix.backend == 'ptx') && steps.cache-build.outputs.cache-hit != 'true'
         run: |
           git clone --recurse-submodules https://github.com/gpuocelot/gpuocelot.git ${{ github.workspace }}/gpuocelot
           cd ${{ github.workspace }}/gpuocelot/ocelot
@@ -253,7 +253,7 @@ jobs:
           cmake .. -Wno-dev -G Ninja -DOCELOT_BUILD_TOOLS=OFF
           ninja
       - name: Install gpuocelot
-        if: matrix.backend == 'cuda'
+        if: matrix.backend == 'cuda' || matrix.backend == 'ptx'
         run: |
           cd ${{ github.workspace }}/gpuocelot/ocelot/build
           sudo ninja install
@@ -262,8 +262,11 @@ jobs:
       - name: Check Device.DEFAULT
         run: python -c "from tinygrad.lazy import Device; assert Device.DEFAULT in ['LLVM','CLANG','CUDA','GPU'], Device.DEFAULT"
       - name: Run pytest (not cuda)
-        if: matrix.backend!='cuda'
+        if: matrix.backend!='cuda' && matrix.backend!='ptx'
         run: python -m pytest -n=auto test/ -k '${{matrix.backend=='llvm'&&'not (test_nn.py and test_conv_transpose2d)'||'test'}}' -m 'not exclude_${{matrix.backend}}'
       - name: Run pytest (cuda)
         if: matrix.backend=='cuda'
         run: python -m pytest -n=auto test/ -k 'not (half or test_efficientnet_safetensors) and not (test_conv2d and test_tensor.py)' -m 'not exclude_cuda' --ignore=test/external --ignore=test/models
+      - name: Run pytest (ptx)
+        if: matrix.backend=='ptx'
+        run: python -m pytest -n=auto test/ -k 'not test_uops' -m 'not exclude_cuda' --ignore=test/external --ignore=test/models

Can you move assembly and assembly_ptx back to extra/assembly so I can read the diff?

So, both #1412 and this are in similar places...how bad are the merge conflicts?
How should I determine who is merged first, or maybe one of you doesn't care.

It's mostly the same, we are handling casting in different ways tho.  I think adding UOps.CAST  inside load and store adds more complexity. My approach basically is the same as in llvmir.py.
I'm passing all the tests btw, you were right about unicorn I was able to bring it down to 12 min with ~26 new lines of code.

I merged ARM first (since the PR was first). Moving assembly to the main codebase #1544

On a real NVIDIA machine
batman@x840:~/tinygrad$ FORWARD_ONLY=1 PTX=1 CUDA=1 python3 test/test_ops.py TestOps.test_add
test_add (__main__.TestOps) ... /home/batman/.pyenv/versions/3.8.10/lib/python3.8/site-packages/pycuda/compyte/dtypes.py:120: DeprecationWarning: `np.bool8` is a deprecated alias for `np.bool_`.  (Deprecated NumPy 1.24)
  reg.get_or_register_dtype("bool", np.bool8)
ERROR

======================================================================
ERROR: test_add (__main__.TestOps)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test/test_ops.py", line 214, in test_add
    helper_test_op([(45,68), (45,68)], lambda x,y: x+y, Tensor.add)
  File "test/test_ops.py", line 25, in helper_test_op
    ret = tinygrad_fxn(*tst).realize()
  File "/home/batman/xx/openpilot/tinygrad/tensor.py", line 94, in realize
    self.lazydata.realize()
  File "/home/batman/xx/openpilot/tinygrad/lazy.py", line 159, in realize
    self.realized = Device[self.device].exec_ast(self.op, output=self, **self._device_extra_args())
  File "/home/batman/xx/openpilot/tinygrad/ops.py", line 196, in exec_ast
    if k.key not in self.method_cache: self.method_cache[k.key] = get_program()
  File "/home/batman/xx/openpilot/tinygrad/ops.py", line 193, in get_program
    return self.to_program(k)
  File "/home/batman/xx/openpilot/tinygrad/ops.py", line 162, in to_program
    return ASTRunner(k.function_name, src, global_size, local_size,
  File "/home/batman/xx/openpilot/tinygrad/ops.py", line 131, in build
    self.clprg = runtime(self.name, self.prg, **self.runtime_args)
  File "/home/batman/xx/openpilot/tinygrad/runtime/ops_cuda.py", line 71, in __init__
    self.prg = cuda.module_from_buffer(prg.encode('utf-8')).get_function(prg.split(".visible .entry ")[1].split("(")[0])
pycuda._driver.LogicError: cuModuleLoadDataEx failed: the provided PTX was compiled with an unsupported toolchain. - ptxas application ptx input, line 1; fatal   : Unsupported .version 8.2; current version is '8.1'

----------------------------------------------------------------------
Ran 1 test in 0.120s

FAILED (errors=1)

Actually, could probably just search for the .version line in an nvcc compiled kernel. I'll look into it tonight if you prefer that approach.

batman@x840:~$ nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2022 NVIDIA Corporation
Built on Wed_Sep_21_10:33:58_PDT_2022
Cuda compilation tools, release 11.8, V11.8.89
Build cuda_11.8.r11.8/compiler.31833905_0

I think you can just use an older version everywhere if you aren't using any of the new features

I'm at a bit of a loss why the error message says current version = 8.1 with CUDA 11.8, so I might be misinterpreting the chart. It seems like ISA 7.8 is the oldest that supports the 4090 though, so I went with that.

Bounty is yours! E-mail your PayPal to<EMAIL_ADDRESS>to claim.


Seeking co-maintainers!

I've been shifting my focus away from UI development, so don't plan on addressing new issues myself. If you use this library and want to see development continue, you can make that happen by becoming a co-maintainer — with permissions to triage issues, merge PRs, cut releases, etc.
Please comment below if you're interested!
Another possibility is for a dedicated owner to fork this code and create a new package. I'd be happy to link to that library from the README of this one.

Let me know where I can help. I do a lot of Accessibility work for target.com and I am a big fan of this utility!

We use this package in Reach UI and I would be more than happy to join the team. Let me know how we can help.

Appreciate the quick response here. Let me know if you have any preferences on process or if you're happy to just have me start reviewing PRs and merging updates. I went ahead and forked it just to get dependencies updated and fix the build in Travis, I'll start with that unless you have any objections.

@chancestrickland Please feel free to take the reins and act as owner. I'll try to keep an eye on things and will speak up if I disagree with a move — but otherwise go ahead and make & review & merge PRs. When you're ready to publish let me know. After that first publish, I'll give you npm collab access, too.

@davidtheclark @chancestrickland Given the inter-dependence of this library with tabbable and focus-trap-react, what do you think about moving this repo to the https://github.com/focus-trap org where we've already moved focus-trap-react? I'd still keep this issue open for maintainers, though!

@davidtheclark Thanks for moving the repo over!

@davidtheclark Can you confirm whether I have permission to publish this package in NPM? I need to make a release.

Closing this. Seems like I'm running the show now. 😅


controller added

@shubhodeep9  controller added according to --name argument issue as discussed in issue #13

👍


Integration Test - Release - 2020/11/18 18:11:43

Auto create for integration test. IssueCommandFlow

#pri1

Just type '#pri3'

#pri2

#pri3

#assign PRMergerTest1

#assign NonAllowedUser

NonAllowedUser is not a valid GitHub ID, or is not a collaborator on this repo.

#reassign PRMergerTest2

GitHub user PRMergerTest2 has been removed from the MicrosoftDocs organization, so they were automatically removed as an assignee.

#reassign NonAllowedUser

NonAllowedUser is not a valid GitHub ID, or is not a collaborator on this repo.

#please-close


Sruthi/improve pii logging

Context
User can turn off logging Personally Identifiable Information (PII) by setting a boolean (ShowPII = false). This is the recommended setting in production and is set by default.
Problem Statement
Currently, all log message arguments are treated as PII and scrubbed as part of message formatting making debugging challenging
Proposed Changes
Mark Non-PII arguments as such by wrapping the argument with LogHelper.MarkAsNonPII(argName) method. This includes system metadata like variable/method/class names, data types, timestamps, claim names and algorithms used. Do this for all log and exception messages

ASIDE: Are there any tricks for turning on word wrap etc

The GitHub mobile app has a line wrapping option.

Finished looking at all the files at least once. didn't make it back to review all the files that changed since the first review. Left a few comments. Thanks for all the good work here @sruke !

https://github.com/StylishThemes/GitHub-code-wrap << Just do the word wrap on the website
https://github.com/henrik-me/Github-Codeflow-Extension-Edge << Allow GitHub PRs to be reviewed using CodeFlow!

In reply to: 961374858

Can you please double-check this change will address the issue outlined in https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/issues/1762 ?


Add check for modified files loaded from HDFS

This PR will avoid losing data in case two different extractions update the files after loading the same hdfs file.
Tests:
target_hdfs.sinks.CanNotUploadFileError: The HDFS file **** was modified after it was loaded.

Thank you for your suggestion, @jessie-ross! Initially, I considered using a lock file, but I was concerned that if the Meltano extraction was externally killed, the lock files would have to be manually deleted each time. However, I believe it is worth a try to see if this occurs.

Initially, I considered using a lock file, but I was concerned that if the Meltano extraction was externally killed, the lock files would have to be manually deleted each time. However, I believe it is worth a try to see if this occurs.

We could also put a timestamp into the lockfiles, and if the time is too old we can auto-clear the lock.


"Format SQL" incorrectly inserts spaces in scientific notation of numbers

System information:

Operating system (distribution) and version: Windows 10
DBeaver version: 6.0.4
Java version: 8
Additional extensions

Connection specification:

Database name and version: PostgreSQL 11.2 / PostGIS 2.5.2
Driver name: PostgreSQL driver for Windows
Do you use tunnels or proxies (SSH, SOCKS, etc)?

Describe the problem you're observing:
"Format SQL" incorrectly inserts spaces in scientific notation of numbers, see the spaces around the "+" as inserted after selecting "Format SQL", which should read as "9E+6". As a consequence, running the query results in an error. Removing the spaces result in successful query evaluation.

Thanks for the bug report

verified


Video gets cut off on the right and the views and date are shifted.

I used the Stylus version of the youtube-style, and when I have the window in fullscreen, the right portion of the video gets cut off.  In addition, the views and the video creation date are now shifted to the default YouTube style (probably due to Youtube's recent update of updating the view counts without refreshing the video).
Video cutting off:

Views and date are being shifted:

I think it is a new update that broke the YouTube styles, as I can use a guest account on private mode just fine, but when I log in to my account, YouTube broke the style, unfortunately.

The video being cut off still appears even when I have a guest account, but the views and date is perfectly intact.

Thanks for the bug report! I'm on vacation rn but I'll take a look when I have the time


false positive:  WARNING:  ../../log4j-samples/false-hits/log4j-core-2.12.2.jar contains "JndiLookup.class"

2.12.2 is not vulnerable to CVE-2021-44228.
I am maintaining a collection of samples here that you may find useful for testing:  https://github.com/mergebase/log4j-samples

Thanks for this!