Invalid/Dead link

PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue
I wanted to use the containers to upgrade a customer NAV2016 to Business Central. But the link to the NAV2016 manifest is not working
Scripts used to create container and cause the issue
$containerName = 'upgrade2016'
$password = 'P@ssw0rd'
$securePassword = ConvertTo-SecureString -String $password -AsPlainText -Force
$credential = New-Object pscredential 'admin', $securePassword
$auth = 'UserPassword'
$artifactUrl = Get-NavArtifactUrl -nav '2016' -cu '7' -country 'dk'
$databaseServer = 'host.containerhelper.internal'
$databaseInstance = ''
$databaseName = 'customerDatabase'
$databaseUsername = 'sa'
$databasePassword = '*********'
$databaseSecurePassword = ConvertTo-SecureString -String $databasePassword -AsPlainText -Force
$databaseCredential = New-Object pscredential $databaseUsername, $databaseSecurePassword
$licenseFile = 'd:\nav\infar\udvikling\bc13.flf'
New-BcContainer     -accept_eula
-containerName $containerName     -credential $credential
-auth $auth     -artifactUrl $artifactUrl
-databaseServer $databaseServer -databaseInstance $databaseInstance -databaseName $databaseName     -databaseCredential $databaseCredential
-licenseFile $licenseFile     -shortcuts DesktopFolder
-includeCSIDE -doNotExportObjectsToText `
-updateHosts
Full output of scripts
New-BcContainerWizard
Setting usePsSession = True
Setting hostHelperFolder = D:\BcContainerHelper
Setting use7zipIfAvailable = True
Setting defaultNewContainerParameters = @{Credential=; Accept_Eula=True; Isolation=Process; UpdateHosts=True; Auth=UserPassword}
Setting containerHelperFolder = C:\ProgramData\BcContainerHelper
Setting defaultContainerName = bcserver
Setting sandboxContainersAreMultitenantByDefault = True
Setting genericImageName = mcr.microsoft.com/dynamicsnav:{0}-generic
Setting bcartifactsCacheFolder = D:\Artifacts.cache
BcContainerHelper version 2.0.1
Launching C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\2.0.1\CreateScript.ps1

$containerName = 'upgrade2016'
$password = 'P@ssw0rd'
$securePassword = ConvertTo-SecureString -String $password -AsPlainText -Force
$credential = New-Object pscredential 'admin', $securePassword
$auth = 'UserPassword'
$artifactUrl = Get-NavArtifactUrl -nav '2016' -cu '7' -country 'dk'
$databaseServer = 'host.containerhelper.internal'
$databaseInstance = ''
$databaseName = 'customerDatabase'
$databaseUsername = 'sa'
$databasePassword = '*********'
$databaseSecurePassword = ConvertTo-SecureString -String $databasePassword -AsPlainText -Force
$databaseCredential = New-Object pscredential $databaseUsername, $databaseSecurePassword
$licenseFile = 'd:\nav\infar\udvikling\bc13.flf'
New-BcContainer `
    -accept_eula `
    -containerName $containerName `
    -credential $credential `
    -auth $auth `
    -artifactUrl $artifactUrl `
    -databaseServer $databaseServer -databaseInstance $databaseInstance -databaseName $databaseName `
    -databaseCredential $databaseCredential `
    -licenseFile $licenseFile `
    -shortcuts DesktopFolder `
    -includeCSIDE -doNotExportObjectsToText `
    -updateHosts

Default parameter Isolation = Process
BcContainerHelper is version 2.0.1
BcContainerHelper is running as administrator
Host is Microsoft Windows 10 Pro - 2004
Docker Client Version is 20.10.5
Docker Server Version is 20.10.5
Downloading application artifact /onprem/9.0.45834.0/dk
Downloading C:\Users\Svend\AppData\Local\Temp\66914d4d-9cb0-45f8-936e-dee0d26e16a7.zip
Unpacking application artifact to tmp folder using 7zip
Downloading platform artifact /onprem/9.0.45834.0/platform
Downloading C:\Users\Svend\AppData\Local\Temp\230f823d-13b1-455a-86f4-c76988623713.zip
Unpacking platform artifact to tmp folder using 7zip
Downloading Prerequisite Components
Downloading D:\Artifacts.cache\onprem\9.0.45834.0\platform\Prerequisite Components\Open XML SDK 2.5 for Microsoft Office\OpenXMLSDKv25.msi
Downloading D:\Artifacts.cache\onprem\9.0.45834.0\platform\Prerequisite Components\Microsoft Report Viewer 2015\ReportViewer.msi
Downloading D:\Artifacts.cache\onprem\9.0.45834.0\platform\Prerequisite Components\IIS URL Rewrite Module\rewrite_2.0_rtw_x64.msi
Downloading D:\Artifacts.cache\onprem\9.0.45834.0\platform\Prerequisite Components\Microsoft Report Viewer 2015\SQLSysClrTypes.msi
Downloading D:\Artifacts.cache\onprem\9.0.45834.0\platform\Prerequisite Components\DotNetCore\DotNetCore.1.0.4_1.1.1-WindowsHosting.exe
Fetching all docker images
Pulling image mcr.microsoft.com/dynamicsnav:10.0.19041.685-generic
DockerDo : Error response from daemon: manifest for mcr.microsoft.com/dynamicsnav:10.0.19041.685-generic not found: manifest unknown: manifest tagged
by "10.0.19041.685-generic" is not found
ExitCode: 1
Commandline: docker pull  mcr.microsoft.com/dynamicsnav:10.0.19041.685-generic
At C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\2.0.1\ContainerHandling\New-NavContainer.ps1:703 char:13
+             DockerDo -command pull -imageName $bestImageName | Out-Nu ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,DockerDo

Screenshots
Additional context
Tried updating the bccontainerhelper just to make sure, but get the same error.
Sidenote or request: Us docker newbies don't know the various conventions, so perhaps a small on containernaming while the wizard helps create the script? My first result had a containername starting with numerics (and contained uncerscore "_" ) Your HelperFunctions did not like that :)
Container name should start with a letter (a-z)
At C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\2.0.1\HelperFunctions.ps1:174 char:9

    throw "Container name should start with a letter (a-z)"

Remove this line from your c:\programdata\bccontainerhelper\bccontainerhelper.config.json file:
"genericImageName": "mcr.microsoft.com/dynamicsnav:{0}-generic",

Small step further
Setting usePsSession = True
Setting hostHelperFolder = D:\BcContainerHelper
Setting use7zipIfAvailable = True
Setting defaultNewContainerParameters = @{Credential=; Accept_Eula=True; Isolation=Process; UpdateHosts=True; Auth=UserPassword}
Setting containerHelperFolder = C:\ProgramData\BcContainerHelper
Setting defaultContainerName = bcserver
Setting sandboxContainersAreMultitenantByDefault = True
Setting bcartifactsCacheFolder = D:\Artifacts.cache
BcContainerHelper version 2.0.7
Default parameter Credential
Default parameter Isolation = Process
Default parameter UpdateHosts = True
Default parameter Auth = UserPassword
BcContainerHelper is version 2.0.7
BcContainerHelper is running as administrator
Host is Microsoft Windows 10 Pro - 2004
Docker Client Version is 20.10.5
Docker Server Version is 20.10.5
Fetching all docker images
Fetching all docker volumes
You have to specify artifactUrl or imageName when creating a new container.
At C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\2.0.7\ContainerHandling\New-NavContainer.ps1:677 char:13

        throw "You have to specify artifactUrl or imageName when  ...

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : OperationStopped: (You have to spe... new container.:String) [], RuntimeException
FullyQualifiedErrorId : You have to specify artifactUrl or imageName when creating a new container.

Also, should I leave the line out for good, or only when using old NAV versions?

For good - you should only include settings in the settings file which you have a reason to change.
Not sure why artifacturl is empty:
Get-NavArtifactUrl -nav '2016' -cu '7' -country 'dk'
https://bcartifacts.azureedge.net/onprem/9.0.45834.0/dk

Check the variables and more

artifactUrl had value here as well. Tried running full script again, but did not help.
However restarting with New-bccontainerwizard and going through the motions seem to have done the trick. Currently downloading and verifying checksums :)
Thank you


Clean setup.py

As part of PEP-517 agenda we should clean the setup.py file and only make use of setuptools-scm, reducing its size to 2-3 lines.
Ideally we would have removed the file completely but we will postpone this until we have confirmation that rpm building tools are updated to be able to build python projects that do not have a setup.py file.

TY for this

Duplicate of https://github.com/ansible/ansible-navigator/issues/553 and https://github.com/ansible/ansible-navigator/issues/554.


Add gluster RWO provisioner.

Signed-off-by: Humble Chirammal<EMAIL_ADDRESS>

@wongma7 PTAL.

@wongma7 Addressed the comments. Thanks..

how to update dependencies:

glide get k8s.io/apimachinery#c810e49 -v
glide-vc --use-lock-file
OPTIONAL:
reset changes in glide.lock that you don't want/need then run glide install -v

lgtm


a simple question about saving npzfile

Hi, when I use d2net-preprocess to reproduce the npz file, I got NpzFile object using np.load(path, allow_pickle=True).
However, I got dict object when I read your npz. I want to know how you save the npzfile

