Untrue statement in "How exposure logging works" section in Exposure Logging settings

Avoid duplicates

[X] Bug is not mentioned in the FAQ
[X] Bug affects both Android and iOS, for specific issues / questions that apply only to one operating system, please raise them in the respective repositories:

Android repository
iOS repository

[X] Bug is not already reported in another issue

Technical details

Device name: Any
iOS/Android version: Any
App version: 2.6.3 (iOS)

Describe the bug
The app contains this text in the "How exposure logging works" section in the Exposure Logging settings (Screenshot):
The app never collects personal data such as your name, address or location, nor is this information passed on to other users. It is not possible to use random IDs to draw conclusions about individual persons.
This text is not true (anymore), since the app can collect personal data such as your name and/or address if you

Add an EU digital COVID certificate to the app (fully possible since CWA version 2.5)
Create an Rapid Test Profile (possible since CWA version 2.2)
Receive a personalized rapid antigen test result in the app (possible since CWA version 2.1)
Create a EU digital COVID certificate for a test result in the app (possible since CWA version 2.4)

The text was not changed with the updates which added the above mentioned features.
Steps to reproduce the issue

Open the Corona-Warn-App
On the top, tap on "Exposure Logging Active/Stopped"
Scroll to the very bottom
See the untrue statement in the last paragraph

Expected behaviour
The text should not make untrue statements.
Possible Fix
Correct the texts here:
iOS: https://github.com/corona-warn-app/cwa-app-ios/blob/66060820e179116bea7b31d35d6fc81855022aee/src/xcode/ENA/ENA/Resources/Localization/en.lproj/Localizable.strings#L1023
Android: https://github.com/corona-warn-app/cwa-app-android/blob/fc7c1bd7377a9db04cb50abc06588c1d93400041/Corona-Warn-App/src/main/res/values/strings.xml#L581
The text could be changed to something like:
The exposure logging feature of the app never collects personal data such as your name, address or location, nor is this information passed on to other users. It is not possible to use random IDs to draw conclusions about individual persons.

Internal Tracking ID: EXPOSUREAPP-8915

@Ein-Tim Ok, see your point: Internal Tracking ID: EXPOSUREAPP-8915. Thanks.

Corona-Warn-App Open Source Team

PR iOS: https://github.com/corona-warn-app/cwa-app-ios/pull/3344

I can confirm that this has been fixed in version 2.8 under iOS.
Awaiting confirmation of fix under Android before closing.

@MikeMcC399 Could you confirm that this has been fixed in version 2.8 under Android?

@Ein-Tim
In CWA Android 2.8.0 the sentence is fixed:
"Personal data, such as your name, address, or location, is never recorded during exposure logging, nor is this information passed on to other users."
Here is the full string:
https://github.com/corona-warn-app/cwa-app-android/blob/d74e5805be8355e000d1cfb9655eb7e857438ccf/Corona-Warn-App/src/main/res/values/strings.xml#L586-L587
"You need to enable the exposure logging feature so that the app can determine whether you are at risk of infection. The exposure logging feature works transnationally, meaning any possible exposure involving users is also detected by other official coronavirus apps.\n\nThe exposure logging feature works by your Android smartphone receiving encrypted random IDs from other app users via Bluetooth and passing your own random IDs to their smartphones. Every day, the app downloads lists containing the random IDs – along with any voluntary information about the onset of symptoms – of all users who have tested positive for the virus and voluntarily shared this information (specifically: their random IDs) via their app. This list is then compared with the random IDs of other users you have encountered that have been recorded by your Android smartphone, in order to calculate the likelihood that you have also been infected and to warn you if necessary.\n\nYou can use the toggle switch to disable exposure logging at any time.\n\nPersonal data, such as your name, address, or location, is never recorded during exposure logging, nor is this information passed on to other users. It is not possible to use random IDs to draw conclusions about individual persons."

You should be able to close the issue now.

Thanks for the confirmation @MikeMcC399!
Closing this issue as fixed.


Update deploy to allow multiple deployments with different Users

Adds the Username to the logfile name, so it won' clash with other Users doing a deployment on the machine. Defaults to 'default', If USER is unset.
Fixes Issue https://github.com/Unitech/pm2-deploy/issues/39

Great, can't wait for this small but important fix to be merged.


Some tweaks to the README

Work in Progress

Shortening the table of contents
Putting the "defining factories" stuff together, and before the "using factories" stuff
Using relative links for the cross-linking (better experience for forks)
Moved the changelog to the bottom
Moved the "how this works" nearer the top
Small tidy-ups and tweaks to the code snippets
Misc tweaks to other code.

Hey @danielspaniel, I was looking through the documentation in the README today and decided I'd like to take a crack at rearranging some of it and making some suggestions. This PR is not there yet but I wanted to get your opinion on whether this was a good idea, and whether I was going in the right direction before I continued with it - I'm probably about half-way there. The diff on the README looks bigger than it really is - there's a bit of rearranging here, I haven't actually added that much.
cc @patocallaghan

Boy .. this is great @lorcan .. I love it.
I am also looking into making a new web site where the navigation is on the left side and it would make it 100% easier to find stuff ( if you know what I mean ) ..
and I will reuse your ideas here for when that time comes.


[Bug]: Remove/Fix uninformative INFO logs/messages

What happened?
Standard dab start results in the following:

Information: Microsoft.DataApiBuilder 0.9.5-rc+73a02dcd3b85a73ac36a5675432a45b7a3cc4a7d
Information: Config not provided. Trying to get default config based on DAB_ENVIRONMENT...
Information: Environment variable DAB_ENVIRONMENT is (null)
Loading config file from dab-config.json.
Information: Loaded config file: dab-config.json
Information: Setting default minimum LogLevel: Debug for Development mode.
Starting the runtime engine...
Loading config file from dab-config.json.
info: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[63]
User profile is available. Using 'C:\Users\jerry\AppData\Local\ASP.NET\DataProtection-Keys' as key repository and Windows DPAPI to encrypt keys at rest.
...entities...
info: Azure.DataApiBuilder.Service.Startup[0]
Successfully completed runtime initialization.
info: Microsoft.Hosting.Lifetime[14]
Now listening on: http://localhost:5000
info: Microsoft.Hosting.Lifetime[14]
Now listening on: https://localhost:5001
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
Content root path: C:\Temp\dab

First, there are three types of console output here. Which is confusing.

Information: ...
Free text...
info: ...

Can we ensure our output consistently uses logging and emits the same output? Probably info:
Second, many lines convey nothing to the user. It is not info at all! These are FOR the developer.
Line 2 Information: Config not provided. Trying to get default config based on DAB_ENVIRONMENT...
This comment should communicate what the correct environment variable to use is. We already do this with DAB-ENVIRONMENT. A message like this:

INFO: Environment variable DAB_CONFIG is (null), using argument -c/--config instead.
INFO: Argument -c/--config is (null), using default "dab-config.json" instead.

Line 3 Information: Environment variable DAB_ENVIRONMENT is (null)
This output implies an error when there is none. (I realize it is INFO). It implies that a value that was expected is (null) and could be a problem when it is not. We can correct this with the following new message

INFO: Environment variable DAB_ENVIRONMENT is (null), using value in config file instead.

Line 4 Loading config file from dab-config.json.
This should be an INFO log. This line tells the file name but not the parent: reference #1791
Line 5 Information: Loaded config file: dab-config.json
Remove this line. Move to Debug. Ideally, just remove it.
⚠ This post-event is not useful in any way other than to debug.
Line 6 Information: Setting default minimum LogLevel: Debug for Development mode.
This line is written in such a way that could be misunderstood.

INFO: Setting LogLevel to Debug because Runtime Mode is set to Development.
INFO: Setting LogLevel to Information because Runtime Mode is set Production.

Line 7 Starting the runtime engine...
This is another line that should be an INFO log. Otherwise OKAY

INFO: Starting Data API builder runtime engine

Line 8 Loading config file from dab-config.json.
Remove this line!
⚠ This line is an error. This has already occurred. #1792
Line 9 info: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[63]
Remove this line. Move to Debug. Ideally, just remove it.
⚠ This cryptic event is not useful in any way other than to debug.
Line 10 User profile is available. Using 'C:\Users\jerry\AppData\Local\ASP.NET\DataProtection-Keys' as key repository and Windows DPAPI to encrypt keys at rest.
Remove this line. Move to Debug. Ideally, just remove it.
⚠ This cryptic event is not useful in any way other than to debug.
Line 12 info: Azure.DataApiBuilder.Service.Startup[0] Successfully completed runtime initialization.
Remove this line. Move to Debug. Ideally, just remove it.
⚠ This post-event is not useful in any way other than to debug.
Line 16 info: Microsoft.Hosting.Lifetime[0] Hosting environment: Production
Remove this line. Move to Debug. Ideally, just remove it.
⚠ This useless event is not useful in any way other than MAYBE to debug.
Line 17 info: Microsoft.Hosting.Lifetime[0] Content root path: C:\Temp\dab
Remove this line. Move to Debug. Ideally, just remove it.
⚠ This useless event is not useful in any way other than MAYBE to debug.
If you want to leave line 17 in, it should be the FIRST log in this list, not the last.
Version
Microsoft.DataApiBuilder 0.9.5-rc+73a02dcd3b85a73ac36a5675432a45b7a3cc4a7d
What database are you using?
Azure SQL
What hosting model are you using?
Local (including CLI)
Which API approach are you accessing DAB through?
REST, GraphQL
Relevant log output
No response
Code of Conduct

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

Some extra context:
The default settings file AppSettings.json and its contents are generated automatically when creating an ASP.NET project. The files contents result in seeing the logging events with source:

Microsoft
Microsoft.Hosting.Lifetime

{
  "Logging": {
    "LogLevel": {
      "Default": "Error",
      "Microsoft": "Warning",
      "Microsoft.Hosting.Lifetime": "Information"
    }
  },
  "AllowedHosts": "*"
}

removing the following lines results in relatively less verbose logs:
      "Microsoft": "Warning",
      "Microsoft.Hosting.Lifetime": "Information"


NPM Installation

Hello can find how to install using NPM.
Can You Help?

Sorry, I don't know how to do that yet. But if you can point me to a quick/short tutorial that would not take much time to learn, I'll probably look into it.

With a bit of UMD it's easy, you've done pretty much all the work. If you give a day or two I'll make a pull request to help you.

Hello I'm not the best person to help on that part @ratiw. WOW @zeratulmdq fantastic :+1:
BTW UMD?

@nacr-dev universal module definition. It's a way to make it compatible with browserify, webpack and as a browser global. If you install it through NPM, you can use it pretty much everywhere. You may also make a NPM package as it is right now, but it'll be useful just for some people, not all.

