How to handle multiple tables from database source

Hi
Any tips to use this example in the real case we have multiple tables to synchronize from the database source ?
Thanks for your help
Benoit COLAS

Can someone please respond to this man?

There are two ways to handle multiple tables from a database source.
First, you can replicate these data pipelines for each table.
The other way is to set up AWS DMS to read CDC data from multiple tables (for more information, see AWS DMS - Wildcards in table mapping) and have AWS Glue Streaming Job upsert streaming CDC data into multiple Apache Iceberg tables.
AWS DMS allows you to get binlogs from many tables under a single database.
Then, if you have the Glue Streaming Job script repeat upserting for each source database table, you can handle multiple tables.


Tags consisting of real numbers not sorted correctly

Please check that this issue hasn't been reported before.

[X] I searched previous Bug Reports didn't find any similar reports.

Expected Behavior
When I add a real-number tag to a task such as #1.5, #2.1 #3.5 etc, the tasks should be sorted according to these numbers if the sort by tag 1 line is included in the codeblock.
The reason I care about this is that I really like the flexibility which real-numbered tags provide for prioritising tasks. Super valuable imo
Current behaviour
Tasks with real-numbered tags are mostly sorted correctly, but with several annoying exceptions where the sorting inexplicably fails. See attached screenshot for example

Codeblock:
```tasks
not done
filename includes test1111
sort by tag 1
has tags
limit to 10 tasks
```

Obsidian file contents:
- [ ] task #0.5
- [ ] task #1
- [ ] task #0
- [ ] task #1.2
- [ ] task #1.9
- [ ] task #1.5
- [ ] task #2
- [ ] task #2.1
- [ ] task #5
- [ ] task #10
- [ ] task #11.1
- [ ] task #1.001

Steps to reproduce
Paste above markdown into an obsidian note and observe incorrect sorting.
File name should be "test11111"
Which Operating Systems are you using?

[ ] Android
[ ] iPhone/iPad
[X] Linux
[ ] macOS
[ ] Windows

Obsidian Version
1.3.5
Tasks Plugin Version
4.0.0
Checks

[X] I have tried it with all other plugins disabled and the error still occurs

Possible solution
No response

Thank you for the clear bug report, for providing actual text example tasks to copy ... AND for including actual motivation for fixing the issue.
I believe that the current tag sorting code sorts the whole tag text, and so the leading # means that the rest of the text is not treated as a number.
I think the solution will be for the tag sorting code to remove (in memory only) the leading # before comparing two tags to decide which comes first.

By the way, your tags #1, #2 etc are not valid Obsidian tags.
https://help.obsidian.md/Editing+and+formatting/Tags#Tag+format

Tags must contain at least one non-numerical character. For example, #1984 isn't a valid tag, but #y1984 is.

We have a bug report to fix Tasks so that it honours the Obsidian definition of tags. (And in fact, we may use Obsidian code to do the actual tag detection...)
I am conscious that this would break your sorting.
This is the issue describing the problem: #929

Thx @claremacrae for your very fast reply. The solution you describe makes sense. And yes I am aware that the tags I am using are not valid Obsidian tags :/
Out of interest, can you think of any other approaches available for achieving a similar thing right now using Tasks?
I.e. the ability to prioritise tasks with arbitrary precision/divisibility.
many thx! :)

Thx @claremacrae for your very fast reply. The solution you describe makes sense. And yes I am aware that the tags I am using are not valid Obsidian tags :/

OK. The workaround would be to use #1.0 instead of #1 of course, as the former is a valid Obsidian tag.

Out of interest, can you think of any other approaches available for achieving a similar thing right now using Tasks? I.e. the ability to prioritise tasks with arbitrary precision/divisibility.

No I can't, and I hadn't thought of this one until you mentioned it!

@claremacrae When I create a tag consisting of #1.1 in Obsidian, it is not recognised by the Obsidian editor as a tag. I.e. it is not highlighted. Is this just me?

One strategy for solving both this issue and #929 is that even if a tag contains a number but also contains a string, the number component is sorted as a number rather than as a string. That way, I could use the tag #x1.1 (which is a valid Obsidian tag) instead of #1.1, and it would still be sorted correctly despite the tag not consisting solely of numbers.

I have also noticed some unusual behaviour where in some situations #1.5 is sorted above #1.1 and #1.1 sorted above #1 despite the sort order being from smallest to largest.

Markdown:
- [ ] L: When implementing Openzeppelin Defender, what functionalities or which data points do you think we would need alerts/monitor for (particularly for economic exploits)? List them out (Ex. oracle price deviations, etc.) #1.5
- [ ] implement liquidation stats calcs and logging #1.1
- [ ] implement funding rate/global state update in margin calcs code [issue 549](https://github.com/Increment-Finance/increment-protocol/issues/549) #1.1
- [ ] Use multicall to update global state #1.1
- [ ] Use multicall to update state of list of accounts #1.1
- [ ] Update py functions to reflect solidity code changes #1.1
- [ ] modify python to use correct margin ratio calcs instead of marginRatio #1.1
- [ ] [Increment parameter calcs](app://obsidian.md/Increment%20parameter%20calcs) #1

not done
filename includes TestFile11
sort by tag 1
has tags
limit to 7 tasks

File name should be TestFile11

I have been investigating this.
One thing I have found is that Tasks does not treat . as a valid tag character.
This can be seen with:

Global filter #task (purely because I was testing this in the Tasks-Demo vault, for convenient)
In a file called test1111.md
These lines:

- [ ] #task task #0.5
- [ ] #task task #1
- [ ] #task task #0
- [ ] #task task #1.2
- [ ] #task task #1.9
- [ ] #task task #1.5
- [ ] #task task #2
- [ ] #task task #2.1
- [ ] #task task #5
- [ ] #task task #10
- [ ] #task task #11.1
- [ ] #task task #1.001

This tasks block:

```tasks
not done
filename includes test1111
group by tags
```

Produces this result:

This most likely explains the behaviour observed in this ticket.
I am thinking about relaxing the tag recognition to allow dots to be recognised... I will see what Obsidian does too - and look back at earlier discussion in Tasks about valid characters in tags.

I am thinking about relaxing the tag recognition to allow dots to be recognised... I will see what Obsidian does too - and look back at earlier discussion in Tasks about valid characters in tags.

It's not a promise of making this change, but when I allow . to be found in Tasks tags, none of the existing tests fails. (The test coverage is not perfect, however)

If you were to allow . in tags, do you think Tasks would correctly interpret the resulting tag as a decimal rather than a string, or would that require additional development? Many thx for this :)

If you were to allow . in tags, do you think Tasks would correctly interpret the resulting tag as a decimal rather than a string, or would that require additional development? Many thx for this :)

Thanks. That's on my list of things to check! 😄

Just saving some notes from an experiment I did, to compare what Obsidian and Tasks consider tags.
In Markdown
In file testing tags.md

## Obsidian says yes

- [ ] #task Am I a tag #quesion?
- [ ] #task Am I a tag #qu-esion?
- [ ] #task Am I a tag #que_sion?
- [ ] #task Am I a tag #12_233?
- [ ] #task Am I a tag #12-233?
- [ ] #task Am I a tag #12/233?

## Obsidian says partial

- [ ] #task Am I a tag #hello.world?
- [ ] #task Am I a tag #12x.x233?

## Obsidian says no

- [ ] #task Am I a tag #12233?
- [ ] #task Am I a tag #12.233?
- [ ] #task Am I a tag #12.x233?

With query:
```tasks
filename includes testing tags
group by heading
group by tags
```

Gives:

In YAML/frontmatter/properties
---
tags:
  - hello
  - 4556
  - 345.6
  - "1234"
  - "234.5"
  - world
---

Displayed in Obsidian 1.4.2 (Insider) as:

So it seems that adding quotes now enables pure numbers to be treated as tags, at least in the Properties...

The regex used by Tasks to recognise tags is:
    // Regex to match all hash tags, basically hash followed by anything but the characters in the negation.
    // To ensure URLs are not caught it is looking of beginning of string tag and any
    // tag that has a space in front of it. Any # that has a character in front
    // of it will be ignored.
    // EXAMPLE:
    // description: '#dog #car http://www/ddd#ere #house'
    // matches: #dog, #car, #house
    public static readonly hashTags = /(^|\s)#[^ !@#$%^&*(),.?":{}|<>]+/g;

Note the . that prevents full-stops/periods from being recognised by Tasks in tags.
This is the line, in my opinion, that prevents a simple solution of removing that . from the regex:
- [ ] #task Am I a tag #hello.world?

The change would mean that:

Obsidian still says the tag is #hello
Tasks says that the tag is #hello.world

Obviously I could add more code, to say that . is only allowed inside pure numbers. But that is more complexity to maintain, and I don't really want to do that, for what is essentially a bug already, that Tasks recognises pure-digits as tags when it should not.
I think my options are:

Do a partial fix of #929 and prevent Tasks from recognising #1224 as a tag. Then Tasks is a bit more consistent with Obsidian
Just do nothing and close this issue
Make the Tasks code more complex and recognise . in a pure number tag, at the expense of more complexity in the code.
Implement custom sorting - sort by function and include an example to show users how to treat decimal "tags" for sorting...

Hey sorry about the delayed response. Just so I understand, does 4) imply 3) or are they distinct? many thx

No it doesn't. They are separate things.

Ah ok I see. I have multiplied all of my tags by 10 so that none of them contain decimal points anymore, and I think the available precision this way is sufficient for my needs. I would very much appreciate though if numbers without decimals are still detected as tags, as the precision this provides is super useful. So option 2) or option 4) (assuming option four will allow for detecting tags that consist of integers) would work for me at least :)
many thx

Another solution which I'd be happy with is that tags containing only numbers are not recognised, but e.g. #x13 is recognised and sorted as though 13 is a number rather than a string. So #13 should be sorted as being higher than #x2 . Not sure whether this is more or less difficult though.

I have multiplied all of my tags by 10 so that none of them contain decimal points anymore, and I think the available precision this way is sufficient for my needs.

Thanks for letting me know.
Whatever else happens then, this specific issue is not needed.
There is already a feature request for point 4 in my list above, should you wish to up-vote that.
And any preferences on whether to retain treating ‘digit only tags’ would be best popped in #929.


chore: add renovate config

What this PR does / why we need it:
chore: add renovate config
Add renovate configuration, which updates main and release branches. release branches are configure to have only security patches.
Release note:
NONE

/hold need to wait until this project is onboarded to renovate

/hold cancel

@akrejcir can you please review this?

But let's wait until we fix renovate issues in SSP. The PR that it opened is not correct.
https://github.com/kubevirt/ssp-operator/pull/1043
/hold

