Disregard "fake" changes (only modified timestamp)

Timestamp might be harvest-time, not an actual change

Fixed by https://github.com/Informasjonsforvaltning/fdk-dataset-harvester/pull/129


Dynamic columns in Grid List

Bug, feature request, or proposal:
Feature:
Have the number of columns in a GridList component change in response
to significant changes to screen/browser dimensions.
What is the use-case or motivation for changing an existing behavior?
While it is relatively straight-forward to determine the initial number of
columns that is optimal for displaying a Gridlist component on the current
device/browser. It is much more difficult to respond to signficant changes
in media size.
Is there anything else we should know?
I am already looking into this. If successful, I would be happy to share.
David Aspinall

@Exertive You should probably have a look at @angular/flex-layout.

Thanks dahaupt. That is what I am now doing. It serves my purpose perfectly.

Dupe of #1072 which we do plan to support eventually


2.1 branch fix getLine hangs

Cherry-picked issue #137 for 2.1 branch of pheanstalk.

oops, wrong remote


Nested collections root index.md long saving time

Hi all,
When using Nested Collections with 11ty, and a larger site, the root index.md file takes an age to save.
Upon investigation, it seems as when triggering a publish, it sends a POST request to /.netlify/git/github/git/trees, which includes a payload of a tree of every file on the same level as that root index.md (which is the whole site).
This obviously is a standard setup for sites using 11ty, but wondered if this was a bug. Obviously, as a workaround I can move the root index.md file to a subfolder, and change the permalink, but then the client loses control of the path within Netlify.
Any advice is much appreciated - thanks!

Closing as stale

I have come across this issue again today - just an FYI.

@ryangittings ok, reopening.


