Authorize fineUploader to send form even without file to upload

Hi !
Type of issue

[ ] Bug report
[x] Feature request

Uploader type

[x] Traditional
[ ] S3
[ ] Azure

Feature request details
FileUploader integration in a form (see) with optional file upload throw "No files to upload." on form submit when there is no file in FileUploader.
Change FileUploader form integration to act like an empty field instead.
Possible fix
Add an optional option in the FileUploader constructor or by default Existing HTML Forms integraton dont throw errors on upload if there is no file.
https://github.com/FineUploader/fine-uploader/blob/401482ec7cda20b9c877f7731d798233769eb0da/client/js/uploader.basic.api.js#L430
Thanks !

Would you like to try a pull request with the necessary changes? You'll need to write some tests as well to ensure this actually works. I'm not sure it will be trivial, but maybe?

Sure, that's what I was planning to do. Just wanted to know if this feature was suitable in this project !


[BUG] Readme icon borked

Describe the bug
Iconography PR broke readme:

Expected behavior
An icon not a broken image tag

Blah!


Index profile page added

Hey, I have added my profile page in the repo. Please check and merge it :)

@itsrahulsehgal
check your pull request i can't see your folder


Small issue in JavaDoc for SpringXmlConfigLauncher?

The JavaDoc says:
/**

The SpringLaucher class resolves the spring.xml file and handles access to
beans
*
@author Andy Moncsek
*
*/

private final String BASIC_CONFIG_BEANS = "basic.xml";

fixed in https://github.com/JacpFX/JacpFX/commit/0d5134842dbb430a89420e52b9510d917541e51a


[8pt] worker_fim_rasters: wse errors

During full scale ras2fim pipeline runs, two HUCs showed what appears to be related errors:
These were seen with the following:
12090301
- str_feature_id = 5791662
- str_feature_id = 5790994
- str_feature_id = 5791806
- str_feature_id = 5789506
- str_feature_id = 5790736
- str_feature_id = 5789214
- str_feature_id = 5789326
12040101
- str_feature_id = 1466258
- str_feature_id = 1466224
- str_feature_id = 1465634