@zeratulmdq That'll be fantastic. Looking forward to that! :)

Nice 😆

Hello is there any timeline on this? It's not a big issue just checking 😊

@nacr-dev Nope. Still haven't got the PR. Any help would be appreciated.

Does this help? https://docs.npmjs.com/getting-started/publishing-npm-packages

@nacr-dev  @mdaliyan  I decided to give it a go and publish it as npm package with the same vuetable package name as in bower.io.  Can you guys please see if it's ok? I don't really use npm myself, so I wouldn't know if I did something wrong.

nice, i was just looking at it, i will install it with npm and report back

@jeroenherczeg Thanks! :)

Thank you

@mdaliyan Good catch! Will take care of it tonight. :)

Install from NPM works!


adoptium-packages-linux-pipeline_new does not work across nodes with different workspace directory

Some ci.adoptium.net nodes use /home/jenkins and some (Azure Cloud VMs) use /home/adoptopenjdk.
The problem is not actually the VM, it's due to the Artifactory installer upload pipeline incorrectly combining "Declarative" and "Scripted" Jenkins pipeline syntax: https://github.com/adoptium/installer/blob/master/linux/Jenkinsfile
As stated in the Jfrog-cli doc: https://jfrog.com/help/r/jfrog-integrations-documentation/use-declarative-or-scripted-syntax-with-pipelines
When working with the Jenkins Artifactory plugin, be sure to choose either scripted or declarative.
In other words, do not use declarative and scripted steps within a single pipeline.
This will not work.

The jfrog-cli Declarative tools definition sets up the pipeline environment for the agent the top-level pipeline runs on, the pipeline then switches to "scripted" mode and switches context using node(), the jfrog-cli will then not necessarily work in that context.
The https://github.com/adoptium/installer/blob/master/linux/Jenkinsfile needs re-working as either a pure "Declarative" pipeline using the jfrog plugin, or as a "Scripted" pipeline (will need server config and credentials adding...).
There is also a secondary issue in that the installer jenkins file locks two "dockerBuild&&linux&&x64" nodes, which inevitably causes a deadlock given there are only 2 of these nodes and in the situation where 2 jobs have been queued.
The top-level agent lock is not required to remain when calling the stages, and is an unfortunate consequence of using a top-level "Declarative" pipeline which then calls "scripted" pipeline that then uses node() locking...
I think the easiest way to refactor this is to split this job into two, the top-level one being a "Scripted" pipeline that does the "what we need to build and where" logic, and a second "Declarative" upload pipeline job which it calls. As it is only the second "upload" job that needs to use the jfrog-cli plugin. The second job then be called multiple times by the top-level job with the appropriate parameters.
Important note: the top-level job does not need to reserve a agent node while calling the sub-jobs...

Another issue found, it seems if a publish installer job is aborted, and then another one started, the upload seems to upload from an existing workspace that has not been "cleaned". The following job for jdk21 riscv uploaded jdk17 as well which was aborted due to "node deadlock":
https://ci.adoptium.net/job/adoptium-packages-linux-pipeline_new/1694/console
[adoptium-packages-linux-pipeline_new] $ /home/jenkins/tools/io.jenkins.plugins.jfrog.JfrogInstallation/jfrog-cli/jf rt u **/build/ospackage/temurin-*${BUILDARCH}.deb deb/pool/main/t/temurin-${VERSION}/ --target-props=${DISTROLIST}deb.component=main;deb.architecture=${BUILDARCH} --flat=true
10:17:47 [Info] [Thread 2] Uploading: jdk/debian/build/ospackage/temurin-21-jdk_<IP_ADDRESS>.0+11-1_riscv64.deb
10:17:47 [Info] [Thread 0] Uploading: jdk/debian/build/ospackage/temurin-17-jdk_<IP_ADDRESS>.0+11_riscv64.deb
{
  "status": "success",
  "totals": {
    "success": 2,
    "failure": 0
  }
}


Fix datatable bug when sorting a column

see https://github.com/VulcanJS/Vulcan/issues/2090#issuecomment-433860782
Previously : when you clicked on a sortable column, the results of the fired query would be null, and the next polling would make it right. You had a long time with no results displayed.
Now : The query fired when you click to sort a column returns the right result, with the props updating correctly, so no need to wait for the polling to update the results.
See #2090 for an in-depth explanation

Thanks for working this out! I noticed the issue but couldn't figure out the root cause,

Feel free to merge this yourself if you have rights, otherwise let me know and I'll do it and/or add you to the core team.


Consider if we should compute compiled_class_hash

Feature Request
Starknet.py does and will not support compilation of Cario1 contracts. Should we provide methods for computing compiled_class_hash? Except for class hash computation, sending transactions through starknet.py would only require the json output of starknet-compile method.
compiled_class_hash computation requires casm output from starknet-sierra-compile so it would have to be supported as separate method anyway. We should consider if there are any realistic use cases of compiled_class_hash computation considering the official CLI will most likely provide this at some point in the future.

For now let's not include this functionality and see if it becomes needed in the future.

Somehow I managed to create #814 and then open this issue 🤦 .
We'll be including computation of compiled_class_hash after all, but most likely only from casm contract (no sierra->casm compilation).


Fix incorrect file paths in index.json

Fixes #17
Update the index.json with the new updated folder sections.

I am so confused, in VScode the branch is up to date. haha

Btw, the docs need update as well.

If this sounds good, let me create another PR and then just link the new pr into this pr. (no need to add hacktoberfest label, to avoid spam pr)


Zap generate objc list callbacks

Problem
This PR exposes the results of reading the Descriptor cluster attributes to Objective-C and ChipTool iOS.
Summary of Changes

Update the templates to generates the Objective-C callbacks
Regen gen/ folders

@saurabhst ?


Update deps for Sept 29, 2023, fix breaking changes in react-markdown

Updates all our deps.  I had to do some surgery to get the react-markdown update to work in our code.
Things seem OK in my testing now (Mermaid diagrams, HTML previews, inline code rendering, GFM, etc).

ok to land?

Let's try.  If something breaks, we'll know who to suspect...


RM3100 : enable I2C

This PR enables I2C for the RM3100 magnetic sensor.
I2C has been bench-tested succesfully. Both external (SPI2 on Pixhawk 3 Pro) and internal (Pixracer-based design) SPI buses have been flight tested succesfully as well. Regarding I2C addresses, even if 0x20 -> 0x23 are possible only 0x20 is implemented as 0x21 -> 0x23 are already used by the SDP3x driver. @ryanjAA can you cross-check?

Flash overflow on fmu-v2, what is the best strategy?

I can confirm it’s working on fmuv3 (Pixhawk 1 with 2mb flash over external i2c). Address is in fact x20. I want to test it against our uavcan version of the unit but I may not be able to until after the new year when I am back. Did some brief testing so probably good to go. No performance testing on accuracy though was done. Just functionality, etc.

Flash overflow on fmu-v2, what is the best strategy?

Comment out more modules for testing, but probably have this disabled in the fmu-v2 build by default  @bkueng Is that reasonable advice?

Yes. This should build for FMUv3 only.


Post not responding in the same way as curl

Posting sync-request doesn't seem work the same as curl. Get requests work fine. The endpoint definitely works as i can curl it with the same body/header, but with sync-request I get "{"detail":"Unsupported media type "" in request."}" error.
Curl command that works:
curl --header "Authorization:Token ' + token + '" -d "' + bodyObj + '" ' + root + '/mobile/endpoint/'
sync-request that doesnt work:
var resPost = request('POST', root + '/mobile/endpoint/', {
  	headers: {
    	'Authorization': "Token " + token,
    	'Content-Type': 'application/json'
  	},
	body: bodyObj
});

Curl will tend to send arbitrary extra headers by default.  sync-requests aims to be a much more bare-bones request library, and generally only sends the headers you ask it to.  You can see the differences in the requests that get sent via a service like requestbin, and then you should be able to add whatever headers you need.


Fix the issue "[ERROR] NoSuitableSigningKeys:No key with kid:"

https://op.certification.openid.net:60186

The issue is fixed since the commit : "https://github.com/thabart/SimpleIdentityServer/commit/c5a9b40b16de19bdf811f74de6020fe4ac56350d"


Fixes for docs component build warnings

See issue #362

@romain-grecourt @barchetta After your earlier (very prompt!) approvals I pushed another changed file. Please take a look at the web intro file (I removed the dangling callout reference, added the <version> for the Maven dependency, and added a catch to the Java code so it would compile if copied and pasted).

I talked off-line to @romain-grecourt about the web server getting started page and the latest push reflects that conversation and his approval.


Feat: Reorg docs following Divio's doc system

Reorganize docs following https://documentation.divio.com. As an example, see https://docs.epinio.io.
This allows to cater to personas. Note that thanks to the Divio system, those personas don't necessarily get specific doc sections for them, they just get an easier time navigating the docs and finding the info relevant to them.
Docusaurus lints on build for broken links, so we can iterate on this process.
Acceptance criteria

Reorg is performed, work prioritized by the following personas (list by @mattfarina), in descending order of importance:

Policy consumer – someone who takes a policy and uses it in a cluster. They don’t develop policies and may not even know how to write software. They may be someone in the CISO office. Their work is around running a policy in a cluster and seeing the results of that.
Kubewarden operator – someone who operates KW in a cluster. The person responsible for installing KW and keeping it up to date. This is an ops/devops role.
Policy developer – someone who writes a policy of their own.
Policy distributor – this is someone who has written a policy and wants to share it with others. They want the policy to be easily consumed by the “policy consumer” role.
Kubewarden integrator – those who want to build on top of KW. This could be a custom UI, a helper tool for generating policies, or something else
Kubewarden developer – those who build Kubewarden itself

No broken links are left in https://docs.kubewarden.io
Links to docs are updated in https://kubewarden.io/blog

Suggestions
As said, work should be prioritized by personas, starting from the first, to maximize adoption.
A low hanging fruit may be to create a "Reference documentation" section, and start moving relevant parts there (e.g: config files, CRDs, etc).

This rebranding should also happen for the landing page at https://kubewarden.io.
An example of a persona reorg:

cluster admins: the universal policy engine, easy to install, modular components, minimal deps, test policies out of cluster, OCI registries
policy consumer: reuse policies from the community, test policies out of cluster, fork and adapt policies as they are modular and not bundled, see policy results via audit-scanner
policy creator: write in your own language, easier testing, SDKs, Wasm


update packages

:x: Build TheIdServer 2.3.1-fix-dependencies1-0076 failed (commit https://github.com/Aguafrommars/TheIdServer/commit/768166355a by @)

:white_check_mark: Build TheIdServer 2.3.1-fix-dependencies.1+76.build.1280 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/768166355a by @)