We use np.savez_compressed().

Thanks!


Pick random port for libertem-server if default/choice not available

Closes #1184
Change the way the server binds to a port server.bind_socket() rather than server.listen() so that we can explicitly create the socket ourselves and set/access its port. Sets a random port if the default/choice by using the alias port 0 when binding to the socket. Required returning the socket object from server.py:main() so that server.py:run() can launch the correct address in the browser tab.
Tested running/using the server on Windows and Linux. I think there is no direct testing of the server.py:main/run, though, I will  try to look into that.
Contributor Checklist:

[x] I have added or updated my entry in the creators.json file
[x] I have added a changelog entry for my contribution
[ ] I have added/updated documentation for all user-facing changes
[ ] I have added/updated test cases
[ ] I have included the rebuilt production build of the client (only if changes were made to the GUI)

Reviewer Checklist:

[ ] /azp run libertem.libertem-data passed
[x] No import of GPL code from MIT code

/azp run libertem.libertem-data

I would agree with choosing a random port if the default is already in use - there is a potential issue with choosing a random port if the explicitly stated port is in use: if we are automatically launching the LiberTEM server, for example for integration into jupyter via libertem-jupyter-proxy, the launch will succeed, but the proxy will be set up for whatever random software is listening on the conflicting port. In that case, I would say that failing to launch is better.
So, maybe we could only choose a random port in the default case, and continue with the original behavior if the port was chosen explicitly?
Is there a reason for only listening on IPv4? Previously, IPv6 was supported - I'd like to keep this functionality if possible!

So, maybe we could only choose a random port in the default case, and continue with the original behavior if the port was chosen explicitly?

Sounds reasonable! 👍

OK, I will work on those changes, should all be possible.

Is there a reason for only listening on IPv4? Previously, IPv6 was supported - I'd like to keep this functionality if possible!

Mainly laziness on my part, it simplifies unpacking the sockets (When I did not specify I had a single IPv4 socket on Ubuntu but both an IPv4 and IPv6 socket on Windows!). I will work something out.

Those changes have been made, with some bonus additional handling of IPv6 hostnames.
New behaviour:

No port specifier -> default to 9000 -> random port if already in use
Port specified -> raise the address in use OSError raised by bind_sockets

I haven't been able to test a case where the hostname maps to two or more IP addresses (v4 and v6 at the same time, for example), which binds more than one socket, so for now I just launch the browser tab at the hostname:port of the first bound socket.
More generally testing all this functionality seems challenging, looking through ./test/server it seems like all the server api tests are done using the custom class ServerThread(threading.Thread): and not the actual CLI/server launcher functions. Is that right ?
NOTE: I also adjusted the 'localhost'/insecure check to also accept '<IP_ADDRESS>' and '::1' without error. @sk1p can you say if this is a security issue ?

No port specifier -> default to 9000 -> random port if already in use
Port specified -> Already in use -> raise the address in use OSError raised by bind_sockets

:+1:

More generally testing all this functionality seems challenging, looking through ./test/server it seems like all the server api tests are done using the custom class ServerThread(threading.Thread): and not the actual CLI/server launcher functions. Is that right ?

That's right - the tests in test/server are IIRC a bit older than much of the CLI functionality - we should have added tests when the CLI gained more options.

NOTE: I also adjusted the 'localhost'/insecure check to also accept '<IP_ADDRESS>' and '::1' without error. @sk1p can you say if this is a security issue ?

Sounds good!

Thanks!


Recently we got AccessViolationException

Hi! Recently we've got the following exception. It happened one time and we cannot reproduce it.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at Microsoft.Win32.TaskScheduler.V2Interop.IRegisteredTask.get_Definition()
at Microsoft.Win32.TaskScheduler.Task.GetV2Definition(TaskService svc, IRegisteredTask iTask, Boolean throwError)
at Microsoft.Win32.TaskScheduler.Task.get_Definition()
We run our WPF application on Win7, .Net 3.5.
Originally posted: 2015-02-19T07:13:11

I've just gone through the code and cannot find a place where there is even a memory allocation or deallocation related to that code. The particular line is even within a "try" clause. My only guess (and sorry to push this off but I really can't see anything that would lead to that exception) is that it has something to do with Microsoft's internal library. That particular method call (IRegisteredTask.get_Definition) is a call into one of Microsoft's COM objects. It would not be surprising given the complexity of that result (ITaskDefinition) and I could see a corner case in creating the return object. I'll leave this issue open for a few months in case you are able to narrow the problem down though.
Originally posted: 2015-02-19T09:21:28

Originally posted: 2015-07-09T19:05:36


chore: reduce more epoch log noise

Closes: #XXX
What is the purpose of the change
This PR aims to reduce more noise that occurs during epoch logs:

Errors occur when attempting to swap fees collected to a specific denom, usually due to a lack of liquidity in the pool that exists. Since this is expected, for this epoch loop of swapping fees, we:

Move the individual error logs to debug logs
Emit an info log with the aggregated data (how much we attempted to swap across what pools) that did not get swapped this epoch, and if specifics are desired, the debug logs can be reviewed.

Testing and Verifying
I ran this logic on v23 mainnet during the last epoch and it got through with no issues, while only emitting the desired logs.
Documentation and Release Note

[ ] Does this pull request introduce a new feature or user-facing behavior changes?
[ ] Changelog entry added to Unreleased section of CHANGELOG.md?

Where is the change documented?

[ ] Specification (x/{module}/README.md)
[ ] Osmosis documentation site
[ ] Code comments?
[ ] N/A

@mattverse I reduced the code duplication and ran the action to update all go mod imports

@czarcas7ic  ace! LGTM 😎


VMware Resource pool update to Ford Branch

VMware resource pool feature set update. Terraform.tfvars have to updated accordingly for this change to work

Hitting EOF error trying to launch. Doing further testing now.

Please address feedback above and after edits, do: terraform fmt . ; make docs examples to format all TF code, and regenerate any docs and examples that would've changed in the process.

Please close this PR and open it against the 1.7.3 rebase branch after the edits are made: https://github.com/lander2k2/tectonic-installer/tree/1.7.3-tectonic.1-ford instead.
I've tested this PR in the lab on top of the new rebase, and it is working.

Closing.  Needs to be opened against the 1.7.3 branch.


Boosting results from only one field

I'm playing with the example implementation here and I'd expect that when I enter name:john^1000000 body:john it will prioritize results where the word "john" is in its title.
But that's not what's happening. The first result is "Charles Duke" and then "John Young" which is not what I'd expect. It looks like the boost has no effect.

for posterity, I had the same issue and determined it was because boosts are relative to terms for the same field only


Mention time and space complexities in comments

For each algorithm, mention its time complexity and space complexity in the "description comment" of its implementation program.
The format for the "description comment" (which is written at the beginning) should be:
/*
    <Name of algorithm>
    -------------------
    <Brief description>

    Time complexity
    ---------------
    O(...), where <description of variable(s)>

    Space complexity
    ----------------
    O(...), where <description of variable(s)>
*/

Following are the algorithms for which time and space complexity hasn't been added yet:

[ ] N-Queens
[ ] Kadane
[ ] Binary search
[x] Bubble sort
[x] Counting sort
[x] Insertion sort
[x] Merge sort
[x] Quick sort
[x] Selection sort

I think its a good idea to put this in the readme or coding guidlines.

Yes. Thanks for the suggestion!

Name of algorithm: Binary Search
Binary search algorithm is a searching algorithm which uses Divide and conquer technique to search the given element. The prior requirements before applying Binary search is that elements should be present in sorted order.

Time complexity:
O(nlogn), where n is the number of input elements

Space complexity:
O(n), where n is the number of input elements

Time complexity of binary search is O(logN) and it's space complexity is O(1)

Name of algorithm: Bubble Sort
Bubble sort is a simple sorting algorithm that repeatedly steps through the list to be sorted, compares each pair of adjacent items and swaps them if they are in the wrong order.
Time Complexity:
O(n^2), where n is the number of elements in the list.
Space Complexity:
O(1), temporary space for swapping.

Name of algorithm: Insertion Sort
Insertion sort is a simple sorting algorithm that builds the final sorted array (or list) one item at a time. Less suitable for large lists.
Time Complexity:
O(n^2), where n is the number of elements in the list.
Space Complexity:
O(1), temporary space for swapping.

Name of algorithm: Selection Sort
The selection sort algorithm sorts an array by repeatedly finding the minimum element (considering ascending order) from the unsorted part and putting it at its right place.
Time Complexity:
O(n^2), where n is the number of elements in the list.
Space Complexity:
O(1), temporary space for swapping.

Name of algorithm: Merge Sort
Merge sort is a Divide and Conquer algorithm. It divides input array into two halves, recursively calls itself for the two halves and then merges the two sorted halves.
Time Complexity:
O(n*logn), where n  is the number of elements in the list.
Space Complexity:
O(n), where n  is the number of elements in the list.

Name of algorithm: Quick Sort
Like merge sort, quick sort is a Divide and Conquer algorithm. It picks an element as pivot and partitions the given array around the picked pivot, then recursively calls itself on those partitions.
Statistically, for large data sets, it amounts to be the fastest sorting algorithm.
Time Complexity:
Worst case ->> O(n^2)
Average case ->> O(n*logn), where n is the number of elements in the list.
Space Complexity:
O(1)