Error:
str_feature_id = 5790994
cannot convert float NaN to integer
Traceback (most recent call last):
File "C:\Users\rdp-user\Projects\ras2fim-dev\ras2fim\src\worker_fim_rasters.py", line 1304, in fn_main_hecras
river = fn_create_hecras_files(str_feature_id, str_geom_path, flt_ds_xs, flt_us_xs, int_max_q, str_hecras_path_to_create, tpl_settings)
File "C:\Users\rdp-user\Projects\ras2fim-dev\ras2fim\src\worker_fim_rasters.py", line 1237, in fn_create_hecras_files
fn_run_hecras(str_ras_projectpath, int_max_flow, model_unit, tpl_settings)
File "C:\Users\rdp-user\Projects\ras2fim-dev\ras2fim\src\worker_fim_rasters.py", line 687, in fn_run_hecras
int_max_wse = int(max(list_avg_water_surface_elev) // flt_interval)
ValueError: cannot convert float NaN to integer
for more details.. see the 05_hecras_output / errors_found.log

Some also showed a slightly different error saying
C:\Users\rdp-user\Projects\ras2fim-dev\ras2fim\src\worker_fim_rasters.py:646: RuntimeWarning: invalid value encountered in multiply
arr_multiply_wse = arr_avg_water_surface_elev * arr_channel_length
C:\Users\rdp-user\Projects\ras2fim-dev\ras2fim\src\worker_fim_rasters.py:687: RuntimeWarning: invalid value encountered in double_scalars
int_max_wse = int(max(list_avg_water_surface_elev) // flt_interval)

Error:
str_feature_id = 5789214
cannot convert float NaN to integer
Traceback (most recent call last):
File "C:\Users\rdp-user\Projects\ras2fim-dev\ras2fim\src\worker_fim_rasters.py", line 1304, in fn_main_hecras
river = fn_create_hecras_files(str_feature_id, str_geom_path, flt_ds_xs, flt_us_xs, int_max_q, str_hecras_path_to_create, tpl_settings)
File "C:\Users\rdp-user\Projects\ras2fim-dev\ras2fim\src\worker_fim_rasters.py", line 1237, in fn_create_hecras_files
fn_run_hecras(str_ras_projectpath, int_max_flow, model_unit, tpl_settings)
File "C:\Users\rdp-user\Projects\ras2fim-dev\ras2fim\src\worker_fim_rasters.py", line 687, in fn_run_hecras
int_max_wse = int(max(list_avg_water_surface_elev) // flt_interval)
ValueError: cannot convert float NaN to integer
for more details.. see the 05_hecras_output / errors_found.log

I was unable to recreate this issue with 12040101 on my EC2. When I looked for the error log, there was no error log.  I am unsure whether the error logging just didn't work or if the issue actually didn't occur.
The image below is the models I used and this is the ras2fim.py command that I used:
python ras2fim.py -w 12040101 -p ESRI:102739 -t C:\ras2fim_data\inputs\3dep_dems\HUC8_10m_5070\HUC8_12040101_dem.tif -o C:\Users\rdp-user\projects\debug_12040101_WSE\test_outputs -i C:\ras2fim_data\OWP_ras_models\wse_errors_12040101

You can open pretty much any 05_hecras_output/error_found.csv and look in the err column for "cannot convert float NaN to interger).  See s3://ras2fim/output_ras2fim/12090301_2277_230804/05_hecras_output/error_found.csv and it will give you some sample models to try it on.


Sample Download Link is broken

Link to article:
https://docs.microsoft.com/tr-tr/aspnet/web-forms/overview/data-access/introduction/master-pages-and-site-navigation-vb?source=docs
Problem:
Download Sample App link is broken and return a 404 error.

@scottaddie Here's the English page - download sample app link is near the top:
https://docs.microsoft.com/en-us/aspnet/web-forms/overview/data-access/introduction/master-pages-and-site-navigation-vb?source=docs

Ok, thank you!


Add block parameter to prediction creation methods

Is the intention here to roll this out quietly via the block param for testing?

Sort of. Because of how run wraps createPrediction, we need to make block a parameter to set the right headers in the original request. So most people will continue using replicate.run, but I suppose they could start using predictions.create and opt-in to the same behavior.


Types mapped from objects containing named functions do not generate validation for those members.

📝 Summary
I have a set of types to validate arguments (and returns, tho not necessary to illustrate the issue) in an async API object. The TS types that extract the arguments, when passed to typia.createValidate does not reliably fail invalid arguments. Hovering over the type in the playground and copying the computed type DOES generate a working validator.

Typia Version: Playground 6.11.0
Expected behavior: Args and Args2 validate with the same results
Actual behavior:  Args incorrectly passes an invalid value, Args2 correctly fails an invalid value

⏯ Playground Link
If you click on the playground link above and hover over Args, you see it evaluates to
type Args = {
    foo: [];
    bar: never;
} | {
    foo: never;
    bar: [];
}

This type represents the possible ways the test API can be called (ie a single API, with it's associated parameters). It has been copied and pasted and assigned to the type Args2.
When an invalid argument is passed to the return of typia.createValidate<Args>(), it is incorrectly validated as correct. When the same invalid argument is passed to the return of typia.createValidate<Args2>(), it is correctly validated as incorrect.
In TS (and the Typia Playground), Args and Args2 are identical, however the execution of the validation function is not.
Included for completeness (same as the playground link):
import typia from "typia";

export type Explode<T> = keyof T extends infer K
  ? K extends unknown
  ? { [I in keyof T]: I extends K ? T[I] : never }
  : never
  : never;

type ApiArguments<API extends {}> = Explode<{
  [api in keyof API]: API[api] extends (this: any, ...a:infer A extends any[])=>Promise<any> ? A : never;
}>

const api = {
  async foo() { return 1 },
  async bar() { return "x" }
}

type Args = ApiArguments<typeof api>;
type Args2 = {
    foo: [];
    bar: never;
} | {
    foo: never;
    bar: [];
};

const validator = typia.createValidate<Args>();
const validator2 = typia.createValidate<Args2>();

console.log(validator({ foo: [] }))
console.log(validator2({ foo: [] }))
console.log(validator({ foo: [true] })) // PASSES, BUT SHOULD FAIL
console.log(validator2({ foo: [true] }))

Simpler version, that remove the Explode and async from the possible source of errors. It's now just a simple mapped type that extracts the Parameters for each function in the object.
Playground
import typia from "typia";

type ApiArguments<API extends { [k:string]: (...a:any[])=>any}> = {
  [api in keyof API]: Parameters<API[api]>;
}

type Args = ApiArguments<{
    foo(x: number): number;
}>;

type Args2 = {
    foo: [x: number];
};

const validator = typia.createValidate<Args>();
const validator2 = typia.createValidate<Args2>();

console.log(validator({ foo: [10] }))
console.log(validator2({ foo: [10] }))
console.log(validator({ foo: [true] })) // PASSES, BUT SHOULD FAIL
console.log(validator2({ foo: [true] }))

Narrowed it down further: typia doesn't correctly recognise keys that are functions in mapped types. However it DOES recognise property keys that are initialized to functions.
Playground link
Key observation:
type Args = ApiArguments<{
    //foo(x: number): number; // BREAKS: `foo` is not mapped to a validation
    foo:(x: number) => number; // Works: `foo` is mapped to a validation
}>;

Going back to the initial example (with the complexity of Parameters, extends, async), changing
const api = {
  async foo() { return 1 },
  async bar() { return "x" }
}

...to...
const api = {
  foo: async function foo() { return 1 },
  bar: async function bar() { return "x" }
}

...generates the correct validation. This demonstrates that the only issue here is that mapped keys defined by functions are for some reason not generating correct validation, even if they are mapped to data (such as to their parameters)
I'll update the issue title to reflect this observation

Canonical example, that shows that the function declarations vs function expression behave differently.
Playground
import typia from "typia";

type Mapper<X> = {
  [K in keyof X]: string
}

type V1 = {
  foo(): void;
}

console.log(
  typia.validate<Mapper<V1>>({ foo: 'foo' }),
  typia.validate<Mapper<V1>>({ foo: null }) // INCORRECTLY PASSES
)

type V2 = {
  foo: ()=> void;
}

console.log(
  typia.validate<Mapper<V2>>({ foo: 'foo' }),
  typia.validate<Mapper<V2>>({ foo: null })
)

@samchon  Perhaps https://github.com/samchon/typia/blob/master/src/factories/internal/metadata/emplace_metadata_object.ts#L179 should be:
   ts.isPropertySignature(node) ||
   ts.isMethodSignature(node) ||

?
I've not yet worked out if this will have any other detrimental effects, as I'm having issues running npm test

Ok, so that "fix" breaks lots of code as it new tries (fails) to generate validators for all function members.
Typia does not (at present) generate validation tests for function elements, as can be shown here  (aside: a basic test here could be that typeof obj[field]==='function' would at least test the function member exists and is a function, even though it can't check the parameter types, only arity).
So the issue is, from a type perspective, that
type FunctionParameters<X extends { [k:string]: (...a:any)=>any }> = {
  [K in keyof X]: Parameters<X[K]>
}

...fails because it's input is stripped of all functional members, even tho the resulting type contains only data members.
I think there are only two approaches to fixing this, and I have little insight into which is the best to implement:

Move the "significant" test up the call tree so that callees can optionally ignore any functional members, or
Pass another flag to significant = (functional: boolean, terminal?: boolean) => so that isMethodDeclaration, isMethodSignature and isShorthandPropertyAssignment are conditionally included.

Given isShorthandPropertyAssignment is not call-specific, I don't think (2) will work. The tests to include/exclude these nodes which define function member types need to be plumbed into iterate_metadata and explore_metadata.
The only other way I can think of doing this is to leave the function members in place, and simply generate a null or trivial validation test for them (or the "aside" above), since the mapped type above will correctly generate data tests as the resulting type does not contain functional members.
There's a strong chance I've over-complicated this case, as I'm still learning how typia is implemented.
Any hints on how to progress this to a fix would be much appreciated 🙏

This playground link seems to narrow down the issue to a cover all cases

import typia, { tags } from "typia";

typia.createIs<{
  foo: [];
  bar: never;
}>();

https://typia.io/playground/?script=JYWwDg9gTgLgBDAnmYBDANHA3g1BzAZzgF84AzKCEOAIiRVRoG4AoF+tAOgGMoBTVDD4BJAgB4sLOOQgQAXHADaAXVbSARqigKAdnwBufKK2IA+ABQBKJkA
At first, the never typed property is considered as only undefined type in the TypeScript type system.
Also, checking only property typed function is not a bug, bug intended spec following the standard way. The member methods are defined in the prototype instance, so that typia checks not only property function, but also member methods, it is not a proper validation.
class SomeClass {
  public methodA() {}
  public propertyFunctionB = () => {};
}

Simpler version, that remove the Explode and async from the possible source of errors. It's now just a simple mapped type that extracts the Parameters for each function in the object.
Playground
import typia from "typia";

type ApiArguments<API extends { [k:string]: (...a:any[])=>any}> = {
  [api in keyof API]: Parameters<API[api]>;
}

type Args = ApiArguments<{
    foo(x: number): number;
}>;

type Args2 = {
    foo: [x: number];
};

const validator = typia.createValidate<Args>();
const validator2 = typia.createValidate<Args2>();

console.log(validator({ foo: [10] }))
console.log(validator2({ foo: [10] }))
console.log(validator({ foo: [true] })) // PASSES, BUT SHOULD FAIL
console.log(validator2({ foo: [true] }))

Also, the third case console.log is tracing failure. What is the problem?

I don't believe this is an invalid question.
The problem is the types:
type V1 = {
  foo(): void;
}
type V2 = {
  foo: ()=>void;
}

....are logically equivalent, but behave differently in typia.
import typia from "typia";

type ApiArguments<API extends { [k:string]: (...a:any[])=>any}> = {
  [api in keyof API]: Parameters<API[api]>;
}

type V1 = ApiArguments<{
  foo(x:number): void;
}>;

type V2 = ApiArguments<{
  foo: (x:number)=>void;
}>

typia.is<V1>({foo:['x']}); // Incorrectly validates
/*
  const $io0 = (input) => true; // NO VALIDATION OF `foo`
  return (input) =>
    "object" === typeof input &&
    null !== input &&
    false === Array.isArray(input) &&
    $io0(input);

*/
typia.is<V2>(null);
/*
  const $io0 = (input) =>
    Array.isArray(input.foo) &&
    input.foo.length === 1 &&
    "number" === typeof input.foo[0]; // CORRECTLY VALIDATES `foo`
  return (input) => "object" === typeof input && null !== input && $io0(input);
*/

You have assumed the former will not generate a type validator because it is a function and omit the key in significant(), however if mapped (or subject to a keyof), this is not true, and the entire iteratie_metadata is terminated early.
A similar issue exists when the type is derived from typeof value where value is initialized by shorthand properties.

Similarly, if you look at the generated code in the playground link in https://github.com/samchon/typia/issues/1302#issuecomment-2379562090, you will see there is no generated code for foo or qux, when there should be

RE you comment above:

Also, checking only property typed function is not a bug, bug intended spec following the standard way. The member methods are defined in the prototype instance. If typia checks not only property function, but also member methods, it is not a proper validation.

This is only true in a class declaration, not plain objects or types.

@samchon - thank you for fixing the shorthand property issue 🙇
However, the original issue with an object containing a member function that is mapped to a data type remains in v6.11.1


favicon

[x] This is a question about using the theme.
[ ] This is a feature request.
[ ] I have updated all gems with bundle update.
[ ] I have tested locally with bundle exec jekyll build.
[ ] I believe this to be a bug with the theme --- not Jekyll, GitHub Pages or one of the bundled plugins.

Environment informations

Minimal Mistakes version:
github-pages or jekyll gem version:
Operating system:

Expected behavior

Steps to reproduce the behavior
Just wondering if you have any advice on getting a favicon.ico to appear. Ive tried just putting it in the main directory,  and it shows up on my localhost, but not when published.
Ive tried other peoples advice  of putting  a " < link rel="shortcut icon" href="/assets/images/favicon.ico"  / > "on a page, but dont think that works either
Thank you!!

I suggest using something like the Favicon Generator. It will create several favicons with instructions on how to load them. Essentially you drop all the icons into your site and then paste in some HTML in the <head>.
The theme has a file just for doing this which you can add here: /_includes/head/custom.html
This question has been asked a few times before so if you need more guidance give these issues a look. You can also Google around as this is a common web development need and isn't specific to this theme or Jekyll.

Ok great advice. Sorry i tried searching earlier but didn't realize i had limited to my search to issues that were still open so didn't see these.
Ive used the favicon generator now and tried to follow your advice and the other posts as best i could but still think ive gone wrong somewhere.
Ive put the files in the root directory, but in some posts you also said assets/images so i placed them there too. Not sure which is correct.
I pasted the code the generator spit out into /head/custom.html but think it must not be correct. The icon shows up in my localhost:4000 but not on the published version. Heres how my custom.html looks;

Thank you!!

If you fire up your browser's web dev tools it'll show you if there are any bad paths. You can place the favicons wherever you want, you'll just need to update the href path in those link elements to match. If you put them in /assets/images then you'll want paths something like: href="/assets/images/apple-touch-icon.png" or href="{{ apple-touch-icon.png | prepend: '/assets/images' | absolute_url }}".
Also browsers tend to cache favicons so they don't always update right away. The Real Favicon site has a tool to verify on their homepage to check if you've loaded favicons correctly.
Closing as this isn't a theme issue. If you're still having troubles I'd suggest poking around Stackoverflow or similar web dev forums for help.


Licence description on PyPI incorrect

https://pypi.org/project/atlite/
Still lists GPLv3 or later, not MIT.
Also the badge in the readme shows wrong, I think that's related to the pypi license.

Looks good with new release.


Activate ComposableParamOrder twitter/compose-rules and fix ./gradlew composeLint

Idea Description
You can activate it in https://github.com/DroidKaigi/conference-app-2022/blob/main/detekt.yml
And please fix ./gradlew composeLint.
Reference images and links
https://github.com/DroidKaigi/conference-app-2022/blob/main/detekt.yml
https://twitter.github.io/compose-rules/rules/

I'd like to try this one. 🙋🏼

Thanks! Assigned!


add grafana views for tekton chains controller workque and latency

a fix for https://issues.redhat.com/browse/SRVKP-4405

@jkhelil when you get the chance can you launch your own OCP cluster, run dev_setup.sh -- use-local-branch , and capture a screen shot of the new panels?
I forgot to mention when we had our video conf that such screen shots were part of our methodology when updating these panels.
I may have one review comment I'll post separately.
thanks

@gabemontero Here is a screenshot

Certainly better than before @jkhelil but it looks like something got lost when I tried to describe it to you before.  I was hoping it would look like how the Watcher Work Queue Depth and Watcher Reconcile Latency works with Tekton Results.
See this screen shot:

Can you copy those panel over to the chains section, and then modify the queries to grab those numbers for chains instead of results watcher?
thanks

@gabemontero I am using the same queries as for watcher, i didnt touch th existant chains panels (work queue rate and cpu) the two first panels on my screenshot.
The panels i have added, are the two last ones. On my cluster, i tried to run chains, example to have some data, mm, but i think i need more example to see some data there.
but yeah just want to highlight that i am using the same queries in the two added panels

@gabemontero ok got it.
Fiixing it to look like this


Optional Api::get

Would you like to work on this feature?
yes
What problem are you trying to solve?
Sometimes I want to get an object if it exists, but have some fallback behaviour otherwise. For example, something along the lines of:
if let Some(obj) = cms.get_opt("foo").await? {
    Ok(obj)
} else {
    cms.create(generate_foo()).await
}

Today, this requires me to pattern-match on the Error::Api, and match the string reason against a constant. This is non-obvious (nothing indicates to new users that this is a viable thing to do), bug-prone (I get no warning if I make a typo in the reason), and interacts poorly with the borrow checker.
Describe the solution you'd like
Introduce a new Api::get_opt (or try_get or get_if_exists?) that does this pattern matching internally, and returns a Result<Option<K>>, returning Some(None) for 404 errors.
Describe alternatives you've considered

Modify Api::get rather than introducing a new method

Smaller API surface
Would disrupt existing users
Most use-cases would probably just want to fail loudly anyway

Introduce a new Error::is_not_found(&self) (or ErrorResponse::is_not_found?) method

More extensible for introducing new cases later
Still not very obvious
Would be usable in a lot of places where it's not really useful (especially if put on Error)
Not very ergonomic

Introduce a new Error::NotFound case

Would silently break anyone currently trying to match on ErrorResponse.reason

Documentation, Adoption, Migration Strategy
If introduced as a new method: it'd show up in the API docs alongside Api::get.
If introduced as an error matcher: we might want to add a note about it to Api::get's docs.
Target crate for feature
kube-client

This makes sense to me. My initial gut feel here was that we ought to change Api::get to return a Result<Option<K>> with us doing the 404 error matching directly... but adding a get_opt is more sensible from a breaking perspective, and it's the only sensible way for users who expect certainty to be able to use .get unobtrusively, and also have users who expect uncertainty to call something else (.get_opt).
..it's also maybe possible to mimic the map Entry api here, or do a Api::get_or_else, but both of those feel a bit crazy.

Entry or get_or_insert might actually make sense for the ger-or-create use-case...

we could sketch out an Api::entry -> kube::api::Entry thing if you prefer to make something proper to cater for these situations

.or_default makes sense for structs that have Default impls
.or_apply_with might make sense instead of .or_insert_with / .or_insert_with_key
.or_apply probably makes less sense
.and_modify i can see being useful

I find myself quite a lot in situations where I need to check for an object to be present and do something else if it isn't (erroring out on failure for any other reason). Perhaps a combinator like .found() -> kube::Result<Option<K>> can be implemented to make this pattern clearer.
Something like
if let Some(obj) = Api::<K>::get().found()? {
    // Yey
} else {
   // No dice
}

That might involve creating an extension trait for kube::Result
Or perhaps even better idea: Api::find() -> kube::Result<Option<K>> to mirror the behaviour of .find for slices and iterators

@imp Does #809 satisfy your requirements?

Yeah, that's exactly that. The name try_get wouldn't be my first choice, because in other places in Rust try_  is a Result<T, U> counterpart of otherwise infallible operation. However, in kube almost everything is kube::Result<T>, so it may hide the intention. Other than that - cool!


(RocMan) Smooth ghost and skeleton collision

@db2882, pat asked me to assign you to this since you dealt with kinect skeleton smoothing before this? Right the now the issue is when the skeleton collides with the ghost, we detect the collision too many times, and so the lives we have in the RocMan decrement too quickly (e.g. 4 at a time when it appears that we collide once with the ghost).

@patxu tagging you

Fixed with #299 - @db2882


ProjectionExpression with ExpressionAttributeNames causes pop index out of range error.

boto==2.45.0
boto3==1.4.4
botocore==1.5.45
moto==0.4.31
Issue:
When a ProjectionExpression and ExpressionAttributeNames are used in tandem with KeyConditionExpression, the resulting query fails due to logic within moto.dynamodb2.responses.query.  Logic requires expressions to be ordered correctly, specifying ExpressionAttributeNames causes the ordering and indexes to be incorrect and can result in IndexError pop index out of range or other unintended results.
Failure occurs on this line.
https://github.com/spulec/moto/blob/0.4.31/moto/dynamodb2/responses.py#L290 as a result of the key_map looking like this:
<type 'list'>: [u'date', u'fail', u'id', u'date', u'percent', u'timestamp']
The hash key index would result in 2.  This index would be used to lookup the matching expression in in line 290 above, where expressions is:
<type 'list'>: [u'(#n0 = :v0', u'#n1 = :v1)']
No index 2 would exist.
Example Failure:
        args = {
            'TableName': 'mytable',
            'KeyConditionExpression': (
                Key('id').eq('myid')
            ),
            'ProjectionExpression': 'id, #date, #percent, #fail, #timestamp',
            'ExpressionAttributeNames': {
                '#date': 'date',
                '#percent': 'percent',
                '#fail': 'fail',
                '#timestamp': 'timestamp'
            }
        }
        args['KeyConditionExpression'] &= Key('date').eq(123456789)

Workaround:
Expressions attributes for the hash and range keys, generated by boto look like ('#n0', 'id') and ('#n1', 'date'), these can be forced to the top of the key mapping list once it is sorted by prefixing ExpressionAttributeNames with z forcing them to the bottom of the list, so a valid index for the hash and range key are returned.
        args = {
            'TableName': 'mytable',
            'KeyConditionExpression': (
                Key('id').eq('myid')
            ),
            'ProjectionExpression': 'id, #zdate, #zpercent, #zfail, #ztimestamp',
            'ExpressionAttributeNames': {
                '#zdate': 'date',
                '#zpercent': 'percent',
                '#zfail': 'fail',
                '#ztimestamp': 'timestamp'
            }
        }
        args['KeyConditionExpression'] &= Key('date').eq(123456789)

This still an issue? Moto is now on version 1.1.22

Going to close; feel free to reopen if this is still happening against the latest version.


Undefined Acronym LUN

LUN did not immediately come to mind when reading this article where it is used 43 times.  It would help to say Logical Unit Number (LUN) the first time it is used.

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

ID: 9d7bd11a-e693-26a0-d374-5cfb1d2335d3
Version Independent ID: bc9a2fb3-fa85-4ec0-8e0f-6e7c4906262b
Content: Volume Shadow Copy Service
Content Source: WindowsServerDocs/storage/file-server/volume-shadow-copy-service.md
Product: windows-server
Technology: storage
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

Fair point, the text "a Logical Unit Number (LUN)" in 12 other pages, but none of them underneath the Storage section/chapters.
Then again, I was wondering how common a problem it is for IT personnel to get as far as the Storage documentation section without ever having seen the acronym LUN before in relation to computer (server) storage.

There you go. Sorry for the delay. PR #4952 is ready for review and comments.


allow skipping optional arguments

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This is generated code. Changes should be made to the code generator template. More info about the code generator can be found here: https://github.com/heroiclabs/nakama-defold/tree/master/codegen

Crazy stuff!

What we need is to change this:
https://github.com/heroiclabs/nakama-defold/blob/master/codegen/realtime.py#L203-L204
We want to check if a value is of the correct type or nil. Example:
assert(_G.type(some_string_var) == 'string' or some_string_var == nil)

So the relevant lines of the code generator should be changed to:
	for prop in props:
		lua = lua + "	assert(_G.type(%s) == '%s' or %s == nil)\n" % (prop["name"], prop["type"], prop["name"])

@britzl I would guess this shall only happend for args[4:] as first 3 are essential?

Oh it's in python? Thank god...

I would guess this shall only happen for args[4:] as the first 3 are essential? And only for this specific function right...

I would assume that there are other functions which also have optional arguments. We either do it for all functions and all arguments or none at all. How can we know which arguments that are optional if the API specification doesn't state it?

@britzl thats exactly what we discussed in the issue with missing docs... I guess if doing it for all of them would be a quick fix, but then if user doesnt give any parameters at all, lua will not throw any errors, only server will - could be a little more tricky to debug...

@britzl alright the argument actually makes a lot of sense. Just wish we had docs to refer to.. Lets go for the change.

Duplicate of https://github.com/heroiclabs/nakama-defold/pull/47


WIP: Sync with master of kube-state-metrics

Hmm, we've got a chicken-and-egg problem because the --metric-blacklist CLI argument has been (rightfully) renamed to --metric-allowlist.
https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_kube-state-metrics/29/pull-ci-openshift-kube-state-metrics-master-e2e-aws/1276490219033464832/artifacts/e2e-aws/gather-extra/pods/openshift-monitoring_kube-state-metrics-7f5487c978-b7ct9_kube-state-metrics.log

/close
we decided to go with 1.9.7


Top-bar / off-canvas parent link

Hello.
I just find out that if you have a Parent page with content, you can't access it from the mobiles menus...
Exemple: Home->Guitars->Acoustic. If I want o access "guitars", because this page has content and is the parent of the page "acoustic", I can't from the mobile menus... I must have somewhere a walker I used a long time ago (Before foundationPress) that generate the parent link in the "sub-menu"...

Oups, my mistake, it's here, it was a CSS matter for the top-bar...
BUT for the Off-canvas, the Parent item is not generated...

This is the WP-admin menu structure for the FoundationPress demo site.

If you look at the site in a mobile browser, you will see that all links in the off-canvas menu works as expected. Am I missing something?

Arf, I didn't think of adding them in the mobile menu! I was stuck on the "automatic generation of the link" like in the top-bar, my head was in "coding" mod...
Sorry!


Recruit a second maintainer for py-libp2p

@pacrob is mostly a lone maintainer of py-libp2p. I would try my best to recruit a new maintainer to help out and give some more momentum to the project. One idea is to run a "mission impossible" micro-hackathon to get the py-libp2p implementation into the multidimensional interop testing system in 24 hours.


add functionality to specify filename of annotation csv that predict generates

[ ] add annot_csv_filename parameter to core.predict
[ ] with default None that then defaults to the input csv filename + predict (or whatever it is now), maybe with a timestamp?
[ ] add annot_csv_filename attribute to PredictConfig
[ ] and use that attribute when calling core.predict in cli.predict

done in #232


fix(cdk/drag-drop): add conditional to scroll update

Fix proposed by internal user to fix an issue with dragging. Open for discussion on whether this fix is valid.

What issue is this supposed to fix? The idea with this block of code is to update the cached dimensions whenever something within the container is scrolled. I think that would be valid when the container itself is scrolled too.


riot crash when try to open any file in the room

If I press by file link - riot crash. On screenshot I try press on "Отчёт по ЗЭС.xlsx". This tihs occur only on android 8.0. I try on android 6.01, android 4 - file opened without any problem.
Steps to reproduce:

Send file to room (pdf or xlsx)
Press on this fule in this room
Riot crash

Riot version: 0.8.15 (G-b150)
Phone: Samsung Galaxy A5 (2017)
Android version: 8.0.0
Screenshot:

logcat:
logcat.log

Same here with some VCFs.
Luckily the file is already downloaded and available in the notification list or the Download folder.
Riot version: 0.8.15 (G-b150)
Phone: Xiaomi Mi A1 (2017)
Android version: 8.1.0 (AospExtended-v5.8-OFFICIAL)

Duplicate of #2573


finish Gittools module [development_path_git]

scan for TODO
create more tests

We have an issue due to cycle import
After refactor,

publisher_config/config.v imports gittools module and use it inside config_load and process_site_repo functions
gittools/gittools.vimports publisher_config and use it inside new and init_codewww functions

Suggestions:

Move functions from one module to another, so one module uses the other one
Separate the functions that cause this conflict in a new module


Add KardiaChain network (KAI)

Description

[X] Symbol: KAI
[X] ChainId: 24
[X] Website: https://kardiachain.io/
[X]  Block-Explorer: https://explorer.kardiachain.io/
[X] slip-0044 type: None

Additional comments
First PR #234

This has already been added here: https://github.com/LedgerHQ/app-ethereum/pull/289


0 byte websocket message breaks future sends

Might be a bug in pipelines
/cc @anurse

Receiving a 0-byte message or sending one?  Looks like a Pipelines thing that was fixed. I'm sending a PR with an additional test to help ensure this doesn't crop up again.


.pb file is larger than .h5

I'm trying to reduce the size of an existing .h5 model (VGG16) before using it for inference. After executing the script, the resulting .pb file is even larger than the .h5 file. Is this a behavior that can occur? I hoped the .pb file will be significantly smaller.

I'm trying to reduce the size of an existing .h5 model (VGG16) before using it for inference. After executing the script, the resulting .pb file is even larger than the .h5 file. Is this a behavior that can occur? I hoped the .pb file will be significantly smaller.

did you find a solution?

I am not sure why the size is bigger, but I never expected it to be "significantly smaller". Please note that Keras is only a wrapper for the backends it supports (i.e. TensorFlow). So, the converted model should have relatively the same size.


Do you rewrite the replay parser based on manta or clarity?

In the readme you mention
`ReDota is a heavily derived project and stands on the shoulders of giants, notably parsers by Dotabuff and Skadistats.
Special thanks to community members from OpenDota and ModDota who assisted in deciphering replay specifics.`
But when I read your code for the past few days, it look you rewrite it in js.
I currently trying to make something like reDota but run on terminal (tui) with go. Im just a bit lost about the dota2 replay structure or the anatomy.

Hi! Legit question, and it's not particularly clear from the README.
Most things under src/lib/parser are ported from Manta (Go) to JavaScript so it's usable directly in the browser without server involvement. The files have a comment on which source file they map to.
That said, there are some bits and pieces that come from Clarity (Java) instead, such as string table handling.


Hash Table in C++

Want to work on this issue?
Yes

Yes, You can take up this issue.

Can you please assign this issue to me ?


windows invocation

Hi Gabe.
I found an issue with the way tq is invoked on Windows.

the stderr has "java not found" but the subprocess did not exit with a non-zero code.
...to fix the "java not found" issue you have to update the env that you're passing to the subprocesss env.update(os.environ).

In any case, you don't really need the windows and bash scripts as they are just setting env vars. You can have that logic in python and pass it through the env arg of subprocess.run. Also, instead of a script (string) you can just make an args sequence (or just the command as a string). This way you don't have to deal with the difference.

HI @majidaldo! I don't have access to a Windows computer to reproduce this, so it would be great to have some help in fixing this implementation. Do you have any cycles over the next couple weeks?

HI @majidaldo! I don't have access to a Windows computer to reproduce this, so it would be great to have some help in fixing this implementation. Do you have any cycles over the next couple weeks?

ya when we get into october :)
but some preliminaries:

why is the 'brick' in the repo name? it could be called py-tq-shacl
testing suite
...github has windows runners. like i mentioned, if you just use python to abstract away the differences, windows is pretty much guaranteed to work.


React scripts build minify error

I am trying to build my solution with react-scripts but getting the following error:
Creating an optimized production build...
Failed to compile.

Failed to minify the code from this file:

 	./node_modules/@sendgrid/helpers/helpers/convert-keys.js:24

Read more here: http://bit.ly/2tRViJ9

What the link told me is that the sendgridib isnt compiled to ES5 and, beacause of that, it is getting an error.
What should I do?

Hello @odelucca,
It seems like there are a couple of workarounds at the link you provided that you can try while you await our solution. If you happen to get one of those workarounds working, please let us know.
Meanwhile, I have added this to our backlog. For this issue to gain priority in our backlog, we need additional +1's or a PR. When we receive a PR, that provides the biggest jump in priority.
With Best Regards,
Elmer

Same issue as @odelucca,
Hopefully a solution can be figured out very soon or SendGrid will have to be replaced with a competitor plugin in my application unfortunately....Have to be able to run React production builds...

@odelucca Did you happen to find a solution that works until this is resolved?

for @mvivonetto and everyone who is looking for a solution.
I solve that problem changing the logic of my code. Instead of trying to sending a request to sendgrid directly from the frontend (my React application) I developed a endpoint on my API (Node Koa backend) that receives the request to send an email and uses the sendgrid lib to do so. It worked and it was much more secure also.
=)

Hello @mvivonetto,
Can you try installing the latest Uglifyjs webpack plugin?
And yes, per @odelucca (thanks for helping out), if you are trying to send email through your front end, that is not recommended as you will be exposing your SendGrid API key.
With Best Regards,
Elmer

Same issue here. Has this seriously not been solved yet???

As called out by @thinkingserious, exposing your API key in the browser is a security vulnerability and should be avoided. @odelucca explained a more proper solution.
That said, I've tested against react-scripts@2 without issue, as described here.
If you simply must run this in the front-end, upgrading react-scripts should resolve the issue.


Midea Wired Remote Controller KJR-120

Hello,
I’m planning to buy a Ferroli Heat Pump that uses a remote wired controller based on the Midea KJR-120 Modbus mapping.
After comparing the mapping from the file provided with the remote control to the addresses in the YAML file published here, many of the addresses don’t seem to match. Unfortunately, I’m not very familiar with RS485 protocols, and I was hoping someone could help me understand how to modify the YAML file to make everything work.
I don’t have the heat pump installed yet, so I’m unable to run tests at the moment, but I want to start writing the ESPHome code and have it ready for when the heat pump gets installed.
Any help would be greatly appreciated!
Thanks
[
120F-modbus-mapping-table-0052003366314-V-B.pdf
](url)

Makes me wonder,
I see a difference for the registers 11 till 20,
(mine has 11,12 and 13, which are not in, but I don't miss them)
But is almost looks like 14 till 17 are the same as register 0 bit 0 to 3
also registers 187 till 197 seems to be new, and everything above 272

@wizardmelon Using this interface -your heatpump will be in 80-90% working with this implementation.
In your heatpump registry 148-187 is more statistical view in real time and divided COP for DHW/ heating etc

Curious if you got anywhere with this. I just had a ducted Heat Pump installed (rebrand of Midea EVOX) with a KJR-120N controller. Unfortunately, there are no posted modbus register lists that I can find.
I am hoping I can use some trial-and-error to get some basic information and controls.

I think the original question is answered, closing this one


[AITT] add aitt option

Set AITT option to open AITT handle.
Signed-off-by: Jaeyun<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #95. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-edge/ci/repo-workers/pr-checker/95-202209201808120.52874708175659-f1e5cc96f00cef38befafca44e2b163a6d2d7cd1/.

We need force update - new interface of AITT (aitt option handle) before group sr.


Ability to define a custom Windows Cluster name and cluster object names

Is your feature request related to a problem? Please describe.
The feature is to cater for an environment where SDAF is used to set up a new SAP landscape, but existing Windows clusters exist with the same naming standard - scscl. Also the DNS name for the DB HA entry.
Describe the solution you'd like
Ability to define the name of the cluster and cluster objects and DB DNS entry
Describe alternatives you've considered
There is no alternative, as the names already exist in AD/DNS, and are in use by existing production systems, it is not possible to re-use them.
Additional context
The code below implements a standard naming convention which has already been used in the existing SAP landscape:

name:                                "5.6 SCSERS - Set the SCS Virtual Instance hostname"
ansible.builtin.set_fact:
scs_virtual_hostname:              "{{ sap_sid | lower }}scs{{ scs_instance_number }}cl1"
when:

scs_high_availability

name:                                "5.6 SCSERS - Set the ERS Virtual Instance hostname"
ansible.builtin.set_fact:
ers_virtual_hostname:              "{{ sap_sid | lower }}ers{{ ers_instance_number }}cl2"
when:

scs_high_availability

We can now add these via the configuration_settings block to the system tfvars file. Which will add them to the sap-parameters.yaml.
# configuration_settings is a dictionary containing values that will be persisted in sap-parameters.yaml
configuration_settings = {
  ora_release = "19",
  ora_version = "19.0.0",
  oracle_sbp_patch = "SAP19P_2305-70004508.ZIP",
  oraclegrid_sbp_patch = "SGR19P_2308-70004550.ZIP",
}


Docs: clarify rationale for button group on links

clarify that putting links in a button group is, in essence, an alternative to using the navigation component (and cross-reference it)
remove the non-sequitur about using .active...that's irrelevant here, as it's already mentioned in the docs page for .btn. otherwise, this would then also need the whole extra explanation about conveying meaning with aria-current etc, which is already covered in ample detail in the navs page

@patrickhlauke this needs to be backported manually, I don't even know if we have those snippets in v4-dev.

This doesn't seem to apply to v4-dev. If you still think it does, re-add it in the v4-next project and make a PR against v4-dev.

ah you're right, could have sworn v4 also had a link button group example, but i must have dreamt it


Fix a ledger bug

This commit fixes the MULTIPLE_OPEN_CONNECTIONS_DISALLOWED error. The problem was that the user could only send one transaction after connected to wallet.

Tested a couple of delegation/undelagations on physical Ledger. Consecutive transactions went through.


Encountered error while using the extension

Got following error while using extension, might be something related to git settings where agent is hosted. Can someone please guide on how to proceed
fatal: could not read Username for 'http://abc.xyz.com': terminal prompts disabled.

hello @sarang3614, could you tell us a little more about your setup? It's incredibly difficult for us to offer much guidance with the minimal information provided in the issue description.
For example:

what's the host platform for the source repository?
does the source repository require authentication (and if so did you include that in your task configuration)?
what's the host platform for the destination repository?
is your pipeline running on the Microsoft-hosted agents or are you using a self-hosted agent?

hi team,
Any suggestions on above..

host platform for destination repository is AzureDevops hosted as SAAS.

Just to confirm, you've got a PAT being passed in for the destination auth field correctly right? Always need to rule out the easy problems first, as I've had a couple cases myself where I had a typo in the variable name I was using for one of those auth fields that was causing problems

Yes, since it was raised, I have checked and can confirm - PAT for destination auth field is passed correctly.

Could you please re-run your job with diagnostics enabled and share the log output (feel free to scrub/obfuscate anything you feel is sensitive). As an FYI for any future reports, would encourage you to leverage our bug issue template and provide the information up front as that helps to minimize the elongated back and forth dialog to try to get the requisite information

Thanks for the response, attached is the log.
logs_797.zip

Thanks, but could you please grab the subset of your log contents relative to the task and paste it inline? You can look for a section header similar to the one shown below.
Having the relevant information inline within the issue will be easier to review, cross reference, and locate later on over an archive file that has to be downloaded/extracted/etc.
2018-12-04T23:30:15.1091356Z ##[section]Starting: Mirror Git Repository
2018-12-04T23:30:15.1094369Z ==============================================================================
2018-12-04T23:30:15.1094484Z Task         : Mirror Git Repository
2018-12-04T23:30:15.1094525Z Description  : A straightforward utility to mirror one Git repository to another location
2018-12-04T23:30:15.1094713Z Version      : 1.1.7
2018-12-04T23:30:15.1094811Z Author       : Swellaby
2018-12-04T23:30:15.1094852Z Help         : [More Information](https://github.com/swellaby/vsts-mirror-git-repository)

hi, sorry, my responses are delayed due to holiday season. Below is the log snipped you are looking for :
2020-12-23T18:53:24.5578624Z ##[debug]C:\Agent\externals\git\cmd\git.exe arg: --mirror
2020-12-23T18:53:24.5579846Z ##[debug]C:\Agent\externals\git\cmd\git.exe arg<EMAIL_ADDRESS>2020-12-23T18:53:24.5580423Z ##[debug]C:\Agent\externals\git\cmd\git.exe arg: PLM
2020-12-23T18:53:24.5583221Z ##[debug]exec tool: C:\Agent\externals\git\cmd\git.exe
2020-12-23T18:53:24.5583537Z ##[debug]arguments:
2020-12-23T18:53:24.5583763Z ##[debug]   -c
2020-12-23T18:53:24.5584028Z ##[debug]   http.sslVerify=false
2020-12-23T18:53:24.5584272Z ##[debug]   clone
2020-12-23T18:53:24.5584515Z ##[debug]   --mirror
2020-12-23T18:53:24.5584908Z ##[debug]<EMAIL_ADDRESS>2020-12-23T18:53:24.5585220Z ##[debug]   PLM
2020-12-23T18:53:24.5590991Z [command]C:\Agent\externals\git\cmd\git.exe -c http.sslVerify=false clone --mirror<EMAIL_ADDRESS>PLM
2020-12-23T18:53:25.2121770Z Cloning into bare repository 'PLM'...
2020-12-23T18:53:25.4628877Z fatal: could not read Password for<EMAIL_ADDRESS>terminal prompts disabled
2020-12-23T18:53:25.4903834Z ##[debug]Exit code 128 received from tool 'C:\Agent\externals\git\cmd\git.exe'
2020-12-23T18:53:25.4908486Z ##[debug]STDIO streams have closed for tool 'C:\Agent\externals\git\cmd\git.exe'
2020-12-23T18:53:25.5711092Z ##[debug]task result: Failed
2020-12-23T18:53:25.5739670Z ##[error]Error: The process 'C:\Agent\externals\git\cmd\git.exe' failed with exit code 128
2020-12-23T18:53:25.5749153Z ##[debug]Processed: ##vso[task.issue type=error;]Error: The process 'C:\Agent\externals\git\cmd\git.exe' failed with exit code 128
2020-12-23T18:53:25.5756193Z ##[debug]Processed: ##vso[task.complete result=Failed;]Error: The process 'C:\Agent\externals\git\cmd\git.exe' failed with exit code 128
2020-12-23T18:53:25.5784067Z ##[section]Finishing: Mirror Git Repository to<EMAIL_ADDRESS>

hi, sorry, my responses are delayed due to holiday season.

No worries.
This line in particular looks problematic

<EMAIL_ADDRESS>
Did you strip the value from the userinfo component on the url here? (anything between the protocol and the @)
Given the above comment I am guessing that this is the self-hosted Gitlab instance, but if you didn't strip anything out of the log then this looks there's an issue with your input for the Source Repository - Personal Access Token field
For example with this config:

The slugs show the pat (obfuscated in the logs by the agent since it's a secure variable) when configured or null when authentication isn't needed for anonymous clones:
<EMAIL_ADDRESS>
<EMAIL_ADDRESS>

hi @calebcartwright ,
yes I did strip the value before sharing.

You are right, this is self (Organization) hosted GitLab instance.
. The input from the source repository seems to be okay. is there a chance where we can connect on a call on and discuss, please let me know.

is there a chance where we can connect on a call on and discuss, please let me know.

No, I don't see that being likely to happen, sorry.
The mirror task provided by this extension is an extremely lightweight wrapper that ultimately just runs a couple git invocations, and what you're experiencing right now is that the following git clone command is failing to clone the repository on your self-hosted Gitlab instance from your self-hosted agent:
git -c http.sslVerify=false clone --mirror<EMAIL_ADDRESS>
The underlying issue is almost certainly related to the auth value you're utilizing or with elements in your setup (e.g. supported auth mechanisms on your Gitlab instance, git version on your pipeline agent, etc.), neither of which we could really assist with and both of which are well outside the scope of the open source support we're willing/able to provide for this extension.
You could try running that git command directly from your pipeline (presumably via a Command Line Script or inline PowerShell task since you are apparently on Windows), but I would expect the exact same behavior so long as the auth components are the same. I'm not terribly familiar with Gitlab, but I vaguely recall past reports of users having better luck utilizing a username:password value for the source auth after having issues with token usage, so you may want to try that as well:
i.e.

hi @calebcartwright , Appreciate all of the support extended and your valuable inputs.
Let me check the supported auth settings on the gitlab and the other try out you mentioned, Thanks.

I'm not terribly familiar with Gitlab, but I vaguely recall past reports of users having better luck utilizing a username:password value for the source auth after having issues with token usage, so you may want to try that as well:

hi @calebcartwright  - the mentioned setting worked and believe the add-in is working as expected. I encountered another error while mirroring, however it is problem with my source repository size.
Thanks for your support.


Inconsistent string interpolation

I'm sure this is likely an issue with the way I've set things up (latest node, bable, webpack, ) but I cannot get string interpolation to work when using  Logger.get. ex:
import Logger from 'js-logger'

Logger.useDefaults()
Logger.warn('TEST')
Logger.warn('TEST %sPOLATED', 'INTER')
const log = Logger.get('Log')
log.warn('Test')
log.warn('TEST %sPOLATED', 'INTER')

Will output:
TEST
TEST INTERPOLATED
[Log] Test
[Log] TEST %sPOLATED INTER

So what am I not understanding here?
In addition, if I do not use Logger.useDefaults(), for example by replacing that line with  Logger.setLevel(Logger.INFO), I won't see any logs at all. Any thoughts as to why this occurs?

Hi @magixx, sorry for the slow response.
Yep, the broken string interpolation is indeed a bug caused by the default log message formatter which will unshift a named Logger's name into the messages array; as you may be aware, console.log() and friends will only perform interpolation on first value.


Remove package lock file

Hello @cgdibble ,
Overall changes seems good to me. May I know the reason for removing the flag "--recursive" ?
Thanks

It wasn't doing anything but I honestly didn't notice I'd committed that. Good catch!


action-profile schema to be updated in core-model-1-4:control-construct

Proposal :
action-profile-1-0:action-profile-pac shall be added in line 3944.
Since the attribute "action-profile-1-0:action-profile-pac"  is not present in "required" section of action-profile schema of /core-model-1-4:control-construct, it causes the input profile-instance to match more than one schemas.
This results in validation failure in "open-api validator" as "oneOf" will allow only one match of schema for an instance. This gives 500 Internal server error response code.
Proposal:
In order to avoid this failure, we would need to add this attribute in "required" section of /core-model-1-4:control-construct :: profile-collection :: action-profile schema (line 3944 in AP_OAS  file)

Also, as per comment provided in above image, I was just going through the bug in mock server and could find a temporary workaround in https://github.com/postmanlabs/postman-app-support/issues/10928#issuecomment-1205985845 .
I tried the workaround, and it is working fine. But, the problem is the workaround given could be applied only when importing a collection into an environment. We could not change the settings in working specification

As per discussion on 17th Feb 2023, checked the schema by including "additionalProperties: false" property constraint to schema of "action-profile" of "core-model-1-4:control-construct". This constraint avoids the 500 Internal server error and the expected response could be obtained as output. A separate issue has been created https://github.com/openBackhaul/ApplicationPattern/issues/578 for updating the OAS. Hence closing this issue


RFC: API Change: Bluetooth Mesh

Problem Description: https://github.com/zephyrproject-rtos/zephyr/pull/57215

Change Define Mesh element as const, the reason is that the Mesh Profile clearly stipulates that Mesh nodes cannot change their own element definitions.

Proposed Change (detailed):

The elem->addr has been removed, just replace with API bt_mesh_elem_addr_get

Detailed RFC:

Function call changes
The elem->addr has been removed, just replace with API bt_mesh_elem_addr_get
Device Tree changes (source and bindings)
No
Kconfig option changes
No

Dependencies:
Any access elem->addr should replace with bt_mesh_elem_addr_get.

@LingaoM you are missing a couple of steps:
https://docs.zephyrproject.org/latest/develop/api/api_lifecycle.html#introducing-incompatible-changes
In particular, you need to send an email to devel@ and bring the topic to the Architecture WG meeting (you don't need to be present, just ask for the topic to be discussed there).

@LingaoM you are missing a couple of steps: https://docs.zephyrproject.org/latest/develop/api/api_lifecycle.html#introducing-incompatible-changes
In particular, you need to send an email to devel@ and bring the topic to the Architecture WG meeting (you don't need to be present, just ask for the topic to be discussed there).

Thanks for the reminder, done.

Merged


golang version update in circle.yml

To set new version of Golang, edit GOVERSION in circle.yml as below
machine:
  environment:
    GOVERSION: "1.5.3"

LGTM!


[Roadmap] Login and Fetch User Specific Data

@bthaile -- I am going to move this epic off the Roadmap, since it is being use for organiational purposes not as a piece of work with and end date.
Each ticket in here should ultimately be put into some deliverable epic.

I agree, if it makes sense, we prob need to focus the effort across UI and backend for some of these.

closing this Epic.


Add startup/exit delay option

To work around regression in R2Northstar/NorthstarMasterServer@fa4fd6c9c01503288d563c8fc3762439dcdfc425.

Obsoleted by https://github.com/R2Northstar/NorthstarLauncher/commit/76864937f3f72ac1fb7bc29ea92864d31c05227d (R2Northstar/NorthstarLauncher#187).


Beginning date for revenues can be wrong.

Which version of Node.js are you running (node -v)?
6.10.1
Which version of urcli are you running (urcli -V)?
2.5.0
What behavior were you expecting to see?
When using revenue to calculate the earnings for a specific month, I would expect to get:
17:37 $ urcli revenue 2

Earnings Report for 2017-02-01 to 2017-03-01:
=============================================

What was the actual behavior?
17:37 $ urcli revenue 2

Earnings Report for 2017-02-06 to 2017-03-01:
=============================================

The first day is not the first day of the month.
Describe the steps needed to reproduce the problem?

urcli revenue 2

What is your Operating System (e.g., Linux Ubuntu, MacOS, Windows)?
Ubuntu 16.04
Comments
I introduced this bug when changing the code that calculates the first day on Udacity. Since I didn't review anything on the first five days of February, revenue is assuming that I started on Udacity at 2017-02-06, which is not.
A solution to this bug has already been coded in v3 branch

Change made to address #52  fix this.

Can we fix this in v2 easily?

Well, I think we can go back to the previous version. Do you think is worth checking?

Since a lot of users rely on urcli to check their earnings, I think it is worth checking.


zsh crashes when completion list doesn't fit on screen

removing zstyle ':completion:*:default' list-prompt line saves it from crash.

Can you give an example?

when i type ls /bin/ and press tab, it show me files that can shows up on the screen and when i press any key other than Enter it crashed with core dumped.

I cannot reproduce. It doesn't not crash here with the latest Zsh.
On Thu, Jun 18, 2015 at 6:14 PM Shashank Chhikara<EMAIL_ADDRESS>wrote:

when i type ls /bin/ and press tab, it show me files that can shows up on
the screen and when i press any key other than Enter it crashed with core
dumped.
—
Reply to this email directly or view it on GitHub
https://github.com/sorin-ionescu/prezto/issues/907#issuecomment-113303010
.

after updating zsh to 5.0.8 from 5.0.7 its fixed!!! thanks.

It still crashes when pressing any arrow key, PgUp, PgDn or any special key that send more than 1 char to terminal.

I was having segfaults using some keys during auto complete too, but I discovered it was the fault of running both prezto and grml-zsh-config at the same time (in Arch Linux, grml-zsh-config is a package that when installed its location is /etc/zsh/zshrc, so it is sourced by every user). Putting unsetopt GLOBAL_RCS inside ~/.zshenv solved the problem for me.

Removing the package grml-zsh-config from my Arch Linux fixes the issue. thanks @m45t3r


Checkboxes has both ticked and filled state on Linux

Description
Checkboxes has both ticked and filled state on Linux
Include screenshot / video recording if possible.

Configuration

Firefox Version: 122
OS: (eg. Windows, macOS, etc.) Linux Fedora 39

Same as https://github.com/edelvarden/material-fox-updated/commit/b9393bd9bb3a304258c2493cd95abf18bfb9e9a2

This should be fixed now in the latest commit of the theme.


100% codecov in model.go

parser.go still has some hard to reach corners, will work on it some day. For now all the code we wrote in model.go has 100%. Also found a bug; fixed in this PR in model.go
Did some renaming and cleanup while I was there.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
Assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
3b379ac33359d0795aa3f870f3295b81f8d0d0c4
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: geeknoid
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [geeknoid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
0f328cedcf0b55b46d72735919458016104e54c1
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
0f328cedcf0b55b46d72735919458016104e54c1
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-v1alpha3.sh
0f328cedcf0b55b46d72735919458016104e54c1
link
/test istio-pilot-e2e-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ldemailly @geeknoid re-lgtm pls

That's why we have unit tests though. If the behavior changes, the test
should catch the problem.
On Fri, Mar 23, 2018 at 11:42 AM, Laurent Demailly<EMAIL_ADDRESS>
wrote:

@ldemailly commented on this pull request.
In mixer/tools/codegen/pkg/modelgen/model.go
https://github.com/istio/istio/pull/4490#discussion_r176831258:

@@ -338,10 +338,6 @@ func (m *Model) addTopLevelFields(fd *FileDescriptor) {

if tmplVariety, err := proto.GetExtension(fd.GetOptions(), tmpl.E_TemplateVariety); err == nil {
m.VarietyName = (*(tmplVariety.(*tmpl.TemplateVariety))).String()

} else {

until the caller changes... and we spend time figuring out what happens
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/4490#discussion_r176831258, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVucHSddN0NJ9us9X6e0kw0hQtlOSk9Lks5thUIUgaJpZM4S3765
.

@geeknoid @ldemailly IMHO, for this PR, there is no rule being violated. The code deleted was dead code to begin with. lgtm / no-lgtm ?

re "l g t m" : builds are very red, so you might need to fix that.
I was just commenting on the trend I see to get to 100% coverage at the expense of resilience (imo) but I don't own this code and you do whichever you feel right (and you do have valid points those being non exposed functions etc...).

@geeknoid lgtm ??

@geeknoid any reason you manually merged instead of typing "/lgtm" ?
https://groups.google.com/d/msgid/istio-dev/CALuuQPAw1dZg3YZ6PzJPb3%3DvQQcJ-7CghkW%3DCkA6u29fNHwEmQ%40mail.gmail.com


Optimization of Detector.collisions method

Changes

The whole logic to keep track of starting, ending and active collisions has been simplified. It used to be spread across 2 methods: Detector.collisions and Pairs.update. It is now segregated to the Detector.collisions method alone (Pairs.update was removed).
Collision pairs are no stored on bodies (the body with the lowest id stores the collision), it allowed to get rid of the slow map lookups and pair id generation - this was achieved efficiently by maintaining a list of bodies sorted by id on each composite.

Includes #522, #526, #527, #528
Results
The heavier the simulation, the higher the gains. Reduced resource usage can be as high as 54.4% (Stress 2). All the measured tests seem to benefit from the optimization.
Stress - Performance gain: 46.6%
Before

After

Stress 2 - Performance gain: 54.4%
Before

After

Bridge - Performance gain: 21.4%
Before

After

Events - Performance gain: 18.9%
Before

After

Notes:

In general, the higher the number of collisions, the higher the performance gain.
We can notice that methods such as solveVelocity benefit from the optimization as well as there is no need to loop over inactive pairs anymore.
Detector.collisions method is running faster in all cases but the SAT.collides method does not benefit from gains when the number of collisions is small.
Pairs.update and Pair.id method have disappeared
Grid.update method benefits from a good performance gain in general.

Overall results
I wanted to resume the overall performance gain achieved by the different optimizations in #522, #526, #527, #528, including this PR:
Stress - Performance gain: 81% (5.3 x faster)
Stress 2 - Performance gain: 84% (6.2 x faster)
Bridge - Performance gain: 52% (2.1 x faster)
Events - Performance gain: 42% (1.7 x faster)

Hi there, just checking in.
Are these optimization PRs still going places?

performance gain on Stress 2 is now about 9x!

Impressive work! This is going to take some time to review, but I've tried it out and the gains appear to be huge. Looks like we'll be needing a harder stress test too :)
But there are a few issues I can see so far:

the ragdoll demo is missing the ragdoll
the debugger shows an extra thread in the ragdoll demo (might be related to the above bug)
the world clear button on the GUI doesn't work now
the boxes in the catapult demo do not fly very high anymore (not sure if that indicates anything)

I had fixed some of the issues in later PR. I imported the specific commits. I am not sure I fixed the extra thread issue. I am not sure how I can test it?
About the catapult, the behavior before and after seem the same.
Before:

After:

Screenshots of maximum reached heights.

Look promise and any things new?

I am looking forward to this merge as well

Any progress on merging these performance pull requests? All combined, they are a major improvement!


[LIVY-376] [Docs] Update README with new naming and links and move Docs to website

LIVY-376

The README has been updated to match our new Apache naming and links.
The API Documentationa and Examples have been moved to the website.
Apache LICENSE and NOTICE files have been added.

This PR is a pair with https://github.com/apache/incubator-livy-website/pull/5

@jerryshao @lresende mind taking a look? (1/2)

Codecov Report

Merging #21 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #21      +/-   ##
============================================
- Coverage     70.41%   70.39%   -0.02%
+ Complexity      777      776       -1
============================================
  Files            97       97
  Lines          5256     5256
  Branches        797      797
============================================
- Hits           3701     3700       -1
  Misses         1024     1024
- Partials        531      532       +1

Impacted Files
Coverage Δ
Complexity Δ

...java/org/apache/livy/rsc/rpc/KryoMessageCodec.java
94.33% <0%> (-3.78%)
18% <0%> (-1%)

...main/scala/org/apache/livy/server/LivyServer.scala
37.05% <0%> (+0.58%)
10% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

I would suggest to maintain API and examples in Livy source code, like what Spark did.

Docs are related to the specific version of Livy, when checking the APIs we should point to the right version of Livy.
Sometimes when changing API, it usually requires to change docs, so it would be better to put docs into Livy code.

Ok, tomorrow I'll update the PRs to move the two API md files back and find a way to still show them on the website. Should the examples md file go with them?

Maybe examples are fine to stay in livy-website repo.

So the more I think about it, Spark is a unique case where the documentation is kept in the main repo then built and copied into the website repo. For most smaller projects I've seen where there's only a few files, like Livy, the docs are storied in the website. So I'm going to sleep on it and might open up the question to the dev list tomorrow.

My concern is that if we keep document in another repo, we may forget to update docs in another repo when we change some API related things in code.
Sure we can bring this out in mail list to hear about others. But thinking is putting things not frequently changed in livy-website repo, whereas API reference, configuration docs in main repo.

While we're discussing where to keep the Docs on the mailing list I made a minor update to the order and wording of the REAME. If we decide to keep the Docs here I'll move them back over in this PR and setup a way to display them on the website in a separate PR

@jerryshao I moved the docs back into this PR so we can focus on reviewing these changes then I can follow up with a PR that actually lets us build the Docs like in Spark and deploy them to the website.

Created LIVY-384 for followup mentioned above

@jerryshao addressed your comments, what do you think about my "Note" ?

LGTM, we could update the docs later when we have a first Apache release. I'm thinking of kicking off a first Apache release when all the migration things are done.

Yeah we should probably get it out soon, I'll try to speed up my web ui work so it can all get out in the release (I believe my only key remaining work after my current pr is auth support and selenium tests)

Thanks! Will merge it after travis test finished.

@ajbozarth can you please retrigger the travis?

I'm going to merge this, since it is an unrelated failure.


Jokeen/bunch o things

Just a whole bunch o' things!

Update to the latest Disnake 2.7.0, and run black formatter on the project
Fixed the AutoPublish cog incorrectly checking for int keys instead of str keys
Added User and Message commands for moderators to be able to create Private Threads easily
Updated the Points module to use timestamp tags, and changed the output for easier command copying on mobile
Added a check for when the #appeals channel gets updated, and then resets the permissions for the Muted role to allow them to send messages inside threads

Dyno edits the channel permissions every time someone gets muted, frustratingly

Added /looking-for commands for users to create postings for their groups/communities

This uses ephemeral messages and modals to generate the postings entirely within Discord
It sets a timer in the db for the specific type of posting, and lets the user know when (with a link to the current post) they are able to create a new post of that type
Moderators have the ability to delete postings, as well as reset individual timers for users

Runs a weekly cleanup on db file, so it wont explode in size over time

I still want to add documentation to a bunch of the features, but wanted to get the PR out there before I forgot >_>


Support for SystemD

Description
Support for SystemD
Motivation and Context
This enables support for SystemD in the sensu_service LWRP
How Has This Been Tested?
Tested in Test-Kitchen
Screenshots (if appropriate):
none
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.

Can this be merged soon?

Hi @shaneramey, thanks for the pull request.
I'm still learning about systemd myself, but it seems like your proposed implementation relies on systemd-sysv-generator to generate unit files that wrap the default sysv init scripts. In my testing so far it doesn't seem this will be sufficient.
When I test your changes in test-kitchen on ubuntu-1404 and ubuntu-1204, the services run but I'm pretty sure the services are actually being managed by upstart. e.g. there's no systemctl available in root's path, but the systemd-shim package is present to help us "fake it".
I also tested against the ubuntu-1604 platform where I'm sure systemd is being used, but systemctl thinks service isn't running:
vagrant@systemd-ubuntu-1604:~# systemctl status sensu-client
* sensu-client.service - LSB: Sensu monitoring framework client
   Loaded: loaded (/etc/init.d/sensu-client; bad; vendor preset: enabled)
   Active: inactive (dead)
     Docs: man:systemd-sysv-generator(8)

I think this is because Sensu services are forking into the background, and that if we want the unit files generated by systemd-sysv-generator to work, they will need to include PIDFile directives pointed at the PID files in /var/run/sensu.
I suspect that a fully functional implementation will need to make use of the systemd unit files that ship with Sensu (see /usr/share/sensu/systemd or https://github.com/sensu/sensu-build/tree/master/sensu_configs/systemd on github). Have you had a look at the options documented here? Any thoughts?
It would be great if this suite also had tests which verify that systemctl sees the service is running, etc. so that we know when a platform isn't really managing one or more Sensu services under systemd.

@cwjohnston Im also looking at this, im going to have a go now, and make another PR using those as templates

Marking this as wontfix for now, as we're working on refactoring our service scripts to better support systemd and others for Sensu 0.27 so this will all change soon anyway.


Unify NuGet casing with what's used elsewhere in this file

This has succeeded now. Github hasn't updated the status here. Feel free to merge.

Thanks, @kzu!


text style display

this is my code, Why are there only polygon and no text?
const polygon = new Polygon([
    [
      ['87.4337103', '43.9690231'],
      ['87.4331741', '43.9670592'],
      ['87.4346341', '43.9665165'],
      ['87.4351897', '43.9688487'],
      ['87.4337103', '43.9690231'],
    ],
  ]);

  const style = new Style({
    fill: new Fill({
      color: 'rgba(22, 195, 81, 0.3)',
    }),

    text: new Text({
      text: 'my Text',
      font: '13px sans-serif',
      fill: new Fill({
        color: '#fff',
      }),
      stroke: new Stroke({
        color: '#000',
        width: 2,
      }),
    }),
  });

  let feature = new Feature({
    geometry: polygon,
  });

  feature.setStyle(style);

  let source = new Vector({});

  source.addFeature(feature);

  let vectorLayer = new VectorLayer({
    source: source,
  });

  map.addLayer(vectorLayer);

Your polygon coordinates are strings, but should be numbers. Other than that, your code looks good and I do see the text as well. Try it out here: https://codesandbox.io/p/sandbox/brave-greider-hwx929?file=%2Fsrc%2Findex.js%3A13%2C6

Your polygon coordinates are strings, but should be numbers. Other than that, your code looks good and I do see the text as well. Try it out here: https://codesandbox.io/p/sandbox/brave-greider-hwx929?file=%2Fsrc%2Findex.js%3A13%2C6

Thank you. That's very helpful


Validation: preserveView

User story 1907185
Guidance: https://review.docs.microsoft.com/en-us/help/contribute/versioning-for-contributors?branch=master

User story 1909902
(Same files)

Docs Build status updates of commit 6e09061:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azps-6.6.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md
:white_check_mark:Succeeded
View (azps-6.6.0)

azps-6.6.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md
:white_check_mark:Succeeded
View (azps-6.6.0)

azps-7.0.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md
:white_check_mark:Succeeded

azps-7.0.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md
:white_check_mark:Succeeded

azps-7.1.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md
:white_check_mark:Succeeded
View (azps-7.1.0)

azps-7.1.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md
:white_check_mark:Succeeded
View (azps-7.1.0)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 3e431de:
:warning: Validation status: warnings

File
Status
Preview URL
Details

azps-6.6.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-6.6.0)
Details

azps-6.6.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-6.6.0)
Details

azps-7.1.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-7.1.0)
Details

azps-7.1.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-7.1.0)
Details

azps-7.0.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md
:white_check_mark:Succeeded

azps-7.0.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md
:white_check_mark:Succeeded

azps-6.6.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: file-not-found - See documentation] Invalid file link: '../az.monitoringsolutions/get-azmonitorloganalyticssolution'.

azps-6.6.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: file-not-found - See documentation] Invalid file link: '../az.monitoringsolutions/get-azmonitorloganalyticssolution'.

azps-7.1.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: file-not-found - See documentation] Invalid file link: '../az.monitoringsolutions/get-azmonitorloganalyticssolution'.

azps-7.1.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: file-not-found - See documentation] Invalid file link: '../az.monitoringsolutions/get-azmonitorloganalyticssolution'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 3bfef6f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

azps-6.6.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-6.6.0)
Details

azps-6.6.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-6.6.0)
Details

azps-7.1.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-7.1.0)
Details

