[WIP] Typescript definition for v6

Typescript definition for v6 RC 3
This allows users to have the definitions just from installing the repo from npm, which is 👍 👍 💯 .
@erikras I don't mind helping maintain this, if you would just ping me before release I can do the definition updates. Or you can do them yourself and I can look over them :) It should be pretty easy to do small tweaks.
I've been playing with the definition for a couple weeks, and it's pretty solid. Some big changes though with RC2, so I wouldn't mind a second look over from others.
This is very close to complete. I just need to test:

[ ] FieldArrays
[ ] Reducer plugin
[ ] validate's 2nd parameter (may have been a bug that was fixed)

@rluiten I know you have a couple more properties in your Field component. I haven't included them because you should be able to specify them with the MyFieldProps generic. But curious if I'm missing something here.
@blakeembrey Would love your thoughts and verification that I'm doing the react dependency right.

While personally a TS virgin, I heartily approve of this PR. Let me know when you feel it is complete.

@CarsonF heads up! I'm getting the following error using your tsd.
ERROR in /home/user/typings/modules/redux-form/index.d.ts
(834,58): error TS7006: Parameter 'from' implicitly has an 'any' type.

ERROR in /home/user/typings/modules/redux-form/index.d.ts
(834,64): error TS7006: Parameter 'to' implicitly has an 'any' type.

@CarsonF Using '?' for FormProps definitions is a hack that helps with compilation but it won't work with TS2 strictNullChecks.
For example, TS will complain that this.props.fields can be undefined (since the prop is optional in definition).
We should be using correct HOC definition (merge Props) like Redux' connect:
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/react-redux/react-redux.d.ts#L26-L73
It was added with this commit https://github.com/DefinitelyTyped/DefinitelyTyped/commit/206c964ed1f68ec1778c029123dada84f2aa25c1 by @use-script
It forwards Redux's props (like state selections or dispatch) in addition to the decorated component's props.
That way you don't need to make HOC's props optionals in order to pass compilation.
Unfortunately I don't feel confident enough in my TS skills to provide any kind of help here.
@use-script would you consider helping us? That would be awesome 🎉

@calvin Yeah those are from the arrayMove action creator I just added. @erikras That one isn't documented and I couldn't figure out from source what from and to parameters where supposed to be. Strings?

@bbenezech Ah good point. Ironically I have problems using react-redux's connect function as a decorator. TS has declared that decorators cannot mutate the class definition (more info at TypeScript#4881).
declare type ClassDecorator = <TFunction extends Function>(target: TFunction) => TFunction | void;

I've looked at that block of code several times too and it's hard to wrap my head around. I'll see what I can do to fix this though.
I've gotten around this before with (target: T)  =>  T & DecoratedT. Although that's still a hack too because it doesn't return T only DecoratedT but it satisfies the compiler.

That one isn't documented and I couldn't figure out from source what from and to parameters where supposed to be. Strings?

Integers. The indexes in the array.

@CarsonF
I had 2 issues with redux decorators:

connect()(MyComponent) doesn't require dispatch; Dispatch<any> prop and doesn't satisfy it. You need to add it to your props with a ?
I fixed the issue with export function connect<TOwnProps>(): ComponentDecorator<{dispatch: Dispatch<any>}, TOwnProps>
I then pass TOwnProps like connect<TOwnProps>()(MyComponent)

The other signature overloads won't work without explicitly type casting the connect function (like above) unless TS can infer TOwnProps with mapStateToProps(state, props: TOwnProps).

For redux-form, we should probably require passing ownProps explicitly and keep ReduxFormProps optionals so that we don't need to redeclare them all in user land.
Unless we Inform user there Component's prop type should extend ReduxFormProp.
Which is better for autocomplete.

@CarsonF I have pulled in your type definition and adjusted my code to match names it mostly looks good.
I have temporarily hacked my BaseFieldProps to allow me to pass id, type and value at moment as I need to be able to pass in 'value' as a minimum this way at the moment due to what I believe may be a bug.
One larger issue a bug in Field maybe ?

Currently it appears it is not possible to pass in the 'value' property to Field via the props property.

This works fine for defining members of my radio buttons.
<Field name={name} component="input" id={fieldTrueId} type="radio" value="true" />

This does not work at, it breaks because the 'value' field in props is not set on the creatd input element in the DOM. I think this one may be a bug in Field for handling the property.
<Field name={name} component="input" props={{value: 'false', id: fieldFalseId, type: 'radio'}} />

If this is a bug
One smaller issue.

I think its nicer to have the 'id', 'type', 'value' on BaseFieldProps so they can be passed to Field rather than forced to use the 'props' property. There are probably a long list of other nice to have attributes for different user cases and different components passed to Field so maybe we need to make BaseFieldProps generic ? (not sure how far reaching that change would be)

@rluiten I think you are having different problems. You shouldn't need to set the value on the Field. You should use the defaultValue prop for that field or initialValues on the form config.

@CarsonF it is a radio button, the value is the value that is set to the identifier name if the radio button is checked or inversely in redux-form. This value is looked up by redux-form and used with type and the current model to derive the checked property for the control. I don't see a way around it, at the moment the only extra field on baseFieldProps I need without modifying redux-form is 'value'.

@CarsonF I have created a branch in my fork of redux-form with a very simple change to examples/src/SimpleForm in redux-form repo.
I changed it so that value property is delivered via the props property and the radio button no longer operates correctly. This is why at least at the moment I think we need value on BaseFieldProps
It may be a bug in redux-form Field but I had a dig around but had no luck making progress there.
I am happy to raise it as an issue if you think thats the better avenue ?
Here is reference to the commit  that makes Field not work right for radio input buttons.
https://github.com/rluiten/redux-form/commit/cf115873ce3b14289c27ebf20edd72e7c690cd00
I would have liked to run up a codepen, jsfiddle or jsbin or something with a runnable example but it didn't appear feasible at the moment with no readily accessible version of rc3 of redux-form around.

@bbenezech I've looked again and I don't think this is possible. Yes what you are proposing is more correct, but if it doesn't compile it doesn't matter. See here: https://github.com/DefinitelyTyped/DefinitelyTyped/issues/9951

@erikras I'm trying to address @rluiten's situation. How does Field's defaultValue differ from component's value?

defaultValue is the answer to the question: "What should I use as a value if value is undefined?"
It defaults to '', but if your component wanted a Number, it could be 0, or for a Date, it could be new Date() (today).
So as far as typing is concerned, it can be anything.

Should've reread the doc :facepalm: Did you intend to have value passed into Field directly? Seems like it is bypassing redux store.. Are radio buttons an edge case maybe?

@rluiten You could do this:
import * as React from 'react';
import { Field } from 'redux-form';

// This is how they say to define react components that have generics
// ...I don't really like it either.
type InputField = new () => Field<React.HTMLAttributes>;
const InputField = Field as InputField;

...
render() {
  return <InputField component='input' type='hidden' />;
}

That would work for input, select, and textarea.

Did you intend to have value passed into Field directly? Seems like it is bypassing redux store.. Are radio buttons an edge case maybe?

Bingo. It's only used for radio buttons.

Thanks for having a look at this case, I really don't want a custom type definition when 6 is released.
It appears that InputField as it stands now does not compile for me and I don't understand the error at the spread attribute to fix it at the moment. I would have expected the casting of Field as the new InputField type was the point of the exercise to address types for typescript.
<InputField component="input" {...this.props} />

The errors is.
error TS2606: Property 'value' of JSX spread attribute is not assignable to target property.

@rluiten My example compiles with my definition. Do you not have a value property on your Field class?

notices rc4 @erikras I think you're just trying to give me more work lol

Yeah, sorry about that. Better to have a breaking change than a shitty API. Blah, eggs, blah, omelet.

@CarsonF I never even thought of the fact I still had value on Input tag, that was it.
I still don't understand type errors to frequently thanks for that.

@erikras Trying to address the type of the second parameter, props, of the validate function passed into reduxForm(). Just from runtime debugging I don't know which of these props are "public api" vs "internal/just happen to be passed along".
I was going to start with my FormProps interface and the "custom" props passed to the component. But I see way more than that...it looks like stuff from Config / Form class.
Any clues?

I'm not 100% sure that I understand the question. Can you list them, and I can check off which ones are "public"?

@reduxForm({
  validate: (values, props) => {} // <-- type of props?
})
class MyForm {}

Chrome is showing me these:

anyTouched
array
arrayMove
arrayRemoveAll
blur
change
destroy
dirty
dispatch (could be custom / from me)
focus
form
handleSubmit
initialize
initialized
invalid
onSubmit
pristine
registeredFrields
reset
setSubmitFailed
setSubmitSucceeded
shouldAsyncValidate
startAsyncValidation
startSubmit
stopAsyncValidation
stopSubmit
submitFailed
submitSucceeded
submitting
touch
untouch
updateSyncErrors
valid
validate

It looks like you have identified some failures of the props doc, along with some masking issues.

anyTouched ✅
array missing from doc
arrayMove should not be passed
arrayRemoveAll should not be passed
blur should not be passed
change should not be passed
destroy ✅
dirty ✅
dispatch (could be custom / from me) ✅
focus should not be passed
form ✅
handleSubmit ✅
initialize ✅
initialized should not be passed
invalid ✅
onSubmit - I think you passed this one
pristine ✅
registeredFrields should not be passed
reset ✅
setSubmitFailed should not be passed
setSubmitSucceeded should not be passed
shouldAsyncValidate should not be passed
startAsyncValidation should not be passed
startSubmit should not be passed
stopAsyncValidation should not be passed
stopSubmit should not be passed
submitFailed ✅
submitSucceeded ✅
submitting ✅
touch should not be passed
untouch should not be passed
updateSyncErrors should not be passed
valid ✅
validate should not be passed

Your TypeScript stuff should only address the ones with a ✅, and I need to mask many of them.

See also: propTypes.js

I am just  updating to rc.4 and the latest type def.
@CarsonF getting this error at moment.
ERROR in C:\dev\qk-enhanced\Enhanced.Eylm.MyFamilyLounge\typings\modules\redux-form\index.d.ts
(340,5): error TS2300: Duplicate identifier 'handleSubmit'.

ERROR in C:\dev\qk-enhanced\Enhanced.Eylm.MyFamilyLounge\typings\modules\redux-form\index.d.ts
(342,5): error TS2300: Duplicate identifier 'handleSubmit'.

I am getting one other error to do with a reduxForm() wrapped component but I had that error previously, and had not figured out why yet, so I had not updated to your most recent rc.3 typedef because of it.
Its one of those multiline errors that I really wish I could get a report of these fields conflict or these fields are added or removed :).

@erikras Ok yeah that's what I was thinking.

touch and untouch are listed in the props doc though.
onSubmit was defined in the form config so I think that should be masked as well.

In my FormProps I have asyncValidate and asyncValidating which I did not see in Chrome, that's just because async wasn't enabled in form config right?
Dispatch as well? I haven't mentioned it anywhere else yet..

@rluiten Derp I knew there was a reason I defined it like I did. One sec

@rluiten What's the other problem you're having?

