[docs] Docs for Updater Module Missing?

Hello Tauri Community!
I am learning Tauri product for the first-time, and note, very new to Rust too.
I was looking up your documentation to answer below:
How do I integrate update capabilities for my Tauri app? For example, 'Version 2.0.0 is out now! Click to update!'

Also in summary:

Is there a third-party service to host your Tauri desktop app for downloading?
Can we host our own service for visitors to download our Tauri desktop app? And to push new app versions out automatically? Similar to an 'Apple Store' or 'Google Play Store'?

I found this page here, https://tauri.studio/docs/api/js/modules/updater#updater but the markdown link is broken or not found. The Docusaurus search bar is not helping thus far with the current search results, is this page located elsewhere or have been renamed?
Lastly, additional resource links regarding how I can answer my question above would be great. Making your own desktop app available for download (and pushing version updates) will be awesome!

The link you mentioned changed to https://tauri.studio/api/js/modules/updater
Other than that, you can find general information about the updating process here: https://tauri.studio/guides/distribution/updater

Thanks a bunch @JonasKruckenberg for the swift reply, much appreciated 😃 !
Noted, valuable and informative points you've shared, for me to digest. Especially about your answer for Question #2, and including your Edit (additional tip) portion.
Anyway, very much appreciated 😃 I'll have to approach my Tauri app project step by step moving forward 😅
Lastly, you've answered my initial question above, the two correct docs links have been noted - cheers! Have a good one!


CircleCI - run nightly UAT tests

Tests was ran 00:00 UTC last night: https://circleci.com/workflow-run/140fb9a6-eb3a-4ef2-bc97-7f6c287ede74 (indeterminate ?)
Successful builds can be found here:

https://circleci.com/gh/aeternity/epoch/1542
https://circleci.com/gh/aeternity/epoch/1527

However, I had to increase the test timeouts in 3e0e94df1244a1711af67a550c4aec44efab9c82 to make it work in CircleCI

I'll rework the commit history before merging.


Azure Communication Calling iOS SDK version 2.1.0

@xumo-95 please post the link to the approved APIView for this release.

This is the ApiView diff of this release. There's no changes on the APIs.
https://apiview.dev/Assemblies/Review/14e758f61b3b4a8088612a9d424a1cdd?revisionId=d0be5c7e31224921b90e9fa9f590e43d&diffRevisionId=cac63cb3806444a195b4d2e9a2824a82&doc=False&diffOnly=False


Messages "from future" not appear in ChatActivity

As a suggestion
When we open chat activity, it loads only messages older than current time, so it may cause wrong behaviour:
if user has wrong time on a device, like two minutes later than current time, his message will not appear in ChatActivity on other device with correct time until the time of message come. However, if we subscribe for new messages, the event will come. In my case new messages counter notifies about new messages, but when I open ChatActivity, they not appear.
I suggest to change AbstractThreadHandler.loadMoreMessagesForThread(), so if fromMesage == null, then load all messages, not from current date.
Thanks a lot anyway, the library is great!

OMG, thanks @Yariko-chan you solved the issue that me and developers could never replicate

I tried setting the time to the future but I can't replicate this issue. Even with the time set incorrectly, messages are still displayed correctly.
I've reviewed the code and the logic look like this:

Are there some messages in the thread? If so listen to messages starting at the timestamp of the last message
Is the thread deleted? If yes, listen to messages starting at the time of thread deletion.
Otherwise listen to all messages.

Since all the timestamps are set by Firebase, there should never be a time when the device's current time interferes with the listeners. I even tested a case where I create a thread, close the app, set the time to an incorrect value, re-open the app and send a message. Messages still came through correctly.
To follow this up further, I would you to send me a demo project which is exhibiting this issue. I'm closing the issue for now, but if you still have this problem and can send me a demo project, I will reopen it.


[1.12] Automated Bump DC/OS UI v2.25.11

High-level description
What features does this change enable? What bugs does this change fix?
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:
DCOS_OSS-4597
Related tickets (optional)
Other tickets related to this change:
DCOS_OSS-4597
Checklist for all PRs

[ ] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ ] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label [Ready for Review]


add --csr-only option

The flag --use-csr is no longer available as of 1.13 on being replaced by --csr-only.

/assign @ryanmcginnis

leaving for this week's PR wrangler.

Thanks for the PR @frederiko !!! the updates on https://deploy-preview-12766--kubernetes-io-master-staging.netlify.com/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/ and also checked https://kubernetes.io/docs/setup/release/notes/#sig-cluster-lifecycle. The updates look good to me. I am assigning this PR to someone in sig cluster life cycle for a technical review.

/sig cluster-lifecycle

/assign @neolit123

@neolit123 could you please review this PR for technical accuracy.

Got it. Will do.

@neolit123 made suggested changes.

/approve


Gateway 3

gateway 3 most of the time unavailable in HA and also the child ZigBee.
Restart HA and the hub don't work.
The hub is close to the router and to the child ZigBee.
The hab and ZigBee child works well and connected well to the mi home app.

same here

This error originated from a custom integration.
Logger: custom_components.xiaomi_gateway3.core.mini_miio
Source: custom_components/xiaomi_gateway3/core/mini_miio.py:324
Integration: Xiaomi Gateway 3 (documentation, issues)
First occurred: 10:24:40 (1 occurrences)
Last logged: 10:24:40
<IP_ADDRESS> | Device offline
Logger: homeassistant.components.zha.core.channels.base
Source: components/zha/core/channels/base.py:457
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 08:18:55 (3 occurrences)
Last logged: 19:36:25
[0x7B00:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0x7b00:1:0x0006]: Message send failure'), DeliveryError('[0x7b00:1:0x0006]: Message send failure'), DeliveryError('[0x7b00:1:0x0006]: Message send failure'), DeliveryError('[0x7b00:1:0x0006]: Message send failure')]
[0xE0B3:1:0x1000]: Couldn't get list of groups: ApplicationController is not running
[0x2010:1:0x1000]: Couldn't get list of groups: ApplicationController is not running
Logger: bellows.zigbee.application
Source: /usr/local/lib/python3.9/site-packages/bellows/zigbee/application.py:735
First occurred: 08:19:46 (8 occurrences)
Last logged: 10:28:57
Watchdog heartbeat timeout:

after HA reload:
2022-04-17 19:46:56  DEBUG    main          SysInfo: {'installation_type': 'Home Assistant OS', 'version': '2022.4.5', 'dev': False, 'hassio': True, 'virtualenv': False, 'python_version': '3.9.9', 'docker': True, 'arch': 'x86_64', 'timezone': 'Europe/Rome', 'os_name': 'Linux', 'os_version': '5.10.108', 'user': 'root', 'supervisor': '2022.04.0', 'host_os': 'Home Assistant OS 7.6', 'docker_version': '20.10.9', 'chassis': 'vm'}
2022-04-17 19:46:57  DEBUG    main          Loaded from MiCloud 1 devices
2022-04-17 19:47:05  DEBUG    base          <IP_ADDRESS> [BASE] Start main loop
2022-04-17 19:47:06  DEBUG    base          <IP_ADDRESS> [BASE] Prepare gateway gw3 with firmware 1.5.0_0102
2022-04-17 19:47:09  DEBUG    base          <IP_ADDRESS> [BASE] 54ef44313b8a (lumi.gateway.mgl03) setup gateway ZNDMWG03LM ZNDMWG02LM: alarm, command, data, cloud_link, led, gateway
2022-04-17 19:47:09  DEBUG    base          <IP_ADDRESS> [MIOT] 54ef44313b8a (lumi.gateway.mgl03) read {'mi_spec': [{'siid': 3, 'piid': 1}, {'siid': 3, 'piid': 22}]}
2022-04-17 19:47:09  DEBUG    base          <IP_ADDRESS> [BASE] Init ZHA mode
2022-04-17 19:47:13  DEBUG    base          <IP_ADDRESS> [BASE] Patch Bluetooth
2022-04-17 19:47:13  DEBUG    base          <IP_ADDRESS> [BASE] Applied 0 patches to daemons
2022-04-17 19:47:13  DEBUG    base          <IP_ADDRESS> [BASE] MQTT connected
2022-04-17 19:51:56  DEBUG    base          <IP_ADDRESS> [BASE] Gateway time offset: -0.6795921325683594

I found the problem, after powerout the ip changed therefote it couldn't connect.
I changed the ip and connected again with the token and telnet.
now I set static ip for the gateway hoping it will stay connected for a long period of time

not in my case, the IP is always the same. The problem started with upgrade to 2022.4.4 or 2022.4.5   I did upgrade one after the other so don't know which one broken zha

for some reasons, have to switch off-on all the sensors, removing the battery, to restablish the connection. Re-pairing not required


Issue trying to build from source

When building from source, I'm getting:
bash-3.2$ make dist
make: *** No rule to make target templates/README.md', needed by ofcourse/bindata.go'.  Stop.

This should be fixed in #4.


Web UI - OIDC Issue

Hello!
I have Incus OIDC set up with Keycloak. This configuration has been working well for a while, but now (update?) when I click the login SSO button, it gets stuck on the /oidc/login page. There are no URL parameters, no body content, and no errors to debug. It just shows an empty page and doesn't continue redirecting me to the configured OIDC provider.

@stgraber and if it is somehow possible to disable the built-in login, I would honestly break out in tears. The authentication situation has given me nothing but issues, even in LXD-UI times, due to the setup I'm working with since there are additional security measures in place that make the built-in Incus UI authentication completely obsolete. Maybe by applying some changes to the incus-ui code?

