1.1.1 update breaks @mock_cloudformation_deprecated

we are still using @mock_cloudformation_deprecated for cloud formation (boto2)
everything works on 1.0.1, but once update to 1.1.1
we receive error on create stack on cloud formation
this is our deploy code:
    c = CloudFormation(self.parameters['aws_access_key_id'],
                       self.parameters['aws_secret_access_key'],
                       self.parameters['region'])
    c.deploy(stack_name=self.parameters['stack_name'],
             template_url=self.parameters['template_url'],
             parameters=cloudformation_parameters)

below is the error trackback
tests/test_src/test_aws_cloudformation_provision.py:47:

src/aws_cloudformation_provision.py:155: in run
self.deploy_stack()
src/aws_cloudformation_provision.py:117: in deploy_stack
parameters=cloudformation_parameters)
src/aws_cloudformation_provision.py:186: in deploy
stack_policy_body, stack_policy_url)
../../../python/p2/lib/python2.7/site-packages/boto/cloudformation/connection.py:403: in create_stack
body = self._do_request('CreateStack', params, '/', 'POST')
../../../python/p2/lib/python2.7/site-packages/boto/cloudformation/connection.py:296: in _do_request
response = self.make_request(call, params, path, method)
../../../python/p2/lib/python2.7/site-packages/boto/connection.py:1116: in make_request
return self._mexe(http_request)
../../../python/p2/lib/python2.7/site-packages/boto/connection.py:944: in _mexe
response = connection.getresponse()
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/httplib.py:1118: in getresponse
response = self.response_class(*args, **kwds)
../../../python/p2/lib/python2.7/site-packages/boto/connection.py:390: in init
http_client.HTTPResponse.init(self, *args, **kwargs)
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/httplib.py:375: in init
self.fp = sock.makefile('rb', 0)
../../../python/p2/lib/python2.7/site-packages/moto/packages/httpretty/core.py:340: in makefile
self._entry.fill_filekind(self.fd)
../../../python/p2/lib/python2.7/site-packages/moto/packages/httpretty/core.py:603: in fill_filekind
self.request, self.info.full_url(), headers)
../../../python/p2/lib/python2.7/site-packages/moto/core/utils.py:106: in call
result = self.callback(request, url, headers)
../../../python/p2/lib/python2.7/site-packages/moto/core/responses.py:111: in dispatch
return cls()._dispatch(*args, **kwargs)
../../../python/p2/lib/python2.7/site-packages/moto/core/responses.py:179: in _dispatch
return self.call_action()
../../../python/p2/lib/python2.7/site-packages/moto/core/responses.py:196: in call_action
response = method()
../../../python/p2/lib/python2.7/site-packages/moto/cloudformation/responses.py:57: in create_stack
role_arn=role_arn,
../../../python/p2/lib/python2.7/site-packages/moto/cloudformation/models.py:152: in create_stack
cross_stack_resources=self.exports,
../../../python/p2/lib/python2.7/site-packages/moto/cloudformation/models.py:34: in init
self.resource_map = self._create_resource_map()
../../../python/p2/lib/python2.7/site-packages/moto/cloudformation/models.py:42: in _create_resource_map
resource_map.create()
../../../python/p2/lib/python2.7/site-packages/moto/cloudformation/parsing.py:425: in create
if isinstance(self[resource], ec2_models.TaggedEC2Resource):
../../../python/p2/lib/python2.7/site-packages/moto/cloudformation/parsing.py:365: in getitem
resource_logical_id, resource_json, self, self._region_name)
../../../python/p2/lib/python2.7/site-packages/moto/cloudformation/parsing.py:258: in parse_and_create_resource
resource_tuple = parse_resource(logical_id, resource_json, resources_map)
../../../python/p2/lib/python2.7/site-packages/moto/cloudformation/parsing.py:233: in parse_resource
resource_json = clean_json(resource_json, resources_map)
../../../python/p2/lib/python2.7/site-packages/moto/cloudformation/parsing.py:200: in clean_json
cleaned_val = clean_json(value, resources_map)
../../../python/p2/lib/python2.7/site-packages/moto/cloudformation/parsing.py:200: in clean_json
cleaned_val = clean_json(value, resources_map)
../../../python/p2/lib/python2.7/site-packages/moto/cloudformation/parsing.py:207: in clean_json
return [clean_json(val, resources_map) for val in resource_json]
../../../python/p2/lib/python2.7/site-packages/moto/cloudformation/parsing.py:200: in clean_json
cleaned_val = clean_json(value, resources_map)

resource_json = {'Fn::Select': [0, {'Fn::GetAtt': ['Subnets']}]}, resources_map = <moto.cloudformation.parsing.ResourceMap object at 0x10d8dad10>
def clean_json(resource_json, resources_map):
    """
    Cleanup the a resource dict. For now, this just means replacing any Ref node
    with the corresponding physical_resource_id.

    Eventually, this is where we would add things like function parsing (fn::)
    """
    if isinstance(resource_json, dict):
        if 'Ref' in resource_json:
            # Parse resource reference
            resource = resources_map[resource_json['Ref']]
            if hasattr(resource, 'physical_resource_id'):
                return resource.physical_resource_id
            else:
                return resource

        if "Fn::FindInMap" in resource_json:
            map_name = resource_json["Fn::FindInMap"][0]
            map_path = resource_json["Fn::FindInMap"][1:]
            result = resources_map[map_name]
            for path in map_path:
                result = result[clean_json(path, resources_map)]
            return result

        if 'Fn::GetAtt' in resource_json:
            resource = resources_map.get(resource_json['Fn::GetAtt'][0])
            if resource is None:
                return resource_json
            try:
                return resource.get_cfn_attribute(resource_json['Fn::GetAtt'][1])
            except NotImplementedError as n:
                logger.warning(str(n).format(
                    resource_json['Fn::GetAtt'][0]))
            except UnformattedGetAttTemplateException:
                raise ValidationError(
                    'Bad Request',
                    UnformattedGetAttTemplateException.description.format(
                        resource_json['Fn::GetAtt'][0], resource_json['Fn::GetAtt'][1]))

        if 'Fn::If' in resource_json:
            condition_name, true_value, false_value = resource_json['Fn::If']
            if resources_map.lazy_condition_map[condition_name]:
                return clean_json(true_value, resources_map)
            else:
                return clean_json(false_value, resources_map)

        if 'Fn::Join' in resource_json:
            join_list = clean_json(resource_json['Fn::Join'][1], resources_map)
            return resource_json['Fn::Join'][0].join([str(x) for x in join_list])

        if 'Fn::Split' in resource_json:
            to_split = clean_json(resource_json['Fn::Split'][1], resources_map)
            return to_split.split(resource_json['Fn::Split'][0])

        if 'Fn::Select' in resource_json:
            select_index = int(resource_json['Fn::Select'][0])
            select_list = clean_json(resource_json['Fn::Select'][1], resources_map)

          return select_list[select_index]

E               KeyError: 0
../../../python/p2/lib/python2.7/site-packages/moto/cloudformation/parsing.py:171: KeyError

just fond the broken part.
1.0.1 has no problem with
AvailabilityZone": {
"Default": "us-east-1b",
"Type": "AWS::EC2::AvailabilityZone::Name",
"Description": "Availablity zone used for the bridge"
},
but 1.1.1 seems have issue with it.
by change the Type to "String", everything works fine

@nadlerjessie Could you take a look at this? This is something that you're pretty good at and it's a bit over my head

Sorry for the delayed response on this.
@ruivapps Can you please let me know what clean_json({'Fn::GetAtt': ['Subnets']}, resource_map) evaluates to? If I am reading your error correctly, it looks like it will be an empty list in 1.1.1. I'd be curious to see what the results are for both versions 1.0.1 and 1.1.1. Thanks!

when I am testing it again. with moto 1.1.11
I no longer see the problem


Update Python files to Python 3.12

As the Docker images are based on Python 3.12.
This updates the pyproject file to depend on Python 3.12.
And also updates the lock file with the command poetry lock --no-update.

These are already different, should those file be removed in one repository, to reduce dependency management and so on.

Thanks for pointing this out! I think removing lock files from actions-mkdocs would be the better solution. I'll update the repo.


Makefile: allow debug info to be specified

