How to send local images in microsoft botframework sdk v4 using c#??

This is not for asking questions or filing bugs
To get help with an issue with your bot

"How To" questions should be submitted on Stack Overflow where there is a robust community to help you

To file an issue against a component please go to the components repo

Create Azure Bot Framework Service or Channel issue
Create Bot Builder Tools issue
Create Bot Builder SDK V3 (.NET or Javascript) issue
Create Bot Builder SDK V4 .NET issue
Create Bot Builder SDK V4 Javascript issue
Create Bot Builder SDK V4 Java issue
Create Bot Builder SDK V4 Python issue

Can you show me the code you're using for attachments? Or are you using the sample code unedited?

https://github.com/Microsoft/BotBuilder-Samples/blob/master/samples/csharp_dotnetcore/15.handling-attachments/AttachmentsBot.cs
I am using  handling attachments sample from github

Just for further clarification: you're attempting to attach a file (such as a picture) from your computer to the bot, using emulator?

I want to send the image  in Base64  format  which is saved in my  computer to bot using C#.

Hi @MounikaPedapati
While researching this issue, I came across your question on Stack Overflow here. The person answering your question there is a member of the Bot Framework Support team, and will be able to further assist you. I'm going to close this issue so you can be better assisted over there.


Add some description for each operator

Hey! RxMarbles is great! I'm learning a lot with it... But for beginners (like me) it's hard to deduce what each operator does... I have to look at the diagram, play a little bit, and than I start to understand what each of them really does...
It's just an opinion, but what you think of adding a simple and easy to understand description to each operator? Like in the Scan operator:
Scan
Does some crazy stuff with x and y, where x is the current value and y is the previous value.
[PLAYABLE DIAGRAM]
I know it's a dumb example, but I think you got the idea :)

I don't want to replicate what we are doing at ReactiveX.io, check out this http://reactivex.io/documentation/operators/scan.html
The plan is to build RxMarbles to such a state that it will be embedded in the docs page in ReactiveX.io, and the latter is the official guide on the operator. RxMarbles would then be just a cheatsheet for quick checks.

@mauriciosoares I am using RxMarbles with my RxBook. You can look on this page http://xgrommx.github.io/rx-book/content/observable/observable_instance_methods/map.html

@staltz, that makes sense...
@xgrommx, thanks for the link! It's what I wanted, a simple description with some code samples... I'll totally take a look at it.
Thanks guys.


Bad docker image

pREST version (or commit ref): v0.3.4
pREST endpoint: -
PostgreSQL version: PostgreSQL 11.1
Operating system: x86_64-pc-linux-gnu
Go version: 1.11.5
Log gist: -

Description
The container prest/prest:v0.3.4 fails to start:
> docker run -e PREST_HTTP_PORT=3000 -e PREST_PG_HOST=<IP_ADDRESS> -e PREST_PG_USER=postgres -e PREST_PG_PASS=pass prest/prest:v0.3.4

standard_init_linux.go:207: exec user process caused "no such file or directory"

Same behaviour for tags v0.3.3, v0.3.2 and v0.3.1. Only the tag latest (which is older than the previous ones) works.

You need to install glibc in the Docker container

@tsmethurst Oh, yes, that's right. thanks!
To fix that, I've just symlinked libraries musl to glibc (as they are compatible), and it worked!
FROM alpine:3.7

RUN mkdir /lib64 && ln -s /lib/libc.musl-x86_64.so.1 /lib64/ld-linux-x86-64.so.2

COPY prest /prest

CMD ["/prest"]

Is there any plan to make the Docker image with tag latest to be the latest version on the repo?

You need to install glibc in the Docker container

@tsmethurst Could you tell me how to do that using the current Dockerfile, please? Thank you for your help!

@airjulio
How I do it in my Dockerfiles:
RUN wget -q -O /etc/apk/keys/sgerrand.rsa.pub https://alpine-pkgs.sgerrand.com/sgerrand.rsa.pub && \
    wget https://github.com/sgerrand/alpine-pkg-glibc/releases/download/2.29-r0/glibc-2.29-r0.apk && \
    apk add glibc-2.29-r0.apk && rm glibc-2.29-r0.apk /etc/apk/keys/sgerrand.rsa.pub

Fixed


Create rabinkarp.cpp

Next time open a issue before adding a pull request, or the PR will be marked as Invalid.
Read the Contributing guidelines for more details.

Next time open a issue before adding a pull request, or the PR will be marked as Invalid.
Read the Contributing guidelines for more details.

Really sorry about that would remember this next Hacktoberfest.


New module: globstar + ignores

ag and editorconfig aren't quite what I'm looking for.

Ability to traverse virtual (no readdir()) trees
Ability to turn ignores on and off

[ ] Clean up and merge branch globstar2.  I have squashed it, but not yet deduped it against main or updated the commit messages.

As of present, I can glob disk files.  Ignores are next to test.


Revert accidental removal

It fixes issue noticed by @gemantzu
in https://github.com/doomspork/elixir-school/pull/1120#issuecomment-309235263

Thank you @eksperimental 😀


Update old link & add related topic from UWP docs.

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


Suggestion: overflow(-[xy])? with 'overlay' value

Just found that at least Chrome and Safari of 2016 supported this undocumented value, which is not listed in W3C documents.
Not sure if support is dropped, but Chrome dev mode suggests the 'overlay' value for overflow-y.
Can't find it at the caniuse.com, please add. TY in advance )

Now available at https://caniuse.com/css-overflow-overlay


Remove "ndk/"-prefixed include path compatibility workarounds

With the way that the native version of android_ndk_repository structured / symlinked the NDK into bazel's external repository directory, the way to include things like cpu-features was
#include "ndk/sources/android/cpufeatures/cpu-features.h"

With the way the Starlark version of android_ndk_repository structures the NDK symlinks, the ndk/ prefix is not needed:
#include "sources/android/cpufeatures/cpu-features.h"

However this presents a migration issue for projects that use the native version of the rule, so a workaround was introduced to allow including the headers with the ndk/ prefix (by adding another symlink that results in the previous include path). We should migrate projects and remove this workaround.

IMO, better to go a step further and migrate people to https://github.com/google/cpu_features. The only reason the NDK still ships its own is because we don't want to break existing builds that depend on it. If someone needs to put in effort to migrate, they might as well migrate to the new thing that's actually maintained (there's even an interface that's compatible with the old NDK one for use as a drop-in replacement: https://github.com/google/cpu_features/tree/main/ndk_compat)

I wasn't aware of the separate cpu_features project -- I'll add a note about this!
For now, some users are blocked from moving to the starlark version of android_ndk_repository because other projects aren't migrated to either  https://github.com/google/cpu_features or non-ndk/-prefixed include paths (this is all pretty new so they're probably not even aware, and I'm sure we'll uncover other migration issues).


⚠ Bofrost.de has degraded performance

In 011b159, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 736 ms

Resolved: Bofrost.de performance has improved in fa1e194 after 6 minutes.


Improve tf_compile to allow emitting HLO module instead of/in addition to executable

Currently tf_compile (tensorflow/compiler/aot) always emits executable. But there are use cases where dumping HLO module is more desired. This is a tracking bug to implement it.

@gmagogsfm While XLA Flags not directly supported by tf_compile, you can leverage XLA flags like --xla_generate_hlo_text_to=<output_dir> during tf.function tracing or conversion. This allows generating HLO text files, but might require additional steps to integrate with tf_compile.
Thank you!


Is it possible to support 5-dim or x-dim data operation

Presently, we are use 4-dim data flow to build most of our models, BatchSize x W x H x Channels or BatchSize x Channels x H x W.
Is it possible to build 5-dim data flow? Maybe BatchSize x Capsule x W x H x Channels, which should be useful in ideas like CapsNet for that we don't have to reshape out data. So we can build high dimensions models which are more complicated and should be better both in structure and data extraction performance.
According to MobileNetV2, performance of relu  is better in high dimensions than in low dimensions. So it maybe even more better if we can build our entire model with high dimensions operations.
Further more, how about 6-dim or 7-dim operations, even x-dim operations?
Is this kind of operations possible? If possible, how hard will it be to implement them?

5 dim version is ok. I already implemented Capsule with MxNet. You can refer to mine. But printting ndarray of high dim is not supported. Gluon is very friendly if you want to have a try.

@dwSun Please use discuss.mxnet.io forum for usability questions like this to get quicker answer and get a larger audience involved.
@sandeep-krishnamurthy Can you add label

Question and close the issue


Enables saml setting to be overridden

Summary

Previously , saml settings were not configured to be overridden , it would enable saml settings to be overridden.
Ticket Link

Fixes https://github.com/mattermost/mattermost-server/issues/382

Hello @KhizerJaan,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.
Per the Mattermost Contribution Guide, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
Once you have signed the CLA, please comment with /check-cla and confirm that the CLA check is green.
This is a standard procedure for many open source projects.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

/check-cla

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

@KhizerJaan the config.tpl doesnt apply to the deployment unless you add the config into a volumemount and volume
since its a Kubernetes installation, the configuration is stored in the database and the whole point of the config file is irrelavent
if you see in the code you can see the config map is only applied to the load test and not the application it self
hope this helps


Timed traffic doesn't skip to next step even after max time

Describe the problem
I set up timed traffic for one of my intersections with a minimum time of 5 seconds and a max time of 10 seconds. When it's supposed to move on to the next step by the 10-second mark, the timer resets and it stays in the same step.
Steps to reproduce

Set up timed traffic on an intersection with multiple steps
Set a minimum and max time
Start timed traffic

Log files
TPME log: https://ufile.io/at0mxgo4
Video
https://streamable.com/kvzpz2
If you look at the Timed Traffic Lights Manager, you'll see that it resets the moment the max time runs out.

Version 11.3.2, Build <IP_ADDRESS>644 STABLE for game version 1.13.0-f8

Could you confirm that you didn't tick the box that disables step changes? I expect you haven't ticked it, but I'd like to be sure first.

Above error was already patched, but version (v.11.5.0) was not released yet.

The last two PRs for v11.5.0 are approved I think so we are close to release

Tagging #861 , #880

Fixed in v11.5.0 LABS

Fixed in v11.5.0 LABS

Just gave it a try again in LABS and it still doesn't work. Do I need to delete my timed traffic settings for it to work?

Please share updated log files (output_log.txt and TMPE.log)

Closing due to inactivity. Reopen or create new issue if problem still exist


[SPARK-50134][SPARK-50132][SQL][CONNECT][PYTHON] Support DataFrame API for Lateral Join in Spark Connect

What changes were proposed in this pull request?
Supports DataFrame API for Lateral Join in Spark Connect.
Why are the changes needed?
DataFrame API for Lateral Join is missing in Spark Connect.
Does this PR introduce any user-facing change?
Yes, Lateral Join will be available in Spark Connect.
How was this patch tested?
Added the related tests.
Was this patch authored or co-authored using generative AI tooling?
No.

The remaining test failures are not related to this PR.

