To do: per-package channels

Here's a proposal.
channels = ["channel1", "channel2"]

[deps]
foo = "1"

[deps.bar]
version = "2"
channels = ["channel3"]

So each package can have a list of channels that it can be installed from. If not specified, it uses the top-level channels list, which if not specified defaults to ["conda-forge"] (as currently).
So in the example, foo implicitly has channels=["channel1", "channel2"].
Now when merging two packages of the same name from different CondaPkg.toml files, take the intersection of their channel lists. Throw an error if the intersection is empty (showing which TOML files specified what). If non-empty, pick one of the channels (arbitrarily?) and install with the channel::package syntax. Don't use the --channel argument at all.
This means that it is guaranteed that a package will be installed from one of the channels specified in the CondaPkg.toml file.
The empty intersection thing might be an issue though - the CondaPkg.toml author ideally should include all the channels that the package could be acceptably installed from. Perhaps only default to conda-forge for a given package if no occurrence of that package in any CondaPkg.toml file specifies any channels.
It also avoids the current weird "channel crossover" behaviour where one TOML file specifies Package1 and Channel1 and another specified Package2 and Channel2, and it's possible to have Package1 installed from Channel2 and Package2 installed from Channel1. (Because we just do conda install -c Channel1 -c Channel2 Package1 Package2.)

Ah, this is interesting.  Instead of just the channel::package=ver syntax, it looks like you could support the whole range of MatchSpec capabilities by using package[channel='channel',version='ver'] syntax, with other key-value pairs as needed — and just some extra processing to resolve conflicting channels, as you've suggested.  In particular, the difference between a package version '=0.53' and '==0.53' seems easier to do if you just put it in as a key-value pair.
It's not clear to me what exactly you mean by

merging two packages of the same name from different CondaPkg.toml files

Are you talking about just merging the channel spec for each package, or merging the whole package spec so that conda only sees each package once?  For example, suppose one of the Project.toml dependencies in your example has this CondaPkg.toml:
[deps]
bar = {channels=["channel3","channel4"], md5="12345678901234567890123456789012"}

When combined with your CondaPkg.toml above, you could merge the channels in the two bar specs in the julia code, but still supply them as separate specs to conda, so that the resulting command would look like this:
conda install foo[version='1'] bar[version='2',channel='channel3'] bar[channel='channel3',md5='12345678901234567890123456789012']

