[athena] fix TypeError while delete messages from SQS

to: @jacknagz or @ryandeivert
cc: @airbnb/streamalert-maintainers
size: small
resolves #590
Background
We noticed there is Athena error due to TypeError while deleting messages from SQS. The root cause of TypeError is because of complicated list comprehensive logic when first deletion failed. The list comprehensive added extra list around pushed back messages.
Changes

Break down complicated list comprehensive to simpler ones.
Add mock class for SQS client and add unit test case to reproduce error.
Add a max_retries in backoff logic to make the code testable.

Testing

Rule testing

python manage.py lambda test --processor all
...
StreamAlertCLI [INFO]: (60/60) Successful Tests
StreamAlertCLI [INFO]: (93/93) Alert Tests Passed
StreamAlertCLI [INFO]: Completed

Unit testing

./tests/scripts/unit_tests.sh
...
Ran 530 tests in 8.466s

OK

Coverage increased (+0.07%) to 95.469% when pulling a2017a28759e8485971d16ad908ee32fd4865114 on fix_sqs_delete_type_error into 954b70b39a432beda4644c2095bb9c6df5586c75 on master.

@chunyong-lin FYI this error is still happening after these changes were deployed


Remove check for clientservicesport

Since Client Services are not mapped via Traefik we should be able to specify the port we want to use.

Will allow this one.
If we get traefik v2 we might put this back in as clientservices will go through traefik v2

Will allow this one.
If we get traefik v2 we might put this back in as clientservices will go through traefik v2


Paragraphs are not executed in an order

In my node, there are three paragraphs, ie, A(Running Shell script) -> B (Running Spark) -> C(Running Shell Script). I found that Sine B will take longer time than A and C, C starts to run when B is still running.
I want the paragraphs should run with the strict order, i.e., according to the dependency.

Thanks for the good suggestion.
We have moved to apache. New github repository is https://github.com/apache/incubator-zeppelin.
And please use https://issues.apache.org/jira/browse/ZEPPELIN to create an issue.


Lists button now in More submenu, cannot be relocated to main menu with current options

The Lists button has been moved from the main sidebar to the More submenu, and as I use lists frequently, having it in the main menu is more convenient for me than having to open it from a second menu.

I have found that is occurs when the browser window becomes less than around 980 pixels in height, which is often the case in 1080p monitors. My main driver is a 1440p monitor so I do not observe it there.

Yes, if I zoom out to 80% it reappears.


Evaluate Pretrained Models - "No module named 'hulc.datasets'"

Hi,
I am trying to evaluate the provided pretrained models. I followed the hulc install instructions, but initially ran into this issue:
Traceback (most recent call last):   File "hulc/evaluation/evaluate_policy.py", line 10, in <module>     from calvin_agent.evaluation.utils import get_default_model_and_env ModuleNotFoundError: No module named 'calvin_agent'
To resolve this I installed the calvin repo.
However, I am now getting the following error:
ImportError: Encountered error: "No module named 'hulc.datasets'" when loading module 'hulc.datasets.hulc_data_module.HulcDataModule'
It seems like the hulc/datasets folder no longer exists in this repository?
Any help is appreciated, thanks!

I managed to get it working by rolling back to a previous commit:
git checkout 0bbc52
Then:
python hulc/evaluation/evaluate_policy.py --dataset_path $HULC_ROOT/dataset/calvin_debug_dataset --train_folder $HULC_ROOT/checkpoints/HULC_D_D --checkpoint $HULC_ROOT/checkpoints/HULC_D_D/saved_models/HULC_D_D.ckpt --debug

This was caused by us not updating the model weights after the last refactoring commit, we apologize for that.
We uploaded the new HULC_D_D checkpoint, so now it should also work on the newest commit!

[ ] add calvin_agent to requirements

evaluate_policy.py works fine now with the new HULC_D_D checkpoint, thanks for the help!

Would it be possible to also upload the updated HULC_ABCD_D checkpoint?
I need the pretrained model to perform as well as possible, and I believe HULC_ABCD_D performs better than HULC_D_D (according to the paper).

是否也可以上传更新的 HULC_ABCD_D 检查点？
我需要预训练模型尽可能地表现出色，而且我相信 HULC_ABCD_D 的表现优于 HULC_D_D（根据论文）。

Hi there! I had the same issue while testing the pre-trained model HULC_ABC_D. Has this problem been resolved yet?

Hi there! I had the same issue while testing the pre-trained model HULC_ABC_D. Has this problem been resolved yet?


add default http attributes to span

Codecov Report

Merging #18 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #18   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           3      3
  Lines          12     12
=====================================
  Hits           12     12

Impacted Files
Coverage Δ

lib/opencensus/plug/trace.ex
100% <ø> (ø)
:arrow_up:

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 8eba092...5dc9c1c. Read the comment docs.


[DS] Generate repositories partitions from HDFS blocks

Repositories will be in a specific folder. Example:
repositories/
├── repo1/
│   └── ...
├── repo2/
│   └── ...
└── repo3/
    └── ...

We should get all the files from a repository, get the blocks information, and aggregate repositories by datanodes with more block of each repository.
With this information we need to create a new class called RepositoryPartition that extends the trait org.apache.spark.Partition, that will include a list of repository folders.
This partitions will be sent to each relation to create RDD partitions correctly, depending of the locality.

not needed anymore.


Stack of general questions

What is the "accuracy" provided during MaskRCNN training process?
Could I change the metric during training process?
Can I make some custom features in training process? Like pin_memory in data loaders or use more than one validation sample?

May you can write a EvalHook in mmdet/core/evaluation

@Czm369
Is there a way to write these changes not in the dependencies library? If I change something in dependencies library these changes could be pushed somewhere and used in another project only manually, this is the bad way

@Czm369
And do you know the answer to the first question? I just wonder what the "accuracy" used for segmentation and cannot find an answer in the code


http header

This PR will correct the example given in #268 but the problem also occurs in
app/http/http-post/http-post.services.ts
app/ui-category/activity-indicator/setting-busy-http-request/setting-busy-http-request.component.ts


additional_property macro should support external types and arrays

Thanks a lot for the amazing library!
Currently additional_property macro doesn't support complex (schema-based) types and arrays.
So the following would not work:
defmodule MyAppWeb.Schemas.UUID do
  use JungleSpec

  @title "UUID"

  open_api_type @title, :string,
    nullable: true,
    format: :uuid,
    pattern: ~r/[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}/,
    example: "193202fc-ab55-4824-8ec8-5bef1201d9eb"
end

### the following will produce errors

defmodule MyAppWeb.Schemas.MapWithExternalType do
  use JungleSpec

  @title "MapWithExternalType",
  @description: "Map With External Type"

  alias MyAppWeb.Schemas.UUID

  open_api_object @title, description: @description, struct?: false do
    additional_properties UUID
  end

end

defmodule MyAppWeb.Schemas.MapWithExternalTypeList do
  use JungleSpec

  @title "MapWithExternalTypeList",
  @description: "Map With External Type List"

  alias MyAppWeb.Schemas.UUID

  open_api_object @title, description: @description, struct?: false do
    additional_properties {:array, UUID}
  end

end

Thanks for mentioning that! I'm starting to work on that issue

Linked PR should hopefully fix the issue, but tell me if there is still something wrong


