Fix build for wasm

Adds necessary #ifs to fix the WASM build.
Motivation:
Seems like a few places were missed in the locking refactor, which made the WASM build fail due to missing pthread types and unknown rwlock variable.
Modifications:
#if-ed out remaining mentions of pthread types and variables not available on WASM.
Result:
swift-log is usable on WASM again.

@swift-server-bot test this please

@swift-server-bot test this please

@ahti Nice!! I'm happy to see that fix landed! Out of curiosity, I thought that if you were to import WASILibc that there was some support for pthreads, or, perhaps those were just stubbed for now?
Somehow I vaguely remember seeing a commit for the removal of the stubs, but it's also entirely possible I'm just confusing myself with something else.
In either event, it's great to see all this progress! Thanks!


Fix #4592 by falling back to a legacy ScrollEvent property on Edge.

The ScrollEvents in Edge are a pain in the a**. The deltaY amount depends on the window geometry (or the ratio between window height and window width), so it can have values as high as 130px or as low as 25, depending on how the user resizes a browser window.
The only way to work around this right now is to rely on the legacy wheelDeltaY event property, which Edge keeps at +/-120 per tick.
I have not tried Edge with a proper touchpad.
Furthermore, changed the values of the guessed deltas to be exactly 60 (this prevents FFX scrolling by 54px and others by 60, which causes problems with small zoomSnaps.

Let's merge and see how that goes :)


[New] jsx-no-target-blank: Add warnOnSpreadAttributes option

Resolves #2827
I've changed the rule to warn on the JSXOpeningElement instead of a specific attribute. There is a technical reason and an architectural reason:

when disabling trustSpreadAttributes, we could end up with multiple warnings for the same problem e.g. once on a target="_blank" attribute and once on {...myUnsafeObject} spread attribute
it makes more sense (to me) that the rule warns on the element instead of a specific attribute since the problem is not necessarily due to any specific attribute, but the combination and order of the attributes on the element

Commit message
Add trustSpreadAttributes for jsx-no-target-blank

Defaults to true. When disabled, treats spread attributes as dangerous
unless explicitly overriden e.g. the following is safe:

<a {...dangerousObject} rel="noreferrer" target="_blank"></a>

This change also extends target="_blank" detection to include
conditional expressions whose alternate or consequent is the "_blank"
string (case-insensitive).

cc @ljharb

I've changed the option name to warnOnSpreadAttributes (defaults to false). Thanks for pointing me to the right pattern for these things. This is ready for review again!

This is ready for review again.

Any chance this could be enabled by default or added to the recommended preset in the next major release? We're using the recommended preset, and that would save an override of the preset with this rule simply to enable this option 🙏

Any chance this could be enabled by default or added to the recommended preset in the next major release? We're using the recommended preset, and that would save an override of the preset with this rule simply to enable this option 🙏

In the next major release, yes (along with many other changes), because it’d be a breaking change - but there’s no major releases planned any time soon.

In the next major release, yes (along with many other changes), because it’d be a breaking change - but there’s no major releases planned any time soon.


Add init.d script for services required by Intercity

/cc @michiels

Ok this PR looks good. I'm still not sure if this is the "Ubuntu" way to use services. I think Ubuntu still uses upstart in 14.04 which looks like this: https://github.com/mperham/sidekiq/blob/master/examples/upstart/sidekiq.conf
However, this solves the problem at the moment in the more traditional init.d scripts. Ubuntu is going to migrate to another upstart variant, systemd. So we can switch to that when new LTS comes out: http://www.pcworld.com/article/2895517/ubuntu-just-switched-to-systemd-the-project-sparking-controversy-throughout-linux.html
:shipit! :D

@michiels Yeah I played with Systemd for another project (which is a super nice service manager). Let's merge this for now, and work on moving to systemd later on.


invalid buildstream.conf format returns stacktrace

See original issue on GitLab
In GitLab by [Gitlab user @knownexus] on Oct 8, 2018, 16:18
Summary
When writing a buildstream.conf file, i missed an indentation.
Running bst pull with this resulted in an ugly stacktrace
Nexus-x240$ bst pull base/ninja.bst                                                                                ~/projects/gnome-modulesets[master:77477be,?M]
Traceback (most recent call last):
  File "/home/phillipsmyth/.local/bin/bst", line 8, in <module>
    sys.exit(cli())
  File "/home/phillipsmyth/.local/lib/python3.5/site-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/home/phillipsmyth/projects/buildstream/buildstream/_frontend/cli.py", line 162, in override_main
    standalone_mode=standalone_mode, **extra)
  File "/home/phillipsmyth/.local/lib/python3.5/site-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/home/phillipsmyth/.local/lib/python3.5/site-packages/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/phillipsmyth/.local/lib/python3.5/site-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/phillipsmyth/.local/lib/python3.5/site-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/home/phillipsmyth/.local/lib/python3.5/site-packages/click/decorators.py", line 27, in new_func
    return f(get_current_context().obj, *args, **kwargs)
  File "/home/phillipsmyth/projects/buildstream/buildstream/_frontend/cli.py", line 448, in pull
    with app.initialized(session_name="Pull"):
  File "/usr/lib/python3.5/contextlib.py", line 59, in __enter__
    return next(self.gen)
  File "/home/phillipsmyth/projects/buildstream/buildstream/_frontend/app.py", line 169, in initialized
    self.context.load(config)
  File "/home/phillipsmyth/projects/buildstream/buildstream/_context.py", line 221, in load
    _yaml.node_validate(overrides, ['artifacts', 'options', 'strict', 'default-mirror'])
  File "/home/phillipsmyth/projects/buildstream/buildstream/_yaml.py", line 948, in node_validate
    invalid = next((key for key in node if key not in valid_keys), None)
  File "/home/phillipsmyth/projects/buildstream/buildstream/_yaml.py", line 948, in <genexpr>
    invalid = next((key for key in node if key not in valid_keys), None)
TypeError: unhashable type: 'ChainMap'
zsh: exit 1     bst pull base/ninja.bst

Steps to reproduce
Create a basic buildstream.conf containing
projects:
  gnome:
  artifacts:
    - url: localhost:5003
      push: false

Note that the artifacts line is on the same indentation level as the project name "gnome"
What is the current bug behavior?
A stacktrace is returned
What is the expected correct behavior?
A clean YAML formatting error should be output, ideally with line numbers

BuildStream version affected: /milestone %BuildStream_v1.x

In GitLab by [Gitlab user @cs-shadow] on Nov 8, 2019, 17:24
This issue appears to be fixed now.
I tried running the current latest version of BuildStream with the user config you provided as example, and got a sensible error message back:
Error loading user configuration: /Users/chandan/.config/buildstream.conf [line 2 column 8]: Value of 'gnome' is not of the expected type 'dict'

In GitLab by [Gitlab user @cs-shadow] on Nov 8, 2019, 17:24
closed


Feature/throttle metrics

Add 8 metrics for each of the 4 different throttling methods  exposed by vcgencmd.
Fixes ericlagergren/pi-stats#3

thanks! gonna try this out this weekend.


Consider using FuncSharp for Controllers and failing logic

The code might benefit from clearer implementation (e.g. matching capabilities and more).

https://github.com/MewsSystems/FuncSharp

Decided not to implement, the same showcases can be observed at https://github.com/zhukovdm/exrates.


Build out alerts documentation.

This feels a little repetitive, but I figured it would provide a better example for the build out of some of the other command sets.
I considered adding examples (curl and python) but figured they may be better served in context for specific scenarios... ie: authenticate, wake/loop, command.
I would be glad to build out other pages, I figure I can knock out one or two an evening over the next few weeks.

Thanks, but I've actually already got this document built out locally, I just didn't commit it yet. I'll be working on these sections today, but feel free to fill in any blanks I leave behind.

Good deal, I will review over the next week and issue a pull for anything I find.


OSSM-3802 Implement SMCP.spec.meshConfig.discoverySelectors

https://issues.redhat.com/browse/OSSM-3802
This PR allows us to make discoverySelectors GA

@mayleighnmyers FYI I ran make gen for you and commited the changes to your PR, so be sure to pull them before you continue.

@mayleighnmyers You still need to implement #2 in @jewertow 's comment:

We need validation that will allow to set discoverySelectors only in cluster-wide mode. Look at this PR as reference: https://github.com/maistra/istio-operator/pull/1143.

Please reset to 10f45c7af0b395a0adaef96b0bdd1beccb6b2ad9 and then rebase.

@mayleighnmyers I squashed all the commits and rebased to maistra-2.4, so this PR is now easier to work with.


NameError: name 'model' is not defined

This is not a shap issue. Your variable is undefined. Are you sure you ran the cell above?


Handle a third-party datasets in a similar way across many providers

Right now the Macrostrat web interface has the ability to showcase data from the Paleobiology Database. However, there are many other data providers which we are building integrations with. We should be able to display data from all of them, with some capabilities to link to the geologic framework. This will require:

A standard way of organizing the APIs for features (probably vector tiles with server-side clustering)
A standard format for displaying information in the sidebar so data displays can be added easily
A specification of links (e.g., age, stratigraphic unit) that should be assigned to data to enable filtering capabilities

Once we have the basic framework, it should be relatively easy to add new integrations and communicate what is required for other organizations to provide data in the right formats.

Several features of the PBDB integration are broken in the development version of the website, so these will have to be fixed in order to properly address this.


useServerAction and useTransition #zsa-react

Issue: execute async function never fulfilled when it invoked inside startTransition cb.
In this example I log all statuses into console.
When i invoked execute fn inside startTransition cb isPending (from useTransition) always true and loader never ending...
~console.log:
status idle
START
status pending
status pending

but when i replacing execute with executeFormAction || or use action directly – everything works great...
~console.log:
status idle
START
status pending
status pending
status success
SUCCESS
FINISHED

