Request GEMMT API

Intel MKL provides an additional GEMM variant, GEMMT, that updates only the upper or lower triangular part of the result matrix.  This would be a great addition to OpenBLAS.
https://software.intel.com/en-us/node/590047

You mean - to wrap _symm with 2 transforms?

I believe that the difference is more than wrapping SYMM with two transforms, but maybe I am misunderstanding your question.
SYMM is described as
C := alphaAB + beta*C
https://software.intel.com/en-us/node/468488
GEMMT is described as
C := alpha*op(A)op(B) + betaC
https://software.intel.com/en-us/node/590047
with different limitations on A, B, and C.  For GEMMT, the upper triangular or lower triangular part of C is overwritten by the respective part of the result.

I wrote DGEMMT in julia and in no-transform case it became plain DSYMM call...
It is really k--ka-s job they did with llvm

This would be nice! :)

Hi.
I'm curious if anyone's still tuned-in for this request.
To reillustrate the problem, GEMMT computes only a part of GEMM.
It's different from SYMM in my opinion as neither of the 2 operands A&B has symmetry restrictions.
Rather, it's more similar to SYR2K but with only A*transpose(B) term.
GEMMT is beyond the BLAS standard but I guess it's implementation could be very close to SRYK/HERK?

Not implemented yet, but not forgotten either. I agree that it does look more like syr2k than symm.

Fwiw, MUMPS solver ( http://mumps.enseeiht.fr/doc/userguide_5.4.1.pdf ) would benefit a lot: "We strongly recommend to use this ability if your BLAS library enables it"

I'd like to second that : GEMMT feature's implementation would be great :).

Not the reference one: https://github.com/Reference-LAPACK/lapack/search?q=dgemmt shows no hits.

Lots of low hanging fruit but never enough pickers (happens in real-world orchards too). ReLAPACK is included in OpenBLAS as a build-time option, but not built by default (even in the original reLAPACK source). I have not gotten around to checking if Peise's algorithm there actually works and is efficient.

fair point @martin-frbg; I'll stop arguing as I cannot devote time to help :)

Looks like this is the last blocker for 0.3.21, should this have been closed by #3548?

There are comments above comparing gemmt to syr2k. I think it is more similar to syrkx provided by cuBLAS and rocBLAS. See the links below:

https://docs.nvidia.com/cuda/cublas/#cublas-t-syrkx
https://docs.amd.com/bundle/rocBLAS-User-Guide---rocBLAS-documentation/page/API_Reference_Guide_80.html#rocblas-xsyrkx-batched-strided-batched

syrkx allows for op(A)op(B)^T where gemmt allows for opa(A)opb(B). If one thinks in terms of gemm, gemmt allows NN, NT, TN, TT. syrkx only allows NT or TN.

Thanks. GEMMT was added in #3796, to be released with 0.3.22, apparently I neglected to add the backlink to this issue in the PR


Fix Helm Chart Prometheus Adapter Metrics

Proposed changes
The x100 multiplier in the existing metrics is not compatible with the scaling ratio from 0.0 to 1.0 in the chart.  I'm removing the multiplier to make it consistent with the comments in the values file for scaling.auto.engine.metrics.requestCapacityRatio
This could be a breaking change for any users that have changed the ratio to use a scale from 0 to 100 rather than changing the custom metrics.