Thanks! merging to master.


Setup.sh - Storage account name already taken prevents project setup

When setting up the solution with setup.sh, there is an error for storage account name conflict. Error message included below.
{"status":"Failed","error":{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"Conflict","message":"{\r\n  "status": "Failed",\r\n  "error": {\r\n    "code": "ResourceDeploymentFailure",\r\n    "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n    "details": [\r\n      {\r\n        "code": "DeploymentFailed",\r\n        "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",\r\n        "details": [\r\n          {\r\n            "code": "Conflict",\r\n            "message": "{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n    \"details\": [\r\n      {\r\n        \"code\": \"DeploymentFailed\",\r\n        \"message\": \"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.\",\r\n        \"details\": [\r\n          {\r\n            \"code\": \"Conflict\",\r\n            \"message\": \"{\\r\\n  \\\"status\\\": \\\"Failed\\\",\\r\\n  \\\"error\\\": {\\r\\n    \\\"code\\\": \\\"ResourceDeploymentFailure\\\",\\r\\n    \\\"message\\\": \\\"The resource operation completed with terminal provisioning state 'Failed'.\\\",\\r\\n    \\\"details\\\": [\\r\\n      {\\r\\n        \\\"code\\\": \\\"DeploymentFailed\\\",\\r\\n        \\\"message\\\": \\\"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.\\\",\\r\\n        \\\"details\\\": [\\r\\n          {\\r\\n            \\\"code\\\": \\\"Conflict\\\",\\r\\n            \\\"message\\\": \\\"{\\\\r\\\\n  \\\\\\\"error\\\\\\\": {\\\\r\\\\n    \\\\\\\"code\\\\\\\": \\\\\\\"StorageAccountAlreadyTaken\\\\\\\",\\\\r\\\\n    \\\\\\\"message\\\\\\\": \\\\\\\"The storage account named synhnsrqjhqd is already taken.\\\\\\\"\\\\r\\\\n  }\\\\r\\\\n}\\\"\\r\\n          }\\r\\n        ]\\r\\n      }\\r\\n    ]\\r\\n  }\\r\\n}\"\r\n          }\r\n        ]\r\n      }\r\n    ]\r\n  }\r\n}"\r\n          }\r\n        ]\r\n      }\r\n    ]\r\n  }\r\n}"}]}}

After some investigation of the .bicep files, found the following in data.bicep, which drives me think that the dataresourcegroup name shall be named in more unique manner
var dataResourceGroupNameVar = empty(dataResourceGroupName) ? '${namingPrefix}-rg' : dataResourceGroupName
var nameSuffix = substring(uniqueString(dataResourceGroupNameVar), 0, 6)
var keyvaultNameVar = empty(keyvaultName) ? '${namingPrefix}-kv' : keyvaultName
var rawDataStorageAccountNameVar = empty(rawDataStorageAccountName) ? 'rawdata${nameSuffix}' : rawDataStorageAccountName

I am curious about how 'synhnsrqjhqd' storage account is referenced, looking at your error. Did bicep create and reference it when you re-run?  Do you see the storage account is in your data resource group? What resources do you see in the data resource group? what makes you think the resource group name is the root cause of this issue when it complains about the existing storage account name? We expect the first parameter to be unique so that it derives unique resource names.
Would you describe how we reproduce your issue from our end to help you? Thank you.

Check https://github.com/Azure/Azure-Orbital-Analytics-Samples/blob/main/deploy/README.md
The code above seems to use it to generate a hash on the first 6 characters of dataResourceGroupNameVar, so if it happens that I have selected a value which begins the same way as someone else's variable value, this would lead to that duplication conflict.
In main.bicep it seems to be initialized as:
Line 50: var dataResourceGroupName = '${environmentCode}-${dataModulePrefix}-rg'
In my case I used "orb" as environmentCode. I afterwards changed it to "orbivo" - including my name in it gave me more uniqueness. In short - the generation of naming is not sufficiently unique and I spent about 1h reading through the bicep files.

Two more things (intentionally in a separate comment), but I believe the resolution approach could be similar.

All the instructions were to use WestUS region for Azure Orbital setup, so I did that here too. However I am based in Europe and my subscription was not allowed to create SQL Server resource in WestUS regions - probably legal stuff, I was not aware of, but a fact. That lead to additional deployment failures, but due to SQL server and not due to errors in the present project deployment approach.
The failure above made me try another region and it worked, but failed the first time due to Synapse deployment duplication.  As I left all other parameters the same, except for the region, the synapse deployment failed as the deployment name was duplicate. In both cases above some suffix generated from the current date should be helpful.

Suggestion - use utcNow function to generate a suffix and help more unique naming.
Challenge - this may severely affect the cleanup as some of the names will not be predictable and the user would have to provide an extra parameter from which the suffix could be extracted
My expectations are that the issue above would be encountered by people predictably setting environmentcode to things like "orbit" or "orbital"

We don't know what resource quota and resource regional constraint customer's subscription/product would have and thus we expect customers to choose the different regions accordingly. The instructions we showed in Readme are examples.
Using utcNow function to create a resource group & resource names is not good idea, either. This will break the idempotency requirement. Rerunning the template with the same parameters would result in creating a new resource groups and resources instead of updating the existing infra.
Going back to my original question, you pass orb initially and you get 'synhnsrqjhqd' as a storage account name, and it failed?

I see synhns* storage account in *-pipeline-rg. I think we need to randomize that storage account name in *-pipeline-rg.

Going back to my original question, you pass orb initially and you get 'synhnsrqjhqd' as a storage account name, and it failed?
I believe exactly that was the cause and renaming from "orb" to "orbivo" was enough to solve it, although (as said before) I had to read through a bunch of bicep files to find what to do.

As said above, the example with another reason for failure was just how I got another name duplication - namely in synapse (and the idempotency did not help there at all)

We expect the first parameter (evcode) to be unique in the subscription.

You may try in pipeline.bicep:
var synapseHnsStorageAccountNameVar = empty(synapseHnsStorageAccountName) ? 'synhns${substring(uniqueString('${synapseResourceGroupNameVar}${location}'), 0, 16)}' : synapseHnsStorageAccountName

I may not have been completely clear. Finally, after 4h, my deployment went through. I still do not know whether everything works but my point was to share experience if you find any of that input useful. For now I am afraid of running another deployment in order not to break something. My next aim is to see that in action, finally
As I see you have not pushed changes to pipeline.bicep yet

We expect the first parameter (evcode) to be unique in the subscription. If you want to use the same evcode in another region, drop the existing environment with cleanup.sh and rerun in the new region.

It did not come to my mind to cleanup to solve the Synapse duplicate name issue. As mentioned above, the bad thing is that I won't try that now after the deployment went through
Please note: envcode was unique in the subscription, but it seems it has a global effect (as it failed form the first try using "orb")

Let's go over what happended to reproduce your issue.

And, now you rerun the command with a new evcode and went thru.
setup.sh orbivo westus2 orbital custom-vision-model-v2

I just want to understand and confirm why we have the duplicate storage account name issue.

Here is it once again:

The first problem was with the "orb" - duplicate name (see the first post on the issue)
I deleted all resource groups with the prefix
I renamed orb to orbivo - SQL deployment failure due to region (no more duplicate name of the storage account)
I deleted all resource groups with the prefix
I changed the region from westus to westeurope - synapse duplicate name error (no more SQL deployment problems, but synapse already had a global deployment with that name)
I deleted all resource groups with the prefix
I changed orbivo to orbivowe - the deployment went through

When you delete resource groups, did you use cleanup.sh?
From my experience, if there is a deployment failure due to regional resource restriction, you run cleanup.sh and run in another region with a new evcode. I usually add/increment number to evcode.    This is because even if you delete resources, Azure still needs some time (more than 1 hour) to clean up the resource clearly. Hope this tip helps you understand why we have a storage account name/synapse name error.

Hope this tip helps you understand why we have a storage account name/synapse name error.
That may be valid for Synapse, but not valid for the storage account.
The storage account issue was the first one I ran and there was nothing to cleanup. I just hit a valid name generated for another user. Regardless whether I cleanup or not another user is highly likely to have that name already used.

I did not use cleanup, which of course could cause the secondary issue in that particular case but still the chance of having name duplication is real and would be getting higher with more users giving it a try (hopefully that is among the objectives).
The particular errors could be found below. The chance of having a conflict with this naming is a problem on global, rather than subscription level.
{"code": "InvalidDeploymentLocation", "message": "Invalid deployment location 'westeurope'. The deployment 'SYNAPSE-ORBIVO-DEPLOY' already exists in location 'westus2'."}
{"code": "InvalidDeploymentLocation", "message": "Invalid deployment location 'westus'. The deployment 'SYNAPSE-ORBIVO-DEPLOY' already exists in location 'westus2'."}

I am working on your input and going thru regression.
The plan is to use this namesuffix:
var nameSuffix = substring(uniqueString(guid('${subscription().subscriptionId}${namingPrefix}${environmentTag}${location}')), 0, 10)

I am working on your input and going thru regression.

Thanks and appreciated :) I am about to continue with the next steps and really hope it would go smooth

@ivo-andreev Would your review the PR and vote? Thanks

I reviewed the comments. Do I need to close unresolved conversations as I do not seem to be able to?


[Question] Best config for multispeaker PWGAN

Hi,
I have been trying to train different models on LibriTTS and some internal speakers, but I think the results leave much to be desired. While in single speaker I get good results, in multispeaker it is not the same case. My understanding was multispeaker would yield much better results, since the range of waveforms and sounds is much, much broader and the hours of speech is more than 200. What happens is that it either synthesizes with static, or it sounds muffled. I am talking about TTS synthesis by the way. I of course am not after WaveNet quality, however single speaker tests sound much better.
Taco2 has been trained for a long time, so the spectrograms should be clean, from that side.
My config is this (which I am guessing may have something wrong), which is also what I used for my single speaker training, which yielded good results:
format: "hdf5"
audio:
  clip_norm: true
  do_trim_silence: false
  frame_length_ms: 50
  frame_shift_ms: 12.5
  max_norm: 4
  hop_length: 275
  win_length: 1100
  mel_fmax: 8000.0
  mel_fmin: 0.0
  min_level_db: -100
  num_freq: 1025
  num_mels: 80
  preemphasis: 0.98
  ref_level_db: 20
  sample_rate: 22050
  signal_norm: true
  sound_norm: false
  symmetric_norm: true
  trim_db: 20