Make scheduled executor service tasks robust against exceptions (#24575)

Fixes #24575
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
n/a Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[x] Provide unit tests (under <subproject>/src/test) to verify logic
n/a Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass sanity check: ./gradlew sanityCheck
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation

Current dependencies on/for this PR:

master

PR #2   👈

This comment was auto-generated by Graphite.


System-tests: Create external clients executor

Create clients executor for external client wrappers from messagingQE (cli-rhea, cli-proton-python, cli-java, cli-netlite)
https://github.com/rh-messaging/cli-rhea
https://github.com/rh-messaging/cli-netlite
https://github.com/rh-messaging/cli-java
https://github.com/rh-messaging/cli-proton-python

https://github.com/EnMasseProject/enmasse/tree/dk_external_client_execution

https://github.com/EnMasseProject/enmasse/commit/33699e99155f7356216dcd632d3f73c6310c019a


Add API endpoints to SentEmailViewerPlug

Added two endpoints to the SentEmailViewerPlug to list and reset the sent emails programatically. These are useful for integration test runners, so it's possible to write tests that can check and respond to emailed content.

@tomtaylor Interesting! Can you share an example of how you are thinking to use this? Is this for integration testing email sending? Would it be possible to achieve this using helpers from Bamboo.Test?

That’s right. I use Cypress for our E2E tests, which can only interact with my Phoenix app over HTTP routes. I expose a couple of test only controller actions for setting up database scenarios, but had no good way of testing journeys with an email step in the middle. With this I can write a function that tell Cypress to reach into the Bamboo sent emails API to assert an email was received.
This isn’t happening in process in Elixir, so the Bamboo.Test helpers don’t help here. Does that make sense?

Ah, okay, that makes sense. What would you think about making these API endpoints in a separate plug that people could then expose in their apps only if they want to? I feel like the use case for these might be different enough to warrant it being separate, and many people would not need these exposed, although I'm not sure and would love to hear your thoughts. In any case it'd be great to have some documentation on here about what these are for. Thanks for your work on this!

Thanks @maymillerricci. Happy to do that if you feel it's clearer - I think it's likely that they wouldn't both be used at the same time, so that makes sense. And I'll add some documentation at the same time.

Thanks @tomtaylor! I can see arguments for both sides, but I do think having them separate would be slightly clearer, and people can decide which endpoints they want to expose. I also left you some minor comments about the tests. Thanks for your work on this!

@maymillerricci just pushed a replacement commit with the final tweaks!

Thanks!


Type hole with compatibility between optional parameters/extra parameters

TypeScript Version:  Whatever runs https://www.typescriptlang.org/play/
Code
const x = (a: number = 1): number => a;
const y: () => number = x;
// TypeScript error: "Supplied parameters do not match signature of call target."
// OK
y('x').toFixed();

const z: (a: string) => number = y;
// No TypeScript error
// Runtime error: Uncaught TypeError: z(...).toFixed is not a function
z('x').toFixed();

Expected behavior:
TypeScript error that either (a?: number) => number is incompatible with () => number, or that () => number is incompatible with (a: string) => number. I'm not sure which one is most correct, but permitting both of these things in combination is definitely unsound.
Actual behavior:
No TypeScript error on the const z: (a: string) => number = y; line nor the z('x').toFixed(); line., but an error when the code runs.

You've identified the problem and why there isn't a solution -- preventing either assignment is problematic. TypeScript does not guarantee soundness and this is one of the holes.
Even Flow, which generally tries to be more sound at the expense of inconvenience, allows this (update: I see you just logged this on their tracker as well).

If you somehow find yourself in this situation and need to track down how the wrong function got assigned in, you can declare out the optional parameter in the nullary case assuming you can figure out which call signature originated the problem in the first place:
// Error
const y: (_?: "must be missing!") => number = x;

@RyanCavanaugh Yeah Flow has the same problem (https://github.com/facebook/flow/issues/3049), but I found it more surprising considering they have more of an objective of soundness than TS does.
If this is just another baked-in gotcha then fair enough, I'll add it to the list.

@RyanCavanaugh I posted a solution against the Flow issue which you may be interested in, which I'll repeat here.
Basically you store against a function signature whether or not extra parameter slots should accept anything {} (mixed in Flow) or only undefined (void in Flow), similar to a rest parameter.
For function literals, the inferred type has any extra parameters set to accept anything, since the function ignores those parameters. This way you can pass callbacks or implement interfaces without specifying all the necessary parameters, eg element.onClick(() => { alert('clicked'); }) would work even though the callback can accept an event.
For function types written directly, the type has any extra parameters set to accept only undefined. This way the same function type with an extra optional parameter is correctly considered compatible, since undefined is a valid input for an optional parameter. Any attempt to call a function with more than the specified parameters is an error (as it is currently) (unless perhaps undefined is being passed).
The only restriction is that a written function type is not compatible with the same written function type with an extra parameter, because the shorter function type could be masking a function type with additional optional parameters for which the only known acceptable input is undefined.
Example:
const x = (a: number = 1): number => a;
// x: (number|undefined, {}...) => number

const y: () => number = x;
// y: (undefined...) => number
// Assignment OK, undefined is compatible with both number|undefined and {}

const z: (a: string) => number = y;
// z: (string, undefined...) => number
// ^ Error on assignment, string is not compatible with undefined

const w = (): number => 1;
// w: ({}...) => number

const v: (a: string) => number = w;
// v: (string, undefined...) => number
// ^ Assignment OK, string and undefined are both compatible with {}

Passing extra arguments should always be allowed. This is just the nature of JS.
However a much easier fix, that catches the problem at its root is disallowing
const x = (a: number = 1): number => a;
const y: () => number = x;

If (x: T?) => U is not assignable to () => U the workaround is easy, just wrap it in a () => f(). There is no simple and generic workaround for the above suggestion. Also optional aliasing should be much easier to detected in the checker. Maybe all we need is just --noOptionalAliasing.

@gcnew I think being able to override class methods and add extra optional parameters is fairly reasonable and expected behaviour, which means (x: T?) => U is assignable to () => U and that calling a function/method with extra arguments must be disallowed. My suggestion aims to maintain that while also being sound.

I see where you are coming from. Unfortunately overloads and overrides are one and the same thing in JavaScript. This makes your proposal better for class hierarchies. On the other hand JavaScript is traditionally used in functional style. As such I'm not in favour of hindering virtually every callback argument.
I still think that conditionally outlawing unsafe optional param assignments is the better alternative. If we go with your proposal then undefined... should always be used for the extra parameters as inferring {}... needs the source file and creates a discrepancy with declaration file functions. The function literal rule is also kind of artificial/confusing.

Unfortunately overloads and overrides are one and the same thing in JavaScript.

I don't see what overloading has to do with anything.

As such I'm not in favour of hindering virtually every callback argument.

Can you give me an example? You can still omit parameters when passing callbacks.

If we go with your proposal then undefined... should always be used for the extra parameters as inferring {}... needs the source file and creates a discrepancy with declaration file functions.

The only purpose {}... serves in an inferred function signature is to be able to omit unused parameters when passing callbacks or overriding/implementing methods, i.e. it only has a purpose where an actual function definition is concerned. When it comes to type definitions and the interfaces between modules, this purpose doesn't apply and undefined... is correct.

The function literal rule is also kind of artificial/confusing.

It's just capturing the knowledge that extra parameters will be ignored by the function and they will therefore accept {}.

I think being able to override class methods and add extra optional parameters is fairly reasonable and expected behaviour

I don't think so. The runtime behaviour / expectations are different. You can't safely use such a function in all contexts the original can be used, precisely because JavaScript functions can be called with extra parameters by definition. It is also not supported in languages such as C# because the type is different although compatible at times.

I don't see what overloading has to do with anything.

Event if we agreed on the above, then comes the problem that you should be able to add overloads in subclasses. Overloads in JS are basically just one function that handles all the cases. This way it clashes with overriding, because banning defaulting overrides has the side effect of banning overloads as well.

Can you give me an example? You can still omit parameters when passing callbacks.

Sure - every named function.
const const42 = () => 42;
[1, 2, 3].reduce(const42, 0)

Now, you'd say that the inferred signature for const42 should be (_: {}...) => number. This might even be the case, but if we had it in a separate module, then the only thing we are left with is its user provided signature which is () => number. If we expand on that it should turn into (_: undefined...) => number and it will no longer be applicable as a callback in the above case. This makes it a no-go for me.
One remedy is declaration files / module interfaces to include extra param information, but I don't see this happening. Also if a user provided signature is present, it should not be silently expanded, but rather taken as is. This makes adding extra: {}... to functions inapplicable and without it many valid cases will be broken.
With the current state of affairs I don't see how the situation can be improved on, without sacrificing valid expressiveness power. As both approaches have their respective flaws, I think the best way forward is adding linter rules for both and allowing programmers to choose their poison.

You can't safely use such a function in all contexts the original can be used, precisely because JavaScript functions can be called with extra parameters by definition.

Of course JavaScript allows a TypeScript function's signature to be disobeyed. JavaScript lets you pass number into a TypeScript function expecting a HTMLElement "by definition".  Of course not.
TypeScript also statically ensures that a function is called without extra parameters and that their runtime value is therefore undefined (apart from the loophole that is the subject of this issue). You can therefore safely add extra optional parameters, because undefined is compatible. The fact that untyped JavaScript allows TypeScript's rules to be broken at runtime is irrelevant.

Overloads in JS are basically just one function that handles all the cases. This way it clashes with overriding, because banning defaulting overrides has the side effect of banning overloads as well.

I don't know what you mean by "defaulting overrides". You can certainly use overriding, extra optional parameters, and overloading all at the same time, right now, in a type safe way, and my suggestion wouldn't change that.
class Foo {
    foo(x: string): void { }
}

class Blah implements Foo {
    // Foo.foo just has to be compatible with at least one of these
    foo(x: string, y?: number): void;
    foo(x: number): void;
    foo(x: Promise<number>): void;

    foo(x: string | Promise<number> | number, y: number = 1) {
        // Test x and y to determine what overload was used
    }
}

let b = new Blah();
b.foo('x');//ok
b.foo(1);//ok
b.foo(Promise.resolve(1));//ok
b.foo(Promise.resolve(1), 1);// not ok, doesn't match any signatures

Now, you'd say that the inferred signature for const42 should be (_: {}...) => number. This might even be the case, but if we had it in a separate module, then the only thing we are left with is its user provided signature which is () => number. If we expand on that it should turn into (_: undefined...) => number and it will no longer be applicable as a callback in the above case.

You could pass () => const42() as the callback instead. If the callback needs parameters threaded through they would need to be mentioned explicitly though, which is an extra few chars. ("There is no simple and generic workaround" as you said earlier.)
Having the effective ({}...) => number signature maintained across modules boundaries and through declaration files would require some syntax, but I have no problem with that. Something simple like an optional , ?), , ?..), , any...) or a keyword like allowextra or anyextra at the end of the function signature would suffice. (You would only need this when expressing the type of a function that you know ignores extra parameters. It would be implied automatically for function definitions, so would only likely show up in generated .d.ts files IMO.)

