Teleport arrival position & orientation issue

When teleporting, it often happens that you arrive looking straight up into the sky.

Homes & Warps are also always set on the cross-point of 4 blocks.  I don't know anything about coding but it looks like the decimals of the coordinates are not saved. Setting a warp/home on a slab or similar will then teleport you into the slab on arrival (decimals of y-coordinate not saved).

I don't know anything about coding but it looks like the decimals of the coordinates are not saved.
The reason for this is that an integer (full numbers) is smaller than a double (e.g. 0.5). For this reason, you are always teleported to a full block. I've considered adding 0.5 to each, to put you on top of slabs and in the center of a block, but never implemented this.

As for looking at the sky, this seems to be a bug in vanilla where if you don't provide the looking direction, it won't keep the looking direction.


Model training duration

Hello ! Great paper and really cool idea overall !
Could you please report how long pretraining took (with the number of gpus) as well as training duration for the NER task on Conll 2003 ?

As reported in our paper, the pretraining was conducted using 16 NVIDIA Tesla V100 GPUs and took approximately 30 days (Appendix A). The training duration of CoNLL-2003 NER was 203 minutes (Table 11).


Can not start scan: 80008000!

I am using RPLiDAR A1 in Raspberry Pi 3B with ROS. I am getting this error when I launch the rplidar node with my launch file. How to rectify this error?

@Gowresh7 i am also facing the same problem , did u solve yours .
Please give a solution

So I identified the problem was primarily due to the inadequate power from the usb ports. Once I switched to a external powered usb hub, it was solved.

@Gowresh7 i am also facing the same problem , did u solve yours . Please give a solution

i am making a raspberry pi + rplidar a1 based autonomous robot car. I am supplying a 5.15V to the raspberry pi through a 12V lipo battery but it still not working . How much volt would you recommend for the robot car using raspberry pi 3 b + rplidar a1m8 + arduino (as motor controlller) . both arduino and rplidar are powered by through the raspberry pi .


potential concurrency problems in bot.builder

From code review, looks like:

TurnContextStateCollection
BotState.CachedBotState

should both be using ConcurrentDictionary and not Dictionary
(Note Dictionary is thread safe for read but not write.)

Hmmm... under what scenario should TurnContextStateCollection have to be worried about being accessed by multiple threads? It's 1:1 with a TurnContext which is, by definition, specific to a single turn.
If downstream logic actually executes code in parallel that logic needs to worry about serializing access to the collection. Just making everything use a ConcurrentDictionary<,> to be defensive comes at a cost as ConcurrentDictionary<,> obviously has additional overhead to help guarantee thread safety.
Don't make everyone pay the tax for a few; let those few who may introduce concurrency into their code deal with serializing access back to the TurnContext themselves.
Finally, as prior art, look at the design of ASP.NET's HttpContext. Its child collections (e.g. Items) are not thread safe because they've taken this same stance.

@drub0y yes that is what @cleemullins said when he saw this yesterday. We'll fix the BotState code (note the cache is a singleton) and leave it to the developer to worry about the TurnContext.

checked in

Instances of CachedBotState are created on every turn as well, so I still don't understand why that needed to be changed to use ConcurrentDictionary<,>.

OK, I guess that would make sense. It seems all a little sketchy having this hidden cache there, especially one that isn't thread safe. I'm not sure I wouldn't be surprised by some of the behavior of the state.
Anyhow, one of the agendas of moving business logic out of direct inline implementation in OnTurn is so that business logic becomes a step more decouped from state.

We're going to leave this for now.


value is "" can not copy to mysql