Add variable `DEBUG' that can be used to specify debug flags for the Go
tool when building either the client or the lxd.
For example:
$ DEBUG='-gcflags "-N -l"' make
The -N flag enables debug information and -l disables compiler inlining.
Example of how to debug using lldb can be found here:
http://ribrdb.github.io/lldb/
http://blog.ralch.com/tutorial/golang-debug-with-lldb/
Signed-off-by: Andrew McDermott<EMAIL_ADDRESS>

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"


Virtual documents: allow the document to be colored with a mode

I think it would be cool to have a way for a virtual document to be colored by one of the language modes installed so that you can e.g. show code snippets for a language and leverage the same coloring we already have for files.

You can. just chose the right filename or extension and tata


fix 404 Not Found message

make 404 text / link app-aware

sometimes public/404.html gets displayed and it has inconsistent message and look from the normal "Page not found" message in addition to not being app-aware

This is a static page, so cannot be made app-aware, however it only gets
displayed in very rare circumstances that may not even occur on
production.  Changed the message from FreeReg to FreeCen in the
freecen_parsing branch.
On Wed, Jun 29, 2016 at 9:53 AM, sean-wood<EMAIL_ADDRESS>wrote:

Assigned #105 https://github.com/FreeUKGen/FreeCENMigration/issues/105
to @dougkdev https://github.com/dougkdev.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FreeUKGen/FreeCENMigration/issues/105#event-707964579,
or mute the thread
https://github.com/notifications/unsubscribe/ANHfzmABNxYmggqVqz7qvdsUQhKyiqSbks5qQpUCgaJpZM4Ii3VD
.


[CI] Release pipeline test case 2

This is to test on scenario that user modify both src/index.json and extension source code.
This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/haroldrandom/azure-cli-extensions.git@release-pipeline-test-case-2#subdirectory=src/$EXT&egg=$EXT"


Compatibility with Kotlin 1.3.40

As @jonasbark said here https://github.com/AlecStrong/kotlin-native-cocoapods/issues/21#issuecomment-499861942 this plugin should still be updated for compatibility reasons, but it doesn't with Kotlin 1.3.40. Might it be fixed?

I think it should work with 1.3.40 as well based on my latest commits. I'm just not sure the newest version with my fixes was ever published?

Oh yeah, it just wasn't published


[Bug] Session ID not being used in file name for 'Run Conversion' step

I built a pipeline with session_id="testing_123", but the output file name (before DANDI organize + upload) was sub-001_ses-1.nwb which is the 'session ID' from the subject table, which was not updated by the downstream forms
The filename should instead show up as sub-001_ses-testing-123.nwb (NOTE: that underscore was converted to a dash in the name since underscores within a block get converted to dashes following the DANDI convention)

You updated the session_id field in the File Metadata section, correct? At present, we've assumed that these updates are only handled on the Subjects table.
The quickest way to handle this specific issue would be to ignore the session_id and subject_id options in the File Metadata page, as changing these would require a complete re-render of that page (or at least many elements) anyways.
This solution is what we decided on in #201, where different aspects of the same problem are discussed.
In addition to the discussion on #201, a more general problem here is that we have two representations of subject metadata:

The Subjects table
One Subject accordion per subject + session combination

It is easy enough to apply (1) as the default value for each session in (2). However, it is not straightforward—nor is it conceptually accurate—to merge (2) into (1).
As such, we need to reconcile changes on both. How would we like to do this?
At first thought, it could be most straightforward to only allow entry of immutable fields (e.g. subject_id, date_of_birth, etc.), thereby limiting the editable metadata in the File Metadata section to things like weight and age. But this is just what's on the top of my mind.
If this is a line of inquiry we'd like to pursue, we should probably move this discussion to a separate issue before going too far.

I've published several related PRs that limit the extent of this issue.
#262 removes the ability of the user to edit these IDs on the File Metadata form.
#264 implements a proper data cascade so that the GUIDE generally only allows updates to flow to dependent forms (e.g. Subject table to NWB File Subject metadata) if the dependent value hasn't been modified by the user.
With these updates, the user is more clearly locked into their decisions made earlier in the application—though they can apply overrides to properties that don't structure the UI itself (e.g. not session_id and subject_id).
We may wish to further lock decisions, as noted in the previous comment. But this particular bug isn't really an intended behavior to begin with—and now it can't be done.

Closed based on the data flow updates in #262 and #264


AttributeError: module 'slowfast.config.defaults' has no attribute '_assert_and_infer_cfg'

Does your code rely on a specific version of SlowFast? It appears that the interface you are using does not match their current latest!

Resolved the issue; see this commit.


Fix RTN20.

I've tested the ARTOSReachability "live" manually (by switching on/off
the real Internet connection on my machine) and it works as expected,
but it needs #385 to properly handle transport errors.

LGTM

@mattheworiordan I rebased it with master.
RTN20 tests are passing and they look good.
Can I force push? /cc @tcard

Yes, please force push.  Are any other tests failing?

@mattheworiordan Yes, there is at least one test failing with something related this PR:
Test Case '-[AblySpec.Auth Token__token_auth_and_clientId__Incompatible_client__with_Realtime__it_should_change_the_connection_state_to_FAILED_and_emit_an_error]' started.
INFO: R:0x7fc6daa1ce80 ARTRealtime closed
INFO: Reachability: stopped listening for host (null)
ERROR: R:0x7fc6daa377c0 WS:0x7fc6daa38f80 ARTWebSocketTransport: token auth failed with ARTErrorInfo with code 401, message: incompatible credentials
EXC_BAD_ACCESS

@ricardopereira well from the title of that test, it should raise an incompatible credentials error I believe, so it sounds like that is a test that genuinely needs to be fixed then.

@mattheworiordan The test is fine. I made a fix and it is running now.
I'm running all the test suite on my machine.

Legacy tests:

Specs:
Test Suite 'AblySpec.xctest' failed at 2016-08-25 10:57:51.589.
	 Executed 520 tests, with 6 failures (0 unexpected) in 417.708 (418.077) seconds
Test Suite 'All tests' failed at 2016-08-25 10:57:51.591.
	 Executed 520 tests, with 6 failures (0 unexpected) in 417.708 (418.080) seconds

Failed:
/Users/ricardopereira/Repositories/Whitesmith/ably-ios/Spec/RealtimeClientPresence.swift:907: error: -[AblySpec.RealtimeClientPresence Presence__enter__should_result_in_an_error_if_the_client_does_not_have_required_presence_permission] : expected to contain <Channel denied access based on given capability>, got <Invalid clientId for credentials>
Test Case '-[AblySpec.RealtimeClientPresence Presence__enter__should_result_in_an_error_if_the_client_does_not_have_required_presence_permission]' failed (0.894 seconds).

/Users/ricardopereira/Repositories/Whitesmith/ably-ios/Spec/RealtimeClientPresence.swift:980: error: -[AblySpec.RealtimeClientPresence Presence__update__should_result_in_an_error_if_the_client_does_not_have_required_presence_permission] : expected to contain <Channel denied access based on given capability>, got <Invalid clientId for credentials>
Test Case '-[AblySpec.RealtimeClientPresence Presence__update__should_result_in_an_error_if_the_client_does_not_have_required_presence_permission]' failed (0.859 seconds).

/Users/ricardopereira/Repositories/Whitesmith/ably-ios/Spec/RealtimeClientPresence.swift:1221: error: -[AblySpec.RealtimeClientPresence Presence__leave__should_result_in_an_error_if_the_client_does_not_have_required_presence_permission] : expected to contain <Channel denied access based on given capability>, got <Invalid clientId for credentials>
Test Case '-[AblySpec.RealtimeClientPresence Presence__leave__should_result_in_an_error_if_the_client_does_not_have_required_presence_permission]' failed (0.918 seconds).

/Users/ricardopereira/Repositories/Whitesmith/ably-ios/Spec/RealtimeClientPresence.swift:1885: error: -[AblySpec.RealtimeClientPresence Presence__history__should_return_a_PaginatedResult_page] : expected to all pass a condition, but failed first at element <<ARTPresenceMessage: 0x7fb114258ea0> {id:
...
/Users/ricardopereira/Repositories/Whitesmith/ably-ios/Spec/RealtimeClientPresence.swift:1900: error: -[AblySpec.RealtimeClientPresence Presence__history__should_return_a_PaginatedResult_page] : expected to all pass a condition, but failed first at element <<ARTPresenceMessage: 0x7fb11417f610> {id:
...
Test Case '-[AblySpec.RealtimeClientPresence Presence__history__should_return_a_PaginatedResult_page]' failed (2.681 seconds).

/Users/ricardopereira/Repositories/Whitesmith/ably-ios/Spec/RestClientPresence.swift:501: error: -[AblySpec.RestClientPresence Presence__presence_messages_retrieved_are_decoded_in_the_same_way_that_messages_are_decoded] : expected to equal <{test = 1;}>, got <nil> (use beNil() to match nils)
2016-08-25 10:56:47.359 xctest[77206:4299336] INFO: Reachability: stopped listening for host sandbox-realtime.ably.io
Test Case '-[AblySpec.RestClientPresence Presence__presence_messages_retrieved_are_decoded_in_the_same_way_that_messages_are_decoded]' failed (1.507 seconds).

@tcard @mattheworiordan Ready to be reviewed.

LGTM


VDom (maquette) integration 1

This PR is part of the ongoing process to improve both the communication (WS) protocol and client side rendering framework. The main change here is the introduction of a virtual DOM js library, maquette, with minimal changes to the current setup.
Motivation and Context
There are a number of good reasons to use a virtual DOM setup. From our standpoint, we would like to ensure efficiency in browser rendering on DOM changes as well as a simple, lightweight, API that will be the foundation of a unified WS protocol (see here for a draft)).
Additional motivation include a simplified client-side setup to allow for better event binding, callbacks and debugging (see discussion in this PR).
Maquette is very lightweight, has great documentation, and is designed to do just this sort of thing and do it well.
Approach
All interaction with the DOM is now handled by the maquette library. All html coming over the WS is converted to a maquette vdom element and all updates, appends and replacements are handled by the maquette projector.
Note: the general client-side rendering and logic has not been altered. For example, the two caches designed to deal with DOM interactions are still present:

this.cells (designed to keep copies of content, some rendered, some to be rendered DOM elements) and
div[id="holding_pen"] (designed to allow for "off-screen" DOM element manipulation).

Neither of these is effectively changed from a logic standpoint. In addition, raw html is still coming across the wire now converted to vdom elements. The goal is to have minimal impact on anything server-side, making an incremental change, but also not avoid development which will become moot with near future changes.
After this PR, the next steps should involve updating the WS protocol to send structured (json) data, as described here, simplify the protocol itself, and remove the multiple DOM caches with their respective logic to allow for a simple DOM update API.
How Has This Been Tested?
Development has been client-side only and testing was done by inspecting the object_database_webtest.py application.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Framework refactoring.

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
(only inline documentation has been updated)

There is a bug when trying to view the GraphDisplay's feigenbaum tab

GraphDisplay's feigenbaum tab bug is present on dev - it's not related to any of the changes here.
Lets open an issue about it

These changes were merged in with the process that resolved #102


Function arrow name property.

Right now I'm using:
node.js: 9.8.0
Jest: 23.4.2
ts-jest: 23.1.3
typescript: 2.9.2
And when trying to doing the following in my *.test.ts files:
const foo = () => 'bar';
console.log(foo.name); // '' -- empty string, not undefined or null

foo has the property name in it but is empty. I've run the same code in a separate *.ts file, just to know whether or not was some .tsconfig setting, but the console prints out 'foo' as expected.
My jest.config.json:
{
    "bail": true,
    "expand": true,
    "verbose": true,
    "useStderr": true,
    "forceExit": true,
    "logHeapUsage": true,
    "collectCoverage": true,
    "testRegex": "(./ci/__tests__/.*| (\\.|/)(test|spec))\\.(jsx?|tsx?)$",
    "transform": {
        "^.+\\.tsx?$": "ts-jest"
    },
    "moduleFileExtensions": [
        "ts",
        "tsx",
        "js",
        "jsx",
        "json",
        "node"
    ],
    "coveragePathIgnorePatterns": [
        "./node_modules/",
        "./dist/"
    ],
    "coverageReporters": [
        "json",
        "lcov",
        "text"
    ],
    "globals": {
        "ts-jest": {
            "enableTsDiagnostics": true
        }
    }
}

Could anyone help me out? Any ideas would help a lot.
note: I've already tried StackOverflow and I really think this is a really good question since after looking around in Google I haven't found anything to help me out, and asking in a closed group would mean that others that someday have the same issues with that won't be able to find anything related to it.
note of a note: The Jest folks told me to talk to you guys.

@Fazendaaa thanks for reporting the issue. I guess you know that, but just to be sure: console.log are swallowed by jest. If they are within a it(...) ot test(...) block, then they should be printed, else I believe jest aren't outputing anything.
Please confirm this is not the case (that you console.log are inside a test(...) block), and if it is, post a link to a minimal repo so we can reproduce the issue and hopefully fix it.

Oh wait, on SO someone answered with the correct answer. Arrow functions are anonymous, so no name.
try this:
const foo = () => 'bar';
console.log(foo.name);
function bar() { return 'foo' };
console.log(bar.name);

@huafu Right now I'm trying a new approach of generating the test functions given.json files that describe the function to be tested. It works passing the function itself and its name as string, but when I tried to remove the string with the function name and use the .name property of the function I ran into this issue.
The problem itself is in line 25, here: https://github.com/Fazendaaa/AnilistBot/blob/master/ci/readMocks.ts, called in line 56 here https://github.com/Fazendaaa/AnilistBot/blob/master/ci/doTesting.ts and this is my first test https://github.com/Fazendaaa/AnilistBot/blob/master/ci/tests/utils/parse.test.ts

Ok so I think it's because transpilation is removing the name. Look at how your source is transpiled to javascript in [here](https://www.typescriptlang.org/play/#src=export const sanitize %3D ({ message }%3A { message%3A string })%3A string %3D> message.replace(%2F(%3F%3A%3D\(|%3A0|%3Ao|%3A o|%3A 0)%2F%2C '%3A o')%3B%0D%0A) - the function becomes anonymous.

So yeah, I'm closing this as it is not ts-jest related.
@Fazendaaa I can't think of any workaround right now, sorry

@Fazendaaa find more info there https://github.com/Microsoft/TypeScript/issues/6433


Remove prepended "_" from public member of VIO

For consistency of naming convention. _cont of VIO is public member, this name should not begin with "_".

Member Variables
Prepend '_' to the beginning of the private or protected member variable to distinguish it from other variable

https://cwiki.apache.org/confluence/display/TS/Coding+Style#CodingStyle-MemberVariables
This has only name changes.

[approve ci autest]


install: Use partx to discover loopdev partitions

When running bootc install to-disk --via-loopback...  under libkrun, BLKRRPART appears to have no effect. Switching to partx solves it.

When running bootc install to-disk --via-loopback... under libkrun,

Hmm.  I'm not opposed to this change but I feel like we probably want to do at least a little bit of root cause analysis...where is the loopback file mounted?
When you say "under libkrun"...is that like a container-as-VM environment, i.e. is systemd and especially udev running or not?  It must be.  Or wait, could this be related to the custom libkrun kernel?  Any theories at all for why this might fail would be appreciated.
On the tangentially related positive side; dropping this ioctl would be a step towards letting us migrate off the nix crate and fully use rustix only, which would be nice.
We're probably going to continue to fork external binaries for partitioning for the forseeable future, and depending on util-linux-core for partx is totally fine by me.

Also, the direct equivalent of the ioctl here is blockdev --rereadpt - partx seems to be doing more.  I am curious if forking blockdev --rereadpt works?

I'm running a bootc container under krun. The entrypoint/PID 1 is /bin/sh running a script that forks bootc.
blockdev --rereadpt also has no effect.
partx uses its own logic to detect partitions, then adds them to the kernel table using ioctl(BLKPG).
I'm assuming this boils down to libkrunfw's kernel config, although it's unclear to me what the relevant options would be. I can dig deeper if needed.
Assuming partx's logic is as good as the kernel's, this patch should have the effect of making bootc compatible with more kernels.

Hmm it might be this https://github.com/containers/libkrunfw/blob/f9bf3af4fc04da8e59c0b09483d0f0c2fdee106a/config-libkrunfw_x86_64#L987 - that option looks like it's very very legacy.

I tried setting CONFIG_UEVENT_HELPER=n and unsetting CONFIG_UEVENT_HELPER_PATH, but I still get:
ERROR Installing to disk: Creating rootfs: Failed to find children after partitioning

@cgwalters would you prefer that whatever kernel config issue is solved, or that bootc is able to tolerate this sort of issue?

I'm running a bootc container under krun. The entrypoint/PID 1 is /bin/sh running a script that forks bootc.

Isn't this the real problem?  bootc is basically expecting systemd to be running as pid 1 because it's udev that will handle creating devices as triggered by the kernel normally (with devtmpfs as a baseline fallback, but I think that's not being covered for the loopback devices).
I am really uncertain about the value of trying to support non-systemd cases at install time.  What use case is there for that given that the target environment will have systemd anyways?

I understand. I haven't measured it, but my intention was to run as few things as possible under krun to avoid additional delays.
I can fix things on my end, so I'm closing the MR.

Don't get me wrong I'm open to negotiation here; if there's enough benefit to supporting non-systemd at install time then we can do it probably, but there really is the flip side where the install code path is already complex and fiddly enough...
BTW have you thought about the architecture we ended up at with https://github.com/containers/podman-bootc-cli where basically the install process is:

run the container itself in privileged mode inside a podman-machine VM (i.e. systemd in VM)
The install target is a file on the host mounted via virtiofs/9p

I think we could mimic this in the crunvm flow right?  (There's...also a whole lot going on with possibly trying to align podman-bootc to use krun, but also podman-machine...)

Don't get me wrong I'm open to negotiation here; if there's enough benefit to supporting non-systemd at install time then we can do it probably, but there really is the flip side where the install code path is already complex and fiddly enough...

crun-vm being the sole use case and it being able to work around it, I agree that it doesn't make sense to complicate bootc further right now.

BTW have you thought about the architecture we ended up at with https://github.com/containers/podman-bootc-cli where basically the install process is:

run the container itself in privileged mode inside a podman-machine VM (i.e. systemd in VM)

crun-vm does this but with libkrun instead of podman-machine, meaning we can fairly easily extend its bootc container support to Docker/Kubernetes in the future. Also we can simply boot a VM to run bootc-install on demand, since that is very fast.

The install target is a file on the host mounted via virtiofs/9p

That's how it works currently: we launch the bootable container using krun to build the VM image into a dir shared with the host, krun terminates, and then we boot the final VM from the generated image using libvirt+qemu.


Fix bug with parent_id assignment when autoloading

Autoloading based on the large scale surveygizmo response subobjects requires constant vigilance to make sure that parent parameters (and in the case of questions, parent_question_id) are passed along to children.
@jarthod

Thanks ;)

oh i was waiting for your +1 but figured you were on vacation or something;
given that it's a bug fix i just went ahead and merged.
On Wed, Jan 6, 2016 at 8:29 AM, Adrien Jarthon<EMAIL_ADDRESS>wrote:

Thanks ;)
—
Reply to this email directly or view it on GitHub
https://github.com/jarthod/survey-gizmo-ruby/pull/56#issuecomment-169322758
.

You did good, I already checked actually but forgot to comment it seems xD

i don't see myself changing anything about the gem anytime soon; given that this is a bug fix maybe it's worth releasing 5.0.3 if you have a chance (but no rush/pressure/etc)

Sure, just released 5.0.3


Reset the receivedStop flag after the thread is stopped, so that the catchup happens correctly.

Current coverage is 63.94% (diff: 100%)

No coverage report found for master at f7f91c2.

Powered by Codecov. Last update f7f91c2...4c8e27e


GC Fixes for Upstream Update

Need to implement a simple version of Frozen Segments
Adding "FEATURE_UNITY_NULLGC_WRITEBARRIER_PATCH"
to workaround write barrier problems with our GC. We need to
remove FEATURE_UNITY_NULLGC_WRITEBARRIER_PATCH
completely  when we move back to the default GC.

What I think is going on with the tests...

Windows x86 is broken upstream
OSX amd64 May be related to my Write barrier patch, will try something else
OSX arm64 (not run on the server) Failing, probably due to WB code that needs attention for arm


Add create invoice description

fixes: https://github.com/stripe/stripe-firebase-extensions/issues/210

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 3 committers have signed the CLA.:white_check_mark: dackers86:x: jhuleatt:x: Alex PattersonAlex Patterson seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Menu Arrows

Can someone help me i want to remove the arrows on the left top of the menu

ImGuiWindowFlags_NoCollapse
put this in imgui begin after &window flags

Thx so much

//close issue?


Travis CI

@jwhonce @jberkus @rhatdan
skopeo has tests that run on Travis, could you please enable Travis for this repository please?

I just turned it on.

@eparis thx


Fix type import ordering

it looks like #153 introduced a bug whereby import type ... imports would no longer be sorted with their matching group even if a type-specific group was not present. (see #329 for more details). this pr changes the matching logic such that:

non-type imports go in the first matching group if there is one
type imports go in the first matching type-specific group if there is one, or the first matching non-type-specific group if there is one
otherwise the behaviour remains unchanged, they go in the THIRD_PARTY_TYPES_SPECIAL_WORD or THIRD_PARTY_MODULES_SPECIAL_WORD groups depending on the node type and whether the THIRD_PARTY_TYPES_SPECIAL_WORD exists in the config.

as this behaviour is starting to feel a little complex i've added a comment in the code - i see there's not a ton of comments so happy to take it out if it's against house style. i also don't love the code so refactoring suggestions welcomed.
this fixes #329  - i've tested it on my codebase and the incorrect ordering changes introduced by 5.0.0 were reversed.

Sure thing, have done! Thanks :-)

hmm not sure why it's failing yarn --immutable with a 404 - works locally. maybe worth rerunning?


Analytics blog post

Background:
Blog post by Jon Jenson on how Californians trust us with their digital privacy through a custom analytics service to keep them safe built by ODI engineering.
Content for review:
https://docs.google.com/document/d/1gTOkzdED0WFb8QhnIVQIytMe-8L_ANX1AU_tDR3jvuo/edit
Leadership review and approve by:
June 23, 2023
Proposed publish date:
June 29, 2023

@m-sullivan7 can you take a look at the content and clean up? This is a blog post that has been sitting.

It's now on my list. Who's the original writer in case I have questions?

It's on my list now! (Deleted original comment because I see Jon is the original author in the top comment. That's why you should read everything!)

@YeseniaGtz I've finished my content design review. I edited the article down to 6th grade reading level in a few places. I also asked a few questions that need a technical person to answer.

Thank you @m-sullivan7 ! I have asked @zakiya to review the edits and questions. This should be completed early next week sometime. Please use this thread to track progress. Thank you both! :)

I answered the technical question and weighed in on one other edit. I'm okay with accepting Michael's edits if everyone else is. We should have the engineers review again after that.

Changes made in response to @zakiya's replies. I'm ready for my edits to be accepted. @YeseniaGtz want me to do that?

Getting back to this, sorry for the delay. @m-sullivan7 yes please accept the edits. thank you

Edits accepted! Ready for the next step. 🙂

@m-sullivan7 Leadership review completed. See comments from Jeffery. OK to publish after review is complete. What is the process for publishing?
https://docs.google.com/document/d/1gTOkzdED0WFb8QhnIVQIytMe-8L_ANX1AU_tDR3jvuo/edit#heading=h.wab56eu5o32s

Fantastic! Here's the process:

[ ] I coordinate with Hayley on when we publish it.

[ ] I ask a developer to create an ODI Tech Lab handle so it has the right author when we publish.

[ ] We decide if we want images in the post. Kimberly handles theses. Possibilities:

Screenshots
Header image that can be used for social sharing.

[ ] I load everything into WordPress with the regular admin tasks (alt text, metadata tasks).

[ ] I publish when ready.

@m-sullivan7 Any update on this?

Last I heard, we were trying to get sign off from CDPH. The post was ready to go, but they had concerns about what we were sharing publicly.

Couple quick notes.

Jim recently modified this system. So it may be worthwhile to check things over with him. There's at least one detail in there that's no longer accurate. ("We periodically replace each daily session hash with another random identifier.")

We've been trying to get this thing approved since 2022. My feelings won't be hurt if we decide to cut our losses and throw this away.


chore(roxctl): password and token-file args

Description

Improving handling of the password and token-file CLI parameters: give preference to the arguments when environment variables are set.
Previously roxctl would complain:
me@work$ ROX_API_TOKEN_FILE=tokenfile roxctl central whoami -p password
ERROR:	determining auth method: cannot use basic and token-based authentication at the same time

User-facing documentation

[x] CHANGELOG is updated OR update is not needed
[x] documentation PR is created and is linked above OR is not needed

Testing and quality

[x] the change is production ready: the change is GA or otherwise the functionality is gated by a feature flag
[x] CI results are inspected

Automated testing

[ ] added unit tests
[x] added e2e tests
[ ] added regression tests
[ ] added compatibility tests
[ ] modified existing tests

How I validated my change

me@work$ roxctl central cert --password abc --token-file xyz
ERROR:	if any flags in the group [password token-file] are set none of the others can be; [password token-file] were all set

me@work$ ROX_ADMIN_PASSWORD=wrong roxctl central whoami --password good
UserID:
	admin
...
me@work$ ROX_ADMIN_PASSWORD=wrong roxctl central whoami --token-file tmp/token
UserID:
	auth-token:485e1468-df27-4a92-b480-c18b8ecfe8cb
...
me@work$ ROX_API_TOKEN_FILE=wrong roxctl central whoami --password good
UserID:
	admin
...
me@work$ ROX_ADMIN_PASSWORD=wrong ROX_API_TOKEN_FILE=wrong roxctl central whoami
ERROR:	determining auth method: cannot use basic and token-based authentication at the same time

me@work$ ROX_ADMIN_PASSWORD=wrong ROX_API_TOKEN_FILE=wrong roxctl central whoami --password good
UserID:
	admin
...

/retest


chore: remove .gitignored files

Similar to the PR for primer-ios-sdk, this adds .build to .gitignore, and removes previously tracked files in that directory.

Updated to also remove pods files..


Update Visualizers Documentation with additional steps in case they are intended for .NET 5.0 scenarios

BinaryFormatter is no longer supported for .NET 5 and will throw when used in ASP.NET . Since part of the DataSet Visualizer runs on the debuggee and relies on BinaryFormatter to pass data to the UI, it no longer works. So, we modified both sides to check beforehand if the BinaryFormatter is still supported and if not, fallback to use the System.Text.Json.JsonSerializer to continue to support it.
The reason for which it is no longer supported is because of security vulnerabilities (more information can be found in the BinaryFormatter security guide and regarding its usage in ASP.NET , here).
In order to fix this issue, changes were made that require some work on user's part when they create their own visualizers. The updates to this documentation have the required information so that they know what steps are necessary so that their visualizers still work on ASP.NET 5.0 onward.

@mpeyrotc : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@hharshada @WardenGnaw could you also help review 😃?

Does PR Merger not ping this message anymore?

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We have closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions


only run upgrade tests on 2.2 and later

Pursuant to some discussion on IRC, these tests need to be run over a few upgrade paths (see CASSANDRA-10269. Until then, they are hard-coded to upgrade from 2.1, so let's only run them on 2.2 and greater for now.

+1

Thanks!


Eliminate non-inclusive language

Hello, we have a project to eliminate non-inclusive language from Linux-system-roles.
Running a utility woke (now it's supported in tox. please install the latest tox-lsr and run tox -e woke), two non-inclusive words are reported - sanity and master.
The word sanity is easily eliminated, but master is not since it's tightly coupled with the SQL context, e.g., as master key.
There are two ways to skip the check - adding wokeignore:rule=master to each master appearing in the source code, or skipping them as warning by applying https://github.com/get-woke/woke/pull/252. Which way should we go or could there be some other ideas to workaround master?

There are too many uses of master in the code. Running woke with --count-only-error-for-failure results in a success, so it's only the word master that matters. And the role cannot fix master in the SQL Server context. The role can only fix the use of master in unrelated context, e.g. rename the GitHub branch master > main.

Thank you for your comments, @spetrosi! Your proposal makes sense.
First, may I ask you to rename the master branch to the main branch as described in https://issues.redhat.com/browse/RHELPLAN-134435 by @richm.
Then, we can reduce the number of the word master before applying the --count-only-error-for-failure change. Thanks!

Thank you for merging https://github.com/linux-system-roles/mssql/pull/158, @spetrosi.
Closing this issue.


Feature request: toggle whether to show hidden files with . globally.

Like https://github.com/sxyazi/yazi/issues/51#issuecomment-1691086346 said, the current behavior of . only works locally (directory-specific).
As a contrast, the behavior of zh can toggle whether to show hidden files globally as shown in a demostration.

Please vote on this or leave your comment

I feel that globally is the more common case. At least from my experience with file managers.
And I would vote for that too, I guess.
Of course this depends on the personal workflow, but adjusting my workflow if I just want a "peek" on the dotfiles in a specific folder and it is applied globally vs. the other way around, is much less of an effort.
If globally applied, this would be, if at all, only a problem for that user outside the initial folder and there it needs only one keystroke to hide the files again.
But if applied locally and the user wants/needs to work with dotfiles and has to go through several folders, the effort is much higher aka multible keystrokes.

Done by https://github.com/sxyazi/yazi/pull/89, take a try!
Now show_hidden is tab-specific, and newly created tabs inherit the previous tab's state, which I think is a reconciliation of convenience and flexibility.
https://github.com/sxyazi/yazi/assets/17523360/c592043b-a623-438c-844a-84430e5f7860

Altough I do not know what tab is, it is good enough for me presently. I confirm that it works.


kevm, Makefile, tests/interactive/*.out: default to BYZANTIUM schedule

VMTESTS run on DEFAULT schedule
output of interactive tests is updated

Addresses #174

Need to also make sure the proofs are updated correctly.


Possible bug in RDM computation?!?!?!

I might be mixing something simple up, but the Pearson correlations RDM I am doing by hand are not aligning with what I am getting from our code.
Consider: x = np.array([[1,2,3],[4,4,6],[2,4,2]])
This is an n x d vector where the two first vectors are  [1,2,3] and [4,4,6]. Which should have a correlation of 0.8666. I did that by hand and also checked online (https://www.statskingdom.com/correlation-calculator.html)
However running standardize from dist_util:276 I get:
tensor([[-1.0690, -1.4142, -0.3922],         [ 1.3363,  0.7071,  1.3728],         [-0.2673,  0.7071, -0.9806]])
Which is obviously incorrect, replacing the default dim 0 to 1 however I get:
tensor([[-1.2247,  0.0000,  1.2247],         [-0.7071, -0.7071,  1.4142],         [-0.7071,  1.4142, -0.7071]])
Which is right, looking at dist.py line 166 however we can see it is called with dim 0 and then is used with torch.corrcoef.
Ofcourse, we don't even need the standardize here since corrcoeff fixes that anyway. But I am worried that other places in the code call the method with distances that will not be standarizing automatically.
Anyway, since this really effected my results I am worried that a few projects might have been effected.  Could someone validate this ASAP? sorry for the trouble

Ok, I see that this was added recently as an implementation of what Kriegeskorte had. Dom already fixed this in dev, so I will close the issue.
Btw, this is not the default in rsatoolbox, and the 2008 paper seems a bit ambiguous, lets talk about this tomorrow


Command-line tool for starting a server?

Would it be possible to depend on gunicorn and support this:
sql-dashboard $DATABASE_URL

Maybe as a separate PyPI package, to avoid gunicorn as a core dependency.

This tool could include helpers for creating read-only roles with access to specific tables.

I'm not going to do this - this can be a feature for Datasette once I get PostgreSQL working there


[Fix #8843] Fix invalid Lint/AmbiguousRegexpLiteral autocorrect when the original node had internal parentheses

This previously used Util#add_parentheses to do correction, but this does not handle send nodes properly, so I changed it to just edit the node in place.
Fixes #8843.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

Thanks for the patch. However, this solution causes incompatibility auto-correction when using method chain.
I opened a PR #8847 that includes a solution to case of method chain's issue. It seems that we tried to resolve the issue at almost the same timing 😅

@koic great! I'll close this one 😄

@dvandersluis I'm sorry about it. Thank you for your activity!

@koic no worries! I’ll keep trying to find more to fix and hopefully we’ll avoid conflicts 😁


set global jl defaults

Is it hard to get stuff like #set jl(show: true) working as other Typst functions do?

That is not possible until Typst supports custom types. Set rules don't work for any user defined function currently.


Central App - Setup issues

Good evening,
I hope you are well.
I've got installed your package (great with Nova, thank you!) However, I seem to run into an issue with the Central App. All I see is the error message: "Tenant could not be identified on this domain - Did you forget to create a tenant for this domain?"
I'm running:
Laravel 6.x
Nova 2.6
Stancl/Tenancy 2.1
Ubuntu -> php 7.3
Laravel Valet (ubuntu version)
Within my config/tenancy.php file, I have my domain name entered into exempt_domains.
Any assistance will be very appreciated.
Many thanks,
Daniel.

Hi,
What URL are you visiting and how does your exempt_domains config look like?

Hey Stancl,
Thank you for your reply.
Urls:
subdomain.crm.fran <- works fine
crm.fran <- having troubles
tenancy.php
'exempt_domains' => [ // e.g. domains which host landing pages, sign up pages, etc
      'crm.fran',
  ],

Whole Tenancy.php file
<?php

declare(strict_types=1);

return [
    'storage_driver' => 'db',
    'storage_drivers' => [
        'db' => [
            'driver' => Stancl\Tenancy\StorageDrivers\Database\DatabaseStorageDriver::class,
            'data_column' => 'data',
            'custom_columns' => [
                // 'plan',
            ],
            'connection' => null,
            'table_names' => [
                'TenantModel' => 'tenants',
                'DomainModel' => 'domains',
            ],
        ],
        'redis' => [
            'driver' => Stancl\Tenancy\StorageDrivers\RedisStorageDriver::class,
            'connection' => 'tenancy',
        ],
    ],
    'tenant_route_namespace' => 'App\Http\Controllers',
    'exempt_domains' => [ // e.g. domains which host landing pages, sign up pages, etc
         'crm.fran',
    ],
    'database' => [
        'based_on' => null, // The connection that will be used as a base for the dynamically created tenant connection.
        'prefix' => 'tenant',
        'suffix' => '',
    ],
    'redis' => [
        'prefix_base' => 'tenant',
        'prefixed_connections' => [
            // 'default',
        ],
    ],
    'cache' => [
        'tag_base' => 'tenant',
    ],
    'filesystem' => [ // https://tenancy.samuelstancl.me/docs/v2/filesystem-tenancy/
        'suffix_base' => 'tenant',
        // Disks which should be suffixed with the suffix_base + tenant id.
        'disks' => [
            'local',
            'public',
            // 's3',
        ],
        'root_override' => [
            // Disks whose roots should be overriden after storage_path() is suffixed.
            'local' => '%storage_path%/app/',
            'public' => '%storage_path%/app/public/',
        ],
    ],
    'database_managers' => [
        // Tenant database managers handle the creation & deletion of tenant databases.
        'sqlite' => Stancl\Tenancy\TenantDatabaseManagers\SQLiteDatabaseManager::class,
        'mysql' => Stancl\Tenancy\TenantDatabaseManagers\MySQLDatabaseManager::class,
        'pgsql' => Stancl\Tenancy\TenantDatabaseManagers\PostgreSQLDatabaseManager::class,
    ],
    'database_manager_connections' => [
        // Connections used by TenantDatabaseManagers. This tells, for example, the
        // MySQLDatabaseManager to use the mysql connection to create databases.
        'sqlite' => 'sqlite',
        'mysql' => 'mysql',
        'pgsql' => 'pgsql',
    ],
    'bootstrappers' => [
        // Tenancy bootstrappers are executed when tenancy is initialized.
        // Their responsibility is making Laravel features tenant-aware.
        'database' => Stancl\Tenancy\TenancyBootstrappers\DatabaseTenancyBootstrapper::class,
        'cache' => Stancl\Tenancy\TenancyBootstrappers\CacheTenancyBootstrapper::class,
        'filesystem' => Stancl\Tenancy\TenancyBootstrappers\FilesystemTenancyBootstrapper::class,
        'queue' => Stancl\Tenancy\TenancyBootstrappers\QueueTenancyBootstrapper::class,
        // 'redis' => Stancl\Tenancy\TenancyBootstrappers\RedisTenancyBootstrapper::class, // Note: phpredis is needed
    ],
    'features' => [
        // Features are classes that provide additional functionality
        // not needed for tenancy to be bootstrapped. They are run
        // regardless of whether tenancy has been initialized.

        // Stancl\Tenancy\Features\TenantConfig::class,
        // Stancl\Tenancy\Features\TelescopeTags::class,
        // Stancl\Tenancy\Features\TenantRedirect::class,
    ],
    'storage_to_config_map' => [ // Used by the TenantConfig feature
        // 'paypal_api_key' => 'services.paypal.api_key',
    ],
    'home_url' => '/app',
    'queue_database_creation' => false,
    'migrate_after_creation' => false, // run migrations after creating a tenant
    'seed_after_migration' => false, // should the seeder run after automatic migration
    'seeder_parameters' => [
        '--class' => 'DatabaseSeeder', // root seeder class to run after automatic migrations, eg: 'DatabaseSeeder'
    ],
    'queue_database_deletion' => false,
    'delete_database_after_tenant_deletion' => false, // delete the tenant's database after deleting the tenant
    'unique_id_generator' => Stancl\Tenancy\UniqueIDGenerators\UUIDGenerator::class,
];

Good morning,
I'm sorry to pressure, is there any movement on this?
Many thanks,
Daniel

Can you try running composer config:clear? If that doesn't help, maybe the issue is specific to Valet.

did you mean artisan config:clear?

Right. Yeah, php artisan config:clear.

Hi Guys,
Sorry for the delay in posting.
Yes, i assumed it was artisan clear ;) - Sadly that did not work. I'm rebuilding my dev server at the moment so will try again when that's rebuilt.
Many thanks for your assistance!
Daniel.

Okay. I'm closing this for now. If you have any further questions, definitely reach out.

Im very new to this package. I have the same issue. Below is my tenancy.php
`<?php
declare(strict_types=1);
use Stancl\Tenancy\Database\Models\Domain;
use Stancl\Tenancy\Database\Models\Tenant;
return [
/**
 * The list of domains hosting your central app.
 *
 * Only relevant if you're using the domain or subdomain identification middleware.
 */
'central_domains' => [
    '<IP_ADDRESS>',
    'localhost',
    'eleganza.local',
],

'tenant_model' =>  \App\Tenant::class,
'id_generator' => Stancl\Tenancy\UUIDGenerator::class,
'domain_model' => Domain::class,
/**
 * Tenancy bootstrappers are executed when tenancy is initialized.
 * Their responsibility is making Laravel features tenant-aware.
 *
 * To configure their behavior, see the config keys below.
 */
'bootstrappers' => [
    Stancl\Tenancy\Bootstrappers\DatabaseTenancyBootstrapper::class,
    Stancl\Tenancy\Bootstrappers\CacheTenancyBootstrapper::class,
    Stancl\Tenancy\Bootstrappers\FilesystemTenancyBootstrapper::class,
    Stancl\Tenancy\Bootstrappers\QueueTenancyBootstrapper::class,
    // Stancl\Tenancy\Bootstrappers\RedisTenancyBootstrapper::class, // Note: phpredis is needed
],

/**
 * Database tenancy config. Used by DatabaseTenancyBootstrapper.
 */
'database' => [
    'central_connection' => env('DB_CONNECTION', 'central'),

    /**
     * Connection used as a "template" for the dynamically created tenant database connection.
     * Note: don't name your template connection tenant. That name is reserved by package.
     */
    'template_tenant_connection' => null,

    /**
     * Tenant database names are created like this:
     * prefix + tenant_id + suffix.
     */
    'prefix' => 'tenant',
    'suffix' => '',

    /**
     * TenantDatabaseManagers are classes that handle the creation & deletion of tenant databases.
     */
    'managers' => [
        'sqlite' => Stancl\Tenancy\TenantDatabaseManagers\SQLiteDatabaseManager::class,
        'mysql' => Stancl\Tenancy\TenantDatabaseManagers\MySQLDatabaseManager::class,
        'pgsql' => Stancl\Tenancy\TenantDatabaseManagers\PostgreSQLDatabaseManager::class,

    /**
     * Use this database manager for MySQL to have a DB user created for each tenant database.
     * You can customize the grants given to these users by changing the $grants property.
     */
        // 'mysql' => Stancl\Tenancy\TenantDatabaseManagers\PermissionControlledMySQLDatabaseManager::class,

    /**
     * Disable the pgsql manager above, and enable the one below if you
     * want to separate tenant DBs by schemas rather than databases.
     */
        // 'pgsql' => Stancl\Tenancy\TenantDatabaseManagers\PostgreSQLSchemaManager::class, // Separate by schema instead of database
    ],
],

/**
 * Cache tenancy config. Used by CacheTenancyBootstrapper.
 *
 * This works for all Cache facade calls, cache() helper
 * calls and direct calls to injected cache stores.
 *
 * Each key in cache will have a tag applied on it. This tag is used to
 * scope the cache both when writing to it and when reading from it.
 *
 * You can clear cache selectively by specifying the tag.
 */
'cache' => [
    'tag_base' => 'tenant', // This tag_base, followed by the tenant_id, will form a tag that will be applied on each cache call.
],

/**
 * Filesystem tenancy config. Used by FilesystemTenancyBootstrapper.
 * https://tenancyforlaravel.com/docs/v3/tenancy-bootstrappers/#filesystem-tenancy-boostrapper.
 */
'filesystem' => [
    /**
     * Each disk listed in the 'disks' array will be suffixed by the suffix_base, followed by the tenant_id.
     */
    'suffix_base' => 'tenant',
    'disks' => [
        'local',
        'public',
        // 's3',
    ],

    /**
     * Use this for local disks.
     *
     * See https://tenancyforlaravel.com/docs/v3/tenancy-bootstrappers/#filesystem-tenancy-boostrapper
     */
    'root_override' => [
        // Disks whose roots should be overridden after storage_path() is suffixed.
        'local' => '%storage_path%/app/',
        'public' => '%storage_path%/app/public/',
    ],

    /**
     * Should storage_path() be suffixed.
     *
     * Note: Disabling this will likely break local disk tenancy. Only disable this if you're using an external file storage service like S3.
     *
     * For the vast majority of applications, this feature should be enabled. But in some
     * edge cases, it can cause issues (like using Passport with Vapor - see #196), so
     * you may want to disable this if you are experiencing these edge case issues.
     */
    'suffix_storage_path' => true,

    /**
     * By default, asset() calls are made multi-tenant too. You can use global_asset() and mix()
     * for global, non-tenant-specific assets. However, you might have some issues when using
     * packages that use asset() calls inside the tenant app. To avoid such issues, you can
     * disable asset() helper tenancy and explicitly use tenant_asset() calls in places
     * where you want to use tenant-specific assets (product images, avatars, etc).
     */
    'asset_helper_tenancy' => true,
],

/**
 * Redis tenancy config. Used by RedisTenancyBootstrapper.
 *
 * Note: You need phpredis to use Redis tenancy.
 *
 * Note: You don't need to use this if you're using Redis only for cache.
 * Redis tenancy is only relevant if you're making direct Redis calls,
 * either using the Redis facade or by injecting it as a dependency.
 */
'redis' => [
    'prefix_base' => 'tenant', // Each key in Redis will be prepended by this prefix_base, followed by the tenant id.
    'prefixed_connections' => [ // Redis connections whose keys are prefixed, to separate one tenant's keys from another.
        // 'default',
    ],
],

'exempt_domains' => [
    parse_url(env('CENTRAL_DOMAIN', 'http://icynta.in'), PHP_URL_HOST),
],

/**
 * Features are classes that provide additional functionality
 * not needed for tenancy to be bootstrapped. They are run
 * regardless of whether tenancy has been initialized.
 *
 * See the documentation page for each class to
 * understand which ones you want to enable.
 */
'features' => [
    // Stancl\Tenancy\Features\UserImpersonation::class,
    // Stancl\Tenancy\Features\TelescopeTags::class,
    // Stancl\Tenancy\Features\UniversalRoutes::class,
    // Stancl\Tenancy\Features\TenantConfig::class, // https://tenancyforlaravel.com/docs/v3/features/tenant-config
    // Stancl\Tenancy\Features\CrossDomainRedirect::class, // https://tenancyforlaravel.com/docs/v3/features/cross-domain-redirect
    // Stancl\Tenancy\Features\ViteBundler::class,
],

/**
 * Should tenancy routes be registered.
 *
 * Tenancy routes include tenant asset routes. By default, this route is
 * enabled. But it may be useful to disable them if you use external
 * storage (e.g. S3 / Dropbox) or have a custom asset controller.
 */
'routes' => true,

/**
 * Parameters used by the tenants:migrate command.
 */
'migration_parameters' => [
    '--force' => true, // This needs to be true to run migrations in production.
    '--path' => [database_path('migrations/tenant')],
    '--realpath' => true,
],

/**
 * Parameters used by the tenants:seed command.
 */
'seeder_parameters' => [
    '--class' => 'DatabaseSeeder', // root seeder class
    // '--force' => true,
],

];
`

This thread is from v2. On v3 just follow the quickstart guide.


Wrong link in activation mail

In your activation mail you link to:
 $url = url("/register/activate/{$notifiable->activation_token}");
But in your routes you define:
Route::get('/registration/activate/{activationToken}', Activation::class . '@show');
I think the url in the mail should also read registration instead of register.

Haha, thanks for reporting this! Wow, you're quick, I haven't even officially included it in my own project yet. (Was going to start that next week.) Woot. You get a gold star, sir.
Will address this early next week.

Fixed the link and added some instructions on customizing the notifications. Please try with version 0.1.2 and let me know how it goes. :)


feat(species): add species endpoint

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


TypeDoc 0.27 Beta

TypeDoc 0.27 is now in beta! :tada:
Please try it out and report any issues in new issues:
npm install --save-dev typedoc@beta

The full release will be made on 2024-11-21 (TS 5.7 release date, may be pushed if TS pushes)
This release mainly focuses on improved flexibility for type conversion and several improvements to the default theme, but also makes some changes to output.
Conversion Flexibility
TypeDoc uses the compiler to retrieve the types of documented members, and converts them into a simplified structure for rendering. Historically, not much flexibility has been exposed to control this behavior. v0.24 added support for @interface to tell TypeDoc to treat a type alias as if it was an interface, and @namespace to convert variables as namespaces. v0.27 extends this support with some additional tags:

@expand - tells TypeDoc to also render details about the properties of this type when rendering references to this type.
@inline - tells TypeDoc to replace references to this type with a copy of the referenced type.
@useDeclaredType - tells TypeDoc to use TypeScript's getDeclaredType method to get types for conversion. Using this on a mapped type will cause the evaluated type to be rendered. Note: This can sometimes produce worse documentation, the most common error case is that it will render as a self-reference.

Default Theme Changes
This release includes quite a few quality of live improvements to the default theme:
Reworked Modules Page
Modules/namespace pages have been re-worked to be more generally useful. The @summary tag can now be used to define a "short summary" for a reflection, which will be rendered on the modules page, or the useFirstParagraphOfCommentAsSummary option can be set to automatically use the first paragraph of a reflection's comment as the summary. Re-exports (like CommentStyle below) will be rendered with an arrow pointing to the canonical export.

Expanded References
If @expand is used on a type alias or interface, references to it will be expanded. In the screenshot below the @expand tag was placed on InlineTagDisplayPart and RelativeLinkDisplayPart. This screenshot also shows how TypeDoc can render comments for each branch of a union at the root level of a type alias.
Code
/**
 * Represents a parsed piece of a comment.
 * @category Comments
 * @see {@link JSONOutput.CommentDisplayPart}
 */
export type CommentDisplayPart =
    /**
     * Represents a plain text portion of the comment, may contain markdown
     */
    | { kind: "text"; text: string }
    /**
     * Represents a code block separated out form the plain text entry so
     * that TypeDoc knows to skip it when parsing relative links and inline tags.
     **/
    | { kind: "code"; text: string }
    | InlineTagDisplayPart
    | RelativeLinkDisplayPart;

/**
 * Represents an inline tag like `{@link Foo}`
 *
 * The `@link`, `@linkcode`, and `@linkplain` tags may have a `target`
 * property set indicating which reflection/url they link to. They may also
 * have a `tsLinkText` property which includes the part of the `text` which
 * TypeScript thinks should be displayed as the link text.
 * @category Comments
 * @expand
 */
export interface InlineTagDisplayPart {
    kind: "inline-tag";
    tag: `@${string}`;
    text: string;
    target?: Reflection | string | ReflectionSymbolId;
    tsLinkText?: string;
}

Smarter Code Rendering
When TypeDoc renders types, it used to apply some very basic rules about when to wrap a type to multiple lines, namely deciding to wrap object types and top level unions on every line, and placing all other types on the same line. This mostly worked, but could also cause very messy rendering. TypeDoc now uses an algorithm similar to prettier, which can be controlled with the typePrintWidth option to determine when types should be wrapped.
Along with this change, TypeDoc will now be smarter when deciding whether or not to recurse into types to render additional details about them. This is most obvious when viewing documentation for functions which accept or return functions or objects with functions. TypeDoc will still render the full details if it detects that there is additional details provided via documentation comments (either directly or via @expand) within the type.

Old New

Note: This is only about half of the rendered signature

Alerts
GitHub supports alerts to call out important information. TypeDoc now supports the same format in comments and markdown documents and will render them in a similar way.

Outputs
TypeDoc supports both HTML and JSON outputs, but if a plugin (e.g. typedoc-plugin-markdown) wanted to add an additional output type, there wasn't an obvious place to hook into the API to expose it to users. TypeDoc now supports the idea of a generic output for a project, which also makes it possible to render TypeDoc's output multiple times with different settings.
The options key is optional, and may include any TypeDoc option, though users should be aware that options which are used during conversion will be effectively ignored if set under outputs.
// typedoc.json
{
    "outputs": [
        {
            "name": "html",
            "path": "../docs"
        },
        {
            "name": "html",
            "path": "../docs-grouped-nav",
            "options": {
                "navigation": true
            }
        },
        {
            "name": "json",
            "path": "../docs/docs.json"
        }
    ],
}

Change Log
Breaking Changes

Relaxed requirements for file names and generated url fragments. This may
result in a different file name structure, #2714.
Anchors to document headings and reflections within a HTML generated pages
have changed. They can be partially restored to the previous format by
setting --sluggerConfiguration.lowercase false. This change was made to
more closely match the default behavior of GitHub's markdown rendering and
VSCode's autocomplete when creating a relative link to an external markdown
file.
Removed the hideParameterTypesInTitle option, this was originally added as
a workaround for many signatures overflowing the available horizontal space
in rendered pages. TypeDoc now has logic to wrap types/signatures smartly,
so this option is no longer necessary.
Changed the default kindSortOrder to put references last.
Changed the default sort order to use alphabetical-ignoring-documents
instead of alphabetical.
Changed default of suppressCommentWarningsInDeclarationFiles to true
API: Constructor signatures now use the parent class name as their name
(e.g. X, not new X)
API: @group, @category, @groupDescription and @categoryDescription
will no longer be removed from the reflections they are present on. They are
skipped during rendering with the notRenderedTags option.

Features

TypeDoc will now discover entry points from package.json exports if they
are not provided manually, #1937.
Relative links to markdown files may now include #anchor links to
reference a heading within them.
Improved support for @param comments with nested object types, #2555.
Improved support for @param comments which reference a type
alias/interface. Important properties on the referenced type can now be
highlighted with @param options.foo, which will result in the additional
note being included under the documentation for that parameter, #2147. Note:
This feature is limited to references. It is not supported on other types of
types.
Added a new outputs option which is an array of outputs. This can be used
to render the documentation multiple times with different rendering options
or output types, #2597.
Added support for rendering alerts (or callouts) in markdown.
Add support for an @expand tag which can be placed on type aliases and
interfaces. When a type with @expand is referenced and TypeDoc has a place
to include additional details about the type, the properties of the type
will be included in the page where @expand is found. Note that use of this
tag can significantly increase the size of your generated documentation if
it is applied to commonly used types as it will result in inlining the
comments for those types everywhere they are referenced, #2303.
Add support for an @inline tag which can be placed on type aliases and
interfaces. When a type with @inline is referenced, TypeDoc will resolve
the referenced type and convert the type as if it was included directly
within the referencing type. Note that use of this tag can significantly
increase the size of your generated documentation if it is applied to
commonly used types as it will result in inlining the comments for those
types everywhere they are referenced, #2303.
Introduced a new @useDeclaredType tag for type aliases which can sometimes
improve their documentation, #2654..
Added a new @mergeModuleWith tag which can be used to tell TypeDoc to
place a module/namespace's children under a different module/namespace and
remove the real parent, #2281.
Add notRenderedTags option. This option is similar to the excludeTags
option, but while excludeTags will result in the tag being completely
removed from the documentation, notRenderedTags only prevents it from
being included when rendering.
Added groupReferencesByType option.
Added navigation.excludeReferences option
Added useFirstParagraphOfCommentAsSummary option to configure how TypeDoc
handles comments for module members without the @summary tag.
Introduced favicon option to specify a .ico or .svg favicon to reference.
Sections within the page and in the "On This Page" navigation are now tied
together and will expand/collapse together, #2335.
API: Introduced a new app.outputs object for defining new output strategies.

Bug Fixes

TypeDoc will now use the first signature's comment for later signatures in
overloads if present, #2718.
Fixed handling of @enum if the type was declared before the variable, #2719.
Fixed empty top level modules page in packages mode, #2753.
TypeDoc can now link to type alias properties, #2524.
Fixed an issue where properties were not properly marked optional in some
cases. This primarily affected destructured parameters.
Added yaml to the highlight languages supported by default.
TypeDoc now recognizes txt as an alias of text to indicate a code block
should not be highlighted.
Items which are hidden with @ignore or @hidden but still referenced by
other types will no longer produce warnings about not being exported.
If a project only has one module within it, TypeDoc will now consider that
module when resolving @link tags.
The arrows to indicate whether or not a section is open now work when
JavaScript is disabled.
Group/category search boosts are now applied when writing the search index
rather than when converting. This prevents issues where boosts used by just
one package were incorrectly reported as unused when running with
entryPointStrategy set to packages.

I was hoping to get this out with the TS release, but want to give a few days to update plugins, as the past couple weeks have kept me entirely too busy, so I didn't get the rest of 0.27 finished until just a few minutes ago... sorry about that! The downside of hobby projects..
Planning on Monday/Tuesday for this release now.
0.27.0-beta.1

Expandable class hierarchy, #2744
Fix infinite loop when handling @mergeModuleWith if targeting a non-toplevel module, #2776
Fix inconsistency with handling of global symbols, #2774
Tag name instead of tag target name is added to class names, #2772
Separated output shortcut --html for HTML output, --out may now be reused by plugins (e.g. typedoc-plugin-markdown) for the default output, #2769
Drop support for TS < 5.0 for consistency with definitely typed support

Nice work! I tried the beta version and everything seemed to be working smoothly.
I suppose you're aware of it, but since I didn't see it mentioned explicitly: Typedoc is now distributed as ESM, not CommonJS anymore, resulting in some plugins such as typedoc-plugin-merge-modules that still use CommonJS not working anymore. They just need to be converted to ESM as well and everything works again.

Thanks for that note! I'm not sure how I missed that in the list of breaking changes, it absolutely should be called out.

Didn't think there was going to be another beta release before the full one, but there were a couple issues which got in the way when updating a plugin.
v0.27.0-beta.2

declare module "foo" will now create a module, #2778
Fix conversion of import types with qualifiers, #2779
Removed dependency on resolve-import by implementing it myself, 28 dependencies aren't worth 140 lines of code
Downgrade Minimatch to restore support for Node 18
Create and use a @gerrit0/mini-shiki package instead of directly using shiki to remove 35 unused dependencies from install

0.27 release is out!

Hey @Gerrit0 , There's some junk/syntax error on the plugins page

Fixed with 68683986ad3264f3822e41ed426bcc5d2d433a1c, thanks!


Add ability to dynamically change log appenders

Add ability to dynamically add/(or enable/disable) log appenders:

[ ] AWS cloudwatch appender
[ ] Splunk appender

Change current loggers

[ ] Make message log configurable (json/xml/none/both?)
[ ] Make ibis xml log optional

Add ability to create loggers with a specific log level without changing the log4j4ibis.xml
Perhaps a loggers.properties with a key (logger) value (level) file.

Not runtime, so may be configured with properties. Part of Epic #3194

See #6142

We've decided that it's up to the end-user to add the required log4j2-appender jar to the classpath, and provide it's own corresponding log4j2.ext configuration file.
This can be done by setting the property log4j.configurationFile which defaults to log4j2.properties,log4j4ibis.xml (comma separated).
When using a file outside of the war archive (almost always?) it has to be an absolute path (ideally prefixed with file:). It is therefor not possible to overwrite our own log4j2.properties,log4j4ibis.xml files.


Add redirect field if status=deprecated

What problem are we trying to solve?
If a source has been deprecated because a new one is available, users need to be able to identify the replacement source.
How do we know when this is done?

The schema includes a redirect field that is conditionally required if status=deprecated`