Hello,
I think I am facing the same issue, and I see this when running journalctl -xeu incus (the timestamp corresponds to the login issue):
juil. 13 17:06:18 REDACTED_HOSTNAME incusd[3108957]: time="2024-07-13T17:06:18+01:00" level=warning msg="Rejecting request from untrusted client" ip="REDACTED_IP:40240"

I'm also going to investigate on the Keycloak side to see if there is an issue there.

We're not planning on allowing disabling HTTPS authentication Incus.
That said, you do have workarounds you can use, most commonly:

Run a proxy going from HTTPS to HTTPS with a hardcoded trusted TLS certificate
Run a proxy going from HTTPS to the local unix socket


Set moduleLocation as jar resource

squashed, renamed some vars, and merged as https://github.com/spring-projects/spring-bus/commit/29faeae51a23618bff1af1bc94a0bebe9fc1e8a6


[CLI] Kamel run does not check source file exists

I wonder if this is a desired behavior. When running any integration which is missing the source file (ie kamel run xyz where xyz file does not exists), the CLI does not check if the file exists, creating an empty integration. I wonder if this is a bug and we should verify that the file exists and returning an error instead.

Duplicate of #1911

Duplicate of #1911


[HUDI-777] Update Deltastreamer param description for --target-table

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
Committer checklist

[x] Has a corresponding JIRA in PR title & commit

[x] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Welcome @iftachsc 👍


UploadedFile file property missing

In https://github.com/slimphp/Slim/blob/3.x/Slim/Http/UploadedFile.php#L143
It does not exist as a protected member.

Fixed.


Lindalu word selection commands

Docs Build status updates of commit 8599410:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch lindalu-word-selection-commands has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Issues Installing LightWeight MMM on M1 MACOS Montery

Tried installing lightweight_mmm using the following commands on python ver 3.9
pip install lightweight_mmm
I am currently running to the following error
Collecting lightweight_mmm
  Using cached lightweight_mmm-0.1.1-py3-none-any.whl (41 kB)
  Using cached lightweight_mmm-0.1.0-py3-none-any.whl (40 kB)
Requirement already satisfied: jax>=0.2.21 in ./miniforge3/envs/tf_env/lib/python3.9/site-packages (from lightweight_mmm) (0.3.23)
ERROR: Cannot install lightweight-mmm==0.1.0, lightweight-mmm==0.1.1, lightweight-mmm==0.1.2, lightweight-mmm==0.1.3, lightweight-mmm==0.1.4, lightweight-mmm==0.1.5 and lightweight-mmm==0.1.6 because these package versions have conflicting dependencies.

The conflict is caused by:
    lightweight-mmm 0.1.6 depends on tensorflow>=2.7.2
    lightweight-mmm 0.1.5 depends on tensorflow>=2.7.2
    lightweight-mmm 0.1.4 depends on tensorflow==2.7.2
    lightweight-mmm 0.1.3 depends on tensorflow==2.7.2
    lightweight-mmm 0.1.2 depends on tensorflow==2.5.3
    lightweight-mmm 0.1.1 depends on tensorflow==2.5.3
    lightweight-mmm 0.1.0 depends on tensorflow==2.4.1

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
(tf_env)

Any help would be greatly appreciated

Hey @freudianfaults !
I dont have direct experience on M1 Macs but I believe they forked tensorflow under tensorflow-macos.
You might have to install that first and then proceed installing LMMM.  You can save this as a requirements.txt file and then install it from it (made the switch for your alread):
absl-py
arviz==0.11.2
dataclasses;python_version<'3.7'
immutabledict>=2.0.0
jax>=0.3.18
jaxlib>=0.3.18
matplotlib==3.3.4
numpy>=1.12
numpyro>=0.9.2
pandas>=1.1.5
scipy
seaborn==0.11.1
sklearn
tensorflow-macos
typing_extensions;python_version<'3.8'

Please feel free to report back as I am unaware of how well this will work.

Hi pablo, thanks for your quick response. I already have tensorflow-macos preinstalled before my initial attempt but still ran into the same error above.
I have also attempted using your requirements.txt with the following terminal command
pip install lightweight_mmm -r requirements.txt
and also
pip install -r requirements .txt
followed by
pip install lightweight_mmm
but still ran into the same error.
Could this be a compatibility issue with tensorflow-macos ?

You might have to add --no-deps when Installing lightweight_mmm directly since that will try to install tf as well.
I not super familiar with tensorflow-macos but tf is a very side dependency which is only used for a couple things so I think it should be fine.

Hi @pabloduque0 the solution you've provided works perfectly ! Thank you so much for your help !


Reflect latest release to README.md

Please update a version number in README.md too.

I merged it
Thank you


Create an API Trigger for the Process - Missing shippingCountry field

Tutorials: https://developers.sap.com/tutorials/spa-create-process-api-trigger.html
Step 3. Modify the Process, task 2. Approval Form, Modify the Inputs section.
The tutorial screenshot lists the shippingCountry field in the Process Content for salesOrderDetails, but this is not present when I perform the tutorial and is a required field in the Approval Form. As a work around I have used the shippingCategory field instead of the shippingCountry field.
Please confirm using shippingCategory instead of shippingCountry is valid.
See screenshots in the attached document.
Issue - Missing shippingCountry field.docx
Kind regards, Andrew

Hi @ASRHARDING
The shipping category field can also be mapped and is valid


本地部署运行scrapy crawl zhihu 报错

2021-03-24 18:26:53 [scrapy.downloadermiddlewares.redirect] DEBUG: Redirecting (301) to <GET http://www.zhihu.com/app/> from <GET https://www.zhihu.com/app?auto_download=true&utm_source=zhihu&utm_campaign=guest_feed&utm_content=guide>
2021-03-24 18:26:53 [scrapy.core.engine] DEBUG: Crawled (400) <GET https://www.zhihu.com?utm_source=zhihu&utm_campaign=guest_feed&utm_content=guide> (referer: https://www.zhizhu.com)
2021-03-24 18:26:53 [scrapy.spidermiddlewares.httperror] INFO: Ignoring response <400 https://www.zhihu.com?utm_source=zhihu&utm_campaign=guest_feed&utm_content=guide>: HTTP status code is not handled or not allowed
2021-03-24 18:26:54 [scrapy.core.engine] DEBUG: Crawled (200) <GET https://www.zhihu.com/signin?next=http%3A%2F%2Fwww.zhihu.com%2Fquestion%2F28227721> (referer: https://www.zhizhu.com)
2021-03-24 18:26:54 [scrapy.core.scraper] ERROR: Spider error processing <GET https://www.zhihu.com/signin?next=http%3A%2F%2Fwww.zhihu.com%2Fquestion%2F28227721> (referer: https://www.zhizhu.com)
Traceback (most recent call last):
File "/usr/local/python3/lib/python3.7/site-packages/scrapy/utils/defer.py", line 120, in iter_errback
yield next(it)
File "/usr/local/python3/lib/python3.7/site-packages/scrapy/utils/python.py", line 347, in next
return next(self.data)
File "/usr/local/python3/lib/python3.7/site-packages/scrapy/utils/python.py", line 347, in next
return next(self.data)
File "/usr/local/python3/lib/python3.7/site-packages/scrapy/core/spidermw.py", line 64, in _evaluate_iterable
for r in iterable:
File "/usr/local/python3/lib/python3.7/site-packages/scrapy/spidermiddlewares/offsite.py", line 29, in process_spider_output
for x in result:
File "/usr/local/python3/lib/python3.7/site-packages/scrapy/core/spidermw.py", line 64, in _evaluate_iterable
for r in iterable:
File "/usr/local/python3/lib/python3.7/site-packages/scrapy/spidermiddlewares/referer.py", line 340, in
return (_set_referer(r) for r in result or ())
File "/usr/local/python3/lib/python3.7/site-packages/scrapy/core/spidermw.py", line 64, in _evaluate_iterable
for r in iterable:
File "/usr/local/python3/lib/python3.7/site-packages/scrapy/spidermiddlewares/urllength.py", line 37, in
return (r for r in result or () if _filter(r))
File "/usr/local/python3/lib/python3.7/site-packages/scrapy/core/spidermw.py", line 64, in _evaluate_iterable
for r in iterable:
File "/usr/local/python3/lib/python3.7/site-packages/scrapy/spidermiddlewares/depth.py", line 58, in
return (r for r in result or () if _filter(r))
File "/usr/local/python3/lib/python3.7/site-packages/scrapy/core/spidermw.py", line 64, in _evaluate_iterable
for r in iterable:
File "/home/search/FunpySpiderSearchEngine/mtianyanSpider/spiders/zhihu.py", line 113, in parse_question
item_loader.add_value("zhihu_id", question_id)
File "/usr/local/python3/lib/python3.7/site-packages/itemloaders/init.py", line 190, in add_value
self._add_value(field_name, value)
File "/usr/local/python3/lib/python3.7/site-packages/itemloaders/init.py", line 208, in _add_value
processed_value = self._process_input_value(field_name, value)
File "/usr/local/python3/lib/python3.7/site-packages/itemloaders/init.py", line 312, in _process_input_value
proc = self.get_input_processor(field_name)
File "/usr/local/python3/lib/python3.7/site-packages/itemloaders/init.py", line 293, in get_input_processor
self.default_input_processor
File "/usr/local/python3/lib/python3.7/site-packages/itemloaders/init.py", line 308, in _get_item_field_attr
field_meta = ItemAdapter(self.item).get_field_meta(field_name)
File "/usr/local/python3/lib/python3.7/site-packages/itemadapter/adapter.py", line 89, in get_field_meta
return MappingProxyType(self.item.fields[field_name])
KeyError: 'zhihu_id'

@Holyfiled 需要在mtianyanSpider/cookies/zhihu.cookie 替换自己登陆后的cookie哈


Do you have this wonderful library for Swift?