@abhishekabk5 For sorting programs, the complexities have already been added.
But your descriptions of the algorithms are much better :+1:. Would you mind sending a PR for those? (It would be a good opportunity to get into open source!)
NOTE: For quick sort, the worst-case time complexity would also be O(N * log(N)) because this variant of quick sort uses random pivot selection which makes the worst-case complexity equal to the average-case complexity which is O(N * log(N)).

Sure, I'll get to it.

@faheel About quick sort, I don't believe that technically, random pivot selection would help in worst case time complexity as an unsorted array can already be considered as random. So, the worst case time complexity would still be O(n^2). Tell me if I'm wrong.
Also, in that case, random selection is redundant. It should be removed.

@faheel About quick sort, I don't believe that technically, random pivot selection would help in worst case time complexity as an unsorted array can already be considered as random. So, the worst case time complexity would still be O(n^2). Tell me if I'm wrong.
Also, in that case, random selection is redundant. It should be removed.

Binary Search
Divide and conquer algorithm -
Given an array of presorted integers: A(0), A(1), A(2), ... , A(n-1) and and a target value X, find and return i such that X = A(i) or return -1 if X is not in the list.
Solution:

recursive:
check if the middle value is X and return if it is, else if the middle value is greater to X then search the left side of the list, this dividing the search time. Else search the right side. This is a recursive function, so the search will stop once X is found or the base case is reached.

iterative:
use a loop and conditionals with the same logic. while (left <= right){ mid = (left+right)/2; if X... }
Time complexity

Best case:
θ(1) when X = middle right away.
worst/ average case:
T(N) = θ(Log(N)), where, T(N) = the time complexity, θ(f(N)) = the tight bounded analysis.
Space complexity
----------------
Recursive:
O( log(N) ), where N = the depth of the tree, and describes how many recursive stacks have been called.
Iterative:
O(1) space since there are no stack calls.

@abhishekabk5 The randomised version of quick sort selects a pivot randomly for a given range of indices, and this partitions the elements around this randomly selected pivot. Therefore, the expected worst-case time complexity comes out to be O(N * log(N)) (see §3.4 in this document for a detailed proof).
But yes, the absolute worst-case time complexity even for the randomised version would still be O(N2), but as the number of elements increase, the probability that this case arises decreases (exponentially, I guess).
So I think that mentioning both the expected and the absolute worst-case complexity for quick sort would be the better thing.

@tb25 The overhead space of the call stack is not considered while calculating the space complexity of recursive functions. Moreover, the implementation of binary search here uses tail recursion which eliminates the stack overhead (if the compiler optimises for it).

@faheel so you're saying that the space complexity of the recursive algorithm is O(N) or O(1)?

Binary Search
Divide and conquer algorithm -
Given an array of presorted integers: A(0), A(1), A(2), ... , A(n-1) and and a target value X, find and return i such that X = A(i) or return -1 if X is not in the list.
Solution:
recursive:
check if the middle value is X and return if it is, else if the middle value is greater to X then search the left side of the list, this dividing the search time. Else search the right side. This is a recursive function, so the search will stop once X is found or the base case is reached.
iterative:
use a loop and conditionals with the same logic. while (left <= right){ mid = (left+right)/2; if X... }
Time complexity
Best case:
θ(1) when X = middle right away.
worst/ average case:
T(N) = θ(Log(N)), where, T(N) = the time complexity, θ(f(N)) = the tight bounded analysis.
Space complexity
O(1), where 1 is the variable X that is created to check for the target value.


grounding dino contrastive loss

if the input is a pair of text (e.g., A cat sets on a table .) and image, what would be the label and the equation of the contrastive loss?

@ProjectDisR The token corresponding to the position of "cat" is the positive sample.


[BUG] Error while uploading to labelbox for annotations

System information

OS Platform and Distribution: Ubuntu 20.04.6 LTS (Databricks)
Python version (python --version): 3.9.5
FiftyOne version (fiftyone --version): 0.21.6
FiftyOne installed from (pip or source): pip

Describe the problem
While using Dataset.annotate() with backend='labelbox', the labelbox server responds with a 'Failed to upload, message: File upload error - invalid MIME type' error for .bmp images.
Reference:
Relevant code block in FiftyOne
Code to reproduce issue
import requests
from PIL import Image
from io import BytesIO
import fiftyone as fo

img_path = "example.bmp"
response = requests.get('https://filesamples.com/samples/image/bmp/sample_640%C3%97426.bmp')
img = Image.open(BytesIO(response.content))
img.save(img_path)

LABELBOX_API_KEY = "<your labelbox api key>"
classes = {
    "class1",
    "class2"
}

sample = fo.Sample(filepath="example.bmp")
dataset = fo.Dataset("test")
dataset.add_sample(sample)
dataset.annotate(anno_key="test", backend="labelbox", api_key=LABELBOX_API_KEY, label_field="ground_truth", label_type="detections", classes=classes)

What areas of FiftyOne does this bug affect?

[ ] App: FiftyOne application issue
[x] Core: Core Python library issue
[ ] Server: FiftyOne server issue

Willingness to contribute
The FiftyOne Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the FiftyOne codebase?

[x] Yes. I can contribute a fix for this bug independently
[ ] Yes. I would be willing to contribute a fix for this bug with guidance from the FiftyOne community
[ ] No. I cannot contribute a bug fix at this time

Found a simple fix: The Labelbox SDK uses the Python mimetypes to infer image mime types. This, in turn, looks up mime types from /etc/mime.types on Linux. On the Databricks cluster I was using, the mime type for BMP images was image/x-ms-bmp instead of the expected image/bmp, causing Labelbox to throw an incorrect mime error.
Solution was to simply update the mime type entry for BMP images in /etc/mime.types to the correct value.


TypeError when session is left

Below code throws TypeError when the program exits, apparently the fix is to close the event loop as discussed here: https://bugs.python.org/issue23548
import asyncio
import sys

from autobahn.asyncio.component import Component, run

component = Component(
    transports=[
        {
            "type": "rawsocket",
            "url": "ws://localhost/ws",
            "endpoint": {
                "type": "unix",
                "path": "/home/om26er/Documents/cb/.crossbar/crossbar.sock",
            },
            "serializer": "json",
        }
    ],
    realm=u"realm1"
)

@component.on_join
async def on_join(session, details):
    data = await session.call('com.example.rawsocket-cbor.run', command)
    print(data)
    session.leave()

if __name__ == "__main__":
    command = sys.argv[1]
    run([component])

The said error logs:
Exception ignored in: <bound method BaseEventLoop.__del__ of <_UnixSelectorEventLoop running=False closed=True debug=False>>
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/base_events.py", line 431, in __del__
  File "/usr/lib/python3.5/asyncio/unix_events.py", line 58, in close
  File "/usr/lib/python3.5/asyncio/unix_events.py", line 139, in remove_signal_handler
  File "/usr/lib/python3.5/signal.py", line 47, in signal
TypeError: signal handler must be signal.SIG_IGN, signal.SIG_DFL, or a callable object

fixed by https://github.com/crossbario/autobahn-python/pull/904


CTA component (with all states and MO button)

PURCHASE-2702
As a collector I want to see a CTA to make an offer, or displaying the specific status of an offer, when accessing a conversation about an artwork that fulfills the required conditions to be offer-able from inquiry.
Acceptance criteria:
-All states should be accounted for, and displayed given the conditions.
-No action should be accounted for (as of this ticket) when engaging with the CTA.
Because of the way. the components are configured, I also ended up adding the make offer button and hooking it up to the modal that Joel made.

Fails

:no_entry_sign:

Please use <SystemQueryRenderer /> instead of <QueryRender />. This prevents double fetching during the server-side render pass. See:

src/v2/Apps/Conversation/Components/OpenInquiryModalButton.tsx

  Generated by :no_entry_sign: dangerJS against 46fb7eb07a2e2ade2f8f02294a3635e8635447f5


Added Graduate Admission Classifcation using Adaboost.

[x]  C++ notebook
[x]  Python notebook
[x]  Visualization and graphs
[ ]  Markdown annotations & explanations (WIP)
[ ]  Dataset source

Dataset Source: https://drive.google.com/file/d/1lmV2rTyD8WxgNKanMGlG73swVDO95ued/view?usp=sharing

Dataset uploaded - http://datasets.mlpack.org/Admission_Predict.csv

Looks great to me, let me know if you need any help with the merge conflict.

Hi @zoq  I'm sorry the uploaded dataset has some issues. Please upload this https://drive.google.com/file/d/18N_ragpP72_Q8FthWtWiRJqMzkxopT0O/view?usp=sharing

Looks great to me, let me know if you need any help with the merge conflict.

Hi @zoq I'm sorry the uploaded dataset has some issues. Please upload this https://drive.google.com/file/d/18N_ragpP72_Q8FthWtWiRJqMzkxopT0O/view?usp=sharing

No problem, uploaded the updated dataset.


Add C++ Solution for Problem Of The Day | 15 January 2023

Comment below if you're interested in working on this issue and would like to be assigned to it.