This is top level form that includes ReactRouter.RouteComponentProps<>
and FormProps<>
Error is.
ERROR in ./containers/transition.tsx
(187,4): error TS2345: Argument of type 'typeof Transition & Form<ITransitionFormViewModel, {}, {}>' is not assignable to parameter of type 'ComponentClass<{ stateValue: string; transition: ITransitionFormViewModel; initialValues: ITransi...'.
  Type 'typeof Transition & Form<ITransitionFormViewModel, {}, {}>' is not assignable to type 'StatelessComponent<{ stateValue: string; transition: ITransitionFormViewModel; initialValues: ITr...'.
    Type 'Form<ITransitionFormViewModel, {}, {}>' is not assignable to type 'StatelessComponent<{ stateValue: string; transition: ITransitionFormViewModel; initialValues: ITr...'.
      Type 'Form<ITransitionFormViewModel, {}, {}>' provides no match for the signature '(props?: { stateValue: string; transition: ITransitionFormViewModel; initialValues: ITransitionFormViewModel; editingServices: Object; } & {}, context?: any): ReactElement<any>'

And it it comes from the last line....
export default connect(mapStateToProps, {
    fetchTransition,
    saveTransition,
    leaveTransitionForm,
    saveTransitionGuardianComplete,
})(transitionForm);

Not sure if you can mind read me enough to help, I can probably paste more type info if think it might help, I suspect its going to be bear to track down.

@rluiten Where does RouteComponentProps come from?

Type def for the wrapped component parameters.
export interface TransitionProps extends
    ReactRouter.RouteComponentProps<TransitionListRouteParams, {}>,
    FormProps<VM.ITransitionFormViewModel, {}> {
    stateValue: string;
    transition: IMinimumTransitionFormViewModel; // not needed with redux-form ?
    fetchTransition: fetchTransitionPromise;
    saveTransition: saveTransitionPromise;
    editingServices: VM.ISupportServicesViewModel[];
    leaveTransitionForm: typeof leaveTransitionForm;
    saveTransitionGuardianComplete: saveTransitionGuardianCompletePromise;
}

With typings from "react-router": "registry:dt/react-router#2.0.0+20160621215300",

Yeah...again decorators have problems not being able to mutate and with the issue around TS #8674. Not really a problem I can solve. Try connect<any, any, any>(

This hides the error, just be nice if I didn't have to, but for now I am not spending more effort on it.
export default connect(mapStateToProps, {
    fetchTransition,
    saveTransition,
    leaveTransitionForm,
    saveTransitionGuardianComplete,
})(transitionForm as any);

@CarsonF Here you go. A complete list of the props.

Perfect. Looks like I'm just missing the array one. Is that just for FieldArray's or Field's too?

Looks like I'm just missing the array one. Is that just for FieldArray's or Field's too?

Not sure what you mean. Those props are for the component decorated by reduxForm()(MyForm).

Ah derp. Of course. Still early for me 😅

☕

@erikras array functions in props are documented. Are their function parameters the same as their action creator counterparts (without the form name param)?

Oops. Forgot to push the docs. There

@erikras They don't return functions do they?

@CarsonF No, they are functions. They are bound action creators so will return nothing.

Although the doc notation is pretty confusing. I'll fix...

Used like this, right?
this.props.array.removeAll('foo'); // returns void

🎉 Bingo!

@erikras Would you mind confirming #1342?

Playing with this briefly, I don't think this exports anything to cover 'redux-form/immutable'. I'm going to take a look in the next few days at what needs to be different for that interface, but I suspect not much.
Also doesn't work with the definitelytyped/types-2.0 version of the react typings (https://github.com/DefinitelyTyped/DefinitelyTyped/tree/types-2.0/react) but thats a problem for a few months further down the track once typescript 2.0 is out and those new bindings get merged in. Just seems to be some react interfaces got changed to generic types.

After some brief investigation I think all thats needed for redux-form/immutable to work is to add immutable.d.ts that re-exports the same bindings. The one thing that should probably change in the immutable typings is DataShape should be an Immutable.Map rather than a normal one, but I think the existing type will match an Immutable.Map. I haven't tested any of these assumptions properly, I need to run up a cleaner example project that doesn't have any of the typescript 2.0 stuff mixed in.

I took simple form and tried to get it to work using your latest typings.
https://github.com/erikras/redux-form/blob/v6/examples/simple/src/SimpleForm.js

placeholder it says is not valid (everywhere it is used)
type it says is not valid (everywhere it is used)
value it says is not valid (only used in the radio type, which I think you identified above is an edge case - but as of now, will not compile - so needs handled in some fashion)
id it says is not valid (used on employee field)
reduxForm call at the bottom, error on the parameter value of SimpleForm.  Error is TS2345: Argument of type '(props: any) => Element' is not assignable to parameter of type 'typeof Component'.
Type '(props: any) => Element' provides no match for the signature 'new <P, S>(props?: P, context?: any): Component<P, S>'    This last issue is probably a lack of support for functional stateless component syntax?

@waynebrantley Field has a generic type, if you a wanting a input element, then check out the example above.
reduxForm also has generics. I'll see if I can write up an example

@Errorific Yeah I've been thinking about Immutable as well. I have some concerns but I'll play around with it first and see if I can get it to behave correctly. Can you test for me once I have something?

@waynebrantley Yeah you are. placeholder, type, value, and id are all defined in React.HTMLAttributes.
I understand wanting to be able to take and use the examples directly though. It's a balance. I'm trying to find it. I don't want those HTMLAttributes properties being code-completed for me for a component from Material UI, since it doesn't accept those.

@CarsonF So you are saying I have to define this new InputField type just so I can use this?  Seems pretty messy - I guess that is a typescript thing?  Seems like you would have the Field definition in your typings implement the HtmlAttributes interface.  (In Material UI, you would know not to use them - but they ARE valid in Redux-Form so I think they should be there)
Also, what about the ReduxForm call at the bottom?

@waynebrantley Yes you are right. I was a bit uncomfortable with it to begin with, and hearing the feedback from you and a couple others gave me motivation to work with it some more. I think I have a solution. Commits inbound!
BTW Sorry if I came off short. I appreciate your input! 👍

Making more work for you, @CarsonF. #1449 #1554 😍

@erikras What's up?

To support forms that are stateless component, I had to change the FormDecorator to
interface FormDecorator<FormData extends DataShape, P, S> {
  <T extends (typeof Component)>(component: T | StatelessComponent<P>): T & Form<FormData, P, S>;
}

To suppress errors such as Generic type \'ReactEventHandler\' requires 1 type argument(s)., I added <any> behind those generic types

Fields is missing from definition
interface BaseFieldsProps {
  /**
   * An array of string paths, in dot-and-bracket notation, corresponding to a value
   * in the form values. It may be as simple as 'firstName' or as complicated
   * as contact.billing.address[2].phones[1].areaCode.
   *
   * Required but made optional so interface can be used on decorated components.
   */
  names?: string[];

  /**
   * A Component, stateless function, or string corresponding to a default
   * JSX element.
   *
   * Required but made optional so interface can be used on decorated components.
   */
  component?: ComponentConstructor | "input" | "select" | "textarea",

  /**
   * If true, the rendered component will be available with the
   * getRenderedComponent() method. Defaults to false. Cannot be used if your
   * component is a stateless function component.
   */
  withRef?: boolean;

  /**
   * Formats the value from the Redux store to be displayed in the field input.
   * Common use cases are to format Numbers into currencies or Dates into a
   * localized date format.
   */
  format?: Formatter;

  props?: Object;

  /**
   * Parses the value given from the field input component to the type that you want
   * stored in the Redux store. Common use cases are to parse currencies into Numbers into
   * currencies or localized date formats into Dates.
   */
  parse?: Parser;
}

export class Fields<FieldCustomProps> extends Component<BaseFieldsProps & FieldCustomProps, {}> {
  /**
   * true if the current value is different from the initialized value,
   * false otherwise.
   */
  dirty: boolean;

  /**
   * The names prop that you passed in.
   */
  names: string[];

  /**
   * true if the current value is the same as the initialized value,
   * false otherwise.
   */
  pristine: boolean;

  /**
   * The current value of the field.
   */
  values: { [name: string]: FieldValue };

  /**
   * Returns the instance of the rendered component. For this to work, you must
   * provide a withRef prop, and your component must not be a stateless function
   * component.
   */
  getRenderedComponent(): Component<{[name: string]: WrappedFieldProps} & FieldCustomProps, any>;
}

@erikras @CarsonF
Why did this get closed??

I'm not sure. I'm still working on this. Just having a busy few weeks.

any progress here?