I truly want to disambiguate the matter, maybe I'm not expressing myself well.
I'm not bringing in the argument that you can violate type expectations via JS. While there is nothing stopping you from doing it, programmers don't do it in practice because even if the type is not explicit it is still there and not abiding to it results in a runtime error.
On the "statically ensures" part is where see different approaches. While it is true that you are not allowed to pass extra arguments on purpose it is often implicitly the case with callbacks. Now there are two ways forward (as you've already stated in the description of the issue).
I think the approach you propose is hardly an ideal one. Why?

it breaks local inference
has non-uniform behaviour with local/module functions
requires extra care or syntax

These reasons are not all true at the same time, rather they are possible consequences of the tradeoffs involved in an actual implementation.
I see the issue from the other side. From my point of view a (a?: number) => number function should  not be assignable to a () => number reference. This is because it is a very standard practice to use functions as callbacks and maybe pass extra arguments to them. If we look at this assignability conundrum from a logical perspective and ask ourselves is it correct to allow it, for me the answer is  sometimes. On the one hand yes, it will work sometimes, because defaulting happens at runtime in the presence of undefined (either explicit or because of a missing argument). On the other hand, the types are actually quite different and it is impossible to say which of the two it is at compile time. The difference is visible at runtime in the presence of non-undefined extra arguments.
My proposal (which is not actually mine, you've mentioned it in the description) embraces the idea that extra arguments will be passed and warns you to use a safer pattern in the case of defaulting. The negatives are that overloading and overriding will be broken. I can live with that as I don't use classes and even less so class hierarchies. Having said that, I do agree it's not acceptable for everyone just as it's not acceptable for me to add boilerplate to my perfectly valid function signatures and usage.
In the end of the day it all boils down to: either functions with lower arity are not assignable to references with higher (your proposal) or functions with extra defaulted parameters are not assignable to references without them. I support the second option, because I admit calling a function with more arguments and it also rules out the uncertainty introduced by runtime defaulting.

Discussed for a while at the backlog slog. Some more detailed notes

This should be accomplishable with just a single bit on the function type that indicates whether or not there might be additional parameters beyond the declared ones.

This would be false for declared functions and consts initialized by a function expression
true for anything else.

Error to assign to something with more parameters when that bit is set
We're not sure if this is a massive breaking change or not?

So if anyone wants to see this happen, we'll need a PR we can run against our internal code suite to see what the real-world impact is and assess value vs breakage.

Just thinking out loud, something that's going to really problematic is class methods. The "could there be extra parameters" bit would have to be set for class methods, because a derived class could declare new optional parameters, but it's entirely reasonable to write code like this and not expect an error:
class Base {
  bar = (n: number) => { console.log(n); }
  foo() {
    // Error, but seems ok...
    [1, 2, 3].forEach(this.bar);
  }

  // Maybe you have to write this instead?? Super annoying?
  bar = (n: number, _1: may_not_use, _2: may_not_use) => { console.log(n); }
}

// Theoretically-possible problem case
// that people will complain that they didn't do and shouldn't be bothered about
class Derived extends Base {
  bar = (n: number, s?: string) => { console.log(n); }
}

Is this related to this problem? I've noticed I can't create a function overload that makes a parameter optional by way of omission in the parameter list. Normally making the trailing parameters optional is a good thing for concise code, but if the overloads have different return types, making a trailing parameter optional just to resolve compatibility seems kind of hacky.
export type CurriedHasFn<K, V> = (map: HashMap<K, V>) => boolean;

export function has<K, V>(key: K): CurriedHasFn<K, V>;
export function has<K, V>(key: K, map?: HashMap<K, V>): boolean; // `map` should not be optional here
export function has<K, V>(key: K, map?: HashMapImpl<K, V>): boolean|CurriedHasFn<K, V> {
  // ...
}

In the above snippet, I'm forced to make the second parameter of the the second overload optional, otherwise I can't get it to compile without compatibility issues.

@axefrog I'm confused by your example - in the first block, why is the second overload specifying map optional? It makes a call to has(key) potentially ambiguous. The second block makes more sense, though  in general you should put longer overloads first, not second. Without an isolated repro (lots of undefined identifiers here) and a more clear explanation of what you would expect a given call to do, it's hard to say. Best asked on Stack Overflow as this example is not related to the subject at hand.

@RyanCavanaugh Because I get red squigglies otherwise. Evidence below:

I suspect it is because the type of the map in the overload declaration is HasMap (interface) and the implementation expects HashMapImpl (implementation). This means that the overload may be called with a different HashMap implementation which renders it incompatible. Just use the same shape in both places.

This issue seems to have fixed.

This doesn't seem to be an issue in practice, and our appetite for breaking changes diminishes every day.

FWIW just as a data point, this unsoundness has been complicit in a production outage at Google.
Authors expected type safety in a refactoring that changed the type of an optional argument (e.g. from T to U). The compiler didn't catch a breakage in a code path going from (a: string, b?: T)=>void to (a: string)=>void to (a: string, b?: U)=>void.
It's a single data point, so not necessarily something that should change the judgement on this particular issue. I just thought I'd leave this here for future reference, in case it comes up again.


Bump package versions

Currently some packages are outdated. We could update manually or try to update with some kind of bot, like renovate or dependabot.
This is the list

[ ] @semantic-release/git
[x] #171
[x] #172
[x] #167
[ ] #173
[x] #168
[x] #166
[ ] semantic-release
[x] #177
[x] #193
[x] #164
[x] #175
[ ] #179

Can we also bump Faker package please.
<EMAIL_ADDRESS>faker "4.1.0" ->     faker "5.5.3"

will<EMAIL_ADDRESS>be published soon? I want to use faker v5
$ npm info typeorm-seeding version
1.6.1

New version cannot be released because of #153.
There is a workaround installing faker as a dependency and using it like
import * as faker from 'faker' // Use this instead of the other one
import { define } from 'typeorm-seeding'
import { User } from '../entities'

define(User, () => { ... })

oh of course. I felt dumb. Thanks

I know that is not the ideal workaround.
If NPM token is not created when the next version will be ready, I will deploy it myself.

Closing this, no versions could be deployed


Add keyboard navigation for search

There is currently no keyboard navigation for the search field and search view.
There are some keyboard combinations that are well established and are expected by many users.
Going back & forward
alt + ←
This is not only valid in the context of search, but also every other area of the app that has back buttons. (Forward i haven't seen yet).
Focus search field
ctrl+f is the best established combo, especially on GNOME.
closing search view / unfocus search field
esc or pressing ctrl+f again.
moving to search results
It would also be nice if the next logical item when pressing tab, is the first item in the results list, i haven't checked this, but i think it makes sense. :-)

In addition to alt+←, spot should also support mouse button 4 as back button (and mouse button 5 as forward, if that gets implemented). Most web browsers have this, so I'm used to using my mouse instead of alt+←

In addition of being able to use mouse button 4 as back button as mentioned above it would be great if the space bar could be used to pause the currently playing track. This is the default in many music / video players (including spotify).

In addition of being able to use mouse button 4 as back button as mentioned above it would be great if the space bar could be used to pause the currently playing track. This is the default in many music / video players (including spotify).

Already a thing, but it only works on dev branch? I wonder if that has something to do with type-to-search eating events

Right, I've got some cleanup to do regarding type to search (well, I'll remove it fully to be clear :D ) but indeed it would sometimes eat up keyboard events!
Spacebar to toggle playback is there too, but sometimes a widget will steal focus and space will just send the activate signal to it. I'm probably not implementing my shortcuts properly (or maybe it'll be sorted out once we're rid of type-to-search)

It seems that in 0.3.0 type-to-search everywhere has disappeared, which might be intentional. More importantly, though, since Ctrl+f isn't bound yet, you now manually need to click the search icon in the header bar every time (?).
Related to this, there also appears to be a slight UX bug where clicking the search icon brings you to the search screen asking you to "Start typing to search", but focus isn't put in the search field in the header bar, so typing doesn't actually do anything until you manually give it focus.

I tried working on this at some point but I somehow can't understand how Gtk handles focusing, I have to dig into it.

@xou816 In Vala you can set the focus to a widget by calling widget.grab_focus(). I don't know how it works in Rust, but I assume it's something similar

It definitely should be similar, but I had ran into some weird issue, was probably doing something wrong, I'll give it another proper shot!


Render rockets

For this milestone I:

Rendered all rockets in the UI
Added style to rockets' info
Added functional component to display a button to book a rocket
Added logic to update reserve value in the store

Thanks 😄


Correct mismatched variable names.

Correct mismatched variable names.

Codecov Report

Merging #127 (8f84c21) into dev (db0b68c) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##              dev     #127   +/-   ##
=======================================
  Coverage   48.23%   48.23%
=======================================
  Files          55       55
  Lines        5759     5759
=======================================
  Hits         2778     2778
  Misses       2738     2738
  Partials      243      243

Impacted Files
Coverage Δ

pkg/cond/sharding_algorithm.go
18.24% <0.00%> (ø)

Continue to review full report at Codecov.

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

LGTM


Callbacks?

I don't know where to ask this, please point me to a better location if you are offended having it here.
I have been trying to introduce myself to binding my own functions into lua.  I have a (from what I can tell) very complicated end-goal read on StackOverflow if interested.
I need to be able to take a callback from lua so I can do asynchronous things before passing back into lua with a result.
// works great
lua.set_function("print", [](const char *  y){ std::cout << y << std::endl; });

// what I need and don't know how to do...
lua.set_function("getUser", [](int id, luaFncPointer cb)
{
/* ... */
// async operation on database, io, etc.
/* ... */
 });

-- user written lua script
getUser(1, function(err, user)
   if err then
      print('Error', err)
   else
      print('Found user with id', user.id)
   end
end)

Do you have some examples I could look at or suggestions on what to do?

You can replace luaFncPointer cb with one of 2 types: std::function<ReturnType(Arguments...)> OR sol::function. sol::function is the most flexible (can pass it different number of args and stuff, while std::function has a fixed signature).
Code would look like...
lua.set_function("print", [](const char *  y){ std::cout << y << std::endl; });
lua.set_function("getUser", [](int id, sol::function cb)
{
/* ... */
cb( 24, some_ptr, ... ); // whatever you like
/* ... */
 });

Sorry about not having a place this is clear: I gotta pump up the docs to be a LOT more specific with this stuff so that people get the proper guidance.

This is great!  But how do I return null or empty to the first argument of the lua callback?
lua.set_function("getUser", [](int id, sol::function cb)
{
    cb(NULL, "THE USER");
});

NULL is a macro from the C standard that, in C++, usually resolves to 0. This will push an integer, which isn't what you want: try doing cb( sol::nil, "THE USER" ) or cb( nullptr, "THE USER" )

Thank you!

Will sol::function take ellipsis?

No, it won't take ellipses, but you can feed it as many arguments as you like.

@ThePhD Thanks for all your help.  I'm really enjoying your library.  I have one more big question for you...
I am trying to call a sol::function callback from an asynchronous thread.  My lua.set_function("getUser" [&](int id, sol::function gotUserDataCb {...}) has to asynchronously ask nodejs for some information, and in that response (using uv_queue_work, uv_after_work_cb, etc) I need to execute gotUserDataCb.  My issue is that causes a segmentation fault.  I think this is because the sol::state goes out of scope long before getUser tries to respond.
Do you have any tips here?  Am I on the correct track, should I try to find a way to keep the sol::state from going out of scope (make it a pointer and manually delete it)?

You need to shift the lifetime of the sol::state you set that function on. Move its scope up your application's stack a bit, so it will last. Make it a shared_ptr if you really need to keep it alive. There's no reason to manually track the lieftime with those kind of tools.

I took your suggestion and made it a shared pointer (moving the sol::state up in scope can't be done in my case).  I am now getting an exception thrown from sol->script:

terminate called after throwing an instance of 'sol::error'
what():  lua: error: attempt to call a nil value

That could happen from a number of things. I have no idea what would be the problem, and I'm not sure I can reason about how your entire application stack sets up things.

Fair enough.  I think the problem is that the actually sol::function gotUserDataCb is being called after lua->script is done executing.  Is there a lua lock offered by sol?  I have head mention of locking and unlocking in other discussions about lua hooks.

@ThePhD hey, I just wanted to say thank you.  I got where I needed to go with the help of your library and advice.  To solve the last problem I was having I had to implement lua_lock and lua_unlock in a custom lua build and bind that custom built lua library and header files into my program along with sol2.  I now have a fully functioning bridge between nodejs and lua.

Nice! If you think there's a nice way to do lua_lock that can be added to sol2, feel free to open up another Bikeshed issue.

I appreciate your willingness but I doubt there is a way to do this.  The lua team seems adamant that tread locking be a custom modification and build.  The locking and unlocking functions are not even public, they expect you to modify the lua internal lua_state struct and interact with your modification.  So, I really don't think there is a way to wrap customization like that.
If I think of something while I am cleaning up my experiment for prime-time, I will let you know.


Support the autoIndexId option for capped collections

What should be done?

https://www.mongodb.com/docs/manual/reference/command/create/#syntax

The autoIndexId option prevents the _id index from being created automatically. When used with non-capped collections the command returns a soon-to-be deprecated note. The option is also not allowed for collections that can be replicated, i.e. created on a DB other than local.

I wonder if we need to implement that at all and why. Does something require it?

@AlekSi see test that requires it here.


Search Bar Getting Cut Off

Hello! I'm loving this extension so far, but noticed that for me the "Search Twitter" bar gets cut off when I click on it. I use Google Chrome, and my laptop screen resolution is 1366 x 768. I use the second smallest text size.

Hey @hepatocyte! Thanks for catching – I added z-index: 1 to the search bar https://github.com/thomaswang/minimal-twitter/commit/98af43ba4a8583e665351157a2e1f47788014484, not a perfect solution because there's still an overlap but don't want to change too much.


Sometimes idracs not getting added in the add service of the ConfigUI

Sometimes idracs not getting added in the add service of the ConfigUI. Seen with both addService and add CSV

Hi @SailM23 can you confirm this is fixed or no longer a problem for you?

didnt really verify as i moved out of the iDRAC org, closing it.


 Can you please add this in next release.

This indeed. I'd like to be able to have a different vibration on an invalid scan (eg the QR may be valid to scan, but is not known in my system). If I could toggle the vibration off here, then it would be not an issue.

Changing this place to 1520 can change the intensity of the vibration

Vibration is enabled by default in 2.0.0, but can be disabled by passing shouldVibrateOnSuccess: false into the initializer.


Try to fix some obvious bugs of the library system

Follow-up #212

Index: cli/src/main/java/org/aya/cli/library/LibraryCompiler.java
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/cli/src/main/java/org/aya/cli/library/LibraryCompiler.java b/cli/src/main/java/org/aya/cli/library/LibraryCompiler.java
--- a/cli/src/main/java/org/aya/cli/library/LibraryCompiler.java	(revision 4a2b5ae649adbc3830e726b8ae80ad1e60138353)
+++ b/cli/src/main/java/org/aya/cli/library/LibraryCompiler.java	(date<PHONE_NUMBER>069)
@@ -155,8 +155,8 @@

     var order = changed.topologicalOrder().view()
       .flatMap(Function.identity())
-      .toImmutableLinkedSeq()
-      .reversed();
+      .reversed()
+      .toImmutableSeq();
     // ^ top order generated from usage graph should be reversed
     // Only here we generate top order from usage graph just for efficiency
     // (transposing a graph is slower than reversing a linked list).

Since we've fixed some very important bugs, I hereby propose these changes to the sacred branch above all:
bors r+


Reducing "Remote Desktop" Window cause client to briefly disconnect

When viewing a client's remote desktop, reducing the window (by pressing the "-" button), cause the client to disconnect.
Steps to reproduce the behavior:

Go to a connected client "Remote Desktop"
Click on 'Start'
Click on minimize button "-"
Client is disconnected

Expected behavior
The remote desktop should keep going when the window is minized and the client should not be disconnected.
Server OS: Windows 10
Client OS: Windows 10
Server installed .NET Framework version: 4.8.03752
Client installed .NET Framework version: 4.8.04084
Quasar Version: 1.4.0
Build configuration: master

I'm sorry I had to do something today but I'll make sure to respond in a couple hours or if I go to sleep when I wake up, sorry but it's 3 am right now.

I need some info first to recreate the issue perfectly
What version of windows are you using? (May be a new update bugging stuff out)
What Quasar Server and Client version are you using? (Maybe you are using an old version?)
Does this happen rarely or a lot?
Are you using open source builds or release builds?

I already provided those informations in the original post, I build Quasar myself based on the latest master commit.

I know that is why I deleted the comment, I forgot that you need to specify those.
But anyways, here's what I found:
I'm looking into it and I noticed quasar closes the connection when the async receiver gets an error.
Could maybe happen due to the client sending incorrect data that causes an error to happen, Still looking into it

Update:
My 3 main reasons for it happening are
Client sending incorrect data that can't be parsed so server drops connection
Server sending unsafe data that drops the connection
The amount of data sent is over the 5 megabyte limit MaxXor put in place.

@dogo99 It was much simpler, the local window size was set to (0,0) when minimized.
@azsde Thanks for the report. It's fixed in https://github.com/quasar/Quasar/commit/4c4cde446d1d39d917bf2459916c3aacf89579fd


Update tea.yaml

This is spam, please review this for more context https://github.com/TryGhost/Ghost/pull/19743


Data Request to add York Region Address Point, Building Footprint, and possibly Imagery

What kind of data are you inquiring about?
Addresses, Buildings, and Imagery
Data License
York Region Open Data License
This license was recently deemed compatible by the License Working Group. https://osmfoundation.org/wiki/OGL_Canada_and_local_variants
Background / where to download this data

Address points: https://insights-york.opendata.arcgis.com/datasets/588a00fa0451426386ca2f6195555601_0/explore
Building footprints: https://insights-york.opendata.arcgis.com/datasets/1142c5a1212a47d48ad5e57ac296399d_0/explore
Imagery: https://insights-york.opendata.arcgis.com/search?q=imagery&type=Feature%2520Service

With regards to the Canadian addresses in the Address Points, here’s how I’d map them:

OSM key
Address Point attribute

addr:housenumber
ADDRESS_NUMBER

addr:street
FULL_STREET_NAME

addr:district
MAIL_COMMUNITY_NAME*¹

addr:city*²
MUNICIPALITY

addr:province
(same for all addresses, it’s “Ontario”)

addr:postcode
MAIL_POSTAL_CODE*³

*¹ If it’s “Thornhill,” include it. Thornhill is a district that overlaps parts of the cities of Vaughan and Markham. addr:city is included because officially they are in those cities — they receive public services, pay taxes, and vote as residents of those cities. addr:district is included because if you want to mail something to an address in Thornhill, you write “Thornhill” in place of the city. For other MAIL_COMMUNITY_NAME values I’d have to do more research with Canada Post to see if they should be included. If addr:district if it matches addr:city, addr:district is redundant and should be omitted.
*² York Region is divided into several towns and cities. addr:city is used in both types of municipalities, and the OSM wiki suggests this is a correct usage.
*³ Not all addresses have postal codes, for example, parks.

Background / where to download this data

Building footprints: https://insights-york.opendata.arcgis.com/datasets/1142c5a1212a47d48ad5e57ac296399d_0/explore
Imagery: https://insights-york.opendata.arcgis.com/search?q=imagery&type=Feature%2520Service

Adding the background images to various editors would be something for https://github.com/osmlab/editor-layer-index and the corresponding JOSM index. The editor layer index is used here in Rapid and in iD.
You can add aerial imagery but also other categories of data (if they are really useful for a wide range of mappers).


Not Working With Existing Worlds!

I am using the dev build from the jenkins. The ONLY problem I have is that if you teleport to a world you created in 1.1 it DOES NOT take you there, it just moves you on the default world. I think this is because of the new anvil format because it works fine with creating new worlds. I installed it simply adding the new jar and deleting the old one. I did NOT delete the old FOLDER. Anybody know why?

fixed. had to manually convert worlds


Feature Request: more output options

Hi,
I'd be interested in using diagram but it's a little tricky right now.
My workflow is markdown to html (just pandoc and a makefile, not quarto), so diagram doesn't really work unless one or both of embed-resources and extract-media options are active.
But those aren't good options for me - there's plenty of other things that I link to in a given document, but nothing else that I'd want embedded or extracted.
Rather, what I'd like is to be able to configure diagram to output its images to some path and then link to that. (I got halfway there by setting the cache directory, but then tripped up on the hashes being different.)
If this is out of scope for the project because it's not a use case that makes sense for other output formats, fair enough.

Apologies for the late reply, my open source work had to lay dormant for a while.
Is this still something that you need, or did you find a workaround?

Hey, thanks for responding, all good!
I think I just didn't do anything with embedded diagrams.
My particular use case is probably going to change anyway (shifting from plain pandoc + makefile to something Jekyll based) so I definitely fall into one of "don't need" or "worked around".
I still think this is a use case that'd make sense to somebody, of course.

OK, thank you. I'll leave this open then, but won't treat it as a priority for now.


Update helm/monocular to kubernetes-helm/monocular

This gets the TLDR instructions working.

Codecov Report

Merging #425 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #425   +/-   ##
=======================================
  Coverage   83.38%   83.38%
=======================================
  Files          26       26
  Lines        1493     1493
=======================================
  Hits         1245     1245
  Misses        197      197
  Partials       51       51

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 3ee5f19...e224d85. Read the comment docs.

oops, thanks!


Polynomials

Added polynomials and piecewise polynomials.

Needs testing, especially the binary search methods in the PiecewisePolynomial class


Implement Content Security Policy

Please explain the problem/why you would want to see a change and any workarounds you might have in place.

Should be an easy one. Already implemented it on my TypeScript experimental branch. This should silence some warnings and things less unnecessarily insecure.

Not required. Custom websites are not loaded in our views (aside from the authenticator) but we don't have any sensitive data that could otherwise be extracted via a XSS vulnerability on Spotify's side.
This is all "from my understanding." No warnings are created. I would consider reopening this if somebody else mentions why.


Webhook doesn't start build

I'm certain that it's me doing something wrong, but for some reason, Jenkins isn't starting a build on my pull request when the webhook is sent.
It seems that GitHub is sending the webhooks and it's delivered (I get a HTTP status 200).
Any pointers as to why?

@Repox Have you looked at the jenkins logs?


HADOOP-18646. Upgrade Netty to 4.1.89.Final to fix CVE-2022-41881 (#5435)

This fixes CVE-2022-41881.
This also upgrades io.opencensus dependencies to 0.12.3
Contributed by Aleksandr Nikolaev
(cherry picked from commit 734f7abfb8b84a4c20dbae5073cf2d4fb60adc1c)
Conflicts:
hadoop-project/pom.xml

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
7m 42s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
18m  6s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
30m  3s

branch-3.3 passed

-1 :x:
compile
5m 34s
/branch-compile-root.txt
root in branch-3.3 failed.

-1 :x:
mvnsite
0m 39s
/branch-mvnsite-root.txt
root in branch-3.3 failed.

-1 :x:
javadoc
9m 22s
/branch-javadoc-root.txt
root in branch-3.3 failed.

-1 :x:
shadedclient
18m 21s

branch has errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
1m 20s

Maven dependency ordering for patch

-1 :x:
mvninstall
1m 30s
/patch-mvninstall-root.txt
root in the patch failed.

-1 :x:
compile
0m 26s
/patch-compile-root.txt
root in the patch failed.

-1 :x:
javac
0m 26s
/patch-compile-root.txt
root in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-1 :x:
mvnsite
0m 24s
/patch-mvnsite-root.txt
root in the patch failed.

+1 :green_heart:
shellcheck
0m  0s

No new issues.

-1 :x:
javadoc
0m 25s
/patch-javadoc-root.txt
root in the patch failed.

+1 :green_heart:
shadedclient
2m  0s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
0m 24s
/patch-unit-root.txt
root in the patch failed.

+0 :ok:
asflicense
0m 25s

ASF License check generated no output?

91m 42s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5729/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5729

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint shellcheck shelldocs

uname
Linux 17052fa75e0e 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 9edfd465ae86abeebaf8b613b2b1f52b717d5869

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5729/1/testReport/

Max. process+thread count
128 (vs. ulimit of 5500)

modules
C: hadoop-project . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5729/1/console

versions
git=2.17.1 maven=3.6.0 shellcheck=0.4.6

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
7m 31s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
17m 20s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
26m 23s

branch-3.3 passed

+1 :green_heart:
compile
20m 51s

branch-3.3 passed

+1 :green_heart:
mvnsite
30m  0s

branch-3.3 passed

+1 :green_heart:
javadoc
8m  2s

branch-3.3 passed

+1 :green_heart:
shadedclient
32m  7s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
1m 13s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
23m  8s

the patch passed

+1 :green_heart:
compile
18m 42s

the patch passed

+1 :green_heart:
javac
18m 42s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
23m 17s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
javadoc
7m 31s

the patch passed

+1 :green_heart:
shadedclient
32m 56s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
722m 45s
/patch-unit-root.txt
root in the patch passed.

+1 :green_heart:
asflicense
1m 50s

The patch does not generate ASF License warnings.

963m  8s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.balancer.TestBalancer

hadoop.hdfs.server.balancer.TestBalancerWithHANameNodes

hadoop.yarn.server.timelineservice.security.TestTimelineAuthFilterForV2

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5729/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5729

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint shellcheck shelldocs

uname
Linux 4b25e7fe6b4d 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 9edfd465ae86abeebaf8b613b2b1f52b717d5869

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5729/2/testReport/

Max. process+thread count
3239 (vs. ulimit of 5500)

modules
C: hadoop-project . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5729/2/console

versions
git=2.17.1 maven=3.6.0 shellcheck=0.4.6

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Looks okay. Merging this one (it's a backport from trunk).


Suggestion: reboot pi after the pull command

Is it possible to add a script line for rebooting the pi when the pull command is finished?
I always get the API error when the pull request is finished and a reboot fixed it.
If not, just tell me where I should add the line and I will do it myself.
Thank you for taking the time to answer.

right below echo 'Done!'; on the Pull command, you can add:
$SUDO reboot
Which will reboot your Pi/device.

I think I'll add the command but comment it out, so that those who want this feature can uncomment. Because there's no way to know what else might be running on a Pi-hole host, I hesitate to force a reboot by default.


Problem with blazeborn

If the player choose the blazeborn origin and the nether is disabled in the server, it generates the nether, when and try to tp the player causes the player to crash.

Remove the blazeborn's power from your server, it can be done via datapack.
I can't be held liable for the owner deciding that half the game should be missing.

I was thinking about adding a condition for the nether respawn, if the nether is disabled in the properties file or by another mod, also the nether spawning needs to be turned off

Yes, it would be feasible, but realistically speaking, this is an extreme edge case that would make the code for that power significantly more complex.
Deactivating the nether is something that is only done in extreme edge cases, and not by 99.9% of the player base.
If someone is willing to disable part of the core experience of the game, they should be willing to do basic research on the origins wiki to fix any issues that may arise.


Prisma Client Binary Not Copied for Netlify Lambda Functions (For Graphql Server)

Bug description
I’m trying to deploy a GraphQL server using Netlify Functions; my app works in development, but doesn’t work in production because the necessary Prisma binary is not copied over post build.
This has been mentioned in another issue (here).
The binary apparently gets copied over using the netlify build command, but not with the specialized netlify-lambda build command.
The current docs offer an example that deploys the Prisma Client to Netlify Functions using REST API endpoints. For that particular use-case, the netlify functions:build command is entirely sufficient (see here). However, in order to build a GraphQL server, only the netlify-lambda build command will work. See here for a step-by-step instruction on how to set up a GraphQL server using Netlify Functions.
Using the netlify-lambda commands, the GraphQL server gets build on Netlify, but Prisma Client’s rhel-openssl-1.0.x binary never gets copied into the functions folder, producing the following log at /graphql.js:
Invalid `prisma.user.findOne()` invocation:

Query engine binary for current platform "rhel-openssl-1.0.x" could not be found.
This probably happens, because you built Prisma Client on a different platform.
(Prisma Client looked in "/query-engine-rhel-openssl-1.0.x")

You already added the platforms "native", "rhel-openssl-1.0.x" to the "generator" block
in the "schema.prisma" file as described in https://pris.ly/d/client-generator,
but something went wrong. That's suboptimal.

Attempts to manually fix it
Since I know (or think I know) what the issue is (i.e. a missing rhel-openssl-1.0.x binary file), I tried to copy it post-installation into the functions destination folder. At first I tried using a custom webpack plugin, which I was able to pass into the build by using netlify-lambda build functions -c ./webpack.config.js (documentation here):
webpack.config.js
const CopyPlugin = require('copy-webpack-plugin')

module.exports = {
	plugins: [
		new CopyPlugin([
			{
				from<EMAIL_ADDRESS>			}
		])
	]
}

However, the issue with that is that Webpack just packs the binary into the build-functions folder. However, then zip-it-and-ship-it just takes the graphql.js function out of the build-functions folder — and not the binary — and places it into a folder like this: /tmp/zisi-5e8687894a4e660007b0e842. Thus, the binary gets lost in production.
Next, I tried salvaging the binary by using a custom-built plugin.
prisma-client-plugin.js
const fs = require('fs')

module.exports = {
	onPostBuild: api => {
		console.log('Copying over `rhel-openssl-1.0.x` binary engine...')
		const src =<EMAIL_ADDRESS>		const dest = `${api.constants.FUNCTIONS_DIST}/query-engine-rhel-openssl-1.0.x`
		fs.copyFile(src, dest, err => console.log(err))
	}
}

Sure enough, that got the binary actually copied into that temporary folder! Still, however, nothing happened. Binary was still missing in production.
So I wondered if the binary needs to be zipped in order for it to make it into the live site. So I did that:
const fs = require('fs')
const zip = new require('node-zip')()

module.exports = {
	onPostBuild: api => {
		console.log('Copying over `rhel-openssl-1.0.x` binary engine...')
		const src =<EMAIL_ADDRESS>		const dest = `${api.constants.FUNCTIONS_DIST}/query-engine-rhel-openssl-1.0.x`
		fs.copyFile(src, dest, err => console.log(err))

		console.log('Zipping binary engine...')
		zip.file(`query-engine-rhel-openssl-1.0.x`, fs.readFileSync(dest))
		const data = zip.generate({ base64: false, compression: 'DEFLATE' })
		fs.writeFileSync(`${api.constants.FUNCTIONS_DIST}/query.zip`, data, 'binary')

		console.log('Removing unzipped binary engine...')
		fs.unlinkSync(dest)
	}
}

The zipping works, but now there’s a query.js function file 😂
So as before, Prisma Client cannot access the rhel-openssl-1.0.x binary engine.
I have spent days trying, to no avail. Any help would be greatly appreciated!
netlify.toml
[build]
publish = "build/"
# Needed to take all netlify-lambda commands out of the package.json file and place them directly into the netlify.toml file for production, since during development Netlify attempts to run scripts that contain `netlify-lambda` functions! See: https://github.com/netlify/cli/issues/723#issuecomment-605511147
command = "cd functions && yarn && cd .. && yarn && npx prisma generate && npx netlify-lambda build functions && react-scripts build"
# During production, `functions` folder cannot be the same as destination when using `netlify-lambda`, so you need to create another destination.
functions = "build-functions/"

[build.environment]
# Fix to ensure the Prisma binary is packaged with the lambda function; [note from Martin: this seems unnecessary when using the netlify-lambda commands]
ZISI_VERSION = "0.4.0-9"

[[plugins]]
package = "./prisma-client-plugin"

[context.develop]
# `netlify dev` in local development won't work unless destination is the same as actual `functions` folder.
functions = "functions/"

How to reproduce
For reproduction, I created a dummy repo that contains all the crucial files. Feel free to clone and connect to your own Postgres db and deploy via Netlify Functions using this guide.

DEMO REPO

Tagging @DavidWells from Netlify — your build plugin instructions were helpful, thank you. Might you know what I’m missing?

@heymartinadams To make it work on Zeit's now, serverless functions i generate in my postinstall script because now prunes dependencies after build.
"postinstall": "npm run generate",

It's a thing i had to do using heroku too.
Don't know if it helps with netlify functions too?

Thanks for the detailed write-up.
Based on a brief reading of the netlify-lambda docs:

Netlify-Lambda uses webpack to bundle up your functions and their dependencies for you, suiting the first approach. However, if you have native node modules (or other dependencies that don't expect to be bundled like the Firebase SDK) then you may want to try the other approaches. In particular, try Netlify Dev.

Have you given Netlify Dev a go?

@2color unfortunately this didn’t work either 😕 By using the netlify dev command instead, Netlify is choosing to run npm run dev, even though I never indicated for it to do so. (I personally dislike this approach: even if I specify exact build commands in netlify.toml, Netlify will still pick-and-choose which script to run from your package.json file — this also happens with netlify-lambda)
If I specify the following command in netlify.toml: yarn && cd functions && yarn && cd .. && npx prisma generate && npx netlify dev and if the dev script reads this: react-scripts build, deployment just keeps hanging and nothing happens.

@2color in case it helps: 2.0.0-beta.1 causes the binary to not be copied over in local development. preview025 on the other hand does.
As you know, Prisma Beta was launched a few days ago — while I was trying to get deployment to work — and so I upgraded right away. When I tried to run the app in dev mode today for the first time since, to my surprise the app gave me the same missing binary error (for the "darwin" binary).
Reverted to and deployed with 2.0.0-preview025 using the above setup, and lo and behold, it is working, at least locally.
So something happened between preview025 and beta.1 that prevents the binary from being copied during local development.

I'm also able to reproduce the problem.
It seems like a change in the Netlify build image caused the ZISI_VERSION to be ignored.
Here's the build log that confirms this hypothesis:
12:04:44 PM: Installing Zip-it-and-ship-it 0.4.0-9
12:04:46 PM: zip-it-and-ship-it version: 0.3.1
12:04:46 PM: Started restoring cached go cache
12:04:46 PM: Finished restoring cached go cache
12:04:46 PM: unset GOOS;
12:04:46 PM: unset GOARCH;
12:04:46 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64';
12:04:46 PM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}";
12:04:46 PM: go version >&2;
12:04:46 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env';
12:04:46 PM: go version go1.12 linux/amd64
12:04:46 PM: Installing missing commands
12:04:46 PM: Verify run directory
12:04:46 PM: Executing user command: npm run build
12:04:46 PM: ><EMAIL_ADDRESS>build /opt/build/repo
12:04:46 PM: > prisma generate
12:04:47 PM: ✔ Generated Prisma Client to ./node_modules/@prisma/client in 153ms
12:04:47 PM: You can now start using Prisma Client in your code:
12:04:47 PM: ```
12:04:47 PM: import { PrismaClient } from '@prisma/client'
12:04:47 PM: // or const { PrismaClient } = require('@prisma/client')
12:04:47 PM: const prisma = new PrismaClient()
12:04:47 PM: ```
12:04:47 PM: Explore the full API: http://pris.ly/d/client
12:04:47 PM: Function Dir: /opt/build/repo/functions
12:04:47 PM: TempDir: /tmp/zisi-5e8afe961d29987fde4707fc
12:04:48 PM: Prepping functions with zip-it-and-ship-it 0.3.1

@heymartinadams there's a workaround which should simplify this further.
By enabling the Netlify Build Plugins beta, the latest version of zip-it-and-ship-it will be used which should resolve the problem you're experiencing.
Source: https://github.com/netlify/build-image/issues/386#issuecomment-609714084

@2color I have the Netlify Build Plugin beta enabled for that site, though 😕
Also, my logs:
2:00:00 PM: Installing Zip-it-and-ship-it 0.4.0-9
2:00:02 PM: zip-it-and-ship-it version: 0.4.0-9

I am trying to deploy directly to Lambda and I am getting the same error. I have the target set in the my schema file.
  binaryTargets = ["rhel-openssl-1.0.x"]

"Invalid `prisma.user.findOne()` invocation:

Query engine binary for current platform "rhel-openssl-1.0.x" could not be found.
This probably happens, because you built Prisma Client on a different platform.
(Prisma Client looked in "/query-engine-rhel-openssl-1.0.x")

You already added the platform "rhel-openssl-1.0.x" to the "generator" block
in the "schema.prisma" file as described in https://pris.ly/d/client-generator,
but something went wrong. That's suboptimal.

Please create an issue at https://github.com/prisma/prisma-client-js/issues/new"

@Jaikant Can you please open a new issue with details of your deployment setup?

Looong time later, an update: https://github.com/prisma/prisma/issues/1015#issuecomment-808490548 netlify-lambda is on its way out, so this problem will hopefully go away by itself.
If anyone is still hitting similar problems, please open a new issue and describe your situation. We are super eager to look into these and improve your experience.


use template.config.js

We can update our template using the new template.config.js file.
More info needed but a few things:

[ ] add setup script to config
[ ] create template directory and add to config
[ ] add title placeholder
[ ] add package.json placeholder name

Source:
https://github.com/react-native-community/cli/blob/master/docs/commands.md#init

This is proving to be tougher than anticipated. I'm not sure why, but for some reason when I do it this way, it creates a generic RN project, and adds the template directory inside.
Things I've tried:

testing with the react-native-community-typescript-template
-- it works with theirs
-- it works when i test it locally with theirs
using their template in our directory (does not work)

So it has to be something with the folder itself? I'm not sure what.

Notes:

break out separate issue for running the postInitScript
write down notes for what we've tried


ol.proj.toLonLat only work with projection as a string it seems

this is with the ol package in version 4.2.0
var center = proj.toLonLat(view.getCenter(), view.getProjection().getCode());

works ok
but
var center = proj.toLonLat(view.getCenter(), view.getProjection());

does not even though the toLonLat function specifies it can take a ProjectionLike

this check
 */
_ol_proj_.getTransform = function(source, destination) {
  var sourceProjection = _ol_proj_.get(source);

results in sourceProjection being null

the instanceof checks fails

ah seems to be a duplicate of #6926 I will check with the latest

ah I actually I have the exact same thing as #6926 in where ol-mapbox-style included ol 4.1.1 and ol 4.2.0 is included in my project's package.json


Migrate nova and libvirt to composable service interface

Migrate nova and libvirt to composable service interface
Depends-On: https://github.com/openstack-k8s-operators/openstack-operator/pull/432

I guess this regress the changes made in https://github.com/openstack-k8s-operators/dataplane-operator/pull/325

I guess this regress the changes made in #325

We may actually just need to revert #325
Everything edpm_ovn* should be set by the config generation interface when OVN is migrated to a proper composable service. Those vars/values should be coming through in a ConfigMap/Secret on the DataPlaneService that deploys OVN and set by the ovn-operator.

I guess this regress the changes made in #325

We may actually just need to revert #325
Everything edpm_ovn* should be set by the config generation interface when OVN is migrated to a proper composable service. Those vars/values should be coming through in a ConfigMap/Secret on the DataPlaneService that deploys OVN and set by the ovn-operator.

You are right. That will be the way to pass these values.

recheck

recheck

recheck

RDO Ci is failing with:
2023-08-10T20:15:02.739558726+00:00 stderr F {"level":"error","ts":"2023-08-10T20:15:02Z","msg":"Unable to deploy edpm-compute","controller":"openstackdataplanerole","controllerGroup":"dataplane.openstack.org","controllerKind":"OpenStackDataPlaneRole","OpenStackDataPlaneRole":{"name":"edpm-compute","namespace":"openstack"},"namespace":"openstack","name":"edpm-compute","reconcileID":"f5b39ab8-fa81-4eea-9489-b679cab7a5a2","ObjectType":"*v1beta1.OpenStackDataPlaneRole","ObjectNamespace":"openstack","ObjectName":"edpm-compute","error":"Secret \"nova-cell1-compute-config\" not found","stacktrace":"github.com/openstack-k8s-operators/lib-common/modules/common/util.LogErrorForObject\n\t/go/pkg/mod/github.com/openstack-k8s-operators/lib-common/modules/common@v0.1.0/util/log.go:65\ngithub.com/openstack-k8s-operators/dataplane-operator/controllers.(*OpenStackDataPlaneRoleReconciler).Reconcile\n\t/remote-source/controllers/openstackdataplanerole_controller.go:329\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:122\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:323\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:274\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:235"}

from https://logserver.rdoproject.org/37/337/9b6ef987c8bbb603953455a009e62595bbad810d/github-check/dataplane-operator-crc-podified-edpm-baremetal/a14dd5a/ci-framework-data/logs/crc/pods/openstack-operators_dataplane-operator-controller-manager-7977db695f-j782t_344f066b-209b-4e53-8106-93c91e7f2147/manager/0.log
looks like the nova-operator being deployed in the test is v0.0.1, which is too old and does not contain https://github.com/openstack-k8s-operators/nova-operator/pull/452. Going to try adding that back as a Depends-On.

recheck

recheck

The baremetal job ran the nova deployment successfully at least. From https://logserver.rdoproject.org/37/337/a79aa53f6434ca1c6c42f618d7bd909b61c29fc5/github-check/dataplane-operator-crc-podified-edpm-baremetal/ea861b5/ci-framework-data/logs/oc_inspect/namespaces/openstack/pods/dataplane-deployment-nova-edpm-compute-n5v4r/openstackansibleee/openstackansibleee/logs/current.log
2023-08-11T12:38:42.614200886Z PLAY RECAP *********************************************************************
2023-08-11T12:38:42.614200886Z edpm-compute-0             : ok=21   changed=8    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0

I'm ok to override then

We still can't override until https://github.com/openstack-k8s-operators/openstack-operator/pull/432 merges.

recheck

recheck

recheck

/retest

recheck

recheck

/lgtm

/hold

/unhold


🌱 Move golang.org/x/*  ignore rules after the * rule

Dependabot is not picking up the ignore rule for golang.org/x/*  and hence not updating it. It might be the * is superseding everything. We will try to move it below the * rule to check if it helps dependabot picking it up
Signed-off-by: Kashif Khan<EMAIL_ADDRESS>

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

/override metal3-centos-e2e-integration-test-main metal3-ubuntu-e2e-integration-test-main

/assign @tuminoid

/retitle 🌱 Move golang.org/x/* ignore rules after the * rule
Removed the formatting, as it'll look funny in the release notes.

/cc @lentzi90 @Sunnatillo @smoshiur1237


Improve the code coverage of the gtype module

Issue：https://github.com/gogf/gf/issues/1974

Codecov Report

Merging #1975 (571af7e) into master (1acc1b8) will increase coverage by 0.79%.
The diff coverage is 73.96%.

:exclamation: Current head 571af7e differs from pull request most recent head 21ec189. Consider uploading reports for the commit 21ec189 to get more accurate results

@@            Coverage Diff             @@
##           master    #1975      +/-   ##
==========================================
+ Coverage   75.41%   76.21%   +0.79%
==========================================
  Files         512      512
  Lines       46504    46656     +152
==========================================
+ Hits        35070    35557     +487
+ Misses       9413     9101     -312
+ Partials     2021     1998      -23

Flag
Coverage Δ

go-1.15-386
76.13% <73.96%> (+0.79%)
:arrow_up:

go-1.15-amd64
76.13% <73.96%> (+0.83%)
:arrow_up:

go-1.16-386
76.13% <73.96%> (+0.80%)
:arrow_up:

go-1.16-amd64
76.13% <73.96%> (+0.77%)
:arrow_up:

go-1.17-386
76.16% <73.96%> (+0.77%)
:arrow_up:

go-1.17-amd64
76.19% <73.96%> (+0.80%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

contrib/drivers/pgsql/pgsql.go
65.89% <0.00%> (+54.78%)
:arrow_up:

database/gredis/gredis_config.go
77.41% <ø> (ø)

net/ghttp/ghttp_request.go
83.20% <ø> (ø)

os/gcron/gcron_schedule.go
70.42% <71.55%> (+3.33%)
:arrow_up:

os/gcron/gcron_entry.go
69.52% <75.60%> (+8.88%)
:arrow_up:

database/gredis/gredis_adapter_goredis.go
91.04% <78.57%> (-3.51%)
:arrow_down:

net/goai/goai_path.go
66.92% <94.11%> (+5.48%)
:arrow_up:

internal/utils/utils_debug.go
75.00% <100.00%> (+5.00%)
:arrow_up:

os/gres/gres_file.go
72.41% <100.00%> (+2.04%)
:arrow_up:

os/gres/gres_resource.go
84.65% <100.00%> (+0.54%)
:arrow_up:

... and 28 more

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 0e6becc...21ec189. Read the comment docs.


chore(main): release 9.11.0

:robot: I have created a release beep boop
9.11.0 (2024-11-19)
Features

mini_pick: allow multi selection in /files (#444) (68e0610)

Bug Fixes

chat: #447 moving between windows (d3e88dd)
OpenAI-compatible adapter (#446) (3bfc575)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v9.11.0
:sunflower:


Fix typo in Removing from an array part

Changes:

Code and snippet have same value but the explanation has different value. With this PR value is same.

Thanks 😄


True/False permission node change

Basically, on discord I was talking about this, and the mod said I should post it here.
Let’s say you set a permission for a player called test.
/lp user test permission set test.permission false
If I want to make that permission TRUE, Then I have to delete the permission, then I have to redo the permission with true at the end.
My suggestion is that you can toggle the permissions from true to false without resetting the permission.

Will do, I’ll tell you if it works afterwards.


Better types

Hi,
I checked the types and noticed the return type (Methods) is too general.
Which results that listenAll being just a Function,

Therefore the listener variable becomes any, also there are no arg types for the listenAll function.

(I would suggest removing the Methods interface as the return type of the bph fn and letting the TypeScript compiler figure out the exact interfaces of the returned fns.)

function bph(config: Config): {
    getBreakpoints: () => Breakpoints;
    getMediaQuery: (name: BpNameOrNames, useMax?: boolean) => string;
    isMatching: (name: BpNameOrNames, useMax?: boolean) => boolean;
    listen: (options: ListenOptions, callback: (event: MediaQueryListEvent | MediaQueryList) => void) => ListenersReturn;
    listenAll: (callback: (bps: string[]) => void, options?: ListenAllOptions) => ListenersReturn;
}

Hey @merobal, thanks for the input, will look into it and add your suggestions.

Works perfectly, thanks!


DistutilsOptionError on Requirements.txt Install & Build

Per this issue in the azure storage repo, we're having an issue with read the docs.
For all the older versions everything built successfully both locally and on read the docs, and locally the html looked as expected. Looks like read the docs has some difference though and while the build succeeds, there's no actual content in the modules, like this example.
I've fiddled around with the advanced settings and tried with both python 2 and 3 as well as with and without virtual env. No changes.
Next I tried adding azure-common to the doc requirements.txt. This worked fine locally again (no changes) but on read the docs now the build is broken.
The most info I could find online was an older issue on Stack Overflow Since you can't specify --update in a requirements.txt as far as I know, I tried forcing to the newest version. Build is still broken. Not much change once again.
Any ideas?
PS: A main clue I used to guide my fiddling was that ReadTheDocs is working fine for azure-sdk-for-python which has a nearly identical configuration. I tried adding the azure-common dependency because it's needed to making the azure-storage package even valid which is why I assumed it could the problem. Still, all just guesses. Hoping you have more insight.

This is maybe the setuptools version we're pinning in our setup steps? We're pinning 18.0.2. Can you confirm 18.0.2 is problematic?

Hmm... very weird. I just tried installing 18.0.2 and that doesn't appear to be a valid version. I thought maybe I messed up but I don't see it listed on pip or in their version list. Could you clarify?
Error:

pip install setuptools==18.0.2
Collecting setuptools==18.0.2
  Could not find a version that satisfies the requirement setuptools==18.0.2 (from versions: 0.6b1, 0.6b2, 0.6b3, 0.6b4, 0.6rc1, 0.6rc2, 0.6rc3, 0.6rc4, 0.6rc5, 0.6rc6, 0.6rc7, 0.6rc8, 0.6rc9, 0.6rc10, 0.6rc11, 0.7.2, 0.7.3, 0.7.4, 0.7.5, 0.7.6, 0.7.7, 0.7.8, 0.8, 0.9, 0.9.1, 0.9.2, 0.9.3, 0.9.4, 0.9.5, 0.9.6, 0.9.7, 0.9.8, 1.0, 1.1, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.2, 1.3, 1.3.1, 1.3.2, 1.4, 1.4.1, 1.4.2, 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2, 2.2, 3.0, 3.0.1, 3.0.2, 3.1, 3.2, 3.3, 3.4, 3.4.1, 3.4.2, 3.4.3, 3.4.4, 3.5, 3.5.1, 3.5.2, 3.6, 3.7, 3.7.1, 3.8, 3.8.1, 4.0, 4.0.1, 5.0, 5.0.1, 5.0.2, 5.1, 5.2, 5.3, 5.4, 5.4.1, 5.4.2, 5.5, 5.5.1, 5.6, 5.7, 5.8, 6.0.1, 6.0.2, 6.1, 7.0, 8.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.1, 8.2, 8.2.1, 8.3, 9.0, 9.0.1, 9.1, 10.0, 10.0.1, 10.1, 10.2, 10.2.1, 11.0, 11.1, 11.2, 11.3, 11.3.1, 12.0, 12.0.1, 12.0.2, 12.0.3, 12.0.4, 12.0.5, 12.1, 12.2, 12.3, 12.4, 13.0.1, 13.0.2, 14.0, 14.1, 14.1.1, 14.2, 14.3, 14.3.1, 15.0, 15.1, 15.2, 16.0, 17.0, 17.1, 17.1.1, 18.0, 18.0.1, 18.1, 18.2, 18.3, 18.3.1, 18.3.2, 18.4, 18.5, 18.6, 18.6.1, 18.7, 18.7.1)
No matching distribution found for setuptools==18.0.2

Oops, sorry, that should have been 18.0.1

pip install setuptools==18.0.1
Collecting setuptools==18.0.1
Using cached setuptools-18.0.1-py2.py3-none-any.whl
Installing collected packages: setuptools
Exception:
Traceback (most recent call last):
File "C:\Python34\lib\site-packages\pip\basecommand.py", line 211, in main
status = self.run(options, args)
File "C:\Python34\lib\site-packages\pip\commands\install.py", line 311, in run
root=options.root_path,
File "C:\Python34\lib\site-packages\pip\req\req_set.py", line 646, in install
**kwargs
File "C:\Python34\lib\site-packages\pip\req\req_install.py", line 803, in install
self.move_wheel_files(self.source_dir, root=root)
File "C:\Python34\lib\site-packages\pip\req\req_install.py", line 998, in move_wheel_files
isolated=self.isolated,
File "C:\Python34\lib\site-packages\pip\wheel.py", line 242, in move_wheel_files
name, user=user, home=home, root=root, isolated=isolated
File "C:\Python34\lib\site-packages\pip\locations.py", line 183, in distutils_scheme
i = d.get_command_obj('install', create=True)
File "C:\Python34\lib\distutils\dist.py", line 857, in get_command_obj
self._set_command_options(cmd_obj, options)
File "C:\Python34\lib\distutils\dist.py", line 901, in _set_command_options
% (source, command_name, option))
distutils.errors.DistutilsOptionError: error in setup.cfg: command 'install' has no such option 'single_version_externally_managed'

Did this get resolved? Let me know if it hasn't, and I'll look into it.

No, not resolved. I reproed on my machine (per above) so it does look like a version issue with read the docs setup tools. Would really appreciate the follow up!

Pinging @dstufft because this appears to be a setuptools/pip bug. Upgrading our pip might fix this (#1958)

I see the pip 8 CR was merged a couple weeks ago but this is still not working for us. Is this not released yet?
This has been open since December 1st and we really need to get some traction on this as I currently can't get anything published and we just had a major release. We don't need a fix, but we do need something that will unblock us. A workaround is totally fine (maybe uploading the pages manually? Is that an option?)
I'm not sure what else I can follow up on since I don't control and can't manually inspect the ReadTheDocs build environment. Best theory I can find besides setuptools version is  this which indicates pip may be installed in a weird way?) which indicates pip could be installed badly.
My broken build is here
Please tell me if there's anything I can do to help with this investigation.

@emgerner-msft are you able to reproduce this locally with a new pip?
The issue you linked seems to be due to an egg version of pip, it looks like it isn't installed this way in your project's env.
What is strange is distutils code executing from /usr/lib/python2.7/distutils/dist.py -- I'd expect this to execute from setuptools. This might explain why the error implies an old version of setuptools. I could also be horribly wrong.

I can't reproduce this locally with my normal setup. I was able to successfully generate docs and post them to GitHub.io for the time being actually.
My Python install is totally standard -- I just downloaded it and installed exactly as specified on the Python page.

Okay, i was able to reproduce consistently with setuptools 18.6. Your setup.cfg blocked further attempts to upgrade setuptools, due to the missing option specified there. Moving outside that path and upgrading to setuptools==20, I was able to resolve the issue.
This will require an upgrade on our side, as even if you try to pin a new version, your setup.cfg will block installation.

Created #2004 to address this.

Awesome, thanks! Really appreciate you looking at this. When can we expect this to take effect so I can try a rebuild?

Hey, I see all of these PRs were merged about a month ago, but I'm still having the same build issues. Should these be resolved?

@emgerner-msft hrm, it should be, though perhaps you need to wipe the version and rebuild from scratch. You should be able to wipe the version from your version dashboard page.

Tried wiping and rebuilding, but it's still failing with the exact same error as before.

Sorry for the delay, getting back to this now. I'll see what's happening on our stack, this might require some poking on our build servers.

Ping... released again and tried building again. Still failing.

I don't want to push you guys, however could you update status of this issue? Thanks in advance (you're still awesome!)

@jotes no worries, we've been rather busy and lost track of this. I've been looking into this for the last couple hours, this has me less stumped, but more frustrated now.
So, inside the virtualenv, distutils is patched in by virtualenv, but it doesn't patch distutils.dist, which passes down to /usr/lib/python2.7/, where distutils.dist is defined. This is where things get aggravating. I thought this might be virtualenv, but it doesn't patch distutils.dist on my machine either, so that looks normal. I thought it might be a matter of Python 2.7.6's distutil, but I can't replicate this locally, which I should be able to if that were the case. My only other thought here is the system setuptools is supposed to monkey patch something that it isn't, but I've attempted upgrades there to no avail.
I'll keep plugging away later tonight, but this is looking like less of an issue of our platform not co-operating with azure-storage, and more of an issue of the setup.cfg you are using causing a problem due to the setuptools/distutils/pip/virtualenv/whatever version. I'm still trying to determine if this is a bug or a matter of system libraries being improperly used, but if you are able to reproduce locally, inside a virtualenv, more debug information would be helpful.

I can't repro this locally. We're successfully building docs and currently hosting them on GitHub. I asked some coworkers with of course slightly different setups to try as well and they can't either. It sounds like you can't either. Why the platform can't handle this stumps me too. Tell me if I can do anything in particular.

So, I was able to reproduce the error locally, on Python 2.7.6, the version reported by Ubuntu 14.04 -- well, it's released as 2.7.5~5, but whatever. This appears to be an incompatibility with Python 2.7.6 distutils, though I can find no information on what changed in distutils. I had tested this yesterday and it passed, but I assume pyenv decided to not use 2.7.6 for some reason. Things are confirmed in a 2.7.6 virtualenv, with a modern virtualenv, setuptools, and pip.
So if this is a simple matter of 2.7.6 distutils not supporting the option in setup.cfg, there seem to be several options:

Wait for https://github.com/rtfd/readthedocs-docker-images/issues/9 -- we'll be testing this soon, and don't expect a huge fallout from the shift in releases
Use conda to target the versions of Python you need
Find some way to move the option out of setup.cfg and into setup.py where it can be evaluated conditionally (??)

Okay. I'm filing this as a setuptools bug.
I added your project to beta test ubuntu 16.04 images and even Python 2.7.11 gives this same error. I thought that maybe this is only included in Python 3 distutils, and lo and behold, it builds correctly. I'm not sure if you are building with py3 locally, which might make sense, but I can't find any information signaling single-version-externally-managed as a py3 specific option.

Annnnd scratch that as well >:x
Consistently reproducing on pypa/setuptools#566 with 3.5.1 as well. I'm stumped.

Looks like the latest builds here are passing. Did this issue get resolved?

I can confirm that my docs with hashes are building without any problems: https://readthedocs.org/projects/jotes-pontoon/builds/5234878/

Just pinging @emgerner-msft here since it seems that the original project reported in the issue is building properly (https://readthedocs.org/projects/azure-storage/builds/) and @jotes says that the issue was solved.
Can you confirm that it's solved for you and we can close this issue?

We ended up (incidentally) changing how our project was built so this looks like it went away as a result of that based on the timeline, not because the issue was necessarily fixed. So, that's why you stopped hearing from me. :) Up to you if you want to close the issue or root cause further, but my project is in a good state so I'm perfectly happy.

Hoo boy. Rereading this thread was a rollercoaster. Glad it was resolved-ish!
Closing this for now.


Audit events

Any plans to add auditing events to the cf_exporter? It would be nice to gather those details per app too.

@omearaj By auditing events, are you referring to audit.* events?
If yes, I'm not sure how you want to report those events. We cannot report events as metrics, but we can report counters like totals or deltas (ie audit_app_restage_total{application_id="xxx"}).
But this is going to be challenging, we need to query the /v2/events periodically doing pagination and this can be tricky in high load environments. We need to start thinking about the architecture and how it can handle millions of events, and the final result will be something like the loggregator. I'm not sure that this makes sense at all, I'd rather prefer that the firehose emits those events. The use case for the cf_exporter is quite simple, it's just to report administrative metrics (like total number of orgs, apps, ...).


it does not work on ie

i got this error even on you demo page : https://sayan.ee/angularjs-pdf/
SCRIPT5007: Unable to get property 'src' of undefined or null reference
pdf.js (9172,5)

which version of IE?

all of them !! , if you enter edge it works fine , but if you try to open with internet explorer  virsion 9 - 11 it does not load .

This module has a dependancy on PDF.js. Seems like there's limited support for IE10 and below: https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#what-browsers-are-supported

thx , i will look into it :) , but still , internet explorer 10 and 11 does not work either

Yeah it does not work on IE. Any updates on this?

any fix? @itssujan  having the same issue here! A white page shows, I think it's because of DFP ads.

i found out some extension for pdfjs and it worked ,can't find it now though , try to update to the latest pdf.js and worker  . they might have fixed the issue


Understanding Search Algorithms in AI

We ask that you please be patient as our team works through approving and publishing all articles/tutorials in a timely manner. Allow 1-3 days for a topic to be reviewed and/or approved - allow 3-7 days for an articles to be reviewed and/or published.
Be sure to visit our Resources Page for tools, resources, and example articles to go over.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
NOTE: We tend to stray away or tend not to publish reviews/comparisons of commercial product offerings.
We're looking for the first 2-3 paragraphs of the article that appropriately summarize what your article will be about.
Proposed title of article
Understanding Search Algorithms in Artificial Intelligence
Introduction paragraph (2-3 paragraphs):
Search algorithms are important because they solve various problems in artificial intelligence. There are various search algorithms in AI. This article takes you through search algorithms, including their importance and properties. It will also provide the classification of search algorithms and identify the popular search algorithms in AI.
Key takeaways:

What is a search algorithm?
Importance of search algorithms
Properties of search algorithms
Types of search algorithms
Applications of search algorithms
Conclusion

References:
Please list links to any published content/research that you intend to use to support/guide this article.
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

@gracejolie
Good afternoon and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

Pinging our resident expert to help shed some more light on the topic @lalith1403

Hey @gracejolie. Thanks for submitting the topic form. Can you explain what search algorithms are and how they solve problems in AI?

Hey @gracejolie. Thanks for submitting the topic form. Can you explain what search algorithms are and how they solve problems in AI?

@lalith1403 Search algorithms are algorithms that help in solving search problems. A search problem consists of a search space, start state and goal state. Search algorithms help the AI agents to attain the goal state through the assessment of scenarios and alternatives. The algorithms provide search solutions through a sequence of actions that transform the initial state to the goal state. Without these algorithms, AI machines and applications cannot implement search functions and find viable solutions.

Yes. Can you discuss some of the algorithms that you will be going deep into. Post that, we can finalize the topic.

Yes. Can you discuss some of the algorithms that you will be going deep into. Post that, we can finalize the topic.

@lalith1403 I will be discussing breadth-first, depth first, iterative deepening, uniform cost, bidirectional, greedy, A* graph, and A* tree algorithms.

Hello @gracejolie. This seems to be a super helpful and essential topic. Please start working on the topic proposed. Let's ignite all the boosters on this one and deliver superior value to the reader.
Let's be sure to provide value that we as developers feel is scarcely available out there on the web. Custom projects would be the best way to explain such concepts. We avoid projects and explanations readily available on documentation sites and blogs.
Cheers,
Lalith

@gracejolie
Just pinging you on this topic form - as I'm making some room in the topic queue.
No rush if you're still working on this one - if you need more time we can always re-open at a later date.

@hectorkambow Please re-open this issue so that I can open a pull request. I've been waiting for almost a month now.
cc @louisefindlay23
cc @lalith1403


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-extensions/eventing-writers
/assign knative-extensions/eventing-writers
Produced by: knative-extensions/knobots/actions/update-deps

/retest

/test integration-tests

/test integration-tests

/retest-required

checking
/cc

Probably misses https://github.com/knative-extensions/reconciler-test/pull/765 in eventing-core.
Tests seem to fail, as WithIstioPodLabels() overrides the labels on the CronJob and thus the sinkbinding does not find the subject by its labels:
https://github.com/knative/eventing/blob/e7fca7646f4a7f47a29494fd8e8b39f0a258c8fb/test/rekt/features/sinkbinding/feature.go#L145-L154


Switch from actions-rs/* actions

Looks like the whole actions-rs organization is archived, so we can't expect any more updates. actions-rs/install uses the deprecated node12 runner and is forced to run on node16 instead. This seems fine for now, but might become a problem as the minimum Node version for GitHub Actions continues to be increased.

Thanks for the heads up @spenserblack
I created a PR to address this issue #1191


[RESOLVED] Unavailable by ICMP ping

Problem started at 20:36:14 on 2023.01.04
Problem name: Unavailable by ICMP ping
Host: ZO-FG
Severity: High
Operational data: Down (0)
Original problem ID: 4660
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23123&eventid=4660

Problem has been resolved in 1m 0s at 20:37:14 on 2023.01.04
Problem name: Unavailable by ICMP ping
Host: ZO-FG
Severity: High
Original problem ID: 4660