Add auto-detection for decoding bytes to string when parsing an ASCII Data file.

Hi, I'm working on using Apache Spark to read in massive amounts of COMTRADE files in a distributed computing fashion. The logical flow of this is to read in all .cfg files as strings, and all .dat files as binary (since we don't know if are ASCII or binary until the .cfg file is processed) from a data lake.
Then the files are joined, based upon their filename, and the python-comtrade library is used to process the files on Spark distributed worker nodes.  This line of code checks to see if the contents passed into the parse() function are of type bytes and, if so, decodes them into a string for ASCII processing.

Hi @coltonpeltier-db thanks for your contribution! Nice addition.


Implement mySky.setDataLink

tested, registry entries match skyns:// compatable entries.

I think we should hold off on this commit until we know what's going on with Skylinks v2.

We'll want to re-run checks probably since now we don't want these registry entries to match skynet:// compatible entries.


Update how to run ansible on cloud shell document

@yuwzho : Thanks for your contribution! The author, @tomarcher, has been notified to review your proposed change.

@yuwzho : Thanks for your contribution! The author, @iainfoulds, has been notified to review your proposed change.

@yuwzho : Thanks for your contribution! The author, @iainfoulds, has been notified to review your proposed change.

@yuwzho : Thanks for your contribution! The author, @iainfoulds, has been notified to review your proposed change.

@yuwzho : Thanks for your contribution! The author, @iainfoulds, has been notified to review your proposed change.

@yuwzho : Thanks for your contribution! The author, @iainfoulds, has been notified to review your proposed change.

Thanks for the contribution, @yuwzho. Unfortunately, this is too large of a modification of core docs to accept as-is without additional discussion. Happy to help listen to your feedback and incorporate some of these changes, but please reach out internally to @TomArcher and myself so that we can discuss these.
For now, #please-close
CC: @jpconnock


Camelcase fixes

Addressing python naming concerns raised in issue #24 raised by @mrocklin - Note that name changes require changes in the ucx-based dask code (calls to ucp.ucp_py_ep need to be changed to ucp.EndPoint).  I will submit a PR to that repository if/when these changes are accepted.

Thanks @rjzamora .  Can you verify that tests continue to pass?
You should be able to check this by installing pytest
conda install pytest

And then running
pytest tests/

from the root ucx-py directory (see the folder there)

Yeah, good point.  I have been running the pytests, and all tests have been passing except tests/test_send_recv_obj.py (which hangs).  However, I get the same behavior for devel

Yeah, same.  I've been slowly trying to track this down in https://github.com/Akshay-Venkatesh/ucx-py/pull/86

@Akshay-Venkatesh are you comfortable with changes like this?

@Akshay-Venkatesh are you comfortable with changes like this?

@mrocklin It's a departure from C-style of coding for me but it makes sense given the context. I see usage similar to what you've suggested in Cython documentation as well, so pretty comfortable.

Yeah, good point. I have been running the pytests, and all tests have been passing except tests/test_send_recv_obj.py (which hangs). However, I get the same behavior for devel

Hi, @rjzamora. I see test_send_recv_obj hanging on devel as well. I'll open a separate issue for that now but I don't think that's related to your PR.

@rjzamora Noticed that there's already an issue for this here #69 Will address this soon

I took a look through the file and the only other thing I saw was ListenerFuture.ucp_listener, which should maybe be ListenerFuture.listener ?

@rjzamora @mrocklin When we recently moved from ucp_py to ucp directory/name, looks like we missed a change and this was causing a hang. I've pushed a change to fix this to allow test_send_recv_obj.py test to pass.  Can you check if this helps?

@Akshay-Venkatesh I just pulled from devel, rebuilt, and ran tests and got the following:
(ucx-dev) mrocklin@dgx15:~/ucx-py$ py.test tests/test_send_recv_obj.py -s --verbose
==================================== test session starts ====================================
platform linux -- Python 3.7.3, pytest-4.4.1, py-1.8.0, pluggy-0.9.0 -- /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python
cachedir: .pytest_cache
rootdir: /home/nfs/mrocklin/ucx-py
plugins: asyncio-0.10.0
collected 7 items

tests/test_send_recv_obj.py::test_send_recv_bytes PASSED
tests/test_send_recv_obj.py::test_send_recv_memoryview PASSED
tests/test_send_recv_obj.py::test_send_recv_numpy PASSED
tests/test_send_recv_obj.py::test_send_recv_cupy [dgx15:13455:0:13455] Caught signal 11 (Segmentation fault: invalid permissions for mapped object at address 0x7f824b200000)
==== backtrace ====
    0  /home/nfs/mrocklin/miniconda/envs/ucx-dev/lib/libucs.so.0(+0x21b50) [0x7f82d0415b50]
    1  /home/nfs/mrocklin/miniconda/envs/ucx-dev/lib/libucs.so.0(+0x21dc4) [0x7f82d0415dc4]
    2  /lib/x86_64-linux-gnu/libc.so.6(+0x14e057) [0x7f82d3669057]
    3  /home/nfs/mrocklin/miniconda/envs/ucx-dev/lib/libucp.so.0(ucp_dt_pack+0xea) [0x7f82d0b20d3a]
    4  /home/nfs/mrocklin/miniconda/envs/ucx-dev/lib/libucp.so.0(+0x2ec38) [0x7f82d0b2fc38]
    5  /home/nfs/mrocklin/miniconda/envs/ucx-dev/lib/libuct.so.0(uct_rc_mlx5_ep_am_bcopy+0xd9) [0x7f82d088bf29]
    6  /home/nfs/mrocklin/miniconda/envs/ucx-dev/lib/libucp.so.0(+0x2f3c7) [0x7f82d0b303c7]
    7  /home/nfs/mrocklin/miniconda/envs/ucx-dev/lib/libucp.so.0(ucp_tag_send_nb+0x53a) [0x7f82d0b4008a]
    8  /home/nfs/mrocklin/ucx-py/ucp/_libs/ucp_py.cpython-37m-x86_64-linux-gnu.so(ucp_py_ep_send_nb+0x2d) [0x7f82d0e2324d]
    9  /home/nfs/mrocklin/ucx-py/ucp/_libs/ucp_py.cpython-37m-x86_64-linux-gnu.so(+0x65f30) [0x7f82d0ddbf30]
   10  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyMethodDef_RawFastCallKeywords+0x264) [0x55d8a99fd6e4]
   11  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyMethodDescr_FastCallKeywords+0x4f) [0x55d8a99fd86f]
   12  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x4c4c) [0x55d8a9a5907c]
   13  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyGen_Send+0x2a2) [0x55d8a99f6672]
   14  /home/nfs/mrocklin/miniconda/envs/ucx-dev/lib/python3.7/lib-dynload/_asyncio.cpython-37m-x86_64-linux-gnu.so(+0xc18e) [0x7f82d101e18e]
   15  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyObject_FastCallKeywords+0x49b) [0x55d8a99fdd2b]
   16  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(+0x20abc3) [0x55d8a9a8ebc3]
   17  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyMethodDef_RawFastCallDict+0x199) [0x55d8a99c08b9]
   18  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyCFunction_FastCallDict+0x21) [0x55d8a99c0ae1]
   19  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x5d21) [0x55d8a9a5a151]
   20  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyFunction_FastCallKeywords+0xfb) [0x55d8a99fc79b]
   21  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x6a0) [0x55d8a9a54ad0]
   22  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyFunction_FastCallKeywords+0xfb) [0x55d8a99fc79b]
   23  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x6a0) [0x55d8a9a54ad0]
   24  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyFunction_FastCallKeywords+0xfb) [0x55d8a99fc79b]
   25  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x6a0) [0x55d8a9a54ad0]
   26  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyFunction_FastCallKeywords+0xfb) [0x55d8a99fc79b]
   27  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x6a0) [0x55d8a9a54ad0]
   28  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalCodeWithName+0xbb9) [0x55d8a999adb9]
   29  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyFunction_FastCallDict+0x1d5) [0x55d8a999b5d5]
   30  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x1e20) [0x55d8a9a56250]
   31  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalCodeWithName+0xbb9) [0x55d8a999adb9]
   32  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyFunction_FastCallKeywords+0x387) [0x55d8a99fca27]
   33  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x14ce) [0x55d8a9a558fe]
   34  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalCodeWithName+0x2f9) [0x55d8a999a4f9]
   35  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyFunction_FastCallKeywords+0x387) [0x55d8a99fca27]
   36  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x4aa9) [0x55d8a9a58ed9]
   37  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyFunction_FastCallKeywords+0xfb) [0x55d8a99fc79b]
   38  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x4aa9) [0x55d8a9a58ed9]
   39  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalCodeWithName+0x2f9) [0x55d8a999a4f9]
   40  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyFunction_FastCallDict+0x400) [0x55d8a999b800]
   41  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyObject_Call_Prepend+0x63) [0x55d8a99b2c43]
   42  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(+0x17116a) [0x55d8a99f516a]
   43  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyObject_FastCallKeywords+0x49b) [0x55d8a99fdd2b]
   44  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x56ac) [0x55d8a9a59adc]
   45  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyFunction_FastCallKeywords+0xfb) [0x55d8a99fc79b]
   46  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x6a0) [0x55d8a9a54ad0]
   47  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyFunction_FastCallDict+0x10b) [0x55d8a999b50b]
   48  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x1e20) [0x55d8a9a56250]
   49  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalCodeWithName+0xbb9) [0x55d8a999adb9]
   50  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyFunction_FastCallKeywords+0x387) [0x55d8a99fca27]
   51  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x14ce) [0x55d8a9a558fe]
   52  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalCodeWithName+0x2f9) [0x55d8a999a4f9]
   53  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyFunction_FastCallKeywords+0x387) [0x55d8a99fca27]
   54  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x4aa9) [0x55d8a9a58ed9]
   55  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyFunction_FastCallKeywords+0xfb) [0x55d8a99fc79b]
   56  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalFrameDefault+0x4aa9) [0x55d8a9a58ed9]
   57  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyEval_EvalCodeWithName+0x2f9) [0x55d8a999a4f9]
   58  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyFunction_FastCallDict+0x400) [0x55d8a999b800]
   59  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(_PyObject_Call_Prepend+0x63) [0x55d8a99b2c43]
   60  /home/nfs/mrocklin/miniconda/envs/ucx-dev/bin/python(+0x17116a) [0x55d8a99f516a]
===================
Segmentation fault

This might be a separate issue.

@mrocklin I get the same

Moved conversation to https://github.com/Akshay-Venkatesh/ucx-py/issues/94

Is this ready to go in?
Also @rjzamora thoughts on https://github.com/Akshay-Venkatesh/ucx-py/pull/93#issuecomment-486841644 ?