I made mistake in previous comment.
I meant this PR: https://github.com/kubevirt/ssp-operator/pull/1039

Renovate is still not fixed in SSP. Let's close this PR.
We can reopen it in the future.


[stable/vmware_exporter] Introduce a new helm chart for vmware_exporter

==> Linting .
[INFO] Chart.yaml: icon is recommended
1 chart(s) linted, no failures
Signed-off-by: Martin Kremers<EMAIL_ADDRESS>Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] title of the PR contains starts with chart name e.g. [stable/chart]

Thanks for the chart, it will be really useful for us!

/assign @sameersbn

hey @kremers
Have you considered hosting this chart and adding it to helm hub?
https://github.com/helm/hub/blob/master/Repositories.md

hey @kremers
Have you considered hosting this chart and adding it to helm hub?
https://github.com/helm/hub/blob/master/Repositories.md

Not yet, this is pretty new to me :1st_place_medal:
I'll double check all the mentioned things and update the pr.

/assign maorfr

@kremers, here is some information about hosting your own charts (copied from a similar PR):
I think that you totally should host your own charts!
This will give you more freedom around management, and you will not be blocked by us (maintainers).
This means that when users want to install your chart, instead of installing them from stable, they will install it from (for example) mycompany-charts:
$ helm install --name my-release mycompany-charts/mychart
Here are some instructions about how to host your own charts repo:
https://github.com/helm/hub/blob/master/docs/github.md#github-pages-as-a-repository
In order for people to find out about your charts repo, you should add it to helm hub:
https://hub.helm.sh/
Here are some instructions about how to add your charts repo to helm hub:
https://github.com/helm/hub#how-to-add-your-helm-charts
Hope that answered all your questions! :)


cigien: Watch apkguru.net

cigien requests the watch of the watch_keyword apkguru\.net. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

apkguru\.net has been seen in 1 true positive, 0 false positives, and 0 NAAs.

apkguru\.net has been seen in 1 true positive, 0 false positives, and 0 NAAs.

From Yatin's watch message in chat

1 TP, no hits on SE search

From Yatin's watch message in chat

1 TP, no hits on SE search

Approved by Mast in Charcoal HQ

Approved by Mast in Charcoal HQ

Approved by Mast in Charcoal HQ

Approved by Mast in Charcoal HQ

Approved by Makyen in Charcoal HQ

Approved by Makyen in Charcoal HQ


Automated cherry pick of #6463: add fuzzy ip matching

Cherry pick of #6463 on release/3.1.
#6463: add fuzzy ip matching

Codecov Report

Merging #6480 into release/3.1 will increase coverage by 0.03%.
The diff coverage is 12.37%.

@@              Coverage Diff               @@
##           release/3.1   #6480      +/-   ##
==============================================
+ Coverage         7.45%   7.48%   +0.03%
==============================================
  Files              584     585       +1
  Lines            98663   98933     +270
==============================================
+ Hits              7354    7407      +53
- Misses           90738   90952     +214
- Partials           571     574       +3

Flag
Coverage Δ

#aFlag
7.48% <12.37%> (+0.03%)
:arrow_up:

Impacted Files
Coverage Δ

pkg/appsrv/workers.go
65.46% <ø> (-0.25%)
:arrow_down:

pkg/cloudcommon/db/db_dispatcher.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/tenantcache.go
1.31% <0.00%> (ø)

pkg/cloudcommon/policy/policy.go
1.58% <0.00%> (+0.04%)
:arrow_up:

pkg/cloudprovider/cloudprovider.go
1.70% <0.00%> (-0.13%)
:arrow_down:

pkg/cloudprovider/instance.go
0.00% <ø> (ø)

pkg/compute/guestdrivers/aws.go
3.96% <0.00%> (-0.14%)
:arrow_down:

pkg/compute/guestdrivers/base.go
0.00% <0.00%> (ø)

pkg/compute/guestdrivers/managedvirtual.go
0.00% <0.00%> (ø)

pkg/compute/guestdrivers/zstack.go
6.49% <0.00%> (-0.18%)
:arrow_down:

... and 50 more

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 47be971...949c202. Read the comment docs.


secrets are written back to file with aws sm

using the documentation here - https://docs.newrelic.com/docs/network-performance-monitoring/advanced/advanced-config/#external-config-files for AWS Secrets Manager -
default_v3:
user_name: aws.sm.SECRET_NAME_1
authentication_protocol: MD5
authentication_passphrase: aws.sm.SECRET_NAME_2
privacy_protocol: AES256
privacy_passphrase: aws.sm.SECRET_NAME_3
After the container is started, it writes back the secrets on the file system.
It shouldn't overwrite the file with sensitive information.

@ankitgupta-e you can write the secret in SM in a JSON format with all of the required configuration fields and reference it like this instead
default_v3: aws.sm.secret.name

Good catch -- default_v3: aws.sm.secret.name is the preferred way and the other approach should be deprecated. @Mesverrum , can you update the docs to reflect this?

I've submitted the docs change to the content team, should go live in the next few days with the corrected syntax


Need to remove hold-out reach observations from calculating metrics for train and val partitions

After #178, we now can mask out segments for validation and testing, but since those segment id's and dates still exist in prepped.npz, when we join them to the observation file during combine_metrics they'll wind up included in the training and validation performance metrics.  TLDR, we need to pass those hold-out segments to combine_metrics and mask them out so they're only included in the metrics for the appropriate partition.

Addressed in #190


Refactored CLI

Closes #95. Feedback on this is very welcome. Makes the CLI stateless and changes the usage from omg start to omg <command> arguments.
Had to make some small modifications so tests pass.

@kfichter Making the MVP client stateless makes things a lot simpler.


Dependencies endpoint