azps-7.1.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-7.1.0)
Details

azps-7.0.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md
:white_check_mark:Succeeded

azps-7.0.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md
:white_check_mark:Succeeded

azps-6.6.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: file-not-found - See documentation] Invalid file link: '../../az.monitoringsolutions/get-azmonitorloganalyticssolution'.

azps-6.6.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: file-not-found - See documentation] Invalid file link: '../../az.monitoringsolutions/get-azmonitorloganalyticssolution'.

azps-7.1.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: file-not-found - See documentation] Invalid file link: '../../az.monitoringsolutions/get-azmonitorloganalyticssolution'.

azps-7.1.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: file-not-found - See documentation] Invalid file link: '../../az.monitoringsolutions/get-azmonitorloganalyticssolution'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 7940ec6:
:warning: Validation status: warnings

File
Status
Preview URL
Details

azps-6.6.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-6.6.0)
Details

azps-6.6.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-6.6.0)
Details

azps-7.1.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-7.1.0)
Details

azps-7.1.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-7.1.0)
Details

azps-7.0.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md
:white_check_mark:Succeeded

azps-7.0.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md
:white_check_mark:Succeeded

azps-6.6.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: file-not-found - See documentation] Invalid file link: '~/az.monitoringsolutions/get-azmonitorloganalyticssolution.md'.