I'm about to address the review suggestions by @mrocklin and @Akshay-Venkatesh - I agree with the ucp_listener change

pytest are passing (besides the problems we already know about),  but I am getting a segfault for the server end of the recv-into-client.py benchmark (https://github.com/rjzamora/ucx-py/blob/camelcase-fixes/benchmarks/recv-into-client.py):
UCX_MEMTYPE_CACHE=n UCX_RNDV_SCHEME=put_zcopy UCX_NET_DEVICES=mlx5_0:1 UCX_TLS=rc,cuda_copy CUDA_VISIBLE_DEVICES=0 python3 benchmarks/recv-into-client.py -o cupy
[1556288710.045742] [dgx16:70159:0]     ucp_worker.c:332  UCX  ERROR Signaling wakeup failed: Bad file descriptor
[dgx16:70159:0:70159] Caught signal 11 (Segmentation fault: invalid permissions for mapped object at address 0x55dba135dea0)
==== backtrace ====
    0  /home/nfs/rzamora/miniconda3/envs/ucx-dev/lib/libucs.so.0(+0x21b50) [0x7fbbb3be4b50]
    1  /home/nfs/rzamora/miniconda3/envs/ucx-dev/lib/libucs.so.0(+0x21dc4) [0x7fbbb3be4dc4]
    2  [0x55dba135dea0]
===================
Segmentation fault

Everything finishes fine on the client side, but I don't see the same error in devel

@Akshay-Venkatesh do you have thoughts on what might cause the error above?

I don't have the full view of the error. From what @rjzamora indicates

The error isn't seen on devel
Things finish on client but not server on this branch, so I would need to see the commands executed on both ends

Sorry @Akshay-Venkatesh - Here are the commands I am using on a dgx...
To run the server process:
$ UCX_MEMTYPE_CACHE=n UCX_RNDV_SCHEME=put_zcopy UCX_NET_DEVICES=mlx5_0:1 UCX_TLS=rc,cuda_copy CUDA_VISIBLE_DEVICES=0 python3 benchmarks/recv-into-client.py -o cupy

To run the client process:
$ UCX_MEMTYPE_CACHE=n UCX_RNDV_SCHEME=put_zcopy UCX_TLS=rc,cuda_copy UCX_NET_DEVICES=mlx5_0:1 CUDA_VISIBLE_DEVICES=1 python3 benchmarks/recv-into-client.py -s <IB0_IP> -p 13337 -o cupy

The client finishes normally, and prints:
Roundtrip benchmark
-------------------
n_iter   | 10
n_bytes  | 10.00 MB
recv     | recv_into
object   | cupy
inc      | False

===================
631.64 MB / s
===================

The server process gives the error above.  Note that the problem could be in dask.

@rjzamora Thanks for the repro. I'm able to reproduce this on devel now as well.
[prm-dgx-02:70633:0:70633] Caught signal 11 (Segmentation fault: invalid permissions for mapped object at address 0x2245600)
==== backtrace ====
    0  /home/akvenkatesh/ucx-github/build/lib/libucs.so.0(+0x26cfb) [0x2abc56019cfb]
    1  /home/akvenkatesh/ucx-github/build/lib/libucs.so.0(+0x26e59) [0x2abc56019e59]
    2  /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390) [0x2abc51f98390]
    3  [0x2245600]
===================

akvenkatesh@prm-dgx-03:~/ucx-py$ UCX_MEMTYPE_CACHE=n UCX_RNDV_SCHEME=put_zcopy UCX_NET_DEVICES=mlx5_0:1 UCX_TLS=rc,cuda_copy CUDA_VISIBLE_DEVICES=1 python3 benchmarks/recv-into-client.py -o cupy -s IP -p 13337
Roundtrip benchmark
-------------------
n_iter   | 10
n_bytes  | 10.00 MB
recv     | recv_into
object   | cupy
inc      | False

===================
5.55 GB / s
===================

I'll look at this in more detail but merging this PR is good from my viewpoint.

@rjzamora I noticed that the benchmark doesn't have the client and server synchronizing before they either one of them calls ucp.fin(). I've made the following commits to fix this: 253e122 a6c0532


feat: enable binary download via http protocol

I added a simple logic to support Redis binary download using the HTTP protocol.
I want to use a custom .tar.gz file uploaded on the private network file storage, which only supports HTTP.
However, it seems impossible to download via HTTP because the protocol is fixed to HTTPS. It leads to an error such as 'SSL routines:ssl3_get_record:wrong version number'
I couldn't find a contribution guide, so I just open this PR :)

Thank you for the contribution!


Object.assign not inferring

🔎 Search Terms
typescript Object.assign
💻 Code
function foo() {
    const a = {a:1, b:2}
    const b = {}

    Object.assign(b,a)
    return b
}

🙁 Actual behavior
ReturnType<foo> is {} when
{
    a: number;
    b: number;
}

could be inferred

Please remember to completely fill out the issue template.
This is working as intended. Object.assign() does not propagate type information to it's target property, so TypeScript is not aware of any changed type of b and the type remains {}.

Shouldn't it?

The only way to change the type of another variable like these are assertion functions, but these are not allowed to return anything

I'm pretty sure there's a feature request for that, but I can't find it.

I'm pretty sure there's a feature request for that, but I can't find it.

https://github.com/microsoft/TypeScript/issues/40562


Some ideas

Hii there,
Finally got the plugin to work after having this issue: #168.
So now I can finally get some ideas and other "issues" flow:

%kills%, %deaths% and %kdr% all return -1 if you never died or made a kill.
add an option to disable "sorting". right now, the sidebar sorts out the stuff based on their values.
custom "layout"?
multiple "titles" (to seperate serverwide stats from the player stats)

Cheers

%kills%, %deaths% and %kdr% all return -1 if you never died or made a kill.

This means you deactivated pvpstats

add an option to disable "sorting". right now, the sidebar sorts out the stuff based on their values.

Limitation by Mojang. There is no way to change it, because it was implemented as a leaderboard

custom "layout"?

Please explain. Currently it's possible to make your own lines, you just have to specify a constant number as value.

add an option to disable "sorting". right now, the sidebar sorts out the stuff based on their values.

It is possible, I've seen other plugins do it aswell (and Hypixel does it aswell). BUt I think it would be better if you make another plugin for it.

%kills%, %deaths% and %kdr% all return -1 if you never died or made a kill.
oops, fixed that :)

custom "layout"?

I mean like having it look like:
+--Server Stats--+
|   Online: 12   |
|   TPS:    80   |
|   Ping:   10   |
+----------------+

+--PvP Stats--+
|  Kills: 120 |
|  Deaths: 3  |
|  KDR: 40.00 |
+-------------+


notif android: Keep the notification icon from being resource-shrunk away

Details in the new comment and in the issue thread.
Fixes: #528

Interesting! Thanks for the fix; merging.


ExportSolution from Onpremise CRM failure

Hi, i am working on a powershell script to export the solution from On-premise Dynamics CRM which is giving me a different error every time when i execute the script. i am receiving multiple issues as below

sometimes it executes fine and connects to Dynamics CRM and gives error as
"Export-XrmSolution : Solution LookupFiltering could not be found"

sometimes it gives error as Object reference not set to an instance
Set-XrmSolutionVersion : Object reference not set to an instance of an object.

sometimes it gives error as unable to login to CRM

Could you let me know what exactly i am missing in the script
Kindly help,
Thanks!!!

@daakaram there could be a number of things that are contributing to this. I suggest you check the below...

Your connection string looks wrong as you are using office 365 for on premise.
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/xrm-tooling/use-connection-strings-xrm-tooling-connect
Ensure there is no proxy interfering with your connection, you may need to add some PS script to work with proxy if needed


Update README.md

Fixed a typo on line 26. Was trying to install to /Library/SApplicationSupport/lashBuddy

Already in mattlavine pull request. You can close this.

Already in the mattlavine pull request, closed.


Bug: method "insertIn" doesn't care if we drop node into another node which is in leaves array in config

If we want to use drag and drop while async loading and there are some nodes without children, we put their ids into the leaves array in config. If we drag and drop into the node which is in leaves array, icon will not show and node id won't be removed from leaves array.
Way to reproduce: drag node into the "text3" or "text4".
Sandbox: https://codesandbox.io/s/async-forked-qq3mii?file=/src/App.vue

Hello, i'm sorry i'm very busy right now, I will take a look as soon as I can.

It's alright

Hey I wanted to have a look but I feel that your example is not working anymore can you create a new test case please :) ?

@N00ts this should work, steps to reproduce: drag task3 into task4

Hello, what you try to do is to handle "leaves" manually. The icon does not appear because you keep the id the drop target node in config.leaves. I modifed the project and put "node-drop" after insert event so you can handle it manually in this event.
Regards

@N00ts, okay. I'm closing this issue


Implement some operators.*

This PR implements the following operators for Omnisci arrays:

operator.add
operator.and_
operator.eq
operator.ge
operator.gt
operator.in
operator.is
operator.is_not
operator.le
operator.lshift
operator.lt
operator.mul
operator.ne
operator.not_in
operator.or_
operator.pow
operator.rshift
operator.sub
operator.truediv
operator.xor

And the numpy function invert
Edit: A complete list of Python operators can be found in the link below:
https://github.com/xnd-project/rbc/issues/90

I have updated the code to remove boilerplate code (for-loop) common to all operators implemented here.

PR is ready for a review


[Win] Deleting folder results in EPERM error that locks all folders that are recursively watched

The Issue:
[Windows only] Chokidar (and fs.watch under the hood) throws an EPERM error when a child folder of a folder that is being watched recursively is deleted.
According to notes i saw on another bug, the Chokidar code here is supposed to deal with it:
https://github.com/paulmillr/chokidar/blob/f17186dff7b27c67b17a644c333cc239b42827ba/lib/nodefs-handler.js#L89-L99
In fact, the comments even lead to this old underlying bug in node:
https://github.com/nodejs/node-v0.x-archive/issues/4337 "Deleting a watched folder in Windows ALWAYS rise an [Error: watch EPERM]"
I'm not sure what these lines are supposed to do to address this bug though. It seems to be just broadcasting the error, as long as the file exists.
Now it would be one thing if I could ignore this error and everything would continue to work. In fact, the watchers do continue to work, receiving the unlinkDir event and others. However, a recursive watcher will then lock all child folders, and any file system operation (delete, rename, etc) on them will fail due to EPERM, whether the operation is through node or the windows file system GUI. This issue doesn't seem to occur with non-recursive watchers, perhaps because the underlying node issue is to throw that error for the top level folder being watched. I'm not sure if Chokidar is creating many watchers for child folders under the hood, but if it is, that would make sense with this old bug.
Turning on the option to suppress EPERM errors from within Chokidar does not stop it from locking up afterwards.
Shutting down the watcher after the EPERM error gets rid of the lock. However, restarting causes it to come back(!).
It doesn't seem to be possible to stop the EPERM error from occurring in the first place using Chokidar or fs.watch, as far as I know. Though perhaps NSFW would be an alternative library that doesn't rely on fs.watch.
Device:
Windows 10 Pro, 64bit
Example code:
const watcher = chokidar.watch(path, {
  persistent: true,
  ignoreInitial: true,
  cwd: path
});