Add /api/dependencies endpoint. This is to be used as part of improving missing dependency discovery in our nightly job (#2562) - and in general to further dependency analysis by giving us an easy way to extract the full dependency tree across all packages.

Ad hoc deploying this to proceed with testing


addition of the school: ENSSAT

@juleslagarde Please rename lib/domains/fr/enssat.fr to lib/domains/fr/enssat.txt.
Please notice that free educational subscription is for students and teachers only. If researchers who are not students, nor teachers at your school need JetBrains tools too, they can email<EMAIL_ADDRESS>to get their academic discount.

@juleslagarde Pull request merged. Thank you for the update!


padepy stops calculating descriptors from .smi files

Hi
padepy stops calculating descriptors from .smi files, the problem is not related to an error of a smile string, it stops calculating anywhere in the smi file, it should be fixed
Thank you

Hi @totocotonio1,
Could you please provide a code snippet and a .smi file so I can help troubleshoot?
Best,
Travis

Hi @tjkessler
here is the script,
` pip install padelpy
from padelpy import padeldescriptor
padeldescriptor(mol_dir='/content/drive/MyDrive/test/test1.smi', d_file='/content/drive/MyDrive/test/descriptors1.csv', fingerprints=True)`
to be noted that I am using google colab
I am generating the files in myDrive
test1.zip

@totocotonio1,
I was able to generate the descriptors for your .smi file locally with everything located in the same directory:
from padelpy import padeldescriptor

padeldescriptor(
    mol_dir='test1.smi',
    d_file='descriptors1.csv',
    fingerprints=True
)

I've attached a ZIP file containing your .smi file, the resulting descriptors1.csv file, and the notebook I used: smiles_file_test.zip
I don't have too much experience with using PaDELPy in Google Colab, hopefully someone else can weigh in! Given that I was able to run everything locally, maybe the error is a file path issue...
Best,
Travis

Hi @tjkessler
Thank you very much for your help,
I will generate the descriptors locally


Allow link to be in isActive state if the current route name is included in to-matches route name array

What problem is this solving
When using an AppBar with VTabs containing links, it is not possible to make the VTab button active for a route other than the one passed in :to. Adding a non-mandatory to-matches array property would make the link active if the named route is included in the to-matches prop.
Proposed solution
Add a to-matches array property for all components actually having a :to prop and update the useLink composable in the router.mjs in order to return true if the route is included in the to-matches property.
Describe alternatives you've considered
Updating the router configuration with all the matches routes for a given route or updating the useLink composable, but actually we can't replace a specific composable.

Sorry, wrong github repository (issue is for vuetify).


fix Error list and error tooltips were not read with JAWS 16

AT-1352

:ok: 7d5884d585d3050778bb6100a69acdddaa09cd4a is fine for me


Add cargo fetch man page

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

Awesome, thanks @munyari! You can probably skip commands like verify-project, locate-project, git-checkout, and read-manifest as well.
Do you want to hold off on r+'ing until this has all of the commands you listed? (I don't mind r+'ing now)

Hey Alex. I guess by r+'ing, you're referring to merging? Whichever you prefer :smile: I may try to complete the rest tomorrow

Should be ready for r+'ing now @alexcrichton

@bors: r+ 7ca06e7b8fde56caa8a748b495f5989b2b99000a
Thanks @munyari!

:hourglass: Testing commit 7ca06e7 with merge 3fe3b87...

:broken_heart: Test failed - cargo-win-msvc-64

@bors: retry
On Tue, Jul 26, 2016 at 4:29 PM, bors<EMAIL_ADDRESS>wrote:

💔 Test failed - cargo-win-msvc-64
https://buildbot.rust-lang.org/builders/cargo-win-msvc-64/builds/573
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang/cargo/pull/2918#issuecomment-235437362, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAD95ANDrngXQGkEwc7Oj7Fu8kP7ZlKVks5qZphhgaJpZM4JUgd3
.

:zap: Previous build results for cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32 are reusable. Rebuilding only cargo-cross-linux, cargo-win-msvc-64...

:sunny: Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64
Approved by: alexcrichton
Pushing 3fe3b876a8651d0e6deb3e819fc2222d08721ee2 to master...


Scenes with 3D nodes do not start on Android

Operating system or device, Godot version, GPU Model and driver (if graphics related):
Google Nexus 5 (Android 6.0.1), Godot Engine v3.0.alpha.build2, Qualcomm Adreno 330 (OpenGL ES 3.0).
Additional info:
Godot Engine build and export templates were downloaded from here.
Issue description:

If scene contains some 3D-related nodes (e.g. MeshInstance with primitive mesh), then application freezes at Godot Engine splash screen.
adb logcat:

11-10 20:26:17.927   775  1392 I ActivityManager: START u0 {act=android.intent.action.MAIN flg=0x10000000 cmp=org.godotengine.nexus53dtest/org.godotengine.godot.Godot} from uid 2000 on display 0
11-10 20:26:17.950 29098 29098 D AndroidRuntime: Shutting down VM
11-10 20:26:17.978   775  4033 I ActivityManager: Start proc 29127:org.godotengine.nexus53dtest/u0a253 for activity org.godotengine.nexus53dtest/org.godotengine.godot.Godot
11-10 20:26:17.986 29127 29127 I art     : Late-enabling -Xcheck:jni
11-10 20:26:18.029   775  1204 I ActivityManager: Config changes=480 {1.0 255mcc6mnc en_US ldltr sw360dp w592dp h336dp 480dpi nrml land finger -keyb/v/h -nav/h s.148}
11-10 20:26:18.038   775   874 I InputReader: Reconfiguring input devices.  changes=0x00000004
11-10 20:26:18.038   775   874 I InputReader: Device reconfigured: id=4, name='touch_dev', size 1080x1920, orientation 1, mode 1, display id 0
11-10 20:26:18.082  1389  1389 W Binder_6: type=1400 audit(0.0:432303): avc: denied { ioctl } for path="socket:[1511054]" dev="sockfs" ino=1511054 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.082  1389  1389 W Binder_6: type=1400 audit(0.0:432304): avc: denied { ioctl } for path="socket:[1511054]" dev="sockfs" ino=1511054 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.090 29127 29127 D GODOT   : ** GODOT ACTIVITY CREATED HERE ***
11-10 20:26:18.129 29127 29127 D GODOT   : command_line is null? yes
11-10 20:26:18.122  4046  4046 W Binder_10: type=1400 audit(0.0:432305): avc: denied { ioctl } for path="socket:[1516672]" dev="sockfs" ino=1516672 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.122  4046  4046 W Binder_10: type=1400 audit(0.0:432306): avc: denied { ioctl } for path="socket:[1516672]" dev="sockfs" ino=1516672 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.293 29127 29127 I godot   : **INIT EVENT! - 0xb4d96a80
11-10 20:26:18.293 29127 29127 I godot   : ***************** HELLO FROM JNI!!!!!!!!
11-10 20:26:18.293 29127 29127 I godot   : *******CLASS FOUND!!!
11-10 20:26:18.293 29127 29127 I godot   : STEP2, 0x1004fe
11-10 20:26:18.293 29127 29127 I godot   : STEP3 -1334633752
11-10 20:26:18.293 29127 29127 I godot   : STEP4, 0x10001d
11-10 20:26:18.293 29127 29127 I godot   : STEP4.5, 0x100502
11-10 20:26:18.294 29127 29127 I godot   : STEP7
11-10 20:26:18.294 29127 29127 I godot   : STEP8
11-10 20:26:18.294 29127 29127 I godot   : *******GOT METHOD dir_open ok!!
11-10 20:26:18.294 29127 29127 I godot   : *******GOT METHOD dir_next ok!!
11-10 20:26:18.294 29127 29127 I godot   : *******GOT METHOD dir_close ok!!
11-10 20:26:18.294 29127 29127 I godot   : *******GOT METHOD dir_is_dir ok!!
11-10 20:26:18.294 29127 29127 I godot   : starting to attempt get methods
11-10 20:26:18.294 29127 29127 I godot   : *******GOT METHOD init_audio ok!!
11-10 20:26:18.294 29127 29127 I godot   : *******GOT METHOD write_buffer ok!!
11-10 20:26:18.294 29127 29127 I godot   : *******GOT METHOD quit ok!!
11-10 20:26:18.294 29127 29127 I godot   : *******GOT METHOD pause ok!!
11-10 20:26:18.294 29127 29127 I godot   : test construction 5
11-10 20:26:18.294 29127 29127 I godot   : running from dir /
11-10 20:26:18.309 29127 29158 I godot   : **SETUP
11-10 20:26:18.309 29127 29158 I godot   : CMDLINE LEN 0 - APK EXPANSION 0
11-10 20:26:18.312  1391  1391 W Binder_8: type=1400 audit(0.0:432307): avc: denied { ioctl } for path="socket:[1516313]" dev="sockfs" ino=1516313 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.312  1391  1391 W Binder_8: type=1400 audit(0.0:432308): avc: denied { ioctl } for path="socket:[1516313]" dev="sockfs" ino=1516313 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.312   495   495 W Binder_4: type=1400 audit(0.0:432309): avc: denied { ioctl } for path="socket:[1517582]" dev="sockfs" ino=1517582 ioctlcmd=7704 scontext=u:r:surfaceflinger:s0 tcontext=u:r:surfaceflinger:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.312   495   495 W Binder_4: type=1400 audit(0.0:432310): avc: denied { ioctl } for path="socket:[1517582]" dev="sockfs" ino=1517582 ioctlcmd=7704 scontext=u:r:surfaceflinger:s0 tcontext=u:r:surfaceflinger:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.331 29127 29159 D OpenGLRenderer: Use EGL_SWAP_BEHAVIOR_PRESERVED: true
11-10 20:26:18.322   224   224 W Binder_1: type=1400 audit(0.0:432311): avc: denied { ioctl } for path="socket:[1511059]" dev="sockfs" ino=1511059 ioctlcmd=7704 scontext=u:r:surfaceflinger:s0 tcontext=u:r:surfaceflinger:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.322   224   224 W Binder_1: type=1400 audit(0.0:432312): avc: denied { ioctl } for path="socket:[1511059]" dev="sockfs" ino=1511059 ioctlcmd=7704 scontext=u:r:surfaceflinger:s0 tcontext=u:r:surfaceflinger:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.362  4038  4038 W Binder_D: type=1400 audit(0.0:432313): avc: denied { ioctl } for path="socket:[1516315]" dev="sockfs" ino=1516315 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.362  4038  4038 W Binder_D: type=1400 audit(0.0:432314): avc: denied { ioctl } for path="socket:[1516315]" dev="sockfs" ino=1516315 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.372 29127 29158 I godot   : *****SETUP OK
11-10 20:26:18.372  2535 16326 I Icing   : Indexing 318F571EA918ABF0F442A78012795AC8B9B9264C from com.google.android.gms
11-10 20:26:18.372 29127 29158 I godot   : ANDROID MODULES: Nothing to load, aborting
11-10 20:26:18.419 29127 29159 I Adreno-EGL: <qeglDrvAPI_eglInitialize:379>: QUALCOMM Build: 10/21/15, 369a2ea, I96aee987eb
11-10 20:26:18.425 29127 29159 I OpenGLRenderer: Initialized EGL, version 1.4
11-10 20:26:18.429  2535 16326 I Icing   : Indexing done 318F571EA918ABF0F442A78012795AC8B9B9264C
11-10 20:26:18.452 29127 29127 D GODOT   : setVirtualKeyboardHeight: 0
11-10 20:26:18.459 29127 29158 W GodotView: creating OpenGL ES 3.0 context :
11-10 20:26:18.467 29127 29127 I godot   : WARNING: not found: display/driver/keep_screen_on
11-10 20:26:18.471 29127 29158 I godot   : ^^^^^ newcontext 0
11-10 20:26:18.471 29127 29158 I godot   : ^^^^^ resize 0, 1920, 1080
11-10 20:26:18.471 29127 29158 I godot   : **FIRST_STEP
11-10 20:26:18.494 29127 29158 I godot   : OpenGL ES 3.0 Renderer: Adreno (TM) 330
11-10 20:26:18.574 29127 29158 I godot   : GLES3: max ubo light: 409
11-10 20:26:18.574 29127 29158 I godot   : GLES3: max ubo reflections: 455, ubo size: 144
11-10 20:26:18.576   775   793 I ActivityManager: Displayed org.godotengine.nexus53dtest/org.godotengine.godot.Godot: +617ms
11-10 20:26:18.572  1204  1204 W Binder_4: type=1400 audit(0.0:432315): avc: denied { ioctl } for path="socket:[1517591]" dev="sockfs" ino=1517591 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.572  1204  1204 W Binder_4: type=1400 audit(0.0:432316): avc: denied { ioctl } for path="socket:[1517591]" dev="sockfs" ino=1517591 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.572   786   786 W Binder_2: type=1400 audit(0.0:432317): avc: denied { ioctl } for path="socket:[1517590]" dev="sockfs" ino=1517590 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.572   786   786 W Binder_2: type=1400 audit(0.0:432318): avc: denied { ioctl } for path="socket:[1517590]" dev="sockfs" ino=1517590 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=0
11-10 20:26:18.591 29127 29127 D GODOT   : setVirtualKeyboardHeight: 0
11-10 20:26:18.603   775   793 I WindowManager: Screen frozen for +597ms due to Window{7e80055 u0 org.godotengine.nexus53dtest/org.godotengine.godot.Godot}
11-10 20:26:18.609 29127 29127 D GODOT   : setVirtualKeyboardHeight: 0
11-10 20:26:18.625 29127 29158 I godot   : OpenSL Init OK!
11-10 20:26:18.650 29127 29158 W AudioTrack: AUDIO_OUTPUT_FLAG_FAST denied by client; transfer 1, track 44100 Hz, output 48000 Hz
11-10 20:26:18.657   202   808 D audio_hw_primary: out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
11-10 20:26:18.668   202   808 D audio_hw_primary: select_devices: out_snd_device(2: speaker) in_snd_device(0: none)
11-10 20:26:18.668   202   808 D msm8974_platform: platform_send_audio_calibration: sending audio calibration for snd_device(2) acdb_id(15)
11-10 20:26:18.668   202   808 D audio_hw_primary: enable_snd_device: snd_device(2: speaker)
11-10 20:26:18.671   202   808 D audio_hw_primary: enable_audio_route: apply and update mixer path: low-latency-playback
11-10 20:26:18.898 29127 29158 I godot   : ARVR: Registered interface: Native mobile
11-10 20:26:19.398 29127 29158 E godot   : ERROR: Error opening file: res://icon.png
11-10 20:26:19.398 29127 29158 E godot   :    At: core/io/image_loader.cpp:54:load_image() - Error opening file: res://icon.png
11-10 20:26:20.609   775   793 I art     : Starting a blocking GC Explicit
11-10 20:26:20.686   775   793 I art     : Explicit concurrent mark sweep GC freed 31273(2MB) AllocSpace objects, 1(20KB) LOS objects, 29% free, 38MB/54MB, paused 969us total 75.884ms
11-10 20:26:22.237  3193  3193 I WearableService: Wearable Services stopping
11-10 20:26:32.275 21643 21722 I Finsky  : [8432] com.google.android.finsky.l.c.a(23): Completed 0 account content syncs with 0 successful.
11-10 20:26:32.275 21643 21643 I Finsky  : [1] com.google.android.finsky.services.e.a(5): Installation state replication succeeded.
11-10 20:26:39.276   212   325 I ThermalEngine: TM Id 'SKIN_THERMAL_management_1' Sensor 'xo_therm_pu2' - alarm raised 1 at 40.0 degC
11-10 20:26:39.276   212   325 I ThermalEngine: ACTION: CPU - Setting CPU[0] to 1958400
11-10 20:26:39.276   212   325 I ThermalEngine: ACTION: CPU - Setting CPU[1] to 1958400
11-10 20:26:39.276   212   325 I ThermalEngine: ACTION: CPU - Setting CPU[2] to 1958400
11-10 20:26:39.276   212   325 I ThermalEngine: ACTION: CPU - Setting CPU[3] to 1958400
11-10 20:26:39.276   212   325 I ThermalEngine: ACTION: LCD - Setting max LCD brightness to 229

Text file format:
logcat.txt
Possible references:
#12117
#11693
Steps to reproduce:

Open project with 3D node(s) in the main scene in Godot Engine editor.
Make one-click deploy.

Link to minimal example project:

nexus-5-3d-test.zip

Present the same error on LG G3:
Chipset | Qualcomm MSM8974AC Snapdragon 801
CPU | Quad-core 2.5 GHz Krait 400
GPU | Adreno 330

On gpaid, I got this incomplete frame:

the ultimate call opengl :

in render thread:

Logcat with opengl calls:
https://pastebin.com/S6Up0w7H
Maybe a driver problem?

probably something incompatible with Adreno 3xx, will need one to test.

Probably, a friend tested on an LG G2, with adreno 3xx, same problem,
I have no idea how to come up with a fix :/

The screen just freezes, no warnings, no logs, no infos, etc

I have a Xiaomi Redmi 3s Pro with Adreno 505 and have the same error.

Encountered similar behaviour on some Adreno devices - the reason was that linking scene.glsl shader (glLinkProgram call) took enormous amount of time.
After removing shader parts related to USE_FORWARD_LIGHTING and fogs, linking started to take tens of seconds instead of infinity.
Not entirely sure this is the same issue though.

Same here with Adreno 305. Some friends who own devices with Adreno gpus reported the same.
My project is pretty big and we're in middle stages of development, I'm very worried about this.

@endragor can you provide steps? I'm not familiar with Godot rendering backstages.

See https://github.com/endragor/godot/commit/02b12c98043afa6418e0463204e638d6f435ed0a. I haven't checked recently if those removals help though, it could be that something new was added that also causes hanging.

@endragor, does this removal of the shader solves the android crash problem?

@Alexia-AT-Digitecnology It solves freezing at the beginning which is mentioned in the OP. I didn't see mentions of crashes here, so I'm not sure which problem you are referring to.

When you run a Godot 3d project into a cellphone with adreno chipset, it crashes. It happens to me and a lot of friends. And mali chipsets too.

@Alexia-AT-Digitecnology then it is likely a different issue - please create a new issue on GitHub and attach a sample project to it.

@endragor, it's issue #11693

There is another issue related: #12192

So this is a duplicate of #11693, which also says there is a freeze. #12192 was a configuration issue. So do you experience a crash or a freeze? If it's a crash, then it is something different from the opened issues.

Thank you, @endragor.
I reproduced this endragor/godot@02b12c9 and now it doesn't stuck on loading screen anymore, but 3D shaders are all black and performance is painful; 30fps with just one Sprite3D (20 with shaded flag on).

UWP also hangs if you add any mesh, I wonder if it's related. ANGLE seems to get into an infinite loop.

There were several reports of non-working or crashing 3D with Adreno 5xx GPUs too, so edited the issue title to match those.

I wanted to clarify what is the plan to correct this problem?
Since the problem is very serious! Processors Qualcomm installed in half of the devices for android. In essence, this problem makes the android platform not suitable for distributing games on the Godot engine. Earlier decisions of this problem seem to me not correct.
1 Wait for the release of version 3.1 for an extremely long time (probably about a year).
2 To solve the problem by replacing OpenGLES 3.0 with OpenGLES 2.0 for processors with a Qualcomm is a very strange way.
What do I suggest:
1 In all likelihood, several GPU developers will have to be supported.
2 Perhaps it is worth discussing this with the developers of Qualcomm. Maybe they will propose something.
Please kindly discuss the situation.

GLES 3 is simply less perfomant and less supported on all mobile vendors than GLES 2, so GLES 2 as a default on mobile platforms does make sense. There is also still a significant market of devices that do not support GLES 3 at all.

3.1 will be out sooner than a year from now, hopefully.

We develop a mobile game and with patches #14902 #15774 Godot works fine on Adreno GPUs. But without them, yeah, either don't develop a mobile game with Godot 3.0 or be ready to apply your own workarounds in the engine code.

Well, I should correct myself: you can develop your mobile game with Godot 3.0, as almost certainly GLES2 support will be implemented sooner than you finish your game.

@endragor

Well, I should correct myself: you can develop your mobile game with Godot 3.0, as almost certainly GLES2 support will be implemented sooner than you finish your game.

Why was it necessary to do GLES3 and spend a lot of time if all the same all are offered to use GLES2? We have a bug but we say: we will not fix this bug. and so come down! use another engine or wait for GLES2.
I do not know what to say to this :(
@volzhs

implement more shader features
implement basic PBR
directional lights

And this all will work for GLES2 or not? If not, then why should we spend it all the time? If it works then is the sense from all these new things?

@endragor

GLES 3 is simply less perfomant and less supported on all mobile vendors than GLES 2, so GLES 2 as a default on mobile platforms does make sense. There is also still a significant market of devices that do not support GLES 3 at all.

I wanted to clarify where did you get the statistics that GLES3 is not so common that it would be time to eliminate problems with it? According to Wikipedia, many GPU manufacturers have long supported the GLES3. You can easily verify this:
https://en.wikipedia.org/wiki/Mali_(GPU)
https://en.wikipedia.org/wiki/Adreno
https://en.wikipedia.org/wiki/PowerVR

I wanted to clarify where did you get the statistics that GLES3 is not so common that it would be time to eliminate problems with it?

https://developer.android.com/about/dashboards/index.html#OpenGL

https://en.wikipedia.org/wiki/Adreno

And yet, here we are, with such a bad OpenGL ES 3.0 support that the engine crashes only on Adreno.

@akien-mga
63.6% of devices support GLES3. More than a half. Especially it is worth to finish the business started and not stop at the finish. Yes, Qualcomm has reworked this task, but other engines are coping with this problem. I'm sure that the Godot will do it.

Those problems in Godot come specifically from bad implementations of GLES3 by GPUs that are still in use. You can also search for benchmarks of other engines that can target both GLES2 and GLES3 (UE4, Unity) - same scene on the same device has significantly worse performance when rendered with GLES3. Or you can build your own benchmark, if you are doubtful.
I'm not sure how you draw conclusions from Wikipedia articles - there are no stats as to how many devices are actually in use. Unity had hardware stats page that could be used to determine which hardware mobile gamers actually use right now. It's down now for some reason, but the archived version can be accessed here: https://web.archive.org/web/20170729230854/http://hwstats.unity3d.com:80/mobile/gpu.html. So according to it about 35% of devices support GLES3. Even if it was 63.6%, as you claim, releasing a GLES3 game would mean discarding 36.4% of the market, which does fall into my measure of significant.

@endragor
From Wikipedia, I received statistics according to the year of release of the GPU and the version of GLS that it supports. The last GPU supporting only GLES2 ends around 2010. Even from the statistics that you instilled (sort the operating system android and see the last paragraph), it is clear that the largest segment with GLES2 is:

ARM ES2.0 Utgard: 26.5%

All the other items where GLE2 is mentioned occupy a small percentage. And if you put them all together, you will end up with about 36.4% of the market with GLES2. What does the link from @akien-mga:
https://developer.android.com/about/dashboards/index.html#OpenGL
I honestly do not understand why, after the team has done such a huge piece of work to support GLES3, suddenly you all start saying that GLES3 is not a thoroughfare for drawing graphics and in the foreseeable future it will be supplemented with a targeted GLES2 renderer!
At me (and not only at me) at once there are questions:
1 Why Godot 3.0 came out with the support of GLES3 and only GLES3 if a year ago it was clear that GLES3 is not promising at the moment?
2 Why, with the support of GLES3 and leaving Godot so much with GLES3, improving the support of facilities becomes not a priority?
Someone, please answer me these 2 questions!
PS
Problems with GLES3 are also on the Radion cards, and they are also not someone who does not want to notice. Everyone pretends as if they are not.

Yeah perhaps those stats are more accurate and there are 36.4% devices not supporting GLES 3, but, as I said, that's still significant in my opinion. Plus those who claim they support GLES3 may support it partially or with many bugs in driver implementation.
GLES3 was implemented mainly as a target for higher end devices and with advanced features in mind. There are things that you can't do with GLES2 or can only do them with significant sacrifices, while they can be implemented easily in GLES3. Some of those were listed by @reduz here: https://github.com/godotengine/godot/issues/14869#issuecomment-353516796 .
Now, I myself am still not convinced whether GLES3 is really a viable platform for complex games as there is evidence that its performance is poor in some cases, and I'm yet to see a game/demo with a complex scene and decent performance.
I can't answer the question (1) as it was @reduz's decision. Even if the answer is "it was fun for him to explore modern rendering techniques that cannot be implemented with GLES2", that works for me. It's work he was doing for free at the time, and as a result we are getting a FREE engine with astonishing capabilities and ease of use. And you just have to wait for a couple of months to get a working GLES2 renderer.
The answer to (2) is that it's not a priority to improve GLES3 on mobile as GLES2 will be the standard on that platform, so there is no point in adding mobile-specific hacks that will affect other platforms. For other platforms fixing GLES3 renderer is a priority, as far as I can tell. If you are aware of Radeon-specific issues, do report them, and there are some in the backlog scheduled for 3.1.

I can't answer the question (1) as it was @reduz's decision. Even if the answer is "it was fun for him to explore modern rendering techniques that cannot be implemented with GLES2", that works for me. It's work he was doing for free at the time, and as a result we are getting a FREE engine with astonishing capabilities and ease of use. And you just have to wait for a couple of months to get a working GLES2 renderer.

So be it. However, based on experience, I can say that a couple of months will not be enough to release Godot 3.1. When I designed Godot 3.0, I gave the most pescemal predictions from all on the forum. And they did not come true, it took more time than I expected. There is a suspicion that the same thing will happen this time. And that would make a correction to the already existing GLES3 will require less effort. And in a month you can release Godot 3.0.1
At the moment there was not a very good situation. The quality of stable version 3.0 leaves much to be desired. And if Godot wants to compete with Unity and Unrial, then the quality of the product will have to be kept at a decent level. And the development of new features is certainly great, but fixing bugs should be in the first place.
PS.
The lack of shadow on Radeon R7. No buffers are created in class "RestorizerSceneGLES3:initialize" line 4882. I raised this topic on Facebook. But there everything was dead.
CPU AMD A10 PRO-7800B R7 Compute Cores 4C+8G

sure, there are part phone only support gles2, not gles3. but they are old, the ram entirely small. other word, the one who uses the old phone, will not play 3D game.  even can't use social app. like wechat, qq.  not all the market is the qualified market. maybe it's better to do some trick to make godot-gles3 work well  on adreno hardware. better including new feather ,sth like the one--tessellation.

@aron3097 You say it right, but everybody doesn't care. :)

Just for the logs, i have the same issue on Adreno 304 on a Lenovo TV-X103F (10" Lenovo Essential tablet with Qualcomm 1.3 quadcore) https://hastebin.com/calevamoqa.vbs
Is it possible to use a small whitelist for GPU's to fall back to GLES2?
Would be a good workaround for now.

I found one more, HTC Desire 530, Adreno 304

Google Pixel 2 Adreno 540

Was reading some other troubleshooting references related to this and I noted that in many of the cases the Device Manufacturer's ended up fixing this through Webview updates before Android 7. Since Webview is tied to Chrome version now, I thought I'd try updating the Pixel 2 to Android P beta and the issue is gone.

Kicking to 3.2, where it will probably be closed due GLES3 renderer being removed.

The bug reads more like "Godot doesn't support some Adreno GPUs", not "GLES3 backend doesn't support <...>". This should be fixed in 3.1 with GLES2 backend, so I think it needs to be tested and closed - otherwise people will think Godot still doesn't support mobile.


Add colorize to output file and add HTML format result

https://github.com/pycontribs/ansi2html
simple qdd  output | ansi2html -u -u
but no any idea  how add to file file formats output  rext .
In my case i parse CallCenrer calls and shiw dialogs in web

no idea what u want


MMSeqs2 parameters

In the paper it is written that sequences were split into train/eval/test via MMSeqs2 clustering with a sequence_identity threshold of 0.95 - could you provide the full set of parameters used for clustering, or were the remaining ones left to be the default? Thanks!

Hi Marc, thank you for the question. Other than using "--cov-mode 1" to better handle fragmented sequences, the rest of the parameters used for clustering were the default ones.
I hope this helps!


Move uwhackweeks to a faster EFS server

Context
In https://2i2c.freshdesk.com/a/tickets/113, it was reported that the home directories for the uwhackweeks weren't fast enough for some tasks. We can improve performance here by switching to a higher EFS tier, at some cost.
Proposal

[ ] Make 'tier' an option in our terraform, so we can give different hubs different price / performance ratios
[ ] Move the uwhackweeks hub to have a faster home directory EFS

Updates and actions
No response

Make 'tier' an option in our terraform, so we can give different hubs different price / performance ratios

This would be great in my opinion! The last time I read the EFS docs I found it hard to digest the various options, so even 'fast', 'faster', 'fastest' would be a nice abstraction to chose from :)
I was thinking it could be good to add a note here on encouraging users to use /tmp for temporary (but faster) storage. Thoughts?
https://docs.2i2c.org/en/latest/user/storage.html

I was thinking it could be good to add a note here on encouraging users to use /tmp for temporary (but faster) storage. Thoughts?
https://docs.2i2c.org/en/latest/user/storage.html

I think that would be a nice addition, do you want to try with a PR, @scottyhq? 😉

I've added notes about the ideas in this issue in the somewhat related issue https://github.com/2i2c-org/infrastructure/issues/2242 for now. Since this mentions uwhackweeks and we have terminated that cluster, I'll go for a close here.


Add Host DNS configuration to NetworkManager

Addresses #7

Thank you @vmorris for the contribution, could you please modify the commit rendering libvirt_dnsmasq.conf as a template?
You can use {{ libvirt.network.net | next_nth_usable(1) }}  for rendering the static <IP_ADDRESS> in the config for dnsmasq and {{ libvirt.network.domain }} for the domain.

Modified and fixed #7

Thanks @kubealex - I have very limited time to look at this project, though I'm very interested in it.. I appreciate you implementing these changes and improving on them.
I wondered about some of the other changes. I don't have any feeling for one technology over another.. would you mind giving some insight on the change to cni_plugin, container_runtime, installing nginx and rancher? Thanks again!


IPT upgrade from 2.3.2 to 2.3.4

Just upgrade

@crebollobr can you please provide some more detail to this issue? Thanks

Hello,
I Have done upgrades 2.2.1, 2.3-SNAPSHOT ( some problem in 2.3.0 ), 2.3.1, 2.3.2 without problem.
My environment configuration has been upgrade to. Now:
Java JDK 1.8.0_121
Apache tomcat 8.5.12
I have clicked in link to send the problem but i gess no another information was send.
After upgrade, the site start to error 500
HTTP Status 500 – Internal Server Error
Type Exception Report
Description The server encountered an unexpected condition that prevented it from fulfilling the request.
Exception
java.lang.NullPointerException
com.google.inject.struts2.Struts2Factory$ProvidedInterceptor.intercept(Struts2Factory.java:215)
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:245)
org.gbif.ipt.struts2.ResourceSessionInterceptor.intercept(ResourceSessionInterceptor.java:41)
com.google.inject.struts2.Struts2Factory$ProvidedInterceptor.intercept(Struts2Factory.java:215)
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:245)
org.apache.struts2.impl.StrutsActionProxy.execute(StrutsActionProxy.java:54)
org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:575)
org.apache.struts2.dispatcher.ng.ExecuteOperations.executeAction(ExecuteOperations.java:81)
org.apache.struts2.dispatcher.ng.filter.StrutsPrepareAndExecuteFilter.doFilter(StrutsPrepareAndExecuteFilter.java:99)
org.gbif.ipt.struts2.ResponseHeaderFilter.doFilter(ResponseHeaderFilter.java:53)
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:66)
org.gbif.ws.server.filter.XSSFilter.doFilter(XSSFilter.java:48)
com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
org.gbif.ipt.struts2.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:43)
com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)
com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)
Note The full stack trace of the root cause is available in the server logs.
Apache Tomcat/8.5.12
ipt_log.tar log ipt folder folders logs
tomcat_log.tar.gz apache folder logs
tomcat_log.tar.gz
ip_log.tar.gz