@CarsonF: just trying out your defs. Would you like me to post any issues in this thread, or submit issues in your fork. Simple issue: the Selector interface returns an object, where it can also return a single value  (see http://redux-form.com/6.0.5/examples/selectingFormValues/)

@LaurensRietveld Post them here. I'll try to take a look at that.
I've just been busy lately. Still haven't forgotten about this.

I have the same issues as @waynebrantley, we should be able to use the examples directly without wrappers. The props should be determined by an intersection of component props and Field props ideally.

Any progress with this? Can what's been done so far be merged and raise new tickets for immutable etc...

My fork: https://gist.github.com/bbenezech/8ebbced86c0f357d09e4000635eea275
Complete 100% typesafe redux-form example: https://gist.github.com/bbenezech/528c7057c62300d41f51b212f0a92ad2
If someone need a FieldArray example, I can help too, I have some in my codebase.
Let's write and exchange some examples through gist, TS with redux is non-trivial, and RF6 with the inversion of control was specially challenging for me.
The TS definition should be merged, it works well, thanks a lot @CarsonF 🎊

That's great - @bbenezech could you add the same declarations for "redux-form/react-native" module name too?

@joewood Sorry I've never used RN, I don't know what it implies and I cannot test it.

@MichaelBitard the typings are really similar: I just added some API that was missing and that I needed. All credits to @CarsonF
To push new values, I use
this.props.fields.push({ firstName: 'Sherlock', lastName: 'Holmes' })
// To hydrate I don't do anything special
<PatientForm
  handleSave={this.handleSave}
  initialValues={{ users: [{ firstName: 'Sherlock', lastName: 'Holmes' }] }}
  form="users"
/>

I am not sure I understand the issue and how it is related to typings?

Doesn't seem like this has been merged yet.

Lol, seen em.
I recently replaced most of the bulbs in my house (like recently 2 weeks back) with led's.
Still uhmming about the flouro's in kitchen, and maybe flouro's in other parts of house.
I hate CFL's so had only a couple of them.

@zakdances do you figure out what happens with definitions?

Sooo, after all we doesn't have definitions?

You removed the onSubmitSuccess and onSubmitFail handlers?
They are still in the documentation: http://redux-form.com/6.2.1/docs/api/ReduxForm.md/

onSubmitFail : Function [optional]
A callback function that will be called when a submission fails for whatever reason. It will be called with the following parameters:
errors : Object
The errors that caused the submission to fail.
dispatch : Function
The Redux dispatch function.
submitError : Error
The error object that caused the submission to fail. If errors is set this will be most likely a SubmissionError, otherwise it can be any error or null.
onSubmitSuccess : Function [optional]
A callback function that will be called when a submission succeeds. It will be called with the following parameters:
result : Object
Any result that onSubmit has returned
dispatch : Function
The Redux dispatch function.

is this issue completed?

We're waiting for DefinitelyTyped people to merge my PR. I don't think Eric wants to maintain the definition here.


beeline cannot connect to ti thrift server

Ater deploying TiDB and TiSpark, using beeline to connect ti thrift server will cause problems:
Unable to open a test connection to the given database. JDBC url = jdbc:derby:;databaseName=metastore_db;create=true, username = APP. Terminating connection pool (set lazyInit to true if you expect to start your database after your app). Original Exception: ------
java.sql.SQLException: Failed to start database 'metastore_db' with class loader org.apache.spark.sql.hive.client.IsolatedClientLoader$$anon$1@10cbd567, see the next exception for details.
at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
......
Caused by: ERROR XJ040: Failed to start database 'metastore_db' with class loader org.apache.spark.sql.hive.client.IsolatedClientLoader$$anon$1@10cbd567, see the next exception for details.
at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
at org.apache.derby.impl.jdbc.SQLExceptionFactory.wrapArgsForTransportAcrossDRDA(Unknown Source)
... 111 more
Caused by: ERROR XSDB6: Another instance of Derby may have already booted the database /home/azkaban/metastore_db.
at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.privGetJBMSLockOnDB(Unknown Source)
at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.run(Unknown Source)

Hi, EstaWang.
You may first check whether another spark-shell is running because Derby does not allow multiple connections. Or you may try to switch external database from Derby to MySQL.
Pls ping us if problem still exists.

Great, it worked out!


Users with role "user" can view config

Pelican Version: Latest
Pelican Service:

[X ] Registry

Describe the bug
A clear and concise description of what the bug is.
If I login through CIlogon and gain the role of a user I can view the config.
{"authenticated":true,"role":"user","user":"http://cilogon.org/serverA/users/46022246"}
To Reproduce
Steps to reproduce the behavior.
Go to the registry page: https://osdf-registry.osg-htc.org/view/registry/
Sign in via CIlogon with a non admin account and view the config.
Expected behavior
A clear and concise description of what you expected to happen.
I expect the config to return a 403 which will redirect the user.

Thanks for catching this! I think #963 should fix it though, where we have a "whitelist" for pages that are open to the general public. For now, it's only "/view/director", "/view/registry", and "/view" (for the server selection page), other pages should be protected behind admin auth.

@haoming29 Wouldn't I be able to login as user and hit the api though?

ah you are right. The API is also not protected by admin auth. Will have a separate PR to address all the issues here


Problem update page setting

Laravel Version: last
Voyager Version: last
PHP Version: 5.6
Database Driver & Version: last

Description:
Hi, I installed the latest version of voyager using composer and combined with the current master of github, because with the master alone I never managed to run the panel translations correctly to other languages.
The case is that since I have updated everything seems to work correctly except for the settings page, when clicking, I throw the permission error denied, I have reviewed the permissions of the admin role and all are correct.
What can it be?
And when will the multiligual stable version be ready?
Thank you, you are doing a great job.
Steps To Reproduce:

Click update setting

The issue is because the visit_settings permission does not exist.  All you have to do is add visit_settings to the permissions table, then assign it to your user's role.
That's a change that was merged into master with a recent pull request.  master is very much unstable at this point while we prepare it for the laravel 5.5 release and our own 1.0 release, so we strongly advise against working with it for now.

@fletch3555 Thanks
I waited for the next update.


Parse postBuild references in the Kustomization

#617

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.56%. Comparing base (6e382e9) to head (8e8bee9).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #625      +/-   ##
==========================================
+ Coverage   93.49%   93.56%   +0.07%
==========================================
  Files          19       20       +1
  Lines        1984     2006      +22
==========================================
+ Hits         1855     1877      +22
  Misses        129      129

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


how to change the vm name

calling init creates a box with the name default, how we supposed to set the vm name ?

Set the box_name parameter.
def init(self, box_name=None, box_url=None)

The box name is set and results to:
config.vm.box = "cent7-1.1503"
the vagrant is creating the machine with the vm_name "default". So I want to be able to set the VMNAME not the boxname.
give the root : vagrantfiles/c7-salt-master
it creates this structure:
vagrantfiles/c7-salt-master/.vagrant/machines/default/virtualbox/

In that case, you need to manually add the name configuration to your Vagrantfile, which will depend on which provider you are using. See this for Virtualbox. The option you are looking for is v.name.
There isn't a way to automatically generate a Vagrantfile using python-vagrant at the moment with provider configuration.

From the Vagrant Docs,

You can customize the name that appears in the VirtualBox GUI by setting the name property. By default, Vagrant sets it to the containing folder of the Vagrantfile plus a timestamp of when the machine was created.

So you could also simply change the name of the directory you are calling vagrant up in.

Ok, because on the subsequent calls to status and up etc, I can pass in the vm_name which has to be default.
My solution is to manage multiple vagrant root dirs.
Thanks for the clarification.
mike

Generating or modifying Vagrantfiles is not in the scope of the python-vagrant project currently.  Thanks for your comments @omoman


core/injector/application_injector.cpp

https://github.com/themesberg/simple-bootstrap-5-dashboard/issues/7#issue-1650886148

Hello


Add "What is AGILE?" link

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

This looks like a good link to add to the page.


[BUG]: iOS looping/repeat has noticable gap between playbacks.

Version
6.2.0
What platforms are you having the problem on?
iOS
System Version
17.5.1
On what device are you experiencing the issue?
Real device
Architecture
Old architecture
What happened?
Looping using repeat has an audio gap between tracks. File type is .m4a. No problems on react-native-sound though similar issue on expo-av.  File is 41s long so I don't believe it's a buffering issue. No such gap on Android.
Reproduction
repository link
Reproduction
Step to reproduce this bug are:

Use file type with no gap like .m4a
Load file from MainBundle with'file:/${fs.MainBundlePath}/${filename}' (Will look something like file://private/var/containers/Bundle/Application/CCB722FF-4134-463F-8969-C481A84CAE51/{yourapp}/{filename}.m4a
Render Video component, set repeat property to true, wait for file to repeat.
You'll hear a noticeable gap on iOS between the end of you playback and the beginning of the next.

I think this old PR is a good clue to start investigate the issue ...
https://github.com/TheWidlarzGroup/react-native-video/pull/1799/files

This is caused because of "seeking" - when video is ending we seek it to start and it seems to be slow - not sure if we can do anything about it


fix(android): Fix bug caused by negative length reported for an asset (CB-13245)

Platforms affected
Android
What does this PR do?
Check the length of CordovaResourceApi.OpenForReadResult in readFileAtURL() to fix loading Android assets with a length greater than FileReader.READ_CHUNK_SIZE. When the length returned is < 0, use InputStream.available() to get the length of compressed assets.
What testing has been done on this change?
Fixes a bug in one of my apps when loading a large .json file into a string.
Checklist

[X] Reported an issue in the JIRA database
[X] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform affected.
[ ] Added automated test coverage as appropriate for this change.

This tripped me up the past few days. I also set up an app to demo this bug:
https://github.com/AnthonyWard/cordova-file-plugin-bug
One line of code it seems can fix it more "upstream" than this, but I don't know if it's a good idea:
cordova-android -> CordovaResourceApi.java -> OpenForReadResult there is one path (in the catch) that leaves the length as -1 causing the defect
case URI_TYPE_ASSET: {
                String assetPath = uri.getPath().substring(15);
                AssetFileDescriptor assetFd = null;
                InputStream inputStream;
                long length = -1;
                try {
                    assetFd = assetManager.openFd(assetPath);
                    inputStream = assetFd.createInputStream();
                    length = assetFd.getLength();
                } catch (FileNotFoundException e) {
                    // Will occur if the file is compressed.
                    inputStream = assetManager.open(assetPath);
                }
                String mimeType = getMimeTypeFromPath(assetPath);
                return new OpenForReadResult(uri, inputStream, mimeType, length, assetFd);
            }

Adding length = inputStream.available(); in the catch fixes the issue for me, but I'm not a java developer so can't evaluate if that's a bad idea for another reason.

This should be fixed in Cordova, not in File.

@infil00p  Is there an issue reported in Cordova? Can we get the ball rolling on this?
It is absolutely unacceptable that such trivial bug exists for such a common functionality on a mature platform such as cordova.

This should be resolved now in version 7.1.1 of cordova-androd
CB-13923 (android) fix -1 length for compressed files
https://github.com/apache/cordova-android/blob/7.1.x/RELEASENOTES.md

Hey, I just fixed the problem that caused Android tests to fail in master. Could you rebase this PR please? This should get rid of the Android failures and possibly fix all test failures for this PR.

Closing because of https://github.com/apache/cordova-plugin-file/pull/217#issuecomment-370883325 and https://github.com/apache/cordova-plugin-file/pull/217#issuecomment-404457427 which indicates this should and has been fixed in cordova-android.
Please let me know if this is not true and we should reopen this PR. Thanks!


update logic and styling for index pages

This PR updates the logic for generating index pages and makes a few minor styling adjustments. Essentially this way of generating the index pages allows us customizability while also being able to take advantage of automating the process a bit since there will be external contributors, some of this should be automated, so they don't have to really know or worry about this
This should be reviewed with polkadot-docs PR: https://github.com/polkadot-developers/polkadot-docs/pull/200

Fixed your suggestion on the other PR here: https://github.com/polkadot-developers/polkadot-docs/pull/200#pullrequestreview-2454137773

⚠ This will need to be merged alongside polkadot-docs PR# 200, otherwise it'll break things


remove black from dev dependencies

to make it intuitive for contributors to use ruff formatter

The correct thing to do would be to set up pre-commit

@timoniq I agree with this proposal, but the typegen is used a black formatter. Black formats types much better than ruff.


New service design changes and other features in TCP module

Purpose

Design doc

Task

[x] Service Type Changes to Socket Module
[x] Introduce readBytes and writeBytes to Socket Client
[x] Introduce Transport Security to TCP Sockets
[x] Complier plugin to validate service types

Closing the issue as this is done.


Cannot open content_image

I'm trying to run on a vm and i'm getting this error:
sudo th neural_style.lua -gpu -1 -style_image A.jpg -content_image B.jpg

[libprotobuf WARNING google/protobuf/io/coded_stream.cc:505] Reading dangerously large protocol message.  If the message turns out to be larger than<PHONE_NUMBER> bytes, parsing will be halted for security reasons.  To increase the limit (or to disable these warnings), see CodedInputStream::SetTotalBytesLimit() in google/protobuf/io/coded_stream.h.
[libprotobuf WARNING google/protobuf/io/coded_stream.cc:78] The total number of bytes read was 574671192
Successfully loaded models/VGG_ILSVRC_19_layers.caffemodel
conv1_1: 64 3 3 3
conv1_2: 64 64 3 3
conv2_1: 128 64 3 3
conv2_2: 128 128 3 3
conv3_1: 256 128 3 3
conv3_2: 256 256 3 3
conv3_3: 256 256 3 3
conv3_4: 256 256 3 3
conv4_1: 512 256 3 3
conv4_2: 512 512 3 3
conv4_3: 512 512 3 3
conv4_4: 512 512 3 3
conv5_1: 512 512 3 3
conv5_2: 512 512 3 3
conv5_3: 512 512 3 3
conv5_4: 512 512 3 3
fc6: 1 1 25088 4096
fc7: 1 1 4096 4096
fc8: 1 1 4096 1000
/usr/local/bin/luajit: /usr/local/share/lua/5.1/image/init.lua:200: cannot open file <B.jpg> for reading
stack traceback:
        [C]: in function 'load'
        /usr/local/share/lua/5.1/image/init.lua:200: in function 'loader'
        /usr/local/share/lua/5.1/image/init.lua:332: in function 'load'
        neural_style.lua:59: in function 'main'
        neural_style.lua:376: in main chunk
        [C]: in function 'dofile'
        /usr/local/lib/luarocks/rocks/trepl/scm-1/bin/th:131: in main chunk
        [C]: at 0x00406260

Any idea on whats wrong?

Looks like the file B.jpg doesn't exist.

Just in case @renatoakamur is not familiar with Linux/Unix: these kind of operating systems use a case-sensitive file system. Meaning: b.jpg is not equal to B.jpg or B.JPG.

I thought the "B.jpg" file existed and was in the folder. @dodekeract I already know about this difference, thanks for your reply.
Just in case, I've changed the image files and tried again, now i've got this error:
vagrant@data-science-toolbox:~/neural-style$ ls
A.jpg  B.jpg  examples  INSTALL.md  LICENSE  loadcaffe_wrapper.lua  models  neural_style.lua  README.md
vagrant@data-science-toolbox:~/neural-style$ th neural_style.lua -gpu -1 -style_image A.jpg -content_image B.jpg
[libprotobuf WARNING google/protobuf/io/coded_stream.cc:505] Reading dangerously large protocol message.  If the message turns out to be larger than<PHONE_NUMBER> bytes, parsing will be halted for security reasons.  To increase the limit (or to disable these warnings), see CodedInputStream::SetTotalBytesLimit() in google/protobuf/io/coded_stream.h. [libprotobuf WARNING google/protobuf/io/coded_stream.cc:78] The total number of bytes read was 574671192
Successfully loaded models/VGG_ILSVRC_19_layers.caffemodel
conv1_1: 64 3 3 3
conv1_2: 64 64 3 3
conv2_1: 128 64 3 3
conv2_2: 128 128 3 3
conv3_1: 256 128 3 3
conv3_2: 256 256 3 3
conv3_3: 256 256 3 3
conv3_4: 256 256 3 3
conv4_1: 512 256 3 3
conv4_2: 512 512 3 3
conv4_3: 512 512 3 3
conv4_4: 512 512 3 3
conv5_1: 512 512 3 3
conv5_2: 512 512 3 3
conv5_3: 512 512 3 3
conv5_4: 512 512 3 3
fc6: 1 1 25088 4096
/usr/local/bin/luajit: ./loadcaffe_wrapper.lua:61: $ Torch: not enough memory: you tried to allocate 0GB. Buy new RAM! at /tmp/luarocks_torch-scm-1-1663/torch7/lib/TH/THGeneral.c:210
stack traceback:
        [C]: in function 'loadModule'
        ./loadcaffe_wrapper.lua:61: in function 'load'
        neural_style.lua:54: in function 'main'
        neural_style.lua:376: in main chunk
        [C]: in function 'dofile'
        /usr/local/lib/luarocks/rocks/trepl/scm-1/bin/th:131: in main chunk
        [C]: at 0x00406260
vagrant@data-science-toolbox:~/neural-style$

After that I've added "-image_size 256" as you @jcjohnson suggested in another ticket, it seems working now (still on Interation 300/1000 atm, i'm waiting to finish).

Looks like you just don't have enough memory to run with an image size of 512. Glad it's working for you now!

Is the default value 512? Because I've got working with 512 (but using other files)..
Btw, how much ram do you think is a reasonable value to use under a vagrant/virtualbox enviroment (ubuntu) without a gpu? Atm I'm using 4gb on this vm.


The preview window becomes black (empty/blank) and weird. (HLSL)

As the pixel inspect window shown, the pixel's color is not black, but the preview window is blank.
But the below one works as expected:

other details:
HLSL Project

Sorry for slow response.
This could be caused by two things:

There was some form of a bug in SHADERed with HLSL shaders that would happen when one of the textures were not used and so it was optimized out of the code; the bindings would be shifted and the wrong texture would be sampled. Haven't found a solution for this one. Though, as seen in your screenshots, you are using both tex0 and tex1 so I believe this shouldn't happen in your case.
Either something was not bound properly by SHADERed or there's some shader code error.

I'd need the project files in order to tackle this issue.

hmmm, I can confirm that it is caused by a large array (the data).
I have deleted the original project, but reproduced it on version 1.5.3.
When the data contains only 40 elements, everything works fine.

When the length increases to 4096, we will get the weird result without any compiling error or warning.

When the length increases to 409600, the Shadered will crashed directly.

Not sure if it's even allowed to define such big arrays. That's why there are buffers -- use a buffer object in your project.
This is not a bug on my end. Thanks for reporting however!


Generate Random Strings Matching Predefined Pattern or Format for Enhanced Flexibility and Control

Is your feature request related to a problem? Please describe.
It is not possible to get a random string based on pattern or format provided. For example provide "A0" as a pattern where A represents an uppercase letter and 0 represents a digit, and get something like "H7"
Describe the solution you'd like
It would be nice if the package provides a method like generateWithPattern(pattern) that takes a pattern as input and generates a random string based on that pattern.
Describe alternatives you've considered
One possible approach could be adding pattern as an argument in the options object.

For enhancement Issues, Please have a discussion first in discussion site.


Make use of num_cpus passed in from ilab to set num_procs

This came up in PR #120.
We are hard coding num_procs to 8. We expose this as a tunable via the CLI, but are currently not using the value anywhere.

Confirmed we're still just using this default:
    # The default number of processes to use when performing parallel operations
    # on individual datasets
    DEFAULT_DATASET_NUM_PROCS = 8


Access_token received from the token endpoint "/vc/connect/token" is invalid

I was trying to receive the access token from the token endpoint then I have received this one in response
{"request":{"configuration":{"authorizationEndpoint":"https:\/\/controller.vc.identity.ky\/vc\/connect\/authorize","tokenEndpoint":"https:\/\/controller.vc.identity.ky\/vc\/connect\/token"},"clientId":"app-auth","nonce":"aeBgbM9fcpwQYk4EQxjOOf0JuXR1QB9k","grantType":"authorization_code","redirectUri":"net.openid.appauthdemo:\/oauth2redirect","authorizationCode":"95b50d0b-a995-4ea2-b360-70a663fecd98","additionalParameters":{}},"token_type":"Bearer","access_token":"invalid","id_token":"eyJhbGciOiJSUzI1NiIsImtpZCI6ImI1NDU3MDhhNjBlNzIyODJhZDU4NTFiYTk0YmQwYmY4IiwidHlwIjoiSldUIn0.eyJuYmYiOjE2MDA0MjIwMjEsImV4cCI6MTYwMDQzMjAyMSwiaXNzIjoiaHR0cHM6Ly9jb250cm9sbGVyLnZjLmlkZW50aXR5Lmt5IiwiYXVkIjoiYXBwLWF1dGgiLCJwcmVzX3JlcV9jb25mX2lkIjoidmVyaWZpZWQtZW1haWwiLCJhY3IiOiJ2Y19hdXRobiIsIm5vbmNlIjoiYWVCZ2JNOWZjcHdRWWs0RVF4ak9PZjBKdVhSMVFCOWsiLCJlbWFpbCI6Imxva2VuYXRoQGtsaXpvcy5jb20iLCJzdWIiOiJsb2tlbmF0aEBrbGl6b3MuY29tIiwiaWF0IjoxNjAwNDIyMDIxfQ.fvQG3mFQ-PYV7WUWiW2HjRMU228n6TL2ZCl5Tu8iWmt9V2dAVmH_s4kV2uF6pg20tqMx6pj6JzTI55MLnCkRvr0WhMh459850GiU_BK1q-_g_3CWFaHi1XNssQVJJ9L4ChGTqM41e2RKIpzGCgdIE1ZLfXOwQdx08H-35fTSxP_Zj3UEqYfayxHjhujsVKg7Y6v-wd6D1d_TH3CHaVRQBqDPVhU24y0_tex_gozXL-_UYCZ1KDuYDbLd1Djmk1TnA18m3wcdniBlDUzlLGDjfpO294PBJvO7py1h_WFRps-bZJvSdFDWyjfDpfXmOO9Jf9aEft2D2IC3ZB8HctTxtA","additionalParameters":{}}
So here the access token is invalid, after serching on the code i have found the the access token is hard-coded as invilid in the tokenEndpointResult.cs file line no. 71.
await context.Response.WriteJsonAsync(              new                 {                     access_token = "invalid",                     id_token = token,                     token_type = "Bearer"                 });
So, without this access_token I can't use the user-info endpoint, is there any way to access the user-info endpoint.

@esune -- this seems weird.  Can you take a look, please?

@dipghoshraj vc-authn-oidc does not have a userInfo endpoint implementation, since it is stateless (there is no user database).

@esune thanks for clearing my query, so to access protected resources at Resource Servers, we need to pass the access token for this. Any information related to this will be very helpful.

@dipghoshraj you are right, vc-authn-oidc does not return an access token, it just returns an identity token.
I am unsure about the reason driving this choice and will have to further investigate on whether it is a missing feature or a limitation, however you should be able to achieve what you are describing by authenticating using vc-authn-oidc through an AIM system such as Keycloak acting as mediator. This way your OIDC authentication endpoints would be with Keycloak and vc-authn-oidc would just be an Identity Provider you can choose when authenticating.

Thank you @esune .


Publish on package manager repository - vcpkg

I'd like to request to publish the package on vcpkg repository to enable seamless integration with projects using this package manager.

Thanks for raising the issue! I will take care of that

I could take this issue

I am currently working on this, I need some changes in the CMakeLists.txt (mainly install) and then I could publish a port on vcpkg, which includes a patch for the CMakeLists to use fmt from vcpkg if using the faker-cxx via vcpkg. If interested, I can submit a PR but I need a CMake guru to review it since my CMake understanding is limited

I am not a guru but I will try to review it :)