// insert business logic on events

watcher.on('error', error => {
  logger.log(error)
  if (error.code === 'EPERM' && Config.WINDOWS) {
    // recursive watcher causes a lock on all watched folders on Windows after EPERM error, so could close it here
    // ...but restarting it causes the locking issue to come back, so that's not the solution
  }
});

I'm aware that the EPERM fs.watch errors are out of Chokidar's hands. However, I'm surprised that the resulting locking issue occurs. Any thoughts on solutions or, for the meantime, workarounds for the locking issue?

Update: We switched from using Chokidar to Node Sentinel File Watcher (https://www.gitkraken.com/nsfw). As a native library, it avoids Windows EPERM errors and the locking issues that resulted. I'm not closing this bug, though, since this is still a major issue with Chokidar.

See https://github.com/paulmillr/chokidar/issues/566#issuecomment-269698736

Update to Chokidar v3, it should resolve this.

it is not solved in v3...

Let's move to #566


undefined symbol: __cudaRegisterFatBinaryEnd

I am getting the following error and I don't understand how to get rid of it coz my cuda version and symlinks are correct.
ImportError: /home/anam/Codes/mask-rcnn.pytorch/lib/model/roi_pooling/_ext/roi_pooling/_roi_pooling.so: undefined symbol: __cudaRegisterFatBinaryEnd
Command Ran is just a try to run inference
python tools/infer_simple.py

System information

Operating system: Linux20.04
CUDA version: 10.0
cuDNN version: 7.5
GPU models (for all devices if they are not all the same): RTX
python version: 3.6.6
pytorch version: 0.3.1
Anything else that seems relevant: ?

I have the same issue. Any insight would be appreciated.


feat: Update GridTable's cardStyle

Adds 'GridStyle.nonHeaderRowCss' to directly apply styles to non-header row elements. Adds 'GridStyle.rowHoverCss' to apply hover styles to non-header row elements Updates cardStyle to take advantage of the new styles to provide a box-shadow and border color change when hovering over a row. Updates cardStyle to apply more styles directly on the row element rather than on the individual cells

If "rowHoverCss" means "non-header", which is cool, do we need the "nonHeader" prefix for nonHeaderRowCss? Could we align those to the same prefix-or-no-prefix?


Updating Getting Started page

Docs Build status updates of commit 26d9d65:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/TOC.yml
:white_check_mark:Succeeded

articles/install-guide/index.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 543b14d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/TOC.yml
:white_check_mark:Succeeded

articles/install-guide/index.md
:white_check_mark:Succeeded

articles/install-guide/python.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit d379818:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/install-guide/index.md
:warning:Warning

Details

articles/TOC.yml
:white_check_mark:Succeeded

articles/install-guide/python.md
:white_check_mark:Succeeded

articles/install-guide/index.md

Line 29: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vs2017).
Line 37: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vscode).

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.

Docs Build status updates of commit 85c66fc:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/install-guide/index.md
:warning:Warning

Details

articles/TOC.yml
:white_check_mark:Succeeded

articles/install-guide/python.md
:white_check_mark:Succeeded

articles/install-guide/index.md

Line 29: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vs2017).
Line 37: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vscode).

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.

Docs Build status updates of commit bd98b6c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/install-guide/index.md
:warning:Warning

Details

articles/TOC.yml
:white_check_mark:Succeeded

articles/install-guide/python.md
:white_check_mark:Succeeded

articles/install-guide/index.md

Line 29: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vs2017).
Line 37: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vscode).

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.

Docs Build status updates of commit 0cd1b1e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/install-guide/index.md
:warning:Warning

Details

articles/TOC.yml
:white_check_mark:Succeeded

articles/install-guide/python.md
:white_check_mark:Succeeded

articles/install-guide/index.md

Line 29: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vs2017).
Line 37: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vscode).

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.

Docs Build status updates of commit a870895:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/install-guide/index.md
:warning:Warning

Details

articles/TOC.yml
:white_check_mark:Succeeded

articles/install-guide/python.md
:white_check_mark:Succeeded

articles/install-guide/index.md

Line 29: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vs2017).
Line 37: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vscode).

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.

Docs Build status updates of commit beaeefd:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/install-guide/index.md
:warning:Warning

Details

articles/TOC.yml
:white_check_mark:Succeeded

articles/install-guide/python.md
:white_check_mark:Succeeded

articles/install-guide/index.md

Line 29: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vs2017).
Line 37: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vscode).

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.

Docs Build status updates of commit 69fbccf:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/install-guide/index.md
:warning:Warning

Details

articles/TOC.yml
:white_check_mark:Succeeded

articles/install-guide/python.md
:white_check_mark:Succeeded

articles/install-guide/index.md

Line 29: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vs2017).
Line 37: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vscode).

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.

Docs Build status updates of commit 840fe0f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/install-guide/index.md
:warning:Warning

Details

articles/TOC.yml
:white_check_mark:Succeeded

articles/install-guide/jupyter.md
:white_check_mark:Succeeded

articles/install-guide/python.md
:white_check_mark:Succeeded

articles/install-guide/index.md

Line 29: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vs2017).
Line 37: [Warning] Invalid file link:(~/install-guide/quickstart?tabs=tabid-vscode).

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.

Docs Build status updates of commit 174fbb5:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/install-guide/index.md
:warning:Warning

Details

articles/TOC.yml
:white_check_mark:Succeeded

articles/install-guide/jupyter.md
:white_check_mark:Succeeded

articles/install-guide/python.md
:white_check_mark:Succeeded

articles/install-guide/index.md

Line 29: [Warning] Invalid file link:(~/quickstart?tabs=tabid-vs2017).
Line 37: [Warning] Invalid file link:(~/quickstart?tabs=tabid-vscode).

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.

Docs Build status updates of commit ff24a2c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/install-guide/index.md
:warning:Warning

Details

articles/TOC.yml
:white_check_mark:Succeeded

articles/install-guide/jupyter.md
:white_check_mark:Succeeded

articles/install-guide/python.md
:white_check_mark:Succeeded

articles/install-guide/index.md

Line 29: [Warning] Invalid file link:(~/quickstart?tabs=tabid-vs2017).
Line 37: [Warning] Invalid file link:(~/quickstart?tabs=tabid-vscode).

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.


Check to make sure Java is installed on a PC

Confirm Java is installed on the PC.
Should check this on the endcoder form load

I did something like this before by just checking the registry for the value. If it's not there then it is not installed. Project will need to be changed to x64 I think in order for the registry code to work,
Some code that might work:
RegistryKey rk = Registry.LocalMachine;
RegistryKey subKey = rk.OpenSubKey("SOFTWARE\\JavaSoft\\Java Runtime Environment");
string currentVerion = subKey.GetValue("CurrentVersion").ToString();

Issue is confirmed to be fixed.


Readme isn't clear about promise polyfill

The readme says you just need to do bower install es6-promise, but I'm guessing you also need to require('es6-promise').polyfill();?

Depends. At GitHub, we're loading the es6-promise v1.0 version which doesn't need an explicit call. However, in the v2.0 version the explicit polyfill() call is necessary. In the v2.1 version, the call won't be necessary anymore (I haven't verified this).
See https://github.com/github/fetch/issues/114#issuecomment-89342951 https://github.com/jakearchibald/es6-promise/issues/75
@dgraham We definitely need a documentation update to address this, since people right now are mostly on es6-promise 2.0 (their version 2.1 is just fresh out of the oven).

Closing as stale. It's possible the es6-polyfill has been fixed by now. If not, a pull request updating the documentation is welcome.


add new endpoint for getting dev container raw data

/claim #8
usage:
curl http://localhost:5001/?repo_url=https://github.com/rajeshj11/test-github-actions

@nkkko please review

hey, sorry, it took me some time to resolve backlog, you have killed the main route and now it serves your endpoint

this should be added functionality for programatic use

hey, sorry, it took me some time to resolve backlog, you have killed the main route and now it serves your endpoint
this should be added functionality for programatic use

let me check

@nkkko fixed the breaking issue.

@nkkko This has been pending for a while. Do we still need these changes?

@nkkko This has been pending for a while. Do we still need these changes?

@nkkko ^^

@rajesh-jonnalagadda I’ve updated main with some changes that affect this PR. Could you please rebase your branch onto the latest main and resolve any conflicts that come up? Once that’s done, we can review the updated changes and move forward.

@rajesh-jonnalagadda I’ve updated the main with some changes that affect this PR. Could you please rebase your branch onto the latest main and resolve any conflicts that come up? Once that’s done, we can review the updated changes and move forward.

@mojafa
I have merged the latest main into my branch. I don't see any conflicts.

@rajesh-jonnalagadda  sorry for the late one. reviewing this PR

@rajesh-jonnalagadda using curl newendpoint works well:

however returning the devcontainer.json as plain text to allow easy piping into bash scripts or workflows for automation doesn't work. Please fix this

however returning the devcontainer.json as plain text to allow easy piping into bash scripts or workflows for automation doesn't work. Please fix this

I did not understand this. Can you please explain to me how my changes will be reflected in the port/prod test without merging my changes?

however returning the devcontainer.json as plain text to allow easy piping into bash scripts or workflows for automation doesn't work. Please fix this

I did not understand this. Can you please explain to me how my changes will be reflected in the port/prod test without merging my changes?

I'm not entirely sure, but the following command should perform the desired task locally.
curl http://localhost:5001/?repo_url=https://github.com/rajeshj11/test-github-actions > .devcontianer/devcontainer.json

@rajesh-jonnalagadda
This commands works well if I directly access the URL and  outputs the correct devcontainer.json to the terminal. curl http://localhost:5001/?repo_url=https://devcontainer.ai/#https://github.com/daytonaio/daytona
however, when i use curl to pipe the output to a file like this:
curl http://localhost:5001/?repo_url=https://devcontainer.ai/#https://github.com/daytonaio/daytona > .devcontainer/devcontainer.json
The content in the newly generated file isn’t correct and doesn’t match the expected JSON output.

@rajesh-jonnalagadda This commands works well if I directly access the URL and outputs the correct devcontainer.json to the terminal. curl http://localhost:5001/?repo_url=https://devcontainer.ai/#https://github.com/daytonaio/daytona
however, when i use curl to pipe the output to a file like this:
curl http://localhost:5001/?repo_url=https://devcontainer.ai/#https://github.com/daytonaio/daytona > .devcontainer/devcontainer.json  The content in the newly generated file isn’t correct and doesn’t match the expected JSON output.