Suggestion:
redirect:
 - 1234 # comments helpful here; i.e. feed split into two separate feeds
 - 1235 # make a list in case there are multiple
last_updated: <auto-filled last updated date>  # sometimes recently deprecated feeds still have "ok" data in them
deprecated: true

Updated issue to specifically focus on adding redirect information, since #171 added a deprecation status.


Analytics: Read the Docs global

Currently, we are injecting Google Analytics ^1 via Javascript. However, we talked about stop depending on Google Analytics and migrate to Plausible. I'm not sure if Plausible is OK to handle all the traffic we have in all the subdomains *.readthedocs.io

This code lives at https://github.com/readthedocs/readthedocs-client/blob/8d1855c868ae83f51cb9464f304f6bdd40b15cc5/src/analytics.js#L32-L72
I'm leaving it for now because it does not affect the UX and we can consider removing/changing at anytime without the needing of notifying the user.

We have a Celery task that talks to GA as well at https://github.com/readthedocs/readthedocs.org/blob/50d265eb2be652bdc055394f7af0f6777c98a072/readthedocs/analytics/tasks.py#L46

We should also update our documentation to remove all the mentions to Google Analytics.


Add a partial variant of getEnv

Fixes #443

Thanks! Good choice of name.

A wise man suggested it 😄

