Adding freezeOnBlur for android and iOS

Solves this: https://github.com/okwasniewski/react-native-bottom-tabs/issues/71
Adding freezeOnBlur property.

Hey @okwasniewski,
I've implemented the freezeOnBlur property, following the same approach as in the JS bottom tabs. I've tested it on Android, both with enableFreeze() globally and by overriding it through options for individual tabs. Currently, I’m testing this on iOS to ensure everything works smoothly there as well.
Meanwhile, feel free to review the PR when you have a chance.
Thanks!

I got instant crash on new arch when going into the example

@okwasniewski Fixed the iOS crash and tested it on Old and New arch for both platforms. Seems to be working fine now with react-native-screens enabled and disabled.

Any updates on this PR? :)

Hi @Nodonisko
Actually I am not available in past few weeks.
Currently I am working on benchmarking native bottom tabs with JS one. Will pick this PR after that.

Merged in #207 thanks @shubhamguptadream11


App is no longer working on launch

I tried restarting my computer and deleting and reinstalling the app, but it isn't functioning for me anymore. Still experiencing the scroll acceleration :/ Not sure if anyone else is having this issue.

This started with the new MacOS version 13.2.1 (22D68).

A fix for anyone experiencing this: Run xattr -d com.apple.quarantine DiscreteScroll.app in the terminal.
Works on MacOS 14.2 for me.

Please see #25, #40, and the instructions I have recently added to the README.


Make it work with the current version of Elm

With those changes, elm-audio works with version 0.15.

@jcollard
Could you please update the version number and tag it so it is installable with the package manager?
https://github.com/elm-lang/elm-package/blob/master/README.md


Optional function properties result in errors if they are defined in an object

Summary

SDK Version: 3.3.37
Expected behavior: An object with a function property should be valid instance of an interface where the function property is optional
Actual behavior:  The object is not a valid member

Code occuring the bug
import TSON from "typescript-json"

interface Foo {
	bar: number;
	baz?: (quz: number) => number;
}

function id(i: number): number {
	return i;
}

console.log(TSON.is<Foo>({ bar: 2, baz: id }))
console.log(TSON.validate<Foo>({ bar: 2, baz: id }))
console.log(TSON.assert<Foo>({ bar: 2, baz: id }))

console.log(TSON.is<Foo>({ bar: 2 }))
console.log(TSON.validate<Foo>({ bar: 2 }))
console.log(TSON.assert<Foo>({ bar: 2 }))

interface Date {
    getVarDate: () => VarDate;
}

This problem is caused by Date type bug of TypeScript.
As you can see from the above code, TypeScript has defined the getVarDate member that never exists on the Date class instance. To avoid such TypeScript's own bug, I supported the functional: false option, but the option is causing endless bugs. I updated a new version v3.3.38 to avoiding this issue's bug, but another bug can be occurred continuously.
Therefore, avoid defining functional property in object type until #372 to be published.
After the #372 patch, I'll erase the functional: false option.

For a fundamental solution, wrote an issue on the TypeScript repo:
https://github.com/microsoft/TypeScript/issues/51636


Add col('w0') and col('w$') to get horizontal scroll offset

Is your feature request about something that is currently impossible or hard to do? Please describe the problem.
I want to retrieve the horizontal scroll offset, like line('w0') and line('w$') does for vertical offset.
Describe the solution you'd like
Add col('w0') and col('w$')
Describe alternatives you've considered
None
Additional context
None

There is the "leftcol" item returned by winsaveview().  Is that what you need?

Not exactly :/ I'm trying to find the screen column of the cursor, with or without 'wrap'. See https://github.com/romgrk/nvim-treesitter-context/pull/12 for more details on the underlying issue.


Viva Insights Add-in Error

I find Viva Insights and the ability to easily delay delivery in outlook using this add-in incredibly helpful. The problem is, I keep getting an "Add-in Error" that says "sorry, we couldn't load the add-in because Internet Explorer is disabled. Click "see Details" for more information." Our IT dept has fixed this a few times, but each time my computer restarts, it requires someone from IT to enable Internet Explorer again. I am not enabled to do this myself. Now our IT dept says they are not allowed to enable IE since it has been retired. Can Microsoft Viva fix this? It seems odd to link Viva with a tool that has been retired by the company. Does anyone have a suggested fix?

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Clear Votes button

@felipedelfim could you explain why do you think this is important?

@glauberramos I know this is old, but I can speak to it. To maintain consistency, and aid in following up on items we have selected to monitor and track during retro sessions, we tend to use our funretro URL as long as it is available and keep "top voted" items in a special column. We want to be able to remove votes from the board so that items can be reconsidered without having to rely on each team member to remove their vote after the retrospective session has concluded.


Support to pull container images automatically

@fike Gofn already pull images but need to support authentication to pull private images https://github.com/gofn/gofn/issues/121

closing because duplicated


Add missing comma between references (1.0.2)

Pushed. Thanks. Anyone care to review the changes for 1.1.0 and master?


Example usage controllers

This PR is to demonstrate how to use terrajet controller and terraformed interface methods generation.

Closing in favor of #7


autoStartup attribute of KafkaListener only exists in version 2.2, how do we use this for 2.1x version?

I am looking for ways to not initialise Kafka when I  start spring application.
So I find that autoStartup attribute can help me on this for the doc, https://docs.spring.io/spring-kafka/reference/htmlsingle/#kafkalistener-lifecycle
However this attribute is only introduced for 2.2 version. First I am wondering why the document already said that and current stable release is 2.1.x?
Second, how can we control to not to initialise Kafka when we start Spring application?

Please don't use GitHub to ask questions.
For earlier versions, set the property on the container factory. The 2.2 Javadoc clearly says that the annotation property overrides the factory property.


Filter returned users from anvil.users.list()

We need the ability to filter anvil.users.list() by the document properties. At the moment there's no way to specify options when querying the User collection: /routes/rest/v1/users.js:35.
Specifically we want to be able to:

Filter by User ID.
(Potentially) filter by other properties on the document.
Select only certain fields to be returned.

This will help us reduce overhead because we won't need to query the entire user collection just to pull out a handful of documents.

To expand on Josh's comments:
anvil.users.list() is a function in connect-nodejs, to allow options to be passed in to the REST API we would need to 1) define a consistent way of passing options 2) define which options are allowed 3) figure out how to best do the filtering

For filtering results, URL query parameters should do the job well

My thoughts on filtering options, which for the moment I'll only comment on for the route GET /v1/users:

Being able to filter by a range of user IDs would be very useful
Specifying the max number of documents to be returned - at the moment there is a default 'size' set in modinha-redis: https://github.com/anvilresearch/modinha-redis/blob/master/lib/RedisDocument.js#L41 and no option to change this.
Filtering by specific document fields might be more complex and is something the client could do, so unless there's an all-encompassing solution this could be split into a separate ticket

Passing query parameters directly through as the options in User.list() could be a quick way to accomplish specifying no. of documents, would it also work for specifying a range?

I've got code working to specify the no of documents here:
https://github.com/hedleysmith/connect/commits/user-endpoint-options
https://github.com/hedleysmith/connect-nodejs/tree/user-endpoint-options
Could add PRs if this seems like a sensible way to go, or could figure out more on the PRs first?

Let me give a little background on this subject while we're thinking it through.
The idea when we started building Anvil Connect was that user data would be limited in scope to identity-related attributes and leave domain-specific profile data and ad hoc querying to a separate microservice. There are a number of reasons this seemed like the way to go at the time.
Given that constraint, there would be no need for the general queryability offered by SQL or Mongo-style backends. We wanted to keep this light, fast, close to the metal. We expected if we needed more sophisticated indexing we're use something like ElasticSearch. The indexing currently done in Redis is limited to the simple lookups needed by program logic, and unfortunately there isn't a great way to scan across the records in a map-reduce kind of way.
After getting some real world experience and feedback from other users, we're changing our thinking on this. For many Anvil Connect users, there are domain-specific user attributes that could end up playing a role in access control (apologies for the pun, I couldn't resist) and with a very large number user accounts, "search results" can be useful. If we're going to allow for extensible user schemas, it only makes sense to have more flexible querying.
These things are being taken into careful consideration for the next generation of Anvil Connect. In the mean time...
To be pedantic, it's not quite possible to filter on a range of user IDs, because being UUIDs they are not sequential and at any rate I'm not sure Redis hashes are ordered by field. Requesting multiple users if you already have all the IDs is feasible. IIRC, User.get() can already take an array of IDs at an argument. Under the hood that method uses the Redis HMGET command.
Selecting specific fields only is certainly possible as well. There's a select option that can be passed to User.list() or User.get.
The only thing stopping us from a "multiget" of users, attribute selection, paging, and controlling the size of the result set via the API is mapping request params to options in the User method calls.
@hedleysmith It's imperative that we restrict which params can be used for options for security purposes. There are a few options that are really intended for internal use only.
Glad to pair on this with anyone that wants to put some effort into fleshing out this part of the API, and look forward to reviewing PRs. Thanks in advance.

Hey Cristian,
Thanks for all the background info on this, very useful to understand. Also good to hear about the plans for the next iteration of Anvil Connect relating to these ideas.
Seems like this is all technically possible and that the underlying functionality in Redis / Modinha will already support what we want to achieve.
Yes lets set up a time to talk this through, I'll ping you on Gitter to figure out when would be a good time.
Just to recap, mainly for my own benefit, I think the main requirements and questions are:

Specify multiple users to return, e.g GET /users/:id,:id,:id...
Size of returned user list, e.g GET /users?size=500
Select specific fields only, e.g GET /users?fields=telephone,givenname,familyname... (note: would using custom scopes instead of be a more sane approach to this, or could both be useful?)

Confirm the best API design for these updates (this could be useful for the next iteration of Anvil Connect as well?)
Figure out how we can safely allow these request parameters to be passed through (I'm guessing storing a list of acceptable parameters and ignoring everything else would make sense, and making sure we also protect for XSS attacks)

:+1:


v2.6.4-rc3 release

Description
v2.6.4-rc3 release
Release Note
v2.6.4-rc3 has a felix fix for "liveness" checking: https://github.com/projectcalico/felix/pull/1662

All the versions look correct to me.


Modularize

The end goal is to split the library up into smaller modules with consistent interfaces, so we can isolate and better reason about interactions. This PR just moves lines of code into different files, without changing any logic, but it starts us down that path.
Maybe something like this?
├── main
├── lib
├── handlers
│   ├── openid_provider
│   └── website
└── providers
    ├── gmail
    └── smtp

I'd like to design the providers such that you can interrogate them, and they can respond with whether or not they can handle a given email address. E.g<EMAIL_ADDRESS>would be true. Then we just just put them in priority order and use the first to say "yes."

Hmm, not sure this is the right way to split up the code. I think it would be better to start putting, say, the storage code in a separate module, so that most of the code doesn't have to know about Redis. Similarly, there could be a token module that can take care of the JWS creation/validation, which can also abstract away the crypto library/algorithms used.
Also, the code that's there is not just gmail; it supports hotmail.com just fine provided you provide configuration for a live.com-authorized application.
Not sure yet if the direction you propose for can_auth() makes sense to me; I'm wondering how it can intersect with the way at least the famous IdPs get configured. It probably still does make sense to extract the two different authentication flows into separate modules.
Another more useful abstraction would probably be to have a kind of URL builder utility method or class.

putting, say, the storage code in a separate module, so that most of the code doesn't have to know about Redis.

Yes, I want that too :)