Let me check

@rajesh-jonnalagadda any updates?

@rajesh-jonnalagadda any updates?

I'm currently participating in a hackathon and working with my team, so it may take me a few days to address this issue.

No worries


[BUG] Missing many data for some of the inverters after upgrading to 0.6.x

Describe the bug
After upgrading to 0.6.x, most inverters are working fine (albeit I need to remove some old sensors and update the ID of the new sensors), but there are some inverters lose majority of its sensors. See the comparison below:

Screenshots showing different inverters

Inverter that works normally
Inverter that loses majority of the sensors

Account type

[ ] Installer
[x] DIY / DHZ
[ ] Home Owner (This integration is not (fully) functional with a home owner account!)

Envoy

[x] Metered with CTs installed

[ ] Metered without CTs

[ ] Standard

FW version: D8.2.127

Amount of micro inverters connected: 56

Home Assistant

Version: 2024.12.1

Additional context
I took a look at some other issues, specially I saw https://github.com/vincentwolsink/home_assistant_enphase_envoy_installer/issues/189#issuecomment-2512484180 and also tried to fetch data from ivp/pdm/device_data, and it seems that it only lists 50 inverters, and the inverters lose the sensors can't be found in that data. So it seems like this endpoint doesn't work as reliably as the previous one I suppose?

And indeed I can found the inverters in the previous ivp/peb/devstatus endpoint but not the new one.

Hi! That is a serious amount of inverters 😁
Can you please provide the output of the ivp/pdm/device_data endpoint?

Looks like the tail-end of device_data shows the limit of 50. Device count matches my 24 inverters and 1 q-relay.
    "deviceCount": 25,
    "deviceDataLimit": 50

Oh, good point. I have 56 inverters + 2 relays so it should be 58 devices in total. Maybe that's over the limit of this endpoint?

Might be something that can be configured as datasheets states it can communicate with up to 300 inverters.

Maybe @krbaker can help shed some light on how to use a different limit or do the pagination on this endpoint?

Maybe this limit is configurable. Or they implemented some sort of pagination.

For now, what I can do is if there are more than 50 devices, fallback to the devstatus endpoint. This is not ideal though. Better is to find out how to do pagination..

Things are now getting a bit too complex for my liking. But I made usage of the old devstatus endpoint configurable for now in #195 .

Keeping this open, since pagination on the new endpoint would still be the preferred solution.

I can confirm that enabling devstatus endpoint option in configuration and reload the integration makes those information come back, thanks! (It does mean all the new sensors become unavailable but that's okay.)


Add script for regenerating bindings

This builds on #82 which did the same thing for the 0.2.x version of the crates.

I do miss the LF at the end of regenerate_bindings.sh but it's a minor thing

Fixed!

Will make so easy to add new bindings

I need to have a look at adding the same for the other FFI crates.

Btw I ran the script through shellcheck and got the following:

In /tmp/x.sh line 15:
        rustup target install $target
                              ^-----^ SC2086 (info): Double quote to prevent globbing and word splitting.

Did you mean:
        rustup target install "$target"

In /tmp/x.sh line 19:
    cargo build --target $target --features generate-bindings
                         ^-----^ SC2086 (info): Double quote to prevent globbing and word splitting.

Did you mean:
    cargo build --target "$target" --features generate-bindings

In /tmp/x.sh line 20:
    find ../target/$target/ -name pkcs11_bindings.rs | xargs -I '{}' cp '{}' src/bindings/$target.rs
    ^-- SC2038 (warning): Use -print0/-0 or -exec + to allow for non-alphanumeric filenames.
                   ^-----^ SC2086 (info): Double quote to prevent globbing and word splitting.
                                                                                ^-----^ SC2086 (info): Double quote to prevent globbing and word splitting.

Did you mean:
    find ../target/"$target"/ -name pkcs11_bindings.rs | xargs -I '{}' cp '{}' src/bindings/"$target".rs

In /tmp/x.sh line 23:
        rustup target remove $target
                             ^-----^ SC2086 (info): Double quote to prevent globbing and word splitting.

Did you mean:
        rustup target remove "$target"

I'm not a shell expert by any means so you'd have to decide if these lints are something to listen to but I wanted to provide yet another angle :)

Ok, fixed those problems flagged by shellcheck.


Make CollectionTTL a pointer and try to make behave like our other SDKS when no value passed

Default TTL behavior when no value is passed:

use default ttl that is specified when a cache client is created
refresh ttl is true by default
.NET SDK default TTL treatment: https://github.com/momentohq/client-sdk-dotnet/blob/4122f30029c03f2db173656a1e627fd39fdd0bca/src/Momento.Sdk/Requests/CollectionTtl.cs#L26


Explorer actions should also be visible on menu

From @misolori
After selecting "open folder" and realizing that it wasn't what I wanted, I went to the menu to open a repository instead and realized that neither "Open Folder" or "Open Repository" was anywhere listed:

Verification: you see a "Open Folder" action in the file menu on vscode.dev and it works (= adds the folder to the workspace).


Artillery helper

Has repair, as well as a strong melee attack to break up anyone who gets near.
Requires code to coordinate movement.

More space efficient than giving every artillery regen.

Duplicate of #12.

Regen artillery works pretty well, so maybe priority is not repair...instead, it's a melee/zapper that follows the artillery around and destroys any units that try to get close.

Less of a problem now that artillery have mines?

Here, they were still a problem: https://www.notion.so/mizzao/Kaiznn-0dc35b4ac5b74d1eac57f945ace3be09

A healing missile bot that moves with the artillery could be helpful to beat up these pesky melee units.


Add file filtartion in srcDirectory

Now jsDstDir and cssDstDir are not filtering files. Plugin tries to minify all files in derectory and fails if there are not suitable file. jsDstDir should filter and minify only *.js files, as for cssDstDir.

The minifier should not fail when encountering non js or css files.
What type of file created the problem and which version are you using?
For more safety I could resolve this like this:
https://github.com/616slayer616/gradle-minify-plugin/pull/26

Yes, this amazing!


Circular countdown timer restricted to 3.0.0 and does not support higher versions of flutter

Using flutter version 3.3.10 doesn't work on circular_countdown_timer. Getting the error below.
Because circular_countdown_timer 0.2.3 requires Flutter SDK version >=1.17.0 and no versions of circular_countdown_timer match >0.2.3 <0.3.0, circular_countdown_timer ^0.2.3 is forbidden. So, because yourProject depends on circular_countdown_timer ^0.2.3, version solving failed.
Could the environment sdk be upgraded to support 3.3.10 ?

Hi everyone, I have released a new version 0.2.4 of the package on pub.dev after migrating it to the Flutter version 3.22.3


I have added my opensource android lib MAHAds to utils list

Thank you very much, you did a good job. :smiley:

Thanks to you much for merging. It's nice to see this reaction.


RFE: podman generate systemd should write files to their proper path

Currently, podman generate systemd --file writes to the current directory. This is problematic:

It requires the user to mv the file into the proper location, which is rife with possibilities for user error
After the mv, systemctl start may fail with the unhelpful message:

Failed to start container-xyz.service: Unit container-xyz.service not found.

This is because a unit file generated in $HOME will have the wrong SELinux type; it has to be fixed with restorecon.
All of this increases user suffering. I believe that podman generate systemd --file should Do The Right Thing:

root: create in /etc/systemd/system/
rootless: create in $HOME/.config/systemd/user/

Whether or not podman should create missing intermediate directories is a good question.
Make special note of the root case: it looks like there is some confusion about the destination path. There shouldn't be: /lib/systemd should never be touched by podman generate systemd, only by the actual podman rpm. Local configuration should be in /etc/systemd/system.
Since podman generate systemd --file currently spits out the path of the generated file, I believe this change can easily be made without fear of ambiguity or incompatibility.

Thanks for the detailed RFE, @edsantiago!

Since podman generate systemd --file currently spits out the path of the generated file, I believe this change can easily be made without fear of ambiguity or incompatibility.

It would still be a breaking change; some users might rely on the current behavior that all files are generated in pwd.
@rhatdan asked for an--install flag which I didn't like yesterday but the selinux issue really convinces me.

Yes I think having --install, and then we could add it to containers.conf to allow users to always do this.

This is because a unit file generated in $HOME will have the wrong SELinux type; it has to be fixed with restorecon.

Took me half an hour to realize what's wrong. I wish I had seen this. It should at least be listed in the man page as an FAQ.

Please open a PR to add the comment to the man page.

Looks like this as fixed in upstream


sass: cannot assign & to a var

Description
I'm trying to solve what's discussed here. It looks like I cannot assign ampersand to a var. For now I've it hardcoded as $_: '.foo';.
Input Before Beautification
This is what the code looked like before:
.foo{
  $_: &;

  &--bar{
    & #{$_}-baz{
      text-align:center;
    }
  }
}

Expected Output
The beautified code should have looked like this:
.foo--bar .foo-baz {
  text-align: center;
}

Actual Output
The beautified code actually looked like this:
Unsupported beautification result 'Parsing error: Please check the validity of the block starting from line #4

Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor
This beautified code does not look right!

Debug
Here is a link to the debug.md Gist:
Checklist
I have:

[ ] Tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[ ] Reloaded (or restarted) Atom to ensure it is not a caching issue
[ ] Searched through existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[ ] Filled out the Input, Expected, and Actual sections above or have edited/removed them in a way that fully describes the issue.
[ ] Generated debugging information and added link for debug.md Gist to this issue

Would you mind doing me a huge favor and producing the debug.md file.  The beautifier is probably Pretty Diff, but I just want to make sure I have all my facts straight.  https://github.com/Glavin001/atom-beautify/blob/master/docs/troubleshooting.md

I just read your issue more closely and examined the Stackoverflow link.  Code beautifiers aren't going to provide this kind of service for you.  You need to find a compiler or transpiler.

I don't want the beautifier to compile the code, I want it to not complain about it on saving since I have enabled 'On save'.

Yeah, sorry I misunderstood.  That is definitely a bug.  What beautifier are you using?

CSScomb

I've just tried Pretty Diff and it doesn't complain, thereby it looks like it's CSSComb's problem. Also I mistakenly tried inputting the sass code here http://csscomb.com/online and it produces similar err. Can it be that you beautify sass with CSSComb before compilation?

@fly1ted I am not sure if that is a preference of the csscomb library, but in my opinion its a bug.  It is a design decision that is absolutely failing you as a user.  What likely happened is that they built their tool for an easily reproducible environment, like their web tool.  This makes testing and maintenance much faster for the core team, but it makes you lethargic and complacent to the concerns of dependent applications.  I am saying this from my own experience because Pretty Diff has had a nearly identical bug in the past (returning an error message instead of code).
I would recommend opening an issue with csscomb and linking back to this issue.

