A simulator for the farmbot

Hello everyone,
I contacted Rory Aronson some time ago about the potential creation of a simulator for the farmbot. I take advantage of the coronavirus to find some free time at last.
First, I would like to know your opinion on the subject, especially if it will be useful for you, and if yes what do you need most. For instance, a simulation could be used to test/debug the code, or it could be released and used as a marketing tool to let anyone play with the web interface. Depending on your answer, the technology and the way it is put together with the current code could be different.
To me, the simulator would be a way to play with the code and see how it works before eventually buying the real robot in the years to come.
If you want to go further, i will give you more details about which simulator will be used, where to link the simulator to the code… There is also some details that I need to discuss with you. And obviously, all that will depend on what you want.
Finally, I must be honest, I will not work on it a lot of time and it won’t be ready before 5 to 6 months minimum. If you think you will be able to dispatch someone to work on the simulator, please let me know, as it will influence the technologies used.
Best regards,
Grégoire Pichereau

Hi @Bracewind
It's a busy day for me here at FarmBot, so it will be some time before I can provide a full response, but this is a very interesting idea.
I will provide a longer response some time this week.
Thanks for reaching out to us!

Ok, thanks for giving me an answer despite your workload,
have a nice day and good luck !

@Bracewind OK- sorry for the delay. Here is a more in-depth response.

I would like to know your opinion on the subject

This is a really fun idea, and we've had quite a few folks request it in the past. I think this would be fun for people who are passively curious about FarmBot.

a simulation could be used to test/debug the codebase

I could see the feature being useful to non-developers, but for a software developer that is not concerned with visualization or aesthetics, it is already possible to simulate a FarmBot by purchasing a RAMPS board on Amazon (~$25 USD), flashing the FarmBot firmware to it, and running FBOS on a host laptop.
This is how I do most local development for FarmBot features. It might also be a good way for you to test things out as you build the simulator.

I will give you more details about which simulator will be used

I am happy to continue the discussion in this Github thread. If it looks like you are very serious about the project, I can hop on a call with you later on.
We also were contacted by some folks this week that had a similar interest and are using IsaacSim, I'm not sure if you've heard of that before (I have not).
From the perspective of a developer, I'd be happy to share advice on the parts of the stack that would be best suited for simulation.

If you think you will be able to dispatch someone to work on the simulator, please let me know

FarmBot has two software developers (including myself) so that's not an option for us. It's also worth mentioning that our ability to change FarmBot source code to meet the needs of this project would be limited as well, since our main focus is meeting the needs of paying customers.
There are ways that a simulator could be built without changes to the FarmBot codebase. Since I don't know how your idea fits in to the roadmap or our coding standards, I can't promise any changes to existing FarmBot code to meet the needs of a simulator. I am fairly certain a simulation could be built unobtrusively, though I would need to know more about your tool chain to provide options, though. I look forward to learning more about the tools you plan on using.
I hope this helps! Speak soon.

@RickCarlino No problem, this is a low priority improvement, so take all the time you need

I could see the feature being useful to non-developers, but for a software developer that is not concerned with visualization or aesthetics, it is already possible to simulate a FarmBot by [...] running FBOS on a host laptop.

I think that more than asthetics, it also helps to simulate what would happen when there is physical inconstencies, for instance if there is less friction between two links, and see if the measures taken by the program are enough to deal with that case. A simple stub may do the trick, but having a physical engine doing the job for you is reassuring.
Anyway, considering what you said, it would probably be more useful to have a beautiful simple model than an ugly complex one.

This is how I do most local development for FarmBot features. It might also be a good way for you to test things out as you build the simulator.

Thanks for the tip, I will definitely use this.

We also were contacted by some folks this week that had a similar interest and are using IsaacSim, I'm not sure if you've heard of that before (I have not).

I don’t know the simulators used in the industry, as most of them are expensive. I made a little search about IssacSim, and the version useful for manipulative robot is still at an early stage. It seems it is a good choice when the robot is controlled using machine learning, as the simulator is probably faster than other simulators, since it is developed by Nvidia. But when it comes to real simulation, I think it will be less realistic than others, and allow for less options. Moreover, I’m not sure it will be completely free when it will be released...
There are three simulators I found interesting : V-rep, Gazebo and Webots.
I still need to test them all more to know which one I will use. I will choose the one that works well on windows, is easy to launch, is easy to interact with, and also one which allows me to easily develop the whole thing.
I know well Gazebo, so I’m keen on using it, but it is probably not the right choice for something easy to use.

our ability to change FarmBot source code to meet the needs of this project would be limited

Changing FarmBot source code never crossed my mind. I think a good way to do this would be to get the g-code generated for arduino and transfer it to the computer, then parse and execute it so it does the movements asked on the simulator. However, this won’t truly be the movements of the farmbot if PID controller or other control systems are executed by the firmware and not the OS, which is probably the case. But I think it’s not really relevant for this project.
If you have anything you want to add or correct, feel free to do so. I will come back after analyzing a little more each simulator

I think a good way to do this would be to get the g-code generated for arduino and transfer it to the computer, then parse and execute it so it does the movements asked on the simulator.

This is a good idea. If you need a starting point (or just want to see how GCode interactions occur), you could flash FarmBot OS onto a RaspberyPi. FBOS can handle the Arduino being unplugged (or not having an Arduino at all). This might be the fastest way to get test data.
Please let me know if you have any questions.

A summary of the available choices is given after this paragraph if you are in a hurry
I've tested the three simulators and.... it will be more complex than what I thought ;)

V-rep : I've tried to import the collada files of the farmbot, but it does not work and crash. Only collada files are accepted with the free version of the software and no color or materials can be imported (Only materials coded using Obj format are accepted by V-rep). Everything seems perfect in V-rep, and maybe creating the structure without the textures could work. It would be ugly but it would work.
Gazebo : Contrary to what is told, Gazebo is only available on Linux. I tried all afternoon to install it on Windows and it's hard and long. But on Ubuntu, the collada files were very well imported !! Well, I didn't try to move the farmbot, but I know Gazebo and I don't think it will be hard, a little long though.
Webots : Webots does not support importing 3D design files, and it will be added in the next release. Stl and collada files will be supported, so it could be a serious option when the release will be done. Moreover, contrary to V-rep, the code source is available, so I will be able to tweek a little the functionnality if needed.

You are the one that needs to choose :

No visual but windows support
No windows but "good" (gazebo is not really good looking) looking visual.
Wait for Webots to release the functionnality and work on the parser instead. It also delays the simulator selection.

To be honest, I don't really know who will use the simulator (except me) and I think you know that better than me, this is why I cannot make this decision myself.
Since a parser will be needed for the project, I also was wondering if a g-code parser had already been implemented somewhere.
If you want more details or need more information, feel free to ask.

@Bracewind

You are the one that needs to choose

Since it sounds like you are doing this as a side project for fun, I would definitely pick the one that you find most rewarding / enjoyable to work with. With that being said, from a "usefulness" perspective, I think a simulator is best suited for non-technical users (as I mentioned in a previous message, there are already a variety of tools available for software developers). Having something that is visual and Windows based is probably the best fit for a non-technical user base. On the flip side, we only use Linux for software development here at FarmBot.

work on the parser instead.

It sounds like you are familiar with the design of parsers. One thing to keep in mind about this parser is that it will most likely be one of the most simple you have ever written. The official FarmBot G-Code parser is here. Depending on your programming background, there is an old Ruby-based GCode parser that can be found here. The GCode spec has not changed too much in 5 years, aside from some new additions.
FarmBot Gcode is easily parsed using string splitting and case statements. Use of more advanced techniques (such as regex or string scanners) might be overkill. What language are you using for the parser? A good experiment to try would be to flash FarmBot firmware onto an Arduino Mega and view the output in a serial terminal, such as Hyperterm.

I’ve seriously tried to use webots, and I could load the model whithout materials using plugins. But I regularly experiment crashes, and I think the cause is huge memory leak in the software… So I will use Gazebo, even though it is clearly not the optimal choice :/
Running Gazebo on Windows is possible using windows subsystems, not sure if it will be performant though.
I’ve started to create the visual, but to add physical properties such as collisions, I would need models with less mesh than what is available on Onshape. I suppose it has not been done so I will try to do it.

One thing to keep in mind about this parser is that it will most likely be one of the most simple you have ever written. [...] A good experiment to try would be to flash FarmBot firmware onto an Arduino Mega and view the output in a serial terminal, such as Hyperterm.

I looked at the parsers you gave me and you’re right it is quite simple. The code will be done in c++ in the whole project because I think it will be easier to interoperate with the arduino, and because it will be easier to optimize the code if needed. To be consistent, the parser will also be in c++.  Since it will probably not be very difficult, and since I still don’t have the Arduino (shipping is longer right now), I will do the parser later.

@Bracewind
How about this one as example? http://amapstudio.cirad.fr/soft/amapsim/start
Seems it has already trained models for some kind of plants that can visualise farming process.with some kind of plugins that can simulate farmbot behaviour.

@gueux
Could you be a little more specific ? This software seems to simulate the plant growth, and I don't find plugins for simulating harvest.(I looked at this page http://amapstudio.cirad.fr/soft/amapsim/c_tools/d_plug-ins/start). I'm interested however to see how it works behind the scene, and if a plugin could do the harvesting part, which is something currently impossible, or at least difficult to do, on Gazebo.
I worked on other things the last year, and could not really find time to develop the simulator. For now, I only did a very simple graphical control with no physics and no gcode.


⚠ Bofrost.com has degraded performance

In 5cf2cfa, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 804 ms

Resolved: Bofrost.com performance has improved in 75c343d after 8 minutes.


Link Diagnose & Solve Best Practices

Diagnose & Solve includes a section on Best Practices for Availability & Performance, and checks for use of features such as Local Cache. This document would be a great place to lead customers to Diagnose & Solve to help proactively identify potential issues with their application.
The Diagnose & Solve detector route is /detectors/ParentAvailabilityAndPerformance.

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

ID: eaaa2dff-e57f-370e-fbf7-3ed37de2bb2a
Version Independent ID: 24c98efe-5bcf-fe19-445d-8512e7929a58
Content: Deployment best practices - Azure App Service
Content Source: articles/app-service/deploy-best-practices.md
Service: app-service
GitHub Login: @JasonFreeberg
Microsoft Alias: jafreebe

@dagrooms52 Thanks for the feedback! We are currently investigating and will update you shortly.