Just use a bridging header and import it that way.

It does not contain nullability information so the generated swift headers will force unwrap variables (unsafe)


Question: why does mmseqs taxonomy not calculate LCA?

Why does mmseqs taxonomy not calculate LCA for a query but the best hit?

You mean for nucl-nucl taxonomy searches? The current implementation of the algorithm doesn't support it yet and we haven't had the resources to implement it yet. The various protein based searches all use LCA.

Sorry, yes I meant the nucl-nucl obviously.
Ah, OK, I was wondering if there is a technical reason, because I could not think of any ;)
Case closed...

There is a technical reason: Our nucleotide alignment algorithm needs one seeding point to align. This seeding point is not correctly propagated for the LCA in the nucl-nucl taxonomy. It's a bit tricky to solve, but it would mostly need a few days of thinking and work.


UI improve

i have added some animations to fa-icons, improved styling, added static user icon with image and logout button, and some hover effects too.
screenshot attached:

Hey @Somgester , please include the issue tag that you have resolved.

issues resolved:
#12 Add User Profile Section.
#27 Enhance UI design for better User Experience.
#15 change twitter logo to new logo('X').
#39 Add FAQs section to the project.

issues resolved: #12 Add User Profile Section. #27 Enhance UI design for better User Experience. #15 change twitter logo to new logo('X'). #39 Add FAQs section to the project.

OK, but this operates on a first-come, first-served basis. You need to be assigned an issue before making a PR.

so, just assign me those issues and merge it.
or what can i do now?

so, just assign me those issues and merge it.
or what can i do now?

You can explore the project and find new issues or enhancements,and raise a new issue.


Code style violations

The current coding style is specified in .editorconfig.
It's quite liberal that only requires space for indentation and trim trailing whitespace.
I run CheckStyle with these two rules;
it shows that most parts of the project conform the style requirements. But there're still a number of violations. For example, the following two files use tab for indentation instead of space:
api/src/main/java/org/neo4j/ogm/config/Configuration.java
api/src/main/java/org/neo4j/ogm/driver/AbstractConfigurableDriver.java
On a follow-up note, shall we use CheckStyle to enforce the code style (as is neo4j doing) as a part of integrating test?
Thanks!

There is current work done for SpotBugs and Checkstyle integration. c4fb1f5a085d5ebd039a436a28e393f5703d6816
Closing this issue because we are introducing checks now step by step.


ArchiveTest.recordAndReplayExclusivePublication Failed

io.aeron.archive.ArchiveTest > recordAndReplayExclusivePublication[threading modes: driver=SHARED archive=SHARED] STANDARD_ERROR
io.aeron.archive.ArchiveTest failed with random seed:<PHONE_NUMBER>89147
io.aeron.archive.ArchiveTest > recordAndReplayExclusivePublication[threading modes: driver=SHARED archive=SHARED] FAILED
java.lang.AssertionError:
Expected: is <2148>
but: was <2149>
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
at io.aeron.archive.ArchiveTest.validateFragment1(ArchiveTest.java:624)
at io.aeron.archive.RecordingFragmentReader.controlledPoll(RecordingFragmentReader.java:191)
at io.aeron.archive.ArchiveTest.validateArchiveFile(ArchiveTest.java:599)
at io.aeron.archive.ArchiveTest.postPublicationValidations(ArchiveTest.java:362)
at io.aeron.archive.ArchiveTest.recordAndReplayExclusivePublication(ArchiveTest.java:206)

This failure can be replicated if the seed is set in the test to :<PHONE_NUMBER>89147.

Turns out the test has invalid assumptions. The above seed will have 320 remaining in the starting term and the first message ends up being 874 bytes and does not fit so a padding record is inserted and the term is rotated thus the actual termId is one greater than the expected.


Typo "Azure file storage"→"Azure File Storage"

https://docs.microsoft.com/en-us/troubleshoot/azure/general/request-body-large
https://github.com/MicrosoftDocs/SupportArticles-docs/blob/main/support/azure/general/request-body-large.md
#PingMSFTDocs

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Docs Build status updates of commit 4773ddd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

support/azure/general/request-body-large.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 2c8c809:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed]

Cannot sync git repo to specified commit because ref +refs/pull/677/merge has been deleted or has been force pushed.
 If this is pull request, please ensure it is mergeable (no merge conflict) and open (not closed).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Tiller CrashLoopBackOff Kubernetes v1.14

Trying to install Helm on a newly created cluster using Kubernetes 1.14, with Kubeadm and Flannel l2bridge networking.
Output of helm version:
Client: &version.Version{SemVer:"v2.13.0", GitCommit:"79d07943b03aea2b76c12644b4b54733bc5958d6", GitTreeState:"clean"}
Error: could not find a ready tiller pod
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:53:57Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:45:25Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
Kubeadm, Ubuntu 18.04 LTS Server Master and Node
Output of kubectl describe:
Name:               tiller-deploy-79db89ccdb-kglq9
Namespace:          kube-system
Priority:           0
PriorityClassName:
Node:               k8s-linux-worker1/<IP_ADDRESS>
Start Time:         Thu, 28 Mar 2019 19:22:50 +0000
Labels:             app=helm
name=tiller
pod-template-hash=79db89ccdb
Annotations:
Status:             Running
IP:                 <IP_ADDRESS>
Controlled By:      ReplicaSet/tiller-deploy-79db89ccdb
Containers:
tiller:
Container ID:   docker://86ff05c2e34e09f8324ee919595b61f7d033b0b2fbc6a16d94a4bbd7e0af3820
Image:          gcr.io/kubernetes-helm/tiller:v2.13.0
Image ID:       docker-pullable://gcr.io/kubernetes-helm/tiller@sha256:c4bf03bb67b3ae07e38e834f29dc7fd43f472f67cad3c078279ff1bbbb463aa6
Ports:          44134/TCP, 44135/TCP
Host Ports:     0/TCP, 0/TCP
State:          Waiting
Reason:       CrashLoopBackOff
Last State:     Terminated
Reason:       Error
Exit Code:    2
Started:      Thu, 28 Mar 2019 19:30:07 +0000
Finished:     Thu, 28 Mar 2019 19:30:32 +0000
Ready:          False
Restart Count:  7
Liveness:       http-get http://:44135/liveness delay=1s timeout=1s period=10s #success=1 #failure=3
Readiness:      http-get http://:44135/readiness delay=1s timeout=1s period=10s #success=1 #failure=3
Environment:
TILLER_NAMESPACE:    kube-system
TILLER_HISTORY_MAX:  0
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-f8xlp (ro)
Conditions:
Type              Status
Initialized       True
Ready             False
ContainersReady   False
PodScheduled      True
Volumes:
default-token-f8xlp:
Type:        Secret (a volume populated by a Secret)
SecretName:  default-token-f8xlp
Optional:    false
QoS Class:       BestEffort
Node-Selectors:
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type     Reason     Age                  From                        Message

Normal   Scheduled  10m                  default-scheduler           Successfully assigned kube-system/tiller-deploy-79db89ccdb-kglq9 to k
8s-linux-worker1
Normal   Pulled     9m39s (x3 over 10m)  kubelet, k8s-linux-worker1  Container image "gcr.io/kubernetes-helm/tiller:v2.13.0" already present on machine
Normal   Created    9m39s (x3 over 10m)  kubelet, k8s-linux-worker1  Created container tiller
Normal   Killing    9m39s (x2 over 10m)  kubelet, k8s-linux-worker1  Container tiller failed liveness probe, will be restarted
Normal   Started    9m38s (x3 over 10m)  kubelet, k8s-linux-worker1  Started container tiller
Warning  Unhealthy  9m19s (x8 over 10m)  kubelet, k8s-linux-worker1  Liveness probe failed: Get http://<IP_ADDRESS>:44135/liveness: net/http
: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Warning  Unhealthy  9m18s (x6 over 10m)  kubelet, k8s-linux-worker1  Readiness probe failed: Get http://<IP_ADDRESS>:44135/readiness: net/ht
tp: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Warning  BackOff    29s (x32 over 8m9s)  kubelet, k8s-linux-worker1  Back-off restarting failed container

Wiping the entire node and re-adding to the cluster was fine.  Assuming something was wrong with networking.


camera module on windows

Hi
I am wondering if i only need the camera module,  are there any issues with compilation the code on windows?
cheers,
CS

Hi @Postea-CS we are currently trying to port the ifm3d (successor of libo3d3xx) to windows. It looks like the hardest part is getting the xmlrpc-c compiled. If you are interested I can share my xmlrpc-c CMake stuff I have at the moment.

@Postea-CS I have some good news for you. Today I released a Version of xmlrpc-c which is capable to be build with the latest version of CMake on Visual Studio 2017 Community Edition. I requires a libcurl as transport layer. If there are any questions, feel free to create an issue on this project.

:exclamation: This is a preliminary documentation how to build the ifm3d on Windows. Most concepts should apply to the libo3d3xx as-well
How to build ifm3d library from source on Windows.
Prepare dependent tools
Make sure that you have installed CMake and VS2017 64bit before you move to the next step.

CMake v3.9.1
Visual Studio Community 2017

Download dependencies
Start with downloading Glog, Gtest and XMLRPC libraries from repository listed below to 3rdParty folder.

Gtest
Glog
xmlrpc-c This is a special version with CMake support. Follow the instructions how to build in this Readme
curl For the xmlrpc-c library

Install dependencies
Install the necessary libraries on your system. In the following example we assume D:\3rdparty is used as a base path.

Boost v1.64.0
PCL v1.8.1
OpenCV v3.3

