rock64 SD silent boot fail with pre-release 0.10.x openmediavault

Rock64 1Gb board.
Pre-release from gitlab build fails to boot:

❌ https://github.com/ayufan-rock64/linux-build/releases/tag/0.10.12
❌ https://github.com/ayufan-rock64/linux-build/releases/tag/0.10.10 (buster-openmediavault-rockpro64-0.10.10-1181-arm64.img.xz)

No boot message, black screen.
Works:

✅ https://github.com/ayufan-rock64/linux-build/releases/tag/0.9.14 works fine (both arm64 and armhf)

Not sure how to debug/trace this. The failing 0.10.x series have 3 partitions, the working 0.9.x images have 2 partitions. There is an extra (appears to be empty) boot-efi partition.
I think this is different to issue #361

I think this might be the same problem as the issue I just created, #428

Based on @ReimuHakurei insight I took the bootloader he suggested https://github.com/ayufan-rock64/linux-u-boot/releases/tag/2017.09-rockchip-ayufan-1065-g95f6152134 and applied to an SD card that had OMV from https://github.com/ayufan-rock64/linux-build/releases/tag/0.10.12 (specifically https://github.com/ayufan-rock64/linux-build/releases/download/0.10.12/buster-openmediavault-rock64-0.10.12-1184-arm64.img.xz)
Boots fine and from a quick experiment with:

usb keyboard/hdmi monitor
network over ethernet

the OMV UI
ssh login

0.10.12 Buster appears to work. I've not tried this in anything like production and not attempted any performance tests on CPU, network, USB3, read/write disk performance, thermal monitoring under load.

I think this might be the same problem as the issue I just created, #428

Agreed! :+1:

I was reading about the new https://www.armbian.com/newsflash/armbian-20-08-caple/ release and a couple of things caught my eye:

includes fix for Armbian bug https://armbian.atlassian.net/browse/AR-282 - which sounds super similar
there is support for Rockchip RK3328 chipset and multiple rock devices, including Rock64 https://www.armbian.com/rock64/

ayufan has been quiet for the last few months, I hope he is OK.
I'm going to try and make time for an Armbian test this week.


Major version bump.

This is probably landing after #863, which removes an options, so that's why it's major.

r? @fitzgen

:pushpin: Commit abc9933 has been approved by fitzgen

@bors-servo r+

I failed hard to update the test expectations in #860, so I'm going to merge this there instead to avoid waiting for double CI.


Update IBMi.ts

removed the dunning msg
Changes
Description of change here.
Checklist

[x] have tested my change
[x] updated relevant documentation
[x] Remove any/all console.logs I added
[x] eslint is not complaining
[x] have added myself to the contributors' list in CONTRIBUTING.md
[x] for feature PRs: PR only includes one feature enhancement.

@worksofliam

@chrjorgensen I have no issues with this personally. What do you think? :D


A lot of repetition in timeline view

Might be worth exploring something like this?

Also spelling out the actual word might be better? months instead of mos, etc.

Yeah, I had an experiment that was very close to that, but I haven't been able to figure out a way to implement it properly. The main issues are ensuring that the first item in the view always has a timestamp and that as time ticks on deal with items that change groupings


Is there a way to focus only on keyboard tab

Is there a way to render out the focus div on the Slide component only on keyboard tab and not on mouse click or touch?

The focus ring is just CSS applied to the Slide component.  You could add your own mouse click and touch event handlers and conditionally add your own css class to the Slide component that hides the focus ring.

Did that work for you?


[Communication] Move core dependency to setup.py from dev_requirements in communication management package

We had this PR  to solve the dependency issue.
However the tests still failing for the scheduled runs of the pipeline. Moving that into setup.py

/azp run python - communication - tests

/azp run python - communication - tests


Feature: Deployment Config

Issue #, if available:
Description of changes:
generator.yaml - CRUD shapes for deployment config are not the same, rename fixes that. Introducing status field pendingdeployment summary which will give user move context over their deployment.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Please add unit tests in a separate PR


docs: Accessibility copy updates

Working in feedback from IBM A, and a broader copy cleanup.

@vpicone I'll add alt tags and remove the snippet stuff 👍

@dakahn do you know where we're getting the "title" attribute guidance for images? Best I can tell, title's are 100% optional and aren't considered an appropriate way to convey info in HTML5: https://www.w3.org/html/wg/wiki/ChangeProposals/ImgElement20091203.
Would want to avoid someone putting any info there that isn't in the alt tag, as it likely wouldn't be available to screen readers.

Like @vpicone said. My understand is that title has no use in images. If I’m understanding our guidelines correctly the text is saying you must use alt and title for accessibility?
“ Use of the title attribute is known to be an unreliable method to visually convey information to users. Refer to Using the HTML title attribute. This is part of the reason why the use of the title attribute to provide a text alternative for an image was deemed non conforming in HTML5”

@aledavila yeah to add on, we're providing a serious footgun here. If the title and alt are the same it's fine, they get a lame little tooltip. BUT, If folks put info in the title tag that isn't in the alt tag, that text isn't accessible to screen readers.
It's also just cumbersome as hell to write.

@connor-leech @aledavila maybe we should open a seperate issue to address the suspect title attribute guidance? Or is that something that we'd want to correct here?

@vpicone It seems like consensus is that we should not be using the title attribute, I think we can address it in this PR.


Exclude some subproject

My project contains deprecated applications. They use old dependecies. I would like to exclude them from syncLibs.

@JanVomlel What do you mean exactly by "exclude"?

Your plugin is applied to root project and generate Libs.kt and Versions.kt from all dependencies in all subprojects. I would like to ignore some subprojects and their dependecies do not add to Libs.kt and Versions.kt.


MusicBot produces error after trying to play music

I run this music bot on a Raspberry Pi and it was working fine. Now after queueing certain songs it produces the following error:
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/usr/local/lib/python3.5/site-packages/youtube_dl/extractor/youtube.py", line 1081, in _decrypt_signature
video_id, player_url, s
File "/usr/local/lib/python3.5/site-packages/youtube_dl/extractor/youtube.py", line 969, in _extract_signature_function
raise ExtractorError('Cannot identify player %r' % player_url)
youtube_dl.utils.ExtractorError: Cannot identify player 'https://www.youtube.com/yts/jsbin/player-vflppxuSE/en_US/base.js'
(caused by ExtractorError("Cannot identify player 'https://www.youtube.com/yts/jsbin/player-vflppxuSE/en_US/base.js'",))
This leads me to believe its opening the java script of certain songs youtube page. I don't know why it does this with some requests and not others but its really annoying. Its out of my limited knowledge on stuff like this to fix it. If you need any other info just ask for it.

#1072


Typo: casual_consistency

casual_consistency should be causal_consistency in the arguments to start_session.

Your help is much appreciated, give me a moment to fix this real quick. Sorry for the typo.


Any medic stuff in the pipeline?

This is god tier hacks for aimbot and other classes, but i main medic and so far medic stuff seems unfinished, I wish the auto vaccinator would work as other hacks, as well as something like auto heal the lowest team mates (on bind would be awesome).
Rest is amazing, thanks all the devs!

I said it before I'll say it again, nullcore before the shitty rewrite had the best auto-vaccinator ever. It had settings to prioritize you or your healing partner, actually predicted if rockets would hit you instead of just "if within Xhu", could quickly flash everyone in a radius if a crit rocket was coming (but only those that would actually die from it (also did this on regular uber)), would spam all bubbles if you were about to die just so your healing target could get all resists even after you die, etc.
Even the auto-kritzkrieg had logic that would pop kritz on your healing target if they saw at least 5 enemies.
Had danger prediction for quickfix/uber based on how many enemies were nearby, auto-pop uber before a backstab, etc.
Then V9 decided he wanted to make nullcore slimmer by getting rid of all of the features... ffs.