Hi @dagrooms52 , we appreciate you bringing this to our attention. After reviewing your feedback, we feel the best place to leave this feedback is on the Azure portal for the Azure Portal UI team to act on it. They monitor all UI feedback on the Azure portal platform. Please see the photo below to see how you can leave your feedback on the portal.
You can click on the smiley face on the top right to leave your feedback.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Undefined method `strip' for nil:NilClass

          Original issue by @nemoeslovo - Imported from fastlane/cert#32

I use to set up username field in cert action and DELIVER_PASSWORD as env variables in Jenkins machine and everything worked perfectly, but with one of the latest update I start getting following error:
[12:58:45]: ------------------
[12:58:45]: --- Step: cert ---
[12:58:45]: ------------------
No username or password given. You can set environment variables:
DELIVER_USER, DELIVER_PASSWORD
-------------------------------------------------------------------------------------
The login information you enter will be stored in your Mac OS Keychain
More information about that on GitHub: https://github.com/fastlane/CredentialsManager
-------------------------------------------------------------------------------------
Username: [12:58:45]: undefined method `strip' for nil:NilClass
[12:58:45]: You passed invalid parameters to 'cert'.
[12:58:45]: Check out the error below and available options by running `fastlane action cert`
[12:58:45]: Variable Dump:
[12:58:45]: {:DEFAULT_PLATFORM=>:ios, :ENVIRONMENT=>nil, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios build_dev", :VERSION_NUMBER=>"1.0.0", :BUILD_NUMBER=>0}
[12:58:45]: Invalid default value for username, doesn't match verify_block

Hi folks - I'm going to close this for now. Please feel free to continue the conversation, and we can reopen as needed :+1:


Thank you!

Just wanted to say "Thank you" for the great work you have done. It really is a complete set for managing the bootloader on a chromebook. Thanks for creating and maintaining it. It helped me tremendously!!
In my case I have an Asus Flip C302, which is EOL since last year. I love this machine for internet browsing and some android apps (and even a very few Linux apps). But having no OS updates anymore, I though it would be a good idea to try a different OS on it. There are so many Linux distros and also ChromeOS Flex, FydeOS, OpenFyde, etc.
It was really a blaze to install the UEFI bootloader, from which I could test all the distros. Bad luck, none of them worked well. None of them had any audio. The tablet mode switch was not working either. So, the best still seems to be the official (even if EOL) chromeos version. Your scripts helped me perfectly to reflash the original bootloader extracted from a Google recovery image. Now I reinstalled the original image and everything is working again.  (I was so happy to see that you included even these options to reflash the original bootloader from the recovery image!)

I too want to express my gratitude for how easy you've made it to convert what would otherwise be e-waste. It took a bit of reading, but the process was clear and the conversion worked out smoothly. When I saw the Coreboot rabbit logo appear on the screen, I had to laugh as I now have a usable PC to do whatever I need with. Thank you!!


Check whether notation-scopes should be used

Description
Gather information about notation-scopes and check whether those should be used in #153 or whether they are not needed there.
Motivation
We need to qualify notations like #153 to avoid name clashes. This could be done by naming those notations ModuleName.NotationName but the Coq-way to do this would be to use notation scopes like
Open Scope ModuleName_notation_scope.
... NotationName ...
Close Scope ModuleName_notation_scope.

or NotationName%ModuleName.
Alternatives
The current approach of #153 tries to stick close to the usage of an function. Therefore for every notation NotationName defined there an explicit application @NotationName is defined as well as qualified versions ModuleName.NotationName and @ModuleName.NotationName. Those qualified versions have to be in their own module to be imported seperatly.
Additional Context

When using notation scopes we would need to use scope keys with the % notation as opening multiple scopes could lead to name clashes. This would however make the notations look not so pretty as the scope key has to follow after the whole notation. For a list constructor it would be (@MyCons Shape Pos a x xs)%MyData instead of @MyData.MyCons Shape Pos a x xs.
Another more important note is, that scope names can not contain a .. So we could not use the module name as a scope name but had to e.g. replace every . with a _. This could however introduce name clashes as a haskell module A_B and a haskell module A.B would share the same notation scope.
The issue, that notations are not imported with a From ... Require ... . sentence and have to be in their own module, that can be imported with a Import ... ., applies to scoped notations as well.
For those reasons the usage of notation scopes to qualify notations are not an improvement to the current approach of #153, which defines for each notation NotationName in module ModuleName an additional qualified version ModuleName.NotationName of that notation. Instead it introduces the problem of name clashes due to naming restrictions for scopes.


Azure publishing for gen1, gen2 images and Marketplace

What this PR does / why we need it:
This PR introduces some changes to the Azure publishing code so that we have means to publish gen1 and gen2 as well as to optionally - based on configuration - publish to the Azure Marketplace (again).
In particular:

introduce dedicated published images types for communityImageGalleries and Marketplace, each containing the images Hyper-V generation
change the release manifest to contain list for published images on communityGalleries and Marketplace
create a seperate gardenlinux-gen2 VM image definition for gen2 images in communityImageGalleries
publish the image twice in gardenlinux and gardenlinux-gen2 VM image definitions to have the image available for both Hyper-V generations
reenable the publishing code to Azure Marketplace
configure publishing to Azure Marketplace and to Azure community image galleries through publishing-cfg.yaml

Special notes for your reviewer:
This PR changes the published_image_metadata field of a release manifest to accommodate gen1 and gen2 variants of the same Garden Linux image.
Previously:
published_image_metadata:
  community_gallery_image_id: /CommunityGalleries/gardenlinux-13e998fe-534d-4b0a-8a27-f16a73aef620/Images/gardenlinux/Versions/934.0.0
  golive_operation_id: ''
  id: ''
  publish_operation_id: ''
  transport_state: released
  urn: ''

Now:
published_image_metadata:
  published_gallery_images:
  - community_gallery_image_id: /CommunityGalleries/gardenlinux-13e998fe-534d-4b0a-8a27-f16a73aef620/Images/gardenlinux/Versions/918.0.0
    hyper_v_generation: V1
  - community_gallery_image_id: /CommunityGalleries/gardenlinux-13e998fe-534d-4b0a-8a27-f16a73aef620/Images/gardenlinux-gen2/Versions/918.0.0
    hyper_v_generation: V2
  published_marketplace_images:
  - golive_operation_id: ''
    hyper_v_generation: V1
    publish_operation_id: ''
    transport_state: released
    urn: gardenlinux:greatest:918.0.0
  - golive_operation_id: ''
    hyper_v_generation: V2
    publish_operation_id: ''
    transport_state: released
    urn: gardenlinux:greatest-gen2:918.0.0

This change would require changes to code that further processes the release manifests (e.g. landscape setup) as well, so do not merge this PR until such code is able to deal with these changes to the data model.
Release note:

- allow publishing gen1 and gen2 images to community galleries
- optionally reenable publishing through the Azure Marketplace

- structure of release manifest for Azure images changed to contain different variants of an image

/invite @ccwienk @AndreasBurger


Achieving Security Awareness Through Social Engineering Attacks

Related/accompanying the Tech@Auth0 series: https://github.com/auth0/blog/pull/1698

@scottmathson-auth0 In this case, it's better to relate the post to our other security content :)


Parametrize / automate process_string parameter in nightlights module

Hi @butchtm , just wanted to flag for future improvements. I have a feeling the process_suffix  will change depending if they have changes in the preprocessing stages. It's possible that they will upload new versions, with a different process_suffix. In that case, since it's hardcoded, we might not find the correct url.
Possible Solution

could we parametrize make_url to accept a custom process_string ?

Originally posted by @tm-jc-nacpil in https://github.com/thinkingmachines/unicef-ai4d-poverty-mapping/pull/75#discussion_r1070847302

implement as per request!


clash-verge-rev: 1.7.5 -> 1.7.6; clash-verge-rev: build from source; clash-verge-rev: add bot-wxt1221 as maintainers;

Description of changes
Just build from source.
https://github.com/NixOS/nixpkgs/pull/324541 https://github.com/NixOS/nixpkgs/pull/318525 are doing the same thing but they haven't got any activities.
Anyway, It is already tested by me.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4437

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

1 package built:

clash-verge-rev

A lot of packages are introduced here. nix-autoupdate-script won't work. feel free to review it but do not merge it. I'd love to write an update script for this.

@SuperSandro2000 Done.

https://github.com/NixOS/nixpkgs/pull/318525/files#diff-b4acdeafd59cb1518d52ce1aa73551f68c00364a4629607655fc7cba3e2a49ccR60

@linsui Done

@linsui Done.

Please add empty lines between blocks.
There are some unused args. Please remove them. You can use an LSP to help you find them.
1.7.7 has been available, please update.

@linsui Done.

We can use linkFarm:
linkFarm pname {
  "bin/clash-verge-service" = "${service}/bin/clash-verge-service";
  "bin/clash-verge" = "${unwrapped}/bin/clash-verge";
  "bin/verge-mihomo" = "${mihomo}/bin/mihomo";
  "lib/clash-verge/resources/geoip.dat" = "${v2ray-geoip}/share/v2ray/geoip.dat";
  "lib/clash-verge/resources/geosite.dat" = "${v2ray-domain-list-community}/share/v2ray/geosite.dat";
  "lib/clash-verge/resources/Country.mmdb" = dbip-country-lite.mmdb;
  share = "${unwrapped}/share";
}

@linsui linkFarm can't be. clash-verge shouldn't be symbol linked because it find mihomo in it's runtime directory.

@Aleksanaa Done

@Aleksanaa Ready for review again.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4504

@SuperSandro2000 Why need meta? They won't be used.

@linsui @Aleksanaa Could you please review again?

Oh no.

programs.clash-verge.autoStart = true;
cp: cannot stat '/nix/store/an7azv5n3cldavi61i96ffpiysa56463-clash-verge-rev-1.7.7/share/applications/clash-verge.desktop': No such file or directory

@Hobr Oh no.


[Request]"text" type enhance

Let the "text" type support value settings, do not output parameters including value when nothing is filled in.
Optional:regular expressions to limit the input characters and number,
for example:
{
	"type": "text",
	"label": "text box",
	"id": "text1",
	"value": " -t",
	"regex": "[A-Z]{1,4}"
},

Or you have a better idea to add a new type.

That's a good suggestion.
But I think the validators should be used to raise errors, not to remove parameters like -t.
So, I'll add another flag optional to ignore the error and to replace its value with an empty string.
Your example will be like this.
"command": "my_exe %text1%",
"components": [
    {
        "type": "text",
        "label": "text box",
        "id": "text1",
        "optional": true,
        "prefix": " -text=",
        "suffix": " -flag"
        "regex": "[A-Z]{1,4}"
    }
]

The command when you type ABCD in the text box.
my_exe -text=ABCD -flag

The command when you type 1234 in the text box.
my_exe

As a workaround, you can use multiple definitions for now.
I mean, you can provide another GUI that doesn't have the text box.
"gui": [
    {
        "label": "With Text",
        "command": "my_exe -t %-%",
        "components": [
            {
                "type": "text",
                "label": "text box"
            }
        ]
    },
    {
        "label": "Without Text",
        "command": "my_exe",
        "components": []
    }
]

Supported at #48


Zcoin atomic swap to be merged

An atomic swap has been done between Decred testnet & Zcoin testnet
The output of the swap has been pasted in the file below:
There remain some issues with estimatefee and/or estimatesmartfee but these can probably be resolved either with talked about changes to the atomic swap cmd code or in the xzcwallet/xzcd zcoin-specific code. The swap is nonetheless successful.
To view the transactions on the Zcoin blockchain please use the temporary explorer at:
http://<IP_ADDRESS>
API Example: http://<IP_ADDRESS>/api/getrawtransaction?txid=3583e1b9f2188862f0648e54ea29c4c2d8e8f31dfb015be80f18918cd106eb3f&decrypt=1
Note: warning: falling back to mempool relay fee policy
xcat-xzc-dcr_2018_01_13.txt

Added 1 more commit:
Changes for "secret size attack changes"

Added 1 commit:
"[main] update for secret size attack on cross-chain hash time lock sm…"
Updated deps

Decred atomicswap

Added 1 commit:
"[main] update for secret size attack on cross-chain hash time lock sm… "
Updated [xczd] for AtomicSwapDataPushes
https://github.com/zcoinofficial/xzcd/blob/ae307d1ae9070c5434a6a203992db0ad35712e96/txscript/standard.go#L630
Updated all the vendor dependencies

Zcoin
Zcoin v<IP_ADDRESS>  "fundrawtransaction now applies fees"
estimatefee/estimatesmartfee - all code exists and is enabled but the # transactions / block is not considered statistically significant. Experimenting with changing bitcoin parameters shows that estimation of fees works and will be available when transaction volumes increase.

Can you rebase+squash this and resolve the conflicts with the Gopkg.toml/lock files?  To resolve those conflicts, you can revert both back to their state on master, add your new deps to Gopkg.toml, and then re-run dep ensure to update the lock without modifying anything else already in the lock.

This is getting in a state - close this and I will do a new PR


DOC: Add more information to entropy docstring

Reference issue

Closes gh-3421
What does this implement/fix?

This PR adds information to the docstring for scipy.stats.entropy giving an overview of the relationship between entropy, Kullback-Leibler divergence, and cross-entropy. The significance of these quantities in information theory is also briefly stated. In addition, relative entropy is explicitly given as a synonym for Kullback-Leibler divergence and an example has been added showing how to calculate cross entropy using the function entropy.
Additional information

There was concern expressed in gh-3421 that the behavior of entropy may be surprising to some users. Rather than adding new functions to the API and/or making backwards incompatible changes to entropy, I think it's reasonable just to add more information to the docstring to clarify the behavior of the function. @mdhaber let me know what you think.

A few more suggestions in steppy/scipy#1, but this is close!

Thanks @mdhaber for the improvements!


Added extra final step

The tutorial gets you to create two windows, One has AE enabled, one doesn't, But you only ever try the code in the one with it enabled. You need to also try it in the other window to see what happens, or it misses a key point of the tutorial.

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

#sign-off


ZEVA - allow Zero value in model year LDV Sales field

Title: Allow a Zero value to be entered in the model year LDV Sales input in Model Year Reports and Supplementary / Reassessment reports.
Description: Currently if a user enters a zero in the field - [Year] Model year LDV sales - in the supplementary report or reassessment recommendation pages it will thrown an error. But we would like the it to be possible to enter a zero value in this field.
Purpose and benefit to user:
The user will not experience an error if they enter a zero value in this field.
Acceptance Criteria:

[ ] Given I am a ZEVA User or government analyst, When I am working on a supplementary report or reassessment recommendation, then I want to be able to enter a zero value in the [Year] Model year LDV sales field.

Development Checklist:

[ ] Allow 0 float value as a valid save object. Check if there is code that replaces 0 with null or validation that doesn't accept 0 in this field.
[ ] Ensure that saving a 0 value updates the calculated credit values below in the form and saves those changes when submitted.

Notes:

Hey team! Please add your planning poker estimate with Zenhub @emi-hi @jig-patel @JulianForeman @tim738745 @vibhiquartech


Add als configurations

Adding example als hyperparameter configurations.

You could add similar extra example config to the other two examples if you like too.

actually, this change isn't needed.
I didn't even know that another ref config existed...
https://github.com/OryxProject/oryx/blob/master/app/oryx-app-common/src/main/resources/reference.conf#L18-L34
I think we should update the documentation to raise the awareness. :)


