[Android]Feat:add InitListener

Brief Description of the PR
Checklist

Demo:
Documentation:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Huiying Jiang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Does this crate support Animations?

Short answer: Not impossible, but don't expect in near future.

First time I implemented this crate, the primary purpose of this crate is to test the API and usability of the lower-level library fbxcel, and to experiment how the high-level API should look like.
You might perceive this extreme experimentality of the current codebase from the version 0.0.9...
(Off topic: the reason this crate currently does not support animation is, test assets I used simply does not have animation data with enough  quantity and variations.)
The current codebase is written without guessing concrete usage, is written partially very straightforwardly (but not so simple and too many boilerplates), is immature modules structure, and have some other bad points in wide range to be fixed.
I've been feeling I should make some design decisions, and make the crate more maintainable with the right design, before more people depend on this (experimental and immature) crate and new features are added.
So,

Maintenance speed of the current code base is low, since I'm planning to rewrite them.

However I'll accept small changes and/or bug fixes.

I'm still willing to develop this library, but new features (including animation support) will based on the rewritten code.

I'll implement animation when I think I understood animation-related schema enough, but it won't come soon.

Sorry to keep you waiting.

Sorry to keep you waiting.
It's okay :')


Calendar of Existing Points

If we supplied the appropriate query (and what would that be?) can we have a calendar that shows what days are available for a particular watershed ?

It is possible to add a calendar widget if we have the query (as well as the data :) )

Let me know what you'd like to see for a query.

let me know what you want to render :)  I'm assuming we are rendering by node?  At which point a query were we pass id and get next 7, 10, 30... days back?

@jrmerz I was thinking more like this: http://watershed.ice.ucdavis.edu/vizsource/rest?view=available_allocations&tqx=out:html  But wonder if you want a JSON column as well mostly.
Or:
http://watershed.ice.ucdavis.edu/vizsource/rest?view=available_allocations&tq=WHERE+watershed='EEL RIVER'&tqx=out:html
Or
http://watershed.ice.ucdavis.edu/vizsource/rest?view=available_allocations&tq=WHERE+allocation_date>'2014-05-01'&tqx=out:html

With the vizsource going away, I'm closing this.


Replace Experiment with something else in the code

We've more or less eliminated the notion of an experiment from our description of iter8. Instead we talk about performance tests. Should we rename the object Experiment as PerformanceTest, PTest, Test, Iter8Test or something similar?

Perhaps ok to leave it as experiment ... for now? This is anyway not user-facing.. if we do change it later (e.g., to Test), it wouldn't constitute a breaking change.


Use with npx?

First, thanks for working on this. Looks like a great project that will be super useful!
Lately I've been using npx to run scripts instead of installing globally. I tried with this (npx gutenblock init), and it didn't work. I did install globally and run and it's working.
Not sure what it takes to work with npx but would be cool if it worked.

it should be able to run with npx, all that does is cause it to use the local path like you're saying. I will look into this over the weekend :D

again, thinking something is wrong with my environment. . .this seems to work for me today 🤔


Improvement course documentation and code comments for project 1

close #113

add code comments for project 1-2
add a Makefile commend for run test in project 1
refine course doc for project 1

PTAL @pupillord

fixed typo and PTAL @pupillord

LGTM


update cuda auto csr param

This PR updates the auto csr parameters

Classical csr: This PR vs original csr (not updated classical)

Automatic csr: This PR vs original csr (not updated classical)

Classical csr: This PR vs original automatical setting

To make the matrices with around 1e5 ~ 1e6 nnz is similar with before. I also tried nnz_limit = 4e5, some matrices is faster but one matrix gets 5~10 times slow. I prefer to keep 1e6 as nnz_limit.


[clkmgr] reset selection

This is related to #12284.
While debugging chip_sw_clkmgr_peri_off, I realized the fact that clkmgr is using por as its main configuration reset once again causes an issue.  In the test, the uart clock is explicitly turned off, causing the access to hang the bus.
This causes a watchdog reset which reboots the system (this is all intended).  However, upon reboot, the rom tries to access uart again, and hangs once more.  This can be addressed by ensuring rom turns on the clock to the blocks it cares about before access, but it is beginning to make me think this is like wack-a-mole.
I'm going to see if the reset source of clkmgr can be adjusetd altogether,

@matutem
@jdonjdon

fixed with #13095


chore(slideshow): fix small error in pagination items width