@SylveonBottle

Oops

@SylveonBottle
Write me a bullet point list of everything you'd like auto vaccinator to do and there is a 1/50 chance I will look into it when I get home tonight

@SylveonBottle
Write me a bullet point list of everything you'd like auto vaccinator to do and there is a 1/50 chance I will look into it when I get home tonight

Autoheal:
-Setting for prioritizing you, your healing target, or both.
--You: Focuses on protecting you, then your healing target. (good for your own survival at all costs, such as in pubs where the heal target is a random player)
--Target: Focuses on protecting your target first above all else, even at the cost of your own life. (good for botting or pocketing other cheaters)
--Both: Run prediction on whoever has less HP, unless one of us is in Danger. "Danger" consists of things that might kill one of us within a few seconds if not prioritized (e.g. a sniper is looking at you, but heavy is on lower health, we should prioritize us over the heavy since we're the one closest to death).
There's two main reasons to use auto-vaccinator:
-To heal our target (we're a bot account, we're healing a really good player that needs to stay alive at all costs, etc)
-To heal in general (healing random players, healing friends but we still need to stay alive, etc)
If the priority is set to Target, we should prioritize healing them no matter the cost. We should never waste a bullet on ourselves, because it doesn't matter if the medic-bot dies, as long as it keeps the target alive.
If the priority is set to You, we should prioritize ourselves. If we're at full hp, then we can predict both us and the target. If we're not at full hp, we should switch to whatever benefits us the most.
If the priority is set to Both, we should always predict both players.
-Default is always Bullet. This is because we can predict rockets and flares from distances with plenty of time, but bullets are hitscan.
--Option to change this, of course.
-Setting for "minimum pops" for explosive, fire, and bullet. I.e. if you set explosive to 2, auto-vacc won't pop explosive unless you have 3 spare pops. If you only have 2, it won't pop it. This is so we can always have 1 pop incase of snipers.
-Option for "flash others", to quickly switch to other players if they're about to die and pop on them. For example, if a crit rocket is about to hit us, and we're within a group of our teams, we should quickly switch to the player with the lowest health that's about to die and pop Explosive on them, then switch to the next lowest health player, etc. We don't have to pop our orriginal heal target (unless priority is on them) if they're not in any danger of it. This is to prevent the crit rocket from wiping our whole team.
-Switch to bullet (if we aren't already on bullet) if:
--You/Target gets targeted by a sentry (sentry is in range and facing you/target)
--Snipers
---Settings for when to switch:
----Always: Always switch to bullet if there's a sniper is within viewable range/loaded.
----Cheaters Only: Switch to bullet if a Cheater is within range
----On Sight: Switch to bullet if you/target can clearly see the sniper's eyesight.
----On Scope: Switch to bullet if you/target can see the sniper, and the sniper is scoped in (not neccesarily facing us).
----Dangerous: Switch to bullet if you/target can see the sniper, and the sniper is scoped in, and the sniper is facing you/target by ~30 degrees.
----Never: Ignore snipers.
---Peek prediction: Do basic movement simulator on snipers, follow above settings if they're about to come into view.
----Peek Prediction ON + On Scope would, for example, switch to bullet if a sniper is scoped and about to come into view. Perfect for bots.
--A scout/heavy is within X hu
--Projectile prediction says an arrow is about to hit you/target.
-AutoPop bullets:
--Sniper is scoped in, is visible, and is facing you/target.
--If "On Scope" or above is set, and Peek Prediction is on, pop bullet if the cheater/bot is about to come into view. We don't need to pop for peek prediction on legit players, only when they're scoped in, are visible, and are facing us.
--If you/target are within Xhu of a sentry, and it's facing us (we can survive a few bullets from long range, but a close-up sentry is a death sentence).
-Switch to fire if:
--To mitigate afterburn
--A pyro is nearby with primary
--Projectile prediction on flare says it's going to hit us
-AutoPop fire:
--Pyro with crits is within Xhu
--We're low on hp, and the only active threat is a pyro with primary
-Switch to explosive if:
--Projectile prediction on rocket/pill says it's going to hit us (or we're within splash radius)
--We're standing on a sticky bomb
-AutoPop explosive:
--Rocket/pill is going to hit us, and we're low on hp
--Crit rocket/pill, splash
--We're standing on a sticky bomb, and it'll kill us
Priority should be based on what's likely to kill us on the shortest time. So something like:
--Sniper is scoped in, looking at us, is visible, and has a charge enough to kill us in 1 shot
--Crit rocket/pill
--Crit pyro
--A scout/heavy is on us and we're low on hp
--Sentry is facing us
--We're standing on a sticky trap that'll kill us
--Predicted rocket/pill is going to hit us
etc, etc.
Example scenarios:
1: We're healing a heavy. There's a soldier that isn't shooting at us, a demoman throwing sticky bombs at the heavy, and a pyro is getting closer. The heal target is set to Target (prioritize the heavy at all costs).
-Auto-vaccinator should completely ignore the soldier, his rockets aren't touching us.
-Auto-vaccinator should prioritize the demoman, since his stickybombs are dealing damage to the heavy.
-The pyro isn't a threat until he's close. Once he's close, switching to fire WOULD help protect the heavy, but those sticky traps are still the biggest threat.
-If, for whatever reason, a sniper marked scoped in on our heavy at any point in time, we should immediately switch to bullet. If the shot is charged enough to kill the heavy, pop it.
In this scneario, auto-vaccinator should stay on explosive. It should also pop explosive, if the heavy gets too low on hp. Once the demoman is dead, switch to fire. Pop fire if heavy is about to die. Switch back to the soldier if his rockets are suddenly about to hit us.
If both the pyro and the soldier are shooting at the heavy, we should keep on fire resistance, but switch to explosive if a rocket is about to hit.
If the pyro goes for us, auto-vaccinator should completely ignore it, because auto-vaccinator is set to prioritize the target at all costs.
If auto-vaccinator was set to prioritize us, we would stay on bullet since the soldier/demoman isn't a threat to us. Once the pyro is within range, he'd be the biggest threat. If a sticky bomb were to ever land near us, we would prioritize that.
If auto-vaccinator was set to Both, we would focus on healing the heavy until that pyro came for us. We would only switch to fire and pop it if we were low on hp (i.e. heavy isn't attacking the pyro)
2: We're healing our cheating sniper. He's about to peak into a group of enemies of an assortment of classe.
-We should stay on bullet. If there's an enemy sniper, we pop the moment he's within view + scoped in + looking at us. If any enemy sniper is there, and ISN'T looking at us, don't pop since he's not a threat.
-Unless there's a pyro coming around the corner (primary + within range) or we're about to get hit by splash damage, there is no reason to switch off of bullet.
3: We're pub-stomping with random players, priority is set to us.
-We should always switch to whatever it takes to keep us alive over all else.
-If we're at full health, THEN we can prioritize the heal target.
Optional settings:
-Heal Others
--If you/target are already at full health, heal others that are in need of healing.
-Panic flash
--Try to prevent dying with a charge, since it's wasteful. If we're about to die (priority is set to Target and a crit rocket is about to hit us, or we're low on hp and we're about to die), switch and pop damage/explosive/fire on the target as quick as possible, even if it's slightly wasteful. It's still better than dying with all of our charges.
The settings will look like this:
Auto-Vaccinator

AutoHeal [X] // a button
Priority: [You] [Target] [Auto] // a dropdown menu
Heal Others [X]
Flash Others [X]
Snipers: [Always] [Cheaters Only] [On Sight] [On Scope] [Dangerous] [Ignore]
Predict Sniper Peek [X]
Panic flash percent [0 - 99] //if set to 0, it's disabled. otherwise, it's heal percent + projectile prediction
Minimum Pops

Explosive [0 -- 4] // a slider
Fire [0 -- 4]
Bullet [0 -- 4]

https://user-images.githubusercontent.com/36936588/204005486-35229dc4-2d25-4c19-938a-64eeb29af4ca.mp4

The general idea is that we should switch to whatever benefits us the most, and pop whatever might kill us if we don't pop.
We don't need to worry about sticky bombs if their owner is nowhere in sight (since there's little chance for the demo to set them off).
We don't need to worry about pyros if the target is a heavy at full hp (since he can just kill them).
We always need to pop against snipers if they're scoped in on us/target and can kill in one shot.
Etc.

Keep in mind that everything I wrote, nullcore already had before the rewrite. And more. Nullcore had that whole "danger prediction" system that gave a score to all enemy players, and could pop uber/kritz depending on how many dangerous players were within view.

Keep in mind that everything I wrote, nullcore already had before the rewrite. And more. Nullcore had that whole "danger prediction" system that gave a score to all enemy players, and could pop uber/kritz depending on how many dangerous players were within view.

I can think of how to do that fairly easily, each class has a score, set a minimum danger value and if that many people are visible then pop

Though I'm only really thinking of vaccinator for now

No promises on implementing all ur things tho

This is god tier hacks for aimbot and other classes

Where can I find these god tier hacks you're talking about?

Give me phosphor

This is god tier hacks for aimbot and other classes

Where can I find these god tier hacks you're talking about?

Give me spookyballs

Give me phosphor

https://www.curseforge.com/minecraft/mc-mods/phosphor

Give me phosphor

https://www.curseforge.com/minecraft/mc-mods/phosphor

Starlight is better 😡😡😡

well this might never get finished but i have added a function for calculating some of the hitscan danger of an individual player, this still needs to account for sniper stuff. I won't do peek prediction on them as i imagine it would cause more false positives and a significant fps loss (assuming using gamemovement) and for huntsman arrows (inclusive of ping). still need to work on when to actually pop the uber too as at the moment it will just pop if there is any damage. so yeah i havent done much from your big list so far but maybe i will keep working on it :-D

gamemovement is fps friendly

You only need to do peek prediction on snipers that are scoped in. I'm sure there's never more than 3 of those in any game at a time.
And this is only to stop those bots from sniping your target.
I guess you could also run this peek prediction on snipers that are looking directly at you. But if a sniper has their yaw exactly 0 (as most bots do, since they always look straight forward), run it on them too.
if ((player = sniper) && (status = scoped)) {
if (player = looking at us) || (player_yaw = 0) {
peekDetection()
}}

Wow, didn't expect to drum up quite the responses, I'm really glad others share the same interest for Medic.
A few things I'd love to see personally:

Auto vaccinator, the vaccinator switches to the correct resistance type based on threats and incoming bullets to the target, or myself. Auto uber would pop with vaccinator based on threats as well,  so not just switching resistances, but also popping uber in conjunction.
Autoheal but ON A HOTKEY, some cheats basically leverage if the user has aimbot active, and just categorizes this as an aimbot feature, the autoheal snaps on to the players in the users selected FOV, and heals the lowest ones first, and keeps snapping to the next until all players in the FOV are healed. I'd like this on a hotkey, cause I want to only do this sometimes, then switch to healing my friend. This is great for building an uber charge quick. I noticed it has to be done in a silent way, perhaps server sided, because people notice you snapping right away if not.
I would love to have a cham on players on your team if they get low in HP, perhaps your team color overlays the lowest people on your team. It's just an easier indicator to heal those people vs. having to keep track of health bars.
Let team member press X and call for Uber, then pop uber.

Maybe some stuff I've never seen before on Medic, would be awesome. These are just features I'd love to have, and have seen before.
Thanks for your time!

I would love to have a cham on players on your team if they get low in HP, perhaps your team color overlays the lowest people on your team. It's just an easier indicator to heal those people vs. having to keep track of health bars.

ESP on low hp teammates only would be neat for figuring out who needs health, yes.

Let team member press X and call for Uber, then pop uber.

Not everyone presses X then reaches all the way to the number 8 on their keyboard.
Just pop uber if they call for Medic while already at full HP. This is basically them saying "get ready to uber me!"


Get function out of run_all_in_graph_and_eager_mode in gelu tests.

See #1328

@aakashkumarnain
You are owner of some files modified in this pull request.
Would you kindly review the changes whenever you have the time to?
Thank you very much.


Can log configuration be added to the chart?

Currently the chart doesn't allow operating the --log <string> flag which is important to us as we've been waiting for a long time for JSON logging and want to get rid of ngrok parsers ASAP.
Thank you.

I think we can:

[ ] Add conf.logging section with enabled: false/true
[ ] Add configmap from logging section
[ ] Mount it to pods
[ ] Pass file to --log-config-file

More details: https://www.cockroachlabs.com/docs/v21.1/configure-logs

Oh, no, you can't... Because --logtostderr is always applied...


Update enable-and-configure-your-app-for-teams-meetings.md

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/apps-in-teams-meetings/enable-and-configure-your-app-for-teams-meetings.md
90
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/enable-and-configure-your-app-for-teams-meetings.md
:white_check_mark:Succeeded
View

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


Network logging not working

Version: "bugbattle": "^3.3.0",
Using the following to enable network logging does not work.
In the Bugbattle dashboard, the the network logging is not captured and tells you to still enable the logging.

BugBattle.enableNetworkLogger();

@arnoBruynseels thanks for the report! We will take a look into this asap and keep you updated.
Can you confirm that there were also network events happening? It might still show "No network logs" when there were no network events happening (xmlhttprequest or fetch will currently be logged - mostly all major libraries are based on them, so they should also be covered as well).
Thanks for your help!

Yes I can confirm that there were network request happening

@arnoBruynseels thanks for the update. One more question: which library are you using for the network requests?

@boehlerlukas
We use fetch API:
https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API

@arnoBruynseels
We dug into your issue today and tried to reproduce it, but couldn't so far. One of the things that came to our minds was that Bugbattle get's initialized after the network requests are done - this would not work as it's not possible to access already processed requests.
Is there any chance we could get a glimpse into the app, which is missing the network requests? This would help us enormously to dig into the issue and fix it asap.
Thanks for your help! 🤝

@arnoBruynseels i hope you are doing great! Do you have any updates on the network logging issue? Thanks in advance for your help. 💪

@arnoBruynseels we had another deep dive into the issue today and found one possible issue - the issue is fix with the latest version. It would be really great if you could give it another shot and see if the fix works for you.


Add RCT1/AA/LL music source games.

Should be correct, I simply checked every track on my RCT1, AA, and LL discs to see when new tracks were introduced and added source games accordingly.
The only odd ones are the two custom music tracks as they obviously don't come with the game.
But the CUSTOM.TXT file first appeared in LL so as such i added LL as a source game for the custom music tracks.
I don't have an install of RCT1+AA so i can't test to see if custom tracks were first introduced there but CUSTOM.TXT is not present on my AA disc so i'm doubtful they were introduced in AA.

AA indeed does not seem to support custom music.


New version: isaaclevin.presencelight version 5.6.113

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hi @isaacrlevin,

This PR's version number 5.6.113 has 3 parameters (sets of numbers between dots - major, minor, etc), which is less than the current manifest's version <IP_ADDRESS>, which has 4 parameters.

Is this intentional?
(Automated response - build 494)

You can close this, it was an accident

You can close this, it was an accident


Question: Android kernel support?

The documentation says that Linux kernel version 6.4 or above has all the required support patches. I don't have a recent Pixel device on hand to verify right now, but from what I can find online, current Pixel phones come with Linux 5.15, with a possible upgrade to Linux 6.1 on the way. Does the Android Common Kernel have all the relevant patches backported by any chance, and if so, which minimum Android kernel version would you recommend?

Does the Android Common Kernel have all the relevant patches backported by any chance [...]

Not that I'm aware of.
You may get lucky with Linux 6.1. It already includes all patches we listed, except posix-timers: Prefer delivery of signals to the current thread. GWPSan includes code that works around the absence of that last patch, and its absence is less severe performance-wise than all the other patches.
If, on the platform of interest, you are able to run the tests,  and they pass, you can try if using GWPSan works for your usecase performance-wise.

Thank you!


Using module causes Get-Command to incorrectly show using module cmdlets

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
If you create a module that has a using module statement, then when calling Get-Command -Module will cause the module to show the using module cmdlets in addition to its own.
BeforeAll {
    "using module PSReadline" > TestDrive:/Test.psm1
    Import-Module TestDrive:/Test.psm1
}

Describe 'Get-Command' {
    It "Get-Command -Module Test should be empty" {
        Get-Command -Module Test | Select-Object -ExpandProperty Name | Should -BeNullOrEmpty
    }
}

Expected behavior
Test should pass

Actual behavior
Describing Get-Command
  [-] Get-Command -Module Test should be empty 8ms (5ms|3ms)
   Expected $null or empty, but got @('PSConsoleHostReadLine', 'Get-PSReadLineKeyHandler', 'Get-PSReadLineOption', 'Remove-PSReadLineKeyHandler', 'Set-PSReadLineKeyHandler', 'Set-PSReadLineOption').
   at Get-Command -Module Test | Select-Object -ExpandProperty Name | Should -BeNullOrEmpty, C:\Users\Thomas\Documents\PowerShell\Modules\Test\Pester.Tests.ps1:9
   at <ScriptBlock>, C:\Users\Thomas\Documents\PowerShell\Modules\Test\Pester.Tests.ps1:9

Error details
N/A

Environment data
Name                           Value
----                           -----
PSVersion                      7.3.1
PSEdition                      Core
GitCommitId                    7.3.1
OS                             Microsoft Windows 10.0.19044
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

Just to summarize:

I don't know what the design intent was, but, yes, using module invariably imports the targeted module session-globally, causing it to show up in subsequent Get-Module calls.

Only Import-Module offers localizing the import on demand with -Scope Local, but Import-Module lacks the ability to import class definitions from a module.


[5.4] Ask for generating a migration file along with the model

Without this you have to manually run additional
php artisan make:migration create_bars_table

Example

I don't want to go crazy with this kind of stuff.


Production deployments for no-kafka

I am exploring kafka clients for node .
The one we are using currently just isnt working for us (after a lot of wrappers and hooks to restart the client on errors).Are there any large scale prod deployments that are using no-kafka without any babysitting/issues .
no-kafka is relatively new and not listed in -
https://cwiki.apache.org/confluence/display/KAFKA/Clients
so just wanted to ask .

+1
Thanks for asking this question. Even we are looking for some information on this.
Due to lack of production info on Node packages for Kafka we were forced to turn to Confluent's Kafka distribution (v0.10). They have a rest proxy for accessing Kafka over HTTP - which kinda worked for us. It's quite stable but has its learning curve and intricacies.
We would love to go to the native driver of we see more testimonials about production usage - as that would simplify our tech stack.
Regards,
Mohit

On 01-Oct-2016, at 13:40, goodfella1408<EMAIL_ADDRESS>wrote:
I am exploring kafka clients for node .
The one we are using currently just isnt working for us (after a lot of wrappers and hooks to restart the client on errors).Are there any large scale prod deployments that are using no-kafka without any babysitting/issues .
no-kafka is relatively new and not listed in -
https://cwiki.apache.org/confluence/display/KAFKA/Clients
so just wanted to ask .
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi All,
We are using no-kafka lib for only consuming data using group consumers and it is quiet satisfactory for us.
Our objective was to read the data from broker and pass to a function.
We are using 3 machine cluster of kafka
Reading 2 topics with 4 partitions each and deployed 4 consumers(2 for each topic) in total.
Thanks,
Ravi

We've been using no-kafka in production over the last few weeks and having good success! I'd recommend writing a solid little test suite to ensure the library works in your production environment, that helped us iron out some kinks and have the confidence to release.

@raviten , @davidsketchdeck, @oleksiyk
Greetings!
Would you mind sharing your experience working with no-kafka module in production?
Could you please tell me: do you use plaintext protocol for your kafka-consumers, and what is the approximate amount of messages being consumed from topic per second? And whether you use standard consumer settings, or some custom ones?
I am currently having trouble trying to use kafka client written in node.js to consume 3-5k messages from ssl-protected kafka cluster with 3 nodes and  topic which have 3 partitions.
I had no success using node-rdkafka and kafka-node, and ended up using java client, piping out messages to stdout. So, if you have experience working with no-kafka in similar environments or even larger, would you mind sharing?
Looking forward to your reply.


#731 Add @RequiresUnitOfWork annotation

Implementation of a @RequiresUnitOfWork annotation equivalent to the @Transactional annotation. One that will automatically start/stop a UnitOfWork as required, but not begin/commit a transaction. See issue #731 for more info. I think this annotation can be interesting, I have also missed it often.
The name of the annotation is important as it's public, and so can be changed. Please check if you like it and change it accordingly.
This pull request also includes a refactoring of JpaLocalTxnInterceptor class, extracting the management of the unit of work to a new utility UnitOfWorkHandler class, which can also be handy to start / end units of work by code (instead of with annotations). Finally, it also solves issue #753 (JpaLocalTxnInterceptor is inconsistent. It uses both UnitOfWork and JpaPersistService), by using the same UnitOfWork injected object to both begin and finish it.

Hi! Is anyone reviewing the pull requests? This PR is already 6 months old...

Guice is dead?


Is QUIC/HTTP3 access now supported?

I have some projects that require QUIC or HTTP3, but I don't find the option to enable HTTP3 access and the option for SSL certificates in the configuration.

Hey @T-baby 👋
Thank you for the PR but QUIC or HTTP3 is not supported in Robyn atm. We are waiting on this - https://github.com/actix/actix-web/issues/309

Thank you for your helpful answers.


Implement Auto Labeling for Issues

Title:
Implement Auto Labeling for Issues
Description:
This feature aims to automate the process of assigning labels to issues when they are created or edited. The following labels will be automatically added:

gssoc-extd: Marks the issue as part of GSSOC-extended contributions.
hacktoberfest: Marks it as eligible for Hacktoberfest.
level?: A placeholder label indicating the level, which will remain until the project admin assigns the appropriate level during the Pull Request (PR) review.

Tasks:

Create a GitHub Action that listens to issue events (opened, edited).

Automatically assign the following labels:

gssoc-extd
hacktoberfest
level?

Ensure the placeholder label level? remains on the issue until the project admin assigns the final level during the PR stage.

Test the automation by creating and editing issues.

Acceptance Criteria:

[ ] Labels are added to issues automatically upon creation or editing.
[ ] Placeholder label level? is correctly assigned to issues.
[ ] Final level is assigned by the project admin during PR review.

@Harshdev098
Pls assign me this issue and give me level3,hacktoberfest-accepted and gssoc-extd

Not needed because this project will be a part of other programs in future


bpf: nat: let caller determine whether SNATed connection needs CT

Right now this is decided at the lowest level of the SNAT path. But actually the callers know much better. In particular this avoids one case where we bake EgressGW knowledge deep into the SNAT code.

/test

Ah sweet, this also nicely reduces the instruction count for the tail_nodeport_nat_egress_ipv*() paths. That traffic never needs CT, and now the compiler understands that it can eliminate all the CT-related code when it pulls in __snat_v*_nat().

@gentoo-root FYI


Lspsaga show_line_diagnostics not working

Describe the bug
when I try to do "show line diagnostics", it gives me the error.
My config
require("lspsaga").setup({
ui = {
theme = "round",
border = "double",
winblend = 1,
},
-- keybinds for navigation in lspsaga window
scroll_preview = {
scroll_down = "",
scroll_up = "",
},
})

Steps to reproduce
.
Expected behavior
see the diagnostic message of a line
Neovim version (nvim -v)
0.8.2
Operating system/version
macOS 13.1 Ventura
Terminal name/version
kitty 0.26.5
$TERM environment variable
xterm-256color

example codes? I can't reproduce

not working like what

example codes? I can't reproduce

oops.  sorry
I just open a file, find an error, do Lspsaga show_line_diagnostics
and I get the error message above

not working like what

when I source the lspsaga file, it shows the double border, but once I quit and restart the neovim, the border is not showing. probably because of the colorscheme? not sure, I'm new to neovim ..

I'm also experiencing this problem, I think the trick to reproducing it is to cause a diagnostic that spans multiple lines and where its starting column on the first line is greater than the ending column on the last line.
I checked the line mentioned in the screenshot: https://github.com/glepnir/lspsaga.nvim/blob/main/lua/lspsaga/diagnostic.lua#L455
and printed out entry and found the end_col was indeed greater than the start_col but it was a different line.

{
  bufnr = 1,
  code = "redundant-parameter",
  col = 18,
  end_col = 5,
  end_lnum = 50,
  lnum = 9,
  message = "This function expects a maximum of 0 argument(s) but instead it is receiving 1.",
  namespace = 37,
  severity = 2,
  source = "Lua Diagnostics.",
  user_data = {
    lsp = {
      code = "redundant-parameter"
    }
  }
}

an example entry

so that's problem the col > end_col.. which column is wrong ?

I've simplified my code to this:
local M = {}

function M.setup()
    local utils = require("daneharnett.utils")
    local status_ok, lspsaga = pcall(require, "lspsaga")
    if not status_ok then
        return
    end

    lspsaga.setup({
        --
    })
end

The error occurs when I show line diag on lspsaga.setup({ and it doesn't matter which column my cursor is on
echo col(".") echos the current cursor position right?
the entry is... when my cursor is on column 1
{
  bufnr = 1,
  code = "redundant-parameter",
  col = 18,
  end_col = 5,
  end_lnum = 11,
  lnum = 9,
  message = "This function expects a maximum of 0 argument(s) but instead it is receiving 1.",
  namespace = 37,
  severity = 2,
  source = "Lua Diagnostics.",
  user_data = {
    lsp = {
      code = "redundant-parameter"
    }
  }
}

this entry come from vim.diagnostic .so I think something wrong in neovim core..

Yeah I think my lua language server is getting confused and thinks that lspsaga.setup is actually M.setup

FYI
nvim --version
NVIM v0.9.0-dev-4818+gfd3d30a22-dirty
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by <redacted>

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/HEAD-fd3d30a/share/nvim"

Run :checkhealth for more info

just add a patch ......but still don't know why end_col will bigger than col  .

not working like what

when I source the lspsaga file, it shows the double border, but once I quit and restart the neovim, the border is not showing. probably because of the colorscheme? not sure, I'm new to neovim ..

nope.  not relate colorscheme and i test with a min config. borde works fine when i change it in setup function. so there may something wrong in your config.

@glepnir The latest patch has fixed my issue. It's worth noting that all three lines:
lspsaga.setup({
        --
    })

have underlines indicating that there is a diagnostic for the whole range, but Lspsaga show_line_diagnostics will only show something on the first line

can paste the whole entrys and your lua language config .these line is correct looks like.

Whole entrys:
{ {
    bufnr = 1,
    code = "redundant-parameter",
    col = 18,
    end_col = 5,
    end_lnum = 11,
    lnum = 9,
    message = "This function expects a maximum of 0 argument(s) but instead it is receiving 1.",
    namespace = 37,
    severity = 2,
    source = "Lua Diagnostics.",
    user_data = {
      lsp = {
        code = "redundant-parameter"
      }
    }
  } }

lua lsp config
    local runtime_path = vim.split(package.path, ";")
    table.insert(runtime_path, "lua/?.lua")
    table.insert(runtime_path, "lua/?/init.lua")

    lspconfig.sumneko_lua.setup({
        capabilities = capabilities,
        on_attach = on_attach,
        settings = {
            Lua = {
                runtime = {
                    version = "LuaJIT",
                    path = runtime_path,
                },
                diagnostics = {
                    globals = { "vim" },
                },
                workspace = {
                    library = vim.api.nvim_get_runtime_file("", true),
                },
                telemetry = {
                    enable = false,
                },
            },
        },
    })

whole entrys only have one item ..so we can just show that one.  no problem with your lua langserver config. wired .

All good, thanks for the quick fix for the error :)

no problem :) close then.


Use ForkHub account if available

ForkHub creates an account in Android with the GitHub access credentials.
Could this app use those for non-anonymous Gist and Pull Requests?

Since I'm already working on logging in to GitHub via OAuth, I don't think a second application would be necessary. The possibility of saving the response token as an Android account was also taken into consideration, but for now, it will be saved on the shared preferences.
Also, about the non-anonymous Gists, once authentication works, there will probably be a CheckBox stating something like "Anonymous Gist" (which will be disabled if you haven't gone through the OAuth flow).

This can be closed  right?

Someone may want to implement it @gsantner :P
I probably won't implement it myself since there are bigger issues to fix, but if someone wants to, I'll gladly merge.


Enable DNS resolution in sidecar Istio Agent

Describe the feature request
Allowing the sidecar to resolve the application's DNS requests is useful in a variety of scenarios:

in multi-cluster, cross cluster dns resolution will become easier - we will no longer need to create dummy k8s services in a cluster just to get dns resolution
for service entries that do not have a VIP, we can allocate class E addresses (not routable in any network), and have the sidecar resolve the app's requests to these hosts to these addresses. The sidecar can then do proper dns resolution and forward traffic. This split resolution model, with fake VIPs will allow us to eliminate wildcard original dst listeners for tcp services (<IP_ADDRESS>:3306) that have been known to cause incorrect routing (e.g., if we have two mysql aws rds services on same port with resolution set to DNS, the sidecar will incorrectly forward traffic from the second service to the first, as it has only one listener on 3306 that forwards to the host specified by the first service).

This will also eliminate our dependency on the coredns plugin, eliminating the need for users to tinker with their k8s clusters' dns configs to forward to our plugin to resolve .global addresses (in many cases, mesh admins are unwilling/unable to change the cluster setups done by their k8s teams).
A preliminary work was done in https://github.com/istio/istio/pull/24919 and spectacularly failed due to the unstable dns implementation in Envoy. The plan of action is to attempt to do this in istio agent.
See https://docs.google.com/document/d/14g079QxTB0ZydbuYctwLHZfzTYOSOm5sNHxMFyg8FFE/edit for the larger context.
Describe alternatives you've considered
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Additional context

cc

cc

https://github.com/istio/istio/pull/24919 has done this. I think it is not enabled yet

This is complete. It is enabled in preview profile and will be enabled by default in 1.9


[Change] Cleanup the markdown

The markdown of README.md was a bit sloppy, I thought I'd fix it up.

thanks. Did not even catch that someone made a PR.

No problem!


Add ezimuel and joshmock as recipe maintainers

cc @ezimuel @joshmock (I can still merge this PR btw, let me know if this is good for you)

Thanks @sethmlarson


libopus: 1.2.1 -> 1.3

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libopus/versions.
meta.description for libopus is: '"Open, royalty-free, highly versatile audio codec"'.

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.3 with grep in /nix/store/98fnrvcf0r462ra4srd9krrn5vp7sydb-libopus-1.3

directory tree listing: https://gist.github.com/eaf53b65ec9ac40ad48efd4a66111909

du listing: https://gist.github.com/c241559aa73f47413ae4a36b118f0c1e

Outpath report (click to expand)

Outpath difference report
3820 total rebuild paths
1480 package rebuilds
1208 x86_64-linux rebuilds
1073 i686-linux rebuilds
243 x86_64-darwin rebuilds
1296 aarch64-linux rebuilds
First ten rebuilds by attrpath
DisnixWebService
MMA
R
SDL2_mixer
SDL_mixer
_20kly
a2jmidid
aacskeys
abcl
acoustidFingerprinter

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/98fnrvcf0r462ra4srd9krrn5vp7sydb-libopus-1.3 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A libopus https://github.com/r-ryantm/nixpkgs/archive/3a3733e18a5f8a4d32f4e0b8914372eee04f22ec.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/98fnrvcf0r462ra4srd9krrn5vp7sydb-libopus-1.3
ls -la /nix/store/98fnrvcf0r462ra4srd9krrn5vp7sydb-libopus-1.3/bin

cc @wkennington for testing.

Failure on x86_64-darwin (full log)
Attempted: libopus
Partial log (click to expand)
cannot build derivation '/nix/store/z23p6rfcfcvisvqmcncbwxn3gfzvjzc8-mirrors-list.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/bz79jzn6f3f4dgi8q7hklwpmjy19mwh8-perl-5.28.0.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/l08jjzb9a20ipvkh5zhg2kvvkacygc64-pkg-config-0.29.2.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/bf7512yl89ql16hwssjn12frm7vi6ij9-openssl-1.0.2p.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/qncj7560h36bpsjdii558ngvmsg1nyi8-libssh2-1.8.0.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/a7a1c2sqn8vvzq9qm80cxx4w9nr28z70-nghttp2-1.34.0.drv': 7 dependencies couldn't be built
cannot build derivation '/nix/store/a8fbq7p98cwpqx0wqridxfysavvd0qr2-curl-7.61.1.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/qjb91sad3qks2x7nnsmnsqlrmggxrh24-opus-1.3.tar.gz.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/wfcgzdwss3z2ppq1nxhhwck6a0ig99ln-libopus-1.3.drv': 3 dependencies couldn't be built
error: build of '/nix/store/wfcgzdwss3z2ppq1nxhhwck6a0ig99ln-libopus-1.3.drv' failed

Success on x86_64-linux (full log)
Attempted: libopus
Partial log (click to expand)
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/98fnrvcf0r462ra4srd9krrn5vp7sydb-libopus-1.3/lib
patching script interpreter paths in /nix/store/98fnrvcf0r462ra4srd9krrn5vp7sydb-libopus-1.3
checking for references to /build in /nix/store/98fnrvcf0r462ra4srd9krrn5vp7sydb-libopus-1.3...
shrinking RPATHs of ELF executables and libraries in /nix/store/yijda18wnr58isc10c83nqhyqbg6df98-libopus-1.3-dev
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/yijda18wnr58isc10c83nqhyqbg6df98-libopus-1.3-dev/lib
patching script interpreter paths in /nix/store/yijda18wnr58isc10c83nqhyqbg6df98-libopus-1.3-dev
checking for references to /build in /nix/store/yijda18wnr58isc10c83nqhyqbg6df98-libopus-1.3-dev...
/nix/store/98fnrvcf0r462ra4srd9krrn5vp7sydb-libopus-1.3

Success on aarch64-linux (full log)
Attempted: libopus
Partial log (click to expand)
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/vcr80rfjmn992zp2j4q053rx596fr53h-libopus-1.3/lib
patching script interpreter paths in /nix/store/vcr80rfjmn992zp2j4q053rx596fr53h-libopus-1.3
checking for references to /build in /nix/store/vcr80rfjmn992zp2j4q053rx596fr53h-libopus-1.3...
shrinking RPATHs of ELF executables and libraries in /nix/store/7vbz2mnpvc107fiain7j7fq539xax6b5-libopus-1.3-dev
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/7vbz2mnpvc107fiain7j7fq539xax6b5-libopus-1.3-dev/lib
patching script interpreter paths in /nix/store/7vbz2mnpvc107fiain7j7fq539xax6b5-libopus-1.3-dev
checking for references to /build in /nix/store/7vbz2mnpvc107fiain7j7fq539xax6b5-libopus-1.3-dev...
/nix/store/vcr80rfjmn992zp2j4q053rx596fr53h-libopus-1.3

Darwin failure appears to be due to a dependency, I think this is safe to update. Tested and worked fine. Due to it causing mass rebuilds I'm a bit hesitant to push to master, so:
pushed to staging as of d836c6ad5727872d20b53b4519398a7690a02512

@MP2E nixpkgs-update/r-ryantm now picks staging as the target branch of the PR, if there are more than 100 package rebuilds. So it agreed with you to send this to staging! 😁


Support projects with dockerfile

[kind/Feature]
Which functionality do you think we should add?
Allow projects that has a dockerfile to be taken into the inner-loop mode. User should be able to run a command such as odo create --image=<path/to/my/dockerfile. This is a different mode than our current s2i based mode.  As a consequence we need a way to capture the commands to modify the contents of the image.
Why is this needed?
There are many container based applications that has a dockerfile and do not use s2i as their build. This will allow them to use odo to do their inner-loop without making major changes to do s2i based builds.

when using this feature, as we cannot know the variables like DEPLOYMENT_DIR etc that are present when s2i builder images are used and also we dont control the startup commands - Features like smarter push wouldn't work and debug wouldn't work.
Instead of smarter push either odo push --config could happen when only the config is changed or a rebuild with a full source code copy ( if source changes ) could happen.
correct me if I am wrong @kadel

is this something we are still interested in @kadel @gorkem ?

is this something we are still interested in @kadel @gorkem ?

It might take a different form, but yes. This is something that we are still interested in

/remove-lifecycle rotten
/lifecycle frozen


BigQuery connector cannot read credentials

Steps To Reproduce
Ensure you are logged out of the CLI and try to connect to a BQ db and run npm run sources
Environment

evidence version: 24.0.8

Expected Behavior
Connects and runs query
Actual Behaviour

See slack thread
Workaround
Downgrade to 24.0.7

Looks like this was a bug introduced in #1483

I was able to add and run a bigquery source using a json keyfile to connect, unsure if there is another auth method that is failing, but that use-case seems resolved

@ItsMeBrianD are you about to build that using env vars?

ie delete the local creds and run EVIDENCE__BIGQUERY_XXX=xxxxx npm run build


Update build.gradle for jarjar-command

Update build file for jarjar-command to build a working CLI tool

https://github.com/shevek/jarjar/pull/12#issue-332072509

Update build file for jarjar-command to build a working CLI tool


Recommend to update code for compatibility with CASA 6

As correctly noted in the documentation, the code runs with CASA 5 (I tested with CASA 5.6.1-8).  I would strongly recommend to update it for compatibility with CASA 6.
https://casa.nrao.edu/casa_obtaining.shtml
https://github.com/openjournals/joss-reviews/issues/4942

Changes have been implemented in all the codes, and SIMIO-continuum has been updated to work in CASA 5.X and at least in CASA 6.3. The changes in the code are mostly related to going from python2 to python3. A minor change was implemented to make the JvM correction work in v>6. All the changes are internal to the codes, and no changes have been done to the way in which the user uses SIMIO.
I will maintain the recommendation of running it in CASA v<6, where I have tested it the most, but there should not be problems with running in v>6.


Optimize writing Hive tables

Avoid unnessary encoding/decoding when writing VARCHAR columns

Currently, the flow in HivePageSink converts VARCHAR columns from
Slice to String to Text before they get written. We now bypass the
conversion to String by dealing directly with Text objects.
Additionally, we include an optimized version of Hive's columnar SerDe
that avoids a call to get the String value in serialize(), which is only
used to check whether the string is empty.

Avoid unnecessary type equality checks to decide how values should be
extracted from column Blocks.

Instead, build field "setters" and rely on the JVM to do the dispatch.
Also, avoid creating boxed objects for each value that's written.
A test with a table containing 13 varchar and 3 bigint columns showed
a reduction in CPU utilization of ~34%.

Looks good


Changes corresponding to PS version 1.2.12

@effingerw , may I know what the "changes corresponding to 1.2.12" are? We don't have a 1.2.12 version now, and may not have it for the next month or two. Can we sit together and review all these changes you have in this PR?

sure i will ping you offline


until there is an auth plan tls testing should support insecure

Over on https://github.com/containerd/cri/pull/681 we added support to containerd/cri and expected that critools would support tls without auth.  However, the following error occurs when attempt to run validation:
Mar 19 20:49:18.310: INFO: Unexpected error occurred: error sending request: Post https://<IP_ADDRESS>:10010/attach/Vy2abuwM: x509: certificate signed by unknown authority
This commit relaxes the certificate requirement on the server, before an encrypted stream can be started from crictl and critest validate.
We should probably discuss, and/or open an issue to discuss, security requirements for streaming for the CRI API.
@Random-Liu
Signed-off-by: Mike Brown<EMAIL_ADDRESS>

Discussed with @tallclair, today the behavior of streaming authentication is not defined in CRI yet. And at least apiserver on GCE doesn't actually validate the certificate. I think it makes sense to skip the certificate validation in CRI validation test for now, until this is well-defined in CRI.
/lgtm

LGTM


vb_run_benchmarks.py not installed?

Hi,
I installed vbench from git as of https://github.com/wesm/vbench/commit/fb0132f4d8944323de112c273c8c0d06648935ac using:
export PYTHONPATH="/home/pjcock/lib/python2.6/site-packages/"
python2.6 setup.py install --prefix=$HOME
As far as I can tell, vb_run_benchmarks.py is not getting installed under $HOME/bin nor $HOME/lib - meaning when I try to use vbench (using an example based on https://github.com/wesm/pandas/blob/5d4bf8febdad007d7804c2e91c5bead01ca92637/vb_suite/benchmarks.py but for another project), it fails with errors like this:
python vb_run_benchmarks.py /tmp/vbench/benchmarks.pickle /tmp/vbench/results.pickle
stdout:
python: can't open file 'vb_run_benchmarks.py': [Errno 2] No such file or directory
I have tried putting symlinks to vb_run_benchmarks.py on my path, in the current directory, and in the temp directory used to run the benchmarks, but to no avail.

It needs to be added to setup.py as a data directory. I've been using vbench with python setupegg.py develop which you might consider also. obviously need to fix things so the lib can be installed

Added the scripts directory to the setup.py build


[regression] export * from 'typescript/lib/typescript.d throws after 2.19.0

related: https://github.com/alexgorbatchev/eslint-import-resolver-typescript/issues/47
Minimal reproduction:
// test.ts
export * from 'typescript/lib/typescript.d'

# .eslint.yml
parserOptions:
  ecmaVersion: 2020
  sourceType: module
extends:
  - plugin:import/errors
  - plugin:import/typescript

run: eslint test.ts
error log:
TypeError: Cannot read property 'type' of null
Occurred while linting /workspace/eslint-import-resolver-typescript-repro/src.ts:1
    at /workspace/eslint-import-resolver-typescript-repro/node_modules/eslint-plugin-import/lib/ExportMap.js:569:30
    at Array.forEach (<anonymous>)
    at /workspace/eslint-import-resolver-typescript-repro/node_modules/eslint-plugin-import/lib/ExportMap.js:565:32
    at Array.forEach (<anonymous>)
    at /workspace/eslint-import-resolver-typescript-repro/node_modules/eslint-plugin-import/lib/ExportMap.js:563:19
    at Array.forEach (<anonymous>)
    at Function.ExportMap.parse (/workspace/eslint-import-resolver-typescript-repro/node_modules/eslint-plugin-import/lib/ExportMap.js:477:12)
    at Function.ExportMap.for (/workspace/eslint-import-resolver-typescript-repro/node_modules/eslint-plugin-import/lib/ExportMap.js:361:25)
    at Function.ExportMap.get (/workspace/eslint-import-resolver-typescript-repro/node_modules/eslint-plugin-import/lib/ExportMap.js:316:23)
    at processBodyStatement (/workspace/eslint-import-resolver-typescript-repro/node_modules/eslint-plugin-import/lib/rules/namespace.js:67:47)

After downgrading to ~2.18.2, there will be no error any more.

If it's throwing from inside the resolver, that's a bug you'll need to file on the resolver, which is a different project.
cc @alexgorbatchev

@ljharb Not at all. There's no resolver used in my reproduction.
The related issue throws because the resolver resolves typescript.d.ts correctly instead of typescript.js.

Hmm, I did misunderstand the stack trace - but the resolver is still the typescript resolver, which is a different package.
What's the exact stack trace on v2.20.2, the latest version?

@ljharb All versions after v2.19.0.

Right, but i need the file and line number on v2.20.2.

What's the exact stack trace on v2.20.2, the latest version?

Yes, I tested it with latest version.

Test seems to pass on latest master.

@ljharb I try to build latest eslint-plugin-import from master branch manually, but the error is still there.
$ /Users/JounQin/Workspaces/Local/eslint-import-issue/node_modules/.bin/eslint test.ts

Oops! Something went wrong! :(

ESLint: 7.2.0

TypeError: Cannot read property 'type' of null
Occurred while linting /Users/JounQin/Workspaces/Local/eslint-import-issue/test.ts:1
    at /Users/JounQin/Workspaces/Local/eslint-plugin-import/lib/ExportMap.js:616:33
    at Array.forEach (<anonymous>)
    at /Users/JounQin/Workspaces/Local/eslint-plugin-import/lib/ExportMap.js:611:28
    at Array.forEach (<anonymous>)
    at /Users/JounQin/Workspaces/Local/eslint-plugin-import/lib/ExportMap.js:606:21
    at Array.forEach (<anonymous>)
    at Function.ExportMap.parse (/Users/JounQin/Workspaces/Local/eslint-plugin-import/lib/ExportMap.js:501:12)
    at Function.ExportMap.for (/Users/JounQin/Workspaces/Local/eslint-plugin-import/lib/ExportMap.js:369:25)
    at Function.ExportMap.get (/Users/JounQin/Workspaces/Local/eslint-plugin-import/lib/ExportMap.js:324:23)
    at ExportAllDeclaration (/Users/JounQin/Workspaces/Local/eslint-plugin-import/lib/rules/export.js:125:51)

@ljharb The minimal reproduction would be like following:
// file1.ts
declare namespace ts {
  const x: string;
  export { x };
}

export = ts;

// file2.ts
export * from './file1.ts'

run eslint file2.ts
I print moduleBlockNode at https://github.com/benmosher/eslint-plugin-import/blob/master/src/ExportMap.js#L593, it is:
{
  "type": "ExportNamedDeclaration",
  "source": null,
  "specifiers": [
    {
      "type": "ExportSpecifier",
      "local": {
        "type": "Identifier",
        "name": "x",
        "range": [
          53,
          54
        ],
        "loc": {
          "start": {
            "line": 3,
            "column": 11
          },
          "end": {
            "line": 3,
            "column": 12
          }
        }
      },
      "exported": {
        "type": "Identifier",
        "name": "x",
        "range": [
          53,
          54
        ],
        "loc": {
          "start": {
            "line": 3,
            "column": 11
          },
          "end": {
            "line": 3,
            "column": 12
          }
        }
      },
      "range": [
        53,
        54
      ],
      "loc": {
        "start": {
          "line": 3,
          "column": 11
        },
        "end": {
          "line": 3,
          "column": 12
        }
      }
    }
  ],
  "exportKind": "value",
  "declaration": null,
  "range": [
    44,
    57
  ],
  "loc": {
    "start": {
      "line": 3,
      "column": 2
    },
    "end": {
      "line": 3,
      "column": 15
    }
  }
}

Thank you, got a properly failing test case with a proper fix :-)


Check for ChakraHub git note during build and copy it to config.json if present

This change is part of the logic to support starting crawler (and eventually full cirro) jobs from ChakraHub.  The user client (ChakraHub or chub) attaches a git note containing cirro configuration settings, represented as a JSON string, to the full commit; pre_build.ps1 detects that note and copies it into a known location for a VSTS release definition (still under development) to find and process.

@dotnet-bot
test OSX static_osx_osx_debug please
test OSX static_osx_osx_release please
test OSX static_osx_osx_test please
test Ubuntu shared_ubuntu_linux_test please

@dotnet-bot test OSX static_osx_osx_debug please

@dotnet-bot test OSX static_osx_osx_debug please


dispatch error while scitype on an SentinelArray which is used by CSV.jl

julia> using MLJScientificTypes, SentinelArrays

julia> b =SentinelArray([1,2,3,4])
4-element SentinelArray{Int64,1,Int64,Missing,Array{Int64,1}}:
 1
 2
 3
 4

julia> scitype(b)
Unknown

julia> scitype(b, MLJScientificTypes.ScientificTypes.convention())
Unknown

julia> scitype(b, MLJScientificTypes.ScientificTypes.convention(), Val(trait(b)))
AbstractArray{Union{Missing, Count},1}

I thinking this is a julia bug. Making a small tweak to the code resolves the issue but i can't seem to understand why this is an issue in the first place.
@ablaom , @tlienart thoughts??

This issue has been fixed in the recent julia 1.5.1 patch release.
julia> using MLJScientificTypes, SentinelArrays

julia> b =SentinelArray([1,2,3,4])
4-element SentinelArray{Int64,1,Int64,Missing,Array{Int64,1}}:
 1
 2
 3
 4

julia> scitype(b)
AbstractArray{Union{Missing, Count},1}

julia> scitype(b, MLJScientificTypes.ScientificTypes.convention())
AbstractArray{Union{Missing, Count},1}

julia> scitype(b, MLJScientificTypes.ScientificTypes.convention(), Val(trait(b)))
AbstractArray{Union{Missing, Count},1}

closing this. Since it's been resolved


Fix generated mod.rs to pass cargo fmt -- --check

Currently, the generated mod.rs does not pass cargo fmt -- --check, and this becomes a problem when ppl choose to include generated files as part of source code.
This PR tries to make rustfmt happy by adding an empty line after each 'pub mod' import.  It also adds This file is generated by line to make mod.rs consistent with other files.
This closes https://github.com/stepancheg/rust-protobuf/issues/621

Thanks!


Multi view camera rendering settings

How to set such a scene: https://wuminye.github.io/NHR/datasets.html

This is a relatively common schematic diagram in the current multi-view research field (such as NeRF), and I hope to add a class of such an example.

The primitives can be corresponding images, or cameras like: https://www-users.cse.umn.edu/~hspark/CSci5980/csci5980_3dvision.html

if you have the individual images and orientations in space you can create
pict1 = Picture("pic1.jpg")
pict1.orientation(pic1_vector)
pict1.pos(pic1_position)
...

In addition, can I define a structure that contains an image and a wireframe model of the camera, and then treat this as a whole and place it somewhere and set the orientation?

You can use an Assembly object to treat multiple objects as a single one:
from vedo import *

pic = Picture(dataurl + "images/dog.jpg")
dz = 800
x0, x1, y0, y1, _, _ = pic.bounds()
cam = [(x0 + x1) / 2, (y0 + y1) / 2, dz]

lines = Lines(
    [
        [cam, (x0, y0, 0)],
        [cam, (x1, y0, 0)],
        [cam, (x0, y1, 0)],
        [cam, (x1, y1, 0)],
    ],
    c="black",
    lw=2,
)

assem = Assembly([pic, lines, Point(cam)])
assem.orientation([0, -1, 0])

show(assem, axes=1)

How to access the four corners of Picture, I do not find in picture.py and base.py?

You can do it with
print(assem.unpack(0).bounds())

Emm, Bounds and Corner are different if I do some transformations like:
pic.origin((1, 2, 2))
pic.orientation((0.2, -0.1, 0.3))

so I wonder if there are any ready-made functions that can be used.

You should transform the  assem obj not the pic.
I suggest not to use orientation() as it's ignoring origin() (bug).
and also there is another small bug about obj.transform to being filled for pure rotations...
from vedo import *

settings.use_depth_peeling = True

pic = Picture(dataurl + "images/dog.jpg")
dz = 800
x0, x1, y0, y1, _, _ = pic.bounds()
cam = [(x0 + x1) / 2, (y0 + y1) / 2, dz]

lines = Lines(
    [
        [cam, (x0, y0, 0)],
        [cam, (x1, y0, 0)],
        [cam, (x0, y1, 0)],
        [cam, (x1, y1, 0)],
    ],
    c="black",
    lw=2,
)

corners = Points([(x0, y0), (x1,y0), (x0,y1), (x1,y1)])

assem = Assembly([corners, pic, lines, Point(cam)])
#assem.orientation([1, -1, -2]) # do not use

assem.origin(cam)
assem.rotate_y(90)
assem.rotate_z(-70)
assem.rotate_y(-90)

# T = assem.transform  # not filled (bug), workaround:
T = assem.GetMatrix()

corner_pts = corners.clone().apply_transform(T).points()
print(corner_pts)

show(assem, axes=1)

Got it.

...also it's probably easier if you use around to define a pivoting point instead of origin:

assem.rotate_y(+90, around=cam)
assem.rotate_z(-90, around=cam)
assem.rotate_y(-90, around=cam)

# instead of:
# assem.origin(cam)
# assem.rotate_y(+90)
# assem.rotate_z(-90)
# assem.rotate_y(-90)

to make the cam the pivoting point.
I must see if there is a more intuitive/natural way for the API as these rotations are a bit tricky...

How to handle this boundary when I turn to the back?

sorry I don't understand the question.

When I scale this down to around 1, the image plane and the line will penetration:
Note the four corners:

from vedo import *

settings.use_depth_peeling = True

pic = Picture(dataurl + "images/dog.jpg")
dz = -1000
if True:
    dz = -0.05
    dim = pic.dimensions()
    pic = pic.scale(2 / np.max(dim) * 0.1)
x0, x1, y0, y1, _, _ = pic.bounds()
cam = [(x0 + x1) / 2, (y0 + y1) / 2, dz]

lines = Lines(
    [
        [cam, (x0, y0, 0)],
        [cam, (x1, y0, 0)],
        [cam, (x0, y1, 0)],
        [cam, (x1, y1, 0)],
    ],
    c="black",
    lw=1.2,
)

assem = Assembly([pic, lines])
assem.origin(cam)
show(assem, axes=0)

I think this is a problem with vtk that has been solved in vtk9.2.2, so I would try:
pip install vtk -U

After the upgrade, I still have this problem on my side. But I can use a larger scale to temporarily circumvent this problem.


FIXFix update hash func array

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

check the ut status？

run beut


Refine .Rprofile to remove unnecessary printing in R startup message.

What problem did you solve?
An uncessary [1] TRUE is printed at startup if user runs R: Create R terminal, which is caused by local(...) in R/.Rprofile returning a logical value visibly.
(If you have)Screenshot

(If you do not have screenshot) How can I check this pull request?

Create R terminal
[1] TRUE should not appear in the startup message.

Thanks!