there could be a token module that can take care of the JWS creation/validation, which can also abstract away the crypto library/algorithms used.

And that!

the code that's there is not just gmail; it supports hotmail.com just fine

We may be able to extend a generic OAuth2 client to support Gmail, but we will need Gmail-specific logic on day one to handle Gmail's +-addressing and .-insensitivity, since Gmail will only return the canonical address from its federated endpoints, but the user may have entered a custom . pattern or subaddress on a specific RP. Also, it has to handle the interchangeability of gmail.com and googlemail.com.
...so we need some kind of isolated place to put that kind of stuff.
Lastly, we may yet determine a reliable way to detect Google Apps for your Domain accounts, which may require DNS probes, etc. that would be completely inapplicable to other providers.

Not sure yet if the direction you propose for can_auth() makes sense to me; I'm wondering how it can intersect with the way at least the famous IdPs get configured.

I believe we should eventually alter the configuration to work per-provider/protocol, not per domain, since a single provider may be able to handle many domains, some of which may only be discoverable at runtime. I'm imagining the configuration calling some kind of constructor that then returns a struct with can_auth(), do_auth(), etc. on it. So you might have something like let providers = vec![gmail::new(API_KEY, API_SECRET), mslive::new(...), mailinator::new(), smtp::new(...)], and could re-order, omit, or swap out providers as desired.

So do you want to take a whack at trying things like extracting the store and/or token code, or shall I see what happens? Your current attempt at modularizing seems a bit random to me. I'd prefer to see how it plays out if the main flow is more concise because helpers are factored out.
In general, it seems like I'm less a fan of spreading code out over multiple files than you. In tightly coupled code, it seems to me that having to switch between files is just harder than keeping the code together; and this is, as I experience it, a very large file.

It's a bit random, yes. Trying to just isolate things along function lines first, and then pull out commonalities. We're on different timezones again, so we could alternate on pushing to a branch?

As to the one-big-file notion, I'm a huge fan of deliberate separation of concerns. We could merge everything back into a single big file by using inline mod foo { ... } statements, but I find separate files easier for focusing attention and preserving encapsulation.

I've pushed a bunch of stuff that should make things more modular (cribbing your nice router!() macro use and fixing clippy lints in the process, with your name on it). Let me  know what you think. I'm happy to rebase your further changes if that makes sense.

Closing this; no longer useful.


Incompatible with latest elm-css

We would like to use this datepicker but we are using elm-css 12. This lib uses 8.
Please consider upgrading elm-css. Or maybe not using elm-css so there are no compatibility issues with elm-css in the apps.

I'm actually thinking of splitting the elm-css code into separate package, so this package doesn't have direct dependency on elm-css. I'm probably gonna do some experiment with this idea soon.

I just released version 6.0.0 that doesn't have a direct dependency to elm-css anymore. Let me know if the new version will work for you or if you have any other concern. In a meantime, I will close this issue as solved.


When building a DC image, the network fails

Operating System Version:macOS Big Sur
Deploying via (VirtualBox/VMWare/AWS/Azure/ESXi):VMWare
Vagrant Version (if applicable): Vagrant 2.2.19

Please verify that you are building from an updated Master branch before filing an issue.
Description of the issue:
When building a DC image, the network fails
Link to Gist Containing Build Logs:
vagrant up dc
Bringing machine 'dc' up with 'vmware_desktop' provider...
==> dc: Cloning VMware VM: 'detectionlab/win2016'. This can take some time...
==> dc: Checking if box 'detectionlab/win2016' version '1.8' is up to date...
==> dc: Verifying vmnet devices are healthy...
==> dc: Preparing network adapters...
WARNING: The VMX file for this box contains a setting that is automatically overwritten by Vagrant
WARNING: when started. Vagrant will stop overwriting this setting in an upcoming release which may
WARNING: prevent proper networking setup. Below is the detected VMX setting:
WARNING:
WARNING:   ethernet0.pcislotnumber = "33"
WARNING:
WARNING: If networking fails to properly configure, it may require this VMX setting. It can be manually
WARNING: applied via the Vagrantfile:
WARNING:
WARNING:   Vagrant.configure(2) do |config|
WARNING:     config.vm.provider :vmware_desktop do |vmware|
WARNING:       vmware.vmx["ethernet0.pcislotnumber"] = "33"
WARNING:     end
WARNING:   end
WARNING:
WARNING: For more information: https://www.vagrantup.com/docs/vmware/boxes.html#vmx-allowlisting
==> dc: Fixed port collision for 22 => 2222. Now on port 2200.
==> dc: Starting the VMware VM...
==> dc: Waiting for the VM to receive an address...
==> dc: Forwarding ports...
    dc: -- 5985 => 55985
    dc: -- 5986 => 55986
    dc: -- 22 => 2200
==> dc: Waiting for machine to boot. This may take a few minutes...
    dc: WinRM address: <IP_ADDRESS>:55985
    dc: WinRM username: vagrant
    dc: WinRM execution_time_limit: PT2H
    dc: WinRM transport: plaintext
==> dc: Machine booted and ready!
==> dc: Setting hostname...
==> dc: Waiting for machine to reboot...
==> dc: Configuring network adapters within the VM...
==> dc: Configuring secondary network adapters through VMware
==> dc: on Windows is not yet supported. You will need to manually
==> dc: configure the network adapter.
==> dc: Configuring proxy environment variables...
==> dc: Enabling and configuring shared folders...
    dc: -- /Users/jk/Desktop/DetectionLab/Vagrant: /vagrant
==> dc: Running provisioner: shell...
    dc: Running: scripts/fix-second-network.ps1 as C:\tmp\vagrant-shell.ps1
    dc: [01:54] Running fix-second-network.ps1...
    dc: [01:54] No VirtIO adapters, moving on...
    dc: [01:54]
    dc: Setting IP address and DNS information for the Ethernet1 interface
    dc: If this step times out, it's because vagrant is connecting to the VM on the wrong interface
    dc: See https://github.com/clong/DetectionLab/issues/114 for more information
    dc: [01:54] Set IP address to <IP_ADDRESS> of interface Ethernet1
    dc:
    dc: [01:54] Set DNS server address to <IP_ADDRESS> of interface Ethernet1
    dc:
==> dc: Running provisioner: shell...
    dc: Running: scripts/provision.ps1 as C:\tmp\vagrant-shell.ps1
    dc: [01:55] Setting timezone to UTC...
    dc: [01:55] Checking if Windows evaluation is expiring soon or expired...
    dc: [01:55] 10 days remaining before expiration
    dc: [01:55] Less than 30 days remaining before Windows expiration. Attempting to rearm...
    dc: Microsoft (R) Windows Script Host Version 5.812
    dc: Copyright (C) Microsoft Corporation. All rights reserved.
    dc:
    dc: Activating Windows(R), ServerStandardEval edition (9dfa8ec0-7665-4b9d-b2cb-bfc2dc37c9f4) ...
    dc: Product activated successfully.
    dc:
    dc: [01:55] Disabling the Invoke-WebRequest download progress bar globally for speed improvements.
    dc: [01:55] See https://github.com/PowerShell/PowerShell/issues/2138 for more info
    dc: [01:55] Lowering the interface metric (increasing priority) for the interface with the 192.168.56.x address
    dc:
    dc: ifIndex InterfaceAlias                  AddressFamily NlMtu(Bytes) InterfaceMetric Dhcp     Connec
    dc:                                                                                tionSt
    dc:                                                                                ate
    dc: ------- --------------                  ------------- ------------ --------------- ----     ------
    dc: 4       isatap.{0A00358B-4710-411A-9... IPv6                  1280              25 Enabled  Con...
    dc: 5       Ethernet0 2                     IPv6                  1500              25 Enabled  Con...
    dc: 7       Local Area Connection* 3        IPv6                  1280              75 Enabled  Con...
    dc: 6       isatap.localdomain              IPv6                  1280              25 Enabled  Con...
    dc: 2       Ethernet1                       IPv6                  1500              15 Enabled  Con...
    dc: 1       Loopback Pseudo-Interface 1     IPv6<PHONE_NUMBER>              75 Disabled Con...
    dc: 5       Ethernet0 2                     IPv4                  1500              25 Enabled  Con...
    dc: 2       Ethernet1                       IPv4                  1500              15 Disabled Con...
    dc: 1       Loopback Pseudo-Interface 1     IPv4<PHONE_NUMBER>              75 Disabled Con...
    dc: [01:55] Unable to connect to ping.detectionlab.network
    dc: The remote name could not be resolved: 'ping.detectionlab.network'
    dc: [01:55] Disabling IPv6 on all network adatpers...
    dc:
    dc: Caption              : MSFT_NetAdapterBindingSettingData 'Intel(R) PRO/1000 MT Network Connection'
    dc: Description          : Internet Protocol Version 6 (TCP/IPv6)
    dc: ElementName          : ms_tcpip6
    dc: InstanceID           : {0A00358B-4710-411A-9281-041C2D3571D4}::ms_tcpip6
    dc: InterfaceDescription : Intel(R) PRO/1000 MT Network Connection
    dc: Name                 : Ethernet1
    dc: Source               : 1
    dc: SystemName           : dc
    dc: BindName             : Tcpip6
    dc: Characteristics      : 132
    dc: ComponentClassGuid   : {4D36E975-E325-11CE-BFC1-08002BE10318}
    dc: ComponentClassName   : Transport
    dc: ComponentID          : ms_tcpip6
    dc: DisplayName          : Internet Protocol Version 6 (TCP/IPv6)
    dc: Enabled              : False
    dc: PSComputerName       :
    dc: ifAlias              : Ethernet1
    dc: InterfaceAlias       : Ethernet1
    dc: ifDesc               : Intel(R) PRO/1000 MT Network Connection
    dc:
    dc:
    dc: Caption              : MSFT_NetAdapterBindingSettingData 'Intel(R) PRO/1000 MT Network Connection
    dc:                        #2'
    dc: Description          : Internet Protocol Version 6 (TCP/IPv6)
    dc: ElementName          : ms_tcpip6
    dc: InstanceID           : {D64464EB-388C-4532-8EF3-5DBC1ED28DAD}::ms_tcpip6
    dc: InterfaceDescription : Intel(R) PRO/1000 MT Network Connection #2
    dc: Name                 : Ethernet0 2
    dc: Source               : 1
    dc: SystemName           : dc
    dc: BindName             : Tcpip6
    dc: Characteristics      : 132
    dc: ComponentClassGuid   : {4D36E975-E325-11CE-BFC1-08002BE10318}
    dc: ComponentClassName   : Transport
    dc: ComponentID          : ms_tcpip6
    dc: DisplayName          : Internet Protocol Version 6 (TCP/IPv6)
    dc: Enabled              : False
    dc: PSComputerName       :
    dc: ifAlias              : Ethernet0 2
    dc: InterfaceAlias       : Ethernet0 2
    dc: ifDesc               : Intel(R) PRO/1000 MT Network Connection #2
    dc:
    dc: The operation completed successfully.
    dc:
    dc: [01:55] Current domain is set to 'workgroup'. Time to join the domain!
    dc: [01:55] Installing bginfo...
    dc: [01:55] Installing BGInfo...
    dc:
    dc: PSPath            : Microsoft.PowerShell.Core\FileSystem::C:\Program Files\sysinternals
    dc: PSParentPath      : Microsoft.PowerShell.Core\FileSystem::C:\Program Files
    dc: PSChildName       : sysinternals
    dc: PSDrive           : C
    dc: PSProvider        : Microsoft.PowerShell.Core\FileSystem
    dc: PSIsContainer     : True
    dc: Name              : sysinternals
    dc: Parent            : Program Files
    dc: Exists            : True
    dc: Root              : C:\
    dc: FullName          : C:\Program Files\sysinternals
    dc: Extension         :
    dc: CreationTime      : 10/3/2022 1:55:43 AM
    dc: CreationTimeUtc   : 10/3/2022 8:55:43 AM
    dc: LastAccessTime    : 10/3/2022 1:55:43 AM
    dc: LastAccessTimeUtc : 10/3/2022 8:55:43 AM
    dc: LastWriteTime     : 10/3/2022 1:55:43 AM
    dc: LastWriteTimeUtc  : 10/3/2022 8:55:43 AM
    dc: Attributes        : Directory
    dc: Mode              : d-----
    dc: BaseName          : sysinternals
    dc: Target            : {}
    dc: LinkType          :
    dc:
    dc: powershell.exe : Exception calling "DownloadFile" with "2" argument(s): "Unable to connect to the remote server"
    dc:     + CategoryInfo          : NotSpecified: (Exception calli... remote server":String) [], RemoteException
    dc:     + FullyQualifiedErrorId : NativeCommandError
    dc: At C:\vagrant\scripts\install-bginfo.ps1:10 char:3
    dc: +   (New-Object Net.WebClient).DownloadFile('http://live.sysinternals.c ...
    dc: +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    dc:     + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    dc:     + FullyQualifiedErrorId : WebException
    dc:
    dc: [01:56] My hostname is DC
    dc: [01:56] Installing RSAT tools
    dc:
    dc: Success       : True
    dc: RestartNeeded : No
    dc: FeatureResult : {Remote Server Administration Tools, Active Directory Administrative Center,
    dc:                 Active Directory module for Windows PowerShell, AD DS and AD LDS Tools...}
    dc: ExitCode      : Success
    dc:
    dc: [01:56] Creating domain controller...
    dc:
    dc: The task has completed successfully.
    dc: See log %windir%\security\logs\scesrv.log for detail info.
    dc: Completed 5 percent (0/18) 	Process Security Policy area
    dc: Completed 22 percent (3/18) 	Process Security Policy area
    dc: Completed 44 percent (7/18) 	Process Security Policy area
    dc: Completed 61 percent (10/18) 	Process Security Policy area
    dc: Completed 77 percent (13/18) 	Process Security Policy area
    dc: Completed 100 percent (18/18) 	Process Security Policy area
    dc:
    dc: The task has completed successfully.
    dc: See log %windir%\security\logs\scesrv.log for detail info.
    dc:
    dc: Success       : True
    dc: RestartNeeded : No
    dc: FeatureResult : {Active Directory Domain Services}
    dc: ExitCode      : Success
    dc:
    dc: WARNING: Windows Server 2016 domain controllers have a default for the security setting named
    dc: "Allow cryptography algorithms compatible with Windows NT 4.0" that prevents weaker cryptography
    dc: algorithms when establishing security channel sessions.
    dc:
    dc:
    dc:
    dc: For more information about this setting, see Knowledge Base article 942564
    dc: (http://go.microsoft.com/fwlink/?LinkId=104751).
    dc:
    dc:
    dc: WARNING: This computer has at least one physical network adapter that does not have static IP
    dc: address(es) assigned to its IP Properties. If both IPv4 and IPv6 are enabled for a network
    dc: adapter, both IPv4 and IPv6 static IP addresses should be assigned to both IPv4 and IPv6
    dc: Properties of the physical network adapter. Such static IP address(es) assignment should be done
    dc: to all the physical network adapters for reliable Domain Name System (DNS) operation.
    dc:
    dc:
    dc: WARNING: A delegation for this DNS server cannot be created because the authoritative parent zone
    dc: cannot be found or it does not run Windows DNS server. If you are integrating with an existing DNS
    dc:  infrastructure, you should manually create a delegation to this DNS server in the parent zone to
    dc: ensure reliable name resolution from outside the domain "windomain.local". Otherwise, no action is
    dc:  required.
    dc:
    dc:
    dc: WARNING: Windows Server 2016 domain controllers have a default for the security setting named
    dc: "Allow cryptography algorithms compatible with Windows NT 4.0" that prevents weaker cryptography
    dc: algorithms when establishing security channel sessions.
    dc:
    dc:
    dc:
    dc: For more information about this setting, see Knowledge Base article 942564
    dc: (http://go.microsoft.com/fwlink/?LinkId=104751).
    dc:
    dc:
    dc: WARNING: This computer has at least one physical network adapter that does not have static IP
    dc: address(es) assigned to its IP Properties. If both IPv4 and IPv6 are enabled for a network
    dc: adapter, both IPv4 and IPv6 static IP addresses should be assigned to both IPv4 and IPv6
    dc: Properties of the physical network adapter. Such static IP address(es) assignment should be done
    dc: to all the physical network adapters for reliable Domain Name System (DNS) operation.
    dc:
    dc:
    dc: WARNING: A delegation for this DNS server cannot be created because the authoritative parent zone
    dc: cannot be found or it does not run Windows DNS server. If you are integrating with an existing DNS
    dc:  infrastructure, you should manually create a delegation to this DNS server in the parent zone to
    dc: ensure reliable name resolution from outside the domain "windomain.local". Otherwise, no action is
    dc:  required.
    dc:
    dc:
    dc:
    dc: Message        : You must restart this computer to complete the operation.
    dc:
    dc: Context        : DCPromo.General.2
    dc: RebootRequired : True
    dc: Status         : Success
    dc:
    dc: [02:02] Setting DNS
    dc:
    dc: __GENUS          : 2
    dc: __CLASS          : __PARAMETERS
    dc: __SUPERCLASS     :
    dc: __DYNASTY        : __PARAMETERS
    dc: __RELPATH        :
    dc: __PROPERTY_COUNT : 1
    dc: __DERIVATION     : {}
    dc: __SERVER         :
    dc: __NAMESPACE      :
    dc: __PATH           :
    dc: ReturnValue      : 0
    dc: PSComputerName   :
    dc:
    dc: [02:02] Setting timezone to UTC
    dc: [02:02] Excluding NAT interface from DNS
    dc: ListenAddresses reset successful.
    dc:
    dc: Command completed successfully.
    dc:
    dc:
    dc:
The following WinRM command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

powershell -ExecutionPolicy Bypass -OutputFormat Text -file "C:\tmp\vagrant-shell.ps1"

Stdout from the command:

[01:55] Setting timezone to UTC...
[01:55] Checking if Windows evaluation is expiring soon or expired...
[01:55] 10 days remaining before expiration
[01:55] Less than 30 days remaining before Windows expiration. Attempting to rearm...
Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.

Activating Windows(R), ServerStandardEval edition (9dfa8ec0-7665-4b9d-b2cb-bfc2dc37c9f4) ...
Product activated successfully.

[01:55] Disabling the Invoke-WebRequest download progress bar globally for speed improvements.
[01:55] See https://github.com/PowerShell/PowerShell/issues/2138 for more info
[01:55] Lowering the interface metric (increasing priority) for the interface with the 192.168.56.x address

ifIndex InterfaceAlias                  AddressFamily NlMtu(Bytes) InterfaceMetric Dhcp     Connec
                                                                                tionSt
                                                                                ate
------- --------------                  ------------- ------------ --------------- ----     ------
4       isatap.{0A00358B-4710-411A-9... IPv6                  1280              25 Enabled  Con...
5       Ethernet0 2                     IPv6                  1500              25 Enabled  Con...
7       Local Area Connection* 3        IPv6                  1280              75 Enabled  Con...
6       isatap.localdomain              IPv6                  1280              25 Enabled  Con...
2       Ethernet1                       IPv6                  1500              15 Enabled  Con...
1       Loopback Pseudo-Interface 1     IPv6<PHONE_NUMBER>              75 Disabled Con...
5       Ethernet0 2                     IPv4                  1500              25 Enabled  Con...
2       Ethernet1                       IPv4                  1500              15 Disabled Con...
1       Loopback Pseudo-Interface 1     IPv4<PHONE_NUMBER>              75 Disabled Con...
[01:55] Unable to connect to ping.detectionlab.network
The remote name could not be resolved: 'ping.detectionlab.network'
[01:55] Disabling IPv6 on all network adatpers...

 Time to join the domain!
[01:55] Installing bginfo...
[01:55] Installing BGInfo...

ExitCode      : Success

[01:56] Creating domain controller...

The task has completed successfully.
See log %windir%\security\logs\scesrv.log for detail info.
Completed 5 percent (0/18) 	Process Security Policy area
Completed 22 percent (3/18) 	Process Security Policy area
Completed 44 percent (7/18) 	Process Security Policy area
Completed 61 percent (10/18) 	Process Security Policy area
Completed 77 percent (13/18) 	Process Security Policy area
Completed 100 percent (18/18) 	Process Security Policy area

The task has completed successfully.
See log %windir%\security\logs\scesrv.log for detail info.

Success       : True
RestartNeeded : No
FeatureResult : {Active Directory Domain Services}
ExitCode      : Success

WARNING: Windows Server 2016 domain controllers have a default for the security setting named
"Allow cryptography algorithms compatible with Windows NT 4.0" that prevents weaker cryptography
algorithms when establishing security channel sessions.

For more information about this setting, see Knowledge Base article 942564
(http://go.microsoft.com/fwlink/?LinkId=104751).

WARNING: This computer has at least one physical network adapter that does not have static IP
address(es) assigned to its IP Properties. If both IPv4 and IPv6 are enabled for a network
adapter, both IPv4 and IPv6 static IP addresses should be assigned to both IPv4 and IPv6
Properties of the physical network adapter. Such static IP address(es) assignment should be done
to all the physical network adapters for reliable Domain Name System (DNS) operation.

WARNING: A delegation for this DNS server cannot be created because the authoritative parent zone
cannot be found or it does not run Windows DNS server. If you are integrating with an existing DNS
 infrastructure, you should manually create a delegation to this DNS server in the parent zone to
ensure reliable name resolution from outside the domain "windomain.local". Otherwise, no action is
 required.

WARNING: Windows Server 2016 domain controllers have a default for the security setting named
"Allow cryptography algorithms compatible with Windows NT 4.0" that prevents weaker cryptography
algorithms when establishing security channel sessions.

For more information about this setting, see Knowledge Base article 942564
(http://go.microsoft.com/fwlink/?LinkId=104751).

WARNING: This computer has at least one physical network adapter that does not have static IP
address(es) assigned to its IP Properties. If both IPv4 and IPv6 are enabled for a network
adapter, both IPv4 and IPv6 static IP addresses should be assigned to both IPv4 and IPv6
Properties of the physical network adapter. Such static IP address(es) assignment should be done
to all the physical network adapters for reliable Domain Name System (DNS) operation.

WARNING: A delegation for this DNS server cannot be created because the authoritative parent zone
cannot be found or it does not run Windows DNS server. If you are integrating with an existing DNS
 infrastructure, you should manually create a delegation to this DNS server in the parent zone to
ensure reliable name resolution from outside the domain "windomain.local". Otherwise, no action is
 required.

Message        : You must restart this computer to complete the operation.

Context        : DCPromo.General.2
RebootRequired : True
Status         : Success

[02:02] Setting DNS

__GENUS          : 2
__CLASS          : __PARAMETERS
__SUPERCLASS     :
__DYNASTY        : __PARAMETERS
__RELPATH        :
__PROPERTY_COUNT : 1
__DERIVATION     : {}
__SERVER         :
__NAMESPACE      :
__PATH           :
ReturnValue      : 0
PSComputerName   :

[02:02] Setting timezone to UTC
[02:02] Excluding NAT interface from DNS
ListenAddresses reset successful.

Command completed successfully.

Stderr from the command:

powershell.exe : Exception calling "DownloadFile" with "2" argument(s): "Unable to connect to the remote server"
    + CategoryInfo          : NotSpecified: (Exception calli... remote server":String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
At C:\vagrant\scripts\install-bginfo.ps1:10 char:3
+   (New-Object Net.WebClient).DownloadFile('http://live.sysinternals.c ...
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : WebException

vagrant reload dc --provision
==> dc: Attempting graceful shutdown of VM...
==> dc: Checking if box 'detectionlab/win2016' version '1.8' is up to date...
==> dc: Verifying vmnet devices are healthy...
==> dc: Preparing network adapters...
==> dc: Fixed port collision for 22 => 2222. Now on port 2200.
==> dc: Starting the VMware VM...
==> dc: Waiting for the VM to receive an address...
==> dc: Forwarding ports...
    dc: -- 5985 => 55985
    dc: -- 5986 => 55986
    dc: -- 22 => 2200
==> dc: Waiting for machine to boot. This may take a few minutes...
    dc: WinRM address: <IP_ADDRESS>:55985
    dc: WinRM username: vagrant
    dc: WinRM execution_time_limit: PT2H
    dc: WinRM transport: plaintext
==> dc: Machine booted and ready!
==> dc: Setting hostname...
==> dc: Configuring network adapters within the VM...
==> dc: Configuring secondary network adapters through VMware
==> dc: on Windows is not yet supported. You will need to manually
==> dc: configure the network adapter.
==> dc: Configuring proxy environment variables...
==> dc: Enabling and configuring shared folders...
    dc: -- /Users/jk/Desktop/DetectionLab/Vagrant: /vagrant
==> dc: Running provisioner: shell...
    dc: Running: scripts/fix-second-network.ps1 as C:\tmp\vagrant-shell.ps1
    dc: [09:12] Running fix-second-network.ps1...
    dc: [09:12] No VirtIO adapters, moving on...
    dc: [09:12]
    dc: Setting IP address and DNS information for the Ethernet1 interface
    dc: If this step times out, it's because vagrant is connecting to the VM on the wrong interface
    dc: See https://github.com/clong/DetectionLab/issues/114 for more information
An error occurred executing a remote WinRM command.

Shell: Elevated
Command: powershell -ExecutionPolicy Bypass -OutputFormat Text -file "C:\tmp\vagrant-shell.ps1" -ip <IP_ADDRESS> -dns <IP_ADDRESS> -gateway <IP_ADDRESS>
Message: Bad HTTP response returned from server. Body(if present): (502).

Likely caused by this change, I've since reverted it: https://github.com/clong/DetectionLab/commit/f919a02133f586cc276f491b8f2931cd9f89d68d


Unable to get highlighting for tsx in fenced code blocks

Describe the bug
I've been trying to get highlighting for tsx in fenced code block to work, but I'm failing even-though I have the parser installed.
Code example
const foo = "foo"

<Test value={foo}>
</Test>

Add the above snippet in a fenced code block with ts vs tsx.
Expected behavior
Both the fenced code blocks should be highlighted.
Actual behavior
Only the ts block is highlighted.

This can not be solved here, but only with the editor you are using. Are you using neovim? If so then you can make a PR to nvim-treesitter adding the alias here: https://github.com/nvim-treesitter/nvim-treesitter/blob/680807fa6a482c639119098bc48ca3831c66db13/lua/nvim-treesitter/query_predicates.lua#L10-L16

This can not be solved here, but only with the editor you are using. Are you using neovim? If so then you can make a PR to nvim-treesitter adding the alias here: https://github.com/nvim-treesitter/nvim-treesitter/blob/680807fa6a482c639119098bc48ca3831c66db13/lua/nvim-treesitter/query_predicates.lua#L10-L16

Awesome. Thank you for pointing me in the right direction. I'll do that. 👌

@MDeiml I've been looking into this further and your suggestion does, sadly, not work. Since js, jsx, and tsx all match a filetype by vim.filetype.match used in https://github.com/nvim-treesitter/nvim-treesitter/blob/680807fa6a482c639119098bc48ca3831c66db13/lua/nvim-treesitter/query_predicates.lua#L18C1-L21.
It looks like nvim-treesitter properly sets javascriptreact and typescriptreact as the filetypes, but the highlighting is still missing in the fenced markdown code blocks. If you have any further input, that would be greatly appreciated.

Hm, I can only speculate then. I guess you checked, that the typescript parser is installed? Does it work on tsx files?
Also did you check the output of the  treesitter-playground plugin? Maybe the typescript is properly parsed (so playground would show nodes) but not highlighted for some reason.

@MDeiml Yeah, both jsx and tsx files parse and highlights correctly using treesitter.
I've only tried the built-in InspectTree, which correctly sets the lang node, but it's missing any content inside. I can install the playground and see if that provides any further insight.
As far as I can tell, it seems like it's correctly getting the lang key, mapping that to a filetype but then something gets lost.


Add a database migration for the credits field of the organization …

…table
And set the default to 100 credits per org, as per the
design

Pull Request Test Coverage Report for Build 1297

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 65.751%

Totals

Change from base Build 1296:
0.0%

Covered Lines:
5660

Relevant Lines:
8118

💛  - Coveralls


Haas as an obm

This branch has code  that does the following

Implement "node_register" call in recursive HaaS
Sets up Base HaaS as an Obm driver.
"power_cycle" method implemented for nodes in Recursive HaaS
node_discover.py script added to auto-populate nodes from Base haas into recursive HaaS
Documentation describing how to configure and use recursive HaaS

This requires some additional updates and merges. Please re-open when it's ready for review.


Passing message to record malformed event

Issue: https://github.com/cloudevents/sdk-go/issues/964

still testing, but I think the race condition will be fixed by https://github.com/cloudevents/sdk-go/pull/958

please rebase

@duglin Rebase done!

@duglin Resolved conflicts and updated PR. Sneaked one more tiny change in invoker.go.

@duglin test seems flakey. Its passing locally on my machine so probably need a rerun.

rebase again and let's see how it goes...

@duglin done!

I'm hoping https://github.com/cloudevents/sdk-go/pull/970 fixes the errors you're seeing....

I'm confused as to why this is associated with the Observability service

@duglin For logging purpose. Basically I want to get malformed message and log it. If there is better approach i.e. if we can pass error handler as an extra client option, I am ok with that. At the moment, there is no way I can get hold of malformed event so that I can investigate it further.

I shouldn't admit this, but I'm not as up to speed on the SDK as I should be :-)  but I just can't help but wonder why we're not doing something like extending the receiveInvoker struct with some kind of DLQ/handler/fn/thingy. And then also send events to it if the receiverFn returns an error, maybe?
@embano1 @lionelvillard any thoughts on whether extending the Obs. service is the best approach?

Yeah, we should think about how we want to give users an option to consume events/requests throughout the various stages of event handling logic in the SDK. We can log, use callbacks, change signatures, or pass objects instead of nil. So we should discuss this a bit more. Perhaps we also need to distinguish for the implementation/PR(s) between error and success cases.

Doing some digging/learning and I have a few questions for @embano1 and @lionelvillard ...
It appears that people are supposed to setup a ceClient and then call StartReceiver() with the call-back Fn. In StartReceiver() it'll setup a receiveInvoker (https://github.com/cloudevents/sdk-go/blob/main/v2/client/client.go#L206) with all of the various options for processing the incoming event. However, I'm wondering why StarrtReceiver() takes the call-back Fn as a parameter instead of it being one of the ceClient options? Is this because there's an assumption that there can be more than one StartReceiver() running at the same time and each might need a different event processor? This line: https://github.com/cloudevents/sdk-go/blob/main/v2/client/client.go#L202 would seem to indicate "no", it's a singleton.
It's probably not a big deal, I'm just wondering why this one option (the call-back Fn) is special from all of the other ceClient options (like Decorators) and not setup the same way? And, this popped in my head because I was trying to think about how we might want to setup a DLQ - to me a DLQ isn't much different from the call-back Fn so for consistency I thought we should follow the same pattern. But, I'm not sure I'd want to extend the StartReceiver() signature with another (optional) arg.

Or maybe it's special because it's the only required param? I could buy that.
So, either way, what do you guys think about adding a DQL field in receiveInvoker?


Allow to specify the maximum number of file descriptors to close

To avoid leaking of file descriptors to started child processes
we close all the ones we don't want to pass. This works efficiently
for as long as the max. number of file descriptors the process
can have is low, such as 1024. When running the crawler on a Ubuntu
host, this number is 1024 (/proc//limits). When running it inside
a container, the number may for example be 1048576. So, we introduce
a parameter to the start_child function that allows us to artificially
limit that number for a process, like the crawler, that doesn't have so
many file descriptors open. We pass 128, which is sufficiently high.
Signed-off-by: Stefan Berger<EMAIL_ADDRESS>

Codecov Report

Merging #280 into master will decrease coverage by 0.15%.
The diff coverage is 28.57%.

@@            Coverage Diff             @@
##           master     #280      +/-   ##
==========================================
- Coverage   89.39%   89.24%   -0.16%
==========================================
  Files         113      113
  Lines        4226     4229       +3
==========================================
- Hits         3778     3774       -4
- Misses        448      455       +7

Impacted Files
Coverage Δ

...rawler/plugins/systems/fprobe_container_crawler.py
81.98% <ø> (ø)
:arrow_up:

crawler/utils/process_utils.py
30% <28.57%> (-1.58%)
:arrow_down:

crawler/plugins/systems/cpu_container_crawler.py
95.77% <0%> (-2.82%)
:arrow_down:

crawler/utils/dockerutils.py
95.85% <0%> (-0.83%)
:arrow_down:

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 225d270...8fe473e. Read the comment docs.

Fixes #281

Thanks!


eureka incorrect Renews (last min)

I have one registered service and the renews(last min) should be 2 instead of 4 (1 heartbeat per 30 seconds), this will cause the self-preservation feature error if there're more than two services,  is my configuration wrong?
eureka server config:
spring.application.name=versa-eureka
server.port=8761
eureka.client.registerWithEureka=false
eureka.client.fetchRegistry=false

eureka client config:
spring.application.name=versa-backend
server.port=8101
eureka.client.serviceUrl.defaultZone=http://localhost:8761/eureka/

I don't think this is a problem. Less renewals would be.

Actulally the renews(last min) always be 4


View.propTypes has been deprecated

First off, great little library, nice work!
Although today when building to release today, I got the following errors from both iOS and Android logging:
...
ReactNativeJS: undefined is not an object (evaluating 'l.View.propTypes.style')
ReactNativeJS: Module AppRegistry is not a registered callable module (calling runApplication)
ReactNative: ReactInstanceManager.detachViewFromInstance()
ReactNativeJS: Module AppRegistry is not a registered callable module (calling unmountApplicationComponentAtRootTag)

I eventually tracked down the issue to this library using View.propTypes.style, but React Native has changed this recently to "ViewPropTypes".

https://github.com/kiok46/react-native-multi-toggle-switch/pull/2

#2

Merged #2


IE 11 issue, Object doesn't support this action

Hi,
I was testing the oidc-client.js library in IE 11 with authorization code with PKCE and after logging in I get this error. Looks like some missing polyfill?
Everything works fine in other browsers.
TypeError: Object doesn't support this action.

Never mind. My code was using CustomEvents and they are not supported in ie 11. Can be closed


ci: check for KVStore status before running tests

Some of tests are failing using Splunk 9.0.x. It seems that KVStore needs a bit more time to initialize after the restart. Adding corresponding check.

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


Docker no compression

When was this decided? And why?

@floion Yes. We discussed this a couple of times when we acknowledged a problem with deltas (afaik) about which @petrosagg can give more details. As well, now we have enough space for this change and it improves compile time of docker a lot - as the compression step takes ages.

Rebased the README conflict.

@floion There are two issues with UPXing the binary. The first is that binary deltas over compressed streams doesn't produce small deltas, since compressed streams are high entropy and change wildly. This is the minor issue.
The second issue is the big one, and we kinda hit it now with docker 1.10 but we'll hit it a lot more with 1.12. Since the UPX binary needs to decompress in memory, the decompressor initially allocates a big buffer, decompresses in there and then jumps to it. This means that if you have 5 instances of docker running at the same time you'll be consuming 5x the uncompressed size of the binary!. So when a background script does docker ps just to check something it will momentarily request 30MB of RAM. This is even worse with docker 1.12 because it is multi-process and there are utility processes per container.
This is solved by not compressing it because the kernel will mmap() the executable file in memory (which is also reclaimable) and it will share the .text portion for all the instances running on the system. And so you only allocate a fraction of the memory per instance.


Parallel thread fix

Coverage decreased (-0.02%) to 11.35% when pulling a2c2bcc56aa1f891bd7a57b31493b0532dc73a37 on parallel_thread_fix into 2f27158ae476711fff984855ea5799de07c02e4a on master.

The executor in use needs to have shutdown called to clean up the threads.  Otherwise when we instantiate a new service a new thread factory is created therefore new threads are created and the old threads are not interrupted.  So implement Closeable to shutdown the threads.


Tracing into another lambda

I have some code that looks like:
	getAddress := "https://xyz.execute-api.us-east-1.amazonaws.com/metrics"
	// trace request with Xray
	ctx, root := xray.BeginSegment(context.Background(), "fetch another microservice")

	resp, err := ctxhttp.Get(ctx, xray.Client(http.DefaultClient), getAddress)
	if err != nil {
		log.WithField("url", getAddress).WithError(err).Error("failed to fetch")
	}

Though in Service Lens, it doesn't seem able to realise than "xyz" is another AWS microservice (in the same account) that I also want to trace and see inline. What am I missing?

I created a minimal code example here: https://github.com/kaihendry/x-amzn-trace-id to reproduce my problem

If I understand your use case then you want to see Remote node as a microservice? Also, I think as per current scenario you are doing HTTP call from fetch another microservice which is instrumented with X-Ray Go SDK. If downstream service is not instrumented with X-Ray then it would mark this node as Remote and that is the reason you're seeing Remote node. Which downstream service you're calling?

I think my confusion comes by how the x-amzn-trace-id is passed along the microservices. Lets just call them "a" & "b".
IIUC when "a" is invoked, and then calls "b", which responds all the way back down, there are two appended x-amzn-trace-id headers?

Not sure if I understand this correctly, but why would there be two appended headers? Ideally microservice "a" generates and propagates header to downstream service which downstream service "b" uses while making a sampling decision. The important thing to note is microservice "b" should be instrumented with X-Ray SDK.

Two appended headers is what I observed here: https://github.com/kaihendry/sam-header-test


Visual glitches exporting JXL to PNG

Testing around the conversion from JXL to PNG yields wee glitches in the form of wrongly colored pixels and/or wrong columns. See attached converted PNG (*.jxl.png). Unfortunately, GitHub does not seem to support attaching JXL, so I'm attaching the original PNG from which the JXL was encoded.
Original PNG:

PNG ->(gimp) JXL ->(jxlatte) PNG

Please attach the JXL so I can test it. (You can actually attach it, you just have to rename it to something supported like .jpg. Yes really.)

Nice trick, here it is.

Fixed in 5b02554f9ab01134b7a19c1182f81b366fd3bcd1.

Awesome, works perfectly now!


Fix frac-line

For frac-line, use an SVG line in an extra tall span.
I still need to think of a way to adust vertical-separator.

Were the vertical separators disappearing at times? Won't this change to the styling affect the horizontal layout slightly?

Revisiting my response to this comment:

Yes. Issue #970
No. It turns out that vertical-separator lines do nothing to the inter-column spacing of an {array}. In the screen shot below, I've drug part of a no-line array over and overlaid it onto an {array}{c|c}. The columns still align perfectly.

In the code for this PR, it was only necessary to adjust the vertical-separator negative left margin. No action is necessary to further fix the horizontal layout.
I believe that we're good to go.

@ronkok you'll have to merge master into your branch and resolve the conflict.  I can regenerate those screenshots afterwards.

@ronkok thank you for tackling this this issue with the fraction bars disappearing.  I'm going to publish a release over the next couple of days.  With this change I think it's safe to make it a beta release or release candidate.  :)

@kevinbarabash You're very welcome. I certainly think that we've now got something better than when we started. I hope it's enough.


feat: add env to activation table

Not sure about this addition. Would expect it to be a lot smarter but now it just sets simple environment variables.
I would expect it to expand variables if you would do:
[activation.env]
PATH = "bla/bli/blu:$PATH"

@wolfv What do you think? Merge this already (after adding docs) or figuring out a better parsing solution for the variables?

After merging #972 This feature is to simple and will cause confusion

@baszalmstra Do you have some smart ideas on how to easily and in a cross-platform way, add these env vars?
Specifically reusing existing variables:
[activation]
env = { PATH = "$PIXI_PROJECT_ROOT/extra/path:$PATH", MODEL_LOCATION = "$PIXI_PROJECT_ROOT/models"}

One of my ideas would be parsing the strings ourself and use rusts std::env::var(), what do you think about that?

Will have to try it out as they seem to just use the direct naming but they do support taskfiles per OS.

After merging #972 This feature is to simple and will cause confusion

Sometimes you really want some variables per environment.
It can be done with activation script, but I personally don't like having to add 2 extra scripts (.sh and .bat) to the repo just for that. Could also need more scripts in case of multi-environments. It's much nicer to be able to keep that in the pixi.toml file.
I currently use the variables per task but when you have several tasks using the same variable(s), it becomes quite verbose. And you might want a variable to be set without defining a specific task.
I think having the same feature as variable per task but per env would be a nice addition. I also really like that those are default you can overwrite from the shell.

He @beenje, Thanks for the input. I completely agree with you. Still need to get back to this PR to test the above discussed change.


Issue 31

Trying to implement issue 31 ; allowing metacat dataset and rucio dataset to be different, via "custom" per-experiment module; but also allowing them to be the same by having metacat_dataset() call rucio_dataset().   Moved the current code that implements the rucio dataset template into the custom code.

wrong upstream.


tests/sqlparser_common.rs / parse_create_view_with_options gives different results with ClickHouseDialect

When changing the test to include ClickHouseDialect, it fails like so:
---- parse_create_view_with_columns stdout ----
thread 'parse_create_view_with_columns' panicked at src/test_utils.rs:77:21:
assertion `left == right` failed: Parse results with DatabricksDialect are different from ClickHouseDialect
  left: Ok([CreateView { or_replace: false, materialized: false, name: ObjectName([Ident { value: "v", quote_style: None }]), columns: [ViewColumnDef { name: Ident { value: "has", quote_style: None }, data_type: None, options: None }, ViewColumnDef { name: Ident { value: "cols", quote_style: None }, data_type: None, options: None }], query: Query { with: None, body: Select(Select { distinct: None, top: None, projection: [UnnamedExpr(Value(Number("1", false))), UnnamedExpr(Value(Number("2", false)))], into: None, from: [], lateral_views: [], prewhere: None, selection: None, group_by: Expressions([], []), cluster_by: [], distribute_by: [], sort_by: [], having: None, named_window: [], qualify: None, window_before_qualify: false, value_table_mode: None, connect_by: None }), order_by: None, limit: None, limit_by: [], offset: None, fetch: None, locks: [], for_clause: None, settings: None, format_clause: None }, options: None, cluster_by: [], comment: None, with_no_schema_binding: false, if_not_exists: false, temporary: false, to: None }])
 right: Err(ParserError("Expected: a data type name, found: ,"))
stack backtrace:
   0: rust_begin_unwind
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panicking.rs:652:5
   1: core::panicking::panic_fmt
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/panicking.rs:72:14
   2: core::panicking::assert_failed_inner
   3: core::panicking::assert_failed
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/panicking.rs:363:5
   4: sqlparser::test_utils::TestedDialects::one_of_identical_results::{{closure}}
             at ./src/test_utils.rs:77:21
   5: core::iter::adapters::map::map_fold::{{closure}}
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/iter/adapters/map.rs:89:21
   6: <core::slice::iter::Iter<T> as core::iter::traits::iterator::Iterator>::fold
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/slice/iter/macros.rs:230:27
   7: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::fold
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/iter/adapters/map.rs:129:9
   8: sqlparser::test_utils::TestedDialects::one_of_identical_results
             at ./src/test_utils.rs:74:9
   9: sqlparser::test_utils::TestedDialects::parse_sql_statements
             at ./src/test_utils.rs:101:9
  10: sqlparser::test_utils::TestedDialects::one_statement_parses_to
             at ./src/test_utils.rs:132:30
  11: sqlparser::test_utils::TestedDialects::verified_stmt
             at ./src/test_utils.rs:161:9
  12: sqlparser_common::parse_create_view_with_columns
             at ./tests/sqlparser_common.rs:6799:11
  13: sqlparser_common::parse_create_view_with_columns::{{closure}}
             at ./tests/sqlparser_common.rs:6796:36
  14: core::ops::function::FnOnce::call_once
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/ops/function.rs:250:5
  15: core::ops::function::FnOnce::call_once
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/ops/function.rs:250:5

There are two potential issues:

all_dialects doesn't contain the ClickHouse dialect for now
ClickHouse's create view requires the data type after the column name

I think we can add the ClickHouse dialect and fix those test cases. cc @alamb

Ah yeah sorry - this goes with #1447; should have added that context there. I added ClickHouse to all_dialects in that PR and manually excluded it from the one test that failed. I filed this to make sure that doesn't get forgotten.

@joshuawarner32 Great!


[Support] How to completely load a video before auto-playing to avoid buffering

Hi @cookpete , I am new to react and have been trying to solve this issue.
I have a list of video URLs that I want to play sequentially based on user interaction. My application can't afford to buffer so I want to play the video only when it's completely loaded.
Can you please help me in this regard. What props to pass in or how to do this thing.
I also want to look into a solution where I can pre-fetch the next 2 or 3 videos in the sequence, so the transition between video is smooth.

I would like to know if it's possible as well. Thank you.


Font path is wrong in /styles/vendor.css

Current behavior
In the network panel I noticed many 404 errors while loading the robots fonts.
Example of one of the non-face rules:
@font-face {
    font-family: 'Roboto';
    src: url('../../fonts/roboto/Roboto-Thin.eot');
    src: local('Roboto Thin'), local('Roboto-Thin'), url('../fonts/roboto/Roboto-Thin.eot?#iefix') format('embedded-opentype'), url('../fonts/roboto/Roboto-Thin.woff2') format('woff2'), url('../fonts/roboto/Roboto-Thin.woff') format('woff'), url('../fonts/roboto/Roboto-Thin.ttf') format('truetype'), url('../fonts/roboto/Roboto-Thin.svg#Roboto') format('svg');
    font-weight: 100;
    font-style: normal;
}

Expected behavior
Not to have 404 errors. If the path was correct this wouldn't be an issue.
The font folder is only up one level, not two:
@font-face {
    font-family: 'Roboto';
    src: url('../fonts/roboto/Roboto-Thin.eot');
    src: local('Roboto Thin'), local('Roboto-Thin'), url('../fonts/roboto/Roboto-Thin.eot?#iefix') format('embedded-opentype'), url('../fonts/roboto/Roboto-Thin.woff2') format('woff2'), url('../fonts/roboto/Roboto-Thin.woff') format('woff'), url('../fonts/roboto/Roboto-Thin.ttf') format('truetype'), url('../fonts/roboto/Roboto-Thin.svg#Roboto') format('svg');
    font-weight: 100;
    font-style: normal;
}

Steps to replicate behavior

Fresh install in a subdomain or subfolder. Navigate to the site and watch the network panel.

Screenshots
Current

Expected

This has been resolved as of release v2.6.0 https://github.com/bullhorn/career-portal/releases/tag/v2.6.0


Leaderboard -dApp - "Find out More" // "Learn More"option

Description
As Carbonable I want the user to be able to be able to find more information about the headers available:

"Leaderboard"

"Learn More" for Launchpad

"Learn More" in the "Earn more" pop up

In order to to spread awareness regarding Leaderoard and its point system.
Additional context
Implementation & Design agreed on:
Figma
https://www.figma.com/file/TxyvqO53GlCiTaJOE26AwM/dApp?type=design&node-id=5297-56151&mode=design&t=hCUjQl00CidA9x58-0
Notion:
https://www.notion.so/carbonable/Users-LeaderBoard-Gamification-7a42afb6bbe74a9c8173f8907cc4bc46
Acceptance Criteria
User can perform the following action

[ ]  Click the Find out more and Learn More  button and be able to read more about the right headers.
[ ]  Anchors to the right topic

@Khyati729 I'm gonna do the 2 links on the leaderboard. The one on the project page will be part of #194


make a failed constraint return a 400 bad request code

Add a clause matching when a constraint fails and which returns a 400 bad request code instead of the 500 server error.
fixes #923

Looks fine, but does miss a test.

Yes exactly, but I was wondering where to put it. I'm fairly new to erlang and even more to erlang testing.
Would that be in the http_SUITE.erl file?

Yes. Check the test against /crash/content-length. Then add a new clause to input_crash_h. This handler and test is used to make sure user input results in a 400.

I've just ensured this is done properly, the code has changed a lot so the solution is fairly different now. Closing, thanks!


WIP: Refactor/api client

Summary

#17 added niftycloud_client module to request api and use it other modules

Coverage decreased (-0.2%) to 94.044% when pulling 3c16805c75e377c462ed698f5d74bd97b631eca2 on refactor/api_client into 5fbce331df23242473ef468700b077f5878d77b5 on master.

Tests are OK, but it is failed on ansible.
like this.
---

- name: create instance
  local_action:
    module: niftycloud
    access_key: "XXX"
    secret_access_key: "XXX"
    endpoint: "east-1.cp.cloud.nifty.com"

    ...

fatal: [localhost -> localhost]: FAILED! => {
    "changed": false,
    "failed": true,
    "invocation": {
        "module_name": "niftycloud"
    },
    "module_stderr": "Traceback (most recent call last):\n  File \"/tmp/ansible_2mJpo4/ansible_module_niftycloud.
py\", line 95, in <module>\n    from niftycloud_client import request_to_api, get_api_error\nImportError: No modu
le named niftycloud_client\n",
    "module_stdout": "",
    "msg": "MODULE FAILURE"
}

Ansible module Best Practices wrotes,
http://docs.ansible.com/ansible/dev_guide/developing_modules_best_practices.html
＞Modules must be self-contained in one file to be auto-transferred by ansible.
http://docs.ansible.com/ansible/ec2_module.html
And, ec2 module depends on boto.
So, we need niftycloud signature module like boto, niftycloud-auth(python2 ver), etc.

related issue of ansible is closed....
and in the future version of ansible (v2.3), it looks can be included custom module script in module_utils directory.
https://github.com/ansible/ansible/blob/devel/CHANGELOG.md#23-ramble-on---release-candidate

Allow module_utils for custom modules to be placed in site-specific directories and shipped in roles

This p-r is marked as WIP until these releases.


Distribute latest version on Android

Is this a finance software that aims for security or? The version in google play is still 2.9.4 (vulnerable to jsonrpc bug and subject to theft).
The latest version on the website is 3.1.1 which removes the cors code but does not merge the latest real fix that actually password protects the interface.
The app is hanging all the time. I suggest trying to do a better job.

I think this issue should be reopen, because the version in Google play is <IP_ADDRESS>, but the latest version is 3.1.6.


Add a Universal Analytics Consent Connector

Closes #2468
👉 This is nearly identical to the "Google Analytics" connector, except it passes in a webPropertyId in the user deletion request instead of a propertyId.
Code Changes

[ ] Update existing google analytics saas config and dataset to clarify this is for GA4 not UA.
[ ] Add a new "universal_analytics" connector that is identical to the "google_analytics" connector except that it takes in a UA property instead of a GA-4 property.
[ ] Add the new universal_analytics connector to the registry and update both universal_analytics and google_analytics connectors to use the Google Analytics logo.
[ ]  Add integration tests for universal_analytics. It can share all secrets for google_analytics except the web_property_id/property_id.  Not turned on for CI. (To run locally, obtain an "access_token" via the oauth workflow and add to your secrets.)
[ ] Update the mailchimp transactional logo to use mailchimp instead of the default.

Steps to Confirm
Base Path

[ ] Run nox -s "fides_env(dev)"
[ ] Add GA to the privacy center and set up a universal analytics connector locally. Internal instructions here
[ ] Set Email Marketing in the privacy center config.json to executable = True, rebuild/reload privacy center
[ ] Log into the privacy center and opt out of email marketing
[ ] Log into the admin ui and approve the privacy request
[ ] Verify in your terminal that a user deletion request was sent with a webPropertyId with your UA Tracking Id

POST https://www.googleapis.com/analytics/v3/userDeletion/userDeletionRequests:upsert
headers: {'Content-Type': 'application/json', 'Content-Length': '163', 'Authorization': 'Bearer REDACTED'}
body: {
  "kind": "analytics#userDeletionRequest",
  "id": {
    "type": "CLIENT_ID",
    "userId": "1696XXXXXXX.XXXXXXXXX"
  },
  "webPropertyId": "UA-XXXXXXXX-1"
}

Opt in path

[ ] Update your Email Marketing consent preferences to opt-in in the privacy center
[ ] Approve the privacy request
[ ] Verify that the request is skipped in the terminal because there is no opt-in request defined

No cookies defined path

[ ] Delete your _ga cookie from Application storage
[ ]  Update your Email Marketing consent preferences to opt-out in the privacy center
[ ] Approve the privacy request
[ ] Verify that the request is skipped in the terminal because there is no _ga cookie

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
Documentation:

[ ] documentation complete, PR opened in fidesdocs
[ ] documentation issue created in fidesdocs

[ ] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created
[ ] Update CHANGELOG.md

Description Of Changes
We have a consent connector capable of deleting users from GA4 properties (the google_analytics connector), but not UA properties (universal_analytics).
Adds a new Universal Analytics connector that is identical to the existing Google Analytics connector, except it passes in a webPropertyId in the user deletion request instead of a propertyId in the user deletion request. https://developers.google.com/analytics/devguides/config/userdeletion/v3/reference/userDeletion/userDeletionRequest#resource

Love this @pattisdr, thanks for adding the logos!

Test failures are the same ones we've been seeing on main. These tests are normally not run by default, but I ran the whole suite here.

test_friendbuy_nextgen_erasure_request_task
test_scan_system_aws_passes


Fixed type: ignore comments

Description
Fixed type: ignore comments:

specify which problem should be ignored
removed comment that is no longer valid due to changes made in the code

Type of change

[x] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)

/lgtm

/approve

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.42%. Comparing base (047ee0f) to head (d41f9a1).
Report is 11 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1194   +/-   ##
=======================================
  Coverage   95.42%   95.42%
=======================================
  Files          56       56
  Lines        2381     2381
=======================================
  Hits         2272     2272
  Misses        109      109

Files
Coverage Δ

ols/app/models/config.py
95.70% <100.00%> (ø)

ols/utils/auth_dependency.py
77.55% <ø> (ø)


Activity > Send email accessible to every one

Send email is before entering password, so :

everyone has access to email list (bots too :D )
everyone can send email by batch :D

Currently, without master access we have :

Must be somethink like :

Further functionalities requiring Master access.

Not the optimal way, but its done


RFC: static sanity checks for energy models

@derkling, @credp, @qperret, @valschneider
Please, can you have a look to check if it covers all the tests that you had in mind for the sanity check of the energy model? and if the global form of the tests is fine for you (that the tests are executed in preliminary.py and test_energy_model.py etc...) or if you have other suggestions?

See  #577


Traffic Monitor Integration Test Framework

Adds a Traffic Monitor Integration Test Framework.
WIP, but making a draft for input. It needs some cleanup, but it works, and has a few tests. Instructions are in the README, let me know if you have trouble getting it to work.
Also adds a Go client for the Monitor (because it needed it).
Comments welcome.

What does this PR (Pull Request) do?

[ ] This PR fixes #REPLACE_ME OR is not related to any Issue

Which Traffic Control components are affected by this PR?

CDN in a Box
Documentation
Grove
Traffic Control Client
Traffic Monitor
Traffic Ops
Traffic Ops ORT
Traffic Portal
Traffic Router
Traffic Stats
Traffic Vault

What is the best way to verify this PR?

If this is a bug fix, what versions of Traffic Ops are affected?

The following criteria are ALL met by this PR

[ ] This PR includes tests OR I have explained why tests are unnecessary
[ ] This PR includes documentation OR I have explained why documentation is unnecessary
[ ] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[ ] This PR includes any and all required license headers
[ ] This PR ensures that database migration sequence is correct OR this PR does not include a database migration
[ ] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3918/
Test FAILed.

Rebased, removed draft/WIP. I haven't had time to do more with this, but it basically worked. I don't think there's a reason not to merge it, if anyone wants to use and extend it for Traffic Monitor Integration Testing.

#5817 is based off of #3707 and is merged.


Warning: Failed propType: Invalid prop icon of type object supplied to t, expected string. Check the render method of t.

Hi,
On a fresh install with the example given in configuration section I get this error.
Warning: Failed propType: Invalid prop iconof typeobjectsupplied tot, expected string. Check the render method of t.

I'm not 100% sure about this but it's probably related to #31 and should be fixed by #37.

The non minified error :
Warning: Failed propType: Invalid prop iconof typeobjectsupplied toButtonLoader, expected string. Check the render method of PasswordResetSuccessModal.

same here

same

Try downgrading to material-ui 0.14.2

Im not using material ui

same

I am not using material-ui or bootstrap and I get this issue.
Hmm... Not sure how to trace this error.

@ChrisCates you can fork the repo and merge pull request pending, which resolve this issue.

Can you guys try this again? I think it's been fixed.

@lynndylanhurley I implemented redux-auth 0.0.5-beta5 with a new project. It works fine except some 'Unknown props' warnings that remain.
I've tried the dummy app from a fresh install and gets the following warnings on my console:
dev-server.js?b7b7:60 [HMR] Waiting for update signal from WDS...
only-dev-server.js?2f87:74 [HMR] Waiting for update signal from WDS...
(program):44 Warning: You are manually calling a React.PropTypes validation function for the `formControlFeedback` prop on `Glyphicon`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.warning @ (program):44
(program):44 Warning: You are manually calling a React.PropTypes validation function for the `justified` prop on `Nav`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.warning @ (program):44
(program):44 Warning: Unknown props `bsClass`, `bsStyle`, `expanded`, `onToggle` on <nav> tag. Remove these props from the element. For details, see https://fb.me/react-unknown-prop
    in nav (created by Navbar)
    in Navbar (created by Uncontrolled(Navbar))
    in Uncontrolled(Navbar) (created by Container)
    in div (created by Container)
    in Container (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in Providerwarning @ (program):44
(program):44 Warning: Unknown props `fluid`, `componentClass` on <div> tag. Remove these props from the element. For details, see https://fb.me/react-unknown-prop
    in div (created by Grid)
    in Grid (created by Navbar)
    in nav (created by Navbar)
    in Navbar (created by Uncontrolled(Navbar))
    in Uncontrolled(Navbar) (created by Container)
    in div (created by Container)
    in Container (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in Providerwarning @ (program):44
(program):44 Warning: Unknown prop `active` on <span> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
    in span (created by NavbarBrand)
    in NavbarBrand (created by Container)
    in LinkContainer (created by Container)
    in div (created by Grid)
    in Grid (created by Navbar)
    in nav (created by Navbar)
    in Navbar (created by Uncontrolled(Navbar))
    in Uncontrolled(Navbar) (created by Container)
    in div (created by Container)
    in Container (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in Providerwarning @ (program):44
(program):44 Warning: Unknown props `justified`, `pullRight`, `pullLeft`, `stacked` on <ul> tag. Remove these props from the element. For details, see https://fb.me/react-unknown-prop
    in ul (created by Nav)
    in Nav (created by Container)
    in div (created by Grid)
    in Grid (created by Navbar)
    in nav (created by Navbar)
    in Navbar (created by Uncontrolled(Navbar))
    in Uncontrolled(Navbar) (created by Container)
    in div (created by Container)
    in Container (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in Providerwarning @ (program):44
(program):44 Warning: Unknown props `activeKey`, `activeHref`, `navItem` on <a> tag. Remove these props from the element. For details, see https://fb.me/react-unknown-prop
    in a (created by SafeAnchor)
    in SafeAnchor (created by NavItem)
    in li (created by NavItem)
    in NavItem (created by Container)
    in LinkContainer (created by Container)
    in ul (created by Nav)
    in Nav (created by Container)
    in div (created by Grid)
    in Grid (created by Navbar)
    in nav (created by Navbar)
    in Navbar (created by Uncontrolled(Navbar))
    in Uncontrolled(Navbar) (created by Container)
    in div (created by Container)
    in Container (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in Providerwarning @ (program):44
(program):44 Warning: You are manually calling a React.PropTypes validation function for the `block` prop on `ButtonGroup`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.warning @ (program):44
(program):44 Warning: Unknown prop `sm` on <div> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
    in div (created by Col)
    in Col (created by IndexPanel)
    in IndexPanel (created by Main)
    in div (created by Row)
    in Row (created by Main)
    in div (created by Main)
    in Main (created by Connect(Main))
    in Connect(Main) (created by RouterContext)
    in div (created by Grid)
    in Grid (created by Container)
    in div (created by Container)
    in Container (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in Providerwarning @ (program):44
(program):44 Warning: Unknown props `header`, `defaultExpanded` on <div> tag. Remove these props from the element. For details, see https://fb.me/react-unknown-prop
    in div (created by Panel)
    in Panel (created by IndexPanel)
    in div (created by Col)
    in Col (created by IndexPanel)
    in IndexPanel (created by Main)
    in div (created by Row)
    in Row (created by Main)
    in div (created by Main)
    in Main (created by Connect(Main))
    in Connect(Main) (created by RouterContext)
    in div (created by Grid)
    in Grid (created by Container)
    in div (created by Container)
    in Container (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in Providerwarning @ (program):44
(program):44 Warning: Unknown props `bordered`, `condensed`, `hover`, `responsive`, `striped` on <table> tag. Remove these props from the element. For details, see https://fb.me/react-unknown-prop
    in table (created by Table)
    in Table (created by Main)
    in div (created by Panel)
    in div (created by Panel)
    in Panel (created by IndexPanel)
    in div (created by Col)
    in Col (created by IndexPanel)
    in IndexPanel (created by Main)
    in div (created by Row)
    in Row (created by Main)
    in div (created by Main)
    in Main (created by Connect(Main))
    in Connect(Main) (created by RouterContext)
    in div (created by Grid)
    in Grid (created by Container)
    in div (created by Container)
    in Container (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in Providerwarning @ (program):44
(program):44 Warning: Unknown props `bsSize`, `block`, `navDropdown` on <button> tag. Remove these props from the element. For details, see https://fb.me/react-unknown-prop
    in button (created by Button)
    in Button (created by ButtonLoader)
    in ButtonLoader (created by RequestTestButton)
    in RequestTestButton (created by Connect(RequestTestButton))
    in Connect(RequestTestButton) (created by Main)
    in td (created by Main)
    in tr (created by Main)
    in tbody (created by Main)
    in table (created by Table)
    in Table (created by Main)
    in div (created by Panel)
    in div (created by Panel)
    in Panel (created by IndexPanel)
    in div (created by Col)
    in Col (created by IndexPanel)
    in IndexPanel (created by Main)
    in div (created by Row)
    in Row (created by Main)
    in div (created by Main)
    in Main (created by Connect(Main))
    in Connect(Main) (created by RouterContext)
    in div (created by Grid)
    in Grid (created by Container)
    in div (created by Container)
    in Container (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in Providerwarning @ (program):44
(program):44 Warning: Unknown prop `glyph` on <span> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
    in span (created by Glyphicon)
    in Glyphicon (created by RequestTestButton)
    in div (created by ButtonLoader)
    in button (created by Button)
    in Button (created by ButtonLoader)
    in ButtonLoader (created by RequestTestButton)
    in RequestTestButton (created by Connect(RequestTestButton))
    in Connect(RequestTestButton) (created by Main)
    in td (created by Main)
    in tr (created by Main)
    in tbody (created by Main)
    in table (created by Table)
    in Table (created by Main)
    in div (created by Panel)
    in div (created by Panel)
    in Panel (created by IndexPanel)
    in div (created by Col)
    in Col (created by IndexPanel)
    in IndexPanel (created by Main)
    in div (created by Row)
    in Row (created by Main)
    in div (created by Main)
    in Main (created by Connect(Main))
    in Connect(Main) (created by RouterContext)
    in div (created by Grid)
    in Grid (created by Container)
    in div (created by Container)
    in Container (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in Providerwarning @ (program):44
(program):44 Warning: You are manually calling a React.PropTypes validation function for the `onEnterKeyDown` prop on `TextField`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.warning @ (program):44
(program):44 Warning: Unknown prop `onTouchTap` on <label> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
    in label (created by TextFieldLabel)
    in TextFieldLabel (created by TextField)
    in div (created by TextField)
    in TextField (created by AuthInput)
    in MuiThemeProvider (created by AuthInput)
    in AuthInput (created by EmailSignInForm)
    in form (created by EmailSignInForm)
    in EmailSignInForm (created by Connect(EmailSignInForm))
    in Connect(EmailSignInForm) (created by Main)
    in div (created by Panel)
    in div (created by Panel)
    in Panel (created by ExampleWell)
    in div (created by ExampleWell)
    in ExampleWell (created by Main)
    in div (created by Panel)
    in div (created by Panel)
    in Panel (created by IndexPanel)
    in div (created by Col)
    in Col (created by IndexPanel)
    in IndexPanel (created by Main)
    in div (created by Row)
    in Row (created by Main)
    in div (created by Main)
    in Main (created by Connect(Main))
    in Connect(Main) (created by RouterContext)
    in div (created by Grid)
    in Grid (created by Container)
    in div (created by Container)
    in Container (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in Providerwarning @ (program):44
(program):44 Warning: Unknown prop `errors` on <input> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
    in input (created by TextField)
    in div (created by TextField)
    in TextField (created by AuthInput)
    in MuiThemeProvider (created by AuthInput)
    in AuthInput (created by EmailSignInForm)
    in form (created by EmailSignInForm)
    in EmailSignInForm (created by Connect(EmailSignInForm))
    in Connect(EmailSignInForm) (created by Main)
    in div (created by Panel)
    in div (created by Panel)
    in Panel (created by ExampleWell)
    in div (created by ExampleWell)
    in ExampleWell (created by Main)
    in div (created by Panel)
    in div (created by Panel)
    in Panel (created by IndexPanel)
    in div (created by Col)
    in Col (created by IndexPanel)
    in IndexPanel (created by Main)
    in div (created by Row)
    in Row (created by Main)
    in div (created by Main)
    in Main (created by Connect(Main))
    in Connect(Main) (created by RouterContext)
    in div (created by Grid)
    in Grid (created by Container)
    in div (created by Container)
    in Container (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in Providerwarning @ (program):44
(program):44 Warning: `value` prop on `input` should not be null. Consider using the empty string to clear the component or `undefined` for uncontrolled components.
    in input (created by TextField)
    in div (created by TextField)
    in TextField (created by AuthInput)
    in MuiThemeProvider (created by AuthInput)
    in AuthInput (created by EmailSignInForm)
    in form (created by EmailSignInForm)
    in EmailSignInForm (created by Connect(EmailSignInForm))
    in Connect(EmailSignInForm) (created by Main)
    in div (created by Panel)
    in div (created by Panel)
    in Panel (created by ExampleWell)
    in div (created by ExampleWell)
    in ExampleWell (created by Main)
    in div (created by Panel)
    in div (created by Panel)
    in Panel (created by IndexPanel)
    in div (created by Col)
    in Col (created by IndexPanel)
    in IndexPanel (created by Main)
    in div (created by Row)
    in Row (created by Main)
    in div (created by Main)
    in Main (created by Connect(Main))
    in Connect(Main) (created by RouterContext)
    in div (created by Grid)
    in Grid (created by Container)
    in div (created by Container)
    in Container (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in Providerwarning @ (program):44
(program):44 Warning: You are manually calling a React.PropTypes validation function for the `linkButton` prop on `EnhancedButton`. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.warning @ (program):44
(program):44 Warning: Unknown props `disabledBackgroundColor`, `disabledLabelColor`, `labelColor` on <button> tag. Remove these props from the element. For details, see https://fb.me/react-unknown-prop
    in button (created by EnhancedButton)
    in EnhancedButton (created by RaisedButton)
    in div (created by Paper)
    in Paper (created by RaisedButton)
    in RaisedButton (created by ButtonLoader)
    in MuiThemeProvider (created by ButtonLoader)
    in ButtonLoader (created by EmailSignInForm)
    in form (created by EmailSignInForm)
    in EmailSignInForm (created by Connect(EmailSignInForm))
    in Connect(EmailSignInForm) (created by Main)
    in div (created by Panel)
    in div (created by Panel)
    in Panel (created by ExampleWell)
    in div (created by ExampleWell)
    in ExampleWell (created by Main)
    in div (created by Panel)
    in div (created by Panel)
    in Panel (created by IndexPanel)
    in div (created by Col)
    in Col (created by IndexPanel)
    in IndexPanel (created by Main)
    in div (created by Row)
    in Row (created by Main)
    in div (created by Main)
    in Main (created by Connect(Main))
    in Connect(Main) (created by RouterContext)
    in div (created by Grid)
    in Grid (created by Container)
    in div (created by Container)
    in Container (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in Providerwarning @ (program):44
(program):44 Warning: Unknown prop `vertical` on <div> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
    in div (created by ButtonGroup)
    in ButtonGroup (created by Main)
    in div (created by Panel)
    in div (created by Panel)
    in Panel (created by ExampleWell)
    in div (created by ExampleWell)
    in ExampleWell (created by Main)
    in div (created by Panel)
    in div (created by Panel)
    in Panel (created by IndexPanel)
    in div (created by Col)
    in Col (created by IndexPanel)
    in IndexPanel (created by Main)
    in div (created by Row)
    in Row (created by Main)
    in div (created by Main)
    in Main (created by Connect(Main))
    in Connect(Main) (created by RouterContext)
    in div (created by Grid)
    in Grid (created by Container)
    in div (created by Container)
    in Container (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in Providerwarning @ (program):44
(program):44 Warning: React attempted to reuse markup in a container but the checksum was invalid. This generally means that you are using server rendering and the markup generated on the server was not what the client was expecting. React injected new markup to compensate which works but you have lost many of the benefits of server rendering. Instead, figure out why the markup being generated is different on the client or server:
 (client) r" id="react-select-2--value" data-react
 (server) r" id="react-select-10--value" data-reac

I am missing something? Or the latest release didn't fix this issue?
Thank you for your work. Apart from this issue everything went fine!

I use redux-auth/default-theme and 0.0.5-beta5 fixes this for me
thanks @lynndylanhurley

I'm having the same errors logs that @vwrobel has. Bunch of Unknown props whenever I try to use one of the components


with latest flutter - exception on list with map example

upgraded to the latest flutter 3.7+. Everything seems to work fine on kitchen sink except - Layout: Map with List throws an exception.
To replicate

upgrade flutter
run starter with kitchen sink's app id on Chrome
click on 'Map with List'

definition fixed.

@vusters please describe what was fixed so people would know. Put the yaml here

This is using outdated definition. We will be updating the definition.


Added missing space

@pregress : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks @pregress for submitting this PR and apologies for the delay in approval. Your commit will be merged and this article update is in flight. After the updated article is published, GitHub will list you as an article contributor.
Thanks again for this feedback, your suggestions help improve our documentation.
#reassign:williamdassafMSFT
#Sign-off

@WilliamDAssafMSFT: I'm sorry - only the author of this article, @MightyPen, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Co-ordinates of Japanese cities not appearing.

Also, Japanese text is not working on the URL https://vedastroapi.azurewebsites.net/api/AddressToGeoLocation/　I think it should generally work and google response doesn't differ with the language.

Not sure why certain Japanese cities are not in the system. (will improve in the future)
But the regions or states clearly and obviously are for instance Yokohama is inside Kantō.
So Kantō, Japan works with accurate longitude and latitude.

I suppose right now the right way to look at it

if the town doesn't exist you go to the city,
if the city doesn't exist, you go to state
if the state doesn't exist you go to the country
and if the country doesn't exist you go to the earth

this way you can find the longitude data location in the current VedAstro system


Put link to issue attachment or inline the attachment

Feature Description
Face this issue at least on https://gitea.lemnoslife.com
Screenshots
No response

Pasting an image when copied from xviewer does the job for instance.

Copying from nemo also works.

Files not being images do not seem supported be copy-pasting etc.


Update tapir-core, tapir-http4s-server, ... to 1.9.8

About this PR
📦 Updates

com.softwaremill.sttp.tapir:tapir-core
com.softwaremill.sttp.tapir:tapir-http4s-server
com.softwaremill.sttp.tapir:tapir-json-circe
com.softwaremill.sttp.tapir:tapir-openapi-docs
com.softwaremill.sttp.tapir:tapir-refined
com.softwaremill.sttp.tapir:tapir-swagger-ui

from 1.9.7 to 1.9.8
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.softwaremill.sttp.tapir" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.softwaremill.sttp.tapir" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:early-semver, commit-count:1

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (ed938d5) 50.00% compared to head (4417949) 50.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #507   +/-   ##
========================================
  Coverage    50.00%   50.00%
========================================
  Files            5        5
  Lines           84       84
========================================
  Hits            42       42
  Misses          42       42

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.