What happens?
If my field's value is \ , it can not be imported to mysql with COPY command.
Because the import sql is
INSERT table value ('\')

The sql will report syntax error.
To Reproduce

create a table in duckdb, insert a row with field's value is \
create the new table in mysql, use

create table table_name as from db.table

OS:
linux & mac
DuckDB Version:
0.10.1
DuckDB Client:
cli
Full Name:
Xiaojun Huang
Affiliation:
MHP
Have you tried this on the latest nightly build?
I have not tested with any build
Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?

[X] Yes, I have

@ywyt738 thanks! I transferred the issue to the duckdb_mysql repository. We'll take a look.

Past week I suffered from a data integrity issue where strings like 12345\0123 had the \0 replaced by the null character and strings like R\L lost the backslash while copying data from a CSV to MySQL through DuckDB. I have only noticed it because of a trailing backslash in one of these input strings, which broke the process the same way described in this issue.


delete unused Containerfile

Summary

delete unused package.Containerfile
found when working on MTSRE-1308

Check List Before Merging

[ ] This PR passes all pre-commit hook validations.
[ ] This PR is fully tested and regression tests are included.
[ ] Relevant documentation has been updated.

/ok-to-test

/retest


OIO Terms API Endpoint is Broken

Describe the bug
OLS doesn't return terms for OIO ontology
To Reproduce
https://www.ebi.ac.uk/ols4/api/ontologies/oio/terms will return 500
Expected behaviour
It should return terms of OIO ontology

fixed in production


Should We Archive the Repository?

Hey team, we have https://github.com/crossplane-contrib/provider-upjet-digitalocean available right now.
The Upjet-based provider supports all resources except the project_resources (we're working on it), so it would close most, if not all, issues and PRs over here.
Would it be prudent to archive this provider and incentivize the community to move to provider-upset-digitalocean?

This sounds like a good idea; thank you for taking the first big step in enabling crossplane users to use DigitalOcean resources reliably!
I'll make a PR shortly indicating in the README that there's a new version of the provider that will continue to be maintained with a link, and then archive.

I am confident enough that the package works, but since you have access to DO resources, it would be helpful for you to perform a one-time integration test of the resources.
Also, I do need help with some issues, primarily related to documentation clarifications, example, https://github.com/crossplane-contrib/provider-upjet-digitalocean/issues/38 I am not sure if those tags are the actual value of the tag, or if they could be a id to the DO Tags resource

ping @jbw976


Annotations Failing (e.g. FGFR3)

We noticed last Friday that some annotations for Genome Nexus are failing (see. e.g. FGFR3):
https://app.circleci.com/pipelines/github/genome-nexus/genome-nexus-annotation-pipeline/487/workflows/f1841313-0bac-47ee-ad37-a17c3cc9691e/jobs/699
Wondering if this is due to changes on the server side or in the annotation-pipeline client

It seems like a server side issue, we had this issue since 28days ago https://app.circleci.com/pipelines/github/genome-nexus/genome-nexus-annotation-pipeline/442/workflows/12f4e6ec-32ee-4fb2-9ca4-3836f16d4457/jobs/654
The issue seems related to https://github.com/genome-nexus/genome-nexus/blob/ab72745fd0c15eeb3cccdb303978003f9c62fd9f/service/src/main/java/org/cbioportal/genome_nexus/service/internal/VerifiedGenomicLocationAnnotationServiceImpl.java#L153

igv screenshot:

our test file:
https://media.githubusercontent.com/media/cBioPortal/datahub/master/public/msk_impact_2017/data_mutations_extended.txt
FGFR3			37	4	1806090	1806090			In_Frame_Ins	DEL	A	A	CACT			P-0000056-T01-IM3																	816	370

Original file:
https://github.com/cBioPortal/datahub/blob/master/public/msk_impact_2017/data_mutations_extended.txt
FGFR3                   GRCh37  4       1806090 1806090 +       protein_altering_variant        In_Frame_Ins    INS     G       A       CACT                    P-0000056-T01-IM3
                                                816     370                     ENST00000260795.2:c.1109delinsCACT      p.Gly370delinsAlaLeu    p.G370delinsAL  ENST00000260795         370     gGc/gCACTc      0

In original file Aug 15, 2018:
https://github.com/cBioPortal/datahub/commit/86b834a76d6cecd1f29f65dcb197e4e4e5b4c9bf#diff-726ef2959f70ddf23692199de5fd3c87c2c30c4819443526d85e984ac9db3448
FGFR3			37	4	1806090	1806090			In_Frame_Ins	DEL	A	A	CACT			P-0000056-T01-IM3

Let's maybe summarize the current behavior another time. Just so we are all on the same page
The original source file in datahub has the following annotation:
https://github.com/cBioPortal/datahub/blob/master/public/msk_impact_2017/data_mutations_extended.txt
FGFR3                   GRCh37  4       1806090 1806090 +       protein_altering_variant        In_Frame_Ins    INS     G       A       CACT                    P-0000056-T01-IM3
                                                816     370                     ENST00000260795.2:c.1109delinsCACT      p.Gly370delinsAlaLeu    p.G370delinsAL  ENST00000260795         370     gGc/gCACTc      0

In CVR it shows up as a frameshift insertion:

In our latest updates for genome nexus it will only show the missense mutation with the given input file since tumor seq allele 1 differs from the ref seq allele

Let's change Tumor_Seq_Allele1 to G as well like the Reference_Allele


Characters need to intersect with the bbox more than some threshold

There are a lot of redactions that look like this:

In this case, the redaction is just barely covering up the line above and so the line above is showing up as redacted. Alas, just checking for an intersection isn't enough. We need to have some threshold above which an intersection is relevant. Too bad.

Here's the example doc.
gov.uscourts.cacd.666997.143.2_2.pdf


Extract admin ui picard from Opencast #2

Some the original PR #98 broke, probably during the numerous merge conflict resolves. Since this PR removes and moves a lot of files, this may happen again in the future. Definitely check if this still builds before merging. I redid this PR to start over clean.
Deletes all Opencast files, leaving only the Create React App Project with the new Admin UI.
Goes together with https://github.com/opencast/opencast/pull/4695.

Have built it locally and tested the mock view a bit.
So far everything seems to be working as expected.

Have built it locally and tested the mock view a bit. So far everything seems to be working as expected.

Could you also test the normal view with local and external Opencast (e.g. develop.opencast.org) while you're at it?


Team Meeting - 202Y-11-20: Pre-PoC Check-in

Date and Time
202Y-11-20
Attendance

[x] Ansel Chen
[x] Muhammad Jawad
[x] Mohamad-Hassan Bahsoun
[x] Matthew Baleanu
[x] Ahmed Al-Hayali

Agenda
Implementation Check-in

Check progress on tempo extraction algorithm testing.
Check progress on Spotify song snippet extraction.

Looking ahead to PoC

What will we present.
Anticipated questions.

Notes
Implementation Check-in

@bahsounm tested with a few soundtracks (insert names & results).
@AhmedAl-Hayali tested with a few BALTHVS tracks, Harvest album:

OurAlgoTempo
SpotifyTempo

Sun Colored Eyes
5167.968750
91.566

Asha
5167.968750
86.406

Anouk
5167.968750
149.347

Like Coconut Water
397.536058
96.949

Lovin'
5167.968750
142.667

Aguacero
5167.968750
98.371

Mango Season
5167.968750
87.014

Sun & Moon
5167.968750
105.805

Venus Flytrap
5167.968750
108.558

Aio
5167.968750
110.685

Sun Colored Eyes, Pt. 1
5167.968750
91.576

Sun Colored Eyes, Pt. 2
5167.968750
91.584

Like Coconut Water - Instrumental
397.536058
97.111

Aguacero - Instrumental
5167.968750
98.638

Lovin' - Instrumental (Extended)
5167.968750
142.265

Aio - Instrumental
5167.968750
110.604

@AhmedAl-Hayali got Spotify API to work (authentication, fetching track information for tracks in a playlist, fetching track .mp3s from Spotify's CDN, converting to .wav locally).
@chenans1 got spotify API to work (authentication, fetching track information given its name, fetching track features from Spotify).

Looking ahead to PoC

Get the @baleanum (algorithm) @AhmedAl-Hayali (track fetching) @chenans1 (feature fetching) pipeline working & integrated ahead of the PoC.
Run some tests on the fully working pipeline above. Keep them for traceability and/or reporting. Both positive and negative/failing test cases.

@bahsounm please include information under "Notes" > "Implementation Check-in" where you are mentioned.

@AhmedAl-Hayali outstanding tasks:

Create issues to capture effort in the implementation, namely break #258 down into 3 components: algo implementation, track + feature fetching, and integration of the 2 aforementioned.
Create issue to capture testing of the PoC.

@AhmedAl-Hayali outstanding tasks:

Create issues to capture effort in the implementation, namely break feat[PoC-algo]: implement chosen song/audio feature extraction algorithm #258 down into 3 components: algo implementation, track + feature fetching, and integration of the 2 aforementioned.
Create issue to capture testing of the PoC.

Effort captured in:

#266
#267
#268


refactor: replace some filter()[0] usages to avoid unneeded iterations

This probably won't affect performance in the common case.
This removes just some unnecessary array method calls.

rebased this onto current master

Thanks @makepanic !


Angular integration - need a hook to call javascript before any action

I'd like to implement with Selenide features that are provided by Protractor for testing Angular apps.
Protractor runs a piece of javascript in the browser to tell whether Angular is done with its logic.
That ensures you the tests won't interact with the browser while an AJAX request is running, or when the change detection cycle is running.
That is easy to do (in this case for Angular2, logic is similar for Angular 1), with something like
public void waitForAngular() {
    getWebDriver().manage().timeouts().setScriptTimeout(5, TimeUnit.SECONDS);
    ((JavascriptExecutor) getWebDriver()).executeAsyncScript(waitForAngularScript);
}

And the content of waitForAngularScript being:
var callback = arguments[arguments.length - 1];
if(!window.hasOwnProperty('getAllAngularTestabilities')){
    callback(true);
}
else{
    window.getAllAngularTestabilities()[0].whenStable(function() {
        callback(true);
    });
}

Now, what I would like is to be able to have my waitForAngular method called before any interaction with the browser. Is there any chance to have such a feature ? It would be great if I could register a hook to be called before each interaction with the browser.

In order to solve your problem, have a look to: http://toolsqa.com/selenium-webdriver/event-listener/

@rcomblen You can use the following method:
  WebDriverListener.addListener(new AbstractWebDriverEventListener() {
    @Override
    public void beforeClickOn(WebElement element, WebDriver driver) {
        waitForAngular();
    }
  });

Thanks. There is a typo in your code snippet, I guess you meant:
WebDriverRunner.addListener(new AbstractWebDriverEventListener() {
    @Override
    public void beforeClickOn(WebElement element, WebDriver driver) {
        waitForAngular();
    }
});

@rcomblen Yes, I had a typo. Thank you.


workspace.onDidOpenTextDocument gives stale, incorrectly located files

Version: 1.46.1 (user setup)
Commit: cd9ea6488829f560dc949a8b2fb789f3cdc05f5d
Date: 2020-06-17T21:13:20.174Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363
Steps to Reproduce:
I have a file package.spiproj which looks like this:
dirOut: qwe
dirSource: c:\qwe
version: 1.2.3 (alpha)
name: Test
files:
    A
    Submodule/
        QQ
        QQ
        WWWW
        E
        Main
    Main

However the document in the onDidOpenTextDocument event is stale and shows up like this in the information window.
dirOut: qwe
dirSource: c:\qwe
version: 1.2.3 (alpha)
name: Test
files:
    A
    Submodule/
        QQ
        Q
        W
        E
        Main
    Main

To make matters worse, its file name (in the event) is package.spiproj.git rather than package.spiproj which indicates that it is fetching it from cache somewhere. This is certainly the case as I do not have package.spiproj.git anywhere on my hard drive.
Right now I am doing a VS Code extension for the configuration files for my language and the way workspace.onDidOpenTextDocument behaves is both broken and useless for me. Even if I close the file and open it again, that event will still give me incorrect data. Also, I tried this using the Insiders build and am getting the same problem.

Documents are addressed by URI which means you they have scheme, authority, path, query, and fragment (just like a web address). Do not assume that all document use the file scheme, there are many other schemes used and you must always check schemes

Even if I check the scheme (which is git:/ in this case,) the problem is that it is fetching the stale version of the file from version control. If you look at the documentation for this function it states that...
/**
 * An event that is emitted when a [text document](#TextDocument) is opened or when the language id
 * of a text document [has been changed](#languages.setTextDocumentLanguage).
 *
 * To add an event listener when a visible text document is opened, use the [TextEditor](#TextEditor) events in the
 * [window](#window) namespace. Note that:
 *
 * - The event is emitted before the [document](#TextDocument) is updated in the
 * [active text editor](#window.activeTextEditor)
 * - When a [text document](#TextDocument) is already open (e.g.: open in another [visible text editor](#window.visibleTextEditors)) this event is not emitted
 *
 */
export const onDidOpenTextDocument: Event<TextDocument>;

More specifically it says that The event is emitted before the document is updated in the active text editor. Am I supposed to parse the uri to extract the actual file system path of the document and load the file separately? That seems very unlikely. There should be some function or event to get the text of the actual document being opened directly.
It is not good to me if the text of the document in that event is from a commit a few hours ago instead of the thing that will show up in the editor. So far I've managed to get along by using the onDidChangeTextDocument event which works as one would expect, but in order to synchronize the editor with the language server I do need to differentiate changes from initialization.

Your assumption that git:///some/path/some/file.txt.git is the current file, as saved on disk or visible in the editor, is wrong. It's just a file, the git extension uses this as the baseline for diff computation but unless you truly understand what a scheme is used for you should simply ignore those documents

So you are saying that the Git extension is doing something under the hood to trigger that event? And that this event has nothing to do with the document actually being opened in the editor, is that right?
I see. Now that I am trying out opening various files after the plugin has activated, I see that the open event gets triggered twice for every file - once for the actual file open, and once by the git extension. The reason why the first one does not get triggered for the currently active file when the editor opens is probably because the extension I am working on is not active at that point. So instead of waiting for the event, I should probably look at the currently open files during activation of the extension...
Thank you. I see what I need to do now.

And that this event has nothing to do with the document actually being opened in the editor, is that right?

Yeah. There is visibleEditors to know what documents are showing in what editor


Fix/1.3.1 hotfix

Apply fixes from master to 1.3.0 branch in preparation for 1.3.1 release

Codecov Report

Merging #71 into release/1.3.0 will decrease coverage by 0.36%.
The diff coverage is 45.45%.

@@                Coverage Diff                @@
##           release/1.3.0      #71      +/-   ##
=================================================
- Coverage          88.21%   87.85%   -0.37%
=================================================
  Files                 26       26
  Lines               1307     1317      +10
=================================================
+ Hits                1153     1157       +4
- Misses               154      160       +6

Impacted Files
Coverage Δ

RPerformanceTracking/Private/_RPTTrackingManager.m
89.79% <ø> (-5.45%)
:arrow_down:

RPerformanceTracking/Private/_RPTSender.m
74.59% <45.45%> (-2.2%)
:arrow_down:

...ng/Private/_RPTClassManipulator+UIViewController.m
98.36% <0%> (-1.64%)
:arrow_down:

...eTracking/Private/_RPTClassManipulator+WKWebView.m
76.02% <0%> (+1.16%)
:arrow_up:

RPerformanceTracking/Private/_RPTConfiguration.m
95.23% <0%> (+1.19%)
:arrow_up:

RPerformanceTracking/Private/_RPTEventWriter.m
88.88% <0%> (+1.38%)
:arrow_up:

RPerformanceTracking/Private/_RPTLocation.m
100% <0%> (+2.04%)
:arrow_up:

...ceTracking/Private/UIDevice+RPerformanceTracking.m
100% <0%> (+12.5%)
:arrow_up:

Continue to review full report at Codecov.

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


Prevent abstract AggregateRoot<,> implementations from being registered as services

…ed as services

missing check for abstract registrations added
AggregateExtensionsTests added to check behavior
assembly helper added to EventFlow.Tests

QUESTIONS

should the test  for abstracts not be moved to AutofacServiceRegistration.ValidateRegistrations()

@JC008 As soon as the build is fixed, I'll merge it. Remember to add the fix for the release notes.

Help!


CI: Update docker image

What does this PR do?

Part of https://github.com/Lightning-AI/lightning/pull/13831.
Updates PyTorch version from 1.8 to 1.9 as we don't build 1.8 images in the PL repo anymore. (Let's see if the CI allows it...)

Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[n/a] Did you make sure to update the documentation with your changes?
[n/a] Did you write any new necessary tests? [not needed for typos/docs]
[n/a] Did you verify new and existing tests pass locally with your changes?
[n/a] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

[x] Is this pull request ready for review? (if not, please submit in draft mode)

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

Please don't worry about the failures, the CI is failing, and I'm working on it: #1410. :)

A couple of examples failures, namely:  Lightning-AI.lightning-flash (Examples) (domain text with GPUs 0) and  Lightning-AI.lightning-flash (Examples) (domain video with GPUs 0,1) are flaky. The text example is failing with some connection error to HuggingFace.co and the video example is failing with CUDA Runtime Error, I'll be re-running these tests to ensure they pass, and then we can merge this. (Other failures are being fixed, should be good very soon)

@krshrimali Thank you, Kush, for having a look at this! I'll re-re-run these three failing jobs and see if they pass this time :)
Lightning-AI.lightning-flash (Examples) Required
Lightning-AI.lightning-flash (Examples) (domain video with GPUs 0,1)
Lightning-AI.lightning-flash (Special)


Fix several compile-time warning messages to make build output more useful

The following changes were made:
Parenthesis were placed around some logical operators to remove warnings about implicit ordering.
Pragmas were placed to explicitly suppress warnings about non-literal format strings within ssprintf.
An incorrect format specifier was fixed within the WERROR macro.
An enum value that had been "added" to a string was changed to actually be appended.
This drastically reduces the number of warnings on my machine (100+ into ~15), and should generally make building information significantly more useful, as well as allowing important warnings to be seen.

It's a step in the right direction, but in Windows GHA x99999:   D:\a\etterna\etterna\main\src\RageUtil/Utils/RageUtil.h(550,9): warning C4068: unknown pragma (compiling source file D:\a\etterna\etterna\main\src\RageUtil\Graphics\RageTextureRenderTarget.cpp) [D:\a\etterna\etterna\main\build\Etterna.vcxproj]

That should be fixed now.


Fix call to reproject_interp

shape_out has its own kwarg.

Coverage remained the same at 72.695% when pulling 4e91090dfcd35f12c028eaaf0ee376ffea0dbe14 on e-koch:fix_reproject_input into 2c6575f17ac8f027f3dd53b0f6f80108b13bcbe6 on radio-astro-tools:master.

@e-koch any tests you want to add?  This function is not tested at all now.

@keflavich It couldn't handle the cube reprojection I need to do right now (way too big), so I haven't actually used it yet. I'll add an issue to remind me later.

@e-koch OK.  If you're having trouble with really large cubes, it might be worth trying to re-make the iterator with a write-to-disk at each step.  I've recently had to do this for some files, and I ended up using astropy.io.fits directly instead of spectral-cube.  It would be better if we could make SC work with this.
The approach we'll need to take is to open the file with mode='update' (which I hope can work on arbitrarily large files....) and then edit each frame in turn.  It may require specifying both an input & an output file on disk, which is somewhat contrary to the general approach of spectral-cube, but is necessary for this sort of operation.   Now that I think of it, having a general mechanism for streaming from one file to another seems like a killer app for SC.

Agreed. That's basically what I've been having to do with large manipulations on big cubes. I'm up for adding this in, but it'll be a few weeks before I can get to it.


$ isn't searching in all columns

I want to make a global filter, I mean, an input where the user can search by all fields, but using $ isn't working:
This is the ng-change binded function:
        function tableFilter( stringToSearch ) {
            vm.table_data.filter( { $: stringToSearch } );
        }

If I specify a column like name instead of $ it works... Also I don't understand why at the examples you use dataset and it works, but when I tried with it, it didn't work, then I changed it to data and it works, I'm talking about the second json of NgTableParams.

You can try - vm.table_data.filter()['$'] = stringToSearch;
I belive this is the setup that works for me

If AmitMY's method didn't work, try vm.data_table.reload() after.
That worked for me


TooltipIcon text overflowing

Detailed description

Describe in detail the issue you're having.
The tooltip width is not wide enough

Is this a feature request (new component, new icon), a bug, or a general issue?
bug

Is this issue related to a specific component?
TooltipIcon and Tooltip

What did you expect to happen? What happened instead? What would you like to see changed?
Tooltip width same as text length

What browser are you working in?
Chrome/FF/ Safari
Tooltip only happens in Safari, TooltipIcon happens in all browsers

What version of the Carbon Design System are you using?
"carbon-addons-cloud": "2.1.0",
"carbon-addons-cloud-react": "1.2.0",
"carbon-components": "9.1.20",
"carbon-components-react": "6.12.2",

What offering/product do you work on? Any pressing ship or release dates we should be aware of?

IBM Cloud
Steps to reproduce the issue

Step one
Step two
Step three
etc.

Additional information

Screenshots or code
Notes

TooltipIcon:
Notice there is more text after '... within'

Tooltip: (safari)

Hi tooltip icon is only used to clarify the action or name of an interactive icon button. Please consider using an interactive tooltip.

@aledavila I was told tooltip icon is to replace tooltip simple, I'll switch it back, thanks...

I removed TooltipIcon from the issue, can someone take a look at Tooltip?

Hi @nicoxxie is it possible to create a code sandbox example showing your issue?

@alisonjoseph I found that we had extra css on top of the .bx--tooltip
  width: max-content;
  white-space: nowrap;

and these broke only in safari.  Closing it since I don't think it's the component iself.  thanks!


UTable: Expand Slot causes EmptyState width issue

Environment

Operating System: Linux
Node Version:     v18.20.3
Nuxt Version:     3.12.4
CLI Version:      3.12.0
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, modules, compatibilityDate
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Version
v2.18.4
Reproduction
https://stackblitz.com/edit/github-kntdwe?file=app.vue
Description
Initialize any UTable, make sure it is empty. Add an expand slot. The Empty State slot will now not span the full width of the table.
Remove the expand slot, and the Empty State is the full width of the table again.
Additional context

Logs
No response

This issue might be related to CSS or layout handling when expand slots are present. Review the CSS styles or layout calculations applied to the UTable component when expand slots are included. Ensure that the styles for the Empty State are applied correctly and consider adding a CSS rule to ensure it spans the full width regardless of other slots.

I'm seeing this, too. When the expand slot is used, an extra <th> is added to the header, but the corresponding colspan for the loading and empty states is not increased by 1 as it is when modelValue is present. The result is that the colspan is one fewer than it should be to completely fill the table.


Develop Nagios plugin

As I've made vague reference to at least once, I plan to include a Nagios plugin in this project. Much of the work for the cmd/hayoh application should be reflected in this new tool, though the overall design of a Nagios plugin will be expected.
As a template, the work I did for the atc0005/check-cert project (specifically the check_cert plugin) can be used.

My plan was to work on this next, potentially this week or the next. I've since had someone show interest in developing this plugin (or contributing efforts towards it), so I will see where things go. It may be that a synergy of sorts occurs and the results of both efforts are combined into final result. If/when I start work on this I'll post back and reference the branch I'm working on in case it is helpful.

Hi Adam, i've gone the references above. But i'm still not clear as to what we want to achieve here.
Please further explain. Thanks.

Nagios is a monitoring system that calls out to "plugins" to perform actions. Plugins are either command-line applications or shell scripts that take zero or more arguments and return an error code and optionally a text string and performance data.
Nagios (what I refer to as the "console") takes those results and makes a determination regarding the state of the host or service it is monitoring.
I am simplifying, but each plugin is in charge of performing the action and returning a specific error code indicating OK, WARNING, CRITICAL, UNNOWN or a 5th state, which I forget.
The plugins that I linked to are for checking and IMAP account and a certificate, respectively. The IMAP check is the first I wrote and uses a different approach to returning the success/failure state than the cert check plugin, which uses an approach that I think I want to polish a bit and use for plugins going forward. I think. Once I get into implementing the code for this latest plugin I would probably have a good feel for things.


QuotaExceededError in Safari incognito mode

When using safari in incognito mode, navigation fails with the following exception:
QuotaExceededError: DOM Exception 22: An attempt was made to add something to storage that exceeded the quota.

Safari denies usage of local/session storages when in incognito mode, and raises this error when you try to.
I am using the BrowserHistory history and it seems like the error stems from history/DOMStateStorage.

Thanks for reporting this bug, @AndreasHogstrom :)
The solution is probably two-fold:

We should catch the QuotaExceededError and emit a warning instead
We should make sure we are only ever calling saveState when we actually need to (i.e. when there is some state to save, e.g. a call to pushState(null, '/path') shouldn't actually try to saveState)

I think that would give developers the flexibility they need to either a) use state and ignore the warnings for users in incognito mode (or possibly try to detect when someone is in incognito mode and do the right thing) or 2) avoid using state entirely, thereby avoiding the warnings.
Would you care to make a PR @AndreasHogstrom?

