Add "print task tree only" option to luigi

Description
Consider a debugging/review command-line option to print task dependency trees in a hypothetical run.
 If so, how?
Well this isnt perfect yet. I need some help fitting this in to the proper place in the command line execution.

Sometimes when you're developing an ETL you want to view the tasks in a dependency tree and their state before you decide on what to execute.
By adding this --print-tree option, the task does not execute. It outputs the tree instead

I think a seperate binary makes more sense in this case. Like see luigi-grep and luigi-deps

This is sweet! Very useful for when you can't access the UI (e.g. for a static report of what a pipeline ran)

Arash is right, this should be in the luigi-deps binary.
The problem is that the code varies widely between what I get with a "pip
install" and what is the latest in github.
I have made changes for my local environment but I still need to make a
version compatible with the latest code.
The newest version of the code is much nicer though. I'll be in touch when
i have more time.
On 10 May 2016 at 22:31, Jason Piper<EMAIL_ADDRESS>wrote:

This is sweet! Very useful for when you can't access the UI (e.g. for a
static report of what a pipeline ran)
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/spotify/luigi/pull/1680#issuecomment-218346385

--
Peter Weissbrod
http://RealLifeData.com | O:<PHONE_NUMBER> | M:<PHONE_NUMBER>

Okay, let us know when you want a second batch of review @PeteW.
Also, what I meant was actually something like a third binary, instead of luigi-deps you create a command like luigi-dependencytree, luigi-asciitree or luigi-asciideps (pick a cool yet informative name).

Well, THAT actually makes things even easier for me, thank you.
By the way: Question: how do I know the tag which matches the version of
luigi I get from [pip install]?
On 16 May 2016 at 22:07, Arash Rouhani<EMAIL_ADDRESS>wrote:

Okay, let us know when you want a second batch of review @PeteW
https://github.com/PeteW.
Also, what I meant was actually something like a third binary, instead of
luigi-deps you create a command like luigi-dependencytree, luigi-asciitree
or luigi-asciideps (pick a cool yet informative name).
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/spotify/luigi/pull/1680#issuecomment-219601040

--
Peter Weissbrod
http://RealLifeData.com | O:<PHONE_NUMBER> | M:<PHONE_NUMBER>

how do I know the tag which matches the version of luigi I get from

If you provide the github URL you'll get the latest and greatest. Which usually does not correspond to a pinned version.