Please assign this issue to me


Added NavEntry to navigate with a button navigation

Description:

Linked issues:

Screenshots:

How to test:

it shows me this error

Do not merge I got an Update for Navigation


Is it working for laravel 6 or 7?

I've installed it over laravel version 7.2 it's not working at all.could you provide any solution it's urgent......
@Crinsane @tkaw220 @jackmcdade

I'm working on a fork that's compatible with Laravel 7 - everything seems to be working at the moment, but please submit a pull request if not;
https://github.com/olimortimer/LaravelShoppingcart

@olimortimer  i've tried that package and that was the result
C:\xampp2\htdocs\E-commerce>composer require olimortimer/laravelshoppingcart
Using version ^4.0 for olimortimer/laravelshoppingcart
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for gloudemans/shoppingcart ^2.6 -> satisfiable by gloudemans/shoppingcart[2.6.0].
- Conclusion: remove laravel/framework v5.8.37
- Conclusion: don't install laravel/framework v5.8.37
- gloudemans/shoppingcart 2.6.0 requires illuminate/events 5.1.* || 5.2.* || 5.3.* || 5.4.* || 5.5.|| 5.6. || 5.7.* -> satisfiable by illuminate/events[5.1.x-dev, 5.2.x-dev, 5.3.x-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8, v5.2.0, v5.2.19, v5.2.21, v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.2.6, v5.2.7, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, 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].
- don't install illuminate/events 5.1.x-dev|don't install laravel/framework v5.8.37
- don't install illuminate/events 5.2.x-dev|don't install laravel/framework v5.8.37
- don't install illuminate/events 5.3.x-dev|don't install laravel/framework v5.8.37
- don't install illuminate/events 5.4.x-dev|don't install laravel/framework v5.8.37
- don't install illuminate/events 5.5.x-dev|don't install laravel/framework v5.8.37
- don't install illuminate/events 5.6.x-dev|don't install laravel/framework v5.8.37
- don't install illuminate/events 5.7.17|don't install laravel/framework v5.8.37
- don't install illuminate/events 5.7.18|don't install laravel/framework v5.8.37
- don't install illuminate/events 5.7.19|don't install laravel/framework v5.8.37
- don't install illuminate/events 5.7.x-dev|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.1.1|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.1.13|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.1.16|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.1.2|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.1.20|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.1.22|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.1.25|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.1.28|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.1.30|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.1.31|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.1.41|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.1.6|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.1.8|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.2.0|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.2.19|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.2.21|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.2.24|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.2.25|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.2.26|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.2.27|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.2.28|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.2.31|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.2.32|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.2.37|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.2.43|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.2.45|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.2.6|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.2.7|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.3.0|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.3.16|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.3.23|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.3.4|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.4.0|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.4.13|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.4.17|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.4.19|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.4.27|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.4.36|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.4.9|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.5.0|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.5.16|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.5.17|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.5.2|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.5.28|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.5.33|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.5.34|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.5.35|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.5.36|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.5.37|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.5.39|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.5.40|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.5.41|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.5.43|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.5.44|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.0|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.1|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.10|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.11|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.12|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.13|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.14|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.15|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.16|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.17|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.19|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.2|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.20|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.21|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.22|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.23|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.24|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.25|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.26|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.27|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.28|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.29|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.3|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.30|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.31|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.32|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.33|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.34|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.35|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.36|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.37|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.38|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.39|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.4|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.5|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.6|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.7|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.8|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.6.9|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.0|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.1|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.10|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.11|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.15|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.2|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.20|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.21|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.22|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.23|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.26|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.27|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.28|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.3|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.4|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.5|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.6|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.7|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.8|don't install laravel/framework v5.8.37
- don't install illuminate/events v5.7.9|don't install laravel/framework v5.8.37
- Installation request for laravel/framework (locked at v5.8.37, required as 5.8.*) -> satisfiable by laravel/framework[v5.8.37].
Installation failed, reverting ./composer.json to its original content.

@phoeni2020 please try again and raise an issue against my fork if it happens again

The same issue, can't install it on Laravel 6

@mrsherlock1 the fork that I have made?  Please try again and raise an issue against my fork if it happens again

@mrsherlock1 the fork that I have made? Please try again and raise an issue against my fork if it happens again

I'm working on a fork that's compatible with Laravel 7 - everything seems to be working at the moment, but please submit a pull request if not;
https://github.com/olimortimer/LaravelShoppingcart

it's working ...thanks

I'm working on a fork that's compatible with Laravel 7 - everything seems to be working at the moment, but please submit a pull request if not;
https://github.com/olimortimer/LaravelShoppingcart

it's working ..Thanks

E:\XAMPP\htdocs\first>composer require gloudemans/shoppingcart
Using version ^2.6 for gloudemans/shoppingcart
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1

Installation request for gloudemans/shoppingcart ^2.6 -> satisfiable by gloudemans/shoppingcart[2.6.0].
Conclusion: remove laravel/framework v7.5.2
Conclusion: don't install laravel/framework v7.5.2
gloudemans/shoppingcart 2.6.0 requires illuminate/events 5.1.* || 5.2.* || 5.3.* || 5.4.* || 5.5.|| 5.6. || 5.7.* -> satisfiable by illuminate/events[5.1.x-dev, 5.2.x-dev, 5.3.x-
dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8,
v5.2.0, v5.2.19, v5.2.21, v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.2.6, v5.2.7, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.
4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6
.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.
6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, 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].
don't install illuminate/events 5.1.x-dev|don't install laravel/framework v7.5.2
don't install illuminate/events 5.2.x-dev|don't install laravel/framework v7.5.2
don't install illuminate/events 5.3.x-dev|don't install laravel/framework v7.5.2
don't install illuminate/events 5.4.x-dev|don't install laravel/framework v7.5.2
don't install illuminate/events 5.5.x-dev|don't install laravel/framework v7.5.2
don't install illuminate/events 5.6.x-dev|don't install laravel/framework v7.5.2
don't install illuminate/events 5.7.17|don't install laravel/framework v7.5.2
don't install illuminate/events 5.7.18|don't install laravel/framework v7.5.2
don't install illuminate/events 5.7.19|don't install laravel/framework v7.5.2
don't install illuminate/events 5.7.x-dev|don't install laravel/framework v7.5.2
don't install illuminate/events v5.1.1|don't install laravel/framework v7.5.2
don't install illuminate/events v5.1.13|don't install laravel/framework v7.5.2
don't install illuminate/events v5.1.16|don't install laravel/framework v7.5.2
don't install illuminate/events v5.1.2|don't install laravel/framework v7.5.2
don't install illuminate/events v5.1.20|don't install laravel/framework v7.5.2
don't install illuminate/events v5.1.22|don't install laravel/framework v7.5.2
don't install illuminate/events v5.1.25|don't install laravel/framework v7.5.2
don't install illuminate/events v5.1.28|don't install laravel/framework v7.5.2
don't install illuminate/events v5.1.30|don't install laravel/framework v7.5.2
don't install illuminate/events v5.1.31|don't install laravel/framework v7.5.2
don't install illuminate/events v5.1.41|don't install laravel/framework v7.5.2
don't install illuminate/events v5.1.6|don't install laravel/framework v7.5.2
don't install illuminate/events v5.1.8|don't install laravel/framework v7.5.2
don't install illuminate/events v5.2.0|don't install laravel/framework v7.5.2
don't install illuminate/events v5.2.19|don't install laravel/framework v7.5.2
don't install illuminate/events v5.2.21|don't install laravel/framework v7.5.2
don't install illuminate/events v5.2.24|don't install laravel/framework v7.5.2
don't install illuminate/events v5.2.25|don't install laravel/framework v7.5.2
don't install illuminate/events v5.2.26|don't install laravel/framework v7.5.2
don't install illuminate/events v5.2.27|don't install laravel/framework v7.5.2
don't install illuminate/events v5.2.28|don't install laravel/framework v7.5.2
don't install illuminate/events v5.2.31|don't install laravel/framework v7.5.2
don't install illuminate/events v5.2.32|don't install laravel/framework v7.5.2
don't install illuminate/events v5.2.37|don't install laravel/framework v7.5.2
don't install illuminate/events v5.2.43|don't install laravel/framework v7.5.2
don't install illuminate/events v5.2.45|don't install laravel/framework v7.5.2
don't install illuminate/events v5.2.6|don't install laravel/framework v7.5.2
don't install illuminate/events v5.2.7|don't install laravel/framework v7.5.2
don't install illuminate/events v5.3.0|don't install laravel/framework v7.5.2
don't install illuminate/events v5.3.16|don't install laravel/framework v7.5.2
don't install illuminate/events v5.3.23|don't install laravel/framework v7.5.2
don't install illuminate/events v5.3.4|don't install laravel/framework v7.5.2
don't install illuminate/events v5.4.0|don't install laravel/framework v7.5.2
don't install illuminate/events v5.4.13|don't install laravel/framework v7.5.2
don't install illuminate/events v5.4.17|don't install laravel/framework v7.5.2
don't install illuminate/events v5.4.19|don't install laravel/framework v7.5.2
don't install illuminate/events v5.4.27|don't install laravel/framework v7.5.2
don't install illuminate/events v5.4.36|don't install laravel/framework v7.5.2
don't install illuminate/events v5.4.9|don't install laravel/framework v7.5.2
don't install illuminate/events v5.5.0|don't install laravel/framework v7.5.2
don't install illuminate/events v5.5.16|don't install laravel/framework v7.5.2
don't install illuminate/events v5.5.17|don't install laravel/framework v7.5.2
don't install illuminate/events v5.5.2|don't install laravel/framework v7.5.2
don't install illuminate/events v5.5.28|don't install laravel/framework v7.5.2
don't install illuminate/events v5.5.33|don't install laravel/framework v7.5.2
don't install illuminate/events v5.5.34|don't install laravel/framework v7.5.2
don't install illuminate/events v5.5.35|don't install laravel/framework v7.5.2
don't install illuminate/events v5.5.36|don't install laravel/framework v7.5.2
don't install illuminate/events v5.5.37|don't install laravel/framework v7.5.2
don't install illuminate/events v5.5.39|don't install laravel/framework v7.5.2
don't install illuminate/events v5.5.40|don't install laravel/framework v7.5.2
don't install illuminate/events v5.5.41|don't install laravel/framework v7.5.2
don't install illuminate/events v5.5.43|don't install laravel/framework v7.5.2
don't install illuminate/events v5.5.44|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.0|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.1|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.10|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.11|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.12|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.13|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.14|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.15|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.16|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.17|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.19|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.2|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.20|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.21|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.22|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.23|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.24|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.25|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.26|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.27|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.28|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.29|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.3|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.30|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.31|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.32|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.33|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.34|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.35|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.36|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.37|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.38|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.39|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.4|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.5|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.6|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.7|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.8|don't install laravel/framework v7.5.2
don't install illuminate/events v5.6.9|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.0|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.1|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.10|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.11|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.15|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.2|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.20|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.21|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.22|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.23|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.26|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.27|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.28|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.3|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.4|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.5|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.6|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.7|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.8|don't install laravel/framework v7.5.2
don't install illuminate/events v5.7.9|don't install laravel/framework v7.5.2
Installation request for laravel/framework (locked at v7.5.2, required as ^7.0) -> satisfiable by laravel/framework[v7.5.2].