azps-6.6.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: file-not-found - See documentation] Invalid file link: '~/az.monitoringsolutions/get-azmonitorloganalyticssolution.md'.

azps-7.1.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: file-not-found - See documentation] Invalid file link: '~/az.monitoringsolutions/get-azmonitorloganalyticssolution.md'.

azps-7.1.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: file-not-found - See documentation] Invalid file link: '~/az.monitoringsolutions/get-azmonitorloganalyticssolution.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5c5062e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

azps-6.6.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-6.6.0)
Details

azps-6.6.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-6.6.0)
Details

azps-7.1.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-7.1.0)
Details

azps-7.1.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md
:warning:Warning
View (azps-7.1.0)
Details

azps-7.0.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md
:white_check_mark:Succeeded

azps-7.0.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md
:white_check_mark:Succeeded

azps-6.6.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: link-out-of-scope] File 'azps-6.6.0/Az.MonitoringSolutions/Get-AzMonitorLogAnalyticsSolution.md' referenced by link '../az.monitoringsolutions/get-azmonitorloganalyticssolution.md?view=azps-5.9.0' will not be built because it is not included in build scope.

azps-6.6.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: link-out-of-scope] File 'azps-6.6.0/Az.MonitoringSolutions/Get-AzMonitorLogAnalyticsSolution.md' referenced by link '../az.monitoringsolutions/get-azmonitorloganalyticssolution.md?view=azps-5.9.0' will not be built because it is not included in build scope.

