Uniques: Allowing multiple approvals

Solves the new approvals structure task from #11783
In short, this PR allows the item owner to make approvals to multiple accounts.
Note: I took a bit of a different approach than proposed in #11791. I believe that this is a bit simpler than storing a BoundedBTreeMap for approvals.

Hi @Szegoo , thanks for your contribution!
I'm thinking it's better to keep the existing Uniques pallet as feature-complete and start pushing all the new changes into V2.
I've created a new branch for this js/uniques-v2-main-branch, this is a new pallet for all V2 works.
It would be good if you could apply your changes on top of that pallet and point your PR to my branch.

The reason I wanted to use BoundedBTreeMap is because of the new structure of approvals I'm proposing: I think each approval should have an optional deadline (the block number) set.
Pls check my prev implementation for reference:
https://github.com/paritytech/substrate/commit/707d69bca379b53ee560a803e00ce181acc0de55
https://github.com/paritytech/substrate/commit/a705c225223ccf3d3d1715ecaf21b054c33a6a10

@jsidorenko What would be the benefit of creating a BoundedBTreeMap, cause we could also probably add deadline like this:
/// The approved transferrer of this item, if one is set.
pub(super) approved:
	BoundedVec<(AccountId, Option<<T as frame_system::Config>::BlockNumber>), ApprovalsLimit>,

I am going to use BoundedBTreeMap if you still think we should use that, I am just interested if there is a reason behind this decision.

BoundedBTreeMap simplifies the management of approvals:

when you need to find an approval, you will simply call item.approvals.get(&sender) instead of item.approvals.get_key_value(&sender)
once you insert, you don't need to check if approval for the same account exists
when you remove, you will simply call item.approvals.remove(&delegate) instead of if let Some(pos) = item.approvals.iter().position(|ap| delegate == ap.who) { item.approvals.remove(pos); }

@jsidorenko I opened a new PR with these changes to the js/uniques-v2-main-branch, Should I close this?


Pretrained model

Hi Chris, wonderful work!
I wonder when will the pretrained model be released so we can test out the model. Thanks!

Hi Chris, wonderful work! I wonder when will the pretrained model be released so we can test out the model. Thanks!

Hi, very sorry for the late upload about our pretrained models. Since I am too busy in the past few months. Then today I have uoloaded the pretrain models to Google Drive, you could find it here:https://drive.google.com/drive/folders/17_4Ux74sdYEsHB1Zy9f1iTgJWyPW5Fyz?usp=drive_link


update Devices and Sensors WG for joint publication

DAS now has a spec jointly published with WebApps, this PR is to include joint publication text into boilerplate.
Required for https://github.com/w3c/contact-picker/pull/53
/cc @tabatkins , please merge when you've noticed with this PR.

thank you!


Consider adjusting terms for spell preparation modes in Modern rules

The 2024 PHB has abolished "known" vs. "prepared", which makes the current delineation of Prepared/Always Prepared vs. Pact Magic inaccurate.
I think this can be tied to the modern vs legacy setting, although this may make guides slightly more difficult due to needing to use two different terms for similar system results.

Related to this, the Pact spells are odd to grant and it complicates tracking the correct # of spells "prepared"

Wizard still uses 'know' to describe the spells stored in their spellbook and uses 'prepared' to refer to spells that can be cast on any given day. Warlock however does only use 'prepared'.
So I wouldn't say 'known' is abolished.

This may be more of a core system issue and is certainly related to this.

Another issue is that an 'always prepared' spell on a warlock no longer shows up in the 'pact magic' section on the spell and then modules like 'token action hud 5e' don't pick up on them

Since wizards still prepare spells, what if the system simply change the default mode for created spells to "always prepared" if the modern rules are selected?


[SPFarmPropertyBag] Resource is only able to configure string values

Problem description
The schema of the SPFarmPropertyBag resource currently allows the configuration of a string value. However it is unable to configure any other type of value like a boolean:
[Key, Description("The key of the SPFarm property bag")] string Key;
[Write, Description("Value of the SPfarm property bag")] String Value;
[Write, Description("Set to present to ensure the SPfarm property exists, or absent to ensure it is removed"), ValueMap{"Present","Absent"}, Values{"Present","Absent"}] string Ensure;

Verbose logs
When the value is configured manually as a boolean, the Test always returns false:

Current Values: Ensure=Present; Key=disableIntranetCalls; Value=False
Target Values: Ensure=Present; Key=disableIntranetCalls; Value=False; Verbose=True
Test-TargetResource returned False

This is because the types of the current values (boolean) and the desired value (string) are not the same.

DSC configuration
SPFarmPropertyBas DisableIntranetCalls
{
    Key = 'disableIntranetCalls'
    Value = 'False'
    Ensure = 'Present'
}

Suggested solution
Add the possibility to specify other types
SharePoint version and build
All

Operating system the target node is running
All

PowerShell version and build the target node is running
v5.1

SharePointDsc version
Dev

Fix is implemented and will be merged in my next Bugfix PR

With this fix you will be able to specify the type of the data in the Value parameter:

SPFarmPropertyBag 'DisableIntranetCalls'
{
    Key                  = 'disableIntranetCalls'
    Value                = 'False'
    ParameterType        = 'Boolean'
    Ensure               = 'Present'
    PsDscRunAsCredential = $SPSetupAccount
}


Support for Async