I had totally forgotten that!


bowtie2 empty output

Hello, I'm using this command to run bowtie2
cannoli-submit \
    spark args...
    -- \
    bowtie2 \
    -executable /home/hadoop/conda/bin/bowtie2 \
    -index file:///home/hadoop/efs/bowtie2/GCA_000001405.15_GRCh38_no_alt_analysis_set.fna.bowtie_index \
    -bowtie2_args "q -t --phred33 --sensitive --end-to-end -p 3" \
    s3://my-s3-bucket/queries/D12.ifq \
    $HDFS_ADDR/user/hadoop/results/bowtie2/D12.sam

it took about 9 min to finish
[hadoop@ip-172-31-37-149 ~]$ hadoop fs -ls results/bowtie2/D12.sam
Found 46 items
-rw-r--r--   1 hadoop hadoop          0 2020-02-11 01:49 results/bowtie2/D12.sam/_SUCCESS
-rw-r--r--   1 hadoop hadoop         23 2020-02-11 01:44 results/bowtie2/D12.sam/part-r-00000.sam
-rw-r--r--   1 hadoop hadoop         23 2020-02-11 01:44 results/bowtie2/D12.sam/part-r-00001.sam
-rw-r--r--   1 hadoop hadoop         23 2020-02-11 01:44 results/bowtie2/D12.sam/part-r-00002.sam
-rw-r--r--   1 hadoop hadoop         23 2020-02-11 01:44 results/bowtie2/D12.sam/part-r-00003.sam
-rw-r--r--   1 hadoop hadoop         23 2020-02-11 01:44 results/bowtie2/D12.sam/part-r-00004.sam
-rw-r--r--   1 hadoop hadoop         23 2020-02-11 01:44 results/bowtie2/D12.sam/part-r-00005.sam
-rw-r--r--   1 hadoop hadoop         23 2020-02-11 01:44 results/bowtie2/D12.sam/part-r-00006.sam
-rw-r--r--   1 hadoop hadoop         23 2020-02-11 01:45 results/bowtie2/D12.sam/part-r-00007.sam
...