@mjackson I ran into this today, does a simple in memory storage that polyfill the localStorage can make the trick?
I can drop you a PR with warning emitting for now.

You can use this pollyfill to use the localStorage in memory:
(function () {
  function isSupported() {
    var item = 'localStoragePollyfill';
    try {
      localStorage.setItem(item, item);
      localStorage.removeItem(item);
      return true;
    } catch (e) {
      return false;
    }
  }

  if (!isSupported()) {
    try {
      Storage.prototype._data = {};

      Storage.prototype.setItem = function (id, val) {
        return this._data[id] = String(val);
      };

      Storage.prototype.getItem = function (id) {
        return this._data.hasOwnProperty(id) ? this._data[id] : undefined;
      },

      Storage.prototype.removeItem = function (id) {
        return delete this._data[id];
      },

      Storage.prototype.clear = function () {
        return this._data = {};
      }
    } catch (e) {
      console.error('localStorage pollyfill error: ', e);
    }
  }
}());

Yeah ! Finally I get the solution here~


Decide how destructuring and capturing should work

The F# implementation currently doesn't do anything much in this area (the tests are explicitly ignored right now). The C# implementation is based on serilog and does whatever Serilog did.
This comment from @nblumhardt is interesting:

For most property types, e.g. Name above, representing them as a simple scalar "nblumhardt", 42, or array-of-scalars, is fine and doesn't require any special types. It's less clear what an @-destructured value should be Capture()d as. Serilog has StructureValue and friends to snapshot object state in a way that makes concurrent access safe (and caches the reflection/allocation done in that process).

For my purposes, this seems quite important. If some library (eg. suave) needs to log the property values associated with a structured message template, it needs to be able capture them into a reasonable structured format.
What's interesting in F# land is that many core types (such as records and lists) are immutable by default, but records (for example) can be made mutable by either having mutable fields or using the CLIMutable attribute. I think this means the F# context is no different to serilog. Anything that needs to be logged/captured by MessageTemplates is potentially mutable, and many bad things would happen if the values are changed by another thread.
I wonder if there should be a way to avoid the copy of the objects if the template owner knows they're immutable? I wonder how ugly it would get when they make a mistake?

No insights to add, but just for the sake of a second opinion I'd favour the safer and simpler option. Seems like an optimisation could be added down the track in a potentially non-breaking way if needed. So far hasn't been requested of Serilog. YMMV ;-)

I think I'm happy with doing things the way Serilog does, and I think I'm not too far away from doing the same in the F# version over in #14, so I'm closing this :)


Disable option to Start Review when no comment text

Extension version: 1.79.0
VSCode Version: 1.33.0
OS: macOS

Steps to Reproduce:

Go to leave a comment on a line
Observe that the comment box has the Start Review option enabled by default.

Solution:
This option should be disabled until some text is actually entered in the comment box.
Discovered when testing for: https://github.com/Microsoft/vscode/issues/71103

Side note: This also seems to confuse things on GitHub.com where it shows a review has been started but there are 0 pending comments.