I have a backup of data folder. And I have back the 2.3.2 version

To eliminate your firewall as the root of this error, can you please try to follow the instructions here: https://lists.gbif.org/pipermail/ipt/2017-March/000674.html ? I look forward to hearing the result. Thanks.

Hello,
the curl command have failed with https. We do not have firewall blocking this host. I have google it and same problems with curl are about update some system packages. I have upgraded host and the curls commands are working now. But upgrade did not work for both 2.3.3 and 2.3.4.
data_logs.tar.gz
tomcat_logs.tar.gz

Sorry wrong button

What operating system are you using, and have you tried restarting Tomcat?

Hello,
CentOS release 6.8 (Final)
Yes a have tried restart the tomcat before update and after update.

I have several installs working on CentOS Linux 7 (Core) running Tomcat 7 and Java 8.
Can you please try checking, if a brand new installation of 2.3.4 works on your server?  This will isolate the problem is to do with your server environment, or to do with your existing data directory. Please remember to backup your IPT data directory before trying this. Thanks.

@crebollobr - any update on fixing this issue please? Thanks.

@crebollobr can I please let me know if your problem has gone away, and if I can close this issue now? Thanks.

Closing issue. If problems persist @crebollobr please reopen a new issue. Thanks.


Update Roughtime docs with new server