Installation failed, reverting ./composer.json to its original content.
@Crinsane @tkaw220 @jackmcdade

@shovokhan have you tried my fork of the repo?

I'm working on a fork that's compatible with Laravel 7 - everything seems to be working at the moment, but please submit a pull request if not;

https://github.com/olimortimer/LaravelShoppingcart

I'm working on a fork that's compatible with Laravel 7 - everything seems to be working at the moment, but please submit a pull request if not;
https://github.com/olimortimer/LaravelShoppingcart

Thank you. It helpful for me. (laravel 7)

I've also created a fork, including various bugs that have been found in this repo such as the ability to now do GST per line item, which is needed in places like Australia. As well as new features like CartFee which is essentially shipping fee.
We are using this fork actively on a major ecommerce site so should always be stable.
https://github.com/digital-bird/LaravelShoppingcart/


Cheng Zhang

UPDATE_00001
by Cheng Zhang
23/11/2016
■Bug Fixes
·Fixed two bugs that leaded to unstability since two variables were not initialized.
■Additions to Functions
·Added a function to record max runup of wave.
·Added a function to record varying bathymetry.
·Added a function to hot start simulation.
·Added a function to limit max maximum Froude number.
·Added a function to generate irregular waves with a internal wave maker.
·Added a function to impose nesting data as boundary conditions.
■Changes
·Changed Sommerfeld open boundary condition to Orlanski open boundary condition.
·Changed subroutine flux_left_right_boundary to impose velocity at inflow boundary.
·Changed subroutine probes to output velocity components at each layer when setting z=-1.0 in stat.txt

Cheng's updates are merged into the NHWAVE master.  These should not overlap with Gangfeng's additions, which I have not received a pull request for yet.

Cheng Zhang branch deleted.  (Cheng, if you want to make more modifications, you need to start a new branch and work with that.  Please do that rather than continuing to modify your existing code.


File explorer is expanding all root folders in a MR workspace

Steps to Reproduce:

Create a MR workspace file with more than one folder
Open the MR workspace

🐛 All top level folders are expanded. This is very slow if there are lot of root folders and also if the MR workspace is in remote

@sandy081 how are you creating your MR workspace? By composing an XXX.code-workspace file directly, then opening it? Or by opening the first folder from File\Open Folder... and then using File\Add Folder to Workspace... to add more folders to make it MR? Or some other way?
When I create a MR workspace and save it, then collapse the top-level folders, then exit VS Code, restart and reopen the MR workspace, the top-level folders remain collapsed. But if I then create a copy of that .code-workspace file and open this, the root folders get expanded (and I also get asked the trust question). Presumably the expand happens because my local storage hasn't got any collapse-state record for a workspace with this name, so it defaults to expanding the first level. I suppose VS Code could be changed so it defaults to keeping root folders collapsed for a workspace it hasn't previously seen. But some users might complain about such a change.

I suppose VS Code could be changed so it defaults to keeping root folders collapsed for a workspace it hasn't previously seen. But some users might complain about such a change.

I think like @bpasero suggested in the duplicate issue, we probably need a limit here. It's nice when you have 3-4 folders to expand but 100s+ can crash VS Code.

By composing an XXX.code-workspace file directly, then opening it?

Yes


Support job archive

to resolve #4453
Support job archive (only Completed jobs can be archived, cannot unarchive job):

Add rest-server interface:

PUT /jobs/{user}~{job}/archive

Admin can archive any job; non-admin user can only archive his own job.
Only completed job can be archived. If job is not a completed job, return 400 Bad Request.
If the job cannot be found, return 404 not found.
If job is successfully archived, return 202 Accepted.
If other error happens, return 500.

Add write-merger interface

PUT /archiveFramework/:frameworkName

Only completed job can be archived. If job is not a completed job, return 400 Bad Request.
If the job is not found, return 404 not found.
If job is successfully archived, return 200 OK.
If other error happens, return 500.

Change rest-server list job api:

support to include archived jobs or not. Default is not to include archived jobs

if a job has been archived, does it appear in the history server?

if a job has been archived, does it appear in the history server?

What does the term history server refers to? Since v1.2.0, all frameworks are stored in the table frameworks. Archive a framework means set archived=true in this table. The archived jobs are excluded from job listing by default.
There is another table named framework_history. But it only stores retried framework object snapshots. Frameworks with no history retries don't have records in the framework_history table. And this table is not related to job archive.

I feel the definition of "archive" might be a bit complicated to end user. How about we simply call it delete? A deleted job won't appear in history server or job list view.
And we can keep all the deleted jobs in a separate table or separate DB. User can view their deleted jobs but cannot restore or further delete it (for auditing issue).
Admin can delete rows in the table.

if a job has been archived, does it appear in the history server?

After DB, there is no history job concept, only job previous retry attempts are stored in history job table.
For my previous comment "backlog storage" can be the "history job table", but this PR still keeps the archived job in "current job table" which occupy the job namespace.

I feel the definition of "archive" might be a bit complicated to end user. How about we simply call it delete? A deleted job won't appear in history server or job list view.
And we can keep all the deleted jobs in a separate table or separate DB. User can view their deleted jobs but cannot restore or further delete it (for auditing issue).
Admin can delete rows in the table.

Agree with this. But seems the orignal requirement from user, is that:

As an Administrator, I could able to archive some bad job to clean up the view for all the users. After archive, the jobs are disappeared from job list and search views, but accessible from the job url (as archived read only job). Admin and user may or may not able to restore this jobs (to be decides, comments are welcomed here).

Anyway, we need to figure out the requirement and a detailed design review before this PR.

BTW, seems what they really want is job label given the perf is not a problem anymore, such as only filter the prod jobs (non-test jobs):

We need admin user can delete some testing jobs. On developing some features in our platform based on OpenPAI, we need get the job list. If admin user cannot delete those useless jobs, the list of jobs that we get by API will be so long. And it seems that too many jobs will impact the performance of OpenPAI.

After discussion with @mydmdm , I think we may use job tag #4853 to resolve this problem.


Order with self route self

This adds the self endpoint from the identity service to align with here
A purchaser column has also been added to the database as per this ticket

lgtm


Adding assertions to test column data

assertTableColumnDataSet($record, $name, $value)
assertTableColumnDataNotSet($record, $name, $value)

Went for passing in the record rather than the key as it was simpler but can look at reworking if it is preferred. Am thinking the context of any test would have the object to hand anyway.

If the id is preferential, we can add in something like...
return function ($record_id, $name, $value): static {

        ...
        $record = $column->getLivewire()->getTableModel()::find($record_id);
        Assert::assertNotEmpty($record);

        $column->record($record);
        ...
}

I handled both record objects and keys


use ColumnScrollbar in ConvertHistoryDetailDialog

SSIA

JaCoCo Code Coverage 81.01% :white_check_mark:

Class
Covered
Meta
Status

  Generated by :no_entry_sign: Danger

Snapshot diff report

File name
Image

PreviewConvertHistoryScreenContent_NoData-Dark-2_0_compare.png

PreviewConvertHistoryScreenContent_NoData-Light-2_0_compare.png


Possible to configure policy overrides with the module?

Is it possible to configure policy overrides with the module?

I want to avoid changing the definition, but that might not be possible.
If I manually make an override by hand in the Azure Portal, terraform does not pick up the diff so I assume this is a feature request for the azurerm provider first and foremost?

@binaryPUNCH, what are you trying to change? There are multiple ways you can manipulate policies, depending on what you are trying to achieve.

So we have this "Deny restricted regions" policy. The plan was to override the policyEffect and leave it on Audit, so I can apply the necessary exemptions before removing the override so it goes back to Deny.
Alternatively, I could redo the definition and set the policyEffect as an assignable parameter, but as far as I understand that would require recreating the policy as you cannot change parameters of a policy after it has been created to my knowledge.

Got it, thank you for providing the additional context @binaryPUNCH.
As of the currently latest version of the Azure RM provider (v3.42.0), the azurerm_management_group_policy_assignment doesn't currently support the "overrides" feature, which is also currently in preview so unlikely to be supported by the provider for a little while.
That is why the module doesn't detect these changes, as Terraform doesn't know to track these attributes.

as you cannot change parameters of a policy after it has been created to my knowledge.

You actually can, as long as you are only adding new with a default value. So this may be your best option.
Regarding the module functionality, you can then set any parameters using the documented methods once the policy supports setting these.
Hope this helps.


Prevent translation of repo filter options

resolves #4209

After checking the PR out for me neither the groups nor the structure levels were translated anymore. Please provide a reproduction.
For (testing) missing/too much translation I like to create a group/structure level with the name "Agenda" if the name is translated to "Tagesordnung" I know a string is marked as "to be translated"


Publish codepoints/versions.json?

I'm interested in creating an icon picker using this package, but I'd really like to have a list of icons available so I don't need to copy the list and keep it updated. Would it be possible to publish codepoints.json and/or versions.json to npm?

I can include _data/versions.json in the package. codepoints.json is not reliable to get list of available icons as it is generated from font files and contains some extra ligatures which are not valid icons.

OK, I thought as much from one of the commits. Publishing versions.json would be very useful!


element-{web,desktop}: compile from source

Description of changes
Converts the element-web build to compile from source instead of pulling the release tarball.
Also removes the need for downloading the package.json file separately for element-desktop.
This makes overriding parts of element-web easier (for example, patching in a different version of matrix-react-sdk).

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Nice to see some node packaging that has line changes in the sub thousands :rocket:

This looks good to me, but I don't really know anything about this type of node.js app packaging. E.g. why the package.json can't be fetched/taken from src. Would that lead to IFD?
If anyone else is knowledgeable about this kind of stuff, feel free to approve, then I'll merge.

I was getting IFD when I was trying to get it from src. See commit: https://github.com/NixOS/nixpkgs/commit/fba059052a7bd2c4da88075bd39e03a49d6a10d1 and corresponding ofborg output: https://gist.github.com/GrahamcOfBorg/127a72ced21ffef0e4212d48d124e32b
Using the mkYarnPackage would require me to put the actual build in postBuild because myYarnPackage does all of the things that I'm doing in the configurePhase in the buildPhase, and I don't think that's ideal.

I got element-web working using mkYarnPackage following "<IP_ADDRESS>.2. mkYarnPackage" in the manual.
some other tweaks too, feel free to copy anything you like
https://github.com/NixOS/nixpkgs/commit/29a1879456057c734f5b4c783d35d0d462dd77d9
I had to change the lockfile with runCommand since yarn2nix doesn't let you change the lockfile in the preBuild part of the dependency fetching. Just means we do the same change before prefetching the hash.
This can be made cleaner by using something like nix-build -E "with import ./. {}; element-web.yarnLock" to get the same modified lock as within nix but that'd require changing the data in pin.json or playing around with overrides so I just went with the easy option.

Yeah the package json is read into eval here so its IFD: https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/tools/yarn2nix-moretea/yarn2nix/default.nix#L176
By the looks of it the usage of package json within eval is just for stuff like names and meta. So it'd be nice if it didn't do that, or at least had a way to turn that off. Then it'd work just fine :upside_down_face:

This shouldn't be backported as it's a pretty major change that could break things in weird ways. Please only backport important bug fixes.

 Why did you remove the wget for the package.json files though?

We have an update script that we can also run on release-21.11 correct?
Also, 21.11 will be EOLed one month after 22.05 is out :)