but each file contains only one line as @HD     VN:1.6  SO:unsorted
use bowtie2 without cannoli can get the normal result which is about 3.5G
here is the executor stderr log
20/02/11 01:47:49 INFO FileOutputCommitter: File Output Committer Algorithm version is 1
20/02/11 01:47:49 INFO FileOutputCommitter: FileOutputCommitter skip cleanup _temporary folders under output directory:false, ignore cleanup failures: false
20/02/11 01:47:49 INFO DirectFileOutputCommitter: Direct Write: DISABLED
20/02/11 01:47:49 INFO FileOutputCommitter: File Output Committer Algorithm version is 1
20/02/11 01:47:49 INFO FileOutputCommitter: FileOutputCommitter skip cleanup _temporary folders under output directory:false, ignore cleanup failures: false
20/02/11 01:47:49 INFO DirectFileOutputCommitter: Direct Write: DISABLED
20/02/11 01:47:49 INFO FileOutputCommitter: Saved output of task 'attempt_20200211014009_0004_r_000034_0' to hdfs://ip-172-31-37-149.ap-northeast-1.compute.internal:8020/user/hadoop/results/bowtie2/D12.sam/_temporary/0/task_20200211014009_0004_r_000034
20/02/11 01:47:49 INFO SparkHadoopMapRedUtil: attempt_20200211014009_0004_r_000034_0: Committed
20/02/11 01:47:49 INFO Executor: Finished task 34.0 in stage 0.0 (TID 34). 807 bytes result sent to driver
20/02/11 01:47:49 INFO CoarseGrainedExecutorBackend: Got assigned task 41
20/02/11 01:47:49 INFO Executor: Running task 41.0 in stage 0.0 (TID 41)
20/02/11 01:47:49 INFO NewHadoopRDD: Input split: s3://my-s3-bucket/queries/D12.ifq:2751463424+67108864
20/02/11 01:47:49 INFO S3NativeFileSystem: Opening 's3://my-s3-bucket/queries/D12.ifq' for reading
Warning: Output file 'q' was specified without -S.  This will not work in future Bowtie 2 versions.  Please use -S instead.
Time loading reference: 00:00:00
Time loading forward index: 00:00:01
Time loading mirror index: 00:00:00
Multiseed full-index search: 00:00:44
107721 reads; of these:
  107721 (100.00%) were paired; of these:
    59211 (54.97%) aligned concordantly 0 times
    34088 (31.64%) aligned concordantly exactly 1 time
    14422 (13.39%) aligned concordantly >1 times
    ----
    59211 pairs aligned concordantly 0 times; of these:
      4902 (8.28%) aligned discordantly 1 time
    ----
    54309 pairs aligned 0 times concordantly or discordantly; of these:
      108618 mates make up the pairs; of these:
        81375 (74.92%) aligned 0 times
        17065 (15.71%) aligned exactly 1 time
        10178 (9.37%) aligned >1 times