generator_params:
    in_channels: 1        # Number of input channels.
    out_channels: 1       # Number of output channels.
    kernel_size: 3        # Kernel size of dilated convolution.
    layers: 30            # Number of residual block layers.
    stacks: 3             # Number of stacks i.e., dilation cycles.
    residual_channels: 64 # Number of channels in residual conv.
    gate_channels: 128    # Number of channels in gated conv.
    skip_channels: 64     # Number of channels in skip conv.
    aux_channels: 80      # Number of channels for auxiliary feature conv.
                          # Must be the same as num_mels.
    aux_context_window: 2 # Context window size for auxiliary feature.
                          # If set to 2, previous 2 and future 2 frames will be considered.
    dropout: 0.0          # Dropout rate. 0.0 means no dropout applied.
    use_weight_norm: true # Whether to use weight norm.
                          # If set to true, it will be applied to all of the conv layers.
    upsample_net: "ConvInUpsampleNetwork" # Upsampling network architecture.
    upsample_params:                      # Upsampling network parameters.
      upsample_scales:
      - 5
      - 5
      - 11

discriminator_params:
    in_channels: 1        # Number of input channels.
    out_channels: 1       # Number of output channels.
    kernel_size: 3        # Number of output channels.
    layers: 10            # Number of conv layers.
    conv_channels: 64     # Number of chnn layers.
    bias: true            # Whether to use bias parameter in conv.
    use_weight_norm: true # Whether to use weight norm.
                          # If set to true, it will be applied to all of the conv layers.
    nonlinear_activation: "LeakyReLU" # Nonlinear function after each conv.
    nonlinear_activation_params:      # Nonlinear function parameters
        negative_slope: 0.2           # Alpha in LeakyReLU.

stft_loss_params:
    fft_sizes: [1024, 2048, 512]  # List of FFT size for STFT-based loss.
    hop_sizes: [120, 240, 50]     # List of hop size for STFT-based loss
    win_lengths: [600, 1200, 240] # List of window length for STFT-based loss.
    window: "hann_window"         # Window function for STFT-based loss

lambda_adv: 4.0  # Loss balancing coefficient.

batch_size: 8              # Batch size.
batch_max_steps: 26125     # Length of each audio in batch. Make sure dividable by hop_size.
pin_memory: true           # Whether to pin memory in Pytorch DataLoader.
num_workers: 8             # Number of workers in Pytorch DataLoader.
remove_short_samples: true # Whether to remove samples the length of which are less than batch_max_steps.
allow_cache: false          # Whether to allow cache in dataset. If true, it requires cpu memory.

generator_optimizer_params:
    lr: 0.0001             # Generator's learning rate.
    eps: 1.0e-6            # Generator's epsilon.
    weight_decay: 0.0      # Generator's weight decay coefficient.
generator_scheduler_params:
    step_size: 200000      # Generator's scheduler step size.
    gamma: 0.5             # Generator's scheduler gamma.
                           # At each step size, lr will be multiplied by this parameter.
generator_grad_norm: 10    # Generator's gradient norm.
discriminator_optimizer_params:
    lr: 0.00005            # Discriminator's learning rate.
    eps: 1.0e-6            # Discriminator's epsilon.
    weight_decay: 0.0      # Discriminator's weight decay coefficient.
discriminator_scheduler_params:
    step_size: 200000      # Discriminator's scheduler step size.
    gamma: 0.5             # Discriminator's scheduler gamma.
                           # At each step size, lr will be multiplied by this parameter.
discriminator_grad_norm: 1 # Discriminator's gradient norm.

discriminator_train_start_steps: 100000 # Number of steps to start to train discriminator.
train_max_steps: 1000000                 # Number of training steps.
save_interval_steps: 5000               # Interval steps to save checkpoint.
eval_interval_steps: 1000               # Interval steps to evaluate the network.
log_interval_steps: 100                 # Interval steps to record the training log.

num_save_intermediate_results: 4  # Number of results to be saved as intermediate results.

I have downsampled the dataset and changed the hop and win sizes to accomodate with my TTS attributes.

My understanding was multispeaker would yield much better results, since the range of waveforms and sounds is much, much broader and the hours of speech is more than 200.

In my experiments, the model with long single speaker data (say, around 24 hours) is better than the case with multi speaker data (e.g., serveral minutes x various speakers). So I think the important point is that the length of each speaker's speech and its quality. If you add bad quality speaker, it may cause quality degradation.

This is exactly what I thought at first, and I would care to wager that some LibriTTS recordings have a lot of noise. My single speaker, admittedly, had no background noise. However, then I thought that during the GAN training noise is introduced, no? So I thought introducing noise within the set may make the model more robust.
I also think you have a point in duration of speech for every speaker; although, I think it then becomes harder to tackle as a problem. Have you done any more experiments with multispeaker?

However, then I thought that during the GAN training noise is introduced, no?

What is the noise?

But I checked your VCTK pretrained model on multiband melgan and it sounds much, much better.

I think VCTK is better recording than libritts. Did you compare my samples of libritts and vctk?

but I am not really sure how many speakers are needed for the model to be able to generalize to other speakers.

This is very difficult question. I have no clear answer.

I do not have samples at hand right not unfortunately, but it was something like a static noise that sounded like "zzzz". Metallic-like, kind of. If you take a listen at your LibriTTS and VCTK gen samples, the VCTK gen sounds so much clearer and very, very close to ground truth. So I think you are right in saying it depends on the dataset sound quality.
Now I read this paper here and they report generalizing to unseen speakers on 60 hours (10 hours for 6 speakers). I will try it and report here. If it does not work, I think I will also try training a PWGAN on VCTK.


SDFormat 1.8 and 1.7 not backwards compatible with 1.6

This is only an issue, if vX.X actually refers to semantic version (which it usually does, but it could be different here, and I didn't find it). If the SDFormat version tag doesn't imply semver, please close this issue :)
In joint.sdf the child element use_parent_model_frame was dropped in v1.7. This currently destroys (backward) compatibility of parsers of v1.7+ and SDF of v1.6 and below. My suggestion would be to re-introduce the element combined with a deprecation warning and/or a note in the documentation that this is deprecated and will be removed in version 2.0. Alternatively, the version of SDFormat could be bumped to v2.0, but I understand that there is general reluctance towards increasing version major.
Relevant docs:
http://sdformat.org/spec?ver=1.6&elem=joint#axis_use_parent_model_frame
http://sdformat.org/spec?ver=1.8&elem=joint#joint_axis

I vaguely recall that this was already discussed somewhere and indeed it was a deliberate choice that minor changes in SDF could result in non-backward compatible changes, but I can't remember where that discussion was.

I found it, the comment was by @scpeters and is in https://discourse.ros.org/t/sdformat-pose-frame-semantics-proposal/9852/6 .

The SDFormat doesn't quite follow semver as it doesn't have patch versions. That being said, we do try to keep backward compatibility for users of the spec via a mechanism that automatically converts older versions to the latest (https://github.com/ignitionrobotics/sdformat/blob/sdf11/sdf/1.7/1_6.convert). This doesn't help parsers though, so yeah, I think our versioning scheme needs improvement.

Thanks for that @traversaro and @azeey . Based on @traversaro 's comment I decided to treat each version as unique. Now I parse the SDF with a generic XML parser (SAX style) until I find the opening tag <sdf version="X.X">, read the version, and then load my SDF parser/schema for version X.X. This does make me think about the weird edge case where a <sdf version="1.8"> includes a <sdf version="1.6"> model or vice versa. I should check how the C++ parser in this repo deals with such a scenario...
Going back to the issue itself, your comment @azeey seems to solve the issue. If I understand it correctly, it's essentially a wontfix since SDFormat doesn't follow semver and doesn't (yet?) seem to implement a depreciation cycle. I'll close this issue, but feel free to reopen if I misunderstood :)

a mechanism that automatically converts older versions to the latest

That's an interesting comment @azeey . I'll have to look into how this works.


Provide GridFS implementation for the new driver

Provide GridFS implementation for the new driver, which is missing at #116 in order to complete #56

Note: do not forger to disabel exclude of group file for phpunit at .travis.yml.


Combine inscriptions_on_output functions

This does a few things:

removes a comment which I think no longer applies
folds inscriptions_on_output_ordered and inscriptions_on_output_unordered, since inscriptions_on_output_unordered is never called anywhere where the increased performance would make a difference

I already did this in the sequence number key PR.


calibrateMag does not give good results

Even after calibrateMag has run, magnetometer seems giving bad results.
I'm not sure but in the calibrateMag procedure, min and max are not initialized.
So in some cases, they may stay default values instead of measured values...

You are correct, I should be initialising the struct members. I've published a new version (1.0.3) today which does that.


Internal payments

If payments are internal the pay request is decoded and handled internally.
I had to add an extra field to apipayments table to store the decoded invoice hash, as all these funding sources have their own internal checking_ids the use, the migration file seems to work and no data is lost

Thats part of the migration process, so no data is lost for people when they upgrade. It transfers all the data from apipayments to a new table apipayment

I'm working on a PR to merge this with #72 and #77.
Also, I think indexing payments by hash instead of checking_id is very necessary and healthy.
Is it ok to break the external API compatibility to do that? We can bump the version.

Actually I think I found a way that prevents any breakage to happen in any third-party service using the LNbits API.

@jiatjaf are you considering using a framework to support database migrations (like Alembic)?

I'm personally very against that, but who knows.
Did you see the new migrations framework? I think it is good.

I am not against it, but I don't think we need it right now. Current solution is stable and matches the kiss philosophy of LNbits. We decided not to use SQLAlchemy for the same reason.
If in the future we see that the application has growing pains, we can reconsider it again.

Sounds absolutely fine to me. (I just personally hate SQL so much that I wouldn't touch anything that has no ORM - but that's just me).

Just in case this needs reminding: Manually written SQL queries in any code base are obviously huge red flags for a Pentest/Code Auditor... Is just too easy to introduce security vulnerabilities (e. g. SQL injections).
Frameworks help prevent this - but of course it's also possible to write secure code without them..! :-D

Luckily, the sqlite3 standard library knows about SQL injections :)
https://docs.python.org/3.7/library/sqlite3.html

Also, it is not completely true that "frameworks help prevent this": you can still make mistakes every time you use raw SQL in an ORM. All ORMs give you the option to write raw SQL, because sometimes it just makes sense (performance being one possible reason).
Writing secure queries has nothing to do with having an ORM or not.

https://docs.djangoproject.com/en/dev/topics/db/sql/ (check the big note at the top)
https://docs.sqlalchemy.org/en/13/core/tutorial.html#using-textual-sql

you can still make mistakes every time you use raw SQL

Exactly the point I wanted to make.
Thanks for clarifying.


Fix github release script backoff exception type

The github release script broke recently and it appears that either the exception type on a 404 changed or it can be multiple types depending on path, so I broadened the @backoff decoration to accommodate that.

I have read the CLA Document and I hereby sign the CLA

recheck


xcode crashed and shut down when i try to read or write to realm !!

Goals

Expected Results

Actual Results

Steps to Reproduce

Code Sample

Version of Realm and Tooling

Realm framework version: ?
Realm Object Server version: ?
Xcode version: ?
iOS/OSX version: ?
Dependency manager + version: ?

