Add warn dialogs when user sets some option which may cause higher data consumption

Add warn dialogs with explanation when user sets some app settings option which may cause higher data consumption. Affected options:

"New notifications check period" set to value lower than 60 minutes
"Check over WiFi only" disabled
"Better read detection" enabled
"Load notification detail" enabled
"Show Labels" enabled

Dialogs should be shown only once per option when user is on Setting screen and changes the option back and forth. Should be shown again later.

I'm just curious, where does this concern about data consumption come from? I saw several open issues here about it and before that I was genuinely surprised when I saw "a bit higher resource consumption" warning on every setting. I thought "well, it's kind of obvious, but if it warns you, probably it really does something extra?", which means that these notes make more impression on the user than they should.

Dialogs should be shown only once per option when user is on Setting screen and changes the option back and forth. Should be shown again later.

Honestly, I think this is too much. Just from the UX point of view. Additional dialogs are annoying.
On one hand care about user's data consumption is good and having granular settings for it is great. But on another hand, if walk into a candy store to buy some candies, I don't want to be warned about sugar consumption every time I choose a candy: that's what I came for. I'm using this application dedicated to delivering Github notifications to stay connected (that's what notifications are about, right?), so I want to get notified and if I miss some important notification because of too restrictive default settings, I will be upset and think that this application hasn't delivered what it's made for.

I have 1 star review from user who has very high consumpion. And it also happen to my friend, his monthly data plan was wasted by this app (he has about 3500 unread botifications ;-) So I'm trying to introduce some safety for these cases. It is not easy to balance.

Maybe instead of this I should implement some mechanism which monitors data consumption by the app (not sure if android provides api to get this info) and warns user if it is too high during some time period.

I have 1 star review from user who had very high consumpion. And it also happened to my friend, his monthly data plan was wasted by this app (he has about 3500 unread notifications ;-)

It sounds a bit suspicious for a notification app.. It shouldn't consume much. Probably it's requesting more data than it needs? Could you point me to the code where it fetches notifications?

Problem is that github notifications REST API v3 is really bad. It sends lots of informations for each notification, most of them unusable. And some other info (like status of issue or PR related to the notification) is missing so separate request must be performed to obtain it.
One thing I want to investigste now is if this REST API supports gzip compression on wire and use this if yes

Most code is in UnreadNotificationsService

Github notifications api supports asking for new notifications only. I use this for background check, but I must do full load from time to time to remove notifications read on other devices, as they are not in difs

Yeah, I see. I just thought whether you actually do incremental queries or every time run full retrieval for some fixed period of time..
GraphQL API would solve the issue with the exact data you want to get, so it's a pity that it's not available for notifications/events.


Update to new interface

Updating the module to use the new brunch promise based interface.  Also converted the coffeescript to plain .js (this seems to be preferred by the brunch authors own plugins).
Updated the dependencies and added .travis.yml.

Wow. This is really great. Thank you!
Would you like to add your name somewhere?

Hi Ryan,
I think before merging it I should probably update the readme to highlight the fact that this will work with brunch >= 2.0.0 and node >=4.0.0.  A mention in the contributors would be appreciated.
Thanks,
Kenley

@rcs I have added the version information to the README.md.


behavior: closing multi-point shapes

Currently when you move/create last point close to the first (~10px), we auto-close the shape. This is not a real point merge, the two points are still retained separately.
This has following behavior:

It creates a sharp corner:

During edit, moving one of the terminal points does not move the other one:

Both of these could be considered bugs or features.
For example, (1) is good for creating shapes like the above heart. But it's bad for creating other shapes where you want to make all corners round.
(1) can be "fixed" by physically merging the two points instead of just overlaying them across one another, but we'd then lose the ability for sharp corner. Or it can be fixed by implementing a separate "fully-round" sharpness option as suggested by @dai-shi.
(2) can be good for disconnecting the two shapes, but bad when you try to move them both. On the whole I think (2) should be fixed, and the ability to disconnect would be done simply by deleting the point. If we don't want physically merging, we can just dynamically move both points when moving one of them.

This might be out of the scope of this issue, but for me it's somewhat related.
Eventually, we may want to support any combination of sharp and round corners.
For example, a rectangle with two sharp corners and two round corners.

I can't think of any good UI for this though, except for something like bezier handles.

I agree it'd a nice feature. That said, it may fall under the category of "too advanced, won't implement".
One way to do it without bezier handles is to have per-point configs ala Figma. It'd like be part of a floating menu if we ever get to implement that.

Makes sense. Thanks for the clarification.
Me:

we'd stick with import-only svg path (not editable).

👉 #1924

TIL that I can overlap the first and last points to "close" a shape. Yay!!! 😄
...300 ms later...
Wait, I can't move them as one or make them smooth/round? 😢
But, but, but, how do all those custom shapes do it?
...4.2 min later...

Bummer. 😭

@timcolson how do you feel about https://github.com/excalidraw/excalidraw/issues/4359?

#4359 is intriguing! Essentially it is "closing" a shape, if fill color is set.
(FYI - Acorn appears to take this approach too. But it also can truly "close" the last points

Today, I realized how two "rounded" edges in Excalidraw, placed super close, form a sharp edge. (ex. tip of the heart).
I also learned that ...

all points in a shape are either round or sharp.
edges cannot be added to built-in shapes. (ex. start with rect, pull out one more edge to make a pentagon)

I appreciate the creativity of #4359. Backwards compatibility could be problematic. I imagine many surprises, and not the good kind, for existing diagrams.
TL;DR - I don't know that #4359 would solve my need to have "all rounded" for a custom shape.
I experimented with drawing filled, rounded shapes in other tools: Acorn, Inkscape, Omnigraffle, and Figma.
A common approach requires each point to be part of a Bezier path, controlled individually. Handles can make the point rounded or angular.
For quick, rough drawings, and collaboration, Excalidraw has no equal! For this specific use case, one of the more complex tools seems a better fit for now. I look forward to seeing how closed shapes evolve in Excalidraw! Thx!


Using with Intel RealSense T265

1.) Has any one used T265 with VINS Fusion
2.) Which is the convenient way calibrating T265 for VINS Fusion (like using Kalibr), if atall required.

Yes. look here: reference, which is only written in Chinese and even I do not understand what the author says.

But thanks to few English words, I found that he used Kalibr with omni-radtan models for T265 stereo fisheye cameras.
and used it with MEI camera model in .yaml file.

@sumitsarkar1
Hi. If you are still interested in operating VINS Fusion with T265,
I tested it recently following the steps I mentioned above.
Here is the result clip: https://youtu.be/8w86LeB6fns

Great work !! can you share the yaml file and one more querry...does VINS-Fisheye allow map saving or can we do it through ROS. Sorry I am just a beginner in ROS !!

@sumitsarkar1 yaml files can be found at this repo's other branch (T265 branch): https://github.com/engcang/vins-application/tree/Intel-T265
Map saving is not supported in VINS-Fusion nor VINS-Fisheye as far as I know.
Lots of works were made to save the map and reuse it within ORB-SLAM2 frame works, you have to check that.

Thnx for the infos....ya map saving is lots of work...I tried it once !!!...do you know any repo for ORB_SLAM2 which allows map saving

@sumitsarkar1
Check out my other repo: https://github.com/engcang/orb-slam2-modified
check the mal_local branch, I forked the map saving ORB-SLAM2 there.


Stuck with no progress on Update

I'm trying to get a planet import to do an osmosis update, but it appears to freeze after processing nodes, ways, and relations. Looking at the database, the only active query is - COPY "place" FROM STDIN. According to my server stats I can see that the query is using tons of disk IO at 200-400MB a second. Still, I have let it run for over 2 days, and the osmosis import showed no updates on progress. I tried using the latest osm2pgsql version from master, as well as updating Nominatim from 3.5.1 to 3.5.2. Am I missing something? Thanks!
sudo docker exec -it nominatim sudo -u postgres ./src/build/utils/update.php --verbose --import-osmosis --osm2pgsql-cache 22000
Currently at sequence 2928 (17/09/2020 23:58:04) - 1 indexed
'/usr/local/bin/pyosmium-get-changes' --server 'https://planet.openstreetmap.org/replication/day' --outfile '/app/src/build/osmosischange.osc' --size 20 '--start-id' 2928
'/app/src/build/osm2pgsql/osm2pgsql' --hstore --latlong --append --slim '--number-processes' 1 --cache 22000 --output gazetteer --style '/app/src/settings/import-full.style' --database nominatim --port 5432 '/app/src/build/osmosischange.osc'
osm2pgsql version 1.2.0 (v3.5.2)

Allocating memory for dense node cache
Allocating dense node cache in one big chunk
Allocating memory for sparse node cache
Sharing dense sparse
Node-cache: cache=22000MB, maxblocks=352000*65536, allocation method=11
Mid: pgsql, cache=22000
Parsing gazetteer style file '/app/src/settings/import-full.style'.
Using projection SRS 4326 (Latlong)

Reading in file: /app/src/build/osmosischange.osc
Using XML parser.
Processing: Node(3588k 66.4k/s) Way(831k 16.62k/s) Relation(12342 726.0/s)  parse time: 121s
Node stats: total(3588852), max(7921640261) in 54s
Way stats: total(831818), max(849053464) in 50s
Relation stats: total(12342), max(11643024) in 17s

Duplicate of https://github.com/mediagis/nominatim-docker/issues/146 where the maintainer of Nominatim and osm2pgsql answered.

The check_import_finished.php script at the end of init seemed to indicate that everything was ok, but after running it again it stated that indexes were missing.  After running "--index --create-search-indices --create-country-names --index-noanalyse" two more times, the check_import_finished.php script finally said that all indices were good.


Adding NSG's for custom vnet

PR Summary
Adding in additional nsg definitions for when AKSC is deploying a custom virtual network.
This was done by deleting the specific AppGwNsg file and creating a single more parameter driven file that can deploy an NSG. EG. Both an Application Gateway subnet and a Bastion subnet that have very specific rules that are checked on association with a subnet.
PR Checklist

[x] PR has a meaningful title
[x] Summarized changes
[x] This PR is ready to merge and is not Work in Progress
[x] Link to a filed issue

As discussed, pulled the enablePrivateClusterPublicFQDN param from this branch

Tested on a standard AKS

Added UI for the 2 params

Ok - this looks good.


Backup-DbaDatabase: Switching from break/continue to Stop-Function

Type of Change