We can't take advantage of the automated backport, but I guess we just leave release-21.11 as is since we don't have to maintain it after a few weeks.

I'll pull in those changes, they look good. Why did you remove the wget for the package.json files though?

@sumnerevans ah sorry, that was left over from when I was playing with removing them

Without a backport, it's going to be hell to maintain, and users on stable versions of NixOS will probably just never get updates to Element.

If we just backport everything because that's easier to maintain, we might as well not have a stable distro. Backports are for important and wherever possible compatible bug fixes, even if it's a bit more effort to do.

@ofborg build element-desktop

Knock, knock. What's the hold up?

It seems that after this PR the jitsi_external_api.min.js is removed and the path in bundles is changed. Jitsi doesn't work anymore due to missing files.


Converting the execution of tpm tools to shell=False

This change converts another partial of tpm2_tools shell execution.

Almost changed all of tpm2 commands except activate_identity, there seems to be some issue with a few specific commands, doing tests on another request.

Since two PRs passed CI separately, merged #463 into this change.


Fold upstream Migrator changes into swift-4.0-branch

In https://github.com/apple/swift/pull/10414, some SE-0110 features
were backed out, so the Migrator no longer needs to add $0 shorthand
prefixing.
rdar://problem/32907276

@swift-ci Please test

Oops. Wrong branch.


changed icon color

Description of the change:
Changed the color of the UI Update icon on the release notes page.
Reason for the change:
The UI Update and API Update icons were similar in color and could cause some confusion. Closes a backlog ticket.

Hello @richbachman,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


[BUG] No explaination on how to run PHP files for Lab 9 using mySQL on Docker

Describe the bug
There is no page that describes how to run PHP files on the mySQL database that is created with Docker
Expected behavior
Explaination given for this lab.
Additional context
How to execute PHP files for Lab 9.

Can you describe what you mean by running PHP files on the mySQL db? I don't know what the assignment details are for that.

Here are the assignment instructions, this lab has always been in CSCN 326, so if you have taken the class you should be able to go back and look at it:
CSCN 326 – Lab 9 Instructions
PHP Programming
Why Learn This?
• Develop basic web programming skills and ensure access to a properly installed web
server
Prerequisite
• Perform or Review PHP Setup Workshop Instructions, located in the PHP Lab folder in
Blackboard.
• Read/Review How LAMP Is Used Today
Learning Objectives
• Understand the various technologies needed to accomplish web programming
Resources
• LAMP/WAMP installed computer
• 60 minutes
Tasks

Perform or Review the PHP Setup Workshop
Execute http://localhost/PHP-Example.php from the step above
Note one valid SID from the records displayed in the step above
Access the course folder
Copy PHP-Example.php and rename it PHP-Changed.php
Change the SQL statement in PHP-Changed.php to include a WHERE clause that selects
only the one SID noted above --- see comments in the PHP file
Save the changed script and execute http://localhost/PHP-Changed.php
Verify only that single record is retrieved
Submit a zip file containing a screen shot of your output (saved in a Word document) and
your PHP-Changed.php file to the appropriate assignment link in Canvas.

https://github.com/PostGuitarist/liberty-macos-docs/pull/11
This has been merged. Take a look at the end of the MySQL section.


Handle the documentation template

Is this covered by the docssearch and or default strategy?

Yes, absolutely :)


Can't build ReactTemplateTS

Not sure what is going, but i can't build the project
Have tried: npm install and failed

What's the error?

2019-07-17T21_38_07_370Z-debug.log

i maybe do something wrong! Here are some step to run your solution that i have tried

Open Content folder and run
npm install
npm run build
Open solution with Visual Studio 2017, run, but error

Can you try the original ReactTemplate?  The steps are just: npm i, followed by dotnet run.   The ReactTemplateTS was from a PR contributor and I don't really maintain it.

got ya, thanks for helping:)

yeah, it is working now


Issue with NotePlan

I'm having an issue using NotePlan with yabai. When I close the NotePlan window, yabai doesn't seem to detect that the window was closed and the space where the window was previously open remains there on the screen.
https://github.com/user-attachments/assets/aaa487f5-c99b-47f9-a06d-c0edfac2ae70
I ran this command yabai -m query --windows | jq '.[] | select(.app == "NotePlan")' to see how the properties change as I interact with the window.
After closing the window by pressing the red "x" button on the top left, I see that the title, role, and subrole were all set to empty strings; and the can-move, can-resize, and is-visible properties were all changed from true to false.
Then, after re-opening the window, I see that the is-visible flag changes to true but everything else remains the same.

I also noticed that when I minimize the screen by pressing the yellow "-" sign, it seems to work properly and snap back into the grid. It also retains the title, role, and subrole properties.
https://github.com/user-attachments/assets/d12553e9-e0f0-42fc-aa29-0a6ef3448bf3