Optimistically staged files are inactive but clickable while status is running

Testing #167418
Once an item moved between staging its buttons become dead clicks.
https://user-images.githubusercontent.com/8599/204858780-bf0b6db4-e572-44e2-8c9d-807c09c782a4.mp4
This causes extra confusion as there is no progress indicator. Maybe we can disable the buttons as status is pending or provide more feedback that git state is pending to apply the git update.

Thanks for the recording. The decision not to show the progress indicator for commands that support optimistic UI updates was deliberate. It felt weird that a resource is moved from one group to another yet there continues to be a progress indicator while we update the model and truly complete the operation. Given that you are able to stage multiple resources one after the other this seems like a bug to me.

@digitarald, very nice catch! After debugging this I have uncovered another issue related to optimistic ui updates - #169750.


[Feature Request] - AI Assist to build with FVM

Is your feature request related to a problem? Please describe.
Hi there,
FVM is a popular tool for managing Flutter SDK versions. However, many developers struggle with keeping up with the latest syntax and best practices. To address this, we created a custom AI Assist trained on the FVM repository code and issues
Describe the solution you'd like
Please try it here.
You can also add it as a badge in the README to help developers landing on the repo manage their Flutter SDK versions more efficiently.

hope this helps!

Wow this is just spam and abuse. Nobody asked for this and I don't think anyone actually has a problem using fvm because it is a pretty simple tool.


feat: add prometheus exporter host and port env vars

Signed-off-by: naseemkullah<EMAIL_ADDRESS>
Which problem is this PR solving?
solves #1852
Short description of the changes
Added env vars for prometheux expoter host and port. Defaults are '<IP_ADDRESS>' (all addresses) and 9464 respectively.

@naseemkullah FYI lint is failing

@naseemkullah FYI lint is failing

Can this be merged @open-telemetry/collector-builder-maintainers ? Seems like unit tests are timing out

Tests keep timing out. Anyone know why?

Tests keep timing out. Anyone know why?

I tried to run the exporter-prometheus tests locally and quite of them fail and test process is not ended. I assume there is some leftover server avoiding this.
Is there anything special needed to run them local?

Tests keep timing out. Anyone know why?

I tried to run the exporter-prometheus tests locally and quite of them fail and test process is not ended. I assume there is some leftover server avoiding this.
Is there anything special needed to run them local?

Thanks! I must have forgotten to shutdown after tests, stay tuned!

The first failing test for me is should start the server by default and call the callback.
It seem this test tries to start the server using NaN as port to listen which throws. This results in an error log but the test itself then times out.

The first failing test for me is should start the server by default and call the callback.
It seem this test tries to start the server using NaN as port to listen which throws. This results in an error log but the test itself then times out.
You could move the exporter.shutdown() into a afterEach block to avoid that a failing test has a leftover server.

Thanks for the tip!


swaggerui-files can't be loaded, responds with 400

Context

hapi-swgger version: 7.4.0
hapi version: 15.0.3
hapi-server is set up with glue 4.0.0

What are you trying to achieve or the steps to reproduce ?
I just installed hapi-swagger, together with inert and vision and registered it in my glue-manifesto like:
    { plugin: 'inert' },
    { plugin: 'vision' },
    {
      plugin: {
        register: 'hapi-swagger',
        options: {
          info: { title: 'Test' },
        },
      },
    },

What result did you get?
 But those files can't be loaded.

The file /swagger.json can be loaded.
As I didn't find anybody else having this issue, I guess there might be a problem with any server-configuration. Does anybody have a clue?

Never mind! I planned to serve the docs as static files via S3 and Cloudfront anyway. And as long as /swagger.json loads, everything works for me. Thanks for this great hapi-plugin!

has this been solved?
I get this:

@alichherawalla i believe it has. If you are having trouble try opening and issue with full working example project that replicates your problem so that others or myself can take a look.


Add Vision Middle School

https://vision-m.goept.kr/vision-m/main.do

@Ren-deRing First stage of verification passed, official domain is vision-m.goept.kr as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

Pull request merged. Thank you!


vanilla JS for UI

Did you consider using Vue, React, etc.? Sorry, not trying to be that guy.

Great question! I started this project out to solve a pretty specific problem for myself and it has grown quite a bit since the initial prototype. The mentality being to spend as little time as possible on it to solve the problem and keep things simple - after all it's just me using this thing right? 😄. So at the time bringing in Vue, React, etc. didn't make sense to me. But as this has grown, it's getting more difficult to maintain and extend with vanilla JS. So something like react boilerplate (or some vue.js equivalent) might be better in the long run as this project matures.

If you're not opposed, I'd like to put together a React-based example using create-react-app in another repo to see what a refactor could look like.

Not at all! That sounds awesome!

Excellent! I'll try to get a first pass up tomorrow. I'll link to the repo here when it's up.

I'm kind of wondering what using web components would be like. Seems like a good place to tinker with them since it's sandboxed to Chrome anyway. 🤔

@arkon pretty nice only need things to work in the Chrome sandbox 😄 I'd like to avoid using web components for now, since the feature set is relatively small and we'd have to do extra work to get a11y features working smoothly.

Awesome @hharnisc! I got an example spun up with create-react-app. You can view it here: https://github.com/raygesualdo/retabbie
Currently, it doesn't function because I haven't been able to mock the chrome extension API. I may take a stab at that. But all the functions that interact with that API are unchanged.
Ideas for continued improvement:

[ ] Use more async/await in utilities
[ ] Create single "promisify" wrapper for all the Chrome APIs
[ ] Implement UUIDs with tab groups
[ ] Add and remove tab groups based on UUID

Have had a pretty busy week and hadn't had a chance yet. But I just took a quick look and this is looking awesome. I'll be out the next week so I won't be able to dig into it until then. On that list there the biggest thing in my mind is the wrapper for Chrome APIs. Would want to make sure this works with the current data people already have.

Absolutely. Wrapper would only be a syntactical nicety. Wouldn't change how data is pulled from chrome.storage.sync.

Hey @raygesualdo had a chance to look at the refactor you've got in place. A couple things I noticed

It would be nice to see components broken up into smaller files
Was hoping to break out google analytics calls into their own actions
Would like to see entirely stateless components
Create react app implementation looks pretty clean, nice work there!

Would you mind taking a look at the react branch in this repo? I've been using browserify (and related tooling) to get a pretty nice DevX and breaking things up into smaller components. The other thing is that I'm using Redux patterns more like an event bus - and eventually plan on calling google analytics somewhere in the action dispatch chain (much like how https://github.com/zeit/hyper does it).

Hi @hharnisc! Below are my thoughts:

The application in my repo could very easily be broken up into more components. It may not be readily apparent because I used styled-components, but common.js contains all individual components. I kept them in a single file so it was easy to import. They could just as easily be split into multiple files. App.js could also be split up further as well.
With the exception of Container.js, all the components are stateless components.
I took a look at the react branch. Lots of good things in there! I can see what you're saying about smaller components as well. A thought about redux: most small applications (which I think applies in Tabbie's case) don't require a full redux implementation. It's a lot of cognitive overhead for very little gain, IMHO. Feel free to push back on that. This is why I created the Container.js in my repo. It is effectively acting as our state management layer. Tabbie's functionality has so little surface area (which is a good thing) that it doesn't require extensive logic to get everything working. Redux seems to add complication when none is needed. Thoughts?

Hey @raygesualdo so great thought's you've laid out here! I think we share a lot of thoughts around keeping things simple and I can see where you're coming from with points 1 and 2.
Did a bit more thinking around your 3rd point around using Redux. I think you're exactly right there IF the current feature set was complete. With some of the features I'd like to add, particularly #9 #10 #11 #26 add enough complexity to warrant the use of Redux in my mind. These are features that could add more control surfaces that would be difficult to manage with a hand rolled solution.
Another big one is #28 - to fully solve that problem a backend solution would need to be implemented. I think that using Redux as the event bus is going to de-couple the syncing mechanism (chrome local storage, sync storage or some other backend). You'd likely have to build something that looked like Redux here either way.
Really enjoyed your thoughts on this, it's great to have a push to keep things as simple as possible!

Hi @hharnisc, I'm glad we've been able to talk through this as well!
I understand now why you want to include Redux. It will add significant value when expanding Tabbie's feature set. What should the next steps be for continuing development here? I would love to be a part of the React/Redux switch-over.
Additionally, I've been thinking about a backend solution. I think there may be a way to implement some serverless architectures combined with object stores to provide what Tabbie needs from a backend solution for free. It's a very simple solution, but I think it could work. It could also be open-sourced so others could host it themselves. We can continue discussing here or feel free to DM me on Twitter.

Hey @raygesualdo sorry for taking so long to get back to you here. Have been playing around with this the past couple weekends and needed some solo time to figure out how to architect the bridge between redux and chrome storage. I ended up using middleware to handle the side effects. There's some room for improvement, but I think this is looking pretty clean.
The other cool thing here is that middleware could be used to hook into another storage engine. You pretty much just need to hook into the ADD_*/REMOVE_* events.
Would love to hear your thoughts around implementing a serverless backend. I'd imagine they're free until you hit a certain level of traffic. At the moment this is pretty low volume so I bet this would be in the free tier of most services for a while.

@raygesualdo would you be up for opening another issue hear with your thoughts on backend solutions?


LSTM dropout_W vs Dropout

Is there any difference between using a Dropout layer before an LSTM and using the argument dropout_W of that LSTM layer?
Like this:
model.add(Dropout(0.5)) model.add(LSTM(100))
model.add(LSTM(100, dropout_W=0.5)
Also, in Zaremba et al paper of RNN regularization, they say dropout should never be applied to recurrent connections (dropout_U = 0). Why do I see many examples with dropout_U > 0? Am I missing something?
Thank you.

Hello, I don't know, but by looking at the source, they reference the paper for the dropout justification : - A Theoretically Grounded Application of Dropout in Recurrent Neural Networks
I guess there are some advanced usage like "consume_less" mode which might provide an explanation for including the dropout, inside the LSTM rather than before and after. (Like grouping both matrix W and U into one for performance, but you then need to group dropoutU and dropoutW)

In the paper cited by @unrealwill the authors provide a bayesian viewpoint on dropout in RNNs (as compared to the ensemble method perspective). Following their conclusions, they propose a theoretically motivated dropout method for RNNs and their variants.
Unlike previous techniques with varying dropout masks for different time steps and no dropout in the recurrent connections (like the Zaremba paper), the same network units are dropped at each time step.
The authours experimental results lead to the suggestion that this dropout method is superior to prior approaches.
This makes dropout_U a valid choice.

To anyone coming to this issue thread more recently:
dropout_U has now been renamed to recurrent_dropout, as seen in legacy_recurrent_support.

@davidlenz has there been significantly more papers supporting better models when dropouts are in the recurrent layers, than dropping before/or after LSTM's?

For recurrent_dropout, is there Model class API? liked Dropout.


Cloud App Security has been renamed Defender for Cloud Apps.

Cloud App Security has been renamed Defender for Cloud Apps.
I'm responsible for Defender for Cloud Apps documentation. Feel free to be in contact with me if you have questions about the rebrand.
Thanks,
David

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

ID: b11d0b9e-11fa-5df0-ae63-c91ccd1bcf31
Version Independent ID: 9f2b9aaf-8b41-4871-556d-04dfaf5a007d
Content: azure.mgmt.securityinsight.models.StatusInMcas enum
Content Source: preview/docs-ref-autogen/azure-mgmt-securityinsight/azure.mgmt.securityinsight.models.StatusInMcas.yml
GitHub Login: @VSC-Service-Account

Dup of #22571


JS fails to generate mnemonic

When creating a new account, the js side fails to create a mnemonic here:
https://github.com/encointer/encointer-wallet-flutter/blob/770a5bab5608b82d6df6fb345674778a7f1ce2bf/lib/js_service_encointer/src/service/account.js#L21
Thus, no account can currently be created.
not sure when this was introduced

I recently generated an account on iOS. probably v0.8.2

most probably upgrade to >2.x version of polkadot api?

This is my guess too.

interestingly, it seems to work if no account has been registered with the app before, but if we navigate from the overview screen to the CreateAccountEntry it does not work anymore.


The application requires the file to be unzipped.

I was try to train a test use lib/images/style/starry-night.jpg,but I have got
"The application requires the file to be unzipped. Unzip? [y/N] "
so. what should I do,plese?

That alert is made after you've completed downloading the MSCOCO dataset zip. Just type 'y' and hit enter.


Fix windows test failures

This PR addresses the problems raised in #24.
I would suggest possibly setting up error testing on https://www.appveyor.com/ for windows if it isn't a big inconvenience. These issues were caught through CI testing on conda-forge.

Coverage increased (+0.02%) to 93.789% when pulling 01c02a9b98cbb5da79e462e96b0689f4ca779cdc on synapticarbors:fix-windows into<PHONE_NUMBER>104f4d0daeb56aefee3a47fbfa71d2 on liampauling:master.


testes

asdfasdfa sdfa d

@flaviohcfreitas, 😕 ?

Out of curiosity, what you are trying to test?

@elevatebart I will close this :)


add namespaces for parent attributes

Fixes #487