[x] Bug fix (non-breaking change, fixes #3784)
[ ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Fixing improper error handling that disrupts script execution
Approach
Replacing break/continue with Stop-Function
Commands to test
& {
  Backup-DbaDatabase -SqlInstance 'localhost,12345' -Database nonexisting -backupfilename '\\myfilename\bak.bak'
  Write-Host "This will now appear on screen"
}

Screenshots

Learning

oh. right. return. I forgot how to powershell.
-Continue are all there though.

I maybe overthinking this, but is it needed at all to pass all the -EnableException $EnableException into Stop-Function? Or they will be implicitly used from the parent function due to having the same variable name? If so, I'll add that too.

you do not need to pass it, it's inherited 👍  I'm so sorry I didn't notice your Continues! Please do use -Continue or it'll stop too soon if you pass in multiples. For instance, if you pass in 3 servers and cant access the first, it wont attempt the second or third.

I made sure that all the loops are covered by Continue (and non-loops are not). Codecov is throwing a tantrum because of the Azure tests. Do you guys need more negative testing on this? I can add something while I'm at it.

@nvarscar - no, it often throws a tantrum, even if you have a PR that's 100% tests. We ignore it for now ;) Thank you for your contribution! Other tests pass, will merge.


Values undefined on page load causing error

This causes an error when username/password attempt to be accessed. To resolve, I've defaulted the param to an empty object.

Hi @samalbert, thanks for the contribution.
I can't actually reproduce this issue - what user are you using?

I ran into this as well. Not sure why it is not consistently reproducible, but I've definitely hit the "Cannot access property 'username' of undefined" when logging in as "user" / "pass"

Hi Seth & Chris - I'm wondering if this is a redux extension for chrome.  I will run some tests tonight.

On Jul 10, 2016, at 6:47 PM, Chris Bond<EMAIL_ADDRESS>wrote:
I ran into this as well. Not sure why it is not consistently reproducible, but I've definitely hit the "Cannot access property 'username' of undefined" when logging in as "user" / "pass"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hey @SethDavenport I'm actually no longer able to reproduce this with the latest commits to the repo.  I'm wondering if it was a package version thing (I see a bunch of stuff was updated since June 28th - most notably awesome-typescript-loader).
Here's a screenshot of the error when I had it a few days ago.

Anyways, going to close, but will let you know if I see it again. Thanks for the awesome starter repo :)


Clarification of hipMallocManaged memory placement (GPU or CPU on Frontier/Crusher)

Hello
I was reading the OLCF documentation of Frontier/Crusher systems and got confused by section "HSA_XNACK=0 Automatic Page Migration Disabled" on page https://docs.olcf.ornl.gov/systems/crusher_quick_start_guide.html#notable-differences-between-summit-and-crusher
Second line of the table says that hipMallocManaged() initially allocates on CPU DDR4, and then CPU accesses are "Zero copy read/write over Infinity Fabric" while GPU accesses are "Local read/write". Wait, migration is disabled in this case so memory won't ever move to GPU HBM. Hence GPU access shouldn't be "local read/write" but rather "Zero copy read/write over Infinity Fabric" (and the contrary of CPU access).
Or is the memory initially allocated on GPU when using hipMallocManaged() ?
Thanks
Brice

@bgoglin Internal ticket has been created to provide clarification? Thanks!

@ppanchad-amd Thanks, can you post some clarification here in the meantime?


Multiple windows per room

This is again a feature that seems to be overlooked with the different Tado plugins (e.g. also the one from lukasroegner):
I have multiple rooms with two or even more windows, these rooms also have one or more thermostats. Almost all windows have contact sensors to detect open windows. What is missing in the plugin is the ability to link these sensors to the heating control so that it shuts down once ANY of the windows gets opened. Since the sensor would turn the window open switch on and off depending on the window state, it could happen that two windows get opened (switch off, switch off) and when one window is closed (switch on), the heating is turned back on although the other window is still open.
I had implemented a solution for the plugin from lukasroegner (see https://github.com/ma-ku/homebridge-tado-smart-thermostat/tree/feature/SensorSwitrches) that allowed adding an arbitrary number of windows/sensors to a zone. Each would have been connected with the window sensor (quite tedious work) to detect an open window. The plugin then used the information to determine the overall window open state applied for the zone.
Maybe this is already possible with that plugin then I would like to learn how that is accomplished, otherwise I would offer my help to implement a similar solution for this plugin.

Not pretty, but the problem can be solved with Homekit automations - two automations for every window sensor in the room:

Automation to turn the heating off when window opened (no further conditions)
Automation to turn the heating on - with the additional conditon(s) that every other window sensor in the room has to be in the closed state.

I have also added a virtual „heating master switch“ (with homebridge-dummy) that I turn off in the summer. Add that as further condition to all the window sensors and you ensure the heating stays off in summer.
As this platform‘s delay functionality is broken I have also added virtual delay switches to delay the heating turning off if a window/door is only open for a short time, but that adds another automation.

I have checked that option and it would work with one caveat; the naming of the open window switches is too long and gets truncated in HK so that I cannot distinguish between the different rooms. @seydx: is there a way to change the naming. I would leave out the name of the Home (at least).
Another remark would be that these ‚advanced‘ rules can only be edited with another tool such as Controller for HomeKit and not with the stock application.

I have checked that option and it would work with one caveat; the naming of the open window switches is too long and gets truncated in HK so that I cannot distinguish between the different rooms. @seydx: is there a way to change the naming. I would leave out the name of the Home (at least).
Another remark would be that these ‚advanced‘ rules can only be edited with another tool such as Controller for HomeKit and not with the stock application.

I have 2 HomeKit scenes for every room (zone in tado speak): one for heating on and one for heating off
Then I set the respective scene when windows open or close. I don’t have any problem with long names that way, and there’s no problem setting it up with the stock Home app.

But it becomes an issue if you have more rooms and no way to distinguish the switches:

And even the details do not help:

But it becomes an issue if you have more rooms and no way to distinguish the switches:

you can rename HomeKit devices in the Home app and give them shorter names, no need to stick with the longish default names from Homebridge. Just tap the gear symbol on the lower right of that device’s screen.
All my tado devices are called „Heating“, in every room the same, that way Siri makes less mistakes when I tell her „set heating to  in “. She should know there’s only one heating device (tado zone) in a room, no matter the name, but she can be dense.

Well, I know that I can rename things but I already do not know which room these switches belong to because that information is already truncated. That‘s really the essence of my request.

Well, I know that I can rename things but I already do not know which room these switches belong to because that information is already truncated. That‘s really the essence of my request.

I don’t understand. The names get synced from your tado account, so should be as you set them in the tado app?!

Make it a large tile and you’ll see more of the nameSent from my iPhoneOn 8 Oct 2022, at 12:25, Mathias Kühn @.***> wrote:
Well, I know that I can rename things but I already do not know which room these switches belong to because that information is already truncated. That‘s really the essence of my request.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

I realized that the zone is not even part of the name. So you get <home.name> + ' Open Window'` for each zone. All these switches are grouped into one service so you can combine them into one control in the Apple Home application or you can keep them separately. So from that perspective I have not found any way to associate a switch with its zone.
However, the solution for me was to toggle a switch and look at the HomeBridge logs. There you could then see which zone was affected and this helped me renaming the switches. Hopefully this is not wrecked by some update on the HomeBridge side as I would need to reconfigure everything again.


auto_source: add Scraper for JSON responses (limited to GET requests)

handle scenario when the response is a jsonfeed.
When scraping a non-jsonfeed JSON, the non-semantic HTML extractor can use some commonly used [class] names:

[ ] card,
[ ] headline, title,
[ ] link, url, permalink, href,
[ ] hero,
[ ] teaser, description, excerpt, summary, abstract,
[ ] categories,

Example sites:

https://indieappsales.com/indieappsales/banner/app-list.json

Another example: https://www.iwm.org.uk/visits/iwm-london/whats-on?field_event_type=Exhibitions
Calls a link inside like this.


Unable to overwrite github_app.pr_commands

I'm using the Hosted PR-Agent service and I'm trying to overwrite github_app.pr_commands by using <REPO_ROOT>/.pr_agent.toml. There is information https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#github-app-automatic-tools which say that you can set pr_commands to [] to cancel the automatic run of all tools. However that doesn't seem to work.
The file itself does work because I have successfully changed inline_code_comments.
The config section itself is, which is copied from https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L71
[github_app]
# these toggles allows running the github app from custom deployments
bot_user = "github-actions[bot]"
override_deployment_type = true
# in some deployments it's possible to get duplicate requests if the handling is long,
# these settings are used to avoid handling duplicate requests.
duplicate_requests_cache = false
duplicate_requests_cache_ttl = 60  # in seconds
# settings for "pull_request" event
handle_pr_actions = ['opened', 'reopened', 'ready_for_review', 'review_requested']
pr_commands = []

But it still runs both /auto_review and /describe for every PR it creates.

Or did i do something wrong? Or is it perhaps not possible for Hosted PR-Agent?

I think this is the same problem that I wrote about here https://github.com/Codium-ai/pr-agent/issues/247

@realDragonium i think its a parsing issue.
try setting:
pr_commands = ""
instead

Thanks for the quick reaction!
Changing pr_commands = [] -> pr_commands = "" didn't resolve the issue. Opening a pull request will still trigger the 'default' pr_commands  of auto_review and describe .... Even if you change it to pr_commands = ["/auto_review"], it will still run both.

I think this is the same problem that I wrote about here 247

It might be! Could it be possible that Codium's Hosted PR-Agent is running on an older version which doesn't contain the fix for that?

@realDragonium can you try once more ? (following https://github.com/Codium-ai/pr-agent/pull/374)

Yes! Sorry for the delayed response but it works. Thanks!
pr_commands = [] also works just fine!


SwitchInput.labelSide prop ignored if input within compact toolbar

Label always on the left for switchInputs within a desktop toolbar with compact:true - looks like it's due to use of flexbox for alignment:
https://github.com/xh/hoist-react/blob/b06c39a5dec04a28f8d7e4c386a797e90cc0d372/desktop/cmp/toolbar/Toolbar.scss#L158

Having trouble reproducing this.  Do you have an example you could share?


Memory allocation with CPU-only

In #788 there's some talk about how to configure XLA memory usage with GPUs -- in particular, with the environment variables described in this page.
Are there similar configuration options when using only CPUs?
I tried setting XLA_PYTHON_CLIENT_ALLOCATOR=platform to see if this option carries over to CPU-only mode, but it doesn't get rid of the memory allocation request errors that I'm getting, such as:
Execution of replica 0 failed: Resource exhausted: Failed to allocate request for 321.75MiB (337385120B) on device ordinal 0

Only thing that seems to help so far is increasing the amount of memory available to my job (far beyond what it ends up using), which isn't ideal.

I realized I never followed on up this. In case anyone else has a similar issue with memory-profiler, I ended up finding that the builtin resource module did a better job of measuring memory usage here:
resource.getrusage(resource.RUSAGE_SELF).ru_maxrss

My actual memory issue ended up being me misunderstanding memory usage of vmap vs. lax.map. (Looks like this will be clarified in #2940!)


Adding Apple Watch Target breaks build process - linker fails - framework not found flutter

Adding an Apple Watch Target to an existing flutter app seems to break the build process.
Steps to reproduce:

`flutter create -i swift myapp
Open Workspace in Xcode and go to FILE -> NEW -> TARGET. This window will pop. Select the watchOS tab and the Watch App for iOS app
Try to build the App go to PRODUCT --> Build

Xcode Output:
`Build target test Extension of project Runner with configuration Debug
Ld /Users/testuser/Library/Developer/Xcode/DerivedData/Runner-bhuykkivgygfqsdffhvxctzpbxtz/Build/Products/Debug-watchsimulator/test\ Extension.appex/test\ Extension normal i386 (in target 'test Extension' from project 'Runner')
cd /Users/testuser/git/myapp/ios
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -target i386-apple-watchos6.2-simulator -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/WatchSimulator.platform/Developer/SDKs/WatchSimulator6.2.sdk -L/Users/testuser/Library/Developer/Xcode/DerivedData/Runner-bhuykkivgygfqsdffhvxctzpbxtz/Build/Products/Debug-watchsimulator -F/Users/testuser/Library/Developer/Xcode/DerivedData/Runner-bhuykkivgygfqsdffhvxctzpbxtz/Build/Products/Debug-watchsimulator -filelist /Users/testuser/Library/Developer/Xcode/DerivedData/Runner-bhuykkivgygfqsdffhvxctzpbxtz/Build/Intermediates.noindex/Runner.build/Debug-watchsimulator/test\ Extension.build/Objects-normal/i386/test\ Extension.LinkFileList -Xlinker -rpath -Xlinker @executable_path/Frameworks -Xlinker -rpath -Xlinker @executable_path/../../Frameworks -dead_strip -Xlinker -object_path_lto -Xlinker /Users/testuser/Library/Developer/Xcode/DerivedData/Runner-bhuykkivgygfqsdffhvxctzpbxtz/Build/Intermediates.noindex/Runner.build/Debug-watchsimulator/test\ Extension.build/Objects-normal/i386/test\ Extension_lto.o -Xlinker -export_dynamic -Xlinker -no_deduplicate -Xlinker -objc_abi_version -Xlinker 2 -fapplication-extension -fobjc-link-runtime -L/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/watchsimulator -L/usr/lib/swift -Xlinker -add_ast_path -Xlinker /Users/testuser/Library/Developer/Xcode/DerivedData/Runner-bhuykkivgygfqsdffhvxctzpbxtz/Build/Intermediates.noindex/Runner.build/Debug-watchsimulator/test\ Extension.build/Objects-normal/i386/test_Extension.swiftmodule -framework Flutter -e _WKExtensionMain -framework WatchKit -Xlinker -sectcreate -Xlinker __TEXT -Xlinker __entitlements -Xlinker /Users/testuser/Library/Developer/Xcode/DerivedData/Runner-bhuykkivgygfqsdffhvxctzpbxtz/Build/Intermediates.noindex/Runner.build/Debug-watchsimulator/test\ Extension.build/test\ Extension.appex-Simulated.xcent -Xlinker -dependency_info -Xlinker /Users/testuser/Library/Developer/Xcode/DerivedData/Runner-bhuykkivgygfqsdffhvxctzpbxtz/Build/Intermediates.noindex/Runner.build/Debug-watchsimulator/test\ Extension.build/Objects-normal/i386/test\ Extension_dependency_info.dat -o /Users/testuser/Library/Developer/Xcode/DerivedData/Runner-bhuykkivgygfqsdffhvxctzpbxtz/Build/Products/Debug-watchsimulator/test\ Extension.appex/test\ Extension
ld: framework not found Flutter
clang: error: linker command failed with exit code 1 (use -v to see invocation)
`
Flutter Doctor Output
[✓] Flutter (Channel stable, v1.17.5, on Mac OS X 10.15.5 19F101, locale de-DE)
[✗] Android toolchain - develop for Android devices
✗ Unable to locate Android SDK.
Install Android Studio from:
https://developer.android.com/studio/index.html
On first launch it will assist you in installing the Android SDK
components.
(or visit https://flutter.dev/docs/get-started/install/macos#android-setup
for detailed instructions).
If the Android SDK has been installed to a custom location, set
ANDROID_SDK_ROOT to that location.
You may also want to add it to your PATH environment variable.
[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
[!] Android Studio (not installed)
[!] IntelliJ IDEA Community Edition (version 2017.3.3)
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
[!] VS Code (version 1.46.0)
✗ Flutter extension not installed; install from
https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (1 available)

Hi @ElreboCM
Can you upgrade to beta and try again
flutter channel dev
flutter upgrade --force
flutter doctor -v
Related https://github.com/flutter/flutter/issues/61566 https://github.com/flutter/flutter/pull/51126
Thank you

I tried and the error is still the same.
flutter doctor -v output:
[✓] Flutter (Channel dev, 1.21.0-1.0.pre, on Mac OS X 10.15.5 19F101, locale
de-DE)
• Flutter version 1.21.0-1.0.pre at /Users/testuser/flutter
• Framework revision f25bd9c55c (9 days ago), 2020-07-14 20:26:01 -0400
• Engine revision 99c2b3a245
• Dart version 2.9.0 (build 2.9.0-21.0.dev 20bf2fcf56)
[✗] Android toolchain - develop for Android devices
✗ Unable to locate Android SDK.
Install Android Studio from:
https://developer.android.com/studio/index.html
On first launch it will assist you in installing the Android SDK
components.
(or visit https://flutter.dev/docs/get-started/install/macos#android-setup
for detailed instructions).
If the Android SDK has been installed to a custom location, set
ANDROID_SDK_ROOT to that location.
You may also want to add it to your PATH environment variable.
[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.6, Build version 11E708
• CocoaPods version 1.9.3
[!] Android Studio (not installed)
• Android Studio not found; download from
https://developer.android.com/studio/index.html
(or visit https://flutter.dev/docs/get-started/install/macos#android-setup
for detailed instructions).
[!] IntelliJ IDEA Community Edition (version 2017.3.3)
• IntelliJ at /Applications/IntelliJ IDEA CE.app
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
• For information about installing plugins, see
https://flutter.dev/intellij-setup/#installing-the-plugins
[!] VS Code (version 1.46.0)
• VS Code at /Applications/Visual Studio Code.app/Contents
✗ Flutter extension not installed; install from
https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (1 available)
• Apple Watch Series 5 - 44mm (mobile) •
CD8D6C82-DFE9-473B-87CF-1852888897B6 • ios •
com.apple.CoreSimulator.SimRuntime.watchOS-6-2 (unsupported) (simulator)
! Doctor found issues in 4 categories.

I deleted and created the app again.
The error seems to be gone now.
I will do further testing with an existing flutter app (not the sample app).

I tried it again with an existing app that uses flutter_blue.
I am receiving now the similar error with the difference that flutter_blue is not found
Ld /Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Products/Debug-watchsimulator/WatchApp\ Extension.appex/WatchApp\ Extension normal i386 (in target 'WatchApp Extension' from project 'Runner')
    cd /Users/testuser/git/wibike_app/ios
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -target i386-apple-watchos6.2-simulator -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/WatchSimulator.platform/Developer/SDKs/WatchSimulator6.2.sdk -L/Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Products/Debug-watchsimulator -F/Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Products/Debug-watchsimulator -F/Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Products/Debug-watchsimulator/Protobuf -F/Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Products/Debug-watchsimulator/flutter_blue -F/Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Products/Debug-watchsimulator/path_provider -F/Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Products/Debug-watchsimulator/shared_preferences -F/Users/testuser/git/wibike_app/ios/Pods/../Flutter -filelist /Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Intermediates.noindex/Runner.build/Debug-watchsimulator/WatchApp\ Extension.build/Objects-normal/i386/WatchApp\ Extension.LinkFileList -Xlinker -rpath -Xlinker @executable_path/Frameworks -Xlinker -rpath -Xlinker @loader_path/Frameworks -Xlinker -rpath -Xlinker @executable_path/Frameworks -Xlinker -rpath -Xlinker @executable_path/../../Frameworks -dead_strip -Xlinker -object_path_lto -Xlinker /Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Intermediates.noindex/Runner.build/Debug-watchsimulator/WatchApp\ Extension.build/Objects-normal/i386/WatchApp\ Extension_lto.o -Xlinker -export_dynamic -Xlinker -no_deduplicate -Xlinker -objc_abi_version -Xlinker 2 -fapplication-extension -fobjc-link-runtime -L/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/watchsimulator -L/usr/lib/swift -Xlinker -add_ast_path -Xlinker /Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Intermediates.noindex/Runner.build/Debug-watchsimulator/WatchApp\ Extension.build/Objects-normal/i386/WatchApp_Extension.swiftmodule -framework CoreBluetooth -framework Flutter -framework flutter_blue -framework path_provider -framework protobuf -framework shared_preferences -framework Flutter -e _WKExtensionMain -framework WatchKit -Xlinker -sectcreate -Xlinker __TEXT -Xlinker __entitlements -Xlinker /Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Intermediates.noindex/Runner.build/Debug-watchsimulator/WatchApp\ Extension.build/WatchApp\ Extension.appex-Simulated.xcent -Xlinker -dependency_info -Xlinker /Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Intermediates.noindex/Runner.build/Debug-watchsimulator/WatchApp\ Extension.build/Objects-normal/i386/WatchApp\ Extension_dependency_info.dat -o /Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Products/Debug-watchsimulator/WatchApp\ Extension.appex/WatchApp\ Extension

ld: warning: directory not found for option '-F/Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Products/Debug-watchsimulator/Protobuf'
ld: warning: directory not found for option '-F/Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Products/Debug-watchsimulator/flutter_blue'
ld: warning: directory not found for option '-F/Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Products/Debug-watchsimulator/path_provider'
ld: warning: directory not found for option '-F/Users/testuser/Library/Developer/Xcode/DerivedData/Runner-cmosbmuzrhohkqgvplroxwvhnmoo/Build/Products/Debug-watchsimulator/shared_preferences'
ld: framework not found flutter_blue
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I cannot 100% trace it back what actually caused the problem for me.
However, doing a pod repo update appears to have solved the problem for me.

Hi @ElreboCM
Since the issue isn't reproducible, given your last message I feel safe to close this issue, if you disagree please write in the comments and I will reopen it.
Thank you


New notebook.experimental.remoteSave setting isn't registered

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.80.1
OS Version: Windows 11 / Ubuntu 20.04 LTS

Based on the change log of version 1.80 (changelog), a new option for enabling the improved notebook saving method should be available. However, this option is not appearing in the settings user interface.
Additionally, when I manually add notebook.experimental.remoteSave to the setting.json file, I receive an error message stating "Unknown Configuration Setting."

Already fixed in Insiders by https://github.com/microsoft/vscode/pull/187189

The setting ought to work on 1.80 even though it gets reported as unknown.

Should be a valid setting now in Insiders.


Remove static BufferId

This fixes the tsan errors in the "correct" way, and undoes the previous changes in https://github.com/Xilinx/mlir-air/pull/410
The code in this PR is not pretty, I can try and

be consistent with camelCase vs CamelCase
remove the "const uint64_t dummy" hacks, which were required to keep the 'getBuffer' APIs aligned as they're used in a template function. I can use template SFINAE to make this better (maybe...)
Pass the parameter BufferId later in the function signature (I've stolen position #0 to make it easier to deal with methods with default parameters)

The thing is that each instance of the AIRToAIEPass must have its own version of BufferID, otherwise there are multithreading issues.

@nirvedh I can't add you as an air reviewer, but this is the "revert" of the mutex approach


Hide Device

homeassistant:
  customize:
    device_tracker.iPhone:
      hidden: true

Having this in my config I would expect this iPhone to be hidden but it is present in the main view.

Are you on the dev or master branch?

If you go to the states developer tool (the icon in the middle):
a. Does the device_tracker.iphone entity exists?
b. If you click on it, does it have hidden in the attributes?

Yea, I've been using the master branch. The states developer tool actually hides it if I manually enter it in. Yes device_tracker.iphone does exist. Hidden attributes are nowhere to be found when you click on a device card.

A couple quick thoughts:

Entity ID's should be all lower case. So try putting in
device_tracker.iphone.
The Hidden attribute is not on the device cards by design. It is only
included in the device attributes if it is True. This way, the user
interface doesn't show details that aren't particularly important.

Ryan Kraus
On Tue, Jun 2, 2015 at 3:03 AM, Stephen Way<EMAIL_ADDRESS>wrote:

Yea, I've been using the master branch. The states developer tool actually
hides it if I manually enter it in. Yes device_tracker.iphone does exist.
Hidden attributes are nowhere to be found when you click on a device card.
—
Reply to this email directly or view it on GitHub
https://github.com/balloob/home-assistant/issues/162#issuecomment-107832986
.

The device_tracker doesn't use the entity class so can currently not be influenced by the customize configuration option. I've added this to my to do list to refactor. Thanks for noticing.

The fix for this has made it to the master branch and was released in version 0.7.0.


Feat/use checks api

As discussed in #822, this adds support for GitHub’s new Checks API.
🚨 Before this can work, Greenkeeper needs to request additional permissions from the app installers, namely read-only access to Checks. Updating these permissions will trigger an email to all users.
Changes

Most of jobs/github-event/status.js now lives in lib/on-branch-status.js. jobs/github-event/status.js and the new jobs/github-event/check_suite/completed.js now only receive the status and check events and everything beyond that happens in lib/on-branch-status.js: we try to fetch combined statuses first (as before), then get all checks for that ref, consolidate everything and pass it on down to whatever else needs the info. Note that we’re basically overloading the combined status object with the info from checks as well, and then adapting the recipients of this object (it’s actually only content/fail-issue.js) to deal with the different kinds of objects (statuses and checks) that can now be found in the combined.statuses array.

Features

Supports checks via the check_suite completed event. Every check state that isn’t success or neutral makes the ref non-passing for Greenkeeper.
Disables repos when they’re archived. Does not re-enable repos when they’re unarchived, this still requires a reset.

The new status details section would look like this:

We’ll have to see whether we can improve that, since there are now 7 states, not just ❌ and ✅


Brazilian Portuguese Version

Hi, I'd like to create a pt-br version. What do you think about create another .md file like "style-guide-pt-BR.md"?

That's great to hear @guylhermetabosa! As discussed on #13, it's easier to keep the translations in separate forks. So you can just fork the project, replace README.md with the translated version and ping me here to add a link to it, in the first paragraph.

Nice, I'll do that. Thanks for the feedback!

This is my pt-br version https://github.com/guylhermetabosa/git-style-guide


Allow :name parameter for an InventoryCollection

Allow :name parameter for an InventoryCollection, name can be
used instead of :association, when we do not want to provide
the association. Name is used to uniquely identify the IC
under a specific Persister.
Adding a constraint requiring the name.

@pkliczewski this should show a nice exception, when there is :association missing

@miq-bot assign @agrare

@miq-bot add_label enhancement

@durandom adding @name attr, so we can easily filter out the ICs


Connects to the Feedback Service constantly

This is in RAPNS 1.0.2.
I know this is a recent addition, and perhaps I need to configure something differently, but this is what I'm seeing in my rapns logs:
[2012-01-13 13:22:34] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:23:34] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:24:34] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:25:34] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:26:35] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:27:35] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:28:35] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:29:35] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:30:36] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:31:36] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:32:36] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:33:37] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:34:37] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:35:37] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:36:37] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:37:38] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:38:38] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:39:39] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:40:39] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:41:39] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:42:39] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:43:39] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:44:40] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:45:40] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:46:40] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:47:40] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:48:41] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:49:41] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:50:41] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:51:41] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:52:42] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:53:42] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:54:42] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:55:42] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:56:43] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:57:43] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:58:43] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 13:59:44] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 14:00:44] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 14:01:44] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 14:02:44] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 14:03:45] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 14:04:45] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
[2012-01-13 14:05:45] [FeedbackReceiver] Connected to feedback.push.apple.com:2196
It seems to be connecting to the feedback service several times a second.