Hello @mostsignificant are you working on this?

@cieslarmichal Yes, please review my PR - some little caveats though, especially on MacOS X

looks good, merged :) what are next steps here?

good job :fire:

I will submit a PR for vcpkg tomo, I have already prepared the files (vcpkg.json, portfile.cmake, usage, and two patch files) for a port. If accepted, I will add a section about vcpkg in your README

Okay, I already opened the Draft PR, you can check it out here: https://github.com/microsoft/vcpkg/pull/38583

Nice

Would it make sense for googletest to also be a dependency of faker-cxx when using vcpkg?

Good question, I don't think we need that there

We could add it as vcpkg port "feature" - which means you could build with tests enabled and it also includes googletest in this case. I am not sure about doing the same for fmt so users must only activate it when doing a Apple clang 12 build

Almost finished with the initial version, but I need some help here:
https://github.com/microsoft/vcpkg/pull/38583/files/64afeaec8a9f0f3cddd3b309f25851dfd6c9f9f7#diff-589dc7ff9a891c76d3949346ccbe3848bd4289668fde9f8c0cc4bbd2ce04a3ef
Does this mean that faker-cxx needs an extra Config.cmake file? In this case I would need to create them in faker-cxx first and then the referenced version in the vcpkg ports needs to be updated. But I don't know how to write those config.cmake files, I initially thought the install commands in the CMakeLists.txt file take care of it