Types of changes
What types of changes does your code introduce to the Deepgram self-hosted resources?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update or tests (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have tested my changes in my local self-hosted environment

Please describe your testing setup and methodology here

[ ] I have added necessary documentation (if appropriate)

Further comments

Here are screenshots of the custom metric and it's components:

And here is the HPA using a scaling factor of 0.5, you can see that the values match the current load show in the custom metrics above
apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
  labels:
    app.kubernetes.io/instance: deepgram-self-hosted
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: deepgram-self-hosted
    app.kubernetes.io/version: release-241121
    helm.sh/chart: deepgram-self-hosted-0.8.0
  name: deepgram-engine-hpa
  namespace: dg-self-hosted
spec:
  behavior:
    scaleDown:
      policies:
        - periodSeconds: 60
          type: Pods
          value: 1
        - periodSeconds: 60
          type: Percent
          value: 25
      selectPolicy: Max
    scaleUp:
      policies:
        - periodSeconds: 15
          type: Pods
          value: 4
        - periodSeconds: 15
          type: Percent
          value: 100
      selectPolicy: Max
      stabilizationWindowSeconds: 0
  maxReplicas: 20
  metrics:
    - external:
        metric:
          name: engine_requests_active_to_max_ratio
        target:
          type: Value
          value: 500m
      type: External
  minReplicas: 2
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: deepgram-engine
status:
  conditions:
    - lastTransitionTime: '2024-12-10T04:28:37Z'
      message: recommended size matches current size
      reason: ReadyForNewScale
      status: 'True'
      type: AbleToScale
    - lastTransitionTime: '2024-12-14T19:13:19Z'
      message: >-
        the HPA was able to successfully calculate a replica count from external
        metric engine_requests_active_to_max_ratio(nil)
      reason: ValidMetricFound
      status: 'True'
      type: ScalingActive
    - lastTransitionTime: '2024-12-14T21:37:54Z'
      message: the desired replica count is less than the minimum replica count
      reason: TooFewReplicas
      status: 'True'
      type: ScalingLimited
  currentMetrics:
    - external:
        current:
          value: 3m
        metric:
          name: engine_requests_active_to_max_ratio
      type: External
  currentReplicas: 2
  desiredReplicas: 2
  lastScaleTime: '2024-12-14T21:39:54Z'

We identified this issue after identifying that only a few concurrent requests would cause the engine to scale up rather than ~100 requests that we were expecting to trigger an increase in scale.  I don't have the previous HPA, but it would be 300m in this case with a single concurrent request.

Great. That all tracks. Could you add a line to CHANGELOG.md describing your changes? Nest it under ## Unreleased, with a subheader of ## Changed.
That will also pass the PR checks.

Looks great! Thanks so much. I'll put out a new version with a minor version bump for you to ingest.

@paulliwog Released in 0.8.1


Typo "Azure data factory"→"Azure Data Factory"

https://docs.microsoft.com/en-us/azure/data-factory/v1/data-factory-pig-activity

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

Here, the intention appears to be to refer to the Azure service ("v1"), so I edited to clarify and will merge the PR. Thanks.


Additional comms message to the UKHPI front page

Given the data problems with the new Bournemouth Christchurch and Poole region - can the following be added to the front UKHPI page.
Note: Bournemouth, Christchurch and Poole data for 2018 to 2020 is missing from the February UK HPI report (published 22 April) due to data issues. The full dataset will be available in the March UK HPI report (published 20 May).

@MalcolmShazell I added a date to the note, as I often find myself wanting to know that when I come across such warnings on the web. But I'm happy to take it out again if you prefer. Please have a look at:
https://lr-dev.epimorphics.net/app/ukhpi
and let me know any changes you'd like me to make.

looks fine to me - but I will check with Dave as he has final say

got the nod from dave - happy to go with that ian

thaks Ian much appreciated


Base image layer optimization

I think we can put more of the layers into the :base image - Namely I am thinking that the entrypoint.sh and .env.docker could just be in the base image also

entrypoint.sh may change in future if env-config is changed. Don't want to rely on base too much :smile:

We could just tag base also - Have seen projects do something like namespace:base-20150817 that way we can have :base releases also.
Currently it is :base-hash which is essentially the same.


/toggle blood does not work, says on but no blood.

Cardinal Version: 1.0-SNAPSHOT-git-CardinalPGM-601a41f

Duplicate of #191


Add isTranslucent()

This is a public facing method, to provide clients the opportunity to know if a given artboard will need per-pixel-alpha after it is drawn. Useful if the client wants to cull out drawings behind the artboard, or as an optimization hint to an image/video encoder (often opaque images can compress better).

... intended to be used here: https://github.com/rive-app/rive-recorder/pull/45

any other comments/issues?


dcc continuosly crashes if system.uuid field isn't found in Elastic document

To reproduce on pe:

enable inline scripting in es.yml: add script.inline: true to app/cm-well/conf/es/es.yml and restart elastic search.
locate an infoton in elastic, and delete the "uuid" field:
curl localhost:9201/cm_well_p0_0/infoclone/c9937ea222b08019b2162a83f54201ce/_update -d ' {"script" : "ctx._source.system.remove("uuid")"}'
reset crawler offsets and restart bg.
Observe continuos restarts of crawler by bgActor.

After a discussion in the grooming meeting we have decided that this case is too artificial and will not be handled. In other cases we will strive to prevent DCC and other components from getting stuck, rather report the issue to the red log and move forward.


Option to remove "-it" from docker command, to avoid TTY error in non-interactive shell?

I'm running smriprep-docker in a google cloud environment using automatic startup scripts, and found that it was exiting with the error "The input device is not a TTY".  If I have my startup script explicitly pull poldracklab/smriprep:0.6.1 and then run the "docker run" command smriprep-docker was trying to execute, but without the "-it", it all works fine.
I like the flexibility of the wrapper, so it would be nice to keep using it. Can you perhaps include a argument to skip the "-it" flag? Same would be useful for fmriprep-docker

sounds like a good idea, @kjamison, perhaps as a --noninteractive or --no-tty flag? would you be up for submitting a PR with this new addition?


[DOC] Update Metrics Framework documentation

What do you want to do?

[x] Request a change to existing documentation
[ ] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
Update the existing doucementation with details about the Gauge metric type.
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
RFC - https://github.com/opensearch-project/OpenSearch/issues/10141#issuecomment-1987093415
Issue - https://github.com/opensearch-project/OpenSearch/issues/12641
PR - https://github.com/opensearch-project/OpenSearch/pull/12642

@hdhalter fyi, this is scheduled for 2.13.0, thank you

@Gaganjuneja - Are you submitting a doc PR for this change? If this is going in 2.13, we need it ASAP.


not reversible json->xml->json

hi there
i tried running below snippet
var xmlJs = require("xml-js")
var json = {"a":[{"t":1}]}
var options = {compact: true, spaces: 4};
result1 = xmlJs.json2xml(json, options);
result2 = xmlJs.xml2json(result1, options);
console.log(result1, '\n', result2);
and the result is not identical to sources can you please help me do that ?

{compact: true is not reversible. See: https://github.com/nashwaan/xml-js#compact-vs-non-compact

{
   "a": [
      {
         "t": 1
      }
   ]
}

may be converted to xml
<?xml version="1.0" encoding="UTF-8"?>
<a array="true">
  <t number="true">1</t>
</a>

https://xmltojson.github.io/json-to-xml.html


Revert "Redirect powershell completion"

This reverts commit 65fdbf0210e8faa1598515a7fd7ef4ed33d68d43 (#27746), as it was still in use for packaging, so may need more discussion. See https://github.com/docker/docker/pull/27746#issuecomment-258063053
Signed-off-by: Sebastiaan van Stijn<EMAIL_ADDRESS>

also opened https://github.com/docker/docker/issues/28016 as an alternative
ping @jhowardmsft @icecrime PTAL

LGTM

note that if we go for https://github.com/docker/docker/pull/28016, this one isn't needed

Closing as #28016 is merged 👼


Add the possibility to have exclusion jpath

We should be able to define a list of jpath that should be excluded from the search.
The list could be in the form of string or regexp maybe

The options should be configurable in the visualizer


Creating example using Jasmine

Adding sample tests with the Jasmine framework :fire:. #11

@gustafsilva That's great! Thanks!


feat(models): Add Gemini 1.5 Pro and Gemini 1.5 Flash models

CLOSE https://github.com/sourcegraph/cody-issues/issues/212
CLOSE https://github.com/sourcegraph/cody-issues/issues/411
Server side change completed in https://github.com/sourcegraph/sourcegraph/pull/62927
This change adds two new AI models to the DEFAULT_DOT_COM_MODELS array:

Gemini 1.5 Pro
Gemini 1.5 Flash

These models are provided by Google and are only available to Cody Pro users.
The changes also update the nodeClient.ts file to handle the new Google models, ensuring they are properly processed and used for code completions.
Test plan

Gemini 1.5 Pro
Gemini 1.5 Flash

Any plans to include Codestral as FIM and instruct code model?

@PriNova I don't have any info on that unfortunately, but feel free to file a feature request on our community site if this is something you want 😄

Nice. Thank you


./esp-idf/export.sh: line 204: complete: nosort: invalid option name (IDFGH-9363)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
5bb59b00e72f8f91eb24d8c65bf9a7ea2b8a4f5f
Operating System used.
macOS
How did you build your project?
Command line with Make
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32S3
Power Supply used.
USB
What is the expected behavior?
I want to run source ./esp-idf/export.sh to run all the required code for a ci
What is the actual behavior?
The command fails and returns this error

./esp-idf/export.sh: line 204: complete: nosort: invalid option name

Steps to reproduce.
Run esp-idf/export.sh idf 4.4 on a Mac m1
Debug Logs.
No response
More Information.
No response

@MATTYGILO Are you sure that you have one copy of ESP-IDF on your computer and you are using the right one? The reported issue is for line 204 but the file has only 188 lines in the v4.4 branch (https://github.com/espressif/esp-idf/blob/release/v4.4/export.sh).
Could you please share also you bash version? (if you use other shell then please state which one and also share the version)

Ok, I see from the commit that you are actually using the master ESP-IDF (v5.1 in development). Is this intentional?

I'm closing this for inactivity.


mongodb version update

mongo 6.0.2 (latest) do not support some queries.
Fixed : Unsupported OP_QUERY command: count. The client driver may require an upgrade. For more details see https://dochub.mongodb.org/core/legacy-opcode-removal, code: 352, codeName: UnsupportedOpQueryCommand}

Thanks for the PR. It should be published within the next our.

Looks like I can't publish this at the moment until https://github.com/bytedance/unpub/pull/85 is accepted into unpubd.


Progress Indicator Color CSS Variable

We need different colors on Progress Indicator component. Can we add css variables for default progress indicator and failed progress indicator?
The design that we want to make is below;

Actually, they are already variables: --bl-color-success and --bl-color-danger. For your use-case you can customise the colors as below:
<style>
.rate-4-progress { --bl-color-success: <some-color>; }
.rate-3-progress { --bl-color-success: var(--bl-color-warning); }
.rate-2-progress { --bl-color-success: <some-color>; }
.rate-1-progress { --bl-color-success: var(--bl-color-danger); }
</style>

<bl-progress-indicator value="68" max="123"></bl-progress-indicator>
<bl-progress-indicator value="21" max="123" class="rate-4-progress"></bl-progress-indicator>
<bl-progress-indicator value="15" max="123" class="rate-3-progress"></bl-progress-indicator>
<bl-progress-indicator value="11" max="123" class="rate-2-progress"></bl-progress-indicator>
<bl-progress-indicator value="8" max="123" class="rate-1-progress"></bl-progress-indicator>

So you can override color variables in the scope of a single progress indicator. Does this make sense?

@CagriAldemir Please consider re-opening the issue if you still need help.


[FirebaseMessaging] instanceFor ?

Are you really still haven't add FirebaseMessaging.instanceFor(app:) Function ?
it exits in every firebase plugin and not in FirebaseMessaging plugin , i really don't know why !!

i found this comment:
//  Messaging does not yet support multiple Firebase Apps. Default app only.
but why !

i added this function:
  /// Returns an instance using a specified [FirebaseApp].
  static FirebaseMessaging instanceFor({required FirebaseApp app}) {
    return _firebaseMessagingInstances.putIfAbsent(app.name, () {
      return FirebaseMessaging._(app: app);
    });
  }

edited to:
  /// Returns an instance using a specified [FirebaseApp].
  static FirebaseMessaging get instanceFor({required FirebaseApp fbApp}) {
    return FirebaseMessaging._instanceFor(app: fbApp);
  }

then:
/// Returns an instance using a specified [FirebaseApp].
  static FirebaseMessaging instanceFor({required FirebaseApp app}) {
    return FirebaseMessaging._instanceFor(app: app);
  }

and it works ..

but why !

firebase_messaging does not have multi app support on the native SDKs. If you read Flutterfire's documentation for firebase_core, you will note that the native SDKs do not support secondary app usage for firebase_messaging.
You can also check out the documentation for android:
firebase_messaging only allows you to set the default app instance.
firebase_auth & cloud_firestore allow you to set the app instance.
See this issue thread for your reference: https://github.com/FirebaseExtended/flutterfire/discussions/5565
Closing as this isn't an issue and something isn't actionable from messaging plugin side.


Release v0.2.0

Discuss what are included and when it will be released here.

Maybe those would be good candidates to include in v0.2:

Checkpoints and protocol log pruning
Integration with Hyperledger Fabric (#81)
Documentation of implementation design and required protocol adjustments


Add errorlint and fix all existing issues

As per title, this seems quite useful to check imo.
/hold
Until linting version bump comes through.

/unhold

/assign @julz


Failed to transcode: Sequence contains more than one element

That's the message I get when I try to do anything with the moflex files from the Sonic Boom games. They seem to contain more than one audio track, so could that be the issue? Here's one of those files, for example.
https://drive.google.com/open?id=1Lt6cNHXTUOsgT6x6UAU8tUXi7y9XiZR6
Also, is there a way to extract audio from these files in their raw format i.e without it getting transcoded to something else? I assumed vgmstream would be able to play said raw audio format, but I'm not quite sure.

Same issue occurs when trying to convert the title screen for Pokémon Ultra Sun/Moon

This may be related (since it has to do with ffmpeg/C#): https://stackoverflow.com/questions/1256757/sequence-contains-more-than-one-element


i got syntax error for wordlist -W command

command :
skipfish -W /root/medium.txt  -S /root/medium.txt -o scanreports  http://zero.webappsecurity.com
Error:
Wordlist '/root/medium.txt': syntax error in line 0.
could you pls help me out above issue
thank you in advance

-W and -S can't point to the same file. -W should point to an empty or site specific file.


Make GatewayClient

For what thing this feature?
GatewayClient for DisBot, receiving events and sending responces

Checklist:

[ ] Adding on message support
[ ] Adding on ready support
[ ] Make new heartbeat (with cooler returns and checking)


[KALMX-62] Connection Manager Presentation Layer - Sidebar and WebViews

[ ] Expose the singleton instance with a getter instead of a publicly accessible static field
[ ] Rename Connection.url to endpoint and make it a string instead of URL


Conversion error: Data rank or shape of sizes input is required to static

I have a model that was created using Azure Machine Learning Studio.
When I try to convert the onnx model, I received the following error. What does it mean and how should I correct it?

Hi @leets0429 ,
Could you share the onnx model as well, so we can try to convert it?
Thanks, Erik

Hi @Erol444,
here is the model.
https://ailandgmbh-my.sharepoint.com/:u:/g/personal/lee_a-i_land/EcKLhm7WNDBBgzms0gQWADcB5ewe7-prXjNoaaEyDQj40Q?e=pMES7d

@tersekmatija could someone from your team look into it? I think it would be valuable to also have a tutorial on how to convert&deploy Azure Machine Learning Studio model(s) to OAK cam.
Thanks, Erik

@Erol444 I think the problem with general support for models from Azure ML is that likely not all models are supported from the drag-and-drop tools they provide. Also, customers can train their own custom models. For example the model from @leets0429 seems to be like that - either custom one or one provided by Azure ML. It seems to have some operations that cause the shape to be dynamic, which is not supported.
[ ERROR ]  Check '((sizes_shape.is_static() || data_shape.rank().is_static()))' failed at frontends/onnx/frontend/src/op/resize.cpp:155:
While validating ONNX node '<Node(Resize): Resize_2327>':
 Data rank or shape of sizes input is required to be static.

Is it possible to change the model and retrain it inside Azure ML @leets0429 ? Or get more information about the model itself - what do the predictions look like, is there some metadata available, etc.?

@tersekmatija It is our custom model. The model is a maskrcnn_resnet50_fpn, that is use to recognize sugarbeet and the output are bounding boxes, labels, scores (confidence level), mask. When validation was done in Azure ML studio it works. I think Azure by default uses Pytorch but model can be exported in onnx format.
Nevertheless, I'll ask my colleague to retrain the model with fixed orientation. The training was done using landscape and portrait images.

@leets0429
Hey, yeah, I'm afraid Mask R-CNN will not be easy to export. I'd suggest you take a look at this comment for instructions. Note that Mask R-CNN might run slowly on OAK as it's quite heavy computationally. If you do not require instance segmentation, I'd recommend you object detection (like YoloV6n) or a modified version of YOLOP if semantic segmentation is enough.
Best, Matija

@tersekmatija
I've recreate a new model (Yolov5) with static images yet the problem still persists. How should I resolved the problem? Do I need to manually convert it instead of using the blob converter. Do you have any resources regarding such topics?
I've attached the model here
https://ailandgmbh-my.sharepoint.com/:u:/g/personal/lee_a-i_land/EQoVtF7IzYxPhNfgxPnYj30Bexo5kRoOlP8IsT91_nPsmQ?e=3AHbcK

@leets0429 So, it seems that generated ONNX does not have a fixed batch size. This can be solved by specifying flag -b=1 or explicitly by --input_shape=[1,3,640,640] in Model optimizer params: under advanced settings. Note that you should clear mean_values and specify --scale=255 and --reverse_input_channels. YoloV5 expects BGR images with values in [0,1], while OAK by default outputs BGR with values in [0,255]. More info on mean values here.
Your export will still fail, that is because of the ScatterND operation in ONNX graph. This happens when you are directly changing the slices, like
x[..., 2:4] = torch.exp(x[..., 2:4]).

Currently, the only solution is to modify the code directly. See this issue for an example.
For Yolo models however, we offer the NMS and post-processing directly on device. If you can download best.pt weights saved during the model training, I'd recommend you to use our tools. Simply upload best.pt weights, define input shape, and choose Yolo version. Then open the link in the left panel for instructions on how to run your model.

@tersekmatija Correct me if I'm wrong, in order to remove the ScatterND, I have to change the code during the conversion from Pytorch to ONNX?

@leets0429 Yes it's likely the post-processing code in the Detect layer. I'd still suggest you to use tools.luxonis.com for YoloV5-V7.

@tersekmatija I've tried using your Yolo tool but it said error while loading the model.
here's my pt file
https://ailandgmbh-my.sharepoint.com/:u:/g/personal/lee_a-i_land/EWIZIq-b5wtCjJVKerb6FDwBjTagBFX0JX2xHpzGc_nVPw?e=mn4D3T

Hey @leets0429 , thanks. We will give this a look. In the meantime can you tell me if official YoloV5 repository was used to produce this .pt?

@tersekmatija I have no information on the Yolo repo. The model was trained from using Azure Automated ML.

Hm, thanks. It could be that they are using some other source code inside their tool rather than the official repo. We will investigate this with the .pt file.
Can you please also send me the ONNX model that you can export with their tool? @leets0429

@tersekmatija any updates on the Yolo tool issue?

@leets0429 Could you please share with us some examples of images and the expected outputs? So that we could test the model.

@leets0429 The issue with the model that you've shared with us is that it is a custom implementation of YoloV5 which seems to have a slightly different postprocessing. We are looking into that. I am not sure a standard support in tools.luxonis.com will be possible, but in case we can match their postprocessing with ours we can share an example of how you can export it yourself.
Besides an example of an input, do you maybe have access to the source code?
For the best plug-and-play experience I'd recommend training your model with official Ultralytics' YoloV5 GitHub repository. Not sure how feasible this is with Azure ML.

In the "input" folder, you will find the required images. As for right now, I am only able to deploy the onnx model from Azure locally. You can find it in the onnx_local_deploy folder. It is not the same model, but it uses Yolov5 too and trained through Azure. The output should be bounding boxes with label.
https://ailandgmbh-my.sharepoint.com/:f:/g/personal/lee_a-i_land/Ej_49ewtOQJMpgX73Y5Wp04BlZXGjIxMYcehJ2JLzNGAxw?e=kjyJvK
I tried to deploying the Pytorch model from Azure on my laptop but the parameter names are not configured correctly. I think this is the same issue you are facing now too. I've contacted support and hopefully I could get a solution from them in a few days.
I can find the source code but it uses Azure services, requiring certain credentials, hence I don't think you can use it.
Regarding the ScatterND problem, shouldn't your Blob Converter considered all kinds of ONNX Layer? As far as I understand ONNX was supposed to be standardized format to ease deployment. As for right now, I could manually convert pt to onnx to avoid the ScatterND issues, but in the long term, it seems troublesome to deal with such exception everytime.

Thanks, @leets0429, @HonzaCuhel will give it a look and give you some updates on the export process when we have them.
The reason I am asking for the source code is to determine whether some different post-processing is used in their YoloV5 version or not, also during the training (for example some constant subtraction). This would help us properly export the model and test it out to make sure it works. We've modified the ONNX model in the way that our DepthAI API expects it, but are seeing some false positive detections.
Regarding the ScatterND, blobconverter is using OpenVINO model optimizer and compile tool in the background which seems to support it, but they don't support ScatterNDUpdate. So, even if ONNX, which is supposed to be a general format supports some layer, it doesn't mean that all of them are supported in OpenVINO and consequently on OAK-D. You can see only supported layers and their limitations here.
As mentioned, this happens due to updating the box "slices" in the postprocessing code in YoloV5. Latest version seems to avoid that by concatenating the box locations and sizes, while this was not the case in the older versions. If you modify the postporcessing code to match that, you should be able to export it without a problem, at least to the NMS layer which could be causing some troubles as well. Note that if you succeed, NeuralNetwork node does all off the post-processing. If you train your model with official YoloV5 repository and export it using tools.luxonis.com, post-processing is not done in the NeuralNetwork, but still completely on device. The benefit is that it enables you to directly use our YoloDetectionNetwork, which you can combine with SpatialLocationCalculator for example.

@tersekmatija @HonzaCuhel I just found out that the model provided was not a well trained model. Hence false positive detections are expected. Could you provided me the modified model and also the way how you modify it so in future if I have a better model, I can do it myself? Thanks

Thank you for the info, and I apologize for the longer delay in my answer, @leets0429. Here is a Colab notebook that takes care of the conversion. I tried to export both models, and the second one (that detects salads and weed) works, but because the model is rather heavy, the performance was around 6fps when I tested it on OAK-1. So for better performance, I'd recommend using a lighter version of YoloV5 if possible.

@HonzaCuhel Hi thank you very much for the script. Could you send me the converted blob file so that I can test it on my OAK right away?

@leets0429, no problem! Yeah, absolutely. Here are the converted files.

@HonzaCuhel I'm not sure whether I deployed the model on the OAK correctly. This is my result after increasing the threshold to 0.8 or else I receive error about to much metadata.

I suspect I interpret the result incorrectly hence the weird bounding boxes. I've seen you have attached a json file too. Is that  relevant to interpretation of the result? If so, how should I used it in the OAK pipeline.
I've faced similar issue when I try to use the ONNX model on my laptop but it was resolved after correctly interpreting the result.  Hence, I suspect what I got now is due to the same cause.
I've attached my OAK pipeline script (oak_stream_custom_nn_noros.py) and also the local deployment onnx script (onnx_local_deploy_example/examples)
https://ailandgmbh-my.sharepoint.com/:u:/g/personal/lee_a-i_land/EfmqfteIqf1JogVsR6BQZCoBZ2vH29TVbn4GpvnsK9g63Q?e=wHEAnY

@leets0429
I haven't checked the export script, but the processing you are doing in the Python script is indeed incorrect. You are using a MobileNetDetectionNetwork which we use for SSDLite based detectors. You should replace it with YoloDetectionNetwork, similar as here (L66). Note that for Yolo you need to use the items from the JSON and set them as parameters of the detection network, like here (L82-L90).
You can give it a quick try using main_api.py from here by simply calling:
python3 main_api.py -m path/to/model.blob -c path/to/config.json

@tersekmatija The model is working now but the fps is quite low (around 5 fps). What are the possible ways that I can increase it? We are using the device on the moving vehicle, hence fps is quite important for us.
Another problem is how do I change the exposure of the camera with this script
https://github.com/luxonis/depthai-experiments/tree/master/gen2-yolo/device-decoding
I've tried using the updateColorCamConfig() but I received the following error.

So far I can't find any documentation about the PipelineManager in your website.


Test grouping in reports

It would be handy to be able to separate tests into groups.
With specflow you can have many different .feature files which keeps everything separated. BDDfy puts all tests from a single run into one report.
We should be able to:

Output tests into multiple reports
Filter/group tests in the html report live in the browser

Thoughts?

I don't think we need to filter out scenarios tests like when overriding the RunsOn on the HtmlConfig.
If we don't want a big report file, there should be an option to produce as many report files as we have test classes. Not just one that contains them all.
That way, our business analysts will have an easier way to check up the reports. They will only open the one with the story/class they are interested in. Is that possible right now ? If not, can this be a new feature in a futur release ?

@karlmet Thanks for the comment.
I don't recommend doing that. That would result into too many files; that said you can use RunsOn on config to put every class into its own report if you want. It should be just a couple of lines of code. See this for an example.


prisma init improvements

Select / radio buttons should be toggleable via Space instead of enter
hide password
cycle through options

Closing this as a newer init flow was implemented.


Create a variable that represents the Github package name

The github issue link currently only works when we run the installed version of the package, because we cannot determine the name of the package that the interview belongs to.
When the interview is created in the AssemblyLine Wizard, we usually know the ultimate name and destination of the Github package. The organization name will be supplied in the al_settings.yml file. We can use this information to create a link that will work even when the package is run from the playground. That will make it a lot simpler for people to get feedback from testers.

FYI the variable to use is package_name

I think this also helps the interview author as they are developing--it's handy to have the easy link to add an issue.

Without knowing how the feedback is supposed to work, I ran it from a brand new package that's only on my playground, not in github, nor installed. I thought I would get an error because this was without the "fix", but I didn't and an issue was created in AssemblyLine (https://github.com/SuffolkLITLab/docassemble-AssemblyLine/issues/275).
To me this means the current code does "work" in a sense, except that since my package is not in github, its destination is defaulted to AL, which is confusing.
Should this behavior be changed in the fix? I.e. generate an error if the package is not found in github.

Hmm, I am not sure if they fully cover what I experienced. I did NOT get any error, and an issue is created in github, only in a wrong package (AL).

That's the current behavior in feedback.yml. If no github package name is supplied, it sends it to the AL package. That made sense early on when almost all of the interviews were in MAVirtualCourt, but it doesn't make sense any more now that each project gets its own repository.
https://github.com/SuffolkLITLab/docassemble-AssemblyLine/blob/main/docassemble/AssemblyLine/data/questions/feedback.yml#L13


Support on Postgresql 13?

Hi, previously I've been running pgdiff on Postgresql 8 but now we already migrate to Postgresql 13 and soon will be Postgresql 14. However when I try to perform pgdiff, error as below appear. Changing pghba to trust/md5/scram-sha method not working. By any chance this current version of pgdiff not support. (additional option SSLMODE disable)
Error running querypq: unknown authentication response: 10

HI raimi did you solve this issue? I am facing the same issue..

HI raimi did you solve this issue? I am facing the same issue..

Hi. No. But in Postgresql 13 there already built in diff under Tools > Schema Diff . It will compare everything under that schema.

Postgresql 13 has no Tools menu. Which client are you using to connect?

please  upgraded github.com/lib/pq ，  go get github.com/lib/pq, and go build .

I have a fix for it in this in forked repo of pgdiff here https://github.com/asifhj/pgdiff/tree/master
Also have pull request here for upstream - https://github.com/joncrlsn/pgdiff/pull/55


Fix device return

Coverage remained the same at 46.03% when pulling e13cb96184a3a20c7dff4f97489e56f2daa20bf0 on fix-device-return into 39521e28da7affe6ed75a08c4929416a6d10eba8 on master.


[Feature Request] PV identifiers as tags on snapshots

It would be helpful if specific identifying information of the PV were included in a tag on the snapshot. For the sake of snapshot auditing and cost attribution.

@rbowlby what sort of information are you looking for? I think on Slack you said pod name?

+1 on this
@ncdc would be great with the pod name and maybe some more details on the namespace, cluster. Similar to the tags that are added to the volume when using pv/pvs in Kubernetes such as:

KubernetesCluster
Name (at least on AWS it's easier to get an overview of your snapshots when they include at Name tag.
Pv-name
Pvc-name
Pvc-namespace.

This issue seems to be related to https://github.com/heptio/ark/issues/278


Innovation - Using Objects

Score 2.7+/3 ( PEER GRADED BY DON TRAN )
LINK TO BLOG
Code.org
Link to Code.org Proof
Java Objects
Link to Objects Notebook
Extra

Worked with Don on Spring Calculator
Worked on HTML portion of html

Score 2.7+/3.0

[x] Completed code.org
[x] Demonstration of use of objects and classes

Completed and thorough showing of knowledge

[x] Team Project using Spring Boot

Worked together with team to create web browser calculator


HDDS-1347. In OM HA getS3Secret call Should happen only leader OM.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
24
Docker mode activated.

_ Prechecks _

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

0
mvndep
10
Maven dependency ordering for branch

+1
mvninstall
991
trunk passed

+1
compile
96
trunk passed

+1
checkstyle
26
trunk passed

+1
mvnsite
63
trunk passed

+1
shadedclient
714
branch has no errors when building and testing our client artifacts.

+1
findbugs
101
trunk passed

+1
javadoc
57
trunk passed

_ Patch Compile Tests _

0
mvndep
13
Maven dependency ordering for patch

+1
mvninstall
65
the patch passed

+1
compile
92
the patch passed

+1
cc
92
the patch passed

+1
javac
92
the patch passed

-0
checkstyle
20
hadoop-ozone: The patch generated 3 new + 0 unchanged - 0 fixed = 3 total (was 0)

+1
mvnsite
55
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
729
patch has no errors when building and testing our client artifacts.

+1
findbugs
120
the patch passed

+1
javadoc
51
the patch passed

_ Other Tests _

+1
unit
36
common in the patch passed.

-1
unit
41
ozone-manager in the patch failed.

+1
asflicense
25
The patch does not generate ASF License warnings.

3385

Reason
Tests

Failed junit tests
hadoop.ozone.om.ratis.TestOzoneManagerRatisServer

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-670/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/670

Optional Tests
dupname  asflicense  compile  javac  javadoc  mvninstall  mvnsite  unit  shadedclient  findbugs  checkstyle  cc

uname
Linux bc6beb534300 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / ec82e4c

maven
version: Apache Maven 3.3.9

Default Java
1.8.0_191

findbugs
v3.1.0-RC1

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-670/1/artifact/out/diff-checkstyle-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-670/1/artifact/out/patch-unit-hadoop-ozone_ozone-manager.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-670/1/testReport/

Max. process+thread count
438 (vs. ulimit of 5500)

modules
C: hadoop-ozone/common hadoop-ozone/ozone-manager U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-670/1/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
40
Docker mode activated.

_ Prechecks _

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

0
mvndep
68
Maven dependency ordering for branch

+1
mvninstall
1174
trunk passed

+1
compile
110
trunk passed

+1
checkstyle
31
trunk passed

+1
mvnsite
69
trunk passed

+1
shadedclient
785
branch has no errors when building and testing our client artifacts.

+1
findbugs
114
trunk passed

+1
javadoc
64
trunk passed

_ Patch Compile Tests _

0
mvndep
12
Maven dependency ordering for patch

+1
mvninstall
76
the patch passed

+1
compile
96
the patch passed

+1
cc
96
the patch passed

+1
javac
96
the patch passed

-0
checkstyle
23
hadoop-ozone: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1
mvnsite
58
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
762
patch has no errors when building and testing our client artifacts.

+1
findbugs
116
the patch passed

+1
javadoc
55
the patch passed

_ Other Tests _

+1
unit
35
common in the patch passed.

+1
unit
52
ozone-manager in the patch passed.

+1
asflicense
28
The patch does not generate ASF License warnings.

3832

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-670/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/670

Optional Tests
dupname  asflicense  compile  javac  javadoc  mvninstall  mvnsite  unit  shadedclient  findbugs  checkstyle  cc

uname
Linux 9da069f35dd1 3.13.0-153-generic #203-Ubuntu SMP Thu Jun 14 08:52:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 04f1db8

maven
version: Apache Maven 3.3.9

Default Java
1.8.0_191

findbugs
v3.1.0-RC1

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-670/2/artifact/out/diff-checkstyle-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-670/2/testReport/

Max. process+thread count
392 (vs. ulimit of 5500)

modules
C: hadoop-ozone/common hadoop-ozone/ozone-manager U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-670/2/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

Rebased this. It is ready for review.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
38
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

0
mvndep
64
Maven dependency ordering for branch

+1
mvninstall
614
trunk passed

+1
compile
349
trunk passed

+1
checkstyle
61
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
797
branch has no errors when building and testing our client artifacts.

+1
javadoc
148
trunk passed

0
spotbugs
419
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
612
trunk passed

_ Patch Compile Tests _

0
mvndep
27
Maven dependency ordering for patch

+1
mvninstall
536
the patch passed

+1
compile
357
the patch passed

+1
cc
357
the patch passed

+1
javac
357
the patch passed

+1
checkstyle
64
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
632
patch has no errors when building and testing our client artifacts.

-1
javadoc
96
hadoop-ozone generated 1 new + 26 unchanged - 0 fixed = 27 total (was 26)

+1
findbugs
665
the patch passed

_ Other Tests _

+1
unit
329
hadoop-hdds in the patch passed.

-1
unit
3436
hadoop-ozone in the patch failed.

+1
asflicense
44
The patch does not generate ASF License warnings.

9101

Reason
Tests

Failed junit tests
hadoop.ozone.scm.pipeline.TestPipelineManagerMXBean

hadoop.ozone.client.rpc.TestOzoneAtRestEncryption

hadoop.ozone.ozShell.TestOzoneShell

hadoop.ozone.scm.node.TestQueryNode

hadoop.ozone.container.TestContainerReplication

hadoop.ozone.om.TestOzoneManagerHA

hadoop.ozone.client.rpc.Test2WayCommitInRatis

hadoop.ozone.dn.scrubber.TestDataScrubber

hadoop.ozone.container.server.TestSecureContainerServer

hadoop.ozone.ozShell.TestS3Shell

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-670/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/670

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle cc

uname
Linux 1cbd7ceb0ff2 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 8fc6567

Default Java
1.8.0_222

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-670/6/artifact/out/diff-javadoc-javadoc-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-670/6/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-670/6/testReport/

Max. process+thread count
4302 (vs. ulimit of 5500)

modules
C: hadoop-hdds/common hadoop-ozone/common hadoop-ozone/integration-test hadoop-ozone/ozone-manager U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-670/6/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
76
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

0
mvndep
23
Maven dependency ordering for branch

+1
mvninstall
663
trunk passed

+1
compile
392
trunk passed

+1
checkstyle
78
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
961
branch has no errors when building and testing our client artifacts.

+1
javadoc
183
trunk passed

0
spotbugs
450
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
663
trunk passed

_ Patch Compile Tests _

0
mvndep
33
Maven dependency ordering for patch

+1
mvninstall
618
the patch passed

+1
compile
416
the patch passed

+1
cc
416
the patch passed

+1
javac
416
the patch passed

+1
checkstyle
85
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
779
patch has no errors when building and testing our client artifacts.

-1
javadoc
96
hadoop-ozone generated 1 new + 26 unchanged - 0 fixed = 27 total (was 26)

+1
findbugs
691
the patch passed

_ Other Tests _

+1
unit
352
hadoop-hdds in the patch passed.

-1
unit
2280
hadoop-ozone in the patch failed.

+1
asflicense
42
The patch does not generate ASF License warnings.

8660

Reason
Tests

Failed junit tests
hadoop.ozone.client.rpc.TestCommitWatcher

hadoop.ozone.container.ozoneimpl.TestOzoneContainer

hadoop.ozone.client.rpc.TestOzoneClientRetriesOnException

hadoop.ozone.client.rpc.TestBlockOutputStreamWithFailures

hadoop.ozone.container.server.TestSecureContainerServer

hadoop.hdds.scm.pipeline.TestRatisPipelineCreateAndDestory

hadoop.ozone.om.TestOzoneManagerHA

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-670/7/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/670

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle cc

uname
Linux 7f29569600a6 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 69ddb36

Default Java
1.8.0_222

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-670/7/artifact/out/diff-javadoc-javadoc-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-670/7/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-670/7/testReport/

Max. process+thread count
4912 (vs. ulimit of 5500)

modules
C: hadoop-hdds/common hadoop-ozone/common hadoop-ozone/integration-test hadoop-ozone/ozone-manager U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-670/7/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

Thank You @arp7 for the review.
I have committed this to the trunk.


Why is GenerateEmbeddingsResponse Vec instead of Vec?

It appears that Ollama generates 32-bit floats for its embeddings.
See this line of code: https://github.com/ollama/ollama/blob/108fb6c1d1c33265dc8f10073f9540e76b820ef9/api/types.go#L268
However, the GenerateEmbeddingsResponse type in the API outputs a vector of 64-bit floating-point numbers (Vec<f64>). Is there a specific reason for this?

I don't remember the specific reason why I chose f64 over f32 but yeah it does look wrong, I'll make a PR


external checks that report errors very quickly sometimes do not register the error

When checks report errors very quickly, without waiting even a couple seconds, the failure does not get properly written into the khstate custom resource.
This can be seen in the upcoming check for external pod restarts in #224.

I believe this is actually issue #251 so I am closing it for now.


feat: use apollo server v3 and set default page to graphql playground

Update example to use Apollo v3 and also add graphql playground as default instead of Apollo Studio. I found it confusing that it takes to studio cause I just want to be able to query and see it work.
Fixes #603

Should be good now @dotansimha


Trying to build on FreeBSD

Trying to build on FreeBSD, compilation stops at
[  5%] Built target resources
[  6%] Building C object CMakeFiles/lmdb.dir/lmdb/libraries/liblmdb/mdb.c.o
/tmp/executor/lmdb/libraries/liblmdb/mdb.c:5169:14: error: variable has incomplete
      type 'union semun'
        union semun semu;
                    ^
/tmp/executor/lmdb/libraries/liblmdb/mdb.c:5169:8: note: forward declaration of
      'union semun'
        union semun semu;
              ^
1 error generated.
gmake[2]: *** [CMakeFiles/lmdb.dir/build.make:82: CMakeFiles/lmdb.dir/lmdb/libraries/liblmdb/mdb.c.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:445: CMakeFiles/lmdb.dir/all] Error 2
gmake: *** [Makefile:182: all] Error 2

As a workaround, in lmdb/libraries/liblmdb/mdb.c delete #ifdef _SEM_SEMUN_UNDEFINED and the next #endif.

Next issue:
[ 25%] Generating parse.tab.cpp
ld-elf.so.1: /usr/local/bin/bison: Undefined symbol<EMAIL_ADDRESS>gmake[2]: *** [src/CMakeFiles/romlib.dir/build.make:586: src/parse.tab.cpp] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:845: src/CMakeFiles/romlib.dir/all] Error 2

Probably need something like
#if defined(OS_MACOSX) || defined(OS_SOLARIS) || defined(OS_FREEBSD) ||\
    defined(OS_NETBSD) || defined(OS_OPENBSD) || defined(OS_DRAGONFLYBSD) ||\
    defined(OS_ANDROID) || defined(CYGWIN) || defined(OS_AIX)
// Use fread/fwrite/fflush on platforms without _unlocked variants
#define fread_unlocked fread
#define fwrite_unlocked fwrite
#define fflush_unlocked fflush
#endif

somewhere...

[  6%] Building C object CMakeFiles/lmdb.dir/lmdb/libraries/liblmdb/mdb.c.o
/tmp/executor/lmdb/libraries/liblmdb/mdb.c:5169:14: error: variable has incomplete
      type 'union semun'
        union semun semu;

lmdb is an upstream project (https://github.com/LMDB/lmdb/); you could check if they've already fixed the problem upstream and report it to them otherwise.
[ 25%] Generating parse.tab.cpp
ld-elf.so.1: /usr/local/bin/bison: Undefined symbol<EMAIL_ADDRESS>
Apparently the bison binary you have installed crashes. Looks like it's this problem: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253452
The conclusion there seems to be:

Short version is that project no longer distribute pre-built packages for 12.1,
since this release is no longer supported.  You need to build on your own, or
update to a supported release.

Apparently the bison binary you have installed crashes.

You are right, I was looking in the wrong place. It's indeed an issue with the bison on my system.

Now running into
[ 57%] Building CXX object src/CMakeFiles/romlib.dir/serial.cpp.o
/tmp/executor/src/serial.cpp:200:19: error: field has incomplete type 'struct sgttyb'
    struct sgttyb sgttyb;
                  ^
/tmp/executor/src/serial.cpp:200:12: note: forward declaration of 'sgttyb'
    struct sgttyb sgttyb;
           ^
/tmp/executor/src/serial.cpp:201:19: error: field has incomplete type 'struct tchars'
    struct tchars tchars;
                  ^
/tmp/executor/src/serial.cpp:201:12: note: forward declaration of 'tchars'
    struct tchars tchars;
           ^
/tmp/executor/src/serial.cpp:541:19: error: variable has incomplete type
      'struct sgttyb'
    struct sgttyb sgttyb;
                  ^
/tmp/executor/src/serial.cpp:200:12: note: forward declaration of 'sgttyb'
    struct sgttyb sgttyb;
           ^
/tmp/executor/src/serial.cpp:542:19: error: variable has incomplete type
      'struct tchars'
    struct tchars tchars;
                  ^
/tmp/executor/src/serial.cpp:201:12: note: forward declaration of 'tchars'
    struct tchars tchars;
           ^
/tmp/executor/src/serial.cpp:616:21: error: use of undeclared identifier 'LPASS8'
            csize = OURCS8;
                    ^
/tmp/executor/src/serial.cpp:521:17: note: expanded from macro 'OURCS8'
#define OURCS8 (LPASS8)
                ^
/tmp/executor/src/serial.cpp:624:22: error: use of undeclared identifier 'ODDP'
            parity = OURODDP;
                     ^
/tmp/executor/src/serial.cpp:524:18: note: expanded from macro 'OURODDP'
#define OURODDP (ODDP)
                 ^
/tmp/executor/src/serial.cpp:628:22: error: use of undeclared identifier 'EVENP'
            parity = OUREVENP;
                     ^
/tmp/executor/src/serial.cpp:525:19: note: expanded from macro 'OUREVENP'
#define OUREVENP (EVENP)
                  ^
/tmp/executor/src/serial.cpp:665:27: error: use of undeclared identifier 'TANDEM'
        sgttyb.sg_flags = TANDEM | CBREAK | parity;
                          ^
/tmp/executor/src/serial.cpp:665:36: error: use of undeclared identifier 'CBREAK'
        sgttyb.sg_flags = TANDEM | CBREAK | parity;
                                   ^
/tmp/executor/src/serial.cpp:683:20: error: use of undeclared identifier 'LLITOUT'
        lclmode |= LLITOUT | LNOHANG | csize | LNOFLSH;
                   ^
/tmp/executor/src/serial.cpp:683:30: error: use of undeclared identifier 'LNOHANG'
        lclmode |= LLITOUT | LNOHANG | csize | LNOFLSH;
                             ^
/tmp/executor/src/serial.cpp:683:48: error: use of undeclared identifier 'LNOFLSH'
        lclmode |= LLITOUT | LNOHANG | csize | LNOFLSH;
                                               ^
/tmp/executor/src/serial.cpp:684:22: error: use of undeclared identifier 'TIOCSETP'
        if(ioctl(fd, TIOCSETP, &sgttyb) < 0 || ioctl(fd, TIOCSETC, &tchars) < ...
                     ^
/tmp/executor/src/serial.cpp:684:58: error: use of undeclared identifier 'TIOCSETC'
        if(ioctl(fd, TIOCSETP, &sgttyb) < 0 || ioctl(fd, TIOCSETC, &tchars) < ...
                                                         ^
/tmp/executor/src/serial.cpp:684:94: error: use of undeclared identifier 'TIOCLSET'
  ...&sgttyb) < 0 || ioctl(fd, TIOCSETC, &tchars) < 0 || ioctl(fd, TIOCLSET, &lclmo...
                                                                   ^
/tmp/executor/src/serial.cpp:704:19: error: variable has incomplete type
      'struct sgttyb'
    struct sgttyb sgttyb;
                  ^
/tmp/executor/src/serial.cpp:200:12: note: forward declaration of 'sgttyb'
    struct sgttyb sgttyb;
           ^
/tmp/executor/src/serial.cpp:705:19: error: variable has incomplete type
      'struct tchars'
    struct tchars tchars;
                  ^
/tmp/executor/src/serial.cpp:201:12: note: forward declaration of 'tchars'
    struct tchars tchars;
           ^
/tmp/executor/src/serial.cpp:714:18: error: use of undeclared identifier 'TIOCGETP'
    if(ioctl(fd, TIOCGETP, &sgttyb) < 0 || ioctl(fd, TIOCGETC, &tchars) < 0)
                 ^
/tmp/executor/src/serial.cpp:714:54: error: use of undeclared identifier 'TIOCGETC'
    if(ioctl(fd, TIOCGETP, &sgttyb) < 0 || ioctl(fd, TIOCGETC, &tchars) < 0)
                                                     ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
gmake[2]: *** [src/CMakeFiles/romlib.dir/build.make:2784: src/CMakeFiles/romlib.dir/serial.cpp.o] Fehler 1
gmake[1]: *** [CMakeFiles/Makefile2:846: src/CMakeFiles/romlib.dir/all] Fehler 2
gmake: *** [Makefile:182: all] Fehler 2

Ah, the serial port support code.
Lots of old stuff in there. I haven't touched that code much myself.
At some point in the past, this code probably worked on various other UNIX systems which might be much closer to FreeBSD than to Linux, and it has #ifdefs for APPLE and works on Macs, so you might get it to work by experimenting with the various #ifdefs near the top.
Alternatively, you should get away with #if 0-ing everything starting from line 183 and adding a trivial empty void Executor::InitSerialDriver() {} instead. That'll just mean that the serial port driver wouldn't exist.

Looks like the right thing to do would be to use sgtty instead of termios. But indeed Serial is not important for me at the moment at all.
#if defined(__APPLE__)
// FIXME: #warning bad serial support right now
//TODO: this seems to use sgtty functions instead of termios.
#include <sgtty.h>
#endif /* !defined (__APPLE__) */

Alternatively, you should get away with #if 0-ing everything starting from line 183 and adding a trivial empty void Executor::InitSerialDriver() {} instead. That'll just mean that the serial port driver wouldn't exist.

This gets me to compile further. Thank you very much :+1:

Towards the end the missing Serial seems to be an issue again?
[ 89%] Built target romlib
[ 89%] Built target front-end-headless
[ 91%] Built target front-end-sdl
[ 91%] Linking CXX executable ../executor-sdl
ld: error: undefined symbol: C_ROMlib_serialopen(Executor::ParamBlockRec*, Executor::DCtlEntry*)
>>> referenced by serial.cpp
>>>               serial.cpp.o:(Executor::traps::WrappedFunction<short (Executor::ParamBlockRec*, Executor::DCtlEntry*), &(C_ROMlib_serialopen(Executor::ParamBlockRec*, Executor::DCtlEntry*)), Executor::callconv::Register<Executor::callconv::D<0> (Executor::callconv::A<0>, Executor::callconv::A<1>)> >::init()::'lambda'(unsigned int)::operator()(unsigned int) const) in archive libromlib.a

ld: error: undefined symbol: C_ROMlib_serialopen(Executor::ParamBlockRec*, Executor::DCtlEntry*)
>>> referenced by serial.cpp
>>>               serial.cpp.o:(Executor::traps::WrappedFunction<short (Executor::ParamBlockRec*, Executor::DCtlEntry*), &(C_ROMlib_serialopen(Executor::ParamBlockRec*, Executor::DCtlEntry*)), Executor::callconv::Register<Executor::callconv::D<0> (Executor::callconv::A<0>, Executor::callconv::A<1>)> >::init()::'lambda'(PowerCore&)::operator()(PowerCore&) const) in archive libromlib.a

ld: error: undefined symbol: C_ROMlib_serialprime(Executor::ParamBlockRec*, Executor::DCtlEntry*)
>>> referenced by serial.cpp
>>>               serial.cpp.o:(Executor::traps::WrappedFunction<short (Executor::ParamBlockRec*, Executor::DCtlEntry*), &(C_ROMlib_serialprime(Executor::ParamBlockRec*, Executor::DCtlEntry*)), Executor::callconv::Register<Executor::callconv::D<0> (Executor::callconv::A<0>, Executor::callconv::A<1>)> >::init()::'lambda'(unsigned int)::operator()(unsigned int) const) in archive libromlib.a

ld: error: undefined symbol: C_ROMlib_serialprime(Executor::ParamBlockRec*, Executor::DCtlEntry*)
>>> referenced by serial.cpp
>>>               serial.cpp.o:(Executor::traps::WrappedFunction<short (Executor::ParamBlockRec*, Executor::DCtlEntry*), &(C_ROMlib_serialprime(Executor::ParamBlockRec*, Executor::DCtlEntry*)), Executor::callconv::Register<Executor::callconv::D<0> (Executor::callconv::A<0>, Executor::callconv::A<1>)> >::init()::'lambda'(PowerCore&)::operator()(PowerCore&) const) in archive libromlib.a

ld: error: undefined symbol: C_ROMlib_serialctl(Executor::ParamBlockRec*, Executor::DCtlEntry*)
>>> referenced by serial.cpp
>>>               serial.cpp.o:(Executor::traps::WrappedFunction<short (Executor::ParamBlockRec*, Executor::DCtlEntry*), &(C_ROMlib_serialctl(Executor::ParamBlockRec*, Executor::DCtlEntry*)), Executor::callconv::Register<Executor::callconv::D<0> (Executor::callconv::A<0>, Executor::callconv::A<1>)> >::init()::'lambda'(unsigned int)::operator()(unsigned int) const) in archive libromlib.a

ld: error: undefined symbol: C_ROMlib_serialctl(Executor::ParamBlockRec*, Executor::DCtlEntry*)
>>> referenced by serial.cpp
>>>               serial.cpp.o:(Executor::traps::WrappedFunction<short (Executor::ParamBlockRec*, Executor::DCtlEntry*), &(C_ROMlib_serialctl(Executor::ParamBlockRec*, Executor::DCtlEntry*)), Executor::callconv::Register<Executor::callconv::D<0> (Executor::callconv::A<0>, Executor::callconv::A<1>)> >::init()::'lambda'(PowerCore&)::operator()(PowerCore&) const) in archive libromlib.a

ld: error: undefined symbol: C_ROMlib_serialstatus(Executor::ParamBlockRec*, Executor::DCtlEntry*)
>>> referenced by serial.cpp
>>>               serial.cpp.o:(Executor::traps::WrappedFunction<short (Executor::ParamBlockRec*, Executor::DCtlEntry*), &(C_ROMlib_serialstatus(Executor::ParamBlockRec*, Executor::DCtlEntry*)), Executor::callconv::Register<Executor::callconv::D<0> (Executor::callconv::A<0>, Executor::callconv::A<1>)> >::init()::'lambda'(unsigned int)::operator()(unsigned int) const) in archive libromlib.a

ld: error: undefined symbol: C_ROMlib_serialstatus(Executor::ParamBlockRec*, Executor::DCtlEntry*)
>>> referenced by serial.cpp
>>>               serial.cpp.o:(Executor::traps::WrappedFunction<short (Executor::ParamBlockRec*, Executor::DCtlEntry*), &(C_ROMlib_serialstatus(Executor::ParamBlockRec*, Executor::DCtlEntry*)), Executor::callconv::Register<Executor::callconv::D<0> (Executor::callconv::A<0>, Executor::callconv::A<1>)> >::init()::'lambda'(PowerCore&)::operator()(PowerCore&) const) in archive libromlib.a

ld: error: undefined symbol: C_ROMlib_serialclose(Executor::ParamBlockRec*, Executor::DCtlEntry*)
>>> referenced by serial.cpp
>>>               serial.cpp.o:(Executor::traps::WrappedFunction<short (Executor::ParamBlockRec*, Executor::DCtlEntry*), &(C_ROMlib_serialclose(Executor::ParamBlockRec*, Executor::DCtlEntry*)), Executor::callconv::Register<Executor::callconv::D<0> (Executor::callconv::A<0>, Executor::callconv::A<1>)> >::init()::'lambda'(unsigned int)::operator()(unsigned int) const) in archive libromlib.a

ld: error: undefined symbol: C_ROMlib_serialclose(Executor::ParamBlockRec*, Executor::DCtlEntry*)
>>> referenced by serial.cpp
>>>               serial.cpp.o:(Executor::traps::WrappedFunction<short (Executor::ParamBlockRec*, Executor::DCtlEntry*), &(C_ROMlib_serialclose(Executor::ParamBlockRec*, Executor::DCtlEntry*)), Executor::callconv::Register<Executor::callconv::D<0> (Executor::callconv::A<0>, Executor::callconv::A<1>)> >::init()::'lambda'(PowerCore&)::operator()(PowerCore&) const) in archive libromlib.a

ld: error: undefined symbol: SDLVideoDriver::putScrap(int, int, char*, int)
>>> referenced by sdlwin.cpp
>>>               sdlwin.cpp.o:(vtable for SDLVideoDriver) in archive config/front-ends/sdl/libfront-end-sdl.a

ld: error: undefined symbol: SDLVideoDriver::getScrap(int, Executor::guestvalues::GuestWrapper<char*>*)
>>> referenced by sdlwin.cpp
>>>               sdlwin.cpp.o:(vtable for SDLVideoDriver) in archive config/front-ends/sdl/libfront-end-sdl.a

ld: error: undefined symbol: we_lost_clipboard()
>>> referenced by sdlevents.cpp
>>>               sdlevents.cpp.o:(SDLVideoDriver::runEventLoop()) in archive config/front-ends/sdl/libfront-end-sdl.a
c++: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[2]: *** [src/CMakeFiles/executor-sdl.dir/build.make:118: executor-sdl] Fehler 1
gmake[1]: *** [CMakeFiles/Makefile2:750: src/CMakeFiles/executor-sdl.dir/all] Fehler 2
gmake: *** [Makefile:182: all] Fehler 2

Ah, about the serial stuff, I overlooked that: #if 0 lines 84-94 of serial.cpp, those REGISTER_FUNCTION_PTR macros generate references to some functions that I told you to remove before.

And the scrap (clipboard) code in the old SDL1 frontend is a big mess. The only reason I haven't deleted the whole thing yet is that I didn't get around to reimplementing it yet...
It's got an #ifdef __linux__ clause that actually should apply to SDL1 on X11. And apparently there's an #ifdef WIN32 that for some reason ended up inside this #ifdef __linux__ by mistake, which makes no sense at all.
Anyway, first try the #ifdef __linux__ in line 221 (change it to #ifdef __unix__ or #if 1 or something, I mean), and if all else fail, activate the #ifdef __APPLE__ code near the bottom of the file...

Thanks @autc04
Look what I have running: Executor2000 on helloSystem FreeBSD

What is the proper way to tell CMake to only configure and make the SDL2 version and not care about SDL1?

So far, there's no 'proper' way, the scripts just configure everything that has the prerequisites installed.
Rootless mode is currently implemented in the Qt and Wayland versions, not in the others. The Wayland version probably contains a few linuxisms, but the Qt version should be portable.

Ah, it looks like the Qt version didn't get built...

It seems like there is some sort of fully transparent window.  Can that transparent window be made fullscreen?

Then I will need to find a way to patch away all build variants from the "Makefile" but the Qt one. I say "Makefile" in quptes because I have not found yet the place where to do this.

Submitted a patch to FreeBSD Ports:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254743


LTR Backup Geo-Redundancy Clarification

Dear Azure Documentation Team,
I am writing to seek clarification regarding the backup storage redundancy for long-term retention (LTR) policies in Azure SQL Managed Instance, as outlined in your article "Automated backups in Azure SQL Managed Instance" dated July 12, 2023.
The article comprehensively covers the automated backup features, including the types of backups (full, differential, and transaction log) and their frequencies. It also details the backup storage redundancy options available, such as Locally Redundant Storage (LRS), Zone-Redundant Storage (ZRS), Geo-Redundant Storage (GRS), and Geo-Zone-Redundant Storage (GZRS).
While the article mentions that by default, Azure SQL Managed Instance stores data in geo-redundant storage blobs, it is not explicitly clear whether this default geo-redundancy applies to backups configured under long-term retention policies. My understanding is that built-in backups are geo-redundant by default. However, I am uncertain if this is also the case for LTR backups.
Could you please clarify the following points?
Are backups configured using long-term retention policies in Azure SQL Managed Instance (and also Azure SQL DBs) geo-redundant by default?
Where are these LTR backups stored specifically?
Is the geo-redundancy of LTR backups configurable, and if so, how can it be configured?
Your clarification on these points will greatly aid in understanding and effectively utilizing Azure's backup services for compliance with data protection rules and disaster recovery strategies.
Thank you for your assistance and looking forward to your response.
Best regards, Maxim

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

ID: d1da21a2-6d3c-ef21-4355-fd90a9f38083
Version Independent ID: dab1dcbb-41d7-0fb2-7105-250c16bb43c0
Content: Automatic, geo-redundant backups - Azure SQL Managed Instance
Content Source: azure-sql/managed-instance/automated-backups-overview.md
Service: sql-managed-instance
Sub-service: backup-restore
GitHub Login: @Stralle
Microsoft Alias: strrodic

@sokoloffmaks
Thanks for your feedback! We will investigate and update as appropriate.

Hi @Stralle,
Could you please look into this, thanks.

Hi, Maxim,
In the linked article under section "Long-Term Retention" it's stated: "LTR backup storage redundancy in Azure SQL Managed Instance is inherited from the backup storage redundancy used by STR at the time that the LTR policy is defined. You can't change it, even if the STR backup storage redundancy changes in the future." => this means that if you create it with Geo-Redundant storage option it will remain geo-redundant in the future as well.
For SQL DB LTR follows redundancy change for STR backups.
Backups for Azure SQL (both DB and MI) are stored on Microsoft-managed Azure storage accounts. These cannot be accessed by customers neither customers can manage files on those storage accounts. Customer can affect lifespan of these backup files through retention period configuration for STR backups, while LTR backups can be deleted if needed through Azure SQL interface.


src: code style

This PR has some goals:

To make more easy for me to understand some parts.
Part of #48
To help with #69 and #68

A brief description of this PR would be:

Modification of attribute names and functions that conflicted a bit with names from another "universe of
use".
Extraction of functions
Some redundancy reduction
Some line comments added

Coverage decreased (-0.06%) to 93.277% when pulling 5e6c23e86ba365389e2723bb618046e7a411930e on helio-frota:inline-doc into f3e2f72c1ec80e6f68be657ed4b911caa527e568 on bucharest-gold:master.


Ambiguous error handling

I'm writing a wrapper for ZStd and faced with a problem.
AFAIK, currently in ZStd there's two ways to remember error code before it will be retrieved by user through some wrapper function:

Remember error code as last size_t for which ZSTD_isError() (ZBUFF_isError() in my case, but who cares?) has returned TRUE.
Convert errorneous size_t values to the ZSTD_ErrorCode enum value and store it.

The problem is this:

In first case, I can't preliminarily initialize error variable by some NO_ERROR value because size_t error codes are undocumented, could change in the future etc. Also I can't reset internal error state to NO_ERROR after the user has received an error code.
In second case, I can't write an interface function to get error description string properly because there's no version of ZSTD_getErrorName() for ZSTD_ErrorCode values.

I know that the possible solution is to store both size_t and ZSTD_ErrorCode values, but I'm sure that things could be done better from ZStd side.
Forgive me in advance for amazingly awful English.

Are you using a language that supports exceptions? I've written a .NET wrapper, and I'm converting the errors into exceptions that are thrown back to the caller when they happen. This solves a lot of problems since now all my API return 'long' for sizes, or throw exception in case of errors (with the error code translated into text).
If your language does not have exceptions, but supports tuples or something equivalent, you could maybe return pairs of (bool, long) with (true, 1234) for success, and (false, error_code) for failure?

KrzysFR, all wrappers are written in Pure (?) C, and the interface is very simple.

A few thoughts on reading your pretty good comments :

Between options 1 and 2, 2 looks the cleaner one
There is no function yet to provide the error string from the enum => that's a show stopper. I shall create one.
I'm considering changing  ZSTD_getErrorName() into  ZSTD_getErrorString(), because it used to be a single word (the stringification of the enum), but now it can be a complete sentence, so Name looks less logical.

I can't preliminarily initialize error variable by some NO_ERROR value because size_t error codes are undocumented, could change in the future etc.

Indeed, they may change, but the value 0 is hard-coded to always mean "No error"

Completely agree.

Indeed, they may change, but the value 0 is hard-coded to always mean "No error"

Yes, it is, and currently things are done by using my own definition of ZSTD_NO_ERROR=0 for size_t. But in my opinion, it's not a good code style when I should make my own definitions for some third-party library.

Trying to complete this issue in preparation of v0.6.1 :
If I do understand correctly, your need would be answered by a function like ZSTD_getErrorName() but using an enum ZSTD_ErrorCode as input parameter ?

To be more precise, I'm considering the following API (to become part of zstd_static.h) :
ZSTD_ErrorCode ZSTD_getErrorCode(size_t functionResult);
const char* ZSTD_getErrorString(ZSTD_ErrorCode code);

Would the call to ZSTD_getErrorCode still be optional? Marshalling from managed languages to native has some cost so I would hope that this method could be replicated from the managed side and still be as simple as the current one.
For ZSTD_getErrorString this is less of an issue (only for exceptional cases and can be cached)

On 10 May 2016, at 13:45, Yann Collet<EMAIL_ADDRESS>wrote:
To be more precise, I'm considering the following API (to become part of zstd_static.h) :
ZSTD_ErrorCode ZSTD_getErrorCode(size_t functionResult);
const char* ZSTD_getErrorString(ZSTD_ErrorCode code);
―
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

Would the call to ZSTD_getErrorCode still be optional?

Yes.
ZSTD_getErrorCode() would be part of zstd_static.h for the foreseeable future, which is optional.
The usual error functions defined within zstd.h would remain available as-is : ZSTD_isError() and ZSTD_getErrorName().
I feel the naming distinction between ZSTD_getErrorName() and ZSTD_getErrorString() is pretty poor, but on the other hand, I'm reluctant modifying functions already defined within zstd.h, as they are supposed to be stable.

FYI, in my wrapper I do not call ZSTD_isError and simply replicate it into a static method that gets inlined by the .NET CLR, vs a virtual dispatch going through marshalling after every call.
Hopefully this will not change in the future :)

On 10 May 2016, at 14:47, Yann Collet<EMAIL_ADDRESS>wrote:
Would the call to ZSTD_getErrorCode still be optional?
Yes.
ZSTD_getErrorCode() would be part of zstd_static.h for the foreseeable future, which is optional.
The usual error functions defined within zstd.h would remain available as-is : ZSTD_isError() and ZSTD_getErrorName().
I feel the naming distinction between ZSTD_getErrorName() and ZSTD_getErrorString() is pretty poor, but on the other hand, I'm reluctant modifying functions already defined within zstd.h, as they are supposed to be stable.
―
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

Proposal uploaded into "dev" branch

New method introduced within v0.6.1


Implement Tuple2#swap

Fix #1406

[Current coverage][cc-pull] is 97.25%

Merging [#1411][cc-pull] into [master][cc-base-branch] will increase coverage by <.01%

@@             master      #1411   diff @@
==========================================
  Files            86         86
  Lines         10306      10307     +1
  Methods           0          0
  Messages          0          0
  Branches       1823       1823
==========================================
+ Hits          10022      10024     +2
  Misses          156        156
+ Partials        128        127     -1

Powered by Codecov. Last updated by [bd24a7b...726ffed][cc-compare]
[cc-base-branch]: https://codecov.io/gh/javaslang/javaslang/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/javaslang/javaslang/compare/bd24a7b61609c7b7e80e5a9bf8f3c7ebf9a1da1d...726ffed64a9b6e04537e4dd4ed9d24b9b997db3c
[cc-pull]: https://codecov.io/gh/javaslang/javaslang/pull/1411?src=pr

Great, thank you!


feat: Add session fragment

Detail:

Add session fragment to show all details of a session.
Fix network call on session + adding sessions to database.

Fixes: #1691
Screenshots for the change:

@anhanh11001 i already completed this PR and was waiting for #1646 to get merged

@anhanh11001 build is failing

@aggarwalpulkit596 I fixed the view. Please review

@iamareebjamal please review

@liveHarshit @nikit19 please review again, this PR has been here for a while

@iamareebjamal please review


Expose testing methods

Similar to numpy's numpy.testing module, I would find it useful for xarray to expose some of its testing methods, particularly those in its base TestCase.
I imagine other folks whose packages and/or modules derive heavily from xarray would find this useful too.  For now I am just copy-pasting xarray's code for these methods into my testing modules.

:+1:

Most of these are as simple as assert d1.identical(d2) or assert d1.equals(d2) (see here for more details on these methods). I'd be OK with adding these methods in a dedicated testing module, though.

Indeed.  I'm happy to do this sometime (eventually...), but if somebody ends up with a pressing need for this in the meantime, go for it.  Thanks!

@spencerahill - have you made any progress here?  If not we (@dgergel) may be able to help out.

Thanks for the ping.  Sorry, I haven't.  I'm actually submitting my PhD thesis in ~2 months and then defending it this summer, so I won't be able to help much until August or September.  So by all means, go for it.

I'd be willing to prepare a PR, if this is still actual. Today I needed the *AllClose methods for my tests, I think it would be great to have these methods exposed.
I think I have an idea on how to proceed, but maybe I am underestimating the required amount of work.
Numpy for example has the np.allclose and np.testing.assert_allclose functions. Should xarray also have a xr.allclose function or are we happy with a xr.testing.assert_allclose alone? Also, the current xarray implementation has a different function for variables, datasets and coordinates: could these be merged in a generic assert_allclose which takes decisions on what to do based on the input type?


adding text

What is Semantic HTML?
2. What is HTML used for?
3. What is an attribute and where do we put it?
4. What is the h1 tag used for? How many times should I use it on a page?
5. Name two tags that have required attributes
6. What do we put in the head of our HTML document?
7. What is an id?
8. What elements can I add an id to?
9. How many times can I use the same id on a page?
10. What is a class?
11. What elements can I add a class to?
12. How many times can I use the same class on a page?
13. How do I get my link to open in a new tab?
14. What is the alt attribute used for?
15. How do I reference an id?
16. What is the difference between a section and a div
17. What is CSS used for?
18. How to we select an element? Example - every h2 on the page
19. What is the difference between a class and an id? - Give me an example of when I might use each one
20. How do we select classes in CSS?
21. How do we select a p element with a single class of “human””?
22. What is a parent child selector? When would this be useful?
23. How do you select all links within a div with the class of sidebar?
24. What is a pseudo selector?
25. What do we use the change the spacing between lines?
26. What do we use to change the spacing between letters?
27. What do we use to to change everything to CAPITALS? lowercase? Capitalize?
28. How do I add a 1px border around my div that is dotted and black?
29. How do I select everything on the page?
30. How do I write a comment in CSS?
31. How do I find out what file I am in, when I am using the command line?
32. Using the command line - how do I see a list of files/folders in my current folder?
33. How do I remove a file via the command line? Why do I have to be careful with this?
34. Why should I use version control?
35. How often should I commit to github?
36. What is the command we would use to push our repo up to github?
37. Walk me through Lambda's git flow.

Great Job!


Issue #551 Make grid configurable from xml/APIs

Hi, this pull request is in reference to issue #551 posted by @RoboErikG. This is also my first time contributing to the library, so I signed the CLA agreement. Hope everything with the pull request is okay and I am open to all feedback.

This change is

Thanks, Travis!
You're on the right track, but a few of the pieces need to move around. The library is set up to make it easy to add flags to the fragments, so most of the time we prefer configuration to be done at that level. You should move the attribute up to WorkspaceFragment and then add a quick demo by changing the default for one of the flyout demos (styled_content.xml or always_open_toolbox.xml)

Looks good. Missed it earlier, but please make the pull request against the develop branch and I'll merge it in.


Upcoming major releases of Chocolatey products that may impact functionality on the Chocolatey cookbook

I'm the Technical Engineering Manager at Chocolatey Software, Inc. and I wanted to make sure you are aware that there will be a new major release of Chocolatey products soon. As it is a major release, we are making changes that may have an impact on the Chocolatey cookbook, such as #13368.
We have beta versions of Chocolatey CLI and Chocolatey GUI publicly available that you can test against.
The release notes for the various products are below (some may or may not be applicable to the module, but I wanted to list them all for completeness):

Chocolatey CLI
Chocolatey Licensed Extension
Chocolatey Agent
Chocolatey GUI
Chocolatey GUI Licensed Extension

We have no fixed date for release as yet, but it is coming soon.
Apologies for the non-standard issue (I could not find any other way to contact the team). Please let me know if I can help in any way.

The Chocolatey products were released today. Please see the above links for the release notes. Here is some more information that may be helpful:

Blog Post.
Guide to upgrading.
Highlight of changes.

Please let me know if you any more details.

Can confirm, the chocolatey_package resource fails to converge if Chocolatey 2.0.0 is installed due to changes in how choco list functions.

I would hope that the resource uses --limit-output or -r. In that case, choco list hasn't changed at all and should continue to work.
Note that I haven't dug into this at all, so this is an uninformed with no context response 😄

I stand corrected. Looking at my failed run output more closely it seems you can no longer specify a feed URL for the source, it MUST be a named source. In this case we were providing a URL as a source override.

To list remote packages, you need to use the choco search command. So choco search --source="'<URL>'".

chocolatey_package is defintely looking a little busted when using 2.0.
   ================================================================================     Error executing actioninstall` on resource 'chocolatey_package[setdefaultbrowser]'
================================================================================
Chef::Exceptions::Package
-------------------------
No candidate version available for setdefaultbrowser`

/cc @GeorgeWestwater @PrajaktaPurohit @brianLoomis


AttributeError: module 'tensorflow' has no attribute 'placeholder'`

When running the train.py I get the following error:
[2020-05-31 12:31:35,782] [train] [INFO] define model+ Traceback (most recent call last):   File "train.py", line 63, in <module>     input_node = tf.placeholder(tf.float32, shape=(args.batchsize, args.input_height, args.input_width, 3), name='image') AttributeError: module 'tensorflow' has no attribute 'placeholder'
Using Conda and TF 2.0
Please help

Can you tell me how you removed this error?


Rotating markers

Hi
Is it possible in future updates to add rotation to the markers? For my specific app, I need to add road signs to the map, and i store a rotation angle in my database. It would be nice to be able to use that rotation in the Marker object, to rotate the icon images.
Thanks

Seconded.

Would love to see this in next release

Any update here?

the project has moved over to NativeScript community and is being maintained by someone else now as I've had no time to focus on this. See one of the other tickets. I need to update the README.

https://github.com/nativescript-community/ui-mapbox

Thank you!


RPC stop_node doesn't stop rai_node process

Description of bug:

v11.2
RPC call "stop_node" results "success", restarting rai_node 2 processes rai_node can be seen.
Steps to reproduce the issue:

RPC call "stop_node"

ps | grep rai

will show a rai_node process
Describe the results you expected:
stop_node should stop the node.
Additional information you deem important (e.g. issue happens only occasionally):
Environment:
arch linux server 4gb ram dual core

logs

Confirmed.
curl -g -d '{"action": "stop"}' stops the node, i.e. it does no longer check blocks, vote, or respond to RPC, but does not terminate the rai_node process.

Fixed now.


odo installation on windows is broken

/kind bug
There are multiple issues with windows installation.

There are 2 distributions for windows one .exe and .tar.gz unfortunately windows does not come with tools to handle tar.gz by default. We should produce .zip files for windows like we do for crc.

I think there is a mismatch with the instructions and the filenames.  Instructions refer to a odo.exe while linking to odo-windows-amd64.exe. There are no instructions to rename this file.

Step 2 on the installation instructions refers to a GOPATH which is not something most windows users would have configured.

Regarding item 1- ... we should produce .zip files for windows like we do for crc., since we provide an executable file for download, it would be silly to provide a zip file as it adds an extra step for the user to unzip the executable. We will not provide a zip file. Unless anyone disagrees.

We are already providing a tar.gz in addition to the .exe are you suggesting that we do not provide the tar.gz going forward?

To be clear, the request was to produce a .zip instead of .tar.gz (i.e. just change the compression format), not a new/second file.

Required changes:

Update logic https://github.com/openshift/odo/blob/master/scripts/prepare-release.sh#L24-L41 to use gzip for windows and tar.gz otherwise
Update to copy .zip as well files https://github.com/openshift/odo/blob/master/rpms/openshift-odo.spec#L63
Update tar.gz to zip https://github.com/openshift/odo/blob/master/rpms/openshift-odo.spec#L95
Review test script https://github.com/openshift/odo/blob/master/scripts/rpm-x86_64-test.sh for changes


Emergency Alert Push Notification System

This task is to build an emergency alert push notification system by leveraging the CMS/JSON, AWS serverless architecture, and FireBase. More details coming soon.

This is no longer needed as messaging integration as a whole now includes emergency notifications/messaging


ignore/forcefail/forcepass as regexes

Hello,
I was wondering if it could be helpful to provide to the testoverride lists (ignore, forcefail and forcepass) a regex syntax like the -i/-e commands. The use case comes from a willingness to exclude all the tests of some specific rules (or even a specific file?) and, currently, the only way I see is listing individually all the tests in a quite verbose way.

After:
...
testoverride:
  ignore:
  '932140-*': 'Currently excluding rule 932140'

My concern is about the implementation: the check would become not just looking for the a value inside the map (e.g. ignore), but iterating over a list of regex looking for a match. Do you think it's worth the overhead?
Thanks for the feedbacks!

That's a great idea. Concerning implementation, I don't think performance would suffer much since the amount of data to  match is pretty short, as is would the regular expression.

It is a good idea, indeed. Let's add it to our backlog.

Hi, I wrote some (most likely dumb) code: Draft PR #80 .
My concerns are about the change of the basic behaviour of simple rules.
A super trivial ignore of a single rule:
  ignore:
  '932140-1': 'Currently excluding rule 932140'

Now that becomes a regex leads to also remove rules like 932140-1, 932140-10, 932140-11.
The rule should now become at least '932140-1$', asserting the position at the end of the line. I feel it is a bit misleading if you face for the first time this functionality.
Thoughts about it? Could it be better to add other lists (something like ignorePattern or ignoreRegex) for this functionality?
...
testoverride:
  ignore:
    '932140-1': 'Currently excluding a specific test'
  ignorePattern:
    '932150-*': 'Currently excluding all the tests of a rule'

Hi there, I implemented it in a bit better way (at least avoiding regex generation inside loops 😅) and added a bit of documentation about it. I removed the draft status from the PR, open to any advice about better implementing it!
Thanks :)


Collectionname max 15 charaters, why?

See issue #10. Is this not an issue anymore? Or was this an issue on an older operating system?

I need to find time to check it. We have bypass this issue, we had create an own module based on the gallery module.
Mvg Sander Walraven
From: Johan Ljunggren
Sent: Monday, August 19, 2019 3:13 PM
To: PowerShell/xRemoteDesktopSessionHost
Cc: Sawal72; Author
Subject: Re: [PowerShell/xRemoteDesktopSessionHost] Collectionname max 15charaters, why? (#60)
See issue #10. Is this not an issue anymore? Or was this an issue on an older operating system?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Would be great if you could help to see (or know) if there is a limit in any operating system 2012 R2 and newer, if not we could just remove that limit altogether.

See comment in PR #61  https://github.com/PowerShell/xRemoteDesktopSessionHost/pull/61#issuecomment-523625254 which can explain why this parameter has a limit of 15 characters.


about file deletion

PR-Codex overview
This PR adds a warning to the README.md file about the deletion of files upon object destruction. It also includes a new Java code snippet that initializes an FkStorage object.
Detailed summary

Added warning about file deletion upon object destruction to README.md
Added a new Java code snippet that initializes an FkStorage object

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@h1alexbel thank you for your Pull Request. I'll assign someone to review it soon.
If this PR solves a todo from the code, please don't forget to remove it.

@h1alexbel please review this Pull Request. Deadline (when it should be merged or closed) is 2023-06-15T09:59:15.345421.
You should check if the requirements have been implemented (partially or in full), if there are unit tests covering the changes and if the CI build passes. Feel free to reject the PR or ask for changes if it's too big or not clear enough.
Estimation here is 30 minutes, that's how much you will be paid. You will be paid even if this PR gets rejected.

@rultor merge

@rultor merge

@h1alexbel OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@h1alexbel Done! FYI, the full log is here (took me 2min)


Please provide doi to enable citation of MindaGap

Hi,
I would like to cite MindaGap as part of the Resolve segmentation pipeline. If possible, please mint a DOI for the repo (see: https://docs.github.com/en/repositories/archiving-a-github-repository/referencing-and-citing-content) to make this possible.
Thanks!
Petar

Hey Peter,
Made a release, thank you for the suggestion. Here is the DOI:          10.5281/zenodo.8120558
And the suggestion of reference:
Ricardo Guerreiro, Florian Wuennemann, & pvtodorov. (2023). ViriatoII/MindaGap: v0.0.3 (0.0.3). Zenodo. https://doi.org/10.5281/zenodo.8120559
Kind regards,
Ricardo


enable named tunnels

Closes #16
Breaking changes with 3.0.0
This is a breaking change to reflect the new beahviour of named tunnels
The role should take care of cleanup if you used the role before v.3.0.0. However you have to update the configuration (variables) in your ansible project. I renamed the variables - usually prefixed with cf_ to make them unique to the role. If they are not unique it may happen that variables using the same name in different roles can have undesired side-effects.

Mark breaking changes in the commit
(s)


Mono: Make missing default constructor error more foolproof

Honestly I'm not sure if this should be merged. I think this is a good change but perhaps by not using the "correct" terminology the error message is made less correct?

Ah, I thought about this. The change is good, but the wording could be better. I would prefer "parameterless constructor".

Changed

Cherry-picked for 3.1.1.


[PlayWright] Two chromium browser instances getting launched Instead of One

What are you trying to achieve?
Trying to Automate Web using Playwright helper on Chromium, expected to get one browser launched and test executed
What do you get instead?
Two Browser instances are getting launched 1 as Incognito mode and other in Normal Mode

Provide console output if related. Use --verbose mode for more details.
CodeceptJS v2.5.0
Using test root "C:\Automation\Demo_Playwright"
Helpers: Playwright
Plugins: screenshotOnFail, retryFailedStep, allure

Test Google Page --
[1] Starting recording promises
Emitted | suite.before ([object Object])
» [Session] Starting singleton browser session
Search Page @Google
Emitted | test.before ([object Object])
Emitted | test.start ([object Object])
Emitted | step.before (I am on page "https://www.google.com/")
Emitted | step.after (I am on page "https://www.google.com/")
Emitted | step.before (I wait 10)
Emitted | step.after (I wait 10)
# paste output here

Provide test source code if related
Feature('Test Google Page');

Scenario('Search Page @Google', (I)=>{
I.amOnPage('https://www.google.com/')
I.wait (10)
I.fillField('q','Google')
I.click('Google Search')
I.say('Done!')
});
// paste test

Details

CodeceptJS version:2.5.0
NodeJS Version:12.16.0
Operating System: Windows 10
puppeteer || webdriverio || protractor || testcafe version (if related)
Configuration file:

# const { setHeadlessWhen,setWindowSize } = require('@codeceptjs/configure');

// turn on headless mode when running with HEADLESS=true environment variable

// HEADLESS=true npx codecept run

setHeadlessWhen(process.env.HEADLESS);

exports.config = {

  tests: './tests/*_test.js',

  timeout: 10000,

  output: './output',

  helpers: {

    Playwright: {

      url: '',

      show: true,

      browser: 'chromium',

      windowSize: '1900x1200',

      waitForNavigation: [ "domcontentloaded", "networkidle0" ]

    }

  },

  include: {

    I: './steps_file.js'

  },

  bootstrap: null,

  mocha: {},

  name: 'Demo_Playwright',

  plugins: {

    retryFailedStep: {

      enabled: true

    },

    screenshotOnFail: {

      enabled: true

    },

    allure: {

      enabled: true

    }

  }

}

I faced similar issue duting development.
For me it was the problem with some Playwright versions. I hope this will be fixed on their end.

Thanks for confirming the issue, will look forward for upcoming releases to get this resolved either by Playwright or by our community.

@MaxTester1 just wait for update
https://github.com/microsoft/playwright/issues/981

so seemed like it's playwright's part
.

@MaxTester1 just wait for update
microsoft/playwright#981

Thanks @Elverslane for the followup and update


Fixed a NullException Bug

A null exception bug may occur if the list is null.
To fix this, return from function if list is null.
Please add this. Thanks

In what case is the instruction list null?

I have tried to deobfuscate a jar file like this, with:
java -jar jmd-cli/build/libs/jmd-cli-1.6.jar ../classes.jar smokescreen true
and here is the log output:
Java Multi-Purpose Deobfuscator
Version UNKNOWN
Created by Contra. Please read LICENSE.txt
Tons of code from skoalman, super_, ollie, popcorn89, the prophecy, and saevion
[SmokeScreenTransformer][DEBUG]Classes loaded from JAR
[SmokeScreenTransformer]SmokeScreen Deobfuscator
[SmokeScreenTransformer]Decrypting Strings...
[SmokeScreenTransformer][DEBUG]Found key for com.google.android.exoplayer2.metadata.id3.a: 3
[SmokeScreenTransformer][DEBUG]Strings for class: &Kkk
[SmokeScreenTransformer][DEBUG]Found key for com.google.android.exoplayer2.metadata.id3.a: 4
[SmokeScreenTransformer][DEBUG]Strings for class: !G[7kk
[SmokeScreenTransformer][DEBUG]Found key for com.google.android.exoplayer2.metadata.id3.a: 3
[SmokeScreenTransformer][DEBUG]Strings for class: &Kkk
[SmokeScreenTransformer][DEBUG]Found key for com.google.android.exoplayer2.metadata.id3.a: 4
[SmokeScreenTransformer][DEBUG]Strings for class: !G[7kk
[SmokeScreenTransformer][DEBUG]Found key for com.google.android.exoplayer2.metadata.id3.a: 3
[SmokeScreenTransformer][DEBUG]Strings for class: &Kkk
[SmokeScreenTransformer][DEBUG]Found key for com.google.android.exoplayer2.metadata.id3.a: 4
[SmokeScreenTransformer][DEBUG]Strings for class: !G[7kk
Then, an exception was caught, which was fixed by this fix.
Exception in thread "main" java.lang.NullPointerException 	at net.contra.jmd.transformers.smokescreen.SmokeScreenTransformer.grabStrings(SmokeScreenTransformer.java:77) 	at net.contra.jmd.transformers.smokescreen.SmokeScreenTransformer.transform(SmokeScreenTransformer.java:137) 	at net.contra.jmd.Deobfuscator.main(Deobfuscator.java:56)


Move apt from hieradata to base

When trying to deploy #432 the apt package was not found.
cc @deanwilson

Merge when green.


Date.parse unit test fails

expect(Date.parse('-000001-01-01T00:00:00Z')).toBe(-62198755200000);
The following line fails.

Windows 7. Tested in all browsers. Of course the native Date.parse works but the shim doesn't

What's the result that the shim produces? It works in IE 6, IE 7, and Safari 3 for me.

I fail >_<.
It's this expect(Date.parse('0001-01-01T00:00:00Z')).toBe(62135596800000); test that is failing.
And the native implementations agree that it should be negative instead of positive. Sorry!

No worries. Glad that you were able to sort it out.