Umm.. looks like every 60 seconds to me, which is the default.

/headdesk
Sorry, I need to learn to read :)


Specified source for NuGet

Related to this: https://github.com/umbraco/Umbraco-CMS/pull/7089
If you have an internal nugetpackagesource specified (like I have) and NuGet cannot connect to that packagesource you'll get an error message that it cannot connect (for example; if you're outside of your company network).
Of course Umbraco does not need that source, but someway it still fails... Now I've added the correct sources to the different files.

And this issue is related: https://github.com/umbraco/Umbraco-CMS/issues/7090

Thanks again @JeffreyPerplex - this has now been deployed and should be available in a few minutes, really lovely fix that took me way too long to merge! 🙈

No problemo! Was afraid that you didn't have access to this repo :)...


⚠ ClamAV has degraded performance

In 8d6ee38, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in 763b724.


'var' is declared but its value is never read false-positive

Bug Report
🔎 Search Terms
Nullish coalescing assignment
declared but its value is never read
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about Nullish coalescing assignment

⏯ Playground Link
Playground link with relevant code
💻 Code

class A {
  private x?: number;

  public foo(): void {
    this.x ??= setTimeout(() => {});
  }
}

🙁 Actual behavior
There is an error that 'x' is declared but its value is never read which is not true because ??= reads and then writes the value.
🙂 Expected behavior
No error on x.