03/31/2018 02:44 : Create Pull Request for branch prTesting_2018033102 -> master

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add Brazilian Portuguese on this extension

Is your feature request related to a problem? Please describe.
No, only adding new internationalization.
Describe the solution you'd like
One pt_BR folder on _locales. So it automatically opens up on browsers with pt_BR default.
Describe alternatives you've considered
One pt_BR folder on _locales.
Already tested the changes locally Chrome browser. Please assign it to me when accepted.

All, clear. As soon as you make sure all things work correctly, please create a PR into major-2.0 branch instead of master

#54 is open to major-2.0

Thanks for your contribution to the project!
I've just completed new version and submitted to Chrome Webstore, Microsoft Edge Add-ons Webstore and Firefox Add-ons Webstore. It has already been approved in both Chrome and FIrefox stores and will be available soon on Microsoft Edge. You can also download latest version from GitHub Releases and test it.
Note that sideloaded extensions work as completely different ones so they don't interfere with officially installed extensions. It means that you don't have to remove the currently installed version


Component Error in Ignition 8.1.39

In the Ignition 8.1.39, the Apexchart component doesn't render and error:

This issue has been fixed in 1.0.17:
https://github.com/Kyvis-Labs/ignition-apexcharts-module/releases/tag/1.0.17

Getting this erros now with 8.1.42 and 1.0.18


refresh advisor to fix paging issue of function recommendations.list()

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-arm-advisor


Automated cherry pick of #10295

Cherry pick of #10295 on release-7.0.
/cc  @pvev
NONE

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

Trying to auto merge this PR.

Pull Request successfully merged
SHA: 43a2bee255f7dc7cf0b2274f17082d4ebc180dea


what's the principle of camera calibration of "O3D303"?

Hi guys,
I understand that we can turn on the rectification flags for amplitude and the distance image through "ifm3d dump" to calibrate the camera. In addition, I have already looked through other issues but I am still confused about the principle of calibration, since the answer in other issues link to different paper and multiple resources. Therefore, could you please provide a link/paper that can explain the principle of calibration.
Looking for your reply,
carolina

Hi @Carolinadeveloper -- could you help me understand a bit more about what you're trying to learn?
There are two types of calibrations:

intrinsic: This releates to the physics of the camera lens and how light is distorted passing through the lens to the photo imager. This information can be used to do rectification (de-warping of the data). Our cameras are factory calibrated for intrinsics and as you've noted there are built-in features to do this work automatically. I think most of the other issues you're talking about are referring to this type of calibration

extrinsic: This is the process of registering the camera's optical coordinate frame (the coordinate frame in which data values are returned from the sensor) against another global coordinate frame, say a vehicle frame, or with respect to other cameras.

Do either of these sound like what you're trying to achieve?

Hi @Carolinadeveloper -- could you help me understand a bit more about what you're trying to learn?
There are two types of calibrations:

intrinsic: This releates to the physics of the camera lens and how light is distorted passing through the lens to the photo imager. This information can be used to do rectification (de-warping of the data). Our cameras are factory calibrated for intrinsics and as you've noted there are built-in features to do this work automatically. I think most of the other issues you're talking about are referring to this type of calibration
extrinsic: This is the process of registering the camera's optical coordinate frame (the coordinate frame in which data values are returned from the sensor) against another global coordinate frame, say a vehicle frame, or with respect to other cameras.

Do either of these sound like what you're trying to achieve?

Hi theseankelly @theseankelly ,
What I want to learn is how u guys factory calibrate for intrinsic? Since I want to recalibrate the camera and check the parameters you provided to improve the accuracy. I did Zhang's calibration with grayscale/rgb of chessboard images collected before, but for O3D303 I only found DistanceImage, AmplitudeImage, and ConfidenceImage, I don't know which images information can be used for recalibration?
Carolina

@Carolinadeveloper Carolinadeveloper for the camera distance calibration we have different ways to do this. Due to the fact we need distance information from defined situations to calibrate the 3D offset to fit the camera body those values are calculated during this process. This is different from the way a classical 2D camera is calibrated. This information is considered confidential an exceeds the detail level of an GitHub issue. Please get in touch with your ifm representative to discuss the details.
For using the checkerboard the amplitude image is the image you are looking for.

@Carolinadeveloper for the camera distance calibration we have different ways to do this. Due to the fact we need distance information from defined situations to calibrate the 3D offset to fit the camera body those values are calculated during this process. This is different from the way a classical 2D camera is calibrated. This information is considered confidential an exceeds the detail level of an GitHub issue. Please get in touch with your ifm representative to discuss the details.
For using the checkerboard the amplitude image is the image you are looking for.

Hi  @graugans,
Thank you for your reply, if I use checkerboard & amplitude image to recalibrate, how can I modify the calibrated parameters, is there provide any interface like "ifm3d dump" ?

Hi @Carolinadeveloper -- there is no mechanism for saving the calibration parameters back to the device. Your custom calibration will produce a new set of unit vectors, which you will need to apply to the radial distance image and generate cartesian information yourself.
That said, we have a fairly advanced factory calibration process and I'd love to learn more about why you feel the need to recalibrate -- what kinds of measurement error are you seeing that's driving this effort?

Hi @Carolinadeveloper I'm closing this issue because as far as I can tell the questions have been answered. Feel free to reactivate if not true.


chore: add c++ tests for generator derivation

This PR adds some tests just to give ground truth values for hash_to_curve and derive_generators which can replicated in test suites for reimplementations of this logic elsewhere

Benchmark results
Metrics with a significant change:

app_circuit_proving_time_in_ms (Test:emit_nullifier): 1,815 (-31%)
app_circuit_proving_time_in_ms (FPC:fee_entrypoint_public): 9,665 (-40%)
protocol_circuit_witness_generation_time_in_ms (base-parity): 339 (-37%)
protocol_circuit_witness_generation_time_in_ms (public-kernel-app-logic): 311 (-29%)
protocol_circuit_witness_generation_time_in_ms (merge-rollup): 89.9 (-43%)
protocol_circuit_proving_time_in_ms (public-kernel-app-logic): 753 (-30%)
protocol_circuit_proving_time_in_ms (merge-rollup): 1,584 (-32%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
740
740
740

l1_rollup_calldata_gas
6,692
6,692
6,668

l1_rollup_execution_gas
586,877
586,877
586,853

l2_block_processing_time_in_ms
1,598
6,028
12,013

l2_block_building_time_in_ms
35,159
138,683
277,032

l2_block_rollup_simulation_time_in_ms
34,934
137,912
275,524

l2_block_public_tx_process_time_in_ms
16,458 (-1%)
70,268
142,775

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
17,909 (+1%)
33,700

node_database_size_in_bytes
21,356,624
38,051,920

pxe_database_size_in_bytes
29,868
59,425

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Circuit
protocol_circuit_simulation_time_in_ms
protocol_circuit_witness_generation_time_in_ms
protocol_circuit_proving_time_in_ms
protocol_circuit_input_size_in_bytes
protocol_circuit_output_size_in_bytes
protocol_circuit_proof_size_in_bytes
protocol_circuit_num_public_inputs
protocol_circuit_size_in_gates

private-kernel-init
164 (+1%)
3,583
22,733 (-3%)
20,412
62,374
85,376
2,601
1,048,576

private-kernel-inner
537 (+1%)
4,637 (+8%)
45,465
89,855
62,374
85,376
2,601
2,097,152

private-kernel-reset
1,006 (+1%)
6,463
88,086
330,808
62,374
85,376
2,601
4,194,304

private-kernel-tail
535 (+1%)
5,161 (+4%)
38,981
87,224
79,333
10,656
266
2,097,152

base-parity
8.32 (+2%)
:warning: 339 (-37%)
4,238 (+7%)
128
64.0
2,208
2.00
131,072

root-parity
52.0 (+2%)
148 (-3%)
38,339
27,064
64.0
2,720
18.0
2,097,152

base-rollup
934 (+2%)
5,230 (+14%)
43,360
111,126
925
3,104
30.0
2,097,152

root-rollup
72.9
177 (+5%)
8,315 (-1%)
11,454
789
3,424
40.0
524,288

public-kernel-app-logic
195 (+1%)
:warning: 311 (-29%)
:warning: 753 (-30%)
96,791
84,967
113,344
3,475
4,096

public-kernel-tail
896 (+1%)
830 (+13%)
1,054 (-5%)
388,047
7,723
10,144
250
512

public-kernel-setup
166 (+4%)
360 (-8%)
915 (-4%)
137,024
84,967
113,344
3,475
4,096

public-kernel-teardown
169
408 (-11%)
1,139 (+1%)
141,902
84,967
113,344
3,475
4,096

merge-rollup
7.01 (+3%)
:warning: 89.9 (-43%)
:warning: 1,584 (-32%)
2,696
925
3,104
30.0
65,536

private-kernel-tail-to-public
N/A
10,503 (-2%)
68,114
N/A
N/A
113,856
3,491
4,194,304

Stats on running time collected for app circuits

Function
app_circuit_proof_size_in_bytes
app_circuit_proving_time_in_ms
app_circuit_size_in_gates
app_circuit_num_public_inputs

SchnorrAccount:entrypoint
15,456
47,121 (-2%)
2,097,152
416

Test:emit_nullifier
15,456
:warning: 1,815 (-31%)
65,536
416

FPC:fee_entrypoint_public
15,456
:warning: 9,665 (-40%)
524,288
416

Token:transfer
15,456
39,483 (-1%)
2,097,152
416

FPC:fee_entrypoint_private
15,456
9,015
524,288
416

Token:unshield
15,456
37,049
2,097,152
416

SchnorrAccount:spend_private_authwit
15,456
2,658
131,072
416

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
13.2
21.5
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.8
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.770
0.662
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
62.0 (+1%)
97.0
314
611
1,189
2,359
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.636 (+1%)
0.600
0.572
0.571
0.565
0.564
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
74.3 (+1%)
143
453
894
1,770
3,529
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
106
208
692
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.649 (+1%)
0.645
0.617
0.617
0.615
0.616
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
80.9

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
108

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.711

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
84,315
673,143

Transaction size based on fee payment method
| Metric |  |
| - |  |
Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes
2 new note hashes

tx_pxe_processing_time_ms
37,553
3,687 (+1%)
113,485

Metric
0 public data writes
1 public data writes
2 public data writes
4 public data writes
8 public data writes

tx_sequencer_processing_time_ms
1,307 (-1%)
2,289 (+2%)
1,905 (+1%)
2,840 (+1%)
1,825 (+1%)


Support snapshots

Snapshopts are unfinished experiments.
The idea is to save partial results (in a dedicated folder) that could be used to implement fancier random search algorithms. (e.g. Population Based Training.) They are also useful for very long / tedious experiments where saving intermediary results is useful.
One way to do it is to create a dedicated subfolder for these in same vein as attachments. However careful (and efficient) annotations need to be added in order to support "versioning" of snapshots. (both dumping and loading) Those should support the usual result + attachments.
Another way to do it is taking advantage of the current infrastructure, and use experiment names for versioning. This is simpler (and maybe cleaner) but it requires adding functions to modify/extend JSON summaries and saving these modified JSON summaries in a separate experiment.

Ideally, if a snapshot is extended you would be able to retrieve the history of hyperparameters that were used at each snapshot.


Make PubSub streamable to gRPC by default

The PubSub abstraction could allow us to expose an gRPC streaming endpoint which sets up a subscription to the TopicActor for a given topic.
e.g.
client connects to grpc endpoint, pass along that it wants to subscribe to topic "abc".
an actual PubSub-subscription is setup for a temp actor to topic "abc"
the temp actor now publishes everything onto a result gRPC stream.
This way, we can very easily create realtime integrations to proto clusters

https://protoactor.discourse.group/t/experimental-proto-cluster-pubsub/15


Add hint text to support request edit dialog for tracking DMCA takedowns

For example:
If resolving a DMCA request add offender account names (in single quotes, comma-delimited), offending package id, and resolution (no action, withdrawn, upheld). Example: accounts:'foo1','foo2' id:BarPkg resolution: upheld)
This will make the text more searchable, and will assist us in identifying repeat offenders in the DMCA space.

