Try to load JSON-File:  "Could not parse the JSON: invalid type: map"

Hello,
I try to load this JSON file:
[
    {
        "name": "Foyer",
        "x": 0,
        "y": 0,
        "width": 3,
        "height": 3,
        "color": "lightgray",
        "description": "Ein großes, einladendes Foyer mit Marmorboden, hohen Decken und einem majestätischen Kronleuchter. An den Wänden hängen alte Gemälde der Familie Blackwood.",
        "image": "foyer.jpg"
    },
    {
        "name": "Bibliothek",
        "x": 3,
        "y": 0,
        "width": 3,
        "height": 3,
        "color": "lightblue",
        "description": "Eine ruhige Bibliothek mit hohen Bücherregalen, vollgestopft mit alten Büchern. In der Mitte steht ein massiver Eichentisch, auf dem noch geöffnete Bücher und ein Glas Whiskey stehen.",
        "image": "bibliothek.jpg"
    }
]

Part of my program:
#[derive(Debug, serde::Deserialize, Asset, TypePath)]
struct Room {
    name: String,
    x: i32,
    y: i32,
    width: u32,
    height: u32,
    color: String,
    description: String,
    image: String,
}
#[derive(serde::Deserialize, Asset, TypePath)]
struct Rooms {
    rooms: Vec<Room>,
}

#[derive(Resource)]
struct RoomsHandle(Handle<Rooms>);

fn main() {
    App::new()
        .add_plugins((
            DefaultPlugins,
            JsonAssetPlugin::<Rooms>::new(&["rooms.json"]),
        ))
        .insert_resource(Msaa::Off)
        .init_state::<AppState>()
        .add_systems(Startup, setup)
        .add_systems(Update, spawn_plane.run_if(in_state(AppState::Loading)))
        .run();
}

fn setup(
    mut commands: Commands,
    asset_server: Res<AssetServer>
) {
    let rooms = RoomsHandle(asset_server.load("cases/Mord im Herrenhaus/data/rooms.json"));
    commands.insert_resource(rooms);
...
}

fn spawn_plane(
    mut commands: Commands,
    room: Res<RoomsHandle>,
    mut meshes: ResMut<Assets<Mesh>>,
    mut materials: ResMut<Assets<StandardMaterial>>,
    mut rooms: ResMut<Assets<Rooms>>,
    mut state: ResMut<NextState<AppState>>,
) {

    if let Some(room) = rooms.remove(room.0.id()) {
        for r in room.rooms  {
            println!("{:?}",r);
        }

        state.set(AppState::Running);
    }
}

There I get the message " Failed to load asset 'cases/Mord im Herrenhaus/data/rooms.json' with asset loader 'bevy_common_assets::json::JsonAssetLoader<rust_bevy_murder_mystery_game::Rooms>': Could not parse the JSON: invalid type: map, expected a sequence at line 2 column 4
"
Whats wrong?
Best regards Gerhard

@gkvoelkl I believe this behaves as intended.
#[derive(serde::Deserialize, Asset, TypePath)]
struct Rooms {
    rooms: Vec<Room>,
}

should serialize to as json? I'd say roughly the following:
{
  "rooms": [
    // the 'Room' objects here.
  ]
}

I am not certain about this, but I assume serde is fine with not specifying the Rooms object as a literal JSON object, because it only has one field. So it allows for swapping the outermost object with an array, like this:
[
  [
    // the 'Room' objects here.
  ]
]

Try putting the #[serde(transparent)] attribute on the Rooms struct. I think this could fix your issue.

Yeah, your .json file is missing the rooms field in a json object. It should work with the first example json from above.
Also, Room is not an asset (at least not for the code you shared). It should be fine to remove the Asset and TypePath derives for that type.

@gkvoelkl did you get it to work?


Can't import operators using import 'rxjs/add/operator/switchMap';

RxJS version:
version 5.5.2:
package.json
 "dependencies": {
    "@angular/animations": "^5.0.0",
    "@angular/cdk": "^5.0.0-rc0",
    "@angular/common": "^5.0.0",
    "@angular/compiler": "^5.0.0",
    "@angular/core": "^5.0.0",
    "@angular/forms": "^5.0.0",
    "@angular/http": "^5.0.0",
    "@angular/platform-browser": "^5.0.0",
    "@angular/platform-browser-dynamic": "^5.0.0",
    "@angular/router": "^5.0.0",
    "@ng-bootstrap/ng-bootstrap": "^1.0.0-beta.2",
    "@swimlane/ngx-datatable": "^11.0.0",
    "angular2-moment": "^1.7.0",
    "bootstrap": "^4.0.0-alpha.6",
    "core-js": "^2.5.0",
    "font-awesome": "^4.7.0",
    "fuse.js": "^3.0.5",
    "ngx-infinite-scroll": "^0.6.1",
    "primeng": "^5.0.0-rc.0",
    "rxjs": "^5.4.3",
    "zone.js": "^0.8.17"
  },
  "devDependencies": {
    "@angular/cli": "1.5.0",
    "@angular/compiler-cli": "^5.0.0",
    "@angular/language-service": "^5.0.0",
    "@types/jasmine": "^2.5.54",
    "@types/node": "~8.0.25",
    "codelyzer": "~4.0.1",
    "jasmine-core": "~2.8.0",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "~1.7.0",
    "karma-chrome-launcher": "~2.2.0",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "^1.3.0",
    "karma-jasmine": "~1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "protractor": "~5.2.0",
    "ts-node": "~3.3.0",
    "tslint": "~5.8.0",
    "typescript": "=2.6.1"
  }

Code to reproduce:
this is what my code looks like
import { Component, OnInit } from '@angular/core';
import { ActivatedRoute } from '@angular/router';
import { DeploymentsService } from './deployments.service';
import 'rxjs/add/operator/switchMap';

@Component({
    selector: 'app-deployment-details',
    templateUrl: 'deployment-details.component.html'
})

export class DeploymentDetailsComponent implements OnInit {
    private id: number;
    private sub: Observable<string>;
    constructor(private route: ActivatedRoute, private deploymentsService: DeploymentsService) { }

    ngOnInit() {
        this.route.params
            .switchMap(params => {
                const id = +params['id'];
                return this.deploymentsService.getDeploymentDetails(id);
            }).subscribe((response) => {
                console.log('response', response);
            });
    }
}

Expected behavior:
I should be able to use switchMap operator
Actual behavior:
An error gets thrown
DeploymentDetailsComponent_Host.ngfactory.js? [sm]:1 ERROR TypeError: this.route.params.switchMap is not a function
at DeploymentDetailsComponent.ngOnInit (deployment-details.component.ts:21)
at checkAndUpdateDirectiveInline (core.js:12095)
at checkAndUpdateNodeInline (core.js:13598)
at checkAndUpdateNode (core.js:13541)
at debugCheckAndUpdateNode (core.js:14413)
at debugCheckDirectivesFn (core.js:14354)
at Object.eval [as updateDirectives] (DeploymentDetailsComponent_Host.ngfactory.js? [sm]:1)
at Object.debugUpdateDirectives [as updateDirectives] (core.js:14339)
at checkAndUpdateView (core.js:13508)
at callViewAction (core.js:13858)
EDIT: just looked at my lockfile looks like it was installing version rxjs 5.5.2, fixing the version to 5.4.3 makes it work again

+1

@finalxcode apparently this is a breaking change that was not stated clearly in the changelog, see https://github.com/ReactiveX/rxjs/blob/master/doc/lettable-operators.md .. Nothing in the changelog says anything about a "BREAKING CHANGE", also the major version was not bumped.. You just upgrade and nothing works anymore.. so you can either use 5.4.x versions instead or migrate all your observables to the new syntax. That's the way the javascript community does it ;)

@khaledosman It's not a breaking change AFAIK, the add operators weren't removed...
My guess is that the Observable returned by params is not the one getting patched. You can do a quick test by wrapping it with Observable.from and see if it works then.
Observable.from(this.route.params).switchMap()

@jdpigeon it's likely something wrong with your bundling setup. It seems to be adding two copies of rxjs observables. (This is basically was @paulpdaniels is suggesting above). There's nothing that the RxJS library itself can really do to solve that.


feat: Adaptive Trials

Adaptive Trials

Introduces a new study schedule to add adaptive trial functionality into StudyU using Thompson sampling
Author: HPI Master's project in winter term 2023/24
Code copied from https://github.com/malte-j/studyu/tree/mp-ws-23

Screenshots

Todo

[ ] Should not be merged into dev before we did a release of the old stuff!

Designer

[ ] Deprecate old schedule

Create database migration and migrate old schedule into new one. make new one not null
Add example study for supabase cli seed again

[ ] Rename all files and objects with mp23_ prefix
[ ] Improve UX/UI for schedule segment selector

Move on-click action to right-aligned edit button
Create visual preview of schedule