Ah, sorry, you're better at searching for issues than me! :smile:

I have many years of practice, and I've seen most reoccurring issues on this repository several times already.


PythonParser and HiredisParser don't use connection encoding kwarg

Given the following code:
client = redis.Redis(host='localhost', charset='utf-8')
client.set('copyright-string', u'Copyright \xa9 2012')
cached_val = client.get('copyright-string')
print 'type=%s' % type(cached_val).__name__
print 'val=%s'  % repr(cached_val)

I expected to get back:
type=unicode
val=u'Copyright \xa9 2012'

Instead, using either HiredisParser or PythonParser, values saved as unicode using charset='utf-8', get returned as str:
type=str
val='Copyright \xc2\xa9 2012'

This is probably what most people expect. However, it will be a backwards incompatible change for people who are doing the response.decode() in their application code.
It's probably time to start a 2.6 release anyway. Sounds like this will be the first change in there. I'll try to find some time later today to push this in.
Thanks!


Define basic database abstraction layer

Define and implement the set of functions that the postgres database provider implements
I'm doing this generally using interfaces to make it easy to write a mocking database interface for testing other components
Closes #13

I've defined the basic interface I'm going to write functions to, so I'm going to move on to implementation. If anyone does have strong opinions on database scheme, I think now would be the best time to express

can we just merge this now?
we’ve been spinning on this, and i feel like it’d be more useful to change it later when writing the application code that uses it, rather than try to speculate what would be useful

Oh, maybe I've misunderstood - my intention was for this pr to contain the postgres implementation (which I'm currently working on), as well as tests of its behaviour

Oh amazing. A postgres layer would be very useful at this point. Didn't realize that was in the works (i think this is my fault for messing up standup).

Having spoken with Mila irl yesterday and seen your pr approval, I'm happy with the actual interface definition if you want to merge this in now and then I'll do the postgres implementation as another pr


NtReadVirtualMemory, error

Environment is Windows 10 + Kaspersky Total Security.
NtReadVirtualMemory, status: 0xc0000022
If you need the environment, here is the download link
https://trial.s.kaspersky-labs.com/registered/vvzkph9ftg3ws2zhfhll/3436353730347c44454c7c32_26155/kts<IP_ADDRESS>1abzh-Hans_26155.exe

Appreciate it, but if nanodump can't to read LSASS while kaspersky is used, that is not an issue on nanodump, as there is nothing to fix. I will take a look though.
If there is a bypass to whatever protection kaspersky uses, PRs are welcome.


Morning session week5 JS

Hey @Azonkeu
your code looks perfectly fine. you did a great job. nothing to say :1st_place_medal:
cheers, Happy coding :rocket:

Hello @Azonkeu, I can see you have done a great job implementing the fetch API, especially the UI... like wow!!👏


[REQUEST] git push --force

We usually use git commit --amend, which we have to make a git push force. That's something quite common.
I think that should be used quite often and I actually see the need.

You can use the custom commands feature to get this. You can read more about it here

Good. What I meant thought is that it should be available by default heh