I need useTransition to handle redirecting process router.push(/blog/${post.slug});...
// Example
export const EditPostForm: RC<IProps> = (props) => {
  const router = useRouter();
  const [isPending, startTransition] = useTransition();
  const { execute, status } = useServerAction(updatePost, {
    onStart: () => {
      console.log('START');
    },
    onSuccess: () => {
      console.log('SUCCESS');
    },
    onError: (error) => {
      console.log('ERROR', error);
    },
    onFinish: () => {
      console.log('FINISHED');
    },
  });

  console.log('status', status);

  return (
    <PostForm
      loading={isPending}
      onSubmit={async (values) => {
        startTransition(async () => {
          const [post] = await execute({ id, values });
          if (!post) return;
          router.push(`/blog/${post.slug}`);
        });
      }}
    />
  );
};

Hi, execute from useServerAction is already wrapped in a startTransition. So this is like a double transition which I think is breaking it.
TLDR: you don't need startTransition and can use the isPending from useServerAction .
export const EditPostForm: RC<IProps> = (props) => {
  const router = useRouter();
  const { execute, status, isPending } = useServerAction(updatePost, {
    onStart: () => {
      console.log('START');
    },
    onSuccess: () => {
      console.log('SUCCESS');
    },
    onError: (error) => {
      console.log('ERROR', error);
    },
    onFinish: () => {
      console.log('FINISHED');
    },
  });

  console.log('status', status);

  return (
    <PostForm
      loading={isPending}
      onSubmit={async (values) => {
        execute({ id, values });
      }}
    />
  );
};

Then I would move router.push(/blog/${post.slug}) to a redirect(/blog/${post.slug}) in your server action so isPending is true until redirect completes.
I have been thinking about introducing an execute without transition but haven't done it yet.

Thnx! Understood, but in my case, this solution does not work correctly when a transition redirection is needed.
  const router = useRouter();
  const [isPending, startTransition] = useTransition();

  <PostForm
    loading={isPending}
    onSubmit={async (values) => {
      startTransition(async () => {
        const [post] = await updatePost({ id, values });
        if (!post) return;
        router.push(`/blog/${post.slug}`); // ← show loader until redirect is done...
      });
    }}
  />

thnx, again...

Hi, happy to help make this work for you. Can you try instead of router.push, using the redirect method inside your server actions?  I think that should work as a transition redirect.


raise EOFError("No valid references for a sentence!") EOFError: No valid references for a sentence!

I'm training an MT LSTM model but keep getting an error during validation after the first epoch. I have no empty lines in validation data and equal number of lines for the source and target. I will appreciate any help in solving this problem.

