svg should be intentionally displayed inline

this prevents css resets, like tailwindcss, from making the svg dispaly: block

Thank you! I'm behind on a few things so may not have time to merge / release until this weekend.
I shouldn't forget, but please feel free to remind me if I do.

No problem at all! It's easy enough to just add it to the CSS on my project until resolved. Thanks for you response!


chore(master): release 0.4.16

:robot: I have created a release beep boop
0.4.16 (2024-07-05)
🚀 Features

switch to release-please release manager (234f244)

📚 Documentation

add PR template (ad0fd01)
refine README.md badges (8fc2a37)

✨ Polish

ci: cleanup GH action (ee255e7)
refine GH action setup-bun configuration (25382b6)
switch biome.js configuration to standard.js style (5d9754a)

🤖 Automation

ci: add autofix GH action (736c4f8)
ci: do not cancel workflow on autofix.ci error (d2b04dc)
ci: fix setup-bun configuration (a12a9d0)
ci: really ensure tag version is not prefixed with 'v' (7dbb1be)
ci: remove v prefix in release-please tag (1aa36d1)
deps-dev: apply updates (51d9eea)
deps-dev: apply updates (e8d8302)
deps-dev: apply updates (8603c48)
deps-dev: apply updates (0a7ace0)
deps-dev: apply updates (0785cfc)
deps-dev: apply updates (1f3034e)
deps-dev: apply updates (b9bb1e0)
deps: bump oven-sh/setup-bun from 1 to 2 (9c3fe1b)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

0.4.16
:sunflower:


Need to add more safegaurds to write methods

added one such example to write_names which now checks if a valid number of variables is present. If it isn't it will do that method call for the user.


Release 2.1.0

Remove support for older versions of Ruby than 2.2.2
Add support for Ruby 2.3.0 and 2.4.0
Update dependency for vCloud Core and vCloud Tools Tester
Various bug fixes

This PR also updates some dependencies.
https://trello.com/c/0uDbDpkt/574-update-dependencies-on-vcloud-tools

Merge away


Simplify high load game number checks

Sparked from https://github.com/Zarel/Pokemon-Showdown/commit/d105beeacdb719f7093b23dca2191bbd9016fe7b discussion.

This just makes the check take more RAM, it only makes it more readable.

We would previously have used Object.size but unfortunately that doesn't currently exist...

So, is there nothing to change with this then?

Honestly, Object.keys(...).length might not be that bad. Do @Slayer95 and @kotarou3 have opinions?

Idk how much the RAM matters. This feels like you're putting too much
emphasis on something that matters very little.

I believe kota had suggested it on the mentioned commit comments

Idk how much the RAM matters.

We're crashing multiple times a day because of a RAM issue. To be fair, I think it's way subtler than just "using too much RAM" but still...

RAM has been the most of a resource that PS demands, so generally speaking, I wouldn't say that it "doesn't matter."


Note: Interrupting pipeline during file saves

Issue to note:

During any numpy savez calls or during zarr saving, if the pipeline is interrupted or killed, this can leave half-done files that can corrupt. In the case of zarr files, this may not fully corrupt the file, and could potentially leave zeros in some places? I am unsure about this.
Be very careful when interrupting a pipeline, if this interrupt occurs during a file save, make sure to delete the file that was half saved (you can check from the progress bar + the interrupt log).

What we can do for the Notebook is, when we try add a new notebook page to the notebook, save a temporary extra Notebook with a different file name, then add and save the notebook with one of the duplicate files. This way, if the save is interrupted and the notebook is corrupted, then we still have a spare that did not have the new notebook page added as a backup. This can then be automatically deleted once the save is fully completed for the notebook with the added page.

However, this does not solve the issue with .zarr arrays, I do not think there is an easy way to deal with this issue.


[#168] Introduced local components for async

ADded TraceKeys for Async and HTTP
Async from Callables in RestControllers continue span
ALl the other async are creating a local component span

This change is positive, but it has highlighted some pretty intense hierarchy :)
I'd axe the "delegate" hierarchy stuff as it indirects things and seems to only serve two incompatible entry points: callable and runnable.
What if instead, you killed everything underneath two types:  LocalSpanCallable, LocalSpanRunnable?
I suspect the line count and indirection would go way down at the cost of duplicating some rather easy to test annotation adding (even that could be a package private utility)

That's actually what I had initially and I changed it to this. So if we both thought about this then most likely it v makes more sense ;)

I'd collapse any single-child hierarchies where only the leaf is used (if that exists). For example, if only LocalSpanFooable is used (not its parent), squash the parent. Also, I think SpanNamer is a better name for what's being done, although (forgetting the language level) it could be a function interface vs a concrete type that's actually injected.
besides that, lgtm

Done in https://github.com/spring-cloud/spring-cloud-sleuth/commit/cf6f62966382a72fb4202ad4cf43414b01bcd433


Migration to CFS

Description: This PR adds .npmrc to all packages in the repository to consume packages from the internal feed.
Related: AB#2197030

/azp list


Update Get-NetEventNetworkAdapter.md

added description for -asjob

Docs Build status updates of commit b3b1b98:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012r2-ps/neteventpacketcapture/Get-NetEventNetworkAdapter.md
:white_check_mark:Succeeded

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

@nenonix Copy editing is needed for this PR. Thanks.

@dariomws306 @tseward
Peer review needed for this PR. Thanks.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.


Configure vscode prelaunch task problem matchers

Perviously we were using $tsc-watch pre configured
problem matcher to let vscode know when to start extension
development host, when running the extension locally.
Once we moved to webpack + typescript watch mode, this
wasn't working anymore, causing vscode to hang when
extension is launched, eventhough the comiplation
is successful.
Vscode doesn't have inbuilt problem matchers for webpack
output. Hence the need for this.
More Info: https://code.visualstudio.com/docs/editor/tasks#_defining-a-problem-matcher
Based on https://github.com/eamodio/vscode-tsl-problem-matcher
Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #15687 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #15687   +/-   ##
=========================================
  Coverage     13.18%   13.18%
  Complexity     1720     1720
=========================================
  Files           925      925
  Lines         35680    35680
  Branches       5134     5134
=========================================
  Hits           4706     4706
  Misses        30498    30498
  Partials        476      476

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 e3832ac...17fed0e. Read the comment docs.


#27 Add base standard props to angular component

Todo:

styleUrls for link scss + .scss related file
spec.ts file for testing
making them above as a options to cli

Amazing! Thank you for your great work @jackcoral89 🎉
This closes #27


[test] Port halo cell exchange to Eiger

I do not like the code duplication in the self.reference dictionary

@ajocksch Can you double check the new references?

@jenkins-cscs retry eiger


[Specific-PSXPC_N] Lara State Control issue (Jump + Roll)

Lara rolls twice in the air during jump + roll.

Fixed in: https://github.com/TOMB5/TOMB5/commit/d89cd175acae25209d5dec21b659ce9847c6f44a


Migrate from TSLint to ESLint

As https://github.com/palantir/tslint#tslint states: "TSLint will be deprecated some time in 2019", so we should migrate to ESLint. Also, after typescript version update https://github.com/celo-org/celo-monorepo/pull/2196 we are now using ^3.7.3, but our TSLint using ~3.4.0. This resolves to discrepancy between the developing process and actual build.
As a short term solution we can update TSLInt to 6.0.0-beta1, where typescript version is ~3.6.3 to shorten the difference.

@nityas is this still something we want to do?


Errors

I didnt understand how I can handle "Your quota is exceeded or your API key is invalid, please set a valid key: ELEVEN_API_KEY" error. It seems like this library does not include any Exception classes. I would be greatly thankful for the update or some explenation. And yeah, appreciate your work a lot.

You can set your API key as:
from elevenlabs import set_api_key

set_api_key("YOUR_API_KEY_HERE")

Check the bottom of the readme for more details: https://github.com/elevenlabs/elevenlabs-python#-api-key

You can set your API key as:
from elevenlabs import set_api_key

set_api_key("<YOUR_API_KEY>")

Check the bottom of the readme for more details: https://github.com/elevenlabs/elevenlabs-python#-api-key

Okay, I do know this, but I`m running to this error because my quota has exceeded. So how can I catch the moment when I cant use my api key anymore this month using this library?

I apologise for the misunderstanding. In v0.2.7 you'll find a more proper error handling that raises a RateLimitError when quota for the current API key is exahusted. Similarly there's a more specific subclass of RateLimitError
called UnauthenticatedRateLimitError for unauthenticated users.
from elevenlabs import RateLimitError, UnauthenticatedRateLimitError

Thank you, this works. ❣ Will continue on exploring this library and using your impressive service`s features, as well as trying to help at least a bit