First off thank you for this project! It has been very useful to us.
I want to share that I'm a bit confused about the async_mode, I use openai and so I thought it was support for acreate completion method. I did some time benchmark between the two async modes and the performance difference is stark.
Here's the benchmark.
RAW openai:
@timer_func
async def run_openai():
    tasks = [openai.ChatCompletion.acreate(model="gpt-3.5-turbo", temperature=0, messages=[{"role": "user", "content": "The best thing about the oce
    an is"}]) for i in range(10)]
    chat_completion = await asyncio.gather(*tasks)
    return [chat.choices[0].message.content for chat in chat_completion]

Results:
run_openai took 15.321205854415894 seconds to complete its execution.
Guidance:
@timer_func
 async def run_program():
     tasks = [program() for i in range(10)]
     res = await asyncio.gather(*tasks)
     return [r['results'] for r in res]

Results:
run_program took<PHONE_NUMBER>802765 seconds to complete its execution.
Performance is on the same for single request.
A few questions:

What is async_modes use case
Is there a possibility to disable "display" functions, I see we call "update_display" each time during async mode. Maybe I'm confused

Thanks! I'll look into it when I get a chance, we have not performance optimized yet too much. It might be that you are running in parallel vs sequential and that might be because we should be using acreate in the OpenAI LLM object.
If you or others get a chance to dig into this and learn more post here (or just post a PR :) ).

Do you have any update on this? Has it been resolved?
These are the only calls to openai that the openai guidance module makes:
        if self.chat_mode:
            kwargs['messages'] = prompt_to_messages(kwargs['prompt'])
            del kwargs['prompt']
            del kwargs['echo']
            del kwargs['logprobs']
            # print(kwargs)
            out = await openai.ChatCompletion.acreate(**kwargs)
            out = add_text_to_chat_mode(out)
        else:
            out = await openai.Completion.acreate(**kwargs)

So I am assuming contrary to the original post, this has been implemented now and is working?

Thanks! I'll look into it when I get a chance, we have not performance optimized yet too much. It might be that you are running in parallel vs sequential and that might be because we should be using acreate in the OpenAI LLM object.
If you or others get a chance to dig into this and learn more post here (or just post a PR :) ).

I just became interested in this project and async is a must. This issue should be relatively easy to trace, right? acreate should be used for every call, unless I'm missing something there. Will try for myself.
I find it hard to believe that something called update_display is blocking the event loop. Let's take a look.

Any news on this?

Does async work on the current version?

guys, I want to tell you something.
asyncio + LLM libraries is the devil. Should it be? of course not. We all want fast event loops but how many repos have you had to fork to fix the asyncio? I've lost count. This is especially present in an emerging 'field' where there are no solid libraries for anything.
I don't see anything about async in the docs for the new version. Personally, I'm just going to take it as a W and pass it to run_in_executor

Or you know we could contribute a fix. Just need the developers to confirm/deny its current implementation and approve a work plan.


branch feature/best_matching: incorrect matching

On branch "feature/best_matching" matching with market_type "fair" partly does not work correctly with actor strategy 1 and linear pricing. Even though residentials could be matched with each other they are sometimes matched with the MarketMaker instead. The same behaviour can be observed with actor strategy 2 and linear pricing.
Examples:

3 actors on 2 clusters, all with load, PV and battery
actor strategy: 1
pricing strategy: linear
weight_factor: 0.003
default_grid_fee = 0.01

Example 1:
Orders:

Matches:

Example 2:
Orders:

Matches:

Note: MarketMaker prices are 0.045, not 45

resolved see test_update_clearing_cluster_issue220 and test_update_clearing_cluster_issue220_b in  tests/test_market_fair.py


Close and restore button colors differ

Button colors differs for window buttons. I suggest to use white colors for theme.

Fixed. Will be a part of the next release

@goldim they should be the same in v1.1.0 release


Ceph is attempting to use the wrong version of Lua

Steps To Reproduce
I'm in the process of trying to build a local version of ceph to try getting around the modprobe issue from #147801 but I was unable to copy a local version for my overlay.

Copy https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/filesystems/ceph/default.nix locally without any changes
Create an overlay to use the file
Build the package that uses ceph

Build log
The relevant sections:
-- Performing Test HAS_VTA
-- Performing Test HAS_VTA - Success
Cmake Error at /nix/store/rxb9zl1mdx9f2n3z0nyv9zhngj3f2pw0-cmake-3.24.3/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:23    0 (message):
  Could NOT find Lua (missing: LUA_INCLUDE_DIR) (Required is at least version
  "5.3")
Call Stack (most recent call first):
  /nix/store/rxb9zl1mdx9f2n3z0nyv9zhngj3f2pw0-cmake-3.24.3/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAI    LURE_MESSAGE)
  /nix/store/rxb9zl1mdx9f2n3z0nyv9zhngj3f2pw0-cmake-3.24.3/share/cmake-3.24/Modules/FindLua.cmake:236 (FIND_PACKAGE_HANDLE_STANDARD_ARG    S)
  src/CMakeLists.txt:580 (find_package)

Additional context
While looking at the problem, I noticed on lines 18 and 171, the packages are referencing lua but according to search.nixos.org, lua is version 5.2.4. Switching this to lua5_3_compat had the minimum version required and let me get past that build step.
Add any other context about the problem here.
Notify maintainers
@adev @ak @johanot @krav
Metadata

system: "x86_64-linux"
host os: Linux 5.15.79, NixOS, 22.11 (Raccoon)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.11.0
channels(root): "nixos-22.05pre358459.3e072546ea9"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

This is for a flake-based system against the latest unstable.
Thank you.

diagnostic looks ok, PR welcome ? (I've got no involvment with ceph)

Closed as this has been solved with a top-level alias.


Split the groups var to group and groups

The user groups can now be set with the group and groups variables.
The group var sets the user's primary (initial) group and with the
groups var the additional groups can be specified (comma separated).
The old behaviour was that the groups vas was was set to the ansible
user module's group var preventing multiple groups to be specified.

Thanks! Looks good to me. I pushed a few changes to the branch in your fork you based the PR on to do some more testing and improve the documentation.

Nice!


default: unable to get latest version number, define a version manually with the --version flag

Platform: Windows 11, AMD64
Git Bash CLI
I pulled this latest repo as of today...
Thomas@Sammy MINGW64 ~/development/rpi-cloud-init (main)
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/focal64' version '20230215.0.0' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: <IP_ADDRESS>:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection reset. Retrying...
default: Warning: Connection aborted. Retrying...
default: Warning: Connection aborted. Retrying...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
default: The guest additions on this VM do not match the installed version of
default: VirtualBox! In most cases this is fine, but in rare cases it can
default: prevent things such as shared folders from working properly. If you see
default: shared folder errors, please make sure the guest additions within the
default: virtual machine match the version of VirtualBox you have installed on
default: your host and reload your VM.
default:
default: Guest Additions Version: 6.1.38
default: VirtualBox Version: 7.0
==> default: Mounting shared folders...
default: /vagrant => C:/Users/Thomas/Development/rpi-cloud-init
==> default: Running provisioner: shell...
default: Running: inline script
default: Downloading package https://github.com/jsiebens/hashi-up/releases/download/v0.16.0/hashi-up as /tmp/hashi-up
default: Download complete.
default:
default: Running with sufficient permissions to attempt to move hashi-up to /usr/local/bin
default: New version of hashi-up installed to /usr/local/bin
default: Version: 0.16.0
default: Git Commit: b062f5d
default: unable to get latest version number, define a version manually with the --version flag: Get "https://api.releases.hashicorp.com/v1/releases/packer?license_class=oss": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Adding the latest release version parameter number, i.e. --version 1.9.4 for packer to Vagrantfile helped get rid of that error.
$script = <<-SCRIPT
curl -sL get.hashi-up.dev | sudo sh
sudo hashi-up packer get --version 1.9.4 -d /usr/local/bin
SCRIPT

Vagrant.configure("2") do |config|

    config.vm.box = "ubuntu/focal64"

    config.vm.boot_timeout = 600

    config.vm.provider "virtualbox" do |vb|
      vb.customize [ "modifyvm", :id, "--uartmode1", "disconnected" ]
    end

    config.vm.provision "shell", inline: $script

  end


[nodejs] Enable Test_Blocking_request_body_multipart

Motivation
With the multer instrumentation we can enable this test
Changes
Implement the multipart handler endpoint based on multer and enable Test_Blocking_request_body_multipart in manifest
Workflow

⚠ Create your PR as draft ⚠
Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
Mark it as ready for review

Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
Framework is modified, or non obvious usage of it -> get a review from R&P team

:rocket: Once your PR is reviewed, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist

[ ] If PR title starts with [<language>], double-check that only <language> is impacted by the change
[ ] No system-tests internal is modified. Otherwise, I have the approval from R&P team
[ ] CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
[ ] A docker base image is modified?

[ ] the relevant build-XXX-image label is present

[ ] A scenario is added (or removed)?

[ ] Get a review from R&P team

A test from DEBUGGER_LINE_PROBES_SNAPSHOT was failing.
But it's unrelated with this PR changes (i guess :smiley:)
That's why I merged main branch again...


Incorrect comments generation for variables and method calls

Hello! It's can be fixed?

For this case must be
using System;

namespace EleWise.ELMA.Core.Model
{
    public class TestClass
    {
        public void Main()
        {
            ///
            var prop = "";
            ///
            Console.WriteLine(prop);
        }
    }
}

I know how to fix second case (Console.WriteLine). Just delete this line of code

Thanks @SteamUpdate ,
This is a deep problem, I can not fix it with the current architecture. We need to add AST, which makes the extension very heavy. This is an important issue, please do not close it. 🙇♂

I might not be up to date with a certain feature here, but does C# even care about documentation comments within a method body? I don't think these will get picked up anywhere to begin with. Still an annoying issue, but IMHO not vital.


Allow a node edit dialog to trigger revalidation

If there are co-dependencies between fields in a node's edit dialog, it ought to be possible for the node to trigger a dialog-wide revalidation so if the change causes another field to become invalid, it will get highlighted as such.

Done in 0.14.0 branch via 088e3e537422d5097c6475f6ae772cf30b640165


token retrieval after keychain fetch on start up does not work

it returns success with token no message returned in the frontend. The backend says: <IP_ADDRESS> - - [26/Apr/2015:09:41:22 +0000] "POST /api/v1/users/553cade9de73770f161f752a/authenticate HTTP/1.1" 401 - "-" "idrop.link/de.andinfinity.idrop-link (1; OS Version 10.10.3 (Build 14D136))"

Note: directly after sign up it works:
success with token eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJlbWFpbCI6InBpc2RoZ24ifQ.iEMkhNZ_B10Sl4-kS1qx9Q9m-gxzV43mkm2_5t5I1R4

with curl it works:
curl -i -X POST -H "Content-Type: application/json" -d '{"email":"foo", "password": "bar"}' http://localhost:7667/api/v1/users/553de8c9330d5ebf2568ad4d/authenticate
HTTP/1.1 200 OK
X-Powered-By: Express
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
Content-Type: application/json; charset=utf-8
Content-Length: 113
ETag: W/"71-5bcd97f8"
Date: Mon, 27 Apr 2015 07:53:12 GMT
Connection: keep-alive

{"token":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJlbWFpbCI6ImZvbyJ9.R8yXEp8NHQIDvM1ayoBIuc88go0mQx2UmGkJB7fEcYg"}~

Well, right now it works:
success with token eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJlbWFpbCI6ImJsYSJ9.kmSgrr9BFzPJEklQDb9IgrQLRbvw3P0vQrq4iIq_xbk

we should validate this.


Security

How secure is Paper and how can it be secured to prevent external manipulation

Paper doesn't provide extra security level. All paper db files saved in the app's files directory available only to that app.


ADDED SPACE SHIP GAME

Description
Spaceship-Game
Game is fully playable! Enemies and teammates will spawn randomly on the map. The current aim is to survive for as long as you can but I will add score and win conditions later. Ships will drop resources when killed. Shooting and using abilities will now consume resources. Shield is the blue bar at the top and health is the grey bar below the shield bar.
press 'start' to start the game.
W to accelerate
S to decelerate
A and D to rotate
Q to switch aiming mode
turrets follow mouse pointer
Left click to shoot turrets
E to shoot main cannon
F to fire railgun
hold down R to boost
X to repair (regenerate hp)
R to boost
U to open/close upgrades menu (and pause)
Save by clicking the save button in the upgrades menu
Zoom out to see more of the map at once
For the experimental version of the game which may or may not work:
Fixes:  #2250

Type of change

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

Checklist:

[x] I have made this from my own
[x] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@Sulagna-Dutta-Roy

@Sulagna-Dutta-Roy manifest file is already there Space "Ship Game/manifest.json" no it's not entry-level give level 2.

It's an entry level project I checked. And labels are defined already previously. Not every project is Intermediate.
Contributors can say this but as an admin. Labels are predefined and dependent on many factors.
Your other PRs are level 2.


Adding configuration for APT unattended upgrades

Closes-Bug: #802
(cherry picked from commit 0d5dc4a4332fe221ebd2cf774ca2e59b62c0e900)

:+1:

:+1:


fix(NodesTable): add consistency to link

I started to build a new component in the UI Kit called Link to wrap the Link component from React Router but because it's out of scope I returned to the original fix.

Fix link in NodesTable to add consistency
across tables.
Closes DCOS-39959
Testing

npm start
Go to Nodes page and note the fix in the name column

After

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Retriggered build, it crashed on docker build

:tada: This PR is included in version 2.4.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Cluster File not being parsed correctly?

I am having an issue with i2cssh interpretting the cluster file (.i2csshrc).  Here is my .i2csshrc file:
---
clusters:
  servers-a:
	- server01
	- server02
  servers-b:
	- server03
	- server04

Here's the error I get:
/usr/local/Cellar/ruby/1.9.2-p290/lib/ruby/1.9.1/syck.rb:135:in `load': syntax error on line 3, col 3: `	- server01' (ArgumentError)
	from /usr/local/Cellar/ruby/1.9.2-p290/lib/ruby/1.9.1/syck.rb:135:in `load'
	from /usr/local/Cellar/ruby/1.9.2-p290/lib/ruby/gems/1.9.1/gems/i2cssh-1.2.3/bin/i2cssh:49:in `block (2 levels) in <top (required)>'
	from /usr/local/Cellar/ruby/1.9.2-p290/lib/ruby/1.9.1/optparse.rb:1308:in `call'
	from /usr/local/Cellar/ruby/1.9.2-p290/lib/ruby/1.9.1/optparse.rb:1308:in `block in parse_in_order'
	from /usr/local/Cellar/ruby/1.9.2-p290/lib/ruby/1.9.1/optparse.rb:1264:in `catch'
	from /usr/local/Cellar/ruby/1.9.2-p290/lib/ruby/1.9.1/optparse.rb:1264:in `parse_in_order'
	from /usr/local/Cellar/ruby/1.9.2-p290/lib/ruby/1.9.1/optparse.rb:1258:in `order!'
	from /usr/local/Cellar/ruby/1.9.2-p290/lib/ruby/1.9.1/optparse.rb:1349:in `permute!'
	from /usr/local/Cellar/ruby/1.9.2-p290/lib/ruby/1.9.1/optparse.rb:1370:in `parse!'
	from /usr/local/Cellar/ruby/1.9.2-p290/lib/ruby/gems/1.9.1/gems/i2cssh-1.2.3/bin/i2cssh:64:in `<top (required)>'
	from /usr/local/Cellar/ruby/1.9.2-p290/bin/i2cssh:19:in `load'
	from /usr/local/Cellar/ruby/1.9.2-p290/bin/i2cssh:19:in `<main>'

Was wondering if there is a fix, or if I'm just got the syntax wrong for the cluster file.

i2cssh doesn't behave well in ruby 1.9. Can you try 1.8?

I could probably test in 1.8, I'll post back results.

Still receiving an error:
$ /Library/Ruby/Gems/1.8/gems/i2cssh-1.2.3/bin/i2cssh -l ddecker -F -c servers-a
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/yaml.rb:133:in `load': syntax error on line 3, col 3: `	- server01' (ArgumentError)
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/yaml.rb:133:in `load'
	from /Library/Ruby/Gems/1.8/gems/i2cssh-1.2.3/bin/i2cssh:49
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1298:in `call'
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1298:in `parse_in_order'
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1254:in `catch'
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1254:in `parse_in_order'
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1248:in `order!'
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1339:in `permute!'
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1360:in `parse!'
	from /Library/Ruby/Gems/1.8/gems/i2cssh-1.2.3/bin/i2cssh:64

Try to use spaces instead of tabs. That should work.

Ok, so uses spaces worked and is the ultimate fix.  In your readme, make sure you tell people to not use tabs at all, as it breaks the parsing of .i2csshrc.
I even reverted back to Ruby 1.9 and was able to get this to work after removing the tabs and just using spaces.

The thing is that the config file should be in YAML, which isn't valid with tabs, but requires spaces. I'll add it to the README though :)


[TextField] Leading zero not going away in TextField when type set to number

When the type of TextField is set to number and give it a initial value, once the entered number is deleted, the displayed value becomes 0. If you then enter another number, the zero will stay unless the page is refreshed.
I've checked the value received in the onChange function, which doesn't come with the leading zero.
If the 'value' attribute is not set, this issue won't occur.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

If the entered number is deleted, it'd be better to not show the default 0 (as seen in Component Demos).
OR
Show the default 0, but remove it if the first digit entered is not 0.
Current Behavior

The leading zero won't go away.
Steps to Reproduce (for bugs)

Use a TextField and set type to number. Apply an onChange function.
In the browser, enter a number in the field, and remove it. You should see a zero now.
Enter another number. You shoud now see a the number with a leading zero.

Context

This behaviour is okay if the field is used for mobile number.
In the case where it's used for currency or quantity, it could be a bit confusing.
Your Environment

Tech
Version

Material-UI
1.0.0-beta.12

React
15.0.0

browser
Chrome Version 60.0.3112.113

etc

I can't reproduce the behavior on the live demo. I'm not sure where you issue is coming from. Make sure the behavior isn't the same with a native input and provide a live reproduction example so we can have a look at it. For now. I'm closing. Thanks for your time.

I have same problem with 1.0.0-beta.40

@sersart As far as I know, you will have the same behavior with a native input.

Yes, you correct. But in native input you can remove zero, before you typing. In this case we can not remove zero

I think the issue is a combination of converting the value to Number() and (as far as I observed the behavior) onChange is fired for every value change.
According to the HTML5 Spec this is actually the behavior of onInput, whereas onChange should only fire when the Input field loses focus. Would it be possible to have both callback options?

That is a general bug in react, as e.g: parseFloat('045') === parseFloat('45') the dom input value is not updated. See https://github.com/facebook/react/issues/9402

@peterrogov Your solution is amazing! 🎉

If you have floating numbers, @peterrogov's solution will work, but use Number(event.target.value) instead of. parseInt

@peterrogov solution is not generic. what if I have 20.2002?  no chance to insert this number

Hi! I had the same issue. Managed to sort it out by converting the value from number to string and back.
TextField:
<TextField
    ...
    value={item.value.toString()}
    ...
/>

Handler:
...
value = parseInt(event.target.value);
...

This will eliminate leading zeros.

@harshit98 Sorry, but no, Peter's solution is not amazing. It's incomplete.
Problem here is that value is defined in the TextField component as a string. But value in your hook (or setState) is set to be a number. So, whenever you delete the value that shows in your component, you then parseInt("") which returns the following warnings :
 The specified value "NaN" cannot be parsed, or is out of range
because parseInt("") returns NaN
That means you need to add a test of event.target.value as follows in your handler :
event.target.value === ""  ? setMyState(0) : setMyState(parseInt(event.target.value));
Now, you will still not be able to delete 0 (your TextField has a number type, so it should not be anything other than a number), but when you type a number, you won't have a leading 0. 45 will not be 045, it will be 45.

I am no fan of converting number to string and doing the backward, as it's overkill and has flaws as some mentioned above.
My best solution is to select all text onClick to overwrite the initial value in the text field.
  <TextField
    ...
    type="number"
    inputProps={{ onClick: (e) => e.currentTarget.select() }}
    ...
  />

The UX looks like this:
https://github.com/mui/material-ui/assets/35392552/6cbaaa82-0afb-46e5-9607-5a3ce44d04ed

I think this is more robust than what has been suggested thus far:
`
const handleFocus = (event) => {
event.target.select();
}
<TextField
onFocus={handleFocus}
id="outlined-start-adornment"
type="number"
sx={{ m: 1, width: 'auto' }}
InputProps={{
startAdornment: $,
inputProps: { min: 0, max: 100 },
}}
/>
`

<TextField
    id="outlined-start-adornment"
    type="Number"
    sx={{ m: 1, width: 'auto' }}
    InputProps={{
      startAdornment: <InputAdornment position="start">$</InputAdornment>,
      inputProps: { min: 0, max: 100 },
    }}
  />

use type="Number" instead of type="number"

value = {this.state.basicSalary === 0 ? "" : this.state.basicSalary}
I hope this solves the issue.

<TextField
    id="outlined-start-adornment"
    type="Number"
    sx={{ m: 1, width: 'auto' }}
    InputProps={{
      startAdornment: <InputAdornment position="start">$</InputAdornment>,
      inputProps: { min: 0, max: 100 },
    }}
  />

use type="Number" instead of type="number"

it does work like a dream, but why?

<TextField
    id="outlined-start-adornment"
    type="Number"
    sx={{ m: 1, width: 'auto' }}
    InputProps={{
      startAdornment: <InputAdornment position="start">$</InputAdornment>,
      inputProps: { min: 0, max: 100 },
    }}
  />

use type="Number" instead of type="number"

I'm also interested on this. Why it works?


Set translation layout.

refs #119

[x] workalendar/africa/algeria.py
[x] workalendar/africa/angola.py
[x] workalendar/africa/benin.py
[x] workalendar/africa/ivory_coast.py
[x] workalendar/africa/madagascar.py
[x] workalendar/africa/sao_tome.py
[x] workalendar/africa/south_africa.py
[x] workalendar/america/argentina.py
[x] workalendar/america/barbados.py
[x] workalendar/america/brazil.py
[x] workalendar/america/canada.py
[x] workalendar/america/chile.py
[x] workalendar/america/colombia.py
[x] workalendar/america/mexico.py
[x] workalendar/america/panama.py
[x] workalendar/america/paraguay.py
[x] workalendar/asia/china.py
[x] workalendar/asia/hong_kong.py
[x] workalendar/asia/israel.py
[x] workalendar/asia/japan.py
[x] workalendar/asia/malaysia.py
[x] workalendar/asia/qatar.py
[x] workalendar/asia/singapore.py
[x] workalendar/asia/south_korea.py
[x] workalendar/asia/taiwan.py
[x] workalendar/core.py
[ ] workalendar/europe/austria.py
[ ] workalendar/europe/belgium.py
[ ] workalendar/europe/bulgaria.py
[ ] workalendar/europe/cayman_islands.py
[ ] workalendar/europe/croatia.py
[ ] workalendar/europe/cyprus.py
[ ] workalendar/europe/czech_republic.py
[ ] workalendar/europe/denmark.py
[ ] workalendar/europe/estonia.py
[ ] workalendar/europe/european_central_bank.py
[ ] workalendar/europe/finland.py
[x] workalendar/europe/france.py
[ ] workalendar/europe/germany.py
[ ] workalendar/europe/greece.py
[ ] workalendar/europe/hungary.py
[ ] workalendar/europe/iceland.py
[ ] workalendar/europe/ireland.py
[ ] workalendar/europe/italy.py
[ ] workalendar/europe/latvia.py
[ ] workalendar/europe/lithuania.py
[ ] workalendar/europe/luxembourg.py
[ ] workalendar/europe/malta.py
[ ] workalendar/europe/netherlands.py
[ ] workalendar/europe/norway.py
[ ] workalendar/europe/poland.py
[ ] workalendar/europe/portugal.py
[ ] workalendar/europe/romania.py
[ ] workalendar/europe/russia.py
[x] workalendar/europe/scotland/mixins/autumn_holiday.py
[x] workalendar/europe/scotland/mixins/fair_holiday.py
[x] workalendar/europe/scotland/mixins/spring_holiday.py
[x] workalendar/europe/scotland/mixins/victoria_day.py
[ ] workalendar/europe/serbia.py
[ ] workalendar/europe/slovakia.py
[ ] workalendar/europe/slovenia.py
[ ] workalendar/europe/spain.py
[ ] workalendar/europe/sweden.py
[ ] workalendar/europe/switzerland.py
[ ] workalendar/europe/turkey.py
[ ] workalendar/europe/united_kingdom.py
[x] workalendar/oceania/australia.py
[x] workalendar/oceania/marshall_islands.py
[x] workalendar/oceania/new_zealand.py
[x] workalendar/usa/alabama.py
[x] workalendar/usa/alaska.py
[x] workalendar/usa/american_samoa.py
[x] workalendar/usa/arizona.py
[x] workalendar/usa/arkansas.py
[x] workalendar/usa/california.py
[x] workalendar/usa/colorado.py
[x] workalendar/usa/connecticut.py
[x] workalendar/usa/core.py
[x] workalendar/usa/delaware.py
[x] workalendar/usa/district_columbia.py
[x] workalendar/usa/florida.py
[x] workalendar/usa/georgia.py
[x] workalendar/usa/guam.py
[x] workalendar/usa/hawaii.py
[x] workalendar/usa/idaho.py
[x] workalendar/usa/illinois.py
[x] workalendar/usa/indiana.py
[x] workalendar/usa/iowa.py
[x] workalendar/usa/kansas.py
[x] workalendar/usa/kentucky.py
[x] workalendar/usa/louisiana.py
[x] workalendar/usa/maine.py
[x] workalendar/usa/maryland.py
[x] workalendar/usa/massachusetts.py
[x] workalendar/usa/michigan.py
[x] workalendar/usa/minnesota.py
[x] workalendar/usa/mississippi.py
[x] workalendar/usa/missouri.py
[x] workalendar/usa/montana.py
[x] workalendar/usa/nebraska.py
[x] workalendar/usa/nevada.py
[x] workalendar/usa/new_hampshire.py
[x] workalendar/usa/new_jersey.py
[x] workalendar/usa/new_mexico.py
[x] workalendar/usa/new_york.py
[x] workalendar/usa/north_carolina.py
[x] workalendar/usa/north_dakota.py
[x] workalendar/usa/ohio.py
[x] workalendar/usa/oklahoma.py
[x] workalendar/usa/oregon.py
[x] workalendar/usa/pennsylvania.py
[x] workalendar/usa/rhode_island.py
[x] workalendar/usa/south_carolina.py
[x] workalendar/usa/south_dakota.py
[x] workalendar/usa/tennessee.py
[x] workalendar/usa/texas.py
[x] workalendar/usa/utah.py
[x] workalendar/usa/vermont.py
[x] workalendar/usa/virginia.py
[x] workalendar/usa/washington.py
[x] workalendar/usa/west_virginia.py
[x] workalendar/usa/wisconsin.py
[x] workalendar/usa/wyoming.py

taking over this PR. Already an impressive job, and a lot more to do. this is my quest.
May Crom give me the strength.


State is undefined in dashboardFilters.js

Emitting filter from a plugin leads to a TypeError: Cannot read property 'columns' of undefined exception incubator-superset/superset-frontend/src/dashboard/reducers/dashboardFilters.js line 110.
The same issue seems to happen with incubator-superset 0.37.2 table plugin when you enable the emit filter functionality.
Expected results
No exception and filter being emitted.
Actual results
Exception: TypeError: Cannot read property 'columns' of undefined exception incubator-superset/superset-frontend/src/dashboard/reducers/dashboardFilters.js line 110
Screenshots

How to reproduce the bug

Pull incubator-superset 39cce712afdc00af73daa2243cbae08a14b7dc0e
Go to data > datasets
Select birth_names
Select customize > emit filter evens
Select Data > GROUP BY and add fields gender and name
Run query
Save as tblNames and add to new dashboard dbNames
Go to dashboard
Open browser console
Click any of the cells in the table
Observe the following error

Uncaught TypeError: Cannot read property 'columns' of undefined
    at Object.CHANGE_FILTER (dashboardFilters.js?12c8:105)
    at dashboardFiltersReducer (dashboardFilters.js?12c8:169)
    at combination (combineReducers.js?89a8:120)
    at dispatch (createStore.js?61ed:165)
    at eval (loggerMiddleware.js?7f0c:68)
    at eval (index.js?b083:11)
    at dispatch (applyMiddleware.js?05f2:35)
    at eval (dashboardFilters.js?1bd4:50)
    at eval (index.js?b083:8)
    at Object.eval [as changeFilter] (bindActionCreators.js?f901:3)
CHANGE_FILTER @ dashboardFilters.js?12c8:105
dashboardFiltersReducer @ dashboardFilters.js?12c8:169
combination @ combineReducers.js?89a8:120
dispatch @ createStore.js?61ed:165
eval @ loggerMiddleware.js?7f0c:68
eval @ index.js?b083:11
dispatch @ applyMiddleware.js?05f2:35
eval @ dashboardFilters.js?1bd4:50
eval @ index.js?b083:8
eval @ bindActionCreators.js?f901:3
changeFilter @ Chart.jsx?484f:192
changeFilter @ react-hot-loader.development.js?c2cb:714
handleAddFilter @ ChartRenderer.jsx?b661:103
handleAddFilter @ react-hot-loader.development.js?c2cb:714
toggleFilter @ TableChart.js?8bc0:178
Cell.cellProps.onClick @ TableChart.js?8bc0:222
callCallback @ react-dom.development.js?7f13:189
invokeGuardedCallbackDev @ react-dom.development.js?7f13:238
invokeGuardedCallback @ react-dom.development.js?7f13:293
invokeGuardedCallbackAndCatchFirstError @ react-dom.development.js?7f13:307
executeDispatch @ react-dom.development.js?7f13:390
executeDispatchesInOrder @ react-dom.development.js?7f13:412
executeDispatchesAndRelease @ react-dom.development.js?7f13:3279
executeDispatchesAndReleaseTopLevel @ react-dom.development.js?7f13:3288
forEachAccumulated @ react-dom.development.js?7f13:3260
runEventsInBatch @ react-dom.development.js?7f13:3305
runExtractedPluginEventsInBatch @ react-dom.development.js?7f13:3515
handleTopLevel @ react-dom.development.js?7f13:3559
batchedEventUpdates$1 @ react-dom.development.js?7f13:21903
batchedEventUpdates @ react-dom.development.js?7f13:1061
dispatchEventForLegacyPluginEventSystem @ react-dom.development.js?7f13:3569
attemptToDispatchEvent @ react-dom.development.js?7f13:4268
dispatchEvent @ react-dom.development.js?7f13:4190
unstable_runWithPriority @ scheduler.development.js?b589:653
runWithPriority$1 @ react-dom.development.js?7f13:11062
discreteUpdates$1 @ react-dom.development.js?7f13:21919
discreteUpdates @ react-dom.development.js?7f13:1072
dispatchDiscreteEvent @ react-dom.development.js?7f13:4169
Show 8 more frames

Environment

superset version: 39cce712afdc00af73daa2243cbae08a14b7dc0e
also replicable with superset version: 0.37.2
python version: Python 2.7.17
node.js version: v12.18.4
npm version: 6.14.6

Checklist
Make sure these boxes are checked before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
I may be able to fix this myself if you just give me proper context so that I know where to look.

Thanks for the ticket @codepic . @ktmud @graceguo-supercat , do I remember correctly that emitting filter events from viz plugins is currently not supported?

My guess is the issue boils down to the chartIds for the visualizations emitting filter events not being present in the dashboardFilters in the state:

Any idea how I get it there? Do I need to add the FilterBoxItemControl into the controlPanel.ts in my plugin or what?

@amitNielsen you've worked on similar stuff lately, does this sound familiar?

@villebro I managed to get the filtering working :+1:

Below are the relevant changes I needed to do in superset-frontend

As it seems, the check form_data.viz_type === 'filter_box' is hard coded so I added my viz_type to the check and my plugin started emitting filter events correctly.
There's a catch. If I add filter_box into the dashboard, the functionality breaks and the table only listens to the filters set in the filter_box plugin.
However this is not an issue as I can still use multiple custom plugins which emit filters and they seem to be working as expected:

Since hard coding viz_type check is not optimal, I would suggest we would add a flag to the form_data when ever a plugin developer adds the FilterBoxItemControl into their control panel. Then we can check in dashboardState.js and getInitialState.js that if this flag is set to true.
This way plugin developers could start implementing their own filters just by adding FilterBoxItemControl into their controlPanel.ts and using the hooks provided by superset.
As it currently stands, having custom filtering functionality is impossible with Superset without modifying superset-frontend yourself.

Erinomaista työtä! 😀  (great to see a fellow Finn here! 🇫🇮) Ping @suddjian, this is probably very relevant for the native filters work you're doing right now. @codepic please drop by the Superset Slack workspace, would be great to discuss this theme in more detail with you and see how to collaborate on this!

@villebro kiitos ;)
@suddjian  Actually, I already found out that the FilterBoxItemControl emits filter_configs array when added to controlPanel so I tried the following:
@@ -169,7 +169,7 @@ export default function getInitialState(bootstrapData) {
     }

     // build DashboardFilters for interactive filter features
-    if (slice.form_data.viz_type === 'filter_box') {
+    if (slice.form_data.filter_configs && slice.form_data.filter_configs.length > 0) {
       const configs = getFilterConfigsFromFormdata(slice.form_data);
       let { columns } = configs;
       const { labels } = configs;

and
@@ -284,7 +284,7 @@ export function addSliceToDashboard(id, component) {
     ]).then(() => {
       dispatch(addSlice(selectedSlice));

-      if (selectedSlice && selectedSlice.viz_type === 'filter_box') {
+      if (selectedSlice && form_data.filter_configs && form_data.filter_configs.length > 0) {
         dispatch(addFilter(id, component, selectedSlice.form_data));
       }
     });
@@ -294,7 +294,7 @@ export function addSliceToDashboard(id, component) {
 export function removeSliceFromDashboard(id) {
   return (dispatch, getState) => {
     const sliceEntity = getState().sliceEntities.slices[id];
-    if (sliceEntity && sliceEntity.viz_type === 'filter_box') {

And for my surprise, I didn't break the FilterBox plugin and my plugin works :D
In any case @villebro, I will drop by the Superset Slack workspace a little bit later as I have this to prepare for our visualization meeting and see what they think of it.

Related to #9593

dashboard filters totally got refactored, you should check out the DASHBOARD_NATIVE_FILTERS ff and the DASHBOARD_CROSS_FILTERS ff
we will probably soon introduce emitting filter from existing plugins

This issue appears to have survived the recent refactoring work. For example, incubator-superset/superset-frontend/src/dashboard/actions/dashboardState.js lines 337 and 347 both still contain hardcoded references to filter_box.


Import-vcmdtapp creates MDT applications with client only OS filters

Expected Behavior
If filters are to be used, they would allow for installation on server operating systems as well as reference images are created for xenapp/rds installations.

Filters on x64 apps create a filter for windows 7 x86 and up, and windows 7 x64 and up.
Recommended Behavior
Add filter for Windows Server 10 x64 and up
Steps to Reproduce
Run against a server operating system in a client task sequence.

Aaron, debugged this a bit on some other systems, and the problem actually is related to the "working directory" value that is created in the MDT application. The subfolder is not present in the path. I am not sure if the filters are a actually a problem anymore, but I have removed them during testing.

it looks like this code was stripped out in commit e7b192f
$dir = "$Publisher VcRedist$($Vc.Release) $($Vc.ShortName) $($Vc.Architecture)"
it was used for
-WorkingDirectory ".\Applications$dir"                     -DestinationFolder $dir
destination folder was updated to
                DestinationFolder       = "$Publisher VcRedist\$($Vc.Release) $($Vc.ShortName) $($Vc.Architecture)"

but working directory is still
                WorkingDirectory        = ".\Applications\$dir"

So this needs updating to
                WorkingDirectory        = ".\Applications\$Publisher VcRedist\$($Vc.Release) $($Vc.ShortName) $($Vc.Architecture)"

at the moment none of the imported applications in MDT work, they fail to install with file not found as the working directory is just ".\Applications"

This should now be fixed in the latest development commit and will make it into the latest release.

Fixed in v<IP_ADDRESS>; commit 7004e11b4e71aa6b84834d1977414b157546cc8d


binary.Write(net.UDPAddr.Port) silently fails

Using go 1.7.3 on linux/amd64.
I tried to use binary.Write on a net.UDPAddr.Port, nothing was buffered.  This took a while to debug.
https://play.golang.org/p/CtZgXsWMUL

I would have expected the binary.Write to either do the right thing (buffer two octets of data) or generate an error (either at compile time or at runtime).

It did return an error. You didn't check it. https://play.golang.org/p/owZlw_-2LP

My bad.

Thinking about it some more -- shouldn't it panic instead of returning an
error?  It's clearly a programmer's error, and it's all the more confusing
since Buffer.Write is documented as never returning an error.

bytes.Buffer's documentation is irrelevant. You're not even making it that far. You're passing in something bogus to binary.Write and that is what is returning an error.

bytes.Buffer's documentation is irrelevant. You're not even making it that
far. You're passing in something bogus to binary.Write and that is what is
returning an error.

I realise that.  But I find this behaviour confusing, I'd expect it to
panic in this particular case.

If something returns an error, check the error. That is the rule in Go.
A panic is not appropriate in this case.


(JAX):Live at least 30 years as per Avie's request

What is your goal?
I have to live at least 30 years or Avie will be mad
Steps to achieve the goal (not required)

[ ] Live 5 years
[ ] Live 10 years
[ ] Live 20 years
[ ] Live 30 years

Do you have a target date for this? If yes, write below
30 years
What will you achieve by completing this goal?
Avie would not hate me
Additional context

You don't have any PR. Update the file every day.😌


The createDir() method has been deprecated

When I set the option to keep original images there is a deprecation warning in the CP:
"The createDir() method has been deprecated. Use createDirectory() instead."

Steps to reproduce

Enable the "Non-destructive" setting
Do some resizing with the plugin

Additional info

Plugin version: 2.0.10
Craft version: Craft Pro 3.6.6
Multi-site: No

Additional context

Fixed in 2.1.0


Image Classifier is significantly more accurate when trained with CPU vs GPU

Possibly related to #2466 opened by @FaithlessDbo
System Information:

Windows 11 22H2
Model Builder 2022 (<IP_ADDRESS>3404)
Visual Studio Version: 17.4.3
Target Framework Version: 6.0
For both CPU and GPU operations:

Microsoft.ML 2.0.0 package
Microsoft.ML.Vision 2.0.0 package

For CPU operations:

SciSharp.TensorFlow.Redist 2.3.1 package

For GPU operations:

SciSharp.TensorFlow.Redist-Windows-GPU 2.3.1 package
CUDA 10.1
cuDNN 7.6.4
NVIDIA driver 531.14 for NVIDIA RTX A2000 Laptop GPU

Describe the bug:
Model Builder was used to create an image classifier trained on CPU-local. The dataset was comprised of 20,972 total images over 2 categories. MicroAccuracy was 0.9995 in 4581sec. Scores using this model are almost always >99%. These are really terrific results, but predictions complete in ~200ms which does not meet production requirements for speed.
To achieve faster predictions, a second ML.NET model was attempted to be trained using the same dataset on the same computer, but using GPU-local training. In this case, everything appeared to work as expected without errors, with training completing much faster. However, the GPU MicroAccuracy achieved was only 0.7312. This is significantly lower than with the CPU training. Prediction scores using this model are around 50% (usually 52%/48%).
Why would a GPU-trained model have a lower accuracy compared to a CPU-trained model using an identical dataset?
Please review the screenshots and log files provided below. I'm happy to work with you to reproduce this issue or provide further logging. Thank you!
CPU Model:
    {
      "Scenario": "ImageClassification",
      "DataSource": {
        "Type": "Folder",
        "Version": 1,
        "FolderPath": "D:\\Data Labeling\\Labeled Dataset 1\\Png"
      },
      "Environment": {
        "Type": "LocalCPU",
        "Version": 1
      },
      "Type": "TrainingConfig",
      "Version": 4,
      "TrainingOption": {
        "Version": 0,
        "Type": "ClassificationTrainingOption",
        "TrainingTime":<PHONE_NUMBER>,
        "Seed": 0
      }
    }

Log File:
MLModel_CPU-81N5HX.txt
GPU Model:
    {
      "Scenario": "ImageClassification",
      "DataSource": {
        "Type": "Folder",
        "Version": 1,
        "FolderPath": "D:\\Data Labeling\\Labeled Dataset 1\\Png"
      },
      "Environment": {
        "Type": "LocalGPU",
        "Version": 1
      },
      "Type": "TrainingConfig",
      "Version": 4,
      "TrainingOption": {
        "Version": 0,
        "Type": "ClassificationTrainingOption",
        "TrainingTime":<PHONE_NUMBER>,
        "Seed": 0
      }
    }

Log File:
MLModel_GPU-AWA83L.txt

@mg-yolo-enterprises   this is very interesting question " Why would a GPU-trained model have a lower accuracy compared to a CPU-trained model using an identical dataset?"
And thank you very much for the detailed information.
@LittleLittleCloud  & @JakeRadMSFT  thoughts ?

@mg-yolo-enterprises This is indeed what I'm experiencing. Thanks for the mention and the far more detailed version of the issue at hand.

I don't have the answer right now, The cause of the difference in training performance between CPU and GPU can be various: a bug in cuda/cudnn, different accuracy in float operation, different initialize seeds... It's difficult to say which exactly could be the possible reason that cause this training performance difference.
It would be helpful if you can provide with us your dataset for reproduction, otherwise we can try reproducing it on other open-source project as well but that might cause more time.
In the meanwhile, the work-around you can try is

training using larger epoch in GPU training. It requires you to use ML.Net framework as ModelBuilder doesn't allow you to customize epoch number. It would be a lovely feature for deep-learning scenario though @luisquintanilla
training using cpu and inferencing using gpu. The model should use the same weight for cpu/gpu training and you can still use gpu for inferencing even if model is trained on cpu


Add natural language description in GV state machines

In the same manner that natural language appears in GV class diagrams, as per issue #1401, the same should be true in state machines.
In a state after the name of the state (which appears now), it should say:
This is the initial state the object is in when created
(if it is the first state of a top level state machine and has an incoming arrow from a start circle)
This is the initial state when VVV is entered
(if it is the first state of a nested state machine and has an incoming arrow from a start circle)
State is entered if XXX occurs when in state YYY
(the above repeated as many times as needed, could be zero if the initial state)
(and after the word 'occurs' it might say ... 'and guard [ZZZ] is true' if there is one
On entry into this state an entry action is executed
(if there is one)
On entry to this state a do activity is started in a separate thread and continues until it ends or the state is exited
(if there is one)
State is exited if PPP occurs; the object then goes to QQQ
(repeated as needed and also with the 'and guard [RRR] is true if there is one)
On exit from this state an exit action is executed
(if there is one)
VVV and PPP would normally be an event, but could also be 'after m milliseconds

Does VVV represented the next state or the state we are currently in?

VVV is a parent state.


Is it possible to control how the samples are chosen in bagging?

Summary
I have a dataset with a categorical feature that is not used for training, but I would like to use that feature to control how samples are selected during bagging.
Motivation
while harmfull for training, the categorical feature groups the samples and thus improves training accuracy when the groups are not split during training
Description
I would like to have only complete groups of the feature selected during bagging. Implementations I could imagine

a categorical variable can be passed so that only groupings of this are considered during bagging. Problem: as the variable is not to be used for training, it cannot be a normal feature in the train_set. Maybe a bagging_groups parameter in the DataSet constructor?
giving control to the user on the bagging by being able to pass a function with signature bag(samples, fraction) that returns the selected samples during that iteration

References
the evaluation metric works inside the groups, so using pandas it does look something like
score = data.groupby('feature').apply(lambda df: some_custom_function(df)).mean()

This is currently not possible as far as I am aware. I just came here to put a request in for this. I have at least two use cases in mind, where it would be very helpful:

When there are multiple records over time for an individual (could be a person, a store, an item etc.). If your intention is to generalize well to new unseen individuals, then sampling the complete data for an individual in each tree is likely helpful.
When you do time-to-event (aka survival) prediction and you don't want a constant hazard function (=could get that via having a single record and using a Poisson target potentially with an offset), but rather want piecewise constant over time. In that case, you would split records into time intervals (e.g. for an individual with an event after 5 years, you'd create records with feature year=1,2,3,4,5 and event count = 0,0,0,0,1 and use Poisson on that). In that case, you want to, again, do bagging for complete individuals.


git rm -r vendor - to remote repo

ignorar vendoring en repo principal

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

con el CLA xd


Visual Studio 2022 support #3

Added support for Visual Studio 2022. Due to braking changes from VS19 to VS22 for extensions mentioned here, the project setup had to change - having core business logic in a shared project and additional projects targeting either VS19 or VS22 version.
Note: VS22 has its own package Guid and should be separate from VS19 as per Microsoft's article mentioned above.

@houstonj1 or @KaidenR could you have a look? Or should I ping someone else?


Shading 2D/ 3D/ 2D switch bug fix

Description
@alisterburt this fixes an additional bug in your shading PR which occurred when you ran python examples/add_surface_2D.py and then toggled to 3D and then back to 2D. I needed to add a
            if self.node.shading_filter is not None:
                self.node.shading_filter._attached = False

I also moved the logic out of the surface layer itself into the vispy file which fixes the one broken test.
I had to merge in master, but just pushed to master on your PR too, so hopefully the diff will be smaller now.
Let me know what you think! I think this is all good to go now and bug free even in the weird corner cases!!
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

Hmm git diff still has all the other files changed :-( not sure how to fix that, it's just the stuff from master. Maybe it all needs to be rebased? ah git :-(


feat(json-schema-form): add input-extra slot

To Reviewers

[ ] Skipping review is not a problem (style, chore ONLY)
[x] Not that difficult

Type of Change

[x] New feature
[ ] Bug fixes
[ ] Feature improvement

[ ] These changes require a usage change

[ ] Others (performance improvement, refactoring, CI/CD, etc.)

Checklist

[x] Updated Storybook documents for component
[ ] Wrote test codes for composable, utils and etc.
[x] Tested with console(if usages are changed)

Description

add input-extra slot

:tada: This PR is included in version 2.0.0-beta.81 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Need to update installation instructions

Sent with GitHawk

In particular, need to document that LaTeX and pdf2svg are now optional (see also #77 )


Print emulation DCTL

Hi! Thank you for sharing all of these wonderful tools! Could you please tell a bit about print emulation DCTL? What's logic behind that? I've tried to get it from the code, but my skills in coding are limited to copying/pasting with some modifications.

Hey great question! Basically that DCTL in particular is intended to replicate an effect I saw in a Cullen Kelly video (and you can somewhat see this if you use Resolve's built-in film emulation LUTs) in which the YMK colors are transformed to be brighter and more saturated than RGB colors. You could see it if you set up a 3D histogram like I have in my screenshot, f(1, 1, 0) > f(1, 0, 0) + f(0, 1, 0) so it skews the shape of the whole 3D cube in an interesting way.
Honestly, I don't think the math I used in this DCTL is based on any physical principles, but it's an interesting operation that doesn't come with Resolve normally.
BTW when making this screenshot, I realized I had some compilation issues with this DCTL because I overloaded the mix function. I've posted a fix so you might have to redownload the DCTL if it wasn't doing anything earlier.


Milestone 1 tasks and devision of work

preprocess the data : Sifan
create the project structure and class file : Charles
define and document the fit method : Waleed
predict and score : Sara
readme file and other files : Collaboration

Great planning, excited to work with everyone! 😄


Error  loading

Hi
Am trying to use this tool but am getting an error 'Invalid dimension' please assist

Hello Chuom, should be corrected with latest version. You will need to be on June 2018 though.


Release Razor views/pages should be minified

Is your feature request related to a problem? Please describe.
When publishing your application the Razor views should be minified as part of the build.
Describe the solution you'd like
Build my well-indented code, get output with no extra whitespace.
Describe alternatives you've considered
Third-party kludges exist but they tend to do heuristic parsing of cshtmls with regexes or IndexOf. This should be built into the system itself which by definition understands cshtml perfectly.
Additional context
https://github.com/aspnet/Razor/issues/423 is related but it seems to have been closed with no final comment when the project was archived.

Thanks for contacting us, @lcsondes.
This is not an area we have immediate plans to invest in.

@mkArtakMSFT Could this be scheduled for a future version perhaps?

Not really, @effyteva.
We usually prioritize asks based on community asks. So far, we haven't heard much feedback from the community that this is something very important. That said, we don't want to add work on our backlog, for which we don't see any mid-term need.


Added Option to close Dropdown on Multiple Select

Needed an option to close the dropdown on multiple select boxes
Kept default behavior to stay open
Setting Option: "closeMultipleOnSelect" to true enables closing on selection

This seems like poor UX to me, but I'm willing to consider this option if somebody can make a case for it.


Create new lane types to express different types of buffers for prote…

…cted bike lanes. They're only created manually right now, to explore rendering.
The goal is to start modeling different types of bike lanes -- some are right in the door-zone of street parking, others have flimsy little flex posts protecting from cars, but some have proper barriers in place. Eventually we'll use this in the routing and simulation layer. But the goal for this PR is actually just to explore the rendering style.
I've started with 4 types of barriers, but happy to add more!
For each of these, any better ideas for visualizing in our top-down view?
Stripes
Top-down rendering:

Reference:

Flex posts ("wands" in the UK)
Rendering:

Reality:

Planters
Rendering:

Reality:

Jersey barrier
Rendering:

Reality:

Next steps
There's more work needed to create/modify these properly in the road editor UI. I also want to start tagging these in OSM, and then importing into A/B Street. https://wiki.openstreetmap.org/wiki/Berlin/Verkehrswende/Radwege#Tagging-Beispiele seems to have some traction.

@trangrei, @matkoniecz, @westnordost -- any design ideas for drawing these bike buffers in a ~top-down view? Or other types of buffers that should be included with this first draft?

You seem to have left out the most important segregation: A curb, so the cycle lane becomes a cycle track.
The drafts look fine to me, I'd maybe make the planters more bush-like for better visual distinction (after all the planters don't need to be rectangular)

I'd maybe make the planters more bush-like for better visual distinction

Those plants look nice, though I don't think we have a great way for drawing sprites like that. We do have textures at our disposal, but they may be cropped arbitrarily.

You seem to have left out the most important segregation: A curb, so the cycle lane becomes a cycle track.

Ah, true! Any thoughts how to create some sense of depth?

though I don't think we have a great way for drawing sprites like that.

Those plants do look nice! And we can draw them without too much trouble -- create an SVG of the plant, then place it like a stencil every few meters, the same as we do with bike stencils

I found some old concept art that I had commissioned in the early days:

Or use a continuous white line before the gutter to mark the end of a street and the beginning of a sidewalk

Jersey barrier looks flat in this example right now, making it more 3D would be nice.

Planters

I would change green shade, right now it has shade of toxic waste from cartoon. Some symbolic vegetation as mentioned also would be nice.

Flex posts ("wands" in the UK)

I would make dost smaller and denser, right now it looks like a row of advertising columns

Stripes

No idea is there OSM tagging for that but sometimes entire lanes are striped out and not drivable.

curb

Some lanes have both curb and bollard separation

Linking to #712 it seems planters can be linear features. I agree with comments in https://github.com/a-b-street/abstreet/pull/704#issuecomment-881797422 that a leafier shade of green could be good but just getting them in there will be amazing and, by the looks of it, that's what this PR does. Amazing work.

This PR https://github.com/a-b-street/abstreet/pull/713 makes the planter look like this:

Inspiration: https://wiki.openstreetmap.org/wiki/Tag:barrier%3Dplanter

Looking forward to seeing this rendered properly in a digital map (they are ignored completely in all OSM renderers I've seen):

There is a video of them somewhere, a work of art that is as of yesterday represented on OSM as follows (invisible unless you select the way):

I think the first cut of this is done. There are 5 types of buffers now available in the road editor:

(Yes, those icons need some work.)
Stripes:

Flex posts:

Planters (need to center between the stripes better):

Jersey barrier:

And just a raised curb:

Some of my next steps:

improve rendering and the editor icons (with help)
rethink the road editor UI. Treating all of these as regular lane types is weird. Maybe there should be a single barrier dropdown, or a way to denote a category of lane. Or maybe the barrier lanes should be "options" on a bike lane/sidewalk.
Investigate OSM tagging and start picking these up during map imports

https://twitter.com/redblobgames/status/1418081197037473798 raised a great idea -- just cheat and stick in a quasi-side view of an object, to create a better sense of depth. (We do this for stop signs already.) All the curvy roads at every angle could get tricky, but the simple cases work well:

just cheat and stick in a quasi-side view of an object

I think this could work for more things. I think in your particular example, I don't like the look of it, but that has more to do with the particular photo-realistic asset you choses which looks very out of place with the rest of the ABStreet style.

Just catching up with this now. Overall I think the main point is that this PR enables people to add separation between modes. That is hugely important, and a key element of streetmix. My take is that the fact that the basic functionality exists is more important than the aesthetics, and that seems to be implemented based on this screenshot which looks amazing:

Only question: do all these great new options clutter the UI? Less can be more.

Or for cycleways behind kerbs, like this:

Cycle track (=cycleway separated by kerb): The paving on the cycle track should make it clear that the track is off the roadway. There is a slight 3D effect for the kerb

the diagonal striping should go all the way into their containing rect

Oh wow this makes such a huge difference in quality!

the planter's look like their corners are chopped off

https://github.com/a-b-street/abstreet/blob/1d7c8ce89cf3180a92da4900bb4083a3d8960089/geom/src/ring.rs#L48
I agree this is annoying. Pre-existing problem also affecting building outlines and anything we hover on. Right now I'm just generating a polyline for the boundary, then doing the normal algorithm to thicken it into a polygon. One hack would be to just stick in an extra polygon to fill in the gap, but it would be a funky Polygon whose boundary isn't a nice ring. Proper fix would be to make it a polygon with a hole.. I'll try and improve this separately.

With this iteration of the jersey barriers, the color does help with the depth perception a bit, but they're still a little hard to distinguish.

These ideas could work. I'll leave this as an open design question for now. If someone makes an example picture, I can make the code to generate it. But I can't even picture what would look good yet.

that has more to do with the particular photo-realistic asset

Yeah, the side-view flex post thing was a quick example. Need to find an actual SVG flexpost. I'll look around.

do all these great new options clutter the UI? Less can be more.

100% agree. I might make the barrier a dropdown, or try to express it in the controls as a specialization of the bike lane.

The paving on the cycle track should make it clear that the track is off the roadway

There are so many things I love about this image! I'm going to experiment with copying that paving style, the colors, and the kerb style. I think it would improve the sidewalks in A/B Street in general, not just for kerb-protected cycletracks. Will keep you posted, thanks for sharing that Streetcomplete example!

Thank you everyone for the feedback! Merging this as a first step, will keep exploring rendering style and cleaning up the editor controls.

100% agree. I might make the barrier a dropdown, or try to express it in the controls as a specialization of the bike lane.

+1 to that but more importantly amazing work on this epic PR tested, refined, and deployed on the main branch in record time :fire:


Implement DX baseline to write proper Readme file

Providing a satisfying Readme file (and corresponding documentation) is still an open task (https://github.com/demos-europe/edt/issues/56). To do so, it is sensible to improve the developer API of the library first, instead of writing the Readme file to explain a bad API.

Will be split into smaller PRs


Possible XPA communication problem on Mac OS 10.8.5

Connection timeout with the ds9. Try to increase the wait_time parameter (current value is  10 s)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/lubeda/astronomy/site-packages/lib/imexam-0.3.dev-py2.7-macosx-10.6-x86_64.egg/imexam/connect.py", line 62, in __init__
    target=target, path=path, wait_time=wait_time, quit_ds9_on_del=quit_window)
  File "/Users/lubeda/astronomy/site-packages/lib/imexam-0.3.dev-py2.7-macosx-10.6-x86_64.egg/imexam/ds9_viewer.py", line 213, in __init__
    self._set_frameinfo()  # initial load
  File "/Users/lubeda/astronomy/site-packages/lib/imexam-0.3.dev-py2.7-macosx-10.6-x86_64.egg/imexam/ds9_viewer.py", line 246, in _set_frameinfo
    frame = self.frame()
  File "/Users/lubeda/astronomy/site-packages/lib/imexam-0.3.dev-py2.7-macosx-10.6-x86_64.egg/imexam/ds9_viewer.py", line 886, in frame
    frame = self.get("frame").strip()  # xpa returns '\n' for no frame
  File "/Users/lubeda/astronomy/site-packages/lib/imexam-0.3.dev-py2.7-macosx-10.6-x86_64.egg/imexam/ds9_viewer.py", line 617, in get
    return self.xpa.get(param)
  File "/Users/lubeda/astronomy/site-packages/lib/imexam-0.3.dev-py2.7-macosx-10.6-x86_64.egg/imexam/xpa_wrap.py", line 12, in get
    r = xpa.get(self, param.encode("ascii"))
  File "xpa.pyx", line 172, in xpa.xpa.get (wrappers/xpa.c:1797)
  File "xpa.pyx", line 112, in xpa._get (wrappers/xpa.c:1037)
xpa.XpaException: XPA$ERROR: no response from server during handshake (?:?)

Don't see this problem anymore


Before proceeding, is there an existing issue or discussion for this?

[X] I have done a search for similar issues and discussions.

Description
I opened traffic-editor and I drawed lanes,walls and saved the file after that got a yaml file i will share the files
Traffic-editor:

Yaml file:
i am not able to post it here i will shhare you the screen shot of it

from this yaml i got 0.yaml i did by using below command
ros2 run rmf_building_map_tools building_map_generator nav /home/research/rmf_ws/src/rmf_traffic_editor/maps/new_map.building.yaml  /home/research/rmf_ws/src/rmf_traffic_editor/maps/
then  after doing colcon build i didnt get the maps or yaml in  share folder.
anyone who solved this could you reply it or who has experience in this
thank you.

@josh-001 - please open a discussion regarding this (link in template above), as this is not an issue but rather a how to question.
As for pasting codeblocks please see Github's guide on markdown syntax


Feature/initial release

Adding the following functionalities:

Deposit
Withdraw
Transfer
Smart Contracts
Smart Accounts
Tokens
Paymaster

[ ] Fix bugs and regression test all functions.
[ ] Add Unit tests to cover basic functions.

Hey guys, cool that you're workin on a new SDK!! I was wondering, any ETA for the initial release? 😅 We might want to use this for ETHGlobal Paris (July 20th).
Some feedback from trying to do the examples using the current main branch.
import ZkSync2

let zkSync: ZkSync // Initialize client
let signer: EthSigner // Initialize signer

let wallet = ZkSyncWallet(zkSync, ethSigner: signer, feeToken: Token.ETH)

For the zkSync instance, I only currently see the JsonRpc2_0ZkSync to implement that ZkSync protocol. It can not be used tho as it's not public. You might wanna change that if that's how it's supposed to be used.


Updated to akka 1.2.0

This PR needs more fixing. Will work on this today

@Danthar could you also send in a PR to master with these changes from dev and tag a release for each of these?


[MODEL EVALUATION REQUEST] HuggingFaceTB/SmolLM2-360M-Instruct

Model ID
HuggingFaceTB/SmolLM2-360M-Instruct
Model type
Decoder model (e.g., GPT)
Model languages

[X] Danish
[X] Swedish
[X] Norwegian (Bokmål or Nynorsk)
[X] Icelandic
[X] Faroese
[X] German
[X] Dutch
[X] English

Merged model
Not a merged model

This is live on the leaderboards now 🎉


Fix broken "Always open in" feature

Fixes #26 .
Most likely not the prettiest fix (I don't even know JS, pretty much went in blind) but it works.

Will it ever be merged?

Well done Watkuren, interesting to see if this gets merged.


is_private_collector vs is_private_collection is confusing...

Suggestion: keep the current name for is_private_collection (identifies that an institution is an individual/private collector regardless of having a RISM siglum) since there the field name is straightforward. For is_private_collector, at least change the public-facing name to something more descriptive (no_rism_siglum?), but perhaps just change the field.

Besides its use in the constraint that institutions should generally have RISM sigla, I'm not totally sure whether we need this field either.

Besides its use in the constraint that institutions should generally have RISM sigla, I'm not totally sure whether we need this field either.

That's its whole purpose -- there needs to be a way to conditionally require the RISM siglum be entered, and the way to do that is to have this field, where either it, or the siglum, but not both, are filled. The idea is that, if it doesn't have a RISM siglum, there is no "public" registration of the details of the collection. (the assumption is that if you have an entry in RISM with a siglum, then you are making a public statement that you have some books, and that there is a way to contact you to find out more. So it's not "private" as in "a private person" it's private as in "the details of the collection are not available to the public."
The "is_private_collection" field was added afterwards, to meet the requirement that individual holders of MSS are identifiable, whether or not they have a RISM siglum assigned. It was the best I could come up with.
If either of them were to change, I would suggest the latter (is_private_collection) -- Possibly "individual collector" or something like that. It's easier because it's not really used anywhere, whereas the setup for the is_private_collector touches a bunch of code.

Yeah, I understand the history/rationale. My point is only that it doesn't currently mean anything in addition to an institution without RISM siglum. In any case, this is the way it is now and doesn't seem worth revisiting in the absence of a compelling reason; maybe someday users will be allowed to add institutions (this could help us force them to do the right thing) or there will be a secret third type of institution to add to our Venn diagram and we'll do more with this checkbox.
In any case, the current display means that Debra/Anna don't know what to do with these checkboxes and I have to look at the help text each time because I'm afraid I'll mix up "collector" vs "collection", which is really the problem.
What about we change the display for is_private_collector to just "Is Private" (keeps "private" per the meaning @ahankinson notes above -- similar to the "private notes" field -- and avoids substantial code changes) and the is_private_collection field to collection_type which can default to "Institutional" but be changed to "Individual" or "Private"?
I'll run by Debra too to see if that distinction seems clearer for her continued use.

What do you think of something like "organization" or "individual" to distinguish between corporate vs. personal collections?

This is great, imho! I realized to have an "Institution" of type "Institutional" made no sense, but "Organization" is perfect.

Perhaps something like "Ownership: Organization | Individual" ?

Also makes a lot of sense!

Ok, there exists general buy-in on "Private" boolean and "Ownership: Organization | Individual" so we'll go ahead with that...


Revamp search results header

This tackles the following:

[x] emoji for specific wordclass (closes #358)
[x] replaces English wordclass with English inflectional category (closes #434)
[x] popup for inflectional category (closes #447 )
[x] Updates layout to match latest mockups (closes #445)

EDIT: it's ready! Here are some screenshots:
non-lemma form with definition:

its linguistic breakdown pop-up:

its inflectional category pop-up:

non-lemma:

lemma:

Codecov Report

Merging #462 into master will increase coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #462      +/-   ##
==========================================
+ Coverage   86.38%   86.48%   +0.09%
==========================================
  Files          67       67
  Lines        2637     2656      +19
==========================================
+ Hits         2278     2297      +19
  Misses        359      359

Impacted Files
Coverage Δ

CreeDictionary/API/models.py
88.61% <100.00%> (+0.32%)
:arrow_up:

CreeDictionary/API/schema.py
100.00% <100.00%> (ø)

...eeDictionary/API/templatetags/inflection_extras.py
64.15% <100.00%> (+5.45%)
:arrow_up:

Continue to review full report at Codecov.

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

@aarppe, note: once this is merged, I'd shorten the inflectional category information for N+*+D forms. They're a bit... noisy:


feat: add github workflow and script to update synapse tables

Here's the code for updating existing synapse tables when a push to project/data files is made to main.
This script will only work as long as the expected columns remain the same. I ran into too many bugs when trying to feed the synapse client a tsv to update tables with directly, which is why this script gets the rows from a tsv to add them as values.
We get only the files changed and pass them to the script. The script takes the changed files, takes snapshots of the associated tables, deletes all of their data, and repopulates using the new tsv. This may seem inefficient, but it's the best workaround for now, until synapseclient supports upserting to tables.
I also have the code for creating schemas on my fork here: https://github.com/katiestahl/b2ai-standards-registry/blob/main/.github/scripts/create_synapse_tables.py
I was unsure if I should add that to this PR or not, since it's pretty messy and could use some love in that regard (but it gets the job done :-) ), but it illustrates the schemas as they currently are, and if we ever need to add or update columns, we will need to update and run that script.
Also note: before merging this script, we will need to create a service account in synapse for updating the tables and add its auth token as a secret SYNAPSE_AUTH_TOKEN to our github actions. We should have a dedicated account in Synapse that's not tied to any of our personal accounts, so it's clear when the tables have been updated from the github action.

@caufieldjh re-requesting your review since I added some documentation and added the script for updating the table schemas in synapse. Someday, it would be cool to automate this, but synapse's defaults for creating schemas from tsv files directly doesn't quite work (ex; I ran into an issue where I created the tables from the tsv but went to update them after I deleted all of the rows with the exact same data, but the default character limits were not adjusted. So that's why everything has custom processing. Any time synapse client sees a string, it automatically imposes a 50 character limit).


fix: fix broken publish action

:tada: This PR is included in version 1.1.0-dev.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Support for box-shadow

Hey @zzarcon love what you're doing here with this library.
Any chance there is a solution here that implements exactly what you have but for box-shadow instead of just a border?

I'm working on building a solution for this now, but was wondering if you or anybody else has done this.
If not I'm happy to work on it and open up a pull request

That would be amazing @adrielklein ! Please do so and let's see how can we get it merged here. Also, if you are interested I could make you maintainer afterwards 🤞

Hey @zzarcon, so after doing some tinkering, I've determined that it's pretty hard to get the box-shadow showing up properly using this library.
The reason for this is that box-shadow must be applied to the elements above and below the scroll area, not by inserting elements before and after the scroll area using css like you do in this library with ::before  and ::after selectors.
However, i was able to implement a solution by creating a scroll handler on the scrollable element, then keeping track of when the user is at the top or bottom of scroll area. Then using that state, I was able to either apply or not apply a box-shadow to the surrounding elements. Also I put a css transition on box-shadow so it shows up smoothly.
I will try to find some time to create a CodeSandbox of my solution to give you a more concrete example of what I'm rambling about. From there I can see if there would be an easy way to integrate that into this library.

@zzarcon yes would be great to be a maintainer!


Updating the namespace for charp in proto

Description
Updating the namespace for charp in proto.
The Dapr.Client.Grpc namespace is now used by the hand written C# client library.
Autogenerated code will use namespace Dapr.Client.Autogen.Grpc

@youngbupark  This seems to be a new check:  dapr-dev-container / build dev container (push)
Is it ok to merge this PR as this PR can't cause it to fail?

@youngbupark This seems to be a new check: dapr-dev-container / build dev container (push)
Is it ok to merge this PR as this PR can't cause it to fail?

It is failing to generate dev-container image. I will fix next week. it should be fine. You can ignore it :)

@youngbupark This seems to be a new check: dapr-dev-container / build dev container (push)
Is it ok to merge this PR as this PR can't cause it to fail?

It is failing to generate dev-container image. I will fix next week. it should be fine. You can ignore it :)

Sounds good, Thanks!


Custom boto3 initialization

Hi!
Is it possible to configure the library initialization in a similar way?
s3 = boto3.resource('s3',
  endpoint_url='http://myhost.com:9000',
  config=boto3.session.Config(signature_version='s3v4')
)

Thank you for this project!

Hi @pakimov2,
glad that you find this tool useful. Can you check if these instructions help you addressing your issue? You can create a profile with your overrides and then use it in the remote URI like<EMAIL_ADDRESS>https://docs.aws.amazon.com/sdkref/latest/guide/feature-ss-endpoints.html#ss-endpoints-config

Hi @massi-ang !
Excuse me for delay. Yes, this configuration solved my issue.
Thank you very much


A unit test is failing

unittest_reinvent/scoring_tests/scoring_components/test_predictive_property_component.py is failing. This is due to changing models/smiles.
Also, the regression fixture functions are currently using the wrong models.

OK, this is fixed.


Thanks

Since the repository has no discussions enabled, I figured I create an issue for thanking you.
With your plugin I could improve the performance of my local styleguide quite a bit, to make switching HTML pages more snappy.
All that was necessary is to add the generated HTML files to the warmup.
Thanks a lot.
Have a nice weekend :)

Glad to hear that ❤


Update license fields.

Allow single values or lists for the license fields at the top level, or in a Reference.
Also remove the spdx-licenses gem dependency as we can now use the SPDX list in the schema.
Fixes #59.

Coverage increased (+0.1%) to 94.7% when pulling cb208038f5aeae625a0126bd0fbf471cf81972e6 on update-licence-fields into 0124d1b6238c5e779f8357303fcb9d9694c70f45 on main.


release version 2.0.1

Codecov Report

Merging #190 into master will decrease coverage by 0.17%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #190      +/-   ##
============================================
- Coverage      96.9%   96.73%   -0.18%
- Complexity        0       21      +21
============================================
  Files             1        3       +2
  Lines            97      153      +56
  Branches          0        3       +3
============================================
+ Hits             94      148      +54
- Misses            2        4       +2
  Partials          1        1

Flag
Coverage Δ
Complexity Δ

#go
96.9% <ø> (ø)
0 <ø> (ø)
:arrow_down:

#java
96.42% <ø> (?)
21 <ø> (?)

Impacted Files
Coverage Δ
Complexity Δ

.../java/com/aliyun/ccpcredentials/models/Config.java
33.33% <0%> (ø)
1% <0%> (?)

...rc/main/java/com/aliyun/ccpcredentials/Client.java
100% <0%> (ø)
20% <0%> (?)

Continue to review full report at Codecov.

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


Add ioBroker.nuki2 to latest repository

I have reworked the existing ioBroker.nuki adapter and optimized the code.
Furthermore, I have added the following features:

using both Bridge API and Web API (current adapter only uses bridge API)
support for multiple bridges
support for discovery within admin panel
additional states for bridges and better separation between software / hardware bridge

retrieve the basic and advanced configuration from the lock
retrieve all users having access to the lock

added Web Interface to view logs

The PR into the ioBroker.nuki adapter has been rejected by the developer (see https://github.com/smaragdschlange/ioBroker.nuki/pull/11#issuecomment-456061232) because my changes have been quite significant and the developer wants to keep the adapter simple and be able to maintain it.


Updated the RxNetty based version of HystrixMetricsStreamHandler

I updated the RxNetty based Hystrix Metrics Stream to a newer version of RxNetty that it could work with Karyon2.

NetflixOSS » Hystrix » Hystrix-pull-requests #96 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » Hystrix » Hystrix-pull-requests #97 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » Hystrix » Hystrix-pull-requests #98 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » Hystrix » Hystrix-pull-requests #99 SUCCESS
This pull request looks good

Thanks @schmitch , merging


Interactively create VM on openstack cloud

This PR has:

[ ] Appropriate testing (molecule, python unit tests)
[ ] Appropriate documentation (README in the role, main README is up-to-date)

/test all

This is something we probably want integrated in the 01-infra.yml playbook... Therefore, would it be possible to get that as ansible? Basically:

getting the VM (maybe using the openstack ansible module, though... it may lag compared to the actual API, probably better to get it as shell/command)
parsing the outputs (you can format them as json, so it's easy to do in ansible)
injecting the node in the inventory

Doing so, we'd be able to use that same unique entry point, while converging technologies..
Also: please, ensure you're up-to-date against main when submitting PR, things are moving fast, and you may be missing some of the latest corrections in your local code.
EDIT: if you want to get user inputs within ansible, there's https://docs.ansible.com/ansible/2.9/user_guide/playbooks_prompts.html available :)

Thanks for the feedback. I'll take a look at ./ci_framework/playbooks/01-bootstrap.yml (guess that was your intention mentioning 01-infra.yml)

up-to-date against main when submitting PR, things are moving fast, and you may be missing some of the latest corrections in your local code.

I have rebased on top of main this afternoon (in vain), but will try again now. Thanks!

Hi @dsariel , this is stale for so long, what's the actual status of this PR?

PR is stalled - closing. Feel free to re-open it with an update if needed.
Note that we're getting out of the "nested virt" scenario - and someone should be working on porting that non-nested on standard openstack ("standard" compared to CI).


Add annotation mappings to DwC fields

Some valuable additional data in annotations can be added to our DwC archives (for GBIF and other DwCA partners).
Alive or Dead -> Vitality
Flowers and Fruits -> reproductiveCondition
Evidence of Presence -> dynamicProperties
Of these, "Alive or Dead" has particular urgency and relevance for partners due to monitoring dead birds for possible bird flu.
See also this forum thread.

I wonder if it would make sense to also include
Flowers and Fruits -> lifeStage
GBIF currently does not provide API search options for reproductiveCondition and would have to implement this, however, it is possible to search on lifeStage and both Flowering and Fruiting are controlled values in the vocabulary server.


Add rocky Dockerfiles and refine docker documentation

Signed-off-by: Alessandro Bellina<EMAIL_ADDRESS>This PR adds Rocky Linux 8 example dockerfiles for UCX. It uses the rdma-core from the distribution, and I tested that this worked fine with ucx_perftest with RoCE and CUDA/Host memory between two hosts with Mellanox nics.
I updated the docker run example command as it was missing ipc/pid flags so that we could use docker containers to communicate between two GPUs in the same host.
I changed the CUDA version picked here for all images to 11.5.1 so all images match.

May I ask if we would like to have the update to 22.08 too?

I think that would be fine, if reviewers are ok with it. The target branch could be changed to 22.08. @jlowe @sameerz thoughts?

22.08 is fine with me since it's just doc changes and samples.

I am ok putting this in 22.08

build