@drewgillies , this is probably already deployed


Why there are two choices of Ubuntu using WSL2 with windows terminal?

Why there are two choices of Ubuntu and what is the difference? I'm a newcomer to WSL. I'd appreciate it if you could answer this issue. THANKS!

This seems to be a bit of a bug (or just timing issue) in the Ubuntu installer, but it seems to be on the Canonical end from my research -- Not a WSL issue, although there may be an additional Windows Terminal bug in play.
The "Ubuntu" with the Penguin icon is created by Windows Terminal as part of the WSL provider.  Terminal will automatically detect all installed WSL distributions and create a profile for each.
The second one, with the Ubuntu icon, is created by a JSON Fragment Extension in the Ubuntu package.
What is supposed to happen is that the JSON Fragment Extension is supposed to hide the auto-generated one.  But for some reason, the GUID is wrong in the JSON.
It's possible (even likely) to end up in a situation where you can't even hide (or delete) the second one, since it will always be regenerated on restart.  This is due to a "corrupt" (bad state) state.json for Windows Terminal.
The easiest way to recover is to delete both settings.json and state.json from %userprofile%\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState.  Of course, this means that you'll need to recreate any Terminal settings you've changed.
It's also possible to manually set the GUID in state.json if you know how, but I haven't gone through that process myself to document it.  If you need more information on what's going on here, see my answers on these two Super User questions:

Can't delete or hide duplicate Ubuntu Profile in Windows Terminal
Different profiles of the same WSL2 linux instance in Windows Terminal

The Windows Terminal GitHub is probably a better place for this question. They auto-create these.

note: you can choose to hide profile from dropdown here.


URL BUG

Description
Sometimes if hit shrty.rf.gd -> then by default shrty.rf.gd?i=1# appear on URL.
What could be the reason and how to solve it ?
Screenshots
No response
Additional information
No response

@apoorvaron
Refer this Article
But in Short
The ?i=1 suffix in the URL is a security measure to protect your website. It ensures that your website can only be accessed through regular web browsers. It acts as a counter, verifying your browser's ability to execute code and store a cookie. If the security system cookie is not present, your browser will receive a new security challenge and be redirected to a URL with an incremented counter (?i=2, ?i=3, and so on). If the counter reaches 3 without a valid cookie, you will be redirected to a page with instructions on enabling cookies. Unfortunately, you cannot remove the ?i=1 URL suffix because the security system is mandatory for all websites.
but still i have  a found solution which adds some  code in .htaccess from some forum but it can create issues
you can try it , i cant check since i have local hosting not a webhosted

@Nishitbaria if this can create issue, then there is no need to remove it. So, closing this issue.
Also, can you share the .htaccess code? To see how it can be removed


social links values

Hi, I'm having trouble finding out what values I should put in for the social links in the TOML. For example, for twitter I assume I would put in my twitter handle. However after deployment the link isn't pointing to twitter but to my own website. Even on https://themes.gohugo.io/theme/hugo-theme-noteworthy/, the links are pointing back to the website and not to the social sites.

I used the full url's. Here is my config.toml.


Merge release-0.3 branch into master

Then we will merge release-1.0 as well, so we have master branch up-to-date.
Important: we will not create a new release from master after merging this, it's just about finally bringing git repository into a consistent up-to-date state, so we can continue working with 1.x releases.

Actually let's create a PR where we have a working branch, not just merge commits


TAS: Updates or deletion of Topology is not reflected in TAS cache resulting in wrong admission

What happened:
The updates to the TAS topology object are not tracked by the resource_flavor controller.
As a consequence:

after deletion of the topology workloads continue to be admitted
after mutating the topology workloads are admitted using the old topology

What you expected to happen:
Updates or deletion to the Topology object are observed and reflected by changing the cache status
Fixing both scenarios can be separate PRs (probably preferred). I think we can cover the scenarios at the integration test level (since we don't need to create pods as in e2e).
How to reproduce it (as minimally and precisely as possible):
Scenario 1 (for deletion):
create the TAS structure
apiVersion: kueue.x-k8s.io/v1alpha1
kind: Topology
metadata:
  name: "gke-default"
spec:
  levels:
  - nodeLabel: "kubernetes.io/hostname"
---
kind: ResourceFlavor
apiVersion: kueue.x-k8s.io/v1beta1
metadata:
  name: "tas-flavor"
spec:
  nodeLabels:
    kubernetes.io/os: "linux"
    #    cloud.google.com/gke-nodepool: "tas-node-pool"
  topologyName: "gke-default"
---
apiVersion: kueue.x-k8s.io/v1beta1
kind: ClusterQueue
metadata:
  name: "tas-cluster-queue"
spec:
  namespaceSelector: {} # match all.
  resourceGroups:
  - coveredResources: ["cpu", "memory"]
    flavors:
    - name: "tas-flavor"
      resources:
      - name: "cpu"
        nominalQuota: 200
      - name: "memory"
        nominalQuota: 200Gi
---
apiVersion: kueue.x-k8s.io/v1beta1
kind: LocalQueue
metadata:
  namespace: "default"
  name: "tas-user-queue"
spec:
  clusterQueue: "tas-cluster-queue"

delete the topology
create a workload like this

apiVersion: batch/v1
kind: Job
metadata:
  generateName: tas-sample-small-required-host-
  labels:
    kueue.x-k8s.io/queue-name: tas-user-queue
spec:
  parallelism: 1
  completions: 1
  completionMode: Indexed
  template:
    metadata:
      annotations:
        kueue.x-k8s.io/podset-required-topology: "kubernetes.io/hostname"
    spec:
      containers:
      - name: dummy-job
        image: gcr.io/k8s-staging-perf-tests/sleep:v0.1.0
        args: ["1800s"]
        resources:
          requests:
            cpu: "1"
            memory: "200Mi"
      restartPolicy: Never

issue: the workload gets admitted
Scenario 2:

instead of deleting the topology in (2.) change the level label to some non-existing
create the same workload - workload gets admitted

/assign @mbobrovskyi
cc @PBundyra

I think we need to start watching for updates to the Topology objects similarly as we watch Nodes, and we need indexer to quickly find what are the ResourceFlavor objects affected by Topology change (and reconcile them). The Reconcile function itself also needs fixes.