👍 for making it an easy accessible default. 200+ people at our company use this workflow of amending/rebasing and force pushing.
For what it's worth i use this alias from the command line to be explicit that i push the current branch name to a remote branch with the same name:
alias forcepush='git push --force-with-lease origin $(git_branch_name):$(git_branch_name)'

@akonwi  Are you against implementing this?
I couldn't get the custom command to work :[
All I did was change the example to be 'push --force-with-lease'
Neither that nor the example verbatim show up in the palette, and I made sure that "Custom Commands" was checked

@xenithorb Amending a commit is less destructive than force pushing. It's a useful feature with some and a dangerous feature for others. I also force push and I do it via the run command to enforce me to be intentional.
If force pushing was to be implemented in this package, it should be behind a configuration option so users have the chance to opt-in. I'll try to do this soon but if someone else wants to create a pull request, please be my guest.
@xenithorb As far as your init script, you don't need two onDidActivateInitialPackages calls. You can do everything in one block like so
atom.packages.onDidActivateInitialPackages (p) ->
  if gitPlus = atom.packages.getActivePackage('git-plus')?.mainModule.provideService()
    gitPlus.registerCommand 'atom-text-editor', 'custom-git-commands:undo-last-commit', ->
    gitPlus.getRepo()
    .then (repo) ->
      gitPlus.run(repo, 'reset HEAD~1')

    gitPlus.registerCommand 'atom-text-editor', 'custom-git-commands:push-force', ->
    gitPlus.getRepo()
    .then (repo) ->
      gitPlus.run(repo, 'push --force-with-lease')

Making this an opt-in feature makes sense to me. 👍  You should know what you're doing before you use it, but it's a workflow that 200+ devs in my company have adopted to keep a nice clean history that is as "flat" as possible.


Add access function for restoration state of alerting rule

Add access function for restoration state of alerting rule

@qinxx108

@roidelapluie

Thanks!


Watch Services and Metallb Endpoints

Problem Statement
The Gateway controller creates the service exposing the DataPlane and (when running with Metallb) an endpoint. The Gateway controller should watch these two resources to reconcile the Gateway and enforce them whenever they may change.
Acceptance Criteria

[ ] The Gateway controller watches the Gateway Service and the Endpoint
[ ] An integration test that deletes them should check the expected resources are enforced.

Hi @mlavacca can I work on this one I have never setup blixt project on kind cluster will test on kind first (the setup part) and then write the code to watch for endpoint resource, will add the IT afterwards .

Hi @mlavacca actually not able to assign it to myself can you please assign it to me.

Getting this error in local setup running in kind cluster can you please help
kubectl logs blixt-dataplane-7vvtb -n blixt-system
error: Found argument 'eth0' which wasn't expected, or isn't valid in this context

USAGE:
    blixt-dataplane [OPTIONS]

For more information try --help

Getting this error in local setup running in kind cluster can you please help
kubectl logs blixt-dataplane-7vvtb -n blixt-system
error: Found argument 'eth0' which wasn't expected, or isn't valid in this context

USAGE:
    blixt-dataplane [OPTIONS]

For more information try --help

The problem is that you're using the latest image. In main right now we're iteratively re-writing the dataplane in Rust so the latest image is broken in the meantime. Try changing the image to this:
ghcr.io/kong/blixt-dataplane@sha256:8d37ce022e289cd4235423844d858555573b6338e8f84c4ec65d3e32db132ff3

That's the most recent build of the Go version and should accept the argument and stop failing.
In general though the dataplane shouldn't be needed for certain kinds of controlplane work to move forward: you can just turn the dataplane off for now and focus on the controlplane logic such as updating the Service here.

Ohhk got it thanks for the info :+1:

Do we need to set gateway as an owner of endpoint resource

Do we need to set gateway as an owner of endpoint resource

No, and as I'm reading back over this issue it's a bit confusing. I've significantly simplified the acceptance criteria for now to make this a nice small change focused on one thing, let me know what you think.
At some point here we're going to want to start thinking about integration tests. I'm happy to do the groundwork for that so that we can test things like this, but let me know if you have any interest in trying to get the integration tests wired up to test these changes.

So can we use envtest here setup integration testing infra

Hi @Rahul-D78, are you still working on this one?

Hey @mlavacca @shaneutt sorry for the delay I have raised a PR for Intregration test scaffolding using envtest please review thanks.

@shaneutt, the gateway controller already watches the service that exposes the Gateway, it looks like this issue is already fixed. I'm not sure it makes sense to keep this one open if the issue's goal is moved to scaffolding integration tests. WDYT?

Sure, let's close this and the test scaffolding can be a separate endeavor :+1:


Is it possible or not to replace the specific targeted part of the request body or response? similar to the section on "Query Param."

Instead of replacing the entire content, Is it possible or not to replace the specific targeted part of the request body or response? similar to the section on "Query Param."
For example:
//old
{
  "text": "abc123"
}

//new (Replace the specific targeted portion of the content.)
{
  "text": "test"
}

@chalitguza Thank you for requesting this feature
Version 1.0.59 has a new feature.
It is possible to modify the response dynamically.


Update YouTube terms in ytdl tag

The YouTube Terms of Service have been updated a bit since March 14, 2020 when they were last edited in the ytdl tag. (They were last changed March 17, 2021 according to the site.)
Specifically, it looks like we need to fix the wording in restrictions 1 and 3.
https://github.com/python-discord/bot/blob/eeacceae01b95e39eaeecab2fd14f6edfb19b94b/bot/resources/tags/ytdl.md
I'm happy to tackle this one really quick once it's assigned to me. :)

Sounds good @bsoyka, thanks!


upd tests.yaml files for preset containers

Description
Update tests.yaml files with user: root
Changes Made
The command groupadd -g 109 render creates a new group called render with the Group ID 109.  Some tests failed because the RENDER group set inside the container (109) mismatches with the RENDER group of the runner. As workaround, some test need to be run as root user

@jafraustro it seems that we are missing the group ID change from your last PR. Is that on purpose?
Please update your branch also.

@jafraustro it seems that we are missing the group ID change from your last PR. Is that on purpose?
Please update your branch also.

Thanks Tyler, GID variable is added

due to memory issue integration tests are failing Jaime validated it locally


[BEAM-6001] Fix DATE - INTERVAL and test DATE +/- INTERVAL.

Fix DATE - INTERVAL
Test DATE +/- INTERVAL.

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

Thanks!


Unexpected error for class using a combination of "keyof", generics and unions

Bug Report
🔎 Search Terms
keyof,  generic, union
🕗 Version & Regression Information
Occurs in version 4.5.4, and this is the only version I have tried.
⏯ Playground Link
https://www.typescriptlang.org/play?#code/C4TwDgpgBAqlC8UDeBDAXFADAXygH2XSgEZsAoMgYwBsUBnOqAIQHsAPAHgDUoI3gIAOwAmjGAD5kZKFABuAfgwBrCCBYAzKF2lRKLQXWAAnAK6VgLIwApZGLgEpk5cmWoRgUAEYZWnCQihBCAB3ZnYrVAxSezIgA
💻 Code
type U = {a: 0} | {a: 1}

class Box<V extends U> {
  v?: keyof V
  constructor(v: V) {}
}

let b: Box<U> = new Box({a: 1})

🙁 Actual behavior
When trying to assign new Box({a: 1}) to Box<U> this error occurs:
Type 'Box<{ a: 1; }>' is not assignable to type 'Box<U>'.
  Type 'U' is not assignable to type '{ a: 1; }'.
    Type '{ a: 0; }' is not assignable to type '{ a: 1; }'.
      Types of property 'a' are incompatible.
        Type '0' is not assignable to type '1'.(2322)

This error does not occur if the line v?: keyof V is removed.
🙂 Expected behavior
The code should not produce an error, and typeof b.v should equal "a".

This is a correct error.
type U = {a: 0} | {a: 1}

class Box<V extends U> {
  v?: keyof V
  constructor(v: V) {}
  do_set(m: keyof V) {
    this.v = m;
  }
  do_get() {
    return this.v!;
  }
}

const j = new Box({a: 1, b: 2});
j.do_set("b");

// Alleged: this is OK
let b: Box<U> = j;
// Unsound: value 'b' inhabits 'a'
const a: "a" = b.do_get();

Gotcha, thank you for correcting my misunderstanding.


Adjust commit sha on the comments footer

Check the bottom of the docs reporter comment, eg: https://github.com/TBD54566975/tbdex-js/pull/40#issuecomment-1745867724

In the above one it's saying Commit: cf8aa7, but this commit should be the head of the PR in the moment of the comment submission (right after the docs-reporter run), in the above case it should be 4012ae7.
Somehow it's picking up a dangling sha.

Fixed within #87
Right here: https://github.com/TBD54566975/tbdocs/pull/87/files#diff-aab0b46bc84d1b7b9b7766e1aa1cfcf676aded1ed81ce6f02e09ee7a1d9762dbR51


[WIP][CANN] Support moe for Ascend NPU

[CANN] Support moe for Ascend NPU
The moe feature based on th NPU is allowed.
Successfully run DeepSpeed CIFAR-10 model with Mixture of Experts (MoE) task in microsoft/DeepSpeedExamples. Using SGD optimizer，the test images achieved an accuracy of 46% on GPU and 47% on NPU.

@microsoft-github-policy-service agree


bug: regression on<EMAIL_ADDRESS>breaking the module

Hi I would like to use this package, I installed it
npx nuxi@latest module add nuxt-maplibre
After that I set ssr: false and wrapped the map in <ClientOnly> but unfortunately I get the following error
Uncaught SyntaxError: The requested module '/_nuxt/node_modules/@indoorequal/vue-maplibre-gl/dist/vue-maplibre-gl.umd.js?v=3efd9a54' does not provide an export named 'MglNavigationControl' (at app.vue:1:148)
Dependencies:
"nuxt": "^3.13.0", "nuxt-maplibre": "^1.0.0", "vue": "latest",

Hi,
Please provide a reproduction, with StackBlitz for example.

Hi, @Gugustinette , sure, I created a sandbox.
https://stackblitz.com/edit/nuxt-maplibre-error-reproduction?file=app.vue
It's important to note that I was able to get the correct nuxt 3 build on stackblitz, when I tried to create a new nuxt 3 project on codesandbox - everything worked.
I just created a new nuxt project today, so maybe this only applies to the newest build
I created the project in the following way: npx nuxi@latest init <project-name>

Thanks for the info and good luck

I'll keep the issue open until this gets fixed in Nuxt and update it when needed 👍

Fixed with Nuxt Maplibre v1.0.1