62.23% overall alignment rate
Time searching: 00:00:45
Overall time: 00:00:45
20/02/11 01:48:35 INFO FileOutputCommitter: File Output Committer Algorithm version is 1
20/02/11 01:48:35 INFO FileOutputCommitter: FileOutputCommitter skip cleanup _temporary folders under output directory:false, ignore cleanup failures: false
20/02/11 01:48:35 INFO DirectFileOutputCommitter: Direct Write: DISABLED
20/02/11 01:48:35 INFO FileOutputCommitter: File Output Committer Algorithm version is 1
20/02/11 01:48:35 INFO FileOutputCommitter: FileOutputCommitter skip cleanup _temporary folders under output directory:false, ignore cleanup failures: false
20/02/11 01:48:35 INFO DirectFileOutputCommitter: Direct Write: DISABLED
20/02/11 01:48:35 INFO FileOutputCommitter: Saved output of task 'attempt_20200211014009_0004_r_000041_0' to hdfs://ip-172-31-37-149.ap-northeast-1.compute.internal:8020/user/hadoop/results/bowtie2/D12.sam/_temporary/0/task_20200211014009_0004_r_000041
20/02/11 01:48:35 INFO SparkHadoopMapRedUtil: attempt_20200211014009_0004_r_000041_0: Committed
20/02/11 01:48:35 INFO Executor: Finished task 41.0 in stage 0.0 (TID 41). 807 bytes result sent to driver
20/02/11 01:49:10 INFO CoarseGrainedExecutorBackend: Driver commanded a shutdown
20/02/11 01:49:10 INFO MemoryStore: MemoryStore cleared
20/02/11 01:49:10 INFO BlockManager: BlockManager stopped
20/02/11 01:49:10 INFO ShutdownHookManager: Shutdown hook called
20/02/11 01:49:10 INFO ShutdownHookManager: Deleting directory /mnt1/yarn/usercache/hadoop/appcache/application_1581382502793_0001/spark-e40ee438-d156-4267-93eb-24ed6f0e03c4
20/02/11 01:49:10 INFO ShutdownHookManager: Deleting directory /mnt/yarn/usercache/hadoop/appcache/application_1581382502793_0001/spark-c467ab8f-d414-462b-a4c3-4ae96f4535df

