chore: bump discord-api-types

Please describe the changes this PR makes and why it should be merged:
Status and versioning classification:

Code changes have been tested against the Discord API, or there are no code changes

This needs a rebase.


Twitter/Opengraph metadata falls back to excerpt before metaDescription

Issue Summary
At the moment how structured data is generated metaDescription is used as the fall back for excerpt which always exists. This means that if you set a custom Meta Description via the Meta tab on a post, Twitter and Opengraph data don't fall back and use this data, instead they use the excerpt.
https://github.com/TryGhost/Ghost/blob/fb7afd1672e8237c86dd7cc12ba37984a6c2f0bc/core/frontend/meta/structured_data.js#L28
Ghost Admin also shows the custom excerpt, its just the front end that doesn't.
To Reproduce

Create a random post and set alternative data in the 'Meta Description' field via the Meta tab
Go to the Twitter or Facebook cards and see the preview in Ghost Admin shows your custom excerpt
View post and see that og:description and twitter:description use the default value of metaData.excerpt

Technical details:
3.0.3

This should be resolved by https://github.com/TryGhost/Ghost/pull/11068 that is due to be updated and merged shortly - you can also see the table of intended fallbacks for each meta/og/twitter property there.

I just noticed the CASE statement above this code, but I'm not sure this holds true still?
https://github.com/TryGhost/Ghost/blob/fb7afd1672e8237c86dd7cc12ba37984a6c2f0bc/core/frontend/meta/structured_data.js#L15-L18

Thanks Kevin! ❤


[Ubuntu 16.04 LTS]: draft connect hangs

Might be related to the sudo issue #611.

Do you have the latest version of the packs?
The error there happens when the client doesn't find a pod with that annotation - and this happens if the template doesn't contain the annotation.

Dunno. to use it, I rm -rf ~/.draft, which I assume torched the older packs. if not, I need to know how to do that. :-)

That should have done the trick.
Could you cat charts/templates/deployment.yaml?

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: {{ template "fullname" . }}
  labels:
    draft: {{ default "draft-app" .Values.draft }}
    chart: "{{ .Chart.Name }}-{{ .Chart.Version | replace "+" "_" }}"
spec:
  replicas: {{ .Values.replicaCount }}
  template:
    metadata:
      labels:
        draft: {{ default "draft-app" .Values.draft }}
        app: {{ template "fullname" . }}
    spec:
      containers:
      - name: {{ .Chart.Name }}
        image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
        imagePullPolicy: {{ .Values.image.pullPolicy }}
        ports:
        - containerPort: {{ .Values.service.internalPort }}
        resources:
{{ toYaml .Values.resources | indent 12 }}

Yup, you don't have the latest version of the pack - either recreate the app (delete stuff and draft create again) or update your deployment.yaml to be:
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: {{ template "fullname" . }}
  labels:
    draft: {{ default "draft-app" .Values.draft }}
    chart: "{{ .Chart.Name }}-{{ .Chart.Version | replace "+" "_" }}"
spec:
  replicas: {{ .Values.replicaCount }}
  template:
    metadata:
      annotations:
        buildID: {{ .Values.buildID }}
      labels:
        draft: {{ default "draft-app" .Values.draft }}
        app: {{ template "fullname" . }}
    spec:
      containers:
      - name: {{ .Chart.Name }}
        image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
        imagePullPolicy: {{ .Values.image.pullPolicy }}
        ports:
        - containerPort: {{ .Values.service.internalPort }}
        resources:
{{ toYaml .Values.resources | indent 12 }}

This most likely happened because you had an existing application created before upgrading - and we must document this somewhere.

resolved


Set value type error!

sjson.Set(b.content, path, []uint8{1, 2, 3, 4})
value type "[]uint8" will change to "string"

Go treats []byte and []uint8 as the same thing, and sjson treats []byte as a string.
https://github.com/tidwall/sjson/blob/master/sjson.go#L674-L676
There's no way, that I know of, to make a distinction between []byte and []uint8.


How to add button on toolbar with action :(save photo in Album)??

Check this issue. Here i have added a delete (custom button) on toolbar.
https://github.com/mwaterfall/MWPhotoBrowser/issues/466


[helm create] Add autoscaling(hpa) boilerplate

Elasticity is an important feature for cloud native stateless apps such as the one deployed out of the box with helm create.  Allowing users to easily autoscale newly created apps would be beneficial.
I propose we add a disabled by default hpa, with default values of 1 to 100 replicas and 80% cpu utilization threshold.
cc @helm/chart-maintainers

@naseemkullah I'm sure this is on your radar already, but just want to note here for others that any PR to address this issue should be sure to add a Helm 3 "Horizontal Pod Autoscaler requires condition" (the third use case described here: https://github.com/helm/charts/issues/19008).

Yep, I plan to implement it as such upon hereby agreement from chart maintainers.

Not sure why that CC link didn't work - maybe you need specific repo perms to do it.
☝ CC @helm/charts-maintainers

Thanks @scottrigby

https://github.com/helm/helm/pull/7381 created. Please take a look 🙏

PR #7381  merged.


Export the needed parts of Winit or add better utilities for centering a window.

What problem does this solve or what need does it fill?
The problem this proposition intents to solve is making the task of centering a window easier.
It intents to remove the need to have dependencies for both bevy and winit.
What solution would you like?
There's multiple ways to o about this.
First, the way I would not like to see, by re-exporting the required parts of winit to center a window: winit::dpi::(::PhysicalPosition) and winit::event_loop(::EventLoop).
Second, the solution I'd like to see implemented, WindowDescriptor.position when set to None should say that the window should be centered, then Bevy can take care of everything behind the scenes.
This also allows all windows to be centered by default.
What alternative(s) have you considered?
The alternative I'm using is to have dependencies for both winit and bevy in my Cargo.toml file:
[[bin]]
name = "bevytest"
path = "./src/main.rs"

[package]
edition = "2021"
version = "0.1.0"
name = "bevy_test"

[profile.dev]
opt-level = 1

[profile.dev.package."*"]
opt-level = 3

[dependencies]
winit = { version = "0.26.0", default-features = false }
bevy = { version="0.7" }

However, this seems inconvenient.
Additional Context
I believe centering the window could be delegated to WindowDescriptor.position = None or a center() method on a Window.
Check out the current solution for centering a window in a Discord-thread on the Bevy Discord guild.

This is an excellent write-up, thanks! I agree with your analysis, and would like this to be simple. We get this question pretty regularly!

@alice-i-cecile Thank you for the compliment. I feel honored to have gotten the "Good-First-Issue" tag, even for as little as its worth.

I just had an afterthought, and this may or may not be a good idea, but it would be cool to control the window's visibility in a WindowDescriptor as a visibility property, this would theoretically allow you to center the window perfectly accounting for the border without anyone seeing, then you can unhide the window once it's in place.

Ideally we reuse our standard visibility component for that, by making windows entities in #4530 :)

Second, the solution I'd like to see implemented, WindowDescriptor.position when set to None should say that the window should be centered

I think that should use the default position assigned by the window manager, not use a centered position.

@bjorn3 Then how would one make the window centered using a WindowDescriptor? Would you suggest a centered:bool property?

Maybe make position an enum between fixed absolute position, centered and default position.

That's exactly what mockersf suggested in #4999 (and I now implemented)

I didn't see PR until after I commented.


Refine joint decision sequential action mode

Description
Changes:

add a new mode: DecisionModel.JointWithSequentialAction
assign action to pending decision events from beginning to end, ignore events that have no action assigned under joint mode.

Linked issue(s)/Pull request(s)

issue_number

Type of Change

[ ] Non-breaking bug fix
[ ] Breaking bug fix
[ ] New feature
[ ] Test
[ ] Doc update
[ ] Docker update

Related Component

[ ] Simulation toolkit
[ ] RL toolkit
[ ] Distributed toolkit

Has Been Tested

OS:

[ ] Windows
[ ] Mac OS
[ ] Linux

Python version:

[ ] 3.6
[ ] 3.7

Key information snapshot(s):

Needs Follow Up Actions

[ ] New release package
[ ] New docker image

Checklist

[ ] Add/update the related comments
[ ] Add/update the related tests
[ ] Add/update the related documentations
[ ] Update the dependent downstream modules usage

Codecov Report

Merging #219 (0e556ed) into v0.2 (6854e80) will decrease coverage by 2.08%.
The diff coverage is 92.85%.

@@            Coverage Diff             @@
##             v0.2     #219      +/-   ##
==========================================
- Coverage   70.29%   68.20%   -2.09%
==========================================
  Files         101      103       +2
  Lines        4571     4800     +229
==========================================
+ Hits         3213     3274      +61
- Misses       1358     1526     +168

Flag
Coverage Δ