I believe this is still an issue. I created a new nuxt project and added the nuxt-maplibre module using the cli: pnpx nuxi@latest module add nuxt-maplibre. I created a client component and tried rendering it on the page. There is nothing rendered, and a console error shows:
Uncaught SyntaxError: The requested module '/_nuxt/node_modules/.pnpm/maplibre-gl@4.7.1/node_modules/maplibre-gl/dist/maplibre-gl.js?v=f4de1131' does not provide an export named 'LngLat' (at vue-maplibre-gl.es.js?v=f4de1131:10:10)

You can see the barebonese reproduction here https://github.com/marr/nuxt-maplibre


Add Adabelief Optimizer

Hi,
I added AdaBelief optimizer along with the training script. It's possible that the training hyper-parameters are not optimal yet, since I did not perform hyper-param tuning. The script should give an accuracy of around 78.04 with EfficientNet-b0 on ImageNet.
I turned off "rectify" and "print_change_log" in "optim_factory.py", you can modify main.py to pass "rectify" from args to AdaBelief but it might require extra coding. Currently, I turn off rectify (in "optim_factory.py") because rectification seems to not help much when the learning rate schedule has warmup in CNN experiments. Though from my experience, rectification helps in transformer training and GAN training.
Please let me know if you need other information.

@juntang-zhuang do you have good results with Adabelief on semantic segmentation tasks?

@juntang-zhuang thanks for the PR, could you remove the extra train script and args.yaml file? They shouldn't be there.
I agree that both are good information as reference for people using them with timm though. Perhaps you could create a gist with those two files, and put a link to that gist as an example in the docstring of the optimizer?