here is the detail of the tasks

Do you have any clue where goes wrong?
btw, I don't think the tasks match the parallelism I set in the spark args

Can you find the log line that looks like
20/02/11 09:46:56 INFO Bowtie2: Piping RDDBoundFragmentDataset with 0 reference
sequences, 0 read groups, and 0 processing steps to bowtie2 with command: [bowtie2,
-x, reference.fa, --interleaved, -] files: []

This shows the command that was used to call bowtie2 (split into an array).
It appears above that the q you added to -bowtie2_args was interpreted by bowtie2 to be an output file.
...
Warning: Output file 'q' was specified without -S.  This will not work in future
Bowtie 2 versions.  Please use -S instead.

Cannoli works by streaming data converted from Spark RDDs to the external application on stdin and streaming stdout from the external application back into Spark RDDs.

Ah, I was a fool, my intention was to specify the file format, and forgot to remove it when using cannoli
remove q solves my problem, thanks


Install @ionic/app-scripts and typescript won't work in platformio

I found this problem accidentally when trying to install @ionic/app-scripts and typescript using npm i @ionic/app-scripts -D (same for typescript).
Using platformio terminal, the installation won't result in successful installation, but using windows command prompt directly will result in successful installation of @ionic/app-scripts and typescript.
At first I thought maybe because platformio is using windows powershell, but actually when using powershell to install @ionic/app-scripts and typescript, the result is still successful.
As you can see in attachment below

