Increasing Granularity in UI for Viewing Short Duration Activities

Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
None that I know of
Describe the feature request
I have been trying to visualize activities with short durations in the Aerie UI and have noticed that “granularity” of the UI seems to be at a mismatch with some activity instance durations. For example, I have the following three activities that change change a Shadow state:
Activity Instance 1: Changes Shadow to Penumbra , start = 2023-030/19:37:42, duration = 12s 840ms
Activity Instance 2: Changes Shadow to  Umbra , start = 2023-030/19:37:55, duration = 25m 44s 160ms
Activity Instance 3: Changes Shadow to Penumbra , start = 2023-030/20:03:39, duration = 9s 840ms
Each activity also changes Shadow back to No Shadow at the end of the effect model. However, the activity instances 2 and 3 begin at the same time the previous activity ends, so we should only see the state set back to No Shadow at the end of the 3rd activity instance. (I’d like to verify this with the UI eventually.)
Here’s the main problem I’m having:
I see the correct times and durations in the Selected Activity viewer on the right. However, I cannot zoom in far enough to see these results using the timeline - you can see from the cursor that the UI in the screenshots below skips over Activity Instance 3, and I don’t see the state go from Umbra-> Penumbra-> No Shadow, it looks like the state goes from Umbra-> No Shadow. If I click on the + sign, it zooms in too much (to the microsecond granularity), and I have to click the left and right arrow hundreds of times to view my activities.

With a recent version of Aerie, I am able to zoom in to the granularity of milliseconds.  I'm not sure if this resolves this issue but it should at least help.

We've done a few more improvements on top of the previous work in https://github.com/NASA-AMMOS/aerie-ui/issues/649. Closing this, but please feel free to create another ticket if you think it's still not sufficient enough @Me-ghana .


Restore bacpac backup from previous container failed

Hi,
I'm trying to restore a backup issued from Export-NavContainerDatabasesAsBacpac with following script :
New-NavContainer -accept_eula:$accept_eula `
                 -containername $containername `
                 -auth Windows `
                 -licensefile $mylicense `
                 -Credential $credential `
                 -alwaysPull `
                 -doNotExportObjectsToText `
                 -usessl:$false `
                 -updateHosts `
                 -assignPremiumPlan `
                 -shortcuts Desktop `
                 -IncludeCside `
                 -imageName $navdockerimage `
                 -UseBestContainerOS `
                    -multitenant  `
                    -myScripts @("c:\temp\app.bacpac" , "c:\temp\default.bacpac") `
                    -additionalParameters @('--env appBacpac="c:\run\my\app.bacpac"' ,'--env tenantBacpac="c:\run\my\default.bacpac"')

and I went to this error:
Starting Container
Hostname is
PublicDnsName is micadev01
Using Windows Authentication
Downloading Dac Framework 18.2
Exception calling "DownloadFile" with "2" argument(s): "Unable to connect to the remote server"
at InstallPrerequisite, C:\Run\HelperFunctions.ps1: line 579
at Restore-BacpacWithRetry, C:\Run\HelperFunctions.ps1: line 83
at <ScriptBlock>, C:\Run\SetupDatabase.ps1: line 101
at <ScriptBlock>, C:\Run\SetupDatabase.ps1: line 87
at <ScriptBlock>, C:\Run\navstart.ps1: line 113
at <ScriptBlock>, C:\Run\start.ps1: line 121
at <ScriptBlock>, <No file>: line 1
Initialization of container micadev01 failed
At C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\<IP_ADDRESS>\ContainerHandling\Wait-NavContainerReady.ps1:44 char:17
+ ...             throw "Initialization of container $containerName failed" ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Initialization ...icadev01 failed:String) [], RuntimeException
    + FullyQualifiedErrorId : Initialization of container micadev01 failed

Thanks a lot for your help,
Xavier.

Looks like your container doesn't have access to the internet.
See the section about dns here: https://freddysblog.com/2019/08/20/business-central-on-docker-for-non-experts/ which might solve your issue

Weird, as I don't have any problem to create the same docker without the bacpac (and BTW no warning regarding DNS).