@rwightman Hi, I just deleted these files from PR and put the link below. Please feel free to put these links wherever you feel helpful.
link to train_scipt: https://gist.github.com/juntang-zhuang/0a501dd51c02278d952cf159bc233037
link to args.yaml: https://gist.github.com/juntang-zhuang/517ce3c27022b908bb93f78e4f786dc3
@JulienMaille Sorry I have not tested it on other tasks, I guess similar hyper-param settings should help. I found another repo with adabelief on object detection (https://github.com/yuanwei2019/EAdam-optimizer), but the adabelief code there is an old version, and you need to manually check changes in default hyper-params (rectify, eps, weight_decouple) in new versions (0.2.1)


Update linter to the latest version (golangci)

https://github.com/golangci/golangci-lint/releases

Someone's going to have fun with goerr113

May I take this issue?

@ken5scal Sure! We would appreciate that.

@soluchok thanks, I'm gonna start doing it!

@soluchok Should I just raise the version number in test-suite.yml? or should I fix all the linter reports?
I'm asking because the number of reports is not so small so that they may be not fixed for the historical reasons that I'm not aware of.

@ken5scal ken5scal  Go version is already updated to 1.15. You need to use golangci-lint 1.31.0. Better to fix inter reports as much as you can.
If not then just disable the specific linters in .golangci.yml. e.g
linters:
  disable:
    - testpackage # TODO enable.

And leave a TODO to enable it.

@soluchok great, thanks

#2181 is done for now.

@ken5scal Thanks.


Unhandled exception in approve_results.dart script

I was trying to pre-approve test status changes using
tools/sdks/dart-sdk/bin/dart tools/approve_results.dart -b vm* -p https://dart-review.googlesource.com/c/sdk/+/94441/7
but then got the following exception
Unhandled exception:
Exception: The log at https://logs.chromium.org/logs/dart/buildbucket/cr-buildbucket.appspot.com/8919605319691735136/+/steps/gsutil_find_latest_build/0/logs/raw_io.output_text_latest_/0?format=raw doesn't exist
#0      loadLog (file:///usr/local/google/home/ajcbik/drive2/dart/sdk/tools/approve_results.dart:86:5)

#1      todoFallbackLoadLog (file:///usr/local/google/home/ajcbik/drive2/dart/sdk/tools/approve_results.dart:107:20)

#2      loadResultsFromBot (file:///usr/local/google/home/ajcbik/drive2/dart/sdk/tools/approve_results.dart:129:21)

#3      main (file:///usr/local/google/home/ajcbik/drive2/dart/sdk/tools/approve_results.dart:493:14)
#4      _RootZone.runUnary (dart:async/zone.dart:1379:54)
#5      _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#6      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#7      Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#8      Future._completeWithValue (dart:async/future_impl.dart:483:5)
#9      Future.timeout. (dart:async/future_impl.dart:737:16)
#10     _RootZone.runUnary (dart:async/zone.dart:1379:54)
#11     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#12     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#13     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#14     Future._complete (dart:async/future_impl.dart:473:7)
#15     _cancelAndValue (dart:async/stream_pipe.dart:63:12)
#16     Stream.first. (dart:async/stream.dart:1170:11)
#17     _RootZone.runUnaryGuarded (dart:async/zone.dart:1314:10)
#18     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
#19     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
#20     _SinkTransformerStreamSubscription._add (dart:async/stream_transformers.dart:68:11)
#21     _EventSinkWrapper.add (dart:async/stream_transformers.dart:15:11)
#22     _JsonStringDecoderSink.close (dart:convert/runtime/libconvert_patch.dart:1489:11)
#23     _ConverterStreamEventSink.close (dart:convert/chunked_conversion.dart:82:18)
#24     _SinkTransformerStreamSubscription._handleDone (dart:async/stream_transformers.dart:141:24)
#25     _RootZone.runGuarded (dart:async/zone.dart:1302:10)
#26     _BufferingStreamSubscription._sendDone.sendDone (dart:async/stream_impl.dart:389:13)
#27     _BufferingStreamSubscription._sendDone (dart:async/stream_impl.dart:399:15)
#28     _BufferingStreamSubscription._close (dart:async/stream_impl.dart:283:7)
#29     _SinkTransformerStreamSubscription._close (dart:async/stream_transformers.dart:96:11)
#30     _EventSinkWrapper.close (dart:async/stream_transformers.dart:23:11)
#31     _StringAdapterSink.close (dart:convert/string_conversion.dart:251:11)
#32     _Utf8ConversionSink.close (dart:convert/string_conversion.dart:302:20)
#33     _ConverterStreamEventSink.close (dart:convert/chunked_conversion.dart:82:18)
#34     _SinkTransformerStreamSubscription._handleDone (dart:async/stream_transformers.dart:141:24)
#35     _RootZone.runGuarded (dart:async/zone.dart:1302:10)
#36     _BufferingStreamSubscription._sendDone.sendDone (dart:async/stream_impl.dart:389:13)
#37     _BufferingStreamSubscription._sendDone (dart:async/stream_impl.dart:399:15)
#38     _BufferingStreamSubscription._close (dart:async/stream_impl.dart:283:7)
#39     _SinkTransformerStreamSubscription._close (dart:async/stream_transformers.dart:96:11)
#40     _EventSinkWrapper.close (dart:async/stream_transformers.dart:23:11)
#41     _ByteAdapterSink.close (dart:convert/byte_conversion.dart:62:11)
#42     _FilterSink.close (dart:io/data_transformer.dart:637:11)
#43     _ConverterStreamEventSink.close (dart:convert/chunked_conversion.dart:82:18)
#44     _SinkTransformerStreamSubscription._handleDone (dart:async/stream_transformers.dart:141:24)
#45     _RootZone.runGuarded (dart:async/zone.dart:1302:10)
#46     _BufferingStreamSubscription._sendDone.sendDone (dart:async/stream_impl.dart:389:13)
#47     _BufferingStreamSubscription._sendDone (dart:async/stream_impl.dart:399:15)
#48     _BufferingStreamSubscription._close (dart:async/stream_impl.dart:283:7)
#49     _ForwardingStream._handleDone (dart:async/stream_pipe.dart:106:10)
#50     _ForwardingStreamSubscription._handleDone (dart:async/stream_pipe.dart:172:13)
#51     _RootZone.runGuarded (dart:async/zone.dart:1302:10)
#52     _BufferingStreamSubscription._sendDone.sendDone (dart:async/stream_impl.dart:389:13)
#53     _BufferingStreamSubscription._sendDone (dart:async/stream_impl.dart:399:15)
#54     _BufferingStreamSubscription._close (dart:async/stream_impl.dart:283:7)
#55     _SyncStreamController._sendDone (dart:async/stream_controller.dart:772:19)
#56     _StreamController._closeUnchecked (dart:async/stream_controller.dart:629:7)
#57     _StreamController.close (dart:async/stream_controller.dart:622:5)
#58     _HttpParser._closeIncoming (dart:_http/http_parser.dart:1037:23)
#59     _HttpParser._doParse (dart:_http/http_parser.dart:752:11)
#60     _HttpParser._parse (dart:_http/http_parser.dart:318:7)
#61     _HttpParser._onData (dart:_http/http_parser.dart:810:5)
#62     _RootZone.runUnaryGuarded (dart:async/zone.dart:1314:10)
#63     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
#64     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
#65     _SyncStreamController._sendData (dart:async/stream_controller.dart:764:19)
#66     _StreamController._add (dart:async/stream_controller.dart:640:7)
#67     _StreamController.add (dart:async/stream_controller.dart:586:5)
#68     _Socket._onData (dart:io/runtime/binsocket_patch.dart:1774:41)
#69     _RootZone.runUnaryGuarded (dart:async/zone.dart:1314:10)
#70     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
#71     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
#72     _SyncStreamController._sendData (dart:async/stream_controller.dart:764:19)
#73     _StreamController._add (dart:async/stream_controller.dart:640:7)
#74     _StreamController.add (dart:async/stream_controller.dart:586:5)
#75     _RawSecureSocket._sendReadEvent (dart:io/secure_socket.dart:1004:19)
#76     Timer._createTimer. (dart:async/runtime/libtimer_patch.dart:21:15)
#77     _Timer._runTimers (dart:isolate/runtime/libtimer_impl.dart:382:19)
#78     _Timer._handleMessage (dart:isolate/runtime/libtimer_impl.dart:416:5)
#79     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:171:12)

@crelier

Even when the preapproval command does not crash, preapproved tests are still failing after committing.
https://logs.chromium.org/logs/dart/buildbucket/cr-buildbucket.appspot.com/8919530372267517456/+/steps/test_results/0/logs/tests_that_began_failing/0
Shows:
The following tests began failing (needs approval):
vm/cc/CodeExecutability is new and failed (Crash, expected Pass)
Here is my preapproval done before committing:
regis@belenos:~/dart1/sdk$ tools/sdks/dart-sdk/bin/dart tools/approve_results.dart -p https://dart-review.googlesource.com/c/sdk/+/95263/11 -b vm-kernel-win*
Selected bot: vm-kernel-win-release-x64
Selected bot: vm-kernel-win-release-ia32
Selected bot: vm-kernel-win-product-x64
Selected bot: vm-kernel-win-debug-x64
Selected bot: vm-kernel-win-debug-ia32
The following tests are now failing:

BOT
TEST
RESULT
EXPECTED

vm-kernel-win-debug-ia32
vm/cc/CodeExecutability
Crash
Pass

vm-kernel-win-debug-x64
vm/cc/CodeExecutability
Crash
Pass

vm-kernel-win-product-x64
vm/cc/CodeExecutability
Crash
Pass

vm-kernel-win-release-ia32
vm/cc/CodeExecutability
Crash
Pass

vm-kernel-win-release-x64
vm/cc/CodeExecutability
Crash
Pass

1804 of 50334 tests are failing (3.58%)
25 of 50334 tests are flaky (0.05%)
0 of 50334 tests were fixed since last approval (0.00%)
5 of 50334 tests were broken since last approval (0.01%)
Note: It is assumed bugs have been filed about the above failures before they are approved here.
Note: Approving the failures will turn the bots green on the next commit.
Warning: Preapproval is currently not sticky and somebody else approving before your CL has landed will undo your preapproval.
Do you want to approve? (yes/no) [yes]
Uploading approved results...
Uploaded approved results for vm-kernel-win-debug-ia32
Uploaded approved results for vm-kernel-win-debug-x64
Uploaded approved results for vm-kernel-win-release-x64
Uploaded approved results for vm-kernel-win-product-x64
Uploaded approved results for vm-kernel-win-release-ia32
Successfully approved results, the next commit will turn bots green

Actually, preapprovals worked on some bots, but not all.

Also, some bots are not recognized by the script:
tools/sdks/dart-sdk/bin/dart tools/approve_results.dart -b dart2js-strong-win-x64-firefox
error: No bots matched pattern: dart2js-strong-win-x64-firefox

Hi. This happens whenever tryjobs have encountered infrastructure issues (alas, it happens) and approve_results fails to find the results. It can't proceed with approving the builders you requested (all of them by default) and stops. I'll improve the tool so it emits a warning and continues with the remaining builders, and tells you to look at the appropriate build for infrastructure issues.

Done. Be sure to update your approve_results.dart and let me know if there's any more problems.


not all properties in fetch_table

First: Thanks for this very nice and handy package!!
My problem: I want to use properties like the electrophility (listed under available properties). With fetch_table('elements') I get only 70 of the 89 listed properties, and also electrophility is missing in the output. Using
from mendeleev import element F = element('F') F.electrophilicity()
gives the correct value. However, having this in the fetch_table would be much more user friendly. Is there any reason for not adding all properties to fetch_table('elements')?

Thanks for the feedback @janphhe.
You are right elecrophilicity (and some other properties) is not included when fetching data with fetch_tablesimply because electrophilicity is computed on the fly rather than stored in the db and fetch_table only reads what's in the db.
This probably isn't ideal but you could values for electrophilicity for all elements with
from mendeleev import element
[element(i).electrophilicity() for i in range(1, 119)]

In general I think it could be useful to get all the stored and and computed properties as a table.


Create automation for getting a list of all org and space managers

Background
We have no easy way to keep track of org managers and space managers in Cloudfoundry. This is problematic because it leaves us unsure who to contact about organization or platform issues.
We should write a script to get the org/space managers and add some automated to run the job regularly.
Implementation

Write script to get all org and space managers
Generate CSV output
Create pipeline to run this task regularly (weekly? daily?)

This is not a priority for now


Fix failing lm1b tests.

Fix lm1b tests failing on a non-important JAX warning (from XLA: non usable donated buffers).

Codecov Report

Merging #1711 (92fd4a5) into main (d10eda8) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #1711   +/-   ##
=======================================
  Coverage   83.21%   83.21%
=======================================
  Files          69       69
  Lines        5867     5868    +1
=======================================
+ Hits         4882     4883    +1
  Misses        985      985

Impacted Files
Coverage Δ

flax/linen/partitioning.py
78.78% <100.00%> (+0.10%)
: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 ef0f564...92fd4a5. Read the comment docs.

Sorry, I was out when this was sent for review, but thanks for the quick fix @levskaya!


Testing console output

Hello,
we're in the process of migrating lint-staged to Listr2, but I have some question regarding test output assertion.
The orginal Listr's verbose renderer printed [started] and [completed] strings, while Listr2 uses fancy symbols like ❯ and ✔. These symbols are different on each platform, though, so testing in a CI environment is a bit difficult.
You can see the progress in the PR https://github.com/okonet/lint-staged/pull/852  and how the assertions fail on our Windows tests: https://ci.appveyor.com/project/okonet/lint-staged/builds/32413566/job/qyae7t039cckykre

That is a easy fix I will add the test renderer as default.

Something in the ballpark of this hopefully does it. I will also add tests here when I have free time but been lazy lately.
To call the test renderer set the renderer to test.
  const tasks = new Listr<ListrCtx>([
    {
      // You can nest Listr objects, as in the original but now you can also call a new listr class throught task.newListr and inject a type as well
      title: 'Concurrent sub test.',
      task: (ctx, task): Listr => task.newListr<ListrCtx>([
        ...someTasks
  ], {
    renderer:'test'
  })

I will merge after I perform usual manual tests.

If it’s configurable I can also set renderer: ’test’ during setup.

Added a test renderer with #11, published with version 1.3.8.
Take a look at Logger and Test Renderer for expected outputs on the given occasion. But they are all text-based now. I will also add automated tests hopefully soon.
As mentioned you can pass in test renderer with { renderer: 'test' } as an option to the given task.

For any more issues, I kindly ask you to please open up a new issue, hopefully I was helpful! Have a nice day.

Thanks, seems to be just what we need! I'll also use the test renderer when TERM=dumb just in case those don't support the fancy glyphs.

What you can also do is to set fallback renderer to test instead of the verbose by passing in { nonTTYRenderer: 'test' } since it should automatically detect non-tty environment.

@iiroj I kindly wanted to inform you about the upcoming changes beforehand.
For further updates with Listr2 there had to be breaking changes how the renderer options get passed in, I just wanted to go ahead and kindly inform you about the breaking changes that were discussed on the original repository by SamVerschueren in Originally posted by @SamVerschueren in https://github.com/SamVerschueren/listr/issues/143#issuecomment-623094930.
This will affect how the renderer and task-scoped renderer options get passed in. This can be seen in detail in here.
While doing that I also exchanged the 'test' renderer which you are mainly using back to 'verbose' since verbose renderer does not use icons anymore and they are basically the same now. So this will not require a major refactoring and a ctrl+h would be more than enough.
Some of the issues about the collection of errors which can be seen here and cli-truncate functionality has been fixed that you mentioned here in this pull request.

@iiroj I kindly wanted to inform you about the upcoming changes beforehand.
For further updates with Listr2 there had to be breaking changes how the renderer options get passed in, I just wanted to go ahead and kindly inform you about the breaking changes that were discussed on the original repository by SamVerschueren in Originally posted by @SamVerschueren in https://github.com/SamVerschueren/listr/issues/143#issuecomment-623094930.
This will affect how the renderer and task-scoped renderer options get passed in. This can be seen in detail in here.
While doing that I also exchanged the 'test' renderer which you are mainly using back to 'verbose' since verbose renderer does not use icons anymore and they are basically the same now. So this will not require a major refactoring and a ctrl+h would be more than enough.
Some of the issues about the collection of errors which can be seen here and cli-truncate functionality has been fixed that you mentioned here in this pull request.

@cenk1cenk2 thanks for the info! I'll see about migrating to it. Since I already moved the error collecting out of the old behaviour of listr before this, does this affect lint-staged? It was a good change to do in lint-staged IMO since it streamlined the collection of task output (other than errors).
I assume I will have to at least change the errors key to something else in the context. Right now it's a Set and various error cases push symbols to it, so that it's easy to check if (errors.has(SomeSymbol))

Sorry to ask an otherwise unrelated question, but does the inclusion of cli-truncate mean that the task name will always be on a single line? Lint-staged currently shortens function task names until the first space in the command string [Function] eslint ..., but this might allow us to skip the truncating and just pass the entire string as the name. This can be really long, since it potentially includes full (absolute) file paths of all staged files during a git commit.

I think it should not cause any problems for the errors because error collection is done out of the context. So after the task has been run, you shoud  access the errors via task.err. As a result if this way works much better for you, I think no refactoring is needed.
const task = new Listr(...)
const ctx = await task.run()
logger.fail(task.err)
// will show all of the errors that are encountered through execution

If your cli-truncate action relies on process.stdout.columns as well it will more or less do the same basic thing utilizing the plugin cli-truncate.
Only thing that may need refactoring is the rendererOptions. They now have their own key and not set from the root of the options and they will change their autocomplete functionallity based on which renderer is selected. This can be seen here in detail.
I have also removed test renderer which you are using for the tests since I equalize verbose and test renderer in a way that verbose renderer now has their icon output as optionals. So since they are basically the same thing now and verbose seemed like a better naming scheme then test, I removed test renderer. But this should be a matter of find&replace { renderer: 'test' } to { renderer: 'verbose' }. If you so wish you can pass a mock funtion for testing purposes to verbose renderer extending Logger class { renderer: 'verbose', rendererOptions: { logger: MyLoggerClass } }, which I think should make testing more easier. But it can also work as a plug-and-play replacement, just changing the logger name.


Build fails on Mac M1

Hi,
I tried to build uBPF on Mac M1. I successfully installed all prerequisites for the project. However, when I want to build the project, I get this:
$ cmake -S . -B build -DUBPF_ENABLE_TESTS=true -DUBPF_ALTERNATE_LLVM_PATH=/opt/homebrew/opt/llvm/bin

CMake Warning at vm/CMakeLists.txt:19 (message):
  uBPF - using compat ELF support for macOS.

-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_add.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_add32.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_and.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_and32.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_cmpxchg.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_cmpxchg32.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_fetch_add.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_fetch_add32.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_fetch_and.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_fetch_and32.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_fetch_or.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_fetch_or32.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_fetch_xor.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_fetch_xor32.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_or.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_or32.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_xchg.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_xchg32.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_xor.data test to fail.
-- Expecting /path/to/ubpf/external/bpf_conformance/tests/lock_xor32.data test to fail.

CMake Warning at bpf/CMakeLists.txt:69 (message):
  Clang supports BPF target

-- Building BPF map
-- Building BPF rel_64_32
-- Configuring done (0.3s)
-- Generating done (0.2s)
-- Build files have been written.

Here it is my llvm version:
$ brew info llvm
llvm: stable 17.0.6, HEAD [keg-only]

I was wondering if I could build uBPF on Mac M1.

How are you reaching the conclusion the build failed? I don't see any error message

Interesting. FYI the output of my cmake -S . is the same as yours, but my target test works just fine, i.e., all tests run
Is your brew x86 or arm? Maybe you wanna do -DUBPF_ALTERNATE_LLVM_PATH=$(brew --prefix llvm)/bin to make sure it is picking up the alternate llvm installed. Brew on x86 vs brew on ARM use different paths.

Interesting. FYI the output of my cmake -S . is the same as yours, but my target test works just fine, i.e., all tests run

That's interesting!

Is your brew x86 or arm?

It is arm64. If I'm not mistaken, all M series are arm-based.

Maybe you wanna do -DUBPF_ALTERNATE_LLVM_PATH=$(brew --prefix llvm)/bin to make sure it is picking up the alternate llvm installed.

It is the same output as before, and the tests are not passing. $(brew --prefix llvm)/bin gives the same llvm path I originally passed to cmake.

Is your brew x86 or arm?

It is arm64. If I'm not mistaken, all M series are arm-based.

Yep, but the M series supports x86 emulation using Rosetta. If you had a time machine backup that you used to migrate from the intel chip to the M chip, you would had got an x86 brew. Been there, done that.
I have just set up a dual-architecture brew, i.e., brew in x86 and arm so I can interchange them when compiling the bpf projects.
Can you try compiling a bpf using clang to make sure that is working?
$(brew --prefix llvm)/bin/clang -O2 -target bpf -c ./bpf/rel_64_32.bpf.c -o hello.o

This ./bpf/rel_64_32.bpf.c file is part of the ubpf repository. Does it work?

Yep, but the M series supports x86 emulation using Rosetta. If you had a time machine backup that you used to migrate from the intel chip to the M chip, you would had got an x86 brew. Been there, done that.

Aha, I see! No, I didn't migrate anything from the time machine.

I have just set up a dual-architecture brew, i.e., brew in x86 and arm so I can interchange them when compiling the bpf projects.

Thank you!

This ./bpf/rel_64_32.bpf.c file is part of the ubpf repository. Does it work?

Yes, it did! it compiled the rel_64_32.bpf.c program without any errors.

I just happened to make a mistake that might have been yours.
I was just going over the ubpf compilation again, and I did:
cmake -S . -B build -DUBPF_ENABLE_TESTS=true -DUBPF_ALTERNATE_LLVM_PATH=$(brew --prefix llvm)/bin
cmake --build build --target test --

And I got a very similar output to yours, where tests didn't run. The mistake is that I forgot to actually compile everything before running the tests:
cmake --build build --config Debug

This should be done before trying to run the tests, as they depend on the project being compiled first.
So the order should be:
cmake -S . -B build -DUBPF_ENABLE_TESTS=true -DUBPF_ALTERNATE_LLVM_PATH=$(brew --prefix llvm)/bin
cmake --build build --config Debug
cmake --build build --target test --

Ah, yes! That was actually the mistake I made! I changed the config to Debug and now the tests are passing except the last two ones!  The output of my tests is the following:
673/674 Test #673: rel_64_32_TEST_INTERPRET ..........................***Failed  Required regular expression not found. Regex=[0xe[
]*[
]*$
]  0.00 sec
        Start 674: rel_64_32_TEST_JIT
674/674 Test #674: rel_64_32_TEST_JIT ..........................***Failed  Required regular expression not found. Regex=[0xe[
]*[
]*$
]  0.00 sec