2021-06-01 07:42:50 | INFO | fairseq_cli.train | begin validation on "valid" subset
/scratch/XXX/fairseq/fairseq/utils.py:368: UserWarning: amp_C fused kernels unavailable, disabling multi_tensor_l2norm; you may get better performance by installing NVIDIA's apex library
warnings.warn(
Traceback (most recent call last):
File "/home/XX/fairseqenv/bin/fairseq-train", line 33, in
sys.exit(load_entry_point('fairseq', 'console_scripts', 'fairseq-train')())
File "/scratch/XXX/fairseq/fairseq_cli/train.py", line 505, in cli_main
distributed_utils.call_main(cfg, main)
File "/scratch/XXX/fairseq/fairseq/distributed/utils.py", line 369, in call_main
main(cfg, **kwargs)
File "/scratch/XXX/fairseq/fairseq_cli/train.py", line 178, in main
valid_losses, should_stop = train(cfg, trainer, task, epoch_itr)
File "/cvmfs/XXX/easybuild/software/2020/avx2/Core/python/3.8.2/lib/python3.8/contextlib.py", line 75, in inner
return func(*args, **kwds)
File "/scratch/XXX/fairseq/fairseq_cli/train.py", line 303, in train
valid_losses, should_stop = validate_and_save(
File "/scratch/XXX/fairseq/fairseq_cli/train.py", line 390, in validate_and_save
valid_losses = validate(cfg, trainer, task, epoch_itr, valid_subsets)
File "/scratch/XXX/fairseq/fairseq_cli/train.py", line 460, in validate
trainer.valid_step(sample)
File "/cvmfs/XXX/easybuild/software/2020/avx2/Core/python/3.8.2/lib/python3.8/contextlib.py", line 75, in inner
return func(*args, **kwds)
File "/scratch/XXX/fairseq/fairseq/trainer.py", line 966, in valid_step
_loss, sample_size, logging_output = self.task.valid_step(
File "/scratch/XXX/fairseq/fairseq/tasks/translation.py", line 385, in valid_step
bleu = self._inference_with_bleu(self.sequence_generator, sample, model)
File "/scratch/XXX/fairseq/fairseq/tasks/translation.py", line 487, in _inference_with_bleu
return sacrebleu.corpus_bleu(hyps, [refs])
File "/home/XXX/fairseqenv/lib/python3.8/site-packages/sacrebleu/compat.py", line 35, in corpus_bleu
return metric.corpus_score(
File "/home/XXX/fairseqenv/lib/python3.8/site-packages/sacrebleu/metrics/bleu.py", line 286, in corpus_score
raise EOFError("No valid references for a sentence!")
EOFError: No valid references for a sentence!

What's your environment?

fairseq Version: master
PyTorch Version:1.8.1
OS: linux
How you installed fairseq: source
Build command you used (if compiling from source):

module load python
virtualenv --no-download newtorch
source newtorch/bin/activate
pip install --no-index torch
pip install --no-index torch torchvision torchtext torchaudio
git clone https://github.com/pytorch/fairseq
cd fairseq
pip install --editable ./

Python version: 3.8
CUDA/cuDNN version:
GPU models and configuration: Tesla V100-SXM2-32GB

Did you find a solution? @fenimi

@fenimi @En-J-A I encountered the same problem. Please kindly check whether blank lines exist in your validation file, especially when you have sacrebleu >= 1.5.0

I really checked many times, there are no blank lines.

@fenimi @En-J-A I encountered the same problem. Please kindly check whether blank lines exist in your validation file, especially when you have sacrebleu >= 1.5.0

I found an empty line at the end of the file in one of the files. Once I removed the empty line, it started working.

"bump"
I really checked many times, there are no blank lines.


[CI] Allow for a ux tag in conventional commits formatting

It's not really a fix to provide a new error message as was done in #187 and some issues are not bugs or features (i.e. #176). It would be good to treat User Experience (UX) as a first class citizen for these cases.
I will add a label for that, however we likely would also like an issue template for it and a conventional commit tag for it, e.g. from the pre-commit:conventional-commits.

Took a look at this and it seems like it's not very trivial and open's up some awkward questions. ux changes are rather vague and could imply a new feature or just a fix, or something that doesn't even warrant a version change on it's own (better error message).
Closing this for now in favour of keeping things simple


feat: update dw-select to v4.9.0

:tada: This PR is included in version 1.6.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Port Dark Theme to ui.frontend.theme.dark format

Is your feature request related to a problem? Please describe.
The Dark Theme needs to be moved to the ui.frontend.theme.xxx format in a discrete FED Maven. module.

@davidjgonzalez i'll pick this up...


Allow operation chains to be run asynchronously

High level design
Create a separate method in the Graph class called "executeJob". This method would generate a 'jobId' (a random id based on the user id, timestamp and a random value) and this value would immediately be returned to the user. Create a new thread and delegate the operation chain to the execute method.
Asynchronous jobs will need to be tracked - so the jobId should be stored along with a job status in a 'Job Tracker' this could be backed various different caches.
An operation should be created to get the details of a job for a given job id.

This will be done as part of gh-721

Merged into develop.

To use this feature see the notes on the wiki.


fix: halt the failover if status extraction has failed

This commit addresses an issue where the failover process would continue even if the operator failed to extract status from the instances, potentially due to network connectivity issues.
The operator now checks if the status has been successfully extracted from the instances before proceeding with the failover. If status extraction fails, the operator logs an error message, halts the current failover attempt, and reschedules another attempt after a delay.
Closes #2144

/test limit=local

/test limit=local

when executing the merge check that the title and commit message is correct

/test


installed flow: support urls with existing query params

Resolves #141

Thanks for merging this and tagging a release so quickly!

Thanks for merging this and tagging a release so quickly!


Introduce MappingIndex for mapping to indexed collection

Right now we only support mapping indexed collections of the entity model as indexed collections in the entity view. For other collection type we already have the concept of remapping. We should support mapping the collection index via @MappingIndex so that we can materialize an indexed collection in the entity view from other relations.
Correlation mappings should also support this. Since the correlationResult more or less models the @Mapping we could either introduce a correlationKeyResult or allow the @MappingIndex on a correlation mapping. @Mobe91 What do you say?

When introducing this, we could actually remove the correlationResult and fetch attributes of the @MappingCorrelated and @MappingCorrelatedSimple. Instead we would rely on the @Mapping for these two attributes which might seem more obvious. Any opinion on this @Mobe91 ?

Since the correlation mappings only got added in 1.2 I'd like to fix this in this version so retargeting for Alpha3 since it should be easy to fix.

We will need to look into allowing Multi-Collection i.e. List<Collection<Target>> or Multi-Maps i.e. Map<Key, Collection<Value>> as part of this as the index can obviously match multiple elements.


Weird behaviour on attempting decimal percentage for PLD

If you attempt to enter a fraction of a percentage say .5, it instantly rounds up to 1 and then once you navigate away it goes to 0.  I tried with 1.5, rounds to 2, then you navigate away and it goes back to 1, so I think there's the pattern.
If we aren't doing fractions lets alert/go red on someone entering a decimal if that is easier to fix, if we're supposed to round it would be cool if it notified the user rounding was happening.  If we are supposed to round then we should stop it subtracting one when leaving the field.
Open to your input @LisaMoore1

@micheal-w-wells Red messaging would be good re. whole number requirement. Same thing for Allowable AUMs for each pasture (that has separate issue)

@micheal-w-wells Red messaging would be good re. whole number requirement. Same thing for Allowable AUMs for each pasture (that has separate issue #560))

Simplest thing to do here was to force whole numbers.

@micheal-w-wells I’m getting the “must be whole number” message when I enter a whole number like 5 or 10. The red and message also appear immediately upon me entering any value rather than on exit field like the other field validations do. Not sure if that is a problem or if it is validating after each keystroke


Fixed #29049 -- Added slicing notation to F expressions.

Ticket: 29049.
Previous PR: #11208
F expressions on string-based fields and arrays can now use standard
python slicing-notation. Added a new class SliceableF that handles
identification of sliceable fields. Step-argument is not supported.

Nick -- thank you so much for your early review. 🙏
I think I've covered all of your points now. It's now holiday time for me, so I'll look at it again with a fresh pair of eyes when I get back in September.

Hmmm, the tests are failing which is interesting as I thought they were passing before 🤔
Anyway, that's good news in a way as in part it is why I took on this ticket, I wanted to start to dip my toes in the water of database issues.
So can I ask for a bit of guidance. How do folk setup their environment for postgres? I tried django-docker-box but have spent hours trying to get it to work (I'll keep going) but wondered if there's and reference material on how to get started?
p.s. I was looking to try and get this workign with Windows / WSL2.

@smithdc1 Thanks for updates :+1: Is it ready for the final review?

I think so.🤞
Just left one comment where I'm not sure how to word.

@smithdc1 Do you have time to keep working on this?

Probably not right now. Happy for someone else to try and get this over the line.

@smithdc1 Thanks :+1: Let's close it for now.


diagm doesn't work

A = OffsetArray(rand(3), -3)
diagm(A)

results in
ERROR: size not supported for arrays with indices (-2:0,); see http://docs.julialang.org/en/latest/devdocs/offset-arrays/
Stacktrace:
 [1] errmsg(::OffsetArrays.OffsetArray{Float64,1,Array{Float64,1}}) at /Users/twan/code/julia/MixedIntegerExperiments/v0.6/OffsetArrays/src/OffsetArrays.jl:48
 [2] diagm at ./linalg/dense.jl:250 [inlined] (repeats 2 times)

on nightly. This should probably be fixed in Base, but I wanted to get your input first.
As for the desired output type of diagm, I guess it should always be
typeof(similar(A, first(indices(A)), first(indices(A))))

?

Thanks for the proposal.
Unfortunately zeros - the important integral part for diagm algorithm is deprecated.
The excerpt from dense.jl is below for reference:
function diagm{T}(v::AbstractVector{T}, k::Integer=0)
    n = length(v) + abs(k)
    A = zeros(T,n,n)
    A[diagind(A,k)] = v
    A
end

Please see https://github.com/alsam/OffsetArrays.jl/pull/12 for more details.

The other important part I think is the indexing. diagind assumes one-indexed arrays, and zeros(T) also produces a one-indexed Array. Shouldn't the indexing of A match that of v?
The current diagm implementation in Base is also a problem for JuMP, where, for T == JuMP.Variable, typeof(zero(T)) == JuMP.AffExpr != JuMP.Variable.
A sketch of something that would solve both problems:
function diagm2{T}(v::AbstractVector{T})
    S = promote_type(T, typeof(zero(T)))
    A = similar(v, S, first(indices(v)), first(indices(v)))
    for i in eachindex(v), j in eachindex(v)
        A[i, j] = i == j ? v[i] : zero(T)
    end
    A
end

with which
using OffsetArrays, JuMP
m = Model()
@variable(m, v[1 : 3])
diagm2(OffsetArray(v, -3))

produces
OffsetArrays.OffsetArray{JuMP.GenericAffExpr{Float64,JuMP.Variable},2,Array{JuMP.GenericAffExpr{Float64,JuMP.Variable},2}} with indices -2:0×-2:0:
 v[1]  0     0
 0     v[2]  0
 0     0     v[3]

Problems of course are that k == 0 is assumed, and that things could probably be improved by linearly indexing into A.
That brings up a different question: what should indices(A) be if k != 0?

That improved diagm would be a great contribution to Base, by all means please submit it.

That brings up a different question: what should indices(A) be if k != 0?

Seems like one might want an interface diagm(v, Δrow, Δcol). But for diagm(v, k), I would follow the rule that, if you snipped out a matrix that would be equal in value to diagm(v), that it should have the same indices. So for your example above, diagm(v, 0) would be a -2:0x-2:0 matrix, diagm(v, 1) would be a -2:1x-3:0 matrix, and diagm(v, -1) would be a -3:0x-2:1 matrix.

diagm(v, 1) would be a -2:1x-3:0 matrix, and diagm(v, -1) would be a -3:0x-2:1 matrix

Interesting. That does seem hard to make consistent with the current behavior for regular Arrays though, where map(first, indices(A)) will be (1, 1) no matter what k is. Also, I think one of the main applications of OffsetArrays is having all arrays you ever have to deal with be zero-based, so changing the start of the range would probably be quite surprising for users.
Another option is to change the last index for each dimension, so -2:1x-2:1 for both diagm(v, 1) and diagm(v, -1). That may be a little bit harder to implement generically in Base (but not that much harder).

Cross-ref https://github.com/JuliaLang/julia/pull/24047: I don't think we can call similar since we will now allow more than just one vector as input. Perhaps the solution to this issue is to define a method diagm(::Pair{<:OffsetVector,<:Integer}...)) in OffsetArrays.jl instead?

The specific example listed in the OP seems to work now
julia> A = OffsetArray(rand(3), -3)
3-element OffsetArray(::Array{Float64,1}, -2:0) with eltype Float64 with indices -2:0:
 0.5009784688952947
 0.09987117852205074
 0.6784469095270629

julia> diagm(A)
3×3 Array{Float64,2}:
 0.500978  0.0        0.0
 0.0       0.0998712  0.0
 0.0       0.0        0.678447

Closing as old. Please reopen if further discussion on this is necessary.


Internal Snapserver problems between b0 and b5

What version of Music Assistant has the issue?
2.1.0b5
What version of the Home Assistant Integration have you got installed?
N/A
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
When adding Snapcast Player Provider in b5, or when adding it in b0 and then upgrading to b5, I get duplicate player entries.
How to reproduce
Repro 1

Clean install / clean backing storage
Add snapcast Player Provider in b0
upgrade to b5

Repro 2

Clean install / clean backing storage
Add snapcast Player Provider in b5
(screenshot above does not apply to Repro 2)

Music Providers
N/A
Player Providers
Snapcast (internal)
Full log output
mass.log
Additional information
N/A
What version of Home Assistant Core are your running
N/A
What type of installation are you running?
Home Assistant Container
On what type of hardware are you running?
Alternative

@SantiagoSotoC

Fix here

First case, the ids changed, it has been discussed several times
The second case has already been discussed and I launched the solution
Hopefully for the next beta it will be fixed


Try out ROS2 Ignition bridge

https://github.com/ignitionrobotics/ros_ign/tree/ros2
https://ignitionrobotics.org/docs/dome/ros2_integration

Use of bridge is pretty self-explanatory
ros2 run ros_ign_bridge parameter_bridge /TOPIC@ROS_MSG<DIRECTION>IGN_MSG

Substitute <DIRECTION>:

@ is a bidirectional bridge.
[ is a bridge from Ignition to ROS.
] is a bridge from ROS to Ignition.

See https://github.com/ignitionrobotics/ros_ign/tree/ros2/ros_ign_bridge for message types
Transport of images and point clouds is pretty demanding - opened new issue https://github.com/AndrejOrsula/DRL_GPC/issues/18 to address this


update minio-js test run as per the new ts workflow

PR to adopt  minio-js ts workflow based release
Note: this PR uses the minio-js master branch for now , It will be updated once minio-js is released
Testing /Verification:
Diff to run only minio-js tests

diff --git a/mint.sh b/mint.sh
index 04f213b..928db2d 100755
--- a/mint.sh
+++ b/mint.sh
@@ -165,6 +165,10 @@ function main() {
                run_list=("${run_list[@]}" "$TESTS_DIR/$sdk")
        done

+  run_list=(/mint/run/core/minio-js)
+  # /mint/run/core/minio-js
+  echo "RUN List ${run_list[*]}"
+
        count="${#run_list[@]}"
        i=0
        for sdk_dir in "${run_list[@]}"; do
diff --git a/release.sh b/release.sh
index 0268d71..f9839d9 100755
--- a/release.sh
+++ b/release.sh
@@ -24,9 +24,10 @@ export WGET="wget --quiet --no-check-certificate"
 "${MINT_ROOT_DIR}"/preinstall.sh

 # install mint app packages
-for pkg in "$MINT_ROOT_DIR/build"/*/install.sh; do
-       echo "Running $pkg"
-       $pkg
-done
+#for pkg in (); do
+#      echo "Running $pkg"
+#      $pkg
+#done
+"${MINT_ROOT_DIR}"/build/minio-js/install.sh
 "${MINT_ROOT_DIR}"/postinstall.sh

Build and run the tests

## Start MinIO Server
CI=true  MINIO_ROOT_USER=minio MINIO_ROOT_PASSWORD=minio123 minio server /tmp/site1{1...4}  --address ":22000" --console-address ":9021"

# Sample Build and run of the tests
podman image prune && podman container prune  && podman build -t minio/mint . -f Dockerfile && podman run -e "SERVER_ENDPOINT=<IP_ADDRESS>:22000" -e "ACCESS_KEY=minio" -e "SECRET_KEY=minio123" -e "ENABLE_HTTPS=0" -e "ENABLE_VIRTUAL_STYLE=0" minio/mint

# Run Result
SERVER_ENDPOINT:      <IP_ADDRESS>:22000
ACCESS_KEY:           minio
SECRET_KEY:           ***REDACTED***
ENABLE_HTTPS:         0
SERVER_REGION:        us-east-1
MINT_DATA_DIR:        /mint/data
MINT_MODE:            core
ENABLE_VIRTUAL_STYLE: 0
RUN_ON_FAIL:          0

To get logs, run 'docker cp :/mint/log /tmp/mint-logs'

RUN List /mint/run/core/minio-js
(1/1) Running minio-js tests ... done in 51 seconds

All tests ran successfully

Note: this PR uses the minio-js master branch for now , It will be updated once minio-js is released

should we make a new release? @prakashsvmx

@prakashsvmx please update the PR minio-js is released.

Thank you @harshavardhana .
I have updated to test the latest release.
Using minio-js RELEASE 7.1.1
....

Running minio-js tests ... done in 50 seconds

All tests ran successfully

Sorry didn't notice this PR early.
There is no need to copy .mocharc.js and babel-register.js, also no need to copy dependencies and devDependencies, we should just use these configs from source.
install deps with npm i and run test with npm run test from minio/minio-js directly.


Formatted Swift Guide Markdown

It now follows the markdown formatting rules which makes it easier to read un-rendered along with making it easier to format when rendering.

Guidelines

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

Moved branches:
#28256


Add thatmlopsguy.github.io

This PR is:

[x] Adding a new domain
[ ] Updating existing domain size
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (512kb.club site)
[ ] Other not listed

[x] I used the uncompressed size of the site
[x] I have included a link to the Cloudflare report
[x] This site is not an ultra minimal site
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ section, particularly the two red items around minimal pages and inappropriate content and I attest that this site is neither of these things.

[x] Check to confirm

- domain: thatmlopsguy.github.io
  url: https://thatmlopsguy.github.io/
  size: 165.9
  last_checked: 2024-07-01

Cloudflare Report: https://radar.cloudflare.com/scan/7cc9e1ed-1692-4451-9c1e-dd416131b3d7/summary

Thanks!


Black line at the bottom of image

Images that are not cropped show a black line at the bottom

Sometimes occurs, probably depending on image height, some sort of rounding error.

Not witnessed anymore since extensive refactoring.


[Chart] Enable zoom bar

Summary
We want to use the zoom bar that Carbon Charts is building.  We have several charts that originally contained zoom bar designs that we de-scoped because Carbon Charts was working on a zoom bar.  It appears in their storybook now, and we'd like to incorporate it as soon as possible so that we can use it in our Health and Predict charts
Storybook: https://carbon-design-system.github.io/carbon-charts/?path=/story/zoom-bar-alpha--stacked-area-time-series-zoom-bar-enabled
Additional context
We've had several user requests for a similar function, and I expect other teams will want to use this as well.
Specific timeline issues / requests
Do you want this work within a specific time period? Is it related to an
upcoming release?
NB: The core contributors will try to work with your timeline, but it's not
guaranteed. The earlier you make a request in advance of a desired delivery
date, the better!
Available extra resources
What resources do you have to assist this effort?
Carbon add-ons for Watson IoT is a collaborative system. We encourage teams to build components and submit them for integration.

The zoombar is already available for TimeSeriesCard and BarChartCard thanks to @sstone2423!
#1454 #1467 #1474 #1473
@KarenGski should we scope this issue to other additional chart types, or are we safe to close here?


clientId and clientSecret are required for http basic auth

Hi Micha, testing the code (thanks for sharing) i found that error appeared when redirect to application. the information displayed on debug:

clientId and clientSecret are required for http basic auth

in vendor/league/oauth2-client/src/OptionProvider/HttpBasicAuthOptionProvider.php
code:
public function getAccessTokenOptions($method, array $params)
    {
        if (empty($params['client_id']) || empty($params['client_secret'])) {
            throw new InvalidArgumentException('clientId and clientSecret are required for http basic auth');
        }

I checked and all dependencies are installed.. thanks in advance

Hi Mr price,
Have you created the .env file and put in your eBay credentials?
https://developer.ebay.com/api-docs/static/oauth-credentials.html

Hi Micha, yes

I created the variables in .env.
Create Controller.
View Code correctly placed at welcome.blade
Routes modified at eBay sandbox.

At this moment accessing welcome.blade.php displays the ebayauthlogin, I press-> log into developer area -> displays "grant authorization area" perfectly and then a code is retrieved (as I can see on the url).
url=> https://www.domain.xss/?code=v^1.1%23i^1%23p^3%23r^1%23I^3%23f^0%23t^Ul41XzA6NDMzNTZEQ0Q1NkYyMkE2OEUxOTAzMThGRDc3NzhFODFfMF8xI0VeMTI4NA%3D%3D&expires_in=299
But in that moment the error appears. I dont understand why

full log
[2019-07-07 22:48:30] local.ERROR: clientId and clientSecret are required for http basic auth {"exception":"[object] (InvalidArgumentException(code: 0): clientId and clientSecret are required for http basic auth at /Applications/MAMP/htdocs/fiverr/vendor/league/oauth2-client/src/OptionProvider/HttpBasicAuthOptionProvider.php:31)
[stacktrace]
#0 /Applications/MAMP/htdocs/fiverr/vendor/league/oauth2-client/src/Provider/AbstractProvider.php(512): League\\OAuth2\\Client\\OptionProvider\\HttpBasicAuthOptionProvider->getAccessTokenOptions('POST', Array)
#1 /Applications/MAMP/htdocs/fiverr/vendor/league/oauth2-client/src/Provider/AbstractProvider.php(536): League\\OAuth2\\Client\\Provider\\AbstractProvider->getAccessTokenRequest(Array)
#2 /Applications/MAMP/htdocs/fiverr/app/Http/Controllers/ebayOauthLogin.php(158): League\\OAuth2\\Client\\Provider\\AbstractProvider->getAccessToken(Object(League\\OAuth2\\Client\\Grant\\AuthorizationCode), Array)
#3 [internal function]: App\\Http\\Controllers\\ebayOauthLogin->welcome(Object(Illuminate\\Http\\Request))
#4 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(54): call_user_func_array(Array, Array)
#5 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(45): Illuminate\\Routing\\Controller->callAction('welcome', Array)
#6 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Route.php(219): Illuminate\\Routing\\ControllerDispatcher->dispatch(Object(Illuminate\\Routing\\Route), Object(App\\Http\\Controllers\\ebayOauthLogin), 'welcome')
#7 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Route.php(176): Illuminate\\Routing\\Route->runController()
#8 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Router.php(682): Illuminate\\Routing\\Route->run()
#9 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(30): Illuminate\\Routing\\Router->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
#10 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php(41): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
#11 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\\Routing\\Middleware\\SubstituteBindings->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#12 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#13 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/VerifyCsrfToken.php(75): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
#14 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\\Foundation\\Http\\Middleware\\VerifyCsrfToken->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#15 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#16 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/View/Middleware/ShareErrorsFromSession.php(49): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
#17 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\\View\\Middleware\\ShareErrorsFromSession->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#18 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#19 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(63): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
#20 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\\Session\\Middleware\\StartSession->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#21 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#22 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php(37): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
#23 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\\Cookie\\Middleware\\AddQueuedCookiesToResponse->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#24 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#25 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php(66): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
#26 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\\Cookie\\Middleware\\EncryptCookies->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#27 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#28 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(104): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
#29 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Router.php(684): Illuminate\\Pipeline\\Pipeline->then(Object(Closure))
#30 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Router.php(659): Illuminate\\Routing\\Router->runRouteWithinStack(Object(Illuminate\\Routing\\Route), Object(Illuminate\\Http\\Request))
#31 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Router.php(625): Illuminate\\Routing\\Router->runRoute(Object(Illuminate\\Http\\Request), Object(Illuminate\\Routing\\Route))
#32 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Router.php(614): Illuminate\\Routing\\Router->dispatchToRoute(Object(Illuminate\\Http\\Request))
#33 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(176): Illuminate\\Routing\\Router->dispatch(Object(Illuminate\\Http\\Request))
#34 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(30): Illuminate\\Foundation\\Http\\Kernel->Illuminate\\Foundation\\Http\\{closure}(Object(Illuminate\\Http\\Request))
#35 /Applications/MAMP/htdocs/fiverr/vendor/fideloper/proxy/src/TrustProxies.php(57): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
#36 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Fideloper\\Proxy\\TrustProxies->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#37 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#38 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(31): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
#39 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#40 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#41 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(31): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
#42 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#43 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#44 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php(27): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
#45 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\\Foundation\\Http\\Middleware\\ValidatePostSize->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#46 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#47 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(62): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
#48 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\\Foundation\\Http\\Middleware\\CheckForMaintenanceMode->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#49 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#50 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(104): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
#51 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(151): Illuminate\\Pipeline\\Pipeline->then(Object(Closure))
#52 /Applications/MAMP/htdocs/fiverr/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(116): Illuminate\\Foundation\\Http\\Kernel->sendRequestThroughRouter(Object(Illuminate\\Http\\Request))
#53 /Applications/MAMP/htdocs/fiverr/public/index.php(55): Illuminate\\Foundation\\Http\\Kernel->handle(Object(Illuminate\\Http\\Request))
#54 {main}
"}

please goto vendor/league/oauth2-client/src/Provider/AbstractProvider.php and put a dump here:

also add a dump here:
app/Http/Controllers/ebayOauthLogin.php

let´s see what you have. in case the params are filled, please deface the security related stuff.

Thanky you for your help. I placed the code but no change. below you will
see the type of error I receive.
[image: Captura de pantalla 2019-07-08 a las 1.38.17 p.m..png]
Sebastián
El lun., 8 jul. 2019 a las 6:00, Michael Bladowski (<
<EMAIL_ADDRESS>escribió:

please goto vendor/league/oauth2-client/src/Provider/AbstractProvider.php
and put a dump here:
[image: image]
https://user-images.githubusercontent.com/3524595/60797135-0347f500-a16f-11e9-9e26-c007e1eafeef.png
also add a dump here:
app/Http/Controllers/ebayOauthLogin.php
[image: image]
https://user-images.githubusercontent.com/3524595/60797462-91bc7680-a16f-11e9-9b9c-0c97978bb8d2.png
let´s see what you have. in case the params are filled, please deface the
security related stuff.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/michabbb/ebay-oauth-playground/issues/1?email_source=notifications&email_token=AADA26Q6EYNDL456X5T3KV3P6L64JA5CNFSM4H6WREL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZMOGZY#issuecomment-509141863,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADA26WFH6LNVPZULVWY7VTP6L64JANCNFSM4H6WRELQ
.

Thank you for your help. I placed the code but no change. below you will
see the type of error I receive.

Sebastián

so the throw seems to block the regular output (of the dump) you should replace this "throw" with a simple exit, then we hopefully should see the dumps.

Excellent, now I have information. I made an error passing values from CERT_ID consequently ClientSecret was empty.
Sir I have a bounty opened at https://stackoverflow.com/questions/56827786/ebay-dts-for-php-generate-usertoken-failed-authnauth-work-ok for 50 points and honestly you code solved all my doubts. please an brief answer referencing your code so I can grant the bounty to you!.
thank you so much for you code and your dedication answering me. Brgds

.

glad to help. thanks for the notice about the bounty, but davids SDK is dead over a year now. people do not realize, they can easily create their own SDK, because there exists so great code generators:
see my example: https://github.com/michabbb/php-ebay-sdk

thank you @michabbb I will check your code. Some of us are not so skilled in programming consequently we rely heavily on other people SDK's... and in my experience oauth + ebay increase its complexity when you work with users tokens.
thank you so much!!

@price2b in case you need prof help, feel free to contact me anytime 😏

Of Course!, thank you
Sebastián Herrera
El lun., 8 jul. 2019 a las 14:23, Michael Bladowski (<
<EMAIL_ADDRESS>escribió:

@price2b https://github.com/price2b in case you need prof help, feel
free to contact me anytime 😏
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/michabbb/ebay-oauth-playground/issues/1?email_source=notifications&email_token=AADA26W4WXYGRN3ZBGTCZTDP6NZZXA5CNFSM4H6WREL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZNY7WI#issuecomment-509317081,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADA26V33PUDHYP27P6ZMC3P6NZZXANCNFSM4H6WRELQ
.


Error when running PSPNet with PascalVOC

Hello,
When I run python train.py --arch pspnet --dataset pascal --n_epoch 500 --batch_size 8
I get the following error.
Tested with PyTorch 0.4.1 on Linux.
Traceback (most recent call last):
  File "train.py", line 162, in <module>
    train(args)
  File "train.py", line 92, in train
    loss.backward()
  File "/home/flr/miniconda3/lib/python3.6/site-packages/torch/tensor.py", line 93, in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph)
  File "/home/flr/miniconda3/lib/python3.6/site-packages/torch/autograd/__init__.py", line 90, in backward
    allow_unreachable=True)  # allow_unreachable flag
RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation

I suspect it might be from the cross_entropy2d in ptsemseg/loss.py, but I am not sure. Please let me know if you need more details.

Hi, @flriancu .
You can check #96 .

@adam9500370 Thanks, solved. Any idea if the align_corners being turned off by default in 0.4 has any influence for the results (see comment in #96)?

I think you still need to set align_corners=True. (see comment in #81)


Support the Popover api

Please support the new Popover api: https://developer.mozilla.org/en-US/docs/Web/API/Popover_API
With this, we can achieve dropdown menu, modal without writting js

Hey @xcaptain,
We will consider it, but the dropdowns that we have also calculate the width and height of the container.
This means that it could still be more advantageous to use our current API as opposed to the new HTML Popover.
Cheers,
Zoltan


feat: update email templates

This PR...
Changes

Fixes

Checklist

[x] tested locally
[ ] added new dependencies
[ ] updated the Swagger API docs
[ ] updated the Postman collection
[ ] added a test
[ ] linter passes
[ ] format check passes

Fixes #

Thank you so much for updating the templates 🎉🥳


Separate CDI logic

Find a nice way to separate CDI logic from the actual classes (Using Producers may be a solution).
It would:

Make our services CDI free just simple classes (without proxy or injection concerns)
Keep the CDI logic in one place
Simpler way to change CDI logic/framework if ever needed

I don't think I agree we should make our services CDI free, on the contrary, they should embrace the CDI annotations and @Inject as many dependencies as needed.

Now if you're talking about a specific module (base/ for example) then I agree that it shouldn't use CDI annotations, but that is a special case and doesn't apply to other modules

I do agree somewhat with @ia3andy here. Personally I'd use CDI only for injection in the "first level" of code. I'm not a great fan of all that "automagical wiring", I'd rather be explicit of who passes what to whom.

Personally I'd use CDI only for injection in the "first level" of code.

What is a "first level" of code? Can you give an example?

I'm not a great fan of all that "automagical wiring", I'd rather be explicit of who passes what to whom

You prefer ServiceLookups and Factories around the code instead of having an injected object? That looks like anti-patterns to me

What is a "first level" of code? Can you give an example?

Web endpoints for example. Where requests come in. The stuff that initiates computation.

You prefer ServiceLookups and Factories around the code instead of having an injected object?

No, I prefer having things explicit. I don't like it at all that I see an @Inject Foo and then have to go looking around the code for some place where that Foo might come from. The moment you start adding selectors it gets even worse.

That looks like anti-patterns to me

What? So code that doesn't use CDI is now an anti-pattern? All those decades that CDI didn't even exist we've been writing bad code? ;)

Btw, I don't mind CDI at all. What I don't like is a) the proliferation of CDI annotations because to me that's doing exactly what CDI was meant to prevent: putting decisions about what and how to wire things together inside the code. IMO code that gets used in CDI should look exactly the same as if done when not using CDI. And b) the automagical part of it. But I actually quite like Guice's way of being able to wire things together in code.
I also understand that this isn't going away any time soon so I accept that people want to do this. And I also won't be campaigning to get rid of it in our code. But you also won't see me writing much of that kind of code.

@gastaldi @quintesse
IMO:
At the end using producers is really close to using @inject on constructors:

it just separates the injection logic from the class itself
it lets you put this injection logic somewhere else (only in module web for example).
It gives you a way to have different injection logic depending on the module you are using it

I don't think that separating injection logic from the classes means not embracing CDI concepts.

I don't think that separating injection logic from the classes means not embracing CDI concepts.

@quintesse it's what I meant there too like Guice exactly..

Dependencies of a Service Classe are using constructors instead of private attributes. Closing this


what's the size of a single record?

i am tring to understand how much bandwise would i need for start using this app,
what's the size of a standard single voice record (lets say of 15 seconds) that we will get from users?

The audio file isn't transferred to you. It is sent directly to the browser vendor. The browser then has access to the transcript.
I suggest reading up on the Speech Recognition API in the browser.

so it does'nt make any use of Google's speech recognition service right?

No.


Error in Ui-select integration with formly

Hello, there is an error in ui-select integration with formly. You have that error in a console shown in your example as well.
http://angular-formly.com/#/example/integrations/ui-select
Error: [$compile:ctreq] http://errors.angularjs.org/1.4.4/$compile/ctreq?p0=select&p1=ngOptions
Thanks & Regards
Martin

Looks like ui-select isn't ready for angular 1.4.x yet. I've downgraded that example's angular to 1.3.19 and it's working great. Thanks for letting me know!

@kentcdodds @Bedo81 This is actually a problem with the example.  ui-select works with angular-1.4 and I currently use it with my project running 1.4.0.  The issue with the example is that the ui-select formly type is defined as extending the formly-bootstrap-templates select type which defines a mapping for ngOptions in ngModelAttrs.  ngOptions is not a valid directive as of 1.4 on anything other than a <select> element.  ui-select does not need that attribute so I just made it not extend select.  Only draw back is that it doesn't inherit the apiCheck.
Ex. http://jsbin.com/kohowax/2/edit?html,js,output

Example code don't work with angular 1.4.8, replace
app.run(function (formlyConfig) {
    formlyConfig.extras.removeChromeAutoComplete = true;
    formlyConfig.setType({
        name: 'ui-select',
        extends: 'select',
        template: ''
    });
});

with
app.config(['formlyConfigProvider', function (formlyConfigProvider) {
    formlyConfigProvider.extras.removeChromeAutoComplete = true;
    formlyConfigProvider.setType({
        name: 'ui-select',
        extends: 'select',
        template: ''
    });
}]);


GH-17288/MM-34367: TypeScript conversion

Converted jsx tests to tsx

Summary
I've found the component files already converted to TypeScript, only the tests were in jsx so I switched them to jsx.
Once I've changed the extension the type check game me 7 errors, 6 came from the instances of the component Reaction declared for the tests and were caused by the absence of many mandatory fields in the hardcoded testing props declared at line 22 (baseProps) while the other came from the method call wrapper.instance().loadMissingProfiles() at line 100, the type inferred from the variable wrapper declared at line 99 ShallowWrapper<any, Readonly<{}>, React.Component<{}, {}, any>> seems to have an instance method which doesn't return an object which exposes the loadMissingProfiles.
Putting an any at line 22 and 99 seems to fix the type check errors but maybe there are better solutions or I can do something else to fit better with the rest of the codebase.
Ticket Link
https://github.com/mattermost/mattermost-server/issues/17288
Once I've get a feedback I can close even the #17287 which is really similar.

Hello @EmiSan1998,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @jfrerich @emilyacook

Hey @EmiSan1998, let us know if you have any questions about the above comments :)

completed i https://github.com/mattermost/mattermost-webapp/pull/9903


HIVE-24559: Fix some spelling issues

What changes were proposed in this pull request?

This pull request fixes some minor typos.
Why are the changes needed?

This pull request fixes some minor typos.
Does this PR introduce any user-facing change?

No
How was this patch tested?

No need to be tested.

I force pushed to fix more spelling mistakes.

Just some typo fixes in some comments, there is no need to pass all the checks. Can anyone please merge this?

Hey @vihangk1, could you please merge this? Just some typo issues~~ Thanks a lot.

The patch does not have any code changes. Merging the patch. Thanks @rickyma for the patch.


global: $ref resolvers extras

During the implementation of resolvers several issues popped up.

[ ] Deprecate JSONSCHEMAS_HOST, it is a dummy domain and it is used from the resolvers to avoid url conflicts with rest api. $ref properties don't work with relative urls and currently we don't have access to request to get our current host.
[ ] There is an ongoing invenio-records-rest issue with the PID being part of the schema for create and update.
[ ] Since CDS will wrap ILS our resolvers have to be overridable.

closing as stale


Cruise Control Not Recreated On Deletion

Description
I updated the Helm Chart to Latest and KOperator to 0.24.1 and was having some issue with the dpeloyment/upgrade
During this process Cruise Control Was deleted, however I cant seem to get the operator to recreate it.
I see there is an issue here: https://github.com/banzaicloud/koperator/issues/740 but it says that it started working again, but Im on the latest version and have this issue
Expected Behavior
Cruise Control Should be Recreated
Actual Behavior
Cruise Control Does not exist and I keep getting errors:
{
   "level":"error",
   "ts":"2023-06-06T07:15:49.909Z",
   "msg":"failed to get unavailable brokers at rebalance",
   "controller":"CruiseControlTask",
   "controllerGroup":"kafka.banzaicloud.io",
   "controllerKind":"KafkaCluster",
   "KafkaCluster":{
      "name":"kafka",
      "namespace":"default"
   },
   "namespace":"default",
   "name":"kafka",
   "reconcileID":"f3a57a35-bb1b-49d7-893f-2751f6937fa4",
   "error":"failed to get list of volumes per broker from Cruise Control: sending HTTP request failed: Get \"http://kafka-cruisecontrol-svc.default.svc.cluster.local:8090/kafkacruisecontrol/kafka_cluster_state?json=true&verbose=true\": dial tcp: lookup kafka-cruisecontrol-svc.default.svc.cluster.local on <IP_ADDRESS>:53: no such host",
   "errorVerbose":"sending HTTP request failed: Get \"http://kafka-cruisecontrol-svc.default.svc.cluster.local:8090/kafkacruisecontrol/kafka_cluster_state?json=true&verbose=true\": dial tcp: lookup kafka-cruisecontrol-svc.default.svc.cluster.local on <IP_ADDRESS>:53: no such host\nfailed to get list of volumes per broker from Cruise Control\ngithub.com/banzaicloud/koperator/controllers.checkBrokerLogDirsAvailability\n\t/workspace/controllers/cruisecontroltask_controller.go:239\ngithub.com/banzaicloud/koperator/controllers.(*CruiseControlTaskReconciler).Reconcile\n\t/workspace/controllers/cruisecontroltask_controller.go:178\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:121\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:320\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:273\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:234\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1594",
   "stacktrace":"github.com/banzaicloud/koperator/controllers.(*CruiseControlTaskReconciler).Reconcile\n\t/workspace/controllers/cruisecontroltask_controller.go:180\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:121\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:320\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:273\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:234"
}

Affected Version
0.24.1
Steps to Reproduce

Fresh Install of Koperator
Delete Cruise Control
Cretae kafkacluster

Checklist

[x] I have read the contributing guidelines
[x] I have verified this does not duplicate an existing issue

I also tried going onto you slack group but it seems you need a Cisco email address :smiling_face_with_tear:

Seems the reason is due to the CC Topic creation:
{
   "level":"info",
   "ts":"2023-06-06T11:12:13.412Z",
   "logger":"webhooks.KafkaTopic",
   "msg":"rejected",
   "name":"kafka-cruise-control-topic",
   "namespace":"default",
   "invalid field(s)":"spec.name: Invalid value: \"__CruiseControlMetrics\": topic \"__CruiseControlMetrics\" already exists on kafka cluster and it is not managed by Koperator,\n\t\t\t\t\tif you want it to be managed by Koperator so you can modify its configurations through a KafkaTopic CR,\n\t\t\t\t\tadd this \"managedBy: koperator\" annotation to this KafkaTopic CR"
}

Okay for anybody that runs into this, there seems to be a race condition, when cruise control Is deleted  and the __CruiseControlMetrics still exists, operator will not recreate the cruise control deployment, the way I handled this was I deleted the topic by running:
kubectl run kafka-topic -it  \
  --image=ghcr.io/banzaicloud/kafka:2.13-3.1.0 \
  --rm=true \
  --restart=Never \
  -- /opt/kafka/bin/kafka-topics.sh --bootstrap-server kafka-headless:29092 --topic __CruiseControlMetrics --delete

This deleted the topic and reconcile logic then created the Cruise Control Deployment, I think the issue arises from a race condition here

Slack:

But i got this link from one of the issues I beleive and the one you provided works without an issue thank you!
I dont have a ton of time at the moment but will swing around next week to see if anybody has picked this up or not and I might give it a crack then

yes it works for me, the other one I got was from a comment from an issue, hence probably why it was not working


Fix/encoding

@hunner @mhaskel @cmurphy could you please review/comment/merge this PR?

What's the rationale for putting this in postgresql::server::initdb instead of, say, postgresql::server::config? Any why make it an elsif with $needs_initdb? Wouldn't there be a case where $needs_initdb was true and also the encoding needed to be fixed?

Discussed at puppet contributors summit, lgtm. Will just wait on TravisCI.

@cmurphy travis fails for 2.7, which imo can be ignored >_>

@cmurphy could you please merge this if it's OK for you also?

@mcanevet the travis errors can be fixed by rebasing against master, where we pinned rspec-core to fix the issue on puppet 2.7/ruby 1.8.7.
@igalic I disagree with ignoring 2.7 errors. We plan to remove support for puppet 2.7 on the next naturally occurring major release, but while we still officially support it we need to keep CI green on it.

@cmurphy Travis still fails, but because of this : https://github.com/puppetlabs/puppetlabs-concat/pull/270 this time...

Ignoring the strict variables failures for now. Thanks!


Cow: Watch jgseeds.com

Cow requests the watch of the watch_keyword jgseeds\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

jgseeds\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Uncaught ReferenceError: admob is not defined

hi i am using ur plugin and it has been working great for me.
However i recently got a bug, i get an js error saying   "Uncaught ReferenceError: admob is not defined " and the line which is getting the error is if(admob)
Let me make it clear that it doesn't happen all the time 99.99% of the time it works..it only happens sometimes.
what i don't understand is that if admob is undefined then it should evaluate to false and go to the else but it shows the error.
similar issue is here but it was asked for the incorrect plugin:
https://github.com/floatinghotpot/cordova-plugin-admob/issues/177
   function initAds() {
          if (admob) {
            var adPublisherIds = {
              ios : {
                banner : "ca-app-pub-xxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxx",
                interstitial : "ca-app-pub-xxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxx"
              },
              android : {
                banner : "ca-app-pub-xxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxx",
                interstitial : "ca-app-pub-xxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxx"
              }
            };

            var admobid = (/(android)/i.test(navigator.userAgent)) ? adPublisherIds.android : adPublisherIds.ios;

            admob.setOptions({
              publisherId: admobid.banner,
              interstitialAdId: admobid.interstitial
            });

            registerAdEvents();

          } else {
            alert('AdMobAds plugin not ready');
          }
        }

  initAds();

  // display a banner at startup
  admob.createBannerView();

  // request an interstitial
  admob.requestInterstitialAd();

Kindly let me know when u get around this...thanks

Hi @prantikv, thanks for the comments.
I will update the documentation (this is just a workaround, is not solving the error when it appears) replacing if (admob) by if (window.admob):
   function initAds() {
          if (window.admob) {
            var adPublisherIds = {
              ios : {
                banner : "ca-app-pub-xxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxx",
                interstitial : "ca-app-pub-xxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxx"
              },
              android : {
                banner : "ca-app-pub-xxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxx",
                interstitial : "ca-app-pub-xxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxx"
              }
            };

            var admobid = (/(android)/i.test(navigator.userAgent)) ? adPublisherIds.android : adPublisherIds.ios;

            admob.setOptions({
              publisherId: admobid.banner,
              interstitialAdId: admobid.interstitial
            });

            registerAdEvents();

          } else {
            alert('AdMobAds plugin not ready');
          }
        }

  initAds();

  if (window.admob) {
    // display a banner at startup
    admob.createBannerView();

    // request an interstitial
    admob.requestInterstitialAd();
  }

Normally this error can happen because of different reasons:

The app is running in an emulator, not in a real device: plugins don't work in emulators (yet)
There is another plugin that is breaking other plugins (really strange)
Not all the dependencies needed by the plugin are ready and updated

I would recommend:

Get the list of installed plugins cordova plugin ls
Remove every plugin with cordova plugin rm ...
Remove every platform with cordova platform rm ios (android, wp8, etc...)
Delete all cached plugins from /Users//.plugman/cache/*
Add all plugins again
Add all platforms again

Hi @prantikv,
Please, could you confirm that this is not repeating anymore? Thanks.

yes thanks now it has been solved..

I am using ionic and tried to your plugin. However it fails to resolve window.AdMob. Any suggestions what could be going on?
Thanks
--Narasimha

It seems the variable name is not correct, should be window.admob lowercase. If still not working, I suggest to clean your plugin cache, remove the plugin and install it again:
cordova plugin rm com.admob.google
cordova plugin rm cordova-admob
rm -rf /Users/<your user>/.plugman/cache
rm -rf /Users/<your user>/.npm/cordova-*
cordova plugin add cordova-admob

After doing everything, your code isn't working at all, i have used typescript (becase i don't why you have not written it in typecript, angular 2 and ionic 2 is best compatible with typescript, still)

EXCEPTION: Error: Uncaught (in promise): ReferenceError: AdMob is not definedBrowserDomAdapter.logError @ browser_adapter.js:77BrowserDomAdapter.logGroup @ browser_adapter.js:87ExceptionHandler.call @ exception_handler.js:57(anonymous function) @ application_ref.js:265schedulerFn @ async.js:123SafeSubscriber.__tryOrUnsub @ Subscriber.js:225SafeSubscriber.next @ Subscriber.js:174Subscriber._next @ Subscriber.js:124Subscriber.next @ Subscriber.js:88Subject._finalNext @ Subject.js:128Subject._next @ Subject.js:120Subject.next @ Subject.js:77EventEmitter.emit @ async.js:112NgZone._zoneImpl.ng_zone_impl_1.NgZoneImpl.onError @ ng_zone.js:120NgZoneImpl.inner.inner.fork.onHandleError @ ng_zone_impl.js:66ZoneDelegate.handleError @ zone.js:327Zone.runGuarded @ zone.js:233_loop_1 @ zone.js:487drainMicroTaskQueue @ zone.js:494ZoneTask.invoke @ zone.js:426
browser_adapter.js:77 STACKTRACE:BrowserDomAdapter.logError @ browser_adapter.js:77ExceptionHandler.call @ exception_handler.js:59(anonymous function) @ application_ref.js:265schedulerFn @ async.js:123SafeSubscriber.__tryOrUnsub @ Subscriber.js:225SafeSubscriber.next @ Subscriber.js:174Subscriber._next @ Subscriber.js:124Subscriber.next @ Subscriber.js:88Subject._finalNext @ Subject.js:128Subject._next @ Subject.js:120Subject.next @ Subject.js:77EventEmitter.emit @ async.js:112NgZone._zoneImpl.ng_zone_impl_1.NgZoneImpl.onError @ ng_zone.js:120NgZoneImpl.inner.inner.fork.onHandleError @ ng_zone_impl.js:66ZoneDelegate.handleError @ zone.js:327Zone.runGuarded @ zone.js:233_loop_1 @ zone.js:487drainMicroTaskQueue @ zone.js:494ZoneTask.invoke @ zone.js:426
browser_adapter.js:77 Error: Uncaught (in promise): ReferenceError: AdMob is not defined
at resolvePromise (zone.js:538)
at zone.js:574
at ZoneDelegate.invokeTask (zone.js:356)
at Object.NgZoneImpl.inner.inner.fork.onInvokeTask (ng_zone_impl.js:36)
at ZoneDelegate.invokeTask (zone.js:355)
at Zone.runTask (zone.js:256)
at drainMicroTaskQueue (zone.js:474)
at HTMLButtonElement.ZoneTask.invoke (zone.js:426)BrowserDomAdapter.logError @ browser_adapter.js:77ExceptionHandler.call @ exception_handler.js:60(anonymous function) @ application_ref.js:265schedulerFn @ async.js:123SafeSubscriber.__tryOrUnsub @ Subscriber.js:225SafeSubscriber.next @ Subscriber.js:174Subscriber._next @ Subscriber.js:124Subscriber.next @ Subscriber.js:88Subject._finalNext @ Subject.js:128Subject._next @ Subject.js:120Subject.next @ Subject.js:77EventEmitter.emit @ async.js:112NgZone._zoneImpl.ng_zone_impl_1.NgZoneImpl.onError @ ng_zone.js:120NgZoneImpl.inner.inner.fork.onHandleError @ ng_zone_impl.js:66ZoneDelegate.handleError @ zone.js:327Zone.runGuarded @ zone.js:233_loop_1 @ zone.js:487drainMicroTaskQueue @ zone.js:494ZoneTask.invoke @ zone.js:426
zone.js:461 Unhandled Promise rejection: AdMob is not defined ; Zone: angular ; Task: Promise.then ; Value: ReferenceError: AdMob is not defined(…)consoleError @ zone.js:461_loop_1 @ zone.js:490drainMicroTaskQueue @ zone.js:494ZoneTask.invoke @ zone.js:426
zone.js:463 Error: Uncaught (in promise): ReferenceError: AdMob is not defined(…)consoleError @ zone.js:463_loop_1 @ zone.js:490drainMicroTaskQueue @ zone.js:494ZoneTask.invoke @ zone.js:426

I have done everything you told me, my code is that i have written in page1.ts (using sidemenu template)
`import { Component } from '@angular/core';
import { NavController, Platform } from 'ionic-angular';
import {StatusBar} from 'ionic-native';
declare var AdMob: any;
@Component({
templateUrl: 'build/pages/page1/page1.html'
})
export class Page1 {
private admobId: any;
constructor(private navController: NavController, private platform: Platform) {
this.platform = platform;
if(/(android)/i.test(navigator.userAgent)) {
this.admobId = {
banner: 'ca-app-pub-5724383886840960/6005198717 ',
interstitial: 'ca-app-pub-jjj/kkk'
};
} else if(/(ipod|iphone|ipad)/i.test(navigator.userAgent)) {
this.admobId = {
banner: 'ca-app-pub-5724383886840960/6005198717 ',
interstitial: 'ca-app-pub-ppp/zzz'
};
}
} createBanner() {
this.platform.ready().then(() => {
if(AdMob) {
AdMob.createBanner({
adId: this.admobId.banner,
autoShow: false
});
}
});
}
showInterstitial() {
    this.platform.ready().then(() => {
        if(AdMob) {
            AdMob.prepareInterstitial({
                adId: this.admobId.interstitial,
                autoShow: true
            });
        }
    });
}

showBanner(position) {
    this.platform.ready().then(() => {
        if(AdMob) {
            var positionMap = {
                "bottom": AdMob.AD_POSITION.BOTTOM_CENTER,
                "top": AdMob.AD_POSITION.TOP_CENTER
            };
            AdMob.showBanner(positionMap[position.toLowerCase()]);
        }
    });
}

hideBanner(position) {
    this.platform.ready().then(() => {
        if(AdMob) {
            AdMob.hideBanner();
        }
    });
}

}
`

Please try with:
import { Component } from '@angular/core';
import { NavController, Platform } from 'ionic-angular';
import {StatusBar} from 'ionic-native';

declare var admob: any;

@Component({
  templateUrl: 'build/pages/page1/page1.html'
})
export class Page1 {

    private admobId: any;

    constructor(private navController: NavController, private platform: Platform) {
         this.platform = platform;
         if(/(android)/i.test(navigator.userAgent)) {
             this.admobId = {
                 banner: 'ca-app-pub-5724383886840960/6005198717 ',
                 interstitial: 'ca-app-pub-jjj/kkk'
             };
         } else if(/(ipod|iphone|ipad)/i.test(navigator.userAgent)) {
             this.admobId = {
                 banner: 'ca-app-pub-5724383886840960/6005198717 ',
                 interstitial: 'ca-app-pub-ppp/zzz'
             };
         }
    }

    createBanner() {
        this.platform.ready().then(() => {
            if (window.admob) {
                admob.createBanner({
                    adId: this.admobId.banner,
                    autoShow: false
                });
            }
        });
    }

    showInterstitial() {
        this.platform.ready().then(() => {
            if (window.admob) {
                admob.prepareInterstitial({
                    adId: this.admobId.interstitial,
                    autoShow: true
                });
            }
        });
    }

    showBanner(position) {
        this.platform.ready().then(() => {
            if (window.admob) {
                var positionMap = {
                    "bottom": admob.AD_POSITION.BOTTOM_CENTER,
                    "top": admob.AD_POSITION.TOP_CENTER
                };
                admob.showBanner(positionMap[position.toLowerCase()]);
            }
        });
    }

    hideBanner(position) {
        this.platform.ready().then(() => {
            if (window.admob) {
                admob.hideBanner();
            }
        });
    }
}

This is written in js to support angular 1/ionic 1.


Dev mode toggle

I saw this in the README roadmap and would love to see it implemented.
We tried using Overriding Plugin Settings to disable Sentry errors on dev. However, the settings seem to be cached in the database anyways so we are currently manually disabling the Sentry plugin after every pull-down from production.

I've added a new config setting that should solve this.
If you add 'enabled' => false, in your sentry.php config file the plugin won't report errors to Sentry. This can be set per-environment.

(this change is available in the latest release)


Use 'disk' resource in Mesos offers

We haven't been using it because it has not been enforced by the Mesos slave and we are planning on leveraging the persistent resource primitives soon.
However with disk not being accounted for, we sometimes run into issues where the disk space has been a resource bottleneck for hosts (e.g. the instance restores from a HUGE backup). We should have a simple implementation first that specifies the disk sources as if they are enforced.

This is addressed in #23.


Footprint updates from overlap analysis

From the analysis in #100, the folks at Seattle have come up with new footprint fixes.
These are on their Sharepoint here, but I can never tell who will be able to access that, maybe only me:
https://seattlegov.sharepoint.com/:x:/r/sites/OSE-External/Shared Documents/Benchmarking/GreenInfo OSE 2024/Shape Review Fixes 20240718.xlsx?d=w99b6598570244ea385f339e6fa2f0a87&csf=1&web=1&e=GiqCfK
So I also uploaded here:
https://docs.google.com/spreadsheets/d/113HDoy6WnkBAx-E7GCazrJRD9VWy4SQE/edit?gid=189376366#gid=189376366
It looks like about 104 building IDs identified for repair.
there's no huge rush on this, though completion in September would be ideal.
┆Issue is synchronized with this Asana task

Shape fixes for Sept. 2024 (from sheet 20240718) are in. I saw a few other overlaps in nearby areas and can go back through and document the ID's for future review if necessary, otherwise the working file is ready to share.
P:\proj_p_s\Seattle Building Dashboard\2024_update\seattle_building_outlines_2024_update\seattle_building_outlines_2024_update

@tomay to update footprints using this data.
As a convenience, here's donwload https://www.dropbox.com/t/OH1TvEe5UEwbrC3n

This has been uploaded to footprints_production, and unless we note any issues, this is done


Reduce resource requests of istio ingress gateway and adapt autoscaling accordingly.

How to categorize this PR?

/area networking
/area auto-scaling
/area cost
/kind enhancement
What this PR does / why we need it:
Reduce resource requests of istio ingress gateway and adapt autoscaling accordingly.
Due to the split of istio ingress gateways across zones in highly available seed setup, its resource requests are slightly oversized except for very large active seed clusters. To reduce the unnecessary resource waste this change reduces the resource requests to a quarter (cpu) and half (memory) respectively. The general assumption is that due to its priority the istio ingress gateway may be able to get additional cpu if available on the node. With regards to memory, the limit is left in place with the same value and again its priority may help not being out-of-memory killed. As an additional measure with regards to memory, the autoscaling is extended to also cover memory so that a scale-up can happen under memory pressure. In addition to that, the scale-up/-down behaviour is now explicitly specified with a fast scale-up and a slow scale-down.
Which issue(s) this PR fixes:
None.
Special notes for your reviewer:
For the istio ingress gateway spanning multiple zones, i.e. the default istio ingress gateway, the autoscaling is not optimal as it does not take zones into account. This means the deployment may scale up in a zone, which is not under pressure.
However, as we have not seen a lot of scale-up operations with regards to istio, this is left as a follow-up step. It might be a good idea to combine the single-zone istio ingress gateways to a virtual multi-zonal one and getting rid of the existing default one, but that requires more changes and may be done as a follow-up.
Release note:

Resource requests of istio ingress gateway are reduced and its horizontal autoscaling behaviour specified in more detail, including scale-up under memory pressure

/cc @vlerenc @voelzmo @dguendisch @axel7born @DockToFuture

Thank you @ScheererJ. I hope we will not break/tear down anything with the change ("never touch a running system", but in this case...). What can we do - as flanking operations? I could get the numbers from dev and staging? Maybe you can ping me?
Something else? I should have also the restart count and such, but what matters is whether the API servers remained accessible and I do not know whether we would see a small decline in availability (a large probably).

/lgtm


New version: PosDefManifold v0.3.5

Registering package: PosDefManifold
Repository: https://github.com/Marco-Congedo/PosDefManifold.jl
Created by: @Marco-Congedo
Version: v0.3.5
Commit: 3df970a82f67b8fbbd1e156d22d5fadaa9e11857
Reviewed by: @Marco-Congedo
Reference: https://github.com/Marco-Congedo/PosDefManifold.jl/issues/92

Ok [noblock]


chore(DataSpreadsheet): #1847 spreadsheet color tokens update

Contributes to #1847
Updates body cell and header cell background colors to match Carbon's data table implementation.
What did you change?
_data-spreadsheet.scss
How did you test and verify your work?
Storybook

I had some merge issues that i had to fix, do you mind reviewing again @lee-chase?


App crash when using drag & drop not as admin

Description
Crashed after opening app and draging a file. No other actions. App is not running as admin, and is not set as the default file manager. Sometimes it happened to work well with no crash for drag & drop but I am not sure about the reason.

[ ]

Steps To Reproduce

open the app and select any file in any folder
drag the file
app crashes right after dragging

Requirements
Fix app crash that occurs when using drag & drop not as admin nor as default file manager.
Files Version
<IP_ADDRESS>
Windows Version
10.0.19045.3448
Log File
debug.log

Thanks for the report, Where are you dragging too? (Local, network, ftp, cloud, etc)

Local. Actually it crashed immediately after I dragged a file.

Does it happen consistently?

Almost everytime.

Is this still an issue in the preview version? https://files.community/download/preview

Can you also check what happens if you try dragging a tab?

Just tried and still crashed in the latest preview version including dragging a tab.

@bhw777 thanks for checking, can you upload the log file for that? If it's affect tabs as well, I'm starting to think it might be a platform issue but perhaps we can come up with a workaround.

I figured it out. I think it has been successfully fixed in the latest preview version because it won't crash if I open it directly or set as the default file manager. It only crashes if I open it using another app (there is an app that helps me open it conveniently, like a shortcut). Maybe there are some conflicts between them.

Do you have the stable version of Files installed? It's possible the other app is opening the stable version of Files which still has this issue.

No, I only have the preview version.

Can you check if the process is elevated (you can check in Task Manager)?

I can not drag file or tab if I open as admin. No response for that.

We disable drag & drop on admin because of a platform limitation, but it seems very similar to this issue. Which app are you using to launch Files?

Everything is good if it is not elevated, and I used Quicker to open it.

Can you try launching Windows Terminal thought Quicker and check if dragging a tab causes a crash?

No crash for Windows Terminal.

@bhw777 what username name is displayed next to the Files process in Task Manager? I think what's happening is that the process is being launched with higher trust, but we currently only check to disable drag and drop as admin.

On second thought, Task Manager might not show this information.

I saw username both in Task Manager and Process Explorer. The username shown next to Files is my computer's name (there are other username like SYSTEM and LOCAL SERVICE, not sure if I that's what you are looking for).

I think it's the integrity level, not the username.

The integrity level is high for admin and medium for not admin.

What about when you launch through Quicker?

Oh, I got it. When I launch through Quicker it is in high because Quicker is in high and the Files process is under Quicker even if I don't launch any of them as admin.

Thanks for sticking with me through all this 😄
Now that we know the cause, we can look into a fix. Unfortunately drag & drop will have to be disabled, but at least it won't crash.

No problem. I haven't use Files for a long time because of this problem.Thanks for helping me know what happened. Looks like I can start using it again. 😄

@yaira2 Still crashed through Quicker. No problem when launched directly.

@bhw777 can you confirm if this is resolved in the v3.5.17 preview version? https://files.community/download

@yaira2 Tested and no crash. I believe it is resolved.

Thank you for checking!

@0x5bfa nice work!


Issues with DF Active and Auto Anim

Doesn't seem to be working right ATM, could it be an issue with them upgrading to Ver 11?

Just tried it out, still works in my game. To my knowledge DF active lights will not receiving updates anymore, autoanimations still should. I updated both modules just in case on my end, just to see they were already up to date on my end.
It could be that it does not show on single shots due to latency delay and how DF active light works. Basically, Active lights uses the server tick rate to animate the light source. Due to latency it could be that the light source is created after the keyframe should be showing the light.
An almost surefire way to check is to use autofire, as it shoots 10 times it should be showing up unless you have a latency of multiple seconds.

Just tested it on my end and with Automated, DF, and the JBSA Patreon. Autofire still won't muzzle flash for me or do the traces like on the preview shown.
Maybe I have something set up wrong?

Make sure you have the setting enabled in the modules settings. It might be disabled.
Can you check if anything is in the clients console which might indicate some issue or error?

I have it enabled an no errors come up when an attack is made. No sound is played either but the hit animation is played.

mind taking a screenshot of the console.
first clear the console, then fire a shot or a full auto attack. take screenshot
make sure that automated animation and df active lights are enabled, and that an attach animation from automated animations is being played.

Just tested this out as well, and it doesn't work for me either.

(Ignore the bottom two messages, that was when I had to change the window size to take the screenshot).
I see messages for rendering the roll dialogue, the array for the dice, and outputting the chat message. I see the basic hit animation (or miss in the case of missing), but the lights and bullet animations aren't working.
I have all modules installed, the setting to show the animations is turned on, I tried using auto-fire on an assault rifle and the animations just aren't showing up. I can see the hit and miss animations, and my custom sound goes off. Basically everything but this, https://github.com/diwako/foundry-cyberpunk-red-core-additions/raw/master/images/dfLights.gif

Hm, weird. then lets try to reconstruct the conditions for it to work.
I will be using some mook with an assault rifle, using Rifle (basic) as ammunition. You need at least one additional token to the mood in the scene. Make sure that the scene is set up so ambient light works and can take effect, might just up the darkness value for that.
First of check if the modules are active. We need 3 modules active.

Automated Animations
DF Active Lights
JB2A (patron version optional) (needed for Automated Animations)

Then we check this ammunition type has an effect configured for the module Automated animations
Here when opening the ammunition item and clicking the A-A button in the header

The config looks like this within the Automated Animations global config.

After that, we select the second token as target, and for easier time spotting the ambient light, choose to autofire or suppressive fire.
https://www.youtube.com/watch?v=0-AHLqO6wOs

So, there's possible two issues for me.

The AA menu doesn't have any Cyberpunk RED specific animations, it's all D&D stuff. However, there are settings for Cyberpunk under Settings for A-A (Enable Autoamtic Repeats, Use forceMiss, etc).

I'm running Forge-VTT on version 10, though I think it should default to the last working version for any version 10 release?

A-A does not ship with cyberpunk configs. you need to make them yourself or find someone who shares their configs
This module at least supports both v10 and v11

I see. I went in and created a default rifle animation to test, and the lighting effects still won't go off, although the animations work now!
The following error is all that shows up in the console after test firing,
commons.js:1703 Error: You are accessing the CPRCombatant#data object which is no longer used. Since V10 the Document class and its contained DataModel are merged into a combined data structure. You should now reference keys which were previously contained within the data object directly.     at logCompatibilityWarning (commons.js:1692:19)     at CPRCombatant._logV10CompatibilityWarning (commons.js:6642:14)     at get data [as data] (commons.js:6542:24)     at CPRCombatant.new_getToken (floating-combat-toolbox.js:285:26)     at 🎁call_wrapper [as call_wrapper] (libWrapper-wrapper.js:616:16)     at 🎁Combatant.prototype.token#getter (libWrapper-wrapper.js:364:19)     at hooks.mjs:261:49     at EmbeddedCollection.some (commons.js:3378:22)     at Object.fn (hooks.mjs:261:37)     at #call (foundry.js:724:20)     at Hooks.callAll (foundry.js:681:17)     at ClientDatabaseBackend.callback (foundry.js:12824:13)     at foundry.js:12804:43     at Array.map (<anonymous>)     at ClientDatabaseBackend._handleUpdateEmbeddedDocuments (foundry.js:12804:33)     at ClientDatabaseBackend._updateEmbeddedDocuments (foundry.js:12672:17)     at async TokenDocument.updateDocuments (commons.js:6153:23)     at async TokenDocument.update (commons.js:6250:23)     at async TokenDocument.updateActorEmbeddedDocuments (foundry.js:22208:5)     at async Proxy.updateDocuments (commons.js:6153:23)

Nevermind, it's working now?
Does seem to be an issue with the delay.

Try autofire, there is some server <-> client delay, i tried to compensate for this but it is a bit hard to do.

Yeah, no worries. At least it's working!

I will be closing this issue now. I know that I answered a bunch of things but not to the original creator of this issue, still it has a bunch of info which can be used to try out how things work