Yeah, I noticed you didn't get the DNS warning - but the error is in the downloadfile.
Maybe a combination with useBestContainerOS causes the DNS error not to appear?
When you have the failed container - it is still running - you can connect to it (enter-navcontainer or docker exec -it  powershell - and try to download something.

The URL it tries to download from is: https://download.microsoft.com/download/9/2/2/9228AAC2-90D1-4F48-B423-AF345296C7DD/EN/x64/DacFramework.msi

Ok, found the root cause : seems that my corporate VPN was messy... switched to NavUserPassword without VPN and now it's ok ;-)
Thanks for your help !


Set-WindowsDesktopWallPaper.ps1

Hi,  We have run this script via Intune and it copies the new Wallpaper from our Azure Storage to the Desktop, however, when I check the log it as the following error and does not automatically set our new corporate wallpaper as the default. Any thoughts?  Thanks Steve
<![LOG[Failed to revert permissions for wallpaper image file. Error message: Cannot convert value "ALL RESTRICTED APPLICATION PACKAGES" to type "Security2.IdentityReference2". Error: "Some or all identity references could not be translated."]LOG]!><time="14:57:03.980+0" date="06-17-2022" component="WindowsDesktopWallpaper" context="NATIONWIDEHIRE\SteveK" type="3" thread="7268" file="">
<![LOG[Failed to revert permissions for wallpaper image file. Error message: Cannot convert value "ALL RESTRICTED APPLICATION PACKAGES" to type "Security2.IdentityReference2". Error: "Some or all identity references could not be translated."]LOG]!><time="16:59:18.345+0" date="06-17-2022" component="WindowsDesktopWallpaper" context="NATIONWIDEHIRE\SteveK" type="3" thread="6656" file="">

We are also seeing this issue. Windows 11 Enterprise 22H2.


Add hint messages when features are disabled.

This patch adds hint messages to give feedback to the user when a
feature is disabled. Namely :

tempfile (disabled because of privileges or timeout)
wal receiver (disabled on Aurora because the feature not available)
system counters (disabled because of lack of privilege, feature unavailable
on Mac, access to the pid file)

I changed pg_is_local_access(). The exceptions are more targeted. I think it's better ... but if I missed one it will crash.
Do you think I should keep the except Exception we had ?

Do you think I should keep the except Exception we had ?

No, that's fine. It doesn't seem needed any more.


Airdrop the giant whale!

Related Safe Addresses
0x8d3a42fd302dfeba6e18f9c48f46ae489fbcbf78
0x3ea4e94791e7ceb84f82fff9decd89c0657fa3c4
0x526f35ed13755a49ff728a1639575972015fdbc9
0x7af79f67ab00a50b4a08390247cc65b8a9512ab4
0xdcb4cf6fc2fed9b80725c1ba0c40723f31a6ff24
0xf08b59fa74174f48e9387b662d4ccfc09b47a7e7
0x95905e9795c6242e1b70c7dca6cb7ff70afe53fb
0x344c416cc1e616223665c0618d123cada1a948fd
0x9715d51c8c5da1c4dfa7ed35750a2bf6d66a47ee
0x27f22677dfab527405bf48b194a1277d2804efc1
0x675b3a5698340dbc0bf4635daa93667b31eea338
0x1500e6a58c031fc9912d301f9a130f9cb3707eed
0xfeb6cfa1d51aa53cd458543e9fd49f3ab87745d4
0x1555dc32f91cf23460bf4b76a2c6196984c02897
0x4985d58c2391ef3caa7502746dc3663e27b2fbc3
0x064210ceb5e1815dc82f274a8ddb8f0d70ac8121
0x993d5adcb4bf8e848ba25a42c92934f59cff5f0a
0x53ff9b7e00c601dcdfeb9d3da5db4252d72757d6
0xb0c67d860158e0592b317488685fbcb3f836c8d6
0x8e1e78354c240f28a01da55611d1bbac2f17fe39
0x5698a89ac10842e658804a9c36a8c5085bfbe3c0
0xcec93b333d4140a7d53b6d72ccf4f5f9dff951b6
0x3b0d3ff250ba494db67fee61d7db296e71a73884
0x3bed69632a03a987cdea408788845bd4818844d4
0x836df11b617bd70c511c56203724c75fee091f0e
0x2502059ec076c5409d7332f57d6f1386710efcb4
0xdb251227116046f5076ae327bd2e8b8cffc22479
0x38810e93eeb9604cccb2ae5a90f8d1e091e3a73d
0x58de9e93c98a88576167d6cd96fc37fe08e4de02
0x7e704b7fa936e14be948338fc9bec46b192bd101
0x37db82ad056447b34aa22feed63fa00fe849c2bf
0x629db9815745cb540bb6526bb3ba19caf6efe011
0x6847b3a7d1d3915dfe361cbb7fb01d79253adde9
0xf4cd502a9eecd2322b453debe9d48a85659670eb
0xa79db9f0fae848a12888f03e5e89e8421c18b71b
0x3b42b6d904b35bf607df792ace74b62b4a9729e2
0xaf7cdadaa6454d2278dc9f6cd0a8eb8f18cf60b3
0xdb7a2deef12a4fb799a3688dc942d92c2feb49aa
0x5c07be8ddd9b34bfb993a98f0b9cf044da08156b
0xbef0e77e3c2c3d07c02ba8a419dab3d95c74dec9
0xfb097c202b55a850a061c09596b4fc709575e020
0xd0ae9c436213ba258cb3fef46733b968c6b3a101
0x6de75bb282898ff5e28e308ee7f8750a0f2b077e
0xb580483068d3a808190287466ab0e524efb908d6
0x0b191f1973c42dd8f1f475752d9272d85f021278
0xc5c22b7afc45ea90e082f4d3b4faea6b30506e8f
0xb687343f5505f33b24eaf395d16f0ec8c5268c26
0xd64ee2aeac0fdb5f431b79c2aed4a2fcda561d23
0xd7fb04241cc0af913bd20433cb732ec4bea57c85
0x02a04a921fbc2716311cb286a3a6fd3636d45421
0xcf16fa07edf1a49e824cbd46e28f849412085a93
0x4d15b6860e2059cb62ec564bfde8b963d6a9c4d8
0x06d169dae221ace6738894b467b6375b37b13f38
0x06368acb396c5b235f5819aac7eff11f6dea142f
0xAE76A64B6Ca68387b953F322cfF7a46097D846E4
0xF02a2098b49D07F335eb66AEbE4eF55706d9EEDf
0x329Cf99D6bac536bac492166e4D4d6B20Cc556be
0x1e2c771266c80dE2dbcbdb57E2716Cfe1C1C9305
0xF3c2879e3815b4D3851B353C76876b93B8Dda5F7
0x12790785fbba06c28c6757e8c7DF7cC3f636b5A3
0x872D65baA9e8fECA7D6dD65796B2855C18C30A54
0x68e77A8145579416f3edA9aEd049d5cf91a53282
0x9E77A2839f572f2BF42B294083CAe9Bb4C875264
0x3bED69632A03a987CDEA408788845bD4818844d4
0x2916965CB25030CeA3045833E36743bADEF32aeD
0x85115B8210bE88F28CA35aC38bF272A0E1B8a0af
0xaDd69F901bAFf4dA16eDA2c1cA0E966918D33502
0x2949353Eb259A91bfb17398DA5451a5Dd8747729
0x14674f786b35150205853D705DB81A26Fba21Ed7
0x3A704C7684238a1b2aeD0ee94A9153Dc1aAC7e6F
0xb566737B43f0BEe5205BfDba9f7f934AfbA1D0a7
0xb59b5ea29690F57b411FBbf9a98E6CDBB6BD45f7
0x4De5bbA9a9FE5EC11d2290a76136C4113552D165
0xB96eE3ffBDd4d2b5Cd4EBF690d91a60a7cd1f4bE
0x21fF718dA8F01FdBBA456d85035B9b3529D787aD
0xd78ae938f0F6df5156EaB14D60DA23Aa3A4aA6E1
0x956e68ceCc3096Ca1c1A1a234b8C64404e094446
0x8c5B88Dc02919177452515114a9000E37510cc7C
0x58e940d446C0899179275B53F9eCF77e1C4c65e9
0xa8246172595716Fa28D62e0e5E26719A87bA67d1
0x667dd118c06324DA9f9DF61C2eb894DC48E32D92
0xa0C33d89C9F8782275B4302f0B37818dF4aCC506
0x4A8C28B424bbd58799b766edeceD5b29F86Cf8fF
0xC6dB09a301Bfb0991458074199a905245f13d043
0x3437977766fe4e39d5AdE5206470ae9aeF15f7aC
0x08551755227D92fdFdF4d2E164eBfe67ec364D8B
0x7C9E2A508d93398B65FA2aecE3F256e3320fb065
0xabB966b8be466a63Ce3B1c5c1cb84C8d923439d5
0xe828fB89DCFdf3f17200aCadC81610Ca6b3bd105
0xAb345D31C805DfBC6983734010DA19d5EE920058
0xBef0E77E3C2c3D07C02Ba8a419DaB3d95C74DEC9
0x5Dd2c4b7CEe0d63f59fbD40E345dc7FAD66550F6
0x27B838c2e151E45b82828630841dc58C75929540
0xfc60020375d6EAF86E299870448B88624cA0202f
0xc44b3e6889C08d0df9Ef494aD8a7cBe176896d11
0x7e704B7fA936e14bE948338fC9bec46B192bD101
0xdb251227116046f5076aE327BD2E8b8cfFc22479
0x3b0D3Ff250ba494DB67FEe61d7DB296e71a73884
0xCeC93b333d4140a7d53B6d72ccf4F5f9dFF951b6
0x5698a89AC10842e658804a9c36A8C5085Bfbe3C0
0x8e1E78354c240F28a01DA55611d1bbac2F17Fe39
0xb0C67d860158e0592b317488685fBCb3F836C8D6
0x53Ff9B7E00C601DcDFEb9D3Da5dB4252D72757D6
0x95905e9795c6242e1b70C7dca6Cb7Ff70AfE53Fb
0x2377420b05bB2df71a5B130ac0e472a46e3297F0
0x61e00016d26a700352E8e7ba3868426b000c8E79
0x7aF79F67Ab00a50B4a08390247Cc65B8A9512ab4
0x993D5ADCB4Bf8E848ba25a42C92934f59cff5f0A
0xEDf65B05908C75a447f3B0462C935429011B318E
0x344C416cc1e616223665c0618d123caDA1A948FD
0xBEABD76e274f9F56c2762e4a5991e3D52F730cfc
0xAB5C0F10Edd3972B5Cd3911c9a81eD2180c218D2
0xe36aaF75975720C0FA3D56087Bf910d2A53Cc959
0xa63d3836d37146a8B186C7B20258f988B5d74426
0xCC191076ef2337cCFA15ce7986e68d45A4144Ee8
Reasoning
After the setup is complete, each safe will receive USDT a few days later and transfer it out. All USDT has been transferred to the exchange, and the following is the address of the exchange that he transferred to receive USDT.
0xacE2689da656A159A17e2Fbdc2ebd1e91C75f229

0xeeB014b4dfb46B11075129fa44E39B1E071F213d

0x980Fd091b280Cdcb98a06b0e2ac3Ceb167FBaa4a

0xdeE8786aE7842D3AE5ed9A5121787fd6cC4671Ec

0x0873b8fCA6E9DA688b9FA46567Ce74A333e1070E

0x0C642Cfc9d008C1048b4Fd6f496b061eCb3aBeb3

0x397fe28Eb459303ba2204c24A272F19491a74e17

0x8A7af05ddf937ec68157b8499c2a9df3Fa290fae

0x363C1807eEAd98D7f3F20614b52B8213B8D8BC88

0xd474ab0BFb3007579Ddb6BF4530DcAA8CF4C1e78
The following are the addresses for creating safes, because the safe addresses I provided are not complete, and some of them are not found because they have created many safes.
0x54f7393E3F2cE76743331c758ae61727D37f08Bd

0xCA33B0EDFB55C99d99B1d8F76f07fFe88036083D

0x196e36D56B480c7FaFa05969122583801C35101a

0x6eafCd29EDE3A1A8C042bdDF9994C204647cad2e

0x1A84e9f0C3E4D4f4278182A126eF6BA55feE0f3c

0x185C16001Fe02bF6F52E9F7A11976C19794eecd4

0x7bDd6529FDFD78b1125AA4d4d152E37b58fE49C0

0x7725913479Ed376B9AcB26Daa4511E8AA335F5AD

0x93750d671c8f424E2A9D39aCE60CeDaaf69d03a8
Methodology
I found the address of the safe in safe_user_allocations_reworked.csv, and clicked on the creator, and found that multiple safes were created at this address, and then I checked whether his safe is related to other addresses association.
Prove that they are all related, check the following addresses, you will find that they have all transferred to the same USDT receiving address, and the correlation is very high.
0x3bED69632A03a987CDEA408788845bD4818844d4

0xb59b5ea29690F57b411FBbf9a98E6CDBB6BD45f7

0x4De5bbA9a9FE5EC11d2290a76136C4113552D165

0xF02a2098b49D07F335eb66AEbE4eF55706d9EEDf

0x4De5bbA9a9FE5EC11d2290a76136C4113552D165
Below are the addresses of the exchanges, also proving the relevance of their safes. Looking at its USDT receipt, you will see that all the USDT comes from the safe, and the addresses they use to create the safe are not the same.
0x397fe28Eb459303ba2204c24A272F19491a74e17
Safe Address
0x3B928329f3dA134c1D72123B7731330D88068777

Related Safe Addresses

Reasoning

Methodology

Safe Address

Airdrop hunters are very cunning, use different addresses to create safes, and use other addresses to execute transactions, but the USDT of the safes will all be sent to the same exchange address, different safe creators, and finally to the same exchange recharge address.

Hopefully, as you can see, these safes are created by different people, deposit USDT, and then transfer out to exchanges.
Please check the USDT records for this address.
https://etherscan.io/token/0xdac17f958d2ee523a2206206994597c13d831ec7?a=0x397fe28Eb459303ba2204c24A272F19491a74e17
There are nearly 50 safe deposit records in USDT with different creators, so it is.

Reasoning
What they do - create multiple safes per address - use other addresses to execute transactions - transfer USDT out through the safe - the exchange address that receives USDT has received USDT from other different creators' safes.

Creating multiple Safes is not airdrop farming per se.

So here they are already identified as hunters, because the last exchange address that received USDT received USDT from other creators' safes.

I don't understand what this means.

After the setup is complete, each safe will receive USDT a few days later and transfer it out. All USDT has been transferred to the exchange, and the following is the address of the exchange that he transferred to receive USDT.

Using the Safe as store of value of USDT is legit usage.
I don't see how storing stable coins of significant value (>1M USD) is airdrop farming. There is a non-zero chance that we would eliminate legit users.


Add ML neuroimaging packages

Follow-up from #3
Most ML-MRI-analysis-packages additionally rely on PyTorch or Tensorflow. Most notably:

fastMRI
Deep-MRI-Reconstruction

Additionally, many pipeline-packages mix and match routines of the "standard" fMRI processing suties AFNI, FSL, ANTs and Freesurfer. Most notably:

mriqc
fMRIPrep
sMRIPrep

With Tensorflow:
neuro-conda-latest.yml.txt


[WIP] Improve AMP, bf16 support. Support oneDNN ops in AMP

Description
General AMP improvements, extending bf16 type support, and adding oneDNN ops support to AMP (and amp_cast fuse)
Backward-incompatible changes
The current model conversion API (convert_symbol, convert_model, and convert_hybrid_block) works without type information and assumes that everything works on floats. To ensure the correctness of conversion of any model and operator, the complete type information must be present. This PR (in addition to numerous fixes) introduces backward-incompatible changes in order to eliminate any assumptions.
Changes in the user API
The user will have to provide information about the data types of the model inputs.
In MXNet 2.0, the main function for model conversion should be convert_hybrid_block. Since the type information will usually be derived from some data example, the user should provide the data example itself. The previous implementation required the model to be hybridized and run at least once before conversion (so the graph is created). This requirement can be now removed since with a data example, the graph can be generated inside convert_hybrid_block (if it is not already present).
Additionally, the cast_optional_params was renamed to: cast_params_offline which I believe is more descriptive.
Before:
def convert_hybrid_block(block, target_dtype="float16", target_dtype_ops=None,
                         fp32_ops=None, conditional_fp32_ops=None,
                         excluded_sym_names=None, device=gpu(0),
                         cast_optional_params=False):

After:
def convert_hybrid_block(block, data_example, target_dtype="float16", target_dtype_ops=None,
                         fp32_ops=None, conditional_fp32_ops=None,
                         excluded_sym_names=[], device=gpu(0),
                         cast_params_offline=False):

convert_model and convert_symbol must also be changed accordingly:
Before:
def convert_model(sym, arg_params, aux_params, target_dtype="float16", target_dtype_ops=None,
                  fp32_ops=None, conditional_fp32_ops=None, excluded_sym_names=None,
                  cast_optional_params=False):

After:
def convert_model(sym, arg_params, aux_params, input_dtypes, target_dtype="float16",
                  target_dtype_ops=None, fp32_ops=None, conditional_fp32_ops=None,
                  excluded_sym_names=[], cast_params_offline=False):

Here the input_dtypes is expected to be a dictionary, mapping names of model inputs to their types.
Before:
def convert_symbol(sym, target_dtype="float16", target_dtype_ops=None,
                   fp32_ops=None, conditional_fp32_ops=None,
                   excluded_sym_names=None, data_names=None,
                   cast_optional_params=False):

After:
def convert_symbol(sym, input_dtypes, param_dtypes, target_dtype="float16", target_dtype_ops=None,
                   fp32_ops=None, conditional_fp32_ops=None, excluded_sym_names=[],
                   cast_params_offline=False):

Similarly, convert_symbol will now require input_dtypes as well as param_dtypes, which will also be a dictionary, mapping names of model parameters to their types.
Changes in behavior
Since we now have full information about the model types, the operator amp_multicast, which previously introduced a lot of uncertainty about the types of layers it preceded, and which had to be handled using (excessive) amp_cast nodes, will never be needed now. It will be replaced by multiple amp_cast nodes (only for tensors that need the casting), which can be then usually fused with oneDNN-optimized nodes using the ONEDNN_AMP pass (if the model was first optimized for the ONEDNN backend).
Because amp_multicast will not be used, the problem with offline casting of parameters discussed below is no longer present.

@ptrendx Could you please explain what is the use case of amp_multicast and why can't we just use multiple amp_cast nodes? Also, why would we cast the input parameters of amp_multicast offline to low precision, doesn't that contradict the purpose of using amp_multicast for these cases?

Hi, the purpose of amp_multicast to cast the inputs of the ops that take multiple of them (think add for example) to be the same widest precision. We can't use multiple amp_cast for this since this cast happens before the type inference and so we do not know what that widest type is. An example - let's take a + b operation. If both a and b are float16, you do not want to insert any casts. If one of them (let's say a) is float32 and the other (b) is float16, then you want to cast b to float32.
Not sure what you mean by casting inputs to amp_multicast offline. There is an optimization for inference cases to cast parameters to float16, but those do not go into amp_multicast but to the regular amp_cast I believe.

Also, adding @mk-61 to the discussion.

Hi, the purpose of amp_multicast to cast the inputs of the ops that take multiple of them (think add for example) to be the same widest precision. We can't use multiple amp_cast for this since this cast happens before the type inference and so we do not know what that widest type is. An example - let's take a + b operation. If both a and b are float16, you do not want to insert any casts. If one of them (let's say a) is float32 and the other (b) is float16, then you want to cast b to float32.
Not sure what you mean by casting inputs to amp_multicast offline. There is an optimization for inference cases to cast parameters to float16, but those do not go into amp_multicast but to the regular amp_cast I believe.

Thanks a lot, I thought that was the case with amp_multicast but wasn't 100% sure.
Regarding the inference optimization - it indeed also applies to the amp_multicast, and it is even tested. I removed this as it seemed unlogical to me, so now these tests fail. Here is a comment about adding this. Was this a bug and my current version is correct?
Here is one of the tests (BTW, the dtype of a variable doesn't matter at here, it will always cast these parameters to fp16):
https://github.com/apache/incubator-mxnet/blob/29ace886946941527047dc5deebe5b4b85b5e4cb/tests/python/gpu/test_amp.py#L133-L139

Hmmm, yeah, not 100% sure about that. I assume this is the effect of this cast_optional_params option? I think I would remove it, since it kind of defies the purpose of AMP (if you want full fp16 you should just cast to it).

@szha What is your take on this?
When a model parameter is an input of the amp_multicast node, it will be cast to lp16 (with cast_optional_params set to True). amp_multicast node is added for ops from this list, so their inputs share one (most accurate) dtype. By the definition, such ops should only run on lp16 when all of its inputs are already in low precision, while currently, input parameters are always cast to lp16, even when they are all f32. I don't think it's intuitive.

@mxnet-bot run ci [windows-gpu]

@mxnet-bot run ci [windows-gpu, windows-cpu, unix-gpu]

Is it still draft/wip?

Is it still draft/wip?

No

@mxnet-bot run ci [sanity]

@mxnet-bot run ci [unix-gpu]

@mxnet-bot run ci [centos-gpu]

@mxnet-bot run ci [centos-gpu]

@szha Could you please review this? Mainly the API changes (shown in the description).

@mxnet-bot run ci [unix-cpu]

@mxnet-bot run ci [centos-gpu, unix-cpu, clang]

@mxnet-bot run ci [unix-gpu, windows-gpu]

@mxnet-bot run ci [centos-gpu, clang]


Set scoped=true/false in require statement

It would be great to allow setting scoped property on a template basis, inside the import statement.
I think something like this could do the trick:
import viewRender from './component.html?scoped=false&style=component.css'

Hmm, I actually want to keep this query trick as minimum as possible since this seems to be non-standard implementation. Also this can be complex and unreadable code easily if we allow more options for that place.
What is the use case of this option? I personally think, it would be enough to use plain style-/css-loader if we want non-scoped style.

I see.
My idea is to have as much as possible the same capabilities that when using .vue single-file components with vue-loader. It's used to emulate the scoped attribute of <style> tag from single-file components.

I've rethought about this but I still have no idea of valid usage. It looks clearer just importing .css files directly if we want non-scoped styles. And I think we can cover the vue-loader's functionality with such approach.
Import css files directly:
import withRender from './template.html'
import './global.css'

Introducing scoped on query:
import withRender from './template.html?scoped=true&./global.css'

So I'm closing this issue. Thanks for your suggestion and PR, though!


Added spsjc

Added spsjc

@TheShaltys Please provide us with:

the school official website URL, if different from the domain you are submitting
an URL of a page on the official website where an IT-related long-term (>1 year) course is offered by the school
an URL of a page or another proof (.pdf or a screenshot are OK) showing that the school recognizes the domain which you are submitting as an official email domain for the students.

@TheShaltys I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for the understanding!


Surfacing Cilium error messages in cilium status

When troubleshooting Cilium installation and deployments, users often rely on the Cilium CLI to check the overall health of the Cilium deployment. While very useful, it lacks the context and the valuable logs that are often available on the Cilium agents.
As an example: when installing Cilium with incorrect settings, you might see fatal error messages in the Cilium agent logs, such as:
time="2024-06-10T14:23:43Z" level=fatal msg="invalid daemon configuration: native routing cidr must be configured with option --ipv6-native-routing-cidr in combination with --enable-ipv6=true --enable-ipv6-masquerade=true --enable-ip-masq-agent=false --routing-mode=native" subsys=daemon
These logs can be very instructive but require the user to check the logs across multiple Cilium agents or on the Cilium operator(s).
Could we append cilium status with logs of the fatal and error severity? This could be the default behaviour or when using a flag (cilium status --show-logs or something along the lines). This would be very helpful for operators of Cilium.

:take-my-money:


Updated edgescan parser and documentation

Context
Some endpoints created from edgescan's vulnerability.location were malformed, most likely due to hostnames being passed to the Endpoint.from_uri() function.
Changes

Updated parser to add endpoints and CVSS scores correctly
Added method to parser to indicate a file is not required
Updated API client to accept multipl asset IDs
Updated documentation

Hi @ShayVD this looks good so far! Can you please update the unit tests as well?


[Inquiry] Killing a Node.js frequently while developing

I have a question. While I am developing my node.js server, I will be killing and restarting the server by either a SIGKILL using CTRL+C or via Nodemon which would restart the Node.js server.
Is this safe? I just want to make sure so I don't have problems down the line.
Thanks!

Hi @PolymorphiK this module is just standard JavaScript and itself doesn't have issues with that.


Horizontal and vertical detail possibly switched in wavedec2

Hi,
I noticed that horizontal and vertical bands may be switched around in wavedec2. Here is some IPython notebook code to reproduce this:
import numpy as np
import pywt
from scipy.misc import imread, imsave
from skimage.draw import polygon
import matplotlib.pyplot as plt
%matplotlib inline

img = np.zeros((256, 256))

poly1 = np.array((
        (50, 50),
        (50, 100),
        (100, 100),
        (100, 50)
    ))

poly2 = np.array((
        (150, 100),
        (100, 150),
        (150, 200),
        (200, 150),
    ))

rr, cc = polygon(poly1[:, 0], poly1[:, 1], img.shape)
img[rr, cc] = 1

rr, cc = polygon(poly2[:, 0], poly2[:, 1], img.shape)
img[rr, cc] = 1

db4 = pywt.Wavelet('db4')
img_w = pywt.wavedec2(img, db4, mode='sym', level=1)

fig1, ((ax1, ax2), (ax3, ax4)) = plt.subplots(2, 2)

ax1.imshow(np.absolute(img_w[0]), cmap=plt.cm.gray)
ax1.axis('off')
ax1.set_title('Approximation')

ax2.imshow(np.absolute(img_w[1][0]), cmap=plt.cm.gray)
ax2.axis('off')
ax2.set_title('Horizontal detail')

ax3.imshow(np.absolute(img_w[1][1]), cmap=plt.cm.gray)
ax3.axis('off')
ax3.set_title('Vertical detail')

ax4.imshow(np.absolute(img_w[1][2]), cmap=plt.cm.gray)
ax4.axis('off')
ax4.set_title('Diagonal detail')

This is not a bug in PyWavelets, but just a different convention on which axis is "horizontal" vs. "vertical".  In PyWavelets, what is labeled "horizontal" is axis 0 while "vertical" is axis 1 (as indicated in the docstring).  However, imshow uses a different convention, where axis 0 is displayed vertically.

That said, we could probably make this clearer in the documentation.   I think it is only the 2D routines that have the potential for confusion as the n-dimensional case uses explicit names such as 'da', 'da', etc. that make it clear which filters were applied on each axis.


Map not rendered after getting Places from the Places API

I am trying to integrate react-google-maps with the vanilla google places API. I have a handler for the bounds_changed event that fires correctly.
onBoundsChanged() {
            let mapBounds = this._map.getBounds();
            console.log(this._map);
            let service = new places.PlacesService(this._map.getDiv());
            console.log(this._map.getDiv());
            service.nearbySearch({bounds: mapBounds, type: "night_club"}, function (results, status) {
                console.log(results);
                console.log(status);
                this.setState({nearBy: results});
            }.bind(this));
        }

this._map,  results and status are  all correctly printed to the screen and this._map.getDiv() correctly prints the target Div. I get no errors, however the map is not rendered.
If I leave out the instantiation of the places service  i.e
let service = new places.PlacesService(this._map.getDiv());

and the call to nearbySearch() then the map is rendered without any issues.
I'm not sure what I'm missing. My knowledge of react is also quite limited so the problem is might be due to that.  Apologies if that is the case.

Hope you found a solution for this. In case I don't and for the future this is my current approach to this topic.
I have the same issue, what (seems) to work for me is remove the map and add it again each time I want to load new marks.
Something like:

componentDidMount: function() {
   this.setState({
      loading: true
   })

   api.getPlaces().then(function(newPlaces) {
      this.setState({
         loading: false,
         places: newPlaces
      }.bind(this))
   })
},

getInitialState: function() {
   loading: true,
   places: []
},

render: function() {
   if (this.state.loading)
      return
LOADING

   else
      return <Map marks={this.state.places}/>
}

The idea is delete the Map component each time you get new places.
Note: I'm using the v5.0.1 because I can't use React 15 at this point. Maybe that's another issue.

Any update on this? I am getting the same issue.

Please refer to Getting Help section in the README (or #469).


enum generated of map[string]int32 should be map[string]MyEnum

For an enum MyEnum which generates:
type MyEnum int32
...
var MyEnum_value = map[string]int32{
  ...
}

Shouldn't it generate a map[string]MyEnum instead? That way you could do:
var foo MyEnum
foo = MyEnum_value["FOO"]

The only other place this map is used (in unmarshalling) just casts it to an int64 anyway, so it should be fine.

No, it's intended. Those maps are principally for internal use (e.g. for the text formatter) and having them all be the same type (map[string]int32) means that the code doesn't need reflection to operate on them. They are used fairly rarely in human-written code.


support global edges

e.g. to write an edge from external id to internal id
right now we can hack around by just using different type and not validate it

Is this something that would be needed for a sharded DB?

Is this something that would be needed for a sharded DB?

theoretically but would need to figure out the source id. or use a different data format to store it
e.g. external id mapped to native id on one of the shards
edge from native id to internal id
involves an extra hop
or use the same logic used for sharding to shard the external id. has its flaws but works.


If source control pane is small, you might not realize you're pushing

When it's small:

When it's bigger:

I didn't realize this was also gonna sync since the & Sync part was hidden.

Thanks for the feedback. This is currently by design. We made a decision not to wrap the action button and that is why commands provide both a title and a description. The description (ex: Commit & Sync) is shown when there is enough space to render it, while the title (ex: Commit) is shown there there is not enough space. All commands have "Commit" as the title, and we use the icons (ex: sync) to convey additional information.  Happy to tweak things if we believe there is a better way to do this.
//cc @misolori, @daviddossett

We could also consider dropping the icon in favor of the text at these smallest widths. However we would lose the nice icon animation.

Is there a reason why there isn't an ellipsis in the text? That should be Commit... so it gives an indication that it's cut off

The current implementation was done based on feedback in the UX channel. I am happy for us to adopt a pattern across all buttons where we always have the labels on one line and use an ellipsis (...) in case there is not enough room to display the label.

Where did the proposal to drop the label altogether end up? E.g.
() Sync Changes 10 v 5 ^
() 10 v 5 ^

Where did the proposal to drop the label altogether end up?

That is something that has been implemented for the "Sync Changes" button as that one is quite complex with multiple icons and text segments. For that particular button it does make sense to drop the label altogether when there is not enough room.
As I said, I do think that in case of the dropdown button we adopt the pattern of have one single label and then using text overflow (...) in case there is not enough room. Here is a prototype of how that would look like. @daviddossett, should we go ahead with this?


MB-6469 Add show=true filter and tests for MTOShipmentsMTOAvailableToPrime function

Description
This PR adds a filter to only find shipments connected to enabled, or show=True, moves in the MTOShipmentsMTOAvailableToPrime function. This service object's purpose is to verify that the shipment is connected to a Prime-available (and now, enabled) move, and it is used in the updateMTOShipment endpoint in the Prime API.
Setup
To test this update, you will have to set up two tools:

Either the Prime API Client or Postman with Prime API
Either Postman with Admin API or a DB viewer connected to the MilMove dev DB (<- these instructions are applicable to most DB viewers, not just the two listed there)

Once you have set up your testing environment, follow these steps:

Hit the Prime API fetchMTOUpdates endpoint. Select a random MTO in the output, and grab these three bits of information:

the MTO's ID
the ID for one of the MTO's shipments
the eTag for the same shipment selected above

Go to the Prime API updateMTOShipment endpoint and, using the same shipment ID and eTag selected previously, try an update with a simple request body like:

{
  "firstAvailableDeliveryDate": "2021-02-02"
}

Verify that your update succeeded (200 response code) and grab the new eTag value for the shipment

(If you set up the Admin API with Postman) Go to the Admin API updateMove endpoint and, using the MTO ID grabbed above, send this request body:

{
  "show": false
}

Verify that your update succeeded (200 response code)

(If you are using a DB viewer) Find the record in the moves table with id='<the MTO ID you picked>'. Go to the show column and change this value to false. Make sure you push and commit this change.
Go back to the updateMTOShipment endpoint and submit the exact same request with the new eTag value. You should get a 404 response saying the shipment was not found.

Code Review Verification Steps

[x] The requirements listed in Querying the Database Safely have been satisfied.
[ ] Request review from a member of a different team.
[x] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change.

Messages

:book:
:link: MB-6469

  Generated by :no_entry_sign: dangerJS against bab180c4896b053b5f0e8e483a5ea873f2b301dd

Messages

:book:
:link: MB-6469

  Generated by :no_entry_sign: dangerJS against bab180c4896b053b5f0e8e483a5ea873f2b301dd


Implement TextAreaFor()

Razor has @Html.TextArea() and @Html.TextAreaFor().
Bootstrap().TextArea() exists, but not Bootstrap().TextAreaFor().
Apparently there's no InputType.TextArea nor any extensions that transform Bootstrap().InputFor() to <textarea> as well, so I doubt the lambda expression version of the html helper to model property for <TextArea> is actually implemented. Correct me if I'm wrong tho.
Thanks in advance!

This is now implemented and will be pushed in a new release to NuGet momentarily - sorry for the delay!


[Bug] Helm releases are not persisting during creation as part of the release process

We need to save the chart created as part of the release process in charts

I think we may want to consider using the Helm Release Action here. Basically, the charts will be published to the gh-pages branch and we would just expose that branch as our GitHub page.
This would have the following benefits:

Avoid branch protection issues that are difficult to workaround.
Remove charts from the main branch
Follow a documented Helm deployment pattern

Would it being on that branch still make the artefacts available?

From what I can tell, yes. As long as the GitHub page contains the artifact, everything should work.

Is this still open?

Yes, it's still an issue. @skyerus was going to look into this tomorrow.

I don't think Helm release action is exactly what we're looking for here as it creates a new release which we already have a workflow for (release-please). However, we can hijack the rest of the process and reproduce it in the existing release workflow.

[ ] Create a branch called gh-pages from main
[ ] Change the Github Pages branch setting to gh-pages here
[ ] Create a PR removing the existing published charts from main
[ ] Create a PR merging main to gh-pages and re-adding the existing published charts
[ ] Create a PR to main appending release charts to the existing workflow


Basic minor improvements

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

Project coverage is 100.00%. Comparing base (c5c9976) to head (11628cc).

Additional details and impacted files
@@            Coverage Diff            @@
##              main        #9   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           50        50
  Lines         1137      1137
=========================================
  Hits          1137      1137

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


The Kali machines have only 1GB of RAM when started

Apparently this makes the Kali machines slow down and eventually freeze to death where only solution is to create a new lab.

At the lowest level in Haaukins' Go code, SetRAM might (see here) malfunction, but since we have no unit test in place, we simply do not know yet.
So in order to test whether this function contains a bug, I would recommend to add a unit test to vbox_test.go. Since the method itself might be difficult to test, you could test the LinkedClone function (see here).
@mrturkmen06 Try to think of a test case:

What must be in place before you call the LinkedClone function?

(For example, must there be parent VM already imported?)
And how can you ensure that these requirements are in place in your test code?

What parameters should you provide to the LinkedClone function?

Hint: the parameters should probably among other parameters contain the SetRAM function somewhere, since that is the piece of code we actually want to test.

What behavior do you expect to observe from Haaukins?

How can you verify this behavior in your test code?

How do you clean up after the test?

Parent VM imported and created Snapshot information set

The requirements to be in test code can be observed by checking parameters of actual function (the function which should be tested.)

Context, Snapshot information and VmOpts parameters provided
The expected behaviour tested out by retrieving information from linkedclone using vboxmanage showvminfo <id-of-vm> then parsed amount of ram and cpu values which should same what I set at the beginning (by providing VmOpts parameters)
After test, the status of test function should remain same therefore all initialised VMs and other parameters removed

According to tests, there is nothing wrong with SetRam and SetCPU functions. In next steps, unmarshalling and creating config files functions will be tested

Tested NewFrontends function here > Passed
The other tests and functions checked, there is no obvious parsing and handling error.
Additionally, when an event file is created on daemon side,  it stores correct information regarding to RAM value, but does not initialise correctly, STOP>MODIFY>RESTART steps will be investigated more carefully.

#226 is ready to review, I think, problem is solved.

closing issue in favor of #226  merged into 1.5.2

Reopening for the sake of TODO in 1.6.2

Fixed (again) in #243


[CI][quality] Post-merge review of #2150

Post-merge review of #2150:

[ ] CODECOV https://github.com/ROCmSoftwarePlatform/MIOpen/pull/2150#discussion_r1205703424
[ ] FP32 gfx1030 Smoke test https://github.com/ROCmSoftwarePlatform/MIOpen/pull/2150#discussion_r1205705720
[ ] FP16 Vega20 Smoke test https://github.com/ROCmSoftwarePlatform/MIOpen/pull/2150#discussion_r1205706541
[ ] INT8 Vega20 Smoke test https://github.com/ROCmSoftwarePlatform/MIOpen/pull/2150#discussion_r1205707320
[ ] INT8 Full tests https://github.com/ROCmSoftwarePlatform/MIOpen/pull/2150#discussion_r1205711247

We are in danger wrt INT8 support.

[Attribution] @junliume @JehandadKhan

https://github.com/ROCmSoftwarePlatform/MIOpen/labels/quality
https://github.com/ROCmSoftwarePlatform/MIOpen/labels/testing
https://github.com/ROCmSoftwarePlatform/MIOpen/labels/urgency_normal
Proposed assignee: @JehandadKhan

@atamazov thanks! I was about to create an issue from your comments until I see this one.

We can add an INT8 stage for the MI series, which should be sufficient

@JehandadKhan Maybe Smoke INT8 for non-MI as well?

@JehandadKhan @junliume I can make the PR, but unfortunately changes in Jenkinsfile from my PRs won't be tested because these reside in the forked repo.

@atamazov I can help to kick off the CI test or take the branch for test.

@junliume

@atamazov I can help to kick off the CI test or take the branch for test.

Thank you, Jun! Jenkinsfile changes from forks are ignored. Anyone who decides to help me will have to copy my branch to the MIOpen repository, like this:
# Do this once:
git remote add fork_artem https://github.com/atamazov/MIOpen.git
# Then
git fetch fork_artem BRANCH && \
git checkout BRANCH  && \
git pull fork_artem BRANCH && \
git push origin BRANCH

He/she then informs me and I will create a PR from the copied branch (which resides in this repo). From time to time I may ask for updating the copy from my fork.
Please let me know if you are Ok with this procedure. BTW I can try to find other volunteers ;)

@atamazov  I can do it, just ping me a few more times in the day :)

@junliume Is this ticket still relevant? Thanks!


tests: net: socket: af_packet_ipproto_raw move to new ztest API

Move af_packet_ipproto_raw tests to use new ztest API
TEST=twister -T tests/net/socket/af_packet_ipproto_raw/
Signed-off-by: Hu Zhenyu<EMAIL_ADDRESS>

This test case cannot be run with CONFIG_ZTEST_SHUFFLE =y, as some of the test case cannot be run twice.


SSL verification is Running - Domain registered in account A pointed to amplify website on account B

App Id: d2ifucdfz09ieg
Region: us-east-2
Step: SSL verification
Status: Running

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
I have a domain www.example.com registered in an AWS Account A, and a hosted zone in AWS account B that also has the amplify app. I have changed the name servers in AWS Account A and can choose the www.example.com domain in the drop-down menu of amplify, but SSL verification has been going on for more than an hour. I want to know if this set up is okay, or if I have to do something to verify.
Error message
"We validated that the CNAME record exists in your DNS file. We will now verify ownership of the domain."
Note: Be sure to check the message for sensitive information.
Additional information
Please add any other relevant information. Please feel free to include screenshots.

Update - been about 4 hours now, still the same status.

@w601sxs you might've seen this message in the console indicating that it may take longer than 8 hours:

If it's still pending verification after 8 hours, you can check this troubleshooting doc if you haven't already to see if it helps: https://docs.aws.amazon.com/amplify/latest/userguide/custom-domains.html#my-domain-hosted-with-a-third-party-is-stuck-in-pending-verification-state
Let me know if you've already gone through those troubleshooting steps and it's still pending.

Hi Don,
Looks like the second troubleshooting section (with respect to Route53 and
nameservers matching) applies to my case.
That is a step that I took, and this is why I was able to select my domain
from the amplify dropdrown, although the domain was registered on a
different AWS account. I have also tried deleting the domain, relaunching
the app in another region, and trying to connect the domain name again.
Now, my app id is d1o5q2rs3dom5k.
I also changed the "baseURL" in my hugo website to match the domain name.
What else can I do?
Shreyas
On Mon, Mar 16, 2020 at 8:10 PM Don J. Kahn<EMAIL_ADDRESS>wrote:

@w601sxs https://github.com/w601sxs you might've seen this message in
the console indicating that it may take longer than 8 hours:
[image: Screen Shot 2020-03-16 at 17 02 10]
https://user-images.githubusercontent.com/8794073/76809650-c7a70580-67a8-11ea-97a7-e4f50887db96.png
If it's still pending verification after 8 hours, you can check this
troubleshooting doc if you haven't already to see if it helps:
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domains.html#my-domain-hosted-with-a-third-party-is-stuck-in-pending-verification-state
Let me know if you've already gone through those troubleshooting steps and
it's still pending.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-console/issues/516#issuecomment-599813606,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZFPFLUUCMCU5AOW2OY5ZLRH25W7ANCNFSM4LMKWDDA
.

Hi Don,
I'm still stuck at the same stage. What do you suggest I do?
Shreyas
On Tue, Mar 17, 2020 at 10:03 AM Shreyas Subramanian<EMAIL_ADDRESS>wrote:

Hi Don,
Looks like the second troubleshooting section (with respect to Route53 and
nameservers matching) applies to my case.
That is a step that I took, and this is why I was able to select my domain
from the amplify dropdrown, although the domain was registered on a
different AWS account. I have also tried deleting the domain, relaunching
the app in another region, and trying to connect the domain name again.
Now, my app id is d1o5q2rs3dom5k.
I also changed the "baseURL" in my hugo website to match the domain name.
What else can I do?
Shreyas
On Mon, Mar 16, 2020 at 8:10 PM Don J. Kahn<EMAIL_ADDRESS>wrote:

@w601sxs https://github.com/w601sxs you might've seen this message in
the console indicating that it may take longer than 8 hours:
[image: Screen Shot 2020-03-16 at 17 02 10]
https://user-images.githubusercontent.com/8794073/76809650-c7a70580-67a8-11ea-97a7-e4f50887db96.png
If it's still pending verification after 8 hours, you can check this
troubleshooting doc if you haven't already to see if it helps:
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domains.html#my-domain-hosted-with-a-third-party-is-stuck-in-pending-verification-state
Let me know if you've already gone through those troubleshooting steps
and it's still pending.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-console/issues/516#issuecomment-599813606,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZFPFLUUCMCU5AOW2OY5ZLRH25W7ANCNFSM4LMKWDDA
.

Still running, any tips? What do I do?

Hi @w601sxs have you checked that your CNAME resolves? Following these steps

I deleted and redeployed with the same settings and I'm now live. No
changes from my end. strange.
On Wed, Mar 25, 2020 at 2:06 PM Jared Franzone<EMAIL_ADDRESS>wrote:

Hi @w601sxs https://github.com/w601sxs have you checked that your CNAME
resolves? Following these steps
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domains.html#how-do-i-verify-that-my-cname-resolves
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-console/issues/516#issuecomment-603997670,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZFPFKA2JY62GRGF5FJ7ALRJJBZ3ANCNFSM4LMKWDDA
.

Great! Closing this issue for now. Please feel free to open if you are still having problems.


[FEATURE] LocalAI integration

Describe the feature you'd like
https://github.com/go-skynet/LocalAI (https://localai.io/) is a OpenAI drop-in API replacement with support for multiple model families to run LLMs on consumer-grade hardware, locally. As it is compatible with OpenAI, it just requires to set the base path as parameter in the OpenAI client, there is also an example with langchain-js in the LocalAI repository here: https://github.com/go-skynet/LocalAI/blob/577d36b5964ba0873b945f2ea00404ed52556408/examples/langchain/langchainjs-localai-example/src/index.mts#L7
Additional context
An integration with Flowise would allow the user to run everything entirely locally - I'm not sure if it makes sense to have a separate integration, or either allow the OpenAI integration which already exists to set a parameter from the user

hey @mudler great to have you here!
We just integrated LocalAI - https://github.com/FlowiseAI/Flowise/pull/123 into Flowise not long ago, will be publishing the new release in next hour or so!

This is fantastic @HenryHengZJ ! thank you!


helm-M-x-execute-command: Wrong number of arguments: (1 . 1), 2 Copilot mode enabled in current buffer

duplicate of #42


Share CBS Session

Initialize the _received_messages when in the __init__ function of the AMQP client so that received messages won't be simply dropped during the authentication process of multiple clients.

@annatisch
I'm wondering whether the self._streaming_receive should be thread-safe or not.
The situation where thread-unsafe may happen to the _streaming_receive variable is that both functions receive_message_batch and receive_messages are called simultaneously.
But I don't think our SDK support such kind of operation, do I miss something?

The function release_async in connection_async.py isn't a co-routine function.
The name is a bit misleading as we may think release-async is an async function and call it by await release_async().


Fix symlink copy of directories for apps icons

cc @terlar
see https://github.com/nix-community/NixOS-WSL/pull/368#issuecomment-1875547214

#380

Thanks, had some time so made the PR anyways. I also agree that the long options is better in code and adds extra clarity.


Build Ruby Gem: Some jobs were not successful

Hi, first of all, thank you for your wonderful theme.
If I modify the file and push, three workflows will be executed as shown below, and the Ruby Gem build will eventually fail like in the picture.

When I click on the failed workflow, it says test (2.6) failed.

If you look at the log, there is an error. I really don't know how to fix the error.
ERROR:  Error installing type-on-strap:
	The last version of rouge (>= 3.0, < 5.0) to support your Ruby & RubyGems was 3.30.0. Try installing it with `gem install rouge -v 3.30.0` and then running the current command again
	rouge requires Ruby version >= 2.7. The current ruby version is <IP_ADDRESS>.

I tried gem install rouge -v 3.30.0 and updated ruby. but it's still the same.
Run gem install type-on-strap
Successfully installed public_suffix-[5](https://github.com/aerimforest/aerimforest.github.io/actions/runs/3296756741/jobs/5438153304#step:7:6).0.0
Successfully installed addressable-2.8.1
Successfully installed colorator-1.1.0
Building native extensions. This could take a while...
Successfully installed http_parser.rb-0.8.0
Building native extensions. This could take a while...
Successfully installed eventmachine-1.2.7
Successfully installed em-websocket-0.5.3
Successfully installed concurrent-ruby-1.1.10
Successfully installed i18n-1.12.0
Building native extensions. This could take a while...
Successfully installed ffi-1.15.5
Building native extensions. This could take a while...
ERROR:  Error installing type-on-strap:
	The last version of rouge (>= 3.0, < 5.0) to support your Ruby & RubyGems was 3.30.0. Try installing it with `gem install rouge -v 3.30.0` and then running the current command again
	rouge requires Ruby version >= 2.7. The current ruby version is 2.[6](https://github.com/aerimforest/aerimforest.github.io/actions/runs/3296756741/jobs/5438153304#step:7:7).10.210.
Successfully installed sassc-2.4.0
Successfully installed jekyll-sass-converter-2.2.0
Successfully installed rb-fsevent-0.11.2
Successfully installed rb-inotify-0.10.1
Successfully installed listen-3.[7](https://github.com/aerimforest/aerimforest.github.io/actions/runs/3296756741/jobs/5438153304#step:7:8).1
Successfully installed jekyll-watch-2.2.1
Successfully installed kramdown-2.4.0
Successfully installed kramdown-parser-gfm-1.1.0
Successfully installed liquid-4.0.3
Successfully installed mercenary-0.4.0
Successfully installed forwardable-extended-2.6.0
Successfully installed pathutil-0.[16](https://github.com/aerimforest/aerimforest.github.io/actions/runs/3296756741/jobs/5438153304#step:7:17).2
Error: Process completed with exit code 1.

Ah it seems Rouge is dropping support for Ruby 2.6, I don't see it in their GitHub action anymore: https://github.com/rouge-ruby/rouge
In my case I think it's Rouge 3.26.0 that is installed.
Let's remove 2.6 and add 3.1 instead.

@sylhare Wow the error is resolved.
Thank you so much:-)


How to handle records with more than 8 fields

The documentation says that "records with up to 8 fields are supported". I have couple questions about that:

Is it possible to give a better error message when you try to use a record with more than 8 fields? Currently I get a bunch of Label "foo" does not occur in R ( (...) ) errors.
Can the limit be increased? In the past I have used a record with 46 fields.

By the way, thanks for making such a wonderful library!

Is it possible to give a better error message when you try to use a record with more than 8 fields? Currently I get a bunch of Label "foo" does not occur in R ( (...) ) errors.

Error messages regarding too many fields are something I haven't worked on. I will look into it.

Can the limit be increased? In the past I have used a record with 46 fields.

In the future, yes. I would like to convert all those instances in rawr to be TH-generated at some point, so changing the number of supported fields will be as simple as changing a number. This is going to take a while though because there will be quite a lot of TH to write.

As of 9e366a58d988526bbfd017471952e68e7266d27b, error messages when attempting to construct records with over 8 fields should be improved:
> R ( #a := (), #b := (), #c := (), #d := (), #e := (), #f := (), #g := (), #h := () ) :*: R ( #i := () )

<interactive>:3:1: error:
    • RecCons: too many fields
    ...

I'm keeping this issue open until more than records with >8 fields are supported.

Great! I'd quite like if more than 8 could be supported as well.
I'm also experimenting with bookkeeper, which does seem to support unlimited amount of fields (tried with 9 and 10 just now), but compile time seems to increase non-linearly (O(n^2) or O(2^n) maybe?) with adding fields.
Even just loading a 10-field book into ghci takes about 20 seconds on my system.
Is this explosion of compile time the reason why rawr prohibits fields greater than 8? Once the aforementioned TH code is written, we can have near-instant 15-field ad-hoc records as well with rawr?


Stils on Android dex issues

When using the stilts-stomp-client on Android, during compilation I get the multiple dex files error:
Error:Android Dex: [example.stomp] com.android.dex.DexException: Multiple dex files define Lorg/projectodd/stilts/stomp/Constants;
The error occurs due to the fact that the Constants.java exists in both the stom-api and stomp-client dependencies in the same package namespace.

I have the same problem

i have too


Custom route configuration

Per our discussion in #41:
@reliq brought up the point:

@austintoddj I ran into one instance which would prevent allowing users to modify the admin routes. This is with TalvBansal\MediaManager\Routes\MediaRoutes. The url's are hard-coded in JS and do not seem customizable.
As you would see in RouteHelper.php on line 62, there is provision to allow customizing admin routes but because of the foreseen errors regarding the hard-coded media manager aspects (mentioned above) I have removed the option from the config/blog.php file. So the end-user cannot customize admin routes the easy way at this time.
What are your thoughts on this?

@talvbansal Can you think of any way we could let the Media Manager play nicely with custom route configuration in Canvas?

I'll have to have a longer think about this, as @reliq rightly says the route names are coded in JS and then webpacked and therefore (at least to me) not going to be configurable using php.
Even if i added route names to the TalvBansal\MediaManager\Routes\MediaRoutes file I dont think tat the javascript would have no way of picking those route names up?
I'm definitely open to suggestion on this if anyone can think of a way around it?

@reliq Is this something that will prevent our v3.0.0 release? If not, I'll move this discussion off the current release schedule and we can further explore our options on it.

@austintoddj we could leave it out for now since the config to change the admin routes is not currently being published (in config/blog.php).

Looks like this could be continued on now that we have at  least configurable prefixes for the media-manager


Use Keytab file for Credentials

Hi All,
I was wondering if there was plans to be able to use a keytab file as means of authentication.
Something like:
... = new KerberosKeytabCredential("PrincipalNameHere", "./PathToKeytabFile", "realm");
Thanks much for the library.

I haven't added it yet, but PR's are welcome.
The keytab functionality is already present, and it produces KerberosKey’s. KerberosCredential is intended to be extended for the various credential types like passwords, certificates, etc. They also produce KerberosKey’s for the client to use.
I haven't tested this, but it would look something like this.
class KeytabCredential : KerberosCredential
{
    private readonly KeyTable keytab;

    public KeytabCredential(KeyTable keytab)
    {
        this.keytab = keytab;
    }

    public override KerberosKey CreateKey()
    {
        var principalName = new Entities.KrbPrincipalName() { Name = new[] { UserName } };

        if (!Salts?.Any() ?? false)
        {
            return keytab.GetKey(EncryptionType.NULL, principalName);
        }

        foreach (var salt in Salts)
        {
            var key = keytab.GetKey(salt.Key, principalName);

            if (key != null)
            {
                return key;
            }
        }

        return null;
    }
}


Set  GOMAXPROCS and GOMEMLIMIT using downward API

Test if setting GOMAXPROCS and GOMEMLIMIT impacts the benchmark results.
xref: https://github.com/fluxcd/source-controller/pull/1443

After running the benchmarks a couple of times, my conclusion is that is safe to add the env vars to the main distribution. There is no regression in terms of reconciliation speed.

Included in #6


fix Infinispan cache store handling

Fix for Infinispan cache store handling, adding a store requires the allow-resource-service-restart header (with the exception of file store but that seems to be a bug).
Also fixing the reload method, fetching selected profile fails in standalone mode.

Thanks for the fix @michpetrov. In general LGTM. I think I'll add a method to Operation.Builder to add arbitrary headers. Will have a closer look over the weekend and keep you posted.


invalid value for parameter "client_encoding": "utf8mb4"

Information

Version of Medoo: 2.1.8
Version of PHP: 8.0
Type of Database (MySQL, MSSQL, SQLite...): PostgreSQL
System (Liunx|Windows|Mac): Linux

Describe the Problem
A clear and concise description of what the problem is.
I'm using PostgreSQL version 14 and it was giving me invalid value for parameter "client_encoding": "utf8mb4"
Detail Code
The detail code you are using causes the problem.
// Write your PHP code here

Expected output
A clear and concise description of what output you expected.

Please remove the 'charset' => 'utf8mb4' or change it to utf8 from your database connection option.
It's an optional option.


Add support for getting all group conditions

fixes https://github.com/hawkular/hawkular-client-python/issues/24

@enoodle @cben @simon3z please review


Incompatability with Optifine's fast render option

With the "Fast Render" setting enabled on Optifine, the game loads and the HUD disappears. Opening player inventory or hitting escape doesn't display their respective GUIs (they still function though). Disabling fast render stops this, and Optifine doesn't seem to have any other issues.

perhaps it has something to do with Fast Render disabling FBOs? i don't think this mod is to blame for that, though

Was able to reproduce in early versions of Forge for 1.14.2, even without OptiFine. As of 1.14.4 there no longer seems to be any issue at all.


Configure Logging?

I’m really digging this tool for creating and configuring APIs. I consider setting up CloudWatch logging in-scope for this automation, but so far I haven’t found any reference to this in the examples or the code… am I missing something? If not, is this maybe on the roadmap? Come to think of it, is there a roadmap anywhere? Thanks!

To answer your specific questions, you aren't missing something. This tool doesn't support the CloudWatch logging setup operations. The CW Logs settings are on the stage settings which are applied outside of the actual API definition deployment, so it's debatable whether that fits in the scope of the tool. The tool does support doing a basic deployment with a stage name, as I'm sure you've noticed, so you could patch that code with additional parameters since the ApiGateway SDK under the hood supports all operations and settings and is easy to use.
In terms of roadmap, we don't have one publicly. I'll have to get back to you on adding a feature like this to the importer.

Thanks @jackrk for the thorough and thoughtful response!

I wrote a PR to provide this functionality. I haven't merged in any recent changes in a while from mainline. We're using my PR in production and have been for a while with no issues.
It made sense for us to add the code into the swagger-importer because the logic to parse the swagger file was already in place. The PR I had: https://github.com/awslabs/aws-apigateway-importer/pull/31

Thanks @cfair that seems perfect for @aviflax

Sure, no problem. The code was out there so I figured I'd point it out.
One note: the PR I have issued against this repo is missing a commit to make caching work. However, it is in my forked repo in the same branch where I issued the PR from. I also have an additional commit there to allow for the standard AWS credential provider chain, so we could use this on Jenkins.

Thanks @cfair that sounds very promising!
@jackrk any chance of some of the changes making their way into master?

Not in the near future. The feature set on master is pretty much locked, so only bug fixes. It's good to have input from customers on stage management as a part of this tool though!


Feature request: onChange event

Hi, actually we have onNextClick and onPrevClick, but if we want to add a callback for both we can't, except duplicating our code to run it twice. Can you please add onChange event? If you are ok, I can do it too, if it will be merged off course

This looks like it should exist in the application rather than the library. Can you please look at the configuration and see if you can use any other hooks; there are onHighlighted and onDeselected as well.


use nonegate to normalize how patterns work

The way we build patterns, a pattern that starts with !(thing) means "anything that's not thing".
However, if the same pattern is used for the top level (schema part with root as the parent),
then the final pattern becomes
!(thing)/.... Because the pattern starts with !, this means the entire pattern is negated.
By adding the option nonegate we disable this behavior, so !(thing) works the same way no matter which part of the schema it is used in.
This is the case that's affected:
schemas:
- id: not-example
  parent: root
  pattern: "!(example)"  # this will cause the entire pattern to be negated, rather than just this section meaning "not example"

Pull Request Checklist
If this is your first time submitting a pull request to Dendron, copy and paste the full Dendron Review Checklist into this request and check off each item as necessary.
This template contains the short checklist which is used by the Dendron core team.
Testing

[ ] Write Tests
[x] Confirm existing tests pass
[x] Confirm manual testing
[ ] If your tests changes an existing snapshot, make sure that snapshots are updated
[ ] If you are adding a new language feature (graphically visible in VS Code/preview/publishing), make sure that it is included in the test workspace

Docs

[ ] if your change reflects documentation changes, also submit a PR to dendron-site and mention the doc PR link in your current PR

Analytics

[ ] if you are adding analytics related changes, make sure the Telemetry docs are updated

@kevinslin Sure, here's an example (it's right under the example schema block): https://wiki.dendron.so/notes/c5e5adde-5459-409b-b34d-a0d75cbb1052/#pattern
The example for negation is at the bottom of that section, and looks like this:
"!(temp|scratch)" matches notes, recipes etc. but not temp or scratch, if you are trying to exclude just those hierarchies
So this can be used to exclude specific hierarchies. And to clarify, this PR is not enabling this functionality. The functionality is already enabled, there's just this edge case where if the topmost hierarchy's pattern begins with ! then the entire pattern gets negated and not just that level of the hierarchy.

@kevinslin Sure, here's an example (it's right under the example schema block): https://wiki.dendron.so/notes/c5e5adde-5459-409b-b34d-a0d75cbb1052/#pattern
The example for negation is at the bottom of that section, and looks like this: "!(temp|scratch)" matches notes, recipes etc. but not temp or scratch, if you are trying to exclude just those hierarchies
To clarify, this PR is not enabling this functionality. The functionality is already enabled, there's just this edge case where if the topmost hierarchy's pattern begins with ! then the entire pattern gets negated and not just that level of the hierarchy. This PR changes the options for minimatch so that doesn't happen.

Got it. Can we add a test for this?

Nevermind, while trying to write tests I found that the top level of the schema doesn't allow/respect patterns so you can't have this case anyway. I'm adding the tests anyway though because I don't think there are any schema tests that check if expected fnames match the schema.

Added the docs to [[Testing Schema Matches|dendron://dendron.docs/pkg.common-test-utils.ref.test-utils#testing-schema-matches]] and revised how it works. The common function just generates the tests now, and there's a local function in dnode.spec.ts that runs them. The run function also supports .skip and '.only` for convenience!


Latest payments not updating

There have been payments completed since the last ones shown on the homepage. It appears the list is not updating

perhaps we should consider showing all the different referal status here (not just paid)

The idea is to add that table to the homepage? Or add to the Latest Referral Payments table the Referral Payments columns?

This task seems to be duplicated to #294, however, this card describes a nice cool feature that could be added to the Proton Affiliate program. This new feature is described in #375


add cli option '--stop-on-failure'

:tada: This issue has been resolved in version 2.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[RFC] Replace HTTP/JSON with Downloads/JSON3

Here are some changes that I personally think might improve this package. The main part is the replacement of JSON with JSON3, which avoid building nested Dict when parsing the response body (and also result in a better display for OpenAIResponse in the REPL for free). The replacement of HTTP with Downloads stdlib is minor, depending on whether less dependency is preferable or not.

Love the generalized request generation. I don't have a strong opinion on Downloads vs HTTP, the former does seem more canonical since it's in the stdlib. I used HTTP by default, not knowing about Downloads.

HTTP would be more feature complete and handling the status more carefully than the manual way here with Downloads. But personally I think we probably don't need that much feature here (at least for now). Either way, the implementation can be easily modified for different request function.


Are cctab local or global?

Category code tables cctab, implemented in l3luatex (using luatex.sty under the hood) behave neither globally nor locally.  As far as I can tell, the catcode assignments are local, and the stack manipulations are global.
\RequirePackage{expl3}
\ExplSyntaxOn

\cctab_new:N \l_my_cctab
\cctab_gset:Nn \l_my_cctab { \char_set_catcode_other:n { `# } }

\cs_show:N # % Macro
\cctab_begin:N \l_my_cctab
{
  \cs_show:N # % Other
  \cctab_end:
  \cs_show:N # % Macro
}
\cs_show:N # % Other since catcode assignments are local
\cctab_end: % error since the stack was globally popped.

\tex_end:D

Both an all-local and an all-global versions can be used.  We can also be stricter, checking that the stack was popped in the same group as it was pushed, but I think this is overly constraining.
I'm in favor of an all-local version, which allows code such as
\DeclareDocumentEnvironment { verbatim } { } { \cctab_begin:N \l_verbatim_cctab } { }

with no explicit \cctab_end:.  Because of this kind of code, I'd like to rename \cctab_begin:N to \cctab_push:N, and \cctab_end: to \cctab_pop:, which would make the code above less odd.  Also, the names \cctab_begin:N and \cctab_end: seem to imply a group, but they don't actually introduce one.

We revisited the entire LuaTeX business a while ago and cut things back down to the minimum. Catcode tables got removed and for the moment are not present at all. Based on ongoing ideas in https://github.com/josephwright/ltluatex we may have a better catcode table stack available generally soon in any case.
At present there is nothing to do here so closing.


tests for "big" fetch_*() functions

We should test all fetch_*() functions/datasets (see #6 and PR #16 ). The "big" datasets have sizes > ~150 MB and download takes a long(ish) time.
We should find a way to mock-out the download or replace it with something tiny. It would nevertheless be good to ascertain that the download URLs are still valid (e.g. by download the first few bytes).

@richardjgowers I tentatively assigned you as the King of Mocks. I don't think that this is super-urgent but I wanted an open issue as a reminder (as opposed to a discussion on closed #6).

This has been addressed by marking most of the dataset fetch tests online: test with
pytest -m online

to run them.
Perhaps we can make this a cron job.


Shifter: New components window:

Folder organization and project component repository
drag and drop
duplicate component + edit in external editor
Guides templates tab
quick search

tags ?

This issue was moved to mgear-dev/mgear_dist#2


WIP: Fix first anchor scroll

Fixes an issue for anchor links
How to reproduce:
Open https://zksync.io/api/sdk/js/accounts.html#get-token-balance-on-ethereum (the current API)
Note that the page will not be open on Get token balance on ethereum, but somewhere at the beginning of the page
Open the PR's link: https://zksync-js-docs--pr91-fix-header-scroll-apz3zv57.web.app/api/sdk/js/accounts.html#get-token-balance-on-ethereum
For some reason the issue was fixed locally but not here.

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


Bug/Error: Cannot Pair wtih Moonlight app (key not found)

Followed the instructions here (docker run): https://games-on-whales.github.io/wolf/stable/user/quickstart.html
When attempting connect a Moonlight client, I successfully get the webpage to input the key and receive the following error:

Thanks for checking out Wolf!
Have you removed the #... part of the URL by any chance? That's a temporary key needed in order to avoid anyone to be able to pair with the instance.

So the url would look like this: http://x.x.x.x:47989/pin/ ?
If that is the case, I did try that and got the same error message

Wolf will log a line with a full URL everytime that you try to pair, example: http://localhost:47989/pin/#337327E8A6FC0C66
You need to put the full URL with the additional #... in the address bar in order to successfully pair.

Wolf will log a line with a full URL everytime that you try to pair, example: http://localhost:47989/pin/#337327E8A6FC0C66
You need to put the full URL with the additional #... in the address bar in order to successfully pair.

That did work! Guess it helps if I fully read....


Custom objects get double escaped when adjusted.

The output of /version on my server is: git-Paper-134 (MC: 1.16.1) (Implementing API version 1.16.1-R0.1-SNAPSHOT)
The output of /version denizen on my server is: Denizen version 1.1.5-SNAPSHOT (build 1714-REL)
Script demonstrating the issue: https://one.denizenscript.com/haste/74462
The issue is:
The "adjust" command does not fully unescape the custom object before applying new values, resulting in existing values becoming double-escaped.
Expected output:

custom@TEST[first=13&dot37;second=0]
custom@TEST[first=13&dot37;second=11&dot55]

Actual result:

custom@TEST[first=13&dot37;second=0]
custom@TEST[first=13&ampdot37;second=11&dot55]

Support is on Discord: https://discord.gg/Q6pZGSR


C# receive  increpted masseges

Any solutions

Please check the changelog, it seems the collaborators are already working on it, they made some changes 9 days ago.
PHP is already having solutions for it, but it seems C# is bit more time consuming for them :)


Fix case where ~/.ssh/id_rsa.pub is a softlink

Some users may have the default id_rsa/id_rsa.pub be a softlink to one
of a set of rsa keys. In this case, the cp would result in a dangling
softlink in the container and the startup fails. Adding a -L to the cp
command results in copying whatever the softlink points to into the
container, which seems like the desired behaviour.
Signed-off-by: brian avery<EMAIL_ADDRESS>

Good catch,
Thanks.


Hardware verification

[x] Test library on real hardware.
[x] Sensor Responds to address 0x38?
[ ] Sensor driver allows reading of temp?
[ ] Sensor Driver allows reading of humidity?
[ ] Verify register's from datasheet v1.1 are accurate.

Have setup and tested it with a i2c address querying program I wrote on the stm32f103c8. Also logged the SDA/SCL wires with my logic analyzer.


Documentation improvement CHAINERX_ENABLE_{BLAS,LAPACK}

Fixes https://github.com/chainer/chainer/issues/8041.
Also improves related existing documentation.

Changed the documentation to more accurately reflect the current behavior and be less general. PTAL.

Thanks for the comments! I tried replying to them.

PTAL.

Comments are addressed, PTAL.

imosCI, please test this.


[BP-596] Payment pending and canceled issue with PayPal

Hello,
We are using the module version 1.24.0 with Magento Commerce 2.3.3 with a multistore setup. We are currently experiencing two issues with PayPal with this module.

When selecting success in the buckroo system the redirect back to Magento happens but the order is not correctly linked back to the currently logged in user. The success page does not include a link to the order as expected with logged in user and the order does not appear in the user's order section (though it does appear in the admin attached to this user),
When selecting any failure the redirect to the cart does not work and we get caught in a loop and the cart is not rebuilt correctly and the user never gets back to the checkout page.

@dmanners  Thank you for the information. We will try to research this a.s.a.p.

It seems to be an issue with the way quotes are recreated and the enterprise module magento/module-checkout-staging.
This module will die when it tries to save the quote id as it is already in its database table.
        if ($this->versionManager->isPreviewVersion() && $quote->getId()) {
            /** @var PreviewQuota $previewQuota */
            $previewQuota = $this->previewQuotaFactory->create();
            $previewQuota->setId($quote->getId());

            $this->previewQuotaRepository->save($previewQuota);
        }

After removing this plugin the recreation of the quote is working again. I wonder if there is a way rather than recreate the old quote with the same ID but to recreate this in a new quote object each time.

Unfortunately we are currently unable to reproduce this issue. Can you please contact our support team ><EMAIL_ADDRESS>with all the information, some staging actions and steps to reproduce this? Thanks you in advance.

Ticket closed, issue is being researched true our standard support channels.

Ticket closed, issue is being researched true our standard support channels.


RegEx class documented.

RegEx class has been documented. In the future I'd like to alter (again) the help viewer to show descriptions for the methd's parameters.

I recall that @reduz said to don't bother writing documentation for arguments for they don't show in the editor help. I'm not sure if he has some plans regarding this issue.

I'd say so! It shouldn't be much trouble to make parameters appear in the
editor help. Maybe I should implement it (along with other enhancements).

Nice! I should add that there is an update to the regex that hasn't been merged yet. https://github.com/godotengine/godot/pull/2642

Well, I'll have to update the docs when it gets merged. I hope it gets merged, it adds a ton of sexy functionality to the regex.

Changes look good, I'm not sure either if the argument documentation will be kept by the parser or it will be discarded, we'll see.

@Ovnuniarchos As I feared, Godot's doctool discards the return and argument descriptions when they exist, i.e.: ./bin/godot.x11.tools.64 -doctool doc/base/classes.xml currently generates this diff: http://hastebin.com/ugumodoxuj.xml
So I guess for the time being it's best that we stick to documenting the necessary argument ranges in the main function description. Same for the return value (though there is often little interest to documenting the return value specifically, as it's usually exactly what the main function description does).

It's time to correct these docs, then.
On Sat, Nov 7, 2015 at 1:40 PM, Rémi Verschelde<EMAIL_ADDRESS>wrote:

@Ovnuniarchos https://github.com/Ovnuniarchos As I feared, Godot's
doctool discards the return and argument descriptions when they exist,
i.e.: ./bin/godot.x11.tools.64 -doctool doc/base/classes.xml currently
generates this diff: http://hastebin.com/ugumodoxuj.xml
So I guess for the time being it's best that we stick to documenting the
necessary argument ranges in the main function description. Same for the
return value (though there is often little interest to documenting the
return value specifically, as it's usually exactly what the main function
description does).
—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/pull/2727#issuecomment-154697352.


wip: feat/eth gateway

Description
WIP
Metadata
Fixes

Fixes # [Link to Issue]

Contributing Agreement

[ ] I have read and understood the Optimism Contributing Guide and Code of Conduct and am following those guidelines in this pull request.

@ben-chain is this deprecated now?

Yes, this was refactored in https://github.com/ethereum-optimism/integration-tests/pull/47


itest: add bitcoind test without txindex enabled

Fixes #1948.
Adds a secondary bitcoind integration test that runs without the -txindex flag set on the chain backend.

Changes LGTM, was the build intentionally canceled?

Haha, thanks for the reviews! I was still trying things out with this. I canceled the build because I made a mistake with the build flags, the btcd tests failed.
I'm not sure we can keep things as they are right now. Because Travis will only start 5 of the 6 tests in parallel. So this could end up taking more than an hour if the last test is only run after another is completed.

Haha, thanks for the reviews! I was still trying things out with this. I canceled the build because I made a mistake with the build flags, the btcd tests failed.
I'm not sure we can keep things as they are right now. Because Travis will only start 5 of the 6 tests in parallel. So this could end up taking more than an hour if the last test is only run after another is completed.

Can we up our travis quota?

I'm not sure we can keep things as they are right now. Because Travis will only start 5 of the 6 tests in parallel. So this could end up taking more than an hour if the last test is only run after another is completed.

I think for now we should proceed with or without the bump in travis jobs. Maybe that will act as a forcing function...
Needs a rebase!!

Rebased.

Doesn't compile?

Oops, fixed.


SCB-829 An index on TxEvent (globalTxId) should be added

https://issues.apache.org/jira/browse/SCB-829

Coverage increased (+0.04%) to 94.379% when pulling b6d0fe4795144ae4878252db7aa800dcd591bc5a on oliugian:master into 8fbf4ac64b9defe0bf40e06bf57123e4e42896bf on apache:master.


Log all searched locations for non existance resources

From @hishamco on Friday, March 3, 2017 10:39:54 PM
After the PR #331, me as a developer I expect to log all searched locations for non-exist localization resources
Assume that I add the culture ar, with enabling parent culture fallback, so when the current culture is ar-YE I except the logger logs:
searched for 'Hello' in 'LocalizationSample.Startup' with culture 'ar-YE'.
searched for 'Hello' in 'LocalizationSample.Startup' with culture 'ar'.

instead of log the first message after fallback
/cc @ryanbrandenburg @pranavkm
Copied from original issue: aspnet/Localization#336

Closing this issue as there was no community involvement for quite a while now.

@mkArtakMSFT I was waiting for the AspNetCore team to respond to me for what I suggested before?!!

Still I believe there is a value for such feature, especially in debugging. BTW what I suggested is similar what MVC is doing if the view that's looking for is not found


Support custom component types via CLI

Ref: #5501
Hey @mattsse ,
I managed to get a first WIP PR up.
Would you mind taking a look?
Thanks!

just to give an update, we're preparing to support this via
#5938
and
#5932


PackageName compatibility with Tauri 2 beta

Forgive me if any of my terminology is off, I'm pretty new to rust...
In Tauri 2.x, the config file appears to have changed. For this issue, the notable change is that productName is now a top-level item instead of being nested underneath package.
This results in the following error when the action tries to locate the artifacts if a productName is set in tauri.conf.json. Note that the action is looking for a file named tortoise-native* when it should be looking for The Tortoise*
In this case, my crate is named tortoise-native and my productName is The Tortoise.
...
    Finished 2 bundles at:
        /Users/<USERNAME>/code/actions-runner/_work/tortoise-native/tortoise-native/src-tauri/target/universal-apple-darwin/release/bundle/macos/The Tortoise.app
        /Users/<USERNAME>/code/actions-runner/_work/tortoise-native/tortoise-native/src-tauri/target/universal-apple-darwin/release/bundle/dmg/The Tortoise_0.7.0_universal.dmg
Looking for artifacts in:
/Users/<USERNAME>/code/actions-runner/_work/tortoise-native/tortoise-native/src-tauri/target/universal-apple-darwin/release/bundle/dmg/tortoise-native_0.7.0_universal.dmg
/Users/<USERNAME>/code/actions-runner/_work/tortoise-native/tortoise-native/src-tauri/target/universal-apple-darwin/release/bundle/macos/tortoise-native.app
/Users/<USERNAME>/code/actions-runner/_work/tortoise-native/tortoise-native/src-tauri/target/universal-apple-darwin/release/bundle/macos/tortoise-native.app.tar.gz
/Users/<USERNAME>/code/actions-runner/_work/tortoise-native/tortoise-native/src-tauri/target/universal-apple-darwin/release/bundle/macos/tortoise-native.app.tar.gz.sig

This seems to be the code of interest:
https://github.com/tauri-apps/tauri-action/blob/4bb1df96ee90cc64b4315bfaf82f4fe70d9d521e/src/utils.ts#L281-L289
I'm not sure what your plans are for 2.x support, but one easy way to address this particular issue would be to add  an additional if to cover this case. Specifically, check the top level of config for productName (and likely other variables as well).
I'm happy to make a PR, but wanted to check before I went ahead with anything.

Hi, thanks for reaching out. There's already a PR from another community manager. I meant to finish it up yesterday but there was an emergency. I hope I can do it today or tomorrow, sorry for the inconvenience.

Oh great, thanks!

Just fyi, i am completely offline over the weekend so i will wait with the release until sunday/monday (in case i broke something). If you can't wait so long please use tauri-apps/tauri-action@dev or tauri-apps/tauri-action@81921ba9d3c8163235d21b262dd0c3ad3fb19029 until then.


Mostly whitespace/syntax cleanup

One or two actual changes to code, but no operational changes.

It is great. But this:
-my $total-found = [+] %found.values.map( *.elems );
+my $total-found = %found.values.map( +* ).sum;

is more like code obfuscation. .sum is fine, but +* instead of *.elems is probably not a good idea. I think that it is worth changing it back to *.elems.

Yeah. I think I was trying to make it consistent with the rest of the code, but it looks like a roughly even split between +<array_goes_here> and <array_goes_here>.elems. Feel free to make that change, unless you'd rather I do it?

Rather you do it :) The documentation may be perused by novices so it's best to avoid clever code, even if it is more concise.

That was ugly, but things seem ok now.

Thanks!


Support build with Pelles C

Pelles C runs well on wine: http://www.smorgasbordet.com/pellesc/

I use GCC extensions so this would not be possible.

I use GCC extensions so this would not be possible.

Pelles C supports some GCC extensions with the /Zx option.

Yeah but it's not really necessary since you can just use MinGW or MSYS2.

Plus I use GNU make for the build system. If you look in the makefiles, you can see that it's pretty specialized and IMO, it's not really worth rewriting the build system when there's no reason to.

Plus I use GNU make for the build system. If you look in the makefiles, you can see that it's pretty specialized and IMO, it's not really worth rewriting the build system when there's no reason to.

Pelles C command line utilities could be used with make too. The same way people using MSVC cl.exe with make.

Yeah but it's not really necessary since you can just use MinGW or MSYS2.

Yeah I understand :smile:


updated navbar with profile and logout

updated navbar with dropdown profile

Its looks good for me and the dropdown menu is a pretty good option.


Prioritize search results based on usage

With the new search-to-add workflow, producing highly relevant search results is even more important than before. I've come across many instances where a very common preset is annoyingly below less-common presets. We should factor taginfo usage into our search algorithm.
Service Road should be first:

Foot Path isn't even shown:

@quincylvania
Taginfo seems to be useful to prioritize presets which match to the same extend, but
I think we should avoid to prioritize more frequent ones over better matching ones.

Yep this relates to #2000.. We've known for a while that  "unmodified Levenshtein distance is probably not the best metric here."  I closed it years ago because nobody seemed interested in digging in to improve the algorithm.
I'm also reluctant to give too much weight to taginfo popularity, but I agree it would be useful as another thing to consider in the weight.  We'd need to calculate these in at build-time to do it perfectly, or it might be ok to just do a few taginfo queries when the user's editing session starts to get the most popular things, and give them a slight boost.
Also worth mentioning - you picked "Service" as an example, which might be one of the worst cases because that tag is used for several different things in OSM.
And it doesn't seem that weird that all the top results for "foo" are "food".

Is this an issue that could have the help wanted label?

We'd need to calculate these in at build-time to do it perfectly

I think it would be fine to bake some rankings (hopefully compressed somehow) into the build. If a tag suddenly and dramatically gains in popularity, it’d be fine for iD’s preset search results to lag that by a month or two. IDEs and IMEs similarly bundle some rudimentary weighting statistics into the build.
Interesting to think about brand presets being weighted based on usage, since I think iD already gets those statistics from NSI.

Is this an issue that could have the help wanted label?

@TAQ2 Not necessarily. We don't use that label too often but mostly it's for stuff we don't know how to do or don't want to spend core time on.


fix issue #83: can't handle problem with Multiline  value comment

the description of #83
this PR can handle problem with Multiline value  comment.

@ndevilla, please take a look ,thank you :)

@hityc2019 thank you for the effort. However, as explained in https://github.com/ndevilla/iniparser/issues/83#issuecomment-2016875658 issue #83 is expected behavior.


optimize: support jmx port in seata

[x] I have registered the PR changes.

Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?
fixes #5269
Ⅲ. Why don't you add test cases (unit test/integration test)?

Ⅳ. Describe how to verify it

export JMX_ENABLE=true
run in local machine, check the opts

Ⅴ. Special notes for reviews

I don't think any feature that isn't part of a transaction should be claimed as a feature

ok, thanks for your advice, I have changed commit message and title

LGTM Please register pr and author information to https://github.com/seata/seata/blob/2.x/changes/zh-cn/2.0.0.md https://github.com/seata/seata/blob/2.x/changes/en-us/2.0.0.md and synchronize the changes to the develop branch.

ok

You also need to register the githubid in 2.0.0.md

done


RT tickets?

Are you aware of the RT tickets, especially https://rt.cpan.org/Ticket/Display.html?id=118518 ?

I am aware of them and I appreciate you taking the time to open them. I
have not had a chance to dig down into them. I will probably address them
over the holidays by the end of the year.
If you would like them addressed sooner, I'm more than happy to accept PRs
if you're interested in submitting one. Otherwise, it will be another 3-6
weeks before I have the personal bandwidth.
On Wed, Nov 9, 2016 at 2:12 PM, Slaven Rezić<EMAIL_ADDRESS>wrote:

Are you aware of the RT tickets, especially https://rt.cpan.org/Ticket/
Display.html?id=118518 ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/robkinyon/dbix-class-sims/issues/25, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AACUMQiAGli04uialDU9ZcR-Dmrr3W9sks5q8hskgaJpZM4Kt4au
.

--
Thanks,
Rob Kinyon
http://greenfishbluefish.com/

OK, I just asked because some users don't get RT mail notifications, and I saw the same test failure I already reported for the previous version.


logging/console: uart: runtime power management

Handle runtime power management for the UART backends of the logging and console APIs.
This lets the logging and console backends continue to operate normally after power management is enabled on the UART backend.

By default, the buffer in the UART log backend is 1 byte. This means that for every single byte, it has to go through wake up -> send one byte -> sleep. That's just too much overhead. I think a better approach is to introduce some type of backend PM actions where the main log processing loop would get/put device PM as needed.

By default, the buffer in the UART log backend is 1 byte. This means that for every single byte, it has to go through wake up -> send one byte -> sleep. That's just too much overhead. I think a better approach is to introduce some type of backend PM actions where the main log processing loop would get/put device PM as needed.

You could make the same argument about LOG_BACKEND_UART_ASYNC, using that byte by byte is rather inefficient.
That's why LOG_BACKEND_UART_BUFFER_SIZE was introduced.
It is certainly possible to update the log backend API with some power management functionality and call it around cbvprintf, but that's a more invasive change that what is proposed here.

setting DNM so I have time to review (will do soon)

@JordanYates can you review the pattern pm_device_runtime_enabled() -> pm_device_runtime_get() ?

I agree the behaviour is equivalent without pm_device_runtime_enabled(). There is a non-trivial amount of code (especially in _put) that can be shortcut with this check however. If we leave it around _put I would also leave it around _get to keep things symmetrical.
So the question is whether the optimising is worth it or not, which I am happy to take advice on.

So the question is whether the optimising is worth it or not, which I am happy to take advice on.

 Can't pm_device_runtime_enabled be moved inside the get / put functions?

@JordanYates can you review the pattern pm_device_runtime_enabled() -> pm_device_runtime_get() ?

I agree the behaviour is equivalent without pm_device_runtime_enabled(). There is a non-trivial amount of code (especially in _put) that can be shortcut with this check however. If we leave it around _put I would also leave it around _get to keep things symmetrical.
So the question is whether the optimising is worth it or not, which I am happy to take advice on.

I'd remove it from both, we should address the problem in get / put moving the check to the beginning of the function.
I'll prepare a pr for that. But for this one I'd remove the enabled checking in both situations since it does not change the behavior

So the question is whether the optimising is worth it or not, which I am happy to take advice on.

 Can't pm_device_runtime_enabled be moved inside the get / put functions?

These functions check for it, but not exactly in the beginning, I'll move around where the check is done. But, a simple answer is, they already check.

https://github.com/zephyrproject-rtos/zephyr/pull/55237

That PR highlighted a problem with dropping pm_device_runtime_is_enabled. If it isn't enabled, _get will return immediately, but _put will attempt to release a power domain, even though it was never taken by _get.

#55237

@ceolin merged

That PR highlighted a problem with dropping pm_device_runtime_is_enabled. If it isn't enabled, _get will return immediately, but _put will attempt to release a power domain, even though it was never taken by _get.

All right .. I'm removing my -1 for this change and lets revisit device_runtime_put behavior.


Axis handle Vapix error messages

Breaking Change:

Description:
Small improvement to handle Vapix errors identified by beta users.
Related issue (if applicable): fixes #
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[x] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

@balloob will you add this for the next beta?

yes, as it's been tagged for the milestone 👍

Just upgraded to 0.94, I'm getting these errors for the newer Axis cameras:

Error: Error -1 getting param in group 'root.IOPort'

from <IP_ADDRESS>

Please open an issue.