99% tests passed, 2 tests failed out of 674

Total Test time (real) =   7.99 sec

The following tests FAILED:
	673 - rel_64_32_TEST_INTERPRET (Failed)
	674 - rel_64_32_TEST_JIT (Failed)

The  tests output log for these two tests contains the following info:
673/674 Testing: rel_64_32_TEST_INTERPRET
673/674 Test: rel_64_32_TEST_INTERPRET
Command: "/path/to/project/ubpf/build/bin/ubpf_test" "--main-function" "main" "/path/to/project/ubpf/build/bpf/rel_64_32.bpf.o"
Directory: /path/to/project/ubpf/build/bpf
"rel_64_32_TEST_INTERPRET" start time: Mar 20 19:14 PDT
Output:
----------------------------------------------------------
uBPF error: number of nested functions calls (11) exceeds max (10) at PC 3
Warning: bad relocation type 10; skipping.
Warning: bad relocation type 10; skipping.
Warning: bad relocation type 10; skipping.
0xffffffffffffffff
<end of output>
Test time =   0.00 sec
----------------------------------------------------------
Test Fail Reason:
Required regular expression not found. Regex=[0xe[
]*[
]*$
]
"rel_64_32_TEST_INTERPRET" end time: Mar 20 19:14 PDT
"rel_64_32_TEST_INTERPRET" time elapsed: 00:00:00
----------------------------------------------------------

674/674 Testing: rel_64_32_TEST_JIT
674/674 Test: rel_64_32_TEST_JIT
Command: "/path/to/project/ubpf/build/bin/ubpf_test" "--main-function" "main" "/path/to/project/ubpf/build/bpf/rel_64_32.bpf.o"
Directory: /path/to/project/ubpf/build/bpf
"rel_64_32_TEST_JIT" start time: Mar 20 19:14 PDT
Output:
----------------------------------------------------------
uBPF error: number of nested functions calls (11) exceeds max (10) at PC 3
Warning: bad relocation type 10; skipping.
Warning: bad relocation type 10; skipping.
Warning: bad relocation type 10; skipping.
0xffffffffffffffff
<end of output>
Test time =   0.00 sec
----------------------------------------------------------
Test Fail Reason:
Required regular expression not found. Regex=[0xe[
]*[
]*$
]
"rel_64_32_TEST_JIT" end time: Mar 20 19:14 PDT
"rel_64_32_TEST_JIT" time elapsed: 00:00:00
----------------------------------------------------------

Have you ever gotten into such a situation before by any chance?

Yeah, test runs the tests, but it assumes binaries have been compiled before.
tl;dr
I am getting the same as you on the last 2 tests, I am ignoring that for now.
Longer thoughts
I have three guesses on why:

either it is some architectural difference that ends up getting a different result
or some other ubpf bug, as I find it particularly weird how it is reaching the maximum number of nested calls. If you look at rel_64_32.bpf.c, it has no reason to be doing more than 10 nested calls, but again this could be a problem with the compiler? Maybe manually inspecting the bpf bytecode. I tried writing a simple main function in c that returns an integer and that worked just fine, so it isn't like toolchain+ubpf is completely broken on Mac
or maybe this is the expected result anyway and the problem is just the regex engine and how it is different on Mac and on the Linux distributions used. Maybe, and only maybe, it is just a matter of tweaking the regex so it works on both systems.

Testing it on a Linux machine (preferably x86, but potentially arm64 as well?) would be ideal to know which path to follow if one wanted to debug it further. Will a Linux machine get the same 0xffffff result (is it an integer overflow?)? Maybe more importantly, would a linux machine also explode the limit of nested function calls?
I tried recompiling ubpf on my Mac with higher limits of nested function calls, making it to the hundreds, and it would still explode. So maybe there is an infinite loop somewhere?
I can't commit to investigating it in the short term, though; feel free to do so, or just ignore them for now as well

I see! That makes sense!
Thank you for your help! On Linux with x86 architecture, I don't have any issues building and passing these tests. But, I'll go and see if I can fix this issue on Mac.

@hadisinaee and @viniciusd I think this should be fixed now? We have a CI/CD that runs on macos-11 (switching to macos-latest).
Please re-open if there is still an issue.


[request] add a SpaceFN function to your stdlib.dyon?

SpaceFN is a concept that uses the spacebar as an additional mod key, see https://geekhack.org/index.php?topic=51069.0
Currently there doesn't appear to be a clean implementation under Linux. As a result implementing this could be a real demonstration of how useful evscript can be. Do you think that is possible?
btw) this doesn't work well when using xcape as xcape lacks rollover detection (see topic I link to above).

hmm — evscript cannot remove emitted events, only create new ones (on a separate device) — so preventing the spacebar from repeating is not possible in a straightforward way.
I guess you'd have to remap the spacebar to some other key using… something (layouts in kernel?), and configure evscript to emit the space key when that key is pressed on its own.
Or use evscript as a proxy — forward all events from the original keyboard, modifying the spacebar — if you can prevent your compositor from picking up the original keyboard (something about udev labels?). I'm not a fan of this idea (a bit brittle and slightly increases latency), but I guess that shows the flexibility :)

I have not yet played with Wayland, but for X11 I do remap 'normal' keys using XCB, before xcape comes into play. The same thing would work for the spacebar, although don't know how to do that for wayland yet.
Are you saying that with a remapped spacebar one could implement SpaceFN relatively easily using your library?
btw) sorry for the question, but rust is not a language I'm that familiar with....and hence don't really see how to do this.

I mean, if you remap at a lower level, before evscript comes into play.
(btw, not a library, an executable that runs scripts written in Dyon, not Rust)


Fix incorrect parsing of component spec

@Carapacik this is an example of a parsing result that I believe is incorrect. Using version 0.10.0.
Here is the OpenAPI spec of a sample component. The notable item is that this component does not have any properties defined.
"UpdateResponse": {
  "type": "object",
  "description": "The response for the `Update` operation."
},

Current Result
Due to the fact that this component does not have any properties, swagger_parser is returning the following result:
typedef UpdateResponse = Object;

This is then problematic in the generated serialization code, as seen below. Of course, the native dart Object type does not have a fromJson defined.
final value = Object.fromJson(_result.data!);

The above will error and the only workaround right now is to simply overwrite the swagger_parser result, after the fact, with the solution provided below.
Desired Result
Changing the typedef parsed result to an empty serializable object (i.e. no parameters) resolves the issue. This should be the appropriate parsed result for that OpenAPI spec definition.
import 'package:json_annotation/json_annotation.dart';
part 'update_response.g.dart';

@JsonSerializable()
class UpdateResponse {
  const UpdateResponse();

  factory UpdateResponse.fromJson(Map<String, dynamic> json) =>
      _$UpdateResponseFromJson(json);

  Map<String, dynamic> toJson() => _$UpdateResponseToJson(this);
}

This is invalid behavior, because you can simply assign an empty class, and not execute fromJSON.
It makes no sense to generate an empty class