I think fixing this might involve tweaking the API. Right now, buttons are added to comments by specifying an acceptInputCommand and an optional list of additionalAcceptInputCommands. Based on the names of those properties, it would make sense that they always be disabled when there is no input. The acceptInputCommand for us is always "Add Comment", the "Start Review", "Finish Review", and "Delete Review" buttons are all from additionalAcceptInputCommands. The "Finish Review" and "Delete Review" buttons we add can be run without input - running "Delete Review" with input would be very weird, but this button is also a bit odd in its current placement.
We could

disable all additionalAcceptInputCommands buttons when there is no text, removing the delete review button from the list
change the additionalAcceptInputCommands property to have a flag indicating if it can be run when there is no input

@RMacfarlane thanks for the additional context here, I appreciate it.
Just to clarify the proposed solution - it will disable the buttons "Start Review, "Finish Review" and "Delete Review" but then add a flag to indicate if the command can be run? So only "Start Review" will have a flag that indicates input is required before running the command?

Yeah, that's right.
So instead of having the API be additionalAcceptInputCommands: Command[];, it would be
additionalAcceptInputCommands: [{
	command: Command;
	disableWhenEmpty: boolean;
}]

Right now we call them additionalCommands and their states are not determined by the textarea, which is designed this way. However if we call them *AcceptInputCommands, then they should behave the same as acceptInputCommand, which is disabled if the textarea is empty.

Side note: This also seems to confuse things on GitHub.com where it shows a review has been started but there are 0 pending comments

I'd love to start a review without creating comments first actually. Right now .com doesn't allow that but the api does.

Yeah that's a great point @rebornix. The API does allow it, but I had never noticed that until testing out the new comment provider and it seemed strange to me.
Are you suggesting we leave this implementation as-is?

It sounds like a good feature to me but if you think we'd better avoid that, we can throw an error or show a notification when users try to create a review without comments. This way we don't need to wait for any vscode side code change, which is already late at this point.

I'm okay with just showing some notification that says review comments must be added before starting a review.