[BEAM-8224] Fix bug in _fn_takes_side_inputs (#9563)

cherrypick of https://github.com/apache/beam/pull/9563

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @markflyhigh

LGTM

The docs task failure is being handled in #9620. Cython failure is not related to this change and integration test is caused by dataflow service. This change is fully tested when merging to master so should be safe to cherry-pick.


fix: resolve conflicting packages; address linting issues; resolve "@…

…/" aliases in generated types
Addressing the type aliasing issue mentioned in https://github.com/ghalex/vue3-charts/issues/33.
On the way through, noticed and cleared up a few things:

package conflicts that were borking install
linting errors -- I've cleared up errors and warnings

Hi @mdodsworth,
Thank you for taking the time to help, I will have a look at the changes and approve them.
Thanks,
Alexandru


poa-logrotate refactor

As we get rid of root activities (#125) it will be a good idea to rewrite poa-logrotate role to use cron module instead of creating scripts (template module) in /etc/cron.hourly/ directory. It will allow us to install user-specific crontab, that will rotate logs in user's folder.

Closed because of #136


⚠ Bofrost.at has degraded performance

In 464cc19, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 983 ms

Resolved: Bofrost.at performance has improved in b223013.


PEP 557

What's our added value? Should we rebase on https://github.com/ericvsmith/dataclasses?

I have the strong feeling that we should at least rebase our current implementation over types.SimpleNamespace, which is there since Python 3.3, but I need to dig into this a bit more.

As discussed in my EuroPython (then Pycon FR) talk, there's place for both.


Remove "Trusted Resources" tabs

The Trusted AI Resources and Trusted AI Providers are no longer required.

Done

The tabs are still visible for me:

@geverit4 I think the deploys are failing

Confirmed removed on test


Cant close in Linux

Godot version
4.2.-6
System information
Godot v4.2.beta6.mono - Fedora Linux 39 (KDE Plasma) - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 6600 (RADV NAVI23) () - AMD Ryzen 7 5700G with Radeon Graphics (16 Threads)
Issue description
After open the engine, close the program, keeps open until force to close with a task manager. The thing, in the previous versions 4.2-1 to 4.2-4, works fine.
Steps to reproduce
Open a project, then close the program.
Minimal reproduction project
Just open a new project.

Thanks for your report! This is a known issue with the mono builds and it will be fixed in the next official build (it's already fixed in master). See https://github.com/godotengine/godot/issues/84728.


Bugfix/mapper fixes

added db name property to generated entities
based annotation are now also resolved for base models
fixed wrong type resolved issue for mapper

Codecov Report

Merging #44 (69e96e0) into master (e98a2c5) will increase coverage by 0.07%.
The diff coverage is 50.00%.

@@             Coverage Diff              @@
##             master      #44      +/-   ##
============================================
+ Coverage     69.83%   69.91%   +0.07%
- Complexity      374      377       +3
============================================
  Files            54       54
  Lines          1263     1273      +10
  Branches        219      220       +1
============================================
+ Hits            882      890       +8
- Misses          261      262       +1
- Partials        120      121       +1

Impacted Files
Coverage Δ

...java/com/kaufland/processing/model/ModelWorkSet.kt
77.27% <0.00%> (-7.73%)
:arrow_down:

.../src/main/java/com/kaufland/model/EntityFactory.kt
75.43% <20.00%> (+0.89%)
:arrow_up:

...com/kaufland/generation/mapper/MapperGeneration.kt
61.48% <100.00%> (+0.26%)
:arrow_up:

.../com/kaufland/generation/model/EntityGeneration.kt
89.09% <100.00%> (+0.10%)
:arrow_up:

...ain/java/com/kaufland/model/entity/EntityHolder.kt
100.00% <100.00%> (ø)

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 e98a2c5...69e96e0. Read the comment docs.


trigger custom click handler upon marker click

It would be useful to have a custom click handler fired when the user clicks a marker, so developers will be able to run their own code when that happens.
To use this implementation simply add a "onMarkerClicked" field (function type) to a marker JSON, for example:
player.markers.add([{
  time: 1,
  text: "ABC",
  onMarkerClicked: function() { console.log("marker clicked"); }
}]);

And then maybe a return of false from that would prevent the default behaviour of jumping to that point in the video.

On 9 Apr 2015, at 10:15, ereztison<EMAIL_ADDRESS>wrote:
It would be useful to have a custom click handler fired when the user clicks a marker, so developers will be able to run their own code when that happens.
To use this implementation simply add a "onMarkerClicked" field (function type) to a marker JSON, for example:
player.markers.add([{
time: 1,
text: "ABC",
onMarkerClicked: function() { console.log("marker clicked"); }
}]);
You can view, comment on, or merge this pull request online at:
https://github.com/spchuang/videojs-markers/pull/13
Commit Summary
trigger custom click handler upon marker click
recompiling dist
File Changes
M dist/videojs-markers.js (5)
M dist/videojs-markers.min.js (4)
M dist/videojs.markers.min.css (5)
M src/videojs.markers.js (3)
Patch Links:
https://github.com/spchuang/videojs-markers/pull/13.patch
https://github.com/spchuang/videojs-markers/pull/13.diff
—
Reply to this email directly or view it on GitHub.

I would also rename the callback to simply "onClicked".
The function onMarkerClicked could take "marker" as the parameter to have access to marker time and text.
In regards to @tjenkinson's comment on preventing default click behavior, I think using the return value of onMarkerClicked for that intent is confusing. I would suggest adding a new property for marker. Something like "preventDefaultClickGoto," (if you have a better naming, please use it instead!)

Thanks @spchuang for the feedback, I updated the pull request with your suggestions.
Regarding preventing default click behaviour I tend to agree with @tjenkinson, returning false seems like [a jQuery practice] (http://stackoverflow.com/questions/1357118/event-preventdefault-vs-return-false) so I guess many developers are familiar with it, it also allows for determining if to cancel the event or not dynamically during the callback execution in a more straight forward manner.
There is also the event.preventDefault() javascript practice which is similar to what you suggested but with the difference it is invoked on the event rather than the marker.
My personal flavour is the "return false" though, but that's only my suggestion :)

@ereztison, okay let's go for the "return false" approach.
Thanks for the update!


Rewrite documentation to recommend Docker.

Resolves https://github.com/frewsxcv/afl.rs/issues/57.

This is not an ideal flow, but it's at least reliable.
Possibility for the future: Instead of running a shell within the Docker environment, it might be sufficient to just cargo build and cross compile to the host architecture so the user can run afl-fuzz locally.


[feature] V2 Migration Guide

Is your feature request related to a problem? Please describe.
We would like to migrate to the latest version of this package (2.x.x) but there is no migration guide and we can't find any examples of how to use the new components with "composition" and move away from class inheritance .
Describe the solution you'd like
A V1 to V2 migration guide or some clear examples of how to use features such as Page and ResponsiveGrid
Describe alternatives you've considered
We have trawled through changelogs, release logs, PRs and unit tests but it is still not clear how to migrate from V1 effectively
Additional context
As a direct example, how would we pass the author components down, like we do for class components with "this.childComponents"
class GenericCmsPage extends Page {
  render() {
   ...
     {this.childComponents}
   ...
  }
}

@maximilianvoss @gabrielwalt FYI

Heya. Any updates on this?
Another query we have is: is there a way to disable the placeholder for certain components in the new world?

Would be really useful to have such examples.
If there is no docs at the moment, some code example would be enough

Any updates on this?

Doesn't seem like a guide is coming anytime soon. Has anyone been successful with extending Page in version 2.0? I'm running into the same issue of OP after upgrade.

Hey Chris,
Thanks for your response! I was able to stumble through and get components
rendering from that approach. I'm noticing that now that after opening a
Page, there is an extra placeholder Grid container added. I tried the same
approach with ResponsiveGrid in the containers. Did you face any
similar issues with the page itself?
On Tue, Mar 21, 2023 at 1:02 PM Chris Wiseman @.***>
wrote:

Hey @jwolfe890 https://github.com/jwolfe890
We have successfully upgraded to V2 but it was a lot of trial and error.
We were given this NextJS example but we didn't find it too useful as it
was not using Typescript and the examples are very basic:
https://github.com/adobe/aem-nextjs-template.
In the example I originally posted, the code would change to
const GenericCmsPage = (props) => {
return (
...
<Page {...props} />
...
)
}
Props being AEM data, childComponents etc.
Each component also needs to be wrapped with EditableComponent where the
config is passed (instead of passing the config to MapTo previously)
    <EditableComponent config={config}>
      <Component {...props} />
    </EditableComponent>

There is a bit of info on it here:
https://github.com/adobe/aem-react-editable-components/tree/master/src/components
And some documentation here:
https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/spa-editor/how-to/react-core-components-v2.html?lang=en
It has been a while since we worked on this is off the top of my head but
let me know if you have any other questions and maybe I can answer or point
in the right direction.
—
Reply to this email directly, view it on GitHub
https://github.com/adobe/aem-react-editable-components/issues/141#issuecomment-1478358449,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADFLI5E2RCMEUJF6HMP4O6DW5HUKBANCNFSM6AAAAAARUGHBKQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @cjwiseman11 , @jwolfe890
I have integrated Next.js using the remote spa editor and v2 components.
But the SPA editor is working a bit off, once I create a new page, in edit mode, component placeholders are not showing up -> I need to switch to preview and back to edit mode to be able to edit components.
Another thing is once I add the same component twice in a container / responsive grid, for the first component placeholder is rendered, and for the component, the placeholder doesn't show up -> page reload is needed to get this working.
Did you have similar issues?
This is what AemPage looks like, I can't just pass props, since some of the objects such as cqChildren don't exist in page.model.json
Also, I need to have 2 different types of pages based if I'm rendering nextjs inside AEM author, and different once Next.js is directly used.
export default function AemPage(props) {
    const getPage = () => {
        let page;

        if (isAuthor()) {
            page = (
                <Page cqChildren={props[Constants.CHILDREN_PROP]}
                      cqItems={props[Constants.ITEMS_PROP]}
                      cqItemsOrder={props[Constants.ITEMS_ORDER_PROP]}
                      cqPath={props[Constants.PATH_PROP]}/>
            );
        } else {
            page = (
                <Page cqChildren={props[Constants.CHILDREN_PROP]}
                      cqItems={props[Constants.ITEMS_PROP]}
                      cqItemsOrder={props[Constants.ITEMS_ORDER_PROP]}
                      model={props}
                      pagePath={props[Constants.PATH_PROP]}
                      itemPath={props[Constants.PATH_PROP]}/>
            );
        }

        return page;
    }

    return (
        getPage()
    );
}

Hi @cjwiseman11 , @jwolfe890
I have integrated Next.js using the remote spa editor and v2 components. But the SPA editor is working a bit off, once I create a new page, in edit mode, component placeholders are not showing up -> I need to switch to preview and back to edit mode to be able to edit components.
Another thing is once I add the same component twice in a container / responsive grid, for the first component placeholder is rendered, and for the component, the placeholder doesn't show up -> page reload is needed to get this working.
Did you have similar issues?
This is what AemPage looks like, I can't just pass props, since some of the objects such as cqChildren don't exist in page.model.json
Also, I need to have 2 different types of pages based if I'm rendering nextjs inside AEM author, and different once Next.js is directly used.
export default function AemPage(props) {
    const getPage = () => {
        let page;

        if (isAuthor()) {
            page = (
                <Page cqChildren={props[Constants.CHILDREN_PROP]}
                      cqItems={props[Constants.ITEMS_PROP]}
                      cqItemsOrder={props[Constants.ITEMS_ORDER_PROP]}
                      cqPath={props[Constants.PATH_PROP]}/>
            );
        } else {
            page = (
                <Page cqChildren={props[Constants.CHILDREN_PROP]}
                      cqItems={props[Constants.ITEMS_PROP]}
                      cqItemsOrder={props[Constants.ITEMS_ORDER_PROP]}
                      model={props}
                      pagePath={props[Constants.PATH_PROP]}
                      itemPath={props[Constants.PATH_PROP]}/>
            );
        }

        return page;
    }

    return (
        getPage()
    );
}

More info here #145
Do you use ResponsiveGrid? How are you rendering your containers? I had Page issues, but not in the way you're describing. The component placeholders are appearing fine, I just get an unneeded one. NextJS I imagine is a different animal though.

I have responsive grid component in AEM template structure, and by only using React Page component, responsive grid is mapped correctly and rendered in Nextjs.
Do you use responsive grid / container from this aem-react-editable-components, or do you extend it and map it to your AEM component?

I have responsive grid component in AEM template structure, and by only using React Page component, responsive grid is mapped correctly and rendered in Nextjs.
Do you use responsive grid / container from this aem-react-editable-components, or do you extend it and map it to your AEM component?

I've the same error here, I've the grid component in aem template structure, but it's not rendering, basically Page component is rendering on Editor Mode, and also on the preview mode, but I'm not able to see the drag and drop placeholder and things from ResponsiveGrid. This is just a question, is it possible that acs-common package is impacting in this issue? or maybe with https://github.com/adobe/aem-core-wcm-components .

Hey
Apologies for not getting back it has been crazy busy lately. Also it has been a while since I worked on this but hopefully I can try and help with some of the questions.

I'm noticing that now that after opening a
Page, there is an extra placeholder Grid container added. I tried the same
approach with ResponsiveGrid in the containers. Did you face any
similar issues with the page itself?

I'm not sure what you mean by this exactly but basically wherever we had a class extending "ResponsiveGrid" we would refactor to passing the props into <ResponsiveGrid {...props} />

class CmsAccordion extends ResponsiveGrid

<ResponsiveGrid {...props} />

Any extends Pages would pass props to <Pages {...props} />
(props being the AEM component data)

I need to switch to preview and back to edit mode to be able to edit components.

I believe you need EditableComponent wrapped for the component placeholder?
Our top level looked like this:
      <EditableComponent {...model}>
        <MappedPage
          cqItems={cqItems[Constants.ITEMS_PROP]}
          cqItemsOrder={cqItems[Constants.ITEMS_ORDER_PROP]}
          cqPath={ModelManager.rootPath}
          navigation={navigation}
          pageTitle={pageTitle}
          title={title}
          hideTitle={hideTitle}
          breadcrumbs={breadcrumbs}
        />
      </EditableComponent>

Anything for author has to be wrapped with EditableComponent

I just get an unneeded one
We had some places where we didn't need the additional placeholder.. I believe we fixed it with a prop

isInEditor={showPlaceholder}

Our top level looked like this:
      <EditableComponent {...model}>
        <MappedPage
          cqItems={cqItems[Constants.ITEMS_PROP]}
          cqItemsOrder={cqItems[Constants.ITEMS_ORDER_PROP]}
          cqPath={ModelManager.rootPath}
          navigation={navigation}
          pageTitle={pageTitle}
          title={title}
          hideTitle={hideTitle}
          breadcrumbs={breadcrumbs}
        />
      </EditableComponent>

So I have Page react component which is mapped to AEM Page component
import React from 'react';
import {Page, MapTo, EditableComponent} from '@adobe/aem-react-editable-components';

function ContentPage(props) {
    return (
        <EditableComponent {...props}>
            <Page {...props} />
        </EditableComponent>
    )
}

export default MapTo('wknd-spa-nextjs/components/remotepagenext')(ContentPage);

import React from 'react';
import {Constants} from "@adobe/aem-spa-page-model-manager";
import {getPageModel} from "../utils/SSRUtils";
import {isAuthor} from "../utils/EnvironemntUtils";
import ContentPage from "../components/page/ContentPage";

export default function AemPage(pageModel) {
    const getPage = () => {
        if (isAuthor()) {
            //cqPath is needed, otherwise authoring doesn't work
            return (
                    <ContentPage cqChildren={pageModel[Constants.CHILDREN_PROP]}
                          cqItems={pageModel[Constants.ITEMS_PROP]}
                          cqItemsOrder={pageModel[Constants.ITEMS_ORDER_PROP]}
                          cqPath={pageModel[Constants.PATH_PROP]}
                          model={pageModel}
                    />
            );
        } else {
            //todo:
            // cqPath has wrong value when when SSR is enabled
            return (
                    <ContentPage cqChildren={pageModel[Constants.CHILDREN_PROP]}
                          cqItems={pageModel[Constants.ITEMS_PROP]}
                          cqItemsOrder={pageModel[Constants.ITEMS_ORDER_PROP]}
                          model={pageModel}
                          pagePath={pageModel[Constants.PATH_PROP]}
                          itemPath={pageModel[Constants.PATH_PROP]}
                          {...pageModel}
                    />
            );
        }
    }

    return (
        getPage()
    );
}

export async function getServerSideProps(context) {
    return await getPageModel(context);
}

@cjwiseman11 I still have funny behavior in the editor. I need to switch from Edit to Preview and back to Edit mode.
Also if in edit mode I drag and drop 2 times some components, 2nd component is not visible (also in the Content tree in sidekick) with a refresh of the page component appearing.
Can you tell me which props should be passed to the Page component from this library? As you can see that I'm having 2 versions (one for author, one for delivery) to get somehow this "working"

Hey Chris, Thanks for your response! I was able to stumble through and get components rendering from that approach. I'm noticing that now that after opening a Page, there is an extra placeholder Grid container added. I tried the same approach with ResponsiveGrid in the containers. Did you face any similar issues with the page itself?
…
On Tue, Mar 21, 2023 at 1:02 PM Chris Wiseman @.> wrote: Hey @jwolfe890 https://github.com/jwolfe890 We have successfully upgraded to V2 but it was a lot of trial and error. We were given this NextJS example but we didn't find it too useful as it was not using Typescript and the examples are very basic: https://github.com/adobe/aem-nextjs-template. In the example I originally posted, the code would change to const GenericCmsPage = (props) => { return ( ... <Page {...props} /> ... ) } Props being AEM data, childComponents etc. Each component also needs to be wrapped with EditableComponent where the config is passed (instead of passing the config to MapTo previously)  <Component {...props} />  There is a bit of info on it here: https://github.com/adobe/aem-react-editable-components/tree/master/src/components And some documentation here: https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/spa-editor/how-to/react-core-components-v2.html?lang=en It has been a while since we worked on this is off the top of my head but let me know if you have any other questions and maybe I can answer or point in the right direction. — Reply to this email directly, view it on GitHub <#141 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADFLI5E2RCMEUJF6HMP4O6DW5HUKBANCNFSM6AAAAAARUGHBKQ .  I too have similar issue after upgrading to V2.
Please let me know the approach you followed to avoid the duplicate placholder on page.


Can a role have another role as role?

Description of the issue
organizational energy producer is a subclass of 'has role' some producer. Is this intended? Both organizational energy producer and producer are subclasses of role. Can a role have another role as role?
Ideas of solution
If a role cannot have another role as a role (I am not sure about it) then organizational energy producer should be a subclass of producer.
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

No, roles can't have roles.   It seems to me that 'organisational energy producer' should definitely be subClassOf 'producer'.

I'll fix it

if we do that we have two parents of organizational energy producer: organization and producer. Is this acceptable in this case?

This also questions the definition of agent: "Agent is a role of a person or organization that directs it's activity towards achieving goals."
Here the role "agent" is defined as a role of person or the role "organization", again a role of a role.
We wanted to include a society in another issue though so maybe this can replace organization in the definition?

The challenge is that legally, an organisation can bear (some) roles, because it becomes a legally recognised entity equivalent (in some ways) to a person. This institutionalised form of an organisation does not fully behave like a role, because it continues to exist even if there are no independent entities that are bearing the role, even though, in many other ways organisations do behave like roles.
I think the definition and classification of organisation is the weak element here.
One possibility to solve is to separate out two distinct entities "organisation role" and "organisation", as an independent entity, defined as "independent continuant and has_role some organisation role". The latter can then bear roles, including by definition the organisation role but also agent role, producer role, etc.

that sounds good, I'll implement it

@jannahastings directly as independent continuant? Or as material/ immaterial etc?

It is definitely not material.
Nor is it a boundary, site, region or any of the other sorts of immaterial entity that are mentioned so far. But perhaps we can put it under immaterial entity nevertheless.
We may want to refer, in the definition, to there needing to be some sort of legal framework that recognises the entity and its continued existence.

yes. Will organizational energy producer than be a subclass of that independent entity "organization" instead?

We may want to refer, in the definition, to there needing to be some sort of legal framework that recognises the entity and its continued existence.

then not everything with the organization role is an organization or do we add this directly to the organization role?

Will organizational energy producer than be a subclass of that independent entity "organization" instead?

I think yes, and this is the superclass that we agreed in the original issue introducing organisational energy producer. So we can keep the relationship has_role producer, and we avoid having a role that has a role.

then not everything with the organization role is an organization or do we add this directly to the organization role?

I think that not everything with an organisation role -- by our current definition of organisation role (a role depending on a society that has a collective goal and a set of organization rules) is an organisation in the legal sense that would allow it to bear other roles such as being itself an agent.

Are there other ontologies having faced the same problem (organisation vs. organisation role)? How did they solve it?

Yes, this is an ongoing discussion in several ontologies. You can see some notes annotated in the organization class in the Ontology for Biomedical Investigations here: http://www.ontobee.org/ontology/OBI?iri=http://purl.obolibrary.org/obo/OBI_0000245. I would not say that it has been solved by any ontologies yet. However, the compromise OBI has adopted is similar to what we are proposing here.

As PR #421 was merged: Should we close this issue? Or move it to the next release?

I think we can close this one as the role no longer has a role.


Indexer Subsystem

[x] List of Inputs (Sensors)
[x] List of Outputs (Motors, Pneumatics)

[x] RobotMap

[ ] List of Actions (Commands)
[ ] Integrate Commands into Robot class

Indexer is fully functional, closing this.


[CI] Passing -Pspark.version to gradle still runs tests for all Spark versions

For example, tests are executed in parallel CI jobs with options -Pspark.version=2.4.8 and -Pspark.version=3.2.4. But both of jobs execute :spark2:tests, :spark32:tests, :spark34:tests and so on:

https://app.circleci.com/pipelines/github/OpenLineage/OpenLineage/9954/workflows/1cadbd7c-4acd-4eca-8292-25c5247c1d46/jobs/197776/parallel-runs/0/steps/0-106
https://app.circleci.com/pipelines/github/OpenLineage/OpenLineage/9954/workflows/1cadbd7c-4acd-4eca-8292-25c5247c1d46/jobs/197781/parallel-runs/0/steps/0-106

Can Gradle or CI config can be changed to run tests only for specific Spark version? This can speed up the tests.
Somewhat related - each run of tests in CI also runs linter which apparently does not depend on Spark version, so it can be run just once.

The logic Maciej describes comes from builder classes like (this one)[https://github.com/OpenLineage/OpenLineage/blob/main/integration/spark/app/src/main/java/io/openlineage/spark/agent/lifecycle/Spark34DatasetBuilderFactory.java]
In this particular case, spark34 builder factory has following imports:
import io.openlineage.spark32.agent.lifecycle.plan.AlterTableCommandDatasetBuilder;
import io.openlineage.spark33.agent.lifecycle.plan.ReplaceIcebergDataDatasetBuilder;
import io.openlineage.spark34.agent.lifecycle.plan.column.CreateReplaceInputDatasetBuilder;
import io.openlineage.spark35.agent.lifecycle.plan.CreateReplaceOutputDatasetBuilder;

I don't think it is doable to have dependency logic replicated in CI and consistent with DatasetBuilderFactory classes.

I see.
I've tried to run ./gradlew :spark2:tests specifically, and it took only 23 seconds. So making CI to run only tests for some specific Spark version actually will not speed up tests much.
Don't mind if I close the issue?


Add AppProvider

Adds AppProvider – this is an abstraction that encapsulates the application creation and respective setup
There are two implementations:

DefaultAppProvider – is the default application instance and should be the one used for normal application instantiation
TestAppProvider – provides application instance given a TestingModule – providing any other module would result in a rejected Promise

These two implementation share the same setup steps – this allows us to write tests that will use the same configuration applied in the production instance. The configuration steps are set under DEFAULT_CONFIGURATION. This configuration is provided to the instances so that it can be changed (e.g. a testing instance might want to remove a configuration step)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

20 of 26 (76.92%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.3%) to 89.169%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main.ts
0
2
0.0%

src/app.provider.ts
20
24
83.33%

Files with Coverage Reduction
New Missed Lines
%

src/main.ts
2
0%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
310

Relevant Lines:
335

💛  - Coveralls


Active Record flexible batch operations(Insert,Update,Delete)

Q
A

Is bugfix?
no

New feature?
yes

Breaks BC?
no

Tests pass?
in development...

MyActiveRecord::$batchInsertSize = 1000;
foreach($myData as $data){
    $obj = new MyActiveRecord();
    $obj->field1 = 'data1';
    $obj->field2 = 'data2';
    $obj->field3 = 'data3';
    $obj->batchSave(); #or batchInsert();
    #no any database operation execute until count of insert operation equal MyActiveRecord::$batchInsertSize
}
MyActiveRecord::flushBatchInsert(); // executing the remaining operations. required.

or batchDelete() or batchUpdate

@ziaratban tests seems to fail: https://travis-ci.com/yiisoft/yii2-mongodb/jobs/293832598


Time in minutes for a customer to finalize a transaction is not working

PHP Version: 8.3   | Shopware Version: <IP_ADDRESS>  | Affected area / extension: Platform(Default)

Expected behaviour:
If the payment status is set to canceled, you can set the time limit here that a customer has to pay for the order again. By default, this is 60 minutes.
Actual behaviour:
Neither the 60 minutes work here nor any time you type into the field.
How to reproduce:

Create a new shop
Setup PayPal with our Shopware Testcredentials
Change the timelimit in Settings > Card Settings > Time in minutes for a customer to finalize a transaction to 1
Place an order via PayPal in the Frontend
Set the Payment Status to canceled
ERROR: You can still finish the payment in the frontend after 1 Minute

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-38403
[created from NEXT-38403, comment 496897]

[public]This is not how this option is supposed to work. It has no impact on the after order payment process. It is the time that you have to finalize a transaction during the initial checkout process. For example being forwarded to a payment provider (like paypal) during the checkout and returning to the shop, after you have finished the transaction steps on the payment provider page. If this action takes longer than the time it is configured here, we consider this as a failed transaction
[created from NEXT-38403, comment 496925]


how do i get user credentials

Hi @rakshitsoni02, sorry about that, we have a page with instructions for that at http://www.ibm.com/smarterplanet/us/en/ibmwatson/developercloud/doc/getting_started/gs-credentials.shtml since it applies to all SDKs, however it should have been linked to from the readme. I've fixed it now.

ok thanks


Secrets rotation 2023-01-05

Per the CircleCI security incident, the secret DOCKERHUB_TOKEN  used for the CircleCI build was rotated today and updated in CircleCI, also GTOKEN secret was removed as I can't find any use for it.
Will wait for next MySQL/Xtrabackup release to see how much is broken.

This is solved.


[Question]: How do I stream both market data from OptionDataStream and StockDataStream?

Question form pre-submit checklist.

[X] I have searched the existing issues to ensure there isn't already an issue about this question.
[X] My question has to do with the Python SDK and isn't a general question about the API. (If it is please open your issue here)
[X] My question isn't about how to do a specific algorithm or asking for trade advice (answers to these are outside the scope of this repo).

Question
I have something like this defined:
self.options_data_stream = OptionDataStream(self.api_key, self.api_secret)
self.stock_data_stream = StockDataStream(self.api_key, self.api_secret)

When I try to run both:
await asyncio.gather([
  asyncio.run(self.stock_data_stream.run()),
   asyncio.run(self.options_data_stream.run())
 ])

Only the first .run() works.
I couldn't get data from the options_data_stream().
How do I stream both stock market and options at the same time?

@jamesmawm
Could you please try this?
async def run():
  await asyncio.gather(
    asyncio.create_task(self.stock_data_stream._run_forever()),
    asyncio.create_task(self.options_data_stream._run_forever())
  )

asyncio.run(run())

.run() calls asyncio.run() in inside. You could use ._run_forever() instead.
But as you can see it has _ prefix in the function name, it means we have an option to change it completely at any given version of alpaca-py including the name of function _run_forever(). So, please be aware of this.

This is perfect, thanks @hiohiohio!
Absolutely, looking forward to seeing this in the official docs.


Running in docker gives EOF error on PUT request

Firstly - thanks for this extremely useful addon for Turborepo! Very impressive!
I have no problems using the downloadable executable, but using the docker container from the registry or built locally gives this error when turbo tries to connect eg:
2021-12-28T16:58:10.774+1000 [DEBUG] run: performing request: method=PUT url=http://<IP_ADDRESS>:8080/v8/artifacts/dad54db4bd311da2?teamId=team_test
2021-12-28T16:58:10.807+1000 [ERROR] run: request failed: error="Put "http://<IP_ADDRESS>:8080/v8/artifacts/dad54db4bd311da2?teamId=team_test": EOF" method=PUT url=http://<IP_ADDRESS>:8080/v8/artifacts/dad54db4bd311da2?teamId=team_test

That's running with an apiUrl and teamId set in ./turbo/config.json via turbo eg:
TURBO_TOKEN=testtoken yarn turbo run build  -vvv --force

Other things I've tried result in a connection refused error instead, so EOF seems to imply it's connecting but failing to PUT. I'm using S3 with valid credentials that work with the non-docker version. I've even modified the container to execute inside it manually various commands to make sure it's not that the command arguments are not being mistranslated somehow.
This is what I've been using in docker-compose:
  tapico-turborepo-cache:
    container_name: dev_tapico-turborepo-cache
    image: ghcr.io/tapico/tapico-turborepo-remote-cache:sha-152ba94
    networks:
      - internal
    ports:
      - "8080:8080"
    environment:
      - AWS_ACCESS_KEY_ID
      - AWS_SECRET_ACCESS_KEY
    entrypoint: /bin/sh
    command: -c "/go/bin/tapico-turborepo-remote-cache --turbo-token=testtoken --kind=s3 --s3.region=us-east-1 --bucket=test-turborepo-cache -v"

The is on Turbo 1.0.23 and 0.0.8.
I'm a little rusty on my Docker and haven't used Go before but I couldn't see anything obviously wrong in either.
Is it possible to show a working example of a docker-compose wrapped around tapico-turborepo-remote-cache that allows the host (eg MacOS) to run turbo against it successfully? Thanks!

Thank you for reporting. I will have a look at it tomorrow :)
I typically use the environment variable alternative for the flags were possible when running the docker image. I didn't see the EOF file before. I will try to reproduce the issue locally.

Hi @weyert, this EOF happens even just using the local version, eg sh'ing into the container and running:
./tapico-turborepo-remote-cache --turbo-token=testtoken --kind=local -v

It shows:
# ./tapico-turborepo-remote-cache --turbo-token=testtoken --kind=local -v
projectID:  kind: local localStoragePath:  aws.endpoint:  google.endpoint:  google.credentialsJsonPath: Starting the Tapico Turborepo remote cache server

But EOF errors still show up when trying to connect. So something fundamental about container networking from a MacOS host and maybe something with the Go network listener?

@weyert ok I've figured it out, this works running inside the container via a shell:
 LISTEN_ADDRESS=:8080 ./tapico-turborepo-remote-cache --turbo-token=testtoken --kind=local -v

That tells http.ListenAndServe to listen on any hostname, whereas at the moment the default is to only listen on 'localhost:8080'. Since calling a docker container from another container or from the host will usually make the call via a different hostname the Go library will never accept this I suspect.
So I guess the fix for this is maybe adding to the LISTEN_ADDRESS as a configuration flag, or defaulting to listening to just ':8080' (any host) instead of 'localhost:8080' on line 547 of main.go?:
		err := http.ListenAndServe("localhost:8080", loggedRouter)

Yeah, probably we should just listen to <IP_ADDRESS>:8080 instead. I should update the README file with the latest state of things.
My apologies for the lack of documenting this LISTEN_ADDRESS.

Awesome! BUCKET_NAME is another good env var to add to the docs too. AWS ECS Fargate as well as docker-compose were way easier to get the syntax right using environment variables. Thanks again for your awesome project!

Awesome, glad you like the project :)
Don't hesitate to raise a PR for the docs or instructions how to get it running on AWS. That would be amazing!

@ckortekaas I have created an example and updated the README. Would you be so kind and have a look at the two README files and the docker-compose example and whether you think it would be a useful example?

I also tried to reproduce the EOF issue of this ticket but I haven't been able to make it happen using the above mentioned docker-compose file

@weyert That looks great!
I suspect the reason you might not have the issue with EOF is a difference in host OS. I am using macOS 12.1 with Docker Desktop 4.3.2 (the latest version). Are you perhaps on a different host OS and older or different version of Docker Desktop?

Ah I am on 4.3.1 and macOS 11. I am updating Docker now and will try again. Are you seeing the issue with the docker compose example?

I haven't had much luck yet to reproduce your problem. I will try to upgrade to macOS 12.1

@ckortekaas I have seen it occasionally earlier this week. I am wondering if it could be to do with some default maximum upload size in Golang for the PUT route? I will look into this

I am wondering if this ticket is related? https://github.com/vercel/turborepo/issues/487


Change a collection from ConcurrentHashSet to HashSet in sync

What changes are proposed in this pull request?
Change a ConcurrentHashSet to HashSet to reduce cost in metadata sync.
Why are the changes needed?
The collection is only locally used for reading and can be changed to HashSet for lower cost.
Does this PR introduce any user facing changes?
NA

In there are no writers to the collection, Collections.unmodifiableSet() will protect the visibility by final and subsequent enumerations and contains check should see no thread safety issues. Ref: https://stackoverflow.com/a/42313926/4933827

alluxio-bot, merge this please


Added covid-19 data in csv form

plz merge my file and add hacktober fest tag

Good one @ManashAnand
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow these steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to the profile section from the top right-hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard!
And don’t forget to share your achievement with your friends.


Is there a concise way to directly export generated STIX data as JSON file?

Well, this package is straightforward at generating a random STIX data and I'm satisfied at this level of convenience. However, when I try to load this as JSON data and save it to the data like the code below,
import stix2generator
import json

stix2_generator = stix2generator.create_stix_generator()
stix = stix2_generator.generate()
stix_dump = json.dumps(stix, indent=4)

I get the errors below because some STIX SDO objects are not python default data types. (For example, the runtime exception log below says that the generated STIX data can't be converted to the JSON format since Note which is one of STIX SDO is not compatible.)
Traceback (most recent call last):
  File "C:\Users\user\Documents\GitHub\nis-ems-client\test\fake_stix2_generator.py", line 6, in <module>
    stix_dump = json.dumps(stix, indent=4)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\user\.pyenv\pyenv-win\versions\3.11.9\Lib\json\__init__.py", line 238, in dumps
    **kw).encode(obj)
          ^^^^^^^^^^^
  File "C:\Users\user\.pyenv\pyenv-win\versions\3.11.9\Lib\json\encoder.py", line 202, in encode
    chunks = list(chunks)
             ^^^^^^^^^^^^
  File "C:\Users\user\.pyenv\pyenv-win\versions\3.11.9\Lib\json\encoder.py", line 432, in _iterencode
    yield from _iterencode_dict(o, _current_indent_level)
  File "C:\Users\user\.pyenv\pyenv-win\versions\3.11.9\Lib\json\encoder.py", line 406, in _iterencode_dict
    yield from chunks
  File "C:\Users\user\.pyenv\pyenv-win\versions\3.11.9\Lib\json\encoder.py", line 439, in _iterencode
    o = _default(o)
        ^^^^^^^^^^^
  File "C:\Users\user\.pyenv\pyenv-win\versions\3.11.9\Lib\json\encoder.py", line 180, in default
    raise TypeError(f'Object of type {o.__class__.__name__} '
TypeError: Object of type Note is not JSON serializable

So, my question is, is there a way to cope with this issue? I'm almost new to STIX, I just read the STIX documentation from the official page today and I am about to use STIX data with my project. Thanks in advance.

It's possible to simply(maybe) parse the STIX2 generation result as a JSON dump with Python's JSON package(json) with STIX2's JSON serialization class object(stix2.serialization.STIXJSONEncoder).  :)
Here I'll attach a working makeshift example
import stix2generator
import stix2validator
import stix2
import json
import uuid
from rich import print

# Generate the fake STIX2 data
stix2_generator = stix2generator.create_stix_generator()
stix = stix2_generator.generate()

# Convert the STIX data (Dictionary with STIX-proprietary objects) to pure JSON objects
def stix_to_json(stix_data):
    stix_objects = []
    for value in stix_data.values():
        stix_objects.append(json.loads(value.serialize()))
    return stix_objects

stix_objects = stix_to_json(stix)

# Create a STIX bundle with the generated objects
stix_bundle = {
    "type": "bundle",
    "id": f"bundle--{uuid.uuid4()}",
    "objects": stix_objects
}

# Convert the STIX bundle to JSON
stix_bundle_json = json.dumps(stix_bundle, cls=stix2.serialization.STIXJSONEncoder, indent=4).encode('utf-8').decode('utf-8')
print(stix_bundle_json)

# Validate the generated STIX bundle
result = stix2validator.validate_string(str(stix_bundle_json))
stix2validator.print_results(result)

Not sure what you mean by repositioning the id property.  Abstractly speaking, mappings/objects don't have an intrinsic order to their entries (some implementations can allow you to control some kinds of ordering, e.g. a traversal order, but that is an implementation detail).  I don't think JSON-Schema allows you to express a required ordering on object entries (correct me if I am wrong).  So, it seems to me an object entry ordering difference cannot cause a JSON-Schema validation failure.
A simpler way to generate and validate is (but does not directly use the json package):
import io
import sys
# ... and all the other imports

stix = stix2_generator.generate()
bundle = stix2.Bundle(list(stix.values()))

# A simple way to dump to stdout:
# (don't use pretty=True for large numbers of objects!)
bundle.fp_serialize(sys.stdout, pretty=True)

# A simple way to dump JSON to a memory text buffer
buf = io.StringIO()
bundle.fp_serialize(buf)

# Reposition for reading, and validate
buf.seek(0, io.SEEK_SET)
result = stix2validator.validate(buf)
stix2validator.print_results(result)

Or via shell:
# -b causes output to be wrapped in a bundle
generate_stix -b > ./bundle.json
stix2_validator ./bundle.json


SW-2217 Switch from Java 11 HTTP client to Ktor

Update the code that makes requests to Balena and Keycloak to use the Ktor HTTP
client instead of the Java 11 one. Remove the helper functions we used to use to
make the Java 11 client's API less cumbersome.
No change in functionality or behavior here.

Current dependencies on/for this PR:

main

PR #842   👈

This comment was auto-generated by Graphite.

Ran LiveBalenaClientTest with a valid Balena API key locally.


In-place stochastic gradient interface

Make the gradient function take a storage argument to write onto, right now each minibatch allocates a new vector

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/46792
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.9 -m "<description of version>" 98c26c4d59479faa312f119116bcfdd2acb1538d
git push origin v0.1.9

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/47821
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.10 -m "<description of version>" 91b0d983273ec2db53b3a0728093019e1aae50d1
git push origin v0.1.10

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/47821
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.10 -m "<description of version>" 91b0d983273ec2db53b3a0728093019e1aae50d1
git push origin v0.1.10


[Feature Request] - StreamReader and StreamWriter implement Send

Description
StreamReader and StreamWriter should implement send to make those objects usable in multi-threaded applications.
Changes
This should be a simple change to make the Box<dyn> member of the Stream* enums to be Box<dyn + Send>.

Impl in 0.3


Results Error

Apologies, but I'm going crazy trying to figure out what I've misconfigured.  I keep getting the following error right at the end of a search:
:: Result
==> Found the following Profiles:
:: Google Reverse Image Search
==> Opening Webdriver
:: Uploading Local Known Images
-> Inserting Path
-> No Prediction given sry...
-> Collecting Links...(Page 1)
-> Switching to Page 2
-> No more pages...
:: Yandex Reverse Image Search
==> Opening Webdriver
==> Uploading Local Images
-> Inserting Image URL
Traceback (most recent call last):
File "eagle-eye.py", line 260, in
main(skipFB=args.skipfb, skipY=args.skipyandex, FBUrls=[], jsonRep=jsonRepFile, dockerMode=aDocker, dockerName=aName)
File "eagle-eye.py", line 139, in main
yandex.collectLinksLocal()
File "/EagleEye/grabber/yandex.py", line 74, in collectLinksLocal
elems = driver.find_elements_by_xpath('/html/body/div[1]/div[2]/div[1]/div[1]/div[1]/div/div/div/div[1]/div[2]/form/div[1]/span/span[2]')[0]
IndexError: list index out of range
cp: cannot stat '/root/EagleEye/*.pdf': No such file or directory
Here is my entry.sh file:
#!/bin/bash
cd /EagleEye
python3.6 eagle-eye.py --docker --name "[person's name]"
#now copy the result
yes | cp -rf ~/EagleEye/.pdf ~/EagleEye/result/.pdf
And here is the docker start code that I enter:
sudo docker run -t --net=host --env="DISPLAY"
--volume="$HOME/.Xauthority:/root/.Xauthority:rw"
-v  ~/EagleEye/known:/EagleEye/known
-v  ~/EagleEye/result:/result
-v ~/EagleEye/entry.sh:/entry.sh
eagle-eye
NOTE:  I have the "known" and "result" folders created in the EagleEye directory.
What am I doing wrong?

Seems like the Grabber for yandex is broken again.
Please use the - sY flag in entry.sh to skip yandex until i fix It.


too many dangling docker containers due to browsertrix-crawler

By always running docker run instead of an initial docker run followed by docker stop and subsequent docker start a lot of containers are accumulated.

Hi @edsu do you see a better solution here than just cleaning the docker containers associated with browsertrix? Otherwise, let's leave the quick fix as the permanent solution.

appending --rm to the docker run command ensures the container is cleaned after the execution.


Move schema generation to bin from examples

Description and Motivation
Schema generation is now done through a bin build type, rather than as an example. See
https://medium.com/cosmwasm/dev-note-1-moving-schema-rs-from-examples-to-bin-7c1b8cde7fc8 for more details.
To generate this PR, I:

changed from --example to --bin in the .cargo/config schema alias.
added --lib to each wasm build in the .cargo/config alias
manually adjusted terraswap_token to use cargo-schema as a dependency rather than dev-dependency.

Related Issues
Closes #115.
Checklist:

[X] I have read Migaloo's contribution guidelines.
[X] My pull request has a sound title and description (not something vague like Update index.md)
[X] All existing and new tests are passing.
[X] I updated/added relevant documentation.
[X] The code is formatted properly cargo fmt --all --.
[X] Clippy doesn't report any issues cargo clippy -- -D warnings.
[X] I have regenerated the schemas if needed cargo schema.

@kaimen-sano can you fix the conflicts so we merge this?

Fixed in another PR


Public-Signed Certificate Validation Error

I recently upgraded to openSUSE Leap 15.0 on my laptop, and now I am getting a "certificate could not be verified" warning when connecting to servers that are using a public-signed certificate.
I redownloaded and recompiled on both openSUSE Leap 42.3 and openSUSE Leap 15.0 today - it works on 42.3, but not on the newer 15.0.
I am attaching the output from a strace for both operating systems. It looks to me like both are checking for /var/lib/ca-certificates/openssl/4bfab552.0 (which exists, and is the correct CA) - but on 15.0, it never opens that file?
openSUSE-Leap-42.3-Works.TXT
openSUSE-Leap-15-Error.TXT

@KenHolloway yes, we currently only implement certificate fingerprint matching, no check for authorities.

I am not sure what the exact terminology is, but when I am running under openSUSE 13.1 or openSUSE 42.3, connecting to a server that is using a public-signed certificate just connects; when I try the exact same thing under openSUSE Leap 15.0, I get an error.
I was not trying to ask for a new feature - just help figuring out why it behaves differently under the different versions of openSUSE, and how to make it behave "right" under openSUSE Leap 15.0 (the newest version, regardless of the version numbers)
Thanks,
Ken

Ok, did you accept keys previously? /cert-tofu does that on first connect

No, I had not accepted the keys - known_hosts2 is empty on my openSUSE 42.3 machine that I am testing from, and I have never used /cert-tofu.
In the output from strace, I see that on both operating systems it is finding that the CA certificate exists:
stat("/var/lib/ca-certificates/openssl/4bfab552.0", {st_mode=S_IFREG|0444, st_size=1492, ...}) = 0
Under openSUSE Leap 42.3, it then opens the CA:
open("/var/lib/ca-certificates/openssl/4bfab552.0", O_RDONLY|O_CLOEXEC) = 13
But, under openSUSE Leap 15.0, I see no attempt to open the CA.

@KenHolloway Just checked, are there some OpenSSL related settings changed? We're verifying the certificate in x509_verify_certificate which is a wrapper creating a X509_STORE with additional lookup paths.

I have not ever made any OpenSSL configuration changes.
I just compared /etc/sll/openssl.cnf on the two systems. The only differences I see are that openSUSE Leap 42.3 had:
basicConstraints = CA:true
digests         = md5, sha1
and openSUSE Leap 15.0 has:
basicConstraints = critical,CA:true
signer_digest  = sha256
digests     = sha1, sha256, sha384, sha512
I tried copying openssl.cnf from the 15.0 system to the 42.3 system, but it made no difference.

I am not sure how to tell. This certificate is from 27 December 2016. When I look at it in a browser (same certificate is used for IIS and RDP), it says Certificate Signature Algorithm is SHA-256.

@KenHolloway ok, so the cert is sha256. Could you check the ca signed with sha256 too? Or, inverse test does it work if you add sha1 to signer_digest? (Please remove again after the test)

Both the Intermediate and Root certificates are also SHA-256.
I copied the opensssl.cnf from my 42.3 computer to my 15.0 computer - no change. (strace still shows that it finds that /var/lib/ca-certificates/openssl/4bfab552.0 exists, but it never tries to open in. Under 42.3, it find that it exists, then opens it.)

Does FreeRDP just call OpenSSL to do the certificate checking? Is this a problem with OpenSSL instead of FreeRDP?

@KenHolloway Roughly yes, but x509_verify_certificate does some argument conversion/preparation before calling openssl

@KenHolloway You don't by chance have a link to a proper documentation of that? The API docs of OpenSSL are light on the workings of this one.

Unfortunately, no. I too felt the documentation was a bit sparse. I found that code in a posting about a similar problem. I also found another posting that said:
store = X509_STORE_new();
verify_params = X509_Store_get0_param(store);
purpose = X509_PURPOSE_get_by_sname("sslclient");
X509_VERIFY_PARAM_set_purpose(verify_params, purpose)
...
PKCS7_verify(..., store, ...);
I don't know which way is "better". I also did not save the URL to either post....

This change did not fix the issue for me. I am still getting:
The above X.509 certificate could not be verified, possibly because you do not have
the CA certificate in your certificate store, or the certificate has expired.

I added a call to X509_STORE_CTX_get_error - it is returning error 28:
X509_V_ERR_CERT_REJECTED: certificate rejected
    the root CA is marked to reject the specified purpose.

@KenHolloway if you change to purpose server does that work?

I tried X509_PURPOSE_SSL_SERVER, and X509_PURPOSE_SSL_CLIENT - it did not make any difference.
Do we need to "X509_STORE_CTX_set0_param(csc,verify_param)"? (It seems like, after getting that param, we might need to set it back.) I tried adding that, but then got a different error (22):
X509_V_ERR_CERT_CHAIN_TOO_LONG: certificate chain too long
    the certificate chain length is greater than the supplied maximum depth. Unused.


Email Login and Logout

Description
To implement Email Login in the Initial Screen. Currently, it's resulting in null uid as shown below.
Screenshots

Steps to Reproduce
Please provide detailed steps for reproducing the issue.

Initial screen : lib\screens\initial_screen.dart
Auth files: lib\services\auth.dart
Also implement the email log out when the user taps on the logout button.
Private profile: lib\screens\profile\private_profile.dart

Additional data
None

I can give it a try!

Cool @keyurgit45, please can try to implement auth provider if you can.
I'll make the state management easier.

I can use firebase.instance.authstatechanged . for that can create a new class to manage these things ?
In main.dart wrapper class route will be given to initialroute.

I can use firebase.instance.authstatechanged . for that we can create a new class to manage these things ? In main.dart wrapper class route will be given to initialroute. @Mohitmadhav

Okay @keyurgit45, also make sure to check the expiry time for logging in (Like if a user opens the app after 1 week, then he'll again have to log in). And remove the Wrapper Constructor if you're not using the key somewhere else

@Mohitmadhav  I have made the changes. Log in and log out are working fine. also in the sign-in method, I added the makeUserDataFromAuthUser() method which I forgot to add in prev PR. but I haven't implemented that expiry time for logging because I don't know how to implement that . Should I make a PR?

For the expiry time for logging in feature, can we store the time each time when a user opens the app in shared pref and checks if it is been a 1 week or not if yes then it will log out else the user will be on the home screen?

For the expiry time for logging in feature, can we store the time each time when a user opens the app in shared pref and checks if it is been a 1 week or not if yes then it will log out else the user will be on the home screen?

In general how long does the user can stay logged in (1 hr) if he doesn't open the app for a few days, which I don't know?
No , don't use shared preferences, I have already setup Flutter Secure Storage Package , have a look at that

official docs : Firebase Authentication sessions are long lived. Every time a user signs in, the user credentials are sent to the Firebase Authentication backend and exchanged for a Firebase ID token (a JWT) and refresh token. Firebase ID tokens are short lived and last for an hour; the refresh token can be used to retrieve new ID tokens. Refresh tokens expire only when one of the following occurs:
The user is deleted
The user is disabled
A major account change is detected for the user. This includes events like password or email address updates.
also take a look at my previous comment also.

official docs : Firebase Authentication sessions are long lived. Every time a user signs in, the user credentials are sent to the Firebase Authentication backend and exchanged for a Firebase ID token (a JWT) and refresh token. Firebase ID tokens are short lived and last for an hour; the refresh token can be used to retrieve new ID tokens. Refresh tokens expire only when one of the following occurs:
The user is deleted The user is disabled A major account change is detected for the user. This includes events like password or email address updates.
also take a look at my previous comment also.

Yeah, I read that too, and also your previous comment.
So don't use shared preference but go for Flutter Secure storage package: https://pub.dev/packages/flutter_secure_storage, and keep the expiry for 2 days instead of a week
See lib\utils\keys_storage.dart

I have written this code, when should we call writeCurrentSessionTime() ? @Mohitmadhav
we can write a new timestamp we user open the app but if we want to write when user exits the app , dispose method can't be used. so need to find another way

I have written this code, when should we call writeCurrentSessionTime() ? @Mohitmadhav we can write a new timestamp we user open the app but if we want to write when user exits the app , dispose method can't be used. so need to find another way

@keyurgit45 it's better to call writeCurrentSesionTime() when the user logs in .
After that, we should call checkForExpiredSession every time the user opens the app again.
If diff>2, then the user will be logged out.
Then the user will have to sign in again, after which, the writeCurrentSessionTime() will be called again to store the current login time.

means you want, the user should sign-in in every 2 days?

means you want, the user should sign-in in every 2 days? @Mohitmadhav

Actually, if the user does not open the app for more than 2 days, then he should sign in again.

means you want, the user should sign-in in every 2 days? @Mohitmadhav

Actually, if the user does not open the app for more than 2 days, then he should sign in again.

ok got it

@Mohitmadhav I have made the changes. Log in and log out are working fine. also in the sign-in method, I added the makeUserDataFromAuthUser() method which I forgot to add in prev PR. the issue #106 is due to this. I am really sorry for that. but I haven't implemented that expiry time for logging because I don't know how to implement that. Should I make a PR?

If you resolved #106 too, then mention it in your final PR, and then I'll assign #106 also to you.

@Mohitmadhav Okay...firstly I will make PR for login and logout and then for issue #106

after doing git pull upstream main, I am getting this. I need onAuthStateChanged method, what to do here? @Mohitmadhav

can you show the complete screenshot once?

Ok cool, accept the incoming changes then.


The question about batch_size/val_iteration/lr.

Thanks for your implementation. When I run the code you give, it just uses 1325MiB GPU. I want to accelerate the speed,  so I change the hyper-parameters of batch_size=256or512(default 64) and val_iteration=256or128(default 1024), but I didn't get the ideal result.  What should I do? Must val_iteration be 1024?

I have the same question with you. In my opinion, the number of labeled data is less than unlabeled. So, in this case,  when val_iteration =1024, we will run the labeled data repeated  many times in a epoch. Does it essential and reasonable? @xiaopingzeng @YU1ut

In my opinion, this method needs to see the same sample with different augmentations a lot of times and get enough mixup samples to improve the performance. So, it is necessary to run a lot of iteration to get enough samples. I have no idea how to accelerate the speed of training at this moment.


Paloma Light Node Client Sale UI/UX

As a user, I want to be able to see a Paloma landing page for the Paloma Node Client Sale so that I am able to join in the Paloma LightNode Client Sale.
Acceptance Criteria

Use the Requirements from the EPIC: https://www.notion.so/volumefi/EPIC-07-12-24-Paloma-Light-Node-Public-Sale-8ea43ca42b2442d3977f8dc6237624f3?pvs=4#37cf7650e6734793a38d672286da780a
Create a design for the Paloma Home Page
Use Software As a Service SaaS shopping experience
We will need designs for FOUR seasons and FOUR pigeons
We want to reuse bot designs were possibe.

@joycehermosilla will you add the Figma link for the views in this ticket please? I am unable to locate them in Figma.


Add pentest environment to Terraform and  Makefile

This commit also introduced a new terraform variable (woker_app_stopped)
This is used in setting if the worker_app should be running or not.
The default is false. For Pentest, this is true
Context
Add pentest environment to Terraform and  Makefile
Changes proposed in this pull request
Add pentest environment to Terraform and  Makefile and introduce work_app_stopped variable
Guidance to review

Merging into 758-add-pen-env so that it can be tested as a whole.


pattern is scan all over the line, same as website app

https://github.com/9r3i/force-firesite/blob/1b39e988bb2eeb01dae5592fc8845f0a5944428f/firesite/firesite.js#L420

solved


uv add pyqt5 error

uv pip install pyqt5 works perfectly
but uv add pyqt5 result error:
❯ uv add pyqt5
Resolved 4 packages in 2.78s
error: distribution pyqt5-qt5==5.15.14 @ registry+https://pypi.org/simple can't be installed because it doesn't have a source distribution or wheel for the current platform

uv version uv 0.4.4 (3d75df6ab 2024-09-04)
os windows 10

I did some digging and found that pyqt5 depends on a package called pyqt5-qt5 which does not support Windows in versions 5.15.11 - 5.15.14, but does support Windows in 5.15.2.
In this case, how to lock dependencies across platforms? In other words, how to avoid errors, after all, there is no problem with normal installation.

This is an inherent problem with distributions that don't ship source distributions, and have limited platform support. We can't guarantee that the set of wheels will cover all the platforms you care about. I'd suggest adding a constraint like:
[tool.uv]
constraint-dependencies = ["pyqt5-qt5 <=5.15.2"]

So, is this a bug or expected behavior? I tried multiple different package managers(poetry and pdm) and all went wrong, but I felt we could do better, after all, this distribution pattern exists for many popular libraries, so how do we lock down dependencies?

This is an inherent problem with distributions that don't ship source distributions, and have limited platform support. We can't guarantee that the set of wheels will cover all the platforms you care about. I'd suggest adding a constraint like:
[tool.uv]
constraint-dependencies = ["pyqt5-qt5 <=5.15.2"]

Since this is a Windows-only issue, wouldn't it be better to do this?
deps = [
    "pyqt5>=5.15.11; sys_platform != 'win32'",
    "pyqt5<=5.15.2; sys_platform == 'win32'"
]

Note: pyside2 is also not available for python >= 3.11 (PyPI-PySide2)


Confusion about ISO triplet

I found the iso_triplet functions related functions and (wrongly) assumed they were referring to {year, month, day} tuples -- after all, an ISO-8601 date is in the form YYYY-MM-DD.  I see now that the ISO 8601 standard also supports a week date:
https://en.wikipedia.org/wiki/ISO_week_date
...but I had never heard about that before, and was quite confused about the iso_triplet functions when I first tried to use them.  I suspect it's a common mistake others will make.  What do you think about renaming the iso_triplet functions to something like iso_week_date_triplet or similar to make it clear that it's not the { year, month, date} triplets someone might expect?
Also, I see that I can construct a timex date time from a { year, month, date } triplet using Timex.Date.from but I don't see a way to convert back to that form with any of the provided functions.  Am I just not seeing it or is that not part of the API provided by Timex?  Would you consider adding it?
Thanks!

@myronmarston You actually did uncover a bug in how I was handling the ISO triplet stuff, so I'm glad you reported the issue you found!
The iso_triplet is a standard form for {YYYY, WW, WD}, so I think I'd rather treat that as a documentation issue. However, the current docs do describe the tuple returned, do you have suggestions on how the docs could be improved?
You can use {{^y, ^m, ^d}, _} = {y, m, d} |> Date.from |> DateConvert.to_erlang_datetime to effectively roundtrip the conversion. However you will get the time component as well (hence the match on the result of the conversion to get the date back). Right now I don't have a specific function for taking in a {YYYY, MM, DD} tuple and converting back to one, but you can get it trivially via {date, _} = DateConvert.to_erlang_datetime(%DateTime{})

However, the current docs do describe the tuple returned, do you have suggestions on how the docs could be improved?

The docs explain this.  However, as someone who thought he already knew what iso_triplet meant, I didn't initially read them, and then got really confused with what I was seeing...and then I read the docs, and realized there was a part of iso8601 I had never dealt with and didn't know existed :).
Maybe the { YYYY, WW, WD } form is common in the community, but I had never seen or heard of that form before.  My experience with other date APIs (e.g. Ruby's Date.iso8601) made me think of iso8601 exclusively in terms of YYYY-MM-DD form (which led me to think the triplet was { YYYY, MM, DD }.  The wikipedia article on iso8601 uses "date" to refer to the "YYYY-MM-DD" format I expect and "Date with week number" or "week date" to refer to what you are calling iso_triplet -- which suggests that putting "week" in the function names somewhere would more closely align with common terminology usage.
All that said: changing the name of a public API is a hard sell as it's disruptive to the community so I can completely understand wanting to keep them as is.  Or maybe I'm the odd one here (as a newcomer to elixir) and most elixir users would understand iso_triplet as you treat it.
Regardless, thanks for the great library :).  Timex is working well for me besides the couple of issues I reported.

I can definitely see the potential for confusion, and I'd be tempted to rename it. However, I think the reason why I feel it's less ambiguous than stated is because the usual meaning of ISO vs not-ISO (when it comes to conversions), has to do with the fact that the ISO calendar represents dates in terms of {year, week, weekday}, not {year, month, day}. This is because ISO weeks/days do not always occur in the same year you'd expect. Using the example from #71, {2014, 1, 1} is actually the date 2013-12-30, because the first day of 2014 according to the ISO calendar is actually in December of 2013. So having a function called iso_triplet which takes a DateTime and produces a {year, month, day} tuple shouldn't be called iso_triplet to begin with as it is effectively redundant (and doesn't tell you much about what is returned, at least without checking the docs), it would make more sense to call it to_date_tuple or to_erl (since the triplet of that form is one of the Erlang datetime types).
As far as alternatives go to make it less confusing, my preference would be more something along the lines of Date.to_iso_calendar, since the dates on the ISO calendar take the form of {year, week, weekday}.
Thoughts?

However, I think the reason why I feel it's less ambiguous than stated is because the usual meaning of ISO vs not-ISO (when it comes to conversions), has to do with the fact that the ISO calendar represents dates in terms of {year, week, weekday}, not {year, month, day}.

I did not know about how the ISO calendar represents dates!  I'm probably not the best person to ask about this because my knowledge of ISO is very limited (I've always just thought of it as the name of the YYYY-MM-DD format for dates).  I've never read the standard.
Maybe you can get feedback from other people who are more familiar with the ISO standard?

@myronmarston Well it's the feedback from users who aren't as familiar that is more important I think :), the reason being that someone who was familiar designed the API, so if it's confusing, then I'd rather get input from those who have less context clouding their opinion. Do you think documenting some of these things would make sense? Would people read documentation on, say, what the ISO calendar is and how Timex APIs relate to it?

Maybe a top-level note in the README (and in the Timex.Date module doc) saying something like would suffice?

Warning: Timex functions with iso in the name refer to how the ISO calendar represents dates and not the YYYY-MM-DD ISO8601 date format.

Included in Version 2.


[Bug]: Thermal model not working for a composite electrode particle model with two (or more) phases

PyBaMM Version
23.5
Python Version
3.9.13
Describe the bug
Lumped thermal model is not compatible with the composite particle phase option.
Steps to Reproduce
import pybamm

pybamm.set_logging_level("INFO")
# load models
options = {
    "particle phases": ("2", "1"),
    "open-circuit potential": (("single", "current sigmoid"), "single"),
    "cell geometry": "arbitrary", "thermal": "lumped"
}
model = pybamm.lithium_ion.DFN(options)

parameter_values = pybamm.ParameterValues("Chen2020_composite")

# create and run simulations
sim = pybamm.Simulation(model, parameter_values=parameter_values)
sim.solve([0, 4500])

Relevant log output
File ~\AppData\Local\Programs\Python\Environments\gen-env\lib\site-packages\pybamm\models\full_battery_models\lithium_ion\dfn.py:32 in __init__
    self.set_submodels(build)

  File ~\AppData\Local\Programs\Python\Environments\gen-env\lib\site-packages\pybamm\models\full_battery_models\lithium_ion\base_lithium_ion_model.py:59 in set_submodels
    self.build_model()

  File ~\AppData\Local\Programs\Python\Environments\gen-env\lib\site-packages\pybamm\models\full_battery_models\base_battery_model.py:907 in build_model
    self._build_model()

  File ~\AppData\Local\Programs\Python\Environments\gen-env\lib\site-packages\pybamm\models\base_model.py:550 in _build_model
    self.build_coupled_variables()

  File ~\AppData\Local\Programs\Python\Environments\gen-env\lib\site-packages\pybamm\models\base_model.py:480 in build_coupled_variables
    raise pybamm.ModelError(

ModelError: Missing variable for submodel 'thermal': 'Negative electrode reaction overpotential [V]'.
Check the selected submodels provide all of the required variables.

Isn't this a relatively simple bug to fix in the BaseThermal class? Something along this line for the heating term due to the reaction overpotential without having gone through the math. Something similar is then also required for the entropic heating term, but that is all no?
a_j_p = variables["Positive electrode volumetric interfacial current density [A.m-3]"]

if int(self.options['particle phases'][1]) > 1:
    a_j_p_p = variables["Positive electrode primary volumetric interfacial current density [A.m-3]"]
    a_j_p_s = variables["Positive electrode secondary volumetric interfacial current density [A.m-3]"]
    eta_r_p_p = variables["Positive electrode primary reaction overpotential [V]"]
    eta_r_p_s = variables["Positive electrode secondary reaction overpotential [V]"]

    Q_rxn_p = a_j_p_p * eta_r_p_p + a_j_p_s * eta_r_p_s
else:
    eta_r_p = variables["Positive electrode reaction overpotential [V]"]
    Q_rxn_p = a_j_p * eta_r_p

Yes, I'd implement as a sum over phases e.g. like here.
Equations, summing over phases, m


Updated the name of cluster tuning parameter

Updated the name of cluster tuning parameter from RoutingHistoryLength to RouteHistoryLength as a correction

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

#label:"aq-pr-triaged"


Add 5 new addons

Just added some compatibility with PimpMyStream for my addons

Oh wow, thanks.
A few mentions though, you will need to create a github release for each repository / addon (you don't need to attach any files, just set a unique tag version for them)
PimpMyStremio uses the releases to download to the users, and every time you make changes and want to update to the users, simply make a new release.
Another thing is that it might be a good idea to use the PimpMyStremio internal proxy for iptvOrg, it makes more streams work usually because it does handles header cache requirements.
To use the proxy, just do:
const { proxy } = require('internal')

And then on this line:
https://github.com/jlvcm/stremio-ptiptv/blob/master/addon.js#L104
Change it to:
			url: proxy.addProxy(stream)

I think this might increase stream success.
I'll test your addons tomorrow to make sure they work and merge if they do.

Oh, one more mention, I think YTS only has movies, it does not have series, so it should be changed to:
		"types": ["Movies"],

in the Pull Request.

changed IPTV, fixed the YTS typo and added releases, thanks @sungshon, let em know if something does not work or needs fixing

I've had a chance to test your addons, the only one that does not is YTS, which gives an error because the node-cache module is missing, PimpMyStremio addons are limited to only these modules: https://github.com/sungshon/PimpMyStremio/blob/master/docs/modules-whitelist.md
The other 4 addons all work fine. If you want to test the addons yourself, there are 2 ways of doing this:

sideload an addon: https://github.com/sungshon/PimpMyStremio/blob/master/docs/README.md#testing-add-ons
(alternatively) in PimpMyStremio's settings, you can change the "Remote Add-ons List URL" to the one in your PR (which is: https://raw.githubusercontent.com/jlvcm/PimpMyStremio/patch-3/src/addonsList.json ) and restart PimpMyStremio, this will make the app pull your own addon list over the default one, and you can change it back to the default one (so it auto-updates itself in the future, the default one is: https://raw.githubusercontent.com/sungshon/PimpMyStremio/master/src/addonsList.json )

I just used the second method, although I can guarantee that if you use only the default modules, it will certainly just work, just mentioned the addon testing methods for future reference if you need them.

Oh, don't forget to make another release for YTS after you made the changes. :)

I've made a PR to YTS to fix compatibility to PimpMyStremio, as @sungshon mentioned, you should also make a new release for YTS after merging that PR.

done, thanks @sungshon and @pakamoon

yup, works fine now, merging


Do not convert index.ts in schemaDirectory [Question]

I would like to have an index.ts in the schemaDirectory that exports all Joi schemas without joi-to-typescript trying to convert it.
The reason for this is because an index.ts allows me to easily import the Joi schemas elsewhere in the code base without the need for one import statement per schema.

I might give this one a crack if maintainers think it's good. I reckon this should have a setting associated with it, defaulted to ignore the index.ts as well. Something like "ignoreIndexFiles" = true by default

Sounds good 👍

or should the setting could be something like ignoreFiles = ['index.ts', 'subDir/ingoreSchema.ts'] ?

Yeah sounds reasonable. I'm not sure how pattern matching or wildcards work but I'm sure I can sort something out

Changed merged just needs releasing

released under v1.10.0


Use coverage 'source' option

Codecov Report

Merging #49 (aa1b0dd) into main (99595ee) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #49   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          167       167
  Branches        26        26
=========================================
  Hits           167       167

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 99595ee...aa1b0dd. Read the comment docs.


404 from /process endpoint when Resource contains a BelongsTo relationship

Loving this plugin so far, but I am having a strange issue.
Something goes wrong while trying to load rulesForCreation that causes Laravel to return a 404 response.
This only happens when the resource has a BelongsTo field which is shown on creation.

Can you post how are you using it? what rules did you set

Sure! Sorry, should've given that at first.
The BelongsTo itself has no rules, it is defined as:
BelongsTo::make('Role')

The Filepond config is also pretty simple:
Filepond::make('Avatar')
    ->image()

The call stack for generating BelongsTo rules is really deep, but it seems to actually die in associatableQueryMethod() of laravel/nova/src/Fields/BelongsTo.php.
$request->resource() is null, so abort_if(is_null($resource), 404); is triggered in resource() in laravel/nova/src/Http/Requests/InteractsWithResources.php.

@gabe565 sorry for the delay, fixed on version v0.2.8


Remove geoquery when working from a saved location close #85

I was able to remove 2 of the 3 geoquery api calls when using the last location stored in 1localStorage1. This is accomplished by adding a new item to localStorage: 'TwcLatLon'.
The third one is a call to the reverse geocode to get the zip code. It could be stored and re-used as well, but it wasn't something that I had tackled in my fork so I didn't try to remove it yet.
The spanLastRefresh had to be moved to it's new location to resolve a race condition exposed by not needing to wait for the two round trips to the geocode server. The _AutoSelectQuery variable and code was also removed as it is no longer needed.

Yes it did! I didn't realize that feature had been added. It is working again.


Flaky test: No_exception_on_diagnostic_event_received_when_null_state

I set No_exception_on_diagnostic_event_received_when_null_state to ignore for now because it fails sometimes. It should be investigated and re-enabled once fixed.
System.Data.SqlClient.SqlException : A connection was successfully established with the server, but then an error occurred during the login process. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.)

@ajcvickers - can you assign someone to take a look at this flaky test?

Potentially fixed by: https://github.com/aspnet/Diagnostics/pull/435

Not fixed. Future instances of this failure will appear here.


"SecRuleEngine On"  No message in audit log

hi
i'm using modsecurity-v3.0.4 Release . When i use DetectionOnly mode, there are messages in auditlog. When i use "SecRuleEngine On" , there are no messages in auditlog, even if the rule is trigged. But i can find the record in nginx's error.log
and here is my modsecurity.conf
SecAuditEngine RelevantOnly
SecAuditLogRelevantStatus "^(?:5|4(?!04))"
SecAuditLogParts ABCDFHZ
SecAuditLogType Concurrent
SecAuditLogStorageDir /var/log/gateway/
I really dont know the reason. please help me solve this problem.

Hi @MapTracy ,
By 'modsecurity-v3.0.4 Release' you mean the official tagged version? -- either from an installed repo version, or if from github the tagged version ( https://github.com/SpiderLabs/ModSecurity/commit/753145fbd1d6751a6b14fdd700921eb3cc3a1d35 )
If you can see the expected output in the audit log when using DetectionOnly, but not when 'On' then that rules out several types of configuration errors.
When 'On' and you cannot see entries in the audit log,

Is there an entry in nginx's error.log ?
if you turn DebugLog level on (and set the level to 9), can you see the same relevant rule processing for both DetectionOnly and On?  (In particular, the rule that you expect to report, should include 'Rule returned 1' in the DebugLog).

Also:

if you change the SecAuditLogType to Serial, do you still have the same problem?
if you change SecAuditEngine from 'RelevantStatus' to 'On', do you then always see the entries in the audit log?

Hi @martinhsv
I had solved my problem with victorhora/ModSecurity-nginx@ac3e8a9
Thank you for replying to my message.


Server can enter a lagged state until a player leaves

Unsure what causes this but the server started lagging hard, with f3 saying we were getting 0.2kb/s bandwidth down. Issue completely disappeared when a player left the server (whether it's specific or just the first player to leave is unknown).
This happened twice today so it wasn't a one-off, the events leading up to it was spawning several hundred thousand hand grenades to bring bandwidth up to 500kb/s then restarting the round before the process completed.
The player who fixed the issue by leaving said they were lagging with the game alt-tabbed.

@PJB3005 did a trace, seems to be netserializer that's having a bad time.

trace.speedscope.zip
Here's the trace for what it's worth. I think it's just the sheer size overloading the connection and Lidgren choking on that.

Is this fixed?

It should be.


Unable to use API Key to Authenticate AppSync requests

I've been looking at how to use .NET to create a client that is capable of making GraphQL requests to AppSync. There's a class AuthenticationType that contains static members, however these never seem to be passed along. E.g. I can't do:
AuthenticationType apiKey = new AuthenticationType.API_KEY;
apiKey.setKey(keyVal);

Or even pass along the variable apiKey in any meaningful way afaict.
Is the only way to use AppSync using C# by using Cognito with User Pools, or am I missing something?
EDIT: I actually don't see how to use Cognito User Pools either. Are there any examples to look at?

Hi @taylor-zr, I'm not too familiar with AppSync or Cognito yet, but they are high on my list of services in which I want to get more knowledge.  To the best of my knowledge, we are lacking in .NET examples in both, which is something we will try to improve.  In the meantime, I'll try to provide as much info as I have.
The AuthenticationType class is not where you set the APIKey.  This class is simply for defining constants that you use to tell the API which authentication means to expect.
You can use the SDK to create the GraphqlApi with your choice of authentication type as seen below.  Once you have created the API, use its ApiId property to create your APIKey.  Per the AppSync documentation, you should be able to then create an HttpRequestMethod with the GraphqlApi's Uris and the APIKey's Id values.
`using System;
using System.Threading.Tasks;
using Amazon;
using Amazon.AppSync;
using Amazon.AppSync.Model;
namespace AppSync
{
class Program
{
static void Main(string[] args)
{
CreateAPI().Wait();
}
    static async Task CreateAPI() {
        using (AmazonAppSyncClient client = new AmazonAppSyncClient(RegionEndpoint.USWest2))
        {
            CreateGraphqlApiResponse createGraphqlApiResponse = await client.CreateGraphqlApiAsync(new CreateGraphqlApiRequest() { AuthenticationType = AuthenticationType.API_KEY, Name = "TestApi" });
            CreateApiKeyResponse createApiKeyResponse = await client.CreateApiKeyAsync(new CreateApiKeyRequest() { ApiId = createGraphqlApiResponse.GraphqlApi.ApiId });
        }
    }
}

}
`

I tried finding a nice GraphQL .NET library that let you set HttpHeaders, but after 3 attempts just used HttpClient.
        public static async Task Main(string[] args)
        {
            using (var client = new HttpClient())
            {
                client.DefaultRequestHeaders.Add("x-api-key", "xxxxxxx");

                client.BaseAddress = new Uri("https://xxxxxxxxxx.amazonaws.com/graphql");

                var query = "{\"query\": \"query ListEvents { listEvents { items { id name }} }\"}";
                var content = new StringContent(query);
                content.Headers.ContentType = MediaTypeHeaderValue.Parse("application/json");

                var response = await client.PostAsync("", content);
                var responseBody = await response.Content.ReadAsStringAsync();
                Console.WriteLine(responseBody);
            }
        }

Hello. Just to be clear, I'm an internal customer and this is an external customer's request. They are currently using HttpClient, but don't see a way to do this cleanly using the SDK and Cognito and would like to push for an actual fix. If there is another issue tracking this item, I'd be happy to send it along to the customer.

There is not an issue tracking this item. This is not core SDK functionality, so this would be a feature request. Please file a request here: https://github.com/aws/dotnet


Transform Layer is not used

Are there any reason that the transform layer is not used in default source code?
Have you found any inefficiency when using Transform?

Are there any reason that the transform layer is not used in default source code?
Have you found any inefficiency when using Transform?

for ljspeech, you need transform layer, but for biaobei dataset, you dont need. You need experiment to decide whether add this layer.


fix(client): allow endpoint on projects

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

It gets overwhelming the number of times that validation message appears, when it could (often is) completely valid.
Does as the comment says:
// If editor link is not allowed, use editor validator
// If local link is not allowed, use local validator
// If local link is allowed, use path validator
// Always used fCCValidator and httpValidator

I refactored, because I did not like the look of:
name === 'githubLink' || isEditorLinkAllowed || !isLocalLinkAllowed : null ? pathValidator

I presumed this is ready for review @ShaunSHamilton?

I presumed this is ready for review @ShaunSHamilton?

Yes 😁

I dislike double negations. How about refactoring the code to be more declarative?
	// All validators by default. The order is important for the next steps
	const validators = [
      fCCValidator,
      httpValidator,
      editorValidator,
      localhostValidator,
      pathValidator
    ];

    // Drop the editor validator if editor link is allowed
    if (name === 'githubLink' && isEditorLinkAllowed) {
      validators.splice(2, 1);
    }

	... and so on.
``s

But the .splice looks horrible, because then you have to think about positional elements for something that has nothing to do with position.

Oh yes, of course. That's just an example; you could use pop or whatever else. I was curious whether the logic can be refactored so the code becomes more "declarative".

NOTE: I also took the time to refactor the logic in form.tsx to be similar (less inline ternary) to form-fields.tsx (the main point of this PR)
it is a tiny change


Adding calling other interfaces in callback tutorial

In response to TSC Humble documentation task 9b

@clalancette The fact that this kind of thing is necessary begs a question: Would it be possible in future versions of ROS to allow for futures to spin while spin() is called in the main() on a particular node class? The examples here are good illustrative examples. In these cases, we're spinning to get a result from a future, not to execute some kind of action/service/subscription callback.
I'll fully admit I haven't tracked the code internally to rclcpp for how the futures are handled, but from a user standpoint, it seems like a reasonable behavior to have since we're really just blocking to get a result, not processing another callback that would need to be handled on another thread. Obviously the main thread is blocked by the current callback where the service is being called in though.
This is in opposition to needing additional executors (or multithreaded ones) to process callbacks in parallel. This is only talking about blocking or querying for future results.

I left some comments / questions / follow up if you can respond to those. I'll plan on fixing this up when I'm back from PTO (will be a nice 'getting back in the groove' task).


autostart

II have problem i think, RPiCam don't start after reboot, i have to start manualy, it's problem for me...
Normaly it's automatic start no ?

Yes. Autostart after reboot is an option when you install.
It places some start up commands into /etc/rc.local Check this file to see if it has the start up commands at the end.

i have this line :
#START RASPIMJPEG SECTION
mkdir -p /dev/shm/mjpeg
chown www-data:www-data /dev/shm/mjpeg
chmod 777 /dev/shm/mjpeg
sleep 4;su -c 'raspimjpeg > /dev/null 2>&1 &' www-data
if [ -e /etc/debian_version ]; then
sleep 4;su -c 'php /var/www/html/RPiCam/schedule.php > /dev/null 2>&1 &' www-data
else
sleep 4;su -s '/bin/bash' -c 'php /var/www/html/RPiCam/schedule.php > /dev/null 2>&1 &' www-data
fi
Program give 777 ?!

the rc.local looks fine.
Either is is not being executed at start up or the commands are not working for some reason.
Have you changed anything in standard set of raspbian?
You can also try putting in some dummy command like another mkdir in home directory to see if it is getting executed at boot time.

nano /etc/raspimjpeg
motion_detection false
motion_detection true


Version - Help -> Release Notes

Hi all,
Here's what do I see by clicking on : Help -> Release Notes

And here's what my (Win 7) control Panel says:

I suppose the versions should be the same....

I hope you clicked on "Restart and update" some time? If yes, that's a different bug then I guess

Double-checked:
-> clicked on "Restart and update"
-> restarts
-> nothing changed

Mind opening a Explorer window and copying in %localappdata%/atom/app-0.169.0 and opening atom.exe from there? (I'm not sure if this would be helpful though)

Same result: 0.150.0

#3757 strikes again?

yes, it's the same...

I close this, and I'll wait till #3757 will be closed...

@picibucor the bug there is already closed. Possibly comment there to reopen it, else your bug won't get fixed.

oh, THX


Different defaults for includeInboundPorts when using CNI vs init container

Bug description
The injection template uses different default values for traffic.sidecar.istio.io/includeInboundPorts, depending on whether CNI or the init container is used.
When you use CNI and you don't specify the traffic.sidecar.istio.io/includeInboundPorts annotation on your pod, the annotation defaults to the list of ports specified in the pod's container definitions (see injection template). When you use the init container, the istio-iptables command runs with the option -b '*' (see injection template).
This produces a different set of iptables rules. With CNI, only the ports that are explicitly specified in the pod definition are forwarded to the proxy, whereas with the init container, all are. The end result is that when you use CNI, authz policies only work on ports that are explicitly defined in the pod.
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[X] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
Iptables rules should be identical, whether you use the init container or CNI.
Version (include the output of istioctl version --remote and kubectl version --short and helm version if you used Helm)
master

/cc @justinpettit @howardjohn

I can confirm that on tag version 1.12.2, this annotation doesn't get override values from values.yaml but uses "*" when cni_enabled.


Fix Sweet32 vulnerability for microk8s versions before 1.18

Sweet32 vulnerability is described in this etcd issue and is handled by this PR in etcd. The solution is to provide a list of strong ciphers using the --cipher-suites parameter.
To apply the etcd solution described above, etcd versions v3.2.22+, v3.3.7+, and v3.4+ must be used.
Microk8s 1.18 uses etcd v3.4.3 so it is fine. The change to etcd v3.4.3 was introduced by https://github.com/ubuntu/microk8s/pull/894. The previous microk8s versions seems to use etcd version v3.3.4, which does not have the solution to the Sweet32 vulnerability.
Is it possible to update the previous versions of microk8s to use etcd version v3.3.7 instead of v3.3.4? In particular, I am interested in microk8s v1.14/stable.

Hi @vadimeisenbergibm, thank you for bringing this to our attention. I added a couple of PRs to update the 1.17 and 1.16 releases. Unfortunately we do not have any incentives to provide any more patches for releases that have gone out of support from upstream [1, 2] so we will not be updating 1.14.
https://kubernetes.io/docs/setup/release/version-skew-policy/
https://github.com/kubernetes/sig-release/blob/master/releases/patch-releases.md#non-active-branch-history

Hi @ktsakalozos, I see, thank you!

Pr merged into 1.17, 1.16


[minor] Couple of same mission same time

Version: develop https://github.com/LordGolias/antistasi/commit/8c0ea9bdacffc86ebd00146e22bf80d16e31a147
Mod: CBA, TFAR
Multiplayer dedicated server
Side: tested both vs East and vs West
Kill specops, i could ask 2 different but i had only one marker on map giving me the position, checked on spectators and both groups are there in their respective locations.

Sorry, I am not understanding what you are trying to say here. Could you clarify what is the error exactly?

I can request multiple tasks of the same kind (example 2 times "Kill specops") but only one marker is displayed for some mission.
Supply mission has the 2 different markers, some others you see just one.

The intended behavior is only be able to have one task of a given type at the time.
Do you remember how you got 2 of the same type? Fast clicking to start a mission?

Kill specops, i don't think i was fast clicking.
Also i had 2 supply missions.