Better describe the update status / better logging

I was happy with the legacy Surface Dock Updater. You start an exe, you see progress. Logging is done in Event Log. I totally don't understand the new Updater. Please don't take this as a rant, but from a user that actually wants to update the dock and fails due to lack of documentation and progress bars. So here are my concerns:
Under "To Run Surface Dock Firmware Update" it says:
2. After you connect Surface Dock to your Surface device, the tool checks the firmware status while running in the background
Please document how I can check that the software is doing the checking. "While running in the background" means that a new Windows Service is installed that is running in the background? When I use the msi logging command documented further below - is that how I can check if it's doing its job? The event log seems to be deprecated.
3. After several seconds, disconnect your Surface Dock from your device and then wait for 5 seconds before reconnecting. The Surface Dock Firmware Update will normally update the dock silently in background after you disconnect from the dock and reconnect. The process can take a few minutes to complete and will continue even if interrupted.
"After several seconds". What does that mean? How do I know it is finished? There is no progress bar or anything. Same goes for "a few minutes to complete" - how do I know it is complete? I guess the flashing LED in the ethernet port? Is there a signal like multiple flashes? No flashes?
Heading "Manual installation"
I am supposed to reconnect "for 2 minutes". Do I need to time this? Why 2 minutes? Is there some progress bar somewhere I can check that whatever did it's thing?
Heading "Event logging"
Since the current version doesn't log to the event log, shouldn't the heading be "logging"?
Why are the event log IDs documented here if only relevant for the legacy versions? I suggest removing everything legacy, and putting that under a "Legacy" heading.
I currently have Component10CurrentFwVersion = 4a26d70, Component20CurrentFwVersion=4a1d570. Display port version looks good, MCU seems "different". Now I have no clue what to do and the documentation doesn't help. I'll do some more of the troubleshooting: Uninstalling the update and randomly unplugging/pluggin back in the dock, but that doesn't seem like a smart process. (Actually it is the same in this unanswered comment)
I would love a step-by-step documentation. First do this, than that. All the IT-Pro stuff (network deployment & Intune) needs to be way lower since that won't be the primary use case. I can gladly help improving the documentation with a pull request but right now I don't actually understand the process that needs to happen.

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

ID: 2a7b356e-3dbd-7f59-845e-a92e05865a52
Version Independent ID: 711c5497-373f-662c-7fae-ba60f046e50c
Content: Microsoft Surface Dock Firmware Update
Content Source: devices/surface/surface-dock-firmware-update.md
Product: w10
Technology: windows
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@officedocsbot assign @jvsam

Hello @DennisGaida, thank you for taking the time to share your feedback, we appreciate it. There are multiple suggestions to this doc that are currently in review. Some of them might address your issues. You can see on #5046 several linked issues and PRs.

I can gladly help improving the documentation with a pull request...

That would be great! I would suggest monitoring the status of the open issues and hopefully once the proposed amendments are approved and merged, the documentation will be easy to understand. From there, you can help by submitting pull requests with your suggestions. Here's the Microsoft Docs contributor guide for reference.
I also encourage you to submit your feedback on UserVoice. Your feedback goes directly to the Microsoft product team and they would love to hear what you think. If there's already a request or suggestion similar to yours, you can add your vote to the request. Thank you.

Agree completely. While this is great for large organizations to potentially push updates remotely, this shouldn't be the default option for everyone. The previous firmware updater made it very clear you can't remove the dock from your PC at certain points, either that was misleading or we are now all in a situation where we might destroy our docks because we disconnect at the wrong time.

@jvsam Thanks for reply! I can't help improving the documentation since, the process isn't clear right now. As you can tell there are multiple issues with the documentation and your linked issue #5046 does not address them. I did file feedback via the Windows Feedback Hub, but you say there is a UserVoice? You link to feedback hub.
Please help improve the documentation and forward this to the surface hub product team.

I did file feedback via the Windows Feedback Hub, but you say there is a UserVoice? You link to feedback hub.

Great and yes, they're the same. Thank you for submitting your feedback. Also, have you tried collaborating with the community? There is a dedicated Microsoft Tech Community for Surface devices. It's the best place to post your questions, if you have any, and to get help from the experts or other community users. For one, you can engage with them on this ongoing discussion. And if there is any relevant information that can be incorporated into this documentation, please let us know or if you are ready, start contributing to make this doc better. Hope this helps.

Hi again @DennisGaida, since there are no requests for content updates/changes, we will close this issue for now. Feel free to reopen if you have feedback or suggestions to help improve the quality of this technical documentation. Thanks for being part of the Microsoft Docs community!

@officedocsbot close

since there are no requests for content updates/changes

The initial issue is exactly about this. Requests for content changes. You did not reply to these requests, but in all requests referred to external sources such as feedback hub, tech community etc. The documentation itself was not touched, but should be updated as per the initial request.

@jvsam : Would it be possible to get a comment from the document owner or someone from the Microsoft Surface Dock Firmware team?

@DennisGaida I have exactly the same issue with the same version numbers as you.  The documentation says that the Component10CurrentFwVersion should be updated to 4ac3970 but has remained at 4a26d70. My situation has got worse recently, after a windows update, the dock no longer detects the external monitor.
Please can the document owner improve the instructions so that it is clear when to connect/ disconnect the dock in relation to running the software.  E.g at the start, do we install the firmware upgrade with or without the dock connected?  I've tried every combination and nothing seems to make any difference.

@DennisGaida - As requested, reopening this issue to get more clarity in improving this doc.
Let me loop in the doc owner to get his insights on this issue.
@Dansimp - Can you please share your insights on this issue? Or is there a way that we can engage the Product Engineering team to help clarify the feedback?
Thank you.
cc: @kenwith

@mypil, after more restarts, the firmware is now showing the correct version and detects the external monitor. I am happy for you to close the issue.

@MJBu : Thank you for the feedback. You seem to have a particularly slow responding Surface Dock & computer combination, but it is good to hear that you were able to resolve the situation.
Not quite certain who is deeply invested in this issue ticket now, so I will ask Dennis.
@DennisGaida : What is the status of this ticket from your viewpoint? Close it or continue to keep it open?

@illfated Technically I got my Suface Dock to update by leveraging several restarts and updating multiple times.
The issues with the documentation remain the same as per original post.

The new and old version of the dock updater are intermingled in the doc (e.g. event log location for the old/new version).
Network & Intune Deployment seem out of place, since non-commercial users wouldn't particularly know what this is.
The lack of visual progress in the new dock updater is very frustrating and the documentation doesn't explain where progress is actually shown, besides "it takes a few minutes"
Manual installation doesn't explain what to do besides "reconnect your dock" - I suppose one should install the MSI before reconnecting the dock - otherwise reconnecting the dock wouldn't do anything? Maybe manual installation replaces step 2&3 of the installation process? Nobody knows.

If you are happy with the documentation, please close the issue. I, as a user, am not and I do read a lot of Microsoft documentation,