I chose deps-tree as the name because it serves the identical purpose of deps, just in a tree type format. The output has been adjusted to make a better tree representation
+---[FactData-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
|--[S3ToRedshift-{'startdate': '2015-01-01', 'tablename': 'data', 'enddate': '2016-06-01'} (PENDING)]
|  +---[DplToS3Upload-{'startdate': '2015-01-01', 'tablename': 'data', 'enddate': '2016-06-01'} (PENDING)]
|--[FactDataTransaction-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
|  |--[S3ToRedshift-{'startdate': '2015-01-01', 'tablename': 'datatransaction', 'enddate': '2016-06-01'} (PENDING)]
|  |  +---[DplToS3Upload-{'startdate': '2015-01-01', 'tablename': 'datatransaction', 'enddate': '2016-06-01'} (PENDING)]
|  |--[System1FactDataBundle-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
|  |  +---[System1DataTransactionLinkEtl-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
|  +---[System2FactDataBundle-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
|--[FactDataTransactionServiceCode-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
|  |--[S3ToRedshift-{'startdate': '2015-01-01', 'tablename': 'datatransactionservicecode', 'enddate': '2016-06-01'} (PENDING)]
|  |  +---[DplToS3Upload-{'startdate': '2015-01-01', 'tablename': 'datatransactionservicecode', 'enddate': '2016-06-01'} (PENDING)]
|  |--[System1FactDataBundle-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
|  |  +---[System1DataTransactionLinkEtl-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
|  +---[System2FactDataBundle-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
|--[FactDataTransactionRtpCode-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
|  |--[S3ToRedshift-{'startdate': '2015-01-01', 'tablename': 'datatransactionrtpcode', 'enddate': '2016-06-01'} (PENDING)]
|  |  +---[DplToS3Upload-{'startdate': '2015-01-01', 'tablename': 'datatransactionrtpcode', 'enddate': '2016-06-01'} (PENDING)]
|  |--[System1FactDataBundle-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
|  |  +---[System1DataTransactionLinkEtl-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
|  +---[System2FactDataBundle-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
+---[FactDataTransactionAdjustment-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
|--[S3ToRedshift-{'startdate': '2015-01-01', 'tablename': 'datatransactionadjustment', 'enddate': '2016-06-01'} (PENDING)]
|  +---[DplToS3Upload-{'startdate': '2015-01-01', 'tablename': 'datatransactionadjustment', 'enddate': '2016-06-01'} (PENDING)/
|--[System1FactDataBundle-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
|  +---[System1DataTransactionLinkEtl-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)]
+---System2FactDataBundle-{'startdate': '2015-01-01', 'enddate': '2016-06-01'} (PENDING)

Requesting a second review

Please also add a binary with a name like luigi-deps-tree. I found the luigi- prefix to be essential, as the typical  real usecase to discover this tool is by using the shells auto-completion.

Also, add at least one test case for this. Here's an example we use for the deps binary.

[Current coverage][cc-pull] is 76.17%

Merging [#1680][cc-pull] into [master][cc-base-branch] will decrease coverage by 2.60%

@@             master      #1680   diff @@
==========================================
  Files            94         95     +1
  Lines         10324      10358    +34
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           8133       7890   -243
- Misses         2191       2468   +277
  Partials          0          0

Powered by Codecov. Last updated by [859095a...2e46e87][cc-compare]
[cc-base-branch]: https://codecov.io/gh/spotify/luigi/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/spotify/luigi/compare/859095a106864ef11176fbe03c3bb8f8a4c3ad42...2e46e8706a6bfa6c91680feea006eb1300caf003
[cc-pull]: https://codecov.io/gh/spotify/luigi/pull/1680?src=pr

Comments, a test, and the binary have been added. I also couldn't resist adding color based status display. I hope it's in line with the rest of the project this time around. The conventions and tooling in this project have taught me quite a bit about how to write better python

Let me know if there is anything else needed

Wow, thanks! This last merged revision looks really clean! :)

Is it possible to get the same result in JSON via CLI so it's more machine-readable?

certainly possible.
two ways this could be done:

update deps-tree.py with a new option for json format output
add new deps-json.py which uses very similar code to deps-tree but
outputs json

Personally I recommend the latter
On 13 October 2016 at 10:13, Ivan Smirnov<EMAIL_ADDRESS>wrote:

Is it possible to get the same result in JSON via CLI so it's more
machine-readable?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spotify/luigi/pull/1680#issuecomment-253525009, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACUWyHTSjKk0hmjT5msuOKvGTYLDwA6jks5qzjyFgaJpZM4IYlSn
.

--
Peter Weissbrod
http://RealLifeData.com | O:<PHONE_NUMBER> | M:<PHONE_NUMBER>

I actually created a JSON version today. I currently have it as a separate command heavily inspired by luigi-deps-tree (read: copied over with minor changes). I see @PeteW recommended a separate command, but if people feel like it would be better to include it as an option in luigi-deps-tree I'm happy to do it that way.
I will need to add tests etc. before it would be ready for a PR but I should be able to open it soonish.

I think both options are fine. I think I also prefer it being invoked by a command line switch.


Added the speakers to Home APP, but they do nothing

I installed, configured the plugin and added all my speakers to Home App. But it does nothing. I'm unable to play music to it nor see what is playing. I do not see any errors on my home bridge logs. What exactly am I missing?

Same here

I can Play and Pause The Last Station only

Same here. They appear in the Home app but I can not use them for anything. What can we do to make them work?
regards Praktiker.

Same issue here, speakers added to the Home app successfully, however they're stuck in the Stopped state regardless of  actual playing status. Additionally, screensAsTelevisions is doing nothing for me, as Show devices are showing as TVs despite it being set to false.
I am currently testing a modified version of the plugin that adds my local Amazon Domain (.com.mx) before I submit a pull request for it. I thought perhaps things were only broken for me, but seeing as others have this issue too, I'm dropping by.

+1

+1

+1

Obviously they don't work because they are not verified by Apple, the only thing you can do is check the device on the current media.


[WIP] Add Pathfinder and Multi Pathfinder

Submission Checklist

[x] Run unit tests: ./runTests.py src/test/unit
[x] Run cpplint: make cpplint
[x] Declare copyright holder and open-source license: see below

Summary
Adds Pathfinder and Multi pathfinder to the service APIs. This is a WIP until I add the final tests some individual functions inside of single pathfinder, but I think both algorithms are ready for review. Both algos can be found in src/stan/services/ along with the functions for generating PSIS weights for multi pathfinder.
Intended Effect
How to Verify
This PR needs a few more tests for some functions used in single pathfinder. But I had tests for the psis functions as well as higher level tests for single and multi-pathfinder that can be run with
./runTests.py -j4 ./src/test/unit/services/pathfinder/*

Side Effects
I think mostly what we want to verify is that the functions in single pathfinder lineup with the math in the paper.
Also I'm happy to delete the debug functions, though they should be essentially no-ops without any of the macros turned on and are nice for debugging.
Documentation
Docs added for each function that is more than encapsulating a one liner.
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company): Steve Bronder
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

(it says +20k lines but that's mostly just from the glm test csv)

This somehow got buried in my email, but I can review tomorrow or Friday.

I would like to have @rok-cesnovar review the matrix efficiency in all of this, but the basic code looks good.

Will do! Requested my review so I don't forget.

Thanks, @rok-cesnovar.  I think it'll be easiest to do this after the fixes are in for all the change requests Lu and I made.  At that point, we really only need the matrix algebra reviewed for efficiency.  I'm much less worried about inefficiency than incorrectness, so it'd also be OK to skip the efficiency review or save it for later.

I think it'll be easiest to do this after the fixes are in for all the change requests Lu and I made. At that point, we really only need the matrix algebra reviewed for efficiency.

Yes of course. Fully agree.

I resolved the issues that I think are resolved.  Sorry there were so many comments in this---it's a massive PR!
I'm happy to add all of the little doc things that I highlighted if you don't want to.  I actually enjoy writing doc.

I ripped out all the parallelization stuff in single pathfinder. I need to answer a few more of the comments and fixup the docs and then I think this will be ready to be looked at again

Hey @SteveBronder, I think the UNSTABLE Jenkins status is an old unintended bug #3166. Fixing develop in should sort it out.

So I think this is all going well now and is ready for review (as long as tests pass).
Just for future reference, I have a version of this locally that does single pathfinder concurrently with the lbfgs iterations. It gives about a 15-20% speedup for single pathfinder but there's a few gotchas that would need to be sorted out if we want to use it in develop. I think for now it's better that we just use a single threaded single pathfinder, but I wrote the below for reference if someone has this idea in the future and wants to work on it.
Each pathfinder iteration only depends on the last lbfgs iteration so we can do a queue scheme. After each lbfgs iteration we copy the inputs needed for that pathfinder iteration, spawn a job in the thread pool, and store the results of the job in a concurrent queue. Then we spawning thread checks the queue to see if new/better results are available and if so updates the best known pathfinder iteration.
This gets bad in multi-pathfinder, where if someone has 8 cores and does multi-pathfinder with 8 single pathfinders, those jobs spawned from the single pathfinder are just going to sit around until a thread is available to start running them. Since in this case all 8 cores are used by all 8 pathfinders we will have tons of copies of the pathfinder job inputs sitting around.
I think the only easy way to resolve this for multi-path users is to look at the number of threads available and the number of single pathfinders in used in the multi pathfinder. If its 1:1 (8 cores / 8 pathfinders) then we have no concurrent jobs, if we have 2:1 (16 cores / 8 pathfinders) then we have 1 concurrent job per pathfinder. Though I think making the main threads wait while their jobs finish would add other overhead we'd have to think about
So because of the above I think it's better we don't do the concurrent scheme atm

per discussion:   add arg to multi-pathfinder signature save_pathfinder_iterations

does this PR include changes to stan::callbacks::unique_stream_writer ?
plugging this branch into CmdStan and running example model bernoulli.stan with the sampler results in this segfault (traceback from gdb)
(gdb) info stack
#0  0x00007ff81555be7d in ?? ()
#1  0x0000000100165f60 in vtable for stan::callbacks::unique_stream_writer<std::__1::basic_ostream<char, std::__1::char_traits<char> > > ()
#2  0x0000000000000000 in ?? ()

Contents / format of single path pathfinder diagnostic file - purpose: figure out where pathfinder algo itself runs off the rails.
records parameters, gradients, and taylor approximation.
{
  {
    // lbfgs
    iter: 0
    params: [...] // vector
    gradients: [....] // vector
    // taylor_approx_t
    x_center: [...] // vector
   logdetcholHk: [.] // double, Log deteriminant of the cholesky
    L_approx [..., ...]  //Matrix of Approximate choleskly
    Qk: [..., ...];  //Matrix Q of the QR decompositon. Only used for sparse approx
    alpha [...]  // vector diagonal of the initial inv hessian
    string use_full;  // boolean indicationg if full or sparse approx was used.
  }
}

is there a reason why output columns from single- and multi-path pf are in different order?
multi-path:  algo outputs "lp_approx__" and "lp__" are first.
single-path:  params first.
convention (although probably unwritten and maybe not always respected) is that all "*" columns come first.  some pkgs might check that first column is "lp" as a kind of sanity check on the contents.   why put "lp_approx__" first?

Pathfinder output diagnostic files missing newline at end.

Awesome!! I'm going through right now to double check stuff and fixed the issues you pointed out above. Once tests pass I will merge!

Thank you so much for all the excellent work. Please contact me if I can help.

From: Steve Bronder @.>
Sent: Tuesday, June 6, 2023 7:54 AM
To: stan-dev/stan @.>
Cc: Lu Zhang @.>; Mention @.>
Subject: Re: [stan-dev/stan] Add Pathfinder and Multi Pathfinder (PR #3123)
@mitzimorrishttps://urldefense.com/v3/__https://github.com/mitzimorris__;!!LIr3w8kk_Xxm!sDYaSwtxyeTTQbLRUfOeIhHUHmdt2wY2-iY8FEbW5An9zGg458VvEufvmVP3TcRdDmIlQbJ-qe0_8U9B9gz7sQNr8g$ done!! Now we just need to hook it up to cmdstan and whatnot
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/stan-dev/stan/pull/3123*issuecomment-1578921271__;Iw!!LIr3w8kk_Xxm!sDYaSwtxyeTTQbLRUfOeIhHUHmdt2wY2-iY8FEbW5An9zGg458VvEufvmVP3TcRdDmIlQbJ-qe0_8U9B9gw4pVLHdw$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AFUN2LIQGH66F7T62T3FPPDXJ5ADJANCNFSM5UQ34YGA__;!!LIr3w8kk_Xxm!sDYaSwtxyeTTQbLRUfOeIhHUHmdt2wY2-iY8FEbW5An9zGg458VvEufvmVP3TcRdDmIlQbJ-qe0_8U9B9gyTsxjNrg$.
You are receiving this because you were mentioned.Message ID: @.***>

Alrighty I can take a look tmrw. That branch I wrote a while ago is kind of old, maybe good to just start with a new one?


Fix Bug.

If the command with the sudo need password, then without the pasword write, the process will be blocked。

Coverage decreased (-0.01%) to 50.478% when pulling 151aed26c96855575dbcce8fd2ce80402ecd7dd9 on yuye/bug_reolve_ssh into d5132e0e5de651227ca244389082d157bd9600f6 on master.


Lab 5 level 5 f method output

Summary
Description of the question / problem here.
Description:
i followed the f method codcrunch provided but the returning result it the reverse of expected. I am somehow not sure how to continue. Any idea would be appreciated! thx!
Code Snippets
Attach code snippets (if any)
Screenshots

Try invoking f() inside flatMap().

I would suggest you think of the order of evaluation of methods. When you call flatMap, you are essentially appending the new String to the back of your old String, what should you do if you want to attach it in front instead?

OK.
I admit my #293 Q&A probably wasn’t clear enough lol, others are still getting stuck.
Thing here is pretend that you have the recursive result evaluated, think what you need to do to said result.

the order for f function is the opposite of the sum function so try and find a way to reverse the order of the output through the use of flatMap. Otherwise, the logic for both sum and f is more or less the same

For each of the recursive statement (if - else statement), try to return a different result for each of them with the use of flatMap. The logic for if-else would stay the same as what code crunch description provided.

okay solved! thank everyone who helped!


Make fault abort message configurable

Currently fault filter when abort is configured aborts requests but also sends a message "fault filter abort" to the client.  Is it possible to customize this message (we want no message to be returned) either via fault filter api or via run time flag?

May be the local reply can helps? According the disscustion in the #9178, may be we needn't dedicated configuration for fault filter.
https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_conn_man/local_reply

I see . That makes sense.


#160915469 Add table queries

What does this PR do?

This chore adds the table queries
The queries are meant to create the relevant tables once the application is run
the tables include the category table, users table,
orders table and blacklist table

Pull Request Test Coverage Report for Build 156

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 96.97%

Totals

Change from base Build 146:
0.0%

Covered Lines:
96

Relevant Lines:
99

💛  - Coveralls


chore: refactor all instances of pubsubTopic to pubSubTopic

This PR addresses https://github.com/waku-org/js-waku/pull/1586#discussion_r1336696259 -- we should update all references to pubsubTopic to pubSubTopic for consistency
Notes

[ ] should we also update instances of pubsub?

for eg: services currently uses pubsub instead of pubSub

[ ] proto actually generates files with the occurence as pubsubTopic

should we maintain this inconsistency?
i incline towards maintaining the term as pubsubTopic instead (moving the PR to draft until we decide)

@fryorcraken would you not prefer if all instances are same and we change it to pubsubTopic to keep it consistent with the protobuf as well?

protobuf definition is coming from the RFC, which is why I am inclined to leave it as it is.


feat(LongToTimestamp):introduce new UDF to cast a long (epoch time) t…

…o timestamp (SQL timestamp)

Why not divide by 1000?
We used Instant.ofEpochMilli:
public static Instant ofEpochMilli(long epochMilli) {
long secs = Math.floorDiv(epochMilli, 1000);
int mos = (int)Math.floorMod(epochMilli, 1000);
return create(secs, mos * 1000_000);
}

val instant: Instant = Instant.ofEpochMilli(timestamp_epoch) --> divides the long (with flooring) by 1000
Timestamp.from(instant) --> Creates a Timestamp that has the given value * 1000
public static Timestamp from(Instant instant) {
try {
Timestamp stamp = new Timestamp(instant.getEpochSecond() * MILLIS_PER_SECOND);
stamp.nanos = instant.getNano();
return stamp;
} catch (ArithmeticException ex) {
throw new IllegalArgumentException(ex);
}
}
So that's why it works.. But looking at it, I think I can just return a new Timestamp with the Long input


Update README / release notes to mention 0.10.0

I see that version 0.10.0 was released.
What breaking changes are there from 0.9 to 0.10?  It would be really useful to put a short description on the release: https://github.com/google/google-api-ruby-client/releases/tag/0.10.0
The README mentions...

Migrating from 0.8.x
Version 0.9 is not compatible with previous versions.  See MIGRATING for additional details on how to migrate to the latest version.

But 0.10 is the latest, so it's a little confusing 😄

Ah yes, I had https://github.com/google/google-api-ruby-client/pull/541 out for that but forgot to update, will do.
Thanks for the issue

Merged #541.


[Bug] The linkedin_pages__post model doesn't handle post history correctly

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
We see failing tests for linkedin_pages__posts.sql for a non-unique combination of columns of ugc_post_id & source_relation.

Expected Behavior
The model is filtering to always use the latest version of this post and hence doesn't produce duplicated rows.
Steps To Reproduce
No response
Relevant log output
10:07:37  Completed with 1 error and 0 warnings:
10:07:37
10:07:37  Failure in test dbt_utils_unique_combination_of_columns_linkedin_pages__posts_ugc_post_id__source_relation (models/linkedin_pages.yml)
10:07:37    Got 2 results, configured to fail if != 0
10:07:37
10:07:37    compiled SQL at target/compiled/linkedin_pages/models/linkedin_pages.yml/dbt_utils_unique_combination_o_321ceac5241ebed20b1e3af34d1381f6.sql

What database are you using dbt with?
snowflake
Additional Context
The primary key for ugc_post_history is the combination of id & last_modified_time according to the ERD provided for the LinkedIn Company Pages connector. When posts get edited, they get a new row in this table, which can be identified by either the last_modified_time or the version_tag columns.

A similar solution to what is already used in int_linkedin_pages__latest_post.sql could be introduced to only use the most recent record for a post.
Are you willing to open a PR to help address this issue?

[X] Yes.
[ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

Fivetran support confirmed that the raw data behaviour is as expected in https://support.fivetran.com/hc/en-us/requests/55700.

@NoToWarAlways thanks so much for this detailed bug report write up!
Based on the supporting information you provided, it is clear to me that the linkedin_pages__posts needs to filter for the most recent ugc_post_id & source_relation record. I just looked through our own data and recognized we have not edited any past posts which is most likely why this test hadn't failed on our end. Glad the test did it's job though in raising this issue!
I will review your PR above and let you know if I have any requested changes or comments before we merge. Thanks again so much. These contributions help make our packages better. We really appreciate it 💯


Aggregates response compressed

Expected Behavior

Actual Behavior
When using request aggregation we are getting response which looks like it's compressed two times.
First time is compressed whole response and second time is compressed content of each endpoint response.
When added Accept-Encoding: br or Accept-Encoding: utf-8 to request header everything works perfectly.
Using Angular 7 HttpClient We cannot set Accept-Encoding because of 'Refused to set unsafe header "Accept-Encoding"'.
Any suggestions, please?
Thank you

Specifications

Version: 12.0.1
Platform: .NET Core 2.1
Subsystem:

@LukasSefcik @philproctor ,
Hi, I've also faced the same issue which I reported below. Can you please provide solution for this issue
https://github.com/ThreeMammals/Ocelot/issues/1072

hi, I have a question about the request to aggregates from Angular CLI.
I set the configuration that I needed for "Aggregates". Normally this Route work on the requested URL but when I try to this on Angular CLI it was returned response "Cors Origin Error". I set the configuration for "Cors Origin Error" and those are work one by one without returned response "Cors Origin Error".

@fadem  @LukasSefcik  @ramesh26  @MSeifAllah
here example how to solve this issue

Here's more detail on solution 1 from @MSeifAllah.
That solution is talking about a Delegating Handler in Ocelot.  I preferred that because it didn't involve a bunch of custom C# code for each aggregate request.  However, I don't know what the side effects might be as far as replacing gzip compression with other types of compression.  Seems to work for my simple test, though.
using System.Net.Http;
using System.Net.Http.Headers;
using System.Threading;
using System.Threading.Tasks;
...
public class NoGzipDelegatingHandler : DelegatingHandler
{
    protected override async Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
    {
        //Trying to avoid gzip encoding in the response, so selecting other compression algorithms
        request.Headers.AcceptEncoding.Clear();
        request.Headers.AcceptEncoding.Add(new StringWithQualityHeaderValue("deflate"));
        request.Headers.AcceptEncoding.Add(new StringWithQualityHeaderValue("br"));
        return await base.SendAsync(request, cancellationToken);
    }
}

Then in Startup.cs, you add your delegating handler as follows.  (The boolean parameter on AddDelegatingHandler set to true makes the handler global across all requests.)
public void ConfigureServices(IServiceCollection services)
{
    services.AddOcelot(Configuration)
    .AddDelegatingHandler<NoGzipDelegatingHandler>(true);
}


Custom keytable

Hi,
Here is a new @copycat_keytable_option option that, if set, uses a custom keytable for all searches except / (this one is too useful to be altered). If this option is not set, the default prefix keytable is used.
With this, my shortcuts are less crowded and I find them easier to remember.
I have added instructions in the README.md and customisations.md
Regards

Hi Bruno have you had some time to give a look at this PR?
Regards

Rebased on latest master

Hey, sorry for the wait. I like the idea.
What do you say we make t the default key-table? This plugin introduces a lot of key-bindings so that would make sense.
How do we handle support for older tmux versions, 1.9 and up?

No problem, thanks for the feedback.
I'm ok with t as the default key-table :)
Here is an update that I tested with tmux 1.9 on Debian bash 4.3 and on my OSX 10.11.4: I tried my best to check for compatibility only once and put the result in a variable (if 2.1+), otherwise not define that variable. Having a compatible syntax, working with various versions of bash took me some time.
Cheers

Progress looks good, I left a couple code-related suggestions.
What do you think about adding a test that checks key table works good? This might be hard-ish, let me know how you feel about it.
Also, what do you say we make t the default key-table for tmux version 2.1 and above ?

Thanks Bruno, I'll have a look at it this evening.

@bruno-,
Thank you for the very constructive feedback! The code is much cleaner now.

it works for both 1.9 and 2.1
the default key-table is t if key-table is supported
I have updated the doc and customisation paragraphs.

Tell me how you feel about it.

I still have to add the tests, but I have not looked into it yet.

Oh, I was not aware it had been merged! Great, thanks.

My bad, I got confused with an old PR from tmux-yank

How about this PR? There was no activity for about two years now.

Hi, I have been using the code from this PR for the last 2 years without a problem, but I never rebased on master, so if the functionality still makes sense then the conflicts need to be solved. On my side I have no time now for this.

cleanup!


Make default "External account" type custom profile fields editable.

In settings > custom profile fields, the "Label" and "Hint" fields are generated by default while creating a new "External account" type custom profile field, and currently this is the only custom profile field type that is non-editable.
As discussed here we would like to make the "Label" and "Hint" input fields of the "External account" custom profile field editable.

@zulipbot claim


Support for OpenAI-Beta assistants v2 and streaming.

Ability to set OpenAI assistants beta header:

v1 is still supported by OpenAI, so it is kept as default (no BC break)
version can be set by calling ->setAssistantsBetaVersion("v2")

Stream option is added to the following methods:

createRun($threadId, $data, $stream = null)
submitToolOutputs($threadId, $runId, $outputs, $stream = null)
stream callback usage is the same as with chat() method

Hello
Are any other changes happening? When can i get the latest when i install from composer please?
Thanks

Sorry, I forget to release the new version.
Please execute:
composer update orhanerday/open-ai
command.
Best regards,
On Thu, May 30, 2024 at 3:21 PM itscvenk @.***> wrote:

Hello
Thanks for this nice update (V2)
Are any other changes happening? When can i get the latest when i install
from composer please?
Thanks
—
Reply to this email directly, view it on GitHub
https://github.com/orhanerday/open-ai/pull/141#issuecomment-2139434757,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFKFT6VSYQTDJC7XOFO6KJDZE4KS3AVCNFSM6AAAAABH7XMIHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZZGQZTINZVG4
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

--
Orhan ERDAY
Software Engineer

Thank you! Love you! Keep up the great work


gen_completion to string

until there is a way to ship additional files with cargo install, i'd like to add a subcommand to my binary that prints the completion code to stdout, (that users can redirect to a file at location at their convenience; this seems more intuitive than pointing the commend at a directory and have it write there)
at the moment it seems the main entry point ComplGen is completely built around writing a file to a directory. what are your thoughts on splitting out the file writing from the generation?
given the single public api gen_completions i'm not sure what the best approach to adding/changing this would be.

Without making a breaking change, this could be possible by adding a App::gen_completion_to<W: io::Write> method. It would require some fairly minor changes to the internals of ComplGen but that shoudln't be too hard. Thanks for the idea :+1:

cool, will have a go


tabular environment is treated as a paragraph in the textlint AST

Problem
textlint-rule-ja-no-mixed-period points out "no period" errors in tabular environments.

Cause
\begin{table}[]
  \begin{tabular}{cc}
    This is & a table
  \end{tabular}
\end{table}

This LaTeX code is converted to an AST like below.
Since textlint-rule-ja-no-mixed-period treats the last Str node of a Paragraph node as the end of a sentence, converting a tabular environment to these nodes causes an unexpected error.
{
  "type": "Document",
  "raw": "...",
  "range": [],
  "loc": {},
  "children": [
    {
      "loc": {},
      "range": [],
      "raw": "cc}\n        This is & a table",
      "type": "Paragraph",
      "children": [
        {
          "loc": {},
          "range": [],
          "raw": "cc",
          "type": "Str",
          "value": "cc"
        },
        {
          "loc": {},
          "range": [],
          "raw": "}\n        ",
          "type": "Html",
          "value": "}\n        "
        },
        {
          "loc": {},
          "range": [],
          "raw": "This",
          "type": "Str",
          "value": "This"
        },
        // ...
      ]
    }
  ]
}

Solution
textlint-plugin-review seems to treat each item in a table as a ListItem node.
We can also wrap Str nodes into ListItem nodes.
https://github.com/orangain/textlint-plugin-review/pull/6

Textlint AST provides Table node. Why not use it instead of ListItem?
I note you that the third party parser latex-utensils has no node for table unfortunately.

Textlint AST provides Table node. Why not use it instead of ListItem?
I note you that the third party parser latex-utensils has no node for table unfortunately.

@tani
Table nodes is surely exists in markdown-to-ast  but not in @textlint/ast-node-types.
Thus I couldn't use node types like `ASTnodetypes.Table'.
https://github.com/textlint/textlint/blob/master/docs/txtnode.md#type

@tani
Table nodes is surely exists in markdown-to-ast  but not in @textlint/ast-node-types.
Thus I couldn't use node types like `ASTnodetypes.Table'.
https://github.com/textlint/textlint/blob/master/docs/txtnode.md#type

OMG, should we send request to ast-node-types?

OMG, should we send request to ast-node-types?

Thanks for writing the issue.
I will wait answers and decide which node to use for tabluar environments.

Thanks for writing the issue.
I will wait answers and decide which node to use for tabluar environments.


telemetry warning is too annoying

也许只显示几次 而不是每次都显示

或许可以提示的时候同时提供一个关闭显示的命令行。
to close / ignore the warning, please

$ ruyi xxx xxx xxx

This is now slated for 0.25.0:
$ ruyi
warn: this ruyi installation has telemetry mode set to on, and will upload non-tracking usage information to RuyiSDK-managed servers every Sunday
info: the next upload will happen anytime ruyi is executed between 2024-12-29 08:00:00 +0800 and 2024-12-30 08:00:00 +0800
info: in order to hide this banner:
info: - explicitly opt out with ruyi telemetry optout
info: - or give consent with ruyi telemetry consent

$ ruyi telemetry optout
info: telemetry data collection is now disabled
info: you can re-enable telemetry data uploads at any time by running ruyi telemetry consent


unable to build android with react native 0.71.1, got error android:exported needs to be explicitly specified for element

What happened?
setup android test on a react native (version 0.71.1) app following the instructions.
when building the android app regularly, it does not throw this error. ios test works fine as well.
keep getting error:
android:exported needs to be explicitly specified for element <activity#androidx.test.core.app.InstrumentationActivityInvoker$BootstrapActivity>. Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details.

What was the expected behaviour?
should not throw above error
Was it tested on latest Detox?

[X] I have tested this issue on the latest Detox release and it still reproduces.

Did your test throw out a timeout?

[X] I have followed the instructions under Identifying which synchronization mechanism causes us to wait too much.

Help us reproduce this issue!
No response
In what environment did this happen?
Detox version: 20.1.2
React Native version: 0.71.1
Has Fabric (React Native's new rendering system) enabled: (yes/no)
Node version: 18.11.0
Device model:
Android version:
Test-runner (select one): jest
Detox logs
Detox logs
npx detox build --configuration android.emu.debug --loglevel trace
cd android ; ./gradlew assembleDebug assembleAndroidTest -DtestBuildType=debug ; cd -

> Task :app:processDebugAndroidTestManifest FAILED
/Users/emilyxiong/Code/tmp/reactNative711/android/app/build/intermediates/tmp/manifest/androidTest/debug/tempFile1ProcessTestManifest17853538679311875052.xml:27:9-33:20 Error:
        android:exported needs to be explicitly specified for element <activity#androidx.test.core.app.InstrumentationActivityInvoker$BootstrapActivity>. Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details.
/Users/emilyxiong/Code/tmp/reactNative711/android/app/build/intermediates/tmp/manifest/androidTest/debug/tempFile1ProcessTestManifest17853538679311875052.xml:34:9-40:20 Error:
        android:exported needs to be explicitly specified for element <activity#androidx.test.core.app.InstrumentationActivityInvoker$EmptyActivity>. Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details.
/Users/emilyxiong/Code/tmp/reactNative711/android/app/build/intermediates/tmp/manifest/androidTest/debug/tempFile1ProcessTestManifest17853538679311875052.xml:41:9-47:20 Error:
        android:exported needs to be explicitly specified for element <activity#androidx.test.core.app.InstrumentationActivityInvoker$EmptyFloatingActivity>. Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details.

See http://g.co/androidstudio/manifest-merger for more information about the manifest merger.

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:processDebugAndroidTestManifest'.
> Manifest merger failed with multiple errors, see logs

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
java.lang.StackOverflowError (no error message)

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

* Get more help at https://help.gradle.org

BUILD FAILED in 9s
37 actionable tasks: 6 executed, 31 up-to-date

Device logs
Device logs
npx detox build --configuration android.emu.debug --record-logs all
cd android ; ./gradlew assembleDebug assembleAndroidTest -DtestBuildType=debug ; cd -
Starting a Gradle Daemon, 1 stopped Daemon could not be reused, use --status for details

> Task :app:processDebugAndroidTestManifest FAILED
/Users/emilyxiong/Code/tmp/reactNative711/android/app/build/intermediates/tmp/manifest/androidTest/debug/tempFile1ProcessTestManifest12150465681108452725.xml:27:9-33:20 Error:
        android:exported needs to be explicitly specified for element <activity#androidx.test.core.app.InstrumentationActivityInvoker$BootstrapActivity>. Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details.
/Users/emilyxiong/Code/tmp/reactNative711/android/app/build/intermediates/tmp/manifest/androidTest/debug/tempFile1ProcessTestManifest12150465681108452725.xml:34:9-40:20 Error:
        android:exported needs to be explicitly specified for element <activity#androidx.test.core.app.InstrumentationActivityInvoker$EmptyActivity>. Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details.
/Users/emilyxiong/Code/tmp/reactNative711/android/app/build/intermediates/tmp/manifest/androidTest/debug/tempFile1ProcessTestManifest12150465681108452725.xml:41:9-47:20 Error:
        android:exported needs to be explicitly specified for element <activity#androidx.test.core.app.InstrumentationActivityInvoker$EmptyFloatingActivity>. Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details.

See http://g.co/androidstudio/manifest-merger for more information about the manifest merger.

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:processDebugAndroidTestManifest'.
> Manifest merger failed with multiple errors, see logs

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
java.lang.StackOverflowError (no error message)

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

* Get more help at https://help.gradle.org

BUILD FAILED in 20s
38 actionable tasks: 3 executed, 35 up-to-date

More data, please!
No response

Our only Android developer is on his vacation, so we can't help earlier than the next week, sorry.

I'm keeping this open but we largely expect this to be resolved via #3867.

I seem to be running into the same issue. I followed the guide from https://wix.github.io/Detox/docs/introduction/project-setup/#step-4-additional-android-configuration
What happened?
tried to build the android app with
detox build --configuration android.emu.debug

but got the following errors:
android:exported needs to be explicitly specified for element <activity#androidx.test.core.app.InstrumentationActivityInvoker$BootstrapActivity>. Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details.
android:exported needs to be explicitly specified for element <activity#androidx.test.core.app.InstrumentationActivityInvoker$EmptyActivity>. Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details.
android:exported needs to be explicitly specified for element <activity#androidx.test.core.app.InstrumentationActivityInvoker$EmptyFloatingActivity>. Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details.

Was it tested on latest Detox?
Yes, I have tested this issue on the latest Detox release and it still reproduces.
In what environment did this happen?
Detox version: 20.1.5
React Native version: 0.70.7 (tried 0.70.0 as well)
Has Fabric (React Native's new rendering system) enabled: (yes/no)
Node version: v19.3.0
Device model:
Android version:
Test-runner (select one): jest

The error is very likely not related to Detox. Try this reference.

I have the same problem. The main project that I am working on, is a react native library. There is a demo app inside this library and I added detox to that demo app. This error (android:exported needs to...) shows a location from the library, which has no activity (or services, etc...) that needs android:exported. If I remove the library dependency, Then the demo app itself has no problem with detox and the build is successful.

This is caused by android.test:core < v1.4.0.
Adding this to android/app/build.gradle fixes for me :
configurations.all {
    resolutionStrategy {
        force 'androidx.test:core:1.5.0'
    }
}

I have seen #1367 which looks very similar however my test is properly placed at android/app/src/androidTest/java/com/sample/DetoxTest.java.

Same issue for me also with Android.

Another way of solving that is to find out the package name causing that and overwriting it in your own AndroidManifest.xml
i.e.
<activity
          android:name="com.surveymonkey.surveymonkeyandroidsdk.SMFeedbackActivity"
          android:exported="false"
          tools:replace="exported"
      />

This is caused by android.test:core < v1.4.0.
Adding this to android/app/build.gradle fixes for me :
configurations.all {
    resolutionStrategy {
        force 'androidx.test:core:1.5.0'
    }
}

That's a great find 💪🏻 Please try to see whether this can be removed with Detox 20.9.0

@arcln ping

This is still an issue 20.11.1

A workaround for me was to add this to app/build.gradle
    androidTestImplementation "androidx.test.ext:junit:1.1.3"
    androidTestImplementation "androidx.fragment:fragment-testing:1.4.1"
    androidTestImplementation "androidx.test:core:1.4.0"

A workaround for me was to add this to app/build.gradle
    androidTestImplementation "androidx.test.ext:junit:1.1.3"
    androidTestImplementation "androidx.fragment:fragment-testing:1.4.1"
    androidTestImplementation "androidx.test:core:1.4.0"

@krini have you tried the latest Detox version? As I mentioned, this should have been fixed in Detox 2.9.x (i.e. by bumping Detox to take androidx.test:core:1.5.0 instead of 1.4.0).

A workaround for me was to add this to app/build.gradle
    androidTestImplementation "androidx.test.ext:junit:1.1.3"
    androidTestImplementation "androidx.fragment:fragment-testing:1.4.1"
    androidTestImplementation "androidx.test:core:1.4.0"

@krini have you tried the latest Detox version? As I mentioned, this should have been fixed in Detox 20.9.x (i.e. by bumping Detox to take androidx.test:core:1.5.0).

You are right. It seems to work. I did actually update detox to version 20.11.4, but maybe it was in the other order.
I removed the packages again and it still builds.

Closing this in favor of more recent upgrades (RN72 in Detox 20.17.0, RN73 in 20.18.1)
Please report whichever issues accordingly 🙏
Sorry for the hassle, but it helps managing things more clearly


Add option of enforcing TLS-only requests via the S3 bucket policy

This change allows an extra statement to be added to the log S3 bucket
policy that denies requests unless they're made via TLS.
This additional policy statement is necessary to be able to enforce
encryption-in-transit requirements alongside the encryption-at-rest
that's already handled by the
apply_server_side_encryption_by_default block on the S3 bucket
resource.
This policy is required for buckets managed by this module to pass the
AWS Config s3-bucket-ssl-requests-only[1] managed rule and
Prowler's[2] extra764 check, which although not part of the CIS
benchmark seems like a sensible thing to satisfy.
Note that Trussworks' AWS Config module[3] enables the
s3-bucket-ssl-requests-only check by default, so before this change,
the two modules together result in failing Config checks.
By default insecure requests are permitted, in line with S3 defaults
and the historical behaviour of this module.
Note that this change does not appear to be implementable in a safe
manner following the pattern of other statements of flipping the
effect. My reading of explicitly allowing aws:SecureTransport requests
would have the effect of permitting all anonymous HTTP requests, which
is definitely not the opposite of denying any HTTP requests.
[1] https://docs.aws.amazon.com/config/latest/developerguide/s3-bucket-ssl-requests-only.html
[2] https://github.com/toniblyx/prowler
[3] https://github.com/trussworks/terraform-aws-config

Thanks for the very detailed PR. I plan to take a look at it today, but just wanted to say I appreciate you adding tests!

Closing in favour of #62 which - as per feedback on this PR - makes TLS-only requests the default.


Angular 2

Is it possible that the examples, like Hello solar system, which are using angular's version 2.0.0 do not work with angular release 2.1.0?

The package.json file for ui-router-ng2 needs a bump, but they should be compatible.
For example, in the Hello solar system plunker, find config/system.config.js and change from
var ng2Ver = '2.0.0';

to
var ng2Ver = '2.1.0';

and it still works.
I'm reorganizing the code (moving ng2 to its own repository).  When that's done I'll fix the package.json and release a new version which explicitly supports 2.1.0

Ok, after lots of struggling I managed to make it work.
Thanks for the help.

I'm adding to the 1.0.0-beta.4 target:

update package.json for 2.x compatibility

I have updated the Quickstart and the three tutorials to angular to version 2.1.2

For posterity: the package.json already specified ^2.0.0 which allows any 2.x.x version of ng2


[Python] Add pytest dataset marker to test_permutation_of_column_order

Can't test this here since we don't have a python build that does not have dataset enabled.

@jorisvandenbossche Thanks for the quick resolution.


add license title

It's not strictly required, but it's useful metadata, and part of the recommended license template text (see http://choosealicense.com/licenses/isc/ and https://opensource.org/licenses/isc-license)

@mjibson ping :)

@mjibson any chance you could take a quick look at this? Thanks!


Fix livereload relative urls

Livereload is hardcoded to localhost which is bad.

Make a <script> for the index.ejs
or, pull request the plugin

https://github.com/statianzo/webpack-livereload-plugin/pull/14


Question regarding bit allocation

Hi,
In your paper you mention that you allocated 2, 3, or 4 bits to each layer of the model using a criteria. But in Fig. 1(d): Construct LUT and Query&Add, the binary weights are shown to be 8-bit. This has confused me a bit. Is the figure created with 8-bit weights in mind instead of <= 4 bit weights? Or am I misunderstanding the flow?
Another way I tried to interpret Fig. 1 is that the FP16 Shift and Query&Add blocks have to run once for every bit of W. For instance, if we have allocated 3 bits to a weight W, the ShiftAddLLM block runs 3 times, each time for one bit of the W. In this interpretation, each bit in the 8-bit binary weights in Fig. 1(d) correspond to one of the activation (x) values.
Could you please elaborate more on how the bit allocation maps to the ShiftAddLLM architecture?

Hi,
Could you find the code how they use this shift&add during inference?
I could only find that they unpacked the alpha and binary weight back to FP16 format, which is contradicting the methodology as shown in figure 1.
Best regards,
Lucas


Add Spin CLI tool to path in "Let's Get Started" documentation

Please share the following
Documentation topic (what would you like covered)?
Add spin tool to path in the documentation. Sort of weird to see it referenced by the file path to the executable instead of like normal cli apps. More appearance than anything functional.
What documentation did you review and why was it not sufficient?
Here's the link. Looks like this is covered in other documentation of the same material so should just be a change for this page.

Being fixed by PR https://github.com/fermyon/developer/pull/301


Multisite synced media libraries

We're using WordPress multisite with MultilingualPress to create a multilingual website. Each subsite is identical to the primary site, but in a different language, i.e., site 1 is English, site 2 is the same content in German, site 3 is the same content in French, and so on. Because each subsite is identical other than the language, we end up having the same images in multiple media libraries, resulting in duplicate images totaling n * subsites.
To reduce wasted storage, we manually create hardlinks between each subsite's media library content and the primary site's media library content. Now that we're using WP Stateless to serve media content, I think we can further improve things by using the same CDN bucket for all subsites and thereby increase the browser cache hit rate (if a customer visits a page in English first and then switches to German, we shouldn't force him to redownload all the images simply because the URL changed).
Therefore my questions are:

For existing media library content, what is the impact of using the same storage bucket and path for all subsites? Is manually syncing the media library mandatory for each subsite necessary or is it good enough to perform the sync once on the primary site and then WP Stateless will automagically see / use the existing storage bucket content on the subsites?

For new media library content, what is the impact of using the same storage bucket and path for all subsites? Will we need to upload images once on each subsite (perhaps to generate the database entries?) or can we simply upload the images once on the primary site and then have them show up in the media libraries of all the subsites?

For existing media library content, what is the impact of using the same storage bucket and path for all subsites?

We have had talks internally about a synchronization tool that would have special handling for files on GCS that don't have any media library objects in WordPress (ref https://github.com/wpCloud/wp-stateless/issues/27). The tool would help the webmaster to identify and provide options for handling these orphaned files.
In your situation where multiple media libraries have the same storage location would have a problem with this (each site is unaware of files uploaded by other sites). In the end, this would be an option with the sync tool - so you wouldn't want to use this feature of new sync tool (still in the conceptual/planning phase). Hope that made sense. :)
In terms of how it will affect your sites now, it shouldn't do anything irregular. Each site will only see the files it uploaded itself. So if you have multiple sites using the same bucket and path, then they would only have knowledge of the files that they uploaded. This is the nature of how WordPress works - there is no concept of shared media library between network sites.

For new media library content, what is the impact of using the same storage bucket and path for all subsites?

From how WordPress handles this, I think I covered it above. From a webmaster point of view, it would be kind of messy - but not that crazy. A great benefit of WP-Stateless is that you shouldn't have to care how things are organized on the GCS -side. As long as you can see the files and manage them within WordPress, then who cares if multiple network sites are sharing the same bucket. I think its just a personal preference on the underlying organization.

Will we need to upload images once on each subsite (perhaps to generate the database entries?) or can we simply upload the images once on the primary site and then have them show up in the media libraries of all the subsites?

Yes - each media library is separate and doesn't know anything else outside of its own site. I think I covered this above.
@ahmed-sigmalux great questions, please let me know if you need any further clarification.

Thanks for answering all my questions.


python312Packages.numpyro: 0.15.0 -> 0.15.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.numpyro is: Library for probabilistic programming with NumPy
meta.homepage for python312Packages.numpyro is: https://num.pyro.ai/
meta.changelog for python312Packages.numpyro is: https://github.com/pyro-ppl/numpyro/releases/tag/0.15.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.15.1 with grep in /nix/store/gnpfvbh3ivp0gnnrf5p4vzyni1crcp14-python3.12-numpyro-0.15.1
found 0.15.1 in filename of file in /nix/store/gnpfvbh3ivp0gnnrf5p4vzyni1crcp14-python3.12-numpyro-0.15.1

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.arviz
python311Packages.bambi
python311Packages.numpyro
python311Packages.pymc
python312Packages.arviz
python312Packages.numpyro

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gnpfvbh3ivp0gnnrf5p4vzyni1crcp14-python3.12-numpyro-0.15.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.numpyro https://github.com/r-ryantm/nixpkgs/archive/08e7a98897370a06c968f819e4c8d21a1354c3de.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/08e7a98897370a06c968f819e4c8d21a1354c3de#python312Packages.numpyro

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gnpfvbh3ivp0gnnrf5p4vzyni1crcp14-python3.12-numpyro-0.15.1
ls -la /nix/store/gnpfvbh3ivp0gnnrf5p4vzyni1crcp14-python3.12-numpyro-0.15.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages marked as broken and skipped:

python311Packages.bambi
python311Packages.bambi.dist

10 packages built:

python311Packages.arviz
python311Packages.arviz.dist
python311Packages.numpyro
python311Packages.numpyro.dist
python311Packages.pymc
python311Packages.pymc.dist
python312Packages.arviz
python312Packages.arviz.dist
python312Packages.numpyro
python312Packages.numpyro.dist

Maintainer pings
cc @fabaff for testing.

duplicate of https://github.com/NixOS/nixpkgs/pull/326480


feat(chrome-extension): WebSSO with URL-based session syncing [SDK-836]

Description
Expand the ability for @clerk/chrome-extension WebSSO to sync with host applications which use URL-based session syncing.
How to Update
WebSSO Local Development Host Permissions:
Add *://localhost:*/* to the host_permissions array in your manifest.json file:
{
  "host_permissions": ["*://localhost:*/*"]
}

If you're using a local domain other than localhost, you'll want replace that entry with your domain: *://<DOMAIN>/*
{
  "host_permissions": ["*://<DOMAIN>/*"]
}

WebSSO Provider settings:
<ClerkProvider
  publishableKey={publishableKey}
  routerPush={to => navigate(to)}
  routerReplace={to => navigate(to, { replace: true })}
  syncSessionWithTab

  // tokenCache is now storageCache (See below)
  storageCache={/* ... */}

  // [Development Only]: If the host application isn't on
  // `http://localhost`, you can provide it here:
  syncSessionHost="http://<DOMAIN>"
>

WebSSO Storage Cache Interface:
With the prop change from tokenCache to storageCache, the interface has been expanded to allow for more flexibility.
The new interface is as follows:
type StorageCache = {
  createKey: (...keys: string[]) => string;
  get: <T = any>(key: string) => Promise<T>;
  remove: (key: string) => Promise<void>;
  set: (key: string, value: string) => Promise<void>;
};

Checklist

[x] npm test runs as expected.
[x] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[x] 🌟 New feature
[x] 🔨 Breaking change
[x] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/backend
[x] @clerk/chrome-extension
[ ] @clerk/clerk-js
[ ] @clerk/clerk-expo
[ ] @clerk/fastify
[ ] gatsby-plugin-clerk
[ ] @clerk/localizations
[ ] @clerk/nextjs
[ ] @clerk/clerk-react
[ ] @clerk/remix
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/themes
[ ] @clerk/types
[ ] build/tooling/chore

!snapshot

Hey @tmilewski - the snapshot version command generated the following package versions:

Package
Version

@clerk/backend
1.0.1-snapshot.vb99c163

@clerk/chrome-extension
1.0.1-snapshot.vb99c163

@clerk/clerk-js
5.0.1-snapshot.vb99c163

@clerk/clerk-expo
1.0.1-snapshot.vb99c163

@clerk/fastify
1.0.1-snapshot.vb99c163

gatsby-plugin-clerk
5.0.1-snapshot.vb99c163

@clerk/localizations
2.0.1-snapshot.vb99c163

@clerk/nextjs
5.0.1-snapshot.vb99c163

@clerk/clerk-react
5.0.1-snapshot.vb99c163

@clerk/remix
4.0.1-snapshot.vb99c163

@clerk/clerk-sdk-node
5.0.1-snapshot.vb99c163

@clerk/shared
2.0.1-snapshot.vb99c163

@clerk/themes
2.0.1-snapshot.vb99c163

@clerk/types
4.0.1-snapshot.vb99c163

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/backend
npm i<EMAIL_ADDRESS>--save-exact

@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

@clerk/fastify
npm i<EMAIL_ADDRESS>--save-exact

gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>--save-exact

@clerk/localizations
npm i<EMAIL_ADDRESS>--save-exact

@clerk/nextjs
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-react
npm i<EMAIL_ADDRESS>--save-exact

@clerk/remix
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>--save-exact

@clerk/shared
npm i<EMAIL_ADDRESS>--save-exact

@clerk/themes
npm i<EMAIL_ADDRESS>--save-exact

@clerk/types
npm i<EMAIL_ADDRESS>--save-exact

Hi guys 👋🏻
Can you please add storageCache to the @clerk/clerk-react as well?
I am writing an desktop app running a react app in the web-view which does not support cookies, but does the local storage.
I would like to use the ClerkProvider in @clerk/clerk-react with storageCache option.


UGUI not working in HandInteractionExamples scene on dev branch

Describe the bug
The UGUI examples on the right hand side are currently not working (e.g. buttons cannot be clicked, input field does not respond to click) on apps deployed to HL2 in debug mode. They work in editor remoting and deployed release mode app though.
Your setup (please complete the following information)

Unity Version 2019.4.15f1 & 2018.4.29f1
MRTK dev_branch

Target platform (please complete the following information)

HoloLens 2

@MaxWang-MS has this been fixed (and then forgotten to close)?

@MaxWang-MS has this been fixed (and then forgotten to close)?

Debug mode drops the app frame rate on HoloLens. This behavior is likely due to the game-loop timing in debug.

Debug mode drops the app frame rate on HoloLens. This behavior is likely due to the game-loop timing in debug.


Feat/137 integrate permit2

I see that conventional commits didn't pass. I am willing to let it slide but we should take the lint-staged hook from the ubiquity-dollar repo to minimize this from happening again. I'll set it as a new issue.


SAMZA-2789: Remove cap on intermediate stream partition count for stream mode

Problem: Intermediate stream partition count inference logic caps the partition size to 256 resulting in imbalances in work assignments to tasks
Description: As part of the intermediate partition size inference logic, we currently employ the following algorithm.

partitionCount = Math.max(maxPartitionSize(inputStreams), maxPartitionSize(outputStreams))
cap the partitionCount to MAX_INFERRED_PARTITIONS defined in the IntermediateStreamManager which is 256
apply the inferred partition count to intermediate streams whose partition count is uninitialized

The logic above always caps the partition size of intermediate streams to 256 for all auto-created intermediate streams. This can prevent the job from scaling up uniformly as the intermediate partition assignment is capped to 256 tasks thereby rendering other tasks imbalanced in case of number tasks > 256.
Changes:

Apply the cap only for batch mode as 256 limit was introduced for batch mode where number of files (partition) could be large
Add unit tests for IntermediateStreamManager
Minor java doc fix for DefaultTaskExecutorFactory

Tests: Added unit tests for the code changes
API Changes: None
Upgrade Instructions:

Jobs that are temporarily worked around this constraint by setting job.intermediate.stream.partitions should remove the configuration in order for samza to infer and apply the partition count as described above
Jobs that don't use job.intermediate.stream.partitions need no changes.

Usage Instructions: Refer to upgrade instruction.

LGTM, thanks for making this change.


fix: move qaHook to qahook to assist with spread props

qaHook is being added in as an attribute on the DOM elements inappropriately when components have spread operators defined on props. Let's stop that nonsense with qahook 🎊
This also has a significant <Link attribute change on it where styles were being wiped out completely  and should be merged once ready.

so qahook is not a valid dom element either, so I'm not sure this will exactly fix our issue. Can you test this branch against our other repos using npm link or the yarn equivalent and see if it solves the console errors we were seeing?


PEP8 compliance?

Is the codebase PEP8 compliant? Some lines look long.  Most functions don't have docstrings.

added styles.


[Android] TuyaUserApi.getCurrentUser() error

I got error when i tried to call TuyaUserApi.getCurrentUser() on Android, But it worked on iOS

E unknown:ReactNative: java.lang.NullPointerException: Attempt to invoke virtual method  'android.content.SharedPreferences android.content.Context.getSharedPreferences(java.lang.String, int)' on a null object reference

Before you call other methods please make sure used TuyaCoreApi. InitWithOptions (); maybe You can refer to the demo


Feature:  URL Encoding safe Base64

Consider adding URL Safe Encoding for Base64 Library
Base64 URL Safe Encoding is defined in RFC468 section § 5^1, whereas the current Base64 specification is defined in RFC 4648 § 4
To avoid the errors, it was proposed to use a “safe alphabet” for URL addresses and filenames.

Replaces “+” by “-” (minus)
Replaces “/” by “_” (underline)
Does not require a padding character
Forbids line separators

The alphabet:
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_[^2]
References
[^2]: It should fit the format ^[A-Za-z0-9+/]+={0,2}$

@sambacha Already implemented.
Pass in true for the fileSafe parameter: https://github.com/Vectorized/solady/blob/d3d564a3451f7128d63e611ac972b37804bd2c21/src/utils/Base64.sol#L11

@sambacha Already implemented.
Pass in true for the fileSafe parameter:
https://github.com/Vectorized/solady/blob/d3d564a3451f7128d63e611ac972b37804bd2c21/src/utils/Base64.sol#L11

The problem is with using = as the padding character - it is used to send data via query string as “key=value” pair.

What about setting noPadding to true too?


!default

You should use the !default flag for configurable settings.

Argh I always forget this one.

Fixed https://github.com/corysimmons/typographic/commit/f76a597d9805d6e71b98cfd5f86551679aac1a0c

Whoops messed this up lol.. so sleepy


job_dispatching.py does not update the Redis Database

I was trying to create my own redis database while investigating a set of apps. But apparently dex_extractor.py won't store anything. It looks like the catch_a_class() method from PackageNodeList is the problem. It stores data while iterating over the pn_list. But this cannot happen, since the pn_list is initialized as an empty list.

please contact<EMAIL_ADDRESS>原始邮件 --------主题：[pkumza/LibRadar] job_dispatching.py does not update the Redis Database (#65)发件人：MBus123 收件人：pkumza/LibRadar 抄送：Subscribed I was trying to create my own redis database while investigating a set of apps. But apparently dex_extractor.py won't store anything. It looks like the catch_a_class() method from PackageNodeList is the problem. It stores data while iterating over the pn_list. But this cannot happen, since the pn_list is initialized as an empty list.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.


Update 1.7.4 Thanks

Hi Jacob
Not an issue. Just to say well done on the 1.7.4 update.
Also to say that I have started a guide on setting up FreeDOS (v1.3) along with some ease of use customization's and setting up a handful of different development environments.
Along with Briggs Softworks File Maven (DOS) for file management, Costa is the feature desktop launch system in the guide.
I am looking forward to showcasing Costa with snapshots in the guide and hopefully some related video guides. Costa 1.7.4 will get a good workout in the coming weeks :)
P.S. the previous 1.7.3 is going great in my FD1.3 test install and playground for working out the guide contents :)
Thank you for Costa Desktop. Your efforts are appreciated.
Axle

Hi Axle,
Thank you for your feedback! It's always nice to hear that someone has found use for something you've made, so I really appreciate it.
I'm very interested in seeing the guide you're working on, so please be sure to let me know when it's done. I might share news about it on the Costa webpage, and link to it from there.
If you encounter any issues in your testing, or think of something you would like to see included in a future version, just post an issue here and I'll look in to it.
Oh, and thank you for using Costa!

My pleasure Jacob.
I have to check the new version and change logs before I post. But I was thinking about a practical future feature from my use of 1.7.3.
The ability to copy paste the shortcuts/links between desktops (database files).
I'll create a new post after I have had a good test run with 1.7.4 :)

The 2 guides are supplemental to my beginners guide to programming series and introduce the basic setups for DOS development environments in FreeDOS and Win95. I will use Costa as my default desktop launch pad for each environment in FD. Although not very familiar with Visual Basic for DOS I will likely include the setup alongside of other environments. I have some tertiary modules to complete before end of year as well as finish my 3rd book on setting up programming libraries so maybe by January I'll have Draft previews done :)
Have a good day
Axle


API docs generation for Docs v2

This issue is to discuss what to make of this library for the upcoming v2 docs:
cc. @jessicaschilling @johnnymatthews
It seems https://docs-beta.ipfs.io/reference/http/api/#getting-started includes the generated HTTP API docs, but I am not sure if they were changed by hand or it is the raw output from here.
I'd like to know if this library needs maintenance, and if we put time into the maintenance, what things do you want out of it. Alternatively we should signal clearly if this is dropped or deprecated.
Maintaining API documentation manually is a very painful process that luckily no one had to go through in the last years, and still we have fairly updated and accurate API docs. So my personal recommendation is to keep this, even with it's shortcomings.
Things that could be improved if we decide to keep this around:

Go all over the docs and fix wordings, improve descriptions etc in go-ipfs so that they make sense for both CLI and HTTP.
Add HTTP-Specific descriptions to go-ipfs when they don't fit.
Add manual specification for of the most problematic endpoints (essentially /add), which describes how to actually add folders, the multipart types etc.
Add more descriptions about general API features that affect several endpoints (stream errors, trailer headers).
Improve formatting of generated text, anchor links etc
Automate generation process on every new release
Potentially generate multiple pages (one per endpoint) rather than a single one (I am really against this, but it has been brought up).
Include fetching/generation of js-ipfs HTTP API docs
Document potential differences between the written Spec and the actual implementations.
...

These did indeed start with the generated API docs but needed quite a bit of massaging (mainly search/replace to escape out things that didn’t render correctly in markdown, IIRC) to display properly. (Note that the result of not escaping out errant characters was that the page just stopped rendering at that point.)
I know @johnnymatthews has both experience with and ideas for API docs going forward, as well as an epic-sized issue in the docs repo as a placeholder for discussing this matter, so I’ll let y’all chat further.

Also see: https://github.com/ipfs/docs/issues/393

These did indeed start with the generated API docs but needed quite a bit of massaging (mainly search/replace to escape out things that didn’t render correctly in markdown, IIRC) to display properly. (Note that the result of not escaping out errant characters was that the page just stopped rendering at that point.)

ok, so that massaging should happen in the generator. I can diff things and get the generator produce exactly what the v2 docs show now.

Continued in https://github.com/ipfs/ipfs-docs/issues/267


build(github-actions): run release action on main branch push

Codecov Report
Base: 99.59% // Head: 99.59% // No change to project coverage :thumbsup:

Coverage data is based on head (0fccef7) compared to base (4e36056).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #449   +/-   ##
========================================
  Coverage    99.59%   99.59%
========================================
  Files          110      110
  Lines         2211     2211
  Branches       314      314
========================================
  Hits          2202     2202
  Misses           9        9

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Refactored consistent writes logic

Keeps the logic outside the surface API.
Fixes https://github.com/BlueBrain/nexus/issues/2632

A few comments but it looks good, it really reduces the complexity.
There is an existing bug for storages I think that affects 1.6.0-M1 as we don't encrypt the storage source no ?


Scoreboard is delayed by 0.5 of a second in video

This issue seems like it's most likely better fixed within the control room, not within the software.


Add UnbindFrom method to bindables

Allows the following sort of usage:
var bindable1 = new Bindable<int>();
var bindable2 = new Bindable<int>();
var bindable3 = new Bindable<int>();

bindable2.BindTo(bindable1)
bindable3.BindTo(bindable1)

bindable1.UnbindFrom(bindable2)

bindable1.Value = 5;

// bindable1.Value == 5
// bindable2.Value == 0
// bindable3.Value == 5

Was this blocked for a reason? Only just saw the label.

Oh, no, I was testing something but couldn't replicate the issue, thought it might've been related to this.


Export Text when in Admin mode filename suggestion has invalid character ":"

Windows Terminal version
1.14.1963.0
Windows build number
22000.795
Other Software
No response
Steps to reproduce
Open Windows Terminal (Admin).
Have text in console window.
Right click on tab and choose "Export Text".
Expected Behavior
Cleanse out the colon character and other invalid characters for filenames based on the tab name.
Actual Behavior
Observe filename provided has "Admin: " as the leading text, and on Windows, a colon is not valid in filenames.

I mean, I guess why not? We'd probably accept this as a contribution

If @restartedwill is not willing to work on this issue, I would try to tackle this, but I'll need guidance to identify what files need to be examined and edited

Yes, I am not able to tackle this change; just raising awareness in the hopes another developer could pick it up.
From: EliaSchiavon @.>
Sent: Friday, August 5, 2022 4:16 AM
To: microsoft/terminal @.>
Cc: Will DP @.>; Mention @.>
Subject: Re: [microsoft/terminal] Export Text when in Admin mode filename suggestion has invalid character ":" (Issue #13664)
If @restartedwill https://github.com/restartedwill  is not willing to work on this issue, I would try to tackle this, but I'll need guidance to identify what files need to be examined and edited
—
Reply to this email directly, view it on GitHub https://github.com/microsoft/terminal/issues/13664#issuecomment-1206284826 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AGHJGH5IQU2AV24YK6GC7RLVXTSWTANCNFSM55POEZIA .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AGHJGHZN5EOK47B4U2XGEITVXTSWTA5CNFSM55POEZIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOI7THEGQ.gif Message ID: @.***>

That'd be great! I'd start right here:
https://github.com/microsoft/terminal/blob/74cdffe9215740a2c783c2d1f393fd303286b2b5/src/cascadia/TerminalApp/TabManagement.cpp#L435-L436
That's the line where we set the proposed text. I don't think we have any existing helpers for trimming a string so that it's a viable filename - I'll leave that as an exercise for the reader 😉

Ahah thank you! Started working on it, I will raise a PR in the next few days


Validate resources as part of build

It would be good if the transformation could also use the configured FHIR server to validate that the resources are valid according to the profiles that they assert.

Unfortunately performance of the validation operation upon the contents of this bundle is not currently good enough to be able to merge this change. It's currently taking about 15 minutes.


Support versioning with headers

Right now versioning only works with url path segments. Headers should also be supported. Here is an explanation on how to do headers versioning.

Related: https://github.com/RSuter/NSwag/issues/1285

Hey!
Any updates on this topic? :)

What is missing?
If you use header versioning then you probably want to manually add the global header parameter in PostProcess, apart from that the operations should correctly be reported by ASP.NET Core API explorer and generated in the spec...
Maybe even version filtering works - if the operation versions are correctly reported in API explorer groups.


pin flatbuffers to 0.8.4

Fix for #238

Codecov Report

Merging #239 (991de9d) into master (ed00e4d) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 991de9d differs from pull request most recent head 8f1a465. Consider uploading reports for the commit 8f1a465 to get more accurate results

@@           Coverage Diff           @@
##           master     #239   +/-   ##
=======================================
  Coverage   82.49%   82.49%
=======================================
  Files         162      162
  Lines       43621    43621
=======================================
  Hits        35983    35983
  Misses       7638     7638

Continue to review full report at Codecov.

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

merging to get CI green


Change a collor pallete to a blue one

changed css style colors to the blue ones

I decided to change styles for a bit by changing colors to the blue ones


Expose LiteLLM model names

There are many models supported by LiteLLM. Currently the frontend has a short hardcoded list of model names. This PR has the frontend fetch all LiteLLM model names from the backend.
I'm not sure this is exactly how we should implement it, but with this change the model names list will update anytime we upgrade the litellm package.

Excited for this! Looks like we need a rebase though

I'll re-open this PR on another branch.


Can not build app

I followed all docs but when i try to build app I always get same error:
[ksp] com.ramcosta.composedestinations.codegen.commons.UnexpectedException: Unable to get package name for module. Please specify a package name to use in the module's build.gradle file with:"
                    ksp {
                        arg("compose-destinations.codeGenPackageName", "your.preferred.package.name")
                    }
                    And report this issue (with steps to reproduce) if possible.

I am using :
ext.kotlin_version = '1.7.0'
ext.compose_version = '1.3.0-alpha01'
Added those in build gradle:

plugins {
    id 'com.android.application'
    id 'org.jetbrains.kotlin.android'
    id 'kotlin-kapt'
    id 'dagger.hilt.android.plugin'
    id 'com.google.devtools.ksp' version '1.7.0-1.0.6'
}
android.applicationVariants.all { variant ->
        kotlin.sourceSets {
            def name = variant.name
            getByName(name) {
                kotlin.srcDir("build/generated/ksp/$name/kotlin")
            }
        }
  }
  implementation 'io.github.raamcosta.compose-destinations:animations-core:1.6.14-beta'
  ksp 'io.github.raamcosta.compose-destinations:ksp:1.6.14-beta'

I could be incorrect here but the library hasn't been tested with Compose 1.3.x. Downgrade Compose to 1.2.0-rc03 and try again.
Also, when posting an issue, it's good to have enough code to be able to test (Here i'd assume you created a new project with an empty compose activity).
Assuming this is correct, I was able to make a basic project work with the following information and versions:
Project build.gradle
buildscript {
    ext {
        compose_version = '1.3.0-alpha01'
    }
}// Top-level build file where you can add configuration options common to all sub-projects/modules.
plugins {
    id 'com.android.application' version '7.2.1' apply false
    id 'com.android.library' version '7.2.1' apply false
    id 'org.jetbrains.kotlin.android' version '1.7.0' apply false
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

App module build.gradle
plugins {
    id 'com.android.application'
    id 'org.jetbrains.kotlin.android'
    id 'com.google.devtools.ksp' version '1.7.0-1.0.6'
}

android {
    compileSdk 32

    defaultConfig {
        applicationId "com.worldline.androidknowledge.myapplication"
        minSdk 21
        targetSdk 32
        versionCode 1
        versionName "1.0"

        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
        vectorDrawables {
            useSupportLibrary true
        }
    }

    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
    kotlinOptions {
        jvmTarget = '1.8'
    }
    buildFeatures {
        compose true
    }
    composeOptions {
        // Watch out here, this version must be compatible with the configured Kotlin version
        kotlinCompilerExtensionVersion "1.2.0"
    }
    packagingOptions {
        resources {
            excludes += '/META-INF/{AL2.0,LGPL2.1}'
        }
    }

    applicationVariants.all { variant ->
        kotlin.sourceSets {
            getByName(variant.name) {
                kotlin.srcDir("build/generated/ksp/${variant.name}/kotlin")
            }
        }
    }
}

dependencies {
    implementation 'io.github.raamcosta.compose-destinations:animations-core:1.6.14-beta'
    ksp 'io.github.raamcosta.compose-destinations:ksp:1.6.14-beta'

    implementation 'androidx.core:core-ktx:1.7.0'
    implementation "androidx.compose.ui:ui:$compose_version"
    implementation "androidx.compose.material:material:$compose_version"
    implementation "androidx.compose.ui:ui-tooling-preview:$compose_version"
    implementation 'androidx.lifecycle:lifecycle-runtime-ktx:2.3.1'
    implementation 'androidx.activity:activity-compose:1.3.1'
    testImplementation 'junit:junit:4.13.2'
    androidTestImplementation 'androidx.test.ext:junit:1.1.3'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.4.0'
    androidTestImplementation "androidx.compose.ui:ui-test-junit4:$compose_version"
    debugImplementation "androidx.compose.ui:ui-tooling:$compose_version"
    debugImplementation "androidx.compose.ui:ui-test-manifest:$compose_version"
}

MainActivity
class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContent {
            MyApplicationTheme {
                val navController = rememberNavController()
                DestinationsNavHost(
                    navGraph = NavGraphs.root,
                    navController = navController
                )
            }
        }
    }
}

Hi @Jalson1982!
Thanks for reporting this.
I'm most interested in what is the package name of your @Destination annotated Composables. We have some logic to get the common part of all of these and you may have found an issue with it.
@MaxMichel2
Thank you for helping here as well! 👍

@Jalson1982 can you kindly help us here?

Thanks for reporting this.
I'm most interested in what is the package name of your @Destination annotated Composables. We have some logic to get the common part of all of these and you may have found an issue with it.

@raamcosta sorry for late response I am on vacation. Actually this was my error. My composable did not have any package name :( . Sorry really for delay I will close issue.

No problem at all!


Enhancement: bio update

Description

Justified Bio

Related Issues

👷 Deploy Preview for boring-kowalevski-3c5544 processing.
🔨 Explore the source changes: af22f271cf6e28faa57246306d0fd07823f68dd6
🔍 Inspect the deploy log: https://app.netlify.com/sites/boring-kowalevski-3c5544/deploys/61d82b6bfde533000758ce89


:bug: Images missing latest tag on quay

docker pull quay.io/kairos/kairos-ubuntu-22-lts Using default tag: latest
Error response from daemon: manifest for quay.io/kairos/kairos-ubuntu-22-lts:latest not found: manifest unknown: manifest unknown

Thanks for reporting this @geetikabatra. The issue applies to other images as well, like fedora. Changing the title to reflect this

Also keep in mind latest sometimes points to latest master not latest release

And some of the release flavors are missing from the matrix

https://github.com/kairos-io/provider-kairos/pull/301


[make] run .t files in examples folder

run .t files from t and examples folders
useful for example policies like https://github.com/3scale/apicast/pull/561

:+1:
I think we should do the same for busted tests.

@davidor I agree, but lets do that when we actually have some so we can try. bin/busted should be ready for it.


Remove blank space w/ no activity icons

When an activity icon is not displayed in the most recent/selected spot div, there is a blank space the size of the corresponding activity icons. This is minor but we basically need to change the display types of activity icons. See picture below for an example.

Fixed as of f444b08e185a9bbbb550377aab1465d6103977d7


Feature/5 db schema implementation

In this Pull Request the data schema was implemented.

After the comments I gave you the database is correct according to the schema. Nice work!


White spaces added in links

Hi! I have a weird bug when I try to get tweets that contains links. It returns tweets with spaces added in the link at random positions.
For example for this tweet https://twitter.com/edimitchel/status/921162963641389056 which is : "TobyMac propose des solutions pour les femmes! #balancetonson #balancetonporc https:// youtu.be/HJ1DHhobVVg"
it returns the same text but there is a white space between https:// and youtu
For this one : https://twitter.com/jennylynn41069/status/921159647343595522 I get a white space between international/ and archive in the link.
My code is :
tweetCriteria = got.manager.TweetCriteria().setQuerySearch('#hello').setSince("2017-10-13").setUntil("2017-11-13").setMaxTweets(10)
tweets = got.manager.TweetManager.getTweets(tweetCriteria)

Does someone had the same problem ? Is there a solution ?
Edit : There is a MR which allows to grab attached links, so its much easier to find these white spaces and delete them.

I have the same issue. It seems to be caused by the underlying XML parsing library. In the following line in TweetManager.py the call to text() already contains this whitespace:
txt = re.sub(r"\s+", " ", tweetPQ("p.js-tweet-text").text().replace('# ', '#').replace('@ ', '@'))

I'm also not sure how to best fix this

Yes, it seems that the problem comes with PyQuery.
I updated it to the 1.4.0 (via pip), and it resolved the problem.


Starlink 16 Livestream not added when live

Not sure if there is an issue with appending the livestream to the launch. Something might have broke? 🤷🏻♂

Some issue with the webcast update job, not sure why it didn't pick up the one from this morning. Also might have to do with how we check for new livestreams. Due to quota restrictions and a terrible youtube api we can only check once an hour for new webcasts.
Going to go the youtube RSS route instead, so we can check more often. should be able to get that done over the weekend.

Officially checking the rss feed now every 5 min for the livestreams now. Should be much more reliable now.

Officially checking the rss feed now every 5 min for the livestreams now. Should be much more reliable now.


call request authorization on main thread

call request authorization on main thread and ignore the first call for didChangeAuthorization

@rpopovici thanks for the PR. I had forgotten to commit and push this update: https://github.com/yonahforst/react-native-permissions/commit/040352cee096f2c98e7fda5252bb5c80de159a97
That should bring requestAuthorization to the main thread. If that fixes it, can you update the PR with just 'ignore the first call for didChangeAuthorization' and i'll merge it.

@yonahforst done!

merged! thanks @rpopovici !

welcome


Outlook 2013 Won't Authenticate Microsoft 365 Account, Missing Reg Keys

Outlook 2013, Windows, M365 Business Basic.
I have reviewed this note but I do not have these registry keys.
https://docs.microsoft.com/en-us/microsoft-365/admin/security-and-compliance/enable-modern-authentication?view=o365-worldwide
Any recommendations?

@chrishill206 Thank you for your feedback. I tested this on a New machine with outlook 2013 and these registry keys do not exist. However, you can add the Key EnableADAL under HKCU\SOFTWARE\Microsoft\Office\15.0\Common\Identity\
Hope this helps!
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @chrishill206 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.