is there any fix for this? its crashing for me too :(..uninstalling and reinstalling the app works .. for xcode 9.2

@bdash Same issue for me, I think it happens when I do some modifications to the model and run again the app.
In my case I had  a class like this:
public class Field:Object, Decodable {
    @objc dynamic var id: String = ""
    @objc dynamic var mandatory: Bool = ""
...
}

When I change it with:
public class Field:Object, Decodable {
    @objc dynamic var id: String = ""
    @objc dynamic var mandatory: String = ""
...
}

It start to crash. Do we have to do some migration? How can we fix this?

@kedavidsa This is a closed issue. Please open a new issue with all details filled into the template. Thanks!


Add support for controlling lifetime of each registered type.

Add more methods to IApplication to allow controlling lifetime of registered types. Use enumeration so that switching to different DI/IOC container may become easy.

This was already done :) and I forgot.


fix(clerk-js): Incorrect result counters in data tables

Description
This PR fixes issues with incorrect values in table pagination as users select pages
Before
Page 2

After
Page 2

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/backend
[ ] @clerk/chrome-extension
[ ] @clerk/clerk-js
[ ] @clerk/clerk-expo
[ ] @clerk/fastify
[ ] gatsby-plugin-clerk
[ ] @clerk/localizations
[ ] @clerk/nextjs
[ ] @clerk/clerk-react
[ ] @clerk/remix
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/themes
[ ] @clerk/types
[ ] build/tooling/chore

!snapshot


MLflow Integration onto Kubeflow

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is
MLflow integration is being highly looked upon in combination with Kubeflow
Describe the solution you'd like
A clear and concise description of what you want to happen
MLflow comes very handy for model Registry and Models tagging across different environments
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hey @Harikantipudi thanks for the issue do you have any links towards where there is discussion of "MLflow integration is being highly looked upon in combination with Kubeflow", so I can take a look, is this in the kubeflow community?


Remove omega

test

@Zimmi48 This one is based on master.  Something seems amiss.  Who can untangle the details?  And merge?

This PR tries to merge into coq-8.11. Is this on purpose? I would have expected a replacement of omega with lia to be based on metacoq/master and be filed against metacoq/master.

Basically, just cherry-pick the last commit on top of master and force push.

I changed the PR target to master, now everything looks reasonable

... but we seem to have no github CI for master. I can fix that tomorrow.

OK thanks @yforster!

As a quick fix, here is an ad hoc CI running for this PR:  https://github.com/yforster/template-coq/pull/8/checks?check_run_id=2263668762

Great, thanks! Apparently CI passed.

@yforster Would you mind merging this?

Thanks!


fix: fetch price immediately after currency changes

Description
as mentioned by @ekzyis here, when we change the currency in settings, we don't immediately query the price, we wait for 30 seconds before doing so, which leaves us with a new currency symbol but with the old value. this PR aims to fix that.
Screenshots

Additional Context

Checklist
Are your changes backwards compatible? Please answer below:
Yes
Did you QA this? Could we deploy this straight to production? Please answer below:
Yes
For frontend changes: Tested on mobile? Please answer below:
Did you introduce any new environment variables? If so, call them out explicitly here:
No

OK thank you for the feedback, I have included a new flag changedCurrency so we only await the response when the currency changes. I think we are ready for a review now :)


sbbf: add backwards compatibility to sbbf02 in addition to sbbf02

This is the current implementation used by starcheat (wizzomafizzo@591e2bd) to guarantee compatibility with sbbf02 mods which are still supported by recent starbound versions.

Thank you!


Add document about development workflow

I've just been reviewing some PRs and realised that I'm not completely clear on the current process.
I started writing an email to ask questions about the process when I realised that it might be easier to document my understanding and use that as a way of discussing it.
Does what I've written match your understanding of our process, @floehopper, @leenagupte, @ikennaokpala and @pmanrubia?

This process closely mirrors my current understanding.

I think it might be good to extend this a bit and include what happens when something comes back from fact-check.

I think it might be good to extend this a bit and include what happens when something comes back from fact-check.

Yes, it would be good to clarify it as well

I've renamed the "LGTM" label to "Passed code review" as suggested by @leenagupte. I've also updated the document in this PR to reflect that change.

I think it might be good to extend this a bit and include what happens when something comes back from fact-check.

What are you thinking about in particular, @floehopper? How to incorporate any changes that come back from fact-check?

Thanks for your feedback, @floehopper, @leenagupte and @pmanrubia. I've tried to incorporate your suggestions in the document. I'd appreciate you all taking another look when you have a moment.

Yes, good starting point 👍 LGTM

@chrisroos I would be happy with this PR unless there are pending comments from @floehopper @leenagupte
We can iterate on top of it in case we would need to amend / add something.
Thank you for your great work 👍

@pmanrubia: I'm happy with this PR as it stands. The most important thing is that we all have a shared understanding of how things work. As you say, if we need to change something, we can iterate. 😄

I've rebased on master and force pushed this in preparation for merging to master.

I've added the "Needs factcheck" and "Ready for code review" GitHub labels as described in this documentation.


OCI Object Storage Repository

Is your feature request related to a problem? Please describe.
Currently the existing blob store repositories do not support OCI object storage.
Describe the solution you'd like
We have developed an OCI native plugin for object storage that is convenient to use on the OCI platform.
For example you can configure the below repository and take advantage of instance principal authentication without the need to push credentials explicitly into a secret store. Can also force bucket creation if the bucket is missing.
curl -XPUT "https://localhost:9200/_snapshot/oci_repository" -H 'Content-Type: application/json' -d"
{
  \"type\": \"oci\",
  \"settings\": {
    \"client\": \"default\",
    \"endpoint\": \"https://objectstorage.${OCI_REGION}.oraclecloud.com\",
    \"bucket\": \"${OCI_BUCKET}\",
    \"namespace\": \"${NAMESPACE}\",
    \"bucket_compartment_id\": \"${OCI_BUCKET_COMPARTMENT}\",
    \"useInstancePrincipal\": true,
    \"forceBucketCreation\" : true
  }
}
" -u <user>:<password> --insecure

That's awesome @samuel-oci! It looks like this is similar to something like the repository-azure built-in plugin but for OCI?
If so, I think this should probably be moved into opensearch-project/OpenSearch as a proposal.

Hi @stockholmux thank you for the response,
Apparently I forgot to add some context from my earlier post. We actually already have the plugin ready as a standalone plugin and would like to contribute it, the question though is whether we should create a new repository for it like we do with other plugins.
There is also a preference from our side to contribute initially in a separate repo since we run into some difficulties to incorporate directly as part of the OpenSearch repo. So perhaps we can start with that and later consolidate with OpenSearch repo or any other that the community finds appropriate?
Thanks in advance,
Sam.

following @stockholmux suggestion, opened the issue at:
https://github.com/opensearch-project/OpenSearch/issues/1854#issue-1094858841
and can probably close it here.


adds some information on which channel is updating.

Should fix #867
small extra: when on latest version, it tells the user instead of silently terminating.

This now showed up in my local version, and I think it is too chatty, so I reverted this. We can discuss the issue in the original issue.

I just saw this and I agree it's too chatty:
x@fedora:~/.julia/dev/AliasTables$ juliaup update
Updating channel: 1.9
Already on the latest version, skipping.
Updating channel: nightly
Updating channel: alpha
Already on the latest version, skipping.
Updating channel: release
Already on the latest version, skipping.
Updating channel: 1.0
Already on the latest version, skipping.
Updating channel: 1.6
Already on the latest version, skipping.

Yup, I agree as well that is way too chatty. I missunderstood the program flow.
I pushed a new version that should print "Updating channel: " only for the channles that are actually being updated

@ghyatzo I think you need to create a new pull request to have the new version put in since you updated the branch after it was merged.


Named pankus

This finally became urgent enough for me to do it today, haha
Let me know what you think. At first I tried to make it work with a templated name argument (using a user type), but as the whole thing is macro'd up that caused me some unfortunate problems, so I went with the macro argument approach instead.
I did try and avoid duplication of the tests, but they're quite coupled to the Metaprogram. I took a few steps toward de-coupling them (as you can see, I could remove the #include from the top of the TypeList tests...) but backed out after I saw how tightly coupled the tests are to the types that are generated by the macro instantiation.
Fun few hours anyway!

Woah, what a throwback! :smile:
I haven't touched C++ in about... 2 or 3 years now? But I'm excited to look into this anyway. I will find time to give a review over the week :)

Bump
lol


then_signal_semaphore introduces VUID-vkQueuePresentKHR-pWaitSemaphores-03268

Template

Version of vulkano: "0.29"
OS: Fedora 35
GPU (the selected PhysicalDevice): GTX 1070 (desktop)
GPU Driver: nvidia
Upload of a reasonably minimal complete main.rs file that demonstrates the issue: https://github.com/LeonMatthes/Vulkano-Hello-Triangle/commit/72720e934502dc967cc75694d326a7dd9277cb5a