Add (i) information tooltips for each form field and explain them
[ ] Fix auto-save not working reliable with all schedule options (after merge of #626)
[ ] Implement missing segment types

[ ] Counter balanced
[ ] Custom schedule (together with https://github.com/hpi-studyu/studyu/issues/651)

[ ] Solve other todos in code
[ ] Implement usability test and validate if study schedule gets set correctly

App
Didn't check yet

The predefined schedule is currently hardcoded to Alternating. We might want to embed the new study scheduler here.


Global planner fails when the goal point is on the same lanelet, behind the vehicle

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
When the lanelet2 map has a loop, it is possible to have Autoware driving over the loop by setting the goal point behind the vehicle. It is very convenient for testing.
However, if the goal points and the ego vehicle happen to be on the same lanelet, the global planner fails to generate a valid path. For example:

If the goal point is behind the vehicle, but on a different lanelet, then there is no problem.
Expected behavior
As long as there is a possible path from start to goal on the lanelet2 map, Autoware should be able to generate it.
Actual behavior
When the goal point is behind the ego vehicle, on the same lanelet, no valid global plan is generated.
Steps to reproduce
Can be reproduced with the simulator, using any map with a loop.
Versions
No response
Possible causes
No response
Additional context
No response

Yes,this is a known limitation in the current planning stack.You also can  see  the discussion in https://github.com/autowarefoundation/autoware.universe/issues/1715

duplicate of #1715


Encapsulate Delta.post_size() wherever possible

The library was so far based on determining number of states by checking size of post which is now implemented by method Delta.post_size(). Since we changed philosophy what number of states is we need to replace call to that method by Nfa.max_state().

The issue #132 will be closed when the proposed method Nfa::states_number() is implemented. The encapsulation of the current uses of Nfa::Delta::post_size() is a requirement for closing this issue and will come in a separate PR.


WFCORE-5493: Invoke DeploymentTransformer in operation "full-replace-…

…deployment"
https://issues.redhat.com/browse/WFCORE-5493

Hello, fanste. I'm waiting for one of the admins to verify this patch with /ok-to-test in a comment.

@jfdenise  may you take a look please ?

I think the code should be shared instead of being copied from DeploymentAddHandler

New superclass that is used by DeploymentAddHandler and DeploymentFullReplaceHandler?
addFromContentAdditionParameter is slightly different in both handlers. The only methods, that could be extracted are loadDeploymentTransformer and doTransformation and of course the variable deploymentTransformer.

I was thinking of all the transformation code: loading the transformer / transforming in some utility class like DeploymentHandlerUtil

+1 for the Utility class.

For the case, that no notification was sent out for my changes: I've moved the common code to a new utility class.

Rebased the PR and applied the change as requested by @bstansberry

/ok-to-test

Core - Full Integration Build 10966 outcome was FAILURE using a merge of adb1ea584d12076b4e32c30e9e37b56d7ca1f3f9
Summary: Out of memory: Java heap space (This problem is reported because OutOfMemoryError has been found in the build log text) (new); tests failed: 1 (1 new), passed: 7073, ignored: 129 Build time: 07:16:46
Failed tests
org.jboss.as.test.compat.jpa.hibernate.HibernateJarsInDeploymentTestCase:     Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0160: Failed to mount deployment content
    Caused by: java.io.IOException: No space left on device"}}}}
Cannot deploy HibernateJarsInDeploymentTestCase.ear: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"HibernateJarsInDeploymentTestCase.ear\".STRUCTURE" => "WFLYSRV0153: Failed to process phase STRUCTURE of deployment \"HibernateJarsInDeploymentTestCase.ear\"
    Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0160: Failed to mount deployment content
    Caused by: java.io.IOException: No space left on device"}}}}
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:184)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:162)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:91)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:255)
------- Stdout: -------
 [0m17:22:52,806 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/compat/target/wildfly/standalone/data/content/94/2c4be245ec052a4dce936c9b0b1aa2c0ba6e12/content
 [0m [0m17:22:52,814 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "HibernateJarsInDeploymentTestCase.ear" (runtime-name: "HibernateJarsInDeploymentTestCase.ear")
 [0m [31m17:22:52,820 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."HibernateJarsInDeploymentTestCase.ear".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."HibernateJarsInDeploymentTestCase.ear".STRUCTURE: WFLYSRV0153: Failed to process phase STRUCTURE of deployment "HibernateJarsInDeploymentTestCase.ear"
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
	at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0160: Failed to mount deployment content
	at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:95)
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
	... 8 more
Caused by: java.io.IOException: No space left on device
	at java.io.FileOutputStream.writeBytes(Native Method)
	at java.io.FileOutputStream.write(FileOutputStream.java:326)
	at org.jboss.vfs.VFSUtils.copyStream(VFSUtils.java:439)
	at org.jboss.vfs.VFSUtils.copyStream(VFSUtils.java:418)
	at org.jboss.vfs.TempDir.createFile(TempDir.java:86)
	at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:77)
	at org.jboss.vfs.VFS.mountZip(VFS.java:386)
	at org.jboss.vfs.VFS.mountZip(VFS.java:410)
	at org.jboss.as.server.deployment.DeploymentMountProvider$Factory$ServerDeploymentRepositoryImpl.mountDeploymentContent(DeploymentMountProvider.java:108)
	at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:91)
	... 9 more

 [0m [31m17:22:52,827 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "HibernateJarsInDeploymentTestCase.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"HibernateJarsInDeploymentTestCase.ear\".STRUCTURE" => "WFLYSRV0153: Failed to process phase STRUCTURE of deployment \"HibernateJarsInDeploymentTestCase.ear\"
    Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0160: Failed to mount deployment content
    Caused by: java.io.IOException: No space left on device"}}
 [0m [31m17:22:52,827 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "HibernateJarsInDeploymentTestCase.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"HibernateJarsInDeploymentTestCase.ear\".STRUCTURE" => "WFLYSRV0153: Failed to process phase STRUCTURE of deployment \"HibernateJarsInDeploymentTestCase.ear\"
    Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0160: Failed to mount deployment content
    Caused by: java.io.IOException: No space left on device"}}
 [0m [31m17:22:52,828 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "HibernateJarsInDeploymentTestCase.ear" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"HibernateJarsInDeploymentTestCase.ear\".STRUCTURE" => "WFLYSRV0153: Failed to process phase STRUCTURE of deployment \"HibernateJarsInDeploymentTestCase.ear\"
    Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0160: Failed to mount deployment content
    Caused by: java.io.IOException: No space left on device"}}
 [0m [0m17:22:52,828 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment HibernateJarsInDeploymentTestCase.ear (runtime-name: HibernateJarsInDeploymentTestCase.ear) in 0ms
 [0m

@fanste thanks

@fanste
The WildFly project would like to change its license from the GNU Lesser General Public License version 2.1 to the Apache Software License 2.0. We feel that ASL 2.0 is a better option for the project and our user community, as we find a project's use of LGPL can be a barrier to adoption in some parts of the software community, while we see no such barriers from use of ASL.
Do you agree to a relicensing of your contributions to the WildFly, WildFly Core or JBoss AS 7 projects from LGPL 2.1 to ASL 2.0?
I'm happy to answer any questions you may have about this, and I hope you are doing well. Thank you for your contributions to WildFly and open source!
Best regards,
Brian Stansberry
WildFly Project Lead


How can I load extra Google fonts?

Hi all! Thanks for Slidev, it's awesome! 👏
I wish to use a custom font for my  tags, using a font loaded from Google.  This falls outside the fonts setup, which is only about Sans/Serif/Mono.
All it would take is adding the relevant <link/> element in the , but nowhere in Slidev do I see any way of augmenting that element of the page. Short of JS injection that link in the page dynamically, is there a "clean" way of doing it?
Thanks!

you can do it like so:
---
fonts:
  custom: Libre Barcode 39
---

# Welcome to Slidev

barcode


arguments in erroneous deferred library calls should be evaluated first

This is the VM specific bug for the meta-issue #25355 (please see that issue for more details)

Closed for two reasons: this was mostly for the dart1-vm (the dart2-vm doesn't have the checks implemented yet). Also note we decided to change the spec to do what the Dart1 implementations did (see #31933)


[GLUTEN-6483] Support Uniffle 0.9.0

What changes were proposed in this pull request?
Apache Uniffle has released v0.9.0, of which release note could refer to v0.9.0 for more details. This pull request is aimed to support v0.9.0 of Uniffle.
Fixes: #6483.
How was this patch tested?
CI.

Ping @summaryzb.

Try to attach spark.rss.client.assignment.shuffle.nodes.max=1  into the uniffle client config.

@zuston, @summaryzb, I have attached spark.rss.client.assignment.shuffle.nodes.max=1 in integration test. But the CI failed with There isn't enough shuffle servers. Should the version upgrade introduce extra configuration of uniffle?

@zuston, @summaryzb, @xianjingfeng, I have attached spark.rss.client.assignment.shuffle.nodes.max=1 in integration test. But the CI failed with There isn't enough shuffle servers. Should the version upgrade introduce extra configuration of uniffle via https://github.com/apache/incubator-uniffle/pull/1753?

You can try to set rss.rpc.server.type  to GRPC_NETTY

@xianjingfeng, I have set rss.rpc.server.type  to GRPC_NETTY in server.conf. Unfortunately there is the same exception There isn't enough shuffle servers.

@SteNicholas
https://github.com/apache/incubator-gluten/blob/0c519c4d5f7bfabc968e65d857b037f46058f51b/.github/workflows/velox_docker.yml#L507
https://github.com/apache/incubator-gluten/blob/0c519c4d5f7bfabc968e65d857b037f46058f51b/.github/workflows/velox_docker.yml#L519

Do you have a solution for the current CI failure? @SteNicholas

Maybe it's better to add mvn options in here https://github.com/apache/incubator-gluten/pull/6484/files#diff-38eda6989d285e6a3d79a3a66cc656d0b6d483b3d5c77bd0969d878642fd0f0eL512

Ping @summaryzb, @xianjingfeng. PTAL.

@PHILO-HE, the CI of uniffle has already been successful. Please help to merge.

Just wait for the CI finished. After that, I would merge this pr if no more comments.


Report out of UX research for ministries

Title of ticket:
Description
Summarize issue
Dependencies
Are there any dependencies?
DOD

[ ] List the items that need to be complete for this ticket to be considered done
[ ]
[ ]
[ ]
[ ]

Description:
Develop a virtual white board to share pain points, information summarized, action items
DOD:

[ ] Miro board completed
[ ] Reviewed by team
[ ] Shared at sprint review

Demo completed on August 31st.


How can I get the aspect ratio of a video?

I don't want to use a fixed aspect ratio.

You don't have to use aspect ratio widget


Some images don't exist in images list, but they could be queried out.

In GitLab by @luotian-github on Sep 19, 2018, 17:02
The object list contains nodegroup. So it is unnormal to turn up nodegroup object when I query node object.

In GitLab by @Robin-Mao on Nov 8, 2019, 07:59
The image item doesn't show all the images, it only show the project's images which you have permissions.

In GitLab by @guyingyan on Nov 8, 2019, 07:59
is issue is fixed in installation tool

In GitLab by @luotian-github on Nov 8, 2019, 07:59
No problem yet.

In GitLab by @sokril on Nov 8, 2019, 08:27
closed

In GitLab by @sokril on Nov 8, 2019, 08:27
assigned to @luotian-github


Training Error

Traceback (most recent call last):
File "train_dreambooth.py", line 822, in
main(args)
File "train_dreambooth.py", line 475, in main
images = pipeline(example["prompt"]).images
File "/usr/local/lib/python3.8/dist-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
return func(*args, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/diffusers/pipelines/stable_diffusion/pipeline_stable_diffusion.py", line 532, in call
noise_pred = self.unet(latent_model_input, t, encoder_hidden_states=text_embeddings).sample
File "/usr/local/lib/python3.8/dist-packages/torch/nn/modules/module.py", line 1190, in _call_impl
return forward_call(*input, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/diffusers/models/unet_2d_condition.py", line 341, in forward
sample, res_samples = downsample_block(
File "/usr/local/lib/python3.8/dist-packages/torch/nn/modules/module.py", line 1190, in _call_impl
return forward_call(*input, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/diffusers/models/unet_2d_blocks.py", line 644, in forward
hidden_states = attn(hidden_states, encoder_hidden_states=encoder_hidden_states).sample
File "/usr/local/lib/python3.8/dist-packages/torch/nn/modules/module.py", line 1190, in _call_impl
return forward_call(*input, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/diffusers/models/attention.py", line 221, in forward
hidden_states = block(hidden_states, context=encoder_hidden_states, timestep=timestep)
File "/usr/local/lib/python3.8/dist-packages/torch/nn/modules/module.py", line 1190, in _call_impl
return forward_call(*input, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/diffusers/models/attention.py", line 479, in forward
hidden_states = self.attn1(norm_hidden_states) + hidden_states
File "/usr/local/lib/python3.8/dist-packages/torch/nn/modules/module.py", line 1190, in _call_impl
return forward_call(*input, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/diffusers/models/attention.py", line 568, in forward
hidden_states = self._memory_efficient_attention_xformers(query, key, value)
File "/usr/local/lib/python3.8/dist-packages/diffusers/models/attention.py", line 624, in _memory_efficient_attention_xformers
hidden_states = xformers.ops.memory_efficient_attention(query, key, value, attn_bias=None)
File "/usr/local/lib/python3.8/dist-packages/xformers/ops/memory_efficient_attention.py", line 967, in memory_efficient_attention
return op.forward_no_grad(
File "/usr/local/lib/python3.8/dist-packages/xformers/ops/memory_efficient_attention.py", line 343, in forward_no_grad
return cls.FORWARD_OPERATOR(
File "/usr/local/lib/python3.8/dist-packages/xformers/ops/common.py", line 11, in no_such_operator
raise RuntimeError(
RuntimeError: No such operator xformers::efficient_attention_forward_cutlass - did you forget to build xformers with python setup.py develop?

colab pro ?

colab pro ?

No,free

it should work then, make sure you're using this notebook : https://colab.research.google.com/github/TheLastBen/fast-stable-diffusion/blob/main/fast-DreamBooth.ipynb

it should work then, make sure you're using this notebook : https://colab.research.google.com/github/TheLastBen/fast-stable-diffusion/blob/main/fast-DreamBooth.ipynb

There’s a AUTOMATIC1111.ipynb error: Traceback (most recent call last):
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 14, in
from modules import shared, devices, sd_samplers, upscaler, extensions, localization, ui_tempdir
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/sd_samplers.py", line 12, in
from modules import prompt_parser, devices, processing, images
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/processing.py", line 15, in
import modules.sd_hijack
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/sd_hijack.py", line 32, in
ldm.modules.attention.BasicTransformerBlock.ATTENTION_MODES["softmax-xformers"] = ldm.modules.attention.CrossAttention
AttributeError: type object 'BasicTransformerBlock' has no attribute 'ATTENTION_MODES'

remove the folder sd and do a clean run


Make the default namepace name changable

Search before asking

[X] I had searched in the issues and found no similar issues.

Motivation
It should be changable, as other namespaces.
Solution
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

I have learned kvrocks for some time. I have the will to implement that (or have a try).
There are two questions.

Current namespace name is not modifiable, token can be modified by function(namespace set). Does changable 'name' refer to token?
Default namespace is a literal value. How to make it modifiable, is it through config file ?

Yeah, IIRC it's currently something like __namespace, but I think it's better to be changable.
I don't know which one is better: store in rocksdb or in the config file.
cc @mapleFU @git-hulk do you have any idea?

Also another big issue is to be compatible to old version: users can use new version of kvrocks with their old data, and they want these old data can work well.

@PragmaTwice I'm not quite sure why we want to make it changeable. If for the space overhead consideration, it shouldn't take much more than the shorter one since the rocksdb has internal compression for the common prefix.

Because I believe the default namespace should have the same status as other namespaces.
Currently, in kvrocks, the default namespace is a very special namespace, and admins cannot switch the default namespace to another one. This has some significant drawbacks, such as certain admin operations can only be performed in the default namespace.
I think this is a design flaw in kvrocks, and correcting it would require some cost at present.

Just curious why it should be changable? Is there any reason for that?

Because I believe the default namespace should have the same status as other namespaces.

It's a good reason but I think we have too many legacy user and perhaps this means maintaining two parts of code?

If there is a good solution, we can avoid maintenance difficulties and correct this problem. (But TBH, design errors in the early stage will lead to unbearable costs, and everyone should understand this truth.)
Perhaps it's time for us to reconsider the authentication and permission management in kvrocks.

Seems it would be a "code" level changing rather than just seting another column family in config 🤔

Currently, in kvrocks, the default namespace is a very special namespace, and admins cannot switch the default namespace to another one. This has some significant drawbacks, such as certain admin operations can only be performed in the default namespace.

We can achieve this by supporting the switch namespace API? The initial design didn't expect the admin to change data of other namespaces except to maintain the namespace/token pair itself. And I do agree the default namespace is very special, but it's to align with the Redis authentication way.


Add syntax highlighting to a code block.

If possible, I would appreciate code block segmentation or syntax highlighting.

This feature has actually been implemented, but sometimes ChatGPT doesn't wrap the generated code in `````` symbols, so occasionally it doesn't work.

Can you please make a few more attempts?

It seems to be working here.


Multple Inlines in Admin  page

Can we have multiple Tablur,Stacked inlines in single admin page

Did you try that? It should works

I'm closing thia since it's not a bug. Feel free to  reopen if you found issues with multiple inlines on the same page.

Thanks for reply,
Yesterday it showed me InlineFormfeildset does not have model object
but today it worked like a charm !
Excellent Work ..


Upgrade Netty to version 4.1.97.Final

Description

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

/component-tests camel-netty camel-netty-http

I think we should backport to 4.0.x


"About" section in settings screen

Include contents of README.txt with links

Added in v1.1.0. Opening README on click of "About Spell Gallery" link.


Does this fw disable the Wifi radio?

Thank you for the work on firmware.
I just want to disable Wifi radio permanently b/c I am concerned staying with wifi on all night long near my bed.
It isn't clear to me what this firmware does?
Does this firmware disable the wifi radio, or just do not communicate with xiaomi servers?
Is there something that can be desoldered on the PCB to disable wifi permanently?
Also can you put a link to the cable that you used to connect to the lamp, USB to serial.
Thank you again !

Hi,
this seems to be a reoccuring question. According to the Espressif SDK we would have to enable Wifi via esp_wifi_init. This firmware is never initializing the wifi.
This is different to the modules which ship preloaded with a firmware. These usually automatically initialize the wifi and wait for some AT commands.
Disabling the wifi via Hardware modification would be pretty invasive. You could replace the entire ESP module with another µC of your choice. Another option could be to cut the WiFi Antenna, but I'm not sure if this will completly block wifi access. Cutting the antenna should at least dampen the signal significantly.
I'm not sure what kind of cable I used, but every 3.3V serial cable should work. If you want a nice one you could buy e.g. https://www.digikey.de/product-detail/de/ftdi/TTL-234X-3V3/768-1319-ND/6823715, but a cheap one https://www.ebay.com/itm/USB-to-TTL-Converter-UART-module-CH340G-3-3V-5V-Replace-Pl2303-CP2102/263540409685 will probably work as well (I have no affiliation with neither digikey or the ebay seller).


3rd function

Pull Request
Before creating a PR, just answer a below questions to get started...

What type of change does your PR bring?

[     ] Bug fix
[✔ ] Feature Update
[     ] Issue fix
[     ] Doc fix/update
[     ] Other

What OS you're using right now?

[     ] Windows 7 & above
[ ✔] Linux (Ubuntu, Debian)
[     ] macOS

If this PR fixes a bug, refer to the issue number
Solves Issue: #21

If this PR brings a feature, what kind it is?
 Add 3rd function to implement files without TXT files

If this PR is related to an issue or it's discussed, refer issue here
Issue: #21

Any else you want to convey?
No

Does your PR work in a stable manner?

[✔ ] Yes
[      ] No

@alphaX86 I have made Issue #21 in this PR Complete.
Here Greetings Check is not passed I don't know why Can you pls look into it.

@alphaX86 I have made Issue #21 in this PR Complete.
Here Greetings Check is not passed I don't know why Can you pls look into it.

Hmm, seems I need to refine that CI a bit. Leave that work flow and the GitLab one. I'll check the functions and return to you

Hmm, seems I need to refine that CI a bit. Leave that work flow and the GitLab one. I'll check the functions and return to you

Do that change alone and I'll merge, consider it as approved @codeit13

Do that change alone and I'll merge, consider it as approved @codeit13


Is scc-broker services for kubernetes used /required ?

I'm looking at the files for deploying SCC on kubernetes.
I don't understand why there is a service defined for the scc-broker (socketcluster/kubernetes/scc-broker-service.yaml). As far as I can see, the service endpoint isn't used in the code at all.
Or am I missing something ?

My bad, I didn't fully understand the deployment on kubernetes.


Switching from validationEngine.js

I'm switching from validationEngine.js which seems no longer actively maintained. When looking at the documentation I noticed the requirements are defined in JavaScript, rather than using HTML attributes. Is there any reason for this?
Also, is there a way to scroll the form to the field that needs to be fixed when clicking a submit button at the end of the form?
Additionally, is it possible to display the errors differently (bubbles), rather than pushing content under the field (potentially breaking the layout)?
Lastly, any support for AJAX calls? I need to verify whether a username/email address already exists and show an error if already taken.

Please see the docs or sewrch stackoverflow.
All of your mentioned points are covered by the lib.

Will close for now. Feel free to ask further questions regarding this topic here. We can re-open if required.


Extension - Screen flickering error when interacting with extensions

Describe the bug
Screen flickering error when interacting with extensions
To reproduce the bug
Browser: Brave
Version: v1.66.115
Actual:

Version test: http://<IP_ADDRESS>:8900/s/zbRn2gnrcqRRrZq
Validation passed

Install
Upgrade version


Sorted imports in docs/_ext/djangodocs.py

Follow up to 1cdfe8d91215eefaa18c398069dd9c6879a9511d.

Docs failure is not related with this PR, see #12698.

@timgraham Thanks :+1:


defaultTheme passed by options in withStyles is ignored

The defaultTheme specified by option in withStyle helper function, has a default value that nevers takes control inside the logic.
Expected Behavior 🤔
The behaviour of the defaultTheme fallback should take the defaultTheme passed by props instead of take the global defaultTheme declaration.
https://github.com/mui-org/material-ui/blob/master/packages/material-ui/src/styles/withStyles.js#L95
this.theme = listenToTheme ? themeListener.initial(context) || props.defaultTheme : noopTheme;

Context 🔦
In many test that we develop we don't want to provide a MuiThemeContext, sometimes it's usefull use a customTheme to ensure the correct style mapping.
Your Environment 🌎

Tech
Version

Material-UI
v3.7.1

React
v16.7.0

I can't see any mention of a default theme being passed in via options but I found
https://github.com/mui-org/material-ui/blob/01dce6d065673d792f3ca8598ee60a18b9f7a0f6/packages/material-ui-styles/src/withStyles.js#L175-L179
which means it's supported by @material-ui/styles. It doesn't look like it's documented though https://material-ui.com/css-in-js/api/#withstyles-styles-options-higher-order-component
@oliviertassinari ?

@oliviertassinari in case that defaultTheme has not support of customDefaultTheme, why the withStyles has the defaultTheme prop but is never used inside the logic?
https://github.com/mui-org/material-ui/blob/master/packages/material-ui/src/styles/withStyles.js#L334
Sorry about my miss understanding of this undocumented part of withStyles but Is weird if you can set such property in fact is declared but never used in line 334.

@rubeniskov You are linking the legacy styling solution. We can forget about it. It will soon be gone. @material-ui/styles !== @material-ui/core/styles.

Let's dive a bit more into how it works. @material-ui/core/styles has a default hard-coded theme. It can't be configured with the options. @material-ui/styles introduces a defaultTheme option.
We can use "Dependency Injection" to swap the core components styling solution between the two versions.

I'm keeping the issue open because we need to add defaultTheme in the documentation.

@oliviertassinari I appreciate your time and your advice, by now we are gonna change the legacy @material-ui/styles/withStyles to the new @material-ui/styles/withStyles in our case all withStyles callings are centralised in a unique custom withStyles decorator so in that case there's no need to refactor all project. In fact this system allow us to set the defaultTheme configuration in our decorator to provide our custom theme when theme provider is not specified. Thank you. If there any contribution that you or your team need don't doubt to propose us.


Add volume_type argument for ebs_block_device

Description
Allow users to pass the "volume_type" variable in the "ebs_block_device" map so that they can use any other volume besides the default "gp2" type.
Documentation

TODOs
Please ensure all of these TODOs are completed before asking for a review.

[ ] Ensure the branch is named correctly with the issue number. e.g: feature/new-vpc-endpoints-955 or bug/missing-count-param-434.
[ ] Update the docs.
[ ] Keep the changes backward compatible where possible.
[ ] Run the pre-commit checks successfully.
[ ] Run the relevant tests successfully.
[ ] Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.

Related Issues

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes
Have you signed the CLA already but the status is still pending? Recheck it.


help, about ffprobe

like this command "ffprobe -v quiet -print_format json -show_packets",I want use the fluent-ffmpeg,what should I do? help,thanks @njoyard

it's supported?


p2p liveness checking

Relates to #291. Add a new pair of messages to the net plugin that carry the current time as a payload. These messages could be used for liveness checking in the case of peers that are non-producing full nodes. The two messages, Ping and Pong, may work for detecting clock skew but I'm not certain that will be particularly accurate when dealing with varying levels of network latency introduced by the use asynch messaging. Perhaps sending a second round of messages that carry the result of timing the send of the first message.

Let's also add fields to the handshake message to make it effectively a "ping" as well. Note that each side will independently send a handshake message at connection start time. To make latency measurement work, we'll have to make the peer answer a handshake with a "pong" message.

Debugging is ongoing.

Packets are transmitted and received and processed and... something is slightly tangled in the processing of each peer's timestamps, so the numbers make no sense.  I just have to work through it.

Processing is working.  Currently attempting to explain unusually high measured latency.

Modifying start_read_message to use async_read_some instead of async_read reduces measured latency from 20 ms to 12 ms.

That's interesting. Can you remind me the branch you are using for this work?
I'd like to see how you are caching partial messages. In fact, on TAO we found amazing speedup using application level buffer management.

The branch name is p2p-liveness-checking-395, but I haven't pushed it yet.  It still contains C-isms that have to be eradicated.  The relevant method is small enough though.
    void read_pending( connection_ptr c ) {
      c->socket->async_read_some(boost::asio::buffer(c->pending_message_buffer.data() + c->pending_message_offset,
                                 c->pending_message_size),
          [this,c]( boost::system::error_code ec, std::size_t bytes_transferred)
    {
          if(!ec) {
            c->message_size += bytes_transferred;
            try {
              auto msg = fc::raw::unpack<net_message>( c->pending_message_buffer );
              c->pending_message_offset = 0; // no unpack exception, so we have a whole msg
              precache pc( c );
              msg.visit (pc);
              start_read_message( c );

              msgHandler m(*this, c);
              msg.visit(m);
              return;
            } catch ( const fc::exception& ) {
              c->pending_message_offset += bytes_transferred;
              read_pending( c );
            }
          } else {
            elog( "Error reading message from connection: ${m}", ("m", ec.message() ) );
          }
        });
    }

This is a substitute for start_reading_pending_buffer(), invoked in the same location and manner as that method, in start_read_message().  It depends on a new member, size_t pending_message_offset{0}; added to the connection class.

After correcting my math, here's what clock offsets look like:

Using async_read is indistinguishable from async_read_some on an unloaded system.
For posterity, the plot comes from outputting the clockoffset with dlog() as:
1011483ms thread-0   net_plugin.cpp:813            handle_message       ] Clock offset is 21413.00000000000000000ns (21.41300000000000026us)

then running:
grep "Clock offset" stderr.txt | tr -d '()' | awk '{print $10}' | gnuplot -p -e "set title 'Clock Offset'; set ylabel '{/Symbol m}s'; set grid xtics ytics; plot '<cat' title '' with lines"

in the data directories produced by launcher.

Rebased and reconstructed to mesh well with branch p2p-sync-slow-peers and pushed.

closing, feature merged into master


Infinite spinner when using ListWidget

thanks a lot for the widget, it's been working great.
I tried upgrading to use ListView but it has a problem:
here is my code
    <FlexWidget style={styles.container}>
      {renderDate()}
      {/* There is bug in using array.map so just render as many as we can. */}

      <ListWidget>
        {renderTask(0)}
        {/*     {renderTask(1)}
        {renderTask(2)}
        {renderTask(3)}
        {renderTask(4)}
        {renderTask(5)}
        {renderTask(6)} */}
      </ListWidget>
    </FlexWidget>
    ```
   with this code, im getting an infinite spinner when i'm previewing it in my app

and the widget on the home screen isn't loading

thanks!

Hi.
What error are you getting in the console?
Can you share the complete code of the widget, or create a minimal widget that reproduces the issue so I can test it?
There was an issue when using a widget next to array.map, but it should be fixed id 0.5.1.

for sure, i was able to repro down to this
const CanonTrackerWidget = () => {
  const myTasks = [{name: 'hi'}, {name: 'bye'}];

  return (
    <FlexWidget>
      <ListWidget>
        {myTasks.map(task => (
          <TextWidget key={task.name}>{task.name}</TextWidget>
        ))}
      </ListWidget>
    </FlexWidget>
  );
};

TextWidget accepts a text prop for the text, the text should not be inside the TextWidget.
https://saleksovski.github.io/react-native-android-widget/docs/public-api/interfaces/TextWidgetProps

hey - sorry for the mistake, i was trying to create a small example to repro.
the issue isn't yet solved even after fixing the text.
Thanks for the followup!

Can you share the error you are getting?
Another thing I can think of is not setting the size (height/width) for the ListWidget, but I'm not sure if that's the case for your widget that's not present in the small example.

I modified my small example to include the h and w
const CanonTrackerWidget = () => {
  const myTasks = [{name: 'hi'}, {name: 'bye'}];

  return (
    <FlexWidget>
      <ListWidget
        style={{
          height: 'match_parent',
          width: 'match_parent',
          backgroundColor: '#1F3529',
        }}>
        {myTasks.map(task => (
          <TextWidget key={task.name}>{task.name}</TextWidget>
        ))}
      </ListWidget>
    </FlexWidget>
  );
};

also attempted to change height and width to 300.
so here is what is happening:
I see no error or warning in the logs, everything seems fine.
I see the same spinner as the screenshot above in the preview in my RN app, and the same gray "click to update widget" on the main screen.

I just released 0.5.2 version of the library.
I think that the problem was that you didn't have clickAction and clickActionData on the items inside ListWidget.
I fixed that bug, and it should work correctly now.
Another issue with the example (besides the {task.name} inside TextWidget which should be set as a text prop) is that the ListWidget has a height/width of 0. I think you don't have that issue in your real widget.
Please try the new version, and see if it fixes your issue.

Okay I figure out what's going on. I copied your ListWidget example and starting modifying closer to my sample code. It turns out, it's the FlexWidget around the ListView.
I think I need it because i need a header to the list, then i want the user to scroll the list while the header is there.
Here is a repro code
const CanonTrackerWidget = () => {
  return (
    <FlexWidget>
      <ListWidget
        style={{
          height: 'match_parent',
          width: 'match_parent',
          backgroundColor: '#1F3529',
          flex: 1,
        }}>
        {Array.from({length: 15}).map((_, i) => (
          <FlexWidget
            key={i}
            style={{
              width: 'match_parent',
              alignItems: 'center',
              flexDirection: 'row',
              justifyContent: 'center',
              padding: 8,
            }}
            clickAction='OPEN_URI'
            clickActionData={{
              uri: `androidwidgetexample://list/list-demo/${i + 1}`,
            }}>
            <TextWidget text={`React Native Android Widget Release 0.${i + 1}`} />
          </FlexWidget>
        ))}
      </ListWidget>
    </FlexWidget>
  );
};

The problem with the latest code you shared is that the first FlexWidget does not have size.
It's default size is match_content (meaning it's size is the same as the size of it's children).
But ListWidget has a match_parent height/width, meaning 0.
You should put style={{ height: 'match_parent', width: 'match_parent' }} on the first FlexWidget.
Also, ListWidget does not accept flex: 1 style prop.
I released a new version, 0.5.3 that will log the native error so it can be easier to see what the error is.
Can you confirm it works now?

I have a feeling this might have broke the widget. like it works fine within the react native preview but not when it's on the home screen. I'll double check tomorrow though i might be wrong

Something is a bit weird.
Here is what it looks like when previewd inside my app:

but here is what it looks like on the home screen

this is my code
export function CanonTrackerWidget() {
  return (
    <ListWidget
      style={{
        height: 'match_parent',
        width: 'match_parent',
        backgroundColor: '#1F3529',
      }}>
      {Array.from({length: 15}).map((_, i) => (
        <FlexWidget
          key={i}
          style={{
            width: 'match_parent',
            alignItems: 'center',
            flexDirection: 'row',
            justifyContent: 'center',
            padding: 8,
          }}
          clickAction='OPEN_URI'
          clickActionData={{
            uri: `androidwidgetexample://list/list-demo/${i + 1}`,
          }}>
          <TextWidget text={`React Native Android Widget Release 0.${i + 1}`} />
        </FlexWidget>
      ))}
    </ListWidget>
  );
}

@mark-yacoub Any update here? Did you make it work?

So I tried it on a physical device and things aren't great.
without the listwidget, things are in good order as shown in the following screenshot

however, you can see that the widget is always not reaching the edge of the widget border.
Here is my xml
<?xml version="1.0" encoding="utf-8"?>

<appwidget-provider xmlns:android="http://schemas.android.com/apk/res/android"
    android:targetCellWidth="3"
    android:targetCellHeight="2"

    android:updatePeriodMillis="1860000"

    android:initialLayout="@layout/rn_widget"

    android:previewImage="@drawable/widget_screenshot"
    android:description="@string/widget_description"

    android:resizeMode="horizontal|vertical"

    android:widgetCategory="home_screen">
</appwidget-provider>

here is my container
  return (
    <FlexWidget style={styles.container}>
      {renderDate()}
      {!!tasksForDate.length && renderTasks()}
      {!tasksForDate.length && renderNoTasks()}
    </FlexWidget>
  );
};

const styles = {
  container: {
    backgroundColor: '#ffffff',
    borderRadius: 16,
    flex: 1,
    height: '130',
    overflow: 'auto',
    paddingVertical: 5,
    width: 'match_parent',
  },

currently, this is my renderTasks
  const renderTasks = () => tasksForDate.map(task => renderTask(task));

however, once i wrap in List widget like
  const renderTasks = () => (
    <ListWidget style={{height: 'match_parent', width: 'match_parent'}}>
      {tasksForDate.map(task => renderTask(task))}
    </ListWidget>
  );

it starts acting weird and it looks like

scrolling is great though.


Performance issues.

(Since LL) the performances of the Drupal are just horrible.
It takes seconds to load pages (in both front and BO)
Not only there were tons of completely useless content types, but they deploy lot of creepy modules (from node_autotitle to fc , etccc....) that are making the whole interface slow and/or un-useable.
(ex. at begining of the summer it was impossible to edit content types, fields, or features, those parts would simply crash.
TODO: ?? good question, continue cleaning up, remove useless modules etc...

largely cleared


Skip empty batches

Previously we were erroring out in fetch_batch#last_offset because messages
would be empty so last would return nil and then nil wouldn't define offset.
I fixed this by returning -2 if messages was empty, thereby avoiding the error.
Fixes #237

@dasch here's my proposed fix for #237

Why not return nil instead?

If I return nil then I get a no method error on the nil object.

This was fixed by #240 which was a better solution.


Fully Configurable TensorFlow Models

Goal
Allow for the Android app to use any TensorFlow model with a supplied configuration file for retrieving the weights and biases. (Most of the big points on #28)
Parts

[ ] Complete #32 basic TensorFlow in the app

[x] Add ability for server to supply the fields to get the weight values trainable parameters

[x] Add ability for app to get & send all the fields supplied by the server

[ ] Test that everything is happening

[ ] Supply a program (set of python methods) to CrowdML supervisors that will populate the .json configuration data needed

Should give named parameters from the graph/model and populate the feature sizes etc.
Something like call:

def generateCrowdMLTFConfig(session):
    ...

Bullets 2 and 3 have been updated with the current work I have implemented. I should have a PR soon.


release artifacts for release v0.0.4

aws-controllers-k8s/community#1701
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/ok-to-test

/lgtm


obs not recognizing conservation status associated with taxon and place

this obs which is in Indiana does not recognize the conservation status associated with this taxon in Indiana https://www.inaturalist.org/observations/1633265
its close to the Michigan border and obs of this taxon in the center of Indiana do recognize the conservation status, but I'm not sure that that border proximity is the problem

What's happening here is the public positional accuracy circle 10,000 m is not contained within the bounding box of Indiana, so if we say the observation was made in Indiana we're reducing the uncertainty of the coordinate obscuration by quite a bit. I believe the intent here was not to reduce the uncertainty of obscuration, as well as to try to make relatively accurate statements about where observations were, e.g. if the coordinate are in San Francisco but the accuracy circle extends to Reno, we can't say with certainty that the observation was made in San Francisco.
If we made an exception in this case, e.g. we pulled conservation statuses based on the coordinates without considering the spatial uncertainty, I guess we would provide more coordinate uncertainty b/c it would be auto-obscured, but less than we would if the user manually obscured it, b/c viewers would know the obs was made in Indiana. So I don't really see a perfect solution here.

I don't think I understood exactly what was going on here when I made this issue. Can you confirm that this is the case:

all observations of taxa in places with conservation statuses for that species (e.g. obs of sandhill cranes in Indiana) ARE being obscured automatically
but if the public positional accuracy overlaps the border, we DO NOT display the 'threatened in Indiana' badge on the observation page
I believe thats whats happening with this test obs http://www.inaturalist.org/observations/1635622. I was unaware when I made this issue that 1 was happening

Well, be clear about what you're saying. These two statements are true:

all observations of taxa in places with conservation statuses for that species AND have coordinates that lie within the boundaries of those places (e.g. obs of sandhill cranes in Indiana) ARE being obscured automatically
but if the public positional accuracy overlaps the border, we DO NOT display the 'threatened in Indiana' badge on the observation page

It's inconsistent, but also seems to provide the maximum privacy for the observed organism. I don't feel incredibly strongly about which way to go on this, but imagine if the obscured coordinates for this observation were such that only a sliver of the circle entered Indiana. If we then revealed that the true coordinates were in Indiana by showing an Indiana conservation status, it would be very obvious where the true coordinates were, and would effectively remove the effect of obscuring the coordinates. It's an edge case, but one that would also apply if we switched to coordinate obscuration by coordinate rounding instead of choosing a random location within a radius.

Seems to me with a large place like a state, nothing is lost by auto
obscuring any time it's in Indiana.  Either we auto obscure in which case
it's sometimes obvious where it is, or we don't in which case it is always
obvious. Right?
Of course, with a smaller place, like a 40 acre preserve, that isn't true.
Not sure what the answer is, just sharing thoughts.
On Mon, Jun 15, 2015 at 2:38 PM, Ken-ichi<EMAIL_ADDRESS>wrote:

Well, be clear about what you're saying. These two statements are true:

all observations of taxa in places with conservation statuses for
that species AND have coordinates that lie within the boundaries of
those places (e.g. obs of sandhill cranes in Indiana) ARE being
obscured automatically
but if the public positional accuracy overlaps the border, we DO
NOT display the 'threatened in Indiana' badge on the observation page

It's inconsistent, but also seems to provide the maximum privacy for the
observed organism. I don't feel incredibly strongly about which way to go
on this, but imagine if the obscured coordinates for this observation were
such that only a sliver of the circle entered Indiana. If we then revealed
that the true coordinates were in Indiana by showing an Indiana
conservation status, it would be very obvious where the true coordinates
were, and would effectively remove the effect of obscuring the coordinates.
It's an edge case, but one that would also apply if we switched to
coordinate obscuration by coordinate rounding instead of choosing a random
location within a radius.
—
Reply to this email directly or view it on GitHub
https://github.com/inaturalist/inaturalist/issues/598#issuecomment-112166020
.

--
Charlie Hohn
Montpelier, Vermont
coyot.es/slowwatermovement

It seems similar to the issue of an obscured terrestrial species along the shore of a large body of water.  many times, the obscured point is placed in the body of water, where the species is very unlikely to be found, living that remaining sliver on land as a pretty good representation of where the species is.
Would it be possible to keep the obscured coordinates within the state boundary?

OK - thanks - my apologies for misunderstanding this issue - I think others, including the original reporter of this on the GoogleGroup are similarly confused about what's happening as I was https://groups.google.com/forum/#!topic/inaturalist/Ox_w4Yr48A4
I've adjusted the title and initial comment to clarify that:

There is no bug/unusual behavior with auto-obscuring. Observations ARE being auto-obscured. I'll chime in to the google group to clarify this.
The only issue here seems to be on whether we should display the 'Threatened' badge on the observation components:

As Ken-ichi clarified, in the example posted to the google group the public positional accuracy circle is not completely contained within Indiana so showing the 'EN in Indiana' would reveal additional information about this private location.

Since this is not a bug, I'm closing this 'bug issue', but I do think that the confusion introduced by the inconsistent display of threatened badges is a cost that outweighs the benefit of not revealing additional information about obscured points (which as CTracey says is analogous to existing issues with terrestrial obs along big bodies of water). So if someone wants to open an 'improvement issue' to suggest displaying threatened badges regardless of the public positional accuracy circle, IMO that would be a good idea


What is wrong with this !add command?

!add sku=31181;6;buy.metal=2.33;sell.metal=2.77
I want to add the killing tree, buying it for 2.33 ref and selling for 2.77 ref
My bot says this:

idk which properties are missing or if I just wrote something wrong. Could someone write the right command and an explanation of why mine was wrong?

Duplicate of #290

Duplicate of #290


Missing step

I was unable to do this on my tenant until I enabled another preview feature: Users can use the combined security information registration experience
This was not listed per the documentation but was required to setup the FIDO2 key.

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

ID: 78c66f8a-1c40-e31c-5c7e-7870b7d65e0c
Version Independent ID: 3e8301bc-8e4d-ee23-8770-2f75e170e01a
Content: Passwordless security key sign-in (preview) - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-authentication-passwordless-security-key.md
Service: active-directory
Sub-service: authentication
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@aperalesMN
Thanks for your feedback! We will investigate and update as appropriate.

@aperalesMN
Within the documentation there's a section that states:
"Registration features for passwordless authentication methods rely on the combined registration feature. Follow the steps in the article Enable combined security information registration (preview), to enable combined registration."
Did you want the "Enable combined security information registration (preview)" within the Requirements section since it's needed to enable the FIDO2 Security key?

Yes, that is what I am referring to. It would just make it more clear if somebody isn’t aware that the other preview features need to be turned on.
Andrew Perales
Network Administrator
4700 Falls of Neuse Rd | Raleigh, NC 27609
P<PHONE_NUMBER> x. 12130 | F<PHONE_NUMBER> | C<PHONE_NUMBER>
Creative People, Practical Solutions. ®
From: James Tran - MSFT<EMAIL_ADDRESS>Sent: Tuesday, August 11, 2020 2:10 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Perales, Andrew<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Missing step (#60642)
CAUTION: This email originated from outside of the organization.
@aperalesMNhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FaperalesMN&data=02|01|aperales%40moffattnichol.com|b0caee7f423c4f53fb0608d83e21b826|e56883ae3b824b47993a9166c2cff860|1|0|637327661829907199&sdata=es7QRSqDhDl4BmIdz%2FWAnDEo43nj6mC8h2XsSvKI%2FPI%3D&reserved=0
Within the documentation there's a section that states:
"Registration features for passwordless authentication methods rely on the combined registration feature. Follow the steps in the article Enable combined security information registration (preview), to enable combined registration."
Did you want the "Enable combined security information registration (preview)" within the Requirements section since it's needed to enable the FIDO2 Security key?
[image]https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F36619112%2F89932772-0360c280-dbc3-11ea-8763-20a676f38763.png&data=02|01|aperales%40moffattnichol.com|b0caee7f423c4f53fb0608d83e21b826|e56883ae3b824b47993a9166c2cff860|1|0|637327661829907199&sdata=pUWEfiA%2B6s4rhmwIbLrhoqLDBxWUDDDkxckt%2FvG4hLQ%3D&reserved=0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F60642%23issuecomment-672149142&data=02|01|aperales%40moffattnichol.com|b0caee7f423c4f53fb0608d83e21b826|e56883ae3b824b47993a9166c2cff860|1|0|637327661829917187&sdata=DUHqFVriPdWjswanY2u%2BEblTk3%2FNrBTMuaTbA8%2F5cOw%3D&reserved=0, or unsubscribehttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPJOGR37GUU3AKEPELCVASLSAGCOFANCNFSM4P3F4EBA&data=02|01|aperales%40moffattnichol.com|b0caee7f423c4f53fb0608d83e21b826|e56883ae3b824b47993a9166c2cff860|1|0|637327661829917187&sdata=RprCjfJ2JL8CfBm7ER0DL0n8iyNy4Gcj%2BOF31fAIeUw%3D&reserved=0.

@aperalesMN
Thank you for the quick response!
I have created a PR to update the documentation and will now close out this issue. Please allow some time for the changes to reflect and if you don't see the document update, please let me know.
I will be more than happy to re-open this issue and look into what happened.
Thank you for your time and patience!


0.1.3 Breaking changes Moved env into env package & more

0.1.3 Breaking changes
Moved env into env package
Moved package vars into env
Added import into vm
Simplified packages
Moved packages testing into vm

Codecov Report

Merging #317 into master will decrease coverage by 1.49%.
The diff coverage is 75.6%.

@@            Coverage Diff            @@
##           master     #317     +/-   ##
=========================================
- Coverage   91.94%   90.45%   -1.5%
=========================================
  Files           9        8      -1
  Lines        2298     2106    -192
=========================================
- Hits         2113     1905    -208
- Misses        122      130      +8
- Partials       63       71      +8

Impacted Files
Coverage Δ

vm/vmExprFunction.go
77% <100%> (ø)
:arrow_up:

vm/vm.go
85.96% <100%> (-0.98%)
:arrow_down:

vm/vmLetExpr.go
86.66% <100%> (ø)
:arrow_up:

vm/vmExpr.go
93.5% <58.82%> (-2.53%)
:arrow_down:

vm/vmStmt.go
95.81% <81.81%> (-1.18%)
:arrow_down:

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 adf6aee...8016764. Read the comment docs.

@mattn Please review and merge

@mattn Any thoughts?

@mattn ?

Sorry. Thank you.


Adobt Quick & Nimble for behaviour-driven testing

Quick is a behavior-driven development framework for Swift and Objective-C.
Inspired by RSpec, Specta, and Ginkgo.
Use Nimble to express the expected outcomes of Swift
or Objective-C expressions. Inspired by
Cedar.

Resolved in b49a0f84948486af415f44c9d5b66a9e4936c76c

Fixed in v3.0.0


Improve the development docs

@mgrauer @yarikoptic Responded to and addressed feedback.

thanks! I just wanted to make sure that nothing "leaked" since title (or PR and the commit where the change is mixed in) said "Improve ... docs". Such descriptions better be placed into the commit messages introducing the changes, that could help later to investigate how the change came about if comes needed.

This brings up a more general question about how hard we want to try to maintain Git hygene. In general, while most of our PRs tend to use branches with reasonable commit messages and squashed local development, I don't think it's something we're enforcing very strongly. We could try to be much more strict about this, but in general, I find code comments to be far more effective at explaining why a change was made and preventing future maintainers from unknowingly changing it.
So, I'll add a comment now to explain why we use port 8085 in the first place (whether specified via --port CLI command or via config file default). Thanks for catching this.

Thank you @brianhelba for raising this.  Well -- I myself isn't "perfect" in commit messages etc, but I think I am getting better since @ kyleam who works with us on DataLad spent too much on git mailing list I guess ;-) so he is our positive encouragement!
To some degree commits actually help to obtain balance in code-vs-comments ratio, since you could add just a brief reasoning in code (if needed to alert future yourself) and then provide a full nice description in the extended commit message.  Also - code changes, and often code comments (if extended) become simply outdated or even contradicting the code.  That cannot happen with git history comments since they relate to that point in time.
On the opposite -- a "dirty git history" (e.g. - a series of commits in a PR fixing up what they just broke until PR is acceptable and merge) complicates code history navigation and even bugs bisection.  Providing no reasoning for a change (in the code it might be out of place) then starts to require more dialogue with an actual human who did the change to figure out "why" ;-)
So I started to tend to use --amend and rebase -i more to bring them up into atomic and more or less well described changes.  It also pretty much forces to re-review the changes, and thus often pick up some bugs or typos.
Altogether, to conclude, I could only repeat my twitter and dandi slack post:
I would recommend to check out review by the current (well -- pretty much "forever") git maintainer Junio: https://github.blog/2020-04-07-celebrating-15-years-of-git-an-interview-with-git-maintainer-junio-hamano/
what made strong influence on me is that  in addition to typical great features decentralized nature of git brings, he brings up the one I had recently quoted in a tweet..:  "that it allows us to completely separate the act of committing and making the result public, and I think that aspect of “distributed”-ness had the biggest impact. It helped imperfect (read: all of us humans) programmers pretend as if they were perfect".

@yarikoptic Thanks for bringing all this up. I think it's an extremely worthwhile discussion, particularly as we create a codebase that needs to have long-term maintainability. Incoming Friday wall of text...

To some degree commits actually help to obtain balance in code-vs-comments ratio, since you could add just a brief reasoning in code (if needed to alert future yourself) and then provide a full nice description in the extended commit message.

I tend to feel the opposite. :smiley: IMO, a full description is most useful right next to the code that it describes. Git is most practically useful to manage the logistics of code, rather than as an authority on the semantics of a given chunk of code. A few years ago, I think I felt differently, as Git (particularly the rationale around atomic commits) markets itself as being the solution to questions of "why is this code here?", but practically, I've found that it's very challenging to rely primarily on Git to provide this.

Also - code changes, and often code comments (if extended) become simply outdated or even contradicting the code.

This can certainly happen, but it's a critical pathology that we need to avoid as developers. Regardless of whether a rationale is in an outdated code comment (which I can easily find the original commit for) or within a previous Git message, a future "code archaeologist" can review the history of changes and reconstruct the reasons for the current code, but this should be a last resort.
IMO, if we're going to hold ourselves to one high standard, it should be to have accurate and useful comments in the code as it is now, rather than to have a pristine history.

On the opposite -- a "dirty git history" (e.g. - a series of commits in a PR fixing up what they just broke until PR is acceptable and merge) complicates code history navigation and even bugs bisection.

Agreed, I think commit hygiene is worth paying some attention to. However, histories will unavoidably get dirty over time. Most significantly, changes to indentation / styling made by automated tools, and file renames are disruptive to history, but we can't be afraid to make these changes because they might break git blame. We don't serve the tools, the tools serve us.

Providing no reasoning for a change (in the code it might be out of place) then starts to require more dialogue with an actual human who did the change to figure out "why" ;-)

Also agreed. I just think this reasoning is better placed in code comments, where it is visible at the time of review as well as obviously visible in the future. With a commit message, you see it at review time, but have to dig for it in the future. Also, future developers need to make a choice to dig through history (even if it's a very clean history), whereas a code comment forces future readers to be confronted with important rationale as they see the code itself.
It's been my experience that most of the time, code that looks bad is actually bad, and should be fixed. However, I've also caused a lot of regressions because I made a "quick fix" to an uncommented line of code that was "obviously wrong", but was actually doing something much more subtle. Do I need to dig through git blame every time I make a change, on the unlikely chance that there was actually a good rationale for some weird code? Wouldn't it be better in the weird-but-important code was just documented as such inline?

So I started to tend to use --amend and rebase -i more to bring them up into atomic and more or less well described changes. It also pretty much forces to re-review the changes, and thus often pick up some bugs or typos.

Agreed. I do this too, and we should encourage it generally. However, one complicating factor is what to do once a code review starts. Do we squash the changes back into the original branch? This makes it very difficult to re-review the changes and figure out what was changed after the first round of feedback. Again, the tools should serve us. I think a good (though admittedly not ideal for the sake of long-term Git hygiene) solution is to fixup your branch as good as possible before pushing, but then don't rewrite history once you create a PR (which is kind of what Git itself traditionally encourages).
However, I'm less certain in my feelings about how to handle branches in response to PR feedback, and I'd really like to know about others' preferences here.


(Alligators) (FP7) (Bug) Getting error while uploading multiple images to School edit (on localhost)

Fatal error: Uncaught Error: Call to undefined function str_contains() in C:\xampp\htdocs\learnandhelp2\school_details.php:113 Stack trace: #0 {main} thrown in C:\xampp\htdocs\learnandhelp2\school_details.php on line 113

I have checked the issue that you're experiencing and found that my localhost does not have error which is the same localhost of the Alligators team. Here, I have attached a screenshot showing successful multiple images uploaded.


Bug: Lualine throws error E903 when opening too many files in tabs

Versions

neovim: v0.7.0
lualine: latest
fugitive: latest
git: v2.36.1

How to reproduce the problem
Method 1:
Open many files (like 40 for example) in buffers and run :bufdo tabnew
OR
Method 2:
Checkout a git branch that has modified over 22 files and run:Git difftool -y main
Either way will reproduce the issue.
Expected behaviour
All tabs are opened and no errors are thrown
Actual behaviour
Neovim is able to open only 22 tabs and the following error gets thrown:
Error detected while processing BufEnter Autocommands for "*":
E5108: Error executing lua Vim:E903: Process failed to start: too many open files:
"/opt/homebrew/bin/git"^@stack traceback:^@^I[C]:
in function 'jobstart'^@^I...pack/packer/start/lualine.nvim/lua/lualine/utils/job.lua:9:
in function 'start'^@^I...rt/lualine.nvim/lua/lualine/components/diff/git_diff.lua:133:
in function 'update_git_diff'^@^I...rt/lualine.nvim/lua/lualine/components/diff/git_diff.lua:121:
in function 'update_diff_args'^@^I[string ":lua"]:1: in main chunk

Weirdly, 22 seems to be the hard cap for this issue.
The only requirements to reproduce: lualine is setup and there are over 22 diffs.
Minimal config to reproduce the issue

Config

require('lualine').setup {
    extensions = {
        'fugitive', -- optional, issue is reproducible even without this line
    },
}

Additional info

When I open multiple tabs with nvim -p $(fzf) the issue does not happen.
When I open multiple buffers and then run :bufdo tabnew the error appears!
The error  appears regardless of whether or not the directory is initialized as a git folder.

Seem like this is a key part of the issue: BufEnter Autocommands for "*"

It feels like we are hitting process/file limit of your system . When new buffers are created we launch a git process to get diff status of associated file. Not sure how to fix it. For now if you have any other plugin that provides git diff like gitsigns you can use source option
as shown here, so lualine uses information for there directly

@shadmansaleh Thank you! I do also have gitsigns.nvim and using it as the diff source for lualine fixes my issue. 🎉
Keeping the issue open for now because it would persist for users without an alternative git diff source.

Oops, I accidentally closed it 😅

hitting the same problem. it essentially prevents me from dong anything 'interesting' on many buffers at once.
don't even have to open tabs. it fails with something as simple as bufdo e. all it does is re-reads files from disk, one after the other. it fails after about 30-40 files.
now.. that limit does indeed seem a bit low, and I'm sure it can be increased somewhere.
but we are ignoring the elephant in the room. why lualine even tries to do anything for buffers that are not attached to the current window? that's a big waste of resources in my opinion. maybe switch from BufEnter to BufWinEnter?

actually tried changing to BufWinEnter, and it didn't help. not sure why ;) looks like bufdo does attach the buffers to the window just without actually showing it in the ui. may be ui is suspended during mass edit operations. I wander if lualine should also stop updating in those cases. it really makes no sense to update git info about tons of buffers that are not shown ...

Maybe this may help you guys
https://gist.github.com/tombigel/d503800a282fcadbee14b537735d202c

use telescope grep to send all files into quickfix list.
run cdo s/foo/bar

This error happened.

for me it was the branchname on display in the lualine, so I added an external source:
https://github.com/nvim-lualine/lualine.nvim/wiki/Component-snippets#using-external-source-for-branch

My previous comment didn't seem to fix it.... whenever I am saving a file after working for a while, I am getting the following:
Error detected while processing BufWritePost Autocommands for "*":
E5108: Error executing lua Vim:E903: Process failed to start: too many open files: "/usr/bin/git"
stack traceback:
        [C]: in function 'jobstart'
        ...l/share/nvim/lazy/lualine.nvim/lua/lualine/utils/job.lua:9: in function 'start'
        ...zy/lualine.nvim/lua/lualine/components/diff/git_diff.lua:133: in function 'update_git_diff'
        [string ":lua"]:1: in main chunk
Press ENTER or type command to continue

Now I am trying to use ulimit -n 10240 per https://github.com/neovim/neovim/issues/14192

The issue arises from one of the refresh events:
https://github.com/nvim-lualine/lualine.nvim/blob/544dd1583f9bb27b393f598475c89809c4d5e86b/lua/lualine.lua#L562
One of these is opening too many files and/or not closing them.
Perhaps reviewing utils/job.lua:9: in function 'start' when called by diff/git_diff.lua:133
Additionally, it is strange that it is trying to refresh the git diff when I don't have any git indicators enabled.

I'm experiencing this issue as well. The only absolutely effective solution is to disable Lualine completely for me. I can get by without it I guess.
I'm on MacOS in case its a MacOS specific issue

If I can get the motivation and time, I would love to contribute and try to fix it up myself

I am going to have to disable it too, eh


fix issue 16319 - 'std.experimental.allocator.make subtly wrong with nested classes'

This also fixes a missing case in std.traits.isInnerClass, recently introduced to allow this change in allocator.make.

Ouch. I should really check the style before pushing...

Current coverage is 88.78% (diff: 91.66%)

Merging #4732 into master will increase coverage by <.01%

@@             master      #4732   diff @@
==========================================
  Files           121        121
  Lines         74140      74152    +12
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          65825      65836    +11
- Misses         8315       8316     +1
  Partials          0          0

Powered by Codecov. Last update bf3669f...6adb44f

Squashed.
Requires @andralex approval.

Ouch. I should really check the style before pushing...

You now should be able to run make -f posix.mak style to execute the style tests directly.

Ouch. I should really check the style before pushing...
You now should be able to run make -f posix.mak style to execute the style tests directly.

Well, this is very good to know. Thanks.

Well, this is very good to know. Thanks.

Yet another advice: if you use the Dlang bot syntax, it will automatically link your issue to this PR, update & close the issue at bugzilla and append the fixed issue to the changelog ;-)
Alternatively you might want to submit a PR to dlang-bot to convert the message to lowercase before applying the regex..

Yet another advice: if you use the Dlang bot syntax, it will automatically link your issue to this PR, update & close the issue at bugzilla and append the fixed issue to the changelog ;-)
Alternatively you might want to submit a PR to dlang-bot to convert the message to lowercase before applying the regex.

You know, I rewrote git history a couple of times trying to get the bot recognize the bugfix, then I gave up. It was my understanding that a commit message containing fix issue xxxxx is enough, but apparently I'm wrong.

You know, I rewrote git history a couple of times trying to get the bot recognize the bugfix, then I gave up. It was my understanding that a commit message containing fix issue xxxxx is enough, but apparently I'm wrong.

Hmm you are right fix issue xxxxx should be a valid pattern, but the fact that it also didn't suggest reviewers for you, might be an indicator that there's an underlying problem.
CC at our awesome dlang-bot guard: @MartinNowak

Well, apparently the auto-tester decided to re-check this PR after I changed the title. Shouldn't this be avoided?
(I think I should ping @braddr about this)

Well, apparently the auto-tester decided to re-check this PR after I changed the title. Shouldn't this be avoided, as no code change happened?
(I think I should ping @braddr about this)

It's probably not a big deal because important PRs get priority over there, but you should ping him or open an issue at https://github.com/braddr/d-tester

I will probably close this in favor of another, more general solution I'm currently working on (should be ready in a couple of hours).

Generally it would be best to just avoid inner anything IMHO. This feature was introduced mostly to simplify porting of Java code, and is significantly complicating the language and its use in non-GC scenarios.

Generally it would be best to just avoid inner anything IMHO. This feature was introduced mostly to simplify porting of Java code, and is significantly complicating the language and its use in non-GC scenarios.
While I agree that in many situations inner classes are not the best solution, we have them, so we must avoid people shooting themselves on the foot when using them.
Also, I think there are a few good uses of this (one example is in my code: https://github.com/lodo1995/experimental.xml/blob/master/source/std/experimental/xml/domimpl.d).

While I have your attention: I'm thinking of moving this fix from allocator.make to emplace, so that it is more general.

Closing in favor of #4734 , which is more general as it solve the issue at is root, that is inside emplace.


Solve issue 'Can not print a resource's fields #144'

Coverage decreased (-0.3%) to 99.718% when pulling f74feaa6a146f5d75649be19528633641accbbaf on jangsutsr:master into cb5b0e24be86906798792ca79a6dbf45ce778e5c on ansible:master.

Coverage decreased (-0.3%) to 99.718% when pulling 926a8627d3fd8f64b272bbd66989305cf5e2c28c on jangsutsr:master into cb5b0e24be86906798792ca79a6dbf45ce778e5c on ansible:master.


Improve federated init, validate reactor program, delimited proto messages

This PR got a little fat...

Improve setup of connection. Now it is done in Environment at assemble. So no need to manually code that.
Fixed some small mistakes in TcpIpChannel receiving if multiple messages were there in the buffer
Use delimted serialize/deserialize
Fix a typo in posix examples
Add a function that validates that the program is correctly set up

@LasseRosenow, I am here providing a initial implementation of your additions to the channel API. I think we should merge this soon before it gets too fat

Thank you for implementing the new NetworkChannelState enum for the TcpIpChannel. It looks good from what I can see.


Migrate IClientInvoker to easier interface

Describe the proposal
Currently the IClientInvoker looks like this:
export default interface IClientInvoker {
  invoke(
    appId: string,
    methodName: string,
    method: HttpMethod,
    data?: object,
    options?: InvokerOptions,
  ): Promise<object>;
}

But we should migrate it to this to have an optional method:
interface IClientInvokerOptions {
    method: HttpMethod,
    data?: object,
    options?: InvokerOptions,
}

export default interface IClientInvoker {
  invoke(
    appId: string,
    methodName: string,
    options: IClientInvokerOptions = {},
  ): Promise<object>;
}

Method can also be optional with a default?
interface IClientInvokerOptions {
    method?: HttpMethod,
    data?: object,
    options?: InvokerOptions,
}

Yep! Will define it in InvokerOptions as follow
import HttpMethod from "../enum/HttpMethod.enum";
import { KeyValueType } from "./KeyValue.type";

/**
 * Options related to service invocation.
 */
export type InvokerOptions = {
  /**
   * The HTTP method to use when invoking the service.
   */
  method?: HttpMethod;

  /**
   * The data to send to the service.
   */
  data?: object;

  /**
   * Headers to include in the service invocation request.
   * Note, this is ignored when using the gRPC protocol.
   */
  headers?: KeyValueType;
};

SHould be tackled by #442


Fix remote-client testing reports

Ensure when using remote attach --no-stdin a mock device is used to
prevent stdin and not nil.  This fixes issue #3009.
When starting a container with the remote client, if the container is
already running and the user asks to attach, we should just attach.
This fixes issue #3011
Signed-off-by: baude<EMAIL_ADDRESS>

LGTM

@rhatdan @giuseppe @TomSweeneyRedHat PTAL

/lgtm


Settings - Timezone is highlighted with a blue background

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to URL https://staging.new.expensify.com
Login with any account
Navigate to Settings > Profile
Click Timezone

Expected Result:
The timezone in the search field should not be highlighted
Actual Result:
Timezone is highlighted with a blue background
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] Windows / Chrome

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/210880425-89397bb8-b183-4c2e-a9df-fd409a0e3cb2.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01af8ef889509b6e67
Upwork Job ID:<PHONE_NUMBER>362830848
Last Price Increase: 2023-01-05

I think this is the expected behavior. You can see the same behavior in the PR that introduced this feature ~1 month ago.

Closing. Please reopen if this is not expected!


docs: fix typos in approach and placeholders

made corrections to the typos i have found in the documentations.

Nice catch, thanks 👌

Thanks 😊


Pack Error

I run npm run build and npm pack, a tgz file will be generated
Then I run npm install in playground forder to install it and npm run docs:dev
Errors occur:

><EMAIL_ADDRESS>docs:dev
> vuepress dev docs --clean-cache

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of URL. Received undefined
    at new NodeError (node:internal/errors:372:5)
    at fileURLToPath (node:internal/url:1420:11)
    at Object.<anonymous> (C:\Users\sshu\Desktop\vuepress2-plugin-full-text-search\playground-for-2.0.0-beta.43\node_modules\vuepress2-plugin-full-text-search\lib\index.cjs:150:45)
    at Module._compile (node:internal/modules/cjs/loader:1105:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (C:\Users\sshu\Desktop\vuepress2-plugin-full-text-search\playground-for-2.0.0-beta.43\docs\.vuepress\config.js:11:14)

Then I try it in another project, this also happens. However, installing it from online npm is ok. How can I solve this problem?

I can't reproduce your problem.
If we build on Windows, can the build files be different? I don't have Windows so I can't check it.

I can't reproduce your problem. If we build on Windows, can the build files be different? I don't have Windows so I can't check it.

I remove the plugin from the package.json and  remove the import, then npm install, then re-add it to the package.json and npm install. The error won't happen. Thanks.


Pulsar functions not found - Windows

Hubble on Windows 10  - Pulsar functions not found:
2019-02-19 11:08:58 [hubblestack.daemon][ERROR   ] Scheduled job pulsar has a function pulsar.process which could not be found.
2019-02-19 11:09:08 [hubblestack.daemon][ERROR   ] Scheduled job pulsar_canary has a function pulsar.canary which could not be found.
Default install/config. Only Splunk info added to config.

Thanks for the report. I'm going to have @Tenebriso look into this.

https://jira.corp.adobe.com/browse/CSTTEAM-44494

I cannot access: https://jira.corp.adobe.com/browse/CSTTEAM-44494 because Secure Connection Failed SSL_ERROR_HANDSHAKE_FAILURE_ALERT
I've tried using Firefox; IE and Edge to no avail...

This is fixed in https://github.com/hubblestack/hubble/pull/601

(Also, note that those jira links are unfortunately to our instance behind Adobe VPN, so they will not be visible to non-Adobe employees.)


Template Rendering fails if jobs.X.properties is empty

If jobs.X.properties is empty, and properties are specified as global properties at properties, all templates fail to render, with the error
/Users/gfranks/.bosh_init/installations/75405607-60e3-4374-5184-d210368f0c72/tmp/erb-renderer806083022/erb-render.rb:11:in `merge!': no implicit conversion of nil into Hash (TypeError)
    from /Users/gfranks/.bosh_init/installations/75405607-60e3-4374-5184-d210368f0c72/tmp/erb-renderer806083022/erb-render.rb:11:in `recursive_merge!'
    from /Users/gfranks/.bosh_init/installations/75405607-60e3-4374-5184-d210368f0c72/tmp/erb-renderer806083022/erb-render.rb:31:in `initialize'
    from /Users/gfranks/.bosh_init/installations/75405607-60e3-4374-5184-d210368f0c72/tmp/erb-renderer806083022/erb-render.rb:188:in `new'
    from /Users/gfranks/.bosh_init/installations/75405607-60e3-4374-5184-d210368f0c72/tmp/erb-renderer806083022/erb-render.rb:188:in `<main>'

Adding an empty map to the job-specific properties key resolves this. This key is not required for traditional bosh deploys, so it feels like this should be allowed in bosh-init as well.
Failing manifest excerpt:
jobs:
- instances: 1
  name: bosh
  networks:
  - name: default
    static_ips:
    - <IP_ADDRESS>
  persistent_disk_pool: bosh
  resource_pool: bosh
  templates:
  - name: postgres
    release: bosh
  - name: nats
    release: bosh
  - name: redis
    release: bosh
  - name: blobstore
    release: bosh
  - name: director
    release: bosh
  - name: health_monitor
    release: bosh
  - name: vsphere_cpi
    release: bosh-vsphere-cpi
properties:
  agent:
    mbus: nats://nats:nats-password@<IP_ADDRESS>:4222
  ... (remaining properties omitted for brevity)

Working manifest excerpt:
jobs:
- instances: 1
  name: bosh
  networks:
  - name: default
    static_ips:
    - <IP_ADDRESS>
  persistent_disk_pool: bosh
  resource_pool: bosh
  templates:
  - name: postgres
    release: bosh
  - name: nats
    release: bosh
  - name: redis
    release: bosh
  - name: blobstore
    release: bosh
  - name: director
    release: bosh
  - name: health_monitor
    release: bosh
  - name: vsphere_cpi
    release: bosh-vsphere-cpi
  properties: {}
properties:
  agent:
    mbus: nats://nats:nats-password@<IP_ADDRESS>:4222
  ... (remaining properties omitted for brevity)

Just ran into this when trying to use bosh create-env to deploy a NAT box.
Also recently came up on slack, although didn't fully diagnose it to this exact issue.

Also ran into the same problem recently. Problem seems to be a very restrictive check in erb rendering: https://github.com/cloudfoundry/bosh-init/blob/a26a88ad318c816ac42cc63368f7ea0bc7ea40b6/templatescompiler/erbrenderer/template_evaluation_context_rb.go#L33-L37


Custom icon for maximized stated

We show now the following icon on full screen:

to switch back to normal window size.

:+1:

Coverage remained the same at 89.335% when pulling 07f6a6c639e71065a58c2b13e63a36093799e504 on FinalAngel:feature/modal into dfa1f8eea1fb0a49c6e8caa779c086349b77cbf1 on divio:develop.

Coverage remained the same at 89.335% when pulling 07f6a6c639e71065a58c2b13e63a36093799e504 on FinalAngel:feature/modal into dfa1f8eea1fb0a49c6e8caa779c086349b77cbf1 on divio:develop.


Linkable search results

Sometimes I want to link to the search results page in Slack. It would nice if the URL would be updated to reflect the current search term.

This would be great for SEO as we could let Google know that we have the feature like this:
<script type="application/ld+json">
  {
    "@context": "http://schema.org",
    "@type": "WebSite",
    "url": "https://www.prisma.io/docs/",
    "potentialAction": {
      "@type": "SearchAction",
      "target": "https://www.prisma.io/search?q={search_term_string}",
      "query-input": "required name=search_term_string"
    }
  }
</script>

Still very much needed.

@janpio Check out this new PR: #3556


Add CWE Catalog importer, daily interval.

Clean up some typos.
Regenerate OpenAPI.

since this importer processes exactly 1 fetched-over-http file (using Last-Modified header to determine continuationing), a lot of the nested Walker/Handler/Context stuff simplified out.


Azure-Sentinel/Playbooks/Prompt-User/incident-trigger/

Describe the bug
Can't create the "Prompt-User-Incident" Playbook from the Repository.
The Deployment goes in to a error:
Deployment Failed
{
"status": "Failed",
"error": {
"code": "InvalidTemplate",
"message": "The template validation failed: 'The template action 'Post_a_message_(V3)' at line '1' and column '2285' is not valid: "The template language expression 'sanitized' is not valid: the string character 'f' at position '24' is not expected.".'."
}
}
To Reproduce
Steps to reproduce the behavior:

Go to 'Microsoft Sentinel\Automation\Playbook template (preview)'
Click on 'Prompt User - Incident\ Create playbook'
Scroll down to '.. Add Teams AD and Chanel ID....'
See error

Screenshots
I

Hi @BenjiSec
I am getting a similar error, but in another part of the code...:
{
"status": "Failed",
"error": {
"code": "InvalidTemplate",
"message": "The template validation failed: 'The template action 'Post_a_message_(V3)' at line '1' and column '2256' is not valid: "The template language expression 'sanitized' is not valid: the string character '%' at position '21' is not expected.".'."
}
Br
Mela

totally right, I can confirm, from github is working.
Thanks


Enabling/Disabling maintenance flag while upgrade and post-upgrade

Signed-off-by: Yashvi Jain<EMAIL_ADDRESS>:nut_and_bolt: Description: What code changed, and why?
A prompt is giving to the user is they are ready to put automate in maintenance mode while starting the upgrade.
When the user run 'post-upgrade migration' command we disable the maintenance mode.

:chains: Related Resources
https://chefio.atlassian.net/jira/software/c/projects/STALWART/boards/361?modal=detail&selectedIssue=STALWART-202
:+1: Definition of Done

Enable the maintenance mode as a part of checklist
if some errors occurs while having checklist, if the user has already enabled the maintenance mode disable it
If some errors occurs while upgrading, a warning is shown to disable the mode.
At the time of starting post-upgrade step, disable the maintenance mode.

:athletic_shoe: How to Build and Test the Change

Deploy chef-automate using new bin
Start the upgrade process
chef-automate config show
Run Post Upgrade step

:white_check_mark: Checklist
All PRs must tick these:

[X] I have read the CONTRIBUTING document.
[X] All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

[X] Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
[X] Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
[X] Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
[X] Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
[X] Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

[ ] Tests added/updated? (all new code needs new tests)
[ ] Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.
:camera: Screenshots, if applicable

https://user-images.githubusercontent.com/91940132/190321283-700c8669-b00c-42ae-8a7e-207fc523f6fb.mov