Conda has no trouble with the fact that bar is specified twice, and already has lots of complex logic to merge the specs (which you surely don't want to reproduce).  Is this what you're intending?

You're absolutely right and in fact currently if a package appears in several CondaPkg.toml files with different versions then we specify the package several times. So indeed we could just allow the user to specify any of the spec fields and pass the specs on to Conda without changing them.
(Unfortunately Pip and Julia dependencies do need to be merged.)
So we could leave the current behaviour as is and just allow specifying more fields.
The main issue is with taking the union of the top-level channels from different toml files. It would be nice to guarantee that the packages in a file are installed from one of the specified channels, which isn't currently the case. To do this would require some logic with the top level channels and those on the package.
It would also be nice to let a package specify several channels it could come from.

You make a lot of good points, and I should go with what is most natural in Conda-land. I just find it weird that you can install the "same" (but actually different) package from different channels. But if that's how Conda works there's no point me trying to fight it.
So this proposal becomes: keep precisely the current behaviour, but allow the user to set all the fields of the Conda package spec, in particular the channel.

I agree that it's weird, but also just how conda works.  The only alternatives I can think of involve

Calling conda install multiple times — once for each CondaPkg.toml.  But that still involves ambiguity about the ordering, and would potentially install and reinstall the same packages, taking lots of time.
Trying to solve things yourself, which would require either using the conda API in complicated ways, or recreating that API in julia code — all in an effort to make CondaPkg behave differently from Conda itself.

So both for simplicity and consistency, I think your proposal sounds like the best option.

@moble I've implemented this on the main branch now, I'd be grateful if you could try it out. You can now do CondaPkg.add("llvmlite", channel="numba") or equivalently pkg> conda add numba::llvmlite.
For now I've only added support for specifying the channel - supporting subdir and build is for another day.

Sorry, this fell off my radar for a bit.  Yes, this works very nicely with the latest release.  Thanks so much!


Improve mt9m114 camera driver

Currently, the driver supports only VGA resolution while 480x272 is needed to match with the display resolution on i.MX RT10XX family.
Also, the current framerate is very low, about 3-4 fps without doing anything else with the image buffers (just discarding them).
This PR reworks the driver to address the low framerate issue as well as to add support for 480x272 and 1280x720 resolutions.

Hi @loicpoulain , is it ok for you now ?
Thanks !


Refactor create base image's form info

Create GraphQL fragment for data into CreateBaseImage form and use it on BaseImageCreate page.
This PR also gets rid of eslint relay/unused-field warning in BaseImageCreate page.

Closing as superseded by #505


Import autocomplete suggests not exported types and interfaces

From @klis87 on December 6, 2017 12:35

VSCode Version: 1.18.1
OS Version: Linux

Steps to Reproduce:

Install redux-saga-requests library with yarn add redux-saga-requests
Start typing import {} from 'redux-saga-requests' and use autocomplete feature between {} with ctrl + space. You will see types and interfaces not exported in typings TypeScript file.

For example, I have a following in my index.d.ts file:
interface ActionTypeModifier {
  (actionType: string): string;
}

but I can still see ActionTypeModifier hint. The problem is, that autocomplete is polluted with many internal types, which are not part of public API. Is it an expected behavior?
Reproduces without extensions: Yes
Copied from original issue: Microsoft/vscode#39785

The export keyword isn't necessary for something to be exported. All declaratinos in a declaration will be exported (the exception being when there is an export = somewhere).
If a type is truly internal, you can simply not include it in the declaration file. But in this case it looks like this is the return type of a public function, so it's not really internal...
If you really don't want that showing up in completions in an import declaration, you could move the "internal" types to another file and import from there. They may still show up as global completions, though.

@andy-ms I am specifically seeing this for all exports declared under types/npm-ramda/src
E.g.
declare const groupWith;
export = groupWith;

auto imports for what are non-existent named exports are being suggested.
Should I open a separate issue or would it be best to track it here?


update

update to main source to enable branching of new features

this was an error, wanted to do the pull request the other way around.


Typescript Example

Hi,
do you know if there is something minimal even for TypeScript Please?

Sorry mate, I don't know anything like it for TS.

thanks


[FEAT] Minor suggestion: rename plugin to "Outliner"

Instead of calling it the "Obsidian Outliner Plugin" in the settings menu and command palette, I think it would be cleaner to just call it "Outliner." This would follow the naming convention of most other plugins I have installed. Thank you for all your hard work!

@ShreyasKallingal Thank you for your contribution! Changed in https://github.com/vslinko/obsidian-outliner/releases/tag/1.0.23


Fix and simplify optimization_targets for S10 compile

Description

The MANUAL_REVERT compile tries to manually revert the minimum latency flow settings to match the NO_CONTROL compile. However, [[intel::speculated_iterations(4)]] becomes unnecessary in MANUAL_REVERT because the speculated iteration is 0 in the corresponding NO_CONTROL compile now.
Also remove two unused -D macros in CMakeLists.

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

[x] Command Line
[x] Regtest

IPA: https://spetc.intel.com/testsummary?trview=0&testRunIds=8501121
Full system: https://spetc.intel.com/testsummary?trview=0&testRunIds=8496942

I see your simulation failed (https://spetc.intel.com/testanalysis?trview=0&testRunIds=8496942&tapgsize=20):
Perhaps you forgot to set the CL... environment variable?
[START scc281175 TestDriver::Common::CommandTask => ./run.sh]
|[14:26:46] Running FPGA binary without minimum latency flow
|[14:26:48] Caught a SYCL host exception:
|[14:26:48] Native API failed. Native API returns: -2 (PI_ERROR_DEVICE_NOT_AVAILABLE) -2 (PI_ERROR_DEVICE_NOT_AVAILABLE)
|[14:26:48] terminate called after throwing an instance of 'sycl::_V1::runtime_error'
|[14:26:48]   what():  Native API failed. Native API returns: -2 (PI_ERROR_DEVICE_NOT_AVAILABLE) -2 (PI_ERROR_DEVICE_NOT_AVAILABLE)
|[14:26:50] ./run.sh: line 35: 11246 Aborted                 (core dumped) ./${EXE_NAME}.${TARGET} ${RUN_ARGS}
|[14:26:50] Running FPGA binary with minimum latency flow
|[14:26:50] Caught a SYCL host exception:
|[14:26:50] Native API failed. Native API returns: -2 (PI_ERROR_DEVICE_NOT_AVAILABLE) -2 (PI_ERROR_DEVICE_NOT_AVAILABLE)
|[14:26:50] terminate called after throwing an instance of 'sycl::_V1::runtime_error'
|[14:26:50]   what():  Native API failed. Native API returns: -2 (PI_ERROR_DEVICE_NOT_AVAILABLE) -2 (PI_ERROR_DEVICE_NOT_AVAILABLE)
|[14:26:50] ./run.sh: line 35: 11255 Aborted                 (core dumped) ./minimum_latency.${TARGET} ${RUN_ARGS}
|[14:26:50] Running FPGA binary with minimum latency flow but reverting controls manually
|[14:26:50] Caught a SYCL host exception:
|[14:26:50] Native API failed. Native API returns: -2 (PI_ERROR_DEVICE_NOT_AVAILABLE) -2 (PI_ERROR_DEVICE_NOT_AVAILABLE)
|[14:26:50] terminate called after throwing an instance of 'sycl::_V1::runtime_error'
|[14:26:50]   what():  Native API failed. Native API returns: -2 (PI_ERROR_DEVICE_NOT_AVAILABLE) -2 (PI_ERROR_DEVICE_NOT_AVAILABLE)
|[14:26:51] ./run.sh: line 35: 11257 Aborted                 (core dumped) ./manual_revert.${TARGET} ${RUN_ARGS}

That's a known issue: https://hsdes.intel.com/appstore/article/#/14020048189

@jimmytwei  please merge


breaking change in upstream gopass.GetPasswd return signature

Hi,
Unfortunately this is one of those situations where package and version management is lacking in the Go ecosystem badly. There are library calls (two of them) in your package that are now broken due to upstream changes in the gopass package from two days ago 6da5953, which I filed a issue there #19
It should be a simple fix for each, ex:
pass, _ := gopass.GetPasswd()
return string(pass)

I suppose you probably need to update godo.v2 with this change, and maybe you might want to release a new godo.v3 with actual handling of the error returned by that function. Or, since it's such a tiny package itself, maybe you might consider pulling it in wholesale since the author's license is wide open and handle it yourself going forward.
Thanks!
Mike

As a reference, I filed a issue in gopass at #19

:+1: thanks!


OK to use Trimmings with Turbolinks and Stimulus?

Is it OK to use Trimmings with Turbolinks and Stimulus in the same project? Any known conflicts?

OK, I RTFM 😂
"Trimmings’s API was inspired by Stimulus and the two libraries work happily together. Trimmings is designed to never allow extension with client-side code, but if you ever need to add your own logic, you can drop in Stimulus controllers without disrupting your workflow or your existing Trimmings hints." 🎉


Don't use the configs in project's filepath if options.runTest.

The config loader has a bug that it ignores options.runTest if there is a blueprints.config.js in your project. This fixes that so we load the testing config that finds all of your tests to compile and run those in mocha.
This broke for mweb when we started using custom configs because of production building (https://github.com/reddit/reddit-mobile/pull/653).
🔕  At some point in the future we may need to make the testing configs smarter. I.E. your project may have some custom config that it relies on that would prevent tests from compiling properly.
👓  @nramadas or @uzi

:fish:

At some point in the future we may need to make the testing configs smarter. I.E. your project may have some custom config that it relies on that would prevent tests from compiling properly.

I'm exactly in this situation as I rely pretty heavily on aliases (really hate relative paths in imports).  I also have multiple entry points, which I think could complicate things further.  Could we solve this by allowing you to specify which configs to load? (I don't always want to build both entry points either but am forced to because all configs are always loaded)


Fix crystal on layout

Connected to #6 and #10

Also connected to #7, now there is no need to order it with 2oz.

Fixed #9

@lifeeth it passes, will add some extra space just to be sure.

Sounds good!

LGTM


boards: nordic: nrf54h20dk: add miscellaneous shared mem for cpusec

This is auxiliary shared memory needed for some of IPC communication.

Needs rebase
@anangl please take a look

@nika-nordic is this PR still relevant? If yes, it needs rebasing :)


Makes sure Bonner program event trainings do not show up for some user

Solves issue #637
Changes made:

Bonner scholar program event training does not show up for students who are not Bonner Scholars and faculty members under the training and education tab on the event list interface

 Bonner Training events should not show up for non-Bonner students #637


why nameserver not have acl ?

when sometime I need nameserver expose outside network , but without acl feature,that mean anyone can add un safe broker to rocketmq ?
or just need a token something to checkout broker identity ？

you can do same ons  of aliyun

I just want to know that rocketmq nameserver without acl feature is good for security ?
or just I misunderstand it work ？

yd when I create a test network with aliyun ECS,will expose rocketmq service to debug,I should pay attention to mq safety?

you should save ak as

https://github.com/apache/rocketmq/issues/403
there is about acl

when sometime I need nameserver expose outside network , but without acl feature,that mean anyone can add un safe broker to rocketmq ?
or just need a token something to checkout broker identity ？

Actually,in rocketmq cloud enviroment or cases,your using namesrv to expose outside network is not a better choice.


Header is being switched on when you close the Wallet load report, even if still synchronising

We don't want the balance to show until the sync has completed so this is wrong

Header now does not switch on in a mainView.refresh(), only when the sync finishes (in MainController).
Awaiting review and closing

Verified working.
Closing.


feat: Global HTTP proxy support (1.6.x backport)

Backport #2858 to 1.6.x branch.
Release Note
feat: Global HTTP proxy support

The upgrade tests will be fixed with #2900 and #2904.


Problem with realtime db

I cannot figure out how to get realtime data. I can get one at a time, but there is no notification saying that the data is finished updating. Can anyone show me how to do it so that I'll know when all the data has come in? Or can it give me a collection of items instead of one at a time?

If you are having this problem. It is because you do not understand how await and async work in c#. I recommend go learning how they operate.
Example:
var firebase = new FirebaseClient("https://you.firebaseio.com/"); var dinos = firebase.Child("your-info"); var query = QueryExtensions.WithAuth(dinos, auth.FirebaseToken).OnceAsync<Object>().Result;
Here query contains all of the objects you need. But ONLY because i did not use await. If i had used await. It would have contained nothing UNTIL the request was finished.

First, let me thank you for responding. You are correct in that I am still learning about await and async.
I think I may not have been clear enough in my question however. I do understand how
OnceAsync works. I originally had that working just fine. What I'm trying to figure out is how to setup a subscription. Using the example code provided, I'm able to get one item at a time through the onNext handler, but the problem is that I never know when the data is finished, so if the record set on the server changes, it sends me everything again, and my local collection has everything in it twice.
Again, I acknowledge that this is my own ignorance at work here. I'm just looking for some guidance on how to learn how this stuff works. I looked up Reactive, and I think I understand the principles. I'm just not sure how to apply them in this case.
When I did this in Objective-C, I was given back a collection of all the items at once, not individual items. So it seems that the way it's done in C# is a bit different.
Thanks for any further help you can offer.
Kenny

On Nov 4, 2016, at 3:42 PM, dthall43<EMAIL_ADDRESS>wrote:
If you are having this problem. It is because you do not understand how await and async work in c#. I recommend go learning how they operate.
Example:
var firebase = new FirebaseClient("https://you.firebaseio.com/");
var dinos = firebase.Child("your-info");
var query = QueryExtensions.WithAuth(dinos, auth.FirebaseToken).OnceAsync().Result;
Here query contains all of the objects you need. But ONLY because i did not use await. If i had used await. It would have contained nothing UNTIL the request was finished.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hello all,
i'm new to firebase with c# xamarin and i would like to make a sample application.
This sample application can just connect to firebase and react with my device on real time.
I can connect to firebase, add, deleve datas, but each time i add on => console firebase a new data my device is not synchronise directly ...
How i can do that ? i read the wiki about subscribe but how i can use it ?
Is there possible to have a little sample or isn't possible to do that actually ?
Thanks for your knowledge you share that's really great to use some project here.
Christophe

You could create an observer which listens to changes made in the database.
You can create an observer like this:
var firebase = new FirebaseClient("https://you.firebaseio.com/");
var observer = firebase.Child("<your-folder>").AsObservable<T>();
Later you can subscribe your observer to the database
Observer.Subscribe(next =>
                    {
                        //do stuff here with every item you collect from the database
                    },
                onError =>
                   {
                       //do stuff here when an error occurs
                   },
                onCompleted =>
                    {
                        //do stuff here when all items are fetched from the database
                    }
                );

I must add that the onError and onCompleted are not called in my project.
I have added a post on this page regarding that issue.

You could create an observer which listens to changes made in the database.
You can create an observer like this:
var firebase = new FirebaseClient("https://you.firebaseio.com/");
var observer = firebase.Child("<your-folder>").AsObservable<T>();
Later you can subscribe your observer to the database
Observer.Subscribe(next =>
                    {
                        //do stuff here with every item you collect from the database
                    },
                onError =>
                   {
                       //do stuff here when an error occurs
                   },
                onCompleted =>
                    {
                        //do stuff here when all items are fetched from the database
                    }
                );

I must add that the onError and onCompleted are not called in my project.
I have added a post on this page regarding that issue.

@kennyray Thank you for posting this question. I myself getting this error. When i update some data, it returns whole data under that node. Also .Subscribe() called for every item in that particular node.
How you solved this?

@pallavbohara  @kennyray  you able to solve it?

Was anyone able to solve this issue? Is there anywhere I can go for better documentation?

@pallavbohara @navingp @pbrownTexasDevices I didn't solve it, and I ended up moving away from Firebase. Sorry I can't help further...

@kennyray What did you move to if you don't mind me asking.

@pbrownTexasDevices  I moved to Azure, but couldn't figure out how to do login, so I stopped working on the project and closed my Azure account because it was costing me money each month. I have been working with Xamarin OAuth and once I have that figured out I will be trying AWS for the db next.

It would be nice if there was a discussion forum where we could talk about how to do stuff without posting as issues. Does that exist? A Slack channel perhaps?

I guess that I resolved this problem, changed the way that I subscribed.
FirebaseDataBaseConfig.Suscription.Add(FirebaseDataBaseConfig.RootReference.Child("chats").Child(conversation).OrderByKey().LimitToLast(1).AsObservable().Subscribe(
delegate(FirebaseEvent e)
{
Debug.WriteLine("FirebaseEventIOS : " + e.Key + " " + e.Object.Message);
MessageChangeTrigger(e, conversation);
}));
If you limit to last item in your subscription, the event "onNext" only once called. I tried with "onCompleted" event, but this never fired.


Redirect Url is somthing not the same to before version？

In version 4.3.1 or before, response is success and the url is change to redirect url,
but in version 4.4.0, response is failed even though the url is change to redirect url.

code

val mainScope = MainScope()
val url = "https://graph.facebook.com/1257982827734689/picture?type=normal"
mainScope.launch {
    val request = Request.Builder()
        .url(url)
        .build()
    withContext(Dispatchers.IO) {
        val call = client.newCall(request)
        val response = call.execute()
        Log.d("EEE", "response: $response")
    }
}

圖片 statusCode 200
圖片 statusCode 404

This is fix on version 4.4.1


KMeans++

Plans for this PR:

[x] Parallel cumulative sum primitive (aka prefix scan, inclusive scan).
[x] Parallel search sorted primitive (see this page)

/intelci: run

@KulikovNikita Current PR is really big and includes several features that could be splitted into several PRs. "One PR - one feature" is more safe concept and better for review.

/intelci: run

/intelci: run

At this point it:

Works in the distributed mode, results are consistent in both modes.
Handles everything consistently with the vanilla sklearn. The results of RNG are slightly different though.
Requires tuning in the extract_and_share_by_indices function. There is a way to optimize it further by using allreduce and selecting candidates in bulk. It should bring up to x4 speedup to this particular kernel

It also shows significant KMeans convergence improvement in comparison with less sophisticated methods

/intelci: run

@KulikovNikita First, thanks for the great work you've done!
This PR is really big. At least it could be splitted into 5-6 small ones.
There is a vicious cycle that happens with long PRs. Long PRs yield long review times, and longer review times yield longer PRs because engineers try to get more code reviewed per PR, repeating the cycle.
It’s actually better to write short PRs. Although initial reviews may still be slow, review times will pick up speed because shorter PRs are easier to review. More over some of functionality could be merged early. And this is more safe in several cases.

/intelci: run

Last CI: http://intel-ci.intel.com/edef3834-ceac-f101-bdd0-a4bf010d0e2e

/intelci: run

Last green CI: http://intel-ci.intel.com/edef4bc1-a699-f1c9-8eba-a4bf010d0e2e

Manually started CI job: http://intel-ci.intel.com/edefd244-2f14-f1c9-972d-a4bf010d0e2e

Yet another one CI job: http://intel-ci.intel.com/edeff7e4-4215-f1fe-bdd0-a4bf010d0e2e


⚠ Spryr has degraded performance

In ab2fa2d, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 5237 ms

Resolved: Spryr performance has improved in 7c87d25 after 7 minutes.


Scroll to anchor in router.scrollBehavior doesn't work

[x] I confirm that this is an issue rather than a question.

Bug report
https://github.com/saberland/saber/blob/61992cbcff3ed552aa90e6bff1cf320e1d35da82/packages/saber/vue-renderer/app/router.js#L68-L87
The code attempts to scroll to the anchor if to.hash exists and the anchor can be found. But the scroll never happens.
Version
0.6.4
Steps to reproduce
about.md:
[Hello](./hello.md#world)

hello.md:
# World

Lorem ipsum...

Then click the link in about.md.

What is expected?
Page scrolled to the title World.
What is actually happening?
Page scrolled to the top (default behavior).
Other relevant information

If to.hash only contains ASCII characters, the hash before and after escaping are the same. If it contains non-ASCII characters (e.g. CJK characters), escaping the hash will produce a selector matching nothing (assuming header's id is generated in standard behavior).

Possible solution: Use decodeURIComponent(to.hash) instead of window.CSS.escape(to.hash)

Even if the selector is valid, document.querySelector(hash) still matches nothing, thus the scroll won't trigger. Chances are page is not loaded at that time.

Possible solution: Move the codition statement to a hook like afterPageLoad or use other methods (can only come up with setTimeout(condition, 0))

Result of running saber -v: cli.js/0.6.4 win32-x64 node-v12.3.1
Browser version (optional): Google Chrome 76.0.3800.0 (64-bit)
Is Saber a global or local install? Local
Which package manager did you use for the install? Yarn
Does this issue occur when all plugins are disabled? Yes

IssueHunt Summary

 krmax44 has been rewarded.
Sponsors (Total: $50.00)

 issuehunt ($50.00)

Tips

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on IssueHunt to raise funds.

@issuehunt has funded $50.00 to this issue.

Submit pull request via IssueHunt to receive this reward.
Want to contribute? Chip in to this issue via IssueHunt.
Checkout the IssueHunt Issue Explorer to see more funded issues.
Need help from developers? Add your repository on IssueHunt to raise funds.

Scroll to id containing URI encoded characters now works but only when clicking heading anchor 😢

Working
Not working

(First two triggered by clicking the heading anchor, last two using browser back/forward)
@krmax44 we should put a const hash = decodeURIComponent(to.hash) here:
https://github.com/saberland/saber/blob/6118d78c3133765e4fcfc4546133b45c6796d9c1/packages/saber/vue-renderer/app/router.js#L64-L67

@kidonng fixed in 0.6.7


docs : adding type of plugins

Description :
Clarified the difference in the types of plugin ,i.e between Task and Hook in the table format to get clear understanding.
Preview :

Related Issues or Pull Requests
Issue #16

@scortier Use conventional commit convention for commits.

@scortier Use conventional commit convention for commits.

Ok ,will go through the convention and will surely make the required changes in the PR

Pull Request Test Coverage Report for Build 977995863

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 63.359%

Totals

Change from base Build 970889294:
0.0%

Covered Lines:
3180

Relevant Lines:
5019

💛  - Coveralls


E2E: go release main config-ldflags-noassets slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v17.0.12
Run: https://github.com/slsa-framework/example-package/actions/runs/6582334488
Workflow name: .github/workflows/e2e.go.release.main.config-ldflags-noassets.slsa3.yml
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.release.main.config-ldflags-noassets.slsa3.yml
Trigger: release
Branch: v17.0.12
Date: Fri Oct 20 01:49:38 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v17.0.12
Run: https://github.com/slsa-framework/example-package/actions/runs/6594457354
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.release.main.config-ldflags-noassets.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.release.main.config-ldflags-noassets.slsa3.yml
Trigger: release
Branch: v17.0.12
Date: Sat Oct 21 01:50:39 UTC 2023
Tests are passing now. Closing this issue.


Potential security issue: dependency on xml2js v0.4.x

@intacct/intacct-sdk depends on xml2js v0.4.x. This version has a vulnerability (link). Can we upgrade to 0.5.x?
Thanks!

@arthur-zhao-anrok I opened #129 to fix this issue. If you've got contacts at Intacct, it'd be great to get them to merge this.


Added APIs

Jira: https://jira.lyrasis.org/browse/FCREPO-3392
What it does
Adds an API for building F6 OCFL objects. The current API is not intended to have feature parity with the OCFL session that's currently used in core. The initial focus is a common abstraction that can be used by the various migration utilities.

I'm not sure why travis is spawning duplicate runs and not resolving them...

Can we start this project off using main instead of master?

How will that affect this PR? Perhaps we can do it after this PR is committed?

I just read the previous iteration of this (rather late), sorry if I'm asking about stuff that came up in slack or on the tech call:

The operations in OcflObjectSession have fragmented quite a bit into separate methods for individual object types. I'm curious the reason for this, versus having the implementation determine what actions are necessary? All the write methods have the same parameters. Just wondering we're overfitting the API, but I recognize that these are the current main categories of objects in the application, so it may be pretty stable.
I see that PersistencePaths is no longer present in the API and is now a resourceId. Was the conclusion that it wasn't necessary or was an internal implementation note?


Better records' model_commited hook error message

When invenio_search.contrib.records:index_record_modification fails because of a connection to elasticsearch issue, the error is reported on invenio_records.api:create as:
InvalidRequestError: This session is in 'committed' state; no further SQL can be emitted within this transaction.

We could log the reason of the rollback in order to make debug easier.

(FWIW saw exactly this when debugging https://github.com/inveniosoftware/invenio-search/pull/34.)

@nharraud we no longer have invenio_search.contrib.records:index_record_modification.
Can we considered closed this issue?


How to remove the inline style?

It's a beautiful component
I use tailwindcss in solid project, but when i use this component i have some question, i can't overwrite the background whit classname
How can i remove the inline style, i want use two theme in my project, so the toast need chang the color when the project chang the theme, if toast can remove the inline style, i think it's will be easy like this

thanks for your help

I find !!!  this is the change method

maybe can help some one
i will close this issus

I find !!!  this is the change method

maybe can help some one
i will close this issus


60 second timeout is a bit to strict for our codebase

I know this is not a finished product but wanted to bring this under your attention. A 60 second timeout is a bit too strict for our application it looks like.
   Symfony\Component\Process\Exception\ProcessTimedOutException  : The process "./phpstan analyse --level=max --autoload-file=/private/var/www/xxx/vendor/autoload.php --configuration=/private/var/www/xxx/vendor/weebly/phpstan-laravel/extension.neon /private/var/www/xxx/app" exceeded the timeout of 60 seconds.

  at /private/var/www/xxx/vendor/symfony/process/Process.php:1154
    1150|
    1151|         if (null !== $this->timeout && $this->timeout < microtime(true) - $this->starttime) {
    1152|             $this->stop(0);
    1153|
  > 1154|             throw new ProcessTimedOutException($this, ProcessTimedOutException::TYPE_GENERAL);
    1155|         }
    1156|
    1157|         if (null !== $this->idleTimeout && $this->idleTimeout < microtime(true) - $this->lastOutputTime) {
    1158|             $this->stop(0);

  Exception trace:

  1   Symfony\Component\Process\Process::checkTimeout()
      /private/var/www/xxx/vendor/symfony/process/Process.php:573

  2   Symfony\Component\Process\Process::getIterator()
      /private/var/www/xxx/vendor/nunomaduro/laravel-code-analyse/src/Console/CodeAnalyseCommand.php:54

  Please use the argument -v to see more details.

Possibly a $process->setTimeout(null); should be enough 😄

@stayallive Thanks for bring that into my attention. Like you said, a release of this package is not even close.
But I will take that in consideration! Thanks!

@stayallive By info: This package will probably have a Laravel configuration file. Those options will be configurable.

I don't think there should be a timeout at all 😊 The analysis can take a long time on case of large codebases.


Also, rows for St. Lucia including 73,568 are similarly wrong ("2196,397,230") in timeseries.csv.

Hm, the source for St Lucia (in src/shared/sources/lc) is hitting https://www.covid19response.lc/ ... looking at that page, everything looks fine, but running the source locally is returning trash:
MacBook-Air:li jeff$ ./start --crawl lc
MacBook-Air:li jeff$ ./start --scrape lc

┌─────────┬────────────┬──────────────┬───────┬────────┬─────────┬────────────────┐
│ (index) │ locationID │     date     │ cases │ deaths │ tested  │   recovered    │
├─────────┼────────────┼──────────────┼───────┼────────┼─────────┼────────────────┤
│    0    │ 'iso1:lc'  │ '2020-08-03' │ '25'  │  '0'   │ '3,548' │ '2229,630,598' │
└─────────┴────────────┴──────────────┴───────┴────────┴─────────┴────────────────┘

Looking into a fix, cheers! jz

The code is erroneously joining the numbers from "Number of COVID-19 Repatriations from Saint Lucia" (2), "Number of Persons Recovered from COVID-19" (22), and "Number of Confirmed Cases of COVID-19 in the Americas" (9,630,598)  ... :-(
The code would have been correct at one point, but the source data page has changed.  Needs a fix to select the right stuff.

That's a lot of recoveries for 25 cases!
From: "JZ"<EMAIL_ADDRESS>To: "covidatlas/li"<EMAIL_ADDRESS>Cc: "Steven Ganz"<EMAIL_ADDRESS>"Comment"<EMAIL_ADDRESS>Sent: Monday, August 3, 2020 6:13:17 PM
Subject: Re: [covidatlas/li] Saint Lucia data has a comma separated string for timeseries-byLocation.json on 07/27 (#353)
Hm, the source for St Lucia (in src/shared/sources/lc ) is hitting [ https://www.covid19response.lc/ | https://www.covid19response.lc/ ] ... looking at that page, everything looks fine, but running the source locally is returning trash:
MacBook-Air:li jeff$ ./start --crawl lc
MacBook-Air:li jeff$ ./start --scrape lc
┌─────────┬────────────┬──────────────┬───────┬────────┬─────────┬────────────────┐
│ (index) │ locationID │     date     │ cases │ deaths │ tested  │   recovered    │
├─────────┼────────────┼──────────────┼───────┼────────┼─────────┼────────────────┤
│    0    │ 'iso1:lc'  │ '2020-08-03' │ '25'  │  '0'   │ '3,548' │ '2229,630,598' │
└─────────┴────────────┴──────────────┴───────┴────────┴─────────┴────────────────┘
Looking into a fix, cheers! jz
—
You are receiving this because you commented.
Reply to this email directly, [ https://github.com/covidatlas/li/issues/353#issuecomment-668318955 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/ABBTK34BW7QZ3EWFVOUQO5LR65OC3ANCNFSM4PJBGKPA | unsubscribe ] .

I've merged a fix into master (ref https://github.com/covidatlas/li/pull/372), but this won't show up fixed in prod until I fix https://github.com/covidatlas/li/issues/368 -- we need to change how we launch code :-)
Thanks, I'll keep this issue and see that it's launched.

Thanks for the quick action!
Steve
From: "JZ"<EMAIL_ADDRESS>To: "covidatlas"<EMAIL_ADDRESS>Cc: "Steven Ganz"<EMAIL_ADDRESS>"Comment"<EMAIL_ADDRESS>Sent: Monday, August 3, 2020 6:58:12 PM
Subject: Re: [covidatlas/li] Saint Lucia data has a comma separated string for timeseries-byLocation.json on 07/27 (#353)
I've merged a fix into master (ref [ https://github.com/covidatlas/li/pull/372 | #372 ] ), but this won't show up fixed in prod until I fix [ https://github.com/covidatlas/li/issues/368 | #368 ] -- we need to change how we launch code :-)
Thanks, I'll keep this issue and see that it's launched.
—
You are receiving this because you commented.
Reply to this email directly, [ https://github.com/covidatlas/li/issues/353#issuecomment-668333455 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/ABBTK3YOFBKCB77TVGAPY4LR65TLJANCNFSM4PJBGKPA | unsubscribe ] .

This one was simple ... there are tons of other issues requiring more head scratching.  Thanks to you and @nateyoder for the check.  We really need to get data quality monitoring in place!!!  👋

Should be in production now, will keep this open until it's checked there.  @nateyoder or @stevenganz , if this clears up, please close the ticket.

Hi JZ,
Any idea when this will be reflected in the downloadable files (timeseries.csv.zip)?
Steve
From: "JZ"<EMAIL_ADDRESS>To: "covidatlas"<EMAIL_ADDRESS>Cc: "Steven Ganz"<EMAIL_ADDRESS>"Mention"<EMAIL_ADDRESS>Sent: Tuesday, August 4, 2020 5:39:45 AM
Subject: Re: [covidatlas/li] Saint Lucia data has a comma separated string for timeseries-byLocation.json on 07/27 (#353)
Should be in production now, will keep this open until it's checked there. [ https://github.com/nateyoder | @nateyoder ] or [ https://github.com/stevenganz | @stevenganz ] , if this clears up, please close the ticket.
—
You are receiving this because you were mentioned.
Reply to this email directly, [ https://github.com/covidatlas/li/issues/353#issuecomment-668571774 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/ABBTK3ZPKYNTEA6BRWV6HM3R676RDANCNFSM4PJBGKPA | unsubscribe ] .

It’s not there now?  Should be!
El El lun, ago. 10, 2020 a la(s) 2:57 p. m., Steven Ganz <
<EMAIL_ADDRESS>escribió:

Hi JZ,
Any idea when this will be reflected in the downloadable files
(timeseries.csv.zip)?
Steve
From: "JZ"<EMAIL_ADDRESS>To: "covidatlas"<EMAIL_ADDRESS>Cc: "Steven Ganz"<EMAIL_ADDRESS>"Mention" <
<EMAIL_ADDRESS>Sent: Tuesday, August 4, 2020 5:39:45 AM
Subject: Re: [covidatlas/li] Saint Lucia data has a comma separated string
for timeseries-byLocation.json on 07/27 (#353)
Should be in production now, will keep this open until it's checked there.
[ https://github.com/nateyoder | @nateyoder ] or [
https://github.com/stevenganz | @stevenganz ] , if this clears up, please
close the ticket.
—
You are receiving this because you were mentioned.
Reply to this email directly, [
https://github.com/covidatlas/li/issues/353#issuecomment-668571774 | view
it on GitHub ] , or [
https://github.com/notifications/unsubscribe-auth/ABBTK3ZPKYNTEA6BRWV6HM3R676RDANCNFSM4PJBGKPA
| unsubscribe ] .
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/covidatlas/li/issues/353#issuecomment-671529751, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMPWDIWDGZ3KRUUVVWBUR3SAA7LHANCNFSM4PJBGKPA
.

I'm still getting bad values for St. Lucia. Please check yourself.
From: "JZ"<EMAIL_ADDRESS>To: "covidatlas"<EMAIL_ADDRESS>Cc: "Steven Ganz"<EMAIL_ADDRESS>"Mention"<EMAIL_ADDRESS>Sent: Monday, August 10, 2020 12:27:57 PM
Subject: Re: [covidatlas/li] Saint Lucia data has a comma separated string for timeseries-byLocation.json on 07/27 (#353)
It’s not there now? Should be!
El El lun, ago. 10, 2020 a la(s) 2:57 p. m., Steven Ganz <
<EMAIL_ADDRESS>escribió:

Hi JZ,
Any idea when this will be reflected in the downloadable files
(timeseries.csv.zip)?
Steve
From: "JZ"<EMAIL_ADDRESS>To: "covidatlas"<EMAIL_ADDRESS>Cc: "Steven Ganz"<EMAIL_ADDRESS>"Mention" <
<EMAIL_ADDRESS>Sent: Tuesday, August 4, 2020 5:39:45 AM
Subject: Re: [covidatlas/li] Saint Lucia data has a comma separated string
for timeseries-byLocation.json on 07/27 (#353)
Should be in production now, will keep this open until it's checked there.
[ https://github.com/nateyoder | @nateyoder ] or [
https://github.com/stevenganz | @stevenganz ] , if this clears up, please
close the ticket.
—
You are receiving this because you were mentioned.
Reply to this email directly, [
https://github.com/covidatlas/li/issues/353#issuecomment-668571774 | view
it on GitHub ] , or [
https://github.com/notifications/unsubscribe-auth/ABBTK3ZPKYNTEA6BRWV6HM3R676RDANCNFSM4PJBGKPA
| unsubscribe ] .
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/covidatlas/li/issues/353#issuecomment-671529751, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMPWDIWDGZ3KRUUVVWBUR3SAA7LHANCNFSM4PJBGKPA
.

—
You are receiving this because you were mentioned.
Reply to this email directly, [ https://github.com/covidatlas/li/issues/353#issuecomment-671543578 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/ABBTK34OIQ3JLH7DXRFDZETSABC33ANCNFSM4PJBGKPA | unsubscribe ] .

I’ll check generation status and the data when I have a better connection.
Thx!
El El lun, ago. 10, 2020 a la(s) 3:47 p. m., Steven Ganz <
<EMAIL_ADDRESS>escribió:

I'm still getting bad values for St. Lucia. Please check yourself.
From: "JZ"<EMAIL_ADDRESS>To: "covidatlas"<EMAIL_ADDRESS>Cc: "Steven Ganz"<EMAIL_ADDRESS>"Mention" <
<EMAIL_ADDRESS>Sent: Monday, August 10, 2020 12:27:57 PM
Subject: Re: [covidatlas/li] Saint Lucia data has a comma separated string
for timeseries-byLocation.json on 07/27 (#353)
It’s not there now? Should be!
El El lun, ago. 10, 2020 a la(s) 2:57 p. m., Steven Ganz <
<EMAIL_ADDRESS>escribió:

Hi JZ,
Any idea when this will be reflected in the downloadable files
(timeseries.csv.zip)?
Steve
From: "JZ"<EMAIL_ADDRESS>To: "covidatlas"<EMAIL_ADDRESS>Cc: "Steven Ganz"<EMAIL_ADDRESS>"Mention" <
<EMAIL_ADDRESS>Sent: Tuesday, August 4, 2020 5:39:45 AM
Subject: Re: [covidatlas/li] Saint Lucia data has a comma separated
string
for timeseries-byLocation.json on 07/27 (#353)
Should be in production now, will keep this open until it's checked
there.
[ https://github.com/nateyoder | @nateyoder ] or [
https://github.com/stevenganz | @stevenganz ] , if this clears up,
please
close the ticket.
—
You are receiving this because you were mentioned.
Reply to this email directly, [
https://github.com/covidatlas/li/issues/353#issuecomment-668571774 |
view
it on GitHub ] , or [

https://github.com/notifications/unsubscribe-auth/ABBTK3ZPKYNTEA6BRWV6HM3R676RDANCNFSM4PJBGKPA

| unsubscribe ] .
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/covidatlas/li/issues/353#issuecomment-671529751,
or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAMPWDIWDGZ3KRUUVVWBUR3SAA7LHANCNFSM4PJBGKPA>

.

—
You are receiving this because you were mentioned.
Reply to this email directly, [
https://github.com/covidatlas/li/issues/353#issuecomment-671543578 | view
it on GitHub ] , or [
https://github.com/notifications/unsubscribe-auth/ABBTK34OIQ3JLH7DXRFDZETSABC33ANCNFSM4PJBGKPA
| unsubscribe ] .
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/covidatlas/li/issues/353#issuecomment-671581573, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMPWDNQJD5LL7LX6WELNLTSABMFHANCNFSM4PJBGKPA
.

I didn't check the report, but I edited the data in prod manually.
We don't yet have a process to correct historical data -- it's not as straightforward as one would think.  There's an open issue.
@stevenganz LMK if this is resolved.  I'm not easily able to check due to my extremely limited data bandwidth.  Cheers! z

Thanks and sorry for the delay in responding. The numbers look more reasonable now, but still contain commas for dates prior to 8/4. I'd appreciate if you could remove those.
From: "JZ"<EMAIL_ADDRESS>To: "covidatlas"<EMAIL_ADDRESS>Cc: "Steven Ganz"<EMAIL_ADDRESS>"Assign"<EMAIL_ADDRESS>Sent: Tuesday, August 11, 2020 7:17:42 AM
Subject: Re: [covidatlas/li] Saint Lucia data has a comma separated string for timeseries-byLocation.json on 07/27 (#353)
I didn't check the report, but I edited the data in prod manually.
We don't yet have a process to correct historical data -- it's not as straightforward as one would think. There's an open issue.
[ https://github.com/stevenganz | @stevenganz ] LMK if this is resolved. I'm not easily able to check due to my extremely limited data bandwidth. Cheers! z
—
You are receiving this because you were assigned.
Reply to this email directly, [ https://github.com/covidatlas/li/issues/353#issuecomment-671974326 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/ABBTK34PMR6KUHOILFQVNX3SAFHINANCNFSM4PJBGKPA | unsubscribe ] .

Strange, I'm sure I edited everything!  Not saying you're wrong, am saying that perhaps it was subsequently updated ... not sure why though.  Double-checking prod tables now.  Thanks for checking @stevenganz

Ah, I was only looking at the terrible "recovered" numbers.  I'm removing commas in "tested" now, assuming that's the field you meant.

OK, hopefully that's all the commas you can see for St Lucia, @stevenganz .  In a day-ish, let me know if all is as expected.  Thanks again, jz

Looks good now, @jzohrab. Thanks! Yes, the commas were in the tested column -- sorry for any confusion.
From: "JZ"<EMAIL_ADDRESS>To: "covidatlas"<EMAIL_ADDRESS>Cc: "Steven Ganz"<EMAIL_ADDRESS>"Mention"<EMAIL_ADDRESS>Sent: Sunday, August 16, 2020 1:16:33 PM
Subject: Re: [covidatlas/li] Saint Lucia data has a comma separated string for timeseries-byLocation.json on 07/27 (#353)
OK, hopefully that's all the commas you can see for St Lucia, [ https://github.com/stevenganz | @stevenganz ] . In a day-ish, let me know if all is as expected. Thanks again, jz
—
You are receiving this because you were mentioned.
Reply to this email directly, [ https://github.com/covidatlas/li/issues/353#issuecomment-674572632 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/ABBTK37R4YIHAZ4ZQRMDEXLSBA5CDANCNFSM4PJBGKPA | unsubscribe ] .


Hide »API / Examples(Tutorials)« navigation if there are no tutorials

Hej,
this JSDoc template really looks promising 💖
But I wonder if its possible to hide the navigation to switch between API and examples if a project comes without examples.
I would think that it should be hidden automatically if there is no tutorials property in the JSDoc configuration.

Would you accepts a pull request for that?

Released 1.0.4

👌


Translating the JSX code to TSX

Changing the existing Javascript to Typescript for simplified error handling.

Revert if necessarry


[Feature Request] Add option to hide permanent item effects from effect tray

Foundry version: v12, build 331
System: DnD5e 3.3.1
I have some magic items that have an active effect granted to the wearer, as well as temporary effects that are granted to a target, which may or may not be the actor owning the item. Right now, both the permanent as well as the temporary effects are shown in the effect tray and could, theoretically, be applied to other targets.
I would love for there to be an option that hides these permanent effects from the effect tray. This could be handled by singling out any AE that has "Effect Suspended" Unchecked and "Apply Effect to Actor" checked. These effects are (in my game, at least) never meant to be transferred to anyone other than the owner of the item, and thus take up unnecessary space. Worse, when Effective Tray grants players access to the effect tray, they might accidentally apply the wrong effect(s).
I don't know how feasible this is, but I figured it was worth a shot.

in my unmerged current branch, effects with 'Apply Effect to Actor' are already filtered out. would this alone (and not filtering out 'Effect Suspended') cover all your cases, too?
originally, i was going to wait until the system made this change (it was on a 4.0 milestone), but since the branch with it has been deleted, its fate is uncertain, so i will probably go ahead and merge this soon


Adding institutional domain alunos.fho.edu.br

@felipelavandeira Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course

@philipto here is the information you asked for:

school official website URL: http://fho.edu.br/home.php
school address : Av. Dr. Maximiliano Baruto, 500. Jd. Universitário | Araras - SP | Brazil
URL from IT-related course: http://vestibular.uniararas.br/cursos/?tag=sistemas-informacao

@felipelavandeira Thank you for the clarification. Pull request merged.


[Bug] Breaks Fragment Typings

when using this library, "Fragment" imported from React only expects a single child which defeats the purpose of using a fragment:
import {Fragment} from 'react';

function F() {
  return (
    // type error
    <Fragment>

    </Fragment>
  )
}

removing the import from @total-typescript/ts-reset fixed my issue

hmm went away for no reason probably typescript bug or something


Visual Studio Test v 2.* fails if no test sources found (used to work a few days ago with just a warning)

I have a generic task group for some of my projects in which some of them have tests and others don't.
Now every time I try to build a project with no tests assemblies the build task fails.
Previously the task would give me a warning, which was OK for me.
Is this something you've just changed in the latest version? can you put it back? or just add an option to not fail the task?
##[debug]Agent.Version=2.155.1
##[debug]Release.ReleaseUri=undefined
##[debug]Release.ReleaseId=undefined
##[debug]Build.BuildUri=vstfs:///Build/Build/2383
##[debug]Build.Buildid=2383
##[debug]telemetry area: TestExecution feature: TestExecutionTask data: {"builduri":"vstfs:///Build/Build/2383","buildid":"2383","state":"completed"}
##[debug]Processed: ##vso[telemetry.publish area=TestExecution;feature=TestExecutionTask;]{"builduri":"vstfs:///Build/Build/2383","buildid":"2383","state":"completed"}
##[error]Error: Preparing the test sources file failed. Error : Error: No test sources found matching the given filter 'test.dll,!TestAdapter.dll,!\obj*'
##[debug]Processed: ##vso[task.issue type=error;]Error: Preparing the test sources file failed. Error : Error: No test sources found matching the given filter 'test.dll,!TestAdapter.dll,!\obj*'
##[debug]task result: Failed
##[error]VsTest task failed.
##[debug]Processed: ##vso[task.issue type=error;]VsTest task failed.
##[debug]Processed: ##vso[task.complete result=Failed;done=true;]VsTest task failed.
Finishing: VsTest - testAssemblies

This has been hotfixed. Please re-open if you are still facing the issues with task version 2.161.4 or higher. Thanks

Hello, I'm also running into this issue @ShreyasRmsft and can't get 2.161.4 to download. I keep getting 2.161.2 (which errors out with no tests selected) even after using a VisualStudioTestPlatformInstaller job to try and update to latest. Any tips on how to get v2.161.4 to download as part of my job?

@logdog16 the roll-out was pending for one ring of accounts, give it a shot now.

There we go! Our hosted agents picked up the change overnight and our builds started working again this morning. Thank you :)

Closing the issue since this is resolved. Thanks.


Pulsar SQL can not query the latest ingested event in a topic , but  Pulsar Consumer/Read always can.

Describe the bug
Pulsar SQL can not query the latest ingested event in a topic , but  Pulsar Consumer/Read always can.
the testing Pulsar version is 2.4.0
from the two screenshots below, we can see the latest event is always missed in Palsar SQL. but Pulsar reader client can fetch the latest one correctly.
I am new to Pulsar but very interested in Pulsar. don't know this is a bug, or just a kind interesting feature which needs some hidden config I don't know yet?
Screenshots
this is the testing code and screenshot of Pulsar Reader:

this is the testing query SQL and  screenshot in Pulsar SQL CLI:

looking at the screenshots above, we can find  Pulsar Reader returns 5 records with the latest ingested event,  but Pulsar SQL only returns 4 records without the latest ingested event.   always missing one latest ingested event from Pulsar SQL while new event comes into Pulsar Topic

@frank-dkvan this is a known issue of #3828. because Pulsar doesn't flush LAC so when Presto SQL reads data from bookkeeper bypassing broker, it will miss the latest message because the advanced LAC is not flushed back.
The fix is waiting for BK 4.10 release.

@sijie got it! thanks

@frank-dkvan this is a known issue of #3828. because Pulsar doesn't flush LAC so when Presto SQL reads data from bookkeeper bypassing broker, it will miss the latest message because the advanced LAC is not flushed back.
The fix is waiting for BK 4.10 release.

I tested and found this bug  hasn't solved in latest 2.5.0 snapshot with BK 4.10 release yet.
will this bug get solved in 2.5.0 official release?

@frank-dkvan I think it requires a change at Pulsar side. since we are cutting 2.5.0 next week, I don't think we are able to include this in time. We can do this for 2.5.1 or 2.6.0.
you might be able to work around with 4.10 with a bk client configuraiton. @codelipenghui should be able to help you with this.

thanks @sijie
Hi @codelipenghui wld you pls help with this: providing more details on bk client configuration at pulsar side...sample code if any would be nice..thanks

@frank-dkvan @sijie I have create a new pull request #5822 for expose the config in broker.conf.

@frank-dkvan
I think you can add bookkeeperExplicitLacIntervalInMills=5 in the JVM system properties when starting the broker.

@sijie I think we need to use explicitLacInterval, this is the name in Bookkeeper client configuration. The bookkeeperExplicitLacIntervalInMills is named in broker side.

You are right!

@frank-dkvan
I think you can add bookkeeperExplicitLacIntervalInMills=5 in the JVM system properties when starting the broker.

Hi @codelipenghui   "5" means there would be  5-ms delay before we can see the latest message in Pulsar SQL?  Am I understanding correctly?

@frank-dkvan @sijie I have create a new pull request #5822 for expose the config in broker.conf.

Thanks @codelipenghui

close via #5822


Turn the remove-namespace kustomize function into a proper function.

Use a client side CRD so we can easily add more types
for which we need to remove the namespace.

Package it in the same docker image as our image-prefix kpt function.

Fix kubeflow/gcp-blueprints#27

Not ready for review but creating a PR so I don't forget about it.

/assign @Bobgy
This is ready for review.

/lgtm
/approve

/lgtm
/approve


JWT or API Key Auth

I'm going to do a little bit refactoring first

okay

yups, just need to take some screenshot for demo

If you're merging this because you're going to address reviewers request in the next PR, don't forget to inform us @DrSensor


docker-instructions for Windows

Need to resolve "Getting Started" instruction 2 to work for Windows

Working on creating a "mclp-web" version that will hopefully allow us to get around this problem.  Apparently this is an issue with using docker on windows and the mapped volume directory in the container must be empty or it causes problems. I'll update with what I find.
http://stackoverflow.com/questions/35315996/how-to-mount-a-docker-volume-while-using-a-windows-host

👍

I've updated the files to reflect the workaround.


add readepi and cleanepi logos

Please check if the PR fulfills these requirements

[ ] I have read the CONTRIBUTING guidelines
[ ] A new item has been added to NEWS.md
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

Thanks!


Bring back ignition from bookworm

What happened:
The ignition package has been removed from debian/testing. Since the _pxe feature requires the ignition package, we had to provide a replacement by uploading a self build variant of ignition:

https://gitlab.com/gardenlinux/gardenlinux-package-ignition

It has been removed from `bookworm´ because one of its build dependencies has been removed as well:

golang-github-pin-tftp

If we want to go back to the offical Debian package, we must ensure that golang-github-pin-tftp is available in testing again, so that ignition can be added again, too.
What you expected to happen:
The current solution is just a workaround to keep the Github Actions running. We should switch to the ignition package once it is available in debian/testing again.

Created an issue for the ignition dependency golang-github-pin-tftp.
https://github.com/pin/tftp/issues/68
Also created a patch for the golang-github-pin-tftp package to remove the problematic tests. Waiting for access to the project on Debian salsa to push the patch and create a merge request.

Done. Patch was excepted and golang-github-pin-tftp is back in Debian Sid.

Hi @chrinorse,
golang-github-pin-tftp is back in Debian testing again:

https://tracker.debian.org/news/1326471/golang-github-pin-tftp-220-3-migrated-to-testing/

In addition, ignition returned to Debian testing with a new version, too:

https://tracker.debian.org/news/1326719/ignition-2130ds1-4-migrated-to-testing/

This would allow us to remove our self-build ignition package and return to the Debian testing one. However, there is still the issue with golang-github-smartystreets-assertions, which is in Debian testing but will get removed on 13th of June if the following bug does not get resolved:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008443

It seems that the issue has been identified and that an upstream issue has already been opened:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008443#25

However, the problematic unit test is still part of the current Debian testing package.

Ignition and it's dependencies are back in Debian testing. Mission accomplished.


Fix imports

The current master branch is failing.

@h3xstream  - thanks a million, merge error! There is a failing unit test as well, will fix asap.


Option to add nonce value to style tag of vue3 web components

Description
When I create web components via custom elements in vue3 (as described here: https://vuejs.org/guide/extras/web-components.html#building-custom-elements-with-vue), the styles are loaded directly into the shadow dom with a <style> tag. In order to meet content security policies, I would need to include a nonce value to this style tag when building the web component. Otherwise the styles are rejected with the following error message:
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self' 'nonce-xxx='". Either the 'unsafe-inline' keyword, a hash ('sha256-xxx='), or a nonce ('nonce-...') is required to enable inline execution.

It would be great, if a nonce value could be applied to the style tags while building the
Suggested solution
Unfortunately, I don't know where these changes could be implemented
Alternative
No response
Additional context
No response
Validations

[x] Follow our Code of Conduct
[x] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

The style tag is inserted in vuejs/core, so the feature request should be made there instead.
A workaround is to create a wrapper for defineCustomElement that updates the shadow root's <style> with the desired nonce value:
import { defineCustomElement } from 'vue'
import HelloWorld from<EMAIL_ADDRESS>
const defineCustomElementWithNonce = (Comp: any, options?: { nonce: string }) => {
  const comp = defineCustomElement(Comp)

  if (typeof options?.nonce !== 'undefined') {
    const origApplyStyles = comp.prototype._applyStyles
    comp.prototype._applyStyles = function (styles: any) {
      origApplyStyles.call(this, styles)

      // add nonce to style element in shadow root
      if (styles) {
        const styleEl = this.shadowRoot.querySelector('style')
        styleEl?.setAttribute('nonce', options.nonce)
      }
    }
  }

  return comp
}

const HelloWorldElement = defineCustomElementWithNonce(HelloWorld, { nonce: /* nonce value pre-determined by server */ })

customElements.define('hello-world', HelloWorldElement)

thank you, that helped a lot. The only problem with that solution is that I need to have the nonce value before the style Tag is added to the DOM. But I will just write my own applyStyles method I guess.
Thanks a lot!

I'm not sure I understand the problem. Are you trying to add the nonce after the style is added to the DOM? What would your proposed _applyStyles do?

I just override the _applyStyles function, so the nonce attribute is added to the style tag before appendChild(style) is called. Like this:
  _comp.prototype._applyStyles = function (styles: string[]) {
    if (styles) {
      styles.forEach((css) => {
        const s = document.createElement('style')
        s.textContent = css
        s.setAttribute('nonce', options?.nonce || defaultNonce)
        this.shadowRoot?.appendChild(s)
        // record for HMR
        if (import.meta.env.DEV) {
          ;(this._styles || (this._styles = [])).push(s)
        }
      })
    }
  }

My reverse-proxy needs it like that.

Closing as this needs to be implemented on vue side.
@tony19 Thanks for the explanation!


Multi chain deployment script issues (Ledger, --verify)

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (903a073 2022-11-15T00:06:12.539932Z)
What command(s) is the bug in?
forge script scripts/FullMultiChain.s.sol:FullMultiChainDeployment --broadcast --private-key ${PRIVATE_KEY} --verify --multi -vvvv
Operating System
macOS (Apple Silicon)
Describe the bug
While trying out the new multi chain deployments from a same script I found a few issues.
While using private key for deployment it works correctly, but when using ledger it breaks.
command: forge script scripts/FullMultiChain.s.sol:FullMultiChainDeployment --broadcast --legacy --ledger --mnemonic-indexes ${MNEMONIC_INDEX} --sender ${LEDGER_SENDER} --verify -vvvv
error:

Script ran successfully.
Gas used: 4208925
Multi chain deployment is still under development. Use with caution.

## Setting up (2) EVMs.
==========================
Simulated On-chain Traces:

  [1670532] → new TransparentProxyFactory@0xc716bDC36D18D903FAC96D9f1491dCAe0B4A7544
    └─ ← 7505 bytes of code

  [446734] TransparentProxyFactory::createDeterministicProxyAdmin(0x6D603081563784dB3f83ef1F65Cc389D94365Ac9, 0x54db45112fa098101a2fad13c11ac68f40a4db2489b6578d89830146fa693ed8)
    ├─ [360715] → new ProxyAdmin@0xf3EE93c92342D5FfE50BA3E4E218055Ec0778D89
    │   ├─ emit OwnershipTransferred(previousOwner: 0x0000000000000000000000000000000000000000, newOwner: TransparentProxyFactory: [0xc716bDC36D18D903FAC96D9f1491dCAe0B4A7544])
    │   └─ ← 1683 bytes of code
    ├─ [2371] ProxyAdmin::transferOwnership(0x6D603081563784dB3f83ef1F65Cc389D94365Ac9)
    │   ├─ emit OwnershipTransferred(previousOwner: TransparentProxyFactory: [0xc716bDC36D18D903FAC96D9f1491dCAe0B4A7544], newOwner: 0x6D603081563784dB3f83ef1F65Cc389D94365Ac9)
    │   └─ ← ()
    ├─ emit ProxyAdminDeterministicCreated(proxyAdmin: ProxyAdmin: [0xf3EE93c92342D5FfE50BA3E4E218055Ec0778D89], adminOwner: 0x6D603081563784dB3f83ef1F65Cc389D94365Ac9, salt: 0x54db45112fa098101a2fad13c11ac68f40a4db2489b6578d89830146fa693ed8)
    └─ ← ProxyAdmin: [0xf3EE93c92342D5FfE50BA3E4E218055Ec0778D89]

  [1670532] → new TransparentProxyFactory@0xA07f8DbbB7ae008904470e10d54716baa7C73e3D
    └─ ← 7505 bytes of code

  [446734] TransparentProxyFactory::createDeterministicProxyAdmin(0x6D603081563784dB3f83ef1F65Cc389D94365Ac9, 0x54db45112fa098101a2fad13c11ac68f40a4db2489b6578d89830146fa693ed8)
    ├─ [360715] → new ProxyAdmin@0x788A5119e3437aDA6b1B3326DdEE98eb3Bf365b4
    │   ├─ emit OwnershipTransferred(previousOwner: 0x0000000000000000000000000000000000000000, newOwner: TransparentProxyFactory: [0xA07f8DbbB7ae008904470e10d54716baa7C73e3D])
    │   └─ ← 1683 bytes of code
    ├─ [2371] ProxyAdmin::transferOwnership(0x6D603081563784dB3f83ef1F65Cc389D94365Ac9)
    │   ├─ emit OwnershipTransferred(previousOwner: TransparentProxyFactory: [0xA07f8DbbB7ae008904470e10d54716baa7C73e3D], newOwner: 0x6D603081563784dB3f83ef1F65Cc389D94365Ac9)
    │   └─ ← ()
    ├─ emit ProxyAdminDeterministicCreated(proxyAdmin: ProxyAdmin: [0x788A5119e3437aDA6b1B3326DdEE98eb3Bf365b4], adminOwner: 0x6D603081563784dB3f83ef1F65Cc389D94365Ac9, salt: 0x54db45112fa098101a2fad13c11ac68f40a4db2489b6578d89830146fa693ed8)
    └─ ← ProxyAdmin: [0x788A5119e3437aDA6b1B3326DdEE98eb3Bf365b4]

==========================

Chain 5

Estimated total gas used for script: 2752445

Estimated amount required: 0.29019783444836731 ETH

==========================

==========================

Chain 43113

Estimated total gas used for script: 2752445

Estimated amount required: 0.068811125 ETH

==========================

###
Finding wallets for all the necessary addresses...

###
Finding wallets for all the necessary addresses...
##
Sending transactions [0 - 1].
⠉ [00:00:13] [####################################################################################################################################################] 2/2 txes (0.0s)##
Waiting for receipts.
⠙ [00:00:07] [################################################################################################################################################] 2/2 receipts (0.0s)
##### fuji
✅ Hash: 0xf75011fcada9978aeeb3cec7fd45ea921a4e7bea9056d9c268a6b37bb05e0b7e
Contract Address: 0xa07f8dbbb7ae008904470e10d54716baa7c73e3d
Block: 15859350
Paid: 0.0417633 ETH (1670532 gas * 25 gwei)

##### fuji
✅ Hash: 0x18d82180d5136fda63947ec674fa532ec9ea68537ba50995ca3056fe294f7f71
Block: 15859352
Paid: 0.0105114 ETH (420456 gas * 25 gwei)

==========================

ONCHAIN EXECUTION COMPLETE & SUCCESSFUL.
Total Paid: 0.0522747 ETH (2090988 gas * avg 25 gwei)

Transactions saved to: /Users/user/bgd/project/broadcast/multi/FullMultiChain.s.sol-latest/run.json

Error:
[Err(
Ledger device not available.

Context:
- hidapi error: hid_error is not implemented yet)]
make: *** [deploy-full-flow-ledger] Error 1

So I can sign the transactions on fuji, but when its time to sign on a different network (goerli) it breaks.
Also verification does not work with private key or ledger. I am adding the expected --verify flag, and have set up on foundry.toml the etherscan vars so i guess there should not be any need to add them to the command:
[etherscan]
mainnet = { key = "${ETHERSCAN_API_KEY_ETH}" }
avalanche= { key = "${ETHERSCAN_API_KEY_AVAX}" }
optimism= { key = "${ETHERSCAN_API_KEY_OP}" }

Don't know if i am missing some flag or maybe the toml config nees something else?
Thx for the help

Can you confirm if this is still an issue? I believe there's been some ledger fixes since this was created (=

Hey!
I can confirm I just ran into this same issue. The script successfully submits the transactions on the first chain, but throws the same error as above once the script reaches the point of switching to the second chain:
Error:
[Err(
Ledger device not available.

I can also confirm that I tested running a single-chain deploy script that submitted multiple transactions, using a Ledger to sign, and it worked perfectly fine. However, once trying a multi-chain script, the Ledger integration fails at the point of switching chains.
Full Logs
forge script DummyScriptMulti --sig "dummy()" --multi --sender REDACTED --broadcast -l
[⠢] Compiling...
No files changed, compilation skipped
Script ran successfully.
Gas used: 3668662
Multi chain deployment is still under development. Use with caution.

###
Finding wallets for all the necessary addresses...
##
Sending transactions [0 - 0].
⠁ [00:00:05] [###############################################################################################################] 1/1 txes (0.0s)##
Waiting for receipts.
⠉ [00:00:06] [###########################################################################################################] 1/1 receipts (0.0s)
##### sepolia
✅  [Success]Hash: REDACTED
Contract Address: REDACTED
Block: REDACTED
Paid: 0.0288 ETH (1982354 gas * 14.528 gwei)

==========================

ONCHAIN EXECUTION COMPLETE & SUCCESSFUL.
Total Paid: 0.0288 ETH (1982354 gas * avg 14.528 gwei)

Transactions saved to: /Users/REDACTED/git/app/broadcast/multi/DummyScriptMulti.s.sol-latest/dummy.json

Error:
[Err(
Ledger device not available.

Context:
- hidapi error: hid_error is not implemented yet)]

Reproduce error
Here's an example forge script to repro:
pragma solidity ^0.8.13;

import {Script} from "forge-std/Script.sol";

contract MyContract {
    function hi() external pure returns (string memory) {
        return "hi";
    }
}

contract DummyScriptMulti is Script {
    /// @notice SCRIPT ENTRYPOINT.
    // forge script DummyScriptMulti --sig "dummy()" --multi --sender [LEDGER_ADDRESS] --broadcast --verify
    function dummy() public {
        vm.createSelectFork("goerli");
        vm.startBroadcast();
        new MyContract();
        vm.stopBroadcast();

        vm.createSelectFork("sepolia");
        vm.startBroadcast();
        new MyContract();
        vm.stopBroadcast();
    }
}

with foundry.toml including
[rpc_endpoints]
goerli = "${GOERLI_RPC_URL}"
sepolia = "${SEPOLIA_RPC_URL}"

[etherscan]
goerli = { key = "${ETHERSCAN_API_KEY}", chain = "goerli" }
sepolia = { key = "${ETHERSCAN_API_KEY}", chain = "sepolia" }

and .env populated with
GOERLI_RPC_URL=
SEPOLIA_RPC_URL=
ETHERSCAN_API_KEY=

Marking as resolved
Unable to replicate the issue with the given instructions with minor modifications (holesky instead of goerli)
forge script DummyScriptMulti --sig "dummy()" --multi --broadcast --sender $SENDER --ledger succeeds
We've also since moved from Ethers to Alloy

I'm using ledger to deploy to multi-chain, the first one will verify successfully but the second one will always failed
Submitting verification for [src/xxx.sol:xxx] 0x....
Submitted contract for verification:
        Response: `OK`
        GUID: `...jbuqj...`
        URL: https://etherscan.io/address/0x...eb62d474...
Contract verification status:
Response: `NOTOK`
Details: `Pending in queue`
Warning: Verification is still pending... (7 tries remaining)
Contract verification status:
Response: `OK`
Details: `Pass - Verified`
Contract successfully verified
All (1) contracts were verified!
##
Start verification for (1) contracts
Start verifying contract `0x...eb62d474...` deployed on bsc

Submitting verification for [src/xxx.sol:xxx] 0x.....
Error: Encountered an error verifying this contract:
Response: `NOTOK`
Details:
                        `Invalid API Key (#err2)|bsc11`

so I have to use this commend one by one
forge verify-contract \
<contract_address> \
src/x.sol:x \
--chain bsc \
--etherscan-api-key $BASESCAN_API_KEY

This is my foundry.toml
[profile.default]
via_ir = true
src = "src"
out = "out"
libs = ["lib"]

[rpc_endpoints]
mainnet = "${ETHERUM_RPC_URL}"
bsc = "${BSC_RPC_URL}"
base = "${BASE_RPC_URL}"

[etherscan]
mainnet = { key = "${ETHERSCAN_API_KEY}", chain = "mainnet" }
bsc = { key = "${BSCSCAN_API_KEY}", chain = "bsc" }
base = { key = "${BASESCAN_API_KEY}", chain = "base" }

Not sure where do I do wrong.


Bufferframe is shallow copy, may lead to error [heap-use-after-free]

mBf point to a space which allocate by mBuffer, if out the scope， the mBuffer member will invoke its destructor function, and the mBf is invalid.

core reason
this is a shallow copy, the mBf rely on input argument bf's life cycle.

reproduce
in debug_tsan mode, call this variable is function will triger this error [heap-use-after-free]

some ideas

use std::unique_ptr move the ownership to member variable mBf
deep copy in Reset()

https://github.com/zz-jason/leanstore/actions/runs/10232967819/job/28310732700  reproduce this bug

Currently, the only usage of AsyncWriteBuffer is page evictor, refer to src/buffer-manager/AsyncWriteBuffer.cpp.
The shadow copy buffer frame address avoids unnecessary memory copy and additional memory consumption. These buffer frames are further given back to the user of AsyncWriteBuffer. The principles are:

BufferFrames are owned by the caller, not AsyncWriteBuffer.
The caller must guarantee these buffer frames stay valid until IterateFlushedBfs() is called.

So:

The easiest way to solve this issue is to change the test implementation.
We do need some debug checks to ensure these referenced buffer frames are valid. But buffer frames are never reclaimed once they are created since the leanstore daemon is initialized, this issue may never happen.


no matching manifest for linux/arm64/v8 in the manifest list entries on raspberry pi3+ running ubuntu server 20.04

Before you start, we need a little bit more information from you:
Use Case (delete as appropriate): Using Portainer at Home, Using Portainer in a Commerical setup.
Have you reviewed our technical documentation and knowledge base? Yes/No YES

Question:
Hi, i'm quite a newbe and I'm trying to install portainer on a raspberry pi3+ on which I've installed ubuntu server 20.04LTS.
Following a tutorial I've issued this command:
sudo docker pull portainer/portainer-ce:linux-arm

then I got this error message:
no matching manifest for linux/arm64/v8 in the manifest list entries

So at the moment I don't know how to resolve/continue.
Thank you.

This is what I used on 2 of my Swarms to install portainer on my docker install
version: '3.2'
services:
agent:
image: portainer/agent
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /var/lib/docker/volumes:/var/lib/docker/volumes
networks:
- agent_network
deploy:
mode: global
placement:
constraints: [node.platform.os == linux]
portainer:
image: portainer/portainer-ce
command: -H tcp://tasks.agent:9001 --tlsskipverify
ports:
- "9000:9000"
- "8000:8000"
volumes:
- portainer_data:/data
networks:
- agent_network
deploy:
mode: replicated
replicas: 1
placement:
constraints: [node.role == manager]
networks:
agent_network:
driver: overlay
attachable: true
volumes:
portainer_data:

Woooo, great Michael!!!
Yep, it worked!  :)

You are welcome glad it worked.....


remove duplicated/problem reporter tests; closes #4469

these were duplicated in the node unit tests, but they were causing problems in the browser tests.

Coverage remained the same at 94.078% when pulling 8fc271b72723a1113d903d2532a6f7c757d62d46 on boneskull/issue/4469 into 31116dbf825487490d5416c95b2685e18e7359d3 on master.


Added the quote to the website

Hey @Mark-42-max , I have added the quote to the website. Please kindly review it and accept/merge my pull request.
Thank you.

Hey bro @Mark-42-max , now I have not touch anyone's code still it is showing some type of conflict. I Only added my quote at the end of index.html file.Please resolve this

Accha one thing. Did you update your fork before sending the PR? Please check this once and if not, update your fork with the actual repository. Then send the pull request again


Facebook share count not working; Possible fix found

The facebook share count is not working because FQL request keeps returning this error:
"(#4) Application request limit reached",
You can also observe the error in action on the example page here:
http://sharrre.com/example1.html
I succeeded in fixing this by changing from FQL to restserver.php. In jquery.sharrre.min.js I replaced this:
facebook: "https://graph.facebook.com/fql?q=SELECT url, normalized_url, share_count, like_count, comment_count, total_count,commentsbox_count, comments_fbid, click_count FROM link_stat WHERE url='{url}'&callback=?",
with this:
facebook: "http://api.facebook.com/restserver.php?method=links.getStats&urls={url}&format=json&callback=?",
Not sure if there are any drawbacks to this fix, for now it seems to be working well.

The old REST API will be deprecated on April 30th 2015. Using the /fql endpoint without an app access token will result in request limit errors.
The only official endpoint usable will  be /?id={url}, see https://developers.facebook.com/docs/graph-api/reference/v2.2/url


PokemonOptimizer keep Pokemon base on current candy count and required candy to evolve

Short Description

Keep Pokemon based base on current candy count and required candy to evolve. For example, keep 0 Pidgeys if you have <12 Pidgey candies, keep 2 Pidgeys if you have 13-23 candies, etc. (since it takes 12 candies to evolve a Pidgey).
Possible solution

Math/modulo + a list of required candies per Pokemon
How it would help others

That way the PokemonOptimizer can be used to keep certain "farmable" Pokemon for lucky egg XP farming without completely filling up the bag. I've had times when my bag was completely full since the PokemonOptimizer kept like 70 Pidgeys although I had only like 2 candies.

Pokemon Optimizer only transfer after free Pokemon slots get lower than a certain value (default 5). Are you sure that even after transfering it still keeps 70 Pidgeys?

That is very very strange since the Pokemon Optimizer does much more than just keeping the Pokemon for xp. It computes exactly how many Pokemon it should keep based on the number of candies you have and the number of candies you will get by transferring Pokemon.
Do you have the log of a run of the PokemonOptimizer where, after the run, you see in your inventory that there is Pidgey that should either be transferred or evolve ?

@Anakin5 Is there a config setting for the Pokemon Optimizer to be smart and "candy-aware"? Because by default top is 0, which means all Pokemon will be kept.

I do not understand your question.
By default, if you do not define any rules, no Pokemon will be kept. If you define a rule and do not define "top", all Pokemon matching the rule will be kept.
The evolve_for_xp does take candies into account, you do not have to take care of that in your configuration. As I said earlier, it is going to keep exactly the number of Pokemon that can be evolved with the number of candies you have.

@Anakin5 hey is there any way to force some pokemon to always eligible for evolve_for_xp, regardless of 2% rule?

I think I'm misunderstanding the configs. Basically I just want to do the following:

Keep all Pokemon above 0.9 IV
Only keep the minimum number of farmable Pokemon (list below) for XP evolving with a lucky egg
Don't touch the super rare Pokemon

Here is what I came up with the config:
{
    "type": "PokemonOptimizer",
    "config": {
        "enabled": true,
        "min_slots_left": 99999,
        "transfer": true,
        "transfer_wait_min": 1,
        "transfer_wait_max": 3,
        "evolve": true,
        "evolve_time": 23,
        "evolve_for_xp": true,
        "evolve_only_with_lucky_egg": true,
        "evolve_count_for_lucky_egg": 80,
        "may_use_lucky_egg": true,
        "upgrade": false,
        "upgrade_level": 60,
        "groups": {
        },
        "rules": [
        {
            "mode": "by_pokemon",
            "names": ["Articuno", "Lapras", "Mew", "Mewtwo", "Moltres", "Snorlax", "Zapdos", "Dragonite", "Arcanine"],
            "keep": true
        },
        {
            "mode": "by_pokemon",
            "names": ["Caterpie", "Ekans", "Goldeen", "Krabby", "Pidgey", "Rattata", "Psyduck", "Paras", "Spearow", "Tentacool", "Poliwag", "Weedle", "Zubat", "Staryu"],
            "sort": ["iv"],
            "evolve": true,
            "upgrade": false
        },
        {
            "mode": "by_pokemon",
            "keep": {"iv": 0.9},
            "evolve": false,
            "upgrade": false
        }
        ]
    }
}

With this setting, my bag would get full when the my candies for the farmable Pokemon gets low, which usually happens after a mass evolve with a lucky egg.

@hobbes3
It is almost good, but just almost.
{
    "mode": "by_pokemon",
    "names": ["Caterpie", "Ekans", "Goldeen", "Krabby", "Pidgey", "Rattata", "Psyduck", "Paras", "Spearow", "Tentacool", "Poliwag", "Weedle", "Zubat", "Staryu"],
    "sort": ["iv"],
    "evolve": true,
    "upgrade": false
},

This rule probably does not do what you think it does. This is going to keep all these Pokemon. That is why you have the problem you are talking about. You do not need that rule at all.
The evolve_for_xp works alone and independently from your rules.
@kureijir
Cannot deactivate it yet but I was thinking about just that yesterday and I am thinking I might open a parameter for that.

@Anakin5 Thanks for the answer. Are you saying the evolve_for_xp will allow a list of Pokemon in a future merge? Or it can get take a list now?

There is PR already, it is for future merge. For now, it is just true or false with the 2% rule to ensure we use Pokemon you have in big quantities in your bag.

@hobbes
If you want to handle these Pokemon with a rule rather than evolve_for_xp, you can consider adding for example keep: {"iv": 0.8} to the rule I mentioned earlier. It is not going to be as effective as evolve_for_xp but it will be restricted to the Pokemon you listed.


Greased line plugin: Fix crash when cloning the material

See https://forum.babylonjs.com/t/greased-line-doesnt-work-with-right-handed-system/42976/17

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14179/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14179/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14179/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14179/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14179/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14179/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14179/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14179/merge#BCU1XR#0


Cannot specify location name in geocoding.dart api

typo in geocoding.dart class line 21 : String args = (createNullableParam("name", name) instead of String args = (createNullableParam(name, "name")

Whoops, thanks for noticing. Fixed in a83ea96. Pushed this change on version 1.0.6.

Whoops, thanks for noticing. Fixed in a83ea96. Pushed this change on version 1.0.6.


Set up redirects and new urls for transpile -> optimize for hardware section

The transpile section is being renamed to "optimize for hardware", the url should be updated accordingly and redirects set up.
Question: how verbose should we make the url? I'm open to either of the following options:

/optimize-for-hardware/page-name
/optimize/page-name
some other option?

superseded by https://github.com/Qiskit/documentation/issues/1297


[Chore] Deprecate AppRollout and remove the CRD and controller in v1.2

AppRollout has become a  rollout trait in v1.1, we should deprecate the usage of AppRollout and remove the legacy code.

Is it related to #2322

I am interested in working on this issue
/assign


[fix] producer do not create when topic update partition

Motivation
When topic update partition, new producer is not created on the new partition. The root is runPartitionUpdateTask not work well.
Modifications
runPartitionUpdateTask should be executed next time when partition not updated.
Verifying this change

[x] Make sure that the change passes the CI checks.

Documentation

[x] doc-not-needed
(Please explain why)

It's better to add a test. The current logic is protected by https://github.com/apache/pulsar-client-cpp/blob/main/tests/PartitionsUpdateTest.cc

I have improved previous PartitionsUpdateTest to verify the problem and fix.

nice fix.

It might also fix https://github.com/apache/pulsar-client-cpp/issues/50, which was closed due to no reproduce code.


Not working anymore after upgrade to Home Assistant 2023.12

Not working anymore after upgrade to Home Assistant 2023.12

I too am having issues after upgrading to 23.12. I have three instances running (price with grid tariffs, pure electricity price and electricity minus tax which is the sales price for my solar), only the first one works now. The other two broke after i updated on Saturday, started working again on Sunday and are now broken again. Luckily the one that works is the only one I use for automations...
I found this in the logs, no idea what to make of it...

Denne feilen stammer fra en tilpasset integrasjon.
Logger: custom_components.entsoe.coordinator
Source: helpers/update_coordinator.py:300
Integration: ENTSO-e Transparency Platform (documentation, issues)
First occurred: 9. desember 2023 kl. 23:07:33 (1089 occurrences)
Last logged: 11:08:33
Unexpected error fetching ENTSO-e coordinator data: ValueError: Template error: float got invalid input 'unknown' when rendering template '{% set s = {"cert": 0.01,"eur": float(states('sensor.kurs_eur')) } %} {{(current_price * s.eur + s.cert) | float}}' but no default was specified
Unexpected error fetching ENTSO-e coordinator data: ValueError: Template error: float got invalid input 'unknown' when rendering template '{% set s = {"eur": float(states('sensor.kurs_eur')) } %} {{(current_price * s.eur) | float}}' but no default was specified
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1916, in forgiving_float
return float(value)
^^^^^^^^^^^^
ValueError: could not convert string to float: 'unknown'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 569, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2247, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/jinja2/environment.py", line 1301, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.11/site-packages/jinja2/environment.py", line 936, in handle_exception
raise rewrite_traceback_stack(source=source)
File "
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 300, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/entsoe/coordinator.py", line 102, in _async_update_data
parsed_data = self.parse_hourprices(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/entsoe/coordinator.py", line 87, in parse_hourprices
hourprices[hour] = self.calc_price(value=price, fake_dt=hour)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/entsoe/coordinator.py", line 77, in calc_price
template_value = self.modifyer.async_render(now=faker(), current_price=price)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 571, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unknown' when rendering template '{% set s = {"cert": 0.01,"eur": float(states('sensor.kurs_eur')) } %} {{(current_price * s.eur + s.cert) | float}}' but no default was specified

I completely removed and reinstalled the integration yesterday, still the same issue with some of the sensors periodically not working. But it's always the same ones not working, the only difference is the template adding the grid tariff. I also added two more instances, identical to the working one and one of the non-working ones but with some extra for the temporary cost compensation we have. (I have little idea how the templates work, just copying other peoples work btw.) Of those two the one based on the working sensor also work, and the one based on the broken one is also broken... So it seems related to something in the templates?
These are the templates, maybe someone with a better understanding of how this works can figuere something out...
Price with grid tariff (working): (this one has vat set in the integration directly)
{% set s = {"day": 0.4855,"night": 0.3480,"cert": 0.0125,"eur": float(states('sensor.kurs_eur'), 10) } %} {% if now().hour >= 6 and now().hour < 22 %}{{(current_price * s.eur + s.day + s.cert) | float}} {% else %}{{(current_price * s.eur + s.night + s.cert) | float}} {% endif %}

Price without grid tariff (broken):
{% set s = {"cert": 0.01,"eur": float(states('sensor.kurs_eur')) } %} {{(current_price * s.eur + s.cert) | float}}

Sale price (broken):
{% set s = {"eur": float(states('sensor.kurs_eur')) } %} {{(current_price * s.eur) | float}}

Price with grid tariff and compensation (working):
{% set s = {"vat": 1.25,"day": 0.4855,"night": 0.3480,"cert": 0.01,"eur": float(states('sensor.kurs_eur'), 10) } %} {% set pb = max(((current_price * s.eur * s.vat) - 0.875) * 0.9, 0.0) %} {% if now().hour >= 6 and now().hour < 22 %}{{(current_price * s.eur * s.vat + s.day + s.cert - pb) | float}} {% else %}{{(current_price * s.eur * s.vat + s.night + s.cert - pb) | float}} {% endif %}

Price with compensation (broken):
{% set s = {"vat": 1.25,"cert": 0.01,"eur": float(states('sensor.kurs_eur')) } %} {% set pb = max(((current_price * s.eur * s.vat) - 0.875) * 0.9, 0.0) %} {{(current_price * s.eur * s.vat + s.cert - pb) | float}}

One more thing: If I try to change the settings for one of the broken ones, even without changing anything i get an template error when trying to submit the change. When they are working they accept the same template with no complaint...
@JaccoR I hope you can find the time to look into this, let me know if there is anything I can more do to help out!

OK, so I'm not alone...
For once I update immediatly...

Give the update you a solution ???  and yes how did you do the update.  A complete remove an fresh install ???

Solve the issue, by moving entsoe from the dir /config/custom_components/hacs/entsoe to /config/custom_components/entsoe

I've had problems too involving a refresh of the dates in the sensor . The dates got all mixed up after midnight: yesterday prices were tomorrow prices in the attributes. I deleted first the entry in integration and removed it from HACS WITH a restart of HA and reinstalled it. This didn't resolve the issue I was having. I then again removed it as mentioned earlier WITHOUT a restart of HA and downloaded the integration again from HACS. This seems to resolve the issue and pull in the correct dates. Now I still have to perform a restart from HA. Fingers crossed everything is kept in place this time.

v0.4.0 is released this version contains fixes that solve a lot of warnings and known issues. This issue is probably also solved.
Please update to the latest version.
Closing this issue for now. If you still have issue please feel free to open a new issue.


[CLOUD-2453][KEYCLOAK-7098] Deploy RH-SSO pod only if DB service is ready

, when provisioning from DB RH-SSO templates
Signed-off-by: Jan Lieskovsky<EMAIL_ADDRESS>

@rcernich @Crumby PTAL (once got a chance)
Thank you, Jan


@NamedDynamoDbTable applicable to parameters would enable constructor injection

Copy from https://github.com/quarkusio/quarkus/issues/42647#issue-2475465827
Description
Currently it is not possible to have
private final DynamoDbTable fooTable;
FooDao(@NamedDynamoDbTable("Foo") fooTable) {
this.fooTable = fooTable
}
Because @NamedDynamoDbTable is not applicable to method parameters. Would this be feasible?
Implementation ideas
No response

@nicklasweasel For implementation ideas, you can wider the targets of the annotation and add support for them here
https://github.com/quarkiverse/quarkus-amazon-services/blob/e17bb8c75d4ad34726618478e228faabebbbbb93/dynamodb-enhanced/deployment/src/main/java/io/quarkus/amazon/dynamodb/enhanced/deployment/DynamodbEnhancedDbTableProcessor.java#L79

Yep. There could be a  static final "allowed kind" collection and then "if kind not in list then continue" which would get rid of the wide if in the loop. And then the allowed location of the annotation itself.
Any specific test one could use as basis for unit testing? And are there any basic docs on how to set up the development environment?


Break time reset when editing working day

When editing a working day entry, the form field for 'break time' is not set to the break time of the entry (0 instead).
This easily leads to losing the break time.

Thanks for the report!


Bug 2021668: Respect cluster_subdomain setting

There was a regression where the cluster_subdomain key was not being
used when creating dvm routes. This PR allows the cluster_subdomain to
be overridden when creating routes.
Additionally, this PR grabs the subdomain from the OpenShift's cluster
ingress config (supported since 4.3
https://docs.openshift.com/container-platform/4.3/networking/ingress-operator.html),
allowing crane-lib's endpoint functionality to handle scenarios where
the route name would be too long.
Add the config API to the manager's scheme as that is automatically used
in migration cluster client schemes.

This is a cherry-pick of #1231

cc @alaypatel07 @pranavgaikwad


Allow more specific trusted domains rule

1.40.0-insider
31f577ec88dc96ad2028699fb597b19022224b46
x64
At some point I had chosen "Trust all domain".
When I now edit the trusted domains using Manage Trusted Domains and remove the * from the list there is no effect. I can still access all domains without any problem.
In stable, this works as expected.

I'm on the same commit.
Version: 1.40.0-insider
Commit: 31f577ec88dc96ad2028699fb597b19022224b46
Date: 2019-10-30T05:36:49.155Z
Electron: 6.1.2
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Darwin x64 18.7.0
And this does not reproduce for me.
What I tried:

Run Manage Trusted Domains
Open an untrusted link in markdown by Cmd+Click

Where in the workbench is the protected link? Also, did you run save in the "Manage Trusted Domains" tab? If not it won't persist the rules.

What we learned after chatting:

Currently, a rule like https://foo.com/bar allows ALL links on https://foo.com
For next month, we should start allowing rules more specific than a domain, so https://foo.com/bar would make below accessible:

https://foo.com/bar
https://foo.com/bar/baz

Verifier:

Add rules such as https://foo.com/bar with command Manage Trusted Domains
Make sure https://foo.com/bar, https://foo.com/bar/baz are accessible
Make sure https://foo.com/baz, https://foo.com/bar2 etc are unaccessible


[SMALLFIX] Various improvements.

This PR makes fixes various minor issues:

removes duplicate call to stop the worker metrics system
uses the proper API (as opposed to sleeping in a loop) to wait for the data server executor groups to shutdown; this speeds up integration tests from 4:50 to 4:30 on my machine
replaces unnecessary protectedqualifiers  with private

LGTM

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11226/
Test PASSed.

Merged build finished. Test PASSed.

Thanks for this improvement, 20 seconds is a ton when you multiply by the number of times the build runs.

LGTM, left one nit

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11233/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11232/
Test PASSed.

Merged build finished. Test PASSed.


Add VPC creation instructions to AWS doc

@TrimBiggs What's your plan for getting this merged?

@tomdee I'll be updating this PR soon with some additional info I've found, then looking for a review.

Fixes #490

LGTM

Fixes #490