Hey, honestly I have no idea how to deal with it. I will ask in our discord channel.

I'm having a read of this right now CMake Export Configuration
Still trying to figure it out, but it seems like it's along the lines of what we need to fix. Posting it incase you guys understand it better

请继续这工作，vcpkg真很方便


Just cloned and installed, but dist folder not beign created

Hello i just cloned the repository and created a new app, but when running "npm run dev" it just loads a white background with no app, and no css, i have triying to check what is happening but nothing seems to load.

Using Mac OS X el Capitan, with node v5.10.1, npm 3.3.10.
I created another new project following all the instructions but the problem remains.

I cannot reproduce it. :\
Make sure the webpack server worked, or provide error logs.

Thisis the full log, still noyt creates the dist folder, and dows not load

<EMAIL_ADDRESS>dev /Users/claudio.castro/Code/xxx/your-project-name
concurrently --kill-others "npm run hot-server" "npm run start-hot"

[0]
[0] ><EMAIL_ADDRESS>hot-server /Users/claudio.castro/Code/xxx/your-project-name
[0] > node server.js
[0]
[1]
[1] ><EMAIL_ADDRESS>start-hot /Users/claudio.castro/Code/xxx/your-project-name
[1] > cross-env HOT=1 NODE_ENV=development electron ./

[1] 2016-04-08 11:16:01.448 Electron Helper[4344:505128] Couldn't set selectedTextBackgroundColor from default ()

<EMAIL_ADDRESS>dev /Users/claudio.castro/Code/xxx/your-project-name
concurrently --kill-others "npm run hot-server" "npm run start-hot"

[0]
[0] ><EMAIL_ADDRESS>hot-server /Users/claudio.castro/Code/xxx/your-project-name
[0] > node server.js
[0]
[1]
[1] ><EMAIL_ADDRESS>start-hot /Users/claudio.castro/Code/xxx/your-project-name
[1] > cross-env HOT=1 NODE_ENV=development electron ./

[1] 2016-04-08 11:16:01.448 Electron Helper[4344:505128] Couldn't set selectedTextBackgroundColor from default ()

As shown in there, it does not generate any error, but when installing i get some warnings that might be related to the problem
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs version 3 and before will fail on newer node releases. Please update to<EMAIL_ADDRESS>as soon as possible.
npm WARN deprecated<EMAIL_ADDRESS>this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs version 3 and before will fail on newer node releases. Please update to<EMAIL_ADDRESS>as soon as possible.
npm WARN deprecated<EMAIL_ADDRESS>this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs version 3 and before will fail on newer node releases. Please update to<EMAIL_ADDRESS>as soon as possible.
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
Thanks for your help

Looks webpack server no problems, and development mode doesn‘t create dist folder, it will built in http://localhost:3000/dist/bundle.js.
Could you please provide logs of DevTools console tab?

Does not show on Ctrl + H, webkit tools only shows that that url cannot be found


WYSIWYG editor issues when tui element in

Describe the bug
Adding the editor to a page within a
 element will cause the WYSIWYG to behave incorrectly when typing in a blank editor
Typed content is added as "plain text" instead of as wrapped

To Reproduce
Steps to reproduce the behavior:

Example editor wrapped in a

(editor)