In case of using Visual Studio 15 2017 we need to adapt "opencv/build/OpenCVConfig.cmake" file.
Replace:
    elseif(MSVC_VERSION EQUAL 1910 OR MSVC_VERSION EQUAL 1911)
        set(OpenCV_RUNTIME vc15)

With:
    elseif(MSVC_VERSION EQUAL 1910 OR MSVC_VERSION EQUAL 1911)
        set(OpenCV_RUNTIME vc14)

After instalation you need to set paths to each of three libraries in "ifm3d/CMakeLists.txt" file.
# Where to find Boost path
    set(BOOST_INCLUDEDIR    "D:/locallibs/boost_1_64_0/")
    set(BOOST_LIBRARYDIR    "D:/locallibs/boost_1_64_0/lib64-msvc-14.1")
    set(BOOST_ROOT          "D:/locallibs/boost_1_64_0/boost/")
# Where to find OpenCV path
    set(OpenCV_DIR          "D:/locallibs/opencv/build/")
# Where to find PCL path
    set(PCL_DIR             "D:/locallibs/pcl1.8.1/cmake/")

Generate VisualStudio project via CMake.
Due to the fact the Visual Studio compiler needs some command line variables correct initialized. It is recommended to use the the Visual Studio command line.
$ mkdir build
$ cd build
$ cmake ..\ifm3d -G "Visual Studio 15 2017 Win64" -DBUILD_SHARED_LIBS=ON -DMUST_BUILD_CURL_CLIENT=ON -DBUILD_TESTING=OFF

Build projects in Visual Studio 2017 64bit.
You will find IFM3D.sln in build folder, created in previous step, launch it.

:exclamation: For the libo3d3xx library it is recommended to build the modules separately and not with the top-level CMake file.

Closing out stale issues (older than a year). Feel free to reactivate as appropriate.


tracers/qemu.patch: Rebased the patch to qemu 2.5.1.

tracers/qemu_build.sh: Updated the qemu version and the hash.

Hello!

Updated tci.c to address the CPUArchState/CPUState rename http://wiki.qemu.org/Features/QOM/CPU.
Took 'extern' off filename in main.c.

I tested that this patch applies cleanly to the current qemu, compiles with the same ./configure line as in the qira script and that make check suceeds.

Nice! How did you do the rebase? Git? It'd be nice to have a good way to do this for maintenance purposes. I recall someone tried to do this before and it wasn't straightforward.

I applied the old patch to the new source tree, it tries its best:
$ patch -p1 -d qemu-2.5.1-patched/ < qemu.patch
patching file disas.c
Hunk #1 succeeded at 172 (offset -15 lines).
Hunk #2 FAILED at 196.
Hunk #3 FAILED at 226.
Hunk #4 succeeded at 237 with fuzz 2 (offset -71 lines).
2 out of 4 hunks FAILED -- saving rejects to file disas.c.rej
patching file include/librarymap.h
patching file linux-user/elfload.c
Hunk #1 succeeded at 1808 (offset 20 lines).
Hunk #2 succeeded at 1877 (offset 20 lines).
patching file linux-user/main.c
Hunk #1 succeeded at 275 with fuzz 1 (offset -6 lines).
Hunk #2 succeeded at 3900 (offset 259 lines).
Hunk #3 succeeded at 3956 with fuzz 1 (offset 259 lines).
patching file linux-user/qemu.h
Hunk #2 succeeded at 364 (offset -11 lines).
Hunk #3 succeeded at 378 (offset -11 lines).
Hunk #4 succeeded at 399 (offset -11 lines).
Hunk #5 succeeded at 419 (offset -11 lines).
patching file linux-user/strace.c
patching file linux-user/strace.list
Hunk #2 succeeded at 1519 (offset 12 lines).
patching file linux-user/syscall.c
Hunk #1 succeeded at 5663 with fuzz 1 (offset 326 lines).
Hunk #2 succeeded at 10031 (offset 490 lines).
patching file tci.c
Hunk #2 succeeded at 414 with fuzz 2 (offset -6 lines).
Hunk #3 succeeded at 707 with fuzz 2 (offset -7 lines).
Hunk #4 succeeded at 1008 (offset -7 lines).
Hunk #5 succeeded at 1016 (offset -7 lines).
Hunk #6 succeeded at 1039 with fuzz 1 (offset -20 lines).
Hunk #7 succeeded at 1098 (offset -20 lines).
Hunk #8 succeeded at 1149 (offset -20 lines).
Hunk #9 succeeded at 1163 (offset -20 lines).
Hunk #10 succeeded at 1185 (offset -20 lines).
Hunk #11 succeeded at 1423 (offset -20 lines).
Hunk #12 succeeded at 1435 (offset -20 lines).
Hunk #13 succeeded at 1478 (offset -20 lines).
Hunk #14 succeeded at 1681 (offset -27 lines).
Hunk #15 succeeded at 1831 (offset -27 lines).

Only disas.c needed fixing manually. Cleared away the .rej and .orig files. After that I created a new patch from these updated sources. There were just a couple fixes that needed done.
For the future it might be easier to maintain a fork of qemu - I think git is a good plan to make it easier to do next time!

Huh, it's good to know it was that straightforward. I suppose Git really is just a timeless patch (see what I did there?).
It looks like Travis passed! Cool.


Add Zowe Conformance Program link #654

Signed-off-by: nannanli<EMAIL_ADDRESS>

@BrandonJenkins14 Agree. That would be helpful to keep users updated of the doc site changes.


Clash with new versions of Az.Storage 5.6.0 or 5.7.0

Describe the bug
Az.StorageTable will not import if Az.Storage 5.6.0 or Az.Storage 5.7.0 are only available versions
Error Message
Import-Module: The script 'AzStorageTableCoreHelper.psm1' cannot be run because the following modules that are specified by the "#requires" statements of the script are missing: Az.Storage.
PowerShell Version
Include here the full output of the following command line:
Name                           Value
----                           -----
PSVersion                      7.3.4
PSEdition                      Core
GitCommitId                    7.3.4
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Complete list of Azure related Powershell modules
Paste here the complete output of Get-Module *az* -ListAvailable
Get-InstalledModule -name az.storage -AllVersions
Version              Name                                Repository           Description

5.6.0                Az.Storage                          PSGallery            Microsoft Azure PowerShell - Storage ser…
5.7.0                Az.Storage                          PSGallery            Microsoft Azure PowerShell - Storage ser…
Code Snippet
Import-Module Az.StorageTable
More information

OS: Windows 10

Additional context
Other scripts that require Az.Storage work.

Is version 2.1.0 published to PowerShellGallery.com? Find-Module Az.StorageTable picks up https://www.powershellgallery.com/packages/Az.StorageTable/1.0.7


feat: next

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

GitHub release
v3.2.0

Your semantic-release bot :package::rocket:


…

When using image lists for feature extraction, 'path' in getitem is no instance of Path (it is a str) and it will crash when trying to call path.as_posix().
I also added a warning if there are no db images retrieved (for some reason) for a query image. Such queries will be skipped.

Thanks for the PR! I will push some fixes to cleanup extract_features.


Magic link ends up with 401

Hello,
I have followed the guide for directus with agencyos template (docker) and  Nuxt, all default (also build my own docker image basing on the guide). The frontend asks just for email (no password), but directus returns 401 and logging Invalid user credentials.
I guess, this magic link requires some additional config on directus or so (its not well explained).
I didn't forget to setup api token for Nuxt.
I have configured smtp variables, but i guess, the problem is somewhere in accepting this magic link auth method.

I've got a few updates coming soon. It's not actually a magic link login - that was just included as a sample of what you might to do, but it appears to be causing more confusion.
If you look at the LoginForm.vue you'll see its just using a preset login and password.
When you load the template instance from directus-template-cli you'll likely have to input new passwords for the pre-loaded users through the Directus instance in order to login to the portal.

Still not sure what shouild i do :) I just copied your git repo, filled env values and started dev instance. Do i need to change something on Nuxt or directus side ?

@Saddamus Create a password field for below the e-mail field.
The default password value is "password". Set here:
const credentials = reactive({
	email<EMAIL_ADDRESS>	password: 'password',
});

This is the password saved in Directus for this account. So when you sign in with this, this should work. Change the password or e-mail and you will get an error.
Good luck!

I've got a few updates coming soon. It's not actually a magic link login - that was just included as a sample of what you might to do, but it appears to be causing more confusion.

Agreed that this was confusing as with some other features that were "roughed-in" for demonstrations. If there are unfinished features (marked with @TODO) they should probably only exist in a feature branch to be pulled into main/master later when they are completed or just provide more comments to understand what this stack is doing at that location.
Two-Cent Opinions: For most new users of this repo (and Directus as a whole) are probably digging through this repo to see "how" the stack works between Frontend+BFF (Nuxt) and Backend (Directus). This stack is so awesome but complex. Using separations into nuxt layers & nuxt modules overriding views and behavior is totally the right choice but the complexity probably warrants more detailed info to understand the setup as a whole. I know I was having difficulty realizing what behavior is hard-coded for show and what would need to be refactored to be dynamic. Logging on the Customer Portal was one of those spots. Stripe invoice payments on that portal is also not very clear if it's a PROD ready solution or just a demo of capabilities with hardcoding.

I've worked on several Nuxt apps using Directus, but still the magic link feature here caused confusion. Despite my experience, this specific issue required a deeper dive into the code to understand fully. A community-driven resource like a Wiki for this repository would be beneficial, as it could have saved time and provided clearer guidance.

#65 solves this confusion.


The heading should say more in the "Map" section

The heading says "Map" now doesn't say anything about the data you're about to see. It should be descriptive of the data shown below.

@suryaceg is this better?

STATE-WISE STATUS or STATE-WISE STATISTICS  would be good

Fixed!