Issue
I've tried following vulkan-tutorial.com and translating the code to vulkano as closely as possible.
The code that errors should therefore be the minimal required to get to the triangle.
The problem occurs when I run the program in debug mode (with validation layers enabled).
The application also freezes in release mode, just without the error message.
At first, the triangle will render correctly, however, once the window is resized, the validation layers issue 2 instances of VUID-vkQueuePresentKHR-pWaitSemaphores-03268 and the application becomes unresponsive.
VUID-vkQueuePresentKHR-pWaitSemaphores-03268(ERROR / SPEC): msgNum: 622825338 - Validation Error: [ VUID-vkQueuePresentKHR-pWaitSemaphores-03268 ] Object 0: handle = 0x55d11b9896b0, type = VK_OBJECT_TYPE_QUEUE; Object 1: handle = 0x980f360000000011, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x251f8f7a | vkQueuePresentKHR: Queue VkQueue 0x55d11b9896b0[] is waiting on pWaitSemaphores[0] (VkSemaphore 0x980f360000000011[]) that has no way to be signaled. The Vulkan spec states: All elements of the pWaitSemaphores member of pPresentInfo must reference a semaphore signal operation that has been submitted for execution and any semaphore signal operations on which it depends (if any) must have also been submitted for execution (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/linux/1.3-extensions/vkspec.html#VUID-vkQueuePresentKHR-pWaitSemaphores-03268)
    Objects: 2
        [0] 0x55d11b9896b0, type: 4, name: NULL
        [1] 0x980f360000000011, type: 5, name: NULL
VUID-vkQueuePresentKHR-pWaitSemaphores-03268(ERROR / SPEC): msgNum: 622825338 - Validation Error: [ VUID-vkQueuePresentKHR-pWaitSemaphores-03268 ] Object 0: handle = 0x55d11b9896b0, type = VK_OBJECT_TYPE_QUEUE; Object 1: handle = 0x980f360000000011, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x251f8f7a | vkQueuePresentKHR: Queue VkQueue 0x55d11b9896b0[] is waiting on pWaitSemaphores[0] (VkSemaphore 0x980f360000000011[]) that has no way to be signaled. The Vulkan spec states: All elements of the pWaitSemaphores member of pPresentInfo must reference a semaphore signal operation that has been submitted for execution and any semaphore signal operations on which it depends (if any) must have also been submitted for execution (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/linux/1.3-extensions/vkspec.html#VUID-vkQueuePresentKHR-pWaitSemaphores-03268)
    Objects: 2
        [0] 0x55d11b9896b0, type: 4, name: NULL
        [1] 0x980f360000000011, type: 5, name: NULL

I know that the swapchain should be invalidated once the resize event happens. I'm checking the appropriate return values of acquire_next_image and aborting the render operation in that case.
There are however multiple unexpected behaviors here:

The ResizeEvent is issued by winit, but the next acquire_next_image function does not fail, and still returns an Ok result and suboptimal == false.
Removing the line 475 (.then_signal_semaphore()) seems to fix the issue

Also: Why does the error appear twice? Are two semaphores used as input semaphores for vkQueuePresentKHR?
I believe what is happening here is that the application hangs on the future.wait(None) call as the semaphore created by vulkano is never signalled.
I would just remove the then_signal_semaphore() code, however the then_execute and then_swapchain_present calls happen on two queues that might be two separate Queues - even though they are not in practice on my GTX 1070.
As the sync docs state, if these two queues are ever actually different, not using the semaphore would always result in a runtime error.
Expected behavior
Either:

Not get the VUID-vkQueuePresentKHR-pWaitSemaphores-03268 error when using the result of swapchain::acquire_next_image after a resize event.
Not get a valid result from the swapchain::acquire_next_image if the window has already been resized.

It is also possible I'm calling vulkano incorrectly somewhere, but as the docs state that vulkano aims to always detect incorrect API usage, this might still indicate a bug.
Thanks for your help.

This might somehow be related to: #1705

Your immediate problem can be solved by removing the call to then_signal_semaphore. then_swapchain_present will work fine without it, as seen in Vulkano's own examples.
The problem you report is valid, though, and is a long-standing problem with Vulkano's synchronisation. Some of the problems within command buffers are dealt with in the upcoming release, but queue synchronisation, the use of semaphores and fences, the lack of timeline semaphores and events, are known problems and quite difficult to solve correctly. They definitely have my attention, but it will probably have to be fixed in small bits at a time in order to not introduce too many new bugs.

Hm, in the meantime I've done some more investigating.
If the graphics_q and surface_q in my example are indeed separate queues instances, I think then I'd actually need the semaphore, otherwise I'd run into a problem.
For further debugging of this, I've dug into the API dump and Semaphore/GPUFuture code a bit.
The API dump can be found in the attached freeze.log file.
Interestingly, the API Dump indicates that Vulkano actually issues 3 vkQueuePresentKHR calls that all wait on the same semaphore, followed by a vkQueueWaitIdle.
I'd suspect the issue here is that only one of the Present calls can correctly wait on the Semaphore and the other ones will never be signaled.
This is also what then causes the freeze when vkQueueWaitIdle is called, as the queue is never emptied.
This issue actually seems to be caused by a bug in the PresentFuture's code.
When a PresentFuture's flush fails with "Err(FlushError::OutOfDate)", the Drop code of the PresentFuture thinks that the future has not yet been correctly flushed and does a second flush, which causes the second vkQueuePresentKHR.
I was able to get around this issue with this code:
        let draw_and_present = acquire_future
            .then_execute(self.graphics_q.clone(), command_buffer.clone())
            .unwrap()
            .then_signal_semaphore()
            .then_swapchain_present(
                self.surface_q.clone(),
                self.swapchain.swapchain.clone(),
                image_i,
            );
        match draw_and_present.flush() {
            Err(FlushError::OutOfDate) => {
                println!("Out of date!");
                unsafe {
                    draw_and_present.signal_finished();
                }
                return;
            }
            Err(e) => {
                println!("{:?}", e);
            }
            Ok(()) => (),
        };

        match draw_and_present.then_signal_fence_and_flush() {
            Ok(future) => {
                future.wait(None).unwrap();
            }
            Err(FlushError::OutOfDate) => {
                println!("Fence - Out of date!");
            }
            Err(e) => {
                println!("Fence - Failed to flush future: {:?}", e);
            }
        }

The issue here is that I need to call "signal_finished" in the Err handler of the draw_and_present future because of the error in the PresentFuture mentioned earlier.
In my opinion this is still the better way to handle the flushing, as every flush represents one vkQueue... command, which should have its own error handling.
It still also has issue #1705 that the fence is created by submitting an empty vkQueuePresent.
Furthermore, if I ever do a resize, I'll get this:
VUID-vkDestroySemaphore-semaphore-01137(ERROR / SPEC): msgNum: -1588160456 - Validation Error: [ VUID-vkDestroySemaphore-semaphore-01137 ] Object 0: handle = 0x56273f5afd00, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xa1569838 | Cannot call vkDestroySemaphore on VkSemaphore 0x9fde6b0000000014[] that is currently in use by a command buffer. The Vulkan spec states: All submitted batches that refer to semaphore must have completed execution (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/linux/1.3-extensions/vkspec.html#VUID-vkDestroySemaphore-semaphore-01137)
    Objects: 1
        [0] 0x56273f5afd00, type: 3, name: NULL
VUID-vkDestroySemaphore-semaphore-01137(ERROR / SPEC): msgNum: -1588160456 - Validation Error: [ VUID-vkDestroySemaphore-semaphore-01137 ] Object 0: handle = 0x56273f5afd00, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xa1569838 | Cannot call vkDestroySemaphore on VkSemaphore 0x980f360000000011[] that is currently in use by a command buffer. The Vulkan spec states: All submitted batches that refer to semaphore must have completed execution (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/linux/1.3-extensions/vkspec.html#VUID-vkDestroySemaphore-semaphore-01137)
    Objects: 1
        [0] 0x56273f5afd00, type: 3, name: NULL

Which is probably because then nothing ever waits on the semaphore signalled by the command_buffer, but I'm not entirely sure.
So as an immediate action I'd say the error handling when flushing a PresentFuture should be improved, so that then dropping the semaphore doesn't submit a duplicate flush.
Maybe changing the current GpuFuture a bit to represent an acyclic graph instead of the current semi-linear program flow would make sense.
i.e.: when calling then_signal_semaphore, actually return two objects - one SemaphoreFuture and the previous CommandBufferExecFuture.
Same with a then_signal_fence call.
That would make it possible to specify which semaphores/fences to use for what.

If you feel up to it, can you make the changes to then_signal_semaphore and create a new PR? I'm currently busy with other Vulkano work, and any help would be greatly appreciated.

@Rua I think I was able to fix this in #1889
Please make sure to review the PR thoroughly though. I'm still at the "Hello Triangle" stage of learning Vulkan, so may have missed some Vulkan details regarding the queue wait, etc.

Thanks for merging my PR. That solves the issue in my book :)


Add custom mobile UI for DartPad

Rather than try to cram everything into one view, let's split between the views. Perhaps with a navigation bar at the bottom?
There are lots of different options, but consideration should be made for where the browser UI is often included and for interaction with the keyboard.

I wonder how important it is to be able to modify code on mobile? Are users viewing an existing snippet - a sample linked to from some docs? Or, are they trying out ~3 lines of dart to verify some language feature?
Not trying to show both the code and the running app at the same time makes sense.
I think of the flutter web UI as supporting three modes; dart code that emits stdout output; flutter code that creates a running flutter web app, and (a lesser use case) flutter code w/ both a running app and some stdout output.

Same thing here in Kyrgyzstan: kids don't have PCs, they use their smartphones to try programming basics. I'd be happy to embed mobile-friendly dart-pad into my educational website instead of building my own custom solution from scratch.
Thank you!


Improve Whisper WASM UI example

Examples are from https://huggingface.co/datasets/Narsil/candle-examples
I'm not sure why tiny.en only has 75MB on your repo and here I'm point to openai repo which has 151MB
I see on the WASM worker config is always set to let config = Config::tiny_en(); does it worth to enable loading this from the model config.json considering the size of the other models?

You can see live demo here

Fell free to merge, when you can. Thanks


[Feature request] Add support for categories/tags

Please provide more info about this
Categories can be created by just using folders
Tags can't be supported yet


benchmark shows that dprint-node is just a bit faster

manjaro linux, node 16.2.0 (latest)
prettier 213.61 opts/sec (mean: 4.682ms, stddev: 6.011ms, 50 samples)
dprint 264.2 opts/sec (mean: 3.785ms, stddev: 0.223ms, 50 samples)

any idea what could have cause that?

js is not much slower than rust after jit.
dprint-node has huge overhead when serialize and deserialize your code.

@IWANABETHATGUY the number seems off. it's so different from the benchmark from the readme
prettier 216.33 opts/sec (mean: 4.623ms, stddev: 6.7ms, 50 samples)
dprint 6,694.02 opts/sec (mean: 0.149ms, stddev: 0.094ms, 50 samples)

I get this on windows:
> node bench.js
prettier 238.19 opts/sec (mean: 4.198ms, stddev: 6.05ms, 50 samples)
dprint 6,020.03 opts/sec (mean: 0.166ms, stddev: 0.075ms, 50 samples)

Then in WSL (ubuntu):
$ node bench.js
prettier 238.9 opts/sec (mean: 4.186ms, stddev: 6.185ms, 50 samples)
dprint 7,141.94 opts/sec (mean: 0.14ms, stddev: 0.105ms, 50 samples)

Overall dprint-plugin-typescript is much faster than prettier in the majority of cases (it usually finishes before babel within prettier even finishes parsing an AST) though the "preferSingleLine" config is not up to par with prettier yet in terms of stability.
I don't think the overhead of sending the data to rust should be that much in comparison to the work being done for formatting. There's probably something else going on here.

@tuananh how did you build it? Did you build with yarn build or yarn build-release?

Just do npm run build and then node bench.js

@tuananh ok cool. Try npm run build-release instead. npm run build will build a debug build, which will be considerably slower.

@dsherret, you're right. But the overhead will become larger with the file size incresizing.
use default small-js, bench result is below:
prettier 201.26 opts/sec (mean: 4.969ms, stddev: 6.969ms, 50 samples)
dprint 5,407.74 opts/sec (mean: 0.185ms, stddev: 0.096ms, 50 samples)

dprint is 27 times faster than prettier.
try to use a bigger js file https://github.com/acornjs/acorn/blob/master/acorn/src/tokenize.js,
prettier 12.41 opts/sec (mean: 80.583ms, stddev: 44.753ms, 50 samples)
dprint 97.65 opts/sec (mean: 10.241ms, stddev: 1.873ms, 50 samples)

dprint is 8 times faster than prettier

@IWANABETHATGUY I agree, but don't think we can say much about the impact without seeing a measurement of the time it takes to pass the data back and forth in comparison with the overall time. It may just be that dprint is slower for that file. I've usually found dprint natively to be about 10x faster on average, but sometimes it may only be 2x. It may actually even be slower than prettier when looking at minified files as dprint-plugin-typescript currently isn't optimized for that (wouldn't be too much work to get it faster though).

@dsherret agree. my mistake


IProposedExtensionApi doesn't handle multiple condas with same interpreter path

Testing #18348

Install conda
Create two conda environments like so:
conda create -n test1
conda create -n test2
Activate each and get python path. They should be the same
Try using the API to find them.

They don't show up at all.

@rchiodo Which API did you use? if the extension was already loaded and you created these then you may have to call refreshInterpreters with clear cache.
/cc @karrtikr  This seems like a underlying discovery issue.

@rchiodo conda create -n test1 does not create a conda environment with python in it.. you have to do conda create -n test1 python
as you can see in my case there is no global python, so when i ask for python path after activation i get nothing:

but if you create conda environment with python then you get python path:

I guess I have a global python set. I didn't get that error

Here's what I used to test:
https://github.com/rchiodo/test-python-api

So if the environment itself does not have python, then we don't detect it or report anything about it. does this happen if you create it like this:
conda create -n test1 python=3.9
conda create -n test2 python=3.9

This is 3.9 because 3.10 in conda is broken.

No that works fine. That's usually how I have to create them in order to get them to work.

I mean this is a problem in the old API too.

Then this is working as expected. if the environment was not created to include python we don't detect those.

I don't think a customer is going to expect this. They have multiple conda environments but they don't see any of them.

You can have pure R environments in conda. Do we expect python extension to detect those? The python in environment created using conda create -n env1 is not the python from the environment. So, if we say install things in the python, then it would be the global python. Essentially, all installation will happen to that. I think that this might lead to greater problems with the python on the machine itself.
/cc @brettcannon, @luabud what do you suggest, should we list every conda environment or only those envs that have been setup with python. Currently we only detect those that have python in the env scripts/bin folder.

So, if we say install things in the python, then it would be the global python.

This isn't true. If I do something like so:
conda activate test1
conda install matplotlib

It installs it here (even though python is global):
C:\Users\aku91\miniconda3\envs\base_sub1\Lib\site-packages\matplotlib>

If I run python from that active environment, its sys path has been modified to use the conda location, and not the global:
(base_sub1) C:\Users\aku91\miniconda3\envs\base_sub1\Lib\site-packages\matplotlib>python
Python 3.10.2 | packaged by conda-forge | (main, Jan 14 2022, 07:57:10) [MSC v.1929 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path
['', 'C:\\Users\\aku91\\miniconda3\\envs\\base_sub1\\python310.zip', 'C:\\Users\\aku91\\miniconda3\\envs\\base_sub1\\DLLs', 'C:\\Users\\aku91\\miniconda3\\envs\\base_sub1\\lib', 'C:\\Users\\aku91\\miniconda3\\envs\\base_sub1', 'C:\\Users\\aku91\\miniconda3\\envs\\base_sub1\\lib\\site-packages']
>>>

In the extension, we support both pip install and conda install for conda environments. The problems happens when people do pip install. In my scenario where I don't have global python, nothing works even from regular terminal, running a python script after env activation also does not work (all outside of vscode). So, we need to do something about this. May be add text that says it uses global python (if we decide to go the route of detecting these).

If we change pip install to instead use the activated environment and run python -m pip install, it works for me.
Running this:
python -m pip install pandas

Put pandas in the site-packages for the environment.
In fact pip seems to work by itself? I can't get it to put it in a different spot (as long as I run it from the environment).
So maybe the only caveat here is that you need a global python so that those commands can run.

@karrtikr The switch to conda run during detection should handle this scenario, right? if not then this is a bug.

In my case this happens:

The scenario where 2 environments have the same path was never supported, so this is not a bug at all. So far we haven't received users asking for this so I'm inclined to close this, unless I'm missing something?

We have (in jupyter). That could be because people doing notebooks use conda more often.

I see, can you link those issues, it'll help make us a decision on whether we want to support these. I remember Don brought up earlier that we need not support these envs at the moment: https://github.com/microsoft/vscode-jupyter/issues/7583#issuecomment-955054968

This one possibly (it can be hard to tell root causes when people don't get kernels they want)
https://github.com/microsoft/vscode-jupyter/issues/1657
And this one:
https://github.com/microsoft/vscode-jupyter/issues/5650

I just ran into this myself by accident.
conda create jimgenv
conda activate jimgenv

Everything seems fine, except I cannot find the environment in VS Code no matter what I do. Of course if I examine my environments with conda, I see it too. This is all highly confusing.
conda env list
# conda environments:
#
                         C:\JupyterLab\resources\jlab_server
base                  *  C:\Users\jimg\anaconda3
covid-analysis           C:\Users\jimg\anaconda3\envs\covid-analysis
donsrepro                C:\Users\jimg\anaconda3\envs\donsrepro
jupyter-lab-test-env     C:\Users\jimg\anaconda3\envs\jupyter-lab-test-env
my-jupyter-lab           C:\Users\jimg\anaconda3\envs\my-jupyter-lab
myenv                    C:\Users\jimg\anaconda3\envs\myenv
ocaml-kernel             C:\Users\jimg\anaconda3\envs\ocaml-kernel
try-new-ipython          C:\Users\jimg\anaconda3\envs\try-new-ipython
xeus-python              C:\Users\jimg\anaconda3\envs\xeus-python

I'm not sure I believe that this was never supported since most of the environments I've ever created I have used anaconda and I haven't specified a python version instance to install to it. In fact, the only reason I ever thought to do that was in case I wanted to use a different version of python than is available on the system. Perhaps I'm incorrect in that thinking, but it seems to make sense.

@greazer it's never been supported by us; see https://code.visualstudio.com/docs/python/environments#_where-the-extension-looks-for-environments and point 7:

Conda environments that contain a Python interpreter. VS Code does not show conda environments that don't contain an interpreter.

conda itself may be manifesting the interpreter lazily upon conda install or something.


⌥⌫ to delete word

It'd be great if ⌥⌫ deleted a word the same way it does basically anywhere on MacOS where you can edit text.

I also use Alt-Backspace as I did in fzf :)


License missing

Could you be so kind to add a license file to this project.

Thanks for reminding us! We've added a license.


Compilation Error When Filtering on Aggregation Functions

Version: 4.8.0
Module: quill-jdbc-zio
Database: postgresql
Expected behavior
import io.getquill._

val ctx = new SqlMirrorContext(MirrorSqlDialect, SnakeCase)
import ctx._

case class Person(firstName: String, lastName: String, age: Int)

val q = quote {
  query[Person]
    .groupBy(_.lastName)
    .map { case (lastName, people) =>
      (
        lastName,
        people.filter(_.firstName != "John").size,
        people.filter(_.firstName != "John").map(_.age).sum
      )
    }
}
println(ctx.run(q).string)

// SELECT x1.last_name AS _1, COUNT(*) FILTER (WHERE x1.first_name <> 'John') AS _2, SUM(x1.age) FILTER (WHERE x1.first_name <> 'John') AS _3 FROM person x1 GROUP BY x1.last_name
// or
// SELECT x1.last_name AS _1, COUNT(CASE WHEN x1.first_name <> 'John' THEN 1 END) AS _2, SUM(CASE WHEN x1.first_name <> 'John' THEN x1.age END) AS _3 FROM person x1 GROUP BY x1.last_name

Actual behavior
// error: Query compilation failed. Invalid group by aggregation: 'x1.filter(x2 => x2.firstName != "John").size'

Steps to reproduce the behavior
https://scastie.scala-lang.org/9aFplZTKSQ6KO1WEOC1a9A
Workaround
import io.getquill._

val ctx = new SqlMirrorContext(MirrorSqlDialect, SnakeCase)
import ctx._

case class Person(firstName: String, lastName: String, age: Int)

val countFilter = quote {
  (cond: Query[Boolean]) => sql"COUNT(*) FILTER (WHERE $cond)".pure.as[Long]
}

def sumFilter[N: Numeric] = quote {
  (expr: Query[N], cond: Query[Boolean]) => sql"SUM($expr) FILTER (WHERE $cond)".pure.as[N]
}

val q = quote {
  query[Person]
    .groupBy(_.lastName)
    .map { case (lastName, people) =>
      (
        lastName,
        countFilter(people.map(_.firstName != "John")),
        sumFilter[Int].apply(people.map(_.age), people.map(_.firstName != "John"))
      )
    }
}
println(ctx.run(q).string)

// SELECT x1.last_name AS _1, COUNT(*) FILTER (WHERE x1.first_name <> 'John') AS _2, SUM(x1.age) FILTER (WHERE x1.first_name <> 'John') AS _3 FROM person x1 GROUP BY x1.last_name

@getquill/maintainers

This is my first comment. I'm sorry if I can't be clear.
I think the solution might be to first filter and group the remaining people according to their surnames.

val q = quote {
  query[Person]
    .filter(_.firstName != lift("john"))
    .groupBy(_.lastName)
    .map { case (lastName, people) =>
      (lastName,people.size,people.map(_.age).sum)
    }
}
//SELECT x1.last_name, COUNT(*), SUM(x1.age) FROM person x1 WHERE x1.first_name <> ? GROUP BY x1.last_name


Clear Containers for Docker Engine

This is initial release of Clear Containers execution driver for Docker Engine.
It is available today, as default, on clearlinux.org however we are also preparing binary distribution for common distributions.
Most of the changes are contained in the clr execution driver, however a few additional details had to be made public - specifically options relating to the network bridge the execution driver should connect to, and addition of the tuntap device support in libnetwork, and up the stack to daemon/execdriver.
This makes clear containers driver the default, and when this execution driver is enabled, the default network driver is flipped to tuntap, as that's the only one that is currently supported by this execution driver. If incompatible network is used, the container will fail to start.
In addition to this code, one also needs compatible kvmtool & vmlinux.container image on the host. All three are in progress to be compiled and made available for download for multiple common distributions.
This is more of an RFC - comments and reviews would be highly appreciated.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "clr-1.8.1-submit" git@github.com:clearlinux/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~3
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "clr-1.8.1-submit" git@github.com:clearlinux/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~3
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Pushing older code, without tuntap libnetwork driver as it is actually very broken still. The code now, does very strange thing (a) delete created veth pair (b) create tap interface it its place (c) mimic/pretend to be the previous veth pair. Architecturally, I think execdriver should be passing endpointoption all the way back to the exec driver to e.g. specify interfacetype and get a tap interface created instead of a veth pair. That should be clean, and logical. Please advice, i'll try to work on that now.

If I'm correct, we decided to not accept more execution drivers that are not provided by runC/libcontainer.  All the execution driver logic is going to be replaced in the future by runC and we don't want other dependencies to stop that from happening.
/cc @crosbymichael

@calavera Indeed, but we had discussions with the Clear Containers team from Intel and both agreed that the PR was worth submitting for educational and testing purpose. You are however right that, with their agreement, this will not be merged.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "clr-1.8.1-submit" git@github.com:clearlinux/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~5
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

hi sorry seeing as this is not going to be merged and i am trying to clean up the repo I am going to close but thank you!!

We now have OCI compatible binary, where is the docker code that calls out to OCI binaries instead of using execution drivers? As we are ready to be merged with that implementation of docker. And in addition to that, we still want to have an exec-driver merged, whilst the exec-driver based docker is the stable/production version in operation.


Gallery has moved

There is no GalleryLocations in the registry anymore. That configuration has changed.
My Hyper-V instance offers Ubuntu 20 under "Create New" and is hilariously slow... it will take a day or so in my gigabit internet connection. It would be great to know where to download these images for manual loading.

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

ID: 10a2abfe-1741-41bf-b4b8-25a42a1d9d0a
Version Independent ID: 33529fa3-e824-bfbb-3d2e-5f502afe9622
Content: Create a custom virtual machine galllery
Content Source: virtualization/hyper-v-on-windows/user-guide/custom-gallery.md
Service: windows-10-hyperv
Product: windows-10-hyperv
GitHub Login: @scooley
Microsoft Alias: scooley

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


draggable items between widgets

I am trying to make some items in widget1 draggable and droppable in widget2, but i cant make the z-index work. When dragging the draggable item from widget1 into widget2 it disappears.
Stackoverflow: http://stackoverflow.com/questions/28606752/draggable-between-widgets-in-angular-gridster

Just reset gridster z-index when widgets is not draggable, as I have suggested here http://stackoverflow.com/a/29436105/1534097


fix(node): read consistency level fix

PR fixes #1565

@wjones127 please review.

@wjones127 Updated PR. Please review.

Thanks @gagan-bhullar-tech !


Required Express entity field types are not validated correctly

When adding an Express entity field type to a form and marking that field as required, user can still submit the form without selecting any data object.
Steps to reproduce:

Create a new Form block.
Add one Express entity field and mark it as required.
Save form.
Submit the form.

What happens:
Form is submitted without an error about the required field.
Expected result:
Form should give an error that the field is required.
# concrete5 Version
Core Version - 8.3.2
Version Installed - 8.3.2
Database Version -<PHONE_NUMBER>3656

# concrete5 Packages
Afixia: Login Redirect (0.9.2), Login Block (0.9.3)

# concrete5 Overrides
themes/extranet/home.php, themes/extranet/page_forbidden.php, themes/extranet/page_theme.php, themes/extranet/right_sidebar.php, themes/extranet/full.php, themes/extranet/images, themes/extranet/left_sidebar.php, themes/extranet/default.php, themes/extranet/view.php, themes/extranet/page_not_found.php, themes/extranet/elements/header_old.php, themes/extranet/elements/header_calendar.php, themes/extranet/elements/header_top_bak.php, themes/extranet/elements/header_top.php, themes/extranet/elements/footer.php, themes/extranet/elements/header.php, themes/extranet/elements/footer_bottom.php, themes/extranet/elements, themes/extranet/description.txt, themes/extranet/css/styles.xml, themes/extranet/css/mixins/mixins.less, themes/extranet/css/mixins, themes/extranet/css/main.less, themes/extranet/css/components/forms.less, themes/extranet/css/components/footer.less, themes/extranet/css/components/header.less, themes/extranet/css/components/navigation.less, themes/extranet/css/components/blocks.less, themes/extranet/css/components, themes/extranet/css/bootstrap-3.2.0/button-groups.less, themes/extranet/css/bootstrap-3.2.0/code.less, themes/extranet/css/bootstrap-3.2.0/variables.less, themes/extranet/css/bootstrap-3.2.0/navs.less, themes/extranet/css/bootstrap-3.2.0/forms.less, themes/extranet/css/bootstrap-3.2.0/breadcrumbs.less, themes/extranet/css/bootstrap-3.2.0/mixins.less, themes/extranet/css/bootstrap-3.2.0/close.less, themes/extranet/css/bootstrap-3.2.0/labels.less, themes/extranet/css/bootstrap-3.2.0/mixins/center-block.less, themes/extranet/css/bootstrap-3.2.0/mixins/grid-framework.less, themes/extranet/css/bootstrap-3.2.0/mixins/image.less, themes/extranet/css/bootstrap-3.2.0/mixins/forms.less, themes/extranet/css/bootstrap-3.2.0/mixins/progress-bar.less, themes/extranet/css/bootstrap-3.2.0/mixins/labels.less, themes/extranet/css/bootstrap-3.2.0/mixins/tab-focus.less, themes/extranet/css/bootstrap-3.2.0/mixins/background-variant.less, themes/extranet/css/bootstrap-3.2.0/mixins/resize.less, themes/extranet/css/bootstrap-3.2.0/mixins/hide-text.less, themes/extranet/css/bootstrap-3.2.0/mixins/gradients.less, themes/extranet/css/bootstrap-3.2.0/mixins/size.less, themes/extranet/css/bootstrap-3.2.0/mixins/pagination.less, themes/extranet/css/bootstrap-3.2.0/mixins/text-emphasis.less, themes/extranet/css/bootstrap-3.2.0/mixins/nav-vertical-align.less, themes/extranet/css/bootstrap-3.2.0/mixins/nav-divider.less, themes/extranet/css/bootstrap-3.2.0/mixins/opacity.less, themes/extranet/css/bootstrap-3.2.0/mixins/table-row.less, themes/extranet/css/bootstrap-3.2.0/mixins/list-group.less, themes/extranet/css/bootstrap-3.2.0/mixins/responsive-visibility.less, themes/extranet/css/bootstrap-3.2.0/mixins/grid.less, themes/extranet/css/bootstrap-3.2.0/mixins/vendor-prefixes.less, themes/extranet/css/bootstrap-3.2.0/mixins/clearfix.less, themes/extranet/css/bootstrap-3.2.0/mixins/border-radius.less, themes/extranet/css/bootstrap-3.2.0/mixins/panels.less, themes/extranet/css/bootstrap-3.2.0/mixins/buttons.less, themes/extranet/css/bootstrap-3.2.0/mixins/text-overflow.less, themes/extranet/css/bootstrap-3.2.0/mixins/alerts.less, themes/extranet/css/bootstrap-3.2.0/mixins/reset-filter.less, themes/extranet/css/bootstrap-3.2.0/mixins, themes/extranet/css/bootstrap-3.2.0/scaffolding.less, themes/extranet/css/bootstrap-3.2.0/utilities.less, themes/extranet/css/bootstrap-3.2.0/tables.less, themes/extranet/css/bootstrap-3.2.0/normalize.less, themes/extranet/css/bootstrap-3.2.0/thumbnails.less, themes/extranet/css/bootstrap-3.2.0/component-animations.less, themes/extranet/css/bootstrap-3.2.0/navbar.less, themes/extranet/css/bootstrap-3.2.0/pagination.less, themes/extranet/css/bootstrap-3.2.0/jumbotron.less, themes/extranet/css/bootstrap-3.2.0/input-groups.less, themes/extranet/css/bootstrap-3.2.0/tooltip.less, themes/extranet/css/bootstrap-3.2.0/glyphicons.less, themes/extranet/css/bootstrap-3.2.0/wells.less, themes/extranet/css/bootstrap-3.2.0/responsive-embed.less, themes/extranet/css/bootstrap-3.2.0/list-group.less, themes/extranet/css/bootstrap-3.2.0/badges.less, themes/extranet/css/bootstrap-3.2.0/grid.less, themes/extranet/css/bootstrap-3.2.0/carousel.less, themes/extranet/css/bootstrap-3.2.0/modals.less, themes/extranet/css/bootstrap-3.2.0/media.less, themes/extranet/css/bootstrap-3.2.0/dropdowns.less, themes/extranet/css/bootstrap-3.2.0/panels.less, themes/extranet/css/bootstrap-3.2.0/buttons.less, themes/extranet/css/bootstrap-3.2.0/progress-bars.less, themes/extranet/css/bootstrap-3.2.0/bootstrap.less, themes/extranet/css/bootstrap-3.2.0/pager.less, themes/extranet/css/bootstrap-3.2.0/print.less, themes/extranet/css/bootstrap-3.2.0/alerts.less, themes/extranet/css/bootstrap-3.2.0/type.less, themes/extranet/css/bootstrap-3.2.0/popovers.less, themes/extranet/css/bootstrap-3.2.0/theme.less, themes/extranet/css/bootstrap-3.2.0/responsive-utilities.less, themes/extranet/css/bootstrap-3.2.0, themes/extranet/css/base/typography.less, themes/extranet/css/base/body.less, themes/extranet/css/base, themes/extranet/css/variables/errors.less, themes/extranet/css/variables/colors.less, themes/extranet/css/variables/typography.less, themes/extranet/css/variables/gutters.less, themes/extranet/css/variables/dimensions.less, themes/extranet/css/variables, themes/extranet/css/bootstrap-modified.css, themes/extranet/css, themes/extranet/js/main.js, themes/extranet/js, themes/extranet

# concrete5 Cache Settings
Block Cache - Off
Overrides Cache - Off
Full Page Caching - Off
Full Page Cache Lifetime - Every 6 hours (default setting).

# Server Software
Apache

# Server API
litespeed

# PHP Version
5.6.36

# PHP Extensions
bcmath, bz2, calendar, Core, ctype, curl, date, dom, ereg, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imap, intl, ionCube Loader, json, libxml, litespeed, mbstring, mcrypt, mhash, mysql, mysqli, mysqlnd, openssl, pcntl, pcre, PDO, pdo_mysql, pdo_sqlite, Phar, posix, readline, Reflection, session, shmop, SimpleXML, soap, sockets, SPL, sqlite3, standard, timezonedb, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend Guard Loader, Zend OPcache, zip, zlib

# PHP Settings
max_execution_time - 30
log_errors_max_len - 1024
max_file_uploads - 20
max_input_nesting_level - 64
max_input_time - -1
max_input_vars - 1000
memory_limit - 128M
post_max_size - 8M
sql.safe_mode - Off
upload_max_filesize - 2M
mysql.max_links - Unlimited
mysql.max_persistent - Unlimited
mysqli.max_links - Unlimited
mysqli.max_persistent - Unlimited
pcre.backtrack_limit - 1000000
pcre.recursion_limit - 100000
session.cache_limiter - <i>no value</i>
session.gc_maxlifetime - 7200
soap.wsdl_cache_limit - 5
opcache.max_accelerated_files - 2000
opcache.max_file_size - 0
opcache.max_wasted_percentage - 5
zend_optimizerplus.max_accelerated_files - 2000
zend_optimizerplus.max_file_size - 0
zend_optimizerplus.max_wasted_percentage - 5

@aembler Is there any news about this bug or chances that it will get fixed in future versions? We get quite a lot of questions about this from our clients who are using the newer form versions.

It's something we'd be happy to accept a fix for, but at the time there's no new news about this bug.


Endpoint for deleting/deactivating a Konfetti Idea

Should be allowed for the creator/owner and the neigborhood admin/reviewer.

Bug Report: I was creator of idea, but when trying to delete the idea it was telling me that I am not allowed.


Add autoLocker

Coverage decreased (-0.2%) to 68.735% when pulling fc34754be159097d0d33838ccaa261423141e78b on autoLocker into<PHONE_NUMBER>ea3249ee53b74f51e2428c28999bb9 on master.

@venkat1109 has some valid concerns/questions on this:

Instead of providing a safety auto locker, why not just enforce the restriction on code where you always follow a Lock with a defer Unlock and rearrange the code to handle unlocks in the middle.
His concern about correctness on auto lock racing - which is not the case here since you always allocate a new auto locker object, which means the lifetime of this object is restricted within the scope of this routine.

We can do a post scrum on this later today.

I tend to agree with previous comments; I think this isn't very idiomatic and relying on the (laziness) of a GC to unlock adds in more uncertainty .. particularly when debugging deadlocks, sync issues, etc.
I think the best way to achieve this (which I presume is a one-liner lock/unlock) in Golang is using defer mechanism, perhaps like this:
func AutoLock(l sync.Locker) func() {

	l.Lock()

	return func() {
		l.Unlock()
	}
}

And use it like this:

var mu sync.RWMutex

func foo() {

    defer AutoLock(&mu)()

    // do stuff under lock, that gets unlocked when we leave the function //
}

Kiran's suggestion is pretty clever. I'm wondering if it can be made to work with the RW lock case, where we want to upgrade the lock.
We should also look at templatizing functions like RWLockReadAndConditionalWrite, which maintains the code readability of having a single function (+ lambdas), while ensuring that mistakes can't be made.


Add Cards app

https://try.cards/
https://contacts.try.cards/

I would recommend a transparent background instead of grey.

Bump, @rtkhanas

@zeke sorry, for unknown reason I haven't noticed your message. I just pushed a commit with a transparent icon.

👌


Lists checkboxes not recognised properly

This repository README.adoc is a good example, just add a [x] to the first list item and it gets detected as Plain text.

Fixed in https://github.com/nlopes/acdc/commit/a7c09140e75af95ea98dce67d4ce99595ac017de


load_in_4bit option for OVModelForCausalLM

API extension:

import nncf
from transformers import AutoTokenizer
from optimum.intel.openvino import OVModelForCausalLM

MODEL_ID = "databricks/dolly-v2-3b"
tokenizer = AutoTokenizer.from_pretrained(MODEL_ID)

model = OVModelForCausalLM.from_pretrained(
    MODEL_ID,
    export=True,
    load_in_4bit=True,
    quantization_config={"dataset": "ptb", "mode": nncf.CompressWeightsMode.INT4_ASYM, "ratio": 0.8},
)

A set of default configs for 4-bit weights-only quantization of popular models
Aligned tests with the latest version of NNCF (+Conv 8-bit quantization)

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

CI is ready. The two failed quantization tests will be fixed by #535.


Running on AWS VM -- modprobe: FATAL: Module kheaders not found in directory /lib/modules/5.15.0-1031-aws

Describe the bug
The logs of the kepler-exporter are given below. The pod is Running but not functioning properly.
See the steps to reproduce for details. However, the kconfig.h file is in fact there in the /include/linux folder within the linux header.
Failed to init nvml: could not init nvml: , using dummy source to obtain gpu power
I0313 16:30:11.169173       1 gpu_nvml.go:45] could not init nvml:
I0313 16:30:11.170197       1 exporter.go:150] Kepler running on version: 46d55d9
I0313 16:30:11.170257       1 config.go:153] using gCgroup ID in the BPF program: true
I0313 16:30:11.170309       1 config.go:154] kernel version: 5.15
I0313 16:30:11.170349       1 config.go:172] EnabledGPU: true
I0313 16:30:11.170510       1 rapl_msr_util.go:143] failed to open path /dev/cpu/1/msr: no such file or directory
I0313 16:30:11.170600       1 power.go:64] Not able to obtain power, use estimate method
I0313 16:30:12.488995       1 exporter.go:168] Initializing the GPU collector
modprobe: FATAL: Module kheaders not found in directory /lib/modules/5.15.0-1031-aws
:1:10: fatal error: './include/linux/kconfig.h' file not found
#include "./include/linux/kconfig.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
I0313 16:30:12.909494       1 bcc_attacher.go:64] failed to attach the bpf program:
I0313 16:30:12.909528       1 bcc_attacher.go:124] failed to attach perf module with options [-DNUM_CPUS=2 -DSET_GROUP_ID]: failed to attach the bpf program: , not able to load eBPF modules
I0313 16:30:12.909581       1 exporter.go:185] failed to start : failed to attach bpf assets: failed to attach the bpf program:
I0313 16:30:12.909756       1 exporter.go:210] Started Kepler in 1.739579451s
To Reproduce
We have a single-node K8s cluster set up using RKE v1.4.3. Kubernetes version is v1.24.8 with Docker 20.10.23. The node is an AWS VM with OS Ubuntu 22.04. Some additional debugging was required to successfully launch the pod. The steps are given below:

Change "DIrectory" --> "DirectoryOrCreate" for the hostPath volume "/lib/modules" otherwise it could not find the folder.
The "build" directory inside /lib/modules/5.15.0-1031-aws is a symlink to "/usr/src/linux-headers-5.15.0-1031-aws" so that also needs to be mounted into the pod. Therefore added a new volumeMount
- mountPath: /usr/src/linux-headers-5.15.0-1031-aws
name: lhd
readOnly: true
with the associated volume

hostPath:
path: /usr/src/linux-headers-5.15.0-1031-aws
type: DirectoryOrCreate
name: lhd

Expected behavior
For the kepler-exporter to be functioning as it is supposed to.
Desktop (please complete the following information):

Running on AWS (kernel headers could be modified)
OS: Ubuntu 22.04
Kubernetes v1.24.8
Docker 20.10.23
cgroupsv2 enabled

can you try this volume config? We have similar issue testing kepler on github runner, the solution is bind mount the entire /usr/src to kepler pod
https://github.com/sustainable-computing-io/kepler/blob/main/manifests/config/exporter/patch/patch-ci.yaml

If the VM is started with host cpu passthrough, Kepler can see the HW perf counters.

Thank you. I believe there is some configuration I'm missing. Closing this issue as the original problem was addressed.


after migrating new schema, photon doesn't know the argument