General summary
Fixed a small oversight from https://github.com/lumapps/design-system/pull/1149 where the focus outline would still be cropped when selecting the right-most pagination item.
(not updating the CHANGELOG because there is already an entry talking about the fix from #1149)

Test OK
With 5 slides, the pagination take the most space but the sufficient space is reserved for the focus outline
Above or below 5 slides, focus outlines are not cropped either


[Mirror] [Do Not Merge] Disk 2019-07-01 version

Mirror from https://github.com/Azure/azure-rest-api-specs/pull/7280

/azp run


Patch?

How do I use a PATCH method?
Example: octo.repos(result.owner.login, result.name).update({
description: 'test'
})
Thanks.

It depends on if you are using callbacks or promises.
With promises:
octo.repos(result.owner.login, result.name).update({description: 'test'})
.then(function(updatedObject) {
  console.log(updatedObject);
});

With callbacks:
function cb(err, updatedObject) {
  console.log(updatedObj);
};
octo.repos(result.owner.login, result.name).update({description: 'test'}, cb);

Hmm. I've tried that.
Repo: https://github.com/RichardLitt/gh-description
node cli.js RichardLitt/awesome-nomad test

It's still not working. :/ Thoughts?

Ah, according to https://developer.github.com/v3/repos/#edit it seems GitHub requires the name to be provided as well. Without the name I got a 422 response but once I added the name the description updated.

So, I tried that, and it still is returning this:
{ [Error: {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}]
  status: 404,
  json:
   { message: 'Not Found',
     documentation_url: 'https://developer.github.com/v3' } }

I'm still not sure if this is my fault.

The only difference between a working call and a failing one is turning .fetch() into .update({'name': 'test-repo', 'description: 'test'}).

It seems the OAuth scope for the key that is generated is "public access" which is not enough to edit repo details. It would need to have either public_repo or repo. See https://developer.github.com/v3/oauth/#scopes for more details.

Fixed by deleting the config file and then adding scopes. Didn't work previously due to not overwriting the ghauth config file. Thanks!

I have the same Not Found bug again, and I have no idea how to diagnose it. How can I find out what URL is being used to hit the GitHub server?

Fixed by deleting the config file and then adding scopes. Didn't work previously due to not overwriting the ghauth config file. Thanks!

Did the same thing. Not sure why I keep running up against this. Not this module's bug at all.
<3 thank you for helping. Sorry for being a bit obstinate.


Do we need additional options for signing?

Right now, the only option appears to be to sign by drawing an image of the signature. I think we probably should let people choose to sign with a /s/, and possibly to sign with wet ink (if they don't choose to e-file).

Could this be an upstream bug? The interview does not assign a value to al_form_requires_digital_signature, which I assume would leave it as false. But I tried explicitly adding al_form_requires_digital_signature = False to a code block and it still didn't give me the option to sign after printing. (docs)


Refactor required

code base ugly  = refactor

Start up and Shutdown are better, now need to make communication between layers better, redo ui window handling/panel manager.


WIP: Add support for User authentication

Will add the descriptions at the end of the day

What this PR does / why we need it:
This PR aims to implement user authentication for feast based on the RFC below:
https://docs.google.com/document/d/14-QBz9X8zK_aGAY2ti43a7PqMxvqp0035ec7QYgmEBM/edit#
Does this PR introduce a user-facing change?:
Yes, these are the changes caused by this Pull Request:
Feast Core API
New RPCs
AddMember
RemoveMember
ListMembers
AddRole
RemoveRole
Feast Core Data Model
New table
Users
Roles
UserProjectRole
New classes
Users
Roles
Python SDK
Addition of user auth configuration
New methods:
add_member()
remove_member()
list_members()
add_role()
remove_role()

/ok-to-test

@woop I have added unit tests for the feast core side that is related to the user authentication

Sorry to bring an RFC question here, I don't want to turn the PR into that level of discussion, but were we going to pull auth out from the Projects RFC into its own? @woop I think we mentioned privately a dedicated GH issue at least.
I'm triggered a bit already by Feast maintaining its own database of users and their credentials 😅

Sorry to bring an RFC question here, I don't want to turn the PR into that level of discussion, but were we going to pull auth out from the Projects RFC into its own? @woop I think we mentioned privately a dedicated GH issue at least.
I'm triggered a bit already by Feast maintaining its own database of users and their credentials

Happy to do that. There is definitely a drift that occurs from RFC to actual implementation, so we should also decide what eventually becomes the source of truth. Perhaps a flow like

RFC
PR (with active discussion, and documentation)
Then Gitbook becomes the source of truth and the RFC can go out of date.

In this case since auth & projects were mixed in together, I think creating an issue to externalize it makes sense.
In terms of managing users & credentials. It's definitely not ideal, and we'd want to offload this to an external service ideally. I think the intent here was to have a basic form off auth out to protect our existing users while we implement something that is more integrated.

@ches Added the issue here: https://github.com/gojek/feast/issues/504

Completely understand and agree about the flow of the source of truth, in general.

Closing this PR until we settle #504. We can submit a new PR at that point.


why use process.stderr as the default stream?

I use single-bar update progress status, but sometimes log will output to one file. So I use isTTY to  judge whether this API should be used.
But I found that only I use stdout as the progress-bar's stream can work. I wonder why process-bar use stderr as default stream?

it gives the possibility to "throw" the "useless" progress away and use stdout for regular logging messages. additionally it doesn't wastes log-files because most users only redirecting the stdout stream.

THX!
When my scripts runs in a build server, they pipe my progress info to other progress, then
  // bar is a multibar
  if (!bar.isTTY()) { // false, cause default stream is process.stderr
     bar.increment(1)); // will throw error: call increment of undefined
  }

so I change the process-bar instance's stream to process stdout


use fieldbuffer copy

little refactoring use fb.Copy(d) instead of iterate.

Thank you @tzzed, but as mentioned in #442 I'd like to avoid small refactoring PRs.
The project is still in development phase so small refactoring are not really useful for several reasons:

This part of the code might move or be removed
This types.Document API, or any other API might change in the near future

I agree that having a clean codebase is important and I understand why you made this change, but it's too early for this project and it would be better if it was grouped with other changes in a bigger cleanup PR.


reactionRemoveCommand not working

Type

[x] Bug fix: yes
[ ] Functions: <Function Name>
[ ] Callbacks: <Callback Name>
[ ] Handlers: <Handler Type>
[ ] Others: ______

Code used:
module.exports = ({
    channel: "$channelID",
    code: `$channelSendMessage[$channelID;popo;no]
$onlyif[$emojiToString==❤;]`,
    type: 'reactionRemoveCommand'
})

More:

Aoi.js 1.0.6
Node.js idk
The message is not sent, and this is spamming the console. Many of my reactionRemove commands are not working now. But that code in the reactionAdd commands works.

$channelUsed does not work either :(

$channelUsed does not work either :(


jdk21 compatibility

related issue:

upgrade dependencies

dokka (https://github.com/querydsl/querydsl/pull/3697)
kotlin (https://github.com/querydsl/querydsl/pull/3638)
asm (https://github.com/querydsl/querydsl/pull/3601)
asm-commons (https://github.com/querydsl/querydsl/pull/3600)
lombok (https://github.com/querydsl/querydsl/pull/3589)

https://github.com/querydsl/querydsl/pull/3596
https://github.com/querydsl/querydsl/pull/3675

Motivation:

make to pass all test with java 1.8 to 21

Modification:

change dependencies version
change bonecp to hikaricp (for jdk21 compatibility)

Result:

pass all test with java 1.8 to 21

I checked through the GitHub Action pipeline that my modified code can pass tests from Java 1.8 to 21
https://github.com/dev-jonghoonpark/querydsl/actions/runs/8269187797
@johnktims


Specified key was too long; max key length is 767 bytes when instsall gogs

The issue will be closed without any reasons if it does not satisfy any of following requirements:

Please speak English, we have forum in Chinese.
Please post questions or config/deploy problems on our forum: https://discuss.gogs.io, here are bugs and feature requests only.
Please take a moment to search that an issue doesn't already exist.
Please give all relevant information below for bug reports; incomplete details considered invalid report.

You MUST delete above content including this line before posting; too lazy to take this action considered invalid report.

Gogs version (or commit ref):
Git version:
Operating system:
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gogs.io:

[ ] Yes (provide example URL)
[ ] No
[ ] Not relevant

Log gist (usually found in log/gogs.log):

Description
...

go to https://github.com/gogits/gogs/issues/4894


fix: reset ready timeout on successful connection

Summary
Correct the connection ready timeout to clear when a successful connection is made. The previous behavior was prematurely closing the ssh session because the timeout was firing even after a successful connection ready event was encountered. In the timeout function there is code to gracefully end the connection.
This behavior resulted in subsequent run button presses resetting/re-establishing the sas -nodms interactive session. When this happened any intermediate work table content was lost.
Testing

[x] Test via steps to reproduce:
1. Connect to a 9.4 environment with a SAS 9.4 Remote connection profile.
2. Place the following sas code in the editor contents:
data test; set sashelp.class; run;
3. Click run. Verify that no errors appear in the log.
4. Replace editor contents with code that uses the work table:
proc print data=test; run;
5. Click run.
6. Verify that proc print step from 4 prints the results from the work table to the log.
7. Verify that result tab shows with 19 observations.
8. Click the close button.
9. Replace the editor contents with code from step 4.
10. Click run.
11. Verify that the intermediate work table is no longer found with error:
File WORK.TEST.DATA does not exist.

[x] Test that a sas program that runs for longer than the ready timeout (default 10) seconds value does not prematurely timeout. Program code:
data _null_;         slept=sleep(25,1);     run;

[ ] Add appropriate unit tests

Main issues are fixed. Working on how we might leverage the extension test api to test different aspect of the duplex stream on the ssh connection provider to shore up some coverage gaps.


Move Dependabot to monthly cycle

What is being addressed
The initial dependabot config is a bit harsh with it working on a weekly internal plus taking all updates into account.
How is this addressed

Move to monthly interval
Ignore patch/build versions (shouldn't impact security updates)

/test-force-approve

/test-force-approve


Generating a tone above hearing range.

hey y'all. The code below is supposed to generate a tone above the threashold of a human hearing, but no.
Is this even supported? I see no upper limit. Or this lib doesn't support such tone?
var sine20Seconds = new SignalGenerator()
           {
               Gain = 0.3,
               Frequency = 28500,
               Type = SignalGeneratorType.Square
           }
      .Take(TimeSpan.FromSeconds(20));
           using (var wo = new WaveOutEvent())
           {
               wo.Init(sine20Seconds);
               wo.Play();
               while (wo.PlaybackState == PlaybackState.Playing)
               {
                   Thread.Sleep(500);
               }
           }

You can't go above the Nyquist limit, which is half of the sample rate. So for example if you are using a sample rate of 44.1kHz, then you can't go above 22kHz. The signal generator won't stop you entering higher values, but you can expect "aliasing" to occur if you try to use them.


New query option: raise_errors (Closes #201)

Waiting for Travis.
@adventures91 Any feedback?

Thanks for the quick update on that and it looks good to me.


[ko] Update outdated files in dev-1.22-ko.1 (p1)

Related issue:

#29257

[ ]  M61.  content/en/docs/tasks/manage-daemon/update-daemon-set.md  | 9(+XS) 6(-)
[ ]  M62.  content/en/docs/tasks/manage-hugepages/scheduling-hugepages.md  | 6(+XS) 0(-)
: Also in #29253
[ ]  M63.  content/en/docs/tasks/network/validate-dual-stack.md  | 1(+XS) 1(-)
[ ]  M64.  content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md  | 1(+XS) 1(-)
[ ]  M65.  content/en/docs/tasks/run-application/horizontal-pod-autoscale.md  | 11(+S) 8(-)
[ ]  M66.  content/en/docs/tasks/tools/install-kubectl-macos.md  | 2(+XS) 2(-)
[ ]  M67.  content/en/docs/tutorials/clusters/apparmor.md  | 5(+XS) 0(-)
[ ]  M68.  content/en/docs/tutorials/kubernetes-basics/create-cluster/cluster-interactive.html  | 1(+XS) 1(-)
[ ]  M69.  content/en/docs/tutorials/kubernetes-basics/deploy-app/deploy-interactive.html  | 2(+XS) 2(-)
[ ]  M70.  content/en/docs/tutorials/kubernetes-basics/explore/explore-interactive.html  | 2(+XS) 2(-)
[ ]  M71.  content/en/docs/tutorials/kubernetes-basics/expose/expose-interactive.html  | 2(+XS) 2(-)
[ ]  M72.  content/en/docs/tutorials/kubernetes-basics/expose/expose-intro.html  | 1(+XS) 1(-)
[ ]  M73.  content/en/docs/tutorials/kubernetes-basics/scale/scale-interactive.html  | 2(+XS) 2(-)
[ ]  M74.  content/en/docs/tutorials/kubernetes-basics/update/update-interactive.html  | 1(+XS) 1(-)
[ ]  M75.  content/en/docs/tutorials/stateful-application/cassandra.md  | 2(+XS) 2(-)
[ ]  M76.  content/en/docs/tutorials/stateful-application/zookeeper.md  | 4(+XS) 4(-)
[ ]  M77.  content/en/docs/tutorials/stateless-application/guestbook.md  | 1(+XS) 1(-)

/assign

/lgtm

/approve


Question 062 for Foundations should prompt for multiple answers

Describe the issue
At the moment it's not clear that the question is expecting multiple answers, when it actually wants you to give 3.

Thanks for raising this @dankatri ! It is indeed missing that bit, must have missed it. I will get it fixed


fix test for getServerCommand

I noticed an error in this test after the prior PR was already closed.
jeremys@skynet> printf $got
/usr/bin/java

jeremys@skynet> printf "$got"
/usr/bin/java -Xms128M -Xmx2048M -Dtesting-the-jvmargs -jar /home/jeremys/mscs/server/minecraft_server.fakedVersion.jar nogui

Looks good. Thanks for catching the error and sending the patch.


Near moon observations

We observed a few tiles closer to the moon than we normally do, following the engineering full moon observations at the end of August.  The following expid were observed closer than we normally are willing to go:
EXPID  TILEID  NIGHT   MOONSEP
int64  int64   int64   float64
------ ------ -------- -------
249647  27122 20240821   38.32
249648  27122 20240821   38.45
249649  27156 20240821   35.91
249650  27117 20240821   36.28
249651  27117 20240821   36.33
249657  27116 20240821   37.54
249661  20801 20240821    36.3
249819  25977 20240822   35.25
249820  25977 20240822   35.34
249823  24589 20240822    37.7
249824  24589 20240822   37.68
249825  27777 20240822   38.06
250082  11419 20240824   36.95
250083  11419 20240824    37.1
250085  20674 20240824   36.75

The bright observations on 20240821 look pretty nominal to me, though there are some RSKYTHRUFRAC warnings that may be related but don't seem to be affecting redshifts.  Likewise 20240822 looks pretty nominal to me.
On 20240824 we observed a dark tile, 11419.  QA looks fine but it reports a low n(z) / n(z)_ref.  My suspicion is that this is just typical for bright sky & good seeing conditions but I'm making that up.  We could throw it away just to not have any dark tiles too near the moon.  The final exposure 250085 has lots of skychi2pdf warnings and spurious redshifts and we should throw it away.
@ashleyjross , you were annoyed by other exposures on something like 20240824; can you say which ones?

few additional infos about tileid=11419:
that tile actually got one extra exposure on 20240825 (probably because we ran ap with --no-network, so nts used efftime_etc, which underestimates efftime_spec when the moon is up), and got in the end efftime_spec~1300s.
with that extra-exposure, the coadds look nominal to me.
@ashleyjross and me exchanged various diagnoses in this thread: https://desisurvey.slack.com/archives/C01HNN87Y7J/p1724704469175409.
for completeness:
here s the tile-qa for 20240824 (another diagnosis: only 93% of lrgs have deltachi2>25):
https://data.desi.lbl.gov/desi/spectro/redux/daily/tiles/cumulative/11419/20240824/tile-qa-11419-thru20240824.png

and here s the tile-qa for 20240824+25 (another diagnosis: 97% of lrgs have deltachi2>25, a nominal value):
https://data.desi.lbl.gov/desi/spectro/redux/daily/tiles/cumulative/11419/20240825/tile-qa-11419-thru20240825.png

Thanks Anand.  Note that the EFFTIME discrepancies don't seem so large, ~20%, so fairly typical for moon and not special about this tile.  So I would have said that 11419 is pretty nominal on the basis of the QA and we should keep it.  If I were better I would try to map out n(z) / n(z)_ref as a function of sky brightness and EFFTIME_SPEC to see how weird that n(z) / n(z)_ref looks in that context, but that sounds like a fair amount of work.  @ashleyjross , do you want to say if you want to keep this tile or not?  My default is to keep it as I can't see any issues with the data.

The extra exposure on the 25th makes it more typical in terms of success and having gotten that exposure, it is probably fine. The evidence suggests to me that EFFTIME_ETC was actually more correct in terms of predicting the S/N for this tile than EFFTIME_SPEC. So, the ultimate EFFTIME_SPEC (or TSNR2) might be suspect for this tile. The other tile I flagged was 1135, which also got another exposure on the 25th (and its LRG success rate went from 0.96 to 0.99).

Here is a histogram of the redshift success of LRGs for tiles in Jura:

(this does include masking, both of fibers and around bright stars, that will improve the statistics, but 0.93 will always be an extreme outlier)

I agree with you that 0.93 is impossibly bad in the context of that plot, but I also can't understand it in terms of anything the QA says.  So fine, I guess we call the 20240824 exposures on 11419 as bad.  1135 is not on my list of near-moon exposures, but 0.96 is also an impossibly bad outlier on that plot, so I guess we declare those exposures to be bad as well?  I'm worried that I would never have declared these images bad without this plot.

I realized the 0.93 isn't the fair comparison there, because 0.93 is using DELTACHI2 > 25 & ZWARN==0 and I was using the LSS definition (which is DELTACHI2 > 15 & ZWARN == 0). The more fair histogram is:

The combination of substantial improvement with some extra time from the 25th and you not finding anything wrong in the data makes me think that (for whatever reason) EFFTIME_SPEC is what is most corrupted in the data. The EFFTIME_ETC is more accurate, somehow, in that at those EFFTIME, we would start getting such low success rates, as this plot from Rongpu's targeting paper shows:

So, the most conservative thing to do would be to reject the exposures, but I'm willing to live with two tiles that could have bad efftime estimates.

(And both 11419 and 1135 appear affected by the issue...Maybe there is someone who can inspect what happened with the EFFTIME determination for those tiles?)

Okay.  @sybenzvi , can you mark these tiles as unsure and then do MTLs, so we don't archive and MTL these two problem cases?  @akremin , can you mark the exposures on the 20240824 on tileid 11419 and 1135 as bad and then reprocess those tiles?
I don't know of any reason that EFFTIME or EFFTIME_ETC should be weird for two tiles.  I think the agreement there was at the ~20% level typical of moony exposures.

@kremin: We need these exposures marked as bad and the tiles rerun.

@akremin, I mean: Could you please mark this exposure as bad and rerun the tile?

Just pinging this ticket again; as we finish the SGC these tiles are leaving a noticeable hole.

All exposures for 11419 and 1135 on 20240824 have been marked bad and removed.
Both of these were re-observed on 20240825. Those redshifts were removed and rerun.
I have updated the exposures-daily and tiles-daily files to reflect the changes in both nights.

@SGontcho , can you reQA these?  Thanks!

I've updated the tiles-specstatus file for 11419 and 1135. @SGontcho: You don't need to take any further action.


[AERIE 1871]  simulated activity id metadata in generated sequences

Tickets addressed: AERIE-1871
Review: By commit
Merge strategy: Merge (no squash)

Description

Adds the simulated activity id to the command metadata
Verification

Added the metadata to the expansion test check
Documentation

No documentation update needed (at some point when things are stable, we'll document the output of expansion more fully)
Future work

None

I am going to merge this as Dylan is still out and will need this for my PRs.
Dylan, I hope you don't mind.


Find a workaround for permalink issue

Description
In #38 we stumbled upon an issue with the preview environment of Storyblok where the preview environment wants to render a page on /pages/original-path but we build the pages to /original-path. I think there are multiple solutions:

Use the ELEVENTY_ENV environment var and make permalink a computed property where if the env is equal to production, it maps to /original-path, otherwise it maps to /pages/original-path
Figure out if there's a way to fix this using now.json or something.

I honestly think that the second one is a more robust solution, especially when we have multiple environments like staging.cmdplayground.com and the live version. However, the first solution also work fine for now.
Acceptance criteria

Use the solution that fits for now
Implement that solution
Test thoroughly

Going to implement the first solution for now.


Script out semantic model

Hi there
I really like the new sempy_labs module.
Would it be possible to create the object to script out and or replace the semantic model?
The reason is sometimes I want to get a copy of the semantic model. And other times I want to do a bulk replace and this makes it a lot easier.

Thanks Gilbert. Are you trying to script out the entire model? Have you tried the get_semantic_model_bim function and create_semantic_model_from_bim functions? If this doesn't help, please give an example of what you are trying to do.

Hi Michael, I somehow managed to miss that. I can get the information I need from the get_semantic_model_bim. I tried it with another error which I will a separate issue so that others who are searching can find this helpful.


Desktop version

In this pull request we made sure to add and style the following:

Images related to the desktop version.
use of grid and flexbox where necessary
include media queries where necessary for responsive design on desktop.
use media queries in our CSS file to make our desktop version look like the template we selected (Desktop: 768px or wider).
we did replicate the design as much as possible (e.g., font, colors, images, text, margins) using the info from the Figma templates.

Hi @Abenezer-Tilahun, please I would like to know the specific link you are referring to so I can work on it. thanks👍

I finished the laptop responsive design in this branch


Meeting with Jacopo and colleage report

Meeting report
@anhtuduong I just had a meeting with Jacopo and Max (Jacopo's colleague who had experience dealing with nnUnet model) yesterday. Following are the workflow they suggested I should do:

Ask<EMAIL_ADDRESS>for jump host access (this is required to access to Optimus - a machine that they said is similar to Google Collab, Kaggle,... that have strong GPU to run the model) (done)

It shows in nnUnet documentation that "nnU-Net expects datasets in a structured format. This format is inspired by the data structure of the Medical Segmentation Decthlon." They said I should try download and run this structured data so I can understand how the file is organized. Moreover, this dataset is light so I can try doing that quickly.
For example, I may want to try dealing with Task04_Hippocampus.tar file - the lightest dataset. (downloaded)

After having the jump host access, Max will provide me his account to use the Optimus.

Max will share the contact of Miliano who had experience with Optimus so I can understand basically how it works.

Install nnUnet on Optimus

Try to run MSD dataset

@anhtuduong In the meantime, I am still trying to do understand the preprocessing part.


added category clothing

Added a new category: "Clothing" consisting of various types clothes

Codecov Report

Merging #35 into main will decrease coverage by 0.24%.
The diff coverage is 80.00%.

@@             Coverage Diff             @@
##              main      #35      +/-   ##
===========================================
- Coverage   100.00%   99.75%   -0.25%
===========================================
  Files           48       49       +1
  Lines          409      405       -4
===========================================
- Hits           409      404       -5
- Misses           0        1       +1

Impacted Files
Coverage Δ

qual_id/categories/clothing.py
75.00% <75.00%> (ø)

qual_id/pattern.py
100.00% <100.00%> (ø)

test/utils/category_helper.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


GCD and LCM

Is your feature request related to a problem? Please describe.
We are given two numbers. We need to find there greatest common divisor (GCD) and least common divisor (LCM).
Describe the solution you'd like
Using Recursion to find greatest common divisor (GCD) and least common divisor (LCM) of given numbers.
Describe alternatives you've considered
Using Recursion in place of iterative process.
Please Assign this task to me Using C++

Is your feature request related to a problem? Please describe.
We know the concepts of Greatest Common Divisor and Least Common Multiplier. We also require them in various competitive coding questions as well as real life examples as well as an approach to simple mathematical calculation.
Example like:
Five bright coloured lights flash once in 2,4,6,8 and 10 seconds respectively. After how much time will they all flash together ??
Answer LCM(2,4,6,8,10) = 120 seconds. The disco will be brilliantly lit with multi color bulbs every 120 seconds. Fact can be used to make Disco more attractive by tweaking the flash interval of individual flash lights.
Describe the solution you'd like
I will be providing solutions based on recursion,loops as well as inbuilt standard template library functions provided in c++.
Describe alternatives you've considered
We can use recursion instead of iterations.
We can also use given __gcd() and lcm() instead of recursion to simplify the process.
Please Assign this task to me Using C++ and SWOC S3

Since this is an easy task, @Shubh08am you have to code GCD and LCM in all four languages

This algorithm has been implemented in all four languages


edit aborted

I typically get the edit aborted but finally get this message today.  The edit aborted error is frequent and make it impossible to get anything done.  Please fix
AbstractController::DoubleRenderError in CatalogController#explorer
Render and/or redirect were called multiple times in this action. Please note that you may only call render OR redirect, and at most once per action. Also note that neither redirect nor render terminate execution of the action, so if you want to exit an action after redirecting, you need to do something like "redirect_to(...) and return".
Extracted source (around line #15):
13
14
15
16
17
18
# Check for double render errors and set the content_type after rendering.
def render(*args) #:nodoc:
  raise ::AbstractController::DoubleRenderError if self.response_body
  super
end

manageiq.txt

@alpha00Zero I see you're using rails <IP_ADDRESS> in the attached txt file.  We're now using rails 5 on master.  Can you provide a screenshot and what version you see this error on?  Can you see if this error occurs on master and provide what steps you followed to recreate it?

@alpha00Zero is this still an issue?  As @jrafanie mentioned, can you please provide a screenshot as well as a recipe to recreate this.  Thx, Dan


How to use the container with an existing Grafana and Prometheus instance?

I already have Grafana and Prometheus setup monitoring other stuff. How to we config the docker container like unifi-poller was?

you would need to have prometheus scrape the exposed port configured in your configuration file in the prometheus section


Ports for docker compose?

Hi there:
I'm trying to run Lurker via docker compose but having trouble with setting the port:
version: "3.9"
services:
  lurker:
    image: ghcr.io/oppiliappan/lurker:latest
    container_name: Lurker
    security_opt:
      - no-new-privileges:true
    ports:
      - 9495:3000
    volumes:
      - /Users/fdsafsd/Documents/docker/lurker:/data
    restart: on-failure:5

With this I get "Connection was reset" error message.
Thanks in advance.

i personally do not use docker-compose to setup services, but i assume the loopback address that lurker listens on (localhost), is not accessible/being exposed correctly. latest master contains the change to make this listen on <IP_ADDRESS>, do let me know if that works.

I've just installed with a similar docker compose to above, and can confirm everything seems to be working just fine in the current version.

glad.
happy to reopen if the issue continues to exist.


Breaking changes

84fa70cae6ba9b53f4c3027b86427d3ffdb2535b deprecates this plugin's null-ls integrations (and ef4f4ac3191c09c44003f9e348f6c3c62a6b18f0 removes them completely).
Since I spun null-ls off from this plugin, I've received requests from users who wanted to configure the sources included here separately. It's now possible to set up diagnostics, formatting, and ESLint code actions exclusively via null-ls. As a result, I've deprecated the integrations here.
To replicate the previous functionality and migrate to the null-ls API (the recommended option), remove all ESLint / formatter-related settings from your nvim-lsp-ts-utils config and use the following as a basis:
local null_ls = require("null-ls")
null_ls.config({
    sources = {
        null_ls.builtins.diagnostics.eslint.with({ -- eslint or eslint_d
            prefer_local = "node_modules/.bin",
        }),
        null_ls.builtins.code_actions.eslint.with({ -- eslint or eslint_d
            prefer_local = "node_modules/.bin",
        }),
        null_ls.builtins.formatting.prettier.with({ -- prettier, eslint, eslint_d, or prettierd
            prefer_local = "node_modules/.bin",
        }),
    },
})
require("lspconfig")["null-ls"].setup({ on_attach = on_attach })

This will register sources for diagnostics, formatting, and code actions that automatically use project-local executables when available and fall back to global executables. Other options you may have set in eslint_opts / formatter_opts can now be passed directly into with.
You can use your plugin manager to pin to 825630a5d28634fbb3663d1e605ff0a82b843d81, the last commit before the deprecation, but you won't receive further updates, so I recommend migrating.
You may also want to consider migrating to the ESLint language server, which can also provide ESLint diagnostics, code actions, and formatting. I've personally switched and find it fast and stable enough to use for daily work.
I hope that shifting integrations entirely to null-ls can help this plugin stay focused and continue to grow. In the future, I'd like to make it a "full" LSP plugin like rust-tools.nvim that automatically sets up tsserver + additional functionality, and removing the burden of coordinating integrations with another plugin will help.

627963630691c3f3113a8b549fca4246ed4960eb switches to the new vim.diagnostic API. As a consequence, the plugin now depends on Neovim 0.6.0.
If you don't want to or cannot update, you can pin the plugin to 7c52536cf40cc1cad3f39ba4e044ce7e92c99758, but Neovim 0.6.0 contains a lot of improvements, so you should aim to update as soon as you can.


Mark OperationsClient classes private, and change synth scripts to reproduce

Fix for https://github.com/GoogleCloudPlatform/google-cloud-ruby/issues/2235

@dazuma Can we apply this fix to Video Intelligence (#2327) and Vision (#2328) as well?

@blowmage This PR already covers Video Intelligence and Vision.


Improve CreateCollectionTask tests

I noticed some issues:

Existence of existing parent collections after revert not tested
Testing is too verbose (should use exists())

Done.


Async weather loader and crop simulation

Hello @tzoiker!
Could you help with async for weather loading anc crop model part here ?
https://github.com/mishagrol/CropBot/blob/6224d08c86d0fa69d352575ab11cf2b771c71c88/src/bot.py#L655C1-L671C10

@all-contributors please add @tzoiker for tests and code

@all-contributors please add @matseralex  for Mentoring and  ideas

@all-contributors please add @petrovskaia for design and research

@all-contributors please add @evgps for code and infrastructure


QControl - export/import of customised hierarchy levels

I am testing the QControl tool. Once I have created a customised level of the hierarchy that I am happy with, I would like to be able to export this and import it into another file (without having to make manual hierarchy adjustments). I'm going to be working with hundreds of files, so something user friendly and efficient would be great.

NESYS_Tools\QControl-v0.5 contains a version where there is an "Import hierarchy" item in the File menu. It can be used to load hierarchy from a QControl JSON file.
It's an absolutely minimal implementation, with no checks and conveniences:

it has to be used when a series is loaded already, otherwise it will crash
it modifies the tree only - it does not reset existing markers, so they may become nonsense
it does not check for matching atlas versions, and may crash when they differ
it has not been tested extensively, the whole 3 times I tried it worked.

NESYS_Tools\QControl-v0.5 contains a version where there is an "Import hierarchy" item in the File menu. It can be used to load hierarchy from a QControl JSON file.
It's an absolutely minimal implementation, with no checks and conveniences:

it has to be used when a series is loaded already, otherwise it will crash
it modifies the tree only - it does not reset existing markers, so they may become nonsense
it does not check for matching atlas versions, and may crash when they differ
it has not been tested extensively, the whole 3 times I tried it worked.

Ok thanks! I tested and it worked fine, every little helps =)

Ok thanks! I tested and it worked fine, every little helps =)

This feature needs check and conveniences before it can be released to external users: it is not user friendly as is. My suggestion is to enable export and import of a customised hierarchy file, with automatic reset of all markers on import, but maybe you have better ideas @Tevemadar ? We can discuss this at a SW meeting.


remaining Anna Ho comments

[x] Figure order (Figures are not referred to in order)?
[x] Units on plots - inconsistent in that sometimes there, sometimes not
[x] Anna suggests stating we do not create ground truth we only propagate the training set (see email for more details).

Regarding the "units on plots" item (cc @annayqho):
I only use "dex" units for abundances when they are referring to a difference in abundances, not respect to Solar. For example in fig:label-recovery-snr, units are only used in abundances because it is showing the difference with respect to the high S/N combined spectrum. As far as I can see, units are consistently used elsewhere.

Got it! Makes sense, thanks.

I think this can be closed, but I will leave it open for @davidwhogg to close.


Update line 46 of TP53_sequence.txt

Merged your changed and added another line (51) as the line you added was already added by another student.


fix #162

fix #162
The path can be a directory or a file, so it should be checked.

This change is

Coverage remained the same at 91.885% when pulling d312f17c793e7782ed38fe1999ca0c433819fafb on lisez:fix_issue_162 into 9744a02f592c5177a11388bf83e5c2c47e0027f1 on kucherenko:master.


⚠ AVS (kty) has degraded performance

In 36238d3, AVS (kty) (https://avus.com.br) experienced degraded performance:

HTTP code: 200
Response time: 8577 ms

Resolved: AVS (kty) performance has improved in d093d23.


Example using the assemblyOutputPath parameter

Hello! I want to change the path of the assembly file app/simple.jar
Need example for assemblyOutputPath, because they do not really understand what to write.
Thx!

Please see https://github.com/sbt/sbt-assembly/blob/master/CONTRIBUTING.md


Define workflow for QoS enforcement

LM gets a list of agents from Recomender
LM sends the list to COMPSs
COMPSs publish expected execution time during service runtime
QoS enforcer detects if SLA will be broken based on the expected execution time
if true, then QoS enforcer notifies the LM (how??)
LM gets an updated (if so) list of devices from Recommender
LM sents the new list to COMPSs

In 2. and 7., LM will use service's num_agents property to set the number agents where to run the COMPSs service.
In 5., LM will provide a method to get and process the QoS enforcer notifications


Main function parameters must match one of the signatures

User from Discord tried to build an example project and it resulted in an error.
https://github.com/dlang/visuald/blob/master/visuald/Templates/ProjectItems/VDProject/main.d#L14

Rename of main function worked.

Fresh install of Visual Studio 2022 and Visual D 1.4.0-rc1, hit new project, x64, DMD+LDC enabled (no dialog options seemed to matter)

Thanks for reporting. dmd 2.100 added this extra check, which is a false positive in this case. I'll rename the function to win_main.


Error

Keep getting the error:
ERROR: Requirements have not been satisfied properly. Please look at the README file for configuration instructions.
Details: No module named 'scapy'
When I try to install scapy it says I already have it installed.

You should try this
curl -O http://python-distribute.org/distribute_setup.py
sudo python3.3 distribute_setup.py
sudo python3.3 -m easy_install pip

OR
visit this page...
http://lgogua.blogspot.in/2013/10/how-to-install-pip-for-python3-in-kali.html

Closing due to inactivity; assuming that the issue has been solved.


Update tapir-core, tapir-http4s-server, ... to 0.19.0

Updates

com.softwaremill.sttp.tapir:tapir-core
com.softwaremill.sttp.tapir:tapir-http4s-server
com.softwaremill.sttp.tapir:tapir-json-circe
com.softwaremill.sttp.tapir:tapir-newtype
com.softwaremill.sttp.tapir:tapir-openapi-circe-yaml
com.softwaremill.sttp.tapir:tapir-openapi-docs
com.softwaremill.sttp.tapir:tapir-openapi-model

from 0.19.0-M4 to 0.19.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.softwaremill.sttp.tapir" } ]

labels: library-update, early-semver-pre-release, semver-spec-pre-release

Superseded by #156.


How to add interior borders/column separators?

I cant figure out how to add vertical dividers for the columns please assist

Hi, I beleive you'd like to get smth like that:

'- there's currently no API exposed that allows to add inner borders.
There're 2 options:

Wait for a few days for me to add and publish the feature.
Do a quick workaround by copying plugins sorces to you projects folder and making an ad-hoc fix there (lib/data_table2.dart - add border property):

      var dataRows = Table(
        columnWidths: widthsAsMap,
        children: tableRows,
        border: TableBorder(verticalInside: BorderSide(color: Colors.grey)),
      );

      var t = Column(
        mainAxisSize: MainAxisSize.min,
        children: [
          Table(
              columnWidths: widthsAsMap,
              children: [headingRow],
              border:
                  TableBorder(verticalInside: BorderSide(color: Colors.grey))),

Btw, there's an issue in Flutter's repo requesting the same API to be exposed: https://github.com/flutter/flutter/issues/36837

Thanks for that. Looking forward to the update! I saw the request on Flutter but seems nothings happened yet

2.0.4 has the feature, sorry for taking a bot longer than promised to publish the update

That was quick! Amazing thanks mate! I'll be using it


HttpCommand instance methods should all return a result, even if it's shy

The SetHeader, AddHeader, and RemoveHeader methods do not return results which makes their use in dfns a bit awkward.  The should return a shy result of the Headers array.

Fixed in 0e3b166e5bc47084371f04ace7da50de026c4fbc


chore(site): ui-playground integration for menu

Closes: https://github.com/exadel-inc/esl/issues/2157

Merging as a site content going to be finally reviewed in bounds of overall 4.15.0 content invalidation

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 5.0.0-beta.12 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Chart List performance issue caused by sql with cartesian join generated by flask-app-builder

Version: I found this bug even on the latest version cloned today.
When user is accessing the chart list page, the get_list controller method of BaseSupersetModelRestApi is called which eventually call the get_list_headless method of the BaseApi class in the  flask_appbuilder.api.__init__  package. The query generated as it turns out is as below with cartesian join between anon_1 and last_saved_by:
SELECT anon_1.last_saved_by_id             AS anon_1_last_saved_by_id,
       anon_1.last_saved_by_first_name     AS anon_1_last_saved_by_first_name,
       anon_1.last_saved_by_last_name      AS anon_1_last_saved_by_last_name,
       last_saved_by.username              AS last_saved_by_username,
       last_saved_by.password              AS last_saved_by_password,
       last_saved_by.active                AS last_saved_by_active,
       last_saved_by.email                 AS last_saved_by_email,
       last_saved_by.last_login            AS last_saved_by_last_login,
       last_saved_by.login_count           AS last_saved_by_login_count,
       last_saved_by.fail_login_count      AS last_saved_by_fail_login_count,
       last_saved_by.created_on            AS last_saved_by_created_on,
       last_saved_by.changed_on            AS last_saved_by_changed_on,
       last_saved_by.created_by_fk         AS last_saved_by_created_by_fk,
       last_saved_by.changed_by_fk         AS last_saved_by_changed_by_fk,
       anon_1.tables_id                    AS anon_1_tables_id,
       anon_1.tables_default_endpoint      AS anon_1_tables_default_endpoint,
       anon_1.tables_table_name            AS anon_1_tables_table_name,
       anon_1.created_by_id                AS anon_1_created_by_id,
       anon_1.created_by_first_name        AS anon_1_created_by_first_name,
       anon_1.created_by_last_name         AS anon_1_created_by_last_name,
       anon_1.changed_by_id                AS anon_1_changed_by_id,
       anon_1.changed_by_first_name        AS anon_1_changed_by_first_name,
       anon_1.changed_by_last_name         AS anon_1_changed_by_last_name,
       anon_1.slices_changed_on            AS anon_1_slices_changed_on,
       anon_1.slices_id                    AS anon_1_slices_id,
       anon_1.slices_slice_name            AS anon_1_slices_slice_name,
       anon_1.slices_datasource_id         AS anon_1_slices_datasource_id,
       anon_1.slices_datasource_type       AS anon_1_slices_datasource_type,
       anon_1.slices_viz_type              AS anon_1_slices_viz_type,
       anon_1.slices_params                AS anon_1_slices_params,
       anon_1.slices_description           AS anon_1_slices_description,
       anon_1.slices_cache_timeout         AS anon_1_slices_cache_timeout,
       anon_1.slices_last_saved_at         AS anon_1_slices_last_saved_at,
       anon_1.slices_last_saved_by_fk      AS anon_1_slices_last_saved_by_fk,
       anon_1.slices_certified_by          AS anon_1_slices_certified_by,
       anon_1.slices_certification_details AS anon_1_slices_certification_details,
       anon_1.slices_created_by_fk         AS anon_1_slices_created_by_fk,
       anon_1.slices_changed_by_fk         AS anon_1_slices_changed_by_fk
FROM   (
                       SELECT          slices.changed_on            AS slices_changed_on,
                                       slices.id                    AS slices_id,
                                       slices.slice_name            AS slices_slice_name,
                                       slices.datasource_id         AS slices_datasource_id,
                                       slices.datasource_type       AS slices_datasource_type,
                                       slices.viz_type              AS slices_viz_type,
                                       slices.params                AS slices_params,
                                       slices.description           AS slices_description,
                                       slices.cache_timeout         AS slices_cache_timeout,
                                       slices.last_saved_at         AS slices_last_saved_at,
                                       slices.last_saved_by_fk      AS slices_last_saved_by_fk,
                                       slices.certified_by          AS slices_certified_by,
                                       slices.certification_details AS slices_certification_details,
                                       slices.created_by_fk         AS slices_created_by_fk,
                                       slices.changed_by_fk         AS slices_changed_by_fk,
                                       changed_by.id                AS changed_by_id,
                                       changed_by.first_name        AS changed_by_first_name,
                                       changed_by.last_name         AS changed_by_last_name,
                                       created_by.id                AS created_by_id,
                                       created_by.first_name        AS created_by_first_name,
                                       created_by.last_name         AS created_by_last_name,
                                       last_saved_by.id             AS last_saved_by_id,
                                       last_saved_by.first_name     AS last_saved_by_first_name,
                                       last_saved_by.last_name      AS last_saved_by_last_name,
                                       `tables`.id                  AS tables_id,
                                       `tables`.default_endpoint    AS tables_default_endpoint,
                                       `tables`.table_name          AS tables_table_name
                       FROM            slices
                       LEFT OUTER JOIN ab_user AS changed_by
                       ON              slices.changed_by_fk = changed_by.id
                       LEFT OUTER JOIN ab_user AS created_by
                       ON              slices.created_by_fk = created_by.id
                       LEFT OUTER JOIN ab_user AS last_saved_by
                       ON              slices.last_saved_by_fk = last_saved_by.id
                       LEFT OUTER JOIN `tables`
                       ON              slices.datasource_id = `tables`.id
                       AND             slices.datasource_type = %(datasource_type_1)s
                       ORDER BY        slices.changed_on DESC limit %(param_1)s) AS anon_1,
       ab_user                                                                   AS last_saved_by

As we can see,  there is no join condition on anon_1 and last_saved_by and the performance is poor once both the table gets large.
As I dig deeper, I found the cartesian join is generated by the from_self call in the apply_all method of the class flask_appbuilder.models.sqla.interface, I wonder if there is anything we could do to fix this?

After debugging for 2 days and seeing no easy solution for this, I have decided to comment out the user relation info part in the list_column of the class ChartRestApi and the performance boost is major, going down from 30 seconds in my production to roughly 0.5 ms, the catch is we lose the user related info, but that 's fine, I will add the user info back in the pre_get_list hook. For now, it's my solution.

I just tested v2.1.0 on our staging environment and saw a significant increase in loading times on the dashboards and charts pages and found this issue.
Compared to v2.0.1, the pod cpu usage in our K8s cluster increased from ~185 millicores to ~520 millicores when continuously refreshing the dashboards and charts pages. I assume this issue is the root cause for this? Didn't want to create a separate issue in case it's a duplicate.

I think this is something @john-bodley took a stab at quite some time ago if memory serves. Is it still an issue in 3.0?

@DataScientistSamChan you might want to check out the following PRs which might help explain the problem:

https://github.com/apache/superset/pull/22413
https://github.com/apache/superset/pull/23113

I'm assuming/hoping that the above PRs mitigated the problem. It's been several months since the last comments here, so I'm closing this as stale. If anyone wants to chip in here with updated context/metrics/etc, we can certainly reopen this.


advance tutorial page is not working

The link provided in the document not working please check.
http://qtip2.com//tutorials/advanced

There is no tutorials section on the website, only Guides. Might be an old link indexed somewhere from the qTip1 docs.


Removed redundant casts with MathF support

System.MathF should be used instead of System.Math to prevent double-casting values.

This can't be done yet because MathF is not available when targeting .NET Framework (which is what Godot uses as a target by default), and also Mono does not have "full" support for .NET Standard 2.1, so it's not guaranteed to work in that case either.
https://docs.microsoft.com/en-us/dotnet/api/system.mathf

This can be re-evaluated in the future if Godot switches to .NET Core (re-branded to ".NET" as of version 5.0). It's hard to give an ETA of when this will be the case, but I can give you a broad range of 2-10 years.


Add method documentation to cuda package

Improve gorepord by adding documentation to cuda package methods.
#328

Coverage remained the same at 62.937% when pulling 98a543fb6c4b9fa1093ee442b5c27eac483bdbad on ilyakaznacheev:master into 1969ec3b19e8c3f9a3ffe9a854571223d4e16054 on gorgonia:master.


For Kris: id: both_cant_divorce_current_state

I'm not sure if I ID right  here, but this is after answering no to 1. do you live in VT? 2. Does the defendant live in VT? 3. Did you get a civil union in VT?
This could probably be a stop screen. If they didn't get a civil union here and neither of them live here, we would want to redirect them to their state.

Similarly, on this page: id: property agreement
If they have already answered the way I shared above and they also answer no to "Do you and your spouse currently live in states where you can’t get a divorce or dissolve your civil union?" They can move to "Do you and your spouse already have an agreement about how to deal with your property and debts?" and if they click yes, it lets them begin filling out forms.


fix armv7 download for dunfell branch

Issue #, if available: -
Description of changes:
I checked out the current dunfell branch and noticed it does not build greengrass v2 bin for ARM because corretto fetch sources task is failing. Cherry picked the missing commit from meta-aws master.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

very sorry about that.


Add support for PEP-723 script metadata to --exe.

Pex now reads script metadata present in --exes by default to augment
requirements and constrain allowed target Pythons. Pex can be instructed
to ignore this script metadata though with --no-pep723 /
--no-script-metadata.
This apparently makes due on a promise no active Pex maintainer ever
made, as immortalized in PEP-723:
https://peps.python.org/pep-0723/#tooling-buy-in

Ok, 94b1e2c was a big addition:
:; git diff --stat 94b1e2c03a7fd9c49f479b2885a294e7ac00b519^!
 pex/pep_723.py        | 237 +++++++++++++++++++++++++++++++++++++++++++------
 tests/test_pep_723.py | 240 +++++++++++++++++++++++++++++++++++++++++++++++++-
 2 files changed, 447 insertions(+), 30 deletions(-)

That's the price you pay when not normal users, but programmers (who presumably know how to debug), lose their debugging skills when the code is not theirs. I'm obviously grumpy about this state of the world, but I can play along.

I am working my way through this while reading the PEP. Will respond hopefully later today, europe time.

Hey there, thank you for taking the time to implement this! I have two questions:

Could you please explain a bit further how the regular expression here breaks? https://packaging.python.org/en/latest/specifications/inline-script-metadata/#specification
Is there anything I could have done differently? I feel bad that you folks aren't very happy.

For 1, given:
import re
from textwrap import dedent

REGEX = r'(?m)^# /// (?P<type>[a-zA-Z0-9-]+)$\s(?P<content>(^#(| .*)$\s)+)^# ///$'

def collect_metadata_blocks(text):
    return list(re.finditer(REGEX, text))

EXAMPLE1 = dedent(
    """\
    # /// script
    # ///
    # /// script
    # ///
    """
)

EXAMPLE2 = dedent(
    """\
    # /// script
    # dependencies = ["ansicolors"]
    # ///
    #
    # /// script
    # dependencies = ["ansicolors"]
    # ///
    """
)

example1 = collect_metadata_blocks(EXAMPLE1)
print(example1)
for index, match in enumerate(example1):
    print(index, match.group("type"), match.group("content"))

example2 = collect_metadata_blocks(EXAMPLE2)
print(example2)
for index, match in enumerate(example2):
    print(index, match.group("type"), match.group("content"))

You find:
:; python example.py
[<re.Match object; span=(0, 37), match='# /// script\n# ///\n# /// script\n# ///'>]
0 script # ///
# /// script

[<re.Match object; span=(0, 103), match='# /// script\n# dependencies = ["ansicolors"]\n# >]
0 script # dependencies = ["ansicolors"]
# ///
#
# /// script
# dependencies = ["ansicolors"]

So the re is too greedy for practical use afaict. It forces you to write 2 script blocks in separate comments (a non "#", non "# "* line is required between them.
For 2, I don't think you were the problem here.

Josh misrepresented himself as being able to speak for Pex / never relayed he did this to an active Pex maintainer. Clearly not your problem. You would have had to have checked with all the projects that promised support to verify those speaking were in fact valid representatives for those projects. I think the default in the PyPA / Python communities is trust.
The TOML choice was effectively sealed in in PEP-518. The fact that Python / the PyPA adopt standards that require code outside either's control for non-deprecated Python versions seems ridiculous to me. Perhaps PyPA tried and failed to adopt toml or tomli / tomli-w and deemed splitting the community further by writing their own under https://github/com/PyPA/ was undesirable or that it was simply too much effort.

Belatedly I just realized this is an almost useful thing now:
#!/usr/bin/env -S pex --exe
# /// script
# ...
# ///
...

So if you know your target environment has recent enough Pex installed on the path. instead of scp'ing a PEX file, you scp just the script. Kind of a party trick though since its very slow to start up that way.


Docs: Fixed broken link in zip.rst

I was browsing the documentation and i noticed that the file zip.rst has a broken link.

Moving pull request to https://github.com/cpp-pm/hunter


Block forever on uploading file to GCS is GCS server return status code other the 2XX

(delete this for feature requests)
Client
e.g. Storage
Describe Your Environment
Go 1.10 on Linux
Expected Behavior
Retry to upload file should not be automatic. Let the user decide about retry.
Or, set a default timeout
Actual Behavior
ctx := context.Background()
gsclient, err := storage.NewClient(ctx, opt...)
uploader := gsclient.Bucket(bucket)
wc := uploader.Object(key).NewWriter(ctx)
 wc.Write(bufCopy.Bytes())
wc.Close() // Block forever if GCS service return status code > 299

Workaround
Use context with timeout.
ctx, cancel := context.WithTimeout(context.Background(), s.config.HTTPClientTimeout)
defer cancel()

That's not merely a workaround. All our client libraries are designed to retry indefinitely. Setting a timeout on the context is the intended way to stop them.

I find it hard to believe that any client wants to retry indefinitely, but leaving that aside, this should be documented some where and should be mandatory in the examples.

Good points. Repurposing this issue.


Design question

First of all: great work, really interesting initiative !
Considering the algorithm, I assume that sorted / range queries is not planned ?

Thanks. Sorted rangers won't be possible, but we do have lists (kinda like linked-lists/deque)


Remove usage of the word “whitelist”

It is by now widely recognised (Examples: 1, 2, 3), that the use of the term “whitelist” is bad because of its racial overtone. So please rephrase where it is used.
The term “allowlist” seems to be what usually supersedes the old term when used as a noun and just “allow” when used as a verb, maybe with small adjustments.

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

Coverage remained the same at 95.192% when pulling c7c8bd9c797aa508e42ef90b4b7fdb704ff02775 on datenreisender:replace_term_whitelist into 7243f8586c4e331005c33fac277d5a4c0712fbb6 on cla-assistant:master.

Thank you very much for your engagement and for this PR!


Bumped node-gyp version

A new version of node-gyp was just released based on this comment: https://github.com/nodejs/node-gyp/pull/1718#issuecomment-486023253

Should fix #2625.

Please check all the other duplicate closed PRs. The fix is much more complicated for us. We're on it.

I mentioned this on this thread (1456ef2) , but I am still having an issue when I update node-gyp. I run npm install node-gyp and get the correct 4.0.0 package, but then I get an error that I something changed and I need to "Run npm rebuild node-sass to download the binding for your current environment." When I do this, it re-loads the 3.8.x version of node-gyp. Error below from the rebuild of node-sass:
gyp ERR! node -v v9.4.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! This is a bug in node-gyp.
gyp ERR! Try to update node-gyp and file an Issue if it does not help:
gyp ERR! https://github.com/nodejs/node-gyp/issues
Build failed with error code: 7
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.


Paving the Way for Model Flexibility in xef.core and Increasing GPT-3.5 Turbo's Context Window

Summary
This PR marks an important shift in the xef.core module, as it lays the groundwork for removing the dependency on OpenAI and enabling the usage of local models and other types of models within the ai block. This flexibility allows the system to be more adaptive and versatile in accommodating various AI models.
Moreover, this PR also includes an update to increase the context window of the GPT-3.5 Turbo model to 16k tokens, enabling the model to consider a larger context when generating responses, thereby potentially improving the model's understanding of the provided context and its ability to generate more relevant responses.
Details
The changes introduced in this PR include:

Refactoring of AI.kt to use AIClient instances instead of specifically OpenAIClient instances. This allows for more versatility and flexibility in the types of AI models that can be used within the ai block.

Creation of a new file AIRuntime.kt that defines an AIRuntime data class. This class provides a structured way to override the runtime environment for executing AI blocks.

Changes to AIScope.kt to accommodate the updates in AI.kt and AIRuntime.kt. The updates include the addition of new parameters like defaultModel, defaultSerializationModel, and AIClient, among others.

The context window of the GPT-3.5 Turbo model has been increased to 16k tokens in the AIScope of the default Open AI AIRuntime.kt. This update allows the model to consider a larger context when generating responses, potentially improving its understanding of the documents in context and its ability to generate more relevant responses. The documents in context default are now 20.

@xebia-functional/team-ai


Rename cf_units to cf-units

Closes #112.

I've renamed the repo, updated the travis-ci config etc.

@pelson Some license headers fails...

🤞


Variant products with wrong data

How To Test This?
The steps are mentioned in the provided video link.
https://webkul.chatwhizz.com/share/view-recording/670fa93ca487c159420c4c5d

@devansh-pal-webkul , Updated with the requested changes


Added back removed metadata

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/about-character-mode-applications.md
:warning:Warning
View
Details

docs/attaching-to-a-console.md
:warning:Warning
View
Details

docs/character-mode-applications.md
:warning:Warning
View
Details

docs/clearing-the-screen.md
:warning:Warning
View
Details

docs/closing-a-console.md
:warning:Warning
View
Details

docs/console-aliases.md
:warning:Warning
View
Details

docs/console-application-issues.md
:warning:Warning
View
Details

docs/console-buffer-security-and-access-rights.md
:warning:Warning
View
Details

docs/console-code-pages.md
:warning:Warning
View
Details

docs/console-control-handlers.md
:warning:Warning
View
Details

docs/console-functions.md
:warning:Warning
View
Details

docs/console-handles.md
:warning:Warning
View
Details

docs/console-input-buffer.md
:warning:Warning
View
Details

docs/console-modes.md
:warning:Warning
View
Details

docs/console-process-groups.md
:warning:Warning
View
Details

docs/console-reference.md
:warning:Warning
View
Details

docs/console-screen-buffers.md
:warning:Warning
View
Details

docs/console-selection.md
:warning:Warning
View
Details

docs/console-structures.md
:warning:Warning
View
Details

docs/console-virtual-terminal-sequences.md
:warning:Warning
View
Details

docs/consoles.md
:warning:Warning
View
Details

docs/creation-of-a-console.md
:warning:Warning
View
Details

docs/ctrl-c-and-ctrl-break-signals.md
:warning:Warning
View
Details

docs/ctrl-close-signal.md
:warning:Warning
View
Details

docs/getconsolescreenbufferinfo.md
:warning:Warning
View
Details

docs/high-level-console-i-o.md
:warning:Warning
View
Details

docs/high-level-console-input-and-output-functions.md
:warning:Warning
View
Details

docs/high-level-console-modes.md
:warning:Warning
View
Details

docs/input-and-output-methods.md
:warning:Warning
View
Details

docs/low-level-console-i-o.md
:warning:Warning
View
Details

docs/low-level-console-input-functions.md
:warning:Warning
View
Details

docs/low-level-console-modes.md
:warning:Warning
View
Details

docs/low-level-console-output-functions.md
:warning:Warning
View
Details

docs/reading-and-writing-blocks-of-characters-and-attributes.md
:warning:Warning
View
Details

docs/reading-input-buffer-events.md
:warning:Warning
View
Details

docs/registering-a-control-handler-function.md
:warning:Warning
View
Details

docs/scrolling-a-screen-buffer-s-contents.md
:warning:Warning
View
Details

docs/scrolling-a-screen-buffer-s-window.md
:warning:Warning
View
Details

docs/scrolling-the-screen-buffer.md
:warning:Warning
View
Details

docs/using-the-console.md
:warning:Warning
View
Details

docs/using-the-high-level-input-and-output-functions.md
:warning:Warning
View
Details

docs/window-and-screen-buffer-size.md
:warning:Warning
View
Details

docs/TOC.md
:white_check_mark:Succeeded
View

docs/addconsolealias.md
:white_check_mark:Succeeded
View

docs/allocconsole.md
:white_check_mark:Succeeded
View

docs/attachconsole.md
:white_check_mark:Succeeded
View

docs/char-info-str.md
:white_check_mark:Succeeded
View

docs/console-cursor-info-str.md
:white_check_mark:Succeeded
View

docs/console-font-info-str.md
:white_check_mark:Succeeded
View

docs/console-font-infoex.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

docs/about-character-mode-applications.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/attaching-to-a-console.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/character-mode-applications.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/clearing-the-screen.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/closing-a-console.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/console-aliases.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/console-application-issues.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/console-buffer-security-and-access-rights.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/console-code-pages.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/console-control-handlers.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/console-functions.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/console-handles.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/console-input-buffer.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/console-modes.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/console-process-groups.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/console-reference.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/console-screen-buffers.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/console-selection.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/console-structures.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/console-virtual-terminal-sequences.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/consoles.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/creation-of-a-console.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/ctrl-c-and-ctrl-break-signals.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/ctrl-close-signal.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/getconsolescreenbufferinfo.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/high-level-console-i-o.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/high-level-console-input-and-output-functions.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/high-level-console-modes.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/input-and-output-methods.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/low-level-console-i-o.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/low-level-console-input-functions.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/low-level-console-modes.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/low-level-console-output-functions.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/reading-and-writing-blocks-of-characters-and-attributes.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/reading-input-buffer-events.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/registering-a-control-handler-function.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/scrolling-a-screen-buffer-s-contents.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/scrolling-a-screen-buffer-s-window.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/scrolling-the-screen-buffer.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/using-the-console.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/using-the-high-level-input-and-output-functions.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

docs/window-and-screen-buffer-size.md

[Warning] unexpected type String[] for metadata api_type, the expected type is string
[Warning] unexpected type String[] for metadata topic_type, the expected type is string
[Warning] unexpected type String[] for metadata api_location, the expected type is string
[Warning] unexpected type String[] for metadata api_name, the expected type is string

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


String data rendered into table in webchat but its not rendering properly in MS team

Describe the bug
I'm getting table data in string from OpenAI it is rendered into table in webchat fine but its not rendering properly in MS team. Please refer the screenshot.
To Reproduce
Steps to reproduce the behavior:

create a bot
integrate it with azure OpenAI
Ask the question "give me random student data in tabular form"

Expected behavior
want the same table rendering in both Webchat and MS Teams
Screenshots
Webchat

MS Teams

@NagarroShobharaja - A few questions for you.

Can you send the raw text you are using to send in the bot message?
Is this text formatted as markdown? From the picture, it appears to be.
If it is markdown, sending a markdown table may not be supported. This Teams doc) seems to confirm this.

Closing due to inactivity.


Send with ack is blocking for the rfm9x library

While we are awaiting a uhf ack, nothing else is running

While it doesn't completely block execution now, it still takes up a considerable amount of time.
With each send calling tx_done something like 226 times, nearly completely taking over the flow of execution from everything else.

interrupts in circuitpython not well supported


EditableGridCell should have a common newValue property

type EditableGridCell = TextCell | ImageCell | BooleanCell | MarkdownCell | UriCell | NumberCell;

EditableGridCell does not have a common property across union types that represents the new value, so you have to do clumsy checking in onCellEdited (for example). It would be nice to be able to:
onCellEdited={([col, row], editedCell) => console.log(editedCell.newValue)}

I think the naming is just bad:

Most cells have data, except for BooleanCell, which has checked.
Some cells also have editData, which is the actual underlying value, whereas their data is the display value.

I think we should

Make data always be the underlying value, and have an optional displayData when appropriate.
Rename checked in BooleanCell to data.


Bug :- The file glob pattern

@azeemshaikh38  The file glob pattern doesn't seem to work with the refactor. security.rst could be docs or other folders and it is not consistent across repositories.
Originally posted by @naveensrinivasan in https://github.com/ossf/scorecard/pull/656#discussion_r663547171

It does work, we use the glob pattern for matching here: https://github.com/ossf/scorecard/blob/main/checks/checkforcontent.go#L31
You simply need to pass in path.Match(globPattern, filename), as the predicate to ListFiles API.

Closing this. Re-open is needed.


Training Time for DeepLab v3

Nice work done. Just curious, how much time does it take to train the model? Some other models, such as Mask R-CNN, take more than one days to train on a 8-GPU machine using standard COCO dataset. I wonder if DeepLab has any advantages of training over other models, since I want to training it personally if the computation cost is not too expensive. Thank you.

It is fast.


PutMarkLogic sometimes stops running when there are still flow files available

After processing a large number of flow files, PutMarkLogic will sometimes stop running with a few left in the queue. PutMarkLogic has already requested them from the queue (they won't show up when asking NiFi to show the list of flow files in the queue), but just sits on them. Stopping PutMarkLogic triggers the @OnStopped event, calling the completeWriteBatcherJob method and finishing them up.
When Concurrent Tasks is greater than 1, it's possible that shouldFlushIfEmpty can end up false when the writeBatcher has unsent documents. When the processor gets stopped, the writeBatcher gets flushed and all's well.
I think we could address that using synchronized blocks when accessing or changing shouldFlushIfEmpty, right?

shouldFlushIfEmpty does look like the culprit here. I think converting it to an AtomicBoolean should do the trick, and then the state in PutMarkLogic is all concurrent-friendly.

@dmcassel  Thoughts on a good test case here? I have a fairly simple test where I have a GenerateFlowFile processor that spits out 200 flowfiles at a time, running every 1 second. I then have a PutML that writes to ML, and I configured that with a concurrency of 3 tasks. I let that flow run for awhile, then I stop GenerateFF and wait to see if everything gets flushed to ML.
With the change to AtomicBoolean, I still see FFs not getting written. I think there's still the problem of "shouldFlushIfEmpty" being a shared resource - I think it needs to somehow be associated with each task that's created for the processor.
Alternatively, we could always flush when FF is null in PutML, as I don't think there's any real penalty to that. The "context.yield()" call is what gives the user control over how often that happens by configuring "Yield Duration" on the processor. Thoughts on that?

Okay, now I'm pretty sure that shouldFlushIfEmpty is unnecessary and that context.yield() is all we need. Going to do the following:

Remove shouldFlushIfEmpty
Add info logging for when PutML calls context.yield(), just so it's obvious in the logs that it's happening

This means every time the PutML processor is invoked, it will do an async flush of the WriteBatcher. When it has zero docs, that's pretty much an instantaneous operation. Then it will yield, and the user can configure how long that takes.

@rjrudin I see you closed this ticket and that it was assigned to the <IP_ADDRESS> milestone. Any ETA on that release?

Hopefully today.

thanks @rjrudin!


positioning mouseTool and creating custom zoom control

This will address https://github.com/VEuPathDB/web-monorepo/issues/94 and https://github.com/VEuPathDB/web-components/issues/396 as they are closely related. A screenshot is attached in the end.

Some notes are made for helping the reviews in the following.

react-leaflet zoomControl component (even leaflet's zoom control) has an inherent limitation to arbitrarily position the zoom control: only four corners (e.g., top left, top right) can be used but due to the top header of the SAM and other floating Vizs, it was necessary to make a custom zoom control.
four zoom-related controls are made: zoom-in, zoom-out, zoom to whole world, and zoom to data.
FontAwesome is used for zoom to whole world and zoom to data icons because MUI icons suggested by Dave were hard to position correctly
zoom to whole world: Bob's suggestion using center: [1e8, 1e8] worked for MapViz, however, it seems that the value is too small for SAM (full screen mode) and map does not recognize it correctly. Thus, I increased it to [0.25, 0.25] which is visibly not that much difference from center: [0, 0].
zoom to data: I tried various approaches but settled down using center: [0,0], which will initiate flyTo function. However, some considerations were made:
a) SAM does not support flyTo yet, thus I could not test zoom to data in there: if necessary, I can work for enabling it (see below), Bob?
b) Thus, MapViz is utilized to test the zoom to data. However, I noticed that flyTo was executed much faster than before full data loading in this case, To avoid this issue, I made additional condition to perform the flyTo only if whole data is visible/loaded. This effectively prevents from running flyTo too quickly without interrupting the original flyTo functionality.
c) As mentioned above, I had to make possibly unnecessary codes for testing zoom to data feature at Mapviz, which are marked as typical(?) DKDK for now :). Not quite sure if we want to use this custom zoom control to the MapViz as well (Bob?). Either way, those DKDK will be treated later.

Thank you for your comments, @bobular. I added my opinion next to your comment in the following (starting with DK):

Looking good!
A general point is that when #125 is done (cc: @jernestmyers ) there will be no need to adjust positioning of controls to take account of the header.

Therefore I strongly recommend that the MapVEuMap should behave identically for SAM or EDA viz deployments. In other words remove the isStandAloneMap props.

DK: Yes I know that work by Jeremy. That being said, we still need to adjust some because both mouse mod/tool and zoom control are now customized. For the isSAM prop, if I remember correctly, the small map of the the full screen map (FSM) (left to the entity diagram) will be affected without having a specified prop. It could be a pre-existing prop instead of isSam but we will see.

I don't think we need the isEqual(completeCasesAllVars, markerSum) condition in the flyTo logic. But if we do, please explain why. We can surely remove this and the markerSum code (which will fail with string values '2k' etc. I guess).

DK: As I mentioned at my initial description of this PR (perhaps TL;DR ? 😄 ) it is for functioning zoom to data. Without the additional condition, flyTo is performed faster than full data loading. It works fine if all markers are visible, but if no or partial markers are visible, then flyTo is performed with none or limited markers which lead to incorrect behavior.
That markerSum can be computed inside useMapMarkers hook before converting large numer to k (e.g., '2k'), I suppose.  It is a temporary one as I mentioned so I think that we can adjust it if necessary.

@bobular I think that I addressed your feedbacks all for both MapViz and SAM: a) defaultViewport is used for setting zoom-to-data. I did change the default zoom of the SAM from 4 to 2 (same to MapViz). I guess this is alright owing to flyTo functionality? b) SAM now has flyTo as well as zoom-to-data as well; c) adjusted positions considering the not-overlapping-banner.
Actually there is an redundant part at MouseTool because of its use at FSM: positioning MouseTool. If FSM will be retired, then some simplification can be further made in the future.

@bobular As I mentioned earlier, if we do not consider FSM, then I can remove that prop isStandAloneMap(): FSM's mouseTool is overlapped with close icon (x).
By the way, at least for my case, I found the reason why zoom: 0 does not work for flyTo. When I checked viewport after performing zoom-to-data, the appState.viewport.zoom does not change to zero, but becomes 1 thus flyTo does not happen. I am not quite sure if it is due to my 4k resolution but it may be possible as I experienced an issue of viewport center for map's full-screen mode like SAM (in the case of zoom-to-whole-world)

@bobular Thanks 👍 Yes I will also look at it. What I also noticed is that I can't zoom out to zero when using zoom-out icon: the minimum zoom level I can reach is 1. So, perhaps it is related to my resolution.

@bobular addressed your feedbacks. Temporarily default zoom level of the SAM was set to be 1. Will test it more.

PS. I think we'll discuss styling these buttons in styling group tomorrow - if you can join, please do!