Fixes #13394.

thanks for flagging and fixing @lukevalenta.
Assuming this is fine to merge once our checks pass?

@kodster28 yep, feel free to merge anytime!


Add specs index to the releases page

We should start querying the specs repo to build an index of all the specs and their versions. This should also include other metadata such as are the ARM or data-plane or are they TypeSpec or not.

Done.


Allow Optional TX Override Params

allows tx overrides object to be passed into the options parameter to use when submitting a tx

Thanks for this PR!  This looks like a reasonable approach which would address https://github.com/OpenZeppelin/openzeppelin-upgrades/issues/85.  Particularly, since deploy.ts in both Hardhat and Truffle are used for all deployments (including proxies, proxy-related contracts and implementations), setting the overrides there would cover the various deployment transactions.
I’ve made some changes to separate the option type for Hardhat and Truffle, since Truffle does not use ethers.js.
Also removed the .idea folder since that is environment-specific and would be more suitable in a local configuration.
There are a few more changes that I am still planning to make:

The Truffle option still needs a more specific type.
Any transactions other than deployments (for example, upgrading a proxy) also need to respect the new options.
Add tests.
Add documentation.
Add changelog entry.


Install with expo ?

Hi,
I have following the automatic instruction but it's still doesn't work.
 I have to detach my app before link external lib.
More information: https://docs.expo.io/versions/v28.0.0/expokit/detach/


[Bug]: Access sequence $Bname$ contains also vendor prefix before 'Bname'

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Access sequence $Bname$ contains the board name but also the vendor (when defined).
Access sequence $Dname$ only contains the device name and not the vendor (expected).
Expected Behavior
$Bname$ should contain only the board name as specified in the documentation.
Access Sequences

$Bname$: Bname of the selected board as specified in the board: node.

Steps To Reproduce
csolution.yml
  target-types:
    - type: STM32H745I-DISCO
      board: STMicroelectronics::STM32H745I-DISCO
      device: STMicroelectronics::STM32H745XIHx

cproject.yml
      files:
        - file: test_$Bname$.c
        - file: test_$Dname$.c

cbuild generates cbuild.yml
      files:
        - file: test_STMicroelectronics::STM32H745I-DISCO.c
          category: other
        - file: test_STM32H745XIHx.c
          category: sourceC

Affected tools

[X] cbuild
[ ] cbuild2cmake
[ ] cpackget
[ ] csolution
[ ] packchk
[ ] svdconv

Affected operating systems

[ ] Windows amd64
[ ] Windows arm64
[ ] Linux amd64
[ ] Linux arm64
[ ] MacOS amd64
[ ] MacOS arm64

Environment
cmsis-toolbox 2.6.1
Windows 11

This just proofs that this expansion with vendor is not limited to the regions: node but probably to all nodes that support the expansion.

Verified: https://github.com/Open-CMSIS-Pack/devtools/issues/1846#issuecomment-2522823462


Visually Distinguish Contingent and Non-Contingent Answers and Explanations