Click on WYSIWYG
Select all content and remove (should have a blank editor)
Type "plain text"
Hit enter (if you inspect the text you'll see it's not wrapped within a

Select the text and change to be a header
Uncaught TypeError: Illegal invocation (screenshot) is thrown

Expected behavior
WYSIWYG adds text wrapped in a

Selecting a header option changes the "plain text" to be a styled header
Screenshots

Desktop (please complete the following information):

OS: iOS
Browser chrome
Version 86

@Ertyguy I checked that the problem occurred. Using a table or list as an editor wrapper is not recommended, but it is a bug and needs to be fixed. There is a PR that solves this problem, so I'll check it out and let you know again. Thanks for reporting the issue.

I just spent some hours to figure this out. Minimal reproduction:
<!DOCTYPE html>

        <meta charset="utf-8">
        <link rel="stylesheet" type="text/css" href="https://cdnjs.cloudflare.com/ajax/libs/codemirror/5.48.4/codemirror.css">
        <link rel="stylesheet" type="text/css" href="https://nhn.github.io/tui.editor/latest/dist/cdn/toastui-editor.css">

Simply select text and try make it heading. OR paste some text and do the same.  But if text is typed everything works.

Using a table or list as an editor wrapper is not recommended

It can be generated html or ignorant designer.

I just spent some hours to figure this out. Minimal reproduction:
<!DOCTYPE html>

        <meta charset="utf-8">
        <link rel="stylesheet" type="text/css" href="https://cdnjs.cloudflare.com/ajax/libs/codemirror/5.48.4/codemirror.css">
        <link rel="stylesheet" type="text/css" href="https://nhn.github.io/tui.editor/latest/dist/cdn/toastui-editor.css">

Simply select text and try make it heading. OR paste some text and do the same.  But if text is typed everything works.

Using a table or list as an editor wrapper is not recommended

It can be generated html or ignorant designer.

Same problem here. Looking foward to this fix.

Same problem here. Looking foward to this fix.

I am also facing the same problem. I have done some debug and I am stuck in this part of the code:
`function findAll(element, selector) {
var nodeList = toArray_default()(element.querySelectorAll(selector));
if (nodeList.length) {
return nodeList;
}
return [];
}`
In my particular case the problem occurs when this part of the code is called:
_proto._unwrapBlockInTable = function _unwrapBlockInTable() {                 var blocks = dom.findAll(this.wwe.getBody(), 'td div,th div,tr>br,td>br,th>br');
The findAll method, instead of returning the NodeList that match the "selector" and belongs to the "element" node, it is returning all document elements that match the "selector".
Think this is the correct way JavaScript works. Should we use the ":scope" pseudo-class? (Not supported on IE)

I am also facing the same problem. I have done some debug and I am stuck in this part of the code:
`function findAll(element, selector) {
var nodeList = toArray_default()(element.querySelectorAll(selector));
if (nodeList.length) {
return nodeList;
}
return [];
}`
In my particular case the problem occurs when this part of the code is called:
_proto._unwrapBlockInTable = function _unwrapBlockInTable() {                 var blocks = dom.findAll(this.wwe.getBody(), 'td div,th div,tr>br,td>br,th>br');
The findAll method, instead of returning the NodeList that match the "selector" and belongs to the "element" node, it is returning all document elements that match the "selector".
Think this is the correct way JavaScript works. Should we use the ":scope" pseudo-class? (Not supported on IE)

have the same problem..;;;


Also show categories of posts

Currently the tags of posts are displayed, and it will be nice to display categories as well.

Well, personally I no longer use categories or tags now (just a title and body, and done). I used to use them, and categories are like higher-level tags. So while I do agree with you that tags could be sufficient, I think there will be users who are like the past me.

Interesting to hear that you no longer use either tags or categories. Fast and simple 🤣
I will consider to add support for displaying categories (for cases where the user adds them in the frontmatter), but probably won't add them to the demo posts as I'm trying to keep the demo interface fairly clean and minimal.

That makes perfect sense. Thanks!

💯


Lepiter: Add Browse Issue on GitHub and Copy Issue Number Buttons

Lepiter GitHub Issue snippets should provide a way to browse an issue on GitHub and copy issue number buttons

New two buttons in the context menu:


Fix: Reduce visibility to protected

This PR

[x] removes visibility of setUp() in tests to protected

:information_desk_person: There's no need to increase the visibility, is there? For reference, see PHPUnit_Framework_TestCase::setUp().

Since there will be no classes extending these, there's no reason to change visibility. While the PHPUnit API defines them as protected, the versions in the test cases will still be called when defined as public. Since there's no technical rationale behind the change, I'd rather leave as-is, particularly as there are new test classes in the develop branch already that also define public setup()/tearDown() methods.

@weierophinney
So why is the visibility changed in the first place?


Update code to remove call

Summary
Remove redundant call to ThrowIfCancellationRequested.
Fixes #27419

This LGTM @IEvangelist
You can :shipit: when ready.

Thanks @BillWagner, but I cannot merge it as the snippets-build is failing. Any ideas on how to address that? These errors seem unrelated:
Error:  D:\a\docs\docs>dotnet build "D:\a\docs\docs\samples\snippets\csharp\VS_Snippets_Misc\tpl_parallel\cs\simpleforeach.csproj"  Microsoft (R) Build Engine version 17.0.0+c9eb9dd64 for .NET Copyright (C) Microsoft Corporation. All rights reserved.    Determining projects to restore...   Restored D:\a\docs\docs\samples\snippets\csharp\VS_Snippets_Misc\tpl_parallel\cs\simpleforeach.csproj (in 106 ms). D:\a\docs\docs\samples\snippets\csharp\VS_Snippets_Misc\tpl_parallel\cs\parallel_file.cs(51,20): error CA2208: Call the ArgumentException constructor that contains a message and/or paramName parameter [D:\a\docs\docs\samples\snippets\csharp\VS_Snippets_Misc\tpl_parallel\cs\simpleforeach.csproj] D:\a\docs\docs\samples\snippets\csharp\VS_Snippets_Misc\tpl_parallel\cs\simpleparallelfor.cs(124,48): warning CA1416: This call site is reachable on all platforms. 'Console.WindowWidth.set' is only supported on: 'windows'. [D:\a\docs\docs\samples\snippets\csharp\VS_Snippets_Misc\tpl_parallel\cs\simpleforeach.csproj]  Build FAILED.  D:\a\docs\docs\samples\snippets\csharp\VS_Snippets_Misc\tpl_parallel\cs\simpleparallelfor.cs(124,48): warning CA1416: This call site is reachable on all platforms. 'Console.WindowWidth.set' is only supported on: 'windows'. [D:\a\docs\docs\samples\snippets\csharp\VS_Snippets_Misc\tpl_parallel\cs\simpleforeach.csproj] D:\a\docs\docs\samples\snippets\csharp\VS_Snippets_Misc\tpl_parallel\cs\parallel_file.cs(51,20): error CA2208: Call the ArgumentException constructor that contains a message and/or paramName parameter [D:\a\docs\docs\samples\snippets\csharp\VS_Snippets_Misc\tpl_parallel\cs\simpleforeach.csproj]     1 Warning(s)     1 Error(s)  Time Elapsed 00:00:11.12
Error:  D:\a\docs\docs>dotnet build "D:\a\docs\docs\samples\snippets\visualbasic\VS_Snippets_Misc\tpl_parallel\vb\simpleforeach.vbproj"  Microsoft (R) Build Engine version 17.0.0+c9eb9dd64 for .NET Copyright (C) Microsoft Corporation. All rights reserved.    Determining projects to restore...   Restored D:\a\docs\docs\samples\snippets\visualbasic\VS_Snippets_Misc\tpl_parallel\vb\simpleforeach.vbproj (in 86 ms). D:\a\docs\docs\samples\snippets\visualbasic\VS_Snippets_Misc\tpl_parallel\vb\fileiteration08.vb(54,50): error CA2208: Call the ArgumentException constructor that contains a message and/or paramName parameter [D:\a\docs\docs\samples\snippets\visualbasic\VS_Snippets_Misc\tpl_parallel\vb\simpleforeach.vbproj] D:\a\docs\docs\samples\snippets\visualbasic\VS_Snippets_Misc\tpl_parallel\vb\simpleparallelfor.vb(104,52): warning CA1416: This call site is reachable on all platforms. 'Public Shared Overloads Property Set WindowWidth(value As Integer)' is only supported on: 'windows'. [D:\a\docs\docs\samples\snippets\visualbasic\VS_Snippets_Misc\tpl_parallel\vb\simpleforeach.vbproj]  Build FAILED.  D:\a\docs\docs\samples\snippets\visualbasic\VS_Snippets_Misc\tpl_parallel\vb\simpleparallelfor.vb(104,52): warning CA1416: This call site is reachable on all platforms. 'Public Shared Overloads Property Set WindowWidth(value As Integer)' is only supported on: 'windows'. [D:\a\docs\docs\samples\snippets\visualbasic\VS_Snippets_Misc\tpl_parallel\vb\simpleforeach.vbproj] D:\a\docs\docs\samples\snippets\visualbasic\VS_Snippets_Misc\tpl_parallel\vb\fileiteration08.vb(54,50): error CA2208: Call the ArgumentException constructor that contains a message and/or paramName parameter [D:\a\docs\docs\samples\snippets\visualbasic\VS_Snippets_Misc\tpl_parallel\vb\simpleforeach.vbproj]     1 Warning(s)     1 Error(s)  Time Elapsed 00:00:01.96

Yikes, why was it this bad before you fixed it?
LGTM

There is still a bunch of really old content that was ported and then untouched, it's kind of a mess.


Can't run latest linux release

https://github.com/streamingfast/substreams-sink-kv/releases/download/v0.1.2/substreams_sink_kv_linux_x86_64.tar.gz
It looks like it's dynamically linked and because of that I can't run it in docker
Getting this error: qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory
Note: previsous version v0.1.1 worked fine

Hello @YaroShkvorets .
I was not able to reproduce the issue in a pod running ubuntu 20.04:
colin@reader-1:~$ wget https://github.com/streamingfast/substreams-sink-kv/releases/download/v0.1.2/substreams_sink_kv_linux_x86_64.tar.gz
--2023-03-07 16:00:17--  https://github.com/streamingfast/substreams-sink-kv/releases/download/v0.1.2/substreams_sink_kv_linux_x86_64.tar.gz
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://objects.githubusercontent.com/github-production-release-asset-2e65be/585704265/9f1f5c9a-45a3-40e2-86a0-77e8e1d0d247?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20230307%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230307T160018Z&X-Amz-Expires=300&X-Amz-Signature=d5fa0ae0ac06a52e5fcae710e51e2b3b7e16e2fb4fc7a2f5c7bd13aa2244a5a6&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=585704265&response-content-disposition=attachment%3B%20filename%3Dsubstreams_sink_kv_linux_x86_64.tar.gz&response-content-type=application%2Foctet-stream [following]
--2023-03-07 16:00:18--  https://objects.githubusercontent.com/github-production-release-asset-2e65be/585704265/9f1f5c9a-45a3-40e2-86a0-77e8e1d0d247?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20230307%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230307T160018Z&X-Amz-Expires=300&X-Amz-Signature=d5fa0ae0ac06a52e5fcae710e51e2b3b7e16e2fb4fc7a2f5c7bd13aa2244a5a6&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=585704265&response-content-disposition=attachment%3B%20filename%3Dsubstreams_sink_kv_linux_x86_64.tar.gz&response-content-type=application%2Foctet-stream
Resolving objects.githubusercontent.com (objects.githubusercontent.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to objects.githubusercontent.com (objects.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 13763459 (13M) [application/octet-stream]
Saving to: ‘substreams_sink_kv_linux_x86_64.tar.gz’

substreams_sink_kv_linux_x86_64.tar.gz  100%[===============================================================================>]  13.12M  --.-KB/s    in 0.1s

2023-03-07 16:00:18 (122 MB/s) - ‘substreams_sink_kv_linux_x86_64.tar.gz’ saved [13763459/13763459]

colin@reader-1:~$ tar -xf substreams_sink_kv_linux_x86_64.tar.gz
colin@reader-1:~$ ls
LICENSE  README.md  substreams-sink-kv  substreams_sink_kv_linux_x86_64.tar.gz
colin@reader-1:~$ ./substreams-sink-kv
Substreams KV Sink

Usage:
  substreams-sink-kv [command]

Available Commands:
  completion  Generate the autocompletion script for the specified shell
  help        Help about any command
  run         Fills a KV store from a substreams output and runs a Connect-Web listener

Flags:
      --delay-before-start duration   [OPERATOR] Amount of time to wait before starting any internal processes, can be used to perform to maintenance on the pod before actually letting it starts
  -h, --help                          help for substreams-sink-kv
      --metrics-listen-addr string    [OPERATOR] If non-empty, the process will listen on this address for Prometheus metrics request(s) (default "localhost:9102")
      --pprof-listen-addr string      [OPERATOR] If non-empty, the process will listen on this address for pprof analysis (see https://golang.org/pkg/net/http/pprof/) (default "localhost:6060")
  -v, --version                       version for substreams-sink-kv

Use "substreams-sink-kv [command] --help" for more information about a command.

What environment are you running docker on, and which ubuntu are you using as your base image?

Try to docker compose up this docker-compose.yaml for example:
version: '3'
services:
  substreams-sink-test:
    image: ubuntu:latest
    container_name: "test-sink"
    command:
      - sh
      - -c
      - |
        apt-get update && apt-get install -y wget
        wget https://github.com/streamingfast/substreams-sink-kv/releases/download/v0.1.2/substreams_sink_kv_linux_x86_64.tar.gz -O - | tar -xz -C /usr/local/bin;
        substreams-sink-kv

Then replace the binary url with earlier version https://github.com/streamingfast/substreams-sink-kv/releases/download/v0.1.1/substreams-sink-kv_0.1.1_linux_x86_64.tar.gz - and it works

ok thank you, i can now reproduce this issue.  are you also running this docker compose on a mac?

Yes, but I also had this issue when running it on Debian 11

when you launch your docker compose up command, you should see the amd64 version of ubuntu being downloaded
test-sink  | Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
test-sink  | Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
test-sink  | Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [107 kB]
test-sink  | Get:5 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 Packages [5557 B]
test-sink  | Get:6 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages [855 kB]
test-sink  | Get:7 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [17.5 MB]
test-sink  | Get:8 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages [823 kB]
test-sink  | Get:9 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [883 kB]
test-sink  | Get:10 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages [164 kB]
test-sink  | Get:11 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages [1792 kB]
test-sink  | Get:12 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [266 kB]
test-sink  | Get:13 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [880 kB]
test-sink  | Get:14 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [10.9 kB]
test-sink  | Get:15 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1189 kB]
test-sink  | Get:16 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1125 kB]
test-sink  | Get:17 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [49.0 kB]
test-sink  | Get:18 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [22.4 kB]```

if not, set the following environment variable:

```export DOCKER_DEFAULT_PLATFORM=linux/amd64```

you might need to delete existing ubuntu docker images downloaded, and you might need to restart docker.

marking this as closed.  let me know if the issue persists.

Couldn't get it to work with the flag.
Anyway, not a big deal, running goreleaser produces a working linux binary I can use in docker, so I'll be using it instead of the one attached with v0.1.2 release.


[BigQuery] Removes SafeTotalRows from BigQueryResults.

TotalRows is now ulong? instead of ulong.
SafeTotalRows has been removed.

Merging now, we can always rollback this change if it causes a lot of pain.


What are or how to get the available Bible versions?

@JohnAzedo, thanks for asking. All versions can be found in @thiagobodruk 's precious repository - https://github.com/thiagobodruk/biblia


Question: should is rename videosubscriptionsd to .bak ?

so alot of people on reddit says that you can fix respring and freezing by renaming videosubscriptionsd to videosubscriptiond.bak
should i do it and what are the drawbacks if i do

@Cryptiiiic this doesn’t relate to Unc0ver.

its related the the jailbreak topic so if you know something about this please share
i do wanna ruin my device because of a mistake ive made wthout consulting the experts and thats why i posted it here

No you shouldn’t rename any files @wishy-96 update your Unc0ver & your issue will be resolved.

well mine is on b17 and unluckely for me it still freezes from time to time like daily, usually while using spotify or refreshing cydia
what is videosubscriptionsd anyway?

nothing to do with unc0ver, ask someplace else.


Return /roles page

PR includes

[x] Feature

Related issues
Resolve #393

https://github.com/taskany-inc/hire/assets/81121562/c748ae37-c362-46cc-9b8c-d9a8c52c857a


Signing Oracle based on keeping CSS styles in replies to HTML emails

Dear K-9 Mail team,
In the scope of academic research in cooperation with Ruhr-Uni Bochum and FH Münster, Germany we discovered a security issue in K-9 Mail when used in combination with PGP (OpenKeychain ): K-9 Mail quotes and includes CSS internal

What's up Johnny?

I hereby declare war.

In this example, different content is shown based on the device's screen resolution. It can be used to obtain a signed email from a mobile device, where a benign message is shown. The reply message instead displays a (signed) declaration of war when shown on a desktop mail client.
Conditional CSS rules
The W3C specifies CSS conditional rules (e.g., @media) which allow different formatting based on conditions such as screen width or orientation. For example, a different text can be shown whether a mobile phone is hold in portrait or landscape mode or whether the document is displayed on a screen or printed out. But there are lots of other options: for example, mail clients can be fingerprinted based on the @support conditional rule or various proprietary conditional statements of certain clients can be applied.
Without going into detail here, in the scope of our research we found conditional CSS to show/hide certain text for virtually every email client that exists.
CSS blinding options
We identified seven CSS properties which can be used for covert content attacks as shown below. However, this list is unlikely to be complete because CSS is very complex and offers more possibilities to hide text.
display:    none;
visibility: hidden;
opacity:    0;
clip-path:  polygon(0px 0px, 0px 0px, 0px 0px, 0px 0px);
position:   absolute; top: -9999px; left: -9999px;
color:      transparent;
font-size:  0;

Impact
The attack allows Eve to obtain valid signatures for arbitrary content to be displayed. This can be used to trick a third party, which relies on the authenticity and integrity of signed messages, to perform certain actions (such as starting a war). A forensic analysis can reveal the deception, but then it may already be too late (the war is already declared).
Countermeasures
There are three options to counter the attack, each with a usability-security trade-off:

Drop CSS support in general: Conditional CSS makes it easy for an attacker to hide certain text within a signed message while showing different text. Ideally, clients would ignore CSS in received emails. However, this is an unrealistic scenario given today's usage of email. Sanitizing conditional CSS rules and properties which can be used to hide content is feasible, but it may be insufficient as web technologies are constantly evolving.
Only ASCII text in replies: It should not harm the user experience if mail clients converted quoted messages into ASCII text when replying to an email. Various clients are already doing this. Thus, we recommend that security-focused clients should adopt this behavior.
Remove CSS styles in replies: Email clients should not sign any quoted CSS >
>
What's up Johnny?>

>
I hereby declare war.
>
```>
>
In this example, different content is shown based on the device's
screen resolution. It can be used to obtain a signed email from a
mobile device, where a benign message is shown. The reply message
instead displays a (signed) declaration of war when shown on a desktop
mail client.>
>
>
**Conditional CSS rules**>
>
The W3C specifies CSS conditional rules (e.g., `@media`) which allow
different formatting based on conditions such as screen width or
orientation. For example, a different text can be shown whether a
mobile phone is hold in portrait or landscape mode or whether the
document is displayed on a screen or printed out. But there are lots
of other options: for example, mail clients can be fingerprinted based
on the `@support` conditional rule or various proprietary conditional
statements of certain clients can be applied.>
>
Without going into detail here, in the scope of our research we found
conditional CSS to show/hide certain text for virtually every email
client that exists.>
>
>
**CSS blinding options**>
>
We identified seven CSS properties which can be used for covert
content attacks as shown below. However, this list is unlikely to be
complete because CSS is very complex and offers more possibilities to
hide text.>
>
```>
display:    none;>
visibility: hidden;>
opacity:    0;>
clip-path:  polygon(0px 0px, 0px 0px, 0px 0px, 0px 0px);>
position:   absolute; top: -9999px; left: -9999px;>
color:      transparent;>
font-size:  0;>
```>
>
>
**Impact**>
>
The attack allows Eve to obtain valid signatures for arbitrary content
to be displayed. This can be used to trick a third party, which relies
on the authenticity and integrity of signed messages, to perform
certain actions (such as starting a war). A forensic analysis can
reveal the deception, but then it may already be too late (the war is
already declared).>
>
>
**Countermeasures**>
>
There are three options to counter the attack, each with a
usability-security trade-off:>
>
1. *Drop CSS support in general*: Conditional CSS makes it easy for an
attacker to hide certain text within a signed message while showing
different text. Ideally, clients would ignore CSS in received emails.
However, this is an unrealistic scenario given today's usage of email.
Sanitizing conditional CSS rules and properties which can be used to
hide content is feasible, but it may be insufficient as web
technologies are constantly evolving.>
2. *Only ASCII text in replies*: It should not harm the user
experience if mail clients converted quoted messages into ASCII text
when replying to an email. Various clients are already doing this.
Thus, we recommend that security-focused clients should adopt this
behavior.>
3. *Remove CSS styles in replies*: Email clients should not sign any
quoted CSS `<style>` (or `<link rel="stylesheet"`) from the original
message, so that they cannot be used as signing oracles, based on
blinding text with CSS conditional statements.>
>
*Greetings,*>
*Jens*>
>
-- >
You are receiving this because you are subscribed to this thread.>
Reply to this email directly or view it on GitHub:>
https://github.com/k9mail/k-9/issues/3925

True, HTML+CSS tricks can be somewhat of a security issue for email and certainly for the web in general, which of course cannot be mitigated by simply signing the email with PGP, but the whole attack scenario as laid out, while technically possible, is neither terribly feasible or practical, nor particularly unique to K-9 mail or to PGP-signatures.
It seems like a little bit of an exaggeration to call a quoted reply to obfuscated CSS a "signing oracle," but I suppose in certain circumstances someone might try to go politicking or leak to the news media with a screenshot of an apparently valid PGP signature on a reply to a quoted HTML email with some carefully crafted CSS trickery.
It is entirely possible to use plain text only for email, but then of course there are various Unicode look-alike characters, "title case" for Cyrillic letters, right-to-left support for flowing Arabic script or vowel-pointed Hebrew block letters, and similar security issues, whereas those German university profs tend to be satisfied with a few umlauts and the occasional double-S on top of the 26-letter American English alphabet.
Too much FUD is coming in from over at that EFF community with letsencrypt, certbot, TOR, etc.

https://community.letsencrypt.org/guidelines

National Socialist Democrats with labor issues are spreading Fear, Uncertainty, and Doubt over Free and Open Souce Software, and Republicans or other conservatives with small business goals are just rubbing their hands together with greed, or else it's another mega-corporate state takeover. Братва.
Una Milicia bien regulada, estando necesaria a la seguridad de un Estado libre, el derecho del pueblo de tener y de portar Armas, no será infringido.
https://www.colmena.biz/~justina/

We don't plan to take any action because of this. However, we do recommend not to accept declarations of war via email.

Update: Here's a full (public) report on the issue: https://arxiv.org/ftp/arxiv/papers/1904/1904.07550.pdf


Is Robotroller working for Android yet?

I saw where there seemed to be a bug with the Android implementation for Robotroller.  Has this been fixed?

It should have been working since cde3beae762020aac8a2ee35ebd1699b7cc6cc54 at the end of October. There is also a branch on the repo with beta code for Windows Phone support.


automate android profile screen

LEARNER-9852
Description
Verify Main Dashboard screen is loaded successfully
Verify that Profile screen will show following contents:
Back icon, "Profile" as Title, Edit
Profile Image, User Name, Video Settings
Support Info, Contact Support, Terms of Use
Privacy Policy, Cookie Policy, Personal Info
View FAQ, App Version, Up to Date
Logout button
Verify that tapping edit button should load Edit profile screen
Verify that tapping back button should leave Edit profile screen
Verify that tapping leave button should leave Edit profile screen
Verify that tapping Video Settings should load Video Settings screen
Verify that tapping back button should leave Video Settings screen
Verify that tapping Terms of Use should load Terms of Use screen
Verify that tapping back button should leave Terms of Use screen
Verify that tapping Privacy Policy should load Privacy Policy screen
Verify that tapping back button should leave Privacy Policy screen
Verify that tapping Cookie Policy should load Cookie Policy screen
Verify that tapping back button should leave Cookie Policy screen
Verify that tapping Personal Info should load Personal Info screen
Verify that clicking logout button should load logout dialog
Verify that tapping close button should leave logout dialog
Verify that tapping logout button should logout from main dashboard screen

Approving overall. I see we are using txt in variable names and method names. Is it possible that we replace these with text?

"Yes, it's intentional because the development teams place the txt inside IDs. That's why we use the same as unique variable names. For instance, txt_screen_title and txt_search_label are unique IDs on elements, and we use the same names as our unique variable names."
I will check with the Dev team and ask if there is any convention they are following, then I will replace the txt with text in a separate PR.


Bug: Issue with the visibility of contents of login page in dark mode.

Description
When I open login page in light mode, email and password fields are visible with black colour on white background. But if I switch it to dark mode, the fields are not visible. They are with white colour on white background of form
Screenshots
I entered text in the email field and highlighted it in blue colour while using dark mode. However, the text is not visible in the fields.

Steps to reproduce the bug

Go to  Login page
Switch to dark mode.
Observe the email and password fields.

The current behaviour
In dark mode, the email and password fields are not visible, appearing with white text on the white background of the form.
The expected behaviour
Two possible solutions:

Change the text colour of the fields to a colour that is visible on a white background.
Change the background colour of the input fields and form. This would be preferable as white text on a white background is uncomfortable for the eyes in dark mode.

Kindly assign me this issue to work on it.

Please assign me this issue to wok on it.

@subhadipbhowmik ,  You have assigned me this issue but someone else fixed it by opening the issue #138


main menu

The main menu looks like a bunch of ascii art and has no buttons to click on, because of this i cannot play the mod.

You should be able to click on "start dying", "arise again", "checklists" and "exit" 🙂


pip-compile incorrectly adds functools32 as matplotlib dependency on Python 3.5

When compiling requirements for matplotlib under python 3.5, one of the generated dependencies is functools32==3.2.3.post2  # via matplotlib. This package, however, is only uses to backport functionality to python 2.7 and pip fails when it tries to install it on python 3. Looks like for some reason pip-compile fails to recognize that functools32 is not required with python 3. When you simply run pip install matplotlib pip correctly understands that functools32 is not required and does not attempt installing it.
Environment Versions

OS Type: Windows 7 x64
Python version: Python 3.5.3 :: Continuum Analytics, Inc.
pip version:  pip 9.0.1 from <...> (python 3.5)
pip-tools version: pip-compile, version 1.9.0

Steps to replicate

Install python 3.5.3, pip-tools 9.0.1
.Create requirements.in with just one line:

matplotlib

Run pip-compile
Run pip-sync

Expected result
functools32 should not be in the generated package list.
Actual result
Results of pip-compile:
cycler==0.10.0            # via matplotlib
functools32==3.2.3.post2  # via matplotlib
matplotlib==2.0.2
numpy==1.13.1             # via matplotlib
pyparsing==2.2.0          # via matplotlib
python-dateutil==2.6.1    # via matplotlib
pytz==2017.2              # via matplotlib
six==1.10.0               # via cycler, matplotlib, python-dateutil

When you run pip-sync, it fails with the error:
    Complete output from command python setup.py egg_info:
    This backport is for Python 2.7 only.

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in C:\Users\<username>\AppData\Local\Temp\pip-build-vbzf_gya\functools32\

Is there a workaround for this? Is it possible to blacklist a package, maybe?

This is extremely similar to #552. I've tried with a docker container, to no effect.
But, I've tried with python 2.7, and functools32 did not appear in the requirements.txt. But it did get installed with pip install, which really confused me.
So I tried another pip-compile, deleting the requirements.txt and clearing the cache with --rebuild, and then functools32 got listed (with python 2.7).
I then retried with --rebuild on python 3.5, and it did not get listed.
So I'm not sure how/why, but I got feeling your pip-tools cache has old or bad stuff. Please try again with --rebuild, and tell me if it fixes the issue.
If it does work, I'll ask right away: do you use both python 2.7 and python 3.X? I'd like to figure out what is wrong with the pip-tools cache.

hmm, it didn't help. To give you some background, I used to work with python 2.7 in a conda environment (and pip-tools correctly resolved functools32 dependency). Now I'm trying to upgrade to 3.5.3 and face this issue.
I tried with --rebuild (and deleting the .txt file) but it did not change anything.  functools32 still got listed.
At that point I still had functools32 package installed in my conda environment because I just upgraded python from 2.7 to 3.5.3 with conda (so the package just persisted from the previous state of my conda environment).
I then uninstalled it manually via pip (pip uninstall functools32) and tried with --rebuild again. This time it failed, apparently while trying to install functools32 (error listed below). Now I seem stuck as I always get this error no matter what I try to do...
(<envname>) C:\<path>>pip-compile --rebuild requirements.in
Traceback (most recent call last):
  File "c:\users\<username>\appdata\local\continuum\anaconda2\envs\<envname>\lib\runpy
.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\users\<username>\appdata\local\continuum\anaconda2\envs\<envname>\lib\runpy
.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\<username>\AppData\Local\Continuum\Anaconda2\envs\<envname>\Scripts\p
ip-compile.exe\__main__.py", line 9, in <module>
  File "c:\users\<username>\appdata\local\continuum\anaconda2\envs\<envname>\lib\site-
packages\click\core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "c:\users\<username>\appdata\local\continuum\anaconda2\envs\<envname>\lib\site-
packages\click\core.py", line 697, in main
    rv = self.invoke(ctx)
  File "c:\users\<username>\appdata\local\continuum\anaconda2\envs\<envname>\lib\site-
packages\click\core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "c:\users\<username>\appdata\local\continuum\anaconda2\envs\<envname>\lib\site-
packages\click\core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "c:\users\<username>\appdata\local\continuum\anaconda2\envs\<envname>\lib\site-
packages\piptools\scripts\compile.py", line 184, in cli
    results = resolver.resolve(max_rounds=max_rounds)
  File "c:\users\<username>\appdata\local\continuum\anaconda2\envs\<envname>\lib\site-
packages\piptools\resolver.py", line 107, in resolve
    has_changed, best_matches = self._resolve_one_round()
  File "c:\users\<username>\appdata\local\continuum\anaconda2\envs\<envname>\lib\site-
packages\piptools\resolver.py", line 195, in _resolve_one_round
    for dep in self._iter_dependencies(best_match):
  File "c:\users\<username>\appdata\local\continuum\anaconda2\envs\<envname>\lib\site-
packages\piptools\resolver.py", line 274, in _iter_dependencies
    dependencies = self.repository.get_dependencies(ireq)
  File "c:\users\<username>\appdata\local\continuum\anaconda2\envs\<envname>\lib\site-
packages\piptools\repositories\pypi.py", line 145, in get_dependencies
    self._dependencies_cache[ireq] = reqset._prepare_file(self.finder, ireq)
  File "c:\users\<username>\appdata\local\continuum\anaconda2\envs\<envname>\lib\site-
packages\pip\req\req_set.py", line 634, in _prepare_file
    abstract_dist.prep_for_dist()
  File "c:\users\<username>\appdata\local\continuum\anaconda2\envs\<envname>\lib\site-
packages\pip\req\req_set.py", line 129, in prep_for_dist
    self.req_to_install.run_egg_info()
  File "c:\users\<username>\appdata\local\continuum\anaconda2\envs\<envname>\lib\site-
packages\pip\req\req_install.py", line 439, in run_egg_info
    command_desc='python setup.py egg_info')
  File "c:\users\<username>\appdata\local\continuum\anaconda2\envs\<envname>\lib\site-
packages\pip\utils\__init__.py", line 707, in call_subprocess
    % (command_desc, proc.returncode, cwd))
pip.exceptions.InstallationError: Command "python setup.py egg_info" failed with
 error code 1 in C:\Users\<username>\AppData\Local\Temp\tmpbcec3wc5build\functools
32\

I also have a global python installed, which is 2.7. It almost looks like some part of pip-tools gets confused and thinks that I'm using python 2.7...

I think the problem originates here. This is what I get if I simply try to resolve dependencies of matplotlib==2.0.2 from PyPI:
Python 3.5.3 |Continuum Analytics, Inc.| (default, May 15 2017, 10:43:23) [MSC v.1900 64 bit (AMD64)] on win32
In[2]: import os
from pip.req import InstallRequirement
from piptools.scripts.compile import get_pip_command
from piptools.repositories.pypi import PyPIRepository

pip_command = get_pip_command()
pip_options, _ = pip_command.parse_args([])
session = pip_command._build_session(pip_options)
repository = PyPIRepository(pip_options, session)

ireq = InstallRequirement.from_line('matplotlib==2.0.2')
repository.get_dependencies(ireq)
Out[2]:
{<InstallRequirement object: pyparsing!=2.0.4,!=2.1.2,!=2.1.6,>=1.5.6 (from matplotlib==2.0.2) editable=False>,
 <InstallRequirement object: cycler>=0.10 (from matplotlib==2.0.2) editable=False>,
 <InstallRequirement object: numpy>=1.7.1 (from matplotlib==2.0.2) editable=False>,
 <InstallRequirement object: pytz (from matplotlib==2.0.2) editable=False>,
 <InstallRequirement object: functools32 (from matplotlib==2.0.2) editable=False>,
 <InstallRequirement object: python-dateutil (from matplotlib==2.0.2) editable=False>,
 <InstallRequirement object: six>=1.10 (from matplotlib==2.0.2) editable=False>}

I am not too familiar with how pip works, unfortunately.. but shouldn't it not list functools32 as a dependency given I am on python 3.5.3?

Hm, I got this resolved now, though I'm not exactly certain what the root cause was. I think it had something to do with either conda or pip caching incompatible version on matplotlib distribution.
Here's what I did. I tried debugging the following script:
from pip.req import InstallRequirement
from piptools.scripts.compile import get_pip_command
from piptools.repositories.pypi import PyPIRepository

pip_command = get_pip_command()
pip_options, _ = pip_command.parse_args([])
session = pip_command._build_session(pip_options)
repository = PyPIRepository(pip_options, session)

ireq = InstallRequirement.from_line('matplotlib==2.0.2')

I then placed a breakpoint on this line, and changed self.ignore_installed to True, and continued. From that point onwards everything worked fine.. I am not exactly sure which cache I ended up clearing with this..

Most likely the wheels cache yes. I'll close this issue, if it occurs again, ping.
I'll pray this one was only a cache issue.


Can set custom domain as IP address?

Hello, my jira url is http://<IP_ADDRESS>:8080, should I make use of domain rather than ip address to make injector worked?

We have not tested using an IP address instead of a domain (we use Atlassian Cloud), but we think it should work fine.


How do i change the strum notes hp?

Describe your problem here.
I'm trying to change the strum notes hp so it wont continuously give me hp,like the sonic.exe mod
when pressing the stum note no hp was given when it was held. Some help would be appreciated
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
Yes i edited PlayState.hx, TitleState.hx i added a Secret code, ChartingState.hx, CoolUtil To Add More Difficulties, and more that i don't remember

#9620

#9620

I was asking the for the code to do that

IT GAS THE CODE IN PLAYSTATE!!!

Ik. what line do i put it on?


Postman to k6 issue - Postman sends value as number, k6 sends value as string

Hi all!
I have an issue with a converted test from Postman to k6.
In Postman I am sending a payload body that has a number as a value, and the test passes, but the converted test in k6, sends the value as a string and the test fails.
The issue here is that it needs to be a number, not a string, for the test to pass.

Hello @thim81 ,
I've attached the Postman collection for you to look over.
testing k6.postman_collection.json
Hopefully, you guys manage to fix the issue, or at least give me a pointer to where I am doing something wrong on my end. I've depleted all of my thoughts on how to fix the code and make it work.

hi @Adrian-2705
The reason it is using "string" values, is because in your Postman request you wrapped the Postman variables in "" which makes them strings.

If you remove the "" around your variables, Postman and K6 will handle them as Number values.
Postman

K6 Script

K6 Request Execution

Hello @thim81,
I've tested what you showed me.
I have the following results:

for validation_request_id, it needs to be a string, if not it will result in a 422 Unprocessable Entity error.
I've removed the quotes from event_timestamp and document_id, and on Postman it sends them as numbers, but in k6 I still get invalid event_timestamp. It sends the values as strings.
I have started manually writing the whole script/test in k6 and got the desired results.
There is a possibility that Postman libraries have an issue when converting the collection to k6.
Anyway, thank you for the help.
If I encounter other issues, I will report them and let you know.

hi @Adrian-2705
The goal of the postman-to-k6 converter is that it generates the correct K6 scripts.
When doing the investigation, I used your Postman collection and made the elements unquoted, which led to the expected K6 scripts. So I'm surprised that you still ran into issues.
If you have more info on what you had to correct so that I can review any changes in the postman-to-k6 converter

Hi @thim81
I understand the purpose of postman-to-k6, and it should generate the correct scripts, but believe me, I still got the same result, issue in k6.
I will do some digging to see if I can change anything else in my Postman test and not break it, and test the conversion to k6.
I will share what I find tomorrow.

It might be helpfull for your debugging to trigger k6 with --http-debug="full"
example => k6 run k6/marvel.k6.js --http-debug="full"

Will use thank, thank you

hi @Adrian-2705
Did you find anything that explains the behaviour or were able to reproduce or overcome it?

Hi @thim81 ,
Sorry for the delay, I've been testing, and trying different approaches, but I get the same result.
This is the debug:
`k6 run possible-fix.js --http-debug="full"
      /\      |‾‾| /‾‾/   /‾‾/
 /\  /  \     |  |/  /   /  /
/  \/    \    |     (   /   ‾‾\

/          \   |  |\  \ |  (‾)  |
/ __________ \  |__| _\ ____/ .io
 execution: local
    script: possible-fix.js
    output: -

 scenarios: (100.00%) 1 scenario, 1 max VUs, 10m30s max duration (incl. graceful stop):
          * default: 1 iterations for each of 1 VUs (maxDuration: 10m0s, gracefulStop: 30s)

INFO[0000] Request:
POST /event/ HTTP/1.1
Host: localhost:5000
User-Agent: k6/0.53.0 (https://k6.io/)
Content-Length: 167
Authorization: Basic aW5zcGlydXM6amU0cW9zM3cwMDc=
Content-Type: application/x-www-form-urlencoded
Accept-Encoding: gzip
event_data=map%5Bdocument_id%3A81890+validation_request_id%3A545851+validation_status%3Avalidated%5D&event_timestamp=1724861529&event_type=document.validation.response  group= iter=0 request_id=cfa91ce2-1536-44dd-5c77-8934a4de151b scenario=default source=http-debug vu=1
INFO[0000] Response:
HTTP/1.1 422 Unprocessable Entity
Content-Length: 38
Access-Control-Allow-Origin: *
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Wed, 28 Aug 2024 16:12:09 GMT
Etag: W/"26-ax897zOYepat8NqDEV12s361pqA"
Keep-Alive: timeout=5
X-Powered-By: Express
{"errors":["Invalid event timestamp"]}  group= iter=0 request_id=cfa91ce2-1536-44dd-5c77-8934a4de151b scenario=default source=http-debug vu=1
`
Hope it helps,
Also I've change the pre-request-scripts from Postman.

As I said, I've managed to write the code manually for what I am testing without the convertion. It would've been a time saver if it worked.
Please let me know what else I can provide to help fixing this issue.


Mayaqua: use "cpu_features" to check whether AES-NI is supported

Fixes #573.

SoftEther VPN Patch Acceptance Policy:
http://www.softether.org/5-download/src/9.patch
I choose option 1.

Wow
I'll review soon
@Andy2244 ?

Nice so the google lib worked out.
Keep in mind that this does not just report aes-ni, but rather all "known" aes accelerators/hardware support. So on x86 this may include (Geode LX, VIA) and on arm its ARM cryptographic extensions.  Mips/mips64 might have some too, but i'm not aware of any for aes.
So the code/lib also needs to support those or use some fallback.
https://wiki.openwrt.org/doc/hardware/cryptographic.hardware.accelerators

OpenSSL's EVP interface makes use of hardware acceleration, if available.
We use cpu_features just to check whether AES-NI is available, in order to show it in the server status.