my firsrt table :

column
Type

employee_id
String

payrol
String

in my schema.prisma
model EmployeePayroll {
  id          String    @default(cuid()) @id
  employee_id Employee?
  payrol      String
  createdAt   DateTime  @default(now())
  updatedAt   DateTime  @updatedAt
}

then i changed the schema to

column
Type

employee_id
String

payrol
String

status
Int

note
String

in my schema.prisma
model EmployeePayroll {
  id          String    @default(cuid()) @id
  employee_id Employee?
  status      Int
  note        String
  payrol      String
  createdAt   DateTime  @default(now())
  updatedAt   DateTime  @updatedAt
}

after i run the command
$ npx prisma2 lift save --name 'init'
$ npx prisma2 lift up
$ npx prisma2 generate
$ npm -s run generate
$ npm run build

then i call the graphql it responsed like this:
{
    "errors": [
        {
            "message": "\nInvalid `photon.employeePayrolls.create()` invocation in Product\\prisma-hcm-apollo\\functions\\lib\\types\\mutations\\Payroll.js:146:48\n\n{\n  data: {\n    employee_id: {\n      connect: {\n        id: 'ck5hmwpnr000040uqppjwe08t'\n      }\n    },\n    payrol: '{\"salaryDelails\":{\"employmentType\":\"Intern\",\"basicSalary\":3000000},\"allowance\":[{\"name\":\"meal\",\"amount\":20000,\"type\":\"monthly\"},{\"name\":\"transport\",\"amount\":20000,\"type\":\"daily\"}],\"deduction\":[{\"name\":\"absent\",\"amount\":20000,\"type\":\"daily\"}]}',\n    status: 1\n    ~~~~~~\n  }\n}\n\nUnknown arg `status` in data.status for type EmployeePayrollCreateInput. Did you mean `select`? Available args:\ntype EmployeePayrollCreateInput {\n  id?: ID\n  payrol: String\n  createdAt?: DateTime\n  updatedAt?: DateTime\n  employee_id?: EmployeeCreateOneWithoutEmployee_idInput\n}\n\n",
            "locations": [
                {
                    "line": 2,
                    "column": 3
                }
            ],
            "path": [
                "createEmployeePayrollHR"
            ],
            "extensions": {
                "code": "INTERNAL_SERVER_ERROR",
                "exception": {
                    "stacktrace": [
                        "Error: ",
                        "Invalid `photon.employeePayrolls.create()` invocation in Product\\prisma-hcm-apollo\\functions\\lib\\types\\mutations\\Payroll.js:146:48",
                        "",
                        "{",
                        "  data: {",
                        "    employee_id: {",
                        "      connect: {",
                        "        id: 'ck5hmwpnr000040uqppjwe08t'",
                        "      }",
                        "    },",
                        "    payrol: '{\"salaryDelails\":{\"employmentType\":\"Intern\",\"basicSalary\":3000000},\"allowance\":[{\"name\":\"meal\",\"amount\":20000,\"type\":\"monthly\"},{\"name\":\"transport\",\"amount\":20000,\"type\":\"daily\"}],\"deduction\":[{\"name\":\"absent\",\"amount\":20000,\"type\":\"daily\"}]}',",
                        "    status: 1",
                        "    ~~~~~~",
                        "  }",
                        "}",
                        "",
                        "Unknown arg `status` in data.status for type EmployeePayrollCreateInput. Did you mean `select`? Available args:",
                        "type EmployeePayrollCreateInput {",
                        "  id?: ID",
                        "  payrol: String",
                        "  createdAt?: DateTime",
                        "  updatedAt?: DateTime",
                        "  employee_id?: EmployeeCreateOneWithoutEmployee_idInput",
                        "}",
                        "",
                        "",
                        "    at Document.validate (D:\\Gtalent Product\\prisma-hcm-apollo\\functions\\lib\\node_modules\\@prisma\\photon\\runtime\\index.js:40664:23)",
                        "    at EmployeePayrollClient.get _document [as _document] (D:\\Gtalent Product\\prisma-hcm-apollo\\functions\\lib\\node_modules\\@prisma\\photon\\index.js:1440:22)",
                        "    at EmployeePayrollClient.then (D:\\Gtalent Product\\prisma-hcm-apollo\\functions\\lib\\node_modules\\@prisma\\photon\\index.js:1461:63)",
                        "    at process._tickCallback (internal/process/next_tick.js:189:7)"
                    ]
                }
            }
        }
    ],
    "data": null
}

how i fix this ? is this kind a bug?

Hey @gaspan , could you have another look at this after @pantharshit00 could not reproduce this? With a newer Prisma version this should definitely not happen any more. If you can not reproduce this, we would like to close the issue (or you can do that for us).

I am going to close this now. Happy to take a look again if we get more information.