azps-7.1.0/Az.OperationalInsights/Get-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: link-out-of-scope] File 'azps-7.1.0/Az.MonitoringSolutions/Get-AzMonitorLogAnalyticsSolution.md' referenced by link '../az.monitoringsolutions/get-azmonitorloganalyticssolution.md?view=azps-5.9.0' will not be built because it is not included in build scope.

azps-7.1.0/Az.OperationalInsights/Set-AzOperationalInsightsIntelligencePack.md

Line 0, Column 0: [Warning: link-out-of-scope] File 'azps-7.1.0/Az.MonitoringSolutions/Get-AzMonitorLogAnalyticsSolution.md' referenced by link '../az.monitoringsolutions/get-azmonitorloganalyticssolution.md?view=azps-5.9.0' will not be built because it is not included in build scope.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

We release new versions monthly. Please update the PR to include docs for version 7.2.0 and remove version 7.0.0. (Current versions).
This content is auto generated reference content. Please also update the source in the azure-powershell repo. (Future versions)

We release new versions monthly. Please update the PR to include docs for version 7.2.0 and remove version 7.0.0. (Current versions).
This content is auto generated reference content. Please also update the source in the azure-powershell repo. (Future versions)

@mikefrobbins We're working from a list provided in the User Story. The docs in the source repo aren't currently listed in the spreadsheet attached to the US. @dbradish-microsoft Please advise.
Thanks!