Does not allow case-insensitive attribute selectors

Per css docs, an attribute selector with an 'i' at the end should be valid, but is not.

Thanks, I didn't know this. Will you be able to create a pull-request?

Resolved in 2.0.0


Update packages with nullsafety constraints

Fixes melos bootstrap on Linux. Tested on master & dev channels.

Before
$ melos bootstrap
[...]

Bootstrapping project...               -Running "flutter pub get" in .melos_tool...

Because every version of android_intent_plus from path depends on platform >=2.0.0 <=3.0.0-nullsafety.2 and every version of flutter_driver from sdk depends on platform 3.0.0-nullsafety.4, android_intent_plus from path is incompatible with flutter_driver from sdk.
So, because plus_plugins depends on both flutter_driver any from sdk and android_intent_plus from path, version solving failed.
pub get failed (1; So, because plus_plugins depends on both flutter_driver any from sdk and android_intent_plus from path, version solving failed.)

[...]

Because every version of android_intent_plus from path depends on platform >=2.0.0 <=3.0.0-nullsafety.2 and every version of flutter_driver from sdk depends on platform 3.0.0-nullsafety.4, android_intent_plus from path is incompatible with flutter_driver from sdk.
So, because plus_plugins depends on both flutter_driver any from sdk and android_intent_plus from path, version solving failed.
pub get failed (1; So, because plus_plugins depends on both flutter_driver any from sdk and android_intent_plus from path, version solving failed.)

[...]

Because every version of device_info_plus_linux from path depends on file >=5.2.1 <=6.0.0-nullsafety.2 and every version of flutter_driver from sdk depends on file 6.0.0-nullsafety.4, device_info_plus_linux from path is incompatible with flutter_driver from sdk.
So, because plus_plugins depends on both flutter_driver any from sdk and device_info_plus_linux from path, version solving failed.
pub get failed (1; So, because plus_plugins depends on both flutter_driver any from sdk and device_info_plus_linux from path, version solving failed.)

Bootstrap failed, reason: pub get failed, see logs above.

After
$ melos bootstrap
   └> /home/jpnurmi/Projects/flutter/plus_plugins

Bootstrapping project...               SUCCESS
Linking project packages...            SUCCESS

Packages:
  • android_alarm_manager_example
    └> ./packages/android_alarm_manager_plus/example
  • android_alarm_manager_plus
    └> ./packages/android_alarm_manager_plus
  • android_intent_example
    └> ./packages/android_intent_plus/example
  • android_intent_plus
    └> ./packages/android_intent_plus
  • battery_plus
    └> ./packages/battery_plus
  • battery_plus_example
    └> ./packages/battery_plus/example
  • battery_plus_macos
    └> ./packages/battery_plus_macos
  • battery_plus_platform_interface
    └> ./packages/battery_plus_platform_interface
  • battery_plus_web
    └> ./packages/battery_plus_web
  • battery_plus_windows
    └> ./packages/battery_plus_windows
  • connectivity_plus
    └> ./packages/connectivity_plus
  • connectivity_plus_example
    └> ./packages/connectivity_plus/example
  • connectivity_plus_macos
    └> ./packages/connectivity_plus_macos
  • connectivity_plus_platform_interface
    └> ./packages/connectivity_plus_platform_interface
  • connectivity_plus_web
    └> ./packages/connectivity_plus_web
  • device_info_example
    └> ./packages/device_info_plus/example
  • device_info_plus
    └> ./packages/device_info_plus
  • device_info_plus_linux
    └> ./packages/device_info_plus_linux
  • device_info_plus_platform_interface
    └> ./packages/device_info_plus_platform_interface
  • device_info_plus_web
    └> ./packages/device_info_plus_web
  • package_info_example
    └> ./packages/package_info_plus/example
  • package_info_plus
    └> ./packages/package_info_plus
  • package_info_plus_macos
    └> ./packages/package_info_plus_macos
  • package_info_plus_platform_interface
    └> ./packages/package_info_plus_platform_interface
  • package_info_plus_web
    └> ./packages/package_info_plus_web
  • package_info_plus_windows
    └> ./packages/package_info_plus_windows
  • regular_integration_tests
    └> ./packages/share_plus_web/test
  • sensors_example
    └> ./packages/sensors_plus/example
  • sensors_plus
    └> ./packages/sensors_plus
  • sensors_plus_platform_interface
    └> ./packages/sensors_plus_platform_interface
  • sensors_plus_web
    └> ./packages/sensors_plus_web
  • share_example
    └> ./packages/share_plus/example
  • share_plus
    └> ./packages/share_plus
  • share_plus_linux
    └> ./packages/share_plus_linux
  • share_plus_platform_interface
    └> ./packages/share_plus_platform_interface
  • share_plus_web
    └> ./packages/share_plus_web
  • share_plus_windows
    └> ./packages/share_plus_windows

 -> 37 plugins bootstrapped

thank you!


Add missing BDD assertions for exception handling.

Check List:

Fixes #1696
Unit tests : YES
Javadoc with a code example (on API only) : YES

Integrated thanks @mwajcht!


The Examples documentation for Test Docker Images has flaws

Hello,
I was playing with the 'Test docker Images' here: https://testinfra.readthedocs.io/en/latest/examples.html#test-docker-images
I had implemented a single parameterized test using the docker_images decorator as suggested and noticed that the behavior was unexpected and caused me to troubleshoot why my tests where using the wrong OS for more than a few hours.
Here's an example that will reproduce this.
VERSION INFO

testinfra version: 1.6.5
docker version: 17.04
python version: 2.7.13
pytest version: 3.2.1

Step 1

Configure your tests/conftest.py as recommended in the link above.

Step 2

Implement some test

# tests/test_flaw.py

@pytest.mark.docker_images('centos:6')
def test_user_exists_on_centos6(host):
    root_user = host.user('root')

    assert root_user.exists
    assert root_user.shell == '/bin/base'
    assert root_user.gecos == 'root'
    assert root_user.home == '/root'
    assert root_user.group == 'root'

@pytest.mark.docker_images('centos:7')
def test_user_exists_on_centos7(host):

    # This will catch the flawed behavior.  On my system the system under test was CentOS 6.x!
    assert host.system_info.release == '7'

    root_user = host.user('root')

    assert root_user.exists
    assert root_user.shell == '/bin/base'
    assert root_user.gecos == 'root'
    assert root_user.home == '/root'
    assert root_user.group == 'root'

Behavior of the above is not what you expect.  Yes, I can combine the test into a single test and just use the decorator @pytest.mark.docker_images('centos:6', 'centos:7') but the flawed behavior is the same.

We expect the two tests to run under two different docker containers one for centos:6 and one for centos:7.  However, what I noticed was that I was executing two tests under centos:6 even when the second test should have only executed on centos:7.  The assertion in the second test should expose the unexpected behavior that I'm noticing.

I'll provide the example failure later.

Yes, I think it's a pytest bug. testinfra has several hacks in it's own test suite to "fix" this: https://github.com/philpep/testinfra/blob/master/test/conftest.py#L105
I simplified the docker example so it's simplier to understand (and is working): https://testinfra.readthedocs.io/en/latest/examples.html#test-docker-images


nsc-events-nextjs_6_342_unit-test-create-event-page

I wrote the test and base on the page but I don't know why it is still errors at the render part

@kaimanasse15 I see the latest commits are two weeks ago and tests are still failing. Did you want to close this PR without merging or are you still working on this?

I can see the PR is still not passing the checks I am not sure if this is still being worked or now but it needs some work to be able to merge.

Closing due to inactivity. Reopen if needed.


Support documentation pages

For the API, how to search etc.

Done:

https://data.occrp.org/#/help
https://data.occrp.org/#/help/api


2FA

Recently had a problem when a token was correct but the changing code was not. Token has worked in the past when I’ve used it but recently stopped working.

?

Let me rephrase. I had a token that was working, I backed up my phone every Friday, then my iPhone broke around two weeks later, I got a new one iPhone, I backed it up with a backup that had the Google Authenticator token in it, the app still has the token as well as the rest of the tokens saved on the device. However, the codes it gives me are wrong. So, please reopen the ticket.

Let me rephrase. I had a token that was working, I backed up my phone every Friday, then my iPhone broke around two weeks later, I got a new one iPhone, I backed it up with a backup that had the Google Authenticator token in it, the app still has the token as well as the rest of the tokens saved on the device. However, the code it is giving me is wrong.

Are all the tokens wrong? Then it's more likely a phone time issue.
In any case I don't see any way to troubleshoot this, especially with this poor bug description and no access to the device.


Add compression/replication/tiering support for storageclass

Compression will support the algos specified in 'File compression' in https://www.ibm.com/docs/en/spectrum-scale
Add replication/tiering support with defaulted replication values
Pull request checklist

Added support for compression/tiering/replication within a storageclass

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature Enhancement
[ ] Test Automation
[ ] Code Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Community Operator listing
[ ] Other (please describe):

What is the current behavior?

N/A

What is the new behavior?

With this change, a compression, tier, and replication values can be supplied in the storageclass spec.
Once a pvc is created, some validation checks will be done such as making sure a valid compression algorithm was specified or a valid range for replication was set. For tiering and replication, a new rule will be set in the filesystem policy so any new files will be placed/replicated accordingly.

How risky is this change?

[ ] Small, isolated change
[x] Medium, requires regression testing
[ ] Large, requires functional and regression testing

There is one issue where
%COMPRESSZ% will conflict with %COMPRESSZFAST% for the fileset name.
Since all the compression algos are documented in the KC we will still want the user to specify "z" vs "zfast" but internally we could rename the pvc to FASTZ instead of ZFAST to avoid such conflicts? Any other ideas what we could name the pvc to avoid such conflicts?