Hello,
Have this error using eleventlabs
File "/var/www/html/projects/dd-MyProject/api/wsgi.py", line 106, in audioGeneration
audio = generate(
TypeError: generate() got an unexpected keyword argument 'model'
^C(.env) root@idarevalos-G7:/var/www/html/projects/dd-MyProject//api#
How to resolve ?
Someone can help me ?
python version 3.10.12
Name: elevenlabs, Version: 0.2.0
Thank you


*(dm): move some SQL utils under BaseDB/BaseConn

What problem does this PR solve?

Issue Number: ref #4287
What is changed and how it works?
BaseDB/BaseConn can retry on errors, this PR let some SQL utils use BaseDB/BaseConn
Check List
Tests

pass existing test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`.

rest lgtm. It seems some of the functions in the utils pkg (e.g. GetFlavor, GetSlaveServerID) have not been utilizing baseDB. Will it be done in future pr or any further consideration around that?

I'll open a tracking issue for them, they should also be done.

/merge

/run-leak-test


#178 Fixed the position of search in Navbar and added a drop down effect to it.

The desktop view remains unchanged. Just added a little margin to search bar so that it doesn't look too close to the rest items.

The search bar is now displayed at the end of the list items. Also on opening the nav menu it appears to be dropping down so it gives a good effect for the user.

Since, the UI has been changed look at for if this issue is still there and make sure to sync the repository with main branch and then make the changes


Dependency package @typescript-eslint/parser has a new version available

We have identified a dependency on version 5.57.1 of @typescript-eslint/parser. A new version (6.2.1) is available for upgrade.
Following are the steps to upgrade package dependency.

Understand the breaking changes between the version being used and the version you want to upgrade to.

Identify all packages that take a dependency on this package.

Go to the root folder for each such package (/sdk/service-name/package-name) and update package.json to have the new version.

Run rush update to ensure the new version is pulled in.

Make relevant changes to absorb the breaking changes.

Repeat steps 3 to 5 for each of the packages that have a dependency on this package.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.3230474,Service Bus:0.18756206,EngSys:0.045930713'

Need node16+ now https://github.com/typescript-eslint/typescript-eslint/issues/7284


[Breaking] drop node < 4 support

I've added some commits recently which fix support down to node 0.10 - those must be published in the 6.x line prior to merging this.
Merging this will be a semver-major change - it drops < node 4 support, and drops support for eslint v2. In the process, we'll be able to use any syntax and API that node 4 supports, yay!
I also enabled rules requiring template literals instead of concatenation, and autofixed them, both because I think it's a superior approach, and because it illustrates some of the new syntax we'll get to use :-)
(I'll manually keep this rebased and updated as time goes by, so ideally it will always be ready to merge when v7 comes along)

Wow! Great! Thanks for all this work. I'll try to review this PR tomorrow.

master must absolutely be published with v6, to fix the incorrect breaking changes in it, before this is merged and v7 is ready.

@yannickcr please don't release v7 before merging all the v7-tagged PRs; I'll update this one shortly and merge it today.

Ho, I was more in the idea the release the v7 to be React 15.5.0 compatible and to postpone theses breaking changes for the v8.
But I'm ok to do all of this in a single major release.

@yannickcr ah, i guess that would work too; the v7.0.0 milestone wasn't edited to v8 so that didn't come across. I think if we're doing a breaking change we might as well get them all in tho - I would have expected react 15.5 compatibility to be non-breaking, and to go in v6.

the v7.0.0 milestone wasn't edited to v8 so that didn't come across
yeah, my bad 😐
I think if we're doing a breaking change we might as well get them all in tho
right, it will avoid people some pain to only have one migration to do
I would have expected react 15.5 compatibility to be non-breaking, and to go in v6
I think this is unavoidable with the changes to createClass and the warnings added to no-deprecated

Couldn't we pivot on the react version in settings tho?

I figured the deprecation would only apply to 15.5 and later.


Issuer Discovery Should Be Standalone

The issuer discovery feature should be a standalone library as is could be used by any other projects without other features

Abandonned


merge from arlac77/template-github-action,arlac77/template-kronos-component

.github/workflows/update_readme_api.yml

chore(deps): (jobs.update_readme_api.steps.with.node-version)

Codecov Report

Merging #1349 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1349   +/-   ##
=======================================
  Coverage   78.94%   78.94%
=======================================
  Files           1        1
  Lines          38       38
  Branches        1        1
=======================================
  Hits           30       30
  Misses          8        8

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 c6cb077...2851265. Read the comment docs.


[Bug]: Gitlab Source is created but not listed

Is there an existing issue for this?

[X] I have searched the existing issues

Description
I tested coolify two weeks ago and didn't had this issue. So I think this is a recent bug.
It's happening on a fresh install.
Steps To Reproduce

Fresh install of coolify with only one user and one group
Go to GitSources
Add new GitSource
Select GitLab
Fill everything
Save
https://coolify.domain.tld/sources/{id} is working
https://coolify.domain.tld/sources shows "No git sources found"
Trying to recreate the GitSource fail with "OAuthID already configured in Coolify."

Version
v3.8.5

It will be fixed in the next version!


Switch demonstration application dependency from Carthage to SPM

Issue type
Feature request
Description of the problem
Since #257, the make setup builds all AppCenter frameworks, for iOS and tvOS platforms. it takes time, and not all libraries are needed (like no AppCenterAnalytics.
The idea is to switch to SPM dependency, as it's the dependency tool used for all SRG libraries.
The goal is to:

keep the single and universal target: see Demo.xcconfig and  https://davedelong.com/blog/2018/11/15/building-a-crossplatform-framework/
keep AppCenterDistribute dependency optional: only for iOS build, not for tvOS build.

Environment information

Package Manager Conditional Target Dependencies in Swift 5.3.

Sadly, the Xcode UI option to filter platform in the general target tab, "Frameworks, Libraries, and Content" section is only use during the link build phases.

When selected an Apple TV destination, Xcode tries to build  AppCenterDistribute library. The build fails, as the target is not available for tvOS.
Swift 5.3 introduced the Package Manager Conditional Target Dependencies (SE-0273). It's only for dependencies. Xcode SPM integration seems to not have this optional option for a dependency per platform.

We got a workaround idea: create an empty local product, which create the optional dependency on AppCenterDistribute.
A AppCenterDistributeOptional library is proposed. Naming can be discussed.
This workaround works.
Proposition is on feature/remove-carthage branch.


Misc gPTP changes part 2

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@c32681f). Click here to learn what that means.
The diff coverage is 71.42%.

@@            Coverage Diff            @@
##             master    #8681   +/-   ##
=========================================
  Coverage          ?   64.29%
=========================================
  Files             ?      440
  Lines             ?    42088
  Branches          ?     7047
=========================================
  Hits              ?    27062
  Misses            ?    11826
  Partials          ?     3200

Impacted Files
Coverage Δ

include/net/net_if.h
63.73% <ø> (ø)

tests/net/tx_timestamp/src/main.c
88.58% <100%> (ø)

subsys/net/ip/net_if.c
63.32% <50%> (ø)

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 c32681f...26f9910. Read the comment docs.

Typos in commit messages fixed.

Resolved merge conflict.


chromatin silencing at central core PMID:12526748

increased transcriptional repression at centromere central core
-> silencing to match others
also
decreased chromatin silencing at central core

The central core terms are different on purpose, per #2904. Could you look at that ticket again and check whether the reasoning there still holds? It does seem that if chromatin silencing reflects heterochromatin assembly, and the central core doesn't have heterochromatin, that it would still make sense for the central core terms not to be the same as the rest. But I don't have any preference as long as you've reviewed the older ticket and think this request explicitly supersedes it.
For 'decreased' see FYPO:0003217 - it's done the same way as the others, with "chromatin silencing" in a related synonym.

There  is chromatin in the central core, but it is specialized chromatin (Cenp-A) not heterochromatin.
So chromatin is still 'silenced'
But it would not make sense to have a 'transcriptional silencing' GO term for this, even when  we had silencing terms. This is because this region is not transcribed  (AFAIK) because it is under the kinetochore. The outer repeats produce the RNA that makes the siRNA, so this was not so bad although it was still  not really regulating transcription per se.
These are definitely 'silencing assays' though. A gene is inserted, and  expressed or not expressed dependent on the disruption of  CENP-A containing chromatin

That was all true at the time of ticket #2904. Please clarify: do you now think the name change done for that ticket was an error?

I thought the solution was to use

Upon closer inspection of the GO silencing terms, it looks like I can use GO "negative regulation of transcription" and SO "centromere central core".

which would seem correct to logically define
"chromatin silencing at the chromosome central core"
I don't see  where the FYPO terms went?

In #3635 we agreed that "silencing" phenotype terms will not have logical definitions using GO BP terms, because silencing is a phenotype that reflects effects on a process of heterochromatin assembly, and that sounds more specific than "negative regulation of transcription".
As I said in my previous comments, the central core terms were renamed to use the "transcriptional repression" wording. Do you now wish to revert that change?

p.s. I think the older suggestion is now out of date, now that "silencing" won't be a GO process any more.

I don't think I fully understood what was done previously.
I think the terms can have
transcriptional repression at centromere central core
and still be called 'silencing' in the term names?

In fact,  the definition could be more precise

Definition
Parents

A cellular process phenotype observed in the vegetative growth phase of the life cycle in which the occurrence of negative regulation of transcription at the central core of the centromeric regions is increased.

Should be
A cellular process phenotype observed in the vegetative growth phase of the life cycle in which the occurrence of constitutive repression of transcription at the central core of the centromeric regions effected by CENP-A containing chromatin is decreased
transcription isn't really 'negatively regulated' in a biological sense  because repression is the default state? Transcription if it ocvcur needs to be activated. This phenotype destroys the repression.
Odd that we have "increased transcriptional repression at centromere central core"
though. I don't know how silencing at the central core can be increased from a WT default repressed state. I will look at those....

also see #2576 and #3446

Can we back up a bit? I think I've lost grip on some key things, with the various changes ...
What (if anything) distinguishes a "chromatin silencing" phenotype from other transcription regulation phenotypes?
Before the move to take silencing BP terms out of GO, it was simple: refer to silencing BP terms or other transcription regulation BPs as needed, and let GO take care of defining them all. Now we have to make the distinction clear in FYPO definitions.
I'm also now confused about whether we should still avoid saying there are specifically "silencing" phenotypes at the centromere central core - at the time of #2904 we thought we shouldn't, and that's why term names were changed (FYPO:0000640, FYPO:0003217, FYPO:0005315). I think I might have a better idea whether they can change back once I understand what defines a "silencing" phenotype anywhere in the genome.

"chromatin silencing"  will always include heterochromatin formation, where transcriptional regulation may or may not.
We can be more specific in the constitutive heterochromatin regions:
"In addition to the larger constitutive heterochromatin regions found at centromeres, the mating-type region, rDNA, and telomeres, there are also so-called facultative heterochromatin regions in S. pombe (Zofall et al. 2012). These heterochromatic “islands” are present in vegetative cells and contain clusters of genes that are expressed and, hence, euchromatic in meiotic cells. "
and say that this  abolished/decreased  silencing is  something along the lines of
"derepression of  the epigenetically regulated region of constitutive heterochromatin at the centromere/telomere/rDNA/mating type region  by heterochromatin misassembly or disassembly )
Then at the facultative regions we can say
"derepression of a region of the facultative heterochromatin at the blah by heterochromatin misassembly or disassembly)
Does that work?
We can say there is "silencing at the central core" as a phenotype. It was only that  it seemed odd to have  this annotated to "silencing/ negative regulation of gene expression" by GO, or to have a GO term for it. There is no control of gene expression at the central core. Any transcription is  cryptic/non functional .

More thoughts on this. Basically it has been a bit of a mess in GO for ages, because nobody really knew the scope of silencing when  thses were first added to GO.
Part of the problem is because "chromatin silencing"  as used by the community, should not strictly have been a GO process. "chromatin silencing" can refer to anything which affects heterochromatin assembly OR maintenance. This would include, for example the factors which tether the heterochromatin to the nuclear envelope. In GO these became annotated to "negative regulation of transcription" which is clearly incorrect. But a "chromatin silencing" phenotype term would be OK.

There's still the same problem for the centromere central core: because it doesn't have heterochromatin, these two statements contradict each other:

"chromatin silencing" will always include heterochromatin formation

and

We can say there is "silencing at the central core" as a phenotype

Apart from that -- i.e. for everywhere except the central core -- it sounds like it would work define silencing phenotypes as affecting transcription in a region of the genome that is normally assembled into heterochromatin (whether constitutively or facultatively; most of the location-specific terms refer to constitutive ones).
So I think I've got it for the general case, and have come back round to the specific case of the central core, which still looks like an exception.

Ah got you.
Then can we say  OR GO:0061638    CENP-A containing chromatin"
That should cover everything.

So - just to confirm - this part of the stuff above wasn't accurate?

"chromatin silencing" will always include heterochromatin formation

And you do want to reverse the term name changes from #2904? (affected FYPO:0000640, FYPO:0003217, FYPO:0005315)

So heterochromatin assembly OR maintenance OR CENP-A containing chromatin assembly or maintenance
will cover it.
And yes, we can call the phenotypes
chromatin silencing at centromere central core
Sorry about the to  and fro-ing.  It's taken me a while to get my head around this. In fact I've been avoiding it for years......

Well, my share of the to-and-fro is probably at least partly because I still don't really have my head round it! So I ask what looks like a simple question that turns out not to be ...
I'll run with this and hope we don't end up wanting to change it back yet again somewhere along the line.

OK, basically done
edit file: 1406da4f08419332f5edf314d3b32c69f3d7202f
release: e78a27623827f37533246f6b61131aff7b85e8ed


"Group By" option in listview

In MS File Explorer you have an option to group files by the columns shown in listview. Its really handy when I want to group files that are older or by size or by type. I miss this feature here.
And same with the drives on the left side. Would be nice to group them too so Network drives are separated from USB drives and from internal drives.

Merging with #1874.


can not open converted vtu file in paraview

header
{"instances": ["PART-1-1"], "steps": [["Step-1", ["Step-1-frame-00", "Step-1-frame-01", "Step-1-frame-02", "Step-1-frame-03", "Step-1-frame-04", "Step-1-frame-05", "Step-1-frame-06", "Step-1-frame-07", "Step-1-frame-08", "Step-1-frame-09", "Step-1-frame-10"]]]}

convert
PS D:\POC\odb2vtk\python> abaqus.bat python .\odb2vtk.py --header 0 --instance "PART-1-1" --step "Step-1:10" --odbFile ..\..\POC_Model.odb
    writing field data
    writing PointData
    writing CellData
    writing cell connectivity, offsets, and types
Complete.
writing ..\..\POC_Model\Step-1_10.vtu
---<PHONE_NUMBER>7 seconds ---
PS D:\POC\odb2vtk\python>

paraview

this odb model i can not upload to you, sorry.
can you @YangShen398  give me some advice?

Hi chenray844
can you upload the vtu file?
Thanks,
Yang

thanks for quickly reply, I can not upload this vtu file. sorry.

Are familiar with vtu format? what I would do is to manually edit the vtu file to narrow down the problem.

You can remove all the field data which leaves the vtu file having only the mesh. See if you can open it in ParaView without any issue.
Now that you have correct mesh. You can manually remove specific field data to see which one is giving you the problem.

either way, this means the code is not robust enough to convert your odb file.

Another quick way to do is to change the source code.
You can comment out
Line  up to line
The code does not output any field data anymore. You can run the script again and open the vtu file in paraview to make sure there is nothing wrong with the mesh conversion.

thanks, i will try it.
:+1:

Another quick way to do is to change the source code.
You can comment out Line  up to line
The code does not output any field data anymore. You can run the script again and open the vtu file in paraview to make sure there is nothing wrong with the mesh conversion.

the mesh conversion is right.
I also tried odb in  https://github.com/Liujie-SYSU/odb2vtk/tree/master/Samples,and the conversions are all right.

You need to find out which field output is causing the issue. What field outputs were you requesting in the ODB file?

@YangShen398
I found this paraview issue about parser large vtu file failed on windows.
thanks.

Thanks for sharing. Good to know that the issue is not on the converter side. May I ask what is the size of your final VTU file? Have you tried to open it on Linux platform?

the size of vtu is 3.8GB, and can be opened in ubuntu platform. 😄


support org api

https://developer.okta.com/docs/reference/api/org/

@fawaf Thanks for posting this issue. We'll need to plan this and update openapi spec first (all Okta SDKs are generated according to common openapi spec). I'll post here when I get more details.

@fawaf I've got more details: we will add support for org api soon. I'll post here when it is ready.

@fawaf SDK v2.2.0 has been released. ORG API is supported now, except org logo uploading. This operation needs some extra codebase changes. You can track progress here: https://github.com/okta/okta-sdk-python/pull/244

@fawaf SDK v2.3.0 has been released. ORG API is fully supported, I'm closing this issue as resolved. Feel free to reopen this issue or create a new one if your problem exists still.


Create a PR template

@colehart @hjawad22 what do you think?
Repo should be already cloned

git pull
git checkout develop
git checkout -b
git status
git add
git status
git commit -m ”added module css and applied css changes”
git push -u origin fix-header
(Go to GitHub  link for pull request)
git fetch upstream (if there was an error)

@DanielekPark Thanks Daniel this looks like a good start! I also have used this one in the past and it has been helpful. Maybe we can make a new one with a conbination of the two?
Types of changes made?

[ ]  testing
[ ] documentation
[ ] functionality

What does this PR do?

[ ] Adds functionality

[ ] Updates JS for

[ ] Fixes bug for

Relevant Tickets?

[ ] Finishes iteration or ticket for

Questions/Comments/Relevant Screenshots?

@hjawad22 sure that looks good


SaveFileDialog issue?

I'm trying to open a save-dialog. In the update-function I call:
| SaveButton -> state,

        let dialog = SaveFileDialog () in

        dialog.Title <- "Save file" ;

        dialog.DefaultExtension <- ".json" ;

        dialog.Directory <- Environment.GetFolderPath(Environment.SpecialFolder.MyDocuments) ;

        let showDialog window = dialog.ShowAsync(window) |> Async.AwaitTask in

        Cmd.OfAsync.perform showDialog window AfterSaveFileSelected

| AfterSaveFileSelected path -> printfn "%s" path ; state, Cmd.none // just to check if the filepath is correctly selected

As I try to open the dialog, I get an odd error message though. Seems like something to do with AppKit. Is this a Mac-issue? Is there something I'm doing wrong?
Error message:
-[NSSavePanel _initBridgeAndStuff] caught non-fatal NSInternalInconsistencyException 'assertion failed: '-[NSRemoteView _preSuperInit] has been invoked on a thread which is incompatible with AppKit; the problem is likely in a much shallower frame in the backtrace' in -[NSRemoteView _preSuperInit] on line 2372 of file /System/Volumes/Data/SWE/macOS/BuildRoots/5b2e67f8af/Library/Caches/com.apple.xbs/Sources/ViewBridge/ViewBridge-638.3/NSRemoteView.m' with backtrace ( ......

Run the code above on the UI thread using the Dispatcher.

I see. I don't know how to use the dispatcher, really. Is there some simple example?
Ps. I tried to run the initial code on a Windows pc, and it works there. So seems like a Mac-related issue.

I see. I don't know how to use the dispatcher, really. Is there some simple example?

See #128


Does vue-strap support Vuejs version 2.x.x?

Hi,
I am new to vue-strap, does it support Vuejs version 2.x.x? Thanks!

I'd suggest checking out the v2 branch.
You can generally use the v2 repo#branch by changing "vue-strap": "yuche/vue-strap", in your packages.json file to use the specified branch "vue-strap": "yuche/vue-strap#v2",

Thanks so much! Is that branch stable enough to use in the production env? Thanks again!

There's an existing issue about supporting vuejs 2.x.x: #435


Avoid tokens weird type checking/eliding

Describe your changes here.
Relates to https://github.com/primer/react/pull/2760
In this pr we omitted onResize and onResizeCapture as typescript was causing these to elide a mandator unknown type, which was super confusing.
I believe this was caused by the fact that these props aren't equally defined across all polymorphic types, and forwardRef swallows polymorphism, making things wonky.
I've re-typed these components using the polymorphic helper, and added some type tests to help validate they don't regress.  I think we would be well served extending our type tests further to cover most/all components, as I'm sure others are limited in the same or similar ways
Screenshots
Please provide before/after screenshots for any visual changes
Merge checklist

[x] Added/updated tests
[ ] Added/updated documentation
[ ] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge

Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.

I believe this was caused by the fact that these props aren't equally defined across all polymorphic types, and forwardRef swallows polymorphism, making things wonky.

Would there be a good place to learn more about how forwardRef swallows polymorphism? (Or this concept more broadly). It was the first time I had seen the output of a type get inlined in such a way that information was lost and I would love to learn more about it if you have any suggestions 👀
For the type tests, is this something that should be a part of the testing requirements for components/props added or changed in a component? It doesn't really seem like there are other alternatives to guarantee that things are showing up, curious if there are other approaches that teams use or if this is kind of our best best moving forward to catch issues like this. Would love to hear your thoughts!

I believe this was caused by the fact that these props aren't equally defined across all polymorphic types, and forwardRef swallows polymorphism, making things wonky.

Would there be a good place to learn more about how forwardRef swallows polymorphism? (Or this concept more broadly). It was the first time I had seen the output of a type get inlined in such a way that information was lost and I would love to learn more about it if you have any suggestions 👀

I don't know of one offhand, but a quick search brings up things like
https://fettblog.eu/typescript-react-generic-forward-refs/
https://twitter.com/jaredpalmer/status/1217149616082296833?lang=en
the crux of the issue is that a HOC in a static context can't return a generic that infers from an internal generic which seem related.  Which is a mouthfull but this might be more easy to grok
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/0e64955901599be1e43a2e50c556d141a2b8fdd8/types/react/index.d.ts#L776-L781
the types for forwardRef don't return a component that's possible of generically defining something based on a certain prop, so it effectively 'swallows' up the as prop (which can't be inferred because it can't be defined)

For the type tests, is this something that should be a part of the testing requirements for components/props added or changed in a component? It doesn't really seem like there are other alternatives to guarantee that things are showing up, curious if there are other approaches that teams use or if this is kind of our best best moving forward to catch issues like this. Would love to hear your thoughts!

@mattcosta7 makes perfect sense, thanks so much!
@broccolinisoup I'm going to merge this is as the follow-up to the TODO from: https://github.com/primer/react/pull/2760 if that makes sense, let me know if it makes the release more complicated and I'd be happy to revert/add it back in after the release 👍


Refs #32567 - LiveServerTestCase fails when URL has special characters on Windows

Added a test in staticfiles_tests/test_liveserver.py. The test tries to access a URL with a colon (:) or pipe (|) in it. It fails on Windows, but not on Linux. This is likely related to the way Windows handles some characters in file / directory names.
I opened the PR even though I don't have a fix yet as suggested in the bugtracker.

Closing due to inactivity.


Der Fotokopierer steht in meinem Büro und wird von mir ausschließlich zu
beruflichen Zwecken verwendet.]

Reproduction URL
No response
Operating system
Linux
Typst version

[X] I am using the latest version of Typst

This is to be expected due to the adjustment of hyphenation costs^1. I honestly like the new result better here. Hyphenation do often reduce readability and I think it does in this case.

This is an intentional change. If you reduce the hyphenation cost you should be able to get the old hyphenation back
(I have not tried)

This is to be expected due to the adjustment of hyphenation costs^1. I honestly like the new result better here. Hyphenation does often reduce readability and I think it does in this case.

I'm mixed about it. In this case I'd consider the word spacing to be slightly too extreme.
Of course the ideal solution is font expansion, but typst does not support that yet.


Add authentication requirement for using LensProxy

Signed-off-by: Sebastian Malton<EMAIL_ADDRESS>

NOTE: This PR is not yet ready for review as I will need to also add HTTPS support since https://github.com/kubernetes/kubectl/issues/744 blocks using authentication of any sort over HTTP


Fast swipe bug [bug]

If i swipe super fast i can't leave introduction view. In your example you it works well. Maybe it's appear because i add MYBlurIntroView to "window" in app delegate?
MYBlurIntroductionView *introductionView = [[MYBlurIntroductionView alloc] initWithFrame:self.window.bounds];
[self.window addSubview:introductionView];

See video
https://www.dropbox.com/s/dkkeczdzcl9c28o/blurbug.mov?dl=0

Yes, i have got this bug too.

Same bug, it's a critical problem for use experience, any owner could give some clue?

I too have the same bug.. is there a fix yet?


Modernize python 2 code again

A subset of #2

No good stuff here?

Too many files at once...  I just opened #10 which should be easier to review.


fix: broken startup ui

Pull Request Test Coverage Report for Build 578871210

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 19.275%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app.js
0
1
0.0%

Totals

Change from base Build 578782039:
0.0%

Covered Lines:
2009

Relevant Lines:
10694

💛  - Coveralls


DotNetCore template should change the default configuration name to start with capital letter

See https://github.com/Microsoft/vsts-tasks/issues/6797#issuecomment-402867062 for more details.

Fix to this has been merged.


Prevent mutating original rows

What kind of change does this PR introduce? (check one with "x")

[x] Bugfix
[x] Feature

What is the current behavior? (You can also link to an open issue here)
Currently $$index is set on the original object you pass to rows, because it's set by reference, thus polluting the original data.
What is the new behavior?
Now it makes a clean copy that it can modify internally
Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[x] No

Other information:
The original data should never be touched by the table.

Relates to: https://github.com/swimlane/ngx-datatable/issues/610

Problem is now if you change a row's value via inline editing for example the original row is not updated.

@amcdnl hmm, then I think the inline editing should be updated to account for updating the cloned row?

The indexes need to be tracked separately.

Resolved :)


Install MSODBC with Ubuntu results in 404  Not Found

The installation of MSODBC as described on:
https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server?view=sql-server-2017#ubuntu17
is not working anymore, the path retrieved from the prod.list results in an 404  Not Found error.
please fix this
Input
curl https://packages.microsoft.com/keys/microsoft.asc | apt-key add -

#Ubuntu 18.04
curl https://packages.microsoft.com/config/ubuntu/18.04/prod.list > /etc/apt/sources.list.d/mssql-release.list

sudo apt-get update
sudo ACCEPT_EULA=Y apt-get install -y msodbcsql17 --fix-missing

Output
Get:1 https://packages.microsoft.com/ubuntu/18.04/prod bionic InRelease [4,003 B]
Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Get:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:5 https://packages.microsoft.com/ubuntu/18.04/prod bionic/main amd64 Packages [207 kB]
Hit:6 https://repos.azul.com/zulu/deb stable InRelease
Hit:7 http://security.ubuntu.com/ubuntu bionic-security InRelease
Fetched 286 kB in 1s (393 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
  libcap2-bin libpam-cap
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
  msodbcsql17
0 upgraded, 1 newly installed, 0 to remove and 52 not upgraded.
Need to get 745 kB of archives.
After this operation, 0 B of additional disk space will be used.
Err:1 https://packages.microsoft.com/ubuntu/18.04/prod bionic/main amd64 msodbcsql17 amd64 <IP_ADDRESS>-1
  404  Not Found [IP: <IP_ADDRESS> 443]
E: Failed to fetch https://packages.microsoft.com/ubuntu/18.04/prod/pool/main/m/msodbcsql17/msodbcsql17_<IP_ADDRESS>-1_amd64.deb  404  Not Found [IP: <IP_ADDRESS> 443]
E: Internal Error, ordering was unable to handle the media swap

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

ID: 0fc3da20-7ab2-d20f-4d29-4664d3183b57
Version Independent ID: 986d25d9-5d2e-5154-39ea-3b683faf2264
Content: Install the Microsoft ODBC driver for SQL Server (Linux) - ODBC Driver for SQL Server
Content Source: docs/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server.md
Product: sql
Technology: connectivity
GitHub Login: @David-Engel
Microsoft Alias: v-daenge

same here :(

+1

+1

seems to be up and running again so closing this issue.


Downgrading typescript version

Summary
Downgrading typescript version, this is needed until we can figure out how to
make "declaration": true works in the last version of typescript.

This doesn't fix the problem properly.


Ignore tags on the SSH security group

In cases where an outside process tags the security group regarding
allowing SSH access from the Internet, these tags should be ignored and
left in place.

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


python package

Hi, I found xdf for python is extremely useful and I think it should be packaged so that you don't need to copy xdf.py to all the project directories.
TODO:

I made a stub setup.py so feel free to edit it if you merge (currently I added @cboulay as the author)
license should be specified in setup.py
Current folder structure is

xdf/
  Matlab/
  pyxdf/
    pyxdf/
      __init__.py

but maybe pip cannot find it if it's registered on PyPI? Should it be
xdf/
  Matlab/
  xdf/
    __init__.py

instead? Or should a separate repository be created?
Thanks,
Naoto

Naoto,
I have no experience packaging python modules, so I'll leave it to you.
You can always create your own branch of the repository, do whatever you
want, than issue a pull request at which point we can merge your work
into the trunk.
Also, I urge you to incorporate your xdf_to_lsl stream tool!
Cheers,
David
On 6/14/17 12:13 PM, Naoto HIÉDA wrote:

Hi, I found xdf for python is extremely useful and I think it should
be packaged so that you don't need to copy xdf.py to all the project
directories.
TODO:

I made a stub setup.py so feel free to edit it if you merge
(currently I added @cboulay https://github.com/cboulay as the
author)
license should be specified in setup.py
Current folder structure is

|xdf/ Matlab/ pyxdf/ pyxdf/ init.py |
but maybe pip cannot find it if it's registered on PyPI? Should it be
|xdf/ Matlab/ xdf/ init.py |
instead? Or should a separate repository be created?
Thanks,
Naoto

    You can view, comment on, or merge this pull request online at:

https://github.com/sccn/xdf/pull/10
    Commit Summary

python package
File Changes

R pyxdf/pyxdf/init.py
https://github.com/sccn/xdf/pull/10/files#diff-0 (0)

A pyxdf/setup.py
https://github.com/sccn/xdf/pull/10/files#diff-1 (11)
Patch Links:

https://github.com/sccn/xdf/pull/10.patch

https://github.com/sccn/xdf/pull/10.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sccn/xdf/pull/10, or mute the thread
https://github.com/notifications/unsubscribe-auth/ADch7gaYqfr9Df7EoXVcFJrkb1C1oNHrks5sD7JLgaJpZM4N5q9k.

Sorry I haven't taken a look at this yet. I will try to get to it soon.

another possibility may be to integrate this in pylsl. what do you think @chkothe ?

I'd prefer keeping this in a separate pyxdf package. I can help creating a package for PyPI, but before we do that we should all agree that the package is functional. If you want to call the package pyxdf then the first folder structure would be correct. For PyPI, we don't need all the other stuff, so this should suffice:
pyxdf/
    __init__.py
    xdf.py

@cbrnr thanks about that. So far I'm testing it with Python 3.6 on Windows 10 and working fine - at least for single stream recorded by LabRecorder. I haven't tested multiple streams and markers.
Although I don't think I will be largely involved in dev of (py)xdf, I'm making a tool to playback xdf file and stream it to LSL:
https://github.com/sccn/labstreaminglayer/pull/201
The aim is to extend it to multiple streams and setting the playback position based on markers. I think this will be a good testbed to verify (py)xdf.

Any news on this front?

as @cbrnr says probably it's a good idea to make another repository for pyxdf instead of changing the structure of this repo

I don't think that's what @cbrnr was saying. It doesn't need to be another repository, it just needs to be an isolated package.
I think the reason there hasn't been any movement on this is that we know that pyxdf is inefficient and hasn't been tested very thoroughly. I think we'd like to make it a little more robust before it goes on pypi, but no one has the time to do that.

ok. in my opinion if pyxdf is published on pypi then it may get more feedback, too.

I agree with @micuat. For the package to be on pypi it doesn't have to be perfect ... but it could spark wider use and with that more feedback.
@cboulay, could you specify what you mean by

we'd like to make it a little more robust

Furthermore, I think that it would be great if the author/person in charge could upload a LICENSE.txt so that this is openly specified.

License added.
I think that at a minimum we should have some unittests that load and inspect a few different very small data files.
Also, for those interested, please take a look at python-neo and see if you would prefer that xdf support be added there instead of having a separate python library.

I think that adding XDF support to NEO would be a better idea than having a separate XDF package. However, it will probably involve even more work than getting the simple pyxdf package to pypi.
Until someone has some time to first add some unit tests and then think about adding pyxdf to NEO, I propose to merge this PR by @micuat so that the pyxdf package can at least be installed with:
pip install git+https://github.com/sccn/xdf/tree/master/Python.git

Since I don't use XDF in my workflow, I don't have the time to contribute to this package at the moment. However, I'd prefer a pyxdf package in this repository since integrating it into Neo is definitely a lot more work. Therefore, I suggest to rename the Python folder to pyxdf and add an empty __init__.py.

@sappelhoff thanks a lot for the comments. It would be great if you could make a new pull request so you can make changes directly.

@micuat, sure I can do that.
@chkothe, what is your take on who should be listed as author and email in the setup.py?

I don't know who actually wrote this module (I sem to remember it was cboulay?) though I guess it is in the git history. I'm pretty sure it wasn't Christian or Alejandro.

+1 @dmedine and @cbrnr ... sounds great

Now part of #21


Can you update the code for introducing?

I found the code in  READ.ME is out of date. Some class was renamed such as ListRule and some class' function was changed such as ShadowsocksAdapterFactory.
Because there are so few of documents about this project, the code for introducing is very important for me or somone else who didn't know this project very much.

I design this framework as something to help avoid reinventing the wheel, not as some black box just works.
You can take a look at the doc site here, https://zhuhaow.github.io/NEKit https://zhuhaow.github.io/NEKit. I think it should be up to date.
Sorry for any inconvenience. I updated the readme to point that out.

On 22 Nov 2017, at 22:02, starFelix<EMAIL_ADDRESS>wrote:
I found the code in READ.ME is out of date. Some class was renamed such as ListRule and some class' function was changed such as ShadowsocksAdapterFactory.
Because there are so few of documents about this project, the code for introducing is very important for me or somone else who didn't know this project very much.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/zhuhaow/NEKit/issues/130, or mute the thread https://github.com/notifications/unsubscribe-auth/ABOmLPRLbV5VRLXwOD01lFCLB-q2B7rTks5s5Cl1gaJpZM4Qnceg.

I know what you mean, but I think it's necessary for providing some code so that others can understand this project easier.


Support Stats() within compiled queries

Hopefully this is going to be rinse and repeat after @nieve 's work on Include() + compiled queries

Will be happy to take this, unless someone else has his eyes on it..?

Created a new PR from a different branch. All tests should be successful.


fix: no action_representation_module in CB constructor

There is an error in when trying to run benchmarks:
configs are defined the following way:
policy_learner_dict: Dict[str, Any] = {
    "name": "NeuralBandit",
    "method": NeuralBandit,
    "params": {
        "feature_dim": feature_dim + dim_actions,
        "hidden_dims": [64, 16],
        "learning_rate": 0.01,
        "batch_size": 128,
        "training_rounds": run_config["training_rounds"],
        "action_representation_module": BinaryActionTensorRepresentationModule(
            bits_num=dim_actions
        ),
    },
}

and then then the NeuralBandit object is created the following way:
policy_learner = policy_learner_dict["method"](
    **policy_learner_dict["params"]
)

However, neither ContextualBanditBase nor any of the classes that extend it take action_representation_module as constructor parameter.
In addition, I have added standard python .gitignore  with added exclusion of dataset/result paths for the benchmark

thanks for the notice.
we're pushing a modification that resolves it. should be available within a day.


grey/white transmog selling options

can u make choose whether uncollected grey gear should be excluded from selling for our character or maybe our alts or both?

@moody This issue is not fixed in v1.5.0, at least not fully. It only excludes unbound gear if your character can currently equip that particular item.
F.ex. on my Druid it will sell Cloth, Mail and Plate grey items, whereas on my Paladin it will not sell the Plate item.


(Byte) Array Support ?

Experiencing a failure when converting from a string value to a byte array. Not sure if I am doing something wrong, or if perhaps the intent is to register an extension for this use case (perhaps for an encoding selection?). Or perhaps there is no array support? Here's the implementation:
// Where type is a byte[], and value is a string
Object converted = TypeConverter.convert( type, value );

// Thrown
IllegalArgumentException: Could not find type conversion for type "class [B" (value = "1111111")

Nice library BTW. I have been building libraries for eons and for whatever reason, this one always ends up being a something that I shim up "for now". Thanks!
Monte

So, the answer appears to be that there is no built in support for arrays and we must implement it. I will try to submit a pull request for one implementation.


Add GigaChat API

Add new model to the library using API with chat templates. We use ast.literal_eval as GigaChat API has no access to tokenizer and chat template. We are open to any suggestions for improving the approach.

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

Hi @seldereyy!
I found your request really useful as we want to evaluate gigachat too.
But I didn't quite understand why you closed it, is there any issues with this request?

@annthehuman hi!
This is the actual one https://github.com/EleutherAI/lm-evaluation-harness/issues/1996
We will commit and fix some bugs soon


Log a hint if handle-generic-xml  doesn't find a record so that the user knows to configure "recordtagname"

Working on a LIDO document an unconfigured handle-generic-xml flux command doesn't yield anything.
This could somehow be configured to be logged ? -The user should be hinted to configure  (recordtagname="lido").
(problem surfaced in the SWIB23 Metafacture workshop)

Thinking about this, some thoughts surfaced:

If there would be logs they wouldn't be helpful for e.g. playground. One would have to throw an Exception (playground can display that) but it would be disputable to throw an exception only because (one) record in the stream didn't yield any data
So it may be better to improve the documentation, i.e. the flux-commands.md , to point out the importance  of the recordtagname, possibly noting the lido example
we also could provide Handlers of their own, like the CGXmlHandler, i.e. a LidoXmlHandler
we could implement LidoXmlHandler just wrapping GenericXmlHandler and setting the proper recordtagname as a convenient shortcut (no need to set a parameter when using GenericXmlHandler instead)
the playground could evaluate the flux and, by finding the usage of handle-generic-xml, printing a note in the Result window, like "If you see this text here after clicking process obviously the result was empty. As you use handle-generic-xml this may be caused by a wrong recordtagname . The default one is record, which couldn't be found in the data. Have a look at the flux-commands.md". Something like this.

WDYT @blackwinter @TobiasNx @fsteeg @maipet ?
I like the generic approach (2) by giving more examples ([onix](url), lido, maybe some more). And would like to see later (5) as a more dynamic help.

Your suggestion 2: Sound good to me! +1

Option 2) is certainly the least intrusive :+1:

+1 for 2)

+1 for opt 2


[Runtime] Introduce runtime module property

Currently, we only classify whether the runtime module is DSO-exportable.
This PR further classifies each runtime module into the properties as follows:

kBinarySerializable: we can serialize the module to the stream of bytes. CUDA/OpenCL/JSON runtime are representative examples.
kRunnable: we can run the module directly. LLVM/CUDA/JSON runtime, executors (e.g, virtual machine) runtimes are runnable. Non-runnable modules, such as CSourceModule, requires a few extra steps (e.g,. compilation, link) to make it runnable.
kBinaryExportable: when the module is kBinarySerializable and kRunnable, we consider this module as binary exportable. A binary exportable module can be integrated into final runtime artifact by being serialized as data into the artifact, then deserialzied at runtime. This class of modules must implement SaveToBinary, and have a matching deserializer registered as runtime.module.loadbinary_<type_key>.
kDSOExportable: we can export the module as DSO. A DSO exportable module (e.g., a CSourceModuleNode of type_key 'c') can be incorporated into the final runtime artifact (ie shared library) by compilation and/or linking using the external compiler (llvm, nvcc, etc). DSO exportable modules must implement SaveToFile.

Please note that kDSOExportable is a mutual exclusive property with kBinaryExportable.
To represent each category, the following status bits are defined.
namespace property {
/*! \brief Binary serializable runtime module */
constexpr const uint8_t kBinarySerializable = 0b001;
/*! \brief Runnable runtime module */
constexpr const uint8_t kRunnable = 0b010;
/*! \brief DSO exportable runtime module */
constexpr const uint8_t kDSOExportable = 0b100;
/*! \brief Binary exportable runtime module */
constexpr const uint8_t kBinaryExportable = kBinarySerializable | kRunnable;
};  // namespace property

Edit based on the review
This PR further classifies each runtime module into the properties as follows:

kBinarySerializable: we can serialize the module to the stream of bytes. CUDA/OpenCL/JSON runtime are representative examples. A binary exportable module can be integrated into final runtime artifact by being serialized as data into the artifact, then deserialized at runtime. This class of modules must implement SaveToBinary, and have a matching deserializer registered as runtime.module.loadbinary_<type_key>.
kRunnable: we can run the module directly. LLVM/CUDA/JSON runtime, executors (e.g, virtual machine) runtimes are runnable. Non-runnable modules, such as CSourceModule, requires a few extra steps (e.g,. compilation, link) to make it runnable.
kDSOExportable: we can export the module as DSO. A DSO exportable module (e.g., a CSourceModuleNode of type_key 'c') can be incorporated into the final runtime artifact (ie shared library) by compilation and/or linking using the external compiler (llvm, nvcc, etc). DSO-exportable modules must implement SaveToFile. In general, DSO exportable modules are not runnable unless there is a special support like JIT for LLVMModule.

To represent each category, the following status bits are defined.
enum ModulePropertyMask : int {
  kBinarySerializable = 0b001,
  kRunnable = 0b010,
  kDSOExportable = 0b100
};

cc. @tqchen

Thank you, @echuraev for the review. As @tqchen pointed out, this PR changes the way we achieve the same functionality but with a more refined manner. This PR was motivated by the discussion in my outstanding PR https://github.com/apache/tvm/pull/14337 about roundtrip-abilty and with this change, we can offer more systematic error message when we cannot guarantee this.

This is a really comprehensive summary and I believe it will generally be quite useful to anyone (including me) who wants to understand runtime.Module in depth. @sunggg @tqchen shall we put it somewhere in the official tutorial?

@sunggg Thank you for your reply! It is a nice summary and the reason why we did it starts to be much clearer for me. I'm ok with current tests but agree with @junrushao that creating some documentation might be very useful.

@junrushao @echuraev Thank you for the suggestion. Addition to the official tutorial also sounds great to me.
By reflecting @tqchen's suggestion, I also added some unit tests and assertion in export_library.
Hope this helps!

@tvm-bot rerun


Add simple robots.txt option for discouraging AI bots

Thanks to them having a feed and me starting to rediscover feedreaders, Ars Technica have alerted me that it's now possible to block ChatGPT using robots.txt.
Given how important this is to many site owners, add an option to put this directive into a robots.txt file published from a container instance. I already have ROBOTS_DISALLOW, a simple boolean. Need to keep supporting this, while extending it for cases like this. I think there is a danger that the number of possible commonly sought-after boilerplate robots.txt files could extend beyond what will scale. For now, I think provide a small number of them and also provide instructions on how to do this by simply bind mounting a custom robots file.
The directive for ChatGPT API bots is:
User-agent: GPTBot
Disallow: /

I can see this needing to be extended. To future-proof, file should be named generically like ai-bots or similar.

A month or two back (ChatGPT doesn't seem to show timestamps on threads), I asked ChatGPT this question with this exact goal. I am going to assume it's OK to paste here:

me: which user-agent string does chatgpt use when crawling websites?

gpt: As an AI language model, ChatGPT does not have a direct browsing capability or the ability to crawl websites. It doesn't have a specific user-agent string associated with it. Instead, ChatGPT is designed to generate text-based responses and provide information based on its pre-existing knowledge. If you have any questions or need assistance with a particular topic, feel free to ask!

I drilled a little further and nothing came of it.

Added Google-Extended in bfe5f55.

Improvement tweaks added in 7f00962, 5859622, and 5f133f3 (docs)


created_at not added when records are created using update/upsert

I think this option should be set by default:
https://docs.mongodb.com/manual/reference/operator/update/setOnInsert/#up._S_setOnInsert
Profile::whereId(1)->update(['name' => 'joe'],['upsert' => true]);
This produces the updated_at but is missing created_at.

+1

Why issue is close?

@quando12 i'm not sure that it's expected behavior

What is the alternative here, use create() if you cannot first find()?  upsert (by definition) would create a new document if one could not be found.  This (in my opinion) should cause the created_at field to be included automatically.

+1


Better travis.yml

Codecov Report

Merging #101 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #101   +/-   ##
=========================================
  Coverage     95.97%   95.97%
  Complexity      203      203
=========================================
  Files            15       15
  Lines           670      670
  Branches        131      131
=========================================
  Hits            643      643
  Misses           11       11
  Partials         16       16

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 d956614...1259df0. Read the comment docs.


quotation mistake

Forgot to include a quotation in one of the generate-id tasks.

/cc bkatyl

/cc zmarano

/lgtm


[* DateTime V2] Refactor Timex parsing code to use Spans instead of Strings

Replace String manipulation operations in TImexUtility with more efficient Span manipulation operations.
For example:
var subStr = inputStr.Substring(start, length);      -->     var subSpan = inputSpan.Slice(start, length);

@tellarin, I left a comment in #2950 about this.
It seems that parsing of spans is not supported in .NET Framework, so the span needs to be converted back to string when passing it to int.TryParse.
Should we still proceed? Or do you have other suggestions?


Failed to load resource with a status of 403

Getting this error on several websites:

1, Failed to load resource: the server responded with a status of 403 (HTTP/2.0 403)    https://mywebsite/images/person1.jpg
2, Failed to load resource: the server responded with a status of 403 (HTTP/2.0 403)    https://mywebsite/images/person2.jpg
3, Failed to load resource: the server responded with a status of 403 (HTTP/2.0 403)    https://mywebsite/js/jquery.min.map

I checked my /static/images/ and person1.jpg & person2.jpg are there, don't know why, and person3.jpg works fine.
Above first two errors happen in production environment, $ hugo server works fine too.
But no jquery.min.map in /static/js/, maybe it's a type error, just don't know which file exists.

Ok, I resolved the first two problems by changing pictures' size into around 20k.
The third problem hasn't worked out yet.


refactor(test): use const/let instead of var

:pushpin: Commit 96c63d5 has been approved by saneyuki

@homu r+

:hourglass: Testing commit 96c63d5 with merge e6d0051...

:sunny: Test successful - status


HDXDSYS-896 fix HND population filenames

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1352

Relevant Lines:
1455

💛  - Coveralls


device '(null)' not found

Always get that error in java console

You mean, when running, it can not find any device (emulated)?

io.selendroid.standalone.server.model.SelendroidStandaloneDriver getsupportedDevices Error occurred when buildung supported device info: null
Same here, I get an error connection a real or virtual device on it (0.17)

If I remove the device, I first get a releasing device notify (works), but then device is disconnect and removing ;-) - seems to be bug or loop ....

This was due to the device using a newer API version than the code could handle.  This should be fixed by #1141, please get the latest code from master and try again.


Broken slides if combining background image with state updates

Hey there 👋🏻
i found some bug i wasn't quite able to debug yet.
Anytime i combine state updates with background-images the first slide loses its background-image.
(Funnily enough if i swap the body and state update statement the first slide works again, but there is now a new, empty slide at the end).
I experienced this behaviour on both typst 0.8.0 as well as 0.9.0.
Even though i don't know what exactly is causing, i created a minimal example for reproduction:
#import "@preview/polylux:0.3.1": *

// definition
#let short_title_state = state("short_title", "")

#let simple-theme(aspect-ratio: "16-9", short-title: "", body) = {
  set page(
    paper: "presentation-" + aspect-ratio,
    margin: 2em,
    header: none,
    footer: none,
  )

  // TODO: play with these to break
  short_title_state.update(short-title)
  body
}

#let title-slide(
  title: "Title",
) = {
  let background-color = blue
  let background-img = image("./minimal.jpg")
  set page(background: {
    set image(fit: "stretch", width: 100%, height: 100%)
    background-img
  }, margin: 1em)
  set text(fill: white, font: "Inria Sans", size: 40pt)
  logic.polylux-slide(text(title))
}

// actual document
#show: simple-theme.with(short-title: "Hello world")

// TODO: add any number of slides here
#title-slide()

Also if you put the update statement above the set page rule, that rule will have no effect.


Snippets - Placeholder-Transform for 2nd (or further) variables.

VSCode Version: 1.47.1
OS Version: Windows_NT x64 10.0.18363

Steps to Reproduce:

Create a new snippet:

"bonjourSnippet": {
        "prefix": "bonjourSnippet",
        "body": "$1 ${1/(.*)/${1:/capitalize}/} $2 ${2/(.*)/${2:/capitalize}/}"
},

Launch the new snippet in any code.
Type zxcv
Press tab once. The first variable will get capitalized.
Type abcd.
Press tab again. The second variable first entry will be registred, but the second entry with the transformation is being erased somehow.

Expected output:
zxcv Zxcv abcd Abcd

Real output:
zxcv Zxcv abcd

Does this issue occur when all extensions are disabled?: Yes
Thanks.

Use this as the body:
"body": "$1 ${1/(.*)/${1:/capitalize}/} $2 ${2/(.*)/${1:/capitalize}/}"
In the replace section of the transform the ${n}'s , as in /${2:/capitalize}/ refer to capture groups, not to your $2 tabstop.  So you want $1 in the replace to refer to your first (and only) capture group.
Your code replaces all of the second tabstop with capture group 2 (capitalized) which is nothing since you didn't have a capture group 2.

Use this as the body:
"body": "$1 ${1/(.*)/${1:/capitalize}/} $2 ${2/(.*)/${1:/capitalize}/}"
In the replace section of the transform the ${n}'s , as in /${2:/capitalize}/ refer to capture groups, not to your $2 tabstop. So you want $1 in the replace to refer to your first (and only) capture group.
Your code replaces all of the second tabstop with capture group 2 (capitalized) which is nothing since you didn't have a capture group 2.

Ah, my bad. Wonderful remark.
Thanks.


Beautify README.md

Hey-hey,
I used structure from official builtin drivers to make readme more readable and similar as official driver (e.g. https://docs.docker.com/machine/drivers/vm-fusion/).
I added available driver options too.

@frapposelli, any chance you take a look on this pr? thanks.


add perf context for write wal and memtable

Signed-off-by: Little-Wallace<EMAIL_ADDRESS>
What have you changed?
add perf context for rocksdb write.
What is the type of the changes?

Misc (other changes)

How is the PR tested?

No code

Does this PR affect documentation (docs) or should it be mentioned in the release notes?

Does this PR affect tidb-ansible?

/release make dist_release

/release make dist_release

/release make dist_release

/release make dist_release

@Little-Wallace Are we still going to add the perf context for write?


Adding the KmlNodeVisibility and KmlNetworkLinks samples to the KML BRANCH.

Adding the KmlNodeVisibility and KmlNetworkLinks samples to the KML BRANCH (aka kml-samples)

@nCastle1 Could you please to a code review to include the proposed KmlNodeVisibility and KmlNetworkLinks samples into the KML BRANCK (aka kml-samples)? This way I can close out the KML samples in my personal repos. Thanks, -don


Disable logging in xclim.ensembles module?

Generic Issue
When importing clisops.subset.core and xclim.ensembles the logging output in the xclim.ensembles is somehow always sent to the console, or worse, to the jupyter notebook output window.
@Zeitsperre has been digging into this (see https://github.com/roocs/clisops/pull/216) but I am wondering just how critical it is to have a logger at all?
Notes - this seems to be the only submodule where a logger is used and as far as I can tell and only keeps track of 1) whether matplotlib is installed or not (for ensemble reduction graphs) or 2) which simulation is being accessed in the loop for the ensemble creation.
Code of Conduct

[X] #1040

Ok to scrap logging.

I'm OK as well for commenting the existing calls out, but this would be a good opportunity to drop-in loguru in its stead.

Ok to scrap clisops.


Changed readme

I added my demo app to this and a few other small edits to the documentation. I hope it's not too obtrusive.

@yifeiwu I would only suggest you squash your commits into 1. Since you are updating 1 file, it will result in a cleaner commit history for this repo

@yifeiwu as @onebree noted this gem supports multiple versions of Rails.  This was the reason for the name change from rails3-jquery-autocomplete to rails-jquery-autocomplete to help make it clearer that this is one gem intended for current and future versions of Rails.  The references in the README to instructions related to Rails 3 should not be removed until the gem no longer supports Rails 3.  At such a time that I decide (out of necessity) to no longer support feature changes for Rails 3 then I would created a tag or possible a permanent branch where people can still see the documentation for the Rails 3 version that may still need it.

@yifeiwu To add to that though; I did indicate in the README.md to continue using the old gem for Rails 3. Originally I was planning to break compatibility with Rails 3 earlier, but have since decided it isn't necessary yet.  I will update the README to better reflect this.

Fair enough, thanks for the clarification. I haven't tested this on Rails 3 and I didn't know if people would be better off using the older branch.

@yifeiwu As long as the Rails 3 branch is kept (relatively) up-to-date, then a separate branch is good. You can define a certain branch in your Gemfile. That way, master will always relate to the latest support rails version.
The Rails project actually has a branch for every stable release. It allows you to deploy 2 versions of something, rather than 1 one-size-fits-all (with errors) gem, or 2 gems in separate repos each.


Xcode 8.2.1

貌似 tun2socks 不支持swift 3.0.2 ?

错误写的这么清楚了，自己编译

Use carthage update --no-use-binaries --platform mac,ios to install all frameworks. Do not use pre-compiled binaries since some of them might be buggy.


cmd/compile: for-loops cannot be inlined

Using go devel +ed4a27a
Currently, functions with for-loops are not inline-able, would be nice if they did. Not long ago, I used a non-idiomatic goto in order to cheat around the inliner.
@dr2chase

For reference, the easy part (inlining for loops with no range and no continue/break)
inlines 924 additional calls in go install std and it gives mixed results on the go1 benchmarks
name                     old time/op    new time/op    delta
BinaryTree17-4              3.00s ± 3%     2.96s ± 4%     ~             (p=0.548 n=5+5)
Fannkuch11-4                2.29s ± 0%     2.29s ± 0%     ~             (p=0.056 n=5+5)
FmtFprintfEmpty-4          50.4ns ± 0%    50.7ns ± 2%     ~             (p=0.556 n=4+5)
FmtFprintfString-4          134ns ± 0%     134ns ± 0%     ~     (all samples are equal)
FmtFprintfInt-4             133ns ± 0%     133ns ± 0%     ~     (all samples are equal)
FmtFprintfIntInt-4          201ns ± 0%     198ns ± 0%     ~             (p=0.079 n=4+5)
FmtFprintfPrefixedInt-4     201ns ± 0%     197ns ± 0%   -1.79%          (p=0.000 n=5+4)
FmtFprintfFloat-4           291ns ± 2%     284ns ± 1%   -2.20%          (p=0.040 n=5+5)
FmtManyArgs-4               845ns ± 0%     841ns ± 1%     ~             (p=0.056 n=5+5)
GobDecode-4                7.81ms ± 1%    7.90ms ± 1%   +1.22%          (p=0.008 n=5+5)
GobEncode-4                6.55ms ± 1%    6.27ms ± 0%   -4.24%          (p=0.008 n=5+5)
Gzip-4                      268ms ± 0%     269ms ± 1%     ~             (p=0.690 n=5+5)
Gunzip-4                   36.8ms ± 0%    36.6ms ± 0%   -0.60%          (p=0.008 n=5+5)
HTTPClientServer-4         58.5µs ± 1%    61.8µs ± 0%   +5.65%          (p=0.008 n=5+5)
JSONEncode-4               17.2ms ± 1%    16.9ms ± 2%   -1.77%          (p=0.016 n=5+5)
JSONDecode-4               51.5ms ± 0%    52.1ms ± 1%   +1.16%          (p=0.008 n=5+5)
Mandelbrot200-4            4.77ms ± 0%    4.74ms ± 1%     ~             (p=0.151 n=5+5)
GoParse-4                  3.58ms ± 0%    3.54ms ± 1%   -1.10%          (p=0.016 n=5+5)
RegexpMatchEasy0_32-4      81.5ns ± 0%    82.1ns ± 0%   +0.74%          (p=0.016 n=4+5)
RegexpMatchEasy0_1K-4       199ns ± 2%     196ns ± 0%   -1.51%          (p=0.048 n=5+5)
RegexpMatchEasy1_32-4      81.2ns ± 1%    82.9ns ± 0%   +2.04%          (p=0.016 n=5+4)
RegexpMatchEasy1_1K-4       360ns ± 2%     356ns ± 1%     ~             (p=0.167 n=5+5)
RegexpMatchMedium_32-4      125ns ± 1%     124ns ± 0%     ~             (p=0.167 n=5+5)
RegexpMatchMedium_1K-4     38.8µs ± 1%    37.9µs ± 1%   -2.54%          (p=0.008 n=5+5)
RegexpMatchHard_32-4       1.98µs ± 0%    1.95µs ± 0%   -1.73%          (p=0.000 n=5+4)
RegexpMatchHard_1K-4       59.7µs ± 0%    58.6µs ± 0%   -1.85%          (p=0.016 n=4+5)
Revcomp-4                   437ms ± 0%     448ms ± 1%   +2.65%          (p=0.008 n=5+5)
Template-4                 62.8ms ± 0%    62.8ms ± 0%     ~             (p=0.841 n=5+5)
TimeParse-4                 328ns ± 0%     295ns ± 0%  -10.17%          (p=0.000 n=5+4)
TimeFormat-4                357ns ± 1%     349ns ± 3%     ~             (p=0.111 n=5+5)

Thanks for doing this; it was not exactly the results I was hoping for ;)
Are you aware of which loops in HTTPClientServer were inlined?

I will give it a look, I have a "adjust inlining parameters" CL up for review and I can try adding this one top see if it helps or hurts.

Turns out that inlining for loops tickles (at least) two other bugs, don't start the party yet.

In theory, yes.  I am doing some benchmarking right now to see what the overall impact is likely to be, with a very naive cost model (i.e., a default cost model).  It also requires change to some test output, or some noinline annotations.  I don't know if this qualifies for 1.12; though it is technically "an open bug" and the change is trivial.

Given that the fix is trivial and already somewhat-ready - any chance this could go in for 1.13? :)

When I tried to revive it, there was some weird failure that it caused.
It looks like inlining of a break or continue caused confusion, not sure how yet.
I just rebased and retested, the problem remains.
# go run run.go -- fixedbugs/issue15838.go
exit status 1
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x18b7362]

goroutine 1 [running]:
cmd/compile/internal/ssa.(*Block).AddEdgeTo(...)
	/Users/drchase/work/go/src/cmd/compile/internal/ssa/block.go:150
cmd/compile/internal/gc.(*state).stmt(0xc0000731e0, 0xc000426200)
	/Users/drchase/work/go/src/cmd/compile/internal/gc/ssa.go:1067 +0x10f2
cmd/compile/internal/gc.(*state).stmtList(0xc0000731e0, 0xc000071780)
	/Users/drchase/work/go/src/cmd/compile/internal/gc/ssa.go:758 +0x59
cmd/compile/internal/gc.(*state).stmt(0xc0000731e0, 0xc000426180)

Any chance for this being fixed sometime soon? I would love to undo my re-writes where I wrote my loops using goto instead of for, so they can be inlined.

Not in 1.13, maybe 1.14.

Go 1.14 is long gone, any chance this is getting fixed? I'm manually inlining functions because of this :/

@elichai goto still works, still not the best solution but may prevent bugs with a manual inline.

As of 30ba7980932dfb7ec6660ee929b4e1982256285f, it seems that for range loops are not inlineable.
For example:
func consumeWhitespace(b []byte) int {
	for i, c := range b {
		if !(c == ' ' || c == '\t' || c == '\r' || c == '\n') {
			return i
		}
	}
	return 0
}

cannot be inlined, but:
func consumeWhitespace(b []byte) int {
	for i := 0; i < len(b); i++ {
		if c := b[i]; !(c == ' ' || c == '\t' || c == '\r' || c == '\n') {
			return i
		}
	}
	return 0
}

is inlineable.
I'm not sure if this is deliberate or an oversight.

I'm not sure if this is deliberate or an oversight.

A little of both. Some range loops desugar into non-trivial code (e.g., ranging over maps), so I punted on this because I expected it would be too complex... but in retrospect, all of that complexity happens after inlining anyway, so it would probably be pretty trivial actually.
We should be able to easily address this for next release, along with labeled for loops.

Is this done? It looks all kinds of loops are capable of being inlined now.

Yes, thanks for pointing out.  This is done now for 1.18.  The missing cases (range loops and loops with labeled breaks/continues) are now inlineable, so all for loops are now inlineable.


Expose scrolling values & add scrollToPixel capabilities

Looks good to me now. Do you want to propose some method name changes?

Cool! Thank you for guiding me through all this.
The only proposition I have is changing the scrolling method names to be clearer.
There are the two methods now scrollX(deltaX) and scrollXToPixel(pixel) that can be misunderstood by a person who just starts using the library. If the first method's name was changed to scrollXBy(deltaX), I think that would be clearer overall. The 2nd method could be renamed to scrollXTo(pixel), but I don't like that for some reason. I'm not sure why.

Makes sense. Though I would keep and deprecate the old scrollX and scrollY methods to give users some transition period. I cannot currently think of better names.

Ok. I'll also update OrientationHelper's method to correspond to the method naming.
scrollHorizontally & scrollVertically will become scrollHorizontallyBy & scrollVerticallyBy, respectively.

Sounds good.

scrollX & scrollY are used in VirtualFlow's ScrollEventHandler, so I'll be updating those methods as well.

Good.
In OrientationHelper, you don't need to keep any deprecated methods, because OrientationHelper is not part of public API.
Only keep and deprecate the old methods on VirtualFlow. Also, please use the @deprecated Javadoc tag to explain the deprecation:
/**
 * ...
 * @deprecated use {@link #scrollXBy(double)} instead.
 */

Still learning how to use those tags properly. I guess that's the next thing I should study.
I've updated it.

Thanks, looks good. Merging.

Sweet! Thanks for guiding me through that.
To release this updated version, what else needs to be done? Now that the scrolling API is exposed, I can't expose it in RichTextFX until the new release, right?

That is basically correct, although in your IDE you can set your local Flowless project as a dependency to your local RichTextFX project if you want to start playing with it.
I will release a new minor version soon.

Ok, cool.
True. I get that I need to change gradle's dependency management to use the local directory, but I haven't yet researched that enough to know how to do that.
Even so, I've already written a few lines of code (commented until I can figure out the dependency thing).

At least Eclipse allows me to add projects as dependencies to other projects. No need to update gradle build script. (Of course that will only have effect in Eclipse, not on gradle builds.)

Version 0.4.6 published.

Now that I think about it, I've already done something like that in my IDE in the past. Hmm... not sure why that didn't come to mind...
Sweet!


config TestResultSetting ResultsDirectory does not take effect

Specify the result directory results_directory, which does not actually take effect。
    def __init__(self, server: str = '<IP_ADDRESS>', port: int = '8888', **kwargs):
        self.server = server
        self.port = port
        self.stc = stchttp.StcHttp(f'{self.server}:{self.port}')
        self.sid = self.stc.new_session('auto', 'auto')

    @property
    def _project(self):
        return self.stc.get('system1', 'children-project')

    def _config_result_setting(self, results_directory):
        # noinspection PyBroadException
        try:
            if setting := self.stc.get(self._project, 'children-TestResultSetting'):
                self.stc.config(
                    setting,
                    ResultsDirectory=str(results_directory),
                    SaveOutputFilesInCwd=True,
                    SaveResultsRelativeTo='CURRENT_WORKING_DIR',
                )
                self.stc.apply()
        except Exception:
            print('An exception occurs when config result config.')

Can you try with SaveOutputFilesInCwd set to False? That parameter, when set to True, overrides the ResultsDirectory and SaveResultsRelativeTo parameters and saves the results into the current working directory.

Can you try with SaveOutputFilesInCwd set to False? That parameter, when set to True, overrides the ResultsDirectory and SaveResultsRelativeTo parameters and saves the results into the current working directory.

I have tried to modify the SaveOutputFilesInCwd parameter to False, but it still does not work

Ok, can you provide some information on the environment? Is this using the stcweb backend on Windows? Is this running against a labserver?

The TestResultSetting configuration controls where the results are saved respective to the location the session is running at.
If the session is local and on Windows, I noticed some odd behavior with configuring TestResultSetting. A workaround I found is the following: self.stc.config(setting, ResultsDirectory=os.path.join(os.getcwd(), str(results_directory)))
If the session is on a remote windows server or labserver, it controls where the results are saved on the server rather than client side.
To download files to the client, StcHttp has a download and download_all method. It also has a files to list the files on the server. https://github.com/Spirent/py-stcrestclient/blob/master/examples/listfiles.py, https://github.com/Spirent/py-stcrestclient/blob/master/examples/downloadfile.py.

Ok, can you provide some information on the environment? Is this using the stcweb backend on Windows? Is this running against a labserver? Which version of STC is being used?

environment： OS Window7,
Is this running against a labserver?   --- is using the client with SpirentTestCenter's stcweb and Spirent TestCenter version is 5.34

self.stc.config(setting, ResultsDirectory=os.path.join(os.getcwd(), str(results_directory)))

Thank you for your reply. I will retest the code based on your changes.


mvn package error with "dyld: lazy symbol binding failed: Symbol not found: ____chkstk_darwin"

mvn package error on Mac OS X 10.15 with following details:
[INFO] --- exec-maven-plugin:1.6.0:exec (default) @ receiver-proto --- dyld: lazy symbol binding failed: Symbol not found: ____chkstk_darwin   Referenced from: /Users/michael/codes-wwdz-arch/service-goven/skywalking830/oap-server/server-receiver-plugin/receiver-proto/target/bin/flatc (which was built for Mac OS X 10.15)   Expected in: /usr/lib/libSystem.B.dylib
Could you give some help?Thank you very much.
Version: 8.3.0

Read FAQ, https://github.com/apache/skywalking/blob/master/docs/en/FAQ/How-to-build-with-mac-m1.md.
I guess you are using the latest MacBook(Pro)

Read FAQ, https://github.com/apache/skywalking/blob/master/docs/en/FAQ/How-to-build-with-mac-m1.md.
I guess you are using the latest MacBook(Pro)

Thank you wu-sheng very much.  I'm trying this solution.

Thank you wu-sheng very much.  I'm trying this solution.

@wu-sheng I also got this problem. addding -Dos.detected.classifier=osx-x86_64 does't work fine.
tag:v8.4.0
[INFO] os.detected.name: osx
[INFO] os.detected.arch: x86_64
[INFO] os.detected.version: 10.13
[INFO] os.detected.version.major: 10
[INFO] os.detected.version.minor: 13
[INFO] os.detected.classifier: osx-x86_64

If you are using M1 chip too, sorry, this is out of our control.

@wu-sheng I also got this problem. addding -Dos.detected.classifier=osx-x86_64 does't work fine.
tag:v8.4.0
[INFO] os.detected.name: osx
[INFO] os.detected.arch: x86_64
[INFO] os.detected.version: 10.13
[INFO] os.detected.version.major: 10
[INFO] os.detected.version.minor: 13
[INFO] os.detected.classifier: osx-x86_64

You're using MacOS version under 10.15, you have to compile flatc by yourself and use ./mvnw -Dfbs.compiler= to specify your local flatc compiler

@wu-sheng I also got this problem. addding -Dos.detected.classifier=osx-x86_64 does't work fine.
tag:v8.4.0
[INFO] os.detected.name: osx
[INFO] os.detected.arch: x86_64
[INFO] os.detected.version: 10.13
[INFO] os.detected.version.major: 10
[INFO] os.detected.version.minor: 13
[INFO] os.detected.classifier: osx-x86_64

You're using MacOS version under 10.15, you have to compile flatc by yourself and use ./mvnw -Dfbs.compiler= to specify your local flatc compiler

thanks, it is useful


Don't use remote theme

Using the remote-theme gem results in downloading the theme every time when building the page. With my current slow connection, that's super annoying.

Before:
$ jekyll build
--->8--- snip
      Generating...
      Remote Theme: Using theme mmistakes/minimal-mistakes
--->8--- snip
                    done in 76.503 seconds.
--->8--- snip

After:
$ jekyll build
--->8--- snip
      Generating...
--->8--- snip
                    done in 30.602 seconds.
--->8--- snip

Done in 4b604262475d4a581b3747cc47ea0cfc48e262b9


config.lock exceptions when multiple Cargo instances run concurrently

Problem
We are seeing issues when we have multiple Cargo instances running concurrently while sharing a ~/.cargo/registry. These builds are run in docker containers, but with a shared volume mounted to ~/.cargo/registry, with the intent that crate dependencies will be cached between jobs.
This works normally. However, when we run 2 jobs concurrently, we occasionally see issues.
Below shows three examples:
+ cargo build --release
error: failed to get `anyhow` as a dependency of package `ztunnel v0.0.0 (/home/prow/go/src/istio.io/ztunnel)`

Caused by:
  failed to initialize index git repository (in "/home/.cargo/registry/index/github.com-1ecc6299db9ec823")

Caused by:
  failed to lock file '/home/.cargo/registry/index/github.com-1ecc6299db9ec823/.git/config.lock' for writing: ; class=Os (2); code=Locked (-14)
make: *** [Makefile.core.mk:23: release] Error 101

+ cargo build --release
    Updating crates.io index
 Downloading crates ...
error: failed to download `petgraph v0.6.2`

Caused by:
  unable to get packages from source

Caused by:
  failed to unpack package `petgraph v0.6.2`

Caused by:
  failed to open `/home/.cargo/registry/src/github.com-1ecc6299db9ec823/petgraph-0.6.2/.cargo-ok`

Caused by:
  File exists (os error 17)
make: *** [Makefile.core.mk:23: release] Error 101

+ cargo build --release
error: failed to get `anyhow` as a dependency of package `ztunnel v0.0.0 (/home/prow/go/src/istio.io/ztunnel)`

Caused by:
  failed to initialize index git repository (in "/home/.cargo/registry/index/github.com-1ecc6299db9ec823")

Caused by:
  could not find repository from '/home/.cargo/registry/index/github.com-1ecc6299db9ec823/.git/'; class=Repository (6); code=NotFound (-3)
make: *** [Makefile.core.mk:23: release] Error 101

Steps
Its a bit hard to reliably reproduce. We do see this in our CI fairly often though. I can try to isolate this in a local environment if desired.
Possible Solution(s)
My expectation is that locks are either waited for, or at least a more clear error message around why its locked and what to do (I assume "don't run cargo concurrently" or similar would be the recommendation, if this is WAI?)
Notes
No response
Version
cargo 1.65.0 (4bc8f24d3 2022-10-20)
release: 1.65.0
commit-hash: 4bc8f24d3e899462e43621aab981f6383a370365
commit-date: 2022-10-20
host: x86_64-unknown-linux-gnu
libgit2: 1.5.0 (sys:0.15.0 vendored)
libcurl: 7.83.1-DEV (sys:0.4.55+curl-7.83.1 vendored ssl:OpenSSL/1.1.1q)
os: Ubuntu 22.04 (jammy) [64-bit]

Thanks for posting this.
Is the shared volume on NFS? I am asking because Cargo does have a coarse advisory file lock mechanism with the file ~/.cargo/.package-cache, based on flock on Unix and LockFileEx on Windows. It seems like flock doesn't work on your platform. Or maybe some other special settings on Docker shared volumes is causing this?

Its on a Kubernetes cluster with a hostPath mount. Its actually using containerd I guess, not Docker.
Volume settings:
            {
                "destination": "/home/.cargo/registry",
                "type": "bind",
                "source": "/var/lib/kubelet/pods/b0f72898-1ae9-40b0-8677-1887f3868a30/volume-subpaths/build-cache/build-tools/1",
                "options": [
                    "rbind",
                    "rprivate",
                    "rw"
                ]
            },

The OS is "COS" (a GCP container optimized OS).
As far as I know this should be ~equivalent to just a standard docker container and mount

Hmm… I see. I guess probably the file lock located at ~/.cargo/.package-cache is not shared, so the advisory lock mechanism won't work. A possible way to solve this might be fetching registry data and .crate file in a single container, and then using multiple containers to build concurrently. This will also save some bandwidth.

Thanks for the insight, that would certainly explain this!
Unfortunately our CI is pretty naive so we can't easily sequence containers. I had initially wanted to mount the full ~/.cargo, but the issue I ran into is that it then overrides ~/.cargo/bin so we lose a bunch of binaries from the container. I suppose we could just move everything out of ~/.cargo/bin though, as a workaround?
It doesn't look like there is a way to "mount ~/.cargo except ~/.cargo/bin" in docker.

Thanks a bunch! Super helpful and I think we have things working now. Sounds like this is WAI so I made the title more clear for future folks and will close


TypeError: utils.readString is not a function

Hi,
I'm getting this error, but only when running under jest, so I'm not sure if the problem is with this library or with jest itself.
TypeError: utils.readString is not a function
at Function.OpenSSH_Private.parse (....\node_modules\ssh2-streams\lib\keyParser.js:525:28)
at parseKey (....\node_modules\ssh2-streams\lib\keyParser.js:1440:32)
at new Server (....\node_modules\ssh2\lib\server.js:45:20)

I tried debug printing:
// avoid cyclic require by requiring on first use
console.error("utils before:", utils);
if (!utils)
  utils = require('./utils.js');
console.error("utils after:", utils);
var cipherName = utils.readString(data, 15, 'ascii');

And the result was:
utils before: undefined
utils after: {}

Okay, and now the problem went away, just as mysterious as it arrived.


Hardhat config

Proposed default HH config:
import "@nomicfoundation/hardhat-toolbox";
import "@zetachain/toolkit/tasks";
import * as dotenv from "dotenv";

import { getHardhatConfig } from "@zetachain/toolkit/client";
import { HardhatUserConfig } from "hardhat/config";

dotenv.config();

export const config: HardhatUserConfig = {
  ...getHardhatConfig({ accounts: [process.env.PRIVATE_KEY] }),
};

I thought about initializing a client as part of HH config, but then it becomes cumbersome to pass the client to HH tasks.

@lukema95 can you, please, take a look at this PR? Thanks!

@lukema95 can you, please, take a look at this PR? Thanks!

Everything looks good to me, I only noticed a minor problem with two lines of code redundancy.


[ANCHOR-790] Add deployment test profile

Description
This adds a deployment test profile that points the SEP-24 interactive UI to the reference UI so that the SEP-24 flows can be completed via the demo walllet.
Context
The deployments will be updated so that the SEP-24 interactive UI is deployed. This PR updates the docker-compose setup so it also works locally.
Testing

./gradlew test

Documentation
N/A
Known limitations
N/A

Please also add the test to extended-tests.

Please also add the test to extended-tests.

Which test are we referring to? This is different than the other test profiles in that integration tests are not meant to run against it.

The test can be added the workflow similar to https://github.com/lijamie98/java-stellar-anchor-sdk/blob/main/.github/workflows/sub_extended_tests.yml#L49