@mikefrobbins We're working from a list provided in the User Story. The docs in the source repo aren't currently listed in the spreadsheet attached to the US. @dbradish-microsoft Please advise.
Thanks!

@v-andreaco Any issue resolved in version 7.1.0 of the reference docs will resurface next month when 7.3.0 is released unless the source version is fixed. Also, all docs for version 7.1.0 will be deleted next month. This process occurs every month (adding a new version and removing an old one).

@mikefrobbins , lines 61 - 66.  The spreadsheet you looked at probably had a filter going in column I.
@ttorble, autogenerated reference content has to be changed in the source.  Making updates to any folder except for \docs-conceptual\ in this repo could be over-written should the version be regenerated.  I'm really not concerned about autogenerated reference content as fully qualified URLs might be required for the autogen to build (?).  I'm not sure.  I'll update my SELECT statement to omit autogenerated content in the future.  Please close this PR and make a note in the work item that Azure PowerShell (any folder except for "docs-conceptual") and Azure CLI reference content (any folder with "docs-ref-autogen" in the name) was skipped.


Running /update a second time on a fresh database results in one attempted update.

Run once:
> curl localhost:8080/update

Run again, and PutStates tries to write:
> curl localhost:8080/update
The preload list has 11360 entries.
- # of preloaded HSTS entries: 11101
- # to be added in this update: 1
- # to be removed this update: 0
[]string{"zzw.ca"}
Updating 1 entries... done.
Success. 1 domain states updated.