@prettydiff I've investigated the issue and came to this conclusion. cssomb is a css parser, hence the name, the reason it worked for scss is just it uses gonzales-pe parser that in turn supports scss. The latest csscomb uses relatively old gonzales-pe thus I think it maybe the reason why it doesn't work.

@fly1ted Thank you for this updated information.  I suggest opening an issue with csscomb so that they can update their dependency.

For future issues:

Please follow the issue template provided. More specifically, adding a link to the required debug.md Gist which includes debugging information that answers our most commonly asked questions.
Thank you.

I am closing this as a CSSComb bug: https://github.com/csscomb/csscomb.js/issues/494


daemonset pre pull images endpoints

Description
Adds a couple of endpoints to provide to the daemonset in charge of pre pulling images what images should be pulled.
Endpoints:

/environment-images/latest for a list of the latest environment images for every environment
ctl/orchest-images-to-pre-pull for the list of orchest images to pre pull (i.e. session related)

Sessions will now make use of a customized jupyter-server image correctly.

LGTM


Combines Andre's changes with some edits to ensure no profile needs to be set

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: andresriancho:x: 0xdabbad00You have signed the CLA already but the status is still pending? Let us recheck it.


Document direct CocoaPods in native code more

Currently, our optimized flow involves using cocoapods transiently by consuming entire plugins that includes dart and their corresponding native code.
There will be edge cases where the user doesn't use any plugins and just writes custom native iOS code and just want to bring in another custom native iOS cocoapod dependency (unrelated to flutter). Document that in that case, they'd have to follow standard iOS development patterns and create a Podfile and run pod install manually.

Issue moved to flutter/website #2086 via ZenHub


bug(hubble): crashes on mainnet

What is the bug?

@eddy on farcaster reported running into this crash:

1|hubble  | node: ../deps/rocksdb/rocksdb/db/write_batch.cc:1520: rocksdb::Status rocksdb::MemTableInserter::PutCFImpl(uint32_t, const rocksdb::Slice&, const rocksdb::Slice&, rocksdb::ValueType): Assertion `seq_per_batch_' failed.

How can it be reproduced? (optional)
Unclear
Additional context (optional)
Eddy says that only one instance of the hub is running.

The db corruption seems to be caused due to pm2 being over-eager on restarts. What was happening here is that the hub is crashing for a different reason (unable to traverse NAT) which causes the initial graceful shutdown. And then the hub goes into a crash loop due to db corruption after pm2's first restart.
I think we should handle and provide a clean error message for the nat traversal error.
For future reference, passing --restart-delay 1000 into pm2 fixes the db crash loop and should reveal the underlying error. If we keep seeing this, we can modify our instructions to always start pm2 with this param dive deeper into what's causing the bad interaction with pm2.

we saw another issue with @davidfurlong's hub and this


Fix the sample so that it actually builds and runs

No need for kapt databinding, since the sample runs without it

Done in #11


Update _index.md to make Contributor Guide section more readable

Why is this needed?
Moved the 'Projects' list lower down the page to improve readability, prioritize key information
Move 'Projects' for better readability
Signed-off-by: jaytiaki<EMAIL_ADDRESS>Thanks for contributing!
If this change is ready to go live immediately, make your pull request against the main branch. Otherwise, make your pull request against the drafts branch.

Thanks this makes it much easier to find the info on TAGs and Working groups, which kind of was getting buried under the long project list.

Thanks alot @carolynvs!


[Bug] miniapp updatespec wh uncurrectly

Version
1.5.2
Link to Minimal Reproduction
xxx
Steps to Reproduce

Current Behavior
Feishu mini program environment updateSpec can cause chart width and height errors
Expected Behavior
The width and height are still correct after updating spec
Environment
- OS:
- Browser:
- Framework:

Any additional comments?
No response

already fixed in 1.5.2


docker_container is --env-file support?

TL:DR does the docker cookbook support --env-file value? I see it listed as supported for version 0.34 of this cookbook but do not see any listing of it being removed in the CHANGELOG.
Cookbook version
2.5.8
Chef-client version
12.12.15
Platform Details
Ubuntu 14.04
Scenario:
I want to pass in a list of ENV variables into an docker container using pre-compiled JSON file.
Steps to Reproduce:
Attempt to start container with an ENV variables loaded from JSON file. Simliar to docker run --env-file  command.
Expected Result:
Container starts with ENV loaded inside container
Actual Result:
==> legacy_lb: ================================================================================
==> legacy_lb: Recipe Compile Error in /var/chef/cache/cookbooks/legacy_nginx/recipes/default.rb
==> legacy_lb: ================================================================================
==> legacy_lb:
==> legacy_lb:
==> legacy_lb: SyntaxError
==> legacy_lb: -----------
==> legacy_lb: /var/chef/cache/cookbooks/legacy_nginx/recipes/default.rb:41: syntax error, unexpected tSTRING_BEG, expecting keyword_do or '{' or '('
==> legacy_lb:
==> legacy_lb:   env-file "/opt/legacy/dynamic-loadbalancer/env.json"
==> legacy_lb:
==> legacy_lb:             ^
==> legacy_lb:
==> legacy_lb:
==> legacy_lb: Platform:
==> legacy_lb: ---------
==> legacy_lb: x86_64-linux
==> legacy_lb:
==> legacy_lb:
==> legacy_lb:
==> legacy_lb: Running handlers:
==> legacy_lb: [2016-07-16T21:18:26+00:00] ERROR: Running exception handlers
==> legacy_lb: Running handlers complete
==> legacy_lb:
==> legacy_lb: [2016-07-16T21:18:26+00:00] ERROR: Exception handlers complete
==> legacy_lb: Chef Client failed. 0 resources updated in 11 seconds
==> legacy_lb: [2016-07-16T21:18:26+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
==> legacy_lb: [2016-07-16T21:18:26+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
==> legacy_lb: [2016-07-16T21:18:26+00:00] ERROR: /var/chef/cache/cookbooks/legacy_nginx/recipes/default.rb:41: syntax error, unexpected tSTRING_BEG, expecting keyword_do or '{' or '('
==> legacy_lb:   env-file "/opt/legacy/dynamic-loadbalancer/env.json"
==> legacy_lb:             ^
==> legacy_lb: [2016-07-16T21:18:26+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

env-file support was lost when the project structure was reorganized. You can you env that until someone makes a PR. It is an unordered array.
docker_container 'env' do
  repo 'debian'
  env ['PATH=/usr/bin', 'FOO=bar']
  command 'env'
  action :run_if_missing
end

I figured something like that happened. thanks @gmreburn
I did work around this by creating an array and then using this array with env attribute.


Compiler failures don't write to STDERR

crystal version
Crystal 0.22.0 [3c71228] (2017-04-20) LLVM 3.5.0

Example bad code:
ARGF.each

Build:
crystal build doesnt_compile.cr

STDOUT:
Error in doesnt_compile.cr:1: undefined method 'each' for IO::ARGF

ARGF.each
     ^~~~

Rerun with --error-trace to show a complete error trace.

STDERR is empty.
Exit status is 1
Same results with added flag --error-trace

I think this is fixed in master. Reopen if not (after the next release).


Real Streaming

Hi!
I was wandering if the streaming functionality isn't actually real streaming but rather an animation, because the completions take quite a while to start.
If this is the case then maybe we can implement real streaming of the responses?
I found a working example with typescript here:
https://github.com/whichlight/chatgpt-api-streaming

I'd be happy to help btw :)

Hi @lukemt, good idea, I'm not sure if it will work in Obsidian but I'll look into it. Thanks for the resource!

Yeah let's hope this works. I found the example after failing to get davinci and gpt-4 to code the thing. Somehow Bing did find this zero star repo

Fixed by https://github.com/bramses/chatgpt-md/releases/tag/1.2.0 ! Check it out!


vscode-icons extension not enabled in remote windows on trusted folders

They work in a non remote instance

Reproduced with the TestResolver:

install vscode-icons-team.vscode-icons extension
verify it works in a local window on a trusted folder
open a new test resolver window
open a trusted remote folder
open the extensions view:  the vscode-icons-team.vscode-icons extension is grayed out in the extensions view, no explanation why, no button to install in remote

Set security.workspace.trust.enabled": false

open the test resolver window again on the same folder, now the extension is enabled

The vscode-icons extension is a UI extension: https://github.com/vscode-icons/vscode-icons/blob/c7a9e3c69a2af799d9ba8693819794718e194956/package.json#L127
It hasn't changed since April.

Friendly ping since this is pretty annoying for me :-)

@dbaeumer sorry about that. I will try to get to this tonight as I am investigating another issue related to workspace trust.

@dbaeumer, until I investigate the root cause of the issue, you can add the following to your user settings as a workaround:
  "extensions.supportUntrustedWorkspaces": {
    "vscode-icons-team.vscode-icons": {
      "supported": true
    },
  }

@lszomoru thanks!

@dbaeumer, the underlying bug has been fixed, so you can remove the entry from your user settings.


[preprocess-auto-slug] Unit Tests

Implement testing for preprocess-auto-slug, simple input source code vs processed output?

merged to #222

merged to #222


type for geoshape set to 'error'

Am seeing:
<input autocomplete="off" type="error" name="/geo/geotype/shape" data-type-xml="geoshape" style="display: none;">

Is this still happening for you?  Doesn't seem to be an issue for me.
Out of interest, what's the benefit of the error type?  For our use we set unknown types as text: https://github.com/alxndrsn/enketo-client-side-transformer/blob/master/xslt/client-side/openrosa2html5form.xsl#L1374
Apart from anything else, some of our CSS expects input[type=text] :)

No, I think this was fixed.
The only benefit to setting this as error is to have some feedback (could do a check after transformation or output the xslt warnings) in case a XForm has a spelling mistake in the type. But considering unknown types should be treated as text I don't have strong feelings about this (nor is it being used).


Better example to SocketHandler

Monolog version 1|2|3?
2. (in Laravel)
I can't make SocketHandler work at all.
Using the example throws an error the sock doesn't exist.
I guess in this case it is supposed to create the stream and post the logs there.
I tried to create a socket but it doesn't work with SocketHandler.
Could somebody give me a 100% working example code both for the server and client side? I would really appreciate that.

Could somebody give me a 100% working example code both for the server and client side? I would really appreciate that.

Why the client side? Monolog is working only on the server.


TypeError: tslib_1.__spreadArray is not a function with msal 1.4.16

Core Library
MSAL.js v1 (@azure/msal or msal)
Core Library Version
1.4.16
Wrapper Library
Not Applicable
Wrapper Library Version
None
Description
msal 1.4.16 uses tslib ^1.9.3, but TelemetryManger.ts uses __spreadArray that is only available in tslib ^2.1.0
I have tried adding an upgraded version of tslib to my build but it does not resolve the issue. Deleting node_modules and jspm_packages and reinstalling also does not resolve the issue.
msal 1.4.16 and msal 1.4.12
tslib 1.14.1
Typescript 3.83 and Typescript 3.9.2
Is my only option to upgrade to msal 2.x (and all the work that entails) or is there another solution?
Error Message
TypeError: tslib_1.__spreadArray is not a function
at new ServerRequestParameters (\wwwroot\jspm_packages\npm\msal@1.4.16\src\serverrequestparameters.ts:63:31)
at UserAgentApplication.eval (\wwwroot\jspm_packages\npm\msal@1.4.16\src\useragentapplication.ts:743:49)
at step (\wwwroot\jspm_packages\npm\tslib@1.14.1\tslib.js:143:28)
at Object.eval [as next] (\wwwroot\jspm_packages\npm\tslib@1.14.1\tslib.js:124:58)
at eval (\wwwroot\jspm_packages\npm\tslib@1.14.1\tslib.js:117:76)
at new Promise ()
at Object.__awaiter (\wwwroot\jspm_packages\npm\tslib@1.14.1\tslib.js:113:17)
at eval (\wwwroot\jspm_packages\npm\msal@1.4.16\src\useragentapplication.ts:710:64)
at new Promise ()
at UserAgentApplication.acquireTokenSilent (\wwwroot\jspm_packages\npm\msal@1.4.16\src\useragentapplication.ts:710:16)
Msal Logs
No response
MSAL Configuration
N/A

Relevant Code Snippets
N/A

Reproduction Steps
N/A
Expected Behavior
N/A
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
Other
Regression
No response
Source
External (Customer)

@tsulli Unfortunately, msal 1.x is only receiving critical security fixes at this point. Unless you are able to use an upgraded version of tslib, our recommendation would be to use the @azure/msal-browser library instead.

Thanks. We had upgrading to msal 2.x in the backlog and this pushed it straight to the top of the queue. I managed to get everything upgraded and mostly working now.


Partial Payment

Add option by payment reference to allow user to record a partial payment, then update the amount due with the total minus the partial payment

Looks good, if the child table is there we can remove the payment reference section on the bottom right


Add formula for RubyMine EAP with bundled JDK

Anything else I can do to get this merged?

@sebroeder Hi Sebastian, sorry for the delay here.
Merging now...


fix: adjust typing

chore: remove unnecessary shebang in python files
chore: update ruff settings
chore(deps): add pyright dev-dependency
chore(deps): update ruff dev-dependency
ci(pre-commit): update poetry-check hook args
fix: adjust typing
fix(deps): update dependency firebirdsql to ^1.2.3
test: add test_reuse_connection

PR Analysis

🎯 Main theme: This PR mainly focuses on adjusting the typing in the code, updating dependencies, and adding a new test case.
📝 PR summary: The PR introduces several changes including the removal of unnecessary shebangs in python files, updating dependencies, adjusting typing in the code, and adding a new test case. It also makes the 'db' parameter optional in the 'execute' and 'callproc' functions.
📌 Type of PR: Enhancement
🧪 Relevant tests added: Yes
⏱ Estimated effort to review [1-5]: 3, because the PR includes changes in multiple files and introduces a new test case. However, the changes are straightforward and do not involve complex logic.
🔒 Security concerns: No security concerns found

PR Feedback
💡 General suggestions: The PR is well-structured and includes meaningful changes. It is recommended to keep the scope of a PR limited to make it easier to review. In this case, the PR could have been split into multiple smaller PRs, each focusing on one aspect (e.g., updating dependencies, adjusting typing, adding tests).
 🤖 Code feedback:relevant filesrc/firebirdsql_run/main.pysuggestion
Consider adding a check to ensure that the 'db' parameter is not an empty string when it is used. This can prevent potential issues when trying to connect to the database. [important]
relevant linedb: Path | str = "",relevant filesrc/firebirdsql_run/main.pysuggestion
It's good practice to close the connection even if an error occurs. Consider using a context manager (with statement) to ensure the connection is always closed properly. [medium]
relevant lineconn: Connection | None = Nonerelevant filetests/test_firebirdsql_run.pysuggestion
It's recommended to add assertions to check the type of 'result.data' to ensure it's a list. This can help catch issues if the function implementation changes in the future. [medium]
relevant lineassert len(result.data) > 0relevant filepyproject.tomlsuggestion
It's recommended to lock the versions of the dependencies to ensure consistent behavior across different environments. [medium]
relevant linefirebirdsql = "^1.2.3"

 ✨ Usage guide:
Overview:
The review tool scans the PR code changes, and generates a PR review. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.
When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:
/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

With a configuration file, use the following template:
[pr_reviewer]
some_config1=...
some_config2=...

  Utilizing extra instructions
The review tool can be configured with extra instructions, which can be used to guide the model to a feedback tailored to the needs of your project.
Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify the relevant sub-tool, and the relevant aspects of the PR that you want to emphasize.
Examples for extra instructions:
[pr_reviewer] # /review #
extra_instructions="""
In the 'general suggestions' section, emphasize the following:
- Does the code logic cover relevant edge cases?
- Is the code logic clear and easy to understand?
- Is the code logic efficient?
...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

  How to enable\disable automation

When you first install PR-Agent app, the default mode for the review tool is:

pr_commands = ["/review", ...]

meaning the review tool will run automatically on every PR, with the default configuration.
Edit this field to enable/disable the tool, or to change the used configurations

  Auto-labels
The review tool can auto-generate two specific types of labels for a PR:

a possible security issue label, that detects possible security issues (enable_review_labels_security flag)
a Review effort [1-5]: x label, where x is the estimated effort to review the PR (enable_review_labels_effort flag)

  Extra sub-tools
The review tool provides a collection of possible feedbacks about a PR.
It is recommended to review the possible options, and choose the ones relevant for your use case.
Some of the feature that are disabled by default are quite useful, and should be considered for enabling. For example:
require_score_review, require_soc2_ticket, and more.

  More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

/review: Request a review of your Pull Request.
/describe: Update the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
/ask <QUESTION>: Ask a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.
/add_docs 💎: Generate docstring for new components introduced in the PR.
/generate_labels 💎: Generate labels for the PR based on the PR's contents.
/analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

See the review usage page for a comprehensive guide on using this tool.

Persistent review updated to latest commit https://github.com/DeadNews/firebirdsql-run/commit/65e2c7a77b87707cebf1868070064c04f83da2cf


ssm doc only applies to us-east-1

am switching between us-east-1 and 2 and noticed that ssm doc only applies to region where cfn stack is deployed. Would be nice to have consistent experience across regions from the single manager pane

No plan to fix


Issue about the users

Is there a case where a user is both an instructor and a student?

No, for simplicity.


New Function in Codeunit 7000 & 7010

Hi,
we need a new external function in Codeunits 7000 and 7010.
With that function it should be able to set variables used in the codeunit.
Without that function the external function "FindSalesPrice" and "FindPurchPrice" cannot be used, as Currency, vat and UoM are not set.
The function could/should look like this:
[External] M365_SetVariabel(itemNoL : Code[20];currencyCodeL : Code[10];currencyfactorL : Decimal;currencyDateL : Date;qtyL : Decimal;qtyPerUoML : Decimal) Item.GET(itemNoL); SetCurrency(currencyCodeL,currencyfactorL,currencyDateL); SetVAT(FALSE,0,0,''); SetUoM(ABS(qtyL),qtyPerUoML);
Parameters are:
itemNoL : Code[20];
currencyCodeL : Code[10];
currencyfactorL : Decimal;
currencyDateL : Date;
qtyL : Decimal;
qtyPerUoML : Decimal
thanks

Hi Lennart. Short question about new function you ask. There are events OnBeforeFindSales(Purch)Price and there are all required parameters with var. Why can't you use it to get what you want?

Hi,
The problem with that solution ist, that the variables i used when calling FindSalesPrice will not be available in the subscriber...

Not sure I fully understand you. Below is part of FindSalesPrice with call of event, which variables are not available in the subscriber?
[External] FindSalesPrice(...)
...
OnBeforeFindSalesPrice(
ToSalesPrice,FromSalesPrice,QtyPerUOM,Qty,CustNo,ContNo,CustPriceGrCode,CampaignNo,
ItemNo,VariantCode,UOM,CurrencyCode,StartingDate,ShowAll);

Hi,
lets say i have an action on a page, where i got a qty saved in a local variable. Then i want to use that qty in the FindSalesPrice. So i call the FindsalesPrice. The event is triggerd and i have to create a subscriber. In that new subscriber i dont have access to the local qty variable. Thats my problem :)

Ok, now it more or less clear.
Let me suggest you the following solution. You have a subscriber codeunit with a function subscribed on the "OnBeforeFindSalesPrice". You need to pass a parameter there. Then you need one more event OnSomeAction, your own and one more subscriber function. This subscriber function should be in the same codeunit as the subscriber on the "OnBeforeFindSalesPrice" one. Then in the place where you are going to call FindSalesPrice function and where you know the value of your parameter, you need manually (BINDSUBSCRIPTION) subscribe your codeunit, call the "OnSomeAction" event, pass your parameter there. And in the subscriber function in your codeunit set a global variable with the value of parameter from event. Then when subscriber function for OnBeforeFindSalesPrice will be called, you can read the global variable set before and pass it further in the event.
Does it look like a working schema for you?

Hi,
This doesnt look like a working schema for us. If we would do it like you suggest, the subscriber would be called every time the FindSales(Purch)Price would be used. That wouldnt work, becouse in the subscriber we cannot see, where we originaly came from. Additionally, if we use the pubisher, only the local variables in the function will be set. By Using out suggested function, we would be able to set the global variables, wich would be important for us.

Hi.
I still suggest to observe suggestion one more time.
The first thing is that you can make manual subscription and then subscriber will not be called any time, only when you do BINDSUBSCRIPTION. According to my suggestion you can also pass parameter to subscriber codeunit (for example) by setting a global variable in it and then reading it in other subscriber function. Or in extreme case you can use single instance codeunit to read/write variables.
The second thing there are local functions that sets VAT, UoM, Currency, I plan to make them global.

HI, i hope if you say you are making them global means external aswell?
Will it be possible to set the Global Item?


Java Toolchains reporting fixes

Fixes #15918
Fixes #16140

@bot-gradle test QFL

OK, I've already triggered the following builds for you:

QuickFeedbackLinux build

@bot-gradle test and merge