Introduce pending state for unresolved follows

Builds on https://github.com/subconsciousnetwork/subconscious/pull/647 because I already threaded app into the profile view there.

[x] Pull to refresh should dispatch .syncAll on app
[x] Follow user form is not being reset between usages
[x] Track which petnames are in-flight

[x] Render this as an icon on the card

[x] Stop waiting if petname is removed from addressbook (check getPetname before resolvePetname)
[x] Move pending state into AddressBookService, provide a method to query the status and do that check when refreshing the profile

Demo
https://github.com/subconsciousnetwork/subconscious/assets/5009316/1f6c7339-e714-4f76-aa24-9418c2f4104e
Fixes #555
Fixes https://github.com/subconsciousnetwork/subconscious/issues/492
Related to https://github.com/subconsciousnetwork/subconscious/issues/604

@gordonbrander not related to this work but I think I'll disable the swiftlint github check, it just adds too much noise to the PR review. I'm using it in Xcode locally so I might update #573 to remove the github action as well.


feat: use gravitee-reporter-common for indexing

see https://gravitee.atlassian.net/browse/APIM-2502
⚠ requires https://github.com/gravitee-io/gravitee-reporter-common/pull/2/ to be merged first

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 5.0.0-2502-reporter-common-SNAPSHOT
download it from Artifactory here

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

5.0.0
GitHub release

Your semantic-release bot :package::rocket:


Spark notebook integration

This PR adds supports for the Spark Notebook.
It fetches the tarbal from s3, and deploys it having the public slave role enabled (listening on port 8899).
It also preconfigure all created notebooks to use the spark docker image already used by current DCOS and sets the master to use the DCOS zk+mesos.
Any comments is more than welcome!

Hey Andy thanks for the PR. I'll be sure to try this out on my machine and see what happens. Generally there's a low-as-possible barrier to entry for getting into the multiverse, so as long as its not byzantine we let things through :)
However, there are a couple things to keep in mind:

Do you need to run this on a public slave? If it registers with mesos, then you can just set the webui_url in the frameworkInfo so that you can expose the framework to the DCOS GUI.
The spark docker has mesos binaries inside of it. Do you need to reference the libmesos on the actual host? I'm not exactly sure how this package works so i'm not sure.
In order to get this into the 'official' universe, the entire notebook will probably have to be containerized.
The version of Java on DCOS is for internal components, so this may change later on (see above point).

However, i'll be happy to add this to the multiverse, and thanks so much for the effort!

Thanks @abhay-agarwal !
Leave me some days to find some time to process all of these, but again, thanks for the tips like webui_url, it might good to try out.
will of course keep you posted
cheers

Hey @andypetrella, I tried to run the code. I had to change the port from 8899 to 80 to make it available on the public slave. I was able to find the spark notebook webpage, but the Kernel was never able to connect. I found one anomaly, the URL for spark to connect to mesos, which should be mesos://zk://master.mesos:2181 not mesos://zk://master.mesos:2181/mesos (I think). But it still was not able to connect. Any ideas?

@abhay-agarwal thanks for trying. So, actually I think I had to put the /mesos thingy to make it work (AFAICR), did you tried with it too?
Also, with 8899 it didn't work on public? I think I was able to do it, or at least using the ec2's public dns, not the PublicSlaveDNS one (is it what you mean?)
We can check in the spark-notebook's logs folder for the notebook logs to see what's going on?
For the 80 port, I guess trying the web uri would be more interesting to use/try?
I can give you a quick hand if you like (if you have a limited access pem file for instance)