Note that this does not happen using an older version of the code at http://hstspreload-mvm.appspot.com/update:
The preload list has 11360 entries.
- # of preloaded HSTS entries: 11101
- # to be added in this update: 0
- # to be removed this update: 0
No updates.
Success. 0 domain states updated.

The root cause it a bug with the Datastore client library (or possibly Datastore itself): https://github.com/GoogleCloudPlatform/gcloud-golang/issues/259
It just happens to be that the number of preload entries with "mode": "force-https" is 11101, which is congruent to 1 (mod 300).
Thus, by 1/300 chance it looked like just the last entry was missing, but that turned out to be a red herring (although it cost me a lot of time).

Fixed in thttps://github.com/GoogleCloudPlatform/gcloud-golang/commit/47856689284450ce6d8a36bdfd9df5f31b4191a0

My bug writeup (originally sent to an internal mailing list, but it contains nothing sensitive):

I'm currently working on v2 of hstspreload.appspot.com, which has its own database to keep track of preload status. The app has a script called /update that fetches the preload list and compares it to the database. Anything domain is preloaded in the official list, but not the database, needs to be updated.
Aside-but-not-aside:
The preload list currently has 11101 HSTS entries (in addition to some HPKP domains), so I did a double-take the first time I tested my preload handling code.
I thought to myself: "Why are almost all the digits 1?" "Why does it look binary?" "Did I use the wrong formatting code?" But it turns out that no, there are actually 11101 entries when written in base 10. I got used to it, and it was actually kind of cute to see the number go by.
Anyhow, the last functional issue before deployment was a "minor" bug with the /update script.
In theory, if the real preload list doesn't change, /update should be an idempotent operation. All the real preloaded domains are marked as preloaded in the database the first time around, and the second time around /update will see that they don't need to be revised. But when I ran the script multiple times it seemed that the that the last entry in the list (zzw.ca) always got updated.
So I thought to myself "hmm, I must have an off-by-one error when I write the preloaded entries to the database"
And so I checked my code, but alas I didn't find an off-by-one error. zzw.ca was marked correctly for an update on every run.
So I thought to myself "hmm, there must be something else that is preventing the correct value from reaching the database"
And so I queried the database directly, but alas it showed zzw.ca as preloaded.
So I thought to myself "hmmm, I must have an off-by-one error when I read from the database"
And so I dumped the list of domains I read from the database.
AHA! zzw.ca was missing.
So I thought to myself "hmmm, I must only be getting back 11100 results"
So I printed the number of entries, but alas there were 11101 results – the right amount.
So I thought to myself "hmmm, are there any duplicate entries?"
So I sorted the list to get ready to find duplicates.
AHA! – the first entry (0.me.uk), appeared twice. However, it didn't appear twice in a row at the beginning. The results were returned as a nearly-sorted list, but it appeared at position #1 and position #301.
In addition, at the very end, zzw.ca was replaced by xbt.co. (I had noticed this before, but since I didn't ask for the results in sorted order I had just assumed that the "mostly sorted" result order was an artifact of the tech stack: indexing, map-reduce, hash maps, etc. I hadn't judged it to be a sufficiently useful clue to pursue earlier.)
So I thought to myself "hmmm, I wonder if there is something funky going on where xbt.co should be."
So I checked the list of domains I got back from the database
AHA! xbt.co was replaced by a domain even further back, which was in turned replaced by another one, and so on.
Turns out that every 300th result was shifted after the first one.