Updated the bandit_parent and bandit_sibling to _bandit_parent and _bandit_sibling` so they are denoted as private attributes

@ericwb - any chance we get this merged as it’s breaking CI pipelines?


Add missing Russian translation

A new inspection was created.

A new inspection was created.

The inspection completed: No new issues

The inspection completed: No new issues

Thank you @lotarbo ! Merged, will be tagged tomorrow with a few more non-breaking changes.


Add ability to overwrite the Kubernetes url and SSL parameters

This does a little more than what was requested in #275 but I need to be able to use a custom url if I want to use my custom ca file so I figured I could add the verify_ssl at the same time.
Closes #275

@repeatedly
I need this too, when do you think you will merge?

Sorry for the late update I missed the latest notifications.
I updated the PR based on @repeatedly and @ganmacs 's feedbacks.
Let me know if you need me to do other changes.
Thanks!

Why is this not in yet? It seems like a crucial part to get fluentd Kubernetes running on Clusters which use a custom CA for the Kubernetes API.

Sorry for the delay. I added some comments.
And if possible, could you please write a more descriptive commit message... ("Update with the feedback from ganmacs" doesn't make sense to other developers... )

Sorry for the late reply.
There are some comments I really don't understand what you meant. Could you develop please?
For the commit message aren't you going to use "Squash and merge" when merging in master to avoid having several commits?

Hi,
FYI I rebased the branch against the latest master, fixed a typo in a variable name, updated the template based on the remaining unaddressed feedback and regenerated the images for version 1.3, 1.4 and 1.7 (current) as this PR was addressing 1.3 when it was originally opened.
Let me know if there are still any blocker to get this merge please.
Thanks,
Joseph

Thanks for working on this.
I will release new image soon.

Awesome, thanks a lot! :)


Allow size to equal max_size for resizes on longer edge

🚀 The feature
Allow max_size == size in torchvision.transforms.Resize()
Motivation, pitch
torchvision.transforms.Resize() does not provide a clean interface for resizing images where the maximum dimension is based off the longer edge.
Alternatives
No response
Additional context
No response

I would be in favor of exactly this feature as well.
I want to do a resize where I provide the dimension for the longer edge, not the shorter edge.
Did you find another solution, or why did you close the issue immediately?

@sweber1 we followed-up with https://github.com/pytorch/vision/issues/8358, this will be available in the next release

@sweber1 we followed-up with #8358, this will be available in the next release

Ah great, thank you!


Openunison Hashicorp Vault integration example

Hello there!
I have finished integrating Openunison with Vault a couple of days ago and I want to share my knowledge. Where can I do that?
Here is my manual: https://github.com/drengskapr/manuals/blob/main/openunison-vault-integration.md
I would be happy if it ends up in your documentation!

@drengskapr this is FANTASTIC.  It's great timing too, because i was just about to work on this integration.  I've got the automation of generating SSO between kubernetes and vault, but hadn't yet gotten to SSO between OpenUnison and Vault.  Would you mind submitting a PR?  That way you get credit for having written it.  To get this integrated into the docs:

Fork https://github.com/OpenUnison/openunison.github.io
Copy your images to assets/images/apps/vault
Create docs/applications/vault.md with your integration guide, change your image tags from ![roles](pictures/openunison_roles.png) -->
Submit PR

Thanks again, this is fantastic!

@mlbiam, sure I'll do it.

merged.  thanks again @drengskapr !


Transparent macos-titlebar-style not honoured when background is close to black

When background = #0d0d0d (or brighter), the titlebar transparency works as expected.
When background = #0c0c0c (or darker), the titlebar is not transparent and behaves as if set to native.

Screenshots

This looks like it's the effect of some code that was added in https://github.com/ghostty-org/ghostty/commit/f086bff65125c49dd11ebaa4cc75fb2bc0f5f41e to make sure it's possible to distinguish the currently selected tab on very dark backgrounds. It could be handled more gracefully than this though.

I think it's these two assignments, conditional on backgroundColor.luminance < 0.05.
https://github.com/ghostty-org/ghostty/blob/f086bff65125c49dd11ebaa4cc75fb2bc0f5f41e/macos/Sources/Features/Terminal/TerminalWindow.swift#L554-L555
Selected tabs are distinguishable based on the colour of the title and indicator, so I suspect this isn't necessary.


Tooling updates

This PR

bumps pre-commit, black/blacken-docs, ruff to their latest versions
uses actions/checkout@v4 in GHA
uses<EMAIL_ADDRESS>with Python 3.11
adds min Python dependency on pyproject.toml, and drops the black target in pre-commit (ref)

Thanks @zerolab!


enhancement: added different color to destroy button

This will serve as a visual help to avoid unwanted destroy executions

Hello @jcanizalez, @alfespa17;
Could you please deploy a beta version of this? I want to use this feature.

Hello @jcanizalez, @alfespa17;
Could you please deploy a beta version of this? I want to use this feature.

You can check the release in some minutes @ilkerispir


New version: JetBrains.MPS.EAP version MPS-.build

Installation timed out.
Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 1435
Microsoft Reviewers: Open in CodeFlow

PackageVersion broke.

It was just a matter of brackets😢(fixed in https://github.com/vedantmgoyal2009/winget-pkgs-automation/commit/b13fce4948ee83518c641b7e427f186064f649ca)


Update translation.json

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] i18n translation has been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ..., provide screenshots if necessary)

minor fixes in the en translation

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

nope

Other information:

Thanks for the help!


Rework interrupts, add mip & mie CSRs, add non-maskable interrupt

This PR adds the mip and mie CSRs and adds three new interrupt input signals: external (connects to a PLIC), software interrupts (connects to a memory-mapped register) and timer (connects to a timer module). In addition, it removes the legacy internal interrupt controller and instead adds 15 fast interrupt lines connected to the mip CSR and controlled through the mie CSR. Together with a memory-mapped software interrupt register and timer module (both not part of Ibex), these changes allow to implement what others refer to as core-local interrupt block (CLINT).
Also, this PR adds one non-maskeable interrupt (NMI) and a three more CSRs to allow for nested interrupts and recoverable NMIs. This extension is not part of the RISCV standard. But might be added in the future: https://github.com/riscv/riscv-isa-manual/issues/261
Finally, this PR also updates the documentation accordingly.

The first two clean-up patches are ready to go in with minor nits. Please do so ahead of the last commit to keep the PR small and manageable by creating a new PR with only these commits.

Thanks @imphil for your feedback. I have created a new PR #156 for the first two commits as suggested. Once it is merged, I will remove these two commits from this draft PR.

This PR contains all the changes for Ibex required to implement the standard compliant CLINT + NMI. It is ready for review but since it might break the setup of downstream users, I am leaving it as a draft currently.

I clicked ready for review which removed the draft status. Unfortunately, I cannot undo this. This PR is ready for review but please do not yet merge!

"draft" is typically used to prevent reviews, so removing that is the right thing to do. I'll leave the merging up to you.

This PR adds the mip and mie CSR to implement a standard compliant core-local interrupt block (CLINT). It adds three new interrupt input signals: external (connects to a PLIC), software interrupts (connects to a memory-mapped register) and timer (connects to a timer module).

Is the naming in this PR title and description correct? I think that the "CLINT" terminology was introduced by SiFive, and they seem to use it to either refer to the block containing memory mapped msip, mtimecmp and mtime registers, or to the combination of that block and the relevant CSRs. This PR obviously just contains CSR changes.

Is the naming in this PR title and description correct? I think that the "CLINT" terminology was introduced by SiFive, and they seem to use it to either refer to the block containing memory mapped msip, mtimecmp and mtime registers, or to the combination of that block and the relevant CSRs. This PR obviously just contains the CSR part of that.

Thanks for your feedback @asb . I will adapt title, description + documentation to avoid confusiong regarding this.

Thanks a lot Philipp for reviewing the PR and for your feedback.

Little update here: Looks like the Smrnmi extension (Resumable Non-Maskable Interrupts) was ratified in July. Might be worth considering for some future Ibex release.


chore(deps): update all non-major dependencies

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

eslint-config-prettier
^8.7.0 -> ^8.8.0

eslint-import-resolver-typescript
^3.5.3 -> ^3.5.5

jsii-diff
^1.78.1 -> ^1.81.0

jsii-docgen
^7.1.28 -> ^7.2.9

jsii-pacmak
^1.78.1 -> ^1.81.0

prettier (source)
^2.8.4 -> ^2.8.8

ts-deepmerge
^6.0.2 -> ^6.0.3

Release Notes

prettier/eslint-config-prettier
v8.8.0
Compare Source

Added: [@typescript-eslint/lines-around-comment].
A bad version was accidentally published and it can't be unpublished, apologies for the churn.
v2.8.7
Compare Source
diff
Allow multiple decorators on same getter/setter (#14584 by @fisker)

// Input
class A {
  @decorator()
  get foo () {}

  @decorator()
  set foo (value) {}
}

// Prettier 2.8.6
SyntaxError: Decorators cannot be applied to multiple get/set accessors of the same name. (5:3)
  3 |   get foo () {}
  4 |
> 5 |   @decorator()
    |   ^^^^^^^^^^^^
  6 |   set foo (value) {}
  7 | }

// Prettier 2.8.7
class A {
  @decorator()
  get foo() {}

  @decorator()
  set foo(value) {}
}

v2.8.6
Compare Source
diff
Allow decorators on private members and class expressions (#14548 by @fisker)

// Input
class A {
  @decorator()
  #privateMethod () {}
}

// Prettier 2.8.5
SyntaxError: Decorators are not valid here. (2:3)
  1 | class A {
> 2 |   @decorator()
    |   ^^^^^^^^^^^^
  3 |   #privateMethod () {}
  4 | }

// Prettier 2.8.6
class A {
  @decorator()
  #privateMethod() {}
}

v2.8.5
Compare Source
diff
Support TypeScript 5.0 (#14391 by @fisker, #13819 by @fisker, @sosukesuzuki)
TypeScript 5.0 introduces two new syntactic features:

const modifiers for type parameters
export type * declarations

Add missing parentheses for decorator (#14393 by @fisker)

// Input
class Person {
  @(myDecoratorArray[0])
  greet() {}
}

// Prettier 2.8.4
class Person {
  @myDecoratorArray[0]
  greet() {}
}

// Prettier 2.8.5
class Person {
  @(myDecoratorArray[0])
  greet() {}
}

Add parentheses for TypeofTypeAnnotation to improve readability (#14458 by @fisker)

// Input
type A = (typeof node.children)[];

// Prettier 2.8.4
type A = typeof node.children[];

// Prettier 2.8.5
type A = (typeof node.children)[];

Support max_line_length=off when parsing .editorconfig (#14516 by @josephfrazier)
If an .editorconfig file is in your project and it sets max_line_length=off for the file you're formatting,
it will be interpreted as a printWidth of Infinity rather than being ignored
(which previously resulted in the default printWidth of 80 being applied, if not overridden by Prettier-specific configuration).

<div className='HelloWorld' title={`You are visitor number ${ num }`} onMouseOver={onMouseOver}/>

<div
  className="HelloWorld"
  title={`You are visitor number ${num}`}
  onMouseOver={onMouseOver}
/>;

<div className="HelloWorld" title={`You are visitor number ${num}`} onMouseOver={onMouseOver} />;

voodoocreation/ts-deepmerge
v6.0.3: Update dependencies
Compare Source

Configuration
📅 Schedule: Branch creation - "before 1am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


On Department edit popup, add drop down for Roles

There can be multiple Roles, so a simple drop down will not work.


Corrected punctuation error

Fixed typo ("it's" means "it is". The possessive pronoun is spelled "its".)

This typo was fixed in a different submitted commit.
Commit: https://github.com/googlesamples/apps-script/commit/622fff29de3479bb74e1d93a33cd7616623522d7
Issue: https://github.com/googlesamples/apps-script/issues/8


"Integration failed to setup" on Home Assistant 2022.10.3

The latest version of hassio seems to not like something about this plugin. It's failing to start with the following error logs:
custom_components.ge_home.entities.common.ge_erd_number::GeErdNumber is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom integration author.
custom_components.ge_home.entities.ccm.ge_ccm_brew_temperature::GeCcmBrewTemperatureNumber is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom integration author.
custom_components.ge_home.entities.ccm.ge_ccm_brew_cups::GeCcmBrewCupsNumber is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom integration author.

Use the prelease version, it resolves these issues.


Issue of suspiciously slow inference

Hi authors,
Thank you for the great work! I've run into the problem that there's no way I can get the same inference speed as mentioned in the paper. The paper states 115ms, however I have tried measuring the time on the RTX 3060 using different methods such as the benchmark method in run_rpn.py and the benchmark method in run_fcos.py. I also measured the forward pass time during evaluation in the script run_fcos.py. I got values of 3 seconds, 5.6 seconds and 8 seconds respectively. Could you advise me what is my measurement mistake, or under what conditions was the time measured as mentioned in the paper?

Hi. One thing we didn't make crystal clear in the paper is what exactly is the "inference time without postprocessing". We considered the bounding box decoding and proposal filtering as postprocessing, which is located here: https://github.com/lyclyc52/NeRF_RPN/blob/2f1d4ce6b2544433fb3e6ce9cf829bac587689cd/nerf_rpn/model/rpn.py#L507-L512
To reproduce the inference time, you may simply comment the lines above out. We rerun the benchmark on an RTX 3090 using the pretrained weights (anchor based, ResNet 50), and the result is 80 ms. I believe the data in the paper is from a 1080ti running a similar model.
Sorry for the confusion. Hope this helps.

Thank you for your response!
Indeed, it became much faster, the benchmark anchor based, ResNet 50 shows Average inference time: 206.5343 ms, std: 0.7214 ms.  on RTX3060.
Also for fcos model I found out that the main time is spent on nmscalculations.
https://github.com/lyclyc52/NeRF_RPN/blob/2f1d4ce6b2544433fb3e6ce9cf829bac587689cd/nerf_rpn/model/fcos/utils.py#L109-L124

Yes, we regard NMS as part of the post-processing and exclude it in the timing.


Move themes to plugin directory. Fixes #2372

PR #2241 introduced a regression locating fonts.
The contents of public/css/assets/ were mistaken as original work and not moved into the correct vendor/ location. This PR moves these files to the correct location and closes #2372.

(not ready for pull)

Note: #2374 is causing the failed test; tests should pass if it is merged

LGTM

LGTM


Replace SimSun, MingLiu, MSGothic, GulimChe with one (or four?) decent monospace fonts.

From @be5invis on May 12, 2017 5:35
THEY ARE UGLY, REALLY.
The new font(s) should be:

Exact half-width monospace, to prevent full-width glyphs being stretched or alignment being broken.
No bitmap. In vector.
Well hinted.
Follows regional (CCJK) orthographic standards and aesthetic habits.

Copied from original issue: Microsoft/WSL#2091

From @SRGOM on May 15, 2017 10:56
Oh, and while you're at it, can you ask MS to comission someone to make a good non-Ming font that covers CJK-ext-2?
Hanazono and MingLiu_HKSCS-ExtB both look horrible.
Thanks!

From @SRGOM on May 15, 2017 10:53
I want this too but I highly doubt anyone would (or could) help you here. If you're looking for a font that works well in the X env, I doubt this team will tries to mess too much with the ubuntu userland. Even if they did, their expertise is very far from understanding fonts.
Outside X env, I doubt their team can touch much anway. This belongs to a different team.
I just noted that you're at MS yourself. It looks to me like you're closer to help solve this problem than anybody else. And while you're at it, can you have MS remove all the "Ming" fonts from the following: "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink"?
It's almost universally accepted that Ming fonts are not suitable for screen. So I would like them not being linked by default

From @be5invis on May 15, 2017 17:32
@SRGOM Cover Ext BCD? This may take $10M and 5 years to make that font.

From @zadjii-msft on May 15, 2017 16:47
@be5invis Hey, could you open a mail thread with richturn AKA @bitcrazed (he'll CC the rest of the team) on this? I'm sure we'd be more than happy to get some help getting better fonts in the console by default :)

From @SRGOM on May 29, 2017 4:39
@be5invis: I am not arguing with you, I'm only trying to understand-  but do you guys not use Chise IDs or cjk decomposition or something similar for making fonts? In that case wouldn't the work be greatly reduced?

From @be5invis on May 29, 2017 18:28
@SRGOM
Using IDS cannot create a typeface fitting the quality requirements of type designers. The parts will interfere so you cannot directly combine them together.

@bitcrazed
Fixing this issue is basically to find a good, exact 1/2-em monospace font and make it the LGC part of a CJK font. Iosevka could be a choice, but the problem is that it cannot be "variable-font-ified" since it changes topologically when the weight changes.
Actions we could take:

Adopt an open-source font — may need to resize the glyphs.
Design a new one — needs some extra budget 💵💴.

@bitcrazed
The font 更纱黑体 looks very well in windows console.
It include all the features you mentioned. And it also contains powerline font graphemic, so you can use it with powerline or airline directly in the WSL without any other powerline patched fonts.
It looks like this:

You can change the default font to it by yourself.

Thanks all for your comments.
We're very aware of the need to modernize & overhaul some of our fonts, especially SimSun, etc. Please bear with us while we work the process.

Started using the Terminal recently and came across this interesting discussion, just want to insert my opinions.
In terms of readability, best monospaced font (preinstalled with Windows) I've seen so far is SimSun. And Courier is  not bad.
Though, both have common issue - originated from print typefaces, thus appear too thin on screen (unless theres some tricky hinting or bitmap strokes included).
About SimSun:
It has better glyph proportions, Times-like (a bit narrowed, which is a plus) and details, but there are some glyphs not optimized for the monospace usage, e.g. glyhps "i", "l", "t" should have been morphed to cover more space, like in Courier.  And most signs are centered to caps instead of being centers to lowercase letters, which is a drawback.
About Courier:
It has slightly better glyph spacing (see "i", "l"). I feel it is initially designed for monospace usage. But regardless, glyph proportions are too wide, and the design is on the 'grotesque' side which makes it less readable than SimSun.
So if I would do the job, I'd do following:

take SimSun as a base
make it slightly bolder (doing it properly in vector actually is long and painful story)
center all signs to lowercase (><=*-{}[] etc.)
work on some letters (i, l, t), i.e. make them wider, like in Courier

Also note that inter-line spacing affects readability, it would be nice to have an option to adjust the line spacing.

Thanks for your feedback @Mikhail22 & @0xafbf
While we still have a lot of work to do, we've come a long way in the last year with the Terminal's new DirectX based text layout and rendering engine, UTF-8-aware text buffer, and other related features, including our new Cascadia Code monospace font.
We (Microsoft) also have work to do to overhaul some of our fonts, esp. for use in monospace environments in mixed Latin & non-Latin languages. Alas, font licensing, creation, hinting, etc. is a laborious, costly and complex subject area, but do know that we are working hard to figure out a decent story moving forward.
We do ask for your patience here though - this work will take some time.

Thanks for yor comments @bitcrazed  as well and good luck with the project!

Alas, font licensing, creation, hinting, etc. is a laborious, costly and complex subject area, but do know that we are working hard to figure out a decent story moving forward.

I dealt a lot with font related things, and I am curious about it.
BTW, I wonder why for this specific case (terminal) one would desire a vector font?
To my understanding, to make life easier, what one want is support for grayscale bitmap fonts aka 'graymaps'.
This would eliminate the pain of creating of fine fonts in the first place.
I would suggest to make the text renderer that can directly use bitmap font by specific sizes.
An example: to create graymaps for one size, Latin set,  and to optimize it's quality/readability may take ca. 3 weeks of one man's work.
But creating a vector font, jiggling the vector paths and hinting may take 10x more time.
Especially trying to achieve the detail level and feel of a finely crafted font, it may take forever.
After all, it's only a question of scalability. In case of bitmap approach, I'd say creating 3-4 different sizes would cover most needs for 100-200 PPI displays. And for bigger sizes the renderer could just switch to some existing vector font, as it works now.
If it would be an open source font storage format, everyone could contribute fonts and edit them.
I could contribute to this too, especially to font design and composer algos.

Trying to make a bitmap font that can scale correctly across the enormous gamut of screens and resolutions that we have to support would be "difficult" ;)
We prefer TrueType/OpenType vector fonts because they're scalable, adjustable, can be rendered by a GPU, etc.
Better still would be variable fonts defined by vectors at a few intermediate weights etc. that modern font engines can then interpolate-between to render at variable weights etc. But this requires more work (and thus cost and time) up-front.
Cascadia Code, gives you a good example of one of our most recently created, and open-source fonts, and for which we have bold goals. Eventually ;)
Now add to this the complexity of designing, creating, and defining the vector glyphs for CJK (Chinese, Japanese, and Korean) - this requires many thousands of glyphs to be defined. So many, in fact, that beyond the time & cost challenges mentioned above, physical factors including storage, memory, and runtime rendering considerations quickly come into sharp focus.
In addition, the font layout and rendering system has to be able to handle the various complexities of fitting complex glyphs into a grid - something that some letter/script forms do NOT easily support.
NOW add-in right-to-left (RTL) support too ... it all gets pretty complex pretty quickly.
So we starting by trying to get Latins to work well. Then added more support for single-cell glyphs and emoji. Next, we'll start figuring out rules and rendering techniques for some of the more complex letter forms.
Again, this will take time and we appreciate the community's help by reporting issues in this repo so that we can catalog and fix issues over time.


Limit the width of the document selectors to the width of the parent.

It's unfortunately not responsive (select2 limitation), but better than being too long.

What do you mean by "it's not responsive"? (I understand the words, but not sure what you're getting at.)
If I understand what it's doing, it should be computing the style seen by the select element and applying that to select2's magic. Does applying responsive style to the input not pass through correctly?

Interesting. I toyed with it on Firefox here and it seemed to behave reasonably when the window was narrow. If I put a %-based style on the select, that caused it to track the window width (without that, it started narrower than the window allowed).
In any case, it looks fine to me.

What I mean that it looks fine with the change, but when you then narrow or widen the window, the select doesn't grow or shrink.

I see what you mean now. Not sure why I didn't notice before - I must have mixed up what I was looking at.
If I put an explicit style="width: 100% on the field then it expands/shrinks with the width and never exceeds the page width. With that, it seems to behave the same with or without the data-width="resolve". Maybe add this to the CSS as a workaround instead or in addition to the change in this PR?

@jennifer-richards I can't style="width: 100%;" to work? It just stays too large.

Maybe I'm misunderstanding the intention and wandering into the woods. For me, the width tracks the <div class="col-sm-10">, so 100% is indeed quite wide, but not wider than the div.

This is what I see now:

With the PR, it becomes:

But when you widen the window, it stays at that width:

Ah, ok. I was looking at a different view (that template is also used on the 'History' tab). It looks to me like there are other width problems on the sidebar. Note the up-arrow button at the top in this screenshot - it's running off the viewport just like the select boxes. I think they're accurately filling a parent that's too wide. (In the screenshot, the top box has both style="width:100%;" and data-width="resolve', while the bottom has neither. They both seem to behave the same.)

Yes, the button is in the top right of the sidebar and the sidebar gets stretched too wide by the select.

That looks much better.
On a lark, I tried throwing in a window resize handler that destroys and re-initializes the select2 fields. It worked great when increasing the width of the window but still happily stretched off the viewport when decreasing it. It really doesn't want to do the right thing...


tasks.json not present in File menu

While I can easily find Workspace Settings and Keyboard Shortcuts from the File menu. I have manually open tasks.json in my .vscode directory.

F1>Configure Task
We decided to keep the File menu small.


feat(dashboard): create dashboards for Kepler on OpenShift

The PR

add kepler dashboard resource which is configmap applied to openshift-config-managed namespace
creates kepler dashboard if running against openshift
ensures namespace for creating dashboard exists in CI cluster

any tests for changes to kepler controller?

@vimalk78 , the Availability test asserts the resource is installed.

@vimalk78
please hold one ...
2023-09-21T06:55:45Z	LEVEL(-3)	continue reconciliation despite error	{"controller": "kepler", "controllerGroup": "kepler.system.sustainable.computing.io", "controllerKind": "Kepler", "Kepler": {"name":"kepler"}, "namespace": "", "name": "kepler", "reconcileID": "20c67a36-6df3-4b5b-a476-2eff2755f804", "error": "kepler-dashboard (/v1, Kind=ConfigMap): deleter: timed out waiting for deletion : timed out waiting for the condition"}

I see this! let me look further into this!

@vimalk78
please hold one ...
2023-09-21T06:55:45Z	LEVEL(-3)	continue reconciliation despite error	{"controller": "kepler", "controllerGroup": "kepler.system.sustainable.computing.io", "controllerKind": "Kepler", "Kepler": {"name":"kepler"}, "namespace": "", "name": "kepler", "reconcileID": "20c67a36-6df3-4b5b-a476-2eff2755f804", "error": "kepler-dashboard (/v1, Kind=ConfigMap): deleter: timed out waiting for deletion : timed out waiting for the condition"}

I see this! let me look further into this!


Update FreeBSD version in CI

Signed-off-by: Kevin Leimkuhler<EMAIL_ADDRESS>

This should be ok.  But there's a risk that we accidentally begin to depend on a feature from FreeBSD 12.0 or 12.1, and mio breaks on 11.3.  To guarantee backwards-compatibility, it would be better to do
  image_family: freebsd-11-3-snap

This bumps the minimum MacOS version from 10.13 to 10.14 as well so that CI starts passing again. Those images are no longer available on Azure. Similar to the FreeBSD version bump, these are minor bumps so that should be fine in order to get v0.6.x branch passing again.


I want to draw some auxiliary functions on other process windows. Can this be achieved?

All the examples I found only operate on their own window. Can't it work on other windows?

you can only do limited operations on other windows but if you look up
examples for objective c they should translate pretty well
Jeff Lindsay
https://progrium.xyz https://progrium.xyz
On Mon, Sep 9, 2024 at 9:07 PM flex @.***> wrote:

All the examples I found only operate on their own window. Can't it work
on other windows?
—
Reply to this email directly, view it on GitHub
https://github.com/progrium/darwinkit/issues/268, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAFB5WK37KO4V5E6ZIEPLZVZH5RAVCNFSM6AAAAABN5W4QQGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUYTKMRUGM4TGNQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


[backport v2.9.next1] Fix CA Bundle format

Summary
Fixes https://github.com/rancher/dashboard/issues/11532

Occurred changes and/or fixed issues

Technical notes summary

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

Checklist

[ ] The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
[ ] The PR has a Milestone
[ ] The PR template has been filled out
[ ] The PR has been self reviewed
[ ] The PR has a reviewer assigned
[ ] The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
[ ] The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

@torchiaf Can you fill in the template and checklist?


Signaling Status Not Coonected

Hi team please help me. It shows Signaling status not connected. Why this happening. I checked out the config.swift file and this is my code.
import Foundation
// Set this to the machine's address which runs the signaling server
fileprivate let defaultSignalingServerUrl = URL(string: "ws://localhost:8080")!
// We use Google's public stun servers. For production apps you should deploy your own stun/turn servers.
fileprivate let defaultIceServers = ["stun:stun.l.google.com:19302",
"stun:stun1.l.google.com:19302",
"stun:stun2.l.google.com:19302",
"stun:stun3.l.google.com:19302",
"stun:stun4.l.google.com:19302"]
struct Config {
let signalingServerUrl: URL
let webRTCIceServers: [String]
static let `default` = Config(signalingServerUrl: defaultSignalingServerUrl, webRTCIceServers: defaultIceServers)

}

Hi, Did you start the signaling server?
Also, in your config you are using localhost as the websocket server which means only simulators will be able to connect to the signaling server.

Hi, this issue has been closed due to inactivity. Please feel free to reopen it if you are still experiencing issues.

i am getting error while connecting signaling server
"Trying to reconnect to signaling server..."


Bugfix: Board is always copied when returned as an observation

Previously this was only done if the state was partially observable. Therefore the fully-observed version led to in-place modifications of the observations when the state of the environment changed (board in state and board in next_state are would be the same)

Seems reasonable. Thanks!


OS is not giving feedback about missing files

In #3668 I had the case that I could not create a ballot paper because of a missing image file. Unfortunately OS did not warn/inform me.
This is a problem because I had to create a ballot paper using Excel during the assembly. This was lot of stress and I got negative feedback and critical people found them self confirmed that software like OS is not yet usable. (And there are always critical people, sic!)
Therefore OS should inform admins what the problem is:

is a file is missing
if an uncodable character in e.g. a motion text is used preventing the display or creation of a PDF/DOCX
maybe there are other cases where OS could warn the admins

@FinnStutzenstein Please add a nice error message if pdf generation failes caused by missing mediafile.


@JuliaRegistrator register()

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/86305
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.2 -m "<description of version>" a7e87012180a8a20c6fe94a9d95712710280c56c
git push origin v0.3.2


Question: can I load and use trained tfdf model in Golang?

is there a way I can do model inference with golang?
what are the current options?
TF C API seems to miss a few inference ops. there is https://github.com/google/yggdrasil-decision-forests but might be hard to use it with golang?

Hi,
unfortunately,  TF-DF has no support for Golang at this time. We are considering it for future releases if there is sufficient interest (no timeline though)

@rstz how much would it to call c++ Yggdrasil-decision-forest code from golang?

hi @Arnold1 , it should work with cgo, but likely you will want to write some wrappers around the C++ libraries that you want to use. Mind the usual "cgo is not go" concerns -- it looks dire, but in some cases the "cons" are ok.
I personally considered doing it on the side more than once, but then I gave up because of the complicated packaging of the mixed go/C++ libraries (I've never done it ...). But it would be awesome if someone would write a binding to TF-DF (Yggdrasil actually) to Go ;) ;)
From our side we have a draft inference only library written purely in Go -- it's not the most optimized version of the library, but in the majority of the cases DF are so fast that it doesn't matter (it's our internal use case here).
We can't give an ETA, but I'll mark the issue as "enhancement" and leave this opened, so we can post an update when we have one.

@janpfeifer library purely in Go seems amazing - any plans for releasing over the summer? that would be amazing - I would have use case to use it in prod.

hi @Arnold1 , we just released a TF-DF (and YDF) inference API in Go.
It's fresh from the oven, so we consider it beta. But internally it has already been used successfully.
Also it doesn't support all types of models yet, but should be easier now to add any model type. If you see the need just ping us.


libxklavier: 5.3 -> 5.4

Motivation for this change
xfce 4.13 needs it
unfortunately, upstream has no source tarball, only git
Things done

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

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

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

@GrahamcOfBorg build libxklavier

Success on x86_64-linux (full log)
Attempted: libxklavier
Partial log (click to expand)
checking for references to /build in /nix/store/24kyfk18kpzpavi22n1m1x2a6k5yd34n-libxklavier-5.4...
shrinking RPATHs of ELF executables and libraries in /nix/store/nwjjgwzpm3vzkvilwfyaqn2iikvvh6hv-libxklavier-5.4-dev
strip is /nix/store/4qvrxzxa535y8304mk195x50b6p9607d-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/nwjjgwzpm3vzkvilwfyaqn2iikvvh6hv-libxklavier-5.4-dev/lib
patching script interpreter paths in /nix/store/nwjjgwzpm3vzkvilwfyaqn2iikvvh6hv-libxklavier-5.4-dev
checking for references to /build in /nix/store/nwjjgwzpm3vzkvilwfyaqn2iikvvh6hv-libxklavier-5.4-dev...
shrinking RPATHs of ELF executables and libraries in /nix/store/a4bgz72bl6wx7g5zlj8g5d7b83f8zl5v-libxklavier-5.4-devdoc
strip is /nix/store/4qvrxzxa535y8304mk195x50b6p9607d-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/a4bgz72bl6wx7g5zlj8g5d7b83f8zl5v-libxklavier-5.4-devdoc
checking for references to /build in /nix/store/a4bgz72bl6wx7g5zlj8g5d7b83f8zl5v-libxklavier-5.4-devdoc...

Success on aarch64-linux (full log)
Attempted: libxklavier
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/k3id4scwwbpv5pn6lcca1fqk135168ck-libxklavier-5.4-dev
strip is /nix/store/0pjsgkxz0rp5baycq5sp2s72lrr5q9sg-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/k3id4scwwbpv5pn6lcca1fqk135168ck-libxklavier-5.4-dev/lib
patching script interpreter paths in /nix/store/k3id4scwwbpv5pn6lcca1fqk135168ck-libxklavier-5.4-dev
checking for references to /build in /nix/store/k3id4scwwbpv5pn6lcca1fqk135168ck-libxklavier-5.4-dev...
shrinking RPATHs of ELF executables and libraries in /nix/store/zx5jmzfkxkj3dp8a195mbczwc4lrxchn-libxklavier-5.4-devdoc
strip is /nix/store/0pjsgkxz0rp5baycq5sp2s72lrr5q9sg-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/zx5jmzfkxkj3dp8a195mbczwc4lrxchn-libxklavier-5.4-devdoc
checking for references to /build in /nix/store/zx5jmzfkxkj3dp8a195mbczwc4lrxchn-libxklavier-5.4-devdoc...
/nix/store/z9hvplk3292w3zscr27ghkrr1f89z7nz-libxklavier-5.4

@GrahamcOfBorg eval

@GrahamcOfBorg eval

Success on x86_64-linux (full log)
Attempted: libxklavier
Partial log (click to expand)
checking for references to /build in /nix/store/vp8la29wjldfacdllvn15s1rz1lf8msx-libxklavier-5.4...
shrinking RPATHs of ELF executables and libraries in /nix/store/n57gc8pw1l1lvmwa3qvmac81plg0iw6h-libxklavier-5.4-dev
strip is /nix/store/90vmpr41dzsx350k5argycaf693hnl1l-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/n57gc8pw1l1lvmwa3qvmac81plg0iw6h-libxklavier-5.4-dev/lib
patching script interpreter paths in /nix/store/n57gc8pw1l1lvmwa3qvmac81plg0iw6h-libxklavier-5.4-dev
checking for references to /build in /nix/store/n57gc8pw1l1lvmwa3qvmac81plg0iw6h-libxklavier-5.4-dev...
shrinking RPATHs of ELF executables and libraries in /nix/store/b355f5wyf1k5xg223xjs0qgldqam4m0d-libxklavier-5.4-devdoc
strip is /nix/store/90vmpr41dzsx350k5argycaf693hnl1l-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/b355f5wyf1k5xg223xjs0qgldqam4m0d-libxklavier-5.4-devdoc
checking for references to /build in /nix/store/b355f5wyf1k5xg223xjs0qgldqam4m0d-libxklavier-5.4-devdoc...

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


Support duplicating and reopening issues

Right now there's support for reopening merge requests, but not issues.
Plus when closing an issue, it can be useful to mark it as a duplicate of another issue.

By the way, is there some trick for fixing the coverage test? If I read https://codecov.io/gh/zaquestion/lab/pull/533/diff correctly, the code that calls IssueDuplicate/IssueReopen is called, but not a single line in those functions is covered ... which is rather baffling?!

TBH, that's a good question. I've faced the same issue other times, but never really looked into for details.
@zaquestion had plans to rework the coverity IIRC, but I don't think we have a workaround for it right now.
So I think it's fine just ignoring, for now.

By the way, is there some trick for fixing the coverage test? If I read https://codecov.io/gh/zaquestion/lab/pull/533/diff correctly, the code that calls IssueDuplicate/IssueReopen is called, but not a single line in those functions is covered ... which is rather baffling?!

I've noticed that before and @zaquestion has too.  It's annoying and I haven't figured out a reason why codecov makes this error on occasion.  In any case, you've added a test and that's really what is important :)


ffmpeg vp8/vc1 decoding failure due to MFX_FRAMETYPE is uninitialized

Reproduce:
Using the latest ffmpeg( commit_id: deb9a04d54045c8021816cfe019bf2bba0e9595d)
./ffmpeg -hwaccel qsv -init_hw_device qsv -c:v vp8_qsv -i /root/lizhong/Videos/fate-suite/vp8-test-vectors-r1/vp80-00-comprehensiv
e-001.ivf -vf "hwdownload,format=nv12" -pix_fmt yuv420p -f md5 -
ffmpeg version N-91336-gdeb9a04 Copyright (c) 2000-2018 the FFmpeg developers
built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.9) 20160609
configuration: --enable-libmfx --enable-libx264 --enable-gpl --disable-optimizations --enable-debug=3
libavutil      56. 18.102 / 56. 18.102
libavcodec     58. 20.103 / 58. 20.103
libavformat    58. 17.101 / 58. 17.101
libavdevice    58.  4.101 / 58.  4.101
libavfilter     7. 25.100 /  7. 25.100
libswscale      5.  2.100 /  5.  2.100
libswresample   3.  2.100 /  3.  2.100
libpostproc    55.  2.100 / 55.  2.100
Input #0, ivf, from '/root/lizhong/Videos/fate-suite/vp8-test-vectors-r1/vp80-00-comprehensive-001.ivf':
Duration: 00:00:00.97, start: 0.000000, bitrate: 131 kb/s
Stream #0:0: Video: vp8 (VP80 / 0x30385056), yuv420p(progressive), 176x144, 30 tbr, 30 tbn, 30 tbc
Stream mapping:
Stream #0:0 -> #0:0 (vp8 (vp8_qsv) -> rawvideo (native))
Press [q] to stop, [?] for help
Assertion 0 failed at libavcodec/qsv.c:219
Aborted (core dumped)
It is failed in ff_qsv_map_pictype() checking frame_type and found it is uninitialized(return a value of MFX_FRAMETYPE_UNKNOWN).  Other codes (h264/vc1/hevc) looks good except vp8.

vp80-00-comprehensive-001.zip

Any comment? All vp8 decoding cases failed in ffmpeg right now.

@lizhong1008 : do you need the same feature supported for Jpeg decoder?

@dvrogozh , yes, it is needed. Basically speaking,  we should keep internal implementation compatibility with same API. If not, then we should expose such limitation with query interface.
As tested with my mjpeg decoding enabling patch (though it is not merged now), JPEG frame_type is also FRAMETYPE_UNKNOWN reported from MSDK.

@akokoshn : we need the same patch for jpeg decoder... and please, check vp9 as well.

@dvrogozh , confirmed with vp9 decoder,  it is FRAMETYPE_UNKNOWN too.

hi @lizhong1008, as far I know for JPEG not actual frame types I/P/B (in my understanding all frames may be named as I), so could you please explain why need ask MSDK about JPEG frame type?
We can report all frames as I, but I'm not sure it's make sense or not.

@akokoshn , good question.  It is similar issue for ffmpeg software jpeg/mjpeg decoding/encoding.  Currently software is taken is as Keyframe (I frame).  See: https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/mjpegdec.c#L708.
I believe MSDK can follow this too, set all frame as I frame.
FRAMETYPE_UNKNOWN as my understanding it means something is broken.

Give a quick testing, I haven't found anything wrong for MJPEG/VP8/VP9, except VC1.
Applied a patch as
diff --git a/libavcodec/qsv.c b/libavcodec/qsv.c
index 7dcfb04316..e7683ffd27 100644
--- a/libavcodec/qsv.c
+++ b/libavcodec/qsv.c
@@ -245,6 +245,8 @@ enum AVPictureType ff_qsv_map_pictype(int mfx_pic_type)
         av_assert0(0);
     }

+    printf("mfx decoding type is %d\n", mfx_pic_type);
+    printf("qsv decoding type is %d\n", type);
     return type;
 }

diff --git a/libavcodec/vc1_parser.c b/libavcodec/vc1_parser.c
index 493ffde611..3f49657da8 100644
--- a/libavcodec/vc1_parser.c
+++ b/libavcodec/vc1_parser.c
@@ -90,6 +90,7 @@ static void vc1_extract_header(AVCodecParserContext *s, AVCodecContext *avctx,
         else
             s->pict_type = vpc->v.s.pict_type;

+        printf("picture type is %d\n",vpc->v.s.pict_type);
         if (avctx->ticks_per_frame > 1){
             // process pulldown flags
             s->repeat_pict = 1;

./ffmpeg -hwaccel qsv -c:v vc1_qsv -i /root/Videos/fate-suite/vc1/SA00040.vc1 -vf 'scale_qsv=format=rgb32, hwdownload,format=rgb32' -f sdl -
All of frames which are not I frames are reported as B frame by ffmpeg software parser, but MSDK return a picture_type unknown.
Then I checked the code: https://github.com/Intel-Media-SDK/MediaSDK/blob/af248638256501f4edad3abc097909a4c2fffdd5/_studio/mfx_lib/decode/vc1/src/mfx_vc1_decode.cpp#L50
Only I frame is handled here.
AFAIK, VC1 picture type are I-picture, P-picture, skipped picture, B/BI-picture. Why only I frames are handled here?

@akokoshn : please, comment.

Hi @lizhong1008 , sorry for delay response.
Current implementation of MSDK VC1d ignore P/B types: frame defines as skip or I-Frame: https://github.com/Intel-Media-SDK/MediaSDK/blob/a14166bd60890c89b174686d68238f6972898b47/_studio/shared/umc/codec/vc1_dec/include/umc_vc1_video_decoder_hw.h#L160
PR: https://github.com/Intel-Media-SDK/MediaSDK/pull/1229 should fix it, but still see reported frame type unknown on test with ffmpeg  (stream
SA00040.vc1)

Hi @lizhong1008 , I have found root cause issue - MSDK specific handling skipped frames leads rewrite real frame type by VC1_SKIPPED_FRAME.
https://github.com/Intel-Media-SDK/MediaSDK/pull/1229 was updated

@akokoshn Patch LGTM and will give an updated testing.

Tested SA00040.vc1 and  SA10091.vc1 (you can get all of them from ffmpeg suite: http://ffmpeg.org/fate.html).  Two issue found:

No I frame exposed for SA00040.vc1.  All frames B frames.
some last frames of SA10091.vc1 are still reported as Unknown.

@lizhong1008, @akokoshn : Let's continue VC1 debug in issue #1239. This issue was about mediasdk decoders not reporting frame types at all - it was fixed. Now, we observe that some decoders don't properly recognize stream and, hence, don't report frame type correctly. Let's deal with these kind of issues separately.


Fix occurrences of timeout

[x] howto/mro.rst:13: [timeout] https://www.phyast.pitt.edu/~micheles/: HTTPSConnectionPool(host='www.phyast.pitt.edu', port=443): Max retries exceeded with url: /~micheles/ (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f744affa4e0>, 'Connection to www.phyast.pitt.edu timed out. (connect timeout=30)'))
[x] library/unittest.rst:67: [timeout] http://lists.idyll.org/listinfo/testing-in-python: HTTPConnectionPool(host='lists.idyll.org', port=80): Max retries exceeded with url: /listinfo/testing-in-python (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f744a44aae0>, 'Connection to lists.idyll.org timed out. (connect timeout=30)'))
[x] whatsnew/3.2.rst:978: [timeout] https://osl.cs.illinois.edu/media/papers/karmani-2009-barrier_synchronization_pattern.pdf: HTTPSConnectionPool(host='osl.cs.illinois.edu', port=443): Max retries exceeded with url: /media/papers/karmani-2009-barrier_synchronization_pattern.pdf (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f744ac17d10>, 'Connection to osl.cs.illinois.edu timed out. (connect timeout=30)'))

Not a recurring issue, nothing to do


pull request for e2e test at 12/09/2016 02:15:02

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

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


Extend and clarify pack name conventions examples

As per title, the aim is to improve the documentation of pack: entries.

LGTM


Qrcode problem

If you do not log in for a long time, this qrcode will not be modified.  will not be able to log in after scanning

You should run your app again. it create a new qr

If you do not log in for a long time, this qrcode will not be modified. will not be able to log in after scanning

If your credentials become invalid, you need to clear them and restart the application so a new qr code can be generated

Oh, I see