Task is here: [http://spark-not-elasticl-1u2cgzieemmjy-1506765246.us-west-2.elb.amazonaws.com/mesos/#/slaves/20150803-180328-17235978-5050-1247-S1/browse?path=%2Fvar%2Flib%2Fmesos%2Fslave%2Fslaves%2F20150803-180328-17235978-5050-1247-S1%2Fframeworks%2F20150803-180328-17235978-5050-1247-0000%2Fexecutors%2Fspark-notebook.19298523-3a0f-11e5-8294-56847afe9799%2Fruns%2F1cc30efc-197c-4a9f-a162-3557dfccdbae]
UI is here: [http://spark-not-publicsl-bks5kbsvj7t8-1884821931.us-west-2.elb.amazonaws.com/notebooks/streaming/Streaming Example.snb]
The cluster will self destruct at midnight
Happy hacking!

Also disregard the containerizer comment. I didn't notice that you bundled your own JRE.

Okay, looks like the websocket connection cannot be established :-S.
And, the settings are not applied to already existing notebooks (because they could be configured to access a specific cluster on purpose). Hence only newly created notebooks will have the refs to use this mesos (or an existing notebook's metadata is adapted accordingly).
So if you create a new notebook, it will have the right parameters to access the mesos cluster.
However, it looks like the web socket connection establishment is not working, when a connection to ws://spark-not-publicsl-bks5kbsvj7t8-1884821931.us-west-2.elb.amazonaws.com:8899/ws/api/kernels/51ebb7b4-eeeb-47d2-a95e-751cbaf5da3a/channels?session_id=149A2D1CCE8D42A5860BAEC0E180AF11 is tried for instance it gots a 400 but I don't see anything in logs :-/.
Do you know if such ws connection should work from the public node?

would it be possible to "chat" on gitter, it's generally easier for this kind of thingy.
You can create a private room and add my @andypetrella account to it if you ilke, or we can discuss that on slack?

Yup sure.

here

Alright LGTM. Merging.


Add spellcheck status check

Similar to execution api: https://github.com/ethereum/execution-apis/blob/main/.github/workflows/spellcheck.yaml

Certainly! To add a spellcheck status check to your Ethereum project, you can follow a similar approach as the execution API repository. Here's a step-by-step guide:

Create a new file named .github/workflows/spellcheck.yaml in the root directory of your Ethereum project.

Open the spellcheck.yaml file and add the following content:

name: Spellcheck

on:
  pull_request:
    branches:
      - main

jobs:
  spellcheck:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Setup Node.js
        uses: actions/setup-node@v2
        with:
          node-version: 14

      - name: Install dependencies
        run: npm ci

      - name: Run spellcheck
        run: npm run spellcheck

Save the file and commit it to your repository.

In your Ethereum project, make sure you have a package.json file with the necessary scripts defined. For example, you can add a spellcheck script to run the spellcheck process. Here's an example of how it could be added:

{
  "scripts": {
    "spellcheck": "spellchecker"
  }
}

Commit the changes to your package.json file.

Now, whenever a pull request is opened on the main branch of your Ethereum project, the spellcheck workflow will be triggered. It will check for spelling errors in your codebase using the spellchecker tool.
Feel free to customize the workflow and the spellcheck script to fit your specific needs.


Genesis hash consistency

Add an optional {Byron,Shelley}GenesisHash config and sanity check
New optional entries in the config file
ByronGenesisHash
ShelleyGenesisHash
As hex encoded hashes. If specified these are checked against the actual
genesis file and an error reported on any mismatch.
This guards against accidental changes (either by users or by any tools
that incorrectly apply some transformation to the file).
Also add cardano-cli shelley genesis hash
Used to compute the expected genesis hash to include in the config file.
This command is specific to Shelley. The Byron hash is computed
differently and there is already a command for that.

bors r+


Long compile times

It seem that ClimaDiagnostics may be largely responsible for the long compile times. This may be related to #82, or complex type signatures + https://github.com/JuliaLang/julia/issues/55807, or a combination of all three. This job in ClimaAtmos took ~98 minutes to compile the driver up to the end of the first call to step!(integrator) with diagnostics, and only 24 without. So, adding diagnostics increases compile times by 4x. Here is a reproducer in ClimaAtmos:
# julia --project=examples

# Make the driver perform one step:
open("examples/hybrid/driver.jl", "w+") do io
    println(io, "redirect_stderr(IOContext(stderr, :stacktrace_types_limited => Ref(false)))")
    println(io, "import ClimaComms")
    println(io, "ClimaComms.@import_required_backends")
    println(io, "import ClimaAtmos as CA")
    println(io, "import Random")
    println(io, "Random.seed!(1234)")
    println(io, "if !(@isdefined config)")
    println(io, "    (; config_file, job_id) = CA.commandline_kwargs()")
    println(io, "    config = CA.AtmosConfig(config_file; job_id)")
    println(io, "end")
    println(io, "simulation = CA.get_simulation(config)")
    println(io, "(; integrator) = simulation")
    println(io, "import SciMLBase")
    println(io, "sol_res = SciMLBase.step!(integrator)")
end

# Common driver configuration
config_vec = [
	"initial_condition: TRMM_LBA",
	"rad: TRMM_LBA",
	"surface_setup: TRMM_LBA",
	"turbconv: diagnostic_edmfx",
	"implicit_diffusion: true",
	"approximate_linear_solve_iters: 2",
	"prognostic_tke: true",
	"edmfx_upwinding: first_order",
	"edmfx_entr_model: \"Generalized\"",
	"edmfx_detr_model: \"Generalized\"",
	"edmfx_nh_pressure: true",
	"edmfx_sgs_mass_flux: true",
	"edmfx_sgs_diffusive_flux: true",
	"moist: equil",
	"cloud_model: \"quadrature_sgs\"",
	"call_cloud_diagnostics_per_stage: true",
	"precip_model: \"1M\"",
	"override_τ_precip: false",
	"config: box",
	"x_max: 1e8",
	"y_max: 1e8",
	"x_elem: 2",
	"y_elem: 2",
	"z_elem: 30",
	"z_max: 16400",
	"dz_bottom: 50",
	"dt: 300secs",
	"t_end: 6hours",
	"dt_save_state_to_disk: 10mins",
	"FLOAT_TYPE: \"Float64\"",
	"toml: [toml/diagnostic_edmfx.toml]",
	"netcdf_interpolation_num_points: [8, 8, 30]",
	"ode_algo: ARS343"
]

#---------------------------- No diagnostics
open("config/model_configs/diagnostic_edmfx_trmm_stretched_box.yml", "w+") do io
    for entry in config_vec
        println(io, entry)
    end
    println(io, "enable_diagnostics: false")
end
empty!(ARGS);
push!(ARGS, "--config_file", "config/model_configs/diagnostic_edmfx_trmm_stretched_box.yml");
push!(ARGS, "--job_id", "diagnostic_edmfx_trmm_stretched_box");
@time include("examples/hybrid/driver.jl")
# 1430.385636 seconds (1.33 G allocations: 78.446 GiB, 87.09% gc time, 99.79% compilation time: <1% of which was recompilation)

#---------------------------- with diagnostics
open("config/model_configs/diagnostic_edmfx_trmm_stretched_box.yml", "w+") do io
    for entry in config_vec
        println(io, entry)
    end
    println(io, "diagnostics:")
    println(io, "  - short_name: [ts, ta, thetaa, ha, pfull, rhoa, ua, va, wa, hur, hus, cl, clw, cli, hussfc, evspsbl, pr]")
    println(io, "    period: 10mins")
    println(io, "  - short_name: [arup, waup, taup, thetaaup, haup, husup, hurup, clwup, cliup, waen, tke, lmix]")
    println(io, "    period: 10mins")
    println(io, "  - short_name: [husra, hussn]")
    println(io, "    period: 10mins")
end
empty!(ARGS);
push!(ARGS, "--config_file", "config/model_configs/diagnostic_edmfx_trmm_stretched_box.yml");
push!(ARGS, "--job_id", "diagnostic_edmfx_trmm_stretched_box");
@time include("examples/hybrid/driver.jl")
# 5878.586855 seconds (1.44 G allocations: 85.778 GiB, 92.98% gc time, 99.94% compilation time: <1% of which was recompilation)

cc @Sbozzolo, @szy21

Wow! That's dramatic! Could you run a test where you use the HDF5 writer instead? The NetCDF writer is much more complex (and inherits type instablity from NCDatasets). That would already give us a sense of where to look.

I know that the loops in orchestrate_diagnostics cause a lot of compiler allocations. I tried unrolling them and it led to a massive explosion in compile time.
If changing writer to HDF5 improves things, we can restructure things to have diagnostics sharing the same writers instead of each one having their own. That would simplify the types quite a lot and we can re-evalute unrolling at that point.

Yeah, it's pretty dramatic, I have a feeling that it's a combination of things, and yes, we can try with HDF5.
I haven't narrowed down between inference / LLVM time.

Here are some tests I performed. I took a baroclinc wave and added a bunch of diagnostics like this:
  - short_name: [pfull, ua, wa, va, rv, ta, ke]
    period: 1days
  - short_name: [pfull, ua, wa, va, rv, ta, ke]
    period: 2days
  - short_name: [pfull, ua, wa, va, rv, ta, ke]
    period: 3days
  - short_name: [pfull, ua, wa, va, rv, ta, ke]
....

in the config.
I tested the case with NetCDF and HDF5 writers, and listed below is approximately the time to compile step:
NetCDF:
0 diagnostics: 32 seconds
10 diagnostics: 32 seconds
20 diagnostics: 36 seconds
40 diagnostics: 42 seconds
60 diagnostics: 48 seconds
HDF5:
50 with HDF5: 33 seconds
150 with HDF5: 38 seconds
Next, I tried turning the diagnostics from a tuple to vector, these are the new times
NetCDF:
50 diagnostics: 30 seconds
150 diagnostics: 33 seconds
HDF5:
50 diagnostics: 27 seconds
150 diagnostics: 38 seconds


Swap samples in customizing_linq.md

First sample should be the extension method and third should be the implementation of IMethodCallParser

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


lsp_installer_allow_federated_servers default behavior breaks jsonls, cssls, and html

Given the following configuration, jsonls, cssls, and html are all created in $HOME/.local/share/nvim/lsp_servers/ in three separate directories: vscode-langservers-extracted_jsonls, vscode-langservers-extracted_cssls, vscode-langservers-extracted_html.  However, their LSP configs all are looking for only vscode-langservers-extracted for their cmd.  Adding vim.g.lsp_installer_allow_federated_servers = 1 before this code fixes the issue.  Setting the global to 0 does not fix the behavior as the cmd for those language servers continue to use only vscode-langservers-extracted.
local desired_servers = {
  sumneko_lua = {
    settings = {
      Lua = {
        diagnostics = {
          globals = { 'vim' }
        },
        telemetry = {
          enable = false
        }
      }
    }
  },
  jsonls = {},
  cssls = {},
  html = {},
  bashls = {},
  yamlls = {},
  pyright = {},
  terraformls = {}
}

local lsp_installer = require'nvim-lsp-installer'

for server_name, _ in pairs(desired_servers) do
  local ok, server = lsp_installer.get_server(server_name)
  if ok then
    if not server:is_installed() then
      server:install()
    end
  end
end

lsp_installer.on_server_ready(function(server)
  local opts = desired_servers[server.name]

  server:setup(opts)
  vim.cmd [[ do User LspAttachbuffers ]]
end)

Thanks for reporting!

Adding vim.g.lsp_installer_allow_federated_servers = 1 before this code fixes the issue. Setting the global to 0

Have you tried using boolean values instead? This global only really supports boolean values, primarily due to how lua does boolean logic with numeric numbers (:lua print(0 and "what?"))

Ah so I found an error which I've fixed in #75. Also fixed support for numeric values for the g: lsp_installer_allow_federated_servers option

Ah, sorry I'm late.  Boolean probably would've worked. Still had my brain in vim-scripty-land.  Thanks for the quick turnaround!


std::bad_alloc error

I am attempting to align a draft genome with a related reference species using mummer4. I've successfully tested the installation on partial chromosomes but receive this error when I try anything larger:
> terminate called after throwing an instance of 'std::bad_alloc'
>   what():  std::bad_alloc
> Aborted (core dumped)

This occurred using a single chromosome (reference) against the draft genome (query). From my understanding this error occurs when the program can't access enough memory. I am using a cluster with 32 GB of memory requested which I thought would be sufficient. Do I need to expand my resources or is it possible that I am making a mistake with the installation, command or approach?  Any help would be appreciated.  Thanks

https://github.com/mummer4/mummer/issues/11

Hello! Have you solved this problem? If so, could you tell me how to solve it. I also receive this error. Thanks a lot!!!

I am having the same issue. Does anyone know how to fix it?


Fix plot issues

Fix issue related to #890 and the reordering of stacked_violin_plots when swap_axes=False and for the case when dendrogram and order are given, in which case dendrogram order takes precedence.
Fix issue #891, now if groups is set for an embedding, the cells belonging to those groups are plotted on top.
I also added missing documentation, pointing that the marker size could be a list of per-cell size.
Added a new plotting test for the groups option.

Great! Can’t say I the #890-related fix though: What went wrong before your fix? Is there a test for it?
Please use 4 space indentation, not visual indentation. Basically, running black on the any newly changed code should yield minimal changes.

@flying-sheep For #890 probably we had never tested that combination of parameters because the output was a broking image.
If I understand you correctly, black can by applied to only some lines? Apparently PyCharm can be used with black, do you have any experience?

One question related to #891, is there any plotting order for continuous values like higher expression plotted on top? That's more controversial but sometimes dropout et al might obscure cells expressing a gene. What do you think?

@gokceneraslan by default, higher values of the column you are plotting are put on top. You can change this behaviour by setting sort_order=False.
Note: The default behaviour can be misleading and give you the impression that for example one cluster is expressing certain gene, when in reality only a small fraction of cells do express the gene, but because they are all plot on top, they seem to be more.

probably we had never tested that combination of parameters because the output was a broking image.

got it!

If I understand you correctly, black can by applied to only some lines? Apparently PyCharm can be used with black, do you have any experience?

AFAIK black can’t be applied to some lines only. Thus my suggestion to just run it on files where you changed a lot. about pycharm

That’s a lot of files reformatted! I didn’t blacken  scanpy/plotting/_anndata.py yet because people were working on it. If currently nobody is working on it, we can go ahead.


Fixes for issue #120.

Extended check if field is public by also taking into account IsFamilyOrAssembly-property of FieldDefinition (now behaves like the method check).
InheritMap now also generates groups for virtual methods of props (set, get) and events (add, remove).
The group info is used to find out if any virtual method in the group belongs to a public type and therefore should be skipped. e.g. public interface implemented by internal class or vice a versa.

@lextm Do you have an idea if/when this PR is going to be accepted?

I already built up some new test cases, but not yet finish reviewing this PR. It might take some more time.

@lextm Any progress on the PR. Can I help you with the tests?

I just began trying out Obfuscar and ran into this issue immediately. Hope it is fixed soon as it's currently a show stopper.

Any progress on this PR?

I cannot accept this PR, as it only fixed the simplest case.
Consider the following test case,
namespace TestClasses
{
    public interface A
    {
        int Property { get; }
        void Method();
    }

    internal interface B
    {
        int Property { get; }
    }

    internal class C : A, B
    {
        // This property should not be obfuscated.
        int A.Property
        {
            get { return 0; }
        }

        // This property should be obfuscated.
        int B.Property
        {
            get { return 1; }
        }

        // This method is not be obfuscated because it's a part of the public interface.
        public void Method()
        { }
    }
}


Fix timeout type cast exception

Signed-off-by: crazyhzm<EMAIL_ADDRESS>What is the purpose of the change
Fix #10618
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #10644 (1c1d25d) into 3.0 (89ef73d) will decrease coverage by 0.06%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##                3.0   #10644      +/-   ##
============================================
- Coverage     65.95%   65.88%   -0.07%
+ Complexity      317      295      -22
============================================
  Files          1240     1240
  Lines         54054    54059       +5
  Branches       8182     8182
============================================
- Hits          35650    35618      -32
- Misses        14541    14568      +27
- Partials       3863     3873      +10

Impacted Files
Coverage Δ

...in/java/org/apache/dubbo/rpc/support/RpcUtils.java
57.60% <0.00%> (-2.40%)
:arrow_down:

...g/apache/dubbo/rpc/protocol/tri/TripleInvoker.java
56.57% <0.00%> (ø)

...va/org/apache/dubbo/remoting/TimeoutException.java
22.22% <0.00%> (-11.12%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
58.33% <0.00%> (-8.34%)
:arrow_down:

...dubbo/remoting/exchange/support/DefaultFuture.java
80.17% <0.00%> (-6.90%)
:arrow_down:

...ava/org/apache/dubbo/rpc/proxy/InvocationUtil.java
84.84% <0.00%> (-6.07%)
:arrow_down:

...e/dubbo/rpc/protocol/tri/transport/WriteQueue.java
73.80% <0.00%> (-4.77%)
:arrow_down:

...ubbo/common/system/OperatingSystemBeanManager.java
50.00% <0.00%> (-4.55%)
:arrow_down:

...registry/zookeeper/util/CuratorFrameworkUtils.java
70.00% <0.00%> (-4.45%)
:arrow_down:

.../apache/dubbo/rpc/protocol/dubbo/DubboInvoker.java
64.28% <0.00%> (-2.86%)
:arrow_down:

... and 22 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


tests: add nsim special cases for two tests

The NSIM emulator has severe performance issues when
the MPU registers are reprogrammed on context switch.
Disable runtime reprogramming of the MPU for these
platforms on these two tests, which have a lot of context
switch thrashing. This is done by ensuring userspace
and hardware stack overflow detection via guard areas
is disabled.
I have assurances from the ARC team that the tests run fine
on real hardware and this is an emulation issue. We're only
changing the test parameters for these emulated targets.
For 1.15, this will be completely resolved by optimizing
MPU region gap-filling to not take place during context
switch time, which will drastically reduce the number of
MPU registers poked during context switch on nsim_sem/
nsim/em. See #15223
Meanwhile, for 1.14 we ensure that no runtime reprogramming
of the MPU is done for these tests.
Fixes: #14642
Signed-off-by: Andrew Boie<EMAIL_ADDRESS>

How about nsim_em and nsim_sem boards? These use userspace but no MPU stack guards. I have seen timeouts for these  as well.

? How about nsim_em and nsim_sem boards? These use userspace but no MPU stack guards. I have seen timeouts for these as well.
Not seeing timeouts for those, I expect because all the threads being swapped around are in the same memory domain and there's no guard regions to update. Running another test now to confirm.

How about nsim_em and nsim_sem boards?

aren't those already covered in the first test filter in the yaml file?

aren't those already covered in the first test filter in the yaml file?

They aren't, they are different board specifications.
We have 4 board definitions:
nsim_em
nsim_sem
nsim_em_mpu_stack_guard
nsim_sem_mpu_stack_guard

Confirmed.
With this patch and #15248 , I get:
$ sanitycheck -p nsim_em -p nsim_sem -p nsim_em_mpu_stack_guard -p nsim_sem_mpu_stack_guard
JOBS: 12
Building testcase defconfigs...
564 tests selected, 93327 tests discarded due to filters
total complete:  560/ 560  100%  failed:    0
560 of 560 tests passed with 0 warnings in 1444 seconds


[T5A1][F12-A2] Yee Jian Feng, Eric

Ready for review

@yeejfe Accepting this PR without a review because another of your PRs for this tutorial was reviewed in detail.


Add WSL Support

Add support for execution of ansible-vault in wsl

Add checkbox for WSL
Run based on path (if binary starts with wsl$ run in wsl with different command)

related to #1

WSL support is integrated on separate branch.
Can use the ansible-vault executable directly from wsl with a path like this:
//wsl$/Ubuntu-20.04/home/timo/.local/bin/ansible-vault
Currently is on feature branch and further testing for verfiying on macos and linux it still works etc.


pull request for e2e test at 12/24/2016 21:56:05

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


deprecating suitecrm chart

What this PR does / why we need it:
SuiteCRM is no longer in maintenance and the images refer in this chart are not going to be mantained and possibly removed eventually
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
following this process https://github.com/kubernetes/charts/blob/master/PROCESSES.md#deprecating-a-chart

/assign @tompizmor

Can you remove the maintainers and OWNERS file for this?

wrong chart :( sorry


Waveform cleaner updates

Updated CHECMWaveformCleaner to have to possible peak finders
Added helper function in charge extractor to quickly obtain window mask

can you merge in the master again? That should fix all the tests (we now require Travis to say all tests pass before merging into master)


Ruby sass

This branch is online now.
Can somebody review this branch and merge it with the master?

We should merge this branch asap.

will merge it and start refactoring before fixing it


glfw3 dynamic build fails on Linux

Package: glfw3:x64-linux
Vcpkg version: 0.0.113-unknownhash
Steps to reproduce:
edit triplets/x64-linux.cmake: "set(VCPKG_LIBRARY_LINKAGE dynamic)"
vcpkg install glfw3
Looking at the portfile.cmake file I see the same problem I found in #4422 where dynamic library files are specified in a platform dependent manner (ie. glfw.lib where Linux builds libglfw3.so).

I have submitted a pull request to address this issue: https://github.com/Microsoft/vcpkg/pull/4465

I am currently working on a fix for this.

I have submitted a pull request to address this issue: https://github.com/Microsoft/vcpkg/pull/4467


feat: add pnpm to engines

The lock (pnpm-lock.yaml) is version controlled, as it should.
Each of us handles the pnpm package installation independently on their machine, which is why it's missing from the root project's package. This is also a standard approach.
The problem is there's no trace of which pnpm version we should be using. Each pnpm version could generate a different lock, resulting in difficulty working with a common lock and issues like broken lock files.
This change "locks" the pnpm version at project level and in case of version mismatch, pnpm will fail.
More on that here: https://pnpm.io/package_json

should we lock the version more strictly? Do we want it to be a bit more loose? This proposal will lock only major

I like the proposal. I remember that the project did not work for me because locally I was using pnpm version 8.x.x while version 9.x.x was required. I would lock only the major version.


Test for LINKED clusters when running certain data strategies

EXPORT_IMPORT, SQL, LINKED, and HYBRID data strategies require the clusters to be linked.  Using the hadoopcli session, test that the link is working before starting the work.

Test performed when option selected requires LINKED clusters.


[StatefulTable] Can't set totalItems when late loading

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
We are using late loading data in StatefulTable, so at first time, the tabledata sent to StatefulTable is just a part of data, not complete data.
we want to use totalItems field to specify the real total data count, instead of table data count. However i found totalItems  doesn’t work.
I found this  https://github.com/IBM/carbon-addons-iot-react/pull/372  seems someone has fixed it but actually still not.
here is my version of carbon-addons-iot-react: 2.62.0
Expected behavior
When using late loading, we expect to set correct totalItems to do pagination.
Environment/versions:

OS: [ MacOS,]
carbon-addons-iot-react version: [ 2.62.0]

Additional context
If applicable, add screenshots to help explain your problem.
Add any other context about the problem here.
Specific timeline issues / requests
Do you want this work within a specific time period? Is it related to an
upcoming release?
Our product will be released in September, so it will be good if can be fix before that timeline.

This might be a small bug in how we set totalItems in the reducer
https://github.com/IBM/carbon-addons-iot-react/blob/2ff6ad3957c7cda90f9d6396d3ee120b322e16e1/src/components/Table/tableReducer.js#L287

One potential workaround is to merge the late data with the existing data and then regenerate the StatefulTable by changing it's key

:tada: This issue has been resolved in version 2.126.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix plugin_install_options example in README.md

The parameter plugin_install_options of fluentd::plugin is of type
Array[Variant[String, Hash]] - in the README.md it is used as if it were
of type Hash.

Good catch, thank you!


LiveWallpaperSource...setBitmapSynchronous doesn't work when invisible

When the homescreen is not visible (a running app hides it) - calling setBitmapSynchronous doesn't do anything.
Is that expected?
Do I need to hold my call and make it when visible?

Anyway, I resolved this by checking if currently invisible, raising a flag and when visibility changes - if the flag is raised, make the call.


Update add-admin-contacts.md

@jaimeo changes reflect new UI on MMD admin portal

The "areas of focus" are concepts, right? That is, not formally named entities. If so, then do not use title case (i.e., "IT help desk" and "App packaging").

@mertenar - kindly check on the response from jaimeo and apply the suggested changes.
Thank you.

edited per @jaimeo 's suggestion - let's await reply from Stuart (Jaime see thread 8/5) before committing


Issues with additional chat windows not working correctly/at all.

@klepp0906 says: creating a 3rd chat window (i make one for loot explicitly) not only does the label not show up on it, but no matter what i have checked inside it filterwise, nothing works.

just to add to this a bit.
ive now added another chat window, and odd as this is i figure it might help you recognize the problem maybe?
the one i added is the one which now loads without the font on the tab and doesnt show anything.  Now the loot one retains its label and is showing loot.  /boggle
the newest one i named "messages" and use rather want to use for tells and bnet messages is busted lol

ya I am trying for one for party chat I hope a update coming for chat soon