Result #301 was a copy of result #1 (0.me.uk)
Result #601 was the result that should have been at position #301
Result #901 was the result that should have been at position #601
...
Result #11101 was the result that should have been at position #10801

On Friday I tracked the bug down to the official google-golang library for interacting with Cloud Datastore. I created a minimized test case and also tried to find the fix. But I ran out of time trying to find the right fix, so I just filed a bug and emailed the cloud team. They confirmed the behaviour I was trying to track down: there was an iterator in Google's library that handled internal batches of size 300, and the first key of every new batch still pointed to the previous one.
The bug was fixed over the weekend, and my app works correctly without any changes. :-)
(But it still concerns me a bit that this bug existed in the first place. Has no one else used Google's official cloud libraries for Go to access more than 300 results from Datastore outside App Engine?)
Anyhow, remember that cute number of preload list entries, 11101? It happens that 11100 is divisible by 300, so result #11101 is the first (and only) value in the final batch. Thus, by a 1/300 chance, the very last result was "shifted off the end". The fact that it turned out to be the last result – rather than a different result somewhere in the last 300 – turned out to be a red herring that cost me a lot of time. :-(


Outdated bower repository

$mdDialog option 'skipHide: true' is not setted in the Dialog config object. This option allows the datetime picker dialog open above another dialog.
Another interesting config is 'clickOutsideToClose: true', this option allows the dialog is closed when clicked outside or when escape key is pressed.

This has been fixed in recent release.

Thanks dude!


Links vs Breadcrumbs

I was wondering how I can get back the old way of moving from chapter to chapter by using links vs using the breadcrumbs plugin?
I am not a big fan of the breadcrumbs navigation and it seems like any option i choose to download the scripture are missing the links page navigation.  So when I download the bible without breadcrumb, I have no way of navigating from chapter to chapter.
Can you help please help with this?
The solution to just go back to the older versions would not be good for me because of other issues like: 1. Each chapter repeats chapter one from each book. 2. The books with numbers don't work well. So this newer version fixes these two issues for me but leaves out the old links navigation that I actually enjoy.
Thank you sooo much for all your hard work. This is such a gift.
Thanks!

@newbonedayatatime
I just stumbled on this today and was having the same issue.  I think this is a bug in the latest script.  I'm not a coder, so I can't tell you why this works or the significance of the brackets, but this change works:
Change Line 188 in the bg2obs.sh file from:
if [[ ${breadcrumbs_yaml} -eq "true" ]]; then

to:
if ${breadcrumbs_yaml} -eq "true"; then

You should see the links show up along the top instead of just the three asterisks.
# Genesis 1

[[Genesis]] | [[Gen 2|Genesis 2 →]]
***

# Genesis 1 (World English Bible)

Hope this helps!

Thank you so much. It worked! Wow. the best! Thank you again.

I can also confirm that this fix works. Thank you.

Many thanks for the navigation fix!

Fixed in https://github.com/selfire1/BibleGateway-to-Obsidian/pull/27.