unittests
68.20% <92.85%> (-2.09%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

maro/simulator/core.py
79.38% <92.30%> (-4.91%)
:arrow_down:

maro/simulator/abs_core.py
78.78% <100.00%> (+0.32%)
:arrow_up:

...o/simulator/scenarios/citi_bike/business_engine.py
73.04% <0.00%> (-2.16%)
:arrow_down:

maro/simulator/scenarios/abs_business_engine.py
87.71% <0.00%> (-1.38%)
:arrow_down:

maro/simulator/scenarios/cim/business_engine.py
85.60% <0.00%> (-0.33%)
:arrow_down:

maro/data_lib/dump_csv_converter.py
15.82% <0.00%> (ø)

maro/simulator/scenarios/cim/ports_order_export.py
50.00% <0.00%> (ø)

maro/utils/exception/cli_exception.py
65.21% <0.00%> (+4.10%)
:arrow_up:

Continue to review full report at Codecov.

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


How can I get the index of counterfactuals?

Hi. Thank you for great package for Interpret.
Here's my question.
How can I get the index of counterfactuals?

ebm = ExplainableBoostingClassifier(interactions=0)
ebm.fit(X_train[:10000], y_train[:10000])
d = dice_ml.Data(dataframe=df_train.iloc[:10000,1:],continuous_features=X_train.columns.tolist(), outcome_name='target')
m = dice_ml.Model(model=ebm, backend='sklearn')
exp = dice_ml.Dice(d,m)
e1 = exp.generate_counterfactuals(X_train[0:1], total_CFs=10, desired_class="opposite")
e1.visualize_as_dataframe(show_only_changes=True)
After "visualize_as_dataframe", It returns dataframe for instance and counterfactuals.
But I have no idea what instance is counterfactuals.
Thank you for you help in advanced.

@Jihyun-Yun-0110 If I understand your question correctly, you are asking for the index of the generated counterfactuals in the dataset.
The default method for generate_counterfactuals looks for the closest point that yields a different predicted class. This point need not be in the dataset. It is a simulated point that helps to understand the model's decision boundary, and therefore there is no corresponding index in the dataset.
That said, there is a method kd-tree that does output the closest point in the dataset. @soundarya98 is there a way to retrieve the index of those points in the original dataset?

@amit-sharma Thank you for your kind reply.
I tried a method kd-tree, but I still want to get dataframe or array or index for the counterfactuals found.

Dear @jh-0110, Thanks for raising the issue.
We will address your issue in a new pull request coming shortly which will give the original indices of the counterfactuals found using `kd-tree'.

Thank you very much @amit-sharma , @soundarya98 :)


Not possible to install on windows via proxy

When trying to install calico on a windows node with restricted internet access (internet may only be accessed via http_proxy) the installation fails.
Expected Behavior
The installer should honor any set HTTP_PROXY / HTTPS_PROXY environment variables.
Current Behavior
Uninstalling any existing Calico install before proceeding with installation...
No Calico services found.
Invoke-WebRequest : Unable to connect to the remote server
At C:\C\0b06ba5db7294ba7c76b1567ec8f316b6c1e175ff9c9ae433e83d8f184392880\install-calico-windows.ps1:424 char:5
+     Invoke-WebRequest https://raw.githubusercontent.com/Microsoft/SDN ...
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc                                                                              eption                                                                                + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Possible Solution
Maybe using powershell >=7 (see https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/invoke-webrequest?view=powershell-7.3)
Steps to Reproduce (for bugs)

Restrict internet access to only be accessible via http proxy
Run calico/windows:v3.26.1 host-process-install.ps1

Context
In a corporate environment direct internet access is often restricted. This issue is blocking our windows rollout.
Your Environment

Calico version 3.26.1
Orchestrator version (e.g. kubernetes, mesos, rkt): k8s on aws eks
Operating System and version: Windows Server 2022 Core

As a workaround one could install powershell 7 on the host and use it to run the calico ps1 scripts:
mkdir C:\powershell
curl.exe --connect-timeout 10 --ssl-no-revoke --retry 10 --retry-all-errors -L https://github.com/PowerShell/PowerShell/releases/download/v7.3.6/PowerShell-7.3.6-win-x64.zip -o C:\powershell\powershell.zip
Expand-Archive C:/powershell/powershell.zip C:/powershell | Out-Null;
Remove-Item C:/powershell/powershell.zip | Out-Null;

      initContainers:
        - name: install
          image: cr.siemens.com/cloud-platform-services/calico/calico/windows:v3.26.1
          args:
            - "C:\\powershell\\pwsh.exe .\\host-process-install.ps1"

@davidgiga1993 I'm happy to announce that Calico v3.27.0 has been released with operator support for Windows!

https://github.com/projectcalico/calico/releases/tag/v3.27.0
https://docs.tigera.io/calico/latest/getting-started/kubernetes/windows-calico/operator

This leverages Windows host process containers (HPC) so Calico for Windows runs in actual Kubernetes pods (that means install-calico-windows.ps1 is no longer needed and thus no need to download anything with Invoke-WebRequest, so a proxy should not be a problem anymore). Please try it out and let us know!

Sorry for the (very late) reply, but I'm happy to report that it's all working now 👍 Still got some issues with pulling images through a http proxy, but that's outside of calico


ResizeRenderer not constraining aspect ratio in all cases

Looks like ResizeRenderer doesn't constrain the aspect ration in all cases when constrain=True.

Fixed in edb0965022a7c42676afebd66c4b1cf2f70b553d


Pydoc fixes for StructuredTensor

Minor fixes for StructuredTensor pydocs that had incorrect example code and Python 2 style print statements.

@rthadur is this something you can review?

@BryanCutler Can you please resolve conflicts? Thanks!

@gbaned I resolved conflicts and updated to reflect some recent changes. Tests look like they failed due to time out. Thanks for taking a look!

Thank you for reviewing @edloper , and congrats on the baby!

@BryanCutler Can you please fix build failures ? Thanks!

@gbaned and @edloper the tests have now passed, is this ok to merge?


onMessage.Listen is not always triggered

Is there an existing issue for this?

[X] I have searched the existing issues.

Which plugins are affected?
No response
Which platforms are affected?
Android
Description
I am making a chat application which heavily relies on fcm messaging . I have recently noticed that all background messages are being stored ie all messages received in background are being stored successfully , but foreground messages sometimes work and sometimes dont work .  onMessage.listen is not always triggered due to which there is a huge skip in my messages .
I cannot really showcase the issue since issue is realtime and also there are no bugs/errors associated to my code . I tried manipulating FirebaseMessagingReciever code but I cannot find any way to manipulate it . I am trying to remove return; statment from if-else block which controls foreground and background messages since backgroundMessages are always triggered . If there's a fix to this please suggest a fix or please guide me on how can I make proposed changes to my code .
Reproducing the issue
1 make a flutter app with 2-3 nested screens
2 add foreground and background listener on main method
3 try multiple fcm messages (mine are all data messages)
4 use recent flutter version as of now
Firebase Core version
3.3.0
Flutter Version
3.24.0
Relevant Log Output
No response
Flutter dependencies

Expand Flutter dependencies snippet

Replace this line with the contents of your `flutter pub deps -- --style=compact`.

Additional context and comments
No response

I noticed in version 15.1.0 that
FirebaseMessaging.onMessage.listen((remoteMessage) async {
is not triggered at all anymore. I had to bump down to my previous version 15.0.4

I noticed on iOS in version 15.1.0 that
FirebaseMessaging.onMessage.listen((remoteMessage) async {
is not triggered at all anymore. I had to bump down to my previous version 15.0.4

Yeah , I was using the same version , but still the problem persisted . Finally modified the source code under FirebaseMessagingReciever.java . Modified this line in perticular if (FlutterFirebaseMessagingUtils.isApplicationForeground(context)) {       FlutterFirebaseRemoteMessageLiveData.getInstance().postRemoteMessage(remoteMessage);     }     Log.d(TAG,"HEY , I MODIFIED THE CODES SUCCESSFULLY !!!!!!!!!!!!!!");  The line basically helps executing both foreground and backgroud triggers simultaneously . Its surely a workaround since I am using inter process communication using sockets to trigger stuff in other files from background reciever

Same here, but not sure if it's a collision with some other plugin I use in the app.
My onMessage is not firing for foreground data notifications in iOS. I can see the notification in Console.app logs and also new log output from FirebaseMessaging but it looks like the data notifications is not passed to didReceiveRemoteNotification in iOS from what I could debug. I had to disable swizzle and then it started working but I know that is frowned upon :)

Hi @USER4247 , thanks for the report. I'm unable to reproduce this issue. I fired a couple of test messages while the app was in foreground and they were all received. A little more context on the conditions required for reproducing this issue will be of help.

Hi @USER4247 , thanks for the report. I'm unable to reproduce this issue. I fired a couple of test messages while the app was in foreground and they were all received. A little more context on the conditions required for reproducing this issue will be of help.

For testing purpose , I am echoing messages back to my device . On cloud console , all fcm messages were recieved and sent back successfully . I have 2 nested screens within my app . I have defined all firebase configs in main method of my app .
The error is very unpredictable since it sometimes trigger foreground and sometimes does not . I am trying a bunch of things , downgrade flutter . I will try to create a new project and test if the problem persists

Kindly share a full sample code reproducing the issue.

Kindly share a full sample code reproducing the issue.

Hi , I have added example code above . Please note that I am using purely data/silent notification messages . All modules used are set to recent versions .

Edit ... I found the issue . I have been using firebase functions for all my messaging . It turns out there is some issue with sendMulticast . Its deprecated and will sometimes work and sometimes will not prompting "UNIMPLEMENTED" error message .  I had to change sendMulticast to sendEachForMulticast in my index.js firebase functions . Thank you

Edit ... I found the issue . I have been using firebase functions for all my messaging . It turns out there is some issue with sendMulticast . Its deprecated and will sometimes work and sometimes will not prompting "UNIMPLEMENTED" error message .  I had to change sendMulticast to sendEachForMulticast in my index.js firebase functions . Thank you


Any question

Hello, dear! I have any question about this project. Can you sand me message?

Hi, what questions do you have?

Please tell me how G2GSESID_V4 is generated?


can i copy part from the documenation  of chartjs  in my site or its not legal ?

i am working in   chart generator for chartjs .  i want to know its legal to use the documentation of chartjs  in my site. to explain to people how to use the chart generator

Yes. Please see here for full details: https://github.com/chartjs/Chart.js/blob/master/LICENSE.md
There is some risk that anything you copy may become outdated, however, so you may want to link to the site for that reason.


Test the model on randomly selected engine from the test dataset

Hello！
eng_df = pd.read_csv(
"/content/sample_data/Eng_plot_" + str(numb) + "" + filename + ".csv"
)
There is no "/content/sample_data/Eng_plot" + str(numb) + "_" + filename + ".csv" files.
Could you help me?

Hi. You should replace the path with your own path (i.e. where you downloaded the data). I hope this helps.

Quote reply


How to use test.xml algo.?

Hi, I have successfully setup the msccl-tools and I can generate the .xml algo files from the examples as described here. Another question is how to use the synthesized .json files here
python msccl-tools/examples/mscclang/allreduce_a100_allpairs.py --protocol=LL 8 2 > test.xml. My quick question is
how to enforce the usage of text.xml in the
or python msccl-tools/examples/mscclang/allreduce_a100_ring.py --protocol=Simple 8 1 1 > test.xml
and copying the text.xml to /msccl/executor/msccl-executor-nccl/build/lib/msccl-algorithms
mpirun -np 1 -x LD_LIBRARY_PATH=msccl/exector/msccl-executor-nccl/build/lib/:$LD_LIBRARY_PATH -x NCCL_DEBUG=INFO -x NCCL_ALGO=TREE -x NCCL_DEBUG_SUBSYS=INIT,ENV msccl/tests/msccl-tests-nccl/build/all_reduce_perf -b 128 -e 32MB -f 2 -g 8 -c 1 -n 100 -w 100 -G 100 -z 0

Because it seems to ignore it and falling back to nccl. Thanks in advance for your help. Following is the topology I used with 8xA100 GPUs and 1 node
       GPU0    GPU1    GPU2    GPU3    GPU4    GPU5    GPU6    GPU7CPU Affinity    NUMA Affinity
GPU0     X      NV12    NV12    NV12    NV12    NV12    NV12    NV120-31    0
GPU1    NV12     X      NV12    NV12    NV12    NV12    NV12    NV120-31    0
GPU2    NV12    NV12     X      NV12    NV12    NV12    NV12    NV120-31    0
GPU3    NV12    NV12    NV12     X      NV12    NV12    NV12    NV120-31    0
GPU4    NV12    NV12    NV12    NV12     X      NV12    NV12    NV1232-63   1
GPU5    NV12    NV12    NV12    NV12    NV12     X      NV12    NV1232-63   1
GPU6    NV12    NV12    NV12    NV12    NV12    NV12     X      NV1232-63   1
GPU7    NV12    NV12    NV12    NV12    NV12    NV12    NV12     X 32-63    1

Legend:

 X    = Self
 SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
 NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
 PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
 PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
 PIX  = Connection traversing at most a single PCIe bridge
 NV#  = Connection traversing a bonded set of # NVLinks

The issue is no matter what test.xml I used I get the same in-place and out-of-place results:
#
#                                                              out-of-place                       in-place
#       size         count      type   redop    root     time   algbw   busbw #wrong     time   algbw   busbw #wrong
#        (B)    (elements)                               (us)  (GB/s)  (GB/s)            (us)  (GB/s)  (GB/s)
         128            32     float     sum      -1    19.96    0.01    0.01      0    17.59    0.01    0.01      0
         256            64     float     sum      -1    17.75    0.01    0.03      0    17.78    0.01    0.03      0
         512           128     float     sum      -1    18.58    0.03    0.05      0    18.61    0.03    0.05      0
        1024           256     float     sum      -1    18.88    0.05    0.09      0    18.86    0.05    0.10      0
        2048           512     float     sum      -1    19.63    0.10    0.18      0    19.57    0.10    0.18      0
        4096          1024     float     sum      -1    21.03    0.19    0.34      0    21.01    0.19    0.34      0
        8192          2048     float     sum      -1    21.98    0.37    0.65      0    22.02    0.37    0.65      0
       16384          4096     float     sum      -1    22.44    0.73    1.28      0    22.48    0.73    1.28      0
       32768          8192     float     sum      -1    23.17    1.41    2.47      0    23.13    1.42    2.48      0
       65536         16384     float     sum      -1    24.22    2.71    4.74      0    24.14    2.72    4.75      0
      131072         32768     float     sum      -1    28.36    4.62    8.09      0    27.79    4.72    8.25      0
      262144         65536     float     sum      -1    44.06    5.95   10.41      0    43.96    5.96   10.44      0
      524288        131072     float     sum      -1    51.40   10.20   17.85      0    51.30   10.22   17.88      0
     1048576        262144     float     sum      -1    60.20   17.42   30.48      0    60.16   17.43   30.50      0
     2097152        524288     float     sum      -1    73.98   28.35   49.61      0    73.65   28.48   49.83      0
     4194304       1048576     float     sum      -1    100.2   41.86   73.25      0    99.04   42.35   74.11      0
     8388608       2097152     float     sum      -1    151.0   55.56   97.23      0    148.8   56.38   98.66      0
    16777216       4194304     float     sum      -1    254.9   65.81  115.16      0    254.6   65.89  115.31      0
    33554432       8388608     float     sum      -1    464.5   72.24  126.43      0    464.7   72.20  126.36      0

# Out of bounds values : 0 OK
# Avg bus bandwidth    : 28.4095

I have doubled checked even if we remove the text.xml, the INFO log still prints CCL INFO NCCL_ALGO set by environment to msccl/executor/msccl-executor-nccl/build/lib/msccl-algorithms/test.xml.
I have logged two cases with and without text.xml . Please find the attached log files
out_without_xml.log
out_with_allreduce_a100_allpairs.py_protocol=Simple_8_1_xml 1.log

The out_without_xml.log is when no .xml file was there in msccl/executor/msccl-executor-nccl/build/lib/msccl-algorithms

The out_with_allreduce_a100_allpairs.py_protocol.Simple_8_1_xml.1.log is when text.xml is generated and put in this path msccl/executor/msccl-executor-nccl/build/lib/msccl-algorithms

The command to generate the text.xml is below
python msccl-tools/examples/mscclang/allreduce_a100_allpairs.py --protocol=Simple 8 1  > test.xml

azharlightelligence:
it seems the algo file already been picked up by msccl executor, however, there exist one bug in msccl tool, which missed generate some key attribute, like outofplace="0" minBytes="0" maxBytes="65565", please add it manually in the generated test.xml file. we will fix it later for the msccl tool. below is the part indicated from your log for these clues.

my-system:52727:52807 [7] NCCL INFO Using MSCCL Algo files from /u/ahussain/workspace/msccl-ah/azure/msccl/executor/msccl-executor-nccl/build/lib/msccl-algorithms
my-system:52712:52782 [0] NCCL INFO Using MSCCL Algo files from /u/ahussain/workspace/msccl-ah/azure/msccl/executor/msccl-executor-nccl/build/lib/msccl-algorithms
my-system:52727:52807 [7] include/msccl/msccl_parser.h:70 NCCL WARN Attribute minBytes of node algo not found
my-system:52727:52807 [7] NCCL INFO include/msccl/msccl_parser.h:84 -> 3
my-system:52727:52807 [7] NCCL INFO misc/msccl/msccl_parser.cc:769 -> 3
my-system:52727:52807 [7] NCCL INFO misc/msccl/msccl_lifecycle.cc:147 -> 3
my-system:52727:52807 [7] NCCL INFO misc/msccl/msccl_lifecycle.cc:178 -> 3
my-system:52727:52807 [7] NCCL INFO misc/msccl/msccl_lifecycle.cc:220 -> 3
my-system:52727:52807 [7] NCCL INFO init.cc:1246 -> 3
my-system:52727:52807 [7] NCCL INFO init.cc:1391 -> 3
my-system:52727:52807 [7] NCCL INFO group.cc:68 -> 3 [Async thread]
my-system:52727:52727 [7] NCCL INFO group.cc:429 -> 3
my-system:52727:52727 [7] NCCL INFO group.cc:115 -> 3
my-system: Test NCCL failure common.cu:973 'internal error - please report this issue to the NCCL developers / '
.. my-system pid 52727: Test failure common.cu:857

v

azharlightelligence: it seems the algo file already been picked up by msccl executor, however, there exist one bug in msccl tool, which missed generate some key attribute, like outofplace="0" minBytes="0" maxBytes="65565", please add it manually in the generated test.xml file. we will fix it later for the msccl tool. below is the part indicated from your log for these clues.
my-system:52727:52807 [7] NCCL INFO Using MSCCL Algo files from /u/ahussain/workspace/msccl-ah/azure/msccl/executor/msccl-executor-nccl/build/lib/msccl-algorithms my-system:52712:52782 [0] NCCL INFO Using MSCCL Algo files from /u/ahussain/workspace/msccl-ah/azure/msccl/executor/msccl-executor-nccl/build/lib/msccl-algorithms
my-system:52727:52807 [7] include/msccl/msccl_parser.h:70 NCCL WARN Attribute minBytes of node algo not found my-system:52727:52807 [7] NCCL INFO include/msccl/msccl_parser.h:84 -> 3 my-system:52727:52807 [7] NCCL INFO misc/msccl/msccl_parser.cc:769 -> 3 my-system:52727:52807 [7] NCCL INFO misc/msccl/msccl_lifecycle.cc:147 -> 3 my-system:52727:52807 [7] NCCL INFO misc/msccl/msccl_lifecycle.cc:178 -> 3 my-system:52727:52807 [7] NCCL INFO misc/msccl/msccl_lifecycle.cc:220 -> 3 my-system:52727:52807 [7] NCCL INFO init.cc:1246 -> 3 my-system:52727:52807 [7] NCCL INFO init.cc:1391 -> 3 my-system:52727:52807 [7] NCCL INFO group.cc:68 -> 3 [Async thread] my-system:52727:52727 [7] NCCL INFO group.cc:429 -> 3 my-system:52727:52727 [7] NCCL INFO group.cc:115 -> 3 my-system: Test NCCL failure common.cu:973 'internal error - please report this issue to the NCCL developers / ' .. my-system pid 52727: Test failure common.cu:857

Thanks for the feedback. The issue is resolved after updating the .xml

Hi @Andyli1007, first of all thanks for quick response and I found that the examples and their .xml generated algos do have significant impact on the system performance. I moved one step further to test custom auto generated algos. Follwowing example script works well for the allgather :
from msccl.topologies import dgx_a100
from msccl.collectives import allgather, alltoall, reduce_scatter, allreduce
from msccl.collectives import reduce,scatter,gather,broadcast
from pprint import pprint
from msccl.strategies import solve_instance
from msccl.instance import Instance
from msccl.language import *
from msccl.topologies import *
from msccl.serialization import MSCCLEncoder
import os

topology = dgx_a100()
pprint(topology.links)
collective = allgather(topology.num_nodes())
algo = solve_instance(topology, collective, Instance(steps=4), logging=True)
jsonfile = MSCCLEncoder().encode(algo)
with open("data.json", "w") as text_file:
    text_file.write(jsonfile)
os.system("msccl ncclize -f data.json -o test.xml")

Output
[[0, 12, 12, 12, 12, 12, 12, 12],
 [12, 0, 12, 12, 12, 12, 12, 12],
 [12, 12, 0, 12, 12, 12, 12, 12],
 [12, 12, 12, 0, 12, 12, 12, 12],
 [12, 12, 12, 12, 0, 12, 12, 12],
 [12, 12, 12, 12, 12, 0, 12, 12],
 [12, 12, 12, 12, 12, 12, 0, 12],
 [12, 12, 12, 12, 12, 12, 12, 0]]
Solving instance steps=4... synthesized! (0.4s)
Wrote to test.xml

But the problem comes if I change allgather to allreduce as below:
from msccl.topologies import dgx_a100
from msccl.collectives import allgather, alltoall, reduce_scatter, allreduce
from msccl.collectives import reduce,scatter,gather,broadcast
from pprint import pprint
from msccl.strategies import solve_instance
from msccl.instance import Instance
from msccl.language import *
from msccl.topologies import *
from msccl.serialization import MSCCLEncoder
import os

topology = dgx_a100()
pprint(topology.links)
collective = allreduce(topology.num_nodes())
algo = solve_instance(topology, collective, Instance(steps=4), logging=True)
jsonfile = MSCCLEncoder().encode(algo)
with open("data.json", "w") as text_file:
    text_file.write(jsonfile)
os.system("msccl ncclize -f data.json -o test.xml")

Output
[[0, 12, 12, 12, 12, 12, 12, 12],
 [12, 0, 12, 12, 12, 12, 12, 12],
 [12, 12, 0, 12, 12, 12, 12, 12],
 [12, 12, 12, 0, 12, 12, 12, 12],
 [12, 12, 12, 12, 0, 12, 12, 12],
 [12, 12, 12, 12, 12, 0, 12, 12],
 [12, 12, 12, 12, 12, 12, 0, 12],
 [12, 12, 12, 12, 12, 12, 12, 0]]
Solving instance steps=4... synthesized! (1.4s)
Traceback (most recent call last):
  File "/miniconda3/envs/py38/bin/msccl", line 33, in <module>
    sys.exit(load_entry_point('msccl==2.3.0', 'console_scripts', 'msccl')())
  File "/miniconda3/envs/py38/lib/python3.8/site-packages/msccl-2.3.0-py3.8.egg/msccl/__main__.py", line 34, in main
  File "/miniconda3/envs/py38/lib/python3.8/site-packages/msccl-2.3.0-py3.8.egg/msccl/cli/ncclize.py", line 29, in handle
  File "/miniconda3/envs/py38/lib/python3.8/site-packages/msccl-2.3.0-py3.8.egg/msccl/ncclize.py", line 548, in ncclize
RuntimeError: Encountered receive and send on the same buffer index on step 1 (gpu=5, buf=i, off=0)

Can you please help check and resolve this issue so that I can use the generated .xml. Thanks in advance

Hi, I have successfully setup the msccl-tools and I can generate the .xml algo files from the examples as described here. Another question is how to use the synthesized .json files here
python msccl-tools/examples/mscclang/allreduce_a100_allpairs.py --protocol=LL 8 2 > test.xml. My quick question is how to enforce the usage of text.xml in the
or python msccl-tools/examples/mscclang/allreduce_a100_ring.py --protocol=Simple 8 1 1 > test.xml and copying the text.xml to /msccl/executor/msccl-executor-nccl/build/lib/msccl-algorithms
mpirun -np 1 -x LD_LIBRARY_PATH=msccl/exector/msccl-executor-nccl/build/lib/:$LD_LIBRARY_PATH -x NCCL_DEBUG=INFO -x NCCL_ALGO=TREE -x NCCL_DEBUG_SUBSYS=INIT,ENV msccl/tests/msccl-tests-nccl/build/all_reduce_perf -b 128 -e 32MB -f 2 -g 8 -c 1 -n 100 -w 100 -G 100 -z 0

Because it seems to ignore it and falling back to nccl. Thanks in advance for your help. Following is the topology I used with 8xA100 GPUs and 1 node
       GPU0    GPU1    GPU2    GPU3    GPU4    GPU5    GPU6    GPU7CPU Affinity    NUMA Affinity
GPU0     X      NV12    NV12    NV12    NV12    NV12    NV12    NV120-31    0
GPU1    NV12     X      NV12    NV12    NV12    NV12    NV12    NV120-31    0
GPU2    NV12    NV12     X      NV12    NV12    NV12    NV12    NV120-31    0
GPU3    NV12    NV12    NV12     X      NV12    NV12    NV12    NV120-31    0
GPU4    NV12    NV12    NV12    NV12     X      NV12    NV12    NV1232-63   1
GPU5    NV12    NV12    NV12    NV12    NV12     X      NV12    NV1232-63   1
GPU6    NV12    NV12    NV12    NV12    NV12    NV12     X      NV1232-63   1
GPU7    NV12    NV12    NV12    NV12    NV12    NV12    NV12     X 32-63    1

Legend:

 X    = Self
 SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
 NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
 PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
 PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
 PIX  = Connection traversing at most a single PCIe bridge
 NV#  = Connection traversing a bonded set of # NVLinks

The issue is no matter what test.xml I used I get the same in-place and out-of-place results:
#
#                                                              out-of-place                       in-place
#       size         count      type   redop    root     time   algbw   busbw #wrong     time   algbw   busbw #wrong
#        (B)    (elements)                               (us)  (GB/s)  (GB/s)            (us)  (GB/s)  (GB/s)
         128            32     float     sum      -1    19.96    0.01    0.01      0    17.59    0.01    0.01      0
         256            64     float     sum      -1    17.75    0.01    0.03      0    17.78    0.01    0.03      0
         512           128     float     sum      -1    18.58    0.03    0.05      0    18.61    0.03    0.05      0
        1024           256     float     sum      -1    18.88    0.05    0.09      0    18.86    0.05    0.10      0
        2048           512     float     sum      -1    19.63    0.10    0.18      0    19.57    0.10    0.18      0
        4096          1024     float     sum      -1    21.03    0.19    0.34      0    21.01    0.19    0.34      0
        8192          2048     float     sum      -1    21.98    0.37    0.65      0    22.02    0.37    0.65      0
       16384          4096     float     sum      -1    22.44    0.73    1.28      0    22.48    0.73    1.28      0
       32768          8192     float     sum      -1    23.17    1.41    2.47      0    23.13    1.42    2.48      0
       65536         16384     float     sum      -1    24.22    2.71    4.74      0    24.14    2.72    4.75      0
      131072         32768     float     sum      -1    28.36    4.62    8.09      0    27.79    4.72    8.25      0
      262144         65536     float     sum      -1    44.06    5.95   10.41      0    43.96    5.96   10.44      0
      524288        131072     float     sum      -1    51.40   10.20   17.85      0    51.30   10.22   17.88      0
     1048576        262144     float     sum      -1    60.20   17.42   30.48      0    60.16   17.43   30.50      0
     2097152        524288     float     sum      -1    73.98   28.35   49.61      0    73.65   28.48   49.83      0
     4194304       1048576     float     sum      -1    100.2   41.86   73.25      0    99.04   42.35   74.11      0
     8388608       2097152     float     sum      -1    151.0   55.56   97.23      0    148.8   56.38   98.66      0
    16777216       4194304     float     sum      -1    254.9   65.81  115.16      0    254.6   65.89  115.31      0
    33554432       8388608     float     sum      -1    464.5   72.24  126.43      0    464.7   72.20  126.36      0

# Out of bounds values : 0 OK
# Avg bus bandwidth    : 28.4095

I have doubled checked even if we remove the text.xml, the INFO log still prints CCL INFO NCCL_ALGO set by environment to msccl/executor/msccl-executor-nccl/build/lib/msccl-algorithms/test.xml.
I have logged two cases with and without text.xml . Please find the attached log files out_without_xml.log out_with_allreduce_a100_allpairs.py_protocol=Simple_8_1_xml 1.log

The out_without_xml.log is when no .xml file was there in msccl/executor/msccl-executor-nccl/build/lib/msccl-algorithms
The out_with_allreduce_a100_allpairs.py_protocol.Simple_8_1_xml.1.log is when text.xml is generated and put in this path msccl/executor/msccl-executor-nccl/build/lib/msccl-algorithms

The command to generate the text.xml is below python msccl-tools/examples/mscclang/allreduce_a100_allpairs.py --protocol=Simple 8 1 > test.xml

you can use the msccl-tool to generate the algo file
you should modify the algo file which I already called out in last conversation to fullfill the missing attribute, like using shell script or any script works to you
copying the modified algo file to the algo folder, in your case it's /u/ahussain/workspace/msccl-ah/azure/msccl/executor/msccl-executor-nccl/build/lib/msccl-algorithms

below is the insight from your log...
my-system:52727:52807 [7] NCCL INFO Using MSCCL Algo files from /u/ahussain/workspace/msccl-ah/azure/msccl/executor/msccl-executor-nccl/build/lib/msccl-algorithms
my-system:52712:52782 [0] NCCL INFO Using MSCCL Algo files from /u/ahussain/workspace/msccl-ah/azure/msccl/executor/msccl-executor-nccl/build/lib/msccl-algorithms
my-system:52727:52807 [7] include/msccl/msccl_parser.h:70 NCCL WARN Attribute minBytes of node algo not found
my-system:52727:52807 [7] NCCL INFO include/msccl/msccl_parser.h:84 -> 3
my-system:52727:52807 [7] NCCL INFO misc/msccl/msccl_parser.cc:769 -> 3
my-system:52727:52807 [7] NCCL INFO misc/msccl/msccl_lifecycle.cc:147 -> 3
my-system:52727:52807 [7] NCCL INFO misc/msccl/msccl_lifecycle.cc:178 -> 3
my-system:52727:52807 [7] NCCL INFO misc/msccl/msccl_lifecycle.cc:220 -> 3
my-system:52727:52807 [7] NCCL INFO init.cc:1246 -> 3
my-system:52727:52807 [7] NCCL INFO init.cc:1391 -> 3
my-system:52727:52807 [7] NCCL INFO group.cc:68 -> 3 [Async thread]
my-system:52727:52727 [7] NCCL INFO group.cc:429 -> 3
my-system:52727:52727 [7] NCCL INFO group.cc:115 -> 3
my-system: Test NCCL failure common.cu:973 'internal error - please report this issue to the NCCL developers / '
.. my-system pid 52727: Test failure common.cu:857

I think this issue is resolved, I will open another one about generating .xml. Thanks


The technology behind dropping an attack traffic

Hello,
I have a question about how the Azure Ddos protection mitigates ddos attacks.
I understand that during the mitigation phase, traffics are sent to the DDos protection service for inspection;
healthy traffics are sent to the original destination and attack traffics are dropped.
My question is, how does the service drop attack traffics?
For example, if the ddos attack uses TCP, does Azure DDos Protection send a RST message to the client and drop the traffic?
Seems to be a very useful solution, but I wasnt able to clarify my understanding on the technology of dropping bad traffics.
Thank you in advance

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

ID: d9b8d15c-f9b4-ed8d-c53b-b2cec3721f23
Version Independent ID: e552f467-b412-fdda-3ad7-09d37b4b37cd
Content: Azure DDoS Protection features
Content Source: articles/ddos-protection/ddos-protection-features.md
Service: ddos-protection
GitHub Login: @AbdullahBell
Microsoft Alias: abell

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

any updates??

Hello @ShawnHag
Thank you for your question. Unfortunately, we cannot provide this specific information regarding how DDoS Protection prevents an attack.
This is because the information is confidential and disclosing it could pose a risk of exploitation by malicious actors.
If you would like more information regarding the logging of attacks, please see  View Azure DDoS Protection logs in Log Analytics workspace. The logging provides customers a detailed view of notifications, mitigation reports and mitigation flow logs within their environment.
#please-close


jsk_common: 2.0.0-1 in 'jade/distribution.yaml' [bloom]

Increasing version of package(s) in repository jsk_common to 2.0.0-1:

upstream repository: https://github.com/jsk-ros-pkg/jsk_common
release repository: https://github.com/tork-a/jsk_common-release.git
distro file: jade/distribution.yaml
bloom version: 0.5.20
previous version for package: 2.0.0-0

dynamic_tf_publisher

No changes

image_view2

No changes

jsk_common
* split jsk_common into jsk_common_msgs and jsk_3rdparty https://github.com/jsk-ros-pkg/jsk_common/issues/919
* Contributors: Kei Okada

jsk_data
* Fix default ROBOT name
* Contributors: Kohei Kimura

jsk_network_tools

No changes

jsk_tilt_laser
* [jsk_tilt_laser] Do not use laser_assembler in order to reduce CPU load
* Contributors: Ryohei Ueda

jsk_tools
* [jsk_tools] Record image_rect of axis camera
* [jsk_tools] Add calibration data
* [jsk_tools] Add launch to record axis camera
* Contributors: Kentaro Wada

jsk_topic_tools

No changes

multi_map_server

No changes

virtual_force_publisher
* pseudo jacobian has different for m>n and n<m
* format jacobian/effort/force output
* Contributors: Kei Okada

Thanks @k-okada the tags are all there this time. Including the last release's tags too.


Measuring element width in a layout that uses flexbox layout

Working on a site that uses flexbox CSS layout, I ran into an issue where only the lowest-resolution image would get loaded, even after resizing.
I narrowed it down to image.parentNode.clientWidth always returning zero in the determineAppropriateResolution function.
Adding a second fallback to offsetWidth seems to fix the issue:
Imager.prototype.determineAppropriateResolution = function (image) {
  return Imager.getClosestValue(image.getAttribute('data-width') || image.parentNode.clientWidth || image.parentNode.offsetWidth, this.availableWidths);
};

My problem isn't completely fixed- it still doesn't initially load the correct size image, but this seems to be an important step on the way.

Okay, it seems the parent node was an <a> tag which did not have display:block, and therefore did not have any measurable size - having fixed that, it now works without the added image.parentNode.offsetWidth fallback.
I wonder if the script ought to handle this case, and what would be the appropriate way to handle it? Throw an exception? Log the error to the console?
This sort of issue going to be common for sure, and should be handled somehow, I think?

Throwing an exception would be aggressive but failing silently is neither good.
So I would suggest to opt in for an explicitly written exception message, with an additional console.error (if available) message to help debugging the troublesome DOM element.
Otherwise, ideally another solution would be to walk up the DOM tree until we find an element with a width.

ideally another solution would be to walk up the DOM tree until we find an element with a width

Won't that lead to even-harder to debug cases? where you can't figure out where the width is coming from or why. I like simple, predictable, consistent behavior - walking up the tree means any of a number of elements could end up determining the width. Using the immediate parent, in my opinion, is cleaner and more predictable.

Maybe close this issue and open a new issue for improved error-handling?


Could not load file or assembly 'netstandard, Version=<IP_ADDRESS>,

When I run the example from README, I get printed 'False'.
Probably it has something to do with the weird warning I'm getting:
An instance of analyzer Generator.Equals.EqualsGenerator cannot be created from C:\Users\Patrik\.nuget\packages\generator.equals\0.3.0\analyzers\dotnet\cs\Generator.Equals.dll: Could not load file or assembly 'netstandard, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified..
Here's the code: https://github.com/PatrikBak/Bug.Generator.Equals
Visual Studio 2019 Version 16.8.1

@PatrikBak what framework are you targeting in your project? I have so far only tested with net50 targeting. I think it needs a tweak to target netstandard. I will have a look.

I deleted my previous comment as I had failed to see the attached example, so it did not make sense.
I tested your code and I get a complete different error due to the top-level statements my code I still don't support. After wrapping your code in a namespace, it worked.
Can you wrap your code in a namespace and try again? If that doesn't work, can you:

check you got the .NET 5.0 SDK RTM version installed;
you don't have any previews or rc installed;
build with dotnet command line (just to make sure it's not VS)?

I haven't tested with VS as I use Rider primarily.

@diegofrata
Thanks.
a) I wrapped the class in a namespace.
b) Regarding SDKs, this is what I have installed
Microsoft .NET Core SDK 3.1.100 (x64)
Microsoft .NET Framework 4.7.2 SDK
Microsoft .NET SDK 5.0.100 (x64) from Visual Studio
Windows SDK AddOn

Here are my observations:

If I do

dotnet clean
dotnet build
dotnet run --project Test

I get no warnings and it prints True.

In Visual Studio, after a rebuild, I still get the warning and it prints False.

If I remove the package, comment out its attributes and using, close VS, delete bin, obj, .vs, open VS, and run the program, then I see no warnings.

Weird. I tried adding NetStandard.Library as a reference, as I saw that in a different analyzer the other day. I released as 0.4.1-alpha1 in NuGet. Should be there in 20 minutes. Would you mind trying that?

@diegofrata
Sadly, it still doesn't work. Neither does it when tried on a different laptop with the latest VS and only one SDK installed, the one that came with the VS update. The .csproj file looks like this
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net5.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Generator.Equals" Version="0.4.1-alpha1">
    </PackageReference>
  </ItemGroup>

</Project>

A colleague of mine managed to run it on VS, both 0.4.0 and the alpha. It’s
definitely something with visual studio — perhaps it’s picking a different
MSBuild than you’d expect?
I’m installing it myself now to see if I can reproduce the problem
On Fri, 13 Nov 2020 at 15:34, PatrikBak<EMAIL_ADDRESS>wrote:

@diegofrata https://github.com/diegofrata
Sadly, it still doesn't work. Neither does it when tried on a different
laptop with the latest VS and only one SDK installed, the one that came
with the VS update. The .csproj file looks like this

Exe
net5.0

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/diegofrata/Generator.Equals/issues/2#issuecomment-726830960,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACLAT42TXBGJBLGFTGZTNLSPVGXBANCNFSM4TUMCC5Q
.

--
Diego Frata

Okay, I think my colleague did not fully test it -- I installed VS and got exactly the same error.
Apparently only netstandard2.0 is supported in VS, so I downgraded the generator from netstandard2.1 to 2.0 an now it works!
Please update to 0.6.0 and try again but I am confident it will work, so I am closing this issue. Let me know if needs reopening.


with install on laravel 8

www-data@f00346702ac4:~/crmv2$ composer require --dev mpociot/laravel-apidoc-generator
Using version ^4.8 for mpociot/laravel-apidoc-generator
./composer.json has been updated
Running composer update mpociot/laravel-apidoc-generator
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- mpociot/laravel-apidoc-generator v4.x-dev requires ramsey/uuid ^3.8 -> found ramsey/uuid[3.8.0, ..., 3.x-dev] but the package is fixed to 4.1.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- mpociot/laravel-apidoc-generator[4.8.0, ..., 4.8.2] require illuminate/console ^5.7|^6.0|^7.0 -> found illuminate/console[v5.7.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev] but it conflicts with another require.
- Root composer.json requires mpociot/laravel-apidoc-generator ^4.8 -> satisfiable by mpociot/laravel-apidoc-generator[4.8.0, 4.8.1, 4.8.2, v4.x-dev].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.

same errror

same

me too

Lol actually there is https://github.com/knuckleswtf/scribe for laravel 8
@vlad-groznov
@h6s8n
@simonproud

Lol actually there is https://github.com/knuckleswtf/scribe for laravel 8
@vlad-groznov
@h6s8n
@simonproud

Thanks for this. This is what I used :-)

Please make it compatible as soon as posible~~thank you

:( @mpociot

@mpociot
:no_mouth:

It work on master : composer require --dev mpociot/laravel-apidoc-generator:dev-master
@mpociot Just missing a new tag for this commit : https://github.com/mpociot/laravel-apidoc-generator/commit/b694bdedbf4d9d516e0fd6f95276ab727e4055e7

@mpociot :-(

@mpociot :-(

Problem 1
- mpociot/documentarian 0.4.0 requires illuminate/view 5.*|^6.0|^7.0 -> found illuminate/view[v5.0.0, ..., v5.8.36, v6.0.0, ..., v6.20.8, v7.0.0, ..., v7.30.1] but it conflicts with another require.
- mpociot/laravel-apidoc-generator dev-master requires mpociot/documentarian ^0.4.0 -> satisfiable by mpociot/documentarian[0.4.0].
- Root composer.json requires mpociot/laravel-apidoc-generator dev-master -> satisfiable by mpociot/laravel-apidoc-generator[dev-master].

Problem 1
- mpociot/documentarian 0.4.0 requires illuminate/view 5.*|^6.0|^7.0 -> found illuminate/view[v5.0.0, ..., v5.8.36, v6.0.0, ..., v6.20.8, v7.0.0, ..., v7.30.1] but it conflicts with another require.
- mpociot/laravel-apidoc-generator dev-master requires mpociot/documentarian ^0.4.0 -> satisfiable by mpociot/documentarian[0.4.0].
- Root composer.json requires mpociot/laravel-apidoc-generator dev-master -> satisfiable by mpociot/laravel-apidoc-generator[dev-master].

+1 - Does anyone recommend a fork that is updated?

+1 - Does anyone recommend a fork that is updated?

Here's a temporary solution to continue using this package. 😁
"mpociot/documentarian": "dev-master as 0.4.0",
"mpociot/laravel-apidoc-generator": "dev-master",

Here's a temporary solution to continue using this package. 😁
"mpociot/documentarian": "dev-master as 0.4.0",
"mpociot/laravel-apidoc-generator": "dev-master",

Here's a temporary solution to continue using this package. 😁
"mpociot/documentarian": "dev-master as 0.4.0",
"mpociot/laravel-apidoc-generator": "dev-master",

thanks this worked for me

Here's a temporary solution to continue using this package. 😁
"mpociot/documentarian": "dev-master as 0.4.0",
"mpociot/laravel-apidoc-generator": "dev-master",

thanks this worked for me

For those also landing here, knuckleswtf/scribe is a near drop-in replacement and supports Laravel 8 - I upgraded in 5-10 minutes.
https://scribe.readthedocs.io/en/latest/migrating.html

For those also landing here, knuckleswtf/scribe is a near drop-in replacement and supports Laravel 8 - I upgraded in 5-10 minutes.
https://scribe.readthedocs.io/en/latest/migrating.html

Problem 1
- Conclusion: remove laravel/framework v8.24.0
- Conclusion: don't install laravel/framework v8.24.0

Problem 1
    - Conclusion: remove laravel/framework v8.27.0
    - Conclusion: don't install laravel/framework v8.27.0
    - Conclusion: don't install laravel/framework v8.26.1
    - Conclusion: don't install laravel/framework v8.26.0
    - Conclusion: don't install laravel/framework v8.25.0
    - Conclusion: don't install laravel/framework v8.24.0
    - Conclusion: don't install laravel/framework v8.23.1
    - Conclusion: don't install laravel/framework v8.23.0
    - Conclusion: don't install laravel/framework v8.22.1
    - Conclusion: don't install laravel/framework v8.22.0
    - Conclusion: don't install laravel/framework v8.21.0
    - Conclusion: don't install laravel/framework v8.20.1
    - Conclusion: don't install laravel/framework v8.20.0
    - Conclusion: don't install laravel/framework v8.19.0
    - Conclusion: don't install laravel/framework v8.18.1
    - Conclusion: don't install laravel/framework v8.18.0
    - Conclusion: don't install laravel/framework v8.17.2
    - Conclusion: don't install laravel/framework v8.17.1
    - Conclusion: don't install laravel/framework v8.17.0
    - Conclusion: don't install laravel/framework v8.16.1
    - Conclusion: don't install laravel/framework v8.16.0
    - Conclusion: don't install laravel/framework v8.15.0
    - Conclusion: don't install laravel/framework v8.14.0
    - Conclusion: don't install laravel/framework v8.13.0
    - Conclusion: don't install laravel/framework v8.12.3
    - Conclusion: don't install laravel/framework v8.12.2
    - Conclusion: don't install laravel/framework v8.12.1
    - Conclusion: don't install laravel/framework v8.12.0
    - Conclusion: don't install laravel/framework v8.11.2
    - Conclusion: don't install laravel/framework v8.11.1
    - Conclusion: don't install laravel/framework v8.11.0
    - Conclusion: don't install laravel/framework v8.10.0
    - Conclusion: don't install laravel/framework v8.9.0
    - Conclusion: don't install laravel/framework v8.8.0
    - Conclusion: don't install laravel/framework v8.7.1
    - Conclusion: don't install laravel/framework v8.7.0
    - Conclusion: don't install laravel/framework v8.6.0
    - Conclusion: don't install laravel/framework v8.5.0
    - Conclusion: don't install laravel/framework v8.4.0
    - Conclusion: don't install laravel/framework v8.3.0
    - Conclusion: don't install laravel/framework v8.2.0
    - Conclusion: don't install laravel/framework v8.1.0
    - Conclusion: don't install laravel/framework v8.0.4
    - Conclusion: don't install laravel/framework v8.0.3
    - Conclusion: don't install laravel/framework v8.0.2
    - Conclusion: don't install laravel/framework v8.0.1
    - Conclusion: don't install laravel/framework v8.0.0
    - mpociot/laravel-apidoc-generator 4.8.2 requires illuminate/routing ^5.7|^6.0|^7.0 -> satisfiable by illuminate/routing[5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, 6.x-dev, 7.x-dev, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9, v6.0.0, v6.0.1, v6.0.2, v6.0.3, v6.0.4, v6.1.0, v6.10.0, v6.11.0, v6.12.0, v6.13.0, v6.13.1, v6.14.0, v6.15.0, v6.15.1, v6.16.0, v6.17.0, v6.17.1, v6.18.0, v6.18.1, v6.18.10, v6.18.11, v6.18.12, v6.18.13, v6.18.14, v6.18.15, v6.18.16, v6.18.17, v6.18.18, v6.18.19, v6.18.2, v6.18.20, v6.18.21, v6.18.22, v6.18.23, v6.18.24, v6.18.25, v6.18.26, v6.18.27, v6.18.28, v6.18.29, v6.18.3, v6.18.30, v6.18.31, v6.18.32, v6.18.33, v6.18.34, v6.18.35, v6.18.36, v6.18.37, v6.18.38, v6.18.39, v6.18.4, v6.18.40, v6.18.41, v6.18.42, v6.18.43, v6.18.5, v6.18.6, v6.18.7, v6.18.8, v6.18.9, v6.19.0, v6.19.1, v6.2.0, v6.20.0, v6.20.1, v6.20.10, v6.20.11, v6.20.12, v6.20.13, v6.20.14, v6.20.15, v6.20.16, v6.20.2, v6.20.3, v6.20.4, v6.20.5, v6.20.6, v6.20.7, v6.20.8, v6.20.9, v6.3.0, v6.4.1, v6.5.0, v6.5.1, v6.5.2, v6.6.0, v6.6.1, v6.6.2, v6.7.0, v6.8.0, v7.0.0, v7.0.1, v7.0.2, v7.0.3, v7.0.4, v7.0.5, v7.0.6, v7.0.7, v7.0.8, v7.1.0, v7.1.1, v7.1.2, v7.1.3, v7.10.0, v7.10.1, v7.10.2, v7.10.3, v7.11.0, v7.12.0, v7.13.0, v7.14.0, v7.14.1, v7.15.0, v7.16.0, v7.16.1, v7.17.0, v7.17.1, v7.17.2, v7.18.0, v7.19.0, v7.19.1, v7.2.0, v7.2.1, v7.2.2, v7.20.0, v7.21.0, v7.22.0, v7.22.1, v7.22.2, v7.22.3, v7.22.4, v7.23.0, v7.23.1, v7.23.2, v7.24.0, v7.25.0, v7.26.0, v7.26.1, v7.27.0, v7.28.0, v7.28.1, v7.28.2, v7.28.3, v7.28.4, v7.29.0, v7.29.1, v7.29.2, v7.29.3, v7.3.0, v7.30.0, v7.30.1, v7.30.2, v7.30.3, v7.30.4, v7.4.0, v7.5.0, v7.5.1, v7.5.2, v7.6.0, v7.6.1, v7.6.2, v7.7.0, v7.7.1, v7.8.0, v7.8.1, v7.9.0, v7.9.1, v7.9.2].
    - mpociot/laravel-apidoc-generator v4.x-dev requires illuminate/routing ^5.7|^6.0 -> satisfiable by illuminate/routing[5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, 6.x-dev, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9, v6.0.0, v6.0.1, v6.0.2, v6.0.3, v6.0.4, v6.1.0, v6.10.0, v6.11.0, v6.12.0, v6.13.0, v6.13.1, v6.14.0, v6.15.0, v6.15.1, v6.16.0, v6.17.0, v6.17.1, v6.18.0, v6.18.1, v6.18.10, v6.18.11, v6.18.12, v6.18.13, v6.18.14, v6.18.15, v6.18.16, v6.18.17, v6.18.18, v6.18.19, v6.18.2, v6.18.20, v6.18.21, v6.18.22, v6.18.23, v6.18.24, v6.18.25, v6.18.26, v6.18.27, v6.18.28, v6.18.29, v6.18.3, v6.18.30, v6.18.31, v6.18.32, v6.18.33, v6.18.34, v6.18.35, v6.18.36, v6.18.37, v6.18.38, v6.18.39, v6.18.4, v6.18.40, v6.18.41, v6.18.42, v6.18.43, v6.18.5, v6.18.6, v6.18.7, v6.18.8, v6.18.9, v6.19.0, v6.19.1, v6.2.0, v6.20.0, v6.20.1, v6.20.10, v6.20.11, v6.20.12, v6.20.13, v6.20.14, v6.20.15, v6.20.16, v6.20.2, v6.20.3, v6.20.4, v6.20.5, v6.20.6, v6.20.7, v6.20.8, v6.20.9, v6.3.0, v6.4.1, v6.5.0, v6.5.1, v6.5.2, v6.6.0, v6.6.1, v6.6.2, v6.7.0, v6.8.0].
    - don't install illuminate/routing 5.7.17|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing 5.7.18|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing 5.7.19|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing 5.7.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing 5.8.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing 6.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing 7.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.10|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.11|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.15|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.20|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.21|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.22|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.23|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.26|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.27|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.5|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.7|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.7.9|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.11|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.12|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.14|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.15|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.17|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.18|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.19|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.20|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.22|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.24|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.27|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.29|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.30|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.31|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.32|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.33|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.34|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.35|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.36|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v5.8.9|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.0.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.0.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.0.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.0.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.0.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.1.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.10.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.11.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.12.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.13.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.13.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.14.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.15.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.15.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.16.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.17.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.17.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.10|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.11|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.12|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.13|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.14|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.15|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.16|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.17|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.18|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.19|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.20|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.21|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.22|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.23|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.24|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.25|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.26|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.27|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.29|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.30|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.31|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.32|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.33|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.34|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.35|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.36|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.37|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.38|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.39|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.40|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.41|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.42|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.43|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.5|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.7|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.18.9|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.19.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.19.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.2.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.10|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.11|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.12|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.13|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.14|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.15|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.16|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.5|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.7|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.20.9|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.3.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.4.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.5.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.5.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.5.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.6.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.6.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.6.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.7.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v6.8.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.0.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.0.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.0.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.0.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.0.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.0.5|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.0.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.0.7|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.0.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.1.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.1.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.1.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.1.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.10.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.10.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.10.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.10.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.11.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.12.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.13.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.14.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.14.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.15.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.16.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.16.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.17.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.17.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.17.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.18.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.19.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.19.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.2.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.2.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.2.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.20.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.21.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.22.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.22.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.22.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.22.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.22.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.23.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.23.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.23.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.24.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.25.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.26.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.26.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.27.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.28.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.28.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.28.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.28.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.28.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.29.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.29.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.29.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.29.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.3.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.30.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.30.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.30.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.30.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.30.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.4.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.5.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.5.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.5.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.6.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.6.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.6.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.7.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.7.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.8.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.8.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.9.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.9.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/routing v7.9.2|don't install laravel/framework 8.x-dev
    - Installation request for laravel/framework ^8.0 -> satisfiable by laravel/framework[8.x-dev, v8.0.0, v8.0.1, v8.0.2, v8.0.3, v8.0.4, v8.1.0, v8.10.0, v8.11.0, v8.11.1, v8.11.2, v8.12.0, v8.12.1, v8.12.2, v8.12.3, v8.13.0, v8.14.0, v8.15.0, v8.16.0, v8.16.1, v8.17.0, v8.17.1, v8.17.2, v8.18.0, v8.18.1, v8.19.0, v8.2.0, v8.20.0, v8.20.1, v8.21.0, v8.22.0, v8.22.1, v8.23.0, v8.23.1, v8.24.0, v8.25.0, v8.26.0, v8.26.1, v8.27.0, v8.3.0, v8.4.0, v8.5.0, v8.6.0, v8.7.0, v8.7.1, v8.8.0, v8.9.0].
    - Installation request for mpociot/laravel-apidoc-generator ^4.8.2 -> satisfiable by mpociot/laravel-apidoc-generator[4.8.2, v4.x-dev].

Here's a temporary solution to continue using this package. 😁
"mpociot/documentarian": "dev-master as 0.4.0",
"mpociot/laravel-apidoc-generator": "dev-master",

This also worked for me, thanks.

This would work for me, if it weren't for fzaninotto/faker.
That need to be replaced by the community fork fakerphp/faker. See #808

@kasperhartwich I'm using fakerphp/faker but it still throw error about 'fzaninotto/faker' and it's a fresh install of laravel 8 with sail

I removed fakerphp/faker and these lines works perfectly
"mpociot/documentarian": "dev-master as 0.4.0",
"mpociot/laravel-apidoc-generator": "dev-master",
but when I want to install fakerphp/faker again , I get these errors
- Root composer.json requires fakerphp/faker ^1.13 -> satisfiable by fakerphp/faker[v1.13.0].     - mpociot/laravel-apidoc-generator dev-master requires fzaninotto/faker ^1.8 -> satisfiable by fzaninotto/faker[1.9.x-dev (alias of dev-master)].     - fzaninotto/faker 1.9.x-dev conflicts with fakerphp/faker v1.13.0.     - mpociot/laravel-apidoc-generator is locked to version dev-master and an update of this package was not requested.

bump

bump

bump

Here's a temporary solution to continue using this package. grin
"mpociot/documentarian": "dev-master as 0.4.0",
"mpociot/laravel-apidoc-generator": "dev-master",

This worked for me thanks

add this in composer.json file and run composer install.
"mpociot/documentarian": "dev-master as 0.4.0",
"mpociot/laravel-apidoc-generator": "dev-master",


Remove scodec bits + Streaming multipart

:D.
NOTE:
The decoder is defined very closely in terms of Chunk.Byte. This was a conscious decision assuming that we get our chunks in this format from the sockets, as it is simply more efficient (since drop is defined in terms of splitAt, it will allocate an extra object for a split :frowning: ) There is an FS2 Pr open that's bincompat with 0.10 https://github.com/functional-streams-for-scala/fs2/pull/1105 that targets the  extra allocation of drop/take.
That said, I'm totally ok with porting this PR over to remove the use of Chunk.Byte in favor of the split, drop and take ops on Chunk[Byte]. Thoughts appreciated.
Changed to use Chunk[Byte].
Closes #1531
Closes #876
Benchmarks on impl:
[info] # Run complete. Total time: 00:03:00
[info] Benchmark                                      Mode  Cnt    Score    Error  Units
[info] Bench.MultipartBench.bigNewMultipart          thrpt   10   35.601 ±  3.328  ops/s
[info] Bench.MultipartBench.bigOldMultipart          thrpt   10    1.579 ±  0.041  ops/s
[info] Bench.MultipartBench.bigPartBodyNewMultipart  thrpt   10   46.773 ±  3.869  ops/s
[info] Bench.MultipartBench.bigPartBodyOldMultipart  thrpt   10    1.633 ±  0.042  ops/s
[info] Bench.MultipartBench.mediumNewMultipart       thrpt   10  107.311 ±  0.937  ops/s
[info] Bench.MultipartBench.mediumOldMultipart       thrpt   10    6.080 ±  0.072  ops/s
[info] Bench.MultipartBench.smallNewMultipart        thrpt   10  835.194 ± 13.572  ops/s
[info] Bench.MultipartBench.smallOldMultipart        thrpt   10  771.936 ±  9.681  ops/s

Located here

Running into an issue testing this first.


Added MRB_API function to get only block arguments

MRB_API function added:

 mrb_get_arg_block()
 mrb_block_given_p() -- The name comes from CRuby's rb_block_given_p ()

At the same time, it applies to f_instance_eval() and f_class_eval() of mruby-eval.

I am not fully satisfied with mrb_get_arg_block (mrb_block_given_p is OK). Why do we need this function where we can retrieve the block argument with mrb_get_args. Thus I don't understand the benefit of the changes for eval.c neither.

There is no strong reason, but:

Because there is mrb_get_arg{c,v,1}() functions.
Because it is heavy to use mrb_get_args() inside the mrb_block_given_p() function.

OK, I will modify and merge the patch.

merged by f678620a436aa015f9252858aa00112256ab0668


Remove DI from core language

Found we are barely using it in practice and it's trivial to create at user level, doesn't require 2 token types, 2 opcodes, and custom context management to achieve.
Removes DI and factory Tests.
Remember to Add/Update the:

[x] Sample scripts
[x] Test scripts

Changes unknown
when pulling 46ab7a545e5c37b756c2ac24bf1c77cfffb18b94 on remove-di
into ** on main**.


Add debounce and throttle options

This was already kind proposed in #9 and multiple other issues call for more lazy inputs like #151 and #40.
A debounce option is good option to remain interactive and performant without the hassle of e.g. an explicit submit button.

when there are multiple DB queries bounding to the Inputs' value, it's doing queries again and again after every keystroke of user input, a lot of those expensive DB queries are wasted;
https://observablehq.com/search?query=debounce although there are many debounce implementation, but all involves a lot of extra code wrapping the builtin Inputs.{text, range, select, textarea, ...}, feeling like doing a lot of boiler plates code,
better to be builtin; :+1:
viewof textarea = Inputs.textarea({label: "Description",
  // debounce: 200ms, or wait: 200ms? or whatever parameter you call it
  // default to no debounce behavior;
})

@tx0c For inputs that trigger queries I would recommend to always use the {submit: true} option.

but submit option isn't available for all Inputs; on number Slider value and other types, better to have debounce option:
viewof Limit = Inputs.range({ label: "Limit",
  // debounce: 200ms, or wait: 200ms? or whatever parameter you call it
  // default to no debounce behavior;
})

This issue is probably going to remain open for a while longer, so here's a simple helper:
function debounce(input, delay = 500) {
  class E extends Event {}
  let id;
  input.addEventListener("input", e => {
    if(e instanceof E) return;
    e.stopImmediatePropagation();
    clearTimeout(id);
    id = setTimeout(() => input.dispatchEvent(new E("input"), {bubbles: true}), delay);
  });
  return input;
}

Example:
viewof myValue = debounce(Inputs.range([0, 100]))


[feature] add ParseEnumPipe to built-in pipes

ValidateEnumPipe might be better naming since it doesn't have to convert it to another format


iOS 5 compatibility and scrolling to bottom in landscape

Here are some changes I made to use this category with iOS 5 and also to fix an issue where UIWebView could not be scrolled to the bottom of the page when in landscape orientation (in iOS 5,6 & 7).

Closing this. Sorry for the delay in the response, but I never had intention in supporting iOS5 with this.


Composer Required Package Issue

So, im having a issue with composer. It keeps having http request failed errors for the file ""http://packagist.org/p/illuminate/cookie%243989eaaa6d018ca55f2075677fff25bd2f536f27f80a0937a9e69f87e36c9.json" Trying it in chrome or firefox or opera results in a 404 error.
And btw it seems like the bootloader is requiring illuminate/html which is now replaced by larvarel/html.
Background Information:
Linux Ubuntu 10.4.2 LTS
PHP5, (all things installed)
TechnicSolder Latest
NGNIX

I would double check you have the latest composer version.

I downloaded composer 0.7 then used composers inbuilt updater. should have latest v

Are you able to attempt the install again? If so, is there any more information pertaining to the failed package install?

Attempting the install again, same issue. And no thats all the error said. Exactly this:
""http://packagist.org/p/illuminate/cookie%243989eaaa6d018ca55f2075677fff25bd2f536f27f80a0937a9e69f87e36c9.json" : HTTP REQUEST FAILED. Thats it. Should i try running it in a debug mode if there is one?

Actually, This time it came up with the error "Cannot create cache directory /home/mac.composer/cache/repo/https---packagist.org/, or directory is not writable proceeding without cache
Repeats twice.

Try rerunning as root. That should fix the cache error, though that's not your main issue.

Trying that the yellow message was gone, the red message continues:

This is getting a little old now(30 days) but I really need some help to get this working. My new modpack depends on me getting it working. Thanks in advance -Mac

actually, now that i look back at this, it probably has something to do with you using an os that eol'd 4 years ago...

Ok i will try updating the OS to the latest ubuntu LTS.

Answer: use sudo apt-get upgrade.


Lint Dockerfile

Issues are resolved by #7

merged https://github.com/jkahrs/cert-manager-webhook-hostingde/pull/7 now fixed in master


predict_proba does not work after freeze()

Hi, seems like a bug. Unless I'm missing a step?
trainer.model.predict_proba raises an error if used after training the differentiable head.
Code:
model = SetFitModel.from_pretrained(
      "sentence-transformers/paraphrase-mpnet-base-v2",
      use_differentiable_head=True,
      head_params={"out_features": 4},
  )

trainer = SetFitTrainer(
    model=model,
    train_dataset=train_dataset,
    eval_dataset=eval_dataset,
    loss_class=CosineSimilarityLoss,
    batch_size=4,
    num_iterations=20,
    num_epochs=1
)

trainer.train()

trainer.freeze()
trainer.unfreeze(keep_body_frozen=True)

trainer.train(
    num_epochs=10,
    batch_size=4,
    body_learning_rate=1e-5,
    learning_rate=1e-2,
    l2_weight=None,
)

print(trainer.evaluate())

trainer.model(list_of_strings) # works
trainer.model.predict_proba(list_of_strings) # does not work

/opt/conda/lib/python3.7/site-packages/setfit/modeling.py in predict_proba(self, x_test)
    329     def predict_proba(self, x_test: List[str]) -> Union[torch.Tensor, np.ndarray]:
    330         embeddings = self.model_body.encode(x_test, normalize_embeddings=self.normalize_embeddings)
--> 331         return self.model_head.predict_proba(embeddings)
    332
    333     def __call__(self, inputs):

/opt/conda/lib/python3.7/site-packages/setfit/modeling.py in predict_proba(self, x_test)
    133         self.eval()
    134
--> 135         return self(x_test)
    136
    137     def predict(self, x_test: Union[torch.Tensor, "ndarray"]) -> Union[torch.Tensor, "ndarray"]:

/opt/conda/lib/python3.7/site-packages/torch/nn/modules/module.py in _call_impl(self, *input, **kwargs)
   1192         if not (self._backward_hooks or self._forward_hooks or self._forward_pre_hooks or _global_backward_hooks
   1193                 or _global_forward_hooks or _global_forward_pre_hooks):
-> 1194             return forward_call(*input, **kwargs)
   1195         # Do not call functions when jit is used
   1196         full_backward_hooks, non_full_backward_hooks = [], []

/opt/conda/lib/python3.7/site-packages/setfit/modeling.py in forward(self, features, temperature)
    117
    118         x = features["sentence_embedding"] if is_features_dict else features
--> 119         logits = self.linear(x)
    120         if self.out_features == 1:  # only has one target
    121             outputs = torch.sigmoid(logits)

/opt/conda/lib/python3.7/site-packages/torch/nn/modules/module.py in _call_impl(self, *input, **kwargs)
   1192         if not (self._backward_hooks or self._forward_hooks or self._forward_pre_hooks or _global_backward_hooks
   1193                 or _global_forward_hooks or _global_forward_pre_hooks):
-> 1194             return forward_call(*input, **kwargs)
   1195         # Do not call functions when jit is used
   1196         full_backward_hooks, non_full_backward_hooks = [], []

/opt/conda/lib/python3.7/site-packages/torch/nn/modules/linear.py in forward(self, input)
    112
    113     def forward(self, input: Tensor) -> Tensor:
--> 114         return F.linear(input, self.weight, self.bias)
    115
    116     def extra_repr(self) -> str:

TypeError: linear(): argument 'input' (position 1) must be Tensor, not numpy.ndarray

Directly using the model body and head seem to work:
embeddings = model_frozen.model_body.encode(
    list_of_strings,
    convert_to_tensor=True
)
model_frozen.model_head.predict_proba(embeddings)

I was missing the convert_to_tensor=True.
Seems duplicate and related to https://github.com/huggingface/setfit/issues/237. Can close.

Hello!

Seems duplicate and related to https://github.com/huggingface/setfit/issues/237. Can close.

You're exactly right. It's indeed related to the convert_to_tensor=True. The issue has been fixed in #207, but I'm afraid I do not have the necessary permissions to publish a release.
Until a new release is pushed, likely some time in early February, you can either use SetFit from the GitHub repository directly. Off the top of my head that involves:
pip install git+https://github.com/huggingface/setfit.git

or you can use exactly the workaround that you described.
I'll close this for now.

Tom Aarsen


Compile cli anytime

@mullefel, @Niederb, @haerdib: I guess you have some make/C++ experience. I discussed with @gaudenzkessler to remove all source file checks because we noticed again that our check is incomplete; for instance, we didn't re-build the CLI if only the STF's toml changed.
I argued to remove all checks for source file changes and to always execute the build with the argumentation that cargo can detect the changes itself, and it will be an overhead of a second only if we let cargo do the check. The same is true for the edger8r.
Does anyone of you have arguments to keep those checks? If not, I would argue to remove them for all executed builds.

I also discussed with Gaudenz a little bit. Yes I thinks to remove the additional checks in the Makefile and rely on cargo to figure out the dependencies

Works for me


cloudflare_origin_ca_certificate resource creation fails due to Error: error creating origin certificate: Authentication error (10000)

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
Terraform v1.3.6
on darwin_amd64

provider registry.terraform.io/cloudflare/cloudflare v3.30.0
provider registry.terraform.io/hashicorp/google v4.44.0
provider registry.terraform.io/hashicorp/google-beta v4.44.0
provider registry.terraform.io/hashicorp/tls v4.0.4

Affected resource(s)
cloudflare_origin_ca_certificate
Terraform configuration files
provider "cloudflare" {
}

terraform {
  required_providers {
    cloudflare = {
      source  = "cloudflare/cloudflare"
      version = "3.30.0"
    }
    google = {
      version = "4.44.0"
    }
    google-beta = {
      version = "4.44.0"
    }
  }
}

resource "tls_private_key" "api-cert-private-key" {
  algorithm = "RSA"
}

resource "tls_cert_request" "api-cert-request" {
  private_key_pem = tls_private_key.api-cert-private-key.private_key_pem
}

resource "cloudflare_origin_ca_certificate" "api-cert" {
  csr                  = tls_cert_request.api-cert-request.cert_request_pem
  hostnames            = ["example.com"]
  request_type         = "origin-rsa"
  requested_validity   = 365
  min_days_for_renewal = 10
}

Link to debug output
https://gist.github.com/Akshaya-T/19404c6fddcca1d9f0c439e0114dee3d
Panic output
│ Error: error creating origin certificate: Authentication error (10000)
│
│   with cloudflare_origin_ca_certificate.api-cert,
│   on certificate.tf line 9, in resource "cloudflare_origin_ca_certificate" "api-cert":
│    9: resource "cloudflare_origin_ca_certificate" "api-cert" {
│
╵
Operation failed: failed running terraform apply (exit 1)
Expected output
Cloud flare ssl certificate should be provisioned.
Actual output
│ Error: error creating origin certificate: Authentication error (10000)
│
│   with cloudflare_origin_ca_certificate.api-cert,
│   on certificate.tf line 9, in resource "cloudflare_origin_ca_certificate" "api-cert":
│    9: resource "cloudflare_origin_ca_certificate" "api-cert" {
│
╵
Operation failed: failed running terraform apply (exit 1)
Steps to reproduce

Create API Token from cloudflare with ssl certificate write permission
Use the token in the provider and run the code mentioned in the Terraform configuration files.

Additional factoids
Using terraform cloud and have created the variable set CLOUDFLARE_API_TOKEN with the cloudflare API token with the ssl certificate write permission. But still facing error while provisioning the certificate.
Tried passing the token directly in the provider block as well but still not working.
eg:
 provider "cloudflare" {   api_token = "1244" }
References
No response

you cannot use API tokens for the origin CA resource; see the documentation for details on this - https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/origin_ca_certificate

Stumbled upon it looking for which permissions are needed for this action. The latter message from @jacobbednarz is valid for older provider versions, but the newer ones accept all authentication schemas:
(from the link https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/origin_ca_certificate)
Since [v3.32.0](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v3.32.0) all authentication schemes are supported for managing Origin CA certificates. Versions prior to v3.32.0 will still need to use [api_user_service_key](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/index#api_user_service_key).

Leaving for anyone who'll encounter this issue.

I'm having he same issue, getting a 10000 when trying to create a certificate.
I tried with the latest terraform provider 4.22 as well as the suggested 3.32, both with the same error message:
Error: error creating origin certificate: Authentication error (10000)
(...) in resource "cloudflare_origin_ca_certificate" (...)

Permissions on the user api token are:

Account: SSL and Certificates:Edit, Access: Mutual TLS Certificates:Edit
Domain:  SSL and Certificates:Edit, Page Rules:Edit, DNS:Edit

Creating the resources tls_private_key and tls_cert_request worked without issues.
Does it require anything else?