This is when using platformio terminal

And this is when using windows command prompt
And same thing is happening here in attachment below also

Even more peculiar things happen in @ionic/app-scripts package installation

While using windows command prompt, it works perfectly
Hope there'll a solution to this as I starting to love platformio terminal already

I encountered a similar problem with VueJS and solved it in the following way, try:
Add in Auto Run Command of the Platformio Ide Terminal settings:
$env:NODE_ENV="development"


fix: npm alias with peer deps

Changes are visible to end-users: yes/no

Searched for relevant documentation and updated as needed: yes/no
Breaking change (forces users to change their own code or config): yes/no
Suggested release notes appear below: yes/no

Test plan

Covered by existing test cases
New test cases added
Manual testing; please provide instructions so we can reproduce:

replaced with https://github.com/aspect-build/rules_js/pull/1824


date range for two input fields

Although its a very nice extension. I'm facing a issue.
The issue is i want to apply date range on two input fields this is what how I'm doing
onClose: function (dateRangeText) {
	       var datesFormatted = dateRangeText.split(" - ");
	       if(datesFormatted.length >=2)
	       {
	    	   var depDate = datesFormatted[0];
	    	   var retDate = datesFormatted[1];
	    	   $("#departDate").val(depDate);
	       	   $("#returnDate").val(retDate);
		   }

which is working fine but problem is after applying splitting functionality I'm loosing ".ui-datepicker-range" class.
How can i fix this. Any help would be appreciated.
Thank you.

Hi!
If you don't need one field for the range, you don't need this plugin. There is a nice example with two fields — http://jqueryui.com/datepicker/#date-range
To highlight previously selected range you should define beforeShowDay callback as described in the documentation — http://api.jqueryui.com/datepicker/#option-beforeShowDay

Thank you for plugin, one question:
How to initialize field with params from Query string
?date_start=&date_end=
this works: $('#myfield').datepicker('setDate', new Date());
but this not:
var date_start = '12/01/2016'
var date_end = '12/16/2016';
var rangeSeparator = ' - ';
$('#myfield').val(date_start + rangeSeparator + date_end);

Hi, Vlad!
You are thinking in a right way. I would initialise it just putting desired value into the text field. It might, your dates don’t match datepicker format. You provide more detailed sample in the blog post and it works fine for me.
Let me know if I can help you any further.