(ref. #5832 )

@DennisGaida @illfated - Thank you for providing more details on how we can improve and for linking the related issues for this topic.
@Dansimp - Can we get the Product Engineering team involved in this issue?
This is so they can shed light on the best approach to address the mentioned concerns for this topic.
Thank you.

I was hoping that I could update this topic by deciphering the instructions myself, but I'm not having much luck. If I can get a reply from the product team at least I should be able to test what they tell me.

See https://github.com/MicrosoftDocs/windows-itpro-docs/issues/5756 for an update. I'm going to use that issue as the main one and close this one.


Mutate empty Tier set in Antrea-native policies to default tier

Fixes: #1550

Codecov Report

Merging #1567 (ea6dd82) into master (9d3d10b) will decrease coverage by 22.69%.
The diff coverage is 10.49%.

@@             Coverage Diff             @@
##           master    #1567       +/-   ##
===========================================
- Coverage   63.31%   40.62%   -22.70%
===========================================
  Files         170      106       -64
  Lines       14250    12752     -1498
===========================================
- Hits         9023     5181     -3842
- Misses       4292     7101     +2809
+ Partials      935      470      -465

Flag
Coverage Δ

kind-e2e-tests
?

unit-tests
40.62% <10.49%> (-0.65%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.


Read images

Allow image file reading including metadata

This could be based on the unpack images section of this tool
https://github.com/cry-inc/e57/blob/master/tools/e57-unpack/src/main.rs
Outputting to a numpy array would be a nice option without additional dependencies. It would be good if the output format was fairly easy to use with open cv or similar python image processing libraries as people might want to do image processing on the photos with the pointcloud

My experience of images in e57 files is the panoramic photos from individual scan stations - A single e57 file contains multiple scans each taken from a single position, a scan station.  Each scan may also be associated with 6 images forming a cube around the scanner position. It would therefore be useful to be able to get the 6 images (is it always 6?) for each scan station and to associate them with the points from the same station.


Suggestion: fade current song when it ends or changes

It currently is kind of jarring when a song changes as it simply cuts off instantly, I suggest making the currently played track fade when it gets changed for a new track, be that another custom one or a vanilla.
Otherwise amazing plugin,  thanks for you work!

Fading is a bit more involved than I would've hoped so I'm not sure when/if I'll have it added but I'll definitely try.
I'll also focus on only a fade-out since that's how I interpret "making the currently played track fade" and afaict that's how the osrs music behaves.


Fix for #2638 - Youtube nocookie option doesn't change iframe src

This micro PR is a fix for issue #2638.
Fixes #2638
For the host parameter:

https://www.sitepoint.com/community/t/using-nocookie-youtube-api-is-this-valid/307018
https://portalzine.de/dev/api/youtube-iframe-api-and-cookieless-domain-solution-gdpr-dsgvo/

(Sadly the official documentation is silent about this param, but it actually works)
To test this, add the nocookie parameter to the player options.
        const player = new MediaElementPlayer('me-video', {
           ...
            youtube: {
                nocookie: 1,
            },
        });

Coverage remained the same at 74.376% when pulling f1925de787378eb0f333629094a508f1c45aa029 on gergely-ujvari:2638-fix-iframe-nocookie into f47895f50adb2155fd8a25333c7dfddb76c155e7 on mediaelement:master.

Also fixes #2674


Mention convertContent in readme and increase version

Update readme and increased version so that it can be published including the unpublished previous PRs.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #21   +/-   ##
=======================================
  Coverage   91.11%   91.11%
=======================================
  Files           1        1
  Lines          45       45
  Branches        2        2
=======================================
  Hits           41       41
  Misses          4        4

Continue to review full report at Codecov.

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

👍

:+1:


boundary issues when rendering a DisplayObject to a RenderTexture

Preface - I have only tried this with v3.0.0-rc2 but this is probably a general issue.
Description - When the size of a DisplayObject that is being rendered to a RenderTexture is being changed, the boundaries are not updated accordingly. This is because the RenderTexture updates the boundaries according to the children of the passed DisplayObject, which however has none (see [1]).
Suggestion - This can be fixed by any user by embedding the DisplayObject into a Container and rendering the Container instead. It should however be fixed internally by introducing a check within the renderWebGL function.
[1] https://github.com/GoodBoyDigital/pixi.js/blob/dev/src/core/textures/RenderTexture.js#L271

Does this issue still happen on the latest v3 release?

Does seem to work now, thank you!
The referenced pull request however does not seem to be the one that solved the problem though. I assume that @GoodBoyDigital solved this issue, so I would highly appreciate it if he would leave a quick comment and reference the commit that solved this issue.


Remove Falco from website

This page is dual hosted 3rd party content.

/lgtm

/hold
per https://kubernetes.io/blog/2020/05/third-party-dual-sourced-content/

@tengqm happy to rebase this? I think we could unhold it given the v1.19 docs deadline has passed.

/lgtm
/hold cancel

/approve


Add support for MariadDB;

Fixes #2705
Changes proposed in this pull request:

Pull Request Test Coverage Report for Build 8834

17 of 28 (60.71%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.003%) to 62.229%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/core/spi/database/MariaDBDatabaseType.java
2
4
50.0%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/core/metadata/datasource/dialect/MariaDBDataSourceMetaData.java
0
9
0.0%

Totals

Change from base Build 8833:
-0.003%

Covered Lines:
8564

Relevant Lines:
13762

💛  - Coveralls

Wonderful pr, thank you.

Can one of the admins verify this patch?


Helm 2.4.0 seems to ignore my kubeconfig

Despite kubectl working, helm seems to not be actually using the kubeconfig file. Every command results in, roughly:
Error: Get http://localhost:8080/api/v1/namespaces/kube-system/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused

I can even see with strace that it opens and reads the kubeconfig and then connects to localhost:8080.
When I downgraded to 2.3.1 this went away.

I meet this problem too.

Same problem here :/

same here.

same problem for me

same problem

Dupe of #2376?

yes duplicate

Closing since dupe of #2376.

On second thought, given the number of thumbs up, maybe we should leave this open until 2.4.1 is available.

2.4.1 is released

same problem, and please never say "Dupe' , because my version is the latest: 2.8.2.

@kinderyj could you please open a new ticket? If you're seeing this on v2.8.2 then it's something we should tackle separately. Thanks!


(NoMethodError) on Private Registry

Describe the bug
I got this error when my dependabot try to create PR for private Nuget package in Azure Devops.
2024/10/22 08:40:23 INFO <job_1729586364> Checking if AAA.Common.Http 2.0.1 needs updating
🌍 --> GET https://xxx.pkgs.visualstudio.com/aaa/_packaging/private-feed/nuget/v3/index.json
🌍 <-- 200 https://xxx.pkgs.visualstudio.com/aaa/_packaging/private-feed/nuget/v3/index.json
🌍 --> GET https://xxx.pkgs.visualstudio.com/744cec9e-c94a-41aa-a3a1-ed866b65b436/_packaging/d7ac292f-e20f-4e34-918f-5406eb9364ee/nuget/v3/registrations2/AAA.Common.Http/index.json
🌍 <-- 200 https://xxx.pkgs.visualstudio.com/744cec9e-c94a-41aa-a3a1-ed866b65b436/_packaging/d7ac292f-e20f-4e34-918f-5406eb9364ee/nuget/v3/registrations2/AAA.Common.Http/index.json
🌍 --> GET https://api.nuget.org/v3/registration5-gz-semver2/AAA.Common.Http/index.json
🌍 <-- 404 https://api.nuget.org/v3/registration5-gz-semver2/AAA.Common.Http/index.json
🌍 --> GET https://api.nuget.org/v3-flatcontainer/AAA.Common.Http/2.0.1/AAA.Common.Http.nuspec
🌍 <-- 404 https://api.nuget.org/v3-flatcontainer/AAA.Common.Http/2.0.1/AAA.Common.Http.nuspec
2024/10/22 08:40:24 INFO <job_1729586364> Latest version is 2.0.2
2024/10/22 08:40:24 ERROR <job_1729586364> Error processing AAA.Common.Http (NoMethodError)
2024/10/22 08:40:24 ERROR <job_1729586364> undefined method contains_dependency?' for an instance of Array 2024/10/22 08:40:24 ERROR <job_1729586364> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:255:in block in pr_exists_for_latest_version?'
2024/10/22 08:40:24 ERROR <job_1729586364> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:255:in any?' 2024/10/22 08:40:24 ERROR <job_1729586364> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:255:in pr_exists_for_latest_version?'
my dependabot.yaml
version: 2
registries:
  artifacts:
    type: nuget-feed
    key: "private-feed"
    url: "https://xxx.pkgs.visualstudio.com/aaa/_packaging/private-feed/nuget/v3/index.json"
    token: PAT:${{ AZURE_ACCESS_TOKEN }}
updates:
  - package-ecosystem: "nuget"
    directories: [ '/xxx/YYY/*' ]
    allow:
      - dependency-name: "AAA.Common.Http"
    target-branch: main
    registries:
      - artifacts
    schedule:
      interval: "daily"
    commit-message:
      prefix: "private repo upgrade"
    open-pull-requests-limit: 5

Additional context
I found something similar on internet https://github.com/dependabot/dependabot-core/issues/8003 However it is for group but I only need to use allow. Any idea how can I pass this error?

@caglanurcetinn thanks for the report.
It looks like you are using version 1 of the task; can you let us know which version of the dockerImageTag you have set in your pipeline?
Briefly looking at the stack trace, it looks like the Dependabot metadata stored one of your existing active pull requests is causing problems. It is possible you might be work around this issue by completing/abandoning any other [active] Dependabot PRs that are currently open.
If you are able to confirm which Docker image tag you are using, I will investigate further.

Thanks for the quick response. It worked when I closed the other open PR. The open PR was related with a different package. Basically, I would expect it to create 2 different PRs as they are not related with same package.
My pipeline is;
pool:
  vmImage: 'ubuntu-latest'

stages:
  - stage: CheckDependencies
    jobs:
      - job: Dependabot
        displayName: 'Run Dependabot'
        steps:
          - task: dependabot@1
            displayName: 'Detect Outdated Nuget Packages and Create PRs'
            inputs:
              useUpdateScriptvNext: true
            env:
              AZURE_ACCESS_TOKEN: $(System.AccessToken)

I could not find the dockerImageTag. How can I find it? And you said I use version1 in task, when I try to use task: dependabot@2, it didnt work. Thanks for help!

The open PR was related with a different package. Basically, I would expect it to create 2 different PRs as they are not related with same package.

Could you elaborate on this? What was the branch names of the two pull requests that were causing the issue?

I could not find the dockerImageTag. How can I find it?

Sorry, I just assumed you had explicitly set it; Based on your pipeline config, looks like you are using the default value, "latest".

when I try to use task: dependabot@2, it didnt work.

No problem, it is still in preview and does still have issues. If it isn't an already known issue, opening a new issue would be appreciated so that I can investigate it.

Sure, I will open another issue for dependabot@2. Thanks!

Could you elaborate on this? What was the branch names of the two pull requests that were causing the issue?

First one --> dependabot/nuget/xxx/YYY/AAA.{facadeName}.BBB/main/Microsoft.NET.Test.Sdk-17.11.1
Second one --> dependabot/nuget/xxx/YYY/AAA.{name}.Producer/main/AAA.Common.Http-2.0.2
After I closed first one, It worked.

I updated Task to version 2 and it worked fine. I dont know why it didnt work at the beginning but now version 2 works for me. Thanks for all the help!


Bone joint Coordinate

Hi Carla team,
From what I know, we can extract the pedestrian coordinate through the coordinate of their static mesh, but can we further extract the coordinate or data of their bone joint or specific arms/legs?
Thank you.

Thank you for the response. When exploring around I tried to modify a pedestrian mesh blueprint and I manage to print out some part of the information on the screen/UE4 log. Do you have any suggestion so that I can print out them on a different text file and print in on every single frame like the coordination from client_example.py code?
Thank you

Hi @Nozomeiste, I am also working on same problem, getting bone joints of pedestrians. Can you please let me know how you managed to get joints in Unreal editor as well as in PythonAPI.
Thanks.

Hi @Nozomeister and @TheNihilisticRobot
I also want to add some animation in the pedestrian. Can you please let me know how you managed to get joints and which blueprint file are you referring to here?

is there an update on this problem, I would like to get the bone joints coordinate from a walker


Add CPPFLAGS in with_standard_compiler_flags

Fixes #415.
Also removed a redundant line in the same function (CXXFLAGS was being set to a value that would be ignored down the road).

Quick note: this doesn't appear to be entirely without consequences. Specifically, ncurses build from opscode/omnibus-software fails to build, most likely because the wrong header file is getting included due to the double build step.
Removing CPPFLAGS from the env does fix the issue in that case.

not sure what to do about that.  unclear on how CPPFLAGS incurs a "double build step".   a gist of all the output might help.

It's the actual software configuration that builds twice (with two different configurations): https://github.com/opscode/omnibus-software/blob/master/config/software/ncurses.rb
If CPPFLAGS is set, then it looks like ncurses ends up picking up its own headers (and this seems to cause conflict).
CPPFLAGS was not a problem for any other software recipe I built (~60 included in my project).
Cheers,

Well I'd be okay with a patch to include it by default with another patch to unset it in the ncurses definition -- that seems like it would give better default coverage.  @schisamo ?

@lamont-granquist agreed. @krallin please open a PR in omnibus-software to properly fix the ncurses software definition.

@schisamo , @lamont-granquist ,
Finally done here: https://github.com/chef/omnibus-software/pull/359 — sorry for the delay, I was buried under work lately!
Cheers,

Thx @krallin. This was merged as ee3038aba0b24ced578279e8961840217a53f883 and 16f4084ae11d79a309aee3efd0acf6b65f7f76b6.

Nice, thanks @schisamo !


[V2] Reinstate pwa-kit-build Test(s)

Description

A test was commented out to get the v2 branch in a "green" state. This PR re-adds this test, and fixes it.
Types of Changes

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Documentation update
[ ] Breaking change (could cause existing functionality to not work as expected)
[ ] Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

Removing a public function or component or prop
Adding a required argument to a function
Changing the data type of a function parameter or return value
Adding a new peer dependency to package.json

Changes

(change1)

How to Test-Drive This PR

(step1)

Checklists

General

[ ] Changes are covered by test cases
[ ] CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance
You must check off all items in one of the follow two lists:

[ ] There are no changes to UI

or...

[ ] Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
[ ] Changes comply with WCAG 2.0 guidelines levels A and AA
[ ] Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

[ ] Changes include a UI text update in the Retail React App (which requires translation)

@bendvc I've gone ahead and applied the fix from #493 into this PR.

@olibrook @kevinxh the changes fro PR #493 to fix the failing test in pwa-kit-build by importing regenerator-runtime to packages/internal-lib-build/configs/jest/setup-jest.js is ready.
And the CircleCI test are passing as well
Could I get a +1 from you?

@adamraya I'm not quite sure why regenerator-runtime is already in the package-lock.json of pwa-kit-build / pwa-kit-cli but not in package.json. Perhaps it got pulled in transitively by some of the other babel packages?


Is this still supporting?

Hi!
Based on the number of open issues and pull requests, I'm wondering if you are still maintaining this project.
Thanks,

@willian I decided to use UpminAdmin for a long term project of mine. @joncalhoun gave me baby sitting rights and I'll do my best to support and contribute as my project now depends on it.
I'll dig more into this in the upcoming weeks.

Thanks for the answer @jdurand.
I need to install an Admin for my client. I have used ActiveAdmin a lot, then I found UpminAdmin. But I don't have time now to learn it or to understand all the main differences between the both systems.
Could you tell me what does UpminAdmin does or doesn't comparing to ActiveAdmin?
Best,

UpminAdmin is lighter.
I've used ActiveAdmin a lot. The main reasons why I decided to invest time in UpminAdmin :

AA is a DSL (based on Arbre) where UA is model decorators and drop-in view partials (haml, erb, whatever really)
AA gives you more out of the box, but UA customization is more flexible
If you really want to customize AA you'll either push it's DSL to the limits (and see your forms disappear for some reason) or resort to use custom templates which I think defeats the purpose of using AA in the first place.

One gotcha: UA does not react well to having models prefixed with admin (i.e. admin_user)
Try it out and make a list of pain points. I have mine. When I get my hands dirtier, I'll try go over everything.

Good to hear that someone is taking care of this nice project.
I've an open issue (142) that's pretty relevant (for many people I believe), hope to see some development soon. :)
Thanks @jdurand!

Developers site is down for a few months (((


For anyone that it's not working for.

The DLL requires ASUS System Analysis to be running for it to work.
And if you're using GHelper along with this and disabled Asus services, you can still disable all the other services while having ASUS System Analysis service still running.
Press the Windows button along with the R key and type "services.msc".

Locate the 'ASUS System Analysis'.

Right click on it, and press the 'Properties' button in the dropdown menu.
Set 'StartMethod' to 'Automatic' and press 'Ok'.
Right click on it again, and this time press "Start" to start the service.
Done!
If it doesn't work, it might be that the your device doesn't work with it unfortunately.

Tested on my A409FJ, indeed it needs System Analysis to be running to have any changes happen to the fans


Encode the project name with space

This is for encoding project name having space.
Reference: https://scan.coverity.com/projects/ohloh-ui

I have updated the PR to use percent encoding of spaces.

Coverity servers supports both + and %20.
%2F is handling only /. The action fails while submitting the build for project name with spaces. Reference - https://github.com/blackducksoftware/ohloh-ui/actions/runs/3289839743/jobs/5421872353
Verified it manually.

curl --form token=token  --form email=email   --form<EMAIL_ADDRESS>--form version="Version" --form description="Description" "https://scan.coverity.com/builds?project=Ohloh UI"
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

<title>400 Bad Request</title>

Bad Request

Your browser sent a request that this server could not understand.

<address>Apache Server at scan.coverity.com Port 80</address>

curl --form token=token  --form email=email   --form<EMAIL_ADDRESS>--form version="Version" --form description="Description" "https://scan.coverity.com/builds?project=Ohloh+UI"
Build successfully submitted.

curl --form token=token  --form email=email   --form<EMAIL_ADDRESS>--form version="Version" --form description="Description" "https://scan.coverity.com/builds?project=Ohloh%20UI"
Build successfully submitted.

once via curl --form

i looked at the code & site again and i think this is a (very) old hold over from pre-GH action days.  i deleted this usage in commit 69efeec2e8db2e30da7a0b62146411018a324d5b.  which leaves the other 3.

once as a URL query string

i've seen other services handle + as a space, so i'd believe Coverity does the same.

thanks for the fix!


mypy: 0.790 → 0.812

Motivation for this change
Upgrade mypy from 0.790 to 0.812.
Things done

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

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

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

Can we enable some debug output while compiling?
building of '/nix/store/3dixhqc2j6fcb60yyxw0n97033qy0na2-python3.7-mypy-0.812.drv' timed out after 600 seconds of silence

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

4 packages marked as broken and skipped:

bareos
pepper
samba4Full
sambaFull

1 package blacklisted:

tests.nixos-functions.nixosTest-test

90 packages built:

ceph (ceph-dev)
ceph-client
coconut (python38Packages.coconut)
errbot
fava
flexget
hydra-check (python38Packages.hydra-check)
libceph
mnemosyne
mypy (python38Packages.mypy)
nix-pin
python37Packages.WSME
python37Packages.aiokef
python37Packages.algebraic-data-types
python37Packages.bsblan
python37Packages.cheroot
python37Packages.cherrypy
python37Packages.coconut
python37Packages.hydra-check
python37Packages.ics
python37Packages.irc
python37Packages.jaraco_logging
python37Packages.mypy
python37Packages.pixelmatch
python37Packages.plugwise
python37Packages.portend
python37Packages.pyalgotrade
python37Packages.pyls-mypy
python37Packages.pylxd
python37Packages.pynamodb
python37Packages.pytest-mypy
python37Packages.tatsu
python37Packages.tempora
python37Packages.typer
python37Packages.web
python37Packages.ws4py
python37Packages.zerobin
python38Packages.WSME
python38Packages.aiokef
python38Packages.algebraic-data-types
python38Packages.bsblan
python38Packages.cheroot
python38Packages.cherrypy
python38Packages.ics
python38Packages.irc
python38Packages.jaraco_logging
python38Packages.pixelmatch
python38Packages.plugwise
python38Packages.portend
python38Packages.pyalgotrade
python38Packages.pyls-mypy
python38Packages.pylxd
python38Packages.pynamodb
python38Packages.pytest-mypy
python38Packages.tatsu
python38Packages.tempora
python38Packages.typer
python38Packages.web
python38Packages.ws4py
python38Packages.zerobin
python39Packages.aiokef
python39Packages.algebraic-data-types
python39Packages.bsblan
python39Packages.cheroot
python39Packages.cherrypy
python39Packages.coconut
python39Packages.hydra-check
python39Packages.ics
python39Packages.irc
python39Packages.jaraco_logging
python39Packages.mypy
python39Packages.pixelmatch
python39Packages.plugwise
python39Packages.portend
python39Packages.pyalgotrade
python39Packages.pylxd
python39Packages.pynamodb
python39Packages.pytest-mypy
python39Packages.tatsu
python39Packages.tempora
python39Packages.typer
python39Packages.web
python39Packages.ws4py
python39Packages.zerobin
qemu_full
sabnzbd
thonny
tribler
ulauncher
zfs-replicate


[Question] datax task not support select hive connection

Which version of DolphinScheduler:
-[1.3.6-binary]
Requirement or improvement

not support hive in datax?
I know datax itself support hive and hdfs, but when I use it in dolphinscheduler, I found that, it just support normal jdbc database , not include Hive. So why? and how to support??

Which version of DolphinScheduler:
-[1.3.6-binary]
Requirement or improvement

not support hive in datax?
I know datax itself support hive and hdfs, but when I use it in dolphinscheduler, I found that, it just support normal jdbc database , not include Hive. So why? and how to support??

no special cause, just because contributors not need to use hive. you can use custom template

if you want to implement and contribute it , please leave a message


[ADLS Gen2] Path - Lease support in storage SDK

https://docs.microsoft.com/en-us/rest/api/storageservices/datalakestoragegen2/path/lease
Current blocker:
Setting headers from Request to Http client.
Getting headers from Http client to Response.
Http pipeline support.

Scope:
Validation and Documentation API support is included.


Add getCameraPresence function

Compatibility

OS
Implemented

iOS
?

Android
✅

Windows
✅

This function was made in response to the fact that react-native-camera does not have such functionality, I will try in the future to add an implementation to Android

Hi ! Would it be possible to distinguish between front and rear camera?

@machour Yes. Some part of device have EnclosureLocation property, in which the location is indicated (Back, Bottom, Front, Left...), but this method gives an answer of whether there is at least some kind of camera at all.
Note that this is the UWP platform and it also works on static computers that can have a usb cameras, without dividing into front and rear. Also there are android devices without a camera but the ability to connect it through the usb port. We have one such.
P.S. Now I'm working on implementing the same function for android, for our project.
The presence of such a function for ios does not make sense.

Hooray! Now for Android 😊

Awesome, I'll have a look as soon as possible.
On iOS, we should return true so that developers don't have to test for the OS

https://noncam.com/ - Perhaps it's worth implementing this function for iOS  =)

https://stackoverflow.com/questions/3643949/detect-existence-of-camera-in-iphone-app

@machour What is the status of this PR? If there are problems, let me know about them

@machour If you have a lot of free time, it will be great if you look at this PR =)

Oh - when I resolved conflicts I pushed right on to your repository. You will likely need to git fetch origin && git rebase (maybe even git rebase --hard) in order to get in sync. That may or may not have broken git-etiquette for you, if so I am sorry but I am trying to help get this merged so apologies in advance :-)

This is now very stale and I haven't seen a response to my previous questions from @Hirurgo - I just invested some time resolving conflicts and I'm willing to merge this. At this point, as the project has moved forward we need an update illustrating usage for App.js (trivial to add) and an entry for the default/empty polyfill (also trivial) along with the changelog entry. All of these are simple so should not be a barrier but if there's no response I will close it without merge- we need responsive authors more than we need more code, sorry :man_shrugging: - would love to get this in though!

I'm here  =)  Now I will try to remember what I did a year ago....

@mikehardy  still actual for our project, I'll fix everything now

:-) fantastic! Let's get this thing merged. It's just what I think of as "mopping up" at this point - all the related bits that aren't the actual code. I'll re-check when you've pushed the extra bits

@mikehardy   Add entry in App.js and change log. But I don't understand what means "entry for the default/empty polyfill "

@mikehardy done

Great stuff, I'll merge this in and make a final comment when released, then if you are using this in your project you can get back to master instead of maintaining a local fork. :fireworks:
As an advance warning, we are about to do a major API shift in v2.0 but the plan is not to introduce different behavior except where strongly desired and just blocked by existing API. We will mostly just convert to promise (already implemented that way here) and package the APIs a bit. So when it happens it shouldn't be hard to migrate for you at all - hopefully useful info since you will have just moved back to master / npmjs.org releases.
Thanks!

Great stuff, I'll test this locally then merge this in, then if you are using this in your project you can get back to master instead of maintaining a local fork. As an advance warning, we are about to do a major API shift in v2.0 but the plan is not to introduce different behavior, just convert to promise and package the APIs a bit, so when it happens it shouldn't be hard to migrate at all - hopefully useful info since you will have just moved back to master / npmjs.org releases.
Thanks!

1.7.0 is out, enjoy :rocket:


Add CONTRIBUTING.md

We should add a CONTRIBUTING.md to make sure folks know that this is a living document and we want them to comment on/improve it.

To make lining documents etc and receiving cmnts


fix(dropdown): align position with or without vertical scrollbar

Fixes #5942.
Plunkr showing the fix:
http://plnkr.co/edit/jlBJjMgpDnR133ByUATF?p=preview

@dolevd your fix lacks tests and failed the eslinter which is why the build failed.  you should try and do the build locally before actually committing so you can ensure your tests pass and the build succeeds.  otherwise, you may just be wasting your time.
please correct the issues, squash your commits, and we will go from there.

@dolevd do you intend on fixing this or shall i close this?  thanks.

Sorry for the radio silence, I'll fix this patch and resubmit.


[Feature] Chat Component API Implementation

A reworked API to achieve the same result as this:
https://www.spigotmc.org/wiki/the-chat-component-api/
Needs to be friendlier than the Java impl - looks messy. Maybe a builder?

Closed & moved to Trello board.


Links to tests using Shaka Player no longer work.

Have you read the FAQ and checked for duplicate open issues?
If the problem is related to FairPlay, have you read the tutorial?

What version of Shaka Player are you using?

Shaka v4.8.4(unkompiled)
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from main?
Are you using the demo app or your own custom app?
Demo
If custom app, can you reproduce the issue using our demo app?
What browser and OS are you using?
CDM 4.10.2710.0, all Chrome browser versions, all platforms.
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
What are the manifest and license server URIs?

asset=https://storage.googleapis.com/wvtemp/hmchen/1080p24fpsVP9_hlg_hdr_cenc.mpd;
license=https://proxy.uat.widevine.com/proxy
What configuration are you using?  What is the output of player.getConfiguration()?

What did you do?

Use Play Link:
https://shaka-player-demo.appspot.com/demo/#audiolang=en-US;textlang=en-US;clockSyncUri=;uilang=en-US;asset=https://storage.googleapis.com/wvtemp/hmchen/1080p24fpsVP9_hlg_hdr_cenc.mpd;license=https://proxy.uat.widevine.com/proxy;panel=CUSTOM CONTENT;build=uncompiled
What did you expect to happen?
Content plays acceptably
What actually happened?

Playback doesn't start.
The error message:
StringUtils.htmlUnescape is not a function

Are you planning send a PR to fix it?

I have two more links to test Videostack Merge - transiting from encrypted to clear and back.
https://shaka-player-demo.appspot.com/demo/#audiolang=en-AU;asset=https://media.axprod.net/TestVectors/v7-MultiDRM-MultiKey-MultiPeriod/Manifest.mpd
https://shaka-player-demo.appspot.com/demo/#audiolang=en-ET;asset=https://media.axprod.net/TestVectors/v7-MultiDRM-MultiKey-MultiPeriod/Manifest.mpd
I got the same error for those tests.

The Axinom v6 and v7 test vectors are likely no longer being hosted.  Please send a PR to update them!  See https://github.com/Axinom/public-test-vectors and https://github.com/shaka-project/shaka-player/blob/main/demo/common/assets.js

I'm not reproducing this on my computer, and this doesn't look like the kind of issue that would be platform-specific. The PR that moved the htmlUnescape method from VttTextParser to StringUtils also changed all references to the method at the same time...
My first thought is it might be an individual source file being cached on your system, or something like that? It might be possible with the uncompiled demo, which you linked in your report.
Does the problem still happen if you run the compiled demo?

I replaced build=uncompiled with build=compiled in the test link. Now it works as expected. I just used old test links for tests using Shaka Player. Now I will change them all.

I realized that the OP is in our office, so I sat down with her to investigate in person.  The issue was caused by a private Chrome extension used by Widevine for debugging.  It appears to break the demo in uncompiled mode, though it's not clear how or why.
Switching to compiled mode is an effective workaround until Widevine fixes that private extension.
@xhwang-chromium JFYI.
In any case, disabling this Widevine debugging extension makes the player and demo work correctly, so there is no Shaka bug or Shaka demo bug here.

Thanks @joeyparrish for help. The problem is in EME Formatter. I will file an internal bug for this issue.


item_factory should not be stored as class ivar, because its value then fails to propagate to subclasses

@david Could you elaborate on this issue? I'm not sure why we'd want instance variable values to sync across sub-classes.

@adsteel if you have list widget classes you want to inherit from, the item factory won't propagate, so it's basically a reuse issue.


Allow keys in the log list to be different sizes

The Venafi log has a different sized key to the other logs, so this change is required in order to add it.

That's going to merit a change in Chromium for handling keys of different sizes. Let's have that reviewed first (and manually edit ct_known_logs_static.h) then change the way the code is generated.

Seeing as this was approved in https://codereview.chromium.org/1338393002/, LGTM


Fixed typos and corrected plural forms.

Fixed typos:
override → overrides
skip → skips
Why it's useful:
These corrections improve consistency and grammatical accuracy.

Hi team! Could someone please review and merge my pull request? Let me know if any changes are needed. Thanks!
@bigs @jonathanpberger @DavidNix

This is pretty blatant airdrop spam


Can we get a separate user_select file for T_embed in tft_eSPI

In latest TFT_eSPI library by Bodmer, we got setup206 file for T-Display-S3 and if i am not wrong, i guess @mmMicky contributed on it too.  Nevertheless it works great for T-Display-S3 board now.  Can we get a separate file for lilygo T-Embed also?  This would solve big problem for users who are using both boards.   I have tried tft_eSPI library included in this repository and have tried everything what i could do but display of my T-Embed is not working.  I was able to run some sketches from Volos Projects on it before but not anymore even if with current repository's tft_eSPI library.

PR has been added to the main branch.
https://github.com/Bodmer/TFT_eSPI/pull/2510


Validate pods running or completed in e2e tests

Validate pods running or completed in e2e tests

/test e2e-aws-pooled

This could be a source of flakes if a component is in the process of rolling out a config change or something.
What is the motivation for this change?

@sjenning here's the context: (from https://issues.redhat.com/browse/HOSTEDCP-225)
This seems to fix an issue we didn't realise we were suffering. The ignition payload was not fetching the core MachineConfig because of the wrong labels.
That resulted in the static pod haproxy not running in the guest cluster. That resulted in multiple pods crashlooping.
We should validate the guest cluster is operative. E.g wait until all the pods are running or fail otherwise

@taragu we can catch that problem with the current checks we have. The problem is we were testing the 4.8 control plane operator with the 4.8 hypershift operator. We should have been using the latest (main) hypershift operator instead. That's being fixed here: https://github.com/openshift/release/pull/22115

we can catch that problem with the current checks we have.

Can we though? we are validating operators reports back successfully but we are not validating explicitly all pods are running/complete right? May be we can introduce this as a safety check that could help highlight subtle issues since the impact in the e2e total time should be none. WDYT?

Can we though?

Yes, in the case you pointed out above, the service-ca operator would never have reported available because the operator itself was failing to start.
My concern with this additional check is that it could result in false positives and instability in CI due to transient pod states.

This seems to fix an issue we didn't realise we were suffering. The ignition payload was not fetching the core MachineConfig because of the wrong labels.

That resulted in the static pod haproxy not running in the guest cluster. That resulted in multiple pods crashlooping.

We should validate the guest cluster is operative. E.g wait until all the pods are running or fail otherwise

We do validate the guest cluster by relying on conditions on the HostedControlPlane which aggregate conditions/status of operators in the guest cluster.
I agree with @csrwng that a blind check of pods is undesirable. All control plane pods should be operated by some controller and their status surfaced through higher level abstraction (e.g. operator status). Reaching into the guest from this test and checking pods is something we've deliberately moved away from. We've progressively expanded status calculations in the control plane operator to assess control plane health and surface status through HCP/HostedCluster, and my preference would be to continue improving that without layering violations (e.g. coupling the e2e with an awareness of control plane implementation details in the form of specific pod or operator introspection).
In the specific cited bug (https://github.com/openshift/hypershift/pull/469/files), what operator status should have been reporting the crashing pod? If the control plane is unhealthy but the HostedControlPlane status doesn't reflect that, it sounds like a bug in either the control plane operator or a control plane component that needs fixed so that status is being reported correctly.

/close

I agree with @csrwng that a blind check of pods is undesirable. All control plane pods should be operated by some controller and their status surfaced through higher level abstraction (e.g. operator status). Reaching into the guest from this test and checking pods is something we've deliberately moved away from. We've progressively expanded status calculations in the control plane operator to assess control plane health and surface status through HCP/HostedCluster, and my preference would be to continue improving that without layering violations (e.g. coupling the e2e with an awareness of control plane implementation details in the form of specific pod or operator introspection).
In the specific cited bug (https://github.com/openshift/hypershift/pull/469/files), what operator status should have been reporting the crashing pod? If the control plane is unhealthy but the HostedControlPlane status doesn't reflect that, it sounds like a bug in either the control plane operator or a control plane component that needs fixed so that status is being reported correctly.

@ironcladlou @csrwng Although I fundamentally agree the cases that I'm concern about are those that we can't think of ahead of time and only realise afterwards. Those that will break us silently and then will cause painful debugging following git history backwards. I like to have a suite of e2e tests product oriented by matching functional requirements and user stories. The most fundamental one is "As a consumer of Hypershift I want to be able to run workloads successfully in a guest cluster right after installing". Today that's not e2e validated.
Anyway we can always pick up the discussion if something pops up :).

The most fundamental one and the one with wider scope is "As a consumer of Hypershift I want to be able to run workloads successfully in a guest cluster right after installing". Today that's not e2e validated.

@enxebre totally agree with you there, but I think that's something we can validate by running the origin e2e conformance test suite against a hypershift cluster. It should be part of our MVP to be able to run those tests succesfully.

ref https://issues.redhat.com/browse/HOSTEDCP-225


Adds CFBundleShortVersionString to the main .plist on OSX

Hi,
this PR adds the CFBundleShortVersionString key to the .plist file when building an OSX app.
This key is used when displaying the app version in the Finder.
Currently, without the key:

With the key:

Thanks !

:+1:
We also needed.

+1

Thanks for the contribution, but I'm more inclined to take #127 instead, as it points out the differences between the two version keys, and also contains doc/test changes.

Thanks for your comment!
Indeed @herrmannplatz's solution in #127 makes more sense.


Update IAM helper methods to protect against IAM conditions

The methods throw an exception if:

The policy version is greater than 1
Any bindings have conditions

The exception message will need to be changed to include a link with more information.
(Note that this is a new PR so I can close #3359 but leave the branch present for now.)

Amanda, this is now ready to merge - PTAL, and I can give you more context if you'd like.


Choice of language

Hi,
This is not really an issue, but more for information purpose. Not even meant for debating.
I am wondering why golang is the choice of language for a sidecar. From my understanding, SideCar is expected to have a very predictable memory/CPU footprint, since it basically shares the resource with the "main" (host) application.
What I understand about GoLang is that,

It does not provide a good memory management functionality like JAVA, wherein you can set Max/Min heap usage. It is possible to set a ulimit basically would cause the sideCar to crash rather than GC coming into the picture and trying to recovering the application, as JAVA does.
It does not provide true thread pool, every time a new goroutine is spawned instead of recycling the older one (agreed that it is lightweight).
No way to kill a running goroutine. This seems to be an important functionality when a upstream service is latent and the downstream does not want to waste resource on the latent request. If the throughput is high such latent request would lead to spike in goroutine and thus more memory/cpu pressure.
debatable Not as mature in performance tuning framework as compared to other mature languages.

The sidecar is written in C++. It is the  Envoy proxy. https://istio.io/docs/concepts/what-is-istio/overview.html#envoy
All Other components are written in go.

 Thanks.


Restore hash partitioning of arrays

Fixes #2330
Now that https://github.com/rapidsai/cudf/issues/8098 has been fixed, this restores support for hash partitioning for arrays that was removed in #2319.

build

did we have any specific tests for this?

Yes, they were added when the support was disabled to prove that we weren't calling through cudf otherwise the tests would fail.  Which reminds me, I need to remove the exclusions on shuffle that @revans2 added recently for those tests.

build

build

build


This doesn't seem to be an assets file or bundle. isssue

after update game i am not able change game texture can you hlep know this message (This doesn't seem to be an assets file or bundle. )
please fix this issue

Real .assets files don't have that kind of naming. If it was a bundle, it might be encrypted. When it says it's not valid, it's generally right. I expect no other tool will open this either.

any other way to decrypt file than open file

If you have to ask, the answer is no


Rustdoc nocapture

Following https://github.com/rust-lang/rust/pull/86230.
It might need to wait for rustdoc latest nightly to be published first to pass CI though (so tomorrow).
Also: the --nocapture option is unstable for now in rustdoc, is there something particular to be done until it's stable on cargo side? For now I simply add -Zunstable-options but not sure if it's the way to go?

r? @Eh2406
(rust-highfive has picked a reviewer for you, use r? to override)

:umbrella: The latest upstream changes (presumably #10408) made this pull request unmergeable. Please resolve the merge conflicts.

Closing as this is a bit stale. I'm also not clear what this was needed, since it looks like one can just pass -Zunstable-options themselves.  Before reopening, please work with the Cargo team to settle on a design for whatever is needed here.

The current cargo doesn't work, I assume because --nocapture gets prefixed with --test-args. Right now cargo test -- --nocapture still hides input from doctests because it doesn't forward the --nocapture argument properly. This fixes that. See the referenced issues.

Is this fixed?

Doesn't seem like.. but in the interim, try this:
RUSTDOCFLAGS="-Z unstable-options --nocapture" cargo +nightly test --doc

@ehuss @GuillaumeGomez Can you please consider reopening this? It seems the hard work has already been done in rustdoc, and but given most people use rustdoc via cargo, it's availability is quite hindered.

I can't reopen it so I'll let it up to cargo team.


GistFile confusing on when collapsed

The GistFile, though under the hood is a collection of files, can be confusing to new users. Currently, the GistFile is shown as a collapsed folder with no title in the JavaFX TreeView. We should look into adding some sort of metadata as text for this. In its current state it just looks like an empty file folder until expanded. If we cannot find appropriate data to display in the TreeView, it may be optimal to expand the nodes by default so that an end user can see the content within them.

@EasyG0ing1 I opened up GistFX again today, and the issue I was referencing is no longer present. On first launch, after the Gists were fetched, the text "Emulates Java's StringBuilder and StringJoiner, sort of." was not present. This node did not have any text, only the subnodes. It must not get updated on the initial install. Perhaps this is being fetched from the local SQLite cache before it's been populated?

So this is the order in which data is fetched from GitHub...
FIRST, we look for the metadata which is stored in JSON format in a Gist
that never gets placed in the tree... I also store the metada locally in
the database AND in the Preferences and the JSON class looks for the newest
version of the metadata (there's a timestamp in the class) and it uses that
newest verson.
Once that is done, (and this process starts of course after your token
validates) ... let me back up .... this is how it is SUPPOSED to work in
the beginning:
You pull a MAP of Gists through your user object in the API ...
The problem is, at the moment that Map doesn't actually contain any file or
Gist content - it ONLY contains GistIDs ....
When I opened an issue about that, it became a confirmed bug in the API,
and is on the list to be fixed at some point. So when I had to do, was used
to just IDs from that map and then use a separate API call to grab each
gist individually, which then does contain the contents of the gist
including all the file contents.
That data gets loaded into a map which then gets sent along to the creation
of the Gist window which then gets used to create the tree - in a nutshell
...
The data is simultaneously loaded into the database when the map is
created, so the database is fully populated on first use and first login
with a valid token.
The database is never changed after that, UNLESS YOU CHANGE IT by:

Editing a file and then saving it.
Making any other changes to your Gist (changing the public state, or
modifying the GitHub description, or adding a new file etc. etc.)

I don't upload any data to GitHub after it's been downloaded (other than
adding new files or changing the Gist description) behind the scenes in
order to reduce the accumulation of Gist file version history ... I make
the user actually commit their file to GitHub - which I call "Saving the
file"
So then, the next time you load GistFX, once the token proves good, it
loads the data from SQL then loads the main window which happens almost
instantly ... but then ... it downloads the GitHub data and compares it to
what is in the database in case there were any changes made since closing
GistFX and the next time it's launched ... but when it finds a conflict
between the local data and the GitHub version, it places a large red X next
to the filename and it expands the branches so that you see it right away.
I can't explain why you experienced what you experienced, but you can start
from scratch by launching GistFX with the masterreset option passed into
the launch which you can do by editing the shortcut or launching it from
CMD.EXE When you pass in the masterreset argument, it will load up a
reset screen where you can clear out all the local settings and local data
and then try it again from scratch and see what happens.
On Tue, Apr 12, 2022 at 5:04 PM Dustin Redmond @.***>
wrote:

@EasyG0ing1 https://github.com/EasyG0ing1 I opened up GistFX again
today, and the issue I was referencing is no longer present. On first
launch, after the Gists were fetched, the text "Emulates Java's
StringBuilder and StringJoiner, sort of." was not present. This node did
not have any text, only the subnodes. It must not get updated on the
initial install. Perhaps this is being fetched from the local SQLite cache
before it's been populated?
[image: Screenshot 2022-04-12 200234]
https://user-images.githubusercontent.com/42328885/163073817-fd809667-ab1e-4507-803b-77af2ad27b15.png
—
Reply to this email directly, view it on GitHub
https://github.com/RedmondSims/GistFX/issues/5#issuecomment-1097403721,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACNDPUSM5OJKBS2ZYNCLOPLVEYFRXANCNFSM5TE3W52A
.
You are receiving this because you were mentioned.Message ID:
@.***>

So this is the order in which data is fetched from GitHub...
FIRST, we validate the token ...
Next, we look for the metadata which is stored in JSON format in a Gist that never gets placed in the tree... I also store the metadata locally in the database AND in the Java Preferences and the JSON class looks for the newest version of the metadata (there's a timestamp in the class) and it uses the newest JSON copy of the metadata class.
Once that is done  .... this is how it is SUPPOSED to work in the beginning:
We pull a MAP<GistID,GHGist> of Gists through your user object in the API ...
The problem is, at the moment that Map doesn't actually contain any file or Gist content - it ONLY contains GistIDs ....
When I opened an issue about that, it became a confirmed bug in the API, and is on the list to be fixed at some point, but at the moment, it's still not working ...  so when I had to do, was I use the gist IDs from that map and then use a separate API call to grab each gist individually, which then does contain the contents of the gist including all the file contents.
That data gets loaded into a map which then gets sent along to the creation of the Gist window which then gets used to create the tree - in a nutshell ...
The data is simultaneously loaded into the SQLITE database when the map is created, so the database is fully populated on first use and first login with a valid token.
The database is NEVER changed after that unless you modify your Gist data.
Also, I don't upload any data to GitHub automatically without the users prompting EXCEPT for adding new Gists or new files or changing the Gist description. The reason for that is to  reduce the accumulation of Gist file version history ... I make the user actually commit their file to GitHub - which I call "Saving the file"
So then, the next time you load GistFX, once the token proves good, it loads the data into the Java window from SQL then we bring up the main window which happens almost instantly ... but then in another thread, ... it downloads the GitHub data and compares it to what is in the database in case there were any changes made since closing GistFX and the next time it's launched ... but when it finds a conflict between the local data and the GitHub version, it places a large red X next to the filename and it expands the branches so that you see it right away.
So, I can't explain why you experienced what you experienced, but you can start from scratch by launching GistFX with the masterreset option passed into the launch which you can do by editing the shortcut or launching it from CMD.EXE When you pass in the masterreset argument, it will load up a reset screen where you can clear out all the local settings and local data and then try it again from scratch and see what happens.

@dustinkredmond - I should add a comment about the words that are placed next to the folder icons ... When you first use GistFX and it pulls all the Gists down into the database and then creates the tree etc., there is a class called Json that handles all of the metadata. So when Gists are downloaded, they are passed over to that class to be assigned a name.
I felt this was a weird thing to do ... not be able to have simple names for your Gists... so GistFX gives you the ability to assign a name to your Gists, while you retain the description as well.
There are a few ways to change the name of a Gist.

Right-click on the Gist object in the tree and choose Rename.
With the Gist selected, at the top of the window, click on the name label and you'll be presented with a popup window that lets you assign your custom name to your Gist.
I thought I added this option in the Edit menu but apparently not, I'll add it there too.

This might help you in simplifying the layout of your Gists in the tree. Of course, you can also create categories for your Gisgts and then drag Gists into those categories which can further help in simplifying the layout in the tree.

@dustinkredmond - one last note ... if you have files within Gists that you decide should belong to another Gist, you can drag and drop files between Gists and GistFX will create the file in the destination Gist then remove it from the source Gist... one more option for you to help you in organizing your Gists a little better.

@dustinkredmond - OK, I found the problem that you were describing. It could only happen at first launch when you've never used the program before, but what it was doing, was it was NOT populating the name fields of the Gist objects when there was no metadata to pull from. Then what would happen is subsequent usage of the program would sort of fill in the missing data.
I fixed it
If you haven't invested a lot of effort into your metadata, then do this:
Run GistFX with these command-line options:
masterreset password=<your password>

Then you will see a master reset window pop up. Check these boxes:
Reset Database (second box)
Wipe out Local Metadata
Wipe out GitHub Metadata

You'll get a warning that all of your metadata will be gone forever - that's ok that's what we want.
Click GO, then confirm, then wait for it to say that it's done.
Then, download and install version 3.4.4 from the releases and install it. Run it normally - it will still have your token stored so you should only need to simply log on with your password and it will then create the metadata properly and re-download your gists etc.


Allow to pass custom timestamp to HBase record and Query by time

This PR includes the feature to write using the RDD timestamp and allow to query into the HBase filtering by timestamp.

Very good @fbbergamo. sorry for the delay, I'll do a review soon!

@nicolaferraro could you reevaluate?


Temporarily disable debug env export.

As title. Workaround issue with GCC 9 series conda packages.

Thanks for the patch!


dCdGdAdT will get the complementary UAGC

hi, I want to get a DNA double strands structure using HELMEditor.
But after I loaded into the sequence dCdGdAdT, and I wanted to get the complementary strand automatically, A RNA strand appeared.
How to fix this bug?

Hi,
We are no longer making changes to the Java thick client, and recommend using the webeditor However, if you want to continue to use the original editor, feel free to suggest a fix to the code. We are an open source project and welcome contributions
The webeditor also has restrictions on creating a complementary strand and will only work for RNA, but it includes the ability to apply rules to molecules. You can create a rule that changes the ribose into deoxyribose using the following script:
function(plugin) {var n = plugin.replaceMonomer(org.helm.webeditor.HELM.SUGAR, 'R','dR');return n>0;}
I have added this rule to the demo version at
http://webeditor.openhelm.org/hwe/examples/App.htm

So hopefully you can try it out.
Please let us know how you get on.


Protein Family Signatures

Can different lengths of bp correspond to different information received about protein families?

Struggling to find stuff related to this. May need a bit more guidance

Consideration of these parts should consider not only families but common motifs/ distinct functional aa's in certain location specific areas


Support for checkboxes

I know these aren't standard in all flavors of markdown, but any interest in supporting Github's style of checkboxes in this package?
This example:
- [ ] An unchecked checkbox
- [x] A checked checkbox

Would render as it does on Github:

[ ] An unchecked checkbox
[x] A checked checkbox

Didn't really notice, but this is in the works (possibly) for chjj/marked, so I'm guessing when it's merged in there it will also work in this package, yes?

@karllhughes Yes. If https://github.com/chjj/marked/pull/587 will be merged, markdown-to-html-pipe will support checkboxes.

@karllhughes With<EMAIL_ADDRESS>chjj/marked is now a peer dependency.
That way you can temporarily replace chjj/marked with jhollingworth/marked. Once the PR will be merged and released, even versions like 0.4.0 or 1.0.0 wouldn't require an update to markdown-to-html-pipe.
If there are any other issues or suggestions, feel free to ask.


Characters out of order on android web browsers

I've noticed that the script works fine on all browsers, including blackberry and iOS. But when using android the characters don't display in the correct order.

still hitting this error on Samsung Galaxy S5 in Chrome, known issue?


Minified

I have downloaded the latest pannelium.is and libpannelium.js, minified them both and that cat them together.  I have a few issues and before I report them I wanted to validate this is the correct process to create a minified version?
John

This is documented in the readme's Building section: https://github.com/mpetroff/pannellum#building
There's a script for doing this (requires Python and Java): https://github.com/mpetroff/pannellum/blob/master/utils/build/build.py

Thank you, very sorry I didn't see this in your documentation.  Nothing more annoying than someone not reading something documented.


Improve performance, fix async put bugs and support glm-9b

@YaoJiayi
I rebased the dev branch so that it can run CI now. Also, it seems okay to directly use _tuple_kv_to_blob in store().
Please fix the remaining problems:

Some of the unit tests are failing
Unit tests take a loooong time to execute (especially in test_cache_engine.py), indicating that there could be some problems in the implementation

@ApostaC Quick question: did you measure the performance of _tuple_kv_to_blob?


feat(algebra/order): unions of Ioc intervals

Forward-port lemmas in Data.Set.Intervals.Group about disjointness of intervals, from mathlib3 PR #18427

bors r+


Cleanup of runtime.Object and meta.Accessor

How to categorize this PR?

/kind cleanup
/priority normal
What this PR does / why we need it:
With<EMAIL_ADDRESS>there are client.Object and client.ObjectList to distinguish between single API objects and object lists.
c-r has replaced their usage of runtime.Object (which is more generic) by those two interfaces to have a clearer func/interface contract of what implementations expect from passed objects.
I followed up on this and cleaned up our usage of runtime.Object as well and replaced it with client.{Object,ObjectList} wherever applicable.
Though, there are still a lot of runtime.Object usages left, e.g. in API and registry packages, which have to comply with other interfaces expecting runtime.Object.
Also some of our helper funcs are generic and accept a single object as well as an object list, so for those cases runtime.Object is also still needed.
I think I cut it down to the bare minimum now.
I also cleaned up some unnecessary usages of meta.Accessor in favor of client.Object where it is helpful and makes code a bit slimmer.
Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/3109
Special notes for your reviewer:
/squash
Release note:

Some helper functions and interface types have been changed to accept `client.{Object,ObjectList}` instead of `runtime.Object` where applicable to have a clearer contract of what is expected from passed parameters.

❤ all these cleanup PRs!

❤ all these cleanup PRs!

/squash

/squash


Add cabal.project file for local Haskell development

I have:

[x] Based work on latest develop branch
[x] Followed the contribution guide
[ ] Looked for lint in my changes with hlint . (lint found code you did not write can be left alone)
[ ] Run the test suite: $(nix-build -A selftest --no-out-link)
[ ] Updated the changelog
[ ] (Optional) Run CI tests locally: nix-build release.nix -A build.x86_64-linux --no-out-link (or x86_64-darwin on macOS)

This is purely an improvement for the Devs. It makes it much easier to use HLS on the code-base.

Added some docs.
I am not sure how to make sure this doesn't bitrot, can I add a test like cabal repl all somewhere? This would work good enough, imo.


 closing tags

It would be great if the code snippets had closing tags to
JSX doesn't allow unclosed  tag!

You can read MDN web doc and understand in HTML 5 its valid without the "closed tag". When using react a lot of tags need to be "closed". Not everybody works with it so I'm not sure if this is a good idea.

Think of it like this, though: for React > is invalid and /> is needed; for everyone else /> is not needed, but it's not invalid either, it's still valid HTML 5 syntax. Adding it would help React users, while not hurting anyone else.

Think of it like this, though: for React > is invalid and /> is needed; for everyone else /> is not needed, but it's not invalid either, it's still valid HTML 5 syntax. Adding it would help React users, while not hurting anyone else.

That was my point. If it works for some without breaking for others, it can be included.

Yes, closing tags should be there. They are needed even in markdown files of Nuxt Content. Thanks for this amazing repo. ❤

Got the same issue for <input> and <br>. I am adding a 👍   for closed tags too, thanks for this nice work by the way !


add new command to report on repos not on master

based off of status command.
use 'git branch --list' to show all branches, and checked out branch is marked with a '*'
only show results for branches not on master

Coverage decreased (-0.1%) to 22.17% when pulling 366830f462175c9da41fc96c9a2efb490fac7a02 on branches into 7107dc4399b1843be5186dd1ab1faa712e73e017 on master.

You should really do that with git rev-parse --abbrev-ref HEAD rather than parsing git branch

nice. I poked around, and didn't find anything better immediately.
other than being shorter and more direct, any reason why the other approach might fail us at any point?

(out of interest; incorporating your suggestion)

Coverage decreased (-0.1%) to 22.17% when pulling a0d31ad0341180695456fa4574eccd15f8e40f1d on branches into 7107dc4399b1843be5186dd1ab1faa712e73e017 on master.

git branch is a porcelain command - a user-focused command. The output format could change between git versions. git rev-parse is a plumbing command - designed for scripting, etc. The output of this is much less likely to change. Also, it saves you a regexp match :-) Note in both cases that you're getting the local branch name, not the remote branch name. I realise that for most people they are the same, but they don't have to be.

ok, @codeaholics. thanks for the insight. as far as different remote branch names, I think this is all I am after for now, but I guess it could be extended.

Most people won't even notice :-) I think this command is a good idea. Would certainly have been useful when I was working on resources with, like, 1,000 microservices checked out.

Coverage decreased (-0.1%) to 22.17% when pulling 4835df176fbd6d85acc8ba827c39d43496d273a7 on branches into 7107dc4399b1843be5186dd1ab1faa712e73e017 on master.

Coverage decreased (-0.1%) to 22.17% when pulling 4835df176fbd6d85acc8ba827c39d43496d273a7 on branches into 7107dc4399b1843be5186dd1ab1faa712e73e017 on master.


add workaround for old gcc

At least on RHEL-5
 include/hprose_reader.h:235: error: 'INFINITY' undeclared (first use in this function)
 hprose_reader.h:264: error: 'NAN' undeclared (first use in this function)

With this workaround, build + test suite are ok.

Thank you!


Converting a notebook to JATS for binder

I saw in the binder examples stencila repo that we have a Jupyter notebook in JATS form, which is pretty awesome! Do we know how that conversion was done? Is there a "standard" conversion tool from ipynb -> jats? Maybe @nuest knows? Would be great to have something like this we can point people to.

What's JATS? And do we still want an example for it?


Install script defaults to running as root

https://github.com/FlowFuse/device-agent/blob/239c1c824212c76575978badd4c765d73c10f308/service/raspbian-install-device-agent.sh#L93
$SUDO_USER is empty as it's not running under sudo.
Probably need to replace this with $USER

Thank you, I'll create a PR and close both with it


Feature/rsi decimal

What? and Why?
EQ added the ability for currency values to be decimal places so we needed to update our code to handle this.
Checklist

[x] CHANGELOG.md updated? (if required)

Codecov Report

Merging #109 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #109      +/-   ##
==========================================
+ Coverage   87.41%   87.47%   +0.05%
==========================================
  Files          17       17
  Lines        1383     1389       +6
==========================================
+ Hits         1209     1215       +6
  Misses        174      174

Impacted Files
Coverage Δ

transform/transformers/PCKTransformer.py
98.86% <100%> (+0.08%)
:arrow_up:

Continue to review full report at Codecov.

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


UI Tasks 2/11/2015

Machine UI [MERGE]
Container Log Support [MERGE]
Projects [MERGE]
Hosts 1.0 UI [WIP]

Machine - Not Merged
Container Log Support - Merged with exception of support to distinguish between stdout and stderr.
Projects - Merged with exception of being able to delete Projects


iOS example missing #include "tensorflow/core/framework/types.pb.h"

NOTE: Only file GitHub issues for bugs and feature requests.  All other topics will be closed.
For general support from the community, see StackOverflow.
To make bugs and feature requests more easy to find and organize, we close issues that are deemed
out of scope for GitHub Issues and point people to StackOverflow.
For bugs or installation issues, please provide the following information.
The more information you provide, the more easily we will be able to offer
help and advice.
What related GitHub issues or StackOverflow threads have you found by searching the web for your problem?
Environment info
Operating System: iOS 10.2
Installed version of CUDA and cuDNN:
(please attach the output of ls -l /path/to/cuda/lib/libcud*): not related it is iOS
If installed from binary pip package, provide:

A link to the pip package you installed:
The output from python -c "import tensorflow; print(tensorflow.__version__)".

If installed from source, provide

The commit hash (git rev-parse HEAD)
The output of bazel version

If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)
What other attempted solutions have you tried?
Logs or other output that would be helpful
(If logs are large, please upload as attachment or provide link).

@kwccoin Does this issue persist?  Looks like this fell through the cracks (cough, @petewarden, cough).

There's no enough information on this bug yet unfortunately. Could you confirm you successfully followed the steps here?
https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/makefile#ios
If that's true, please post reproduction steps so we can see the same error here.

No response received after several weeks, so I'm closing for now. Please reopen with more information if this is incorrect.

Getting the issue here as well when building for iOS!


Splitting API and data sources

Heyho @jklmnn and @kiliankoe
The data-sources are now compartmentalized into ParkAPI2-sources and the CI script and README are updated.
As it looks, you need to review and accept the pull request #12

@jklmnn, if you have time please configure this repo the same way as the original ParkAPI, meaning: do not allow merge requests to not interfere with rebasing and please explain how an actual contribution from a fork must be requested.
The last time you picked the commits from a pull requests and did something. I'd like to add this part to the README

I configure the repo. Now PRs can only rebased and merge commits are forbidden. Also all conversations in reviews have to be resolved.
The rationale for not having merge commits is that they infer with rebasing. A linear history allows to rebase the whole branch. Having a merge commit will break that since it has to be reapplied manually each time a rebase is done. This is especially useful when git bisect is used to analyze an old bug but an early commit has to be modified to e.g. adapt to new tooling. Having merge commits basically makes this impossible (or at least utterly annoying).
The review process I have in mind works as follows:
The reviewers will open comments with questions, change requests, etc. The author will have to address all each comment, either with an explanation or justification or with a new commit. When the author has addressed all comments they rerequest the review from the reviewer. The reviewer will see the comments and either continue the discussion or resolve the comment. The author of the commit MUST NOT resolve any comment not written by themselves. This ensures that no review comment is missed.
If the author of the PR has merge rights it's the authors task to merge the commit, if not the maintainer will do that (additionally we could ask the author for confirmation that the PR is ready). This ensures that no PR is merged in an incomplete state.
About the commit picking: Many people just clone the repo, add something to their master/main and then open a PR. That works for the first time but will likely break the second time when the fork is not properly updated. In the particular cases people merged the projects current master into their own master creating a merge commit. Since merge commits are not allowed I cannot directly merge that PR. If it was allowed the projects commit history would include multiple merge commits of other people updating their branches, adding a lot of clutter to our history and making it hard to read.
To fix this I usually open a new branch that is based on the current master, cherry-pick the relevant changes onto that branch and then rebase that branch into master (either by opening a new PR or just on the command line).
The proper way to update a fork is as follows:
$ git remote add upstream <url of the upstream repo>
$ git checkout master
$ git rebase upstream/master
$ # if that fails:
$ git reset --hard upstream/master
$ # note that this will delete any change on master that is different from upstream

Then all new changes can be based on the proper master branch.
A good example for the problem that merge commits create is https://github.com/offenesdresden/ParkAPI/pull/235. This PR would add 19 commits. 8 of them are merge commits, 10 of them are commits that are already on master. There is only a single commit that contains the change this PR intends to add to the upstream repo.

Hey, thanks a lot. I'm still trying to understand the work-around. The appearance of the useless merge commits is understood.
If a contributor forks the repo, commits something and then later (after new upstream commits) pulls with git pull --rebase, these useless merge commits would not happen, right? Well, unless there's a merge conflict.
I start to get an idea of the git rebase upstream/master part above. As the docs say: The changes will be boiled down to the set of commits that would be displayed with git log <upstream>..HEAD. But i guess your if that fails comment addresses the same problem of not resolvable merge conflicts.

Sorry for the late reply. I'm not 100% sure I understand your question correctly.
What git rebase does is basically taking your HEAD and apply the commits from HEAD .. upstream HEAD to your local branch. For this to work git needs to find a compatible set of changes. It also works if you have different commit IDs. So if you have branch A and B. They're identical.  If you instead cherry pick the commit from C to A both A and B will have the same set of changes but different commit IDs. If you run git rebase B now A will be identical to B again, because git recognizes that this is the same change.
If you cherry pick two different commits to A and B git rebase B will try to use B as your new "base" which means that it will take the common history of A and B and then apply the commit from B first and the commit from A second. So A contains both commits after that with the HEAD of A being the same commit after the operation. If it cannot apply the changes made on A on the commits of B, the rebase will stop with a merge conflict that you have to resolve by hand. If you want to do this depends on your situation. If you have changes on A that are older but you need them on the newer version (B) you have to resolve the merge conflict by hand. If you just want to have the same version as B you'd just use git reset --hard B which is basically telling git to throw everything on the current branch away and use the version of B.
I hope that answers your questions.


nix-flatpak "stopped working"

Hey!
Recently, I added the nix-flatpak flake to my NixOS flake!
Though, it first worked fine, but now it does not seems to do anything when reloading the config.
Maybe related: #26

Don't know if I'll be able to help, but if I am, I'll need more details.

Don't know if I'll be able to help, but if I am, I'll need more details.

Yea, sorry for an vague PR, seems to be related to some HM import stuff and infinite recursion...

There's an example on how to import nix-flatpak in HM (installed as nixos module) at: https://github.com/gmodena/nix-flatpak/blob/main/testing-base/flake.nix#L23
Hope this helps. Infinite recursion issues can be a pain to troubleshoot. Feel free to paste a stack trace (build --show-trace).


Introduce higher-level interface to API

I'm picturing a class wrapping a HaloInfiniteClient instance, maybe HaloInfiniteResource, that is initialized similarly to the client but integrates calls to services and provides more opinionated responses. For example, it would be nice to request matches and have the names of playlists, maps, modes, and players returned (and less deeply nested) instead of asset IDs and version IDs that the user needs to understand how to process further.

@aapokaapo I'm actually playing with returning the Pydantic models directly from the HaloInfiniteClient service methods.
A new MatchAPI class would wrap a client instance and have 2 methods, get_match and iter_match_history, which return/yield new models wrapping the current Pydantic models. The new models would provide convenience properties for more direct access to the match/stat/skill attributes.
Models might look like:
Match
match_id
start_time
map_name
...
teams
players
Team
team_id
name
kills
...
mmr
Player
player_id
gamertag
kills
...
csr_before
csr_after
What do you think?
I'd welcome a 2nd opinion if you are interested in reviewing a PR.


Project Add: Lead case study model

Pull Request for PyVerse 💡
Requesting to submit a pull request to the PyVerse repository.

Issue Title
Please enter the title of the issue related to your pull request.
#860

[X] I have provided the issue title.

Info about the Related Issue
What's the goal of the project?
Adding a Lead case study project that shows the different techniques which we can use to analyze the proper sales, with the different visualizations that allows us to see data analysis of various different factors & growths.

[X] I have described the aim of the project.

Name
Please mention your name.
Yash K. Saini

[X] I have provided my name.

GitHub ID
Please mention your GitHub ID.
yashksaini-coder

[X] I have provided my GitHub ID.

Email ID
Please mention your email ID for further communication.
Enter your email ID here.

[ ] I have provided my email ID.

Identify Yourself
Mention in which program you are contributing (e.g., WoB, GSSOC, SSOC, SWOC).
GSSoC-Ext

[X] I have mentioned my participant role.

Closes
Enter the issue number that will be closed through this PR.
#860

[X] I have provided the issue number.

Type of Change
Select the type of change:

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[X] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Describe how your changes have been tested.
I tested and generated plots

[X] I have described my testing process.

Checklist
Please confirm the following:

[X] My code follows the guidelines of this project.
[X] I have performed a self-review of my own code.
[X] I have commented my code, particularly wherever it was hard to understand.
[X] I have made corresponding changes to the documentation.
[X] My changes generate no new warnings.
[X] I have added things that prove my fix is effective or that my feature works.
[X] Any dependent changes have been merged and published in downstream modules.

@yashksaini-coder remove plus sign from the file name.

@yashksaini-coder remove plus sign from the file name.

I don't see a plus sign, which file u talking about ?

Data_Science/Lead Conversion Case Study/EDA+Feature Engineering+Outlier Analysis.ipynb

@UTSAVS26 bro done with the changes you can merge it now


Specify 'engines' in package.json

Overview
Keep the size small and compilation simple.
Deliverables

[x] specify "node": ">=18.0.0"

Work for this issue will begin begin on branch work-liquid-labs/npm-toolkit/30.

Issue released.


expose agent_wait_timeout property

expose agent_wait_timeout property, it maybe useful in slow environment.
Fixes-Bug: #2405
What is this change about?
The bosh agent timeout is 600 by default, and there is no way to customize right now for ops manager managed bosh cause the manifest is not exposed.
We are running in nested environment, sometimes due to resource contention, the environment can get slow, expose the timeout setting, we can adjust the timeout setting to redure failure rate.
To avoid error like this:
Task 32

Task 32 | 03:19:13 | Preparing deployment: Preparing deployment (00:00:09)
Task 32 | 03:19:22 | Preparing deployment: Rendering templates (00:00:10)
Task 32 | 03:19:32 | Preparing package compilation: Finding packages to compile (00:00:00)
Task 32 | 03:19:32 | Compiling packages: jq-1.6/a0adb6701bf46e97d40023cd6cc02c5c2c59b9bc
Task 32 | 03:19:32 | Compiling packages: golang-1.17-linux/355e0f4a536222d97a513bf5ca619f4abd4b755f4d3b9a5f788c84995414da7c
Task 32 | 03:19:32 | Compiling packages: ruby-3.1.1-r0.86.0/6cbb082298da54481330e30a57a4c587ae20db0c51b1bdee448ca817263bda3a
Task 32 | 03:19:32 | Compiling packages: jemalloc-5.2.1/a2271abcfb45d7943bf671cbdf4322176de7ef8c
Task 32 | 03:22:20 | Compiling packages: jq-1.6/a0adb6701bf46e97d40023cd6cc02c5c2c59b9bc (00:02:48)
Task 32 | 03:22:20 | Compiling packages: ruby-3.1.1-r0.86.0/6cbb082298da54481330e30a57a4c587ae20db0c51b1bdee448ca817263bda3a
Task 32 | 03:24:08 | Compiling packages: jemalloc-5.2.1/a2271abcfb45d7943bf671cbdf4322176de7ef8c (00:04:36)
Task 32 | 03:24:08 | Compiling packages: pks-nsx-t-curl/5bd047f96fe7d228f2d188a23941b6bbb74dabdf2c5f9a2da5dd8cc14945e1e9 (00:01:15)
Task 32 | 03:25:23 | Compiling packages: pks-nsx-t-jq/04efd099e0390fdc6fe33166fbd76991d36b182a93705cd817f0660ae1892540 (00:00:18)
Task 32 | 03:25:41 | Compiling packages: pks-nsx-t-govc/3a5954e78a7d8bbf71b8d0479429f5264e501f2045524fd4187fbeccfed5184d (00:00:19)
Task 32 | 03:26:00 | Compiling packages: pks-nsx-t-scripts/ea2810557652749d719aea9624957aa39fb15856c5247668535b7497fcfcd239 (00:00:17)
Task 32 | 03:26:17 | Compiling packages: database-backup-restorer-boost/05f72399bdd8d91643f42ac411ba65befb78ac0334484dbc3ca95c5286ab7680
Task 32 | 03:26:43 | Compiling packages: ruby-3.1.1-r0.86.0/6cbb082298da54481330e30a57a4c587ae20db0c51b1bdee448ca817263bda3a (00:07:11)
Task 32 | 03:26:43 | Compiling packages: libopenssl1/fc7399fff08220e310276752269465ea796a68700f506af401b14693a266458f
Task 32 | 03:26:51 | Compiling packages: ruby-3.1.1-r0.86.0/6cbb082298da54481330e30a57a4c587ae20db0c51b1bdee448ca817263bda3a (00:07:19)
Task 32 | 03:26:51 | Compiling packages: libpcre2/179e9ac923922eafa49c6ca5ba58c1a0ef996a066ff1673d57549c2a6e140f52
Task 32 | 03:26:56 | Compiling packages: database-backup-restorer-boost/05f72399bdd8d91643f42ac411ba65befb78ac0334484dbc3ca95c5286ab7680 (00:00:39)
Task 32 | 03:26:56 | Compiling packages: database-backup-restorer-postgres-13/cde50a4f0c08d11adfa6ae4a55a6d7a7a116f7cf8206de6262080d20128f976c
Task 32 | 03:27:20 | Compiling packages: libpcre2/179e9ac923922eafa49c6ca5ba58c1a0ef996a066ff1673d57549c2a6e140f52 (00:00:29)
Task 32 | 03:27:20 | Compiling packages: database-backup-restorer-postgres-11/9988edefe0e8272e2621ba76177ec39cd359c5f80a106f7ba0d5579e7c33a32a
Task 32 | 03:30:43 | Compiling packages: libopenssl1/fc7399fff08220e310276752269465ea796a68700f506af401b14693a266458f (00:04:00)
Task 32 | 03:30:43 | Compiling packages: database-backup-restorer-postgres-10/67733ad1b5143425b5ee7a46a491e1389910f5b96c15d8c29bd73b8bae70e6f7
Task 32 | 03:30:45 | Compiling packages: golang-1.17-linux/355e0f4a536222d97a513bf5ca619f4abd4b755f4d3b9a5f788c84995414da7c (00:11:13)
L Error: Timed out pinging VM 'vm-ddcc1564-3897-41a6-958c-8194f0a16015' with agent '5eb45e7a-f007-4b18-a969-db19db307d37' after 600 seconds
Task 32 | 03:32:58 | Compiling packages: database-backup-restorer-postgres-11/9988edefe0e8272e2621ba76177ec39cd359c5f80a106f7ba0d5579e7c33a32a (00:05:38)
Task 32 | 03:32:58 | Compiling packages: database-backup-restorer-postgres-13/cde50a4f0c08d11adfa6ae4a55a6d7a7a116f7cf8206de6262080d20128f976c (00:06:02)could not execute "apply-changes": installation was unsuccessful

Task 32 | 03:36:25 | Compiling packages: database-backup-restorer-postgres-10/67733ad1b5143425b5ee7a46a491e1389910f5b96c15d8c29bd73b8bae70e6f7 (00:05:42)
Task 32 | 03:36:51 | Error: Timed out pinging VM 'vm-ddcc1564-3897-41a6-958c-8194f0a16015' with agent '5eb45e7a-f007-4b18-a969-db19db307d37' after 600 seconds

Task 32 Started  Tue Oct 25 03:19:13 UTC 2022
Task 32 Finished Tue Oct 25 03:36:51 UTC 2022
Task 32 Duration 00:17:38
Task 32 error
Updating deployment:
Expected task '32' to succeed but state is 'error'

Exit code 1

Please provide contextual information.
https://vmware.slack.com/archives/C047TFNTP98/p1666616286016119
What tests have you run against this PR?
Include a comprehensive list of all tests run successfully.
How should this change be described in bosh release notes?

allow use to customize agent_wait_timeout, for slow environments

Does this PR introduce a breaking change?
Should not break anything, the default value 600 is the same as previously hardcoded value.
Tag your pair, your PM, and/or team!
It's helpful to tag a few other folks on your team or your team alias in case we need to follow up later.

@adam-jian-zhang If you're getting "Error: Timed out pinging VM '...' after 600 seconds", then something else is wrong. There is no good reason for a VM to take 10 minutes to talk to a BOSH Director. Usually it's because the networking is broken or the BOSH agent can't come up.
I don't believe increasing the agent timeout will help you, but I wish you luck.

We are running in nested environment, the ESXI hosts that run bosh vms are VM itself, sometime it error out, but retry would be fine. I think expose the timeout options can help in our use cases.

@adam-jian-zhang do you have any evidence that these instances would have come up fine after 10 minutes? Because I agree with Cunnie, VMs should not take more than 10 minutes to boot.

I merged the commit but modified the message to be more explicit about the condition we're trying to address. Good luck, @adam-jian-zhang.

I merged the commit but modified the message to be more explicit about the condition we're trying to address. Good luck, @adam-jian-zhang.

thanks a lot.

@adam-jian-zhang do you have any evidence that these instances would have come up fine after 10 minutes? Because I agree with Cunnie, VMs should not take more than 10 minutes to boot.

VM boots fine, we observed extreme slowness when doing compile in jammy stemcell, and some times it error out, hard to get error log since the compliation VM got deleted. And if we are lucky enough to get past to installation phase, sometime also error out, we are debugging this. We are hoping extend this timeout to increase the success rate, but we need to address the jammy compliation slowness.


Vuex stores cleanup and stores documentation addition

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/799
Originally created by @derek-knox on 2019-07-16 20:44:23

Originally from https://gitlab.com/meltano/meltano/merge_requests/722#note_191922021

(trim down non-shared state) and then maybe add a small guide (like you did for the UI decisions) in the contribution guide?

I think it should be along the lines of:

[x] Vuex stores' state should be used when you need to edit the shared state
Vuex actions should return Promises (thenable, i.e. support async/await) (holding off as a one-time fix for now https://gitlab.com/meltano/meltano/issues/799#note_207016050 where we can update piece by piece when needed)
[x] Component data should be used for local mutable state
[x] Component propsshould be used for local immutable state
[x] Standardize on a resetDefaults implementation and ensure we properly inject state/getters/context etc. vs leveraging the scope reference due to the const state = ...; const getters = ... approach. Related to this const approach results in shadowing linting errors. Either change the linter or change our const to inlining our export default and destructuring approach. Completed as part of !734
[x] Documentation update (similar to Contributing UI/UX section + likely link to specific Vuex docs)

View 10 previous comments from the original issue on GitLab


Update Unifi Controller version

Merge with https://github.com/gozoinks/unifi-pfsense/pull/86
Update only new version package. Force install snappyjava  when openjdk is update.

Superceded by #96


how select or unselect tag programacaly?

Hello
how select or unselect tag programmatically?

I have the same question. How can I do it?

same problem

Just save your list , and again set the data with your modified list.