This was fixed as part of adopting the new comments API (https://github.com/microsoft/vscode-pull-request-github/pull/1168)


Openssl cross compilation not working

I can't seem to figure out the problem:
error: failed to run custom build command for `openssl-sys v0.9.86`
[366](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:382)

[367](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:383)
Caused by:
[368](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:384)
  process didn't exit successfully: `/home/runner/work/oci-tester/oci-tester/target/release/build/openssl-sys-fb313cace2c4dd0e/build-script-main` (exit status: 101)
[369](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:385)
  --- stdout
[370](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:386)
  cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_MUSL_OPENSSL_LIB_DIR
[371](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:387)
  X86_64_UNKNOWN_LINUX_MUSL_OPENSSL_LIB_DIR unset
[372](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:388)
  cargo:rerun-if-env-changed=OPENSSL_LIB_DIR
[373](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:389)
  OPENSSL_LIB_DIR unset
[374](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:390)
  cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_MUSL_OPENSSL_INCLUDE_DIR
[375](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:391)
  X86_64_UNKNOWN_LINUX_MUSL_OPENSSL_INCLUDE_DIR unset
[376](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:392)
  cargo:rerun-if-env-changed=OPENSSL_INCLUDE_DIR
[377](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:393)
  OPENSSL_INCLUDE_DIR unset
[378](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:394)
  cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_MUSL_OPENSSL_DIR
[379](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:395)
  X86_64_UNKNOWN_LINUX_MUSL_OPENSSL_DIR unset
[380](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:396)
  cargo:rerun-if-env-changed=OPENSSL_DIR
[381](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:397)
  OPENSSL_DIR unset
[382](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:398)
  cargo:rerun-if-env-changed=OPENSSL_NO_PKG_CONFIG
[383](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:399)
  cargo:rerun-if-env-changed=PKG_CONFIG_ALLOW_CROSS_x86_64-unknown-linux-musl
[384](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:400)
  cargo:rerun-if-env-changed=PKG_CONFIG_ALLOW_CROSS_x86_64_unknown_linux_musl
[385](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:401)
  cargo:rerun-if-env-changed=TARGET_PKG_CONFIG_ALLOW_CROSS
[386](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:402)
  cargo:rerun-if-env-changed=PKG_CONFIG_ALLOW_CROSS
[387](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:403)
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-musl
[388](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:404)
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_musl
[389](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:405)
  cargo:rerun-if-env-changed=TARGET_PKG_CONFIG
[390](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:406)
  cargo:rerun-if-env-changed=PKG_CONFIG
[391](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:407)
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-musl
[392](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:408)
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_musl
[393](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:409)
  cargo:rerun-if-env-changed=TARGET_PKG_CONFIG_SYSROOT_DIR
[394](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:410)
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
[395](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:411)
  run pkg_config fail: pkg-config has not been configured to support cross-compilation.
[396](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:412)

[397](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:413)
  Install a sysroot for the target platform and configure it via
[398](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:414)
  PKG_CONFIG_SYSROOT_DIR and PKG_CONFIG_PATH, or install a
[399](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:415)
  cross-compiling wrapper for pkg-config and set it via
[400](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:416)
  PKG_CONFIG environment variable.
[401](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:417)

[402](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:418)
  --- stderr
[403](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:419)
  thread 'main' panicked at '
[404](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:420)

[405](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:421)
  Could not find directory of OpenSSL installation, and this `-sys` crate cannot
[406](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:422)
  proceed without this knowledge. If OpenSSL is installed and this crate had
[407](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:423)
  trouble finding it,  you can set the `OPENSSL_DIR` environment variable for the
[408](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:424)
  compilation process.
[409](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:425)

[410](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:426)
  Make sure you also have the development packages of openssl installed.
[411](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:427)
  For example, `libssl-dev` on Ubuntu or `openssl-devel` on Fedora.
[412](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:428)

[413](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:429)
  If you're in a situation where you think the directory *should* be found
[414](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:430)
  automatically, please open a bug at https://github.com/sfackler/rust-openssl
[415](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:431)
  and include information about your system as well as this message.
[416](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:432)

[417](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:433)
  $HOST = x86_64-unknown-linux-gnu
[418](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:434)
  $TARGET = x86_64-unknown-linux-musl
[419](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:435)
  openssl-sys = 0.9.86
[420](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:436)

[421](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:437)
  ', /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/openssl-sys-0.9.86/build/find_normal.rs:190:5
[422](https://github.com/lswith/oci-tester/actions/runs/4783838997/jobs/8504576386#step:4:438)
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

It seems like I need to set the PKG_CONFIG and the OPENSSL_DIR, but they are already there. Any ideas?

Have you tried put openssl package as vendored in you cargo? Generally it solves the problema
[target.x86_64-unknown-linux-musl.dependencies]
openssl = { version = "*", features = ["vendored"] }

I'll give that a go! Thanks


Do not separate core functions into their own package

Some of the core functions are separated into their own package without any reason. This causes problems related to go get getting confused and go itself doesn't know the location of the packages.

It should be on the same package which is main


python agent.py start 启动时 提示服务没有及时响应启动或控制请求

hi, can you check the environment variable?

I also get this error.

No description provided.

have you slove this problem?

Mostly this is caused by wrong env variable settings.

Mostly this is caused by wrong env variable settings.

I have installed all packages.which variable settings need to do.

通常，这是由错误的环境变量设置引起的。

我已经安装了所有软件包。需要进行变量设置。


Fix contradictory description of extension requirements for int in int+fp structs for the FP ABI

Pull request #74 clarified that when an int+fp struct is passed in a
GPR+FPR in the floating point ABI, the integer isn't extended to XLEN
(i.e. it is anyext, just as if it were passed on the stack).
Unfortunately, a previous part of the sentence which mandated
sign/zero-extension was left in. This patch removes the contradictory
information.

Thanks, Alex!


Problems with cluster creation

Hi team,
I'm moving this from here: https://github.com/MicrosoftDocs/azure-docs.es-es/issues/467
The contributor is reporting the instructions have errors.
@VaroJulio commented 5 days ago
When executing the poweshell script to create the cluster, the following error occurs:
WARNING: Access policy is not set. No user or application have access permission to use this vault. Please use Set
-AzKeyVaultAccessPolicy to set access policies.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 922b9c51-6a6d-1118-d2a2-6d485b222ce8
Version Independent ID: 6874cc89-a1f8-addd-430f-a4d6b7f89ae8
Content: Create a Windows container app on Service Fabric in Azure
Content Source: articles/service-fabric/service-fabric-quickstart-containers.md
Service: service-fabric
GitHub Login: @aljo-microsoft
Microsoft Alias: aljo

Thanks for the question. We are currently investigating and will update you shortly.

@VaroJulio Can you please check this stack overflow thread on the same issue and see if this unblocks you. Let me know the update.

@VaroJulio Is there any update? Did that help?

Yes. It works, thanks for your help!

@VaroJulio Thanks for the update. We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


Interface concentration discontinuities (fenicsx)

Proposed changes
A massive thank you to @jorgensd who was instrumental in getting this functionality in FESTIM 🥇
This PR is a first (big) step towards interface discontinuities in the fenicsx branch (#719).
(requires #764)
This new approach to conservation of chemical potential relies on the mixed domain approach implemented in dolfinx 0.8.0 and based off a demo available here
I created a new problem class HTransportProblemDiscontinuous - which is not yet complete - to avoid breaking existing functionality. We will complete this class by integrating transient, post-processing, ICs, etc. Eventually this whole class will be merged with HydrogenTransportProblem.
In the current interface, users need to provide correspondence between surfaces and volumes as well as listing interfaces and which volumes they are connected to:
list_of_interfaces = {5: [left_domain, right_domain]}
my_model.subdomains = [left_domain, right_domain, left_surface, right_surface]

I believe this can be streamlined by FESTIM under the hood but I'll keep that for a future PR.
Proposed user interface:
import festim as F

import dolfinx
import numpy as np
import festim as F

my_model = F.HTransportProblemDiscontinuous()

interface_1 = 0.2
interface_2 = 0.8

vertices = np.concatenate(
    [
        np.linspace(0, interface_1, num=100),
        np.linspace(interface_1, interface_2, num=100),
        np.linspace(interface_2, 1, num=100),
    ]
)

my_model.mesh = F.Mesh1D(vertices)

material_left = F.Material(D_0=2.0, E_D=0.1)
material_mid = F.Material(D_0=2.0, E_D=0.1)
material_right = F.Material(D_0=2.0, E_D=0.1)

material_left.K_S_0 = 2.0
material_left.E_K_S = 0
material_mid.K_S_0 = 4.0
material_mid.E_K_S = 0
material_right.K_S_0 = 6.0
material_right.E_K_S = 0

left_domain = F.VolumeSubdomain1D(3, borders=[0, interface_1], material=material_left)
middle_domain = F.VolumeSubdomain1D(4, borders=[interface_1, interface_2], material=material_mid)
right_domain = F.VolumeSubdomain1D(5, borders=[interface_2, 1], material=material_right)

left_surface = F.SurfaceSubdomain1D(id=1, x=vertices[0])
right_surface = F.SurfaceSubdomain1D(id=2, x=vertices[-1])

# the ids here are arbitrary in 1D, you can put anything as long as it's not the same as the surfaces
my_model.interfaces = {6: [left_domain, middle_domain], 7: [middle_domain, right_domain]}
my_model.subdomains = [left_domain, middle_domain, right_domain, left_surface, right_surface]
my_model.surface_to_volume = {right_surface: right_domain, left_surface: left_domain}

H = F.Species("H", mobile=True)
trapped_H = F.Species("H_trapped", mobile=False)
empty_trap = F.ImplicitSpecies(n=0.5, others=[trapped_H])

my_model.species = [H, trapped_H]

for species in [H, trapped_H]:
    species.subdomains = [left_domain, middle_domain, right_domain]

my_model.reactions = [
    F.Reaction(
        reactant=[H, empty_trap],
        product=[trapped_H],
        k_0=2,
        E_k=0,
        p_0=0.1,
        E_p=0,
        volume=domain,
    )
    for domain in [left_domain, middle_domain, right_domain]
]

my_model.boundary_conditions = [
    F.DirichletBC(left_surface, value=0.05, species=H),
    F.DirichletBC(right_surface, value=0.2, species=H),
]

my_model.temperature = lambda x: 300 + 100 * x[0]

my_model.settings = F.Settings(atol=None, rtol=None, transient=False)

my_model.initialise()
my_model.run()

for subdomain in my_model.volume_subdomains:
    u_sub_0 = subdomain.u.sub(0).collapse()
    u_sub_0.name = "u_sub_0"

    u_sub_1 = subdomain.u.sub(1).collapse()
    u_sub_1.name = "u_sub_1"
    bp = dolfinx.io.VTXWriter(
        my_model.mesh.mesh.comm, f"u_{subdomain.id}.bp", [u_sub_0, u_sub_1], engine="BP4"
    )
    bp.write(0)
    bp.close()

Types of changes
What types of changes does your code introduce to FESTIM?

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Code refactoring
[ ] Documentation Update (if none of the other choices apply)
[ ] New tests

Checklist

[x] Black formatted
[x] Unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

We have noticed crashed in 1D simulations with coarse meshes. This is a fix for it (needs testing and review) and the working example is here (works with this PR).

We had a discussion with @jorgensd @jhdark and @JonathanGSDUFOUR and noticed weird things happening with the performance so we need to investigate. Otherwise I'll carry on writing tests for this

Also, you should update the proposed user interface on the PR with the other classes that were introduced


Add favicons

Description
Added favicons to demo page
Fixes #143
Type of change

[ ] Bug fix (added a non-breaking change which fixes an issue)
[x] New feature (added a non-breaking change which adds functionality)
[ ] Updated documentation (updated the readme, templates, or other repo files)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?
Tested on Safari 15.0, Edge 94.0.992.38, Firefox 92.0.1.

[x] Tested locally with a valid username
[ ] Tested locally with an invalid username
[ ] Ran tests with composer test
[ ] Added or updated test cases to test new features

Checklist:

[x] I have checked to make sure no other pull requests are open for this issue
[x] The code is properly formatted and is consistent with the existing code style
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Screenshots
Safari tab

Edge Tab

Safari Bookmark

Edge Bookmark

Thanks for contributing!


cannot run chatGLM3-1.5B on LNL iGPU

ChatGLM3-6B, GLM4-9B and llama3-8B can run on LNL iGPU.
But chatGLM3-1.5B fails to run on LNL iGPU.
The scripts exit on model.generate without error log.
The code we use is the sample code in ipex-llm.
Verion:
Intel Core Ultra 9 288V  32GB 7467MHz， Intel Arc Graphic 140V (8 Xe-Core);
Windows 11 24H2，ipex 2.1.20, ipex-llm 2.1.0b20240717
Can you help to support chatGLM3-1.5B on LNL iGPU？  Thanks.

Fixed, you can update your ipex-llm to 2.1.0b20240723 and try again.

Fixed. Thanks for your help.


[REQUEST] X crosshair

As the title say

What is it?

What is it?

change + crosshair to X crosshair like this
https://www.nicepng.com/png/detail/28-281738_losing-track-of-your-aiming-reticle-enel-x.png

isnt that hitmark ?

isnt that hitmark ?

yep but always on not hitmark

i have the possibly dumbest way to make it lol
make logaritmic slider for hitmarker disappear time
make float 0 to 382173127sec for if u wanna use as hitmarker use in 0.2sec if u wanna use as crosshair make it 83247234sec
hit someone in game make ur crosshair alpha 0
here is ur x crosshair :P

https://github.com/danielkrupinski/Osiris/pull/2275

@dayz2000 @danielkrupinski https://github.com/danielkrupinski/Osiris/pull/2275


Install on High Sierra, Python 3.6, no Conda

Problem Description
I am trying to install Spyder on a Mac to control a remote Kernel (machine with nvidia GPU for deep learning).
I don't have Conda, at least I tried to remove it. conda on the terminal returns nothing.
Also, the documentation says I would have found a dmg file in github releases, but I only found the source files and I couldn't find how to build it.
What steps will reproduce the problem?

ran pip install -U spyder a few times
I get:

Requirement already up-to-date: spyder in /Library/Python/2.7/site-packages (3.2.8)
Requirement not upgraded as not directly required: pyflakes in /Library/Python/2.7/site-packages (from spyder) (1.6.0)
Requirement not upgraded as not directly required: cloudpickle in /Library/Python/2.7/site-packages (from spyder) (0.5.2)
Requirement not upgraded as not directly required: pickleshare in /Library/Python/2.7/site-packages (from spyder) (0.7.4)
Requirement not upgraded as not directly required: pygments>=2.0 in /Library/Python/2.7/site-packages (from spyder) (2.2.0)
Requirement not upgraded as not directly required: qtawesome>=0.4.1 in /Library/Python/2.7/site-packages (from spyder) (0.4.4)
Requirement not upgraded as not directly required: chardet>=2.0.0 in /Library/Python/2.7/site-packages (from spyder) (3.0.4)
Requirement not upgraded as not directly required: rope>=0.10.5 in /Library/Python/2.7/site-packages (from spyder) (0.10.7)
Requirement not upgraded as not directly required: numpydoc in /Library/Python/2.7/site-packages (from spyder) (0.8.0)
Requirement not upgraded as not directly required: pycodestyle in /Library/Python/2.7/site-packages (from spyder) (2.4.0)
Requirement not upgraded as not directly required: nbconvert in /Library/Python/2.7/site-packages (from spyder) (5.3.1)
Requirement not upgraded as not directly required: psutil in /Library/Python/2.7/site-packages (from spyder) (5.4.5)
Requirement not upgraded as not directly required: jedi>=0.9.0 in /Library/Python/2.7/site-packages (from spyder) (0.12.0)
Requirement not upgraded as not directly required: qtpy>=1.2.0 in /Library/Python/2.7/site-packages (from spyder) (1.4.1)
Requirement not upgraded as not directly required: qtconsole>=4.2.0 in /Library/Python/2.7/site-packages (from spyder) (4.3.1)
Requirement not upgraded as not directly required: pyzmq in /Library/Python/2.7/site-packages (from spyder) (17.0.0)
Requirement not upgraded as not directly required: sphinx in /Library/Python/2.7/site-packages (from spyder) (1.7.4)
Requirement not upgraded as not directly required: pylint in /Library/Python/2.7/site-packages (from spyder) (1.8.4)
Requirement not upgraded as not directly required: pathlib2; python_version in "2.6 2.7 3.2 3.3" in /Library/Python/2.7/site-packages (from pickleshare->spyder) (2.3.2)
Requirement not upgraded as not directly required: six in ./Library/Python/2.7/lib/python/site-packages (from qtawesome>=0.4.1->spyder) (1.11.0)
Requirement not upgraded as not directly required: Jinja2>=2.3 in /Library/Python/2.7/site-packages (from numpydoc->spyder) (2.10)
Requirement not upgraded as not directly required: traitlets>=4.2 in /Library/Python/2.7/site-packages (from nbconvert->spyder) (4.3.2)
Requirement not upgraded as not directly required: mistune>=0.7.4 in /Library/Python/2.7/site-packages (from nbconvert->spyder) (0.8.3)
Requirement not upgraded as not directly required: nbformat>=4.4 in /Library/Python/2.7/site-packages (from nbconvert->spyder) (4.4.0)
Requirement not upgraded as not directly required: bleach in /Library/Python/2.7/site-packages (from nbconvert->spyder) (2.1.3)
Requirement not upgraded as not directly required: jupyter-core in /Library/Python/2.7/site-packages (from nbconvert->spyder) (4.4.0)
Requirement not upgraded as not directly required: testpath in /Library/Python/2.7/site-packages (from nbconvert->spyder) (0.3.1)
Requirement not upgraded as not directly required: pandocfilters>=1.4.1 in /Library/Python/2.7/site-packages (from nbconvert->spyder) (1.4.2)
Requirement not upgraded as not directly required: entrypoints>=0.2.2 in /Library/Python/2.7/site-packages (from nbconvert->spyder) (0.2.3)
Requirement not upgraded as not directly required: parso>=0.2.0 in /Library/Python/2.7/site-packages (from jedi>=0.9.0->spyder) (0.2.0)
Requirement not upgraded as not directly required: ipython-genutils in /Library/Python/2.7/site-packages (from qtconsole>=4.2.0->spyder) (0.2.0)
Requirement not upgraded as not directly required: jupyter-client>=4.1 in /Library/Python/2.7/site-packages (from qtconsole>=4.2.0->spyder) (5.2.3)
Requirement not upgraded as not directly required: ipykernel>=4.1 in /Library/Python/2.7/site-packages (from qtconsole>=4.2.0->spyder) (4.8.2)
Requirement not upgraded as not directly required: imagesize in /Library/Python/2.7/site-packages (from sphinx->spyder) (1.0.0)
Requirement not upgraded as not directly required: sphinxcontrib-websupport in /Library/Python/2.7/site-packages (from sphinx->spyder) (1.0.1)
Requirement not upgraded as not directly required: alabaster<0.8,>=0.7 in /Library/Python/2.7/site-packages (from sphinx->spyder) (0.7.10)
Requirement not upgraded as not directly required: snowballstemmer>=1.1 in /Library/Python/2.7/site-packages (from sphinx->spyder) (1.2.1)
Requirement not upgraded as not directly required: docutils>=0.11 in ./Library/Python/2.7/lib/python/site-packages (from sphinx->spyder) (0.14)
Requirement not upgraded as not directly required: typing; python_version < "3.5" in /Library/Python/2.7/site-packages (from sphinx->spyder) (3.6.4)
Requirement not upgraded as not directly required: babel!=2.0,>=1.3 in /Library/Python/2.7/site-packages (from sphinx->spyder) (2.5.3)
Requirement not upgraded as not directly required: requests>=2.0.0 in /Library/Python/2.7/site-packages (from sphinx->spyder) (2.9.1)
Requirement not upgraded as not directly required: setuptools in /Library/Python/2.7/site-packages (from sphinx->spyder) (39.1.0)
Requirement not upgraded as not directly required: packaging in /Library/Python/2.7/site-packages (from sphinx->spyder) (17.1)
Requirement not upgraded as not directly required: isort>=4.2.5 in /Library/Python/2.7/site-packages (from pylint->spyder) (4.3.4)
Requirement not upgraded as not directly required: astroid<2.0,>=1.6 in /Library/Python/2.7/site-packages (from pylint->spyder) (1.6.3)
Requirement not upgraded as not directly required: singledispatch; python_version < "3.4" in /Library/Python/2.7/site-packages (from pylint->spyder) (<IP_ADDRESS>)
Requirement not upgraded as not directly required: mccabe in /Library/Python/2.7/site-packages (from pylint->spyder) (0.6.1)
Requirement not upgraded as not directly required: configparser; python_version == "2.7" in /Library/Python/2.7/site-packages (from pylint->spyder) (3.5.0)
Requirement not upgraded as not directly required: backports.functools-lru-cache; python_version == "2.7" in /Library/Python/2.7/site-packages (from pylint->spyder) (1.5)
Requirement not upgraded as not directly required: scandir; python_version < "3.5" in /Library/Python/2.7/site-packages (from pathlib2; python_version in "2.6 2.7 3.2 3.3"->pickleshare->spyder) (1.7)
Requirement not upgraded as not directly required: MarkupSafe>=0.23 in /Library/Python/2.7/site-packages (from Jinja2>=2.3->numpydoc->spyder) (1.0)
Requirement not upgraded as not directly required: decorator in /Library/Python/2.7/site-packages (from traitlets>=4.2->nbconvert->spyder) (4.3.0)
Requirement not upgraded as not directly required: enum34; python_version == "2.7" in /Library/Python/2.7/site-packages (from traitlets>=4.2->nbconvert->spyder) (1.1.6)
Requirement not upgraded as not directly required: jsonschema!=2.5.0,>=2.4 in /Library/Python/2.7/site-packages (from nbformat>=4.4->nbconvert->spyder) (2.6.0)
Requirement not upgraded as not directly required: html5lib!=1.0b1,!=1.0b2,!=1.0b3,!=1.0b4,!=1.0b5,!=1.0b6,!=1.0b7,!=1.0b8,>=0.99999999pre in /Library/Python/2.7/site-packages (from bleach->nbconvert->spyder) (1.0.1)
Requirement not upgraded as not directly required: tornado>=4.1 in /Library/Python/2.7/site-packages (from jupyter-client>=4.1->qtconsole>=4.2.0->spyder) (5.0.2)
Requirement not upgraded as not directly required: python-dateutil>=2.1 in ./Library/Python/2.7/lib/python/site-packages (from jupyter-client>=4.1->qtconsole>=4.2.0->spyder) (2.6.1)
Requirement not upgraded as not directly required: ipython>=4.0.0 in /Library/Python/2.7/site-packages (from ipykernel>=4.1->qtconsole>=4.2.0->spyder) (5.6.0)
Requirement not upgraded as not directly required: pytz>=0a in /Library/Python/2.7/site-packages (from babel!=2.0,>=1.3->sphinx->spyder) (2018.4)
Requirement not upgraded as not directly required: pyparsing>=2.0.2 in /Library/Python/2.7/site-packages (from packaging->sphinx->spyder) (2.2.0)
Requirement not upgraded as not directly required: futures in ./Library/Python/2.7/lib/python/site-packages (from isort>=4.2.5->pylint->spyder) (3.1.1)
Requirement not upgraded as not directly required: wrapt in /Library/Python/2.7/site-packages (from astroid<2.0,>=1.6->pylint->spyder) (1.10.11)
Requirement not upgraded as not directly required: lazy-object-proxy in /Library/Python/2.7/site-packages (from astroid<2.0,>=1.6->pylint->spyder) (1.3.1)
Requirement not upgraded as not directly required: functools32; python_version == "2.7" in /Library/Python/2.7/site-packages (from jsonschema!=2.5.0,>=2.4->nbformat>=4.4->nbconvert->spyder) (3.2.3.post2)
Requirement not upgraded as not directly required: webencodings in /Library/Python/2.7/site-packages (from html5lib!=1.0b1,!=1.0b2,!=1.0b3,!=1.0b4,!=1.0b5,!=1.0b6,!=1.0b7,!=1.0b8,>=0.99999999pre->bleach->nbconvert->spyder) (0.5.1)
Requirement not upgraded as not directly required: backports-abc>=0.4 in /Library/Python/2.7/site-packages (from tornado>=4.1->jupyter-client>=4.1->qtconsole>=4.2.0->spyder) (0.5)
Requirement not upgraded as not directly required: simplegeneric>0.8 in /Library/Python/2.7/site-packages (from ipython>=4.0.0->ipykernel>=4.1->qtconsole>=4.2.0->spyder) (0.8.1)
Requirement not upgraded as not directly required: backports.shutil-get-terminal-size; python_version == "2.7" in /Library/Python/2.7/site-packages (from ipython>=4.0.0->ipykernel>=4.1->qtconsole>=4.2.0->spyder) (1.0.0)
Requirement not upgraded as not directly required: appnope; sys_platform == "darwin" in /Library/Python/2.7/site-packages (from ipython>=4.0.0->ipykernel>=4.1->qtconsole>=4.2.0->spyder) (0.1.0)
Requirement not upgraded as not directly required: pexpect; sys_platform != "win32" in /Library/Python/2.7/site-packages (from ipython>=4.0.0->ipykernel>=4.1->qtconsole>=4.2.0->spyder) (4.5.0)
Requirement not upgraded as not directly required: prompt-toolkit<2.0.0,>=1.0.4 in /Library/Python/2.7/site-packages (from ipython>=4.0.0->ipykernel>=4.1->qtconsole>=4.2.0->spyder) (1.0.15)
Requirement not upgraded as not directly required: ptyprocess>=0.5 in /Library/Python/2.7/site-packages (from pexpect; sys_platform != "win32"->ipython>=4.0.0->ipykernel>=4.1->qtconsole>=4.2.0->spyder) (0.5.2)
Requirement not upgraded as not directly required: wcwidth in /Library/Python/2.7/site-packages (from prompt-toolkit<2.0.0,>=1.0.4->ipython>=4.0.0->ipykernel>=4.1->qtconsole>=4.2.0->spyder) (0.1.7)

I can't find Spyder anywhere

What is the expected output? What do you see instead?
I would expect either an error (installation failed) or to be able to find Spyder in the app folder or in the usr/local/bin
Paste Traceback/Error Below (if applicable)

No visible error
Package Versions

Spyder:
Python: 3.6
Qt:
PyQt:
Operating System: MacOS 10.13.4

Dependencies

PASTE DEPENDENCIES HERE

Found the .dmg of version 2.3.4

Thanks for reporting @nuthinking With regard to your actual issue, as our docs state we unfortunately are not able to provide individual installation support for pip installs  due to lack of resources, as they are only for experts who can resolve the numerous tricky, machine-specific problems that can result, like this one. Therefore, we recommend you download the latest version of Anaconda instead. Best of luck!

I would have found a dmg file in github releases

Where does it say this? It previously contained an out of date reference to our dmg installers, but we haven't been offering these in years, and this should have been fixed half a year ago in #5978

Found the .dmg of version 2.3.4

That version is ancient, years and years out of date (the current version is 3.2.8). We haven't released dmg installers in years, so they shouldn't even be available anywhere—where did you find that?

I can't find Spyder anywhere

You need to open Terminal.app and run there
spyder3

to start it.

-bash: spyder3: command not found

@CAM-Gerlach here it says "Use our DMG installers, ..." Thanks for the info! ;)

Thanks @nuthinking Those docs are well out of date; PyHosted has been deprecated and frozen for a long time so we can't modify them there. Our new docs are up as part of our site; they should be officially released in full shortly and will be linked from the next release of Spyder on, and those will eventually be removed or redirected.


Added eformity connector

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.

[x] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
[x] I attest that the connector works and I verified by deploying and testing all the operations.
[x] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[x] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[x] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[ ] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[ ] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[ ] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[ ] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

@microsoft-github-policy-service agree company="eformity document solutions b.v."

Hello @bas-eenhoorn,
Thank you so much for submitting your connector artifacts. May I ask you please to confirm if you own the API?
As we ask all our partners/API Owners to register their connectors, may I ask you please to register your connector by filling out our registration form.
Thank you so much again.
Please let me know if you have any questions.

Thank you very much!
I do have a question (if this is the place for that). Is the 230x230 icon size a requirement? Because the submission requirements dont make that clear. It says approximately ("Create a logo of approximately 160 × 160 pixels inside a square of approximately 230 × 230 pixels").

@bas-eenhoorn yes the icon must be 230 × 230 pixels. and please submit in ISV Studio only.


Bump build number

This PR bumps the build number to create a build against the latest assimp build. Workaround until assimp migration are properly handled by conda-forge machinery, see https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/2455 .
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

ppc64 build lacks an assimp build, it should be fixed by https://github.com/conda-forge/assimp-feedstock/pull/37 .


Update nanopb from <IP_ADDRESS> to <IP_ADDRESS>

No appreciable change.

Doesn't this require a corresponding change to the nanopb CocoaPod?

Doesn't this require a corresponding change to the nanopb CocoaPod?

It shouldn't since the generated sources are identical. I've been using a newer nanopb to generate these sources from the beginning (on accident).

The podspec is still at 0.3.901.
Is there a reason for updating or going out of sync?

I just set a periodic reminder to update nanopb. I'm actually ahead of the cocoapod and have been using <IP_ADDRESS> to generate since the creation of GDT. Since the actual code didn't change at all, we can consider this to just future-proof GDT for a while.

That seems reasonable as long as there are also no differences with what gets generated by <IP_ADDRESS>.  Have you verified that?

Yeah, this PR is the difference is generated sources. The only thing it did was change the nanopb version number in the file comment.

I’m not sure I agree with the rationale of this change. While the generated sources may not have changed, the runtime has and the change gives the appearance that you’ve tested with <IP_ADDRESS>.
Given that there’s no effective change and you haven’t tested I’d advocate for deferring this. I don’t feel strongly though, so I won’t block the PR.

I'll hold off on updating in the future to make sure the cocoapod matches
the generation version.
On Wed, Oct 2, 2019 at 1:37 PM Gil<EMAIL_ADDRESS>wrote:

I’m not sure I agree with the rationale of this change. While the
generated sources may not have changed, the runtime has and the change
gives the appearance that you’ve tested with <IP_ADDRESS>.
Given that there’s no effective change and you haven’t tested I’d advocate
for deferring this. I don’t feel strongly though, so I won’t block the PR.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/firebase/firebase-ios-sdk/pull/3977?email_source=notifications&email_token=AAIILARENUX4HFVJ35647PTQMUBBJA5CNFSM4I42DC4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAGDCMY#issuecomment-537669939,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIILAVWAOYYUBRXE7TJN5LQMUBBJANCNFSM4I42DC4A
.


Fix some typos and warnings found by static check

Signed-off-by: Li Yi<EMAIL_ADDRESS>Ⅰ. Describe what this PR does
Fix some typos and warnings found by static check
https://staticcheck.io/
staticcheck ./...
Ⅱ. Does this pull request fix one issue?
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

/lgtm


add WithFieldFunc() for dynamic fields at log invocation with fixed calldepth

Hi!
we've been scratching our heads for a way to implement line numbering in a non fragile way that won't break when new wrapper handlers are added, and this is what i've come up with. i appreciate i've changed quite a few things so i welcome feedback, or if you'd rather not that's fine too!
thanks
example line number implementation:
func GetAppLogContext() *alog.Entry {
	log := log.WithFieldFunc(func() alog.Fielder {
		_, file, line, ok := runtime.Caller(alog.FieldFuncCallDepth)
		if ok {
			return alog.Fields{
				"caller_file": file,
				"caller_line": strconv.Itoa(line),
			}
		}
		return nil
	})
	return log
}

bruh

It's a little hacky due to how pkg/errors exposes the filename/lineno, but there's support for pkg/errors which may help a bit if you can use that.
I'm not against it but I'd definitely prefer to keep the API smaller if possible, couldn't a function just implement Fielder? similar to http.HandlerFunc(), maybe we just need FielderFunc

hey, thanks for getting back to me!
we're currently moving over to pkg/errors so hopefully will have that soon, however we wanted to be able to attach additional info for non-error logs as well, i think this would be useful for attaching extra dynamic info without having to register an entire new log.Handler to wrap all logs, such as only attaching something like memory/runtime info to log lines in a certain area of code. I'm not sure what you mean by the http.HandlerFunc equivalent, as the WithFieldFunc() already accepts a FielderFunc, so the api is about as terse as i can see it being

Something like:
  // The HandlerFunc type is an adapter to allow the use of
  // ordinary functions as HTTP handlers.  I've only ever really needed ctx = ctx.WithFields(...), not saying it's a bad idea or anything but good to know :D

i think i get what ya mean now! i think i'll remove the CallDepth const as that kinda pollutes the api too, i'll just add a mention of the expected calldepth in godoc.
one of the main use cases i can think of is how it can simplify the flow of your logging in many situations, instead of having to call WithFields() to reattach new/updated data for each log line, you simply attach a FieldFunc to the root context for that area of code, and you can log knowing that each log line will have totally up to date data. the kind of things i'd attach to this are runtime/memory/gc stats, current reads of counters from instrumentation, cpu load, LOC/package

Seems like something that could maybe be delegated with a little util func, like ctx = util.LogContext(ctx) in the app somewhere


Training  problem Got processor for bboxes, but no transform to process it.

Hi,
trying to replicate your examples (bird nests) and my own data
training always stops at the same point:
Environment (please complete the following information):

OS: Mac and windows
Python version and environment : 3.13.1 conda env

Using your Tutorial for training a nest detection model
`# Start the training
start_time = time.time()
m.trainer.fit(m)`
I get:
UserWarning: Consider setting persistent_workers=True in 'train_dataloader' to speed up the dataloader worker initialization.
/opt/anaconda3/envs/deepforest/lib/python3.13/site-packages/albumentations/init.py:24: UserWarning: A new version of Albumentations is available: 1.4.22 (you have 1.4.21). Upgrade using: pip install -U albumentations. To disable automatic update checks, set the environment variable NO_ALBUMENTATIONS_UPDATE to 1.
check_for_updates()
UserWarning: Got processor for bboxes, but no transform to process it.
UserWarning: Consider setting persistent_workers=True in 'val_dataloader' to speed up the dataloader worker initialization.
and then:
"name": "KeyError",
"message": "Caught KeyError in DataLoader worker process 0.\nOriginal Traceback (most recent call last):\n  File "/opt/anaconda3/envs/deepforest/lib/python3.13/site-packages/torch/utils/data/_utils/worker.py", line 351, in _worker_loop\n    data = fetcher.fetch(index)  # type: ignore[possibly-undefined]\n  File "/opt/anaconda3/envs/deepforest/lib/python3.13/site-packages/torch/utils/data/_utils/fetch.py", line 52, in fetch\n    data = [self.dataset[idx] for idx in possibly_batched_index]\n            ~~~~~~~~~~~~^^^^^\n  File "/opt/anaconda3/envs/deepforest/lib/python3.13/site-packages/deepforest/dataset.py", line 110, in getitem\n    targets["labels"] = image_annotations.label.apply(\n                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^\n        lambda x: self.label_dict[x]).values.astype(np.int64)\n        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n  File "/opt/anaconda3/envs/deepforest/lib/python3.13/site-packages/pandas/core/series.py", line 4924, in apply\n    ).apply()\n      ~~~~~^^\n  File "/opt/anaconda3/envs/deepforest/lib/python3.13/site-packages/pandas/core/apply.py", line 1427, in apply\n    return self.apply_standard()\n           ~~~~~~~~~~~~~~~~~~~^^\n  File "/opt/anaconda3/envs/deepforest/lib/python3.13/site-packages/pandas/core/apply.py", line 1507, in apply_standard\n    mapped = obj._map_values(\n        mapper=curried, na_action=action, convert=self.convert_dtype\n    )\n  File "/opt/anaconda3/envs/deepforest/lib/python3.13/site-packages/pandas/core/base.py", line 921, in _map_values\n    return algorithms.map_array(arr, mapper, na_action=na_action, convert=convert)\n           ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n  File "/opt/anaconda3/envs/deepforest/lib/python3.13/site-packages/pandas/core/algorithms.py", line 1743, in map_array\n    return lib.map_infer(values, mapper, convert=convert)\n           ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n  File "lib.pyx", line 2972, in pandas._libs.lib.map_infer\n  File "/opt/anaconda3/envs/deepforest/lib/python3.13/site-packages/deepforest/dataset.py", line 111, in \n    lambda x: self.label_dict[x]).values.astype(np.int64)\n              ~~~~~~~~~~~~~~~^^^\nKeyError: 'Nest'\n",

@robinsandfort Thank you for reporting the issue! Could you clarify which example you're trying to replicate?
Please verify that the label column in your dataset contains the correct labels and matches those in the label_dict. Let us know if that works.

@henrykironde Hi Henry,
for example this one:
https://deepforest.readthedocs.io/en/v1.4.1/user_guide/examples/nest_detection.html
I somehow think that
`##Set parameters for the training run
#Define the pre-trained model
model = main.deepforest()
model.config['gpus'] = '-1' #move to GPU and use all the GPU resources
#model.config["save-snapshot"] = False
#model.config["train"]["fast_dev_run"] = True
#The annotation table
model.config["train"]["csv_file"] = training_file
#The directory where the training imagery is located
model.config["train"]["root_dir"] = os.path.dirname(training_file)
model.config["score_thresh"] = 0.4
model.config["train"]['epochs'] = 4
model.config["validation"]["csv_file"] = validation_file
model.config["validation"]["root_dir"] = os.path.dirname(validation_file)
model.create_trainer()
`
Is not correctly created. Where are this settings saved?
deepforest_config.yml is not changed:
args?
Greetings,
Robin

Maybe no dataloader is defined?

@robinsandfort Thank you for reporting the issue! Could you clarify which example you're trying to replicate?
Please verify that the label column in your dataset contains the correct labels and matches those in the label_dict. Let us know if that works.

Hi Henry,
yes. I use the nest exampel files with the label Nest and
m = main.deepforest(label_dict={"Nest": 0})

Got it running. Most likely it was a mismatch between label_dict and the label column.
Thanks for your hind!


Model / gather non-interactive assets for the construction site

Basic props and materials added to the project's folders, with a demo scene. I'll add more models for things like basic building structures later (tomorrow).


When PowerShell runs elevated on Windows, starting *.msc files locks the console

When PowerShell v7.1.0-preview.7 or v7.1.0-rc.1 is started as Administrator on Windows, and I start some mmc snap-in: compmgmt, diskmgmt, etc., it locks the console until I close the snapin.
It doesn't lock on v7.1.0-preview.6 and earlier versions.
It doesn't lock when PowerShell started as standard user (no elevation).
Also, it doesn't lock, when I start the snapin as mmc compmgmt.msc
I haven't found (yet?) other file types, that behave like this, maybe there are some.
Steps to reproduce
compmgmt

Expected behavior
Computer management snapin starts, console doesn't lock.

Actual behavior
Computer management snapin starts, console locks until snapin closes.

Environment data

Name                           Value
----                           -----
PSVersion                      7.1.0-rc.1
PSEdition                      Core
GitCommitId                    7.1.0-rc.1
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

This only appears to repro in Windows Terminal and not conhost.  cc @dhowett

It doesn't lock on v7.1.0-preview.6 and earlier versions.

That's alarming!

This reproduces in conhost and terminal for me.

I'm probably not familiar enough to trace exactly where or why this changed, but I have a feeling it's probably a .NET change between the preview versions used for 7.1-p6 and later 7.1 previews/RC.

The change inhttps://github.com/PowerShell/PowerShell/pull/13481 landed in preview7, and it changes a bit about how PowerShell detects what applications to "wait" for. It looks like it subtly shuffles the logic around in a way that may have caused an issue?

/cc @iSazonov

@dhowett, oops I forgot to run cmd.exe elevated which is why it didn't repro for me...


httproute 权重更新有问题

httproute
apiVersion: gateway.networking.k8s.io/v1beta1
kind: HTTPRoute
metadata:
  creationTimestamp: "2023-04-27T07:30:47Z"
  generation: 57
  labels:
    app_id: d3251dc4bd6748a4ae9ec4e1da73c7a8
  managedFields:
  - apiVersion: gateway.networking.k8s.io/v1beta1
    fieldsType: FieldsV1
    fieldsV1:
      f:status:
        .: {}
        f:parents: {}
    manager: pilot-discovery
    operation: Update
    subresource: status
    time: "2023-04-27T07:30:47Z"
  - apiVersion: gateway.networking.k8s.io/v1beta1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:labels:
          .: {}
          f:app_id: {}
      f:spec:
        .: {}
        f:hostnames: {}
        f:parentRefs: {}
    manager: rainbond-api
    operation: Update
    time: "2023-04-27T07:30:47Z"
  name: default-038a99
  namespace: zhangqh
  resourceVersion: "7457252"
  uid: cd174b49-a50c-4151-a7aa-a7cede3d0c87
spec:
  hostnames:
  - rainbond.example.com
  parentRefs:
  - group: gateway.networking.k8s.io
    kind: Gateway
    name: bookinfo-gateway
    namespace: zhangqh
  rules:
  - backendRefs:
    - group: ""
      kind: Service
      name: nginx
      namespace: zhangqh
      port: 80
      weight: 1
    matches:
    - path:
        type: PathPrefix
        value: /
status:
  parents:
  - conditions:
    - lastTransitionTime: "2023-05-06T03:57:02Z"
      message: Route was valid
      observedGeneration: 57
      reason: Accepted
      status: "True"
      type: Accepted
    - lastTransitionTime: "2023-05-06T03:57:02Z"
      message: All references resolved
      observedGeneration: 57
      reason: ResolvedRefs
      status: "True"
      type: ResolvedRefs
    controllerName: istio.io/gateway-controller
    parentRef:
      group: gateway.networking.k8s.io
      kind: Gateway
      name: bookinfo-gateway
      namespace: zhangqh

rollout
apiVersion: rollouts.kruise.io/v1alpha1
kind: Rollout
metadata:
  annotations:
    rollouts.kruise.io/hash: 2f5d4z94dvv5z4zb9fz4vd4z95w7297fd4825wb7cdw8464fdfcbvz49d5vbd2w2
    rollouts.kruise.io/rolling-style: partition
  creationTimestamp: "2023-05-06T05:41:24Z"
  finalizers:
  - rollouts.kruise.io/rollout
  generation: 1
  labels:
    app_id: d3251dc4bd6748a4ae9ec4e1da73c7a8
    component_id: 2dd5cc625b09f75b9a01ef632045d183
    hostname: rainbond.example.com
  managedFields:
  - apiVersion: rollouts.kruise.io/v1alpha1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          f:rollouts.kruise.io/hash: {}
        f:finalizers:
          .: {}
          v:"rollouts.kruise.io/rollout": {}
    manager: kruise-rollout
    operation: Update
    time: "2023-05-06T05:41:24Z"
  - apiVersion: rollouts.kruise.io/v1alpha1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .: {}
          f:rollouts.kruise.io/rolling-style: {}
        f:labels:
          .: {}
          f:app_id: {}
          f:component_id: {}
          f:hostname: {}
      f:spec:
        .: {}
        f:objectRef:
          .: {}
          f:workloadRef:
            .: {}
            f:apiVersion: {}
            f:kind: {}
            f:name: {}
        f:strategy:
          .: {}
          f:canary:
            .: {}
            f:steps: {}
            f:trafficRoutings: {}
    manager: rainbond-worker
    operation: Update
    time: "2023-05-06T05:41:24Z"
  - apiVersion: rollouts.kruise.io/v1alpha1
    fieldsType: FieldsV1
    fieldsV1:
      f:status:
        .: {}
        f:canaryStatus:
          .: {}
          f:canaryReadyReplicas: {}
          f:canaryReplicas: {}
          f:canaryRevision: {}
          f:currentStepIndex: {}
          f:currentStepState: {}
          f:lastUpdateTime: {}
          f:message: {}
          f:observedWorkloadGeneration: {}
          f:podTemplateHash: {}
          f:rolloutHash: {}
          f:stableRevision: {}
        f:conditions: {}
        f:message: {}
        f:observedGeneration: {}
        f:phase: {}
    manager: kruise-rollout
    operation: Update
    subresource: status
    time: "2023-05-06T05:41:27Z"
  name: default-nginx
  namespace: zhangqh
  resourceVersion: "7489716"
  uid: e60ce2c7-2753-4355-a9aa-ed796fda264c
spec:
  objectRef:
    workloadRef:
      apiVersion: apps/v1
      kind: Deployment
      name: default-nginx
  strategy:
    canary:
      steps:
      - matches:
        - headers:
          - name: qqq
            type: Exact
            value: qqq
        pause: {}
        weight: 50
      - matches:
        - headers:
          - name: qqq
            type: Exact
            value: qqq
        pause: {}
        weight: 70
      - matches:
        - headers:
          - name: qqq
            type: Exact
            value: qqq
        pause: {}
        weight: 100
      trafficRoutings:
      - gateway:
          httpRouteName: default-038a99
        service: nginx
status:
  canaryStatus:
    canaryReadyReplicas: 2
    canaryReplicas: 2
    canaryRevision: 66c4494759
    currentStepIndex: 1
    currentStepState: StepPaused
    lastUpdateTime: "2023-05-06T05:41:39Z"
    message: BatchRelease is at state Ready, rollout-id , step 1
    observedWorkloadGeneration: 265
    podTemplateHash: 66c4494759
    rolloutHash: 2f5d4z94dvv5z4zb9fz4vd4z95w7297fd4825wb7cdw8464fdfcbvz49d5vbd2w2
    stableRevision: 8487bf6555
  conditions:
  - lastTransitionTime: "2023-05-06T05:41:24Z"
    lastUpdateTime: "2023-05-06T05:41:24Z"
    message: Rollout is in Progressing
    reason: InRolling
    status: "True"
    type: Progressing
  message: Rollout is in step(1/3), and you need manually confirm to enter the next
    step
  observedGeneration: 1
  phase: Progressing

@ZhangSetSail The problem is not clearly described.


Fix BITBUCKET mapping [UNTESTED]

Description
UNTESTED.
Allows multiple PRs from bitbucket
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Chore: cleanup/renaming, etc
[ ] RFC

Notes

Acceptance

[x] I have read the Contributing guidelines
[x] I have read the Code of Conduct

This is gonna be hard to test w/o access to an actual repo, indeed. Should we just release it and test in the wild with our Bitbucket users?

This is gonna be hard to test w/o access to an actual repo, indeed. Should we just release it and test in the wild with our Bitbucket users?

Yes, I sent the PR because worst case scenario we stay broken


RFC 21: Internal Data Monitoring

Tracking issue: #21, #20
Rendered version

By submitting this pull request, I confirm that my contribution is made under
the terms of the MIT license

@tylercxu i think u need to check to see if the [my-branch] part of the PR description works out to data


When scaffolding a data view in VS, I get duplicated key error for DOTNET_SKIP_FIRST_TIME_EXPERIENCE

From @twsouthwick on March 1, 2017 22:42
Not sure if this is the right repo, but I'll start here:
Steps to reproduce

Set DOTNET_SKIP_FIRST_TIME_EXPERIENCE=1 as an environment variable
Launch VS (I'm using 15.0.26228.0)
Create an ASP.NET Core application
In project view, right click Controllers ->Add->New Scaffolded Item and then select MVC Controller - Empty
Fill in name

Expected  behavior

New controller should be generated

Actual behavior

Get an error:

For searching, the text is:
Error

There was an error running the selected code generator: 'Item has already been added. Key in dictionary: 'DOTNET_SKIP_FIRST_TIME_EXPERIENCE' Key being added: 'DOTNET_SKIP_FIRST_TIME_EXPERIENCE''

Environment data
dotnet --info output:
.NET Command Line Tools (1.0.0)

Product Information:
 Version:            1.0.0
 Commit SHA-1 hash:  e53429feb4

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.14393
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\1.0.0

C:\Program Files (x86)\Microsoft Visual Studio\2017\Internal>

Copied from original issue: dotnet/cli#5887

From @livarcocc on March 1, 2017 23:12
@BillHiebert Can you take a look? Are you the right person?

This issue was moved to aspnet/Tooling#1008

Unrelated, but how are you guys moving the issues between repos?

@twsouthwick https://github-issue-mover.appspot.com/


Add state transaction operation api

Describe the proposal
Add state transaction operation api - dapr/dapr#1892

Isn't this already merged?

Isn't this already merged?

Really? I did not recognize it..

Ok sorry, wrong repo.


How to reduce the amount of metadata when there are a lot of reflections in the code.

Describe the problem
See a class:
public class ClassAlias {

    private static final Map<String, Class<?>> CLASS_ALIAS = new HashMap<>();

    static {
        addAlias("class1", Class.forName("Class1")); // in the `native-image`, throw `ClassNotFoundException`.
        addAlias("class2", Class.forName("Class2"));
        addAlias("class3", Class.forName("Class3"));
        addAlias("class4", Class4.class); // in the `native-image`, the clazz will be a `null` value.
        addAlias("class5", Class5.class);
        addAlias("class6", Class6.class);
        ......
        addAlias("class99", Class.forName("Class99"));
        addAlias("class100", Class100.class);
    }

    public static void addAlias(String alias, Class<?> clazz) {
        CLASS_ALIAS.add(alias, clazz);
    }

}

Please see a specific class: https://github.com/x-stream/xstream/blob/master/xstream/src/java/com/thoughtworks/xstream/XStream.java
Can I only add 100 metadata? Or are there other simpler configurations?
Additional context
Add any other context about the problem here.
System Info (please complete the following information):

OS: [e.g. Windows]
GraalVM Version [e.g. 22.0 CE]
Java Version [e.g. 17]
Plugin version [e.g. native-gradle-plugin:0.9.10]

To Reproduce
If possible please attach a complete reproducer here (either as a zip file or as a link to public repository/branch).

We are working towards a way to do this kind of definition in the code of the project. This is expected to land in the next release of GraalVM as a preview feature. Until then, we can only do this via JSON.

OK, I understand.
Thank you for your answer.
Look forward to the next release.

@vjovanov @dnestoro Is there a new feature?

Yes, the example above should already work with Native Image. When forName gets a literal it should be converted directly into a class. If that is not the case please open a ticket.


Fixing typo error in docs/

Description
This PR fixing a some typos errors in code documentations. Like:

Adding missing ',' in vector_stores.md
Deleted extra '...' in fullstack_app_guide.md
Fixing except margin in fullstack_with_delphic.md
Adding missing ‘)’ in fullstack_with_delphic.md

Type of Change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] I stared at the code and made sure it makes sense

Suggested Checklist:

[ ] I have performed a self-review of my own code
[ ] My changes generate no new warnings

Thank you, I appreciate it


Compile Issue

I am facing below error while I am trying to run "npm run dev".

For reference: https://github.com/almasaeed2010/AdminLTE/issues/1669