Right now, all answers in the scenario editor, and all explanations for those answers are displayed similarly. It would be useful to be able to distinguish between those that can only be proved with the use of assumptions. It would be more useful still to be able to distinguish between assumptions made in the fact scenario and assumptions made in the code or the test, which the user can't avoid.
One option would be to outline any answers that have a non-contingent explanation in green, and outline non-contingent explanations in green, also.

There is a problem with two different kinds of abudction being used in the interview reasoner resulting in two different sorts of displays for assumed values.  Will need to fix that, first. See herefor details.


[INFRA] Add ASF DOAP file

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

What would you like to be improved?
https://projects.apache.org/create.html
How should we improve?
No response
Are you willing to submit PR?

[ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
[ ] No. I cannot submit a PR at this time.

Per ASF‘s request, would you mind to take a look? @pan3793

OK, I probably will take a look next week.


teleport: 4.0.4 -> 4.1.0

Motivation for this change
bump version to 4.1.0
Also adding myself as maintainer.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @tomberek

@GrahamcOfBorg build teleport


⚠ Bofrost.be has degraded performance

In ecce113, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1129 ms

Resolved: Bofrost.be performance has improved in ea35880 after 6 minutes.


unzip is not unzipping subdirectories

in fmu::fmu, unzip is called, and it finds the appropriate files.  However, those in the subdirectories (e.g.  binaries/win64)  are not written to the uncompressed temp location.  I see logic in unzipper
if (sb.size == 0) {
fs::create_directories(newFile);
} else {
that is meant to catch the directories and create them, but it never executed.  Is there a specific compression method needed so that libzip finds the directories first?  I used normal windows compressed folder creation and 7zip without success.

Does this happen with all FMUs you've tested or only does you made yourself?

Thanks
. strangely enough, it does not happen for any of the FMU's I've tried in the FMI4cpp package.  In those, I see the individual folders appearing before the files in the unzip loop, so the "if(sb.size == 0)" condition is encountered for those folders before the actual files are, so all seems well.
It must be my compression somehow.  I'm not sure if I need to use something besides Windows explorer compression or 7zip.  The FMI spec says I need to use "deflate", so I'm looking for a method where I know that is happening.  My bouncing ball is attached... beware it has some other issue where init works in my C tester but not here.  No doubt, I have problem in my code on that one.
CRBouncingBall.zip

User Error!  Please don't bother further.  I figured out how to deflate with 7Zip, although it was not immediately obvious.  FMI4cpp now decompresses the FMU.  Thanks for your time Lars.


IHeaderDictionary should be IRequestHeaderDictionary and IResponseHeaderDictionary

As reported by @nathan-alden in https://github.com/aspnet/Mvc/issues/5532:
IHeaderDictionary should be IRequestHeaderDictionary and IResponseHeaderDictionary, each with properties defined for each standard HTTP header, the way it was with Web API 2's HttpRequestHeaders and HttpResponseHeaders classes. Why remove this very useful abstraction? I can't extend IHeaderDictionary because then those extensions would improperly apply to both request and response headers and the members would have to be methods instead of properties. As a result, we're back to accessing headers using Dictionary with magic strings for keys.

http headers are fundamentally loosely typed dictionaries, the lower level abstraction represents that. Typed headers are a layer on top that can be accessed via the GetTypedHeaders() extension method.

See https://github.com/aspnet/HttpAbstractions/blob/dev/src/Microsoft.AspNetCore.Http.Extensions/HeaderDictionaryTypeExtensions.cs
https://github.com/aspnet/HttpAbstractions/blob/dev/src/Microsoft.AspNetCore.Http.Extensions/RequestHeaders.cs
https://github.com/aspnet/HttpAbstractions/blob/dev/src/Microsoft.AspNetCore.Http.Extensions/ResponseHeaders.cs

Cool! That's exactly what I was looking for. Thank you!


XUnit does not support public async void in next version

The next version of XUnit does not support public async void in test methods.
This should be changed to public async Task
https://dotnet.social/@xunit/112265523775265162
More recent versions of XUnit 2.x also issue a Warning - which gets treated as an Error in this project.

If you're working on tests is there any way you can make them work in visual studio? currently the netcore tests all fail because of missing sni.
It'd also be really nice if the test conditions evaluated and worked correctly. They haven't for as long as i've worked on this library.

At least with current main it seems that I can run unit tests from VS Test Explorer:


Only load one copy of React

React is currently loaded twice:

by Meteor itself via the reactjs:react-meteor package (v0.12.2)
by browserify as part of the client-side app (v0.11.0)

See #1

Fixed in 055bccd90271dd36cdb0a3934b072e6f814e7343.


[ISSUE #4787]integration connector

Fixes https://github.com/apache/eventmesh/issues/4787
########
UnMergeable！！！ its demo ，不能合并这只是用于讨论
########
Motivation
Integrate connector with minimal modification
Very simple integration using connecter
Modifications
Integrating 'connecter' means that 'connecter' has to have another running mode, and integrating into 'runtime' has some problems to solve
集成 connecter ，意味着 connecter 要有另一种运行模式，集成到 runtime 中有一些问题需要解决

The first problem that needs to be solved is that the main method is not called, but connecter is a plug-in module, and it is troublesome to hard-code main once for each plug-in. So the method I think of is that all the connecter module's startup class inherits a EmbeddableConnector interface, and uses the Eventmesh-SPI to load, so that the changes are brought
EmbeddableConnector
All startup classes in Connector (in this case, FileConnectServer)
All files referred to by SPI in Connector
首先需要解决的问题就是 main 方法没有被调用，但是 connecter 是插件化的模块，为每一个插件都硬编码一次 main 这样很麻烦，所以我想到的方法是所有 connecter 模块的启动类都继承一个EmbeddableConnector 接口,使用 Eventmesh 的 SPI 进行加载，这样带来的修改就有
EmbeddableConnector
所有 Connector 中的启动类（这个例子中的启动类是 FileConnectServer ）
所有 Connector 中 SPI 涉及的文件

Second, the original interaction between connector and runtime uses tcp protocol, and the purpose of integration is to reduce serialization and communication consumption. Therefore, interaction needs to be realized in other ways. The method I think is to use the form of service. connector itself only has two roles, sink and source, which are publish and subscribe in terms of function, so this service needs to use publish and subscribe functions. Meanwhile, in order to preserve the original structure and design to the greatest extent, the connector uses a tcp adapter (the adapter does not implement network communication in the middle). Instead, the service is called.) So the design changes are
IInnerPubSubService Indicates the interface of the service
InnerPubSubService implementation
IntegrationCloudEventTCPClientAdapter TCP adapter
Application must have a static variable holding the service
The SinkWorker passes the service to the tcp adapter
SourceWorker transfers the service tcp adapter
其次需要解决的就是原有 connector 和 runtime 之间的交互使用的是 tcp协议 而集成的目的就是减少序列化和通信消耗，所以需要通过其他方式对交互进行实现，我想到的方法是使用服务的形式， connector 本身其实只有两种角色，sink 和 source ，从功能来说就是发布和订阅，那么这个服务就需要用发布和订阅的功能即可，同时为了最大程度保留原有结构和设计，使用tcp适配器（适配器中间不在实现网络通信，而是对服务进行调用）所以设计的修改有
IInnerPubSubService 服务的接口
InnerPubSubService 服务的实现
IntegrationCloudEventTCPClientAdapter tcp适配器
Application 要有静态变量持有服务
SinkWorker 传递服务给tcp适配器
SourceWorker 传递服务tcp适配器

Unfinished changes:
The implementation of InnerPubSubService
未完成的修改：
InnerPubSubService 的具体实现

达成的效果：
只要 gradle 引用了对应的 connector  插件就会自动处理 内嵌 connector 相关逻辑
Results achieved:
The built-in connector logic is automatically handled whenever gradle references the corresponding  connector plug-in

Sorry, I have a bad cold these days, so I think it may be necessary to use a form like file lock. After connector is activated, the Worker will generate a file named Connector-instance-mian at a fixed location. When the connector is booted either integrally or separately, it will get an error that cannot be started if the file exists (init timing), and delete the file when the connector stops (shutdown timing). The only drawback is the need to manually delete this file if the connector stops unexpectedly (such as when the process is killed).
不好意思，这几天重感冒，那我想可能需要使用比如类似文件锁的形式，当connector启动后Worker在某一固定位置生成一个名为connector-instance-mian类名的文件，当无论以集成的方式还是单独启动都会去获取这个文件如果文件存在那么就报错不可以启动（init时机），当connector停止时删除这个文件（shutdown时机），唯一的缺陷是当connector意外停止时需要手动删除这个文件（比如进程被杀了）

Sorry, I have a bad cold these days, so I think it may be necessary to use a form like file lock. After connector is activated, the Worker will generate a file named Connector-instance-mian at a fixed location. When the connector is booted either integrally or separately, it will get an error that cannot be started if the file exists (init timing), and delete the file when the connector stops (shutdown timing). The only drawback is the need to manually delete this file if the connector stops unexpectedly (such as when the process is killed).
不好意思，这几天重感冒，那我想可能需要使用比如类似文件锁的形式，当connector启动后Worker在某一固定位置生成一个名为connector-instance-mian类名的文件，当无论以集成的方式还是单独启动都会去获取这个文件如果文件存在那么就报错不可以启动（init时机），当connector停止时删除这个文件（shutdown时机），唯一的缺陷是当connector意外停止时需要手动删除这个文件（比如进程被杀了）

I see in the issue that you have raised a lot of queries about the community's planning for this part of the demand, so let's leave this minor detail aside for now. I'll keep an eye on these queries as well https://github.com/apache/eventmesh/issues/4787#issuecomment-2003288218 .
我看到issue中您提了很多关于社区对这部分需求的规划的疑问，所以这个次要的细节问题暂不考虑吧。对于这些疑问（https://github.com/apache/eventmesh/issues/4787#issuecomment-2003288218 ），我也会继续关注。

@Ish1yu
Now we have a detailed issue describing the connector integration design, which may greatly help your subsequent work of this PR. So any communication with community is welcomed~


Docs: typo

Here is a typo:

we can use the CreateModelField`` form field, ie:

... there are two back-ticks
http://django-autocomplete-light.readthedocs.org/en/master/creation.html

That doc is removed in next release #609

Yep, it's gone, be careful, it has changed in 3.1: http://django-autocomplete-light.readthedocs.org/en/documentation/tutorial.html#creation-of-new-choices-in-the-autocomplete-form (release iminent).


(MAINT) Fix bug in hiera-in-templates test

This test was written assuming that there would always be
exactly one agent SUT.  It threw an error when run in a
configuration that had multiple agent SUTs (such as Puppet Server);
this commit changes the code so that the test won't definitely
fail, but a better fix would probably mandate that the whole
test be restructured to support the ability to have a unique
tempdir per agent node.

Sigh. We just did a purge of exactly this type of mistake. Beaker makes it too easy to do this.

Yup, and I filed that as https://tickets.puppetlabs.com/browse/BKR-558

Ping @segatspiretech.

Closing in favor of #4306


Subscription change issue

There are some dangerous issues with the way the SubscriptionChange object works.
If you take this code, for example:
            var change = new SubscriptionChange
            {
                TimeFrame = SubscriptionChange.ChangeTimeframe.Now,
                NetTerms = 30,
                PoNumber = "12345"
            };

            ChangeSubscription(subscriptionUuid, change);

What you would expect:

Net terms and PO number are updated to new values.

What actually happens is:

All add-ons are removed from the subscription!
The addon-list defaults to an empty list, instead of null. You can't actually null it, because the property getter (which is called when writing the XML) will just recreate an empty list.
Net terms and PO number are not updated.
You have to also set the CollectionMethod property, even if it didn't change, because of a check in the WriteChangeSubscriptionXml method.

@tuhland Thank you for reporting this. Looking into the issue 👀

@tuhland I have confirmed the problems that you describe. I want to point out that it looks like these problems existed before the SubscriptionChange objects were introduced, but I agree that these should be fixed. In the case of subscription add-ons, we should be able to just make it nullable and ensure that the XmlWriter doesn't write a tag unless it contains a value.
As for net terms and PO number, I believe the assumption at the time it was written was that those values can only be changed on a manual invoice. I am unsure whether that is still the case, but either way, client side validation is not something I support, so I'm a fan of removing that check either way. If the API won't allow you to set those values, you'll just have to null them out before sending in a request.
Thanks for bringing this up, I'll get in the fix for this as soon as possible.


various changes (see 1st comment)

Here are the changes I'd like to submit:

RFC7283 to informative reference (was obsoleted by 8415, can't keep it as normative, as idnits treats it as an error)
added list of deprecated mechanisms in 8415 (there is a similar list for 8415bis)
typo (gleaming => gleaning)
added text what to do if IA_TA is received (ignore option, continue message processing)

Updated the IA_TA processing as discussed over mail (MUST => SHOULD).


How to run on other datasets

Hello, could you tell me how to run your tensorflow code on my own datasets?

Hi,
When I run the TF.py in the "[Online_Demo_Models]_Deep-Photo-Enhancer/LPGAN_exp_G3_736" file, I face this error:
Shapes (2, 1, 32, 32, 128) and () are incompatible
in line: netG_test_output1 = model(netG, test_df.input1, False, netG_act_o, is_first=True)
Would you mind helping me with it? Thank you in advance.

I don't know. I am not the author. The author could be busy and may not to response to you.

Sorry, I am not the author. I don't even know how to run it on my dataset. The author could be busy and may not response to you.

Hi, sorry to bother you,
I'm a graduate student. And I'm majoring image enhancement. I want to test some of my own data, but I don't find the code, the web link and training model are not working.
Could you please share the project code with me? If you could share the code with me, I would be appreciated.
My email<EMAIL_ADDRESS>


Trigger fails to run handler

Couldn't get this working with the latest version of Flogo. The flow is not started.

What trigger are you using? Can you provide the flogo.json?


SyntaxError: The storage file is not properly formatted

Hello I'm using commando this is the error I got
0|shard    | (node:31837) UnhandledPromiseRejectionWarning: SyntaxError: The storage file is not properly formatted.
0|shard    |     at GiveawaysManager.getAllGiveaways (/root/dreambot/node_modules/discord-giveaways/src/Manager.js:272:27)
0|shard    |     at async GiveawaysManager._init (/root/dreambot/node_modules/discord-giveaways/src/Manager.js:363:26)
0|shard    | (node:31837) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
0|shard    | (node:31837) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Hello,
This is going to be fixed.

Is the problem fixed?

@whitskin can you try to install the package using Github? (npm install Androz2091/discord-giveaways) and retry? You should have more informations in the console.

Error
7|shard  | SyntaxError: The storage file is not properly formatted.
7|shard |     at GiveawaysManager.getAllGiveaways (/root/dreambot/node_modules/discord-giveaways/src/Manager.js:273:27)
7|shard |     at async GiveawaysManager._init (/root/dreambot/node_modules/discord-giveaways/src/Manager.js:364:26)


Bug Report: Correct Organ Does Not Turn On Automatically in EUI

This is a bug report about the EUI. When opening a custom, organ-specific registration set, the expected behavior is for the EUI to turn on the skin plus the correct organ, which is the organ that contains actual tissue blocks in the current registration set. This fails to happen.
For example, the link below is a pancreas-specific registration set so the correct organ to turn on would be the pancreas, but this fails to happen: https://hubmapconsortium.github.io/hra-registrations/staging/hubmap-pancreas-campbell-2024/
This is becoming more confusing as we are preparing more and more organ-specific registration sets that outsiders use in their presentations.
OS: MacOS
Browser: Chrome

There has never been a feature to automatically turn on the 'right' organs. That said, we do have an option in the html code to turn on specific organs with the 'selected-organs' attribute. I'll see if I can write an example for you for the pancreas case in particular.
It would be worth considering adding something like this, but it'd need to be thought through a bit. There are some considerations on what to show, especially if there are a lot of relevant organs. Do you show them all? No, the 3d models are too bulky and would slow down the browser and have a ton of overlap. Do you pick the top n organs by tissue block count? Maybe, but doesn't guarantee a legible 3d view.
CC @LibbyUX


fix: make subcommands pick up [env]

What does this PR try to resolve?
Fixes #10094
This also aims to address some of the issues pointed out in the issue, namely:

This seems reasonable; we should set the environment variables for third-party subcommands too.

This happens by default now. Users can opt-out by setting apply_to_subcommands = false for the var.

What happens if you set PATH? Does that affect finding the subcommands?

TODO

What happens if you set CARGO_HOME? Do we read .cargo/config.toml from the new location?
What happens if you set configuration environment variables?

Setting any CARGO_ var from [env] is now forbidden, and will result in an
error. I'm not sure we want something so strict, so it probably warrants further
discussion.
How should we test and review this PR?
I added tests env_external_subcommands and env_no_cargo_vars.
Additional information
I didn't add any special handling of PATH, which means currently it will not
cause the subcommand to not be found, even if the specified PATH doesn't
contain the subcommand.
I think this could lead to surprising behavior in a scenario like this:

User has cargo-foobar in their PATH
cargo-foobar relies on foobar-cli being in PATH
The user has foobar-cli in their PATH
They override PATH in [env] to one containing neither cargo-foobar nor
foobar-cli
They can invoke cargo-foobar, but it will fail due to foobar-cli not bein
in its PATH

Some options to solve this are:

We can make the vars apply prior to finding the subcommand, which should make
cargo-foobar to not be found, which is a bit less surprising
We make apply_to_subcommands default to false (the current behavior)

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ehuss (or someone else) soon.
Please see the contribution instructions for more information.

This also aims to address some of the issues pointed out in the issue, namely:

While we understand and appreciate the work that has gone into this, we ask that design discussions happen on Issues first and implementations to wait on the issue being marked as "Accepted'.  Could we move this discussion over to the Issue?
In the mean time, I'm going to close this as there are still open issues on the design that need settling.
From CONTRIBUTING.md

We encourage people to discuss their design before hacking on code. Typically, you file an issue or start a thread on the internals forum before submitting a pull request

From Process

Due to limited review capacity, the Cargo team is not accepting new features or major changes at this time. Please consult with the team before opening a new PR. Only issues that have been explicitly marked as accepted will be reviewed.

@epage I'm a little confused — this follows the suggestions from @joshtriplett in https://github.com/rust-lang/cargo/issues/10094#issuecomment-976791401. I suppose we can take the open questions over there for discussion if that's preferred, though I didn't actually see any disagreement there, so it feels as though these are less open questions and more "we'll need to pick a path and stick with it", with basic consensus on what that path should be.

@epage could you chime in on what I should do next to get this fixed?
There is already an issue for this, and there's already been a discussion on how to solve it, with no one disagreeing. I implemented what was proposed there.
What do you think needs settling before I submit this PR?

Clarifying something: we had discussions on 10094, and I suggested an approach that I thought would work. This PR, correctly, raised a few additional questions and open issues, as well as design possibilities that we need to decide between. For instance, apply_to_subcommands, or the strictness about CARGO_, and the issue of PATH.
From experience, the Cargo team has found that doing some discussion directly on a PR has been harder and higher-bandwidth for us to deal with than getting the discussion done first and then having a PR that implements the conclusion. That way, when we're reviewing the PR, we just need to worry about the implementation, and we don't have to simultaneously review design proposals in code form and not just prose form.
Closing this PR is not an indication that we don't want to see this change; on the contrary, we definitely want to see things finished and shipped. Rather, we'd just like to direct the design discussion back to the issue, deal with the open design questions, and once we have a settled design we'd be happy to see a PR.

@joshtriplett That makes sense, thanks for the clarification! Will follow up in the issue 👍

Sorry for the delay in getting a response back to the confusion over my post.  I had just left on a road trip and wifi didn't work at any of our hotels.  Thanks @joshtriplett for clarifying things in my absence!

All good — a road trip without WiFi sounds wonderful!


IRange problem in CP

In CP, the maximum current is obtained according to i_max = max( currents ), which determines the IRange later. But if the currents are passed as negative values (e.g., to reduce metallic salt in working electrode), the IRange would not be correct.
Maybe measuring the maximum of the absolute values of currents can be the solution. Something like:
currents = [abs(current) for current in currents]
i_max = max( currents )

Great catch. I have updated this in commit 6d95f8e.


Update README.md

Just making the readme look a Little bit more professional

And don't forget to add hacktoberfest-accepted label please

As mentioned, the README page is going to be subject for change after merging couple of PRs. Thanks!


layer: wordsmith non-distributable section

Attempt to clarify when non-distributable policies should be enforced
(only on upload, never on download); as discussed in + fixes #475
Signed-off-by: Jonathan Boulle<EMAIL_ADDRESS>

I like (and don't see anything controversial in) everything about
a2dda98 except for the new SHOULD NOT's reliance on fuzzy “upload” and
“download” wording 1.  Is there any chance of splitting that off
into it's own PR?  Then we can land the cleaner wording quickly while
we hash out whether we need to define upload/download.  Unless I'm the
only person who sees uncertainty around what upload/download mean in
the cache/proxy context ;).

I'm not sure what you're suggesting - just strike the line here for now?

Yeah, drop your new "Implementations SHOULD NOT upload..." line and keep the old "It is implementation-defined..." line.  Then we land this one quick and easy, and you open a new PR with just that "implementation-defined" -> "SHOULD NOT" line swap.

Added a few lines, otherwise, LGTM.
You must have a fine forge to be smithing at such a level.

@jonboulle Ping.

LGTM

@jonboulle Looks like the DCO check failed.

le sigh. now with fixed DCO

LGTM

LGTM


Plugins hangs at "Creating Jenkins instance"

Hello. After watching a co-worker use this plugin I was really impressed by it and tried to copy their configuration to get things set up - it looks like this plugin will greatly improve my workflow. Unfortunately, after selecting the job to run, it seems to hang on the first step without progressing to any future steps. Do you have any idea what I could be doing wrong?
Output in the debug log:
[2020-06-17 16:54:47.140] [Jenkins] [info] Creating Jenkins instance @url=<redacted but I know this URL is valid>, with user=mfasman, password=****

Config:
{
  "jenkins-runner.hostConfigs": {
    "cat-jenkins": {
      "url": "<redacted but I know this URL is valid>",
      "user": "mfasman",
      "useCrumbIssuer": false
    }
  },
  "jenkins-runner.jobs": {
    "mfasman-test": {
      "isDefault": true,
      "runWith": "cat-jenkins",
      "name": "mfasman-test"
    }
  }
}

I have the same issue, any clues on what might be causing this?

@tahaiqbalkhan9  thanks and this helped in giving further useful error messages to debug. I had my job inside several folders within in a view. I had to refer the "http://.../Sudarshan-jobs/job/my-first-pipeline/api/json?pretty=true" and the attribute "fullName" to mention in the settings.json as job name


New api version to remove operationsMonitoring related properties

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Some context
We (IoT Hub team) have been preparing for the deprecation of the operations monitoring feature since October 2017.
With this PR, we are removing OperationsMonitoring properties from our swagger. This is a breaking change, hence the new api-version.
At the same time, we're removing the properties from our latest preview version without incrementing the api version.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-node

Closing PR to see if I could generate another using the open API hub

Automation for azure-sdk-for-go

Automation for azure-sdk-for-js

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/5476
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/5476/commits/3d92aded8396677733d5b9c7c66c969f00d79312

Automation for azure-sdk-for-java


Don't recompile contracts before each test

Contracts need only be compiled once at the beginning of the test run. This should improve speed significantly.

Fixed by 3f79d7e882bb4ed996cf43eddf361f06ee9b5850


Allow reposts section on homepage settings

You can claim search by claim type repost - add this as an option for homepage customization.

Someone recently requested this again, would be some nice low hanging fruit to add.


Clinical Result Observation resource (value)

The value element of the Clinical Result Observation resource reflects the result attribute of the Diagnostic Study, Performed.
This search is only relevant to the Breast Cancer Screening and Colorectal Cancer Screening measures, neither of which need the result attribute. As a result, that element won't be populated.
So, I would recommend removing the Must Send flag from that element, at least until the Diagnostic Study, Performed result attribute is relevant to a UDS measure.

The MUST support only means that you send it if you have it. You dont have to support it if you dont have it. The alignment with US Core and QI Core is one of the reasons we have additional attributes as MUST Support so that the work done here can be reused for all quality measures in general.

Should we update the MS definition in UDS+ then, the current definition has this:
https://fhir.org/guides/hrsa/uds-plus/spec.html#must-support-definition

Systems SHALL be capable of populating data elements as specified by the profiles and data elements are returned using the specified APIs in the capability statement.

Note that MS is always tricky, since normally (and I think, per the UDS+ definition) the MS requirement is against the technology provider / product.  So the EHR in this case.  MS requirements normally don't have anything to do with the operator (the Heath Center).  That is at least how US Core MS support works, and the current UDS+ MS definition is similar enough to imply the same.

Cooper - Good point, we can update and clarify the Must Support further.
We are starting our work on 1.0.2 in a week or so and we can make sure this gets done as part of the work.

Let me know once things are in the current build.  I'd love to have a chance to review (and comment on) the updates planned for 1.0.2 in the current build before publication.


invalid flag in #cgo CFLAGS: -arch

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
localhost:~ wsli$ go version
go version go1.10 darwin/amd64
Does this issue reproduce with the latest release?
YES
What operating system and processor architecture are you using (go env)?
go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/wsli/Library/Caches/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/wsli/go"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.10/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.10/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/0j/8lghc3kd7yx2c_1lp9zhc6_h0000gn/T/go-build160152071=/tmp/go-build -gno-record-gcc-switches -fno-common"
localhost:~ wsli$ cd /Users/wsli/go/
What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
What did you expect to see?
no error
What did you see instead?


Add feature to enable scrolling for Jupyter cell outputs?

I really like the beta features that allow you to control the page layout with Jupyter cell tags (such as "popout"). I was wondering about the possibility of enabling scrolling for Jupyter cell outputs in a similar fashion.
To clarify, if the output of a cell in a Jupyter notebook is super long, you can right-click and select "Enable Scrolling for Outputs." I find this option very handy. It would be cool if you could do the same thing with Jupyter Book.

that's a clever idea! I think this could just be a matter of adding a CSS rule to Jupyter Book like:
div.tag_scroll_output div.output_wrapper {
    max-height: 200px;
    overflow-y: scroll;
}

I think one main question is: what should be the max height used? Maybe whatever the classic notebook interface defaults to?

Cool! Yeah I think the default Jupyter notebook max height would be great.

any chance you'd be interested in giving a PR a shot to implement this? Otherwise I can try to get to it sometime when I have a moment.
FWIW, I think we'd need to add the extra CSS rule here:
https://github.com/jupyter/jupyter-book/blob/master/jupyter_book/book_template/_sass/page/components/_components.page.scss#L62
then some documentation explaining the new feature (probably on the "controlling page layout" page)


zoxide: 0.9.2 -> unstable-20-11-2023

Description of changes
latest version of nushell will break with zoxide. The fix landed on master, but the maintainer hasn't had time to release a new version (I've sent him 3 messages in the last 2 weeks).
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 273882 run on x86_64-linux 1

5 packages built:

felix-fm
vimPlugins.telescope-zoxide
vimPlugins.zoxide-vim
yazi
zoxide

Result of nixpkgs-review pr 273882 run on x86_64-linux 1

5 packages built:

felix-fm
vimPlugins.telescope-zoxide
vimPlugins.zoxide-vim
yazi
zoxide


Folders with a different language from Cpanel's webmail

I've tried all the methods and none work.

@vitorliduario Please indicate which document you referring and what is your feedback to improve it. Thanks.

@vitorliduario We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if you see an improvement is required in the specific area of this documentation. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Output path parameter

Can you add an output path parameter for the 'convert' function? Then there would be a copy of the converted files without modifying the originals. This would save a step for engineers to have to copy the files, then run the convert against safely.
Thank you.
Mike

Hey Mike,
sorry about the delay, but v1.1.8 has that implemented.
Release pipeline running right now, by the time you get this notification it should be live in the gallery :)


Typo fixes in the documentation

@tomzx thanks for your contribution. For this pr, could you revert the changes to chinese doc? because we have a dedicated pipeline to do the translation.

@QuanluZhang Done. Let me know if there's anything else that needs to be done :)


jsdom: specify omitJSDOMErrors: true.

See https://github.com/tmpvar/jsdom#virtual-consoles
This fixes #322 for me. So the behavior is like before the jsdom switch.
/CC @mikelambert @RyanZim

Also, with this change protocol-relative URLs seem to work again, or at least don't throw.

Coverage remained the same at 97.328% when pulling c43804a7edd5c1ee7bb6fde9963fb619dc208020 on omitjserrors into c4333d2bf20914a536e804d12695095e56564411 on master.

OK, I believe this is the opposite of what we want. So I'm not sure how to proceed... Note that this really works for me with the updated jsdom.

I believe JS errors (for whatever reason) will indicate the page is not fully set up, and so it is impossible for uncss to make the traditional guarantees it makes.
It just so happens that phantom was extremely lenient in ways that none of us knew. But I don't think anyone would argue that is a desirable state.
My argument, if someone were complaining to me about this in a bug/issue:

don't use scheme-relative urls. specify the scheme
possibly implement (if it's not already implemented) a "base path against which to resolve host-relative-urls" feature, so one could continue to use host-relative urls
do not run uncss on raw html files. If you want to load host-relative content, you need to run on a host. set up a server for the duration of the uncss run, and run it against that

However, if you want to make an uncss flag that causes it to "ignore errors and potentially generate malformed pages at your own peril" escape hatch, then that would be fine with me too.

Agree :100: with @mikelambert.

if you want to make an uncss flag that causes it to "ignore errors and potentially generate malformed pages at your own peril" escape hatch, then that would be fine with me too.

I think this is a good idea.

All right, sounds a good idea. I'll try to implement it when I have some time.


Sg/area dist debug

I realized that I missed a few geometry types that were coming up in my simulations.
I also realized that my code failed with empty geometries as it was trying to access the first point. This then led me to the discovery of an issue with the implementation of isempty at least with LibGEOS. So now I have to check isempty and find if there is a non-zero number of points to determine the type of the points within a geometry that returns an area of 0.
import LibGEOS as LG
import GeoInterface as GI

p = LG.readgeom("POLYGON EMPTY")
GI.isempty(p)  # false
GI.npoint(p) # 0

This seems like too much work just to return 0. I am wondering if it would be bad to just return an Int 0 for everything but non-empty polygons / multipolygon / collections.
This isn't the best type-wise, but there is no guarantee that we can even determine the type.
Thoughts?

I wanted to preserve the flexibility so that if I run a simulation with Float32 or Float64 polygons, the area returns the correct type. But I can see why that is tricky, especially with the empty geometries for which we would have to default to something. Do you think it is better just for it to return Float64 so that the user can plan?

Maybe default to Float64 but let the user pass in the type?

Okay, I updated the type stuff! They all have optional parameters now. I also just simplified some stuff.
Something I am noting is that I am doing GI.getpoint(geom, i) a lot in order to deal with "closed" curves. This is my way of making it so that it doesn't matter if a Geometry library repeats the last coordinates in linear rings / polygons, we still repeat the last point for our algorithms. I don't have an idea for a better way of doing this though.
As discussed in #32, this can be problematic if a library does a poor job of implementing GeoInterface. I kinda feel like that is the library's fault though, not ours. For example, using tuples to convert an input geometry into a GeoInterface geometry feels like cheating, because we aren't really dealing with an arbitrary polygon, we're converting a given polygon to a specific type...
However, if you think this is still slower than GI.getpoint(geom) and using the iterator regardless, then we can think up a new way of iterating. Maybe that can be a separate PR though.